python3Packages: remove broken, unmaintained packages

Motivation for this change
This PR is for packages that are unmaintained and broken in python-modules
Things done

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

[ ] NixOS
[ ] macOS
[ ] other Linux distributions

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

rebased on latest master, going to merge when ofborg succeeds

@GrahamcOfBorg eval

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/misuse-of-commit-permissions/10071/43


Update bower

If you want to bring in the changes to the lab pricing (and the quality assurance stuff too), you should update the digitalmarketplace-frameworks to its current version while you're at it.

Would be good to describe in the pull request what this change is bringing in, or link to the diff: https://github.com/alphagov/digitalmarketplace-frontend-toolkit/compare/v13.1.0...v13.3.0

I though the convention was that versions were just bumped, has this change now?

:+1:


Order of chained Task execution is LIFO, not FIFO

This may, or may not depend on the FJP async mode, but we can also enforce this at the application level, two places in particular.
cloud.orbit.actors.runtime.InternalUtils#linkFutures
cloud.orbit.actors.runtime.Hosting#locateActor should also return an OrderedFuture, see https://github.com/atomix/atomix/blob/master/utils/src/main/java/io/atomix/utils/concurrent/OrderedFuture.java .

Going to defer any action on this to Orbit 2.x


[Doc Issue][Update token parameter and link for SSO][3077745]

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/tabs/how-to/authentication/tab-sso-code.md
89
13
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/tabs/how-to/authentication/tab-sso-code.md
91
8
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/tabs/how-to/authentication/tab-sso-code.md
91
8
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/tabs/how-to/authentication/tab-sso-code.md
91
8
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/tabs/how-to/authentication/tab-sso-code.md
91
8
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/graph-api/App-permissions/Teams-app-permissions.md
94
2
link
:white_check_mark:

msteams-platform/tabs/how-to/authentication/tab-sso-code.md
91
8
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/graph-api/App-permissions/Teams-app-permissions.md
94
2
link
:white_check_mark:

msteams-platform/tabs/how-to/authentication/tab-sso-code.md
91
8
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

The PR has been approved:

Closing this PR as the content has been added to https://github.com/MicrosoftDocs/msteams-docs/pull/8716 .


CVE-2022-21698 and CVE-2023-45142 - 7.5 High Vulnerability

https://nvd.nist.gov/vuln/detail/CVE-2022-21698
https://nvd.nist.gov/vuln/detail/CVE-2023-45142
go.opentelemetry.io/contrib/instrumentation/net/http/otelhttp
Installed version / Fixed version
0:v0.40.0 / 0.44.0
This is present in the datadog agent container major version 7 we use from public.ecr.aws/datadog/agent

Fixed by #20082.


XMLElement.Attr causes runtime error

Description
Calling Attr on XMLElement causes interface conversion: interface {} is []xmlquery.Attr, not []xml.Attr error. If attributes property of element is of type interface {} | []xmlquery.Attr and throws an error when being casted to []xml.Attr inside of the Attr method:
func (h *XMLElement) Attr(k string) string {
	if h.isHTML {
		for _, a := range h.attributes.([]html.Attribute) {
			if a.Key == k {
				return a.Val
			}
		}
	} else {
		for _, a := range h.attributes.([]xml.Attr) {
			if a.Name.Local == k {
				return a.Value
			}
		}
	}
	return ""
}

while an equivalent method on HTMLElement does a simple loop over attributes. Is this isHTML distinction really needed?
Expected
c := colly.NewCollector()
c.OnXML("//element", func(element *colly.XMLElement) {
  id := element.Attr("id")
})

to work.
Actual
runtime_panic

Sorry, for some reason I had v1.2 installed :/ I just noticed in source code it was fixed 2 years back...


During automatic backup, Orientdb should verify the files are not corrupted

OrientDB Version: 3.2.4
Java Version: 1.8
OS: OL8
Expected behavior
During automatic backup, Orientdb should verify the files are not corrupted
Actual behavior
During automatic backup, orientdb isnt checking the state of his files.
We had a corruption, no error in the automatic backup and the backups were corrupted too.
Steps to reproduce

delete or modify the file with the name name_id_map_v3.cm
wait for automatic backup
try to restore your orientdb

Can we have a roadmap info @tglman  please. Thanks


Show XML body when unable to parse XML

Right now you'll get a vague message about invalid
syntax if we can't parse the XML for whatever reason.
Now, we catch this error and raise a specific exception that
also includes the XML body so a user can see why we couldn't parse
the exception.
BTW, this happens when:

You provide an invalid endpoint-url.  Sometimes you might get some
boiler plate HTML from a site which will trigger this exception.
There are some cases are XML parser can't handle when we get
invalid XML.  While the end goal is to handle these cases, we
should at least be providing a better error message when this
isn't the case.

cc @kyleknap @danielgtaylor

Coverage increased (+0.0%) to 94.58% when pulling 043938b7a6281a3a1ec47b9f7818d8a69a03dc18 on jamesls:bad-xml into 5e83859f62ed977d5801b2a61519299210409445 on boto:develop.

Looks good. :ship:


API version query parameter is not specified or was specified incorrectly

Does this occur consistently?
Repro steps:

Action: azureApiManagement.showServicePolicy
Error type: Error
Error Message: API version query parameter is not specified or was specified incorrectly.  Supported versions: 2021-08-01,2021-12-01-preview,2022-04-01-preview,2022-08-01,2022-09-01-preview,2023-03-01-preview,2023-05-01-preview,2023-09-01-preview  Example query param format: api-version=SupportedVersion
Version: 1.0.8
OS: win32
OS Release: 10.0.19044
Product: Visual Studio Code
Product Version: 1.86.2
Language: en

Call Stack
ServicePolicyEditor.<anonymous> extension.bundle.js:16:392980
rejected extension.bundle.js:16:392126

For a quick fix you can edit this file,
~/.vscode/extensions/ms-azuretools.vscode-apimanagement-1.0.8/dist/extension.bundle.js
replace the two "2019-12-01" with "2021-08-01" and it should work.
Hopefully one day MS will change the correct line, https://github.com/microsoft/vscode-apimanagement/blob/6e590a25b7cb5961f2c2bfb4306f5b1eab915d0d/src/constants.ts#L33

For a quick fix you can edit this file,
~/.vscode/extensions/ms-azuretools.vscode-apimanagement-1.0.8/dist/extension.bundle.js
replace the two "2019-12-01" with "2021-08-01" and it should work.
Hopefully one day MS will change the correct line, https://github.com/microsoft/vscode-apimanagement/blob/6e590a25b7cb5961f2c2bfb4306f5b1eab915d0d/src/constants.ts#L33

I changed the enforce minimum API version into Yes, previously I was able to connect to my API manager via VS Code but after this change I'm unable to connect, did the above-mentioned changes also but did not work what to do for this

Duplicate of https://github.com/microsoft/vscode-apimanagement/issues/317


Metal1 assumptions on macro placement

Hello,
Why is it assumed that block macros are supposed to have metal1 OBS? (i.e., the size of a macro seems to be calculated based on its obstructions on metal1)
For example, to reproduce,

Try to place a macro that has no OBS shapes on the first metal layer. -> replace exits complaining that the macro has no metal1 OBS statements.
Insert a dummy OBS statement on metal1 (e.g., RECT 0 0 0 0 ;) -> replace reports such macros as having 0 height.

Thanks.

We are moving away from having replace handle macro placement.


Viz flowchart re-focus on every click

Description

The flowchart shouldn't refocus at the center. Maybe either center the chart with the clicked node, or do nothing at all.

Context

This make the navigation very hard to use

To achieve this, we need to disable the node re-focus on click when Kedro-Viz is used in embedded mode or within a VSCode setup. However, we currently don't have a flag in the code that indicates whether Kedro-Viz is being used in normal or embedded mode. I would like to know the team's opinion on what the optimal prop structure would be, one that not only fulfils the current requirement but is also scalable for future use cases.

Here I added mode as new prop which accept vscode, default or test. We can pass additional props as options with modeOptions

<KedroViz
  options={{
    mode: 'embed', // or 'vscode', 'default', etc.
    display: {
      globalNavigation: true,
      sidebar: true,
      metadataPanel: false,
    },
    modeOptions: {
      nodeFocus: true,
      showPipelineList: true,
      xyzList: [1, 2, 3],
    },
  }}
  data={getPipelineData()}
/>

Here I added vscode as single flag which can be use whenever we do VSCode specific task.

<KedroViz
  options={{
    display: {
      globalNavigation: true,
      sidebar: true,
      metadataPanel: false,
    },
    vscode: true,
  }}
  data={getPipelineData()}
/>

@rashidakanchwala @ravi-kumar-pilla @Huongg @SajidAlamQB

hey @jitu5 thanks for the summary! My initial thought is, why not pass it directly through the mode? For example:
modeOptions: {
     reFocus: false, // default is true
     nodeFocus: true,
     showPipelineList: true,
     xyzList: [1, 2, 3],
},

I think this approach offers more flexibility, allowing users to customize the Kedro-Viz standalone app more easily. I can imagine a scenario where we're building an extension for a different code editor—adding new props for every new tool could become cumbersome. What do you think?

hey @jitu5 thanks for the summary! My initial thought is, why not pass it directly through the mode? For example:
modeOptions: {
     reFocus: false, // default is true
     nodeFocus: true,
     showPipelineList: true,
     xyzList: [1, 2, 3],
},

I think this approach offers more flexibility, allowing users to customize the Kedro-Viz standalone app more easily. I can imagine a scenario where we're building an extension for a different code editor—adding new props for every new tool could become cumbersome. What do you think?

@Huongg
Okay I will drop mode prop and only use modeOptions as main prop object for mode related options. So for this ticket below props will used.
modeOptions: {
     reFocus: false, // default is true
}


RATIS-1024.Unit Tests for MemoryRaftLog entry truncation

What changes were proposed in this pull request?
Add unit tests to test MemoryReftLog log truncation
What is the link to the Apache JIRA
https://issues.apache.org/jira/browse/RATIS-1024
Please replace this section with the link to the Apache JIRA)
How was this patch tested?
unit tests

@szetszwo
Per file history I am guessing you are the right person to review this PR. Can you take a look?

@amaliujia , could you see if the failed unit test is related?

@szetszwo
The failed UT is not related. org.apache.ratis.TestMultiRaftGroup has failed and I created https://issues.apache.org/jira/browse/RATIS-1026 to track it.

Thanks, @amaliujia .  I just have merged this.

Thank you!


Provide an environment variable to control nat-outgoing

Currently in v1.0.2, the default value for nat-outgoing is false. To enable out going connection for the containers, I have to follow these steps: http://docs.projectcalico.org/master/usage/external-connectivity. Also I was informed that with the next release the default value for nat-outgoing would be false. This is great but it would be really useful if this option was configurable via an environment variable. (Something similar to CALICO_IPIP_ENABLED, say CALICO_NAT_OUTGOING?)

Added documentation pull request #775 for pull request introducing CALICO_NAT_OUTGOING


ci: remove .github/travis/

Subdir .github/travis does not make sense, now that Travis CI was replaced with GitHub Actions. In this PR, .github/travis/script.sh is moved to .github/ci.sh. The workflow is updated accordingly.
There are two other sources in .github/travis/. success.sh is currently not used. All it does is call surelog-coverage.pages.sh. However, I think that not executing surelog-coverage.pages.sh in GHA might be an oversight. @kamilrakoczy wdyt? Should I remove surelog-coverage.pages.sh or have it executed in GHA?

LGTM


Add TransactionManager to execute certified transactions based on input object availability

Background
This change adds a TransactionManager component that manages dependencies between pending certified transactions and objects in their input. TransactionManager accepts certified transactions from various sources e.g. consensus output currently and checkpoint sync in future. It builds dependencies between objects and transactions, and publishes transactions that have all input available locally. The goal of the change is to avoid the inefficiency and instability in the existing execution logic, by guaranteeing availability of input objects before execution, and simplify execution logic.
Transaction Manager
Here is a diagram for how TransactionManager communicates with other components.

Right now, TransactionManager is only activated in validators. The next step is to use TransactionManager in fullnode as well.
Shared locks
Since TransactionManager requires input objects' versions, shared objects in a certificate must be locked before sending to TransactionManager. Currently, SharedObjectLockNotSetError is often observed in logs, so this is not yet guaranteed. Enforcing this invariant involves a few changes:

Drop the logic to remove shared object locks after a transaction commits. I'm unable to convince myself the existing logic of removing shared locks are correct. And even with 2 and 3 below, I still observed SharedObjectLockNotSetError in tests. Later after dust settles down with the new TransactionManager, we can implement the logic to clear shared locks table at epoch boundaries.
In handle_consensus_transaction(), take shared locks and add certificates to the pending_certificates table in one batch write, then send the certificate to TransactionManager. Otherwise if a certificate is added to the pending queue or TransactionManager first, it can get executed immediately, without taking the shared locks.
Certificates were sent to the pending queue (add_pending_certificates()) quite liberally before. Most of these corner cases are removed to avoid sending a certificate containing shared objects to TransactionManager, if no shared locks are taken for the certificate.

Execution Driver and Node Sync
The new execution driver runs AuthorityState::handle_certificate() to process certificates directly, instead of sending digests to node sync. The driver shares similarities with the execution logic in node sync. Eventually we may want to merge the two. But right now, keeping the validator execution logic simple seems to be more beneficial.
There is no longer a retry path for certificates missing parents, since it is no longer possible. We will rely on other mechanisms (e.g. Narwhal) to catch up on missing certificates.
#4990 #5514

Overall, this is fantastic! To summarize the important points from my comments:

We need to be deliberate about how pending certificates are persisted and when it is ok to forget about them. This code seems to muddy those waters slightly.
I believe TransactionManager should be aware of the unsequenced state and model it explicitly.
I think there are a few data consistency problems here, (deletion of shared locks, notification of object writes).

Thanks for very detailed and informative review! There are indeed issues I missed at the beginning, e.g. pending_execution / pending_certificates table is actually part of the data consistency and recovery guarantee. I moved writing to the pending_certificates table into the same batch write that updates consensus tables and execution index.
For shared locks, I understand it should mostly work. But we are indeed seeing SharedObjectLockNotSetError from logs currently. And even after implementing (2) and (3) from the shared lock section above (still removing shared locks after commit), I still observed the error within TransactionManager::enqueue(). There are code paths that make thinking about the correctness of shared locks difficult. For example in hanele_certificate_and_effects() no transaction recovery lock is taken, so many instances can run in parallel. When effects of the transaction exist, no shared lock is taken regardless of existence of shared locks. It may take a few days to make everything work correctly all the day.
And I don't see the benefit of clearing shared locks right now. They should not occupy as much disk space as some other data. I think cleaning up temporary transaction data can be sequenced to be worked on, after we have a solid reconfiguration implementation. Then some of the storage cleanup work will be trivial as part of the epoch cleanup. Also, I think we need proper rocksdb transaction or our own custom transaction implementation. Otherwise it is really error prone to manage data consistency with multiple reads and writes.
Let me know what you think and we can chat off thread.

@mystenmark as we discussed yesterday, I looked into how to make sure shared object locks can be written and cleared correctly per transaction, instead of per epoch as I proposed in this PR. I believe we must cover writing and clearing the shared object locks within a per-transaction critical section. I can think of two ways to implement this:

Reuse the transaction lock mechanism we have. Since the lock is a scoped object right now, we need to acquire and pass it through TransactionManager. And we may need to avoid waiting on the lock on critical path, e.g. handle_consensus_transaction().
Simplify transaction locking by try inserting pending certificate. Transaction recovery will just be retrying pending certificates as well. This should be correct since we need to clear the pending certificate for each certificate, similar to unlocking the transaction. And this would simplify the transaction logic further.

What do you think @mystenmark @lxfind?


Project health document created

I added a docs directory with README to give us a place for the project health doc. This mirrors the structure of the governance subproject documentation.
The project health doc is designed to help point projects in the right direction with suggestions for how to measure health for their project.

/lgtm
/approve

Not sure if this info is needed here, but implemented a new K8s dashboard per request linked to this PR.

I added a new commit with a link to the new contributions chart that @lukaszgryglicki added - thank you!
@parispittman Have a look when you get a chance and let me know if you want me to change anything else before we merge it!

lets merge it! Carolyn gave ok on todays sig-contrib-strat meeting (for the record).
thanks soooo much dawn!! not enough exclamation points.

Thanks Dawn!
/approve


TypeError: Cannot compare two different types

Describe the bug
A clear and concise description of what the bug is.
TypeError: Cannot compare two different types even when both types are REAL
Code required to reproduce
The pseudocode that you used to trigger the bug.
DECLARE w:REAL
DECLARE h:REAL
DECLARE hs:REAL
DECLARE bmi:REAL

OUTPUT "Please enter your weight in kg:"
INPUT w

OUTPUT "Please enter you height in cm:"
INPUT h

h <- h/100

hs <- h*h

bmi <- w/hs

OUTPUT "Your bmi is ", bmi

IF bmi < 18.5
THEN
    OUTPUT "You are underweight"
ELSE
    IF 25.0 > bmi < 18.0
    THEN
        OUTPUT "You are normal weight"
    ELSE
        IF 30.0 > bmi < 25.0
        THEN
            OUTPUT "You are overweight"
        ELSE
            IF bmi > 30.0
            THEN
                OUTPUT "You are obese"
            ENDIF
        ENDIF
    ENDIF
ENDIF

Expected behavior
A clear and concise description of what you expected to happen.
It outputs the string
Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

OS: [e.g. Windows]
Architecture [e.g. 64 bit]

OS: macOS
Architecture: 64 bit Intel
Additional context
Add any other context about the problem here.

Thanks for submitting this issue!
However, your pseudocode appears to be incorrect.
See this line:
IF 25.0 > bmi < 18.0

This evaluates to
IF (25.0 > bmi) < 18.0

 (25.0 > bmi) is of type BOOLEAN and 18.0 is of type REAL, so you are indeed comparing a BOOLEAN and a REAL.
If you want to make your program not error, you must write:
IF 25.0 > bmi AND bmi < 18

In any case, thank you again for taking the time to report something! If you have any other issues, feel free to report them.


src/env.rs: Deduplicate (effectively move) inline fns

Is this change necessary? It seems like those inline functions were only being used in decode.rs, so I'm not sure there's any advantage to moving them to env.rs.

They are only used in decode.rs, but I thought it's useful just to keep the C to Rust source correspondence close where possible.  It also proved a tiny bit useful for some find and replace stuff I could do on the whole file in the next PR without touching the rest of the decode stuff.


Severe: License

Readme says MIT but does not contain any statement of ownership.
No Licence file is present.

I want to discuss this with someone, please contact me on Slack

Add MIT license in the repo (2016, Refugee Tech in the blank)
https://opensource.org/licenses/MIT


Adds missing AnyCodable to package manifest

The module uses the AnyCodable module but the manifest doesn't declare it as a dependency.

Thank you for noticing and correcting this. What an omission!


Have travis check app codesigning

It would eliminate the need to use VirusTotal if travis checked .app codesigning.
Using travis to perform the check would allow us to skip downloading, uploading to VirusTotal and checking that the sha256 matches the PR.
It also allows us to verify casks that use a container other than a dmg or zip and are larger than 128Mb.
Edit: This could also be used with pkgs.

$ . ci/travis/script.sh

Running script.sh...

>>> brew cask _audit_modified_casks 3bb6d41fa492f82e9c13e33362cfade9aedc6d9f...85a3dc9fb92c
==> 1 modified cask: iterm2
==> Downloading https://iterm2.com/downloads/stable/iTerm2-3_0_15.zip
==> Verifying checksum for Cask iterm2
audit for iterm2: passed

>>> brew cask style Casks/iterm2.rb

1 file inspected, no offenses detected

>>> brew cask install Casks/iterm2.rb
==> Satisfying dependencies
complete
==> Downloading https://iterm2.com/downloads/stable/iTerm2-3_0_15.zip
Already downloaded: /Users/travis/Library/Caches/Homebrew/Cask/iterm2--3.0.15.zip
==> Verifying checksum for Cask iterm2
==> Installing Cask iterm2
==> Moving App 'iTerm.app' to '/Applications/iTerm.app'.
🍺  iterm2 was successfully installed!

>>> codesign -dvv /Applications/iTerm.app
Executable=/Applications/iTerm.app/Contents/MacOS/iTerm2
Identifier=com.googlecode.iterm2
Format=app bundle with Mach-O thin (x86_64)
CodeDirectory v=20200 size=48789 flags=0x0(none) hashes=1519+3 location=embedded
Signature size=4608
Authority=Developer ID Application: GEORGE NACHMAN (H7V7XYVQ7D)
Authority=Developer ID Certification Authority
Authority=Apple Root CA
Signed Time=Mar 4, 2017, 10:14:58 PM
Info.plist entries=35
TeamIdentifier=H7V7XYVQ7D
Sealed Resources version=2 rules=13 files=120
Internal requirements count=1 size=216

>>> codesign -vv /Applications/iTerm.app
/Applications/iTerm.app: valid on disk
/Applications/iTerm.app: satisfies its Designated Requirement

The command ". ci/travis/script.sh" exited with 0.

$ . ci/travis/script.sh

Running script.sh...

>>> brew cask _audit_modified_casks e31e2d087558fb38a0160c501fec1386b2615850...2700e9ca7f44
==> 1 modified cask: metasploit
==> Downloading https://osx.metasploit.com/metasploit-framework-4.15.0+20170627092234-1rapid7-1.pkg
==> Verifying checksum for Cask metasploit
audit for metasploit: passed

>>> brew cask style Casks/metasploit.rb

1 file inspected, no offenses detected

>>> pkgutil --check-signature /Users/travis/Library/Caches/Homebrew/Cask/metasploit--4.15.0+20170627092234.pkg
Package "metasploit--4.15.0+20170627092234.pkg":
   Status: signed by a certificate trusted by Mac OS X
   Certificate Chain:
    1. Developer ID Installer: Rapid7 LLC (UL6CGN7MAL)
       SHA1 fingerprint: 76 2C 0C 45 5E CD 91 EB B1 2C D1 23 EC FE BE 8A BC C3 BD 69
       -----------------------------------------------------------------------------
    2. Developer ID Certification Authority
       SHA1 fingerprint: 3B 16 6C 3B 7D C4 B7 51 C9 FE 2A FA B9 13 56 41 E3 88 E1 86
       -----------------------------------------------------------------------------
    3. Apple Root CA
       SHA1 fingerprint: 61 1E 5B 66 2C 59 3A 08 FF 58 D1 4A E2 24 52 D1 98 DF 6C 60

The command ". ci/travis/script.sh" exited with 0.

Just realised that this could also be used with pkgs.
more pseudocode

if {only_sha_changed}; then
  if brew cask _stanza app "${modified_casks[@]}"; then
    run brew cask install "${modified_casks[@]}"
    run brew cask _stanza app "${modified_casks[@]}" | EDIT (to remove [" "])
    run codesign -dvv /Applications/{OUTPUT_OF_EDIT}
    run codesign -vv /Applications/{OUTPUT_OF_EDIT}
  elif brew cask _stanza pkg "${modified_casks[@]}"; then
    run brew cask _stanza pkg "${modified_casks[@]}" | EDIT (to remove [" "])
    run pkgutil --check-signature ~/Library/Caches/Homebrew/Cask/{OUTPUT_OF_EDIT}
  else
    "${modified_casks[@]}" does not have an app or pkg stanza.
  fi
fi

pkgutil --check-signature ~/Library/Caches/Homebrew/Cask/hwsensors--6.25.1426,45.pkg
Package "hwsensors--6.25.1426,45.pkg":
   Status: signed by a certificate trusted by Mac OS X
   Certificate Chain:
    1. Developer ID Installer: Natan Zalkin (R3YQC22TX8)
       SHA1 fingerprint: 46 97 0F 72 D0 DD 0A 43 7F DE BC 44 D1 54 1D 67 1A E7 EE 2B
       -----------------------------------------------------------------------------
    2. Developer ID Certification Authority
       SHA1 fingerprint: 3B 16 6C 3B 7D C4 B7 51 C9 FE 2A FA B9 13 56 41 E3 88 E1 86
       -----------------------------------------------------------------------------
    3. Apple Root CA
       SHA1 fingerprint: 61 1E 5B 66 2C 59 3A 08 FF 58 D1 4A E2 24 52 D1 98 DF 6C 60

Not sure if this might work better (or easier) as part of cask/lib/hbc/audit to be run by travis during brew cask _audit_modified_casks.

This would need to be part of audit, not just the Travis script.

This would need to be part of audit, not just the Travis script.

I was hoping this would be easy for me to implement! 😭 😆

As this has to be added to audit I guess we need to discuss if it's a good idea or not.

I was hoping this would be easy for me to implement! 😭 😆

Ruby is easy. 😂

@vitorgalvao Would it be acceptable for maintainers to verify app codesigning locally in cases where virustotal cannot be used due to size or container?

Would it be acceptable for maintainers to verify app codesigning locally in cases where virustotal cannot be used due to size or container?

Yes.

Cool, that'll be easier than getting audit to verify it. Closing.


#10703: Make ttnn::Buffer allocation thread/memory safe

Ticket
https://github.com/tenstorrent/tt-metal/issues/10703
Problem description
ttnn Buffer allocation was not thread or memory safe.
What's changed
Make ttnn::Buffer inherit from enable_shared_from_this, to ensure that worker thread and main thread can have joint ownership (this will bypass a segfault that could show up in a degenerate allocation, where the user allocates a buffer asynchronously and does nothing with it).
Remove the GLOBAL_ADDRESS_MAP and use a static thread_local map instead.
Make buffer.address() async aware.
Checklist

[ ] Post commit CI passes
[ ] Blackhole Post commit (if applicable)
[ ] Model regression CI testing passes (if applicable)
[ ] New/Existing tests provide coverage for changes

@namhyeong-kim

We are almost here but I don't like that in allocation you call highlevel public api function AllocateBuffer,
But in destructor you are calling details::deallocate_buffer - low level from namespace details. Overall namespace details means it is part of internal implementation of the module.
I understand why you cannot call DeallocateBuffer, because you cannot pass this. But It means maybe its time to remove dependency on Buffer from this two functions?


⚠ Fetchers has degraded performance

In 499a04f, Fetchers ($STATUS_URL) experienced degraded performance:

HTTP code: 200
Response time: 293 ms

Resolved: Fetchers performance has improved in 811b59b.


feat: Add DDL queries

Feature Request
Describe the Feature Request

Describe Preferred Solution

Describe Alternatives

Related Code

Additional Context

If the feature request is approved, would you be willing to submit a PR?
Yes / No (Help can be provided if you need assistance submitting a PR)

made possible by Query service


Revert "Patch for PR#20873"

CC @ZhenLian @jiangtaoli2016
Reverts grpc/grpc#21087
This PR broke our CI test: prod:grpc/core/master/linux/grpc_build_protobuf_at_head.
https://source.cloud.google.com/results/invocations/8a6e9ebb-f7f6-4fb7-ad75-dc8977fe7467/targets

prod:grpc/core/master/linux/grpc_build_protobuf_at_head

@ZhenLian You should to check local_service_account size before set it in AltsContext in line 296-298

@jiangtaoli2016  Could you please help me check if this PR: https://github.com/grpc/grpc/pull/21199 fixes the issue?
I have no idea why this change would cause the build failure... maybe we could try first revert this PR, and wait until the build succeeds again?

Hi @lidizheng
It looks like the kokoro build still fails with this reverting PR. From the log, it seems that something went wrong with the "ccache" command in protobuf sub repo.  This PR just contains three lines of code removing a conditional check, which looks irrelevant with the build failure.
That being said, I probably miss something important which is the cause of the failure, and feel free to let me know if you(or the build team) has some other findings. Thank you so much for the help so far!

@ZhenLian Thanks for reminding. Based on the test result, I agree that this PR seems not relevant. I will close this one.


Modify command bugs resolved

As referenced in the respective issue, this deals mainly with two problems. 1) tower-cli group modify will error 2) tower-cli job_template modify will silently modify things that it shouldn't. These both relate to hazards with setting defaults that also apply to the modify command. To explain that better, I would distinguish between command-line-level defaults, and defaults for a specific method. When you set a default on a field inside of a class, it's not exactly clear what the intention is.
Group Modify Fix
This command takes two actions - first it modifies the group, then it modifies the group's connected inventory_source. The problem is that the --source option on the group modify commands was set to an invalid value as a default, so so it would fail without that option specified. Since this was implemented with a click.option decorator, it can just be removed from the modify command and not the create command.
Another minor issue is that the result would appear green (represents unchanged) when it should have appeared yellow (changed). That is because it modifies two things in the method. A a quick fix, I set it to output whenever of the two changed. If they both changed, it doesn't matter much, because the information displayed to the user isn't very different between the two.
Job Template Fix
Previously, job_type had its default set to run. You can still create a JT and set job_type to check, but if you then edit something unrelated in this JT (like its description), it would set the job_type back to run. We would like to change the logic more broadly so that we can still use field defaults in this way, but it doesn't go well. If a JT has its job_type set to check, and then it is modified, there is no way for the method write in base.py to tell if that was a user input, or if it was passed as a default. Thus, we can't really fix the issue on this level.
The simple solution is to have a special clause in creation of a job template that sets the job_type if none is given. That is the solution I went with.
Fixes #98

The last commit was solving another issue related to groups and inventory_source. The tower API expects an empty string, "", for when the source is set to manual. So I just added one "if" statement that changed "manual" to "" inside of group.py. The inventory_source resource just has its manual option set to an empty string (because it's unlikely that a user will ever interact directly with it anyway).
It fixes the problem, with this, you can now modify a group and set it back to a manual source from a cloud source. In the process of creation, the bug never surfaced because of other special cases.

:+1:


Add Hotkeys for Underline and makeDiv

Adds hotkeys:
Underline:  ctrl/cmd + u
 <u>|</u>

*pipe indicates final cursor position when no selection
This commit does also change the current makeItalic hotkey to use * instead of _.   This is sort of an arbitrary change, but I feel it is more consistent with the syntax used in existing snippets.
makeDiv:   shift + ctrl/cmd + m
{{
|
}}

*pipe indicates final cursor position when no selection
Considerations

makeDiv is for v3 only, using curly syntax.
I considered setting the final cursor position on makeDiv to be immediately after the opening brackets, to facilitate quickly adding classes etc....

but not sure how to find that position when creating from non-empty selection (when using replace)
if going ahead with this, likely best to eliminate the empty line between brackets, so that the first "empty" line is created by hitting enter after entering class names etc.

Here is a demo page for markdown-it showing use of the plug-in markdown-it-ins

Added another set of hotkeys, inspired by #732.
makeNbsp: ctrl / cmd + .

Finishes with the cursor at the end.  May look into an additional hotkey (ctrl + ,) to remove as well.
makeSpace: shift + ctrl / cmd + .
{{width:10% }}

Finishes with span selected.  Repeated use increases the percentage by 10% increments to a max of 100%.
removeSpace: shift + ctrl / cmd + ,
Reduces the above span by 10% increments until 0%, at which point the span is removed entirely.
Overall, these hotkeys should make it easier to work with wrapping text around images, if not using shape-outside etc.  While shape-outside might be the ideal method of wrapping text, it is still difficult to use and doesn't work in every situation.

makeComment() was added in a previous PR/release, but in this PR I just updated it to be responsive to either the GFM editor or CSS editor (commit 3bf5d7a).  It will now comment correctly in either editor.  It also fixes a minor issue where undoing a comment left a leading and trailing space.  This would close #1303.

Ok, this all seems to be working and I don't have any strong feelings on how the hotkeys work, as I rarely use them myself. We can release this into the wild and if people complain we can make tweaks.
At some point we should move all of these out into a separate file, since Hotkey scripts are becoming their own beast. That will probably also make it easier to change behavior based on the current view / renderer (i.e., MakeDiv would be different depending on Legacy or V3, etc.)


Can't install ctrld on a Synology DiskStation (NAS)

Hello,
I'm trying to install ctrld on a Synology DiskStation (NAS), but the system is giving me an error.
I can't find the error log in the Log Center.
The ctrld installer thinks this is a Synology router.
Please advise how to install ctrld on a Synology DiskStation (NAS).
Thanks.
user@DiskStation:~$ sh -c 'sh -c "$(curl -sSL https://api.controld.dev/dl)" -s #DID forced'

        __         .__       .___
  _____/  |________|  |    __| _/
_/ ___\   __\_  __ \  |   / __ |
\  \___|  |  |  | \/  |__/ /_/ |
 \___  >__|  |__|  |____/\____ |
     \/       installer       \/

Please re-run this command with root/system permissions.

user@DiskStation:~$ sudo sh -c 'sh -c "$(curl -sSL https://api.controld.com/dl)" -s $DID forced'

We trust you have received the usual lecture from the local System
Administrator. It usually boils down to these three things:

    #1) Respect the privacy of others.
    #2) Think before you type.
    #3) With great power comes great responsibility.

Password:

        __         .__       .___
  _____/  |________|  |    __| _/
_/ ___\   __\_  __ \  |   / __ |
\  \___|  |  |  | \/  |__/ /_/ |
 \___  >__|  |__|  |____/\____ |
     \/       installer       \/

---------------------
|    System Info    |
---------------------
OS Type      : linux
OS Vendor    : Synology
Is Router    : yes
Arch         : x86_64
CPU          : Intel(R) Atom(TM) CPU D2701 @ 2.13GHz
Free RAM     : 2182 MB / 3947 MB
---------------------
|  Install Details  |
---------------------
Resolver ID  : $DID
Binary URL   : https://assets.controld.com/ctrld/linux/amd64/ctrld
Install Path : /usr/sbin
---------------------
 - Starting download
 - Making binary executable
 - Launching /usr/sbin/ctrld
---------------------
Aug 13 09:45:57.000 INF writing default config file to: /etc/controld/ctrld.toml
Aug 13 09:45:57.000 INF fetching Controld D configuration from API: $DID mode=cd
Aug 13 09:45:58.000 INF generating ctrld config from Control-D configuration mode=cd
Aug 13 09:45:58.000 INF writing config file to: /etc/controld/ctrld.toml mode=cd
Aug 13 09:46:30.000 ERR Service did not start, please check system/service log for details error
Aug 13 09:46:30.000 FTL exit status 1

If you change the domain in the installer command to api.controld.dev, and re-run that on your NAS, it should work.
This is the v1.3.0 release: https://github.com/Control-D-Inc/ctrld/pull/68

I pasted the wrong installer .com instead of .dev.
That solved the issue. Thanks!
user@DiskStation:~$ sudo sh -c 'sh -c "$(curl -sSL https://api.controld.dev/dl)" -s $DID forced'
Password:

        __         .__       .___
  _____/  |________|  |    __| _/
_/ ___\   __\_  __ \  |   / __ |
\  \___|  |  |  | \/  |__/ /_/ |
 \___  >__|  |__|  |____/\____ |
     \/       installer       \/

---------------------
|    System Info    |
---------------------
OS Type      : linux
OS Vendor    : Synology
Arch         : x86_64
CPU          : Intel(R) Atom(TM) CPU D2701 @ 2.13GHz
Free RAM     : 2143 MB / 3947 MB
---------------------
|  Install Details  |
---------------------
Resolver ID  : $DID
Binary URL   : https://assets.controld.dev/ctrld/linux/amd64/ctrld
Install Path : /usr/sbin
---------------------
 - Detected running process, this is an upgrade
 - Starting download
 - Stopping running process
 - Replacing old binary with the new one
 - Making binary executable
 - Launching /usr/sbin/ctrld
---------------------
Aug 14 11:05:31.000 NTC Starting service
Aug 14 11:05:43.000 NTC Service started


CornerPathEffect for web

Description
Hi, thanks for the great library :)
I'm making a cross-platform app and would love to use CornerPathEffect on web

I recommend building your own CornerPathEffect that will work on web as well. This is not a change we are likely to work on. https://github.com/google/skia/blob/cde544390afce8a798c7358a597aa3cdadb59ddf/src/effects/SkCornerPathEffect.cpp#L46 Skia does provide you with the necessary API to build it.

I recommend building your own CornerPathEffect that will work on web as well. This is not a change we are likely to work on. https://github.com/google/skia/blob/cde544390afce8a798c7358a597aa3cdadb59ddf/src/effects/SkCornerPathEffect.cpp#L46 Skia does provide you with the necessary API to build it.

Ok, thanks for letting me know, I'll give that a go 👍


Implement entire Snapshot GraphQL API

With snapshot creation, there's issue of filesystem going stopped unexpectedly.
With everything else, there's potential to hit this issue: https://github.com/whamcloud/integrated-manager-for-lustre/issues/2218
Signed-off-by: Michael Pankov<EMAIL_ADDRESS>

This change is

With snapshot creation, there's issue of filesystem going stopped unexpectedly.

This is due to us not filtering out zed events for snapshots (which also will only appear after a reboot).

Has conflicts on master

Looks like this now

I've changed to use mutations instead of queries

Has a conflict on master, otherwise LGTM


[ALLUXIO-2142] - Removed newline from containsObject method

https://alluxio.atlassian.net/browse/ALLUXIO-2142
Removed newline before last return statement from containsObject() in NonUniqueFieldIndex.java and UniqueFieldIndex.java

Can one of the admins verify this patch?

ok to test

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/11577/
Test PASSed.

LGTM


Implement better module resulution strategy

Currently Files.resolveModule is implemented by messing with the NODE_PATH. WE should instead call node with an executeable script (-e) option and simply use require.resolve.

Fixed with 2.4.2-next.6


Error with block namespace names conflicting with block names

Here's the relevant spirv and resultant glsl files:
SpirV.txt
Glsl.txt
In the spirv there's two ssbos with the same buffer name. It looks like in spirv-cross this is handled around line 1560 when duplicate buffer names are found by using a fallback name based upon the variable's name. The problem is that if another variable already has this name it produces an error in glsl because I guess they're both in the global namespace.

Right, I found this passage in the GLSL 4.5 spec:
The block name (block-name) is used to match within shader interfaces: an output block of one pipeline
stage will be matched to an input block with the same name in the subsequent pipeline stage. For uniform
blocks, the application uses the block name to identify the block. Block names have no other use within a
shader beyond interface matching; it is a compile-time error to use a block name at global scope for
anything other than as a block name (e.g., use of a block name for a global variable name or function
name is currently reserved). It is a compile-time error to use the same block name for more than one
block declaration in the same shader interface (as defined above) within one shader, even if the block
contents are identical.


Add release note for 2.7.4

Motivation
As releasing 2.7.4, so add release note.
Documentation

[x] no-need-doc

@Technoboy-
maybe we should cheery pick this PR :  #13392

@Technoboy-
maybe we should cheery pick this PR? #13392

Yes, right.

@Technoboy- can we re-organize the structure to the following? So that users can capture the desired info in a quicker manner

2.x.x release notes

- Enhancement
  - Security
  - Broker
  - xxx

- Bug fix
  - Broker
  - Client
  - xxx

- Miscellaneous
  - xxx
  - xxx
  - xxx


[CI] matrix build

Workflow Reference
https://github.com/smarie/python-makefun/blob/main/.github/workflows/base.yml

https://github.com/sosiristseng/sosiristseng.github.io/issues/43


Run js-sdk build tests only when a python file changed

Description
Adding the workflow feature requested in issue #2256
Changes

Now js-sdk build tests should run only when a python file *.py changed somewhere in the project

Notes:

This affects the js-sdk workflow only. the js-sdk-check-wheel workflow will still work on every Push or PR.

Related Issues
closes #2256

I think we also need to add .github/workflows/ too to paths.
so when we bush a commit that changing the workflow itself, the workflow would run.
agree? @abom @waleedhammam

@sameh-farouk Isn't that the case already? the workflow is regardless of this path filter?

@sameh-farouk Isn't that the case already? the workflow is regardless of this path filter?

If at least one path matches a pattern in the paths filter, the workflow runs.
'**.py' will trigger the build anytime you push a python file.
.github/workflows/** will also trigger the build anytime you push any file (regardless of its type) to this specific path (where .yml files for the workflow exists). also we could make it more explicit .github/workflows/**.yml

@sameh-farouk Isn't that the case already? the workflow is regardless of this path filter?

If at least one path matches a pattern in the paths filter, the workflow runs.
**.py will trigger the build anytime you push a python file.
.github/workflows/** will also trigger the build anytime you push any file (regardless of its type) to this specific path (where .yml files for the workflow exists). also we could make it more explicit .github/workflows/**.yml

No problem 👍

I think we also need to add .github/workflows/** too to paths.
so when we bush a commit that changing the workflow itself, the workflow would run.
agree? @abom @waleedhammam

added as well as pyproject.toml and poetry.lock files


Requests on a book doesn't show up sometimes

Requests on a book doesn't show up for the first few times. Access any book that has requests from your owner page.

I did see the similar problem. Boy it might be because the inconsistency in our database.
Most of book request work well. And I only see the same problem one time when I made random requests in this afternoon.

@Kaho-Lee @MarcusBoay this done?

No clue

It is done. I haven’t seen this error in our  newest version of app.
在 2019年3月31日，下午4:31，Marcus Boay <notifications<EMAIL_ADDRESS>写道：
No clue
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/CMPUT301W19T11/Atheneum/issues/144#issuecomment-478391522, or mute the threadhttps://github.com/notifications/unsubscribe-auth/Aei91q5mk_Oik9aWIWNOlruAufIfi2Eiks5vcTcigaJpZM4bzV31.


cmd/go: support compiling all tests without running

I want this to work:
$ go test -c std cmd
cannot use -c flag with multiple packages

But I don't actually care about the binaries. I just want to test that all the tests can compile, and how fast. @randall77 also wants this for SSA coverage reasons.

Is go test -run xxxxx std cmd a reasonable workaround for at least some of those use cases?

And I want this, but I do want the test binary. I'd use it to compile tests, change the compiler, compile tests again, and then run before/after benchmarks. (All in a script, of course.) Like toolstash for std tests. I currently do something similar but with go list std and a lot of bookkeeping and go test -c invocations.
It seems to me would could generate a testmain that invokes all the tests in all the included packages. There are some questions: How do you know from the -v output which package this particular instance of TestReader is from? How does the -run filter work? And so on. My hand-waving answer is: Minic the UI for subtests and sub benchmarks, which already have this nesting problem; the nesting is just up a level rather than down.

we can't generate one binary for tests in multiple packages
because there is no guarantee that package A's test doesn't
interfere with package B's use of package A.

What if we leave that up to the user to diagnose? If package A's test interferes with package B's use of package A, then don't test them together. This sort of issue can already arise in a single package.

how could the user know that one can't test package A and package B
together?
consider "go test -c ./...", which could easily contain hundreds of
packages.

They'll know when the test fails. If the tests pass when run independently (i.e. go test ./..., no -c), then there's clearly an interaction problem.

Even if they could know the bad interaction between A & B (it's
not that easy because given that B's tests failed, you still don't
know which of B's dependent [both directly and indirectly] might
be the cause. What's more, the behavior also depends on the
order tests for different packages are run.) because cmd/go
doesn't support negative patterns, there is no way to use ./...
and exclude B.
Given a large enough GOPATH, it's very likely there are bad
interactions between the package tests, and then basically
the new feature is useless (in the worse case, the user has
to name all the packages on the command line, and it's no
better than status quo.)
We might be able to do this if multiple packages are compiled
into a single package from the beginning, but I don't think we
can add this feature now.

I can't imagine someone wanting to run go test -c ./... on their entire GOPATH unless they had a very good reason. I can, however, see this for a particular project or set of packages, in which case this becomes very useful. Think e.g. of cross-compiling all the tests for your project and having to only scp a single binary.

cmd/go doesn't support negative patterns

Yes, this is unfortunate.
I apologize, but I don't quite understand the resistance here. It seems like the resistance is "something could go wrong". But this doesn't really seem like a big footgun to me. And when this is helpful, like cross-compiling all tests for a big project or keeping around an old version for benchmarking or testing compilation speed, it is very helpful, and users will be motivated to make it work (or not use it). And it is entirely backwards compatible.

I think this issue gives one reason for do go test -c ./... for the
whole GOPATH: test the SSA compiler code generation.
The key point is most tests are not prepared for this.
How many packages support go test -count=2?
Even some of the std packages don't, until they're
fixed not long ago.
And how do you propose to handle conflicting flags added
by tests and multiple TestMains? Again, these features
are just not designed to combine tests for multiple packages
into a single executable.

How many packages support go test -count=2? Even some of the std packages don't, until they're
fixed not long ago.

Exactly. And they got fixed because people cared. Same situation here, I'd say.

conflicting flags added by tests

Sorry, what do you mean by this?

multiple TestMains

Refuse to compile, with a lucid error message. Rare.

tests for a package needs to run at the directory for the package

os.Chdir? Note that the go command has the directory available at compilation time. This is a bit ugly for the cross-compilation case, but we could print a warning instead of failing when os.Chdir fails.

I have been thinking about this feature a long time
ago

Yeah, I recall there being another issue about this but couldn't find it.
I agree that there are limitations, I just see them as limitations rather than showstoppers.

By conflicting flags added by tests, consider two
packages that both add -update flags to update
golden output of their test data.
The code will compile, but will fail at runtime with
a flag redefined panic.

I'm new to Go, but FWIW, the lack of this feature is one of the most frustrating things that I have found so far about the tooling. I tend to write production code and test code at the same time, and during my normal dev cycle I want to see if things compile many more times than I want to run the tests. So right now I'm doing roughly the same thing as stated above inside my project with a few packages: basically
for i in go list ./...; do go test -c $i; done
It would be great if this could be done in one pass with a single link and have it be up to the user to deal with conflicts as suggested by @bradfitz

If you want to compile but run not tests,
 go test -run=nope ./...

Replace nope with another pattern if you have test cases that match.
On Fri, 27 May 2016, 03:45 Matt Klein<EMAIL_ADDRESS>wrote:

I'm new to Go, but FWIW, the lack of this feature is one of the most
frustrating things that I have found so far about the tooling. I tend to
write production code and test code at the same time, and during my normal
dev cycle I want to see if things compile many more times than I want to
run the tests. So right now I'm doing roughly the same thing as stated
above inside my project with a few packages: basically
for i in go list ./...; do go test -c $i; done
It would be great if this could be done in one pass with a single link and
have it be up to the user to deal with conflicts as suggested by @bradfitz
https://github.com/bradfitz
—
You are receiving this because you are subscribed to this thread.
 I tried:
go test -run nope ./...
Also still runs tests.

 I
tried:
go test -run nope ./...
Also still runs tests.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/golang/go/issues/15513#issuecomment-222027132, or mute
the thread
https://github.com/notifications/unsubscribe/AAAcA8xNrwQtBDQEF3AeZEF-377nOLMUks5qFjMwgaJpZM4IV2e-
.

I tried both:
mklein@vm:~/Source/go/src/github.com/<redacted>$ go test -run=nope ./...
ok  	github.com/<redacted>	0.025s

-run=nope and -run nope are equivalent.
@mattklein123 no tests are being run (probably). Use -v to confirm.
Please use the mailing list if you have further questions about go test.

That is correct. The test binary is built and executed, but none of the
test cases will be executed because they don't match the -run filter
On Fri, May 27, 2016 at 10:11 AM, Caleb Spare<EMAIL_ADDRESS>wrote:

-run=nope and -run nope are equivalent.
@mattklein123 https://github.com/mattklein123 no tests are being run
(probably). Use -v to confirm.
Please use the mailing list if you have further questions about go test.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/golang/go/issues/15513#issuecomment-222029023, or mute
the thread
https://github.com/notifications/unsubscribe/AAAcA8u95PM2MDjAGCytHBIVmp0py0RIks5qFjaxgaJpZM4IV2e-
.

i prefer -run ^$

My motivation is for the builders, and test sharding.
The problem with go test -run=^$ std cmd is that it deletes the *.test binaries afterwards. I want the test binaries, to ship around the network and shard out isolated test execution. But I want to burn CPU as hard as possible where it's not latency sensitive. (That is, I can run compilation jobs at 100% CPU, but tests are often flaky at 100% if they sleep or depend on time.)

@bradfitz, I think for your purpose, having multiple go test -c processes
is better than figuring out where to store the compiled binaries when
building multiple tests (the only safe way is to put the compiled test
binary in their own package directories, but then you need to collect them.
It's probably easier to just go test -c with explicitly output filename).
It won't do much more work either (assuming go install std cmd has passed.)

I can do it myself, but my concern is that I can't keep the CPU busy as well as the cmd/go binary could.
cmd/go can load the dependency graph once, come up with a plan, and keep a certain number of worker processes running at all times.
Any coordination I do trying to run multiple cmd/go binaries wouldn't be as good.
Definitely low priority, though.

There are at least three different things people might want here (and have asked for either here or other places):

Build all binaries and don't save them.
Build all binaries and do save them (maybe in a directory tree).
Compile but don't link (for quick turnaround in save hooks).

I propose we keep accumulating these kinds of go command issues and try to take a coherent look at them in the first half of next year.
I'll create a new GoCommand label. Feel free to label other (proposal or non-proposal) issues with that too.
Thanks.

It would be great if this enabled "buildall.bash" to also check if all tests compile. That would have saved me some embarrassment when submitting CLs.

I have a large C based codebase which has Go wrappers. I would like to write Go test packages (only test *.go code) as test drivers for the C code, using the go wrappers, create go test binary and ship the binary with the installed software as a test suite for the environment. This is not a typical test suite in a dev machine.
The structure of go source code and the godoc helps in organizing the test suite nicely out of the box.

Just a note for future travellers:

if you're doing something like go test ./... it will continue with all package tests even if one of them fails to compile (they effectively run individually, as in O(N) not O(1)),
the flag -failfast doesn't seem to have any effect on this (1.12), all package tests will run,
note that the trick -run=^$ from above still runs ANY TestMain() which you may have - it's false to say that you are only compiling tests. This is especially dangerous with integration tests as you may populate an external service with data from TestMain,...

Overall: ouch

Hi there, I think this could make multiplatform testing more simple/easy. (At least for me with Packer):
1/ have your ci in docker
2/ cross build your test binaries for the systems you care about.
3/ link & test
This should be fairly simply doable on circle-ci for example, since they recently added macos and windows support.
This way I don't have to install go for every OS I want to test upon.
I wouldn't mind that multiple binaries could be generated, if I can get a parsable list of generated binaries.
In my case I think the argument of pkg.test A making pkg.test B fail is not an issue as it would be super easy to compartmentalise were these tests are being run.
And for now I will do this manually using that good old go list ./... 🙂
Cheers !
PS: Happy to contribute if need be !

-run ^$ not works,  -run=nope not perfect. I prefer -count=0

Any hope that we will be able to compile all tests and cache the results without running the tests?

Any progress? I would like to have this feature. Thank you.

I would highlight again the desire to be able to build all tests into a single binary. If go test ./... works, it seems strange that it'd be impossible to make a single binary which does the same thing

go test ./... works by building and running several different binaries.  In particular, test binaries assume that they are run in the directory of the package being tested, so that they can refer directly to testdata files.  That seems awkward if we build a single binary for multiple packages.

I have found pretty workaround.
Idea is to use go test --exec flag. Here it's doc from go help test:
	-exec xprog
	    Run the test binary using xprog. The behavior is the same as
	    in 'go run'. See 'go help run' for details.

If pass --exec that does exit 0, than it works like  build all binaries and don't save them.
If pass --exec that moves binary somewhere, than works like Build all binaries and do save them (maybe in a directory tree).

I have implement the workaround in simple script: https://github.com/skipor/go-test-compile
It just works:
# Download some packages to test.
go get -d -t golang.org/x/tools/...
# Just check that all code building. Like `go build ./...` but also build test packages.
go-test-compile golang.org/x/tools/godoc/...

# Compile all test binaries. # Like `go test -c ./...` it it were implemented.
go-test-compile -o /tmp/test-executables golang.org/x/tools/cmd/godoc golang.org/x/tools/godoc/...
tree /tmp/test-executables
#> /tmp/test-executables
#> └── golang.org
#>     └── x
#>         └── tools
#>             ├── cmd
#>             │   └── godoc.test
#>             ├── godoc
#>             │   ├── redirect.test
#>             │   ├── static.test
#>             │   ├── vfs
#>             │   │   ├── gatefs.test
#>             │   │   ├── mapfs.test
#>             │   │   └── zipfs.test
#>             │   └── vfs.test
#>             └── godoc.test

Of course, it is better to implement that features in go tooling, but workaround already works well.
P.S. To get compile but don't link (for quick turnaround in save hooks) same idea may be applied to go build --toolexec flag, that can be passed to go test too. Passing --toolexec, that writes exit 0 executable  if link called and does exec else will give us desired behaviour.

https://gist.github.com/howardjohn/c0f5d0bc293ef7d7fada533a2c9ffaf4 provides a small script to do this, inspired by some of the comments above. By skipping the linker we save a lot of time on warm builds (60s -> 3s)

This has been on hold for 4 1/2 years for taking an overall look at the go command.  I think that has happened, so taking off hold.

The go embed feature and could be useful now. If tests were embedding things from testdata  then a test binary would 'just work'.
Now, I'm not sure if the solution should auto-embed things for tests.

Adding an ability to build all tests, similar to how we can build all code including commands with go build ./... would be helpful in Go repos where building is fast and tests are slow, because it is beneficial to have CI separately build all code in a separate run than tests.

We already have go build -o <directory> writing multiple binaries to a directory.
We also have go build -o /dev/null already special casing throwing the test binary away.
And apparently that works for multiple binaries today already (see https://github.com/golang/go/issues/37378#issuecomment-591603974).
It seems like we should make go test -c -o /dev/null work for multiple tests,
as well as go test -c -o <directory>.
(On Windows /dev/null is spelled NUL in these commands; it's os.DevNull.)
/cc @bcmills

This proposal has been added to the active column of the proposals project
and will now be reviewed at the weekly proposal review meetings.
— rsc for the proposal review group

Does anyone object to https://github.com/golang/go/issues/15513#issuecomment-959775908 ?

I totally expected -count=0 to compile all tests without running them. If we can't change that behavior, can we at least document it better in go help testflag and other places? Maybe even issue a warning?

go build -o /dev/null

This is no where documented.

go build -o /dev/null doesn't really need documentation when writing a single file, since it's just what /dev/null always means on Unix. We should absolutely document that it works for multiple targets (once we make that true).

Based on the discussion above, this proposal seems like a likely accept.
— rsc for the proposal review group

No change in consensus, so accepted. 🎉
This issue now tracks the work of implementing the proposal.
— rsc for the proposal review group

Regarding this:

We also have go build -o /dev/null already special casing throwing the test binary away. And apparently that works for multiple binaries today already (see #37378 (comment)).
It seems like we should make go test -c -o /dev/null work for multiple tests, as well as go test -c -o .

What if we are interested to take the test execution binaries and execute them in another process?
This can be beneficial if you have long running tests and very different resources footprint between compilation and test runtime. For instance - e2e tests.

It will allow us to compile all tests on a strong expensive machine and then run the tests on cheaper ones.

@mknyszek and @prattmic pointed out that on Unix platforms go test -exec /bin/true does seem to support compiling the tests without running them today. 😅

You can speed things up a lot faster with https://gist.github.com/howardjohn/c0f5d0bc293ef7d7fada533a2c9ffaf4 by avoiding linking the binaries. A warm run on even huge repos like k8s can do this in 1-2s on my machine.

@howardjohn, it may be faster but it's not the same. Link-time errors are possible in pure Go programs and even fairly common in cgo programs.

At last! Excited to see this supported by the toolchain, will avoid nasty hacks like this in the future :joy:

So, one minor detail: for a single package, go test -c $pkg would be equivalent to go test -c -o $(pwd)/ $pkg.
For consistency, should go test -c ./... also write test binaries in the current working directory for all matching packages?

should go test -c ./... also write test binaries in the current working directory for all matching packages?

How would conflicts be avoided here, with multiple packages of the same name but different paths?
Just thinking about a general solution for different use-cases... If -o supported a template you could use e.g. -o '{{.pkgPathRel}}.test" (maybe that should be the default to avoid the possibility of conflicts). It could then be set to {{.pkgName}}.test to write them all to the same dir. This would also remove the need for a special-case for /dev/null, as /dev/null would be a valid template...

How would conflicts be avoided here, with multiple packages of the same name but different paths?

Conflicts would cause the go invocation to fail. (But go test -c ./... already fails today if ./... matches more than one package at all, so no invocation that works today would start failing as a result.)

If -o supported a template you could use e.g. -o '{{.pkgPathRel}}.test" (maybe that should be the default to avoid the possibility of conflicts).

I think that's probably overkill. I expect that the vast majority of uses will be -o /dev/null, and consistency with go build -o is important to provide a predictable UX.

Yeah, I agree that those cases exist but I think the solution for them is, as you mentioned, to have those cases run go test -c with the specific packages they want to build. It's a bit more coding work but it's also a more complicated and nuanced use-case (precisely because of those kinds of collisions).

This is super useful, thanks everyone involved. I opened a followup issue here: https://github.com/golang/go/issues/61199 that I think can help make this more useful.

For posterity, and anyone who wants to include this in their build, the following command finds all the packages in the current directory:
go list -f '{{if .TestGoFiles}}{{.ImportPath}}{{end}}' ./...

So checking if all the tests compile can be accomplished like this:
go test -c -o /dev/null $(go list -f '{{if .TestGoFiles}}{{.ImportPath}}{{end}}' ./...)


Towards separation of 'internal' and 'function' storage backends

Modified storage config dictionary to ease the separation of internal and function storage backends.
Changed name of storage.py to storage_internal.py --> Adapted imports and inits.
Developer's Certificate of Origin 1.1
   By making a contribution to this project, I certify that:

   (a) The contribution was created in whole or in part by me and I
       have the right to submit it under the Apache License 2.0; or

   (b) The contribution is based upon previous work that, to the best
       of my knowledge, is covered under an appropriate open source
       license and I have the right under that license to submit that
       work with modifications, whether created in whole or in part
       by me, under the same open source license (unless I am
       permitted to submit under a different license), as indicated
       in the file; or

   (c) The contribution was provided directly to me by some other
       person who certified (a), (b) or (c) and I have not modified
       it.

   (d) I understand and agree that this project and the contribution
       are public and that a record of the contribution (including all
       personal information I submit with it, including my sign-off) is
       maintained indefinitely and may be redistributed consistent with
       this project or the open source license(s) involved.

@JosepSampe
May be you need init.py to the backends?
Traceback (most recent call last):
File "./deploy_runtime", line 5, in
from pywren_ibm_cloud import wrenconfig
File "/usr/local/lib/python3.6/site-packages/pywren_ibm_cloud-1.0.1-py3.6.egg/pywren_ibm_cloud/init.py", line 19, in
from pywren_ibm_cloud.wren import *
File "/usr/local/lib/python3.6/site-packages/pywren_ibm_cloud-1.0.1-py3.6.egg/pywren_ibm_cloud/wren.py", line 27, in
from pywren_ibm_cloud import future
File "/usr/local/lib/python3.6/site-packages/pywren_ibm_cloud-1.0.1-py3.6.egg/pywren_ibm_cloud/future.py", line 22, in
from pywren_ibm_cloud.storage import storage, storage_utils
File "/usr/local/lib/python3.6/site-packages/pywren_ibm_cloud-1.0.1-py3.6.egg/pywren_ibm_cloud/storage/storage.py", line 19, in
from pywren_ibm_cloud.storage.backends.cos import COSBackend
ModuleNotFoundError: No module named 'pywren_ibm_cloud.storage.backends'

@JosepSampe I tried to run map.py example from examples folder. Got
gilv-mac:pywren gilv$ bx wsk activation logs 1f49bd6a927d4dff89bd6a927d2dff68
2018-11-18T13:02:52.201933471Z stdout: [INFO] main: Starting IBM Cloud Function execution
2018-11-18T13:02:52.201976821Z stdout: [INFO] wrenhandler: Starting handler
2018-11-18T13:02:52.202422736Z stdout: [ERROR] wrenhandler: There was an exception: 'backend_config'
2018-11-18T13:02:52.204311237Z stderr: Traceback (most recent call last):
2018-11-18T13:02:52.204339882Z stderr: File "pythonrunner.py", line 88, in run
2018-11-18T13:02:52.204345199Z stderr: exec('fun = %s(param)' % self.mainFn, self.global_context)
2018-11-18T13:02:52.204349632Z stderr: File "", line 1, in
2018-11-18T13:02:52.204354548Z stderr: File "main.py", line 11, in main
2018-11-18T13:02:52.204358586Z stderr: ibm_cloud_function_handler(args)
2018-11-18T13:02:52.204362622Z stderr: File "/action/pywren_ibm_cloud/action/wrenhandler.py", line 225, in ibm_cloud_function_handler
2018-11-18T13:02:52.204366963Z stderr: if 'STORE_STATUS' in extra_env:
2018-11-18T13:02:52.204370791Z stderr: UnboundLocalError: local variable 'extra_env' referenced before assignment
gilv-mac:pywren gilv$
I also think this change requires to update all example and documentation, right? since "storage_handler" is no longer passed as a parameter, but it's ibm_cos?
I also think we need to document that ibm_cos is a client of ibm_boto3, right?
Thanks

@JosepSampe getting other error print as well, like
gilv-mac:pywren gilv$ bx wsk activation logs XXX
2018-11-18T13:01:54.611585278Z stderr: Traceback (most recent call last):
2018-11-18T13:01:54.611718665Z stderr: File "pythonrunner.py", line 99, in
2018-11-18T13:01:54.611962891Z stderr: setRunner(PythonRunner())
2018-11-18T13:01:54.611989686Z stderr: File "pythonrunner.py", line 32, in init
2018-11-18T13:01:54.611995035Z stderr: ActionRunner.init(self, '/action/main.py')
2018-11-18T13:01:54.611999297Z stderr: File "../actionProxy/actionproxy.py", line 55, in init
2018-11-18T13:01:54.61200369Z  stderr: os.chdir(os.path.dirname(self.source))
2018-11-18T13:01:54.61200773Z  stderr: FileNotFoundError: [Errno 2] No such file or directory: '/action'
gilv-mac:pywren gilv$

I think you need to run ./deplo_pywren to update the default pywren_3.6 action

@JosepSampe I used custom docker image, i did run deploy_pywren

run  ./deplo_pywren clone imagename

@JosepSampe this one is not enough "./deploy_runtime create ... " ?

Yep, it should be enough

@JosepSampe ahh...my mistake, you are correct. the map.py works now.

@JosepSampe this is most scary merge of the project ;)


Getting github timeout issue while composing docker

qlu@qlu-ThinkPad-E15:~/Final_zoom_repo/meetingsdk-headless-linux-sample$ docker compose up
permission denied while trying to connect to the Docker daemon socket at unix:///var/run/docker.sock: Get "http://%2Fvar%2Frun%2Fdocker.sock/v1.44/containers/json?all=1&filters=%7B%22label%22%3A%7B%22com.docker.compose.config-hash%22%3Atrue%2C%22com.docker.compose.project%3Dmeetingsdk-headless-linux-sample%22%3Atrue%7D%7D": dial unix /var/run/docker.sock: connect: permission denied
qlu@qlu-ThinkPad-E15:~/Final_zoom_repo/meetingsdk-headless-linux-sample$ sudo docker compose up
[sudo] password for qlu:
Sorry, try again.
[sudo] password for qlu:
Sorry, try again.
[sudo] password for qlu:
WARN[0000] Found orphan containers ([meetingsdk-headless-linux-sample-services-1]) for this project. If you removed or renamed this service in your compose file, you can run this command with the --remove-orphans flag to clean it up.
[+] Running 1/0
✔ Container meetingsdk-headless-linux-sample-zoomsdk-1  Recreated                                                                                0.1s
Attaching to zoomsdk-1
zoomsdk-1  | Preset CMake variables:
zoomsdk-1  |
zoomsdk-1  |   CMAKE_TOOLCHAIN_FILE:FILEPATH="/opt/vcpkg/scripts/buildsystems/vcpkg.cmake"
zoomsdk-1  |
zoomsdk-1  | -- Running vcpkg install
zoomsdk-1  | Detecting compiler hash for triplet x64-linux...
zoomsdk-1  | Compiler found: /usr/bin/c++
zoomsdk-1  | The following packages will be built and installed:
zoomsdk-1  |<EMAIL_ADDRESS>zoomsdk-1  |<EMAIL_ADDRESS>zoomsdk-1  |<EMAIL_ADDRESS>zoomsdk-1  |   *<EMAIL_ADDRESS>zoomsdk-1  |   * vcpkg-cmake:x64-linux@2023-05-04
zoomsdk-1  |   * vcpkg-cmake-config:x64-linux@2022-02-06#1
zoomsdk-1  | Additional packages (*) will be modified to complete this operation.
zoomsdk-1  | Restored 1 package(s) from /root/.cache/vcpkg/archives in 4.07 ms. Use --debug to see more details.
zoomsdk-1  | Installing 1/6<EMAIL_ADDRESS>zoomsdk-1  | Building<EMAIL_ADDRESS>zoomsdk-1  | -- Installing: /opt/vcpkg/packages/vcpkg-cmake-config_x64-linux/share/vcpkg-cmake-config/vcpkg_cmake_config_fixup.cmake
zoomsdk-1  | -- Installing: /opt/vcpkg/packages/vcpkg-cmake-config_x64-linux/share/vcpkg-cmake-config/vcpkg-port-config.cmake
zoomsdk-1  | -- Installing: /opt/vcpkg/packages/vcpkg-cmake-config_x64-linux/share/vcpkg-cmake-config/copyright
zoomsdk-1  | -- Performing post-build validation
zoomsdk-1  | Stored binaries in 1 destinations in 3.26 ms.
zoomsdk-1  | Elapsed time to handle vcpkg-cmake-config:x64-linux: 19.7 ms
zoomsdk-1  | vcpkg-cmake-config:x64-linux package ABI: a20346158aac4cdb803cb683ecdefc3faafd752e65e52e3748e294773ecd0494
zoomsdk-1  | Installing 2/6<EMAIL_ADDRESS>zoomsdk-1  | Elapsed time to handle vcpkg-cmake:x64-linux: 839 us
zoomsdk-1  | vcpkg-cmake:x64-linux package ABI: eb4e3852eb046ce518073208e881943afe67fa3bb15224a3021109d6732f3e23
zoomsdk-1  | Installing 3/6<EMAIL_ADDRESS>zoomsdk-1  | Building<EMAIL_ADDRESS>zoomsdk-1  | -- Downloading https://github.com/ada-url/ada/archive/v2.7.6.tar.gz -> ada-url-ada-v2.7.6.tar.gz...
zoomsdk-1  | [DEBUG] To include the environment variables in debug output, pass --debug-env
zoomsdk-1  | [DEBUG] Disabling metrics because vcpkg.disable-metrics exists
zoomsdk-1  | [DEBUG] Trying to load bundleconfig from /opt/vcpkg/vcpkg-bundle.json
zoomsdk-1  | [DEBUG] Failed to open: /opt/vcpkg/vcpkg-bundle.json
zoomsdk-1  | [DEBUG] Bundle config: readonly=false, usegitregistry=false, embeddedsha=nullopt, deployment=Git, vsversion=nullopt
zoomsdk-1  | [DEBUG] Feature flag 'binarycaching' unset
zoomsdk-1  | [DEBUG] Feature flag 'compilertracking' unset
zoomsdk-1  | [DEBUG] Feature flag 'registries' unset
zoomsdk-1  | [DEBUG] Feature flag 'versions' unset
zoomsdk-1  | [DEBUG] Feature flag 'dependencygraph' unset
zoomsdk-1  | [DEBUG] Detected /.dockerenv file
zoomsdk-1  | [DEBUG] 1000: execute_process(curl --fail -L https://github.com/ada-url/ada/archive/v2.7.6.tar.gz --create-dirs --output /opt/vcpkg/downloads/ada-url-ada-v2.7.6.tar.gz.107.part)
zoomsdk-1  | [DEBUG] 1000: cmd_execute_and_stream_data() returned 28 after 130802862 us
zoomsdk-1  | error: Failed to download from mirror set
zoomsdk-1  | error: https://github.com/ada-url/ada/archive/v2.7.6.tar.gz: curl failed to download with exit code 28
zoomsdk-1  |   % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
zoomsdk-1  |                                  Dload  Upload   Total   Spent    Left  Speed
zoomsdk-1  |
zoomsdk-1  | curl: (28) Failed to connect to github.com port 443 after 130784 ms: Connection timed out
zoomsdk-1  |
zoomsdk-1  | [DEBUG] /mnt/vss/_work/1/s/src/vcpkg/base/downloads.cpp(1031):
zoomsdk-1  | [DEBUG] Time in subprocesses: 130802862us
zoomsdk-1  | [DEBUG] Time in parsing JSON: 5us
zoomsdk-1  | [DEBUG] Time in JSON reader: 0us
zoomsdk-1  | [DEBUG] Time in filesystem: 5us
zoomsdk-1  | [DEBUG] Time in loading ports: 0us
zoomsdk-1  | [DEBUG] Exiting after 2.2 min (130803372us)
zoomsdk-1  |
zoomsdk-1  | CMake Error at scripts/cmake/vcpkg_download_distfile.cmake:32 (message):
zoomsdk-1  |
zoomsdk-1  |       Failed to download file with error: 1
zoomsdk-1  |       If you are using a proxy, please check your proxy setting. Possible causes are:
zoomsdk-1  |
zoomsdk-1  |       1. You are actually using an HTTP proxy, but setting HTTPS_PROXY variable
zoomsdk-1  |          to https://address:port. This is not correct, because https:// prefix
zoomsdk-1  |          claims the proxy is an HTTPS proxy, while your proxy (v2ray, shadowsocksr
zoomsdk-1  |          , etc..) is an HTTP proxy. Try setting http://address:port to both
zoomsdk-1  |          HTTP_PROXY and HTTPS_PROXY instead.
zoomsdk-1  |
zoomsdk-1  |       2. If you are using Windows, vcpkg will automatically use your Windows IE Proxy Settings
zoomsdk-1  |          set by your proxy software. See https://github.com/microsoft/vcpkg-tool/pull/77
zoomsdk-1  |          The value set by your proxy might be wrong, or have same https:// prefix issue.
zoomsdk-1  |
zoomsdk-1  |       3. Your proxy's remote server is out of service.
zoomsdk-1  |
zoomsdk-1  |       If you've tried directly download the link, and believe this is not a temporary
zoomsdk-1  |       download server failure, please submit an issue at https://github.com/Microsoft/vcpkg/issues
zoomsdk-1  |       to report this upstream download server failure.
zoomsdk-1  |
zoomsdk-1  |
zoomsdk-1  | Call Stack (most recent call first):
zoomsdk-1  |   scripts/cmake/vcpkg_download_distfile.cmake:270 (z_vcpkg_download_distfile_show_proxy_and_fail)
zoomsdk-1  |   scripts/cmake/vcpkg_from_github.cmake:106 (vcpkg_download_distfile)
zoomsdk-1  |   ports/ada-url/portfile.cmake:1 (vcpkg_from_github)
zoomsdk-1  |   scripts/ports.cmake:175 (include)
zoomsdk-1  |
zoomsdk-1  |
zoomsdk-1  | error: building ada-url:x64-linux failed with: BUILD_FAILED
zoomsdk-1  | Elapsed time to handle ada-url:x64-linux: 2.2 min
zoomsdk-1  | Please ensure you're using the latest port files with git pull and vcpkg update.
zoomsdk-1  | Then check for known issues at:
zoomsdk-1  |   https://github.com/microsoft/vcpkg/issues?q=is%3Aissue+is%3Aopen+in%3Atitle+ada-url
zoomsdk-1  | You can submit a new issue at:
zoomsdk-1  |   https://github.com/microsoft/vcpkg/issues/new?title=[ada-url]+Build+error+on+x64-linux&body=Copy+issue+body+from+%2Ftmp%2Fmeeting-sdk-linux-sample%2Fbuild%2Fvcpkg_installed%2Fvcpkg%2Fissue_body.md
zoomsdk-1  |
zoomsdk-1  | -- Running vcpkg install - failed
zoomsdk-1  | CMake Error at /opt/vcpkg/scripts/buildsystems/vcpkg.cmake:899 (message):
zoomsdk-1  |   vcpkg install failed.  See logs for more information:
zoomsdk-1  |   /tmp/meeting-sdk-linux-sample/build/vcpkg-manifest-install.log
zoomsdk-1  | Call Stack (most recent call first):
zoomsdk-1  |   /usr/share/cmake-3.22/Modules/CMakeDetermineSystem.cmake:124 (include)
zoomsdk-1  |   CMakeLists.txt:2 (project)
zoomsdk-1  |
zoomsdk-1  |
zoomsdk-1  | CMake Error: CMake was unable to find a build program corresponding to "Unix Makefiles".  CMAKE_MAKE_PROGRAM is not set.  You probably need to select a different build tool.
zoomsdk-1  | CMake Error: CMAKE_C_COMPILER not set, after EnableLanguage
zoomsdk-1  | CMake Error: CMAKE_CXX_COMPILER not set, after EnableLanguage
zoomsdk-1  | -- Configuring incomplete, errors occurred!

Hey @Kamalkumarqlu, if you're running into GitHub timeout issues while composing Docker, check out the Recall.ai API.
It’s a simple 3rd party API that lets you use meeting bots to get raw audio/video/metadata from meetings without you needing to spend months to build, scale and maintain these bots.
Here are the API docs: https://docs.recall.ai/page/tutorials


[AMHACK] Error popup should be corrected with proper message for email username validation, when register a tenant

Description:
Error popup should be corrected with proper message for email username validation, when register a tenant
Suggested Labels:
2.1.0
Suggested Assignees:

Affected Product Version:
APIM-2.1.0
OS, DB, other environment details and versions:
Steps to reproduce:

Enable email username
Add a tenant
Enter normal username an Register => an error popsup as below
Improve the error message say enter a valid email address for admin username (since we are giving 3 names)

I’m closing this issue because it has been inactive for more than two years. Please reopen if you still encounter this issue with the latest version.


Enable ABS and ATS

Replace build pipeline with ABS
Replace test with ATS basic test.

Towards https://github.com/giantswarm/giantswarm/issues/28366

maybe also use the released version of architect-orb with ats 0.5.0?


Gltf errors while using Filament

Hi
I made a test project here: https://github.com/mariuspena/TestFilament
I exported the same model with animation from Blender 2.9.2 - with or without compression
(updated to this version because of this issue here: https://github.com/KhronosGroup/glTF-Blender-IO/issues/1326)
and I use them like this:
`
//loadGlb("Airplane_Compressed_glb")
//loadGlb("Airplane_None_Compressed_glb")
loadGltf("Airplane_Compressed_gltf")
//loadGltf("Airplane_None_Compressed_gltf")
`
Result:

all the .glb files work on all of our devices (for now pixel 3, huawei mate x)
all the .gltf files do not work and throw a nasty error: https://pastebin.com/r0qeabSz

I just try to open Airplane_None_Compressed_gltf.gltf on https://gltf-viewer.donmccurdy.com/
It opened without any problem
Same with import it back on blender.
Note that on blender, we got this info/warning. Maybe that some kind of stuff that Filament doesn't like:

I got a response here: https://github.com/google/filament/issues/3596#issuecomment-789895795 saying that is not a Filament issue :(

It seems like there are really two questions here: errors with Draco-compressed model, and a different error with uncompressed .gltf (but not .glb) models. Is that correct? And, could you link to a .blend for testing? You can add .ZIP files to comments directly.

Draco
Those warnings are normal, Draco compression does often change the number of vertices in a model, which is fine. However, the comment from the other thread does worry me:

The glTF accessor wants 12680 vertices, but the decoded Draco mesh has 12684 vertices.

This exporter should be ensuring that the vertex count in the accessor matches the compressed data. Based on the warning logged I would assume that it does. That is odd.
But since the model isn't loading with or without compression in Filament, it is not the root issue here. Unfortunately the glTF Validator cannot validate Draco-compressed data to tell us if it is correct. Access to the .blend might help.

Uncompressed
If a model passes the https://github.khronos.org/glTF-Validator/ test suite without any significant issues, and renders correctly in multiple viewers, but doesn't render in your application, then it's very likely a bug specific to that application or platform. As for the errors in https://pastebin.com/r0qeabSz I think that must be the case, I'm not familiar with the file loading process in Filament.

The Filament team is continuing to get bug reports about this issue:
https://github.com/google/filament/discussions/3815

Hello,
This ticket is quite old, and I am not sure what is the status, and if there are any issue in the glTF-Blender-IO addon.
Without any answer (and simple test case), I will close this ticket in a week.

Closing this ticket.
Feel free to open a new one if you have still some issues!


kicad: migrate to wxGTK32

Description of changes
As in the title.
Things done

Built on platform(s)

[ ] x86_64-linux
[x] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
22.11 Release Notes (or backporting 22.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

@ofborg build kicad

i recommend waiting to merge until there has been a review from a darwin user
or moving the darwin fix to a separate PR

@evils Removed the darwin-specific commit.


Update README.md

Style/grammar edits
Closes T-773857

@ediril
Convex source link throws a 404

@fivetran/menon please take a look at the Convex link throwing a 404.


Placeholder search

close #729

Can you add the label meilisearch-http since only this PR is added to the v0.13.0 Milestones and no the issue.


Add PR template

Add PR template for the project.

I can do this please assign it to me

Do you think this Template will work?
Do you have any change proposals?
Also, I apologise for being late

Can I do this task?

Hi @prathna17,
You can work ok any other issue as this is already assigned.

Closed via #6


[Obsidian] Skip vault selection

Extension
https://www.raycast.com/marcjulian/obsidian
Description
Having to select a vault every time I use a command such as "Search Note" or "Pinned Notes" is cumbersome. There should be a setting to skip vault selection and always choose the last selected vault while still providing a way to switch to a different vault.
Who will benefit from this feature?
No response
Anything else?
No response

Hi @nathaniel-palmer-simplisafe,
you should be able to set a specific vault in the extensions preferences. Just add the path of your vault and it should be auto-selected.

@marcjulianschwarz I'm aware of that option, but ideally there would still be a way to quickly select a different vault from within the command without having to update the settings. I updated the issue to make that clearer.


Add Strikes to KP command

Add strikes to KP command.  Particularly as new players come in, this is meant to be intro content that folks can track progress against - and can share publicly as they are looking to get accepted into raid training / statics.

Working on this now - Can't assign to self.


Windows UC command not Starting

Describe the bug
UC command does not work on Windows bash

It Give Error
Usage: java [options]  [args...]
(to execute a class)
or  java [options] -jar  [args...]
(to execute a jar file)
or  java [options] -m [/] [args...]
java [options] --module [/] [args...]
(to execute the main class in a module)
or  java [options]  [args]
(to execute a source-file program)
Arguments following the main class, source file, -jar ,
-m or --module / are passed as the arguments to
main class.
Solution
In UC to remove Eval from UC script
eval $CLI_JAVA_COMMAND $@  || exit
replace with
$CLI_JAVA_COMMAND $@  || exit
it work in windows bash

Solution also provided, Now it working in my local windows enviroement


[REQUEST] Allow RichHandler to receive custom log rendered class

At this moment RichHandler does use a hardcoded LogRender and the only way to use an alternative one is to modify _log_render after instantiation.
How would you improve Rich?
I am more than happy to create a very small PR that allows user to specify which class to be used for log renderer. That is a no risk change to do as all existing code would default to current LogRender.
What problem does it solved for you?
This would allow implementation of other renderers, like one that does soft wrapping.
The current workaround of using of private attributes is dangerous as it could break on any new rich release.

If you want to customize it to that degree, why not extend the class or write your own version?

I am already doing this, i will publish a link later today after I clean the implementation. Once I do it will be very easy to see why allowing this would make code cleaner as it would reduce the amount of customization or private API usage.
My desired is to minimize the divergence from core rich logger features in order to avoid bugs and other surprises.

It appears that I forgot to include a link to https://github.com/pycontribs/enrich/blob/main/src/enrich/logging.py#L13 -- That is where FluidLogRender is implemented which does not produce output fixed to the terminal width.

You are probably better off overriding emit that using a private attribute.
What might help is factoring out a separate render method that is responsible for just the printing. That would reduce the boiler-plate code, and not require a new public interface.
@ssbarnea you might get better feedback if you ask for advice in solving your problem, rather than asking me to implement your solution to the problem.

I think I started this with https://github.com/willmcgugan/rich/discussions/344 but the thread got bit lost in time. Better to continue there. I am more than interested to improve the hacky implementation.
I agree with you that use of private interfaces was far from great and believe me that every time I read about a new release I get bit scared as I wonder if my hacks stopped working.

I think I'm facing a very similar issue. I want to use the RichHandler as a handler for the logging python module, in a job that is running on Jenkins. The terminal output is captured by Jenkins and the result has a unnecessary hard-wrap that I would like to avoid.

I think I'm facing a very similar issue. I want to use the RichHandler as a handler for the logging python module, in a job that is running on Jenkins. The terminal output is captured by Jenkins and the result has a unnecessary hard-wrap that I would like to avoid.

@willmcgugan do you have any suggestion for the use-case I described above? My console log output is captured by jenkins, so I would very much like to not have it truncated. I really need my console output to not assume any maximum width, as it is captured by another process.

RichHandler was designed for readability on a terminal and uses a table to create the neat columns. There's just no way to soft wrap a table. If you set the console width to maxsize I'm afraid you are going to generate an awful lot of padding!
I'd suggest using a different handler for CI. You could implement a logging handler that prints a Text instance with the required fields.  See the RichHandler source for an example of implementing a logging handler, but your implementation could be much simpler.

Yeah I was hopping I could find something in Rich to support this use-case. I think @ssbarnea implemented such a handler in enrich, but sometimes the libs can get out of sync and it's causing compatibility issues.


Add support for PagerDuty

This PR adds support for PagerDuty.
There are some assumptions made in regards to what should trigger an incident, I'm happy to be corrected on this.
It would be nice to allow Alerts to override some Provider settings e.g. override the channel (integration key) to send alerts to different PagerDuty integrations without needed to create a Provider for each.

Thanks for this PR @MartiUK !

Hi @makkes, @stefanprodan is there anything else needed to progress this PR further?

Please resolve the conflicts with main and squash the commits into one.

Your generated CRD manifests don't match the code. Please run make manifests and commit the changes. Also please squash your commits.


fix(node): add and modify node.Status.Conditions

Which issue(s) this PR fixes:

Issue # longhorn/longhorn#9153
What this PR does / why we need it:
Add the node.Status.Condition ModulesLoaded and check if the module dm_crypt is enabled.
Special notes for your reviewer:
Additional documentation or context

@Mergifyio backport v1.7.x


pretrained checkpoint loading bug

Hi,
I found a bug in pretrained checkpoint loading.
in mmdetection/tools/train.py line: 159
"model.init_weights()"
in convnext.py line:115 "def init_weights(self, pretrained=None): ",  we need set param "pretrained",
but nowhere i can see this param setting location.

Hi,
This seems to be a version mismatch problem. Did you follow our instruction and use the specific version we provided?
We add ConvNeXt model and config files to Swin Detection. Our code has been tested with commit 6a979e2
https://github.com/SwinTransformer/Swin-Transformer-Object-Detection/tree/6a979e2164e3fb0de0ca2546545013a4d71b2f7d


Install-Script from PowerShellGet kills variables in Path variable.

Steps to reproduce
Run Install-script on Windows 10 to install a script from the PowerShell Gallery. On a fresh system the cmdlet will ask you to add to the path PATH Environment Variable Change, if you agree your path variable is screwed up.
Expected behavior
Path environment variable should be:
%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem;%SYSTEMROOT%\System32\WindowsPowerShell\v1.0\;%BinDir%;%BinDir%\scripts;C:\Program Files\WindowsPowerShell\Scripts
Actual behavior
Path environment variable is:
C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\bin;C:\bin\scripts;C:\Program Files\WindowsPowerShell\Scripts
Environment data
I have seen this problem before and wrote a blog post about it:
It also links to code to do it correctly.

@hahndorf Please move the Issue in PowerShellGet repo https://github.com/PowerShell/PowerShellGet

Wrong repo, open issue in PowerShellGet repo and close it here.

For reference https://github.com/PowerShell/PowerShellGet/issues/116


Quick switching of the source will label the wrong source

To reproduce:

Add a source with a nested source
Select the nested source
Press up on the keyboard to change the selection to the parent source and quickly press the add source button
The GUI will think the nest source is still selected when adding a new source
Add the new source to the nested source and try to modify its label
The parent sources label will be change instead of the nested sources

This turns out to be a pretty tricky problem and one that may be more work to fix than it's worth. This happens because, if you're quick enough, you can interrupt the selection of a new source with an action like pressing "Add Source". After you've added a source, MATLAB will then finish running the interrupted select node code and think the wrong node is selected. I'm not aware of a good way to make node selection non-interruptible.