why it?

hi, i do this:

1, install the tmux sudo apt-get install tmux

and it is tmux2.0

2, install powerline pip install powerline-status and sudo apt-get install powerline
3, install your config just like readme 1, 2, 3, 4
4, I change some config as readme
then I restart terminal and turn into tmux but it does not work at all, just like the original tmux
and Why?
anyway, Thx!

Hello, as README.md says, the instructions are just
$ cd
$ rm -rf .tmux
$ git clone https://github.com/gpakosz/.tmux.git
$ ln -s .tmux/.tmux.conf
$ cp .tmux/.tmux.conf.local .

You may want to replace $ rm -rf .tmux with $ mv ~/.tmux ~/.tmux.save.
This tmux configuration doesn't rely on powerline-status nor powerline.
This configuration is a self contained tmux configuration that has a "powerline look & feel". The "powerline look & feel" requires you're using a font that contains the powerline symbols. To do so, you have to follow instructions in README.md in the paragraph entitled "Enabling the Powerline like visual theme".
Please try again or describe better "but it does not work at all".
BTW, as a general tmux tip, for colors to work correctly you want to make sure the TERM environment variable is set to xterm-256color outside of tmux and is set to screen-256color inside of tmux.
Hope that helps.

Hi gpakosz: thx for reply
Just now, i try again, uninstall the tmux, remove the file .tmux, .tmux.conf, .tmux.conf.local
and then
$ cd
$ rm -rf .tmux
$ git clone https://github.com/gpakosz/.tmux.git
$ ln -s .tmux/.tmux.conf
$ cp .tmux/.tmux.conf.local .

But when i start tmux, it still like this, status line nothing append.

It dose not work like the picture in readme

THX again! pardon my poor english!

Hi again,
Can you tell me which version of tmux you're using? By launching:
$ tmux -V

Also, make sure all tmux processes are killed and try again please.

2.0

Can you try with the 2.0 branch then?
cd ~/.tmux
git checkout 2.0

And try again.

plz killall tmux and restart it

thanks @zaxguo @gpakosz
I try check to 2.0 ,and kill all tmux,
it still not work ,it maybe my problam, :smiley:
THX!

According to your screen shot, you're inside the 7th tmux session which seems to indicate a previous tmux server process is still running

But after i kill then and try again.

Which version of Ubuntu are you running?

Ubuntu15.10

Works for me. Here are the steps I followed:
cd /→ ~ cd /tmp
→ /tmp vagrant init ubuntu/wily64; vagrant up --provider virtualbox
A `Vagrantfile` has been placed in this directory.  Please read
the comments in the Vagrantfile as well as documentation on
`vagrantup.com` for more information on using Vagrant.
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Box 'ubuntu/wily64' could not be found. Attempting to find and install...
    default: Box Provider: virtualbox
    default: Box Version: >= 0
==> default: Loading metadata for box 'ubuntu/wily64'
    default: URL: https://atlas.hashicorp.com/ubuntu/wily64
==> default: Adding box 'ubuntu/wily64' (v20160329.0.0) for provider: virtualbox
    default: Downloading: https://atlas.hashicorp.com/ubuntu/boxes/wily64/versions/20160329.0.0/providers/virtualbox.box
==> default: Successfully added box 'ubuntu/wily64' (v20160329.0.0) for 'virtualbox'!
==> default: Importing base box 'ubuntu/wily64'...
==> default: Matching MAC address for NAT networking...
==> default: Checking if box 'ubuntu/wily64' is up to date...
==> default: Setting the name of the VM: tmp_default_1460029312221_72345
==> default: Clearing any previously set forwarded ports...
==> default: Fixed port collision for 22 => 2222. Now on port 2201.
==> default: Clearing any previously set network interfaces...
==> default: Preparing network interfaces based on configuration...
    default: Adapter 1: nat
==> default: Forwarding ports...
    default: 22 => 2201 (adapter 1)
==> default: Booting VM...
==> default: Waiting for machine to boot. This may take a few minutes...
    default: SSH address: <IP_ADDRESS>:2201
    default: SSH username: vagrant
    default: SSH auth method: private key
    default: Warning: Connection timeout. Retrying...
    default: Warning: Remote connection disconnect. Retrying...
    default:
    default: Vagrant insecure key detected. Vagrant will automatically replace
    default: this with a newly generated keypair for better security.
    default:
    default: Inserting generated public key within guest...
    default: Removing insecure key from the guest if it's present...
    default: Key inserted! Disconnecting and reconnecting using new SSH key...
==> default: Machine booted and ready!
==> default: Checking for guest additions in VM...
==> default: Mounting shared folders...
    default: /vagrant => /private/tmp
→ /tmp vagrant ssh
Welcome to Ubuntu 15.10 (GNU/Linux 4.2.0-34-generic x86_64)

* Documentation:  https://help.ubuntu.com/

  Get cloud support with Ubuntu Advantage Cloud Guest:
    http://www.ubuntu.com/business/services/cloud

0 packages can be updated.
0 updates are security updates.

vagrant@vagrant-ubuntu-wily-64:~$ tmux -V
tmux 2.0
vagrant@vagrant-ubuntu-wily-64:~$ git clone https://github.com/gpakosz/.tmux.git
Cloning into '.tmux'...
remote: Counting objects: 353, done.
remote: Total 353 (delta 0), reused 0 (delta 0), pack-reused 353
Receiving objects: 100% (353/353), 131.93 KiB | 0 bytes/s, done.
Resolving deltas: 100% (169/169), done.
Checking connectivity... done.
vagrant@vagrant-ubuntu-wily-64:~$ ln -s .tmux/.tmux.conf
vagrant@vagrant-ubuntu-wily-64:~$ cp .tmux/.tmux.conf.local .

vagrant@vagrant-ubuntu-wily-64:~$ cd .tmux
vagrant@vagrant-ubuntu-wily-64:~/.tmux$ git checkout 2.0
Switched to branch '2.0'
Your branch is up-to-date with 'origin/2.0'.
vagrant@vagrant-ubuntu-wily-64:~/.tmux$

vagrant@vagrant-ubuntu-wily-64:~/.tmux$ tmux

And I ended up having the default look:

If you want the powerline look&feel and change the style of the battery bar, you have to edit ~/.tmux.conf.local.
Hope that helps

Oh! it works!!
Very Thx!!

So? What did you change to make it work?

I just try again....and the same as yesterday..then it works.

Ok. I'm closing this issue then.

it works! This is the original reason！OMG

This https://github.com/gpakosz/.tmux/issues/16#issuecomment-206277590 solves it.
Maybe worth mentioning in README to close all tmux session?
Thanks.


Do not configure launcher if processes are launched externally

What does this PR do?

If processes are created externally, Lightning should not use the subscript process launcher at all. Currently, this is a bug. The launcher is configured, which in turn causes the trainer to invoke this path here: https://github.com/PyTorchLightning/pytorch-lightning/blob/a9bfcc7407d3ca24716497806298c6a1d050b2be/pytorch_lightning/trainer/trainer.py#L722-L723
Does your PR introduce any breaking changes? If yes, please list them.

Before submitting

[ ] Was this discussed/approved via a GitHub issue? (not for typos and docs)
[x] Did you read the contributor guideline, Pull Request section?
[x] Did you make sure your PR does only one thing, instead of bundling different changes together?
[ ] Did you make sure to update the documentation with your changes? (if necessary)
[ ] Did you write any new necessary tests? (not for typos and docs)
[x] Did you verify new and existing tests pass locally with your changes?
[ ] Did you list all the breaking changes introduced by this pull request?
[ ] Did you update the CHANGELOG? (not for typos, docs, test updates, or internal minor changes/refactorings)

PR review
Anyone in the community is welcome to review the PR.
Before you start reviewing make sure you have read Review guidelines. In short, see the following bullet-list:

[x] Is this pull request ready for review? (if not, please submit in draft mode)
[ ] Check that all items from Before submitting are resolved
[x] Make sure the title is self-explanatory and the description concisely explains the PR
[x] Add labels and milestones (and optionally projects) to the PR so it can be classified

Did you have fun?
Make sure you had fun coding 🙃
cc @justusschock @kaushikb11 @awaelchli @akihironitta @rohitgr7

@ananthsub even if the condition if self.strategy.launcher is not None:  is True in a second call to e.g. Trainer.fit (inside a subprocess), we would expect the SubprocessLauncher to skip the call to call_children_scripts and only call the passed through function directly. In other words, the launcher should know itself whether it is in a subprocess already or not.


Typing error on 4_quantum_circuit_properties notebook

Summary
On the second example of the 4_quantum_circuit_properties notebook the right circuit qc2 is not used to compute the different operations like circuit.width() and circuit.size().
Details and comments
I just changed the name qc1 to qc2 on the second part.

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


Backport ca91f5a to 2.1

Workaround for broken Windows Phone client.
Fixes #691.
See #685 for more detail.
(cherry picked from commit ca91f5a9603e53cd4edef2749996ae600cf742a9)

I backported this patch because we use Sabre 2.1 in ownCloud 8.1 and our Windows Phone users need this patch to sync their calendars.

Looks great!


ldeep: 1.0.34 -> 1.0.35

Diff: https://github.com/franc-pentest/ldeep/compare/refs/tags/1.0.34...1.0.35
Changelog: https://github.com/franc-pentest/ldeep/releases/tag/1.0.35
Description of changes

Things done

Built on platform(s)

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

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

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 257576 run on x86_64-linux 1

2 packages built:

ldeep
ldeep.dist


Oops! Unexpected "endfor" tag (expecting closing tag for the "block" tag defined near line 8).

Hello everyone,
Did someone have this issue already:
Oops! Unexpected "endfor" tag (expecting closing tag for the "block" tag defined near line 8).
If so, could you please help me to fix it?
Kind regards,
Ata

For information, this happens when I want to display a specific commit

Sounds like something in your commit is breaking the Twig template. Is there any Twig-specific keyword in this commit?

I have checked it and in facts it is in all commit, example of URL:
https://<server_name>/gitlist/<git_repo>/commit/
Do you also get this issue? To reach it, when I go to a specific repos, I click on "Commits" on the right of "Files", then I choose any commit by clicking "view ", then I get the issue


Add stateful app chart to epinio

https://github.com/epinio/epinio/pull/1652#issuecomment-1195497825
Add the referenced app chart, or something modified fixing issues with it to epinio.
At least for use in testing, to ensure that #1652 works for #1629.
Maybe also as a new standard chart.
~Note: We have this as branch of the helmchart repo ( https://github.com/epinio/helm-charts/tree/additional_application_charts/chart/stateful-appliction ). Not a PR yet. The branch would however be a starting point.~
~Edit: PR is https://github.com/epinio/helm-charts/pull/175, with more app charts than just stateful. Rebased that PR to latest main. TODO comparing the charts to current state (were created in April, between 0.8.1 and 0.9.0 tags).~
Proper PR now is https://github.com/epinio/helm-charts/pull/255. That PR limits itself to the new stateful app chart, and leaves the others behind.
~Packaged at https://chameleons.sfo3.digitaloceanspaces.com/epinio-stateful-application-0.1.15.tgz~ Ignore this.

Indeed the new test failing, plus an existing cli test ...
The API test failures are around listing app charts, i.e. they have to be adapted for the additional chart.

Regarding the new test ... Looks to be a server side issue, with the app not coming up properly ... Needs server logs I believe ... First use of

acceptance/helpers/machine/machine.go:183:func (m *Machine) SaveServerLogs(destination string) {

since that helper was added to the test setup.

Server log contains:

" "report"="StatefulSet is not ready: namespace-184213286/rapps-638969828-57dab137b6cc0d487f9a0bfcbae58c0e2fd58ad5. 0 out of 1 expected pods have been scheduled"

And now I wonder ... The stateful chart allocates a volume to the app, of size 1Gi, for its state.
If creation of that volume fails then the pod will not be scheduled, waiting for it.

Falsified ...
Looking at the STS events note

Warning  FailedCreate      11s (x15 over 94s)  statefulset-controller  create Pod rapps-131928537-ba68929e91ee4945913a02c526956b91f4c111f2-0 in StatefulSet rapps-131928537-ba68929e91ee4945913a02c526956b91f4c111f2 failed error: Pod "rapps-131928537-ba68929e91ee4945913a02c526956b91f4c111f2-0" is invalid: metadata.labels: Invalid value: "rapps-131928537-ba68929e91ee4945913a02c526956b91f4c111f2-d49f6894": must be no more than 63 characters

Label value is getting to long.

So, state: The truncation+hashing of resource names generates names which are too long, by the chart. The Statefulset puts a controller-revision-hash label on the pods, which the name + suffix, and when the original app name is too long (i.e. app-132928537 , etc, as produced by the tests) the added suffix brings it above 63 chars. In manual testing I used a short app name (fox) which generated something which was short enough (just, by 7 chars).
This needs some changes in the name generation done by the chart.
I can do that in 2 weeks, after the vacation.
I am moving the PR back to todo however, and unassign myself, i.e. everybody else is free to have a go at this as well.


SyntaxError: Unexpected token

$ ng server
C:\Users\Administrator\AppData\Roaming\npm\node_modules@angular\cli\models\conf                                     ig\config.js:16
constructor(_configPath, schema, configJson, fallbacks = []) {
^
SyntaxError: Unexpected token =
at exports.runInThisContext (vm.js:53:16)
at Module._compile (module.js:373:25)
at Object.Module._extensions..js (module.js:416:10)
at Module.load (module.js:343:32)
at Function.Module._load (module.js:300:12)
at Module.require (module.js:353:17)
at require (internal/module.js:12:17)
at Object. (C:\Users\Administrator\AppData\Roaming\npm\node_modul                                     es@angular\cli\models\config.js:3:18)
at Module._compile (module.js:409:26)
at Object.Module._extensions..js (module.js:416:10)

Thanks for reporting!
First, could you try ng serve instead of ng server?
Second, could you execute ng version and copy/paste the output in a comment? Make sure your node version is up-to-date (for example, mine outputs node: 7.3.0).

Please reopen if you are still having the issue, but I suspect your node is probably not up to date. Make sure you have the latest version! :)


Fhir data retrieve changes

Fixes issue with Fhir Retrieve to

Not skip inactive patients to ensure deceased patients are not omitted unless cql filters it out
Handle Task beneficiary which is not sent as contextPath. Rather requestor (Practitioner) is sent as contextPath which is not correct and Task should be filtered on 'for` i.e. subject
Handle code filters for entities

Description
Clear and concise code change description.
Type
Choose one: Bug fix
Screenshots (if applicable)
Checklist

[x] I have read and acknowledged the Code of conduct.
[x] I have read the Contributing page.
[x] I have signed the Google Individual CLA, or I am covered by my company's Corporate CLA.
[x] I have discussed my proposed solution with code owners in the linked issue(s) and we have agreed upon the general approach.
[x] I have run ./gradlew spotlessApply and ./gradlew spotlessCheck to check my code follows the style guide of this project.
[x] I have run ./gradlew check and ./gradlew connectedCheck to test my changes locally.
[x] I have built and run the demo app(s) to verify my change fixes the issue and/or does not break the demo app(s).

@maimoonak is this PR still needed?

The issue with activePatients is fixed in the master.
The remaining two fixes for:

Handle Task beneficiary which is not sent as contextPath. Rather requestor (Practitioner) is sent as contextPath which is not correct and Task should be filtered on 'for` i.e. subject
Handle code filters for entities
seem like handling of the edge cases.

I don't have enough context to make a call.  Is @maimoonak still around? Are the problems, fixed in this PR common? If no, would it make sense to make an extension to the workflow library to workaround individual integrators issues, or should we rather enforce the standard?

This was resolved by @vitorpamplona in PR and discussion https://github.com/google/android-fhir/pull/1603#discussion_r982143535. Issue on DBCG repo is https://github.com/cqframework/clinical_quality_language/issues/858.


Add support for bucket to bucket copy

About this change - What it does
This adds support for copy of multiple files across different buckets,
for now only if the two buckets are on the same provider.
Why this way
This enables copying data from bucket to bucket without storing it locally.

Codecov Report

Merging #139 (e7cb156) into main (3142922) will decrease coverage by 0.21%.
The diff coverage is 45.45%.

@@            Coverage Diff             @@
##             main     #139      +/-   ##
==========================================
- Coverage   66.53%   66.33%   -0.21%
==========================================
  Files          35       35
  Lines        3846     3864      +18
==========================================
+ Hits         2559     2563       +4
- Misses       1287     1301      +14

Files Changed
Coverage Δ

rohmu/object_storage/s3.py
61.84% <22.22%> (-1.31%)
:arrow_down:

rohmu/object_storage/azure.py
32.75% <25.00%> (+0.16%)
:arrow_up:

rohmu/object_storage/google.py
39.32% <33.33%> (-0.22%)
:arrow_down:

rohmu/object_storage/base.py
77.51% <80.00%> (-0.07%)
:arrow_down:

rohmu/object_storage/local.py
85.95% <88.88%> (-0.07%)
:arrow_down:

... and 4 files with indirect coverage changes
:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


fix: check delete eol flag

What this PR does / why we need it:
Adds the missing check for eol images
Which issue(s) this PR fixes (optional, using fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when the PR gets merged):
Fixes #
Special notes for your reviewer:

Codecov Report

Merging #712 (01904b9) into main (a6819bd) will decrease coverage by 0.01%.
The diff coverage is 0.00%.

@@            Coverage Diff             @@
##             main     #712      +/-   ##
==========================================
- Coverage   14.58%   14.57%   -0.01%
==========================================
  Files          13       13
  Lines        1700     1701       +1
==========================================
  Hits          248      248
- Misses       1424     1425       +1
  Partials       28       28

Flag
Coverage Δ

unittests
14.57% <0.00%> (-0.01%)
:arrow_down:

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

Impacted Files
Coverage Δ

pkg/scanners/trivy/types.go
23.25% <0.00%> (-0.28%)
:arrow_down:

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


[FEEDBACK] Request for response to contributor/user survey (updated)

We are increasing focus on Dr. Elephant and the community of contributors and users. Our immediate goals are to support the latest versions of Spark. Over the last year, we have noticed that Dr. Elephant is being used more in cloud platforms like AWS and Azure. The following issues track these efforts:

Support for Spark 2.3/2.4 in Dr.Elephant
Support for Hadoop 3
Installation instructions for AWS EMR and Azure HDInsight

We also want to know from you how you are using Dr. Elephant as well as how Dr. Elephant and the community can be improved. Can you please respond to this survey? Your responses will help us prioritize features.
If we have missed something in the survey please let us know in this issue or in the last question of the survey.
@CalvinNeo @jilugulu @luoze-god @BruceXu1991 @PHippolyte @labbedaine @theyaa
@shkhrgpt @KiritoCurry @Tagar @orbiran88 @cpcXiaocun

Kindly take some time to fill out the feedback survey for Dr.Elephant for providing feedback for current features and any requirements you have for which Dr.Elephant can be helpful
@CalvinNeo @jilugulu @luoze-god @BruceXu1991 @PHippolyte @labbedaine @theyaa
@shkhrgpt @KiritoCurry @Tagar @orbiran88 @cpcXiaocun @tooptoop4


NixOS module compatibility

Complete compatibility obviously isn't possible, but for things like auto-generated cachix configurations, it would be convenient to reuse them in nix-on-droid.
Continuing with the cachix config example, NixOS has nix.binaryCaches and nix.binaryCachePublicKeys, while nix-on-droid has the equivalent nix.substituters and nix.trustedPublicKeys. Instances such as these where attrs have the same type and semantics should favor the NixOS names rather than create new incompatible ones that break compatibility.

We do not break compatibility because we never wanted that between NixOS and nix-on-droid. WIth your examples: We aligned to the new wording of latest nix releases, NixOS just still uses the deprecated namings. So we will not rename option to a deprecated wording. Ideally these options should be renamed in NixOS.
Like you said, there will never be compatibility between NixOS and nix-on-droid but if you would like to see new options added to nix-on-droid, feel free to open an issue or a PR.

We aligned to the new wording of latest nix releases, NixOS just still uses the deprecated namings. So we will not rename option to a deprecated wording. Ideally these options should be renamed in NixOS.

While I agree in principle, from a practical perspective, getting that changed in NixOS is much more difficult than adding compatibility here. Big, slow-moving projects, etc. etc.
I've used the mkRenamedOption pattern in home-manager modules to add new names for options while keeping deprecated support for the old name around. Would it not be possible to retcon the NixOS options as the "old" name in cases like these?

I do not get why this would be that difficult in NixOS? Just plug in a mkRenamedOption. I can create the PR (if not already one present) in a few days.
In the mean time you can add the mkRenamedOption in your own config if you need these aliases but I do not see the big benefit because you will never be able to share your whole config between NixOS and nix-on-droid and if we start with these two options then we should be somehow consistent with this compatibility approach which does not look reasonable to me.

And will such a change in NixOS make it back to the stable release channels as well? I'm not super familiar with where option renames are allowed to land stability-wise. If it's just the -unstable branches and the next stable release, then the upstream rename is a non-starter as far as this issue is concerned. It means that anyone wanting to share configs that should be compatible won't be unable to until the next release (and they actually migrate to it), unless they're using unstable. Even then, it still forces migration from the user.

you will never be able to share your whole config between NixOS and nix-on-droid

You're moving the goalposts - I never suggested that the whole config should be sharable. There's obviously been some effort to keep things semi-compatible since many of the attributes do line up. It doesn't seem unreasonable to keep with that effort.

Out of interest: Do you have a concrete use case where you want to share the exact same config file for NixOS and nix-on-droid?
See https://github.com/NixOS/nixpkgs/pull/152950.

Yes - the example options I provided were from my attempts to use the files generated from cachix use <cache name>.
As I said before, unless the renames trickle back to the stable branches, renaming things upstream in NixOS to match nix-on-droid doesn't solve this problem. In addition, you'd also want to make the change in cachix so that it generates the proper attributes, which isn't going to happen unless they increase the minimum supported NixOS release, or put it behind a flag.
So I still stand by my earlier statement that it's much easier to accept the established options here than it is to make the rest of the world change to match.

But doesn't cachix generate the nix.conf file? This one can just be used like that.
Just to be clear: We are not the reason that makes "the rest of the world change", this change of terminology originated from a recent nix release. Therefore, it is not "renaming things upstream in NixOS to match nix-on-droid" but "renaming things upstream in NixOS to match nix".

No, on NixOS, it generates a NixOS module since nix.conf is an immutable file in the store. The configuration for each cache looks like this:
{
  nix = {
    binaryCaches = [
      "https://nix-on-droid.cachix.org"
    ];
    binaryCachePublicKeys = [
      "nix-on-droid.cachix.org-1:56snoMJTXmDRC1Ei24CmKoUqvHJ9XCp+nidK7qkMQrU="
    ];
  };
}

Just to be clear: We are not the reason that makes "the rest of the world change", this change of terminology originated from a recent nix release. Therefore, it is not "renaming things upstream in NixOS to match nix-on-droid" but "renaming things upstream in NixOS to match nix".

Sure, but it doesn't really matter what motivated the change. It's still a slow process to get everything updated since some people would likely need to wait until the new names are backported to the stable branch that they use (if that ever happens) before they can actually use them. In the meantime, it's impossible (or at least inconvenient) for them to share configs using them between NixOS and nix-on-droid.
"Be liberal in what you accept"

FYI: NixOS did a bit of refactoring here. https://github.com/NixOS/nixpkgs/pull/139075


use charset consistently

I don't like this PR, so using it for discussion.
The spec says

Encoding MIME Type: MIME Type for encoding of Data and Metadata. This MAY be a US-ASCII string that includes the Internet media type specified in RFC 2045. Many are registered with IANA such as CBOR. Suffix rules MAY be used for handling layout. For example, application/x.netflix+cbor or application/x.reactivesocket+cbor or application/x.netflix+json. The string may or may not be null terminated.

Does this actually mean:  "This MAY be a Internet media type specified in RFC 2045.  If present, the value MUST be US-ASCII.".  If it can be UTF-8 then string.length() may not be the byte length.
Also can we change the spec to say that the string MUST NOT be null terminated.  we need to string before creating strings.  I assume this is useful if we want to have 0-copy strings in C++.  But we create these garbage strings in Java anyway...
I'll add tests once this is agreed.

@yschimke I am not quiet sure if we want to use US-ASCII over UTF-8, do you want to open an issue for the protocol?
Since, mime-length is part of the frame, I am sure we don't intend it to be null terminated. It would help to make it clear in the spec.

@NiteshKant I agree about using UTF-8, I'll fix the bug with string.length and remove the null termination handling.

@NiteshKant anything blocking this merging? AFAIK it only fixes bug, no breaking behaviour.

@yschimke just time, been busy today. I should be able to get to this today.

👍 LGTM


Make Gherkin less ego-centric

Almost all steps in our Gherkin start with I. I consider this a "ego-centrism" a pretty bad anti-pattern. Steps should describe what is going on, not make the user do every step.

replaces I with the proper noun for who does things

reduces redundancy by replacing the noun with it in repeated steps. Instead of:
Then Git Town prints foo
And Git Town prints bar

it says now:
Then Git Town prints foo
And it prints bar

cc @ChrisMM and @kaylarazavi (FYI only, this is an anti-pattern that I see on a lot of projects)

@kevgo So elegant!
When I first looked at this PR, I was like "Yikes" but then the line changes being equally 1,378 put me quickly at ease. I reviewed a few of the line changes (my workspace & my repository - brilliant!) then scanned through the rest delightfully. Great example to set and share in Engineering and the world.
FYI @ryansand @kbomkamp @larkinmagner

Thanks @ChrisMM! Git Town has exactly 200 feature spec at this point. Any improvement to them leads to massive PRs and hasn’t to be done with automation. In this case I used a tool that allows search-and-replace. That’s another advantage of using Git to store feature specs: one can download them, massage them, and upload the changes again. Try that with 200 JIRA tickets!

I was starting out with nested PRs, but then I could imagine each individual change not making sense without the others. So I merged them all together.
An easy way to review the actual changes is to see the changes of the step implementations at the end of the PR. The Gherkin updates all implement these changes and are mostly very similar to each other. So, if you look at a few dozen lines, you should have seen them all.

All comments addressed

All comments addressed. I also renamed Git Town runs the commands to it runs the commands. I didn't rename Then Git Town is now aware of this branch hierarchy because it would read strange in my opinion.


Multiple select boxes (size > 1) freezes under asynchronous conditions in IE11

We're having issues with select boxes, where selection in one box leads to an asynchronus load of options for the next select box. In IE11 the select boxes will freeze until somthing as simple as setting visibility to hidden and back again.
I have reproduced this in this plunker: http://plnkr.co/edit/NGwG1LUVk3ctGOsX15KI?p=preview
If you fiddle around with the topmost select, the second and third select will often freeze. One interesting thing is that if you open the plunker in its own window, the freezing will not happen. I have tested this with 1.4.7 and 1.5.0-beta-1.
This seems like similar problem to  #11314 and #11795 one thing being different is the async behaviour.

Oh, it's this bug again.  I assume I can count myself lucky that I never had to support IE6-7.

http://plnkr.co/edit/UZGWX9?p=preview
I have similar code & the issue is also reproducible in chrome & IE10

@rockyrfernandes are there any specific steps to produce the bug i your plunker? I'm just clicking around and can't seem to get the selectbox freeze, neither in chrome nor in IE11.

same issue. n in angular v1.3 17.


Increase asyncify stack size

This fixes the example on #105.
I've added the debug script that I used, which I aspire to turn into an automated test in future.
The value does seem rather large but not really significant in a browser context. I've not explored whether it's possible to optimise our asyncify use.
I found an analogous issue in a JS interpreter here: https://github.com/justjake/quickjs-emscripten/issues/112

I use the following test to determine maximum stack depth when calling a function:
def g():
    global depth
    depth += 1
    g()
depth = 0
try:
    g()
except RuntimeError:
    pass
print('maximum recursion depth g():', depth)

That works only when MICROPY_STACK_CHECK is enabled, which it's not for this simulator.  It might be worth trying to enable that option here, which would protect against large call depths.
Otherwise, you can make a simple fixed-depth test like this:
def f(n):
    if n:
        f(n - 1)
f(168)

I use the following test to determine maximum stack depth when calling a function:
def g():
    global depth
    depth += 1
    g()
depth = 0
try:
    g()
except RuntimeError:
    pass
print('maximum recursion depth g():', depth)

That works only when MICROPY_STACK_CHECK is enabled, which it's not for this simulator. It might be worth trying to enable that option here, which would protect against large call depths.
Otherwise, you can make a simple fixed-depth test like this:
def f(n):
    if n:
        f(n - 1)
f(168)

Yeah that makes sense. I got fixated on the structure of the original example. I've updated it to be a Python example alongside the others. Both examples you give work for me without enabling MICROPY_STACK_CHECK.
If I do enable MICROPY_STACK_CHECK (which is enabled for the CODAL port) I see worse behaviour:
FATAL: uncaught NLR 0x510d30 [firmware.js:1483:35](http://localhost:63072/build/firmware.js)
Aborted(Assertion failed: native function `stackRestore` called after runtime exit (use NO_EXIT_RUNTIME to keep it alive after main() exits)) [firmware.js:990:6](http://localhost:63072/build/firmware.js)
Aborted(Assertion failed: native function `mp_js_force_stop` called after runtime exit (use NO_EXIT_RUNTIME to keep it alive after main() exits)) [firmware.js:990:6](http://localhost:63072/build/firmware.js)
Simulator internal error: [demo:205:23](http://localhost:63072/demo)
Error: Aborted(Assertion failed: native function `mp_js_force_stop` called after runtime exit (use NO_EXIT_RUNTIME to keep it alive after main() exits))
    abort http://localhost:63072/build/firmware.js:1013
    assert http://localhost:63072/build/firmware.js:512
    createModule http://localhost:63072/build/firmware.js:1075
    forceStop http://localhost:63072/build/simulator.js:2201
    createRunningPromise http://localhost:63072/build/simulator.js:2470
    start http://localhost:63072/build/simulator.js:2440
    flash http://localhost:63072/build/simulator.js:2548
    createMessageListener http://localhost:63072/build/simulator.js:2751
    EventListener.handleEvent* http://localhost:63072/build/simulator.js:2826
    <anonymous> http://localhost:63072/build/simulator.js:2827
[demo:206:23](http://localhost:63072/demo)

Some of that (the mp_js_force_stop bit) seems like it might be a knock-on error from whatever originally goes wrong.
For the moment at least, I think it makes sense to go with the PR as I've just updated it.


fix: incorrect linux checksums

Summary
The checksums seem to have changed for the linux versions. This updates all of the ones that have changed by running scripts/mirror_releases.sh for all existing versions in versions.bzl.
Motivation
My CI runs are failing with a checksum validation error:
ERROR: An error occurred during the fetch of repository 'cypress_linux-x64':
   Traceback (most recent call last):
	File "/home/runner/.cache/bazel/_bazel_runner/f11a8be521d5e75cfb1ae3f1c16635c8/external/aspect_rules_cypress/cypress/repositories.bzl", line 27, column 40, in _cypress_repo_impl
		repository_ctx.download_and_extract(
Error in download_and_extract: java.io.IOException: Error downloading [https://cdn.cypress.io/desktop/12.3.0/linux-x64/cypress.zip] to /home/runner/.cache/bazel/_bazel_runner/f11a8be521d5e75cfb1ae3f1c16635c8/external/cypress_linux-x64/temp629800849139[56](https://github.com/jackvincentnz/lab/actions/runs/7592287327/job/20681466740?pr=248#step:5:57)60268/cypress.zip: Checksum was 3a300d6c903a8f5fced488183dcc7faa06e9df14c946d6dab4b5822ec738e9cd but wanted 57dd85936373e6ce2ae5378f9035a3ad118899341e0c6e71783c3e58c039ce92
ERROR: /home/runner/work/lab/lab/WORKSPACE:437:28: fetching cypress_repositories rule //external:cypress_linux-x64: Traceback (most recent call last):
	File "/home/runner/.cache/bazel/_bazel_runner/f11a8be521d5e75cfb1ae3f1c16635c8/external/aspect_rules_cypress/cypress/repositories.bzl", line 27, column 40, in _cypress_repo_impl
		repository_ctx.download_and_extract(
Error in download_and_extract: java.io.IOException: Error downloading [https://cdn.cypress.io/desktop/12.3.0/linux-x64/cypress.zip] to /home/runner/.cache/bazel/_bazel_runner/f11a8be521d5e75cfb1ae3f1c16635c8/external/cypress_linux-x64/temp6298008491395660268/cypress.zip: Checksum was 3a300d6c903a8f5fced488183dcc7faa06e9df14c946d6dab4b5822ec738e9cd but wanted [57](https://github.com/jackvincentnz/lab/actions/runs/7592287327/job/20681466740?pr=248#step:5:58)dd85936373e6ce2ae5378f9035a3ad118899341e0c6e71783c3e58c039ce92
ERROR: no such package '@@cypress_linux-x64//': java.io.IOException: Error downloading [https://cdn.cypress.io/desktop/12.3.0/linux-x64/cypress.zip] to /home/runner/.cache/bazel/_bazel_runner/f11a8be521d5e75cfb1ae3f1c16635c8/external/cypress_linux-x64/temp6298008491395660268/cypress.zip: Checksum was 3a300d6c903a8f5fced488183dcc7faa06e9df14c946d6dab4b[58](https://github.com/jackvincentnz/lab/actions/runs/7592287327/job/20681466740?pr=248#step:5:59)22ec738e9cd but wanted 57dd8[59](https://github.com/jackvincentnz/lab/actions/runs/7592287327/job/20681466740?pr=248#step:5:60)36373e6ce2ae5378f9035a3ad118899341e0c6e71783c3e58c039ce92

Type of change

Bug fix (change which fixes an issue)

Test plan

Covered by existing test cases

@jackvincentnz I haven't checked it out but do you know the reason for the test failure? Have it setup locally where you can take a look?

@jackvincentnz I haven't checked it out but do you know the reason for the test failure? Have it setup locally where you can take a look?

@jbedard Not sure. This is working for me locally:
➜  rules_cypress git:(main) bazel test //...
Starting local Bazel server and connecting to it...
INFO: Analyzed 22 targets (302 packages loaded, 13663 targets configured).
INFO: Found 18 targets and 4 test targets...
INFO: Elapsed time: 32.612s, Critical Path: 17.86s
INFO: 42 processes: 13 internal, 9 darwin-sandbox, 18 local, 2 worker.
INFO: Build completed successfully, 42 total actions
//cypress/tests/cli_test:cli_test                                        PASSED in 16.2s
//cypress/tests/module_test:module_test                                  PASSED in 16.4s
//docs:update_0_test                                                     PASSED in 0.1s
//docs:update_1_test                                                     PASSED in 0.1s

Executed 4 out of 4 tests: 4 tests pass.
There were tests whose specified size is too big. Use the --test_verbose_timeout_warnings command line option to see which ones these are.

The tests themselves passed in ci, but it is the parsing of the result at the end that is failing:
[186:0122/081012.841989:ERROR:connection.cc(46)] X connection error received.
One or more cypress tests have failed
Could not find Cypress test run results

I have added some additional log output from the cypress result to see what the contents are. Likely we are expecting something from output differently to what is there.
Once we know the right property to check for failures we can fix this. In my own cypress consumption, I am having to check result.totalFailed !== 0 instead of result.failures like this repo. Maybe that changed for some reason with the new checksum. 🤷♂
https://github.com/jackvincentnz/lab/blob/caed085d30b7314b552d5cd1323930d9a181f070/learn/cypress/module_test/runner.js#L31

Now it magically stopped? Is it just flaky?
Mind dropping the console log for now? 😅

Now it magically stopped? Is it just flaky?
Mind dropping the console log for now? 😅

@jbedard Dropped. I think at least we can assume it is unrelated to this PR. Maybe related to this: https://github.com/tnicola/cypress-parallel/issues/89


Bugfix/additional dsb tests

Made 0.3.9 compatible with tests on Docker with changes to requirements.txt, run_docker_tests.sh, and Dockerfile

Great, thanks. This solves issues #3 and #4 .


Add more tests for Permissions class

Added more tests to the Permissions class that tries to cover more of the methods than were already being tested. These are similar to the existing tests for GuildPermissions and ChannelPermissions but work more closely with Permissions by converting them to ulong raw values first.
Added tests for OverwritePermissions that checks that values are set correctly and that flags can be toggled correctly, including when both allow and deny are set for the same bit.
Tried to make tests fail with issue described in #965 but I was unable to find a case that broke the tests. Would appreciate input and any suggestions on making a test case for that. (CC: @FiniteReality )
My discord handle is @ChrisJ#8703 should you need to ping/DM me.

I may be making a bad habit out of doing more than one thing in a PR.
The GuildPermissions and ChannelPermissions classes didn't need to be part of the Test class, and would fail if the test fixture wasn't supplied. I moved them into their own classes..


[Rendering] Column render error in ReactNative AdaptiveCard

Target Platforms
Other
SDK Version
2.2.24
Application Name
Test app
Problem Description
When I use ReactNative to render AdaptiveCard, I found that the column layout is error, when the card width is auto
I think that the column flex is set error, when width is auto, we should not set the flex attr.
Screenshots

Card JSON
{
    "type": "AdaptiveCard",
    "version": "1.3",
    "body": [
        {
            "type": "ColumnSet",
            "columns": [
                {
                    "type": "Column",
                    "width": "auto",
                    "items": [
                        {
                            "type": "Image",
                            "url": "https://searchuxcdn.azureedge.net/designerapp/images/servicenow-icon.png",
                            "size": "Small",
                            "horizontalAlignment": "Center",
                            "altText": "Not available"
                        }
                    ],
                    "height": "stretch"
                },
                {
                    "type": "Column",
                    "width": 8,
                    "items": [
                        {
                            "type": "TextBlock",
                            "text": "[KB0033192 OneITVSO: Create Repos In a Test Instance and Provide Force Push Access](https://microsoft.service-now.com/kb_view.do?sys_kb_id=713adb5d131fd6003976bc42f244b0f2)",
                            "color": "Accent",
                            "size": "Medium",
                            "weight": "Bolder"
                        },
                        {
                            "type": "TextBlock",
                            "text": "Last modified {{DATE(2022-03-21T14:02:23Z,SHORT)}}",
                            "spacing": "None"
                        },
                        {
                            "type": "TextBlock",
                            "text": " 1. You can create repositories through the web application 2. For links to both Prod and Staging, ...",
                            "wrap": true,
                            "maxLines": 3,
                            "spacing": "Small",
                            "color": "Dark"
                        }
                    ],
                    "horizontalAlignment": "Center",
                    "spacing": "Medium"
                }
            ]
        }
    ],
    "$schema": "http://adaptivecards.io/schemas/adaptive-card.json"
}

Sample Code Language
No response
Sample Code
No response

Please file this in the BigThinkCode/AdaptiveCards repo, as that's where active development on the ReactNative renderer happens. Thanks!


Ensure all promises are persisted on the heap

Unlike dictionaries, there is no use case for a limited lifetime promise. The lifetime of promises can extend the lifetime of local scopes and normally have to.

@MarshallOfSound please rebase on the latest master to fix the CI jobs.


Undefined behavior in ElementTransformation::GetIntPoint()

https://github.com/mfem/mfem/blob/893b127aedb8c495efb63cf1f45d7befe23c4db9/fem/eltrans.hpp#L54
The IntegrationPoint pointer stored in an ElementTransformation object is NULL by default but the GetIntPoint() method dereferences this pointer without checking its value.  I imagine that in practice this pointer is set using SetIntPoint() before any calls to GetIntPoint() are made but can we really be certain of this?
Also, SetIntPoint() could be used to pass in a NULL pointer which would also lead to undefined behavior in GetIntPoint().
I'd like to suggest that we add a method to ElementTransformation class which could be used to check if an IntegrationPoint is set i.e. a method that returns (IntPoint != NULL).  So that nervous developers can call this before calling GetIntPoint().

I personally dislike design that allow attributes to be NULL, one of the (many) problem with NULL pointers I've tried to explain to @v-dobrev is that we have to always check if NULL which has many drawbacks. I think that in this case we shouldn't allow IntegrationRule to be NULL, if we allow it means that we need to carry all the information to build the IntegrationPoint by ourself in some way, but if we now have to carry this information then we don't need this function (which is just bug prone since it can be NULL in an unpredictable way).
What I suggest is either this can never be NULL (we should always have an IntegrationRule associated when building the object), or we remove this method and the associated attribute to avoid bugs. I imagine that for backward compatibility none of this is possible though... Maybe adding a constructor that does not let the user set the IntegrationRule to NULL, and throwing a warning message saying that the other constructor is deprecated because unsafe, and adding your function bool HasIntegrationRule() const is an acceptable path.

@YohannDudouit , I tend to use a lot of NULL pointers so I cannot say that I agree with you completely.  The trouble is that it is not always possible to have all of the necessary information needed to build all contained objects when the container is being constructed.  With that in mind I tend to use NULL pointers as indicators that the containing object is not yet ready to be used.
However, the trouble with ElementTransformation is more subtle.  The IntegrationPoint class does not require any arguments for its constructor so we could certainly create one inside ElementTransformation by default.  But then we have what looks like a valid integration point even when it really is not valid.  It may have the incorrect dimension and its value is (0,0,0) which may not be what you need.  And furthermore you have no way of knowing if this is the default integration point or one that was intentionally set.  The way the code is written now, calls to GetIntPoint made before SetIntPoint will cause a segfault which is not ideal but at least it halts execution which is probably for the best.  If we had a default integration point then execution would continue but with invalid data which would be bad (and difficult to debug).
I think the better alternative is to add a check for the NULL pointer which developers could use inside MFEM_ASSERT or MFEM_VERIFY to issue warnings in debug mode.  Then we would know that we have forgotten to a set proper integration point.

@mlstowell I guess this is the reason behind RAII, I think that we should not construct object if the constructor does not build an object that is ready to use (This is called a broken object). The construction of the object should be delayed until the point where you have all the information needed to construct a well formed object. I agree that there is cases where it is not possible, I don't think this is the case for an ElementTransformation.
Using the explicit keyword for the default constructor of IntegratorRule could solve some of the issues you're mentioning (or deleting it, i.e. making it private? since I'm not sure a default IntegrationRule has meaning). I agree that using the default constructor does not solve this problem. I had a similar problem recently with the IntegrationRule contained in NonlinearFormIntegrator who was NULL. I think we should be more careful with the use of this kind of function that can return NULL, because we don't always have an easy way to figure out what the value should be (because it should not be NULL). The problem is that programmers are lazy by essence, they write only what is necessary for a code to work, so if we let them set to NULL something that they don't use, it's likely that they do it, and then a user of this same code does not understand why something that shouldn't be NULL is NULL... This is why NULL makes poor API.
The thing that I don't like with the check for NULL is that it does not solve our problem, because we want the value that this NULL should have had, knowing that this is NULL barely helps in reconstructing the value. The best way to solve this problem, in my opinion, would be to forbid to set it to NULL and see where the code does not compile, and set the IntegrationRule at this point. I agree that it might result in several compilation errors which might not be trivial to solve.
How where you thinking of recovering the value of this IntegrationRule or IntegrationPoint?

@mlstowell  Looking closer at ElementTransformation it looks like most of its attributes are here to do some kind of caching. Usually, this kind of attributes is marked with the mutable keyword, it would also be good for the const correctness of mfem, because then most methods of ElementTransformation class could be const. I think it would make sense since evaluating the transformation, Jacobian, etc... does (should?) not conceptually change the state of an ElementTransformation.
class ElementTransformation
{
private:
   mutable const IntegrationPoint *IntPoint;
   mutable DenseMatrix dFdx, adjJ, invJ;
   mutable double Wght;
   mutable int EvalState;
   enum StateMasks
   {
      JACOBIAN_MASK = 1,
      WEIGHT_MASK   = 2,
      ADJUGATE_MASK = 4,
      INVERSE_MASK  = 8
   };
   int geom, space_dim;

   // Evaluate the Jacobian of the transformation at the IntPoint and store it
   // in dFdx.
   virtual const DenseMatrix &EvalJacobian() const = 0;

   double EvalWeight() const;
   const DenseMatrix &EvalAdjugateJ() const;
   const DenseMatrix &EvalInverseJ() const;

public:
   int Attribute, ElementNo;//really? mutable too?

   ElementTransformation()
   : IntPoint(new IntegrationPoint)//memory leak? we don't have to store a pointer... copying 4 values is not really expensive
   , EvalState(0)
   , Attribute(-1)
   , ElementNo(-1)
   {}

   void SetIntPoint(const IntegrationPoint *ip) const //Why a pointer here and a reference bellow? change this one to a reference? Since we don't want to evaluate at `NULL`... or is it a feature?
   { IntPoint = ip; EvalState = 0; }
   const IntegrationPoint &GetIntPoint() const { return *IntPoint; }

   virtual void Transform(const IntegrationPoint &, Vector &) const = 0;
   virtual void Transform(const IntegrationRule &, DenseMatrix &) const = 0;

   /// Transform columns of 'matrix', store result in 'result'.
   virtual void Transform(const DenseMatrix &matrix, DenseMatrix &result) const = 0;

   /** @brief Return the Jacobian matrix of the transformation at the currently
       set IntegrationPoint, using the method SetIntPoint(). */
   /** The dimensions of the Jacobian matrix are physical-space-dim by
       reference-space-dim. The first column contains the x derivatives of the
       transformation, the second -- the y derivatives, etc. */
   const DenseMatrix &Jacobian() const
   { return (EvalState & JACOBIAN_MASK) ? dFdx : EvalJacobian(); }

   double Weight() const { return (EvalState & WEIGHT_MASK) ? Wght : EvalWeight(); }

   const DenseMatrix &AdjugateJacobian() const
   { return (EvalState & ADJUGATE_MASK) ? adjJ : EvalAdjugateJ(); }

   const DenseMatrix &InverseJacobian() const
   { return (EvalState & INVERSE_MASK) ? invJ : EvalInverseJ(); }

   virtual int Order() const = 0;
   virtual int OrderJ() const = 0;
   virtual int OrderW() const = 0;
   /// Order of adj(J)^t.grad(fi)
   virtual int OrderGrad(const FiniteElement *fe) const = 0;

   /// Return the Geometry::Type of the reference element.
   int GetGeometryType() const { return geom; }

   /// Return the dimension of the reference element.
   int GetDimension() const { return Geometry::Dimension[geom]; }

   /// Get the dimension of the target (physical) space.
   /** We support 2D meshes embedded in 3D; in this case the function will
       return "3". */
   int GetSpaceDim() const { return space_dim; }

   /** @brief Transform a point @a pt from physical space to a point @a ip in
       reference space. */
   /** Attempt to find the IntegrationPoint that is transformed into the given
       point in physical space. If the inversion fails a non-zero value is
       returned. This method is not 100 percent reliable for non-linear
       transformations. */
   virtual int TransformBack(const Vector &pt, IntegrationPoint &ip) const = 0;

   virtual ~ElementTransformation() { }
};

This does not directly solves your problem, but we could propose a cleaner API that goes in the direction I proposed. Then, it would solve your problem I think.

I think that having:
mutable IntegrationPoint IntPoint;

would solve your problem. I think this is reasonable, because storing the pointer is not really less expensive, because when we use a new point we need to read its values, thus copying the new IntegrationPoint should be relatively inexpensive.

I think that the idea of GetIntPoint() is to give you the point at which DenseMatrix dFdx, adjJ, invJ; double Wght; are cached so that you can avoid a potentially expensive computation of these. You shouldn't be worried to use the method SetIntPoint() as you need it.

This issue will be resolved by PR #593


Voice file not playing

Describe your bug here.
As said in the title the voice file isn't playing, it does play in the chart editor, however. I've made sure that it is a .ogg file, I've made sure it looked exactly like other songs in my mod, but it just wont load or play in game, or in the player in the chart editor.
Command Prompt/Terminal logs (if existing)
No response
Are you modding a build from source or with Lua?
Lua
What is your build target?
Windows
Did you edit anything in this build? If so, mention or summarize your changes.
Not in the source files, I have that downloaded but I want to get the pre-compiled build finished

Nevermind, I'm just fricking dumb. I checked the .JSON and needs voices was false.


Revise the flow of the documentation

Docusaurus automatically adds PREV and NEXT page links, even across category boundaries, which sometimes misleads the readers of the documentation by implying a sequential connection between often unrelated pages.
We should make sure this does not happen by either removing these cross-links or ensuring that there is a continuity between the pages that are connected this way.

This has been resolved.


CI fails on master branch due to sample app + ASAN

CI fails on master branch, e.g. https://github.com/trustwallet/wallet-core/actions/runs/1591071772
Building the sample CPP app was added to the CI; it links with the wallet-core lib which is built in the previous steps.
As coverage is enabled, linking with coverage tooling had to be added to the sample app as well.
Same with ASAN: on master branch ASAN check is enabled.
Either add ASAN flags to sample app as well, or re-build the lib with no coverage&asap (takes long), and link with that.

Reopen, will close once it is verified that CI build is green on master branch (after PR merge)

Last build on master succeeded, with Asan+coverage enabled sample app building. Closing.
https://github.com/trustwallet/wallet-core/runs/4591216341?check_suite_focus=true


Do you have the sample file

Do you have the sample file

Not yet, I'm sorry. I'm working on another work. but I'll be back to develop this project soon.

Do you have the sample file

Not yet, I'm sorry. I'm working on another work. but I'll be back to develop this project soon.


Fix rendering of images

Fixes the rendering of the images which are currently rendered as a code block

@pascalberger : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@pascalberger : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@pascalberger : Thanks for your contribution! The author(s) have been notified to review your proposed change.

Hi @pascalberger, Thanks for this update. In preview, I still see the images rendered as code block. I believe both images need to be indented with 2 more spaces...

@pascalberger : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@chcomley I addd two more spaces, but this seems wrong to me. 4 spaces should be fine, like you have in other documents (e.g. here).
Is it possible for me to see the preview rendering somewhere? At least on GitHub it renders fine.

#sign-off

Thanks @pascalberger, The preview in GitHub should be fine. I'm not sure what was going on. Thanks very much for your contribution!


Explicit and Implicit conversions on Derived and Base Classes

Would not casting a derived class to a base class lose all data only present in the derived class? I would think that casting a base class to a derived class would lose no data.
For example:

class A
{
    int a = 5;
}
class B : A
{
    int b = 4;
}

Casting an instance of class B to A would lose the value of b, but the other way (A -> B) would lose no data.

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

ID: 91266ab9-071d-067c-df52-8a297045af24
Version Independent ID: 1d378928-4bb5-6bcf-49ca-2026768ab2aa
Content: Casting and Type Conversions (C# Programming Guide)
Content Source: docs/csharp/programming-guide/types/casting-and-type-conversions.md
Service: unspecified
Product: dotnet-csharp
GitHub Login: @BillWagner
Microsoft Alias: wiwagn

Sorry, got this cleared up. I didn't know fields weren't inherited.


Add PrimeNG

Fix https://github.com/pascalgrimaud/qualitoast/issues/20

Codecov Report

Merging #39 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master      #39   +/-   ##
=======================================
  Coverage   80.71%   80.71%
=======================================
  Files          71       71
  Lines        1799     1799
  Branches       92       92
=======================================
  Hits         1452     1452
  Misses        314      314
  Partials       33       33

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 89f9874...dc2a5df. Read the comment docs.


Getting 400 response in cloudwatch logs

Hi @OxHimanshu
in case if it still relevant for you and for any who might found this usefull  -
The issue is that Discord don't accept None format and it may be occured at least for lines
#15
"value": event["Trigger"]["Dimensions"][0]["value"] if len(event["Trigger"]["Dimensions"]) > 0 else 'no data',
&&&
#25
"value": event.get("AlarmDescription") if event.get("AlarmDescription") == True else "no description",
above is workaround that work fine for me (at least so far ) :)

Hey @truekoi thanks for the solution. Please @OxHimanshu let me know if it works for you too


Add change details to audit log

It would be helpful if the audit log included some details of the change made, rather than just indicating that a change occurred.
A few use-cases:

Post-mortems
Debugging
Double checking changes made by others
Checking recent changes to the state of the system (like skimming over recent commits/merges in a git repo to catch up on where everything is at)

With the refactor of the AuditLog, this will be achievable using the history record stored against the AuditLog record.
Note that this functionality available in django-simple-history may also come in useful when implementing this.

The API for this was implemented here. It works by adding a new endpoint (GET /api/v1/audit/:id/) to retrieve a specific AuditLog record which includes a change_details attribute consisting of a list of changes that were made to trigger the AuditLog record.
Further details of the new endpoint can be found by reviewing the API docs here.

@matthewelwell This is ready to test under the flag audit_log_detail

Flag has been enabled in all environments.


Double-click, "Open", or "Open With" from Windows 10 File Explorer won't open file

Sometimes, when I double-click a file associated with VS Code, VS Code will open if it is not already open, but the selected file does not open in VS Code. If VS Code is already running, nothing at all happens (not even focus change). Same is true for "Open" and "Open With" from the context menu (right-click). Using "code " on the command line works whether VS Code is already running or not. I've tried uninstalling and reinstalling VS Code and several registry hacks found on the Web. Any other suggestions?

Ok, I didn't try uninstalling, cleaning registry of all references to vscode, rebooting, then reinstalling (which put VS Code in the Appdata directory now and rewrote all the registry keys). All working now. Whew! It had been that way for years and I finally got around to looking into it.


WIP: functional API

If we swap the order of data and params, the params associated with the model are treated as defaults and can be overriden by giving them explicitly.
This (to my understanding) makes the function callable with parameters as args instead of updating the parameters in the model.
There should not be any legacy issue as I hardly doubt anyone gives wrong parameter values and relies on the functionto overwrite it with the defaults?
If that's fine, I'll gladly add a quick test, changelog etc.
What do you think @redeboer ?

Thanks for the explanations @redeboer, that's useful insights!
But I think my point is different: the order of the arguments doesn't matter (as it's a mapping), but the code has a different meaning
params = {**p1, **p2}

gives precedence to p2
In the code, this means that it gives precedence to the default args. So think of the following
assuming it takes x (data) and mu, sigma (parameters). The model has a default for mu and sigma.
We can call it with just data = {'x': array}. That's fine, it uses mu & sigma as defaults.
But we cannot explicitly say the parameters here, i.e. data = {'x': array, 'mu': float} will not use mu, because it will be override by the default.
Now it says basically "if the users gives a parameter value, override it and ignore it, use the default". On the other hand, if we swap as suggested, it's "use the default values if not given, but if the user provides a parameter explicitly, use that instead"
So nothing changes anywhere basically except that a parameter can be given explicitly. Actually, the current order of deliberatly (and silently!) overwriting parameters that are given explicitly to the function is probably not intentional? It looks a bit to me as if this always should have been the other way around?
Or is there maybe any disadvantage that I don't see?

Yes, exactly, that's the idea, and I think, except of adding in the docs that you can also use it directly, there is nothing to change, should be 100% backwards compatible but rather forward compatible (at least if I think about the best API idea).

Btw, is there a speficic use case you have in mind?

The main consequence: it becomes jittable (right? Or am I missing something here?)! Also, the parametrized function becomes, automatically, from a very specific object that has a very specific interface (such as the parameter update) to a general function that takes the variables as inputs.  But even without the jitting, for example for minimization, it's now a completely functional API aswell, basically for free. So JIT and minimization is the main motivation. (I thought grads also work, that would have been better, but yep).
So there is a difference between calling the function with specific parameters and changing the default values of the function. While autodiff doesn't quite work with it (not sure why?), it's also the way to go for that.

it's a bit hacky and going against the way the interfaces are designed now (the ParametrizedFunction call expects a DataSample that has arrays as values).

Is it? To me, it looks perfectly elegant. Especially as internally, the ParametrizedFunction does the exact same thing but overrides the parameters if given: It currently doesn't allow but forces it's state. I think it would just solve, in a very elegant way, one of the largest problems with the API, namely that it isn't functional (but here I may miss details).
Since you're also working on jitting in other PRs I've seen, maybe I am really just missing details. But then, the functional API that it offers for free seems, without a downside I think, seems easy to enable?

We can also discuss this tomorrow, it's an interesting issue ;)

If not, why would it become jittable if parameters can be passed to the call method?

It passes through a "symbolic parameter", much like sympy, but care must be taken that it's not converted somewhere. Also, it would not reflect any updated state, leading to a different behavior if run with JIT vs without (i.e. the Python object won't be updated if jitted, but it will if not jitted if the parameter is set).
I think it's jittable because it's simply a function now? Hm, ParametrizedBackendFunction okay! So that's the "executable", I've been a bit confused about what to call then and what not to, I'll try that! The ParametrizedBackendFunction.function is maybe what I was "looking for"

what the effect of those internal parameters is, even if the unpacking order is swapped

actually, here, only Python is happening: yes, these are "symbolic parameters", but only the ones that survive the dict merge survive the jit, so to say

Hah, actually this touches on a larger issue :D

Sounds good, that is well aligned and I am really happy to see the extensive work on the conversion and careful backend handling, it's quite a tricky issue (so happy to make use of it!)

@redeboer feel free to close or merge, whatever you think fits best, as discussed, it's not crucial and I'll use other ways to access the function.


cannot find type definition: address.Address

2020/11/17 11:46:44 Generating wallet.Address
2020/11/17 11:46:44 ParseComment error in file api/handlers_transfer.go :cannot find type definition: address.Address

code
package wallet

import(
	"github.com/filecoin-project/go-address"  // package address
)

type AddressBalance struct {
	Addr    address.Address
	Balance types.BigInt
	Default bool
}

Hi @weaming
Can you show your swag annotations?

Do you mean
// @title title
// @version 1.0
// @contact.name API Support
// @contact.email email
// @host <IP_ADDRESS>:3127
// @BasePath /

Alireza Salary<EMAIL_ADDRESS>于2020年11月19日周四 下午7:20写道：

Hi @weaming https://github.com/weaming
Can you show your swag annotations?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/arsmn/fiber-swagger/issues/7#issuecomment-730305846,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACOMW747BRVGRWSBEGYMBYTSQT5PBANCNFSM4TYA4BZQ
.

--
From Garden.Yuen

replaced address.Address as string. closed


[s11n 6/7] Serialisation test

Description
This is a side-port to development of PR https://github.com/ARMmbed/mbedtls-restricted/pull/575 that has already been merged to baremetal.
Dependencies: based on #2764, #2766 #2785 #2788 and #2789  - see "Background" below.
This PR adds ssl_client2/ssl_server2 -tests for the session serialisation/deserialisation.
Background
This is the sixth in a series of seven PRs implementing serialization of a full SSL context (not just the session), under some restrictions.
The PRs in the series are:

r563 -> #2764 Refactor derive keys
r568 -> #2766 Make session serialisation functions public
r570 -> #2785 Make session format ABI-independent
r567 -> #2788 Add version + config check to SSL tickets
r572 -> #2789 Context serialisation: API and documentation
r575 -> #2791 Serialisation test (this PR)
r616 -> #2792 Implement context serialisation

The full series is already merged in baremetal. It needs upstreaming for the benefit of the Could team, who will be the main user, and relies on upstream releases.
Side-porting details
Side-porting was done with git cherry-pick; all commits were picked with no conflicts.
The table shows how each side-ported commit was handled:

(nothing) cherry-picking worked without conflict
"t" only trivial context-related conflicts (eg. independent additions to the same place)
"r" manual rework after cherry-picking
"R" the commit was reconstructed manually (moving code around)
"+" added in this side-port PR

resolution
original commit
commit message

t
0ea3cfe5bf2f
Add option for serialization in ssl_client/server2

d736d086184d
Serialization/deserialization in ssl_client2

654e8de16302
Rely on opt.exchanges for sending after serialization

f457293b5791
Serialize/deserialize for ssl_server2

cf1b6724c968
Use MBEDTLS_SSL_CONTEXT_SERIALIZATION flag

fa45e6005e9a
Add serialization tests to ssl-opt.sh

dcfc2a736455
Add missing slashes to tests

cc281b8a549a
ssl-opt.sh tests for serialization are currently using stub implement…

38061f4a179d
Remove mbedtls_ssl_free() and mbedtls_ssl_init() from serialization f…

5737ec97a620
Address review comments for code-style issues

f4f8ed7e82ab
Allow stub implementation of the context_save for now

bff4a91827eb
Fix spacing

b5ff6a4ced96
Add option for ssl-context re-initialization flow

8a91c0650a96
Add tests for re-init flow for context serialization

034ae84601cc
Fix compiler warnings

85c238018e03
Fix spacing

29a15c2de528
Set timer callbacks with serialization

8b2608b6c2a5
Fix style issues

Review notes
Reviewers are strongly encouraged to review commit by commit, as the final diff is unlikely to make sense. Please note that the first commits (up to "Clarify documentation of mbedtls_ssl_context_load()") are part of #2764, #2766 #2785 #2788 and #2789 and don't need to be re-reviewed here (except checking that they're indeed part of #2764 #2766 #2785 #2788 #2789).

Rebased on top of #2789

@hanno-arm please re-review

Thank you for the review @artokin, the indentation was fixed in https://github.com/ARMmbed/mbedtls/commit/8b2608b6c2a5368ff09f35e41d294fd4de592be0

Rebased without conflicts, then amended "Add option for serialization in ssl_client/server2" and fixed an issue with changed function names.

@hanno-arm @artokin please re-review

All of the serialisation PRs now have 2 approving reviews and passing CI. Thus considering all of them ready for merge.


Launches with "-high" option, leading to potential instability

Describe the bug
By default, TF2BD attempts to load TF2 with high priority. This could cause issues with resource management, and shouldn't be used for long-running processes.
To Reproduce
Open TF2 through TF2BD.
Expected behavior
N/A (Not a bug, but a potential flaw. TF2 should be able to run without high priority.)
Desktop:

OS: Windows 10
Version: <IP_ADDRESS>6

Many users are on computers that are resource constrained: 4 cores or less. In those situations, I find that running tf2 with high priority helps reduce issues with other programs (including tf2bd) taking up cpu time. That being said, I'll leave this on by default but add an option to turn it off.

I think having it off by default would probably be safer, since not many users actually understand what it does enough to make an informed decision.

Could you elaborate on what kind of issues you are experiencing? I haven't heard of problems related to this from any other users.

No issues personally, emphasis on "potential" instability.
However, to clarify: https://docs.microsoft.com/en-us/windows/win32/procthread/scheduling-priorities

Use HIGH_PRIORITY_CLASS with care. If a thread runs at the highest priority level for extended periods, other threads in the system will not get processor time. If several threads are set at high priority at the same time, the threads lose their effectiveness. The high-priority class should be reserved for threads that must respond to time-critical events.

It's best to only use it if you need it for a specific purpose, for a short period of time.

It's true this is what the documentation says, however:

TF2 is not going to occupy 100% of your CPU for extended periods of time, or at all if you have more than ~4 cores. This is primarily what that note in the documentation is about, where long-running, entirely-cpu-bound tasks can completely starve other applications of cycles. TF2 and most other games are a highly intermittent load compared to that.
I have found that there are lots of background services, particularly from third parties, that like to run with above normal priorities. The priority boosting that windows applies to focused applications is not always sufficient to overcome this.

Fair! I can see the logic in that :P

Such as game input, logic, and rendering ;)

Later in the documentation, it says: "The important point is that a high-priority thread should execute for a brief time, and only when it has time-critical work to perform."

TF2 is not going to occupy 100% of your CPU for extended periods of time, or at all if you have more than ~4 cores. This is primarily what that note in the documentation is about, where long-running, entirely-cpu-bound tasks can completely starve other applications of cycles. TF2 and most other games are a highly intermittent load compared to that.

You also say:

Many users are on computers that are resource constrained: 4 cores or less. In those situations, I find that running tf2 with high priority helps reduce issues with other programs (including tf2bd) taking up cpu time.

Could you clarify this information about <4 and >4 cores?

Also, I would argue that -high is out of the scope of TF2 Bot Detector. You could add an option for it, but realistically, this launch option is up for the user to add for their launch options in Steam. There's lots of arguably helpful launch options which improve the experience or performance, but obviously TF2 Bot Detector isn't trying to add all of those too.

Also, I would argue that -high is out of the scope of TF2 Bot Detector. You could add an option for it, but realistically, this launch option is up for the user to add for their launch options in Steam. There's lots of arguably helpful launch options which improve the experience or performance, but obviously TF2 Bot Detector isn't trying to add all of those too.

I would tend to agree with what mastercoms is saying here, the -high launch option is entirely user dependent and unrelated to TF2BD. In my opinion there is not a solid enough reason to justify it being included by default, even as a toggle. It's just another option that any TF2 player can choose to add, similarly to changing resolutions, novid, etc.
TL;DR it's not mandatory for TF2BD to run and therefore should not be included until there is strong enough evidence/reason to dispute the performance claims

It was added specifically in response to users on low-end CPUs complaining of reduced FPS while running tf2bd.

I bet why don't they tried to lower the priority for the TF2BD itself

Yeah, I would think that setting the priority of the tool lower would be a better solution.


docs: Include link to dnscrypt-proxy blocklist tool

Copy-pasted the tool description from the dnscrypt-proxy page.
Fixes: #1830
@StevenBlack @dnmTX PTAL . I think that should suffice, but let me know. Thanks!

Thank you Lokesh!  Merging.


Add TCP as mode of communication

i think we don't need it right now. Let's make other things work first.

Yeah it's a low prio issue for now

Have been implemented.


Event subscription broken when using Marathon version >=1.5.0

Hello,
I don't know if anyone is aware of this but I would like to let you know that I figured Bamboo (all recent releases I've checked (>=2.14) and even master branch) doesn't work with versions of Marathon superior to 1.5.0 since the endpoint /v2/eventSubscriptions in Marathon API has been deprecated and removed from Marathon as stated in this changelog: https://github.com/mesosphere/marathon/blob/v1.5.0/changelog.md.
Those events must now be read from the stream of events coming from /v2/events.

In the current implementation, the setup can only be one or another. By setting "UseEventStream", subscription won't be registered.
"UseEventStream": true

Thanks for the heads up, I will add to the documentation.

I've updated the documentation, closing the issue now. If you have any suggested documentation improvements, feel free to make a PR.


split up protein prep and use SEQRES to make mutations

Description
Enable preparing the receptors as an independent step from the whole 'hallucinate fragalysis' pipeline.
Todos
Notable points that this PR has either accomplished or will accomplish.

[ ] implement everything described in this issue #47
[ ] track the new changes highlighted here #46

Questions
Status

[ ] Ready to go

Here was the traceback for the kinoml test that didn't work:
OEProteinStructureFeaturizer:   0%|          | 0/1 [00:00<?, ?it/s]DPI: 0.23, RFree: 0.27, Resolution: 2.34
Processing BU # 1 with title: 3C-LIKE PROTEINASE, chains AB
Found unresolved N-terminal with 1 residues before GLY 2   A 1  , with sequence S
Found 2 residue gap between PRO 75   A 1   and LEU 78   A 1  , with sequence AN
Found 2 residue gap between LEU 170   A 1   and GLY 173   A 1  , with sequence AN
Found unresolved C-terminal with 6 residues after ILE 300   A 1  , with sequence MGVVMQ
Found unresolved N-terminal with 1 residues before GLY 2   B 2  , with sequence S
Found 2 residue gap between ALA 74   B 2   and ASN 77   B 2  , with sequence PA
Found unresolved C-terminal with 5 residues after MET 301   B 2  , with sequence GVVMQ
Warning: There was a problem building some missing pieces, built as much as was possible
   Falling back to charging protein with OEMMFF94Charges
Traceback (most recent call last):
  File "/Users/alexpayne/Scientific_Projects/covid-moonshot-ml/scripts/test-protein-prep.py", line 123, in <module>
    main()
  File "/Users/alexpayne/Scientific_Projects/covid-moonshot-ml/scripts/test-protein-prep.py", line 119, in main
    featurizer.featurize(systems)
  File "/Users/alexpayne/opt/anaconda3/envs/mers-docking2/lib/python3.8/site-packages/kinoml/features/core.py", line 63, in featurize
    features = self._featurize(systems)
  File "/Users/alexpayne/opt/anaconda3/envs/mers-docking2/lib/python3.8/site-packages/kinoml/features/core.py", line 309, in _featurize
    features = [self._featurize_one(s) for s in tqdm(systems, desc=self.name)]
  File "/Users/alexpayne/opt/anaconda3/envs/mers-docking2/lib/python3.8/site-packages/kinoml/features/core.py", line 309, in <listcomp>
    features = [self._featurize_one(s) for s in tqdm(systems, desc=self.name)]
  File "/Users/alexpayne/opt/anaconda3/envs/mers-docking2/lib/python3.8/site-packages/kinoml/features/protein.py", line 226, in _featurize_one
    protein = self._process_protein(
  File "/Users/alexpayne/opt/anaconda3/envs/mers-docking2/lib/python3.8/site-packages/kinoml/features/core.py", line 1124, in _process_protein
    protein_structure = apply_mutations(protein_structure, amino_acid_sequence)
  File "/Users/alexpayne/opt/anaconda3/envs/mers-docking2/lib/python3.8/site-packages/kinoml/modeling/OEModeling.py", line 1423, in apply_mutations
    if oespruce.OEMutateResidue(
  File "/Users/alexpayne/opt/anaconda3/envs/mers-docking2/lib/python3.8/site-packages/openeye/oespruce.py", line 992, in OEMutateResidue
    return _oespruce.OEMutateResidue(*args)
TypeError: in method 'OEMutateResidue', argument 3 of type 'std::string const'
OEProteinStructureFeaturizer:   0%|          | 0/1 [00:11<?, ?it/s]

that's strange... it looks like there's no res_name for that residue either, so maybe it's some kind of ghost residue? I added a new implementation of the function that I think is more direct (using OEMutateResidues to mutate them all at once rather than doing each mutation individually). can you lmk if you still get the same error with this implementation?

Running! I was hoping to avoid mutating all the residues since its much slower to do it that way. The point was to find only the residues where the res_names are different. It looks like it worked in theory although we know that the sequences aren't the same length for each one so that will need to be adjusted!

sorry, I should've been clearer about that, it doesn't mutate every single residue, just the ones that are different like you said (that's what the if statement in the mut_map dict comprehension does). also, the only length requirement is that the SEQRES entry be the same length as the number of residues in the protein, which I think should be the case but I could be wrong about that

But the proteins have different residue lengths (i.e. 7DR8 is missing the initial Serine, and some of the proteins have a series of histidines at the n-terminus)
also, I think it also fails if we keep waters!
Being able to connect the residue number to the SEQRES we want to use would be nice

ughhhhh also if there are missing sequences (i.e. in the loops) it won't skip them intelligently:

ah yeah those are definitely issues. I have an idea though, hopefully will commit in a few minutes

ah yeah those are definitely issues. I have an idea though, hopefully will commit in a few minutes

sorry just saw this, my most recent commit works

I think your new approach looks good. it will fail though in the case that chain B has a different sequence than chain A, is this something that can happen?

it will fail though I think in the case that chain B has a different sequence than chain A, is this something that can happen?

Which chain A and chain B are you referring to? the one in the starting molecule or the one in the sequence that we want?

I meant in the SEQRES, but since it's a homodimer I guess that shouldn't really happen


Switch from logging_util.py to rich package for log output and progress bars

I'm currently writing an article about logging in Python. As a part of that, I look at other projects and how logging is done there. I've seen logging_util.py and was wondering why this project does not use the built-in logging module.
Could somebody share some thoughts around logging? Why is it done like that in this project? Do you consider this a best practice?

It's not a best practice, I just tend to write my own logging utils because I like very fine-grained control over how colored log output appears and I find the logging builtin library to be somewhat clunky.

Thank you for answering!
If it's not a best practice, what would you consider a best practice for logging?
Have you given 3rd party logging libraries a try (structlog, loguru, pysnooper, or something else)? If so, what do you think of them?

I find the logging builtin library to be somewhat clunky

Could you explain that a bit more? What exactly is it that you don't like?
I think I have heard about loguru at Python bytes and they mentioned that it deals pretty well with colored output (e.g. over various consoles / terminals / within PyCharm)

Those libraries would all be great for a server, e.g. archivebox server, but the output is far too verbose/hard-to-tune for a one-shot cli command like archivebox add, archivebox version, etc.
Because I sometimes want timestamps, I sometimes want color, I sometimes want structured output sections, but not always, I it's easier for me to just hand code it than use a logger that imposes those things all the time or never.
Take for example this output from archivebox add:

There are multiple tiers of indentation that are context-dependent, multiple colors for different types of notifications that are tuned for UX, not for strict internal consistency with any particular "log level" e.g. DEBUG/INFO/etc. (which a library would enforce). I also have multiple colors on a single line to highlight important parts of the line, something not any of the tools let you do easily.
I also dislike having to import/declare a logger at the top of every file, something that neither matches with my mental model of logging, nor is enforced by any linter, so it's easy to forget and cause subtle logging errors in certain environments.

I've decided to re-open this because I found rich: https://github.com/Textualize/rich
It's an amazing package and it provides everything we need out-of-the-box! including:

scrolling partial-height livepanes: https://rich.readthedocs.io/en/stable/live.html
progress with known and unknown totals: https://rich.readthedocs.io/en/stable/progress.html
pretty traceback printing with locals: https://rich.readthedocs.io/en/stable/traceback.html
filesystem tree display: https://rich.readthedocs.io/en/stable/tree.html
generic syntax highlighting: https://rich.readthedocs.io/en/stable/syntax.html
markdown rendering to console: https://rich.readthedocs.io/en/stable/markdown.html
full layouts with sub-panels: https://rich.readthedocs.io/en/stable/layout.html
integration with python/django logging system: https://rich.readthedocs.io/en/stable/logging.html
pretty printing for archivebox shell: https://rich.readthedocs.io/en/stable/pretty.html
tabular data display for archivebox list: https://rich.readthedocs.io/en/stable/tables.html


Create crawler for CVS

Not available yet but will be able to begin work once it is.
https://www.cvs.com/immunizations/covid-19-vaccine#statetool

Waiting for CVS to add Texas.

Or any other state. I'm unable to find any locations at all.
https://www.cvs.com/vaccine/intake/store/cvd-store-select/first-dose-select

Created and hosted by S


⚠ Fortnite has degraded performance

In ddb2d02, Fortnite (https://fortnite.com) experienced degraded performance:

HTTP code: 200
Response time: 1657 ms

Resolved: Fortnite performance has improved in 89e634f.


Question: Setting Serialized Mode in PCL

Hi, in non PCL version of SQLite.Net I was able to do this for Android and iOS:
        SQLite.SQLite3.Shutdown();
        SQLite.SQLite3.Config(SQLite.SQLite3.ConfigOption.Serialized);
        SQLite.SQLite3.Initialize();

and this would stop the threading error.
I cannot see how to set serailize mode with the PCL. Can you explain please.

Is this still supported?


Add simple low latency threadpool

Updated to rust 1.80
Updated azure pipeline
Modified code to allow for static lifetime objects to be passed to worker thread. This means that we don't need scoped threads which cannot be implemented without unsafe code. The main change here is to pass cloned objects which keep their lifetime vs references.

OK for me.


Date/time is wrong (UTC instead of local time)

I read https://github.com/binwiederhier/ntfy/pull/307 and https://github.com/binwiederhier/ntfy/issues/700 but even after being sure I am exporting the correct TZ variable (America/New_York in my case) and bind mounting /etc/localtime from the docker host (-v /etc/localtime:/etc/localtime:ro) I am still getting this...
From my ntfy container (2.7.0 pulled from Docker hub)
/ # date
Sat Oct 21 19:21:44 UTC 2023
/ # echo $TZ
America/New_York

From the docker host
root@nas:~# date
Sat Oct 21 03:21:46 PM EDT 2023

I think this is why my scheduled notifications aren't working (?). Is this wrong? Or is date from the container just showing the time in UTC? (MM:SS is correct)
Can anyone help?

Hmm, date -u from the docker host returns
root@nas:~# date -u
Sat Oct 21 19:28:21 UTC 2023

So maybe this isn't really a problem? If not, then I need to figure out why scheduled notifications aren't working...

Based in New Zealand so currently time +13 GMT. Scheduling works fine if delay entered in Unix format but any time entered as numerals passes into the following day so no simple way to schedule say for 17.00 today. Using "today" makes no difference. I am sending HTTP from android.

Thinking about it, this actually makes sense. Unless a header is passed by the client indicating the client time zone, there's really no way the ntfy server could know what time zone they are in to set the schedule accordingly.

The workaround is to offset the time in the APP but the Eastern Standard Time HTTP example in the NTFY documentation does not fit in with this.

This is a dup of https://github.com/binwiederhier/ntfy/pull/307 and https://github.com/binwiederhier/ntfy/issues/894. It'll be fixed in the next release.


Usage of cast when From is available

Using From (or into()) is easier to read than using casts because it stops devs having to wonder if an data being lost.
We have a few places where we use casts to cast u8 to usize
            let log1 = LOG[self.0 as usize];
            let log2 = LOG[other.0 as usize];

Could be written as:
            let log1 = LOG[usize::from(self.0)];
            let log2 = LOG[usize::from(other.0)];

Interesting. TIL that usize implements From<u8> and From<u16>. (But not From from any other numeric type, and I don't believe Into for any numeric types).


Continuserv: Reduce number of watches

rather than trying to watch half the filesystem, be a bit more conservative in
what we put watches on. This means that we don't end up dying with "No space on
device" (thanks for that, Linux.)

Assigning to @NegativeMjark as he is probably most likely to pick up on the Go style points at :)

LGTM modulo comment with my limited Go knowledge

LGTM


Test Fake TLS proxy

Hi,
I want to check if a running proxy is available and it's not banned??
Is it possible to test fake-TLS proxy in Nodejs??

Hi,
I want to check if a running proxy is available and it's not banned??
Is it possible to test fake-TLS proxy in Nodejs??

Of course, this is possible; but this repository is non intended for the checking of proxy servers. Unfortunately I am not interested in sharing the code here, because it may be abused by auto-filtering systems especially in Iran. But if you want to develop your own code, you can refer to telegram core documentation, 'PING' command.
If you are using this repository code, you can simply load http report. It may help.

Hi,
I want to check if a running proxy is available and it's not banned??
Is it possible to test fake-TLS proxy in Nodejs??

Of course, this is possible; but this repository is non intended for the checking of proxy servers. Unfortunately I am not interested in sharing the code here, because it may be abused by auto-filtering systems especially in Iran. But if you want to develop your own code, you can refer to telegram core documentation, 'PING' command.
If you are using this repository code, you can simply load http report. It may help.

Can we discuss on telegram, @NimaPaymard


ToCode Solution: תרגול תחביר

Hi and welcome to the exercises.
I am waiting for all the exercises to be submitted, but please keep the original comments at the top. They are the description of the exercise and help me making sure I am checking the correct exercise.
Please also look at the video: https://www.tocode.co.il/bundles/python/lessons/syntax-lab and run the tests on your own machine before submitting the solutions.

Thanks for submitting all the exercises.
Some of the automatic tests have failed. Please make sure those pass before we continue.
Please note the "All checks have failed" and the link to "Details" under it. That leads to results of the system that checks your submission automatically against the spec. This indicates there were some exercises that failed.
You can run the spec on your computer by cd into the directory where your Python files are e.g.
cd \Users\itelbaz\PycharmProhects\untitled and then run the tests:
python spec.py
and you can run it for the individual files using
python spec.py TestEx1
python spec.py TestEx2
...

The following video provides more detailed explanation how to run the tests
https://www.tocode.co.il/bundles/python/lessons/syntax-lab

?
On Mon, Dec 19, 2016 at 11:18 AM, Gabor Szabo<EMAIL_ADDRESS>wrote:

Closed #31 https://github.com/tocodeil/python-course-examples/pull/31.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/tocodeil/python-course-examples/pull/31#event-898317099,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AXJ9X50XObJrC4NRhh0fsTx25Y9LVs5jks5rJkvogaJpZM4LAslH
.


docs: Typo for Daisy UI

Typo in the docs
https://gyazo.com/c3c036767073471b84fb6769778ff1d3
What is it?

[ ] Feature / enhancement
[ ] Bug
[x] Docs / tests

Description
Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change.
Use cases and why

One use case

Another use case

Screenshots/Demo

Checklist:

[ ] My code follows the developer guidelines of this project
[ ] I have performed a self-review of my own code
[ ] I have made corresponding changes to the documentation
[ ] Added new tests to cover the fix / functionality

I have read the CLA Document and I hereby sign the CLA

@all-contributors please add @thejackshelton  for code, doc


The new oozie coordinator doesn't work

http://gethue.com/hadoop-tutorials-ii-3-schedule-hive-queries-with/
I was following the old tutorial and the UI changed a lot.
date -- input path, parameter, output path? I'm not sure which one to choose. After trying a few values. It popped up the error.
The frequency of the workflow parameter "date" cannot be guessed from the frequency of the coordinator. It so needs to be specified manually.
None

How often do you want to run it? Try to put every day

I was trying to run it every day but I don't know where I can put this frequency. The new oozie dashboard is no longer consistent with the tutorial. When I put 1 there, it kept giving me the error below:
The frequency of the workflow parameter "date" cannot be guessed from the frequency of the coordinator. It so needs to be specified manually.
I'm wondering can we update our tutorial so we can have a step by step learning for newbees?
Thanks a lot!


Not working with @feathersjs 4.3.10

Steps to reproduce
feathers-client.js
import feathers from '@feathersjs/feathers'
import socketio from '@feathersjs/socketio-client'
import auth from '@feathersjs/authentication-client'
import io from 'socket.io-client'
import { iff, discard } from 'feathers-hooks-common'
import feathersVuex from 'feathers-vuex'
import { CookieStorage } from 'cookie-storage'

const storage = new CookieStorage();
const socket = io('http://localhost:3000', {transports: ['websocket']})

const feathersClient = feathers()
  .configure(socketio(socket))
  .configure(auth({ storage }));

export default feathersClient

// Setting up feathers-vuex
const { makeServicePlugin, makeAuthPlugin, BaseModel, models } = feathersVuex(
  feathersClient,
  {
    serverAlias: 'api', // optional for working with multiple APIs (this is the default value)
    idField: 'id', // Must match the id field in your database table/collection
    whitelist: ['$regex', '$options']
  }
)

export { makeAuthPlugin, makeServicePlugin, BaseModel, models }

store/index.js
import feathersClient from '../feathers-client';
import feathersVuex, { initAuth } from 'feathers-vuex';

const { makeServicePlugin, makeAuthPlugin } = feathersVuex(feathersClient, { idField: 'id' });

export const state = () => ({});
export const mutations = {};

export const actions = {
  nuxtServerInit({ commit, dispatch }, { req }) {
    return initAuth({
      commit,
      dispatch,
      req,
      moduleName: 'auth',
      cookieName: 'feathers-jwt'
    })
  }
};

export const plugins = [
  makeAuthPlugin({
    userService: 'users'
  })
];

Expected behavior
It should work
Actual behavior
"export 'default' (imported as 'dbCommons') was not found in '@feathersjs/adapter-commons'

Output from browser upon reload is
TypeError
Cannot destructure property `filterQuery` of 'undefined' or 'null'.

import { _ } from '@feathersjs/commons'
import dbCommons from '@feathersjs/adapter-commons'
import { globalModels as models } from './global-models'
import _get from 'lodash/get'
import _omit from 'lodash/omit'
const { filterQuery, sorter, select } = dbCommons
const FILTERS = ['$sort', '$limit', '$skip', '$select']
const OPERATORS = ['$in', '$nin', '$lt', '$lte', '$gt', '$gte', '$ne', '$or']
const additionalOperators = ['$elemMatch']
const defaultOps = FILTERS.concat(OPERATORS).concat(additionalOperators)
export default function makeServiceGetters() {

System configuration
Tell us about the applicable parts of your setup.
Module versions (especially the part that's not working):
    "@feathersjs/authentication": "^4.3.10",
    "@feathersjs/authentication-client": "^4.3.10",
    "@feathersjs/authentication-local": "^4.3.10",
    "@feathersjs/authentication-oauth": "^4.3.10",
    "@feathersjs/configuration": "^4.3.10",
    "@feathersjs/errors": "^4.3.10",
    "@feathersjs/express": "^4.3.10",
    "@feathersjs/feathers": "^4.3.10",
    "@feathersjs/socketio": "^4.3.10",
    "@feathersjs/socketio-client": "^4.3.10",
    "@feathersjs/transport-commons": "^4.3.10",
    "@feathersjs/adapter-commons": "^4.3.10",

NodeJS version:
v11.4.0
Operating System:
MacOSX
Browser Version:
Chrome
React Native Version:
Module Loader:
NUXT

This looks like an error that was fixed a few versions back.  Could you npm i feathers-vuex@latest or yarn add feathers-vuex@latest and try again?

I'm currently using "feathers-vuex": "^2.2.3" - I saw this issue #247 but as it's old and im on the latest version - I assumed its something new. :/

Hmm... Everything looks fine in the feathers-vuex node_modules folder. The adapter-commons package definitely has an exported object, so there's not really a good reason for it to be undefined in your setup:

Try npm cache clean or yarn cache clean, maybe?

Ah.  Nope.  Something's definitely off in the repo, this is the latest code on Github: https://github.com/feathersjs/feathers/blob/master/packages/adapter-commons/src/index.ts#L4
This is for me to fix.

nah - same things.
Could this not maybe be causing some issues?
https://github.com/feathersjs-ecosystem/feathers-vuex/blob/fbde9705ce6cb09d243b7b9b65d1982df9c70644/package.json#L101

Ah i just saw your comment now - awesome man! thanks.

Ok.  Try installing @latest again and let me know how it goes.

I've updated all of the dependencies and enabled Greenkeeper, so this should now be resolved.  Feel free to reopen if you find there's still an issue.

Sorted, thanks @marshallswain !