Speed up sync XHR result parsing

I figured that rather than using JSON.parse()'s reviver function, it might be more efficient to let JSON.parse() do its thing and modify the resulting object afterwards.
This seems to cut the time spent parsing the result from the other process from an average of 650ms to 60ms. It should help with https://github.com/tmpvar/jsdom/issues/1833, and might allow us to enable some timeout-tests :-)

9 => 7 minute travis runs is 👌

Turns out that a JSON.parse()-reviver was used in xhr-sync-worker.js as well. Replacing it seems to have improved performance further.

Wow. Another ~2 mins shaved off. This change is amazing. Can you get us another 2 minutes? 😀


add interface of sendTransactionWithStringParamsAndGetResponse

Codecov Report

Merging #73 into dev will decrease coverage by 0.00%.
The diff coverage is 25.00%.

@@             Coverage Diff              @@
##                dev      #73      +/-   ##
============================================
- Coverage     15.45%   15.45%   -0.01%
  Complexity      790      790
============================================
  Files           437      437
  Lines         15089    15096       +7
  Branches       1556     1556
============================================
+ Hits           2332     2333       +1
- Misses        12495    12501       +6
  Partials        262      262

Impacted Files
Coverage Δ
Complexity Δ

...ransaction/manager/AssembleTransactionManager.java
0.00% <0.00%> (ø)
0.00 <0.00> (ø)

src/main/java/org/fisco/bcos/sdk/abi/ABICodec.java
15.83% <40.00%> (+0.14%)
9.00 <1.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 59c3b49...8af10f3. Read the comment docs.


FIX: Fixed typo.

Typo fix.

Codecov Report

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

@@           Coverage Diff           @@
##           master    #1058   +/-   ##
=======================================
  Coverage   89.55%   89.55%
=======================================
  Files          50       50
  Lines        8370     8370
=======================================
  Hits         7496     7496
  Misses        874      874

Impacted Files
Coverage Δ

bluesky/run_engine.py
96.27% <ø> (ø)
:arrow_up:

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 d474078...d31a06d. Read the comment docs.


Compatibility with typeahead 0.11.x

Looks like the function signature for a dataset source has changed in typeahead.
old:  (query, cb)
new: (query, syncResults, asyncResults)
Perhaps it's an ideal time to return cached results during the syncResults call if available and then the usual remote call in the async one.

Hi @chrisivens,
yes the new typeahead release includes a lot of changes, and there are actually some bugs with remote sources... So we decided to fork it and build our own autocomplete.js library: we'll update our website to promote it in the very next days.
You shouldn't have any issue using it instead of Typeahead.js, very similar: https://github.com/algolia/autocomplete.js
Let me know if that works for you!


Adapt traffic management rules to Kubernetes.

https://cn.dubbo.apache.org/zh-cn/overview/core-features/traffic/

https://github.com/apache/dubbo-admin/pull/1161


Implement Caching for Unchanged Data Nodes

Description
Summary:
Improve performance by caching data nodes that haven't changed since their last read. Subsequent reads could retrieve data from the cache instead of the original storage, speeding up access and improving application efficiency.
Details:

Cache only applies to unchanged data nodes.
Invalidate cache on data modification.
Optional for supported storage types.

Benefits:

Faster data access.
Reduced I/O operations.
Simplified application development.

This feature would significantly enhance performance for frequently accessed data nodes.
Acceptance Criteria

[ ] Ensure new code is unit tested, and check code coverage is at least 90%.
[ ] Propagate any change on the demos and run all of them to ensure there is no breaking change.
[ ] Ensure any change is well documented.

Code of Conduct

[X] I have checked the existing issues.
[ ] I am willing to work on this issue (optional)

Can you provide a dataset with a reference time, so we can monitor if the cache implementation actually improve the performance or not?

Depends on taipy-benchmark results.


Update OTP Auth to 1.0.0

After making all changes to the cask:

[x] brew cask audit --download {{cask_file}} is error-free.
[x] brew cask style --fix {{cask_file}} reports no offenses.
[x] The commit message includes the cask’s name and version.

Additionally, if adding a new cask:

[ ] Named the cask according to the token reference.
[ ] brew cask install {{cask_file}} worked successfully.
[ ] brew cask uninstall {{cask_file}} worked successfully.
[ ] Checked there are no open pull requests for the same cask.
[ ] Checked the cask was not already refused in closed issues.
[ ] Checked the cask is submitted to the correct repo.

Hey @reitermarkus,
Your changes looks good to me!


Prepare for Perl 7

Even if we don't adopt Perl 7 (and I'm aagnostic on that idea at the moment), there are a lot of best practices being enabled by default, so it'll be worth seeing what's needed to adopt them. Not least, it'll give me some insight before looking into how/if we should attempt this in the day job!
Some relevant links:

https://www.activestate.com/blog/getting-ready-for-perl-7/
https://leanpub.com/preparing_for_perl7

Fixed by PR #373


Nice-to-have feature: Allow to specify an additional indent amount

I'm using indoc to generate a YAML file. This is done piecewise; among other reasons to generate an array through a loop. Now these pieces need to be indented to produce a valid YAML.
It would be really nice to be able to specify an additional indentation amount that would apply to all lines. The effective code would be a minor change in https://github.com/dtolnay/indoc/blob/master/src/unindent.rs#L45-L47, but this would of course require more changes to pass around the parameter.
Currently, I see two workarounds for my use case:

Use a dummy character on the first line to define the indent level, which is either ignored (e.g., a line comment) or later removed. (This is what I do currently.)
Manually add spaces to the lines afterwards. Unfortunately this somewhat defeats the use of indoc in the first place.

I would be happy to contribute this feature, but I wanted to check if this is even desired before starting on it.

I would not want this built into this crate. But it would be nice for some to maintain a more fully featured macro library which could serve this use case.


Sitting Ducks support?

I haven't tried the tool yet, though given most games listed in README are after Version 1.38xx, while Sitting Ducks is 1.19(PS2) or 1.22(PC), I have doubts
I'll close this issue if there are no problems

Check out https://github.com/chebureki/DuckHax-CLI. All of my development for the BigFile format has moved to https://github.com/widberg/bff. I should just archive this repository.


Updating dependencies

I changed the dependencies to be less restrictive for the system which might include this crate.
I also changed config to be cloneable and adapted one test to the changes in uuid

The second change adds claims taken from user info, we might want to move that change into a separate PR.


Introduce captureUnhandledException

Currently we ask users to implement this in their error handler:
public function register()
{
    $this->reportable(function (Throwable $e) {
        if (app()->bound('sentry')) {
            app('sentry')->captureException($e);
        }
    });
}

However going forward we are going to change this to:
public function register()
{
    $this->reportable(function (Throwable $e) {
        \Sentry\Laravel\Integration::captureUnhandledException($e);
    });
}

The old way will still work but the "new way" will make sure exception are correctly marked as unhandled in the Sentry UI.
Fixes #607 (TODO: Docs PR)

I did thought about that, however, it's not certain that we have a unhandled exception there since a user could also just log an exception like they would use captureException, so it wouldn't be a 100% correct. WDYT?

Fair point, so let's leave it as is.

After switching from captureException() to captureUnhandledException() I'm no longer seeing any additional context in Sentry. No headers, no user, no breadcrumbs.
I'm using v3.1.0 of sentry/sentry-laravel.

@devfrey you are right... fixing that now @ #611!

3.1.1 was just released fixing this, sorry for that!

Our goal was to introduce a distinction between errors sent via captureException() handled: true and errors caught by the global error handler of the framework handled: false.
https://laravel.com/docs/9.x/errors#the-report-helper
public function isValid($value)
{
    try {
        // Validate the value...
    } catch (Throwable $e) {
        \Sentry\captureException($e); // handled: true

        return false;
    }
}

It's a bit odd that report() behaves that way. So we may have to make a decision on how to handle this going forward.
Having handled: false is highly valuable, as it highlights the errors with higher priority IMO.

@devfrey @axlon 3.1.2 was just released that properly sets the handled property when using report().

Yes, report_if() and report_unless() are also set to handled: true 🙂

Yes, report_if() and report_unless() are also set to handled: true 🙂


Add reasons why to not use uuid_generate_v4 in migrations

Description
I wanted to note down why we do not generate uuids in a migration but before to help future people understand the choice better.
References

#169549297 for this change

Can you find instances of uuid_generate_v4() in the docs/ folder and either fix them or link to this comment wherever you see them? I am seeing stuff in a few places around tspp and tariff data that should be fixed or annotated.

@chrisgilmerproj that's not in the scope of this story. Plus that would have to involve developing new instructions how to do those imports. I would request that a new story is written to handle that. Plus I see a bunch of migrations using it and how do you want to handle that?

@chrisgilmerproj that's not in the scope of this story. Plus that would have to involve developing new instructions how to do those imports. I would request that a new story is written to handle that. Plus I see a bunch of migrations using it and how do you want to handle that?

Maybe I was confusing. I'm asking for documentation fixes only. Links primarily but if you can fix something that would be nice.

Also, @jacquelineIO - since I forgot to add this. Previous migrations aren't ever run again in Production so we decided to leave them alone. We can retroactively modify all of them but it would only affect development and was considered not worth it at the time.

@chrisgilmerproj Adding links seems reasonable. I think the two docs may have been okay since they are for generating sql to import into the database, which I think is typically exported. But just in case I made some updates to hopefully clarify things. Please review it again and let me know if it's good to go.


consider using github pages instead of tgz in the repo

What
Please consider using github pages to host the index.yaml and tgz files that comprise a helm release, instead of committing binary blobs into the git repo
Why
Git is not well suited for hosting binary artifacts, and committing a tgz for each release will cause the repo to grow without bound (short of using some repo surgery commands to expunge old artifacts)
How
Take for example the kubernetes ingress-nginx repo:
https://github.com/kubernetes/ingress-nginx/blob/helm-chart-3.29.0/.github/workflows/helm.yaml although I'm sure there are others, that's just the most famous one that sprang to mind which uses this pattern
One can see the repo patterns in their install instructions

The helm chart releaser action as well as the chart tester action are two github actions-based test and deployment patterns used by a lot of helm chart repo owners today.
It may be a good idea to at least explore or investigate this as a quick solution to achieving the concept of leveraging github pages to publish helm chart releases.  There is even a demo repo showing how the actions work together.


Add firestore

Generated a new client from swagger for Firestore.

Veebie, my employer has signed the the CLA.

It's signed!

@bshaffer Yes indeed! I'm using it right now, working beautifully! 🤓

@chingor13 Yes, we have some plans to work on getting a Firebase SDK using gRPC going when grpc-elixir is a bit more stable, based on the Ruby version. In the interim, we don't really need Pub/Sub on our backend, we only need it on the clients and interacting with Firestore via REST is perfect for our specific use case at the moment.
I ran the formatter on the client and updated the copy right notices across all files in the project. Those changes are in two separate commits for obvious reasons 😆

@carlodicelico Sorry, I meant to update the copyright year only on the new files (ones in the firebase client only). I opened #65 for me to deal with. If we change them here, it would have to be manually.

Oh! I misinterpreted the phrase "on all the files". 😆 I'll fix that now.


New package: Lux v0.3.0

Registering package: Lux
Repository: https://github.com/avik-pal/Lux.jl
Created by: @avik-pal
Version: v0.3.0
Commit: 3a7a44a217cd89023db91a05e74138fa689b58f1
Reviewed by: @avik-pal
Reference: https://github.com/avik-pal/Lux.jl/commit/3a7a44a217cd89023db91a05e74138fa689b58f1#commitcomment-72800577
Description: Explicitly Parameterized Neural Networks in Julia

[noblock] This is a package name change from ExplicitFluxLayers to Lux
Public Discussion regarding name change -- https://julialang.slack.com/archives/C690QRAA3/p1650979193377099


Work towards "mod refactor" (issue 5)

As per subject.
No functional changes, just a refactor of the code we already have.
This starts to go in the direction of what is described in #5.
TODO after this: break up modROS.lua into separate functional units and use modROS.lua itself only to coordinate/glue everything together.

I've tested this in FS just now. No errors loading files, and everything appears to work as it did before the shuffle.

Feel free to merge.


Deployment fails when creating and setting permissions on new table in same commit

Before opening, please confirm:

[X] I have searched for duplicate or closed issues and discussions.
[X] I have read the guide for submitting bug reports.
[X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.

JavaScript Framework
Not applicable
Amplify APIs
GraphQL API
Amplify Categories
function
Environment information

  System:
    OS: macOS 11.2.3
    CPU: (8) x64 Apple M1
    Memory: 23.94 MB / 16.00 GB
    Shell: 5.8 - /bin/zsh
  Binaries:
    Node: 15.12.0 - /usr/local/bin/node
    npm: 7.6.3 - /usr/local/bin/npm
  Browsers:
    Chrome: 90.0.4430.212
    Firefox: 88.0.1
    Safari: 14.0.3
  npmPackages:
    @babel/cli: ^7.10.5 => 7.12.10
    @babel/core: ^7.10.5 => 7.12.10 (7.9.0)
    @babel/plugin-proposal-class-properties: ^7.10.4 => 7.12.1 (7.8.3)
    @babel/preset-env: ^7.10.4 => 7.12.11 (7.9.0)
    @emotion/react: ^11.1.5 => 11.1.5
    @emotion/styled: ^11.1.5 => 11.1.5
    @fortawesome/fontawesome-free: ^5.13.0 => 5.15.1
    @fortawesome/fontawesome-svg-core: ^1.2.28 => 1.2.32
    @fortawesome/free-solid-svg-icons: ^5.13.0 => 5.15.1
    @fortawesome/react-fontawesome: ^0.1.9 => 0.1.13
    @material-ui/core: ^5.0.0-alpha.25 => 5.0.0-alpha.27
    @material-ui/icons: ^5.0.0-alpha.24 => 5.0.0-alpha.27
    @sentry/cli: ^1.63.1 => 1.61.0
    @sentry/react: ^6.3.6 => 6.3.6
    @sentry/rrweb: ^0.2.0 => 0.2.0
    @sentry/tracing: ^6.3.6 => 6.3.6
    @sentry/webpack-plugin: ^1.14.1 => 1.14.0
    @testing-library/jest-dom: ^4.2.4 => 4.2.4
    @testing-library/react: ^9.5.0 => 9.5.0
    @testing-library/user-event: ^7.2.1 => 7.2.1
    aws-amplify: ^3.3.4 => 3.3.13
    body-parser: ^1.19.0 => 1.19.0
    brace: ^0.11.1 => 0.11.1
    classnames: ^2.2.6 => 2.2.6
    copy-to-clipboard: ^3.3.1 => 3.3.1
    cypress: ^5.4.0 => 5.6.0
    example:  undefined ()
    formik: ^2.1.4 => 2.2.6
    foundation-sites: ^6.6.1 => 6.6.3
    husky: ^4.2.5 => 4.3.6
    immutable: ^4.0.0-rc.12 => 4.0.0-rc.12
    jsoneditor: ^9.0.0 => 9.1.5
    jsoneditor-react: ^3.0.0 => 3.1.0
    libphonenumber-js: ^1.9.11 => 1.9.13
    libphonenumber-js-core:  1.0.0
    libphonenumber-js-max:  1.0.0
    libphonenumber-js-min:  1.0.0
    libphonenumber-js-mobile:  1.0.0
    lint-staged: ^10.2.11 => 10.5.3
    lodash: ^4.17.21 => 4.17.20
    mime-types: ^2.1.27 => 2.1.27 (2.1.11)
    mochawesome-report-generator: ^5.1.0 => 5.1.0
    node-sass: ^4.13.1 => 4.14.1
    prettier: ^1.19.1 => 2.2.1
    prettier-airbnb-config: ^1.0.0 => 1.0.0
    react: ^16.13.1 => 16.14.0 (16.13.1)
    react-alice-carousel: ^2.4.0 => 2.4.0
    react-countdown-circle-timer: ^1.2.1 => 1.2.1
    react-datepicker: ^2.15.0 => 2.16.0
    react-device-detect: ^1.17.0 => 1.17.0
    react-dom: ^16.13.1 => 16.14.0
    react-ga: ^3.0.0 => 3.3.0
    react-modal: ^3.11.2 => 3.12.1
    react-phone-input-2: ^2.13.9 => 2.13.9
    react-places-autocomplete: ^7.2.1 => 7.3.0
    react-responsive-carousel: ^3.2.12 => 3.2.13
    react-router: ^5.1.2 => 5.2.0
    react-router-config: ^5.1.1 => 5.1.1
    react-router-dom: ^5.1.2 => 5.2.0
    react-scripts: 3.4.1 => 3.4.1
    react-select: ^3.1.0 => 3.1.1
    react-toastify: ^5.5.0 => 5.5.0
    react_advanced_demo:  0.1.0
    react_demo:  0.1.0
    rrweb: ^0.9.14 => 0.9.14
    source-map-explorer: ^2.4.2 => 2.5.1
    uuid: ^8.1.0 => 8.3.2 (3.4.0, 3.3.2)
    yup: ^0.28.3 => 0.28.5
  npmGlobalPackages:
    eslint: 7.25.0
    lambda-local: 1.7.4
    n: 7.0.1
    node-prune: 1.0.2
    npm: 7.6.3
    webpack-cli: 4.5.0
    webpack: 5.26.3

Describe the bug
If I define a new @model in my schema.graphql, then try to give one of my functions access to it through the amplify CLI using
amplify function update -> select function -> resource access permissions -> storage -> choose table,
then push, the push fails with
No export named qifwdw4eyfcabcgphqnnygcele:GetAtt:ExpendedBudgetTable:Name found
Expected behavior
The deployment should succeed, with the API changes being deployed first, and the resource permissions afterwards.
Reproduction steps

Add a new table using the @model directive in schema.graphql
amplify push
Update a function to reference that new table using
amplify function update -> select function -> resource access permissions -> storage -> choose table, e.g. MyTable: @model(appsync) -> give it permissions, etc.
Commit code in one commit.
Try deploying code to a different env

Code Snippet
N/A
Log output

 UPDATE_FAILED functioncreateCardForUserCampaign AWS::CloudFormation::Stack Mon May 17 2021 23:21:49 GMT+0000 (Coordinated Universal Time) Embedded stack arn:aws:cloudformation:us-east-2:272407951964:stack/amplify-wesponsored-web-production-20723-functioncreateCardForUserCampaign-1BWFDKU94KSEO/b872d820-af9a-11ea-9960-023006f8d510 was not successfully updated. Currently in UPDATE_ROLLBACK_IN_PROGRESS with reason: No export named qifwdw4eyfcabcgphqnnygcele:GetAtt:ExpendedBudgetTable:Name found

aws-exports.js
No response
Manual configuration
No response
Additional configuration
No response
Mobile Device
No response
Mobile Operating System
No response
Mobile Browser
No response
Mobile Browser Version
No response
Additional information and screenshots
No response

@josefaidt transferred as this sounds like more of a cli issue than a js one.

@yiweixia This is a bug I can verify that for now you could push the api first by invoking amplify push api and then do an amplify push. The lambda function gets deployed first and looks for the table while it's not deployed yet.

Thanks @ammarkarachi, I had the same issue.
I still had to remove the function before running amplify push api, which worked, and then re-added the function.
When I ran amplify push api it still tried to update the function (which fails), perhaps because the function still has a dependency on the API?  I'm not really sure.

@ngnathan I believe we are missing a depends on when the deployment happens in the same call. As another workaround you could remove the permission and add the permissions back. I know this is kind of an inconvenience but we should have a fix out soon


Unresolved dependency bdio2:3.2.1

58.0.1 and above depend on com.blackducksoftware.bdio:bdio2:3.2.1, which is not available in any of configured repositories.

Have you tried excluding the module? E.g. if using Gradle:
implementation ('com.synopsys.integration:blackduck-common:58.0.1') {
    exclude group: 'com.blackducksoftware.bdio', module: 'bdio2'
  }


Missing required key 'KeyId' in params

This error happens when I attempt to encrypt. The alias for my KMS is PhotoboothConn
service: userApi
provider:
   ...
plugins:
   - serverless-crypt
custom:
   - cryptKeyId: ${env:PhotoboothConn}
functions:
   ...

And the command I run is
sls encrypt -n PhotoboothConn -t "postgres://restOfConnectionString" --save

@Outc4sted Thank you for your reporting.
cryptKeyId  must be a valid KMS key ID.
Does ${env:PhotoboothConn} mean "Using PhotoboothConn environment variable" in Serverless Framework.
Have you set PhotoboothConn  environment variables?

I didn't. I thought when I created the KMS it would automatically be set as an environment var for my lambdas. I just tried with pasting my key id in there and that worked, so thanks. Is it okay to make that into an environment var within my serverless.yml or is that something sensitive I don't want in plain text?

Is it okay to make that into an environment var within my serverless.yml or is that something sensitive I don't want in plain text?

I think it is better not to show the ID to others. But, it is not a problem. It's like Account ID in the relationship between Account ID and Password.


[VA-5837] Add cdn field in xdm schema in mediaCollection and mediaReporting

https://github.com/adobe/xdm/issues/1550

@mjasrotia please review, this PR adds a field on the sessionDetails datatype which will be needed for both mediaCollection and mediaReporting


Import issue

Hi.  Awesome program.  I have modeled a head in SculptGL and attempted to save it.  It downloaded as a 116mb .text file.  It's not opening which seems kind of obvious.  Is the file corrupted or should I change the file extension?  I will remodel if necessary.  Any advice would be greatly appreciated.  Thanks

And of course just like that I changed the file extension and it worked.  Please disregard.


Cannot find entry file index.ios.js

This error occur on my first attempt to build / run the starter kit.
Repro(s)
git clone https://github.com/jhabdas/react-native-webpack-starter-kit.git mobile && cd $_
npm install # or simply npm i
npm start

Open ios/App.xcodeproj in Xcode, build and run the project.

Environment(s)
npm ERR! Darwin 15.0.0
npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "install"
npm ERR! node v4.2.1
npm ERR! npm  v2.14.7

It started working after I made small changes to the  component in App.js. Could it be that index.ios.js did not generate initially?  I don't see ios.index.js anywhere in the root directory.

Sorry to hear you're having issues getting set-up @thachp. But you're almost there! I used nvm to install v4.2.1 and then did a npm i -g<EMAIL_ADDRESS>to get your version of NPM and, after a fresh clone from master see the following:

Try taking a spin through the the Getting Started guide for RN again please let us know how it goes!

Superb. Glad to hear you got it working. I dropped some knowledge in the README to help you get through from here to the App Store. Best of luck!


Orchestrator Recovery Time (version 3.0.11)

Description
I discussed this long time ago with @shlomi-noach in Slack and I finally got the chance to start looking into this. I'm looking into better understand what are the expected times that orchestrator should take to recover a dead master.
In our setup, I'm seeing two patterns in how long it takes to recover a dead master and wanted to check if these are the expected times or if there are ways to improve this and shorten this time.
Pattern 1:

Time
Event

11:07:35
Master is Dead from App perspective

11:07:42
UnreachableMaster

11:07:46
DeadMaster

11:07:58
DeadMaster Recovered

Total Time: 23s
Pattern 2:

Time
Event

16:23:45
Master is Dead from App perspective

16:23:52
UnreachableMaster

16:23:55
DeadMaster

16:23:57
DeadMaster Recovered

Total Time: 12s
From my observations in these tests, the time that it takes orchestrator to declare a DeadMaster is pretty stable (around 10s).
The time that it takes to recover seems to vary and I would love to understand this a bit better. When I look in the audit log, when it takes longer, the time is being spent in these steps:
2018-10-05 11:07:46 | RecoverDeadMaster: regrouping replicas via GTID
-- | --
2018-10-05 11:07:58 | RecoverDeadMaster: 0 postponed functions

Other notes:
I tried what we discussed in Slack:
change master to master_heartbeat_period=5

But that didn't make a difference in the detection time.

@rafael both these times fall under our acceptable failover time expectation, but we got more on the 12sec side than on the 23sec side.
change master to master_heartbeat_period=5

A 10sec detection time is OK but can be made better; we see down to 5-7sec. You have updated heartbeat to 5 on all servers, correct? At chat, I suggested setting slave_net_timeout=5 which implicitly causes master_heartbeat_period to be half that value. That would shave off a couple more seconds.
Did you also set MASTER_CONNECT_RETRY to 1? To elaborate, with both these settings at hand, a replica will detect master is gone by heartbeat interval, plus 1secit will take for it to attempt to reconnect to master, after which it will most surely claim "I'm broken".
As you work with GTID, and time is spent on regrouping replicas via GTID, I have some hints for you:

MySQL does not-so-good of a job in correlating the binary logs of a replica and a would-be master. At best case scenario it will scan the last binary log of the would-be master sequentially from top until it finds the position (GTID entry) to correlate the replica to. It will do so multiple times, once per replica.

(To contract, with Pseudo-GTID orchestrator records and caches heuristic "injection points" into the binary logs, and can jump directly into a heuristic last section of the log).
So: the time it takes to run regrouping replicas via GTID basically depends on the size of the binary logs.
Easy answer (which I have done before): standard binary log size is 1G. Reduce it to 100MB. You'll get 10x binary logs at smaller size. 100MB is small enough size for GTID scan to be faster.
Also, do you happen to have a delayed replica among those replicas which were regrouped? I incidentally optimized that in https://github.com/github/orchestrator/pull/641 (not yet merged).

@shlomi-noach -  Correct, I updated all the servers. I will check MASTER_CONNECT_RETRY. Thank you for these pointers. I'll play with them and report back.
oh I was actually thinking the same about the GTID issue. Could we apply the same trick we did in Vitess in https://github.com/vitessio/vitess/issues/4161 to flush binary bin logs before we try to regroup GTIDs?

In the tests I did, the replicas were not delayed. But I think binlogs were big. I will try to reproduce this situation.

Could we apply the same trick we did in Vitess in vitessio/vitess#4161 to flush binary bin logs before we try to regroup GTIDs?

That won't help you at time of failover since there's no incoming writes to populate the newly rotated binary logs.

@shlomi-noach - Correct, I updated all the servers. I will check MASTER_CONNECT_RETRY. Thank you for these pointers. I'll play with them and report back.
oh I was actually thinking the same about the GTID issue. Could we apply the same trick we did in Vitess in vitessio/vitess#4161 to flush binary bin logs before we try to regroup GTIDs?

Ah yes. Forgot about that detail.

You can either configure the binary logs to be 100MB, or to routinely flush them via cron/daemon as soon as they extend 100MB (just make sure to SET SQL_LOG_BIN=0).

BTW you can ask orchestrator to flush logs on a server: orchestrator -c flush-binary-logs -i <instance>

Thanks @shlomi-noach. Yes! we've used that one in the past.
Our slave_net_timeout was too high and with a more careful setup, I was able to reproduce some slow detection times... similar to the ones we've seen in prod.
We are in the process of rolling out a change to set slave_net_timeout to 5s in prod.
Still thinking what to do about the binlogs issue.
I'll make sure to update here if we see improvements next time we get failure!

Looking forward for your update.
I got to thinking. Since the binlog size is a read-only variable in MySQL (need to restart server to apply it), it would be reasonable in my opinion to have orchestrator auto-flush binary logs that exceed a configured size. It's also easy to solve via cronjob, but orchestrator is already there, is already observing the binlog status, has the privileges to rotate logs...


AI-Powered Resume Analyzer with LLM #399

Related Issues or bug
Resume AI Analyzer project! This project aims to leverage machine learning techniques to help job seekers optimize their resumes for specific job applications. We are excited to have contributors who are interested in improving the job application process through AI.
Fixes: #399
Proposed Changes
Features
Keyword Extraction: Identifies critical keywords from job descriptions and suggests their inclusion in the user's resume.
Formatting Recommendations: Provides tips on how to format resumes for better readability and ATS compatibility.
Scoring System: Gives a score based on the resume's relevance to the job description, helping users understand their strengths and weaknesses.
Interactive Feedback: Users receive real-time feedback on their resumes with suggestions for improvement

@UppuluriKalyani kindly review my pr :)

@Niraj1608 show me results (screenshots of screen recording)

@UppuluriKalyani hey check
AI_Powered_Resume_Analyzer.ipynb - Colab.pdf

@UppuluriKalyani Thank you :)


Realignment of Choose page

Patient / Clinician - same line
Genders - all 3 try to fit in same line
Male / female - sex assigned at birth in the same line.
4)Continue button | Blue | Centre aligned

So we can add another button --- "Tell us more about your health status" or any other catchy line -- redirects us to a questionnaire (to be prepared).

Moving the issue to test


index.html is colorless

Is it only me or the top page after running coverage html is colorless ?

When clicking on files, the code is properly highlighted, but it would be very helpful if the index showed each file with a green or red background to highlight the coverage on that file.

I have it all colored


zif_interface missing type declarations

When using the openAPI JSON from https://api.sap.com/api/Subscription_APIs/overview in the abap.openapi-client, resulting element 'totaledvalues' of type 'totaledprices' in zif_interface is  created as 'totaledvalues TYPE STANDARD TABLE OF  WITH DEFAULT KEY' with the row type missing. The row type seems to not only be missing in the 'totaledprices' type definition but seems to not be included in zif_interface at all. - Element 'totaledvalues' of 'totaledprices' is one of 10 missing type definitions.

yea, I hope to get some more time to fix stuff
but, as always, pull requests welcome


fix: retrieve DependentResource based on name instead of class

This causes issues if the class is proxied for any reason (e.g. because
it's a CDI bean).

Could the name be provided by the DependentResourceSpec and set during createAndConfigureFrom ?

This would allow to have two dependents of the same type with different name. Related to your question https://github.com/java-operator-sdk/java-operator-sdk/issues/1038#issuecomment-1068488775. Even if without configuration, I doubt it would be that usefull.
This would allow to have the real static class name from annotation in logs instead of I guess the proxy one return by getClass.getCanonicalName ?

Could the name be provided by the DependentResourceSpec and set during createAndConfigureFrom ?

This would allow to have two dependents of the same type with different name. Related to your question DependentResource CDI awareness #1038 (comment).
This would allow to have the real static class name from annotation in logs instead of I guess the proxy one return by getClass.getCanonicalName ?

And name could be latter override by configuration on the annotation if needed

Looks good so far, my question is also that, the name should be mandatory in the annotation? Or how do you see that?

Looks good so far, my question is also that, the name should be mandatory in the annotation? Or how do you see that?

If not provided, then it should take the type canonical name and raise an error if there is a dup

Looks good so far, my question is also that, the name should be mandatory in the annotation? Or how do you see that?

If not provided, then it should take the type canonical name and raise an error if there is a dup

Yep, probably a sensible default makes sense in this case.

Could the name be provided by the DependentResourceSpec and set during createAndConfigureFrom ?

Yes, that's the plan indeed.

This would allow to have two dependents of the same type with different name. Related to your question DependentResource CDI awareness #1038 (comment).

This would allow to have the real static class name from annotation in logs instead of I guess the proxy one return by getClass.getCanonicalName ?

I think so, yes.

Looks good so far, my question is also that, the name should be mandatory in the annotation? Or how do you see that?

If not provided, then it should take the type canonical name and raise an error if there is a dup

Yes, that is the plan but this PR is not finished yet. Great to see some early feedback that validates what I was thinking, though! 😄

Still having issues with this, so switching back to draft mode as I uncovered issues that need to be fixed with the event source registration. Basically, the dependent resource name should be propagated to the associated event source if it exists.  The MySQL sample is also behaving weirdly…

Can we merge this?


WebView control for MAUI application using Chromely

I got chromely cross plat working.
I want to make it as control similar to webview
Can this be achieved, and it needs to work both on windows and macOS
I am using MAUI application

@vmeganathan81
The way Chromely is designed, no you cannot use it as a control. It is a browser running in a thin host - Win32, GTK or Cocoa window.
With some work it is of course possible, but not as-is.


masked array error

loglikelihoods[i] = kf.loglikelihood(data.observations) incurred masked array error in scipy linalg module.
This needs to be changed to loglikelihoods[i] = kf.loglikelihood(data.observations.data)

I get problems from this line:
https://github.com/pykalman/pykalman/blob/8d3f8e498b64d902016a0216bf2bcc8b262d917b/pykalman/utils.py#L73
I wrapped the inputs to the linalg function in np.asarray(a) and things worked.

I get the error in plot_em.py. Can you provide the code to fix it @JesseLivezey ?

https://gist.github.com/JesseLivezey/5d80ef651e75b21a7079

Is this now merged?


CAMEL-15635: Fixed some Kudu tests that were failing with JDK >= 12

[ ] Make sure there is a JIRA issue filed for the change (usually before you start working on it).  Trivial changes like typos do not require a JIRA issue.  Your pull request should address just this issue, without pulling in other changes.
[ ] Each commit in the pull request should have a meaningful subject line and body.
[ ] If you're unsure, you can format the pull request title like [CAMEL-XXX] Fixes bug in camel-file component, where you replace CAMEL-XXX with the appropriate JIRA issue.
[ ] Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
[ ] Run mvn clean install -Psourcecheck in your module with source check enabled to make sure basic checks pass and there are no checkstyle violations. A more thorough check will be performed on your pull request automatically.
Below are the contribution guidelines:
https://github.com/apache/camel/blob/master/CONTRIBUTING.md

Let's see the checks, maybe we merge after the release ?

Gregor is working on a branch, he confirmed this. We have already the 3.8.x branch pushed here. So we can safely merge.

Many thanks @oscerd


Fix bug of unmanagedResourceDirectories

I found that sometimes files in directories added to unmanagedResourceDirectories are ignored.
This was because the resourcesDirectories are managed as a Set like below
  def copyResourcesTask =
    Def.task {
      val t = classDirectory.value
      val dirs = resourceDirectories.value.toSet
      ...

But, you know, the default Set in scala is implemented as a HashSet, which does not guarantee ordering of elements.
For example, When I added my config directory src/main/resources/conf to unmanagedResourceDirectories in order to include a file called src/main/resources/conf/my-conf.json as a resource, but my config file was compiled as target/scala/classes/conf/my-conf.json, not target/scala/classes/my-conf.json.
When I printed out the variable dirs mentioned above, I got the following result. (For convenience, represent the project path as ~)
Set(~/src/main/resources/conf, ~/src/main/resources)

When I improved it using SortedSet and printed out the variable dirs, It looks fine!
TreeSet(~/src/main/resources,~/src/main/resources/conf)

Hi @minkyu97,
Thank you for your contribution! We really value the time you've taken to put this together.
Before we proceed with reviewing this pull request, please sign the Lightbend Contributors License Agreement:
https://www.lightbend.com/contribute/cla

I signed the CLA as individual

TreeSet(~/src/main/resources,~/src/main/resources/conf)

Thanks for the report and sending a PR. Are you saying that sbt currently does not support adding overlapping unmanagedResourceDirectories like src/main/resources and its subdirectory src/main/resources/conf? I think that's an intended design, and I am not sure if we should make the set sorted to support this.

@eed3si9n Thanks for the comment.
You're right, the problem occurs when unmanagedResourceDirectories is a subdirectory of other resources.
Although this may not be mainstream, I think it's a workable way to do it and doesn't impact existing logic at all. Do you have any issues you're anticipating when you sort this out?

Are there any issues you're worried about when sorting it?

I think so. In general having static typing in the build definition allows sbt, builds, and plugin ecosystem to evolve at different pace. I am particularly concerned about making implementation-level changes that would make semantic difference in exactly the opposite of what the type promises in an observable way. It might work for some time, but it could break again later. I would recommend creating a different directory with your conf files.

Are there any issues you're worried about when sorting it?

I think so. In general having static typing in the build definition allows sbt, builds, and plugin ecosystem to evolve at different pace. I am particularly concerned about making implementation-level changes that would make semantic difference in exactly the opposite of what the type promises in an observable way. It might work for some time, but it could break again later. I would recommend creating a different directory with your conf files.

If I take the paths to the unmanaged resources directories out of resources, the same problem will occur if one unmanaged resources directory becomes a superset of another unmanaged resources directory.
However, I also agree with you that having static typing at build time can cause problems. I've also thought about it and determined that the underlying problem is not that the dirs variable is unordered, but that unordered oldBases are being passed to the rebase function. So, How about changing the rebase function to something like below? Do you still think it's not worth it?
  def rebase(oldBases: Iterable[File], newBase: File, zero: FileMap = transparent): FileMap =
    fold(zero, oldBases.toList.sorted)(old => rebase(old, newBase))

@eed3si9n Hi, there!
I'm sorry for bothering you again 😥
Can you let me know if there is a possibility of causing issues at build time by changing copyResourcesTask as follows?
  def copyResourcesTask =
    Def.task {
      val t = classDirectory.value
      val dirs = resourceDirectories.value.toSet
      val sortedDirs = resourceDirectories.value.sorted
      val s = streams.value
      val syncDir = crossTarget.value / (prefix(configuration.value.name) + "sync")
      val factory = CacheStoreFactory(syncDir)
      val cacheStore = factory.make("copy-resource")
      val converter = fileConverter.value
      val flt: File => Option[File] = flat(t)
      val transform: File => Option[File] = (f: File) => rebase(sortedDirs, t)(f).orElse(flt(f))
      val mappings: Seq[(File, File)] = resources.value.flatMap {
        case r if !dirs(r) => transform(r).map(r -> _)
        case _             => None
      }
      s.log.debug("Copy resource mappings: " + mappings.mkString("\n\t", "\n\t", ""))
      Sync.sync(cacheStore, fileConverter = converter)(mappings)
      mappings
    }

I just added a variable, sortedDirs, and only used it in the rebase function instead of using static typing.
The directories within sortedDirs are always sorted and rebase function will traverse them in reverse order (because it is @tailrec function), so the arbitrary path X will always be processed later than X/Y which is also an arbitrary subpath of X.
Therefore, the problem will be resolved.

@eed3si9n Hi, there!
I'm sorry for bothering you again 😥
Can you let me know if there is a possibility of causing issues at build time by changing copyResourcesTask as follows?
  def copyResourcesTask =
    Def.task {
      val t = classDirectory.value
      val dirs = resourceDirectories.value.toSet
      val sortedDirs = resourceDirectories.value.sorted
      val s = streams.value
      val syncDir = crossTarget.value / (prefix(configuration.value.name) + "sync")
      val factory = CacheStoreFactory(syncDir)
      val cacheStore = factory.make("copy-resource")
      val converter = fileConverter.value
      val flt: File => Option[File] = flat(t)
      val transform: File => Option[File] = (f: File) => rebase(sortedDirs, t)(f).orElse(flt(f))
      val mappings: Seq[(File, File)] = resources.value.flatMap {
        case r if !dirs(r) => transform(r).map(r -> _)
        case _             => None
      }
      s.log.debug("Copy resource mappings: " + mappings.mkString("\n\t", "\n\t", ""))
      Sync.sync(cacheStore, fileConverter = converter)(mappings)
      mappings
    }

I just added a variable, sortedDirs, and only used it in the rebase function instead of using static typing.
The directories within sortedDirs are always sorted and rebase function will traverse them in reverse order (because it is @tailrec function), so the arbitrary path X will always be processed later than X/Y which is also an arbitrary subpath of X.
Therefore, the problem will be resolved.

@minkyu97 Sorry about the delayed response. I'd be fine with going forward with the idea.

@eed3si9n I'm sorry too.. I missed your comment for a long time because of my work. I pushed a commit applying the above idea. I'd appreciate it if you could take a look at it and close the PR if you don't think it needed to be applied.


feature(wayland): add double buffering

Add double buffering to Wayland driver: one buffer is updated while another one is being displayed.
This doubles the memory requirement, but lowers the possibility to encounter a busy buffer when LVGL core is ready to draw.
Signed-off-by: Francesco Valla<EMAIL_ADDRESS>

Please note that the MR is marked as draft as it is still, in fact, a draft: some of the logic for a proper double buffering is still lacking. Moreover, the entire work will probably be converted to a direct_mode implementation for better performance (no data copy).

Added carry-over of previous buffer damages, proper double-buffering logic should be in place now.

And the problem https://github.com/lvgl/lv_drivers/pull/242 still exist. (I haven't found the reason so far.)

you can use weston --use-pixman to test on you machine.
Thanks @WallaceIT

Recently, I was studying the implementation of weston-terminal. It need some time. I think we can find a good solution from it.
The code is located in weston/clients/terminal.c in (weston)[https://gitlab.freedesktop.org/wayland/weston]


Add error popup if dependency wasn't added

Related to #4

I've applied your suggestions, @yigit , but it still wants me to fix something :) Please, do not disappear for next two months, let's merge this PR so I can say to my friends that I've contributed to ArtifactFinder :D

:+1: i'll stay around no worried. I kind of get side-tracked w/ work and wasn't sure how many people are actually using the plugin, i love it though (being in the android team, we create way too many new projects to reproduce bugs etc so it help me a lot :) )

so i guess i'll wait to merge this? We can merge this  (if it works) and do another PR for whatever else you want to fix?

It works, @yigit.

I'm open to suggestions, @yigit , have no idea what is really needed.

I was just trying this before i push a new version but it actually fails if it is added as we cannot query the model before sync.
i'll play w/ this see how we can get this data w/o sync as waiting for sync will be very unresponsive (but might be reasonable).


Change "auto generated" to "auto-generated"

Change "auto generated" to "auto-generated"

Again, a really minor edit on a file that is itself auto generated. Please avoid in the future

Noted. Thank you.


Test prelude package

Codecov Report

Merging #928 (f50c6a5) into main (cb65976) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #928   +/-   ##
=======================================
  Coverage   84.30%   84.30%
=======================================
  Files         387      387
  Lines       40855    40855
=======================================
  Hits        34441    34441
  Misses       6414     6414

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 cb65976...f50c6a5. Read the comment docs.


Duplicate Bile Acid Synthesis Reactions

Background:
There are currently pathways for converting 25(R)THCA-CoA to cholyl-CoA/cholate in both the [m] and [x] comparments, but these reactions only occur in peroxisomes (sources: (1, 2, 3)), so all of the [m] reactions (and their associated metabolites, since they do not participate in any other reactions) should be removed. Some of these reactions were already mentioned in #634, so I've updated the proposed changes in #634 to skip these reactions, since I have now determined that they do not occur in mitochondria
Diagram with metabolite/reaction IDs:

with metabolite names:

MAR01458 sort of duplicates MAR01642+MAR01646, except there's also conversion of O2 to water, and I have no idea where that's coming from; also the only gene associated with it, HSD17B4, is only known to be NAD-dependent and not NADP-dependent (Uniprot), so I'm pretty sure it should be removed.
According to the reference associated with MAR01656, "all newly formed primary bile acid-CoA esters within the peroxisomes are instantly conjugated in situ with glycine or taurine before secretion", so MAR01656 should also be removed, because MAR01659 already represents ATP-dependent import of choloyl-CoA into peroxisomes.
While there are enzymes that produce choloyl-CoA in the cytosol, MAR07758, MAR01662, and MAR01666 are also suspicious because:

The only gene associated with MAR07758, DBI (ENSG00000155368), is not known to be localized to mitochondria, and MAR07758 has no references associated with it
The references (1, 2, 3, 4) associated with MAR01662 all provide evidence of this reaction occuring in peroxisomes, not mitochondria
The reference associated with MAR01666 says that "a transport system similar to the carnitine/carnitine palmitoyl transferase machinery used to import fatty acids into the mitochondria may exist to shuttle bile acid intermediates between intracellular compartments; however, no covalently modified derivatives of bile acid intermediates that could represent a transport form have been reported", and neither associated gene (SLC27A2 and SLC27A5) is known to localize to either mitochondrial membrane or transport cholate

Proposed Changes:

[ ] Remove MAR01630, MAR01635, MAR01637, MAR01644, MAR01651, MAR01653, MAR03754, and MAR03760 for being redundant with peroxisomal versions
[ ] Remove MAM00616m, MAM00618m, MAM00749m, MAM00036m, MAM00748m, MAM03367m, MAM01445m, and MAM01514m (MAM03368m was already removed in #649)
[ ] Remove MAR01656 for being redundant with MAR01659
[ ] Remove MAR07758, MAR01662, and MAR01666 for being redundant with peroxisomal versions
[ ] Remove MAR01458 for being redundant with MAR01642+MAR01646

I think it's pretty evident from these diagrams that MAR03764, MAR03756, MAM03368x, and MAM003367x should also be removed for being redundant with MAR01646, MAR01642, MAM00748x, and MAM00036x, but I didn't include those proposed changes here, since it seems like #616 is going to handle that

nice plot!
it seems that enough evidence has been provided for removing the mitochondria version

Some of these reactions were already mentioned in https://github.com/SysBioChalmers/Human-GEM/issues/634, so I've updated the proposed changes in https://github.com/SysBioChalmers/Human-GEM/issues/634 to skip these reactions, since I have now determined that they do not occur in mitochondria

very good that you noticed overlap issue to this one (please always check overlap/conflict issues before making new ones).

I think it's pretty evident from these diagrams that MAR03764, MAR03756, MAM03368x, and MAM003367x should also be removed for being redundant with MAR01646, MAR01642, MAM00748x, and MAM00036x, respectively, but I didn't include those proposed changes here, since it seems like https://github.com/SysBioChalmers/Human-GEM/issues/616 is going to handle that

A likely sequence of implementation might be: 1) #616; 2) #637; 3) #634. what do you think?

A likely sequence of implementation might be: 1) https://github.com/SysBioChalmers/Human-GEM/issues/616; 2) https://github.com/SysBioChalmers/Human-GEM/issues/637; 3) https://github.com/SysBioChalmers/Human-GEM/issues/634. what do you think?

Sounds reasonable to me

by looking into the pair of MAR01635 versus MAR01632, they both are supported by the annotation of associated gene AMACR (ENSG00000242110) in catalytic activity and subcellular localization. Should it really be removed? any more evidence for the deletion?

Yes, because while AMACR is localized to both compartments, the substrate of MAR01653 is not produced in mitochondria, since it is strictly an intermediate in bile acid production, which only occurs in peroxisomes, because only peroxisomal fatty acid oxidation machinery can handle bile acids (sources: 1, 2, 3)

Ok let's move forward according to the provided evidence.
Even if new conflicting evidence appeared later, the changes can be easily reverted given the clear history in #637


A warning in VS2019

warning MSB8028: The intermediate directory (Release) contains files shared from another project (Osiris.vcxproj).  This can lead to incorrect clean and rebuild behavior.

Then and I can't use AimBot

/sad

first result on google.
also warnings shouldn't prevent you from using features
how did you even encounter this problem?

I don't know


Update service-new-look-where-actions.md

Share and Export menu have changed in the new look

@wim-dp : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@maggiesMSFT : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@maggiesMSFT : Thanks for your contribution! The author(s) have been notified to review your proposed change.

#sign-off


fix: Handle template defined Provider Health Check

Forgot to force enable the default Provider Health Check when the
templates have this value defined.
See also: PSOBAT-2365

This really works this time.
2016-09-15 11:57:25,658 [DEBUG] foremast.pipeline.construct_pipeline_block:check_provider_healthcheck:43 - Template defined Health Check Providers: {'amazon': False}
2016-09-15 11:57:25,659 [INFO] foremast.pipeline.construct_pipeline_block:check_provider_healthcheck:51 - Eureka enabled, enabling default Provider Health Check: Amazon
2016-09-15 11:57:25,659 [DEBUG] foremast.pipeline.construct_pipeline_block:check_provider_healthcheck:56 - Override defined Provider Health Check: False -> True
2016-09-15 11:57:25,659 [INFO] foremast.pipeline.construct_pipeline_block:check_provider_healthcheck:65 - Provider healthchecks: ['Amazon']
2016-09-15 11:57:25,659 [INFO] foremast.pipeline.construct_pipeline_block:construct_pipeline_block:138 - Switching health check type to: EC2


Validate secure gRPC ingress

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

Test name
Commit
Details
Rerun command

prow/pilot-presubmit.sh
2250f738198f624dad021e9dd401d1b8c4a2dd66
link
@istio-testing bazel test this

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

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

Test name
Commit
Details
Rerun command

prow/pilot-presubmit.sh
312cf752e42f68ba104a1fa299dc8166787907fe
link
@istio-testing bazel test this

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

/retest

Gazelle automatically removes unused dependencies.
On Sun, Aug 6, 2017, 4:19 PM Shriram Rajagopalan<EMAIL_ADDRESS>wrote:

@rshriram commented on this pull request.
In cmd/pilot-discovery/BUILD
https://github.com/istio/pilot/pull/997#discussion_r131554997:

@@ -12,7 +12,6 @@ go_library(
"//cmd:go_default_library",
"//model:go_default_library",
"//platform/kube:go_default_library",

   "//platform/consul:go_default_library",

Why remove this?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/istio/pilot/pull/997#pullrequestreview-54546333, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AJGIxkfipqpGrIZgFU2EL9IxVnlKIBeWks5sVknrgaJpZM4Ou2cL
.


Get a page access token

All right, I can get the user access token, but how can I get a page access token?

Answering my own question, you can get the access token for a page that user own from a call to the graph as follow:
final facebookLogin = FacebookLogin();
final resp = await facebookLogin.logIn([
   'pages_show_list',
   'pages_read_engagement',
]);

final graphResponse = await http.get("https://graph.facebook.com/${resp.accessToken.userId}/accounts?access_token=${resp.accessToken.token}");


Add LTE attach purpose guid

@DaniHalfin @mjcaparas @Justinha @greg-lindsay @jaimeo  @AndreaBarr - Can anyone of you assist to check, approve and merge the content of this PR?
I'm tagging you all on this PR since the doc owner shows MariciaAlforque and we were informed that she may no longer be active anymore. If anyone of you knows who is the new author for this article, please do let us know so we can change the author field metadata. Thank you.

@huypub, can you please merge this PR?
Thanks,
@EliotSeattle


#184 rename response=>source, request=>sink

[x] tests pass
[x] recompiled + uglify files
[x] code like so number$.request(1); left alone

Sorry :(

no worries :cry:
:joy:


[Bug]: aboveLayerID and belowLayerID is not working

Mapbox Implementation
Mapbox
Mapbox Version
10.0.11
Platform
Android
@rnmapbox/maps version
10.0.11
Standalone component to reproduce
import React from 'react';
import {View, SafeAreaView} from 'react-native';
import Mapbox from '@rnmapbox/maps';
Mapbox.setWellKnownTileServer('mapbox');

function App() {
  return (
    <SafeAreaView style={{flex: 1}}>
      <View style={{flex: 1}}>
        <View style={{flex: 1}}>
          <Mapbox.MapView style={{flex: 1}}>
            <Mapbox.ShapeSource
              id="layerShape1"
              shape={{
                type: 'FeatureCollection',
                features: [
                  {
                    type: 'Feature',
                    properties: {},
                    geometry: {
                      coordinates: [
                        [
                          [21.45378587617762, -30.927389493460453],
                          [28.45632001172416, -30.927389493460453],
                          [28.45632001172416, -26.785285894952878],
                          [21.45378587617762, -26.785285894952878],
                          [21.45378587617762, -30.927389493460453],
                        ],
                      ],
                      type: 'Polygon',
                    },
                  },
                ],
              }}>
              <Mapbox.FillLayer
                id="layerShape1_1"
                belowLayerID={'layerShape2_1'}
                style={{
                  fillColor: 'red',
                  fillOpacity: 0.5,
                }}
              />
            </Mapbox.ShapeSource>
            <Mapbox.ShapeSource
              id="layerShape2"
              shape={{
                type: 'FeatureCollection',
                features: [
                  {
                    type: 'Feature',
                    properties: {},
                    geometry: {
                      coordinates: [
                        [
                          [20.301493903642296, -25.99586902816941],
                          [20.301493903642296, -30.141598495038032],
                          [27.41504821231871, -30.141598495038032],
                          [27.41504821231871, -25.99586902816941],
                          [20.301493903642296, -25.99586902816941],
                        ],
                      ],
                      type: 'Polygon',
                    },
                  },
                ],
              }}>
              <Mapbox.FillLayer
                aboveLayerID={'layerShape1_1'}
                belowLayerID={'layerShape3_1'}
                id="layerShape2_1"
                style={{
                  fillColor: 'blue',
                  fillOpacity: 0.5,
                }}
              />
            </Mapbox.ShapeSource>

            <Mapbox.ShapeSource
              id="layerShape3"
              shape={{
                type: 'FeatureCollection',
                features: [
                  {
                    type: 'Feature',
                    properties: {},
                    geometry: {
                      coordinates: [
                        [
                          [18.49727785709905, -24.446994796685757],
                          [18.49727785709905, -29.024343444057266],
                          [26.161309407118722, -29.024343444057266],
                          [26.161309407118722, -24.446994796685757],
                          [18.49727785709905, -24.446994796685757],
                        ],
                      ],
                      type: 'Polygon',
                    },
                  },
                ],
              }}>
              <Mapbox.FillLayer
                id="layerShape3_1"
                aboveLayerID={'layerShape2_1'}
                style={{
                  fillColor: 'green',
                  fillOpacity: 0.5,
                }}
              />
            </Mapbox.ShapeSource>

            <Mapbox.Camera
              // minZoomLevel={mapMetaData.minzoom}
              zoomLevel={3}
              centerCoordinate={[21.45378587617762, -30.927389493460453, 5]}
              animationMode="flyTo"
            />
          </Mapbox.MapView>
        </View>
      </View>
    </SafeAreaView>
  );
}

export default App;

Observed behavior and steps to reproduce
in 10.0.10 it is working in android but not in ios. Now 10.0.11 it stopped working in android too. if i place in an order in return also 70% time it is not following order (tested in 10.0.10). Is there any other way i can achieve this.
Expected behavior
to work with by layers defined
Notes / preliminary analysis
No response
Additional links and references
No response

Hi @mfazekas, can you please review it. Our clients rising to many tickets mainly form iOS

Your aboveLayerId and belowLayerId that exactly match the default render order (so they have no effect in this case)
Here is how I understand it :

1_1; 2_1; 3_1 (render order; so, from back to front of screen)
1_1 below 2_1 => 1_1; 2_1; 3_1 (changes nothing)
2_1 above 1_1 => 1_1; 2_1; 3_1 (changes nothing)
2_1 below 3_1 => 1_1; 2_1; 3_1 (changes nothing)
3_1 above 2_1 => 1_1; 2_1; 3_1 (changes nothing)

What order do you want those layers in, what result do you except from front to back of screen for example ?

Hi @paperrin i want to render like
layerShape3   -> top
layerShape2  -> middle
layerShape1. -> bottom
if i don't give above and below. the order is changing

Hi @mfazekas  and @paperrin
Here's what we are trying to achieve:
We want to render all three layers but define the order such that we control what is visible on top. For example, we want to render feature layer on top of a custom raster layer.
It was working fine on Android in the older version (tested in 10.0.6) but now it is not working in latest version and old version also (tested in my repo it has old version 10.0.6 which is not updated since May) . However in the iOS, it's only considering the top layer i.e we can't see the custom raster layer, only the one features layer is visible. I'm attaching the screenshots for comparison.
Version :
"@rnmapbox/maps": "10.0.11",
    "react": "18.2.0",
    "react-native": "0.71.4"

code:
return (
    <SafeAreaView style={{flex: 1}}>
      <View style={{flex: 1}}>
        <View style={{flex: 1}}>
          <Mapbox.MapView style={{flex: 1}}>
            <Mapbox.ShapeSource
              id="layerShape1"
              shape={{
                type: 'FeatureCollection',
                features: [
                  {
                    type: 'Feature',
                    properties: {},
                    geometry: {
                      coordinates: [
                        [
                          [21.45378587617762, -30.927389493460453],
                          [28.45632001172416, -30.927389493460453],
                          [28.45632001172416, -26.785285894952878],
                          [21.45378587617762, -26.785285894952878],
                          [21.45378587617762, -30.927389493460453],
                        ],
                      ],
                      type: 'Polygon',
                    },
                  },
                ],
              }}>
              <Mapbox.FillLayer
                id="layerShape11"
                belowLayerID={'layerShape21'}
                style={{
                  fillColor: 'red',
                  fillOpacity: 0.5,
                }}
              />
            </Mapbox.ShapeSource>
            <Mapbox.ShapeSource
              id="layerShape2"
              shape={{
                type: 'FeatureCollection',
                features: [
                  {
                    type: 'Feature',
                    properties: {},
                    geometry: {
                      coordinates: [
                        [
                          [20.301493903642296, -25.99586902816941],
                          [20.301493903642296, -30.141598495038032],
                          [27.41504821231871, -30.141598495038032],
                          [27.41504821231871, -25.99586902816941],
                          [20.301493903642296, -25.99586902816941],
                        ],
                      ],
                      type: 'Polygon',
                    },
                  },
                ],
              }}>
              <Mapbox.FillLayer
                aboveLayerID={'layerShape11'}
                belowLayerID={'layerShape31'}
                id="layerShape21"
                style={{
                  fillColor: 'blue',
                  fillOpacity: 0.5,
                }}
              />
            </Mapbox.ShapeSource>

            <Mapbox.ShapeSource
              id="layerShape3"
              shape={{
                type: 'FeatureCollection',
                features: [
                  {
                    type: 'Feature',
                    properties: {},
                    geometry: {
                      coordinates: [
                        [
                          [18.49727785709905, -24.446994796685757],
                          [18.49727785709905, -29.024343444057266],
                          [26.161309407118722, -29.024343444057266],
                          [26.161309407118722, -24.446994796685757],
                          [18.49727785709905, -24.446994796685757],
                        ],
                      ],
                      type: 'Polygon',
                    },
                  },
                ],
              }}>
              <Mapbox.FillLayer
                id="layerShape31"
                aboveLayerID={'layerShape21'}
                style={{
                  fillColor: 'green',
                  fillOpacity: 0.5,
                }}
              />
            </Mapbox.ShapeSource>

            <Mapbox.Camera
              // minZoomLevel={mapMetaData.minzoom}
              zoomLevel={3}
              centerCoordinate={[21.45378587617762, -30.927389493460453, 5]}
              animationMode="flyTo"
            />
          </Mapbox.MapView>
        </View>
      </View>
    </SafeAreaView>
  );

return (
    <SafeAreaView style={{flex: 1}}>
      <View style={{flex: 1}}>
        <View style={{flex: 1}}>
          <Mapbox.MapView style={{flex: 1}}>
            <Mapbox.ShapeSource
              id="layerShape1"
              shape={{
                type: 'FeatureCollection',
                features: [
                  {
                    type: 'Feature',
                    properties: {},
                    geometry: {
                      coordinates: [
                        [
                          [21.45378587617762, -30.927389493460453],
                          [28.45632001172416, -30.927389493460453],
                          [28.45632001172416, -26.785285894952878],
                          [21.45378587617762, -26.785285894952878],
                          [21.45378587617762, -30.927389493460453],
                        ],
                      ],
                      type: 'Polygon',
                    },
                  },
                ],
              }}>
              <Mapbox.FillLayer
                id="layerShape11"
                belowLayerID={'layerShape21'}    ----------> removing this
                style={{
                  fillColor: 'red',
                  fillOpacity: 0.5,
                }}
              />
            </Mapbox.ShapeSource>
            <Mapbox.ShapeSource
              id="layerShape2"
              shape={{
                type: 'FeatureCollection',
                features: [
                  {
                    type: 'Feature',
                    properties: {},
                    geometry: {
                      coordinates: [
                        [
                          [20.301493903642296, -25.99586902816941],
                          [20.301493903642296, -30.141598495038032],
                          [27.41504821231871, -30.141598495038032],
                          [27.41504821231871, -25.99586902816941],
                          [20.301493903642296, -25.99586902816941],
                        ],
                      ],
                      type: 'Polygon',
                    },
                  },
                ],
              }}>
              <Mapbox.FillLayer
                aboveLayerID={'layerShape11'}
                belowLayerID={'layerShape31'}
                id="layerShape21"
                style={{
                  fillColor: 'blue',
                  fillOpacity: 0.5,
                }}
              />
            </Mapbox.ShapeSource>

            <Mapbox.ShapeSource
              id="layerShape3"
              shape={{
                type: 'FeatureCollection',
                features: [
                  {
                    type: 'Feature',
                    properties: {},
                    geometry: {
                      coordinates: [
                        [
                          [18.49727785709905, -24.446994796685757],
                          [18.49727785709905, -29.024343444057266],
                          [26.161309407118722, -29.024343444057266],
                          [26.161309407118722, -24.446994796685757],
                          [18.49727785709905, -24.446994796685757],
                        ],
                      ],
                      type: 'Polygon',
                    },
                  },
                ],
              }}>
              <Mapbox.FillLayer
                id="layerShape31"
                aboveLayerID={'layerShape21'}
                style={{
                  fillColor: 'green',
                  fillOpacity: 0.5,
                }}
              />
            </Mapbox.ShapeSource>

            <Mapbox.Camera
              // minZoomLevel={mapMetaData.minzoom}
              zoomLevel={3}
              centerCoordinate={[21.45378587617762, -30.927389493460453, 5]}
              animationMode="flyTo"
            />
          </Mapbox.MapView>
        </View>
      </View>
    </SafeAreaView>
  );

@somasekharkakarla first you don't want to have both above and below layer id as only one of them is considered, we'll add a warning for that use.
second you don't want to make a cycle of with above/below layer id's as before adding a layer it waits for the layer with after or below to be added. But if there is a cycle none of the layers will be added in the end


Makes creation of abstract and doi columns more modular

As of now, the doi column is created inside the CreateOutput method as follows:
https://github.com/popbr/abstract_doi_finder/blob/7180fceba3880188879aa395b2a2f7da7fda4e1a/abstract_doi_finder/src/main/java/popbr/AbstractDoiFinder.java#L157-L168
We could

have a method AddCol(XSSFWorkbook inputWB, String column) that creates a column column at the (say) right of the title column if it's not here already, and shift all the rest,
call this method twice, for doi and abstract.

I have made an attempt to make this specific method more modular. However, I did not base it off of the title column (or any other column), yet. I plan on working on this now, I just wanted to verify that the method worked. Here is the specific commit where it worked: (https://github.com/popbr/abstract_doi_finder/commit/9618cb816090f67a7f55aee2e6466477911538ad)

I have tested it and it seems to work as intended. Even more modularity could help (cf. https://github.com/popbr/abstract_doi_finder/issues/12 ), but it does the job as of now.


Typo in VS HTML designer intelli-sense

I have no idea where this bug should go so I'm putting it here and someone can move it to the correct place.
I noticed this typo for the HTML underline tag: http://i.imgur.com/3mKpE9c.png

@mayurid @barrytang

I opened a VS bug to track.

Note that we now have a public Tooling repo that you can open issues in.

@madskristensen's comment - This is a ReSharper issue, not VSs.


Admin improvements

Full details: https://github.com/Koed00/django-q/pull/605

Coverage decreased (-0.05%) to 90.24% when pulling 044265db851afc25991e47454ff2a10e9d690775 on admin_improvements into 4aa6325ae888147d629d6bcc81c9bfdc8642f6b2 on master.


look into reporting

in #16, I moved the reporting to be after acquiring a permit, since this better reflects when file downloads actually start, rather than when the async jobs are spawned. However, I'm not sure this maintains ordering / is doing the right thing.
I'm now seeing reporting like this:
Loaded 94784 rows in total
Starting accession 1894/94784 (2%)
Starting accession 947/94784 (1%)
Starting accession 1894/94784 (2%)

the error handling fix for v0.2.2 seems to have fixed any issues here


Robot name

Solution to robot_name exercise from LevelUp.

Good work!  A few comments throughout, but nothing major.  You're done with this one.


Version: Comparison of NumericToken and StringToken

Please note we will close your issue without comment if you delete, do not read or do not fill out the issue checklist below and provide ALL the requested information. If you repeatedly fail to use the issue template, we will block you from ever submitting issues to Homebrew again.

[x] ran brew update and can still reproduce the problem?
[x] ran brew doctor, fixed all issues and can still reproduce the problem?
[x] ran brew config and brew doctor and included their output with your issue?

What you were trying to do (and why)
When running brew livecheck cataclysm, the newest version is reported as 0.9, though this is older than the current version of 0.D. This formula uses a version scheme where versions go 0-9 and then roll into capital letters (A, B, etc.), as seen on the releases page. I'm not sure whether they're using hex numbering (0-9, A-F) or if it's A-Z but I guess time will tell.
What happened (include command output)

Command output

Trying with url https://github.com/CleverRaven/Cataclysm-DDA.git
Possible git repo detected at https://github.com/CleverRaven/Cataclysm-DDA.git
0.1 => #<Version:0x00007f8567426370 @version="0.1", @tokens=[#<Version::NumericToken 0>, #<Version::NumericToken 1>]>
0.2 => #<Version:0x00007f8567426190 @version="0.2", @tokens=[#<Version::NumericToken 0>, #<Version::NumericToken 2>]>
0.3 => #<Version:0x00007f8567425fd8 @version="0.3", @tokens=[#<Version::NumericToken 0>, #<Version::NumericToken 3>]>
0.4 => #<Version:0x00007f8567425d80 @version="0.4", @tokens=[#<Version::NumericToken 0>, #<Version::NumericToken 4>]>
0.5 => #<Version:0x00007f8567425c90 @version="0.5", @tokens=[#<Version::NumericToken 0>, #<Version::NumericToken 5>]>
0.6 => #<Version:0x00007f8567425b00 @version="0.6", @tokens=[#<Version::NumericToken 0>, #<Version::NumericToken 6>]>
0.7 => #<Version:0x00007f8567425948 @version="0.7", @tokens=[#<Version::NumericToken 0>, #<Version::NumericToken 7>]>
0.7.1 => #<Version:0x00007f8567425718 @version="0.7.1", @tokens=[#<Version::NumericToken 0>, #<Version::NumericToken 7>, #<Version::NumericToken 1>]>
0.8 => #<Version:0x00007f8567425560 @version="0.8", @tokens=[#<Version::NumericToken 0>, #<Version::NumericToken 8>]>
0.9 => #<Version:0x00007f85674253a8 @version="0.9", @tokens=[#<Version::NumericToken 0>, #<Version::NumericToken 9>]>
0.A => #<Version:0x00007f85674252e0 @version="0.A", @tokens=[#<Version::NumericToken 0>, #<Version::StringToken "A">]>
0.B => #<Version:0x00007f8567425218 @version="0.B", @tokens=[#<Version::NumericToken 0>, #<Version::StringToken "B">]>
0.C => #<Version:0x00007f8567425150 @version="0.C", @tokens=[#<Version::NumericToken 0>, #<Version::StringToken "C">]>
0.D => #<Version:0x00007f8567425088 @version="0.D", @tokens=[#<Version::NumericToken 0>, #<Version::StringToken "D">]>
cataclysm : 0.D ==> 0.9

What you expected to happen
Version 0.D should be interpreted as the newest version (since D > 9).
Step-by-step reproduction instructions (by running brew commands)
brew livecheck cataclysm
Output of brew config and brew doctor commands

HOMEBREW_VERSION: 2.2.10-64-g4d5424c
ORIGIN: https://github.com/Homebrew/brew
HEAD: 4d5424c7faaa53313f08fd67f2a861036cd3cd55
Last commit: 9 hours ago
Core tap ORIGIN: https://github.com/Homebrew/homebrew-core
Core tap HEAD: 71079f20cf15b162588b007e7677328f607754e2
Core tap last commit: 4 hours ago
HOMEBREW_PREFIX: /usr/local
HOMEBREW_DEV_CMD_RUN: 1
HOMEBREW_NO_ANALYTICS_THIS_RUN: 1
CPU: dodeca-core 64-bit kabylake
Homebrew Ruby: 2.6.3 => /System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/bin/ruby
Clang: 11.0 build 1100
Git: 2.25.1 => /usr/local/bin/git
Curl: 7.64.1 => /usr/bin/curl
macOS: 10.15.3-x86_64
CLT: N/A
Xcode: 11.3.1

General Comments
From what I've seen in trying to resolve this issue, I imagine this is related to the comparison that happens in Version between NumericToken and StringToken. I've tinkered with this to see if I could resolve the issue but haven't had any luck so far.

Is this not a brew livecheck issue?

I previously started by troubleshooting it in Homebrew/homebrew-livecheck but livecheck is only doing Version comparisons. The main areas of interest in livecheck are:

heuristic.rb's version_heuristic(), where the highest identified Version is returned using match_version_map.values.max
livecheck.rb's print_latest_version(), where the current and latest versions are compared

The implementation details of how two Versions are compared is something that's handled in version.rb and would occur outside of livecheck as well. This ultimately arises due to how comparisons are handled between NumericToken (e.g., 9) and StringToken (e.g., "D").
I worked on this some more and found that modifying the conditions in the loop where token comparison occurs in Version.<=> can achieve the desired effect:
diff --git a/Library/Homebrew/version.rb b/Library/Homebrew/version.rb
index 27116a243e94a30c138070333a05013067e53791..8b55b5bbdb16ac4ff187ce0f783344d22a1b7b7d 100644
--- a/Library/Homebrew/version.rb
+++ b/Library/Homebrew/version.rb
@@ -412,6 +412,10 @@ class Version
         next
       elsif a.numeric? && b.numeric?
         return a <=> b
+      elsif a.numeric? && b.is_a?(StringToken)
+        return -1
+      elsif a.is_a?(StringToken) && b.numeric?
+        return 1
       elsif a.numeric?
         return 1 if a > NULL_TOKEN

This basically means "If we're comparing a numeric token and a StringToken, always treat the StringToken as greater". I imagine we may want to approach this in a more intelligent manner but hopefully this will further the discussion.

@samford A patch like that makes sense to me! Could you submit a PR?

If it's fine with you, I would like to see how this change shakes out when I do my next full livecheck run tonight (comparing it to yesterday's output). I usually compare output between runs (with/without a change) before creating PRs that can potentially affect the checks for all formulae (or a large number of them). It helps to confirm that the fix is working as expected and that we're not introducing issues into other formulae.
Once I've gone through the output I'll gladly create a PR and link it to this issue.

Works for me, thanks 👍

After looking at the livecheck output, I'm going to have to think a little more about how to best address this.
The big blocker right now is that the Sourceforge strategy in the livecheck heuristic returns a lot of files versions, so they're always interpreted as the newest version with this change. Without the change, only 121 formulae checks were giving files as the newest version. With the change, the number is 258.
There are also some other individual issues that will need to be accounted for (e.g., 3.10-gtk3 being given as newer than 3.10.1-gtk3 with the audacious formula, due to "gtk3" always being greater than 1).
This can be mitigated to some extent through improving the Sourceforge strategy and/or restricting version matching for formulae using livecheckables regexes. However, I'm not yet sure whether the issue can be totally resolved in this manner. In the end, it may require changes in livecheck as well as approaching the version comparison in a less heavy-handed manner.
I'm going to hold off on creating a PR for this until livecheck and/or the version comparison is in a state where it wouldn't break any checks. I'm temporarily avoiding adding large numbers of livecheckables until I've finished implementing all the forthcoming features, so I likely won't get to this for a good while.

I'm going to hold off on creating a PR for this until livecheck and/or the version comparison is in a state where it wouldn't break any checks. I'm temporarily avoiding adding large numbers of livecheckables until I've finished implementing all the forthcoming features, so I likely won't get to this for a good while.

Ok, given this: let's close this out for now. Happy to review a PR when it appears. Thanks for the explanation!


[Documentation] Wrong documentation for TypeORM

Informations

Type
Version

Bug
4.30.1

Description
A few sentences describing the overall goals of the issue.
In the typeorm documentation, there is an example which says you should use the AfterInit interface, but it does not exist:
http://tsed.io/#/tutorials/typeorm?id=typeormservice

You've right, it's AfterRoutesInit XD

😄
is AfterRoutesInit good?
will this happen before the server is "ready"? since I think that once the routes are loaded, the service should already be provisioned.

The lifecycle is described here :) http://tsed.io/#/docs/services/lifecycle-hooks
If isn't clear, tell me ;)

But the picture src are broken...

maybe it can also be fixed 😄

Yep, the new version of website is almost done. I'll fix that with this new version ;)


DBZ-7845 [FEAT] adds reduced buffer implementation and test cases

adds reduced buffer
created interface Buffer
test cases for reduced buffer
change log level  in EnumType.java as it is happening for every record, in our case loki logs are this log line

seems like checkstyle issue, looking into it,  team any handy command that i can run to fix checkstyle, will be helpful

thanks for typo @Naros , i was pushing same

@gaurav7261 Applied, thanks a lot!


Add a CONTRIBUTING doc to this repo

We need a CONTRIBUTING doc with instructions for potential cookiecutter-pypackage contributors.

i'm working on it

Hi @zaro0508, the following information would be helpful to add in the CONTRIBUTING doc for contributors that use MaxOS.
I got an error trying to install the cryptography dependency on MacOS el capitan, to run the tests:
pip install cryptography
and I solve it installing openssl and running a ln:
brew install openssl
cd /usr/local/include
ln -s ../opt/openssl/include/openssl .
For further information:
https://solitum.net/openssl-os-x-el-capitan-and-brew/

This is done. I will open a separate issue for adding the openssl part to CONTRIBUTING.rst.


how to redeem mooncoin on mooncoincore wallet

i downloaded mooncoincore wallet for windows 64 bit and purchased mooncoin on bleutreade.com and withdrew the tokens to an address in my wallet.  nothing ever arrived.   it is showing that they were successfully withdrawn from bleutrade to my address, but not showing up in my wallet.  i have tried restarting the computer several times.  i looked up the txid and it shows the blockchain transaction but says the coins are not redeemed.  i have no clue how to redeem the coins.  i hate these little wallets.  there are always issues like this.  i already lost .5 million doge coins.  i would appreciate if someone could offer some advice to resolve this issue.  thanks

This is an issue for bleutreade.com support.


fix(NumberInput): add button type and disabled

Add button type to arrow button to prevent a form from being submitted
when it is clicked

Disable the arrow buttons when the NumberInput is disabled just in
case

Fixes #358

Can we also bump the version of carbon-components to 8.1.11? That way the disabled styles are bundled in. Otherwise, looks good 👍 ✅

the peer is set to "carbon-components": "^8.0.0", which would update to that version. updated


Scala GMM and EncEval GMM don't give the same results

I'm trying to compare the results of the two implementations of GMM estimator in keystoneml and they are very differents. As sample data, I use the gmm_data.txt available in spark source.
The EncEval version give results similar to scikit-learn GMM.
import nodes.learning.GaussianMixtureModelEstimator
import nodes.learning.external.{GaussianMixtureModelEstimator => EGMM}
import org.apache.spark.mllib.clustering.{GaussianMixtureModel => SGMM, GaussianMixture}
import org.apache.spark.mllib.linalg.Vectors
import org.apache.spark.{SparkConf, SparkContext}
import breeze.linalg.{DenseVector => BDV}

object GMM {

  def main (args: Array[String]) {
    val conf = new SparkConf()
      .setAppName("Extract Face Features")
      .setIfMissing("spark.master", "local[4]")
    val sc = new SparkContext(conf)
    val data = sc.textFile("spark/data/mllib/gmm_data.txt")
    val parsedData = data.map(s => BDV[Double](s.trim.split(' ').map(_.toDouble))).cache()

    val gmmEstimator = GaussianMixtureModelEstimator(2,
        maxIterations = 100000,stopTolerance = 0d,
        smallVarianceThreshold = 0d)
    val gmmModel = gmmEstimator.fit(parsedData)

    val gmmEstimator2 = new EGMM(2)
    val gmmModel2 = gmmEstimator2.fit(parsedData)

    println("===================")
    println(gmmModel.means)
    println(gmmModel2.means)
    println("-------")
    println(gmmModel.variances)
    println(gmmModel2.variances)
    println("-----------")
    println(gmmModel.weights)
    println(gmmModel2.weights)

    sc.stop()
  }
}

Thanks for the bug report and code example - very helpful!
There are a few differences between the two implementations, one important one is the initialization strategy. The scala version is initialized via KMeans++, while the EncEval library version is initialized uniformly at random in data domain. A quick look also inidcates that the scala version actually achieves a better log-likelihood near the end of its iterations. -3.609 for EncEval vs. -3.564 for the Scala version.

Hey there - @tomerk and I took a look at this today.

Allowing the scala GMM to be initialized with the same method as the EncEval GMM has been enabled by #201 . Additionally, we've included a new unit test on the "+" dataset to ensure it is actually doing the right thing when the data really are a mixture of (diagonal-covariance) Gaussians.
I'm going to close this but feel free to reopen if you don't find the new initialization satisfactory.


brook: 20200201 -> 20210701

Motivation for this change
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
21.11 Release Notes (or backporting 21.05 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.

Result of nixpkgs-review pr 135113 at 960c5f47 run on aarch64-linux 1

1 package built successfully:

brook

1 suggestion:

warning: unclear-gpl
gpl3 is a deprecated license, please check if project uses gpl3Plus or gpl3Only and change meta.license accordingly.
Near pkgs/tools/networking/brook/default.nix:19:5:
   |
19 |     license = with licenses; [ gpl3 ];
   |     ^

Hi @marsam, I think it is ready to be merged. Thank you!


Fix CodeGen V2 for zero-length array

Summary
Fix issue #295

Replace the recursive validate_size template with a non-recursive one, making CodeGen compile
Process zero-length array as containers, so no object size is left unread in the data buffer
Enable the zero-length array test

Is it ok to process zero-length array as container?
I had to modify the test's results to all 0 sizes. Is this the behavior expected? Or should it report an exclusive size of 1 for the Foo struct?
Test plan
The example provided in #295 now passes successfully and has been enabled in the integration tests.
$ build/test/integration/integration_test_runner --gtest_filter='OidIntegration.arrays_member_int0' --verbose --preserve --enable-feature type-graph

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Comparison is base (cbeafba) 62.38% compared to head (cff773b) 62.41%.

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #453      +/-   ##
==========================================
+ Coverage   62.38%   62.41%   +0.02%
==========================================
  Files         123      123
  Lines       12007    12006       -1
  Branches     1956     1955       -1
==========================================
+ Hits         7491     7493       +2
+ Misses       3571     3570       -1
+ Partials      945      943       -2

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Port the NanoVG demo to WebGL

It'd be neat if the NanoVG demo could run in the browser, to show how to use Pathfinder as a canvas renderer on the Web.

After looking at it, the main problem will be fonts.
My WebGL demos all use a pure rust font parser and avoids the canvas API.
One approach could be to use a different CanvasFontContext on WebGL.

CanvasFontContext::from_system_source() will definitly not be avaible.


Grafana-Watcher import of dashboards exported via UI leads to nil pointer dereference

What did you do?
I exported Grafana dashboards via the web UI, mounted them via a k8s configmap to the grafana-watcher and let grafana-watcher import the dashbords.
What did you expect to see?
I expected the dashbaords to be imported to Grafana
What did you see instead? Under which circumstances?
I realized this leads to an server side error on Grafana and the grafana-watcher received 500 from the Grafana API
Environment
Grafana 4.4.3
grafana-watcher 0.0.8
Solution
The used Grafana API to import dashboards (/api/dashboards/import), which isn't documented, expects the dashboard JSON to be wrapped in {dashboard: {}}. This wrapper is missing, when exporting dashboards via the web UI. The grafana-watcher should check for this syntax and optionally add this wrapper automatically.
Example:
Via web ui exported dashboard JSON, which leads to exception if imported via /api/dashboards/import (API used by grafana-watcher) to Grafana:
{"id":null,"rows":[{"collapse":false,"height":"250px","panels":[],"repeat":null,"repeatIteration":null,"repeatRowId":null,"showTitle":false,"title":"Dashboard Row","titleSize":"h6"}],"schemaVersion":6,"title":"New dashboard Copy","version":0}

Manually modified web ui exported JSON, which gets imported correctly:
{"dashboard": {"id":null,"rows":[{"collapse":false,"height":"250px","panels":[],"repeat":null,"repeatIteration":null,"repeatRowId":null,"showTitle":false,"title":"Dashboard Row","titleSize":"h6"}],"schemaVersion":6,"title":"New dashboard Copy","version":0}}

When exporting a dashboard from the UI, you need to drop it into the assets/grafana/ directory and then run the make generate make target, it will take care of wrapping the exported blob correctly as you described and generate a ConfigMap manifest accordingly.
Let us know or feel free to contribute to this document:
https://github.com/coreos/prometheus-operator/blob/master/contrib/kube-prometheus/docs/developing-alerts-and-dashboards.md
If the content was not clear enough :slightly_smiling_face: . Or if you didn't see it, let us know how you think we could highlight it more so people find it :slightly_smiling_face: .

Thank you @brancz for the fast reply! The problem was, that we are not using the whole prometheus-operator ecosystem, but only the grafana-watcher docker-image, which most probably is not what it is designed for.
Would you accept an PR adding a README to https://github.com/coreos/prometheus-operator/tree/master/contrib/grafana-watcher with some basic information about just this part of the prometheus-operator? This would have helped me a lot.

Definitely! I've been meaning to add a README.md to the grafana-watcher, but haven't gotten around doing it. If you are up for it, it would be highly appreciated if you could write up one :slightly_smiling_face: .

PR: https://github.com/coreos/prometheus-operator/pull/656


[Feature]  Unicode Keyword

Is your feature request related to a problem? Please describe.
Hello, I would like to suggest a feature that allows Unicode keywords.
Now, only English keywords trigger Combos.
Then, if someone uses other languages in keyboards, the user should switch their input language to English to use Beeftext Combos.
Therefore, I suggest allowing Unicode keywords to trigger Combos.
Describe the solution you'd like
As Is: Only English keywords trigger Combos.
ex) gm| -> 'Good morning!'
To Be: Any Unicode keywords trigger Combos.
ex) ㅈㅇ| -> '좋은 아침입니다!'
Describe alternatives you've considered
Additional context

Hi. Thank you for reporting. Normally Beeftext should work with Unicode keywords. Unfortunately I cannot check every input method available. I'll have a look.

@dorajistyle
I found this program useful, so I'm testing it a little bit and felt the same need.
If you put "whgdms" as a keyword, which corresponds to "좋은"
(typing English characters based on Hangul character positions on the keyboard),
and then you type '좋은' in Hangul typing mode, it does the job magically.
I guess this is probably because the Bt substitutes based on the scan code entered on the keyboard, not on the characters you typed.
The solution adressing the root cause of Unicode input would be decrypting IME's high level output rather than the scan code of the keyboard.
Due to the input method characteristics of CJK characters, it might be difficult to implement I guess.


install rMETL in 2023

An executable environment:
python=2.7
pip=19.0
cython=0.26
ngmlr=0.2.6
pysam=0.20.0
cigar=0.1.3
biopython=1.76

Note that pip(>=21.0) doesn't support python2 anymore, pysam has removed python2.X since version 0.21(the latest). I found similar problems when installing biopython, and I changed to another version that had closed released time to rMETL, and that was 1.76.

Note that pip(>=21.0) doesn't support python2 anymore, pysam has removed python2.X since version 0.21(the latest) as well. Besides, I found similar problems when installing biopython, and I changed to another version(1.76) that had closed released time compared to rMETL.

Besides, rMETL used "get_index_statistics()" of pysam, which was added since 0.15.0, so even if 0.8.0 supports python2, you may found runtime errors as well.

my instructions(I already have samtools):
conda create -n rMETLenv python=2.7
conda activate rMETLenv
pip install pip==19.0
pip install cython
pip install pysam==0.19.0
pip install Biopython==1.76
conda install -c bioconda ngmlr
pip install cigar
#change current dir to rMETL/
python setup.py install

Thanks @120L021101,
Now I have mentioned this in the README to inform other users.
Many thanks for your work.
Tao


"?pretty=true" does not work

When I change
curl "http://XXX:YYY@ZZZ:9200/_searchguard/authinfo"
to
curl "http://XXX:YYY@ZZZ:9200/_searchguard/authinfo?pretty=true"
text stay in one line. But in other queries (e.g. curl "http://XXX:YYY@ZZZ:9200/_cluster/health?pretty=true"), responses look pretty
ES 5.1.1
SG 5.1.1-10 from https://oss.sonatype.org/content/repositories/snapshots/com/floragunn/search-guard-5/5.1.1-10-SNAPSHOT/search-guard-5-5.1.1-10-20161218.194423-1.zip

fixed


Join discord of 3d modeling

I want to add this model to my discord whats the simplest way to do it?

don't, use it locally inside blender really easy to use and its got new features like prompt batching and batching to generate multiple models https://devbud.gumroad.com/l/Shap-e


init-max-area with an aspect-ratio lower than 1 not working

If the init-max-area binding is set to true and the provided aspect-ratio in lower than 1 (portrait area required), the init-max-area is not applied and the crop area is positionned in the center not reaching neither the height nor width.
I tried different things but nothing is working.

Up !

create codepen, I will check

CodePen : https://codepen.io/anon/pen/EOWwGv
The behavior I am describing is only true if you upload a portrait image (height greater than width).

ok, I see, i believe I know how to solve that. Will try to check it within few next days. You can also check if you want to.

Awesome ! Thank you !
I will check when you make the PR !
Btw, do you need help for maintaining the project ?

Well, I don't have much time for public repos currently. Any PR is accepted if it not brake any of mine codepen.


Bug Report: App Veyor says Acess Denied

Please check for duplicates, similar issues or closed issues with the same problem, as well performing simple troubleshooting steps (such as deleting the export folder if it's an issue with compiling, reinstalling Kade Engine) before submitting an issue.
If you are playing a downloaded version of the game, what operating system are you using?
Windows (x86), Windows (x86_64), Linux, or macOS? Specify below.
Linux x64
What version of the game are you using? Look in the bottom left corner of the main menu.
Didn't get to download
Have you identified any steps to reproduce the bug? If so, please describe them below. Use images if possible.
Press the Linux download from the AppVeyor Realese
Please describe your issue. Provide extensive detail and images if possible.
When I try to download the linux version trough AppVeyor it gives me an error:

But if I go to the windows AppVeyor page it works

who is weird because it was realesed yesterday

Oops I think I just fixed that.

so kade closed this for no reason
the actual problem is appveyor won't let him make the linux project for some reason, you can download linux builds from here while that's being resolved (as of posting this comment a build is running so you might need to wait for it to finish)

oh wait I actually just read this wrong lol. but yeah for now you can go to daniel's page.

It seems once again this is broken

Tough differently I should've not reopened this should've just made new issue

It seems once again this is broken

CI is now on GitHub actions, click the "actions" tab at the top of this page