set default_branch in .github/settings.yml

[ ] lets start by setting to master
[ ] follow up by prompting for a choice (maybe keep it simple to start with by providing a static list with master and main as choices?)
[ ] default to main once we work out any quirks that we find

transferred from https://github.com/travi/github-scaffolder/issues/223


cakephp 4.x version

Why this project disabled in travis?

@skie Probably because I accidentally logged into travis-ci.com one time. I'll get that fixed.

Thank you :clap:


Out of bound exception when reading fron paged block store

Alluxio Version:
current master
Describe the bug
ArrayIndexOutOfBoundsException when doing random reads from a paged block.
2022-08-02 06:35:49,058 DEBUG BlockReadHandler - Exception occurred while reading data for read request BlockReadRequest{chunkSize=1048576, end=14830815, id=16777216, openUfsBlockOptions=ufs_path: “hdfs://BlockStorePerfPage-master-0:9000/alluxio_ufs/stress-worker-bench-base/data0”
offset_in_file: 0
block_size: 20971520
maxUfsReadConcurrency:<PHONE_NUMBER>
mountId: 1
no_cache: false
, promote=false, sessionId=1871510110820781136, start=14789855, positionShort=true}. session<PHONE_NUMBER>820781136
java.lang.ArrayIndexOutOfBoundsException
        at java.lang.System.arraycopy(Native Method)
        at alluxio.worker.page.PagedBlockReader.read(PagedBlockReader.java:107)
        at alluxio.worker.grpc.BlockReadHandler$DataReader.getDataBuffer(BlockReadHandler.java:528)
        at alluxio.worker.grpc.BlockReadHandler$DataReader.runInternal(BlockReadHandler.java:407)
        at alluxio.worker.grpc.BlockReadHandler$DataReader.run(BlockReadHandler.java:369)
        at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
        at java.util.concurrent.FutureTask.run(FutureTask.java:266)
        at alluxio.worker.grpc.GrpcExecutors$ImpersonateThreadPoolExecutor.lambda$execute$0(GrpcExecutors.java:144)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
        at java.lang.Thread.run(Thread.java:750)

To Reproduce
Steps to reproduce the behavior (as minimally and precisely as possible)
Expected behavior
A clear and concise description of what you expected to happen.
Urgency
Describe the impact and urgency of the bug.
Are you planning to fix it
Please indicate if you are already working on a PR.
Additional context
Add any other context about the problem here.

@beinan FYI. Not sure if it's related 3d205d8119c4de95971e49a153a2427ebf01ae11

The reproduce method is:

set alluxio.worker.network.reader.buffer.pooled as false;
use PAGE as the block store.
client calls  public int read(long position, byte[] buffer, int offset, int length)

The change of https://github.com/Alluxio/alluxio/commit/3d205d8119c4de95971e49a153a2427ebf01ae11 is on the write path, so I guess it won't be related.

By running several clusters, we find that:

alluxio.worker.network.reader.buffer.pooled
write mode
error?

true
sequential read
No

false
sequential read
No

true
random read
No

false
random read
Yes


[NCL-8173] Implement nested tabs

Will be applied on Group Build detail page once https://github.com/project-ncl/pnc-web-ui-react/pull/302 is merged.

Hi @DnsZhou , can you please do a code-review for this one?


Created eslint.yml file

Created workflows folder under .github directory with the eslint.yml file inside
Naming Rules
Name your PR like this: ISSUENUMBER-TITLE-YOURNAME
Description
Write a summary of your change. Explain why you have made it.
Related to
Make sure you include the issue number with a hash sign # so Github can link this PR to the right issue, like this:
Fixes #1
Checklist:

[ ] My code follows the style guidelines of this project
[ ] I have carefully reviewed my own code
[ ] I have commented my code
[ ] I have updated any documentation

looks good, you may want to run the fix but this is the epected behaviour


hlo-legalize-to-linalg is incorrect for mhlo::DotGeneralOp

The usage of i in https://github.com/tensorflow/tensorflow/blob/master/tensorflow/compiler/mlir/hlo/lib/Dialect/mhlo/transforms/legalize_to_linalg.cc#L2945 and https://github.com/tensorflow/tensorflow/blob/master/tensorflow/compiler/mlir/hlo/lib/Dialect/mhlo/transforms/legalize_to_linalg.cc#L2970 is incorrect.  You need another index, say j that only increments when assigned_dims[i] is false.
Suggested fix
      for (int i = 0, j = 0; i < lhs_rank; ++i) {
        if (!assigned_dims[i]) {
          lhs_indices[i] =
              rewriter.getAffineDimExpr(j + lhs_batching_dims.size());
              j++;
        }
      }

and similarly for the corresponding loop for RHS map.  Here's a test case
func.func @dot_general_2(%arg0: tensor<64x16x128x32xf32>,
                  %arg1: tensor<16x256x32x128xf32>) -> tensor<16x32x64x256xf32> {
  %0 = "mhlo.dot_general"(%arg0, %arg1) {
    dot_dimension_numbers = #mhlo.dot<
      lhs_batching_dimensions = [1, 3],
      lhs_contracting_dimensions = [2],
      rhs_batching_dimensions = [0, 2],
      rhs_contracting_dimensions = [3]
    >,
    precision_config = [#mhlo<"precision DEFAULT">, #mhlo<"precision DEFAULT">],
    someattr
  } : (tensor<64x16x128x32xf32>, tensor<16x256x32x128xf32>) -> tensor<16x32x64x256xf32>
  func.return %0 : tensor<16x32x64x256xf32>
}
// The iterations are (Batch Dim, Batch Dim, LHS Other Dim, RHS Other dim, Contracting Dim)
// CHECK: #[[MAP0:.*]] = affine_map<(d0, d1, d2, d3, d4) -> (d2, d0, d4, d1)>
// CHECK: #[[MAP1:.*]] = affine_map<(d0, d1, d2, d3, d4) -> (d0, d3, d1, d4)>
// Output is the iterators excluding contracting
// CHECK: #[[MAP2:.*]] = affine_map<(d0, d1, d2, d3, d4) -> (d0, d1, d2, d3)>
// CHECK: func @dot_general_2(
// CHECK-SAME: %[[ARG0:.*]]: tensor<64x16x128x32xf32>, %[[ARG1:.*]]: tensor<16x256x32x128xf32>)
// CHECK: %[[INIT:.*]] = linalg.init_tensor [16, 32, 64, 256]
// CHECK: %[[FILL:.*]] = linalg.fill ins(%{{.*}}{{.*}}outs(%[[INIT]]
// CHECK: linalg.generic
// CHECK-SAME: indexing_maps = [#[[MAP0]], #[[MAP1]], #[[MAP2]]]
// Only contracting dims are reductions
// CHECK-SAME: iterator_types = ["parallel", "parallel", "parallel", "parallel", "reduction"]
// CHECK-SAME: ins(%[[ARG0]], %[[ARG1]] : tensor<64x16x128x32xf32>, tensor<16x256x32x128xf32>)
// CHECK-SAME: outs(%[[FILL]] : tensor<16x32x64x256xf32>)
// CHECK-SAME: {someattr}
// CHECK:   ^bb0(%[[ARG2:.*]]: f32, %[[ARG3:.*]]: f32, %[[ARG4:.*]]: f32):
// CHECK:     %[[MUL:.*]] = arith.mulf %[[ARG2]], %[[ARG3]] : f32
// CHECK:     %[[SUM:.*]] = arith.addf %[[MUL]], %[[ARG4]] : f32
// CHECK:     linalg.yield %[[SUM]] : f32
// CHECK: } -> tensor<16x32x64x256xf32>

It might be worth considering adding even more test cases, as obviously the current coverage isn't enough.

Hello @srcarroll ,
I request you,can you please feel free to submit a PR for the requested change is to be made.Thanks!

Yes I can do that.  However, the issue is that I need to contribute from my work account which will require some amount of bureaucracy.  This is why I decided to post the fix here, since it's a very small change.  If this can wait, I'd be happy to submit a PR after we get things sorted out.

@srcarroll ,
As suggested I request you,can you please feel free to submit a PR for the requested change is to be made.Thanks!

I have been given the go ahead to do this from my personal account so I will submit a PR soon.

I submitted a PR here already https://github.com/tensorflow/tensorflow/pull/55722

@srcarroll ,
The PR has been assigned for reviewing and once it is merged this issue will move to closed status.Thanks!

@srcarroll ,
Related PR has been closed.Can you please feel free to move this issue to closed status.Thanks!


StealthOne support is broken

Nothing shows up

Moved S1 code from incorrect telephone receiver subsystem to the correct IKE subsystem as the messages come from the phone and go to the IKE, not the other way. Duh.


NO Entry Point for Kernel Drivers

There is no entry point for kernel drivers. How can I get rid of this nasty pseudo error message LNK1561???
[Enter feedback here]

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

ID: 361ad94f-165c-a218-a436-0046f7b23416
Version Independent ID: 95aef15e-dd24-cc35-934a-e10c81d8e154
Content: /ENTRY (Entry-Point Symbol)
Content Source: docs/build/reference/entry-entry-point-symbol.md
Product: visual-cpp
Technology: cpp-tools
GitHub Login: @corob-msft
Microsoft Alias: corob

@Mike191919
Sorry you're having trouble. This is a support question, not a documentation question. You shouldn't need to use the /ENTRY option on a kernel driver. If the linker reports LNK1561 on a kernel driver project then there's something wrong with the way your project is set up. Did you start with an app or DLL project template and edit it to create a driver project? I'd recommend you recreate the project as a kernel driver project and copy the code over. Best of luck with your code.


Inference in NDarray reshape.

Makes shape the default parameter in nd.reshape (rather than the current deprecated target_shape) so that the function behaves as expected (e.g. mx.nd.reshape(X, (1, -1)) works as expected).
Added support for shape inference (-1) on NDarray objects (e.g. for an array X, X.reshape((-1, )) works as expected).

Sorry meant to pull request the main mxnet repo.


CHEBI:144321 wrong formula

CHEBI:144321 is named a residue but none of the residues should have an InChi key, if I understand correctly. The entity associated with the SMILES is rather a compound (it contains no stars).
What is a puzzle to me however is that the formula still contains placeholders. Can you please clarify?

I just noted that the definition writes "hepatitUs" not hepatitIs

This has now been corrected. Thanks


data Tevatron/msmarco-passage

hi,where is the data Tevatron/msmarco-passage

Hi,
This is the name for the Tevatron internal dataset, Tevatron will automatically download and process it and store it in a cache folder.

Thank you for your prompt reply


How can I set specific format for Columns ?

Hi how are you ?
I need format the columns that have numeric values, including monetary symbol. But, I can have in same pivot table, different columns, that must have different formats, one can be money, other can be percent and etc.
I believe, using "" I can do that, but, I dont know how can I check what field are to apply the specific format.
Can you help-me ?
Thanks a lot

Hi :) I have the same issue and it is indeed very tricky. (the whole library is tricky but this one in particuliar)
It is currently not possible.
To solve this problem I introduced additional parameters to the value slot: col and row. They allow you to get the values of the columns/rows for the current cell.
The idea is that if you have for example a specific row or column value that should generate a row or column formatted as a currency, you will want to provide a value slot like:
<template v-slot:value="{ value, col, row }">
  <template v-if="checkIfCurrency(col, row)">{{ value | currency }}</template>
  <template v-else>{{ value }}</template>
</template>

But the checkIfCurrency doesn't know the order of the rows/columns, so it doesn't know which part of the col/row arguments corresponds to the column that has a currency value.
I think I need to provide a way to get the row/column fields selected by the user, so that this function can check the right value.

Hi antoinematyja ,
In my case, if I try use a function similar to "checkIfCurrency, the parameters col and row, are undefined.
I dont know wy.

You are probably using an old version, these parameters were added in v0.2.1. Can you tell me what version you are using ?
Also I just released v1.0.0 which changed a little bit the Pivot component API, now the row/col provide arrays instead of objects.

Its true, Im using the version 0.0.1, because I  created my project based on the project of "mitsakosgr" , he create a solution that allow I can use different algoritms by Colfield.
I will try merge the solutions, and after solve this problem.
In my local solution, I implemented grand total by grouping, after merge, I share with you.
Thanks a lot

antoinematyja how are you ?
i got it to format the columns in another way. I created an hash that stores the columns key that have slotName, like implemented in rowFields, and I use a similar method like "value" to retrieve the slotName of column. In this way, I need when I use the pivotTable component, list one slot per column field.
Thanks for your help


Remove WorkQueue spec from workqueue db

Use spec from request manager.

@alexanderrichards, Hi Alex could look at this problem.
We keep the same information in 2 different places.
https://cmsweb.cern.ch/couchdb/reqmgr_workload_cache/pdmvserv_task_EXO-RunIISummer15wmLHEGS-04951__v1_T_170913_201940_8297/spec
and
https://cmsweb.cern.ch/couchdb/workqueue/pdmvserv_task_EXO-RunIISummer15wmLHEGS-04951__v1_T_170913_201940_8297/spec
We like to just keep the data in one place. (The first one reqmgr_workload_cache)
Second data is used in WorkQueueManager component.
The patch should contain.

remove the code for creating workqueue spec data.
change the code using workqueue spec data to use reqmgr_workload_cache data

I will dig into the code to find where it happens next week.

I think that for 1. at least it's probably located here:
WorkQueueBackend.py#L111


Adding «Creatives To Follow» endpoint and small fixes to other

List of changes:

Introducing CHANGELOG.md.
Creatives To Follow Endpoint added.
@client.popular retrieves all Creative Fields (in 'popular').
@client.user_appreciations, @client.user_collections and @client.wip_revision_comments now accepts options hash.
@client.user_followers and @client.user_following added.

P. S. I've also bumped VERSION to 0.6.0. Please make a tag.
P. P. S. This PR dedicated to #hacktoberfest!

Great work @toydestroyer! The gem is published now.


[app] cannot read property getScrollableNode of undefined

trying to install v.15.0.0 on mac, web works fine, but ios always have error:

Cannot read property 'getScrollableNode' of undefined
Unhandled JS Exception: Cannot read property 'getScrollableNode' of undefined
Possible Unhandled Promise Rejection (id: 0):
RelayQL: Unexpected invocation at runtime. Either the Babel transform was not set up, or it failed to identify this call site. Make sure it is being used verbatim as Relay.QL.
Invariant Violation: RelayQL: Unexpected invocation at runtime. Either the Babel transform was not set up, or it failed to identify this call site. Make sure it is being used verbatim as Relay.QL.

everything fine :) My issue was result  'react-native upgrade' this command can rewrite .babelrc and remove babel plugin settings

Unfortunately I have not worked on transferring the native code to the new boilerplate - it should mostly work from the previous boilerplate, but the GraphQL names should be changed. Also, I will separate the app into distinct units instead of bundling everything by functionality like in the previous version.


My app craches on IOS, problems with memory

flutter doctor -v
[✓] Flutter (Channel stable, 2.0.0, on Mac OS X 10.15.7 19H15 darwin-x64, locale en)
    • Flutter version 2.0.0 at /Users/hellomik/development/flutter
    • Framework revision 60bd88df91 (2 days ago), 2021-03-03 09:13:17 -0800
    • Engine revision 40441def69
    • Dart version 2.12.0

[✓] Android toolchain - develop for Android devices (Android SDK version 30.0.2)
    • Android SDK at /Users/hellomik/Library/Android/sdk
    • Platform android-30, build-tools 30.0.2
    • Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6222593)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 12.4, Build version 12D4e
    • CocoaPods version 1.10.1

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 4.0)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin version 47.1.2
    • Dart plugin version 193.7361
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6222593)

[✓] IntelliJ IDEA Ultimate Edition (version 2020.2.3)
    • IntelliJ at /Applications/IntelliJ IDEA.app
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart

[✓] IntelliJ IDEA Community Edition (version 2020.2.3)
    • IntelliJ at /Applications/IntelliJ IDEA CE.app
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart

[✓] VS Code (version 1.53.2)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.20.0

ERROR
* thread #80, queue = 'com.Metal.CommandQueueDispatch', stop reason = EXC_RESOURCE RESOURCE_TYPE_MEMORY (limit=1450 MB, unused=0x0)
    frame #0: 0x00000001d3c06644 libsystem_kernel.dylib`mach_msg_trap + 8
libsystem_kernel.dylib`mach_msg_trap:
->  0x1d3c06644 <+8>: ret
libsystem_kernel.dylib`mach_msg_overwrite_trap:
    0x1d3c06648 <+0>: mov    x16, #-0x20
    0x1d3c0664c <+4>: svc    #0x80
    0x1d3c06650 <+8>: ret

HI @Hellomik2002
Which device are you experiencing this issue on? Device details  are omitted from your fluter doctor -v
Can you please provide flutter run --verbose logs (paste the log in a text file and drop it in the comment below), and a minimal complete reproducible code sample?
Thank you

Without additional information, we are unfortunately not sure how to resolve this issue.
We are therefore reluctantly going to close this bug for now.
Please don't hesitate to comment on the bug if you have any more information for us; we will reopen it right away!
Thanks for your contribution.
Could everyone who still has this problem please file a new issue with the exact description of what happens, logs, and the output of flutter doctor -v.
All system setups can be slightly different, so it's always better to open new issues and reference related issues.


Added Contributor's Page

Issue Solved: #1145
I developed and optimized the Contributor Page, focusing on enhancing user experience, responsiveness, and performance.
Page Development:
a. Design and Layout: Crafted a visually appealing and user-friendly layout for the Contributor Page, ensuring consistency
with the overall theme of the website.
b. Fetching Contributor Data: Implemented functionality to fetch and display contributor data from the GitHub API. This
involved asynchronous data fetching, error handling for rate limits, and dynamically generating contributor cards.
c. DOM Manipulation: Optimized the DOM manipulation process to reduce reflow and repaint operations, resulting in
smoother and faster rendering of contributor information.
d. Caching: Added local storage caching to store contributor data, reducing the need for repeated API requests and
improving load times for returning users.
Responsiveness:
a. Responsive Design: Made the Contributor Page fully responsive, ensuring an optimal viewing experience across various
devices and screen sizes.
b. Mobile Optimization: Ensured that the layout, images, and text adapt seamlessly on mobile devices, providing a consistent
and intuitive user experience.
Adding the contributor option in the footer in order to easily navigate to the contributor page.
On clicking to the profile picture , we can navigate directly to their github account.
https://github.com/user-attachments/assets/1514c08d-3148-4fb4-bced-62a35e96a583
https://github.com/user-attachments/assets/8a84c64b-6298-47db-b31f-b36693890bfb

@Its-Aman-Yadav @Kalivarapubindusree ,
Please review this PR,
Thank You!

Kindly resolve conflicts @TBorundia

Kindly resolve conflicts @TBorundia

@Its-Aman-Yadav Sir, Please check it now.
I have resolved conflicts.


[Feature] Add taking screenshots-on-failure config property

Node.js has screenshots-on-failure property in config that you can use to take screenshot upon failure. This is especially useful when you run headless or in container

This is a part of the Playwright Test runner which is only available in Node.js version. In java we recommend using existing testing frameworks with their runners (JUnit, TestNG etc.). I'm closing this issue as there are no plans to bring that support into java but if we decide to port test runner functionality to java it is definitely at the top of the feature list.


My match statistics do not take into account in ranking

14 days ago i played as Juggernaut and got the highest gpm/xpm, dmg/sec, etc, but these statistics do not take into account in my rankings
My ranking - https://www.opendota.com/players/158519110/rankings?hero_id=8
Match - https://www.opendota.com/matches/2880758066
Same problems with some other matches
-- Windows 10
-- Opera browser/newest version

Stats do not affect ranking, only wins and average MMR in the match do.
You can read more about it here: http://blog.opendota.com/2016/09/30/explaining-rankings/


NTR: XMP 5-nucleosidase activity

Please provide as much information as you can:

Suggested term label:
XMP 5-nucleosidase activity

Definition (free text)
RHEA 28530

Reference, in format PMID:#######
PMID:34824243

Gene product name and ID to be annotated to this term
AGI_LocusCode:AT2G32150

Parent term(s)

Children terms (if applicable) Should any existing terms that should be moved underneath this new proposed term?

Synonyms (please specify, EXACT, BROAD, NARROW or RELATED)

Cross-references

For enzymes, please provide RHEA and/or EC numbers.

Can also provide MetaCyc, KEGG, Wikipedia, and other links.

Any other information

@hdrabkin  submitted request

Yep I see it now!
From: lreiser @.>
Reply-To: geneontology/go-ontology @.>
Date: Wednesday, December 1, 2021 at 11:23 AM
To: geneontology/go-ontology @.>
Cc: me @.>, Mention @.***>
Subject: [EXTERNAL]Re: [geneontology/go-ontology] NTR: XMP 5-nucleosidase activity (Issue #22500)
@hdrabkinhttps://github.com/hdrabkin submitted request
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/geneontology/go-ontology/issues/22500#issuecomment-983807622, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ACPU3EHYITJ2AUZL4G33JC3UOZDXBANCNFSM5JE4XERA.
Triage notifications on the go with GitHub Mobile for iOShttps://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Androidhttps://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
The information in this email, including attachments, may be confidential and is intended solely for the addressee(s). If you believe you received this email by mistake, please notify the sender by return email as soon as possible.

+id: GO:0106411
+name: XMP 5'-nucleosidase activity
+namespace: molecular_function
+def: "Catalysis of the reaction: 5'XMP + H20 = phosphate + xanthosine." [PMID:34824243, RHEA:28530]
+xref: EC:<IP_ADDRESS> {source="skos:broadMatch"}
+xref: MetaCyc:XMPXAN-RXN {source="skos:exactMatch"}
+xref: RHEA:28530 {source="skos:exactMatch"}
+is_a: GO:0008253 ! 5'-nucleotidase activity
+property_value: creation_date 2021-12-01T16:29:52Z xsd:dateTime
+created_by: hjd


Error when deleting too many repositories

Description
When attempting to delete many repositories e.g. >20, this could be observed in the console.
Uncaught (in promise) SyntaxError: Unexpected token 'A', "An error o"... is not valid JSON

It seems to be caused by GitHub's API
Solution

To log out the error in full
Error handling & retry request

Will be taking a look at this


Problem getting it to work with Rhino 6

This is a continuation of the comment I left on the plugin page. I created rhinoremote2 virtualenv and it installed fine. No errors apart from deprecation warnings. This is the full error message when I try and run the example file (Ì changed the location to conda://rhinoremote2)
DEBUG: ghpythonremote.connectors:
Using python executable: C:\Users\john\.conda\envs\rhinoremote2\python.exe
DEBUG: ghpythonremote.connectors:
Using rpyc_server module: C:\Users\john\AppData\Roaming\McNeel\Rhinoceros\6.0\Plug-ins\IronPython (814d908a-e25c-493d-97e9-ee3861957f49)\settings\lib\ghpythonremote\pythonservice.py
DEBUG: ghpythonremote.connectors:
Using port: 52348
DEBUG: ghpythonremote.connectors:
Using log_level: DEBUG
DEBUG: ghpythonremote.connectors:
Using working_dir: C:\Users\john\AppData\Roaming\Grasshopper\UserObjects\gh-python-remote\examples
INFO: ghpythonremote.connectors:
Connecting...
DEBUG: ghpythonremote.connectors:
Connecting. Timeout in 10 seconds.
Runtime error (EndOfStreamException): EOFError

Traceback:
  line 55, in recv, "C:\Users\john\AppData\Roaming\McNeel\Rhinoceros\6.0\Plug-ins\IronPython (814d908a-e25c-493d-97e9-ee3861957f49)\settings\lib\rpyc\core\channel.py"
  line 100, in value, "C:\Users\john\AppData\Roaming\McNeel\Rhinoceros\6.0\Plug-ins\IronPython (814d908a-e25c-493d-97e9-ee3861957f49)\settings\lib\rpyc\core\async_.py"
  line 76, in syncreq, "C:\Users\john\AppData\Roaming\McNeel\Rhinoceros\6.0\Plug-ins\IronPython (814d908a-e25c-493d-97e9-ee3861957f49)\settings\lib\rpyc\core\netref.py"
  line 161, in __getattribute__, "C:\Users\john\AppData\Roaming\McNeel\Rhinoceros\6.0\Plug-ins\IronPython (814d908a-e25c-493d-97e9-ee3861957f49)\settings\lib\rpyc\core\netref.py"
  line 217, in _install, "C:\Users\john\AppData\Roaming\McNeel\Rhinoceros\6.0\Plug-ins\IronPython (814d908a-e25c-493d-97e9-ee3861957f49)\settings\lib\rpyc\core\service.py"
  line 213, in on_connect, "C:\Users\john\AppData\Roaming\McNeel\Rhinoceros\6.0\Plug-ins\IronPython (814d908a-e25c-493d-97e9-ee3861957f49)\settings\lib\rpyc\core\service.py"
  line 105, in _connect, "C:\Users\john\AppData\Roaming\McNeel\Rhinoceros\6.0\Plug-ins\IronPython (814d908a-e25c-493d-97e9-ee3861957f49)\settings\lib\rpyc\core\service.py"
  line 44, in connect_channel, "C:\Users\john\AppData\Roaming\McNeel\Rhinoceros\6.0\Plug-ins\IronPython (814d908a-e25c-493d-97e9-ee3861957f49)\settings\lib\rpyc\utils\factory.py"
  line 56, in connect_stream, "C:\Users\john\AppData\Roaming\McNeel\Rhinoceros\6.0\Plug-ins\IronPython (814d908a-e25c-493d-97e9-ee3861957f49)\settings\lib\rpyc\utils\factory.py"
  line 99, in connect, "C:\Users\john\AppData\Roaming\McNeel\Rhinoceros\6.0\Plug-ins\IronPython (814d908a-e25c-493d-97e9-ee3861957f49)\settings\lib\rpyc\utils\factory.py"
  line 75, in connect, "C:\Users\john\AppData\Roaming\McNeel\Rhinoceros\6.0\Plug-ins\IronPython (814d908a-e25c-493d-97e9-ee3861957f49)\settings\lib\rpyc\utils\classic.py"
  line 36, in __init__, "C:\Users\john\AppData\Roaming\McNeel\Rhinoceros\6.0\Plug-ins\IronPython (814d908a-e25c-493d-97e9-ee3861957f49)\settings\lib\ghpythonremote\connectors.py"
  line 256, in read, "C:\Users\john\AppData\Roaming\McNeel\Rhinoceros\6.0\Plug-ins\IronPython (814d908a-e25c-493d-97e9-ee3861957f49)\settings\lib\rpyc\core\stream.py"
  line 374, in serve, "C:\Users\john\AppData\Roaming\McNeel\Rhinoceros\6.0\Plug-ins\IronPython (814d908a-e25c-493d-97e9-ee3861957f49)\settings\lib\rpyc\core\protocol.py"
  line 47, in wait, "C:\Users\john\AppData\Roaming\McNeel\Rhinoceros\6.0\Plug-ins\IronPython (814d908a-e25c-493d-97e9-ee3861957f49)\settings\lib\rpyc\core\async_.py"
  line 455, in sync_request, "C:\Users\john\AppData\Roaming\McNeel\Rhinoceros\6.0\Plug-ins\IronPython (814d908a-e25c-493d-97e9-ee3861957f49)\settings\lib\rpyc\core\protocol.py"
  line 117, in _get_connection, "C:\Users\john\AppData\Roaming\McNeel\Rhinoceros\6.0\Plug-ins\IronPython (814d908a-e25c-493d-97e9-ee3861957f49)\settings\lib\ghpythonremote\connectors.py"
  line 49, in script

Hi, I get the exact same error message as @markhorgan.
Running windows 10 on a 64 bits machine with Rhino 6.

Following my previous comment I tried with a conda environement and ended-up with the same issue.
DEBUG: ghpythonremote.helpers:
Directly trying python executable at C:\Users\solub\Anaconda2\envs\rhinoremote\python.exe

DEBUG: ghpythonremote.connectors:
Using python executable: C:\Users\solub\Anaconda2\envs\rhinoremote\python.exe

DEBUG: ghpythonremote.connectors:
Using rpyc_server module: C:\Users\solub\AppData\Roaming\McNeel\Rhinoceros\6.0\Plug-ins\IronPython (814d908a-e25c-493d-97e9-ee3861957f49)\settings\lib\ghpythonremote\pythonservice.py

DEBUG: ghpythonremote.connectors:
Using port: 62462

DEBUG: ghpythonremote.connectors:
Using log_level: DEBUG

DEBUG: ghpythonremote.connectors:
Using working_dir: C:\Users\solub\Anaconda2\envs\rhinoremote\Lib\site-packages\ghpythonremote\examples

INFO: ghpythonremote.connectors:
Connecting...

DEBUG: ghpythonremote.connectors:
Connecting. Timeout in 10 seconds.

Runtime error (EndOfStreamException): EOFError

Traceback:
  line 76, in syncreq, "C:\Users\solub\AppData\Roaming\McNeel\Rhinoceros\6.0\Plug-ins\IronPython (814d908a-e25c-493d-97e9-ee3861957f49)\settings\lib\rpyc\core\netref.py"
  line 161, in __getattribute__, "C:\Users\solub\AppData\Roaming\McNeel\Rhinoceros\6.0\Plug-ins\IronPython (814d908a-e25c-493d-97e9-ee3861957f49)\settings\lib\rpyc\core\netref.py"
  line 217, in _install, "C:\Users\solub\AppData\Roaming\McNeel\Rhinoceros\6.0\Plug-ins\IronPython (814d908a-e25c-493d-97e9-ee3861957f49)\settings\lib\rpyc\core\service.py"
  line 213, in on_connect, "C:\Users\solub\AppData\Roaming\McNeel\Rhinoceros\6.0\Plug-ins\IronPython (814d908a-e25c-493d-97e9-ee3861957f49)\settings\lib\rpyc\core\service.py"
  line 105, in _connect, "C:\Users\solub\AppData\Roaming\McNeel\Rhinoceros\6.0\Plug-ins\IronPython (814d908a-e25c-493d-97e9-ee3861957f49)\settings\lib\rpyc\core\service.py"
  line 44, in connect_channel, "C:\Users\solub\AppData\Roaming\McNeel\Rhinoceros\6.0\Plug-ins\IronPython (814d908a-e25c-493d-97e9-ee3861957f49)\settings\lib\rpyc\utils\factory.py"
  line 56, in connect_stream, "C:\Users\solub\AppData\Roaming\McNeel\Rhinoceros\6.0\Plug-ins\IronPython (814d908a-e25c-493d-97e9-ee3861957f49)\settings\lib\rpyc\utils\factory.py"
  line 256, in read, "C:\Users\solub\AppData\Roaming\McNeel\Rhinoceros\6.0\Plug-ins\IronPython (814d908a-e25c-493d-97e9-ee3861957f49)\settings\lib\rpyc\core\stream.py"
  line 55, in recv, "C:\Users\solub\AppData\Roaming\McNeel\Rhinoceros\6.0\Plug-ins\IronPython (814d908a-e25c-493d-97e9-ee3861957f49)\settings\lib\rpyc\core\channel.py"
  line 374, in serve, "C:\Users\solub\AppData\Roaming\McNeel\Rhinoceros\6.0\Plug-ins\IronPython (814d908a-e25c-493d-97e9-ee3861957f49)\settings\lib\rpyc\core\protocol.py"
  line 47, in wait, "C:\Users\solub\AppData\Roaming\McNeel\Rhinoceros\6.0\Plug-ins\IronPython (814d908a-e25c-493d-97e9-ee3861957f49)\settings\lib\rpyc\core\async_.py"
  line 100, in value, "C:\Users\solub\AppData\Roaming\McNeel\Rhinoceros\6.0\Plug-ins\IronPython (814d908a-e25c-493d-97e9-ee3861957f49)\settings\lib\rpyc\core\async_.py"
  line 455, in sync_request, "C:\Users\solub\AppData\Roaming\McNeel\Rhinoceros\6.0\Plug-ins\IronPython (814d908a-e25c-493d-97e9-ee3861957f49)\settings\lib\rpyc\core\protocol.py"
  line 99, in connect, "C:\Users\solub\AppData\Roaming\McNeel\Rhinoceros\6.0\Plug-ins\IronPython (814d908a-e25c-493d-97e9-ee3861957f49)\settings\lib\rpyc\utils\factory.py"
  line 75, in connect, "C:\Users\solub\AppData\Roaming\McNeel\Rhinoceros\6.0\Plug-ins\IronPython (814d908a-e25c-493d-97e9-ee3861957f49)\settings\lib\rpyc\utils\classic.py"
  line 117, in _get_connection, "C:\Users\solub\AppData\Roaming\McNeel\Rhinoceros\6.0\Plug-ins\IronPython (814d908a-e25c-493d-97e9-ee3861957f49)\settings\lib\ghpythonremote\connectors.py"
  line 36, in __init__, "C:\Users\solub\AppData\Roaming\McNeel\Rhinoceros\6.0\Plug-ins\IronPython (814d908a-e25c-493d-97e9-ee3861957f49)\settings\lib\ghpythonremote\connectors.py"
  line 49, in script

I have to say though that I encountered an error during installation when pasting the following line in the Anaconda prompt:
 C:\Users\solub>python -m ghpythonremote._configure_ironpython_installation
WARNING:No ghpy_version.txt file installation found in C:\Users\solub\AppData\Roaming\McNeel\Rhinoceros\5.0\Plug-ins\IronPython (814d908a-e25c-493d-97e9-ee3861957f49)\settings.
Was ghpython installed and opened in Grasshopper at least once on this machine?
ERROR:IronPython lib directory for Rhinoceros not found in C:\Users\solub\AppData\Roaming\McNeel\Rhinoceros\5.0\Plug-ins\IronPython (814d908a-e25c-493d-97e9-ee3861957f49)\settings.
Please provide a full path to one of the folders in your IronPython for Rhinoceros path.
These folders are listed in the settings of the window opened with the command `_EditPythonScript` in Rhinoceros
Traceback (most recent call last):
  File "C:\Users\solub\Anaconda2\envs\rhinoremote\lib\runpy.py", line 174, in _run_module_as_main
    "__main__", fname, loader, pkg_name)
  File "C:\Users\solub\Anaconda2\envs\rhinoremote\lib\runpy.py", line 72, in _run_code
    exec code in run_globals
  File "C:\Users\solub\Anaconda2\envs\rhinoremote\lib\site-packages\ghpythonremote\_configure_ironpython_installation.py", line 15, in <module>
    rhino_ironpython_path = get_rhino_ironpython_path(location=location)
  File "C:\Users\solub\Anaconda2\envs\rhinoremote\lib\site-packages\ghpythonremote\helpers.py", line 78, in get_rhino_ironpython_path
    return get_ironpython_from_appdata()
  File "C:\Users\solub\Anaconda2\envs\rhinoremote\lib\site-packages\ghpythonremote\helpers.py", line 121, in get_ironpython_from_appdata
    raise RuntimeError('No IronPython lib folder found in %APPDATA%')
RuntimeError: No IronPython lib folder found in %APPDATA%

So my reaction to try again and specifying a correct location:
C:\Users\solub>python -m ghpythonremote._configure_ironpython_installation "C:\Users\solub\AppData\Roaming\McNeel\Rhinoceros\6.0\Plug-ins\IronPython (814d908a-e25c-493d-97e9-ee3861957f49)\settings"
The installation was then successful but I'm still facing the errors mentionned above.
Really hope someone can help.

Just to be clear, what Rhinoceros' IronPython's folder are we supposed to install ghPythonRemote in ?
This one:
 C:\Users\solub\AppData\Roaming\McNeel\Rhinoceros\6.0\Plug-ins\IronPython (814d908a-e25c-493d-97e9-ee3861957f49)\settings\lib
or this one:
C:\Program Files\Rhino 6\Plug-ins\IronPython\Lib\site-packages
Tried both and still getting the rpyc related errors.

Hi all, I'm having the same problem. It is odd as I was sure I had ghpython remote working on this laptop previously. I have it running on my desktop PC fine. Both Rhino6 . I can't think what I have done that is different between these two installs.

Let's hope @pilcru will find some time to investigate the issue. Have spent a whole week on this, to no avail.

Sorry for the delayed response, I've got very little time to work on the plugin these days. I haven't been able to reproduce that issue on my end, and I don't really know what could be causing it. So I'm gonna have to have you do some of the debugging, if that's okay.
Do you see any sign of the CPython side running? On most setups, a terminal will open, running the Python process and with this output (don't confuse it with the one that opens up to run conda to find the path to the python executable):

On some machines, this does not open. If you don't see it, is there a new Python process that shows up in the task manager? Considering the connection gets dropped almost immediately, any of these might be difficult to spot, so not a definite way to check if it's working.
Another way to test the CPython end of this would be to try running it independently. Open a cmd.exe and run:
cd "C:\Users\solub\Anaconda2\envs\rhinoremote\Lib\site-packages\ghpythonremote\examples"
"C:\Users\solub\Anaconda2\envs\rhinoremote\python.exe" "C:\Users\solub\AppData\Roaming\McNeel\Rhinoceros\6.0\Plug-ins\IronPython (814d908a-e25c-493d-97e9-ee3861957f49)\settings\lib\ghpythonremote\pythonservice.py" 62462 DEBUG

(using @solub's log file here, adapt to your own username and settings)
Another thing that could be an issue are firewalls and execute permissions in general. In a stock Windows install, the port that's opened is not blocked by the windows firewall, and normal user permissions are enough to launch a python process.
Are you running corporate machines, with especially restrictive firewalls and antivirus? If you can disable these, and/or run Rhino as an admin, and try again, that might provide additional info.

Just to be clear, what Rhinoceros' IronPython's folder are we supposed to install ghPythonRemote in ?
This one:
 C:\Users\solub\AppData\Roaming\McNeel\Rhinoceros\6.0\Plug-ins\IronPython (814d908a-e25c-493d-97e9-ee3861957f49)\settings\lib
or this one:
C:\Program Files\Rhino 6\Plug-ins\IronPython\Lib\site-packages
Tried both but still getting the rpyc related errors.

I don't think that would make a difference, since they are both in Rhino's IronPython path. I normally recommend the first one because it's in the user files and so has fewer permission issues.
That's the command I use to install on Rhino 6:
python -m ghpythonremote._configure_ironpython_installation "%APPDATA%\McNeel\Rhinoceros\6.0\Plug-ins\IronPython (814d908a-e25c-493d-97e9-ee3861957f49)\settings\lib"

Hi there,

Do you see any sign of the CPython side running? On most setups, a terminal will open, running the Python process and with this output (don't confuse it with the one that opens up to run conda to find the path to the python executable):

@pilcru, Thank you for your help, I have the same problem and tried all of the solutions you suggested, but I can't fix it. When I try to run the component, I see the terminal you mentioned in this way:

That's interesting, I thought I had fixed those string vs unicode type errors before... Can you tell me what versions you have installed, by running the following commands?
In the Windows cmd:
conda activate rhinoremote
conda -V
python -V
pip show rpyc
pip show gh-python-remote

In a Rhino Python script:
import rpyc, ghpythonremote, sys, os
from ghpythonremote import version as ghpyrv

print(sys.version)
print(sys.path)
print(rpyc.__version__)
print(rpyc.__path__)
print(ghpyrv.__version__)
print(ghpythonremote.__path__)

For reference, this is what I get:
conda 4.6.14

Python 2.7.16 :: Anaconda, Inc.

Name: rpyc
Version: 4.0.2
Summary: Remote Python Call (RPyC), a transparent and symmetric RPC library
Home-page: http://rpyc.readthedocs.org
Author: Tomer Filiba
Author-email<EMAIL_ADDRESS>License: MIT
Location: c:\users\pierre\appdata\local\continuum\anaconda3\envs\rhinoremote\lib\site-packages
Requires: plumbum
You are using pip version 9.0.3, however version 19.1.1 is available.
You should consider upgrading via the 'python -m pip install --upgrade pip' command.

Name: gh-python-remote
Version: 1.1.4
Summary: GH Python Remote is a package to get Rhinoceros3D/Grasshopper and Python to collaborate better: connect an external python instance to Grasshopper, and vice-versa.
Home-page: https://github.com/Digital-Structures/ghpythonremote
Author: Pierre Cuvilliers
Author-email<EMAIL_ADDRESS>License: MIT
Location: c:\users\pierre\appdata\local\continuum\anaconda3\envs\rhinoremote\lib\site-packages
Requires: rpyc
You are using pip version 9.0.3, however version 19.1.1 is available.
You should consider upgrading via the 'python -m pip install --upgrade pip' command.

2.7.8 (IronPython 2.7.8 (<IP_ADDRESS>) on .NET 4.0.30319.42000 (64-bit))
['C:\\Users\\pierre\\AppData\\Local\\Temp', 'C:\\Program Files\\Rhino 6\\Plug-ins\\IronPython\\Lib', 'C:\\Users\\pierre\\AppData\\Roaming\\McNeel\\Rhinoceros\\6.0\\Plug-ins\\IronPython (814d908a-e25c-493d-97e9-ee3861957f49)\\settings\\lib', 'C:\\Users\\pierre\\AppData\\Roaming\\McNeel\\Rhinoceros\\6.0\\scripts', 'C:\\Program Files\\IronPython 2.7', 'C:\\Program Files\\IronPython 2.7\\DLLs', 'C:\\Program Files\\IronPython 2.7\\Lib']
(4, 0, 2)
['C:\\Users\\pierre\\AppData\\Roaming\\McNeel\\Rhinoceros\\6.0\\Plug-ins\\IronPython (814d908a-e25c-493d-97e9-ee3861957f49)\\settings\\lib\\rpyc']
1.1.4
['C:\\Users\\pierre\\AppData\\Roaming\\McNeel\\Rhinoceros\\6.0\\Plug-ins\\IronPython (814d908a-e25c-493d-97e9-ee3861957f49)\\settings\\lib\\ghpythonremote']

Thank you @pilcru, I tried the commands in windows cmd and I got this error:

I retried using activate <\env> command without conda prefex:

Rhino Python script Results:
2.7.8 (IronPython 2.7.8 (<IP_ADDRESS>) on .NET 4.0.30319.42000 (64-bit))
['C:\Users\farzanehhh\AppData\Local\Temp', 'C:\Program Files\Rhino 6\Plug-ins\IronPython\Lib', 'C:\Users\farzanehhh\AppData\Roaming\McNeel\Rhinoceros\6.0\Plug-ins\IronPython (814d908a-e25c-493d-97e9-ee3861957f49)\settings\lib', 'C:\Users\farzanehhh\AppData\Roaming\McNeel\Rhinoceros\6.0\scripts']
(4, 1, 0)
['C:\Users\farzanehhh\AppData\Roaming\McNeel\Rhinoceros\6.0\Plug-ins\IronPython (814d908a-e25c-493d-97e9-ee3861957f49)\settings\lib\rpyc']
1.1.4
['C:\Users\farzanehhh\AppData\Roaming\McNeel\Rhinoceros\6.0\Plug-ins\IronPython (814d908a-e25c-493d-97e9-ee3861957f49)\settings\lib\ghpythonremote']

So the rpyc version that is installed is newer than the one I have, and I also run into issues when upgrading to 4.1.0. Can you try this, in the windows cmd:
activate rhinoremote
pip uninstall -y rpyc
pip install rpyc==4.0.2
pip install --upgrade --target="C:\Users\farzanehhh\AppData\Roaming\McNeel\Rhinoceros\6.0\Plug-ins\IronPython (814d908a-e25c-493d-97e9-ee3861957f49)\settings\lib" --no-binary=:all: --no-compile --ignore-requires-python rpyc==4.0.2

and try again? It gets me back to a working installation here, but if I missed something and it's not working for you, please also report the result of runming the commands from my previous comment again.
Apparently the "fresh" install I was using when investigating was just a few hours older than the RPyC update from May 25th, so that's why I did not see the issue at first. Sorry to those whom I didn't know how to help.

So the rpyc version that is installed is newer than the one I have, and I also run into issues when upgrading to 4.1.0. Can you try this, in the windows cmd:

It worked fine.
Thank you for your great efforts in developing and supporting this great component.

Closed wrong issue.

Hi,
I am trying to get GH python remote work with rhino 5, and it seems i get the same kind of error message.
Versions installed:

rhino: 5.0
conda : 4.7.5
pyhton: 2.7.16
rpyc: 4.1.0
gh-pyhton-remote: 1.1.4

This is the error message I get when I try to run the example file:
   DEBUG: ghpythonremote.helpers:
   Directly trying python executable at D:\DATA\k.mam\AppData\Local\Continuum\anaconda3\envs\rhinoremote
   DEBUG: ghpythonremote.connectors:
   Using python executable: D:\DATA\k.mam\AppData\Local\Continuum\anaconda3\envs\rhinoremote\python.exe
   DEBUG: ghpythonremote.connectors:
   Using rpyc_server module: D:\DATA\k.mam\AppData\Roaming\McNeel\Rhinoceros\5.0\Plug-ins\IronPython (814d908a-e25c-493d-97e9-ee3861957f49)\settings\lib\ghpythonremote\pythonservice.py
   DEBUG: ghpythonremote.connectors:
   Using port: 65493
   DEBUG: ghpythonremote.connectors:
   Using log_level: DEBUG
   DEBUG: ghpythonremote.connectors:
   Using working_dir: D:\DATA\k.mam\AppData\Roaming\Grasshopper\UserObjects\gh-python-remote\examples
   INFO: ghpythonremote.connectors:
   Connecting...
   DEBUG: ghpythonremote.connectors:
   Connecting. Timeout in 10 seconds.
   Runtime error (EndOfStreamException): EOFError

   Traceback:
   line 55, in recv, "D:\DATA\k.mam\AppData\Roaming\McNeel\Rhinoceros\5.0\Plug-ins\IronPython (814d908a-e25c-493d-97e9-ee3861957f49)\settings\lib\rpyc\core\channel.py"
   line 100, in value, "D:\DATA\k.mam\AppData\Roaming\McNeel\Rhinoceros\5.0\Plug-ins\IronPython (814d908a-e25c-493d-97e9-ee3861957f49)\settings\lib\rpyc\core\async_.py"
   line 161, in __getattribute__, "D:\DATA\k.mam\AppData\Roaming\McNeel\Rhinoceros\5.0\Plug-ins\IronPython (814d908a-e25c-493d-97e9-ee3861957f49)\settings\lib\rpyc\core\netref.py"
   line 217, in _install, "D:\DATA\k.mam\AppData\Roaming\McNeel\Rhinoceros\5.0\Plug-ins\IronPython (814d908a-e25c-493d-97e9-ee3861957f49)\settings\lib\rpyc\core\service.py"
   line 213, in on_connect, "D:\DATA\k.mam\AppData\Roaming\McNeel\Rhinoceros\5.0\Plug-ins\IronPython (814d908a-e25c-493d-97e9-ee3861957f49)\settings\lib\rpyc\core\service.py"
   line 105, in _connect, "D:\DATA\k.mam\AppData\Roaming\McNeel\Rhinoceros\5.0\Plug-ins\IronPython (814d908a-e25c-493d-97e9-ee3861957f49)\settings\lib\rpyc\core\service.py"
   line 44, in connect_channel, "D:\DATA\k.mam\AppData\Roaming\McNeel\Rhinoceros\5.0\Plug-ins\IronPython (814d908a-e25c-493d-97e9-ee3861957f49)\settings\lib\rpyc\utils\factory.py"
   line 56, in connect_stream, "D:\DATA\k.mam\AppData\Roaming\McNeel\Rhinoceros\5.0\Plug-ins\IronPython (814d908a-e25c-493d-97e9-ee3861957f49)\settings\lib\rpyc\utils\factory.py"
   line 99, in connect, "D:\DATA\k.mam\AppData\Roaming\McNeel\Rhinoceros\5.0\Plug-ins\IronPython (814d908a-e25c-493d-97e9-ee3861957f49)\settings\lib\rpyc\utils\factory.py"
   line 75, in connect, "D:\DATA\k.mam\AppData\Roaming\McNeel\Rhinoceros\5.0\Plug-ins\IronPython (814d908a-e25c-493d-97e9-ee3861957f49)\settings\lib\rpyc\utils\classic.py"
   line 36, in __init__, "D:\DATA\k.mam\AppData\Roaming\McNeel\Rhinoceros\5.0\Plug-ins\IronPython (814d908a-e25c-493d-97e9-ee3861957f49)\settings\lib\ghpythonremote\connectors.py"
   line 256, in read, "D:\DATA\k.mam\AppData\Roaming\McNeel\Rhinoceros\5.0\Plug-ins\IronPython (814d908a-e25c-493d-97e9-ee3861957f49)\settings\lib\rpyc\core\stream.py"
   line 374, in serve, "D:\DATA\k.mam\AppData\Roaming\McNeel\Rhinoceros\5.0\Plug-ins\IronPython (814d908a-e25c-493d-97e9-ee3861957f49)\settings\lib\rpyc\core\protocol.py"
   line 47, in wait, "D:\DATA\k.mam\AppData\Roaming\McNeel\Rhinoceros\5.0\Plug-ins\IronPython (814d908a-e25c-493d-97e9-ee3861957f49)\settings\lib\rpyc\core\async_.py"
   line 455, in sync_request, "D:\DATA\k.mam\AppData\Roaming\McNeel\Rhinoceros\5.0\Plug-ins\IronPython (814d908a-e25c-493d-97e9-ee3861957f49)\settings\lib\rpyc\core\protocol.py"
   line 76, in syncreq, "D:\DATA\k.mam\AppData\Roaming\McNeel\Rhinoceros\5.0\Plug-ins\IronPython (814d908a-e25c-493d-97e9-ee3861957f49)\settings\lib\rpyc\core\netref.py"
   line 117, in _get_connection, "D:\DATA\k.mam\AppData\Roaming\McNeel\Rhinoceros\5.0\Plug-ins\IronPython (814d908a-e25c-493d-97e9-ee3861957f49)\settings\lib\ghpythonremote\connectors.py"
   line 49, in script

Can you try installing rpyc v4.0.2 while I fix this?
conda activate rhinoremote
pip install --force-reinstall rpyc==4.0.2
pip install --force-reinstall --target="D:\DATA\k.mam\AppData\Roaming\McNeel\Rhinoceros\6.0\Plug-ins\IronPython (814d908a-e25c-493d-97e9-ee3861957f49)\settings\lib" --no-binary=:all: --no-compile --ignore-requires-python rpyc==4.0.2

Can you try installing rpyc v4.0.2 while I fix this?
conda activate rhinoremote
pip install --force-reinstall rpyc==4.0.2
pip install --force-reinstall --target="D:\DATA\k.mam\AppData\Roaming\McNeel\Rhinoceros\6.0\Plug-ins\IronPython (814d908a-e25c-493d-97e9-ee3861957f49)\settings\lib" --no-binary=:all: --no-compile --ignore-requires-python rpyc==4.0.2

Just tried this. But it doesn't seem to work either (see below). Please note that I am using a corporate machine (maybe my problem comes from network security restrictions).
  DEBUG: ghpythonremote.helpers:
  Directly trying python executable at D:\DATA\k.mam\AppData\Local\Continuum\anaconda3\envs\rhinoremote
  DEBUG: ghpythonremote.connectors:
  Using python executable: D:\DATA\k.mam\AppData\Local\Continuum\anaconda3\envs\rhinoremote\python.exe
  DEBUG: ghpythonremote.connectors:
  Using rpyc_server module: D:\DATA\k.mam\AppData\Roaming\McNeel\Rhinoceros\5.0\Plug-ins\IronPython (814d908a-e25c-493d-97e9-ee3861957f49)\settings\lib\ghpythonremote\pythonservice.py
  DEBUG: ghpythonremote.connectors:
  Using port: 56151
  DEBUG: ghpythonremote.connectors:
  Using log_level: DEBUG
  DEBUG: ghpythonremote.connectors:
  Using working_dir: D:\DATA\k.mam\AppData\Roaming\Grasshopper\UserObjects\gh-python-remote\examples
  INFO: ghpythonremote.connectors:
  Connecting...
  DEBUG: ghpythonremote.connectors:
  Connecting. Timeout in 10 seconds.
  Runtime error (Exception): KeyError

  Traceback:
  line 352, in _dispatch, "D:\DATA\k.mam\AppData\Roaming\McNeel\Rhinoceros\5.0\Plug-ins\IronPython (814d908a-e25c-493d-97e9-ee3861957f49)\settings\lib\rpyc\core\protocol.py"
  line 47, in wait, "D:\DATA\k.mam\AppData\Roaming\McNeel\Rhinoceros\5.0\Plug-ins\IronPython (814d908a-e25c-493d-97e9-ee3861957f49)\settings\lib\rpyc\core\async_.py"
  line 100, in value, "D:\DATA\k.mam\AppData\Roaming\McNeel\Rhinoceros\5.0\Plug-ins\IronPython (814d908a-e25c-493d-97e9-ee3861957f49)\settings\lib\rpyc\core\async_.py"
  line 455, in sync_request, "D:\DATA\k.mam\AppData\Roaming\McNeel\Rhinoceros\5.0\Plug-ins\IronPython (814d908a-e25c-493d-97e9-ee3861957f49)\settings\lib\rpyc\core\protocol.py"
  line 485, in root, "D:\DATA\k.mam\AppData\Roaming\McNeel\Rhinoceros\5.0\Plug-ins\IronPython (814d908a-e25c-493d-97e9-ee3861957f49)\settings\lib\rpyc\core\protocol.py"
  line 44, in connect_channel, "D:\DATA\k.mam\AppData\Roaming\McNeel\Rhinoceros\5.0\Plug-ins\IronPython (814d908a-e25c-493d-97e9-ee3861957f49)\settings\lib\rpyc\utils\factory.py"
  line 56, in connect_stream, "D:\DATA\k.mam\AppData\Roaming\McNeel\Rhinoceros\5.0\Plug-ins\IronPython (814d908a-e25c-493d-97e9-ee3861957f49)\settings\lib\rpyc\utils\factory.py"
  line 99, in connect, "D:\DATA\k.mam\AppData\Roaming\McNeel\Rhinoceros\5.0\Plug-ins\IronPython (814d908a-e25c-493d-97e9-ee3861957f49)\settings\lib\rpyc\utils\factory.py"
  line 75, in connect, "D:\DATA\k.mam\AppData\Roaming\McNeel\Rhinoceros\5.0\Plug-ins\IronPython (814d908a-e25c-493d-97e9-ee3861957f49)\settings\lib\rpyc\utils\classic.py"
  line 36, in __init__, "D:\DATA\k.mam\AppData\Roaming\McNeel\Rhinoceros\5.0\Plug-ins\IronPython (814d908a-e25c-493d-97e9-ee3861957f49)\settings\lib\ghpythonremote\connectors.py"
  line 102, in value, "D:\DATA\k.mam\AppData\Roaming\McNeel\Rhinoceros\5.0\Plug-ins\IronPython (814d908a-e25c-493d-97e9-ee3861957f49)\settings\lib\rpyc\core\async_.py"
  line 455, in sync_request, "D:\DATA\k.mam\AppData\Roaming\McNeel\Rhinoceros\5.0\Plug-ins\IronPython (814d908a-e25c-493d-97e9-ee3861957f49)\settings\lib\rpyc\core\protocol.py"
  line 313, in _netref_factory, "D:\DATA\k.mam\AppData\Roaming\McNeel\Rhinoceros\5.0\Plug-ins\IronPython (814d908a-e25c-493d-97e9-ee3861957f49)\settings\lib\rpyc\core\protocol.py"
  line 300, in _unbox, "D:\DATA\k.mam\AppData\Roaming\McNeel\Rhinoceros\5.0\Plug-ins\IronPython (814d908a-e25c-493d-97e9-ee3861957f49)\settings\lib\rpyc\core\protocol.py"
  line 384, in serve, "D:\DATA\k.mam\AppData\Roaming\McNeel\Rhinoceros\5.0\Plug-ins\IronPython (814d908a-e25c-493d-97e9-ee3861957f49)\settings\lib\rpyc\core\protocol.py"
  line 213, in on_connect, "D:\DATA\k.mam\AppData\Roaming\McNeel\Rhinoceros\5.0\Plug-ins\IronPython (814d908a-e25c-493d-97e9-ee3861957f49)\settings\lib\rpyc\core\service.py"
  line 105, in _connect, "D:\DATA\k.mam\AppData\Roaming\McNeel\Rhinoceros\5.0\Plug-ins\IronPython (814d908a-e25c-493d-97e9-ee3861957f49)\settings\lib\rpyc\core\service.py"
  line 117, in _get_connection, "D:\DATA\k.mam\AppData\Roaming\McNeel\Rhinoceros\5.0\Plug-ins\IronPython (814d908a-e25c-493d-97e9-ee3861957f49)\settings\lib\ghpythonremote\connectors.py"
  line 49, in script

I think one of the two downgrades did not work as planned. Did you see any errors? Can you run the same commands as in this message above and report what you get?

I think one of the two downgrades did not work as planned. Did you see any errors? Can you run the same commands as in this message above and report what you get?

 (rhinoremote) D:\DATA\k.mam\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Anaconda3 (64-bit)>pip install --force-reinstall rpyc==4.0.2
 Requirement already satisfied: rpyc==4.0.2 in d:\data\k.mam\appdata\local\continuum\anaconda3\envs\rhinoremote\lib\site-packages
 Requirement already satisfied: plumbum in d:\data\k.mam\appdata\local\continuum\anaconda3\envs\rhinoremote\lib\site-packages\plumbum-1.6.7-py2.7.egg (from rpyc==4.0.2)
 You are using pip version 9.0.3, however version 19.1.1 is available.
 You should consider upgrading via the 'python -m pip install --upgrade pip' command.

 (rhinoremote) D:\DATA\k.mam\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Anaconda3 (64-bit)>pip install --force-reinstall --target="D:\DATA\k.mam\AppData\Roaming\McNeel\Rhinoceros\6.0\Plug-ins\IronPython (814d908a-e25c-493d-97e9-ee3861957f49)\settings\lib" --no-binary=:all: --no-compile --ignore-requires-python rpyc==4.0.2
 Collecting rpyc==4.0.2
 Using cached https://files.pythonhosted.org/packages/ba/88/1cea477a4ad7c0f546a4c82aa367185be7b8fce512db8283e82de8454772/rpyc-4.0.2.tar.gz
 Collecting plumbum (from rpyc==4.0.2)
 Using cached https://files.pythonhosted.org/packages/78/4c/1fb849111fda37d65358be1859e062278b2f94b5269f19838115966e4493/plumbum-1.6.7.tar.gz
 Skipping bdist_wheel for rpyc, due to binaries being disabled for it.
 Skipping bdist_wheel for plumbum, due to binaries being disabled for it.
 Installing collected packages: plumbum, rpyc
 Running setup.py install for plumbum ... done
 Running setup.py install for rpyc ... done
 Successfully installed plumbum-1.6.7 rpyc-4.0.2
 Target directory D:\DATA\k.mam\AppData\Roaming\McNeel\Rhinoceros\6.0\Plug-ins\IronPython (814d908a-e25c-493d-97e9-ee3861957f49)\settings\lib\plumbum already exists. Specify --upgrade to force replacement.
 Target directory D:\DATA\k.mam\AppData\Roaming\McNeel\Rhinoceros\6.0\Plug-ins\IronPython (814d908a-e25c-493d-97e9-ee3861957f49)\settings\lib\plumbum-1.6.7-py2.7.egg-info already exists. Specify --upgrade to force replacement.
 Target directory D:\DATA\k.mam\AppData\Roaming\McNeel\Rhinoceros\6.0\Plug-ins\IronPython (814d908a-e25c-493d-97e9-ee3861957f49)\settings\lib\rpyc already exists. Specify --upgrade to force replacement.
 Target directory D:\DATA\k.mam\AppData\Roaming\McNeel\Rhinoceros\6.0\Plug-ins\IronPython (814d908a-e25c-493d-97e9-ee3861957f49)\settings\lib\rpyc-4.0.2-py2.7.egg-info already exists. Specify --upgrade to force replacement.
 You are using pip version 9.0.3, however version 19.1.1 is available.
 You should consider upgrading via the 'python -m pip install --upgrade pip' command.

Can you run the same commands as in this message above and report what you get? So that we know what versions we are really working with.
You can also throw in an --upgrade argument to the second pip command to see if it complains a bit less, but really, the interesting thing here is going to be the versions of everything you are using.

Can you run the same commands as in this message above and report what you get? So that we know what versions we are really working with.
You can also throw in an --upgrade argument to the second pip command to see if it complains a bit less, but really, the interesting thing here is going to be the versions of everything you are using.

My bad, I reinstalled rpyc v4.0.2 and It works fine now. Thanks for your help !!

All these issues should be fixed in the new version 1.2.0. If you run into similar issues (same error messages), under v1.2.0, and you find that downgrading RPyC to v4.0.2 solves your issues, feel free to reopen. Instructions to downgrade RPyC.
Otherwise, please open a new issue.


analyzer should run with -A for bug-report based on issue#31918

This PR was submitted for issue: issue#31918
[ ] Configuration Infrastructure
[ ] Docs
[ ] Installation
[ ] Networking
[ ] Performance and Scalability
[ ] Policies and Telemetry
[ ] Securitygit commit -m "this submit is for issue#31918"
[x] Test and Release
[x] User Experience
[ ] Developer Infrastructure
Pull Request Attributes
Please check any characteristics that apply to this pull request.
[ ] Does not have any changes that may affect Istio users.

@zhlsunshine: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

release-notes_istio
e5f6e1c5e4500a01b01b2d49dcaa945b4d30bca4
link
/test release-notes_istio

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

Here is the test result:
$ istioctl bug-report
`......
Fetching Istio control plane information from cluster.
Running istio analyze on all namespaces and report as below:
################################################################
################################################################
Info [IST0102] (Namespace calico-system) The namespace is not enabled for Istio injection. Run 'kubectl label namespace calico-system istio-injection=enabled' to enable it, or 'kubectl label namespace calico-system istio-injection=disabled' to explicitly mark it as not needing injection.
Info [IST0102] (Namespace istio-system) The namespace is not enabled for Istio injection. Run 'kubectl label namespace istio-system istio-injection=enabled' to enable it, or 'kubectl label namespace istio-system istio-injection=disabled' to explicitly mark it as not needing injection.
Info [IST0102] (Namespace tigera-operator) The namespace is not enabled for Istio injection. Run 'kubectl label namespace tigera-operator istio-injection=enabled' to enable it, or 'kubectl label namespace tigera-operator istio-injection=disabled' to explicitly mark it as not needing injection.
Info [IST0118] (Service calico-typha.calico-system) Port name calico-typha (port: 5473, targetPort: calico-typha) doesn't follow the naming convention of Istio port.
Info [IST0118] (Service productpage.default) Port name httpd (port: 9080, targetPort: 9080) doesn't follow the naming convention of Istio port.
################################################################
################################################################
Creating an archive at /home/zhlsunshine/go/src/istio/bug-report.tar.gz.
Cleaning up temporary files in /tmp/bug-report.
Done.
......`

@zhlsunshine: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

release-notes_istio
e5f6e1c5e4500a01b01b2d49dcaa945b4d30bca4
link
/test release-notes_istio

integ-pilot-multicluster-tests_istio
e5f6e1c5e4500a01b01b2d49dcaa945b4d30bca4
link
/test integ-pilot-multicluster-tests_istio

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

/test release-notes_istio

/test integ-pilot-multicluster-tests_istio

@zhlsunshine: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-pilot-multicluster-tests_istio
e5f6e1c5e4500a01b01b2d49dcaa945b4d30bca4
link
/test integ-pilot-multicluster-tests_istio

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

/test integ-pilot-multicluster-tests_istio

Hi @howardjohn  could you please help to do code review for this PR related to issue#31918, thanks!

@zhlsunshine: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-pilot-multicluster-tests_istio
e37afc447a372add8ba273b47913090f7d180a3f
link
/test integ-pilot-multicluster-tests_istio

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

/test integ-pilot-multicluster-tests_istio

Hi @howardjohn , it's done, please help to check it again, thanks! ^_^

And Here is the newest result:
$ istioctl bug-report
......
Fetching Istio control plane information from cluster.
Running istio analyze on all namespaces and report as below:
Analysis Report:
Info [IST0102] (Namespace calico-system) The namespace is not enabled for Istio injection. Run 'kubectl label namespace calico-system istio-injection=enabled' to enable it, or 'kubectl label namespace calico-system istio-injection=disabled' to explicitly mark it as not needing injection.
Info [IST0102] (Namespace istio-system) The namespace is not enabled for Istio injection. Run 'kubectl label namespace istio-system istio-injection=enabled' to enable it, or 'kubectl label namespace istio-system istio-injection=disabled' to explicitly mark it as not needing injection.
Info [IST0102] (Namespace tigera-operator) The namespace is not enabled for Istio injection. Run 'kubectl label namespace tigera-operator istio-injection=enabled' to enable it, or 'kubectl label namespace tigera-operator istio-injection=disabled' to explicitly mark it as not needing injection.
Info [IST0118] (Service calico-typha.calico-system) Port name calico-typha (port: 5473, targetPort: calico-typha) doesn't follow the naming convention of Istio port.
Info [IST0118] (Service productpage.default) Port name httpd (port: 9080, targetPort: 9080) doesn't follow the naming convention of Istio port.
Creating an archive at /home/zhlsunshine/go/src/istio/bug-report.tar.gz.
Cleaning up temporary files in /tmp/bug-report.
Done.
......


Enable Host Tests to work without Device

@tarafdarTT do we have a dedicated suite of host tests that don't require the device?

Not yet, I can see what I can dig up. I think a subset of tests can be host only and need to be separated. I don't have the bandwidth to work on this full-time and a run-time person might be better tasked at this.


Account - Message 'Account closed successfully" doesn't appear

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Action Performed:

Launch App and login
Navigate to security > Close account
Enter your default contact method
Tap on "Close account" button

Expected Result:
Account should be close and green dot with the message 'Account closed successfully" appeared.
Actual Result:
Account was closed and only green dot without the message 'Account closed successfully" appeared.
Workaround:
unknown
Platform:

Where is this issue occurring?

Web
iOS
Android
Desktop App
Mobile Web

Version Number: 1.2.37-0
Reproducible in staging?: y
Reproducible in production?: n
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos:

https://user-images.githubusercontent.com/43996225/206614984-9932d9cc-04dc-4e87-b04c-73197aedfd71.mp4
Expensify/Expensify Issue URL:
Issue reported by: Applause internal team
Slack conversation:
View all open jobs on GitHub

Grabbing this!

Not seeing this in web:

Could reproduce it in iOS:

Not a deploy blocker since the PR was CP'd to staging. I briefly tested on staging ios and it looks like the issue is resolved for me. removing deploy blocker label.

This was solved internally, so no payments needed


Reduce verbosity of buildDir replacement

Expected Behavior
buildDir has been deprecated https://github.com/gradle/gradle/issues/20210
The replacement, layout.buildDirectory.get().asFile, is verbose and introduces strange concepts like 'layout'.
It leads to difficult to read code compared to the previous version.
Before:
val aggregateTestReports by tasks.registering(TestReport::class) {
  // ...

  testResults.from("$buildDir/test-results/test/binary")
  testResults.from("$buildDir/test-results/testFunctional/binary")
  testResults.from("$buildDir/test-results/testIntegration/binary")
}

After:
val aggregateTestReports by tasks.registering(TestReport::class) {
  // ...

  testResults.from("${layout.buildDirectory.get().asFile}/test-results/test/binary")
  testResults.from("${layout.buildDirectory.get().asFile}/test-results/testFunctional/binary")
  testResults.from("${layout.buildDirectory.get().asFile}/test-results/testIntegration/binary")
}

While buildDir returns a non-lazy property it is still a useful property, as a significant proportion of Gradle properties don't accept Provider API compatible properties.
Current Behavior (optional)
No response
Context
For now I've added a replacement in my buildSrc utils
// buildSrc/src/main/kotlin/utils.kt

// workaround for the overly verbose replacement for the deprecated buildDir property
val Project.buildDir_: File get() = layout.buildDirectory.get().asFile

While I agree that the replacement is more verbose, you are actually using it wrong. The whole point of the layout API is to be lazy. In other words, every time you have to call .get() explicitly, it is likely you are doing something wrong.
In your case, the code should be :
val aggregateTestReports by tasks.registering(TestReport::class) {
  // ...

  testResults.from(layout.buildDirectory.dir("/test-results/test/binary")
  testResults.from(layout.buildDirectory.dir("test-results/testFunctional/binary")
  testResults.from(layout.buildDirectory.dir("test-results/testIntegration/binary")
}

which isn't that bad. Also instead of having a call to layout.buildDirectory, there should probably be a task which provides the output directory you're looking for, in which case you would get rid of the call altogether and have automatic task dependency tracking.

I think there are cases where the replacement is verbose and, as far as I know, isn't being used incorrectly. Configuring the destinationDir of a Sync task was one that I encountered when moving away from buildDir.

Thank you for your interest in Gradle!
This issue will be closed as a duplicate of

#26211

Please add your use case and 👍 to that issue.


Nonexistent property for Service_Generic: vlansEnabled

Environment

Application Services Version: f5devcentral/f5-as3-config-converter:1.11.0
BIG-IP Version: 15.x

Summary
Charon wrongly convers VS property: vlans-enabled to vlansEnabled instead of allowVlans
Steps To Reproduce
Steps to reproduce the behavior:

Convert following config:

ltm virtual /tenant_1/application_1/test_vs {
    description "Created by Web Configuration Utility for PEM Listener test_vs"
    destination /tenant_1/application_1/<IP_ADDRESS>:80
    ip-protocol udp
    mask any
    profiles {
        /Common/classification_pem {
            context clientside
        }
        /tenant_1/application_1/test_profile {
            context clientside
        }
        /Common/udp_decrement_ttl { }
    }
    source <IP_ADDRESS>/32
    source-address-translation {
        pool /Common/cgnat-pool
        type lsn
    }
    translate-address disabled
    translate-port enabled
    vlans-enabled
}

Observe the following error message:

{
    "code": 422,
    "message": "Invalid data property: vlansEnabled"
}

when deploying generated declaration:
 "test_vs": {
                "remark": "Created by Web Configuration Utility for PEM Listener test_vs",
                "layer4": "udp",
                "translateServerAddress": false,
                "translateServerPort": true,
                "vlansEnabled": "",
                "class": "Service_Generic",
                "profileClassification": {
                    "bigip": "/Common/classification_pem"
                },
                "profileEnforcement": {
                    "use": "/tenant_1/application_1/test_profile"
                },
                "virtualAddresses": [
                    [
                        "<IP_ADDRESS>/0",
                        "<IP_ADDRESS>/32"
                    ]
                ],
                "virtualPort": 80,
                "persistenceMethods": []
            },

Expected Behavior
Instead vlansEnabled, charon should use: allowVlans as per documentation for Service_Generic: https://clouddocs.f5.com/products/extensions/f5-appsvcs-extension/latest/refguide/schema-reference.html#service-generic
Actual Behavior
Charon converts vlans-enabled to vlansEnabled instead of allowVlans property.

Please double check scenario when vlans-enabled in bigip.conf is empty - if allowVlans property should be present  / what should be the exact value of allowVlans property .

Filed Jira CHARON-318 for PM tracking

Merge branch 'vlans_enabled' into 'develop. Closing issue as complete


Unable to import node:crypto when using AWS Lambda Powertools logger module

To reproduce
import crypto from "node:crypto";

export const handler = async (event: any) => {
    const randomInt = crypto.randomInt(16);
    expect(typeof randomInt).toEqual("number");

    return "Hello, world!";
};

Fixed by https://github.com/awslabs/llrt/pull/306


[ssr] Can't bundle into SSR app because of side-effects

Description
I understand that this project is inherently incompatible with SSR, but this module can literally not be imported into a NextJS project (for example) because you get the following error:
ReferenceError: window is not defined

This is because of the following lines in shady-render.ts:
if (typeof window.ShadyCSS === 'undefined') {
  compatibleShadyCSSVersion = false;
} else if (typeof window.ShadyCSS.prepareTemplateDom === 'undefined') {
  console.warn(
      `Incompatible ShadyCSS version detected. ` +
      `Please update to at least<EMAIL_ADDRESS>and ` +
      `@webcomponents/shadycss@1.3.1.`);
  compatibleShadyCSSVersion = false;
}

If this could be refactored to be side-effect-free (and not depend on window at import-time) then we could do the following without an error:
import { html, render } from "lit-html";

/* Detect SSR: */
if (typeof window !== "undefined") {
  render(
    html`<h1>Hello World</h1>`,
    document.querySelector("[data-app]"))
  );
}

Expected Results
No error thrown by importing the lit-html library in an SSR context.
Actual Results
An error is thrown by importing the lit-html library in an SSR context.
Browsers Affected
Not applicable.

The problem with fixing the window reference is that you'll then hit other references in lit-element, like HTMLElement.
What we're doing in lit-ssr is creating a minimal DOM shim to define the needed APIs: https://github.com/PolymerLabs/lit-ssr/blob/master/src/lib/dom-shim.ts
If you don't want to actually run the code you can have an even more minimal shim.

I'm not using lit-element :) Is my fix invalid?

Leaving this open to add a Node importability test per this comment: https://app.zenhub.com/workspaces/polymer-project-5ce5a1fc3c14bf6d63636b62/issues/lit/lit/1214#issuecomment-820668662.

I can see that this issue is still present and even importing throws "window is not defined". React component created from createComponent lit-labs/react is not much useless to many outside APIs that wrap around react components

We've just published some pre-releases for Lit which includes https://github.com/lit/lit/pull/3156. This change means that Lit should now be importable directly from Node, without crashing, without the need to first load the global DOM shim.
You should be able to upgrade with:
npm i<EMAIL_ADDRESS>Note this won't automatically enable any kind of actual SSR of Lit components out-of-the-box, since that requires specific integration with the framework/renderer -- but it should allow you to import without crashing Node.
Also note that this does not automatically globally define any DOM APIs like the global DOM shim does, apart from customElements which is shimmed as a no-op. So if you have any calls like window.addEventListener running at module initialization, that will still error.
If you have a chance to check out this pre-release, that would be great, and please comment here to let us know how that works for you!

The PR mentioned above has made its way to a stable release so closing this as fixed!


React / RCTBridge.h not found in my project

I see someone experiencing a similar problem, I tried changing my headpath but did not succeed if I changed

@xuanheScript are you running React Native v0.40+? If not then you need to downgrade version v0.1.5 or lower of this app.

I'm using React native 0.40+, still facing the same error. I've already tried everything possible.

same error RN0.61


Enable app extension API only.

The allows Swish to be used in targets that only support app extension APIs.
Since none of the unavailable APIs are being used, this is a backwards compatible change.
Some more info on this is available here: https://developer.apple.com/library/prerelease/ios/documentation/General/Conceptual/ExtensibilityPG/ExtensionScenarios.html

Merged as 988bebd


Asks password multiple times in succession to upgrade each cask

Yes, I had to input my password 7 times to upgrade one cask 😵
I run brew cu -facy each month. Today for the first time I noticed that brew cu is asking me for the device's password in quick succession. Before it would simply ask me once or twice, for specific casks, usually docker or java. But now it's asks that many times for a single cask. This makes the script unusable.
I'm using the company's laptop, could it that they changed some access policy?

Hey @dialex
Thank you for the question. It's actually quite hard to know what's causing that, I haven't personally experienced that. Could be because of computer policy, could be also related to how the casks are defined.
I'm not sure if there is actually anything we could do about it. We solely rely on brew reinstall --cask XYZ command to do the updates, so we can't really control much.

If there is a way to know ahead whether a cask requires root to reinstall, maybe consider skipping and postponing them, so that the upgrade doesn't get stuck every other cask, because brew doesn't seem to cache sudo access anymore since that turned out to be a security issue.

In fact I would be quite interested in how to configure it to run in full unattended mode, so the "sudo" prompt would not be needed. I am aware that this might be seen as a security issue but some users might be ok with it, so it should be an opt-in workaround.

Alternatively we should have an option to tag the few packages that need sudo and avoid updating them when in unattended/scripted mode. Any suggestions?

You can use the cask pinning feature (brew cu pin <cask>) to avoid updating them. So at least part of it is possible.
For the unattended mode, I'm not sure if that's easily possible unless homebrew itself supports that.


fix: export MapView interface

Description

Make it easy to reuse official types.

import { MapView } from '@rnmapbox/maps';

const MyComponent = ({ projection }: { projection: MapView['props']['projection'] }) => (
  <MapView projection={projection}>
    ...
  </MapView>
)

Checklist

[x] I have tested this on a device/simulator for each compatible OS
[x] I updated the documentation with running yarn generate in the root folder
[x] I added/updated a sample - if a new feature was implemented (/example)

@jeremybarbet thanks much. But isn't your example already working with current version?
What error do you get with this code, on the current version, and with which tool?
It seems to be working just fine for me, both with tsc and vscode
const MyComponent = ({ projection }: { projection: MapView['props']['projection'] }) => (
  <MapView projection={projection}>
    ...
  </MapView>
)

Yep you are correct it works. Probably some Vscode typescript server error for a minute.
I wonder if these types shouldn't be exported in other places then? (example: https://github.com/rnmapbox/maps/blob/main/src/components/LineLayer.tsx#L13)


Fedora 40 with Nvidia - Performance

Describe the bug
If I start zwift on my Fedora Linux machine the GPU is not used.
Maybe a regression bug.
I know that the NVIDIA_DRIVER_CAPABILITIES is set in the Dockerfile.
Expected behavior
I can use my Nvidia GPU
Additional context
If  I add -e NVIDIA_DRIVER_CAPABILITIES=all   the problem is fixed.
  I assume Nvidia?

Proprietary nvidia driver. I am on the 555 which is really fresh.

I'll look into it currently using Nouveau as not got round to setting up the proprietary but have to for another project.

No worry. I am able to fix this issues from my side. I opened this issue for other people with the same problem.
I just had a view to the Dockerfile.
The ENV var was introduced there.
https://github.com/netbrain/zwift/blob/cf43c78c8fb4e154002f9107be6f30705e9d295b/Dockerfile#L29
In the meantime we have multi step build there.
In the last step the ENV var is missing.
If we move the env var after the FROM wine-base it may be fixed.

If you can give that a go :) if not I will try it out once I get my driver switched over.

Hi, I switched to the nvidia drivers, after some issues with resiable bar and the /dev/card changing sorted.  I don't have this issue but I only have an NVIDIA card in mine no other capable device.
Do you have an intel chip with video?
And do you think it might be related to #21

@sHedC I have a AMD based system (AMD Ryzen 9 7950X) with a  NVIDIA 4060 TI.

@cmuench - Can you try with the latest zwift.sh and container, I have moved relevant flags to the correct location so hopfully works.

@sHedC Works on my machine :-)

@sHedC Thank you very much.


AWS install stops with Authentication failed - policy incorrect?

using flynn install for an AWS cluster, have tried 3 sets of credentials on 2 different accounts. Have set up with the managed policies for AmazonEC2FullAccess, AmazonS3FullAccess and a custom policy for Cloudformation (AWS doesn't have one pre-built) that looks like this:
{
    "Version": "2012-10-17",
    "Statement": [
        {
            "Sid": "Stmt1476880971000",
            "Effect": "Allow",
            "Action": [
                "cloudformation:*"
            ],
            "Resource": [
                "arn:aws:cloudformation:*"
            ]
        }
    ]
}

the logs just look like this:
$ flynn install
Open http://localhost:49637 in your browser to continue.
INFO[10-19|09:30:43] Event: new_cluster:
INFO[10-19|09:30:43] Event: log: Using saved key pair (flynn)
INFO[10-19|09:30:43] Event: log: Allocating domain
INFO[10-19|09:30:43] Event: log: Fetching image manifest
INFO[10-19|09:30:44] Event: log: Generating start script
INFO[10-19|09:30:44] Event: log: Creating stack
INFO[10-19|09:30:53] Event: prompt:

The UI shows "Authentication failed, please select a new credential to continue". Not sure what operation is being performed, but I think the credentials are correct, because if I detach the Cloudformation policy, the logs show:
Error: User: arn:aws:iam::588275505772:user/flynn-test is not authorized to perform: cloudformation:CreateStack on resource: arn:aws:cloudformation:us-east-1:588275505772:stack/flynn-1476884287/*
It's only when I actually have the Cloudformation policy attached that I get the "Authentication failed" result.
Not sure what policies people are using to install on AWS, but if it's full admin access, we won't be able to use that. So, just wondering what the setup should be.

update: mostly fixed. I found the logs needed to diagnose in the Cloudformation console, and adding AmazonRoute53FullAccess policy results in a successful install.
However, leaving this open in case anyone can document the minimum policy requirement and ARN patterns to lock down the permissions better.


commentParserToESTree: Working with full comment blocks and removal of new lines / empty description lines.

So,
The last problem I think I will run into re: jsdoccomment and processing full comment blocks is that commentParserToESTree compacts the AST data for description lines. While the parsing in parseComment is setup to preserve through the AST generation from comment-parser there is forced compaction in commentParserToESTree. This occurs on line 366.
Change if (description) { to if (typeof description === 'string' && delimiter !== '/**') { and the compaction doesn't occur. There may be a better test to change this to and of course a reason for the compaction for the type of processing that you are utilizing jsdoccomment for as things go. For my purposes of modifying a complete comment block it is important to preserve the extra new lines / empty description lines particularly around the use of markdown in comment blocks which won't be interpreted correctly by downstream tooling like TypeDoc without them.
My general suggestion is adding an additional option to commentParserToESTree for spacing just like comment-parser and it can default to compact, but if preserve is passed then new lines are kept for description generation. Perhaps you can suggest a better conditional test that you might prefer rather than using delimiter for if (typeof description === 'string' && delimiter !== '/**') { as that is just a quick test I used to determine the source of the issue I'm facing. Maybe: if ((spacing === 'compact' && description) || (spacing === 'preserve' && delimiter !== '/**')).
I'd be glad to work up a PR with the changes after a bit of discussion.

I think you are saying that line 366 triggers compacting, but I don't see where the compacting actually occurs. holder.descriptionLines.push in line 368 is just optional AST to have separate lines, whereas line 395 doesn't seem to be compacting per se. Is the issue in line 395 because we are not always adding a newline there? It would help if you had a sample JSDoc block which was triggering this ES block that we could discuss.

I'll provide some examples tomorrow, but you can see this clearly if you print out the AST of a comment block from parseComment then the output of commentParserToESTree. I too started investigating around line 395 potentially adding an extra new line, but w/ JS an empty string evaluates to false in a bare conditional if (description) when description is an empty string evaluates to false.

I submitted a PR that adds a spacing option to commentParserToESTree that mirrors the same option available in comment-parser. When spacing is set to preserve empty lines are preserved in the AST parsing and subsequent conversion back to a string via estreeToString. Two new tests were added.
Here is some additional data / example of the problem.
1: Original test comment block with empty lines.

2: Test logging around if (description) showing when description is an empty string it evaluates to false.

3:Test logging output showing skipped empty lines (3 & 5); line 0 should be skipped as it is the delimiter line /**:

4: For a complex markdown comment block what should look like the following.

5: It gets mangled in TypeDoc without the empty line spacing.

Thanks for the extra info.
I think though that if we are adding a "preserve" mode, that we should add the description even for /** (and the line break before */ which is not always present) and leave it to consumers to trim if they wish. There are plenty of users who do like to use the 0th line.

That is to be expected hence the question previously as the conditional I proposed and initially implemented in the PR works for "normal" well formatted comment blocks. I'll start working on permutations. Also checking with estreeToString in the tests. Any chance you can list as many permutations as you can come up with that are known that should parse? I can see this growing into several additional test cases for the preserve option.
IE: This should parse in preserve mode, but it won't currently, etc. Like:
/** A comment */

/** It should
 *
 * parse */

So upon further investigation I'd like to clarify two more things.

Regardless of spacing being compact or preserve there is likely some unwanted behavior in the existing code. For instance /** Should parse */ when run through commentParserToESTree then estreeToString produces /** /** Should parse */. This is a separate issue / code point to examine which is lines 248 - 268

I have so far made the following changes to detect a single line comment block and not include the delimiter / postDelimiter in the single entry of descriptionLines if so and the output will match the input:
      if (end && !tag) {
        ast.terminal = end;
        if (description) {
          if (lastTag) {
            ast.hasPreterminalTagDescription = 1;
          } else {
            ast.hasPreterminalDescription = 1;
          }

          const holder = lastTag || ast;
          holder.description += (holder.description ? '\n' : '') + description;

          // In the end tag handling; check if there are any description lines and if not then this is a
          // one line comment block.
          const isDelimiterLine = holder.descriptionLines.length === 0 &&
            delimiter === '/**';

          holder.descriptionLines.push({
            // If a one line comment block do not include the delimiter.
            delimiter: isDelimiterLine ? '' : delimiter,
            description,
            // If a one line comment block do not include the postDelimiter.
            postDelimiter: isDelimiterLine ? '' : postDelimiter,
            initial,
            type: 'JsdocDescriptionLine'
          });
        }
        return;
      }

As an aside the changes I proposed for the if conditional if ((spacing === 'compact' && description) || (spacing === 'preserve' && delimiter !== '/**')) later on in commentParserToESTree won't be reached due to the early return in the above mentioned block. So far things seem safe in that regard for one line comment blocks, but more exhaustive tests need to be completed.

Is the intention to reformat comment block strings when passing the ESTree AST through estreeToString?

Should this:
/**
 * Should parse one line. */

Result in this:
/**
 * Should parse one line.
 */

Rather than exactly matching the input comment block? This is just for comparisons with new tests I'm writing. I think it's valid to rewrite the comment blocks into well formatted blocks on output, but just want to clarify the intention.

That is to be expected hence the question previously as the conditional I proposed and initially implemented in the PR works for "normal" well formatted comment blocks. I'll start working on permutations. Also checking with estreeToString in the tests. Any chance you can list as many permutations as you can come up with that are known that should parse? I can see this growing into several additional test cases for the preserve option.
IE: This should parse in preserve mode, but it won't currently, etc. Like:
/** A comment */

/** It should
 *
 * parse */

I think you've covered them; i.e., 0th line, intervening lines, and final line. The existing tests should give an idea of permutations, as we have full testing coverage (besides for one file which had been covered when jsdoccomment was just a part of eslint-plugin-jsdoc).

So upon further investigation I'd like to clarify two more things.
1. Regardless of `spacing` being `compact` or `preserve` there is likely some unwanted behavior in the existing code. For instance `/** Should parse */` when run through `commentParserToESTree` then `estreeToString` produces `/** /** Should parse */`. This is a separate issue / code point to examine which is [lines 248 - 268](https://github.com/es-joy/jsdoccomment/blob/main/src/commentParserToESTree.js#L248-L268)

Feel free to prepare any PRs to fix these issues. eslint-plugin-jsdoc does not use all these APIs, so we might not have discovered as many bugs like this.

2. Is the intention to reformat comment block strings when passing the ESTree AST through `estreeToString`?

Should this:
/**
 * Should parse one line. */

Result in this:
/**
 * Should parse one line.
 */

Rather than exactly matching the input comment block? This is just for comparisons with new tests I'm writing. I think it's valid to rewrite the comment blocks into well formatted blocks on output, but just want to clarify the intention.

It'd be ideal, I think, if we could allow both via config, since "well-formatted" is a bit subjective, (even if newlines at the beginning and end are more typical) and I tend to favor the ability to either have full round-trippability or something akin to linting (for "fixing" the formatting). But that isn't critical now.

OK.. I have everything working smoothly and the associated PR is updated with new tests and ready for review. In the process of roundtrip testing for parseComment -> commentParserToESTree -> estreeToString I also fixed the 0th / single line issue of the duplicated leading /** delimiter as these changes go hand in hand.


Bower?

Any chance of making Vuikit available on bower?

Honestly, don't see any advantage. What does Bower solve that you can't with NPM?

Nothing. But some people and projects use bower, some use npm. Forcing people to use npm to manage a dependency on a bower based project could discourage adoption.
Making it available via bower will potentially increase adoption.

Will keep that in mind, but taking in consideration Bower usage is decreasing and supporting two methods for the same feature is not a good idea, I must decline. At least until further notice :)

Ok. As a data point, Vue supports bower.

Do you happen to know how is done by Vue? I can't find any script or repo regards it.

Good question. There is a bower.json file at the top of the repo on the 1.0 branch, but I don't see it on the 2.0 branch. Yet Vue 2.0 is available in bower.

If there is a way to automate it, I have no problem on adding the script. But so far, no clue on how is done with Vue2.

Even thought the bower spec says a repo has to have a bower.json file, I'm beginning to think it is actually optional. So, maybe all you need to do is register the repo:
https://bower.io/docs/creating-packages/#register

Done, try it please :)

Success!
$ bower install vuikit
bower vuikit#*              not-cached https://github.com/vuikit/vuikit.git#*
bower vuikit#*                 resolve https://github.com/vuikit/vuikit.git#*
bower vuikit#*                checkout 0.6.0
bower vuikit#*                resolved https://github.com/vuikit/vuikit.git#0.6.0
bower vuikit#^0.6.0            install vuikit#0.6.0

vuikit#0.6.0 ../bower/vuikit
$

Thanks!

No problem :)