ps:restart scenarios resulting in 503

The e2e ps:restart tests are consistently hitting 503 Service Unavailable.  (See recent jenkins run for all related failures.)  I'm hitting this locally when focusing on these tests.
------------------------------
Processes with a deployed app can restart processes
  restarts all of 1
  /go/src/github.com/deis/workflow-e2e/vendor/github.com/onsi/ginkgo/extensions/table/table_entry.go:46
$ deis login http://deis.<IP_ADDRESS>.xip.io --username=test-81 --password=asdf1234
Logged in as test-81
$ deis ps:scale web=1 --app=test-260918254
Scaling processes... but first, coffee!
...done in 0s
=== test-260918254 Processes
--- web:
test-260918254-v2-web-ap44e up (v2)
$ deis ps:restart  --app=test-260918254
Restarting processes... but first, coffee!
...Error:
503 Service Unavailable
detail: tuple index out of range

• Failure [2.388 seconds]
Processes
/go/src/github.com/deis/workflow-e2e/tests/ps_test.go:161
  with a deployed app
  /go/src/github.com/deis/workflow-e2e/tests/ps_test.go:160
    can restart processes
    /go/src/github.com/deis/workflow-e2e/vendor/github.com/onsi/ginkgo/extensions/table/table.go:96
      restarts all of 1 [It]
      /go/src/github.com/deis/workflow-e2e/vendor/github.com/onsi/ginkgo/extensions/table/table_entry.go:46

      No future change is possible.  Bailing out early after 0.046s.
      Got stuck at:
           coffee!
          ...
      Waiting for:
          done in \d+s

      /go/src/github.com/deis/workflow-e2e/tests/ps_test.go:124
------------------------------

A sampling of the controller pod logs show the following when this occurs:
...
<IP_ADDRESS> "POST /v2/apps/test-387025991/pods/web/test-387025991-v2-web-xhmps/restart/ HTTP/1.1" 200 114 "Deis Client v2.0.0-dev"
<IP_ADDRESS> "GET /v2/apps/test-387025991/pods/?limit=1000 HTTP/1.1" 200 701 "Deis Client v2.0.0-dev"
<IP_ADDRESS> "GET /v2/ HTTP/1.1" 401 58 "Deis Client v2.0.0-dev"
<IP_ADDRESS> "POST /v2/auth/login/ HTTP/1.1" 200 52 "Deis Client v2.0.0-dev"
DEBUG create test-387025991
INFO test-387025991: test-81 scaled containers web=6
INFO [test-387025991]: test-81 scaled containers web=6
DEBUG create test-387025991
<IP_ADDRESS> "POST /v2/apps/test-387025991/scale/ HTTP/1.1" 204 - "Deis Client v2.0.0-dev"
<IP_ADDRESS> "GET /v2/apps/test-387025991/pods/?limit=100 HTTP/1.1" 200 701 "Deis Client v2.0.0-dev"
<IP_ADDRESS> "POST /v2/apps/test-387025991/pods/restart/ HTTP/1.1" 503 37 "Deis Client v2.0.0-dev"
<IP_ADDRESS> "GET /v2/ HTTP/1.1" 401 58 "Deis Client v2.0.0-dev"
<IP_ADDRESS> "POST /v2/auth/login/ HTTP/1.1" 200 52 "Deis Client v2.0.0-dev"
DEBUG create test-387025991
INFO test-387025991: test-81 scaled containers web=6
INFO [test-387025991]: test-81 scaled containers web=6
DEBUG create test-387025991
<IP_ADDRESS> "POST /v2/apps/test-387025991/scale/ HTTP/1.1" 204 - "Deis Client v2.0.0-dev"
<IP_ADDRESS> "GET /v2/apps/test-387025991/pods/?limit=100 HTTP/1.1" 200 701 "Deis Client v2.0.0-dev"
<IP_ADDRESS> "GET /healthz HTTP/1.1" 200 2 "Go 1.1 package http"
<IP_ADDRESS> "GET /healthz HTTP/1.1" 200 2 "Go 1.1 package http"
<IP_ADDRESS> "POST /v2/apps/test-387025991/pods/web/restart/ HTTP/1.1" 503 37 "Deis Client v2.0.0-dev"
<IP_ADDRESS> "GET /v2/ HTTP/1.1" 401 58 "Deis Client v2.0.0-dev"
<IP_ADDRESS> "POST /v2/auth/login/ HTTP/1.1" 200 52 "Deis Client v2.0.0-dev"
DEBUG create test-387025991
INFO test-387025991: test-81 scaled containers web=6
INFO [test-387025991]: test-81 scaled containers web=6
DEBUG create test-387025991
<IP_ADDRESS> "POST /v2/apps/test-387025991/scale/ HTTP/1.1" 204 - "Deis Client v2.0.0-dev"
<IP_ADDRESS> "GET /v2/apps/test-387025991/pods/?limit=100 HTTP/1.1" 200 701 "Deis Client v2.0.0-dev"
<IP_ADDRESS> "POST /v2/apps/test-387025991/pods/cmd/restart/ HTTP/1.1" 503 37 "Deis Client v2.0.0-dev"
<IP_ADDRESS> "GET /v2/ HTTP/1.1" 401 58 "Deis Client v2.0.0-dev"
<IP_ADDRESS> "POST /v2/auth/login/ HTTP/1.1" 200 52 "Deis Client v2.0.0-dev"
DEBUG create test-387025991
INFO test-387025991: test-81 scaled containers web=0
INFO [test-387025991]: test-81 scaled containers web=0
DEBUG scale test-387025991-v2-web, img http://<IP_ADDRESS>:9000/git/home/test-387025991:git-779ca3d7/push/slug.tgz, params {'num': 0, 'build_type': 'buildpack', 'envs': {}, 'memory': {}, 'app_type': 'web', 'version': 'v2', 'tags': {}, 'healthcheck': {}, 'cpu': {}}, cmd "start web"
DEBUG scaling RC test-387025991-v2-web in Namespace test-387025991 from 6 to 0 replicas
DEBUG waiting for RC test-387025991-v2-web to get a newer resource version than 36118 (30s timeout)
DEBUG RC test-387025991-v2-web has a new resource version 36135
DEBUG waiting for 6 pods in test-387025991 namespace to be terminated (120s timeout)
<IP_ADDRESS> "GET /healthz HTTP/1.1" 200 2 "Go 1.1 package http"
<IP_ADDRESS> "GET /healthz HTTP/1.1" 200 2 "Go 1.1 package http"
DEBUG 6 pods in namespace test-387025991 are terminated
DEBUG create test-387025991
<IP_ADDRESS> "POST /v2/apps/test-387025991/scale/ HTTP/1.1" 204 - "Deis Client v2.0.0-dev"
<IP_ADDRESS> "GET /v2/apps/test-387025991/pods/?limit=100 HTTP/1.1" 200 24 "Deis Client v2.0.0-dev"
<IP_ADDRESS> "POST /v2/apps/test-387025991/pods/restart/ HTTP/1.1" 503 37 "Deis Client v2.0.0-dev"
<IP_ADDRESS> "GET /v2/ HTTP/1.1" 401 58 "Deis Client v2.0.0-dev"
<IP_ADDRESS> "POST /v2/auth/login/ HTTP/1.1" 200 52 "Deis Client v2.0.0-dev"
DEBUG create test-387025991
INFO test-387025991: test-81 scaled containers web=0
INFO [test-387025991]: test-81 scaled containers web=0
DEBUG create test-387025991
<IP_ADDRESS> "POST /v2/apps/test-387025991/scale/ HTTP/1.1" 204 - "Deis Client v2.0.0-dev"
<IP_ADDRESS> "GET /v2/apps/test-387025991/pods/?limit=100 HTTP/1.1" 200 24 "Deis Client v2.0.0-dev"
<IP_ADDRESS> "POST /v2/apps/test-387025991/pods/web/restart/ HTTP/1.1" 503 37 "Deis Client v2.0.0-dev"
<IP_ADDRESS> "GET /v2/ HTTP/1.1" 401 58 "Deis Client v2.0.0-dev"
<IP_ADDRESS> "POST /v2/auth/login/ HTTP/1.1" 200 52 "Deis Client v2.0.0-dev"
DEBUG create test-387025991
INFO test-387025991: test-81 scaled containers web=0
INFO [test-387025991]: test-81 scaled containers web=0
DEBUG create test-387025991
<IP_ADDRESS> "POST /v2/apps/test-387025991/scale/ HTTP/1.1" 204 - "Deis Client v2.0.0-dev"
<IP_ADDRESS> "GET /v2/apps/test-387025991/pods/?limit=100 HTTP/1.1" 200 24 "Deis Client v2.0.0-dev"
<IP_ADDRESS> "POST /v2/apps/test-387025991/pods/cmd/restart/ HTTP/1.1" 503 37 "Deis Client v2.0.0-dev"
<IP_ADDRESS> "GET /v2/ HTTP/1.1" 401 58 "Deis Client v2.0.0-dev"
<IP_ADDRESS> "POST /v2/auth/login/ HTTP/1.1" 200 52 "Deis Client v2.0.0-dev"
<IP_ADDRESS> "GET /v2/apps/?limit=100 HTTP/1.1" 200 231 "Deis Client v2.0.0-dev"
DEBUG destroy test-387025991
<IP_ADDRESS> "GET /healthz HTTP/1.1" 200 2 "Go 1.1 package http"
<IP_ADDRESS> "GET /healthz HTTP/1.1" 200 2 "Go 1.1 package http"
WARNING test-387025991: Error deleting existing application logs: HTTPConnectionPool(host='<IP_ADDRESS>', port=80): Max retries exceeded with url: /logs/test-387025991 (Caused by NewConnectionError('<requests.packages.urllib3.connection.HTTPConnection object at 0x7ffae4306be0>: Failed to establish a new connection: [Errno 111] Connection refused',))
WARNING [test-387025991]: Error deleting existing application logs: HTTPConnectionPool(host='<IP_ADDRESS>', port=80): Max retries exceeded with url: /logs/test-387025991 (Caused by NewConnectionError('<requests.packages.urllib3.connection.HTTPConnection object at 0x7ffae4306be0>: Failed to establish a new connection: [Errno 111] Connection refused',))
INFO test-387025991: domain test-387025991 removed
INFO [test-387025991]: domain test-387025991 removed
<IP_ADDRESS> "DELETE /v2/apps/test-387025991/ HTTP/1.1" 204 - "Deis Client v2.0.0-dev"
<IP_ADDRESS> "GET /v2/ HTTP/1.1" 401 58 "Deis Client v2.0.0-dev"
<IP_ADDRESS> "POST /v2/auth/login/ HTTP/1.1" 200 52 "Deis Client v2.0.0-dev"
<IP_ADDRESS> "DELETE /v2/auth/cancel/ HTTP/1.1" 204 - "Deis Client v2.0.0-dev"
<IP_ADDRESS> "GET /v2/ HTTP/1.1" 401 58 "Deis Client v2.0.0-dev"
<IP_ADDRESS> "POST /v2/auth/login/ HTTP/1.1" 200 52 "Deis Client v2.0.0-dev"
<IP_ADDRESS> "GET /v2/apps/?limit=100 HTTP/1.1" 200 52 "Deis Client v2.0.0-dev"
<IP_ADDRESS> "GET /v2/ HTTP/1.1" 401 58 "Deis Client v2.0.0-dev"
<IP_ADDRESS> "POST /v2/auth/login/ HTTP/1.1" 200 52 "Deis Client v2.0.0-dev"
<IP_ADDRESS> "DELETE /v2/auth/cancel/ HTTP/1.1" 204 - "Deis Client v2.0.0-dev"
<IP_ADDRESS> "GET /healthz HTTP/1.1" 200 2 "Go 1.1 package http"
<IP_ADDRESS> "GET /healthz HTTP/1.1" 200 2 "Go 1.1 package http"
...

These 9 tests are the consistent ones failing:
Summarizing 9 Failures:

[Fail] Processes with a deployed app can restart processes [It] restarts all of 1
/Users/vaughndice/work/go/src/github.com/deis/workflow-e2e/tests/ps_test.go:124

[Fail] Processes with a deployed app can restart processes [It] restarts all of 1 by type
/Users/vaughndice/work/go/src/github.com/deis/workflow-e2e/tests/ps_test.go:124

[Fail] Processes with a deployed app can restart processes [It] restarts all of 1 by wrong type
/Users/vaughndice/work/go/src/github.com/deis/workflow-e2e/tests/ps_test.go:122

[Fail] Processes with a deployed app can restart processes [It] restarts all of 6
/Users/vaughndice/work/go/src/github.com/deis/workflow-e2e/tests/ps_test.go:124

[Fail] Processes with a deployed app can restart processes [It] restarts all of 6 by type
/Users/vaughndice/work/go/src/github.com/deis/workflow-e2e/tests/ps_test.go:124

[Fail] Processes with a deployed app can restart processes [It] restarts all of 6 by wrong type
/Users/vaughndice/work/go/src/github.com/deis/workflow-e2e/tests/ps_test.go:122

[Fail] Processes with a deployed app can restart processes [It] restarts all of 0
/Users/vaughndice/work/go/src/github.com/deis/workflow-e2e/tests/ps_test.go:122

[Fail] Processes with a deployed app can restart processes [It] restarts all of 0 by type
/Users/vaughndice/work/go/src/github.com/deis/workflow-e2e/tests/ps_test.go:122

[Fail] Processes with a deployed app can restart processes [It] restarts all of 0 by wrong type
/Users/vaughndice/work/go/src/github.com/deis/workflow-e2e/tests/ps_test.go:122

Fixed by #497


add containerd custom rootpath support

配置采集容器内文件采集异常，通过查看日志发现
2023-06-30 06:45:44 [WRN] [metric_docker_file.go:359] [Collect] [config#/usr/local/ilogtail/./user_yaml_config.d/test.yaml,]AlarmType:DOCKER_FILE_MATCH_ALARM       unknow error:can't find path from this container        path:/home/test-log     container:busybox   logstore:       config:config#/usr/local/ilogtail/./user_yaml_config.d/test.yaml

然后查看源码，发现containerd container rootfs查找方法是通过固定的路径查询。目前调用containerd接口也无法获取rootfs目录，所以建议添加环境变量支持用户配置自定义目录。

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


using Docker in the welcome page

Description
when I try to use Docker in the welcome page after I locally deployed my verba using docker I get this error :
Failed to connect to Weaviate Collection may not have been created properly.! Unexpected status code: 422, with response body: {'error': [{'message': 'class already exists: found similar class "VERBA_Config"'}]}.
Installation

[ ] pip install goldenverba
[ ] pip install from source
[ X] Docker installation

If you installed via pip, please specify the version:
Weaviate Deployment

[ ] Local Deployment
[X ] Docker Deployment
[ ] Cloud Deployment

Configuration

Reader:
Chunker:
Embedder:
Retriever:
Generator:
Steps to Reproduce
I just downloaded all files and build my docker using the commands below:
git clone https://github.com/weaviate/Verba
docker compose --env-file  up -d --build
Additional context
I am on Mac Apple M1 Max , local link is the only thing working for me on the welcome page

Thanks for the issue! It's happening because the v2 Verba is trying to create a new collection called VERBA_Config, if you used v1 before, the old VERBA_Config is already existing, but the v2 can't recognize it because we're using the UUID as ID.
We'll add a fix to that to automatically detect these cases, as workaround you can delete the collection manually or remove the whole weaviate cluster itself and rebuild it

where do I look on a Mac for the collection so I can  delete them

If you're using Verba with Weaviate Embedded, the data should be located ~/.local/share/weaviate
If you're using Verba with a Weaviate Cluster you can use Collection interface to individually edit your data there as well

Are you using Weaviate Embedded or a Cluster?

Are you using Weaviate Embedded or a Cluster?

I am using Weaviate deployed in Docker

This should be fixed in the upcoming v2.1 version, I renamed the collections so they shouldn't conflict with older verba versions

Just released v2.1! 🚀  Let me know if it still persists


could you update the demo to show a set zoom level?

It seems too challenging to achieve a simple task: fire up a viewcontroller, set an imagescrollview with a preset zoom and offset.
I know i had it working before, but at present it doesn't seem to want to work.
thank you, drew..

The challenge with the demo is that the pod project needs a cleaning before any changes to it manifest in the running of the demo. So until you realize this, NO code changes are touched.  So.. that means that i don't know what code was being run that allowed the initial view to show a zoomed control.
As soon as i cleaned the project, the desired result was lost.  Back to square one.

The line in private func configureImageForSize(_ size: CGSize), is the culprit:
zoomScale = minimumZoomScale
Commenting it out provides proper behaviour.

Currently, I don't have a good solution for this issue. If you set initial zoomScale, it will be reset by the first orientation change. So a workaround solution is set imageScrollViewDelegate (that I have just added, am going to pushed). In this function of delegate func imageScrollViewDidChangeOrientation(imageScrollView: ImageScrollView), set your initial zoomScale.
imageScrollView.imageScrollViewDelegate = self

extension ViewController: ImageScrollViewDelegate {
	func imageScrollViewDidChangeOrientation(imageScrollView: ImageScrollView) {
               imageScrollView.zoomScale = 2
   	}
}

I've just updated version 1.7, that has delegate to do that.

This would force a scale of 2 with each change, with negates the base use-case for the repo.  I have a solution in play and will revisit this as the project matures a bit more.

Could you please share you solution?


added PREFIX=/usr to Debian package make

Fixes wrong prefix value in /usr/lib/pkgconfig/libre.pc.

Wrong branch to start with.  Will redo.


New Procedure for Post-Partum details

Incorporate a form to capture information relating to pregnancy outcomes .
This is for both VHT and Midwife App

@donrukanga1 I am assigning to you as the primary for building the forms and I will assist with the integration when the procedure form is ready.


Adapter fails to discover tests

The following messages appears on output Window after trying to rebuild my Nunit test project
------ Discover test started ------
NUnit Adapter <IP_ADDRESS>: Test discovery starting
Error: Unable to get runner for this assembly. Check installation, including any extensions.
RemotingException: Found two different objects associated with the same URI, '/ad6409a5_eed6_4df5_b143_6aea6249e17e/TestAgency'.
An exception occurred while test discoverer 'NUnit3TestDiscoverer' was loading tests. Exception: Found two different objects associated with the same URI, '/ad6409a5_eed6_4df5_b143_6aea6249e17e/TestAgency'.
========== Discover test finished: 0 found (0:00:00.4420455) ==========

Interestingly the last change that I made to my visual studio is that I put a product key on it. Before that the tests were able to be found.
This happened for me with Visual Studio Professional 2015
Version 14.0.25431.01 Update 3
Running as administrator
.Net Framework 4.5.2
NUnit version 3.5.0
I am using the visual studio extension test adapter 3.5.0
I already tried to reinstall the adapter after putting my product key.
The following message also appears at the very end of test discovery, if I rebuild my solution (which has tests with other testing frameworks)
An exception occurred while test discoverer 'NUnit3TestDiscoverer' was loading tests. Exception: Format of the executable (.exe) or library (.dll) is invalid.

The test discovery was successful after I changed the test to prefer 64 bits
Test -> Test Settings -> Default processor architecture -> x64

Since this is about the NUnit 3 adapter, I'm moving the issue to that project.

Issue moved to nunit/nunit3-vs-adapter #248 via ZenHub


[FEAT]-Have  custom-subreddit specification

Feature Request
Is your feature request related to a problem? Please describe:
Most memes that you can get from the qq meme command are from r/me_irl

Describe the solution you'd like
If we have a command to specify a subreddit or a command that can fetch memes from completely different subreddits it will be better.

Additional context

this would be worked on 👍
Do you want to work on this?
It's sort of a simple fix

thanks for contributing to EddieBot

@all-contributors add @SKULLXL for ideas

closed by 48f49f7

closed by 48f49f7


consider allowing users to pause the animated background

I find motion in animations like that used in the background will sometimes set off my motion sickness.
IMHO, it would be good if we gave the user an option to stop the animation so that it's easier to interact with the site.
I found an example codepen that does just that. Seems easy enough to add a class via javascript.
https://codepen.io/zjun/pen/dGPqzQ

If I can find some time, I might propose this change.

First and foremost, thank you very much for letting me know this.
I think instead of pausing the animated gif, I just transition to a nice, high DPI graphic for the background image. That will make it safer and more enjoyable for everyone.
The last thing I want is to inadvertently hurt anyone.

I resolved this issue with PR 22. Let me know if we need to re-open this for additional modification.

Thanks @joeblankenship1


Cas/finish risk scenarios

Last changes supporting 4 scenarios for FDA risk analysis, e.g. enabling Loop specific event reporting without a pump, supporting times for user input of events in addition to the event time, and surfacing differences between what is reported and what has happened.

Wrong merge branch, closing


Testing of fee currencies

Part of #6
### Tasks
- [ ] Add state transition tests in `op-geth` repo
- [ ] Add e2e test

Initial work is being done in https://github.com/celo-org/op-geth/pull/30


Please provide the updated api version or type

The api version this page references is a preview api ["2015-08-01-preview"]. According to the azure docs here, all preview documents are deprecated and are gone as of December 2018 -- https://azure.microsoft.com/en-us/updates/postgresql-preview-api-deprecation/
When I looked for the Dashboards type in other released apis, I do not see them. I checked the available apis mentioned in the git doc -- https://github.com/Azure/azure-resource-manager-schemas#submitting-a-pr
When I attempt to use the type [Microsoft.Portal/dashboards] I recieve a 'Value is not acceptid. Valid values: "Microsoft.Logic.integrationAccounts/assemblies".' error. Can the documentation be updated here to reflect the correct type and the api version that supports it?

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

ID: 47fb1c00-f103-92c2-32e9-eefae46a6ce9
Version Independent ID: 33555263-7be5-7164-310d-e97e6bea6704
Content: Programmatically create Azure Dashboards
Content Source: articles/azure-portal/azure-portal-dashboards-create-programmatically.md
Service: azure-portal
GitHub Login: @adamabmsft
Microsoft Alias: mblythe

Thanks for your comment. The feedback has been shared with the content owner for further review. Thanks for your patience.

I realize now that the deprecation I mentioned is for a different product - I am however still seeing this issue with the listed options


Bootstrap error classes and validation message not displaying on array field names

As the subject indicates. The bootstrap errors classes and validation messages are not displaying when there is a validation error on array fields. I have tracked this down to the following view and included a fix. I'm sure there is a more elegant solution than this, but it works!
File form_content.blade.php line 89
From
var field = $('[name="' + property + '"]'),
    container = field.parents('.form-group');

container.addClass('has-error');

To
var field = $('[name="' + property + '[]"]').length ?
    $('[name="' + property + '[]"]') :
    $('[name="' + property + '"]'),
    container = field.parents('.form-group');

container.addClass('has-error');

Hi @splodgeco ,
You're totally right, thank you, haven't noticed that. I'm just now workind on a "monster entry" with all features in the Demo, so this kind of bugs will be more visible.
I've applied your fix to the dev branch and it will be available to everyone next week. Thanks a lot, cheers!


Can't see describe of extensions

Issue Type: Bug
Hello I can't see describe of any extensions or describe of new update. Last time when I was using VS code I have at bottom of my screen white line from errors to option button.
VS Code version: Code 1.27.2 (f46c4c469d6e6d8c46f268d1553c5dc4b475840f, 2018-09-12T16:17:45.060Z)
OS version: Windows_NT x64 10.0.17134

@lakid1 Not sure if I understood your issue. Can you please provide screenshot of what you are seeing to get better understanding?

@mjbvz Could be related to web view?
@lakid1 Can you please check if the other tabs are showing content?

Still the same. I am actually tried to reinstall vscode but no results.

@lakid1 You mean you do not see anything in Contributions tab?
Can you open developer tools and let us know if there are any errors?

Duplicate of #57209
Please try this in latest VS Code insiders build


No ViewManager defined for class LottieAnimationView on android

my version:
"react-native": "^0.45.1",
"lottie-react-native": "^2.2.0",
I try :
react-native run-android
This might create a build failure.
cd android && ./gradlew clean
not fix

I had the same problem on android, i fixed it by rebuild the app using a USB cable instead of over Wifi, try that and also remember to change
android {
compileSdkVersion 25 // <-- update this to 25
// ...
according to the guide, hope it helps.

Feel free to reopen this if @tangtai's solution doesn't work


Bug - Failing Apache Cassandra 3.9 tests on CI

Expected Behaviour
CI tests on Apache Cassandra 3.9 should pass.

Actual Behaviour
CI tests on Apache Cassandra 3.9 in Travis started to fail recently, first identified in PR #25. Exact error message is:
...
shouldHaveDefaultConfigValues(com.builtamont.cassandra.migration.config.ClusterConfigurationTest)  Time elapsed: 0.007 sec  <<< FAILURE!
java.lang.AssertionError:
Expected: is "localhost"
     but: was "<IP_ADDRESS>"
...

One possible cause is due to coercion of localhost input string to InetAddress type and back.

Steps to Reproduce
Run the integration test against the latest Apache Cassandra version (3.9).

As mentioned in #25 , this could be a side effect of the test setup (which passes <IP_ADDRESS>) as part of the contact points system property value.
Provided a workaround to accept <IP_ADDRESS> for now, will refactor unit tests to clear and restore existing system properties variable as part of #28 .


pre-commit: PR119316

Link: https://github.com/llvm/llvm-project/pull/119316
Requested by: @dtcxzyw

/add-label reviewed
/close


Added semantic-release

Added semantic-release

why? i spend the last 2 weeks telling people howto fix problems coming from<EMAIL_ADDRESS>;)
doesn't have to be a problem, but for eg i18n it would be needed. it's just a recommendation for being on the save side

@doktordirk But this seems to work just fine. I think it's best to leave it in, if it works like this.

alright


save offsets when calling streamBuffered

Looking good to me, I think those errors are because our changes in azure environment?


Bower dependencies too restrictive

After #20, which is a good thing, I was about to do it myself.
May I suggest :
"dependencies": {
    "iso8601-js-period": "*",
    "leaflet": "~0.7.4 || ~1.0.0",
    "jquery": "1.x || 2.x"
    "jquery-ui": "~1.10 || ~1.11"
  }

Because you use almost nothing from jquery ($.ajax), you don't need a specific version.
You also support leaflet 1.0

I'm also wondering why ignore list contains "src" folder.

Hi @ram-one,
ok, I'm changing the dependencies.
I think we should also change main to:
  "main": [
    "dist/leaflet.timedimension.src.js",
    "dist/leaflet.timedimension.control.css",
  ],

I'm not sure about the src folder. I've checked some projects, and some of them include this folder (ex: jQuery) and others don't (ex: Leaflet). Initially, you shouldn't use the files of src folder, as you have them concatenated and minified at dist.
Any suggestion @fox91?

Yes, main is also wrong because bower will ignore src folder when downloading the package so automated tool that uses the main declaration won't find theses.
Including src allows custom builds. For example I don't want the player control because I use mine.
If the folder is in ignore list, it is simply not donwloaded.

Hi @bielfrontera,
I also looked at how it is implemented in other projects.
I think the src folder is essential for the development phase (git clone or npm) but not in the integration phase (bower), following the philosophy of Leaflet.
In any case it is a decision they make the developers of each project, as there are no real guidelines on the folders to skip.
Include the dist/ folder in the main is definitely correct.
Dependencies suggested by @ram-one seem appropriate.

Hi @bielfrontera,
I have included some changes in the pull request #22.
If you proceed with the merge you must first regenerate the dist folder.

Ok! Updated the version number to 0.1.7 and built with the enhancement for leaflet 1.0.


Missing availability set creation instructions

The VM creation instructions make reference to an availability set "myAvailabilitySet"
You need to create the availability set in advance (before creating the VMs):
az vm availability-set create --name myAvailabilitySet -g myResourceGroupSLB --location eastus
Without it the VMs creation fails. I am using a free Azure trial subscription and the Azure CLI 2.1.0 on Windows 10 + WSL1 (Ubuntu session).

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

ID: b7142f06-bd33-daf4-d7fc-475c3eaafbed
Version Independent ID: e03a6992-2329-fe7c-63bf-18d5094c5189
Content: Quickstart:Create a public Load Balancer - Azure CLI - Azure Load Balancer
Content Source: articles/load-balancer/quickstart-load-balancer-standard-public-cli.md
Service: load-balancer
GitHub Login: @asudbring
Microsoft Alias: allensu

@adrianichim As is discussed Here, the Availability Set is not needed unless you are using a Basic Load Balancer. if you are using a Standard Load Balancer, the Availability Set is not needed and can be removed from the VM Create command.
This doc seems to be confused between basic and standard, and even though it states on the title that this is for a Standard Load Balancer, it gives commands for a basic. I am assigning the issue to the doc author to evaluate and update as appropriate.
@asudbring Although the doc states that this is for Standard Load Balancer, it gives partial instructions for both, and will not work as is.

Sending to PM for review
#reassign:@anavinahar

Will fix this one.
#reassign:@asudbring

Reworked article.  Restored basic instructions and put tabs in to show both procedures.
#please-close


Update ImPACT code

ImPACT is rather outdated with respect to the rest of ctapipe.
Some points come to mind:

TelescopeParameter for the template paths
Unit tests
How to produce templates? E.g. adapt to use the stage1 tool?

I think @ParsonsRD had a script to make templates, but it is so far not included (should be), as well as a dummy template for testing.   Who should we put as maintainer for this?  I would like to keep it around, since it's a very useful algorithm and likely will be the standard one used for final products, but it needs somebody to keep it working or at least enough of a push to get it to a testable state so others can make sure it works without breaking things.

we can bring this up in the next ASWG meeting

We have two new PHD students, I could ask if we might be interested in template based analysis

note there is still this PR to finish: it's been stalled for a while: #1170


Ghost is mispositioned on touch devices when parent has transform property applied in CSS

This is caused because of bug in Chromium (https://code.google.com/p/chromium/issues/detail?id=20574), when position:fixed doesn't work if parent is transformed. Since sortable's ghost element is using position:fixed on touch devices, it is positioned wrongly.
To reproduce, just use example in index.html and add this to .block {} in CSS
-webkit-transform: translate(0, 0);
transform: translate(0, 0);

@NeosinneR Your commit solved my issue on iPad.

@techntrails I'm also having a problem using Sortable with Ionic, though in my case the item that's being dragged (not the ghost) is mispositioned. I'm wondering if Ionic's bar header is interfering with the calculation of the 'top' property on the draggable item? I haven't been able to find many examples of people using this with Ionic, was just wondering if you'd had this issue.


Define and support template development process

[ ] Define local development process.
[ ] Define local testing process.
[ ] Define PR validation + automated test process. See #676 for requirements
[ ] #661
[ ] Guidance for sequencing azd dependencies and validation. Needs to be caught during PR validation when surfacing to azd template list.

Some questions I have related to templates:

Should a template define a version? (I think the current approach is to use git branches for versioning)
Should it be a template repository schema? A way to tell azd where to discover/pull templates from
Do we want to have the concept of official templates vs non-official templates ??  As a way to ensure flaky templates ?

Templates are versioned in azure.yaml

Related to #287


Add Vulnerability Assessment in SSMS gif to SSMS tips

https://docs.microsoft.com/en-us/sql/relational-databases/security/sql-vulnerability-assessment
Create separate images and gif from it using http://gifmaker.me.
Database: WorldWideImporters.

Closed via https://github.com/ktaranov/sqlserver-kit/pull/115


Git: Stage Changes (git.stageFile) doesn't seems to work

Git: Stage Changes
I tried to add a keybinding for "Git: Stage Changes" (git.stageFile) and use it to stage a file, but nothing happened

Does this issue occur when all extensions are disabled?: Yes

VS Code Version: 1.90.1 (611f9bfce64f25108829dd295f54a6894e87339d) x64
OS Version: Win10

Pre-requisite
Add a Keybinding for "Git: Stage Changes" (git.stageFile)
Steps to Reproduce:

Open a folder
Run git init in that folder
Create a new file
Open "Source Control" (Ctrl+Shift+G)
Tab (or use vim keybinding) to hover the file
Press the git.stageFile keybinding

=> The file is not staged

You can also:

Open a folder
Run git init in the folder
Create a new file
Open the file
Press the git.stageFile keybinding

=> The file is not staged
I don't know if I'm using the keybinding wrongly or if this is really a problem

The git.stageFile command is specific to the multi-file diff editor. The "+" action in the "Source Control" view executes the git.stage command. Having said that, the problem with executing a command using a keybinding is that no context (ex: the resource URI) is being passed to the command, hence the command exits silently as it does not have the necessary context information. I will see if there is anything that we an do in order improve this experience.


Does this work with React?

I'm trying to do something like:
import SVGInject from "@iconfu/svg-inject";

function Test() {
  return (
    <div>
             <img
                src={MySvg}
                onLoad={SVGInject(this)}
              />
    </div>
  );
}

Doesn't seem to be doing anything. I don't get an error, but the svg is still the same, and if I inspect it in console, it's still img instead of svg

I replaced the onLoad={SVGInject(this)} with onLoad={() => SVGInject(this)} and it still does nothing. The error in the console tells me no img element

Hello @joshuarobs
I try to do the same, did you find a solution ?
Thanks

@Audreymlgm Nope, I'm not using this repo and I'm just using the <svg>...</svg> html tag

Just to let you know that onLoad={(e) => SVGInject(e.srcElement)} did the trick for me.

Just to let you know that onLoad={(e) => SVGInject(e.srcElement)} did the trick for me.

That didn't work for me, but onLoad={(e) => SVGInject(e.target)} did.

Just to let you know that onLoad={(e) => SVGInject(e.srcElement)} did the trick for me.

That didn't work for me, but onLoad={(e) => SVGInject(e.target)} did.

thanks my bro, I searched a lot to solve this problem


Claude Desktop fails to connect to brave-search, other MCP work correctly

Describe the bug
I have setup 3 MCP Servers, Jetbrains, Memory and Brave Search. Both Jetbrains and memory work and Claude Desktop can use them. However for Brave it does not work.
To Reproduce
Steps to reproduce the behavior:

Add content to claude_desktop_config.json

{
  "mcpServers": {
    "jetbrains": {
      "command": "npx",
      "args": [
        "-y",
        "@jetbrains/mcp-proxy"
      ]
    },
    "memory": {
      "command": "npx",
      "args": [
        "-y",
        "@modelcontextprotocol/server-memory"
      ]
    },
    "brave-search": {
      "command": "npx",
      "args": [
        "-y",
        "@modelcontextprotocol/server-brave-search"
      ],
      "env": {
        "BRAVE_API_KEY": "REPLACE_WITH_YOUR_KEY"
      }
    }
  }
}

Restart Claude Desktop
Start new chat and ask "Can you search the web for latest news about Spring boot"
Claude says he cannot search the web

Expected behavior
As the other MCP Server work correctly I assume npx and MCP work correctly in general for my Claude Desktop, just the Brave MCP has an issue. So I that brave search MCP would work correctly and shows up as mcp tool and can be used.
Logs
mcp.log:
2024-12-17T15:01:56.213Z [info] Attempting to connect to MCP server jetbrains...
2024-12-17T15:01:56.215Z [info] Attempting to connect to MCP server memory...
2024-12-17T15:01:56.216Z [info] Attempting to connect to MCP server brave-search...
2024-12-17T15:01:56.235Z [info] Connected to MCP server jetbrains!
2024-12-17T15:01:56.242Z [info] Connected to MCP server memory!
2024-12-17T15:01:56.250Z [info] Connected to MCP server brave-search!
2024-12-18T07:23:36.662Z [info] Attempting to connect to MCP server jetbrains...
2024-12-18T07:23:36.666Z [info] Attempting to connect to MCP server memory...
2024-12-18T07:23:36.667Z [info] Attempting to connect to MCP server brave-search...
2024-12-18T07:23:36.704Z [info] Connected to MCP server brave-search!
2024-12-18T07:23:36.710Z [info] Connected to MCP server memory!
2024-12-18T07:23:36.716Z [info] Connected to MCP server jetbrains!

mcp-server-brave-search.log:
npm error code ENOENT
npm error syscall lstat
npm error path C:\Users\jolehm\AppData\Local\AnthropicClaude\app-0.7.5\${APPDATA}
npm error errno -4058
npm error enoent ENOENT: no such file or directory, lstat 'C:\Users\jolehm\AppData\Local\AnthropicClaude\app-0.7.5\${APPDATA}'
npm error enoent This is related to npm not being able to find a file.
npm error enoent
npm error A complete log of this run can be found in: C:\Users\jolehm\npm-cache\_logs\2024-12-18T07_23_37_019Z-debug-0.log

Additional context
I have:

Latest version of Claude Desktop
Windows 11
Node Version v20.18.1 (not using NVM)

did you fix?

can we please update the readme to tell people not to use the installer?


Rancher settings not allowing TLSv1.3 version or cipher suites

Rancher Server Setup

Rancher version: 2.6.3
Installation option (Docker install/Helm Chart): Docker install
Proxy/Cert Details: n/a

Information about the Cluster

Kubernetes version: RKE2 1.21.3
Cluster Type (Local/Downstream): Downstream

If downstream, what type of cluster? (Custom/Imported or specify provider for Hosted/Infrastructure Provider):

Imported = Running kubectl apply onto an existing k8s cluster

User Information

What is the role of the user logged in? Admin

Describe the bug
Receive an error when providing the TLS environment variables for TLSv1.3 described on the TLS Settings.
To Reproduce
TLS Minimum Version
Start the docker container with --env CATTLE_TLS_MIN_VERSION=1.3
TLS Ciphers
Start the docker container with --env CATTLE_TLS_CIPHERS=TLS_AES_256_GCM_SHA384
Result
TLS Minimum Version
Server fails to start and docker logs shows:
2022/01/06 16:08:59 [FATAL] failed to setup TLS listener: error while configuring minimal TLS version: invalid minimal TLS version [1.3], must be one of: 1.1 1.0 1.2

TLS Ciphers
Server fails to start and the docker logs shows:
2022/01/06 14:26:55 [FATAL] failed to setup TLS listener: error while configuring TLS ciphers: unsupported cipher [TLS_AES_256_GCM_SHA384], must be one or more from: TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256 TLS_RSA_WITH_3DES_EDE_CBC_SHA TLS_RSA_WITH_AES_128_GCM_SHA256 TLS_ECDHE_RSA_WITH_RC4_128_SHA TLS_ECDHE_RSA_WITH_3DES_EDE_CBC_SHA TLS_RSA_WITH_RC4_128_SHA TLS_RSA_WITH_AES_128_CBC_SHA TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305 TLS_RSA_WITH_AES_128_CBC_SHA256 TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305 TLS_RSA_WITH_AES_256_CBC_SHA TLS_RSA_WITH_AES_256_GCM_SHA384 TLS_ECDHE_ECDSA_WITH_RC4_128_SHA TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA

Expected Result
TLS Minimum Version
Server starts up and the minimum TLS version is set to 1.3.
TLS Ciphers
Server starts up and the only listed cipher in the settings is TLS_AES_256_GCM_SHA384
Screenshots
N/A
Additional context
Following the documentation which references the Golang tls constants.
Also note that the 2.6.3 version of  pkg/tls/base.go does not appear to have any of the TLS v1.3 constants added which appears to be where the errors are originating.

Thanks, we can merge this into https://github.com/rancher/rancher/issues/35654


docs build is failing

due to VERSION file change. see: http://readthedocs.org/projects/looper/builds/5087567/

Appears to be stabilized by https://github.com/epigen/looper/pull/67


readme: add deprecation notice.

As per subject.
This adds a deprecation notice to kinetic-devel.

Context: the announcement on ROS Discourse and ros-industrial/ros_industrial_issues#66.

Related: #364.


intermittent bad cert in the chain

---
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/9912968-intermittent-bad-cert-in-the-chain?utm_campaign=plugin&utm_content=tracker%2F85909&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F85909&utm_medium=issues&utm_source=github).

Where are you seeing this, @clone1018? In Chrome I have the "does not have public audit records" message if I drill down, but the address bar is still locked green. Opera is green. Firefox is locked gray.

Version 42.0.2311.39 beta (64-bit)
Which should be the next stable.

@clone1018 Are you sure the warning you're seeing is due to the audit records issue? That was also present on #3160 but wasn't why we were getting a broken lock.

What else do you want me to look for @whit537 ?

@clone1018 When you click "Certificate information" what do you see? Below is what I see. The problem on #3160 was that the signature algorithm was SHA-1 instead of SHA-256.

I'm on Chrome 43.0.2327.5 (Official Build) dev (64-bit) and while I get the public audit warning, the padlock is green for me,

Closing because not reproducible with a stable version of Chrome. Reopen if it happens once 42 is stable.

I'm still on a dev-build (45), but I tracked down the issue to a a sha1 starcom SSL certificate somewhere in the chain. Here is a screenshot of the Startcom SSL certificate in the chain with SHA1 as the signature algorithm:

This cert (StartCom) is valid till 10/25/17, 2:27:09 AM GMT+5:30, which is why Chrome gives the warning. The list of domains in the gratipay cert is:
DNS Name: 0nfx8fkf.gratipay.com
DNS Name: gratipay.com
DNS Name: www.gratipay.com
DNS Name: gittip.co
DNS Name: www.gittip.co
DNS Name: gittip.com
DNS Name: gittip.org
DNS Name: gratipay.co
DNS Name: gratipay.net
DNS Name: gratipay.org
DNS Name: www.gittip.com
DNS Name: www.gittip.org
DNS Name: www.gittip.com
DNS Name: www.gratipay.co
DNS Name: www.gratipay.org
DNS Name: www.gratipay.net

I am guessing that this is a configuration issue on Heroku side?

@captn3m0 Why do you think it's Heroku? Sounds like a StartCom/Chrome interaction to me.

I was guessing it must be a mis-configuration issue on Heroku's side because that intermediary cert is clearly wrong. I was thinking it might be using an old cert config, but that seems unlikely as well.

I haven't ever used Heroku custom SSL, so don't really know much here.

I believe we are responsible for uploading the intermediate certificate bundle to Heroku. I guess we're using an out-of-date chain?

Weird. I'm seeing a SHA-256 signature algorithm for the intermediate certificate:

I'm on Chrome 43.0.2357.132. What could explain the discrepancy?

It looks like the expiration timestamps differ as well.

Yes, I'm seeing green here as well for now. But once every few weeks this
gets red again because I get a sha1 cert in the chain.
On Fri 10 Jul, 2015 06:03 Chad Whitacre<EMAIL_ADDRESS>wrote:

It looks like the expiration timestamps differ as well.
—
Reply to this email directly or view it on GitHub
https://github.com/gratipay/gratipay.com/issues/3278#issuecomment-120181329
.

Blech. Reminds me of https://github.com/gratipay/gratipay.com/issues/1512 and https://github.com/gratipay/gratipay.com/issues/2586. :disappointed:

If this is indeed parallel to #1512 and #2586, then I interpret this bug as a result of leaky abstraction. We have so very little hope of getting to the bottom of this, because it seems to be a bug somewhere in AWS, and we're insulated even from that by Heroku. To my way of thinking, the way to resolve this class of bugs is to port to an architecture that we control more directly.

Yeah. Maybe file a support ticket with heroku?

We're seeing intermittent behavior—"once every few weeks"—where an out-of-date certificate is included in the chain for our SSL cert on https://gratipay.com/. The result is a broken trust indicator in Chrome. Here's our public ticket with more detail. How can we debug this?

https://help.heroku.com/tickets/251995

@captn3m0 One thing to check: do you have any StartCom root certificates in your system certificate chain? You might see two with the common name "StartCom Certification Authority", one as SHA-1 and the other as SHA-256. I'm not sure which OS you are on, but I'm trying to find if this post from the Chrome team is related. This certificate is issued under the SHA-1 root, so maybe it is taken that to mean insecure.
On Chrome 45/OSX I can't reproduce, so I wonder if it might related to your OS certs from this clause:

Note: SHA-1-based signatures for trusted root certificates are not a problem because TLS clients trust them by their identity, rather than by the signature of their hash.

I do have 3 StartCom certs in my system certificate chain. I'm on arch linux. Only one of the 3 certs is a SHA1 cert, but its not the one being referenced above. (all 3 have CA=true)
The one breaking the ssl is a sha1 intermediate cert.

Ok, after much digging around (using the cert's name) I think I have understood the issue.

http://serverfault.com/a/685089/78192

It's due to Windows' or Chrome's certificate cache. Because they (old and new intermediary cert) have the same name, the client will use the cached variant, which might be old and SHA1. The naming is StartCOM's fault. The bad caching is Windows' or Chrome's fault. They're not working very hard to fix it.

It makes perfect sense in my case because I'm very reluctant of clearing my browser cache. I copy my chrome profile over OS re-installs.
This thread on StartCom forums also has others facing the same issue.
Closing this issue as we can't really do anything about it for now.

Good debugging, @stevo550 @captn3m0, thanks.


Translations update from Hosted Weblate

Translations update from Hosted Weblate for Adaptive Lighting/Adaptive Lighting.
Current translation status:

@all-contributors please add @rVlad93  for translations


add and activate point robinson & sunset bay hydrophones

Updated documentation
Added two new hydrophones
Fixed small typos

@micya can you merge if we are ready

Thanks again for hacking with us @salsal97 ! Since the Sept Hackathon we've received at least one notification of a new candidates from Sunset Bay and many from Point Robinson...
...but can you or @micya explain how that is possible if this PR has not yet been merged?
My guess is that it was done manually (like you did with Point Robinson, Saloni, as an in-person tutorial for me and Dave)... but if so, this PR should still be merged so we get the improvements in documentation and the new .yml files, right?

Hi @scottveirs, glad it’s working fine!
So the code is in a container and already in kubernetes, even if the PR Isn’t necessarily merged. The docker container has a copy of it all and that’s how it’s working already. The container doesn’t refresh with every PR merge - refreshing it is a manual process.
So that part of the thread is already ahead, and merging the PR is definitely essential for future alignment with our new hydrophones. Since I don’t have permission to merge, I’d be dependent on either of you to make that final merge if this version of the PR looks good.

Apologies for the late reply. Thanks @salsal97 !

It might be useful to add some kind of GitHub pipeline to handle auto rollout based on committed yaml files. Maybe something for next hack?


Gazebo Polylines

Get latitudes and longitudes from Gazebo world coordinates and use them to make polylines for simulations. Will close #189 when finished.

Note that this issue also includes formalizing the way we generate coordinates in the gazebo coord system when creating worlds (like, we'd write the procedure down on a readme if its manual labor)

Yeah, I read the issue comments.


⚠ Bofrost.at has degraded performance

In 676e444, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 2632 ms

Resolved: Bofrost.at performance has improved in 53f2c38 after 6 minutes.


Tech debt: Increase code coverage - Part 1

JIRA link (if applicable)
https://tools.hmcts.net/jira/browse/PRL-4531
Change description
Does this PR introduce a breaking change? (check one with "x")
[ ] Yes
[ ] No

Testing complete no longer required


feat: add catppuccin as a new topic

Please confirm this pull request meets the following requirements:

[x] I followed the contributing guidelines: https://github.com/github/explore/blob/main/CONTRIBUTING.md.
[ ] I have no affiliation with the project I am suggesting (as a maintainer, creator, contractor, or employee).

Please note that I do maintain a few themes for the project

Which change are you proposing?

[ ] Suggesting edits to an existing topic or collection
[x] Curating a new topic or collection
[ ] Something that does not neatly fit into the binary options above

Curating a new topic or collection

[x] I've formatted my changes as a new folder directory, named for the topic or collection as it appears in the URL on GitHub (e.g. https://github.com/topics/[NAME] or https://github.com/collections/[NAME])
[x] My folder contains a *.png image (if applicable) and index.md
[x] All required fields in my index.md conform to the Style Guide and API docs: https://github.com/github/explore/tree/main/docs

I think that the catppuccin colorscheme should have its respective topic page, since the theme is rapidly growing.

Please note that I do maintain a few themes for the project

Sorry, we don't allow contributions from active maintainers, as per our contribution guidelines:

Maintainers of a project cannot add a topic or collection for their own project. If a topic is popular enough to warrant inclusion, someone else will add or improve it.

We do this so that we can maintain a high level of independence in this project, so that projects will be curated organically if there is enough support/activity in the community.
Thank you!

Ok


Horizontal lines not supported?

The following markdown caused a Error: Request failed with status code 400 when trying to sync to Confluence:
---
Thank you very much for creating this very nice project and have a lovely day
Lukas

Thanks for the report @LMarsoner :)
Turns out I simply needed to write self-closing tags in XHTML, not HTML 5 style. I wanna fix one or two things more and will then release a tag.

Thank you very much! :)
Have a lovely rest of the week


Compress requests / responses

Leverage gzip to compress requests / responses.

I'd be cautious about how this is implemented - for small payloads, the compression/decompression time might be a more significant cost than the network's speed.
Also for small payloads or ones without much repetition in their content, the compressed size might be larger than its uncompressed equivalent because of the dictionary's overheads.
There are probably some heuristics about what dictionary size to use and when to apply compression.


Support Map Type?

Not yet.
Have a quick look of the description of Map type.
For ClickHouse

Map(key, value) data type stores key:value pairs.
Parameters
key — The key part of the pair. String, Integer, LowCardinality, or FixedString.
value — The value part of the pair. String, Integer, Array, LowCardinality, or FixedString.

For Spark

MapType(keyType, valueType, valueContainsNull): Represents values comprising a set of key-value pairs. The data type of keys is described by keyType and the data type of values is described by valueType. For a MapType value, keys are not allowed to have null values. valueContainsNull is used to indicate if values of a MapType value can have null values.

As we don't support LowCardinality yet, other than that, the rest seem to be a good match overall.
You can expect this feature to be available in a week or two.
BTW, do you need the key support types other than String?

thx for reply，currently only string type key in our usage

Thanks for verification, because currently we use JSON for data serialization, key type other than String may cause unexpected behavior, will investigate it later.

@camper42 FYI, implemented.

thx


[WIP] JAMES-2586 Implement PostgresMailboxMessageDAO

jira https://issues.apache.org/jira/browse/JAMES-2586
resolve https://github.com/linagora/james-project/issues/4899

My concerns when implementing:

Should we need a PostgresMailboxMessage implement MailboxMessage, or try to SimpleMailboxMessage
Not sure about insert message flow now, we should upload content first (to get blob_id), or save the message first (without blob_id) and update later.
Should we create a separate test class for DAO, or the test will be done in MessageMapper?

->  try to SimpleMailboxMessage
-> we should upload content first, then save message entry, then save mailbox contexts.
-> I am not fan of DAO tests. If doable I prefer messageMapper tests

:white_check_mark: The PostgresMessageMapper test passed.

[ ] Now I will fix deep logic based on Benoit's comments

@vttranlina in mailbox_message table, lets...

Enforce that mailboxes exist
and cascade deletes

CF ChatGPT answer: mailbox_id UUID REFERENCES mailbox(mailbox_id) ON DELETE CASCADE
WDYT?
We could also enforce the mailbox_message message_id references an existing message...
CF message_id UUID REFERENCES message(message_id)

@vttranlina in mailbox_message table, lets...

Enforce that mailboxes exist
and cascade deletes

CF ChatGPT answer: mailbox_id UUID REFERENCES mailbox(mailbox_id) ON DELETE CASCADE
WDYT?
We could also enforce the mailbox_message message_id references an existing message...
CF message_id UUID REFERENCES message(message_id)

:+1: It will be more consistency

But should we worry about Maibox listener (case DELETE CASCADE), which works asynchronously?

You are right.
Let's just:
 mailbox_id UUID REFERENCES mailbox(mailbox_id)

what about this in this ticket? https://github.com/linagora/james-project/issues/4958#issuecomment-1829749045

Should be done as part of https://github.com/linagora/james-project/issues/4958 IMO. This work is huge already.


How To Get The Current Text ?

Hello ! first of all i want to thank you for this beautiful library.. i really love it!
so, i have 3 Fragments for searching, each one is connected to the SearchView from the root Activity, everything is working fine when the user writes something, what i want to do is to show items when an other Fragment starts based on the Query of the previous on.. i've managed to do that with an invisible TextView in the Root Activity.. it works but it's not the best of what i can achieve! so yeah is there anyway to retrieve the current text from the SearchView? something like getText() or something ?

You can consider writing a different service class for storing last query. Don't forget to initalize empty String there in order not to get NullPointerException.


Header Invariant Violation by default on iOS

I have gone through these following points

[x]   Check latest documentation: https://docs.nativebase.io/
[x]   Check for existing open/closed issues for a possible duplicate before creating a new issue: https://github.com/GeekyAnts/NativeBase/issues
[x]   Use the latest NativeBase release: https://github.com/GeekyAnts/NativeBase/releases
[]   Check examples from NativeBase KitchenSink https://github.com/GeekyAnts/NativeBase-KitchenSink
[]   For discussion purpose make use of NativeBase Slack: http://slack.nativebase.io/
[]   For queries related to theme, check Theme Variables from Docs and live NativeBase Theme Editor http://nativebase.io/customizer/

Issue Description

App crashing on startup. Found the Issue was the Header. I was testing an existing app after upgrading expo and Native Base. This is limited to my iPhone X. My android emulator works fine.
<Header>
  <Left/>
  <Body>
    <Title>[omited]</Title>
  </Body>
  <Right />
</Header>

node, npm, react-native, react and native-base version, expo version if used, xcode version

node/12.0.0
"expo": "^34.0.1"
"react": "16.8.3",
"react-native": "0.59.8",
"native-base": "2.13.4"

Expected behaviour
No crash
Actual behaviour
Crashses with the following error:
Invariant Violation: [25,"RCTView",171,{"backgroundColor":4283326034,"flexDirection":"row","paddingLeft":10,"paddingRight":10,"justifyContent":"center","paddingTop":42,"borderBottomWidth":0.3333333333333333,"borderBottomColor":4282339765,"height":"<<NaN>>","elevation":3,"shadowColor":4278190080,"shadowOffset":{"width":0,"height":2},"shadowOpacity":0.2,"shadowRadius":1.2,"top":0,"left":0,"right":0}] is not usable as a native method argument

Note "height":"<<NaN>>".
Steps to reproduce

Should crash on a clean install for iOS.
Is the bug present in both iOS and Android or in any one of them?
Only iOS
Any other additional info which would help us debug the issue quicker.
Setting height, <Header style={{height: 10}}> or example, resolves the issue.

This was similar to other issues but seemed deferent enough (hight specific) to deserve its own issue.

I seem to be getting this issue as far back as "native-base": "2.10.0". (though I know I tested this on iOS with a later version). This may be a configuration issue on my side but I would not know how to check. Advice?

I faced the same problem too, and based on https://github.com/GeekyAnts/NativeBase/issues/2603, setting the height of the <Header> works for me
<Header style={styles.header}/>
...
...
const styles = StyleSheet.create({
    header: {
      height: Platform.OS === 'ios' ? 90 : 50,
      paddingTop: Platform.OS === 'ios' ? 40 : 0,
      paddingBottom: Platform.OS === 'ios' ? 0 : 0,
    },
});

And remember to set the headerStyle for <Picker> if you use it
<Picker headerStyle={styles.header}>...</Picker>

Hope it helps ~

Thank you @timching! That was actually very helpful. Still a bug but I have now statically added that to all my headers and can push to production now.

@Sivli-Embir  I tried reproducing it but seems to work fine for me. Please check this. Am I missing something obvious?

I tried reproducing the issue but it seems to work fine for me. Please check this. Please let me know if I am missing something obvious.

@Sivli-Embir  I tried reproducing the issue but it seems to work fine for me. Please check this. Please let me know if I am missing something obvious.


Message text not line-wrapped on reply or forward

When replying to or forwarding a plain-text email with the two panel layout, the quoted email's lines are not line-wrapped, making it hard to read.
Can anybody else reproduce this bug?

I tried and I see it line-wrapped.  See below.

a screenshot would be good and a version number @davdavf. you can do the redacted stuff by Menu>Developer>Toggle Screenshot Mode
@nirmit you had this text on long lines, correct?
also @davdavf is it possible your nylas window was on the skinnier side? it's possible we have a min width supported for wrap before the content overflows

Yes, it’s one line of garbage text!
On Wed, Dec 13, 2017 at 10:05 PM Mike Seese<EMAIL_ADDRESS>wrote:

a screenshot would be good and a version number @davdavf
https://github.com/davdavf. you can do the redacted stuff by Menu>Developer>Toggle
Screenshot Mode
@nirmit https://github.com/nirmit you had this text on long lines,
correct?
also @davdavf https://github.com/davdavf is it possible your nylas
window was on the skinnier side? it's possible we have a min width
supported for wrap before the content overflows
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/nylas-mail-lives/nylas-mail/issues/180#issuecomment-351595110,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAaUJLa2JmhheutTpDecOnzTXxZPgmMuks5tAJBrgaJpZM4QuPwI
.

I'm on version 2.2.2. With quoted text, it doesn't wrap no matter how big the window.
Just had a look at the formatting rules with the help of Developer Tools, and it seems that while the normal email text has the rule "white-space: pre-wrap", the quoted plaintext replies are being displayed in monospace font and with "white-space: pre".
Could this be the issue?

Curious to know what theme are you using.
On Mon, Dec 18, 2017 at 4:25 PM davdavf<EMAIL_ADDRESS>wrote:

I'm on version 2.2.2. With quoted text, it doesn't wrap no matter how big
the window.
Just had a look at the formatting rules with the help of Developer Tools,
and it seems that while the normal email text has the rule "white-space:
pre-wrap", the quoted plaintext replies are being displayed in monospace
font and with "white-space: pre".
Could this be the issue?
[image: nylas-wrap]
https://user-images.githubusercontent.com/15054744/34128806-44f0ca90-e442-11e7-9572-322311780415.png
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/nylas-mail-lives/nylas-mail/issues/180#issuecomment-352562189,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAaUJJ0ziD_IJsXBdUO2OgsVHoLgrA6jks5tBthkgaJpZM4QuPwI
.

The standard Dark theme.


Empty codeblock appears when using mention with bold markdown

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

Action Performed:

Go to NewDot
Go to any chat with User B
First send a message that is bold in nature and which should be within backtick. For example : *hello*
Notice that the message is sent without any problem
Now follow the same process but in this case, mention the user B. For example :*<EMAIL_ADDRESS>Notice that nothing is displayed but if you try to edit it, you can see the whole text

Expected Result:
Mentioning user in bold format and within backticks should not behave weirdly and empty message should not be shown
Actual Result:
Mentioning user in bold format and within backticks behaves weirdly and empty message is shown (works well with the messages , problem is with the mentions only)
Workaround:
Can the user still use Expensify without this being fixed? Have you informed them of the workaround?
Platforms:

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

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

Version Number: 1.3.13
Reproducible in staging?: y
Reproducible in production?:
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
https://github.com/Expensify/App/assets/43996225/af1d1166-22ec-416d-9828-0e55d67dc12f
https://github.com/Expensify/App/assets/43996225/05511163-414a-4374-995c-b266615f6051
Expensify/Expensify Issue URL:
Issue reported by: @priya-zha
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1683802669770569
View all open jobs on GitHub

Proposal
Please re-state the problem that we are trying to solve in this issue.
Empty codeblock appears when mention with bold markdown inside codeblock
What is the root cause of that problem?
Codeblock is rendered in here, the content of text is props.defaultRendererProps.tnode.data
https://github.com/Expensify/App/blob/615ebd98c4b32affe2875712187d202a7dc64ab0/src/components/InlineCodeBlock/index.js#L12
https://github.com/Expensify/App/blob/615ebd98c4b32affe2875712187d202a7dc64ab0/src/components/InlineCodeBlock/index.native.js#L17

Mention without bold markdown inside codeblock. For example<EMAIL_ADDRESS>The html when is rendered of this message is : "<EMAIL_ADDRESS>After translation by react-native-render-html it is:

<TBlock>
  <TText>
<EMAIL_ADDRESS>  </TText>
</TBlock>

The children of codeblock is TText so that props.defaultRendererProps.tnode.data is the content that user enter.
2. Mention with bold markdown inside codeblock. For example: *<EMAIL_ADDRESS>The html when is rendered of this message is : "<EMAIL_ADDRESS>because bold markdown is disabled inside code markdown that is the rule replace of expensify-common. After translation by react-native-render-html it is:
<TBlock>
  <TPhrasing>
    <TText>
      *
    </TText>
    <TText>
<EMAIL_ADDRESS>    </TText>
    <TText>
      *
    </TText>
  </TPhrasing>
</TBlock>

The children of codeblock is TPhrasing that has threee TText children so that props.defaultRendererProps.tnode.data now is undefined, causing this issue.
What changes do you think we should make in order to solve the problem?
We could change the children of text from props.defaultRendererProps.tnode.data to <TNodeChildrenRenderer tnode={props.defaultRendererProps.tnode} /> to render exactly content for all case.
https://github.com/Expensify/App/blob/615ebd98c4b32affe2875712187d202a7dc64ab0/src/components/InlineCodeBlock/index.js#L12
https://github.com/Expensify/App/blob/615ebd98c4b32affe2875712187d202a7dc64ab0/src/components/InlineCodeBlock/index.native.js#L17
What alternative solutions did you explore? (Optional)

Proposal
Please re-state the problem that we are trying to solve in this issue.
Mentions within codeblocks are resulting in an empty codeblock displaying on the FE, despite the message correctly reaching the BE.
What is the root cause of that problem?
Mentions within codeblocks  are incorrectly being processed by ExpensiMark. You can see this in the HTML that is generated when sending the message `<EMAIL_ADDRESS>
This also happens for any additional text included in a codeblock, e.g. `hello<EMAIL_ADDRESS>will have the same result of an empty codeblock.
If we look at the regex used by the mentions in ExpensiMark, we can see that there's only handling for a codeblock with optional whitespace character(s) following it, see here or below:
regex: new<EMAIL_ADDRESS>'gm'),

There's an underlying issue that @dukenv0307's proposal highlights that is actually causing the codeblock to display as empty, but I don't think it's worth fixing as it's only happening because mentions are being rendered within the codeblock, which shouldn't be happening in the first place!
What changes do you think we should make in order to solve the problem?
The reason we're capturing the , etc. tags in the snippet above is so that we can check with isValidMention to ensure the mention isn't surrounded by any disallowed tags (like ). So we need to update the regex so that they handle codeblocks followed by any character, whilst also maintaining the behaviour that those HTML tags are pulled through for validation.
We can therefore change the regex (for both userMentions and hereMentions) here to this:
regex: new<EMAIL_ADDRESS>'gm'),

Changing the \s to the any character (*) regex ensures we can have any of those tags followed by any character.
I've also added a negative lookahead for the same tags as closing tags, so that we don't match other codeblocks within the message, e.g.: hi<EMAIL_ADDRESS>which would translate into hi<EMAIL_ADDRESS>That whole string would be matched and pulled into isValidMention which would fail as it checks for the validity of the first character in the match, see here).
What alternative solutions did you explore? (Optional)
We could also avoid the negative lookahead and use capture groups instead to pass the actual captured mention separately from the context (i.e. any HTML tags). Then in isValidMention we can check if the mention itself starts with a valid character, and separately check if it is surrounded by HTML tags.

I can't get the blank message.

@tjferriss you need start after * with "@" before email

@tjferriss Just to clarify, the string you need to enter is: `*<EMAIL_ADDRESS>(with the leading @ so that it's a mention). I am still able to repro on both production and main.

@tjferriss I am also able to reproduce.

Should be getting fixed in #18983


Update go version

go1.16 is not supported after go1.18 release.

At first I thought that we will keep in sync go versions of neofs-node and corresponding api-go / sdk-go libraries.
However it might not be necessary, because lib doesn't have to follow the same security concerns as application and it may benefit from long-time support for 3rd party apps. So we can avoid update until there will be explicit reasons for (performance \ security breach \ something else).

It's up to date now at 1.19.


What is this? Where to download the copy file, people ?!?!?!?!?!?!!!!

Issue in ./help/release/release-notes/open-source/2-4-6.md

Hello @aljumiai, the exact source of your frustration with the Magento Open Source 2.4.6 release notes isn’t clear to me. Is the issue that you don’t see a link that takes you directly to the 2.4.6 open source package? Installing and deploying Magento Open Source is a multi-phase procedure, and to carefully prepare merchants, we encourage them to first read the system requirements for running Magento Open Source so they can best prepare their environment before deployment. We also provide a link to the Quick start on-premises installation, which describes the installation process and instructions for accessing the software packages.
If this is not the source of your frustration, please add a note to this issue so I can respond more helpfully. I will close this issue in three days if you do not respond.


How to generate self-signed code-signing certificate

Let's add step-by-step guide describing how to generate self-signed code-signing certificate so I can link it in NuGet issue tracking signing command options.

Generating self-signed certificate with private key managed by CNG provider
Execute certmgr.msc command.

Select "Personal" store.
Righ-click anywhere in the right pane.
Select "All Tasks > Advanced Operations > Create Custom Request..." option from the context menu.

Click on "Next" button.

Select "Proceed without enrollment policy".
Click on "Next" button.

Select "(No template) CNG key" template.
Select "PKCS #10" request format.
Click on "Next" button.

Click on "Properties" button.

Select "Subject" tab.
In "Subject name" group select "Common name" type.
Enter "CNGTestCert" as value.
Click on "Add >" button.

Select "Extensions" tab.
Select "Key usage" group.
Select "Digital signature" option.
Click on "Add >" button.

Select "Extended Key Usage (application policies)" group.
Select "Code Signing" option.
Click on "Add >" button.

Select "Basic constraints" group.
Select "Enable this extension" option.

Select "Private Key" tab.
Select "Cryptographic Service Provider" group.
Select "RSA, Microsoft Software Key Storage Provider" option.

Select "Key Options" group.
Select "2048" key size.

Select "Select Hash Algorithm" group.
Select "sha256" hash algorithm.
Click on "OK" button.

Click on "Next" button.

Select any file name you want.
Click on "Finish" button.

Select "Certificate Enrollment Requests > Certificates" store.
Righ-click on "CNGTestCert".
Select "Cut" option from the context menu.

Select "Personal" store.
Righ-click anywhere in the right pane.
Select "Paste" option from the menu.

There is now self-signed certificate with private key managed by CNG provider present in your CurrentUser\My certificate store.

Generating self-signed certificate with private key managed by CAPI provider
Execute certmgr.msc command.

Select "Personal > Certificates" store.
Righ-click anywhere in the right pane.
Select "All Tasks > Advanced Operations > Create Custom Request..." option from the context menu.

Click on "Next" button.

Select "Proceed without enrollment policy".
Click on "Next" button.

Select "(No template) Legacy key" template.
Select "PKCS #10" request format.
Click on "Next" button.

Click on "Properties" button.

Select "Subject" tab.
In "Subject name" group select "Common name" type.
Enter "CAPITestCert" as value.
Click on "Add >" button.

Select "Extensions" tab.
Select "Key usage" group.
Select "Digital signature" option.
Click on "Add >" button.

Select "Extended Key Usage (application policies)" group.
Select "Code Signing" option.
Click on "Add >" button.

Select "Basic constraints" group.
Select "Enable this extension" option.

Select "Private Key" tab.
Select "Cryptographic Service Provider" group.
Deselect all selected options.
Select "Microsoft Enhanced RSA and AES Cryptographic Provider (Signature)" option.

Select "Key Options" group.
Select "2048" key size.

Select "Key type" group.
Select "Signature" option.
Click on "OK" button.

Click on "Next" button.

Select any file name you want.
Click on "Finish" button.

Select "Certificate Enrollment Requests > Certificates" store.
Righ-click on "CAPITestCert".
Select "Cut" option from the context menu.

Select "Personal > Certificates" store.
Righ-click anywhere in the right pane.
Select "Paste" option from the menu.

There is now self-signed certificate with private key managed by CAPI provider present in your CurrentUser\My certificate store.

Performing signing and verification operations
Create new console application targeting at least .NET Framework 4.6 and use both certificates (first one with private key managed by CNG provider and second one with private key managed by CAPI provider) to sign and verify some data:
using System;
using System.Security.Cryptography;
using System.Security.Cryptography.X509Certificates;
using System.Text;

namespace CryptoProvidersTest
{
    public static class Program
    {
        private static readonly byte[] _testData = Encoding.ASCII.GetBytes("Hello world!");

        public static void Main(string[] args)
        {
            // Find both CAPI and CNG certificates in CurrentUser\My store
            X509Store x509Store = new X509Store(StoreName.My, StoreLocation.CurrentUser);
            x509Store.Open(OpenFlags.ReadOnly);
            X509Certificate2 capiCert = x509Store.Certificates.Find(X509FindType.FindBySubjectName, "CAPITestCert", false)[0];
            X509Certificate2 cngCert = x509Store.Certificates.Find(X509FindType.FindBySubjectName, "CNGTestCert", false)[0];
            x509Store.Close();

            // Sign and verify some data with both CAPI and CNG certificates using the same code
            foreach (X509Certificate2 cert in new X509Certificate2[] { capiCert, cngCert })
            {
                if (cert.PublicKey.Oid.FriendlyName == "RSA")
                {
                    // Note: cert.GetRSAPrivateKey() is available since net46
                    RSA rsaPrivKey = cert.GetRSAPrivateKey();
                    byte[] signature = rsaPrivKey.SignData(_testData, HashAlgorithmName.SHA256, RSASignaturePadding.Pkcs1);

                    // Note: cert.GetRSAPublicKey() is available since net46
                    RSA rsaPubKey = cert.GetRSAPublicKey();
                    if (!rsaPubKey.VerifyData(_testData, signature, HashAlgorithmName.SHA256, RSASignaturePadding.Pkcs1))
                        throw new Exception("Signature is invalid");
                }
                else
                {
                    // Note: ECDSA keys can be supported with cert.GetECDsaPrivateKey() and cert.GetECDsaPublicKey() available since net461
                    throw new Exception("Unsupported type of private key");
                }
            }
        }
    }
}


Describe the release process in the contributing.md

Describe masterflow with tagged releases.

Tests passed here: https://travis-ci.org/github/CitrineInformatics/gemd-python/builds/678236350


test dist build

I think it would be nice to find a way to test the dist build, in a similar fashion to how I added CI dist build testing to react-recompose.
Prettier does this in a much more elaborate way when building new releases.

Done with a quick solution in ee7e71e7eb551aace5c286117e6f4cd87cb6d217


astropy.fits Too Many Files Open

Problem description
When I open too many fits files I get an error saying too many files open.

Expected behavior
I should be able to load an arbitrary number of fits files?

This issue is literally never ever going to happen again, so i'm closing it without fixing it.
NO ONE will ever do this.


Team 4   waves

Changes include adding difficulty and organising the mobs into specific waves. Most changes were made in WaveFactory, Forest Game Area and NPC Factory. Please note that it has not been cleaned up and any functions which had no usages but generated mobs were hashed out because of changes. All mob generating functions have had a health input added so the health can be changed for different waves. Because of this a number of tests have been hashed out, however this will be completed by us and will be done before the end of the sprint.
Request Changes: The fireboss has currently be changed out with the IceBoss. Splitting xenos have not been removed . The reason the frequency was different was because there were 2 types of xenos and only two mobs in the possible mob pool for each planet. As spliiting mobs has been removed this should now be more frequent. As for the bosses they occur every 5 waves. For wave 5 there is one boss, wave 10 2 bosses and 15 there are three bosses which is why you haven't seen them yet.

Hi sorry for any troubles, our PR was pushed before you guys (but you were before us) [sorry about that!] You'll need to merge main again (there shouldn't be many major conflicts except for MainGameArea)


arm64: support NVDIMM

As Arm64 is using the block device as the rootfs in guest. If we run two or more kata-container instances
on one host, we will get following error:
root@entos-thunderx2-desktop:~# docker run -dt --runtime kata-runtime ubuntu
7baf2c0f26100b0e642ad4122ce9ea1cb556fb3ed6cfcb454cb0586cbbe6194d
root@entos-thunderx2-desktop:~# docker run -dt --runtime kata-runtime ubuntu
2065fcf560c136091b5e69b6a12c95de94308309bb7fd5309df852503752203a
docker: Error response from daemon: OCI runtime create failed: qemu-system-aarch64: -device virtio-blk,drive=image-9f100592ac95eec6,scsi=off,config-wce=off: Failed to get "write" lock
Is another process using the image?: unknown.

Thanks to the new expanded IPA_SIZE feature in kernel 4.20 and Eric Auger's patch set ARM virt: Initial RAM expansion and PCDIMM/NVDIMM support in qemu(which are still under upstream review), we could fully support nvdimm on arm64.

I'm not triggering ARM CI here, since this pr needs to wait packaging/#377 landed firstly.

@jodh-intel @sboeuf already updated. ;) ptal

/test

/test

/test

Hi~ all. @grahamwhaley @jodh-intel @sboeuf a few sad news and one great news.
Great news is that ARM CI got green~~~
But I got dozens of build timeout in multiple x86_64 CIs, and it seems like a pattern to me. you may want to have a look. ;)
•Build timed out (after 5 minutes). Marking the build as aborted.
Build was aborted
Performing Post build task...
Match found for :.* : True
Logical operation result is TRUE
Running script  : #!/bin/bash

Hi @Pennyzct \o/ for the ARM CI :-)
The timeouts - yes, I think we have had a bunch of those overnight - I think it may be related to an image file/clearlinux update that happened - I think @chavafg and @jcvenegas are looking into it. Thanks for reporting!

/test
This looks to be very ARM specific, and the ARM CI is happy. We know the x86 ones had some wobbles overnight - I'm probably happy to merge this as is. @sboeuf wdyt?
I'll kick the CIs off again anyway, as the 'wobbles' should be fixed now - but we could force merge without waiting if we wanted...

@grahamwhaley I agree this is ARM specific, but the code being modified is in virtcontainers. There could be some unexpected relation with the common code that could cause some failures. I would feel more confident to merge this if we had at least our main jenkins-ci-ubuntu-18-04 job passing.

Fedora CI failed with:
not ok 32 ctr with non-root user has no effective capabilities

Fedora vsocks CI failed with:
docker: Error response from daemon: OCI runtime create failed: Failed to check if grpc server is working: context deadline exceeded: unknown.
And we have hit the max 20 containers
Checking 20 containers have all relevant components
Wrong number of shims running (20 != 19) - stopping
Wrong number of netmons running (20 != 19) - stopping
Wrong number of 'runtime list' containers running (20 != 19) - stopping
Wrong number of pods in /var/lib/vc/sbs (20 != 19) - stopping)
Showing system state:

Let's re-spin the wheels and see if the errors are consistent...

/test

/test

2 failing CI's are known issues, so merging...

Hi~@jodh-intel this pr is tested on ARM CI with the dependency of packaging#377, for now, packaging#377 hasn't been merged yet, I'm afraid ARM ci could break down.
But I see that packaging#377 has got all green, maybe could we merge it?? ;)

@Pennyzct - done ;)


Apex error DUPLICATE_VALUE, duplicate value found: dlrs__UniqueName__c

I have created multiple DLRS that are scheduled and have been working fine for several weeks but  just got an Apex error related to a DLRS:
Apex script unhandled trigger exception by user/organization: 005f4000000SSyf/00Df4000000m7L4
dlrs_TaskTrigger: execution of AfterInsert caused by: System.DmlException: Insert failed. First exception on row 0; first error: DUPLICATE_VALUE, duplicate value found: dlrs__UniqueName__c duplicates value on record with id: a2Rf4000001TMBA: []Class.dlrs.RollupService.updateMasterRollupsTrigger: line 1012, column 1
Class.dlrs.RollupService.handleRollups: line 919, column 1
Class.dlrs.RollupService.triggerHandler: line 311, column 1
Trigger.dlrs_TaskTrigger: line 7, column 1
The user referenced is a Portal Guest User.
The record with the duplicate UniqueName is a dlrs__LookupRollupSummary__c
I see this record shows it was created by an end user. I see that the configurations I have made are stored as MetaData and the Portal Guest User did not have permission to the dlrs.Lookup Rollup Summary Custom MetaData. It also doesn't have permissions to any of the DLRS Custom Objects.
The DLRS that caused the error Sums a field on Task and puts the result on Contact. I can't find any automation where a task could be created by Portal Guest User but it could update a contact.
I'm not sure how to reproduce this.

@climenhaga this looks like an issue fixed in the latest release - please review the release notes carefully. Let me know if this does not help.

@climenhaga - we were having this same issue with records being created by the guest user.  We had to the give the guest user profile "read" access to the DLRS objects in order to resolve the issue.

Duplicate of #375


"film_roll:moved" does not trigger : When Carousel width is more than all carousels combined

Hello,
"film_roll:moved"  does not trigger in following example :
http://codepen.io/Prashantsani/pen/emoXGO
Reason : The carousel width is more than the number of items in it.
But the same thing works in following example :
http://codepen.io/Prashantsani/pen/WbWmZY
Reason : carousel width is bigger than number of items in it.
Thanks.

I guess that doesn't hurt to fire that event. The thing is, nothing has moved. But I can see the value of having a single event fire in both instances. (I'll probably do it anyway, but it is worth thinking about.) Can you think of any situations where this would not be desirable?

Hey!
Thanks for the reply.
We have a thumbnail carousel, and whenever a new item triggers, we change the background and the text via ""film_roll:moved"".
So, i have edited my previous pens to show the effect that we have in our code, "film_roll:moved".
http://codepen.io/Prashantsani/pen/emoXGO
http://codepen.io/Prashantsani/pen/WbWmZY
(instead of "film_roll:moved"  we can also have something like "film_roll:change" )
Thanks,

That's true, we could add another event that would always happen.

Is there any workaround for this?
I have added the code for "film_roll:moved" in the click handler event.
Here is codepen :
http://codepen.io/Prashantsani/pen/WbBwPX
(it works fine.....but it fires twice, if the carousel width is smaller then number of items in it)

Fixed with 0.1.16


Windows Terminal Does Not Render 4-digit unicode.

Environment
Windows build number: Microsoft Windows [Version 10.0.18363.720]
Windows Terminal version (if applicable): 0.10.781.0

Any other software?
Git Bash: 4.4.23(1)-release (x86_64-pc-msys)
Mintty: 3.1.0 (x86_64-pc-msys)

Steps to reproduce

Install windows terminal.
Install git bash.
Use git bash in windows terminal.
Run echo -e '\u25B6'

Expected behavior
Expect to see (from running git bash in mintty):

Actual behavior

This is exactly what it looks like when bash isn't translating the escape code for you. How are you launching git bash?

@DHowett-MSFT Thanks for getting back to me.
Example 1 (the working example) is launched using the 'Git Bash', an executable at C:\Program Files\Git\git-bash.exe.
Example 2 is using windows terminal, with the following profile:
           {
                "guid": "{e4b90cc8-3358-4c53-bd74-bcc1c3cd9144}",
                "name": "Git bash",
                "commandline": "C:\\Program Files\\Git\\bin\\bash.exe",
                "hidden": false,
                "snapOnInput": true,
                "startingDirectory": "C:\\projects",
                "fontFace": "Fira Code",
                "colorScheme": "One Half Light",
                "cursorColor": "#000"
            }

I imagined that the 'bash' executable above would do the translation when running in windows terminal, but perhaps it is actually mintty which does it in the working example?

It's definitely bash that does the translation. Can you try changing your commandline from bash.exe to bash.exe -li?

Yes, that works now - thank you very much! I'm not sure at what point the login changes something to allow this, but I can look into that on my own.
Thanks.


Typings are messed up

When importing version 2.0.3, TypeScript types are completely messed up:

It's impossible to use Promises as returned methods. Taking one method as example: exists(options: any, callback?: any): void;. The documentation says that it can be used with Promises too (and it works), but the type definition shows return type as void.
Types are just wrong. In the same method, the JSDoc definition says that the first argument (options) is optional, but the method signature marks it mandatory.
The library uses any as type anywhere. Options dictionaries, callbacks, etc: these are things that should be explicitly typed.
The library still uses JSDoc types everywhere, which should be migrated to TypeScript definitions.

Add (getFiles)[https://github.com/googleapis/nodejs-storage/blob/master/src/bucket.ts#L1521] to the list. The signature is getFiles(query: GetFilesRequest, callback?: any): void; but the function returns a promise.

Almost all methods have wrong typings. I showed one just as example.

@welkie Thanks. Will do

@rraina Google appears to have disabled the built in types with recent versions of this package until they resolve the issues with them. Therefore, to override them, you'd just opt to use the latest version of of this package with the latest version of the @types package as well. Because I'm not affiliated with Google, I don't know when the issues will be resolved. I'm merely keeping track of their TypeScript efforts so I can reduce the number of dependencies my Node projects have.

Thanks Matt. I tried downloading 2.0.3 (the latest package on NPM at time of this writing) and the @types/google-cloud__storage": "^1.7.2”. However, the 2.0.3 package has a conflicting index.d.ts :/. Let me know if I am doing something wrong.
On Sep 21, 2018, at 1:19 PM, Matt Welke <notifications<EMAIL_ADDRESS>wrote:
@rrainahttps://github.com/rraina Google appears to have disabled the built in types with recent versions of this package until they resolve the issues with them. Therefore, to override them, you'd just opt to use the latest version of of this package with the latest version of the @typeshttps://github.com/types package as well. Because I'm not affiliated with Google, I don't know when the issues will be resolved. I'm merely keeping track of their TypeScript efforts so I can reduce the number of dependencies my Node projects have.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/googleapis/nodejs-storage/issues/384#issuecomment-423659233, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ABfM1JmtMAH1z8gizO_GqXiZ4Efi3Urzks5udUnfgaJpZM4WkfGP.

@rraina I can't reproduce that issue. I just created a test project (using the tsconfig file from Microsoft's TypeScript-Node-Starter repo) and it compiled properly when I invoked VS Code's default build task: https://github.com/welkie/node-storage-test

tried it with the latest<EMAIL_ADDRESS>and has the problem
const isExist = await storage.bucket(CLOUD_STORAGE_BUCKET_NAME || '')
        .file(filePath)
        .exists(undefined);

and I have this problem error TS1345: An expression of type 'void' cannot be tested for truthiness and when I check the typings, the method returns void...
starting typescript 3.1,  they have enforce this, so the older version of typescript might work https://github.com/Microsoft/TypeScript/issues/26262

getFiles() promise is fixed in #402
A released is planned ? Thanks!

@welkie Your repo doesn't have enough code to repro the issue.
Try adding this:
import { Storage } from "@google-cloud/storage";
async function listBuckets() {
    const storage = new Storage();
    const [buckets] = await storage.getBuckets();
    return buckets;
}

First the  storage.getBuckets(); call will be an error because of lack of parameters:
$ tsc
src/index.ts:7:29 - error TS2554: Expected 2 arguments, but got 0.

7     const [buckets] = await storage.getBuckets();
                              ~~~~~~~~~~~~~~~~~~~~

So no, it doesn't work to just include the types, because even in your own example, it's finding the local index.d.ts first. So 1.7.2 is entirely broken for TypeScript users.

@TimMensch Yeah I just tested that and I'm getting the same issue. It looks like any non-trivial code example will run into issues since they're currently bundling type declaration files side by side with their source code files:

That's going to be a problem and it looks like people will have to revert to older versions of @google-cloud__storage to a version with no type declaration files bundled at all, in order to get to a working state. We won't be updating the package in our TS projects at my work until this is resolved.

Unfortunately, we had to roll back to an earlier 1.x version of cloud storage.
Also, does not seem to be able to import the File type anymore.
Really hope those will get fixed so that we can use the latest.

I must be missing something. It seems that now the 2.x provides it own typing, that take precedence of @types/google-cloud__storage, which is a good step.
However, it feels that now the internal types are vastly different than the original @types/..., which i am not sure it is because the 2.x has a different API or just because the types were written from scratch.
The challenge, is that right now, I am not sure how to use 2.x, since all type check fail?
Anybody else using 2.x with TypeScript ?

We haven't moved to 2.x yet. But I see in the team's 2.1.0 release (https://github.com/googleapis/nodejs-storage/releases/tag/v2.1.0) that they "disable TypeScript as we continue to annotate the project with types". So it sounds like they're completely turning off the d.ts file generation for now. I tried updating my example project to 2.1.0 to test this, but they haven't published 2.1.0 to NPM yet. I'm hoping when they publish it, we can go back to using latest version without TypeScript issues.


[Operational Management] Add print-account command to CLI.

Motivation
This small PR adds the 'print-account' command to the management operator tooling. This will allow us to view the 'operator_account' and 'owner_account' held in storage, to better enable debugging.
Have you read the Contributing Guidelines on pull requests?
Yes.
Test Plan
Tested locally:
$ ./libra-operational-tool print-account --config config --account-name owner_account
f7d4dd491014f0d5bc98f90a286bc109
Related PRs
None.

Thanks, David! 😄 @bors-libra r=davidiw

:pushpin: Commit b331c8f has been approved by davidiw

:hourglass: Testing commit b331c8fb7bad16fba652f312ac7ddceb15c4da55 with merge 6fe3176e36517231fe2e056e3daccc4ddf76a98a...

:sunny: Test successful - checks-actions_land_blocking_test, checks-circle_commit_workflow
Approved by: davidiw
Pushing 6fe3176e36517231fe2e056e3daccc4ddf76a98a to master...


How to enable IGPU?

I need to use the IGPU for Metal compute, separately from the dGPU.
It looks like the default install has the IGPU disabled via the boot-args -disablegfxfirmware.   I've removed this, but the IGPU still doesn't show up as a Metal device, nor visible in System Report.  (I have the Intel graphics enabled in the BIOS.)
I see WEG listed in ioreg, but it's not matched?
    | +-o WhateverGreen  <class WhateverGreen, id 0x100000128, !registered, !matched, active, busy 0, retain 4>

Any tips to get the IGPU working?  I have seen that #12 references problems with wakeup, but with my 4K+2K+2K multi-monitor graphics I can't use sleep anyway #7.

HaC Mini version: 2.6
OSX version: 10.15.3
NUC model: NUC8i7HVK
Boot SSD model and protocol: EVO 970, m.2
Display port(s) used: 2xUSB-C, 1xDP
Display resolution(s): 4K, 2K, 2K
Any TB3 devices: none
Any USB devices: N/A

The flag doesn’t remove it. By default it’s enabled.

OK, I'll put that boot-arg back in.  My apologies.
Any other ideas as to why it doesn't show up?  (I've also looked at MTLCopyAllDevices() and only the dGPU is listed.)

Yeah it’s the same behavior as Mac mini. The igpu is “offline”. You can force it to show up in a few ways but I can’t remember how exactly. Try using the amd gpu option when running the hac mini installer.

Try using the amd gpu option when running the hac mini installer.

It looks like that replaces the graphics-related boot-args to shikigva=80 -radcodec.   Unfortunately, that didn't help.
I've learned that WEG defines an "offline" IGPU as one having no connectors:

If you use a discrete graphics card (AMD or NVIDIA), having integrated Intel graphics enabled is still useful, as it can be used in offline mode (also known as "empty framebuffer", 0 connectors) for hardware encoding and decoding of media files and so forth.

The default HaC-Mini config uses the ig-platform-id of 0x59120003, which is an "offline" configuration with zero connected displays (zero connectors).  That looks good to me.
I loaded a debug version of WEG and used the -wegdbg boot-arg, but didn't see anything obviously wrong on a verbose boot. (I used a camera to catch the output.  Is there a way to look at that in macOS? dmesg doesn't go that far back.)
iStat menu sees the UHD630, but the Metal Framework does not list it as an device, nor does it appear System Information under Hardware > Graphics/Displays.  I do see it in IORegistryExplorer, along with an associated IntelAccelerator.
Any other suggestions? :)


Move existing materials to FastConfigurable, delete old shaders

With the superior performance in the new FastConfigurable and growth of features there, all my older shaders should be removed:

BlinnPhongConfigurable
BlinnPhongConfigurableTransparent
LambertianConfigurable
LambertianConfigurableTransparent
StandardFast
UnlitConfigurable
UnlitConfigurableTransparent
UnlitNoDepthTest
VertexLitConfigurable
VertexLitConfigurableTransparent

And matierals using them moved to use FastConfigurable.

@dbastienMS I can look at updating the materials used throughout the toolkit test scenes and examples, but is there a strategy for removing the old shaders without breaking user materials based on the old shaders when they upgrade to the latest toolkit?

@thebanjomatic their materials will point to the old meta files - the only way I can think of to solve this is to have a script that rips through materials looking for ones that point to the old shaders and pointing them to the new one.  there's some work done on auto-migration in the editor script already.  depending on how well that works as you're converting, we can look into making that script or improving the auto-migration.  great question - this is a tricky but super important issue.

You know I think it's fine for them to manually move things over - they can keep using the existing shaders if they want, they just won't be present in the htk going forwards.

@dbastienMS is there a way to mark a shader as obsolete?

Only thing I could think of was to move its folder location. For Example:
// Very fast shader that uses the Unity lighting model.
// Compiles down to only performing the operations you're actually using.
// Uses material property drawers rather than a custom editor for ease of maintenance.

Shader "HoloToolkit/Obsolete/BlinnPhong Configurable"
{
    Properties
    {
...

Hah, I was just about to say the same thing!
I think either that approach or just removing them are both fine - if they're removed users moving from older HTK versions can still keep their old copies.

One small step at a time haha

@dbastienMS do you know anything about the UnlitTriplanar shaders?

I don't - theoretically a triplanar shader should be combining axial textures in world space but this one does not appear to be doing that.

Yeah it seems to be used in all sorts of materials that don't do what you'd think. I'm thinking of making that one obsolete too and switching them to the fast configurable too lol.

If it's a good replacement that'd be ideal - the fewer things the better!


Upgrade lodash to fix a security issue

Synk analysis flags lodash as having a security issue around
prototype pollution. This upgrades to the first version
that fixes this issue.
Resolves: https://github.com/dlmanning/gulp-sass/issues/775
Relates to: https://app.snyk.io/vuln/SNYK-JS-LODASH-567746
Relates to: https://app.snyk.io/vuln/SNYK-JS-LODASH-590103
Relates to: https://app.snyk.io/vuln/SNYK-JS-LODASH-608086
Relates to: https://app.snyk.io/vuln/SNYK-JS-LODASH-450202
Relates to: https://app.snyk.io/vuln/SNYK-JS-LODASH-73638
Relates to: https://app.snyk.io/vuln/SNYK-JS-LODASH-73639

The issue related to this will be solved in #802 by 0ccfa8b

Released in 4.1.1 so it's available without adopting a major version bump.


Use of private API in Walkthrough

OpenUI5 version: 1.66 (maybe even earlier)
In Step 27 of the Walkthrough  the API sap/base/util/UriParameters is used.
However according to the source, this module/API is private.

IMPORTANT: This is a private module, its API must not be used and is subject to change. Code other than the OpenUI5 libraries must not introduce dependencies to this module.

At the same time the only alternative jQuery.sap.util.UriParameters is part of the deprecated jQuery.sap namespace.

That's unfortunately true, yes. Regarding jQuery.sap.util.UriParameters and sap/base/util/UriParameters we got somehow stuck.
We considered to bring the new module more into the direction of the URLSearchParams api (namely, separate get and getAll) to latter be able to get rid of it completely. That's why we kept it private and reverted the deprecation of jQuery.sap.util.UriParameter. But we then struggled in the migration tooling with properly distinguishing between the two use cases and, even worse, the new module was unintentionally made public via the tutorials and WebIDE templates.
At that point, we decided to go on with the old route (deprecation + new module in its current form), but, ehem, somehow it went lost again.


realtive change returns 0.00 using GPU on neural-style example

I noticed this problem that when running the neural-style example, on gpu (gtx 760), the relative change returns 0.00 at epoch 0, right after loading the default images and variables, and stops. Running the same defaults on the cpu, works. This is running on windows. Has anyone come across with this before?
edit:
just checked this using a titan x in the same env, and has returned the same problem.
thanks
laszlo

@hjk41 There seems to be problems with running on windows under specific version

Thanks, I re-built it for win7, and it works as it should.