Cooperate with Quartz to publish on GitHub Pages

Hi, I am recently looking for methods to publish Obsidian notes to a site like GitHub Pages.
Step 1. Write a note in Obsidian, add a tag "publish: true" as a mark;
Step 2. Run a command to upload the notes (including the embedded notes or images) in step 1 to a specified folder in a Github repo;
Step 3. Github Pages updated according to the new file pushed in automatically, with the features like graph view supported.
As I know, step 3 can be done beautifully by Quartz (https://github.com/DefenderOfBasic/obsidian-quartz-template). Quartz is not a plugin of Obsidian, however, it supports Obsidian very well. It can generate a nice site with GitHub Pages from markdown notes in Obsidian. However, we need to export the published notes to a separate folder for Quartz.
Step 2 can be done with your plugin, I think. I am new to here, and trying to do this.
If you have any other methods to do the similar workflow, please let me know. Thanks a lot.
PS:
I've tried plugin "Digital Garden", which works well with vercel. While I prefer GitHub Pages. This plugin implemented Step 2 conveniently.

Even though this plugin and Quartz both aim to publish notes in websites, we have very different design (explained in a sec), so I generally don't recommend use this plugin together with Quartz.
If you really want to use Quartz, set target path in this plugin's settings to source/content, and this plugin will upload your notes into that folder in repo. It may comes with some strange behaviour, because it is not the expected way to use Quartz.
I recommend using a general-propose site generator, such as Hugo. Find a theme, and use this plugin to upload files to your hugo blog repo. There should be many tutorial on how to init a hugo project and deploy it to github pages. Maybe I'll also write a tutorial on how to use this plugin with hugo, if you are interested, let me know and I'll notify you when it is done.
Back to the design difference. The usage of Quartz is initialize a repo, and use its source/content folder as obsidian vault. This plugin has a very differnet use case: I have a large vault, but only want to make a few notes into a website. Thus this plugin picked those notes and transform them, and then any site generator (Hugo, Jekyll, Astro, etc.) can be used to generate the site and deploy it.

Thanks for your guidence! I would like to try Hugo as you mentioned.
I just found you are from 西安交大！
祝在 UC Berkeley学业有成！

Thanks!


Performance issues

Hi,
Server TPS is low (down and up spike cpu usage), entities sometimes do not move or like in slideshow and block breaking/placing event don't work. I believe it is caused by your AI mod, but i can be wrong. There is no console error while in game.
debug command results:
profile-results-2021-04-07_14.55.45.txt
What is causing TPS drop ?

I will dig into it more, easy test is to disable AI look helper in the config. If things improve that means our math is less effective on your server then the vanilla math. This can happen depending on your hardware, software, and even jvm flavor being used. I've seen results of different TPS based on which JVM is used.


Is it for React Native as well?

Hello,
Thanks a lot for the great library.
Can I use if in React Native project. If yes, can you please provide documentation or help me in the same?

Sorry, it isn't.
But if you want this circle UI, I think this article: https://tympanus.net/codrops/2013/08/09/building-a-circular-navigation-with-css-transforms/ is useful for you.

Thanks a lot for the reply


Footer styles for launch

This next push is about to break the branch but i need to access some commits.

And homepage stuff in the branch?

@misscs do you mean my PR is going to break things? How?


Closes #46 - Move should_DeleteOldWorkbasketCleanupJobs_When_InitializingSchedule to AbstractKadaiJobAccTest.java

Closes #46 - Move should_DeleteOldWorkbasketCleanupJobs_When_InitializingSchedule to AbstractKadaiJobAccTest.java

Thanks for your PR! Please fill out the following list :)

[ ] I put the ticket or multiple tickets in review
[x] Commit message format → Closes #<Issue Number> - Your commit message.
[x] Sonarcloud link : https://sonarcloud.io/summary/new_code?id=jannikFuellgrafEnvite_kadai&branch=kadai%2F46
[x] No documentation update needed
[ ] Link to PR with documentation update: <add the link here>
[x] No Release Notes needed
[ ] Release Notes :

What about this comment?
// Dirty Hack, please refactor me with ticket #46

James told me to ignore it and just refactor the test function


config.json should be encrypted

The config.json file contains a private key in the "wallet" field in cleartext. At a minimum, the user should be given the option of encrypting the file.

Yes I agree, that is why I added this issue already. See https://github.com/Storj/dataserv-client/issues/59


Category Pages - content holes

Better Indiv Production, Crosscutting Category pages need deck, into paragraph and a link to all category resources

This is all done! These are old issues and can be closed.


Don’t try to read local git config if not git repo

Fixes https://github.com/pivotal/git_scripts/issues/16

Oops this still needs some more work...


Confusing error message when stream is expected

Summary
Wherever a stream is expected, if a Promise is passed (by mistake) instead, the message returned is very hard to understand.
Expected result
TypeError: Wrong type passed to 'most.chain' {insert func used}. Expected Stream, passed in Promise.
Actual Result
(node:41876) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 1): TypeError: Cannot read property 'run' of undefined
(node:41876) DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
Versions

most.js: 1.5.1 (all versions apply right now)

Code to reproduce
const most = require('most');
const shouldBeStream = foo => {
return most.fromPromise(Promise.resolve(foo + 'bar'));
};
most.of('foo')
.chain(shouldBeStream)
.observe(console.log);

This has already bit me twice. First time I blamed myself, the second I realized that in the midst of many code pieces this can happen more times than you think

IMO, introducing runtime checks and custom error messages is expensive. Already, most has TypeScript types defined, which statically check for such errors. In the future, Flow types will also be available. If you have such concerns about correct types, I suggest you use TS if you can.

Duplicate of #480

These runtime checks can be placed only for development versions (like react, redux and others have) via process.env.NODE_ENV

I'm not sure how I feel about this.  I understand the error coming from the VM is cryptic.
It's quite unhelpful that Node's unhandledRejection machinery appears not to be printing stack traces.  There's nothing we could do about that.  Even if we threw a descriptive error message, you'd never see the stack trace, due to node not printing it.
The only actual guarantee is a type system.  If we check (x != null && typeof x.run === 'function'), there's no guarantee it's a Most.js Stream.  Even instanceof isn't really a guarantee.  The TS defs will prevent this code from ever running, and soon we'll have Flow defs (thanks to @TrySound) as well.
I'm open to finding a simple way to help as long as we don't have to pollute the code or take on much additional maintenance (e.g. in a build step).  On the other hand, I'm not sure how much help we can realistically provide if Node is hiding the stack trace.

We can try to introduce something like calls chain like promises do. We can use displayName property of functions. This will let at least to identify place by shape.
just.chain.map.switchLatest.tap.drain

I'm not in favor of adding that level of extra machinery.  Also, it'd have to be done in a way that works across 3rd party libraries (which may export pure functions), which I don't think is possible.
I'd rather we all ask Node to improve their unhandled rejection reporting to include a stack.
When you see an unhandled rejection, you do have options for getting a stack trace.  You can add a process unhandledRejection event handler, or you can .catch the promise returned by observe/drain/reduce.  In either case, you'll be able to log the error stack trace, which should lead you reasonably close to the source of the problem.

Wow, I tried to reproduce and seems like stack trace was improved in chrome. There's now a section in stack trace Promise resolve (async) which at least shows where observe was called. This can make debugging a bit simpler. However yes, we should force to use ts or flow to save performance.

We can make a version with runtime checks for those who don't use type systems. It will also make stack trace more transparent, because checks throw errors inside constructors instead of delegated run methods.

@TrySound

We can make a version with runtime checks for those who don't use type systems.

That’s extra maintenance.

For what it's worth, I completely agree with the reasoning above and in fact I wouldn't want to trade speed for clearer messages tbh.
This may be possibly fine in my case once Flow types are added and I might be able to use comment types.

I wonder if there is something we can do for those who dont not use TS/Flow... maybe in the form of docs or tips how to debug via the devtools?

Just as an extra data point, React provides runtime checks in the dev-only build. I do the same in my own code in some places. I use tiny-preprocessor to strip out the dev-only checks for production. Disclaimer: not a request or an opinion about what Most.js should do in this regard.


fix(stream): Fixed a problem that onAbort() is called even if request is normally closed in deno

#3042 fixed the problem in bun, but in deno, onAbort() was being called after a successful exit.
In deno, an "abort" event is fired for req.signal even if it exits successfully.
In this pull request, fix so that onAbort() is not called when stream finishes successfully.
import { Hono } from 'hono'

const app = new Hono()
app.get('/stream', (c) => {
  return stream(c, async (stream) => {
    stream.onAbort(() => {
      console.log('Aborted!')
    })
    await stream.write('Hello')
  })
})

export default app

The author should do the following, if applicable

[x] Add tests
[x] Run tests
[x] bun run format:fix && bun run lint:fix to format the code
[x] Add TSDoc/JSDoc to document the code

@usualoma Thank you for the fix and also adding the tests! Merging now.


How To Use github link is to wrong samples repo

The link at the top of the page takes you too the right D365 samples repo, the How To Use section link goes to the Power Apps samples repo, which is an entirely different one.

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

ID: fb4f2472-cbce-a328-a8dc-747ef196e15e
Version Independent ID: d046699e-cdbc-1d79-56db-a7f1e9afd32c
Content: Sample: Distribute a quick campaign (Developer Guide for Dynamics 365 Customer Engagement)
Content Source: ce/customerengagement/on-premises/developer/sample-distribute-a-quick-campaign.md
Product: d365ce-op
GitHub Login: @JimDaly
Microsoft Alias: jdaly

Thanks for your comment, @jhaas13. This issue has been assigned to the doc author for review.

@jhaas13
Thanks for reporting this.
I've applied a change that should fix this and other sample topics in this repo so that the point to the Dynamics365-Apps-Samples repo rather than the PowerApps-Samples repo.
Change should be in place by EOD.


fix(device_info_plus): Add iOS Privacy Info

Description

Add PrivacyInfo to podspec of Device Info Plus

Related Issues

Part of #2447

Checklist

[x] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[x] I titled the PR using Conventional Commits.
[x] I did not modify the CHANGELOG.md nor the plugin version in pubspec.yaml files.
[x] All existing and new tests are passing.
[x] The analyzer (flutter analyze) does not report any problems on my PR.

Breaking Change
Does your PR require plugin users to manually update their apps to accommodate your change?

[ ] Yes, this is a breaking change (please indicate that with a ! in the title as explained in Conventional Commits).
[x] No, this is not a breaking change.

Hi, @miquelbeltran could you please provide your thoughts re: if the empty PrivacyInfo.xcprivacy actually follow the Apple's guideline for API declaration? As far as I understand developers should provide NSPrivacyAccessedAPIType with NSPrivacyAccessedAPITypeReasons, not just empty plist 🤔 This question is general one as it looks like common "PR fix" across the Flutter packages and I'm just going by the list of these provided by Apple here https://developer.apple.com/support/third-party-SDK-requirements/ and device_info_plus at the top of my packages subset

Eg from WWDC video https://developer.apple.com/wwdc23/10060?time=578

As explained here, I couldn't find the use of any "Required API" by the plugin: https://github.com/fluttercommunity/plus_plugins/issues/2447#issuecomment-1934296316 that's why the privacy manifest NSPrivacyAccessedAPIType array is empty.
I am currently not developing iOS apps, so I have no way to verify this. If you are still facing issues, please fork the project, do the appropriated changes and report back, I'll be very interested to know!


fixed broken episode_callback in stable_baselines_strategy.py

the current statement eposide_callback(self._environment._exchange.performance) on line number 112 isnt working
Changed it to episode_callback(performance) since they're technically same things
also, episode_callback() returning true (as per the documentation) breaks the loop (which should be reverse) .. added a not in the if condition.

You're welcome amigo! :) I'd love to contribute more!


[Spaceship] can only delete the build not select?

Question Checklist

[x] Updated fastlane to the latest version
[x] I read the Contribution Guidelines
[x] I read docs.fastlane.tools
[x] I searched for existing GitHub issues

Question Subject
Spaceship
Question Description
Spaceship has a action that can be select build
eg:
version = app.edit_version

builds = version.candidate_builds
version.select_build(builds.first)
version.save!

now i want only to delete the selected build and not to choose other build,  what should i do？In other words, i want to clear the build. Can Spaceship  simulate the delete action from the Itunes Connect?
like this:
version = app.edit_version
version.delete_build!
version.save!

I find a solution to this problem.  I added a method called ‘delete_build!’ to 'app_version.rb' (you local  installation path eg: /usr/local/lib/ruby/gems/x.x.x/gems/fastlane/spaceship/lib/spaceship/tunes/app_version.rb)
here is the code:
      # Delete the build that you have selected to be submitted for Review.
      # Don't forget to call save! after calling this method
      def delete_build!
        raw_data.set(['preReleaseBuildVersionString', 'value'], nil)
        raw_data.set(['preReleaseBuildTrainVersionString'], nil)
        raw_data.set(['preReleaseBuildUploadDate'], nil)
      end

how to use?
like this:
       version = app.edit_version
       version.delete_build!
       version.save!


Fix bugs when execute parallel

Summary
Resolve #19
The builderHelper bypass has to be initialized for each traverse,
but the opts parameter in the builderHelper instance had to be inherited.
Test
$ yarn test
yarn run v1.19.0
$ jest
(node:15358) ExperimentalWarning: The fs.promises API is experimental
(node:15357) ExperimentalWarning: The fs.promises API is experimental
 PASS  src/__tests__/basic.test.ts
 PASS  src/__tests__/error.test.ts

Test Suites: 2 passed, 2 total
Tests:       16 passed, 16 total
Snapshots:   16 passed, 16 total
Time:        2.124 s, estimated 3 s
Ran all test suites.
✨  Done in 3.33s.

LGTM


Field comparison not ignoring static fields

Summary
Similar to #590, but this time for statics.
A static element won't ever be a field, so it shouldn't be comparing them.
Field has an isStatic() method to simplify this

Thanks for reporting this.

And I've submitted a pull request, so no one else needs to investigate it.

:+1:
pretty busy these days but I have planned it for the next release.

done.


API to disable routing

Hello @arunoda
I was thinking of a use case when the client loose the connection with the server.
In this case, like a lot of apps, i show a dimmer/absolute div to explain the problem, provide a reconnection button and a timer.
Anyway, this is not the problem. I was thinking of blocking the routing globally in my app when the client connection is lost to prevent from page reloading, or things like that.
I couldn't figure by myself a solution to achieve this with the actual implementation of flow-router. I'd like to hear you about this. Could it be a feasible feature for flow-router, or do you have any ideas about this problemtaic?
Best regards,
William

Flow Router won't have such an API. May be someone can write a package for this.


fake server in front of main server

is it possible to put a fake server in front that redirects all the traffic to main server.
I have clients that only can access this fake server IP internally but I want to bypass that and give them access to mtproto server.
If its possible please tell me how or point me to right direction.
thanks

the link is broken

Retry with VPN. (Outside of Iran)


Resource names for MM Input

In Terraform, we will also set the name back to user configuration files after "Get" operation is finished. The second /name matches one of the response item defined under 'read' section, which instructs MM to copy that value back to user state. Typically, all resources names is made of two items: ['{WhatEverPropertyName}', '/name']
    Suggested change

              azure_sdk_references: ['accountName']

                azure_sdk_references: ['accountName', '/name']

                  Commit suggestion

                Add suggestion to batch

https://github.com/VSChina/magic-modules/pull/5/files#r271983294

closing as it's done already


Add PyCSW instances

List https://catalogue.ejpsoil.eu/
Search keywords "Powered by PyCSW"

All added


Use moving average instead of overall one

Now some Prometheus-based (or all of them) average panels for histograms/summaries (metric_sum / metric_count) are computed improperly: they display the average value of something over instance lifetime instead of displaying the average value of something "now":
https://github.com/tarantool/grafana-dashboard/blob/c0dba2a9fad996f4e545e58f49b1c2dbfb66c455/tests/Prometheus/dashboard_tdg_compiled.json#L19935
It results in useless "constant" graphs for instances with large uptime.

Prometheus documentation: https://prometheus.io/docs/practices/histograms/#count-and-sum-of-observations


NgSemantic is not a module

When using any<EMAIL_ADDRESS>It does not recognize NgSemantic as a valid module.. it works for me with<EMAIL_ADDRESS>

Seems like a similar issue to https://github.com/vladotesanovic/ngSemantic/issues/144.
As soon as i can i'll try to downgrade my angularcli version and test if it works

Works for me with this on package.json :
"ng-semantic": "https://github.com/vladotesanovic/ngSemantic/tarball/master",
@vladotesanovic : I read somewhere on angular-cli issue, that lib must be compiled with angular > 2.2.* because of an incompatibility.

Failing for me as well:
  "dependencies": {
    "@angular/common": "2.3.1",
    "@angular/compiler": "2.3.1",
    "@angular/core": "2.3.1",
    "@angular/forms": "2.3.1",
    "@angular/http": "2.3.1",
    "@angular/platform-browser": "2.3.1",
    "@angular/platform-browser-dynamic": "2.3.1",
    "@angular/router": "3.3.1",
    "alertify.js": "^1.0.12",
    "angular2-jwt": "^0.1.27",
    "core-js": "^2.4.1",
    "font-awesome": "^4.7.0",
    "jquery": "^3.1.1",
    "jwt-decode": "^2.1.0",
    "moment": "^2.17.1",
    "ng-semantic": "https://github.com/vladotesanovic/ngSemantic/tarball/master",
    "primeng": "^1.1.2",
    "rxjs": "5.0.1",
    "semantic-ui": "2.2.7",
    "ts-helpers": "^1.1.1",
    "zone.js": "^0.7.2",
    "csspin": "^1.1.0"
  },
  "devDependencies": {
    "@angular/compiler": "2.3.1",
    "@angular/compiler-cli": "2.3.1",
    "@angular/core": "2.3.1",
    "@types/jasmine": "^2.5.38",
    "@types/node": "^6.0.42",
    "angular-cli": "^1.0.0-beta.24",
    "codelyzer": "~2.0.0-beta.1",
    "jasmine-core": "2.5.2",
    "jasmine-spec-reporter": "2.5.0",
    "karma": "1.2.0",
    "karma-chrome-launcher": "^2.0.0",
    "karma-cli": "^1.0.1",
    "karma-jasmine": "^1.0.2",
    "karma-remap-istanbul": "^0.2.1",
    "protractor": "4.0.9",
    "ts-node": "1.2.1",
    "tslint": "^4.0.2",
    "typescript": "~2.0.3",
    "webdriver-manager": "10.2.5"
  }

Ok, so after A LOT of wrestling, i've finally managed to solve my issues.
First, those are my dependencies:
  "dependencies": {     "@angular/common": "2.4.1",     "@angular/compiler": "2.4.1",     "@angular/core": "2.4.1",     "@angular/forms": "2.4.1",     "@angular/http": "2.4.1",     "@angular/platform-browser": "2.4.1",     "@angular/platform-browser-dynamic": "2.4.1",     "@angular/router": "3.4.1",     "class-transformer": "^0.1.3",     "core-js": "^2.4.1",     "es6-shim": "^0.35.2",     "jquery": "^3.1.1",     "ng-semantic": "https://github.com/vladotesanovic/ngSemantic/tarball/master",     "reflect-metadata": "^0.1.8",     "rxjs": "5.0.2",     "ts-helpers": "^1.1.1",     "zone.js": "^0.7.4"   },   "devDependencies": {     "@angular/compiler-cli": "2.4.1",     "@types/es6-shim": "^0.31.32",     "@types/jasmine": "2.5.38",     "@types/node": "^6.0.42",     "angular-cli": "1.0.0-beta.24",     "codelyzer": "~2.0.0-beta.1",     "jasmine-core": "2.5.2",     "jasmine-spec-reporter": "2.7.0",     "karma": "1.3.0",     "karma-chrome-launcher": "^2.0.0",     "karma-cli": "^1.0.1",     "karma-jasmine": "^1.0.2",     "karma-remap-istanbul": "^0.4.0",     "protractor": "4.0.14",     "ts-node": "1.7.3",     "tslint": "^4.0.2",     "typescript": "2.0.10",     "webdriver-manager": "11.1.0"   }
The most important things are:

The fact that typescript MUST be v.2.0.x and not 2.1.x or it will not compile saying that AppModule is not a module
The import for ng-semantic should be something like import { NgSemanticModule } from "ng-semantic/ng-semantic";
I'm using an updated version of angular and reflect-metadata (it's not required for ng-semantic), but if anyone have a similar issue, please add as first thing the import of reflect-metadata in the main.ts otherwise you'll receive an error stating something about attributes missings

Today I started new project, still getting NGSemanticModule is not an NgModule.
My dependencies -
  "dependencies": {     "@angular/common": "^2.3.1",     "@angular/compiler": "^2.3.1",     "@angular/core": "^2.3.1",     "@angular/forms": "^2.3.1",     "@angular/http": "^2.3.1",     "@angular/platform-browser": "^2.3.1",     "@angular/platform-browser-dynamic": "^2.3.1",     "@angular/router": "^3.3.1",     "core-js": "^2.4.1",     "jquery": "^3.1.1",     "ng-semantic": "^1.1.13",     "rxjs": "^5.0.1",     "ts-helpers": "^1.1.1",     "zone.js": "^0.7.2"   },   "devDependencies": {     "@angular/compiler-cli": "^2.3.1",     "@types/jasmine": "2.5.38",     "@types/node": "^6.0.42",     "angular-cli": "1.0.0-beta.24",     "codelyzer": "~2.0.0-beta.1",     "jasmine-core": "2.5.2",     "jasmine-spec-reporter": "2.5.0",     "karma": "1.2.0",     "karma-chrome-launcher": "^2.0.0",     "karma-cli": "^1.0.1",     "karma-jasmine": "^1.0.2",     "karma-remap-istanbul": "^0.2.1",     "protractor": "~4.0.13",     "ts-node": "1.2.1",     "tslint": "^4.0.2",     "typescript": "~2.0.3"   }

@ReFirnE try to use the same dependencies that i've used. In particular, update angular, ts-node  and zone.js

Thanks @gnegno84! That worked :)

I solved that only adding the @NgModule() decorator to the NgSemanticModule and works fine.

This issue appear when you use angular-cli (i'm using angular-cli version 1.0.0-beta.26) because is based in webpack, and the library was created for systemjs, i'm working to port it. Currently this branch works https://github.com/BennyFranco/ngSemantic/tree/angular-cli but I need to do some debug tasks and  create a way to maintain the compatibility with both..

I just fixed one line:
import { NgSemanticModule } from 'ng-semantic/ng-semantic';`
Even works with Angular 2.4.6.

@borisfeldmann are you working with angular-cli?

Hi @BennyFranco, yes I am using angular-cli. But I just setup a brand new project with ´ng-semantic` and got the same error again.
I could fix it by adding this to the file ng-semantic.d.ts in the ng-semantic node package:
import { NgModule } from '@angular/core';

...

@NgModule({
	declarations: [
		NgSemanticModule
	]
})
export declare class NgSemanticModule {
}

Thanks @borisfeldmann! That worked for me!!

@borisfeldmann thanks, that worked!

@borisfeldmann Great Fix!  Will this be available with the fix on NPM anytime soon?  The github shows the code in place, but when installing via npm; the code is not there.
"@angular/common": "2.4.7",     "@angular/compiler": "2.4.7",     "@angular/core": "2.4.7",     "@angular/forms": "2.4.7",     "@angular/http": "2.4.7",     "@angular/platform-browser": "2.4.7",     "@angular/platform-browser-dynamic": "2.4.7",     "@angular/router": "3.4.7",     "@ng-bootstrap/ng-bootstrap": "1.0.0-alpha.15",     "@swimlane/ngx-charts": "^4.2.0",     "@types/d3": "^4.5.0"<EMAIL_ADDRESS>"^1.4.29",     "core-js": "^2.4.1",     "d3": "^4.5.0",     "ng-semantic": "^1.1.13",     "ng2-translate": "^5.0.0",     "reflect-metadata": "^0.1.10",     "rxjs": "^5.1.0",     "socket.io-client": "^1.7.3",     "zone.js": "^0.7.6"

Still not working when doing a fresh
npm install

The only working solution is @borisfeldmann's and because of zone.js' problems, every time I add/remove a dependency, I need to run rm -rf node_modules first and update ng-semantic.d.ts all over again.

This Comment works perfectly for me thanks to @gnegno84. Just Pay attention to ts-node, typescript and ng-semantic dependencies! 👍
I still wonder why there's no latest release on NPM? 🤔
It's ok to install it from GitHub but I think it should be fixed ASAP!

@BennyFranco Could you get back your repo with the changes you've done so far?
As I used it for the project, and now it's missing and I'm getting an error.
Thank you.

This is really strange, but after
npm install ng-semantic
in file ng-semantic.d.ts i see just that:
export * from "./src/accordion/accordion";
export declare let SEMANTIC_COMPONENTS: Array<any>;
export declare let SEMANTIC_DIRECTIVES: Array<any>;
export declare class NgSemanticModule {
}

But I think should be like that:
export declare let SEMANTIC_COMPONENTS: Array<any>;
export declare let SEMANTIC_DIRECTIVES: Array<any>;

import { NgModule } from "@angular/core";
@NgModule({
	declarations: [NgSemanticModule]
})
export declare class NgSemanticModule {
}

for me, using the version 1.0.0 of @angular/cli and its dependencies, the working solution was to add the NgModule annotation on ng.semantic.d.ts file
import { NgModule } from '@angular/core';
@NgModule() export declare class NgSemanticModule { }

above solution works for me with typescript 2.2.1 and angular cli 1.0.1

Boris solution works... hopefully @vladotesanovic will update the NPM package as this does not seem such a big change

@vladotesanovic, @borisfeldmann I have forked the project and proposed a fix on #178, that would update this library to angular-cli and fix this issue. Hope that it serves.

When I try @borisfeldmann solution with angular 4.0.0 I get Uncaught Error: Unexpected module 'NgSemanticModule' declared by the module 'AppModule'. Please add a @Pipe/@Directive/@Component annotation. Can't add it as a declaration :(

hey everyone,
I too have been struggling with the NgSemanticModule is not a module issue and I just recently upgraded to Angular 4. Same as above, when angular first compiles, it gives me that error, but when I change some code, it recompiles without the error.
I see some of you have found a fix by changing the ng-semantic.d.ts file, but I actually don't seem to have that file anywhere in my project or in my node_modules folder :/
Does anyone have any suggestions? I see there a pull request to fix this from @mp3sii but I'm actually not entirely sure what to do with that. Can I merge that change into my project as well?

borisfeldmann fix didn't work for me - I already had those lines in my ng-semantic.d.ts file.
Also, tried npm install.

@borisfeldmann your solution works for me, even on "ngx-semantic-ui" package with<EMAIL_ADDRESS>

I had an error (ngSemantic with angular error - unexpected module NgSemanticModule) using ng build --prod and it was fixed using in ng.semantic.d.ts file:
import { NgModule } from '@angular/core';
@NgModule() export declare class NgSemanticModule { }

Im still having this issue.  although implementing @borisfeldmann solution fixes it for me, is there a pending pull request to fix the issue or any plan to implement it?

Commenting out import { NgSemanticModule } from 'ng-semantic'; and NgSemanticModule in the imports array in app.module.ts makes it possible to run ng-serve. You can then uncomment those lines when it's up.


Selected items button doesn't work on production, but work on local

For some reason "Selected items" button doesn't work on production (Digital Ocean with Ubuntu 18 + nginx). When i click on this button nothing happens. If i change in inspector display attribute for dropdown which this button should open and click on buttons there, for example "Remove items" button also nothing happens. These clicks also don't throw errors in console. But on my local when i just run rails server command these buttons work nice without any problems

Sounds like an asset-related issue. Check your configuration.


All nodes should be talking to some archive node deployment

The archive node supports many daemons connecting to the same archive node (we're not sure how many, this needs testing), but our infrastructure does not. The block producer chart needs to optionally accept an archive node config, and we then need to test how many simultaneous connections can the archive node keep up with.

Is this needed for mainnet if we have a partner running an archive node? Would propose we do other work first (like having alerts + monitoring for all the things we talk about) before implementing this

Is this needed for mainnet if we have a partner running an archive node? Would propose we do other work first (like having alerts + monitoring for all the things we talk about) before implementing this

Also handle making the postgres DB or entire deployment "serializable" using on of the methods defined in comments on https://github.com/MinaProtocol/mina/pull/7707#issuecomment-769825661

Also handle making the postgres DB or entire deployment "serializable" using on of the methods defined in comments on https://github.com/MinaProtocol/mina/pull/7707#issuecomment-769825661


Added ColorStateList for Label class

Added ColorStateList for Label class - label text changes color when FloatingActionButton is pressed

I have added things that you have asked for in last commit.
By the way very nice work on those Floating buttons!


Nest + Xamarin iOS / Android is not working

I am trying to get ES working on a Xamarin.iOS / Android app; it's not clear if iOS / Android is intended to be supported (which it should be) or if I'm doing something wrong
if you can clarify what the intent is, then i will fill out either as a bug or feature request.

NEST/Elasticsearch.Net version:
Elasticsearch version:
Description of the problem including expected versus actual behavior:
Steps to reproduce:
1.
2.
3.
Provide DebugInformation (if relevant):

Describe the feature:

Hey @Sohojoe, I take it you're using the core clr builds (dotnet5.1 TFM)  of NEST and Elasticsearch.NET?

@russcam - I'm trying to include v2.3.1 from NuGet which does not target iOS or Android. Is there an alternative package? (that would be awesome)
error output:

Adding NEST...
Adding 'NEST 2.3.1' to SynergyScout.iOS.
Could not install package 'NEST 2.3.1'. You are trying to install this package into a project that targets 'Xamarin.iOS,Version=v1.0', but the package does not contain any assembly references or content files that are compatible with that framework. For more information, contact the package author.

If I'm reading the most recent .NET Platform Standard documentation correctly, Xamarin iOS/Android requires netstandard1.5 .NET Platform Standard version, although looking at the Target Framework documentation on Nuget, it requires netstandard1.4 (dotnet5.5). I'm inclined to go with the version specified in the .NET Platform Standard Documentation as it is a newer document than the one on Nuget.
Right now, we have a dotnet5.1 (netstandard1.0) compatible version of NEST in the 2.x releases of Nuget, which is experimental (it's unit and integration tested; experimental because .NET Core is not RTM'ed). The solution is currently using DNX RC1 tooling to build targeted versions.
To release a Xamarin iOS/Android compatible version, we would need to update to target netstandard1.5 which would also require moving over to using RC2 tooling for the build. With the recent announcement that project.json will be retired (which is what we use for RC1), we would need to understand what the impact will be to the solution setup.

A problem that we have in updating to netstandard1.x right now is that there is not a compatible version of Json.Net available on nuget

Hey @Sohojoe, we released a .NET Core 1.0 RTM, Elasticsearch 2.x compatible client yesterday if you'd like to give it a try with iOS or Android? It's a netstandard1.3 targeted release so should work for Xamarin iOS, which requires netstandard1.4.
Let me know if you have any issues.


Disappearing devices?

Added some devices to demo.traccar.org server, but to access the account now, all devices have disappeared, and when I tried to add again received the message that the unique code is already being used.
What is happening?

You already asked this question on the forum. Please don't duplicate it.


Unable to apply where condition to join table

Hello @jenssegers
I am unable to apply where condition to join table when I am using laravel-mongodb.
Please help me asap!
Thanks in advanced

MongoDB's left join $lookup operator has not been implemented here. Check here how to use advanced aggregations


Eslint plugin can't be found

I'm not entirely sure whether to report this here or in the eslint project, but I thought I'd start here.
I'm using eslint in a node project. For some reason, eslint plugins can't be found when run through Jest, even though they're in the node_modules folder. Here's a minimal repro case to demonstrate what I'm seeing:
First, install dependencies:
echo '
{
  "dependencies": {
    "eslint": "^2.8.0",
    "eslint-config-airbnb": "^7.0.0",
    "eslint-plugin-jsx-a11y": "^0.6.2",
    "eslint-plugin-react": "^4.3.0",
    "jest-cli": "^11.0.1"
  }
}
' > package.json
npm install

Then, create a test (using eslint):
mkdir __tests__
echo "
jest.autoMockOff();
const CLIEngine = require('eslint').CLIEngine;
new CLIEngine().executeOnText('var foo = 0;');
" > __tests__/foo-test.js

Tell eslint to depend on airbnb configuration:
echo module.exports = { extends: 'airbnb' };

Run the test
node_modules/.bin/jest

Get error:
Using Jest CLI v11.0.1, jasmine2
 FAIL  __tests__/foo-test.js
● Runtime Error
Error: Cannot find module 'eslint-config-airbnb'

If I run the test file without jest, it works.
Any ideas what could be wrong? This might be related to https://github.com/facebook/jest/issues/894, but I'm not sure.

This seems to work fine with eslint 2.5.3, but with 2.6.0, I see errors like:
- TypeError: Cannot read property 'concat' of undefined
      at Object.<anonymous> (node_modules/eslint/lib/util/module-resolver.js:28:30)
      at Object.<anonymous> (node_modules/eslint/lib/config/config-file.js:23:22)
      at Object.<anonymous> (node_modules/eslint/lib/config.js:17:18)
      at Object.<anonymous> (node_modules/eslint/lib/cli-engine.js:31:14)
      at Object.<anonymous> (node_modules/eslint/lib/api.js:10:16)

Same with 2.7.0.
With 2.8.0, I see Error: Cannont find module 'eslint-config-airbnb'.
Tested with Jest CLI v0.9.2, jasmine2.

This is a little bit upsetting, eslint is using private APIs ("module.paths") which Jest's sandbox isn't polyfilling as expected. @lencioni you are setting this because prior to 11.0 paths was not defined. In 11.0 it is an empty array which is why it cannot find airbnb's config.
I'll look into fixing this for the release today.

Fix will go out with 11.0.2 today.

Thanks @cpojer for the fix and @lencioni for providing additional information! I've verified that things are working as they should after installing jest-cli 11.0.2.


E tensorflow/stream_executor/cuda/cuda_blas.cc:226] failed to create cublas handle: CUBLAS_STATUS_NOT_INITIALIZED

Put the following code below import tensorflow as tf at demo.py
config = tf.compat.v1.ConfigProto()
config.gpu_options.allow_growth = True
session = tf.compat.v1.Session(config=config)
otherwise you will get E tensorflow/stream_executor/cuda/cuda_blas.cc:226] failed to create cublas handle: CUBLAS_STATUS_NOT_INITIALIZED

That's strange.
I'm not able to replicate this error.
I just tested using tensorflow-gpu==2.2.0 with cudatoolkit==10.1 and cudnn==7.6.5.
(the standard conda install tensorflow-gpu as of today).
Are you using multiple GPUs?

That's strange.
I'm not able to replicate this error.
I just tested using tensorflow-gpu==2.2.0 with cudatoolkit==10.1 and cudnn==7.6.5.
(the standard conda install tensorflow-gpu as of today).
Are you using multiple GPUs?

I see exactly the same error with tensorflow-gpu==2.4 with cudatoolkit==11.2 and cudnn==8.1.1
[I 05:14:34.514 NotebookApp] Kernel started: e5839984-732b-4715-ae1b-677560c51561, name: python3
2021-03-25 05:14:44.423139: I tensorflow/stream_executor/platform/default/dso_loader.cc:49] Successfully opened dynamic library libcudart.so.11.0
2021-03-25 05:15:00.356721: I tensorflow/compiler/jit/xla_cpu_device.cc:41] Not creating XLA devices, tf_xla_enable_xla_devices not set
2021-03-25 05:15:00.358954: I tensorflow/stream_executor/platform/default/dso_loader.cc:49] Successfully opened dynamic library libcuda.so.1
2021-03-25 05:15:00.373974: I tensorflow/stream_executor/cuda/cuda_gpu_executor.cc:941] successful NUMA node read from SysFS had negative value (-1), but there must be at least one NUMA node, so returning NUMA node zero
2021-03-25 05:15:00.374943: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1720] Found device 0 with properties:
pciBusID: 0000:01:00.0 name: Tesla M40 computeCapability: 5.2
coreClock: 1.112GHz coreCount: 24 deviceMemorySize: 11.18GiB deviceMemoryBandwidth: 268.58GiB/s
2021-03-25 05:15:00.375035: I tensorflow/stream_executor/platform/default/dso_loader.cc:49] Successfully opened dynamic library libcudart.so.11.0
2021-03-25 05:15:00.381241: I tensorflow/stream_executor/platform/default/dso_loader.cc:49] Successfully opened dynamic library libcublas.so.11
2021-03-25 05:15:00.381362: I tensorflow/stream_executor/platform/default/dso_loader.cc:49] Successfully opened dynamic library libcublasLt.so.11
2021-03-25 05:15:00.383005: I tensorflow/stream_executor/platform/default/dso_loader.cc:49] Successfully opened dynamic library libcufft.so.10
2021-03-25 05:15:00.383415: I tensorflow/stream_executor/platform/default/dso_loader.cc:49] Successfully opened dynamic library libcurand.so.10
2021-03-25 05:15:00.388525: I tensorflow/stream_executor/platform/default/dso_loader.cc:49] Successfully opened dynamic library libcusolver.so.10
2021-03-25 05:15:00.389576: I tensorflow/stream_executor/platform/default/dso_loader.cc:49] Successfully opened dynamic library libcusparse.so.11
2021-03-25 05:15:00.389801: I tensorflow/stream_executor/platform/default/dso_loader.cc:49] Successfully opened dynamic library libcudnn.so.8
2021-03-25 05:15:00.389948: I tensorflow/stream_executor/cuda/cuda_gpu_executor.cc:941] successful NUMA node read from SysFS had negative value (-1), but there must be at least one NUMA node, so returning NUMA node zero

I think this is an upstream issue. I ran into a similar error while running the MNIST example on Kubeflow, and resolved it using the above solution by @Sequential-circuits.
Short version info: containerized tensorflow-gpu 2.4.1 and cuda 11.0.3.
Long version info:

Host running Ubuntu 20.04.2
Single GPU: GeForce GTX 1050 Ti
NVIDIA driver 460.39
CUDA 11.2
nvidia-container-runtime 3.4.2
nvidia-container-toolkit 1.4.2
Docker 19.03.8 / containerd 1.4.3
Kubernetes 1.20.5
Kubeflow 1.2.0
Tensorflow v2.4.1 from Docker image tensorflow/tensorflow:latest-gpu as of 2021-01-22

Relevant logs:
...
2021-04-07 20:59:48.297555: I tensorflow/compiler/jit/xla_cpu_device.cc:41] Not creating XLA devices, tf_xla_enable_xla_devices not set
2021-04-07 20:59:48.298272: I tensorflow/stream_executor/platform/default/dso_loader.cc:49] Successfully opened dynamic library libcuda.so.1
2021-04-07 20:59:48.308894: I tensorflow/stream_executor/cuda/cuda_gpu_executor.cc:941] successful NUMA node read from SysFS had negative value (-1), but there must be at least one NUMA node, so returning NUMA node zero
2021-04-07 20:59:48.309112: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1720] Found device 0 with properties:
pciBusID: 0000:01:00.0 name: GeForce GTX 1050 Ti computeCapability: 6.1
coreClock: 1.4425GHz coreCount: 6 deviceMemorySize: 3.95GiB deviceMemoryBandwidth: 104.43GiB/s
2021-04-07 20:59:48.309130: I tensorflow/stream_executor/platform/default/dso_loader.cc:49] Successfully opened dynamic library libcudart.so.11.0
2021-04-07 20:59:48.310580: I tensorflow/stream_executor/platform/default/dso_loader.cc:49] Successfully opened dynamic library libcublas.so.11
2021-04-07 20:59:48.310627: I tensorflow/stream_executor/platform/default/dso_loader.cc:49] Successfully opened dynamic library libcublasLt.so.11
2021-04-07 20:59:48.311241: I tensorflow/stream_executor/platform/default/dso_loader.cc:49] Successfully opened dynamic library libcufft.so.10
2021-04-07 20:59:48.311436: I tensorflow/stream_executor/platform/default/dso_loader.cc:49] Successfully opened dynamic library libcurand.so.10
2021-04-07 20:59:48.312884: I tensorflow/stream_executor/platform/default/dso_loader.cc:49] Successfully opened dynamic library libcusolver.so.10
2021-04-07 20:59:48.313234: I tensorflow/stream_executor/platform/default/dso_loader.cc:49] Successfully opened dynamic library libcusparse.so.11
2021-04-07 20:59:48.313364: I tensorflow/stream_executor/platform/default/dso_loader.cc:49] Successfully opened dynamic library libcudnn.so.8
2021-04-07 20:59:48.313463: I tensorflow/stream_executor/cuda/cuda_gpu_executor.cc:941] successful NUMA node read from SysFS had negative value (-1), but there must be at least one NUMA node, so returning NUMA node zero
2021-04-07 20:59:48.313770: I tensorflow/stream_executor/cuda/cuda_gpu_executor.cc:941] successful NUMA node read from SysFS had negative value (-1), but there must be at least one NUMA node, so returning NUMA node zero
2021-04-07 20:59:48.314018: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1862] Adding visible gpu devices: 0
2021-04-07 20:59:48.314297: I tensorflow/core/platform/cpu_feature_guard.cc:142] This TensorFlow binary is optimized with oneAPI Deep Neural Network Library (oneDNN) to use the following CPU instructions in performance-critical operations:  AVX2 FMA
To enable them in other operations, rebuild TensorFlow with the appropriate compiler flags.
2021-04-07 20:59:48.314617: I tensorflow/compiler/jit/xla_gpu_device.cc:99] Not creating XLA devices, tf_xla_enable_xla_devices not set
2021-04-07 20:59:48.314741: I tensorflow/stream_executor/cuda/cuda_gpu_executor.cc:941] successful NUMA node read from SysFS had negative value (-1), but there must be at least one NUMA node, so returning NUMA node zero
2021-04-07 20:59:48.314986: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1720] Found device 0 with properties:
pciBusID: 0000:01:00.0 name: GeForce GTX 1050 Ti computeCapability: 6.1
coreClock: 1.4425GHz coreCount: 6 deviceMemorySize: 3.95GiB deviceMemoryBandwidth: 104.43GiB/s
2021-04-07 20:59:48.315006: I tensorflow/stream_executor/platform/default/dso_loader.cc:49] Successfully opened dynamic library libcudart.so.11.0
2021-04-07 20:59:48.315026: I tensorflow/stream_executor/platform/default/dso_loader.cc:49] Successfully opened dynamic library libcublas.so.11
2021-04-07 20:59:48.315034: I tensorflow/stream_executor/platform/default/dso_loader.cc:49] Successfully opened dynamic library libcublasLt.so.11
2021-04-07 20:59:48.315043: I tensorflow/stream_executor/platform/default/dso_loader.cc:49] Successfully opened dynamic library libcufft.so.10
2021-04-07 20:59:48.315049: I tensorflow/stream_executor/platform/default/dso_loader.cc:49] Successfully opened dynamic library libcurand.so.10
2021-04-07 20:59:48.315057: I tensorflow/stream_executor/platform/default/dso_loader.cc:49] Successfully opened dynamic library libcusolver.so.10
2021-04-07 20:59:48.315065: I tensorflow/stream_executor/platform/default/dso_loader.cc:49] Successfully opened dynamic library libcusparse.so.11
2021-04-07 20:59:48.315073: I tensorflow/stream_executor/platform/default/dso_loader.cc:49] Successfully opened dynamic library libcudnn.so.8
2021-04-07 20:59:48.315118: I tensorflow/stream_executor/cuda/cuda_gpu_executor.cc:941] successful NUMA node read from SysFS had negative value (-1), but there must be at least one NUMA node, so returning NUMA node zero
2021-04-07 20:59:48.315299: I tensorflow/stream_executor/cuda/cuda_gpu_executor.cc:941] successful NUMA node read from SysFS had negative value (-1), but there must be at least one NUMA node, so returning NUMA node zero
2021-04-07 20:59:48.315451: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1862] Adding visible gpu devices: 0
2021-04-07 20:59:48.315472: I tensorflow/stream_executor/platform/default/dso_loader.cc:49] Successfully opened dynamic library libcudart.so.11.0
2021-04-07 20:59:48.699735: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1261] Device interconnect StreamExecutor with strength 1 edge matrix:
2021-04-07 20:59:48.699758: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1267]      0
2021-04-07 20:59:48.699764: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1280] 0:   N
2021-04-07 20:59:48.699902: I tensorflow/stream_executor/cuda/cuda_gpu_executor.cc:941] successful NUMA node read from SysFS had negative value (-1), but there must be at least one NUMA node, so returning NUMA node zero
2021-04-07 20:59:48.700123: I tensorflow/stream_executor/cuda/cuda_gpu_executor.cc:941] successful NUMA node read from SysFS had negative value (-1), but there must be at least one NUMA node, so returning NUMA node zero
2021-04-07 20:59:48.700306: I tensorflow/stream_executor/cuda/cuda_gpu_executor.cc:941] successful NUMA node read from SysFS had negative value (-1), but there must be at least one NUMA node, so returning NUMA node zero
2021-04-07 20:59:48.700474: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1406] Created TensorFlow device (/job:localhost/replica:0/task:0/device:GPU:0 with 931 MB memory) -> physical GPU (device: 0, name: GeForce GTX 1050 Ti, pci bus id: 0000:01:00.0, compute capability: 6.1)
2021-04-07 20:59:48.702531: I tensorflow/stream_executor/cuda/cuda_driver.cc:789] failed to allocate 931.00M (976224256 bytes) from device: CUDA_ERROR_OUT_OF_MEMORY: out of memory
2021-04-07 20:59:48.881729: I tensorflow/compiler/mlir/mlir_graph_optimization_pass.cc:116] None of the MLIR optimization passes are enabled (registered 2)
2021-04-07 20:59:48.882236: I tensorflow/core/platform/profile_utils/cpu_utils.cc:112] CPU Frequency:<PHONE_NUMBER> Hz
Epoch 1/10
2021-04-07 20:59:49.075014: I tensorflow/stream_executor/platform/default/dso_loader.cc:49] Successfully opened dynamic library libcublas.so.11
2021-04-07 20:59:49.167725: E tensorflow/stream_executor/cuda/cuda_blas.cc:226] failed to create cublas handle: CUBLAS_STATUS_NOT_INITIALIZED
2021-04-07 20:59:49.170178: E tensorflow/stream_executor/cuda/cuda_blas.cc:226] failed to create cublas handle: CUBLAS_STATUS_NOT_INITIALIZED
2021-04-07 20:59:49.171979: E tensorflow/stream_executor/cuda/cuda_blas.cc:226] failed to create cublas handle: CUBLAS_STATUS_NOT_INITIALIZED
2021-04-07 20:59:49.173476: E tensorflow/stream_executor/cuda/cuda_blas.cc:226] failed to create cublas handle: CUBLAS_STATUS_NOT_INITIALIZED
2021-04-07 20:59:49.174947: E tensorflow/stream_executor/cuda/cuda_blas.cc:226] failed to create cublas handle: CUBLAS_STATUS_NOT_INITIALIZED
2021-04-07 20:59:49.176206: E tensorflow/stream_executor/cuda/cuda_blas.cc:226] failed to create cublas handle: CUBLAS_STATUS_NOT_INITIALIZED
2021-04-07 20:59:49.176222: W tensorflow/stream_executor/stream.cc:1455] attempting to perform BLAS operation using StreamExecutor without BLAS support
Traceback (most recent call last):
  File "/tmp/tmp.vZeQzAzGzj", line 49, in <module>
    _outputs = mnist_train(**_parsed_args)
  File "/tmp/tmp.vZeQzAzGzj", line 30, in mnist_train
    model.fit(train_images, train_labels, epochs=10)
  File "/usr/local/lib/python3.6/dist-packages/tensorflow/python/keras/engine/training.py", line 1100, in fit
    tmp_logs = self.train_function(iterator)
  File "/usr/local/lib/python3.6/dist-packages/tensorflow/python/eager/def_function.py", line 828, in __call__
    result = self._call(*args, **kwds)
  File "/usr/local/lib/python3.6/dist-packages/tensorflow/python/eager/def_function.py", line 888, in _call
    return self._stateless_fn(*args, **kwds)
  File "/usr/local/lib/python3.6/dist-packages/tensorflow/python/eager/function.py", line 2943, in __call__
    filtered_flat_args, captured_inputs=graph_function.captured_inputs)  # pylint: disable=protected-access
  File "/usr/local/lib/python3.6/dist-packages/tensorflow/python/eager/function.py", line 1919, in _call_flat
    ctx, args, cancellation_manager=cancellation_manager))
  File "/usr/local/lib/python3.6/dist-packages/tensorflow/python/eager/function.py", line 560, in call
    ctx=ctx)
  File "/usr/local/lib/python3.6/dist-packages/tensorflow/python/eager/execute.py", line 60, in quick_execute
    inputs, attrs, num_outputs)
tensorflow.python.framework.errors_impl.InternalError:  Blas GEMM launch failed : a.shape=(32, 784), b.shape=(784, 128), m=32, n=128, k=784
	 [[node sequential/dense/MatMul (defined at tmp/tmp.vZeQzAzGzj:30) ]] [Op:__inference_train_function_536]
Function call stack:
train_function


已配置本地化，但是不显示中文！

Laravel Version: 8.83.27
PHP Version:7.4
Laravel-admin: 1.8.19

Description:

Steps To Reproduce:

I think it expects the locale to be "zh-CH" with a dash. Can you test that?

You can also rename the dir to be lang/zh_CH (or resources/lang/zh_CH for Laravel < 9.x) if you feel like it suits you better.


Add hard-coded options to choose currency for the membership registering

@cmutel Can you remind, which exact options should be used?

Isn't it required anymore?


CHT Issue 28

Hi guys, please check this PR. @noescape00 @Aprogiena .
Thanks.

Looks good, just minor improvements required

@Aprogiena, the test is improved.

Passing to @noescape00


enable wasi-c by default for releases

can the wasi-c functionality be enabled by default, at least for releases ?  the only way to experiment with wasmtime --wasi-c currently is by building wasmtime yourself from source which is a bit of a drag.  would be nice if the release prebuilts just included that.

We disabled it by default in part because it uses cmake as a dependency, which turned out to be a noticeable for many people building Wasmtime. Also, disabling it makes our code footprint smaller; we don't usually need two WASI implementations. Can you say more about what you're looking to do here?

I'm curious to see what you're after @vapier here as well :-)

i was experimenting with code that used /dev/urandom which the default runtime doesn't support.  i tried tracing the code a bit but couldn't see where it was going wrong.  the wasi-c runtime had no problem with it (the wasmtime-wasi-c/sandboxed-system-primitives/src/rights.h header has comments around RIGHTS_CHARACTER_DEVICE_BASE saying "grant all for now").
test case:
#include <errno.h>
#include <fcntl.h>
#include <stdio.h>
#include <stdlib.h>
#include <string.h>
#include <unistd.h>
int main(int argc, char *argv[])
{
	char *path = "/dev/urandom";
	if (argc > 1)
		path = argv[1];
	errno = 0;
	printf("open(%s) = %i (%i = %s)\n", path, open(path, O_RDONLY),
		errno, strerror(errno));
	return 0;
}

compiling with wasi-sdk-7.0:
$ ./wasi-sdk/bin/clang -Wall --sysroot=./wasi-sdk/share/wasi-sysroot test.c -o test.wasm

running with wasmtime-0.3.0:
$ wasmtime --dir=. --dir=/dev ./test.wasm /dev/null
open(/dev/null) = 5 (0 = Success)
$ wasmtime --dir=. --dir=/dev ./test.wasm /dev/zero
open(/dev/zero) = 5 (0 = Success)
$ wasmtime --dir=. --dir=/dev ./test.wasm /dev/full
open(/dev/full) = 5 (0 = Success)
$ wasmtime --dir=. --dir=/dev ./test.wasm /dev/urandom
open(/dev/urandom) = -1 (28 = Invalid argument)
$ wasmtime --dir=. --dir=/dev ./test.wasm /dev/random
open(/dev/random) = -1 (28 = Invalid argument)

repeating with current master (e1b9c01d94485fa63d90920a10f49a3e9499f863) shows same behavior.  switching to --wasi-c makes it work.
i know that wasi-sdk includes the non-standard BSD arc4random APIs, but i don't want to go through projects and rewrite code to use them instead of /dev/urandom (or the Linux getrandom API).

That's interesting. I cannot actually reproduce this error with the latest version of wasi-common. Here's the output I'm getting:
$ target/release/wasmtime -d --dir=/dev test.wasm /dev/null
open(/dev/null) = 4 (0 = Success)

$ target/release/wasmtime -d --dir=/dev test.wasm /dev/random
open(/dev/random) = 4 (0 = Success)

$ target/release/wasmtime -d --dir=/dev test.wasm /dev/urandom
open(/dev/urandom) = 4 (0 = Success)

It seems that the version of wasi-common is somewhat outdated in wasmtime and that might just be the cause of the issue you've encountered. I've now submitted PR #398 which fast-forwards wasmtime to the latest wasi-common version. Could you do me a favour and after the PR lands in master, build wasmtime from source (without the --wasi-c flag) and see whether you're still getting an error?

i can give it another try once the PR goes through.  i'm not blocked on anything as i can continue experimenting with wasi-c.
i get that wasi-c requiring cmake/updated native compilers can be problematic for enabling it by default everywhere.  but i think that's a bit orthogonal to "should it be enabled in the default release binaries hosted here".  i have no idea where it's being built though (someone's workstation rather than the CI?).
wrt size, it doesn't seem to add that much unstripped ... adds (very) roughly ~1MB to wasmtime.  although i see the release prebuilts include debug info in them which balloons the size quite a lot (like 4x+).  i guess the current state of wasmtime is more on the "it's a developer preview" rather than "it's MVP" so shipping debug info directly isn't unreasonable.

i get that wasi-c requiring cmake/updated native compilers can be problematic for enabling it by default everywhere.

The bigger reason for not enabling it by default—or including it in our CI-built binaries—is that we want to remove it. Anything supported in wasi-c but not wasi-common is a bug in wasi-common, and by now there should be very few of these left, luckily.
Hopefully, your issue will be resolved once #398 lands! :)

if the overall goal is to replace wasi-c with wasi-common, that's good to know.  i started extending wasi-c, but i'll transition over to that.

@vapier I've now merged #398 so if you could check if you can reproduce the error, that'd be great!
In terms of not having wasi-c baked in, in addition to what @sunfishcode and @tschneidereit already said, providing Windows support for wasi-c proved, well, to be problematic. Hence yet another reason why we're removing custom build.rs scripts in favour of the majority of the codebase written in Rust without any tricky C interops.

if the overall goal is to replace wasi-c with wasi-common, that's good to know. i started extending wasi-c, but i'll transition over to that.

Please do! If you have any questions about the code organisation in wasi-common, you know, the "what, where, why", fire away and I'll do my best to help out as best as I can!

i ran git pull --recurse so i'm at daa3c3aeefc2633f563c2f485b13fee679e355e4.  then cargo build to update things.  still not happy though.  no idea what to check next.
$ RUST_LOG=trace ./target/debug/wasmtime -d --dir=. --dir=/dev ./test.wasm /dev/urandom
 DEBUG wasmtime_environ::cache::worker > Cache worker thread started.
 DEBUG wasmtime_environ::cache::worker > New nice value of worker thread: 3
 DEBUG wasmtime_environ::cache::config > Cache init("None"): CacheConfig {
    errors: [],
    enabled: true,
    directory: Some(
        "/home/vapier/.cache/wasmtime",
    ),
    worker_event_queue_size: Some(
        16,
    ),
    baseline_compression_level: Some(
        3,
    ),
    optimized_compression_level: Some(
        20,
    ),
    optimized_compression_usage_counter_threshold: Some(
        256,
    ),
    cleanup_interval: Some(
        3600s,
    ),
    optimizing_compression_task_timeout: Some(
        1800s,
    ),
    allowed_clock_drift_for_files_from_future: Some(
        86400s,
    ),
    file_count_soft_limit: Some(
        65536,
    ),
    files_total_size_soft_limit: Some(
        536870912,
    ),
    file_count_limit_percent_if_deleting: Some(
        70,
    ),
    files_total_size_limit_percent_if_deleting: Some(
        70,
    ),
}
 DEBUG cranelift_codegen::timing::details > timing: Starting Translate WASM module, (during <no pass>)
 DEBUG cranelift_codegen::timing::details > timing: Ending Translate WASM module
 TRACE wasmtime_environ::cache            > get_data() for path: /home/vapier/.cache/wasmtime/x86_64-unknown-linux-gnu/cranelift-e1b9c01d94485fa63d90920a10f49a3e9499f863-1570154157334/mod-OD6fNonRmbH0u3JQUxR7Gzwr8wFom6Uz-AyHxwmxYEQ
 TRACE wasmtime_environ::cache::worker    > handle_on_cache_get() for path: /home/vapier/.cache/wasmtime/x86_64-unknown-linux-gnu/cranelift-e1b9c01d94485fa63d90920a10f49a3e9499f863-1570154157334/mod-OD6fNonRmbH0u3JQUxR7Gzwr8wFom6Uz-AyHxwmxYEQ
 TRACE wasmtime_wasi::syscalls            > fd_prestat_get(fd=3, buf=0x11480)
 TRACE wasi_common::hostcalls_impl::fs    > fd_prestat_get(fd=3, prestat_ptr=0x11480)
 TRACE wasi_common::hostcalls             >     -> errno=__WASI_ESUCCESS
 TRACE wasmtime_wasi::syscalls            > fd_prestat_dir_name(fd=3, path=0x200a0, path_len=1)
 TRACE wasi_common::hostcalls_impl::fs    > fd_prestat_dir_name(fd=3, path_ptr=0x200a0, path_len=1)
 TRACE wasi_common::hostcalls_impl::fs    >      | (path_ptr,path_len)='.'
 TRACE wasi_common::hostcalls             >     -> errno=__WASI_ESUCCESS
 TRACE wasmtime_wasi::syscalls            > fd_fdstat_get(fd=3, buf=0x11468)
 TRACE wasi_common::hostcalls_impl::fs    > fd_fdstat_get(fd=3, fdstat_ptr=0x11468)
 TRACE wasi_common::hostcalls_impl::fs    >      | *buf=__wasi_fdstat_t { fs_filetype: 3, fs_flags: 0, fs_rights_base: 264240792, fs_rights_inheriting: 268435455 }
 TRACE wasi_common::hostcalls             >     -> errno=__WASI_ESUCCESS
 TRACE wasmtime_wasi::syscalls            > fd_prestat_get(fd=4, buf=0x11480)
 TRACE wasi_common::hostcalls_impl::fs    > fd_prestat_get(fd=4, prestat_ptr=0x11480)
 TRACE wasi_common::hostcalls             >     -> errno=__WASI_ESUCCESS
 TRACE wasmtime_wasi::syscalls            > fd_prestat_dir_name(fd=4, path=0x200a0, path_len=4)
 TRACE wasi_common::hostcalls_impl::fs    > fd_prestat_dir_name(fd=4, path_ptr=0x200a0, path_len=4)
 TRACE wasi_common::hostcalls_impl::fs    >      | (path_ptr,path_len)='/dev'
 TRACE wasi_common::hostcalls             >     -> errno=__WASI_ESUCCESS
 TRACE wasmtime_wasi::syscalls            > fd_fdstat_get(fd=4, buf=0x11468)
 TRACE wasi_common::hostcalls_impl::fs    > fd_fdstat_get(fd=4, fdstat_ptr=0x11468)
 TRACE wasi_common::hostcalls_impl::fs    >      | *buf=__wasi_fdstat_t { fs_filetype: 3, fs_flags: 0, fs_rights_base: 264240792, fs_rights_inheriting: 268435455 }
 TRACE wasi_common::hostcalls             >     -> errno=__WASI_ESUCCESS
 TRACE wasmtime_wasi::syscalls            > fd_prestat_get(fd=5, buf=0x11480)
 TRACE wasi_common::hostcalls_impl::fs    > fd_prestat_get(fd=5, prestat_ptr=0x11480)
 TRACE wasi_common::hostcalls             >     -> errno=__WASI_EBADF
 TRACE wasmtime_wasi::syscalls            > environ_sizes_get(environ_count=0x11480, environ_buf_size=0x1148c)
 TRACE wasi_common::hostcalls_impl::misc  > environ_sizes_get(environ_count_ptr=0x11480, environ_size_ptr=0x1148c)
 TRACE wasi_common::hostcalls_impl::misc  >      | *environ_count_ptr=0
 TRACE wasi_common::hostcalls_impl::misc  >      | *environ_size_ptr=0
 TRACE wasi_common::hostcalls             >     -> errno=__WASI_ESUCCESS
 TRACE wasmtime_wasi::syscalls            > environ_get(environ=0x200a0, environ_buf=0x200d0)
 TRACE wasi_common::hostcalls_impl::misc  > environ_get(environ_ptr=0x200a0, environ_buf=0x200d0)
 TRACE wasi_common::hostcalls             >     -> errno=__WASI_ESUCCESS
 TRACE wasmtime_wasi::syscalls            > args_sizes_get(argc=0x1148c, argv_buf_size=0x11480)
 TRACE wasi_common::hostcalls_impl::misc  > args_sizes_get(argc_ptr=0x1148c, argv_buf_size_ptr=0x11480)
 TRACE wasi_common::hostcalls_impl::misc  >      | *argc_ptr=2
 TRACE wasi_common::hostcalls_impl::misc  >      | *argv_buf_size_ptr=23
 TRACE wasi_common::hostcalls             >     -> errno=__WASI_ESUCCESS
 TRACE wasmtime_wasi::syscalls            > args_get(argv=0x200e0, argv_buf=0x200f0)
 TRACE wasi_common::hostcalls_impl::misc  > args_get(argv_ptr=0x200e0, argv_buf=0x200f0)
 TRACE wasi_common::hostcalls             >     -> errno=__WASI_ESUCCESS
 TRACE wasmtime_wasi::syscalls            > fd_fdstat_get(fd=4, buf=0x11428)
 TRACE wasi_common::hostcalls_impl::fs    > fd_fdstat_get(fd=4, fdstat_ptr=0x11428)
 TRACE wasi_common::hostcalls_impl::fs    >      | *buf=__wasi_fdstat_t { fs_filetype: 3, fs_flags: 0, fs_rights_base: 264240792, fs_rights_inheriting: 268435455 }
 TRACE wasi_common::hostcalls             >     -> errno=__WASI_ESUCCESS
 TRACE wasmtime_wasi::syscalls            > path_open(dirfd=4, dirflags=1, path=0x200ff, path_len=7, oflags=0x0, fs_rights_base=0xfbffebe, fs_rights_inheriting=0xfffffff, fs_flags=0x0, fd=0x11424)
 TRACE wasi_common::hostcalls_impl::fs    > path_open(dirfd=4, dirflags=1, path_ptr=0x200ff, path_len=7, oflags=0x0, fs_rights_base=0xfbffebe, fs_rights_inheriting=0xfffffff, fs_flags=0x0, fd_out_ptr=0x11424)
 TRACE wasi_common::hostcalls_impl::fs    >      | (path_ptr,path_len)='urandom'
 DEBUG wasi_common::hostcalls_impl::fs_helpers > cur_path = "urandom"
 TRACE wasi_common::hostcalls                  >     -> errno=__WASI_EINVAL
 TRACE wasmtime_wasi::syscalls                 > fd_fdstat_get(fd=1, buf=0x10ff8)
 TRACE wasi_common::hostcalls_impl::fs         > fd_fdstat_get(fd=1, fdstat_ptr=0x10ff8)
 TRACE wasi_common::hostcalls                  >     -> errno=__WASI_EBADF
 TRACE wasmtime_wasi::syscalls                 > fd_write(fd=1, iovs=0x11000, iovs_len=2, nwritten=0x10ffc)
 TRACE wasi_common::hostcalls_impl::fs         > fd_write(fd=1, iovs_ptr=0x11000, iovs_len=2, nwritten=0x10ffc)
open(/dev/urandom) = -1 (28 = Invalid argument TRACE wasi_common::hostcalls_impl::fs         >      | *nwritten=46
 TRACE wasi_common::hostcalls                  >     -> errno=__WASI_ESUCCESS
 TRACE wasmtime_wasi::syscalls                 > fd_write(fd=1, iovs=0x11000, iovs_len=2, nwritten=0x10ffc)
 TRACE wasi_common::hostcalls_impl::fs         > fd_write(fd=1, iovs_ptr=0x11000, iovs_len=2, nwritten=0x10ffc)
)
 TRACE wasi_common::hostcalls_impl::fs         >      | *nwritten=2
 TRACE wasi_common::hostcalls                  >     -> errno=__WASI_ESUCCESS

snippet from strace:
fcntl(7, F_GETFD)                       = 0x1 (flags FD_CLOEXEC)
readlinkat(7, "urandom", 0x7ffc58e9358f, 4097) = -1 EINVAL (Invalid argument)
openat(7, "urandom", O_RDONLY|O_NOFOLLOW) = 8
close(7)                                = 0
fstat(8, {st_dev=makedev(0, 6), st_ino=1033, st_mode=S_IFCHR|0666, st_nlink=1, st_uid=65534, st_gid=65534, st_blksize=4096, st_blocks=0, st_rdev=makedev(1, 9), st_atime=2019-10-02T18:39:50-0400.615180139, st_mtime=2019-10-02T18:39:50-0400.615180139, st_ctime=2019-10-02T18:39:50-0400.615180139}) = 0
ioctl(8, TCGETS, 0x7ffc58e94fb0)        = -1 EINVAL (Invalid argument)
close(8)                                = 0
write(1, "open(/dev/urandom) = -1 (28 = In"..., 46open(/dev/urandom) = -1 (28 = Invalid argument) = 46

vs
fcntl(7, F_GETFD)                       = 0x1 (flags FD_CLOEXEC)
readlinkat(7, "null", 0x7ffffb0a4cbf, 4097) = -1 EINVAL (Invalid argument)
openat(7, "null", O_RDONLY|O_NOFOLLOW)  = 8
close(7)                                = 0
fstat(8, {st_dev=makedev(0, 6), st_ino=1028, st_mode=S_IFCHR|0666, st_nlink=1, st_uid=65534, st_gid=65534, st_blksize=4096, st_blocks=0, st_rdev=makedev(1, 3), st_atime=2019-10-02T18:39:50-0400.615180139, st_mtime=2019-10-02T18:39:50-0400.615180139, st_ctime=2019-10-02T18:39:50-0400.615180139}) = 0
ioctl(8, TCGETS, 0x7ffffb0a66e0)        = -1 ENOTTY (Inappropriate ioctl for device)
fstat(8, {st_dev=makedev(0, 6), st_ino=1028, st_mode=S_IFCHR|0666, st_nlink=1, st_uid=65534, st_gid=65534, st_blksize=4096, st_blocks=0, st_rdev=makedev(1, 3), st_atime=2019-10-02T18:39:50-0400.615180139, st_mtime=2019-10-02T18:39:50-0400.615180139, st_ctime=2019-10-02T18:39:50-0400.615180139}) = 0
ioctl(8, TCGETS, 0x7ffffb0a6500)        = -1 ENOTTY (Inappropriate ioctl for device)
fcntl(8, F_GETFL)                       = 0x28000 (flags O_RDONLY|O_LARGEFILE|O_NOFOLLOW)
write(1, "open(/dev/null) = 5 (0 = Success", 32open(/dev/null) = 5 (0 = Success) = 32

ioctl TCGETS for urandom gives EINVAL, while TCGETS for null gives ENOTTY.

Hey @vapier! Sorry for not getting in touch earlier but I just got back from my travels. A quick update on my end, I believe I've managed to replicate your issue on my Linux box (running latest Arch distro), so fingers crossed this will lead me to the solution. Interestingly enough though, as I've posted earlier, I couldn't replicate the issue on my MacOS, so perhaps a hint lies somewhere there :-)

I believe I've found the root cause of the issue and (hopefully) now fixed it in CraneStation/wasi-common#131. Just to sum up briefly, it turns out that the problem lied in our use of nix's nix::unistd::isatty wrapper for libc::isatty syscall. nix's implementation handles only ENOTTY as a signal for a valid file descriptor which is not a TTY, which indeed is as POSIX prescribes. However, on Linux, it seems that EINVAL is also used for that very purpose, which, in our implementation of wasi-common was treated only as an error, and hence, leading to the erroneous behaviour that you've uncovered (thanks for that BTW!).
When CraneStation/wasi-common#131 lands, I'll update the dependencies in wasmtime and let you know @vapier! :-)

@vapier the fix should now be available if you compile wasmtime from source :-) I'd be much appreciated if you could check it out and verify that it indeed works for you as well! Also, thanks again for your bug report, it's been really helpful, and I hope you'll submit more of those should come across some additional bugs :-)
@tschneidereit how do we publish latest nightly wasmtime builds nowadays? Is it automated after every merged PR into upstream, or do we press some magic button? I'm asking cause it'd be good to have the latest fixes to wasi-common baked into latest nightly wasmtime build :-)

It gets build automatically: https://github.com/CraneStation/wasmtime/releases/tag/dev

It gets build automatically: https://github.com/CraneStation/wasmtime/releases/tag/dev

Ah, of course, now I see it. Thanks for pointing it out!


LaTeX formula support?

Any plans to support inline LaTeX compilation? Otherwise, any guidance on how one might go about implementing it?

This would depend a bit on what you mean.
If you are talking about about code blocks having LaTeX support, that would be pretty easy to do and I’d be happy to give you some guidance on how to make the change in organized to support it.
If you are talking about LaTeX export, that’s going to have to wait a bit. I have plans to allow exporting to HTML and maybe PDF at some undetermined point in the future. Getting there is going to require some design work and refactoring on my part to avoid something that’s impossible to maintain.  My work on Organized is adhoc, uneven, and mostly done on a train, so no guarantees when that will happen.

I would love to have some guidance on how to make that change. It would be really useful to me to have the code blocks with LaTeX.
On Oct 26, 2017, 2:07 PM +0100, Matt Flower<EMAIL_ADDRESS>wrote:

This would depend a bit on what you mean.
If you are talking about about code blocks having LaTeX support, that would be pretty easy to do and I’d be happy to give you some guidance on how to make the change in organized to support it.
If you are talking about LaTeX export, that’s going to have to wait a bit. I have plans to allow exporting to HTML and maybe PDF at some undetermined point in the future. Getting there is going to require some design work and refactoring on my part to avoid something that’s impossible to maintain. My work on Organized is adhoc, uneven, and mostly done on a train, so no guarantees when that will happen.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

Sure, I'd be happy to accept a PR on this.
Organized relies on other plugins for highlighting support.  For example in Java, it relies on https://github.com/atom/language-java to do the highlighting.  To make highlighting work in organized, we need to instruct organized/atom to know that the code inside a code block is actually LaTeX code.  This amounts to mapping the latex part of
```latex
```

To something that knows the grammar of LaTeX.  To do that, modify organized.cson and copy one of the existing blocks that does this.  For example, "java.code.block.organized".  Choose a string to identify LaTeX code (latex sounds good to me) and search/replace.
The tricky part here is the part that says "source.java".  That refers to the scope name for a plugin that understands the grammar of the language you are adding.  You'll need to figure out what the scope name of your plugin is.  If you happened to use this plugin, you'd find the scope name in one of these files.  I'm going to guess you want the scope "text.tex.latex" from latex.cson, but you are the expert here - I haven't touched TeX since years started with the number 19.
You could conceivably add the ability to execute LaTeX code blocks as well.  If you are interested in that, you'd need to change codeblock.coffee.  The changes would be as follows:

If LaTeX really cares what the extensions are on files (some compilers or interpreters do), modify the execute method to put an extension on there.
Modify the executionEngine method to support LaTeX.

Good luck -- it would be fantastic to see a PR on this.


Trace return values too

Before, dllexport functions were generated like:
fn name(args) -> ret {
  trace(args);
  // ... user code
}

Now they look like:
fn name(args) -> ret {
  fn name_impl(args) -> ret {
    // ... user code
  }
  let ctx = trace_begin(args);
  let ret = name_impl(args);
  trace_return(ctx, ret);
  ret
}

The idea is to format the arguments before running the impl, in case the impl modifies them. Then the log line is printed after the impl returns and includes the return value.
One interesting consequence of this approach is that dllexport impl arguments now are actually checked for unused-ness, since they're not considered used by the trace call.  I think this is a good thing, though, and could later remove that allow when cleaning up files and renaming unused parameters to have a _ prefix.

One unsolved problem is with implementations calling other dllexport functions (for example, ReadFile
calling SetLastError), SetLastError's trace line will be printed before ReadFile's trace line. One idea is to swap it around so it looks like:
fn name(args) -> ret {
  // ... user code
}
fn name_trace(args) -> ret {
  let ctx = trace_begin(args);
  let ret = name(args);
  trace_return(ctx, ret);
  ret
}

Then builtin would call the name_trace function instead. This way we can internally call other winapi functions without creating more trace logs. I tried this originally, but it required odd changes where modules that did pub use module::InnerDllExport to do pub use module::InnerDllExport_trace, which felt wrong. So I thought I'd submit it in its current state and revisit that later if you like this idea in general.

I merged this with two small changes:

moved the allow-unused to the function scope
made the return values trace as hex, for consistency with how we print all numbers in traces


Update README.md

data uploader threw an error at unrecognised keyword parameter but does recognise parameters

This is resolved by d2feff3 as part of #812 which will shortly be merged


Release 1.0.0 alpha.5

1.0.0-alpha.5 (2021-04-07)
Added

Proteomic and Metabolomic Products can now be selected and included in an Offer
(#425 <https://github.com/qbicsoftware/offer-manager-2-portlet/pull/425>_)

Link offers to project now. The life.qbic.business.offers.Offer and life.qbic.portal .offermanager.dataresources.offers have been extended with a new property to associate it with
an existing project by its project identifier.
(#410 <https://github.com/qbicsoftware/offer-manager-2-portlet/pull/410>_).

Finalized the life.qbic.business.products.archive.ArchiveProduct and life/qbic/business/products/create/CreateProduct.groovy
use cases of the product maintenance and creation feature
(#411 <https://github.com/qbicsoftware/offer-manager-2-portlet/pull/411>_).

After a project has been created from an offer, the offer overview is updated accordingly
(#427 <https://github.com/qbicsoftware/offer-manager-2-portlet/pull/427>_)

Add the UpdatePersonView to separate the Update and Create Person use cases more consequently (#436 <https://github.com/qbicsoftware/offer-manager-2-portlet/pull/436>_)

Proteomic and Metabolomic Products are now included in the Offer PDF
(#420 <https://github.com/qbicsoftware/offer-manager-2-portlet/pull/420>_)

Fixed

Popup based Notifications are now properly centered in a liferay-environment
(#428 <https://github.com/qbicsoftware/offer-manager-2-portlet/pull/428>_)

Properly refresh the SearchPersonView after Updating a Person
(#436 <https://github.com/qbicsoftware/offer-manager-2-portlet/pull/436>_)

Products that cannot be read from the database are skipped
(#444 <https://github.com/qbicsoftware/offer-manager-2-portlet/pull/444>_)

Dependencies
Deprecated

@jenniferboedker i updated the PR text with the release changelog


Remove play core reference and implement review library instead.

- Remove play core reference and implement review library instead.
- Use gms.tasks.Task instead of play core tasks reference

Thank you for your efforts.  @Solly74


docs: wrong default value for max_cat_bytes

in bpftrace.adoc the default value for max_cat_bytes is indicated as 10000, while it is 10240
https://github.com/bpftrace/bpftrace/blob/32d12ad522e09e1e37acbca265e571a233c6d6a8/src/config.cpp#L19

i am a beginner can i take this :-)

@5AIPAVAN sure, feel free.

to fix your trouble check this solution click
maybe this will solve your problem.


Win32 update monitor handles when monitors are added or removed

On Windows, when a monitor is added or removed (or in some cases just a display setting change is made), the monitor display handle can change.
Currently GLFW does not update handles for monitors whose names remain the same after a monitor change, which results in calls to some functions which need the monitor handle, such as glfwGetMonitorWorkArea to fail.
This PR has the minimal change needed to fix this by updating the monitor handle. A larger code change could be made which would minimize the computation, but as monitor changes are infrequent and also take some time this is a decent enough and minimal solution.
This should fix issue #1676

Just a quick note to say that should a more optimal performance version be required which only calls EnumDisplayMonitors once, I would be happy to make the change - it would only add a few more lines of code.

Thank you! This has been merged as 166611cef5967313e6a3d50849e57ddbcdc33f26.
This should be sufficiently optimal until the changes land that make disconnected monitor objects more robust.


LogScale data source is not showing up on Tempo Traces to Logs

What happened:
In Grafana 9.4.9 the LogScale data source is not present in the Traces to Logs of Tempo
What you expected to happen:
It should be possible to select LogScale data source in Tempo Traces to logs. This functionality is supported from v9.4.8
How to reproduce it (as minimally and precisely as possible):

setup Grafana v9.4.9
install LogScale and Tempo Plugins
Add LogScale data source
Go to Tempo and try to select LogScale data source in the Trace to Logs section

Screenshots

Environment:

Grafana version: 9.4.9
Plugin version: the latest LogScale plugin

Closing 9.4 is no longer supported. 🙂


Partition of specialization form (named "form.spec") is not specified

This partition is mentioned twice in DeclSort::PartialSpecialization and DeclSort::Specialization sections, but is not defined anywhere in the specification.

@gdr-at-ms, @cdacamar could you, please, take a look at the issue, because it's really impossible to handle any compilated modules (like std or header unit for <iostream>) without processing class specializations.

cc @GabrielDosReis

Fixed by #98


Store drawable elements to the state

Calculating the drawable elements once per chart update and storing them in the state, this PR is improving the performance of annotations drawing.
Just a simple test by Chrome, setting 4 annotations (box) but with different drawTime.

Master
PR

@stockiNail note about the versioning; 1.2.1 will be a patch release, only fixing bug(s) in 1.2.0. So no other improvements to that release.
I'm sure you know this, but as this is the 2nd pr today you place to 1.2.1 milestone that does not really belong there, I'll explain just in case :)
So the version numbers are major.minor.patch

Matjor releases can include breaking changes + anything else
Minor releases non-breaking enhancements + anything else
Patch releases are bug fixes to that minor version.

@kurkle thank you ! Another thing to learn. I'm working differently in the other project, but no problem! And apologize!

@kurkle thank you ! Another thing to learn. I'm working differently in the other project, but no problem! And apologize!

You are probably not distributing through npm: https://docs.npmjs.com/about-semantic-versioning

The main repo got lots of negative feedback when we accidentally broke things in minor/patch releases. We had to learn the hard way 😂

@kurkle Yes, I'm not distributing by NPM because my project is not JS one.


Add Multiplex signal support. Fix big endian decoding.

Fix for #44, #45 and #13. However this change is not fully featured as when adding and removing signals to the dbc they do not properly reflect in the object (also writing the db might not show multiplexing correctly?)

@bit-dream as in my pr comment I was not able to completely finish adding proper multiplex support. Would definitely need help on dbc adding / removing and dbc writing.

@bit-dream as in my pr comment I was not able to completely finish adding proper multiplex support. Would definitely need help on dbc adding / removing and dbc writing.

That shouldn't be an issue at all. I can work on adding that functionality.

@bit-dream I removed the can and bit changes as requested.

@agent6262 I approved your pull request and merged into main. Awesome work and thanks for contributing.
I'll take a stab at implementing a more robust decode method. I'll update issue #45 so you can be in the loop when those changes get pulled in.
Additionally, if you are looking to be an active maintainer, feel free to give me a shout.


add compiler/gfortran

based on PR https://github.com/ruslo/polly/pull/162
adds the compiler/gfortran file and uses it in clang-libstdcxx
alternative to https://github.com/ruslo/polly/pull/161

rebased and updated to print a status message instead of an error message

squashed

I can't reproduce this error. I tried it with the following CMakeLists.txt file
cmake_minimum_required(VERSION 3.0)

function(polly_add_cache_flag var_name flag)
  set(spaced_string " ${${var_name}} ")
  string(FIND "${spaced_string}" " ${flag} " flag_index)
  if(NOT flag_index EQUAL -1)
    return()
  endif()
  string(COMPARE EQUAL "" "${${var_name}}" is_empty)
  if(is_empty)
    # beautify: avoid extra space at the end if var_name is empty
    set("${var_name}" "${flag}" CACHE STRING "" FORCE)
  else()
    set("${var_name}" "${flag} ${${var_name}}" CACHE STRING "" FORCE)
  endif()
endfunction()

# if this line is activated gfortran breaks
#polly_add_cache_flag(CMAKE_Fortran_FLAGS "-stdlib=libstdc++")

polly_add_cache_flag(CMAKE_CXX_FLAGS "-stdlib=libstdc++")
polly_add_cache_flag(CMAKE_EXE_LINKER_FLAGS "-stdlib=libstdc++")
polly_add_cache_flag(CMAKE_SHARED_LINKER_FLAGS "-stdlib=libstdc++")

project(example_project CXX Fortran)

This are all the flags that I could find, that libstdc++ is set. I'm only able to break the gfortran compiler if I set CMAKE_Fortran_FLAGS, which is not done by the toolchain

I can't reproduce this error

Try https://github.com/forexample/fortran-simple with polly.py --toolchain clang-libstdcxx

Try https://github.com/forexample/fortran-simple with polly.py --toolchain clang-libstdcxx

with your example AND polly I can reproduce the error. Now how do we find what the difference is between my simple example and your simple polly example?

calling cmake by hand and supplying the polly toolchain file the same /usr/bin/gfortran  -- broken error occurs
cmake -H. -B_build -DCMAKE_TOOLCHAIN_FILE=/home/gc/repos/hunter/polly/clang-libstdcxx.cmake

I think your code is not equivalent to loading flags with toolchain.
For example toolchain loaded several times in CMake's internals:

http://cgold.readthedocs.io/en/latest/tutorials/project.html#tools-discovering

Just for your info without polly.py issue reproduced by:
> rm -rf _builds
> cmake -H. -B_builds -DCMAKE_TOOLCHAIN_FILE=/.../polly/clang-libstdcxx.cmake

I recreated a toolchain file and gfortran breaks by adding the following line
polly_add_cache_flag(CMAKE_EXE_LINKER_FLAGS "-stdlib=libstdc++")

minimal toolchain-clang-gfortran.cmake File
set(CMAKE_C_COMPILER clang)
set(CMAKE_CXX_COMPILER clang++)
set(CMAKE_Fortran_COMPILER gfortran)

set(CMAKE_EXE_LINKER_FLAGS "-stdlib=libstdc++" CACHE STRING "" FORCE)

set(CMAKE_FIND_ROOT_PATH_MODE_PROGRAM NEVER)
set(CMAKE_FIND_ROOT_PATH_MODE_LIBRARY ONLY)
set(CMAKE_FIND_ROOT_PATH_MODE_INCLUDE ONLY)

breaks by adding the following line

That's the whole point of this toolchain :) Otherwise it's the same as libcxx (Clang + libc++), which is not working on Linux even for C++ projects.


Filtering is not working for nested object

Is there an existing issue for this?

[X] I have searched the existing issues

Describe the bug
Hi,
While applying filter in GQL Query,am not getting response as expected.It returns entire data as response
Expected behaviour:
It should return only data which satisifies the filter condition
Steps to reproduce
using Annotation Based - Filtering, we are generating GQL Schema.
My Schema is loading fine and I can execute queries and get response. Problem is while applying filter condition,it returns entire data as response,data is not filtered properly. Let say,this is my GQL Query with filter condition:
{
  getEquipmentLocationDetails(actionflag:"Tree"
  eqporLoc:"L",where:{
    data:{
      some:{
        EqpLocCode:{eq:"001"}
      }
    }

  }){
    data{
      Childflag
      EqpLocCode
    }
  }
}

What I am expecting is,it should return data which matched the filter condition but it returns entire data.
Also getting the same for And filter:
{
  getEquipmentLocationDetails(actionflag:"Tree"
  eqporLoc:"L",where:{
    and:[
        { data:{some:{EqpLocCode:{eq:"as"}}}}
        { data:{some:{Childflag:{eq:"0"}}}}
      ]

  }){
    data{
      Childflag
      EqpLocCode
    }
  }
}

My schema registry and EqpMetaData.cs be like :
  servicecollection.AddGraphQLServer("test")
            .AddQueryType<EqpMetaData>()
            .AddFiltering()
            .AddFiltering("data")

EqpMetaData.cs : EqpMetaData.cs.txt
sample Response with and without filtering :
Response.txt
Is any other way to apply filter? and what does "some","any" and "all" mean in filters?
Thanks !
Relevant log output
No response
Additional Context?
No response
Product
Hot Chocolate
Version
12.4.1

you apply filtering on a field that returns Response and not on the list itself.
Inject IResolverContext into you resolver and apply filtering on response.Data.Filter(context)

Hi @PascalSenn , any sample for applying filter on nested object. It may help!

This is because you try to filter on a single item instead of a list
[HotChocolate.Data.UseFiltering(typeof(FilterInputType<TheTypeOfDataProperty>)]
        public async System.Threading.Tasks.Task<Response> getEquipmentLocationDetailsAsync(IResolverContext res, string eqporLoc, string actionflag, string eqpLocCode, string eqpLocDesc, System.Threading.CancellationToken cancellationToken)
        {

                string response = ""; //some serialised response;
                var data = (JsonConvert.DeserializeObject<Response>(response));
                data.Data.Filter(res);
                return data;
        }

Using [HotChocolate.Data.UseFiltering(typeof(FilterInputType)] also not filtering data properly. So what I tried was,just added the [UseFiltering] attribute in the data field like below:
public class Response
   {
       [HotChocolate.Data.UseFiltering]
       [GraphQLName("data")]
       public EqpLocDetInfo[] Data { get; set; }

       [GraphQLName("message")]
       public string Message { get; set; }

   }

It resolved my issue and now filtering is working properly.
Thanks for your response!!


VSCode's FileDialog overwrites the file managers (Nautilus) "Show hidden files" setting

VSCode Version: 1.49.1 (and insider version as well)
OS Version: Fedora 32

Steps to Reproduce:

Enable "Show hidden files" in nautilus.
Open VSCode's file dialog (for example via Ctrl+O). The hidden files in nautilus will be hidden again.

(Not sure if this can be considered a bug report or a feature request but) VSCode should respect nautilus' setting or at least not overwrite it.

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

I see that electron provides a properties support to pass in showHiddenFiles and we do not pass it here:
https://github.com/microsoft/vscode/blob/cadabab73fef89fe0c4bfe23b5a33cd58e39ea9c/src/vs/platform/dialogs/electron-main/dialogs.ts#L95-L109
Maybe this causes the dialog to not show hidden files? Though I would think it should show them if configured by the user?

Though I would think it should show them if configured by the user?

For me VSCode's file dialog always opens with "Show hidden files" unchecked (regardless of my settings in Nautilus).

Happens also on Fedora 33, with latest VS Code:
Version: 1.51.1
Commit: e5a624b788d92b8d34d1392e4c4d9789406efe8f
Date: 2020-11-10T23:31:29.624Z
Electron: 9.3.3
Chrome: 83.0.4103.122
Node.js: 12.14.1
V8: <IP_ADDRESS>-electron.0
OS: Linux x64 5.9.10-200.fc33.x86_64

I'm having the same issue.
When I set show hidden files feature, Nautilus shows all hidden files and folders.
But when I try to open folder with Vscode, Nautilus setting overrides to not show hidden files.
You can see screenshots.

Disbled

Enabled

Open with Vscode

Vscode info
Version: 1.55.1
Commit: 08a217c4d27a02a5bcde898fd7981bda5b49391b
Date: 2021-04-07T15:01:24.315Z
Electron: 11.3.0
Chrome: 87.0.4280.141
Node.js: 12.18.3
V8: <IP_ADDRESS>-electron.0
OS: Linux x64 5.9.15-200.fc33.x86_64

OS Info
OS name: Fedora 33 (Workstation Edition)
Os Type: 64-bit
Gnome Version: 3.38.2

I'm commenting here to mention that I'm having this issue as well in order to ask if there are any updates regarding the progress of this issue.

Also having this issue, find it strange that vscode would overwrite system settings on file open

I've been experiencing the same behavior/issue for some time now.
I found a similar issue reported for ATOM but was closed due no additional information provided: https://github.com/atom/atom/issues/20712
I couldn't find any related issue on Electron repo (but, to me, seems to be the source of the behavior/issue as, all work is done by an Electron API): https://github.com/electron/electron/issues
Please, also note that when the folder is opened inside VSCode if I have a Nautilus window opened the content is refreshed (and the hidden files dissapear from the view).
Additional info:

I'm currently running on Ubuntu 20.04.3, Nautilus amd64 1:<IP_ADDRESS>-1ubuntu2 and VSCode 1.63.0.
GNome settings org.gnome.nautilus.preferences show-hidden-files - now deprecated - and org.gtk.Settings.FileChooser show-hidden could be involved on this.

Just downloaded the latest Atom version (1.58.0) and the behavior is exactly the same.  When I open a folder (project) in Atom, the Nautilus window is refreshed and the "Show hidden files" check automatically disabled.

I don't have Nautilus on my system, but I still have this bug with VSCode 1.76.0. I found a workaround. See below.
Actually, on my system, VSCode doesn't read the hidden files setting, it always open the GTK file chooser without displaying hidden files, then when the GTK file chooser is closed, it updates the setting.
Steps to reproduce:

Make hidden files displayed in the GTK file chooser:
$ dconf write /org/gtk/settings/file-chooser/show-hidden true
$ dconf read /org/gtk/settings/file-chooser/show-hidden
true

Open VSCode. Hidden files are still set to be displayed:
$ code
$ dconf read /org/gtk/settings/file-chooser/show-hidden
true

In VSCode, go to File > Open File. Hidden files are not displayed, but settings have not been updated yet:
$ dconf read /org/gtk/settings/file-chooser/show-hidden
true

Close the "Open File" popup. Even if we don't choose a file and click on "Cancel", settings were updated by VSCode:
$ dconf read /org/gtk/settings/file-chooser/show-hidden
false

Here's a workaround:

Make again hidden files displayed:
$ dconf write /org/gtk/settings/file-chooser/show-hidden true
$ dconf read /org/gtk/settings/file-chooser/show-hidden
true

Open VSCode with the following environment variable:
$ GTK_USE_PORTAL=1 code

In VSCode, go again to File > Open File. VSCode reads the setting and hidden files are now displayed in the file chooser.


Overload addition for Models to allow easy composition of submodels

Overload the add operator for Models so that submodels can be easily composed into a full model. This also allows for an easy method of adding new physics / degradation mechanisms to the models

this issue has now been changed to: modify the .update method so that it checks .ids of keys in models being combined and also combines the algebraic dict

closed by #166


A way to modify a YAML parameter before conversion ?

hello,
In the YAML, I defined in the footer an image (to specify the privacy policy).
But I want to be able to modify it according to a parameter of my asciidoc document.
Is it possible ? Either directly in the YAML, or from an extension (in an extension, I haven't found how to retrieve footer parameters).
Thank you.
Jérôme

I found a solution by modifying the converter.rb but is really the best way ?
    if !(doc.attr 'confidentiality').nil?
        if (doc.attr 'confidentiality')==''
            doc.set_attr 'confidentiality', 'public'
        end

        @theme.footer_recto_left_content = "image:#{doc.attr 'commonresourcesdir'}/icons/confidential/#{doc.attr 'confidentiality'}.png[privacy, align=left]"
        @theme.footer_verso_right_content = @theme.footer_recto_left_content
    end

Shall we update the title to make this more specific?

Yes, you can update the title.
The ideal would be to be able to use an attribute defined in the asciidoc document to specify the path of the image and to use it in the YAML like this : content:   image:{image-attribute}
But the path to the image should be resolved from the document directory but not from the theme directory (Certainly the most difficult point).

Btw, the Asciidoctor API now accepts the resolved theme via the pdf_theme option. So it's possible to read the theme in yourself, manipulated it as you see fit, then pass it to Asciidoctor (PDF). You can see tons of examples of this in the test suite since that's how all the theme overrides in the test suite are handled.

Here's a method you can use (from the test suite) to build on an existing theme:
def build_pdf_theme overrides = {}, extends = nil
  (Asciidoctor::PDF::ThemeLoader.load_theme extends).tap {|theme| overrides.each {|k, v| theme[k] = v } }
end

You can then pass the result to the pdf_theme option of the Asciidoctor load or convert APIs.
Given that this is now possible, I'm going to close this issue.


Use proper escaping in npmrc.md

@ramiMSFT

Can you review this PR?
IMPORTANT: When this content is ready to merge, you must add #sign-off in a comment or the approval may get overlooked.

#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

Windows tab section should be updated. This change will not be relevant. Thank you!


Minor: rename GetFieldAccessCharacteristic and add docs

Which issue does this PR close?
Related to https://github.com/apache/arrow-datafusion/issues/7193
Follows https://github.com/apache/arrow-datafusion/pull/7215 from @izveigor
Rationale for this change
In order to have a good experience accessing fields, it should be easy to use the code that manipulates them
What changes are included in this PR?

Rename GetFieldAccessCharacteristic to GetFieldAccessSchema to better reflect what it does
move the calculation into  GetFieldAccessSchema::get_accessed_field
Reduce duplication

Are these changes tested?
Covered by existing tests

Are there any user-facing changes?
No, these are unreleased APIs (added in https://github.com/apache/arrow-datafusion/pull/7215)

CI is failing due to https://github.com/apache/arrow-datafusion/issues/7221


GUI loading params from hdf5

Add support for loading connectivity and drive parameters from a hdf5 file.
Input buttons

Load connection

hdf5 only
Only loads connection information from hdf5 file

Load drives

hdf5 only
Only loads drive information from hdf5 file

Should incorporate planned deprecation of param files.
To Do:

[ ] Load local connectivity button support for hdf5
[ ] Load external drives button support for hdf5
[ ] Param file deprecation warning

Closed because hdf5 files are too large for this purpose. Continuing work in #756 instead.


multilib support for library installation

small patch to support multilib, like lib64:
--- CMakeLists.txt
+++ CMakeLists.txt
@@ -91,11 +91,11 @@
Exec Install Locations
set (BINDIR   "${CMAKE_INSTALL_PREFIX}/bin")
-set (LIBDIR   "${CMAKE_INSTALL_PREFIX}/lib")
+set (LIBDIR   "${CMAKE_INSTALL_PREFIX}/lib${LIB_SUFFIX}")
set (PYLIBDIR "${CMAKE_INSTALL_PREFIX}/python")
if (EXEC_INSTALL_PREFIX)
set (BINDIR   "${EXEC_INSTALL_PREFIX}/bin")

set (LIBDIR   "${EXEC_INSTALL_PREFIX}/lib")
set (LIBDIR   "${EXEC_INSTALL_PREFIX}/lib${LIB_SUFFIX}")
set (PYLIBDIR "${EXEC_INSTALL_PREFIX}/python")
endif ()

Closing. This slipped through the cracks somehow, and in years nobody has asked for it. The cmake files have change too much for a direct merge. I trust that if this is important, someone will ask for it again.


feat: use latest binary if plugin version is not specified

Added

Download the latest version of binary if plugin version is not specified
Log plugin binary version

Codecov Report

Merging #49 (f99aee4) into master (6c86c07) will not change coverage.
The diff coverage is 0.00%.

@@           Coverage Diff           @@
##           master      #49   +/-   ##
=======================================
  Coverage   79.56%   79.56%
=======================================
  Files           4        4
  Lines         137      137
=======================================
  Hits          109      109
  Misses         22       22
  Partials        6        6

Impacted Files
Coverage Δ

main.go
0.00% <0.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 6c86c07...f99aee4. Read the comment docs.

@all-contributors please add @adikari for code, example, doc, maintenance, review, test, infra


tabBarVisible: false on react-navigation-stack

I used the tabBarVisible: false  on the react-navigation-stack, but it doesn't work
import { createStackNavigator } from 'react-navigation-stack';

const MainStack = createStackNavigator({
    HomeScreen: {
        screen: HomeScreen,
        navigationOptions: () => ({
            header: null
        }),
    },
    MakeupArea: {
        screen: MakeupArea,
        navigationOptions: ({ navigation }) => ({
            tabBarVisible: false
        })
    },
    SceenBarcodeFN: {
        screen: SceenBarcodeFN,
        navigationOptions: ({ navigation }) => ({
            header: null,
            tabBarVisible: false
        })
    }
}, {
    initialRouteName: 'HomeScreen'
})
MainStack.navigationOptions = ({ navigation }) => {
    if (navigation.state.index == 0) {
        return {
            tabBarVisible: true
        };
    }
    return {
        tabBarVisible: false
    };
};
export default createAppContainer(MainStack);

@Ahmad31 there is no tabBarVisible on navigation stack:
https://reactnavigation.org/docs/en/stack-navigator.html
Are you trying to hide the tab bar from a bottom navigation? https://reactnavigation.org/docs/en/bottom-tab-navigator.html#tabbarvisible
I suggest you to use:
 stack ->
   bottomNavigator:
      -> bottomRouteOne
      -> bottomRouteTwo
   routeThatDontHaveBottomOne
   routeThatDontHaveBottomTwo

That way the stack will open those routes above the bottom tab and 'hide' it.
But if you need to hide the bottom tab bar anyway you will need to configure on the tab navigationOptions definition not on the stack.
btw: I'm not a maintainer :P I just happen to have time to try to help.

https://reactnavigation.org/docs/en/navigation-options-resolution.html

const AppNavigator = createBottomTabNavigator({
HomeScreen: {
screen:  HomeScreen
},
MakeupArea: {
screen: MakeupArea
},
SceenBarcodeFN: {
screen:  SceenBarcodeFN
  }

},
{
defaultNavigationOptions: {
header: null
}
})