AVIF not accepting alpha channel

Possible bug
Is this a possible bug in a feature of sharp, unrelated to installation?

[x] Running npm install sharp completes without error.
[x] Running node -e "require('sharp')" completes without error.

If you cannot confirm both of these, please open an installation issue instead.
Are you using the latest version of sharp?

[x] I am using the latest version of sharp as reported by npm view sharp dist-tags.latest.

If you cannot confirm this, please upgrade to the latest version and try again before opening an issue.
If you are using another package which depends on a version of sharp that is not the latest, please open an issue against that package instead.
What is the output of running npx envinfo --binaries --system --npmPackages=sharp --npmGlobalPackages=sharp?
System:
OS: Windows 10 10.0.22621
CPU: (16) x64 AMD Ryzen 7 5800X 8-Core Processor
Memory: 19.72 GB / 31.88 GB
Binaries:
Node: 20.7.0 - C:\Program Files\nodejs\node.EXE
npm: 10.1.0 - C:\Program Files\nodejs\npm.CMD
npmPackages:
sharp: ^0.32.6 => 0.32.6

What are the steps to reproduce?
Just try to convert a PNG with an alpha channel to AVIF.

What is the expected behaviour?
The AVIF retains the alpha channel from the PNG.

Please provide a minimal, standalone code sample, without other dependencies, that demonstrates this problem
sharp(pngFilePath).avif({ quality: 75, effort: 0 }).toBuffer()

Please provide sample image(s) that help explain this problem
Yes, I have tried this with WebP and it works flawlessly. I have tried carrying over the PNG metadata and extracting the alpha channel from the PNG and joining it into the AVIF but no luck.
Original Image:

Result Image (IMPORTANT: I took this screenshot in HDR so ignore the colours, thats not the issue here):

You can download the AVIF here: https://cdn.discordapp.com/attachments/1146047428873695322/1154067865750732821/google-logo-png-google-logo-icon-png-transparent-background-1000-3575646148.6b3b0c0ef03a9f158710.avif

The AVIF image provided looks OK to me.
{
  format: 'heif',
  width: 1000,
  height: 1000,
  space: 'srgb',
  channels: 4,
  depth: 'uchar',
  isProgressive: false,
  pages: 1,
  pagePrimary: 0,
  compression: 'av1',
  hasProfile: false,
  hasAlpha: true
}

$ heif-info google-logo-png-google-logo-icon-png-transparent-background-1000-3575646148.6b3b0c0ef03a9f158710.avif
MIME type: image/avif
main brand: avif
compatible brands: avif, mif1, miaf

image: 1000x1000 (id=1), primary
  color profile: nclx
  alpha channel: yes
  depth channel: no

I took this screenshot

Which software are you using to render the AVIF?

The AVIF image provided looks OK to me.
{
  format: 'heif',
  width: 1000,
  height: 1000,
  space: 'srgb',
  channels: 4,
  depth: 'uchar',
  isProgressive: false,
  pages: 1,
  pagePrimary: 0,
  compression: 'av1',
  hasProfile: false,
  hasAlpha: true
}

$ heif-info google-logo-png-google-logo-icon-png-transparent-background-1000-3575646148.6b3b0c0ef03a9f158710.avif
MIME type: image/avif
main brand: avif
compatible brands: avif, mif1, miaf

image: 1000x1000 (id=1), primary
  color profile: nclx
  alpha channel: yes
  depth channel: no

I took this screenshot

Which software are you using to render the AVIF?

Hm, you gave a good point on viewing it in other apps. I tried Brave and looked at it on my Mac and it interestingly seems fine. I have had images where the entire background is black which probably roots from the same issue within Windows 11's Pictures and File Explorer apps.
Perhaps it would be good to mention this in the docs to prevent further issues like this?

Thanks for confirming. Windows inability to render AVIF images is probably something for Microsoft (annual revenue: ~$200 billion) to be mentioning in their docs :sweat_smile:


Remove kubevirt-config from kubevirt admin rbac role

The kubevirt admin rbac role will be aggregated with the default
k8s admin role, which gives users access to the config-map.
related to #1105

virt-controller depends on being able to read this config. whatever role that takes needs read-access to kubevirt-config.

this patch doesn't impact virt-controller's ability to access the kube-config.  This just modifies the default user roles.

retest this please

Looks good.  I was converging on this same conclusion during my investigation.

retest this please

Are the CI issues fixed?  Can we retest this?

Are the CI issues fixed? Can we retest this?

The CI failures don't appear to be related to this patch. We just need someone to approve the patch and it can go in.


Handle node_shape in networkx

Fixes https://github.com/holoviz/hvplot/issues/521

Coverage decreased (-0.1%) to 75.151% when pulling 0f002a0eaa0f769165c856186c7267d7f066ddb9 on node_shape into b1809080c1e6457c66f2baedff6a714b17cb5164 on master.


Executing the test crashes

Describe the bug
Recently, vue/core has been used for vitest migration, but when I execute the command test-unit command on my computer, vitest will crash. I don’t know if other people have encountered this situation, which makes me very distressed, whether it is using webstorm , vscode, or the terminal will have this situation. This crash will occur during the execution of any unit test script.

Fatal error in , line 0
Check failed: result.second.

Reproduction

System Info
System:
    OS: macOS 13.2
    CPU: (8) arm64 Apple M2
    Memory: 517.91 MB / 16.00 GB
    Shell: 5.8.1 - /bin/zsh
  Binaries:
    Node: 16.16.0 - /usr/local/bin/node
    Yarn: 1.22.19 - /usr/local/bin/yarn
    npm: 8.11.0 - /usr/local/bin/npm
  Browsers:
    Chrome: 110.0.5481.177
    Safari: 16.3

pnpm 7.27.1
nodejs 16.16.0

Used Package Manager
pnpm
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
[X] The provided reproduction is a minimal reproducible example of the bug.

Can someone give me some help

@baiwusanyu-c I was hitting a similar stack trace using node 16.15 on macOs.
Updating to node 16.20 helped and I haven't seen this issue since.

thx !


image_type="photo" gives error

Hi, I was reading here https://github.com/Lukas0025/python-pixabay/blob/main/examples/advanceQuery.py
that I can basically use all the filters listed here https://pixabay.com/api/docs/
Is this right? I don't understand why if I use image_type="photo" gives error.
This is the error: TypeError: core.query() got an unexpected keyword argument 'image_type'
while the other filters works

Okay thanks. I also suppose that orientation is another parametr that is it not implemented yet? Could you please also add this parametr? Thanks

Orientation should by implemented. I not tested it now but it is in
documentation
https://python-pixabay.readthedocs.io/en/latest/classpixabay_1_1core_1_1core.html#a0a2c46c79c85013f6f48e705e2aac027
When i have time i check if it working.
Dne út 10. 1. 2023 17:23 uživatel giggioman00 @.***>
napsal:

Okay thanks. I also suppose that orientation is another parametr that is
it not implemented yet? Could you please also add this parametr? Thanks
—
Reply to this email directly, view it on GitHub
https://github.com/Lukas0025/python-pixabay/issues/8#issuecomment-1377521007,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACM7NGMMTTHTIY4ZDXUNQD3WRWEHJANCNFSM6AAAAAATW7NUYY
.
You are receiving this because you commented.Message ID:
@.***>

Yes you are right thanks.
Another question please. I'm trying to bulk download images from a list made of searches on Python, the only problem is that if a term gives 0 images, thw hole script stop working. I'm unsure how to check if the images results are 0 in order to skip to the next term, any tips on this please?
I blindly tried this with not much hope honestly, and indeed doesn't work
if len(search_results)==0:                     print(f"No results for term: {term}, skipping to the next term")                     continue                 # get len of hits len(space)                 print("{} hits for term: {}".format(len(search_results), term))


Return configurator itself from IExceptionConfigurator methods...

...so fluent configuration can be used

I intentionally avoid this style of return processing due to the inherited nature of these interfaces. It creates a mess down the road. So I'm going to say no to this one.


Frequent crashing

Issue Type: Bug
Any file or folder open with any number of windows.
App will crash frequently when window is brought to front, or not touched at all for a few minutes.
Close to unusable as the last open files are not remembered but a previous set is remembered for some reason.
 I had lots of other (non-code) windows open at the time. No crashing has occurred so far. I'll keep experimenting with it.
Thanks for your help.

@Anti-Widdershins so its a extension issue

It looks like my installation of VSCode (basic) was corrupted somehow. I gradually deleted all extensions but the C/C++ extension without having any effect on the crashing. At that point the extensions window hung up trying to connect to the web. I could not change it so I uninstalled VSCode. Interestingly, since then the VSCode-insiders version stopped crashing - some cross effect?
Trying to download the VSCode basic installer was fraught with difficulty because it was always corrupted (with antivirus turned off) regardless of which binary installation I tried to fetch. On the 12th attempt I got a clean download.
I've installed it and added two extensions and it doesn't crash.
Thanks very much for your assistance.


Banner display is repeatedly faulty in both view modes if banner overrides are used

Details view: Switching with arrow keys doesn't update the banner in all cases.
Grid view: Some games display a banner which should only be displayed for games more than 1 spot away.
To reproduce the issue:

At least 4 games are necessary:

Game 1: Library A, Source A*, Platform PC

Game 2: Library Playnite, Source B, Platform PC

Game 3: Library Playnite, Source C, Platform PC

Game 4: Library D, Source D, Platform PC

Additionally other games to be able to scroll and one of these games uses Source E.

No source banner override set for: A*, D

Source banner overrides set for: B, C, E

No other banner overrides than these 3 set.

Grid view: 4 games are displayed in each row.

Note: A = A* with different capitalization (I guess it doesn't affect it but in my opinion it's better to state all details).
Confirmed this issue for two themes: DH_Dawn, Harmony
Confirmed this issue for Theme Extras versions: 1.4.1 and 1.4.2
Details view:
If I use arrow keys to switch between these four games the two games being part of Playnite library always display the same banner.
If I cycle from top to bottom game 2 and 3 display the banner of game 2.
If I cycle from bottom to top game 3 and 2 display the banner of game 3.
Game 1 and 4 display their library banner without issues.
Grid view:
If the games are in view when switching to grid view the banners are displayed properly.
If the games are not in view (either because of selecting a game far away or because of scrolling to a different game and scrolling back) the banner display is faulty in some cases. It doesn't matter if arrow keys or mouse scrolling is used. It also doesn't matter how fast I'm scrolling. One of the two Playnite library games in between the two other libraries will sometimes display a banner which doesn't belong to itself or any of it's direct neighbors. It's similar to the details view issue but the distance between the game with the faulty banner and the next game with said banner is bigger.

Fixed via 8f3e24a8b1238f3fe8adbd1457313845c41e5c49


Project Manager: Remove project button cleanup

Brief description
Remove project does not have label so it may confuse people that it's meant for removing assets and tasks. And confimation dialog should expect project name as text instead of delete.
Changes

delete project button has label Delete project
delete confirmation dialog expect to enter project name instead of delete

Can we make the project name a warning RED color? Or have the Delete button be colored red?
Somehow I feel this particular dialog doesn't raise my stress indicators as much as it should for what it is actually capable of. :)
I want to feel the urgency like in this examples:

And to be more safer and fun, how about making this action to require more than 1 people to be done ?

So deleting projects will look like this? 🚀

We could sell the hardware then. vfx pipeline AND missile launch systems (used for project deletion)

I hope this is enough

Definitely looks much better to me!


BundleMon seems to fail for external contributions

Here's a recent commit where BundleMon job fails: https://github.com/Leaflet/Leaflet/runs/4930516600?check_suite_focus=true
Error:  create commit record: bad project credentials
{"error":"GitHub action<PHONE_NUMBER> should be \"in_progress\" status"}
Error:  Failed to create commit record
Error:  Unhandled error
Error: Failed to generate report
    at /home/runner/work/Leaflet/Leaflet/node_modules/bundlemon/lib/main/index.js:32:15
    at Generator.next (<anonymous>)
    at fulfilled (/home/runner/work/Leaflet/Leaflet/node_modules/bundlemon/lib/main/index.js:5:58)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
Error: Process completed with exit code 1.

Not sure what this means but probably worth investigating, or if it's expected, disabling the job if it can't run.

@LironEr do you have any idea what might be causing this exception?

Looks like it happens sporadically and for maintainer commits as well, not just contributors. Here's the latest occurrence: https://github.com/Leaflet/Leaflet/runs/4964248089?check_suite_focus=true
Error:  create commit record: bad project credentials
{"error":"GitHub action status should be \"in_progress\""}
Error:  Failed to create commit record
Error:  Unhandled error
Error: Failed to generate report
    at /home/runner/work/Leaflet/Leaflet/node_modules/bundlemon/lib/main/index.js:32:15
    at Generator.next (<anonymous>)
    at fulfilled (/home/runner/work/Leaflet/Leaflet/node_modules/bundlemon/lib/main/index.js:5:58)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
Error: Process completed with exit code 1.

One of the checks that the service does when running bundlemon in GitHub action (and without API key) is to check if the action that runs bundlemon is currently running (code)
Since yesterday I added some logs to check GitHub response in those cases, and it looks like there is another status that I should allow.
I just deployed a new code that allows the new status and I will continue to monitor it.

@jonkoops can we prevent running bundlemon without a PR?

Looks like it's working well now so we can close.

@jonkoops can we prevent running bundlemon without a PR?

Why? This can be useful (e.g. checking for wins when you're experimenting in a branch but not yet ready to submit a PR yet).

@mourner yesterday I get still the error, look into #7974, can you confirm that the error doesn't happen anymore since yesterday?

This can be useful

In general yes, but not if most of the times the run fails

@Falke-Design might be useful to link the specific run here so we can inspect any exceptions.

@jonkoops same as the other errors: https://github.com/Falke-Design/Leaflet/actions/runs/1802780798

BundleMon GitHub app is not installed on this repo (Falke-Design/Leaflet)

This seems to be the issue, we can guard against this by adding a check. I've opened up a PR (#7983).


client module should be redesing and refactor

https://github.com/naiteluo/mondrian/blob/3428d104ba5b18aa6a3308af27011f25b8146c23/packages/mondrian/src/data-manager/ws-client.ts#L24

done.


Missing protection against multiple inclusion

I think there should be some protection against multiple inclusion of the header file like this
#ifndef __ADAFRUIT_STMPE610_H__
#define __ADAFRUIT_STMPE610_H__
  ...
#endif

done


GEODE-7497: Check CQs prior to change authorizer

The QueryConfigurationService now requires an extra flag to determine,
in the presence of continuous queries, whether to update the configured
MethodInvocationAuthorizer and invalidate the CQ's internal cache or
throw an exception and abort the update.

Fixed minor warnings.
Added unit and distributed tests.
Updated docs for alter query-service command.
Added 'forceUpdate' flag to 'AlterQueryServiceFunction' and
'AlterQueryServiceCommand'.
Fixed 'AlterQueryServiceCommand' to always require the
'method-authorizer' parameter.

Thank you for submitting a contribution to Apache Geode.
In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:
For all changes:

[X] Is there a JIRA ticket associated with this PR? Is it referenced in the commit message?

[X] Has your PR been rebased against the latest commit within the target branch (typically develop)?

[X] Is your initial contribution a single, squashed commit?

[X] Does gradlew build run cleanly?

[X] Have you written or updated unit tests to verify your changes?

[ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?

Note:
Please ensure that once the PR is submitted, check Concourse for build issues and
submit an update to your PR as soon as possible. If you need help, please send an
email to<EMAIL_ADDRESS>

@DonalEvans @BenjaminPerryRoss

Thanks for reviewing @jhuynh1
Please find my answers below, inline for an easier follow-up.

I thought clearing the local cq cache was needed if we updated the cq context with the new authorizer.

The CQ will always pick up the latest configured authorizer, no matter wether the forceUpdate flag is set as true or false, this logic is part of the reset method invoked by CQs during the execution. See CqServiceImpl.evaluateQuery and ExecutionContext.reset.

If they have the old authorizer, why do we need to clear the cache?

If we don't clear the cache, the CQ won't be evaluated for those keys that are part of the cache, which can result in invoking onEvent instead of onError for the associated CqListener.

As an example, let's say the user has the CQ  SELECT * from /testRegion object WHERE object.getId() > -1 running in the cluster, the configured MethodInvocationAuthorizer allows getId to be invoked. Some time passes and the CQ internal cache builds up to improve performance.
At that point the user decides to install a new MethodInvocationAuthorizer that doesn't allow getId. If we don't invalidate the internal CQ cache, the engine will invoke onError for events that are not part of the internal cache (the CQ will be executed) and onEvent for those events that that are part of the internal cache (the CQ won't be executed), which is not consistent.
Long story short, by invalidating the internal cache we make sure the CQ will be re-executed for every event  no matter what, and the execution itself will result in error if the newly configured authorizer doesn't allow the execution of methods present in the CQ expression.
Hope it makes sense now, please let me know your thoughts.
Cheers.


Usage in the doc not working

I supposed that the usage in the readme was wrong.
  /**
   * @param Request $request
   */
  public function postValidate(Request $request)
  {
    $result = $this->validate($request, [
      'geetest_challenge' => 'geetest',
    ], [
      'geetest' => config('geetest.server_fail_alert')
    ]);
    if ($result) {
      return 'success';
    }
  }

A prompt will be shown by phpstorm that function validate is a void function. And this code did fail to work, it returns false even if I properly dealed with the captcha.
In fact, in laravel doc,

The validate method accepts an incoming HTTP request and a set of validation rules. If the validation rules pass, your code will keep executing normally; however, if validation fails, an exception will be thrown and the proper error response will automatically be sent back to the user. In the case of a traditional HTTP request, a redirect response will be generated, while a JSON response will be sent for AJAX requests.

Indeed I cannot found a usage like that.
I suppose, by any chance, a proper use should be like this,
    /**
     * @param Request $request
     * @return bool
     */
    private function geetestValidate(Request $request)
    {
        $this->validate($request, [
            'geetest_challenge' => 'geetest',
        ], [
            'geetest' => config('geetest.server_fail_alert')
        ]);
        return true;
    }

And this did work for me.
Regards.

Thanks, I've updated the document.


Bitly doesn't work with 2 factor auth

Ref: Conversation #4357 / Kevin

Should be OK now as using OAuth


SSLCertVerificationError: vehicle_info.py

I can't login successfully via python or via the integration in HA. The integration was previously working.
File "/Library/Frameworks/Python.framework/Versions/3.12/lib/python3.12/site-packages/aiohttp/connector.py", line 990, in _wrap_create_connection
raise ClientConnectorCertificateError(req.connection_key, exc) from exc
aiohttp.client_exceptions.ClientConnectorCertificateError: Cannot connect to host mobile.deneb.prod.infotainment.pdx.atieva.com:443 ssl:True [SSLCertVerificationError: (1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: unable to get local issuer certificate (_ssl.c:1000)')]

Wild theory, but check the clock on the machine where you're running HA? It's saying the SSL certificate is invalid. That certificate currently expires on December 12th. If you clock got badly out of sync that could explain it.

It looks like it might be something with my account. The curl worked and no issues. My MBPro clock is up to date. The same SSL error came back when I entered a null password to test.

Very weird. I get an actual error message back (Login call failed.invalid loginID or password) for invalid creds. I'd say give it a day to see if there's just a problem on Lucid's end, but do let us know if it doesn't resolve itself.

I just reenabled Passive Lock, reset the HA integration, and reauthenticated successfully. Embarrassingly, it must be something with my local environment. I had disabled passive lock earlier in the day and that is what broke the HA integration.
Any MacOS Python cleanup/reinstall guides you can recommend lol? ;)


[FR]: Support lockfile v9 and pnpm 9

What is the current behavior?
Error in fail: npm_translate_lock currently supports a maximum lock_version of 6.1, but found 9.0.

Describe the feature
PNPM dropped v9 today and it changes the lockfile version and a few other things. I'm just filing this change as a way to track when rules_js adopts the new lockfile format and supports the new version.
https://github.com/pnpm/pnpm/releases/tag/v9.0.0

looks like we are beta testing v2.0.0-alpha.0, would be nice if we can add pnpm 9 support in v2

Completed for rules_js 2.0: https://github.com/aspect-build/rules_js/pull/1679

Hey guys, I would suggest you amend the documentation per the third paragraph to reflect that this issue has been closed.

Thanks for the info @creatifcoding 🙏
See https://github.com/aspect-build/rules_js/pull/1882


Enhanced job filtering, status change observers, runnable dependencies

This pull request includes various new features. It addresses issues with job filtering, model enhancements, and query filters. Additionally, it introduces configurable retries, minimum duration between attempts, and status change observers.

Was this intended for your own fork? With all the namespace changes I can't tell if this was intended to upstream or not.

Oh I should have cleaned that up first sorry about that. Yeah we are using our fork in prod so changed the names so we could publish privately.
If you have any feedback outside of that, we can definitely clean that up before merging if it's something you think should be merged upstream.

I do really like a few things

skip a job - useful for some of use cases
delete all failed jobs - useful for a use case

Others look good as well - just can't think at the moment of an immediate use case in our situations.
I think if you've been running these changes in prod on your side, I'll feel more comfortable upstreaming.

We are new to prod, so we can wait on a merge until a bit more time has passed. I just wanted to get it on your radar.
One key feature I can point out is the isRunnable() function added to job options.
When isRunnable is defined, it allows RNQ to mark a job as skipped instead of failed when a dependency has not yet been met. Early in our testing, we saw jobs with network calls in them fail over and over when the device was offline, exhausting all configured retries almost immediately.
The isRunnable() function was devised to allow a job author to declare n dependencies by checking them in the function, then returning a boolean which indicates if all the jobs dependencies have been met. If RNQ receives a false from isRunnable() at runtime, the job is skipped with a skip reason added to the job object (similar to how failure reasons work).
Skipped jobs are then not processed and the worker function is not called. RNQ will then move onto the next job in the queue. The next time the queue runs (or the next batch of jobs fetched) the skipped jobs will be retried to see if isRunnable() returns true.
A couple of other experiments we wrote but ultimately stopped using once isRunnable() was implemented are the failureBehavior and minimumMillisBetweenAttempts. They were less than great solutions to the problem described above that I left in just incase they might be useful for someone else.
Happy to answer any questions.

Running in prod for a month or so now and the changes appear to be stable. No rush of course, just figured I'd shared the feedback.

Thanks - I could consider upstreaming, but as the PR is now with all the branding changes/rename/etc. We couldn't merge that as-is.

Yeah, great point. I will try to put some cycles on a clean PR without the HopDrive stuff in it over the next month.


Updated ReadMe

Thanks for the contribution, but I think the text in the README is clear enough as it currently is.


How can I get the file?

How can I get the file?
Is there a way to just generate and get the file? without showing the option to listen or submit?

Hi @robinhodemorais, thanks for your message. Theoretically, yes, I could program a feature with the option to download the voice message as a file. What exactly is your use case?


feat: proxy for mapbox

Summary

Addresses #718
Secure the access token on the backend by proxying requests to MapBox.
Cache the request for map tiles because that overwhelms the free tier allowance.

Works on localhost, but on staging, directions work but tiles don't 😭

My only theory rn is that staging didn't actually update the backend when I updated the tile proxy code, so I'm gonna try opening another PR on the same branch to get another fresh staging deployment

Interestingly, now it marks the staging deploy for this PR as In progress as well while #732 is deploying.

CORS 💀💀💀💀💀

Maybe not CORS 🤔

localhost response (13128-2) has a different size than the response from the backend on staging 🤔🤔🤔

When we're reading the image from mapbox, it's the correct size, but when we send the response, it's 20kb larger????

ok I kinda figured it out. The response is larger because it's base64 encoding the image. I manually verified this with base64 -w 0 and diff utilities on my machine, and had the suspicion this was the case after reading this: https://docs.aws.amazon.com/apigateway/latest/developerguide/api-gateway-payload-encodings.html and then opening both files in a text editor.

So I noticed that the request headers didn't have image/png explicitly under their Accept header, but it turns out we can't even change that via library code or anything because it's done from HTML img elements:

The base64 to binary conversion isn't being run as a response integration because we're using a lambda proxy.

Apparently not doing this will fix it.

But, this is done by default in the component we're using to wrap our lambda in an API gateway :(

FWIW, this is exactly what I was anticipating when you suggested proxying image requests from S3 lol. Dealing with encoding over Lambda is a headache, and why I like to have the browser do it when it fetches directly from S3 :^)

FWIW, this is exactly what I was anticipating when you suggested proxying image requests from S3 lol. Dealing with encoding over Lambda is a headache, and why I like to have the browser do it when it fetches directly from S3 :^)

This isn't even touching S3 yet, what I'm stuck on is literally just the thinnest proxy possible with no caching on our end.

P.S. If it's possible, I'd like to have a solution that doesn't involve editing the devops, because I don't like complexity there 🤓

I'm not sure this is possible with how the current solution is looking. One thing we could do is swap out our tile provider but keep the directions api integration, but I've tried ~20 tilesets so far and they all are worse than MapBox's. https://wiki.openstreetmap.org/wiki/Raster_tile_providers
Most of them have either not enough detail like the names of the buildings, or too much extraneous overlay info.

IT WORKS NOW!!!!!


fix dash escape

Fixes: https://github.com/ryboe/CSS3/issues/224
Inside of a character range, escape - to be treated literally instead of as [a-z] range notation in Oniguruma

I'm not sure what the next step for this is. How does this get "workflow approval" ?

It needs the approval of a maintainer to be merged. The maintainers work on this repository voluntarily, so sometimes it can take a little while until they have time to get to it.
That said, I think @argyleink will see this PR soon enough and he'll likely merge it since it's only a small change.

Got it; thank you! Didn't know if I needed to do something.


Detox Setup on Windows for Testing React Native Android Apps

We need to configure Detox on windows platform to run the test for react native apps on  android device.
Is there any support for this?

We tried to make the project as cross platform as we can, and it should support window, though we haven't tested it on Windows yet.
You are welcome to try and give us your feedback, In fact, I encourage you to be the first who tries. Your feedback will be very useful.

How will all the bash scripts work on Windows? @rotemmiz
Does it run in a cygwin/msys environment?
If not, we could look into using msys to run the non-JS portions of Detox. Another option is to use the Linux Subsystem for Windows.

IIRC there is no sh/bash related code on Android, we even got rid of the postinstall.sh script we had recently.

Hi. I folowed the getting started tutorial, intalled everything but when I try to do anything I get the message 'bash' not reconized

what is the command you used ?
Please provide the error log.

First I tried to run detox -h after I installed detox-cli. Everything was intalled.
There was no log. Just the message.

I am sorry, this is not enough for us to understand your issue.
what was the command you ran, and what was its output ?

I think I got it. detox-cli is not windows compatible.
https://github.com/wix/detox/blob/master/detox-cli/cli.sh
We'll need to work on that. In the meantime, to overcome this issue, you can use your test runner directly.
If you're using mocha, read its docs on how to use on Windows, but it should be something like mocha e2e --opts e2e\mocha.opts --configuration yourConfiguration

Or you can install bash shell on Windows 10
https://www.howtogeek.com/249966/how-to-install-and-use-the-linux-bash-shell-on-windows-10/

Any way, I'll use Linux. Was just trying on windows to see what would happen. Thanks for your answer!

After installing Windows 10 Bash (+ node), now I am getting unable to boot emulator error.
$ detox test -c android.emu.debug
node_modules/.bin/mocha e2e --opts e2e/mocha.opts --configuration android.emu.debug

detox info 11:45:52: server listening on localhost:50412...
  1) "before all" hook

  0 passing (3s)
  1 failing

  1) "before all" hook:
     Error: Can not boot Android Emulator with the name: 'Nexus_5X_API_25',
      make sure you choose one of the available emulators:
      at EmulatorDriver._callee3$ (node_modules/detox/lib/devices/EmulatorDriver.js:35:19)
      at tryCatch (node_modules/regenerator-runtime/runtime.js:65:40)
      at Generator.invoke [as _invoke] (node_modules/regenerator-runtime/runtime.js:303:22)
      at Generator.prototype.(anonymous function) [as next] (node_modules/regenerator-runtime/runtime.js:117:21)
      at step (node_modules/detox/lib/devices/EmulatorDriver.js:1:809)
      at node_modules/detox/lib/devices/EmulatorDriver.js:1:969

I have made one change to the detox/lib/devices/android/emulator.js build emulator path script, I changed "emulator" to "emulator.exe" in order to recognize the emulator path in the window bash terminal.
this.emulatorBin = path.join(Environment.getAndroidSDKPath(), 'tools', 'emulator');

to
this.emulatorBin = path.join(Environment.getAndroidSDKPath(), 'tools', 'emulator.exe');

The emulator name is correct.
Any Idea what needs to be changed in order to move forward from here..

run the same command with --loglevel verbose, paste the log here

running detox test -c android.emu.debug --loglevel verbose
detox test -c android.emu.debug --loglevel verbose
node_modules/.bin/mocha e2e --opts e2e/mocha.opts --configuration android.emu.debug --loglevel verbose

detox info 12:53:45: server listening on localhost:53063...
detox verb ws onOpen [object Object]
detox verb ws send: {"type":"login","params":{"sessionId":"3da23a9b-2a94-389f-2e85-98109b1b5767","role":"tester"},"messageId":0}
detox verb ws onMessage: {"type":"loginSuccess","params":{"sessionId":"3da23a9b-2a94-389f-2e85-98109b1b5767","role":"tester"},"messageId":0}
detox verb ws
detox verb 1: /mnt/c/Users/ram/AppData/Local/Android/sdk/tools/emulator.exe -list-avds --verbose
  1) "before all" hook

  0 passing (370ms)
  1 failing

  1) "before all" hook:
     Error: Can not boot Android Emulator with the name: 'Nexus_5X_API_25',
      make sure you choose one of the available emulators:
      at EmulatorDriver._callee3$ (node_modules/detox/lib/devices/EmulatorDriver.js:35:19)
      at tryCatch (node_modules/regenerator-runtime/runtime.js:65:40)
      at Generator.invoke [as _invoke] (node_modules/regenerator-runtime/runtime.js:303:22)
      at Generator.prototype.(anonymous function) [as next] (node_modules/regenerator-runtime/runtime.js:117:21)
      at step (node_modules/detox/lib/devices/EmulatorDriver.js:1:809)
      at node_modules/detox/lib/devices/EmulatorDriver.js:1:969

detox verb ws send: {"type":"cleanup","params":{"stopRunner":true},"messageId":1}

node node_modules/mocha/bin/mocha e2e --opts e2e/mocha.opts --configuration android.emu.debug

In Windows Terminal Not Bash the above command open the emulator. But I am not able to get the tests run.
verbose, indicates that the package is wrong,
com.awesomeproject.test,
I have the Test.java @
awesomeproject/android/app/src/androidTest/java/com/awesomeproject/Test.java
intially I had DetoxTest.java I changed it to Test.java after seeing the unknown package error. still I am getting the same unknown package error/exception.
node node_modules/mocha/bin/mocha e2e --opts e2e/mocha.opts --configuration android.emu.debug --loglevel verbose

detox info 13:10:55: server listening on localhost:53997...
detox verb ws onOpen [object Object]
detox verb ws send: {"type":"login","params":{"sessionId":"67eda7ec-4fb5-8c56-4aed-33456e047e22","role":"tester"},"messageId":0}
detox verb ws onMessage: {"type":"loginSuccess","params":{"sessionId":"67eda7ec-4fb5-8c56-4aed-33456e047e22","role":"tester"},"messageId":0}
detox verb ws
detox verb 1: C:\Users\ram\AppData\Local\Android\Sdk\tools\emulator.exe -list-avds --verbose
detox verb 1: stdout: Nexus_5X_API_25
detox verb 1: stdout:
detox verb Emulator stdout:  emulator: Android virtual device file at: C:\Users\ram\.android\avd\Nexus_5X_API_25.ini
detox verb Emulator stdout:  emulator: virtual device content at C:\Users\ram\.android\avd\Nexus_5X_API_25.avd
detox verb Emulator stdout:  emulator: virtual device config file: C:\Users\ram\.android\avd\Nexus_5X_API_25.avd/config.ini
detox verb Emulator stdout:  emulator: using core hw config path: C:\Users\ram\.android\avd\Nexus_5X_API_25.avd/hardware-qemu.ini
detox verb Emulator stdout:  emulator: Found AVD target API level: 25
detox verb Emulator stdout:  emulator: Read property file at C:\Users\ram\AppData\Local\Android\Sdk/system-images\android-25\google_apis_playstore\x86\/build.prop
detox verb Emulator stdout:  emulator: No boot.prop property file found.
detox verb Emulator stdout:  emulator: found skin 'nexus_5x' in directory: C:\Users\ram\AppData\Local\Android\Sdk\skins\
detox verb Emulator stdout:  emulator: autoconfig: -skin nexus_5x
detox verb Emulator stdout:  emulator: autoconfig: -skindir C:\Users\ram\AppData\Local\Android\Sdk\skins\
detox verb Emulator stdout:  emulator: autoconfig: -kernel C:\Users\ram\AppData\Local\Android\Sdk/system-images\android-25\google_apis_playstore\x86\/kernel-ranchu
detox verb Emulator stdout:  emulator: Target arch = 'x86'
detox verb Emulator stdout:  emulator: Auto-config: -qemu -cpu qemu32
detox verb Emulator stdout:  emulator: Auto-detect: Kernel image requires new device naming scheme.
detox verb Emulator stdout:  emulator: Auto-detect: Kernel does not support YAFFS2 partitions.
detox verb Emulator stdout:  emulator: autoconfig: -ramdisk C:\Users\ram\AppData\Local\Android\Sdk/system-images\android-25\google_apis_playstore\x86\/ramdisk.img
detox verb Emulator stdout:  emulator: Using initial system image: C:\Users\ram\AppData\Local\Android\Sdk/system-images\android-25\google_apis_playstore\x86\/system.img
detox verb Emulator stdout:  emulator: autoconfig: -data C:\Users\ram\.android\avd\Nexus_5X_API_25.avd/userdata-qemu.img
detox verb Emulator stdout:  emulator: autoconfig: -initdata C:\Users\ram\.android\avd\Nexus_5X_API_25.avd/userdata.img
detox verb Emulator stdout:  emulator: autoconfig: -cache C:\Users\ram\.android\avd\Nexus_5X_API_25.avd/cache.img
detox verb Emulator stdout:  emulator: autoconfig: -sdcard C:\Users\ram\.android\avd\Nexus_5X_API_25.avd/sdcard.img
detox verb Emulator stdout:  emulator: Physical RAM size: 1536MB
detox verb Emulator stdout:
detox verb Emulator stdout:  emulator: VM heap size 256MB is below hardware specified minimum of 384MB,setting it to that value
detox verb Emulator stdout:  emulator: System image is read only
detox verb Emulator stdout:  emulator: Found 1 DNS servers: <IP_ADDRESS>
detox verb Emulator stdout:  emulator: trying to load skin file 'C:\Users\ram\AppData\Local\Android\Sdk\skins\/nexus_5x/layout'
detox verb Emulator stdout:  emulator: CPU Acceleration: working
detox verb Emulator stdout:  emulator: CPU Acceleration status: HAXM version 6.2.1 (4) is installed and usable.
detox verb Emulator stdout:  emulator: GPU emulation enabled using 'host' mode
detox verb Emulator stdout:  emulator: Using default value for kernel Contiguous Memory Allocation.
detox verb Emulator stdout:  emulator: Found 1 DNS servers: <IP_ADDRESS>
detox verb Emulator stdout:  Content of hardware configuration file:
detox verb Emulator stdout:    hw.cpu.arch = x86
detox verb Emulator stdout:    hw.cpu.model = qemu32
detox verb Emulator stdout:    hw.cpu.ncore = 2
detox verb Emulator stdout:    hw.ramSize = 1536
detox verb Emulator stdout:    hw.screen = multi-touch
detox verb Emulator stdout:    hw.mainKeys = false
detox verb Emulator stdout:    hw.trackBall = false
detox verb Emulator stdout:    hw.keyboard = true
detox verb Emulator stdout:    hw.keyboard.lid = false
detox verb Emulator stdout:    hw.keyboard.charmap = qwerty2
detox verb Emulator stdout:    hw.dPad = false
detox verb Emulator stdout:    hw.rotaryInput = false
detox verb Emulator stdout:    hw.gsmModem = true
detox verb Emulator stdout:    hw.gps = true
detox verb Emulator stdout:    hw.battery = true
detox verb Emulator stdout:    hw.accelerometer = true
detox verb Emulator stdout:    hw.audioInput = true
detox verb Emulator stdout:    hw.audioOutput = true
detox verb Emulator stdout:    hw.sdCard = true
detox verb Emulator stdout:    hw.sdCard.path = C:\Users\ram\.android\avd\Nexus_5X_API_25.avd/sdcard.img
detox verb Emulator stdout:    disk.cachePartition = true
detox verb Emulator stdout:    disk.cachePartition.path = C:\Users\ram\.android\avd\Nexus_5X_API_25.avd/cache.img
detox verb Emulator stdout:    disk.cachePartition.size = 66m
detox verb Emulator stdout:    hw.lcd.width = 1080
detox verb Emulator stdout:    hw.lcd.height = 1920
detox verb Emulator stdout:    hw.lcd.depth = 16
detox verb Emulator stdout:    hw.lcd.density = 420
detox verb Emulator stdout:    hw.lcd.backlight = true
detox verb Emulator stdout:    hw.gpu.enabled = true
detox verb Emulator stdout:    hw.gpu.mode = host
detox verb Emulator stdout:    hw.gpu.blacklisted = no
detox verb Emulator stdout:    hw.initialOrientation = Portrait
detox verb Emulator stdout:    hw.camera.back = emulated
detox verb Emulator stdout:    hw.camera.front = emulated
detox verb Emulator stdout:    vm.heapSize = 384
detox verb Emulator stdout:    hw.sensors.light = true
detox verb Emulator stdout:    hw.sensors.pressure = true
detox verb Emulator stdout:    hw.sensors.humidity = true
detox verb Emulator stdout:    hw.sensors.proximity = true
detox verb Emulator stdout:    hw.sensors.magnetic_field = true
detox verb Emulator stdout:    hw.sensors.orientation = true
detox verb Emulator stdout:    hw.sensors.temperature = true
detox verb Emulator stdout:    hw.useext4 = true
detox verb Emulator stdout:    kernel.path = C:\Users\ram\AppData\Local\Android\Sdk/system-images\android-25\google_apis_playstore\x86\/kernel-ranchu
detox verb Emulator stdout:    kernel.newDeviceNaming = yes
detox verb Emulator stdout:    kernel.supportsYaffs2 = no
detox verb Emulator stdout:    disk.ramdisk.path = C:\Users\ram\AppData\Local\Android\Sdk/system-images\android-25\google_apis_playstore\x86\/ramdisk.img
detox verb Emulator stdout:    disk.systemPartition.initPath = C:\Users\ram\AppData\Local\Android\Sdk/system-images\android-25\google_apis_
detox verb Emulator stdout:  playstore\x86\/system.img
detox verb Emulator stdout:    disk.systemPartition.size = 2g
detox verb Emulator stdout:    disk.dataPartition.path = C:\Users\ram\.android\avd\Nexus_5X_API_25.avd/userdata-qemu.img
detox verb Emulator stdout:    disk.dataPartition.size = 800m
detox verb Emulator stdout:    disk.encryptionKeyPartition.path = C:\Users\ram\.android\avd\Nexus_5X_API_25.avd/encryptionkey.img
detox verb Emulator stdout:    PlayStore.enabled = true
detox verb Emulator stdout:    avd.name = Nexus_5X_API_25
detox verb Emulator stdout:  .
detox verb Emulator stdout:  QEMU options list:
detox verb Emulator stdout:  emulator: argv[00] = "C:\Users\ram\AppData\Local\Android\Sdk\emulator/qemu/windows-x86_64/qemu-system-i386.exe"
detox verb Emulator stdout:  emulator: argv[01] = "-no-audio"
detox verb Emulator stdout:  emulator: argv[02] = "-dns-server"
detox verb Emulator stdout:  emulator: argv[03] = "<IP_ADDRESS>"
detox verb Emulator stdout:  emulator: argv[04] = "-serial"
detox verb Emulator stdout:  emulator: argv[05] = "null"
detox verb Emulator stdout:  emulator: argv[06] = "-cpu"
detox verb Emulator stdout:  emulator: argv[07] = "android32"
detox verb Emulator stdout:  emulator: argv[08] = "-enable-hax"
detox verb Emulator stdout:  emulator: argv[09] = "-smp"
detox verb Emulator stdout:  emulator: argv[10] = "cores=2"
detox verb Emulator stdout:  emulator: argv[11] = "-m"
detox verb Emulator stdout:  emulator: argv[12] = "1536"
detox verb Emulator stdout:  emulator: argv[13] = "-lcd-density"
detox verb Emulator stdout:  emulator: argv[14] = "420"
detox verb Emulator stdout:  emulator: argv[15] = "-kernel"
detox verb Emulator stdout:  emulator: argv[16] = "C:\Users\ram\AppData\Local\Android\Sdk/system-images\android-25\google_apis_playstore\x86\/kernel-ranchu"
detox verb Emulator stdout:  emulator: argv[17] = "-initrd"
detox verb Emulator stdout:  emulator: argv[18] = "C:\Users\ram\AppData\Local\Android\Sdk/system-images\android-25\google_apis_playstore\x86\/ramdisk.img"
detox verb Emulator stdout:  emulator: argv[19] = "-object"
detox verb Emulator stdout:  emulator: argv[20] = "iothread,id=disk-iothread"
detox verb Emulator stdout:  emulator: argv[21] = "-drive"
detox verb Emulator stdout:  emulator: argv[22] = "if=none,overlap-check=none,cache=unsafe,index=0,id=system,file=C:\Users\ram\.android\avd\Nexus_5X_API_25.avd\system.img.qcow2,read-only"
detox verb Emulator stdout:  emulator: argv[23] = "-device"
detox verb Emulator stdout:  emulator: argv[24] = "virtio-blk-pci,drive=system,iothread=disk-iothread,modern-pio-notify"
detox verb Emulator stdout:  emulator: argv[25] = "-drive"
detox verb Emulator stdout:  emulator: argv[26] = "if=none,overlap-check=none,cache=unsafe,index=1,id=cache,file=C:\Users\ram\.android\avd\Nexus_5X_API_25.avd/cache.img.qcow2,l2-cache-size=1048576"
detox verb Emulator stdout:  emulator: argv[27] = "-device"
detox verb Emulator stdout:  emulator: argv[28] = "virtio-blk-pci,drive=cache,iothread=disk-iothread,modern-pio-notify"
detox verb Emulator stdout:  emulator: argv[29] = "-drive"
detox verb Emulator stdout:  emulator: argv[30] = "if=none,overlap-check=none,cache=unsafe,index=2,id=userdata,file=C:\Users\ram\.android\avd\Nexus_5X_API_25.avd/userdata-qemu.img.qcow2,l2-cache-size=1048576"
detox verb Emulator stdout:  emulator: argv[31] = "-device"
detox verb Emulator stdout:  emulator: argv[32] = "virtio-blk-pci,drive=userdata,iothread=disk-iothread,modern-pio-notify"
detox verb Emulator stdout:  emulator: argv[33] = "-drive"
detox verb Emulator stdout:  emulator: argv[34] = "if=none,overlap-check=none,cache=unsafe,index=3,id=encrypt,file=C:\Users\ram\.android\avd\Nexus_5X_API_25.avd/encryptionkey.img.qcow2,l2-cache-size=1048576"
detox verb Emulator stdout:  emulator: argv[35] = "-device"
detox verb Emulator stdout:  emulator: argv[36] = "virtio-blk-pci,drive=encrypt,iothread=disk-iothread,modern-pio-notify"
detox verb Emulator stdout:  emulator: argv[37] = "-drive"
detox verb Emulator stdout:  emulator: argv[38] = "if=none,overlap-check=none,cache=unsafe,index=4,id=sdcard,file=C:\Users\ram\.android\avd\Nexus_5X_API_25.avd/sdcard.img.qcow2,l2-cache-size=1048576"
detox verb Emulator stdout:  emulator: argv[39] = "-device"
detox verb Emulator stdout:  emulator: argv[40] = "virtio-blk-pci,drive=sdcard,iothread=disk-iothread,modern-pio-notify"
detox verb Emulator stdout:  emulator: argv[41] = "-netdev"
detox verb Emulator stdout:  emulator: argv[42] = "user,id=mynet"
detox verb Emulator stdout:  emulator: argv[43] = "-device"
detox verb Emulator stdout:  emulator: argv[44] = "virtio-net-pci,netdev=mynet"
detox verb Emulator stdout:  emulator: argv[45] = "-netdev"
detox verb Emulator stdout:  emulator: argv[46] = "user,id=mynet2,net=<IP_ADDRESS>/24"
detox verb Emulator stdout:  emulator: argv[47] = "-device"
detox verb Emulator stdout:  emulator: argv[48] = "virtio-net-pci,netdev=mynet2"
detox verb Emulator stdout:  emulator: argv[49] = "-show-cursor"
detox verb Emulator stdout:  emulator: argv[50] = "-L"
detox verb Emulator stdout:  emulator: argv[51] = "C:\Users\ram\AppData\Local\Android\Sdk\emulator/lib/pc-bios"
detox verb Emulator stdout:  emulator: argv[52] = "-soundhw"
detox verb Emulator stdout:  emulator: argv[53] = "hda"
detox verb Emulator stdout:  emulator: argv[54] = "-vga"
detox verb Emulator stdout:  emulator: argv[55] = "none"
detox verb Emulator stdout:  emulator: argv[56] = "-append"
detox verb Emulator stdout:  emulator: argv[57] = "qemu=1 androidboot.hardware=ranchu clocksource=pit android.qemud=1 console=0 console=0 android.checkjni=1 qemu.gles=1 qemu.encrypt=1 cma=256M"
detox verb Emulator stdout:  emulator: argv[58] = "-android-hw"
detox verb Emulator stdout:  emulator: argv[59] = "C:\Users\ram\.android\avd\Nexus_5X_API_25.avd/hardware-qemu.ini"
detox verb Emulator stdout:  Concatenated QEMU options:
detox verb Emulator stdout:   C:\Users\ram\AppData\Local\Android\Sdk\emulator/qemu/windows-x86_64/qemu-system-i386.exe -no-audio -dns-server <IP_ADDRESS> -serial null -cpu android32 -enable-hax -smp cores=2
detox verb Emulator stdout:  -m 1536 -lcd-density 420 -kernel C:\Users\ram\AppData\Local\Android\Sdk/system-images\android-25\google_apis_playstore\x86\/kernel-ranchu -initrd C:\Users\ram\AppData\Local\Android\Sdk/system-images\android-25\google_apis_playstore\x86\/ramdisk.img -object iothread,id=disk-iothread -drive if=none,overlap-check=none,cache=unsafe,index=0,id=system,file=C:\Users\ram\.android\avd\Nexus_5X_API_25.avd\system.img.qcow2,read-only -device virtio-blk-pci,drive=system,iothread=disk-iothread,modern-pio-notify -drive if=none,overlap-check=none,cache=unsafe,index=1,id=cache,file=C:\Users\ram\.android\avd\Nexus_5X_API_25.avd/cache.img.qcow2,l2-cache-size=1048576 -device virtio-blk-pci,drive=cache,iothread=disk-iothread,modern-pio-notify -drive if=none,overlap-check=none,cache=unsafe,index=2,id=userdata,file=C:\Users\ram\.android\avd\Nexus_5X_API_25.avd/userdata-qemu.img.qcow2,l2-cache-size=1048576 -device virtio-blk-pci,drive=userdata,iothread=disk-iothread,modern-pio-notify -drive if=none,overlap-check=none,cache=unsafe,index=3,id=encrypt,file=C:\Users\ram\.android\avd\Nexus_5X_API_25.avd/encryptionkey.img.qcow2,l2-cache-size=1048576 -device virtio-blk-pci,drive=encrypt,iothread=disk-iothread,modern-pio-notify -drive if=none,overlap-check=none,cache=unsafe,index=4,id=sdcard,file=C:\Users\ram\.android\avd\Nexus_5X_API_25.avd/sdcard.img.qcow2,l2-cache-size=1048576 -device virtio-blk-pci,drive=sdcard,iothread=disk-iothread,modern-pio-notify -netdev user,id=mynet -device virtio-net-pci,netdev=mynet -netdev user,id=mynet2,net=<IP_ADDRESS>/24 -device virtio-net-pci,netdev=mynet2 -show-cursor -L C:\Users\ram\AppData\Local\Android\Sdk\emulator/lib/pc-bios -soundhw hda -vga none -append 'qemu=1 androidboot.hardware=ranchu clocksource=pit android.qemud=1 console=0 console=0 android.checkjni=1 qemu.gles=1 qemu.encrypt=1 cma=256M' -android-hw C:\Users\ram\.android\avd\Nexus_5X_API_25.avd/hardware-qemu.ini
detox verb Emulator stdout:  emulator: Starting QEMU main loop
detox verb Emulator stdout:  Hax is enabled
detox verb Emulator stdout:  Hax ram_size 0x60000000
detox verb Emulator stdout:  emulator: registered 'boot-properties' qemud service
detox verb Emulator stdout:  emulator: Adding boot property: 'qemu.sf.fake_camera' = 'both'
detox verb Emulator stdout:  emulator: Adding boot property: 'qemu.adb.secure' = '1'
detox verb Emulator stdout:  emulator: Initializing hardware OpenGLES emulation support
detox verb Emulator stdout:  emulator: Adding boot property: 'ro.opengles.version' = '131072'
detox verb Emulator stdout:  emulator: Adding boot property: 'dalvik.vm.heapsize' = '384m'
detox verb Emulator stdout:  emulator: Adding boot property: 'qemu.hw.mainkeys' = '0'
detox verb Emulator stdout:  emulator: Adding boot property: 'qemu.sf.lcd_density' = '420'
detox verb Emulator stdout:  HAX is working and emulator runs in fast virt mode.
detox verb Emulator stdout:
detox verb Emulator stdout:  emulator
detox verb Emulator stdout:  : goldfish_events.have-dpad: false
detox verb Emulator stdout:  emulator: goldfish_events.have-trackball: false
detox verb Emulator stdout:  emulator: goldfish_events.have-camera: true
detox verb Emulator stdout:  emulator: goldfish_events.have-keyboard: true
detox verb Emulator stdout:  emulator: goldfish_events.have-lidswitch: false
detox verb Emulator stdout:  emulator: goldfish_events.have-touch: false
detox verb Emulator stdout:  emulator: goldfish_events.have-multitouch: true
detox verb Emulator stdout:
detox verb Emulator stdout:  emulator
detox verb Emulator stdout:  : control console listening on port 5554, ADB on port 5555
detox verb Emulator stdout:
detox verb Emulator stdout:  Not u
detox verb Emulator stdout:  sing any http proxy
detox verb Emulator stdout:  emulator: android_hw_fingerprint_init: fingerprint qemud listen service initialized
detox verb Emulator stdout:
detox verb Emulator stdout:
detox verb Emulator stdout:  emulator: _h
detox verb Emulator stdout:  wFingerprint_connect: connect finger print listen is called
detox verb Emulator stdout:
detox verb Emulator stdout:  emulator: got message from guest system fingerprint HAL
detox verb Emulator stdout:
detox verb Emulator stdout:
detox verb Emulator stdout:  emulator:
detox verb Emulator stdout:  onGuestSendCommand: [00000000214f8140] Adb connected, start proxing data
detox verb Emulator stdout:
detox verb 2: C:\Users\ram\AppData\Local\Android\Sdk\platform-tools\adb  devices
detox verb 2: stdout: List of devices attached
detox verb 2: stdout: emulator-5554     device
detox verb 2: stdout:
detox verb 2: stdout:
detox verb 3: C:\Users\ram\AppData\Local\Android\Sdk\platform-tools\adb -s emulator-5554 shell input keyevent 82
detox verb 4: C:\Users\ram\AppData\Local\Android\Sdk\platform-tools\adb -s emulator-5554 uninstall com.awesomeproject
detox verb 4: stdout: Success
detox verb 4: stdout:
detox verb 5: C:\Users\ram\AppData\Local\Android\Sdk\platform-tools\adb -s emulator-5554 uninstall com.awesomeproject.test
detox verb 5: stderr:
detox verb 5: stderr: Exception occurred while dumping:
detox verb 5: stderr: java.lang.IllegalArgumentException: Unknown package: com.awesomeproject.test
detox verb 5: stderr:   at com.android.server.pm.Settings.isOrphaned(Settings.java:4134)
detox verb 5: stderr:   at com.android.server.pm.PackageManagerService.isOrphaned(PackageManagerService.java:18105)
detox verb 5: stderr:   at com.android.server.pm.PackageManagerService.deletePackage(PackageManagerService.java:15522)
detox verb 5: stderr:   at com.android.server.pm.PackageInstallerService.uninstall(PackageInstallerService.java:888)
detox verb 5: stderr:   at com.android.server.pm.PackageManagerShellCommand.runUninstall(PackageManagerShellCommand.java:792)
detox verb 5: stderr:   at com.android.server.pm.PackageManagerShellCommand.onCommand(PackageManagerShellCommand.java:118)
detox verb 5: stderr:   at android.os.ShellCommand.exec(ShellCommand.java:94)
detox verb 5: stderr:   at com.android.server.pm.PackageManagerService.onShellCommand(PackageManagerService.java:18363)
detox verb 5: stderr:   at android.os.Binder.shellCommand(Binder.java:468)
detox verb 5: stderr:   at android.os.Binder.onTransact(Binder.java:367)
detox verb 5: stderr:   at android.content.pm.IPackageManager$Stub.onTransact(IPackageManager.java:2387)
detox verb 5: stderr:   at com.android.server.pm.PackageManagerService.onTransact(PackageManagerService.java:3031)
detox verb 5: stderr:   at android.os.Binder.execTransact(Binder.java:565)
detox verb 5: stderr:
detox verb 6: C:\Users\ram\AppData\Local\Android\Sdk\platform-tools\adb -s emulator-5554 install -r -g C:\Users\ram\Projects\AwesomeProject\android\app\build\outputs\apk\app-debug.apk
detox verb 6: stderr: Success
detox verb 6: stderr:
detox verb 7: C:\Users\ram\AppData\Local\Android\Sdk\platform-tools\adb -s emulator-5554 install -r -g C:\Users\ram\Projects\AwesomeProject\android\app\build\outputs\apk\app-debug.apk
detox verb 7: stderr: Success
detox verb 7: stderr:
detox verb 8: C:\Users\ram\AppData\Local\Android\Sdk\platform-tools\adb -s emulator-5554 shell am force-stop com.awesomeproject
detox verb adb -s emulator-5554 shell am instrument -w -r -e detoxServer ws://localhost:53997 -e detoxSessionId 67eda7ec-4fb5-8c56-4aed-33456e047e22 -e debug false com.awesomeproject.test/android.support.test.runner.AndroidJUnitRunner
detox verb Instrumentation spawned, childProcess.pid:  728
detox verb ws send: {"type":"isReady","params":{},"messageId":-1000}
detox verb Instrumentation stderr:  android.util.AndroidException: INSTRUMENTATION_FAILED: com.awesomeproject.test/android.support.test.runner.AndroidJUnitRunner
detox verb Instrumentation stderr:
detox verb Instrumentation stderr:      at com.android.commands.am.Am.runInstrument(Am.java:890)
detox verb Instrumentation stderr:      at com.android.commands.am.Am.onRun(Am.java:400)
detox verb Instrumentation stderr:      at com.android.internal.os.BaseCommand.run(BaseCommand.java:51)
detox verb Instrumentation stderr:      at com.android.commands.am.Am.main(Am.java:121)
detox verb Instrumentation stderr:      at com.android.internal.os.RuntimeInit.nativeFinishInit(Native Method)
detox verb Instrumentation stderr:      at com.android.internal.os.RuntimeInit.main(RuntimeInit.java:262)
detox verb Instrumentation stderr:
detox verb Instrumentation stdout:  INSTRUMENTATION_STATUS: id=ActivityManagerService
detox verb Instrumentation stdout:
detox verb Instrumentation stdout:  INSTRUMENTATION_STATUS: Error=Unable to find instrumentation info for: ComponentInfo{com.awesomeproject.test/android.support.test.runner.AndroidJUnitRunner}
detox verb Instrumentation stdout:  INSTRUMENTATION_STATUS_CODE: -1
detox verb Instrumentation stdout:
detox verb instrumentationProcess terminated due to receipt of signal null
  1) "before all" hook

  0 passing (2m)
  1 failing

  1) "before all" hook:
     Error: Timeout of 120000ms exceeded. For async tests and hooks, ensure "done()" is called; if returning a Promise, ensure it resolves.

detox verb ws send: {"type":"cleanup","params":{"stopRunner":true},"messageId":1}

Any Help on what I am missing?

same problem

Hello,
We are moving support questions to Stack Overflow. Please ask a question there with the detox tag. This section is only meant for Detox issues and enhancement requests.
Thanks

@LeoNatan is detox support Linux?

Linux should be supported.


Burrow crashes if __consumer_offsets not yet exists

Hi,
I'm going to construct a Kafka cluster and monitor it with Burrow.
Just after Kafka installation, Burrow crashes with outputs below:
Started Burrow at July 31, 2015 at 11:16pm (JST)
1438352170387870777 [Info] Starting Zookeeper client
1438352170387958149 [Info] Starting Offsets Storage module
1438352170388042830 [Info] Starting HTTP server
1438352170388103038 [Info] Starting Zookeeper client for cluster local
1438352170388130970 [Info] Starting Kafka client for cluster local
1438352170416477260 [Critical] Cannot start Kafka client for cluster local: kafka server: Unexpected (unknown?) server error.
Burrow failed at July 31, 2015 at 11:16pm (JST)

After create some topics and consume them to create __consumer_offsets, Burrow worked well.

This is expected behavior, as Burrow can't do most of its work without that topic. However, the larger problem is that there is no clean handling of the situation when the topic does not exist, which also means there is no proper handling of the case where there is a serious problem consuming.
This will need a lot of work to add some error checking and retry behavior around the consumer.

That makes sense. Thank you.
As for me, It was hard to find the cause of the error and took some time...
More detailed error message like "Failed to get a partition count for the consumption topic" may be very helpful!
Thanks.


Purpose of temporary directory for lowerdirs

I wonder why do we need a temporary directory for lowerdir here https://github.com/fuweid/go-mountidmapped/blob/3fd58984b086d362853b988dd7828abf80a1bbed/cmd/ovl-mountidmapped/main.go#L141
Looks like it is possible to just id-map lowerdir, mount overlay directory, unmount lowerdir. In this case lowerdir will have initial mapping, but merged one will have id-mapped mapping.
Later we can id-map the same lowerdir, use it to mount another overlay and unmount, it will have initial mapping, but this another merged directory will have new id-mapped mapping.
May be I missed something?

I wonder why do we need a temporary directory for lowerdir here

It has data-race issue. We don't know who is using the lowerdir right now. For example , images share the same lowerdirs and the containers can mount it concurrently. If we mount it in the same place, it will cause data-race.

It has data-race issue.

Thank you for clarification, data-race was the only scenario I thought about, but wasn't sure, thanks! Going to close this issue.


chore(deps): update ci dependencies

This PR contains the following updates:

Package
Type
Update
Change

common-dev-assets

digest
81754c2 -> 4076144

github.com/terraform-ibm-modules/ibmcloud-terratest-wrapper
require
minor
v1.41.5 -> v1.42.0

Release Notes

terraform-ibm-modules/ibmcloud-terratest-wrapper (github.com/terraform-ibm-modules/ibmcloud-terratest-wrapper)
v1.42.0
Compare Source
Features

add schematics consistency test features (#892) (d33d6d0)

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

/run pipeline

/run pipeline

ℹ Artifact update notice
File name: tests/go.mod
In order to perform the update(s) described in the table above, Renovate ran the go get command, which resulted in the following additional change(s):

4 additional dependencies were updated
The go directive was updated for compatibility reasons

Details:

Package
Change

go
1.22.0 -> 1.22.4

github.com/IBM/cloud-databases-go-sdk
v0.7.0 -> v0.7.1

github.com/IBM/platform-services-go-sdk
v0.71.0 -> v0.71.1

github.com/IBM/schematics-go-sdk
v0.3.0 -> v0.4.0

golang.org/x/net
v0.25.0 -> v0.30.0

/run pipeline


Project status?

Can't find examples, contributor guidelines or anything similar but the source code.

Contribution guidelines are here: https://github.com/blacksky-algorithms/rsky?tab=readme-ov-file#contribution
If you have any questions or wanna chat about stuff feel free to ping me in the #rust channel of the Bluesky Dev DIscord: https://discord.gg/UGwzQwDPf7
I'm admittedly newer to working in open source so if you think there are things that could be added to the repo to make things clearer, just let me know and I'll try to implement. I know documentation can be better.
Currently the most active development is around rsky-pds and getting it to a state where it can be used in the production network without issues. To get there I've been starting with implementing the same tests used in the canonical typescript implementation.
Generally speaking, besides rsky-feedgen and rsky-firehose, everything should follow closely to the canonical typescript implementation including tests. Differences will be the one noted in the root README where rsky-pds uses postgres, s3 for blobs, and mailgun for mailing.
Thanks for your interest!

Contribution guidelines are here: https://github.com/blacksky-algorithms/rsky?tab=readme-ov-file#contribution
If you have any questions or wanna chat about stuff feel free to ping me in the #rust channel of the Bluesky Dev DIscord: https://discord.gg/UGwzQwDPf7
I'm admittedly newer to working in open source so if you think there are things that could be added to the repo to make things clearer, just let me know and I'll try to implement. I know documentation can be better.
Currently the most active development is around rsky-pds and getting it to a state where it can be used in the production network without issues. To get there I've been starting with implementing the same tests used in the canonical typescript implementation.
Generally speaking, besides rsky-feedgen and rsky-firehose, everything should follow closely to the canonical typescript implementation including tests. Differences will be the one noted in the root README where rsky-pds uses postgres, s3 for blobs, and mailgun for mailing.
Thanks for your interest!

Thank you for providing directions!


mkEntityDefList

This PR adds a function mkEntityDefList to work around the issue covered here.
This function could easily be upstreamed into persistent, and that may be a better place for it.

Closing b/c i merged it upstream


Managed identities and applicability of this MFA rule

We currently have a couple of "service principals" defined with Azure AD roles (eg: Office 365 Yammer). We can't exclude these from the Conditional Access policy and when verifying the sign-in logs, we see that this Conditional Access policy is applied. How can we exclude these "service principals" in the conditional access policy?

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

ID: ca2fb784-f7e9-6fad-9889-2dc6639bc0e1
Version Independent ID: 8b90e35e-6918-1073-85f6-ad47786033c6
Content: Conditional Access - Require MFA for administrators - Azure Active Directory
Content Source: articles/active-directory/conditional-access/howto-conditional-access-policy-admin-mfa.md
Service: active-directory
Sub-service: conditional-access
GitHub Login: @MicrosoftGuyJFlo
Microsoft Alias: joflore

@Silencer0001 Thank you for reaching out to us! We will review and provide an update as appropriate.

@Silencer0001, I would like to know what kind of error you get when you try to exclude a service principal from a CA policy. Excluding the Service Principal is the only way to get the CA policy not get applied on it. Also I am not clear on that statement where you say Service Principals defined with AAD roles. Do share some more insights on this so that we can help you better.


Added image field to RSS feed

Reason for PR
Related to #3597, a member of the EngEd Community, (@katungi), requested if we could add images to the new JSON feed so they could display featured article images. To do this, requires an extra image field in the Section RSS Feed which this PR adds.
Code Changes
layouts/articles/rss.xml
{{ range .Params.images }}
	<image>https://www.section.io{{ .url }}</image>
{{ end }}

Result

Can we have the team review this as well. Just to make sure everything looks proper.
👍

Great job! @louisefindlay23


New tech available message years later

Years after discovering a tech, you sometimes get a message about it being available.

I suspect this is related to something about MT tech rewards not giving messages for newly gained techs.


Write vignette files

[ ] Vignette about spliting any genome file into individual cromossome files (is there a way around that? rewriting the package in C or Rust maybe?)


Add ability to run app using webpack

Add ability to run app using webpack.
Date: 2/24/17
Purpose: This installs and configures a bundler so that we can run the app in a more complex way than just with a simple server. I think this will allow us to modify the CSS more simply, as well as keep us out of trouble as it starts to grow.
State of PR: This is a complete feature.
Request: Please QA this feature and check to make sure the code is clean and correct.
To Test

Run npm install. I think this will install all of the necessary packages for you.
run npm start and check on localhost:8080 if it is working.

This is cool.


Add diagrams for "Putting markup into JavaScript"

Overview
Adds diagrams for the "Putting markup into JavaScript" section of "Writing Markup with JSX".
Screens
Light

Dark

Nice catch, fixed!


[move-analyzer] Automatically upload the move binary program after the Release is generated #208_104

Motivation
[move-analyzer] Automatically upload the move binary program after the Release is generated
Have you read the Contributing Guidelines on pull requests?
Yes
Test Plan
CI/CD tests are covered.

/canary

:sunny: Canary successful

/land


diacritics not supported

Environment
Platform ServicePack Version      VersionString

Win32NT             10.0.18363.0 Microsoft Windows NT 10.0.18363.0
Windows Terminal
Version: 1.3.2651.0
Steps to reproduce
run console with some language using diacritics - e.g. i'm writing in polish where we have a lot of ąśćęłóżź
try typing them... even the trick with using the tilde is not working - diacritics are 'blocked' /:

Expected behavior
be able to type diacritics

Actual behavior
...which you currently cannot

Which shell are you using? CMD/PowerShell/WSL Bash ?

PowerShell... indeed i just run CMD and diacritics works fine there /:

It works fine in CMD
But does not work in PowerShell. Is that correct?
If that's the case, it is a PowerShell issue. Are you using PowerShell Core or the Windows PowerShell that comes with Windows?

Windows PS.
hmm... you're correct, i checked on the console and don't have diacritics there either... i do most of the job from within VSC, didn't notice this glitch before.
lol. found that https://github.com/PowerShell/PowerShell/issues/10298
i installed recent psreadline version and all's working fine.
sorry for bothering, didn't notice it's a global issue

Well you can then close this issue

Glad you were able to figure this out! Hopefully this will help someone in the future ☺


Make pigar respect gitignore

I have subfolder which I like to ignore as specified in my gitignore.
But there is no way to avoid those for pigar.
Let me know if this is already passible,

pigar does not respect gitignore, however, there is already an option to ignore directories:
-i DIR [DIR ...]      given a list of directory to ignore, relative directory

Feel free to reopen this issue if it does not work.


can we send custom metrics into dynatrace

is there a way to send custom metrics into dynatrace using the existing  code by modifying values.yaml file or any other files ??

Hey. When it comes to this integration, you can ingest GCP custom metrics as long as you declare them and assign it to a single GCP resource type. Then, the autodiscovery feature can be enabled (specifying that resource type in the autodiscovery-values.yaml).
Ref: https://docs.dynatrace.com/docs/shortlink/gcp-autodiscovery#select-resources
On a general level, outside of this particular extension, any metric can be manually ingested into Dynatrace following our protocol: https://docs.dynatrace.com/docs/extend-dynatrace/extend-metrics/reference/metric-ingestion-protocol


lbr_fri_ros2_stack for Galactic

Hi Martin.
Based on "foxy" branch, I modified "lbr_hardware" for Ros-Galactic.
[1] This is the official guideline to migrate from foxy to galactic.
https://github.com/ros-controls/ros2_control/blob/master/hardware_interface/doc/hardware_components_userdoc.rst
[2] Simulation tests with Gazebo and Moveit have been successfully completed.  but i could not test it with real robot.
[3] This PR is to merge from "galactic" branch in my repo to "master" branch in KCL-BMEIS.
So, if you make "galactic" branch on yourside, I will re-open PR to merge it.
Thank you.

hi @ggory15 , thanks so much, just saw it. I'll revisit it soon.


docs/Maintainer-Guidelines: Document brew mirror

[x] Have you followed the guidelines in our Contributing document?
[x] Have you checked to ensure there aren't other open Pull Requests for the same change?
[x] Have you added an explanation of what your changes do and why you'd like us to include them?
[x] ~Have you written new tests for your changes? Here's an example.~
[x] ~Have you successfully run brew style with your changes locally?~
[x] ~Have you successfully run brew tests with your changes locally?~

I vaguely remembered that ImageMagick was a download we mirrored on BinTray and that doing so required some manual effort post-merge. I went looking for some docs to confirm that memory, but didn't find any.

Thanks @issyl0!

Oh, I was planning on waiting until Dawid's PR was merged (since it exists! super fast!) so we don't have to edit these docs twice.


Add CPS button

@GoFroggyRun The two most recent commits in PR #738 (nested_form_parameters are grayed out and Look for puf_not_cps flag in views.py) add the back-end capabilities to handle a "use cps" flag.
I'm not exactly sure what we need to do to add this to the front-end.  I think it would work something like the "change start year" action where the page is refreshed with a different start year.  So, you would click a "use cps" button, the page would refresh but would include only parameters that are compatible with the CPS.  I'm open to other approaches though.

Ideally we'll 'gray out' rather than eliminate params that don't work with a given dataset.

In that case, I think it would make sense to add a flag attribute, gray_out, to the TaxCalcParam object.  That would be "on" when parameters that are compatible with the CPS but not the PUF when the PUF data set is selected and vice versa.  I'll update PR #738.
This attribute can be accessed in the html and javascript files I think.

@hdoupe thanks for the updates in #738.
As @MattHJensen pointed out, the way that I have in mind is to display all parameters while grey out certain ones that are not compatible with the dataset selected. A flag attribute sounds sufficient.

@GoFroggyRun I made the changes in PR #738 that add the graying out attribute.

@hdoupe,  Note that using the cps.csv data file on TaxBrain will not work correctly until the data bug in the cps_weights.csv file is fixed in the taxdata repo and used in the Tax-Calculator repo.
See taxdata issue 125 for details.

Closed via #835, #842


move default value to config block

A bit weird to have this be the only option that have the default (re)specified in the description
Please don't delete this checklist! Before submitting the PR, please make sure you do the following:

[ ] It's really useful if your PR references an issue where it is discussed ahead of time. In many cases, features are absent for a reason. For large changes, please create an RFC: https://github.com/sveltejs/rfcs
[x] This message body should clearly illustrate what problems it solves.
[ ] Ideally, include a test that fails without this PR but passes with it.

Tests

[x] Run the tests with pnpm test and lint the project with pnpm lint and pnpm check

Changesets

[ ] If your PR makes a change that should be noted in one or more packages' changelogs, generate a changeset by running pnpm changeset and following the prompts. All changesets should be patch until SvelteKit 1.0

we really need to do a better job of the config documentation — i have some loose ideas — but yeah, this is the right move for now


Investigate- Support for iOS 11

Summary (Required)
Support for iOS 11
Description (Required)
iOS 11 has already released. Please test and investigate whether there is no problem.
If there is any problem, can you tell me?
If there is no problem, I will close this issue.

@at-aoiyamamura
There is no problem with iOS 11

@at-duyentran E check library trên iOS11 chưa? Và có vấn đề gì k?
E report vào đây giúp c nhé.

@at-aoiyamamura @at-diemnguyen I checked library on IOS 11 and don't found problem

@at-duyentran @at-thinhung
So far, I will close this issue
@at-duyentran
If you find any bugs on iOS 11, please make new issue.


I don't know whats wrong with this challenge.

Challenge Nest an Anchor Element within a Paragraph has an issue.
User Agent is: Mozilla/5.0 (Windows NT 6.1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/56.0.2924.87 Safari/537.36.
Please describe how to reproduce this issue, and include links to screenshots if possible.
  I am able to get your code to pass, could you post a description of what errors you are getting and possibly a screenshot?
Cheers!

@prashantmasule you have two opinions.
first, try the refresh on that challenge.
or second, you could copy your code then reset it then paste it.
I hope that will solve a problem.
I close this because this doesn't have a bug. we could reopen this issue if you still have a problem.


Emoji not rendering

When using a emoji inside a Text/RichText/TextSpan using a physical Android 10 device (Google Pixel 3 XL), compiled using Flutter's latest master release on Windows, the emoji doesn't render properly.
Also, when using it inside an app, when the Text with emoji is inside an StatefulWidget and it is updated, the emoji is rendered correctly (couldn't reproduce behavior with minimum sample app).
Steps to Reproduce

Run sample app
Emoji is not rendered correctly

The first emoji is from Window's Emoji picker, the second one from Emojipedia
Target Platform: Android
Target OS version/browser: 10
Devices: Pixel 3 XL
Sample app
import 'package:flutter/material.dart';

void main() {
  runApp(TestWidget());
}

class TestWidget extends StatelessWidget {
  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      home: Scaffold(
        body: Center(
          child: Row(
            mainAxisAlignment: MainAxisAlignment.spaceEvenly,
            children: <Widget>[
              Text('✈'),
              Text('✈'),
            ],
          ),
        ),
      ),
    );
  }
}

Flutter doctor
[√] Flutter (Channel master, v1.10.11-pre.3, on Microsoft Windows [VersiÃ³n 10.0.18362.387], locale es-ES)
    • Flutter version 1.10.11-pre.3 at C:\src\flutter
    • Framework revision dc03c44321 (42 minutes ago), 2019-10-04 04:01:43 -0400
    • Engine revision 759d3dba25
    • Dart version 2.6.0 (build 2.6.0-dev.5.0 7a7dcd1ed9)

[√] Android toolchain - develop for Android devices (Android SDK version 29.0.2)
    • Android SDK at C:\Users\Cristian\AppData\Local\Android\sdk
    • Android NDK location not configured (optional; useful for native profiling support)
    • Platform android-29, build-tools 29.0.2
    • Java binary at: C:\Program Files\Android\Android Studio\jre\bin\java
    • Java version OpenJDK Runtime Environment (build 1.8.0_202-release-1483-b03)
    • All Android licenses accepted.

[√] Android Studio (version 3.5)
    • Android Studio at C:\Program Files\Android\Android Studio
    • Flutter plugin version 40.0.2
    • Dart plugin version 191.8423
    • Java version OpenJDK Runtime Environment (build 1.8.0_202-release-1483-b03)

[√] Connected device (1 available)
    • Pixel 3 XL • 89PY09NNV • android-arm64 • Android 10 (API 29)

• No issues found!

Since it has been a while and we have landed font loading fixes in the meantime, can you confirm you are still seeing this? @Zazo032 Thanks!

Seems to be fixed, I'll close this. I faced a different issue with emoji rendering, but I'll open a separate issue to track it.

FYI, this may be related: https://github.com/flutter/flutter/issues/45947

It was a different one, on iOS, a Text with a plane taking off emoji was changed with a fire emoji, it's weird but I could only reproduce it once.


Support iojs directly in node-gyp

Such as downloading iojs libs and cconfigure correct iojs.lib path.

Dup of #564.


Use socks-proxy-agent for socket requests

Will allow us to secure the socket requests as well.
Move the initialization of the proxyagent to a shared lib to avoid duplicate code.
## With VIP_PROXY set and proxy active

# GraphQL request:
❯ node ./dist/bin/vip app 123
===================================
+ id: 123
+ name: example
+ repo: wpcomvip/example
===================================

node ./dist/bin/vip wp @123 option get home
https://example.com

# With proxy not active
node ./dist/bin/vip wp @123 option get home
App 123 does not exist

Steps to Test
Use the following commands to verify things:
./dist/bin/vip @309 wp option get home
./dist/bin/vip app 309

Start with VIP_PROXY not defined: commands should work (if you have superadmin)
Set VIP_PROXY but do not start proxy: commands should error out
Set VIP_PROXY and also start proxy: commands should work.

I can successfully execute the commands with or without VIP_PROXY defined. 🤔

I can successfully execute the commands with or without VIP_PROXY defined.

I think that was expected. However, now that we have the proxy enforcement in place, it should fail when not defined.


Update OKD-based CRC build

Same issue as #636.
Looks like these are outdated again at: https://dl.fedoraproject.org/pub/alt/okd-crc/release/
[protosam@nullhost]$ curl -Lo ~/bin/crc https://dl.fedoraproject.org/pub/alt/okd-crc/release/macos-amd64/crc
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100 2690M  100 2690M    0     0  12.1M      0  0:03:40  0:03:40 --:--:-- 13.0M

[protosam@nullhost]$ chmod +x ~/bin/crc

[protosam@nullhost]$ crc config set consent-telemetry no
Successfully configured consent-telemetry to no

[protosam@nullhost]$ crc setup
INFO Checking if running as non-root
INFO Checking if crc-admin-helper executable is cached
INFO Caching crc-admin-helper executable
INFO Using root access: Changing ownership of /Users/pilot/.crc/bin/crc-admin-helper-darwin
Password:
INFO Using root access: Setting suid for /Users/pilot/.crc/bin/crc-admin-helper-darwin
INFO Checking for obsolete admin-helper executable
INFO Checking if running on a supported CPU architecture
INFO Checking minimum RAM requirements
INFO Checking if running emulated on a M1 CPU
INFO Checking if HyperKit is installed
INFO Setting up virtualization with HyperKit
INFO Using root access: Changing ownership of /Users/pilot/.crc/bin/hyperkit
INFO Using root access: Setting suid for /Users/pilot/.crc/bin/hyperkit
INFO Checking if crc-driver-hyperkit is installed
INFO Installing crc-machine-hyperkit
INFO Using root access: Changing ownership of /Users/pilot/.crc/bin/crc-driver-hyperkit
INFO Using root access: Setting suid for /Users/pilot/.crc/bin/crc-driver-hyperkit
INFO Checking if CodeReady Containers daemon is running
INFO Checking file permissions for /etc/resolver/testing
INFO Setting file permissions for /etc/resolver/testing
INFO Using root access: Creating file /etc/resolver/testing
INFO Using root access: Changing ownership of /etc/resolver/testing
INFO Checking if CRC bundle is extracted in '$HOME/.crc'
INFO Checking if /Users/pilot/.crc/cache/crc_hyperkit_4.7.0-0.okd-2021-06-13-090745.crcbundle exists
INFO Extracting bundle from the CRC executable
INFO Ensuring directory /Users/pilot/.crc/cache exists
INFO Extracting embedded bundle crc_hyperkit_4.7.0-0.okd-2021-06-13-090745.crcbundle to /Users/pilot/.crc/cache
INFO Uncompressing crc_hyperkit_4.7.0-0.okd-2021-06-13-090745.crcbundle
crc.qcow2: 9.84 GiB / 9.84 GiB [------------------------------------------------------------------------------] 100.00%
Your system is correctly setup for using CodeReady Containers, you can now run 'crc start' to start the OpenShift cluster

[protosam@nullhost]$ crc start
WARN A new version (1.29.1) has been published on https://developers.redhat.com/content-gateway/file/pub/openshift-v4/clients/crc/1.29.1/crc-macos-amd64.pkg
INFO Checking if running as non-root
INFO Checking if crc-admin-helper executable is cached
INFO Checking for obsolete admin-helper executable
INFO Checking if running on a supported CPU architecture
INFO Checking minimum RAM requirements
INFO Checking if running emulated on a M1 CPU
INFO Checking if HyperKit is installed
INFO Checking if crc-driver-hyperkit is installed
INFO Checking file permissions for /etc/resolver/testing
INFO Loading bundle: crc_hyperkit_4.7.0-0.okd-2021-06-13-090745...
INFO Creating CodeReady Containers VM for OpenShift 4.7.0-0.okd-2021-06-13-090745...
INFO Generating new SSH Key pair...
INFO Generating new password for the kubeadmin user
INFO Copying kubeconfig file to instance dir...
INFO Starting CodeReady Containers VM for OpenShift 4.7.0-0.okd-2021-06-13-090745...
INFO CodeReady Containers instance is running with IP <IP_ADDRESS>
INFO CodeReady Containers VM is running
INFO Updating authorized keys...
INFO Restarting the host network
INFO Check internal and public DNS query...
INFO Check DNS query from host...
INFO Adding user's pull secret to instance disk...
INFO Verifying validity of the kubelet certificates...
INFO Starting OpenShift kubelet service
INFO Kubelet client certificate has expired, renewing it... [will take up to 8 minutes]
INFO Kubelet serving certificate has expired, waiting for automatic renewal... [will take up to 8 minutes]
Failed to renew TLS certificates: please check if a newer CodeReady Containers release is available: Temporary error: certificate /var/lib/kubelet/pki/kubelet-server-current.pem still expired (x58)

[protosam@nullhost]$ ssh -i ~/.crc/machines/crc/id_ecdsa $(jq -r '.Driver.IPAddress' ~/.crc/machines/crc/config.json) -l core
Warning: Permanently added '<IP_ADDRESS>' (ECDSA) to the list of known hosts.
Fedora CoreOS 34
Tracker: https://github.com/coreos/fedora-coreos-tracker
Discuss: https://discussion.fedoraproject.org/c/server/coreos/

Last login: Mon Jul 26 02:15:45 2021 from <IP_ADDRESS>
[core@crc-tlqlw-master-0 ~]$ sudo openssl x509 -in /var/lib/kubelet/pki/kubelet-server-current.pem -noout -enddate | cut -d= -f 2
Jul 18 13:36:23 2021 GMT

From ~/.crc/crc.log:
time="2021-07-25T20:57:39-05:00" level=debug msg="retry loop: attempt 56"
time="2021-07-25T20:57:39-05:00" level=debug msg="Running SSH command: date --date=\"$(sudo openssl x509 -in /var/lib/kubelet/pki/kubelet-server-current.pem -noout -enddate | cut -d= -f 2)\" --iso-8601=seconds"
time="2021-07-25T20:57:39-05:00" level=debug msg="SSH command results: err: <nil>, output: 2021-07-18T13:36:23+00:00\n"
time="2021-07-25T20:57:39-05:00" level=debug msg="Certs have expired, they were valid till: 18 Jul 21 13:36 +0000"
time="2021-07-25T20:57:39-05:00" level=debug msg="error: Temporary error: certificate /var/lib/kubelet/pki/kubelet-server-current.pem still expired - sleeping 5s"
time="2021-07-25T20:57:44-05:00" level=debug msg="retry loop: attempt 57"
time="2021-07-25T20:57:44-05:00" level=debug msg="Running SSH command: date --date=\"$(sudo openssl x509 -in /var/lib/kubelet/pki/kubelet-server-current.pem -noout -enddate | cut -d= -f 2)\" --iso-8601=seconds"
time="2021-07-25T20:57:44-05:00" level=debug msg="SSH command results: err: <nil>, output: 2021-07-18T13:36:23+00:00\n"
time="2021-07-25T20:57:44-05:00" level=debug msg="Certs have expired, they were valid till: 18 Jul 21 13:36 +0000"
time="2021-07-25T20:57:44-05:00" level=debug msg="error: Temporary error: certificate /var/lib/kubelet/pki/kubelet-server-current.pem still expired - sleeping 5s"
time="2021-07-25T20:57:49-05:00" level=debug msg="RetryAfter timeout after 58 tries"
time="2021-07-25T20:57:49-05:00" level=debug msg="Bundle has been generated 37 days ago"
time="2021-07-25T20:57:49-05:00" level=debug msg="Making call to close driver server"
time="2021-07-25T20:57:49-05:00" level=debug msg="(crc) Calling .Close"

So far as I can tell, the only thing not working is kubeadmin.
[protosam@nullhost]$ crc console --credentials
To login as a regular user, run 'oc login -u developer -p developer https://api.crc.testing:6443'.
To login as an admin, run 'oc login -u kubeadmin -p PBese-d6Qg4-tg3Zj-PzWja https://api.crc.testing:6443'

[protosam@nullhost]$ oc login -u kubeadmin -p PBese-d6Qg4-tg3Zj-PzWja https://api.crc.testing:6443
The server uses a certificate signed by an unknown authority.
You can bypass the certificate check, but any data you send to the server could be intercepted by others.
Use insecure connections? (y/n): y

Login failed (401 Unauthorized)
Verify you have provided correct credentials.

To fix this, I just patched the kubeadmin password with the developer password. /shrug
NEW_HTPASSWD=$(echo -e "$(kubectl -n openshift-config get secrets htpass-secret -o=jsonpath='{.data.htpasswd}' | base64 -D | sed -e '/^kubeadmin:.*/d')\nkubeadmin:$(kubectl -n openshift-config get secrets htpass-secret -o=jsonpath='{.data.htpasswd}' | base64 -D | awk -F: '{if($1=="developer"){print $2}}')" | base64)
kubectl -n openshift-config --type merge patch secret htpass-secret -p '{"data":{"htpasswd":"'"${NEW_HTPASSWD}"'"}}'

I'm not really sure what to make of this. It looks like crc should be patching the random password in for me:
https://github.com/code-ready/crc/blob/a70420d59b220a97d4a6b890557d4b294e1538dc/pkg/crc/cluster/kubeadmin_password.go#L24-L58

I am having this same issue on the windows build. I tried your method of patching the password via the developer password. The steps are a little more convoluted in PowerShell, but this worked for me.
$env:KUBECONFIG = "C:\Users\user\.crc\machines\crc\kubeconfig"
$pass = [System.Text.Encoding]::UTF8.GetString([System.Convert]::FromBase64String($(kubectl -n openshift-config get secrets htpass-secret -o=jsonpath='{.data.htpasswd}')))
$env:NEW_HTPASSWD = [System.Convert]::ToBase64String([System.Text.Encoding]::UTF8.GetBytes($($pass -replace '(?<=kubeadmin:).+',"$(($pass | sls  '(?<=developer:).+').Matches.Value)")))
$json = '{"data":{"htpasswd":"<token>"}}' -replace '<token>',$env:NEW_HTPASSWD  | ConvertTo-Json
kubectl -n openshift-config --type merge patch secret htpass-secret -p $json

This is a work around, but it would be great if this was fixed... I am fairly new to okd/os and it creates barriers for getting up to speed fast.

The community is aware of the issue and is working to address it. No ETA at the moment, but we're making some changes that will allow more flexibility in updating OKD CRC.

A workaround for us was to manually issue/approve the newly generated CSRs. After doing so the CRC started without further issues. We just did a internal company workshop using the CRC build from June. A fresh CRC version would be nice, but the old one, especially if you are just starting of with OKD, should be fine.
Here is what we did:

open a second shell where you also export the KUBECONFIG

export KUBECONFIG=~/.crc/machines/crc/kubeconfig

start the CRC from your first shell and wait until it starts the renewal of the serving certificate

...
INFO Kubelet serving certificate has expired, waiting for automatic renewal... [will take up to 8 minutes]

at this point you should be able to communicate with the cluster itself and check for unapproved certificate signing requests
oc get csr
repeat until signing requests appear in pending condition
now you can issue these CSRs manually
oc adm certificate approve <CSR NAME>
repeat the steps 3 to 5 until the CRC prints (1st shell)

INFO Waiting for kube-apiserver availability
...

The CRC startup should now finish without further issues:

INFO Adding crc-admin and crc-developer contexts to kubeconfig...
Started the OpenShift cluster.

If the startup still fails just stop your CRC ./crc stop and start over.
Maybe @JaimeMagiera or some other folks from the OKD Team can confirm this approach?

New release of CRC has been uploaded to okd.io.
Apologies that it took so long.  I had to make some code changes which will be submitted as a couple of PRs to the CRC projects.

@begris That is a fantastic workaround.
It should be possible to inject that logic into the crc binary to automate it.

it looks like the new CRC version is failed again because this issue
CodeReady Containers version: 1.28.0-OKD+08de64bd
OpenShift version: 4.7.0-0.okd-2021-08-07-063045 (embedded in executable)

[core@crc-lrg4f-master-0 ~]$ sudo openssl x509  -in /var/lib/kubelet/pki/kubelet-server-current.pem -enddate -noout
notAfter=Sep 16 11:28:14 2021 GMT

We'll get a new release pushed.

New release being built from 4.7.0-0.okd-2021-09-19-013247

New release is uploading now.  It will take a bit for the files to push to the server.


Appstudio update test-component-pac-ygzk

Pipelines as Code configuration proposal
To start the PipelineRun, add a new comment with content /ok-to-test
For more detailed information about running a PipelineRun, please refer to Pipelines as Code documentation Running the PipelineRun
To customize the proposed PipelineRuns after merge, please refer to Build Pipeline customization

Pipelines as Code CI/test-component-pac-ygzk-on-pull-request has successfully validated your commit.


Add Canada

Add Canadian lookups (based on Geonames.org and converting Tab-delimited to JSON... with extra data that is mostly harmless).

TODO: Update readme.


Error in digitalRead example

Hi there,
there is an error in the MCP23008_digitalRead  example:
MCP.pinMode8(0x00);
should instead be:
MCP.pinMode8(0xFF);
Cheers, Ale.

Thanks for reporting, will have a look asap

Fixed in master branch, not made a new release.
Again thanks for reporting!


How to turn pages when there are a lot of comments and sub-comments?

How to turn pages when there are a lot of comments and sub-comments?turn pages to grouping comments (Newest, Oldest, Popular, ...)?

Can you be more specific please. what do you mean by pages?

I mean , Asynchronously retrieve data for each page from the server , Thank you。

"data-container" class is used down below, you can try using pagination on this class.

Please is there an example how to implement this?


[Bug]: Not working with Forge

What happened?
I installed openOutpaint from Forge and looks fine, but when I go to Stable Diffusion tab and try to select a checkpoint or sampler, it is empty. And refresh does not do anything.  Forge is working fine, checkpoints, loras, embeddings, and general operation is working fine. But Openpaint does not load checkpoints.
Please help
Steps to reproduce the problem
Install OpenOutpaint from forge
Run any promt text2image
Send to outpaint
select a checkpoint
Refresh not working, Model is empty (no options)
What should have happened?
auto update Model field with A1111 settings
Commit where the problem happens
version: f0.0.16v1.8.0rc-latest-240-ga0c89fae  •  python: 3.10.6  •  torch: 2.1.2+cu121  •  xformers: N/A  •  gradio: 3.41.2  •  checkpoint: 676f0d60c8
What platforms do you use to access openOutpaint?
Windows
What browsers do you use to access the UI ?
Opera
Browser Extensions/Addons
Opera Ad Blocker
AUTOMATIC1111 webUI Commandline Arguments
Forge:
set A1111_HOME=I:/stable-diffusion-webui
set VENV_DIR=%A1111_HOME%/venv
set COMMANDLINE_ARGS=%COMMANDLINE_ARGS% ^
--ckpt-dir %A1111_HOME%/models/Stable-diffusion ^
--embeddings-dir %A1111_HOME%/embeddings ^
--hypernetwork-dir %A1111_HOME%/models/hypernetworks ^
--lora-dir %A1111_HOME%/models/Lora
call webui.bat
Additional information
No response

hey, so to my understanding forget doesn't really do anything different than A1111's API, but support for forge is still kind of not really there, it just "works" but hasn't had anything specifically written to accommodate forge in any way outside of what already exists for the A1111 API.
that being said, i can't confirm what you're experiencing - however, i'm not using the @REM statements in webui-user, and set the COMMANDLINE_ARGS essentially as a copy/paste from A1111 webUI with a few additional flags it recommended on startup:
set COMMANDLINE_ARGS=--ckpt-dir "F:\storage\stable diffusion models" --vae-dir "F:\storage\stable diffusion VAEs" --lora-dir "F:\storage\loras" --api --api-log --cors-allow-origins=http://<IP_ADDRESS>:3456 --pin-shared-memory --cuda-malloc --cuda-stream
with --api-log in there specifically, i can verify that (in firefox and chrome, at least, and opera being a chromium offshoot, chrome's rendering engine should be the same, but i admit i haven't tried opera) it does indeed not only list all available models but switches between them as expected
[...]

Using pytorch attention in VAE
extra {'cond_stage_model.clip_l.text_projection', 'cond_stage_model.clip_l.logit_scale'}
Loading VAE weights specified in settings: F:\storage\stable diffusion VAEs\wd13-kl-f8-anime2.vae.pt
To load target model SD1ClipModel
Begin to load 1 model
[Memory Management] Current Free GPU Memory (MB) =  23148.51406097412
[Memory Management] Model Memory (MB) =<PHONE_NUMBER>280762
[Memory Management] Minimal Inference Memory (MB) =  1024.0
[Memory Management] Estimated Remaining GPU Memory (MB) =  21670.306438446045
Moving model(s) has taken 0.19 seconds
Model loaded in 7.3s (unload existing model: 0.3s, load weights from disk: 0.3s, forge load real models: 6.2s, load VAE: 0.2s, calculate empty prompt: 0.3s).
API 2024-03-02 09:38:17.892553 200 http/1.1 POST /sdapi/v1/options <IP_ADDRESS> 7.3328
[...]

any chance you could test it in a different browser, or possibly with the COMMANDLINE_ARGS filled out in the A1111 expected format? my uneducated guess is it's probably the %A1111_HOME% vars more than the browser

Hi, sorry for delay.
I tested with Chrome and Firefox and have same problem
Also I noticed I have this in console when starting Forge:
[openOutpaint-extension-submodule] failed to download update, check network
But when checking extensions check for updates for openoutpaint have latest:
main 1c3a931c 2024-03-02 05:24:12 latest.
Any suggestion?

Hi,
I found I missing --api in command line.
Sorry,
Now it is working fine

Will be closing this issue as solved! If you find any other issues, please file a new issue!