Store error: the application attempted to write an object with no provided id but the store already contains an id of Customer:ck73s1dqm2ue30b98uepy9is3 for this object

When updating a record, even when the update itself works, there is an alert with:
Error: Network error: Error writing result to store for query:
 {"kind":"Document","definitions":[{"kind":"OperationDefinition","operation":"query","selectionSet":{"kind":"SelectionSet","selections":[{"kind":"Field","name":{"kind":"Name","value":"products"},"alias":{"kind":"Name","value":"items"},"arguments":[{"kind":"Argument","name":{"kind":"Name","value":"where"},"value":{"kind":"Variable","name":{"kind":"Name","value":"where"}}},{"kind":"Argument","name":{"kind":"Name","value":"orderBy"},"value":{"kind":"Variable","name":{"kind":"Name","value":"orderBy"}}},{"kind":"Argument","name":{"kind":"Name","value":"skip"},"value":{"kind":"Variable","name":{"kind":"Name","value":"skip"}}},{"kind":"Argument","name":{"kind":"Name","value":"first"},"value":{"kind":"Variable","name":{"kind":"Name","value":"first"}}}],"selectionSet":{"kind":"SelectionSet","selections":[{"kind":"Field","name":{"kind":"Name","value":"id"},"arguments":[],"directives":[]},{"kind":"Field","alias":{"kind":"Name","value":"title"},"name":{"kind":"Name","value":"title"},"arguments":[{"kind":"Argument","name":{"kind":"Name","value":"locale"},"value":{"kind":"EnumValue","value":"FR"}}],"directives":[]},{"kind":"Field","alias":{"kind":"Name","value":"titleFR"},"name":{"kind":"Name","value":"title"},"arguments":[{"kind":"Argument","name":{"kind":"Name","value":"locale"},"value":{"kind":"EnumValue","value":"FR"}}],"directives":[]},{"kind":"Field","alias":{"kind":"Name","value":"titleEN"},"name":{"kind":"Name","value":"title"},"arguments":[{"kind":"Argument","name":{"kind":"Name","value":"locale"},"value":{"kind":"EnumValue","value":"EN"}}],"directives":[]},{"kind":"Field","name":{"kind":"Name","value":"price"},"arguments":[],"directives":[]},{"kind":"Field","name":{"kind":"Name","value":"customer"},"arguments":[],"directives":[],"selectionSet":{"kind":"SelectionSet","selections":[{"kind":"Field","name":{"kind":"Name","value":"label"},"arguments":[],"directives":[]},{"kind":"Field","name":{"kind":"Name","value":"__typename"}}]}},{"kind":"Field","name":{"kind":"Name","value":"images"},"arguments":[],"directives":[],"selectionSet":{"kind":"SelectionSet","selections":[{"kind":"Field","name":{"kind":"Name","value":"id"},"arguments":[],"directives":[]},{"kind":"Field","name":{"kind":"Name","value":"url"},"arguments":[],"directives":[]},{"kind":"Field","name":{"kind":"Name","value":"height"},"arguments":[],"directives":[]},{"kind":"Field","name":{"kind":"Name","value":"width"},"arguments":[],"directives":[]},{"kind":"Field","name":{"kind":"Name","value":"fileName"},"arguments":[],"directives":[]},{"kind":"Field","name":{"kind":"Name","value":"__typename"}}]}},{"kind":"Field","name":{"kind":"Name","value":"__typename"}}]}},{"kind":"Field","name":{"kind":"Name","value":"productsConnection"},"alias":{"kind":"Name","value":"total"},"arguments":[{"kind":"Argument","name":{"kind":"Name","value":"where"},"value":{"kind":"Variable","name":{"kind":"Name","value":"where"}}}],"selectionSet":{"kind":"SelectionSet","selections":[{"kind":"Field","name":{"kind":"Name","value":"aggregate"},"selectionSet":{"kind":"SelectionSet","selections":[{"kind":"Field","name":{"kind":"Name","value":"count"}},{"kind":"Field","name":{"kind":"Name","value":"__typename"}}]}},{"kind":"Field","name":{"kind":"Name","value":"__typename"}}]}}]},"name":{"kind":"Name","value":"products"},"variableDefinitions":[{"kind":"VariableDefinition","variable":{"kind":"Variable","name":{"kind":"Name","value":"where"}},"type":{"kind":"NamedType","name":{"kind":"Name","value":"ProductWhereInput"}}},{"kind":"VariableDefinition","variable":{"kind":"Variable","name":{"kind":"Name","value":"orderBy"}},"type":{"kind":"NamedType","name":{"kind":"Name","value":"ProductOrderByInput"}}},{"kind":"VariableDefinition","variable":{"kind":"Variable","name":{"kind":"Name","value":"skip"}},"type":{"kind":"NamedType","name":{"kind":"Name","value":"Int"}}},{"kind":"VariableDefinition","variable":{"kind":"Variable","name":{"kind":"Name","value":"first"}},"type":{"kind":"NamedType","name":{"kind":"Name","value":"Int"}}}]}]}
Store error: the application attempted to write an object with no provided id but the store already contains an id of Customer:ck73s1dqm2ue30b98uepy9is3 for this object. The selectionSet that was trying to be written is:
{"kind":"Field","name":{"kind":"Name","value":"customer"},"arguments":[],"directives":[],"selectionSet":{"kind":"SelectionSet","selections":[{"kind":"Field","name":{"kind":"Name","value":"label"},"arguments":[],"directives":[]},{"kind":"Field","name":{"kind":"Name","value":"__typename"}}]}}
    at new ApolloError (bundle.esm.js:63)

I do not understand where this comes from.
Full stack trace:
at new ApolloError (bundle.esm.js:63)
    at bundle.esm.js:1247
    at bundle.esm.js:1559
    at Set.forEach (<anonymous>)
    at bundle.esm.js:1557
    at Map.forEach (<anonymous>)
    at QueryManager.push../node_modules/apollo-client/bundle.esm.js.QueryManager.broadcastQueries (bundle.esm.js:1555)
    at bundle.esm.js:1161

This error has disappeared, I don't know how. I believe it was related to i18n fields and got fixed by https://github.com/marcantoine/ra-data-graphql-prisma/pull/12 but I'm not sure.


Xcode project is not building

due to invalid reference to ULDeadlockDetector*

Thanks! I've just pushed an update.


Real Press Arrow keys not working on Mac

Confirmed by a coworker. Using the latest version of cypress-real-events and cypress, Using Real Press with the arrow keys down not function properly in a Mac environment.

I've been using arrow keys just a day ago :)
cy.realPress("ArrowDown") works perfectly. Please provide a reproduction.

@dmtrKovalenko My coworker is trying to navigate through the options of a select box when it has focus. The select box opens but the selected option is not changed.

The issue is not valid without reproduction. Feel free to reopen when you will have a repro.

@noahgelman Wanted to ping you on this again. A reproduction repo is attached in my previous comment.

I am not sure it is possible to fix.


We do not really need the formatted error message that deep in the API or do we ?

superseeded by https://github.com/arangodb/arangodb/pull/7339


Mechanism to Convey Zone and Region Information in a Common and Consistent

Original Title
Move zone and region information out of app into fluentbit. https://docs.fluentbit.io/manual/pipeline/filters/modify.
Description
The zone and region information is needed for logging in all deployed pods.  Each one has Fluentbit configured and the zone and region information needs to be made available to the Fluentbit configuration so that it may be added to the logs.
This has a few benefits

further decouples app and logger. only fluentbit has to know where the cluster is located.
less chance of mismatched zone and region names. ex, capitalization issues between apps, misspellings, etc.
any app deployed to the cluster can get this location info automagically.

bartr - I like the concept, but not sure how you solve for the issue when l8r is in a different region from the app. The current implementation sends that data back in the trace headers where it gets logged by l8r.
You could modify l8r to have that info about each of the servers, but, then you lose the simplicity of just adding an endpoint to the -s command line.
I wonder if there's a way to extend the k8s config so that it has Zone and Region so we can just grab it from the config?

ACTION: Work with customer to leverage best practice

Another consideration. A cluster could span multiple zones in one region. How will this affect final implementation?


Async functions should accept and respect cancellation tokens

Skills/plugins are async functions, but they can't take a cancellation token. Not only should those functions accept a cancellation token, it should be passed down and respected through chains of functions. Apparently there is a PR that fixes this. It's a large breaking change (in a good way) which needs careful planning about how/when it's introduced.

Fixed with https://github.com/microsoft/semantic-kernel/pull/1195


Daily Job Not Perform as Expected

I created a crono job to send birthday email every day at 7:30 PM. It was supposed to run only once in one day!
 This is a mutiple Job
Crono.perform(AccountSyncJob).every 1.minutes
Crono.perform(TeacherBirthdayJob).every 1.day   #, at: '07:30'

I encountered the same problem with rake task, could you find any workaround? @shenhf

@gastongouron Try to truncate crono_jobs table before start crono.


Provide "schema" in the Sequelize constructor parameter

I am using PostgreSQL, and I would like to pass the "schema" of PostgerSQL (to put the tables in) in the Sequelize ctor options and it seems it doesn't exist.
I know there is a @table decorator on each model, but I want to define it once when I define the specific connection instead of define every time in every model declaration.
I did it in the Sequelize ctor like this:
      sequelize = new Sequelize({database: databaseConfig.database,
      username: databaseConfig.username,
      password: databaseConfig.password,
      options: {
        host: host,
        port: port,
        dialect: 'postgres',
        schema: 'SCHEMA NAME"
      }

Thanks

@aviranco Try this
new Sequelize({
  ...,
  define: {
    schema: 'SCHEMA NAME'
  }
})

@aviranco does the suggested solution work for you. Can we close this issue?

Close this issue due to no further information was given.

yes thanks

Hello,
How can I pass the schema name as a parameter to the model class, during the runtime?


fix: sepolia delegate fixes

#4318  👈
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @wraeth-eth and the rest of your teammates on  Graphite


nodejs issue at require('avalanche') after installation

it seems the type script in avalanche/src/utils/index.ts  is not compiled for nodejs to javascript file

ok solved by replacing "src" by "dist", sorry for posting on wrong github


Add support for ordering by relevance

Problem

Prisma has support for ordering full text search results by relevance, we should support it too.
https://www.prisma.io/docs/concepts/components/prisma-client/filtering-and-sorting#sort-by-relevance-postgresql
Suggested solution

Work in progress.

This is now supported by #1003


Problems with install-badge-dev-env

I know that a pull request would be more useful, but I wanted to document what I am seeing while it is still fresh.
When I try to install the badge app on a fresh system (Ubuntu 15.10) using install-badge-dev-env, I get several failures as follows:

install-badge-dev-env does not attempt to install postgresql. postgresql and postgresql-client are both needed to successful completion of the install. It is possible that postgresql-contrib is also needed, but I haven't confirmed this yet.

Since I didn't have postgresql installed, I didn't have a role for my username. install-badge-dev-env stopped with the error "FATAL: role "username" does not exist". I had to create the role as the postgres user to get past this step.

Although phantomjs is added as a requirement for MacOS systems, it was not one of the packages installed by install-badge-dev-env so during one of the latter steps, the install process errorred out because it could not find the phantomjs executable.

rake db:drop-database does not clean up the install enough for install-badge-dev-env to be re-run. Perhaps there is a command that cleans the system up enough, but I missed it. I couldn't find a way to re-run install-badge-dev-env successfully after encountering an error.

After working through these errors, I do now have a running local installation of the badge app, but it took some doing. I do plan to submit a pull request which fixes these issues, but that will come later.

@ejratl If you have proposed changes to the install script, I would love to see them. I see your points about the additional postgresql and phantomjs packages, and will look into that. Ubuntu 15.10 is only supported until July, so I will focus on making it work in Ubuntu 16.04 LTS, but try to keep it general enough for all releases.

Still not a pull request, but...
1 and 3 are solved by adding postgresql-client and phantomjs to line 134 of install-badge-dev-env
The postgresql role error actually occurs on line 275 where the script is checking whether the database is already set up.

This appears to be solved for Debian/Ubuntu, so I'm closing this issue.


"packageManager"<EMAIL_ADDRESS>is ignored

What version?
0.41.1
Which command?
No response
What happened?
I'm expecting proto to automatically update bun as the current package.json state that it needs 1.1.27, I have 1.1.26 installed.
It works fine with pnpm but not bun for some reason?
Trace logs?
No response
Operating system?
MacOS
Architecture?
arm64

@baptisteArno This field is for corepack and I don't think corepack supports bun?

Indeed! https://github.com/nodejs/corepack/issues/295 My bad :)


Week of Dec 14: Cut buildpack releases

I'd like to see Forest's 3.1 removal PRs make it into this release.


Add ability to view "right-click" options within puzzles

On the website version, you can right-click within a puzzle to show additional options (such as beam to puzzlemaker). At some point, it would be great to be able to replicate this capability within the mobile app.
Tested on 1.4.1 on iPhone 8.

My concern with this tackling this right now is we haven't thought through the UX of how this would work at all. How do we want to implement a right-click on mobile? Press and hold? (that will trigger the "copy-paste" bug at the moment) Double tap? A mobile only floating action button? And I'm not sure that we have any plans for Puzzlemaker UX on mobile.


[Request] Different Goggles of Revealing aspects shown when shifting

If possible, this would be incredibly helpful for a new feature I'm working on, where I want to show two sets of aspect data

This sounds like something you will need to write your own block overlay handler for.


Allow extensions to overwrite service port for webhook registration

How to categorize this PR?

/area networking
/kind enhancement
/priority normal
What this PR does / why we need it:
The code was implicitly assuming that service port and server port are the same. However, some extensions might want to expose their server on a different port than the one they use to expose the service.
This PR allows to specify the service port via the new --webhook-config-service-port command line parameter (optional). If it's not present, the old behaviour is preserved (i.e., the service port is defaulted to the server port).
Special notes for your reviewer:
/cc @timebertt @stoyanr
Release note:

Extension developers who want to use different ports for their provider extension webhook server and the corresponding server port can now specify the service port with the new `--webhook-config-service-port` command line flag. If it's not present the service port is defaulted to the webhook server port (i.e., old behaviour is preserved).

Extension developers that use the webhook framework with the `url` mode do now have to explicitly specify the port as part of their supplied `--webhook-config-url` flag (earlier, the webhook server port was implicitly used).

/lgtm


Build performance concerns.

I've got a small project that takes 3 seconds to compile without stylecop analyzers, adding them to the project increases compilation time to 13 seconds. It's not an issue for CI or manual(command line) build, but I definitely would not expect 400% percent longer builds in Visual Studio during development time especially taking into account that validation happens in background during file editing(incremental compilation) anyway. Is there any way to disable analyzers completely for VBCSCompiler when I build from Visual Studio?
I tried the following hack, it disables analyzers for debug builds, but the build still takes 5-6 seconds instead of expected 3.
        public static void HandleCompilationStart(CompilationStartAnalysisContext context)
        {
            if (context.Options.GetType().FullName == "Microsoft.CodeAnalysis.Diagnostics.WorkspaceAnalyzerOptions" || context.Compilation.Options.OptimizationLevel == OptimizationLevel.Release)
            {
            	// ...
            }
        }

Thoughts?

Build performance is a big concern for us.
Can you clarify what you mean by "It's not an issue for CI or manual(command line) build"? I interpreted this as "Adding StyleCop.Analyzers did not slow down CI or command line builds".
What version of StyleCop.Analyzers do you have installed?
Did you install Visual Studio 2015 Update 1 CTP, or are you running the original Visual Studio 2015 release?
Is your project and branch open source in a location where we can try out the build?

Can you clarify what you mean by "It's not an issue for CI or manual(command line) build"? I interpreted this as "Adding StyleCop.Analyzers did not slow down CI or command line builds".

It takes exact same time(so using StyleCop.Analyzers slows down it), by 'not an issue' I meant that I'm personally OK the fact that it's slower than in regular dev process, because my CI builds also do fxcop and resharper cli, so StyleCop.Analyzers is not the slowest thing in my build script :) and happen less frequently than builds from Visual  Studio during development.

What version of StyleCop.Analyzers do you have installed?

I used latest from nuget: https://www.nuget.org/packages/StyleCop.Analyzers/1.0.0-beta013

Did you install Visual Studio 2015 Update 1 CTP, or are you running the original Visual Studio 2015 release?

No I didn't, I'm running Visual Studio 2015 release. Did they optimise something in Roslyn?

Is your project and branch open source in a location where we can try out the build?

Unfortunately it's not, but the issue can be easily reproduced on StyleCop.Analyzers  code base. With StyleCop.Analyzers added it takes ~8 seconds to build StyleCop.Analyzers.csproj(with nuget related imports/targets disabled) project, and less than ~1 second without.

Hi,
Just want to chime in on this discussion - I observed the following when moving from the StyleCop.MSBuild package to StyleCop.Analyzers:

(Total) build time doubled (more or less) from 2 minutes to 4 minutes
When starting Visual Studio, there's about 33% CPU usage (it's a dual-core PC) for 1,5 minute

The increase it total build time is something I don't worry about too much - we do incremental builds most of the time and it's not too big an issue if the build on the build server takes a bit more time.
The CPU usage when starting Visual Studio is more annoying - it slows down the machine. It's also noticeable when switching branches.
That said, the couple of minutes lost here and there are easily compensated for by the fixes StyleCop.Analyzers provides :-).
It's a closed source project, unfortunately, but I'm happy to run VS or MSBuild under a profiler if it helps & you provide some guidance on what procedure you'd like me to follow.
Cheers,

From everything I can tell so far, StyleCop.Analyzers is actually remarkably efficient, consuming around 12% of the overall compilation time. Unfortunately, time spent in another part of the analyzer infrastructure appears to be responsible for the large increase in build times users are observing with StyleCop.Analyzers enabled. I filed dotnet/roslyn#6053 to expand the investigation.

With 1.0.0-beta014 installed (commit 1b3948b5f73fbd0c8d61bd9122b4fc7612f2746e), StyleCop.Analyzers builds in 27 seconds on my machine. With 1.0.0-beta015 installed, it builds in 8 seconds. For now I'm going to consider this issue resolved, but we will continue to work on minimizing the overall footprint of this set of analyzers.

Thanks @sharwell, very impressive improvement.
StyleCop.Analyzers(with analyzers | without analyzers):
Time Elapsed 00:00:01.59 | Time Elapsed 00:00:00.60
Time Elapsed 00:00:01.35 | Time Elapsed 00:00:00.57
Time Elapsed 00:00:01.39 | Time Elapsed 00:00:00.57
Time Elapsed 00:00:01.53 | Time Elapsed 00:00:00.54
Time Elapsed 00:00:01.46 | Time Elapsed 00:00:00.63
StyleCop.Analyzers.CodeFixes(with analyzers | without analyzers):
Time Elapsed 00:00:00.79 | Time Elapsed 00:00:00.40
Time Elapsed 00:00:00.80 | Time Elapsed 00:00:00.39
Time Elapsed 00:00:00.84 | Time Elapsed 00:00:00.40
Time Elapsed 00:00:00.83 | Time Elapsed 00:00:00.40
Time Elapsed 00:00:00.80 | Time Elapsed 00:00:00.43
But what do you think about having 'enable/disable' switch for StyleCopAnalyzers?

But what do you think about having 'enable/disable' switch for StyleCopAnalyzers?

I'm trying to avoid this as much as possible because it reduces the overall effectiveness of the product. I'm fairly sure it's possible to do this by creating a new project build configuration (e.g. DebugNoAnalyzers) and either not including the <Analyzer Include="..."> items in that configuration or using a different code analysis rule set which disables all the diagnostics.

I understand, it's definitely possible to implement it in a way you've described, but I think of a different scenario though: I would like to have analyzers working during editing files but not when I compile in Visual Studio. Previously I had StyleCop.Resharper running StyleCop in background during editing files and I had StyleCop.MsBuild tasks running StyleCop in cli/ci builds, so I didn't lose any time on analyzing during Visual Studio builds.
I totally understand that this feature probably should not be part of the official package/repository, but could we at least introduce a single method(base class or static) for all analyzers where I could put the following or similar logic:
            if (context.Options.GetType().FullName == "Microsoft.CodeAnalysis.Diagnostics.WorkspaceAnalyzerOptions" || context.Compilation.Options.OptimizationLevel == OptimizationLevel.Release)
            {
                // ...
            }

Currently I have to change all analyzers' HandleCompilationStart method and it obviously will give me more merge conflicts later.
Thoughts?

Cool, build times for my project dropped from 66s to 43s and 3.2 minutes to 2.6 minutes. Great improvement, thanks!

@NikGovorov Just add the following at the end of your project file:
<Target Name="DisableAnalyzersForVisualStudioBuild"
        BeforeTargets="CoreCompile"
        Condition="'$(BuildingInsideVisualStudio)' == 'True' And '$(BuildingProject)' == 'True'">
  <!--
    Disable analyzers when building a project inside Visual Studio. Note that analyzer behavior for IntelliSense
    purposes is not altered by this.
  -->
  <ItemGroup>
    <Analyzer Remove="@(Analyzer)"/>
  </ItemGroup>
</Target>

@sharwell, that's awesome! Does exactly what I need. Thanks heaps!

I tried the trick with $(BuildingInsideVisualStudio), but without the other tricks of BeforeTargets="CoreCompile" and $(BuildingProject) it didn't work. Now it works great, thanks!
This trick should be documented somewhere, I'm sure that are many people with the same need of disabling StyleCop during build from VisualStudio as @NikGovorov
BTW. it should work this way right inside Visual Studio, maybe to be implemented on some VS update, but at least there is this workaround now.

BTW. it should work this way right inside Visual Studio, maybe to be implemented on some VS update, but at least there is this workaround now.

For users who enable "warnings as errors" and users who use a rule set file to treat specific analyzer warnings as errors, which would cause building in Visual Studio to produce different results than building from the command line. This would dramatically increase the chances that developers commit code they believe works but in reality causes the automated build for their project to fail.
This issue is sufficiently important that I am quite comfortable advising people to avoid this build customization and instead focus on continually reducing the performance overhead of the StyleCop Analyzers.

blockquote {padding-left: 1ex; margin: 0px 0px 0px 0.8ex; border-left: #cccccc 1px solid;} p {margin: 0px;padding: 0px;}
I'm still sure that for users that do not set warnings as errors, such behavior would be very appreciated, be it enabled by default or not.

@whut Take a look at #1711. Let me know if you think that approach will address the needs of our audience.


Send container CPU usage spike metric

This draft PR suggests emitting a new CPU Usage Spike Metric, so that the cpu entitlement plugin of cf-cli can warn users that their app instances have spiked over their CPU entitlement over last month.
This PR is not standalone it is complemented by this draft PR

@georgethebeatle can you please add tests for this new metric. Thanks.

As mentioned in the corresponding executor PR, could you mark this as 'ready to review' please? It's no longer Draft, but I can change that status.
Thanks,
Kieron

Thanks All - pulling this into our next sprint.


Fix xcode9.3 -Wunused-lambda-capture errors

Disable the warning on 3rdparty files
${glslang_dir}/hlsl/hlslParseHelper.cpp
Disable the warning on files where fixing it would cause a non-OSX compile error
os/os_specific.cpp

Description

Merged manually, thanks!


Generalized Linear Models	- Poisson Regression

@jmanitz and me would like to take over the R part.


feat: integrate exchange contracts

close #322

Need to fix contract_deploy.py

https://github.com/BoostryJP/ibet-SmartContract/blob/a8b7f0b413e77f30d18618f80ebadf76b8e46040/contracts/IbetExchange.sol#L529
https://github.com/BoostryJP/ibet-SmartContract/blob/dev-21.9.0/contracts/IbetCouponExchange.sol#L528
Previously IbetCouponExchange did not have this process, is it as expected?(Bug from before version?)

https://github.com/BoostryJP/ibet-SmartContract/blob/a8b7f0b413e77f30d18618f80ebadf76b8e46040/contracts/IbetExchange.sol#L529
https://github.com/BoostryJP/ibet-SmartContract/blob/dev-21.9.0/contracts/IbetCouponExchange.sol#L528
Previously IbetCouponExchange did not have this process, is it as expected?(Bug from before version?)

I do not think this check is necessary. It has been removed.
As for IbetCouponExchange, I had removed it in the last modification, but it had caused a degrade.


Updated to clarify the instructions about how to start the app

Documentation it's unclear about how to run the app (Copy over your app), I also have uploaded a sample app on Github with some instructions (simple TODO Api), here's the repo: https://github.com/christianhxc/dotnetcore-todoapi

Hi @christianhxc, I'm your friendly neighborhood .NET Foundation Pull Request Bot (You can call me DNFBOT). Thanks for your contribution!

This seems like a small (but important) contribution, so no Contribution License Agreement is required at this point. Real humans will now evaluate your PR.

TTYL, DNFBOT;

I will also include some instructions on how to clean up everything to remove the source code from the server.

Using dotnet restore and dotnet run from source is how you would typically run your app during development, but for deployment to a production server the recommendation is to run dotnet publish, which will collect all of the runtime artifacts needed by your app into a single folder. This folder can then be copied to the production server.

@danroth27 thanks for the clarification, I did tried that but couldn't figure out how to start the app, I tried to do it with dotnet run but I was getting an error, might be because I was not in the correct folder. Could you clarify that part or give me a link for reference? Thanks!

It's in the opening of https://docs.microsoft.com/en-us/dotnet/articles/core/deploying/index

@GuardRex thanks! but unfortunately I still don't get how to start up the application to run in port 5000 (default). Previous version of this documentation was referring to a communication between sockets, not about starting the app as self hosted, which is better @danroth27?

I think this might be the answer to my question http://stackoverflow.com/questions/37376880/net-cli-how-to-run-app-after-publish-on-linux

I guess the only thing I was doing wrong is that instead of dotnet run I just need to do dotnet projectname.dll in the root folder of the files that the publish command generated.

To run a published app you simple run dotnet <path-to-assembly>. You can see this done in the Configuring Supervisor section:
command=bash /usr/bin/dotnet /var/aspnetcore/HelloMVC/HelloMVC.dll

why is bash there?

Not sure - maybe it isn't needed? @shirhatti ?

Oops! That's an artifact of the old document that executed a shell script. @davidfowl is right, it needn't be there.

@Rick-Anderson
@shirhatti Could you please open a doc issue with the change that we should make? Do we just need to remove "bash"? Or you could just PR the change yourself :smile:

Looks like an external contributor has already fixed this for us: https://github.com/aspnet/Docs/pull/1646


Document behavior in case of suspension by owner.

Why:
Document what I learned about GitHub App suspension by asking GitHub support (ticket #1291684).

What's being changed:

Check off the following:

[ ] I have reviewed my changes in staging (look for the latest deployment event in your pull request's timeline, then click View deployment).
[ ] For content changes, I have completed the self-review checklist.

Writer impact (This section is for GitHub staff members only):

[ ] This pull request impacts the contribution experience

[ ] I have added the 'writer impact' label
[ ] I have added a description and/or a video demo of the changes below (e.g. a "before and after video")

@TorrZeed duplicate of which PR?

@Zimmi48
Thanks so much for opening a PR! I got this triaged for a writer's review :zap:

Looks better now. Thanks @ramyaparimi!


The mod ID included in your request could not be found (cache update).

While trying to update my cache, I get this error. The mod.io page is still up, so I know it's not that it was removed.
Code: 403
error_ref: 15024

Can you provide a bit more information? What's the mod.io URL? Has the author made the mod hidden or have they renamed the mod?

I'm going to close this because there are no further information provided. If you have any more information that you can provide, such as your mod list, then feel free to reopen this issue.
If you are still having this problem, try deleting the cache directory at %AppData%\Local\drg-mod-integration\cache.


Missing struct fields when using CGO on macOS

When importing MIT Kerberos krb5.h on macOS some struct fields are not defined, while on Linux the same header causes the structs to have these fields as expected. This behavior can be replicated by trying to use github.com/zephyr-im/krb5-go library on macOS Catalina 10.15 (19A603).
What version of Go are you using (go version)?

$ go version
go version go1.13.4 darwin/amd64

Does this issue reproduce with the latest release?
Yes
What operating system and processor architecture are you using (go env)?
go env Output
$ go env
GO111MODULE=""
GOARCH="amd64"
GOBIN=""
GOCACHE="/Users/pedro/Library/Caches/go-build"
GOENV="/Users/pedro/Library/Application Support/go/env"
GOEXE=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="darwin"
GONOPROXY=""
GONOSUMDB=""
GOOS="darwin"
GOPATH="/Users/pedro/go"
GOPRIVATE=""
GOPROXY="https://proxy.golang.org,direct"
GOROOT="/usr/local/Cellar/go/1.13.4/libexec"
GOSUMDB="sum.golang.org"
GOTMPDIR=""
GOTOOLDIR="/usr/local/Cellar/go/1.13.4/libexec/pkg/tool/darwin_amd64"
GCCGO="gccgo"
AR="ar"
CC="clang"
CXX="clang++"
CGO_ENABLED="1"
GOMOD=""
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/h8/24ggm1b922xdhz91lg7krpqh0000gn/T/go-build346701707=/tmp/go-build -gno-record-gcc-switches -fno-common"

What did you do?
go test github.com/zephyr-im/krb5-go

What did you expect to see?
# github.com/zephyr-im/krb5-go
../go/src/github.com/zephyr-im/krb5-go/krb5.go:241:58: princ.data undefined (type _Ctype_krb5_principal has no field or method data)
../go/src/github.com/zephyr-im/krb5-go/krb5.go:248:33: princ.realm undefined (type _Ctype_krb5_principal has no field or method realm)
../go/src/github.com/zephyr-im/krb5-go/krb5.go:269:3: unknown field 'realm' in struct literal of type _Ctype_struct_krb5_principal_data
../go/src/github.com/zephyr-im/krb5-go/krb5.go:270:3: unknown field 'data' in struct literal of type _Ctype_struct_krb5_principal_data
../go/src/github.com/zephyr-im/krb5-go/krb5.go:276:17: p.realm undefined (type *_Ctype_struct_krb5_principal_data has no field or method realm)
../go/src/github.com/zephyr-im/krb5-go/krb5.go:277:54: p.data undefined (type *_Ctype_struct_krb5_principal_data has no field or method data)
../go/src/github.com/zephyr-im/krb5-go/krb5.go:332:43: cksum.contents undefined (type *_Ctype_struct__krb5_checksum has no field or method contents)
../go/src/github.com/zephyr-im/krb5-go/krb5.go:339:3: unknown field 'contents' in struct literal of type _Ctype_struct__krb5_checksum
../go/src/github.com/zephyr-im/krb5-go/krb5.go:352:39: k.contents undefined (type *_Ctype_struct__krb5_keyblock has no field or method contents)
../go/src/github.com/zephyr-im/krb5-go/krb5.go:359:3: unknown field 'contents' in struct literal of type _Ctype_struct__krb5_keyblock
../go/src/github.com/zephyr-im/krb5-go/krb5.go:359:3: too many errors
FAIL	github.com/zephyr-im/krb5-go [build failed]
FAIL

What did you see instead?
ok  	github.com/zephyr-im/krb5-go	0.009s

The problem actually was that the structs were packed on macOS.
#if defined(TARGET_OS_MAC) && TARGET_OS_MAC
#    pragma pack(push,2)
#endif

…

#if defined(TARGET_OS_MAC) && TARGET_OS_MAC
#    pragma pack(pop)
#endif

https://github.com/golang/go/wiki/cgo#struct-alignment-issues


Get all return TypeError: Cannot read property 'getAll' of undefined

this mys script
import {
PermissionsAndroid
} from "react-native";
import MusicFiles from "react-native-get-music-files";
async componentDidMount() {
try {
const granted = await PermissionsAndroid.request(
PermissionsAndroid.PERMISSIONS.READ_EXTERNAL_STORAGE,
{
title: "Listen Music App Storage Permission",
message:
"Listen Music App needs access to your storage " +
"so you can listen music.",
buttonNeutral: "Ask Me Later",
buttonNegative: "Cancel",
buttonPositive: "OK"
}
);
if (granted === PermissionsAndroid.RESULTS.GRANTED) {
console.log("You can use the camera");
} else {
console.log("Camera permission denied");
}
} catch (err) {
console.warn(err);
}
}
_getSongs = () => {
MusicFiles.getAll({
blured: true, // works only when 'cover' is set to true
artist: true,
duration: true, //default : true
cover: false, //default : true,
genre: true,
title: true,
cover: true,
minimumSongDuration: 10000, // get songs bigger than 10000 miliseconds duration,
fields: ["title", "albumTitle", "genre", "lyrics", "artwork", "duration"] // for iOs Version
})
.then(tracks => {
console.log(tracks);
})
.catch(error => {
console.log(error);
});
};
can someone help me ?

Getting the exact same error.

@M1n007 did you checked that ´react-native-get-music-files´ is linked correctly into Android build graddle? BTW this packaged does not work with EXPO

I only use automatic link, maybe I should try the manual link.
Pada tanggal Min, 17 Mar 2019 09.03, Dante Cervantes <
<EMAIL_ADDRESS>menulis:

@M1n007 https://github.com/M1n007 did you checked that
´react-native-get-music-files´ is linked correctly into Android build
graddle? BTW this packaged does not work with EXPO
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/cinder92/react-native-get-music-files/issues/42#issuecomment-473608813,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AVx0eQja1o6jXXAqeQdDzcwNz81Ltnxbks5vXaKAgaJpZM4b2OXP
.

I solved it by creating a new vanilla React Native Project and importing all my source code into that. It works but takes 10-15 seconds to fetch around 450 audio files. @cinder92 any tips to improve its performance?

@cinder92 i try to link manually but i get error result

Configure project :app
WARNING: The specified Android SDK Build Tools version (27.0.3) is ignored, as it is below the minimum supported version (28.0.3) for Android Gradle Plugin 3.3.1.
Android SDK Build Tools 28.0.3 will be used.
To suppress this warning, remove "buildToolsVersion '27.0.3'" from your build.gradle file, as each version of the Android Gradle Plugin now has a default version of the build tools.

Configure project :react-native-get-music-files
WARNING: Configuration 'compile' is obsolete and has been replaced with 'implementation' and 'api'.
It will be removed at the end of 2018. For more information see: http://d.android.com/r/tools/update-dependency-configurations.html
WARNING: The specified Android SDK Build Tools version (27.0.3) is ignored, as it is below the minimum supported version (28.0.3) for Android Gradle Plugin 3.3.1.
Android SDK Build Tools 28.0.3 will be used.
To suppress this warning, remove "buildToolsVersion '27.0.3'" from your build.gradle file, as each version of the Android Gradle Plugin now has a default version of the build tools.

Task :react-native-get-music-files:generateDebugBuildConfig FAILED

FAILURE: Build failed with an exception.

What went wrong:
java.io.IOException: Unable to delete directory F:\Projects\react-native\ListenMusic\node_modules\react-native-get-music-files\android\build\generated\source\buildConfig\debug.

Unable to delete directory F:\Projects\react-native\ListenMusic\node_modules\react-native-get-music-files\android\build\generated\source\buildConfig\debug.

@eff-society the getAll method on MusicFiles class parses all the metadata including the cover directly from the music files, did you try Pagination via batchNumber option? ie:
MusicFiles.getAll({
            id : true,
            blured : false,
            artist : true,
            duration : true,
            cover : true,,
            title : true,
            cover : true,
            batchNumber : 5, // this option
            minimumSongDuration : 10000
            fields : ['title','artwork','duration','artist','genre','lyrics','albumTitle']
        });

Also on android >=5 you can use RNAndroidAudioStore.getSongs with no arguments ( ie:
RNAndroidAudioStore.getSongs().then(res=>console.log(res)).catch(er=>console.log(er))

)
to retrieve all the songs from androids internal metadata database, this method will be faster however if some songs haven't been scanned by android or if their meta data is not supported by android scanner they wont show up correctly.
(the documentation on the RNAndroidAudioStore is missing from the readme though, ill add it asap, meanwhile you can find the example app here. )
@M1n007 can you please reproduce the issue by making a public repo so we can go through the code?

this my public repo, can you help me about new error
https://github.com/M1n007/ListenMusic

@M1n007: seems to be working as intended :

the only error this throws is related to write permissions.

@Drazail @cinder92
yes for now after I try this again it works, thanks in advance.