New Metric: Event Accessibility

This issue is created to collect comments about the rolling release of "Event Accessibility"
This metric can be found here: https://github.com/chaoss/xxxxxxx/xxxxxxx/xxxxxxx.md
See all release candidates: https://chaoss.community/metrics/
CHAOSS Metric Quality Checklist
This checklist is used for new and updated metrics to ensure we follow CHAOSS quality standards and processes. Below checklist items don’t have to be completed all at once: create the metric release candidate issue first and then start working on the checklist.
Process

[x] Create the “review issue” in the authoring WG’s repo for comments during review period and paste this template in
[x] Create pull request to edit or add metric to WG’s repo (after checking Content Quality and Technical Requirements below)
[ ] Add the new metric or metric edit to release notes issue in working group repo
[ ] Update the Metrics Spreadsheet
[ ] Create issue in CHAOSS/Translations repository to kick-off translation to other languages (please use the the translation issue template)
[ ] "Metric Candidate Release" label added to the metric release candidate issue.
[ ] Metric was added to website

When above steps are completed:

[ ] Announce new/updated metric on mailing list, newsletter, community Zoom call, and Twitter. This can be coordinated with the community manager.

Content Quality

[x] Required headings are filled in, including Questions.
[x] Description provides context to metric
[x] Objectives list sample uses for the metric and desired outcomes
[x] If any, DEI uses of the metric are included in Objectives
[x] Optional headings that have no content were removed
[x] Contributors section lists those contributors that want to be named
[x] The name of the metric is the same in (1) metric heading, (2) metric file name, (3) focus area, (4) metrics spreadsheet, (5) “review issue”, (6) translation issue, and (7) website

Technical Requirements

[x] Message in the metric markdown file that the metric will be part of the next regular release is at top of page and the links are correct (this is in the metric template)
[x] Metric file name is the full metric name and only contains lower case letters and hyphens (“-”) for spaces
[x] Images are included using markdown and relative links (as described in the metrics template)
[x] Images have at least one empty line above and below them
[x] Ensure images are placed in image folder and followed naming convention
[x] If new focus area is created, ensure focus area is added to wg repo readme and focus area folder readme
[ ] Within the focus area, add the metric in the table and provide the link to the metric and metric question
[x] Ensure tables within metric are converted as image and placed in the image folder (both original MD and screenshotted PNG format) and follow the naming convention
[x] No HTML code in the metrics markdown file

PR for this metric is here: https://github.com/chaoss/wg-dei/pull/404

Please add this metric to the focus area readme

Done! @klumb

Oh I did it too lol https://github.com/chaoss/wg-dei/pull/405. Should I just close this PR?

I already closed it :)
On Wed, Mar 2, 2022 at 5:20 PM Elizabeth Barron @.***>
wrote:

Oh I did it too lol #405 https://github.com/chaoss/wg-dei/pull/405.
Should I just close this PR?
—
Reply to this email directly, view it on GitHub
https://github.com/chaoss/wg-dei/issues/401#issuecomment-1057489095, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAFAGUE4THLAPQDOTQ2BT3DU57ZVJANCNFSM5PEXB5WQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you commented.Message ID:
@.***>

--
Mutual of Omaha Distinguished Chair of Information Science & Technology
Professor of Information Systems and Quantitative Analysis
College of Information Science & Technology
University of Nebraska Omaha
CV: https://bit.ly/2kftONr
Vice President
Omaha Parks Foundation
CHAOSS Board Member
https://chaoss.community/
@.***
he / him / his

This metric is ready for release.


Added AutoGPTQ readme and test

Added AutoGPTQ UINT4 to README.md (https://github.com/huggingface/optimum-habana/pull/279[)](https://github.com/huggingface/optimum-habana/commit/1e3ccc0fa5afae12cceea45868d8647ef9e48d33)
Added SRAM_SLICER_SHARED_MME_INPUT_EXPANSION_ENABLED envar to the readme, in AutoGPTQ
(https://github.com/huggingface/optimum-habana/pull/305)
Added gptq to test_text_gen (https://github.com/huggingface/optimum-habana/pull/307[)](https://github.com/huggingface/optimum-habana/commit/a9f4b5496cbfeb3f1c51ce2b0402775eb44cb62f)

@HolyFalafel , is this PR ready for v1.17? Please resolve conflicts against latest main.

DO NOT merge it yet, need to get approval first

@MrGeva Can you clarify if this is targeted for v1.17?

Please sync your PR with main/upstream and fix any merge conflicts. Thank you.

@HolyFalafel @libinta
Will this patch be merged? At present, Gaudi has been integrated into AutoGPTQ. But I didn't see OH to install this package in this patch. I made a patch to integrate the AutoGPTQ in tgi-gaudi and submitted a patch  for optimum. It works. Can you add  AutoGPTQ package installation in this patch?

Can you rebase and revise your patch if necessary, so that it merges cleanly with main?
Also do "pip install -U ruff; make style" and check for any issues.
In addition, please run "tests/ci/fast_tests.sh" after installing
pip install -e ".[tests]"
and any slow tests, e.g.,
GAUDI2_CI=1 RUN_SLOW=1 python -m pytest
tests/test_text_generation_example.py -v -s -k
and report the results here.

Can you rebase and revise your patch if necessary, so that it merges cleanly with main?
Also do "pip install -U ruff; make style" and check for any issues.
In addition, please run "tests/ci/fast_tests.sh" after installing pip install -e ".[tests]" and any slow tests, e.g., GAUDI2_CI=1 RUN_SLOW=1 python -m pytest tests/test_text_generation_example.py -v -s -k and report the results here.

@HolyFalafel
Thanks for this draft PR.
what is the status of this, if this is still needed:  Can you rebase, synch with top of main habana and follow the instructions to test it?
if not needed, please close.
thanks.


Fix Execution View Test

Fixing the failing tests for the NodeExecutionsTable
Type

[x] Bug Fix
[ ] Feature
[ ] Plugin

Are all requirements met?

[x] Code completed
[ ] Smoke tested
[x] Unit tests added
[ ] Code documentation added
[ ] Any pending items have an associated Issue

Complete description
Except the NodeExecutionsTable tests, this PR fixes the filters on the table to apply for future nodes that are manually added.
Tracking Issue
fixes https://github.com/flyteorg/flyte/issues/604

Do you plan on adding tests for ExecutionTabContent? I think we discussed it on Friday

yes. I'm on it


在介绍LeastActiveLoadBalance时,有一处笔误。

原文是:2.6.4 版本中的 LeastActiveLoadBalance 还要一个缺陷
修改后:2.6.4 版本中的 LeastActiveLoadBalance 还有一个缺陷
What is the purpose of the change
修复文档
Brief changelog
Follow this checklist to help us incorporate your contribution quickly and easily:

[x] Make sure there is a GITHUB_issue filed for the change (usually before you start working on it). Trivial changes like typos do not require a GITHUB issue. Your pull request should address just this issue, without pulling in other changes - one PR resolves one issue.
[ ] Format the pull request title like Fix UnknownException when host config not exist #XXX. Each commit in the pull request should have a meaningful subject line and body.
[ ] Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
[ ] Test your code locally by running docsite start, and make sure it works as expected.
[ ] Make sure no files under build directory is added.
[ ] If this contribution is large, please follow the Software Donation Guide.

thanks for your contribution


Bug when string passed in multi-screen apps contains spaces

From Ghica, and verified by Hal
I have this super simple app with 2 screens. You open the second screen, type something in the text box, the text should contain spaces, and then press return button.
The text in the first screen contains only the text before the first blank.
Strange!
Verified by Hal
This might have to do with the fact that values passed in intent.putextra are XML encoded.

I just tried this again, and the problem wasn't there.    Hmmm.....  Needs more investigation.

This is not a bug.  The bad behavior is being causes by the misuse of close screen with text to return a raw text value to another screen, which is rxpecting a JSON encoded string.    The way to fix this is to rename CloseScreenWithText to somethng that will not lead people into misusing it.   Maybe Return Raw Text to External App, and Return to External App?

I added a note to the tooltip for CloseScreenwithText saying not to use it when returning a value to an App Inventor screen.  That should help, although people might still ignore the advice.   I'm closing the issue.


How to install Hubot on wedeploy.com

Hello!
I want to install Hubot to my server but I don`t know how to do it on my server on wedeploy.com.
Please help! :)

Can you use docker on wedeploy?
https://hub.docker.com/r/rocketchat/hubot-rocketchat/


Remember page number

After you refresh the page, you can have table page number

Saving the state of the table on page refresh is already implemented. See demo5.html


Addition of links to Opportunities under Opportunities Hub and addition of effects on hovering the cards in Opportunities Hub

i)Addition of links to cards
whenever we click on opportunities like internships, the page moves to the internship site showing all available internships, similarly to all other cards.

ii)addition of effects or changing of color on hovering the cards.
I want to work on this
@codeaashu assign me this task with the labels gssoc-ext, hacktoberfest-accepted and level according to the issue

Hello @Shirisha-16, before diving into the features, please make sure to add your profile on DevDisplay. It’s the first priority for contributing to the project.

@ishap11 I am getting some error while adding my profile

Please help me in this

I noticed the issue and raised it as #202  because I thought we could solve it together. Why don’t you try to fix it first? If you get stuck, I’m here to help with some hints!

📢 Invitation to Join the DevDisplay WhatsApp Community!
We are excited to invite you to join the WhatsApp community of DevDisplay, where developers and contributors come together to collaborate and share their ideas.
Collaborative Support: If you are interested in working together with extensive support, we encourage you to join our community.
Open Source Contribution: If you would like to contribute to the DevDisplay open-source project, your participation is welcomed in our WhatsApp group.
By joining, you will have the opportunity to connect with like-minded individuals, discuss project developments, and contribute to our shared goals.
For more information and to join the community, please visit: Join DevDisplay WhatsApp Community.
We look forward to your participation!

H


fix url function variables - make them strings

@incuna/frontend please review
I broke stuff

thanks

👍


Fix the kestrel warnings for 2.6

latest OPC stack with new nodeset
stack now supports DataTypeDefinition on servers
2 files removed causing build errors and which had no dependencies
not officially tagged as release yet -- testing only for early birds

Can 2.6.0 be tested on a dev environment after this PR is completed?


Localization support

Major WIP, maybe more of a POC.
Added a few translations to act as examples, not going to add the rest until I'm / we're sure this is how to go about it.
Need to add server-side option for default language and language selector on the client. Also need to setup translations server-side for use in index.html and all the plugins/inputs (like what commands return).
Todo (missing stuff):

[x] Client settings option to change language
[x] Support switching language with page reload
[x] Complete en-US translations
[x] Server-side default language option
[ ] Tests
[ ] Finalize JSON layout

This basically works now. Just need to:

translate index.html before it renders
translate server log() calls
default language server setting (need to somehow access defaults in lounge.js)
write tests 😢

translate server log() calls

I don't think server logs should be localized, I don't think I've ever seen it done elsewhere. It also opens up for misinterpretations due to server logs being more low-level and detailed by nature. Server logs should be English only imo.

translated messages are bad. when you google an error, you would find the most results in english.
also, imagine someone opening a issue here, only able to provide a log in chinese or smth.

Makes my life easier 👍

I haven't reviewed but just took a random look through the PR.
This is very exciting, I can't wait! Pretty sure language files are going to flourish after that!!

Ref https://github.com/wycats/handlebars.js/issues/1360 and https://github.com/wycats/handlebars.js/issues/1361 and

Because of https://github.com/wycats/handlebars.js/issues/1360#issuecomment-313910281 (there won't be new features to Handlebars at least for now), how do we want to handle this? :(

There may be a solution we haven't thought of? @xPaw any ideas?

Should i rebase this or not worth the effort until handlebars updates? (which may be never...)
Comes down to if we want half-baked or not

If you can rebase, that would be awesome. I am still very much looking forward to get involved with this and would absolutely love for us to support multiple languages soon :)

Rebased to master and updated to translate new strings.

In the console I see
i18next::backendConnector: loaded namespace translation for language en-US ...
i18next::backendConnector: loaded namespace translation for language fr ...

 Shouldn't it just load the current or default language?

It also tries to load /locales/en.json and 404s. I remember you saying it will load the language.json then override that with language-COUNTRY.json, to allow for regional translations. I'm indifferent about this 404, but it would be nice to not have

The condense messages aren't translated at all

So much for a "quick check" on the pr :stuck_out_tongue: So happy to see this PR mostly working, and looking forward to it eventually being merged!

@MaxLeiter, I know this is going to be a huge pain, but would you mind rebasing this? I'd like to start reviewing it.

@astorije sure, but still need to decide how to handle different word ordering/insertion.
Should I go with
{{before}} {{middle}} {{end}}

?

@astorije sure, but still need to decide how to handle different word ordering/insertion.

Yes, that's precisely why I want to start reviewing it :)
I can't answer that question before I take a serious look at it. Just rebase and ignore that issue for now.

@MaxLeiter I really think we should avoid that as much as we can, which is why I want to spend some time on this PR and play with it, see what can be done. There are internationalization solutions for handlebars out there, I just need to experiment with them.

Closing until Vue is more fleshed out and implemented. Will probably need to be totally rewritten at that point


Folding: sketch quadraticization testing

@fabrizio-m you can continue on top of this, if you want.

Closing in favor of PR https://github.com/o1-labs/proof-systems/pull/2224


Changes for a rollback feature from ausmith

So only giving the rollback option for the most recent deploy, I can deal with that.


Look into calling setUnderlyingNetworks

It looks like this isn't causing a problem for Outline, but it still might be worth calling setUnderlyingNetworks in the VpnService just for maximum correctness.

Cool find. Does this fix, for example, the issue whereby apps set to use only wifi may shun the VPN?:
https://www.valuewalk.com/2018/05/wifi-and-vpn-issue-oreo-8-1-android-p/

Yes, that's the idea.  The exact behavior depends on the Android version, and indeed this doesn't seem to work quite right in 8.1, but it does help in some versions, especially 9.


ceilometer : Request returned failure status. Invalid OpenStack Identity credentials.

After installing ceilometer for most services (except swift), ceilometer command shows authentication error:
ceilometer alarm-list
WARNING (http:172) Request returned failure status.
Invalid OpenStack Identity credentials.

Logs gives the following:
tail /var/log/ceilometer/ceilometer-api.log

2016-12-12 15:51:40.744 4249 INFO urllib3.connectionpool [-] Starting new HTTPS connection (1): <IP_ADDRESS>
2016-12-12 15:51:40.758 4249 WARNING keystoneclient.middleware.auth_token [-] Retrying on HTTP connection exception: [Errno 1] _ssl.c:510: error:140770FC:SSL routines:SSL23_GET_SERVER_HELLO:unknown protocol
2016-12-12 15:51:41.260 4249 INFO urllib3.connectionpool [-] Starting new HTTPS connection (1): <IP_ADDRESS>
2016-12-12 15:51:41.277 4249 WARNING keystoneclient.middleware.auth_token [-] Retrying on HTTP connection exception: [Errno 1] _ssl.c:510: error:140770FC:SSL routines:SSL23_GET_SERVER_HELLO:unknown protocol
2016-12-12 15:51:42.279 4249 INFO urllib3.connectionpool [-] Starting new HTTPS connection (1): <IP_ADDRESS>
2016-12-12 15:51:42.294 4249 WARNING keystoneclient.middleware.auth_token [-] Retrying on HTTP connection exception: [Errno 1] _ssl.c:510: error:140770FC:SSL routines:SSL23_GET_SERVER_HELLO:unknown protocol
2016-12-12 15:51:44.299 4249 INFO urllib3.connectionpool [-] Starting new HTTPS connection (1): <IP_ADDRESS>
2016-12-12 15:51:44.317 4249 ERROR keystoneclient.middleware.auth_token [-] HTTP connection exception: [Errno 1] _ssl.c:510: error:140770FC:SSL routines:SSL23_GET_SERVER_HELLO:unknown protocol
2016-12-12 15:51:44.317 4249 WARNING keystoneclient.middleware.auth_token [-] Authorization failed for token
2016-12-12 15:51:44.318 4249 INFO keystoneclient.middleware.auth_token [-] Invalid user token - rejecting request

Looks like related to the issue with installing ceilometermiddleware

When troubleshooting issue https://github.com/AJNOURI/COA/issues/45, I recreated the user service ceilometer
tail /var/log/keystone/keystone-all.log

2016-12-15 04:27:55.782 1031 WARNING keystone.token.controllers [-] User f83ab8ce5420427784334e3df514de9d is unauthorized for tenant 10ecc50015f94cc68c62545f9a6d555b
2016-12-15 04:27:55.783 1031 WARNING keystone.common.wsgi [-] Authorization failed. The request you have made requires authentication. from <IP_ADDRESS>
2016-12-15 04:28:55.103 1031 WARNING keystone.token.controllers [-] User f83ab8ce5420427784334e3df514de9d is unauthorized for tenant 10ecc50015f94cc68c62545f9a6d555b
2016-12-15 04:28:55.103 1031 WARNING keystone.common.wsgi [-] Authorization failed. The request you have made requires authentication. from <IP_ADDRESS>
2016-12-15 04:28:55.831 1031 WARNING keystone.token.controllers [-] User f83ab8ce5420427784334e3df514de9d is unauthorized for tenant 10ecc50015f94cc68c62545f9a6d555b
2016-12-15 04:28:55.831 1031 WARNING keystone.common.wsgi [-] Authorization failed. The request you have made requires authentication. from <IP_ADDRESS>
2016-12-15 04:29:55.893 1031 WARNING keystone.token.controllers [-] User f83ab8ce5420427784334e3df514de9d is unauthorized for tenant 10ecc50015f94cc68c62545f9a6d555b
2016-12-15 04:29:55.894 1031 WARNING keystone.common.wsgi [-] Authorization failed. The request you have made requires authentication. from <IP_ADDRESS>
2016-12-15 04:30:55.940 1031 WARNING keystone.token.controllers [-] User f83ab8ce5420427784334e3df514de9d is unauthorized for tenant 10ecc50015f94cc68c62545f9a6d555b
2016-12-15 04:30:55.941 1031 WARNING keystone.common.wsgi [-] Authorization failed. The request you have made requires authentication. from <IP_ADDRESS>

openstack user list
INFO: urllib3.connectionpool Starting new HTTP connection (1): controller
INFO: urllib3.connectionpool Starting new HTTP connection (1): controller
+----------------------------------+------------+
| ID                               | Name       |
+----------------------------------+------------+
| 095d40706f004ba0a5afdc6fe326480e | nova       |
| 3157cfe3f44243e5bc2aaea007460b54 | cinder     |
|<PHONE_NUMBER>544418b95507cabfb33b66 | ajn        |
| 4ac4bb45dd504f53a027b79ca3e9f2e8 | admin      |
| 4c838d66c07b4ef6ad18927e09280b51 | glance     |
| 8cc6d64748df4ab7964ea3dc328381a8 | neutron    |
| df81fd7089c24f7e961634bdb7cda2b6 | demo       |
| ef2b0526b7c9460aaf43f6779a8e51a8 | swift      |
| f83ab8ce5420427784334e3df514de9d | ceilometer |
+----------------------------------+------------+

 openstack project list

INFO: urllib3.connectionpool Starting new HTTP connection (1): controller
INFO: urllib3.connectionpool Starting new HTTP connection (1): controller
+----------------------------------+-------------+
| ID                               | Name        |
+----------------------------------+-------------+
| 10ecc50015f94cc68c62545f9a6d555b | service     |
| 513a3eb3b3b742d09e89fffb64a53a6d | company XYZ |
| 62c353aacad140488aac55552b659334 | demo        |
| cdbcbc3eeb8a472c8abb2b67e749774c | admin       |
+----------------------------------+-------------+

Which means I forgot to assign the user to service tenant and assign an admin role:
As soonas I've done it:
keystone user-role-add --user=ceilometer --tenant=service --role=admin
And boom! It works.
ceilometer alarm-list

+----------+------+-------+---------+------------+-----------------+
| Alarm ID | Name | State | Enabled | Continuous | Alarm condition |
+----------+------+-------+---------+------------+-----------------+
+----------+------+-------+---------+------------+-----------------+


Please release new version to bower

Because I always encounter exception when destroy instance.
I discover the issue already fixed in GitHub repo, but bower is not yet.
So please update package in bower.

+1

+1

+1


533 missing validation errors

Triggered validation by touching all form elements on submit. This is what the page looks like now:

To make all fields consistent, I added an error message to the name field but I could also remove all error messages.

This makes sense to me code-wise, @zackcl do you think the error messages under each field are necessary? They get crunched in the space, I think for a required error a message might be overkill, it's pretty obvious what got missed if it turns red and has that asterisk.

@danoswaltCL I agree, I think it's better without the error messages under each field.

i love when PRs remove more lines than they add


feat: local debugging with wrangler

Setting up a local debugging environment was pretty difficult, so I thought I'd upstream it. The worker shares a local KV with pages, and @cloudflare/next-on-pages/next-dev provides KV binding interop with next dev. I also added npm run preview since Cloudflare recommend static testing before deployment.

Thanks for your contribution! I've been using GitHub Actions to deploy code to my private test page for testing, which is cumbersome to configure, so this should make debugging more efficient.

Glad I could help! If you use VSCode, pages works out-of-the-box but the worker needs a launch.json:
{
  "version": "0.2.0",
  "configurations": [
    {
      "name": "Wrangler",
      "type": "node",
      "request": "attach",
      "port": 9229,
      "cwd": "/",
      "resolveSourceMapLocations": null,
      "attachExistingChildren": false,
      "autoAttachChildProcesses": false
    }
  ]
}


Missing TypeScript typings

After building the package from the source code, TypeScript typing is missing. Is there any plan to add updated typings to https://github.com/DefinitelyTyped/tsd?

this language gets in the way of development and makes things that should be simple difficult. The additional compilation stage and gymnastics with types only worsen the situation.  In addition, neural networks are increasingly breaking into our lives, and in the end typescript will be supplanted by them. Don't resist, just relax and have fun.


Node 10 LTS expires in May

When will SPFx update to a newer version of Node that will be supported past May?

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

ID: 5bee09a8-022e-1b5a-4aab-d6e7c6216808
Version Independent ID: 49edce1e-f2be-e989-917f-c6b389363e2f
Content: Set up your SharePoint Framework development environment
Content Source: docs/spfx/set-up-your-development-environment.md
Product: sharepoint
Technology: sharepoint-framework
GitHub Login: @VesaJuvonen
Microsoft Alias: vesaj

MSFT has stated that the next version of SPFx, v1.12, will support Node.js v12.

Is there a public document like the roadmap where we can find this information?
SPFx Roadmap

I guess that could have been on the page you reference... usually this is shared in the bi-weekly community calls.

It's up on the site now.
https://docs.microsoft.com/en-us/sharepoint/dev/spfx/release-1.12.0

This still needs to be address as even in the the Microsoft Release Docs (https://docs.microsoft.com/en-us/sharepoint/dev/spfx/release-1.12.0) it states that 1.12 currently considered as deprecated due the unexpected regressions and you recommend usage of v1.11 which then by your documentation (https://docs.microsoft.com/en-us/sharepoint/dev/spfx/compatibility) is only compatible with Node 10.  So are you guys going to be releasing an updated SPFx that is compatible with Node 12+?


x/telemetry/upload: decide upload retry logic

The upload package keeps retrying unconditionally if the POST request ends with non-200 status code. code The upload program will keep retrying...
In case the upload fails due to transient network errors or some internal errors etc, a few retries before giving up completely make sense. But currently telemetry.go.dev upload server also returns http.StatusBadRequest, or other errors. In that case, retrying upload with the same data is not desirable.
Either make the upload package distinguish retryable and non-retryable status codes, or make the upload server never return an error if the upload shouldn't be retried.
cc @golang/tools-team @pjweinb @findleyr

Yes, something should be done. None of the alternatives seem perfect:

same behavior, but give up after 15 minutes. Then after a few weeks of this the report will be removed.
upload server doesn't take the report, but returns no error. Then the report is moved into the local telemetry/upload directory, and looks like it was uploaded.
upload server returns errors. What errors? (E.g., how many retryable erros are there for the upload process to think about?) What happens to the report for unretryable errors?

I am thinking combination of these:

4XX status code can indicate client didn't behave as expected and client shouldn't need to retry. Alternatively, upload server can return http OK with a non-empty response (e.g. rejected) so client distinguished rejected upload requests.
Client will keep retrying (same behavior as now - whenever the uploader runs) and after days of retrying, give up and delete the intermediate reports (.json). This handles 5XX cases.

From today's discussion:

4XX status code - client shouldn't retry.
Other status code - client should retry. Retry is done by leaving the intermediate json file untouched for 7days. Next upload processes will pick it up.

Not a release blocker. We will pick up in the next sprint.

Tentatively assigning to @pjweinb. Peter -- does this seem like something you could pick up?

Looking at the code...

Decision:
The uploader should not retry 4xx error codes, but should retry 5xx. When not retrying, the uploader can just delete the uploadable report in the local directory.
Additionally, uploading should be rate limited, but that is integrated with telemetry.Start as part of #65500.


TagBot trigger issue

This issue is used to trigger TagBot; feel free to unsubscribe.
If you haven't already, you should update your TagBot.yml to include issue comment triggers.
Please see this post on Discourse for instructions and more details.
If you'd like for me to do this for you, comment TagBot fix on this issue.
I'll open a PR within a few hours, please be patient!

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/41059

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/58225

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/86646

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/87355

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/87396


iPhone can not connect to local HTTP server over WiFi

I can not open static HTML pages after I run http-server on my MacBook in iPhone 6s iOS 9.2, neither in 'Safari' nor in 'Chrome' browser when using: http://ip:8080
I am able to open the pages on Android phones and I'm also able to open the pages if I turn MacBook's WiFi off and on, but if I change the page and refresh the browser, it again fails to load the page and says that server has stopped responding or that Safari could not connect to the server.
Resetting network settings in iPhone didn't help, nor did turning off Cellular Data in iPhone settings. Any idea what's wrong?

Does the http-server process in the command line crash?
Can you ping your MacBook from your iPhone, using apps like Fing?

No, pinging from iPhone shows 0 received packets. If I turn WiFi off and on on Macbook ping works, but if I leave iPhone idle for a few minutes and ping again it ping fails again.

Also I can't reproduce the problem using the same iPhone in a different location with different router and different MacBook.

Well, if pinging doesn't even work properly, then it's most likely not http-server's fault. Please check your network configuration & firewalls.
Also, try if you can reach your MacBook on other protocols, e.g. AirDrop or printer sharing (cups).

You might check if your Firewall blocks node from listening on a port.

Firewall is off.

So this issue can be closed then?


Add tests for SessionData and StudentModuleData and their JSON-adapted versions

Is this still necessary with methods like updateGrade?

@Berted StudentModuleData tests were added as part of #327. SessionData doesn't currently have any logic heavy component that requires testing.
However, we still need to test the Json adapted variants.


replacing "stringcase" python package with internal implementation

the python package "stringcase" is unmaintained with the latest pypi release in 2017.
stringcase is being removed  and replaced with an internal implementation.

Changes in this PR:

matter_idl: java and kotlin generators and  filters.py

src/controller/python/chip/yaml/runner.py

generated java and kotlin code; the removed stringcase package generated wrong code in constant case conversion of variables in the jinja templates:

example: COMMISSIONING_A_R_L_ATTRIBUTE_ID instead of the correct COMMISSIONING_ARL_ATTRIBUTE_ID

two golden tests used for scripts/py_matter_idl/matter_idl/test_generators.py were updated.

unit tests for the implemented functions

removing stringcase from various config files

Tested:

matter idl and the constcase conversion using ./scripts/codegen.py -g kotlin-class src/controller/data_model/controller-clusters.matter
Running unit test cases on the implemented functions: python scripts/py_matter_idl/matter_idl/test_case_conversion.py -v

Do we have a place for general internal python helpers? I can see stringcase replacement functions being useful elsewhere.
maybe....
I suppose we haven't needed them up until this point, ya?
@andreilitvin - thoughts? Is there a more central place to put this, or do you want this in the matter_idl folder?

i thought about putting it in src/controller/python/chip/utils since i also used these functions in src/controller/python/chip/yaml/runner.py but wasn't sure.
we also have other instances of similar "case changing" functions, in scripts/py_matter_idl/examples/matter_idl_plugin/__init__.py, so i can also refactor my stringcase replacement functions there too

Do we have a place for general internal python helpers? I can see stringcase replacement functions being useful elsewhere.
maybe....
I suppose we haven't needed them up until this point, ya?
@andreilitvin - thoughts? Is there a more central place to put this, or do you want this in the matter_idl folder?

i thought about putting these functions in src/controller/python/chip/utils since i also used these functions in src/controller/python/chip/yaml/runner.py ...but wasn't sure if they should be there.
we also have other instances of similar "case changing" functions, in scripts/py_matter_idl/examples/matter_idl_plugin/__init__.py, so i can also refactor my stringcase replacement functions there too

Please do not use utils (or support, core, helpers, base and such names that are graball). If we do want to reuse, we could have a separate package, with some name that is focused on strings, naming or something similar.
maybe matter_name_mangling or matter_string_casing or something like that. I think we may want to iterate: have this first to get the updates on generated files in, then create a separate package if we do find reuse utility


Version of Sabre/Dav

Hello thanks for the great adapter to flysystem .. We are implementing this and found we had a issue with some PROPFIND requests returning 408 (others seem fine)
After a few checks we have not established totally why that is but have discovered an update to 4.01 Sabre DAV solves the issues. Are you happy if we put in a PR to upgrade ?

friendly ping @frankdejonge :) looks like composer constraints mean this will happen now


Add badge for Marten

Marten is an awesome .NET Transactional Document DB and Event Store on PostgreSQL with over a million downloads on nuget. Would be great to get a badge created for it.
Logo url: https://github.com/JasperFx/marten/blob/master/documentation/content/images/emblem.png
Background color: White
Label Text: Marten

@jeremydmiller @mysticmind @oskardudycz @codinggorilla @jokokko thought it would be cool to get a badge done for Marten, If you'd like to see this one created then please give the issue a thumbsup and @MikeCodesDotNET will hopefully consider this 😄
I will attempt this week to see if I can try and create the badge myself. I took the Marten logo from the repo, but is there a png version available by any chance?

@tonykaralis I think you were requesting for a SVG version, have managed to exports the paths from the PNG file using GIMP and created an SVG file using Inkscape. Also created the badges using the Figma template file. The attached zip file contains the badges.
Below is the sample badge:

Marten_badges.zip
I will add the badges and the logo SVG file in Marten repo. You can close this issue opened here.
@MikeCodesDotNET Thanks for the wonderful project, the badges look great. 👍


build error kali

Hello.
iam trying to use this on my kali nethunter phone everyting went good untill i tried to build a payload.
it gives me the following error
http://imgur.com/a/RE2mK

https://github.com/nccgroup/Winpayloads/issues/21

It now gives me this. http://imgur.com/a/OqESo
It does not actually create the payload.

Please run with -debug
./winpayloads.py -debug

Doesnt do anything no debug showing atall and still same error

Duplicate https://github.com/nccgroup/Winpayloads/issues/40

I redownloaded it re ran the setup still gives the same error.

Please help me help you.
Please show output of ./winpayloads.py -debug

It doesnt give any debug output with that command?

Generate a payload while using that command

this it what it shows with debug command http://imgur.com/a/AYDcL

I have the same error :c

how can i fix it ?


"E.D.N. III Vista" Profile Background Misalignment

"E.D.N. III Vista" appears to be misaligned:
https://steam.design/#https://steamcdn-a.akamaihd.net/steamcommunity/public/images/items/226720/4a7f3784347cf0a24611a34cbfc7e4af748974da.jpg
Originally reported by FreeZ#1697 on Discord.
I attached the correct/fixed crops for measuring purposes.
The issue affects both https://next.steam.design/ and https://steam.design/

Please re test this on latest site version

Still not fixed after the update.

Solved by https://github.com/sapic/sapic/pull/55

Solved by https://github.com/sapic/sapic/pull/55


Crashes when downloading to files in multiple threads.

I got a report via email. Calling client.DownloadToFile() from multiple threads, sharing the same client can result in crashes.
This is on Debian 10 (Buster), with:
curl libs : curl 7.64.0 (x86_64-pc-linux-gnu) libcurl/7.64.0 OpenSSL/1.1.1c zlib/1.2.11 libidn2/2.0.5 libpsl/0.20.2 (+libidn2/2.0.5) libssh2/1.8.0 nghttp2/1.36.0 librtmp/2.3
compiler : g++ (Debian 8.3.0-6) 8.3.0
google-cloud-cpp: 0.13.0
crc32c: 1.1.0
To repro, create about 1,000 small objects (about 16KiB) in a single bucket, download them using 8 threads.

FWIW, I was able to reproduce this on Debian 10, but cannot reproduce on Ubuntu 16:04.  I think the main different is the libcurl version, will try this will different versions and see if I can repro that way.

Just tested on Ubuntu 16:04 with libcurl-7.64 and I got a crash pretty reliably.  Same platform with libcurl-7.66 no crash so far (32 threads 10,000 objects, running again as I write this).
I am inclined to believe this is a libcurl bug.  Time for me to read the change log for libcurl.

For what is worth, 7.65 seems fine too.  An anonymous contributor clued me to curl/curl#3904 which seems very likely to be the issue.  I will follow up with a PR to merge the test I used in these experiments.

I think with #3079 and #3080 we can close this bug.


Added Kadane's algorithm in Task 3

@codermind-divya Make separate commits. Remove the previous question code from commit and create a new PR


How to install this exactly?

I added:
Plug 'hwartig/vim-seeing-is-believing'

Reloaded the file, did :PlugInstall and opened the editor again.
Immediately I get this:
No such group or event: FiteType ruby nmap <buffer> <Enter> <Plug>(seeing-is-believing-mark-and-run)

What do I need to do to get this installed properly?

I believe "FiteType" is a typo, it should be "FileType".
Hopefully that will get you up and running!

That was it, thanks!


Filter in grading tab too keen

The filter function should wait for the user to hit return. Currently, the display of the keystrokes is very laggy because each keystroke leads to a turn-around with the server to get the filtered list of assessments:

Addressed by #897.

Reopened as the fix did not fully resolve the issue - some unknown behaviour is likely occurring that cannot be replicated in the development environment.

Prof @martin-henz, @geshuming and I have found the cause of the performance issues - we will try to implement a more satisfactory long-term fix.


Fix app.stop so doesn’t go on-fire briefly

Previously in app.stop, we set the serviceUp=false before setting
expectedState=stopping. This meant there was a race where we could
briefly infer the actual state as on_fire.
This caused failure of SoftwareProcessEntityLatchTest.testStopLatchBlocks:
the attributeWhenReady latch would abort because it received an
event saying that the app was on_fire, so the stop_latch completely
immediately.
The fix is simple: in app.stop, set the expectedSate=stopping before
setting serviceUp=false.
@neykov @geomacy you'll both be interested in this.

👍  LGTM. The change makes sense according to the description above.
On the question of reproducing this, I wasn't able to reproduce the test failure prior with master at date of 26th October (34eab17).  I caught up with master today and was able to get a couple of test failures by running 500 iterations of testStopLatchBlocks.   It's possible that recent changes have affected the visibility of the race that @aledsage mentions above.
Having pulled and merged this PR, however, I was able to run 1000 iterations without any failures.

Thanks @geomacy - merging now.


fix: Correct invalid React peerDep versions

Fixes #102
Simple typo

Will need to add a changeset! 😅

Was on my way to do

Haha no worries, just wanted to remind you after my quick checkmark 😅

Was just running into this right now. Awesome to see that a fix is already merged 👍


cmd/go: allow "go get" when outside a module in module mode

UPDATE: This is a feature request to be able to install a program/main package to a user's home directory (basically $GOBIN) outside of a module context.
Background
While dep, glide and other tools provide a way of fetching project dependencies, part of what they are missing which I think belongs in any official go get with versioning, is a way to install programs (tools, CLI, or a binary compiled from any main package) into a user's PATH (e.g. GOBIN, which may be relevant, even if GOPATH get's deprecated).

Please answer these questions before submitting your issue. Thanks!
What did you do?
$ vgo get<EMAIL_ADDRESS>
Example command only; but this would be the closest to how things currently work with go get.
What did you expect to see?
dep binary (in this case) installed to either $GOBIN, $GOPATH[0]/bin or $HOME/go/bin, in that order.
What did you see instead?
$ vgo get<EMAIL_ADDRESS>cannot determine module root; please create a go.mod file there

System details
go version go1.10 darwin/amd64
GOARCH="amd64"
GOBIN=""
GOCACHE="/Users/smyrman/Library/Caches/go-build"
GOEXE=""
GOHOSTARCH="amd64"
GOHOSTOS="darwin"
GOOS="darwin"
GOPATH="/Users/smyrman/.local"
GORACE=""
GOROOT="/usr/local/Cellar/go/1.10/libexec"
GOTMPDIR=""
GOTOOLDIR="/usr/local/Cellar/go/1.10/libexec/pkg/tool/darwin_amd64"
GCCGO="gccgo"
CC="clang"
CXX="clang++"
CGO_ENABLED="1"
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/sj/d5g1dfkd3g75ccz83k505v3r0000gn/T/go-build848907380=/tmp/go-build -gno-record-gcc-switches -fno-common"
VGOMODROOT=""
GOROOT/bin/go version: go version go1.10 darwin/amd64
GOROOT/bin/go tool compile -V: compile version go1.10
uname -v: Darwin Kernel Version 17.4.0: Sun Dec 17 09:19:54 PST 2017; root:xnu-4570.41.2~1/RELEASE_X86_64
ProductName:	Mac OS X
ProductVersion:	10.13.3
BuildVersion:	17D102
lldb --version: lldb-900.0.64
  Swift-4.0

@smyrman I think this is a genuine concern, but it isn't just about pulling down a specific version of a program; it is using vgo outside the context of a module. You'll get the same error if you omit the versuib @v0.0.0 specifier as well. vgo thinks you are trying to pull in a dependency; you are trying to install a program into GOBIN.
Maybe:
x/vgo: no longer supports installing an executable from outside of a module
?

You'll get the same error if you omit the versuib @v0.0.0 specifier as well. vgo thinks you are trying to pull in a dependency; you are trying to install a program into GOBIN.

@kardianos, thanks for the response. I am actually not concerned about the error message being unclear. This is meant as a feature request to (somehow) still be able to install binaries to a user's PATH, no matter what your current working directory is, similar to what we can with go get today. Even better, the possibility to install a program at as specific version. I believe a language package manger should not be just about dependencies.
I am not to particular about the syntax, but maybe there could be a flag like -home, -user or even -gopath, that allowed installing stuff to either $GOBIN or $GOPATH/bin. This would be similar to how e.g. pip works, for Python, to mention one, where if you use e.g. venev or virtualenv for a per-project experience, you can still add an option to pip to install tools to a user's home:

https://pip.pypa.io/en/stable/user_guide/#user-installs
https://docs.python.org/3/install/index.html#alternate-installation-the-user-scheme

Further, even though vgo deprecates GOPATH/GOBIN for project development, it's not necesarily right to deprecate GOPATH for other potentially valid use-cases, but that's probably another discussion, an not one I am particular interested in.
While OS package managers are good at doing exactly this kind of thing, there is often a delay for programs to be packaged, and language power users may prefer to use a language package manger for installing his/hers software, while also being able to pull down unreleased software, as we do today with

PS! I am also not concerned about this issue being solved right away, but it would be really cool to solve it before vgo goes main-line, if that's what going to happen.

Updated the description.

$ vgo get<EMAIL_ADDRESS>cannot determine module root; please create a go.mod file there

This clearly must work eventually. The thing I'm not sure about is exactly what this does as far as the version is concerned: does it create a temporary module root and go.mod, do the install, and then throw it away? Probably. But I'm not completely sure, and for now I didn't want to confuse people by making vgo do things outside go.mod trees. Certainly the eventual go command integration has to support this.
Note that installs already happen to $GOBIN or else $GOPATH/bin (so default $HOME/go/bin), not the modue tree.
Will mark NeedsDecision because we still need to work out how to do this, but yes absolutely the command must work.

does it create a temporary module root and go.mod, do the install, and then throw it away? Probably.

This is a reasonable approach, and have some obvious benefits, such as the result of go get<EMAIL_ADDRESS>not being affected by other tools installed on the system. To make a decision easier, I will supply an alternative approach and highlight some problems with it:
I suppose an alternative would be to have a "default" module that is used when a flag is provided to the go get command.
E.g. one could picture a default module in $GOPATH[0]/src/u (first entry of GOPATH) that is automatically created and used when the -user flag is given to the go get command line. This would let go get -user<EMAIL_ADDRESS>be semantically equivalent to:
#!/bin/sh
set -e
_module_path=$(echo $GOPATH | awk -F':' '{ print $1}')/src/u
mkdir -p ${_module_path}
cd  ${_module_path}
test -f go.mod || echo 'module "u"' > go.mod
go get<EMAIL_ADDRESS>
Some benefits

One easy flag to access a user-specific module for user-installed cross-project binaries.
The module path is preserved on disk, so power users could sync the folder via tools like Git or Dropbox to keep their tools with them at specific versions across machines.

Major drawback

Tool installation (e.g. installation of dep at a specific version as used in the example above), may be affected by (minimal) version selection of overlapping dependencies with other tools, leading to potentially weird bugs.

Conclusion
For me, I belive the drawback outweighs any benefit, and a temporary module root / mod.go root is the semantically correct solution; perhaps implementation wise the temporary module root and go.mod file only exists in memory.

This isn't blocking Go 1.11. The main reason being that if GO111MODULE=auto (the default) then we can't reasonably do anything with modules when outside a go.mod tree. That's the opt-in. And inside a go.mod tree this already works.

I agree that this doesn't block Go 1.11, but I do think it should be a blocker for 1.12. There are a lot of repos that have READMEs saying "just run go get github.com/me/myrepo to install". That should continue to work once GO111MODULE changes to "on".

Agreed. I've marked it as a release-blocker for 1.12.

IMO go get with modules semantic is not the right place for the functionality.
go bin may be?

@kortschak, that's at least in part covered by #26404. It would be up to the one building the binary to expose that via a flag command or similar.

I've been giving this some more thought, and by now I think the right behavior — if we're in module mode and not inside any other module — is to use the go.mod file from the module containing the requested package.
In that mode, we should emit an explicit error if the go.mod file has any replace directives that point to (relative or absolute) file paths outside of that module, or if the process of building the package required any additions to the go.mod file (i.e., as if the user had implicitly set -mod=readonly).
That has several nice properties:

It applies the same versions, including replacements and exclusions, that the tool author (presumably) used when testing their binary and its dependencies.
It uses an existing artifact — the go.mod file — that doesn't disappear after the build completes.
The versions used are not specific to the individual user, so (modulo other GOFLAGS) builds remain highly reproducible.

I can see one downside to this approach:

Versions of packages that have dependencies beyond the standard library but lack go.mod files cannot be built outside a module in module mode.

I think that may actually be a good thing: if you want to build a tool that doesn't specify the versions for its dependencies, you need to specify those versions, and the logical place to do that is in a module definition.

@bcmills Just expanding slightly on the downside you listed, I think that means that go get tool-foo when run outside of a go.mod tree would not work in module mode for a tool that itself has not opted in to modules?
If so, that might be problematic as 1.12 behavior, or whenever module-mode becomes the default behavior of the go tooling. Ideally go get tool-foo would would continue to work for tools that have not updated their readmes, including for tools that have not yet opted in to modules (given it will take some time for the ecosystem to fully adopt modules).
Perhaps an alternative would be to do as you outlined for a module-based tool, but liberalize it such that a non-module based tool would also work via go get tool-foo in module-aware mode when run outside of a module (e.g., perhaps by following 1.10 behavior, or perhaps by effectively creating a temporary go.mod as outlined in https://github.com/golang/go/issues/24250#issuecomment-377553022, or ___).

@bcmills We are using replace directives in main modules pointing to submodules in the same repository, so that changes to submodules can immediately affect the main module and be tested without needing an intermediate step to publish a new module version.  When you say

we should emit an explicit error if the go.mod file has any replace directives that point to (relative or absolute) file paths outside of that module

do you mean the repo?  What does a replace directive pointing "outside the module" mean?

do you mean the repo? What does a replace directive pointing "outside the module" mean?

I think I mean the module itself, since that's what module proxies will have available. “Outside the module” means either above the directory containing the module's go.mod file, or at or below the directory of a submodule's go.mod file.

@jrick

We are using replace directives in main modules pointing to submodules in the same repository, so that changes to submodules can immediately affect the main module and be tested without needing an intermediate step to publish a new module version.

But presumably this is just an intermediate, transition step? Because then the "released" version of a command/library should not have any directory-target replace directives, thereby indicating it was tested against specific versions of all its dependencies.
By the way, I can empathise with the pain of the multiple steps involved. I added an Experience Report on just this situation (actually with the added complication of a cyclic module dependency):
https://gist.github.com/myitcv/79c3f12372e13b0cbbdf0411c8c46fd5

I think that means that go get tool-foo when run outside of a go.mod tree would not work in module mode for a tool that itself has not opted in to modules?

Yes.

Ideally go get tool-foo would would continue to work for tools that have not updated their readmes, including for tools that have not yet opted in to modules (given it will take some time for the ecosystem to fully adopt modules).

That's true. Perhaps a fallback per-user go.mod would work for that, but I don't think we should use a fallback if we have the binary's actual go.mod file available.

@myitcv so far, we have been tagging releases with the replace directives, and fetching the repository or tarball has been a necessary step to build a release (I realize this doesn't play well with module proxies who don't operate on repos).  It could be possible to remove those after we branch off to make a release and leave the replaces on our master branch.

For the case where you in module mode but outside a module and do go get example.com/tool-foo, and tool-foo lacks a go.mod file, the go tooling could automatically create something like:
$GOPATH/pkg/mod/....something.../example.com/tool-foo/go.mod
That would track dependencies and provide reproducible builds via that go.mod without cross contamination from other globally installed tools.
This is separate case from whatever is done for a tool that itself has a go.mod.
I've told a couple people that today with Go 1.11 they can manually create something like ~/tools/gorename/go.mod or  ~/tools/goimports/go.mod and then do a go get or go install for the proper tool from within the corresponding directory, but approach outlined above would be automating that process and putting the go.mod into some canonical location (and given no human in the loop, avoid collisions by including the full import path in the directory structure).

If so, that might be problematic as 1.12 behavior, or whenever module-mode becomes the default behavior of the go tooling. Ideally go get tool-foo would would continue to work for tools that have not updated their readmes, including for tools that have not yet opted in to modules (given it will take some time for the ecosystem to fully adopt modules).

I think that this is essential behavior for any future 'module only' world, whether it is in 1.12 or later. The reality of life is that there are many people who will not immediately add go.mod files to their programs for various reasons and some number of programs that will never add it because they are no longer being actively developed. A world in which go get <program> stops working unless the program has been updated to have a go.mod file is a world where a great many Go programs are no longer conveniently installable, probably for a significant amount of time. People are unlikely to be happy with this.
In my view, retaining GOPATH for at least this usage is the simplest answer, but people may not like it. Otherwise, the best solution I can think of is to create a temporary go.mod file for the package on the fly.

That would track dependencies and provide reproducible builds via that go.mod without cross contamination from other globally installed tools.

Maybe, although go get -u in non-module mode today is a nice forcing function to pick up at least some updates, and if there isn't any go.mod for the requested package, then maybe using other information gleaned from the community about what works isn't really a bad thing.
I could imagine, say, a $HOME/.go.mod file used as a fallback, where any go get or go install outside a module updates $HOME/.go.mod with indirect dependencies. My fear then is that it might be too convenient: we probably do want to retain some incentive for folks to add go.mod files to individual projects, and if we make it too easy to work without them we lose some of the broader benefits of reproducibility.

I've been giving this some more thought, and by now I think the right behavior — if we're in module mode and not inside any other module — is to use the go.mod file from the module containing the requested package.

I've also been thinking about it these days and came to the same conclusion. We have all we need in the go.mod of the module we're building.
I've got only one thing to think about.
If we are building an exteranal binary with go get inside some current module - the current module's dependencies could affect the build (implicitly set other versions than are set in the go.mod of the binary we're installing).
I don't think it's a good behaviour if we are driving for high-fidelity builds.
I would vote for a more predictable behaviour. Something like "if we run go get on a main-package having its own go.mod - we shouldn't use the dependencies from current go.mod (if having one)".
If we apply this rule, all binaries installed with go get will have a predictable build list, affected only by their own module requirements.

@mwf

If we are building an [external] binary with go get inside some current module - the current module's dependencies could affect the build […].
I don't think it's a good behaviour if we are driving for high-fidelity builds.

It may reduce fidelity somewhate, but seems like a desirable and perhaps even necessary behavior (see #25922). For example, suppose that one of the tools you're using calls out to a parser for some language (perhaps Go itself): if you run into a bug in the parser, you may want to rebuild the tool with an updated parser without waiting to push that update upstream.

You're absolutely right, it seems we just need a support for both cases.
What do you think about adding some build flag to switch the behaviour?
Maybe something like -mod=standalone, telling go build to use the original go.mod and nothing more.

@punya the go tool already has go run pkg which does exactly that in a module context. In a global context it probably make sense to ensure that we retain this behaviour (although I don't think the multiple version support is necessary - major versions, yes, via the import path /vX, but not minor/patch versions).
However, the main issue with using go run is https://github.com/golang/go/issues/25416. Although there is a clear way to sidestep that: https://github.com/golang/go/issues/25416#issuecomment-401882645

Thanks for the pointe. Russ's comment clearly goes against the substance of what I proposed so I'll hold off.

Just as a reminder when we come to look at this issue that we will need to bear in mind https://github.com/golang/go/issues/26794

Would it make sense to re-title this issue? Some people read this current issue title:
"cmd/go: allow installing programs (at specific versions) to GOBIN"
...as meaning that this issue is just about making go get<EMAIL_ADDRESS>work (in other words, that this issue is about allowing versions for go get with tools). However, the discussion in this issue is broader than that (including in terms of the other GitHub issues are being closed as duplicates of this issue here).

I'm a go noobie (coming in at an excellent time with the introduction of go modules) and I wanted to throw in my 2¢ of my use case.
First
I would expect either success (installed bin) or an error message when from my home directory I do this:
go install github.com/UnnoTed/fileb0x

or this:
go get github.com/UnnoTed/fileb0x

Instead (go1.11 darwin/amd64) I get no error and, even worse, echo $? yields 0.
Second
I don't have a $GOBIN. I would expect that to be... dirname $(command -v go) if not otherwise specified?
Third
The purpose of fileb0x is to be used by go generate, which is why I was trying to install it following the readme.
For anyone else in a similar use case finding this via search, I did find that adding go run worked for me. However, it added everything to my go.mod. I'm not sure if that's desirable or undesirable. Personally I appreciate it.
//go:generate go run github.com/UnnoTed/fileb0x b0x.yaml

GOBIN is optional, go install will install to $GOPATH/bin of GOBIN is not provided and in the case that GOPATH is not provided the Go tool will assume it to be $HOME/go, thus go install installs to $HOME/go/bin unless instructed otherwise.

On 22 Sep 2018, at 14:59, AJ ONeal<EMAIL_ADDRESS>wrote:
I'm a go noobie (coming in at an excellent time with the introduction of go modules) and I wanted to throw in my 2¢ of my use case.
First
I would expect either success (installed bin) or an error message when from my home directory I do this:
go install github.com/UnnoTed/fileb0x
or this:
go get github.com/UnnoTed/fileb0x
Instead (go1.11 darwin/amd64) I get no error and, even worse, echo $? yields 0.
Second
I don't have a $GOBIN. I would expect that to be... dirname $(command -v go) if not otherwise specified?
Third
The purpose of fileb0x is to be used by go generate, which is why I was trying to install it following the readme.
For anyone else in a similar use case finding this via search, I did find that adding go run worked for me. However, it added everything to my go.mod. I'm not sure if that's desirable or undesirable. Personally I appreciate it.
//go:generate go run github.com/UnnoTed/fileb0x b0x.yaml
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

Thanks @davecheney. Since I'm using go1.11 I don't have a GOPATH either. I do see that the bins were put in $HOME/go/bin/. I'll set GOBIN=$(dirname $(command -v go)).
Interestingly, I actually don't have command -v go in my user PATH variables. It appears that go installed itself sneakily into /etc/paths.d/go when I wasn't looking (probably the mac .pkg installer)

I think that GOPATH is "The Right Place" ™.
I will (except in rare circumstances) have write access to my GOPATH. I may or may not have write access to my GOBIN (i.e. if I install via `apt install go-1.11', heaven forbid).
However, I still am a firm believer that go install should print the install path.
Beautiful is better than ugly.
Explicit is better than implicit.
Simple is better than complex.
Complex is better than complicated.
...
Readability counts.
...
Although practicality beats purity.
...
In the face of ambiguity, refuse the temptation to guess.
There should be one-- and preferably only one --obvious way to do it.
...
If the implementation is hard to explain, it's a bad idea.

Printing the path is beautiful, explicit, obvious, simple, readable, does not require guessing, not difficult to explain over the phone and remember later.
For example, I had to search my email to find the go list command you mentioned, and I had to try it three times to get it right.

1st time I used the '.', which was obviously wrong, but I just copy-pasted
2nd time I had the " in the wrong place, including the package
3rd time the quote was correct, as was my guess that . should be replaced with the qualified name.

I'm assuming there are temporary variables that could be set in the environment (i.e. when using gvm or other tools) that could lead to the package installing into an alternate place that would become non-reproducible if I were to run the go list command at a later time or in another terminal.

I will (except in rare circumstances) have write access to my GOPATH. I may or may not have write access to my GOBIN (i.e. if I install via apt install go-1.11, heaven forbid).

I think you're confusing GOBIN with GOROOT?
You should always have write access to GOBIN, because that's where go get puts binaries normally.

Probably
s/GOBIN/GOROOT/g
s/GOPATH/GOBIN/g

As something of an experiment in this space, would appreciate feedback etc on https://github.com/myitcv/gobin

@bcmills is something going to happen here for the Go 1.12 freeze?
Not being able to use go get in the "fetch/update a tool globally" sense has been the biggest frustration for us with the module changes in Go 1.11. We need a command we can run from anywhere that updates tools, now that go get has been broken for that purpose.
I'm not sure I totally follow the entire lengthy discussion here, but it sounds like even with this change we would still need to do cd /somewhere/outside/of/a/module && go get blah.

I'm not sure I totally follow the entire lengthy discussion here, but it sounds like even with this change we would still need to do cd /somewhere/outside/of/a/module && go get blah.
Well, I really hope the final solution will include a  flag as suggested here:
https://github.com/golang/go/issues/24250#issuecomment-370554691
Or that it uses a different command entirely... Or that go modules (as it's still an experiement), is in fact changed to use go mod add if you want to download something not globally, but for the current module...

@cespare

is something going to happen here for the Go 1.12 freeze?

I'm trying to get this in today, now that the stack for #26794 has been tested and mailed. Whether it makes the freeze will depend largely on how invasive the fix is.

@bcmills
Regarding @cespare's comment

I'm not sure I totally follow the entire lengthy discussion here, but it sounds like even with this change we would still need to do cd /somewhere/outside/of/a/module && go get blah.

Doesn't that somewhat defeat the purpose of this change? Its nice things work concurrently now but sometimes you're in your project directory and want to download a tool. What should I do in this case? Just cd to a tmp dir?

Nvm.
To anyone wondering about my question in the future: https://github.com/go-modules-by-example/index/blob/master/010_tools/README.md


Allow to peak at a specific node (instead of range)

I noticed that FnlPeak targets a range but it'd be nice to target a specific node also. I feel like that's the more sensible way to do Fennel peaks.
Got the idea from Olical/conjure where you can evaluate a specific node (e.g. word node, current node, root node, etc.).

@oblitzitate
I am currently taking a break from this project. So I would add this feature when I get some free time and some refactoring has been done to current codebase.

Alright cool! Also I just realized, I think it should probably be Peek (taking a glance) instead of Peak (top/pinnacle of something)

@ob

@oblitzitate
Thanks for finding out that silly typo. I could fix that now but it can cause some breaking changes, so I will fix it when I am releasing a newer version.

@oblitzitate
After thinking for some time I have decided to close this issue as adding this feature requires a lot of refactoring in current codebase.


Remove unit tests from codecov and configure threshold

Description
Rookie error 😄 . Forgot an extra file to ignore unit tests in the coverage.
Testing instructions
Add a set up instructions describing how the reviewer should test the code

[ ] Review code
[ ] Check Actions build
[ ] Review changes to test coverage

Agile board tracking
Related to #18

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 98.70%. Comparing base (d2183e6) to head (f898268).

Additional details and impacted files
@@             Coverage Diff             @@
##           develop      #51      +/-   ##
===========================================
- Coverage    99.02%   98.70%   -0.32%
===========================================
  Files           30       19      -11
  Lines          715      310     -405
===========================================
- Hits           708      306     -402
+ Misses           7        4       -3

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


     Push rejected, failed to compile Go app.
 !     Push failed

v126 works fine.

Hitting the same issue as well since last night.

Fixed. I merged the branch yesterday w/o doing the sync to the bucket.
Maybe I should make the tooling functions fall back to fetching from the source URL if it's not found in the bucket. That's probably sane.

PS: Sorry about this. Will think about doing above and some other options as well.


Docker Image

I'm trying to generate a docker image to host Circular with limited success.  PHP isn't my language of choice, so I'm possibly doing something silly - or it might be because the code depends on the deprecated mongo driver, rather than the new one?
Anyway, this might be helpful to someone - or perhaps someone can help me get this working?
Dockerfile
FROM composer/composer
##### Add mongodb support to PHP
RUN apt-get update
RUN apt-get install libcurl4-openssl-dev pkg-config libssl-dev
RUN pecl install mongodb
RUN cp /usr/local/lib/php/extensions/no-debug-non-zts-20151012/mongodb.so /usr/lib/php5/20131226/
RUN echo 'extension=mongodb.so' > /usr/local/etc/php/conf.d/mongodb.ini
##### Clone Circular repo (inc. submodules)
WORKDIR /app
RUN git clone --recursive https://github.com/julien-c/Circular.git
WORKDIR /app/Circular/api
##### Default Configuration
RUN cp /app/Circular/api/config.php.sample /app/Circular/api/config.php
##### Installation all dependencies
RUN composer install
##### Run the daemon
WORKDIR /app/Circular
RUN Daemon/run.php

I've got two problems when I try to start the daemon with Daemon/run.php:

PHP Warning:  PHP Startup: Unable to load dynamic library '/usr/lib/php5/20131226/mongodb.so' - /usr/lib/php5/20131226/mongodb.so: undefined symbol: __zend_calloc in Unknown on line 0
PHP Fatal error:  require_once(): Failed opening required 'MongoClient.php'

For a reference point, the hosted version runs under ubuntu 16.04 with PHP 5.6.11-1ubuntu3.4 (cli)   and a mongo driver version of 1.6.10 (which I probably installed doing sudo apt-get install php5-mongo)
Let me know if you get it to work


For deleted recurring_tasks

Hi, Let me ask you a question about https://github.com/rails/solid_queue/pull/272.
This support is very convenient as it allows recurring_tasks to be checked in MissionControl.　thanks 👍
However, there seems to be a problem with “recurring_tasks deleted from the YAML configuration file” that continue to remain on the MissionControl dashboard.
This is because we only process create or update for SolidQueue::RecurringTask.
https://github.com/rails/solid_queue/blob/7901a8e786de79daf4f35861b1393503bd7000b2/lib/solid_queue/dispatcher/recurring_schedule.rb#L43-L45
We do not think this is a major issue since the task does not continue to run, just remains on the MissionControl dashboard.
However, as the recurring_task setting is repeatedly added and removed, the MissionControl dashboard becomes polluted.
Is this the intended behavior?

Yes, it's intended, for now. The reason is that the current setup allows you to have multiple dispatchers, running different recurring tasks so a single dispatcher can't delete all tasks that aren't in its configuration because they might belong to a different dispatcher with a different configuration.
I plan to improve this, though, and clean up these old tasks. I have other improvements that I need to implement for recurring tasks, so I'll do all those together.

Thanks for the reply!
Yes, I agree. I didn't think it would be easy.
I'm looking forward to seeing more improvements in the future!


Unload meshes from the CPU automatically

Objective

Meshes are currently automatically uploaded to the GPU. However, once on the GPU, copies of all vertex data and indices are still kept around in RAM, which is a waste of memory.
Furthermore, doing the Mesh->GpuMesh asset lookup every frame for rendering is a minor waste of CPU time.
Supersedes #1782.

Solution

Mesh no longer implements RenderAsset.
A new system called transfer_meshes_to_gpu will take any entity with a Handle<Mesh> component, upload the mesh to the GPU and attach a GpuMesh, and then remove the handle.

If this handle is the last instance, refcounting will then delete the underlying mesh data.

Render systems now query for GpuMesh directly.

TODO

Fix examples
Check that the GLTF loader isn't keeping a different copy of the data in memory
Extend this PR to textures

Maybe keep RenderAsset around, but revamp it to convert handles instead

Write changelog and migration guide

Changelog

This section is optional. If this was a trivial fix, or has no externally-visible impact, you can delete this section.

What changed as a result of this PR?
If applicable, organize changes under "Added", "Changed", or "Fixed" sub-headings
Stick to one or two sentences. If more detail is needed for a particular change, consider adding it to the "Solution" section

If you can't summarize the work, your change may be unreasonably large / unrelated. Consider splitting your PR to make it easier to review and merge!

Migration Guide

This section is optional. If there are no breaking changes, you can delete this section.

If this PR is a breaking change (relative to the last release of Bevy), describe how a user might need to migrate their code to support these changes
Simply adding new functionality is not a breaking change.
Fixing behavior that was definitely a bug, rather than a questionable design choice is not a breaking change.

Given that certain assets have to be kept in RAM anyway (shaders for recompilation when specializing, dynamic meshes that are mutated from the CPU side), asset itself might need to have an ability to be "unloaded" when consumed by internal system.
I would however try to look for ways to keep end user API consistent.

A new system called transfer_meshes_to_gpu will take any entity with a Handle component, upload the mesh to the GPU and attach a GpuMesh, and then remove the handle.
If this handle is the last instance, refcounting will then delete the underlying mesh data.

If Handle<Mesh> is how mesh is attached to entity, end user would expect to be able to call commands.entity(entity).remove::<Handle<Mesh>>(); later.
Also assets are usually managed separately (load/unload on new scene), so handle will never be removed (since it's kept inside some "resource"), And when removed, you might as well unload GPU data as well.
See bevy_asset_loader

I'm going to close this for now and come back to this after the asset rework happens.


Trying to switch default theme is not working.

Trying to switch default theme. Not working. I started with a basic github pages site. The only thing that works is the classic theme.
minima:
  skin: dark

Are you using the gem version of the theme or the remote version? You need the remote version to use skins.
To pull in the remote version, use the following config entries:
plugins:
  - jekyll-remote-theme
remote_theme: jekyll/minima

@ashmaroli yes thank you, that was it. however, it actually worked without the plugins: key.
It would be nice if the documentation warned people of this, underneath the skins section.


"Go to Symbol in Workspace…" but with symbols in dependencies, or equivalent functionality

🔍 Search Terms
typescript, symbol, go to symbol in workspace, dependencies
✅ Viability Checklist

[x] This wouldn't be a breaking change in existing TypeScript/JavaScript code
[x] This wouldn't change the runtime behavior of existing JavaScript code
[x] This could be implemented without emitting different JS based on the types of the expressions
[x] This isn't a runtime feature (e.g. library functionality, non-ECMAScript syntax with JavaScript output, new syntax sugar for JS, etc.)
[x] This isn't a request to add a new utility type: https://github.com/microsoft/TypeScript/wiki/No-New-Utility-Types
[x] This feature would agree with the rest of our Design Goals: https://github.com/Microsoft/TypeScript/wiki/TypeScript-Design-Goals

⭐ Suggestion
When using the "Go to Symbol in Workspace…" feature in VS Code, only symbols within my project are shown. I think it should show symbols in my project and my dependencies, or at the very least there should be a setting to toggle showing dependency symbols.
I previously thought this was a bug but was told this was intentional (#59551) so I'm opening a formal feature request.
📃 Motivating Example
I often want to use "Go to Symbol in Workspace…" to look up symbols in Node, TS, VS Code, or other dependencies, as I work. I actually rarely use it to look up my own symbols, I instead use ⌘P and jump to the relevant file.
💻 Use Cases
What do you want to use this for?
I want to use it for browsing the APIs of my dependencies, such as whether a given API even exists.
What shortcomings exist with current approaches?
It is more tedious to type out the desired type and ⌘-click it.
Sometimes I want to want to look up a symbol to see if it even exists before I type it.
What workarounds are you using in the meantime?
I type out the symbol and ⌘-click it.

I believe you're asking for this setting? If not, a concrete repro that demonstrates what you're expecting to find would be needed


rdkafka properties as directive parameters

Revamp configuration directives with properties parsed by rdkafka
Motivation is ability to set properties at configuration time. Currently a known set is hardcoded in configuration parsing together with string/int types (note that rdkafka property setting is always string). It will be useful to tweak various properties without a code change.
Tests:

bad configurations fail in master process before workers are started
print modified properties at producer-creation time with their expected values
see requests appear as batches in Kafka log segment of a test topic
NGINX reload applies changed rdkafka settings (and unset directives fall back to defaults)
starts ok when module compiled but not configured
builds and starts ok when compiled without module

Not all configuration errors are detected in master process, eg dependencies between properties like idempotence and acks. Those are flagged by rdkafka at time of producer create, at which point you get dying workers.

Hi @larry-cdn77,
Thank you for contributing this pull request!
Please sign the Kaltura CLA so we can review and merge your contribution.
Learn more at http://bit.ly/KalturaContrib

Thanks @larry-cdn77, I'm ok with adding a generic directive for arbitrary librdkafka params, but prefer not to remove the existing ones, since -

I think the defaults in the code are more suitable for this use case than the more generic defaults in librdkafka (e.g. enabling compression by default + limiting the number of retries)
Removing the defaults + existing directives would force us to update the conf of all components that currently use this module

Regarding the enable flag, the module writes to kafka only when -

The location uses the kafka_log directive
The topic expression evaluates to some non-empty string
So I don't think we need another directive to disable it.

Thank you for the response
Clearly, I did not consider compatibility. Here is another changeset then, with the current setting rdkafka properties like the new universal one.
One exception is log level, where librdkafka seem to be phasing out the rd_kafka_set_log_level function in favour of the global 'log_level' property.
I retained the direct setting of rdkafka properties only because having this fail in worker is messy in my environment. I try to push configuration problems into master and spot them nice and early.
I do think the enable flag is useful but might be missing something. The case I address with it is module compiled in but not used. Worker process init (ngx_http_kafka_log_init_worker) will call ngx_kafka_log_configure_kafka and that just goes on creating a producer. No bootstrap servers have been set and you get errors that are confusing if a developer happens to have no idea about the module (despite it being compiled in).

I noticed that the string translation from directive to property in ngx_http_kafka_log_set_property  could probably be implemented with the post attribute of ngx_command_t

Right, better use the post attribute for this, instead of mapping it in the code.
Also, for setting the defaults in ngx_kafka_log_init_kafka, I think it would be more elegant to have a static array of ngx_keyval_t that is null terminated (ngx_null_string) and loop over it.
Regarding the enable flag, I want to understand the issue better... you said that if the module is built into nginx and there are no kafka_log directives in the conf, it fails to start?

Right, better use the post attribute for this, instead of mapping it in the code.

Now changed. Looks a great deal better.

Also, for setting the defaults in ngx_kafka_log_init_kafka, I think it would be more elegant to have a static array of ngx_keyval_t that is null terminated (ngx_null_string) and loop over it.

Done, thanks, also looks and reads much better. Used zero-terminated string so that I am not going into NGINX string and then back down again straight after.

Regarding the enable flag, I want to understand the issue better... you said that if the module is built into nginx and there are no kafka_log directives in the conf, it fails to start?

Sorry I should just describe an example scenario. Build with head of nginx-kafka-log-module, use nginx.conf without any Kafka directives and start NGINX. The module will attempt to create a producer without a bootstrap address with this error log message:
No `bootstrap.servers` configured: client will not be able to connect to Kafka cluster
It could be confusing to see this unexpectedly, and potentially time consuming to diagnose if you don't know that the module is compiled in and what it is for. It also relies on the producer creation failing gracefully, which may not always be the case. An enable flag is my attempt to be handle this defensively, but appreciate that it is possibly against how modules normally interface.


add sasl auth for kafka

pr https://github.com/kedacore/keda/pull/486

Thanks you!

Thank you @iyacontrol for the PR & @jeffhollan for the review!


Added Gallery Slider to Home Page

Related Issue

#472

Proposed Changes

Added a gallery slider displaying images from community workshops etc.
The slider swiftly switch images and is built using html, css and js only.

Additional Info

NIL

Checklist

[x] ✅ My code follows the code style of this project.
[ ] 📝 My change requires a change to the documentation.
[ ] 🎀 I have updated the documentation accordingly.
[x] 🌟 ed the repo

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Output Screenshots

Screenshot #1
Screenshot #2

Light mode
Dark mode

Please add the pagination slider like this

https://codemyui.com/gradient-card-ui-image-info-slider/

You may prefer any design you like

I've added a pagination slider along with two buttons for navigation, plz have a look @agamjotsingh18 !

@agamjotsingh18 it's a lind request to review the PR since it's over a week now. Please let me rectify if you need some changes.

@agamjotsingh18 plz approve the merge !


Fix build guide for tpch benchmnark

VELOX_BUILD_BENCHMARKS is removed by https://github.com/facebookincubator/velox/pull/8015.

@PHILO-HE I am adding a makefile target to disable tests and build only the benchmarks. We should suggest this new target so that users can build benchmarks faster (by avoiding building tests).
I hit some build issues due to the coupling of tests and benchmarks. I will open a PR soon to fix this and update the documentation.

I see. Thanks for clarification! Looking forward to your PRs. I'm closing this one.


Compile error in visual studio: 'resultCheck': identifier not found

I'm new to vulkan and memory allocator. I started a simply project and get the compile error 'resultCheck': identifier not found.. Did I miss something when initializing?

These are additional include paths.

This is because your Vulkan-Hpp headers come from Vulkan SDK, they are older and incompatible with VMA-Hpp. Please try using Vulkan headers of compatible version as specified in submodules.

Thanks, it get compiled. By the way, folder Vulkan-Hpp/vulkan doesn't include the c header file vulkan.h. The file need to be included somewhere else.