WIP: Add testnode and client-demo

Codecov Report

Merging #26 into master will decrease coverage by 0.77%.
The diff coverage is 96.49%.

@@            Coverage Diff             @@
##           master      #26      +/-   ##
==========================================
- Coverage    99.4%   98.63%   -0.78%
==========================================
  Files           4        6       +2
  Lines         508      661     +153
==========================================
+ Hits          505      652     +147
- Misses          3        9       +6

Impacted Files
Coverage Δ

src/lib.rs
100% <ø> (ø)
:arrow_up:

src/accountant.rs
99.31% <100%> (+0.2%)
:arrow_up:

src/historian.rs
100% <100%> (ø)
:arrow_up:

src/log.rs
98.11% <89.58%> (-1.14%)
:arrow_down:

src/accountant_skel.rs
95.55% <95.55%> (ø)

src/accountant_stub.rs
98.68% <98.68%> (ø)

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 f3dd479...3fcc2dd. Read the comment docs.


Is it possible to get updates, without notification builder?

Hi @DalveerSinghDaiya !
sorry for the delay 😔
I'm afraid not because the notification is needed in order to keep the service alive.

OK thanks !!
Dalveer Singh Daiya
Add Worth Rise Technologies
Website : https://www.awrtechnologies.com
Email<EMAIL_ADDRESS>https://www.awrtechnologies.com/>
On Wed, May 31, 2017 at 12:28 AM, Miguel Garcia<EMAIL_ADDRESS>wrote:

Hi @DalveerSinghDaiya https://github.com/dalveersinghdaiya !
sorry for the delay 😔
I'm afraid not because the notification is needed in order to keep the
service alive.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/miguelbcr/RxGpsService/issues/8#issuecomment-304974994,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AVn7wxl3_Z18lNcvq4N2GdgF28q0qmPDks5r_GbygaJpZM4NN4xM
.


Subfield assignment error message unhelpful

Type of issue:  other enhancement

Impact: no functional change

Development Phase: request
Other information

What is the current behavior?
Currently, attempting to assign a subfield like so:
cmdq_wrdata(127,0) := rxIO.rx_wrc_rd_data

results in a pretty confusing exception chisel3.internal.ChiselException: Cannot reassign to read-only UInt<128>.
What is the expected behavior?
Something that explains that subfield assignment isn't allowed and suggests using vectors bundles (even though I'm of the belief Chisel should support something so natural to hardware engineers as bit assignment).
Please tell us about your environment:
version: 3.4.1
What is the use case for changing the behavior?
Give better guidance on subfield assignment. A majority of people starting from SystemVerilog who look at https://github.com/freechipsproject/chisel-cheatsheet are going to try extracting the bitfield and then assigning to that bitfield. While I believe this should be legal in Chisel, if it's not going to be, it should at least be clear to the user as to what's going on.
Since https://github.com/chipsalliance/chisel3/issues/878 is closed and fwiw: I'm planning to use blackboxes / inline verilog to get around the issue of not being able to directly do sub-word assignment.

Maybe you wanna take a look at the dataview api by @jackkoenig. IIRC, it should resolve this issue elegantly.

Maybe you wanna take a look at the dataview api by @jackkoenig. IIRC, it should resolve this issue elegantly.

I'm taking a deeper look into Dataview. I'm not quite sure on what the Dataview solution would look like (something with viewing Uints as BigInts?).
However, there is a simpler, albeit unnatural, workaround for Reg. Build the field with the necessary subfield replaced on the right-hand side.
cmdq_wrdata  := cmdq_wrdata(255, 128) ## rxIO.rx_wrc_rd_data

This will not work for wire types however due to combinational loops and perhaps DataView and viewing UInt as BigInt can provide a solution in that case.


Improved naming convention Update and rename CONTRIBUTING.md to readme.md

Task/Issue URL:
Tech Design URL:
CC:
Description:
Steps to test this PR:
1.
1.

Internal references:
Software Engineering Expectations
Technical Design Template

Please follow our contributing guidelines from https://github.com/duckduckgo/Android/blob/develop/CONTRIBUTING.md


update date-fns to v3

Thanks for the great package, I've been using it for a while on various projects. It would be great to update date-fns to the latest v3 version or set it as peer-dependency to stay compatible.
I would have liked to provide a PR, but the husky precommit prevents me from doing so.

sorry, was on holiday. will release a new version with an updated date-fns here in a few minutes.


Display caps-lock status on proxy credential window

When a system proxy is detected by VSCode, a window opens asking for proxy credentials. This window would benefit from displaying whether or not the user has the caps lock on when typing in the password.
I would be happy to create a PR and add this feature in if we can agree that this would benefit other users.
(FYI - This is my first logged issue, and would be my first PR, please let me know if I need to provide any additional information)

This window would benefit from displaying whether or not the user has the caps lock on when typing in the password

We are using a normal standard HTML input field of type password in this case if I remember correctly. If there is a usability issue with this, I would think it should be addressed in the runtime (Electron, Chromium) and not VS Code that just utilizes this widget. Does that make sense?

This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines.
Happy Coding!


JSON.stringify leading to bug in timestamp parsing

I think 00d1348a14c10a617e489523953b84a9b18f1b46 might have lead to a bug in parsing timestamps for visualizations. Since JSON.stringify adds quotes around the timestamp, all timestamp are parsed as 0.

A temporary fix if someone really needs their visualizations (and happen to come by here) is to change the timestamp to a category field instead =)

Good catch! Deployed c66301aedb3d04d36e12de5d4e42eddbd7c7a871 for now.


k8s: add comment that this code is copied in helmclient

Towards https://github.com/giantswarm/giantswarm/issues/4709.
Follow up of https://github.com/giantswarm/helmclient/pull/65.

Closing. See https://github.com/giantswarm/helmclient/pull/65#issuecomment-442856301.


Add mapping constructor support to constant

Description:
Need to add mapping constructor support in constants.
Eg -
const map<string> m = { "k": "v" };

Record literal support is added with https://github.com/ballerina-platform/ballerina-lang/pull/14185.


Automator: update common-files@master in istio/istio@master

Generated by Automator - 2022-05-20T16:18:04+00:00

@istio-testing: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-operator-controller_istio
4e45a0de3dfe4a9ffb9be3222e822818b27af042
link
true
/test integ-operator-controller_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-operator-controller_istio


"warning: failed to get scripting definition"

$ yabai
2019-06-22 16:23:11.127 yabai[555:8381] warning: failed to get scripting definition from /System/Library/CoreServices/Dock.app; it may not be scriptable.
yabai configuration loaded..

Does this indicate installing the sa-additions failed? I did run the command without error.
macOS 10.14.5

This warning is just because there is no .sdef file within the Dock.app "folder".
This file is supposed to define an interface for applications that provide an API such that external software written by other people can call functions or otherwise interact with a running instance of the application. (see e.g Spotify as an example).
The Dock.app provides no such definition, and that is what this warning is about.
It is not related to how we use the Scripting Bridge framework for code injection.
Hopefully this clears up some misconceptions regarding this warning.
For people who are interested in more information, search for"sdef", "scripting bridge framework", "scriptable applications" on google/apple docs.

@dominiklohmann
Maybe we should mention something about this warning as well in the wiki somewhere? I've given a few attempts at trying to silence the warning before we issue the load command, but I cannot seem ti silence it..

Noted.
Did you try temporarily redirecting stderr to /dev/null while loading the scripting addition using freopen, unless --verbose is set?

No need to mention it, apparently I was just doing some dumb mistake last time I attempted to temporarily redirect stderr to /dev/null

Noted. 😅


[PROPOSAL] Use with golang Elastic Search equivalent

What kind of business use case are you trying to solve? What are your requirements?
Need golang server to have more control over our destiny and hate the JVM ( sorry )
What is the problem? What is preventing you from meeting the requirements?
We are golang coders in the team and so using a golang server is much easier.
What are you proposing? What do you suggest we do to solve the problem or improve the existing situation?
THIS: https://github.com/prabhatsharma/zinc
Its taking off. Does not have clustering yet
but there is another clustered one here https://github.com/mosuka/phalanx, but it needs the ziny APi on top of it.
What are your assumptions or prerequisites?
Dont think i am assuming much. but i probably dont know what i dont know.
What are remaining open questions?
i would like to know if this interests the community.
I can put time into it, but it would be nice to know if others like this idea and is they also want to get involved.

If Zinc has a 100% compatible API with ES/OpenSearch, then this client should "just work". Have you tried it?

I plan to work on it .
zinc does not yet provide all of the API but it’s does cover done of it .

Cc
@prabhatsharma

Given @mosuka's intention to create a different kind of database without all of the methods of opensearch, I propose we close this Issue.


@W-12627096@ Improve accessibility of variation attribute swatches

Description
The implementation of the swatches is weird.  Ideally, I would have liked to refactor this to use native radio inputs, because that would be simpler and more semantically correct. However, I couldn't get our current logic ("selected value" derived from the URL) to work nicely with Chakra's radio hooks/components (which, btw, are not particularly accessible!), so I gave up on that approach and just added missing accessibility features to the existing solution. Namely, I made tab navigation skip non-selected radio buttons and added the ability to select options using the arrow keys (see native behavior here). This seems to be as close to the native behavior as we can reasonably get, without doing a complete refactor of the component.
I also pulled the component out into a new file, because the indentation was getting excessive.

Types of Changes

[ ] Bug fix (non-breaking change that fixes an issue)
[ ] New feature (non-breaking change that adds functionality)
[ ] Documentation update
[ ] Breaking change (could cause existing functionality to not work as expected)
[ ] Other changes (non-breaking changes that does not fit any of the above)

Breaking changes include:

Removing a public function or component or prop
Adding a required argument to a function
Changing the data type of a function parameter or return value
Adding a new peer dependency to package.json

Changes

(change1)

How to Test-Drive This PR

Start dev server
Visit a product with variants
Tab through the page
When on the radio buttons, use the arrow keys to change the selection
Do a little dance
Use VoiceOver to validate that each variation attribute is read out like a native radio group

Checklists

General

[ ] Changes are covered by test cases
[ ] CHANGELOG.md updated with a short description of changes (not required for documentation updates)

Accessibility Compliance
You must check off all items in one of the follow two lists:

[ ] There are no changes to UI

or...

[ ] Changes were tested with a Screen Reader (iOS VoiceOver or Android Talkback) and had no issues
[ ] Changes comply with WCAG 2.0 guidelines levels A and AA
[ ] Changes to common UI patterns and interactions comply with WAI-ARIA best practices

Localization

[ ] Changes include a UI text update in the Retail React App (which requires translation)

@wjhsf I checked out the changes localhost, it seems like the variants are not tablable, and when non variant is selected, using arrow keys are also not working, it will scroll the page. It only works when I use my mouse to click on the selection, then i can use arrow keys to move the variant selection.  This seems like less accessible then before imo because I have to use my mouse to locate the variant buttons before I can use the arrow keys

@wjhsf I checked out the changes localhost, it seems like the variants are not tablable, and when non variant is selected, using arrow keys are also not working, it will scroll the page. It only works when I use my mouse to click on the selection, then i can use arrow keys to move the variant selection. This seems like less accessible then before imo because I have to use my mouse to locate the variant buttons before I can use the arrow keys

Is that the case when viewing this product? I can tab / arrow just fine... 🤔

@wjhsf that is when a variant has been selected, your url has pid, when you navigate from PLP to PDP, there is not variant select yet, so it is impossible to select the variant on that screen unless you use mouse. It was tablable on previous implementation

@wjhsf that is when a variant has been selected, your url has pid, when you navigate from PLP to PDP, there is not variant select yet, so it is impossible to select the variant on that screen unless you use mouse. It was tablable on previous implementation

Thanks for catching that! I've pushed a fix.

@wjhsf Looking at the screenshot linked in the ticket seems that the a11y issue is related to the size refinements buttons of the PLP not having the role HTML attribute.
https://github.com/SalesforceCommerceCloud/pwa-kit/blob/de45adda41e69e3dab53a8567de8e544d17a23ac/packages/template-retail-react-app/app/pages/product-list/partials/size-refinements.jsx#L39
Why are we not making changes to that file to include therole="switch" attribute?

Because I accidentally improved the accessibility of the wrong swatches. 🤦 This PR improves the accessibility of an area unrelated to the ticket.
The root issue of the ticket is that we use buttons to select filters, but don't have any way for a screen reader to tell the user "this filter is not selected; click this button to add it" or "this filter is selected; click this button to remove it". I addressed that issue in #1607 (which is linked to a different ticket that I was working on that touches the same area). My fix is a bit different, it changes the labels rather than updating the ARIA attributes, but it achieves the same goal.


add option to change chiclet items corner style

upgrade to version 1.1.0.
add option to change chiclet items corner style (rounded/square/cut)

Hi @b-vikras, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution!
You've already signed the contribution license agreement. Thanks!
The agreement was validated by Microsoft and real humans are currently evaluating your PR.
TTYL, MSBOT;


Explore the API gateway Kong

Kong seems to be one - if not the one - most popular API gateway solution based on its popularity on GH. This project is open source (Apache 2.0).

https://github.com/Kong/kong
Spring Boot Apps with Kong API Gateway using OpenAPI & Declarative Configuration

Spring Boot Apps with Kong API Gateway using OpenAPI & Declarative Configuration

Compatible with OpenAPI generator?

So far Spring Eureka Server used in the articles I read does the job.


Problem with git-commit-id-plugin

I had to comment the version of git-commit-id-plugin, I had the following error when i compiled mandrel:
[ERROR] Failed to execute goal pl.project13.maven:git-commit-id-plugin:2.2.0:revision (default) on project core: The plugin pl.project13.maven:git-commit-id-plugin:2.2.0 requires Maven version [3.1.1,) -> [Help 1]
After comment, i can compile.

Ok, can you try with the version 2.1.15? The 2.2.0 has some major changes, but I was not aware of the Maven compatibility.

No, 2.1.15 same error.

Maven 3.1.1 was released in 2013 and is no more recommanded, Mandrel use Maven 3.3+, the documentation is updated with the compatibility.


Development

Coverage increased (+1.0%) to 96.951% when pulling 5f319749469b6d03c4924750dc06da392a637fd6 on development into 6edb9e84aafc7e7e8c75c38b194d3cbcf4986044 on master.


Google Colab LORA Dreambooth Dependency Issue

@Linaqruf please when u free fix this problem , thx for ur hard work


chore(master): release 0.11.0

:robot: I have created a release beep boop
0.11.0 (2024-04-25)
Features

updating from newer svd2rust (#90) (1fd8b67)

Bug Fixes

deps: update rust crate cortex-m-rt to 0.7.4 (#92) (606dcab)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/xmc-rs/xmc4500/releases/tag/v0.11.0 :sunflower:


Should JavaScript.Web.AnimationFrame re-export OnBlocked?

Using the AnimationFrame things requires an import of the GHCJS.Foreign.Callback to use the OnBlocked data type, exported by the seemingly unrelated (in hiearchy) module GHCJS.Foreign.Callback.
There's also the same data type in GHCJS.Concurrent, which I think is really the place that it should be in (or at least canonically exported from).
Todo:

Remove OnBlocked from GHCJS.Foreign.Callback, use the one from GHCJS.Concurrent instead
Decide whether GHCJS.Foreign.Callback and JavaScript.Web.AnimationFrame should re-export OnBlocked.

Important thing done, getting rid of the duplicate OnBlocked


Karma: configure the static asset proxy

Partial for #1721.

I also added props to unrandomize element location for now.


T5 support more model types

Hi,
I am following the enc_dec example and after changing a bit your code and adapting it to my case, I am hitting a wall when defining the weights. I see the example is running t5-small, my version is a t5-large, but after changing the config.ini with my values I expected it to run.
The error:
Traceback (most recent call last):
  File "/code/tensorrt_llm/TensorRT-LLM/examples/enc_dec/build.py", line 365, in <module>
    run_build(component='encoder')
  File "/code/tensorrt_llm/TensorRT-LLM/examples/enc_dec/build.py", line 357, in run_build
    build(0, args)
  File "/code/tensorrt_llm/TensorRT-LLM/examples/enc_dec/build.py", line 329, in build
    engine = build_rank_engine(builder, builder_config, engine_name,
  File "/code/tensorrt_llm/TensorRT-LLM/examples/enc_dec/build.py", line 228, in build_rank_engine
    load_t5_from_pytorch(tllm_model,
  File "/code/tensorrt_llm/TensorRT-LLM/examples/enc_dec/weight.py", line 180, in load_t5_from_pytorch
    layer.mlp.fc.weight.value = pytorch_model[
KeyError: 'encoder.block.0.layer.1.DenseReluDense.wi.weight'

I currently use fastertransformer_backend to optimize T5, but I see maintenance effort is dropped. Plus, it is not great not to be able to select GPU in the instance group config for triton server...
So I have two questions:

Do you plan to add support to T5 as an alternative to the fastertransformer repo?
If so, as a feature request, could we get a more general optimization for different T5 models? Or an explanation on how to adapt the current t5-small example?

Thank you for the amazing work!

Hi @VictorM-PS ,
We're in the progress of adding full support for general T5 and BART etc models. With that, simply specifying model name t5-xx can automatically handle the config setup without hardcoded values and manual changes.
Before that, please kindly make the two changes below to make t5-large working:

In load_t5_from_pytorch() in weight.py, please change the hardcoded line to pytorch_ckpt = torch.load(os.path.join(pytorch_ckpt_path,'t5-large.ckpt')). Again, this will soon be made more flexible instead of hardcoded.
in models/config.ini, I changed these fields in both [encoder] and [decoder] to make t5-large running:
n_layer = 24
n_head = 16
hidden_size = 1024
ffn_hidden_size = 4096
...
n_positions = 512

As for the triton server question, are you aware of the corresponding TRT-LLM backend released at the same time as the main repo: https://github.com/triton-inference-server/tensorrtllm_backend?
T5 is not supported in Triton TRT-LLM yet, but this can give you a flavor of TRT-LLM equivalent of the previous Triton FT path.

Hi @VictorM-PS , more general T5 and Flan-T5 support has been done and scheduled for TRT-LLM's 0.6.0 monthly release soon. Please stay tuned.

Hi @symphonylyh, thank you very much for the heads-up and the amazing work! :)

@VictorM-PS
actually it has been released to dev branch (i.e., main) earlier! please check: https://github.com/NVIDIA/TensorRT-LLM/discussions/424

Let me close this issue as the support has been released. Feel free to reopen if needed.

Hi @yuanze1024 , thanks, yes it seems other Flan-T5 variants all have a n_positions (unused though) but only flan-t5-xxl does.


Stop migration pipeline on failure.

Pull Request Test Coverage Report for Build 200

32 of 33 (96.97%)  changed or added relevant lines in 6 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+2.7%) to 94.026%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/Business/Repository/ElasticsearchMigrationStep.php
2
3
66.67%

Totals

Change from base Build 191:
2.7%

Covered Lines:
362

Relevant Lines:
385

💛  - Coveralls


Deprecation warnings at run time

bundle exec jekyll serve produces the below warnings:
rules will be changing to match the behavior specified by CSS in an upcoming
version. To keep the existing behavior, move the declaration above the nested
rule. To opt into the new behavior, wrap the declaration in `& {}`.

More info: https://sass-lang.com/d/mixed-decls

   ╷
20 │ ┌   @media (prefers-color-scheme: dark) {
21 │ │     background: $projectbox-dark;
22 │ │   }
   │ └─── nested rule
23 │     height: 200px;
   │     ^^^^^^^^^^^^^ declaration
   ╵
    projects.scss 23:3                                  @import
    /home/bod/dev/beod.co.uk/assets/css/main.scss 23:9  root stylesheet
Deprecation Warning: Sass's behavior for declarations that appear after nested
rules will be changing to match the behavior specified by CSS in an upcoming
version. To keep the existing behavior, move the declaration above the nested
rule. To opt into the new behavior, wrap the declaration in `& {}`.

More info: https://sass-lang.com/d/mixed-decls

    ╷
20  │ ┌   @media (prefers-color-scheme: dark) {
21  │ │     background: $projectbox-dark;
22  │ │   }
    │ └─── nested rule
... │
24  │     width: 100%;
    │     ^^^^^^^^^^^ declaration
    ╵
    projects.scss 24:3                                  @import
    /home/bod/dev/beod.co.uk/assets/css/main.scss 23:9  root stylesheet
Deprecation Warning: Sass's behavior for declarations that appear after nested
rules will be changing to match the behavior specified by CSS in an upcoming
version. To keep the existing behavior, move the declaration above the nested
rule. To opt into the new behavior, wrap the declaration in `& {}`.

More info: https://sass-lang.com/d/mixed-decls

    ╷
20  │ ┌   @media (prefers-color-scheme: dark) {
21  │ │     background: $projectbox-dark;
22  │ │   }
    │ └─── nested rule
... │
25  │     overflow: hidden;
    │     ^^^^^^^^^^^^^^^^ declaration
    ╵
    projects.scss 25:3                                  @import
    /home/bod/dev/beod.co.uk/assets/css/main.scss 23:9  root stylesheet
Deprecation Warning: Sass's behavior for declarations that appear after nested
rules will be changing to match the behavior specified by CSS in an upcoming
version. To keep the existing behavior, move the declaration above the nested
rule. To opt into the new behavior, wrap the declaration in `& {}`.

More info: https://sass-lang.com/d/mixed-decls

    ╷
20  │ ┌   @media (prefers-color-scheme: dark) {
21  │ │     background: $projectbox-dark;
22  │ │   }
    │ └─── nested rule
... │
26  │     display: table;
    │     ^^^^^^^^^^^^^^ declaration
    ╵
    projects.scss 26:3                                  @import
    /home/bod/dev/beod.co.uk/assets/css/main.scss 23:9  root stylesheet```

Fixed in #12

Fixed in #12


In holofuel cli querying for pending returns an error

When I use an option p I receive a following error:
 [root@qaNet-reserve-controller:~]# hf p
 Error: invalid type: integer `1689604857696370`, expected a string

Option p calls get() method. In line 16 code is trying to deserialize a zome call result and obviously fails.

Let's look at types returned vs expected:

In this repo: Transaction
in holofuel: Transaction

This points to an issue that holofuel's Timestamp serializes to integer while hf-cli is expecting String


Uncaught Failed resolution of: Lcom/google/android/gms/R$string;

Finally got the module to run after a few hoops then when I tried to registerforpushnotifications I now get this error.  Any ideas?
Ti.Goosh 2.0.6
Titanium 6.0.4
[ERROR] :  TiExceptionHandler: (main) [204,206] ----- Titanium Javascript Runtime Error -----
[ERROR] :  TiExceptionHandler: (main) [0,206] - In /app.js:341,11
[ERROR] :  TiExceptionHandler: (main) [0,206] - Message: Uncaught Failed resolution of: Lcom/google/android/gms/R$string;
[ERROR] :  TiExceptionHandler: (main) [0,206] - Source: 		TiGoosh.registerForPushNotifications({
[ERROR] :  V8Exception: Exception occurred at /app.js:341: Uncaught Failed resolution of: Lcom/google/android/gms/R$string;
[ERROR] :  V8Exception: Failed resolution of: Lcom/google/android/gms/R$string;
Not sure if its relevant or related but incase it is, I also use Ti.GA and used the gps-jars folder fix which works and allows me to atleast launch the app with both modules enabled.  But as soon as I try to registerforpush then this error pops up

Make sure the app is using the correct module version. Copy both Ti.GA and ti.goosh in your app's modules folder. In tiapp.xml specify the version along the module name for ti.goosh and ti.ga.
Let me know if this fixes the issue

@progress44 I believe it is using the correct module version as the app successfully launches (it would not even launch without the gps-jars fix).
Ti.Goosh 2.0.6
Ti.GA 3.0.7
I only have 1 version of each of the modules in fact.
However, this bug or exception pops up if I try to actually call the registerforpushnotifications function.
Thanks much!  Can't wait to get Ti.Goosh running

Even if I delete Ti.GA altogether and run Ti.Goosh alone I have the same set of errors

Hello. Good evening. I have the same issue also.
Does anyone know if there is a workaround for this? I have the same issue:
[ERROR] TiExceptionHandler: (main) [1297,1297] ----- Titanium Javascript Runtime Error -----
[ERROR] TiExceptionHandler: (main) [0,1297] - In /tailored.js:1557,51
[ERROR] TiExceptionHandler: (main) [0,1297] - Message: Uncaught Failed resolution of: Lcom/google/android/gms/R$string;

Thanks, and best,
Antonio

Hi all,
I'm testing the module on a clean app adding the following modules as well.

ti.ga (3.0.0)
ti.map (3.0.1)

The steps I took are these:

Created new app
Added the modules ti.ga, ti.goosh, ti.map locally to the app
Added jar google-play-services-gcm+analytics+maps.jar in lib folder in ti.goosh
Removed all jars from ti.ga lib folder and ti.map lib folder
Removed assets/Readme from ti.goosh.jar (it's a simple zip archive)
ran app

App opens. At this point I changed alloy.js to execute registerForPushNotifications() as in the documentation
Added gcm sender id
  <property name="gcm.senderid">785852287040</property>

When launching the app, in the terminal I see correctly
Notifications: device token is fno50kOLlOU:APA91bFTezbb-nqsx5LeO0mPot117GEJc3amuyPGxludPqrRBJv7QBZiMPSnMDsOyVt3jJY8GqIQn6-feqnP_B3s8rj4kYaT20gQpygVtPMi_0D1nt_lUdHj6NP3slHyx4uCfa8CDf8k

Make sure to have Google Play Services APK (https://developers.google.com/android/guides/setup)
For Genymotion:
Visit opengapps.org
Select x86 as platform
Choose the Android version corresponding to your virtual device
Select nano as variant
Download the zip file
Drag & Drop the zip installer in new Genymotion virtual device (2.7.2 and above only)
Follow the pop-up instructions


[YUNIKORN-1112] Use K8s ENV vars to locate yunikorn service from within admission controller

What is this PR for?
In certain networking environments (such as EKS with Calico), the yunikorn-service DNS entry is unavailable within the admission controller when running in the host network. However, we can use Kubernetes ENV vars to locate the service.
This patch uses YUNIKORN_SERVICE_SERVICE_HOST and YUNIKORN_SERVICE_SERVICE_PORT in preference to SCHEDULER_SERVICE_ADDRESS if present.
What type of PR is it?

[x] - Bug Fix
[ ] - Improvement
[ ] - Feature
[ ] - Documentation
[ ] - Hot Fix
[ ] - Refactoring

Todos

[ ] - Task

What is the Jira issue?
https://issues.apache.org/jira/browse/YUNIKORN-1112
How should this be tested?
Verified with local deployment using the new syntax.
Screenshots (if appropriate)
Questions:

[ ] - The licenses files need update.
[ ] - There is breaking changes for older versions.
[ ] - It needs documentation.

Withdrawing patch as this will not survive service restarts.


Bugfix: 193

This generically fixes issue #193, with clicking around causing completions to stay visible and potentially outdated. We might want to add logic to re-evaluate if there's a new line, but I figured it would be better to wait until someone actually complains about it.

Looks good! Thanks for the fix, @bert88sta !


Update to jQuery 1.12.4 and jQuery Migrate 1.4.1 - fixes 2932

Fixes #2932.

Refactors module wirings to remove redundancy so I only have one place to udpate
Updates jQuery to the latest 1.x and jQuery Migrate 1 to the latest.
Updates Suggest widget to a slightly later version which doesn't use browser.msie
Updates property getting/setting code for checked, disabled, value properties to not use .attr(), .removeAttr() and other obsolete methods.

A cursory check of the various dialogs seems to indicate that that covers the bulk of the issues for this version of jQuery, but we should keep an eye on the Javascript console for a while to see if there are other migration issues to be addressed.

I cleaned up a few more loose ends and took a pass through all of the dialogs in the UI without finding any new jQuery Migrate warnings, so I think this is as good as I'm going to get it. The jQuery Migrate plugin should protect us from any remaining issues, but it would be useful if developers could run with the Javascript console when possible to spot any additional warnings.
Next steps are:

remove the jQuery Migrate plugin and make sure everything still works
Update to jQuery 3.5 and jQuery Migrate 3.3 and start the whole process over again

@tfmorris I got this one that popped up.

let me try to get the context...

Clicking About link under Preferences , Help causes some problem

This popped up when clicking on one of these in the Extract Operation History dialog:

individual checkboxes
Select All
Unselect All

But cannot get it to trigger again...wtf?  Does it only trigger once for this Jquery Migrate logging? That would be non-helpful?

@tfmorris maybe we should clarify... is a Jquery Migrate warning going to show up in yellow (!) icon in Firefox with the prefix JQMIGRATE: ? or does it appear differently? I'm wondering what an INFO versus a WARNING might look like in the context of JQMIGRATE since I want to be helpful here and not waste my time or yours.

Columnize by Key/Value Columns
JQMIGRATE: jQuery.fn.attr('selected') may use property instead of attribute

Facet by choice counts

This one is weird...
happened once I clicked on a Star in the History tab on Expression Editor, I think after clicking on Reuse links.

@thadguidry I believe they will all have the JQMigrate: prefix with a Warning severity, followed by the traceback as Info severity messages. The traceback is very valuable for figuring out where the error occurs.
@wetneb I'll take a closer look at the Suggest plugin changes. Unfortunately, with Google Code shut down, the SVN history isn't available to extract a patch that I could apply. Perhaps I'll jut fix the msie.browser error and leave the rest alone.

@thadguidry I reviewed all of those errors and, as far as I can tell, they all represent things that I've fixed already, except for the last one, which I can't reproduce and doesn't have enough context to be able to figure out what's going on (the entire traceback appears to be jQuery functions). Can you double check that you've got the latest code from the branch and perhaps do a refine clean then refine build to make sure that everything is up to date?

In itself, this change should not break extensions - it should just emit warnings when they are using deprecated APIs, right?

Correct. The Migrate plugin both acts as a shim to restore the deprecated behavior, as well as warning of its use, but only on the Javascript console and only if the non-minified developer version is used. Merging this PR should have no impact on extensions.

But I wonder how the broader migration should fit with our release process.
So, do we need to have one stable release with this step of the migration only, in order to give time to extension maintainers to see the warnings this emits, before migrating to a newer major version of jQuery? Or do you see a way to get this done faster?

This ties in to the discussion that I tried unsuccessfully to start on the dev list about what interfaces we keep stable and what guarantees we offer related to them. Are there no extensions which have yet repaired the JSON & CSRF breakage, I'd be tempted to just bundled everything together as one giant breaking change. Do we have an inventory of what extensions support what OpenRefine versions?

I am not aware of a way for extensions to isolate their own jQuery version…

I think you can get namespace isolation using one of the module systems, but I'm not sure whether that would require OpenRefine to move to a module system first.

(On that note, if you want to take the responsibility of managing the release process for 3.5, I am not going to stand in the way! But no worries if not)

I'm happy to have that discussion when we know what the timing and content is.

@tfmorris OK cleaned and built...testing on your branch... I'll start logging these down in comments starting now...(as you fix them with pushed commits, I'll keep pulling and testing/retesting)
When clicking on project tags this is thrown:
Attribute selector with '#' must be quoted: #projectTags a[href=#records]

Clicking a Star on GREL History throws...

I'll start logging these down in comments starting now...(as you fix them with pushed commits, I'll keep pulling and testing/retesting)

Let's just create new issues for them. Unless we find a functional problem, we should just merge this PR and fix the Migrate warnings later, as we find them. I already created an issue for your second issue yesterday #3013.
Speaking of functional issues, though, is the expression dialog much wider than normal or is that my imagination?

@tfmorris Ah, gotcha...you want to address additional stuff after we get this merged...sounds like a better plan and I agree, otherwise it gets confusing for me also!
Yes, Expression dialog is wider but I think only in certain contexts?  We'll figure that out later.

@tfmorris Found the context on wider Expression Dialog ... it seems only on Edit Cells -> Transform ?
There's this: https://github.com/OpenRefine/OpenRefine/issues/1266
And this: https://github.com/OpenRefine/OpenRefine/issues/421
but maybe it was this?  https://github.com/OpenRefine/OpenRefine/commit/bd07fe0e1aacb2e1c12ecb2082b916f14bf24661

@tfmorris Should /benchmark/.factorypath be added to .gitignore ?  I noticed it pulled in.

@thadguidry Thanks. Good to know that the Expression dialog sizing is a preexisting bug (and yes, it was @tfmorris bd07fe0 for #1339 that broke it).

Should /benchmark/.factorypath be added to .gitignore?

No idea. Doesn't appear in my working tree.
I pushed a fix for the "# must be quoted" bug.

Are there no extensions which have yet repaired the JSON & CSRF breakage, I'd be tempted to just bundled everything together as one giant breaking change.

There is the rdf extension, which has been updated for Jackson and CSRF changes. I am not aware of others.

@wetneb Is there anything left to do to get this merged? I think the release strategy discussion affects follow-on steps, not this PR.


Issues with mypy / other CI checks

I think our static type checking configuration might not be 100% correct.

The mypy configuration in pyproject.toml at https://github.com/zarr-developers/VirtualiZarr/blob/b34a1ee47572901ed6a3623c97d340157a0fa62a/pyproject.toml#L75 must be under a tool.mypy prefix, not mypy when you're using pyproject.toml
I think that the mypy configuration in .pre-commit-config.yaml isn't , at least for my machine. Mine fails with ERROR: No matching distribution found for types-pkg_resources. We aren't using pkg-resources, so we shouldn't need that.
IMO, it might make sense to move mypy checks out of pre-commit and to a separate check? I think that mypy requires that 3rd party dependencies be installed into the environment so that those boundaries are type checked. Seems wasteful to install all those deps for testing, and then again for type checking.
I think that pre-commit isn't being run in CI

I have a branch starting to fix these up.
Expanding on issue 3, on main I have two failures:
virtualizarr/zarr.py:98: error: Argument "zarr_format" to "ZArray" has incompatible type "int"; expected "Literal[2, 3]"  [arg-type]
virtualizarr/tests/test_zarr.py:43: error: Argument "filetype" to "open_virtual_dataset" has incompatible type "str"; expected "FileType | None"  [arg-type]

On a branch with that moved to my dev env (and a few modules suppressed, since they don't provide type hints), I get more
virtualizarr/zarr.py:137: error: Function "virtualizarr.zarr.ZArray.dict" is not valid as a type  [valid-type]
virtualizarr/zarr.py:137: note: Perhaps you need "Callable[...]" or a callback protocol?
virtualizarr/zarr.py:253: error: Unsupported operand types for / ("Path" and "Hashable")  [operator]
virtualizarr/zarr.py:289: error: Argument 1 to "list" has incompatible type "tuple[Hashable, ...]"; expected "Iterable[str]"  [arg-type]
virtualizarr/kerchunk.py:226: error: Argument 2 to "variable_to_kerchunk_arr_refs" has incompatible type "Hashable"; expected "str"  [arg-type]
virtualizarr/kerchunk.py:239: error: Argument 1 to "join" of "str" has incompatible type "list[Hashable]"; expected "Iterable[str]"  [arg-type]
virtualizarr/xarray.py:31: error: Definition of "__array__" in base class "ManifestArray" is incompatible with definition in base class "ExplicitlyIndexed"  [misc]
virtualizarr/xarray.py:162: error: Argument 1 to "open_dataset" has incompatible type "Any | IOBase"; expected "str | PathLike[Any] | BufferedIOBase | AbstractDataStore"  [arg-type]
virtualizarr/xarray.py:196: error: Cannot infer type argument 1 of <dict>  [misc]
virtualizarr/xarray.py:196: note: Try assigning the literal to a variable annotated as dict[<key>, <val>]
virtualizarr/xarray.py:379: error: Incompatible types in assignment (expression has type "IndexVariable", target has type "tuple[Hashable, Any, dict[Any, Any], dict[Any, Any]]")  [assignment]
virtualizarr/xarray.py:383: error: Incompatible types in assignment (expression has type "Variable", target has type "tuple[Hashable, Any, dict[Any, Any], dict[Any, Any]]")  [assignment]
virtualizarr/tests/test_zarr.py:43: error: Argument "filetype" to "open_virtual_dataset" has incompatible type "str"; expected "FileType | None"  [arg-type]
Found 13 errors in 5 files (checked 22 source files)

Thanks for the work here, Tom. I actually plagiarized (with credit) the pre-commit config here for another project, and then started hitting the same types-pkg_resources issue as you mention here, so seeing your issue pop up here helped me understand the cause and solution.

We aren't using pkg-resources, so we shouldn't need that.

Yes, same in my other project 😮💨

I think this is all resolved now.


how git you code?

how can i get your code, so i can run it on my local computer?

Hi Just fork it or clone.

git clone https://github.com/vijishmadhavan/ArtLine.git in your terminal to clone. Or click the fork button to fork a copy to your own repo then clone to work on. You might be interested in reading up on git and how it works! https://lmgtfy.app/?q=how+to+use+git

Check my new project Toon-Me.
https://github.com/vijishmadhavan/Toon-Me
On Tue, 22 Dec, 2020, 6:55 am Ryan Lewis<EMAIL_ADDRESS>wrote:

git clone https://github.com/vijishmadhavan/ArtLine.git in your terminal
to clone. Or click the fork button to fork a copy to your own repo then
clone to work on. You might be interested in reading up on git and how it
works! https://lmgtfy.app/?q=how+to+use+git
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/vijishmadhavan/ArtLine/issues/4#issuecomment-749285662,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AMVUYPN6BQ5337GUKJX6CWDSV7YPRANCNFSM4U7CXTFQ
.

Check my new project Toon-Me.
https://github.com/vijishmadhavan/Toon-Me
On Tue, 22 Dec, 2020, 6:55 am Ryan Lewis<EMAIL_ADDRESS>wrote:

git clone https://github.com/vijishmadhavan/ArtLine.git in your terminal
to clone. Or click the fork button to fork a copy to your own repo then
clone to work on. You might be interested in reading up on git and how it
works! https://lmgtfy.app/?q=how+to+use+git
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/vijishmadhavan/ArtLine/issues/4#issuecomment-749285662,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AMVUYPN6BQ5337GUKJX6CWDSV7YPRANCNFSM4U7CXTFQ
.


Error when going to Authentication in Settings - Failure Cannot read properties of null

Bug description
Error when going to Authentication in Settings - Failure Cannot read properties of null - Portainer Business 2.12.1 ee
Expected behavior
To open Authentication settings to update/make changes without the error
Portainer Logs
Provide the logs of your Portainer container or Service.
You can see how here
5cf2a24e0f0f   portainer/portainer-ee                           "/portainer"             3 hours ago      Up 3 hours                8000/tcp, 9000/tcp, <IP_ADDRESS>:9999->9443/tcp                                                                                Portainer-Business-Mar-2022
docker container logs 5cf2a24e0f0f
today at 11:45:40 AMlevel=info msg="Encryption key file `portainer` not present"
today at 11:45:40 AMlevel=info msg="proceeding without encryption key"
today at 11:45:40 AMlevel=info msg="Loading PortainerDB: portainer.db"
today at 11:45:41 AMlevel=info msg="Opened existing store" version=35
today at 11:45:41 AMlevel=debug msg="[useractivity] [check_interval_seconds: 86400.000000] [message: starting logs cleanup process]"
today at 11:45:41 AMlevel=info msg="[DEBUG] [message: removed 0 old auth logs]"
today at 11:45:41 AMlevel=info msg="[DEBUG] [message: removed 0 old user activity logs]"
today at 11:45:41 AM2022/03/22 15:45:41 server: Reverse tunnelling enabled
today at 11:45:41 AM2022/03/22 15:45:41 server: Fingerprint 20:19:50:73:a1:53:ae:0b:b1:cf:87:f3:14:c6:0a:5a
today at 11:45:41 AM2022/03/22 15:45:41 server: Listening on <IP_ADDRESS>:8000...
today at 11:45:41 AMlevel=info msg="2022/03/22 15:45:41 [DEBUG] [chisel, monitoring] [check_interval_seconds: 10.000000] [message: starting tunnel management process]"
today at 11:45:41 AMlevel=info msg="[INFO] [cmd,main] Starting Portainer version 2.12.1\n"
today at 11:45:41 AMlevel=info msg="2022/03/22 15:45:41 [DEBUG] [internal,init] [message: start initialization monitor ]"
today at 11:45:41 AMlevel=info msg="2022/03/22 15:45:41 [INFO] [http,server] [message: starting HTTPS server on port :9443]"

Steps to reproduce the issue:

Go to Settings
Click on Authentication
See error

Screenshot:

I can't edit anything or click save.

Technical details:

Portainer version:
Docker version (managed by Portainer): Docker version 20.10.3, build b455053 + docker-compose version 1.28.5, build 324b023a
Kubernetes version (managed by Portainer): N/A
Platform (windows/linux): Linux - Synology DSM
Command used to start Portainer (docker run -d -p 9443:9443 --name=Portainer-Business-Mar-2022 --restart=always -v /var/run/docker.sock:/var/run/docker.sock -v /volume1/docker/Portainer/portainer_data:/data portainer/portainer-ee ):
Browser: Chrome/Firefox
Use Case (delete as appropriate): Using Portainer at Home
Have you reviewed our technical documentation and knowledge base? Yes

Additional context
Similar to old issue # https://github.com/portainer/portainer/issues/2388
This is issue happened after updating my Community Portainer CE with Business EE
https://github.com/portainer/portainer/issues/6690

Update: I managed to do a strange workaround, at least things are working now.
Steps:

You may try to rollback Portainer to use portainer-ce
Then make sure to run only basic authentication (no other SSO) option enabled
And then re-run the docker shell again with the business image portainer-ee
And re-add your SSO authentication settings again there, things should work.

Just encountered this too.

I've also just encountered this issue...

I can reproduce this in 2.19.4
When clicking "Save Settings" the following javascript error is thrown and the settings are not saved.
angular.js:15697
TypeError: Cannot read properties of null (reading 'map')
    at d (settingsAuthenticationController.js:173:35)
    at t.saveSettings [as onSaveSettings] (settingsAuthenticationController.js:133:67)
    at fn (eval at compile (angular.js:16548:14), <anonymous>:4:184)
    at i (angular.js:29123:13)
    at l.$eval (angular.js:19523:16)
    at l.$apply (angular.js:19622:25)
    at HTMLButtonElement.<anonymous> (angular.js:29127:19)
    at HTMLButtonElement.dispatch (jquery.js:5430:27)
    at g.handle (jquery.js:5234:28) undefined

@ansred, I think this issue needs reopening rather than ignoring. It's a bad look for a piece of enterprise software to ignore something like this, especially when it's the additional complexity of there being a different version in the first place that's to blame.

As this issue was opened and closed by a user over a week or so, this likely wasn't something that anyone in the Portainer team saw at the time. With the volume of GitHub issues that we see and the small team we have looking at them, it isn't always feasible that we can see every one (especially those that are closed as completed).
In saying that, this initial issue was reported over two years ago and we've gone through a massive amount of change in the app since then. I can see that more recent comments have indicated the error still occurs, but I suspect this is likely a different error manifesting in a similar error message. I would suggest this be opened as a new issue and we can proceed investigation from there.

As this issue was opened and closed by a user over a week or so, this likely wasn't something that anyone in the Portainer team saw at the time. With the volume of GitHub issues that we see and the small team we have looking at them, it isn't always feasible that we can see every one (especially those that are closed as completed).
In saying that, this initial issue was reported over two years ago and we've gone through a massive amount of change in the app since then. I can see that more recent comments have indicated the error still occurs, but I suspect this is likely a different error manifesting in a similar error message. I would suggest this be opened as a new issue and we can proceed investigation from there.

If the suspicion is that it's not related, feel free to create a new Issue based off of a recent comment, e.g., https://github.com/portainer/portainer/issues/6692#issuecomment-2039333859, and to tag the user and myself in it, though I rather feel my time is better spent looking at alternatives than opening up a GitHub Issue just to repeat what's already been said.


current rustRegistry doesn't have the clap 2.22.1

update rustRegistry
Motivation for this change
Things done

[ ] Tested using sandboxing
(nix.useSandbox on NixOS,
or option build-use-sandbox in nix.conf
on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] Linux

[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Fits CONTRIBUTING.md.

Can you please change the commit message to follow the naming conventions of Contributing.md? I'll merge it right after changing it.

Oh-kay, nevermind then.


[$500] Web - Workspace request money message displays wrong currency before conversion

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:

Open the app
Open settings and click on new workspace
In new workspace, if current currency is not 'USD' the change  to USD and if 'USD', change to any other currency.
In LHN, workspace chat will be created, open it
Click on plus and click Request money
In request money, select currency different then workspace currency eg: In video, INR is selected in request money and workspace currency is USD
Complete the request with any amount
Observe the IOU message displays the workspace currency even before conversion to it eg: In video, it displays $900 instead of ₹900 and few moments later, it converts to $10.9

Expected Result:
Before conversion to workspace currency, app should display request money selected currency symbol in request money message
Actual Result:
Before conversion to workspace currency, app still displays workspace selected currency symbol in request money message
Workaround:
Unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[ ] Android / native
[ ] Android / Chrome
[ ] iOS / native
[ ] iOS / Safari
[x] MacOS / Chrome / Safari
[ ] MacOS / Desktop

Version Number: <IP_ADDRESS>
Reproducible in staging?: y
Reproducible in production?: y
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
https://github.com/Expensify/App/assets/93399543/8ce7b6da-f681-450d-81fb-e615fbc9b982
https://github.com/Expensify/App/assets/93399543/2ff52168-af31-402f-acc3-ddf2a5384427
Expensify/Expensify Issue URL:
Issue reported by: @dhanashree-sawant
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1692866442917089
View all open jobs on GitHub
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~010daaf0b73a652083
Upwork Job ID:<PHONE_NUMBER>519152128
Last Price Increase: 2023-09-13
Automatic offers:

DylanDylann | Contributor | 26746667
dhanashree-sawant | Reporter | 26746668

Reviewing today!

Reviewing today while in the air! Currently taxi'd, will get to once I can hop on wifi! Sorry I didn't get to this last week, had head down on wave4 saastr

Reviewing today while in the air! Currently taxi'd, will get to once I can hop on wifi! Sorry I didn't get to this last week, had head down on wave4 saastr

Reviewing today while in the air! Currently taxi'd, will get to once I can hop on wifi! Sorry I didn't get to this last week, had head down on wave4 saastr

Coming back from conference last week - updating today!

confirmed

Proposal
Please re-state the problem that we are trying to solve in this issue.
Workspace request money message displays wrong currency before conversion
What is the root cause of that problem?
https://github.com/Expensify/App/blob/d68263ad664d8a8a81ca859147696df8abfcd480/src/pages/iou/steps/NewRequestAmountPage.js#L70
If there is no currency in the param we will use currency from iou
What changes do you think we should make in order to solve the problem?
I suggest that we can get policyID from params and get currency of that policy. We only use iou.currency if the currency from policy is falsy
const currency = currentCurrency || policy.currency || iou.currency;

What alternative solutions did you explore? (Optional)

Hi @DylanDylann!
Your solution looks well designed and addresses the issue entirely, as it's the only one here let's see it in action 🚀
🎀 👀 🎀 C+ reviewed

Nice! Let's get that PR raised and merged for that sweet bonus!

@robertKozik I see the problem still happens if we change currency when requesting money. Let's see this case,

Normal case: In the first request money, I request 23000Đ, in the second time I request 23000Đ and then the IOU message will display 46000Đ.
exception case: Turn offline. In the first request money, I request 23000Đ, in the second time I request 1$. what should we do display in the IOU message ? Note that we can't convert currency from FE and we are offline

@dylanexpensify can you confirm the expected use case on @DylanDylann 's question above from the product perspective?

@dylanexpensify Could you help to check above comment?

I posted this question to Slack to get more eyes.
cc @dylanexpensify

@DylanDylann @dylanexpensify I'm not sure how this should look from the product perspective, but maybe we could stick with the current behaviour (even when requests are in different currencies, values are added together as it would be one currency)? Attaching video from the staging env
https://github.com/Expensify/App/assets/61146594/1d48b26e-3706-4a60-81a4-c62d12b5940c

Yeah, it is currently behavior. But it maybe make some confusions when we display incorrect amount

I'd agree we stick with current behavior - but I'm just checking internally to confirm that flow!

@dylanexpensify Gentle bump, Any update here?

@dylanexpensify @robertKozik Any update here?
If we agree with the current behavior, we don't need to do anything in this issue

I think we agree to keep the current behaviour for the offline requests (your exception case described before). How is it interfere with the main problem of this issue?

@robertKozik @danieldoglas
Let's see the current logic:

Case 1: I request $2 in workspace chat, In optimistic data we will convert currency to the default currency of workspace (in this case is đ) then we display đ2. Then the Server returns the correct amount with this currency is đ48609 and the App displays it correctly. The optimistic data are causing flickers
Case 2:  In workspace chat, the first request money I request 23000Đ, in the second time I request 1$. In optimistic data we use currency to the default currency of workspace (in this case is đ) and then we display total amount đ23001 (23000 + 1). Then the Server returns the correct amount with this currency is đ48609 and the App displays it correctly. The optimistic data are causing flickers

Should we consider removing the amount of optimistic data to avoid flicker

I thought that this issue was about the currency symbol flickering and this should be resolved. I think we cannot interfere into the amount, as changing the currency is done on backend.
Don't removing the amount from the optimistic data cause strange UX (request with no amount) when it will be first money request? (being offline scenario)

Sorry, we agreed we always show the report in the output currency of the workspace. @danieldoglas thoughts on keeping this open?

@dylanexpensify I think we still need to fix the flick that is happening right?
based on the original report:
Observe the IOU message displays the workspace currency even before conversion to it eg: In video, it displays $900 instead of ₹900 and few moments later, it converts to $10.9

So even if we're converting on the backend, we should show ₹900 and not $900 when we just create it.

@danieldoglas I agree with you in this comment. But we have another flicker:
In workspace chat, the first request money I request 23000Đ, in the second time I request 1$. In optimistic data we use currency to the default currency of workspace (in this case is đ) and then we display total amount đ23001 (23000 + 1). Then the Server returns the correct amount with this currency is đ48609 and the App displays it correctly. The optimistic data are causing flickers
https://github.com/Expensify/App/assets/141406735/ec76eef9-bc47-4a12-a4dd-64a280c2083e
What is expected for this case? (Note that we can't convert amount currency from FE)

Summary, we have 2 cases that make flickers as mentioned here. We can fix the flicker in case 1 as @danieldoglas mentioned here but flicker in case 2 still happen. As I undestand, We have 2 options:

Do nothing
Remove optimistic data and only update amount of request from BE (don't update amount if user request money offline)

I believe we shouldn't remove the optimistic data in this scenario since the request won't update any visuals while the user is offline.
We should focus on fixing the currency symbol flicker, and leave the amount flicker as it is, since there's no way to predict it for the optimistic data. Alternatively we can close this issue, as flicker on this is unavoidable as exchanging the currency needs the BE

I agree with doing nothing on the second case.

@danieldoglas You mean that we should fix case 1, right? Just a note, case 1 is only an edge case of case 2. If we agree with the behavior of case 2, we should do nothing here (also accept case 1). Only fixing case 1 will make the code complicated and I don't see that It helps to improve UX because users still see a flicker if request money for the second time.
cc @robertKozik

I see, thanks for that @DylanDylann . @dylanexpensify So I think you agree we should do nothing in this case too, right?
I'll be OOO next week, but if you (@dylanexpensify) agree, let's :do-nothing: here.

@dylanexpensify Are we eligible for compensation for our effort? Contributors are already assigned and started on the PR. It's just due to the expectation changes and the solution becomes outdated.

@danieldoglas mind confirming here? ^ If we agree, happy to do so!

@dylanexpensify Yeah, I think compensation is due in this case.

Do we feel fine with $250 @danieldoglas @DylanDylann

That works for me.

I think the payment should be 100% like some other similar cases below:
https://github.com/Expensify/App/issues/26470#issuecomment-1750485083
https://github.com/Expensify/App/issues/26309#issuecomment-1759950890
https://github.com/Expensify/App/issues/21419#issuecomment-1629018328
https://github.com/Expensify/App/issues/22806#issuecomment-1767395619
Anyway, Happy with your decision.

bump @danieldoglas @dylanexpensify

Reopening the issue so we don't lose track of it

@danieldoglas @dylanexpensify Could you help to check this comment

bump @dylanexpensify

Apologies! Looking now

ah, confirming we paid $250, and the request is for an amount of $500? Is that right @DylanDylann ?

@dylanexpensify yeah. But happy with your final decision

Sounds good - thanks for understanding!

@dylanexpensify I haven't received any payment for this issue 😄 Could you help to check again? This is my opinion
cc @danieldoglas

Oh apologies! Jeez - blonde time. Payment of $250 sent, as discussed above!


Link https://www.microsoft.com/download/details.aspx?id=9905 no longer works

Link "https://www.microsoft.com/download/details.aspx?id=9905" to MSTR tool does not work anymore. I get a "Page not found"

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

ID: 507d0de3-492a-3b24-c08c-e771f1cc58e3
Version Independent ID: 69abc2f3-e7d9-43ba-6508-ddc3a3b77f4c
Content: Azure backup and restore plan to protect against ransomware
Content Source: articles/security/fundamentals/backup-plan-to-protect-against-ransomware.md
Service: security
Sub-service: security-fundamentals
GitHub Login: @TerryLanfear
Microsoft Alias: terrylan

@Owenvanderlee - Thank you for sharing your experience with us. The link appears to still be working for me. Can you try again? Thank you.

@Owenvanderlee
Thanks for your feedback! We will investigate and update as appropriate.

@Owenvanderlee
Could you kindly confirm this? The link works perfectly for me.

@Owenvanderlee Could you kindly confirm this? The link works perfectly for me.

Hi, I checked and it works fine for me too now.
Greetz, Owen

@Owenvanderlee - Again, thank you for your interest in our content. Glad to hear the link is now working for you.
#please-close


npm run only-once throw Error: Connection strategy not found     at MongoStore

Challenge Name

Issue Description
'I am following the Getting-Started instructions on https://forum.freecodecamp.com/t/how-to-clone-and-setup-the-free-code-camp-website-on-a-windows-pc/19366
Mongo db is running in the back
After the command rpm run only-once, I get this (see below)...
command_like_logs.txt
$ npm run only-once

<EMAIL_ADDRESS>only-once F:\FreeCodeCamp\freeCodeCamp
npm run create-rev && echo '//' && echo 'Seeding Database' && echo '//' && node seed && echo '//' && echo 'Seeding Completed' && echo '//'

<EMAIL_ADDRESS>create-rev F:\FreeCodeCamp\freeCodeCamp
node -e "var fs = require('fs'); fs.access('./server/rev-manifest.json', function(err) { if (err) { console.log('\n\ncreating manifest\n\n'); return fs.writeFileSync('server/rev-manifest.json', '{}'); } console.log('\n\nrev-manifest present\n\n'); });"

rev-manifest present
'//'
'Seeding Database'
'//'
The user model "User" is attached to an application that does not specify
whether other sessions should be invalidated when a password or
an email has changed. Session invalidation is important for security
reasons as it allows users to recover from various account breach
situations.
We recommend turning this feature on by setting
"logoutSessionsOnSensitiveChanges" to true in
server/config.json (unless you have implemented your own solution
for token invalidation).
We also recommend enabling "injectOptionsFromRemoteContext" in
User's settings (typically via common/models/*.json file).
This setting is required for the invalidation algorithm to keep
the current session valid.
Learn more in our documentation at
https://loopback.io/doc/en/lb2/AccessToken-invalidation.html
The user model "user" is attached to an application that does not specify
whether other sessions should be invalidated when a password or
an email has changed. Session invalidation is important for security
reasons as it allows users to recover from various account breach
situations.
We recommend turning this feature on by setting
"logoutSessionsOnSensitiveChanges" to true in
server/config.json (unless you have implemented your own solution
for token invalidation).
We also recommend enabling "injectOptionsFromRemoteContext" in
user's settings (typically via common/models/*.json file).
This setting is required for the invalidation algorithm to keep
the current session valid.
Learn more in our documentation at
https://loopback.io/doc/en/lb2/AccessToken-invalidation.html
Error: Connection strategy not found
at MongoStore (F:\FreeCodeCamp\freeCodeCamp\node_modules\connect-mongo\src\index.js:105:23)
at sessionsMiddleware (F:/FreeCodeCamp/freeCodeCamp/server/middlewares/sessions.js:15:12)
at EventEmitter.proto.middlewareFromConfig (F:\FreeCodeCamp\freeCodeCamp\node_modules\loopback\lib\server-app.js:74:25)
at F:\FreeCodeCamp\freeCodeCamp\node_modules\loopback-boot\lib\executor.js:353:9
at Array.forEach (native)
at setupMiddleware (F:\FreeCodeCamp\freeCodeCamp\node_modules\loopback-boot\lib\executor.js:340:14)
at execute (F:\FreeCodeCamp\freeCodeCamp\node_modules\loopback-boot\lib\executor.js:40:3)
at bootLoopBackApp (F:\FreeCodeCamp\freeCodeCamp\node_modules\loopback-boot\index.js:154:3)
at Object. (F:/FreeCodeCamp/freeCodeCamp/server/server.js:42:1)
at Module._compile (module.js:570:32)
at loader (F:\FreeCodeCamp\freeCodeCamp\node_modules\babel-register\lib\node.js:144:5)
at Object.require.extensions.(anonymous function) [as .js] (F:\FreeCodeCamp\freeCodeCamp\node_modules\babel-register\lib\node.js:154:7)
at Module.load (module.js:487:32)
at tryModuleLoad (module.js:446:12)
at Function.Module._load (module.js:438:3)
at Module.require (module.js:497:17)
npm ERR! Windows_NT 6.1.7601
npm ERR! argv "C:\Program Files (x86)\nodejs\node.exe" "C:\Program Files (x86)\nodejs\node_modules\npm\bin\npm-cli.js" "run" "only-once"
npm ERR! node v6.10.2
npm ERR! npm  v3.10.10
npm ERR! code ELIFECYCLE
npm ERR<EMAIL_ADDRESS>only-once: npm run create-rev && echo '/****/' && echo 'Seeding Database' && echo '/****/' && node seed && echo '/****/' && echo 'Seeding Completed' && echo '/****/'
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>only-once script 'npm run create-rev && echo '//' && echo 'Seeding Database' && echo '//' && node seed && echo '//' && echo 'Seeding Completed' && echo '//''.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the freecodecamp package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     npm run create-rev && echo '//' && echo 'Seeding Database' && echo '//' && node seed && echo '//' && echo 'Seeding Completed' && echo '//'
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs freecodecamp
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls freecodecamp
npm ERR! There is likely additional logging output above.
npm ERR! Please include the following file with any support request:
npm ERR!     F:\FreeCodeCamp\freeCodeCamp\npm-debug.log

Hi @tharun26, I also just experienced this on my mac, but fixed it when I realised I had missed the step where you copy the .sample.env file into a file called .env:
cp sample.env .env (or the equivalent on Windows)
Have you definitely completed this step?


New sample - Send different types Of Cards using bot: NodeJS.

Execution Of Build PipeLine : https://github.com/OfficeDev/Microsoft-Teams-Samples/actions/runs/3911246730

@Mohammed-MSFT  - Please re-run build pipeline.

@Mohammed-MSFT - Please run build pipeline again and share the updates here.


Bump default to k8s 1.12/stable

Please note that 1.12/stable is currently empty and we still need to promote 1.12.0 there.


Rename notebooks directory

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint.


[language] make standard library scripts generic

Change the payment-related standard library scripts to accept a type argument
Change transaction-builder encoders to accept a TypeTag + refactor accordingly

Motivation
Making scripts more flexible
Have you read the Contributing Guidelines on pull requests?
Y
Test Plan
Refactored existing tests, all pass

:umbrella: The latest upstream changes (presumably bcf18904d6e739adc5a36877d286fb6cbf219de1) made this pull request unmergeable. Please resolve the merge conflicts.

:pushpin: Commit 9888505 has been approved by tzakian

:hourglass: Testing commit 9888505b9474b10c5c47df31f6d5fefad64b23fb with merge a8de12021e92e4ee745884db2f5c8da20ef0a0e4...

:sunny: Test successful - checks-actions_land_blocking_test, checks-circle_commit_workflow
Approved by: tzakian
Pushing a8de12021e92e4ee745884db2f5c8da20ef0a0e4 to master...


final design

The layout is error-free. But you're adding the design under the root directory and not under 'submissions'
I'm closing this. Please resubmit.


Add CurrentTransaction API to context.Database

Issue #5552
/cc @rowanmiller for public surface API docs.

:shipit:

@rowanmiller Will merge now, but I can update doc comments later if needed.

Merged.


Piping has weird behaviors with complex function expressions

This query makes no semantic sense and should be eliminated:

This query makes semantic sense and should execute properly:

Solved in #142


ChromelyResponse won't serialize structs correctly

I made a controller that returns a list of struct objects, each struct with three float values.
When I print the console output in the dev tools or print the JSON representation of the ChromelyResponse object, structs are serialized as {}.
Do structs have to be wrapped in an object in order to be properly serialized?

@nicolasdeory Chromely uses System.Text.Json, so may you want to look closely into that for struct serialization.
May be related to this:
https://github.com/dotnet/runtime/issues/29455
Using what was discussed here, may help:
https://stackoverflow.com/questions/59242149/jsonserializer-struct-with-asp-net-core-3-0
        [Serializable]
        struct Item
        {
            public float x { get; set; }
            public float y { get; set; }
            public float z { get; set; }
        }

            var item= new Item();
            item.x = 10.0F;
            item.y = 10.0F;
            item.z = 10.0F;

            return new ChromelyResponse(request.Id)
            {
                Status = 200,
                Data = item
            };

{
   "RequestId":"",
   "ReadyState":4,
   "Status":200,
   "StatusText":"OK",
   "Data":{
      "x":10,
      "y":10,
      "z":10
   }
}

Thanks for the detailed response. Adding public properties and the Serializable attribute fixes the issue.


Block get stuck !!!!

Hello For testing I created 15 masternode with posv and proposed the masternode on the tomo master app but after certain time I lost my coin base address and 11 nodes are down and get slashed and all the nodes are stuck I can not see any block syncing any data on master node app And block also got stuck in the middle
How can I fix it? It would be great if you can provide any solution

closed, refer to the issue in TomoChain Repo


[Refactor]: Simplify SecurityAnalyzer Logic

Summary
The logic in SecurityAnalyzer (where the initializer registers the securityanalyzer) is not very clear, and could be refactored to something more explicit.
https://github.com/All-Hands-AI/OpenHands/blob/add4653335218eb04d0b7960fa67c21f8e313b8e/openhands/security/analyzer.py#L11

Duplicate of #3624


Removing "Bicep: Open Source" from the command palette

With the move to Showing all bicep commands (#5629), we will also look to make it such that command pallete commands are not "file specific" and are omniscient to the user's workspace.
For that reason, it won't make sense for the Bicep: Open Source command (which has very low usage) to exist out of the context of the image below.

Already have this in a PR.


Changelog for WPCS version 1.2.1

Release date set at this Tuesday December 18th.
Includes all currently merged changes.

[ci skip]

Merging this now so all builds should have passed before the release tomorrow.


Add GoReleaser release action for gotpm CLI

The CLI binary is a useful artifact to have prebuilt and ready to use. This action ensures that all new releases that get cut will have the binary artifacts ready for download for the tableau of supported OSes and architectures.

/gcbrun


Return int for compressStream or endStream in ZstdOutputStream.java?

Hi, @luben why is int returned in java side when the signature in c version's compressStream/endStream is size_t?

The size of "size_t" is platform specific and does not have equivalent on the java side. So we have to map it either to int (32bit) or long (64bit). I am mapping them to int as they are always bounded by the buffers sizes that are less than 2G.

Then what about the error code?
I can see an error code returned as an int will have negative value, then Zstd.isError can just get it right? (negative value converted to size_t, mapped to the corresponding error code?)

The error codes are negative numbers way smaller than what an integer can represent. So there is no loss of information in casting from size_t to int and back. BTW, zstd has also to follow the same constraint if it want to work on platforms where size_t is 32 bit signed integer.

Thanks. I had figured that out, but want to double check with you.


More than 6 classeurs causes scrolling glitch

When I have more than 6 classeurs on the menu, scrolling down messes up the images.
Screenshot:

Note:
It's the background tabs on the classeurs glitching out, the program is still completely usable.

Reproduced. Looks like a Chrome issue though. Will investigate.

Should be fixed with version 0.18.

Thanks! It is fixed now!


[RELEASE] cucim v21.06

❄ Code freeze for branch-21.06 and v21.06 release
What does this mean?
Only critical/hotfix level issues should be merged into branch-21.06 until release (merging of this PR).
What is the purpose of this PR?

Update documentation
Allow testing for the new release
Enable a means to merge branch-21.06 into main for the release

Hi @ajschmidt8
Could https://github.com/rapidsai/cucim/pull/48 be merged before this is merged?

The linked PR above has been merged along with another that fixed CI
Separately we seem to see the size check above failing. Not sure if that's expected or if there's something else we need to do there

rerun tests
(looks like it might have been spurious)


schema: swap closeTabsAfter and closeOtherTabs

The descriptions were flipped, so I unflipped them.

@msftbot merge this in 1 minute


Updated README

Instruction to activate environment did not work before.
source activate labx

returned the error "activate: No such file or directory"

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

Thanks, this is related with conda version. We will keep it as it is now.


it seems that native memory is unnormal

When i close the filechooser activity, the native memory still remains, is it normal?

Can u let me know the steps to check it?


Intuitive abstract support by stopping support of no CONFIGURATIONS

In this contribution, I revert #123 which introduced support of Models without CONFIGURATIONS.
Which in turns allow to come back on a very intuitive support of Abstract Model.
I keep the tests and documentation about Abstract Model support so we ensure we don't break this support later on again.


Cannot open vfx editor with /vfxedit

Basically the title.  Cannot open vfxedit using the /vfxedit command but can only open the editor FROM the plugin page (/xlplugins). no error shows up in /xllog

Checked with other friends, its the same issue as well so it isnt a isolated event

I accidentally broke it with the latest update. For now you can use /vfxedit vfx, /vfxedit pap until it’s fixed

I accidentally broke it with the latest update. For now you can use /vfxedit vfx, /vfxedit pap, etc until it’s fixed

fixed in latest update


Arduino ide 1.8.10 uploading the update from October 2019 does not work matrix keypad

When I go back to the previous version everything is ok.
What can I do to make the 4x4 key matrix enable?

must be #define UI_KEYPAD_ORIENTATION 0
I had #define UI_KEYPAD_ORIENTATION 180

Oops... The default was supposed to be zero... I don’t know how that made it into the version that got pushed to github; but I’ll fix it in the next update.


Add server request / response logging

Straw man proposal for issue #48
This code produces the following in log/server.log after server startup and a request:
2015-01-20 11:25:15,102 [<module>] INFO: Server started
2015-01-20 11:25:15,597 [_log] INFO:  * Running on http://<IP_ADDRESS>:8000/
2015-01-20 11:25:15,607 [_log] INFO:  * Restarting with reloader
2015-01-20 11:25:15,728 [<module>] INFO: Server started
2015-01-20 11:25:17,495 [_log] INFO: <IP_ADDRESS> - - [20/Jan/2015 11:25:17] "POST /variants/search HTTP/1.1" 200 -
2015-01-20 11:25:17,592 [_log] INFO: <IP_ADDRESS> - - [20/Jan/2015 11:25:17] "POST /variants/search HTTP/1.1" 200 -
2015-01-20 11:25:17,654 [_log] INFO: <IP_ADDRESS> - - [20/Jan/2015 11:25:17] "POST /variants/search HTTP/1.1" 200 -
2015-01-20 11:25:17,671 [_log] INFO: <IP_ADDRESS> - - [20/Jan/2015 11:25:17] "POST /variants/search HTTP/1.1" 200 -

It also doesn't send any messages to stdout or stderr anymore.  The POST messages are from the werkzeug logger.  (Still trying to figure out how to eliminate the werkzeug logger's extraneous formatting.)
Feedback appreciated.

Looks good, thanks @dcolligan. Here's some random thoughts on logging

I think we should log to stdout by default when we are running the development server, and log to a file when running under apace/nginx/whatever. It's not clear to me what the default for this should be, if anything.  What happens if we log to stdout when running under a real webserver? I think there are real advantages to logging directly to the webserver's file if we can (log rotation, etc).
I'm not a big fan of having a log directory in our source tree. When we deploy using pip, this won't be of any use and I think it's more useful to log to stdout for development purposes.
Should logging all be done in frontend.py? It would be nice if this was possible, as we'd avoid bringing in extra dependencies on the frontend from backend.py.

+1 on stdout/stderr by default for all the reasons @jeromekelleher described. Let others decide where they want it to go, rotation, etc.

@jeromekelleher various logging file handlers support log rotation, e.g. https://docs.python.org/2/library/logging.handlers.html#rotatingfilehandler I suggest if we're logging to a file we rotate by default.  Does this change your opinion on a log directory?  If not, where should the log(s) go?  (I'm less convinced than you are about unifying Apache/Flask logs; I'm not sure if people necessarily want GET/POST/GET log msgs intertwined with error msgs.)  Now that I think about it, we should probably have a separate galogging module that any component can import.
Since there seems to be a lot of opinions on logging, perhaps it would be good to also make the logger configurable in the same way that we are making Flask configurable.  Otherwise we're going to be stuck with something like a stdout/err in dev, unified logs and file rotation to a set place default.  Maybe that's fine, but it's something we should consider...

+1 on making logs configurable @dcolligan --- let's see what other people think about this.

1 for configurable, though I'd like to see a more detailed proposal.

TBH, I'm kind of uncertain about how to proceed on this PR.  The original issue stated by @kerrydc was "Access to data should be logged. Flask provides a logging framework, so that may be a good start. Once we have authentication we should log user IDs along with actions."  But the HTTP requests are already logged to stdout by werkzeug, at least in development.  And there's no auth feature yet.  So that seems to satisfy the requirements for development.  No one seems to have a good idea of what is required in production.  People also (rightly) seem to be against producing any log files.  Configurable logs seem to be a second step after having some custom logging infrastructure in place and knowing a bit about what kinds of configurations we want. So AFAICT, #48 is already satisfied by virtue of what the server already does.  Unless anyone has a specific suggestion of how to move forward on this, I would advocate closing this PR and the issue.

I'm with you here @dcolligan --- let's revisit this when we have auth.


database_setup: toDo - added info about the table and fieldname

Will this change work? I want to know at least which table-fieldname is wrong.

I did this because I got:
database_setup, todo toType handle: DateType

thanks 👍


remove last dependency to ReEnumerable

...so I can clean up common, the more we have to do on the CodeModel the next weeks/months, the less I wanna deal with non-standard types

🤖 AutoRest automatic publish job 🤖
> will publish once PR gets merged

🤖 AutoRest automatic feature coverage report 🤖
feature set version 2.3.13
❌ General: 99%
2 out of 522 features are not covered by tests
getComplexPolymorphismComplicated, putComplexPolymorphismComplicated
✔ Azure: 100%

🤖 AutoRest automatic feature coverage report 🤖
feature set version 2.3.13
❌ General: 99%
2 out of 522 features are not covered by tests
getComplexPolymorphismComplicated, putComplexPolymorphismComplicated
✔ Azure: 100%

🤖 AutoRest automatic feature coverage report 🤖
feature set version 2.3.13
❌ General: 99%
2 out of 522 features are not covered by tests
getComplexPolymorphismComplicated, putComplexPolymorphismComplicated
✔ Azure: 100%

🤖 AutoRest automatic feature coverage report 🤖
feature set version 2.3.13
❌ General: 99%
2 out of 522 features are not covered by tests
getComplexPolymorphismComplicated, putComplexPolymorphismComplicated
✔ Azure: 100%

🤖 AutoRest automatic feature coverage report 🤖
feature set version 2.3.13
❌ General: 99%
2 out of 522 features are not covered by tests
getComplexPolymorphismComplicated, putComplexPolymorphismComplicated
✔ Azure: 100%

🤖 AutoRest automatic feature coverage report 🤖
feature set version 2.3.13
❌ General: 99%
2 out of 522 features are not covered by tests
getComplexPolymorphismComplicated, putComplexPolymorphismComplicated
✔ Azure: 100%


Do not close window with JSON after error "wrong json format"

This bug is fixed in the latest version

@boneVidy Thank you!


document kube-vip version compatibility matrix

Users have reported confusion aligning versions of kube-vip with CPEM.
In the documentation, we should point out which versions of kube-vip/metallb are compatible (recommended!) with the versions of CPEM.  This could be included in the k8s version table.
https://github.com/equinix/cloud-provider-equinix-metal#version
Kube-vip may also need to take on this responsibility, documenting which versions of CPEM are compatible with the CPEM annotations that kube-vip is aware of.

Closed by #381


Quicktile

Project description
Keyboard-driven Window Tiling for your existing X11 window manager
Metadata

homepage URL:
quicktile-master.zip
https://github.com/ssokolow/quicktile
source URL: https://github.com/ssokolow/quicktile
license: gpl2+
platforms: linux

Duplicate of https://github.com/NixOS/nixpkgs/issues/164551


Allow access to Components/Registrar from DialOptions/ListenerOptions when creating a new transport

When creating a new transport, we are unable to register any new streams with the registrar, or fetch handles for any incoming streams. We are also unable to find the list of supported protocols, incoming and outgoing stream limits, and track metrics. Currently, transport implementations implement the MultiaddrConnection interface and use the upgrader for muxing, encryption, and handling streams. This is unnecessary when using transports which inherently contain encryption and stream multiplexing (WebRTC, QUIC). Allowing access to the components or some subset of it containing the registrar would simplify implementing these transports.

If your transport implements Initializable it'll get handed a Components instance after construction - that'll give you access to the Registrar and other libp2p components.
At that point you should be able to do stream/connection gating, encryption, multiplexing, etc in the same way the upgrader does for transports that don't have their own versions of these things.
Hopefully that helps?

Yes, thank you! We can close this issue.


"angular-whitespace" rule false-positive (when using string with pipe, ngx-translate)

My code is par example:
<button>
  {{ "button.label" | translate }}
</button>

This is complained by codelyzer: The pipe operator should be surrounded by one space on each side, i.e. " | ".
However, if I add a span, codelyzer is satisfied:
<button>
  <span>{{ "button.label" | translate }}</span>
</button>

The same problem was already reported in #415. It was fixed in release 3.2.2, but in 4.0.1, it happens again.

I have this issue even when using version 3.2.2

BTW, the error happens randomly with 3.2.2.
I made a change (removed an empty line) and the error did not happen.

Any news about this issue?
It still happens on the latest release (4.0.2)

Here are the changes from 4.0.2.

OK. I read the changelog for the 4.0.2.
My question was when would this issue (related to the check-pipe) be solved?

Let's drop the check-pipe as @wKoza suggested https://github.com/mgechev/codelyzer/issues/460.

I had an issue with angular-whitespace or one of the fixers that seemed to identify angular moustache templates in my typescript files (no templates) and
import {
  FormControl,
  FormGroup,
  FormBuilder,
  Validators,
  FormArray
} from "@angular/forms";

became
imp; }}t{{ { {  }}{  }} {  }} {  }}
  }}ormArray,
  FormBuilder,
  FormGroup,
  Validators;
} from; '@angular/forms';

I had ridiculously run the tslint --fix autofix while working out how to use tslint and ended up replacing even more }} 🤣.
I'm still trying to track things down.


WSL 2 networking doesn't work at all for me

Environment
Windows build number: Microsoft Windows [Version 10.0.19041.508]
Your Distribution version: Release:        20.04  (It's Ubuntu)
Whether the issue is on WSL 2 and/or WSL 1: WSL 2 - cat /proc/version gives this: MSYS_NT-10.0-19041 version 3.0.7-338.x86_64 (Alexx@WARLOCK) (gcc version 9.1.0 (GCC) ) 2019-07-11 10:58 UTC

Steps to reproduce

Not sure how to reproduce this, specifically, but it has happened on two of my machines in which I installed Hyper-V before enabling WSL, and I can't reproduce this on a new machine where WSL was enabled first.
When using WSL 2, networking doesn't work in any way.  Some of this may be due to my employer's firewall configuration, I don't know.  DNS lookups don't work, pinging the host WSL interface doesn't work, nothing.  No networking works at all.
Setting the WSL instance to V1, uninstalling Hyper-V, rebooting, then setting the WSL instance to V2 made networking work, but only once, and only until I rebooted next, and I can't reproduce that success, now.  I'm not sure what was going on there.  I'm back to no network connectivity at all in WSL 2 instances, no matter what I try.
I collected logs per Craig Loewen's instructions on twitter and they're attached below.

WSL logs:
logs.zip
Expected behavior

Networking should work.  I should be able to ping stuff and do DNS lookups and apt should be able to do its thing.
Actual behavior

Networking doesn't seem to be working at all in WSL 2 instances.
If there is further details I can collect, let me know, and I'll collect them.  Edit the bug subject/title as desired.

hi, i have the same problem, but on my machine i will access the outside via Wifi and not Ethernet.
-----> Wifi ---->      INETRNET   (ok)
WSL2  ---->  Pyhsical Laptop  |
-----> Eth0  ----->  INTERNET   (X)
theoretically between Wsl2 and Internet ( on the windows ) musst runed a NAT or PAT function.
can you please test it that have you outside access over Wifi or conversely?

#5831 appears to be related.  Same basic symptoms at least.

@mahdi7839 I switched to Wi-Fi and it doesn't work.  I notice now that I have two virtual Ethernet adapters with the same IP address, and three with the same network, and that may or may not be related.  It probably isn't good, whether it's the cause of this or not.
...

Ethernet adapter vEthernet (WSL):

   Connection-specific DNS Suffix  .  :

...

Ethernet adapter vEthernet (Ethernet):

   Connection-specific DNS Suffix  .  :

Ethernet adapter vEthernet (Ethernet 3):

   Connection-specific DNS Suffix  .  :

All of these are of course managed by Windows and I didn't set them up.
does this give you any clues as to what's going on?

https://gist.github.com/danvy/9486bf730371436131cb888ff4c2ceb6 does not fix the issue for me.
Disabling the non-WSL ethernet adapters which share IPs or networks does not resolve the issue for me.

if the cause of this particular issue has been found, can anyone let me know if there is a workaround?  anything short of a complete OS reinstall is acceptable to me.
I really want to use WSL 2...

I am no longer convinced that this problem is related to anything I posted in the issue originally.
There is a far more pedestrian problem in my cases, that I failed to take into consideration.  Company mandated firewall on non-domain networks, and all WSL 2 networks are non-domain networks.
Closing.

I am no longer convinced that this problem is related to anything I posted in the issue originally.
There is a far more pedestrian problem in my cases, that I failed to take into consideration.  Company mandated firewall on non-domain networks, and all WSL 2 networks are non-domain networks.
Closing.


Gene cards link for gene page

Could provide a gene cards link for further information, similar to linking to CPIC/FDA

Decided that information might be too complex; at least not include for study (instead rather #251)