IndexError: list index out of range

I don't know very well how TOML works, but I just stumbled upon this, and it looks like an issue:
>>> toml.loads('foo = [ { bar="\\"{{baz}}\\""} ]')
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/home/dev-py/.local/lib/python3.5/site-packages/toml.py", line 373, in loads
    multibackslash)
  File "/home/dev-py/.local/lib/python3.5/site-packages/toml.py", line 478, in _load_line
    value, vtype = _load_value(pair[1], _dict, strictly_valid)
  File "/home/dev-py/.local/lib/python3.5/site-packages/toml.py", line 635, in _load_value
    return (_load_array(v, _dict), "array")
  File "/home/dev-py/.local/lib/python3.5/site-packages/toml.py", line 739, in _load_array
    nval, ntype = _load_value(a[i], _dict)
  File "/home/dev-py/.local/lib/python3.5/site-packages/toml.py", line 638, in _load_value
    _load_inline_object(v, inline_object, _dict)
  File "/home/dev-py/.local/lib/python3.5/site-packages/toml.py", line 398, in _load_inline_object
    candidate_groups[0] = candidate_group + "," + candidate_groups[0]
IndexError: list index out of range

Thank you for reporting this issue! It looks like there wasn't any backslash detection for detecting string boundaries inside inline tables in arrays of inline tables. This should be fixed by the related commits.


Fix broken code link in OpenApi docs

The link was broken, updated it.
Perhaps we should use a permalink here?

Thanks @ElanHasson! 🚀 ... No permalink for our API code links in the vast majority of cases. We just fix bad links 😈 when they're discovered.

love the yolo @guardrex :D


VTK support

Needs to support old and new (XML) VTK formats.
http://www.vtk.org/wp-content/uploads/2015/04/file-formats.pdf

THREEJS now provides a VTK parser that might be good enough for now.


Make alias protocol_compiler visible

Make //third_party:protocol_compiler target public as required by macros.
Fixes #1189

How was this tested?
Since the previous release had a bug that was only visible in downstream usage, it would be nice to know how you verified there isn't yet another bug present in this release.

@alexeagle I tested this PR with our code base. Of course I cannot guarantee that we are using all code paths. Given that I only searched and replaced the protocol_compiler target in the whole code base as compared to the known working version 1.48.1.bcr.1 and made this target public now, I am quite confident that this should work now.

How was this tested? Since the previous release had a bug that was only visible in downstream usage, it would be nice to know how you verified there isn't yet another bug present in this release.

Downstream user here. The release didn't introduce a new bug per se - it fixed enough for my use case that this one last visibility issue became obvious. And I verified this change is good.
I also don't mind waiting for 1.48.1.bcr.2 to bake longer if anyone's unsure.

gonna go ahead and merge now; if more fixes are needed we can always push a .bcr.4

@Wyverald any idea why the test is failing?

any idea why the test is failing?

This seems to be https://github.com/bazelbuild/bazel/issues/10472. The openssl system headers on the macOS test system are getting picked up in some cases, causing conflicts with the typedefs in BoringSSL's headers.
In file included from external/boringssl~0.0.0-20211025-d4f1ab9/src/crypto/x509v3/v3_skey.c:62:
In file included from /usr/local/include/openssl/err.h:21:
/usr/local/include/openssl/e_os2.h:183:11: warning: 'OPENSSL_EXPORT' macro redefined [-Wmacro-redefined]
#  define OPENSSL_EXPORT extern
          ^
external/boringssl~0.0.0-20211025-d4f1ab9/src/include/openssl/base.h:222:9: note: previous definition is here
#define OPENSSL_EXPORT

@Wyverald friendly ping

Just for my information, do you know why 1.48.1.bcr.2 didn't have this failure? It might be due to some mac CI machine upgrades we did recently; just wanted to confirm.

Just for my information, do you know why 1.48.1.bcr.2 didn't have this failure? It might be due to some mac CI machine upgrades we did recently; just wanted to confirm.

Yeah a machine update could have triggered this if /usr/local/include/openssl/ didn't exist before or contained base.h. I guess the opposite is true now (openssl system headers exist and base.h is not one of them), causing Clang to use some headers from the system and some from boringssl.
It's also possible that the --sandbox_block_path=/usr/local workaround was removed (e.g., maybe the build user's .bazelrc was deleted).

@Wyverald Could you please trigger the tests again?
I tried applying the workaround from #10472.

the workaround is unfortunately breaking the windows build; you'll need to separate the CI configs for those platforms

the workaround is unfortunately breaking the windows build; you'll need to separate the CI configs for those platforms

Well, it does proof that the problem is bazelbuild/bazel#10472 and in turn unrelated to this PR. So can't we just merge the first commit without the workaround as it works as intended and just the CI is broken?

I modified the workaround to be applied for macOS only.

Thanks for pulling through! All looks good now.


Error estimating fee

Not sure whether the issue is on Insight side, but I got the following in BWS logs:
WARN Insight https://insight.bitpay.com:443/api/utils/estimatefee?nbBlocks=1,2,6 Returned Status: 400
ERR! Error estimating fee Error querying the blockchain

Insight response:
Method not found. Code:-32601

Did you just recently start up your node (the one behind the insight instance)?
Estimate fee will fail until bitcoind has had time to calculate the fee estimates. (You will have to wait a few blocks after you start up bitcoind before it starts working with estimatefee.)

That's on insight.bitpay.com

Now is something else:
WARN Insight https://insight.bitpay.com:443/api/tx/send Returned Status: 400
ERR! /v1/txproposals/01460455176797b749c5f7-799d-4ada-823e-ef92a44501f9/broadcast/ :500:Error querying the blockchain


[$250] Remove MoneyRequestConfirmationList.js and copy any changes since Nov 27 into MoneyTemporaryForRefactorRequestConfirmationList.js

This is a part of https://github.com/Expensify/App/issues/29107. You can look at that issue for more context behind the cleanup process.
Problem
The app has two redundant components:
Old Component: MoneyRequestConfirmationList
New Component MoneyTemporaryForRefactorRequestConfirmationList
Solution
Now that most of the referenced components have been cleaned up and following the examples (example 1, example 2), the Old Component needs to be completely removed from the codebase

Look at the history of the Old Component
If there are any changes since Nov 27, 2023 which have not been added to the New Component, copy those changes
Replace all uses of the Old Component with the New Component
Remove all traces of Old Component

Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~01a11e5428841cbb31
Upwork Job ID:<PHONE_NUMBER>127291392
Last Price Increase: 2024-04-03

@bfitzexpensify I might have messed up on the price for this. Can you please confirm for me that the UpWork issue is $250?

Proposal
Please re-state the problem that we are trying to solve in this issue.
Remove MoneyRequestConfirmationList.js and copy any changes since Nov 27 into IOURequestStepConfirmation.js
What is the root cause of that problem?
New Feature
What changes do you think we should make in order to solve the problem?
Old Component: MoneyRequestConfirmationList
New Component IOURequestStepConfirmation

Look at the history of the Old Component
If there are any changes since Nov 27, 2023 which have not been added to the New Component, copy those changes
Replace all uses of the Old Component with the New Component
Remove all traces of Old Component

Proposal
Please re-state the problem that we are trying to solve in this issue.
This belongs to Wave 5 cleanup
Phase 2 is all about removing the original components and any of the duplicated efforts.
What is the root cause of that problem?
Replace MoneyRequestConfirmationList to IOURequestStepConfirmation.
What changes do you think we should make in order to solve the problem?

Look at the history of the Old Component
If there are any changes since Nov 27, 2023 which have not been added to the New Component, copy those changes

From history change I didn't find any changes that should be carried over. Since we have MoneyTemporaryForRefactorRequestConfirmationList we were using it and working on it, so all the important changes were made to it.

Replace all uses of the Old Component with the New Component
Remove all traces of Old Component

We use MoneyRequestConfirmationList only at SplitBillDetailsPage. We can replace it with MoneyTemporaryForRefactorRequestConfirmationList (we already use MoneyTemporaryForRefactorRequestConfirmationList in the new component IOURequestStepConfirmation).

After remove MoneyRequestConfirmationList  rename MoneyTemporaryForRefactorRequestConfirmationList and all it uses.

Be sure to update all routes and navigation to use the new :action param (instead of being hard-coded with "create")
Update any logic like isEditing to use the new action param from the route

What alternative solutions did you explore? (Optional)
N/A

@bfitzexpensify I might have messed up on the price for this. Can you please confirm for me that the UpWork issue is $250?

Confirmed it's $250

Asked a question in the parent issue https://github.com/Expensify/App/issues/29107

Proposal
Updated
https://github.com/Expensify/App/issues/29107#issuecomment-2037221079: Remove MoneyRequestConfirmationList.js and copy any changes since Nov 27 into MoneyTemporaryForRefactorRequestConfirmationList.js
MoneyRequestConfirmationList has been migrated to TypeScript, so first we need to migrate MoneyTemporaryForRefactorRequestConfirmationList to TS as well.

MoneyRequestConfirmationList has been migrated to TypeScript, so first we need to migrate MoneyTemporaryForRefactorRequestConfirmationList to TS as well.

@brunovjk Thanks for the update. That's a good point.
@tgolen Should we do migrating MoneyTemporaryForRefactorRequestConfirmationList to TS in this task? Or in a separate task just like other TS migration tasks?

Ah, I would probably avoid doing both the TS migration and the cleanup in the same task (to keep the PR scope smaller). Would it be better to do the TS migration first or second?

Sorry everyone, I confused IOURequestStepConfrimation.js with MoneyTemporaryForRefactorRequestConfirmationList.js.
This issue doesn't need to have anything major done with IOURequestStepConfirmation.js.
This issue should be for replacing MoneyConfirmationList with MoneyTemporaryForRefactorRequestConfirmationList.

Updated my proposal according to the last comment

Proposal
Updated

Added clarification on passing splitTag to MoneyTemporaryForRefactorRequestConfirmationList.

Ah, I would probably avoid doing both the TS migration and the cleanup in the same task (to keep the PR scope smaller). Would it be better to do the TS migration first or second?

Yeah, I agree it's better to do them one by one. I found there's an ongoing PR https://github.com/Expensify/App/pull/37181 to migrate MoneyTemporaryForRefactorRequestConfirmationList.js. I think we can wait for that PR.
Once the TS migration PR is merged, I think we can let @brunovjk  to take this task as their proposal first pointed out we should replace MoneyConfirmationList with MoneyTemporaryForRefactorRequestConfirmationList and @brunovjk also started the discussion about TS migration.
@tgolen All yours.
🎀👀🎀 C+ reviewed

I'm going to unassign myself since Tim will be back from OOO tomorrow and it doesn't seem like this is quiet ready to be assigned out? 🤷

@bondydaa Thanks for your comment. This issue needs to wait for the TS migration to be merged, so I think we can wait for @tgolen .

Thank you, accept the offer. I will wait for the migration to complete to raise the PR. I believe it will be soon.
@eh2077 should we wait the 7 days of the migration regression period to merge our PR?

@brunovjk I think generally you can start working on the PR once the migration PR is merged.

Thanks :D

TS migration has been merged. I will start working on our PR immediately.

PR ready for review

LGTM and tested well! https://github.com/Expensify/App/pull/40176#pullrequestreview-2008558539

Yep! We are good to go :D

We merge @MrMuzyk

@brunovjk I think something might be off when it comes to displaying footer. I can't review the Split expense request

I might be mistaken but this condition should probably be reversed
https://github.com/Expensify/App/blob/9b2c5187e2203d83bba50bfa66936691788cbd18/src/components/MoneyRequestConfirmationList.tsx#L931

@MrMuzyk You're right, sorry, I missed that.
What do you think about using the isReadOnly variable, something like this:
footerContent={!isReadOnly && footerContent}

I tested it and it seems to do the job. I can raise a PR to fix today.

At first glance it seems to work 👍 It's probably worth for people who reviewed the PR to have a look at it too.

I think something might be off when it comes to displaying footer

@eh2077 Let's fix this before going to QA, let's avoid a regression here :D

@brunovjk Sure. Please tag me when the PR is ready, thank you!

We already have a PR https://github.com/Expensify/App/pull/40659 to fix the DB

@brunovjk yes, the solution in this issue caused a regression, so the regression penalty applies.
Payment to @brunovjk complete.
@eh2077, please complete the BZ checklist so I can finalise payment. Thanks!

BugZero Checklist: The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed:

[x] [@eh2077] The PR that introduced the bug has been identified. Link to the PR: This is not a bug. It's part of refactoring.
[x] [@eh2077] The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake. Link to comment: N/A
[x]  [@eh2077] A discussion in #expensify-bugs has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner. Link to discussion: N/A
[x] [@eh2077] Determine if we should create a regression test for this bug. N/A

BugZero Checklist: The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed:

[x] [@eh2077] The PR that introduced the bug has been identified. Link to the PR: This is not a bug. It's part of refactoring.
[x] [@eh2077] The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake. Link to comment: N/A
[x]  [@eh2077] A discussion in #expensify-bugs has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner. Link to discussion: N/A
[x] [@eh2077] Determine if we should create a regression test for this bug. N/A

@bfitzexpensify  Could we get an increase in the bounty  here? Mainly to cover the regression. Despite being a simple refactoring here, the component is used in several flows, create and edit as well. Excessive testing was done during and after the PR was merged. Thank you 🙏

To make it easier to evaluate @brunovjk 's request above, I'd like to add on:
Though we conducted many tests in the main PR https://github.com/Expensify/App/pull/40176, we still slipped up a bit. There're two fix PRs after the main PR

https://github.com/Expensify/App/pull/40659

[!NOTE]
The first fix PR was up before the main PR hit staging (means the DB was created later) and was merged shortly when the DB was linked, see https://github.com/Expensify/App/issues/39559#issuecomment-2066409074

https://github.com/Expensify/App/pull/41152

[!NOTE]
The second fix PR was a minor issue that reported by https://github.com/Expensify/App/pull/40176#issuecomment-2079801206 (There's no dedicated GH issue created for it)

Below are my two cents on this
Given @brunovjk was dedicated and proactive in whole process of this task 👍, it would be encouraging to be exempt from penalty. Or let's just move on, it happens.
cc @bfitzexpensify @tgolen

Will defer this one to you @tgolen - what do you think an appropriate bounty is for this issue?

The scope of this issue was pretty large and I am OK authorizing an increase to $500.

Thanks!
OK, payment of $500 finalised to @eh2077, and bonus of $375 paid to @brunovjk
Thanks for the work here, everyone!

Thank you all! It's always good to contribute to Expensify!!! 🌟


Fixed: Nested/mixed selectors now works correctly

This commit include a refactoring based on postcss-selector-matches and
add the ability to limit the transformation to :matches() usage.
I may have removed some tests already covered by postcss-selector-matches
Also in this commit:

add eslint
rewrite using babel (es6/7)
fixtures files removed in favor of es6 template string
should also fix some weird “undefined” warnings

Close #19
@yisibl feel free to update the README-zh as well (I moved the nodejs/grunt/gulp stuff at the end since most people already know how to do that part most of the time).
By the way, are you open to add me as a collaborator on npm? ($ npm owner add moox postcss-custom-selectors) so I can push release directly?

By the way, are you open to add me as a collaborator on npm? ($ npm owner add moox postcss-custom-selectors) so I can push release directly?

No problem!

Thanks!


Create new images with tags for ceph version

We currently ship firefly as latest tag, we should move to giant and add a tag for firefly.
Next steps:

[x] Create firefly branch in Github
[x] Create firefly tag referencing that branch on Docker Hub
[ ] Update each FROM statements in Dockerfiles for downstream components in the firefly branch to reference ceph/base:firefly
[ ] Create firefly tags for each downstream component on Docker Hub

I've got to run for a few hours; if it's not done before 20:00 UTC, I'll complete the last two steps here.

I don't think I'll have time to do this today.

No problem; I just wanted to make sure we didn't both work on it, since this was assigned to you at the time.

Giant tags on docker track the master branch, for now.


Use the Dedicated server Steam App instead of downloading whole game.

There is a space engineers dedicated server App on steam now so you can directly download it instead of downloading the whole game and extracting the dedicated server files. The appid is 298740, here is the reference on steamdb https://steamdb.info/app/298740/

just submitted a fix for that #13

This was merged so you can close this @NolanSyKinsley


load extension account after user selects extension option (kusama)

Metging main to Kusama theme.
The changes includes:

moved load extension accounts to a separate module (extension.js), and set it to load the extension after user has selected the polkadot extension option. (closes #41 , #73)
fixed the case where work-0 would be selected in verify seed phrase (fixes #82 )

closing this since the counterpart PR is opened from the topic branch as #86

closing this since the counterpart PR is opened from the topic branch as #86


Scrutinize code so that Scrutinizer is happy

Probably not worth a new tag for this, but wanted to get it pushed upstream.

Now that this PR includes json-api/json-api#447, a new tag is a good idea, given that this is a breaking change.

Great work @pmccarren

Tagged as v2.2


fix alpha value on material value

The alpha value should be 0.5 by default to avoid the message in the console build

I trust you, let's merge this.


When only one slide in  the slider, it still  displays many

When the slider has only 1 slide and loop=true, the user could still navigate back and forth. However, the user navigates to the same slide, which is confusing for the user, since he sees the same slide all the time.

Hey,
From v0.6.2, if the slide item count is the same with the items in the options, the nav and controls will not be displayed.
Would you mind to check it?

I checked and the items=1 option does not fix this issue. Why do we need the items option if the slider can detect the number of slide in the slider?

I checked and the items=1 option does not fix this issue.

Are you able to make a demo?

Why do we need the items option if the slider can detect the number of slide in the slider?

Even though we can detect the slider number, but you may have different option. E.g. the slider number is 8, but I want to show only 3 in a page.

Also if there is only 1 slide in the slider, there is no need for extra clones.

The extra clones are for the loop and is been done in the initialization stage. It's specially useful when you have many breakpoints. I clone it first, because I don't want to check the init for every resize event.
While, in reality, if you know you will have only one slide, why do slider any more?


⚠ Bofrost.de has degraded performance

In 5d384aa, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 958 ms

Resolved: Bofrost.de performance has improved in 2a409b9.


feat: remove emoji tag from data-code-raw in pre

Fixed Issues
$ GH_LINK
Tests

What unit/integration tests cover your change? What autoQA tests cover your change?
What tests did you perform that validates your changed worked?

QA

What does QA need to do to validate your changes?
What areas to they need to test for regressions?

I have read the CLA Document and I hereby sign the CLA

recheck


Add monochrome icon

Please add support Themed Icon on Android.

Hi @xmha97,
I have added a monochrome icon and tested on an Android 13 emulator. I don't have a physical Android 13 device. Would you be able to try this out? Thanks.

Yes, please release a new version.

I have pushed a new release to the Beta channel.


Pluggable authentication

Build authentication between clients and the Cactus API

clients supports basic auth, apiKey, accessToken now - closing


Update to 1.4.1 gem?

The latest gem version is <IP_ADDRESS> and noch 1.4.1.
Would you generate a new gem?

:+1:

:+1:

@RyanScottLewis PR 12 proposed.


Curry: Add functions curry2 through curry5

Hi, first pull request here. Thanks for the hand-holding. This closes #277.
Things not complete or I'm not sure about:

[x] Examples for curry3 - 5.
Looks like all of the examples in the readme are one liners.
[x] Documentation text is probably too short, but I'm not the one that should be explaining currying to anyone.
[x] I probably skipped some test cases. Is there an S.__ or similar that needs to be tested?
[x] The definition forvar e = $.TypeVariable('e'); is skipped and I don't know why. So curry4 and 5 don't have an 'e': S.curry4 = def('curry4', {}, [$.Function, a, b, c, d, f], curry4);
[x] Not sure what variable names people traditionally use for functions of large arity.
I have function(v, w, x, y, z)...
[x] Should I make the README and commit, or does that happen later?

Thanks for the pull request, @laduke! It's exciting to have received pull requests from three new code contributors in the past week!
I edited this pull request's description to include the substring closes #277 so the issue this pull request addresses will automatically be closed when this pull request is merged. See Closing Issues via Pull Requests for details. :)

The definition forvar e = $.TypeVariable('e'); is skipped and I don't know why.

We simply haven't needed this so many unary type variables before, but we're free to define e. :)

Should I make the README and commit, or does that happen later?

The readme gets updated automatically at release time. See https://github.com/sanctuary-js/sanctuary-set/pull/1#issuecomment-258782119 if you're interested in the details.

Thank you for your patience @davidchambers.

I've become spoiled by jsfmt. Sorry about those.

We should make it clear that the functions are curried Ramda-style. I'd like to see two applications of each function. For example:
> toUrl('https:')(S.Nothing)('example.com')(S.Just('443'))('/foo/bar')
'https://example.com:443/foo/bar'

> toUrl('https:', S.Nothing, 'example.com', S.Just('443'), '/foo/bar')
'https://example.com:443/foo/bar'

Chippin' away. Thanks for that script.

Looking good, @laduke! After addressing the final comment could you squash the commits and rebase on master? We'll then be ready to merge, I think. :)

Oops!

🎉

$ npm install<EMAIL_ADDRESS>
$ node
> const S = require('sanctuary')
undefined
> S.curry2
curry2 :: ((a, b) -> c) -> a -> b -> c
> S.curry3
curry3 :: ((a, b, c) -> d) -> a -> b -> c -> d
> S.curry4
curry4 :: ((a, b, c, d) -> e) -> a -> b -> c -> d -> e
> S.curry5
curry5 :: ((a, b, c, d, e) -> r) -> a -> b -> c -> d -> e -> r


feat: read/unread states

Notify Server PR: https://github.com/WalletConnect/notify-server/pull/423


Merge UAT to Master 28 Mei 2018

Coverage decreased (-0.0004%) to 78.419% when pulling b6638eeb604b3e949bcc971fbe7dfc203aebf43b on uat into 30fa2c96a0e7a409a6f2d508a35da73d35314aeb on master.


Getting Started/Workflow Guide for just TFS

Pretend you are familiar with GitHub and GitLab and now you've been invited to contribute to a project being hosted on TFS. You want to double check Microsoft's definition of "fork" vs "clone" so, from within TFS, you start looking for help.  Is it possible? I finally made my way here, but it wasn't any better. I found the documentation site (the design of which looks awesome, btw) but now TFS has morphed into an "Azure" product? There is no simple getting started guide.

There needs to be a more obvious way to get from TFS to the documentation site, since that is where it looks like most answers should be and since it was deemed unnecessary to have help within the app.
There needs to be a way to get information on the product I want to use without being force fed content about other products, if that's what's going on. I don't even know. I just couldn't find the information I needed about the TFS workflow.
I should be able to search for a term like "fork" and get at least one response, right?

This experience does not win any points for TFS as we evaluate adopting a collaborative development platform.

@cillroy Is this your area you can follow up?


kubeconfig file correction

kubeconfig file flag change.

I believe just for sake of consistency with other components in kubernetes ecosystem, this PR should go in ahead of #37, @aveshagarwal @containscafeine WDYT?

Not sure why I had kubeconfig-file, but @ravisantoshgudimetla  if you have verified that kubeconfig is everywhere instead of  kubeconfig-file, lets go ahead with this, and close the other ones.


System.InvalidOperationException: Cannot call Set on a null context

After I built the latest corert build, I started gettting this error when working with WebClient and httpClient

Could you please share the callstack and/or repro?
cc @stephentoub This is likely related to one of the execution context optimizations. I expect that it will show up in UAPAOT runs eventually as well.

@jkotas It only happens once it's compiled into .net native.

Understood. It is likely CoreRT-specific bug. The code for handling execution contexts is not reconciled between CoreCLR and CoreRT yet, and so there can be behavior differences between the two.
Could you please add <IlcArg Include="--stacktracedata" /> to the .csproj file, recompile and run your test? This options enables full textual stacktraces, and so the exception string will have the information that will help us to diagnose this.

@jkotas I'm sorry for asking a question which I would think most people would know the answer to, but where exactly should I put <IlcArg Include="--stacktracedata" /> in the .csproj file?

No problem ... I agree that it is not obvious where to put it. It should be inside ItemGroup. It does not matter where exactly. It can be the last thing in the .csproj file.
  <ItemGroup>
    <IlcArg Include="--stacktracedata" />
  </ItemGroup>

</Project>

Unhandled Exception: System.InvalidOperationException: Cannot call Set on a null context    at System.Threading.ExecutionContext.ThrowNullContext() + 0x2d    at System.Threading.Win32ThreadPoolNativeOverlapped.CompleteWithCallback(UInt32, UInt32, Win32ThreadPoolNativeOverlapped*) + 0xc7    at System.Threading.ThreadPoolBoundHandle.OnNativeIOCompleted(IntPtr, IntPtr, IntPtr, UInt32, UIntPtr, IntPtr) + 0x97


Background image resizing issue

Hi! When resizing the window, the background image doesn't cover completely at the bottom.

I would recommend the following:

Remove the inline style at <div class="image-container set-full-height" style="background-image: url('assets/img/wizard.jpg')">
And put a block style as

<style>
        body {
            background: url('assets/img/wizard.jpg') no-repeat center center fixed;
            -webkit-background-size: cover;
            -moz-background-size: cover;
            -o-background-size: cover;
            background-size: cover;
        }
</style>

It worked for me.

@akshaybabloo thank you for pointing out. Yes, you're right, there is an issue with the image, we will fix that based on your code in our next update.
All the best,
Alex


Use sysconfdir & localstatedir for conf/pid/logs

Use autoconf-supplied paths as the default values for the configuration
file, the pidfile and the logfile. So, for example:
/etc/nutcracker/nutcracker.yml
/var/run/nutcracker/nutcracker.pid
/var/log/nutcracker/nutcracker.log
The separate subdirectory under /var/run was picked since nutcracker
doesn't possess the capability of dropping privileges by itself, so we
need to have a system user writeable directory to place the pidfile.
Similarly, we need a separate /var/log subdir as logs can't go to
syslog, and out of convenience (need to be able to perform logrotate,
cleanup upon removing a package etc.)
The separate subdirectory under /etc/ is just for being pretty
(top-level /etc conffiles are ugly) and for future use (multiple configs
for the same daemon?)
All of the above can of course be used in the case where a single init
script spawns multiple nutcrackers, each with a separate config, pidfile
and logfile, for example for extra redundancy reasons.
(also fix an underlying bug where NC_PID_FILE was completely unused)

Ping?

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

This is a 6-year old unacknowledged patch which I've given up on. If someone is interested in reviving this, I can be persuaded to sign a CLA, but otherwise I have no intentions of bothering with that as things stand. HTH!


Create pypi packages for all plugins

PyPI package for cxflow-tensorflow created. Moving the issue to the respective repositories.


Failure on repeated JNI connection

Hi! I'm trying to run ZetaSQL analyzer from a Scala macro, to make some query validation at compile time. It works wonderfully on the first compilation, but when I try to change code (or just clean) and compile again it crashes with this error message:
[libprotobuf FATAL external/com_google_protobuf/src/google/protobuf/extension_set.cc:93]
Multiple extension registrations for type "google.protobuf.FieldOptions", field number 68711883.

libc++abi.dylib: terminating with uncaught exception of type google::protobuf::FatalException:
Multiple extension registrations for type "google.protobuf.FieldOptions", field number 68711883.

This can be reproduced without any macros, just doing a normal runtime call to the ZetaSQL API with the build tool (sbt) trying to reuse the same JVM. It works with forking JVM for each run, but it's not a solution for the original use case (calling ZetaSQL at compile time).
I tried a few things, including reimplementing JniChannelProvider in Scala to be able to localize the problem and potentially tweak its behavior. Unfortunately, I don't know what I could (safely) tweak to make it work. As far as I understood the problem is not in the JniChannelProvider itself, but in the JNI library being loaded twice. I thought that maybe I can avoid that, so I tried this:

extract the .dylib file and load the library from that stable location (in contrast to how cz.adamh.utils.NativeUtils extracts it to a new temp location every time), that led to

UnsatisfiedLinkError: Native Library [...]/liblocal_service_jni.dylib already loaded in another classloader

load it conditionally by checking if the classloader already has it (after the first run), that led me to

UnsatisfiedLinkError: static.experiment.SocketProvider.getSocketChannel()Ljava/nio/channels/SocketChannel;

So from that I'm deducing that the problem is in the native getSocketChannel method. I'm hoping to get some insights in the way it works. I tried to look at zetasql/local_service/local_service_jni.cc but didn't understand much. Maybe it can be made idempotent to avoid "multiple extension registrations"? Or maybe I'm doing it all wrong and should somehow reuse the connection?
I can provide more details and some code if that helps. I would appreciate any advice or information.

The ZetaSQL native library can only be loaded once per JVM. The UnsatisfiedLinkError: Native Library [...]/liblocal_service_jni.dylib already loaded in another classloader error is correct here. (It seems the cz.adamh.utils.NativeUtils library is bypassing the protections in the JVM. The crash you are seeing is deep in the C++ code, it is failing to initialize because it is already initialized.)
For performance, SBT is doing some unusual things with class loaders that cause this. It appears there is a classLoaderLayeringStrategy config that you can use by only loading this library once with the AllLibraryJars or Flat setting.

@apilloud thank you for the quick reply!

The ZetaSQL native library can only be loaded once per JVM. The UnsatisfiedLinkError: Native Library [...]/liblocal_service_jni.dylib already loaded in another classloader error is correct here.

Okay, this is good to understand. As I mentioned, I tried to skip the NativeUtils.loadLibraryFromJar line based on whether the library has been loaded before and that resulted in an UnsatisfiedLinkError regarding the getSocketChannel method. So I'm not sure how to make use of that native method assuming that the JNI library has been loaded. But I guess it's better to ask this with some reproducible code examlpe.

The crash you are seeing is deep in the C++ code, it is failing to initialize because it is already initialized

Could you clarify, just for my understanding, what is being initialized in the code that's failing?

It appears there is a classLoaderLayeringStrategy

Yes, thanks for pointing it out. I did try to change this setting, but it didn't help. I will try a bit more, but I don't think it will help. I think the issue is that the channel provider is loaded dynamically via ServiceLoader, so even if we cache all dependency jars, this class will be initialized after that (when trying to instantiate ZetaSQL formatter or analyzer), so it will make a call to load the JNI part and on the second run fail again.

The UnsatisfiedLinkError: static.experiment.SocketProvider.getSocketChannel()Ljava/nio/channels/SocketChannel; is because the RegisterNatives method hasn't been called on your class. It is called in JNI_OnLoad_zetasql_local_service, which is called by java.lang.ClassLoader.NativeLibrary.load(), which is called right after already loaded in another classloader is thrown in java.lang.ClassLoader.NativeLibrary.loadLibrary1(). If you deleted the code that generates the already loaded in another classloader exception this might work. I believe it is safe to call JNI_OnLoad_zetasql_local_service multiple times.
I believe the line that generates the code that crashes is this one: https://github.com/google/zetasql/blob/cc1e20d6c800daf3270b5dee07fbf9315409e3fa/zetasql/public/proto/type_annotation.proto#L173
Protobuf generates C++ code that is registering a new enum in a static initializer using a dynamically linked protobuf method. That registration is failing because the extension is already registered. This is approximately equivalent to a java class doing Class.forName("proto2.TypeRegistry").register(type), where reflection is returning proto2.TypeRegistry from the system class loader instead of the context class loader. I believe this issue is relevant (but not the only one): https://github.com/protocolbuffers/protobuf/issues/6029

@apilloud thank you so much for the links and a detailed explanation! I followed your advice and made it work 🎉
I did solve it with a call to the NativeLibrary.load method at first, but that seemed overcomplicated and required instantiating the NativeLibrary class via reflection (because the nativeLibraries field doesn't contain the library after first compilation).
So another way to achieve the same (or very similar result) is to remove the mention of the library in the loadedLibraryNames field and call System.load on that path again. This goes the normal way it would usually go, but bypassing the check that causes the "already loaded" exception. One caveat of this approach is that I can't rely on cz.adamh.utils.NativeUtils, because it deletes the extracted library file right after it's loaded. I replaced that with .deleteOnExit() to keep the extracted file for the lifetime of the JVM and (re)load it with the described method.
This overall feels rather hacky, to be honest, and I'm worried that it might be adding some unnecessary overhead to incremental compilation. But it's definitely better than nothing and is totally fine for the proof-of-concept that I'm building at the moment.


DEBUG: Debug binary #2

[x] Direct CAN

[x] sending
[x] receiving

Codecov Report

Merging #141 (25b9cce) into debug-binary (2de0c67) will decrease coverage by 0.06%.
The diff coverage is 10.00%.

@@               Coverage Diff                @@
##           debug-binary     #141      +/-   ##
================================================
- Coverage         39.15%   39.09%   -0.07%
================================================
  Files                66       66
  Lines              3762     3763       +1
================================================
- Hits               1473     1471       -2
- Misses             2289     2292       +3

Impacted Files
Coverage Δ

src/sensors/bms.hpp
100.00% <ø> (ø)

src/utils/io/can.cpp
23.61% <0.00%> (-3.15%)
:arrow_down:

src/utils/io/can.hpp
100.00% <ø> (ø)

src/debugging/observer.cpp
32.22% <40.00%> (ø)

Continue to review full report at Codecov.

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


Node approval process design

if a user doesn't open voyager for more than 3 weeks voyager will not be able to safely determine what the validator set is - and therefore will not be able to trust any data.
so we'll need to track time for our users - so we can notify them when it has been 3 weeks and we'll need to provide a mechanism for verifying the real validator set (maybe by verifying a hash of the current set).
this is an interesting and unique design / technical problem.
maybe @mappum has some insights here.

We actually have a modal to approve a validator hash implemented.
Is it really 3 weeks? This sounds strange in a blockchain context. Maybe block height? Or just the diff of the validators is > 1/3?

We actually have a modal to approve a validator hash implemented.

😍 — i'd still like to discuss how we can help users get this hash.

Is it really 3 weeks?

apparently, yes. i'm sure we can translate this to block height.

the diff of the validators is > 1/3

this is also something to consider i think!

as discussed in the ui / ux call

the time period is however long the unbonding period is (30 days / 3 weeks)

introduce "trust status" - LCD will check 100 nodes (every startup / every week) to see if more than 2/3 of full nodes agree on the validator set hash

no need to notify with modal unless more than 1/3 disagree

will help build trust with user and provide important assurances from a security perspective

ui designs to come 🎨

Link #55 #1222

Can we close this now that we're always connecting to the same node?

i think so

ok, we can reopen the topic when we have more dynamic nodes.


afterglow-cursors-recolored: init at unstable-2023-10-04

Description of changes
afterglow-cursors-recolored: init at unstable-2023-10-04

Things done

Built on platform(s)

[X] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[X] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.05 Release Notes (or backporting 23.05 and 23.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[X] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-ready-for-review/3032/3350

Just not sure if we should use lowercase options for the enum or as they are currently with the first letter uppercase.

Result of nixpkgs-review pr 284617 run on x86_64-linux 1

1 package built:

afterglow-cursors-recolored

@h7x4 about this PR, is something still required?


Make logging consistent

The current logging situation is a little bit ad-hoc. There is no enforced standard, and we would benefit greatly from a serviceability and usability point if we were to enforce logging standards across the Caliper code base.
We should be logging at debug level:

[ ] entry/exit from every method, including passed values

We should be logging at error level

[ ] every error thrown through the code

We should be logging at info level:

[ ] caliper lifecycle items
[ ] round information and basic statistics (we do this already)

Hey I would like to contribute to Caliper, starting with this issue.

@amogh-jrules Awesome! To get familiar with the logging aspects you can refer to this doc page: https://hyperledger.github.io/caliper/vNext/logging/
We're changing a LOT of the core code right now, so give us a few days to finish it, just to avoid a conflict hell :)
And drop by the next Caliper call, so we can have a discussion about the logging rules/guidelines:
https://github.com/hyperledger/caliper/wiki/Caliper-Calls

Thanks, I'll do that!

Hey, may I begin?

@amogh-jrules Sorry for the late reply. After PR #682 is merged, you can start working on the "master modules" in the following directory: https://github.com/hyperledger/caliper/tree/master/packages/caliper-core/lib/master
Until that time you can still inspect the different SUT adapters whether they require additional logging (probably yes). I'd recommend to start with the following adapters: Fabric, Ethereum, Sawtooth and FISCO-BCOS.
One thing to look out for: the invokeSmartContract and querySmartContract methods are considered hot paths, so they're performance critical, try not to stringify big objects during logging.

Okay, thanks, if I have some queries where can I discuss them? Is there a community channel for this project?

@amogh-jrules Yes, see the Communication section of this page:
https://wiki.hyperledger.org/display/caliper

Is this issue resolved? If not can you explain a bit about the issue?
I am new to this ecosystem but would like to start with this issue if it's open. Please share some beginner-friendly resources if possible.

The issue is far from resolved, so every contribution is welcome! Check the following doc for guidelines on contributing: https://github.com/hyperledger/caliper/blob/main/CONTRIBUTING.md

Ok. Thank you!
Checked CONTRIBUTING.md,

@Tezas-6174 That sounds like a good workflow. Correcting error message per package sounds reasonable

Yes. So now, I will start by working on caliper-cli package following the above workflow.
Thank you.

May I work on this issue ?
@aklenik @nklincoln


Update docs

Codecov Report

Merging #214 (0b9b74c) into master (5f75ed4) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master     #214   +/-   ##
=========================================
  Coverage     70.29%   70.29%
  Complexity      596      596
=========================================
  Files            90       90
  Lines          2057     2057
  Branches        224      224
=========================================
  Hits           1446     1446
  Misses          533      533
  Partials         78       78

Continue to review full report at Codecov.

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


Language provider

This PR adds a Provider for languages. It has en_US and nb_NO language names, both taken from a list on wikipedia.
Example output can include:

Afrikaans
English
Norwegian

Nice work. Although I advise that you create a specialized provider for that, and publish it as a standalone package.


Bug: natural sort ignores order

Describe the bug
Please see the self-explicit code example below.
Code example
Configuration:
{
  type: 'natural',
  order: 'desc'
}

Code:
interface Test {
    a
    b
}

No error is reported.
ESLint version
8.57.0
ESLint Plugin Perfectionist version
4.1.2
Additional comments
No response
Validations

[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.

Fixed in 82cb68a964fcb03869b415eea4d665ad305c8ca1.
Released in v4.2.0.


ec2 added to localstack services enum

Now the EC2 service can be initialized like the other services.
This should close localstack/localstack#3590

Hi @rnorth, I'm sorry to bother you.
Could you review this PR?.
Thanks


Discussion / Question: offer recommendation for usage in libraries or applications?

Hi @AndersDJohnson,
Great library, thanks for making it.
As I was using use-yarn for the first time I realized that it is ideal to use it in applications but probably not in widely distributed libraries since its functionality (when in preinstall) trickles into downstream dependencies. So if Library A implements use-yarn and Library B relies on it then now Library B is effectively also going to get use-yarn as a constraint. Now this might be intended for some people but not for others.  I think the key is letting people that use use-yarn know that by using it they will be enforcing this constraint on their downstream dependencies.
So in the end it seems like use-yarn is probably mostly useful for
A) Applications or
B) For libraries whose downstream dependents explicitly do not need to support npm (favoring yarn instead).
Does that sound right to you?

@jimthedev You are right that this was incidentally designed for use in applications rather than libraries. Do you have any ideas how to solve the preinstall hook issue to allow it to be used in libraries as well? Maybe some NPM environment variable to indicate whether this is a dependency of the root package or of a (possibly transitive) dependency?

I would suggest using the prepare hook, rather than preinstall

@nevir Hi, thanks for participating the discussion. Can you explain the advantages of prepare over preinstall for this use case?


@marmeladema

    @marmeladema

Originally posted by @Nuttapon43 in https://github.com/cloudflare/sliceslice-rs/issues/77#issuecomment-1303236565

    @marmeladema

Originally posted by @Nuttapon43 in #77 (comment)

@Nuttapon43


bug: [Ionic 4.6.0] Icons not loaded in prod using relative path

Bug Report
Ionic version:

[x] 4.6.0
Current behavior:

Building ionic app with ionic build --prod and publish it in prod environment. Load the app then icons are not displayed.
Expected behavior:

Should be able to load ionicons. This was working perfect when<EMAIL_ADDRESS>We had to downgrade to 4.5.0 :c
Steps to reproduce:

Upgrade from 4.5.0 to 4.6.0 version, building ionic app with ionic build --prod and publish it in prod environment

Other information:

Ionic info:

Ionic:

   Ionic CLI                     : 5.1.0 (/usr/local/lib/node_modules/ionic)
   Ionic Framework               : @ionic/angular 4.5.0
   @angular-devkit/build-angular : 0.13.0
   @angular-devkit/schematics    : 7.2.3
   @angular/cli                  : 7.3.1
   @ionic/angular-toolkit        : 1.4.0

Cordova:

   Cordova CLI       : 9.0.0<EMAIL_ADDRESS>   Cordova Platforms : ios 5.0.1
   Cordova Plugins   : cordova-plugin-ionic-keyboard 2.1.3, cordova-plugin-ionic-webview 3.1.2, (and 14 other plugins)

Utility:

   cordova-res : not installed
   native-run  : not installed

System:

   ios-sim : 8.0.1
   NodeJS  : v10.16.0 (/usr/local/bin/node)
   npm     : 6.9.0
   OS      : macOS Mojave
   Xcode   : Xcode 10.2.1 Build version 10E1001

Thanks for the issue! I two questions that will help me figure out what's going on:

How are you setting the relative path?
Can you do rm -rf node_modules and then run npm i to see if things start working again?

Thanks! 🙂

same situation, after rm -rf node_modules and re-run npm i does not work. 404 Error <IP_ADDRESS>/svg/md-menu.svg

I have the same issue. I have an ionic site in a subfolder e.g.: example.com/backend/ of my server. But the production build will try to load the icons from the absolute path /svg/ so from example.com/svg/ and this will fail because all icons are in example.com/backend/svg/. Also in android/ios apps the icons disappear after updating to ionic 4.6.0. This issue may is a duplicate of #18614 ?!

Fixed by https://github.com/ionic-team/ionic/commit/4038e0a60c5faa89e5723b815ad7b4e0a5883bce

Issue persists for me. Created a tabs starter project and made a production build, icons not showing and no errors in console.


Upgrade Python RLP encoding library to v1

Upgrade the RLP encoding library to the latest version, so that we can continue with other upgrades and switching into plasma-framework.
The code must have changed a little, as the API of the lib has changed.
Refers to  #28
I took a little different approach and applied some of the comments that appeared there in a CR.

curious, this becomes mandatory because we are using new python stack?

The new stack deprecates py-ethereum and several others libs and as a result we have to upgrade RLP


Usage in HTML?

Thank you for providing the plugin, but to me it is still not clear how to use a gradient in the HTML code. Could you please provide some examples in the docu? Thank you!
EDIT:
It would also be great, if you could provide examples for how to define more then one "linearGradients".
The example use 2 "colors" keys, one for the definition of colors (what, if those are in "extend"?) and another one in the "linearGradients" definition. It is confusing, when later on the cSS examples mentions the "colors" key in brackets: which one is meant?
I have this put together and it does not work:
    extend: {
      colors: {
        'pink': {
          300: '#4F031C',
          400: '#630D29',
        }
      },
      gradientDarkColors: {
        'pink300': '#4F031C',
        'pink400': '#630D29'
      },
    },
    linearGradients: theme => ({
      colors: theme('gradientDarkColors'),
    }),

// Usage in html:
class="bg-gradient-b-colors"

What works is this:
// Usage in html:
class="bg-gradient-b-pink300"

But that does not allow to use a second pre-defined color, instead the first color is taken from - I have no idea where... (I think it is ransparent)

You need to use and array of colors as shown in the README.md:
linearGradients: {
  directions: { // defaults to these values
    't': 'to top',
    'r': 'to right',
    'b': 'to bottom',
    'l': 'to left',
  },
  colors: { // defaults to {}
    'red': '#f00',
    'red-blue': ['#f00', '#00f'],
    'red-green-blue': ['#f00', '#0f0', '#00f'],
    'black-white-with-stops': ['#000', '#000 45%', '#fff 55%', '#fff'],
  },
},

/* configurable with the "linearGradients" theme object */
.bg-gradient-[direction-key]-[color-key] {
  background-image: linear-gradient([direction-value], [color-value-1], [color-value-2], [...]);
}

What the things in brackets refer to are the directions and colors object keys. In this case [direction-key] would be one of ['t', 'r', 'b', 'l'] and [color-key] one of ['red', 'red-blue', 'red-green-blue', 'black-white-with-stops'].
You need to use it like you mentioned: bg-gradient-b-pink300

I got it after a lot of trying. But to be honest: the documentation could do better - no offense!
1: when starting reading the docu and just wanting to try out the linear gradient, there is no mentioning of the need of array notation.
2: what happens, when there is no array, but only one color? The docu says nothing.
3: The usage in an HTML example should be present.
4: using "colors" twice for two different keys is nothing else but confusing in the beginning.
If you agree, I'd be happy to provide a PR.
Thanks for getting back to me!

@rowild Definitely agree with you there. I want to improve the documentation of all my plugins in the near future, and this one is one of the hardest ones because there are so many options and different ways to do things.

what happens, when there is no array, but only one color? The docu says nothing.

Like you guessed in your first post, it creates a gradient from transparent to that color (or, in the case of radial or conic gradients, from that color to transparent).

using "colors" twice for two different keys is nothing else but confusing in the beginning.

The first colors key is Tailwind's colors which I assumed most people would already customize, so the "Simple" example is supposed to show the minimal amount of configuration necessary to create gradients from your existing theme colors. But we should definitely say that in words rather than just spouting code samples haha.

If you agree, I'd be happy to provide a PR.

That would be very generous of you! Thank you for offering it.

Great! Thank you! I'll provide a PR soon. Let me just finish a project...

Thanks to the original creator and everyone on this thread. I am trying to get this to work as well and it is a bit outside of my skillset because I can't get it to do what it is supposed to. Patiently waiting for some updated docs to follow along :)

Sorry that I didn't provide anything yet. Maybe I can help you now and here. How about you post your code and I have a look at it?


how can i set query_by

Description

Steps to reproduce

Expected Behavior

Actual Behavior

Metadata
Typsense Version:
OS:

You can set query_by in additionalSearchParameters like this: https://github.com/typesense/typesense-instantsearch-adapter#with-instantsearchjs


Added API 2.0 Files Routes

@RackHD/corecommitters @abildw @zyoung51
Contributions made by Billy Abildgaard, Brian Parry, Anitha Srinivasan, Dale Bremner

*** BUILD #1004 ***

test this please


CreateFromCVS for Exploration/QuickReports

Running CreateFromCVS returns error - "the given key was not present in the dictionary".   The JSON making up the CVS is formatted in  {"MDX":"SELECT ...."} and is a string.  Does the JSON need to be encoded?  I have tried running different CVS JSON strings from different cubes - some using a Meta object, but they each return the same error.  Note that I am able to run other PAX API commands without issue.  I am running on <IP_ADDRESS>.

can you provide a slightly more complete/representative sample of the common view spec you're trying to create from?

I have tried the CVS with various alterations including the Meta object - with Meta as null or {} and also with Meta objects Aliases, ExpandAboves, ContextSets as {} or null.  Perhaps you could advise what is expected.  I had wondered if this required encoding?

it should be a string value of valid json, who's MDX string is valid mdx, and meta is a valid json object (if it exists).
it's possible to use the schema on the site https://ibm.github.io/paxapi/#common-view-specification-schema to validate the structural content of the CVS string value with regards to json notation (it won't validate the mdx, of course).


Consider inserting exceptions before remarks in triple slash

As suggested by @eiriktsarpalis . Remarks are the least important items.

Also typeparams must go before params, to be consistent with dotnet-api-docs xmls.


Fix flow::any constructor bug

:+1:  Straight :ship:  Can you also delete this for me?
https://github.com/taskworld/flowcpp/blob/master/main.cpp#L76

I no longer encounter this bug in the master branch. Do you remember what causes this?

It's happened in tw-chat. When we create an action that has meta and payload of flow::any type without constructor.

Argh, it doesn't make sense to me at all. It works just fine in this repo.  Let's find out the actual root cause of this.


PR/commits full of formatting changes - hard to parse the actual code change - codebase not formatted as .clang-format

Branch/Tag/Commit
main
Docker Image Version
n/a
GPU name
n/a
CUDA Driver
n/a
Reproduced Steps
For example, this commit https://github.com/NVIDIA/FasterTransformer/commit/b41451e6225b0a80bb9a6924660b1485407fe7ad consists of many line changes that are purely reformatting(e.g. src/fastertransformer/kernels/add_residual_kernels.cu). It takes much longer than necessary to read and understand changes in the commit.
After some investigation, I also found that running formatting according to .clang-format produces updates on files. For example, https://github.com/NVIDIA/FasterTransformer/blob/b41451e6225b0a80bb9a6924660b1485407fe7ad/3rdparty/INIReader.h#L26 will become typedef int (*ini_handler)(void* user, const char* section, const char* name, const char* value); with no line breaks. This seems to show that the repo was not formatted before every commit to main.
In the future, the formatting changes in commits can be avoided by running the repo through a consistent formatter before every commit. Are there any ways we can quickly fix this and narrow down the code changes in the commits as a short-term solution?

Thank you for the suggestion. Sometime, we will update the clang file and then need to update format of many codes. We will prevent ignoring updating some files in the future.
I don't have solution for short-term.


Update bugfix about the settings issues (weird behavior with booleans)

I changed the Painter API to ensure that the returned value of alg.settings.value() returned a value of the same type as the defaultValue. so now when you call alg.settings.value(foo, false) the returned value will be a Boolean and alg.settings.value(foo, "false") will be a String


Nothing about using AIP Scanner

I would expect this document to mention AIP Scanner as a tool to learn about sensitive information types in on-premises data stores. Is there a reason that it is not mentioned?
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 63b6844d-dbb1-e9b8-8ce5-35090ce1d89e
Version Independent ID: 5bbe339f-be21-49d3-6c0b-0c3394aeda20
Content: Assess data privacy risks and identify sensitive items with Microsoft 365
Content Source: microsoft-365/solutions/information-protection-deploy-assess.md
Product: microsoft-365-enterprise
GitHub Login: @BrendaCarter
Microsoft Alias: bcarter

@DeanGross Thank you for your feedback. I have added a note to the document with a reference link to Find what sensitive information you have in files stored on-premises.
This can be tracked via PR#https://github.com/MicrosoftDocs/microsoft-365-docs/pull/3565
Thanks
Sri

@msbemba Thank you very much for the contribution and updating the documentation with PR. @DeanGross Hope this update is helpful for you. Thanks for taking out some time to open the issue. Appreciate and encourage you to do the same in future also.

@msbemba Thank you very much for the contribution and updating the documentation with PR. @DeanGross Hope this update is helpful for you. Thanks for taking out some time to open the issue. Appreciate and encourage you to do the same in future also.


Why did you use VGG16 instead of Resnet?

Hi, I found that the model just overfits in just some epochs, is this because the backbone is VGG instead of resnet?

you can change the backbone

and how to change the backbone.

@Zhang-O @hcnhatnam It's ok to change to resnet50 by two lines, but it seems no improvement.
vgg16 = ResNet50(input_tensor=self.input_img, weights='imagenet', include_top=False)
self.f = [vgg16.get_layer('activation_49').output, vgg16.get_layer('activation_40').output, vgg16.get_layer('activation_22').output, vgg16.get_layer('activation_10').output]

3ks,could you add me to qq friends? my account is 691259192

I am new to advanced East .i think I will have lots questions when study east and advanced east

????

I have flowed you

@Zhang-O @hcnhatnam It's ok to change to resnet50 by two lines, but it seems no improvement.
vgg16 = ResNet50(input_tensor=self.input_img, weights='imagenet', include_top=False)
self.f = [vgg16.get_layer('activation_49').output, vgg16.get_layer('activation_40').output, vgg16.get_layer('activation_22').output, vgg16.get_layer('activation_10').output]

@scut-salmon HELLO i changed resnet50 based your method， it occurs out  dimension error


pod2man not found during builds

build output says that pod2man is not found, even when perl package is installed
looks like the build users PATH is missing /usr/bin/site_perl:/usr/bin/vendor_perl:/usr/bin/core_perl

looks like the build users PATH is missing /usr/bin/site_perl:/usr/bin/vendor_perl:/usr/bin/core_perl

There's no reason why these directories would be in $PATH unless you add them explicitly.

I worked around with setting PATH via docker run


feat: added WonderCMS login route

feat: added WonderCMS login route

@BRAVO68WEB This Pull Request has now been merged in Seclists-Express!
Seclists-Express is a frequently-updated fork of Seclists.

Source: https://github.com/WonderCMS/wondercms/blob/main/index.php

Thanks for the suggestion @BRAVO68WEB !


CMSPlugin position vs MPTT order vs Treebeard order

I'm having trouble wrapping my head around CMSPlugin.position vs MPTT order vs Treebeard order.
I have a site originally developed under 3.0 and then migrated to 3.1 (I ran the mptt fix tree manage command before migrating).
When I run fix-tree under 3.1, CMSPlugin.position is updated by CMSPlugin.fix_tree to match the order as given by the treebeard path and ends up being wrong. What is the intended behavior in 3.0, should position always match the MPTT ordering? How is it kept in sync?
Searching through the code base CMSPlugin.position seems to be mostly used for ordering the plugins while rendering?
I have a quite a few pages that have this issue. It is possible that the discrepancy between MPTT ordering and position came from exceptions during editing of the pages (due to other plugins/apps), or maybe there's an actual bug here. The MPTT -> Treebeard migration does not seem to do anything with the position.

@julienp In 3.1 it's less used than it was in mptt, but it's still needed in some part of the code.
I expect it to be phased out at some point if we can efficiently use the treebeard information to substitute it
The above PR should anyway make it consistent with path and depth values set by treebeard


Doc - Update OVA links in doc

Signed-off-by: kcoriordan<EMAIL_ADDRESS>What this PR does / why we need it
Updated OVA links and graphics for v0.10.0
Note: I need to replace the graphics in Create vSphere Clusters topic, step 7, 8, 9. Can someone who has a vSphere client and 010.0 OVA downloaded pls sent to me?
thanks!
Details for the Release Notes (PLEASE PROVIDE)

Which issue(s) this PR fixes

Fixes: #
Describe testing done for PR
Run hugo server as per instructions in readme
Special notes for your reviewer

Need to replace some screenshots in getting started guide


return the old value in map.put, not the new one

I didn't want to interfere with the release process, so I didn't push this. But it's a critical fix.
I think we should also look for other changes where the result of put() was used before, but is now []=, but it's too late for me to do that.

Well, CorrespondenceMutator.put is defined as void, but []= is defined as returning the new value (RHS). If MapMutator.put is defined as returning the old value, this is confusing at best.


test.py error tests should support context messages from the CFE

(Parent issue #44897)
As of a42244f73b27256eca44def4daa552e91c2dbc55, I've begun implementing "why not promoted" functionality in the CFE.  For example, this code:
f(int? i, int? j) {
  if (i == null) return;
  i = j;
  i.isEven;
}
main() {
  f(null, null);
}

leads to the following output:
../../tmp/test.dart:4:5: Error: Property 'isEven' cannot be accessed on 'int?' because it is potentially null.
Try accessing using ?. instead.
  i.isEven;
    ^^^^^^
../../tmp/test.dart:3:3: Context: Variable 'i' could be null due to a write occurring here.
Try null checking the variable after the write.
  i = j;
  ^

I tried to write a language test to validate this functionality (see https://dart-review.googlesource.com/c/sdk/+/182901) but test.py currently only supports testing the main error message; it ignores the "Context:" messages entirely.  We need a way to test the context messages as well.
(Eventually we'll want to extend these tests to support analyzer as well, but some analyzer work needs to be done first, to get the context messages exposed in a machine readable way, so it makes sense to start with CFE support).

@munificent any progress on this?

I made some progress today. I'm trying to figure out:

Whether we should track context for all static error tests or just some that opt in. I think if we want to add context for all tests, there are about 100 that would need updating. I don't mind updating them, but I don't know if it makes the tests noisier than we want.
How we want context expectations to look in tests. The simplest solution is to have them just appear like separate errors. I have this working locally:

class C {
  int? x;
  //   ^
  // [cfe] Context: 'x' refers to a property so it couldn't be promoted.

  f() {
    if (x == null) return;
    x.isEven;
//  ^
// [analyzer] COMPILE_TIME_ERROR.UNCHECKED_USE_OF_NULLABLE_VALUE
//    ^
// [cfe] Property 'isEven' cannot be accessed on 'int?' because it is potentially null.
  }
}

Note the // [cfe] Context: 'x' refers... line. This works, but it's not clear which error this context is associated with. If there are multiple static errors in the same test, there's no real way to tell which context is for which error. The nice thing about this format is that if you insert lines or rearrange the test, the context should still be fine. You wouldn't have to manually update explicit line numbers or anything.
Another option is something more like:
class C {
  int? x;
  //   ^
  // [cfe] Context: 'x' refers to a property so it couldn't be promoted.

  f() {
    if (x == null) return;
    x.isEven;
//  ^
// [analyzer] COMPILE_TIME_ERROR.UNCHECKED_USE_OF_NULLABLE_VALUE
//    ^
// [cfe] Property 'isEven' cannot be accessed on 'int?' because it is potentially null.
// [cfe context line 2, column 8] 'x' refers to a property so it couldn't be promoted.
  }
}

I think that's a little clearer, but it means changes to the test will change those line numbers. Of course, the test updater do this for you.
@stereotype441 and @johnniwinther (and anyone else who cares about CFE static error tests), any thoughts or preferences?

I prefer the format that doesn't have embedded line/column numbers for maintainability reasons, but I'm a little worried that it will get us into trouble by making the test ambiguous if there's multiple errors.  How about an approach where we have numbered identifiers to point to the locations?  Something like this:
class C {
  int? x;
  //   ^
  // [cfe @1]

  f() {
    if (x == null) return;
    x.isEven;
//  ^
// [analyzer] COMPILE_TIME_ERROR.UNCHECKED_USE_OF_NULLABLE_VALUE
//    ^
// [cfe] Property 'isEven' cannot be accessed on 'int?' because it is potentially null.
// [cfe context @1] 'x' refers to a property so it couldn't be promoted.
  }
}

That way the @1 serves to tie together the two locations.  It wouldn't interfere too badly with automatically updating test expectations, because the updater script could just number consecutively starting at 1.

I like that. I was idly considering something similar, so our convergent evolution here is a signal that it's a good idea. Let me see how hard that is to implement and I'll go from there.

Fixed by: https://dart-review.googlesource.com/c/sdk/+/193281


Add power shell example

- What I did
The example command doesn't work on Windows, so added Powershell example
- How to verify it
Build without context on Windows system.

Please sign your commits following these rules:
https://github.com/docker/docker/blob/master/CONTRIBUTING.md#sign-your-work
The easiest way to do this is to amend the last commit:
$ git clone -b "add-power-shell-example" git@github.com:friism/docker-1.git somewhere
$ cd somewhere
$ git rebase -i HEAD~2
editor opens
change each 'pick' to 'edit'
save the file and quit
$ git commit --amend -s --no-edit
$ git rebase --continue # and repeat the amend for each commit
$ git push -f

Ammending updates the existing PR. You DO NOT need to open a new one.

@friism can you squash your commits?
otherwise, LGTM

LGTM after commits are squashed

thx, rebased

thanks!


A11y: Price disclaimers are purely visual

Every price in the product detail page is followed by a star (to indicate pricing includes Vat + shipping). We need to better associate the star with the relevant content because if you’re using VoiceOver, that star is never repeated anywhere. So you have to guess what it means/is referring to.
Product listing components also have one.
{panel:bgColor=#deebff}
Also affects ByteClub/CMS Extensions/Shopping Experiences
{panel}

[public] Shopware automated response: This issue is linked to the internal issue: NEXT-39112
[created from NEXT-39112, comment 505479]

[public]

Status Change: Open

This issue is ready for implementation.
[created from NEXT-39112, comment 510207]


Azure Developer CLI Post

@puicchan PTAL - the post is largely finished with the exception of pipeline config (waiting until the fix goes in for the release tomorrow).
@austinauth FYI - for the graphic

@puicchan @jongio @austinauth @rajeshkamal5050 @nitya This is now ready for review. Please take a look folks!

One typo else LGTM.


proposal: make []byte comparable (more accurately, reflect its inherent comparability)

What version of Go are you using (go version)?

$ go version
1.14.1

Does this issue reproduce with the latest release?
Yes.
What operating system and processor architecture are you using (go env)?
I don't think this is relevant.
What did you do?
I tried to use byte slices in a context where they might be compared (most notably, as fields in a struct which is a map key).
What did you expect to see?
Considering https://github.com/golang/go/issues/31587, byte slices are as comparable as strings are and the comparison does not allocate. Therefore, I would expect them to be comparable like strings and acceptable as members of a struct used as a map key.
What did you see instead?
Byte slices are not comparable while strings are.

Using bytes.Equal instead of == for comparing byte slices is merely a syntactic nuisance.
So is using byte slices as keys in a map via string(b).
However the current behavior means that it is not possible to use a struct containing byte slices as a map key whereas it is possible to use a struct containing strings as a map key. This leads to hacks converting one type to another or using less intuitive solutions altogether which provide no benefit over []byte being comparable as-is.

It doesn't seem to me that changing this would break backwards compatibility/any code out there as currently it is not possible to use a []byte in a comparable type context at all.
Also, the invalid map key type fnord error message could be more helpful.

The problem with comparable byte slices, especially for use as map keys, is that they are modifiable. What happens if you modify the slice after insertion?
m := map[[]byte]int{}
b := []byte{1,2,3}
m[b] = 7
b[1] = 8
println(m[b])
println(m[[]byte{1,2,3}])
println(m[[]byte{1,8,3}])

What do those printlns print?
We'd have to make a copy of the backing store to make this work, I think. Then that would be different from all the other reference types that can be used as keys.

Pointers used as map keys are modifiable in the same fashion. Consider this playground example.

But maps with pointers as keys use pointer equality, not contents-of-the-thing-pointed-to equality.
But it sounds like that's not what you want for slices.
Arrays are modifiable but are values, so you implicitly make a copy on insertion into a map (same with any value type, really).

You are right. Why not treat byte slices the same as arrays then? Slice pretends to be a value type in some ways while being a reference type. Here I think it would be warranted to treat it as a value type.

It seems to me that it would still be ripe for confusion.
Do we compare the values between len and cap?
b := []byte{1,2,3,4}[:3]
c := []byte{1,2,3,5}[:3]
if b == c { ... }

I could see arguments for either decision.
Does assignment make a copy?
b := []byte{1,2,3}
c := b
b[1] = 5
if c[1] == 5 { ... should reach here ... }

It never used to, but now, sometimes, it does.
Why do map keys make a copy but map values don't?
m := map[[]byte][]byte{}
k := []byte{1,2,3}
v := []byte{4,5,6}
m[k] = v
k[1] = 9
v[1] = 9
if _, ok := m[k]; !ok { ... should reach here, as map doesn't have 1,9,3 as a key ... }
if m[[]byte{1,2,3}][1] == 9 { ... should reach here, as map does have 4,9,6 as a value ... }

We certainly don't want to copy the backing store of the slice for map values. Too much code depends on the reference semantics. For example, m[k] = append(m[k], 7).

Valid concerns, thank you.
Just to clarify, I am not suggesting to necessarily change []byte's default behavior, but as it is right now, there is also no explicit way to have e. g. []byte-containing structs as keys without writing ugly code. It simply can't be done cleanly although it's technically possible (even without having to allocate extra).
The simplest solution I can think of is creating a struct type identical in structure to the []byte-containing one but with string fields instead and converting to it before assigning it as a map key. That's suboptimal. And for my use case (which is using a map as a set for <O(n) lookup) it's going to look terrible.
Another way is to serialize the struct via e. g. JSON which I am currently using but that has its own drawbacks (performance, runtime use of reflection etc).
Do you think this proposal as such has merit independent of its concrete implementation?
Might this be considered in the scope of a generics mechanism for a future Go version?
Or perhaps (if that ever makes it to Go) in the scope of an immutable type/variable mechanism?

Just to clarify, I am not suggesting to necessarily change []byte's default behavior, but as it is right now, there is also no explicit way to have e. g. []byte-containing structs as keys without writing ugly code. It simply can't be done cleanly although it's technically possible (even without having to allocate extra).

I agree that this would be a nice problem to solve. I'm just skeptical that this proposal is the right solution. I think it creates more issues than it solves.

Do you think this proposal as such has merit independent of its concrete implementation?

Any proposal needs to at least argue that a concrete implementation is possible. I don't think it would need details, however.

Might this be considered in the scope of a generics mechanism for a future Go version?

I don't really know how generics would figure into this. It's certainly ok to assume you have generics and design from there. It would just have to wait until generics happen before it gets implemented.

Or perhaps (if that ever makes it to Go) in the scope of an immutable type/variable mechanism?

Same. I would imagine immutable byte slices would behave much like strings. But it's hard to be sure, we don't have a immutable proposal that is likely to be accepted at the moment.

There isn't anything particularly special about []byte, the same arguments apply to slices of any comparable type.  See #23725.
Historically we've never implemented slice equality because there are two logical choices for equality: element-by-element comparison and identical-backing-array comparison.  Different programs would prefer different choices, and neither is clearly correct.  In the presence of this ambiguity, the language declines to make a choice.
When and if we have generics I'm confident that people will implement hashmap types that provide different tradeoffs, including the opportunity to define your own hash and equality functions, which can then be used to implement the semantics you need.

For language change proposals, please fill out the template at https://go.googlesource.com/proposal/+/refs/heads/master/go2-language-changes.md .
When you are done, please reply to the issue with @gopherbot please remove label WaitingForInfo.
Thanks!


Double date separators appearing in DatePicker, preventing date selection

Originally mentioned in https://github.com/flutter/flutter/issues/55535 by @whoch in this comment.
The issue might be related to incorrect date separators for particular locales: https://github.com/flutter/flutter/issues/63372
This issue occurs because the dateHelpText, dateSeparator in MaterialLocalization are different from the compactDateFormat used by the validator in TextFormField.
In Korea, helpText and separator of MaterialLocalizationKo are as follows:
String get dateHelpText => 'yyyy/mm/dd';
String get dateSeparator => '/';

And compactDateFormat is y. M. d.
InputText is initially shown in y. M. d. format, but when the value is modified, it is changed to y//M//d// by inputFormatters. And Only '/' is entered, therefore cannot be entered y. M. d. format.
HintText also outputs 'yyyy/mm/dd' which is different from the compactDateFormat.
Even if input the hintText format,  the errorText is displayed because the _validateDate method, validator of InputDatePickerFormField, internally parse the compateDate.
String _validateDate(String text) {
  final DateTime date = _parseDate(text);
  if (date == null) {
    return widget.errorFormatText ?? MaterialLocalizations.of(context).invalidDateFormatLabel;
  } else if (!_isValidAcceptableDate(date)) {
    return widget.errorInvalidText ?? MaterialLocalizations.of(context).dateOutOfRangeLabel;
  }
  return null;
}

DateTime _parseDate(String text) {
 final MaterialLocalizations localizations = MaterialLocalizations.of(context);
 return localizations.parseCompactDate(text);
}

Can I modify compactDateFormat or can someone solve this issue?

CC @darrenaustin

Yikes. So all of this is stemming from the date picker trying to keep the user from typing invalid dates. In order to do that it uses a date text formatter that rejects anything but digits and the date separator. This is based on an apparently faulty assumption that there is a single character as the separator for all locales. Perhaps a better solution would be remove the text formatter altogether and let the user type whatever they want and let the validator handle the errors.
We would still need to get the help text correctly translated (as per #63372), but we could get out of the separator business altogether.
I will put together a PR that removes the formatter and see what that looks like.


New Twig Extension: Thumbnail

Thumbnail twig extension purpose is to be the equivalent of the glorious sfThumbnailPlugin for symfony1.x.
I think an extension like this could be very useful and should be available to everybody, to provide Symfony developers with a smart tool to handle thumbnail generation in an easy way.
Thanks, Emanuele Gaspari.

Btw, both AvalancheImagineBundle and LiipImagineBundle provide such features

Hi, I have to admit I didn't find those two bundles, in that case I would have used them.
The only conceptual difference between them and my proposed extension is that they are usable only in Symfony and the extension would be part of twig. The current functionalities of this extension can not compete with the bundles ones, so I don't know if proposing the extension does make any sense anymore. what do you think?
off topic: great work with StofDoctrineExtensionBundle!

btw, you don't respect the coding standards at all in your extension:

the code should use 4 spaces per level for the indentation, not 2 spaces or tabs
variable names should be camel-cased
curly braces should be on the same line for control structures (if, elseif, while, try...)
the visibility should be specified explicitly
you should always use the curly braces for if statements even when there is only one line
you should use elseif instead of else if

And the following code is totally useless:
<?php
try {
    // some code here
} catch (Exception $e) {
    throw $e;
}

I agree with @stof. Imagine is a great library and there is no need to duplicate the effort. What we could add is an apply_filter like in the Symfony2 bundle.

ok, sorry for wasting time with proposing non standard code, thanks!


Bad links to DateFormat docs in README.md

There are at least two links to the documentation for DateFormat that are broken in README.md. The bad links point to:
https://api.dartlang.org/apidocs/channels/stable/dartdoc-viewer/intl/intl.DateFormat
I don't know if the problem is with the README.md or api.dartlang.org.

Fixed in c2b7d3d9c51c0c141ffe2f257c53eae9d21984f9


ARROW-12508: [R] expect_as_vector implementation causes test failure on R <= 3.3 Remove ifelse as causes failure on R <3.4

@github-actions crossbow submit test-r-versions


Docker installation (with Python3 support)

I'm working on an automated setup, and for the whitelist to work properly on Pi-hole on Docker, I need an entrypoint script. Since a script is needed, I'm working on installing python, checking if the repo was already cloned, if not, cloning it, and if so, pulling it, then proceeding to invoke the whitelist.py and add it to crontab. But the script I managed to reach is facing a fatal error:
fatal: destination path 'whitelist' already exists and is not an empty directory.
My init.sh as entrypoint:
apt install python3 -y
cd

# The name of the directory to check/create
dir_name="whitelist"

# The Git repository URL to clone/pull from
repo_url="https://github.com/anudeepND/whitelist.git"

# Check if the directory already exists
if [ -d "$dir_name" ]; then
  echo "Directory '$dir_name' already exists. Doing a 'git pull'..."
  cd "$dir_name"
  git pull
else
  echo "Directory '$dir_name' does not exist. Doing a 'git clone'..."
  git clone "$repo_url" "$dir_name"
fi

python3 whitelist/scripts/whitelist.py

cat /etc/crontab >> tmp_crontab
echo "0 1 * * */7     root    /root/whitelist/scripts/whitelist.py" >> tmp_crontab

cp tmp_crontab /etc/crontab
rm tmp_crontab

I'm willing to send a PR with the working instructions once I get it working properly.

The cd after installing python3, cd to where? I'm not sure how you plan on using this. Will you have this init.sh on the machine that runs docker and then add it to crontab?


strange issue with map on andriod

Hey, a wrote a app that uses react-native-maps and it works perfectly on iOS.
I wanted to run it on Android, did steps from installation guide (https://github.com/airbnb/react-native-maps/blob/master/docs/installation.md#android).
When I open my app, I get blank page with markers (can't scroll, zoom, press on markers etc.)

But, when I hide the app and then make it active again, tiles are loaded (sometimes with names of the places and sometimes not 🤔)

Unfortunately I still can't interact with map.
I suppose the API key is working correctly, there is some traffic

For comparison, screenshot from iOS version

Version I use:
"react-native-maps": "^0.13.0",
"react-native": "0.43.2",

And this is my Map component:
import React, {PropTypes} from 'react';
import {
  Text,
  View,
  TouchableOpacity
} from 'react-native';
import styles from './Map.style';
import * as Shapes from '../../Utils/Shapes';
import {
  LATITUDE_DELTA,
  LONGITUDE_DELTA
} from '../../Utils/Constants'
import dismissKeyboard from 'dismissKeyboard';
import MapView from 'react-native-maps';

const Map = (props) => {
  const createDescription = (lunch) => {
    return lunch.reduce((accumulator, currentValue, currentIndex) => {
      return currentIndex === 0 ? `${currentValue.price}zł, ${currentValue.desc}` :
      `${accumulator}\n${currentValue.price}zł, ${currentValue.desc}`
    }, '');
  };

  const renderMarkers = () => {
    return (
      props.data.map((marker, index) =>
        <MapView.Marker
          coordinate={marker.coordinate}
          key={index}
        >
          {props.showCallout &&
            <MapView.Callout style={styles.callout}>
              <TouchableOpacity
                onPress={() => {
                  props.handleCalloutPress(marker);
                }}
              >
              <View>
                <Text style={styles.calloutTitle}>
                  {marker.name}
                </Text>
                <Text
                  ellipsizeMode='tail'
                  numberOfLines={5}
                >
                {createDescription(marker.lunch)}
                </Text>
              </View>
              </TouchableOpacity>
            </MapView.Callout>
          }
        </MapView.Marker>
      )
    );
  }

  return (
    <View style={styles.container}>
      <MapView
        loadingEnabled={props.loadingEnabled}
        rotateEnabled={props.rotateEnabled}
        pitchEnabled={props.pitchEnabled}
        scrollEnabled={props.scrollEnabled}
        zoomEnabled={props.zoomEnabled}
        onPress={() => {
          dismissKeyboard();
          props.handlePress();
        }}
        style={styles.map}
        showsUserLocation={true}
        initialRegion={{
          ...props.region,
          latitudeDelta: LATITUDE_DELTA,
          longitudeDelta: LONGITUDE_DELTA
        }}
      >
        {renderMarkers()}
      </MapView>
    </View>
  );
};

Map.propTypes = {
  data: PropTypes.arrayOf(PropTypes.shape({
    name: PropTypes.string,
    coordinate: Shapes.coordinate.isRequired,
    lunch: Shapes.lunch
  })),
  region: Shapes.coordinate.isRequired,
  handleCalloutPress: PropTypes.func,
  handlePress: PropTypes.func,
  showCallout: PropTypes.bool,
  loadingEnabled: PropTypes.bool,
  rotateEnabled: PropTypes.bool,
  pitchEnabled: PropTypes.bool,
  scrollEnabled: PropTypes.bool,
  zoomEnabled: PropTypes.bool
};

Map.defaultProps = {
  handleCalloutPress: () => {},
  handlePress: () => {},
  loadingEnabled: true,
  rotateEnabled: true,
  pitchEnabled: true,
  scrollEnabled: true,
  zoomEnabled: true
}

export default Map;

No clue what can be problem here, it works on iOS like a charm.
Edit:
the same happens with version
"react-native-maps": "^0.15.2",

I've also tried to run this example with my configuration and here is result https://youtu.be/YSAke3T6fvo
💥

I have been having the exact same issue. I ended up reverting back to 0.15.0 and it works fine. Both 0.15.1 and 0.15.2 have this same issue.

Thanks @BobaFaux!
I can confirm, it works with 0.15.0 🎉
Is this known issue?

+1 This occured for me too, on RN 0.45.1 and RNM versions 0.15.3, 0.15.2....downgrading to 0.15.1 worked for me. Same behaviour as the images above, on a clean install.
If you're trying to fix this, setting an explicit dependency on 0.15.2 in package.json like so will do the trick: "react-native-maps": "0.15.2" and then npm install or yarn install.
Error logged repeatedly in emulator console:
E/GLConsumer: [SurfaceTexture-0-14704-0] syncForReleaseLocked: error dup'ing native fence fd: 0x3000

I have same problem in 0.15.3 version.
Error:
[SurfaceTexture-0-5888-0] syncForReleaseLocked: error dup'ing native fence fd: 0x3000

After a bit of bashing about, I've found this is caused by using an outdated GoogleMaps pod. I was using GoogleMaps 2.1.0. Running pod update in the ios folder instead of pod install does the trick. At the time of writing, the current version of GoogleMaps is 2.4.1.

After a lot of bashing about, I found that removing google play compilation from the grade dependencies fixed this.
In app/build.gradle:
dependencies {
    ...
     compile "com.airbnb.android:react-native-maps:+"
}

Having the same issue right here, using rnm 0.16.2 and rn 0.48.3

Same issue on rn 0.47.2 and rnm 0.16.4

I resolved this by doing this:
https://github.com/airbnb/react-native-maps/issues/1043

I encountered this exact issue with with RN 0.49.3 and RNMaps 0.17.1.
To add further info i saw a lot of this error in logcat whenever the map view was onscreen or i tried to interact with it while it was grey and after minimizing and pulling it back up (when it would show the map):
11-04 12:15:36.081  5754  5794 E GLConsumer: [SurfaceTexture-0-5754-2] syncForReleaseLocked: error dup'ing native fence fd: 0x3000

'Fixed' it by reverting to 0.15.0, i had to modify 0.15.0 however as it had incompatibilities with the latest RN version due to breaking changes introduced (Proptypes and one @override).
I tried all the different options mentioned above but only reverting worked. Here's my dependencies for google play base and maps
    compile(project(':react-native-maps')){
        exclude group: 'com.google.android.gms', module: 'play-services-base'
        exclude group: 'com.google.android.gms', module: 'play-services-maps'
    }
    compile 'com.google.android.gms:play-services-maps:11.4.2'
    compile "com.google.android.gms:play-services-base:11.4.2"

Would be great to use the latest version of RNMaps tho, anyone have any ideas on how to get it working?

This happens when your google maps API key is invalid.
On 5 Nov 2017 3:06 pm, "rtman"<EMAIL_ADDRESS>wrote:
I encountered this exact issue with with RN 0.49.3 and RNMaps 0.17.1.
To add further info i saw a lot of this error in logcat whenever the map
view was onscreen or i tried to interact with it while it was grey and
after minimizing and pulling it back up (when it would show the map):
11-04 12:15:36.081  5754  5794 E GLConsumer: [SurfaceTexture-0-5754-2]
syncForReleaseLocked: error dup'ing native fence fd: 0x3000
'Fixed' it by reverting to 0.15.0, i had to modify 0.15.0 however as it had
incompatibilities with the latest RN version due to breaking changes
introduced (Proptypes and one @override https://github.com/override).
I tried all the different options mentioned above but only reverting
worked. Here's my dependencies for google play base and maps
compile(project(':react-native-maps')){
    exclude group: 'com.google.android.gms', module: 'play-services-base'
    exclude group: 'com.google.android.gms', module: 'play-services-maps'
}
compile 'com.google.android.gms:play-services-maps:11.4.2'
compile "com.google.android.gms:play-services-base:11.4.2"

Would be great to use the latest version of RNMaps tho, anyone have any
ideas on how to get it working?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/airbnb/react-native-maps/issues/1399#issuecomment-341947678,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACll3_CtxdGIrmMO60kUzrsv6tPEUW_Lks5szTQ1gaJpZM4N2FDx
.

@heysailor
I'm fairly certain that is not the case since I could see my interactions with the Maps API in the dashboard while this issue was happening. So the key was functioning and I was communicating and receiving data from the server. Also i didn't change my API key at all when trouble shooting this, just react-native-maps version to 0.15.0 and it started working properly.

Apologies, I was on mobile and didn't check through the prior posts. Did
you try the Google Play services one-liner as I posted before?
Cheers
On 6 Nov 2017 12:08 pm, "rtman"<EMAIL_ADDRESS>wrote:

@heysailor https://github.com/heysailor
I'm fairly certain that is not the case since I could see my interactions
with the Maps API in the dashboard while this issue was happening. So the
key was functioning and I was communicating and receiving data from the
server. Also i didn't change my API key at all when trouble shooting this,
just react-native-maps version to 0.15.0 and it started working properly.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/airbnb/react-native-maps/issues/1399#issuecomment-342021857,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACll3wShLlzFIVLn7QcOKDDCUSphUzE8ks5szlwggaJpZM4N2FDx
.

I'm running into this too with the latest version. Has anyone figured out the cause or found a work-around for now? My app is essentially unusable on Android.

Ok, I found the source of the bug. However, I'm not skilled enough in Android to know why this causes the issue or what this means but hopefully some of you can help figure it out.
The issue was introduced in this commit 7bba6f939f425865cf917fc3b65fdf63533dcbd1.
Specifically, this change, when rolled back on version 0.18.3 fixes the issue for me.
Anyone care to elaborate what this does, what the intension behind this change might have been, and why this is causing problems on our use cases?
// lib/android/src/main/java/com/airbnb/android/react/maps/AirMapView.java
-        if (contextHasBug(superContext)) {
+        if (!contextHasBug(appContext.getCurrentActivity())) {
+            superContext = appContext.getCurrentActivity();
+        } else if (contextHasBug(superContext)) {

@aforty I'm confused. What did you do, precisely, to make it work?

@carlove60
I changed this
       if (!contextHasBug(appContext.getCurrentActivity())) {
           superContext = appContext.getCurrentActivity();
       } else if (contextHasBug(superContext)) {

to this
        if (contextHasBug(superContext)) {

That commit was supposed to fix #1225, #1161, and #453.

@aforty This also fixes this issue!! Thank you very much for finding this weird ass bug.

@aforty please PR

@christopherdro I'm a little bit confused. What shall we do here?

Came across this with<EMAIL_ADDRESS>and<EMAIL_ADDRESS>Seems like this issue is worse than the ones the offending change was meant to fix (#1225, #1161, and #453).

@aranda-adapptor could you please try installing from git. 0.19.0 on npm doesn't have many fixes (still needs to be pushed).

@rborn I tested the current git master and the issue remains. Applying the change as mentioned by @aforty above does resolve the issue, but I'm not sure why.
As far as I can tell, the issue is that the map is simply not triggering RN to re-render when it should. You can pan the map, click on markers etc and nothing changes, but when you trigger a re-render by changing a different component, the map updates to be where you'd expect it to be.
If anyone wants to test the change and re-test the associated issues, it is here: https://github.com/Adapptor/react-native-maps#fix_1399

Having the same issue here:
Thow im using:
"react-native": "^0.50.4",
"react-native-maps": "^0.20.1",

E/GLConsumer: [SurfaceTexture-0-8734-0] syncForReleaseLocked: error dup'ing native fence fd: 0x3000

Works fine on real device but not in my emulater.

Same issue here
"react-native": "^0.51.0",
"react-native-maps": "0.20.1",

Shows a blank map on both a real device and emulator.
@aforty Solution seems to work, should this merged to master or is there a more long term solution?

Same issue here
"react": "16.3.2",
"react-native": "0.55.3",
"react-native-maps": "^0.21.0",

@aforty Solution still makes it work.

Same issue still...
`"react": "16.3.1",`
`"react-native": "0.55.3",`
`"react-native-maps": "^0.21.0"`

@0angelic0 led me to @aforty 's solution which fixes it for me!
Here's some screenshots for visual aids.
He changed:
/node_modules/react-native-maps/lib/android/src/main/java/com/airbnb/android/react/maps/AirMapView.java
Before

to this
After

I've just encountered this issue also.
Changing my emulator from x86_64 to x86 fixed the issue for me.

Ok, I found the source of the bug. However, I'm not skilled enough in Android to know why this causes the issue or what this means but hopefully some of you can help figure it out.
The issue was introduced in this commit 7bba6f9.
Specifically, this change, when rolled back on version 0.18.3 fixes the issue for me.
Anyone care to elaborate what this does, what the intension behind this change might have been, and why this is causing problems on our use cases?
When I undo the change below, contextHasBug(superContext) then returns false and therefore the function then return superContext. That seems to work and makes the map function as intended.
With the code below in place !contextHasBug(appContext.getCurrentActivity()) returns true and superContext is then set to appContext.getCurrentActivity() which seems to render the map unusable.
Thoughts?
// lib/android/src/main/java/com/airbnb/android/react/maps/AirMapView.java
-        if (contextHasBug(superContext)) {
+        if (!contextHasBug(appContext.getCurrentActivity())) {
+            superContext = appContext.getCurrentActivity();
+        } else if (contextHasBug(superContext)) {

this solution work for me
I have the same issue
"react-native": "0.56.0",
"react-native-maps": "^0.21.0",

@pohnean 's solution worked for me. I didn't and I still don't like the solution directly modifying the library from node_modules.
solution for Mac OS Google maps working while Android is showing a blank screen. On mine, the map displayed when I rotated the device simulator, so it was some kind of problem with initial state. Whatever runs when you rotate the screen rrun some code that made the map display.
By default, it was blank like OPs image.

Go to Android Studio
Goto SDK manager
Download Nougat x86 (not x86_64)
Make a new virtual device with that new image
Run it
react-native run-android
Success?

NOTE: Notice that I said x86 and not x8_64. The issue probably has something to do with graphics rendering logic differences between 32bit and 64bit architecture.
Try @pohnean 's solution before you modify anything in the node_modules.  pohnean's solution is Occam's razer.