Kong DNS resolution issues on DC/OS

Summary
This is the same report as #3082, we're closing that one and creating this as we have more relevant information about our issue and that one is a little messy. We spent some time yesterday afternoon debugging out environment and Kong container.
Our Problem
We have some APIs running in our DC/OS cluster, and Kong serving them. After we trigger a deployment on the cluster, some of those API stop responding through Kong, but if we go directly to it, it works. And all the applications can still communicate between them and resolve DNS, only Kong is complaining and the applications it's complaining about aren't accessible through Kong.
Sometimes we can make things work again by restarting Kong and, when it don't start resolving again after the restart, we restart the application(s) whose address Kong is complaining so it will have it's DNS entry recreated/updated and Kong start resolving that address again.
Our Tests
We made some tests: we set up a few scripts in loop running inside Kong container do try to resolve DNS using dig and nslookup, trying to access other APIs using curl and accessing kong database. No problem was found:

The scripts were working fine, resolving names and communicating with the APIs and the database
The other services were communicating with each other and resolving DNS without problems
Services that don't go through Kong work fine
No DNS errors in Spartan or Mesos DNS logs
Kong still complaining:

2018/04/04 17:03:39 [error] 56#0: *5032 [lua] cluster_events.lua:356: [cluster_events] poll() threw an error: /usr/local/share/lua/5.1/pgmoon/init.lua:233: attempt to index local 'sock' (a nil value), context: ngx.timer
2018/04/04 17:03:44 [error] 57#0: *5244 lua entry thread aborted: runtime error: /usr/local/share/lua/5.1/pgmoon/init.lua:233: attempt to index local 'sock' (a nil value)
2018/04/04 17:02:07 [error] 54#0: *921 upstream timed out (110: Operation timed out) while reading response header from upstream, client: <IP_ADDRESS>, server: kong, request: "GET /<REDACTED> HTTP/1.1", upstream: "http://<IP_ADDRESS>:9000/<REDACTED>", host: "<REDACTED>"
2018/04/04 17:02:07 [error] 54#0: *921 [lua] balancer.lua:781: balancer_execute(): [dns] dns server error: 100 cache only lookup failed. Tried: (short)figs-workbench-dashboard:(na) - cache-miss
figs-workbench-dashboard.marathon.l4lb.thisdcos.directory:1 - cache only lookup failed/dns server error: 100 cache only lookup failed

Then we tried to play with Kong DNS options:

KONG_DNS_STALE_TTL=120
KONG_DNS_ORDER=A
KONG_DNS_NOT_FOUND_TTL=1
KONG_DNS_NO_SYNC=on

But the same error happened using these four settings with different values/combinations.
Steps To Reproduce

On your DC/OS cluster spin up Kong container
Launch a few APIs in the cluster and create them in Kong without any plugin or consumer
Start a deployment of one service inside the DC/OS cluster
Some of the APIs that go through Kong stop responding and Kong has problems resolving DNS:
throwing cache only lookup errors and upstream timeout errors (but if you go to Kong container command prompt and try to reach the same address, it's ok)

Additional Details & Logs

Kong version (0.13.0)
Using Kong official docker image inside DC/OS
DC/OS 1.10
DNS TTL: 5s (Spartan + Mesos DNS)
Kong container CMD: export KONG_NGINX_DAEMON="off" && kong migrations up && kong prepare -p /usr/local/kong/ && /usr/local/openresty/nginx/sbin/nginx -c /usr/local/kong/nginx.conf -p /usr/local/kong/

/etc/resolv.conf
# Generated by gen_resolvconf.py. Do not edit.
# Change configuration options by changing DC/OS cluster configuration.
# This file must be overwritten regularly for proper cluster operation around
# master failure.

options timeout:1
options attempts:3

search marathon.l4lb.thisdcos.directory l4lb.thisdcos.directory marathon.mesos cv.vpc
nameserver <IP_ADDRESS>
nameserver <IP_ADDRESS>
nameserver <IP_ADDRESS>

/etc/hosts
<IP_ADDRESS>	localhost
::1	localhost ip6-localhost ip6-loopback
fe00::0	ip6-localnet
ff00::0	ip6-mcastprefix
ff02::1	ip6-allnodes
ff02::2	ip6-allrouters
<IP_ADDRESS>	f77e2b6d5aad

Sample API definition
{
	"created_at":<PHONE_NUMBER>000,
	"strip_uri": true,
	"id": "cc924892-9914-46e8-b2e8-7304ecd8ff6f",
	"hosts": ["<redacted>"],
	"name": "EventsDashboard",
	"http_if_terminated": false,
	"https_only": false,
	"retries": 5,
	"preserve_host": true,
	"upstream_connect_timeout": 6000,
	"upstream_read_timeout": 9000,
	"upstream_send_timeout": 6000,
	"upstream_url": "http://figs-workbench-dashboard:9000"
}

Kong Logs

2018/04/04 17:03:39 [error] 56#0: *5032 [lua] cluster_events.lua:356: [cluster_events] poll() threw an error: /usr/local/share/lua/5.1/pgmoon/init.lua:233: attempt to index local 'sock' (a nil value), context: ngx.timer
2018/04/04 17:03:44 [error] 57#0: *5244 lua entry thread aborted: runtime error: /usr/local/share/lua/5.1/pgmoon/init.lua:233: attempt to index local 'sock' (a nil value)
stack traceback:
coroutine 0:
	/usr/local/share/lua/5.1/pgmoon/init.lua: in function 'keepalive'
	/usr/local/share/lua/5.1/kong/dao/db/postgres.lua:354: in function 'query'
	/usr/local/share/lua/5.1/kong/dao/db/postgres.lua:184: in function 'clear_expired_ttl'
	/usr/local/share/lua/5.1/kong/dao/db/postgres.lua:218: in function </usr/local/share/lua/5.1/kong/dao/db/postgres.lua:213>, context: ngx.timer
2018/04/04 17:03:44 [error] 54#0: *5248 lua entry thread aborted: runtime error: /usr/local/share/lua/5.1/pgmoon/init.lua:233: attempt to index local 'sock' (a nil value)
stack traceback:
coroutine 0:
	/usr/local/share/lua/5.1/pgmoon/init.lua: in function 'keepalive'
	/usr/local/share/lua/5.1/kong/dao/db/postgres.lua:354: in function 'query'
	/usr/local/share/lua/5.1/kong/dao/db/postgres.lua:184: in function 'clear_expired_ttl'
	/usr/local/share/lua/5.1/kong/dao/db/postgres.lua:218: in function </usr/local/share/lua/5.1/kong/dao/db/postgres.lua:213>, context: ngx.timer
2018/04/04 17:03:44 [error] 53#0: *5252 lua entry thread aborted: runtime error: /usr/local/share/lua/5.1/pgmoon/init.lua:233: attempt to index local 'sock' (a nil value)
stack traceback:
coroutine 0:
	/usr/local/share/lua/5.1/pgmoon/init.lua: in function 'keepalive'
	/usr/local/share/lua/5.1/kong/dao/db/postgres.lua:354: in function 'query'
	/usr/local/share/lua/5.1/kong/dao/db/postgres.lua:184: in function 'clear_expired_ttl'
	/usr/local/share/lua/5.1/kong/dao/db/postgres.lua:218: in function </usr/local/share/lua/5.1/kong/dao/db/postgres.lua:213>, context: ngx.timer
2018/04/04 17:03:44 [error] 58#0: *5258 lua entry thread aborted: runtime error: /usr/local/share/lua/5.1/pgmoon/init.lua:233: attempt to index local 'sock' (a nil value)
stack traceback:
coroutine 0:
	/usr/local/share/lua/5.1/pgmoon/init.lua: in function 'keepalive'
	/usr/local/share/lua/5.1/kong/dao/db/postgres.lua:354: in function 'query'
	/usr/local/share/lua/5.1/kong/dao/db/postgres.lua:184: in function 'clear_expired_ttl'
	/usr/local/share/lua/5.1/kong/dao/db/postgres.lua:218: in function </usr/local/share/lua/5.1/kong/dao/db/postgres.lua:213>, context: ngx.timer
2018/04/04 17:03:44 [error] 52#0: *5266 lua entry thread aborted: runtime error: /usr/local/share/lua/5.1/pgmoon/init.lua:233: attempt to index local 'sock' (a nil value)
stack traceback:
coroutine 0:
	/usr/local/share/lua/5.1/pgmoon/init.lua: in function 'keepalive'
	/usr/local/share/lua/5.1/kong/dao/db/postgres.lua:354: in function 'query'
	/usr/local/share/lua/5.1/kong/dao/db/postgres.lua:184: in function 'clear_expired_ttl'
	/usr/local/share/lua/5.1/kong/dao/db/postgres.lua:218: in function </usr/local/share/lua/5.1/kong/dao/db/postgres.lua:213>, context: ngx.timer
2018/04/04 17:03:46 [error] 54#0: *3944 upstream timed out (110: Operation timed out) while reading response header from upstream, client: <IP_ADDRESS>, server: kong, request: "GET /<REDACTED> HTTP/1.1", upstream: "http://<IP_ADDRESS>:9000/<REDACTED>", host: "<REDACTED>"
2018/04/04 17:03:46 [error] 54#0: *3944 [lua] balancer.lua:781: balancer_execute(): [dns] dns server error: 100 cache only lookup failed. Tried: (short)figs-workbench-dashboard:(na) - cache-miss
figs-workbench-dashboard.marathon.l4lb.thisdcos.directory:1 - cache only lookup failed/dns server error: 100 cache only lookup failed
figs-workbench-dashboard.l4lb.thisdcos.directory:1 - cache only lookup failed/dns server error: 100 cache only lookup failed
figs-workbench-dashboard.marathon.mesos:1 - cache only lookup failed/dns server error: 100 cache only lookup failed
figs-workbench-dashboard.cv.vpc:1 - cache only lookup failed/dns server error: 100 cache only lookup failed
figs-workbench-dashboard:1 - cache only lookup failed/dns server error: 100 cache only lookup failed
 while connecting to upstream, client: <IP_ADDRESS>, server: kong, request: "GET /<REDACTED> HTTP/1.1", upstream: "http://<IP_ADDRESS>:9000/<REDACTED>", host: "<REDACTED>"

This is still very similar to #3082. There seem to be multiple issues mixed here.
See this response here. It is no longer a 500 since the bug of using the say method in the balancer_by_lua context has been fixed in 0.13 which you are now using. Also we can see better dns debug info being displayed, which was also added.
So I see 3 issues:

a problem with the postgres driver (pgmoon) trying to work with some socket that seems unavailable: attempt to index local 'sock' (a nil value)
an upstream connection that times out upstream timed out (110: Operation timed out) while reading response header from upstream
a DNS error, cache only lookup failed, which is a logical consequence of the previous timeout.

as for nr 3 above, see the comment I linked to above, it is a retry, but due to timings the dns data is not available (anymore) and the resolver cannot resolve because it is in the balancer_by_lua context where no sockets are available. The only viable thing to do here is to extend the stale_ttl setting to be longer than the timeout on the upstream-connection.
The nr 2 really seems an upstream service problem. Apparently Kong was able to connect, and then send the request, but now times out while waiting for the service to respond.
And the nr 1 is something to look into.

@protetore can you post the full logs from system start?

@protetore do you have any updates on this issue?

Hi guys, sorry about the delay.
We're trying to figure out by ourselves and see if there is some problem with some cluster component.
We don't have any definitive answer yet, but it seems that the problem is related to the DC/OS layer 4 load balancer. In our last test the problem only happened with services that were using a load balanced address.
Although the nslookups inside Kong container and the services containers never fails (there is no change in the DNS when a deploy happens, it's using the same load balancer address), Kong throw those errors I mentioned above.
Maybe the upstream stops responding for a fraction of time during deployment and it triggers some Kong behavior, and Kong keeps throwing errors for many minutes until it recovers by itself or it recovers when we restart the container.
There is any other setting worth of trying, at least to try to make it recover faster?
I'm thinking about closing this issue until we test another LB and reopen after the tests if we can't find any error on our side.

@protetore Hi,
Any news in your investigation?

Just as an update. The issue was addressed by mesosphere.

@grillorafael thx for the feedback!

I'm facing the same issue with Kong 1.1.1/Kubernetes 1.13.3:
<IP_ADDRESS> - - [12/Jun/2019:06:17:31 +0000] "GET /ControlCenter/World.asmx/GetList?GameCenterKey=Local HTTP/1.1" 500 40 "-" "Apache-HttpClient/4.5.5 (Java/1.8.0_191)"
2019/06/12 06:17:31 [error] 42#0: *18053500 upstream timed out (110: Operation timed out) while reading response header from upstream, client: <IP_ADDRESS>, server: kong, request: "GET /ControlCenter/World.asmx/GetList?GameCenterKey=Local HTTP/1.1", upstream: "http://<IP_ADDRESS>:80/World.asmx/GetList?GameCenterKey=Local", host: "it.oa.com"
2019/06/12 06:17:31 [error] 42#0: *18053500 [lua] balancer.lua:822: balancer_execute(): [dns] dns server error: 100 cache only lookup failed. Tried: ["(short)control-center.dbcode:(na) - cache-miss","control-center.dbcode.kong.svc.cluster.local:33 - cache only lookup failed/dns server error: 100 cache only lookup failed","control-center.dbcode.svc.cluster.local:33 - cache only lookup failed/dns server error: 100 cache only lookup failed","control-center.dbcode.cluster.local:33 - cache only lookup failed/dns server error: 100 cache only lookup failed","control-center.dbcode.q1lan.k8s:33 - cache only lookup failed/dns server error: 100 cache only lookup failed","control-center.dbcode:33 - cache only lookup failed/dns server error: 100 cache only lookup failed","control-center.dbcode.kong.svc.cluster.local:1 - cache only lookup failed/dns server error: 100 cache only lookup failed","control-center.dbcode.svc.cluster.local:1 - cache only lookup failed/dns server error: 100 cache only lookup failed","control-center.dbcode.cluster.local:1 - cache only lookup failed/dns server error: 100 cache only lookup failed","control-center.dbcode.q1lan.k8s:1 - cache only lookup failed/dns server error: 100 cache only lookup failed","control-center.dbcode:1 - cache only lookup failed/dns server error: 100 cache only lookup failed","control-center.dbcode.kong.svc.cluster.local:5 - cache only lookup failed/dns server error: 100 cache only lookup failed","control-center.dbcode.svc.cluster.local:5 - cache only lookup failed/dns server error: 100 cache only lookup failed","control-center.dbcode.cluster.local:5 - cache only lookup failed/dns server error: 100 cache only lookup failed","control-center.dbcode.q1lan.k8s:5 - cache only lookup failed/dns server error: 100 cache only lookup failed","control-center.dbcode:5 - cache only lookup failed/dns server error: 100 cache only lookup failed"] while connecting to upstream, client: <IP_ADDRESS>, server: kong, request: "GET /ControlCenter/World.asmx/GetList?GameCenterKey=Local HTTP/1.1", upstream: "http://<IP_ADDRESS>:80/World.asmx/GetList?GameCenterKey=Local", host: "it.oa.com"
2019/06/12 06:17:31 [error] 42#0: *18053500 [lua] init.lua:613: balancer(): failed to retry the dns/balancer resolver for control-center.dbcode' with: dns server error: 100 cache only lookup failed while connecting to upstream, client: <IP_ADDRESS>, server: kong, request: "GET /ControlCenter/World.asmx/GetList?GameCenterKey=Local HTTP/1.1", upstream: "http://<IP_ADDRESS>:80/World.asmx/GetList?GameCenterKey=Local", host: "it.oa.com"

Not the same context ,but same problem having the same problem trying to proxy a file from an aws s3 bucket behind kong and getting the exact same dns resolution failures. if I curl the file in the container kong is running in it downloads it just fine, but kong just hangs on it

@rhorv please not not comment on closed issues, please open a new one and add the relevant input for us the look into it.


feat(sync): Add wait for task with requests options

Changes Unknown when pulling 141cb6704f83bded12a2095951cf85c7f7302062 on feat/wait_task_options into ** on master**.


Provide OWASP CRS version info

We have been testing the "Microsoft_DefaultRuleSet_1.1" managed rules, and seems there's quite a few false positives for us.  For example, rule 942330 is blocking cookies with valid JSON payloads.  Based on CRS Issue 693, rule 942330 is disabled by default in version 3.x, however this isn't the case with "Microsoft_DefaultRuleSet_1.1".
It would be good to know what CRS version WAF is using in order to know how the rule is being used and if there are current issues with the version / rule.  I wasn't able to find this information anywhere in the docs or in Azure.

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

ID: d38eb998-6925-5ab2-ad2c-4367a7c22895
Version Independent ID: 0e0590c0-42d5-c5a3-86b6-2d396a43cf19
Content: Tuning Web Application Firewall (WAF) for Azure Front Door
Content Source: articles/web-application-firewall/afds/waf-front-door-tuning.md
Service: web-application-firewall
GitHub Login: @mohitkusecurity
Microsoft Alias: mohitku

@aapalm , thank you for your question. We'll review this and get back to you shortly!

@aapalm , thank you for your feedback. We have assigned this issue to the respective product owner for review.
@mohitkusecurity , Could you please provide your insights here?

@aapalm @GitaraniSharma-MSFT -
Regarding Based on CRS Issue 693, rule 942330 is disabled by default in version 3.x, however this isn't the case with "Microsoft_DefaultRuleSet_1.1".  We are investigating this with the PG and will provide a response.
In the meantime, here are a couple of things to be aware of -

"Microsoft_DefaultRuleSet_1.1" is a customized version of CRS 3.1 and not exactly the same as the original ruleset
The out of box rules in WAF are pretty strict and may block legitimate traffic for some applications.  It is expected that you will need to tune the WAF for any false positives using Exclusions and Custom Rules

@ccmartins - Copying Camila for awareness.

Hello @aapalm
The managed rules in Azure WAF's Default Rule Sets are there by design. For the specific example of rule 942330, we designed it to be part of the managed rule set, and customers can choose to disable them (or not). It is just not disabled by default in our WAF - as customers should assess each rule and then make the decision to disable them.
As for the availability of information in regards to how the rule is being used (details on the rules' signatures), we purposely do not expose this information for security reasons. Such level of detail can provide attackers with an understanding of how to manipulate requests and evade the logic of the rules.

We have an interesting issue relating to this and would like to know more for our own sanity. Azure FD WAF Microsoft_DefaultRuleSet-1.1-XSS-941101 is triggering on URLs which have filenames beginning with "onedrive". We have employee html pages about onedrive and they all trigger a block because of a referrer URL containing a query param. If we access the link direct (without a referrer) it passes. If the filename is called something else not containing "onedrive", it passes.
Thoughts?

@PbALpi7xEX Rule 941101 in fact looks at the referrer header as you're stating, as you can see here. It then compares the value against the "detectXSS" operator which is based on libinjection and likely the cause of the match, but it is hard to pin-point why (or if) it's triggering on the "onedrive" value.
Since our AFD WAF offering is based on open source CRS but it does have some of our own modifications, I suggest you get support involved to find out why this is happening exactly within our service. You probably know this, but false positives can often happen. So, if this is legitimate traffic, you could fine tune the WAF with an exclusion as explained here.

Thank you for your dedication to our documentation.
Unfortunately, we have been unable to review this issue in a timely manner. We sincerely apologize for the delayed response. We are closing this issue. If you feel that the problem persists, please respond to this issue with additional information.
Please continue to provide feedback about the documentation. We appreciate your contributions to our community.
#please-close


make precommit error

Seems that I just can't get pylint successfully installed in build/bin when running make precommit.
Here's a part of the log:
Running setup.py install for lazy-object-proxy
`warning: no directories found matching 'examples'`
`warning: no files found matching '.isort.cfg'`
`warning: no previously-included files matching '*.py[cod]' found anywhere in distribution`
`warning: no previously-included files matching '__pycache__' found anywhere in distribution`
`warning: no previously-included files matching '*.so' found anywhere in distribution`
`warning: no previously-included files matching '*.dylib' found anywhere in distribution`
`building 'lazy_object_proxy.cext' extension`
`x86_64-linux-gnu-gcc -pthread -fno-strict-aliasing -DNDEBUG -g -fwrapv -O2 -Wall -Wstrict-prototypes -fPIC -Isrc/lazy_object_proxy -I/usr/include/python2.7 -c src/lazy_object_proxy/cext.c -o build/temp.linux-x86_64-2.7/src/lazy_object_proxy/cext.o`
`x86_64-linux-gnu-gcc -pthread -shared -Wl,-O1 -Wl,-Bsymbolic-functions -Wl,-Bsymbolic-functions -Wl,-z,relro -fno-strict-aliasing -DNDEBUG -g -fwrapv -O2 -Wall -Wstrict-prototypes -D_FORTIFY_SOURCE=2 -g -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security build/temp.linux-x86_64-2.7/src/lazy_object_proxy/cext.o -o build/lib.linux-x86_64-2.7/lazy_object_proxy/cext.so`

Successfully installed pylint configparser backports.functools-lru-cache six isort mccabe astroid wrapt lazy-object-proxy
Cleaning up...
/bin/sh: 1: build/bin/pylint: not found

Thanks for reporting this! I've had lots of problems with pip and pylint. I'm thinking I need to bundle a fixed version of pylint in third_party instead of relying on system pip.

So if I want to do a pull request, what should I do?Just running "make test" instead?

make precommit is the equivalent of make cover gofmt golint pylint test so if you want to skip pylint but do the rest you can do:
make cover gofmt golint test

Got it! Thanks!

This may have been fixed in https://github.com/google/grumpy/pull/143
Let me know if it helps.

I think it works now. Thanks!

Thanks for the confirmation. Closing for now. Reopen if it recurs.


what is the minimum memory required for the GPU

When I use the nvidia 3090  GPU (Memory 24576M) to run the “EfficientSAM_segment_everything_example” code, the model used is vitt,  GRID_SIZE = 32， which indicates that the graphics card memory is not enough and cannot run。
when I adjust parameter 32 to 16, it can be run but the segment effect is not good

Hey Hello, I also encountered this problem, how did you solve it, or what model did you use, can you recommend it?


Redundant public key in ed25519 private key

The private key bytes already includes the public key. However, we append it on again. Steps to fix:

Fix parsing keys without this additional public key copy appended.
Stop producing keys with the key appended.

Fixed.


Add DevConf talk to presentations list

Current State of the Meshery.io site
List of presentations - https://meshery.io/talks-and-presentations

Contributor Resources
The meshery.io website uses Jekyll and GitHub Pages. Site content is found under the master branch.

See the Contributing to Meshery.io Website section of the readme.md and other contributing instructions, too.
See Meshery site designs in this Figma designfile. Fill-in the Layer5 Community Member Form and join the Layer5 Community Slack for access.

Should I work on this Issue @leecalcote ?

Hey @ashutosh887
This needs the access to slides and talks as well, I am working on this one 👀
Please fell free to take a look at some other issues if interested and lmk if you want to work on any of them, I'll assign it to you (if it is unassigned though 😶 )


CFFL

CFFL

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_7476x4zfrt/clone/recipe/meta.yaml:15: pip_install_args: pip install should be run with --no-deps.
ERROR: /tmp/abs_7476x4zfrt/clone/recipe/meta.yaml:21: missing_wheel: For pypi packages, wheel should be present in the host section
ERROR: /tmp/abs_7476x4zfrt/clone/recipe/meta.yaml:41: missing_pip_check: For pypi packages, pip check should be present in the test commands
ERROR: /tmp/abs_7476x4zfrt/clone/recipe/meta.yaml:50: invalid_url: https://gsuitedevs.github.io/PyDrive/docs/build/html/index.html : Not reachable: 404
WARNING: /tmp/abs_7476x4zfrt/clone/recipe/meta.yaml:51: missing_description: The recipe is missing a description
Errors were found

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_72yljcbkpf/clone/recipe/meta.yaml:15: pip_install_args: pip install should be run with --no-deps.
ERROR: /tmp/abs_72yljcbkpf/clone/recipe/meta.yaml:21: missing_wheel: For pypi packages, wheel should be present in the host section
ERROR: /tmp/abs_72yljcbkpf/clone/recipe/meta.yaml:41: missing_pip_check: For pypi packages, pip check should be present in the test commands
ERROR: /tmp/abs_72yljcbkpf/clone/recipe/meta.yaml:50: invalid_url: https://gsuitedevs.github.io/PyDrive/docs/build/html/index.html : Not reachable: 404
WARNING: /tmp/abs_72yljcbkpf/clone/recipe/meta.yaml:51: missing_description: The recipe is missing a description
Errors were found


CNDB-8187 Add metrics about time spent writing sstables (compaction and flush) and support tracking SAI build time

Add new table and keyspace metrics to track the time spent in SSTables writing (both compaction and flush).
Add a new table metric with the time spent on writing SAI

New Table and Keyspace metrics:
Histogram flushTime
Histogram  storageAttachedIndexWritingTime
Histogram  compactionTime

storageAttachedIndexWritingTime is the time spent in "StorageAttachedIndexWriter#addRow"
For MemTable flush:

flushTime is the total time
storageAttachedIndexWritingTime is always smaller than flushTime

For Compaction:

compactionTime is the total time
storageAttachedIndexWritingTime is always smaller than compactionTime

The index part is to be reworked, because during compaction with build the indexes and we have to track the time spent while adding the rows (addRow)
https://github.com/datastax/cassandra/blob/338902ce0849e2e6f9b11a689a9c478e0b20ad6c/src/java/org/apache/cassandra/index/sai/disk/StorageAttachedIndexWriter.java#L316

There is still one problem on Compactors: we use StorageAttachedIndexWriter.addRow() even when rebuilding the indexes, we have to disambiguate this case from the other two cases (memtable flush and compaction activities) otherwise it is not possible to correlate correctly storageAttachedIndexWritingTime with the activities that are going on in the node.

@jasonstack I have changed storageAttachedIndexRebuildTime to storageAttachedIndexBuildTime, in order to have consistent naming


Address Family key to the dictionary 'bgp'

Under BGP config we have the address-family commands for both V4 and V6 to either activate or deactivate a certain peer-group. While V4 BGP can be run  by default, V6 BGP needs the peer-group or the corresponding neighbor to be activated in order to run. So essentially we might need a key called "address-family ipv4" and "address-family ipv6"
Example config:
router bgp 100
neighbor v4Group peer-group
neighbor v6Group peer-group
address-family ipv4
neighbor v4Group activate
no neighbor v6Group activate
address-family ipv6
neighbor v6Group activate
no neighbor v4Group activate

hoping to add this with the eVPN support since that will also require an address-family (address family evpn).  This is being tracked via #10


Freeze and update dependencies

This PR will freeze the most important dependencies of this package. I also included some compatible updates to the package.

LGTM.
Will merge, as this seems like a minor change that fixes some blocking issues.


Revert comments changes to scheduled classes to avoid update issues.

Changing a scheduled class isn't allowed.

Included in beta release version 3.30 (Beta 5) and higher

Included in production release version 3.30


tests with nosetests and MSVC compatability

Pretty sure it is not 100% working on linux or mac... only worked on it with MSVC

merged with 573fca65a4e6fe8517ce912b7edca8c2c2a55da9


Scrolling UI issue

https://docs.centre.io/verite/developers/issue-a-verifiable-credential
I cannot scroll content on chrome Version 98.0.4758.102 (Official Build) (x86_64) / macOS

I cannot reproduce. I'm on same version, M1 chip.

Closing as not reproducible.


refactor: Code Refactoring and Optimization

Changelog

Moved title display to separate function
Fixed spelling mistakes
Extracted display functionality to separate module
Setup CMake build chain
Extracted rectangle calculation logic to separate module
Created utils module for handling program utility functions
Defined triangle calculation logic in separate module

That's rectangle down, three more to go. I'll remove the square functions since, they're still just rectangles

triangle down, two more to go

Parallelogram down, only the trapezium implementation left now

Alright! Trapezium down. Looks good to me 👍🏼

All done!


Feature many

Branch name is not a good description. This adds an assign method, makes the 3rd argument to replace required, and updates the docs and tests.

:+1:


Update Event Hubs Example

Update the Event Hubs Connector example for 1.0 release.

@prateekm @xinyuiscool please take a look.

Update on the tutorial for the new website for this is coming soon.


[stable/prometheus-operator] CoreDNSDown alert needs kubeDns to be enabled.

Describe the bug

A cluster with Coredns pods having the label: k8s-app: coredns, after deploying prometheus-operator, the rule CoreDNSDown (and maybe other things) doesn't get created because it needs kubeDns to be enabled in values.yaml file. See: https://github.com/helm/charts/blob/f815a594fa5daf91d99fc60937c22b290ad67632/stable/prometheus-operator/templates/prometheus/rules/kubernetes-absent.yaml#L37 and https://github.com/helm/charts/blob/02f24b0e556af7bcd724b3b2811e6fdeacc8b83a/stable/prometheus-operator/hack/sync_prometheus_rules.py#L83

The alert template is generated from here :
https://github.com/coreos/kube-prometheus/blob/da959c643657c7d2aac6f5ddd68582a949283c49/jsonnet/kube-prometheus/kube-prometheus.libsonnet#L88

If we enable kubeDns (even if kubedns isn't deployed on the cluster), the alert will always fire because there are no pods with the label k8s-app: kube-dns in the cluster ( we don't want to alter coredns pods' labels)

Version of Helm and Kubernetes:
Kubernetes: v1.13.5
Helm: v2.14.2
Which chart:
[stable/prometheus-operator]
What happened:
The alert CoreDNSDown isn't added.
What you expected to happen:
the alert CoreDNSDown in kubernetes-absent.yaml should be added only when we enable coreDns
How to reproduce it (as minimally and precisely as possible):
See Describe the bug
Anything else we need to know:

We can enable kubeDns with k8s-app: coredns for the selector but even if that solves the pb, I think it isn't coherent.

We've encountered this issue too, re-linking the relevant lines:
https://github.com/helm/charts/blob/22b6484babdfffa2f34f6ec1ca2ff87c905aa9d4/stable/prometheus-operator/templates/prometheus/rules/kubernetes-absent.yaml#L41-L50


GitHub Label Management

Summary
The focus of these changes is to update the set of tools and data associated with managing GitHub labels across the set of Azure SDK repositories.
The previous set of Python scripts have been replaced by Alex Ghiondea's GHCreator tool with a set of PowerShell wrappers.  Label and repository data are the result of recent leadership efforts to normalize labels and reflect the currently agreed upon common set.
Considerations
I decided against managing the GH Creator tool as a submodule, as that tends to add complexity and is unfamiliar to many.  Since the tool is stable for what is needed at present and is not rapidly evolving, I concluded a binary drop would be the better way to go.

/check-enforcer override

./check-enforcer override

/check-enforcer override


V2.3.x

Is this a proposal to merge 2.3.x into master? If so then current version on master is 3.x.
2.3.x is an old version. If you need that version - you can always get it from 2.3.x branch.
That version is also published on NPM.


[Bug 🐞]: logging in with threefold connect in hub.grid.tf fails sometimes

What happened?
When i login with threefold connect in hub.grid.tf , i get the following error sometimes and sometimes it logs in without any issue.

The issue mostly occurs in the first login using threefold connect, any logins after the first one works fine.
What did you expect?
Should've logged in without any issues.
What browsers are you seeing the problem on?
No response
ZOS info
No response
Dashboard info
No response
weblets info
No response
Relevant log output
No response

Does this still happen ? I think this was the same issue as https://github.com/threefoldtech/0-hub/issues/68


Has this been abandoned?

There hasn't been an update in some time and wondering what is going on!

https://github.com/GoogleCloudPlatform/terraformer


Dovado integration fails to configure

Home Assistant release with the issue:
Hass.IO v0.101.3, Supervisor v192
Last working Home Assistant release (if known):
First time I tried
Operating environment (Hass.io/Docker/Windows/etc.):
Debian, Docker
Integration:
Dovado
Description of problem:
When entering the config proposed in the Dovado integration , it fails with the following error:
Invalid config for [dovado]: [lovelace] is an invalid option for [dovado]. Check: dovado->lovelace. (See /config/configuration.yaml, line 330). Please check the docs at https://home-assistant.io/integrations/dovado/
Problem-relevant configuration.yaml entries
dovado:
  host: !secret dovado_ip
  port: !secret dovado_port
  username: !secret dovado_user
  password: !secret dovado_password`

Hi, there @miljume,
This error generally indicates an issue with the indenting of your YAML file. I would highly recommend joining our Discord chat server since there are many people in there that can help you to guide you through this and pinpoint the issue.
https://www.home-assistant.io/join-chat

@miljume any updates on this? :)

No, nothing so far, still the same issue. I am quiet sure it's a bug as it's a very simple configuration and I only copy/pasted the config

How does your config look like? Because I would agree with @frenck that it looks like an indentation problem.

See my config for Dovado in my first post, if I comment out these lines everything works
I used the config from https://www.home-assistant.io/integrations/dovado/

@miljume, the problem is, that it is not conclusive, hence everybody asking for more information (and I'm redirecting you to the chat server). The error looks like it is incorrect indented with the things around that piece of code (so no caused by this piece directly, more its location).

Just scanned over the code and found that the CONFIG_SCHEMA does not include the DOMAIN at all. Have not seen a schema like that or is that a special case @frenck?
In comparison:
https://github.com/home-assistant/home-assistant/blob/c35f9ee35f8efb318a8ab59c1e6d9d277a415379/homeassistant/components/dovado/__init__.py#L20-L29
https://github.com/home-assistant/home-assistant/blob/c35f9ee35f8efb318a8ab59c1e6d9d277a415379/homeassistant/components/ecovacs/__init__.py#L14-L25
Testing this gives me a similar error just with different parts of my configuration file inside of the brackets depending on the position of the dorado part e.g.
Invalid config for [dovado]: [XYZ] is an invalid option for [dovado]. Check: dovado->XYZ. (See /config/configuration.yaml, line XXX). Please check the docs at https://home-assistant.io/integrations/dovado/

@miljume, the problem is, that it is not conclusive, hence everybody asking for more information (and I'm redirecting you to the chat server). The error looks like it is incorrect indented with the things around that piece of code (so no caused by this piece directly, more its location).

Unfortunately I haven't got access to my config right now since the WAN link to my cabin (where the NUC is located) is down
But I can mention that I also tried including the config as a package yaml with the same result, no other code inside
So I highly doubt that it has to do with indentation


Support for<EMAIL_ADDRESS>

https://github.com/twbs/bootstrap/blob/a2b5901efc6de12bb828f8dda118ddccbcd545cf/scss/_functions.scss#L140
This code work fine for<EMAIL_ADDRESS>For<EMAIL_ADDRESS>support we need to use math.div($number1, $number2) for division : https://sass-lang.com/documentation/breaking-changes/slash-div
Or the Sass migrator to automatically update stylesheets to use math.div() and list.slash()
$ npm install -g sass-migrator
$ sass-migrator division **/*.scss

#34051


testing random number generator

seed = None or size x?
rerun with same seeds

I added a test for the bootstrap function in test_stats.py: it works, but the bootstrap values (d["bootstrap") are only identical for two runs with the same integer seed after sorting. Doesn't really matter but is that expected behavior, @fbkarsdorp?

I added a test for the bootstrap function in test_stats.py: it works, but the bootstrap values (d["bootstrap") are only identical for two runs with the same integer seed after sorting. Doesn't really matter but is that expected behavior, @fbkarsdorp?

(Probably the result of async: the numbers are the same, but not necessarily returned in the same order. Closing this for now.)

(Probably the result of async: the numbers are the same, but not necessarily returned in the same order. Closing this for now.)


Estimate work items in an iteration not populating

Since about 1-2 weeks we have a problem, that the dropdown "Estimate work items in an iteration" does no longer populate, though iterations exist.

In other projects of the same account, the dropdown is populated.
Any ideas ?

Any error message on the console? Or failed requests in the network tab?
Have you tried the new version?

Unfortunately no errors on console/network tab.
We switched to the new version, which does not have the issue.


[BUG] Vulkan / AMD

RawrBox lib

[x] rawrbox.render

Description
Vulkan on AMD does not support NonUniformResourceIndex well and so it creates small artifacts on those vertexes

DXC compiler needs to be used, but there is currently a problem with it related to shader compilation


Update UserManager to support construction of IUserServices with IRuntimeManager as a constructor parameter

In gitblit-crowd-plugin I make use of my own subclass of ConfigUserService.
Unfortunatelly i'm not able to get the data directory from the settings during construction, which is quite bad.
A very simple approach of supporting customized IUserServices is implemented in this PR:
Behavior at the moment:

Try to instantiate an IUserService with default constructor.
If class not found ->create ConfigUserService from conf file
If instantiation fails -> log error (and die... this will cause NullPointerExceptions afterwards

Newly implemented behavior:

Try to instantiate an IUserService with default constructor.
If class not found -> create ConfigUserService from conf file
If instantiation with default constructor fails -> Try again with constructor having IRuntimeManager as a parameter
If this instantiation fails also -> log error (and die... this will cause NullPointerExceptions afterwards

This way no further changes in existing UserServices are needed. New implementations will have the possibility to access all application settings by implementing a constructor like the following:
public class MyCoolUserService implements IUserService {
  public MyCoolUserService(IRuntimeManager manager){
    //do whatever you like. you know the runtimeManager now
  }
}

I like this idea.  Would you please make instantiation of a user service a new method?  i.e. extract realmClass.newInstance() and your catch block into a new method.


Pdc client add support for build-image-rtt-tests

Add build-image-rtt-tests to support pdc client.
JIRA: PDC-1261

it is better if more test cases added.

@simozhan  and @ycheng-aa ; please review this patch.

@simozhan and @ycheng-aa ; please review this patch again~!

Looks good for me.


[Question] How is the concurrency supported?

Hello,
How is supported concurrency? I mean if I want to process two commands on the same aggregate ?
Regards

Hi,
there is an option to check for the expected version.
In the domain command you can set the expected version number.
If the actual version is different from the expected version a concurrency exception is thrown.
Is this answer your question?

Ok but when are we supposed to set the expected version exactly? in the command handler when the aggregate is loaded?

When the command is created before using the dispatcher.
Imagine you have a web app and a mobile app and two commands are sent to the API at the same time. Both apps are expecting the aggregate to be on version let's say 4 and the second command to finish the work would find the version to be 5 and therefore the state is invalid because the command was based on version 4.

Do you mean that I have to load the aggregate (in order to get the current version) before I can create a command?

If you want to use the expected version functionality in oprder to prevent concurrency issues you need somehow to provide the version number which might even come from the read model so you won't need to load the whole aggregate.

Here is the way I would like to use it. Please tell me if I am doing it wrong or if I am missing something.
Let's take an example with an “account” with a Sold property and a “debitCommand” with an Amount property:
All is coded in the debit command handler:
1: Load aggregate
var account = await _repository.GetByIdAsync(debitCommand.AggregateRootId);

2: Check the account is known
if (account == null)
{
    throw new ApplicationException("Account not found.");
}

3: Check the command can be applied (based on the loaded aggregate version) in other words check if the sold account is bigger than the debit amount. (By the way is it the best place where to process this check or should it be in account.Debit() method implementation?)
if (account.Sold < debitCommand.Amount)
{
    throw new ApplicationException("Account sold too low.");
}

4: Update the command expected version
debitCommand.ExpectedVersion = account.Version + 1 ;

I am not really happy with the way of doing it:

Is there a better way to compute the next version?
Is the command supposed to be immutable?

5: Apply the command to the aggregate
account.Debit(debitCommand.Amount) ;

6: Return command resulting events
return account.Events;

There is an error in your implementation, the expected version should be account.Version and not account.Version + 1 also my concern is related to the fact that a command could be based on a stale version. Let's assuming that 2 users load the same aggregate on a particular UI and the version for both of them is 4.
The first user sends a command and your implementation would be correct (after removing the + 1).
The second user sends another command and the expected version set by the handler would be 5, because the first event would have been already saved. It is not correct because the user modified the aggregate based on version 4 and not 5, therefore it would potentially override some changes of the first user without even knowing what they are.

Ok thanks for the +1.
My point about the concurrent access is that if my API is receiving two commands (debit 10) concurrently, I will have two thread handling the commands and my account sold is 15.
Let's say that I have the following operations:
Thread 1: load aggregate in version 4 (sold = 15)
Thread 2: load aggregate in version 4 (sold = 15)
Thread 1: check sold 15>10 and set the expected version 4
Thread 2: check sold 15>10 and set the expected version 4
Thread 1: save debit event successfully with expected version 4.
Thread 2: fail to save the event because of the expected version is 4 instead of 5 (throw exception).
In this case the thread 2 will eventually retry the command (automatically or with a user action) and load the new version of aggregate and see that the account sold is too low.
In this case, this is my expected behavior. Don't you agree ?

Yes, I agree that in your specific scenario is fine because you are covering it in your business logic :-)

Ok thanks for your answers! I will try with this implementation then....
Regards

No worries, please let me know if you have any other questions!


gofmt to fix formatting

LGTM.
I think we should add gofmt to the list of things to check for on CI.

LGTM

@dqminh It is already there https://jenkins.dockerproject.org/job/Libcontainer-PRs/683/console:
Congratulations!  All Go source files are properly formatted.

But seems like not strict enough or I don't know.

Yeah, not sure why this wasn't caught. It should have been by what we have.

I think the CI script only checks format on changed files. It would not do anything for existing code.


Mark Synonyms API as stable

Thanks! In what version do they become stable? (Wondering if this should be backported to the 8.12 branch.)
@pquentin  This is planned for 8.13! Thanks for asking!

Thanks! In what version do they become stable? (Wondering if this should be backported to the 8.12 branch.)

Marked as Stable in 8.10:
https://github.com/elastic/elasticsearch/pull/97962/files
Please ensure online docs are updated too as they are showing the API is in beta (which is incorrect):

The docs built from the main branch (that will become 8.13) are already correct: https://www.elastic.co/guide/en/elasticsearch/reference/master/synonyms-apis.html


New package: DuckStudio.GitHubLabelsManager version v1.1

Checklist for Pull Requests

[x] Have you signed the Contributor License Agreement?
[x] Resolve #161394 & DuckDuckStudio/GitHub-Labels-Manager#2

Manifests

[x] Have you checked that there aren't other open pull requests for the same manifest update/change?
[x] This PR only modifies one (1) manifest
[x] Have you validated your manifest locally with winget validate --manifest <path>?

PS> winget validate --manifest manifests\d\DuckStudio\GitHubLabelsManager\1.1
清单验证成功。

Thanks to aisgbnok for the help.
DuckDuckStudio/GitHub-Labels-Manager#3

[x] Does your manifest conform to the 1.6 schema?

Note: <path> is the directory's name containing the manifest you're submitting.
Packing log: packing.log

Microsoft Reviewers: Open in CodeFlow

Example:

DuckStudio.GitHubLabelsManager.installer.yaml

# Created using wingetcreate <IP_ADDRESS>
# yaml-language-server: $schema=https://aka.ms/winget-manifest.installer.1.6.0.schema.json

PackageIdentifier: DuckStudio.GitHubLabelsManager
PackageVersion: "1.1"
InstallerType: inno
Scope: machine
InstallModes:
- interactive
- silent
- silentWithProgress
InstallerSwitches:
  Silent: /verysilent /suppressmsgboxes
  SilentWithProgress: /verysilent
UpgradeBehavior: install
Commands:
- glm
Protocols:
- http
- https
ReleaseDate: 2024-07-04
AppsAndFeaturesEntries:
- DisplayVersion: 'v1.1'
ElevationRequirement: elevatesSelf
Installers:
- InstallerLocale: zh-CN
  Architecture: x86
  InstallerUrl: https://github.com/DuckDuckStudio/GitHub-Labels-Manager/releases/download/v1.1/GitHub_Labels_Manager_Setup_v1.1.exe
  InstallerSha256: 7AB9CA2467A5CEE9B25E32CA91036AE1D852A8A95E4ED07404532C6762FFDB54
- InstallerLocale: zh-CN
  Architecture: x64
  InstallerUrl: https://github.com/DuckDuckStudio/GitHub-Labels-Manager/releases/download/v1.1/GitHub_Labels_Manager_Setup_v1.1.exe
  InstallerSha256: 7AB9CA2467A5CEE9B25E32CA91036AE1D852A8A95E4ED07404532C6762FFDB54
- InstallerLocale: en-US
  Architecture: x86
  InstallerUrl: https://github.com/DuckDuckStudio/GitHub-Labels-Manager/releases/download/v1.1/GitHub_Labels_Manager_Setup_v1.1_EN.exe
  InstallerSha256: D51CD388AC02DFB5B792C5B262DC814BFE947C993452772E59DD5EB09B4D7F0C
- InstallerLocale: en-US
  Architecture: x64
  InstallerUrl: https://github.com/DuckDuckStudio/GitHub-Labels-Manager/releases/download/v1.1/GitHub_Labels_Manager_Setup_v1.1_EN.exe
  InstallerSha256: D51CD388AC02DFB5B792C5B262DC814BFE947C993452772E59DD5EB09B4D7F0C
ManifestType: installer
ManifestVersion: 1.6.0

DuckStudio.GitHubLabelsManager.locale.zh-CN.yaml

# Created using wingetcreate <IP_ADDRESS>
# yaml-language-server: $schema=https://aka.ms/winget-manifest.defaultLocale.1.6.0.schema.json

PackageIdentifier: DuckStudio.GitHubLabelsManager
PackageVersion: "1.1"
PackageLocale: zh-CN
Publisher: DuckStudio
PublisherUrl: https://duckduckstudio.github.io/yazicbs.github.io/
PublisherSupportUrl: https://github.com/DuckDuckStudio/GitHub-Labels-Manager/issues
Author: 鸭鸭「カモ」
PackageName: GitHub Labels Manager
PackageUrl: https://github.com/DuckDuckStudio/GitHub-Labels-Manager
License: GPL-3.0
LicenseUrl: https://github.com/DuckDuckStudio/GitHub-Labels-Manager/blob/main/LICENSE
Copyright: Copyright (c) DuckStudio 鸭鸭「カモ」
ShortDescription: GitHub仓库标签管理工具
Description: 自动帮你复制仓库标签、获取仓库标签、清空已有标签的工具
Moniker: glm
Tags:
- devtools
- github
- github-labels
- labels
ReleaseNotes: 初始功能实现
ReleaseNotesUrl: https://github.com/DuckDuckStudio/Chinese_git/releases/tag/v1.1
ManifestType: defaultLocale
ManifestVersion: 1.6.0

DuckStudio.GitHubLabelsManager.locale.en-US.yaml

# Created using wingetcreate <IP_ADDRESS>
# yaml-language-server: $schema=https://aka.ms/winget-manifest.locale.1.6.0.schema.json

PackageIdentifier: DuckStudio.GitHubLabelsManager
PackageVersion: "1.1"
PackageLocale: en-US
Publisher: DuckStudio
PublisherUrl: https://duckduckstudio.github.io/yazicbs.github.io/
PublisherSupportUrl: https://github.com/DuckDuckStudio/GitHub-Labels-Manager/issues
Author: 鸭鸭「カモ」
PackageName: GitHub Labels Manager
PackageUrl: https://github.com/DuckDuckStudio/GitHub-Labels-Manager
License: GPL-3.0
LicenseUrl: https://github.com/DuckDuckStudio/GitHub-Labels-Manager/blob/main/LICENSE
Copyright: Copyright (c) DuckStudio 鸭鸭「カモ」
ShortDescription: A GitHub Labels Manager
Description: Tools that automatically help you copy repo labels, get repo labels, and empty existing labels.
Tags:
- devtools
- github
- github-labels
- labels
ReleaseNotes: Initial function implementation.
ReleaseNotesUrl: https://github.com/DuckDuckStudio/Chinese_git/releases/tag/v1.1
ManifestType: locale
ManifestVersion: 1.6.0

DuckStudio.GitHubLabelsManager.yaml

# Created using wingetcreate <IP_ADDRESS>
# yaml-language-server: $schema=https://aka.ms/winget-manifest.version.1.6.0.schema.json

PackageIdentifier: DuckStudio.GitHubLabelsManager
PackageVersion: "1.1"
DefaultLocale: zh-CN
ManifestType: version
ManifestVersion: 1.6.0

Manifest Warning: Unknown field. [Moniker]

Moniker is only allowed in ManifestType: defaultLocale.

Edit: DuckDuckStudio/GitHub-Labels-Manager#4

/azp run

/azp run

AFAIK it installs correctly for me, not sure what needs repaired. (https://github.com/microsoft/winget-pkgs/labels/Validation-Executable-Error https://github.com/microsoft/winget-pkgs/labels/Validation-Installation-Error)
zh-CN
--> Installing the Manifest 1.1

Found GitHub Labels Manager [DuckStudio.GitHubLabelsManager] Version 1.1
This application is licensed to you by its owner.
Microsoft is not responsible for, nor does it grant any licenses to, third-party packages.
Downloading https://github.com/DuckDuckStudio/GitHub-Labels-Manager/releases/download/v1.1/GitHub_Labels_Manager_Setup_v1.1.exe
  ██████████████████████████████  12.0 MB / 12.0 MB
Successfully verified installer hash
Starting package install...
Successfully installed

--> Refreshing environment variables

--> Comparing ARP Entries

DisplayName                        DisplayVersion Publisher  ProductCode               Scope
-----------                        -------------- ---------  -----------               -----
GitHub Labels Manager version v1.1 v1.1           DuckStudio GitHub Labels Manager_is1 Machine

en-US
--> Installing the Manifest 1.1

Found GitHub Labels Manager [DuckStudio.GitHubLabelsManager] Version 1.1
This application is licensed to you by its owner.
Microsoft is not responsible for, nor does it grant any licenses to, third-party packages.
Downloading https://github.com/DuckDuckStudio/GitHub-Labels-Manager/releases/download/v1.1/GitHub_Labels_Manager_Setup_v1.1_EN.exe
  ██████████████████████████████  12.0 MB / 12.0 MB
Successfully verified installer hash
Starting package install...
Successfully installed

--> Refreshing environment variables

--> Comparing ARP Entries

DisplayName                        DisplayVersion Publisher  ProductCode               Scope
-----------                        -------------- ---------  -----------               -----
GitHub Labels Manager version v1.1 v1.1           DuckStudio GitHub Labels Manager_is1 Machine

2024-07-07 05:37:47.045 [FAIL] Installer failed security check. Url: https://github.com/DuckDuckStudio/GitHub-Labels-Manager/releases/download/v1.1/GitHub_Labels_Manager_Setup_v1.1_EN.exe Result: 0x80004005

I will change late.

Main program: glm.exe

Automatic Validation ended with:
(Automated response - build 886.)

Verify:

I couldn't find the version number displayed inside the application.

I couldn't find the version number displayed inside the application.

Use this command to display the version:
PS> glm config --version
✓ 当前使用的版本为:
GitHub Labels Manager v1.1
[!] 按 Enter 键退出...

Yes, these 2 lines should still be removed.

Automatic Validation ended with:
(Automated response - build 886.)


Github Actions new changes

TODOs:
@Abhi
git checkout repo
@Abhi
support relative path lookup
@Abhi
support kubernetes manifest OR helm chart
@Abhi
add conditional logic for invocation via website
Example command to merge the yamls into one: FILE_PATH=tests/manifest-test ./manifest-merger.sh

TODOS:
Manage Wronf file-path
Manage curl failure
Manage File Upload Via node/Not using Curl due to Base64 Error


Suggestion: suggestedAction should be treated like choicePrompt in dialog/waterfall

While testing the MessageFactory.suggestedAction(), I found that I cannot use it in a waterfall step because it does not cause the dc.continue() to continue executing my dialog. I suggest that it should.
For instance, this dialog cannot proceed to step 2 of the waterfall:
dialogs.add('suggestedAction', [
    async function(dc){
        var suggestedAction = MessageFactory.suggestedActions(["Red", "White", "Blue"], "What's your favorite color?");
        await dc.context.sendActivity(suggestedAction);
    },
    async function(dc, result){
        await dc.context.sendActivity("You choose: " + result.value);
        await dc.end();
    }
]);

However, this dialog will proceed to step 2 because it's using a prompt:
dialogs.add('suggestedAction', [
    async function(dc){
        await dc.prompt("choicePrompt", "What's your favorite color?", (["Red", "White", "Blue"]);
    },
    async function(dc, result){
        await dc.context.sendActivity("You choose: " + result.value);
        await dc.end();
    }
]);

Since the expected behavior of sending a "suggestedAction" is similar to a "choicePrompt" where both expect users to pick an option from the list of choices, it would make sense for the dialogs.continue() pass execution to the active dialog so it can process the user's input for a suggestedAction too.

So currently if you don't call prompt() or begin()  within a waterfall step and instead send an activity to the user without calling end() the waterfall will be automatically ended for you when the user replies.  This has always been "by design" and is almost always the result of a user simply forgetting to call end().  You raise an interesting observation @v-ducvo that if I have more waterfall steps after the current one then my intention probably was NOT to end the dialog. I just didn't do the right thing to get the dialog to advance.
While it's not really practical for the waterfall to know that you sent suggestedActions so you really were trying to use a choice prompt, I think there is something smarter we can do here.  Instead of ending the dialog we could just pass the users response to the next step.  You're still going to have to be intentional about the code you're writing but it will let you now write a waterfall that moves forward without the use of prompts at all which I like.  So updating your example:
dialogs.add('suggestedAction', [
    async function(dc){
        var suggestedAction = MessageFactory.suggestedActions(["Red", "White", "Blue"], "What's your favorite color?");
        await dc.context.sendActivity(suggestedAction);
    },
    async function(dc, result){
        switch (result.toLowerCase()) {
             case 'red':
                  await dc.sendActivity(`I like Red too!`);
                  break;
              case 'white':
              case 'blue':
              default:
                  await dc.sendActivity(`Well my favorite is red.`);
                  break;
        }
        await dc.end();
    }
]);

The fact you always have to start a dialog to drive the waterfall forward has always felt a little heavy so I like that you can now write a waterfall without the use of prompts.  Open to feedback from others.

Waterfalls now follow the proposal I outlined above.

The above shown code is not working for me. sendActivity is still ending my dialog


How to use this Library to use the transreceiver on the NRF chip without the BLE stack?

Hi ,
I wish to build a sensor mesh using BLE nano, where each node can be a master or slave. I am hoping to use the trans receiver on the chip without the BLE stack to perform this... since this library only supports peripheral roles. Please let me know if there is a hack for this.
Thanks

@suveergarg there are no hacks for it using this library.


hub create

First, I dont get if this is a local or remote repo.
I can create a local with git as well, so I would not get the sense of hub create here.
If it's meant as a remote repo, this is what I get on git push:
fatal: The current branch master has no upstream branch.
To push the current branch and set the remote as upstream, use

    git push --set-upstream origin master

Secondly, the command here seems to be hub create, not git create?

It's at least not working with git create here: git create is not a git command
While it is working with hub create.
Thanks a lot in advance

Oh, it seems to be a local repo?

And how to create a repo in an organisation?

One more thing:
https://hub.github.com/hub.1.html
No Organisation/repo here:

Then not here in the header, while part of the description:

And then finally here, in another syntax:

And not working in both cases:

There seems to be some misalignment between emphasising the hub command and aliasing hub with git in different documentation (ghpages vs manpages vs readme). I guess depending on what the maintainers are biasing users towards (using hub vs the aliased git) they should try to focus on... My preference would be hub with the option to alias.
I'm curious to hear what the maintainers say.
For the hub create command, assuming you have an existing git repository, you can do the following:
hub create -d "Test" # this creates the repo "hub" in your own users' namespace with description "Test"
hub create -d "Test" someorg/hub # this creates the repo "hub" in "someorgs" namespace, assuming you have the proper authorization

The git create command doesnt work here currently. Does it for you?

Yes but I added this to my .bashrc file which aliases "git" with "hub" allowing git to initiate any git or hub command.
eval "$(hub alias -s)"
Instructions for aliasing are here: https://github.com/github/hub#aliasing

Yeah fine. This change anything on the documentation?

It is covered in both README and ghpages site - but there are stylistic differences and perhaps ghpages is not explicit enough?
@mislav  - do you think there is room for improvement in docs for being more explicit?

This is the current documentation which you get with hub help create on the master branch (available as prereleases):
Usage: hub create [-poc] [-d <DESCRIPTION>] [-h <HOMEPAGE>] [[<ORGANIZATION>/]<NAME>]

Create a new repository on GitHub and add a git remote for it.

## Options:
        -p
                Create a private repository.

        -d <DESCRIPTION>
                Use this text as the description of the GitHub repository.

        -h <HOMEPAGE>
                Use this text as the URL of the GitHub repository.

        -o, --browse
                Open the new repository in a web browser.

        -c, --copy
                Put the URL of the new repository to clipboard instead of printing it.

        [<ORGANIZATION>/]<NAME>
                The name for the repository on GitHub (default: name of the current working
                directory).

                Optionally, create the repository within <ORGANIZATION>.

## Examples:
                $ hub create
                [ repo created on GitHub ]
                > git remote add -f origin git@github.com:USER/REPO.git

                $ hub create sinatra/recipes
                [ repo created in GitHub organization ]
                > git remote add -f origin git@github.com:sinatra/recipes.git

When the master branch is released, this will become the official documentation on the site.
Do you think this latest documentation is better?

It suggests writing hub create instead of git create because it doesn't assume that hub was aliased as git;
It clearly documents the ORGNAME/REPONAME syntax.

@ShalokShalom The correct syntax would be simply hub create KPC-quarantine-area/hub instead of pasting the whole URL. Is there anything else unclear?

When you take a look on my first screenshot, can you see, that your main homepage lists git create instead hub create.

And it still seems confusing to me, which USER/REPO get used, when hub create get triggered without any additional arguments.

If you don't pass any arguments to hub create, the default USER/REPO will be:

USER: your username on GitHub ("ShalokShalom")
REPO: the name of the local project's directory (e.g. "myproject" when in "/path/to/myproject" directory).

Then maybe mention that too.
From where knows hub that? Does it ask me for my login details, when i launch this command?

Most (if not all) hub commands will ask for login details when first launched. This is not specific to hub create. Also, isn't it intuitive that a comamand whose description is "Create a repository on GitHub" would create one under your personal account by default?

Yes.

Could hub create prompt you whether you want public or private? Or if that's too difficult, how about making hub create -p be the default, and letting the user make it public if they want to?
It's not obvious that it will be public by default. I'm using the fish completions, and there's no indication of that.

Of course public by default.

I have multiple git alias such as `alias gac = "git add -A; git commit".
It seems there are 2 different methods suggested to alias hub to git:

"alias git=hub" https://hub.github.com/

eval "$(hub alias -s)"

What is the difference between the 2 methods..
Will my other git aliases work, if I use either of them? Which one is preferred and why?

@alphaCTzo7G The 2nd one is preferred for long-term use by putting this in your ~/.bash_profile or similar shell initialization script. The 1st one is preferred for examples (such as on our site) where the alias is temporarily configured in the current shell so that git commands expanded by hub could be demonstrated.
Anyway, this issue is not the correct thread to discuss this, since the original thread was about hub create and not aliases.

makes sense.. thanks for the clarification.


npm ERR! 404 Not Found<EMAIL_ADDRESS>

Version
3.7.0
Reproduction link
https://github.com/vuejs/vue-cli
Environment info
zsh: command not found: vue

Steps to reproduce
install
What is expected?
install success
What is actually happening?
I don't know, I just installed it for the first time

node : v10.15.3
npm :6.4.1

I have this problem too, and don't know how to solve it.

I have this problem too, and don't know how to solve it.

Me too.

➜  ~ npm i -g @vue/cli
npm WARN deprecated<EMAIL_ADDRESS>This module has moved and is now available at @hapi/joi. Please update your dependencies as this version is no longer maintained an may contain bugs and security issues.
npm WARN deprecated<EMAIL_ADDRESS>This module has moved and is now available at @hapi/hoek. Please update your dependencies as this version is no longer maintained an may contain bugs and security issues.
npm WARN deprecated<EMAIL_ADDRESS>cross-spawn no longer requires a build toolchain, use it instead
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none is installed. You must install peer dependencies yourself.

npm ERR! code E404
npm ERR! 404 Not Found<EMAIL_ADDRESS>WARN tar ENOENT: no such file or directory, open '/Users/w/.nvm/versions/node/v8.16.0/lib/node_modules/.staging/finalhandler-b7bdbd25/index.js'
WARN tar ENOENT: no such file or directory, open '/Users/w/.nvm/versions/node/v8.16.0/lib/node_modules/.staging/finalhandler-b7bdbd25/LICENSE'
WARN tar ENOENT: no such file or directory, open '/Users/w/.nvm/versions/node/v8.16.0/lib/node_modules/.staging/finalhandler-b7bdbd25/README.md'
WARN tar ENOENT: no such file or directory, open '/Users/w/.nvm/versions/node/v8.16.0/lib/node_modules/.staging/apollo-cache-inmemory-9c05cc12/lib/bundle.umd.js'
WARN tar ENOENT: no such file or directory, open '/Users/w/.nvm/versions/node/v8.16.0/lib/node_modules/.staging/unbzip2-stream-067973f1/index.js'
WARN tar ENOENT: no such file or directory, open '/Users/w/.nvm/versions/node/v8.16.0/lib/node_modules/.staging/unbzip2-stream-067973f1/LICENSE'
WARN tar ENOENT: no such file or directory, open '/Users/w/.nvm/versions/node/v8.16.0/lib/node_modules/.staging/unbzip2-stream-067973f1/README.md'
WARN tar ENOENT: no such file or directory, open '/Users/w/.nvm/versions/node/v8.16.0/lib/node_modules/.staging/apollo-utilities-43a5bb1d/jest.config.js'
WARN tar ENOENT: no such file or directory, open '/Users/w/.nvm/versions/node/v8.16.0/lib/node_modules/.staging/apollo-utilities-43a5bb1d/LICENSE'
WARN tar ENOENT: no such file or directory, open '/Users/w/.nvm/versions/node/v8.16.0/lib/node_modules/.staging/recast-192c9bd5/lib/lines.js'
WARN tar ENOENT: no such file or directory, open '/Users/w/.nvm/versions/node/v8.16.0/lib/node_modules/.staging/recast-192c9bd5/lib/mapping.d.ts'
WARN tar ENOENT: no such file or directory, open '/Users/w/.nvm/versions/node/v8.16.0/lib/node_modules/.staging/recast-192c9bd5/lib/mapping.js'
WARN tar ENOENT: no such file or directory, open '/Users/w/.nvm/versions/node/v8.16.0/lib/node_modules/.staging/recast-192c9bd5/lib/options.d.ts'
WARN tar ENOENT: no such file or directory, open '/Users/w/.nvm/versions/node/v8.16.0/lib/node_modules/.staging/recast-192c9bd5/lib/options.js'
WARN tar ENOENT: no such file or directory, open '/Users/w/.nvm/versions/node/v8.16.0/lib/node_modules/.staging/recast-192c9bd5/lib/parser.d.ts'
WARN tar ENOENT: no such file or directory, open '/Users/w/.nvm/versions/node/v8.16.0/lib/node_modules/.staging/recast-192c9bd5/lib/parser.js'
WARN tar ENOENT: no such file or directory, open '/Users/w/.nvm/versions/node/v8.16.0/lib/node_modules/.staging/recast-192c9bd5/lib/patcher.d.ts'
WARN tar ENOENT: no such file or directory, open '/Users/w/.nvm/versions/node/v8.16.0/lib/node_modules/.staging/recast-192c9bd5/lib/patcher.js'
WARN tar ENOENT: no such file or directory, open '/Users/w/.nvm/versions/node/v8.16.0/lib/node_modules/.staging/recast-192c9bd5/lib/printer.d.ts'
WARN tar ENOENT: no such file or directory, open '/Users/w/.nvm/versions/node/v8.16.0/lib/node_modules/.staging/recast-192c9bd5/lib/printer.js'
WARN tar ENOENT: no such file or directory, open '/Users/w/.nvm/versions/node/v8.16.0/lib/node_modules/.staging/ajv-29972b33/README.md'
WARN tar ENOENT: no such file or directory, open '/Users/w/.nvm/versions/node/v8.16.0/lib/node_modules/.staging/rss-parser-332b082b/dist/rss-parser.min.js.map'
WARN tar ENOENT: no such file or directory, open '/Users/w/.nvm/versions/node/v8.16.0/lib/node_modules/.staging/apollo-client-d1eff61a/ApolloClient.js'
WARN tar ENOENT: no such file or directory, open '/Users/w/.nvm/versions/node/v8.16.0/lib/node_modules/.staging/apollo-client-d1eff61a/ApolloClient.js.map'
WARN tar ENOENT: no such file or directory, open '/Users/w/.nvm/versions/node/v8.16.0/lib/node_modules/.staging/apollo-client-d1eff61a/bundle.cjs.js'
WARN tar ENOENT: no such file or directory, open '/Users/w/.nvm/versions/node/v8.16.0/lib/node_modules/.staging/express-eb187a30/index.js'
WARN tar ENOENT: no such file or directory, open '/Users/w/.nvm/versions/node/v8.16.0/lib/node_modules/.staging/express-eb187a30/LICENSE'
WARN tar ENOENT: no such file or directory, open '/Users/w/.nvm/versions/node/v8.16.0/lib/node_modules/.staging/express-eb187a30/Readme.md'
^C
➜  ~ npm i -g @vue/cli
npm WARN deprecated<EMAIL_ADDRESS>This module has moved and is now available at @hapi/joi. Please update your dependencies as this version is no longer maintained an may contain bugs and security issues.
npm WARN deprecated<EMAIL_ADDRESS>This module has moved and is now available at @hapi/hoek. Please update your dependencies as this version is no longer maintained an may contain bugs and security issues.
npm WARN deprecated<EMAIL_ADDRESS>cross-spawn no longer requires a build toolchain, use it instead
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none is installed.

Maybe it is caused by taobao registry , I switch to npm registry and success.

Maybe it is caused by taobao registry , I switch to npm registry and success.

I switch to npm registry and success too.  thx!


creating aks cluster with a long resource group name errors out with bad request

Describe the bug
Creating a aks cluster with long resource group name errors out with a bad request
To Reproduce
az aks create -g clitest.rgjug4amagf7n42kaltr3tbreekmwv2gfd76u6w3swsqsiphvtfhc23le2kq7iihc36 -n cliakstestjwiv6f
Expected behavior
Restrict client to provide a valid resource group name acceptable by AKS
Environment summary
Install Method (e.g. pip, interactive script, apt-get, Docker, MSI, edge build) / CLI version (az --version) / OS version / Shell Type (e.g. bash, cmd.exe, Bash on Windows)
Additional context

This has been fixed, you can only pass in an RG name that exists which means only valid names can be handled. @yugangw-msft could you #please-close?

#close

/close


Update to use TriggerContextData and disable deno lock

Type of change (place an x in the [ ] that applies)

[ ] New sample
[x] New feature
[ ] Bug fix
[ ] Documentation

Summary
Use the TriggerTypes object, the TriggerContextData object instead of using the templatized strings like {{data.interactivity}}, and disable deno.lock based on recent convos
Requirements (place an x in each [ ] that applies)

[x] I’ve checked my submission against the Samples Checklist to ensure it complies with all standards
[x] I have ensured the changes I am contributing align with existing patterns and have tested and linted my code
[x] I've read and agree to the Code of Conduct

Woops I accidentally pushed to main my trigger and deno.jsonc tweaks, forgetting this PR exists! My bad.
Closing this PR as as a result - sorry Neil!


Error shown when no response received from user can be improved.

Our current error in this case is:
[stage-N] Received: ""
[stage-N]            ^ error
[stage-N] Error: Expected start of a new RESP value (either +, -, :, $ or *)
[stage-N] Test failed (try setting 'debug: true' in your codecrafters.yml to see more details)

This can be updated a bit to something like:
[stage-N] No response received.
[stage-N] Test failed (try setting 'debug: true' in your codecrafters.yml to see more details)

Fixed here: https://github.com/codecrafters-io/redis-tester/pull/130/files


Thanks for making this and I update to version 1.5, seems the commands not available anymore

Thanks for making this, this is really my ideal way of using the chatGPT superpower.

Hi @LintaoAmons,
Can you try restarting Obsidian and see if that fixes it?

Hi @bramses,
There are no commands even after I restart the obsidian

hmm idk then, its showing up fine for me in multiple vaults, perhaps check the developer tools pane and see if any error is occurring? if that doesnt work, downgrade to 1.4.3 for now?

Yes, I currently still using the 1.4.3.


java.lang.IllegalStateException using BufferedReader

We tried implementing a Slack bot using slack's official SDK (Bolt).
When Invoking the servlet we are experiencing the exception detailed below:

java.lang.IllegalStateException: Cannot use BufferedReader while ServletInputStream is in use

I looked up the OldHttpServletRequestWrapper class and found that:
getInputStream is decorated by the adapter: https://github.com/OpenNTF/org.openntf.xsp.jakartaee/blob/0e9f200d1c52a3669803b5393c439663cb9f9cba/eclipse/bundles/org.openntf.xsp.jakartaee.commons/src/org/openntf/xsp/jakartaee/servlet/OldHttpServletRequestWrapper.java#L102
getReader is plain calling the delegate: https://github.com/OpenNTF/org.openntf.xsp.jakartaee/blob/0e9f200d1c52a3669803b5393c439663cb9f9cba/eclipse/bundles/org.openntf.xsp.jakartaee.commons/src/org/openntf/xsp/jakartaee/servlet/OldHttpServletRequestWrapper.java#L157
I'm not sure if the exception can be managed by also decorating the getReader() call or if this is a limit that cannot be worked around.
Below the entire stack trace.

java.lang.IllegalStateException: Cannot use BufferedReader while ServletInputStream is in use
com.ibm.domino.xsp.bridge.http.servlet.XspCmdHttpServletRequest.getReader(XspCmdHttpServletRequest.java:1412)
com.ibm.designer.runtime.domino.adapter.servlet.LCDAdapterHttpServletRequest.getReader(LCDAdapterHttpServletRequest.java:324)
org.openntf.xsp.jakartaee.servlet.OldHttpServletRequestWrapper.getReader(OldHttpServletRequestWrapper.java:158)
com.slack.api.bolt.jakarta_servlet.ServletAdapterOps.doReadRequestBodyAsString(ServletAdapterOps.java:19)
com.slack.api.bolt.jakarta_servlet.SlackAppServletAdapter.doReadRequestBodyAsString(SlackAppServletAdapter.java:44)
com.slack.api.bolt.jakarta_servlet.SlackAppServletAdapter.buildSlackRequest(SlackAppServletAdapter.java:31)
com.slack.api.bolt.jakarta_servlet.SlackAppServlet.doPost(SlackAppServlet.java:33)
jakarta.servlet.http.HttpServlet.service(HttpServlet.java:520)
jakarta.servlet.http.HttpServlet.service(HttpServlet.java:587)
org.openntf.xsp.jakarta.servlet.nsf.XspServletWrapper.doService(XspServletWrapper.java:64)
org.openntf.xsp.jakartaee.AbstractXspLifecycleServlet.service(AbstractXspLifecycleServlet.java:129)
jakarta.servlet.http.HttpServlet.service(HttpServlet.java:587)
org.openntf.xsp.jakartaee.servlet.NewHttpServletWrapper.service(NewHttpServletWrapper.java:112)
com.ibm.designer.runtime.domino.adapter.ComponentModule.invokeServlet(ComponentModule.java:600)
com.ibm.domino.xsp.module.nsf.NSFComponentModule.invokeServlet(NSFComponentModule.java:1352)
com.ibm.designer.runtime.domino.adapter.ComponentModule$AdapterInvoker.invokeServlet(ComponentModule.java:877)
com.ibm.designer.runtime.domino.adapter.ComponentModule$ServletInvoker.doService(ComponentModule.java:820)
com.ibm.designer.runtime.domino.adapter.ComponentModule.doService(ComponentModule.java:589)
com.ibm.domino.xsp.module.nsf.NSFComponentModule.doService(NSFComponentModule.java:1336)
com.ibm.domino.xsp.module.nsf.NSFService.doServiceInternal(NSFService.java:725)
com.ibm.domino.xsp.module.nsf.NSFService.doService(NSFService.java:515)
com.mindoo.domino.jna.xsp.http.DominoJNAHttpService$2.call(DominoJNAHttpService.java:76)
com.mindoo.domino.jna.xsp.http.DominoJNAHttpService$2.call(DominoJNAHttpService.java:1)
com.mindoo.domino.jna.gc.NotesGC$1.run(NotesGC.java:537)
java.security.AccessController.doPrivileged(AccessController.java:682)
com.mindoo.domino.jna.gc.NotesGC.runWithAutoGC(NotesGC.java:532)
com.mindoo.domino.jna.xsp.http.DominoJNAHttpService.doService(DominoJNAHttpService.java:68)
com.ibm.designer.runtime.domino.adapter.LCDEnvironment.doService(LCDEnvironment.java:363)
com.ibm.designer.runtime.domino.adapter.LCDEnvironment.service(LCDEnvironment.java:319)
com.ibm.domino.xsp.bridge.http.engine.XspCmdManager.service(XspCmdManager.java:272)

Hrm, interesting. In theory, having that wrapper there should be inert if you're not calling that method. I don't have a wrapper for the Reader because there's no specialized Servlet version of the type returned, so we shouldn't need one.
I wonder if something in here is calling getInputStream() beforehand... it shouldn't, but that would certainly cause that trouble. I'll see if I can reproduce the trouble.

I see this happens with an installation that only has XPages JEE installed and with a Servlet that just echoes the incoming payload back, so the trouble must be in this project.

Possibly the servletutil doing the transformation is triggering some statechange on the inputstream. (Just guessing).
Good to know you've been able to reproduce.

Moreover, it's definitely specific to Jakarta Servlets in NSFs: a legacy Servlet in an NSF (whether or not that NSF also has Jakarta libraries enabled) works fine.

The trouble comes in somewhere with the use of the Faces-lifecycle wrapper Servlet. If I skip that part, the Servlet executes without issue.
This is a sticky problem, though. I use that Faces-lifecycle wrapper to allow the Servlet to participate in the full app lifecycle, which means that it gets sessionAsSigner and, importantly, kicks off all the app-init listeners for CDI and the like.
I'll try to see if I can track down the part of the XSP stack that calls this and work around it. I assume that it's something that checks for a viewId in the POST data to re-hydrate a saved view. If so, I could work around it by having a specialized request wrapper that returns an empty stream.
Failing that, I may add an annotation that one could put on their Servlet class to have it opt out of the Faces context. That should work for cases like this, where presumably you're just wrapping the stock Slack Servlet outright.

Wow, thank you for the quick analysis.
In our use case the slack servlet is anonymous but then needs to access sessionAsSigner to interact with db data.
Opting out of lifecycle (if I understand your comment) would strip this Injection possibility away.
Thank you for investigating.


Wayland cursor locking buggy

Cursor locking on wayland seems to be non-functional after the winit update
It doesn't work in-game (the cursor gets hidden but can escape from the window)
Weirdly enough upon leaving the server and getting back into the server list it seems to suddenly work

For me I had it happen intermittently, within the same session connected to the server. It works most of the time and occasionally I would get a on hover description on the taskbar (the left hand side on Ubuntu), although clicking doesn't seem to escape the window.


Typo in the Wiki

There's a repetition in https://github.com/CanCanCommunity/cancancan/wiki/Defining-Abilities : because because. And it looks like the wiki is not in an edit access for all mode. :smile:

Removing the duplicated word:
https://github.com/CanCanCommunity/cancancan/pull/644

thanks


Switch to purely rust backend

https://github.com/cberner/redb

This is fixed by https://github.com/StaffEngineer/velo/pull/166


StorageExampleSwift Download not working

Getting the error below when clicking on the Download button in the Swift example. Works fine in the Obj-C example.

Error downloading:Error Domain=FIRStorageErrorDomain Code=-13000 "An unknown error occurred, please check the server response."

Can you give more detail?

I simply take a photo, it gets uploaded. Then click on the download button in the app and I get the failure above. I tried in simulator and phone, same in both. That happens in Swift example, but the obj-c example works fine.
Can you try the example on your devbox?

Thanks for you nice friendlyChatSwift tutorial unable to type a letter. I want have user name not from the part of the email. Enter the username field the use displlayName

Attachment is also not working only the name part of @ like<EMAIL_ADDRESS>only jey is displayed nothing else

var photoUrl =  NSURL?.self getting error without self or var photoUrl =  NSURL()

can explain why use :??
AppState.sharedInstance.displayName = user?.displayName ?? user?.email what does "??" mean

https://github.com/firebase/quickstart-ios/pull/41

still waiting if possible an answer

Hi jeyosman1, have you tried with the newest version of the app? Is your issue similar with the one guydaher had?

Where is the newest version
On Fri, Jun 10, 2016 at 2:59 PM, Thomas Césaré-Herriau <
<EMAIL_ADDRESS>wrote:

Hi jeyosman1, have you tried with the newest version of the app? Is your
issue similar with the one guydaher had?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/firebase/quickstart-ios/issues/15#issuecomment-225267548,
or mute the thread
https://github.com/notifications/unsubscribe/AI3w0tRE1f8iOSyog8IbuQDJSVuGgUwXks5qKbQEgaJpZM4Ik16f
.


Crash with JDK 8 and MacOS Catalina

Crash with JDK 8 and MacOS Catalina
When active Window pull on the second monitor
The same process works without errors with MacOS Mojave only with Catalina a crash
JDK Build
JAVA_VERSION="1.8.0_262"
OS_NAME="Darwin"
OS_VERSION="11.2"
OS_ARCH="x86_64"
SOURCE=""
JDK

CFBundleDevelopmentRegion
English
CFBundleExecutable
libjli.dylib
CFBundleGetInfoString
OpenJDK (1.8.0_262)
CFBundleIdentifier
net.java.openjdk.jdk
CFBundleInfoDictionaryVersion
7.0
CFBundleName
OpenJDK 8
CFBundlePackageType
BNDL
CFBundleShortVersionString
1.0
CFBundleSignature
????
CFBundleVersion
1.8.0_262
JavaVM

JVMCapabilities

CommandLine

JVMMinimumFrameworkVersion
13.2.9
JVMMinimumSystemVersion
10.6.0
JVMPlatformVersion
1.8
JVMVendor
AdoptOpenJDK
JVMVersion
1.8.0_262

nfo.plist
Thread 25 Crashed:: Java: Java2D Queue Flusher
0   libsystem_kernel.dylib        	0x00007fff701ff33a __pthread_kill + 10
1   libsystem_pthread.dylib       	0x00007fff702bbe60 pthread_kill + 430
2   libsystem_c.dylib             	0x00007fff70186808 abort + 120
3   libjvm.dylib                  	0x000000010bdeb35a os::abort(bool) + 22
4   libjvm.dylib                  	0x000000010bef86e7 VMError::report_and_die() + 2205
5   libjvm.dylib                  	0x000000010bdef948 JVM_handle_bsd_signal + 529
6   libjvm.dylib                  	0x000000010bded318 signalHandler(int, __siginfo*, void*) + 45
7   libsystem_platform.dylib      	0x00007fff702b05fd _sigtramp + 29
8   libobjc.A.dylib               	0x00007fff6ef03954 lookUpImpOrForward + 63
9   libawt_lwawt.dylib            	0x000000012600e16b CGLSD_MakeCurrentToScratch + 71
10  libawt_lwawt.dylib            	0x000000012600e27f OGLSD_MakeOGLContextCurrent + 99
11  libawt_lwawt.dylib            	0x000000012602acbd OGLContext_SetSurfaces + 133
12  libawt_lwawt.dylib            	0x000000012602eb32 Java_sun_java2d_opengl_OGLRenderQueue_flushBuffer + 1578
13  ???                           	0x00000001107258ea 0 +<PHONE_NUMBER>
14  ???                           	0x0000000110726b0c 0 +<PHONE_NUMBER>
15  ???                           	0x000000010eff34e7 0 +<PHONE_NUMBER>
16  libjvm.dylib                  	0x000000010bc2ae0f JavaCalls::call_helper(JavaValue*, methodHandle*, JavaCallArguments*, Thread*) + 1681
17  libjvm.dylib                  	0x000000010bc29c5b JavaCalls::call_virtual(JavaValue*, KlassHandle, Symbol*, Symbol*, JavaCallArguments*, Thread*) + 325
18  libjvm.dylib                  	0x000000010bc29e37 JavaCalls::call_virtual(JavaValue*, Handle, KlassHandle, Symbol*, Symbol*, Thread*) + 87
19  libjvm.dylib                  	0x000000010bca1001 thread_entry(JavaThread*, Thread*) + 120
20  libjvm.dylib                  	0x000000010bebc256 JavaThread::thread_main_inner() + 130
21  libjvm.dylib                  	0x000000010bebc11b JavaThread::run() + 361
22  libjvm.dylib                  	0x000000010bdeae8f java_start(Thread*) + 250
23  libsystem_pthread.dylib       	0x00007fff702bc109 _pthread_start + 148
24  libsystem_pthread.dylib       	0x00007fff702b7b8b thread_start + 15

The information provided is insufficient but thankfully the description sounded familiar so there's https://bugs.openjdk.java.net/browse/JDK-8244818. If the problem is not the same, please answer as many questions as possible from our issue template and provide a reproducer.

Hallo Andreas Ahlenstorf
yes the bug description is the same.
thanks for the information.
There is already an Adopt Version with Jdk8u271 or Jdk8u272 ?
—
Stefan Lorenz
<EMAIL_ADDRESS>phone:  0049 351 84 22 71 75
fax: 0049 180 355 56 88 50
onexip GmbH
Steglichstraße 38 | D-01324 Dresden | Germany
http://www.ultramixer.com
http://www.onexip.com

Am 31.07.2020 um 13:50 schrieb Andreas Ahlenstorf<EMAIL_ADDRESS>The information provided is insufficient but thankfully the description sounded familiar so there's https://bugs.openjdk.java.net/browse/JDK-8244818 https://bugs.openjdk.java.net/browse/JDK-8244818. If the problem is not the same, please answer as many questions as possible from our issue template https://github.com/AdoptOpenJDK/openjdk-support/blob/master/.github/ISSUE_TEMPLATE/bug-report.md and provide a reproducer.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/AdoptOpenJDK/openjdk-support/issues/152#issuecomment-667081345, or unsubscribe https://github.com/notifications/unsubscribe-auth/AQOXL265PSXLJRSXN2ULI63R6KVXRANCNFSM4PQBTO5A.

You can try a nightly build from https://adoptopenjdk.net/nightly.html?variant=openjdk8&jvmVariant=hotspot. The fix should already be in. The official release of 8u272 will be in October (closest Tuesday to the 17th).

Hallo Andreas Ahlenstorf
I have a question.
Is it possible to build the Openjdk yourself, if so how ?
I get a compiler error on Catalina.
Which Mac requirements must be met to build ?
—
Stefan Lorenz
<EMAIL_ADDRESS>phone:  0049 351 84 22 71 75
fax: 0049 180 355 56 88 50
onexip GmbH
Steglichstraße 38 | D-01324 Dresden | Germany
http://www.ultramixer.com
http://www.onexip.com

Am 01.08.2020 um 12:12 schrieb Andreas Ahlenstorf<EMAIL_ADDRESS>Closed #152 https://github.com/AdoptOpenJDK/openjdk-support/issues/152.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/AdoptOpenJDK/openjdk-support/issues/152#event-3611610880, or unsubscribe https://github.com/notifications/unsubscribe-auth/AQOXL26XM3WOMXUQH7ICIPTR6PS73ANCNFSM4PQBTO5A.

https://github.com/AdoptOpenJDK/openjdk-build has the build scripts. http://openjdk.java.net/groups/build/doc/building.html lists the requirements. What most people forget is that they need a boot JDK of version n-1 when building n (for example, 13 for building 14). We're building on 14. If you have specific issues, it might make sense to open a new ticket or even join our Slack workspace: https://adoptopenjdk.net/slack.html

Hallo Andreas Ahlenstorf
The Nightly Build of Adopt Openjdk 8 is now 272 b01 from 05.08.2020
I tested it right away, but I found that the bug still exists in the version.
https://bugs.openjdk.java.net/browse/JDK-8244818 https://bugs.openjdk.java.net/browse/JDK-8244818
Are the changes included in this nightly version or do you have to work on it  ?
—
Stefan Lorenz
<EMAIL_ADDRESS>phone:  0049 351 84 22 71 75
fax: 0049 180 355 56 88 50
onexip GmbH
Steglichstraße 38 | D-01324 Dresden | Germany
http://www.ultramixer.com
http://www.onexip.com

Am 04.08.2020 um 09:41 schrieb Andreas Ahlenstorf<EMAIL_ADDRESS>https://github.com/AdoptOpenJDK/openjdk-build https://github.com/AdoptOpenJDK/openjdk-build has the build scripts. http://openjdk.java.net/groups/build/doc/building.html http://openjdk.java.net/groups/build/doc/building.html lists the requirements. What most people forget is that they need a boot JDK of version n-1 when building n (for example, 13 for building 14). We're building on 14. If you have specific issues, it might make sense to open a new ticket or even join our Slack workspace: https://adoptopenjdk.net/slack.html https://adoptopenjdk.net/slack.html
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/AdoptOpenJDK/openjdk-support/issues/152#issuecomment-668436571, or unsubscribe https://github.com/notifications/unsubscribe-auth/AQOXL26B7QRJXIR622N5BJLR663SFANCNFSM4PQBTO5A.

The change was merged on the 4th, so I'm not sure whether the build on the 5th got that already (might have started before). Can you check https://ci.adoptopenjdk.net/job/build-scripts/job/jobs/job/jdk8u/job/jdk8u-mac-x64-hotspot/682/? That's from yesterday, so it should have it.

Hallo Andreas Ahlenstorf
Thanks for the link of the new version.
I tested this version right away, but the bug still persists.
stefan@Stefans-MBP UltraMixer6 % java -version
openjdk version "1.8.0_272"
OpenJDK Runtime Environment (AdoptOpenJDK)(build 1.8.0_272-202008061713-b01)
OpenJDK 64-Bit Server VM (AdoptOpenJDK)(build 25.272-b01, mixed mode)
Thread 25 Crashed:: Java: Java2D Queue Flusher
0   libsystem_kernel.dylib        	0x00007fff6aa0f33a __pthread_kill + 10
1   libsystem_pthread.dylib       	0x00007fff6aacbe60 pthread_kill + 430
2   libsystem_c.dylib             	0x00007fff6a996808 abort + 120
3   libjvm.dylib                  	0x00000001046569e0 os::abort(bool) + 22
4   libjvm.dylib                  	0x000000010475f80c VMError::report_and_die() + 2148
5   libjvm.dylib                  	0x000000010465aef0 JVM_handle_bsd_signal + 523
6   libjvm.dylib                  	0x00000001046588d0 signalHandler(int, __siginfo*, void*) + 45
7   libsystem_platform.dylib      	0x00007fff6aac05fd _sigtramp + 29
8   libobjc.A.dylib               	0x00007fff69713954 lookUpImpOrForward + 63
9   libawt_lwawt.dylib            	0x0000000114498858 CGLSD_MakeCurrentToScratch + 69
10  libawt_lwawt.dylib            	0x000000011449896c OGLSD_MakeOGLContextCurrent + 99
11  libawt_lwawt.dylib            	0x00000001144b4cc7 OGLContext_SetSurfaces + 133
12  libawt_lwawt.dylib            	0x00000001144b8b3c Java_sun_java2d_opengl_OGLRenderQueue_flushBuffer + 1580
13  ???                           	0x00000001063c326a 0 +<PHONE_NUMBER>
14  ???                           	0x00000001063c493c 0 +<PHONE_NUMBER>
15  ???                           	0x0000000104f664e7 0 +<PHONE_NUMBER>
16  libjvm.dylib                  	0x00000001044c867d JavaCalls::call_helper(JavaValue*, methodHandle*, JavaCallArguments*, Thread*) + 1673
17  libjvm.dylib                  	0x00000001044c74e0 JavaCalls::call_virtual(JavaValue*, KlassHandle, Symbol*, Symbol*, JavaCallArguments*, Thread*) + 330
18  libjvm.dylib                  	0x00000001044c76c1 JavaCalls::call_virtual(JavaValue*, Handle, KlassHandle, Symbol*, Symbol*, Thread*) + 87
19  libjvm.dylib                  	0x0000000104517303 thread_entry(JavaThread*, Thread*) + 120
20  libjvm.dylib                  	0x000000010472299e JavaThread::thread_main_inner() + 130
21  libjvm.dylib                  	0x0000000104722863 JavaThread::run() + 409
22  libjvm.dylib                  	0x0000000104656517 java_start(Thread*) + 250
23  libsystem_pthread.dylib       	0x00007fff6aacc109 _pthread_start + 148
24  libsystem_pthread.dylib       	0x00007fff6aac7b8b thread_start + 15
—
Stefan Lorenz
<EMAIL_ADDRESS>phone:  0049 351 84 22 71 75
fax: 0049 180 355 56 88 50
onexip GmbH
Steglichstraße 38 | D-01324 Dresden | Germany
http://www.ultramixer.com
http://www.onexip.com

Am 07.08.2020 um 10:56 schrieb Andreas Ahlenstorf<EMAIL_ADDRESS>The change was merged on the 4th, so I'm not sure whether the build on the 5th got that already (might have started before). Can you check https://ci.adoptopenjdk.net/job/build-scripts/job/jobs/job/jdk8u/job/jdk8u-mac-x64-hotspot/682/ https://ci.adoptopenjdk.net/job/build-scripts/job/jobs/job/jdk8u/job/jdk8u-mac-x64-hotspot/682/? That's from yesterday, so it should have it.

The build I references built c5bd042db3 from https://github.com/AdoptOpenJDK/openjdk-jdk8u. That's the relevant section from jdk/src/macosx/native/sun/java2d/opengl/CGLSurfaceData.m:
#if USE_NSVIEW_FOR_SCRATCH
    [ctxinfo->context makeCurrentContext];
#else
    [ctxinfo->context clearDrawable];
    [ctxinfo->context makeCurrentContext];
    [ctxinfo->context setPixelBuffer: ctxinfo->scratchSurface
            cubeMapFace: 0
            mipMapLevel: 0
            currentVirtualScreen: [ctxinfo->context currentVirtualScreen]];
#endif

So the fix is in, looks similar on the other versions. So there might be another problem somewhere.
To eliminate other causes, can you test with http://jdk.java.net/16/, @onexipStefan?

thanks for the information.
Yes I know,
i would change it myself and build openjdk.
But I can't get it built with Mac, it stops at that point with the error message
The last part of Build.log
x86_64-normal-server-release/jdk/lib/server
[12] LDFLAGS_macosx := -framework CoreAudio -framework CoreFoundation -framework CoreServices -framework AudioUnit -framework CoreMIDI -framework AudioToolbox
[13] LDFLAGS_windows := /Users/stefanlorenz/Movies/Build_OpenJdk/jdk8u-xcode10/jdk8u/build/macosx-x86_64-normal-server-release/jdk/objs/libjava/java.lib advapi32.lib winmm.lib
[14] LDFLAGS_SUFFIX_posix := -ljava -ljvm
[15] LDFLAGS_SUFFIX_solaris := -lc
[16] VERSIONINFO_RESOURCE := /Users/stefanlorenz/Movies/Build_OpenJdk/jdk8u-xcode10/jdk8u/jdk/src/windows/resource/version.rc
[17] RC_FLAGS := -D "JDK_FNAME=jsound.dll" -D "JDK_INTERNAL_NAME=jsound" -D "JDK_FTYPE=0x2L"
[18] OBJECT_DIR := /Users/stefanlorenz/Movies/Build_OpenJdk/jdk8u-xcode10/jdk8u/build/macosx-x86_64-normal-server-release/jdk/objs/libjsound
[19] DEBUG_SYMBOLS := true
echo  "Compiling e_acos.c (for libfdlibm.dylib)"
echo  "Compiling e_asin.c (for libfdlibm.dylib)"
Compiling e_acos.c (for libfdlibm.dylib)
/usr/bin/clang -D_LP64=1 -D_LITTLE_ENDIAN -DMACOSX -DARCH='"x86_64"' -Dx86_64 -DNDEBUG -DRELEASE='"1.8.0-internal"' -D_ALLBSD_SOURCE -D_DARWIN_UNLIMITED_SELECT -DMAC_OS_X_VERSION_MAX_ALLOWED=1090 -mmacosx-version-min=10.9.0 -I/Users/stefanlorenz/Movies/Build_OpenJdk/jdk8u-xcode10/jdk8u/build/macosx-x86_64-normal-server-release/jdk/include -I/Users/stefanlorenz/Movies/Build_OpenJdk/jdk8u-xcode10/jdk8u/build/macosx-x86_64-normal-server-release/jdk/include/macosx -I/Users/stefanlorenz/Movies/Build_OpenJdk/jdk8u-xcode10/jdk8u/jdk/src/share/javavm/export -I/Users/stefanlorenz/Movies/Build_OpenJdk/jdk8u-xcode10/jdk8u/jdk/src/macosx/javavm/export -I/Users/stefanlorenz/Movies/Build_OpenJdk/jdk8u-xcode10/jdk8u/jdk/src/share/native/common -I/Users/stefanlorenz/Movies/Build_OpenJdk/jdk8u-xcode10/jdk8u/jdk/src/solaris/native/common -isysroot "/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.15.sdk" -iframework"/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.15.sdk/System/Library/Frameworks" -F"/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.15.sdk/System/Library/Frameworks/JavaVM.framework/Frameworks" -I/Users/stefanlorenz/Movies/Build_OpenJdk/jdk8u-xcode10/jdk8u/build/macosx-x86_64-normal-server-release/jdk/gensrc_headers -I/Users/stefanlorenz/Movies/Build_OpenJdk/jdk8u-xcode10/jdk8u/jdk/src/share/native/java/lang/fdlibm/include           -DTHIS_FILE='"e_acos.c"' -c  /Users/stefanlorenz/Movies/Build_OpenJdk/jdk8u-xcode10/jdk8u/build/macosx-x86_64-normal-server-release/jdk/objs/libfdlibm/e_acos.d -o /Users/stefanlorenz/Movies/Build_OpenJdk/jdk8u-xcode10/jdk8u/build/macosx-x86_64-normal-server-release/jdk/objs/libfdlibm/e_acos.o /Users/stefanlorenz/Movies/Build_OpenJdk/jdk8u-xcode10/jdk8u/jdk/src/share/native/java/lang/fdlibm/src/e_acos.c
Compiling e_asin.c (for libfdlibm.dylib)
/usr/bin/clang -D_LP64=1 -D_LITTLE_ENDIAN -DMACOSX -DARCH='"x86_64"' -Dx86_64 -DNDEBUG -DRELEASE='"1.8.0-internal"' -D_ALLBSD_SOURCE -D_DARWIN_UNLIMITED_SELECT -DMAC_OS_X_VERSION_MAX_ALLOWED=1090 -mmacosx-version-min=10.9.0 -I/Users/stefanlorenz/Movies/Build_OpenJdk/jdk8u-xcode10/jdk8u/build/macosx-x86_64-normal-server-release/jdk/include -I/Users/stefanlorenz/Movies/Build_OpenJdk/jdk8u-xcode10/jdk8u/build/macosx-x86_64-normal-server-release/jdk/include/macosx -I/Users/stefanlorenz/Movies/Build_OpenJdk/jdk8u-xcode10/jdk8u/jdk/src/share/javavm/export -I/Users/stefanlorenz/Movies/Build_OpenJdk/jdk8u-xcode10/jdk8u/jdk/src/macosx/javavm/export -I/Users/stefanlorenz/Movies/Build_OpenJdk/jdk8u-xcode10/jdk8u/jdk/src/share/native/common -I/Users/stefanlorenz/Movies/Build_OpenJdk/jdk8u-xcode10/jdk8u/jdk/src/solaris/native/common -isysroot "/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.15.sdk" -iframework"/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.15.sdk/System/Library/Frameworks" -F"/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.15.sdk/System/Library/Frameworks/JavaVM.framework/Frameworks" -I/Users/stefanlorenz/Movies/Build_OpenJdk/jdk8u-xcode10/jdk8u/build/macosx-x86_64-normal-server-release/jdk/gensrc_headers -I/Users/stefanlorenz/Movies/Build_OpenJdk/jdk8u-xcode10/jdk8u/jdk/src/share/native/java/lang/fdlibm/include           -DTHIS_FILE='"e_asin.c"' -c  /Users/stefanlorenz/Movies/Build_OpenJdk/jdk8u-xcode10/jdk8u/build/macosx-x86_64-normal-server-release/jdk/objs/libfdlibm/e_asin.d -o /Users/stefanlorenz/Movies/Build_OpenJdk/jdk8u-xcode10/jdk8u/build/macosx-x86_64-normal-server-release/jdk/objs/libfdlibm/e_asin.o /Users/stefanlorenz/Movies/Build_OpenJdk/jdk8u-xcode10/jdk8u/jdk/src/share/native/java/lang/fdlibm/src/e_asin.c
clang: error: clangno such file or directory: '/Users/stefanlorenz/Movies/Build_OpenJdk/jdk8u-xcode10/jdk8u/build/macosx-x86_64-normal-server-release/jdk/objs/libfdlibm/e_asin.d': error: no such file or directory: '/Users/stefanlorenz/Movies/Build_OpenJdk/jdk8u-xcode10/jdk8u/build/macosx-x86_64-normal-server-release/jdk/objs/libfdlibm/e_acos.d'
make[2]: *** [/Users/stefanlorenz/Movies/Build_OpenJdk/jdk8u-xcode10/jdk8u/build/macosx-x86_64-normal-server-release/jdk/objs/libfdlibm/e_asin.o] Error 1
make[2]: *** Waiting for unfinished jobs....
make[2]: *** [/Users/stefanlorenz/Movies/Build_OpenJdk/jdk8u-xcode10/jdk8u/build/macosx-x86_64-normal-server-release/jdk/objs/libfdlibm/e_acos.o] Error 1
make[1]: *** [libs-only] Error 2
Stefan Lorenz
<EMAIL_ADDRESS>phone:  0049 351 84 22 71 75
fax: 0049 180 355 56 88 50
onexip GmbH
Steglichstraße 38 | D-01324 Dresden | Germany
http://www.ultramixer.com
http://www.onexip.com

Am 07.08.2020 um 13:44 schrieb Andreas Ahlenstorf<EMAIL_ADDRESS>s similar on the other versions. So there might be another problem somewhere.

@onexipStefan Can we focus in this ticket on the crash and look at your build issues somewhere else? Otherwise it's hard to keep track what was tested, was needs to be done, ... For build issues, it might be best to join the #build channel on Slack.

Hallo Andreas Ahlenstorf
Bug is fixed with Nightly build Version Jdk8 272 b04
Issue can be closed
—
Stefan Lorenz
<EMAIL_ADDRESS>phone:  0049 351 84 22 71 75
fax: 0049 180 355 56 88 50
onexip GmbH
Steglichstraße 38 | D-01324 Dresden | Germany
http://www.ultramixer.com
http://www.onexip.com

Am 31.07.2020 um 13:50 schrieb Andreas Ahlenstorf<EMAIL_ADDRESS>The information provided is insufficient but thankfully the description sounded familiar so there's https://bugs.openjdk.java.net/browse/JDK-8244818 https://bugs.openjdk.java.net/browse/JDK-8244818. If the problem is not the same, please answer as many questions as possible from our issue template https://github.com/AdoptOpenJDK/openjdk-support/blob/master/.github/ISSUE_TEMPLATE/bug-report.md and provide a reproducer.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/AdoptOpenJDK/openjdk-support/issues/152#issuecomment-667081345, or unsubscribe https://github.com/notifications/unsubscribe-auth/AQOXL265PSXLJRSXN2ULI63R6KVXRANCNFSM4PQBTO5A.