multi project with sbt 0.13.7 failed

[info] [error] (module1/*:update) sbt.ResolveException: download failed: javax.jms#jms;1.1!jms.jar
[info] [error] download failed: com.sun.jdmk#jmxtools;1.2.1!jmxtools.jar
[info] [error] download failed: com.sun.jmx#jmxri;1.2.1!jmxri.jar
[info] [error] Total time: 13 s, completed 2015-3-6 23:54:36

[info] [warn] 	::::::::::::::::::::::::::::::::::::::::::::::
[info] [warn] 	::              FAILED DOWNLOADS            ::
[info] [warn] 	:: ^ see resolution messages for details  ^ ::
[info] [warn] 	::::::::::::::::::::::::::::::::::::::::::::::
[info] [warn] 	:: javax.jms#jms;1.1!jms.jar
[info] [warn] 	:: com.sun.jdmk#jmxtools;1.2.1!jmxtools.jar
[info] [warn] 	:: com.sun.jmx#jmxri;1.2.1!jmxri.jar
[info] [warn] 	::::::::::::::::::::::::::::::::::::::::::::::

can't download com.sun.jdmk#jmxtools;1.2.1!jmxtools.jar

seems like #7 , because log4j 1.2.15 dependency jms, jmxtools, jmxri

it's not a bug, sbt update task need to resolve dependency before, and zookeeper-3.4.5 depend log4j-1.2.15, so as #7


Nick Volynkin: Blacklist mobile-version.ru

Nick Volynkin requests the blacklist of the following website(s):

mobile-version.ru - MS search

mobile-version.ru has been seen in 0 true positives, 0 false positives, and 0 NAAs.

http://chat.stackexchange.com/transcript/message/34027421#34027421


Can't propose block

Non-static API calls are not recognized:
curl -X POST --data '{
                                   "jsonrpc": "2.0",
                                   "method": "timestampvm.proposeBlock",
                                   "params":{
                                       "data":"SkB92YpWm4Q2iPnLGCuDPZPgUQMxajqQQuz91oi3xD984f8r"
                                   },
                                   "id": 1
                               }' -H 'content-type:application/json;' <IP_ADDRESS>:9650/ext/vm/timestampvm
{"jsonrpc":"2.0","error":{"code":-32000,"message":"rpc: can't find method \"timestampvm.ProposeBlock\"","data":null},"id":1}

Static calls work fine:
curl -X POST --data '{
                                   "jsonrpc": "2.0",
                                   "method": "timestampvm.encode",
                                   "params":{
                                       "data":"SkB92YpWm4Q2iPnLGCuDPZPgUQMxajqQQuz91oi3xD984f8r"
                                   },
                                   "id": 1
                               }' -H 'content-type:application/json;' <IP_ADDRESS>:9650/ext/vm/timestampvm
{"jsonrpc":"2.0","result":{"bytes":"M2NcATdFX63NpvNFE5pRgLXY1DLgo7oLVNKYNzTVEswz6YEALQ5EvzXeoR6sqzBJhjUo84t","encoding":"cb58"},"id":1}

The tutorial shows to use an /ext/bc address (typo?), but I've tried all the endpoints listed by the node on startup and none recognize the method. From the tutorial:
curl -X POST --data '{
    "jsonrpc": "2.0",
    "method": "timestampvm.proposeBlock",
    "params":{
        "data":"SkB92YpWm4Q2iPnLGCuDPZPgUQMxajqQQuz91oi3xD984f8r"
    },
    "id": 1
}' -H 'content-type:application/json;' <IP_ADDRESS>:9650/ext/bc/sw813hGSWH8pdU9uzaYy9fCtYFfY7AjDd2c9rm64SbApnvjmk

If that's not a typo, it would help to mention where to find the right endpoint vs. just using a hardcoded value in the sample call, i.e., sw813hGSWH8pdU9uzaYy9fCtYFfY7AjDd2c9rm64SbApnvjmk.

This is not a static API. The sw813hGSWH8pdU9uzaYy9fCtYFfY7AjDd2c9rm64SbApnvjmk is blockchain ID, so it can be different on your end. This is the same ID when you create your blockchain with platform.createBlockchain. See: Create Custom Blockchain .
We're also updating the doc to prevent any confusion about that. Thanks for feedback!

Got it, that makes sense 👍
Following the Custom Blockchain tutorial, whenever I create a subnet against a local test net, the P chain seems to crash/go unhealthy with:
DEBUG[09-10|15:37:42] avalanchego/health/service.go#95: starting to run P
ERROR[09-10|15:32:43] avalanchego/health/service.go#102: failed to encode "P" when it was failing due to: json: unsupported value: NaN

I'll keep poking around and raise the issue in a more appropriate place if needed. Thanks for the help.

Feel free to join our discord channel in: chat.avalabs.org


nimforum as a solution

https://github.com/nim-lang/nimforum

the one running forum.nim-lang.org
pretty lightweight
sqlite based so no server hassle
minimal, and discourse-ish feeling

should be suggested a vdc solution

should be suggested a vdc solution


Fix a small bug in the integrate function

Fix a small bug in the integrate function, where xy must be arrays

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 2 (0.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.09%) to 78.975%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

appletree/utils.py
0
2
0.0%

Totals

Change from base Build<PHONE_NUMBER>:
-0.09%

Covered Lines:
1356

Relevant Lines:
1717

💛  - Coveralls


GEN-XSS clober requests

If a payload created from GEN-XSS is used in multiple requests, they end up clobbering each other. Should make separate tracers rows for each request. This might involve UI changes so that events get mapped to hosts and payload rather than just payload.

Fixed in 02d8f0e5923774693fcb12240b5faef0999335c1

I think this is still a problem. While it accepts multi request now. I did not update the logic in proxy to handle it.

I'm going to change it in the plugin version.

Closed by 7c7413dec0d2465758d3883e6c704592c5ac06bc


Python version

Thanks for making this library!
I was just testing this out in a Python 3.9.15 environment and ran into this sort of error:
File [~/miniconda3/lib/python3.9/site-packages/castep_outputs/castep_outputs_main.py:65](https://file+.vscode-resource.vscode-cdn.net/home/jks/coding/castep_outputs/docs/~/miniconda3/lib/python3.9/site-packages/castep_outputs/castep_outputs_main.py:65), in parse_single(in_file, parser, out_format, loglevel, testing)
     63     data = parser(in_file)
     64 else:
---> 65     with fileinput.FileInput(in_file, mode='r', encoding='utf-8') as file:
     66         data = parser(file)
     68 if out_format == "json" or testing:

TypeError: __init__() got an unexpected keyword argument 'encoding'

I think this is because the encoding argument was added from Python 3.10 onwards.
Proposed fix: Either bump the Python version requirement to 3.10 (in the setup.py it asks for 3.8 or up), or remove 3.10 - specific things.
Cheers

Ah! You're right, I hadn't noticed, don't particularly want to bump to 3.10 just for that. Will get that updated.
Besides that does it do the sort of thing that you want or has it still not managed to run yet?
Jacob

From: Kane Shenton @.>
Sent: 09 August 2023 15:37
To: oerc0122/castep_outputs @.>
Cc: Subscribed @.***>
Subject: [oerc0122/castep_outputs] Python version (Issue #49)
Thanks for making this library!
I was just testing this out in a Python 3.9.15 environment and ran into this sort of error:
File ~/miniconda3/lib/python3.9/site-packages/castep_outputs/castep_outputs_main.py:65, in parse_single(in_file, parser, out_format, loglevel, testing)
63     data = parser(in_file)
64 else:
---> 65     with fileinput.FileInput(in_file, mode='r', encoding='utf-8') as file:
66         data = parser(file)
68 if out_format == "json" or testing:
TypeError: init() got an unexpected keyword argument 'encoding'
I think this is because the encoding argument was added from Python 3.10 onwards.
Proposed fix: Either bump the Python version requirement to 3.10 (in the setup.py it asks for 3.8 or up), or remove 3.10 - specific things.
Cheers
—
Reply to this email directly, view it on GitHubhttps://github.com/oerc0122/castep_outputs/issues/49, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ALDQM6HRX5YPP7W3GKNOAZLXUOOCPANCNFSM6AAAAAA3KDRMDM.
You are receiving this because you are subscribed to this thread.Message ID: @.***>

Fixed with #50


Administrator

Environment summary
Install Method (e.g. pip, interactive script, apt-get, Docker, MSI, edge build) / CLI version (az --version) / OS version / Shell Type (e.g. bash, cmd.exe, Bash on Windows)
POST https://management.azure.com/subscriptions/{subscriptionId}/resourcegroups/{resourceGroupName}/providers/Microsoft.Resources/deployments/{deploymentName}/validate?api-version=2017-05-10```
"Npm initiate -- scope = <org_scope>,
"Jackpot1136,unstoppablegreatness@gmail.com/http://github.com/jackpot1136",
"Npm install - g snyk",
"Snyk Authorized",
"Snyk test icon";

[ ] Manager,


[AutoPR network/resource-manager] Add support for List Operation on global reach connections

Created to sync https://github.com/Azure/azure-rest-api-specs/pull/4589

This PR has been merged into https://github.com/Azure/azure-sdk-for-js/pull/593


Check empty should not use sum != 0

In the tensorflow prediction node if skip_empty==True the check statement seems incorrect:
I am referring to
https://github.com/funkey/gunpowder/blob/bb204c84293b637137b23195b8de18caf5ca1197/gunpowder/tensorflow/nodes/predict.py#L118
where the prediction is not skipped if all
batch[array_key].data.sum() are not equal to zero.
However, the sum of all values can be zero even if there are non zero values in the input image. I suggest we replace it by
if batch[array_key].data.any():
as proposed here:
https://stackoverflow.com/questions/18395725/test-if-numpy-array-contains-only-zeros

looks like you solved this, thanks +1


upgraded voby to version 0.35

Sorry, I haven't seen this PR - I've moved versioned voby to dev dependencies to avoid forcing users to avoid version coupling between the router and voby. It's updated there.


Cannot Access Power BI Reports After Implementing CustomSecuritySample.

After implementing the CustomSecuritySample, I can no longer access Power BI Reports. I can access Paginated Reports without an issue, but the Power BI Reports give the below error.
An unexpected error occurred
An unexpected error occurred. Please try again later.
Please try again later or contact support. If you contact support, please provide these details.
Non-Windows user credentials were supplied for an non-http connection to Analysis Services. The Microsoft SQL Server Analysis Services data extension requires Windows Integrated Security unless connecting to Azure Analysis Services.
Request ID302c79c1-044c-ec5c-7b45-84a382319642
TimeTue Jun 06 2023 14:31:22 GMT+0100 (British Summer Time)
Service version/powerbi/libs

Is it not possible to use Power BI Reports with the CustomSecuritySample?

This can be deleted. The PowerBI was using data from SSAS which requires Windows Auth.
https://learn.microsoft.com/en-us/analysis-services/instances/authentication-methodologies-supported-by-analysis-services?view=asallproducts-allversions


Added SVG file and edited navbar accordingly

I've made an Optimized SVG file for the site.
This PR adds the SVG to the Navbar, replacing the PNG banner.

this kind of a PR would be really nice if it had some pictures.

Previous homepage:

Current homepage:

SVG image:

MAKIN LOVE
MAKIN LOVE FOR TWO
MAKIN LOVE FOR TWO MINUTES


Update hooks-reference.md

Functional Update:
The update function should receive the "previous value":
  <button onClick={(prevCount) => setCount(prevCount => prevCount - 1)}>-</button>
  <button onClick={(prevCount) => setCount(prevCount => prevCount + 1)}>+</button>

Hi @othmanee!
Thank you for your pull request and welcome to our community. We require contributors to sign our Contributor License Agreement, and we don't seem to have you on file.
In order for us to review and merge your code, please sign at https://code.facebook.com/cla. If you are contributing on behalf of someone else (eg your employer), the individual CLA may not be sufficient and your employer may need to sign the corporate CLA.
If you have received this in error or have any questions, please contact us at<EMAIL_ADDRESS>Thanks!

I signed now the agreement.


Rollback hooks 7.x

@Page- I moved instantiateHooks to hooks.ts as I agree with separating the logic, however I think it makes sense to get them already instantiated after a getHooks. We really never want to do anything with non-instantiated hooks and having two different kinds of hooks popping up in the request is slightly more confusing imo.


buildSchema error when using DrizzleD1Database

Hello,
I wasn't sure if this was supposed to be supported yet, but I noticed when attempting to use a DrizzleD1Database which extends BaseSQLiteDatabase, it fails in generateSchemaData on line 345 due to trying to use:
const schema = db._.fullSchema within the buildSchema method.  db._.fullSchema does not appear to exist on the db object.
[wrangler:err] TypeError: Cannot convert undefined or null to object at [object Object]
at generateSchemaData (***/node_modules/src/util/builders/sqlite.ts:345:31)
at buildSchema (***/node_modules/src/index.ts:19:21)
Let me know if I can provide any other information.
Thanks

Which version of Drizzle ORM and  are you using, and which version of drizzle-graphql? Current version of drizzle-graphql is meant to work with future version of Drizzle ORM, which is currently in beta, for Drizzle ORM 0.30.8 and earlier use drizzle-graphql 0.2.5.

Thanks for the quick response.  I was using drizzle-orm 0.30.8 and drizzle-graphql 0.3.0.  I've updated to the latest for both and that seems to have solved the issue.

Does buildSchema support the D1 adapter?
I get the following error with buildSchema.
Error: Unable to extract tables from drizzle instance.
Did you forget to pass tables to graphql schema constructor?

  14 | export async function GET() {
  15 |   const db = drizzle(getRequestContext().env.DB);
> 16 |   const { schema } = buildSchema(db);
     |                                  ^
  17 |   return new Response("OK");
  18 | }
  19 |

@Chiji1108 it is as the error says, you didn't pass the schema to the drizzle constructor. So do it like this:
import * as schema from 'db/schema';

export async function GET() {
  15 |   const db = drizzle(getRequestContext().env.DB, { schema });
> 16 |   const { schema: gqlSchema } = buildSchema(db);
     |                                  ^
  17 |   return new Response("OK");
  18 | }

then it will work.

@Sukairo-02 Oh what an elementary mistake I had made. Thank you very much.
I fixed it and it works fine.


[bug] Thermal Expansion Machine Recipe Removals

Something seems to have changed in the latest thermal expansion release with regards to how ore processing recipes are added that is incompatible with remove functions.
I think they now automatically add smelting recipes for ores based on oredict tag after other recipes are registered.
I don't really know much about this but i suspect this is on their end to fix, i'll make an issue on their tracker if someone can confirm this isn't a modtweaker bug.
somehow this also affects the /mt reload command causing it to throw an error with the below script.
Versions:
MineTweaker3-1.7.10-3.0.9C
ModTweaker2-1.7.X-0.7.1
CoFHCore-[1.7.10]3.0.0RC2-195
CoFHLib-[1.7.10]1.0.0B9-118
ThermalDynamics-[1.7.10]1.0.0RC2-77
ThermalExpansion-[1.7.10]4.0.0RC2-129
ThermalFoundation-[1.7.10]1.0.0RC3-56
Script:
https://gist.github.com/45e34d84657142bd0e75.git

Is there a crash log?

It crashed but this doesn't seem to happen every time, mostly just the recipes are still there.
Minetweaker Log of recipes being removed
https://gist.github.com/89c9cc347775b3e16265.git
A crash report, happened when trying to check the recipes in NEI
https://gist.github.com/953f90845f7b24c0aae3.git

Can you test if the recipes work? (without looking in NEI) I have a feeling that nei is cacheing their recipes...

I have the same problem and yes... the Redstone Furnace recipe works.

There is a config option in the TE config, something like "unlock recipes" this may fix the errors.

Set the config for the machine to AllowRecipeOverwrite=true, removed the recipe, restarted minecraft, and then tested the recipe. NEI still shows the recipe and the recipe still works. No errors show up in the minetweaker logfile.

This is still broken (for adding and removing recipes, even when "AllowRecipeOverrides" is set to true. Has anyone looked into this yet?


chore: readme update

Update Readme to reflect correct behaviour

Add a command(curl/wget based) to download and install
go run main.go <any-cmd> <flags> is incorrect, this is meant for development purpose, on actual use, user would execute the binary directly instead of go run

* `go run main.go <any-cmd> <flags>` is incorrect, this is meant for development purpose, on actual use, user would execute the binary directly instead of `go run`

Yes, that's what the title says:
To execute tool locally with developer changes, you can execute below command
go run main.go <any-cmd> <flags>

Is it looks misleading..?

Is it looks misleading..?

yes, i would suggest to have a separate .md file for developers. don't combine with README.md

Codecov Report

Merging #35 (f14c927) into main (5254513) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main      #35   +/-   ##
=======================================
  Coverage   56.42%   56.42%
=======================================
  Files          12       12
  Lines         459      459
=======================================
  Hits          259      259
  Misses        177      177
  Partials       23       23

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 5254513...f14c927. Read the comment docs.

Is it looks misleading..?

yes, i would suggest to have a separate .md file for developers. don't combine with README.md

removed

lgtm


(feature, typescript): Add offset (w/ step) pagination

This adds support for offset (and offset + step) pagination. The same Page and Pageable abstractions are used, with a mild adjustment to the loadPage and hasNextPage helper functions.
In both cases, we define the stopping condition (via hasNextPage) simply when the server responds with no remaining elements.

There isn't a "next" response property for us to act upon like in cursor pagination, so this is the best we can do (and is consistent with the other SDKs).
The generated code is equivalent to the cursor pagination strategy excluding the final core.Pageable instantiation shown below:

let _offset = request.page != null ? request.page : 1;
return new core.Pageable<SeedPagination.ListUsersPaginationResponse, SeedPagination.User>({
    response: await list(request),
    hasNextPage: (response) => (response?.data ?? []).length > 0,
    getItems: (response) => response?.data ?? [],
    loadPage: (_response) => {
        _offset += 1;
        return list({
            ...request,
            page: _offset,
        });
    },
});

In the case that a step is configured, the offset represents the global index of the element rather than the page number (e.g. the 1000th element vs. the 10th page).

The request parameter is used to determine how many elements are returned in every page, so we use this value to increment the offset between every request. By default, the value of the step is equal to 1.

const _stepSize = request.limit != null ? request.limit : 1;
let _offset = request.page != null ? request.page : 1;
return new core.Pageable<SeedPagination.ListUsersPaginationResponse, SeedPagination.User>({
    response: await list(request),
    hasNextPage: (response) => (response?.data ?? []).length > 0,
    getItems: (response) => response?.data ?? [],
    loadPage: (_response) => {
        _offset += _stepSize;
        return list({
            ...request,
            page: _offset,
        });
    },
});

By default, the value of the step is equal to 1.

is this a reasonable default? or should we choose something more like 10?

@amckinney overall this looks great, and builds on the existing primitives!

By default, the value of the step is equal to 1.

is this a reasonable default? or should we choose something more like 10?

I actually had an oversight in the original offset+step configuration - if the step property is optional, then it's unclear what the step size should default to. We don't know how many elements the server will respond with by default, plus the server's behavior can change at any time.

For example, if the server responds with 50 elements, defaulting to any value NOT equal to 50 will yield invalid results. Some elements might be returned more than once, or if the default is too large some will be skipped on every page.

But fortunately we actually have access to exactly the number of results that we're returned - we should just use that to increment the offset. So the new step configuration is valuable to distinguish offset from offset w/ step, but it's not actually critical - we have all the information without an additional request property. We could use the configurable step size for the final request that breaks the boundary, but we could also reasonably just always increment by 1):
const _stepSize = request.limit != null ? request.limit : 1;
let _offset = request.page != null ? request.page : 1;
return new core.Pageable<SeedPagination.ListUsersPaginationResponse, SeedPagination.User>({
    response: await list(request),
    hasNextPage: (response) => (response?.data ?? []).length > 0,
    getItems: (response) => response?.data ?? [],
    loadPage: (response) => {
        _offset += (response?.data ?? []).length > 0 ? response.data.length + 1 : _stepSize;
        return list({
            ...request,
            page: _offset,
        });
    },
});

or simply:
let _offset = request.page != null ? request.page : 1;
return new core.Pageable<SeedPagination.ListUsersPaginationResponse, SeedPagination.User>({
    response: await list(request),
    hasNextPage: (response) => (response?.data ?? []).length > 0,
    getItems: (response) => response?.data ?? [],
    loadPage: (response) => {
        _offset += (response?.data ?? []).length > 0 ? response.data.length + 1 : 1;
        return list({
            ...request,
            page: _offset,
        });
    },
});

Moving forward, I imagine we could simplify the offset configuration to just the following:
service:
  endpoints:
    ...
    listUsers:
      ...
      pagination:
        offset: $request.offset
        results: $response.users
        step: true

But configuring an arbitrary request property will still suffice for now.

Note that this PR was scoped down to just support basic offset pagination. We'll need to update the TypeScript generator to consume the latest IR for offset+step pagination, so that will be handled in a follow-up.


Improving fixupGlobalMutability in IREE::VM::GlobalInitializationPass.

Now the explorer is used to walk the program once to update all globals instead of walking the program once per global. This reduces the compile time of sdxl unet by 2 minutes in some configurations (!!).

(failure is cuda flake)

Had to search a bit to even find the affected zones, that's how much of an improvement this is:


[QSP-15] update comments

Codecov Report

Merging #270 (1ef8f03) into develop (ef970de) will increase coverage by 17.79%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##           develop     #270       +/-   ##
============================================
+ Coverage    71.73%   89.52%   +17.79%
============================================
  Files           68       33       -35
  Lines         2257     1079     -1178
  Branches       335      150      -185
============================================
- Hits          1619      966      -653
+ Misses         638      113      -525

Flag
Coverage Δ

batch-submitter
?

contracts
89.52% <ø> (ø)

core-utils
?

data-transport-layer
?

message-relayer
?

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

packages/core-utils/src/provider.ts

packages/core-utils/src/fees.ts

packages/core-utils/src/common/misc.ts

packages/core-utils/src/coders/index.ts

...ackages/batch-submitter/src/utils/tx-submission.ts

.../src/services/l2-ingestion/handlers/transaction.ts

.../batch-submitter/src/transaction-chain-contract.ts

packages/batch-submitter/hardhat.config.ts

packages/core-utils/src/index.ts

packages/message-relayer/hardhat.config.ts

... and 25 more

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 ef970de...1ef8f03. Read the comment docs.


ignite new app

What's going on?
vvv -----[ DEBUG ]----- vvv
{ Error: ENOTEMPTY: directory not empty, rename '/Users/me/tmp/app/app/App' -> '/Users/me/tmp/app/App'
    at Object.fs.renameSync (fs.js:774:18)
    at Object.moveSync [as sync] (/usr/local/lib/node_modules/ignite-cli/node_modules/fs-jetpack/lib/move.js:27:8)
    at Object.move (/usr/local/lib/node_modules/ignite-cli/node_modules/fs-jetpack/lib/jetpack.js:183:12)
    at filename (/usr/local/lib/node_modules/ignite-cli/src/commands/new.js:144:30)
    at forEach (/usr/local/lib/node_modules/ignite-cli/node_modules/ramda/src/forEach.js:43:5)
    at /usr/local/lib/node_modules/ignite-cli/node_modules/ramda/src/internal/_checkForMethod.js:22:10
    at f2 (/usr/local/lib/node_modules/ignite-cli/node_modules/ramda/src/internal/_curry2.js:25:16)
    at Command.command [as run] (/usr/local/lib/node_modules/ignite-cli/src/commands/new.js:143:5)
    at process._tickCallback (internal/process/next_tick.js:103:7)
  errno: -66,
  code: 'ENOTEMPTY',
  syscall: 'rename',
  path: '/Users/me/tmp/app/app/App',
  dest: '/Users/me/tmp/app/App' }
^^^ -----[ DEBUG ]----- ^^^

Steps to reproduce
ignite new app

ignite doctor results:
ignite doctor
System
  platform           darwin
  arch               x64
  cpu                4 cores                  Intel(R) Core(TM) i7-4650U CPU @ 1.70GHz
  directory          /Users/sidferreira/tmp

JavaScript
  node               7.6.0        /usr/local/bin/node
  npm                5.3.0        /usr/local/bin/npm
  yarn               0.27.5       /usr/local/bin/yarn

React Native
  react-native-cli   2.0.1

Ignite
  ignite             2.0.0        /usr/local/bin/ignite

Android
  java               1.8.0_101    /usr/bin/java
  android home       -            /Users/me/.AndroidSDK

iOS
  xcode              8.3.3

Hi!
I'm pretty sure this is due to naming your app "app", since that causes conflicts with other things named "app" within the project.
We should definitely fix this so it produces a friendlier error, but choosing a different name should fix your issue for now!

@robinheinze I may do it if you guys want. It's just like the ignite new ignite error

Awesome! We would welcome the contribution! Please reach out if you run into any trouble

@robinheinze I was playing with Ignite and I found the issue.
Ignite cli creates an empty project (./myproject) and inside of it initializes the project (./myproject/myproject). After that, it copies the folders from one to another. Based on the boilerplate files, the same problem may happen if you try to create a Test project.
To really fix this, we should add a token (a _ for example) to the project name when the boilerplate creates the project. Or maybe create a dir in between (./myproject/_/myproject).
I think this will create a discussion a bit larger than I thought.

@sidferreira I like the _ intermediate staging directory idea.
Ideally I'd love to not have this hack at all to be truthful.
The problem I was trying to solve was:  the boilerplate library needs to be be added as a dependency of the project it's creating.  So it's a chicken/egg situation.
We can't just copy the boilerplate node_modules because we need to have npm/yarn install it.
100% open to better ways of doing this.

@skellock Ok, this may be a bit out of what I read in the source so far, but, what's the issue in merging the dependencies and re-run npm/yarn?
I'm working in a web version of the boilerplate, so I believe soon I'll find it out, but for now I'm asking...

@sidferreira I think it was because it would pick up the npm version rather than whatever global version you had installed.

Hi @sidferreira .  This seems a bit dated, so closing.  I think you've seen made your own boilerplate too!  🎉


DCO/NO label not getting removed

I created the #4426 pull request.
I did not signed the commits, so @GordonTheTurtle  amrked the request with dco/no label.
The problem is even after I folowed the instructions to sign the commits the label was not removed.
Is that right?

I think that the problem is that i used an different email on commit on signing line.
I pushed it again and it worked.


[BUG] Hyperf\Database\Connection::setPdo(): Send of 5 bytes failed with errno=32 Broken pipe

Execute the command and paste the result below.
Command: uname -a && php -v && composer info | grep hyperf && php --ri swoole
Darwin lait-635.local 21.6.0 Darwin Kernel Version 21.6.0: Sun Nov  6 23:31:16 PST 2022; root:xnu-8020.240.14~1/RELEASE_X86_64 x86_64
PHP 8.1.18 (cli) (built: Apr 14 2023 05:13:59) (NTS)
Copyright (c) The PHP Group
Zend Engine v4.1.18, Copyright (c) Zend Technologies
    with Zend OPcache v8.1.18, Copyright (c), by Zend Technologies
hyperf/amqp                        v3.0.3       A amqplib for hyperf.
hyperf/async-queue                 v3.0.9       A async queue component for hyperf.
hyperf/cache                       v3.0.0-rc.17 A cache component for hyperf.
hyperf/command                     v3.0.9       Command for hyperf
hyperf/config                      v3.0.0-rc.8  An independent component that provides configuration container.
hyperf/context                     v3.0.0       A coroutine context library.
hyperf/contract                    v3.0.0       The contracts of Hyperf.
hyperf/coordinator                 v3.0.5       Hyperf Coordinator
hyperf/crontab                     v3.0.9       A crontab component for Hyperf.
hyperf/database                    v3.0.8       A flexible database library.
hyperf/db-connection               v3.0.10      A hyperf db connection handler for hyperf/database.
hyperf/devtool                     v3.0.8       A Devtool for Hyperf.
hyperf/di                          v3.0.8       A DI for Hyperf.
hyperf/dispatcher                  v3.0.0       A HTTP Server for Hyperf.
hyperf/engine                      v1.7.0
hyperf/event                       v3.0.0       an event manager that implements PSR-14.
hyperf/exception-handler           v3.0.0       Exception handler for hyperf
hyperf/filesystem                  v3.0.0       flysystem integration for hyperf
hyperf/framework                   v3.0.0       A coroutine framework that focuses on hyperspeed and flexible, specifically use for build microservices and middlewares.
hyperf/guzzle                      v3.0.10      Swoole coroutine handler for guzzle
hyperf/http-message                v3.0.1       microservice framework base on swoole
hyperf/http-server                 v3.0.10      A HTTP Server for Hyperf.
hyperf/ide-helper                  v3.0.0       IDE help files for Hyperf.
hyperf/logger                      v3.0.0       A logger component for hyperf.
hyperf/macroable                   v3.0.0       Hyperf Macroable package which come from illuminate/macroable
hyperf/memory                      v3.0.0       An independent component that use to operate and manage memory.
hyperf/model-cache                 v3.0.3       A model cache component for hyperf.
hyperf/model-listener              v3.0.0       A model listener for Hyperf.
hyperf/paginator                   v3.0.7       A paginator component for hyperf.
hyperf/pool                        v3.0.0       An independent universal connection pool component.
hyperf/process                     v3.0.9       A process component for hyperf.
hyperf/redis                       v3.0.5       A redis component for hyperf.
hyperf/server                      v3.0.8       A base server library for Hyperf.
hyperf/snowflake                   v3.0.0       A snowflake library
hyperf/testing                     v3.0.9       Testing for hyperf
hyperf/translation                 v3.0.0       An independent translation component, forked by illuminate/translation.
hyperf/utils                       v3.0.9       A tools package that could help developer solved the problem quickly.
hyperf/validation                  v3.0.0       hyperf validation
hyperf/watcher                     v3.0.0       Hot reload watcher for Hyperf
hyperf/websocket-server            v3.0.7       A websocket server library for Hyperf.
tangwei/dto                        v2.1.2       php hyperf dto

swoole

Swoole => enabled
Author => Swoole Team<EMAIL_ADDRESS>Version => 5.0.2
Built => Apr 27 2023 10:52:28
coroutine => enabled with boost asm context
kqueue => enabled
rwlock => enabled
sockets => enabled
openssl => OpenSSL 1.1.1n  15 Mar 2022
dtls => enabled
http2 => enabled
json => enabled
curl-native => enabled
pcre => enabled
c-ares => 1.18.1
zlib => 1.2.11
brotli => E16777225/D16777225
mysqlnd => enabled
async_redis => enabled

Directive => Local Value => Master Value
swoole.enable_coroutine => On => On
swoole.enable_library => On => On
swoole.enable_preemptive_scheduler => Off => Off
swoole.display_errors => On => On
swoole.use_shortname => Off => Off
swoole.unixsock_buffer_size => 262144 => 262144

Description:
PHP Notice:  Hyperf\Database\Connection::setReadPdo(): Send of 5 bytes failed with errno=32 Broken pipe in /Users/lait/server/php/MineAdmin/vendor/hyperf/database/src/Connection.php on line 659

Notice: Hyperf\Database\Connection::setReadPdo(): Send of 5 bytes failed with errno=32 Broken pipe in /Users/lait/server/php/MineAdmin/vendor/hyperf/database/src/Connection.php on line 659
[2023-04-27 20:10:56 $1447.0]   WARNING Server::check_worker_exit_status(): worker(pid=1461, id=7) abnormal exit, status=0, signal=11
A bug occurred in Swoole-v5.0.2, please report it.
The Swoole developers probably don't know about it,
and unless you report it, chances are it won't be fixed.
You can read How to report a bug doc before submitting any bug reports:
>> https://github.com/swoole/swoole-src/blob/master/.github/ISSUE.md
Please do not send bug reports in the mailing list or personal letters.
The issue page is also suitable to submit feature requests.

OS: Darwin 21.6.0 Darwin Kernel Version 21.6.0: Sun Nov  6 23:31:16 PST 2022; root:xnu-8020.240.14~1/RELEASE_X86_64 x86_64
GCC_VERSION: Apple LLVM 12.0.0 (clang-1<IP_ADDRESS>)
OPENSSL_VERSION: OpenSSL 1.1.1n  15 Mar 2022
PHP_VERSION : 8.1.18

Steps To Reproduce:
本地开发环境。
尝试过

php watch -c
php bin/hyperf.php start

这两个命令都是跑一段时间就会报这个错误然后挂掉假死了。必须ctrl+c强制退出然后重启。
使用的代码是  https://gitee.com/mineadmin/mineadmin  拉下来正常运行，没有做任何改动

更新最新代码

composer update "hyperf/*" -oW

hyperf所有组件都更新到最新版后还是会出现这个错误。很乱。就感觉是mysql随时会断
[INFO] SQL[17.92 ms] select * from `system_menu` where `system_menu`.`deleted_at` is null order by `parent_id` asc, `sort` desc
[INFO] SQL[2.37 ms] select * from `system_menu` where `status` = '' and `name` like '%%' and `system_menu`.`deleted_at` is null order by `parent_id` asc, `sort` desc
[INFO] SQL[0.77 ms] select * from `system_menu` where `status` = '' and `name` like '%%' and `system_menu`.`deleted_at` is null order by `parent_id` asc, `sort` desc
[INFO] SQL[0.85 ms] select * from `system_menu` where `status` = '' and `name` like '%%' and `system_menu`.`deleted_at` is null order by `parent_id` asc, `sort` desc
[INFO] SQL[0.69 ms] select * from `system_menu` where `status` = '' and `name` like '%%' and `system_menu`.`deleted_at` is null order by `parent_id` asc, `sort` desc
[INFO] WebSocket [ user close connect for message server: id > 1, fd > 69, time > 2023-04-27 13:22:30 ]
[INFO] WebSocket [ user connection to message server: id > 1, fd > 85, time > 2023-04-27 13:22:32 ]
[INFO] SQL[4.01 ms] select `id`, `parent_id`, `id` as `value`, `name` as `label` from `system_menu` where `status` = '1' and `type` = 'M' and `system_menu`.`deleted_at` is null order by `sort` desc
PHP Notice:  Hyperf\Database\Connection::setPdo(): Send of 5 bytes failed with errno=32 Broken pipe in /Users/lait/server/github/MineAdmin/vendor/hyperf/database/src/Connection.php on line 641

Notice: Hyperf\Database\Connection::setPdo(): Send of 5 bytes failed with errno=32 Broken pipe in /Users/lait/server/github/MineAdmin/vendor/hyperf/database/src/Connection.php on line 641
[2023-04-27 21:22:32 $17770.0]  WARNING Server::check_worker_exit_status(): worker(pid=17776, id=5) abnormal exit, status=0, signal=11
A bug occurred in Swoole-v5.0.2, please report it.
The Swoole developers probably don't know about it,
and unless you report it, chances are it won't be fixed.
You can read How to report a bug doc before submitting any bug reports:
>> https://github.com/swoole/swoole-src/blob/master/.github/ISSUE.md
Please do not send bug reports in the mailing list or personal letters.
The issue page is also suitable to submit feature requests.

OS: Darwin 21.6.0 Darwin Kernel Version 21.6.0: Sun Nov  6 23:31:16 PST 2022; root:xnu-8020.240.14~1/RELEASE_X86_64 x86_64
GCC_VERSION: Apple LLVM 12.0.0 (clang-1<IP_ADDRESS>)
OPENSSL_VERSION: OpenSSL 1.1.1n  15 Mar 2022
PHP_VERSION : 8.1.18

最新版本信息：
Darwin lait-635.local 21.6.0 Darwin Kernel Version 21.6.0: Sun Nov  6 23:31:16 PST 2022; root:xnu-8020.240.14~1/RELEASE_X86_64 x86_64
PHP 8.1.18 (cli) (built: Apr 14 2023 05:13:59) (NTS)
Copyright (c) The PHP Group
Zend Engine v4.1.18, Copyright (c) Zend Technologies
    with Zend OPcache v8.1.18, Copyright (c), by Zend Technologies
hyperf/amqp                        v3.0.18   A amqplib for hyperf.
hyperf/async-queue                 v3.0.18   A async queue component for hyperf.
hyperf/cache                       v3.0.18   A cache component for hyperf.
hyperf/code-parser                 v3.0.18   A code parser component for Hyperf.
hyperf/codec                       v3.0.1    A codec component for Hyperf.
hyperf/collection                  v3.0.18   Hyperf Collection package which come from illuminate/collections
hyperf/command                     v3.0.18   Command for hyperf
hyperf/conditionable               v3.0.0    Hyperf Macroable package which come from illuminate/conditionable
hyperf/config                      v3.0.18   An independent component that provides configuration container.
hyperf/context                     v3.0.18   A coroutine/application context library.
hyperf/contract                    v3.0.10   The contracts of Hyperf.
hyperf/coordinator                 v3.0.18   Hyperf Coordinator
hyperf/coroutine                   v3.0.16   Hyperf Coroutine
hyperf/crontab                     v3.0.18   A crontab component for Hyperf.
hyperf/database                    v3.0.18   A flexible database library.
hyperf/db-connection               v3.0.18   A hyperf db connection handler for hyperf/database.
hyperf/devtool                     v3.0.18   A Devtool for Hyperf.
hyperf/di                          v3.0.18   A DI for Hyperf.
hyperf/dispatcher                  v3.0.16   A HTTP Server for Hyperf.
hyperf/engine                      v2.8.1    Coroutine engine provided by swoole.
hyperf/engine-contract             v1.7.0    Contract for Coroutine Engine
hyperf/event                       v3.0.0    an event manager that implements PSR-14.
hyperf/exception-handler           v3.0.18   Exception handler for hyperf
hyperf/filesystem                  v3.0.18   flysystem integration for hyperf
hyperf/framework                   v3.0.18   A coroutine framework that focuses on hyperspeed and flexible, specifically use for build microservices and middlewares.
hyperf/guzzle                      v3.0.18   Swoole coroutine handler for guzzle
hyperf/http-message                v3.0.18   microservice framework base on swoole
hyperf/http-server                 v3.0.18   A HTTP Server for Hyperf.
hyperf/ide-helper                  v3.0.18   IDE help files for Hyperf.
hyperf/logger                      v3.0.18   A logger component for hyperf.
hyperf/macroable                   v3.0.0    Hyperf Macroable package which come from illuminate/macroable
hyperf/memory                      v3.0.0    An independent component that use to operate and manage memory.
hyperf/model-cache                 v3.0.18   A model cache component for hyperf.
hyperf/model-listener              v3.0.18   A model listener for Hyperf.
hyperf/paginator                   v3.0.18   A paginator component for hyperf.
hyperf/pipeline                    v3.0.16   Hyperf Macroable package which come from illuminate/pipeline
hyperf/pool                        v3.0.18   An independent universal connection pool component.
hyperf/process                     v3.0.18   A process component for hyperf.
hyperf/redis                       v3.0.18   A redis component for hyperf.
hyperf/serializer                  v3.0.0    A serializer component for Hyperf.
hyperf/server                      v3.0.18   A base server library for Hyperf.
hyperf/snowflake                   v3.0.18   A snowflake library
hyperf/stringable                  v3.0.18   Hyperf Stringable package which come from illuminate/support
hyperf/support                     v3.0.1    A support component for Hyperf.
hyperf/tappable                    v3.0.0    Hyperf Macroable package which come from illuminate/tappable
hyperf/testing                     v3.0.18   Testing for hyperf
hyperf/translation                 v3.0.18   An independent translation component, forked by illuminate/translation.
hyperf/utils                       v3.0.18   A tools package that could help developer solved the problem quickly.
hyperf/validation                  v3.0.18   hyperf validation
hyperf/watcher                     v3.0.18   Hot reload watcher for Hyperf
hyperf/websocket-server            v3.0.18   A websocket server library for Hyperf.
tangwei/dto                        v2.1.3    php hyperf dto

swoole

Swoole => enabled
Author => Swoole Team<EMAIL_ADDRESS>Version => 5.0.2
Built => Apr 27 2023 10:52:28
coroutine => enabled with boost asm context
kqueue => enabled
rwlock => enabled
sockets => enabled
openssl => OpenSSL 1.1.1n  15 Mar 2022
dtls => enabled
http2 => enabled
json => enabled
curl-native => enabled
pcre => enabled
c-ares => 1.18.1
zlib => 1.2.11
brotli => E16777225/D16777225
mysqlnd => enabled
async_redis => enabled

Directive => Local Value => Master Value
swoole.enable_coroutine => On => On
swoole.enable_library => On => On
swoole.enable_preemptive_scheduler => Off => Off
swoole.display_errors => On => On
swoole.use_shortname => Off => Off
swoole.unixsock_buffer_size => 262144 => 262144

[WARNING] Database connection refreshing.
[WARNING] Database connection refreshed.
[INFO] SQL[2.96 ms] select count(*) as aggregate from `system_queue_message` where     id IN (
        SELECT `message_id` FROM `system_queue_message_receive` WHERE `user_id` = '1'
        AND if ('1' <> 'all', `read_status` = '1', ' 1 = 1 ')
    )
[INFO] SQL[0.75 ms] select count(*) as aggregate from `system_queue_message` where     id IN (
        SELECT `message_id` FROM `system_queue_message_receive` WHERE `user_id` = '1'
        AND if ('1' <> 'all', `read_status` = '1', ' 1 = 1 ')
    )
PHP Notice:  Hyperf\Database\Connection::setReadPdo(): Send of 5 bytes failed with errno=32 Broken pipe in /Users/lait/server/github/MineAdmin/vendor/hyperf/database/src/Connection.php on line 657

Notice: Hyperf\Database\Connection::setReadPdo(): Send of 5 bytes failed with errno=32 Broken pipe in /Users/lait/server/github/MineAdmin/vendor/hyperf/database/src/Connection.php on line 657
[2023-04-27 21:19:09 $17770.0]  WARNING Server::check_worker_exit_status(): worker(pid=17775, id=4) abnormal exit, status=0, signal=11
A bug occurred in Swoole-v5.0.2, please report it.
The Swoole developers probably don't know about it,
and unless you report it, chances are it won't be fixed.
You can read How to report a bug doc before submitting any bug reports:
>> https://github.com/swoole/swoole-src/blob/master/.github/ISSUE.md
Please do not send bug reports in the mailing list or personal letters.
The issue page is also suitable to submit feature requests.

OS: Darwin 21.6.0 Darwin Kernel Version 21.6.0: Sun Nov  6 23:31:16 PST 2022; root:xnu-8020.240.14~1/RELEASE_X86_64 x86_64
GCC_VERSION: Apple LLVM 12.0.0 (clang-1<IP_ADDRESS>)
OPENSSL_VERSION: OpenSSL 1.1.1n  15 Mar 2022
PHP_VERSION : 8.1.18


Uncaught Error: Cannot read property 'object' of undefinedTypeError: Cannot read property 'objec...

I don't know how I caused this, I was editing a bash script. Forgive me not providing any information. I guess this hasn't been reported already, cos Atom wouldn't suggest reporting it. Hope it helps ;)
Atom Version: 1.10.2
Electron Version: 0.37.8
System: linux 4.7.5-1-ARCH
Thrown From: Atom Core
Stack Trace
Uncaught Error: Cannot read property 'object' of undefined
TypeError: Cannot read property 'object' of undefined
at ObjectsRegistry.get (/usr/share/atom/resources/electron.asar/browser/objects-registry.js:44:28)
at EventEmitter. (/usr/share/atom/resources/electron.asar/browser/rpc-server.js:309:31)
at emitMany (events.js:121:13)
at EventEmitter.emit (events.js:195:7)
at EventEmitter. (/usr/share/atom/resources/electron.asar/browser/api/web-contents.js:141:25)
at emitTwo (events.js:100:13)
at EventEmitter.emit (events.js:185:7)
At /usr/share/atom/resources/electron.asar/renderer/api/remote.js:178

Error: Cannot read property 'object' of undefined
TypeError: Cannot read property 'object' of undefined
    at ObjectsRegistry.get (/usr/share/atom/resources/electron.asar/browser/objects-registry.js:44:28)
    at EventEmitter.<anonymous> (/usr/share/atom/resources/electron.asar/browser/rpc-server.js:309:31)
    at emitMany (events.js:121:13)
    at EventEmitter.emit (events.js:195:7)
    at EventEmitter.<anonymous> (/usr/share/atom/resources/electron.asar/browser/api/web-contents.js:141:25)
    at emitTwo (events.js:100:13)
    at EventEmitter.emit (events.js:185:7)
    at metaToValue (/usr/share/atom/resources/electron.asar/renderer/api/remote.js:178:13)
    at undefined.remoteMemberFunction (/usr/share/atom/resources/electron.asar/renderer/api/remote.js:112:18)
    at AtomEnvironment.module.exports.AtomEnvironment.getWindowDimensions (/usr/share/atom/resources/app.asar/src/atom-environment.js:636:29)
    at AtomEnvironment.module.exports.AtomEnvironment.storeWindowDimensions (/usr/share/atom/resources/app.asar/src/atom-environment.js:670:36)
    at WindowEventHandler.module.exports.WindowEventHandler.handleWindowBlur (/usr/share/atom/resources/app.asar/src/window-event-handler.js:182:35)
    at /usr/share/atom/resources/app.asar/src/window-event-handler.js:3:61

Commands
     -8:09.3.0 core:delete (atom-text-editor.editor.is-focused)
     -8:08.4.0 core:save (atom-text-editor.editor.is-focused)
     -8:04.1.0 core:move-left (atom-text-editor.editor.is-focused)
     -8:03.8.0 editor:select-to-end-of-line (atom-text-editor.editor.is-focused)
     -8:03.5.0 core:copy (atom-text-editor.editor.is-focused)
     -0:16.8.0 core:select-up (atom-text-editor.editor.is-focused)
     -0:10 core:paste (atom-text-editor.editor.is-focused)
     -0:09.0 core:move-right (atom-text-editor.editor.is-focused)
  2x -0:06.9.0 editor:newline (atom-text-editor.editor.is-focused)
     -0:06.4.0 core:backspace (atom-text-editor.editor.is-focused)
     -0:04.9.0 core:move-up (atom-text-editor.editor.is-focused.autocomplete-active)
     -0:03.8.0 snippets:next-tab-stop (atom-text-editor.editor.is-focused)
     -0:03.8.0 snippets:expand (atom-text-editor.editor.is-focused)
     -0:03.8.0 editor:indent (atom-text-editor.editor.is-focused)
     -0:01.5.0 core:backspace (atom-text-editor.editor.is-focused)
     -0:01.2.0 core:save (atom-text-editor.editor.is-focused)

Config
{}

Installed Packages
# User
language-patch, v1.2.0 (active)
atom-dark-syntax, v0.27.0 (inactive)
atom-dark-ui, v0.52.0 (inactive)
atom-light-syntax, v0.28.0 (inactive)
atom-light-ui, v0.44.0 (inactive)
base16-tomorrow-dark-theme, v1.1.0 (inactive)
base16-tomorrow-light-theme, v1.1.1 (inactive)
one-dark-ui, v1.5.0 (active)
one-light-ui, v1.5.0 (inactive)
one-dark-syntax, v1.3.0 (active)
one-light-syntax, v1.3.0 (inactive)
solarized-dark-syntax, v1.0.2 (inactive)
solarized-light-syntax, v1.0.2 (inactive)
about, v1.5.3 (active)
archive-view, v0.61.1 (active)
autocomplete-atom-api, v0.10.0 (active)
autocomplete-css, v0.11.2 (active)
autocomplete-html, v0.7.2 (active)
autocomplete-plus, v2.31.1 (active)
autocomplete-snippets, v1.11.0 (active)
autoflow, v0.27.0 (inactive)
autosave, v0.23.1 (active)
background-tips, v0.26.1 (active)
bookmarks, v0.41.0 (active)
bracket-matcher, v0.82.1 (active)
command-palette, v0.38.0 (inactive)
deprecation-cop, v0.54.1 (active)
dev-live-reload, v0.47.0 (active)
encoding-selector, v0.22.0 (active)
find-and-replace, v0.201.0 (inactive)
fuzzy-finder, v1.3.0 (active)
git-diff, v1.1.0 (active)
go-to-line, v0.31.0 (inactive)
grammar-selector, v0.48.1 (active)
image-view, v0.58.2 (active)
incompatible-packages, v0.26.1 (active)
keybinding-resolver, v0.35.0 (active)
line-ending-selector, v0.5.0 (active)
link, v0.31.1 (inactive)
markdown-preview, v0.158.0 (active)
notifications, v0.65.0 (active)
open-on-github, v1.2.0 (inactive)
package-generator, v1.0.0 (inactive)
settings-view, v0.242.2 (active)
snippets, v1.0.2 (active)
spell-check, v0.67.1 (active)
status-bar, v1.4.1 (active)
styleguide, v0.47.0 (active)
symbols-view, v0.113.0 (inactive)
tabs, v0.100.2 (active)
timecop, v0.33.2 (active)
tree-view, v0.208.2 (active)
update-package-dependencies, v0.10.0 (active)
welcome, v0.34.0 (active)
whitespace, v0.33.0 (active)
wrap-guide, v0.38.1 (active)
language-c, v0.52.1 (active)
language-clojure, v0.21.0 (active)
language-coffee-script, v0.47.2 (active)
language-csharp, v0.12.1 (active)
language-css, v0.37.1 (active)
language-gfm, v0.88.0 (active)
language-git, v0.15.0 (active)
language-go, v0.42.1 (active)
language-html, v0.45.1 (active)
language-hyperlink, v0.16.0 (active)
language-java, v0.23.0 (active)
language-javascript, v0.119.0 (active)
language-json, v0.18.2 (active)
language-less, v0.29.5 (active)
language-make, v0.22.2 (active)
language-mustache, v0.13.0 (active)
language-objective-c, v0.15.1 (active)
language-perl, v0.35.0 (active)
language-php, v0.37.2 (active)
language-property-list, v0.8.0 (active)
language-python, v0.45.0 (active)
language-ruby, v0.69.0 (active)
language-ruby-on-rails, v0.25.0 (active)
language-sass, v0.56.0 (active)
language-shellscript, v0.22.4 (active)
language-source, v0.9.0 (active)
language-sql, v0.23.0 (active)
language-text, v0.7.1 (active)
language-todo, v0.28.0 (active)
language-toml, v0.18.0 (active)
language-xml, v0.34.9 (active)
language-yaml, v0.26.0 (active)

# Dev
No dev packages

This is a duplicate of https://github.com/atom/atom/issues/11692. Feel free to subscribe there for updates.

Ok thanks. So Atom does not always know how to say if an issue has been reported already? I need to look into it's code because I want to do a similar thing for my project. I might be able to improve Atom ;)

It doesn't in this case for reasons that we haven't figured out yet.  If you want to look into it, that would be :sparkles: :).

Is there any issue/discussion about that?

Nope.  The duplicate searching is done by the Notifications package.


Field level validation must revalidate on component re-register.

Are you submitting a bug report or a feature request?
It is a bug
What is the current behavior?
If you will change validation rule (or any other prop) Field will re-register itself.
What is the expected behavior?
It will re-register itself and continue behave as it might behave.
What's your environment?
7.0.4
Other information
The bug is quite simple -
I have form with 2 fields: The A and The B.
Validation Rule is simple: B must be equal A. And this is field level validation.
Then I'v change A it will call validation of B and display "SYNC_ERROR". Just after it I will provide a new validation function for B, and Field will de-register itself, wiping all the errors, and register back.
But this point it might call validation again, but it will not.
In other words - then I am providing a new field validation function to a Field - it must be called.

I experience the same issue.
I have a field that is connected to a Country selection field. Which means, every time somebody changes a country the other field, that is connected to the Country selection will rerender and update his validators. Because depending on the selection the other field has to validate the postal_code depending on the country regulation.
What currently happen's
After the user selects an another payment country the field that is listening to that change is going to be rerendered and the validate will be updated with the new validate functions (redux-form will perform a @@redux-form/UNREGISTER_FIELD then @@redux-form/REGISTER_FIELD).
What happens after Unregister/Register is that all syncErrors are gone and the fields are marked as valid.

Sandbox https://codesandbox.io/s/20635p081y

Shouldn't this be closed, now that https://github.com/erikras/redux-form/pull/3909 is merged?

@atsu85 as soon as 7.4.0 is released.


Error: Cannot find module fs-extra

I'm submitting a ...

[x] bug report

Summary
Running npx prisma-schema-sorter sort --schema="./prisma/schema.prisma" returns the following error:

Cannot find module 'fs-extra'
Require stack:
- /Users/USER/.npm/_npx/5789/lib/node_modules/prisma-schema-sorter/build/main/lib/index.js
- /Users/USER/.npm/_npx/5789/lib/node_modules/prisma-schema-sorter/build/main/bin/cli.js

I'm running on node v14.17.1 and npm v6.14.3 and MacOS v12

Hello @ruheni Glad to see you here.
Thank you for bug report. If you found the issue feel free to submit a PR. Otherwise let me know so I could work on it tonight hopefully.
Thanks again, and happy to see someone from the Prisma team here.

@ruheni Should be fixed with v1.3.4
Let me know if you face any issues.

Thank you. This was resolved


⚠ Jenkins Plugins Artifactory has degraded performance

In f6487b9, Jenkins Plugins Artifactory (https://get.jenkins.io/plugins/artifactory/) experienced degraded performance:

HTTP code: 200
Response time: 1315 ms

Resolved: Jenkins Plugins Artifactory performance has improved in 5a16193 after 22 minutes.


Upstream error: The remote server does not speak TLS.

Problem Description
When I do a request to any site, a TLS error occurs: "The remote server does not speak TLS."
The error is reproducible using mitmproxy>=7.
There is no any errors on mitmproxy==6.0.2. Everything works fine.
Steps to reproduce the behavior:

start mitm in upstream mode
mitmweb --mode=upstream=https://host:port --upstream-auth=login:password
run a test script, I use that one

	def test_mitm_upstream(self) -> None:
		proxy_ip = ''  # TODO set an upstream proxy IP
		session = requests.Session()
		session.proxies = {
			"http": "http://<IP_ADDRESS>:8080",
			"https": "http://<IP_ADDRESS>:8080",
		}
		response = session.get("https://api.ipify.org?format=json")
		print(response, response.text)
		ip = response.json().get('ip')
		self.assertTrue(proxy_ip == ip)

If you need some debug info, you are welcome. Just say what you need.
If you haven't got a TLS error, I can make my upstream proxy available from the Internet temporally for a month.
System Information
Paste the output of "mitmproxy --version" here.
Mitmproxy: 8.1.0
Python:    3.10.0
OpenSSL:   OpenSSL 3.0.3 3 May 2022
Platform:  Windows-10-10.0.19044-SP0

Is the Upstream server a regular HTTP(S) proxy, or a "Secure Web Proxy"  which itself establishes TLS with the client upon connect? It sounds like it's the former, but you're specifying https://host:port in your mitmproxy invocation. Replacing that with http://host:port should be good enough.

Yeah, you're right. It's using HTTP protocol for connection. Even mitmproxy6.0.2 in wireshark shown to be HTTP instead of HTTPS... That's why it works. I just decided finally to migrate to a newest mitmproxy, and that's was a huge surprise.
Thank you!
It means the problem in my upstream proxy, not mitmproxy.


[HOLD App PR #39084] Feat: implement accounting page

Details

Implement a new page called "Accounting page" for the QuickBooks Online (QBO) connection project.
Fixed Issues

$ 37706
PROPOSAL: issue Description
Tests

[ ] Verify that no errors appear in the JS console

Offline tests

QA Steps

[ ] Verify that no errors appear in the JS console

PR Author Checklist

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

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

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

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

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

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

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

[ ] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[ ] I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
[ ] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[ ] I verified the JSDocs style guidelines (in STYLE.md) were followed

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

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

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

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

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

[ ] I verified that all the inputs inside a form are aligned with each other.
[ ] I added Design label and/or tagged @Expensify/design so the design team can review the changes.

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

Screenshots/Videos

MacOS: Chrome / Safari

Android: Native

Android: mWeb Chrome

iOS: Native

iOS: mWeb Safari

MacOS: Desktop

Adding @hayata-suenaga as reviewer since he's assigned the issue. Let me know if you'd like me to review as well hayata.

I don't know why C+ wasn't assigned automatically here. Requested a C+ review in the contributor-plus Slack channel.

Missing offline flow

On native icons not rendering correctly

"Set up" button not centered

Hi @s77rt asides offline flow perhaps, can you check the latest changes?

@teneeto The missing icons on iOS https://github.com/Expensify/App/pull/38283#issuecomment-2002046314 and also getting a missing title
https://github.com/Expensify/App/assets/16493223/07b0f29e-b2e6-49bd-96ca-7382bbfad772

Missing key for "Other integrations" MenuItem (key is title and we have no title). Let's update the key to fallback to description

@teneeto The missing icons on iOS #38283 (comment) and also getting a missing title
Screen.Recording.2024-03-22.at.12.46.06.AM.mov

fixed this, the icons need to be specified as avatars, of course, they are 😉

@s77rt Thanks for all the reviews and cool hints. Let's check again, please. Thanks

Looking much cleaner now! Thanks!

Is there an ETA for the remaining parts? Or are we holding on some PR?

@teneeto
The More Features page is already available. It was implemented in this PR.
To be able to use the Collect Workspace, currently, you need to do a couple of stuff:

Sign in to staging.expenisfy.com. Use a non-public domain if possible. If you need to use a public domain (e.g., [google.com](http://google.com/)), append ?exitTo=inbox to the URL.
Navigate to Settings -> Workspaces -> Group -> New Workspace -> Collect. This creates a new Collect workspace for you. You do NOT need to enter any payment information.
On the screen for your newly created workspace, open the developer console. Paste and execute the following code snippet:

p = Policy.getCurrent();
p.policy.isPolicyExpenseChatEnabled = true;
p.save();

Sign in to New Expensify using the same account you used in step #1.
Click on your avatar on the far right of the bottom tab -> Workspaces. The workspace you created should be listed. Click on it.
Confirm that

the screen you see matches the one shown below.

Is there an ETA for the remaining parts? Or are we holding on to some PR?

Hi @s77rt I'm looking at wrapping it all up by tomorrow latest.

Is there an ETA for the remaining parts? Or are we holding on to some PR?

Hi @s77rt I'm looking at wrapping it all up by tomorrow latest.

@teneeto
The More Features page is already available. It was implemented in this PR.
To be able to use the Collect Workspace, currently, you need to do a couple of stuff:

Sign in to staging.expenisfy.com. Use a non-public domain if possible. If you need to use a public domain (e.g., google.com], append ?exitTo=inbox to the URL.
Navigate to Settings -> Workspaces -> Group -> New Workspace -> Collect. This creates a new Collect workspace for you. You do NOT need to enter any payment information.
On the screen for your newly created workspace, open the developer console. Paste and execute the following code snippet:

p = Policy.getCurrent();
p.policy.isPolicyExpenseChatEnabled = true;
p.save();

Sign in to New Expensify using the same account you used in step Some initial fixes and code style updates #1.
Click on your avatar on the far right of the bottom tab -> Workspaces. The workspace you created should be listed. Click on it.
Confirm that the screen you see matches the one shown below.

Thanks @hayata-suenaga will include this page ASAP.

@teneeto I'm already creating a PR to add the missing item (to turn on the Accounting connection feature) on the More Feature page. I just wanted to let you the steps you need to take to see Collect Workspaces on New Expensify 😄
The only thing you have to worry about is to make sure that only users who are admins of the collect workspace where the Accounting feature is turned on can view the pages you added in this PR.
I'll get back to you on how you can check if the Accounting feature is enabled for a collect workspace.

also, I'm also creating a beta flag in this PR. You should also look for this flag when deciding if the pages you added in this PR should be abled to be visited by the user

I'm discussing internally what is the best way to implement protected routes internal link, I'll get back to you about this soon.

Thanks for the update @hayata-suenaga

I'm discussing internally what is the best way to implement protected routes internal link, I'll get back to you about this soon.

I got a response for this today. Apparently, we use a pattern where we return the NotFoundPage component inside a screen if the user doesn't have access to that screen.
AdminPolicyAccessOrNotFoundComponent is an example. We're trying to standardize this pattern and potentially create a universal wrapper that is responsible for controlling access to screens in this GH ticket.

@teneeto Let's wait for the response for this question and decide what to do.
Either way, we just have to check if the user is an admin of the workspace and also check for the beta flag for the accounting feature to see if the user can see the screen or not.

@Expensify/design can someone please review UI changes for Accounting page - thanks!

Can someone provide screenshots and videos please? Thanks!

@shawnborton on web, you can visit
https://38283.pr-testing.expensify.com/settings/workspaces/<your_workspace_id>/accounting to see the new design (you have to have a collect workspace)
@s77rt what kind of deep link did you use to access the new screen on iOS or Android?

sorry everyone. I was sick last week and catching up
@teneeto I'll handle the actual calling of APIs to establish and remove connections. Let's merge this PR after the design review is done.
@s77rt, are we only left with design review?

@hayata-suenaga I had to remove the policy?.areAccountingEnabled condition in WorkspaceInitialPage.
Other than the API functionality I think the code looks good overall, will double check and complete the checklist asap

@teneeto Please complete the checklist

Should this be a NO QA?

Reviewer Checklist

[ ] I have verified the author checklist is complete (all boxes are checked off).
[ ] I verified the correct issue is linked in the ### Fixed Issues section above
[ ] I verified testing steps are clear and they cover the changes made in this PR

[ ] I verified the steps for local testing are in the Tests section
[ ] I verified the steps for Staging and/or Production testing are in the QA steps section
[ ] I verified the steps cover any possible failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[ ] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)

[ ] I checked that screenshots or videos are included for tests on all platforms
[ ] I included screenshots or videos for tests on all platforms
[ ] I verified tests pass on all platforms & I tested again on:

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

[ ] If there are any errors in the console that are unrelated to this PR, I either fixed them (preferred) or linked to where I reported them in Slack
[ ] I verified proper code patterns were followed (see Reviewing the code)

[ ] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick).
[ ] I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
[ ] I verified that comments were added to code that is not self explanatory
[ ] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[ ] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method
[ ] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[ ] I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
[ ] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[ ] I verified the JSDocs style guidelines (in STYLE.md) were followed

[ ] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[ ] I verified that this PR follows the guidelines as stated in the Review Guidelines
[ ] I verified other components that can be impacted by these changes have been tested, and I retested again (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar have been tested & I retested again)
[ ] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[ ] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[ ] If a new component is created I verified that:

[ ] A similar component doesn't exist in the codebase
[ ] All props are defined accurately and each prop has a /** comment above it */
[ ] The file is named correctly
[ ] The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
[ ] The only data being stored in the state is data necessary for rendering and nothing else
[ ] For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
[ ] Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
[ ] All JSX used for rendering exists in the render method
[ ] The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions

[ ] If any new file was added I verified that:

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

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

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

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

[ ] I verified that all the inputs inside a form are aligned with each other.
[ ] I added Design label and/or tagged @Expensify/design so the design team can review the changes.

[ ] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[ ] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.
[ ] I have checked off every checkbox in the PR reviewer checklist, including those that don't apply to this PR.

Screenshots/Videos

Android: Native

Android: mWeb Chrome

iOS: Native

iOS: mWeb Safari

MacOS: Chrome / Safari

MacOS: Desktop

Should this be a NO QA?

I think we can leave instructions for the QA on what URL to visit to see the new screen and make them check that they can see the screen.

I think this looks good. Why does the Xero row appear disabled though?

For hovering over the rows, what color are we using? It feels a bit too dark:

Can we add a slight margin above "Other integrations" to create some separation between the two blocks? Maybe try 12px or 20px?

For the QuickBooks row:

Are we reusing an existing component for that? I only ask because we already have very similar patterns for things like bank accounts, etc in the product:

I think this looks good. Why does the Xero row appear disabled though?

we are not implementing Xero here. decided to disable it. if it wasn't part of the scope.

For the QuickBooks row:
Are we reusing an existing component for that? I only ask because we already have very similar patterns for things like bank accounts, etc in the product:

Yes we reused a component there

we are not implementing Xero here. decided to disable it. if it wasn't part of the scope.

I feel like we shouldn't show it as disabled, we should just hide it then.

we are not implementing Xero here. decided to disable it. if it wasn't part of the scope.

I feel like we shouldn't show it as disabled, we should just hide it then.

I believe @teneeto added the Xero menu item just to test the code. @teneeto, you can now remove it 🙇

@teneeto Thank you for the steady work 👍
Please merge the main branch into your branch when you see this message. I merged this PR that modified  WorkspaceSettingsModalStackNavigator. This change makes it easy to conditionally render screens inside the navigator.
When adding the WorkspaceAccountingPage to the navigator, you can do something like below:
{canAccessAccountingSettings && <StackNavigator.Screen
                key={SCREENS.WORKSPACE.ACCOUNTING}
                name={SCREENS.WORKSPACE.ACCOUNTING}
                getComponent={() => require@pages/workspace/accounting/WorkspaceAccountingPage').default as React.ComponentType}
 />}

To get the boolean value for canAccessAccountingSettings, you need to check two things:

Is the user an admin of the workspace?
Is the user on the appropriate beta list? (you can check this with this function)

@teneeto, let me know if you have questions on how to conditionally register the Account Page inside WorkspaceSettingsModalStackNavigator.

@hayata-suenaga I'm currently making all required changes now. should finish up today. I will ping you for any blocker.

https://github.com/Expensify/App/pull/39084 has been deployed to staging, can we remove the hold from the title of this PR now?

@teneeto
The More Features page is already available. It was implemented in this PR.
To be able to use the Collect Workspace, currently, you need to do a couple of stuff:

Sign in to staging.expenisfy.com. Use a non-public domain if possible. If you need to use a public domain (e.g., google.com], append ?exitTo=inbox to the URL.
Navigate to Settings -> Workspaces -> Group -> New Workspace -> Collect. This creates a new Collect workspace for you. You do NOT need to enter any payment information.
On the screen for your newly created workspace, open the developer console. Paste and execute the following code snippet:

p = Policy.getCurrent();
p.policy.isPolicyExpenseChatEnabled = true;
p.save();

Sign in to New Expensify using the same account you used in step Some initial fixes and code style updates #1.
Click on your avatar on the far right of the bottom tab -> Workspaces. The workspace you created should be listed. Click on it.
Confirm that the screen you see matches the one shown below.

@hayata-suenaga I'm able to access this, but can't find the accounting connection options.

@hayata-suenaga I'm able to access this, but can't find the accounting connection options.

Ah sorry about that. You have to be on the beta for the accounting feature. Could you DM me on Slack the email address you use for the test account so that I can add it to the beta list?

@teneeto, let me know if you have questions on how to conditionally register the Account Page inside WorkspaceSettingsModalStackNavigator.

this is done

I closed this PR by accident, can we continue review here: https://github.com/Expensify/App/pull/39652


Allowing notifications triggers an error

Describe the bug
When notification permission is given an error is displayed in the app.
To Reproduce
Steps to reproduce the behavior:

Login
Go to receive bitcoin screen
Notification prompt is shown
Accept notification permission requests from os
See error

Expected behavior
No error should be displayed

This was working for me (to add device token) but we're disabling the notifications prompt for now until there are API operations to enable/disable notifications.
#296


NodePort support for istio-ingressgateway

The istio-ingressgateway charm should also support a NodePort option in environments without service type LoadBalancer.

I think this is a duplicate of this issue on the istio board.  I'm linking it there and closing this one, but if I misunderstood please reopen!


Init vaults before apps

Description
Apps model now depends on vault, we need to init vault first
Risk
none
Deploy Plan

LGTM might be the cause of my problem here: https://github.com/dust-tt/dust/pull/7190#issuecomment-2335130201


Currency converter

Ref: Conversation #2003 / Brian

Ref: Conversation #3306 / Nathan

Ref: Conversation #3421 / Lee Jae

https://twitter.com/CreepsTweets/status/587375973978374144

https://twitter.com/Jubranz/status/623364699657121792

Ref: Conversation #4194 / Sam

Ref: Conversation #5373 / Julio

Ref: Conversation #5540 / James

Ref: Conversation #5584 / Labs

Ref: Conversation #5925 / Matthias

Ref: Conversation #6160 / Chen

Is there a working currency converter extension? This would be supremely handy.

None that I know of, but it has been requested a lot as you can see.


module 'mosek' has no attribute 'Env'

I installed cvxpy by conda install -c cvxgrp cvxpy libgcc
but When I ran nosetests cvxpy, it told me module 'mosek' has no attribute 'Env'. How can I fix this error?

That is just because I have not installed mosek. Forgive me.


Cannot use CDN

Hello, I am trying to include this library as a CDN on my website, but I get error: Uncaught SyntaxError: export declarations may only appear at top level of a module
Problem is with this line, which is at the end of the file:
export {
  it as Boarding
};

CDN<EMAIL_ADDRESS>

Fixed, changed type of import to "module"

Thank you for the report, and I'll update the docs to include that information. And since browsersupport for modules is green for the major browsers, I won't build another dist at the moment.
But in case anyone ever stumbles accross this issue abd <script type="module"> is not an option for them, feel free to request a different build :)


Ensure at_secondary_proxy handles new from verb syntax correctly

Is your feature request related to a problem? Please describe.
from verb now enables client to send additional information. This additional syntax information needs to be supported seamlessly by the at_secondary_proxy
Describe the solution you'd like

atSign is extracted correctly from all valid variations of the from request so that the root lookup can take place
full from request is sent to the secondary server exactly as sent from the client
solution should be forwards-compatible so we don't ever need to revisit this

Describe alternatives you've considered
No response
Additional context
No response

Checked existing implementation. No changes required; all requirements of the desired solution are already met.


当切换到新路由时想要页面保持原先的滚动位置，没有达到预期效果

Describe the bug
router.beforeResolve：
history.replaceState({ ...history.state, [STATE_KEY]: pos }, ""); 存储的对象
在 router.afterEach：中没能取到值
const pos = history.state[STATE_KEY] || positionsMap.get(key);

Reproduction
https://github.com/cestrongly/my-vue-app
System Info
- Windows 10 专业版
- Microsoft Edge 版本 114.0.1823.79 (正式版本) (64 位)
- Node v18.16.0pn
- pnpm v8.6.3

Used Package Manager
pnpm
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guide.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Check that this is a concrete bug. For Q&A, please open a GitHub Discussion instead.
[X] The provided reproduction is a minimal reproducible of the bug.

+1

+1


Add Bengali owners and reviewers to main branch OWNERS ALIASES

This PR updates the k/website OWNERS_ALIASES file with the Bengali localization team owners and reviewers

/assign @divya-mohan0209 @natalisucks

I initially included GitHub users Mouly22 and ikramulkayes as Bengali owners and reviewers but they are not Kubernetes org members

I'm closing this PR and will recreate this PR once the Bengali localization is ready to go live with at least 2 owners who are Kubernetes org members
/close

Hey, @reylejano we have got our 2nd reviewer @Imtiaz1234 . Can you add him to the owners  file?


Added 'deprecated' tag to 'microsoft.dem'

@stevemunk - It looks like your branch has developed a conflict. You'll need to resolve this before we can review the PR.


[Event Request] Codeunit 22 Item Jnl.-Post Line - Function InitValueEntry

Dear ALAppExtensions Team,
We would like to request the following event publisher in codeunit 22 Item Jnl.-Post Line - Function InitValueEntry
               if ("Invoiced Quantity" < 0) and ("Applies-to Entry" <> 0) and
                   ("Entry Type" = "Entry Type"::Purchase) and ("Item Charge No." = '') and
                   (ValueEntry."Entry Type" = ValueEntry."Entry Type"::"Direct Cost")
                then begin
                    CalcPurchCorrShares(OverheadAmount, OverheadAmountACY, VarianceAmount, VarianceAmountACY);
                    OnAfterCalcPurchCorrShares(
                      ValueEntry, ItemJnlLine, OverheadAmount, OverheadAmountACY, VarianceAmount, VarianceAmountACY);
                end;
            end
            // DINNL <<
            ;
            DINOnCalcDirectCost(CostAmt, Item, ItemJnlLine,
           (Item."Costing Method" = Item."Costing Method"::Standard) and (not ValueEntry."Expected Cost"),
           VarianceAmount, ValueEntry."Expected Cost");
            // DINNL >>
        end else begin
            CostAmt := "Unit Cost";
            CostAmtACY := "Unit Cost (ACY)";
        end;

local procedure DINOnCalcDirectCost(var DirCost: Decimal; Item: Record Item; ItemJnlLine: Record "Item Journal Line"; CalcPurchVar: Boolean; var VarianceAmount: Decimal; Expected: Boolean)

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one.


crypto/aes: add dedicated asm version of AES, AES-GCM for arm64

Add a dedicated asm version of AES, AES-GCM for arm64 - utilizing ARMv8-A crypto extension when available.
It should be noted that an asm accelerated version of this algorithm, utilizing AES-NI when available,  exists for amd64.

A partial implementation seems to have been developed under changelist:
https://go-review.googlesource.com/#/c/32579/

Any chance to be targeted for 1.9?

@cherrymui, is this something you could review?

I am not familiar with the algorithm. I may be able to review in terms of whether the assembly version and the Go version are equivalent. Probably not so fast though.

There's related wrok here https://github.com/minio/sha256-simd/ and this open issue there for upstream support https://github.com/minio/sha256-simd/issues/7

I agree it's "related" in that they both accelerate crypto things, and they
are both nice to haves, but sha256 acceleration should be filed as a
separate issue.
On 27 March 2017 at 07:03, Edward Vielmetti<EMAIL_ADDRESS>wrote:

There's related wrok here https://github.com/minio/sha256-simd/ and this
open issue there for upstream support minio/sha256-simd#7
https://github.com/minio/sha256-simd/issues/7
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/golang/go/issues/18498#issuecomment-289361249, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAUR3thfZBFUp5-nLRyl2Blm9gW6gKW-ks5rp1EegaJpZM4LZeXN
.

A partial fix here: https://go-review.googlesource.com/c/go/+/64490

On arm64, Packet Type 2A / c1.large.arm Cavium ThunderX:
ed@ed-2a-bcc-llvm:~$ go test crypto/cipher -bench GCM

goos: linux
goarch: arm64
pkg: crypto/cipher
BenchmarkAESGCMSeal1K-96           20000             68788 ns/op          14.89 MB/s
BenchmarkAESGCMOpen1K-96           20000             68697 ns/op          14.91 MB/s
BenchmarkAESGCMSign8K-96           10000            182114 ns/op          44.98 MB/s
BenchmarkAESGCMSeal8K-96            3000            536359 ns/op          15.27 MB/s
BenchmarkAESGCMOpen8K-96            3000            537432 ns/op          15.24 MB/s
PASS
ok      crypto/cipher   9.404s
ed@ed-2a-bcc-llvm:~$
ed@ed-2a-bcc-llvm:~$ go version
go version go1.10.2 linux/arm64
ed@ed-2a-bcc-llvm:~$ ~/go/bin/go1.11beta1 test crypto/cipher -bench GCM
goos: linux
goarch: arm64
pkg: crypto/cipher
BenchmarkAESGCMSeal1K-96           50000             37520 ns/op          27.29 MB/s
BenchmarkAESGCMOpen1K-96           50000             37550 ns/op          27.27 MB/s
BenchmarkAESGCMSign8K-96           10000            172278 ns/op          47.55 MB/s
BenchmarkAESGCMSeal8K-96            5000            289794 ns/op          28.27 MB/s
BenchmarkAESGCMOpen8K-96            5000            288511 ns/op          28.39 MB/s
PASS
ok      crypto/cipher   9.274s

1.11beta1 is substantially faster than 1.10.2.

So excited to see this merge! https://go-review.googlesource.com/c/go/+/107298

Thanks so much for the hard work on this!


Provide the link or reference

Description:
The current quick start page provides instructions on how to publish a new API. As an example, wso2 using a mock HTTP API and there is a note on HTTPS on the requirement of importing the cert.
If the referral link shared in the note itself, it will be helpful to locate the instruction right away!

Suggested Labels:
Improvement, Suggestions

Closing the issue, as the fix is provided.


Add Media-Upload Sample to NodeJS

Fixes #10.
This commit adds 'media' object to requests that allows media upload.
This addresses some of compilecheck's warnings.

cc @vchudnov-g

LGTM


Add schema validation to devfile community registry

What does this PR do?:

Adds schema validation to the devfile community registry.
Updates workflows to use a delta between origin/main and main to find the modified devfiles on PRs.

odo v2
odo v3
non-terminating images
schema validation
openshift ci test (uses odo v2 test)

Workflows on a schedule will still test all devfiles.
Adds a workflow status badge to the README.
Adds multiversion support to the tests.

Which issue(s) this PR fixes:
fixes https://github.com/devfile/api/issues/939
related https://github.com/devfile/api/issues/757
PR acceptance criteria:

[x] Contributing guide
Have you read the devfile registry contributing guide and followed its instructions?
[x] Test automation
Does this repository's tests pass with your changes?
[ ] Documentation
Does any documentation need to be updated with your changes?
[x] Check Tools Provider
Have you tested the changes with existing tools, i.e. Odo, Che, Console? (See devfile registry contributing guide on how to test changes)

How to test changes / Special notes to the reviewer:

/retest

/uncc

replaces https://github.com/devfile/registry/pull/141

/retest


Include SPDX license info in project metadata

A license entry in the project metadata makes it easier to detect the license of a project.
Before:
$ pip install pip-licenses outlines
$ pip-licenses  | grep outlines
 outlines                   0.0.46       UNKNOWN

After:
$ pip install .
$ pip-licenses  | grep outlines
 outlines                   0.0.47.dev43+g8b78f5d  Apache-2.0

Thank you so much, both for teaching me something, and improving the library.

 Thanks for merging the PR in record time. :+1:


Close when click outside Popup

Is there a way to config this? So when the user tap/clicks outside the popup it closes itself?

No, you can only close the popup with the button present on the popup or modal only.


Add tests for string and id variants

Use different parameter sets

Hi,
I'm currently trying to use a custom id on a schema, I have checked out what looks like the commit for this issue, but can't get it to work. If I set the id in the schema as anything other than integer it does not set it as a primary key, I can run a sql migration insert, but I cannot add any more rows after that.
If I set up the table using a postgres migration, I can input pre-existing data, I can query, edit and delete and the model.save() runs without error but does not actually save to the DB. Because you are sending it in with an ID the update function is called instead of the create within the sync.js file of backbone-orm module. Before I edit this function, am I missing something?
I would prefer to set up the table using the backbone module, in the same way as other tables I have created.
Is there any documentation for this case?
Thanks.


Fix router schema and examples

/cc @bgentry @benburkert

That looks like it makes much more sense :) Sorry I missed the examples.json previously!
LGTM

LGTM


[NETBEANS-1075]-Adding var hints for enhanced-for-loop

In cases of enhanced for loops :
for (String s : stringArray) {         // Nothing }
Hint to change "String" s to "var" and vice versa in appropriate cases would be available.
The hints are available for primitive types as well.

Is this ready, can it be merged?

@geertjanw , we can merge this as soon as Reema reviews this.

I have tested var related tests with the new changes and all of them seem to be passing.

OK, let's merge. Thanks a lot for your hard work on this!


Unable to disable spacy pipeline components

From spacy 2.x doc (https://spacy.io/usage/processing-pipelines#disabling),
in order to disable spacy pipeline components, it uses the "disable" argument. For example,
nlp = spacy.load(spacy_model_name, disable=['parser', 'tagger', 'ner'])
However, in utils/spacy_utils.py, it is
nlp = spacy.load(spacy_model_name, parser=False)
which seems to be obsolete.
I wonder if I could do the disabling in rasa_nlu config file. Thanks.

Thanks for raising this issue, @Ghostvv  will get back to you about it soon.

this functionality is not supported from config, you would need to write a custom component


Network responses are displayed twice

Also mentioned in this thread:
https://groups.google.com/forum/#!topic/firebug/S_xl207pDCo
Happens if a custom tab actor is registered.
STR1:

Enable remote logging here: https://github.com/firebug/firebug.next/commit/da32a47300192f28324157a47a29688b3002eb0a#commitcomment-10679192
Load this page: https://getfirebug.com/tests/head/net/601/issue601.html
Make sure the Console panel is selected by default
Press the POST button on the page, there is one request displayed
Select the Network panel and go back to the Console panel
Press the POST button on the page, there are two requests displayed -> BUG

STR2:

Install Firebug.next + FireQuery
Load this page: https://getfirebug.com/tests/head/net/601/issue601.html
Make sure the Console panel is selected by default
Press the POST button on the page, there is one request displayed
Select the Network panel and go back to the Console panel
Press the POST button on the page, there are two requests displayed -> BUG

Honza

Corresponding platform bug:
https://bugzilla.mozilla.org/show_bug.cgi?id=1155168
Honza

I've fixed the platform bug and the patch is now in Nightly
Closing this report too.
Honza


Add sample icon

Like a lot of other people I'm having trouble getting the notification icon in the STATUS BAR to work. According to the documentation it should work by specifying this in the init function, however I just keep getting a white/gray square there.
Perhaps someone can provide a sample project where this is working properly?

@rubenstolk does the icon you specify in init have any transparency?

@macdonst Yes it does, it it not supposed to have?

@rubenstolk Android 5.0 and later will take your icon and completely white wash the icon, i.e. replace each non-white pixel with a white pixel except for the transparent pixels. It's explained here:
https://github.com/phonegap/phonegap-plugin-push#images
https://www.google.com/design/spec/style/icons.html#
You can use the attached phonegap icon which has transparency as know working test icon.

You'll need to copy the image to <project>/platforms/android/res/drawable, rename it phonegap.png and call init with the following parameter:
var push = PushNotification.init({
        "android": {
            "senderID": "Your Sender ID", "icon": "phonegap", "iconColor": "blue"},
        "ios": {"alert": "true", "badge": "true", "sound": "true"}, "windows": {}
    });

and then you should get an icon that doesn't look like a white square in the status bar.

Right, so I had an icon with only white and transparent, if I understand correctly, I have to make everything that is transparent black... Will try that!

@rubenstolk can you send me your icon so I can take a look?

Give me 10 minutes, it seems the actual issue was that I was using drawables folder instead of drawable. Trying my way out now and will let you know!

@macdonst  Not work for me..  if (ionic.Platform.isAndroid()) {         config = {           "senderID": "290439193995",           "icon": "phonegap",           "iconColor": "blue"         };       }
what am I doing wrong ? :S

@Fr4ncx well is the "phonegap.png" file copied to platforms/android/res/drawables?

yes but not work for me..

It's in the drawable directory. for example platforms/android/res/drawable/notification.png
then:
     const pushOpt: PushOptions = {
        android: {
          senderID: PUSH_SENDER_ID,
          // image file should be located in the Android drawables folder
          icon: 'notification',
          iconColor: '#484848'
        }
      };

See the source code:
https://github.com/phonegap/phonegap-plugin-push/blob/630907cf3d8802bcd5d91b6bd768c989f6ef897a/src/android/com/adobe/phonegap/push/PushConstants.java#L19
https://github.com/phonegap/phonegap-plugin-push/blob/3acdfa338d7a8b56ec4dc73c50aa9917ecb3be7c/src/android/com/adobe/phonegap/push/GCMIntentService.java#L506
I made a PR to fix this confusion in the Docs: https://github.com/phonegap/phonegap-plugin-push/pull/1711


Do not support IntelliJ idea 15?

can not formate the java code accurately when run plugin.

Turn off the plugin, restart IDEA and turn on the plugin again. After that plugins seems to work again.

That's strange... :(

I have similar problem in Intellij 15/16 EAP. Configuration tab "Settings | Other Settings | Eclipse Code Formatter" is not there anymore. Turning off/on the plugin didn't help. Any ideas?

Same problem as vehovmar happening on Clion EAP build 144.3143.4. I cannot access the Other Settings Tab. Any workarounds?

Did you try to reinstall the plugin? Is there anything in the log?
I will probably try it myself tommorow...

Reinstalling had no effect. I do not see anything in the event log unless there is some other log I should check.

Reinstall didn't help me either.

Working on fix... they broke almost all my plugins :(

fixed, i will release it soon, testers welcomed :] https://github.com/krasa/EclipseCodeFormatter/releases/download/<IP_ADDRESS>7.0/EclipseFormatter.zip

Works for me! Thanks!

Works also for me, thanks.

The fix worked for me. Thanks!