Objective-C Headers

This is a neat project. Is there a way to use this in an objective-c project?

Hi @electic! Thanks for interest to our component!
Unfortunately, it's not possible to subclass a Swift class in Objective-C. Straight from the docs:

You cannot subclass a Swift class in Objective-C.


When is the state of the session set to connected when requestSession is established?

As the title says

When the connection is ready to send and receive messages

When the connection is ready to send and receive messages

Actually when request a presentation session by use the example:
var presentation = navigator.presentation;
var session = presentation.requestSession("my.html");
session.onstatechange = function() {
switch (session.state) {
case 'connected':
session.postMessage(/.../);
session.onmessage = function() { /.../ };
break;
case 'disconnected':
console.log('Disconnected.');
break;
}
};
The code above is to get connection, i think
when execute session.onstatechange, none of the code in the body of the method executes.
Expected to get session.state to execute switch (session.state) but not.


What a best way to handle exception in service ctor?

Hi all
This is theoretical question, not an issue.
We have some services that need to read configuration and may fails. We already have some ETW logging to handle this, so logging itself works fine.
The little problem came from another side: if ctor throw exception then Service Fabric tries to re-init the service.
Let's take OOB code with some very minor modifications (they all about logging):
private static void Main()
        {
            StatelessServiceContext sharedContext = null;

            try
            {
                // The ServiceManifest.XML file defines one or more service type names.
                // Registering a service maps a service type name to a .NET type.
                // When Service Fabric creates an instance of this service type,
                // an instance of the class is created in this host process.

                ServiceRuntime.RegisterServiceAsync("MyServiceType",
                    context =>
                    {
                        sharedContext = context;
                        return new MyService(context);
                    }).GetAwaiter().GetResult();

                ServiceFabricEventSource.Instance.ServiceTypeRegistered(Process.GetCurrentProcess().Id, typeof(AuditTrailService).Name);

                // Prevents this host process from terminating so services keep running.
                Thread.Sleep(Timeout.Infinite);
            }
            catch (Exception e)
            {
                ServiceFabricEventSource.Instance.ServiceHostInitializationFailed(e, sharedContext);
                throw;
            }
        }

Let's assume that MyService ctor throw an exception. In this case code inside RegisterServiceAsync's lambda will be executed again and again. Good in dev, but really not good in production, because that will flood logs. I understand why this was done like this in Service Fabric, but sometime service can't be fix just by re-init.
What I did (I have found this sample in Azure/diagnostics-eventflow and adopt to "clean" Service Fabric):
private static void Main()
{
	StatelessServiceContext sharedContext = null;
	try
	{
		using (ManualResetEvent terminationEvent = new ManualResetEvent(initialState: false))
		{
			Console.CancelKeyPress += (sender, eventArgs) => Shutdown(terminationEvent);
			AppDomain.CurrentDomain.UnhandledException += (sender, unhandledExceptionArgs) =>
			{
				if(unhandledExceptionArgs.ExceptionObject is Exception e)
					ServiceFabricEventSource.Instance.ServiceHostInitializationFailed(e, sharedContext);
				Shutdown(terminationEvent);
			};

			ServiceRuntime.RegisterServiceAsync("MyService",
				context =>
				{
					try
					{
						sharedContext = context;
						return new MyService(contex);
					}
					catch (Exception e)
					{
						ServiceFabricEventSource.Instance.ServiceHostInitializationFailed(e, sharedContext);
						Shutdown(terminationEvent);
						throw;
					}
				}).Wait();

			ServiceFabricEventSource.Instance.ServiceTypeRegistered(Process.GetCurrentProcess().Id, typeof(BinaryManagerService).Name);

			terminationEvent.WaitOne();
		}
	}
	catch (Exception e)
	{
		ServiceFabricEventSource.Instance.ServiceHostInitializationFailed(e, sharedContext);
		throw;
	}
}

private static void Shutdown(ManualResetEvent terminationEvent)
{
	try
	{
		// we could do something here if needed
	}
	finally
	{
		terminationEvent.Set();
	}
}

So here I just finish the process if ctor throw an exception.
Now questions:

Will Service Fabric engine supports this?
What will happen when process shutdown?
Right now I see that local cluster tries to restart process couple times and then do nothing (that good for me). Will it be same in Azure?

I suggest using Environment.FailFast() if you want the process to shut down after an exception from your service constructor. Much simpler to implement and read than using a manual reset event to let the process end gracefully, and it will actually be treated as an error (which it is) and will be logged in the Windows event log.
Shouldn't be a problem doing this. SF will attempt to restart the process a number of times before giving up for a period of time on a node type. Doesn't matter where your SF cluster is hosted, works the same way everywhere.
Finally, I would recommend finding a better place to load your config. Any heavy lifting or throwing from a constructor is bad in general. Couple other options you can try:

Load the config in Main() before registering the service type, then pass the config object to your service's constructor. This has the added benefit of allowing you to pass mock configurations to your service constructor for easier unit testing. Downside to this is that every instance of the service type will have the same config.
Use the OnOpenAsync() event inside your service class to load config. This is called by Service Fabric once when the service instance is created. This is a good place to perform heavy or async operations, and you can throw normally if it fails and let Service Fabric re-create the replica and try again.

@vturecek, thank you for your answer. Let me comment point by point.

We are using config packages for sure, and they are loaded in service ctor. Config loading may fail by many reasons, nut mostly because or wrong encryption of the value (at least this is most common reason in your case).
Because of (1), it's a bit hard to read config in main method, because we need to have the context of the service
Well, actually I want to avoid re-create of the replica. What behavior I really want from Service Fabric is to shutdown the replica with failed state in SF. Is it possible at all?

I suggest using Environment.FailFast() if you want the process to shut down after an exception from your service constructor. Much simpler to implement and read than using a manual reset event to let the process end gracefully, and it will actually be treated as an error (which it is) and will be logged in the Windows event log.
Shouldn't be a problem doing this. SF will attempt to restart the process a number of times before giving up for a period of time on a node type. Doesn't matter where your SF cluster is hosted, works the same way everywhere.
Finally, I would recommend finding a better place to load your config. Any heavy lifting or throwing from a constructor is bad in general. Couple other options you can try:

Use config packages to store and load config. This is the safest and recommended approach to managing configuration for services in Service Fabric.
Load the config in Main() before registering the service type, then pass the config object to your service's constructor. This has the added benefit of allowing you to pass mock configurations to your service constructor for easier unit testing. Downside to this is that every instance of the service type will have the same config.
Use the OnOpenAsync() event inside your service class to load config. This is called by Service Fabric once when the service instance is created. This is a good place to perform heavy or async operations, and you can throw normally if it fails and let Service Fabric re-create the replica and try again.

Is there a documentation on the number of times SF re-tries and the interval between each retry.


Issue 1

Checklist

[x] Used a personal fork of the feedstock to propose changes
[x] Bumped the build number (if the version is unchanged)
[x] Reset the build number to 0 (if the version changed)
[x] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[x] Ensured the license file is being packaged.

@conda-forge-admin, please rerender

@conda-forge-admin, please rerender

Artifacts can be downloaded from the azure pipeline and tested using the following:
https://conda-forge.org/docs/maintainer/knowledge_base/#local-testing
https://conda-forge.org/docs/maintainer/updating_pkgs/#testing-changes-locally

@conda-forge-admin, please ping team

Not trying to be annoying but we're trying to use this package in a class next week.

Dear @scharlton2, thank you for this.
You made same approach as I was having in mind.


lifewatch logo is broken in authors pkgdown page

https://inbo.github.io/camtraptor/authors.html

Also broken on other lifewatch packages pkgdown websites:
https://docs.ropensci.org/frictionless/

See https://github.com/frictionlessdata/frictionless-r/commit/9af0da8d0528c65b474ad498f9f5ff12a7f7d1bd

This issue has been solved via https://github.com/inbo/camtraptor/commit/48c9a574877680dc4e49839c1594b99a303fc45c. Version 1.0 will contain the correct logo.


Proposal: Publish command

The main purpose of the publish command is to create a release. It would executes the following sub commands:

check local repository is clean (no uncommitted files) and all commits have been pushed.
prompt user for input values (see below)
create a git tag with the following parameters:

tag: semver based on the latest release fetched from the server + 1. A flag determines whether +1 means MAJOR, MINOR or PATCH
object: the latest local commit SHA.

create a github release, with the following parameters:

tag_name: the tag previously created
name: prompt user
body: prompt user
draft: false
prerelease: prompt user

Optional: pull tags
Update version in manifest
Register github repo to OW hub. If already registered, this is a noop.

Note that 3, 4  and 7 are server-side commands run by OW actions. This actions should probably be implemented in a different github project.

3 is not needed. 4 does 3.

Sorry, did not mean to close.
I think this feature will be very useful for developers.  At some point could it also submit the repo for review to a public registry of other OW packages?


editor.action.quickFix command cannot be completed using the keyboard

VSCode Version: 1.11.1
OS Version: Windows 10

Steps to Reproduce:

In editor (typescript file) use editor.action.quickFix command (ctrl+.) to automatically generate import statement for certain type
Pop-up window is shown with the one or more options (e.g. Import xxx from 'yyy')
It is not possible to select any popup menu item using keyboard (arrow keys). So in my case, I need to use touchpad or mouse to choose the menu item.

Which color theme are you using? The selection color seems to be more subtle than it used to be. Maybe it still works without the selected item being highlighted?

So I am using: Monokai Dimmed.
You are right, it is working, but the selected item is highlighted very subtle. It is very confusing in case when only one menu item is in the popup list (basically you cannot see the difference in transition from non-selected to selected item).
Basically, for light themes the difference is obvious, but for dark group of themes is not.

I think it's a native menu, not sure if we have controls over the colors

Yes, it's the native context menu

 I can also not reproduce on windows

Closing because this issue is without actionable information.


[PAN-2752] Add findPrivacyGroup endpoint

findPrivacyGroup returns the list of all the details of the privacy groups the given addresses are a part of.

Waiting for https://github.com/PegaSysEng/orion/pull/251 to be merged


Request: Randomly change the search engine with a 70% higher chance of it being Ask.com

please

Make it so searching will open every search engine

70% chance of ask, 30% chance of wikipedia


https://issues.apache.org/jira/browse/SPARK-17614

What changes were proposed in this pull request?
Use JdbcDialect's getTableExistsQuery rather than the hard-coded "SELECT * FROM $table WHERE 1=0" to get table's schema.
How was this patch tested?
Create unit test using DataFrameReader.read() with Cassandra can test this since Cassandra does  not support "SELECT * FROM $table WHERE 1=0".

@paulzwu something's wrong with this, can you try again from master?

Can one of the admins verify this patch?


Fix repo-search template errors for go1.7

Should fix #2331.

LGTM

Can confirm that it fixes #2331

LGTM


Added switch for warnings as errors

This can be handy if you want to be really strict about code warnings.

Not sure why Ruby 2.1.3 is failing.
Lots of people are referencing adding this step to .travis.yml
before_install:
  - gem install bundler

https://github.com/travis-ci/travis-ci/issues/5239
https://github.com/rubygems/rubygems/issues/1419

@richy486 This seems reasonable, but I'm curious why don't you just enable "Treat warnings as errors" on your project.

@marcelofabri good idea! I just wanted to make sure the CI is showing the errors regardless of the individual developer environment setup

@diogot This can probably be closed

👍


certificate invalid error for self-signed cert

I have a marathon deployment using mantl which uses aws loadbalancing and self-signed certs.
depcon -e dev mar app list
2016-04-14 14:56:49 ERROR [depcon]: Get https://k4b4-mantl-control-01.node.c1.io/marathon/v2/apps: x509: certificate is valid for localhost, *.node.consul, *.service.consul, not k4b4-mantl-control-01.node.c1.io
Maybe there should be an option to allow self-signed certs to be accepted.
I can browse to this page fine, there is just an insecure ssl connection browser warning.

Ok, Just released 0.8.3 which should cover that.  Can grab a new binary under the releases.
I will look into making this an option in the config for the environment depending on if this fixes it or not.
A new --insecure flag under all marathon commands is now available.
Example:
depcon -e dev mar app list --insecure

Let me know if this fixes your case

Thanks for the quick turnaround!
I still see an error with the new binary.
(master)][brew_py2] depcon -e dev mar --insecure  app list
2016-04-19 09:41:14 ERROR [depcon]: Get https://k4b4-mantl-control-01.node.c1.io/marathon/v2/apps: x509: certificate signed by unknown authority
I'm going to try and get a proper cert installed in the mean time.

I'm using version .86 and I am also seeing this on my mantl cluster.
/work/Official/depcon$ ./depcon-osx64 app list --insecure
2016-05-12 15:03:37 ERROR [depcon]: Get https://control.z.blahblahablah.com/marathon//v2/apps: x509: certificate is valid for localhost, *.node.consul, *.service.consul, not blahblahblahblah.z.tropo.com

#44 fixes this.


[Dubbo-2218] Fix the issuse: When using telnet "invoke" method, if there is a [null] param, the response always be [null]  #2218 team3

What is the purpose of the change
fix issue #2218, by BaiJi the 269th team3
Brief changelog
When using telnet "invoke" method, if there is a [null] param, the response is not  always null
Verifying this change
XXXXX
Follow this checklist to help us incorporate your contribution quickly and easily:

[x] Make sure there is a GITHUB_issue filed for the change (usually before you start working on it). Trivial changes like typos do not require a GITHUB issue. Your pull request should address just this issue, without pulling in other changes - one PR resolves one issue.
[x] Format the pull request title like [Dubbo-XXX] Fix UnknownException when host config not exist #XXX. Each commit in the pull request should have a meaningful subject line and body.
[x] Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
[ ] Write necessary unit-test to verify your logic correction, more mock a little better when cross module dependency exist. If the new feature or significant change is committed, please remember to add integration-test in test module.
[x] Run mvn clean install -DskipTests & mvn clean test-compile failsafe:integration-test to make sure unit-test and integration-test pass.
[x] If this contribution is large, please follow the Software Donation Guide.

You should use:
if (condition) {
        do_this();
        do_that();
} else if {
        otherwise();
} else {
        otherwise();
}

By team 5.


removed extra blank line between sections

Checklist:

[ ] I have read freeCodeCamp's contribution guidelines.
[ ] My pull request has a descriptive title (not a vague title like Update index.md)
[ ] My pull request targets the main branch of freeCodeCamp.
[ ] I have tested these changes either locally on my machine, or GitPod.

Closes #XXXXX

Hey @sahilbalia
Thank you for opening this pull request.
This is a standard message notifying you that we've reviewed your pull request and have decided not to merge it. We would welcome future pull requests from you.
Thank you and happy coding.


Carry through Exit Code

Hi, thanks for such a useful action!
After trying this out, I'm a little confused on how to properly fail the workflow job if one of the terraform steps fail.
We're passing continue-on-error: true to the terraform step, like the example shows.    It seems the commenter step(s) should exit non-zero after posting the comment as to stop processing subsequent job steps, but the commenter exits zero even when it was handed a non-zero from the terraform wrapper.
I feel like I'm missing something obvious but the readme states

In English: "Always run this step, but only on a pull request and only when the previous step succeeds or fails...and then stop the build.

What trigger should be used stop the build?
Thanks again!

Completely agree with this one. I think the exit code should carry through.


Enhancement: Granular Plugin Control

What features would you like to see added?
It would be nice for an enterprise deployment to be able to control a list of allowed plugins without codebase modification (for those who fork the public repository).
More details
A number of plugin definitions are included in LibreChat's codebase. We'd rather not create drift between the upstream LibreChat codebase and our Fork by deleting plugin definitions.
Which components are impacted by your request?
Plugins
Pictures
No response
Code of Conduct

[X] I agree to follow this project's Code of Conduct

Understandable! This is planned along with granular user access control in general.


Add questions about revenue and sustainability to README

And put the questions at the top of the README

"Do we generate enough money to keep Interlock in business?"
"Will users generate enough revenue for users to keep using it?"


Scancode and fossology scans

Adding scancode-toolkit and fossology scans for licensing/copyright vetting. Bumping gotests image to latest version.

/approve

/approve
/lgtm


How to use amplitude in React?

Hi. Your library works great with just plain HTML file, but how can I use it with React?
So far I've managed to successfully play music only with autoplay function. Cannot make buttons to work.
I'll apreciate any help.

would you share with me how you even started using it with react. where do i put the amplitude.init()
Im also not seeing any buttons

I'm not really familiar with React, but if it's anything like Vue, you will need to put the Amplitude.init() method in a created() lifecycle hook or the React equivalent. The HTML needs to be there to bind events to elements.


Recursion error on instancecheck when making sub-serializers inherit from a PolymorphicSerializer child

Hi everyone,
Here is my situation:

In my Django models, I have a ParentModel class that inherits from django-polymorphic's PolymorphicModel. ParentModel is also inherited by some children, such as ChildModelA, ChildModelB, etc. ParentModel is not abstract and ChildModelA, B are not proxy models. I need this setup because ParentModel has attributes that I need to link to its children. When I run ParentModel.objects.all() in the console, django-polymorphic behaves as expected and returns me a collection of ChildModelA, ChildModelB, etc., even if they actually inherit the "polymorphic traits" of the 2nd-level parent.
However, django-rest-polymorphic strikes me with RecursionError: maximum recursion depth exceeded in __instancecheck__ when I try to replicate this setup for my corresponding serializer classes.
I realized that this is fixed by not making my children serializer classes inherit ParentModelSerializer, but that defeats the purpose of what I want to achieve. So, I don't know if what I'm asking for is a bug fix or a feature request.

Thank you in advance for your time.
Here is the code to clarify (field declarations are not accurate for the sake of simplicity):

In the models file:

class ParentModel(PolymorphicModel):
    attributeA = models.CharField()
    attributeB = models.IntField()

class ChildModelA(ParentModel):
    attributeC = models.ForeignKey()
    attributeD = models.URLField()

class ChildModelB(ParentModel):
...

When running ParentModel.objects.all():

[<ChildModelA: ChildModelA object (3739843)>, <ChildModelB: ChildModelB object (3098393)>, ...]

In the serializers file:

class ParentModelSerializer(serializers.ModelSerializer, PolymorphicSerializer):
    attributeA = serializers.CharField()
    attributeB = serializers.IntField()

    class Meta:
        model = ParentModel

        fields = [
            "attributeA",
            "attributeB",
        ]

class ChildModelASerializer(ParentModelSerializer):
    attributeC = serializers.HyperlinkedRelatedField()
    attributeD = serializers.URLField()

    class Meta:
        model = ChildModelA

        fields = [
            "attributeC",
            "attributeD",
        ]

class ChildModelBSerializer(ParentModelSerializer):
...

ParentModelSerializer.model_serializer_mapping = {
    ChildModelA: ChildModelASerializer,
    ChildModelB: ChildModelBSerializer
    ...
}

Stacktrace when attempting to access any ParentModel or ChildModel resource using DRF:

Stacktrace
Internal Server Error: /api/v1/parentmodel/33fe48b6-eb67-40e0-8910-cafce5b61ea5/
Traceback (most recent call last):
  File "/home/dev/Devel/project/lib/python3.9/site-packages/django/core/handlers/exception.py", line 47, in inner
    response = get_response(request)
  File "/home/dev/Devel/project/lib/python3.9/site-packages/django/core/handlers/base.py", line 181, in _get_response
    response = wrapped_callback(request, *callback_args, **callback_kwargs)
  File "/home/dev/Devel/project/lib/python3.9/site-packages/django/views/decorators/csrf.py", line 54, in wrapped_view
    return view_func(*args, **kwargs)
  File "/home/dev/Devel/project/lib/python3.9/site-packages/django/views/generic/base.py", line 70, in view
    return self.dispatch(request, *args, **kwargs)
  File "/home/dev/Devel/project/lib/python3.9/site-packages/rest_framework/views.py", line 509, in dispatch
    response = self.handle_exception(exc)
  File "/home/dev/Devel/project/lib/python3.9/site-packages/rest_framework/views.py", line 469, in handle_exception
    self.raise_uncaught_exception(exc)
  File "/home/dev/Devel/project/lib/python3.9/site-packages/rest_framework/views.py", line 480, in raise_uncaught_exception
    raise exc
  File "/home/dev/Devel/project/lib/python3.9/site-packages/rest_framework/views.py", line 506, in dispatch
    response = handler(request, *args, **kwargs)
  File "/home/dev/Devel/project/lib/python3.9/site-packages/rest_framework/generics.py", line 208, in get
    return self.retrieve(request, *args, **kwargs)
  File "/home/dev/Devel/project/lib/python3.9/site-packages/rest_framework/mixins.py", line 55, in retrieve
    serializer = self.get_serializer(instance)
  File "/home/dev/Devel/project/lib/python3.9/site-packages/rest_framework/generics.py", line 110, in get_serializer
    return serializer_class(*args, **kwargs)
  File "/home/dev/Devel/project/lib/python3.9/site-packages/rest_polymorphic/serializers.py", line 40, in __init__
    serializer = serializer(*args, **kwargs)
  File "/home/dev/Devel/project/lib/python3.9/site-packages/rest_polymorphic/serializers.py", line 40, in __init__
    serializer = serializer(*args, **kwargs)
  File "/home/dev/Devel/project/lib/python3.9/site-packages/rest_polymorphic/serializers.py", line 40, in __init__
    serializer = serializer(*args, **kwargs)
  [Previous line repeated 472 more times]
  File "/home/dev/Devel/project/lib/python3.9/site-packages/rest_polymorphic/serializers.py", line 22, in __new__
    if not isinstance(cls.resource_type_field_name, string_types):
RecursionError: maximum recursion depth exceeded in __instancecheck__

I came up with this workaround but I think we can all agree this looks kinda hacky...
In the serializers file:
class ParentModelSerializer(PolymorphicSerializer):
    pass

class ParentModelSerializerFieldsMixin(serializers.ModelSerializer):
    attributeA = serializers.CharField()
    attributeB = serializers.IntField()

    class Meta:
        model = ParentModel

        fields = [
            "attributeA",
            "attributeB",
        ]

class ChildModelASerializer(ParentModelSerializerFieldsMixin):
    attributeC = serializers.HyperlinkedRelatedField()
    attributeD = serializers.URLField()

    class Meta:
        model = ChildModelA

        fields = [
            "attributeC",
            "attributeD",
        ]

class ChildModelBSerializer(ParentModelSerializerFieldsMixin):
...

ParentModelSerializer.model_serializer_mapping = {
    ChildModelA: ChildModelASerializer,
    ChildModelB: ChildModelBSerializer
    ...
}


Continues PR #4376

Continues PR #4376

Fixes up
Adds tests

This passed CI https://dev.azure.com/numba/numba/_build/results?buildId=4447&view=results, but github is broken and not picking this up.

/AzurePipelines run


Add ability to specify runOptions in story config

[sc-205390] (Fixes #50)

specify schema for RunOptions type, and use to pass down run options ultimately to axe.run
define override of rules when both runOptions.rules and disabledRules is present
add unit tests to cover updated methods

@ahuth All tidied up 🧹 lemme know what you think

@booc0mtaco, this was published in https://github.com/chanzuckerberg/axe-storybook-testing/releases/tag/v6.2.0


Several minor issues

connection take several seconds.
result is not readable for table with many columns.

the result of raw psql is not readable too, but in psql '\x' can be configed and the display is readable
3. if my input is not valid, PRQL will exit. I think it should not exit because of a query.

And thanks for make PRQL available as a repl.  I might fix the issues 2 if add a config option is an acceptable approach.

ideally, all my input history are saved in a .sqlite or  text files.

Thanks for the report, I agree on 2 & 3 I'll open an issue for it.  1 is straight from SQLAlchemy so I doubt there is much we can do there.


Permissions/Manage

I was messing around with permissions I tried changing my password in the Management screen and it wouldn't let me so I went into Permission Management and I deleted Settings.Manage.Self I tried putting it back into Permissions and it added two of the Settings.Manage.Self.
EDIT: I went ahead and deleted another one I put it back into the Permissions box and it added two.

Thank you for submitting this bug. The issue has already been resolved and will be updated ASAP in the next version.


chore(main): release 0.1.0

:robot: I have created a release beep boop
0.1.0 (2023-12-12)
Miscellaneous Chores

release 0.1.0 (9196eab)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/christian-vdz/hassio-mqtt2prometheus-addon/releases/tag/v0.1.0 :sunflower:


Updated/Refactored README.md to make it more new-user friendly

Description
Created a few different updates to the README. Major changes include creating an overview section, addition of a short intro blurb, as well as some rewording of other sections to make them clearer/new-user friendly. Formatting was also changed slightly to make sections more easily read/understood.
Checklist
Not applicable as this is a documentation only pull request.

Not sure about the verbose twist. 🤔
Maybe I just prefer short and not overselling.


Navigation Item - Add new method to check Gate for visibility

[ ] Changes have been thoroughly tested to not break existing functionality.
[ ] New functionality has been documented or existing documentation has been updated to reflect changes.
[ ] Visual changes are explained in the PR description using a screenshot/recording of before and after.

Old:
use Filament\Navigation\NavigationItem;

NavigationItem::make('Analytics')
    ->visible(auth()->user()->can('view-analytics'))
    // or
    ->hidden(! auth()->user()->can('view-analytics'));

New:
use Filament\Navigation\NavigationItem;

NavigationItem::make('Analytics')
    ->visibleIfCan('view-analytics')
    // or
    ->hiddenIfCan('view-analytics');

Thank you, but I'm not going to merge this. I don't think the authorization logic should be defined on the navigation item, it should be defined on the page class etc, otherwise it's dangerous because then people will forget to actually authorise their pages too.

I didn't add a new delegation logic (it already exists) what I did is add a function whose purpose is a script shortcut

Yeah, but adding such a function would encourage users to do this, and they shouldnt. They should add authorization to their page and then call it from their nav item.


Move data to YAML files and keep map.jinja a template

Add Gentoo support
Add FreeBSD support

@mgomersbach thanks for this


Bridge.Htm5's RangeException file has whitespace in filename

A typo in the file name made it read as: Html5/Errors/RangeError .cs instead of Html5/Errors/RangeError.cs. Rename it.

Ops, forgot to close the issue after sending the commit. :)


What happens when you abort a dscan?

When you abort a dscan does it return the motor to its original position?
cc @lwiegart

No. Soon (next cycle) you will be able to set cleanup instructions for any exit condition (success, error, user-initiated abort).

To elaborate, it's not clear which behavior is more desirable. In most conditions, the user probably wants the motors returned. But if the scan is aborted because of a dangerous condition, the user wants the motors to stop where they are.

'abort' sounds like it should stop everything.  Crtl-c should
behave that way.
There could be a 'cancel' that just stops the current measurement and
configurably returns to it's start point or not.  And maybe a 'rewind'
that moves back to the start, which you could use after 'abort' when
you really meant 'cancel'.
And then 'wait_wait_wait__no__that_was_ok__I_just_panicked__please_continue'
(it's more clear than 'undo_cancel_or_abort' :)
On Thu, 19 Nov 2015, Eric Dill wrote:

When you abort a dscan does it return the motor to its original position?
cc @lwiegart
?
Reply to this email directly or view it on
GitHub.[AFOf40T1h7u5nG9QDtBq0_aG-VxgveNLks5pHhKTgaJpZM4GlzIm.gif]

@cowanml In the terminology of bluesky, I think you and I agree on the following:

'abort' : Stop everything where it is. Record run as 'aborted'. This is what Ctrl+C Ctrl+C does.
'stop': Return motors to their positions. Record run as 'success'. This was Ctrl+C RE.stop() does.
'pause': Stop everything where it is. Allow user to decide if they want to abort or stop. This is where the "rewinding" comes in.

Original question was answered above. More control over abort/stop/pause behavior will be developed as part of #243.


[FR]: PTP unregistered API

Is your feature request related to a problem? Please elaborate.
PTP requires a lot of manual input for management of deregistered torrents due to trumps.
I installed this not realising the api script was specific to BHD
Describe the solution you'd like
Updating the unregistered torrent options to include PTP UR API
Does your solution involve any of the following?

[ ] New config option
[ ] New command option

Describe alternatives you've considered
I had a look at the script and suspect it would be transferable to PTP API for unregistered torrents. I'm just not clever enough to make a commit myself.
Who will this benefit?
Anyone using qbittorrent via webui knows there's no simple way to filter unregistered torrents, they still appear to be seeding.
There doesn't seem to be an elegant fix currently for Radarr/Sonarr users.
Additional Information
No response

This should not be required. PTP uses standardized naming so the remove unregistered should work on PTP just fine. I haven't seen any issues of not catching unregistered torrents with PTP. BHD was an exception since they don't standardize their torrent error message making it difficult to identify unregistered torrents.


Adapt module to make it more capable of provisioning multiple clusters

The idea here is that the kubeconfig file will be named based on the cluster itself since when trying to provision multiple clusters in the same TF setup I anticipate you would experience clashes between the various kubeconfig files with the original implementation.
This includes a few related changes:

Replace kubeconfig output with kubeconfig_env (current behaviour) and kubeconfig_file (basically the same as previous but without the 'export KUBECONFIG=' stuff.)

Added variable for config_output_path (in-line with what the AWS module uses) and defaulted that to generated/ (in-line with your current implementation.)

Replaced all hard-coded references to kubeconfig with the new dynamic filenaming strategy.

Adds output value of the API endpoint (incl. HTTPS)

These changes combined should allow k8s clusters to be easily provisioned and then instantly used within a single TF deployment.

Discarding this PR in favour of the other.


OutOfMemory exception when using it for about 6 hours

I have observed high CPU (25% on my 8-core CPU) and Memory usage when I use live-server with my simple angular2 application. Very often live-server struggles to server html pages using around 25% on my 8-core CPU and I need to wait for more than 10 seconds to refresh the page. I think this happens only when I have used live-server for about 5-6 hours continuously and only when automatic refresh is initiated because of a change in one of my html files. It happens also when I change some of the .ts files after which they are processed by "tsc -w".
Today it thrown an exception:
[1] FATAL ERROR: CALL_AND_RETRY_LAST Allocation failed - process out of memory
[1]
[1] npm
[1]  ERR! Windows_NT 6.3.9600
[1] npm ERR! argv "C:\\Program Files\\nodejs\\node.exe" "C:\\Program Files\\node
js\\node_modules\\npm\\bin\\npm-cli.js" "run" "lite"
[1] npm ERR! node v5.3.0
[1] npm ERR! npm
[1]  v3.3.12
[1] npm ERR! code ELIFECYCLE
[1] npm ERR<EMAIL_ADDRESS>lite: `lite-server`
[1] npm ERR! Exit status 3
[1] npm ERR!
[1] npm ERR! Failed at the<EMAIL_ADDRESS>lite script 'lite-server'.
[1] npm ERR! Make sure you have the latest version of node.js and npm installed.

[1] npm ERR! If you do, this is most likely a problem with the ccm2-site package
,
[1] npm ERR! not with npm itself.
[1] npm ERR! Tell the author that this fails on your system:
[1] npm ERR!     lite-server
[1] npm ERR!
[1]  You can get their info via:
[1] npm ERR!     npm owner ls ccm2-site
[1] npm ERR! There is likely additional logging output above.
[1]
[1] npm ERR! Please include the following file with any support request:
[1] npm ERR!     D:\Projects\ccm2-site\npm-debug.log
[1] npm run lite exited with code 1
^CTerminate batch job (Y/N)? y

The above log is preceded by a lot of fast file servings for about or below 5ms.
A sample that shows how big (response ?) times are after I have changed one of my html files - usually serving these files takes less than 5ms but from the log file it is visible, that after the file change detection, service of really small (.css) files takes 5 seconds:
[1] 15.12.30 10:57:56 200 GET /app/configuration/language-and-font/language-and-
font.html (Unknown - 1ms)
[1] [BS] File changed: app\configuration\prices\prices.html
[1] [BS] File changed: app\configuration\prices\prices.html
[1] 15.12.30 11:41:02 200 GET /./index.html (Unknown - 852ms)
[1] 15.12.30 11:41:08 200 GET /assets/css/reset.css (Unknown - 4816ms)
[1] 15.12.30 11:41:08 200 GET /assets/css/style.css (Unknown - 4816ms)
[1] 15.12.30 11:41:08 200 GET /node_modules/systemjs/dist/system.js (Unknown - 4
816ms)
[1] 15.12.30 11:41:08 200 GET /node_modules/es6-shim/es6-shim.min.js (Unknown -
4817ms)
[1] 15.12.30 11:41:08 200 GET /node_modules/angular2/bundles/angular2-polyfills.
min.js (Unknown - 4818ms)
[1] 15.12.30 11:41:08 200 GET /node_modules/rxjs/bundles/Rx.min.js (Unknown - 48
22ms)
[1] 15.12.30 11:41:08 200 GET /node_modules/angular2/bundles/router.min.js (Unkn
own - 14ms)

My package.json scripts section is:
    "scripts": {
        "tsc": "tsc",
        "tsc:w": "tsc -w",
        "lite": "lite-server",
        "start": "concurrent \"npm run tsc:w\" \"npm run lite\" "
    },

And I'm starting everything with npm run start
My configuration is Chrome 47, Node 5.3.0.

i have not run it for 5 hours so i cant tell you what to expect for that long. but i think resetting is pretty simple (cancel and restart).
i generally leave it running til i add new files, because lite-server and most file watchers are not good at picking up new files or folders. so i cancel and restart it.

I walked away from my box last friday and without even using it over the weekend I come in to the "out of memory" error and so far today (after 3 hours) I've been unable to get it to run successfully again. I too have a simple 1 page angular2 app with 2 components.


Failed on Run

python3 cloudmapper.py
Traceback (most recent call last):
File "/root/cloudmapper/cloudmapper.py", line 72, in
main()
File "/root/cloudmapper/cloudmapper.py", line 55, in main
module = importlib.import_module(full_package_name)
File "/usr/lib/python3.10/importlib/init.py", line 126, in import_module
return _bootstrap._gcd_import(name[level:], package, level)
File "", line 1050, in _gcd_import
File "", line 1027, in _find_and_load
File "", line 1006, in _find_and_load_unlocked
File "", line 688, in _load_unlocked
File "", line 883, in exec_module
File "", line 241, in _call_with_frames_removed
File "/root/cloudmapper/commands/amis.py", line 5, in
import pyjq
ModuleNotFoundError: No module named 'pyjq'

I am using it on latest kali linux Version

same here


port snark profiler fix to comp

port https://github.com/MinaProtocol/mina/pull/16165 to compatible

!ci-build-me

!ci-build-me

since we merged release/3.0.2 to master we don't need this porting branch


Exporter/Trace/OcAgent: Add integration test.

Updates https://github.com/census-instrumentation/opencensus-java/issues/1408.
As a follow-up of https://github.com/census-instrumentation/opencensus-java/pull/1773.

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@e24dd5e). Click here to learn what that means.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master    #1776   +/-   ##
=========================================
  Coverage          ?   82.45%
  Complexity        ?     1993
=========================================
  Files             ?      291
  Lines             ?     9221
  Branches          ?      891
=========================================
  Hits              ?     7603
  Misses            ?     1320
  Partials          ?      298

Impacted Files
Coverage Δ
Complexity Δ

...ter/trace/ocagent/OcAgentTraceExporterHandler.java
59.57% <ø> (ø)
7 <0> (?)

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 e24dd5e...4605a7b. Read the comment docs.

Build is fixed, PTAL.

Adding @rghetia for owner approval.

LGTM


Inline macro attribute parsing changes after first document conversion

There appears to be a problem with the parsing of an inline macro's attributes. Consider an inline macro that's used like this:
example:alpha.bravo[format=test]

I expect the InlineMacroProcessor implementation to be called with a map containing format -> test. This is the case the first time convert or convertFile is called. When a subsequent conversion is performed the behaviour of the parsing changes and the map then contains text -> format=test.
The problem is illustrated by this test:
package com.example;

import static org.assertj.core.api.Assertions.assertThat;

import java.util.Collections;
import java.util.HashMap;
import java.util.Map;

import org.asciidoctor.Asciidoctor;
import org.asciidoctor.ast.ContentNode;
import org.asciidoctor.extension.InlineMacroProcessor;
import org.junit.jupiter.api.Test;

class AttributeTests {

	@Test
	void inlineMacroAttributes() {
		Asciidoctor asciidoctor = Asciidoctor.Factory.create();
		asciidoctor.javaExtensionRegistry().inlineMacro(new InlineMacroProcessor("example") {

			@Override
			public Object process(ContentNode parent, String target, Map<String, Object> attributes) {
				return createPhraseNode(parent, "quoted", attributes.toString(), attributes, new HashMap<>());
			}

		});
		assertThat(convert(asciidoctor)).contains("{format=test}");
		assertThat(convert(asciidoctor)).contains("{format=test}");
	}

	private String convert(Asciidoctor asciidoctor) {
		return asciidoctor.convert("example:alpha.bravo[format=test]", Collections.emptyMap());
	}

}

It will fail when run with AsciidoctorJ 2.3. This problem appears to be a regression as the test passes with 2.0.0. I've
attached a small project containing the above test. ./gradlew build should fail.

Thank you for the ticket!
It's a really interesting behavior, currently it looks like on the second run the extension config contains :content_model->"attributes" instead of :content_model->:attributes as in the first run.
I'll continue digging into this.
Until there is a fix it seems to work if you register the extension as a class instead of an instance:
    public static class ExampleMacro extends InlineMacroProcessor {
        @Override
        public Object process(ContentNode parent, String target, Map<String, Object> attributes) {
            return createPhraseNode(parent, "quoted", attributes.toString(), attributes, new HashMap<>());
        }
    }

    @Test
    public void inlineMacroAttributes() {
        Asciidoctor asciidoctor = Asciidoctor.Factory.create();
        asciidoctor.javaExtensionRegistry().inlineMacro("example", ExampleMacro.class);
        ...

Thanks for taking a look and for the workaround. Unfortunately,I need to pass something into the constructor of my real processor so I can't register it is a class. For now, I'm working around the problem by parsing things manually when text is present in the attributes.

I created #927 with a fix and also copied your test into it.
Would you be able to test this?

I tried to build your branch locally (with ./gradlew pTML) and it failed:
> Task :asciidoctorj:signPom FAILED

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':asciidoctorj:signPom'.
> Cannot perform signing task ':asciidoctorj:signPom' because it has no configured signatory

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

* Get more help at https://help.gradle.org

BUILD FAILED in 1m 10s
10 actionable tasks: 10 executed

You can pass the gradle property "skip.signing" https://github.com/asciidoctor/asciidoctorj/blob/e24117322049950a92daa46b9c04252fde78b653/gradle/signing.gradle#L1 to avoid that for a local build.
We do need to highlight this somewehere, it's not the first time someone reports struggling with this.

Thank you, @abelsromero. ./gradlew -Pskip.signing pTML gave me a successful build. I'll test the locally built snapshot and report back later today hopefully.

The fix looks good to me. I removed our workaround and rebuilt our documentation. The problem reoccured as expected. I then configured the Asciidoctor Gradle plugin to use AsciidoctorJ 2.4.0-SNAPSHOT from my local Maven repository. The problem then went away again. Thanks for the quick fix.

:+1: Awesome, thank you for testing this out.
I'll create a release 2.3.1 this week.

I just released 2.3.1 which should contain the fix.

Thanks very much.


TypeError: argument 'files': 'WordPieceTrainer' object cannot be converted to 'Sequence'

Hi, while trying to create new tokens from my data and add them to the tokenizer of "emilyalsentzer/Bio_ClinicalBERT" I'm getting this error message.

I'm having the same issue here.


updated layout of docker installation pages in preparation for site template docs

Purpose / why
Preparation for more docs on the site template. This is the first step to addressing https://github.com/Islandora/documentation/issues/2302
What changes were made?
Updated docker installation page layout to group isle-dc and site template under "Docker" and added more folders to keep the docs separate. Also a couple small wording changes so that prereqs and intro to isle can be shared between both.
Verification
Check that the pages still load.
Interested Parties
@Islandora/documentation
Checklist
Pull-request Reviewer
Pull-request reviewer should ensure the following:

[x] Does this PR link to related issues?
[x] Does the proposed documentation align with the Islandora Documentation Style Guide?
[x] Are the changes accurate, useful, free of typos, etc?

Person Merging
The person merging should ensure the following:

[x] Does mkdocs still build successfully? (This is indicated by TravisCI passing. To test locally, and see warnings, see How To Build Documentation.)
[ ] If pages are renamed or removed, have all internal links to those pages been fixed?
[x] If pages are added, have they been linked to or placed in the menu?
[x] Did the PR receive at least one approval from a committer, and all issues raised have been addressed?

Thanks @rosiel that has been merged now


Fix handler key in request logging

During the removal of Gin in #395 I accidentally removed the handler key from the request logs. This key turned out to be very useful for understanding request flows. This change fixes the behavior to work as it did before.

I know that we have debated it before about error logs and status codes. I have only seen other libraries log 404 status codes as errors. Do you have any example of projects that logs 404 as info level? While we could be "right" is does not help if we are the only ones being "right".

I can go check some common projects and see what they do. This PR is anyway free to ignore that aspect if you feel ready to merge.


Move markdown folder into playground/cli

I think this is already done. Markdown is now under playground -> cli

Thanks @vasudeveloper001


Now incorrect statement about package.el in README

This statement in README is no longer true in Emacs 27.1:

straight.el considers modifying the user's init-file extremely uncouth. package.el aggressively inserts a call to package-initialize into the init-file if it is not already present, whenever any package management operation is performed.

Thank you for pointing out the problem. Luckily, I can still nail it on package-selected-packages :sparkles: (unless somebody fixed that too without my noticing :)

Luckily, I can still nail it on package-selected-packages sparkles (unless somebody fixed that too without my noticing :)

That's true for any package that uses custom, including straight.el, right?
Feel free to close this if you disagree. Thanks for your time!

That's true for any package that uses custom, including straight.el, right?

No quite. While straight.el does use defcustom, there is no requirement for those variables to be set using Custom. In fact, I would actively recommend against it. The problem with package.el is that it automatically sets the variable using Custom when you install a package, which forces the init-file to be modified even if you otherwise did not use Custom at all.


Load and save models

This PR closes issue #68.
Allows one to load and save keras, sklearn and deepchem models.
The sklearn models are saved either in joblib or pickle.
Keras models are saved with the model builder and the model.h5 file.
DeepChem models are saved only by the checkpoints as there is no other way to store them.
The loading of sklearn models and Keras is made with a class method as this:
# sklearn model
rf = RandomForestClassifier()
model = SklearnModel(model=rf)

model.fit(self.binary_dataset)
model.save("random_forest.pkl")

stored_random_forest = SklearnModel.load("random_forest.pkl")

# keras model
def make_cnn_model(input_dim=None,
                   g_noise=0.05,
                   DENSE=128,
                   DROPOUT=0.5,
                   C1_K=8,
                   C1_S=32,
                   C2_K=16,
                   C2_S=32,
                   activation='relu',
                   loss='binary_crossentropy',
                   optimizer='adadelta',
                   learning_rate=0.01,
                   metrics='accuracy'):
    model = Sequential()
    # Adding a bit of GaussianNoise also works as regularization
    model.add(GaussianNoise(g_noise, input_shape=(input_dim,)))
    # First two is number of filter + kernel size
    model.add(Reshape((input_dim, 1)))
    model.add(Conv1D(C1_K, (C1_S), activation=activation, padding="same"))
    model.add(Conv1D(C2_K, (C2_S), padding="same", activation=activation))
    model.add(Flatten())
    model.add(Dropout(DROPOUT))
    model.add(Dense(DENSE, activation=activation))
    model.add(Dense(1, activation='sigmoid'))
    if optimizer == 'adadelta':
        opt = Adadelta(lr=learning_rate)
    elif optimizer == 'adam':
        opt = Adam(lr=learning_rate)
    elif optimizer == 'rsmprop':
        opt = RMSprop(lr=learning_rate)
    else:
        opt = optimizer

    model.compile(loss=loss, optimizer=opt, metrics=metrics)

    return model

model = KerasModel(model_builder=make_cnn_model,
                           epochs=2, input_dim=self.binary_dataset.X.shape[1])
model.fit(self.binary_dataset)

model.save("cnn")
loaded_model = KerasModel.load("cnn")

Unfortunately, deepchem models cannot be stored in such a way to load the models back with a classmethod.

gcn = GCNModel(n_tasks=1, graph_conv_layers=[32, 32], activation=None,
                       residual=True, batchnorm=False, predictor_hidden_feats=64,
                       dropout=0.25, predictor_dropout=0.25,
                       learning_rate=1e-3,
                       batch_size=20, mode="classification", epochs=10)

model = DeepChemModel(gcn)
model.fit(self.binary_dataset)
test_predict = model.predict(self.binary_dataset)

model.save("gcn_model")

new_gcn = GCNModel(n_tasks=1, graph_conv_layers=[32, 32], activation=None,
                           residual=True, batchnorm=False, predictor_hidden_feats=64,
                           dropout=0.25, predictor_dropout=0.25,
                           learning_rate=1e-3,
                           batch_size=20, mode="classification", epochs=10)
new_model = DeepChemModel(new_gcn)
new_model.load("gcn_model")
new_model.predict(self.binary_dataset)

Hi @jcapels, the PR seems good to me. I just made some comments. Take a look to see if you find them relevant, otherwise, you can merge the PR.

Just another quick comment... Now that I am implementing the pipeline, I noticed that the way DeepChem models are saved/loaded could be problematic for Pipeline saving/loading...
It is possible that in some way the "model builder" is also saved with the model checkpoint? And then when loading performing this part:
new_gcn = GCNModel(n_tasks=1, graph_conv_layers=[32, 32], activation=None,
                           residual=True, batchnorm=False, predictor_hidden_feats=64,
                           dropout=0.25, predictor_dropout=0.25,
                           learning_rate=1e-3,
                           batch_size=20, mode="classification", epochs=10)
new_model = DeepChemModel(new_gcn)
new_model.load("gcn_model")

automatically?

@jcorreia11 Can you please take a look at the new methods I added? I am a little insecure about the implementation as I didn't test for all DeepChem models (this would be a little intensive).

Everything seems good, you can merge the PR.


[Linux] crash upon generating debug symbols

Software version:
ILCompiler 1.0.0-alpha-28407-01
.NET Core 3.1
Ubuntu 18.04 x64 (native/VirtualBox)
Symptoms:
Segmentation fault upon generating debug symbols.
Compiling [S.P.TypeLoader]Internal.Runtime.TypeLoader.ConstrainedCallSupport+GenericConstrainedCallDesc+<>c..ctor()...
Compiling [S.P.TypeLoader]Internal.Runtime.TypeLoader.ConstrainedCallSupport+NonGenericConstrainedCallDesc+<>c..ctor()...
Compiling [S.P.TypeLoader]Internal.Runtime.TypeLoader.ConstrainedCallSupport.GetThunkThatDereferencesThisPointerAndTailCallsTarget(native int)...
Segmentation fault (core dumped)

gdb output:
Thread 1 "ilc" received signal SIGSEGV, Segmentation fault.
DwarfMemberFunctionIdTypeInfo::DumpTypes (this=<optimized out>, TypeBuilder=<optimized out>, Streamer=<optimized out>, TypeSection=<optimized out>, StrSection=<optimized out>)
    at /root/corert_3112221/bin/obj/Native/Linux.x64.Release/ObjWriter/llvmCap/LLVM-prefix/src/LLVM/tools/ObjWriter/debugInfo/dwarf/dwarfTypeBuilder.cpp:559
559     in /root/corert_3112221/bin/obj/Native/Linux.x64.Release/ObjWriter/llvmCap/LLVM-prefix/src/LLVM/tools/ObjWriter/debugInfo/dwarf/dwarfTypeBuilder.cpp
(gdb) where
#0  DwarfMemberFunctionIdTypeInfo::DumpTypes (this=<optimized out>, TypeBuilder=<optimized out>, Streamer=<optimized out>, TypeSection=<optimized out>, StrSection=<optimized out>)
    at /root/corert_3112221/bin/obj/Native/Linux.x64.Release/ObjWriter/llvmCap/LLVM-prefix/src/LLVM/tools/ObjWriter/debugInfo/dwarf/dwarfTypeBuilder.cpp:559
#1  0x00007fff5e289a76 in DwarfClassTypeInfo::DumpTypes (this=<optimized out>, TypeBuilder=<optimized out>, Streamer=<optimized out>, TypeSection=<optimized out>, StrSection=<optimized out>)
    at /root/corert_3112221/bin/obj/Native/Linux.x64.Release/ObjWriter/llvmCap/LLVM-prefix/src/LLVM/tools/ObjWriter/debugInfo/dwarf/dwarfTypeBuilder.cpp:375
#2  0x00007fff5e288c2b in DwarfInfo::Dump (this=0x83d2870, TypeBuilder=<optimized out>, Streamer=0x1a0dd30, TypeSection=0x18ffb18, StrSection=0x1901ee0)
    at /root/corert_3112221/bin/obj/Native/Linux.x64.Release/ObjWriter/llvmCap/LLVM-prefix/src/LLVM/tools/ObjWriter/debugInfo/dwarf/dwarfTypeBuilder.cpp:34
#3  0x00007fff5e289ac5 in DwarfClassTypeInfo::Dump (this=0x83d2870, TypeBuilder=0x1a0cb00, Streamer=0x1a0dd30, TypeSection=0x18ffb18, StrSection=0x1901ee0)
    at /root/corert_3112221/bin/obj/Native/Linux.x64.Release/ObjWriter/llvmCap/LLVM-prefix/src/LLVM/tools/ObjWriter/debugInfo/dwarf/dwarfTypeBuilder.cpp:384
#4  0x00007fff5e28a287 in UserDefinedDwarfTypesBuilder::EmitTypeInformation (this=<optimized out>, TypeSection=<optimized out>, StrSection=<optimized out>)
    at /root/corert_3112221/bin/obj/Native/Linux.x64.Release/ObjWriter/llvmCap/LLVM-prefix/src/LLVM/tools/ObjWriter/debugInfo/dwarf/dwarfTypeBuilder.cpp:641
#5  0x00007fff5e28fc38 in DwarfGen::Finish (this=0x1a2bf10) at /root/corert_3112221/bin/obj/Native/Linux.x64.Release/ObjWriter/llvmCap/LLVM-prefix/src/LLVM/tools/ObjWriter/debugInfo/dwarf/dwarfGen.cpp:1038

Expected behavior:
The compiler succeeds and the executable with proper debug symbols is generated.
Workaround:
Specify <DebugSymbols>false</DebugSymbols> and <DebugType>none</DebugType> in your project configuration file to avoid executing the problematic code path, e.g.:
  <PropertyGroup Condition="'$(Configuration)|$(Platform)'=='Release|AnyCPU'">
    <DebugSymbols>false</DebugSymbols>
    <DebugType>none</DebugType>
    <PlatformTarget>AnyCPU</PlatformTarget>
  </PropertyGroup>

Without DebugSymbols, DebugType works?

Any chance you can create a repro for this problem that you can share?

@josephmoresena I don't remember if I had tested it myself, but there's an open issue with MSBuild (https://github.com/Microsoft/msbuild/issues/2169), so I figure including both options just makes the workaround guaranteed in most circumstances.
@jkotas I might give it a go once I have more time to spare, but it's unlikely to happen anytime soon. My gut feeling tells me that it might have something to do with the compiler optimizing certain paths/structures away and dwarfTypeBuilder expecting them to remain unchanged.

I got that issue too. There can be found project, that generates issue.

Also, probably, [ReliabilityContract(Consistency.WillNotCorruptState, Cer.MayFail)] can cause this error too.

@DjArt I have tried your repro on Ubuntu 20.04 and it does not crash for me. What is the Linux distro that you are running this on?

@jkotas Ubuntu 20.04 on wsl1

@jkotas Also I can provide dump and other info, if you say me how to do it and what you need.

The core dumps (and debuggers in general) do not work well on WSL1 https://github.com/microsoft/WSL/issues/1262 .
Yes, sharing a core dump of the crash would help.

Omg, updating from 3.1.202 dotnet sdk to 3.1.300 fixes issue. Perhaps in the future I will meet this error.

Also I find that it's happens only in Release mode for me.

@jkotas okay, I generated dump with gdb by running gdb --args source/repos/corert/bin/Linux.x64.Debug/tools/ilc @obj/corert/netstandard2.0/linux-x64/native/libEGL.Linux.ilc.rsp.
Used ilc version: https://github.com/dotnet/corert/tree/325f31dce46e893506899c913c39be6c4b219750
gdb output before dump generation:
(gdb) r
Starting program: /mnt/c/Users/artle/source/repos/corert/bin/Linux.x64.Debug/tools/ilc @obj/corert/netstandard2.0/linux-x64/native/libEGL.Linux.ilc.rsp
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7ffffe440700 (LWP 9545)]
[New Thread 0x7ffffdbf0700 (LWP 9546)]
[New Thread 0x7ffffd3d0700 (LWP 9547)]
[New Thread 0x7ffffc6f0700 (LWP 9548)]
Warning: RD.XML processing will change before release (https://github.com/dotnet/corert/issues/5001)
[New Thread 0x7ffff89c0700 (LWP 9549)]
[New Thread 0x7ffff81b0700 (LWP 9550)]
[New Thread 0x7ffff8160700 (LWP 9551)]
[New Thread 0x7ffff7950700 (LWP 9552)]
[New Thread 0x7ffff7110700 (LWP 9553)]
[New Thread 0x7ffff6900700 (LWP 9554)]
[New Thread 0x7fff84860700 (LWP 9555)]
[New Thread 0x7fff5ffe0700 (LWP 9559)]
[New Thread 0x7fff5f7d0700 (LWP 9560)]
[New Thread 0x7fff5efc0700 (LWP 9561)]
[New Thread 0x7fff5e7b0700 (LWP 9562)]
[New Thread 0x7fff5dfa0700 (LWP 9563)]
[New Thread 0x7fff5d790700 (LWP 9564)]
[New Thread 0x7fff5cf80700 (LWP 9565)]
[New Thread 0x7fff27ff0700 (LWP 9566)]

Thread 17 "ilc" received signal SIG34, Real-time event 34.
[Switching to Thread 0x7fff5dfa0700 (LWP 9563)]
0x00007ffffe93ec10 in CorUnix::CSimpleHandleManager::GetObjectFromHandle(CorUnix::CPalThread*, void*, unsigned int*, CorUnix::IPalObject**) ()
   from /mnt/c/Users/artle/source/repos/corert/bin/Linux.x64.Debug/tools/libcoreclr.so

Dump generation output:
(gdb) gcore ilc.dump
warning: target file /proc/9538/cmdline contained unexpected null characters
warning: Memory read failed for corefile section, 1048576 bytes at 0x7fff1c037000.
warning: Memory read failed for corefile section, 1048576 bytes at 0x7fff20048000.
warning: Memory read failed for corefile section, 4096 bytes at 0x7fff277f0000.
warning: Memory read failed for corefile section, 1048576 bytes at 0x7fff280fb000.
warning: Memory read failed for corefile section, 1048576 bytes at 0x7fff2c06b000.
warning: Memory read failed for corefile section, 1048576 bytes at 0x7fff30049000.
warning: Memory read failed for corefile section, 1048576 bytes at 0x7fff34099000.
warning: Memory read failed for corefile section, 1048576 bytes at 0x7fff3807a000.
warning: Memory read failed for corefile section, 1048576 bytes at 0x7fff3c081000.
warning: Memory read failed for corefile section, 1048576 bytes at 0x7fff40021000.
warning: Memory read failed for corefile section, 1048576 bytes at 0x7fff440be000.
warning: Memory read failed for corefile section, 1048576 bytes at 0x7fff48056000.
warning: Memory read failed for corefile section, 1048576 bytes at 0x7fff4c0cb000.
warning: Memory read failed for corefile section, 1048576 bytes at 0x7fff50021000.
warning: Memory read failed for corefile section, 1048576 bytes at 0x7fff54090000.
warning: Memory read failed for corefile section, 1048576 bytes at 0x7fff580f9000.
warning: Memory read failed for corefile section, 4096 bytes at 0x7fff5c780000.
warning: Memory read failed for corefile section, 4096 bytes at 0x7fff5cf90000.
warning: Memory read failed for corefile section, 4096 bytes at 0x7fff5d7a0000.
warning: Memory read failed for corefile section, 4096 bytes at 0x7fff5dfb0000.
warning: Memory read failed for corefile section, 4096 bytes at 0x7fff5e7c0000.
warning: Memory read failed for corefile section, 4096 bytes at 0x7fff5efd0000.
warning: Memory read failed for corefile section, 4096 bytes at 0x7fff5f7e0000.
warning: Memory read failed for corefile section, 1048576 bytes at 0x7fff61c3e000.
warning: Memory read failed for corefile section, 1048576 bytes at 0x7fff70442000.
warning: Memory read failed for corefile section, 1048576 bytes at 0x7fff78021000.
warning: Memory read failed for corefile section, 1048576 bytes at 0x7fff7c021000.
warning: Memory read failed for corefile section, 1048576 bytes at 0x7fff80021000.
warning: Memory read failed for corefile section, 4096 bytes at 0x7fff84060000.
warning: Memory read failed for corefile section, 212992 bytes at 0x7fff8486c000.
warning: Memory read failed for corefile section, 8192 bytes at 0x7fff848ae000.
warning: Memory read failed for corefile section, 8192 bytes at 0x7fff848be000.
warning: Memory read failed for corefile section, 8192 bytes at 0x7fff848c2000.
warning: Memory read failed for corefile section, 20480 bytes at 0x7fff848c6000.
warning: Memory read failed for corefile section, 180224 bytes at 0x7fff848d0000.
warning: Memory read failed for corefile section, 319488 bytes at 0x7fff84902000.
warning: Memory read failed for corefile section, 20480 bytes at 0x7fff84951000.
warning: Memory read failed for corefile section, 20480 bytes at 0x7fff84957000.
warning: Memory read failed for corefile section, 12288 bytes at 0x7fff8495d000.
warning: Memory read failed for corefile section, 151552 bytes at 0x7fff84961000.
warning: Memory read failed for corefile section, 233472 bytes at 0x7fff84987000.
warning: Memory read failed for corefile section, 61440 bytes at 0x7fff849c1000.
warning: Memory read failed for corefile section, 61440 bytes at 0x7fff84bff000.
warning: Memory read failed for corefile section, 61440 bytes at 0x7fff84c39000.
warning: Memory read failed for corefile section, 61440 bytes at 0x7fff854df000.
warning: Memory read failed for corefile section, 24576 bytes at 0x7fff8551a000.
warning: Memory read failed for corefile section, 204800 bytes at 0x7fff8556e000.
warning: Memory read failed for corefile section, 61440 bytes at 0x7fff855c1000.
warning: Memory read failed for corefile section, 61440 bytes at 0x7fff855d1000.
warning: Memory read failed for corefile section, 61440 bytes at 0x7fff855ea000.
warning: Memory read failed for corefile section, 24576 bytes at 0x7fff855fa000.
warning: Memory read failed for corefile section, 61440 bytes at 0x7fff85601000.
warning: Memory read failed for corefile section, 61440 bytes at 0x7fff85631000.
warning: Memory read failed for corefile section, 61440 bytes at 0x7fff85643000.
warning: Memory read failed for corefile section, 61440 bytes at 0x7fff856ae000.
warning: Memory read failed for corefile section, 8192 bytes at 0x7fff856be000.
warning: Memory read failed for corefile section, 61440 bytes at 0x7fff856c1000.
warning: Memory read failed for corefile section, 61440 bytes at 0x7fff856d3000.
warning: Memory read failed for corefile section, 65536 bytes at 0x7fff8572f000.
warning: Memory read failed for corefile section, 28672 bytes at 0x7fff85749000.
warning: Memory read failed for corefile section, 61440 bytes at 0x7fff85761000.
warning: Memory read failed for corefile section, 61440 bytes at 0x7fff85771000.
warning: Memory read failed for corefile section, 122880 bytes at 0x7fff85782000.
warning: Memory read failed for corefile section, 61440 bytes at 0x7fff857a1000.
warning: Memory read failed for corefile section, 61440 bytes at 0x7fff857b6000.
warning: Memory read failed for corefile section, 61440 bytes at 0x7fff858c4000.
warning: Memory read failed for corefile section, 45056 bytes at 0x7fff858d5000.
warning: Memory read failed for corefile section, 4096 bytes at 0x7fff858ff000.
warning: Memory read failed for corefile section, 61440 bytes at 0x7fff85901000.
warning: Memory read failed for corefile section, 65536 bytes at 0x7fff85916000.
warning: Memory read failed for corefile section, 61440 bytes at 0x7fff859bf000.
warning: Memory read failed for corefile section, 4096 bytes at 0x7fff859df000.
warning: Memory read failed for corefile section, 61440 bytes at 0x7fff859f1000.
warning: Memory read failed for corefile section, 61440 bytes at 0x7fff85a02000.
warning: Memory read failed for corefile section, 65536 bytes at 0x7fff85a3e000.
warning: Memory read failed for corefile section, 4096 bytes at 0x7fff85a4f000.
warning: Memory read failed for corefile section, 61440 bytes at 0x7fff85a61000.
warning: Memory read failed for corefile section, 61440 bytes at 0x7fff85a71000.
warning: Memory read failed for corefile section, 122880 bytes at 0x7fff85a82000.
warning: Memory read failed for corefile section, 61440 bytes at 0x7fff85aa1000.
warning: Memory read failed for corefile section, 61440 bytes at 0x7fff85ab1000.
warning: Memory read failed for corefile section, 98304 bytes at 0x7fff85ad8000.
warning: Memory read failed for corefile section, 61440 bytes at 0x7fff85b01000.
warning: Memory read failed for corefile section, 61440 bytes at 0x7fff85b11000.
warning: Memory read failed for corefile section, 61440 bytes at 0x7fff85b24000.
warning: Memory read failed for corefile section, 49152 bytes at 0x7fff85b34000.
warning: Memory read failed for corefile section, 61440 bytes at 0x7fff85b41000.
warning: Memory read failed for corefile section, 61440 bytes at 0x7fff85b51000.
warning: Memory read failed for corefile section, 61440 bytes at 0x7fff85b69000.
warning: Memory read failed for corefile section, 28672 bytes at 0x7fff85b79000.
warning: Memory read failed for corefile section, 61440 bytes at 0x7fff85b81000.
warning: Memory read failed for corefile section, 61440 bytes at 0x7fff85b91000.
warning: Memory read failed for corefile section, 61440 bytes at 0x7fff85bb1000.
warning: Memory read failed for corefile section, 61440 bytes at 0x7fff85bc1000.
warning: Memory read failed for corefile section, 61440 bytes at 0x7fff85bd1000.
warning: Memory read failed for corefile section, 65536 bytes at 0x7fff85be3000.
warning: Memory read failed for corefile section, 61440 bytes at 0x7fff85c58000.
warning: Memory read failed for corefile section, 28672 bytes at 0x7fff85c69000.
warning: Memory read failed for corefile section, 12288 bytes at 0x7fff85c9d000.
warning: Memory read failed for corefile section, 61440 bytes at 0x7fff85ca1000.
warning: Memory read failed for corefile section, 61440 bytes at 0x7fff85cb2000.
warning: Memory read failed for corefile section, 61440 bytes at 0x7fff85cf2000.
warning: Memory read failed for corefile section, 57344 bytes at 0x7fff85d02000.
warning: Memory read failed for corefile section, 61440 bytes at 0x7fff85d21000.
warning: Memory read failed for corefile section, 61440 bytes at 0x7fff85d32000.
warning: Memory read failed for corefile section, 61440 bytes at 0x7fff85d7c000.
warning: Memory read failed for corefile section, 16384 bytes at 0x7fff85d8c000.
warning: Memory read failed for corefile section, 61440 bytes at 0x7fff85d91000.
warning: Memory read failed for corefile section, 61440 bytes at 0x7fff85da1000.
warning: Memory read failed for corefile section, 122880 bytes at 0x7fff85db2000.
warning: Memory read failed for corefile section, 61440 bytes at 0x7fff85de1000.
warning: Memory read failed for corefile section, 61440 bytes at 0x7fff85df1000.
warning: Memory read failed for corefile section, 122880 bytes at 0x7fff85e02000.
warning: Memory read failed for corefile section, 61440 bytes at 0x7fff85e31000.
warning: Memory read failed for corefile section, 61440 bytes at 0x7fff85e41000.
warning: Memory read failed for corefile section, 61440 bytes at 0x7fff85e5e000.
warning: Memory read failed for corefile section, 8192 bytes at 0x7fff85e6e000.
warning: Memory read failed for corefile section, 61440 bytes at 0x7fff85e91000.
warning: Memory read failed for corefile section, 61440 bytes at 0x7fff85ea1000.
warning: Memory read failed for corefile section, 122880 bytes at 0x7fff85eb2000.
warning: Memory read failed for corefile section, 61440 bytes at 0x7fff85ed1000.
warning: Memory read failed for corefile section, 61440 bytes at 0x7fff85ee1000.
warning: Memory read failed for corefile section, 122880 bytes at 0x7fff85ef2000.
warning: Memory read failed for corefile section, 61440 bytes at 0x7fff85f11000.
warning: Memory read failed for corefile section, 61440 bytes at 0x7fff85f21000.
warning: Memory read failed for corefile section, 122880 bytes at 0x7fff85f32000.
warning: Memory read failed for corefile section, 61440 bytes at 0x7fff85f51000.
warning: Memory read failed for corefile section, 61440 bytes at 0x7fff85f61000.
warning: Memory read failed for corefile section, 122880 bytes at 0x7fff85f72000.
warning: Memory read failed for corefile section, 61440 bytes at 0x7fff85f91000.
warning: Memory read failed for corefile section, 61440 bytes at 0x7fff85fa1000.
warning: Memory read failed for corefile section, 122880 bytes at 0x7fff85fb2000.
warning: Memory read failed for corefile section, 4096 bytes at 0x7fff85fef000.
warning: Memory read failed for corefile section, 61440 bytes at 0x7fff86001000.
warning: Memory read failed for corefile section, 61440 bytes at 0x7fff86011000.
warning: Memory read failed for corefile section, 122880 bytes at 0x7fff86022000.
warning: Memory read failed for corefile section, 61440 bytes at 0x7fff86041000.
warning: Memory read failed for corefile section, 61440 bytes at 0x7fff86053000.
warning: Memory read failed for corefile section, 61440 bytes at 0x7fff860ba000.
warning: Memory read failed for corefile section, 24576 bytes at 0x7fff860ca000.
warning: Memory read failed for corefile section, 61440 bytes at 0x7fff860d1000.
warning: Memory read failed for corefile section, 61440 bytes at 0x7fff86104000.
warning: Memory read failed for corefile section, 61440 bytes at 0x7fff86904000.
warning: Memory read failed for corefile section, 24576 bytes at 0x7fff8691a000.
warning: Memory read failed for corefile section, 4096 bytes at 0x7fff8695f000.
warning: Memory read failed for corefile section, 61440 bytes at 0x7fff86971000.
warning: Memory read failed for corefile section, 61440 bytes at 0x7fff86982000.
warning: Memory read failed for corefile section, 61440 bytes at 0x7fff869c9000.
warning: Memory read failed for corefile section, 28672 bytes at 0x7fff869d9000.
warning: Memory read failed for corefile section, 61440 bytes at 0x7fff869f1000.
warning: Memory read failed for corefile section, 61440 bytes at 0x7fff86a01000.
warning: Memory read failed for corefile section, 61440 bytes at 0x7fff86a18000.
warning: Memory read failed for corefile section, 32768 bytes at 0x7fff86a28000.
warning: Memory read failed for corefile section, 61440 bytes at 0x7fff86a31000.
warning: Memory read failed for corefile section, 61440 bytes at 0x7fff86a43000.
warning: Memory read failed for corefile section, 65536 bytes at 0x7fff86aa7000.
warning: Memory read failed for corefile section, 32768 bytes at 0x7fff86ab8000.
warning: Memory read failed for corefile section, 16384 bytes at 0x7fff86adc000.
warning: Memory read failed for corefile section, 61440 bytes at 0x7fff86af1000.
warning: Memory read failed for corefile section, 61440 bytes at 0x7fff86b01000.
warning: Memory read failed for corefile section, 61440 bytes at 0x7fff86b24000.
warning: Memory read failed for corefile section, 49152 bytes at 0x7fff86b34000.
warning: Memory read failed for corefile section, 61440 bytes at 0x7fff86b81000.
warning: Memory read failed for corefile section, 61440 bytes at 0x7fff86b92000.
warning: Memory read failed for corefile section, 61440 bytes at 0x7fff86bd1000.
warning: Memory read failed for corefile section, 61440 bytes at 0x7fff86be1000.
warning: Memory read failed for corefile section, 106496 bytes at 0x7fff86c86000.
warning: Memory read failed for corefile section, 61440 bytes at 0x7fff86d01000.
warning: Memory read failed for corefile section, 61440 bytes at 0x7fff86d11000.
warning: Memory read failed for corefile section, 61440 bytes at 0x7fff86d27000.
warning: Memory read failed for corefile section, 36864 bytes at 0x7fff86d37000.
warning: Memory read failed for corefile section, 61440 bytes at 0x7fff86d61000.
warning: Memory read failed for corefile section, 61440 bytes at 0x7fff86d71000.
warning: Memory read failed for corefile section, 122880 bytes at 0x7fff86d82000.
warning: Memory read failed for corefile section, 53248 bytes at 0x7fff86e93000.
warning: Memory read failed for corefile section, 61440 bytes at 0x7fff86ed1000.
warning: Memory read failed for corefile section, 61440 bytes at 0x7fff86ee1000.
warning: Memory read failed for corefile section, 122880 bytes at 0x7fff86ef2000.
warning: Memory read failed for corefile section, 4096 bytes at 0x7fff86f1f000.
warning: Memory read failed for corefile section, 61440 bytes at 0x7fff86f61000.
warning: Memory read failed for corefile section, 61440 bytes at 0x7fff86f71000.
warning: Memory read failed for corefile section, 122880 bytes at 0x7fff86f82000.
warning: Memory read failed for corefile section, 57344 bytes at 0x7fff86fc2000.
warning: Memory read failed for corefile section, 122880 bytes at 0x7fff87052000.
warning: Memory read failed for corefile section, 61440 bytes at 0x7fff87071000.
warning: Memory read failed for corefile section, 61440 bytes at 0x7fff87081000.
warning: Memory read failed for corefile section, 122880 bytes at 0x7fff87092000.
warning: Memory read failed for corefile section, 45056 bytes at 0x7fff870e5000.
warning: Memory read failed for corefile section, 28672 bytes at 0x7fff87109000.
warning: Memory read failed for corefile section, 1048576 bytes at 0x7fff87125000.
warning: Memory read failed for corefile section, 4096 bytes at 0x7ffff6670000.
warning: Memory read failed for corefile section, 4096 bytes at 0x7ffff66e0000.
warning: Memory read failed for corefile section, 4096 bytes at 0x7ffff66f0000.
warning: Memory read failed for corefile section, 4096 bytes at 0x7ffff6700000.
warning: Memory read failed for corefile section, 4096 bytes at 0x7ffff6720000.
warning: Memory read failed for corefile section, 4096 bytes at 0x7ffff6740000.
warning: Memory read failed for corefile section, 4096 bytes at 0x7ffff6750000.
warning: Memory read failed for corefile section, 4096 bytes at 0x7ffff6790000.
warning: Memory read failed for corefile section, 4096 bytes at 0x7ffff6870000.
warning: Memory read failed for corefile section, 4096 bytes at 0x7ffff68c0000.
warning: Memory read failed for corefile section, 4096 bytes at 0x7ffff6910000.
warning: Memory read failed for corefile section, 4096 bytes at 0x7ffff7120000.
warning: Memory read failed for corefile section, 4096 bytes at 0x7ffff7130000.
warning: Memory read failed for corefile section, 4096 bytes at 0x7ffff7140000.
warning: Memory read failed for corefile section, 4096 bytes at 0x7ffff7150000.
warning: Memory read failed for corefile section, 4096 bytes at 0x7ffff7960000.
warning: Memory read failed for corefile section, 4096 bytes at 0x7ffff8170000.
warning: Memory read failed for corefile section, 4096 bytes at 0x7ffff81c0000.
warning: Memory read failed for corefile section, 4096 bytes at 0x7ffff8ca5000.
warning: Memory read failed for corefile section, 4096 bytes at 0x7ffff9085000.
warning: Memory read failed for corefile section, 8192 bytes at 0x7ffff90c1000.
warning: Memory read failed for corefile section, 1048576 bytes at 0x7ffff90c3000.
warning: Memory read failed for corefile section, 4096 bytes at 0x7ffff9620000.
warning: Memory read failed for corefile section, 4096 bytes at 0x7ffff96b0000.
warning: Memory read failed for corefile section, 4096 bytes at 0x7ffff96c0000.
warning: Memory read failed for corefile section, 4096 bytes at 0x7ffff97fe000.
warning: Memory read failed for corefile section, 1048576 bytes at 0x7ffff97ff000.
warning: Memory read failed for corefile section, 4096 bytes at 0x7ffff9cec000.
warning: Memory read failed for corefile section, 4096 bytes at 0x7ffffb9a0000.
warning: Memory read failed for corefile section, 20480 bytes at 0x7ffffb9d2000.
warning: Memory read failed for corefile section, 1048576 bytes at 0x7ffffb9d7000.
warning: Memory read failed for corefile section, 4096 bytes at 0x7ffffbee0000.
warning: Memory read failed for corefile section, 4096 bytes at 0x7ffffbef0000.
warning: Memory read failed for corefile section, 1048576 bytes at 0x7ffffc8b9000.
warning: Memory read failed for corefile section, 4096 bytes at 0x7ffffcbc0000.
warning: Memory read failed for corefile section, 4096 bytes at 0x7ffffcbd0000.
warning: Memory read failed for corefile section, 4096 bytes at 0x7ffffd3e0000.
warning: Memory read failed for corefile section, 4096 bytes at 0x7ffffd3f0000.
warning: Memory read failed for corefile section, 106496 bytes at 0x7ffffdc07000.
warning: Memory read failed for corefile section, 4096 bytes at 0x7ffffdc30000.
warning: Memory read failed for corefile section, 4096 bytes at 0x7ffffdc40000.
warning: Memory read failed for corefile section, 4096 bytes at 0x7ffffe458000.
warning: Memory read failed for corefile section, 8192 bytes at 0x7ffffed4c000.
warning: Memory read failed for corefile section, 1048576 bytes at 0x7ffffed4e000.
warning: Memory read failed for corefile section, 8192 bytes at 0x7ffffeff7000.
warning: Memory read failed for corefile section, 1048576 bytes at 0x7ffffeff9000.
warning: Memory read failed for corefile section, 4096 bytes at 0x7fffff407000.
warning: Memory read failed for corefile section, 4096 bytes at 0x7fffff440000.
warning: Memory read failed for corefile section, 4096 bytes at 0x7fffff75f000.
Saved corefile ilc.dump

Dump file (zipped by 7z)
ilc.part1.zip
ilc.part2.zip
ilc.part3.zip
ilc.part4.zip

This crash dump is stopped on signal that the GC thread suspension uses internally. gdb stops on this signal by default unfortunately. The runtime will handle this gracefully and continue.
The best way to get the right crash dump is to run ulimit -c unlimited and then look for core file (or whatever is configured by /proc/sys/kernel/core_pattern) once the crash occurs.

Oh, then I should prepare native Linux environment. It will take some time.


Compile Error: Cannot access 'com.prolificinteractive.materialcalendarview.OnDateSelectedListener' which is a supertype of

Cannot access 'com.prolificinteractive.materialcalendarview.OnDateSelectedListener' which is a supertype of
using,
implementation "com.github.prolificinteractive:material-calendarview:2.0.1"
against
com.android.tools.build:gradle:4.1.2
Suggestions, please.

I was accessing the class that has this implementation from another module, hence the error. solved it by adding the dependency to the other module.


Userstamp not being saved with API controller

Hi,
Using an API controller that does not inherit from ApplicationController the userstamps will not get saved to database unless I add "before_action :authenticate_user_from_token!, :set_stamper trigger to the API controller.
Even with this trigger the saved model is not getting userstamped (though its associated models are) on create and none get userstamped on updates.
Any ideas?

Very odd. Now it's working.


fix: testing and relative imports fix

Stuff to do

[x] Import executor in __init__.py
[x] Use only relative imports
[x] Fix VGGish
[x] Fix AudioCLIPEncoder
[x] Add small load from config test to each executor
[x] add CI to test docker image start @cristianmtr
[ ] add default args to all Executors
[ ] test manually that using relative imports and importing only __init__.py works for jinahub://

Ok, apart from catboost problems, this is almost done. Some things I would still do:

docker_args.txt should be in tests folder
I would split the docker test from the tests.sh script, and also create another step for it in unit-tests job.


Wyujie

New features/changes since Nov 11

add new Pkg deps for testing PkgUtility
CanopyLayers

add fluspect example in docs
rename container to cache (more accurate definition)
remove iLAI from Canopy4RT and calculate it within functions
add functions to calculate remote sense products, such as EVI, NDVI, NIRv, and SIF

PlantHydraulics

add PV curve functions
add non-steady state mode flow
add capacitance functions and fields
add diurnal cycle example
rename many functions to be more general
make xylem slice number flexible (instead of a fix number 10)
add segmented PV curve
use Organ and Organism instead of HS

StomataModels

update functions to use refactored PlantHydraulics
make Wang model at whole plant level

SoilPlantAirContinuum

reorganize the tests
use new PlantHydraulics

bors r+

bors r+


Added todo list and inbox blocks for canvas

Block that takes domain and token as input and returns todo list from canvas

Completed required changes @ankush-dcoder

@nmghelani can you get rid of all the semi colons. We do not use semicolons here for clean code.


add testutils to compare changes, im provider allow to inspect changes

/cc @linki

There's a circular import between internal and plan

@linki yes, thanks. Changed to use map[string]Endpoint instead, should be pretty simple to cast plan.Changes to the map


Template builder: Create template > select template

Description
Create template builder: select template list item

Type of change
Please delete options that are not relevant

[x] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)

How Has This Been Tested?
Created boilerplate jest test for page, AXE test browser extension, cross browser testing.
Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I updated the CHANGELOG.md and added documentation if necessary
[x] I have added tests that prove my fix is effective or that my feature works
[x] I have completed manual or automated accessibility testing for my changes
[ ] New and existing unit tests pass locally with my changes
[ ] Any dependent changes have been merged and published in downstream modules

Hi @fraserclark. The PR looks good to me. The only request I had was to add the associated ticket # to the CHANGELOG.md file next to your changes, as well as a link to the associated ticket in the description section of your PR. That will help us locate this PR later, when we are looking at the ticket.


Clean failed pods

For one reason or another, pods will fail (and the scheduler will recreate these). They are not being cleaned up and this is counting against storage quotas.
Fix this.

We can't call the local kube-api from a pod with a serviceAccount. This makes sense -- the api endpoint we need to hit is really the vk8s endpoint.
We'll need to use a kubeconfig passed into a job pod.

Let's do this from the spec itself.
For Jobs we can use ttlSecondsAfterFinished. We'll need to determine the correct way to handle for deployments.

Using the following in the CronJon instead:
failedJobsHistoryLimit
successfulJobsHistoryLimit


Segfault on closing of sol::state

If I register a class with the "new_usertype" method (at any point in time) and the "sol::state" is destructed (when the application is closed) there is a segfault.
Screenshot of the error
Screenshot of stacktrace
Stacktrace in text
I believe it may be related to this:
http://stackoverflow.com/questions/7427969/under-what-conditions-can-lua-close-raise-a-segmentation-fault-error
Code Example:

#include <sol.hpp>

class ship
    {
        public:
            int bullets = 20;
            int life = 100;

            bool shoot () {
                if (bullets > 0) {
                    --bullets;
                    // successfully shot
                    return true;
                }
                // cannot shoot
                return false;
            }

            bool hurt (int by) {
                life -= by;
                // have we died?
                return life < 1;
            }

            ~ship()
            {
            }
    };

int main(int argc, char *argv[])
    sol::state lua;

    lua.new_usertype<ship>(
                "ship",
                "shoot",        &ship::shoot,
                "hurt",         &ship::hurt,
                "life",         &ship::life,
                "bullet_count", &ship::bullets
                );

    return 0;
}

I am using the latest code from the repository. (Btw awesome library I love it)

Windows is okay for all versions of Lua (including JIT), so I'm gonna assume this is only for g++/linux machines. Gonna take me a bit to get the VM set up for this...

Hmmm that's odd this is happening for me then because I'm on windows 10.

Windows, with the VC++ compiler* . You're probably using clang or g++?

Yeah, I'm using g++.

Okay, I managed to repro, finally, on MinGW with Windows. Not sure what's going on. Time to open GDB...

Heyo. I managed to get this fixed. We were double-destructoring the usertype metatable and it was screwing things up: thanks for reporting this! It should be all set once I push.

Awesome thanks for fixing this!! I love this library and was really hoping this would not be too much of a detrimental bug.


HAWQ-472. Add checks to HAWQ standby start up

We should add HAWQ standby start up check, to make sure standby master is started successfully.
Now if standby master is not initialized, then start standby will report success but not failed.
Use fast mode to stop master while remove standby master.

+1


STM32 NUCLEO-144: compiling failed

Hi,
I'm trying to compile OpenMRNLite on STM32 Nucleo-144 and the compiler is complaining that is not finding netdb.h file. I've tried to find this file, but I don't know if is another library which is providing it.
Here is the output:
In file included from C:\Users\Adrian\Documents\Arduino\libraries\OpenMRNLite-0.1.1\src\freertos_drivers\esp32\Esp32WiFiManager.hxx:45,
                 from C:\Users\Adrian\Documents\Arduino\libraries\OpenMRNLite-0.1.1\src\freertos_drivers\esp32\Esp32WiFiManager.cpp:35:
C:\Users\Adrian\Documents\Arduino\libraries\OpenMRNLite-0.1.1\src/utils/SocketClient.hxx:44:10: fatal error: netdb.h: No such file or directory
   44 | #include <netdb.h>
      |          ^~~~~~~~~
compilation terminated.

exit status 1
Error compiling for board Nucleo-144.

Any ideas?

If you are compiling for the STM32 nucleo, you should probably not be
including the ESP32 wifi driver (that's for a different chip). What is the
target / example application you were trying to compile?

Hi,
I was thought about that, but I didn't add any drivers for ESP32 WiFi.
Here is the code I'm trying to compile:
#include <cmsis_os.h>
#include <croutine.h>
#include <event_groups.h>
#include <FreeRTOS.h>
#include <FreeRTOSConfig.h>
#include <FreeRTOSConfig_Default.h>
#include <list.h>
#include <mpu_prototypes.h>
#include <portmacro.h>
#include <queue.h>
#include <semphr.h>
#include <stack_macros.h>
#include <STM32FreeRTOS.h>
#include <stream_buffer.h>
#include <task.h>
#include <timers.h>

#include <LwIP.h>
#include <OpenMRNLite.h>

void setup() {
  // put your setup code here, to run once:

}

void loop() {
  // put your main code here, to run repeatedly:

}

Very basic compilation to check if the libs are ok.
Kind regards,
Adrian

Aha, it seems that we have a .cpp file which is specific to the esp32 but
it is being compiled under all targets.
add an
#ifdef ESP32
...
#endif
around the entire contents of OpenMRNLite-0.1.1\src\freertos_drivers
esp32\Esp32WiFiManager.cpp
We'll have to upstream that ifdef but this will get you going faster.

I'll add that to my open PR for the same file...

Hi,
Thanks for the fix. Is not giving anymore this error, but I'm receiving this error:
In file included from C:\Users\Adrian\Documents\Arduino\libraries\OpenMRNLite-0.1.1\src/executor/Executor.hxx:50,
                 from C:\Users\Adrian\Documents\Arduino\libraries\OpenMRNLite-0.1.1\src/openlcb/SimpleStack.hxx:40,
                 from C:\Users\Adrian\Documents\Arduino\libraries\OpenMRNLite-0.1.1\src/OpenMRNLite.h:44,
                 from C:\Users\Adrian\Nextcloud\Electronic Projects\Arduino\DCCpp+LCC\Ethernet_Test\Ethernet_Test.ino:21:
C:\Users\Adrian\Documents\Arduino\libraries\OpenMRNLite-0.1.1\src/os/OSSelectWakeup.hxx: In member function 'int OSSelectWakeup::select(int, _types_fd_set*, _types_fd_set*, _types_fd_set*, long long int)':
C:\Users\Adrian\Documents\Arduino\libraries\OpenMRNLite-0.1.1\src/os/OSSelectWakeup.hxx:231:16: error: 'ret' was not declared in this scope; did you mean 'creat'?
  231 |         return ret;
      |                ^~~
      |                creat
exit status 1
Error compiling for board Nucleo-144.

Kind regards,
Adrian


[Bug]Charts not shown with version 0.9.5

Describe the bug
I updated Microcharts and Microcharts.Forms to newest version.
The only change from previously working code when I used version 0.7.1 was changing Microcharts.Entry to Microcharts.ChartEntry.
Now when I start my app, the chart is not shown. I tried with LineChart and BarChart. Is there anything else that needs to be changed in the code?.
Which platform and version is this for?
Android 10
Screenshots
Before (0.7.1):

Now (0.9.5):

Try installing SkiaSharp, that should fix it. I thought I fixed the dependency issue but it looks like it's still an issue.

Yes, installing SkiaSharp in Android Project fixed the issue. Thank you.


adding systemd notification listener

Codecov Report

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

@@           Coverage Diff           @@
##           master      #99   +/-   ##
=======================================
  Coverage   92.52%   92.52%
=======================================
  Files         130      130
  Lines        2048     2048
  Branches      119      119
=======================================
  Hits         1895     1895
  Misses        153      153

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 d870189...5ccae1d. Read the comment docs.


Sped up portions are silent

To test this I used -x 1 which should produce the same output as was the input. But that is not the case.
Portions marked as silent were silent, but at normal speed, only the loud portions were actually present in the sound.

https://github.com/emkademy/jumpcutter/blob/92f1894e6f4c6ef0490d04192efe73d854fbc55f/jumpcutter/clip.py#L62
with audio:
--- a/jumpcutter/clip.py
+++ b/jumpcutter/clip.py
@@ -59,7 +59,7 @@ def jumpcut_silent_parts(
                 silence_clip = self.clip.subclip(start, stop)
                 silence_clip = speedx(
                     silence_clip, self.silence_part_speed
-                ).without_audio()
+                )
                 jumpcutted_clips.append(silence_clip)

             previous_stop = stop

if sped up, there is no pitch correction, so the fast portions sound like chipmunks.


Create my college

@Chrestkoo lib/domains/saitostudent/edu/my: this request has an incorrect file path format, please ensure that you are familiar with     this repository rules located at the bottom of this page and change     your request accordingly. If you don't know how to change request, close it and open a new one.     If you are not able to make the pull request according the instructions, please send us an email to<EMAIL_ADDRESS>Please mention this request URL in the message.

@Chrestkoo Thank you for your patience while waiting for a review and processing your request. Pull request merged.
Please start requesting the licenses in about an hour, to let the changes to propagate through our system.


Add support for secure compilation flags on aarch64 (specific) and generic

Hi,
I would like to have those secure flags by default on the main repo because they improve the security of the binary procuded by the compilation process.
This pull request only gives support to ROP protection with the -mbranch-protection flag on aarch64, but specifying -fcf-protection can enable it for x86_64.
I don't know how to make a platform dependant compilation flags switching, but maybe you encounter this pull request interesting and know how to do it well.
Best regards.

@looptc Thanks for the PR, I approached the same based on your suggestions in https://github.com/keshavbhatt/whatsie/commit/4720ffebebcb7e81c7f6e4f193a5732e5bee73ca
let me know if it is enough.

Looks awesome! Thank you.


Current HTTP implementation problem?

I am wondering what is meant by:

This implementation of HTTP, while far from complete...

I've used this implementation to base my RESTful API, and I'm wondering if there are any pitfalls that will come up eventually? The performance is great, and I don't see any downsides atm.

This library will never be production ready, it is a proof of concept :) In fact, I would highly recommend not shipping anything with this :) Instead, we are working to get hyper on Tokio. You can see the hyper master branch for this work.


dbt-meshify operation create-group sets model's access to public, should it instead be protected?

Describe the bug

When I run dbt-meshify operation create-group to create a new group...

all models that are only referenced by other models in their same group will have access: private
all other models (those that are referenced by models outside their group or are leaf nodes) will have access: public

Is this correct? We're assuming, then, that this person has plans to split apart their project. But what if that's not the case? If you're just trying to create a group, wouldn't you want...

all models that are only referenced by other models in their same group will have access: private
all models that are leaf nodes will have access: public
all other models (those that are referenced by models outside their group) will have access: protected

Same question for the dbt-meshify group command.
Steps to reproduce

run the dbt-meshify operation create-group command on a subset of your project that has leaf nodes and nodes that are referenced by models outside the group

Expected results

models in the new group that are referenced by other models outside the group, would have access protected

Actual results

models in the new group that are referenced by other models outside the group, have access public

Screenshots and log output

System information
Which database are you using dbt with?

[ ] postgres
[ ] redshift
[ ] bigquery
[x] snowflake
[ ] other (specify: ____________)

The output of dbt debug:
<output goes here>

The output of dbt --version:
<output goes here>

Additional context

Are you interested in contributing the fix?

I don't know in what command this belongs - but what about updating the access of models upstream of exposures to be public and contracted?


phenotype queries failing

preview and -dev

Do new queries fail or just those in your history?  I temporarily broke things at one point and invalid queries were being added to the history.

reran, still getting zero on preview

Ah I see what you man. If I re run from the interface rather than reloading from the history, they work

Ah I see what you man. If I re run from the interface rather than reloading from the history, they work

Sorry about that.  Is it a hassle to re-run them and delete the ones from your history?

No I can do that when i need them, no problem.


Typo "a Azure Databricks"→"an Azure Databricks"

https://learn.microsoft.com/en-us/azure/databricks/data-governance/unity-catalog/get-started

#PingMSFTDocs

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

ID: 6e7dd177-0bec-3b6e-ade5-888c0c1f661a
Version Independent ID: 6e7dd177-0bec-3b6e-ade5-888c0c1f661a
Content: Set up and manage Unity Catalog - Azure Databricks
Content Source: databricks/data-governance/unity-catalog/get-started.md
Service: azure-databricks
GitHub Login: @mssaperla
Microsoft Alias: saperla

@hyoshioka0128
Thanks for your feedback! We will investigate and update as appropriate.

@hyoshioka0128
Thanks for reporting this! We have created a PR for this issue and the changes should go live soon.


feat: add CheckboxField

Summary
Type

Feature

Summarise concisely:
The following changes where made:
Migrate TextboxField from the console

Codecov Report

Merging #61 (6dc96f6) into main (f580fcc) will decrease coverage by 9.40%.
The diff coverage is 52.38%.

@@            Coverage Diff             @@
##             main      #61      +/-   ##
==========================================
- Coverage   98.82%   89.42%   -9.41%
==========================================
  Files          14       15       +1
  Lines          85      104      +19
  Branches       10       11       +1
==========================================
+ Hits           84       93       +9
- Misses          0        9       +9
- Partials        1        2       +1

Impacted Files
Coverage Δ

src/components/CheckboxField/index.tsx
47.36% <47.36%> (ø)

src/helpers/pickValidators.ts
100.00% <100.00%> (ø)

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 f580fcc...6dc96f6. Read the comment docs.

I'm sure I missed some props 😅