Fix lerna publish not editing package.json files

Codecov Report

Merging #8 (31b4ada) into master (25fad56) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##            master        #8   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            3         3
  Lines           52        52
  Branches         7         7
=========================================
  Hits            52        52

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 25fad56...31b4ada. Read the comment docs.


Protocol Handler not working with flutter version 3.16.0 in Macos

the protocol listeners did'nt work even thought the cusotm uri permission is added in info.plist file

I'm seeing the same issue. onProtocolUrlReceived doesn't get called now.
It works fine in iOS.

Moving the listener to AppDelegate worked for me for now on 3.16.0
https://github.com/knoeone/soundsetr/blob/main/macos/Runner/AppDelegate.swift#L14
  override func applicationWillFinishLaunching(_ notification: Notification) {
    super.applicationWillFinishLaunching(notification)
      NSAppleEventManager.shared().setEventHandler(self, andSelector:#selector(handleURLEvent(_:with:)), forEventClass: AEEventClass(kInternetEventClass), andEventID: AEEventID(kAEGetURL))
  }

  @objc public func handleURLEvent(_ event: NSAppleEventDescriptor, with replyEvent: NSAppleEventDescriptor) {
    guard let urlString = event.paramDescriptor(forKeyword: AEKeyword(keyDirectObject))?.stringValue else { return }

      let window = self.mainFlutterWindow?.contentViewController as! MacOSWindowUtilsViewController
    let messenger = window.flutterViewController.engine.binaryMessenger
    let channel = FlutterMethodChannel(name: "protocol_handler", binaryMessenger: messenger)
    let args: NSDictionary = [
        "url": urlString,
    ]
    channel.invokeMethod("onProtocolUrlReceived", arguments: args)
  }

Thanks, @spacedevin! Also, if you are not using the macos_window_utils dependency, you will need to modify the handleURLEvent function to look like this:
@objc public func handleURLEvent(_ event: NSAppleEventDescriptor, with replyEvent: NSAppleEventDescriptor) {
  guard let urlString = event.paramDescriptor(forKeyword: AEKeyword(keyDirectObject))?.stringValue else { return }

  //These two lines are different
  guard let window = NSApplication.shared.windows.first else{ return }
  let controller = window.contentViewController as! FlutterViewController

  let messenger = controller.engine.binaryMessenger
  let channel = FlutterMethodChannel(name: "protocol_handler", binaryMessenger: messenger)
  let args: NSDictionary = [
      "url": urlString,
  ]
  channel.invokeMethod("onProtocolUrlReceived", arguments: args)
}


Revamp paginator

Our current paginator is a bit problematic, as it shows far too few results on desktop. We should do some competitive research and refactor it accordingly to accommodate our needs better.

After some competitive research, it seems that our paginator makes sense from a UX standpoint. Users generally need to know which page they are on and the number of pages. As far as interactions go, they need to have the option to go to the next and previous pages as well as the first and last (nice to have). Therefore, we will be making some smaller changes to the paginator to make it look more modern, while also adding some much needed microinteractions to its buttons.


Dynamically map platforms from ProblemList to PLATFORM

Currently, we have a hardcoded map  to map platform value in problem list to PLATFORM. For enhancement, I think we can map this dynamically. We can split the platform value in the problem list by -. The matching PLATFORM should contain the tokens with a few exceptions.
Related: https://github.com/adoptium/aqa-tests/issues/2698

Hi @llxia can you please elaborate a little more over this. What exactly do you mean by dynamical mapping? I am getting it as that the "platform_map" is a dictionary that stores string as keys and list as values. So you want to split the keys by - and then map the splitted keys to the list?

For example, if we get linux-ppc32, we can set PLATFORM to be ppc32_linux by split the value using - and reverse the first and the second token. We do not really need a hardcoded map.
There are a few mistakes in the map:
https://github.com/adoptium/aqa-tests/blob/master/disabledTestParser/generateDisabledTestListJson.py#L8
https://github.com/adoptium/aqa-tests/blob/master/disabledTestParser/generateDisabledTestListJson.py#L17
You can ignore them for now. They should be fixed in https://github.com/adoptium/aqa-tests/issues/2908

I think that one of the possible solution is to directly add the result we get by doing above mentioned operation over unresolved_platform_name in the revolved_platform_list instead of doing it by if-elif conditions here https://github.com/adoptium/aqa-tests/blob/master/disabledTestParser/generateDisabledTestListJson.py#L49. I am working toward this @llxia, please assign this issue to me.

Is the solution seems correct to you? Should I start working toward this @llxia ?

I'd like to work on this.
@llxia transforming the platform and eliminating the map should be fairly easy, but there's one tricky thing: currently, when the platform is a *-all (generic-all, linux-all, etc.), we use the map to expand it to a list of "concrete platforms" (aarch64_linux, x86-64_linux, etc.).

Should I copy the same platforms chosen when we run Grinder with PLATFORM=all and filter for linux, windows, mac, aix if needed? https://github.com/adoptium/aqa-tests/blob/253c7bf6fb188ca14c46bc13b2cc5426e13a12ea/buildenv/jenkins/openjdk_tests#L117-L123
If a platform in an exclude file is already in the right {ARCH}_{OS} format (instead of the {OS}-{ARCH} format), I don't think it's fair for the script to stop completely. Should we simply log a warning and keep going with the value? I could detect the {ARCH}_{OS} format by splitting on _ and asserting the len is 2.
I'd also like to refactor the code a little bit by introducing some data types, logging and taking stdin/stdout as default input/output streams (instead of "../openjdk/excludes" and getcwd()). Am I free to open a separate PR after the one for this issue, or should all the work be tracked with an issue?

@llxia just poking for the comment above https://github.com/adoptium/aqa-tests/issues/2910#issuecomment-1025730571 I'd like some feedback before opening any PR.

Thanks @gervaisj

yes, we can set PLATFORM=all and let Jenkins script handle it
Do you see any {ARCH}_{OS} format in the exclude list? If you do, can you list them? It may be a mistake.

Should we simply log a warning and keep going with the value?

yes, that is correct.

Yes, please feel free to open separate PR for refactoring. IMO, it is better to have separate PRs in this case.

Thanks @gervaisj

yes, we can set PLATFORM=all and let Jenkins script handle it
Do you see any {ARCH}_{OS} format in the exclude file? If you do, can you list them? There may be some mistakes.

Should we simply log a warning and keep going with the value?

yes, that is correct.

Yes, please feel free to open separate PR for refactoring. IMO, it is better to have separate PRs in this case.

@llxia

I was proposing, when we see linux-all in the exclude file, to set PLATFORM=linux-all in the output JSON (same for windows-all, macos-all, aix-all, sunos-all), and update Jenkins to handle these sorts of values, but we should always set PLATFORM=all regardless of the requested OS?
If I understood our format correctly, all the problems I saw were in "ProblemList_openjdk18.txt": linux_ppc64le should be linux-ppc64le, linux_s390x should be linux-s390x, win_64 should be windows-x64, and on line 403 ppc64le_linux is already formatted.
Ok, I'll log a warning anytime I see a _ and blindly assume the platform is correct (worst thing that can happen is Jenkins will say it doesn't recognize the platform)
In a separate PR, super!


Custom panic messages in snapbox

std::assert_eq supports providing a custom panic message in a third argument (optionally followed by further parameters for the message arguments). pretty_assertions and similar-asserts both provide assert_eq! macros that are compatible.
snapbox however currently appears to hard-code it's panic message:
https://github.com/assert-rs/trycmd/blob/d73c84cda48aebda8a4b3fd404745c8bff0ab649/crates/snapbox/src/assert.rs#L55-L61
I think custom panic messages are a nice way to provide more context to a test failure, so I think it would be great if snapbox supported them.

Yeah, I've recently gotten requests for this from others.  When creating snapbox, I overlooked this because

I tend to use filesystem snapshots which provides enough extra context that I wasn't needing it
A lot of times, I'm needing to use Assert, meaning the macros don't get as much attention

The main care about I had was then handled with track_caller.
If we move forward with this, I would expect we'd try to match the new assert format that is coming out soon, where relevant.
My main concern is what the API should look like for something like this.  Assert is a first class citizen in the API and should be able to be reused across calls (something which the current solution in #224 does not handle).  I also don't like creating a bunch of variations of functions for different use cases.  Maybe smaller builders off of Assert?

the new assert format that is coming out soon

Do you have a link for that?

https://github.com/rust-lang/rust/pull/111071


Unicode BIG Problem in plain body

I have some emails with unicode encoding. When I try to get plain body of each of them I get an string like this:
=D9=85=D8=AA=D9=86 =D9=81=D8=A7=D8=B1=D8=B3=DB=8C=20 =D8=A7=D8=B2 =D9=86=D9=88=D8=B9
I searched in web for a solution to decode/convert this string to unicode/UTF-8 but problem not yet solved.
It's not deference whether emails in HTML format or not. All non-English email (Arabic or Persian Emails) has this problem.
This problem just in Plain body and HTML body of emails haven't this problem and characters shows normally.
How can I convert this string to Unicode/UTF-8 characters?
Thanks for your help.

Are you saying it shows normally in plain or html bodys?

We do have our convertToUtf8 function. Try using that and let me know what it does please.

Show me your $imap->incomingMessage->message->info

And write a correct result, if possible.

Show me your $imap->incomingMessage->message->info

Everything is OK when I vard_ump($imap->incomingMessage);
I downloaded files again in github and after test now Everything is OK!!!

Hmmm.. It works now with our latest up to date code?

Please do composer update. Try it. And if everything is okay, we cover the topic.

@MSAyrese ping

Hmmm.. It works now with our latest up to date code?
Yes.


Fix for issue #92: duplicate entries in messages.txt have been removed

Fixes error in messages.txt

Coverage increased (+0.4%) to 91.297% when pulling 78cd75a194a115d079ff227e8104cf2474448bcd on edgarmueller:issue-92 into dfbd09b3fa1b542e49975a81bc9abcb1230bfd3a on eclipsesource:master.


OpenAI Failure when running AZD Up

Please provide us with the following information:

This issue is for a: (mark with an x)
- [ ] bug report -> please search issues before submitting
- [ ] feature request
- [ X] documentation issue or request
- [ ] regression (a behavior that used to work and stopped in a new release)

Minimal steps to reproduce

Ran all the commands
everything runs ok except it fails
Any log messages given by the failure

The subscription does not have QuotaId/Feature required by SKU 'S0' from kind 'OpenAI' or contains blocked QuotaId/Feature. (Code: SpecialFeatureOrQuotaIdRequired)
Expected/desired behavior

OS and Version?

Windows 7, 8 or 10. Linux (which distribution). macOS (Yosemite? El Capitan? Sierra?)

Running on a Mac - Ventura
azd version?

run azd version and copy paste here.

azd version 1.5.1 (commit 3856d1e98281683b8d112e222c0a7c7b3e148e96)
Versions

Mention any other details that might be useful

Thanks! We'll be in touch soon.

Does your account have OpenAI permissions? Have you been able to create OpenAI deployments from the Azure Portal in that region?

Hi Pam
No - I don't have permissions approved.
Not sure why they locked it down like this.
Regards
Iain
403 671 4665
On Thu, Jan 4, 2024 at 8:12 AM Pamela Fox @.***> wrote:

Does your account have OpenAI permissions? Have you been able to create
OpenAI deployments from the Azure Portal in that region?
—
Reply to this email directly, view it on GitHub
https://github.com/Azure-Samples/azure-search-openai-demo/issues/1104#issuecomment-1877256894,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAE7DKUWGOCQZ2K5YVGFSFTYM3BGZAVCNFSM6AAAAABBJFBCNGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNZXGI2TMOBZGQ
.
You are receiving this because you authored the thread.Message ID:
@.***>


Make cargo metadata output deterministic

Uses BTreeMap instead of HashMap for the cargo metadata command, ensuring the output is sorted.
The change did not cause a measurable performance impact for running cargo metadata on cargo itself.
Fixes #8477

Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @ehuss (or someone else) soon.
If any changes to this PR are deemed necessary, please add them as extra commits. This ensures that the reviewer can see what has changed since they last reviewed the code. Due to the way GitHub handles out-of-date commits, this should also make it reasonably obvious what issues have or haven't been addressed. Large or tricky changes may require several passes of review and changes.
Please see the contribution instructions for more information.

Can you add a test that called cargo metadata twice and makes sure the output is the same?

I modified the test framework to enforce order in Json arrays. I had to re-arrange the expected output in several tests such that it was sorted.

@bors: r+
Looks good to me, thanks for this!

:pushpin: Commit 58869e5ce6e72c27c3534d404eb9e1ba9f76c5e7 has been approved by alexcrichton

:hourglass: Testing commit 58869e5ce6e72c27c3534d404eb9e1ba9f76c5e7 with merge e37b35cc5386042319575788b662bf9850c38c47...

:sunny: Test successful - checks-actions
Approved by: alexcrichton
Pushing e37b35cc5386042319575788b662bf9850c38c47 to master...


Support whitelisting passwords and domains

We often use weak passwords for internal/non critical test apps. It will be great if I can whitelist specific passwords or domains that the plugin won't alert me every time.

+1 on this - I would love to roll this out enterprise-wide but that's a non-starter without ability to whitelist domains. The extension would just pop all the time for our QA team's test accounts and similar things which are likely to have common / easy passwords, be design.

Hi,
It would be indeed great to whitelist specific passwords ! Was curious to know if it would be like  having an other text field that would list of all the passwords (Hardcoded) or would you want the list to be populated dynamically. Thanks


Adding tmp to writable path

Signed-off-by: vipsharm<EMAIL_ADDRESS>

Opened https://github.com/kairos-io/kairos/pull/136 which supersedes this PR

https://github.com/kairos-io/kairos/pull/136 was merged, closing


Unable to install qdrant on K8s

When you try to install qdrant on orbstack K8s cluster using the helm chart as instructed in https://qdrant.tech/documentation/guides/installation/#kubernetes. An error appears: " Error: template: qdrant/templates/tests/test-db-interaction.yaml:57:48: executing "qdrant/templates/tests/test-db-interaction.yaml" at <$root.Values.config.service.enable_tls>: nil pointer evaluating interface {}.enable_tls".
I checked the https://github.com/qdrant/qdrant-helm/blob/main/charts/qdrant/values.yaml and noticed that TLS is enabled.
Current Behavior

Steps to Reproduce

Create a K8s cluster using orbstack
helm repo add qdrant https://qdrant.to/helm
helm install qdrant-release qdrant/qdrant

Expected Behavior
qdrant should be installed on the k8s cluster.
Possible Solution

Context (Environment)

Detailed Description

Possible Implementation

I can't reproduce this issue. I'm not familiar with Orbstack but just tested it locally with Kind and K3d. It should not depend on the Kubernetes distribution, since the template rendering is done by the Helm CLI.
Which Helm version are you using (helm version)?
Which Kubernetes version are you using (kubectl version)?
Which version of the Helm chart are you installing (helm search repo qdrant)?
Are you setting any additional values or value files during the installation?

I can't reproduce this issue. I'm not familiar with Orbstack but just tested it locally with Kind and K3d. It should not depend on the Kubernetes distribution, since the template rendering is done by the Helm CLI.
Which Helm version are you using (helm version)? Which Kubernetes version are you using (kubectl version)? Which version of the Helm chart are you installing (helm search repo qdrant)? Are you setting any additional values or value files during the installation?

rkodhandapani@blr-mpqob ~ % orb start k8s
rkodhandapani@blr-mpqob ~ % kubectl get nodes
NAME       STATUS   ROLES                  AGE     VERSION
orbstack   Ready    control-plane,master   2d19h   v1.27.4+orb1
rkodhandapani@blr-mpqob ~ % kubectl version
Client Version: version.Info{Major:"1", Minor:"20", GitVersion:"v1.20.2", GitCommit:"faecb196815e248d3ecfb03c680a4507229c2a56", GitTreeState:"clean", BuildDate:"2021-01-14T05:15:04Z", GoVersion:"go1.15.6", Compiler:"gc", Platform:"darwin/amd64"}
Server Version: version.Info{Major:"1", Minor:"27", GitVersion:"v1.27.4+orb1", GitCommit:"40f54c2c6d383b1de832c2bc95f0966e047f7e7b", GitTreeState:"dirty", BuildDate:"2023-08-29T06:26:34Z", GoVersion:"go1.20.4", Compiler:"gc", Platform:"linux/amd64"}
rkodhandapani@blr-mpqob ~ % helm version
WARNING: Kubernetes configuration file is group-readable. This is insecure. Location: /Users/rkodhandapani/.kube/config
WARNING: Kubernetes configuration file is world-readable. This is insecure. Location: /Users/rkodhandapani/.kube/config
version.BuildInfo{Version:"v3.4.1", GitCommit:"c4e74854886b2efe3321e185578e6db9be0a6e29", GitTreeState:"dirty", GoVersion:"go1.15.4"}
rkodhandapani@blr-mpqob ~ % helm repo add qdrant https://qdrant.to/helm
WARNING: Kubernetes configuration file is group-readable. This is insecure. Location: /Users/rkodhandapani/.kube/config
WARNING: Kubernetes configuration file is world-readable. This is insecure. Location: /Users/rkodhandapani/.kube/config
"qdrant" already exists with the same configuration, skipping
rkodhandapani@blr-mpqob ~ % helm install qdrant-release qdrant/qdrant
WARNING: Kubernetes configuration file is group-readable. This is insecure. Location: /Users/rkodhandapani/.kube/config
WARNING: Kubernetes configuration file is world-readable. This is insecure. Location: /Users/rkodhandapani/.kube/config
Error: template: qdrant/templates/tests/test-db-interaction.yaml:57:48: executing "qdrant/templates/tests/test-db-interaction.yaml" at <$root.Values.config.service.enable_tls>: nil pointer evaluating interface {}.enable_tls
rkodhandapani@blr-mpqob ~ %
rkodhandapani@blr-mpqob ~ % helm search repo qdrant
WARNING: Kubernetes configuration file is group-readable. This is insecure. Location: /Users/rkodhandapani/.kube/config
WARNING: Kubernetes configuration file is world-readable. This is insecure. Location: /Users/rkodhandapani/.kube/config
NAME         	CHART VERSION	APP VERSION	DESCRIPTION
qdrant/qdrant	0.6.1        	v1.6.1     	Qdrant - Vector Database for the next generatio...
rkodhandapani@blr-mpqob ~ %

The same error on Minikube too:
NAME       STATUS   ROLES           AGE   VERSION
minikube   Ready    control-plane   16s   v1.27.4
rkodhandapani@blr-mpqob ~ % helm repo add qdrant https://qdrant.to/helm
WARNING: Kubernetes configuration file is group-readable. This is insecure. Location: /Users/rkodhandapani/.kube/config
WARNING: Kubernetes configuration file is world-readable. This is insecure. Location: /Users/rkodhandapani/.kube/config
"qdrant" already exists with the same configuration, skipping
rkodhandapani@blr-mpqob ~ % helm install qdrant-release qdrant/qdrant
WARNING: Kubernetes configuration file is group-readable. This is insecure. Location: /Users/rkodhandapani/.kube/config
WARNING: Kubernetes configuration file is world-readable. This is insecure. Location: /Users/rkodhandapani/.kube/config
Error: template: qdrant/templates/tests/test-db-interaction.yaml:57:48: executing "qdrant/templates/tests/test-db-interaction.yaml" at <$root.Values.config.service.enable_tls>: nil pointer evaluating interface {}.enable_tls
rkodhandapani@blr-mpqob ~ %

I tested the same on my machine:
❯ kubectl get nodes
NAME       STATUS   ROLES                  AGE   VERSION
orbstack   Ready    control-plane,master   27s   v1.27.4+orb1

❯ kubectl version
Client Version: v1.28.2
Kustomize Version: v5.0.4-0.20230601165947-6ce0bf390ce3
Server Version: v1.27.4+orb1

❯ helm version
version.BuildInfo{Version:"v3.13.1", GitCommit:"3547a4b5bf5edb5478ce352e18858d8a552a4110", GitTreeState:"clean", GoVersion:"go1.21.3"}

❯ helm repo add qdrant https://qdrant.to/helm
"qdrant" has been added to your repositories

❯ helm search repo qdrant
NAME         	CHART VERSION	APP VERSION	DESCRIPTION
qdrant/qdrant	0.6.1        	v1.6.1     	Qdrant - Vector Database for the next generatio...

❯ helm install qdrant-release qdrant/qdrant
NAME: qdrant-release
LAST DEPLOYED: Thu Oct 19 11:00:18 2023
NAMESPACE: default
STATUS: deployed
REVISION: 1
NOTES:
Qdrant v1.6.1 has been deployed successfully.

The full Qdrant documentation is available at https://qdrant.tech/documentation/.

To forward Qdrant's ports execute one of the following commands:
  export POD_NAME=$(kubectl get pods --namespace default -l "app.kubernetes.io/name=qdrant,app.kubernetes.io/instance=qdrant-release" -o jsonpath="{.items[0].metadata.name}")

If you want to use Qdrant via http execute the following commands
  kubectl --namespace default port-forward $POD_NAME 6333:6333

If you want to use Qdrant via grpc execute the following commands
  kubectl --namespace default port-forward $POD_NAME 6334:6334

If you want to use Qdrant via p2p execute the following commands
  kubectl --namespace default port-forward $POD_NAME 6335:6335

@Rajakavitha1 The one big difference that I see and could explain this: Your Helm CLI version is very old (nearly 3 years). Maybe there is a bug in the Helm CLI that triggers the if check to not work properly. Could you try to update your Helm CLI?


chore(docs): fix markdown reported by clippy

Summary
While running cargo clippy, I get a few warnings about Markdown formatting in our doc comments (see the dropdown for warning text). This should both clean my cargo output and guarantee proper formatting on docs.rs.

excerpt of `cargo clippy` output
warning: doc list item missing indentation
  --> packages/fuels-code-gen/src/program_bindings/abigen.rs:34:9
   |
34 |     /// for, and of what nature (Contract, Script or Predicate).
   |         ^
   |
   = help: if this is supposed to be its own paragraph, add a blank line
   = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#doc_lazy_continuation
   = note: `#[warn(clippy::doc_lazy_continuation)]` on by default
help: indent this line
   |
34 |     ///   for, and of what nature (Contract, Script or Predicate).
   |         ++

warning: doc list item missing indentation
   --> packages/fuels-code-gen/src/program_bindings/abigen.rs:154:9
    |
154 |     /// generated.
    |         ^
    |
    = help: if this is supposed to be its own paragraph, add a blank line
    = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#doc_lazy_continuation
help: indent this line
    |
154 |     ///   generated.
    |         ++

warning: `fuels-code-gen` (lib) generated 2 warnings
warning: doc list item missing indentation
   --> packages/fuels-programs/src/calls/call_handler.rs:297:9
    |
297 |     /// Note that this is a builder method, i.e. use it as a chain:
    |         ^
    |
    = help: if this is supposed to be its own paragraph, add a blank line
    = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#doc_lazy_continuation
    = note: `#[warn(clippy::doc_lazy_continuation)]` on by default
help: indent this line
    |
297 |     ///   Note that this is a builder method, i.e. use it as a chain:
    |         ++

warning: `fuels-programs` (lib) generated 1 warning

Checklist

[x] All changes are covered by tests (or not applicable)
[x] All changes are documented (or not applicable)
[x] I reviewed the entire PR myself (preferably, on GH UI)
[x] I described all Breaking Changes (or there's none)

@calldelegation Sure! Should I/we avoid scoping (parenthesised parts) altogether in the future?

@Br1ght0ne yea the titles should be chore, feat, or fix | chore!, feat!, or fix!
https://github.com/FuelLabs/fuels-rs/blob/master/scripts/change-log/src/get_full_changelog.rs#L159-#L175

@Br1ght0ne, can you please sync the branch?


$location.state()

when I called $location.state() like this:
$location.state
  cellPhone: $scope.cellPhone

the browser throwed an error:
Error: [$location:nostate] History API state support is available only in HTML5 mode and only in browsers supporting HTML5 History API

my browser is Safari (Version 8.0.7)
the Plunker address: $location.state() error

Hey @unique-vv
Do you already tried use $locationProvider.html5Mode(true); ?
I used it here and now, it's working.
Fell free to look this -> https://docs.angularjs.org/error/$location/nostate

@rmdias thanks very much for teaching me!


feat: add commandCall method to AwsStub

fixes: #240

I can't take credit https://github.com/sinonjs/sinon/blob/372593f5450c5d3d54ff23f09a90e33dbc706b59/lib/sinon/proxy.js#L47

Released in v4.1.0

Thanks!


Updating property name of changelog schema

What and why?
The collection-exercise deployment into the performance environment is suffering from a Liquibase error during application startup where the scripts appear to be getting reapplied causing constraint violations.
The issue is that Liquibase doesn't have the correctly named property and is looking in the default (public) schema.
This updates the Liquibase property name that specifies in which schema the delta changelog tables live.
How to test?
Deploy into a new and existing development environment (i.e. Docker Postgres), and deploy into a newly build and existing performance environment (i.e. Managed Cloud SQL). In all scenarios the collection-exercise should deploy and startup and data should be provisioned (new) or persistent (existing).
Trello
https://trello.com/c/RpAdmz8R/1908-bug-performance-environment-infrastructure-track-time-2d

/deploy performance


fix: use sentence casing

Description
Updated text to use sentence casing.

wiki: Title case
apa: Sentence case

Type of change

enhancement

How Has This Been Tested?
Manually.
Before:

After:

Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes

Test coverage results :test_tube:
:green_circle: Total coverage has increased
// Code coverage diff between base branch:release and head branch: fix-casing

Status
File
% Stmts
% Branch
% Funcs
% Lines

:green_circle:
total
55.77 (0)
37.13 (0.01)
35.82 (0)
56.13 (0.01)

:red_circle:
app/client/src/ce/constants/messages.ts
76.98 (-0.02)
100 (0)
31.75 (-0.05)
81.94 (0.02)

:green_circle:
app/client/src/utils/WorkerUtil.ts
89.76 (0.78)
72.55 (1.96)
100 (0)
93.33 (0.95)

:green_circle:
app/client/src/utils/autocomplete/TernServer.ts
52.94 (0.23)
41.67 (0.84)
36.21 (0)
56.99 (0.25)

@IAmAnubhavSaini Thanks for this change. As part of this PR can we also correct the casing for https://github.com/appsmithorg/appsmith/blob/48446e67143af028d943b692834afc37111dafeb/app/client/src/ce/constants/messages.ts#L613 ? It's related to the Git feature and looks weird when the user first interacts with the Git feature.

/ok-to-test sha=72a9ac1ad00c9d5d969ac08485246a3e26842700


Ergonomics for missing fields

Values can be missing during a preview. We need a way to indicate a missing field to the...

provider, so that we don't make decisions based on a missing field.
engine, so it displays unknown data in diffs correctly.

This was accomplished via the ExplicitDependencies interface for custom resources. Merged in https://github.com/pulumi/pulumi-go-provider/pull/33.


Adds steps to run docker without sudo in README

Overview
Adds steps to run docker without sudo in README.md.
Closes #2
Demo
n/a
Notes
n/a
Testing Instructions
n/a

lgtm


Vof peeling

Description of the problem

Peeling/wetting was not implemented in VOF solver

Description of the solution

create BC section for VOF
implement peeling/wetting basic methods

How Has This Been Tested?
No test for now, will be added when the solver is more mature. I tested it locally on the "glissomètre" (dough on slopped plane) that we used during our experimental campaign.
Documentation
For now I did not put it in the documentation, as it is really immature so I do not really want anyone to use it. Will be in the next PR with improved peeling/wetting!
Future changes

none BC could be generalized
improving peeling/wetting : this is a basic implementation of the methods needed
give a physical meaning to the pressure threshold (link it to the friction coefficient?)
I really want to clarify the VOF solver: VOF or CFD parameters have different suffix throughout the code and I want to make it uniform. This will be my next PR!

Comments
I thought I had to rebase but git says it is able to automatically merge. Do not hesitate to tell me if you think a rebase is still necessary!

@jeannejoachim  Is the PR ready for the final review?

@jeannejoachim Is the PR ready for the final review?

No not at all! I rebased on master and now I should deal with the new physical property manager, I still have some work to do. Thank you for asking, I will notify you when this is the case :)

@shahabgol and @blaisb it is ready to be reviewed again! Thank you for your feedback, it improved this PR a lot.
I also merged (twice) with master to resolve conflicts and use the new property_manager. Please tell me what you think about it!
The only thing missing from your suggestions is the test. I have it (water droplet falling on a plane), but it would require a more mature peeling/wetting mechanism for the results to be convincing. I could still add the test and its output (number of cells wet/peeled) but it would still need to be rewritten in future versions. I would rather merge what is already here and then work on a version 2 than continue on the same PR, but do not hesitate to tell me if you think otherwise!


Support new compiler flags in Visual Studio

It would be great to get checkboxes for the new TypeScript 1.4 compiler flags in Visual Studio 2013.  In particular, noEmitOnError (actually to disable it, since this seems to default to on now in VS, but seemingly not on the command line).  suppressImplicitAnyIndexErrors and preserveConstEnums would also be great to see.  Many thanks!

There is no UI support (project property pages) for all switch, we only have the ones most commonly used. however, you can still control them from the project file by adding an MSBuild property. so for noEmitOnError, just add:
<PropertyGroup>
    <TypeScriptNoEmitOnError>false</TypeScriptNoEmitOnError>
</PropertyGroup>

Just as a note, the reason why noEmitOnError is set by default is to allow incremental build to work correctly. MSBuild incremental build relies on checking the timestamps of input (.ts) files against those of the output (.js) files. The typescript compiler does generate outputs in the face of semantic errors (e.g. number not assignable to string). this means that if you have an error, build first time, build fails, then build a second time with no changes to your project, this time the build succeeds, cause it finds all outputs up-to-date. This can be really confusing in big projects where you only see all errors on rebuild.
And for future references, here is the full list of MSBuild property names for controling diffrent flags.
<TypeScriptRemoveComments>
<TypeScriptNoImplicitAny>
<TypeScriptGeneratesDeclarations>
<TypeScriptModuleKind>
<TypeScriptOutFile>
<TypeScriptOutDir>
<TypeScriptSourceMap>
<TypeScriptTarget>
<TypeScriptNoResolve>
<TypeScriptAdditionalFlags>
<TypeScriptMapRoot>
<TypeScriptSourceRoot>
<TypeScriptCodePage>
<TypeScriptCharset>
<TypeScriptEmitBOM>
<TypeScriptNoLib>
<TypeScriptPreserveConstEnums>
<TypeScriptSuppressImplicitAnyIndexErrors>

Thanks.  This documentation is very helpful.  I may submit a PR to web essentials to add a separate UI.  For future versions of the VS extension, it would be so great to have an option to treat type errors as warnings.  This would allow "first time converters" to get the old default behavior which in my opinion was better while you were just getting started.  Technically 1.4 is a breaking change for people in that phase of TypeScript implementation.  Thanks so much!  I think 1 4 is awesome.

Looks like Mads isn't interested to add this to Web Essentials so I guess manually editing the project is the only way.  Thanks Mohamed.

I really don't think we should ask people to manually hack up the project file. If it's important enough to expose a compiler option for then we should provide UI for that setting. If we don't want to make the project properties have 30 different checkboxes then we could always provide a textbox for writing out command line args.

If it's important enough to expose a compiler option for then we should provide UI for that setting.

Awesome.  +1000000 if this could mean type errors as Visual Studio warnings.

Not all compiler options have the same usage numbers, some are more common than others. for instance --module vs. --emitBOM.
Adding a text box for a command line gets a bit tricky with Language Service and compiler having different versions, MSBuild properties are nicer in this front, as they are honored only by the systems that understand them and ignored by others.
@nycdotnet this is a different feature, the compiler currently only emits errors, and there is no commandline option for changing their category to 'warning'. I would file another issue for this request.

@mhegazy Understood.  We've had good luck on the grunt-ts team identifying the difference (emit-preventing vs non-emit preventing), but agreed it's a separate issue.  I will submit and try to find the old codeplex request as well.  Many thanks.

@nycdotnet, on a side note, the compiler now returns a code that tells you if the errors have prohibited emit or not. See EmitReturnStatus]

editing the project file is no use for typescript files in a virtual project

@gulbanana we will be adding tsconfig support to VS in the next release. So that would be your way to configure your virtual projects.

We need to fix this. Asking people to edit project files is a bad user experience, especially for core flags like this one.

editing the project file is no use for typescript files in a virtual project

perhaps virtual projects can be tsconfig.json based

cool, sounds good- when you say the next version, do you mean VS2015?

By next release I mean TypeScript 1.5. we do not have a set scheduled for this release yet.


feat: update OpenFeature NodeJS test harness to use new getOpenFeatureProvider() method

feat: update OpenFeature NodeJS test harness to use new getOpenFeatureProvider() method
chore: update to nodejs sdk 1.21.0

Current dependencies on/for this PR:

main

PR #364   👈

This stack of pull requests is managed by Graphite.


How to use with huge single state

In most of my projects I'm using single masterReducer and masterStore, making use of multiple combineReducers. My substates have several levels of depth and usually contain quite a lot of data (whole JSONs from the backend), and I'd like to use only specific substates for each test. Can I do that with redux-test-recorder? stateKey seems to be working only one level deep.
Sample reducer:
const masterReducer = combineReducers({
  auth,
  api: combineReducers({
    login,
    account,
    filterModel,
    users
  }),
  views: combineReducers({
    progressBar,
    stringDetails,
    stringDetailsHistory,
    review,
    navbar,
    replace
  }),
  uiLocale
})

I've prepared a branch with a fix (splitting stateKey on ., so stateKey: 'api.login' would work in my case), but don't know if it's intended use of this feature. Should I make a PR?

@pawelchojnacki I think that's a good solution, I would accept a pr for that!


state machines' guard doesn't react properly when there are minus numbers

Consider the following example which is a valid one.
class A{
  status{
    on{
      turnOff (Integer pn) [pn >-1] -> off;
    }
    off{
      turnOn -> on;
    }
  }
}

it shows the following messages. The code is correct. The issue is because of -1.
Warning on line 4 : State machine syntax could not be processed. It has been considered as Extra Code. More information (1006)
Warning on line 7 : State 'off' from StateMachine 'status' is non-reachable.. More information (67)

This has


Update tapir-akka-http-server, ... to 0.17.12

Updates

com.softwaremill.sttp.tapir:tapir-akka-http-server
com.softwaremill.sttp.tapir:tapir-enumeratum
com.softwaremill.sttp.tapir:tapir-json-circe
com.softwaremill.sttp.tapir:tapir-openapi-circe-yaml
com.softwaremill.sttp.tapir:tapir-openapi-docs
com.softwaremill.sttp.tapir:tapir-swagger-ui-akka-http

from 0.17.0-M8 to 0.17.12.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "com.softwaremill.sttp.tapir" } ]

labels: library-update, semver-pre-release

Superseded by #88.


Question: RACK_TIMEOUT_TERM_ON_TIMEOUT on one cluster

Sorry if this is the wrong place to post a question, if so feel free to direct me to a better place to get information about rack-timeout configuration settings.
Anyways, I read the documentation on the RACK_TIMEOUT_TERM_ON_TIMEOUT setting since I'm running puma on Heroku. The number of processes run by puma for our application is being set using the WEB_CONCURRENCY ENV variable, since puma defaults to using this ENV variable to set workers if it is set. Since we have it set to 1, I believe puma is running in "cluster mode" (with just one cluster), where I believe if it is set to 0, the server will be running in "single mode". My question is, is it okay to use RACK_TIMEOUT_TERM_ON_TIMEOUT in "cluster mode" with one cluster?

I believe it's objectively "safe," but your app will not be able to serve requests until it has booted a new cluster to replace the [only] one that was SIGTERM'd. I don't know if Puma will hold new incoming requests or drop them on the floor. It's certainly better if you can set it to at least 2.
This question would be better addressed by the Puma documentation and/or team, since the behavior is specific to Puma.


Comments in nginx config talks names Apache

Minor issue as can be seen in the comments:
https://github.com/hyn/multi-tenant/blob/0e7e51801c038c5a969b0a6ce8568c6924b5965f/assets/configs/webserver.php#L125-L187
Where Apache is named, it should be nginx.

Feel free to create a PR for this, @pedzed!

@luceos Did you also change the other ones? There is more than one occurrence.

@Thijmen patched that up, I incidentally totally missed that 😊


Open orders in resolved market modal

We should add description that this will require multiple MM signings ( i believe v1 only need to confirm)

creating another tix to describe how all modals that might need multiple transactions when user clicks All ... button


module: komodo.control

komodo/control.py:

includes all control command functions
with attached docstrings to every function

to be merged to 'dev'.

Seems like you've delete the deleted the files in this PR.


Same groups in ReactSelect for relationship fields

Link to reproduction
No response
Describe the Bug
ReactSelect is used for relationship fields. It will be populated with OptionGroups.
Unfortunately there are multiple groups with the same label.
For example I have a relation to a pages collection:

There will be a group with a "pages" header and a single document (the selected one).
There will be another group also with a "pages" header and 10 documents.
I think after scrolling, the next lazy loaded pages (10 again) will be pushed to a new "pages" group.

To Reproduce

Create a collection with a relationship field (relation to a single or multiple collections).
Edit the collection and open the relation dropdown.

Payload Version
2.11.2
Adapters and Plugins
db-mongodb 1.4.2

I have the same issue. An additional category title is added when you add a new item to the select box.

When the select dropdown is filled initially, there is only one category title afterwards.


RDPWrap forgets some settings after autoupdate

RDPWrap loses the "GUI Authentication Only" setting after running the autoupdate script.  The problem this creates is that the user can't login after an update, until an administrator goes in to click on the radio but for this option.

The autoupdate script is not distributed as a part of this project or in this repository. Ask for support in RDP Wrapper Telegram chat.


Better copy component button

Make it so when clicking to copy a component, you copy the most pure version of the showed component.
It includes removing the current Label and id, which is only meant to be used for preview and intern purposes, and are unnecessary in the final code.
Also saw a PR talking about giving the chance to visualize such code before copying it directly from the button, and I think that would be a great feature too

Working on that!


Near/Far Pointer Mismatch

in VirtualShield::sendFlashStringOnSerial() (around line 788) the for loop checks for a far pointer and the next line does a pgm_read_byte_near.

by-design... this was the only way this worked. the pgm_read_byte_far didn't work at all here. bug in arduino code? not sure.

the signature for strlen_PF() is size_t  strlen_PF (uint_farptr_t src), which is probably where the requirement for the uint_farptr_t is coming from.


[douma-app] Needs to boot without config

Douma-app can now boot without config and persist the configuration.


[5.0] Add single minute granularity to console scheduling

I'd venture a guess that some folks would like to run tasks a bit faster than every 5 minutes.

This is redundant I suppose, unless all you want is API verbosity. Every minute is the default behaviour:
	protected $expression = '* * * * * *';

:+1: This would be nice to have.
PR should probably be squashed to one commit?

This is already possible. You just don't call any method and that defaults to every minute.
$schedule->call(function() { echo 'every minute'; });

Wouldn't the intent be more clear if there was a everyMinute() method even if it's more verbose? From reading the docs it doesn't seem obvious that leaving off the method call defaults to every minute.


Fix keys validation option not being respected

Ran into an issue after upgrading to v3 where they keys validation option would not be respected anymore.
This pull request adds a check to the final doValidation() filter, where any errors not matching the provided keysToValidate argument are discarded.
Reference #477

Thanks! Fixed a different way in https://github.com/longshotlabs/simpl-schema/commit/ded2a356537db3d14e20aca6decfccfe44fcafdf


Search functionality crashes computer every time

Every time I use the search functionality, it crashes my Mac. It's been months since this started happening. It didn't use to happen.
I have disabled all extensions. I have uninstall and reinstall. It keeps happening.
Steps to reproduce:

Open VS Code.
It will load my workspace.
Search a couple of times for different strings, it will crash almost immediately, forcing me to button-shutdown my mac because it's completely frozen.

OS: Mojave 10.14.6 (18G2022)
Thanks,
Julio.

CPUs
Intel(R) Core(TM) i7-7820HQ CPU @ 2.90GHz (8 x 2900)

GPU Status
2d_canvas: enabledflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmetal: disabled_offmultiple_raster_threads: enabled_onoop_rasterization: disabled_offprotected_video_decode: unavailable_offrasterization: enabledskia_renderer: disabled_offsurface_control: disabled_offsurface_synchronization: enabled_onvideo_decode: enabledviz_display_compositor: enabled_onviz_hit_test_surface_layer: disabled_offwebgl: enabledwebgl2: enabled

Load (avg)
8, 2, 1

Memory (System)
16.00GB (8.93GB free)

Process Argv

Screen Reader
no

VM
0%

Extensions: none
Info about VS Code:
Version: 1.41.1
Commit: 26076a4de974ead31f97692a0d32f90d735645c0
Date: 2019-12-18T14:57:51.166Z
Electron: 6.1.5
Chrome: 76.0.3809.146
Node.js: 12.4.0
V8: 7.6.303.31-electron.0
OS: Darwin x64 18.7.0

Are you sure it's been months, or did it start more recently? I ask because we have gotten similar issues after the past release.

I have similar issues when searching in the large workspace folder.
Kubuntu 18.04 / VS Code Stable 1.41.1
OS is frozen due to memory consumption. Search eats all my 16 Gb in about 2 minutes.
There is two running processes that consume more memory over time:
user      5501  715 56.8 9310240 9281832 ?     Sl   11:05  15:15 /usr/share/code/resources/app/node_modules.asar.unpacked/vscode-ripgrep/bin/rg --hidden --ignore-case --max-filesize<PHONE_NUMBER>4 --no-ignore --follow --crlf --fixed-strings --no-config --no-ignore-global --json -- uv5647 .
user      6263  148 14.2 2839108 2322096 ?     Rl   11:07   1:35 /usr/share/code/code /usr/share/code/resources/app/out/bootstrap-fork --type=watcherService

Search was done without any option (Match case etc).
Killing rg process prevents OS from instant freeze and stops the search engine, though watcherService continues to eat memory for some time.
Also watcherService sometimes frees part of its memory during search (I saw a drop from 2.4 Gb to 1.8), but then continues to consume more memory.

@roblourens it's been happening at least since November 2019. I keep my VS Code updated.

I have tried upgrading to the latest 1.4x a few times to see if it has been patched and it still hasn't.  I have also noticed that it only seems to crash when a previous search is not yet finished.  For example, if I turn off the searchOnType and I type something like "searfh" and hit Enter but then realize I had a typo and change it.  If I hit Enter on the new search before the previous search finishes, then my Mac will lock up.  As long as I let the previous search finish before performing a new search then I am fine.  Sometimes I correct my typo and re-run the search without thinking and I lose all my work so this issue is still a pain.

This is a disruptive issue with 100% repro rate. Occurs even after disabling multiple search features like FollowSymlinks, Global Find Clipboard, Maintain file search cache, Include History, Search On Type, Seed with nearest word..etc. Please fix this ASAP.
When I'm searching for something, I'm always scared that this might crash the whole OS if I touch something. I tried it on .45 as well as .39 versions, the issue persists.
It is very easy to reproduce, just open any directory which has many files and directories in it, try searching for something and while the search is in progress, remove a char from the search string and hit enter, crash, macOS restart. This is just one of the flows, similar issues were seen when doing search and modifying something in the search window be it file type, directories or anything.

If someone with this problem can reproduce this issue outside VS Code with an rg command on their workspace, then I'd be happy to take a look. Just let me know which version of ripgrep you're using.
N.B. I am not a VS Code user, so I can't really help with any aspect there. But if you can isolate it to a problem with a ripgrep command, then I can try to help. (I am the maintainer of ripgrep.)

The same issue is 100% reproducible even after search.searchOnType. The issue moved away from search string type action to files to include /exclude type.
Step to reproduce search any expression with include file filter. After the search just try to change the filter file values. The VS code will freezes. Its a pain and productivity loss during this covid19 time.

I'm running into this issue on Mac OS 10.14.6 with version VS Code version 1.46.0. It literally started today. I've never seen the issue before. I've had to hard reboot my system three times today to regain control of my system. It feels like all processors are at 100% CPU and the fans start running on high.

If someone with this problem can reproduce this issue outside VS Code with an rg command on their workspace, then I'd be happy to take a look. Just let me know which version of ripgrep you're using.

@BurntSushi, I have tried to reproduce this issue with running rg command but no matter how many instance I run at the same time, I cannot get it to cause a crash like VSC.
ripgrep 11.0.1 (rev 973de50c9e)
-SIMD -AVX (compiled)
+SIMD +AVX (runtime)

When I run the search in VSC, I see the following process:
"/Applications/Visual Studio Code.app/Contents/Resources/app/node_modules.asar.unpacked/vscode-ripgrep/bin/rg" --hidden --ignore-case -g !**/.svn -g !**/.hg -g !**/CVS -g !**/.DS_Store -g !**/bower_components -g !**/*.code-search --max-filesize<PHONE_NUMBER>4 --no-ignore-parent --follow --crlf --fixed-strings --no-config --no-ignore-global --json -- foobar .

I thought maybe the !* may be causing the issue since this is a bash bang function so I removed the search exclusions in VSC which ran rg without the !** but it still crashed.
"/Applications/Visual Studio Code.app/Contents/Resources/app/node_modules.asar.unpacked/vscode-ripgrep/bin/rg" --hidden --ignore-case --max-filesize<PHONE_NUMBER>4 --no-ignore --follow --crlf --fixed-strings --no-config --no-ignore-global --json -- foobar .

If I open up a lot of terminal sessions and run either of these commands at the same time in all my terminals they take about 3-4 seconds but they all eventually finish without freezing.
However, if I open VSC to my ansible playbook directory and search for "foobar" then quickly add a "2" to the end of the search and hit ENTER again, my system freezes after a couple of seconds and I never see the rg process for "foobar2".  It's almost like VSC isn't properly killing the first process and it hangs.

Hey guys, been love VS Code for a while, but this bug suddenly started I think a month ish ago for me? What is this about? Its really hurting my experience with VS Code big time :(
Never knew that now I actually may forced to switch to something else soon if this still not getting fixed. This should really be a high priority fix for VS Code team as its really really hurting the experience by constantly had to restart the machine because code search jam the system time to time too frequent. Is there some sort of stackoverflow cause by some sort of recursive functions? Because its the only thing I can think of when this level of jammies came up.

Sorry, no update and I still don't have a theory for what's going on, except that it probably involves starting multiple searches quickly. I am merging this issue into https://github.com/microsoft/vscode/issues/87254


Bugfix/prevent upsert when images are uploaded

Linked PR: https://github.com/FlowiseAI/FlowiseChatEmbed/pull/233

Same problem in my system.


issues with page numbers in documentation

I am just browsing through the documentation and noticed two issues:

page 16 and 22 miss the page numbers
page number "18" is rendered off-center

No folios on chapter numbers is deliberate, but I've just fixed the off-center problem.


dateTimeadd function doesn't add years correctly

Bicep version
0.9.1
Describe the bug
I have a start date '2022-09-01T00:00:00Z' and I calculated the end date with var endDate = dateTimeAdd(startDate, 'P10Y')
The resulted end date is '2032-08-29T00:00:00Z' while I expected '2032-09-01T00:00:00Z'
To Reproduce
See bug description
Additional context
Code was executed in Azure devops pipeline

There's some interesting points under https://softwareengineering.stackexchange.com/questions/179993/is-the-addition-of-a-duration-to-a-date-time-defined-in-iso-8601. Seems like there is no 'right' answer for how a duration should be added to a datetime.
We should document the current behavior.

// Expected
var startDate = System.DateTime.Parse("2022-09-01T00:00:00Z");
var endDate = startDate.AddYears(10);

// Currently
var endDateCurrent = startDate.Add(System.TimeSpan.FromDays(365 * 10)); // TimeSpan does not support years

Console.WriteLine($"Start Date: {startDate}");
Console.WriteLine($"End Date (Expected): {endDate}");
Console.WriteLine($"End Date (Current): {endDateCurrent}");

// Start Date: 09/01/2022 00:00:00
// End Date (Expected): 09/01/2032 00:00:00
// End Date (Current): 08/29/2032 00:00:00

Is there a draw back to adding a few more functions like dateAddMonth, dateAddYear, dateAddDays
dateAddMonth(dateAddYear(utcNow(), 2), 1)

I agree with @anthony-c-martin. Our underlying implementation uses the .net date/time library to perform the calculations and we have no plans to deviate from that given a lack of standard way to adding years or months to a date. We definitely need to document this current behavior, though.

PR created - https://github.com/MicrosoftDocs/azure-docs-pr/pull/254757.

See the remarks section in https://learn.microsoft.com/en-us/azure/azure-resource-manager/bicep/bicep-functions-date#datetimeadd


websocketpp: fix cross

Apparently, that's all needed to get websocketpp to cross-compile.
Motivation for this change
Things done

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

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 107540 run on x86_64-darwin 1

1 package built:

websocketpp


Allow a way to deal with unsigned certificates

I am trying to use Kitura-net to do a POST but the request fails because the host is using an unsigned certificate. Unfortunately, while the underlying libcurl should support this scenario, Kitura-net does not expose a way to control it.

In my specific case, I need to disable both CURLOPT_SSL_VERIFYHOST and CURLOPT_SSL_VERIFYPEER in order to make my scenario work.

@bjustin-ibm I pushed an enhancement that allows curl options to be passed in. This is on its own branch atm but hopefully will be merged in soon.

@bjustin-ibm Hey we talked it over internally and decided that allowing arbitrary options to be passed in could mess things up too much. Therefore we changed the option to just allow SSL verification disabling.

@dfirsht I took a peek at ee863d73d68899075ddbd7c8267028c7dda7696d and verified this should definitely work for my needs. Thanks!

Great! We just need to get this validated by @shmuelk and then we can merge this in.

Shmuel validated it and I merged it in. It is in 0.13.8.


build and publish multi-arch image manifest

What this PR does / why we need it:
Build and push multi-arch images + manifest in github actions
Which issue this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged): fixes #142
❯ curl -L https://github.com/jbpratt/cluster-api-provider-kubevirt/releases/download/v0.1.2-test-3/infrastructure-components.yaml | kubectl apply -f -
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
100  630k  100  630k    0     0   131k      0  0:00:04  0:00:04 --:--:--     0
namespace/capk-system created
customresourcedefinition.apiextensions.k8s.io/kubevirtclusters.infrastructure.cluster.x-k8s.io created
customresourcedefinition.apiextensions.k8s.io/kubevirtmachines.infrastructure.cluster.x-k8s.io created
customresourcedefinition.apiextensions.k8s.io/kubevirtmachinetemplates.infrastructure.cluster.x-k8s.io created
serviceaccount/capk-manager created
role.rbac.authorization.k8s.io/capk-leader-election-role created
clusterrole.rbac.authorization.k8s.io/capk-manager-role created
clusterrole.rbac.authorization.k8s.io/capk-proxy-role created
rolebinding.rbac.authorization.k8s.io/capk-leader-election-rolebinding created
clusterrolebinding.rbac.authorization.k8s.io/capk-manager-rolebinding created
clusterrolebinding.rbac.authorization.k8s.io/capk-proxy-rolebinding created
service/capk-controller-manager-metrics-service created
service/capk-webhook-service created
deployment.apps/capk-controller-manager created
certificate.cert-manager.io/capk-serving-cert created
issuer.cert-manager.io/capk-selfsigned-issuer created
validatingwebhookconfiguration.admissionregistration.k8s.io/capk-validating-webhook-configuration created

❯ kubectl get pods -n capk-system
NAME                                       READY   STATUS              RESTARTS   AGE
capk-controller-manager-6856dbb6c6-4bpwm   2/2     Running             0          9s

Run the make targets to build and publish the multi-arch images and
manifest, updating the image kustomized into the manager deployment to
be the manifest.
Signed-off-by: jbpratt<EMAIL_ADDRESS>I did a test release here https://github.com/jbpratt/cluster-api-provider-kubevirt/releases/tag/v0.1.2-test-3
Special notes for your reviewer:
:)
Release notes:

Publish a multi-arch image manifest with amd64, arm64 and arm images

/ok-to-test


Figure out why Error test model did not catch regression fixed by #470

See https://github.com/smithy-lang/smithy-dafny/pull/470#issuecomment-2207492791

To be fair, I am not certain it was a regression... I think the dtor_message was always there, and never evalulated.

NVM: It was a regression. dtor_message was NOT there.
https://github.com/aws/aws-cryptographic-material-providers-library/pull/466/files#diff-dd5fcb32e2c3c0081e3a9168f7ff4d1c17fcb2122f6565925dfcc103d47bd7ee


How to use

I paste the files into the classes and src folders. I then run the command on the terminal to open the GUI and I get this error in the log: Can not find class Calculator
Please check CLASSPATH
Can someone help me?

Hi @pedrogyn
First, you must to create a session folder, similar with this: https://github.com/jacksonpradolima/MuJava4Run/tree/master/examples/session1
Addictionaly, You must to create the result folder.
After, set the config files, mujava.config for GUI or mujavaCLI.config for command line, with the path of your session.
Finally, run the program =D


Use Machine Learning to Extract Information from Documents with Document Information Extraction Trial UI

Tutorial URL: https://developers.sap.com/tutorials/cp-aibus-dox-ui.html
Please specify the step you are referring to : Step 2: See and edit extraction results
The names of Header fields and Line items are different than the actual result. Such as Document Number(in screenshot its Invoice number), Receiver Name(Buyer Name) Receiver Address(Buyer Address) etc. as shown in screenshot below
Expected :

Actual Header field names :

Landscape Label name : trail1 & trail2
Scenario Label: SCPTest-docinfo
Sprint Label: SCPTest-2012B
Priority: Low

Hello,
The screenshots have been updated, as requested (https://github.com/SAPDocuments/Tutorials/pull/6356).
Best regards,
Juliana


False caching with docker:build from tar

Output of docker version:
Client:
 Version:      1.10.3
 API version:  1.22
 Go version:   go1.6
 Git commit:   20f81dd
 Built:        Sat Mar 12 04:07:44 UTC 2016
 OS/Arch:      darwin/amd64

Server:
 Version:      1.10.1
 API version:  1.22
 Go version:   go1.5.3
 Git commit:   9e83765
 Built:        Thu Feb 11 20:39:58 2016
 OS/Arch:      linux/amd64

Output of docker info:
Containers: 9
 Running: 0
 Paused: 0
 Stopped: 9
Images: 313
Server Version: 1.10.1
Storage Driver: aufs
 Root Dir: /mnt/sda1/var/lib/docker/aufs
 Backing Filesystem: extfs
 Dirs: 513
 Dirperm1 Supported: true
Execution Driver: native-0.2
Logging Driver: json-file
Plugins:
 Volume: local
 Network: bridge null host
Kernel Version: 4.1.17-boot2docker
Operating System: Boot2Docker 1.10.1 (TCL 6.4.1); master : b03e158 - Thu Feb 11 22:34:01 UTC 2016
OSType: linux
Architecture: x86_64
CPUs: 1
Total Memory: 3.859 GiB
Name: default
ID: A3MX:GV5U:BPUI:D5MK:NUE5:OSG2:4QIC:BQ46:ZPER:ZCWN:7252:A7CN
Debug mode (server): true
 File Descriptors: 11
 Goroutines: 22
 System Time: 2016-04-01T06:56:34.579020913Z
 EventsListeners: 0
 Init SHA1:
 Init Path: /usr/local/bin/docker
 Docker Root Dir: /mnt/sda1/var/lib/docker
Username: rhuss
Registry: https://index.docker.io/v1/
Labels:
 provider=virtualbox

Additional environment details (AWS, VirtualBox, physical, etc.):
docker-machine with VirtualBox on OS X
Steps to reproduce the issue:
Please use the attached tar archive which contains Dockerfile + content and which are clearly different.
Then:
$ cat jolokia-1.2.3.tar | docker build -t test -
Sending build context to Docker daemon 665.6 kB
Step 1 : FROM consol/tomcat-7.0:latest
 ---> 7c34bafd1150
Step 2 : COPY maven /maven/
 ---> ea6f3b06163b
Removing intermediate container 41d60250f1c7
Successfully built ea6f3b06163b

$ cat jolokia-1.3.2.tar | docker build -t test -
Sending build context to Docker daemon 675.8 kB
Step 1 : FROM consol/tomcat-7.0:latest
 ---> 7c34bafd1150
Step 2 : COPY maven /maven/
 ---> Using cache
 ---> ea6f3b06163b
Successfully built ea6f3b06163b

Describe the results you expected:
The second step must not cache because the content of the tar is different.
Additional information you deem important (e.g. issue happens only occasionally):
The tar file looks like
$ tar tvf jolokia-1.2.3.tar
-rw-r--r--  0 roland staff  307617 Apr  1 08:30 maven/./jolokia.war
-rw-r--r--  0 roland staff  345487 Apr  1 08:30 maven/./jolokia-it.war
-rw-r--r--  0 roland staff      49 Apr  1 08:44 Dockerfile

$ tar tvf jolokia-1.3.2.tar
-rw-r--r--  0 roland staff  315524 Feb 13 21:19 maven/./jolokia.war
-rw-r--r--  0 roland staff  353833 Oct 13 11:31 maven/./jolokia-it.war
-rw-r--r--  0 roland staff      49 Apr  1 08:47 Dockerfile

So albeit this is a completely valid tar archive, it could be that the extra dot confuses Docker. If the tar is rearrange to look like
drwxr-xr-x  0 roland staff       0 Apr  1 09:05 maven/
-rw-r--r--  0 roland staff      49 Apr  1 09:05 Dockerfile
-rw-r--r--  0 roland staff  353833 Oct 13 11:31 maven/jolokia-it.war
-rw-r--r--  0 roland staff  315524 Feb 13 21:19 maven/jolokia.war

then caching works as expected.
The tar-archive above which prevents caching is created by a tool (Maven) and can't be changed easily. See also https://github.com/fabric8io/docker-maven-plugin/issues/422 where this issue was reported the first time.

Test data containe tars mentioned above: test-data.zip

ping @aaronlehmann @tonistiigi PTAL
thanks for reporting and investigating @rhuss

Yes, I think this is due to the extra . in the tar.
Tarsum maintains a map of hashes by file path. It removes a leading ./ from the path but doesn't do any additional normalization to remove extra ./ components from the path: https://github.com/docker/docker/blob/master/pkg/tarsum/tarsum.go#L238
Then the builder walks the untarred directory and queries each file by in this map by relative path: https://github.com/docker/docker/blob/master/builder/tarsum.go#L141. It won't find these files because they will be stored in the map under maven/./... instead of maven/....
To fix this, I think https://github.com/docker/docker/blob/master/pkg/tarsum/tarsum.go#L238 should not just strip a leading ./ - it should do a full normalization.


Implement cloning from GitHub.

Codecov Report

Merging #11 (8e97952) into main (b4bd54c) will decrease coverage by 1.82%.
The diff coverage is 47.72%.

@@            Coverage Diff             @@
##             main      #11      +/-   ##
==========================================
- Coverage   57.83%   56.01%   -1.83%
==========================================
  Files          15       16       +1
  Lines         600      732     +132
==========================================
+ Hits          347      410      +63
- Misses        224      289      +65
- Partials       29       33       +4

Impacted Files
Coverage Δ

cmd/gritd/internal/apiserver/server.go
0.00% <0.00%> (ø)

cmd/gritd/internal/source/github/clone.go
62.96% <62.96%> (ø)

cmd/gritd/internal/source/github/cache.go
40.00% <100.00%> (+10.58%)
:arrow_up:

cmd/gritd/internal/source/github/repo.go
76.92% <100.00%> (+6.92%)
:arrow_up:

Continue to review full report at Codecov.

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


remove default template leading spaces

Removes 2 leading spaces from the default template.
The spaces were coming through the output, and on github this caused sections following a list to be indented as though it were a multiline list item (I've read this is a markdown thing in general)
For example:

a janet

more janets

multi-
^ line
^ janets (there are 5 blank new lines preceding this, and just two spaces at the start of the line)

For example:
* a janet
* more janets
* multi-

  ^ line
  ^ janets  (there are 5 blank new lines preceding this, and just two spaces at the start of the line)

Seems odd that multiple zero-space blank lines will still trigger a multiline list item, but I saw people struggling with this back to 2013, and its new to me. But here we are :)

Hmm, I wonder what's going on here.
IIUC, I think the intent was for Janet's parser to trim the leading spaces because the item in question is a long-string.
Is it possible there is a Windows environment involved here?  If so, it might have something to do with:

https://github.com/janet-lang/janet/issues/1302
https://github.com/janet-lang/janet/issues/1502

Ah I think you're right! I just tested on linux (like I should have first) and none of the spaces make it through.
I'm unfamiliar with the .gitattributes though, does that go in the project directory or some global location? I had installed documentarian via jpm install (git url), do I have some influence over that compilation then?

I'll close this since there seems to be a bigger issue

On second thought I am going to reopen this. The core issue is a wont-fix in Janet, so it would probably be good if this works multiplatform

closed while core issue is potentially resolved


How to CORS in Lumen

Hello I switched to Lumen 9.1.6. I had composer saying that laravel-cors has to be replaced. Currently, I have in app.php :
<?php

$app->configure('cors');

$app->middleware([
    Fruitcake\Cors\HandleCors::class,
]);

$app->register(Fruitcake\Cors\CorsServiceProvider::class);

I have replaced \Fruitcake\Cors\HandleCors::class, with \Illuminate\Http\Middleware\HandleCors::class but what about the service provider ?

+1 I've same problem

I'm sorry, Lumen is not supported. I think you can keep using laravel-cors probably?


<EMAIL_ADDRESS>Decompress Error

Updating 'librewolf' (90.0.2 -> 91.0.1)
Downloading new version
librewolf-91.0.1.en-US.win64.zip (75.0 MB) [==================================================================] 100%
Checking hash of librewolf-91.0.1.en-US.win64.zip ... ok.
Uninstalling 'librewolf' (90.0.2)
Removing shim for 'librewolf'.
Removing shortcut ~\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Scoop Apps\LibreWolf.lnk
Unlinking ~\scoop\apps\librewolf\current
Installing 'librewolf' (91.0.1) [64bit] [confetti]
WARN  By installing you accept following license: MPL-2.0 (https://spdx.org/licenses/MPL-2.0.html)
Loading librewolf-91.0.1.en-US.win64.zip from cache
Extracting librewolf-91.0.1.en-US.win64.zip ... ERROR Could not find 'librewolf in C:\Users\[username]\scoop\apps\librewolf\91.0.1'! (error 16)

Please try again or create a new issue by using the following link and paste your console output:
https://github.com/starise/Scoop-Confetti/issues/new?title=librewolf%4091.0.1%3a+Decompress+Error&body=Could+not+find+%27librewolf+in+C%3a%5cUsers%5c[username]%5cscoop%5capps%5clibrewolf%5c91.0.1%27!+(error+16)

They changed zip's dir structure. It should work now.


Duplicate Add Badge PRs

@greenkeeperio I'm getting multiple "add badge" PRs. It appends another badge after the first one. Just FYI

— https://twitter.com/dbrckmn/status/823813359824945152
Asked for org/repo details in a reply, will update the issue when we get this info

Example here: https://github.com/Springworks/swagger-md/pull/152/files

Should be fixed by now. Happy to reopen.


Tyleryasaka/dev container tweaks

Checklist:

[x] Code contains relevant tests for the problem you are solving
[x] Ensure all new and existing tests pass
[x] Update any relevant READMEs and docs
[x] Submit to the develop branch instead of master

Description:
Makes some modifications to our docker container setup. Thanks again @ambertch for all the work getting it to this point. Made this easy for me.

Moves management of ganache/ipfs from container. This can already be done with a single command outside the container (npm run start), so no need to complicate things by putting it in the container. (My bad - I think it was originally my suggestion to put it in there.) See https://github.com/OriginProtocol/origin-js/issues/230. Also, if this is merged, https://github.com/OriginProtocol/origin-js/issues/228 will be unnecessary.
Creates npm commands to easily manage the docker container. See https://github.com/OriginProtocol/origin-js/issues/231
Renames the directory to bridge-container, as the container is now just managing the bridge server.

This escaped me when I reviewed it, but would this more logically belong in bridge-server?

A side effect of running the blockchain outside of the container is that the bridge server in the container can't reach http://localhost::8545 (in the container run: pm2 logs celery)...
What do you think about mounting origin-js as a volume? That way, the addresses of any deployed contracts will still be kept in sync between origin-js, the dapp linking it, and the container. There might also be docker networking configuration that does this.

@cuongdo There's a few different ways we could set this up. I think it all comes down to the use cases. In this case, I think this container exists for people that are working on origin-js (not bridge-server), so it's a bit more convenient for it to exist in this repo. People can just start hacking away at origin-js without having to clone yet another repo. That said, it might be a bit cleaner to keep the bridge-server container in, well, the bridge-server repo.
The other use case that comes to mind is for people doing bridge-server development. I'm still thinking about how to best support that.
Some options in my head are:

Keep this container in origin-js, for the purpose of making origin-js development as easy as possible
Place this container in bridge-server, which is cleaner and probably feels like the more "correct" place to put it.
Try implementing this "Origin-in-a-box" idea that has been floated around; I'm visualizing this as its own repository that uses docker-compose to clone all of our different repos (demo-dapp, origin-js, bridge-server) and spin them up into separate containers that interact with each other, and mount them as volumes so that you can do development on any or all of the repos.

The first 2 options don't address the issue of bridge-server development that needs to have origin-js running to support it. For that use case, we have a couple options:

Just ask the user to symlink the origin-js and bridge-server contract ABI directories
Use pip to more elegantly manage this symlinking (npm has this capability; I'm not familiar enough with pip to know if it supports this)
Place a docker container inside the bridge-server repo that spins up origin-js

I'm sort of leaning towards the origin-in-a-box idea. If we can get it to work, it could be really awesome. It would be a single place to easily spin up all of our different pieces and see them interact with each other. And it would take care of all the development use cases at once, with no redundancies and weird container placement schemes, or asking the user to have 3+ terminal tabs open and running several commands in each.

I also lean toward the Origin-in-a-box idea with, if possible, the ability to swap out the in-container Git repos with Docker volumes that mount the repos from the host. This would allow editing of source using a GUI editor on the host but testing in an easy to setup Docker environment. I'm no expert on Docker, so I'm not sure what challenges exist here.

@cuongdo I'm also not a docker expert but yes I'm thinking along the same lines; I think mounted volumes would be necessary for this to be useful in development, for using your own GUI code editor like you say.
My goal is to do some exploration on this idea today.


Support eager loading translations

Revisiting PR #34, whose feature must have been left behind in a version change.
Additionally to caching the translations, this PR loads the translation as an Eloquent relation. Also, I added a query scope for easily eager loading translations for a single locale.

@vinkla I see the travis tests fail for this one. It's the testbench dependency #70 was aimed at. It will pass if you merge this after the other one. (I tried to keep both PRs separate, but there's this conflict here...)

Okay, lets merge #70 first then we can rebase and merge this in.

(Ok, ended up opening another one: #72 )

Closing in favour of #72.


Preparation for The Journal of Open Source paper

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 53.971%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
3269

Relevant Lines:
6057

💛  - Coveralls


Update LexDAO space (token)

update dao token reference to 0x4053981a40836141Cb79F05f68E9da385ff1814E

also, if possible, how might I include update logo.png - https://imgur.com/gallery/fRrvQGJ ?

also, if possible, how might I include updated logo.png - https://imgur.com/gallery/fRrvQGJ ?

Replace them on your local fork folder and commit the changes. You can use doc to see how update your local fork https://docs.snapshot.page/guides/create-a-space#1-fork-snapshot-spaces-repository-here

Closing this PR for now, feel free to open it again once you've done the changes.


Dropdown-button

I've got a problem with Dropdown-button (http://maximelb.fr/ We can look here with "Réseaux sociaux" on the right top corner
Go on many times and we can see the dropdown don't run

hi, i don't know if this is a framework problem and beacuse i had the same problem, my fix for that was:
adding this to my style.css
.dropdown-content {
height: auto !important;
}
it worked for me.

Fixed in ac116d6b8a633835cb655b460f2a67a5efdf666c


Canceling out of LB Service, sends me to the static/balancing/balancers page

v0.19.2
Steps:

Go to Services
Create an Project
Click on Add Load Balancer
Click on Cancel or Save

Results:
Takes you to balancers page
Expected:
Should take you back to services page

v0.23.0-rc1
Verified fixed


Compile "includes" in the templates

Hi, it would be great to have a compile function that not only compiles the code but also compiles the includes within it. This would be useful for a webpack loader, for instance.
instead something like that:
__eta.res+='<!DOCTYPE html>\n\n  \n    Hi '
__eta.res+=__eta.e(it.name)
__eta.res+='!\n    '
__eta.res+=include("./tpls/menu.eta")
__eta.res+='  \n\n'

to a:
__eta.res+='<!DOCTYPE html>\n\n  \n    Hi '
__eta.res+=__eta.e(it.name)
__eta.res+='!\n    '
__eta.res+=include((__eta) => {
__eta.res+='This is a menu template';
})
__eta.res+='  \n\n'

I would appreciate hearing your opinion regarding the proposal

@sviridoff, I think this is a great idea for a plugin or otherwise as an extension of the Eta template engine!
This would break the ability of templates to reference themselves conditionally, e.g.
partials/comment.eta
<% if (it.childComment) { %>
<%~ include("/partials/comment.eta") %>
<% } %>

So I won't change the builtin behavior.


Beta 1.10: Open With Button Spacing is Off

Testing on beta.hydroshare.org - Chrome on my Mac. The spacing on the "Open With" button is off. This is what it looks like on Beta:

This is what it looks like on www:

tested on beta


set up with Nginx

I try to set up with Nginx but I always get 502 Bad Gateway.  Do you have any suggest?
Here is docker-compose.production.yml
services:
  nginx:
    image: nginx:1.16 # this will use the latest version of 1.13.x
    ports:
      - "80:80" # expose 80 on host and sent to 80 in container
    volumes:
      - ./nginx/nginx.conf:/etc/nginx/conf.d/default.conf:ro
    depends_on:
      - app
  redis:
    image: "redis:alpine"
    ports:
      - "6379:6379"
    hostname: redis
  app:
    container_name: app
    build:
      context: ./
    restart: always
    ports:
      - "8080:8080"
    environment:
      NODE_ENV: production
    depends_on:
      - redis

And this is Nginx config
server {
    listen 80;
    server_name example.org
    location / {
        proxy_pass http://<IP_ADDRESS>:8080;
        proxy_http_version 1.1;
        proxy_set_header Upgrade $http_upgrade;
        proxy_set_header Connection 'upgrade';
        proxy_set_header Host $host;
        proxy_cache_bypass $http_upgrade;
        proxy_redirect off;
     }
}

Thank you!!

I'm planning to add a couple updates, including Nginx in a week or two.
I'll report back here if I run into a similar issue.

Thank you! however, I solved the problem.


Rename application-sql.mysql to application-mysql.sql

incorrect file name

@Vishanth Will it be possible for you to re-submit this pull request on the latest master branch? I tried to merge this but the rebase process fails as this commit is bit old.
Thanks

@imesh I think someone has already made this change. so we could close this PR


Can't find and install pylance

When switching language server to Pylance, I see a popup stating that Pylance is not installed and that I should click yes to get to the Pylance page. However, the page does not open after clicking yes. I can also not find Pylance when searching for it in the extensions pane.
Environment data
Version: 1.49.1
Commit: 58bb7b2331731bf72587010e943852e13e6fd3cf
Date: 2020-09-23T22:26:38.399Z
Electron: 9.2.1
Chrome: 83.0.4103.122
Node.js: 12.14.1
V8: <IP_ADDRESS>-electron.0
OS: Linux x64 5.4.67-1-MANJARO
Expected behaviour
The Pylance page opens and I can install it.
Actual behaviour
The Pylance page does not open.
Logs
From developer tools:
Error: No matching bindings found for serviceIdentifier: Symbol(ILanguageServerActivator)
Symbol(ILanguageServerActivator) - named: Jedi
at /home/felipe/.vscode…ent/extension.js:47
at m (/home/felipe/.vscode…ent/extension.js:47)
at e (/home/felipe/.vscode…ent/extension.js:47)
at Object.t.plan (/home/felipe/.vscode…ent/extension.js:47)
at /home/felipe/.vscode…ent/extension.js:47
at e._get (/home/felipe/.vscode…ent/extension.js:47)
at e.getTagged (/home/felipe/.vscode…ent/extension.js:47)
at e.getNamed (/home/felipe/.vscode…ent/extension.js:47)
at a.get (/home/felipe/.vscode…ent/extension.js:56)
at C.createRefCountedServer (/home/felipe/.vscode…ent/extension.js:47)
at processTicksAndRejections (internal/process/task_queues.js:94)
at async C.activate (/home/felipe/.vscode…ent/extension.js:47)
at async Promise.all (/usr/lib/code/out/vs…r/workbench/index 4)
at async y.activateWorkspace (/home/felipe/.vscode…ent/extension.js:47)

Are you using an official build of VS Code, or one out of the manjaro repos? To find it, you can also open the extensions tab and search for Pylance.
Would potentially be fixed by microsoft/vscode-python#14264 (though it's not perfectly related). This is technically a core extension issue, but I'll leave it here for now.

I use VS Code from the Manjaro repos and I can't find Pylance when I search for it in the extensions tab (neither "pylance" nor "ms-python.vscode-pylance" works).
I'll try with a different build.

After installing visual-studio-code-bin from the AUR, I can find and install Pylance.

Weird, it should be searchable regardless. Either way, we can't support running in unofficial builds and installing from the AUR worked, so I'll close this.

I use the Arch Linux code package.  I also could not find it in the market place.  I could, though, download the extension as VSIX file and then install it.
Installing by just opening the file did not work, but in my extensions overview I could select "..." > "Install von VSIX..." and install it.
When I then look into the Extension Host Logs, I find
[2020-10-19 20:40:37.755] [exthost] [error] Activating extension ms-python.vscode-pylance failed due to an error:
[2020-10-19 20:40:37.756] [exthost] [error] Error: You may only use the Pylance extension with Visual Studio Code, Visual Studio or Xamarin Studio software
to help you develop and test your applications.
The software is licensed, not sold.
This agreement only gives you some rights to use the software.
Microsoft reserves all other rights
You may not work around any technical limitations in the software;
reverse engineer, decompile or disassemble the software
remove, minimize, block or modify any notices of Microsoft or
its suppliers in the software share, publish, rent, or lease
the software, or provide the software as a stand-alone hosted as solution for others to use.

In the case that it's useful, here is the rest of the logs:
[2020-10-19 20:40:37.755] [exthost] [error] Activating extension ms-python.vscode-pylance failed due to an error:
[2020-10-19 20:40:37.756] [exthost] [error] Error: You may only use the Pylance extension with Visual Studio Code, Visual Studio or Xamarin Studio software
to help you develop and test your applications.
The software is licensed, not sold.
This agreement only gives you some rights to use the software.
Microsoft reserves all other rights
You may not work around any technical limitations in the software;
reverse engineer, decompile or disassemble the software
remove, minimize, block or modify any notices of Microsoft or
its suppliers in the software share, publish, rent, or lease
the software, or provide the software as a stand-alone hosted as solution for others to use.
	at /home/skunk/.vscode-oss/extensions/ms-python.vscode-pylance-2020.10.1/dist/extension.bundle.js:1:33467
	at /home/skunk/.vscode-oss/extensions/ms-python.vscode-pylance-2020.10.1/dist/extension.bundle.js:1:33486
	at Generator.next (<anonymous>)
	at /home/skunk/.vscode-oss/extensions/ms-python.vscode-pylance-2020.10.1/dist/extension.bundle.js:1:31099
	at new Promise (<anonymous>)
	at _0x235f1d (/home/skunk/.vscode-oss/extensions/ms-python.vscode-pylance-2020.10.1/dist/extension.bundle.js:1:30296)
	at _0x176030.activate (/home/skunk/.vscode-oss/extensions/ms-python.vscode-pylance-2020.10.1/dist/extension.bundle.js:1:31953)
	at Function._callActivateOptional (/usr/lib/code/out/vs/workbench/services/extensions/node/extensionHostProcess.js:927:841)
	at Function._callActivate (/usr/lib/code/out/vs/workbench/services/extensions/node/extensionHostProcess.js:927:492)
	at /usr/lib/code/out/vs/workbench/services/extensions/node/extensionHostProcess.js:925:841
	at processTicksAndRejections (internal/process/task_queues.js:94:5)
	at async Promise.all (index 0)
[2020-10-19 20:40:40.001] [exthost] [error] [ms-python.python] provider FAILED
[2020-10-19 20:40:40.003] [exthost] [error] Error: [ms-python.python]: Proposed API is only available when running out of dev or with the following command line switch: --enable-proposed-api ms-python.python
	at a (/usr/lib/code/out/vs/workbench/services/extensions/node/extensionHostProcess.js:655:99)
	at Object.t.checkProposedApiEnabled (/usr/lib/code/out/vs/workbench/services/extensions/node/extensionHostProcess.js:655:567)
	at Object.get activeNotebookEditor [as activeNotebookEditor] (/usr/lib/code/out/vs/workbench/services/extensions/node/extensionHostProcess.js:1003:116)
	at u.get activeNotebookEditor [as activeNotebookEditor] (/home/skunk/.vscode-oss/extensions/ms-python.python-2020.9.114305/out/client/extension.js:54:383170)
	at g.provideCodeLenses (/home/skunk/.vscode-oss/extensions/ms-python.python-2020.9.114305/out/client/extension.js:56:230947)
	at /usr/lib/code/out/vs/workbench/services/extensions/node/extensionHostProcess.js:731:671
	at /usr/lib/code/out/vs/workbench/services/extensions/node/extensionHostProcess.js:51:976
	at new Promise (<anonymous>)
	at Object.t.asPromise (/usr/lib/code/out/vs/workbench/services/extensions/node/extensionHostProcess.js:51:948)
	at _.provideCodeLenses (/usr/lib/code/out/vs/workbench/services/extensions/node/extensionHostProcess.js:731:642)
	at /usr/lib/code/out/vs/workbench/services/extensions/node/extensionHostProcess.js:753:370
	at K._withAdapter (/usr/lib/code/out/vs/workbench/services/extensions/node/extensionHostProcess.js:752:10)
	at K.$provideCodeLenses (/usr/lib/code/out/vs/workbench/services/extensions/node/extensionHostProcess.js:753:348)
	at m._doInvokeHandler (/usr/lib/code/out/vs/workbench/services/extensions/node/extensionHostProcess.js:870:464)
	at m._invokeHandler (/usr/lib/code/out/vs/workbench/services/extensions/node/extensionHostProcess.js:870:156)
	at m._receiveRequest (/usr/lib/code/out/vs/workbench/services/extensions/node/extensionHostProcess.js:868:766)
	at m._receiveOneMessage (/usr/lib/code/out/vs/workbench/services/extensions/node/extensionHostProcess.js:867:623)
	at /usr/lib/code/out/vs/workbench/services/extensions/node/extensionHostProcess.js:865:691
	at l.fire (/usr/lib/code/out/vs/workbench/services/extensions/node/extensionHostProcess.js:45:801)
	at v.fire (/usr/lib/code/out/vs/workbench/services/extensions/node/extensionHostProcess.js:256:381)
	at /usr/lib/code/out/vs/workbench/services/extensions/node/extensionHostProcess.js:1059:179
	at l.fire (/usr/lib/code/out/vs/workbench/services/extensions/node/extensionHostProcess.js:45:801)
	at v.fire (/usr/lib/code/out/vs/workbench/services/extensions/node/extensionHostProcess.js:256:381)
	at t.PersistentProtocol._receiveMessage (/usr/lib/code/out/vs/workbench/services/extensions/node/extensionHostProcess.js:261:451)
	at /usr/lib/code/out/vs/workbench/services/extensions/node/extensionHostProcess.js:258:489
	at l.fire (/usr/lib/code/out/vs/workbench/services/extensions/node/extensionHostProcess.js:45:801)
	at p.acceptChunk (/usr/lib/code/out/vs/workbench/services/extensions/node/extensionHostProcess.js:253:851)
	at /usr/lib/code/out/vs/workbench/services/extensions/node/extensionHostProcess.js:253:203
	at Socket.t (/usr/lib/code/out/vs/workbench/services/extensions/node/extensionHostProcess.js:263:54)
	at Socket.emit (events.js:223:5)
	at addChunk (_stream_readable.js:309:12)
	at readableAddChunk (_stream_readable.js:290:11)
	at Socket.Readable.push (_stream_readable.js:224:10)
	at Pipe.onStreamRead (internal/stream_base_commons.js:181:23)

Pylance is not licensed for use in unofficial builds; that message is expected when pulling code from the Arch repos as it is not "VS Code". The alternative for Arch is building visual-studio-code-bin from the AUR, which pulls an official build.

Could you please mention that on the marketplace site? That might save some people a headache.

Sure, we can add it to the readme or add a troubleshooting section that lists this.

Pylance is not licensed for use in unofficial builds

Hey @jakebailey, it looks like this thread has garnered a lot of attention on Reddit today, and I think a lot of people including myself are wondering what the rationale was for only licensing Pylance for official builds. I believe your team is well within their rights to do this, I am just a bit curious is all. Are you able to shed some light on this? Thanks and have a wonderful day :)

Ping @jakebailey

@subnut, We have shared our reason for licensing Pylance for use only in Microsoft products and services in issue #4. We are currently working on further clarifying the answers to this and other questions in a FAQ.
Thanks

Far from the first time any of this happens. Let it be a reminder that Vscode is not how free software is done. I have already switched to something else since I take open source seriously, as should anyone that cares about open source.

Just stumbled across this, because I use an unofficial VSCode build that enables native Wayland support (Microsoft doesn't offer this yet, so I pretty much have to use this...)
So it seems to me like i have no chance to use the Pylance extension now, which really is a pity and unnecessary.

@jakebailey If you don't want to provide official support for unofficial builds, that's totally understandable. But there's a difference between merely not guaranteeing compatibility, and actively taking steps to prevent compatibility. Why can't you let us at least try it in unofficial builds, in case it does still work?

No answers.

"not licensed" doesnt mean "not supported". they're not going to remove the message unless they decide to open source in the future

Wow, that is really frustrating for me as archlinux user.

I'm using Manjaro and have VSCode installed from the 'Official Repositories'. In order to have the Python extension correctly running with Pylance, you just need to install from AUR code-features and code-marketplace.

Hey, I also stumbled across this issue as a manjaro user using code OSS. None of the other workarounds did not do the trick for me but installing pylance via cmd-line (code --install-extension ms-python.vscode-pylanc) and updating the user-settings with "python.languageServer": "Pylance" worked.


can not create account use cleos command

i have create local wallet address and import two private key.
and run this command
cleos  -u http://mainnet.genereos.io create account eosio eosio.token EOS74bPXbwdz7Any4me8Zwwrs5SVxeSmLYmW35n9e4jKWiFgBHrqk EOS8LPedxtcz5KzDT8oUZMgyptQh9v3jXxQzqsGCfcZdbSdPgyzAJ
it returns
Error 3090003: provided keys, permissions, and delays do not satisfy declared authorizations
Ensure that you have the related private keys inside your wallet and your wallet is unlocked.
but the wallent is unlock status and has two keys inside.
so have a  solution ?

No, that's not the right way. cleos create account CREATOR NEW_ACCOUNT OWNER_KEY AVTICE_KEY -p CREATOR is TESTING only.
The right way to create account on main net is cleos -u http://mainnet.genereos.io CREATOR NEW_ACCOUNT OWNER_KEY ACTIVE_KEY --staked-net "0.0001 EOS" --stake-cpu "0.0001 EOS" --buy-ram "0.0439 EOS" -p CREATOR

and then return the error.
cleos --wallet-url http://localhost:8900/ -u http://mainnet.genereos.io/ creator eostonystark EOS74bPXbwdz7Any4me8Zwwrs5SVxeSmLYmW35n9e4jKWiFgBHrqk EOS8LPedxtcz5KzDT8oUZMgyptQh9v3jXxQzqsGCfcZdbSdPgyzAJ --staked-net "0 EOS" --stake-cpu "0 EOS" --buy-ram "0 EOS" -p creator
the error message
Host and port options (-H, --wallet-host, etc.) have been replaced with -u/--url and --wallet-url
Use for example -u http://localhost:8888 or --url https://example.invalid/

Try with cleos -v ... to see better error message. You are not allowed to specify 0 EOS.

the wallet and public key save on the local host.
now can not query on the main net.
how to transfer eos to this wallet ?

Also unable to create a/c on mainnet. Proper examples and docs are very needed.

There is no account named creator on the mainnet, and even if there was, you would need its private key to be able to execute that command.  Accounts can only be created from existing accounts.  There is no mechanism whatsoever to simply inject a new account into the system after it's up and running.  If you did not register ICO tokens before mainnet launch, you do not have and can not create an account.
Presumably an account creation service with arise, but I'm not aware of any at present.

Presumably an account creation service with arise, but I'm not aware of any at present.

https://medium.com/coinmonks/create-your-own-eos-account-easily-using-the-non-service-fee-dapp-signupeoseos-b15c5347f2fc
There is one such service now, worth a try.


Add F8/BF8 hybird mode CI testes

local test result is pass on gfx941.
[----------] Global test environment tear-down
[==========] 11563 tests from 2 test suites ran. (2020594 ms total)
[  PASSED  ] 11563 tests.
hipBLASLt version: 300


Feature/company views client

[x] Add view for company (client side)
[x] Add partial for news
[x] Add partial for documents
[x] Add button 'Load more'
[x] Update script load_more
[x] Add styles
[x] Add adaptability to the company page
[x] Add tests for the company page

https://trello.com/c/Eoy4ZTyk/32-create-companies-page

Hm, I thought we agreed on another icon.

Changed icons


Fix site title outside posts and text selection around pagination

The main title would show " - Scribble", because page.title is empty, now it will show just "Scribble"
I made the pagination container ignore pointer events so that when selecting text, the pagination container doesn't confuse the cursor

2. I made the pagination container ignore pointer events so that when selecting text, the pagination container doesn't confuse the cursor

Would you clarify what you meant by "confuse the cursor"?

Sorry, that wasn't very clear. See the gif below. When the cursor passes over the area where the pagination container is located, selection jumps all the way to the bottom until the cursors exits the pagination area.

I made the pagination container ignore pointer events so that when selecting text, the pagination container doesn't confuse the cursor

This is a very nice change :) Previously, links that fall right behind the container also get unclickable. But your PR solves the problem, thanks :) I hope you don't mind, I already applied this commit to my fork (keeping your authorship, of course)


fix: layout shifting issue with navbar caused by scroll bar

There is an issue with layout shifting when clicking the navbar as shown in the image below.
I resolved it by adding padding-left to the body tag.

Thanks, this is a very clever hack!


HTTP 204s do not conform to HTTP spec

First check

[X] I added a very descriptive title to this issue.
[X] I used the GitHub search to find a similar issue and didn't find it.
[X] I searched the FastAPI documentation, with the integrated search.
[X] I already searched in Google "How to X in FastAPI" and didn't find any information.
[X] I already read and followed all the tutorial in the docs and didn't find an answer.
[X] I already checked if it is not related to FastAPI but to Pydantic.
[X] I already checked if it is not related to FastAPI but to Swagger UI.
[X] I already checked if it is not related to FastAPI but to ReDoc.
[X] After submitting this, I commit to one of:

Read open issues with questions until I find 2 issues where I can help someone and add a comment to help there.
I already hit the "watch" button in this repository to receive notifications and I commit to help at least 2 people that ask questions in the future.
Implement a Pull Request for a confirmed bug.

Description
Hello! I have noticed that fastAPI's HTTP 204's No Content response does not appear to conform to the HTTP spec by default. Per the HTTP spec: https://tools.ietf.org/html/rfc2616#section-10.2.5:
   The 204 response MUST NOT include a message-body, and thus is always
   terminated by the first empty line after the header fields.

It appears that fastapi is attempting to serialize as a JSON, and thus adding data to the message body. Here is an example that you can use to reproduce:
from fastapi import FastAPI, HTTPException

app = FastAPI()

@app.get("/")
def read_root():
    raise HTTPException(status_code=204)

Curling this will result in:
curl -v localhost:8000/
*   Trying <IP_ADDRESS>...
* TCP_NODELAY set
* Connected to <IP_ADDRESS> (<IP_ADDRESS>) port 8000 (#0)
> GET / HTTP/1.1
> Host: <IP_ADDRESS>:8000
> User-Agent: curl/7.64.1
> Accept: */*
>
< HTTP/1.1 204 No Content
< date: Mon, 29 Mar 2021 20:28:47 GMT
< server: uvicorn
< content-length: 23
< content-type: application/json
<
* Excess found in a non pipelined read: excess = 23 url = / (zero-length body)
* Connection #0 to host <IP_ADDRESS> left intact
* Closing connection 0

This line indicates the issue:
* Excess found in a non pipelined read: excess = 23 url = / (zero-length body)

It looks as though it's adding the following to the body:
{"detail":"No Content"}

Expected Behavior
The expected behavior is to not return anything in the body. This behavior should be the default when handling HTTPException of a status code of 204.
The current behavior can cause issues if you have your service being fronted with a proxy that strongly enforces the HTTP spec.
I don't have time today to attempt to fix, but would be happy to.
Environment

OS: [e.g. Linux / Windows / macOS]: macOS
FastAPI Version [e.g. 0.3.0]: 0.63.0
Python version: 3.8.5

Duplicated https://github.com/tiangolo/fastapi/issues/2832

Doh!

Thanks for the help here @Kludex ! 👏  🙇
Thanks for reporting back and closing the issue @mikegrima  👍

Sorry for the long delay! 🙈  I wanted to personally address each issue/PR and they piled up through time, but now I'm checking each one in order.


Put labels at the center of residues (or chains, models, structures)

for TextBuffer & LabelRepresentation

How about for whole selections?
(Not trying to make your life harder; honestly! 😛 )

I am thinking of a parameter labelType (open to a better name)

"perAtom" (current behavior)
"perGroup"
"perChain"
"perModel"
"perStructure" (seems unnecessary)
"perSelection"