Add --log-level option and retire --silent

This is to be done after: #144
Instead of using --silent we should be adding --log-level and have the many options, for starters:
--log-level 1 to 3
1 = equal to --silent
2 = only show process block()...
3 = show everything (same as without --silent)

@YukihoAA See https://github.com/DeadSix27/waifu2x-converter-cpp/tree/log_level_support
Question: I reached a point where I figured it would be smarter to have a class that handles logging.. as now I have no idea how to otherwise access functions from
main.cpp in w2xconv.cpp
So I thought that with creating a new logging Class, we can pass a reference to that class to w2xconv.
So that w2xconv can call logger->whatever()
Same as I do currently with for example:
print_processing_file()
Only that print_processing_file() is not in a class.
But my c++ skills are limited, I am not so sure how to implement a basic logger class and pass it to w2xconv.

I don't recommend to implement logger class because..
In fact, our libw2x is not in c++, it is C
in C, there is no classes and it is procedural programming language so..
It is not good idea to use external classes in lib and it is more capable to control functions in argument parameter not by calling some classes or something.
If we do that.. there is no meaning that we uses lib.
lib cannot standalone any more so.. It will better to combine in an exe...

Then I'm not sure how to expose functions into w2xconv.cpp defined in main.cpp
And if we can't do that I would have to double up a lot of code, I was going to create the whole format (e.g json/human-readable) etc in main.cpp and have w2xconv only call some functions there..
If we can't do that I would have to define the json logic in w2xconv and main.
Unless theres another way?

You cannot use functions in main.cpp inside of dll directly because it compiled separately.
if you declare some event system class by using struct in w2xconv.cpp and calling it from main.cpp is working but it is not in "C" way. (but actually you can use it anyway... who cares?)
but.. This project is created in C because original creator wanted to extremely speed up.
JSON parsing is quite slow to support.. I doubt it has value to loosing dependence and speed..
I think bypass cout and cerr to string buffer in main.cpp, parse it, and make format for that is more in "C" way and it won't make slowdown if we made toggle function and there is no dependence problem.
and.. if you need real-time support, you can use json parse thread to do that.
if you want to print json in cout, you need to bypass default output or create custom pipeline to other program anyway so.. i think it is better to implement

you can make function pointers in one structure and pass it. it works.

So, catching stderr and stdout in main.cpp, implement a whole new parser just to parse my own stdout and then stdout it in a different format to make it the most "C" ?
That said, since I'd be capturing stdout from w2xlib the original format can be simplified right, comma seperated lists of values, easier to parse.
But still, sounds annoying, I was hoping it's possible to have libw2x expose a logger-function, and everyone using libw2x can either use said logger or ignore it and get no stdout.
And in main.cpp we just don't ignore it.

Yes C language is not comfortable to programmers..
I read CMakeLists.txt, and i found out w2xconv.h, .cpp is "C" but the others does not.
You can create some logger class out side of w2xconv.cpp (*but inside of lib), but i have no idea that works in w2xconv.cpp or not.
EDIT: it works because i declared W2Mat in "Class" but it works fine.
Implement Logger class inside of libw2x but outside of w2xconv, and declare getJSON() function in w2xconv.h is could be solution? we can hand over setting like stdout or toggle funcions in a struct anyway.

Ye, setPathError handles errors from w2xconv to main, however its just passing strings/ints around at single points in the code.
E.g when main.cpp calls check_for_errors().
We'd need a thread to constantly do check_for_logs() which sounds inefficient to me..
however maybe that fixes the log slowing down the processing, not sure.. what would stop w2xconv from just continuing and not waiting for check_for_logs() to finish displaying, nothing.. unless we make it a buffer/queue and check_for_logs() has to dequeue log lines until its empty.. which in many cases will result in the log taking longer than the conversion but won't slow it down anymore.. ?
I'll prob do the w2xlog.cpp and take w2mat as example.. but this will take me some time.. Im not the biggest fan of C/cpp 🙃


Pulse Oximetry 3.1.1 test validation

Test 4.18.06 - Observation resources returned during previous tests conform to the US Core Pulse Oximetry Profile
Based on the 3.1.1 profile
http://hl7.org/fhir/us/core/STU3.1.1/StructureDefinition-us-core-pulse-oximetry.html
We expected a check for code 59408-5 but Inferno is checking for both 59408-5 and 2708-6 to be present in the code section.

us-core-pulse-oximetry profile is based on FHIR oxygensat profile (http://hl7.org/fhir/R4/oxygensat.html). So a resource has to conform to constraints from both profile.
Instead of reading the "Differential View", look at the "Full View" which indicates that both codes are required:

Thanks for the clarification

@yunwwang Another question. In our data we have an Observation with 59408-5, an Observation with 2708-6 and then one that has the panel of 59408-5 and 2708-6. It appears that for the Observations with one LOINC code this test is also picking those up those and thinking they should also have both codes. Is that correct?

Because US Core Pulse Ox profile is based on FHIR Ox Sat profile, all US Core Pulse Ox observations are also FHIR Ox Sat observation, but not vise versa. That is same to say that US Core Pulse Ox observations are a subset of FHIR Ox Sat observations.
It means that all observations with code 59408-5 (US Core Pulse Ox) shall also have code 2708-6 (FHIR Ox Sat) but observation with code 2708-6 may or may not have 59408-5.
"It appears that for the Observations with one LOINC code this test is also picking those up those and thinking they should also have both codes." This is true for those with code 59408-5.
Tests in 4.18 (Pulse Ox) shall not deal with any observation having code 2708-6 only. If there is such observations (having 2708-6 only), please double check the server response in test 4.18.01. Server shall not return such observations.


vscode: Update to version 1.84.0

Remove the 32-bit version as it no longer provides

[x] I have read the Contributing Guide.

This PR seems a bit broken. Can you fix it so this can be merged?

I guess that's because you have accidentally enabled workflows on your fork?

I guess that's because you have accidentally enabled workflows on your fork?

I just fork this repository and push to my fork repository, and magic happens.
Embarrassed 😂.

@mikisama I know how that feels... I had some problems with forks and pull requests as well.
Do you need a hand?

@mikisama I know how that feels... I had some problems with forks and pull requests as well. Do you need a hand?

Yes. I would be grateful if you would help me.
Should I close this issue and let you push your commit?

Should I close this issue and let you push your commit?

Yep, close it, I'll create a new pull request and then ask the reviewer to move over.


ci: skip custom sentry on windows

Thank you for your contribution to the KodaDot NFT gallery.
👇 _ Let's make a quick check before the contribution.
PR type

[ ] Bugfix
[ ] Feature
[ ] Refactoring

What's new?

[x] PR closes #4690

Before submitting Pull Request, please make sure:

[x] My contribution builds clean without any errors or warnings
[x] I've merged recent default branch -- main and I've no conflicts
[x] I've tried to respect high code quality standards
[x] I've didn't break any original functionality
[ ] I've posted a screenshot of demonstrated change in this PR

Optional

[ ] I've tested it at </rmrk/collection/26902bc2f7c20c546a-1FVG7>
[ ] I've tested PR on mobile and everything seems works
[ ] I found edge cases
[ ] I've written some unit tests 🧪

Had issue bounty label?

[x] Fill up your KSM address: Payout

Community participation

[x] Are you at KodaDot Discord?

Screenshot

[ ] My fix has changed something on UI; a screenshot is best to understand changes for others.

pay 50 usd

😍 Perfect, I’ve sent the payout
💵 $50 @ 28.11 USD/KSM ~ 1.779 $KSM
🧗 DY4SQF2iD456tH89aQtz5wv1EV3BbSW8wKKuMcwbmXaj1pM
🔗 0x89b3a7347d11ef90d94089833f806f9180e2648923ee72d92e5727b9e0ca407e
🪅 Let’s grab another issue and get rewarded!
🪄 github.com/kodadot/nft-gallery/issues


systemd-networkd: Add wireguard-related options.

Motivation for this change
The systemd.network nixos module is lacking the wireguard-related options.
Things done
Add wireguard-related netdev options and their associated nixos test.
Note: I omitted both the PrivateKey and PresharedKey options to prevent the user from leaking private keys to the store.

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

[x] NixOS
[ ] macOS
[ ] other Linux distributions

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

CC @andir @flokli @grahamc

I'm confused by the ofborg error here, it seems like it's somehow trying to load /var/run/wg/secret.key.
This string is coming from the example section of the module. Should I set that up to something else? If yes, where?

As for PrivateKey and PreshareKey, why not include them also but give a warning in the description? There might be good reason to use them even if they become world-accessible in the nix store.

I agree - we should include them, but warn.

Note that there is a PrivateKeyFile option in 242

@arianvp this PR adds it already - I still think we shouldn't artificially limit what a user can do. Warning if sb shoots into is food should probably be enough ;-)

Closing in favor of #45392


Failed AsyncTestCase displayed as "PASSED"

This issue was imported from Closure Library's previous home at http://closure-library.googlecode.com
The link to the original issue is:
https://code.google.com/p/closure-library/issues/detail?id=535

Fixed somewhere along the way


Tutorial for Paired RNA+ATAC dataset

Hi, thank you for your excellent tools!
Recently, our collaborator generated a series of 10X multiome datasets, and we hope to use GLUE to our paired datasets.
I found the class PairedSCGLUEModel in your "readthedocs" tutorial. Is there a tutorial for this class and applying GLUE to paired-datasets?
Thanks!

Thanks for your interest in GLUE! Currently there is no tutorial for PairedSCGLUEModel yet. I will add one and let you know when it's ready.

Hi there! The tutorial is finally available. Please be advised that you need the latest version (v0.3.2) of scglue to use it.


Redisson don't switch read operation properly when slave is down

I configured master-slave configuration for standalone Redis. readMode = ReadMode.MASTER_SLAVE
val server = config.useMasterSlaveServers().apply {
masterAddress = master.uri
laves.forEach { addSlaveAddress(it.uri) }
val weights = mutableMapOf<String, Int>()
slaves.asSequence()
.map { it.uri to getReadProbabilityOrDefault(it.readProbability) }
.toMap(weights)
weights[master.uri] = getReadProbabilityOrDefault(master.readProbability)
loadBalancer = RoundRobinLoadBalancer()
readMode = ReadMode.MASTER_SLAVE
}
When I do on slave debug segfault there aren't operations in a monitor on a master node. Only after timeout in 180000 ms all operations will start to perform on the master node. My code didn't receive any exception from Redisson.
I can reduce a delay by setting up failedSlaveCheckInterval = 3000 parameter but why Redisson didn't switch to slave after the first failed command?
And that more important why Redisson didn't send any command to the master node?

but why Redisson didn't switch to slave after the first failed command?

It waits for topology update. In useMasterSlaveServers mode topology is not updated.

It waits for topology update. In useMasterSlaveServers mode topology is not updated.
How can I avoid pause?
Configure standalone Master-slave with another configuration?

try to use cluster or sentinel mode

try to use cluster or sentinel mode

we use standalone redis without sentinel. Just master node with several read slaves. It's not a cluster.
Redisson don't have any options for that configuration?

In this case Redisson can't update topology without any info about it.


[Improve][Manager] Add comments in manager modules

Description
[Improve] Add comments in manager modules
InLong Component
InLong Manager
Are you willing to submit PR?

[X] Yes, I am willing to submit a PR!

Code of Conduct

[X] I agree to follow this project's Code of Conduct

i will deal with this problem.


404 page not found under HTTP

does the relay is supposed to be not accessible thought HTTP?
or it is it still loading events (in which case it could be useful to serve HTTP earlier)
Cheers

Why? It is a personal relay?!

yes, personal
I have an impression that haven is personal,
right?

fixed now.


Added destructor to support migrations starting from django 1.7

According to issue #50 this the missing small code to recognize the custom options.

Super! Thanks for this cool PR :) I read all the confusion you went through in #50 so I really appreciate that you finished it off and made a pull request out of it.
Cheers! :beers:

I just released 0.10.0 which contains your change and the refactoring of #49.
https://pypi.python.org/pypi/django-sortedm2m/


feat(*): Make @HostBinding('disabled') work again

Feature Description
With Material prior 12 I could write a directive with a HostBinding on disabled to support the use case.
  @Directive({
    selector: '[permission]'
  })
  export class PermissionDirective {
    @Input() permission: string = ''; // Required permission
    @HostBinding('attr.disabled') get disabled() {
      return this.permission != "allowed" || null;
    }
  }

Since Material 12 I don't know anymore how to do this. For a button I could add a HostBinding for the class 'mat-button-disabled'.
HostBinding('class.mat-button-disabled')
But how to do it when I want to use the directive for all controls that can be disabled (checkbox, radio, input, ...)?
There was already an issue (#24006) filed regarding that. But with no general solution.
Use Case
I want to disable controls, if the user has no permission to use them

Interacting with a sibling component using a directive might be challenging using attributes and class names. Ideally you use something that provides the permission value directly to the disabled input of the button, like a common service. That way you are not coupled with the implementation details for each individual component.

Could you please elaborate how such a common service would look and how it could interact with the input properties of the different types of components?


Add BETHER token

你好，
合约有问题，请检查。
https://etherscan.io/tx/0x924ad93c12549dac417231ee54ac278bb48e1ab8047ba2d0937cdfbc3d28efc2

@wenyanwang You tried sending tokens to our ERC223 Smart Contract, if the token doesn't have a fallback function it wont work. It's not a problem with our Smart Contract it's just how ERC223 contracts are coded.
您尝试将令牌发送到我们的ERC223智能合约，如果令牌没有后备功能则无法工作。 这不是我们的智能合约的问题，而是ERC223合同的编码方式。

@wenyanwang Also the tokens are still locked, therefore the function you've used raises an error.


[2.2] Return the icon url to the template to display in the UI

Problem: The icon url was not returned to the template so the template
would not display icons for charts with remote icons.
Solution: Do not fetch the icon but still return the url of the icon
to the template

LGTM


BUG: Firmware update source

When trying to download the firmware update from altek, I am requested to sign in with a Microsoft account. Post sign in, I am presented with a prompt message saying the file is not available, or that I do not have access to it.
Is this the only source for a firmware update on the VAIDK or is there other sources?

I have same issue.

I have the same issue.. have you figured anything out yet?

I have been in contact with Olivier Bloch and Altek has now fixed the firmware update and it is ready for download! Thank you Olivier!

Awesome @greeksy! Thanks!


Support --dry-run flag when installing crd

Output of helm version:
version.BuildInfo{Version:"v3.0.2", GitCommit:"19e47ee3283ae98139d98460de796c1be1e3975f", GitTreeState:"clean", GoVersion:"go1.13.5"}
Output of kubectl version:
Client Version: version.Info{Major:"1", Minor:"17", GitVersion:"v1.17.0", GitCommit:"70132b0f130acc0bed193d9ba59dd186f0e634cf", GitTreeState:"clean", BuildDate:"2019-12-13T11:52:32Z", GoVersion:"go1.13.4", Compiler:"gc", Platform:"darwin/amd64"}
Server Version: version.Info{Major:"1", Minor:"15", GitVersion:"v1.15.7", GitCommit:"6c143d35bb11d74970e7bc0b6c45b6bfdffc0bd4", GitTreeState:"clean", BuildDate:"2019-12-11T12:34:17Z", GoVersion:"go1.12.12", Compiler:"gc", Platform:"linux/amd64"}

Cloud Provider/Platform (AKS, GKE, Minikube etc.):
AKS v1.15.7
Hello
What happened?
Trying to run a dry-run fails but actual install succeeds. I'm unsure if it's a problem with helm as a tool or the specific chart
$ helm upgrade -i prometheus-operator stable/prometheus-operator --dry-run
Release "prometheus-operator" does not exist. Installing it now.
manifest_sorter.go:175: info: skipping unknown hook: "crd-install"
manifest_sorter.go:175: info: skipping unknown hook: "crd-install"
manifest_sorter.go:175: info: skipping unknown hook: "crd-install"
manifest_sorter.go:175: info: skipping unknown hook: "crd-install"
manifest_sorter.go:175: info: skipping unknown hook: "crd-install"
Error: unable to build kubernetes objects from release manifest: [unable to recognize "": no matches for kind "Alertmanager" in version "monitoring.coreos.com/v1", unable to recognize "": no matches for kind "Prometheus" in version "monitoring.coreos.com/v1", unable to recognize "": no matches for kind "PrometheusRule" in version "monitoring.coreos.com/v1", unable to recognize "": no matches for kind "ServiceMonitor" in version "monitoring.coreos.com/v1"]

$ helm upgrade -i prometheus-operator stable/prometheus-operator
Release "prometheus-operator" does not exist. Installing it now.
manifest_sorter.go:175: info: skipping unknown hook: "crd-install"
manifest_sorter.go:175: info: skipping unknown hook: "crd-install"
manifest_sorter.go:175: info: skipping unknown hook: "crd-install"
manifest_sorter.go:175: info: skipping unknown hook: "crd-install"
manifest_sorter.go:175: info: skipping unknown hook: "crd-install"
NAME: prometheus-operator
LAST DEPLOYED: Wed Jan 22 07:59:14 2020
NAMESPACE: default
STATUS: deployed
REVISION: 1
NOTES:
The Prometheus Operator has been installed. Check its status by running:
  kubectl --namespace default get pods -l "release=prometheus-operator"

Visit https://github.com/coreos/prometheus-operator for instructions on how
to create & configure Alertmanager and Prometheus instances using the Operator.

Suggested proposal (from @technosophos in https://github.com/helm/helm/issues/7449#issuecomment-591498826):
The most promising proposal (which nobody has yet implemented) was to write a client-side validation for CRs, which would load any CRDs in the crds directory into the local validator and then specifically validate those. While it sounds easy, that's actually a fairly major work-around, since the existing Kubernetes-provided libraries don't really provide us with a way of doing this. PRs are definitely welcome if anyone can think of a clean way of doing this.

At the time of writing prometheus-operator chart includes the new format (the crds/ folder) and it still doesn't work, even when removing the templates using the crd-install hooks.
For what I've found, it seems like all charts that installs CRDs and uses them in the same chart can only install and can't do install --dry-run.

@Xartos Thanks for raising this issue again.
I have confirmed that it fails on --dry-run from the master branch. I am going to set as a bug but would like to get feedback from people who worked on the CRD capability.
@technosophos Is this a bug or expected behaviour?

This was a documented behavior.
At issue is the fact that during a dry run, we do not install the CRDs, but we do use the Kubernetes validation against the output of the chart. So any CR that uses a CRD will fail validation during dry run.
This is one of those edge cases that surfaced during our protracted discussions of CRDs, and their strange place in the Kubernetes world of objects. The purpose of Dry Run is (at least in my mind) to validate that the output of the chart will actually work if sent to the server. But CRDs are actually a modification of the server's behavior. We can't install the CRD on a dry run, so the discovery client will not know about that CR, and validation will fail. But the workaround seems to be ignoring the CR errors, which means one could get spurious validation where the actual server would not have validated it. Effectively, that would invalidate what dry run is supposed to be doing.
The most promising proposal (which nobody has yet implemented) was to write a client-side validation for CRs, which would load any CRDs in the crds directory into the local validator and then specifically validate those. While it sounds easy, that's actually a fairly major work-around, since the existing Kubernetes-provided libraries don't really provide us with a way of doing this. PRs are definitely welcome if anyone can think of a clean way of doing this.

@technosophos Thanks for the feedback and the detailed response.
Just wondering:

Where is this documented? I don't see any mention of it in the CRD doc
Is there a proposal/issue already open that means this issue can be duplicated?

The CRD implementation is described in detail in PR #6243, which implements CRDs in Helm 3.

I guess it could make sense to put that whole thing in documentation.

@jungopro  @technosophos Opened a doc PR to describe that --dry-run flag does not work when CRDs in a chart and is expected behaviour.
Going to set this to a feature (as this is expected behaviour) and change the title.  I will also add @technosophos proposal in https://github.com/helm/helm/issues/7449#issuecomment-591498826 to the description.
Thanks @technosophos for the informed feedback.

looks like this can be closed now that helm/helm-www#545 has been merged for some time.


Restore Bugs :)

Fixes #3360

I think it used .js-repo-nav before too, so we can probably replace most .pagehead selectors with it.

I will try it now.

We used '[data-hotkey="g i"]' but now there are 2 of them. so we need to specify which one.
I dont know how the old layout was

We used '[data-hotkey="g i"]' but now there are 2 of them. so we need to specify which one.

Right, but .js-repo-nav is the right one; the first of those link is in the page header

🙌

My 100th commit to refined github!!


Minor fixes

This fixes the e2e baremetal test and an unnecessary error check for not found after a list operation.

/lgtm

/retest

/retest

/retest


integrate envtest

Pull Request Description
Describe what this PR does / why we need it
Integrate envtest to introduce an automatic integration test.
Does this pull request fix one issue?

Describe how you did it
Describe how to verify it
Special notes for reviews

Codecov Report

Merging #261 (2df68eb) into main (cc3ac8e) will increase coverage by 5.52%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##             main     #261      +/-   ##
==========================================
+ Coverage   25.42%   30.95%   +5.52%
==========================================
  Files          24       34      +10
  Lines        1805     2536     +731
==========================================
+ Hits          459      785     +326
- Misses       1294     1649     +355
- Partials       52      102      +50

Flag
Coverage Δ

unittests
30.95% <100.00%> (+5.52%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

pkg/controllers/networking/node_controller.go
58.18% <100.00%> (ø)

pkg/controllers/networking/ipam.go
59.57% <0.00%> (ø)

pkg/controllers/networking/quota_controller.go
73.01% <0.00%> (ø)

pkg/controllers/networking/error.go
100.00% <0.00%> (ø)

...kg/controllers/networking/ipinstance_controller.go
31.70% <0.00%> (ø)

...controllers/networking/networkstatus_controller.go
61.20% <0.00%> (ø)

.../controllers/networking/subnetstatus_controller.go
77.35% <0.00%> (ø)

pkg/controllers/networking/pod_ip_cache.go
31.74% <0.00%> (ø)

pkg/controllers/networking/pod_controller.go
20.52% <0.00%> (ø)

... and 1 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update cc3ac8e...2df68eb. Read the comment docs.


kpt fn runs functions as nobody which is a hassle for scratch-based containers

Expected behavior
I can use scratch-based containers without adding a fake /etc/passwd file.
Actual behavior
When running kpt fn run, kpt defaults to the user nobody. This means that when I create a container image from scratch, I have to create a fake /etc/passwd file with nobody in it, or the function execution will fail. This is not the end of the world but annoying. Wouldn't a numerical user ID be better?
Information

Steps to reproduce the behavior
Build a docker container from scratch, copying in your kpt function binary.
Run kpt fn run with a declarative function configuration pointing to that container.

Is your request to have the kpt orchestrator run all containers with a well-known uid instead of user nobody?
If so, this would be a backwards incompatible change. Although the Functions Spec doesn't explicitly state user nobody, the API has been effectively defined via current implementation, so we need a very strong justification for changing it:
https://github.com/kubernetes-sigs/kustomize/blob/master/cmd/config/docs/api-conventions/functions-spec.md
I see two AI(s) here:

Through a combination of  functions SDK and documentation, make it easy to create container images that can be run with user nobody.
Functions Spec must be explicit about how the orchestrators invokes the container.

Yes, that is essentially the request. I suppose in my pipeline I can use
the --as-current-user flag. So it's not a huge deal, more of an
inconvenience. It seems an odd default to assume a specific username exists
in the container.
On Mon, Mar 29, 2021 at 10:50 AM Frank Farzan @.***>
wrote:

Is your request to have the kpt orchestrator run all containers with a
well-known uid instead of user nobody?
If so, this would be a backwards incompatible change. Although the
Functions Spec doesn't explicitly state user nobody, the API has been
effectively defined via current implementation, so we need a very strong
justification for changing it:
https://github.com/kubernetes-sigs/kustomize/blob/master/cmd/config/docs/api-conventions/functions-spec.md
I see two AI(s) here:

Through a combination of functions SDK and documentation, make it
easy to create container images that can be run with user nobody.
Functions Spec must be explicit about how the orchestrators invokes
the container.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/GoogleContainerTools/kpt/issues/1628#issuecomment-809581876,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACIHRM5ALBELQV24IDCTYDLTGC4XFANCNFSM42AAVF7Q
.


Allow compilation parameters

'provide a way to change the compilation parameters (e.g. compile to Python 3 instead of universal Python as if you had passed "--target 3")'

[x] write/test backend
[ ] implement frontend
[ ] merge backend PR #51

assigned @jcruz since I don't think I would be able to figure out how/where to stick in a form field for the compile parameters

Postponed to later phase based on the discussion that it may be too advanced for end users.

Will revisit later if needed.

Remaining work on the frontend

https://github.com/cs121-team-panda/coconut-interpreter-react/issues/6
https://github.com/cs121-team-panda/coconut-interpreter-react/issues/7


Lighthouse shuttle

Adds the BC class Emergency Shuttle to Lighthouse

i want you to confirm for me this was saved as a grid and not a map

I'll do a quick re-save, because it;s been a while and don't actually remember.


[GLBC] Support Host HTTP Header for GCE health checks

According to the GCE controller docs, one of the 2 options for passing health checks sent by the GCE load balancers is to expose an arbitrary URL as a readinessProbe - but with a caveat that if the readinessProbe requires "special headers or HTTPS" it defaults back to /.
My request is to make the HTTP Host Header a "non-special header", because it is quite common, and it is explicitly supported by GCE health-checks. Also, this is explicitly mentioned in k8s docs as the way to work with pods that rely on vhosts.
I've hit this issue quite hard when using Ingress to expose a Django app - once I've set DEBUG=False, it went dark because / didn't respond with 200 and GCE load balancer didn't set the Host header which is whitelisted in Django production mode.
I was able to solve it by manually modifying the health-check to use /healthz and add the required Host header. Luckily, GLBC's control loop doesn't detect this as a change and undoes it... (but I'm hoping for a less manual solution)
Here's a sample YAML that can be used to reproduce this behavior:
apiVersion: v1
kind: Service
metadata:
  name: web-app
spec:
  type: NodePort
  ports:
  - port: 5000
    targetPort: web
    name: www
  selector:
    app: app
---
apiVersion: extensions/v1beta1
kind: Deployment
metadata:
  name: app
spec:
  replicas: 1
  template:
    metadata:
      labels:
        app: app
        version: "0.1"
    spec:
      containers:
      - name: app
        image: gcr.io/itamaro/app:0.1
        command: ["python", "-m", "app.app"]
        ports:
        - name: web
          containerPort: 5000
        readinessProbe:
          httpGet:
            path: /healthz
            port: web
            httpHeaders:
              - name: Host
                value: "app.example.com"
          periodSeconds: 30
          timeoutSeconds: 20
          successThreshold: 1
          failureThreshold: 3
apiVersion: extensions/v1beta1
kind: Ingress
metadata:
  name: app-ing
spec:
  backend:
    # Re-use fe as the default backend so we stay under the default
    # quota for gce BackendServices.
    serviceName: web-app
    servicePort: www
  rules:
  # app
  - host: app.example.com
    http:
      paths:
      - backend:
          serviceName: web-app
          servicePort: www

Thanks for creating this issue and preparing a PR.
There's some discussion about changing how GLBC creates health checks.  The current methodology isn't a great indicator of anything other than a node's ability to talk to a pod. In the worst case (a single pod in a large cluster), N health checks hit the pod at every interval. We could address your issue, but it could be irrelevant before the next GLBC release if we're health checking kube-proxy instead of the service.  Let's wait for decisions to be made on that front before merging/closing your PR.

/close


HDDS-8720. Improve thread names in SCM

What changes were proposed in this pull request?
Improve thread names in SCM by adding instance-specific prefix to make it easier to distinguish log messages from different instances.
https://issues.apache.org/jira/browse/HDDS-8720
How was this patch tested?
Ran integration test with SCM HA (e.g. TestSecretKeysApi), checked thread names in log messages.
[scmNode-1-BackgroundPipelineScrubber]
[scmNode-1-ExpiredContainerReplicaOpScrubber]
[scmNode-1-ReplicationMonitor]
[scmNode-1-SCMHATransactionMonitor]
[scmNode-1-SecretKeyManagerService]

CI:
https://github.com/adoroszlai/hadoop-ozone/actions/runs/6532064840

Thanks @ArafatKhan2198, @devmadhuu, @errose28 for the review.


errors

非常好的工作，感谢你的发布。我使用了自己的数据集，但在评估时出现了这个错误，我很疑惑，我的image的形状大小是[3,224,224]， label是[224,224], 我的是二分类，但出现了下面维度不匹配的情况，为什么要用 for ind in range(imag.shape)这个代码吗？这样输入的input不就变成了[1,1,224,224]吗？这和我训练时的输入形状[12,3,224,224]岂不是不匹配，预测会不会因此有问题呢？

Hi @long123524, thank you for your question. The function "test_single_volume()" is directly borrowed from https://github.com/Beckschen/TransUNet/blob/main/utils.py, and "for ind in range(imag.shape)" is used to perform 2D segmentation for each slice in a 3D volumetric medical image (because MT-UNet is a 2D network trained with 2D slices). I'm sorry that this function can only process ordinary single-channel 3D image right now.
If you would like to apply MT-Unet to other 2D datasets, i suggest that you use your own evaluation code. For example, if you would like to evalute the Jaccard Coefficient of the output and your label, simply use:
from medpy.metric import jc

def test_2d:
    model.eval()
    mt_unet_output=model(YOUR_3-224-224_INPUT)  # make sure num_classes is set to 1(BCE).
    score=jc(mt_unet_output, your_label)  # squeeze(0) if u have to
    return score

谢谢你的答复！我还有一个问题，MT-UNet好像并不能适应其他尺寸的大小的图片，比如256×256的图片，我应该如何去修改，才能使得它适用于任何尺寸大小的图片呢？

Hi @long123524, thank you for your further interest. MT-UNet is especially designed for 224×224 input so it can compare with previous sota methods. To make MT-Unet accept 256×256 input, you have to modify the network structure and some more.
Modifications to make MT-Unet accept 256×256 input includes but not limited to:

position_embedding
args.img_size

This issue is closed since no further activity has happened for a while.


no-raw-text fails on line breaks

I don't expect no-raw-text to fail in this case according to the tests, but it does for me.
import React from "react";
import { View, Text } from "react-native";

export default class Test extends React.Component {
  constructor() {
    super();
    this.state = {};
  }

  render() {
    return (
      <View>
        <Text>Some text.</Text>
      </View>
    );
  }
}

Run eslint:
/myproject/src/components/Test.js
  12:13  error  Whitespace(s) cannot be used outside of a <Text> tag  react-native/no-raw-text
  13:40  error  Whitespace(s) cannot be used outside of a <Text> tag  react-native/no-raw-text

It's specifically complaining at the line endings. 🤔
Ideas? Editor line endings are \n. Here's the relevant config:
.eslintrc
{
  "parserOptions": {
    "ecmaVersion": 2018,
    "ecmaFeatures": {
      "jsx": true
    }
  },
  "plugins": [
    "react",
    "react-native",
    "prettier"
  ],
  "env": {
    "react-native/react-native": true
  },
  "extends": [
    "airbnb",
    "plugin:react-native/all",
    "plugin:prettier/recommended"
  ],
  "rules": {
    "prettier/prettier": "error",
    "react/jsx-filename-extension": ["error", { "extensions": [".js", ".jsx"] }]
  }
}

package.json:
{
  "name": "empty-project-template",
  "main": "./index.js",
  "private": true,
  "scripts": {
    "start": "expo start",
    "android": "expo start --android",
    "ios": "expo start --ios",
    "eject": "expo eject",
    "prettier": "prettier src/{,**/}*.js --write",
    "eslint": "eslint src/"
  },
  "dependencies": {
    "expo": "^30.0.1",
    "prop-types": "^15.6.2",
    "react": "16.3.1",
  },
  "devDependencies": {
    "eslint": "^5.9.0",
    "eslint-config-airbnb": "^17.1.0",
    "eslint-config-prettier": "^3.3.0",
    "eslint-plugin-import": "^2.14.0",
    "eslint-plugin-jsx-a11y": "^6.1.2",
    "eslint-plugin-prettier": "^3.0.0",
    "eslint-plugin-react": "^7.11.1",
    "eslint-plugin-react-native": "^3.5.0",
    "prettier": "^1.15.3"
  }
}

Thanks!

will check it

I'm getting the same thing. Something I can do to help look at this?

+1

+1

#208 dupe?

@jasonschock @donovanhiland
can't reproduce the issue 😞
can you create a gist with your code?

I'm seeing this same issue. It looks like it's related to: https://github.com/Intellicode/eslint-plugin-react-native/issues/208

@jdrorrer pls describe your environment

I’ll see if I can get a repo up today with the issue

@AleksandrZhukov https://github.com/donovanhiland/eslint-plugin-react-native-210

@donovanhiland thanks a lot, your repo was very useful
PR with fix is here https://github.com/Intellicode/eslint-plugin-react-native/pull/220

@Intellicode can you create a new release? 🙏

@AleksandrZhukov done, sorry for the wait, but had to fix npm audit issues :)

@AleksandrZhukov thank you for the fix! As of 3.7.0, the rule works just fine. It seems that this issue can be closed?

seems you're right, it can be closed

I am having the same issue with my application which is not using typescript. I am on eslint-plugin-react-native version 3.8.1
package.json
devDependencies": {
"@babel/core": "7.9.6",
"@babel/runtime": "7.9.6",
"@react-native-community/eslint-config": "0.0.5",
"babel-jest": "24.9.0",
"eslint": "^6.8.0",
"eslint-config-airbnb": "^18.1.0",
"eslint-plugin-import": "^2.20.2",
"eslint-plugin-jsx-a11y": "^6.2.3",
"eslint-plugin-react": "^7.20.0",
"eslint-plugin-react-hooks": "^2.5.1",
"eslint-plugin-react-native": "^3.8.1",
"jest": "24.9.0",
"metro-react-native-babel-preset": "0.58.0",
"react-test-renderer": "16.11.0"
},
eslintrc.json
{
"env": {
"react-native/react-native": true,
"browser": true,
"es6": true
},
"extends": [
"airbnb",
"plugin:react-native/all",
"plugin:react/recommended"
],
"globals": {
"Atomics": "readonly",
"SharedArrayBuffer": "readonly"
},
"parserOptions": {
// .jsx extension cannot be used with React Native
//"ecmaFeatures": {
//  "jsx": true
//},
"ecmaVersion": 11,
"sourceType": "module"
},
"plugins": [
"react",
"react-native"
],
"rules": {
"no-console": "off",
// .jsx extension cannot be used with React Native
// https://github.com/airbnb/javascript/issues/982
"react/jsx-filename-extension": ["error", { "extensions": [".js", ".jsx"] }]
}
}
Component
const Welcome = () => (

Hello
How are you

);
It complains with "Whitespace(s) cannot be used outside of a  tag" on every line. I should be permitted to have different elements on different lines not everything on one line.


Feat: Social Winter of Code: Implementation of UI page for Social Winter of Code

Describe the feature
Under this Issue, I intend to complete the Social Winter of Code UI page along with the features already added to the project(Search, Bookmark, Timeline Update) for SWoC.
Add ScreenShots
N.A.
Record

[X] I agree to follow this project's Code of Conduct
[X] I'm a GSSOC'24 contributor
[X] I want to work on this issue

@RishavKumarSinha assign this to me i am GSSOC'24 contributor and have 2+ years of experience in flutter


rarible project link

Updating Rarible to a live project https://github.com/3box/3box/issues/965

@oznekenzo do you know what this is flagging a licence issue, It was only a small change so I can't imagine why it would be a problem?


fix fix error open in scan

Proposed changes
It's possible that the filter becomes ready while executing "_filter_dependency->is_blocked_by(this)".
if (st.is<ErrorCode::PIP_WAIT_FOR_RF>()) {
            DCHECK(_filter_dependency);
            _blocked_dep = _filter_dependency->is_blocked_by(this);
            if (_blocked_dep) {
                set_state(PipelineTaskState::BLOCKED_FOR_RF);
                RETURN_IF_ERROR(st);
            }
        } else {
            RETURN_IF_ERROR(st);
        }

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall


Python: Update reference docs

### Tasks
- [ ] #4703
- [ ] #4685
- [ ] Autodoc from `__init__`?
- [ ] Add link to Conda package

Just an update: I started working on this a month ago but it was harder than it looks and had to shift focus to other priorities.


[UI] Non common annotations are way too much on the right.

I have the following trace https://gist.github.com/ys/f02cf3a291b35b3f52aac8f88c990b08
It has a few custom annotations (sidekiq.start and sidekiq.end`)
The interesting part is:
"annotations": [
      {
        "timestamp":<PHONE_NUMBER>779197,
        "value": "cs"
      },
      {
        "timestamp":<PHONE_NUMBER>783701,
        "value": "sr"
      },
      {
        "timestamp":<PHONE_NUMBER>783703,
        "value": "sidekiq.start"
      },
      {
        "timestamp":<PHONE_NUMBER>975805,
        "value": "sidekiq.end"
      }

You can see that the timestamps between sr and sidekiq.start are super close.
The end is just a few 100ms away.
but the UI displays it wrong.

It lacks the annotations, I discovered I had to scroll a lot to the right.

  8μ : sidekiq

This is the inline CSS, you can see that the left percentage there is totally off.
Unsure what the fix is but I guess it is in the javascript calculation.

can you retry on latest? the build was a bit mucked up

I am on 1.21 if that is the latest.

sorry I was just working on zipkin-ui (a different repo) ignore my comment.

killing irrelevant comments which I caused.

@cburroughs @virtuald either of you bored? :)

@adriancole sorry, got moved to another project, so haven't been using zipkin in a few months. I expect in a few months a different project will start that will need zipkin... we'll see what happens.

@adriancole I can try to take a look. Am I correct seeing this broken or am I doing something wrong?

One thing surprising in that span is that the client and server annotations
have the same endpoint.. was that a loopback?
On 24 Mar 2017 18:16, "Yannick Schutz"<EMAIL_ADDRESS>wrote:
@adriancole https://github.com/adriancole I can try to take a look. Am I
correct seeing this broken or am I doing something wrong?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/openzipkin/zipkin/issues/1541#issuecomment-288984047,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAD61yyrGrD89lsXWfC4JEtqU2k59jX5ks5ro5gRgaJpZM4MljZP
.

It is a sidekiq background job.
So yeah async tasks on same app.

If it doesnt make a remote call, maybe best to not add cs sr in that span.
It is possible there is some ui logic that is looking at that. This is just
a guess
On 24 Mar 2017 20:05, "Yannick Schutz"<EMAIL_ADDRESS>wrote:

It is a sidekiq background job.
So yeah async tasks on same app.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/openzipkin/zipkin/issues/1541#issuecomment-289005890,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAD6124khNW-aWrUkHKzshiht0dN4L-Pks5ro7GSgaJpZM4MljZP
.

This enqueue the job into redis.
Side question is how would you render that ?
It is async jobs with a queue that is redis.
Different instances

Existing code (zipkin-js and finagle) render redis as a client span (cs
cr). There wouldnt be a 'sr' until redis itself has zipkin support. cr is
the end of a span.. if theres something later that happens as a callback
from the redis command.. probably a child span?
Ascii art flow of what is going on in real life might help. Usually the
boxes in a flow diagram end up as spans.
On 24 Mar 2017 9:15 pm, "Yannick Schutz"<EMAIL_ADDRESS>wrote:

This enqueue the job into redis.
Side question is how would you render that ?
It is async jobs with a queue that is redis.
Different instances
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/openzipkin/zipkin/issues/1541#issuecomment-289019342,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAD612Ao1upv4YA-IpfQM6v933InnuyNks5ro8HegaJpZM4MljZP
.

+-------------+       +-------------------------+       +-----------------------------------+
| web request |  --> | Enqueuing job in sidekiq |  --> | worker pick the job and process it  |
+-------------+       +-------------------------+       +-----------------------------------+

https://gist.github.com/ys/a7190081d466747e1d42376cd65928fa here are the two classes responsible for serializing the trace and deserialize it.

here's my 2p:
so I think the client enquing the span would be a one-way "cs"
the worker pulling the message extracts trace ids and adds "sr" to the same
span as the client.
a child span of that should be made for the processing of that message

PS we have messaging spans now.. do you like things like this?

zipkin-classic is no longer maintained, i verified that the linked trace displays correctly in Lens.


feat: add uuid0 and uuid1 features

Add a way to specify uuid 0 or 1, or both!
Signed-off-by: Tiago Castro<EMAIL_ADDRESS>

Based on #455 and #447 we exposed both version 0 and 1.
There is no nice solution here... PTAL


Don't send badge value

Is it currently possible to not send a value for badge count? It seems to be the badge count is always sent since when it isn't explicitly set to something the library sets it to -1. I realize the issue here is differentiating between an empty badge count and a badge count set to zero. Two possible solutions would be to either make badge count an int pointer or create a method/flag on the payload that signals that the user wants to exclude the badge count. Thoughts?

A third option exists which would be to treat badge numbers as such:

badge == 0 - omit
badge > 0 - set badge number
badge < 0 - set badge number to -1 (which Apple treats as 0 on their end)

Just would need to heavily document that if you want to clear the badge number, you should set the badge to < 0 rather than 0.
This doesn't match one to one with Apple's spec but would alleviate the issue without changing the Payload interface.

As an update, ended up going with a typed solution and implementing json Marshaller interface (https://github.com/joekarl/go-libapns/blob/ccef56a3e7cb9f0f0da4add6da007a23ad0da46d/badge_number.go) props to @themartorana for that one


Page titles rendered using H1 should have an ID for permanent link

🐛 Bug Report
Currently in V1 of docusaurus, when the site is generated, it uses the title metadata of each markdown files (default/out of the box behaviour). However, this title does not have any id or anchor links unlike all other headings found in the markdown files.
This is causing a very weird behaviour when the title of the page matches search results (if algolia search is integrated). Clicking on the link from algolia search result, takes us to the correct page but the header/title of the page is tucked under the site navigation header.
I believe this is happening because the title of the page does not have an "id". When the search query matches the page title, it tries to generate a permanent link to that particular "heading". So, Algolia search result generates a permanent link using the closest parent that has an id, which is docsNav.
The issue is easier to see with an illustration.
Have you read the Contributing Guidelines on issues?
Yes
To Reproduce

Go to Docusaurus' documentation site here: https://docusaurus.io/docs/en/installation
In the search box, type query such as version. The search result might look like this:

Click on the result that matches the title/heading of this page (the first result in the above screenshot):  https://docusaurus.io/docs/en/versioning
You'll be taken to a page whose URL looks like this: https://docusaurus.io/docs/en/versioning#docsNav

Expected behavior

Clicking on the search result that matches the page title should have taken me to that page anchored to the page title properly. It should be displayed like this:

Actual Behavior

Clicking on link (https://docusaurus.io/docs/en/versioning#docsNav) from search result takes me to the correct page but the display is skewed. The title is touching the bottom of the top navigation bar:

This does not happen if you try any other anchor links on the page from the right hand side table of content.
Reproducible Demo
(Paste the link to an example repo, including a siteConfig.js, and exact instructions to reproduce the issue.)

@endiliey - Thanks for reviewing this bug report. Do you agree with my assessment of this issue? I think the required change for this is straight-forward (set an id for the title) but I don't have any way of testing or validating the fix.

Actually this is happening to v2 site too, but it isn't a problem there because __docusaurus because it points to the main body div id.
Happening in reactjs.org too, try searching This page is an overview and they'll point to https://reactjs.org/docs/getting-started.html#___gatsby
cc @s-pace from algolia for suggestion.

👋 @endiliey @parvezakkas
In order to have the best redirection possible, we highly recommend website owner to add a unique id to headings (lvlx selectors defined from the DocSearch configuration)
These headings should expose a unique "anchor". Anchors are extracted from HTML attributes (name or id) added to headers that will allow the browser to directly scroll to the right position in the page when clicking a link with a # in it.
From a DocSearch POV, we would need every headings to have a unique id. Not only the h1 tag.

Thanks @s-pace for the explanation.
@endiliey - Do you agree that all docusaurus generated h1 needs to have an id? I haven't checked the V2 code yet, but for V1 I believe the id needs to be set here on line 241
https://github.com/facebook/docusaurus/blob/b56adb7ca1e8a0f473b33c00385e902e46c50409/packages/docusaurus-1.x/lib/core/Doc.js#L236-L248

v2 wont have an id and thats intentional, because the main div body already has id="__docusaurus".
We wont put anchor on both v1 and v2, but I think putting id can make sense for v1 to avoid this scrolling bug. Naturally it will be best to slugify the h1 title, but since the beginning of docusaurus, we never slugify it and it could potentially conflict with other headings defined in markdown
e.g
---
title: hello
---
## Hello

Let's just put id="__docusaurus" here on v1. Its very less likely to see a conflict. Welcoming PR on that

Thanks for the details @endiliey
Sorry but I don't get what are the drawbacks of having a unique id or name attribute to every headers? It is a W3C recommendation for handling links and redirections.
Having the main div body's id set to "__docusaurus" is a good start. However, the redirection will not be as accurate as having every header accessible from a unique anchor.
Thanks

Hmmm. Well, to be honest I don't really know why we did so. (had to ask @JoelMarcey as the original author of Docusaurus), but I think its because we actually just don't want the page title as destination anchors. Similar to how the wc3 example don't want Table of Contents to be a destination anchor. That's why the h1 doesnt have an id
https://www.w3.org/TR/html401/struct/links.html

It's just like https://reactjs.org/docs/getting-started.html

and https://webpack.js.org/api/node/

P.S Interestingly algolia docs also dont have id for its h1. https://community.algolia.com/docsearch/what-is-docsearch.html

Thanks for the prompt reply and the clarification @endiliey
DocSearch Documentation doesn't expose an id for h1 because there is no need to scroll down for these results since h1 are at the top of the page. Every other header does/should expose a unique id or name. By headers, I meant every <hX/> markup, not only h1. Same reasoning applies for webpack. Just notice that this issue is only about <h1/>.
Table of content is always an edge case and I do agree that these elements should not be part of the search either. This one of the reasons why we do recommend to remove them from the DOM before to parse it at the crawling time.
We are going to move our own documentation to docusaurus. I will keep you posted regarding what are the room of improvement in order to provide the best learn-as-you-type experience.

DocSearch Documentation doesn't expose an id for h1 because there is no need to scroll down for these results since h1 are at the top of the page. Every other header does/should expose a unique id or name. By headers, I meant every  markup, not only h1. Same reasoning applies for webpack. Just notice that this issue is only about .

Yep its actually the same for our case too. We didn't put id for h1 because page title are at the top of the page. All other <hX /> will have id. Even h1 header that is not located on the top of the page will have id. (only the most top one don't)

We are going to move our own documentation to docusaurus. I will keep you posted regarding what are the room of improvement in order to provide the best learn-as-you-type experience.

Sure thing. Naturally we want to dogfood docsearch v3 as well when it came out to all of our v2 users

@endiliey - Just for clarification, are you saying that v2 of docusaurus does not need an id for the h1 element that is used as the page title? I just checked the v2 site and looks like it has the same issue (I think you mentioned that once):

In my opinion, all <hx /> elements should have an id. I think another factor contributing to this scrolling bug is not just the lack of id in the page title that is picked up by search; it's because of the fixed header at the top. If the header is not fixed at the top of the page, we wouldn't see this issue.
I spent some time to find a fix using css but haven't found a proper fix yet. Having said that, I think we need to keep styling and html structure separate as separate concern. Styling should not dictate the html structure, because styling can always change, if needed.

Just {this.props.title} to fix it in v1
Sent from Mail for Windows 10

Well, to be honest I don't really know why we did so. (had to ask @JoelMarcey as the original author of Docusaurus), but I think its because we actually just don't want the page title as destination anchors. Similar to how the wc3 example don't want Table of Contents to be a destination anchor. That's why the h1 doesnt have an id

I don't recall the exact reason for this, but I believe @endiliey is correct. At the time, we were not going to anchor h1s. It's very possible though it was just an artifact of how we developed the project and wasn't a real conscience decision.
cc @deltice in case he remembers (Hi 👋)

We are going to move our own documentation to docusaurus. I will keep you posted regarding what are the room of improvement in order to provide the best learn-as-you-type experience.

@s-pace Love this! :)

Well, to be honest I don't really know why we did so. (had to ask @JoelMarcey as the original author of Docusaurus), but I think its because we actually just don't want the page title as destination anchors. Similar to how the wc3 example don't want Table of Contents to be a destination anchor. That's why the h1 doesnt have an id

I don't recall the exact reason for this, but I believe @endiliey is correct. At the time, we were not going to anchor h1s. It's very possible though it was just an artifact of how we developed the project and wasn't a real conscience decision.
cc @deltice in case he remembers (Hi 👋)

Yup, this wasn't really something that had a lot of deliberate thought put into it, we just didn't have anchors for page titles.


Client side router

Arrow looks promising. Is there any plan to build a client side router or an adapter for TankStack router TanStack/router ?

He mentioned routing in the documentation, as I imagine client-side routing might increase the library quite a bit 😊

Router is a key part of a web application. It can be build separately and not as part of core library or an adapter for TankStack router TanStack/router

Personally i'd be interested in using Remix router with ArrowJS at some point — something akin to what @brophdawg11 has been doing with https://github.com/brophdawg11/remix-routers and vue/svelte

For the foreseeable future this will be considered out of scope.

This has been tickling the back of my brain for a little while.  The basic wire up is pretty straightforward given Arrow's reactivity.  The "tricky" part not handled by the @remix-run/router (and this is true for react-router/remix-router-vue, etc.) is handling the nested routing via an <Outlet /> component so you can render nested routes based on router.state.matches.  This then opens up route-scoped useLoaderData() capabilities as well.
Ignoring nested routes though, a simple non-nested UI with Link/Form support clocks in at just over 100 lines including console logs for clarity 😀: https://codesandbox.io/s/remix-router-arrow-js-ncu52c?file=/src/index.js

I guess its time to build an entire meta framework now 😂

Not like you don't have enough else to do 😂 !  If you ever dip into SSR don't forget to check out createStaticHandler from @remix-run/router as well.  Docs are still pending but it'll handle all the server-side data loading aspects for you.

Nice contribution @brophdawg11 ! I'd been looking at a (now archived but still good) routing solution "roadtrip" - which is actually a strong fit for driving view from state with arrow-js. But, as you've shown, the @remix-run stuff is very interesting too....ahhh dilemmas!!

I've been having fun experimenting with Remix router wrappers for Lit and Preact Signals recently and would love to help with a wrapper for Arrow too! As @brophdawg11 mentioned, to properly handle nested routing (and make some other APIs nicer to use), Arrow will need a context system.

I’ve actually been thinking about how context could be created in as minimal of a way as possible — nothing to report yet 😂 but I’m open to suggestions. It’s certainly possible for each template to pass it’s parent’s context down via internal call states, but I really want to avoid creating an implicit tree that requires an arrow template as an ancestor. For example, in a perfect world you could:
<dom-element>
  { arrow-template }
    <another-dom-element-not-rendered-by-arrow>
      { arrow-template } <!-- this guy could read context -->
    </another-dom-element-not-rendered-by-arrow>
  {/ arrow-template }
</dom-element>

The above example assumes that <another-dom-element-not-rendered-by-arrow> is a dom element created by some outside force, lets say someone dropped a chunk of old jQuery code right in there, but then a child of that could still pickup context. Crawling parent nodes is horribly inefficient to be a framework feature though and rendering sequencing cannot be guaranteed in this scenario either so an index-based store wouldn’t work. Sounds like a fun problem honestly. More to think on here.

I have two ideas here:

Use custom elements/web components: there is an open standard protocol for cross-framework web component context using event listeners attached to the custom element. You could create custom elements to handle context in a generic way and then wrap them with a more Arrow-friendly function component syntax. This works particularly well for context compatibility across the DOM tree rather than relying on a home-built system, but it does mean adding extra elements to the DOM, which might be okay in some cases but is definitely not in others. I'll experiment with this some this week in relation to the router.
Use the reactive system: Voby does something interesting here: their context system is part of their reactive system (Oby), not their component/templating system. It's built in a way that any code running within a reactive root can access the context, so this might work well for the sort of jQuery-within-an-Arrow-template scenario, but less well with custom elements, which are instantiated by the browser and managed outside of your control.


wilcoxon() function does not return z-statistic

stats\morestats.py - wilcoxon function
documentation for version of 0.10.0 stated that the first return value is a z-statistic, but the function returned a t-statistic.  However, looking at the 0.12.0 version, it appears that documentation has been amended to reflect the code and not the other way around which would appear more logical.  Any idea why?  If it is desirable to leave the current return values, would it be possible to add the z-statistic to the return list as well?  Thanks.

I would also vote in favour to return the z value as this would make it easier to calculate the effect size z/sqrt(N)

Returning the z value would be super to easily report the statistics.

This could be done in a backwards-compatible way now with @ev-br's suggested Bunch on steroids: https://github.com/scipy/scipy/issues/3665#issuecomment-106085454
So let's say we want to add the Z value and change this issue from defect to enhancement request.
I won't have time to work on this any time soon, but if someone wants to have a go at this I'd be happy to help/review.

I believe that even if we return Z value, it is still not possible to determine one-sided result (whether x-y>0 or y-x>0) using this two-sided statistic, due to the following:
Code:
T = min(r_plus, r_minus)
r_plus = np.sum((d > 0) * r, axis=0) #Always positive
r_minus = np.sum((d < 0) * r, axis=0) #Always positive
Reasoning:
So, if you swap x and y, T will still be the same, z statistics will still be the same
Final Thoughts:
We should also aim to return in some way that whether r_plus was used or r_minus was used (through a flag maybe) in order to know the result of a one-sided tailed test

Any chance this (rejection direction) will get fixed sometime soon? Just got bit by this bug.

In case if someone like me needs that Z stat and couldn't be bother doing the maths reversing return:
copy paste into your project wilcoxon() from: https://github.com/scipy/scipy/blob/v1.2.1/scipy/stats/morestats.py#L2709-L2806
add:
from numpy import (asarray, compress) # requiered for local modification
from scipy.stats import (find_repeats, distributions)
from math import sqrt
replace the:
return WilcoxonResult(T, prob)
with:
return T, prob, z
add a comment at the top to credit scipy.stats library
problem solved ;)

Still not possible to get the z-statistic and direction from wilcoxon()?

@swallan @DominicChm if you need a side project this looks useful


docs: architecture design

Pages

Page(s) that need to be done

Success Criteria
Content that should be covered
Additional context
Examples, reference pages, resources

I am going to close this issue; this is an ongoing process that is better handled by "living" Spec pages:
https://github.com/janhq/cortex.cpp/discussions/categories/specs


dx12 option: GFXRECON_CAPTURE_DRAWCALLS

Specify one index or a range indices drawacalls(include dispatch) based on a ExecuteCommandList index and a CommandList index to capture. The index is 1-based. The args are one submit index, one command index, one or a range indices of draw calls, like "1,1,1" or "1,1,1-2". Default is: Empty string (all drawcalls are captured).
For writing a queue submit, it starts and stops in PreQueueSubmit and PostQueueSubmit, as GFXRECON_CAPTURE_QUEUE_SUBMITS. Since it only write one queue submit, the target commandlist and drawcalls will be saved in Dx12StateWriter.
For writing a commandlist, it check target commandlist in Dx12StateWriter::WriteCommandListState. Only write the target commandlist.
For writing drawcalls, it check target drawcalls in Dx12StateWriter::WriteCommandListCommands. If the drawcalls aren't target, skip them, and skip the rest of commands after the last target drawcall, and write Close, EndRenderPass and EndQuery.

CI gfxreconstruct build queued with queue ID 226028.

CI gfxreconstruct build queued with queue ID 226039.

CI gfxreconstruct build # 4476 running.

CI gfxreconstruct build # 4476 passed.

CI gfxreconstruct build queued with queue ID 226629.

CI gfxreconstruct build queued with queue ID 226632.

CI gfxreconstruct build queued with queue ID 226633.

CI gfxreconstruct build queued with queue ID 226636.

CI gfxreconstruct build queued with queue ID 226734.

CI gfxreconstruct build # 4491 running.

CI gfxreconstruct build # 4491 passed.

CI gfxreconstruct build queued with queue ID 228058.

CI gfxreconstruct build queued with queue ID 228061.

CI gfxreconstruct build queued with queue ID 228064.

CI gfxreconstruct build queued with queue ID 228065.

CI gfxreconstruct build queued with queue ID 228103.

CI gfxreconstruct build # 4511 running.

CI gfxreconstruct build # 4511 passed.

CI gfxreconstruct build queued with queue ID 230041.

CI gfxreconstruct build queued with queue ID 230065.

CI gfxreconstruct build queued with queue ID 230069.

CI gfxreconstruct build queued with queue ID 230083.

CI gfxreconstruct build queued with queue ID 230093.

CI gfxreconstruct build # 4538 running.

CI gfxreconstruct build # 4538 passed.

CI gfxreconstruct build queued with queue ID 231760.

CI gfxreconstruct build # 4564 running.

CI gfxreconstruct build # 4564 passed.

CI gfxreconstruct build queued with queue ID 232173.

CI gfxreconstruct build # 4575 running.

CI gfxreconstruct build # 4575 passed.


Workflow + Engine - Filter out deleted status workflows from the various API calls

We have made the decision to mark Workflows as deleted rather than removing them. This was done as otherwise its hard to render the WorkflowRuns for that workflow.
We could make a decision to show a note that says "this will remove all associated data including activity, if you no longer want it to be runnable, mark this Workflow as inactive instead"

@gchickma @timrbula could you comment on the above.
For delete... do we remove the Workflow, WorkflowTokens, WorkflowRuns, TaskRuns, etc i.e. cascade delete.
Or do we mark as 'deleted' status (keeping in mind we have Active, InActive, Deleted). We then need to make the queries based on status i.e. you cant update a deleted Workflow. -> This is mostly implemented as we stand.
What happens in the current 'delete'? is that what the current inactive is used for?


Added Sorting Program in cpp

Pls review and merge my PR under Hacktoberfest 2022.

Every thing looks good you are good to go


Issue Full-Text Search is not installed, or a full-text component cannot be loaded. on windows container

Hey Guy,
I found this error when I added full-text search to my container.
How can I solve it ??
Thank you in advance.

I found this error when I added full-text search to my container.

How did you add the full-text feature to your container? I am using image "microsoft/mssql-server-windows-developer" and this feature is not installed out of the box. I am struggling now on how I can add this feature for an existing instance. I know via GUI this can be done. There might be also some ways to install a new instance from command line whith specific options. But I don't know a way to add features from command line to an existing instance (installation).

You would need to use the published Dockerfile and change the command line parameters to include the features you want and then build your own image.
Dockerfile: https://github.com/Microsoft/mssql-docker/blob/master/windows/mssql-server-windows-developer/dockerfile
Command line parameters (look for FEATURES parameter): https://docs.microsoft.com/en-us/sql/database-engine/install-windows/install-sql-server-from-the-command-prompt#Feature

@twright-msft I managed to successfully change the command line parameters to include FullText for the Developer version. However, this does not work for the SQL Server Express version. Example Docker file:
https://github.com/robinho81/mssql-server-windows-express-fts
Any reason why this is? I had assumed that SQL Server Express supported Full Text search...

Glad to hear that you got FTS working in the Developer Edition.  Sorry, Express Edition doesnt have FTS in it.
https://docs.microsoft.com/en-us/sql/sql-server/editions-and-components-of-sql-server-2017

If anyone else ends up here, adding FTS to SQL Server on Linux seems a little easier as there's no need to edit and rebuild the Dockerfile as you can base your work on microsoft/mssql-server-linux. These are the key bits for installing FTS (taken from here):
apt install -y curl
curl https://packages.microsoft.com/config/ubuntu/16.04/mssql-server.list | tee /etc/apt/sources.list.d/mssql-server.list
apt update
apt install -y mssql-server-fts

I guess you can do the same and modify the previous installation on Windows with the downloaded SQL.exe.

Express Edition doesnt have FTS in it

is this new for 2017? i'm pretty sure previous releases on express had fts.

@twright-msft Would it be possible to tweak your Dockerfile with FTS to sue SQL Server 2014 instead of 2017? I'm not sure what I should change...

@electrotype  - the Dockerfile you pointed to is only for SQL Server on Linux.  SQL Server on Linux was first released in SQL Server 2017.
You could try to tweak this Dockerfile and get FTS running on Windows containers.
https://github.com/Microsoft/mssql-docker/blob/master/windows/mssql-server-windows/dockerfile
You would need to change the URL for the .box and .exe in the ENV variables at the top of the Dockerfile to point to the SQL Server 2014 versions of those files.

I've revised the steps I posted above:
apt-get update
apt-get install --yes curl apt-transport-https
curl --fail --silent --show-error --location https://packages.microsoft.com/keys/microsoft.asc | gpg --dearmor | tee /usr/share/keyrings/microsoft-archive-keyring.gpg > /dev/null
curl --fail --silent --show-error --location https://packages.microsoft.com/config/ubuntu/16.04/mssql-server-2017.list | sed "s@arch=amd64@arch=amd64 signed-by=/usr/share/keyrings/microsoft-archive-keyring.gpg@" | tee /etc/apt/sources.list.d/mssql-server.list > /dev/null
apt-get update
apt-get install --yes mssql-server-fts

The difference between this and the mssql-agent-fts-ha-tools example is that as per Debian's guidelines, the third-party key is not loaded via apt-key add.

Express Edition doesnt have FTS in it
What about Express with Advanced Services?

Regarding the Linux image: Since Microsoft has changed how the Docker images are build, installing mssql-server-fts does not work anymore. However, you can just extract the .deb and it should work:
wget https://packages.microsoft.com/ubuntu/16.04/mssql-server-preview/pool/main/m/mssql-server-fts/mssql-server-fts_15.0.1500.28-1_amd64.deb
dpkg --extract mssql-server-fts_15.0.1500.28-1_amd64.deb /

And then docker restart the container.
root@c5b9f4b5b88c:/# /opt/mssql-tools/bin/sqlcmd -S localhost -U sa -P pa -Q "SELECT FULLTEXTSERVICEPROPERTY('IsFullTextInstalled')"

-----------
          1

(1 rows affected)

I've just added the full text search feature to the docker file install step, but then I had to follow these instructions: https://social.technet.microsoft.com/wiki/contents/articles/31786.sql-server-not-starting-after-fresh-installation.aspx

I created a fork a while ago. Maybe this helps you:
https://github.com/pulla2908/docker-mssql-server-windows-developer-fti

@pulla2908, it is interesting that you don't add the additional steps noted by the article. I wonder if it has to do with your use of server 2019 instead of 2016.

@JesseKPhillips I immediately moved to 2019 because I wanted to have the latest version. Then I modified the setup to get full text index feature. Maybe this issue is connected to the windows server version but I have no further information about this.

I am having the same problem with RHEL 7 and SQL Server 2019. fts is installed yet SQL Server doesn't recognize it:
Full-Text Search is not installed, or a full-text component cannot be loaded.

1> select @@version
2> go

Microsoft SQL Server 2019 (RTM) - 15.0.2000.5 (X64)
Sep 24 2019 13:48:23
Copyright (C) 2019 Microsoft Corporation
Developer Edition (64-bit) on Linux (Red Hat Enterprise Linux Server 7.6 (Maipo))
(1 rows affected)
1>

@skinfrakkijm
To check if FTS is installed execute:
IF (1 = FULLTEXTSERVICEPROPERTY('IsFullTextInstalled')) print 'INSTALLED' else print 'NOT INSTALLED'
go

@raviumishra don't know why it is not working for you but in case SQL Server 2017 is also an option for you then you can use my docker definition which you can find here.

@pulla2908 Need to use SQL 2019

@raviumishra
About express edition I have no idea.
A while ago I was searching for box and env download URLs in order to move from SQL Server 2017 (Developer) to 2019 but I did not find them. If something can tell me how to get these URLs then I could update my docker definition. @raviumishra  for you I don't know if e.g. Developer Edition is an option at all. However, I struggle with getting the URLs.

i cant believe this issue is 7 years old... 🤦

@haras-unicorn see my post

@haras-unicorn see my post

i dont care about random forks theres a bunch of those already on docker hub - id rather have my own dockerfile
why cant we just have an official image with fts?
like there are images with timescale for postgres


IPMI SDR Cache out of date disables IPMI collectors during update-status hook

IPMI collectors worked on a machine before. At some point, they disappeared from the metrics list silently without triggering any alerts (ipmi_sel_command_success):
2024-03-25 14:36:43 INFO juju.worker.uniter.operation runhook.go:159 ran "update-status" hook (via hook dispatching script: dispatch)
2024-03-25 14:42:20 WARNING unit.hardware-observer/7.update-status logger.go:60 SDR Cache '/root/.freeipmi/sdr-cache/sdr-cache-redacted.localhost' out of date: Please flush the cache and regenerate it
2024-03-25 14:42:20 INFO unit.hardware-observer/7.juju-log server.go:316 IPMI sensors monitoring is not available
2024-03-25 14:42:20 WARNING unit.hardware-observer/7.update-status logger.go:60 SDR Cache '/root/.freeipmi/sdr-cache/sdr-cache-redacted.localhost' out of date: Please flush the cache and regenerate it
2024-03-25 14:42:20 INFO unit.hardware-observer/7.juju-log server.go:316 IPMI SEL monitoring is not available
2024-03-25 14:42:20 INFO unit.hardware-observer/7.juju-log server.go:316 Attempt 1 of /redfish/v1/
2024-03-25 14:42:22 INFO unit.hardware-observer/7.juju-log server.go:316 Response Time for GET to /redfish/v1/: 1.5902138333767653 seconds.
2024-03-25 14:42:22 INFO unit.hardware-observer/7.juju-log server.go:316 Attempt 1 of /redfish/v1/SessionService/Sessions/
2024-03-25 14:42:22 INFO unit.hardware-observer/7.juju-log server.go:316 Response Time for POST to /redfish/v1/SessionService/Sessions/: 0.1784691703505814 seconds.
2024-03-25 14:42:22 INFO unit.hardware-observer/7.juju-log server.go:316 Login returned code 400: {"error":{"code":"iLO.0.10.ExtendedInfo","message":"See @Message.ExtendedInfo for more information.","@Message.ExtendedInfo":[{"MessageId":"iLO.2.14.UnauthorizedLoginAttempt"}]}}
2024-03-25 14:42:22 INFO juju.worker.uniter.operation runhook.go:159 ran "update-status" hook (via hook dispatching script: dispatch)

cat /etc/hardware-exporter-config.yaml
port: 10200
level: INFO

enable_collectors:

  - collector.ipmi_dcmi

  - collector.redfish

redfish_host: "https://redacted"
redfish_username: "redacted"
redfish_password: "redacted"

The issues here are:

update-status hook (or any other hook like config-changed) can disable collectors days or weeks after deployment on its own
SDR cache being out of date is not handled by the charm
it fails silently without any alerts

hardware-observer revision latest/stable   25

This specific behavior is addressed by #213 . So we can close this issue.
#214 and #96 will be addressed in the future


Query examples page contains outdated metric name

What did you do?
Opened the documentation at https://prometheus.io/docs/prometheus/latest/querying/examples/
What did you expect to see?
Examples using the metric http_requests_total  to be valid for the newest Prometheus.
What did you see instead? Under which circumstances?
It is a non-existing metric because it was renamed to prometheus_http_requests_total, therefore half of the page is outdated for newcomers.
System information
No response
Prometheus version
Prometheus version 2.35.0

Prometheus configuration file
No response
Alertmanager version
No response
Alertmanager configuration file
No response
Logs
No response

I am closing this issue as the examples in the page are generic and not tied to Prometheus server itself.


AdvancedFiltering

What does this PR do?
This PR allows the FilterTextBox to support advanced filtering

AND-Operator: Use these chars to match all the substrings: '&', '+', ',', ';'
OR-Operator: Use this char to match any substring: '|'

Example
Typing delete | remove + user will return all Icons which contains delete OR remove AND user

Closes
Closes #219

@timunie your changes have been merged, thanks for your contribution 👍


cask install java FAILS

Description of issue:
Java Cask will not install (but different error than #16475  )
Output of brew cask install java --verbose
==> Caveats
This Cask makes minor modifications to the JRE to prevent issues with
packaged applications, as discussed here:

  https://bugs.eclipse.org/bugs/show_bug.cgi?id=411361

If your Java application still asks for JRE installation, you might need
to reboot or logout/login.

Installing this Cask means you have AGREED to the Oracle Binary Code
License Agreement for Java SE at

  http://www.oracle.com/technetwork/java/javase/terms/license/index.html

==> Downloading http://download.oracle.com/otn-pub/java/jdk/8u66-b17/jdk-8u66-macosx-x64.dmg
/usr/bin/curl -fLA Homebrew-cask v0.51+ (Ruby 2.0.0-481) http://download.oracle.com/otn-pub/java/jdk/8u66-b17/jdk-8u66-macosx-x64.dmg -C 0 -o /Library/Caches/Homebrew/java-1.8.0_66-b17.dmg.incomplete -b oraclelicense=accept-securebackup-cookie
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
100   286    0   286    0     0    250      0 --:--:--  0:00:01 --:--:--   979
100  227M  100  227M    0     0   782k      0  0:04:57  0:04:57 --:--:--  506k
==> Verifying checksum for Cask java
==> Running installer for java; your password may be necessary.
==> Package installers may write to any location; options such as --appdir are ignored.
Password:
==> installer: Package name is JDK 8 Update 66
==> installer: Upgrading at base path /
==> installer:PHASE:Preparing for installation…
==> installer:PHASE:Preparing the disk…
==> installer:PHASE:Preparing JDK 8 Update 66…
==> installer:PHASE:Waiting for other installations to complete…
==> installer:PHASE:Configuring the installation…
==> installer:STATUS:
==> installer:%7.196462
==> installer:PHASE:Writing files…
==> installer:%23.973903
==> installer:PHASE:Writing files…
==> installer:%37.156177
==> installer:PHASE:Writing files…
==> installer:%47.941674
==> installer:PHASE:Writing files…
==> installer:%61.123949
==> installer:PHASE:Writing files…
==> installer:%79.338033
==> installer:PHASE:Moving items into place…
==> installer:%79.938550
==> installer:PHASE:Moving items into place…
==> installer:%91.616866
==> installer:PHASE:Running package scripts…
==> installer:PHASE:Validating packages…
==> installer:%97.750000
==> installer: The upgrade failed (The Installer encountered an error that caused the installation to fail. Contact the software manufacturer for assistance.)
Error: Command failed to execute!

==> Failed command:
["/usr/bin/sudo", "-E", "--", "/usr/sbin/installer", "-pkg", "#<Pathname:/opt/homebrew-cask/Caskroom/java/1.8.0_66-b17/JDK 8 Update 66.pkg>", "-target", "/", "-verboseR"]

==> Output of failed command:
installer: Package name is JDK 8 Update 66
installer: Upgrading at base path /
installer:PHASE:Preparing for installation…
installer:PHASE:Preparing the disk…
installer:PHASE:Preparing JDK 8 Update 66…
installer:PHASE:Waiting for other installations to complete…
installer:PHASE:Configuring the installation…
installer:STATUS:
installer:%7.196462
installer:PHASE:Writing files…
installer:%23.973903
installer:PHASE:Writing files…
installer:%37.156177
installer:PHASE:Writing files…
installer:%47.941674
installer:PHASE:Writing files…
installer:%61.123949
installer:PHASE:Writing files…
installer:%79.338033
installer:PHASE:Moving items into place…
installer:%79.938550
installer:PHASE:Moving items into place…
installer:%91.616866
installer:PHASE:Running package scripts…
installer:PHASE:Validating packages…
installer:%97.750000
installer: The upgrade failed (The Installer encountered an error that caused the installation to fail. Contact the software manufacturer for assistance.)

==> Exit status of failed command:
#<Process::Status: pid 6389 exit 1>
Error: Kernel.exit

Output of brew doctor
Warning: "config" scripts exist outside your system or Homebrew directories.
`./configure` scripts often look for *-config scripts to determine if
software packages are installed, and what additional flags to use when
compiling and linking.

Having additional scripts in your path can confuse software installed via
Homebrew if the config script overrides a system or Homebrew provided
script of the same name. We found the following "config" scripts:
    /Users/carlos/anaconda/bin/curl-config
    /Users/carlos/anaconda/bin/freetype-config
    /Users/carlos/anaconda/bin/libdynd-config
    /Users/carlos/anaconda/bin/libpng-config
    /Users/carlos/anaconda/bin/libpng16-config
    /Users/carlos/anaconda/bin/python-config
    /Users/carlos/anaconda/bin/python2-config
    /Users/carlos/anaconda/bin/python2.7-config
    /Users/carlos/anaconda/bin/xml2-config
    /Users/carlos/anaconda/bin/xslt-config

Output of brew cask doctor
==> OS X Release:
10.10
==> OS X Release with Patchlevel:
10.10.5
==> Hardware Architecture:
intel-64
==> Ruby Version:
2.0.0-p481
==> Ruby Path:
/System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/bin/ruby
==> Homebrew Version:
Homebrew 0.9.5 (git revision 2302; last commit 2016-01-18)
==> Homebrew Executable Path:
/usr/local/bin/brew
==> Homebrew Cellar Path:
/usr/local/Cellar
==> Homebrew Repository Path:
/usr/local
==> Homebrew Origin:
https://github.com/Homebrew/homebrew
==> Homebrew-cask Version:
0.60.0 (git revision dbef; last commit 2 hours ago)
==> Homebrew-cask Install Location:
<NONE>
==> Homebrew-cask Staging Location:
/opt/homebrew-cask/Caskroom
==> Homebrew-cask Cached Downloads:
/Library/Caches/Homebrew
/Library/Caches/Homebrew/Casks
0 files, 0B
==> Homebrew-cask Default Tap Path:
/usr/local/Library/Taps/caskroom/homebrew-cask
==> Homebrew-cask Alternate Cask Taps:
<NONE>
==> Homebrew-cask Default Tap Cask Count:
2942
==> Contents of $LOAD_PATH:
/usr/local/Library/Taps/caskroom/homebrew-cask/lib
/usr/local/Library/Homebrew
/Library/Ruby/Site/2.0.0
/Library/Ruby/Site/2.0.0/x86_64-darwin14
/Library/Ruby/Site/2.0.0/universal-darwin14
/Library/Ruby/Site
/System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/vendor_ruby/2.0.0
/System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/vendor_ruby/2.0.0/x86_64-darwin14
/System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/vendor_ruby/2.0.0/universal-darwin14
/System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/vendor_ruby
/System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/2.0.0
/System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/2.0.0/x86_64-darwin14
/System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/2.0.0/universal-darwin14
==> Contents of $RUBYLIB Environment Variable:
<NONE>
==> Contents of $RUBYOPT Environment Variable:
<NONE>
==> Contents of $RUBYPATH Environment Variable:
<NONE>
==> Contents of $RBENV_VERSION Environment Variable:
<NONE>
==> Contents of $CHRUBY_VERSION Environment Variable:
<NONE>
==> Contents of $GEM_HOME Environment Variable:
<NONE>
==> Contents of $GEM_PATH Environment Variable:
<NONE>
==> Contents of $BUNDLE_PATH Environment Variable:
<NONE>
==> Contents of $PATH Environment Variable:
PATH="/Users/carlos/anaconda/bin:/Users/carlos/anaconda/bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/Library/TeX/texbin:/usr/local/Library/Taps/caskroom/homebrew-cask/cmd:/usr/local/Library/ENV/scm"
==> Contents of $SHELL Environment Variable:
SHELL="/bin/bash"
==> Contents of Locale Environment Variables:
LANG="en_US.UTF-8"
==> Running As Privileged User:
No

In this case, all we are doing is running the .pkg, and it seems like an installer error - Can you try installing Java manually and seeing if the issue persists?

The issue persists when attempting the manual install. I guess the error
might come from another point. Thanks for the attention!
2016-01-19 6:41 GMT-08:00 Aditya Dalal<EMAIL_ADDRESS>
In this case, all we are doing is running the .pkg, and it seems like an
installer error - Can you try installing Java manually and seeing if the
issue persists?
—
Reply to this email directly or view it on GitHub
https://github.com/caskroom/homebrew-cask/issues/17309#issuecomment-172873102
.

Definitely not related to us, then. Try Stack Overflow, perhaps.


libmysofa: add package

proj points to mysofa-shared.vcxproj everytime.... too troublesome to fixup these flags... My attempt to exclude BUILD_STATIC_LIBS did not go as expected... 😕😕😕
Feel free to edit or propose change.
https://github.com/hoene/libmysofa/blob/dd315a8ec1fee7193d40e4a59b12c5590a4a918c/src/CMakeLists.txt#L74
Wasm (Ubuntu) / build (ubuntu-latest, shared) (pull_request) => linked by target "mysofa-static"
Is it set_license("BSD-3-Clause")?

proj points to mysofa-shared.vcxproj everytime.... too troublesome to fixup these flags... My attempt to exclude BUILD_STATIC_LIBS did not go as expected... 😕😕😕

I don't know you mean, you can try
table.insert(configs, "-DBUILD_STATIC_LIBS=" .. (package:config("shared") and "OFF" or "ON"))
table.insert(configs, "-DBUILD_SHARED_LIBS=" .. (package:config("shared") and "ON" or "OFF"))

Is it set_license("BSD-3-Clause")?

Yes, We can reference https://archlinux.org/packages/extra/x86_64/libmysofa

android
r27 ci see https://github.com/xmake-io/xmake-repo/issues/5142
windows

C:\PROGRA~1\MICROS~2\2022\COMMUN~1\VC\Tools\MSVC\1442~1.344\bin\Hostx64\x64\cl.exe  /nologo  -IC:\Users\star\AppData\Local\.xmake\cache\packages\2412\l\libmysofa\v1.3.2\source\build_7ef28615\src -IC:\Users\star\AppData\Local\.xmake\cache\packages\2412\l\libmysofa\v1.3.2\source\windows\third-party\zlib-1.2.11\include -IC:\Users\star\AppData\Local\.xmake\cache\packages\2412\l\libmysofa\v1.3.2\source\src\hrtf /DWIN32 /D_WINDOWS /W3 -Wall /DWIN32 /D_WINDOWS /W3  /Zi /Ob0 /Od /RTC1 -MD -DDEBUG -DVDEBUG /showIncludes /Fosrc\CMakeFiles\mysofa-static.dir\hdf\gcol.c.obj /Fdpdb\ /FS -c C:\Users\star\AppData\Local\.xmake\cache\packages\2412\l\libmysofa\v1.3.2\source\src\hdf\gcol.c

Try to patch xrepo zlib to unbundle deps.

We can apply this patch to improve shared library build.
https://github.com/hoene/libmysofa/commit/1f9c8df42dfd6765e390ed8840341f15e1ab997b#diff-148715d6ea0c0ea0a346af3f6bd610d010d490eca35ac6a9b408748f7ca9e3f4

IDK maybe we should limit BSD & Wasm here, because https://github.com/xmake-io/xmake-repo/blob/aa72d472b106727cf9cd823f1ce675e0c4c19ff5/packages/l/libkmod/xmake.lua#L14-L19 is limited to Linux, android & rely over endian-darwin.h just as shown in Wasm error log of this port with Unsupported platform error.

if deps unsupport some platforms (wasm/ios etc...), We can limit this platforms in on_check
https://github.com/xmake-io/xmake-repo/blob/95aa0e9479edf717df0b993a9c5e6bd9daf4a496/packages/i/igraph/xmake.lua#L25-L31


doesn't work if node binary is called nodejs

If node is not called 'node', but in my case 'nodejs', phantom will fail to install.
><EMAIL_ADDRESS>install /home/blabla/bleble/node_modules/phantomjs-prebuilt
> node install.js

sh: 1: node: not found

npm config content:
$ nodejs node_modules/.bin/npm config list
; cli configs
user-agent = "npm/3.9.5 node/v0.10.29 linux x64"

; node bin location = /usr/bin/nodejs
; cwd = /home/blabla/bleble
; HOME = /home/blabla
; "npm config ls -l" to show all defaults.

I would expect it would use the same binary that called npm.
The workaround mentioned here seems like work that can be automated:
https://www.npmjs.com/package/phantomjs#im-on-debian-or-ubuntu-and-the-installer-failed-because-it-couldnt-find-node

Hmm this seems to be a problem with phantomjs-prebuilt. I don't support version < 3. There is a few missing features that you would need to have a polyfill. Since there is a workaround, and even they say they don't recommend it, then I am going to mark this as won't fix.


List valid subcommands via --help

It is currently quite hard to get started with cargo-crev because the list of valid commands is not displayed when you type an incorrect one.

Sorry, I made an error and invoked cargo-crev instead of 'cargo crev'.

@andrewchambers can we close this?


Checks nova services running in venv

Adds post-upgrade task to check running nova services to ensure
all are running in the correct venv.
Connects rcbops/u-suk-dev#856

failure was on repo setup, unrelated.
recheck_cit_upgrade

Failure was on repo setup, unrelated to PR.
recheck_cit_swift


Resolve CSV to JSON-LD weirdness

I think we have resolved this.... ie attributes were being moved within the JSON-LD or given different parents due to reuse by new Components that are earlier in the alphabet.
@elv-sb if you agree we can close


Error when updating an object that is created within a Transaction

It looks like there is an issue in the TransactionContextManager function used to wrap different rest calls into a transaction. When I attempt to modify an object that is created within a transaction an error message is returned.
From what I can tell when an object is updated the _meta_data['uri'] attribute incorrectly refers to the URI path of the transaction instead of the URI path of the object that will be created.
Using the snippet below pool._meta_data['uri'] == 'https://<IP_ADDRESS>:80/mgmt/tm/transaction/1507766047230839/commands/1/' but in order to modify the object within the transaction the _meta_data['uri'] path is expected to be 'https://<IP_ADDRESS>:80/mgmt/tm/ltm/pool/pool_1/'
Code Snippet:
from f5.bigip import ManagementRoot
mgmt = ManagementRoot(hostname='<IP_ADDRESS>', port='80', username='myUsername', password='myPassword')
transaction = mgmt.tm.transactions.transaction
with TransactionContextManager(transaction, validate_only=False) as tx:
    pool = tx.tm.ltm.pools.pool.create(name='pool_1')
    pool.update(description = 'pool_descr')

Error:
Text: u'{"code":400,"message":"Found invalid command id 1/","errorStack":[],"apiError":1}'

@rotelly and I verified this offline. I will be handling it's fix

@caphrim007 any status on this ?


Use SEND

I'll merge this when https://github.com/Lartu/ldpl/pull/111 makes it into an official release.

using https://github.com/dvkt/ldpl-socket instead


Unable to view the last sub category of  main category.Category menu get closed when trying to click on this category if already any category is opened.

Framework Version: 0.1.5

Framework Version: 0.1.5
Fixed


Air alarm

Related to #1576 and #1579.
We need air alarms. And also fire alarms so you can press a button and make firelocks go brrr.

#5018 closes this...albeit with some bugfixes pending.


build-distro

Updated the pyproject.toml file to include new variables
Updated README to include examples

Codecov Report
Base: 89.20% // Head: 89.20% // No change to project coverage :thumbsup:

Coverage data is based on head (0e5c73b) compared to base (38440a6).
Patch has no changes to coverable lines.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
Additional details and impacted files
@@           Coverage Diff           @@
##           master       #4   +/-   ##
=======================================
  Coverage   89.20%   89.20%
=======================================
  Files           4        4
  Lines         139      139
=======================================
  Hits          124      124
  Misses         15       15

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.