text:
Initial run at draft/2019-04 tests, complete with output

This is essentially the draft-07 test suite with the addition of the expected output.  I generated the output as I ran the test suite in Manatee.Json.
It's missing a few things:

Some of the optional tests don't pass (for various reasons), so these aren't included.  I can look at adding them manually, but it would be a serious undertaking to make all of them pass in .Net (e.g. zeroTerminatedFloats: "a float is not an integer even without fractional part" just isn't going to happen since I don't save the string representation of numeric values, so I can't test for integer vs fraction-less float).
I didn't create any tests for the keywords, formats, etc. that are new as of this draft.
There should be tests that validate annotation collection.  Maybe these should be optional since annotation collection is not required.

Resolves #247

@gregsdennis thanks!
This is obviously too big to review as-is, so still thinking about how to do that, but at least the tests are failing because the schema for tests themselves has now changed to add the output. I suppose the cheap way to fix that is to remove the additionalProperties, which would evade tackling #223 or having per-draft test suite schemas.

I think (maybe) looking at some of the larger, more deeply nested ones then assuming the others follow suit would be okay .  Other than that, ¯_(ツ)_/¯

I think another thing after I sent that is (assuming the new draft is fully backwards compatible) first merging a complete copy over, such that what's left is at least purely the diff from what's already here.
I'm going to try that later, unless you mind giving that a shot perchance and beat me to it.

@Julian off the top of my head the main incompatibilities are is that dependencies was split into dependentSchemas and dependentRequired, and that definitions was renamed $defs
However, it's still entirely valid to use definitions (because it's a placeholder location and doesn't actually do anything), and dependencies effectively becomes an extension keyword that people can support for backwards compatibility if they want to.  Both of these old keywords are still present in the schema meta-schema, they're just not present in the individual vocabulary meta-schemas.
Anyway, those are pretty simple changes so I think copy, commit, and then PR the copies would make sense.

Sure. If you'd like to split the migration of draft 7 -> 8 from the addition of the output, that's fine.  Just let me know. It's simple enough to generate the output.
I didn't think about the keyword differences.  It's probably a good idea to migrate the tests first.

OK, pushed a straight up copy (without yet handling the renames) to master directly, and pushed a rebased version of this @gregsdennis to the output branch, which at least looks slightly more manageable.
Will now need to handle reviewing that, and then handling the changes @handrews mentioned (thanks!)

I'll update this when we're happy that the new draft suite is ready.

Github just closed this for some reason. And the reopen button is gone too.
Thanks GitHub :/

GH merged the changes! ???!!

Github closed the associated issue (#247) because the first post says "Resolves #NUMBER".
The "Resolves' word is underlined.
I'm assuming you're referencing the issue as opposed to the PR, which cannot be re-opened once merged.

No, we can't figure out why this was merged. It's understandable that the issue closed when this merged, but why did this merge?

Just to confirm @Julian you did NOT merge this PR yourself?

If so, I'll contact github =]

You guys seem more interested in the mystery than I was :D
I merged the other PR (#267).
But, now looking, all that it looks like happened here is that @gregsdennis it looks like you put the commits from #265 on your master branch, then put commits after that that essentially reverted the ones adding output (e.g. 1ce104fb738fba63e7f111b1a608f7d2fa114175), then branched off of that to create the defs branch.
So when I merged that, the commits adding output were in fact merged (and then reverted by later commits).

It's still dumb IMHO by the way that GitHub won't let me reopen the PR, as a marker (as if it were an issue), but whatever.

Given you can close manually, I would guess you CAN open manually, but only IF the code hasn't been merged.

Oh. Oops.

Hard-reset the branch if you have to, that's simpler than any other option.

I've already opened a new PR.

authors: Julian Relequestual awwright gregsdennis handrews

repo: json-schema-org/JSON-Schema-Test-Suite


text:
Reset graphics cannot send 0 monitors, fixes Microsoft App Store clients with avc:420 H264 mode

When testing this with the Microsoft Remote Desktop (app store clients) this fixes the ability of the graphics transmission to work at all.
It wasn't an error in the capabilities of the clients, it's that there is a difference between the protocol and the implementation that Microsoft has released in their remote desktop clients.
This may not be the "proper" fix, but it prevents the clients from crashing and having a non-functional black screen.
We should file a bug with Microsoft on this, as well.

looks good to me

source: gharchive/pull-request

license_type: permissive

license_source: bigquery


text:
Figure out why at least parts of the Checker Framework build apparently run twice

For example, in https://github.com/jspecify/nullness-checker-for-checker-framework/actions/runs/3185722197/jobs/5195599320 (which comes after https://github.com/jspecify/nullness-checker-for-checker-framework/pull/39), I see the following twice:
running "./gradlew assemble" for checker-framework

That apparently includes actual work being done twice for (for example):
> Task :checker-qual-android:javadoc

I think it's because the Checker Framework build runs a shell script that reentrantly runs the build. I'd love to get rid of that shell script and make everything Gradle.

source: gharchive/issue

authors: cpovirk netdpb


text:
IE 9 not able to run test - Script error in benchmark-47.js

When I open http://jsperf.com/sql-js-vs-alasql-js/10 with chrome I get a big red box stating that
Uncaught TypeError: Cannot read property 'name' of undefined.

message: Uncaught TypeError: Cannot read property 'name' of undefined
fileName: http://jsperf.com/benchmark-47.js
lineNumber: 21

This test will run when I click Run tests
Using IE9 I get
Script error.
•message: Script error
•fileName: http://kripken.github.io/sql.js/js/sql.js
•lineNumber: 0

in a red box. Clicking Run tests will give a new error but the tests will not run

Closing in favor of #64.

:+1:

authors: mathiasbynens mathiasrw

license: MIT

license_source: github-api


text:
staticDeps and dynamicDeps as full graph

Currently staticDeps and dynamicDeps are just arrays of modules, without further graph information.
It could be useful to actually expose the entire graph for these in the generation to be able to lookup arbitrary dependency information.
We currently have a getAnalysis method which returns the analysis per module. It could be useful to effectively get the whole graph in one:
generator.getGraph() = () => ({
  [url: string]: {
      staticDeps: { specifier: string }[],
      dynamicDeps: { specifier: string }[]
  }
})

The current getAnalysis could be extended to support this form relatively easily.

The current primitive we have with getAnalysis is enough I think to do this, closing for now.

repo: jspm/generator


text:
Enable header selection

Today, If we want to selct, copy data from table and paste it to excel we can update the property includeHeadersOnCopy that will automatically copy the header when copying couple of cells. So either with header or without.
Can we enable header selection via mouse so the header will be included in the selection rectangle?

Currently, you can click on header for select full column. After on event onbeforecopy you can defined, if column is full selected you add header
The better solution : use contextmenu on header and add item copy with header et create your own function copy

authors: GBonnaire assadi

repo: jspreadsheet/ce


text:
T7828 - arrows and rebindable syntax

General TODO:

[ ] implement new desugaring
[ ] implement typechecking
[ ] think about desugaring if_then_else_
[ ] interaction of arrows and TH is unknown. Need to check.

Short-term TODO:

[ ] desugaring of LastStmtA
[ ] try to fix typechecking

I'm not working this any more. Marking as wontfix

repo: jstolarek/ghc


text:
fix(version): update @angular/core to 4.4.3

generated by UpdateBot

UpdateBot commands:
updatebot push /workspace/java/updatebot/updatebot-core/target/test-data/io/fabric8/updatebot/PushSourceDependenciesTest/github/jstrachan-testing/ngx-base

repo: jstrachan-testing/ngx-widgets


text:
Finalizar textos da home.

HTML + CSS.

Finalizado os textos "sobre o projeto" e "diferenciais" da home.

repo: jthanlopes/SysGAP

license: mit


text:
UI/UX - differentiate closed restaurants from open ones

Some way to to differentiate already closed restaurants would be useful.  Hiding them or just rendering using a different color scheme.  In mobile view perhaps straight up hiding/collapsing them or sorting differently (with closed ones at the end of the list)

Good idea, but a bit difficult to implement at the moment. The opening times do not have standard syntax, so some kind of parsing should be done. F.ex. Amica Central Station has some additional information in it's closing time field. Also, all restaurants don't have opening times at all.
This is definitely a nice-to-have feature. This could be done at the same time as #9, since normalizing opening times is needed to make this function.
This can be also extended to differentiate restaurants which menus couldn't be shown for some reason (menu not found for example)

authors: jtiala shinr

repo: jtiala/ruoka


text:
🛑 Private website is down

In 491dda5, Private website ($PRIVATE_WEBSITE) was down:

HTTP code: 500
Response time: 77 ms

Resolved: Private website is back up in c451ce9 after 21 minutes.

repo: jtsimoes/upptime


text:
HHVM package fails on debian 7

The following packages have unmet dependencies:
 hhvm : Depends: libstdc++6 (>= 4.9.0) but 4.7.2-5 is to be installed
        Depends: gcc-4.9-base but it is not installable

I wish I could send you a PR, but haven't found why it requires gcc 4.9 for the package, and no idea how to fix it.

Just tried again the package install on debian 7 and it now works. They probably fixed it in 3.4.1 or 3.4.2.

awesome. Thanks a lot!

authors: jubianchi pelletiermaxime

repo: jubianchi/hhvm-cookbook


text:
Does it work on MAC?

Hey,
I was searching for a project like this and I want to try it out. I'm on a mac so some things are like linux. Do you know if it does not work?
If it works I can help with some JS UX development.

I'm not sure. I suggest you try to run https://github.com/mart1nro/joycontrol first and if that works then this should too. I'd be happy to know!

It does not work easily if it really works. Too much workarounds for Bluetooth configuration... I borrowed my fathers Raspberry and worked 1st try.

authors: ebisbe juharris

repo: juharris/switch-remoteplay


text:
Figure 6: Visualization of learned attentions Φp and Φa for l ∈ {3, 4, 8}.

Hello, can the attention visualization code of Figure 6 in the paper be provided? Thank you so much.

Sorry, I tried that, adding the visualization during testing only gets figure 4（Figure 4: Learned attentions Φp of PerViT-T）.


text:
Unknown error 512 on try to get lock when graceful upgrade.

What happened:
In terminal 1:
root@bench-01:~/juicefs#  ./juicefs mount -d sqlite3://test.db /tmp/jfs
root@bench-01:~/juicefs# echo abc | tee /tmp/jfs/test
root@bench-01:~/juicefs# flock -x /tmp/jfs/test -c cat

In terminal 2:
root@bench-01:~/juicefs# flock -s  /tmp/jfs/test -c "echo abc"
In terminal 3:
root@bench-01:~/juicefs#  ./juicefs mount -d sqlite3://test.db /tmp/jfs
Terminal 2 will report flock: /tmp/jfs/test: Unknown error 512 after graceful upgrade in terminal 3.
root@bench-01:~/juicefs# flock -s  /tmp/jfs/test -c "echo abc"
flock: /tmp/jfs/test: Unknown error 512

What you expected to happen:
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know?
Environment:

JuiceFS version (use juicefs --version) or Hadoop Java SDK version:
Cloud provider or hardware configuration running JuiceFS:
OS (e.g cat /etc/os-release):
Kernel (e.g. uname -a):
Object storage (cloud provider and region, or self maintained):
Metadata engine info (version, cloud provider managed or self maintained):
Network connectivity (JuiceFS to metadata engine, JuiceFS to object storage):
Others:

This is the expected behavior.

$ root@dev1  /tmp/test1  strace flock -x afile -c "echo 123"
execve("/usr/bin/flock", ["flock", "-x", "afile", "-c", "echo 123"], 0x7ffc35815890 /* 31 vars */) = 0
brk(NULL)                               = 0x55558ffad000
arch_prctl(0x3001 /* ARCH_??? */, 0x7ffdeaf548b0) = -1 EINVAL (Invalid argument)
mmap(NULL, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x7fd27c4aa000
access("/etc/ld.so.preload", R_OK)      = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/etc/ld.so.cache", O_RDONLY|O_CLOEXEC) = 3
newfstatat(3, "", {st_mode=S_IFREG|0644, st_size=22935, ...}, AT_EMPTY_PATH) = 0
mmap(NULL, 22935, PROT_READ, MAP_PRIVATE, 3, 0) = 0x7fd27c4a4000
close(3)                                = 0
openat(AT_FDCWD, "/lib/x86_64-linux-gnu/libc.so.6", O_RDONLY|O_CLOEXEC) = 3
read(3, "\177ELF\2\1\1\3\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0P\237\2\0\0\0\0\0"..., 832) = 832
pread64(3, "\6\0\0\0\4\0\0\0@\0\0\0\0\0\0\0@\0\0\0\0\0\0\0@\0\0\0\0\0\0\0"..., 784, 64) = 784
pread64(3, "\4\0\0\0 \0\0\0\5\0\0\0GNU\0\2\0\0\300\4\0\0\0\3\0\0\0\0\0\0\0"..., 48, 848) = 48
pread64(3, "\4\0\0\0\24\0\0\0\3\0\0\0GNU\0\302\211\332Pq\2439\235\350\223\322\257\201\326\243\f"..., 68, 896) = 68
newfstatat(3, "", {st_mode=S_IFREG|0755, st_size=2220400, ...}, AT_EMPTY_PATH) = 0
pread64(3, "\6\0\0\0\4\0\0\0@\0\0\0\0\0\0\0@\0\0\0\0\0\0\0@\0\0\0\0\0\0\0"..., 784, 64) = 784
mmap(NULL, 2264656, PROT_READ, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0x7fd27c27b000
mprotect(0x7fd27c2a3000, 2023424, PROT_NONE) = 0
mmap(0x7fd27c2a3000, 1658880, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x28000) = 0x7fd27c2a3000
mmap(0x7fd27c438000, 360448, PROT_READ, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x1bd000) = 0x7fd27c438000
mmap(0x7fd27c491000, 24576, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x215000) = 0x7fd27c491000
mmap(0x7fd27c497000, 52816, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x7fd27c497000
close(3)                                = 0
mmap(NULL, 12288, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x7fd27c278000
arch_prctl(ARCH_SET_FS, 0x7fd27c278740) = 0
set_tid_address(0x7fd27c278a10)         = 270271
set_robust_list(0x7fd27c278a20, 24)     = 0
rseq(0x7fd27c2790e0, 0x20, 0, 0x53053053) = 0
mprotect(0x7fd27c491000, 16384, PROT_READ) = 0
mprotect(0x55558e77c000, 4096, PROT_READ) = 0
mprotect(0x7fd27c4e4000, 8192, PROT_READ) = 0
prlimit64(0, RLIMIT_STACK, NULL, {rlim_cur=8192*1024, rlim_max=RLIM64_INFINITY}) = 0
munmap(0x7fd27c4a4000, 22935)           = 0
getrandom("\xd5\xfe\xc3\xbe\x9b\x99\x38\x5c", 8, GRND_NONBLOCK) = 8
brk(NULL)                               = 0x55558ffad000
brk(0x55558ffce000)                     = 0x55558ffce000
openat(AT_FDCWD, "/usr/lib/locale/locale-archive", O_RDONLY|O_CLOEXEC) = 3
newfstatat(3, "", {st_mode=S_IFREG|0644, st_size=3048928, ...}, AT_EMPTY_PATH) = 0
mmap(NULL, 3048928, PROT_READ, MAP_PRIVATE, 3, 0) = 0x7fd27bf8f000
close(3)                                = 0
openat(AT_FDCWD, "afile", O_RDONLY|O_CREAT|O_NOCTTY, 0666) = 3
flock(3, LOCK_EX

)                       = ? ERESTARTSYS (To be restarted if SA_RESTART is set)
write(2, "flock: ", 7flock: )                  = 7
write(2, "afile", 5afile)                    = 5
openat(AT_FDCWD, "/usr/share/locale/locale.alias", O_RDONLY|O_CLOEXEC) = 4
newfstatat(4, "", {st_mode=S_IFREG|0644, st_size=2996, ...}, AT_EMPTY_PATH) = 0
read(4, "# Locale name alias data base.\n#"..., 4096) = 2996
read(4, "", 4096)                       = 0
close(4)                                = 0
openat(AT_FDCWD, "/usr/share/locale/en_US.UTF-8/LC_MESSAGES/libc.mo", O_RDONLY) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/usr/share/locale/en_US.utf8/LC_MESSAGES/libc.mo", O_RDONLY) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/usr/share/locale/en_US/LC_MESSAGES/libc.mo", O_RDONLY) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/usr/share/locale/en.UTF-8/LC_MESSAGES/libc.mo", O_RDONLY) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/usr/share/locale/en.utf8/LC_MESSAGES/libc.mo", O_RDONLY) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/usr/share/locale/en/LC_MESSAGES/libc.mo", O_RDONLY) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/usr/share/locale-langpack/en_US.UTF-8/LC_MESSAGES/libc.mo", O_RDONLY) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/usr/share/locale-langpack/en_US.utf8/LC_MESSAGES/libc.mo", O_RDONLY) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/usr/share/locale-langpack/en_US/LC_MESSAGES/libc.mo", O_RDONLY) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/usr/share/locale-langpack/en.UTF-8/LC_MESSAGES/libc.mo", O_RDONLY) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/usr/share/locale-langpack/en.utf8/LC_MESSAGES/libc.mo", O_RDONLY) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/usr/share/locale-langpack/en/LC_MESSAGES/libc.mo", O_RDONLY) = -1 ENOENT (No such file or directory)
write(2, ": Unknown error 512\n", 20: Unknown error 512
)   = 20
dup(1)                                  = 4
close(4)                                = 0
dup(2)                                  = 4
close(4)                                = 0
exit_group(65)                          = ?
+++ exited with 65 +++

repo: juicedata/juicefs


text:
🛑 Colegio de Escribanos de Santa Fe is down

In 2e2b970, Colegio de Escribanos de Santa Fe (https://www.coessfe1.org.ar/portal/index.php/es/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Colegio de Escribanos de Santa Fe is back up in cdc2574 after 5 minutes.

repo: juliannavarro/upptime


text:
Incomplete and Incorrect Barcode Readings with MobileScanner

I am using the MobileScanner, version ^6.0.2, and it seems that the scanner is having difficulty correctly identifying barcodes. Most of the time, when a barcode is detected, only the initial digits are correct, and the remaining digits are repeated incorrectly (e.g., 21231500000000000000).

This sounds like an MLKit issue, which unfortunately we do not have much control over (except for upgrading MLKit every so often)

authors: navaronbracke silva-luiz


text:
travis: go versions

There is a gap in the tested go versions. tip points already to the coming 1.10.
I added the kind of missing 1.9 release

thanks!

authors: Comradin julienschmidt

repo: julienschmidt/httprouter


text:
[Snyk] Upgrade io.cucumber:cucumber-junit from 7.3.4 to 7.4.0

This PR was automatically created by Snyk using the credentials of a real user.Snyk has created this PR to upgrade io.cucumber:cucumber-junit from 7.3.4 to 7.4.0.
:information_source: Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

The recommended version is 1 version ahead of your current version.
The recommended version was released 22 days ago, on 2022-06-22.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.
For more information:
🧐 View latest project report
🛠 Adjust upgrade PR settings
🔕 Ignore this dependency or unsubscribe from future upgrade PRs

Resolvido em 1973910.

repo: jultty/semtec-api


text:
cd to sub directory of directory with spaces does not work as slash gets removed

[ ] I have read through the manual page (man fzf)
[x] I have the latest version of fzf
[x] I have searched through the existing issues

Info

OS

[x] Linux
[ ] Mac OS X
[ ] Windows
[ ] Etc.

Shell

[x] bash
[ ] zsh
[ ] fish

Problem / Steps to reproduce

I have following things in the bashrc file
source "$HOME/fzf-tab-completion-master/bash/fzf-bash-completion.sh"
bind -x '"\t": fzf_bash_completion'
export FZF_COMPLETION_AUTO_COMMON_PREFIX=true
[ -f ~/.fzf.bash ] && source ~/.fzf.bash

I think you should report the issue to https://github.com/lincheney/fzf-tab-completion

authors: junegunn overtomanu

repo: junegunn/fzf


text:
🛑 kawaki is down

In 0ccf44e, kawaki (https://www.pegasusknight.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: kawaki is back up in eade4c2.

repo: junjanjon/WatchSomeSites


text:
Shim to support the notebook extensions

This PR add a shim to ensure the classic notebook extension installed on top of nbclassic do not break while importing notebook packages being no more available in nbclassic. To achieve this backwards compatibility, the needed module/package are shimmed, based on the existence or not of specific versions of notebook (V6, >V7).

[x] Discuss if we need to keep distinct shimming logic for notebook v6 and notebook v7.
[x] Discuss if we need to consider a more generic module loading shim based on https://docs.python.org/3/library/importlib.html#importlib.abc.Loader

For classic extensions to be operational, we may also need https://github.com/jupyter-server/jupyter_server/pull/868 (add back IPythonHandler) and depend on a new jupyter-server release with that patch.

We have discussed this PR and the options to ensure backwards compatibility of the notebook extensions for nbclassic at last community call with @Zsailer  and @afshin . I have further discussed the options with @ericsnekbytes , @RRosio  and @seibert.
My last commit takes into account the feedback to not add IPythonHandler into jupyter-server. There are advantages to progress with the option of this PR to:

Have a single place where the shim occurs. To further adopt the idea to not inject shim in non-related repos like jupyter-server, it sounds good and in-line to also not inject shims in the notebook repos.
We should avoid allowing extensions developers of notebook 7 to use the old notebook packages (notebook.base..) as we want at some point to remove that shim. In other words, if we allow them to use eg. notebook.base..., those extensions will break when the shim that would be in notebook 7 will be removed (e.g. in notebook 8)

I will demo this PR at today community call with various setups (nbclassic with a working notebook extension while notebook 7, or notebook 7 or no notebook is installed).
cc/ @kevingoldsmith

@Zsailer We have just discussed the options at the community call and would love you feedback on the options proposed in this PR. I have given the demo and will be happy to replay it in one-one if you like.
We have decided to re-discuss this during next week community call. Of course, we don't need to wait that call to further brainstorm and exchange on this 👍

Have a single place where the shim occurs. To further adopt the idea to not inject shim in non-related repos like jupyter-server, it sounds good and in-line to also not inject shims in the notebook repos.
We should avoid allowing extensions developers of notebook 7 to use the old notebook packages (notebook.base..) as we want at some point to remove that shim. In other words, if we allow them to use eg. notebook.base..., those extensions will break when the shim that would be in notebook 7 will be removed (e.g. in notebook 8)

:+1: Totally agree with these two goals.
I think this approach is good. Let's roll with it. If we hear reports of major issues coming from patching sys.modules, we can always change course. In the meantime, this is a nice, clean solution. 🚀

Super! Thx a log @Zsailer for the review and though with this. I see relevant CI failure due to the usage of assert. Let me fix that before merging 👍

The failing selenium tests are also encountered in https://github.com/jupyter/nbclassic/pull/114. This is prolly a regression and not related to this PR.
I have fixed the relevant tests, so this is good to go. Merging.

I have opened https://github.com/jupyter/nbclassic/pull/114 to follow-up on the selenium tests.

authors: Zsailer echarles

repo: jupyter/nbclassic


text:
tests fail on windows if unix utilities are not available

The unit tests make calls to unix utilities including bash and whoami.  There are various method for installing these in Windows, WSL, Cygwin, MSYS2, but they are not installed on many systems.  The unit tests fail if these utilities are not installed and I suspect that terminado does not work properly in these cases.
The AppVeyor build enviornment does provide these tools via MinGW, MSYS and Cygwin which explains the passing CI.
Is the expectation that terminado requires these utilities on Windows?

Tested that jupyter notebook and jupyter lab will open a Powershell is bash is not installed.  terminado works fine without bash, the only concern is tests.

Verified this on https://github.com/conda-forge/terminado-feedstock/pull/16 ... py36 runs fine once it has posix as a test dependency.
A few other tests also failed on different windows/python combinations, with these skips (hopefully) clearing it up...
{% set skips = "-k 'not single_process'" %}  # [win and py37]
{% set skips = "-k 'not (namespace or basic_command)'" %}  # [win and py38]

Perhaps it's time to move this to azure pipelines/github actions and get some deeper coverage...

authors: bollwyvl jjhelmus

repo: jupyter/terminado


text:
Re-structuring docs to have consistent sections

This restructures our documentation to roughly follow the divio documentation framework. It breaks down our docs into a few pieces:

Tutorials (where getting started now lives)
How To (now a top-level section)
Reference
About

The goal is to make the documentation easier / more consistent to navigate, and to make it more obvious how somebody could extend the documentation based on the kind of content they want to write.
I don't believe that it changes any of the URL structures, just the navigation in Sphinx (some pages are added / broken apart / etc however)

OK all - I think that I've addressed comments in the last couple of commits!

Hey all - if nobody objects, I'm going to resolve the merge conflict and then merge this in a couple of days

repo: jupyterhub/binder


text:
Title bar blur state is missing

When switching between two JupyterLab Dekstop windows it is impossible to tell which on is active because title bar does not change state. Can you tell which one is active when I am switching?

Compare it with native title bars:

Of note this is properly implemented in https://github.com/AlexTorresSk/custom-electron-titlebar.

this is fixed now with v3.5.1-1

authors: krassowski mbektas

repo: jupyterlab/jupyterlab-desktop


text:
Github Pages

Hey Justus,
Kannst du unter Settings den gh-pages branch als provider für die Pages einstellen? https://help.github.com/articles/configuring-a-publishing-source-for-github-pages/#enabling-github-pages-to-publish-your-site-from-master-or-gh-pages
Ich schau mir das System zwar erst an, aber eigentlich sollte die Seite dann unter
https://jusjusjus.github.io/StadtteilsucheDD erreichbar sein.
Cheers,
P

Mit #3 funktioniert alles einwandfrei in Github Pages. See https://thegreatwhiteshark.github.io/StadtteilsucheDD/index.html
Dafür musst du nur unter Settings den Master branch als Quelle für die Pages angeben.

repo: jusjusjus/StadtteilsucheDD


text:
fix(refunds): remove to schema from refund aggregate response and exclude it from open api documentation

Type of Change

[x] Bugfix
[ ] New feature
[ ] Enhancement
[ ] Refactoring
[ ] Dependency updates
[ ] Documentation
[ ] CI/CD

Description

Additional Changes

[ ] This PR modifies the API contract
[ ] This PR modifies the database schema
[ ] This PR modifies application configuration/environment variables

Motivation and Context

#5990
How did you test it?

Checklist

[x] I formatted the code cargo +nightly fmt --all
[x] I addressed lints thrown by cargo clippy
[x] I reviewed the submitted code
[ ] I added unit tests for my changes where possible

Hi @apoorvdixit88 ,
I've removed all the openapi references (both v1 and v2) to RefundAggregateResponse. However, I don't see any differences in the generated openapi documents. It seems RefundAggregateResponse is not displayed even though openapi document has reference to it.

Hi @apoorvdixit88 ,
I've removed all the openapi references (both v1 and v2) to RefundAggregateResponse. However, I don't see any differences in the generated openapi documents. It seems RefundAggregateResponse is not displayed originally even though openapi document has reference to it.

Hi @qstommyshu
We can see the openapi documents changes in the files.
Also there is some conflict, can you please check?

Hi @apoorvdixit88 ,
I've removed all the openapi references (both v1 and v2) to RefundAggregateResponse. However, I don't see any differences in the generated openapi documents. It seems RefundAggregateResponse is not displayed originally even though openapi document has reference to it.

Hi @qstommyshu We can see the openapi documents changes in the files. Also there is some conflict, can you please check?

I pulled out the generated openapi documents but didn't see anything different for some reason...

@qstommyshu Please add the proper description and testcases

@qstommyshu Please add the proper description and testcases

HI @qstommyshu Please add description as well.

@apoorvdixit88 Can you add the test cases ?

@apoorvdixit88 Can you add the test cases ?

Humm, I'm not sure what other test cases I can add. According to this comment, I think the test case I currently have is proper test cases?

Hi @apoorvdixit88 ,
I've removed all the openapi references (both v1 and v2) to RefundAggregateResponse. However, I don't see any differences in the generated openapi documents. It seems RefundAggregateResponse is not displayed originally even though openapi document has reference to it.

Hi @qstommyshu We can see the openapi documents changes in the files. Also there is some conflict, can you please check?

Correct me if I'm wrong.

repo: juspay/hyperswitch


text:
I'm new to VS  and  mapDriver is hard to  build ,  can you give me the mapDriver.exe? thx  very much

I build the usemode app success but mapDriver was failed

How to build your usermode success?

repo: jussihi/PUBG-map-hack


text:
🛑 Bitwarden is down

In af2df04, Bitwarden (https://bitwarden.mkacg.com) was down:

HTTP code: 530
Response time: 147 ms

Resolved: Bitwarden is back up in a0faa55 after 10 minutes.


text:
Issue with cluster-level resources

I've been seeing this issue a lot lately:
ts=2019-03-19T18:15:52.144930335Z caller=loop.go:412 component=sync-loop err="executing HTTP request: 400 Bad Request parsing <cluster>:clusterrole/kube2iam: invalid service ID\n"

It causes fluxctl sync to return Error: timeout, but no other discernible issues.
See https://github.com/weaveworks/flux/issues/1843

It also prevents the flux-sync tag from being moved forward.

This error is actually coming from flux code, and is already fixed in flux.

I will get to this eventually, but as this is an open source project anyone can bump the version.

Yes that was meant as a tip to people they can resolve it that way (I have) not as a complaint. Thanks, fluxcloud does a nice job

Seeing this with justinbarrick/fluxcloud:v0.3.4 && quay.io/weaveworks/flux:1.11.1 and quay.io/weaveworks/flux:1.12
flux-665cffc4fb-bfkjx fluxcloud {"id":0,"serviceIDs":["\u003ccluster\u003e:namespace/infra-integ","\u003ccluster\u003e:namespace/infra-prod"],"type":"sync","startedAt":"2019-04-11T22:05:58.564240083Z","endedAt":"2019-04-11T22:05:58.564240083Z","logLevel":"info","metadata":{"commits":[{"revision":"f956e3c6a3ee444b8ff36dad1dae60fc68245d14","message":"test"},{"revision":"4f691aa2e00f8d46d419edd907bfa6853b89d220","message":"add the gke cluster folder"},{"revision":"9a5b243217ecd69bee8616064105e41688cacc56","message":"Add global folder structure for apps, and warning about clusters folder (#7)"}],"includes":{"other":true},"initialSync":true}}
flux-665cffc4fb-bfkjx fluxcloud parsing <cluster>:namespace/infra-integ: invalid service ID
flux-665cffc4fb-bfkjx flux ts=2019-04-11T22:05:59.575092664Z caller=loop.go:412 component=sync-loop err="executing HTTP request: 400 Bad Request parsing <cluster>:namespace/infra-integ: invalid service ID\n"
flux-665cffc4fb-bfkjx flux ts=2019-04-11T22:05:59.588819181Z caller=loop.go:90 component=sync-loop err="executing HTTP request: 400 Bad Request parsing <cluster>:namespace/infra-integ: invalid service ID\n"

@justinbarrick which version needs bumping?

Seems like this was fixed with v0.3.6

Can confirm fixed in v0.3.6 with flux 1.11.1

authors: davidkarlsen justinbarrick kraney rcohenDBRS rocktavious

repo: justinbarrick/fluxcloud


text:
Chefdk for CI tests

Stolen from https://github.com/chef-cookbooks/docker/blob/master/.travis.yml :wink:
Seems to have reduced CI testing from ~4min to ~1min.

I'm all for this. But I feel @justincampbell should press the magic merge button on this one.

:+1:

Thanks @justincampbell :)

authors: jmccann justincampbell predominant

repo: justincampbell/chef-drone


text:
Implement $ref compliance

I have added some tests to #210
These tests shows that there are still work do be done to make this code work.

@TerjeBr you would want to open a PR against @araines fork and branch to expand on his work

This was forked off @araines branch.
Do you mean I should open the PR at https://github.com/araines/json-schema instead of here at https://github.com/justinrainbow/json-schema ?

Correct. That will allow your work to come in on the open PR. Otherwise, your open PR would be bringing in his work and I think he is still making adjustments. I would prefer you work together on that branch of changes. Make sense?

authors: TerjeBr bighappyface

repo: justinrainbow/json-schema


text:
chrome-headless: Fontconfig error

I cannot access <host>:9222/json/version. It return text/html, not application/json nor json formatted text. I think chrome was dead and it return error html page.
I find some error in docker compose logs.
headless_chrome_1  | [0510/184749.130251:ERROR:gpu_process_transport_factory.cc(1007)] Lost UI shared context.
headless_chrome_1  |
headless_chrome_1  | DevTools listening on ws://0.0.0.0:9222/devtools/browser/eed68d51-7784-42ff-925d-e6ad4e2e8fd9
headless_chrome_1  | Fontconfig warning: "/etc/fonts/fonts.conf", line 5: unknown element "its:rules"
headless_chrome_1  | Fontconfig warning: "/etc/fonts/fonts.conf", line 6: unknown element "its:translateRule"
headless_chrome_1  | Fontconfig error: "/etc/fonts/fonts.conf", line 6: invalid attribute 'translate'
headless_chrome_1  | Fontconfig error: "/etc/fonts/fonts.conf", line 6: invalid attribute 'selector'
headless_chrome_1  | Fontconfig error: "/etc/fonts/fonts.conf", line 7: invalid attribute 'xmlns:its'
headless_chrome_1  | Fontconfig error: "/etc/fonts/fonts.conf", line 7: invalid attribute 'version'
headless_chrome_1  | Fontconfig warning: "/etc/fonts/fonts.conf", line 9: unknown element "description"
headless_chrome_1  | Fontconfig warning: "/etc/fonts/conf.d/10-hinting-slight.conf", line 4: unknown element "its:rules"
headless_chrome_1  | Fontconfig warning: "/etc/fonts/conf.d/10-hinting-slight.conf", line 5: unknown element "its:translateRule"
headless_chrome_1  | Fontconfig error: "/etc/fonts/conf.d/10-hinting-slight.conf", line 5: invalid attribute 'translate'
headless_chrome_1  | Fontconfig error: "/etc/fonts/conf.d/10-hinting-slight.conf", line 5: invalid attribute 'selector'
headless_chrome_1  | Fontconfig error: "/etc/fonts/conf.d/10-hinting-slight.conf", line 6: invalid attribute 'xmlns:its'
headless_chrome_1  | Fontconfig error: "/etc/fonts/conf.d/10-hinting-slight.conf", line 6: invalid attribute 'version'
headless_chrome_1  | Fontconfig warning: "/etc/fonts/conf.d/10-hinting-slight.conf", line 8: unknown element "description"
headless_chrome_1  | Fontconfig warning: "/etc/fonts/conf.d/10-scale-bitmap-fonts.conf", line 4: unknown element "its:rules"
headless_chrome_1  | Fontconfig warning: "/etc/fonts/conf.d/10-scale-bitmap-fonts.conf", line 5: unknown element "its:translateRule"
headless_chrome_1  | Fontconfig error: "/etc/fonts/conf.d/10-scale-bitmap-fonts.conf", line 5: invalid attribute 'translate'
headless_chrome_1  | Fontconfig error: "/etc/fonts/conf.d/10-scale-bitmap-fonts.conf", line 5: invalid attribute 'selector'
headless_chrome_1  | Fontconfig error: "/etc/fonts/conf.d/10-scale-bitmap-fonts.conf", line 6: invalid attribute 'xmlns:its'
headless_chrome_1  | Fontconfig error: "/etc/fonts/conf.d/10-scale-bitmap-fonts.conf", line 6: invalid attribute 'version'
headless_chrome_1  | Fontconfig warning: "/etc/fonts/conf.d/10-scale-bitmap-fonts.conf", line 8: unknown element "description"
headless_chrome_1  | Fontconfig warning: "/etc/fonts/conf.d/11-lcdfilter-default.conf", line 4: unknown element "its:rules"
headless_chrome_1  | Fontconfig warning: "/etc/fonts/conf.d/11-lcdfilter-default.conf", line 5: unknown element "its:translateRule"
headless_chrome_1  | Fontconfig error: "/etc/fonts/conf.d/11-lcdfilter-default.conf", line 5: invalid attribute 'translate'
headless_chrome_1  | Fontconfig error: "/etc/fonts/conf.d/11-lcdfilter-default.conf", line 5: invalid attribute 'selector'
headless_chrome_1  | Fontconfig error: "/etc/fonts/conf.d/11-lcdfilter-default.conf", line 6: invalid attribute 'xmlns:its'
headless_chrome_1  | Fontconfig error: "/etc/fonts/conf.d/11-lcdfilter-default.conf", line 6: invalid attribute 'version'
headless_chrome_1  | Fontconfig warning: "/etc/fonts/conf.d/11-lcdfilter-default.conf", line 8: unknown element "description"
headless_chrome_1  | Fontconfig warning: "/etc/fonts/conf.d/20-unhint-small-vera.conf", line 4: unknown element "its:rules"
headless_chrome_1  | Fontconfig warning: "/etc/fonts/conf.d/20-unhint-small-vera.conf", line 5: unknown element "its:translateRule"
headless_chrome_1  | Fontconfig error: "/etc/fonts/conf.d/20-unhint-small-vera.conf", line 5: invalid attribute 'translate'
headless_chrome_1  | Fontconfig error: "/etc/fonts/conf.d/20-unhint-small-vera.conf", line 5: invalid attribute 'selector'
headless_chrome_1  | Fontconfig error: "/etc/fonts/conf.d/20-unhint-small-vera.conf", line 6: invalid attribute 'xmlns:its'
headless_chrome_1  | Fontconfig error: "/etc/fonts/conf.d/20-unhint-small-vera.conf", line 6: invalid attribute 'version'
headless_chrome_1  | Fontconfig warning: "/etc/fonts/conf.d/20-unhint-small-vera.conf", line 8: unknown element "description"
headless_chrome_1  | Fontconfig warning: "/etc/fonts/conf.d/30-metric-aliases.conf", line 4: unknown element "its:rules"
headless_chrome_1  | Fontconfig warning: "/etc/fonts/conf.d/30-metric-aliases.conf", line 5: unknown element "its:translateRule"
headless_chrome_1  | Fontconfig error: "/etc/fonts/conf.d/30-metric-aliases.conf", line 5: invalid attribute 'translate'
headless_chrome_1  | Fontconfig error: "/etc/fonts/conf.d/30-metric-aliases.conf", line 5: invalid attribute 'selector'
headless_chrome_1  | Fontconfig error: "/etc/fonts/conf.d/30-metric-aliases.conf", line 6: invalid attribute 'xmlns:its'
headless_chrome_1  | Fontconfig error: "/etc/fonts/conf.d/30-metric-aliases.conf", line 6: invalid attribute 'version'
headless_chrome_1  | Fontconfig warning: "/etc/fonts/conf.d/30-metric-aliases.conf", line 8: unknown element "description"
headless_chrome_1  | Fontconfig warning: "/etc/fonts/conf.d/40-nonlatin.conf", line 4: unknown element "its:rules"
headless_chrome_1  | Fontconfig warning: "/etc/fonts/conf.d/40-nonlatin.conf", line 5: unknown element "its:translateRule"
headless_chrome_1  | Fontconfig error: "/etc/fonts/conf.d/40-nonlatin.conf", line 5: invalid attribute 'translate'
headless_chrome_1  | Fontconfig error: "/etc/fonts/conf.d/40-nonlatin.conf", line 5: invalid attribute 'selector'
headless_chrome_1  | Fontconfig error: "/etc/fonts/conf.d/40-nonlatin.conf", line 6: invalid attribute 'xmlns:its'
headless_chrome_1  | Fontconfig error: "/etc/fonts/conf.d/40-nonlatin.conf", line 6: invalid attribute 'version'
headless_chrome_1  | Fontconfig warning: "/etc/fonts/conf.d/40-nonlatin.conf", line 8: unknown element "description"
headless_chrome_1  | Fontconfig warning: "/etc/fonts/conf.d/45-generic.conf", line 4: unknown element "its:rules"
headless_chrome_1  | Fontconfig warning: "/etc/fonts/conf.d/45-generic.conf", line 5: unknown element "its:translateRule"
headless_chrome_1  | Fontconfig error: "/etc/fonts/conf.d/45-generic.conf", line 5: invalid attribute 'translate'
headless_chrome_1  | Fontconfig error: "/etc/fonts/conf.d/45-generic.conf", line 5: invalid attribute 'selector'
headless_chrome_1  | Fontconfig error: "/etc/fonts/conf.d/45-generic.conf", line 6: invalid attribute 'xmlns:its'
headless_chrome_1  | Fontconfig error: "/etc/fonts/conf.d/45-generic.conf", line 6: invalid attribute 'version'
headless_chrome_1  | Fontconfig warning: "/etc/fonts/conf.d/45-generic.conf", line 8: unknown element "description"
headless_chrome_1  | Fontconfig warning: "/etc/fonts/conf.d/45-latin.conf", line 4: unknown element "its:rules"
headless_chrome_1  | Fontconfig warning: "/etc/fonts/conf.d/45-latin.conf", line 5: unknown element "its:translateRule"
headless_chrome_1  | Fontconfig error: "/etc/fonts/conf.d/45-latin.conf", line 5: invalid attribute 'translate'
headless_chrome_1  | Fontconfig error: "/etc/fonts/conf.d/45-latin.conf", line 5: invalid attribute 'selector'
headless_chrome_1  | Fontconfig error: "/etc/fonts/conf.d/45-latin.conf", line 6: invalid attribute 'xmlns:its'
headless_chrome_1  | Fontconfig error: "/etc/fonts/conf.d/45-latin.conf", line 6: invalid attribute 'version'
headless_chrome_1  | Fontconfig warning: "/etc/fonts/conf.d/45-latin.conf", line 8: unknown element "description"
headless_chrome_1  | Fontconfig warning: "/etc/fonts/conf.d/49-sansserif.conf", line 4: unknown element "its:rules"
headless_chrome_1  | Fontconfig warning: "/etc/fonts/conf.d/49-sansserif.conf", line 5: unknown element "its:translateRule"
headless_chrome_1  | Fontconfig error: "/etc/fonts/conf.d/49-sansserif.conf", line 5: invalid attribute 'translate'
headless_chrome_1  | Fontconfig error: "/etc/fonts/conf.d/49-sansserif.conf", line 5: invalid attribute 'selector'
headless_chrome_1  | Fontconfig error: "/etc/fonts/conf.d/49-sansserif.conf", line 6: invalid attribute 'xmlns:its'
headless_chrome_1  | Fontconfig error: "/etc/fonts/conf.d/49-sansserif.conf", line 6: invalid attribute 'version'
headless_chrome_1  | Fontconfig warning: "/etc/fonts/conf.d/49-sansserif.conf", line 8: unknown element "description"
headless_chrome_1  | Fontconfig warning: "/etc/fonts/conf.d/50-user.conf", line 4: unknown element "its:rules"
headless_chrome_1  | Fontconfig warning: "/etc/fonts/conf.d/50-user.conf", line 5: unknown element "its:translateRule"
headless_chrome_1  | Fontconfig error: "/etc/fonts/conf.d/50-user.conf", line 5: invalid attribute 'translate'
headless_chrome_1  | Fontconfig error: "/etc/fonts/conf.d/50-user.conf", line 5: invalid attribute 'selector'
headless_chrome_1  | Fontconfig error: "/etc/fonts/conf.d/50-user.conf", line 6: invalid attribute 'xmlns:its'
headless_chrome_1  | Fontconfig error: "/etc/fonts/conf.d/50-user.conf", line 6: invalid attribute 'version'
headless_chrome_1  | Fontconfig warning: "/etc/fonts/conf.d/50-user.conf", line 8: unknown element "description"
headless_chrome_1  | Fontconfig warning: "/etc/fonts/conf.d/51-local.conf", line 4: unknown element "its:rules"
headless_chrome_1  | Fontconfig warning: "/etc/fonts/conf.d/51-local.conf", line 5: unknown element "its:translateRule"
headless_chrome_1  | Fontconfig error: "/etc/fonts/conf.d/51-local.conf", line 5: invalid attribute 'translate'
headless_chrome_1  | Fontconfig error: "/etc/fonts/conf.d/51-local.conf", line 5: invalid attribute 'selector'
headless_chrome_1  | Fontconfig error: "/etc/fonts/conf.d/51-local.conf", line 6: invalid attribute 'xmlns:its'
headless_chrome_1  | Fontconfig error: "/etc/fonts/conf.d/51-local.conf", line 6: invalid attribute 'version'
headless_chrome_1  | Fontconfig warning: "/etc/fonts/conf.d/51-local.conf", line 8: unknown element "description"
headless_chrome_1  | Fontconfig warning: "/etc/fonts/conf.d/60-generic.conf", line 4: unknown element "its:rules"
headless_chrome_1  | Fontconfig warning: "/etc/fonts/conf.d/60-generic.conf", line 5: unknown element "its:translateRule"
headless_chrome_1  | Fontconfig error: "/etc/fonts/conf.d/60-generic.conf", line 5: invalid attribute 'translate'
headless_chrome_1  | Fontconfig error: "/etc/fonts/conf.d/60-generic.conf", line 5: invalid attribute 'selector'
headless_chrome_1  | Fontconfig error: "/etc/fonts/conf.d/60-generic.conf", line 6: invalid attribute 'xmlns:its'
headless_chrome_1  | Fontconfig error: "/etc/fonts/conf.d/60-generic.conf", line 6: invalid attribute 'version'
headless_chrome_1  | Fontconfig warning: "/etc/fonts/conf.d/60-generic.conf", line 8: unknown element "description"
headless_chrome_1  | Fontconfig warning: "/etc/fonts/conf.d/60-latin.conf", line 4: unknown element "its:rules"
headless_chrome_1  | Fontconfig warning: "/etc/fonts/conf.d/60-latin.conf", line 5: unknown element "its:translateRule"
headless_chrome_1  | Fontconfig error: "/etc/fonts/conf.d/60-latin.conf", line 5: invalid attribute 'translate'
headless_chrome_1  | Fontconfig error: "/etc/fonts/conf.d/60-latin.conf", line 5: invalid attribute 'selector'
headless_chrome_1  | Fontconfig error: "/etc/fonts/conf.d/60-latin.conf", line 6: invalid attribute 'xmlns:its'
headless_chrome_1  | Fontconfig error: "/etc/fonts/conf.d/60-latin.conf", line 6: invalid attribute 'version'
headless_chrome_1  | Fontconfig warning: "/etc/fonts/conf.d/60-latin.conf", line 8: unknown element "description"
headless_chrome_1  | Fontconfig warning: "/etc/fonts/conf.d/65-fonts-persian.conf", line 34: unknown element "its:rules"
headless_chrome_1  | Fontconfig warning: "/etc/fonts/conf.d/65-fonts-persian.conf", line 35: unknown element "its:translateRule"
headless_chrome_1  | Fontconfig error: "/etc/fonts/conf.d/65-fonts-persian.conf", line 35: invalid attribute 'translate'
headless_chrome_1  | Fontconfig error: "/etc/fonts/conf.d/65-fonts-persian.conf", line 35: invalid attribute 'selector'
headless_chrome_1  | Fontconfig error: "/etc/fonts/conf.d/65-fonts-persian.conf", line 36: invalid attribute 'xmlns:its'
headless_chrome_1  | Fontconfig error: "/etc/fonts/conf.d/65-fonts-persian.conf", line 36: invalid attribute 'version'
headless_chrome_1  | Fontconfig warning: "/etc/fonts/conf.d/65-nonlatin.conf", line 4: unknown element "its:rules"
headless_chrome_1  | Fontconfig warning: "/etc/fonts/conf.d/65-nonlatin.conf", line 5: unknown element "its:translateRule"
headless_chrome_1  | Fontconfig error: "/etc/fonts/conf.d/65-nonlatin.conf", line 5: invalid attribute 'translate'
headless_chrome_1  | Fontconfig error: "/etc/fonts/conf.d/65-nonlatin.conf", line 5: invalid attribute 'selector'
headless_chrome_1  | Fontconfig error: "/etc/fonts/conf.d/65-nonlatin.conf", line 6: invalid attribute 'xmlns:its'
headless_chrome_1  | Fontconfig error: "/etc/fonts/conf.d/65-nonlatin.conf", line 6: invalid attribute 'version'
headless_chrome_1  | Fontconfig warning: "/etc/fonts/conf.d/65-nonlatin.conf", line 8: unknown element "description"
headless_chrome_1  | Fontconfig warning: "/etc/fonts/conf.d/69-unifont.conf", line 4: unknown element "its:rules"
headless_chrome_1  | Fontconfig warning: "/etc/fonts/conf.d/69-unifont.conf", line 5: unknown element "its:translateRule"
headless_chrome_1  | Fontconfig error: "/etc/fonts/conf.d/69-unifont.conf", line 5: invalid attribute 'translate'
headless_chrome_1  | Fontconfig error: "/etc/fonts/conf.d/69-unifont.conf", line 5: invalid attribute 'selector'
headless_chrome_1  | Fontconfig error: "/etc/fonts/conf.d/69-unifont.conf", line 6: invalid attribute 'xmlns:its'
headless_chrome_1  | Fontconfig error: "/etc/fonts/conf.d/69-unifont.conf", line 6: invalid attribute 'version'
headless_chrome_1  | Fontconfig warning: "/etc/fonts/conf.d/70-no-bitmaps.conf", line 4: unknown element "its:rules"
headless_chrome_1  | Fontconfig warning: "/etc/fonts/conf.d/70-no-bitmaps.conf", line 5: unknown element "its:translateRule"
headless_chrome_1  | Fontconfig error: "/etc/fonts/conf.d/70-no-bitmaps.conf", line 5: invalid attribute 'translate'
headless_chrome_1  | Fontconfig error: "/etc/fonts/conf.d/70-no-bitmaps.conf", line 5: invalid attribute 'selector'
headless_chrome_1  | Fontconfig error: "/etc/fonts/conf.d/70-no-bitmaps.conf", line 6: invalid attribute 'xmlns:its'
headless_chrome_1  | Fontconfig error: "/etc/fonts/conf.d/70-no-bitmaps.conf", line 6: invalid attribute 'version'
headless_chrome_1  | Fontconfig warning: "/etc/fonts/conf.d/70-no-bitmaps.conf", line 8: unknown element "description"
headless_chrome_1  | Fontconfig warning: "/etc/fonts/conf.d/80-delicious.conf", line 4: unknown element "its:rules"
headless_chrome_1  | Fontconfig warning: "/etc/fonts/conf.d/80-delicious.conf", line 5: unknown element "its:translateRule"
headless_chrome_1  | Fontconfig error: "/etc/fonts/conf.d/80-delicious.conf", line 5: invalid attribute 'translate'
headless_chrome_1  | Fontconfig error: "/etc/fonts/conf.d/80-delicious.conf", line 5: invalid attribute 'selector'
headless_chrome_1  | Fontconfig error: "/etc/fonts/conf.d/80-delicious.conf", line 6: invalid attribute 'xmlns:its'
headless_chrome_1  | Fontconfig error: "/etc/fonts/conf.d/80-delicious.conf", line 6: invalid attribute 'version'
headless_chrome_1  | Fontconfig warning: "/etc/fonts/conf.d/90-synthetic.conf", line 4: unknown element "its:rules"
headless_chrome_1  | Fontconfig warning: "/etc/fonts/conf.d/90-synthetic.conf", line 5: unknown element "its:translateRule"
headless_chrome_1  | Fontconfig error: "/etc/fonts/conf.d/90-synthetic.conf", line 5: invalid attribute 'translate'
headless_chrome_1  | Fontconfig error: "/etc/fonts/conf.d/90-synthetic.conf", line 5: invalid attribute 'selector'
headless_chrome_1  | Fontconfig error: "/etc/fonts/conf.d/90-synthetic.conf", line 6: invalid attribute 'xmlns:its'
headless_chrome_1  | Fontconfig error: "/etc/fonts/conf.d/90-synthetic.conf", line 6: invalid attribute 'version'
headless_chrome_1  | Fontconfig error: Cannot load config file from /etc/fonts/fonts.conf

and it is my docker-compose.yml file
ersion: '3'
services:
  bot_item4:
    image: item4/yui:latest
    volumes:
      - ./item4:/yui/data
    environment:
      - YUI_CONFIG_FILE_PATH=data/yui.config.toml
    depends_on:
      - db
      - headless_chrome
    links:
      - db
      - headless_chrome
    command: ./data/run.sh
  bot_9xd:
    image: item4/yui:latest
    volumes:
      - ./9xd:/yui/data
    environment:
      - YUI_CONFIG_FILE_PATH=data/yui.config.toml
    depends_on:
      - db
      - headless_chrome
    links:
      - db
      - headless_chrome
    command: ./data/run.sh
  bot_xnuk:
    image: item4/yui:latest
    volumes:
      - ./xnuk:/yui/data
    environment:
      - YUI_CONFIG_FILE_PATH=data/yui.config.toml
    depends_on:
      - db
      - headless_chrome
    links:
      - db
      - headless_chrome
    command: ./data/run.sh
  db:
    image: postgres:alpine
    volumes:
      - ./postgres/data:/var/lib/postgresql/data
    environment:
      - POSTGRES_PASSWORD=<super secret>
    healthcheck:
      test: "pg_isready -h localhost -p 5432 -q -U postgres"
      interval: 3s
      timeout: 1s
      retries: 10
  headless_chrome:
    image: justinribeiro/chrome-headless
    cap_add:
    - SYS_ADMIN
    command: --headless --disable-gpu --remote-debugging-address=0.0.0.0 --remote-debugging-port=9222

Resolved by #52

repo: justinribeiro/dockerfiles


text:
Alternative for header text on Mobile devices

Is your feature request related to a problem? Please describe.
The current vertical header text on mobile devices look extremely wonky.
Describe the solution you'd like
An alternative (ideally horizontal) approach to the header text to be implemented. The biggest issue would be the "Country" header text which is vastly larger than the field size, hence alternative wording can be used if need be.

This issue is closed with PR #71.


text:
Deprecated string view arguments in urls.py

RemovedInDjango110Warning: Support for string view arguments to url() is deprecated and will be removed in Django 1.10 (got user). Pass the callable instead.

fixed in master, and staged for 0.6.1 release

repo: justquick/django-activity-stream


text:
Add JustList: {JustList name}

Before submission deletes this line:
THIS IS NOT A TOKEN LISTING REQUEST FORM. IF YOU DO NOT FOLLOW THE FORMAT OR MAKE A GENERIC TOKEN REQUEST YOUR ISSUE WILL BE DELETED WITHOUT COMMENT
YOUR JUSTLIST MUST FOLLOW THE JSON SPECIFICATION
https://github.com/justswaporg/justlists/blob/main/example.justlists.ts
Checklist

[x] I understand that this is not the place to request a token listing.
[x] I have tested that my JustList is compatible by pasting the URL into the add a list UI at justswap.org.
[x] I understand that filing an issue or adding liquidity does not guarantee addition to the justlists website.

Please provide the following information for your token.
JustList URL must be HTTPS.
JustList URL:
JustList Name:
Link to the official homepage of the JustList manager:

Sorry, your issue will be closed as you did not submit your information in the correct format.Please resubmit.

repo: justswaporg/justlists


text:
添加JustList: {JustList name}

提交之前请删除下面的话:
如果您没按照要求提交正确的JustList样式，您的issue将会被删除
您提交的JustList json格式必须满足下面链接中定义的例子格式
https://github.com/justswaporg/justlists/blob/main/example.justlists.ts
检查清单

[ ] 我已知晓此issue不是提交token而是提交JustList
[ ] 我已经测试粘贴JustList URL到justswap.org的添加列表中并能够正常展示.
[ ] 我已知晓提交的issue不能确保通过并且提交的JustList不确保能在jsutlists网站中显示.

请提供以下的信息
JustList的json URL必须以HTTPS开头.
JustList URL:
JustList 名称:
JustList 提交者的网站或主页:

Please submit the correct information, invalid information will cause the issue to close

Sorry I'm still trying to understand how this all works


text:
Add JustList: {JustList name}

Before submission deletes this line:
YOUR JUSTLIST MUST FOLLOW THE JSON SPECIFICATION
https://github.com/justswaporg/justlists/blob/main/example.justlists.ts
Checklist

[x] I understand that this is not the place to request a token listing.
[x] I have tested that my JustList is compatible by pasting the URL into the add a list UI at justswap.org.
[x] I understand that filing an issue or adding liquidity does not guarantee addition to the justlists website.

Please provide the following information for your token.
{
"name": "TVD List",
"logoURI": "http://tokenvest.io/v12_files/logo-light.png",
"timestamp": 1660291736000,
"version": {
"major": 1,
"minor": 4,
"patch": 47
},
"tokens": [
{
"symbol":"TVD",
"address":"TWiwCRJPAKPpfMiEWpDrpYQKwHWY5wwPjC",
"chainId":1,
"decimals":18,
"name":"TOKEN VEST Dinar",
"logoURI":"https://static.tronscan.org/production/upload/logo/TWiwCRJPAKPpfMiEWpDrpYQKwHWY5wwPjC.png?t=1656366332208"
}
]
}

https://github.com/justswaporg/justlists/issues/3051


text:
Add+JustList:+{JustList+name}

Before submission deletes this line:
THIS IS NOT A TOKEN LISTING REQUEST FORM. IF YOU DO NOT FOLLOW THE FORMAT OR MAKE A GENERIC TOKEN REQUEST YOUR ISSUE WILL BE DELETED WITHOUT COMMENT
YOUR JUSTLIST MUST FOLLOW THE JSON SPECIFICATION
https://github.com/justswaporg/justlists/blob/main/example.justlists.ts
Checklist

[x] I understand that this is not the place to request a token listing.
[x] I have tested that my JustList is compatible by pasting the URL into the add a list UI at justswap.org.
[x] I understand that filing an issue or adding liquidity does not guarantee addition to the justlists website.

Please provide the following information for your token.
JustList URL must be HTTPS.
JustList URL:
JustList Name:
Link to the official homepage of the JustList manager:

Please submit the correct information, invalid information will cause the issue to close


text:
🛑 Main Website is down

In bbdb7e4, Main Website (https://tecnoscientifica.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Main Website is back up in 27cbd64.

repo: justudin/tsp-status


text:
gopass git: failed to run git  on sub store root

Hi,
Is this another issue between gpg and git?
$ gopass git
[DEBUG] Loaded config: &{Root:0xc4200639e0 Mounts:map[] Version:1.6.0-git+HEAD XXX:map[]}
[DEBUG] Loaded config from /home/jungle/.config/gopass/config.yml: &{Root:0xc4200639e0 Mounts:map[] Version:1.6.0-git+HEAD XXX:map[]}
[root]Running git
[root][DEBUG] store.Git: /usr/local/bin/git [git]
usage: git [--version] [--help] [-C <path>] [-c name=value]
           [--exec-path[=<path>]] [--html-path] [--man-path] [--info-path]
           [-p | --paginate | --no-pager] [--no-replace-objects] [--bare]
           [--git-dir=<path>] [--work-tree=<path>] [--namespace=<name>]
           <command> [<args>]

These are common Git commands used in various situations:

start a working area (see also: git help tutorial)
   clone      Clone a repository into a new directory
   init       Create an empty Git repository or reinitialize an existing one

work on the current change (see also: git help everyday)
   add        Add file contents to the index
   mv         Move or rename a file, a directory, or a symlink
   reset      Reset current HEAD to the specified state
   rm         Remove files from the working tree and from the index

examine the history and state (see also: git help revisions)
   bisect     Use binary search to find the commit that introduced a bug
   grep       Print lines matching a pattern
   log        Show commit logs
   show       Show various types of objects
   status     Show the working tree status

grow, mark and tweak your common history
   branch     List, create, or delete branches
   checkout   Switch branches or restore working tree files
   commit     Record changes to the repository
   diff       Show changes between commits, commit and working tree, etc
   merge      Join two or more development histories together
   rebase     Reapply commits on top of another base tip
   tag        Create, list, delete or verify a tag object signed with GPG

collaborate (see also: git help workflows)
   fetch      Download objects and refs from another repository
   pull       Fetch from and integrate with another repository or a local branch
   push       Update remote refs along with associated objects

'git help -a' and 'git help -g' list available subcommands and some
concept guides. See 'git help <command>' or 'git help <concept>'
to read about a specific subcommand or concept.
[root][DEBUG] Output of '/usr/local/bin/git [git]': ''
[DEBUG] Stacktrace: exit status 1
failed to run command /usr/local/bin/git [git]
github.com/justwatchcom/gopass/backend/git/cli.(*Git).Cmd
        /home/jungle/gopath/src/github.com/justwatchcom/gopass/backend/git/cli/git.go:50
github.com/justwatchcom/gopass/store/sub.(*Store).Git
        /home/jungle/gopath/src/github.com/justwatchcom/gopass/store/sub/git.go:36
github.com/justwatchcom/gopass/store/root.(*Store).Git
        /home/jungle/gopath/src/github.com/justwatchcom/gopass/store/root/git.go:40
github.com/justwatchcom/gopass/action.(*Action).Git
        /home/jungle/gopath/src/github.com/justwatchcom/gopass/action/git.go:22
main.main.func38
        /home/jungle/gopath/src/github.com/justwatchcom/gopass/main.go:614
github.com/justwatchcom/gopass/vendor/github.com/urfave/cli.HandleAction
        /home/jungle/gopath/src/github.com/justwatchcom/gopass/vendor/github.com/urfave/cli/app.go:485
github.com/justwatchcom/gopass/vendor/github.com/urfave/cli.(*App).RunAsSubcommand
        /home/jungle/gopath/src/github.com/justwatchcom/gopass/vendor/github.com/urfave/cli/app.go:379
github.com/justwatchcom/gopass/vendor/github.com/urfave/cli.Command.startApp
        /home/jungle/gopath/src/github.com/justwatchcom/gopass/vendor/github.com/urfave/cli/command.go:280
github.com/justwatchcom/gopass/vendor/github.com/urfave/cli.Command.Run
        /home/jungle/gopath/src/github.com/justwatchcom/gopass/vendor/github.com/urfave/cli/command.go:79
github.com/justwatchcom/gopass/vendor/github.com/urfave/cli.(*App).Run
        /home/jungle/gopath/src/github.com/justwatchcom/gopass/vendor/github.com/urfave/cli/app.go:250
main.main
        /home/jungle/gopath/src/github.com/justwatchcom/gopass/main.go:1030
runtime.main
        /usr/local/go/src/runtime/proc.go:185
runtime.goexit
        /usr/local/go/src/runtime/asm_amd64.s:2337
failed to run git  on sub store root
github.com/justwatchcom/gopass/store/root.(*Store).Git
        /home/jungle/gopath/src/github.com/justwatchcom/gopass/store/root/git.go:45
github.com/justwatchcom/gopass/action.(*Action).Git
        /home/jungle/gopath/src/github.com/justwatchcom/gopass/action/git.go:22
main.main.func38
        /home/jungle/gopath/src/github.com/justwatchcom/gopass/main.go:614
github.com/justwatchcom/gopass/vendor/github.com/urfave/cli.HandleAction
        /home/jungle/gopath/src/github.com/justwatchcom/gopass/vendor/github.com/urfave/cli/app.go:485
github.com/justwatchcom/gopass/vendor/github.com/urfave/cli.(*App).RunAsSubcommand
        /home/jungle/gopath/src/github.com/justwatchcom/gopass/vendor/github.com/urfave/cli/app.go:379
github.com/justwatchcom/gopass/vendor/github.com/urfave/cli.Command.startApp
        /home/jungle/gopath/src/github.com/justwatchcom/gopass/vendor/github.com/urfave/cli/command.go:280
github.com/justwatchcom/gopass/vendor/github.com/urfave/cli.Command.Run
        /home/jungle/gopath/src/github.com/justwatchcom/gopass/vendor/github.com/urfave/cli/command.go:79
github.com/justwatchcom/gopass/vendor/github.com/urfave/cli.(*App).Run
        /home/jungle/gopath/src/github.com/justwatchcom/gopass/vendor/github.com/urfave/cli/app.go:250
main.main
        /home/jungle/gopath/src/github.com/justwatchcom/gopass/main.go:1030
runtime.main
        /usr/local/go/src/runtime/proc.go:185
runtime.goexit
        /usr/local/go/src/runtime/asm_amd64.s:2337

Error: git operation failed: failed to run git  on sub store root: failed to run command /usr/local/bin/git [git]: exit status 1

Actually this doesn't look like an issue at all.
If you run gopass git ... it will invoke git and pass any arguments along to git. If you run gopass git it will run git without any arguments. If invoked without any arguments git will display a usage information and exit with a status of 1. Since this is a return code indicating a sub-process failure gopass will report this.

authors: dominikschulz jungle-boogie

repo: justwatchcom/gopass


text:
Release #3 2016

This is a tracking issue for the Juttle release 3/2016 starting on 2015-02-01. See the wiki page for details about the process.
When you release a package, check a checkbox in this list and add the released version in parens after the package name:

Juttle

[] juttle (0.4.0 shipped, need 0.4.1 with docs changes)

Adapters

[ ] juttle-elastic-adapter
[ ] juttle-gmail-adapter
[ ] juttle-graphite-adapter
[x] juttle-influx-adapter (0.4.0)
[ ] juttle-opentsdb-adapter
[ ] juttle-sql-adapter-common

[ ] juttle-mysql-adapter
[ ] juttle-postgres-adapter
[ ] juttle-sqlite-adapter

[ ] juttle-twitter-adapter

Client side

[ ] juttle-viz
[ ] juttle-client-library

Engine

[ ] juttle-service
[ ] juttle-engine
[ ] outrigger (push deprecated version)

@juttle/developers I updated this checklist to reflect the new juttle-service and juttle-engine packages. As discussed internally, the plan is to release these instead of a new outrigger release and start guiding customers to use that instead, deprecating the existing outrigger package
Since there are references to outrigger in the juttle docs, I think we should push a 0.4.1 juttle release that points to juttle-engine instead.

Also I renamed this issue to avoid potential confusion -- some people thought that 3/2016 meant March 2016.

And I just renamed again to avoid # so that github wouldn't auto-link to an issue.

Released all the things. Phew.

authors: demmer dmajda

repo: juttle/juttle


text:
🛑 TRAPANNI PIZZA is down

In c0f39f3, TRAPANNI PIZZA (https://trapanipizzaestofada.com) was down:

HTTP code: 500
Response time: 825 ms

Resolved: TRAPANNI PIZZA is back up in ab427ce after 30 days, 14 hours, 35 minutes.

repo: jveyes/upptime


text:
小程序 from 组件里面的图片上传失效

小程序 from 组件里面的图片上传失效， h5可以

用uni.uploadFile 自己实现一下吧

authors: jwaterwater zhuanghongbin

repo: jwaterwater/uni-nutui


text:
Syscall Sysv: Add support for unreferencing callbacks

Also deduplicate callbacks by function pointer.
Function equality in Go is problematic, which is why functions are not comparable in the language spec or via reflect.Value.Equal().
For our particular use-case though I believe that comparing function pointers is good enough, since we don't need to differentiate closures based on scope variable content.

Wow! I think this is exactly what we want. The notion of slots/holes was my idea as well. It generally looks good, if these tests pass I would say LGTM

Hmm, not sure what's up with the test runners, looks like the FreeBSD runners are in a boot loop. I would like to see the tests pass for platforms/architectures I don't have access to, but they pass locally on amd64 with 1.19 / 1.20 / 1.21.

Hmm, not sure what's up with the test runners, looks like the FreeBSD runners are in a boot loop. I would like to see the tests pass for platforms/architectures I don't have access to, but they pass locally on amd64 with 1.19 / 1.20 / 1.21.

let me rebase with newest purego anyways. But I was mainly commenting that because the ubuntu 1.19.x container failed

Updated per review comments and rebased against main.

Thanks! I can reproduce the CI crashes with:
CGO_ENABLED=1 go test -shuffle=on -v -count=10

any idea? I can have a more detailed look later

This is related to callback re-use - I believe what's happening is that when the callback is re-used across goroutines it logs to the originally captured test instance, which results in logs being output to a comlpeted test run.
Either removing the log line inside the callback, or unref'ing the cb inside the callback and creating a new cb for each iteration allows the tests to pass, but this does illustrate a pitfall with callback re-use (and function equality in general) for closures.

I tested a number of scenarios, but didn't find this one - I think perhaps this means that the concept of callback re-use is flawed, since it cannot work correctly in the presence of changing variables passed into the outer scope for the callback. The below should illustrate a little more clearly.
This will work:
for i := 0; i < 10_000; i++ {
	time.Sleep(10 * time.Millisecond)

	cb := func(data uintptr) bool {
		fmt.Println(`i is increasing in scope`, i)
		return false
	}
	glib.IdleAdd(cb, 0)
}

But this will not work:
for i := 0; i < 10_000; i++ {
	time.Sleep(10 * time.Millisecond)

	update(i)
}

func update(i int) {
	cb := func(data uintptr) bool {
		fmt.Println(`i is captured from scope and not increasing`, i)
		return false
	}

	glib.IdleAdd(cb, 0)
}

We could remove this optimization while retaining manual unref'ing, or providing a separate API (e.g. purego.NewReusableCallback()) to enable re-use at the user's discretion, however the implication for our desired use-case in puregotk https://github.com/jwijenbergh/puregotk/pull/2 is that we don't have a safe way to track wrapped callbacks in the case that they might be instantiated with this kind of scope.

The latest push replaces the old unref behaviour for functions with explicit support for function pointers only (but retains unref by cb addr). By forcing users to use function pointers we can be sure of the identity of the argument passed to New/UnrefCallbackFnPtr.
Update for the puregotk side coming shortly.

Hmm, I don't have access to Windows, or any experience with win32 APIs, but from a quick search I don't see a way to unregister a callback on Windows. so maybe we just implement the unref operations as NOOPs (mostly, we should still be able to do FnPtr dedup)  for Windows.

would it be possible to implement these NOOPs?

Hmm, I don't have access to Windows, or any experience with win32 APIs, but from a quick search I don't see a way to unregister a callback on Windows. so maybe we just implement the unref operations as NOOPs (mostly, we should still be able to do FnPtr dedup) for Windows.

would it be possible to implement these NOOPs?

Rather than implement NOOPs, I moved the Unref-specific tests into a platorm-specific test file and omitted the Unref APIs from the Windows code.
On the Windows side, I implemented NewCallbackFnPtr() only, allowing callback deduplication.
I also added input validation to NewCallback(), which the sysv implementation has. This is probably not strictly required, since the syscall package will panic if the input is invalid, but this provides consistent error messaging.
We could potentially DRY this up across platforms by putting the public functions into the untagged syscall file and using some tag shenanigans for the internal platform-specific stuff, but I'm not sure that's worth the effort.

LGTM = Let's Gamble Try Merging
Thanks!

authors: jwijenbergh pdf

repo: jwijenbergh/purego


text:
Does this work with lan hosts?

I know next to nothing about nginx and network routing, so this may just be a matter of my own ignorance, but is nginx-proxy not intended to work on a host on a LAN?  I've been trying to get a vanilla deployment of this going exactly by the book using the examples (and the original blog post).  I have a local server that I can reach at hostname.local but after running through the example setup (and a dozen variations) I cannot get any subdomain.hostname.local to route.  I can reach the web service on the intended subdomain's container just fine, but not through that route.  Looking through the issues here and on docker hub it looks like this might not be possible at all or maybe Im missing something in my local DNS setup (which would be way over my head).
Anyway, my questions are:

Is this not even possible in the first place?

If it is, any suggestions on how I can troubleshoot this?

you can try if it the nginx-proxy works by temporarily adding the subdomain to the /etc/hosts file on your workstation, i.e.
# IP address of your docker host (where NGINX proxy is running on)
123.456.789.012    subdomain.hostname.local

That way you don't use the DNS for the subdomain. If that works, your DNS isn't configured properly :)

Thanks @thaJeztah for the advice.  I tried exactly that and subdomain.hostname.local indeed resolves... but it resolves to a 503 which I'm assuming means that subdomain.hostname.local is just resolving to hostname.local and not the subdomain supposedly being served by nginx?
Do I need to run the subdomain's container with -P or -p x:x ?  The container's image is def build with EXPOSE set to the contained web service's port number.

-p is not required, the NGINX proxy uses the docker private network to communicate with the container. However, if the webserver in the container is using a non-standard port, you may have to add a VIRTUAL_PORT environment variable as well for the container.

Also, you can check the logs, docker logs my-nginx-proxy-container and check if the generated NGINX config looks okay.
You should be able to copy that file out of the container using
docker cp [nginx-proxy-container-name]:/etc/nginx/conf.d/default.conf /destination/path

Then check if the content of the config file looks okay

Aha!!  I got it to work.  Our DNS is def not setup properly to handle the subdomain requests.  Temporarily adding it to my /etc/hosts like you suggested allowed me to try a few things and it worked ( I was setting VIRTUAL_HOST="justsubdomain" instead of VIRTUAL_HOST="subdomain.hostname.local").
Ok, so I've got the source narrowed down.  Now.. any chance you can tell me what I need to ask my friendly neighborhood network engineer to configure on DNS?  (Thanks so much for the tip, this is such an awesome docker image)

Basically you need a wildcard DNS server, so that [whatever].[whatever].hostname.local resolves to the IP address of your docker host.
If you're the only one that needs to use it, you could even run your own DNS server in a container, and have your workstation use that as it's primary DNS :)

Awesome, thanks again.

Good luck! And have fun with Docker :)

authors: andrewcstewart thaJeztah

repo: jwilder/nginx-proxy


text:
Alacritty randomly closes

Which operating system does the issue occur on? Linux, Fedora 30.
If on linux, are you using X11 or Wayland? X11, i3.
I'm using latest master branch. Mostly while using Vim, Alacritty randomly crashes.

Please provide backtrace for a crash. You can use coredumpctl gdb alacritty, it should give you the most recent crash.

@kchibisov Just checked again, it didn't crash. Here's the log:
[2019-10-23 21:00] [TRACE] [alacritty_terminal/src/term/mod.rs:1467] Going to: line=41, col=0
[2019-10-23 21:00] [TRACE] [alacritty_terminal/src/term/mod.rs:1467] Going to: line=42, col=0
[2019-10-23 21:00] [TRACE] [alacritty_terminal/src/term/mod.rs:1467] Going to: line=43, col=0
[2019-10-23 21:00] [TRACE] [alacritty_terminal/src/term/mod.rs:1467] Going to: line=44, col=0
[2019-10-23 21:00] [TRACE] [alacritty_terminal/src/term/mod.rs:1467] Going to: line=45, col=0
[2019-10-23 21:00] [TRACE] [alacritty_terminal/src/term/mod.rs:1467] Going to: line=46, col=0
[2019-10-23 21:00] [TRACE] [alacritty_terminal/src/term/mod.rs:1467] Going to: line=47, col=0
[2019-10-23 21:00] [TRACE] [alacritty_terminal/src/term/mod.rs:1955] Setting attribute: Reset
[2019-10-23 21:00] [TRACE] [alacritty_terminal/src/term/mod.rs:1467] Going to: line=48, col=78
[2019-10-23 21:00] [TRACE] [alacritty_terminal/src/term/mod.rs:1534] Moving forward: 11
[2019-10-23 21:00] [TRACE] [alacritty_terminal/src/term/mod.rs:1467] Going to: line=2, col=0
[2019-10-23 21:00] [TRACE] [alacritty_terminal/src/term/mod.rs:2029] Unsetting mode: BlinkingCursor
[2019-10-23 21:00] [TRACE] [alacritty_terminal/src/term/mod.rs:2063] ... unimplemented mode
[2019-10-23 21:00] [TRACE] [alacritty_terminal/src/term/mod.rs:1988] Setting mode: ShowCursor
[2019-10-23 21:00] [TRACE] [alacritty_terminal/src/term/mod.rs:2029] Unsetting mode: ShowCursor
[2019-10-23 21:00] [TRACE] [alacritty_terminal/src/term/mod.rs:1467] Going to: line=48, col=78
[2019-10-23 21:00] [TRACE] [alacritty_terminal/src/term/mod.rs:1467] Going to: line=3, col=0
[2019-10-23 21:00] [TRACE] [alacritty_terminal/src/term/mod.rs:2029] Unsetting mode: BlinkingCursor
[2019-10-23 21:00] [TRACE] [alacritty_terminal/src/term/mod.rs:2063] ... unimplemented mode
[2019-10-23 21:00] [TRACE] [alacritty_terminal/src/term/mod.rs:1988] Setting mode: ShowCursor
[2019-10-23 21:00] [TRACE] [alacritty_terminal/src/term/mod.rs:2029] Unsetting mode: ShowCursor
[2019-10-23 21:00] [TRACE] [alacritty_terminal/src/term/mod.rs:1467] Going to: line=48, col=0
[2019-10-23 21:00] [TRACE] [alacritty_terminal/src/term/mod.rs:1803] Clearing line: Right
[2019-10-23 21:00] [TRACE] [alacritty_terminal/src/term/mod.rs:1467] Going to: line=48, col=0
[2019-10-23 21:00] [TRACE] [alacritty_terminal/src/term/mod.rs:2029] Unsetting mode: BlinkingCursor
[2019-10-23 21:00] [TRACE] [alacritty_terminal/src/term/mod.rs:2063] ... unimplemented mode
[2019-10-23 21:00] [TRACE] [alacritty_terminal/src/term/mod.rs:1988] Setting mode: ShowCursor
[2019-10-23 21:00] [INFO] Goodbye

More on reproducing the error: When I get myself into #2906, pressing "w" will cause the terminal to close.

Could you repro with alacritty --config-file /dev/null?

Could you repro with alacritty --config-file /dev/null?

Probably not, using it for a while and still not see the bug. Sometime arrow keys are not usable, but it doesn't close.

Would you mind to share your config then?

Here:
window:
  dimensions:
    columns: 80
    lines: 24

  # Window padding
  padding:
    x: 2
    y: 2

  # Window decorations
  decorations: none

tabspaces: 4

scrolling:
  # How many lines of scrollback to keep,
  # '0' will disable scrolling.
  history: 10000

  # Number of lines the viewport will move for every line
  # scrolled when scrollback is enabled (history > 0).
  multiplier: 3

  # Automatically scroll to the bottom when new text is written
  # to the terminal.
  auto_scroll: false

draw_bold_text_with_bright_colors: true

# Font configuration (changes require restart)
#
# Important font attributes like antialiasing, subpixel aa, and hinting can be
# controlled through fontconfig. Specifically, the following attributes should
# have an effect:
#
# * hintstyle
# * antialias
# * lcdfilter
# * rgba
#
# For instance, if you wish to disable subpixel antialiasing, you might set the
# rgba property to "none". If you wish to completely disable antialiasing, you
# can set antialias to false.
#
# Please see these resources for more information on how to use fontconfig
#
# * https://wiki.archlinux.org/index.php/font_configuration#Fontconfig_configuration
# * file:///usr/share/doc/fontconfig/fontconfig-user.html
font:
  normal:
    family: Source Code Pro
    style: Medium

  bold:
    family: Source Code Pro
    style: Bold

  italic:
    family: Source Code Pro
    style: Italic

  size: 9

  # Offset is the extra space around each character. offset.y can be thought of
  # as modifying the linespacing, and offset.x as modifying the letter spacing.
  offset:
    x: 0
    y: 0

  # Glyph offset determines the locations of the glyphs within their cells with
  # the default being at the bottom. Increase the x offset to move the glyph to
  # the right, increase the y offset to move the glyph upward.
  glyph_offset:
    x: 0
    y: 0

# Should display the render timer
# render_timer: false

# Colors (Dracula)
colors:
  # Default colors
  primary:
    background: '0x282a36'
    foreground: '0xf8f8f2'

  # Normal colors
  normal:
    black:   '0x000000'
    red:     '0xff5555'
    green:   '0x50fa7b'
    yellow:  '0xf1fa8c'
    blue:    '0xbd93f9'
    magenta: '0xff79c6'
    cyan:    '0x8be9fd'
    white:   '0xbfbfbf'

  # Bright colors
  bright:
    black:   '0x4d4d4d'
    red:     '0xff6e67'
    green:   '0x5af78e'
    yellow:  '0xf4f99d'
    blue:    '0xcaa9fa'
    magenta: '0xff92d0'
    cyan:    '0x9aedfe'
    white:   '0xe6e6e6'

# Visual Bell
#
# Any time the BEL code is received, Alacritty "rings" the visual bell. Once
# rung, the terminal background will be set to white and transition back to the
# default background color. You can control the rate of this transition by
# setting the `duration` property (represented in milliseconds). You can also
# configure the transition function by setting the `animation` property.
#
# Possible values for `animation`
# `Ease`
# `EaseOut`
# `EaseOutSine`
# `EaseOutQuad`
# `EaseOutCubic`
# `EaseOutQuart`
# `EaseOutQuint`
# `EaseOutExpo`
# `EaseOutCirc`
# `Linear`
#
# To completely disable the visual bell, set its duration to 0.
#
visual_bell:
  animation: EaseOutExpo
  duration: 0

# Background opacity
background_opacity: 0.85

# Mouse bindings
#
# Currently doesn't support modifiers. Both the `mouse` and `action` fields must
# be specified.
#
# Values for `mouse`:
# - Middle
# - Left
# - Right
# - Numeric identifier such as `5`
#
# Values for `action`:
# - Paste
# - PasteSelection
# - Copy (TODO)
mouse_bindings:
  - { mouse: Middle, action: PasteSelection }

mouse:
  hide_when_typing: false
  # Click settings
  #
  # The `double_click` and `triple_click` settings control the time
  # alacritty should wait for accepting multiple clicks as one double
  # or triple click.
  double_click: { threshold: 300 }
  triple_click: { threshold: 300 }

  # Faux Scrollback
  #
  # The `faux_scrollback_lines` setting controls the number
  # of lines the terminal should scroll when the alternate
  # screen buffer is active. This is used to allow mouse
  # scrolling for applications like `man`.
  #
  # To disable this completely, set `faux_scrollback_lines` to 0.
  faux_scrollback: 2

  url:
    # URL launcher
    #
    # This program is executed when clicking on a text which is recognized as a URL.
    # The URL is always added to the command as the last parameter.
    launcher: xdg-open
    modifiers: Control

selection:
  semantic_escape_chars: ",│`|:\"' ()[]{}<>"

dynamic_title: true

# Style of the cursor
#
# Values for 'cursor_style':
# - Block
# - Underline
# - Beam
cursor:
  style: Block

# Live config reload (changes require restart)
live_config_reload: false

# Shell
#
# You can set shell.program to the path of your favorite shell, e.g. /bin/fish.
# Entries in shell.args are passed unmodified as arguments to the shell.
#
# shell:
#   program: /bin/bash
#   args:
#     - --login

# Key bindings
#
# Each binding is defined as an object with some properties. Most of the
# properties are optional. All of the alphabetical keys should have a letter for
# the `key` value such as `V`. Function keys are probably what you would expect
# as well (F1, F2, ..). The number keys above the main keyboard are encoded as
# `Key1`, `Key2`, etc. Keys on the number pad are encoded `Number1`, `Number2`,
# etc.  These all match the glutin::VirtualKeyCode variants.
#
# A list with all available `key` names can be found here:
# https://docs.rs/glutin/*/glutin/enum.VirtualKeyCode.html#variants
#
# Possible values for `mods`
# `Command`, `Super` refer to the super/command/windows key
# `Control` for the control key
# `Shift` for the Shift key
# `Alt` and `Option` refer to alt/option
#
# mods may be combined with a `|`. For example, requiring control and shift
# looks like:
#
# mods: Control|Shift
#
# The parser is currently quite sensitive to whitespace and capitalization -
# capitalization must match exactly, and piped items must not have whitespace
# around them.
#
# Either an `action`, `chars`, or `command` field must be present.
#   `action` must be one of `Paste`, `PasteSelection`, `Copy`, or `Quit`.
#   `chars` writes the specified string every time that binding is activated.
#     These should generally be escape sequences, but they can be configured to
#     send arbitrary strings of bytes.
#   `command` must be a map containing a `program` string, and `args` array of
#     strings. For example:
#     - { ... , command: { program: "alacritty", args: ["-e", "vttest"] } }
#
# Want to add a binding (e.g. "PageUp") but are unsure what the X sequence
# (e.g. "\x1b[5~") is? Open another terminal (like xterm) without tmux,
# then run `showkey -a` to get the sequence associated to a key combination.
key_bindings:
  - { key: V,        mods: Control|Shift,    action: Paste               }
  - { key: C,        mods: Control|Shift,    action: Copy                }

  - { key: PageUp,   mods: Control,   action: ScrollPageUp               }
  - { key: PageDown, mods: Control,   action: ScrollPageDown             }
  - { key: End,      mods: Control,   action: ScrollToBottom             }
  - { key: Home,     mods: Control,   action: ScrollToTop                }
  - { key: K,        mods: Command,   action: ClearHistory               }

  - { key: Q,        mods: Command, action: Quit                         }
  - { key: W,        mods: Command, action: Quit                         }
  - { key: Insert,   mods: Shift,   action: PasteSelection               }
  - { key: Key0,     mods: Control, action: ResetFontSize                }
  - { key: Equals,   mods: Control, action: IncreaseFontSize             }
  - { key: Subtract, mods: Control, action: DecreaseFontSize             }
  - { key: Home,                    chars: "\x1bOH",   mode: AppCursor   }
  - { key: Home,                    chars: "\x1b[H",   mode: ~AppCursor  }
  - { key: End,                     chars: "\x1bOF",   mode: AppCursor   }
  - { key: End,                     chars: "\x1b[F",   mode: ~AppCursor  }
  - { key: PageUp,   mods: Shift,   chars: "\x1b[5;2~"                   }
  # - { key: PageUp,   mods: Control, chars: "\x1b[5;5~"                   }
  - { key: PageUp,                  chars: "\x1b[5~"                     }
  - { key: PageDown, mods: Shift,   chars: "\x1b[6;2~"                   }
  # - { key: PageDown, mods: Control, chars: "\x1b[6;5~"                   }
  - { key: PageDown,                chars: "\x1b[6~"                     }
  - { key: Tab,      mods: Shift,   chars: "\x1b[Z"                      }
  - { key: Back,                    chars: "\x7f"                        }
  - { key: Back,     mods: Alt,     chars: "\x1b\x7f"                    }
  - { key: Insert,                  chars: "\x1b[2~"                     }
  - { key: Delete,                  chars: "\x1b[3~"                     }
  - { key: Left,     mods: Shift,   chars: "\x1b[1;2D"                   }
  - { key: Left,     mods: Control, chars: "\x1b[1;5D"                   }
  - { key: Left,     mods: Alt,     chars: "\x1b[1;3D"                   }
  - { key: Left,                    chars: "\x1b[D",   mode: ~AppCursor  }
  - { key: Left,                    chars: "\x1bOD",   mode: AppCursor   }
  - { key: Right,    mods: Shift,   chars: "\x1b[1;2C"                   }
  - { key: Right,    mods: Control, chars: "\x1b[1;5C"                   }
  - { key: Right,    mods: Alt,     chars: "\x1b[1;3C"                   }
  - { key: Right,                   chars: "\x1b[C",   mode: ~AppCursor  }
  - { key: Right,                   chars: "\x1bOC",   mode: AppCursor   }
  - { key: Up,       mods: Shift,   chars: "\x1b[1;2A"                   }
  - { key: Up,       mods: Control, chars: "\x1b[1;5A"                   }
  - { key: Up,       mods: Alt,     chars: "\x1b[1;3A"                   }
  - { key: Up,                      chars: "\x1b[A",   mode: ~AppCursor  }
  - { key: Up,                      chars: "\x1bOA",   mode: AppCursor   }
  - { key: Down,     mods: Shift,   chars: "\x1b[1;2B"                   }
  - { key: Down,     mods: Control, chars: "\x1b[1;5B"                   }
  - { key: Down,     mods: Alt,     chars: "\x1b[1;3B"                   }
  - { key: Down,                    chars: "\x1b[B",   mode: ~AppCursor  }
  - { key: Down,                    chars: "\x1bOB",   mode: AppCursor   }
  - { key: F1,                      chars: "\x1bOP"                      }
  - { key: F2,                      chars: "\x1bOQ"                      }
  - { key: F3,                      chars: "\x1bOR"                      }
  - { key: F4,                      chars: "\x1bOS"                      }
  - { key: F5,                      chars: "\x1b[15~"                    }
  - { key: F6,                      chars: "\x1b[17~"                    }
  - { key: F7,                      chars: "\x1b[18~"                    }
  - { key: F8,                      chars: "\x1b[19~"                    }
  - { key: F9,                      chars: "\x1b[20~"                    }
  - { key: F10,                     chars: "\x1b[21~"                    }
  - { key: F11,                     chars: "\x1b[23~"                    }
  - { key: F12,                     chars: "\x1b[24~"                    }
  - { key: F1,       mods: Shift,   chars: "\x1b[1;2P"                   }
  - { key: F2,       mods: Shift,   chars: "\x1b[1;2Q"                   }
  - { key: F3,       mods: Shift,   chars: "\x1b[1;2R"                   }
  - { key: F4,       mods: Shift,   chars: "\x1b[1;2S"                   }
  - { key: F5,       mods: Shift,   chars: "\x1b[15;2~"                  }
  - { key: F6,       mods: Shift,   chars: "\x1b[17;2~"                  }
  - { key: F7,       mods: Shift,   chars: "\x1b[18;2~"                  }
  - { key: F8,       mods: Shift,   chars: "\x1b[19;2~"                  }
  - { key: F9,       mods: Shift,   chars: "\x1b[20;2~"                  }
  - { key: F10,      mods: Shift,   chars: "\x1b[21;2~"                  }
  - { key: F11,      mods: Shift,   chars: "\x1b[23;2~"                  }
  - { key: F12,      mods: Shift,   chars: "\x1b[24;2~"                  }
  - { key: F1,       mods: Control, chars: "\x1b[1;5P"                   }
  - { key: F2,       mods: Control, chars: "\x1b[1;5Q"                   }
  - { key: F3,       mods: Control, chars: "\x1b[1;5R"                   }
  - { key: F4,       mods: Control, chars: "\x1b[1;5S"                   }
  - { key: F5,       mods: Control, chars: "\x1b[15;5~"                  }
  - { key: F6,       mods: Control, chars: "\x1b[17;5~"                  }
  - { key: F7,       mods: Control, chars: "\x1b[18;5~"                  }
  - { key: F8,       mods: Control, chars: "\x1b[19;5~"                  }
  - { key: F9,       mods: Control, chars: "\x1b[20;5~"                  }
  - { key: F10,      mods: Control, chars: "\x1b[21;5~"                  }
  - { key: F11,      mods: Control, chars: "\x1b[23;5~"                  }
  - { key: F12,      mods: Control, chars: "\x1b[24;5~"                  }
  - { key: F1,       mods: Alt,     chars: "\x1b[1;6P"                   }
  - { key: F2,       mods: Alt,     chars: "\x1b[1;6Q"                   }
  - { key: F3,       mods: Alt,     chars: "\x1b[1;6R"                   }
  - { key: F4,       mods: Alt,     chars: "\x1b[1;6S"                   }
  - { key: F5,       mods: Alt,     chars: "\x1b[15;6~"                  }
  - { key: F6,       mods: Alt,     chars: "\x1b[17;6~"                  }
  - { key: F7,       mods: Alt,     chars: "\x1b[18;6~"                  }
  - { key: F8,       mods: Alt,     chars: "\x1b[19;6~"                  }
  - { key: F9,       mods: Alt,     chars: "\x1b[20;6~"                  }
  - { key: F10,      mods: Alt,     chars: "\x1b[21;6~"                  }
  - { key: F11,      mods: Alt,     chars: "\x1b[23;6~"                  }
  - { key: F12,      mods: Alt,     chars: "\x1b[24;6~"                  }
  - { key: F1,       mods: Super,   chars: "\x1b[1;3P"                   }
  - { key: F2,       mods: Super,   chars: "\x1b[1;3Q"                   }
  - { key: F3,       mods: Super,   chars: "\x1b[1;3R"                   }
  - { key: F4,       mods: Super,   chars: "\x1b[1;3S"                   }
  - { key: F5,       mods: Super,   chars: "\x1b[15;3~"                  }
  - { key: F6,       mods: Super,   chars: "\x1b[17;3~"                  }
  - { key: F7,       mods: Super,   chars: "\x1b[18;3~"                  }
  - { key: F8,       mods: Super,   chars: "\x1b[19;3~"                  }
  - { key: F9,       mods: Super,   chars: "\x1b[20;3~"                  }
  - { key: F10,      mods: Super,   chars: "\x1b[21;3~"                  }
  - { key: F11,      mods: Super,   chars: "\x1b[23;3~"                  }
  - { key: F12,      mods: Super,   chars: "\x1b[24;3~"                  }

Have you changed terminfo to match your tabspace value? Change it back to default otherwise and retest.

Maybe you have some problem with Command(Win), since you have a binding for K and W and you've mentioned in other issue(iirc), that your K also doesn't work in vim some time.

Have you changed terminfo to match your tabspace value?

I don't understand this, so probably I didn't to it.

I use Win+K to switch between windows (i3wm), now I can reproduce this by pressing it really fast.

Closed as duplication of #2906

authors: juchiast kchibisov

repo: jwilm/alacritty


text:
Instructor fails to work with OpenRouter when using Anthropic models

What Model are you using?

[ ] anthropic/cloaude-3-sonnet
[ ] gpt-4o

Describe the bug
Instructor fails to work work with openrouter when using Anthropic.
base_url = 'https://openrouter.ai/api/v1'
client = instructor.from_openai(AsyncOpenAI(base_url=base_url, api_key={openrouter_api_key}))
client.chat.completions.create(**params, model='anthropic/claude-3-sonnet', extra_headers=headers, response_model=response_model)
The we get is:
`    ) -> BaseModel:
message = completion.choices[0].message
assert (

      len(message.tool_calls or []) == 1

    ), "Instructor does not support multiple tool calls, use List[Model] instead."

E       AssertionError: Instructor does not support multiple tool calls, use List[Model] instead.`
If
Same code as above for 'openai/gpt-4o' works perfectly for OPENAI (using openrouter) and we get a response model as expected:
client.chat.completions.create(**params, model='openai/gpt-4o', extra_headers=headers, response_model=response_model)
If you will try to use the AsyncAnthropic instead of AsyncOpenAI the error gets even weirder and there is a long stack trace, this is the outmost error, something with not reaching the proper endpoint or something.

      raise self._make_status_error_from_response(err.response) from None

E           anthropic.NotFoundError
Expected behavior
Allow to use Anthropic models over openrouter wether if it by using the openai client or anthropic (which would be better since the APIs are not identical)

@syberkitten  does instructor work with open router for other models. I tried with mixtral-8x22b-instruct, get this error
AssertionError: Instructor does not support multiple tool calls, use List[Model] instead.

I think I found a solution here https://python.useinstructor.com/examples/ollama/#ollama

same bug as https://github.com/jxnl/instructor/issues/735

@ApurvaMisra did your solution work?

I think I found a solution here https://python.useinstructor.com/examples/ollama/#ollama

Yup, this worked for me
    client = instructor.from_openai(OpenAI(       base_url="https://openrouter.ai/api/v1",       api_key=os.environ["OPENROUTER_API_KEY"],     ),     mode=instructor.Mode.JSON,     )

found MD_JSON works widely among many models

authors: ApurvaMisra scruffynerf syberkitten vikyw89 wasauce

repo: jxnl/instructor


text:
How exactly does langcc beat Knuth?

There seems to be no Web forum or mailing list, so I guess I should ask questions here?
It's well-known that any language parseable with a pushdown automaton is a deterministic context-free language. However, langcc seems to be able to generate parsers for some wider class of languages, so I'm interested in which of the results from your paper improve on the recognizing power of LR(k)/PDA?
If I wanted to make a strictly LR(1) parser generator based on your paper, which of your features/results should I ignore?

There is a Discussions tab on GitHub.
For a canonical LR(1) parser, you'll have to ignore virtually all of the innovations of the paper, notably, (i) the improved optimization procedure for LR automata (which produces coarser automata than canonical LR(1)); (ii) the CPS grammar transformation; (iii) recursive-descent actions; and (iv) per-symbol attributes.

Thanks!

authors: jzimmerman nsajko

repo: jzimmerman/langcc


text:
Make VersionInfo Hashable

Hello,
VersionInfo doesn't implement __hash__
https://github.com/scls19fr/arduino_libraries_search/blob/master/arduino_libraries_search.py
raises TypeError: unhashable type: 'VersionInfo'
This is quite close to #72
Kind regards

An other approach for hashing VersionInfo (differently than hashing it's string representation) could be to get a dict from VersionInfo but dict are not hashable (only immutable objects are hashable according https://stackoverflow.com/questions/13264511/typeerror-unhashable-type-dict).
So we can convert dict to frozenset using
def freeze(d):
    if isinstance(d, dict):
        return frozenset((key, freeze(value)) for key, value in d.items())
    elif isinstance(d, list):
        return tuple(freeze(value) for value in d)
    return d

and called __hash__ of this frozenset
Here is an example:
In [51]: v = semver.parse_version_info('1.2.3')

In [52]: d = v._asdict()

In [53]: fs = freeze(d)

In [54]: fs.__hash__()
Out[54]: -1214760729421905988

A last approach (and probably sympler) could be to get a tuple from a VersionInfo
def __hash__(self):
    return hash(self._astuple())

repo: k-bx/python-semver


text:
Add inputs.args parameter

I added inputs.args parameter to pass arbitrary options for octocov.
https://github.com/k1LoW/octocov/issues/406
There are other ways, for example adding inputs.report-path option, however octocov has many options and subcommands so inputs.args is useful I think.

@lufia Thank you!!!


text:
Whisper Fine-tuning Recipe on Aishell1

This PR supports fine-tuning whisper models using aishell1.

[ ] Fix code comments & lint errors

test (before fine-tuning)
test (after fine-tuning)
comment

medium
7.23
3.27
--epoch 10 --avg 4,  ddp

large-v2
6.56
2.47
--epoch 10 --avg 6,  deepspeed zero stage1

large-v3
6.06
2.84
--epoch 5 --avg 3,   deepspeed zero stage1

Nice work!
Would you mind sharing how much GPU memory and how long it takes to fine-tune the Whisper model?

Nice work!
Would you mind sharing how much GPU memory and how long it takes to fine-tune the Whisper model?

On a 8xA100(80GB) machine, it takes about 15 mins per epoch for large models. Since I am always set the max_duration as large as possible, I think people could fine-tune it on 24GB cards with deepspeed and smaller batch size.

    model = whisper.load_model(filename)
  File "/opt/hostedtoolcache/Python/3.8.18/x64/lib/python3.8/site-packages/whisper/__init__.py", line 147, in load_model
    dims = ModelDimensions(**checkpoint["dims"])
KeyError: 'dims'

It throws the above error while using whisper.load_model() with the checkpoint
Could you make your checkpoint compatible with whisper? For instance, you need to save dims in the resulting checkpoint.
@yuekaizhang

Sorry, I added this converion script https://huggingface.co/yuekai/icefall_asr_aishell_whisper/blob/main/convert.sh. I have uploaded a converted medium model. Would you mind trying it again? https://huggingface.co/yuekai/icefall_asr_aishell_whisper/blob/main/exp_medium/whisper-medium-aishell1-epoch-10-avg-4.pt

@yuekaizhang
Thanks! It works perfectly. I have converted it to sherpa-onnx with https://github.com/k2-fsa/sherpa-onnx/pull/565
You can find the converted model at
https://huggingface.co/csukuangfj/sherpa-onnx-whisper-medium-aishell/tree/main
You can also try it in the following huggingface space
https://huggingface.co/spaces/k2-fsa/automatic-speech-recognition-with-whisper

authors: csukuangfj marcoyang1998 yuekaizhang