text:
Changes control flow credits increases to a fixed amount of half init…

…ial max_data
See issue #983
Previous implementation of update_max_data() and related code has an issue that may result in
max_data increments becoming smaller over time and increasing the amount of MAX_STREAM_DATA
frames sent.
Another potential issue would be to have the difference between max_data and max_data_next
increasing over time.
The implemented solution sets a max_data_incr that is equal to half the initial max_data.
max_data_incr is used to determine when the stream is almost full, i.e. len > max_data - max_data_incr and to set the new max_data, i.e. max_data = max_data + max_data_incr. The
control flow credits always increase by half the initial max_data and the unspent control
flow credits (max_data - len) is never larger than the initial max_data.

max_data_incr is the value by which max_data will be incremented regularly, i.e. each time len > max_data - max_data_incr. Because the increment is triggered each time len is greater than max_data - max_data_incr and the new limit is set to max_data = max_data + max_data_incr, the available control flow credit is always less than 2x max_data_incr. More explicitly: max_data - max_data_incr < len < max_data < max_data + max_data_incr. By setting max_data_incr = max_data/2 using the initial value, the code ensures that the available control flow credit is always less than 2x ([initial]max_data/2) == [initial]max_data.
Supposing a symmetrical connection with a throughput equal to the initial max_data. Then after 1/2 RTT, the connection would have consumed max_data/2, triggering the increase max_data = max_data + max_data/2 from the receiver. The MAX_DATA frame would arrive 1/2 RTT later at the sender, just in time for refreshing the limit for the sender. I've not run test or graphs for that part but that would surely be interesting.
Regarding dynamically changing the control flow limit, my understanding is that the limit ensures the receiver does not over-commit on memory, and so I believe that whatever the BDP or other network properties, the network should not influence the control flow limit. Otherwise that would allow the network to force the receiver into committing more memory than intended. As I understand, this serves as a way to communicate the buffer limit to the sender while having a throughput otherwise unlimited (except for congestion control).
Feel free to correct if I'm wrong in anything. ;)

Regarding dynamically changing the control flow limit, my understanding is that the limit ensures the receiver does not over-commit on memory, and so I believe that whatever the BDP or other network properties, the network should not influence the control flow limit

That kind of depends. Autotuning flow control based on network perf is a common practice. To address the concern that you raise, what's needed is some receiver-local implementation control of the window scaling maximum. Right now quiche is quite basic - an application states the initial limit and we use that as the upper bound forever more.
Autotuning can indeed help implementations be more efficient or conservative with memory because they can afford to set lower initial limits for "light/slow" connections and allow the "heavy/faster" connections to make use of the freed up resource.

Let's be clear here though. The point of this PR is to fix a problem with the existing and currently used flow control update mechanism, the point is not to completely change it. That is out of topic for this PR.

I did the same quick and dirty test I've done in #983, and this time I've plotted the max_data and len of the stream. The first graph shows what's happening with the master branch, the second shows this PR. In the first graph, the linear increase in max_data is because the value is continuously increasing while on the second graphs, the stairs pattern shows that the value is updated quite less frequently.

Supposing a symmetrical connection with a throughput equal to the initial max_data. Then after 1/2 RTT, the connection would have consumed max_data/2, triggering the increase max_data = max_data + max_data/2 from the receiver. The MAX_DATA frame would arrive 1/2 RTT later at the sender, just in time for refreshing the limit for the sender. I've not run test or graphs for that part but that would surely be interesting.

Let's see the following example. I have the following dev environment:

MacOS (as a client) -> Linux VM (Debian Buster) (as a server)
server: running quiche-server at linux vm, from master branch.
client: run two different version, your PR and master right before your PR (5afe2882)
set linux qdisc as follows: this is to simulate 1000Mbit bandwidth/25ms rtt/0% packet loss. Note that this link's BDP is 3125000 (1000Mbit * 25ms)
tc qdisc add dev enp2s1 root netem delay 25ms 0ms rate 1000Mbit limit 2116 reorder 0 loss 0
Note that client's max_data and max_data as default will be 10000000 and 1000000. (see tools/apps/arc/args.rs)

Now, run the client with the following option, downloading 100Mbyte file.

with default option (--max-stream-data 1000000)
with --max-stream-data 4000000 (4000000 is just a higher number than the BDP above).

Here is what I get (total download time as seconds):

this PR + default: 6.031s
this PR + max-stream-data 4000000: 2.276s
master branch + default: 3.666s
master branch + max-stream-data 4000000: 2.304s

As I expected, current PR seems to start to throttle where current BDP > initial max_stream_data (max_data is not considered here because current default is pretty high - 10M - no impact on the current test)
On the other hand, we can see the problem of current master branch here but its behavior can be a separate discussion.

@Sparika I understand sending less frames can save the number of packets going back to the sender. (note that # of saved frames > # of saved packets because we need to send ACK and other frames to the sender) but from my perspective it should be balanced with the performance as well.

My latest commit implemented changes requested by @ghedo. Is there anything I should change to get the PR accepted?

authors: LPardue Sparika ghedo junhochoi


text:
cloudflare_custom_hostname not returning ownership_verification.type /value /name

Confirmation

[X] My issue isn't already found on the issue tracker.
[X] I have replicated my issue using the latest version of the provider and it is still present.

Terraform and Cloudflare provider version
Terraform v1.0.0
on darwin_amd64
Your version of Terraform is out of date! The latest version
is 1.0.1. You can update by downloading from https://www.terraform.io/downloads.html
Affected resource(s)
cloudflare_custom_hostname
Terraform configuration files
resource "cloudflare_custom_hostname" "testoutput" {
  custom_origin_server = "something.test.com"
  hostname = "random.test.com"
  zone_id = var.zone_id

  ssl {
    settings {
      min_tls_version = "1.2"
    }
    certificate_authority = "digicert"
    method = "txt"
    type = "dv"
    wildcard = false
  }
}

output "ownership_verification_type" {
    value = cloudflare_custom_hostname.testoutput.ownership_verification.type
}

output "ownership_verification_value" {
    value = cloudflare_custom_hostname.testoutput.ownership_verification.value
}

output "ownership_verification_name" {
    value = cloudflare_custom_hostname.testoutput.ownership_verification.name
}

Debug output

Panic output

Expected output
ownership_verification_name = "something_here"
ownership_verification_type = "txt"
ownership_verification_value = "somethingelse_here"
Actual output
ownership_verification_name = ""
ownership_verification_type = ""
ownership_verification_value = ""
Steps to reproduce
Use cloudflare_custom_hostname in your .tf and use output to print ownership_verification.(type/name/value)
Additional factoids

References

This isn't a bug but a new feature request. You also don't need to output the type as you already have that exported and set on your resource. The rest seem reasonable though.

looks like this has shipped in a subsequent release; https://cs.github.com/cloudflare/terraform-provider-cloudflare/blob/353c535ae25ffb6b4cd4d3b6f7ea48bf98b274b8/cloudflare/schema_cloudflare_custom_hostname.go#L123
please open a new issue if this isn't returning what you expect here.

source: gharchive/issue

authors: jacobbednarz mihaiturcu

license_type: permissive

license_source: github-api


text:
Revert access applications to use zone-id instead of account-id

Hi,
Please revert changes introduced in https://github.com/cloudflare/terraform-provider-cloudflare/pull/724 so that access resources prefer zone_id instead of account_id.
Zones path deprecation has been cancelled due the fact that you cannot create granular enough access-tokens in large enterprises without the zones. Currently we are unable to work with provider versions 2.10 forward.
Br,
Petteri

@piizei Are you able to please elaborate on the issue you're facing here? A production test case would be great to fully demonstrate the issue.
@Justin-Holmes do you know anything about the deprecation being reverted?

Hello,
@piizei is correct that we reverted our decision to deprecate zone-level routes. In terms of next steps, I was thinking we'd support both zone_id and account_id for Access resources and direct the request to the proper route. This will require us to add support for the zone-level endpoints in cloudflare-go before we can make this change. Assuming this approach sounds good to you @jacobbednarz, I can get started on this tomorrow!

Hi,
@jacobbednarz the problem is that after 2.10.1 release this does not work anymore:
provider "cloudflare" {
  api_token = var.api_token
}
resource "cloudflare_access_application" "app" {
  zone_id          = var.dns_zone_id
  name             = var.target_dns
  domain           = var.target_dns
  session_duration = "30m"
  auto_redirect_to_identity = true
  allowed_idps = var.allowed_idps
}

Reason being that our api_tokens don't have account level access. Change introduced in 2.10.1 tries to use level access even if just zone_id is provided. This results 403 for us when terraform runs.

authors: Justin-Holmes jacobbednarz piizei


text:
[nfc] 110824 assorted build cleanup

Roll Rust deps, rules_rust

The rules_rust update includes checksums for Rust 1.82, fixing a warning.

[build] Fix protobuf warning, compile_flags.txt
[build] Port libc++ defines from downstream to reduce include overhead

ASAN errors might be related

ASAN errors might be related

Thank you for approving. The crash disappears after re-running the ASan job, so it is unlikely to be caused by this (there are two libc++ flags being added but they are unrelated to ASan and are working well with downstream). There is a downstream V8 patch dealing with ASan issues for html-rewriter tests, perhaps the html-rewriter crash here has the same root cause.

source: gharchive/pull-request

authors: anonrig fhanau

repo: cloudflare/workerd


text:
chore(create-cloudflare): enable observability for Workers templates

What this PR solves / how to test
Adds Workers Observability to newly generated create-cloudflare projects.
Fixes WO-198
Author has addressed the following

Tests

[ ] TODO (before merge)
[ ] Tests included
[x] Tests not necessary because: Only adds an already tested setting to template configs

E2E Tests CI Job required? (Use "e2e" label or ask maintainer to run separately)

[ ] I don't know
[ ] Required
[x] Not required because: Only adds an already tested setting to template configs

Changeset (Changeset guidelines)

[ ] TODO (before merge)
[x] Changeset included
[ ] Changeset not necessary because:

Public documentation

[ ] TODO (before merge)
[x] Cloudflare docs PR(s): https://github.com/cloudflare/cloudflare-docs/pull/17028
[ ] Documentation not necessary because:

for posterity, approved under https://jira.cfdata.org/browse/CR-1000332

authors: lrapoport-cf zebp

repo: cloudflare/workers-sdk


text:
Can't Deploy with workers_dev = false

🐛 Bug Report
I'm trying to deploy to my cloudflare workers but when workers_dev = false, it gives me this error.
command: wrangler publish
Using namespace for Workers Site "__resources-workers_sites_assets"  Success ⬇ Installing wranglerjs... ⬇ Installing wasm-pack...  Built successfully, built project size is 11 KiB. Error:  There was an error fetching your project's routes.  Status Code: 403 Forbidden  Msg: {"success":false,"errors":[{"code":10000,"message":"Authentication error"}]}
The API access token has all the rights, still get this error in deployment.
Here is my wrangler.toml file
`name = "resources"
type = "webpack"
account_id = "xxx"
zone_id = "xxx"
workers_dev = false
route = "mydomain.com/*"
[site]
bucket = "./dist"
entry-point = "workers-site"
[env.staging]
name = "worker-dev"
route = "dev.mydomain.com/*"
[env.production]
name = "worker"
route = "prod.mydomain.com/*"`

operating system:
output of node -v:10.16.3
output of wrangler -V:1.6

When workers_dev = true, it deploy fine but URLs other than index.html shows this error:
could not find login/index.html in your content namespace
Thanks

I'd also double check to see if you have an environment variable that is overriding your wrangler.toml. CF_ACCOUNT_ID, CF_ZONE_ID, CF_API_KEY, CF_API_TOKEN, and CF_EMAIL will all override your various configuration settings.
If you still can't figure out what's happening here, you can run RUSTLOG=info wrangler publish, paste the output here, and we will take a look.

I'm just following the tutorial (https://developers.cloudflare.com/pages/tutorials/build-an-api-with-workers) and it doesn't specify how to change these values, so I'm running into this error at the "Publishing the API" stage, FYI.

authors: janzheng wpmaps

repo: cloudflare/wrangler


text:
[pages] serve returns a 200 response when no static asset is found.

This obviously messes with frameworks which do a:
const response = await env.ASSETS.fetch()
if (response.ok) return response

// else
return new Response(dynamic)

which is pretty common. We should return 404s if they are the asset does not exist.

Or better yet, remove serve and do-it-ourselves so we have complete control (and a smaller bundle).

Fixed in #105 . We'll hopefully get it released soon :)


text:
every record stored in etcd is encoded, formatted, and versioned

codec, envelope, json/proto marshalling code, all moved to bbs/format.
removed encoding/decoding from StoreClient, but kept StoreClient interface because it's still a little nicer that the raw etcd Client.
all db/etcd storage goes through ETCDDB.serializeModel and ETCDDB.deserializeModel, which in turn invokes format.Marshal and format.Unmarshal.
should work with existing diego-release.
some tests still need to be backfilled.

@tedsuo I've rebased this on top of master, my commits conflicted a lot with this since I touched errors everywhere, force-pushed to your branch, hope it's alright.

authors: luan tedsuo

repo: cloudfoundry-incubator/bbs

license_source: bigquery


text:
Refine the docs for deploying Diego

Add how to replace the system domain in CF and Diego manifest

Close #81


text:
creating stemcell timedout

Hello,
I have been trying to create a bosh directory on openstack. I am having a manifest file and I tried to deploy it and ended up with an error while creating the stemcell.

P:S: I can see the stemcell or partially created stem cell under private images in the cloud.
Thanks

Hey @manojRy
what is the state your image ends up in? Does it just take long to become 'active' or does it enter any 'error' state? Also: can you manually upload the same image using e.g. Horizon or the OpenStack CLI?
Out of curiosity: what kind of OpenStack installation are you running this against? Is this a DevStack or some local installation?

Hi @voelzmo . I have resolved it by adding state_timeout: 3600 in the bosh.yml file. This is because my cloud provider is taking more time than usual cloud providers. With the above line, I have extended it to an hour which by default is no more than 5 mins. I haven't tried it uploading manually, I am trying it on a devstack

authors: manojRy voelzmo


text:
Need to wipe off both partitions and devices

The original PR is https://github.com/cloudfoundry/bosh-agent/pull/190, but we found after OS reload, the ephemeral disk is not re-formatted, because it only wipes off the device, but doesn't wipe off partitions. This PR is very important to our IBM Cloud, the disk is not cleaned up  after stemcell upgrade, which caused many problems in our cf deployments. Please help review this PR. Thanks.
/cc @dpb587 @maximilien

Did anyone review the PR? Thanks.

repo: cloudfoundry/bosh-agent


text:
Add bosh custom passwords

We found that VMs deployed by Bosh for CloudFoundry were not sufficiently secure: the default password for root/vcap users (c1oudc0w) could not be changed easily.
What we want:

Possibility to change the password easily by resource_pool
Keep the use of Spiff to generate the final template

Our patch:

By default, the password is still c1oudc0w
Ability to set a new password overall

meta:
  ...
  default_env:
    # Default vcap & root password on deployed VMs (ie c1oudc0w)
    # Generated using mkpasswd -m sha-512
    bosh:
      password: $6$4gDD3aV0rdqlrKC$2axHCxGKIObs6tAmMTqYCspcdvQXh3JJcvWOY2WGb4SrdXtnCyNaWlrf3WEqvYR2MYizEGp3kMmbpwBC6jsHt0
    ...

Ability to set a password for each resource_pool

resource_pools:
    name: small_z1
    ...
    bosh:
      # Change default password:
      #   hashed password - Generate SHA hash using mkpasswd -m sha-512
      #   Generated hash for FT9KDyDoBqmeKQqEKoap
      password: $6$DVhgWycGMhiQYKsH$py04MGy0HVislvOLxtg/fx1RhycpbH7bSHBjxwZYC/KYg6gc59uN6LulsEk33WzggDQPBDjm0BM9iQXSzjITi1
    ...

@dieucao According to me, it should be backward compatible. By default, standard password is kept. This patch only allow to specify the tag bosh in resource_pools spec and being correctly merged by spiff.

Hi @fbonelle
The VMs deployed by BOSH are only accessible if you have the private ssh key. I believe the usernames and passwords are only there because the OS requires some sort of username and password.
If you remove your ssh keys, there should be no way to ssh into one of the VMs. Are you seeing different behavior?

Hi @jpalermo
What we have seen:

By default, there is no ssh keys on the VMs deployed by Bosh ?
For our deployments, we take VSphere or VCloud stemcell. With these stemcells, there is a default password that can be customized (threw bosh template).

I didn't really found a documentation or tutorial explaining how pushing ssh keys to deployed VMs with bosh yaml template file.
Thanks

@fbonelle
We confirmed what you are seeing. The behavior is different for VSphere and AWS. We'll see about getting this merged in.
Thanks for the follow up.

authors: fbonelle jpalermo

repo: cloudfoundry/cf-release


text:
UAAC CLI not validating scopes

Recently we went through small typo that delayed some of our troubleshooting efforts. Below is the same code we are trying to create a client(The actual scope and authorities are spelled wrong in the code).  Surprisingly, uaac never complained, but the authentication for this client keeps failing. After going through many hops, we have identified that the uaac command line is not checking scopes, we saw that its validating grant types, but not --authorities and --scope. Any specific reason that this syntax not validating? or something I am missing to interpret?.
Command With Typo:-
uaac client add testclient --name testclient --scope cloudcontroller.read --authorities cloudcontroller.admin --authorized_grant_types "authorization_code,refresh_token" --access_token_validity 3600 --refresh_token_validity 3600 --secret XXXXXX --redirect_uri https://concourse.domain.com/auth/uaa/callback --autoapprove true
Actual command:-
uaac client add testclient --name testclient --scope cloud_controller.read --authorities cloud_controller.admin --authorized_grant_types "authorization_code,refresh_token" --access_token_validity 3600 --refresh_token_validity 3600 --secret XXXXXX --redirect_uri https://concourse.domain.com/auth/uaa/callback --autoapprove true

Perhaps give the new uaa cli a go as to where the core team is putting active development.
https://github.com/cloudfoundry-incubator/uaa-cli

@drnic  I just compiled, but it seems I am getting "You must have a token in your context to perform this command". Any idea on how to log in, if I want to use default admin client account?.

uaa target https://192.168.50.6:8443 --skip-ssl-validation
uaa get-client-credentials-token admin -s <uaa_admin_client_secret>

@drnic Thanks.
I have tested this and have still same issues.  It's weird, that new uaa is exhibiting the same behavior. the typo is not validated for scopes, but validated for grant types.

Scopes can be anything. The resource servers can decide to use scopes x64bytes+salmon or hacker.bruce. It's not possible even for the UAA to validate the scopes, even less for the CLI.
Sorry for the 5 year delay btw.

repo: cloudfoundry/cf-uaac


text:
Fix org automation blocked by "backup-restore-team-bot"

This bot has been added with https://github.com/cloudfoundry/community/pull/448 The pr didn't add the bot to the contributors.yml. To unblock the org automation I will remove it.
If this bot is required please add it again also to the contributors.yml.

Yes, we've deleted the bot. I missed updating here. Thanks.

authors: beyhan dlresende

repo: cloudfoundry/community


text:
Multiple BBS instances think they are the leader: router-emiter not working properly.

Summary
We had a situation in our production Cloud Foundry, where two different BBS instances where thinking that they were the leader.
Both BBS were registered in consul, which return 2 ips for bbs.service.cf.internal.
The issue seems to happen after one of the consul nodes (cluster of 3x) is marked as failed.
Environment description

CF release: v240
Diego release: v0.1482.0
Setup: 2x route-emitters, 2x bbs servers, 3x consul servers.

Job ids: route-emiter: route_emitter/{0,1}, bbs = database/{0,1}, consul: consul/{0,1,2}

Observed symptoms
Due this situation, the route-emitter was connecting to the wrong BBS server and not getting the events of models.ActualLRPCreatedEvent. This delayed the creation of the routes to new instances up to 60 seconds,  until the route of sync+emit routes was running.
Checking the connections of the route-emitter, we found that there were connections to two different BBS:
# netstat -tpn  |grep 8889
tcp        0      0 10.0.17.8:55427         10.0.17.5:8889          ESTABLISHED 20622/route-emitter
tcp        0      0 10.0.17.8:55477         10.0.17.5:8889          ESTABLISHED 20622/route-emitter
tcp        0      0 10.0.17.8:51114         10.0.16.5:8889          ESTABLISHED 20622/route-emitter

This should not happen as only one should be active.
The consul service DNS responded two IPs:
$ host bbs.service.cf.internal
bbs.service.cf.internal has address 10.0.16.5
bbs.service.cf.internal has address 10.0.17.5

Logs and events:
You can find attached all the logs related to locks from the two BBS services in bbs.log. The issue starts around September 14th 2016, 19:41
In consul.log there are the logs related to the consul servers around September 14th 2016, 19:41.
In consul_agent_bbs.log there are the logs from the consul agent running on the BBS VMs. Some interesting messages there:
2016/09/14 19:40:41 [ERR] http: Request GET /v1/kv/v1/locks/bbs_lock?index=1214439&wait=15000ms, error: rpc error: No cluster leader from=127.0.0.1:53672

bbs.log.gz
consul_agent_bbs.log.gz
consul.log.gz

Specific Incident details (for reference)
Symptoms
Starting 18 September 2016 at 04:17, our monitoring based on the CF Smoke tests, started failing. The applications did not get their new routes registered after being push.
Investigating further, we found out that any application, after push, was taking up to 60s to get their routes registered.
We analised the route-emitter service, and discovered that:

route-emitter was not sending the corresponding nats message when the application was created. Logs route-emitter.watcher.handling-actual-create.complete and route-emitter.watcher.handling-actual-update.watcher-add-and-emit were missing.
But route-emitter was sending the routes after sync route-emitter.syncer.syncing and emit route-emitter.watcher.handling-actual-update.watcher-add-and-emit

This suggested that route-emitter was not receiving the event models.ActualLRPCreatedEvent from BBS. But in the logs of the active BBS, there were the related logs bbs.request.start-actual-lrp.* and the app was starting.
Root cause
Checking the connections of the route-emitter, we found that there were connections to two different BBS:
# netstat -tpn  |grep 8889
tcp        0      0 10.0.17.8:55427         10.0.17.5:8889          ESTABLISHED 20622/route-emitter
tcp        0      0 10.0.17.8:55477         10.0.17.5:8889          ESTABLISHED 20622/route-emitter
tcp        0      0 10.0.17.8:51114         10.0.16.5:8889          ESTABLISHED 20622/route-emitter

This should not happen as only one should be active.
The consul service DNS responded two IPs:
$ host bbs.service.cf.internal
bbs.service.cf.internal has address 10.0.16.5
bbs.service.cf.internal has address 10.0.17.5

Diagnosis
Since several days ago (Last lock acquired September 7th 2016, 17:31:12.157) BBS id 0 had the lock and was running as the unique BBS leader instance.
But on September 14th 2016, 19:41:32.837, the BBS id 1 managed to get the lock, becoming leader, but the BBS id 0 did not lose that lock.
This caused a situation of brain-split in the BBS cluster, but the impact was low as both BBS used the same backend (etcd). The problem was mainly the event distribution inside of BBS, but this was mitigated because all services, including route-emitter were running and keeping their connections open to the same BBS instance.
In some point in time, route-emitter re-established some of the connections, and it stoping getting the message models.ActualLRPCreatedEvent.
Question to investigate and report upstream: Why two BBS instance acquired the lock and remain in that state.
Resolution
Restarting the BBS id 1 did not solve the issue, as it was the instance holding the lock: The lock was being released and gained again.
Restarting the BBS id 0 did fix the issue. The BBS service got blocked when acquiring the lock in consul, and the service was de-registered from consul DNS.
All services with openned connections reconnected to the right BBS instance.

Thanks for the excellent report, @keymon. We'll investigate this right away.
Best,
Eric, CF Runtime Diego PM

Hi keymon,
Thanks for the detailed bug report. We had a few questions for you.

Are the logs you provided filtered at all, or are those exactly the same as what you downloaded from bosh (except for isolating the logs to a specific timeframe).

Where you doing a deployment around 19:40 on Sept 14th (the timestamp of the consul server logs)? It's interesting that so many nodes were unreachable by consul during that time.

In your deployment manifest, do the static IPs listed for the consul cluster match across VMs that list them? We've seen a similar problem before when some nodes were missing one of the three consul cluster IPs.

Also, we believe it's unrelated here, but in general, we recommend deploying an odd number of database (BBS) VMs if ETCD is your backend. The ETCD job is deployed on same VM as the BBS job by default, and ETCD itself is a raft cluster. Thus, having 1 BBS or 2 BBS's makes no difference to high availability. Elections won't be possible within ETCD when there are only 2 instances, so if one fails, the other won't be able to to be elected. For high availability with ETCD as the backend, we recommend deploying 3 BBS nodes.
Thanks,
@jvshahid and @jenspinney

Are the logs you provided filtered at all, or are those exactly the same as what you downloaded from bosh (except for isolating the logs to a specific timeframe).

I extracted all the logs them from our ELK platform. I think they are in the servers anymore in, they rotated. We use the logsearch distribution, and loggregator with metron agent. I got the logs filtering by jobname & component. I do not discard that some logs might have been drop.
The BBS logs were indeed filtered, to remove all the stuff not related to locks or start/stop. The query was like: NOT @message:bbs.request.* AND NOT @message:bbs.converge-lrps* AND NOT @message:bbs.executing-convergence* AND NOT @message:bbs.task-completion-workpool* AND NOT @message:bbs.actual-lrp-handler* AND @message:bbs*

Where you doing a deployment around 19:40 on Sept 14th (the timestamp of the consul server logs)? It's interesting that so many nodes were unreachable by consul during that time.

No, nothing AFAIK. No tasks run on bosh at that time.
I will have a look in AWS console and come back later.

In your deployment manifest, do the static IPs listed for the consul cluster match across VMs that list them? We've seen a similar problem before when some nodes were missing one of the three consul cluster IPs.

Yes, all the consul IPs are setup everywhere. We deploy consul agents in all the systems with the same config, including the 3x different IPs of the masters.

Also, we believe it's unrelated here, but in general, we recommend deploying an odd number of database (BBS) VMs if ETCD is your backend.

We deploy etcd in 3x dedicated servers, one in each AZ. So the etcd cluster is fine.

Where you doing a deployment around 19:40 on Sept 14th (the timestamp of the consul server logs)? It's interesting that so many nodes were unreachable by consul during that time.

No, nothing AFAIK. No tasks run on bosh at that time.
I will have a look in AWS console and come back later.

I cannot find anything at all in AWS console or in the servers. No interface errors. Only consul getting nuts.

I think the most confusing thing about the bbs logs is that bbs job with index 0 doesn't have any log lines after September 11th 2016; 09:05:12. Is it possible to get the full logs ?

Attaching all the logs from the vms "database" (bbs) from 2016-09-14 19:35 to 19:45
database-all.log.gz

I got more information. The database/0 vm stopped sending log messages on Sept 14 19:40, but it came back on Sept 17th at 17:19. But the VM was up all time. This correlates with the CPU usage:

In the ELK stack I don't have too many logs and I suspect that logs might been dropped. But I was able to recover the logs from the bbs on database.0 and consul_agent on database.0 and  database.1, please find them attached.
You can observe that on 17th at 17:18 there is a suspicious message, that might mean that database.0 registered back as a service:
    2016/09/17 17:18:28 [INFO] agent: Synced service 'bbs'
    2016/09/17 17:18:28 [INFO] agent: Synced check 'service:bbs'

database.1.consul_agent.stdout.log.gz
database.0.consul_agent.stdout.log.gz
database.0.bbs.stdout.log.gz

Adding logs from route_emitter/1. The route-emitter.watcher.handling-actual-create.complete was not being  logged from 09/19 10:57:39.51 to 15:35:03.05
route_emitter.0.route_emitter.stdout.log.gz

All raw logs from the host for BBS here:  https://s3-eu-west-1.amazonaws.com/hector-state/database.0.bbs.stdout.log.gz https://s3-eu-west-1.amazonaws.com/hector-state/database.1.bbs.stdout.log.gz

database/0 from 09/14 13:30:07.93
database/1 from 09/20 04:45:08.65. Other logs are in ELK, and have been attached already.

Note: the host bbs.service.cf.internal with two entries was happening between (at least) 09/19 10:57 and 15:35
bbs.service.cf.internal has address 10.0.17.5

@keymon i'm not sure what to do with these logs. It is really hard to make sense of them. I'm trying to find a timestamp in the logs where the two bbs instances where responding to requests or thought they had the locks but it is really difficult. bbs.log.gz makes it even more confusing, since the last log line that appear from job database index 0 is on 2016/09/07 but the raw logs have lock.started on the following dates:

2016/09/14
2016/09/17

which makes me believe that the bbs logs provided earlier are aggressively filtered. can you please provide the full bbs logs when you saw multiple bbs job ips in consul's dns response. Another question, are the time stamps mentioned in the previous comment in UTC or another timezone ?

I'm also curious to know if you have this property set to true for the consul_agents consul.agent.dns_config.allow_state ? if yes, what's the value of consul.agent.dns_config.max_stale ?

No, we don't have the stale setting enabled.
About the logs: in comment https://github.com/cloudfoundry/diego-release/issues/201#issuecomment-248671156 you can find all the raw logs we have.
I do not discard that some logs were dropped in the first ones.

Combined, sorted, and formatted all the lager log lines into one file combined-sorted-formatted.log in hopes of providing better readability. View formatted with
cat combined-sorted-formatted.log | less -r
Also stripped the lager log lines from the consul_agent stdout from database-0 and database-1.
logs-combined.tar.gz

@keymon Unfortunately, we are unable to make much progress diagnosing this issue due to the gaps in the logs and lack of information regarding what happened exactly to cause this. As a result we'll be closing this out for now, but please let us know if you happen to encounter it again or determine reproducible steps so we can investigate more on our end. If you happen to see it again, try to dump as many logs as soon as you can while they're still accessible. In the meantime we'll try to forcibly reproduce this issue on a test environment.

Thanks again, @keymon. I've prioritized a separate story in the Diego backlog for the team to attempt to reproduce this situation independently: https://www.pivotaltracker.com/story/show/131822105.
Best,
Eric

authors: caod123 ematpl jenspinney jvshahid keymon

repo: cloudfoundry/diego-release


text:
Issue with JQuery Sortable and cloudinary_js

Hi has anyone reported an issue with jquery sortables and cloudinary_js.
I get the following error in jquery when i have the following sortable code running.
$('#goals').sortable({
  axis: 'y',
  dropOnEmpty: false,
  handle: '.handle',
  cursor: 'crosshair',
  items: '.nested_fields',
  opacity: 0.4,
  scroll: true
})

this is using:
jQuery UI - v1.9.0 - 2012-10-15
jQuery v1.7.2
jquery.ui.min.js:7
Uncaught TypeError: Object function ( name, base, prototype ) {
var namespace = name.split( "." )[ 0 ],
fullName;
name = name.split( "." )[ 1 ];
fullName = namespace + "-" + name;
if ( !prototype ) {
	prototype = base;
	base = $.Widget;
}

// create selector for plugin
$.expr[ ":" ][ fullName ] = function( elem ) {
	return !!$.data( elem, name );
};

$[ namespace ] = $[ namespace ] || {};
$[ namespace ][ name ] = function( options, element ) {
	// allow instantiation without initializing for simple inheritance
	if ( arguments.length ) {
		this._createWidget( options, element );
	}
};

var basePrototype = new base();
// we need to make the options hash a property directly on the new instance
// otherwise we'll modify the options hash on the prototype that we're
// inheriting from

//	$.each( basePrototype, function( key, val ) {
//		if ( $.isPlainObject(val) ) {
//			basePrototype[ key ] = $.extend( {}, val );
//		}
//	});
basePrototype.options = $.extend( true, {}, basePrototype.options );
$[ namespace ][ name ].prototype = $.extend( true, basePrototype, {
namespace: namespace,
widgetName: name,
widgetEventPrefix: $[ namespace ][ name ].prototype.widgetEventPrefix || name,
widgetBaseClass: fullName
}, prototype );
$.widget.bridge( name, $[ namespace ][ name ] );

} has no method 'extend'

Closing this issue due to the time elapsed.
Please feel free to contact our support http://support.cloudinary.com or create a new ticket if you have any additional issues.

authors: nodrog taragano

license: MIT


text:
docs: Update README.md

Adding the Airplay pre-requisites for MacOS users

@LaetitiaAvrot Can you please add your signoff as explained here? https://github.com/cloudnative-pg/cloudnative-pg/pull/127/checks?check_run_id=6368133575

authors: LaetitiaAvrot mnencia

repo: cloudnative-pg/cloudnative-pg


text:
Add talks for pre-event

https://cloudnativedays.connpass.com/event/252961/

Review app
https://dreamkast-dk-1307.dev.cloudnativedays.jp

authors: dreamkast-cloudnativedays jacopen

repo: cloudnativedaysjp/dreamkast


text:
Update readme.md

Completed the text, thanks @cholmes!!
I've also added that this refers to a release of embeddings from an outdated mode, Clay v0.1. We already have Clay v1 which is much better. However, we have not released new embeddings simply becuase we are still trying to figure out what format (please suggest one :D). We are also holding on creating too many until we can figure out if we need to do any small tweaks for the model before launching any massive embedding creation.
If you have time, @yellowcap please review.

Awesome, merged! Sounds good on v1 - I hope we can get the conversation here moving pretty quickly, aiming to post widely on monday. Thanks for your contributions.

authors: brunosan cholmes

repo: cloudnativegeo/geo-embeddings-survey


text:
feat: add pid and ipc mode to task def

what

add ipc_mode
add pid_mode

why

support host level access for monitoring processes

/terratest

authors: dudymas milldr


text:
Update Terraform cloudposse/repository-webhooks-github to v0.13.0

what

Removed variables no longer available in the cloudposse/repository-webhooks/github module.
Supersedes #106

why

Version 0.13.0 removes hardcoded provider, so some variables have been removed in favor of instantiating the provider separately.

references

Upstream issue: https://github.com/cloudposse/terraform-github-repository-webhooks/issues/37
Upstream pull request: https://github.com/cloudposse/terraform-github-repository-webhooks/pull/40

@jamengual @joe-niland could we have this PR merged today?


text:
Could you please add S3 server access logging option to this module?

Please add logging option to this module so that users of this module can provide an s3 access logging bucket as input. It would be very useful to have since many security rules expect S3 server access logging to be setup for all S3 buckets. So anyone that has that restriction won't be able to use this module (per my understanding) and would have to manually add the server access logging through console.
So the next time, terraform plan will show this change & terraform apply it will revert the manual change back.

this module is to create such bucket. this is somewhat a chicken and egg problem, which one you create first?
if we do this we will be creating yet another bucket for logging and what will happen to that bucket, it will need a log bucket too, and so on....
CloudTrail can be used to log bucket access too so you could use that to log bucket access to the log bucket if you must

authors: gitmor jamengual


text:
revert: preserves tools inner in local drawer in AppLayout toolbar variant

Reverts cloudscape-design/components#2816
There is a regression: https://d21d5uik3ws71m.cloudfront.net/components/2dc1dbac64920a30fa81c761749f6ca825d93410/dev-pages/index.html#/light/app-layout/with-split-panel?appLayoutToolbar=true
This page renders an empty space on the right now

Can we merge this instead? https://github.com/cloudscape-design/components/pull/2828

We found a fix: https://github.com/cloudscape-design/components/pull/2828

authors: fralongo just-boris

repo: cloudscape-design/components


text:
GSD Request

--- GSD JSON ---
{
  "vendor_name": "Linux",
  "product_name": "Kernel",
  "product_version": "versions from v5.10.58 to before v5.10.89",
  "vulnerability_type": "unspecified",
  "affected_component": "unspecified",
  "attack_vector": "unspecified",
  "impact": "unspecified",
  "credit": "",
  "references": [
    "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=1340dc3fb75ea69221f4f5dcb0cbace55ad0331c",
    "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=ad338d825e3f7b96ee542bf313728af2d19fe9ad"
  ],
  "extended_references": [
    {
      "type": "commit",
      "value": "1340dc3fb75ea69221f4f5dcb0cbace55ad0331c",
      "note": "introduced"
    },
    {
      "type": "commit",
      "value": "ad338d825e3f7b96ee542bf313728af2d19fe9ad",
      "note": "fixed"
    }
  ],
  "reporter": "joshbressers",
  "reporter_id": 1692786,
  "notes": "",
  "description": "tee: optee: Fix incorrect page free bug\n\nThis is an automated ID intended to aid in discovery of potential security vulnerabilities. The actual impact and attack plausibility have not yet been proven.\nThis ID is fixed in Linux Kernel version v5.10.89 by commit ad338d825e3f7b96ee542bf313728af2d19fe9ad, it was introduced in version v5.10.58 by commit 1340dc3fb75ea69221f4f5dcb0cbace55ad0331c. For more details please see the references link."
}
--- GSD JSON ---

This issue has been assigned GSD-2021-1002811

repo: cloudsecurityalliance/gsd-database


text:
Segment Fault in js-shopping-cart example

I am trying to create a project from scratch based on the node js-shopping-cart example but when I try to run npm install I get the segmentation failure error:
[root@sleipnir shopping-cart]# npm clean-install

> protobufjs@6.8.8 postinstall /home/sleipnir/development/workspace/pessoal/cloudstate-templates/templates/node/shopping-cart/node_modules/protobufjs
> node scripts/postinstall

> grpc@1.22.2 install /home/sleipnir/development/workspace/pessoal/cloudstate-templates/templates/node/shopping-cart/node_modules/grpc
> node-pre-gyp install --fallback-to-build --library=static_library

node-pre-gyp WARN Using request for node-pre-gyp https download
[grpc] Success: "/home/sleipnir/development/workspace/pessoal/cloudstate-templates/templates/node/shopping-cart/node_modules/grpc/src/node/extension_binary/node-v64-linux-x64-glibc/grpc_node.node" is installed via remote

> cloudstate@0.0.2 postinstall /home/sleipnir/development/workspace/pessoal/cloudstate-templates/templates/node/shopping-cart/node_modules/cloudstate
> bin/download-protoc.js

Falha de segmentação (imagem do núcleo gravada)
[root@sleipnir shopping-cart]# ./bin/download-protoc.js
Falha de segmentação (imagem do núcleo gravada)
[root@sleipnir shopping-cart]# vim bin/download-protoc.js
[root@sleipnir shopping-cart]# vim bin/download-protoc.js
[root@sleipnir shopping-cart]# npm clean-install
npm WARN prepare removing existing node_modules/ before installation

> protobufjs@6.8.8 postinstall /home/sleipnir/development/workspace/pessoal/cloudstate-templates/templates/node/shopping-cart/node_modules/protobufjs
> node scripts/postinstall

> grpc@1.22.2 install /home/sleipnir/development/workspace/pessoal/cloudstate-templates/templates/node/shopping-cart/node_modules/grpc
> node-pre-gyp install --fallback-to-build --library=static_library

node-pre-gyp WARN Using request for node-pre-gyp https download
[grpc] Success: "/home/sleipnir/development/workspace/pessoal/cloudstate-templates/templates/node/shopping-cart/node_modules/grpc/src/node/extension_binary/node-v64-linux-x64-glibc/grpc_node.node" is installed via remote

> cloudstate@0.0.2 postinstall /home/sleipnir/development/workspace/pessoal/cloudstate-templates/templates/node/shopping-cart/node_modules/cloudstate
> bin/download-protoc.js

Falha de segmentação (imagem do núcleo gravada)

Node Version:
v10.15.2
NPM Version:
6.11.3
System:
Linux sleipnir 3.10.0-957.27.2.el7.x86_64 #1 SMP Mon Jul 29 17:46:05 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
CentOS Linux release 7.6.1810 (Core)
The project found in:
https://github.com/sleipnir/cloudstate-templates/tree/master/templates/node/shopping-cart

@sleipnir I tried to reproduce this in a controlled environment. I did:
>docker run -it --rm centos:7

[root@c52df629673a shopping-cart]# yum install epel-release
[root@c52df629673a shopping-cart]# yum install nodejs
[root@c52df629673a shopping-cart]# node --version
v6.17.1
[root@c52df629673a shopping-cart]# npm --version
3.10.10
[root@c52df629673a shopping-cart]# uname -a
Linux c52df629673a 4.9.184-linuxkit #1 SMP Tue Jul 2 22:58:16 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
[root@c52df629673a shopping-cart]# yum install git
[root@c52df629673a shopping-cart]# mkdir cs && cd cs
[root@c52df629673a shopping-cart]# git clone https://github.com/sleipnir/cloudstate-templates.git
[root@c52df629673a shopping-cart]# cd cloudstate-templates/templates/node/shopping-cart/
[root@c52df629673a shopping-cart]# npm install

which worked.

I tried then to match your environment with:
>docker run -it --rm centos:7
[root@2d3df5041ea5 shopping-cart]# curl -sL https://rpm.nodesource.com/setup_10.x | bash -

[root@2d3df5041ea5 shopping-cart]# yum clean all && sudo yum makecache fast
[root@2d3df5041ea5 shopping-cart]# yum install -y gcc-c++ make
[root@2d3df5041ea5 shopping-cart]# yum install -y nodejs
[root@2d3df5041ea5 shopping-cart]# node --version
v10.17.0
[root@2d3df5041ea5 shopping-cart]# npm --version
6.11.3
[root@2d3df5041ea5 shopping-cart]# yum install git
[root@2d3df5041ea5 shopping-cart]# git clone https://github.com/sleipnir/cloudstate-templates.git
[root@2d3df5041ea5 shopping-cart]# cd cloudstate-templates/templates/node/shopping-cart/
[root@2d3df5041ea5 shopping-cart]# npm clean-install

which also worked.
I think this is a segfault, yes ? Falha de segmentação (imagem do núcleo gravada) You might try to find from where it is coming getting a dump from your OS.

@sleipnir this could help to get the dump https://jvns.ca/blog/2018/04/28/debugging-a-segfault-on-linux/
I could no describe it better (check her other zines/posts, she's awesome)

This is cause of the problem
which npm
/opt/java/graalvm-ce-19.1.1/bin/npm

authors: marcellanz sleipnir

repo: cloudstateio/cloudstate


text:
DyNet crashes on this NER task

@kwalcock: @gcgbarbosa reports that the DyNet NER crashes when trained on the attached file. The crash does not seem to happen in the same place all the time...
@gcgbarbosa: can you please paste the cmd line you used for training here?
@kwalcock: can you please see if you can replicate this first?
Thank you both!
train-bottom-bottom-NER.conll.txt

Please also include the versions or branches of github repos and perhaps operating system and version, options like amount of Java memory, and that kind of thing.  A whole lot can go wrong.  core dumps, stack traces, java error files. and logs all help.

@gcgbarbosa, did this problem go away?  I haven't yet seen the command line or any other details that would help me investigate.

Hi @kwalcock, I wish the problem had disappeared, but no. I am just overwhelmed with other things. I will come back to this either by the end of the evening or tomorrow morning. Sorry about the delay.

No problem.  I can delay a long, long time.

This is the config file I am using:
mtl {
  maxEpochs = 50
  epochPatience = 5
  numberOfTasks = 1

  layers {
    initial {
      learnedWordEmbeddingSize = 128
      charEmbeddingSize = 32
      charRnnStateSize = 16
      c2i = "org/clulab/c2i-en.txt"
    }

    intermediate1 {
      rnnStateSize = 128
      useHighwayConnections = true
      numLayers = 1    }  }

  task1 {
    name = "En NER"
    train = "/work/gcgbarbosa/repos/research/data/train-bottom-bottom-NER.conll"
    dev = "/work/gcgbarbosa/repos/research/data/dev-NER.conll"
    test = "/work/gcgbarbosa/repos/research/data/test-NER.conll"
    type = "basic"

    layers {
      final {
        inference = "viterbi"
      }
    }
  }
}

Along with:
sbt 'runMain org.clulab.dynet.Metal -conf mtl-proteins.conf -train mtl-proteins'

I am using the default settings for the rest.
I am also running it again with the updated master branch so that I can give you the stack trace I was getting with the most updated version of the codebase.
I am running it on river.

And the stack trace:
stack-trace.txt

I can at least verify seeing the same result on river.  I have it running locally where I hope to be able to catch the exception in the act.

So far it has refused to crash locally, but it is spitting out more errors than it is making progress.  I'll pick a different random number pretty soon.
21:20:21.418 [main] INFO  org.clulab.dynet.SafeTrainer - Caught an invalid gradient exception: Magnitude of gradient is bad: -nan(ind). Reset gradient L2 norm to: 0.0

This is just luck, probably, but the program ended with this.  Would any of the output be useful?
22:17:11.567 [main] DEBUG org.clulab.dynet.Metal - Started evaluation on the development dataset for task 1 (En NER)...
22:23:44.918 [main] INFO  org.clulab.dynet.Metal - Accuracy on 11595 development sentences for task 1 (En NER): 56.36
22:23:44.918 [main] INFO  org.clulab.dynet.Metal - Precision on 11595 development sentences for task 1 (En NER): 8.32
22:23:44.918 [main] INFO  org.clulab.dynet.Metal - Recall on 11595 development sentences for task 1 (En NER): 84.05
22:23:44.918 [main] INFO  org.clulab.dynet.Metal - Micro F1 on 11595 development sentences for task 1 (En NER): 15.14
22:23:44.918 [main] INFO  org.clulab.dynet.Metal - 	P/R/F1 for label B-Gene_or_gene_product (18428): 87.87 / 83.34 / 85.54
22:23:44.918 [main] INFO  org.clulab.dynet.Metal - 	P/R/F1 for label I-Gene_or_gene_product (1275): 0.66 / 94.27 / 1.31
22:23:44.918 [main] INFO  org.clulab.dynet.Metal - 	P/R/F1 for label * (19703): 8.32 / 84.05 / 15.14
22:23:44.918 [main] INFO  org.clulab.dynet.Metal - Average accuracy across 1 tasks in epoch 9: 56.36
22:23:44.918 [main] INFO  org.clulab.dynet.Metal - Average P/R/F1 across 1 tasks in epoch 9: 8.32 / 84.05 / 15.14
22:23:44.918 [main] INFO  org.clulab.dynet.Metal - Best epoch so far is epoch 4 with an average F1 of 99.5, and average accuracy of 99.95.
22:23:44.918 [main] INFO  org.clulab.dynet.Metal - Epoch patience is at 0.
Disconnected from the target VM, address: '127.0.0.1:65156', transport: 'socket'

Process finished with exit code 0

Hmm... This going to be one of those non-deterministic errors...
I have also seen this error before, but rarely. I wonder if there is a way to prepare for whenever we see this error again, to understand better where it crashes in the C code?

It looks like all the output appears in mtl-proteins-epochN.* and task1.dev.output.N files, which I've saved.  I'll pick a different random number and try again.

Yeah, I don't think that's consistent, so repetition would be nice.
But the stack trace looks similar all the time.

It's something in the trainer and I'll look, but it would also be great to catch it in the act, write a unit test, know that it's fixed, etc.
[error]         at edu.cmu.dynet.internal.Trainer.update(Trainer.java:39)

My computer is not cooperating in this attempt at failing, but it looks like amy has gdb installed, so I will try there in the meantime.

It ran to completion again on my computer, but it did crash on amy and I am able to catch the SIGSEGV signal.  The *.so file used in fatdynet has been stripped of symbols, so it can't tell me much, but I can change that.  SEGV hints at a pointer problem rather than a problem with the math and pointers are hard to track down.
I notice that clab/dynet has been updated quite a bit recently and it is now passing unit tests again.  A merge results in quite a few conflicts that I have to study carefully.  At least one of the updates is a patch for a memory leak in the CUDA version which probably helps us.  They have worked on C# and Rust bindings a lot which to me indicates an extended life of the project.

I agree that keeping the .so files debuggable is worth it, even if it produces a larger library.
Great point about merging the latest dynet! I knew I forgot something at the WM meeting today: I wanted to ask about the same thing... Thank you! Maybe after solving the conflicts we can raise a PR with your changes?

It isn't feasible to not strip the symbols.  The file is 160MB without and can't be used with github.  I have to publish a debug version of fatdynet locally.

It never happens when someone is looking.  The program ran to completion on amy while being monitored by the debugger.  It lived for over four hours.  Maybe next time.

This is going to be hard...
Thank for trying!

I did not get back to this on Wednesday.  If @gcgbarbosa needs an answer before I find one, he can try another run.  So far 3/4 of mine have worked.  One thing extra I do is export _JAVA_OPTIONS=-Xmx16g.  Perhaps that has been helping.  I will try again soon.

I am looking into exceptions just now because of a different crash.  I will try to get something out of fatdynet better than "unknown exception".  However, this RuntimeException should be catchable in Processors.  I suspect there are exception conditions in dynet that can never be completely avoided.  Metal.train might be revised to catch the exception and do something like stop and use the previous best answer, move on to the next epoch, start over with a different random seed, at least end the training cleanly, etc.
[error] (run-main-0) java.lang.RuntimeException: unknown exception
[error] java.lang.RuntimeException: unknown exception
[error]         at edu.cmu.dynet.internal.dynet_swigJNI.Trainer_update(Native Method)
[error]         at edu.cmu.dynet.internal.Trainer.update(Trainer.java:39)
[error]         at edu.cmu.dynet.Trainer.update(Trainer.scala:5)
[error]         at org.clulab.dynet.SafeTrainer.update(SafeTrainer.scala:16)
[error]         at org.clulab.dynet.Metal.batchBackprop(Metal.scala:247)
[error]         at org.clulab.dynet.Metal.$anonfun$train$3(Metal.scala:169)
[error]         at org.clulab.dynet.Metal.$anonfun$train$3$adapted(Metal.scala:136)
[error]         at scala.collection.Iterator.foreach(Iterator.scala:929)
[error]         at scala.collection.Iterator.foreach$(Iterator.scala:929)
[error]         at org.clulab.dynet.SentenceIterator.foreach(TaskManager.scala:128)
[error]         at org.clulab.dynet.Metal.$anonfun$train$2(Metal.scala:136)
[error]         at scala.runtime.java8.JFunction1$mcVI$sp.apply(JFunction1$mcVI$sp.java:12)
[error]         at scala.collection.TraversableLike$WithFilter.$anonfun$foreach$1(TraversableLike.scala:789)
[error]         at scala.collection.immutable.Range.foreach(Range.scala:156)
[error]         at scala.collection.TraversableLike$WithFilter.foreach(TraversableLike.scala:788)
[error]         at org.clulab.dynet.Metal.train(Metal.scala:124)
[error]         at org.clulab.dynet.Metal$.main(Metal.scala:423)
[error]         at org.clulab.dynet.Metal.main(Metal.scala)
[error]         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[error]         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
[error]         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
[error]         at java.lang.reflect.Method.invoke(Method.java:498)
[error] Nonzero exit code: 1

Thanks @kwalcock !
I'll try to handle this one better.

I've got the error handling largely revised so that fewer problems from C++ should map onto unknown exception and more should show their messages.

I'm not sure this will make a difference, but two bug fixes just went into DyNet which I ran into while in the test portion of an example program looking for memory leaks: https://github.com/clab/dynet/pull/1627 and https://github.com/clab/dynet/pull/1593.

I'm not sure this will make a difference, but two bug fixes just went into DyNet which I ran into while in the test portion of an example program looking for memory leaks: https://github.com/clab/dynet/pull/1627 and https://github.com/clab/dynet/pull/1593.

Thank you Keith!!
On Sun, Jan 17, 2021 at 13:57 Keith Alcock notifications@github.com wrote:

I'm not sure this will make a difference, but two bug fixes just went into
DyNet which I ran into while in the test portion of an example program
looking for memory leaks: clab/dynet#1627
https://github.com/clab/dynet/pull/1627 and clab/dynet#1593
https://github.com/clab/dynet/pull/1593.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/clulab/processors/issues/429#issuecomment-761878794,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAI75TWA6A7DQZZPLQLDSITS2NFLZANCNFSM4SRBUGBA
.

Thank you Keith!!
On Sun, Jan 17, 2021 at 13:57 Keith Alcock notifications@github.com wrote:

I'm not sure this will make a difference, but two bug fixes just went into
DyNet which I ran into while in the test portion of an example program
looking for memory leaks: clab/dynet#1627
https://github.com/clab/dynet/pull/1627 and clab/dynet#1593
https://github.com/clab/dynet/pull/1593.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/clulab/processors/issues/429#issuecomment-761878794,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAI75TWA6A7DQZZPLQLDSITS2NFLZANCNFSM4SRBUGBA
.

This crash no longer happens. Confirmed by @gcgbarbosa.

authors: MihaiSurdeanu gcgbarbosa kwalcock

repo: clulab/processors


text:
Shipyard variables Stored ships not set and Stored ships n model not updating correctly

Hi CmdrMcDonald,
Before I begin, I would like to thank you for all the time and hard work you've put into EDDI so all the rest of us can enjoy a truly immersive experience!
I have found two issues regarding shipyard variables after using the ((EDDI ship swapped)) event:
Issue #1: {INT:Stored ships} is currently NOT SET.
I have 2 ships in storage. I tried looking at {TXT:Stored ship n=1,2 model} and they are populated, so EDDI seems to know that I have 2 ships in storage. I have also checked the Shipyard tab in EDDI configuration and all 3 of my ships are listed.
Issue #2: {TXT:Stored ship n model} is not updating correctly.
I am using VoiceAttack to say {TXT:Stored ship n=1,2 model) after the ((EDDI ship swapped)) event to debug. What I found is if I swap from my Cobra into my Viper the variables for n=1,2 shows my Viper and Sidewinder as stored, and not my Cobra and Sidewinder. If I swap back to my Cobra the two ships showing as stored show up as my Cobra and my Sidewinder as opposed to my Viper and Sidewinder.
I have included both my EDDI.log and Ships.json files. Any help you can provide on this would be much appreciated. Thank you!
EDDI.zip
EDIT #1:
I just checked with ED Market Connector and it is not showing the correct ship I am in unless I do an update. I guess this won't be updated until my next ship swap or docking event.

{INT:Stored ships} will be set in the next release, although it will be known as {INT:Stored ship entries} to be consistent with other similar values.
The companion API can be a little slow, so obtaining up-to-date information on current ship Vs. shipyard ships can be tricky.  I've tweaked the existing code to attempt to handle this situation a bit better where it does have the information that it needs (e.g. swapping ships rather than purchasing a new ship).

I checked using ED Connector and the update there is also lagged.  I see your note #111 and I agree that would probably be the only way to permanently resolve this issue. Anyway, thanks for your work on this amazing plug-in!

This is fixed in release 2.2.0.

authors: cmdrmcdonald mikelimtw

repo: cmdrmcdonald/EliteDangerousDataProvider


text:
OpenWeatherMap Class Not Found Error (NOT Installed through Composer)

I wasn't able to install this through composer so I used php-download.com to pull the package from packagist, downloaded it as a zip and saved it on my server.
Here's the code where I called the API:
use cmfcmf_openweathermap_php_api_2_4_0\vendor\cmfcmf\openweathermap_php_api\Cmfcmf\OpenWeatherMap_Class;
use cmfcmf_openweathermap_php_api_2_4_0\vendor\cmfcmf\openweathermap_php_api\Cmfcmf\OpenWeatherMap\Exception as OWMException;

//Run Google Calendar API and Fetch Calendar Events
include '\cmfcmf_openweathermap_php_api_2_4_0\vendor\autoload.php';

$owm = new OpenWeatherMap('my API key in here');

I'm getting an error of "Fatal error: Class 'OpenWeatherMap' not found..."
I've tried several variations but can't get it to work. I wonder if it's related to my file structure. The webpage 'weather-test.php' is in the root folder. Here is the full structure showing where vendor/autoload.php and OpenWeatherMap are located.
Root Dir
file: weather-test.php
-\cmfcmf_openweathermap_php_api_2_4_0
--\vendor
    file: autoload.php
---\cmfcmf
----\openweathermap_php_api
-----\Cmfcmf
------\OpenWeatherMap
         OpenWeatherMap_Class.php

Thank you in advance.

Hi @GermanPearls,
I highly recommend to use composer – what exactly did not work when you tried?
I've also looked at the download provided by php-download.com: You'll have to first require("vendor/autoload.php") before you can use any of the classes of this project. Then you should use these imports:
use Cmfcmf\OpenWeatherMap;
use Cmfcmf\OpenWeatherMap\Exception as OWMException;

Thank you for your time @cmfcmf .
I didn't use composer because I have no command line access to my server.
I've tried what you suggested. However, because of my file structure, I used:
include '\cmfcmf_openweathermap_php_api_2_4_0\vendor\autoload.php';

I still get the class not found error. Any other thoughts?
Thank you.

It's working.
I'm not sure the root cause of the original error but here are the changes I made to get it to finally work.
I removed the extra directory level. In addition, I found that, during troubleshooting, I changed the directory name to include _ instead of -
Thank you for your help (and for the use of the package).

authors: GermanPearls cmfcmf

repo: cmfcmf/OpenWeatherMap-PHP-Api

license: mit


text:
Decouple the DataTable pointer from the plan objects

We now have the storage::DataTable pointer inside many plan objects, such as AbstractScanPlan, AnalyzePlan, DeletePlan, InsertPlan, and UpdatePlan.  This prevents us from shipping the plan objects around or using the "what-if" API on the brain side.
I'll take SeqScanPlan for example. Instead of getting the table pointer and storing it in the plan object here:
https://github.com/cmu-db/peloton/blob/master/src/optimizer/plan_generator.cpp#L82
We should directly store the database oid and table oid. And then at the query execution/compilation time, we should get the TableCatalogObject using the `oid's with this API:
https://github.com/cmu-db/peloton/blob/master/src/include/catalog/catalog.h#L224
Then we can get the table name, database name and the schema name.
Finally we can use this API to get the table object pointer:
https://github.com/cmu-db/peloton/blob/master/src/include/catalog/catalog.h#L203
Everything should go through the catalog.

I will assign this to @Zeninma once he joins the group on Github.

I am having a problem while doing the decoupling. It would be great if I can get some help on this.
My approach for decoupling
In ordert to do the decoupling, I substitute storage::DataTable target_table in some plan objects with the corresponding database and table oid_t. The storage::DataTale *GetTable() is replaced with storage::DataTable *GetTable(concurrency::TransactionContext *txnt). The new GetTable method uses the database and tabe oid_t to first get DatabaseCatalogObject and GetTableObject via (https://github.com/cmu-db/peloton/blob/master/src/include/catalog/catalog.h#L218), (https://github.com/cmu-db/peloton/blob/master/src/include/catalog/catalog.h#L228) in Catalog. Then uses GetTableWithName (https://github.com/cmu-db/peloton/blob/master/src/include/catalog/catalog.h#L207) to get the storage::DataTable object.
My current Problem
The GetDatabaseObject, GetTableObject and GetTableWithName all take in the concurrency::TransactionContext as their arguments. However, under some circumstances, the transaction argument cannot be derived. Here is one such circumstance for instance:
In the PostgresProtocolHandler::ExecBindMessage method it calls a plan object's SetParameterValues function (https://github.com/cmu-db/peloton/blob/master/src/network/postgres_protocol_handler.cpp#L526). If the plan object is an IndexScanPlan, it will result in calling GetTable method(https://github.com/cmu-db/peloton/blob/master/src/planner/index_scan_plan.cpp#L88) and needs a concurrency::TransactionContext argument. However, the transaction object cannot be derived. I am not sure how to bypass this issue.

The storage::DataTale *GetTable() is replaced with storage::DataTable *GetTable(concurrency::TransactionContext *txnt)

I don't think that the plan objects should support GetTable anymore. That should be down from outside of the plan.

If the plan object is an IndexScanPlan, it will result in calling GetTable method and needs a concurrency::TransactionContext argument.

@tli2 It looks IndexScanPlan just needs the value type for a particular column in the index:
https://github.com/cmu-db/peloton/blob/master/src/planner/index_scan_plan.cpp#L88
Can we modify the binder to record this when it constructs the IndexScanPlan? The plan objects should never need to reference the catalog internally. All of that should be done on the outside.

authors: Zeninma apavlo malin1993ml

repo: cmu-db/peloton


text:
Fix pipeline when barrier column is all NAs part 2

Description
Followup to #1346. Set answer code 13 to NA before checking if col is all NA.
Changelog

variables.R

Fixes
In rare cases, vaccine_barriers <- ifelse(vaccine_barriers == "13", NA, vaccine_barriers) or vaccine_barriers <- ifelse(input_data$V15b == "13", NA, input_data$V15b) will make a column all NA when it wasn't before. This happens when the only non-NA responses have answer code "13".

@capnrefsmmat FYI. I'm thinking the more robust fix is to change split_options to return a list of NA if given a column of all NA. I don't think that messes up any of our other logic, but that'll need a more careful look and more code changes, so I'll do it in a separate PR.

repo: cmu-delphi/covidcast-indicators


text:
Adding auto test for ANM

Updates

Remove print commands and add assertions.
Add more simulated functions and save the data.
Fix some typos.

Test plan
python -m unittest TestANM.py      # should pass

@ErdunGAO You should fix the issues in this PR, and update your current PR (instead of doing it in next PR). This is why we need code review --- to guarantee the code quality is good before pushing the code into main trunk.
If you are not sure how to do it, let me know. Actually this should be really easy --- just commit to your forked repo with your new changes, and then create Pull Request.

In the new version, p_value_th is set to 0.1. The specific p_value is related to the distribution of the simulated data.
The test plan section is added with the screenshot of the testing results.

Please let me know if there is any further concern. Thanks!

Thanks for the great work! I have some nits that needs to be addressed.
BTW, I remembered that we discussed to use Haoyue's method to make sure our code logic doesn't change?
See #53 as another example.
In your specific case, you can do some easy things like: compute the current p_values using current code for 'TestData/pair0001.txt', and store it. And make sure the code can return the same result as your stored results. In this way, we can make sure when making future changes, if the code logic get changed, we can detect it.

Thanks for your kind suggestion! In the new version, simulated data have been well saved to ensure that consistent results can be obtained when meeting future changes.

Sorry for not making myself clear.
Do you have some time today to meet to discuss?

Sorry for not making myself clear.
Do you have some time today to meet to discuss?

Thanks a lot for your kind explanation!

The data simulation codes are well included in the new version.
We have saved the results for the fixed datasets, which can be recalled and compared to check future changes.

authors: ErdunGAO tofuwen

repo: cmu-phil/causal-learn


text:
Allow to set feasibility tolerance in optlang

Needs investigation

Related #33

When setting the model tolerance (e.g. via the "Configure COBRApy" dialog) this value is propagated to the feasibility tolerance of the underlying optlang model.

@axelvonkamp Can this be closed?

Yes.

authors: axelvonkamp sthiele

repo: cnapy-org/CNApy


text:
Graylog

Suggestion to add graylog in Logging
https://www.graylog.org/

Hi @zorel this is slated to be added in the next release. Thanks.

+1 Hopefully Graylog is added

Thanks @zorel, closing as this update was included in the most recent version https://github.com/cncf/landscape#current-version

@shawnpreissner why is graylog in logging greyed out its an opensource tool.

authors: raghu999 shawnpreissner zorel

repo: cncf/landscape


text:
[Tracking] Friendly organizations and foundations

As a follow-up task to https://github.com/cncf/wg-env-sustainability/issues/24
Plan who is going to reach out to which org/foundation.
Prepare before some basic communication: https://github.com/cncf/wg-env-sustainability/issues/25
Description
There are many organizations out there that have their very own perspective on sustainability and work on different levels and topics. As we want to be a bridge to those, being open to inviting them as well as collaborating with them to bring best practices to the cloud native community, we should document on the one hand side the activities and meetings with those.
In further steps, we can sharpen the collaboration and how to be better together.
Milestones

Overview of existing connections
Overview of potential connections
Decision on how and where to document and track the gatherings
...

Input

Discussion: https://github.com/cncf/tag-env-sustainability/discussions/16

Outcome

Todos

[ ] Cleanup the initialized document
[ ] Decide on how to track the meetings e.g. having a doc per org and they are all linked up at a Readme on this repo
[ ] Update the tracking documents with so far happened meetings and inputs
[ ] Plan concrete next steps
[ ] (is maybe part of this) Communication Cheat Sheet

Since the discussion has been locked, are we still able to add new organizations for this one?
I found that Cambridge University has Institute of Computing for Climate Science (https://twitter.com/Cambridge_ICCS) in which they also held Climate Informatics (https://cambridge-iccs.github.io/climate-informatics-2023/) conference next year. This seems really interesting.

Hey @mkorbi Sir. I would love to contribute by doing 2nd task in the TODO List. And can create the Doc or something to track the meetings.
Kind Regards,
Devarsh

@caradelia I think we need to give this issue a little rebirth under the Comms WG - I like the current dynamics with the GSF and wish we can grow it with other groups too

Is anyone working on this issue ?
If no , I would like to contribute

repo: cncf/tag-env-sustainability


text:
renamed some variables to prevent shadowing warning

Hi,
I normally compile with g++ using the warning switch -Wshadow=local , which gives me an alert when a variable in a function is shadowing another one such as a parameter of the function itself. By this switch I've noticed that a couple of files in nana have this problem (combox.hpp and place.hpp), so I've changed there the name of the variable.
Recompiled nana and tested : I get no more shadow warnings in my programs and they work fine.

Thanks,
     Marco

Hi, @crillion , this PR has been merged into branch develop-1.8. Thanks for your PR!

authors: cnjinhao crillion

repo: cnjinhao/nana


text:
feat: add @unocss scope

Summary by CodeRabbit

Chores

Updated dependencies to include @unocss package.
Removed @unocss/cli package from dependencies.

https://www.npmjs.com/search?q=%40unocss&csrftoken=WOJ3Nfa2fh5-F6Gn_v4M4jck6K3pwicFTUw8mxRICob

repo: cnpm/unpkg-white-list


text:
feat: enable sync to browser account

Implement #355

Here is an zipped build tested on Chrome on two PCs, which could successfully sync data with my google account.
Usage
Open two chrome installation (maybe in two PCs) and log in with same google account.  Then perform the following action for both of the chrome.

Download dist.zip
Unzip it into folder dist/
Click LOAD UNPACKED button and select dist/ path

First you add a tab to one of the better-onetab, refresh the page, wait for seconds.
Then you open another better-onetab you should see the added tab.
The time for sync depends on your network, you may need an proxy to access google. In my experience, it just several seconds with some refresh.
Development
If you want to test with your build, just add an key to manifest.json and build as below and build, you'll get an dist with stable ID which enables synchronize between multiple devices.
{
   "key": "MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA5MjBbnZCLkCC6nc4Ssp3u2zQ57Nw5G00CZ44CYfuBskn08BFVNgtzl5pd4Sc4RlTktbL1DzkgIE33PcKAd0+QXVaM7vpRE7ydN84+ONjIFNFFSJo+EQh7aIOffQy/aTMRTdGrzhxe49++VlKSFOKrO3Cb1k/GgMP+vWdlPztNzc2pgjHeG4vBvQubHWWb6udgPTr0LkFwmv84m48cXX6mvBaF1Taqk0qj0utFZpg2CFLIwTKIcTGrnA4/ijO1B7lz40pJxMYzq052F29vdxtI19oxtU/vqZ4b0Gcc4XC6vb7EwU4ZVvIACzQKgJixnUh8UJZyroDPu8buK4mJBbS4wIDAQAB",
}

In fact, storage.sync would lost data if you close or refresh page before it successfully save it to server. It didn't seem to store data locally like storage.local.
I think there's much more work to support storage.sync, therefore I think it's better to close it first.

In fact, storage.sync would lost data if you close or refresh page before it successfully save it to server. It didn't seem to store data locally like storage.local.
I think there's much more work to support storage.sync, therefore I think it's better to close it first.

After I removed the dist/ package and install version 1.4.7 from chrome extension store, I've got the same problem of data lost. Seems it's not the storage api causing the data lost. storage.sync behaves same with storage.local.
Please look into #349.

repo: cnwangjie/better-onetab


text:
Plasma wayland does not start with XDG_SESSION_ID set

Creating the following file: /etc/lemurs/wayland/Plasma
#!/bin/bash

exec startplasma-wayland

Plasma fails to start from lemurs unless I rebuild with the following line removed: https://github.com/coastalwhite/lemurs/blob/main/src/post_login/env_variables.rs#L42

Hey, thank you for reporting this issue. This is something that was mentioned in #108 as well and is a real issue. Interesting to see that it also effect KDE Plasma Wayland.
I am a bit hesitant to address this issue without some extra research. It seems that this comes from the interaction between SystemD(pam_systemd) and most Wayland environments. And not setting the environment variable could mean that other environments don't work anymore.
At the moment I am a bit swamped with other things, but I will look into moving this all forward in a couple of weeks.
Thank you again for the issue, I do really appreciate them. If you have any extra insight into the problem, please let me know.

This is now fixed in v0.3.1 :smile:

authors: coastalwhite msmol

repo: coastalwhite/lemurs


text:
Connection URI string still requires setting of a DATABASE variable.

I am attempting to connect with a mongolab uri provided by heroku. I store it as an evironment variable.
MONGOLAB_URI="mongodb://heroku_tchBR549:saaaalute@aa111111.mongolab.com:57934/heroku_tchBR549"

In my config.py, I declare it like so:
MONGOALCHEMY_CONNECTION_STRING = os.environ["MONGOLAB_URI"]

... whch results in the following:
File "/home/clownshoes/project/venv/local/lib/python2.7/site-packages/flask_mongoalchemy/__init__.py", line 116, in init_app
"(the %s setting)." % key('DATABASE'))
flask_mongoalchemy.ImproperlyConfiguredError: You should provide a database name (the MONGOALCHEMY_DATABASE setting).

The database name is the final value after the port number in the URI.
When I actually put the database name in like so:
MONGOALCHEMY_CONNECTION_STRING = os.environ["MONGOLAB_URI"]
MONGOALCHEMY_DATABASE="heroku_tchBR549"

I can successfully connect.
init_app actually gets the uri at line 119. It seems that the DATABASE variable check might do it's job in _get_mongo_uri just as well, and avoid this problem by declaring DATABASE by snipping it off the end of CONNECTION_STRING.  (unless I'm reading it wrong, and brother, I am prone to that . . .)

Similar issue 3 years later. Anyone know a fix ? Problem with my set up maybe?

authors: lysdexia pattoM

repo: cobrateam/flask-mongoalchemy


text:
cockroach debug zip for Kubernetes clusters

Re: cockroach debug zip
Issue Description
Customers running in K8s are not sure how to create debug.zip as the current instructions are setup for non K8s environment.
Suggested Resolution
The steps for creating debug.zip from K8s cluster should be provided.  Wonder if there is K8s operator already available for this from @keith-mcclellan.  cc @jseldess

@johnrk to track making sure the operator has a mechanism for grabbing diagnostic bundles from the cluster

@taroface I think this is in your product area but I tend to get CLI area conflated. Feel free to reroute if necessary.

Yup, this is me!

authors: keith-mcclellan lnhsingh robert-s-lee taroface

repo: cockroachdb/docs


text:
No-op UPDATE ONLY/DELETE ONLY syntax

Fixes #8500.
Note that this PR will conflict with the updates to UPDATE documentation in #8667.

This change is

Online preview: http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/e947fb722eddf964e5054fe710f3d54c70b2d365/
Edited pages:

v20.2/delete.md
v20.2/update.md

Online preview: http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/a94d2f37abaefd7a4c41202b189dd9c802712310/
Edited pages:

v20.2/delete.md
v20.2/update.md

authors: cockroach-teamcity ericharmeling


text:
quick fix to remove client pod from Operator doc

Temporarily removed steps in the K8s Operator docs that reference the secure client pod used to run SQL in the Helm and manual docs, as they were at odds with the current guidance.

This change is

Online preview: http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/86c3a8ee18c8204aa4c9bbb4a66d0b4e2e96c0b4/

authors: cockroach-teamcity taroface


text:
FrontEnd Mutations

UPDATE_WORKOUT  ( _id, username, email, savedWorkouts(workoutId, title, description) )

completed

repo: cococnde/git-fit


text:
New release

Hello,
Would it be possible to release the changes already on main?
Also it seems the discord invite link is not valid anymore.

Hey @voidcontext I hope to find some time next week to update the docs and publish a new release.
Meanwhile you can install the latest via cargo install --git https://github.com/cocogitto/cocogitto
Thanks for your patience.

Hey @voidcontext I hope to find some time next week to update the docs and publish a new release. Meanwhile you can install the latest via cargo install --git https://github.com/cocogitto/cocogitto Thanks for your patience.

There's no rush, for personal use I am already on the latest using the flake. But I am planning to introduce this tool to my team at work, and the auto bump fix would be useful to have.

:partying_face:  5.4.0

@oknozor that was quick, thank you!

authors: oknozor voidcontext

repo: cocogitto/cocogitto


text:
Invoker does not pass on SIGINT to child processes

Sending SIGINT ( Ctrl+Cing ) invoker should kill all the processes started by invoker, however this isn't so right now.
Best example for this is sidekiq; if you have a sidekiq process along with say, rails and you SIGINT invoker, then a sidekiq zombie process lingers on.  To cleanly exit all processes, invoker remove sidekiq is needed before sending SIGINT to invoker.

This is really weird one. I have pushed a fix that uses same code when you run invoker remove sidekiq vs when you stop invoker by pressing Control-C. If you see any errors logged in console when you press ctrl-c can you paste it here @swanandp ?
Cheers

https://github.com/code-mancers/invoker/commit/ea59cbdc4c1258cec7d1778ced6f7c0d9e387872 <-- fix btw. You may have to pull and build gem locally though

Thanks for the fix! No errors on the terminal that I can see, by the way.

So the fix does not fixes the problem?

So yes, upgrading to latest version did solve this issue. I had actually stopped using Invoker for a period of time because of this problem. Thanks for solving!

Cheers. New version 1.5.1 is out - let us know if you find anything else. thanks @swanandp  :D

authors: gnufied swanandp

repo: code-mancers/invoker


text:
feat: Adds GitHub Action for publishing new release

closes #424

Outdated.

repo: codeRIT/hackathon-manager


text:
Changed regex for url for amOnPage func

Motivation/Description of the PR

Description of this PR, which problem it solves
Resolves #2311

Applicable helpers:

[ ] WebDriver
[ ] Puppeteer
[ ] Nightmare
[ ] REST
[ ] FileHelper
[ ] Appium
[ ] Protractor
[ ] TestCafe
[x] Playwright

Type of change

[ ] :fire: Breaking changes
[ ] :rocket: New functionality
[x] :bug: Bug fix
[ ] :clipboard: Documentation changes/updates
[ ] :hotsprings: Hot fix
[ ] :hammer: Markdown files fix - not related to source code
[ ] :nail_care: Polish code

Having some issues with installing required dependencies to run tests because of wrong processor arch, but I tested it manually:
URL examples:
https://hello.com    // false
/                    // true
about:blank          // false
mailto:example@gmail.com  // false
/login           // true
/hello/world     // true
test-link        // true

Please add tests here if that's applicable https://github.com/codeceptjs/CodeceptJS/blob/3.x/test/helper/Playwright_test.js

@PeterNgTr I've added three tests, please take a look

Thank you!

authors: DavertMik PeterNgTr zaxoavoki

repo: codeceptjs/CodeceptJS


text:
[bug?] JUnit test result files are discovered and uploaded as coverage

I've been looking into why the newly integrated Codecov app does not post any coverage statuses to GitHub, with all the configuration mimicking what I've been doing in dozens of other repos.
While doing that, I noticed something strange, looking into the upload @ https://app.codecov.io/github/ansible/awx/commit/acd6b2eb2270ff3ebde9b229e0efecb6edee004e. It contains 2 XML files in the payload, while I expected that there would be one file with coverage in it.
So I looked into the job logs @ https://github.com/ansible/awx/actions/runs/10856012453/job/30129820229#step:5:53 and saw that codecov-cli finds 2 files (/home/runner/work/awx/awx/reports/coverage.xml and /home/runner/work/awx/awx/awxkit/report.xml) and decides that both need to be uploaded.
Interestingly, the next CI job step uploads test results and it discovers a different file — /home/runner/work/awx/awx/reports/junit.xml (but not /home/runner/work/awx/awx/awxkit/report.xml) —
@ https://github.com/ansible/awx/actions/runs/10856012453/job/30129820229#step:6:34.
I don't know if that's the reason Codecov can't post statuses to GH (they don't show up for pushed commits, nor PRs), but I figured that it might as well be related.
Anyway, I think this behavior is a bug and the uploader should only look for the files of the correct shape for any given upload type (coverage or test).
My suggestion is that codecov-cli should look into the files before uploading and at least verify they have the correct root-level XML node. Alternatively, a check against a good schema would be even better.
P.S. I've found some dead code in place you changed @joseph-sentry @ https://github.com/codecov/codecov-cli/blame/main/codecov_cli/services/upload/file_finder.py#L217-L219 — it's probably unrelated but contributes to confusion when reading it.
cc @rohan-at-sentry — there might be a deeper issue here, not sure if I should open an issue in the feedback repo..

UPD: it seems like this issue has nothing to do with GH statuses not showing up. It still persists after I started enumerating the files explicitly.

@webknjaz thanks for opening it.
For the meta question - Opening it here is fine because you have specific cli based feedback.
Status checks not showing up could potentially be un-related.  I see you opened https://github.com/codecov/feedback/issues/511 so I'm happy to continue that convo there.
WRT Test result files being uploaded as coverage, we'll take a look

Using disable_search: true turned out to be an unobvious workaround.

authors: rohan-at-sentry webknjaz

repo: codecov/codecov-cli


text:
angular-ui-bootstrap-bower should not be a dependency

I think this is used for the demos but it installs some dependencies that are not needed.

If I do not add it in bower.json then you can not run the demos locally unless you manually resolve angular-ui-bootstrap dependency. Why do you think it's wrong?

I have an app without bootstrap and my build scripts automatically include all bower dependencies (https://github.com/yeoman/generator-angular). This means that bootstrap UI is loaded into my app although it is not needed which breaks some components in the UI. I had to manually delete angular-ui-bootstrap from the package.json which will of course break if somebody else downloads the code for my app and installs the bower components.

Broke my build as well, because that particular dependency caused conflicts with the angular version. It uses angular < 1.3 instead of the 1.3.X series.  Make it a dev dependency?

@domoritz and @mtraynham guys, let me know if it works for you.

I would have left the other dependencies in the dependencies section as they are requirements for this library.  The angular-ui-bootstrap-bower dependency is only for this repo and demo purposes, thus it shouldn't be a requirement for an end-user to install.

The bower install angular-dragdrop command unnecessarily installs other dependencies in your project under bower_components/, now it will not because of devDependencies.

Not sure I follow.  Say I have an empty project and I want my first dependency to be angular-dragdrop.  So, I type bower install angular-dragdrop.  If I was an ignorant user or used wiredep, this would only attach angular-dragdrop to the index page.  angular nor jquery wouldn't be downloaded or attached because you didn't specify them as dependencies.
The angular-ui-bootstrap-bower is not a dependency for the end user, it is only a dev-dependency to showcase a running demo.  Follow?

Makes sense!

@codef0rmer are you making a new release?

@domoritz Yes.

Sweet. I shouldn't be so impatient ;-)

@domoritz hehe, done.

authors: codef0rmer domoritz mtraynham


text:
show logged-in status on the login page

So you don't have to log in unnecessarily

http://localhost:5000/login/

authors: TiffanyAndrews tmaybe

repo: codeforamerica/comport


text:
DEL: Non-functional UI elements from production

Remove:

[ ] Save results
[ ] Existing clients section
[ ] Login button
[ ] Alert that occurs after one submits a new client's info

Rationale:  Current version shows potential functionality.  Moving to production, therefore removing non-functional elements.

*[ ] @lianilychee test check boxes

Are you saying that you'd prefer that the demo go straight to filling out the form instead of going through the other steps first?

I made a pull request to the dev branch with a completely simplified (just the form) version a few days ago. Pinged you folks for a review of it, but I think you haven't had a chance to review it.
Also, there seemed to still be some discussion going on as to whether to go with such a simplified version or not.

I saw a comment in slack from Alec (@danaher2):

the search function is working, albeit with fake client data. My 2 cents is that I think we should only remove functionality that is truly not functional such as the login and creating a new client account. I think getting feedback on what has been built so far, including selecting a client and adding a visit is worthwhile.

I think we should remove the search functionality for now, because we can't save clients, and so the search functionality can't search real clients. I'd like to differentiate between a high fidelity mockup, which should be used in client interviews to get feedback on potential direction, and a minimum viable product, which should be include only features that provide current value.
While we want to include features like search in something like a high fidelity mockup, we should keep it out of our production release until case workers can use it to make their jobs easier.

(Taking it as a given that not all forms/questions/calculations have been implemented yet)
@carpeliam or any folks: Have you had a chance to clone and try the simplified version (https://github.com/knod/cliff-effects-1/tree/simple for a direct link)? If so, is it what you think the flow of the project is looking for right now? It's simplified down to just the form, but the goal is currently everything except the listed items, I can try to do a version like that too.

Starting work on item 1.

Starting work on item 2

Starting work on item 3

Starting work on item 4

The changes should now be deployed. Just to confirm, you don't want any of the other non-functioning elements removed?

@knod yup, that's right!

authors: carpeliam knod lianilychee nlkassad

repo: codeforboston/cliff-effects


text:
Two more parameters added in UserSchema

Description
Two more parameters added in UserSchema i.e. Score(number) and IsAdmin(boolean) for mentors. This will help us in differentiating b/w mentors and students. And Score will help in the student rating system.
Type of Change:

[x] Code
[x] New Feature

How Has This Been Tested?
This change passes all tests.
Additional Info (OPTIONAL)

Checklist

[x] My code follows the code style of this project.
[ ] My UI is responsive
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[x] All new and existing tests passed.
[x] My changes generate no new warnings
[x] The title of my pull request is a short description of the requested changes.

Screenshots

Original
Updated

** original screenshot **
** updated screenshot **

@Abhishek-kumar09 Please Review this, I will be happy to implement changes😄

Looks useful, thanks @shivambhatia5432

repo: codeforcauseorg/edu-server


text:
Web Analytics

As a product owner/UI designer, I would like to know how users are interacting with the site. Implement something like google analytics to help see usage statistics.

In process of setting up a Google Analytics account.

authors: Aaron-Lathrop ximsce

repo: codefordenver/Circular

license: isc


text:
About mysqli options MYSQLI_OPT_INT_AND_FLOAT_NATIVE

I am sorry to post the question here. I can't open the forum, I think because the Chinese network has blocked some websites, such as google. I have no time to configure a vpn recently.
Describe the bug
I have a problem, MySQL query results need to return integer and float, but mysql 5.7 defaults to return integer and float as a string type. So I need to use a configuration, MYSQLI_OPT_INT_AND_FLOAT_NATIVE. In CodeIgniter 3, I can do this:
$db->conn_id->options(MYSQLI_OPT_INT_AND_FLOAT_NATIVE, TRUE);
But CodeIgniter 4, this method is no longer useful.
$db->connID->options(MYSQLI_OPT_INT_AND_FLOAT_NATIVE, TRUE);
This doesn't work either.
I want to know, there is any good way  to use mysqli's options directly, without changing the framework source.
In addition, regarding MYSQLI_OPT_INT_AND_FLOAT_NATIVE, can you consider making a configurable item and implementing it directly in the Mysqli driver.
CodeIgniter 4 version
CodeIgniter 4.0.0 beta.2
Context

OS: Mac OS 10.14.4
Web server [Nginx 1.13.2]
PHP version [7.2.14]

There are a number of users in China who have no problem accessing the forum from there, and I have done so myself.  I don't know enough to answer your question, but it is definitely something for the forum, as we use github for bug tracking and planned work.
ps - I was unable to access google from China, but most sites, including our forum, were not blocked.
Jim Parry
Faculty, Computer Systems
Project Lead, CodeIgniterhttps://codeigniter.com

From: Haibin notifications@github.com
Sent: Wednesday, May 1, 2019 8:02 PM
To: codeigniter4/CodeIgniter4
Cc: Subscribed
Subject: [codeigniter4/CodeIgniter4] About mysqli options MYSQLI_OPT_INT_AND_FLOAT_NATIVE (#1979)
I am sorry to post the question here. I can't open the forum, I think because the Chinese network has blocked some websites, such as google. I have no time to configure a vpn recently.
Describe the bug
I have a problem, MySQL query results need to return integer and float, but mysql 5.7 defaults to return integer and float as a string type. So I need to use a configuration, MYSQLI_OPT_INT_AND_FLOAT_NATIVE. In CodeIgniter 3, I can do this:
$db->conn_id->options(MYSQLI_OPT_INT_AND_FLOAT_NATIVE, TRUE);
But CodeIgniter 4, this method is no longer useful.
$db->connID->options(MYSQLI_OPT_INT_AND_FLOAT_NATIVE, TRUE);
This doesn't work either.
I want to know, there is any good way to use mysqli's options directly, without changing the framework source.
In addition, regarding MYSQLI_OPT_INT_AND_FLOAT_NATIVE, can you consider making a configurable item and implementing it directly in the Mysqli driver.
CodeIgniter 4 version
CodeIgniter 4.0.0 beta.2
Context

OS: Mac OS 10.14.4
Web server [Nginx 1.13.2]
PHP version [7.2.14]

You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://github.com/codeigniter4/CodeIgniter4/issues/1979, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AAYOG33NB7DLRSQWC7TZE3DPTJKSXANCNFSM4HJ3CWNQ.

There are a number of users in China who have no problem accessing the forum from there, and I have done so myself. I don't know enough to answer your question, but it is definitely something for the forum, as we use github for bug tracking and planned work. ps - I was unable to access google from China, but most sites, including our forum, were not blocked. Jim Parry Faculty, Computer Systems Project Lead, CodeIgniterhttps://codeigniter.com
…

The forum can be accessed, but the account cannot be registered. If I am not mistaken, the forum registration uses the google verification code. Although it is not a big problem, it still takes a certain amount of work to overturn the wall. China's network Great Wall is a helpless and sad system.

The google captcha was removed some time ago.
Jim Parry
Faculty, Computer Systems
Project Lead, CodeIgniterhttps://codeigniter.com

From: Haibin notifications@github.com
Sent: Wednesday, May 1, 2019 10:10 PM
To: codeigniter4/CodeIgniter4
Cc: James Parry; Comment
Subject: Re: [codeigniter4/CodeIgniter4] About mysqli options MYSQLI_OPT_INT_AND_FLOAT_NATIVE (#1979)
There are a number of users in China who have no problem accessing the forum from there, and I have done so myself. I don't know enough to answer your question, but it is definitely something for the forum, as we use github for bug tracking and planned work. ps - I was unable to access google from China, but most sites, including our forum, were not blocked. Jim Parry Faculty, Computer Systems Project Lead, CodeIgniterhttps://codeigniter.com
...
The forum can be accessed, but the account cannot be registered. If I am not mistaken, the forum registration uses the google verification code. Although it is not a big problem, it still takes a certain amount of work to overturn the wall. China's network Great Wall is a helpless and sad system.

You are receiving this because you commented.
Reply to this email directly, view it on GitHubhttps://github.com/codeigniter4/CodeIgniter4/issues/1979#issuecomment-488555005, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AAYOG32DVRAQT5MU5ZZJ6R3PTJZV3ANCNFSM4HJ3CWNQ.

I know is not a place to write about it, but...
unfortunately,  I think the easiest option is to extend Model class and add there required options.
I will be able to add code which will allow to do so using database's config, but I won't have time for writing tests and the same functionality for other db drivers :(

The google captcha was removed some time ago. Jim Parry Faculty, Computer Systems Project Lead, CodeIgniterhttps://codeigniter.com
…

Maybe the google captcha hasn't been removed yet....

Will investigate, thanks!
Jim Parry
Faculty, Computer Systems
Project Lead, CodeIgniterhttps://codeigniter.com

From: Haibin notifications@github.com
Sent: Thursday, May 2, 2019 6:54 AM
To: codeigniter4/CodeIgniter4
Cc: James Parry; Comment
Subject: Re: [codeigniter4/CodeIgniter4] About mysqli options MYSQLI_OPT_INT_AND_FLOAT_NATIVE (#1979)
The google captcha was removed some time ago. Jim Parry Faculty, Computer Systems Project Lead, CodeIgniterhttps://codeigniter.com
...
Maybe the google captcha hasn't been removed yet....
[1556802688333]https://user-images.githubusercontent.com/25802553/57077574-fba74280-6d1e-11e9-9f22-1af774d26f69.jpg
[1556802693129]https://user-images.githubusercontent.com/25802553/57077591-0661d780-6d1f-11e9-9e2b-14a0208bdfc4.jpg
[1556802706169]https://user-images.githubusercontent.com/25802553/57077599-0a8df500-6d1f-11e9-98be-37e8b45170b4.jpg

You are receiving this because you commented.
Reply to this email directly, view it on GitHubhttps://github.com/codeigniter4/CodeIgniter4/issues/1979#issuecomment-488682480, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AAYOG3ZWDWF5UXF6RNMB2I3PTLXAXANCNFSM4HJ3CWNQ.

I know is not a place to write about it, but...
unfortunately, I think the easiest option is to extend MySQLi/Connection or Model class and add there support for required options.
I will be able to add code which will allow to do so using database's config, but I won't have time for writing tests and the same functionality for other db drivers :(

Thanks for your suggestion, I extended the model. To use mysqli options, I need a real connection connID, but the connID will only exist when the query is actually connected to the database. So I had to use $db->initialize() first in the constructor of the model, then execute options(); I don't know is this will affect the efficiency of the on-demand connection.
it's ok, thank you, and thanks jim parry again~.

I used this stackoverflow answer and it works :
$this->db->mysqli->options(MYSQLI_OPT_INT_AND_FLOAT_NATIVE, true);

See #7265

authors: LoganTann jim-parry kenjis nowackipawel viosion