Usability improvements prototyping

Prototype and ask user feedback (lightweight UX testing) would the following changes improve the date picker usability:

[ ] tweak mouse scroll speed to less sensitive (issue origin) (#102)
[x] replace year scroll dots with month names (issue origin) (#138)

At the same time, consider adding another breakpoint above 375px and increase the width and font-size of the year scroller

[x] stack year numbers stacked more closely vertically (issue origin) (#138)
[ ] ARIA spec regarding year browse with keyboard shortcut (prototype if needed, issue origin) (Shift+Page Up/Down already work)
[ ] replace month grid with e.g. big year number overlay while scrolling (scrolling speed distracting eyesight, issue origin)

@jouni shouldn't we close these old issues because of inactivity also the context of the component has changed a lot since it was prototyped. We can open new feature tickets when we need them anyways.

Well, I suppose we can close them. I suppose all the important issues will resurface eventually, so there’s no point in keeping these open to “not forget”.


doc: add Medal

What type of PR is this?
/kind doc

What is the purpose of this PR and its related background?
add Medal
Which issue(s) this PR fixes:

Fixes #
Does this PR introduce a user-facing change?

 Codecov will compare coverage reports and display results in all future pull requests.
Thanks for integrating Codecov - We've got you covered :open_umbrella:


Coding help needed

I'm not sure this is the right place to ask for help, so please feel free to close this "issue" and redirect me to the correct place, but I didn't know where to go so that's how I ended up here.
I'm using deck.gl in combination with react-map-gl. For my application, I would like to add a draw control so the user can draw lines/polygons. I've noticed there are some pretty nice plugins written for this purpose already so rather than reinventing the wheel I wanted to try to include it in my current setup. It didn't take much effort to add an instance of mapbox-gl-draw to the controls of the mapbox underlying react-map-gl, but the .overlays div introduced by react-map-gl is preventing the controls from working. I've found that if I hide that div manually using the development tools of the browser to set visibility: hidden, everything works. Obviously, hiding that div hides the layers added by deck.gl, which is not what I want. My guess is that the click events that the draw controls needs to function are being intercepted, but I'm not sure that's the real reason why it's not working.
I know the uber team is not responsible for the draw control nor for how it works, and I'm not asking that you "fix" this - I just want to check if either deck or react-map-gl (or both) intercept click events (maybe it's mapcontrollerjs?) and if so, how I can modify this behavior. For my purpose, it would be acceptable to disable the controls of deck/react-map-gl when the application goes into some "user-drawing" state and to re-enable them when the user finishes. Is this possible at all? It would help me a lot if someone would point me in the right direction here because I can't seem to figure it out.
Thanks!

To follow up: I got things to work but the solution isn't pretty... So here's what I have currently:
<ReactMapGL>
    <DeckGL>
        <ReactMapGL ref={m => this.innerMap = m} className={'inner-map'}/>
    </DeckGL>
</ReactMapGL>

Then, in componentDidMount, I use the ref to add an instance of MapboxDraw to the map and register to the load event (which is fired when the styles are loaded) so I can access the layers, removing all of them except the ones that have an id starting with gl-draw (these are the layers that the draw component adds and needs to function).
        const innerMapRef = this.innerMap.getMap();
        innerMapRef.addControl(new MapboxDraw());
        innerMap.on('load' , e => {
                innerMap.getStyle().layers.forEach(l => {
                    if (!l.id.startsWith('gl-draw')) {
                        innerMap.setLayoutProperty(l.id, 'visibility', 'none')
                    }
                });
            }
        );

In the css file associated to the component, I add a css rule to ensure the inner map's canvas is rendered on top of the deck.gl layers and the underlying (outer) ReactMapGL's canvas.
.inner-map .mapboxgl-canvas {
    z-index: 1;
}

This setup basically creates a mapbox instance with no layers except the ones needed for the draw component at z-index 1. This breaks pointer-events for deck.gl, but to work around this, it makes sense to have the entire component switch states between "drawing" and "regular". In "regular" mode, pointer-events: none can be added to the same css selector as above to ensure pointer-events reach deck.
I'm glad it works, but I'm not really satisfied with how this works. I can't imagine this doesn't cause issues somewhere in the internals of these libraries... If anyone is interested, I could work towards uploading a working code example...

@Warkst These rendering canvases and libraries are independent, only the events input is shared, that's why there is no internal conflict, ideally deck.gl should support a drawing layer. For now we have no better solution.

Hi @jianhuang01, is there any news on supporting drawing on a deck?


resolves #226 add Pygments.pygments_version method to query underlying Pygments version

@mojavelinux do you have better ideas for method name? I don't want to call it Pygments.version to avoid confusion with Pygments::VERSION, though possibly even in current state it is too much confusing.
Pygments::underlying_version? Pygments::backend_version? Pygments::python_version (though this can be read as "version of Python itself that is used to run Pygments")

Since there's ambiguity in the naming, I think being explicit is the best strategy. So I recommend Pygments.pygments_version.


How to stop the server?

I would like to be able to stop  the server from a route, something like that:
import bottle

app = bottle.Bottle()

@bottle.route('/')
def index():
    return 'hello'

@bottle.route('/stop')
def stopit():
    # do cleanup here
    app.stop()       # the script should exit here

bottle.run(port=80)

but app.stop() is not defined.
How to stop a server from code?
Is there a stop function?
Or should we send a SIGKILL / SIGTERM ? Then is there a listener to do some final cleanup before the server stops?

The controlling part here is not bottle, but the server implementation. bottle.run() simply starts the selected wsgi-server and tells it to loop forever. Some have a shutdown method, but it is hard to get hold of it when using the run() convenience method and not start the server yourself. Most gracefully shutdown if they receive a SIGINT signal or encounter a SystemExit or KeyboardInterrupt exception. So, sys.exit() should do the trick.
That said, it is unusual to stop a server from within. You usually send a SIGINT from outside.
As for cleanup code: SIGINT triggers a KeyboardInterrupt in all running threads (if I remember correctly).  But there is no guarantee. Never rely on clean-up code to run before a process terminates.

Thank you for your answer. Last questions:

When using WSGIRefServer(), is there a way to call its stop method, and if so, how?

How to call your function close() https://github.com/bottlepy/bottle/blob/master/bottle.py#L864 from inside a route?

I tried sys.exit(0) from inside a route, but the Bottle app continues running

Here is the context (maybe you have an idea): https://stackoverflow.com/questions/61600356/how-to-commit-db-changes-in-a-flask-or-bottle-app-efficiently
I can't do SQLite db.commit() after each request (100ms  is too much when there are many clients) so I wanted to do once every 30 seconds, but I need to be sure that it happens if the server is stopped. So I need to be able to have a stop handler.

WSGIRefServer has many issues, one of them not providing a clean shutdown method. It even catches and ignores SIGINT in some situations, which is plain wrong. I do not know if they fixed that in recent releases. cheroot has proper start() and stop() methods.
Bottle.close() does not stop the server.  Bottle cannot stop it natively.

If you are concerned about 100ms for a blocking db.commit() perrequst then perhaps stop using a single-threaded WSGI server implementation (wsgiref)? You are optimising at the wrong end.

Thanks for your answer, I'll study this.
PS: It seems this has been added recently to Bottle: https://github.com/josephernest/bottle/blob/master/bottle.py#L3282
self.srv = make_server(self.host, self.port, app, server_cls,
                           handler_cls)

instead of
srv = make_server...

This is interesting because then we can simply do
server = bottle.WSGIRefServer(port=80)
bottle.run(server=server)

and this in a route:
server.srv.shutdown()

Is that correct?

Not a public or documented API, but that might work, yes. I'd still move away from wsgref as soon as possible.

Thanks for the advice @defnull. Last thing: what do you think of this solution found on stackoverflow:

I eventually found the solution was to do:
sys.stderr.close()

inside the request (that got passed up to the bottle server and axed it).

? I tried and it works indeed.

The solution I found is:
bottle is started with

run(app, reloader=False, host='<IP_ADDRESS>', debug=True, quiet=True, port=2020)

And shutdown of the server including release of the ports is done via:

import psutil
import signal
@app.route('/shutdown')
def shutdown():
# https://stackoverflow.com/a/60888399
current_process = psutil.Process()
current_process.send_signal(signal.SIGTERM)`

The solution I found is:
bottle is started with

run(app, reloader=False, host='<IP_ADDRESS>', debug=True, quiet=True, port=2020)

And shutdown of the server including release of the ports is done via:

import psutil
import signal
@app.route('/shutdown')
def shutdown():
# https://stackoverflow.com/a/60888399
current_process = psutil.Process()
current_process.send_signal(signal.SIGTERM)`


"toast-center-center" position?

May you provide such class for positioning in the center of page?

this has been requested, but its not on our radar. all pul requests have been situational, meaning they only work in certain circumstances, but not all. would only pull if it was foolproof. otherwise my advice is to add your own

.toast-center-center {
position: absolute;
top: 50%;
left: 50%;
-ms-transform: translateX(-50%) translateY(-50%);
-webkit-transform: translate(-50%,-50%);
transform: translate(-50%,-50%);
}


Readme for default template has a dead link

...for the Underscore Template Library -- I believe it should be pointing to http://underscorejs.org

Fixed on master and releases/3.4. Thanks for the heads up!


Select tags disabled in custom plugin

Hello @JiHong88 . Select tags were working fine in custom plugins, but now they seem to be disabled.
Steps to reproduce

Create a custom plugin with a select tag

The select functionality is disabled.

Hi @aderaHenry
It does mean the select tag is disabled in your custom plugin?

Yes JiHong. Select tags are disabled by default, in my custom plugin. I
can't seem to find a way to enable them. This came after the recent update.
Warmest regards,
Adera Henry
On Fri, Mar 27, 2020, 21:35 JiHong.Lee<EMAIL_ADDRESS>wrote:

Hi @aderaHenry https://github.com/aderaHenry
It does mean the select tag is disabled in your custom plugin?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/JiHong88/SunEditor/issues/302#issuecomment-605203556,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AK5762ERE7SULNKWIGNHW4DRJTWWDANCNFSM4LVFDCLA
.

The 2.28.1 version has been updated.
If this issue has not been resolved, please reopen this issue.
Thank you.

@JiHong88 this issue has not solved in v2.28.1


[model integration] add support for gemini models 12/13

It's shipped, but needs support for vision model

Currently Gemini Model Parser doesn't implement the serialize() method. This is a high priority.
Next steps is incorporating MultiModality for Gemini-pro-vision

Keeping this issue open. Couple of non priority items remain with Gemini, such as Multimodal.


Admin flags to disable individual Trusted Publisher providers

With #13551 we will support multiple IdPs for Trusted Publishers. PyPI admins should be able to disable individual providers via Admin flags.

I can prioritize this now that a few other providers are in flight -- are you thinking N + 1 flags total (N for each provider, plus 1 for trusted publishing as a whole)?

Yep, that's what I was thinking.

Opened #13871 for this.


Redmine #7318 None button for Traffic Graphs Widget filter

This implements the "None" button functionality on the Traffic Graphs widget, in the same way as proposed in #3653
This is a separate PR because it needs all the underlying code in the Traffic Graphs Widget to work in a similar way to the other widgets. That is in the following other PRs which are waiting for review/merging:
#3654 Traffic Graphs Widget whitespace
#3655 Traffic graph widget filter checkboxes
#3656 Traffic Graphs Widget handle no items selected for display
Those need to be merged first in order, then this one will show just a few lines of diff.

This will [should] easily port back to 2.3.*


Theming nits from bug bash

From 1.16.2142.0 bash on Aug 2nd

[x] Gap between inactive tabs and content

This might be related to the gap I was seeing in 2.8. Maybe fixing this (or at least understanding the root cause) might alleviate that issue as well.
Tracked upstream at: https://github.com/microsoft/microsoft-ui-xaml/issues/7674

[x] A light tabRow.BG in dark mode causes the chevron to be white:

fixed in #13871

[x] We need to remove useMica
[x] With "tab.background" set to "terminalBackground":

[x] Hover over a terminal tab -> the tab color doesn't change/give any visual feedback that it is being hovered over
[x] Hover over a settings tab -> the tab color does change/give visual feedback

[ ] With "tab.showCloseButton" set to "hover": Height of inactive tabs change upon hover - (can't seem to post a GIF in OneNote so try it yourself)

Mike couldn't repro this, so maybe someone else can?

[ ] There should be a bit more space to the right of the tab title to match the left side (next to icon)

additional

[ ] more...

note:
setting the bottom padding to -1 (0,0,0,-1) on this element:

(first tab has no line, second does)
seems to fix this, now I just have to find the right way to do that

Ah hecks no

The "thin line under the inactive tabs" repros even in the WinUI gallery. I'm betting that's out of our control. Great. I'll file upstream.

Apologies if this is not the right place to post this, but just wanted to add a +1 for There should be a bit more space to the right of the tab title to match the left side (next to icon) from the OP. The fact that tab titles are not centered with showCloseButton: never has been bugging me recently.
On a similar note, would it be feasible to remove the (erroneous?) straight line cutting through the rounded bottom left corner of each tab? This seems like it may be some kind of stray rendering artifact left over from when the tab is not active (if I'm seeing this right, the corner rounding is applied when the tab becomes active).

Just ran across this, and this issue has been quiet for a while. Is this still planned?


Does the UseOtlpExporter change prevent other Aspire components changing OTEL config?

The Seq Aspire component relies on the OTEL AddOtlpExporter method to extend telemetry configuration and this has now been made incompatible with the ServiceDefaults generated code (as UseOtlpExporter makes AddOtlpExporter throw an exception).
Is there a way that an Aspire component can extend the telemetry configuration?

cc @reyang

@liammclennan Are you trying to add additional OtlpExporters or change the settings for the ones added by Aspire?

@CodeBlanch to add additional OtlpExporters

@liammclennan You could do something like this: https://github.com/dotnet/aspire/compare/main...CodeBlanch:seq-otel-otlp-registration?expand=1
There is a slight behavioral difference when retrieving settings that way (I dropped a note about it in there) but otherwise it will work the same as calling the extension.

cc @eerhardt

@CodeBlanch thanks for putting that together.
Is there a way that can use the normal .NET configuration system? Given how much OpenTelemetry relies on configuration I think it would be hard to explain to consumers of the component why their OTEL configuration is not being applied.

@liammclennan - do you think that the Seq component can be updated to support this? If so, do you want to send a PR? We are in the middle of locking down for preview6. If we get a change quickly, it can still make 8.0.0 GA.
Or is the ask to change opentelemetry?

Hi @eerhardt! It just clicked over to Saturday here, so not sure whether @liammclennan will be online this morning, but I think it's fair to say we'll assemble a PR for preview6 with as much as we can get working (whether we're able to incorporate JSON configuration support or not).
This would likely be Monday in our time zone (so Sunday evening in yours), let me know if we'd miss the boat in that case 😄

Reopening to track backporting to release/8.0.


Searching for literal filename gives odd results

I can't seem to combine filename search (-g) with literal patterns (-Q) properly.
Here's what happens:
$ ls
*be     a    c
*bee    b

$ ag -gQ '*b'
1:contents of *b
2:

$ ag -gQ '*be'
ERR: Error stat()ing: *be
ERR: Error opening directory *be: No such file or directory

When what I'd expect to happen is:
$ ag -gQ '*b'
*b
*bee

$ ag -gQ '*be'
*bee

Not sure if this is an actual error or just me trying to do something that isn't implemented/supported. In the latter case, I guess we could call this a feature request instead of a bug report lol.

First, it looks like your example is wrong. I think you intended for ls to go like this:
$ ls
*b      a    c
*bee    b

Single-letter options that take arguments (like -g) will grab their arguments either from the remainder of the current option token or from the next option token, whichever comes first. This means that the argument to -g is Q, and *be is interpreted as a file name. You have no file named *be in your directory, which leads to the error about statting a file that doesn't exist.
To interpret the arguments correctly, you need to either specify the non-argument-accepting options first, as in ag -Qg '*b', or specify each argument separately, as in ag -g '*b' -Q.
However, if you try to do that, you'll get a different error:
$ ag -g '*b' -Q
ERR: Bad regex! pcre_compile() failed at position 0: nothing to repeat
If you meant to search for a literal string, run ag with -Q

This would suggest the -Q option doesn't work with -g. This is apparent in options.c; it doesn't consult the result of -Q before calling compile_study(file_search_regex, ...). That's the function that emits the message above suggesting to use -Q.

#1006 is opened regarding -Q not working with -g.


AndroidBuild

Hello,
I have some problems, could you please help me out?
I finish your tutorial and go to the next step AndroidBuild
I run
"lunch"
and it appears the menu like this
"    1. full-eng
2. full_x86-eng
3. vbox_x86-eng
"- only 3 options.
I chose 1 (also check with 2 and 3)
However, when I run "make clean && make ..."
the error shows
" PLATFORM_VERSION_CODENAME=REL
PLATFORM_VERSION=4.0.1
TARGET_PRODUCT=full
TARGET_BUILD_VARIANT=eng
TARGET_BUILD_TYPE=release
TARGET_BUILD_APPS=
TARGET_ARCH=arm
TARGET_ARCH_VARIANT=armv7-a
HOST_ARCH=x86
HOST_OS=linux
HOST_BUILD_TYPE=release
BUILD_ID=ITL41D
Checking build tools versions...
make: *** No rule to make target `opentee-engine'.  Stop.
"

The "no rule to make target...." error appears when the Android.mk files of opentee-engine are not visible in the android source tree you have.
Have you done the symlink step mentioned in the android tutorial?
The goal is to have the following directory structure
android_sourcetree/
------------------------->opentee/
------------------------------------->emulator/
------------------------------------->libtee/
etc....

The android make searches in all the subdirectories in it's root dir to find the makefiles for the specific modules mentioned.

Thanks for your reply,
I make a link already
I saw Android.mk in the following directory structure
(Android_Envi is the source)
/home/user/Android_Envi/Open-TEE
In my system, the directory structure look likes your mention:
Android_Envi
- Open-TEE
-emulator
- libtee
-Android.mk
etc.
I check and run it again. But it is still not work

This is weird.

Are you running all the commands from bash or from zsh? Only bash is compatible with the android build system for now.

Have you setup the following environment variables?
export ANDROID_ROOT="$HOME/Android_Envi"
$ANDROID_ROOT/prebuilts/misc/linux-x86/ccache/ccache -M 50G
source "$ANDROID_ROOT/build/envsetup.sh"

It seems weird that your sourcetree has only 3 lunch targets. Usually the official AOSP has >5 available. Have you tried with the AOSP tree as well?

I'm assuming you have synced opentee with the latest changes in the repos?

Thank you very much,
I have done all things which you mentioned but it still not working
I will re-setup my system, and do it again. I really want to work on TEE

Hello I am experiencing the following issue when I invoke make clean && make opentee-engine libManagerApi libInternalApi libLauncherApi libCommonApi libta_conn_test_app conn_test_app libtee
Which results in the following error:
Starting build with ninja
ninja: Entering directory `.'
ninja: error: unknown target 'opentee-engine'
build/core/ninja.mk:123: recipe for target 'ninja.intermediate' failed
make: *** [ninja.intermediate] Error 1

When I run lunch it outputs:
You're building on Linux

Lunch menu... pick a combo:
     1. aosp_arm-eng
     2. aosp_arm64-eng
     3. aosp_mips-eng
     4. aosp_mips64-eng
     5. aosp_x86-eng
     6. aosp_x86_64-eng

Which would you like? [aosp_arm-eng]

I have made a Symlink to Open-TEE project as opentee in my android_source folder. As mentioned above I have also set the environment variables inside of bash.
Any suggestions would be much appreciated.
Thanks.

For some reason it cannot find the Android.mk make file that contains the opentee-engine module. This file is in emulator/opentee-main/Android.mk and in each directory from $ANDROID_SOURCE_ROOT till opentee-main/ there should be an Android.mk file that instructs the build to continue to all subdirectories.
Can you do ls -la in your android_source/ folder  and then ls -laR android_source/Open-TEE/ so that the full structure is visible? If you just try to make libtee does it still fail?
I assume you run the lunch and make commands inside the android_source directory.

ls -la produces:
jorden@Phantom:~/Android/android_source$ ls -al
total 120
drwxrwxr-x  29 jorden jorden 4096 Sep 29 19:43 .
drwxrwxr-x   5 jorden jorden 4096 Sep 29 16:37 ..
drwxrwxr-x   3 jorden jorden 4096 Sep 29 12:03 abi
lrwxrwxrwx   1 jorden jorden   19 Sep 29 12:03 Android.bp -> build/soong/root.bp
drwxrwxr-x  19 jorden jorden 4096 Sep 29 12:03 art
drwxrwxr-x  12 jorden jorden 4096 Sep 29 12:03 bionic
drwxrwxr-x   3 jorden jorden 4096 Sep 29 12:03 bootable
lrwxrwxrwx   1 jorden jorden   26 Sep 29 12:03 bootstrap.bash -> build/soong/bootstrap.bash
drwxrwxr-x  10 jorden jorden 4096 Sep 29 12:03 build
drwxrwxr-x  18 jorden jorden 4096 Sep 29 15:31 .ccache
drwxrwxr-x  12 jorden jorden 4096 Sep 29 12:03 cts
drwxrwxr-x  10 jorden jorden 4096 Sep 29 12:03 dalvik
drwxrwxr-x   6 jorden jorden 4096 Sep 29 12:03 developers
drwxrwxr-x  21 jorden jorden 4096 Sep 29 12:03 development
drwxrwxr-x  11 jorden jorden 4096 Sep 29 12:03 device
drwxrwxr-x   3 jorden jorden 4096 Sep 29 12:03 docs
drwxrwxr-x 217 jorden jorden 4096 Sep 29 12:04 external
drwxrwxr-x  17 jorden jorden 4096 Sep 29 12:04 frameworks
drwxrwxr-x  13 jorden jorden 4096 Sep 29 12:04 hardware
drwxrwxr-x  17 jorden jorden 4096 Sep 29 12:04 libcore
drwxrwxr-x   5 jorden jorden 4096 Sep 29 12:04 libnativehelper
-r--r--r--   1 jorden jorden   87 Sep 29 12:03 Makefile
drwxrwxr-x   8 jorden jorden 4096 Sep 29 12:04 ndk
lrwxrwxrwx   1 jorden jorden   29 Sep 29 19:43 Open-TEE -> /home/jorden/Android/Open-TEE
drwxrwxr-x   4 jorden jorden 4096 Sep 29 16:43 out
drwxrwxr-x   9 jorden jorden 4096 Sep 29 12:04 packages
drwxrwxr-x   6 jorden jorden 4096 Sep 29 12:04 pdk
drwxrwxr-x  19 jorden jorden 4096 Sep 29 12:05 prebuilts
drwxrwxr-x   7 jorden jorden 4096 Sep 29 12:03 .repo
drwxrwxr-x  25 jorden jorden 4096 Sep 29 12:05 sdk
drwxrwxr-x  24 jorden jorden 4096 Sep 29 12:05 system
drwxrwxr-x   3 jorden jorden 4096 Sep 29 12:05 toolchain
drwxrwxr-x   3 jorden jorden 4096 Sep 29 12:05 tools

Then running ls -laR android_source/Open-TEE/ shows me the full structure as expected. I can post the output if you want but is large.
Yes I am running in the android_source folder. I have run lunch then make clean then make libtee I then get the following error:
Starting build with ninja
ninja: Entering directory `.'
ninja: error: unknown target 'libtee', did you mean 'libfec'?
build/core/ninja.mk:123: recipe for target 'ninja.intermediate' failed
make: *** [ninja.intermediate] Error 1

#### make failed to build some targets (23 seconds) ####

Any thoughts on why this might not build?
When I download the project with repo I did not use the -m developer.xml would this make a difference?

I always use the -m developer.xml option but it shouldn't make any difference. It's the same tree.
The Android.mk files in Open-TEE/ and Open-TEE/emulator should have
    LOCAL_PATH := $(my-dir)
    include $(call all-makefiles-under,$(LOCAL_PATH))

in them.

Both Android.mk have the exact content as shown above. The includes are when running make libtee are:
Checking build tools versions...
including ./abi/cpp/Android.mk ...
including ./art/Android.mk ...
including ./bionic/Android.mk ...
including ./bootable/recovery/Android.mk ...
including ./build/libs/host/Android.mk ...
including ./build/target/board/Android.mk ...
including ./build/target/product/security/Android.mk ...
including ./build/tools/Android.mk ...
including ./cts/Android.mk ...
including ./dalvik/Android.mk ...
including ./development/apps/BluetoothDebug/Android.mk ...
including ./development/apps/BuildWidget/Android.mk ...
including ./development/apps/CustomLocale/Android.mk ...
including ./development/apps/Development/Android.mk ...
including ./development/apps/DevelopmentSettings/Android.mk ...
including ./development/apps/Fallback/Android.mk ...
including ./development/apps/GestureBuilder/Android.mk ...
including ./development/apps/NinePatchLab/Android.mk ...
including ./development/apps/OBJViewer/Android.mk ...
including ./development/apps/SdkSetup/Android.mk ...
including ./development/apps/SettingInjectorSample/Android.mk ...
including ./development/apps/WidgetPreview/Android.mk ...
including ./development/apps/launchperf/Android.mk ...
including ./development/build/Android.mk ...
including ./development/cmds/monkey/Android.mk ...
including ./development/host/windows/prebuilt/usb/Android.mk ...
including ./development/ndk/Android.mk ...
including ./development/perftests/panorama/Android.mk ...
including ./development/samples/AccelerometerPlay/Android.mk ...
including ./development/samples/ActionBarCompat/Android.mk ...
including ./development/samples/AliasActivity/Android.mk ...
including ./development/samples/AndroidBeamDemo/Android.mk ...
including ./development/samples/ApiDemos/Android.mk ...
including ./development/samples/AppNavigation/Android.mk ...
including ./development/samples/BackupRestore/Android.mk ...
including ./development/samples/BasicGLSurfaceView/Android.mk ...
including ./development/samples/BluetoothChat/Android.mk ...
including ./development/samples/BluetoothHDP/Android.mk ...
including ./development/samples/BusinessCard/Android.mk ...
including ./development/samples/Compass/Android.mk ...
including ./development/samples/ContactManager/Android.mk ...
including ./development/samples/CubeLiveWallpaper/Android.mk ...
including ./development/samples/FixedGridLayout/Android.mk ...
including ./development/samples/HeavyWeight/Android.mk ...
including ./development/samples/HelloActivity/Android.mk ...
including ./development/samples/HelloEffects/Android.mk ...
including ./development/samples/Home/Android.mk ...
including ./development/samples/HoneycombGallery/Android.mk ...
including ./development/samples/JetBoy/Android.mk ...
including ./development/samples/KeyChainDemo/Android.mk ...
including ./development/samples/LunarLander/Android.mk ...
including ./development/samples/MultiResolution/Android.mk ...
including ./development/samples/MySampleRss/Android.mk ...
including ./development/samples/NotePad/Android.mk ...
including ./development/samples/Obb/Android.mk ...
including ./development/samples/RSSReader/Android.mk ...
including ./development/samples/RandomMusicPlayer/Android.mk ...
including ./development/samples/RenderScript/Android.mk ...
including ./development/samples/SampleSyncAdapter/Android.mk ...
including ./development/samples/SearchableDictionary/Android.mk ...
including ./development/samples/SimpleJNI/Android.mk ...
including ./development/samples/SipDemo/Android.mk ...
including ./development/samples/SkeletonApp/Android.mk ...
including ./development/samples/Snake/Android.mk ...
including ./development/samples/SoftKeyboard/Android.mk ...
including ./development/samples/SpellChecker/Android.mk ...
including ./development/samples/StackWidget/Android.mk ...
including ./development/samples/Support13Demos/Android.mk ...
including ./development/samples/Support4Demos/Android.mk ...
including ./development/samples/Support7Demos/Android.mk ...
including ./development/samples/SupportAppNavigation/Android.mk ...
including ./development/samples/SupportDesignDemos/Android.mk ...
including ./development/samples/SupportLeanbackDemos/Android.mk ...
including ./development/samples/ToyVpn/Android.mk ...
including ./development/samples/TtsEngine/Android.mk ...
including ./development/samples/USB/Android.mk ...
including ./development/samples/UiAutomator/Android.mk ...
including ./development/samples/Vault/Android.mk ...
including ./development/samples/VoiceRecognitionService/Android.mk ...
including ./development/samples/VoicemailProviderDemo/Android.mk ...
including ./development/samples/WeatherListWidget/Android.mk ...
including ./development/samples/WiFiDirectDemo/Android.mk ...
including ./development/samples/WiFiDirectServiceDiscovery/Android.mk ...
including ./development/samples/Wiktionary/Android.mk ...
including ./development/samples/WiktionarySimple/Android.mk ...
including ./development/samples/XmlAdapters/Android.mk ...
including ./development/samples/training/NsdChat/Android.mk ...
including ./development/testrunner/Android.mk ...
including ./development/tools/apkcheck/Android.mk ...
including ./development/tools/emulator/test-apps/SmokeTests/Android.mk ...
including ./development/tools/etc1tool/Android.mk ...
including ./development/tools/hosttestlib/Android.mk ...
including ./development/tools/idegen/Android.mk ...
including ./development/tools/line_endings/Android.mk ...
including ./development/tools/mkstubs/Android.mk ...
including ./development/tools/recovery_l10n/Android.mk ...
including ./development/tools/rmtypedefs/Android.mk ...
including ./development/tools/yuv420sp2rgb/Android.mk ...
including ./development/tutorials/MoarRam/Android.mk ...
including ./development/tutorials/NotepadCodeLab/Notepadv1/Android.mk ...
including ./development/tutorials/NotepadCodeLab/Notepadv1Solution/Android.mk ...
including ./development/tutorials/NotepadCodeLab/Notepadv2/Android.mk ...
including ./development/tutorials/NotepadCodeLab/Notepadv2Solution/Android.mk ...
including ./development/tutorials/NotepadCodeLab/Notepadv3/Android.mk ...
including ./development/tutorials/NotepadCodeLab/Notepadv3Solution/Android.mk ...
including ./development/tutorials/ReverseDebug/Android.mk ...
including ./device/asus/deb/dumpstate/Android.mk ...
including ./device/asus/deb/self-extractors/Android.mk ...
including ./device/asus/flo/Android.mk ...
including ./device/asus/fugu/Android.mk ...
including ./device/asus/grouper/Android.mk ...
including ./device/asus/tilapia/recovery/Android.mk ...
including ./device/asus/tilapia/self-extractors/Android.mk ...
including ./device/generic/goldfish/audio/Android.mk ...
including ./device/generic/goldfish/camera/Android.mk ...
including ./device/generic/goldfish/gps/Android.mk ...
including ./device/generic/goldfish/lights/Android.mk ...
including ./device/generic/goldfish/opengl/Android.mk ...
including ./device/generic/goldfish/power/Android.mk ...
including ./device/generic/goldfish/qemu-props/Android.mk ...
including ./device/generic/goldfish/qemud/Android.mk ...
including ./device/generic/goldfish/sensors/Android.mk ...
including ./device/generic/goldfish/vibrator/Android.mk ...
including ./device/google/accessory/arduino/Android.mk ...
including ./device/google/accessory/demokit/Android.mk ...
including ./device/google/atv/LeanbackSampleApp/Android.mk ...
including ./device/google/atv/sdk/Android.mk ...
including ./device/htc/flounder/Android.mk ...
including ./device/lge/hammerhead/Android.mk ...
including ./device/lge/mako/Android.mk ...
including ./device/moto/shamu/Android.mk ...
including ./device/sample/Android.mk ...
including ./device/samsung/manta/Android.mk ...
including ./docs/source.android.com/Android.mk ...
including ./external/aac/Android.mk ...
including ./external/android-clat/Android.mk ...
including ./external/ant-glob/Android.mk ...
including ./external/antlr/Android.mk ...
including ./external/apache-harmony/Android.mk ...
including ./external/apache-xml/Android.mk ...
including ./external/avahi/Android.mk ...
including ./external/bison/Android.mk ...
including ./external/blktrace/Android.mk ...
including ./external/boringssl/Android.mk ...
including ./external/bouncycastle/Android.mk ...
including ./external/bsdiff/Android.mk ...
including ./external/bzip2/Android.mk ...
including ./external/c-ares/Android.mk ...
including ./external/cblas/Android.mk ...
including ./external/ceres-solver/Android.mk ...
including ./external/chromium-libpac/Android.mk ...
including ./external/chromium_org/Android.mk ...
including ./external/clang/Android.mk ...
including ./external/compiler-rt/Android.mk ...
including ./external/conscrypt/Android.mk ...
including ./external/cryptsetup/Android.mk ...
including ./external/curl/Android.mk ...
including ./external/dbus-binding-generator/Android.mk ...
including ./external/dbus/Android.mk ...
including ./external/deqp/Android.mk ...
including ./external/dexmaker/Android.mk ...
including ./external/dhcpcd-6.8.2/Android.mk ...
including ./external/dhcpcd/Android.mk ...
including ./external/dnsmasq/Android.mk ...
including ./external/doclava/Android.mk ...
including ./external/droiddriver/Android.mk ...
including ./external/e2fsprogs/Android.mk ...
including ./external/easymock/Android.mk ...
including ./external/eclipse-windowbuilder/propertysheet/Android.mk ...
including ./external/eigen/Android.mk ...
including ./external/elfutils/Android.mk ...
including ./external/emma/Android.mk ...
including ./external/expat/Android.mk ...
including ./external/eyes-free/Android.mk ...
including ./external/f2fs-tools/Android.mk ...
including ./external/fdlibm/Android.mk ...
including ./external/fec/Android.mk ...
including ./external/fio/Android.mk ...
including ./external/flac/Android.mk ...
including ./external/freetype/Android.mk ...
including ./external/fsck_msdos/Android.mk ...
including ./external/gemmlowp/Android.mk ...
including ./external/giflib/Android.mk ...
including ./external/glide/Android.mk ...
including ./external/gmock/Android.mk ...
including ./external/google-breakpad/Android.mk ...
including ./external/google-fonts/carrois-gothic-sc/Android.mk ...
including ./external/google-fonts/coming-soon/Android.mk ...
including ./external/google-fonts/cutive-mono/Android.mk ...
including ./external/google-fonts/dancing-script/Android.mk ...
including ./external/google-tv-pairing-protocol/Android.mk ...
including ./external/gtest/Android.mk ...
including ./external/guava/Android.mk ...
including ./external/hamcrest/Android.mk ...
including ./external/harfbuzz_ng/Android.mk ...
including ./external/icu/Android.mk ...
including ./external/iproute2/Android.mk ...
including ./external/ipsec-tools/Android.mk ...
including ./external/iptables/Android.mk ...
including ./external/iputils/Android.mk ...
including ./external/iw/Android.mk ...
including ./external/jarjar/Android.mk ...
including ./external/javasqlite/Android.mk ...
including ./external/javassist/Android.mk ...
including ./external/jdiff/Android.mk ...
including ./external/jemalloc/Android.mk ...
including ./external/jhead/Android.mk ...
including ./external/jmdns/Android.mk ...
including ./external/jpeg/Android.mk ...
including ./external/jsilver/Android.mk ...
including ./external/jsmn/Android.mk ...
including ./external/jsoncpp/Android.mk ...
including ./external/jsr305/Android.mk ...
including ./external/junit/Android.mk ...
including ./external/ksoap2/Android.mk ...
including ./external/libavc/Android.mk ...
including ./external/libcap-ng/Android.mk ...
including ./external/libcap/Android.mk ...
including ./external/libchrome/Android.mk ...
including ./external/libchromeos/Android.mk ...
including ./external/libcxx/Android.mk ...
including ./external/libcxxabi/Android.mk ...
including ./external/libdaemon/Android.mk ...
including ./external/libdivsufsort/Android.mk ...
including ./external/libedit/Android.mk ...
including ./external/libevent/Android.mk ...
including ./external/libexif/Android.mk ...
including ./external/libgsm/Android.mk ...
including ./external/libhevc/Android.mk ...
including ./external/liblzf/Android.mk ...
including ./external/libmicrohttpd/Android.mk ...
including ./external/libmpeg2/Android.mk ...
including ./external/libnfc-nci/Android.mk ...
including ./external/libnfc-nxp/Android.mk ...
including ./external/libnl/Android.mk ...
including ./external/libogg/Android.mk ...
including ./external/libopus/Android.mk ...
including ./external/libpcap/Android.mk ...
including ./external/libphonenumber/Android.mk ...
including ./external/libpng/Android.mk ...
including ./external/libselinux/Android.mk ...
including ./external/libunwind/Android.mk ...
including ./external/libunwind_llvm/Android.mk ...
including ./external/libutf/Android.mk ...
including ./external/libvorbis/Android.mk ...
including ./external/libvpx/Android.mk ...
including ./external/libvterm/Android.mk ...
including ./external/libweave/libweave/Android.mk ...
including ./external/libxml2/Android.mk ...
including ./external/libyuv/Android.mk ...
including ./external/linux-tools-perf/Android.mk ...
including ./external/littlemock/Android.mk ...
including ./external/lldb/Android.mk ...
including ./external/llvm/Android.mk ...
including ./external/lohit-fonts/Android.mk ...
including ./external/ltrace/Android.mk ...
including ./external/lvm2/Android.mk ...
including ./external/lz4/Android.mk ...
including ./external/lzma/C/Android.mk ...
including ./external/lzma/xz-embedded/Android.mk ...
including ./external/markdown/Android.mk ...
including ./external/mdnsresponder/Android.mk ...
including ./external/mesa3d/Android.mk ...
including ./external/messageformat/Android.mk ...
including ./external/minijail/Android.mk ...
including ./external/mksh/Android.mk ...
including ./external/mockito/Android.mk ...
including ./external/mockwebserver/Android.mk ...
including ./external/modp_b64/Android.mk ...
including ./external/mp4parser/Android.mk ...
including ./external/mtpd/Android.mk ...
including ./external/nanohttpd/Android.mk ...
including ./external/nanopb-c/Android.mk ...
including ./external/naver-fonts/Android.mk ...
including ./external/netcat/Android.mk ...
including ./external/netperf/Android.mk ...
including ./external/neven/Android.mk ...
including ./external/nfacct/Android.mk ...
including ./external/nist-pkits/Android.mk ...
including ./external/noto-fonts/Android.mk ...
including ./external/oauth/core/src/main/java/Android.mk ...
including ./external/objenesis/Android.mk ...
including ./external/okhttp/Android.mk ...
including ./external/opencv/Android.mk ...
including ./external/opencv3/Android.mk ...
including ./external/owasp/sanitizer/Android.mk ...
including ./external/pcre/Android.mk ...
including ./external/pdfium/core/Android.mk ...
including ./external/pdfium/fpdfsdk/Android.mk ...
including ./external/ppp/pppd/Android.mk ...
including ./external/proguard/Android.mk ...
including ./external/protobuf/Android.mk ...
including ./external/regex-re2/Android.mk ...
including ./external/replicaisland/Android.mk ...
including ./external/rmi4utils/Android.mk ...
including ./external/robolectric/Android.mk ...
including ./external/rootdev/Android.mk ...
including ./external/safe-iop/Android.mk ...
including ./external/scrypt/Android.mk ...
including ./external/selinux/Android.mk ...
including ./external/sepolicy/Android.mk ...
including ./external/sfntly/Android.mk ...
including ./external/skia/Android.mk ...
including ./external/smali/baksmali/Android.mk ...
including ./external/smali/deodexerant/Android.mk ...
including ./external/smali/dexlib2/Android.mk ...
including ./external/smali/smali/Android.mk ...
including ./external/sonivox/Android.mk ...
including ./external/speex/Android.mk ...
including ./external/sqlite/android/Android.mk ...
including ./external/sqlite/dist/Android.mk ...
including ./external/squashfs-tools/Android.mk ...
including ./external/srtp/Android.mk ...
including ./external/stlport/Android.mk ...
including ./external/strace/Android.mk ...
including ./external/svox/Android.mk ...
including ./external/tagsoup/Android.mk ...
including ./external/tcpdump/Android.mk ...
including ./external/tinyalsa/Android.mk ...
including ./external/tinycompress/Android.mk ...
including ./external/tinyxml/Android.mk ...
including ./external/tinyxml2/Android.mk ...
including ./external/tlsdate/Android.mk ...
including ./external/toybox/Android.mk ...
including ./external/tremolo/Android.mk ...
including ./external/v8/Android.mk ...
including ./external/valgrind/Android.mk ...
including ./external/vixl/Android.mk ...
including ./external/vogar/Android.mk ...
including ./external/webp/Android.mk ...
including ./external/webrtc/Android.mk ...
including ./external/wpa_supplicant_8/Android.mk ...
including ./external/xmlrpcpp/Android.mk ...
including ./external/xmp_toolkit/Android.mk ...
including ./external/zlib/Android.mk ...
including ./external/zopfli/Android.mk ...
including ./external/zxing/Android.mk ...
including ./frameworks/av/camera/Android.mk ...
including ./frameworks/av/cmds/screenrecord/Android.mk ...
including ./frameworks/av/cmds/stagefright/Android.mk ...
including ./frameworks/av/drm/common/Android.mk ...
including ./frameworks/av/drm/drmserver/Android.mk ...
including ./frameworks/av/drm/libdrmframework/Android.mk ...
including ./frameworks/av/drm/mediadrm/plugins/clearkey/Android.mk ...
including ./frameworks/av/drm/mediadrm/plugins/mock/Android.mk ...
including ./frameworks/av/media/common_time/Android.mk ...
including ./frameworks/av/media/img_utils/Android.mk ...
including ./frameworks/av/media/libcpustats/Android.mk ...
including ./frameworks/av/media/libeffects/downmix/Android.mk ...
including ./frameworks/av/media/libeffects/factory/Android.mk ...
including ./frameworks/av/media/libeffects/loudness/Android.mk ...
including ./frameworks/av/media/libeffects/lvm/lib/Android.mk ...
including ./frameworks/av/media/libeffects/lvm/wrapper/Android.mk ...
including ./frameworks/av/media/libeffects/preprocessing/Android.mk ...
including ./frameworks/av/media/libeffects/proxy/Android.mk ...
including ./frameworks/av/media/libeffects/visualizer/Android.mk ...
including ./frameworks/av/media/libmedia/Android.mk ...
including ./frameworks/av/media/libmediaplayerservice/Android.mk ...
including ./frameworks/av/media/libnbaio/Android.mk ...
including ./frameworks/av/media/libstagefright/Android.mk ...
including ./frameworks/av/media/mediaserver/Android.mk ...
including ./frameworks/av/media/mtp/Android.mk ...
including ./frameworks/av/media/ndk/Android.mk ...
including ./frameworks/av/services/audioflinger/Android.mk ...
including ./frameworks/av/services/audiopolicy/Android.mk ...
including ./frameworks/av/services/camera/libcameraservice/Android.mk ...
including ./frameworks/av/services/medialog/Android.mk ...
including ./frameworks/av/services/soundtrigger/Android.mk ...
including ./frameworks/av/soundtrigger/Android.mk ...
including ./frameworks/av/tools/resampler_tools/Android.mk ...
including ./frameworks/base/Android.mk ...
including ./frameworks/compile/libbcc/Android.mk ...
including ./frameworks/compile/mclinker/Android.mk ...
including ./frameworks/compile/slang/Android.mk ...
including ./frameworks/ex/camera2/Android.mk ...
including ./frameworks/ex/common/Android.mk ...
including ./frameworks/ex/framesequence/Android.mk ...
including ./frameworks/ex/variablespeed/Android.mk ...
including ./frameworks/minikin/libs/minikin/Android.mk ...
including ./frameworks/minikin/sample/Android.mk ...
including ./frameworks/ml/Android.mk ...
including ./frameworks/multidex/Android.mk ...
including ./frameworks/native/cmds/atrace/Android.mk ...
including ./frameworks/native/cmds/bugreport/Android.mk ...
including ./frameworks/native/cmds/dumpstate/Android.mk ...
including ./frameworks/native/cmds/dumpsys/Android.mk ...
including ./frameworks/native/cmds/flatland/Android.mk ...
including ./frameworks/native/cmds/installd/Android.mk ...
including ./frameworks/native/cmds/ip-up-vpn/Android.mk ...
including ./frameworks/native/cmds/rawbu/Android.mk ...
including ./frameworks/native/cmds/service/Android.mk ...
including ./frameworks/native/cmds/servicemanager/Android.mk ...
including ./frameworks/native/libs/binder/Android.mk ...
including ./frameworks/native/libs/diskusage/Android.mk ...
including ./frameworks/native/libs/gui/Android.mk ...
including ./frameworks/native/libs/input/Android.mk ...
including ./frameworks/native/libs/ui/Android.mk ...
including ./frameworks/native/opengl/libagl/Android.mk ...
including ./frameworks/native/opengl/libs/Android.mk ...
including ./frameworks/native/opengl/tests/Android.mk ...
including ./frameworks/native/services/batteryservice/Android.mk ...
including ./frameworks/native/services/inputflinger/Android.mk ...
including ./frameworks/native/services/powermanager/Android.mk ...
including ./frameworks/native/services/sensorservice/Android.mk ...
including ./frameworks/native/services/surfaceflinger/Android.mk ...
including ./frameworks/opt/bitmap/Android.mk ...
including ./frameworks/opt/bluetooth/Android.mk ...
including ./frameworks/opt/calendar/Android.mk ...
including ./frameworks/opt/chips/Android.mk ...
including ./frameworks/opt/colorpicker/Android.mk ...
including ./frameworks/opt/datetimepicker/Android.mk ...
including ./frameworks/opt/emoji/Android.mk ...
including ./frameworks/opt/inputmethodcommon/Android.mk ...
including ./frameworks/opt/mms/Android.mk ...
including ./frameworks/opt/net/ethernet/Android.mk ...
including ./frameworks/opt/net/ims/Android.mk ...
including ./frameworks/opt/net/voip/Android.mk ...
including ./frameworks/opt/net/wifi/service/Android.mk ...
including ./frameworks/opt/photoviewer/Android.mk ...
including ./frameworks/opt/setupwizard/navigationbar/Android.mk ...
including ./frameworks/opt/telephony/Android.mk ...
including ./frameworks/opt/timezonepicker/Android.mk ...
including ./frameworks/opt/vcard/Android.mk ...
including ./frameworks/rs/Android.mk ...
including ./frameworks/support/Android.mk ...
FindEmulator: find: `frameworks/support/design/dummy': No such file or directory
FindEmulator: find: `frameworks/support/v17/leanback/dummy': No such file or directory
including ./frameworks/volley/Android.mk ...
including ./frameworks/webview/Android.mk ...
including ./frameworks/wilhelm/src/Android.mk ...
including ./frameworks/wilhelm/tests/Android.mk ...
including ./hardware/akm/AK8975_FS/akmdfs/Android.mk ...
including ./hardware/akm/AK8975_FS/libsensors/Android.mk ...
including ./hardware/broadcom/libbt/Android.mk ...
including ./hardware/broadcom/wlan/bcmdhd/Android.mk ...
including ./hardware/intel/audio_media/hdmi/Android.mk ...
including ./hardware/intel/bootstub/Android.mk ...
including ./hardware/intel/common/libmix/Android.mk ...
including ./hardware/intel/common/libstagefrighthw/Android.mk ...
including ./hardware/intel/common/libva/Android.mk ...
including ./hardware/intel/common/libwsbm/src/Android.mk ...
including ./hardware/intel/common/omx-components/Android.mk ...
including ./hardware/intel/common/utils/ISV/Android.mk ...
including ./hardware/intel/common/utils/ituxd/Android.mk ...
including ./hardware/intel/common/wrs_omxil_core/Android.mk ...
including ./hardware/intel/img/hwcomposer/Android.mk ...
including ./hardware/intel/img/libdrm/Android.mk ...
including ./hardware/intel/img/psb_headers/Android.mk ...
including ./hardware/intel/img/psb_video/Android.mk ...
including ./hardware/invensense/Android.mk ...
including ./hardware/libhardware/Android.mk ...
including ./hardware/libhardware_legacy/Android.mk ...
including ./hardware/qcom/audio/Android.mk ...
including ./hardware/qcom/bt/Android.mk ...
including ./hardware/qcom/display/Android.mk ...
including ./hardware/qcom/gps/Android.mk ...
including ./hardware/qcom/keymaster/Android.mk ...
including ./hardware/qcom/media/Android.mk ...
including ./hardware/qcom/power/Android.mk ...
including ./hardware/qcom/wlan/qcwcn/Android.mk ...
including ./hardware/ril/libril/Android.mk ...
including ./hardware/ril/librilutils/Android.mk ...
including ./hardware/ril/reference-ril/Android.mk ...
including ./hardware/ril/rild/Android.mk ...
including ./hardware/samsung_slsi/exynos5/Android.mk ...
including ./hardware/ti/omap3/Android.mk ...
including ./hardware/ti/omap4-aah/Android.mk ...
including ./hardware/ti/omap4xxx/Android.mk ...
including ./libcore/Android.mk ...
including ./libnativehelper/Android.mk ...
including ./ndk/Android.mk ...
including ./packages/apps/BasicSmsReceiver/Android.mk ...
including ./packages/apps/Bluetooth/Android.mk ...
including ./packages/apps/Browser2/Android.mk ...
including ./packages/apps/Calculator/Android.mk ...
including ./packages/apps/Calendar/Android.mk ...
including ./packages/apps/Camera/Android.mk ...
including ./packages/apps/Camera2/Android.mk ...
including ./packages/apps/CellBroadcastReceiver/Android.mk ...
including ./packages/apps/CertInstaller/Android.mk ...
including ./packages/apps/Contacts/Android.mk ...
including ./packages/apps/ContactsCommon/Android.mk ...
including ./packages/apps/DeskClock/Android.mk ...
including ./packages/apps/Dialer/Android.mk ...
including ./packages/apps/Email/Android.mk ...
including ./packages/apps/Exchange/Android.mk ...
including ./packages/apps/FMRadio/Android.mk ...
including ./packages/apps/Gallery/Android.mk ...
including ./packages/apps/Gallery2/Android.mk ...
including ./packages/apps/HTMLViewer/Android.mk ...
including ./packages/apps/KeyChain/Android.mk ...
including ./packages/apps/Launcher2/Android.mk ...
including ./packages/apps/Launcher3/Android.mk ...
including ./packages/apps/LegacyCamera/Android.mk ...
including ./packages/apps/ManagedProvisioning/Android.mk ...
including ./packages/apps/Mms/Android.mk ...
including ./packages/apps/Music/Android.mk ...
including ./packages/apps/MusicFX/Android.mk ...
including ./packages/apps/Nfc/Android.mk ...
including ./packages/apps/OneTimeInitializer/Android.mk ...
including ./packages/apps/PackageInstaller/Android.mk ...
including ./packages/apps/PhoneCommon/Android.mk ...
including ./packages/apps/Protips/Android.mk ...
including ./packages/apps/Provision/Android.mk ...
including ./packages/apps/QuickSearchBox/Android.mk ...
including ./packages/apps/Settings/Android.mk ...
including ./packages/apps/SoundRecorder/Android.mk ...
including ./packages/apps/SpareParts/Android.mk ...
including ./packages/apps/SpeechRecorder/Android.mk ...
including ./packages/apps/Stk/Android.mk ...
including ./packages/apps/Tag/Android.mk ...
including ./packages/apps/Terminal/Android.mk ...
including ./packages/apps/TvSettings/QuickSettings/Android.mk ...
including ./packages/apps/TvSettings/Settings/Android.mk ...
including ./packages/apps/UnifiedEmail/Android.mk ...
including ./packages/experimental/Android.mk ...
including ./packages/inputmethods/LatinIME/Android.mk ...
including ./packages/inputmethods/OpenWnn/Android.mk ...
including ./packages/providers/BookmarkProvider/Android.mk ...
including ./packages/providers/CalendarProvider/Android.mk ...
including ./packages/providers/ContactsProvider/Android.mk ...
including ./packages/providers/DownloadProvider/Android.mk ...
including ./packages/providers/MediaProvider/Android.mk ...
including ./packages/providers/PartnerBookmarksProvider/Android.mk ...
including ./packages/providers/TelephonyProvider/Android.mk ...
including ./packages/providers/TvProvider/Android.mk ...
including ./packages/providers/UserDictionaryProvider/Android.mk ...
including ./packages/screensavers/Basic/Android.mk ...
including ./packages/screensavers/PhotoTable/Android.mk ...
including ./packages/screensavers/WebView/Android.mk ...
including ./packages/services/Mms/Android.mk ...
including ./packages/services/Telecomm/Android.mk ...
including ./packages/services/Telephony/Android.mk ...
including ./packages/wallpapers/Basic/Android.mk ...
including ./packages/wallpapers/Galaxy4/Android.mk ...
including ./packages/wallpapers/HoloSpiral/Android.mk ...
including ./packages/wallpapers/LivePicker/Android.mk ...
including ./packages/wallpapers/MagicSmoke/Android.mk ...
including ./packages/wallpapers/MusicVisualization/Android.mk ...
including ./packages/wallpapers/NoiseField/Android.mk ...
including ./packages/wallpapers/PhaseBeam/Android.mk ...
including ./pdk/apps/HelloPDK/Android.mk ...
including ./pdk/apps/TestingCamera/Android.mk ...
including ./pdk/apps/TestingCamera2/Android.mk ...
including ./prebuilts/gcc/darwin-x86/aarch64/aarch64-linux-android-4.9/Android.mk ...
including ./prebuilts/gcc/darwin-x86/arm/arm-linux-androideabi-4.9/Android.mk ...
including ./prebuilts/gcc/linux-x86/aarch64/aarch64-linux-android-4.9/Android.mk ...
including ./prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.9/Android.mk ...
including ./prebuilts/misc/Android.mk ...
including ./prebuilts/ndk/Android.mk ...
including ./prebuilts/qemu-kernel/x86/pc-bios/Android.mk ...
including ./prebuilts/sdk/Android.mk ...
including ./prebuilts/tools/Android.mk ...
FindEmulator: find: `prebuilts/tools/android-arm': No such file or directory
including ./sdk/annotations/Android.mk ...
including ./sdk/avdlauncher/Android.mk ...
including ./sdk/dumpeventlog/Android.mk ...
including ./sdk/emulator/mksdcard/Android.mk ...
including ./sdk/eventanalyzer/Android.mk ...
including ./sdk/find_java/Android.mk ...
including ./sdk/find_lock/Android.mk ...
including ./sdk/hierarchyviewer/etc/Android.mk ...
including ./sdk/hierarchyviewer/src/Android.mk ...
including ./sdk/sdklauncher/Android.mk ...
including ./system/bt/Android.mk ...
including ./system/ca-certificates/Android.mk ...
including ./system/connectivity/apmanager/Android.mk ...
including ./system/connectivity/shill/Android.mk ...
including ./system/core/Android.mk ...
including ./system/extras/Android.mk ...
including ./system/firewalld/Android.mk ...
including ./system/gatekeeper/Android.mk ...
including ./system/keyguard/Android.mk ...
including ./system/keymaster/Android.mk ...
including ./system/media/audio_route/Android.mk ...
including ./system/media/audio_utils/Android.mk ...
including ./system/media/camera/src/Android.mk ...
including ./system/media/camera/tests/Android.mk ...
including ./system/nativepower/Android.mk ...
including ./system/netd/client/Android.mk ...
including ./system/netd/server/Android.mk ...
including ./system/peerd/Android.mk ...
including ./system/security/keystore-engine/Android.mk ...
including ./system/security/keystore/Android.mk ...
including ./system/security/softkeymaster/Android.mk ...
including ./system/tools/aidl/Android.mk ...
including ./system/update_engine/Android.mk ...
including ./system/vold/Android.mk ...
including ./system/weaved/Android.mk ...
including ./system/webservd/Android.mk ...
including ./tools/external/fat32lib/Android.mk ...

No sign of Open-TEE being included. So the Android.mk files in Open-TEE and Open-TEE/emulator are not being picked up by make.
Also my environment variables I set are:
export ANDROID_ROOT="$HOME/Android/android_source"
export USE_CCACHE=1
export CCACHE_DIR="$HOME/Android/android_source/.ccache"
$ANDROID_ROOT/prebuilts/misc/linux-x86/ccache/ccache -M 50G
source "$HOME/Android/android_source/build/envsetup.sh"

I'm really not sure what might be causing this. Could you rename your Open-TEE folder to just "opentee" ? It's a longshot but it might have an issue with caps or symbols like dash. I always named it just "opentee".

Deleted the symlink and recreated with name "opentee". I then run make clean then lunch then make libtee and it gave the following error:
Starting build with ninja
ninja: Entering directory `.'
ninja: error: unknown target 'libtee', did you mean 'libfec'?
build/core/ninja.mk:123: recipe for target 'ninja.intermediate' failed
make: *** [ninja.intermediate] Error 1

#### make failed to build some targets (34 seconds) ####

Again from inspecting the output from running make "opentee" does not appear.

I have tried to run and build this all on another machine of mine. It has a fresh install of Ubuntu 14.04 on and it still results in the same error as above when running make libtee. Any ideas?

I have it building and running just now. It appears that doing a symlink to opentee for me did not work. Instead I cloned Open-TEE directly into my android_source directory. Appears to be building. Weird...

It would be far-fetched but could you try with the cyanogenmod android tree? https://github.com/CyanogenMod/android
Here are some guides https://wiki.cyanogenmod.org/w/Development
Also try to run ./build/envsetup.sh from the android_source directory before doing lunch and make...  .  In case it doesn't recognize $HOME somehow.
If nothing works I'll redo the whole setup on my local machine during the weekend cause I'm busy now and try to debug this.

I tried to run envsetup.sh and place the symlink back but for me it didn't work. Currently pulling down the cyanogenMod source and I will try. I'll keep you posted.
Thank you for all your support so far it is very much appreciated :D

What operating system are you building on? I know that I had problems when I used zsh instead of bash in a similar case so I had to default to that. I always built on an Ubuntu x86_64 14.04 VM.

Ubuntu 14.04 LTS, 64-bit with Bash shell. Native install not on a VM but won't make a difference I am sure.  Will let you know the result of CM and I am happy to debug / try things for you if you need any assistance. :)

I have always had issues with symlinks in the Android tree once it is
outside of 'croot'. For small standalone projects it seems to work, but
when there are dependencies to other sub-projects within a project it seems
to fail. I have not really studied which pass and why, it is more of an
observation. So the "safe" option is to copy not link.
On Thu, Oct 1, 2015 at 5:09 PM, Jorden Whitefield<EMAIL_ADDRESS>wrote:

Ubuntu 14.04 LTS, 64-bit with Bash shell. Native install not on a VM but
won't make a difference I am sure. Will let you know the result of CM and I
am happy to debug / try things for you if you need any assistance. :)
—
Reply to this email directly or view it on GitHub
https://github.com/Open-TEE/project/issues/7#issuecomment-144738464.

@uberspot I have tried the same with CyanogenMod 12.1 and using the sym link it results in the same issue. It does work if I copy opentee in to the android_source root.

Hello everyone,
Like thinhlevinh I'm trying to build Open tee on Android but I'm using an Ubuntu 14.04 virtualbox.
I have some trouble during make command :
VirtualBox:~/android_source$ lunch
You're building on Linux
Lunch menu... pick a combo:
1. full-eng
2. full_x86-eng
3. vbox_x86-eng
I chose the third
then make clean && make opentee-engine pass without problem
But when I start to build libraries (libManagerApi libInternalApi libLauncherApi libCommonApi libta_conn_test_app) I have some issues :
VirtualBox:~/android_source$ make libManagerApi
PLATFORM_VERSION_CODENAME=REL
PLATFORM_VERSION=4.0.1
TARGET_PRODUCT=vbox_x86
TARGET_BUILD_VARIANT=eng
TARGET_BUILD_TYPE=release
TARGET_BUILD_APPS=
TARGET_ARCH=x86
TARGET_ARCH_VARIANT=x86
HOST_ARCH=x86
HOST_OS=linux
HOST_BUILD_TYPE=release
BUILD_ID=ITL41D
target  C: libManagerApi <= Open-TEE/emulator/manager/ext_storage_stream_api_posix.c
target  C: libManagerApi <= Open-TEE/emulator/manager/opentee_manager_storage_api.c
target  C: libManagerApi <= Open-TEE/emulator/manager/../internal_api/opentee_storage_common.c
target  C: libManagerApi <= Open-TEE/emulator/manager/io_thread.c
target  C: libManagerApi <= Open-TEE/emulator/manager/logic_thread.c
target  C: libManagerApi <= Open-TEE/emulator/manager/mainloop.c
target  C: libManagerApi <= Open-TEE/emulator/manager/ta_dir_watch.c
target  C: libManagerApi <= Open-TEE/emulator/manager/shm_mem.c
Open-TEE/emulator/manager/shm_mem.c: In function 'generate_random_path':
Open-TEE/emulator/manager/shm_mem.c:51: error: 'CLOCK_BOOTTIME' undeclared (first use in this function)
Open-TEE/emulator/manager/shm_mem.c:51: error: (Each undeclared identifier is reported only once
Open-TEE/emulator/manager/shm_mem.c:51: error: for each function it appears in.)
make: *** [out/target/product/vbox_x86/obj/SHARED_LIBRARIES/libManagerApi_intermediates/shm_mem.o] error 1
VirtualBox:~/android_source$
I have search on the web but nothing helped me.
Do you have an idea ?

shall take a look at it  next week

okay, it looks like those definitions have moved from libc/include/time.h to libc/kernel/common/linux/time.h
I don't have a proper dev env up at the moment so it'll take a little bit before I can try a fix. If anyone else feels up to the task please do :p


api v3 calls doesn't work

I use api v2 client in golang to do standard GET/SET/DELETE calls, which works fine, but I have problem with v3 client which returns me following error all the time:
context deadline exceeded
I've tried to verify v3 endpoints using etcdctl, but problem still exists (v2 calls works fine):
>> ETCDCTL_API=3 ./etcdctl  put foo bar
Returns:
No help topic for 'put'
In my OS ports 2382 and 4001 are in use, so I'm using following command to run etcd server:
./etcd --listen-peer-urls=http://localhost:2382 --advertise-client-urls http://localhost:2379 -listen-client-urls=http://localhost:2379
Any thoughts?

@jwierzbo You would need to run https://github.com/coreos/etcd/tree/release-2.3/etcdctlv3 if you run etcd 2.3.x.
Or I recommend to run etcd and etcdctl from our master branch.
Thanks.

I've binary pointed in documentation:
curl -L  https://github.com/coreos/etcd/releases/download/v2.3.6/etcd-v2.3.6-linux-amd64.tar.gz -o etcd-v2.3.6-linux-amd64.tar.gz
so etcdctlv3  can fix problem with CLI client but what about with golang v3 api (github.com/coreos/etcd/clientv3)?

Did you try clientv3 in release-2.3 branch or master branch? The v3 code and binaries in 2.3.6 was pre-alpha, which means it might contain a lot of bugs. But if you just want to try out, either 2.3.6 or master branch should work, although master branch clientv3 code is much more stable.
Thanks.

Everything works fine with version from master branch.
@gyuho thanks for help!
Closing

np!


[gitlab] Run less jobs by default on branch pipelines

What does this PR do?
Changes the Gitlab pipeline to run less jobs on branch pipelines by default (ARM and MacOS builds do not run by defaults. Unit tests still run on all platforms).
Exposes two new variables, RUN_ALL_BUILDS and RUN_KITCHEN_TESTS, to allow creating custom pipelines with or without some parts of the pipeline.
Updates the inv pipeline.run-all-tests (renamed inv pipeline.run) task to allow using these parameters.
Motivation
Lighten the load on our CI infrastructure.
Give more options to customize pipelines.
Describe how to test your changes
Tested: a branch pipeline, a branch pipeline with all builds, a branch pipeline with kitchen tests, a branch pipeline with both, a deploy pipeline.

Would it be possible to leave a single arm64 system-probe kitchen test job on by default? We added them to prevent us breaking arm64 on accident.

Would it be possible to leave a single arm64 system-probe kitchen test job on by default? We added them to prevent us breaking arm64 on accident.

I can re-add all of them if you'd like, since they do not use ARM runners themselves (only their dependency, tests_ebpf_arm64, uses it, and we always run it anyway because it's a unit test job).

LGTM, although the naming between "pipeline.trigger" and "pipeline.run" might be a bit confusing, since they are kind of synonyms...

I agree. I'm considering merging the two commands into one. I'll propose that in a follow-up PR.


Update http4s-blaze-client, http4s-client to 0.21.22

Updates

org.http4s:http4s-blaze-client
org.http4s:http4s-client

from 0.21.21 to 0.21.22.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.http4s" } ]

labels: library-update, semver-patch

Codecov Report

Merging #226 (3995561) into main (089419e) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #226   +/-   ##
=======================================
  Coverage   58.77%   58.77%
=======================================
  Files          30       30
  Lines         929      929
  Branches       59       59
=======================================
  Hits          546      546
  Misses        383      383

Continue to review full report at Codecov.

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


Cannot scroll on the backup page

On my device there is no scroll bar on the backup page. So I'm not able to see all options.
LineageOS 14.1 (Android 7.1.2)

I always had everything on one page on my test device so I never encountered that problem.
Will look into it as soon as I can.
Sent from my Google Nexus 5X using FastHub


webpack build error. Module not found: Can't resolve '@rrule-rust/lib-android-arm-eabi'

I don't know how to run this package, it reported errors in webpack packaging, and it also reported errors in my project running.

@shxlsp could you provide the full log including command which you used to install the package? Also please specify the OS version you use


Experimental Component - Structured List - Development

Development
A developer can discover and install the experimental component by following accessible documentation.

[ ] Add to carbon-components
[ ] Update website (add to the experimental section and update component status page)

Development
A developer can discover and install the experimental component by following accessible documentation.
-[ ] Add to carbon-components
-[ ] Update website (add to the experimental section and update component status page)

Design issue: https://app.zenhub.com/workspace/o/ibm/carbon-components/issues/1242
Sketch file: https://ibm.ent.box.com/file/332823096737

linked the wrong one to tag. have closed tag


Inconsistency: what is a "VPN" in OPNsense?

There are different services in OPNsense potentially having some properties of a VPN: IPsec, OpenVPN, L2TP, PPTP, PPPoE (?), PPP (?), etc. . Some of them are called "VPN" at different points of the GUI, but others are not:

The screen System: System logs: VPN shows L2TP, PPTP, and PPPoE, but not IPsec and OpenVPN
In the main section VPN there are only IPsec, OpenVPN, and L2TP configurable
PPTP and PPPoE are configured in the section Services

Suggestions:

Maybe PPTP should move from the Services to the VPN section?
I think PPP and PPPoE are not really considered VPN technologies (are they?). Maybe they should be called something like "dial-in services"?
The screen System: System logs: VPN should either contain also IPsec and OpenVPN logs, or should be renamed to something different than VPN. Also either PPP and PPPoE should be shown, or non of them.

Other suggestions/opinions?

PPTP is not secure, so it was just recently moved to Services to retain backwards compatibility. The VPN Diagnostics page still needs work as described in #461. L2TP I was also thinking of moving out of VPN, so there are only IPsec and OpenVPN as the true VPN solutions...
The pages have always been this way. By reordering the menu we've made these problems more visible and they will be cleaned up for 16.1 for sure.
PS: Some page names still have a "vpn_" prefix, but we'd like to avoid moving files as much as possible, it is risky as the pages may be called from various other pages, are registered in the ACL, etc.

@fichtner Technically speaking a VPN does not need to be secure. :wink: The traditional definition of a VPN does not require encryption, I would say... But from the point of usability I totally agree that PPTP should not be "promoted" as a VPN with similar features as IPsec.
What about renaming the System: System logs: VPN to System: System logs: Dial in services and removing PPTP and L2TP? The logs for these services could then go to the corresponding config section (like IPsec has it): Services: PPTP: Log file and VPN: L2TP: Log file

You're right, maybe as a sidestep to the whole debate we could actually call the VPN section "Secure VPN", but that is also a bit risky. The philosophy is to promote the best choices for VPN if users do not know it. If e.g. they know they need to use PPTP there is nothing that will stop them from using it. With that reasoning, it may be ok to leave VPN as OpenVPN and IPsec only.
The VPN Log will be split up, PPPoE goes to the PPPoE Service, PPTP to the PPTP Service and LT2P to the L2TP Service. The only reason I haven't done this yet is that the logs pages are all clones of each other and duplicate a lot of lines of code. Before adding new log pages, we should make sure we don't just copy them but reduce the code into a single template function/file maybe.

Sounds good to me! So let's close this issue, since #461 already deals with that topic?

Let's leave this open, I've deleted the task from the other ticket. Thanks. :)

One more thing regarding L2TP and PPTP: What about having a sub item in VPN called Legacy and putting L2TP and PPTP in there?

We'd need a sub-sub menu level for this to work with the current menu flow. We've added one for the current structure, pushing for one more will not make it much better, especially when there only one potential use case (as of now).

The DNS services (Forwarder, Resolver, Dynamic DNS) would also be a candidate... :wink:

DNS Filter and DynDNS (both types) have been merged into DNS Tools. DNS Resolver/Forwarder is a whole other story. The idea was to hide the one that isn't enabled and make a config setting to switch it and then finally merge the rest of the DNS Tools into the remaining item.

Small ending note: VPN is now again meant in the traditional sense of Virtual Private Network. Thus, it now has a globe icon. PPTP was moved back. Only IPsec and OpenVPN get a closed lock to indicate their secure status. L2TP and PPTP are unlocked. I hope that's clear now. :)


Which task do you want to work on?

[ ] Task 1
[ ] Task 2
[ ] Task 3
[ ] Task 4
[ ] Task 5
[ ] Task 6
[x] Unlisted Task

Expected behaviour

A hamburger menu on Arabic mobile view.
A drop-down menu on mobile view in Arabic on the main website.
Translate back to English.

Actual behaviour

No hamburger menu icon.
Can't translate to English once in Arabic.

What needs to be done?

Add missing hamburger icon in ar-index.html

Who want to work on this issue?
I would like to work on this

@BatoolMM @alswajiab please could you review

Thank you @Tammy-Ajoko, this is fantastic, we'll review it soon!

Good day. I am an outreachy applicant, and I would like to work on this issue.

@BatoolMM @alswajiab  Please can I work on this issue?

@Cadeau1 I'm already working on it

@Cadeau1 I'm already working on it

Okay


[BUG] OhHeyYouFoundMe missing

Acknowledgement of preliminary instructions

[X] I have read the preliminary instructions, and I am certain that my problem has not already been addressed.

What problem did you encounter?
So ive gotten bloxtrap to exploit in roblox with solara executor but for the executor to work I need to change the "OhHeyYouFoundMe" file to true. For some reason the code isnt anywhere to be found in the settings file and idk why its not showing up. I Thought maybe I forgot to download something or maybe I downloaded something wrong but even after redownloading bloxtrap I still cant find the code.

I remember that you don't need it set to true

You only need the channel to be set to LIVE

If you look in the commits, they removed it

Every video ive seen it says it needs to be set to true for a certain menu to show up that I dont have

Maybe im missing something

Just download the 2.5.2 version of bloxstrap


Can't resolve './types'

When importing the component I get below output from npm:
ERROR in ./node_modules/svelte-multiselect/dist/index.js 5:0-24
.Module not found: Error: Can't resolve './types' in '/var/www/html/orodata-website/node_modules/svelte-multiselect/dist'
Did you mean 'types.js'?
BREAKING CHANGE: The request './types' failed to resolve only because it was resolved as fully specified
(probably because the origin is strict EcmaScript Module, e. g. a module with javascript mimetype, a '*.mjs' file, or a '*.js' file where the package.json contains '"type": "module"').
The extension in the request is mandatory for it to be fully specified.
Add the extension to the request.

I am not using TypeScript and I see the types.js file exports an empty object.  How do I resolve this?

Could you post a StackBlitz repro? Would be good to know what package versions you're using.

Was a fresh install in a Laravel 8 environment with following package.json dependencies:
"scripts": {
        "dev": "mix",
        "development": "mix",
        "watch": "mix watch",
        "watch-poll": "mix watch -- --watch-options-poll=1000",
        "hot": "mix watch --hot",
        "prod": "mix --production",
        "production": "mix --production"
    },
    "devDependencies": {
        "@babel/core": "^7.16.0",
        "@babel/plugin-syntax-dynamic-import": "^7.8.3",
        "@babel/preset-env": "^7.16.0",
        "babel-loader": "^8.2.3",
        "laravel-mix": "^6.0.49",
        "laravel-mix-svelte": "^0.5.0",
        "lodash": "^4.17.19",
        "resolve-url-loader": "^3.1.0",
        "sass": "^1.32.13",
        "sass-loader": "^11.1.1",
        "svelte": "^3.1.0",
        "svelte-loader": "^2.13.4",
    },
    "dependencies": {
        "laravel-svelte-direct-mix": "0.0.1",
        "svelte-multiselect": "^10.1.0"
    }

Tried downgrading to v9, but did not work.  Have not used StackBlitz yet: will try this weekend and send you feedback.

Are you setting
"type": "module",

in your package.json?

+1 to this, I'm facing exactly the same issue

A fresh npm install solved it 🤔 weird, will look further into this to see what was triggering it

Ill add to this, I'm facing the same issue.
Changing export * from './types'; to export * from './types.js'; in both the dist/index.js and dist/index.d.ts fixes it.
Fresh install did not change anything for me.

I'm also hitting this error on an old project, same package.json as @Hmerman6006's example

same question

Are you setting
"type": "module",

in your package.json?

@janosh No I'm not
Thanks for the quick reply

i'm not firm on the details but i think Svelte is ESM-only at this point

Yeah but we're on Svelte 3, and this plugin used to work. I've even locked it back to version ^8.0 and no luck. Ah well, maybe someone finds something.


Need better documentation on Directline

We need documentation on

How directline works / what is it

I found the diagram under What is the DirectLine Channel anyway?  in this blog post  helpful

What is the relationship between DirectLine & Webchat?

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

ID: 8b093e81-4542-f9db-c79a-88b9b753d353
Version Independent ID: dd976121-5f44-2205-826b-186f1ae2fa72
Content: Connect a bot to Direct Line - Bot Service
Content Source: articles/bot-service-channel-connect-directline.md
Service: bot-service
Product: bot-framework
GitHub Login: @RobStand
Microsoft Alias: kamrani

This came up on StackOverflow today too: https://stackoverflow.com/questions/54515066/directline-and-webchatdifference-and-similarities/54525419

Added directline channel in web app bot   azure.Request to provide documentation on integrate Luis.ai to directline

New docs on Direct Line are here.


N30: Release, take 2

Part of #912
Netlify preview: https://sharp-aryabhata-9cc78b.netlify.app/news/030/
A contributor asked for a little more time to finish their section, so I reverted last night's release PR. Here it is again - changes from last night are:

Graphite section has been added to 'Tooling Updates' (the image was broken so I've fixed as part of this PR).
A few extra bullet points have been added to Bevy Cheatbook's section.
I snuck in a tweak to the formatting on horizontal rules, as it's been bothering me for months how cramped they look 😄

⏰ Planning to get this merged at around 9PM GMT (three and a half hours from now), assuming no issues found.

Going to have to push this back till tomorrow as I'm dealing with my second work callout of the evening... fun times 😅

I just noticed a broken link in the rafx post.
This:
[video demonstrating TAA](rafx-youtube-video)

should be:
[video demonstrating TAA][rafx-youtube-video]

I can PR this in a few hours (or feel free to slip it in if that's the easiest way to fix it.)

@aclysma: I'll just fix it here, thanks for the heads up!

I just noticed a broken link in the rafx post.

Nice catch! Might be good to set up some regex like \[[^\[\]]*?\]\([^()]*?\) to detect that as part of the build process, or at least as a step in the release process to check for that.

Basic concept worked on the terrain, and the mini working group transitioned
I'm not sure the beginning of this sentence makes sense?

Last couple of months saw great disappointment for the failed port to WGPU
should be
The last couple of months saw great disappointment for the failed port to WGPU


Update e2e test AMI

Issue #, if available:
Description of changes:
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/approve

/lgtm


Automatic PR from RestAPI-PR1160

Generated from RestAPI PR: https://github.com/Azure/azure-rest-api-specs/pull/1160

Codecov Report

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

@@           Coverage Diff           @@
##           master    #1180   +/-   ##
=======================================
  Coverage   55.42%   55.42%
=======================================
  Files        2226     2226
  Lines       61470    61470
=======================================
  Hits        34070    34070
  Misses      27400    27400

Continue to review full report at Codecov.

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

Doc only


Fix: Selected category moves to the top when category list size is under 8

Details

When category list length is under 8, selected category should remain its position in alphabetic order within the list. Otherwise, it moves to the top.
Fixed Issues

$ https://github.com/Expensify/App/issues/36912
PROPOSAL:
Tests

In OD, make sure the category list size is under 8
In ND, create a money request with any category
Verify the category list is sorted in alphabetic order, including the selected one
In OD, make sure the category list size is from 8 and above
In ND, verify selected category is on top of the list

[x] Verify that no errors appear in the JS console

Offline tests

NA
QA Steps

In OD, make sure the category list size is under 8
In ND, create a money request with any category
Verify the category list is sorted in alphabetic order, including the selected one
In OD, make sure the category list size is from 8 and above
In ND, verify selected category is on top of the list

[x] Verify that no errors appear in the JS console

PR Author Checklist

[x] I linked the correct issue in the ### Fixed Issues section above
[x] I wrote clear testing steps that cover the changes made in this PR

[x] I added steps for local testing in the Tests section
[x] I added steps for the expected offline behavior in the Offline steps section
[x] I added steps for Staging and/or Production testing in the QA steps section
[x] I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[x] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
[x] I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).

[x] I included screenshots or videos for tests on all platforms
[x] I ran the tests on all platforms & verified they passed on:

[x] Android: Native
[x] Android: mWeb Chrome
[x] iOS: Native
[x] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[x] MacOS: Desktop

[x] I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
[x] I followed proper code patterns (see Reviewing the code)

[x] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
[x] I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
[x] I verified that comments were added to code that is not self explanatory
[x] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[x] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method

[x] If any non-english text was added/modified, I verified the translation was requested/reviewed in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:

[x] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[x] I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is approved by marketing by adding the Waiting for Copy label for a copy review on the original GH to get the correct copy.
[x] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[x] I verified the JSDocs style guidelines (in STYLE.md) were followed

[x] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[x] I followed the guidelines as stated in the Review Guidelines
[x] I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
[x] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[x] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[x] I verified that if a function's arguments changed that all usages have also been updated correctly
[x] If any new file was added I verified that:

[x] The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory

[x] If a new CSS style is added I verified that:

[x] A similar style doesn't already exist
[x] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG))

[x] If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
[x] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[x] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[x] If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
[x] If the PR modifies the form input styles:

[x] I verified that all the inputs inside a form are aligned with each other.
[x] I added Design label so the design team can review the changes.

[x] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[x] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.

Screenshots/Videos

Android: Native

Android: mWeb Chrome

iOS: Native

iOS: mWeb Safari

MacOS: Chrome / Safari

MacOS: Desktop

@eVoloshchak please ignore this PR, It is a regression from another issue. So I will review it

Closing as discussed here. Please comment in the issue if you believe partial payment would be required.


Is it possible to have the explanations and the examples in English? Not-Chinese speaking people are not able to use this library

Is it possible to have the explanations and the examples in English?
Not-Chinese speaking people are not able to use this library.

Hello, thank you for your attention. It has not been translated into English for the moment.

Hello, thank you for your attention. It has not been translated into English for the moment.