Temporary fix for String, Int32 and Bool on the Hololens2

The issue was on Unity Editor, String, Int32 and Bool were being properly subscribed to on RosBridge however, after deploying onto the Hololens2 (through appx package on the web server) the Unity Application on the Hololene2 would no longer subscribe to those topics i.e. not appearing on RosBrdige. Redefining the types String, Int32 and Bool in RosSharpMessages appears tohave fixed this. However, it doesn't fix the problem completly (thus temporary fix); but its working. It maybe a problem with importing on the Hololens2
Also wrote some example subscribers for these messages in scripts.
Also a small fix for differentiating colors in spherelist and cubelist

Hi,
Have you tried to be explicit in declaring parameter type when using Bool (MessageTypes.Std.Bool instead of just Bool)?

Yeah, but still had the issue though

Instead of undoing your additions in
with extra commits, it'll be better to just force push changes to the original commits with the corrections


[CP] Turn websocket's handshake timeout down again.

As per title. This impacts upgradeability. See https://github.com/knative/serving/issues/6197 for more details.

/assign mattmoor


Update GreetingController.java

@chanmi910: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

pr
1255f77c288689200017df65add844e4b1ea0562
link
/test pr

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the jenkins-x/lighthouse repository. I understand the commands that are listed here.


Apply cleanups and refactorings for #482.

This simplifies the overall implementation, reduces API footprints and better exposes dependences coming from def-use traversal requirements directly in the API.

Landing now, will address comments in followups


Game Demos crashing after title screen

I don't have much details about the crash, however downloading a snapshot of the repo, placing it in the c:\raylib\raylib directory, then compiling the demo games "Skully Escape" and "Light My Ritual". They compile just fine using MinGW + MSYS. Once running, the raylib animation plays then the splash for the game loads, then it crashes, with no errors or debug output.
any suggestions?

Hi @tazdij, just been working on raylib games some days ago and everything was fine.
Just tested "Skully Escape" and "Light My Ritual" right now and they work. Are you using latest raylib develop branch?

I am using master branch. Maybe it has something to do with the version of
MinGW I am using?
I will do some more fiddling around with it and see if I can get the game
to run past the splash.
Thanks for verifying the demo games have not been left to ruins while the
main library is developed; as so many demos are with many other software
projects.
On May 10, 2017 12:42 AM, "Ray"<EMAIL_ADDRESS>wrote:

Hi @tazdij https://github.com/tazdij, just been working on raylib games
some days ago and everything was fine.
Just tested "Skully Escape" and "Light My Ritual" right now and they work.
Are you using latest raylib develop branch?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/raysan5/raylib/issues/283#issuecomment-300402030, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ABOqF8w19MkfFS6Z5N5uzgfcSBfVQoFxks5r4WpIgaJpZM4NWCmP
.

Just for reference, I used MinGW32 with GCC 5.3.0 on Windows 10 Pro, no MSYS, compiled using:
mingw32-make PLATFORM=PLATFORM_DESKTOP -B

Actually I used Notepad++ provided script: raylib_makefile
About "Wave Collector", it is broken but it's a known error, I'm working on it (needs some redesign to also work on web).

Thanks for verifying the demo games have not been left to ruins while the
main library is developed; as so many demos are with many other software
projects.

raylib is primary intended for education so I try to care for examples and sample games (completely review for upcoming raylib v1.7). :)

Alright Just checked all of my toolchain and I am running MinGW GCC 4.8.1 and I have tried as follows:
MinGW + MSYS: (Which I think links in cygwin or something like that, I don't really know)
make PLATFORM=PLATFORM_DESKTOP -B
This creates an exe with zero errors at compile time, however it crashes at the title screen.
MinGW32: (Run from a windows PowerShell or Command Prompt)
mingw32-make PLATFORM=PLATFORM_DESKTOP -B
Same outcome as MinGW + MSYS
Finally I created a VisualStudio project for the game and added it to the raylib vs2015 solution. This worked. The game compiled and runs. This leads me to believe that the issue is actually in the MinGW GCC 4.8.1 compiler I was using or possibly the stdlibc or libc which is bundled with that version.
When I get a chance to upgrade to GCC 5.3.0 I will try this all again, and see if the game still crashes.
Thank you for your help and the great library.

Thanks for the report! :)

Alright, I think I figured it out.
Looks like static libraries compiled with certain versions of GCC are incompatible with certain other versions og GCC. Since the static library is pre-compiled (I assume with 5.3.0) in the release folder, I had not compiled it with my current version of GCC (4.8.1)
By going to the src directory and running make, recompiling libraylib.a, I was able to get the games to run correctly
I tested this with both MinGW32 + MSYS & just MinGW32 via mingw32-make and both worked.

Hey @tazdij! Good catch!
Just note that provided OpenAL Soft static version has also been compiled with GCC 5.3.0.

I really am not trying to drag this conversation on, but would like to respond to the OpenAL comment.

Just note that provided OpenAL Soft static version has also been compiled with GCC 5.3.0.

This shouldn't matter since OpenAL is dynamically linked. If we were to create a dll/so/dylib version of libraylib.a, the version of GCC used by the developer of either the game or raylib will no longer be as consequential.
Or might I suggest a possible solution? Not to store libraylib.a in the repo, and include it in the Makefiles for the games and examples. Allowing the developer's toolchain to build the static library the first time the developer runs make.


Allow page to change private page options

Is your proposal related to a problem?

I would like to be able to disable private pages or limit the types of private pages for specific page models. I sometimes like to disable being able to change the privacy of the child pages and control the privacy from the parent page. There are other occasions as well where I would like to only allow the page's privacy to be switched to specific groups and disable the password and logged-in users. While there is in the latest version a global setting to disable the shared password option, I would like to sometimes only disable the shared password for specific page models.
Describe the solution you'd like

I would like the page model to have a property and/or a method to allow overriding the default private page permissions or a flag to disable private pages.
 class BlogPage(Page):
     private_page = ["logged_in", "shared_password", "user_groups"]

    def get_private_page(self):
       return self.private_page

    # or
   disable_private_pages = True

   def get_disable_private_pages(self):
       return self.disable_private_pages

Describe alternatives you've considered

I looked through the documentation and could not find a simple way to do this. I asked how to do this on the wagtail slack and the suggestion I got was to see if it is possible to do this with wagtail permissions or add a signal for page save. I didn't look into these options so much, but it seems a bit more complex than what I would like.
Working on this

I would be happy to work on this myself once the issue is accepted, but I am not very familiar with how the page editor part of wagtail is developed and what skills would be needed. Is this part made with react or something else?
Anyone can contribute to this. View our contributing guidelines, add a comment to the issue once you’re ready to start.

Merged in https://github.com/wagtail/wagtail/commit/95eac5ab7801a624451ce53fe0eb94763d07bb9e

As an extension to this it would be nice if you could programmatically require the page to be private. Right now I can as a page allow certain kinds of private but "public" is still always an option. It would be nice to be able to never allow a page to be public.

@PureTryOut I was thinking about that as well, as it would be useful for some of my projects. I think it would be best if it was a separate issue for that.

@PureTryOut Before requiring a page to be private work would need to be done to allow setting the default page privacy #3708. Without that removing public as an option would be relatively easy, but it would not stop the page from being public by default. So on page creation you would still have to set the page to private using page hooks.


[WFCORE-65][WFCORE-632] Use an 'owner' attribute to determine if a scanner controls a deployment

Core - Full Integration Build 745 is now running using a merge of 5b78d6f5005e3c7397efa9e1a192bb879468a09c

Windows Build 1143 is now running using a merge of 5b78d6f5005e3c7397efa9e1a192bb879468a09c

Linux Build 1487 is now running using a merge of 5b78d6f5005e3c7397efa9e1a192bb879468a09c

Linux Build 1487 outcome was SUCCESS using a merge of 5b78d6f5005e3c7397efa9e1a192bb879468a09c
Summary: Tests passed: 3083, ignored: 66 Build time: 0:20:25

Windows Build 1143 outcome was FAILURE using a merge of 5b78d6f5005e3c7397efa9e1a192bb879468a09c
Summary: Tests failed: 1 (1 new), passed: 3082, ignored: 66 Build time: 0:21:44
Build problems:
Failed tests detected
Failed tests
org.jboss.as.test.integration.domain.SSLMasterSlaveOneWayTestCase.testReadSlaveStatusFromMaster: <no details avaliable>

Core - Full Integration Build 745 outcome was SUCCESS using a merge of 5b78d6f5005e3c7397efa9e1a192bb879468a09c
Summary: Tests passed: 2838, ignored: 416 Build time: 0:53:15

Core - Full Integration Build 763 is now running using a merge of 62335bd1f2bc49a33204cf14232feb907189bb07

Linux Build 1507 is now running using a merge of 62335bd1f2bc49a33204cf14232feb907189bb07

Windows Build 1162 is now running using a merge of 62335bd1f2bc49a33204cf14232feb907189bb07

Linux Build 1507 outcome was SUCCESS using a merge of 62335bd1f2bc49a33204cf14232feb907189bb07
Summary: Tests passed: 3083, ignored: 66 Build time: 0:19:37

Windows Build 1162 outcome was SUCCESS using a merge of 62335bd1f2bc49a33204cf14232feb907189bb07
Summary: Tests passed: 3083, ignored: 66 Build time: 0:20:23

Core - Full Integration Build 763 outcome was SUCCESS using a merge of 62335bd1f2bc49a33204cf14232feb907189bb07
Summary: Tests passed: 2842, ignored: 416 Build time: 0:52:56

Reviewed by Emmanuel (thanks!)


Replace Slack with Discord

Description

feature Discord as the main comms channel across all django CMS documentation

Checklist

[x] I have opened this pull request against develop-4
[ ] I have added or modified the tests when changing logic
[ ] I have followed the conventional commits guidelines to add meaningful information into the changelog
[ ] I have read the contribution guidelines  and I have joined #workgroup-pr-review on Slack to find a “pr review buddy” who is going to review my pull request.

@macolo @marksweb I have replaced all discord links by https://www.django-cms.org/discord we can manage all redirects there then. For now, this redirects to https://discord.com/channels/800813886689247262/1201999613272535130 which to my understanding is a permanent link. If not, we only need to change the redirect.


DynamicGroup Server Error when Region set

Environment

Nautobot version (Docker tag too if applicable): 1.4.8 1.4.9 1.5.0
Python version: 3.8
Database platform, version: postgres
Middleware(s):

Steps to Reproduce

Create dynamic group
Add a region as filter
save

Can be replicated on demo.nautobot.com and next.demo.nautobot.com

Expected Behavior
FIlter by region

Observed Behavior
500 Server Error, Device has no field named 'site__region'

Confirmed. Thanks. This looks related to #2695. No good deed goes unpunished.


Changes from Leapsight project

Includes change:

Returns pid() from enforce_once/3 in order to be able to kill the process.

This change seems to break existing tests.  Are you sure it's safe?

This change seems to break existing tests.  Are you sure it's safe?

Hi Christopher,
You are right, some tests need to be updated because of the change in
return value of enforce_once/3. I searched through the lasp code base and
didn't find any internal use of the function, so it's safe from lasp's
point of view, but lasp users may need to update their code to align with
the changes. Please let us get back to you with proposed test code updates
next week!
Thanks and regards,
Gergely
On Sat, 9 Jan 2021 at 05:44, Christopher S. Meiklejohn <
<EMAIL_ADDRESS>wrote:

This change seems to break existing tests. Are you sure it's safe?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/lasp-lang/lasp/pull/314#issuecomment-757095482, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AELVKAF7LGJZFAKSE66AW4LSY7NJ3ANCNFSM4V2NQPFQ
.

--
Code BEAM STO
https://www2.codesync.global/code-sync/code-beam-sto-2021: 27-28 May 2021
Erlang Solutions cares about your data and privacy; please find all
details about the basis for communicating with you and the way we process
your data in our Privacy Policy
https://www.erlang-solutions.com/privacy-policy.html. You can update your
email preferences or opt-out from receiving Marketing emails here
https://www2.erlang-solutions.com/email-preference?epc_hash=JtO6C7Q2rJwCdZxBx3Ad8jI2D4TJum7XcUWcgfjZ8YY.

Hi Christopher,
You are right, some tests need to be updated because of the change in
return value of enforce_once/3. I searched through the lasp code base and
didn't find any internal use of the function, so it's safe from lasp's
point of view, but lasp users may need to update their code to align with
the changes. Please let us get back to you with proposed test code updates
next week!
Thanks and regards,
Gergely
On Sat, 9 Jan 2021 at 05:44, Christopher S. Meiklejohn <
<EMAIL_ADDRESS>wrote:

This change seems to break existing tests. Are you sure it's safe?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/lasp-lang/lasp/pull/314#issuecomment-757095482, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AELVKAF7LGJZFAKSE66AW4LSY7NJ3ANCNFSM4V2NQPFQ
.

--
Code BEAM STO
https://www2.codesync.global/code-sync/code-beam-sto-2021: 27-28 May 2021
Erlang Solutions cares about your data and privacy; please find all
details about the basis for communicating with you and the way we process
your data in our Privacy Policy
https://www.erlang-solutions.com/privacy-policy.html. You can update your
email preferences or opt-out from receiving Marketing emails here
https://www2.erlang-solutions.com/email-preference?epc_hash=JtO6C7Q2rJwCdZxBx3Ad8jI2D4TJum7XcUWcgfjZ8YY.

There are a couple of calls to enforce_one on common test suite:
https://github.com/lasp-lang/lasp/blob/56f7c1d4c4ac20b2ebd43f5b7259dfc44e7e72d8/test/lasp_SUITE.erl#L1083

There are a couple of calls to enforce_one on common test suite:
https://github.com/lasp-lang/lasp/blob/56f7c1d4c4ac20b2ebd43f5b7259dfc44e7e72d8/test/lasp_SUITE.erl#L1083

Hi Christopher,
I've just pushed CT updates that passed the CI, please have a look!
Thanks,
Gergely

Hi Christopher,
I've just pushed CT updates that passed the CI, please have a look!
Thanks,
Gergely

Looks good.  Can you just explain the motivation for the change?  It's not clear at all from the pull request that you submitted.

Looks good.  Can you just explain the motivation for the change?  It's not clear at all from the pull request that you submitted.

Erleans uses the enforce_once processes for continuously checking if a grain with a specific grain reference has multiple activations (duplicates) in the cluster and for terminating these duplicates. Unfortunately during grain deactivation, the enforce_once process is not killed and at the time of re-activation, a new enforce_once process is started leading to increasing number of processes with no limit. Currently in our fork, we're using the process id returned by enforce_once to kill these guard processes.

Erleans uses the enforce_once processes for continuously checking if a grain with a specific grain reference has multiple activations (duplicates) in the cluster and for terminating these duplicates. Unfortunately during grain deactivation, the enforce_once process is not killed and at the time of re-activation, a new enforce_once process is started leading to increasing number of processes with no limit. Currently in our fork, we're using the process id returned by enforce_once to kill these guard processes.

OK, sounds good.  Might be worth considering an enforce_once_link in the future, where it auto-links and removes if the calling process dies.

OK, sounds good.  Might be worth considering an enforce_once_link in the future, where it auto-links and removes if the calling process dies.


[manif] Add new port

If this PR adds a new port, please uncomment and fill out this checklist:

[x] Changes comply with the maintainer guide
[x] The name of the port matches an existing name for this component on https://repology.org/ if possible, and/or is strongly associated with that component on search engines.
[x] Optional dependencies are resolved in exactly one way. For example, if the component is built with CMake, all find_package calls are REQUIRED, are satisfied by vcpkg.json's declared dependencies, or disabled with CMAKE_DISABLE_FIND_PACKAGE_Xxx
[x] The versioning scheme in vcpkg.json matches what upstream says.
[x] The license declaration in vcpkg.json matches what upstream says.
[x] The installed as the "copyright" file matches what upstream says.
[x] The source code of the component installed comes from an authoritative source.
[x] The generated "usage text" is accurate. See adding-usage for context.
[x] The version database is fixed by rerunning ./vcpkg x-add-version --all and committing the result.
[x] Only one version is in the new port's versions file.
[x] Only one version is added to each modified port's versions file.

Usage test pass on x64-windows.

Note: I will be converting your PR to draft status. When you respond, please revert to "ready for review". That way, I can be aware that you've responded since you can't modify the tags.

@unageek  Please re-run vcpkg x-add-version to update the git-tree.

Thanks for the new port!


Update vscode-extension-telemetry

This module is important to keep up to date as new version often bring better cleaning and new features which keep the python extension aligned with VS Code core. This particular update sees a bug that caused large CPU usage fixed.
Closes #18242

It looks like the NPM package shipped a minimized JS file which is breaking Webpack.

Could this have been caused by bumping to Node LTS?

Looking at the error message (ERROR in ./node_modules/vscode-extension-telemetry/lib/telemetryReporter.web.min.js 8:55451), it seems like the failing code is the e part in there: return{logEvent:(n,i)=>{e?.trackEvent({name:n}. I would guess that we don't support optional chaining.

Thanks! That did it!


ReactNative app craches on Android 11 device with targetSdkVersion 30

Description
ReactNative app crashes on Android 11 device with targetSdkVersion 30.
React Native version:
react-native info output:
System:
OS: macOS 10.15.7
CPU: (12) x64 Intel(R) Core(TM) i7-9750H CPU @ 2.60GHz
Memory: 209.25 MB / 16.00 GB
Shell: 3.2.57 - /bin/bash
Binaries:
Node: 10.16.3 - /usr/local/bin/node
Yarn: 1.17.3 - /usr/local/bin/yarn
npm: 6.9.0 - /usr/local/bin/npm
Watchman: 4.9.0 - /usr/local/bin/watchman
Managers:
CocoaPods: 1.10.0 - /usr/local/bin/pod
SDKs:
iOS SDK:
Platforms: iOS 13.2, DriverKit 19.0, macOS 10.15, tvOS 13.2, watchOS 6.1
Android SDK:
API Levels: 23, 25, 26, 27, 28, 29, 30
Build Tools: 26.0.2, 27.0.3, 28.0.0, 28.0.3, 29.0.0, 29.0.2, 30.0.0, 30.0.1
System Images: android-26 | Google Play Intel x86 Atom, android-29 | Google Play Intel x86 Atom, android-30 | Google APIs Intel x86 Atom, android-30 | Google APIs Intel x86 Atom_64, android-30 | Google Play Intel x86 Atom, android-30 | Google Play Intel x86 Atom_64
Android NDK: 21.3.6528147
IDEs:
Android Studio: 4.1 AI-201.87<IP_ADDRESS>58069
Xcode: 11.2.1/11B500 - /usr/bin/xcodebuild
Languages:
Java: 1.8.0_211 - /usr/bin/javac
Python: 2.7.16 - /usr/bin/python
npmPackages:
@react-native-community/cli: Not Found
react: 16.13.1 => 16.13.1
react-native: 0.63.2 => 0.63.2
react-native-macos: Not Found
npmGlobalPackages:
react-native: Not Found
[Updated] Steps To Reproduce

Connect Android 11 device or create Android 11 emulator
$ react-native init MyApp --version 0.63.2
Update targetSdkVersion and compileSdkVersion to be 30 in build.gradle
Open new terminal window and do: $ cd MyApp && react-native start --port 8082
In previous terminal window do: $ cd MyApp && react-native run-android --port 8082

Actual Results
Exception in native call
java.lang.RuntimeException: Unable to load script. Make sure you're either running a Metro server (run 'react-native start') or that your bundle 'index.android.bundle' is packaged correctly for release.
at com.facebook.react.bridge.CatalystInstanceImpl.jniLoadScriptFromAssets(Native Method)
at com.facebook.react.bridge.CatalystInstanceImpl.loadScriptFromAssets(CatalystInstanceImpl.java:234)
at com.facebook.react.bridge.JSBundleLoader$1.loadScript(JSBundleLoader.java:29)
at com.facebook.react.bridge.CatalystInstanceImpl.runJSBundle(CatalystInstanceImpl.java:258)
at com.facebook.react.ReactInstanceManager.createReactContext(ReactInstanceManager.java:1293)
at com.facebook.react.ReactInstanceManager.access$1100(ReactInstanceManager.java:131)
at com.facebook.react.ReactInstanceManager$5.run(ReactInstanceManager.java:1016)
at java.lang.Thread.run(Thread.java:923)
Expected Results
App should build and run successfully on Android 11 device/emulator with targetSdkVersion 30

Make sure that you run ‘react-native start’

Make sure that you run ‘react-native start’

I did run ‘react-native start’, the issue is still there.

Some dependencies, like OkHTTP3, crashing when targetSdkVersion is 29 or above, please don't change this. 0.63.4 and 0.64 bumped all dependencies to latest ones.

Getting this issue on RN version 0.62.2 as well

I have similar error for<EMAIL_ADDRESS>I set only targetSdkVersion on 29 and solved my problem.
Notice that I don't change compileSdkVersion, that's stills in 30

Why is it closed changing targetSdkVersion back to 29 is not a permanent fix, It is mandatory to update targetSdkVersion to 30 before November for existing apps and before August for new apps

Any updates on that? As far as I know Google will require targetSDKVersion = 30 starting from November 2021.

The crash fixed for me on updating sentry/react-native library, please check your dependencies support targetsdkversion 30

🔥🔥🔥
Finally 🦾 fixed by help form 💻 stack-overflow

The crash fixed for me on updating sentry/react-native library, please check your dependencies support targetsdkversion 30

It works for me 💯 💯 💯 💯 💯

@girish54321  where did you add the lines?
implementation("com.squareup.okhttp3:okhttp:4.9.1")
implementation("com.squareup.okhttp3:okhttp-urlconnection:4.9.1") ?

@carefreeav09
At /projectName/android/app/build.gradle
Under dependencies
dependencies {
      //------------

    implementation("com.squareup.okhttp3:okhttp:4.9.1")
    implementation("com.squareup.okhttp3:okhttp-urlconnection:4.9.1")

  //--------
}

@carefreeav09
implementation("com.squareup.okhttp3:okhttp:4.9.1")
implementation("com.squareup.okhttp3:okhttp-urlconnection:4.9.1")

Did it work for you?
I added this but still crashing.

The crash fixed for me on updating sentry/react-native library, please check your dependencies support targetsdkversion 30

It work's for me!
My sentry package is now: "@sentry/react-native": "^2.0.0"
And followed to migration guide from their docs. https://docs.sentry.io/platforms/react-native/migration/#from-1x-to-2x

@ErickMaeda What version of react-native?

@ErickMaeda What version of react-native?

@ashishprasad2163
"react-native": "0.59.10"

@ErickMaeda  Ok Thanks😊. I upgraded sentry to 2.0.0. Tried @carefreeav09's solution. Upgraded clever tap also. Still, the app is crashing on android 11 devices without any error and working fine on android 9 and below devices.
I'm new to mobile development. Please suggest some way to debug it. I'm on "react-native": "^0.60.5"

@ashishprasad2163 Try running the release build with logcat you can find the package that's causing the issue

Create an APK and  install it on a device
connect the device with USB
Run adb logcat to see logs (better if you do it from Android Studio)
Now open app on your device and notice crash logs

@manohar-octifi Thanks for sharing the steps.
I did as you said and got this. Is this useful?
I was searching this on StackOverflow and GitHub, maybe something is wrong with the webview package. Not sure.
--------- beginning of crash
2021-11-19 02:29:35.780 20128-20221/? A/libc: Fatal signal 11 (SIGSEGV), code 2 (SEGV_ACCERR), fault addr 0x728afff000 in tid 20221 (mqt_js), pid 20128 (angle.traveller)
2021-11-19 02:29:35.802 726-726/? E/qdmetadata: paramType 2048 not supported
2021-11-19 02:29:35.817 726-726/? E/qdmetadata: paramType 2048 not supported
2021-11-19 02:29:35.821 726-726/? E/qdmetadata: paramType 2048 not supported
2021-11-19 02:29:35.826 726-726/? E/qdmetadata: paramType 2048 not supported
2021-11-19 02:29:35.843 726-726/? E/qdmetadata: paramType 2048 not supported
2021-11-19 02:29:35.853 726-726/? E/qdmetadata: paramType 2048 not supported
2021-11-19 02:29:35.874 726-726/? E/qdmetadata: paramType 2048 not supported
2021-11-19 02:29:35.891 726-726/? E/qdmetadata: paramType 2048 not supported
2021-11-19 02:29:35.901 726-726/? E/qdmetadata: paramType 2048 not supported
2021-11-19 02:29:35.921 20235-20235/?  A/DEBUG: pid: 20128, tid: 20221, name: mqt_js  >>> com.traveltriangle.traveller <<<
2021-11-19 02:29:35.922 20235-20235/? A/DEBUG: uid: 10205
2021-11-19 02:29:35.922 20235-20235/? A/DEBUG: signal 11 (SIGSEGV), code 2 (SEGV_ACCERR), fault addr 0x728afff000
2021-11-19 02:29:35.922 20235-20235/? A/DEBUG:     x0  000000728ba1c6d0  x1  000000728afff000  x2<PHONE_NUMBER>000000  x3  000000728b124c90
2021-11-19 02:29:35.922 20235-20235/? A/DEBUG:     x4  000000728b42c960  x5  000000728b124d00  x6  fff9000000000000  x7  fff9000000000000
2021-11-19 02:29:35.922 20235-20235/? A/DEBUG:     x8<PHONE_NUMBER>382ca4  x9  ffff000000000000  x10 000000728b400000  x11 000000728b42c8a8
2021-11-19 02:29:35.922 20235-20235/? A/DEBUG:     x12 fff9000000000000  x13 fff9000000000000  x14<PHONE_NUMBER>000000  x15<PHONE_NUMBER>01ffff
2021-11-19 02:29:35.922 20235-20235/? A/DEBUG:     x16<PHONE_NUMBER>4b9718  x17 000000760facf400  x18<PHONE_NUMBER>000038  x19 000000728ba1c6d0
2021-11-19 02:29:35.922 20235-20235/? A/DEBUG:     x20 b40000745ea84af0  x21 b40000745ea84850  x22<PHONE_NUMBER>000000  x23 000000728afff000
2021-11-19 02:29:35.922 20235-20235/? A/DEBUG:     x24 000000728ba1f000  x25 b40000728affe550  x26<PHONE_NUMBER>000000  x27 b40000745ea84d50
2021-11-19 02:29:35.922 20235-20235/? A/DEBUG:     x28<PHONE_NUMBER>000000  x29 000000728ba1c630
2021-11-19 02:29:35.922 20235-20235/? A/DEBUG:     lr<PHONE_NUMBER>343f78  sp  000000728ba1c5b0  pc<PHONE_NUMBER>382ca4  pst 00000000a0000000

None of the above suggestions worked for me. As in your case, my app, using targetSdkVersion 30, is running properly on android 7 and 8 but is crashing on android 11.
Does anybody have another idea?


Add skip to content button

Is your feature request related to a problem? Please describe.
We need a button for keyboard users to skip the nav bar, however short it may be.
Describe the solution you'd like
Like YouTube does it, show the button on tab focus.
Describe alternatives you've considered
NA
Additional context
NA

I would like to work on this project.

Hiii, @Marvin-Brouwer  I made a PR on this project

@shindodkar I see, I'm not sure you understand what this issue is about from what I see in your pr.
I'll have a better look this weekend but I'm pretty busy tbh.
I might make a discord channel so we can have a screen sharing session when it's convenient

@shindodkar, sorry I had quite the busy weekend.
I'll get to it ASAP next week in the evening somewhere

@shindodkar Sorry for taking so long, I had quite the week.

Since you'd like to help out I'm going to assign this issue to you. However, I strongly urge you to have a read through the Contribution guide and the Contributor covenant code of conduct.
I spent quite some time working out the Contribution guide to make reviewing contributions as efficient as possible, plus I'd like your feedback.
Now, about the Pull request.
In extension of reading the contribution guidelines, I noticed you didn't really read the PR template, or maybe misunderstood.
I'd like you to reference the issue you're fixing in the heading, you can see an example here:
https://github.com/Marvin-Brouwer/five-dice/pull/70
I also noticed, you committed your changes to the main branch. This means it's not very easy for me to see which issue your changes relate to, there's a part in the Contribution guide explaining how to name your branches.
Not only is it easier for me, it's also smart for you to branch your work, and name it appropriately.
It'll allow you to switch between work when you're waiting for a PR and you'd like to pickup another issue in the mean time for example. It'll also help you remember what you were doing if you've left the project for a while. And finally, it's common practice in software development. So if you're thinking of a future in development, it's best to get used to it already.
Lastly, your change.
I had a look at your change, and I'm pretty sure you misunderstood what I meant with "skip to content" it appears to me that you've created a "Skip adds button" like YouTube, but this app doesn't have any adds. And Honestly, I don't think it needs it.
So then what did I mean? I'm talking about accessibility features.
If you tab through YouTubes UI without using the mouse you'll see this button pop up:

Clicking this button, means you'll skip the navigation items, and go right into the contents of the page.
Here's a good video on what it is, and, why every site should have one: https://www.youtube.com/watch?v=jDDaOFr9nqQ.
I'm going to close the PR since it's not the change I was looking for. However, I am going to assign this issue to you and I'd like you to try again with this additional information.
A little implementation tip:
There's already a tabbable element for scrolling to the top of the page here:
https://github.com/Marvin-Brouwer/five-dice/blob/main/src/app/src/layouts/content.astro#L18
You can reuse that to skip to.
The layout for the game itself doesn't contain this item:
https://github.com/Marvin-Brouwer/five-dice/blob/main/src/app/src/layouts/in-game.astro
However, I don't recommend putting it in here.
I recommend removing it from the content.astro and placing it just above here:
https://github.com/Marvin-Brouwer/five-dice/blob/main/src/app/src/layouts/main.astro#L66
This means every page has this element now, and you can just assume it's there from the header component.
I haven't really given it a lot of thought whether this button should be in the header itself or in the navbar, maybe you can get some inspiration on how YouTube did it, or maybe from the video.
When you have questions while developing, please feel free to ask questions in this issue.
I'll try to answer them ASAP.
Good luck and again thanks for wanting to help!

I just noticed GitHub also has one:


[Bug]: ngModel & disabled not a known property of 'ngx-editor'

What happened?
I have scaffolded a basic Angular 13 app and added ngx-editor as described. When I try and build the project I get:
Can't bind to 'ngModel' since it isn't a known property of 'ngx-editor'.

If 'ngx-editor' is an Angular component and it has 'ngModel' input, then verify that it is part of this module.
If 'ngx-editor' is a Web Component then add 'CUSTOM_ELEMENTS_SCHEMA' to the<EMAIL_ADDRESS>of this component to suppress this message.
To allow any property add 'NO_ERRORS_SCHEMA' to the<EMAIL_ADDRESS>of this component.

Can't bind to 'disabled' since it isn't a known property of 'ngx-editor'.

If 'ngx-editor' is an Angular component and it has 'disabled' input, then verify that it is part of this module.
If 'ngx-editor' is a Web Component then add 'CUSTOM_ELEMENTS_SCHEMA' to the<EMAIL_ADDRESS>of this component to suppress this message.
To allow any property add 'NO_ERRORS_SCHEMA' to the<EMAIL_ADDRESS>of this component.

Version
^12.0.0
What browsers are you seeing the problem on?
Chrome
Link to reproduce
https://github.com/grahamroy/editor
Relevant log output
as above

Willing to submit a PR?
Yes

DOH!
Thanks for your help :)


I can't make this project running.

Error said nhost init or nhost config pull, but nhost.toml was existed.
So what should I do?

Where can I get these .env variables?

@chrtze Excuse me, could you please check this issue?

you should be able to run the platform locally by using placeholder secrets like
DISCORD_NOTIFICATIONS_WEBHOOK='-'
GITHUB_CLIENT_ID='-'
GITHUB_CLIENT_SECRET='-'
GRAFANA_ADMIN_PASSWORD='-'
HASURA_GRAPHQL_ADMIN_SECRET='nhost-admin-secret'
HASURA_GRAPHQL_JWT_SECRET='-'
MAILJET_APIKEY_PRIVATE='-'
MAILJET_APIKEY_PUBLIC='-'
NHOST_WEBHOOK_SECRET='nhost-webhook-secret'
SMTP_PASSWORD='-'
STRIPE_SECRET_KEY='-'
STRIPE_WEBHOOK_SECRET='-'
VERCEL_WEBHOOK_SECRET='-'
GITHUB_ACCESS_TOKEN='-'
UPSTASH_REDIS_URL='-'
UPSTASH_REDIS_TOKEN='-'

The platform is not about the React Flow Pro examples (they are also not included in this repo). The platform can be used for inspiration, learning or as a starting point for your own projects.

Got it, thanks replay.

Message ID: @.***>

you should be able to run the platform locally by using placeholder secrets like
DISCORD_NOTIFICATIONS_WEBHOOK='-'
GITHUB_CLIENT_ID='-'
GITHUB_CLIENT_SECRET='-'
GRAFANA_ADMIN_PASSWORD='-'
HASURA_GRAPHQL_ADMIN_SECRET='nhost-admin-secret'
HASURA_GRAPHQL_JWT_SECRET='-'
MAILJET_APIKEY_PRIVATE='-'
MAILJET_APIKEY_PUBLIC='-'
NHOST_WEBHOOK_SECRET='nhost-webhook-secret'
SMTP_PASSWORD='-'
STRIPE_SECRET_KEY='-'
STRIPE_WEBHOOK_SECRET='-'
VERCEL_WEBHOOK_SECRET='-'
GITHUB_ACCESS_TOKEN='-'
UPSTASH_REDIS_URL='-'
UPSTASH_REDIS_TOKEN='-'

The platform is not about the React Flow Pro examples (they are also not included in this repo). The platform can be used for inspiration, learning or as a starting point for your own projects.

Thanks replay.


paper link？

I have been attempting to access the paper using the link provided in the readme file, but it appears that the link leads to a r resource that is not the intended paper.

It is my great honor to receive your interest in our work just hours after making this repository public! I uploaded the paper to arXiv earlier today and it is currently scheduled to be announced on Fri, 17 Mar 2023 00:00:00 GMT. Please use this link to access the paper for now.

Hello DachunKai,
Thanks for your patience! The paper link in README.md has been updated.

Get it! Thanks!


Is nakama really support cocos-js ??

Hello Admin.
First of all, I was really happy when I find your service, cause there is not much back-end sass service for cocos creator.

But!!
I found your example or cocos sdk which you support is totally incomplete.
for example - email auth
[your website example]
const email =<EMAIL_ADDRESS>const password = "3bc8f72e95a9";
client.authenticateEmail(email, password, true, "mycustomusername")
.then(function(session) {
cc.log("Authenticated successfully. User ID:", session.user_id);
},
function(error) {
cc.error("authenticate failed:", JSON.stringify(error));
});
this is example I see in your web-site. I try this example so many time, and everytime I get fail message, even nakama server is working very well.
And then I found this example is UNMATCH with cocos-sdk!
below is your sdk for supporting cocos.
[actual function]
Client.prototype.authenticateEmail = function (request) {
...
fetchOptions.headers = __assign({}, headers);
fetchOptions.body = JSON.stringify({
** email: request.email,**
** password: request.password**
});
return Promise.race([
fetch(this.configuration.basePath + urlPath + urlQuery, fetchOptions).then(function (response) {
if (response.status >= 200 && response.status < 300) {
return response.json();
}
else {
throw response;
}
}),
new Promise(function (_, reject) {
return setTimeout(reject, _this.configuration.timeoutMs, "Request timed out.");
}),
]).then(function (apiSession) {
return Session.restore(apiSession.token || "");
});
};
To call e-mail auth function, In your website example, I thought all I should do is sending e-mail and password as parameter.
But actually I should send request object as a parameter which contains e-mail and password  as a variable.
=============================================================================
I know your service is pretty good and very organized sass service. But after I experience this, I so worried that every example in your web-site have same error like this. and I also I have afraid I encounter same error after I publish my game to the market.
So I request you to make your website example correctly or please update cocos sdk!
thank you very much.
the sdk now I'm using is here : https://github.com/heroiclabs/nakama-cocos2d-x-javascript/releases/tag/v2.0.0

@jhyoo2 Thanks for the detailed email. You're right the code examples in the docs for the Cocos Creator compatible client are outdated. I've opened a documentation issue to track updates for it which you can follow here.
In the meantime you can also look at the JavaScript client code examples in the docs because the Cocos Creator compatible client is derived from that client SDK.
I will close this issue because its a documentation task and not an issue with the game server.

Hey @jhyoo the issue actually wasn't the docs, it's that the cocos-2d-js v2.0 release was out of date. I released a new one today that should match what exists in the docs.


A channel library file is now needed

Need channelLibFile in the config for the migrators to work.  -MW

The goal of #115 was that the ChannelLibrary was a QGL thing and anything that needed it should import it from QGL.

Ah!  I had an older version of JSONLibraryUtils laying around.  It was still looking for config.channelLibFile.  Seems to work now without setting anything in the config.py.


MSBuild - Xaml MarkupCompile passes slow

Describe the bug

References: https://github.com/dotnet/wpf/issues/3954
When running msbuild against a uwp project, the steps to compile XAML are very slow performing in relation to other tasks.
Are there any improvements or caching that can be done to speed up compilation times related to XAML?
Running Windows 10.0.17763.0 XamlCompiler.
C:\Program Files (x86)\Windows Kits\10\bin\10.0.17763.0\XamlCompiler\Microsoft.Windows.UI.Xaml.Common.targets
Steps to reproduce the bug

Steps to reproduce the behavior:

Go to '...'
Click on '....'

Expected behavior

msbuild -maxCpuCount:4 -v:m -bl -clp:PerformanceSummary;ShowCommandLine;ShowTimestamp

Screenshots

Sample of relevant csproj properties
<?xml version="1.0" encoding="utf-8"?>
<Project ToolsVersion="15.0" DefaultTargets="Build" xmlns="http://schemas.microsoft.com/developer/msbuild/2003">
  <Import Project="$(MSBuildExtensionsPath)\$(MSBuildToolsVersion)\Microsoft.Common.props" Condition="Exists('$(MSBuildExtensionsPath)\$(MSBuildToolsVersion)\Microsoft.Common.props')" />
    <PropertyGroup>
   <RuntimeIdentifier>win10</RuntimeIdentifier>
  <TargetPlatformIdentifier>UAP</TargetPlatformIdentifier>
  <TargetPlatformMinVersion>10.0.17763.0</TargetPlatformMinVersion>
  <AppxBundlePlatforms>x86|x64</AppxBundlePlatforms>

Version Info

NuGet package version:

 <PackageReference Include="Microsoft.NETCore.UniversalWindowsPlatform">
      <Version>6.2.9</Version>
    </PackageReference>
    <PackageReference Include="Microsoft.Toolkit.Uwp.UI.Controls">
      <Version>5.1.1</Version>
    </PackageReference>
    <PackageReference Include="Microsoft.Toolkit.Uwp.UI.Controls.DataGrid">
      <Version>5.1.0</Version>
    </PackageReference>
    <PackageReference Include="Redux.NET">
      <Version>2.0.0</Version>
    </PackageReference>
    <PackageReference Include="Telerik.UI.for.UniversalWindowsPlatform">
      <Version><IP_ADDRESS></Version>
    </PackageReference>
    ```

<!-- If you are using WinUI 3, please specify for which Windows app type you have encountered the issue. Leave blank if you didn't try that app type. -->
Windows app type:
| UWP              | Win32            |
| :--------------- | :--------------- |
| <!-- Yes/No? --> | <!-- Yes/No? --> |

<!-- Which Windows versions did you see the issue on? Leave blank if you didn't try that version. -->
| Windows 10 version                  | Saw the problem? |
| :--------------------------------- | :-------------------- |
| Insider Build (xxxxx)              | <!-- Yes/No? -->   |
| May 2020 Update (19041)            | <!-- Yes/No? -->   |
| November 2019 Update (18363)       | <!-- Yes/No? -->   |
| May 2019 Update (18362)            | <!-- Yes/No? -->   |
| October 2018 Update (17763)        | Yes   |
| April 2018 Update (17134)          | <!-- Yes/No? -->   |
| Fall Creators Update (16299)       | <!-- Yes/No? -->   |
| Creators Update (15063)            | <!-- Yes/No? -->   |

<!-- Which device form factors did you see the issue on? Leave blank if you didn't try that device. -->
| Device form factor | Saw the problem? |
| :----------------- | :--------------- |
| Desktop            | Yes/No |
| Xbox               | <!-- Yes/No? --> |
| Surface Hub        | <!-- Yes/No? --> |
| IoT                | <!-- Yes/No? --> |

**Additional context**
<!-- Enter any other applicable info here -->

Here is an example of the steps being run.

```plaintext
  10303 ms  MarkupCompilePass2                         2 calls
    14030 ms  MarkupCompilePass1                         2 calls

Analysis

Versions & Configurations

msbuild <IP_ADDRESS>705
Triggering build perf test from command line.  Visual Studio 2019 Enterprise is slower.

@alwu-msft or @RealTommyKlein fyi

@alwu-msft or @RealTommyKlein fyi

Thanks for filing this issue @asears.
We have #1535 open related to compiler perf, unless you think there is a reason to have separate issues, I'll close this as a dupe

Thanks for filing this issue @asears.
We have #1535 open related to compiler perf, unless you think there is a reason to have separate issues, I'll close this as a dupe

Sure thing, close it as a duplicate unless you can use this issue to target / track optimizing the 2 Xaml compile tasks and targets.   Might be simpler.  The issue you linked seems to relate to upgrading to fix the performance regression issues.  A drop-in replacement to these xaml tasks & targets or some pointers on addressing the build issues with msbuild flags would be much appreciated instead of code updates or upgrades.  Shouldn't need to change code to fix build tooling performance?
The build doesn't seem to take into account the fact that the xaml/cs files haven't changed, and looking internally at the .NET Framework code for those 2 compile tasks seem to have much room for perf tweaks.
There are two other issues we're having which may be associated to these tasks:

the incorrect detection of language by filename (which is picking up some unit tests and throwing a compiler warning)
the inability to overwrite files during the build (which could be caused by switching appdomains, threads or target permissions in the compile task).

I see this option.  How do we pass it in to msbuild/will it help?
AlwaysCompileMarkupFilesInSeparateDomain | Optional Boolean parameter.Specifies whether to run the task in a separate AppDomain. If this parameter returns false, the task runs in the same AppDomain as MSBuild and it runs faster. If the parameter returns true, the task runs in a second AppDomain that is isolated from MSBuild and runs slower.

Would be nice if a fix for performance regression could be backported for the community.   Appreciate any help.

Sure thing, close it as a duplicate unless you can use this issue to target / track optimizing the 2 Xaml compile tasks and targets.   Might be simpler.  The issue you linked seems to relate to upgrading to fix the performance regression issues.  A drop-in replacement to these xaml tasks & targets or some pointers on addressing the build issues with msbuild flags would be much appreciated instead of code updates or upgrades.  Shouldn't need to change code to fix build tooling performance?
The build doesn't seem to take into account the fact that the xaml/cs files haven't changed, and looking internally at the .NET Framework code for those 2 compile tasks seem to have much room for perf tweaks.
There are two other issues we're having which may be associated to these tasks:

the incorrect detection of language by filename (which is picking up some unit tests and throwing a compiler warning)
the inability to overwrite files during the build (which could be caused by switching appdomains, threads or target permissions in the compile task).

I see this option.  How do we pass it in to msbuild/will it help?
AlwaysCompileMarkupFilesInSeparateDomain | Optional Boolean parameter.Specifies whether to run the task in a separate AppDomain. If this parameter returns false, the task runs in the same AppDomain as MSBuild and it runs faster. If the parameter returns true, the task runs in a second AppDomain that is isolated from MSBuild and runs slower.

Would be nice if a fix for performance regression could be backported for the community.   Appreciate any help.

@asears - unfortunately, there isn't much in the way of MSBuild flags to address the performance issue.  The current slowness in the Windows.UI.Xaml compiler is due to its core logic of evaluating which .xaml files it needs to reparse.  As far as MSBuild flags, it looks like you're looking at the documentation for the WPF compiler.  The Windows.UI.Xaml compiler doesn't have that AlwaysCompileMarkupFilesInSeparateDomain parameter, and for Windows.UI.Xaml the 2nd compilation pass is MarkupCompilePass2 is always required.

@asears - unfortunately, there isn't much in the way of MSBuild flags to address the performance issue.  The current slowness in the Windows.UI.Xaml compiler is due to its core logic of evaluating which .xaml files it needs to reparse.  As far as MSBuild flags, it looks like you're looking at the documentation for the WPF compiler.  The Windows.UI.Xaml compiler doesn't have that AlwaysCompileMarkupFilesInSeparateDomain parameter, and for Windows.UI.Xaml the 2nd compilation pass is MarkupCompilePass2 is always required.

Closing as dupe and known issue.


UTF-8 unicode problem with PHP 8.3

Dear Shortcode developers,
since i upgraded to the latest release of PHP 8.3 my Grav instance will not render some pages anymore. At first i thought it belongs to the plugin markdown-collapsible, which triggers it. But it's developer says it comes from Shortcode.
Could you maybe have a look at https://github.com/X-Ryl669/grav-plugin-markdown-collapsible/issues/8#issuecomment-2143991948 ?
for Umlauts like äüö it will fail with PCRE error value 4, because preg_match does not seem to use /u unicode support. Is there an option or safe way to implement this?
The alternative is to wrwite ü escaped chars but it is not convenient writing in this way to omit those rendering problems :/
regards, Mario

@vmario89 thank you for reporting the issue, I read into the linked Grav issue but I don't see you using shortcodes there? Can you share a minimal text and expected result to reproduce the issue? Thanks!

Hi,
the shortcode is the collapsible field starting with !> and ending with<EMAIL_ADDRESS>the content between has Umlauts and does not render, instead fails with the error. The errors throws basically in an class/method of Shortcode which is in user/plugins/shortcode-core/vendor/thunderer/shortcode/src/Parser/RegularParser.php
!> Übersicht anzeigen ...

Nr
Name

17
Gerhard Werner

!@

@vmario89 I can't reproduce the PCRE error on PHP 8.3 and the latest Shortcode version, it would help if you can provide a minimal script for that. Please check RegexBuilderUtility::buildNameRegex() method, though, and try replacing the regex inside with just \w+. Parsers restrict the valid shortcode name to [a-zA-Z0-9-_\\*]+, and that will exclude Übersicht. If you try the script below it should not apply any changes (shortcode will not be detected because of name restriction), afterwards it will be processed as you expect (result is yes!). I replied in the Grav repository asking @X-Ryl669 for a small reproduction script as well, as I'm still not sure how Shortcode it setup there and what syntax is used.
<?php
declare(strict_types=1);
namespace X;

use Thunder\Shortcode\HandlerContainer\HandlerContainer;
use Thunder\Shortcode\Parser\RegularParser;
use Thunder\Shortcode\Processor\Processor;
use Thunder\Shortcode\Shortcode\ProcessedShortcode;

require __DIR__.'/vendor/autoload.php';

$handlers = new HandlerContainer();
$handlers->add('Übersicht', fn(ProcessedShortcode $shortcode) => 'yes!');
$processor = new Processor(new RegularParser(), $handlers);
var_dump($processor->process('[Übersicht]'));

@vmario89 were you able to reproduce the issue in a script you can share? I'm afraid I can't help you without that, everything works fine on my end. Let me know if you have any new information, otherwise I'll close the issue in the near future.

hey. i am sorry i was not able to find time again yet and i dont know how to do.. i am not a php developer. i am web admin and content maintainer. For me it's hard to think about on all edges and a.t.m. i have no clue how to make a proper test script in the right place :-( i will need to close this then


Setup Nightwatch for end-to-end (e2e) tests

We got the base covered with unit testing, thanks to Jasmine + Karma, but we lack end-to-end testing, mainly for user interaction tests.
Nightwatch.js should be setup.

...or webdriver.io, since nightwatch.js syntax is not the most usable, and the documentation is almost non-existant when it's not contradictory (browser vs client, assert vs expect...), while still not having a instant messaging system like IRC, Gitter or the like.

On the other hand, webdriver.io and perhaps more generally Selenium seems limited when it comes to do a very simple thing like :

Set the caret position in the input wherever I want,
Input some characters at that position,
...and that's it.

cf. the webdriver.io issue https://github.com/webdriverio/webdriverio/issues/1791.
I'm not sure what I'm trying to achieve is doable with the current version of Selenium, hence I'm pausing this work until I get more answers.

I finally managed to find a way to move the caret by sending keys like 'ArrowLeft', 'Home' and 'End', by calling :
browser.keys(['End', 'ArrowLeft', 'ArrowLeft', 'ArrowLeft']);

for instance, without having to specify the element since it'll send those keys to the current active (focused) element.

The end-to-end tests can be run with yarn test:e2e.
You can edit test/e2e/index.html to setup form input(s) for a given issue, and test/e2e/spec/autoNumeric.e2e.spec.js for the webdriver.io tests.


Issue 163: getAnnotationsByType is available from java 8

Coverage remained the same at 94.822% when pulling d272faa0f9a1e188d0c7923a4d7fee388fe9a973 on dlemures/163 into 8deade32b179607f42801644bdc1f9e9faf6827f on master.

RTM


Introduce BlockLabel mixin

The current label mixin is always used in a block context and only in such a context is the included padding sensible. By extracting both the display and padding into a wrapping mixin, we can now
1: only use a single mixin for block labels without further declarations
2: use the Label mixin also for inline labels (which will be useful for the checkbox component)

In my opinion (but of course, take this with a grain of salt), it'd be ideal if, instead of creating a new label mixin, we could  add some arguments to the existing one that allow implementers to change its display and the end padding.
What do you think, @itamargiv? Deciding this will unblock the Checkbox component.

In my opinion (but of course, take this with a grain of salt), it'd be ideal if, instead of creating a new label mixin, we could  add some arguments to the existing one that allow implementers to change its display and the end padding.
What do you think, @itamargiv? Deciding this will unblock the Checkbox component.

I tend to agree with @SaiSan-WMDE. I think we can simply wrap the additional CSS rules with an @if operator and pass a boolean to determine if it's block or not, or even pass the value we would like for the display property and accordingly use a conditional to decide on adding padding-block-end or not.

I tend to agree with @SaiSan-WMDE. I think we can simply wrap the additional CSS rules with an @if operator and pass a boolean to determine if it's block or not, or even pass the value we would like for the display property and accordingly use a conditional to decide on adding padding-block-end or not.

I chose to make a second Mixin, because in most programming languages that I'm familiar with, it is considered a code smell to add a flag parameter to a public method and thereby increasing its complexity. Rather the preferred way is usually to have simple methods with descriptive names instead of more general methods with flags and conditionals where possible.
But, since I'm not familiar with the established patterns in Sass, I'll happily adjust the PR as you suggest. Probably tomorrow.

I chose to make a second Mixin, because in most programming languages that I'm familiar with, it is considered a code smell to add a flag parameter to a public method and thereby increasing its complexity. Rather the preferred way is usually to have simple methods with descriptive names instead of more general methods with flags and conditionals where possible.
But, since I'm not familiar with the established patterns in Sass, I'll happily adjust the PR as you suggest. Probably tomorrow.

it is considered a code smell to add a flag parameter to a public method and thereby increasing its complexity.

Yes, in any other programming language I would agree with you, and also that is why I would prefer that you implement my second suggestion, of having callers of the mixin pass the desired value for the display property over a simple boolean.
Either or, a function with different outcomes depending on passed argument is not completely unheard of and is a pattern I've seen before in sass for example: https://github.com/twbs/bootstrap/blob/main/scss/mixins/_caret.scss#L28-L62

it is considered a code smell to add a flag parameter to a public method and thereby increasing its complexity.

Yes, in any other programming language I would agree with you, and also that is why I would prefer that you implement my second suggestion, of having callers of the mixin pass the desired value for the display property over a simple boolean.
Either or, a function with different outcomes depending on passed argument is not completely unheard of and is a pattern I've seen before in sass for example: https://github.com/twbs/bootstrap/blob/main/scss/mixins/_caret.scss#L28-L62

I'm sorry, I still fail to see the benefits that justify the trade-offs and I don't think the example compares to this situation. The example mixin is about adding the caret and letting the caller control the direction via a parameter. This mixin is about changing either just the font or doing that and also   do a second unrelated thing and change the display type and padding.
Nonetheless, I have adjust the mixin as you suggested and I hope the PR can now be merged so that we can use it in the Checkbox PR.

I'm sorry, I still fail to see the benefits that justify the trade-offs and I don't think the example compares to this situation. The example mixin is about adding the caret and letting the caller control the direction via a parameter. This mixin is about changing either just the font or doing that and also   do a second unrelated thing and change the display type and padding.
Nonetheless, I have adjust the mixin as you suggested and I hope the PR can now be merged so that we can use it in the Checkbox PR.


Override config file

Hi, thanks for this tool!
It would be really useful to add a flag for the user to specify a custom configuration file, something like --override-config <...>
In my case, I want to call tldr from albert and in that case (only in that case, not system-wide) I 'd like to specify a custom configuration file which overrides the use_pager option

Hi! Could you maybe override XDG_CONFIG_HOME?
$ XDG_CONFIG_HOME=/tmp tldr --config-path
Config path is: /tmp/tealdeer/config.toml

That could be a way I suppose, but it's more of a hack rather than a solution to this.
This isn't super important to me, I can bypass it and parse the markdown files directly. I raised the issue because I thought it was a nice feature to have.
FWIW, here's the albert plugin I'm using tldr for: https://github.com/bergercookie/awesome-albert-plugins/tree/master/plugins/tldr_pages

Yeah, I suppose a --config flag wouldn't hurt :slightly_smiling_face:

This could also be considered when running with the --seed-config flag to specify where to put the generated file. I think the option should then have a more verbose name like config-location (unfortunately config-path is already taken).

(unfortunately config-path is already taken)

Should --config-path be deprecated considering we have --show-paths? Or perhaps --config-path should be renamed to --show-config-path.
Or for consistency, deprecate --config-path in preference for something like this --show-path <config|cache|pages|custom>. Then we would have show-paths and show-path <enum> which would be a bit more intuitive.
Isn't so relevant to this issue, but is this worth raising a new issue for @dbrgn @niklasmohrin ?

--config-path is already deprecated:
danilo@c3po:~$ tldr --config-path
Warning: The --config-path flag is deprecated, use --show-paths instead
Config path is: /home/danilo/.config/tealdeer/config.toml

It will be removed in a future version.

About --show-path <config|cache|pages|custom>: I feel like --show-paths is primarily intended for humans to understand how path precedence works with tealdeer or to initially find a place of interest. Having the single --show-path to me seems like a convenience thing for scripts, but they can just know the location or grep it from --show-paths. Unless specific feature requests come in, I would not bother to implement it


re-enable search preference

Package version (if known): v0.6.2
Describe the bug
Search preference is not enabled and it could potentially lead to bouncing effect.
Steps to Reproduce

see services/records/service.py::search()

Additional context
It was disabled due to the lack of user-agent and ip related information. This info should be extracted and set in the resource_requestctx, then the resource should pass it to the service.
The old search object uses the request object https://github.com/inveniosoftware/invenio-search/blob/81f4d23a1f24fe0d1c2fb7b1a9c64fd7870daed3/invenio_search/api.py#L150 it should be migrated in a way that is not accessed and just passed https://github.com/inveniosoftware/invenio-search/blob/81f4d23a1f24fe0d1c2fb7b1a9c64fd7870daed3/invenio_search/api.py#L270
Values should be accessed at the resource level and passed to the service search? (maybe is the service who calculates the preference (hash) based on what the resource passes.
Why:

https://github.com/inveniosoftware/invenio-search/pull/107
https://www.elastic.co/guide/en/elasticsearch/guide/current/_search_options.html#_preference

Blocked by merge + release of https://github.com/inveniosoftware/invenio-search/pull/207 first


xunit reporter doesn't properly excape non-ascii characters

While working on node-snmpjs I upgraded tap (from v0.4!) to gain support for reporters and coverage.  Unfortunately it looks like some tests generate non-ascii bytes in test names, which causes the xunit reporter to emit invalid XML.
The fix for the mocha xunit reporter is here: https://github.com/mochajs/mocha/commit/9f403bf33119290c262f293207766be1c1e51350#diff-50e3aa130a4f97a42ee2cf111c7b1d9d
Here's the test in question:
https://github.com/joyent/node-snmpjs/blob/master/test/protocol/data.test.js#L359-L385
And the invalid XML output:
<testcase classname="./test/protocol/data.test.js octet string encode" name="encode foobar" time="0"/>
<testcase classname="./test/protocol/data.test.js octet string encode" name="encode �AL� M" time="0"/>
<testcase classname="./test/protocol/data.test.js octet string encode" name="encode foo bar baz quux" time="0"/>
<testcase classname="./test/protocol/data.test.js octet string encode" name="encode �$Y���" time="0"/>
<testcase classname="./test/protocol/data.test.js octet string encode" name="encode fööbå®" time="0"/>

In the meantime I will update the test to avoid non-ascii.

I just realized that the original escape from mochajs is very broken and doesn't even properly replace '<>&"'.  It only replaces the first instance of each char:
exports.escape = function(html){
  return String(html)
    .replace('&', '&')
    .replace('"', '"')
    .replace('<', '<')
    .replace('>', '>');
}

to wit:
'bbb'.replace('b', 'o'); // results in 'obb' !

The proper form would use /expr/g:
exports.escape = function(html){
  return String(html)
    .replace(/&/g, '&')
    .replace(/"/g, '"')
    .replace(/</g, '<')
    .replace(/>/g, '>');
}

apologies as I realized this should be reported at tapjs/tap-mocha-reporter#43


Broken link about audit logs in Azure Monitor

The link "auditing logs in Azure Monitor logs and Azure Event Hubs" (https://blogs.msdn.microsoft.com/sqlsecurity/2018/09/13/sql-audit-logs-in-azure-log-analytics-and-azure-event-hubs/) is broken.

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

ID: 57944e9d-0efa-3503-9fe8-46c91119ecc9
Version Independent ID: 32caa5c0-aac4-75f8-42f8-b483d55a8392
Content: Azure SQL Database metrics and diagnostics logging
Content Source: articles/sql-database/sql-database-metrics-diag-logging.md
Service: sql-database
Sub-service: monitor
GitHub Login: @danimir
Microsoft Alias: danil

Updated / done. Will be visible in 24-48 hrs online.

@danimir Thank you! @BzSpi We will now proceed to close this thread. If there are further questions regarding this matter, please comment and we will gladly continue the discussion.


cannot use functions that return strings inside style property

Example of invalid code (throws a compile error)
<section
style={fmt.Sprintf("background: %s", "red")}
>
Project Page
</section>

Expected behavior
It should compile and work like every other property. I am so confused. Is there a reason why it doesn't?

I found the security page...


Peer dependencies are duplicated

Describe the bug
When a dependency uses a peer dependency that is also used by our project, the peer dependency is duplicated. This can be a breaking issue if they use React's contexts for example.
Reproduction
Repro link
In this example the project uses the library @litbase/alexandria, which has formik as a peer dependency, and provides a FieldWrapper component. The FieldWrapper component is a wrapper around Formik's Field component. This component can only be placed under a Formik component, as it uses a context Formik provides.
However, when importing Formik from formik, and importing FieldWrapper from @litbase/alexandria, the FieldWrapper cannot find the context Formik provides, as they are using two different formik libraries.
This is the case even though in the vite config resolve.dedupe contains formik.
System Info
Output of npx envinfo --system --npmPackages vite,@vitejs/plugin-vue --binaries --browsers:
 System:
    OS: Windows 10 10.0.19042
    CPU: (4) x64 Intel(R) Core(TM) i5-2400 CPU @ 3.10GHz
    Memory: 3.93 GB / 11.94 GB
  Binaries:
    Node: 14.15.4 - C:\Program Files\nodejs\node.EXE
    Yarn: 1.22.5 - C:\Program Files (x86)\Yarn\bin\yarn.CMD
    npm: 7.11.2 - C:\Program Files\nodejs\npm.CMD
  Browsers:
    Edge: Spartan (44.19041.1023.0), Chromium (91.0.864.48)
    Internet Explorer: 11.0.19041.1
  npmPackages:
    vite: ^2.3.7 => 2.3.7

Used package manager:  yarn

Can't reproduce.
I don't know why your app is throwing errors.
But there is an easy way to test if the two packages uses the same formik dependency:

I added import { Formik } from 'formik' and FieldWrapper.Formik = Formik to<EMAIL_ADDRESS>And console.log(Formik === FieldWrapper.Formik) to src/App.jsx

The output is true, meaning they are the same.

@sodatea I just tried this on my machine and console.log(Formik === FieldWrapper.Formik) returned false. I suspect the issue might have to do with the operating system. On a Mac it seems to work fine for me too.

It prints true on my Windows 10 VM.
Maybe it's caused by incorrect dependency hoisting by the package manager?
How about running yarn --frozen-lockfile and try again?

@sodatea The issue persists even after running yarn --frozen-lockfile

How about https://github.com/atlassian/yarn-deduplicate?

I'm sorry, I made a couple of mistakes, after fixing them everything worked as you described. However I was able to pinpoint where the problem is: Everything works fine with yarn 1, but on yarn 2, when using the pnp nodeLinker, the error appears.
I made some updates to both @litbase/alexandria and the repro repo. I now export a Formik as TempTestFormikk (excuse the typo) from @litbase/alexandria to make it easy to compare it with our top level Formik without changing the library files locally. I also changed the package manager on the repro repo to yarn 2 using the pnp nodeLinker. I confirmed that switching the nodeLinker to node-modules makes everything work fine, and as soon as you change it back to pnp the error appears.
On Mac it still works fine even with the pnp nodeLinker.


Set investigation Risk Level

Trello ticket
Allow users to set the risk level for the investigation through a radio button selection between a list of risk levels.
Description
Users will be able to either choose one of the default risk levels or to set a customised risk level for the case.
Once set, the risk level can be changed or removed.
The risk level will be displayed in the case Overview. In this case is not set, an will display a link allowing the user to set it

The risk level page will have the current risk level pre-selected

After selecting a risk level an submitted, the user will be sent to the case overview and will see a flash message informing them about the change

The overview page will display the current risk level and a link to change it

Users will be able to set their own risk level

Flash message will also be displayed when the risk level changes

Risk level can also be removed from the case

The audit activity log for the case will register every change on the risk level

Checklist:

[x] Have you documented your changes in the pull request description?
[ ] Does the change present any security considerations?
[ ] Is any gem functionality overloaded? Eg: Devise controller methods being overloaded.
[ ] Has acceptance criteria been tested by a peer?
[x] Has the CHANGELOG been updated? (If change is worth telling users about.)

Hi @scruti  I'm testing this manually so please don't merge until I confirm, thanks.

Thanks for the heads up @nasirkhanbeis


feat: export getTailwindFormat function for separate usage

fixes https://github.com/nado1001/style-dictionary-tailwindcss-transformer/issues/311

Thanks for the great suggestions!


No armv7  in the App.framework/App

Steps to Reproduce

update code
flutter build ios --release
lipo -info ios/Flutter/App.framework/App
It does't happen on every Mac

what I get : "Architectures in the fat file: ios/Flutter/App.framework/App are: arm64 "
Logs
the  logs of "flutter build ios --release" is too long to be written in the issue.
I could email you , if you tell me your emal.
I chose some logs here

LINKER_DISPLAYS_MANGLED_NAMES = NO
LINK_FILE_LIST_normal_arm64 =
LINK_WITH_STANDARD_LIBRARIES = YES
LOCALIZABLE_CONTENT_DIR =
LOCALIZED_RESOURCES_FOLDER_PATH = Runner.app/English.lproj
LOCALIZED_STRING_MACRO_NAMES = NSLocalizedString CFLocalizedString
LOCAL_ADMIN_APPS_DIR = /Applications/Utilities
LOCAL_APPS_DIR = /Applications
LOCAL_DEVELOPER_DIR = /Library/Developer
LOCAL_LIBRARY_DIR = /Library
LOCROOT =
LOCSYMROOT =
MACH_O_TYPE = mh_execute
MAC_OS_X_PRODUCT_BUILD_VERSION = 18A391
MAC_OS_X_VERSION_ACTUAL = 101400
MAC_OS_X_VERSION_MAJOR = 101400
MAC_OS_X_VERSION_MINOR = 1400
METAL_LIBRARY_FILE_BASE = default
METAL_LIBRARY_OUTPUT_DIR =
/Users/lianjia/Jenkins_workspace/workspace/RD/flutter_im_portal_iOS_i/build/ios/Release-iphoneos/Runner.app
MODULE_CACHE_DIR = /Users/lianjia/Library/Developer/Xcode/DerivedData/ModuleCache.noindex
MTL_ENABLE_DEBUG_INFO = NO
NATIVE_ARCH = armv7
NATIVE_ARCH_32_BIT = i386
NATIVE_ARCH_64_BIT = x86_64
NATIVE_ARCH_ACTUAL = x86_64
NO_COMMON = YES
OBJECT_FILE_DIR =
/Users/lianjia/Library/Developer/Xcode/DerivedData/Runner-dtqiifbbyzywmherykgihurrqpri/Build/Intermediates.noindex
/Runner.build/Release-iphoneos/Runner.build/Objects
OBJECT_FILE_DIR_normal =
/Users/lianjia/Library/Developer/Xcode/DerivedData/Runner-dtqiifbbyzywmherykgihurrqpri/Build/Intermediates.noindex
/Runner.build/Release-iphoneos/Runner.build/Objects-normal
OBJROOT =
/Users/lianjia/Library/Developer/Xcode/DerivedData/Runner-dtqiifbbyzywmherykgihurrqpri/Build/Intermediates.noindex
ONLY_ACTIVE_ARCH = NO
OS = MACOS
OSAC = /usr/bin/osacompile
OTHER_CFLAGS =  -isystem
"/Users/lianjia/Jenkins_workspace/workspace/RD/flutter_im_portal_iOS_i/ios/Pods/Headers/Public" -isystem
"/Users/lianjia/Jenkins_workspace/workspace/RD/flutter_im_portal_iOS_i/ios/Pods/Headers/Public/AFNetworking"
-isystem
"/Users/lianjia/Jenkins_workspace/workspace/RD/flutter_im_portal_iOS_i/ios/Pods/Headers/Public/CocoaLumberjack"
-isystem
"/Users/lianjia/Jenkins_workspace/workspace/RD/flutter_im_portal_iOS_i/ios/Pods/Headers/Public/Crashlytics"
-isystem "/Users/lianjia/Jenkins_workspace/workspace/RD/flutter_im_portal_iOS_i/ios/Pods/Headers/Public/Fabric"
-isystem "/Users/lianjia/Jenkins_workspace/workspace/RD/flutter_im_portal_iOS_i/ios/Pods/Headers/Public/Flutter"
-isystem
"/Users/lianjia/Jenkins_workspace/workspace/RD/flutter_im_portal_iOS_i/ios/Pods/Headers/Public/LJBBaseHttpService"
-isystem
"/Users/lianjia/Jenkins_workspace/workspace/RD/flutter_im_portal_iOS_i/ios/Pods/Headers/Public/LJBBrokerBase"
-isystem
"/Users/lianjia/Jenkins_workspace/workspace/RD/flutter_im_portal_iOS_i/ios/Pods/Headers/Public/LJBase3rdFramework"
-isystem
"/Users/lianjia/Jenkins_workspace/workspace/RD/flutter_im_portal_iOS_i/ios/Pods/Headers/Public/LJBaseAppConfig"
-isystem
"/Users/lianjia/Jenkins_workspace/workspace/RD/flutter_im_portal_iOS_i/ios/Pods/Headers/Public/LJBaseRouter"
-isystem
"/Users/lianjia/Jenkins_workspace/workspace/RD/flutter_im_portal_iOS_i/ios/Pods/Headers/Public/LJBaseToolKit"
-isystem
"/Users/lianjia/Jenkins_workspace/workspace/RD/flutter_im_portal_iOS_i/ios/Pods/Headers/Public/LJBaseViewControlle
rComponents" -isystem
"/Users/lianjia/Jenkins_workspace/workspace/RD/flutter_im_portal_iOS_i/ios/Pods/Headers/Public/LJBrokerCompileConf
iguration" -isystem
"/Users/lianjia/Jenkins_workspace/workspace/RD/flutter_im_portal_iOS_i/ios/Pods/Headers/Public/LJEventTracting"
-isystem
"/Users/lianjia/Jenkins_workspace/workspace/RD/flutter_im_portal_iOS_i/ios/Pods/Headers/Public/LJHTTPService"
-isystem
"/Users/lianjia/Jenkins_workspace/workspace/RD/flutter_im_portal_iOS_i/ios/Pods/Headers/Public/LJMAlertView"
-isystem
"/Users/lianjia/Jenkins_workspace/workspace/RD/flutter_im_portal_iOS_i/ios/Pods/Headers/Public/LJNetworkService"
-isystem
"/Users/lianjia/Jenkins_workspace/workspace/RD/flutter_im_portal_iOS_i/ios/Pods/Headers/Public/LJProgressHUDHelper
" -isystem
"/Users/lianjia/Jenkins_workspace/workspace/RD/flutter_im_portal_iOS_i/ios/Pods/Headers/Public/MBProgressHUD"
-isystem
"/Users/lianjia/Jenkins_workspace/workspace/RD/flutter_im_portal_iOS_i/ios/Pods/Headers/Public/SAMKeychain"
-isystem
"/Users/lianjia/Jenkins_workspace/workspace/RD/flutter_im_portal_iOS_i/ios/Pods/Headers/Public/SensorsAnalyticsSDK
" -isystem "/Users/lianjia/Jenkins_workspace/workspace/RD/flutter_im_portal_iOS_i/ios/Pods/Headers/Public/YYCache"
-isystem "/Users/lianjia/Jenkins_workspace/workspace/RD/flutter_im_portal_iOS_i/ios/Pods/Headers/Public/base"
-isystem
"/Users/lianjia/Jenkins_workspace/workspace/RD/flutter_im_portal_iOS_i/ios/Pods/Headers/Public/flutter_im_basic_pl
ugin" -isystem "/Users/lianjia/Jenkins_workspace/workspace/RD/flutter_im_portal_iOS_i/ios/Pods/Headers/Public"
-isystem
"/Users/lianjia/Jenkins_workspace/workspace/RD/flutter_im_portal_iOS_i/ios/Pods/Headers/Public/AFNetworking"
-isystem
"/Users/lianjia/Jenkins_workspace/workspace/RD/flutter_im_portal_iOS_i/ios/Pods/Headers/Public/CocoaLumberjack"
-isystem
"/Users/lianjia/Jenkins_workspace/workspace/RD/flutter_im_portal_iOS_i/ios/Pods/Headers/Public/Crashlytics"
-isystem "/Users/lianjia/Jenkins_workspace/workspace/RD/flutter_im_portal_iOS_i/ios/Pods/Headers/Public/Fabric"
-isystem "/Users/lianjia/Jenkins_workspace/workspace/RD/flutter_im_portal_iOS_i/ios/Pods/Headers/Public/Flutter"
-isystem
"/Users/lianjia/Jenkins_workspace/workspace/RD/flutter_im_portal_iOS_i/ios/Pods/Headers/Public/LJBBaseHttpService"
-isystem
"/Users/lianjia/Jenkins_workspace/workspace/RD/flutter_im_portal_iOS_i/ios/Pods/Headers/Public/LJBBrokerBase"
-isystem
"/Users/lianjia/Jenkins_workspace/workspace/RD/flutter_im_portal_iOS_i/ios/Pods/Headers/Public/LJBase3rdFramework"
-isystem
"/Users/lianjia/Jenkins_workspace/workspace/RD/flutter_im_portal_iOS_i/ios/Pods/Headers/Public/LJBaseAppConfig"
-isystem
"/Users/lianjia/Jenkins_workspace/workspace/RD/flutter_im_portal_iOS_i/ios/Pods/Headers/Public/LJBaseRouter"
-isystem
"/Users/lianjia/Jenkins_workspace/workspace/RD/flutter_im_portal_iOS_i/ios/Pods/Headers/Public/LJBaseToolKit"
-isystem
"/Users/lianjia/Jenkins_workspace/workspace/RD/flutter_im_portal_iOS_i/ios/Pods/Headers/Public/LJBaseViewControlle
rComponents" -isystem
"/Users/lianjia/Jenkins_workspace/workspace/RD/flutter_im_portal_iOS_i/ios/Pods/Headers/Public/LJBrokerCompileConf
iguration" -isystem
"/Users/lianjia/Jenkins_workspace/workspace/RD/flutter_im_portal_iOS_i/ios/Pods/Headers/Public/LJEventTracting"
-isystem
"/Users/lianjia/Jenkins_workspace/workspace/RD/flutter_im_portal_iOS_i/ios/Pods/Headers/Public/LJHTTPService"
-isystem
"/Users/lianjia/Jenkins_workspace/workspace/RD/flutter_im_portal_iOS_i/ios/Pods/Headers/Public/LJMAlertView"
-isystem
"/Users/lianjia/Jenkins_workspace/workspace/RD/flutter_im_portal_iOS_i/ios/Pods/Headers/Public/LJNetworkService"
-isystem
"/Users/lianjia/Jenkins_workspace/workspace/RD/flutter_im_portal_iOS_i/ios/Pods/Headers/Public/LJProgressHUDHelper
" -isystem
"/Users/lianjia/Jenkins_workspace/workspace/RD/flutter_im_portal_iOS_i/ios/Pods/Headers/Public/MBProgressHUD"
-isystem
"/Users/lianjia/Jenkins_workspace/workspace/RD/flutter_im_portal_iOS_i/ios/Pods/Headers/Public/SAMKeychain"
-isystem
"/Users/lianjia/Jenkins_workspace/workspace/RD/flutter_im_portal_iOS_i/ios/Pods/Headers/Public/SensorsAnalyticsSDK
" -isystem "/Users/lianjia/Jenkins_workspace/workspace/RD/flutter_im_portal_iOS_i/ios/Pods/Headers/Public/YYCache"
-isystem "/Users/lianjia/Jenkins_workspace/workspace/RD/flutter_im_portal_iOS_i/ios/Pods/Headers/Public/base"
-isystem
"/Users/lianjia/Jenkins_workspace/workspace/RD/flutter_im_portal_iOS_i/ios/Pods/Headers/Public/flutter_im_basic_pl
ugin"
OTHER_CPLUSPLUSFLAGS =  -isystem
"/Users/lianjia/Jenkins_workspace/workspace/RD/flutter_im_portal_iOS_i/ios/Pods/Headers/Public" -isystem
"/Users/lianjia/Jenkins_workspace/workspace/RD/flutter_im_portal_iOS_i/ios/Pods/Headers/Public/AFNetworking"
-isystem
"/Users/lianjia/Jenkins_workspace/workspace/RD/flutter_im_portal_iOS_i/ios/Pods/Headers/Public/CocoaLumberjack"
-isystem
"/Users/lianjia/Jenkins_workspace/workspace/RD/flutter_im_portal_iOS_i/ios/Pods/Headers/Public/Crashlytics"
-isystem "/Users/lianjia/Jenkins_workspace/workspace/RD/flutter_im_portal_iOS_i/ios/Pods/Headers/Public/Fabric"
-isystem "/Users/lianjia/Jenkins_workspace/workspace/RD/flutter_im_portal_iOS_i/ios/Pods/Headers/Public/Flutter"
-isystem
"/Users/lianjia/Jenkins_workspace/workspace/RD/flutter_im_portal_iOS_i/ios/Pods/Headers/Public/LJBBaseHttpService"
-isystem
"/Users/lianjia/Jenkins_workspace/workspace/RD/flutter_im_portal_iOS_i/ios/Pods/Headers/Public/LJBBrokerBase"
-isystem
"/Users/lianjia/Jenkins_workspace/workspace/RD/flutter_im_portal_iOS_i/ios/Pods/Headers/Public/LJBase3rdFramework"
-isystem
"/Users/lianjia/Jenkins_workspace/workspace/RD/flutter_im_portal_iOS_i/ios/Pods/Headers/Public/LJBaseAppConfig"
-isystem
"/Users/lianjia/Jenkins_workspace/workspace/RD/flutter_im_portal_iOS_i/ios/Pods/Headers/Public/LJBaseRouter"
-isystem
"/Users/lianjia/Jenkins_workspace/workspace/RD/flutter_im_portal_iOS_i/ios/Pods/Headers/Public/LJBaseToolKit"
-isystem
"/Users/lianjia/Jenkins_workspace/workspace/RD/flutter_im_portal_iOS_i/ios/Pods/Headers/Public/LJBaseViewControlle
rComponents" -isystem
"/Users/lianjia/Jenkins_workspace/workspace/RD/flutter_im_portal_iOS_i/ios/Pods/Headers/Public/LJBrokerCompileConf
iguration" -isystem
"/Users/lianjia/Jenkins_workspace/workspace/RD/flutter_im_portal_iOS_i/ios/Pods/Headers/Public/LJEventTracting"
-isystem
"/Users/lianjia/Jenkins_workspace/workspace/RD/flutter_im_portal_iOS_i/ios/Pods/Headers/Public/LJHTTPService"
-isystem
"/Users/lianjia/Jenkins_workspace/workspace/RD/flutter_im_portal_iOS_i/ios/Pods/Headers/Public/LJMAlertView"
-isystem
"/Users/lianjia/Jenkins_workspace/workspace/RD/flutter_im_portal_iOS_i/ios/Pods/Headers/Public/LJNetworkService"
-isystem
"/Users/lianjia/Jenkins_workspace/workspace/RD/flutter_im_portal_iOS_i/ios/Pods/Headers/Public/LJProgressHUDHelper
" -isystem
"/Users/lianjia/Jenkins_workspace/workspace/RD/flutter_im_portal_iOS_i/ios/Pods/Headers/Public/MBProgressHUD"
-isystem
"/Users/lianjia/Jenkins_workspace/workspace/RD/flutter_im_portal_iOS_i/ios/Pods/Headers/Public/SAMKeychain"
-isystem
"/Users/lianjia/Jenkins_workspace/workspace/RD/flutter_im_portal_iOS_i/ios/Pods/Headers/Public/SensorsAnalyticsSDK
" -isystem "/Users/lianjia/Jenkins_workspace/workspace/RD/flutter_im_portal_iOS_i/ios/Pods/Headers/Public/YYCache"
-isystem "/Users/lianjia/Jenkins_workspace/workspace/RD/flutter_im_portal_iOS_i/ios/Pods/Headers/Public/base"
-isystem
"/Users/lianjia/Jenkins_workspace/workspace/RD/flutter_im_portal_iOS_i/ios/Pods/Headers/Public/flutter_im_basic_pl
ugin" -isystem "/Users/lianjia/Jenkins_workspace/workspace/RD/flutter_im_portal_iOS_i/ios/Pods/Headers/Public"
-isystem
"/Users/lianjia/Jenkins_workspace/workspace/RD/flutter_im_portal_iOS_i/ios/Pods/Headers/Public/AFNetworking"
-isystem
"/Users/lianjia/Jenkins_workspace/workspace/RD/flutter_im_portal_iOS_i/ios/Pods/Headers/Public/CocoaLumberjack"
-isystem
"/Users/lianjia/Jenkins_workspace/workspace/RD/flutter_im_portal_iOS_i/ios/Pods/Headers/Public/Crashlytics"
-isystem "/Users/lianjia/Jenkins_workspace/workspace/RD/flutter_im_portal_iOS_i/ios/Pods/Headers/Public/Fabric"
-isystem "/Users/lianjia/Jenkins_workspace/workspace/RD/flutter_im_portal_iOS_i/ios/Pods/Headers/Public/Flutter"
-isystem
"/Users/lianjia/Jenkins_workspace/workspace/RD/flutter_im_portal_iOS_i/ios/Pods/Headers/Public/LJBBaseHttpService"
-isystem
"/Users/lianjia/Jenkins_workspace/workspace/RD/flutter_im_portal_iOS_i/ios/Pods/Headers/Public/LJBBrokerBase"
-isystem
"/Users/lianjia/Jenkins_workspace/workspace/RD/flutter_im_portal_iOS_i/ios/Pods/Headers/Public/LJBase3rdFramework"
-isystem
"/Users/lianjia/Jenkins_workspace/workspace/RD/flutter_im_portal_iOS_i/ios/Pods/Headers/Public/LJBaseAppConfig"
-isystem
"/Users/lianjia/Jenkins_workspace/workspace/RD/flutter_im_portal_iOS_i/ios/Pods/Headers/Public/LJBaseRouter"
-isystem
"/Users/lianjia/Jenkins_workspace/workspace/RD/flutter_im_portal_iOS_i/ios/Pods/Headers/Public/LJBaseToolKit"
-isystem
"/Users/lianjia/Jenkins_workspace/workspace/RD/flutter_im_portal_iOS_i/ios/Pods/Headers/Public/LJBaseViewControlle
rComponents" -isystem
"/Users/lianjia/Jenkins_workspace/workspace/RD/flutter_im_portal_iOS_i/ios/Pods/Headers/Public/LJBrokerCompileConf
iguration" -isystem
"/Users/lianjia/Jenkins_workspace/workspace/RD/flutter_im_portal_iOS_i/ios/Pods/Headers/Public/LJEventTracting"
-isystem
"/Users/lianjia/Jenkins_workspace/workspace/RD/flutter_im_portal_iOS_i/ios/Pods/Headers/Public/LJHTTPService"
-isystem
"/Users/lianjia/Jenkins_workspace/workspace/RD/flutter_im_portal_iOS_i/ios/Pods/Headers/Public/LJMAlertView"
-isystem
"/Users/lianjia/Jenkins_workspace/workspace/RD/flutter_im_portal_iOS_i/ios/Pods/Headers/Public/LJNetworkService"
-isystem
"/Users/lianjia/Jenkins_workspace/workspace/RD/flutter_im_portal_iOS_i/ios/Pods/Headers/Public/LJProgressHUDHelper
" -isystem
"/Users/lianjia/Jenkins_workspace/workspace/RD/flutter_im_portal_iOS_i/ios/Pods/Headers/Public/MBProgressHUD"
-isystem
"/Users/lianjia/Jenkins_workspace/workspace/RD/flutter_im_portal_iOS_i/ios/Pods/Headers/Public/SAMKeychain"
-isystem
"/Users/lianjia/Jenkins_workspace/workspace/RD/flutter_im_portal_iOS_i/ios/Pods/Headers/Public/SensorsAnalyticsSDK
" -isystem "/Users/lianjia/Jenkins_workspace/workspace/RD/flutter_im_portal_iOS_i/ios/Pods/Headers/Public/YYCache"
-isystem "/Users/lianjia/Jenkins_workspace/workspace/RD/flutter_im_portal_iOS_i/ios/Pods/Headers/Public/base"
-isystem
"/Users/lianjia/Jenkins_workspace/workspace/RD/flutter_im_portal_iOS_i/ios/Pods/Headers/Public/flutter_im_basic_pl
ugin"
OTHER_LDFLAGS =  -ObjC -l"AFNetworking" -l"CocoaLumberjack" -l"LJBBaseHttpService" -l"LJBBrokerBase"
-l"LJBase3rdFramework" -l"LJBaseRouter" -l"LJBaseToolKit" -l"LJBaseViewControllerComponents"
-l"LJBrokerCompileConfiguration" -l"LJEventTracting" -l"LJHTTPService" -l"LJMAlertView" -l"LJProgressHUDHelper"
-l"MBProgressHUD" -l"SAMKeychain" -l"SensorsAnalyticsSDK" -l"YYCache" -l"base" -l"c++" -l"flutter_im_basic_plugin"
-l"icucore" -l"sqlite3" -l"z" -framework "AVFoundation" -framework "AdSupport" -framework "CoreFoundation"
-framework "CoreGraphics" -framework "CoreLocation" -framework "CoreMotion" -framework "CoreTelephony" -framework
"Crashlytics" -framework "Fabric" -framework "Flutter" -framework "Foundation" -framework "LJBaseAppConfig"
-framework "LJNetworkService" -framework "MobileCoreServices" -framework "QuartzCore" -framework "Security"
-framework "SystemConfiguration" -framework "UIKit" -ObjC -l"AFNetworking" -l"CocoaLumberjack"
-l"LJBBaseHttpService" -l"LJBBrokerBase" -l"LJBase3rdFramework" -l"LJBaseRouter" -l"LJBaseToolKit"
-l"LJBaseViewControllerComponents" -l"LJBrokerCompileConfiguration" -l"LJEventTracting" -l"LJHTTPService"
-l"LJMAlertView" -l"LJProgressHUDHelper" -l"MBProgressHUD" -l"SAMKeychain" -l"SensorsAnalyticsSDK" -l"YYCache"
-l"base" -l"c++" -l"flutter_im_basic_plugin" -l"icucore" -l"sqlite3" -l"z" -framework "AVFoundation" -framework
"AdSupport" -framework "CoreFoundation" -framework "CoreGraphics" -framework "CoreLocation" -framework
"CoreMotion" -framework "CoreTelephony" -framework "Crashlytics" -framework "Fabric" -framework "Flutter"
-framework "Foundation" -framework "LJBaseAppConfig" -framework "LJNetworkService" -framework "MobileCoreServices"
-framework "QuartzCore" -framework "Security" -framework "SystemConfiguration" -framework "UIKit"
PACKAGE_TYPE = com.apple.package-type.wrapper.application
PASCAL_STRINGS = YES
PATH =
/Applications/Xcode10.1.app/Contents/Developer/usr/bin:/Users/lianjia/Documents/Software/flutter/bin:/Users/lianji
a/Document/Software/flutter/bin:$/Users/lianjia/Documents/Software/flutter/bin:/usr/local/bin:/usr/bin:/bin:/usr/s
bin:/sbin
PATH_PREFIXES_EXCLUDED_FROM_HEADER_DEPENDENCIES = /usr/include /usr/local/include /System/Library/Frameworks
/System/Library/PrivateFrameworks /Applications/Xcode10.1.app/Contents/Developer/Headers
/Applications/Xcode10.1.app/Contents/Developer/SDKs /Applications/Xcode10.1.app/Contents/Developer/Platforms
PBDEVELOPMENTPLIST_PATH = Runner.app/pbdevelopment.plist
PFE_FILE_C_DIALECTS = objective-c
PKGINFO_FILE_PATH =
/Users/lianjia/Library/Developer/Xcode/DerivedData/Runner-dtqiifbbyzywmherykgihurrqpri/Build/Intermediates.noindex
/Runner.build/Release-iphoneos/Runner.build/PkgInfo
PKGINFO_PATH = Runner.app/PkgInfo
PLATFORM_DEVELOPER_APPLICATIONS_DIR =
/Applications/Xcode10.1.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/Applications
PLATFORM_DEVELOPER_BIN_DIR =
/Applications/Xcode10.1.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/usr/bin
PLATFORM_DEVELOPER_LIBRARY_DIR =
/Applications/Xcode10.1.app/Contents/PlugIns/Xcode3Core.ideplugin/Contents/SharedSupport/Developer/Library
PLATFORM_DEVELOPER_SDK_DIR =
/Applications/Xcode10.1.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/SDKs
PLATFORM_DEVELOPER_TOOLS_DIR =
/Applications/Xcode10.1.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/Tools
PLATFORM_DEVELOPER_USR_DIR =
/Applications/Xcode10.1.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/usr
PLATFORM_DIR = /Applications/Xcode10.1.app/Contents/Developer/Platforms/iPhoneOS.platform
PLATFORM_DISPLAY_NAME = iOS
PLATFORM_NAME = iphoneos
PLATFORM_PREFERRED_ARCH = arm64
PLATFORM_PRODUCT_BUILD_VERSION = 16B91
PLIST_FILE_OUTPUT_FORMAT = binary
PLUGINS_FOLDER_PATH = Runner.app/PlugIns
PODS_BUILD_DIR = /Users/lianjia/Jenkins_workspace/workspace/RD/flutter_im_portal_iOS_i/build/ios
PODS_CONFIGURATION_BUILD_DIR =
/Users/lianjia/Jenkins_workspace/workspace/RD/flutter_im_portal_iOS_i/build/ios/Release-iphoneos
PODS_PODFILE_DIR_PATH = /Users/lianjia/Jenkins_workspace/workspace/RD/flutter_im_portal_iOS_i/ios/.
PODS_ROOT = /Users/lianjia/Jenkins_workspace/workspace/RD/flutter_im_portal_iOS_i/ios/Pods
PRECOMPS_INCLUDE_HEADERS_FROM_BUILT_PRODUCTS_DIR = YES
PRECOMP_DESTINATION_DIR =
/Users/lianjia/Library/Developer/Xcode/DerivedData/Runner-dtqiifbbyzywmherykgihurrqpri/Build/Intermediates.noindex
/Runner.build/Release-iphoneos/Runner.build/PrefixHeaders
PRESERVE_DEAD_CODE_INITS_AND_TERMS = NO
PRIVATE_HEADERS_FOLDER_PATH = Runner.app/PrivateHeaders
PRODUCT_BUNDLE_IDENTIFIER = com.example.flutterImPortal
PRODUCT_MODULE_NAME = Runner
PRODUCT_NAME = Runner
PRODUCT_SETTINGS_PATH =
/Users/lianjia/Jenkins_workspace/workspace/RD/flutter_im_portal_iOS_i/ios/Runner/Info.plist
PRODUCT_TYPE = com.apple.product-type.application
PROFILING_CODE = NO
PROJECT = Runner
PROJECT_DERIVED_FILE_DIR =
/Users/lianjia/Library/Developer/Xcode/DerivedData/Runner-dtqiifbbyzywmherykgihurrqpri/Build/Intermediates.noindex
/Runner.build/DerivedSources
PROJECT_DIR = /Users/lianjia/Jenkins_workspace/workspace/RD/flutter_im_portal_iOS_i/ios
PROJECT_FILE_PATH = /Users/lianjia/Jenkins_workspace/workspace/RD/flutter_im_portal_iOS_i/ios/Runner.xcodeproj
PROJECT_NAME = Runner
PROJECT_TEMP_DIR =
/Users/lianjia/Library/Developer/Xcode/DerivedData/Runner-dtqiifbbyzywmherykgihurrqpri/Build/Intermediates.noindex
/Runner.build
PROJECT_TEMP_ROOT =
/Users/lianjia/Library/Developer/Xcode/DerivedData/Runner-dtqiifbbyzywmherykgihurrqpri/Build/Intermediates.noindex
PROVISIONING_PROFILE_REQUIRED = YES
PUBLIC_HEADERS_FOLDER_PATH = Runner.app/Headers
RECURSIVE_SEARCH_PATHS_FOLLOW_SYMLINKS = YES
REMOVE_CVS_FROM_RESOURCES = YES
REMOVE_GIT_FROM_RESOURCES = YES
REMOVE_HEADERS_FROM_EMBEDDED_BUNDLES = YES
REMOVE_HG_FROM_RESOURCES = YES
REMOVE_SVN_FROM_RESOURCES = YES
RESOURCE_RULES_REQUIRED = YES
REZ_COLLECTOR_DIR =
/Users/lianjia/Library/Developer/Xcode/DerivedData/Runner-dtqiifbbyzywmherykgihurrqpri/Build/Intermediates.noindex
/Runner.build/Release-iphoneos/Runner.build/ResourceManagerResources
REZ_OBJECTS_DIR =
/Users/lianjia/Library/Developer/Xcode/DerivedData/Runner-dtqiifbbyzywmherykgihurrqpri/Build/Intermediates.noindex
/Runner.build/Release-iphoneos/Runner.build/ResourceManagerResources/Objects
SCAN_ALL_SOURCE_FILES_FOR_INCLUDES = NO
SCRIPTS_FOLDER_PATH = Runner.app/Scripts
SCRIPT_OUTPUT_STREAM_FILE =
/var/folders/8l/7g9mvtz51k7f5_c0m1nsv2780000gn/T/flutter_build_log_pipe.q7SsFe/pipe_to_stdout
SDKROOT =
/Applications/Xcode10.1.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS12.1.sdk
SDK_DIR =
/Applications/Xcode10.1.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS12.1.sdk
SDK_DIR_iphoneos12_1 =
/Applications/Xcode10.1.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS12.1.sdk
SDK_NAME = iphoneos12.1
SDK_NAMES = iphoneos12.1
SDK_PRODUCT_BUILD_VERSION = 16B91
SDK_VERSION = 12.1
SDK_VERSION_ACTUAL = 120100
SDK_VERSION_MAJOR = 120000
SDK_VERSION_MINOR = 100
SED = /usr/bin/sed
SEPARATE_STRIP = NO
SEPARATE_SYMBOL_EDIT = NO
SET_DIR_MODE_OWNER_GROUP = YES
SET_FILE_MODE_OWNER_GROUP = NO
SHALLOW_BUNDLE = YES
SHARED_DERIVED_FILE_DIR =
/Users/lianjia/Jenkins_workspace/workspace/RD/flutter_im_portal_iOS_i/build/ios/Release-iphoneos/DerivedSources
SHARED_FRAMEWORKS_FOLDER_PATH = Runner.app/SharedFrameworks
SHARED_PRECOMPS_DIR =
/Users/lianjia/Library/Developer/Xcode/DerivedData/Runner-dtqiifbbyzywmherykgihurrqpri/Build/Intermediates.noindex
/PrecompiledHeaders
SHARED_SUPPORT_FOLDER_PATH = Runner.app/SharedSupport
SKIP_INSTALL = NO
SOURCE_ROOT = /Users/lianjia/Jenkins_workspace/workspace/RD/flutter_im_portal_iOS_i/ios
SRCROOT = /Users/lianjia/Jenkins_workspace/workspace/RD/flutter_im_portal_iOS_i/ios
STRINGS_FILE_OUTPUT_ENCODING = binary
STRIP_BITCODE_FROM_COPIED_FILES = YES
STRIP_INSTALLED_PRODUCT = YES
STRIP_STYLE = all
STRIP_SWIFT_SYMBOLS = YES
SUPPORTED_DEVICE_FAMILIES = 1,2
SUPPORTED_PLATFORMS = iphonesimulator iphoneos
SUPPORTS_TEXT_BASED_API = NO
SWIFT_PLATFORM_TARGET_PREFIX = ios
SYMROOT = /Users/lianjia/Library/Developer/Xcode/DerivedData/Runner-dtqiifbbyzywmherykgihurrqpri/Build/Products
SYSTEM_ADMIN_APPS_DIR = /Applications/Utilities
SYSTEM_APPS_DIR = /Applications
SYSTEM_CORE_SERVICES_DIR = /System/Library/CoreServices
SYSTEM_DEMOS_DIR = /Applications/Extras
SYSTEM_DEVELOPER_APPS_DIR = /Applications/Xcode10.1.app/Contents/Developer/Applications
SYSTEM_DEVELOPER_BIN_DIR = /Applications/Xcode10.1.app/Contents/Developer/usr/bin
SYSTEM_DEVELOPER_DEMOS_DIR = /Applications/Xcode10.1.app/Contents/Developer/Applications/Utilities/Built Examples
SYSTEM_DEVELOPER_DIR = /Applications/Xcode10.1.app/Contents/Developer
SYSTEM_DEVELOPER_DOC_DIR = /Applications/Xcode10.1.app/Contents/Developer/ADC Reference Library
SYSTEM_DEVELOPER_GRAPHICS_TOOLS_DIR = /Applications/Xcode10.1.app/Contents/Developer/Applications/Graphics Tools
SYSTEM_DEVELOPER_JAVA_TOOLS_DIR = /Applications/Xcode10.1.app/Contents/Developer/Applications/Java Tools
SYSTEM_DEVELOPER_PERFORMANCE_TOOLS_DIR = /Applications/Xcode10.1.app/Contents/Developer/Applications/Performance
Tools
SYSTEM_DEVELOPER_RELEASENOTES_DIR = /Applications/Xcode10.1.app/Contents/Developer/ADC Reference
Library/releasenotes
SYSTEM_DEVELOPER_TOOLS = /Applications/Xcode10.1.app/Contents/Developer/Tools
SYSTEM_DEVELOPER_TOOLS_DOC_DIR = /Applications/Xcode10.1.app/Contents/Developer/ADC Reference
Library/documentation/DeveloperTools
SYSTEM_DEVELOPER_TOOLS_RELEASENOTES_DIR = /Applications/Xcode10.1.app/Contents/Developer/ADC Reference
Library/releasenotes/DeveloperTools
SYSTEM_DEVELOPER_USR_DIR = /Applications/Xcode10.1.app/Contents/Developer/usr
SYSTEM_DEVELOPER_UTILITIES_DIR = /Applications/Xcode10.1.app/Contents/Developer/Applications/Utilities
SYSTEM_DOCUMENTATION_DIR = /Library/Documentation
SYSTEM_KEXT_INSTALL_PATH = /System/Library/Extensions
SYSTEM_LIBRARY_DIR = /System/Library
TAPI_VERIFY_MODE = ErrorsOnly
TARGETED_DEVICE_FAMILY = 1,2
TARGETNAME = Runner
TARGET_BUILD_DIR =
/Users/lianjia/Jenkins_workspace/workspace/RD/flutter_im_portal_iOS_i/build/ios/Release-iphoneos
TARGET_NAME = Runner
TARGET_TEMP_DIR =
/Users/lianjia/Library/Developer/Xcode/DerivedData/Runner-dtqiifbbyzywmherykgihurrqpri/Build/Intermediates.noindex
/Runner.build/Release-iphoneos/Runner.build
TEMP_DIR =
/Users/lianjia/Library/Developer/Xcode/DerivedData/Runner-dtqiifbbyzywmherykgihurrqpri/Build/Intermediates.noindex
/Runner.build/Release-iphoneos/Runner.build
TEMP_FILES_DIR =
/Users/lianjia/Library/Developer/Xcode/DerivedData/Runner-dtqiifbbyzywmherykgihurrqpri/Build/Intermediates.noindex
/Runner.build/Release-iphoneos/Runner.build
TEMP_FILE_DIR =
/Users/lianjia/Library/Developer/Xcode/DerivedData/Runner-dtqiifbbyzywmherykgihurrqpri/Build/Intermediates.noindex
/Runner.build/Release-iphoneos/Runner.build
TEMP_ROOT =
/Users/lianjia/Library/Developer/Xcode/DerivedData/Runner-dtqiifbbyzywmherykgihurrqpri/Build/Intermediates.noindex
TOOLCHAIN_DIR = /Applications/Xcode10.1.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain
TREAT_MISSING_BASELINES_AS_TEST_FAILURES = NO
UID = 501
UNLOCALIZED_RESOURCES_FOLDER_PATH = Runner.app
UNSTRIPPED_PRODUCT = NO
USER = lianjia
USER_APPS_DIR = /Users/lianjia/Applications
USER_LIBRARY_DIR = /Users/lianjia/Library
USE_DYNAMIC_NO_PIC = YES
USE_HEADERMAP = YES
USE_HEADER_SYMLINKS = NO
VALIDATE_PRODUCT = YES
VALID_ARCHS = arm64 arm64e armv7 armv7s
VERBOSE_PBXCP = NO
VERBOSE_SCRIPT_LOGGING = YES
VERSIONING_SYSTEM = apple-generic
VERSIONPLIST_PATH = Runner.app/version.plist
VERSION_INFO_BUILDER = lianjia
VERSION_INFO_FILE = Runner_vers.c
VERSION_INFO_STRING = "@(#)PROGRAM:Runner  PROJECT:Runner-1"
WRAPPER_EXTENSION = app
WRAPPER_NAME = Runner.app
WRAPPER_SUFFIX = .app
WRAP_ASSET_PACKS_IN_SEPARATE_DIRECTORIES = NO
XCODE_APP_SUPPORT_DIR = /Applications/Xcode10.1.app/Contents/Developer/Library/Xcode
XCODE_PRODUCT_BUILD_VERSION = 10B61
XCODE_VERSION_ACTUAL = 1010
XCODE_VERSION_MAJOR = 1000
XCODE_VERSION_MINOR = 1010
XPCSERVICES_FOLDER_PATH = Runner.app/XPCServices
YACC = yacc
arch = arm64
variant = normal
 flutter_im_portal_iOS_i git:(rent/1.0.0) ✗ flutter doctor -v
[✓] Flutter (Channel stable, v1.2.1, on Mac OS X 10.14 18A391, locale zh-Hans-CN)
    • Flutter version 1.2.1 at /Users/lianjia/Documents/Software/flutter
    • Framework revision 8661d8aecd (4 weeks ago), 2019-02-14 19:19:53 -0800
    • Engine revision 3757390fa4
    • Dart version 2.1.2 (build 2.1.2-dev.0.0 0a7dcf17eb)

[✗] Android toolchain - develop for Android devices
    ✗ Unable to locate Android SDK.
      Install Android Studio from: https://developer.android.com/studio/index.html
      On first launch it will assist you in installing the Android SDK components.
      (or visit https://flutter.io/setup/#android-setup for detailed instructions).
      If Android SDK has been installed to a custom location, set ANDROID_HOME to that location.
      You may also want to add it to your PATH environment variable.

[✓] iOS toolchain - develop for iOS devices (Xcode 10.1)
    • Xcode at /Applications/Xcode10.1.app/Contents/Developer
    • Xcode 10.1, Build version 10B61
    • ios-deploy 1.9.4
    • CocoaPods version 1.5.3

[!] Android Studio (not installed)
    • Android Studio not found; download from https://developer.android.com/studio/index.html
      (or visit https://flutter.io/setup/#android-setup for detailed instructions).

[!] Connected device
    ! No devices available

! Doctor found issues in 3 categories.

my fault

my fault

so how did u solve this issue


Added Ethereum and linked to corresponding list

[Insert URL to the list here]
https://github.com/void4/awesome-ethereum
[Explain what this list is about and why it should be included here]
Ethereum is a Decentralized System like Bitcoin and Ripple. THe list of Decentralised System is incomplete without Etehreum
By submitting this pull request I confirm I've read and complied with the below requirements.
Please read it multiple times. I spent a lot of time on these guidelines and most people miss a lot.

I have read and understood the contribution guidelines and the instructions for creating a list.
This pull request has a descriptive title.For example, Add Name of List, not Update readme.md or Add awesome list.
The entry in the Awesome list should:

Include a short description about the project/theme of the list. It should not describe the list itself.Example: - [Fish](…) - User-friendly shell., not - [Fish](…) - Resources for Fish..
Be added at the bottom of the appropriate category.

The list I'm submitting complies with these requirements:

Has been around for at least 30 days.That means 30 days from either the first real commit or when it was open-sourced. Whatever is most recent.
It's the result of hard work and the best I could possibly produce.
Non-generated Markdown file in a GitHub repo.
Includes a succinct description of the project/theme at the top of the readme. (Example)
The repo should have awesome-list & awesome as GitHub topics. I encourage you to add more relevant topics.
Not a duplicate.
Only has awesome items. Awesome lists are curations of the best, not everything.
Includes a project logo/illustration whenever possible.

Placed at the top-right of the readme. (Example)
The image should link to the project website or any relevant website.
The image should be high-DPI. Set it to maximum half the width of the original image.

Entries have a description, unless the title is descriptive enough by itself. It rarely is though.
Includes the Awesome badge.

Should be placed on the right side of the readme heading.
Should link back to this list.

Has a Table of Contents section.

Should be named Contents, not Table of Contents.
Should be the first section in the list.
Should only have one level of sub-lists, preferably none.

Has an appropriate license.

That means something like CC0, not a code licence like MIT, BSD, Apache, etc.
If you use a license badge, it should be SVG, not PNG.

Has contribution guidelines.

The file should be named contributing.md. Casing is up to you.

Has consistent formatting and proper spelling/grammar.

Each link description starts with an uppercase character and ends with a period.Example: - [AVA](…) - JavaScript test runner.
Drop all the A / An prefixes in the descriptions.
Consistent and correct naming. For example, Node.js, not NodeJS or node.js.

Doesn't include a Travis badge.You can still use Travis for list linting, but the badge has no value in the readme.

Go to the top and read it again.

Please read the above guidelines point for point. Many things are not followed.

@deepusnath Ping