Use null as access to all content-scopes

To support many (thousands) of content-scopes we have to handle this data more efficient. This means that when a user has access to all content-scope we simply set the contentScopes-field of the currentUser-object to null.
This is vastly an internal change and should be completely backwards compatible (the change in the schema is abstracted in the currentUser-Hook).

Admitedly, the data structure is confusing

Changing an Api to a possibly confusing data structure "just" for performance reasons should be avoided if possible.

Suggestions

Maybe take one step back:

what data do we need here?
if I understand correctly

a list of all scopes the user has access to (only needed if the default scope picker is used)
a list of all permissions in the currently active scope to show/hide menu items (and possibly other parts of the UI)

Maybe we can have an Api containing only the data we currently need.

@johnnyomair What do you think about this issue?

I think @thomasdax98 is right, it's really confusing that null means "has access to all content scopes"

The problem is that GraphQL doesn't support this and I can't think of a simple solution.

We could create an additional layer and return something like this:
currentUser {
  contentScopes {
    canAccessAllContentScopes // true | false
    contentScopes // Array or null
  }
}

Or we could somehow use a union type. But I believe that's what you meant with:

Split up the CurrentUser-Object (for server side permission check) and a CurrentUser-ObjectType (for graphql) which transports the relevant data in a different way

Don't transfer permissions at all to the client side and require a server call

This would result in a lot of API calls for something like the menu I suppose, so I'm not sure if this is a good idea.
Let's talk about this in this week's meeting!


Use SpanExporter instead of AzureMonitorTraceExporter and exclude pom.xml from CI

AzureMonitorTraceExporter was made package-private in the last release of OTel exporter. This was used in the build tool and is now updated to use SpanExporter instead.

API change check
API changes are not detected in this pull request.


rename cache to query, action onComplete

Proposed updates to Router APIs...
Mainly rename cache to query
Also add the onComplete API to submissions. That I brainstormed here: https://hackmd.io/@0u1u3zEAQAO0iYWVAStEvw/ry9vVctJkg

Instead of completely replacing on this release, how about we add a deprecation warning so the minor doesn't break existing apps?
/**
 * @deprecated Use `query()` instead..
 * This method will be removed on v0.15.0+
 */
export const cache = query

This will allow TS codebases at least to have a clear distinct warning on their code:

I agree with @atilafassina here. Let's keep cache available with a deprecation notice and provide query as the new option. In a few releases we can officially deprecate it, just give users some warning before we do.

If i'm not mistaken I think he did this already here?
https://github.com/solidjs/solid-router/pull/490/files#diff-ec90fda2df5f2c5fb4fdc9858fdece2ed80173595f5443fd20720df0a6623b12R233

I really like the new action api to allow for those advanced optimizations for people that are willing to put effort into manual cache management.
My only slight disappointment is that if I'm writing manual cache mutations anyways, I would like it to optimize all the way and prevent any reconciliation by making the cache update fine grained. This is still a good optimization over the default since it saves server resources and latency, but it feels like there is potential to save on data reconciliation as well without adding any more work for the developer.
What if query could be configured to use a store under the hood, and createAsyncStore can check if the thing I returned was a store and just let it through?

@devagrawal09 I've thought about this before. As you can imagine I moved stuff all around originally. The Store on the inside is awkward for hydration and serialization. It needs to upgrade to a store without running the store code on the client. There may be solutions there but finding a good solution for this with the constraints of how createResource works is pretty tough.

Aww hydration PITA strikes again
So am I hearing that this idea could be revisited in 2.0 once createAsync is the building block?

Aww hydration PITA strikes again
So am I hearing that this idea could be revisited in 2.0 once createAsync is the building block?

Maybe but it also brings with it the question of if createAsync should automatically serialize for hydration. That's more of the challenge here. We could make a change where it doesn't. Which would make these sort of things easier but we'd need to still find ways for people not using this stuff to find success.

Docs are ready:
https://github.com/solidjs/solid-docs/pull/937


fix: throw when given a non-V2 Prismic Rest API in all non-production environments

Types of changes

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

Description
This PR changes an existing check to ensure a Prismic Rest API V2 endpoint is used.
Before this PR, the client would throw an error on instantiation if it detected a non-V2 endpoint only in development. The check now happens in any environment other than production, including tests.
Detecting the production environment is done by evaluating process.env.NODE_ENV !== "production".
Checklist:

[ ] My change requires an update to the official documentation.
[x] All TSDoc comments are up-to-date and new ones have been added where necessary.
[x] All new and existing tests are passing.

🐤

Codecov Report

Merging #235 (1d8c473) into master (7d3e4c3) will not change coverage.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##           master     #235   +/-   ##
=======================================
  Coverage   99.72%   99.72%
=======================================
  Files          23       23
  Lines         361      361
  Branches       68       68
=======================================
  Hits          360      360
  Misses          1        1

Impacted Files
Coverage Δ

src/client.ts
99.51% <100.00%> (ø)

Continue to review full report at Codecov.

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


Scripts that don't directly inherit from GTA.Script won't load on separate_api builds

Just checking full name of classes' base type ignores scripts that are subclasses of GTA.Script but doesn't directly inherit from it. Some script mods use abstract classes that inherit from GTA.Script for advanced controls. Any solutions?

This should work now with https://github.com/crosire/scripthookvdotnet/commit/e1fabca9fcafc68ce6629d44e2d68169b8e33410.

All scripts I have work now with https://github.com/crosire/scripthookvdotnet/commit/e1fabca9fcafc68ce6629d44e2d68169b8e33410. If I should find scripts that still don't work with that commit, I'll reopen this issue.


flow checks all files of dependencies

See this repo. Everything is checked in, no need for npm i.
The package in the repo depends on @wunderflats/configman. configman uses tap as a devDependency for testing and requires it in the test file. The test file is not the main entry point to the module. When installing configman as a dependency tap is not installed. Thus a flow check will output:
$ flow check
node_modules/@wunderflats/configman/test/index.js:5
  5: const test = require('tap').test
                  ^^^^^^^^^^^^^^ tap. Required module not found

Found 1 error

I know I can circumvent this by using an .npmignore file, but should flow probably just use the main entry point when checking (and maybe deep requires, if the code requires something other from a dependency)?

This also happens if you install babel:
node_modules/babel-core/lib/util.js:172
172:         _i = _iterator.next();
                            ^^^^ property `next`. Property not found in
172:         _i = _iterator.next();
                  ^^^^^^^^^^^^^^^^ Array

node_modules/babel-core/lib/util.js:190
190:         _i2 = _iterator2.next();
                              ^^^^ property `next`. Property not found in
190:         _i2 = _iterator2.next();
                   ^^^^^^^^^^^^^^^^^ Array

node_modules/babel-generator/lib/generators/jsx.js:73
 73:       _i = _iterator.next();
                          ^^^^ property `next`. Property not found in
 73:       _i = _iterator.next();
                ^^^^^^^^^^^^^^^^ Array

node_modules/babel-generator/lib/generators/statements.js:256
256:         _i = _iterator.next();
                            ^^^^ property `next`. Property not found in
256:         _i = _iterator.next();
                  ^^^^^^^^^^^^^^^^ Array

node_modules/babel-types/lib/index.js:170
170:         _i = _iterator.next();
                            ^^^^ property `next`. Property not found in
170:         _i = _iterator.next();
                  ^^^^^^^^^^^^^^^^ Array

node_modules/babel-types/lib/index.js:206
206:         _i2 = _iterator2.next();
                              ^^^^ property `next`. Property not found in
206:         _i2 = _iterator2.next();
                   ^^^^^^^^^^^^^^^^^ Array

node_modules/babel-types/lib/index.js:286
286:       _i3 = _iterator3.next();
                            ^^^^ property `next`. Property not found in
286:       _i3 = _iterator3.next();
                 ^^^^^^^^^^^^^^^^^ Array

node_modules/babel-types/lib/index.js:505
505:       _i5 = _iterator5.next();
                            ^^^^ property `next`. Property not found in
505:       _i5 = _iterator5.next();
                 ^^^^^^^^^^^^^^^^^ Array

node_modules/babel-types/lib/index.js:530
530:       _i6 = _iterator6.next();
                            ^^^^ property `next`. Property not found in
530:       _i6 = _iterator6.next();
                 ^^^^^^^^^^^^^^^^^ Array

This should not be a problem since flow checks only direct and transitive dependencies.
This probably can be closed.
/cc @vkurchatkin


keyboard avoiding in nav stack

seems ok on ios and android
@keybase/react-hackers

@keybase/react-hackers bump

weird, this works for me. i guess i'll remove it since it works normally on android

@cjb please retest on android


change startup parsing to eval

done for similar reason as 2e366792c15eba443cea2b7ea38abf396d9f9c31
I'm not sure if anything is lost with not using exec env
All Submissions:

[x] Have you ensured there aren't other open Pull Requests for the same update or change?
[x] Have you created a new branch for your changes and PR from that branch and not from your master branch?
[x] Have you added an explanation of what your changes do and why you'd like us to include them?

how did this get created on my fork... ghcli is great, when it works


Be able to add parameters to the data-scrollto

Be able to add parameters to the [data-scrollto]
The idea would be to be able to redefine the offset or animations (which is taken care of by the library we use). E.g :

content

Released in v2.1.1.


Update fontawesome to latest version of 4

Update font awesome to latest of release of version 4

@maximest-pierre thanks bro. LGTM

Why update to version 4? Version 5 is out.

Its a drop in replacement instead of redoing a some of the code. There is also not that much to gain from upgrading to 5 right now. I would wait for a complete redesign before upgrading to version 5.

@maximest-pierre if my PR and your PR in this comment merged. it shouldnt break lbry.io page guys ?.

I'll review this by the end of the week.

@tzarebczan I hope if this PR merge . doesnt affect or broke my PR. because i import Font awesome to the layout/basic.php


Unexpected error : read failed :EISDIR(is a directory)

Preparation

[X] I tested the latest release
[X] I looked at other issues (even the closed ones)
[X] I read the Troubleshooting Guide

FGO server
NA
FGA build number
1611
Describe the bug
it is unable to pick the support servant
Video
this also happens when i didnt record bt
https://user-images.githubusercontent.com/99825070/154316299-3a9eb28e-92d1-4db7-9627-ab3cb793343d.mp4
w
Device model
oppo r17
Android version
10
Screen size
not sure(1080x2340)
RAM
6GB

could you have instructions on how i can do the first one i am not very familiar

Just upload some screenshots from a file explorer like this

like this?

Delete the extra Skadi folders, remove the support folder inside of "Skadi" and choose the parent folder of "support" in FGA.
In my case "Fate-Grand-Automata" was selected and contains a support folder with "servant", "ce" and "friend" folders inside.

thank for your quick replies


fix build break in Android rpc

fix build break in android_rpc

I have a same pr, today

Thanks @euntaik @new-TonyWang ! This is merged as the change is useful. @new-TonyWang please followup in your new pr and let us rebase and get the rest improvements in


Implement propagateMessages in MessageMixin to fix ControlMessageProcessor

As a developer, I want to use the ControlMessageProcessor to propagate messages to controls without databinding. In order for that to work, controls must implement a propagateMessages function.
However, a refactoring in 2016 removed that bit of functionality from UI5's standard controls, leaving message processing only working with a databinding: https://github.com/SAP/openui5/commit/344286249226e6877ef27fa6cb374908960dc242
Please fix this by adding an implementation for propagateMessages to MessageMixin, so messaging works as documented (and as before the regression 6 years ago). To me, it looks like you should be able to reuse nearly everything inside the already existing refreshDataState method, so this wouldn't even be a huge effort: https://github.com/SAP/openui5/blob/master/src/sap.ui.core/src/sap/ui/core/message/MessageMixin.js#L37-L79
Thank you for considering to fix this long-standing bug!
I can also provide a small PR to fix this myself and get the behavior restored in a timely manner.
Kind regards
Lukas

As discussed via phone:
The preferred way is to use messaging in combination with data binding but we also agree, without data binding it's not working as before anymore.
Since you're not relying on a fix for your use-case, we need to discuss first, if we want to re-enable the messaging for usage without data binding. If not we need to adjust at least the documentation Validation Messages (at least the section "Manually Created Messages" does not work as described anymore).
We prepared the following change as base for further discussions: [FIX] MessageMixin: propagateMessage implementation missing


Load balancer Health Probe port needs clarification.

In the section of this document where you talk about creating the health probe for the load balancer you state "Set to an available TCP port. This port requires an open firewall port. Use the same port you set for the health probe at the firewall."  This is very misleading.  It cannot be a TCP port that is in use or assigned. so please clarify this statement.  It will reduce the number of support cases that you get because it would have prevented mine.

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

ID: af26cb8a-f7a0-291b-7ac3-e38f679df4ba
Version Independent ID: dd04d12d-05cb-6fb4-4a2c-ef85ebb15d0e
Content: SQL Server FCI - Azure Virtual Machines
Content Source: articles/virtual-machines/windows/sql/virtual-machines-windows-portal-sql-create-failover-cluster.md
Service: virtual-machines-sql
GitHub Login: @MikeRayMSFT
Microsoft Alias: mikeray

Thanks for the feedback! We are currently investigating and will update you shortly.

@rvahaver I have assigned the issue to the content author to investigate further and update the doc as appropriate. Thanks.

@rvahaver - thank you for this submission, I'm submitting PR #73958 to clarify the instruction. Let us know if this helps.
#please-close


Enable intellisense in IDE

Is your feature request related to a problem? Please describe.
One problem is that herbsJs doesn't have type declaration files or JsDocs, which means we don't have intellisense in any of the libs or glues.
Describe the solution you'd like
We can insert .d.ts type declaration files to enable intellisense, at the same time these files become documentation.
This makes it easier to know which methods can be called and what they return.
Describe alternatives you've considered
We can also use DefinitelyTyped, where we can leave the type declarations in a separate repository, example: @types/herbs
Or add a JsDocs header to the functions we want to document.
Additional context
Example:

TS to JsDoc conversion

i prefer use JSdocs since it already document the code


runtime/internal/atomic: on Linux/ARM, support kernel without CONFIG_KUSER_HELPERS?

On Linux/ARM, we use the atomic operations provided by the kernel. (https://github.com/torvalds/linux/blob/master/arch/arm/kernel/entry-armv.S#L941)
This can be configured with CONFIG_KUSER_HELPERS in the kernel. On some machine, this option may not be enabled.
Should we support machines without this option enabled? Maybe only on GOARM=7, where the machine has atomic instructions? And keep relying on kernel helpers on older machines?
See also issue #23787.
cc @rsc @minux @davecheney

The documentation for KUSER_HELPERS says "Warning: disabling this option may break user programs." Reading between the lines a bit, it seems like this config option should only be disabled in tightly integrated embedded situations where you control the software from top to bottom and know that nothing uses the helpers. It doesn't seem like it should be disabled for a general-purpose kernel. Given this, I don't think Go should be working around this config option.

Thanks, @aclements. I agree. Closing.

@aclements, @cherrymui, the documentation for CONFIG_KUSER_HELPERS also state:

However, the fixed address nature of these helpers can be used by ROP (return orientated programming) authors when creating exploits.

Taken from here: https://cateee.net/lkddb/web-lkddb/KUSER_HELPERS.html
I believe that's the reason our security policy is to disable it. Does that mean that our security policy is in conflict with running go binaries? Is there any workaround?

CONFIG_KUSER_HELPERS is controlled by GRKERNSEC_OLD_ARM_USERLAND, which I have explicitly disable precisely because of the exploit possibility that @Risca mentions.
I have found that the protobuffer project had a similar issue with dependency on CONFIG_KUSER_HELPERS; and that redhat issued a patch to remove that dependency: https://gist.github.com/BennettSmith/7111094
Perhaps you would reconsider your decision to close this issue? I am very interested in running golang programs with a kernel that has been secured by disabling CONFIG_KUSER_HELPERS.

Related pull request for protobuf: google/protobuf#2301

GRKERNSEC_OLD_ARM_USERLAND is also documented as causing problems: "It's recommended that you try without this option enabled first, and only enable it if your userland does not boot (it will likely fail at init time)."
Has the C toolchain (gcc/clang and libc in particular) moved away from using these helpers?
There are good technical reasons for using these helpers: because of the myriad subtleties around the support for, performance of, and lack of forward-compatibility of ARM memory barriers, the kernel is in the best position to figure out what the right barriers are. We aren't simply using them out of convenience. But, if the C toolchain has figured out a good way to handle the barriers in user space, we could see what it's doing.

@aclements: I see, thanks for this information. I do not know if the toolchain uses the helpers or not.

@aclements, you cannot have KUSER_HELPERS enabled without also enabling GRKERNSEC_OLD_ARM_USERLAND. GRKERNSEC_OLD_ARM_USERLAND is listed as a dependency to KUSER_HELPERS in our kernel.
Symbol: KUSER_HELPERS [=n]
...
Depends on: MMU [=y] && (!CPU_V6 [=n] && !CPU_V6K [=n] && !CPU_V7 [=y] || GRKERNSEC_OLD_ARM_USERLAND [=n])

So, in order for us to use grsecurity and golang, we would need to enable GRKERNSEC_OLD_ARM_USERLAND which, as you pointed out, is not really recommended. I feel like we're stuck between a rock and a hard place.
I don't know the state of C toolchains regarding this. I wish I had the time to keep up.
I fully understand that there is a really valid use case for the kernel user helpers. Unfortunately for us, it also creates an incompatibility.
Could this possibly be made into a compiler option?

Could this possibly be made into a compiler option?

It's all in assembly, so no compiler option. A build tag might be more appropriate, if we end up with it.
If we go this way, would it be enough if we only do this on ARMv7? As @aclements mentioned, a good reason to use the kernel helper is not to dealing with the complexity of various incompatible memory barriers. If we do it on ARMv7 only, I think it is more feasible.

I am mainly interested in ARM7.

For what it's worth, I checked what GCC does.  It looks like if GCC is compiled with -march=armv6 or higher, it inlines the compare-and-exchange.  With a lower -march value, it calls the kernel entry point unconditionally.  This is based on compiling
_Bool f(int *p, int old, int new) {
  return __atomic_compare_exchange_n(p, &old, new, 0, __ATOMIC_ACQ_REL, __ATOMIC_RELAXED);
}

In principle we could check at run time which type of processor we were on, and select the compare-and-exchange implementation accordingly.  But of course we would prefer to avoid that because it is more complex.
I don't think we should use build tags.
I don't see any good solution here.  At least not until we can assume a sufficiently new ARM processor.

Let me change that a bit; I am only interested in ARM7. So if there is a resonable way to do this for ARM7, I would be very happy if you would consider it.

I think we can do this for ARMv7, by just testing runtime.goarm. It shouldn't be too complicated. I'll try making a CL.

+1 for issuing native instructions.
https://www.kernel.org/doc/Documentation/arm/kernel_user_helpers.txt states:

User space is expected to bypass those helpers and implement those things
inline (either in the code emitted directly by the compiler, or part of
the implementation of a library call) when optimizing for a recent enough
processor that has the necessary native support, but only if resulting
binaries are already to be incompatible with earlier ARM processors due to
usage of similar native instructions for other things.

This seems to be in line with the behavior in GCC @ianlancetaylor described.
Chromium also removed dependence on KUSER_HELPERS https://codereview.chromium.org/1840203004, relying on GCC intrinsics instead.

musl libc can also be investigated. (here, here and here are some pointers to related codes. )

@frepe360, or anyone interested, could you try CL https://golang.org/cl/94076 (which depends on CL https://golang.org/cl/93637), to make sure it works on ARMv7 machines without the kernel helpers? I don't have the environment to test. Thanks.

@cherrymui, of course, no problem. But I don't have access to it for a few days.
Until then; I understand that this is patch, correct? I have no experience in building a golang compiler. Can you explain what I need to do in order to test these changes?

@frepe360 thank you!
The easiest way is probably:
$ git clone https://go.googlesource.com/go # check out Go source tree, if not already done
$ cd go

Find the "DOWNLOAD" button on the webpage https://golang.org/cl/94076, click and copy the first command (currently as below),
$ git fetch https://go.googlesource.com/go refs/changes/76/94076/2 && git checkout FETCH_HEAD

Then build and test:
$ cd src
$ ./all.bash

The last step will probably take a while (hopefully).

@cherrymui Ok, that's not going to be a problem.

@cherrymui, just to be perfectly clear; I build this compiler according to your instructions. Then I compile a helloworld.go program with my homebuilt compiler, and then I try to run the resulting helloworld program on an ARM7 with my specific kernel configuration.
Correct?

@frepe360 the instruction above was to build natively on ARM machine. It will also work for cross-compilation. Once you build the compiler as above, just do
$ GOARCH=arm GOOS=linux GOARM=7 /path/to/new/go build helloworld.go

If you could try some programs more than a helloworld, that will be great. Thanks!

Building Go toolchain1 using /usr/lib/go-1.6.

Building Go toolchain2 using go_bootstrap and Go toolchain1.
Building Go toolchain3 using go_bootstrap and Go toolchain2.
Building packages and commands for linux/arm.
Testing packages.
ok      archive/tar     0.786s
ok      archive/zip     35.433s
ok      bufio   3.822s
ok      bytes   9.887s
ok      compress/bzip2  0.827s
ok      compress/flate  8.000s
ok      compress/gzip   0.187s
ok      compress/lzw    0.063s
ok      compress/zlib   0.204s
ok      container/heap  0.090s
ok      container/list  0.060s
ok      container/ring  0.133s
ok      context 1.027s
ok      crypto  0.053s
ok      crypto/aes      0.116s
ok      crypto/cipher   0.105s
ok      crypto/des      0.138s
ok      crypto/dsa      0.104s
ok      crypto/ecdsa    2.437s
ok      crypto/elliptic 0.386s
ok      crypto/hmac     0.028s
ok      crypto/md5      0.039s
ok      crypto/rand     0.627s
ok      crypto/rc4      0.849s
ok      crypto/rsa      1.609s
ok      crypto/sha1     0.063s
ok      crypto/sha256   0.064s
ok      crypto/sha512   0.073s
ok      crypto/subtle   0.050s
ok      crypto/tls      13.494s
ok      crypto/x509     21.999s
ok      database/sql    1.493s
ok      database/sql/driver     0.054s
ok      debug/dwarf     0.129s
ok      debug/elf       0.177s
ok      debug/gosym     0.090s
ok      debug/macho     0.049s
ok      debug/pe        0.074s
ok      debug/plan9obj  0.025s
ok      encoding/ascii85        0.068s
ok      encoding/asn1   0.086s
ok      encoding/base32 0.046s
ok      encoding/base64 0.150s
ok      encoding/binary 0.055s
ok      encoding/csv    0.082s
ok      encoding/gob    0.490s
ok      encoding/hex    0.125s
ok      encoding/json   4.820s
ok      encoding/pem    0.152s
ok      encoding/xml    0.380s
ok      errors  0.041s
ok      expvar  0.065s
ok      flag    0.836s
ok      fmt     0.892s
ok      go/ast  0.063s
ok      go/build        2.219s
ok      go/constant     0.036s
ok      go/doc  0.859s
ok      go/format       0.087s
ok      go/importer     0.826s
ok      go/internal/gccgoimporter       0.150s
ok      go/internal/gcimporter  3.134s
ok      go/internal/srcimporter 6.119s
ok      go/parser       0.346s
ok      go/printer      3.166s
ok      go/scanner      0.078s
ok      go/token        0.231s
ok      go/types        9.519s
ok      hash    0.030s
ok      hash/adler32    1.196s
ok      hash/crc32      0.056s
ok      hash/crc64      0.036s
ok      hash/fnv        0.022s
ok      html    0.027s
ok      html/template   0.426s
ok      image   1.251s
ok      image/color     0.222s
ok      image/draw      0.564s
ok      image/gif       5.666s
ok      image/jpeg      2.160s
ok      image/png       0.388s
ok      index/suffixarray       0.095s
ok      internal/cpu    0.037s
ok      internal/poll   0.168s
ok      internal/singleflight   0.082s
ok      internal/trace  18.736s
ok      io      0.123s
ok      io/ioutil       0.065s
ok      log     0.084s
ok      log/syslog      1.407s
ok      math    0.057s
ok      math/big        25.209s
ok      math/bits       0.103s
ok      math/cmplx      0.039s
ok      math/rand       2.350s
ok      mime    0.109s
ok      mime/multipart  5.509s
ok      mime/quotedprintable    1.612s
ok      net     5.359s
ok      net/http        22.371s
ok      net/http/cgi    3.747s
ok      net/http/cookiejar      0.087s
ok      net/http/fcgi   0.082s
ok      net/http/httptest       0.420s
ok      net/http/httptrace      0.038s
ok      net/http/httputil       0.539s
ok      net/http/internal       0.035s
ok      net/internal/socktest   0.028s
ok      net/mail        0.092s
ok      net/rpc 0.219s
ok      net/rpc/jsonrpc 0.115s
ok      net/smtp        0.313s
ok      net/textproto   0.072s
ok      net/url 0.150s
ok      os      1.399s
ok      os/exec 2.843s
ok      os/signal       6.875s
ok      os/user 0.044s
ok      path    0.035s
ok      path/filepath   0.245s
ok      reflect 1.489s
ok      regexp  1.782s
ok      regexp/syntax   6.697s
ok      runtime 138.645s
ok      runtime/debug   0.085s
ok      runtime/internal/atomic 0.774s
ok      runtime/internal/sys    0.058s
ok      runtime/pprof   16.114s
ok      runtime/pprof/internal/profile  0.063s
ok      runtime/trace   26.836s
ok      sort    1.100s
ok      strconv 4.799s
ok      strings 2.449s
ok      sync    1.576s
ok      sync/atomic     0.673s
ok      syscall 0.251s
ok      testing 1.506s
ok      testing/quick   1.433s
ok      text/scanner    0.042s
ok      text/tabwriter  0.084s
ok      text/template   4.087s
ok      text/template/parse     0.097s
ok      time    8.371s
ok      unicode 0.134s
ok      unicode/utf16   0.092s
ok      unicode/utf8    0.149s
ok      vendor/golang_org/x/crypto/chacha20poly1305     2.369s
ok      vendor/golang_org/x/crypto/chacha20poly1305/internal/chacha20   0.018s
ok      vendor/golang_org/x/crypto/cryptobyte   0.097s
ok      vendor/golang_org/x/crypto/curve25519   1.885s
ok      vendor/golang_org/x/crypto/poly1305     0.024s
ok      vendor/golang_org/x/net/http2/hpack     0.049s
ok      vendor/golang_org/x/net/idna    0.040s
ok      vendor/golang_org/x/net/lex/httplex     0.034s
ok      vendor/golang_org/x/net/nettest 2.943s
ok      vendor/golang_org/x/net/proxy   0.044s
ok      vendor/golang_org/x/text/transform      0.046s
ok      vendor/golang_org/x/text/unicode/norm   0.024s
ok      cmd/addr2line   13.561s
ok      cmd/api 0.099s
ok      cmd/asm/internal/asm    4.143s
ok      cmd/asm/internal/lex    0.035s
go build cmd/compile/internal/gc: /home/ubuntu/src/go/pkg/tool/linux_arm/compile: signal: killed
go build cmd/compile/internal/ssa: /home/ubuntu/src/go/pkg/tool/linux_arm/compile: signal: killed
ok      cmd/compile     344.411s
FAIL    cmd/compile/internal/gc [build failed]
FAIL    cmd/compile/internal/ssa [build failed]
ok      cmd/compile/internal/syntax     0.101s
ok      cmd/compile/internal/test       0.052s [no tests to run]
ok      cmd/compile/internal/types      0.043s
ok      cmd/cover       50.191s
ok      cmd/doc 1.463s
ok      cmd/fix 261.314s
ok      cmd/go  30.287s
ok      cmd/go/internal/cache   4.047s
ok      cmd/go/internal/generate        0.066s
ok      cmd/go/internal/get     0.635s
ok      cmd/go/internal/load    0.046s
ok      cmd/go/internal/work    0.174s
ok      cmd/gofmt       0.482s
ok      cmd/internal/buildid    4.004s
ok      cmd/internal/dwarf      0.028s
ok      cmd/internal/edit       0.027s
ok      cmd/internal/goobj      5.426s
ok      cmd/internal/obj        0.026s
ok      cmd/internal/obj/arm64  0.053s
ok      cmd/internal/obj/x86    20.844s
ok      cmd/internal/objabi     0.021s
ok      cmd/internal/src        0.022s
ok      cmd/internal/test2json  1.697s
ok      cmd/link        15.828s
ok      cmd/link/internal/ld    166.859s
ok      cmd/nm  28.347s
ok      cmd/objdump     16.980s
ok      cmd/pack        15.810s
ok      cmd/trace       0.121s
ok      cmd/vendor/github.com/google/pprof/internal/binutils    0.109s
ok      cmd/vendor/github.com/google/pprof/internal/driver      13.971s
ok      cmd/vendor/github.com/google/pprof/internal/elfexec     0.031s
ok      cmd/vendor/github.com/google/pprof/internal/graph       0.688s
ok      cmd/vendor/github.com/google/pprof/internal/measurement 0.035s
ok      cmd/vendor/github.com/google/pprof/internal/report      0.129s
ok      cmd/vendor/github.com/google/pprof/internal/symbolizer  0.096s
ok      cmd/vendor/github.com/google/pprof/internal/symbolz     0.110s
ok      cmd/vendor/github.com/google/pprof/profile      0.935s
ok      cmd/vendor/github.com/ianlancetaylor/demangle   0.194s
ok      cmd/vendor/golang.org/x/arch/arm/armasm 0.214s
ok      cmd/vendor/golang.org/x/arch/arm64/arm64asm     1.728s
ok      cmd/vendor/golang.org/x/arch/ppc64/ppc64asm     0.064s
ok      cmd/vendor/golang.org/x/arch/x86/x86asm 1.892s
ok      cmd/vet 21.210s
ok      cmd/vet/internal/cfg    0.080s
2018/02/16 20:36:23 Failed: exit status 1

(This was done on an ARM7, a raspberry pi. It does not have my "special" kernel.)

go build cmd/compile/internal/gc: /home/ubuntu/src/go/pkg/tool/linux_arm/compile: signal: killed
go build cmd/compile/internal/ssa: /home/ubuntu/src/go/pkg/tool/linux_arm/compile: signal: killed

I guess they are OOM'd, or timeout (which is possible on raspberry pi). Anyway, these are just tests, now you should already have the compiler built. You can use this new Go toolchain to build helloworld and run on the device with the special kernel. Thanks!

Ok, no problem. I'll let you know on monday.

The helloworld build with the compiler that I build according to your instructions, does NOT segfault on my kernel. The helloworld built with the regular compilar, DOES segfault:
/tmp/nfs # ./helloworld-arm7
Segmentation fault
/tmp/nfs # ./helloworld-ARM7-new-go-compiler
hello world
/tmp/nfs #

I assume that this is progress?

The helloworld built with the compiler that I build according to your instructions, does NOT segfault on my kernel. The helloworld built with the regular compiler, DOES segfault:
/tmp/nfs # ./helloworld-arm7
Segmentation fault
/tmp/nfs # ./helloworld-ARM7-new-go-compiler
hello world
/tmp/nfs #

I assume that this is progress?

Thanks, @frepe360! This is great.


Overcompilation with incremental, mixed Java/Scala file edits in 1.9.0-RC1

This is a follow up to this issue and the fix for the related zinc issue.  I took jdsalchow's minimum repro repo, I set the sbt version to 1.3.13 (known working version from our affected project), and things worked as normal:
sbt:compile_loop> compile
[info] Compiling 3 Scala sources and 5 Java sources to /CCL-Repos/compile_loop/target/scala-2.13/classes ...
[info] Non-compiled module 'compiler-bridge_2.13' for Scala 2.13.6. Compiling...
[info]   Compilation completed in 8.224s.
[success] Total time: 12 s, completed May 3, 2023, 2:36:45 PM

I edited A.scala and ABase.java (just whitespace changes, no real code edits) and saw:
sbt:compile_loop> compile
[info] Compiling 1 Scala source to /CCL-Repos/compile_loop/target/scala-2.13/classes ...
[info] Compiling 1 Scala source and 1 Java source to /CCL-Repos/compile_loop/target/scala-2.13/classes ...
[success] Total time: 1 s, completed May 3, 2023, 2:37:04 PM

Which seems fine.
Then I updated the sbt version to 1.9.0-RC1.  I cleaned the repo and the first compile was the same as before:
sbt:compile_loop> compile
[info] compiling 3 Scala sources and 5 Java sources to /CCL-Repos/compile_loop/target/scala-2.13/classes ...
[info] Non-compiled module 'compiler-bridge_2.13' for Scala 2.13.6. Compiling...
[info]   Compilation completed in 9.728s.
[success] Total time: 12 s, completed May 3, 2023, 2:38:16 PM

But after the non-code whitespace edits I saw:
sbt:compile_loop> compile
[info] compiling 1 Scala source and 1 Java source to /CCL-Repos/compile_loop/target/scala-2.13/classes ...
[info] compiling 1 Scala source and 1 Java source to /CCL-Repos/compile_loop/target/scala-2.13/classes ...
[info] compiling 1 Scala source and 1 Java source to /CCL-Repos/compile_loop/target/scala-2.13/classes ...
[info] compiling 3 Scala sources and 5 Java sources to /CCL-Repos/compile_loop/target/scala-2.13/classes ...
[success] Total time: 1 s, completed May 3, 2023, 2:38:30 PM

It's now invalidating all Scala and Java files and recompiling the whole source tree.  For this small repo that only takes a few seconds, but for our repo it takes 90 seconds or more.  Since things were working as expected in 1.3.13 this seems like a regression.
Editing one Scala file and one Java file seems necessary to trigger the issue.  If I modify just one type or the other it compiles just the changed files.

@SethTisue Would you mind to move this issue to Zinc repo?
By the way, I am unfamiliar with how Github works, but would it be possible to grant me the privilege to close / move issues around? So I don't have to ping you over and over again for these chores.


DRILL-7196: Queries are still runnable on disabled plugins

Storage client is not created anymore for disabled plugins
GET "/storage/{name}.json" endpoint changed to work with
plugin configuration directly, without client instantiation.
It have increased UI responsivity.
Hbase and Mongo base test classes refactored to honor enabled
plugin attribute
Fixed path constructor for Mongo test data-sets:
Now it is cross-platform
Fixed test json files format which using plugin definitions
Code cleanup

For the problem description please check DRILL-7196.

+1, LGTM.


Dataset size is showing size : 0

I have created a pdbs folder containing .pdb files under the afdbreps_l-256_plddt_80 folder and similarly created a genie2run folder under the run folder with a file called configuration, whose value is the same as the example/configuration. when running the python script python genie/train.py --devices 1 --num_nodes 1 --config runs/genie2run/configuration, it throwing error saying Dataset size : 0. And i have 15gb memory, would i able to run the codebase , or i should need to update the memory.

You will have to specify the dataset directory in the configuration e.g.
dataDirectory data/afdbreps_l-256_plddt_80/pdbs


Introspection warnings for unsupported features guide

Create a guide for Introspection warnings for unsupported features
Link out to "Introspection warnings for unsupported features" from Getting Started with an existing guide

Duplicate of: https://github.com/prisma/docs/issues/4425


after SVM train how to make trainer become object_detector

this is svm train example
https://github.com/davisking/dlib/blob/master/examples/svm_c_ex.cpp
after trainer.train(samples, labels) i want to make it become object detect include slider window
how to do it?
load_image_dataset -> svm_c_trainer -> detector

this is my tracing maybe this is a method
https://www.mediafire.com/view/fajm30lcmkjiuip/svm_image_scanner_type.png


Use describe tags so that soft tags are used

git describe only uses annotated tags.
It therefore prints incorrect version when new soft tags are created.
--tags arg fixes the problem.
✔ ~/GOHOME/src/istio.io/istio [fix_version L|…57⚑ 42]
20:50 $ git describe
1.1.6-936-g4a03ec440
✔ ~/GOHOME/src/istio.io/istio [fix_version L|…57⚑ 42]
20:50 $ git describe --tags
1.2.0-rc.1-19-g4a03ec440

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: mandarjog
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

bin/OWNERS [mandarjog]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@mandarjog: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/integ-mixer-k8s-presubmit-tests.sh
1e220c673ff2aeb57880116a9e891df2b6933eac
link
/test integ-mixer-k8s-presubmit-tests-master

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: mandarjog, sdake
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

bin/OWNERS [mandarjog,sdake]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


Reply to this email directly, view it on GitHub, or unsubscribe.


[WON'T FIX[ dom-commchannel: Add 'current' to communication channels

To indicate whether a communication channel is currently in use

Won't fix - this is only example code.  Sander made the change in his app's local copy of this module.


How to test multiple resources of the same type?

Hi, and thank you for your work on this tool! Just getting started with it, and running into a (possibly obvious) issue I cannot figure out. How do I write tests for specific instances of a resource?
Example:
The repository for our project contains different TF files, for different bits of the infra. Amongst these, there are two, unrelated to each other, azurerm_storage_account resources. How do I write tests that target each specific instance? I have tried the following:
Given I have azurerm_storage_account defined
When it contains name
Then its value must match the "resourceTwo" regex

Even though I have a "resourceTwo" resource, this fails because it matches the name on "resourceOne" first.
I have also tried the following variations:
Given I have resourceTwo resource defined/configured
Given I have azurerm_storage_account resourceTwo defined/configured

but all of those fail. I feel as if I am missing something obvious, and was not able to find an example that covers this situation... How do I do this?
Thanks in advance!

Hi @eugeneromero,
Thanks for trying the tool !
The idea was, terraform-compliance will enforce same/similar standards/checks to all same resource_types, instead of an individual resource. So, assuming you are trying to enforce naming standards to these two resources, why not doing it with ;
Given I have azurerm_storage_account defined
When it contains name
Then its value must match the 'resource.*' regex

Of course this is just a different approach, may not fulfil what you want to do.
For the specific case that you have - which is creating a Scenario specific for a resource - we need to add a new step like ;
Given I have azurerm_storage_account defined
When its name is resourceTwo                   <--- New step
Then ....

I must agree this kind of an approach will have pros and cons both.
Can you give a bit more context about the test you want to write ?

hey @eerkunt, thanks for getting back to me :)
My idea was something along the lines of what you propose. My final goal (and please bear with me if my understanding of the tool is flawed) was to have a 1:1 correlation between tests and TF resources. So basically, for every resource I have declared, have a corresponding test, sort of like a unit test that devs can run in their workstation before deploying to Azure. Our pipeline already handles Integration testing (by means of InSpec), so I was hoping to use tf-compliance as a sort of unit testing tool, in addition to compliance.
Extending my original example, say one of my storage accounts has a container which must be of type private, but the other one has one of type public. Here, an all encompassing test would just not do the trick for me.
Is my scenario valid, or have I misunderstood at a deeper level the usage of tf-compliance? :)

Well, if anyone has problems with how the terraform-compliance should be used, then it is a problem we need to fix :)
Gladly, you got it right. terraform-compliance can be used as a unit-tester, yes, but it is more used - as I see in the market - as a compliance-as-code tool against terraform. Thus, instead of defining tests for a specific resource, defining compliance rules against that resource type is a more common use case.
I am happy to extend the tool to have tests against individual resources features along with tests against individual resource types.
Will implement
When its name is resourceTwo

on the next release. Possibly in few hours.

Glad to hear! Thank you very much! Look forward to testing it out.

I will also add, there seems to be two different names you could leverage, either the terraform resource name, or the azure resource name. Like so:
resource "azurerm_storage_container" "terraform_resource_name" {
  name = "azure_resource_name"
  resource_group_name = "my_rg"
}

In my opinion, using the terraform_resource_name as an identifier would make more sense. These names are (for the most part) unique across a Terraform repository.
In our repos, the azure names are many times generated on-the-fly by adding together some predefined strings, and (although we don't use it) I understand TF has the capability of generating random names (to maintain name-uniqueness in Az). So at first glance, it does not seem like it would make too much sense to use the azure name as the When matcher. Worst case scenario the name would not be known before creating the resource, defeating the purpose of TDD.
Just a thought :)

I am planning to add both. Enable every possibility :)

terraform-compliance 1.0.19 has this filtering capability (fe84712b02fde9884a5e328d4f375dbc9297706b)
Here is an example  about it. Can you have a look and let me know if this is the thing that you wanted ?
Feature: Resource Filtering example

  Scenario Outline: Ensure that extra tags are defined and match regex for S3 Buckets
    Given I have AWS S3 Bucket defined
    When its address is aws_s3_bucket.s3_bucket_prod
    And it contains tags
    Then it must contain <tag_keys>
    And its value must match the "<pattern>" regex

    Examples:
      | tag_keys            | pattern                   |
      | Data Classification | ^PRIVATE$                 |
      | Data Residency      | ^EU$                      |

  Scenario Outline: Ensure that extra tags are defined and match regex for S3 Buckets
    Given I have AWS S3 Bucket defined
    When its name is my-s3-bucket
    And it contains tags
    Then it must contain <tag_keys>
    And its value must match the "<pattern>" regex

    Examples:
      | tag_keys            | pattern                   |
      | Data Classification | ^PRIVATE$                 |
      | Data Residency      | ^EU$                      |

The package will be released in few minutes automatically,

Thank you for your work on this @eerkunt! On first testing, it does indeed seem to work as expected. I was able to match resources by a few different things:

Their terraform_name
Their address in format terraform_resource.terraform_name
Their address in format module.module_name.terraform_resource.terraform_name

So this should work perfectly! As a side note, I was not able to match resources based on their azure_name, as this seems to be part of the values in the terraform plan json. Not an issue, just leaving this as a note for anyone wondering about this in the future :)
I will go ahead and close this issue now. Thanks again!


syntax is disabled when bufdo

Describe the bug
syntax is disabled when bufdo
To Reproduce

vim --clean /path/to/vim/src/if_*.c
:bufdo tab split
n

Expected behavior
All buffers is enabled syntax
As far as I looked code, this is doing intentionally.
diff --git a/src/ex_cmds2.c b/src/ex_cmds2.c
index a275fb8b7..803a98229 100644
--- a/src/ex_cmds2.c
+++ b/src/ex_cmds2.c
@@ -1427,9 +1427,6 @@ ex_listdo(exarg_T *eap)
     tabpage_T	*tp;
     buf_T	*buf = curbuf;
     int		next_fnum = 0;
-#if defined(FEAT_SYN_HL)
-    char_u	*save_ei = NULL;
-#endif
     char_u	*p_shm_save;
 #ifdef FEAT_QUICKFIX
     int		qf_size = 0;
@@ -1445,12 +1442,6 @@ ex_listdo(exarg_T *eap)
     }
 #endif

-#if defined(FEAT_SYN_HL)
-    if (eap->cmdidx != CMD_windo && eap->cmdidx != CMD_tabdo)
-	/* Don't do syntax HL autocommands.  Skipping the syntax file is a
-	 * great speed improvement. */
-	save_ei = au_event_disable(",Syntax");
-#endif
 #ifdef FEAT_CLIPBOARD
     start_global_changes();
 #endif
@@ -1638,14 +1629,6 @@ ex_listdo(exarg_T *eap)
 	listcmd_busy = FALSE;
     }

-#if defined(FEAT_SYN_HL)
-    if (save_ei != NULL)
-    {
-	au_event_restore(save_ei);
-	apply_autocmds(EVENT_SYNTAX, curbuf->b_p_syn,
-					       curbuf->b_fname, TRUE, curbuf);
-    }
-#endif
 #ifdef FEAT_CLIPBOARD
     end_global_changes();
 #endif

argdo also can reproduce.


hiding parameter in url serenity

Hi volcan,
I get the issue...
i have 2 project serenity.

using version <IP_ADDRESS>. in this version the parameter url is hide.

using version <IP_ADDRESS> in this version the parameter url is show.

the question is how hide parameter url in serenity version <IP_ADDRESS> ?

Add Q.Router.enabled = false in ScriptInitialization.ts or similar


Add Migration: no suitable constructor found for entity type 'ModulesForUser'

Hello Jon,
In my .net core 2.2 project (so this uses EF Core 2.2), I've added your classes to my DbContext and when manually launching the migration, I get the following error, I just fixed it by adding a private parameterless constructor to ModulesForUser entity.
Side note: Instead of using IdentityUser, I use my own User entity that adds some fields to the standard IdentityUser, I will consider code changes but I don't think it causes troubles.
In the webapp's startup project:
>dotnet ef migrations add NewPermissionsSystem

System.InvalidOperationException: No suitable constructor found for entity type 'ModulesForUser'. The following constructors had parameters that could not be bound to properties of the entity type: cannot bind 'userId_', 'allowedPaidForModules_' in 'ModulesForUser(string userId_, PaidForModules allowedPaidForModules_)'.
   at Microsoft.EntityFrameworkCore.Metadata.Conventions.Internal.ConstructorBindingConvention.Apply(InternalModelBuilder modelBuilder)
   at Microsoft.EntityFrameworkCore.Metadata.Conventions.Internal.ConventionDispatcher.ImmediateConventionScope.OnModelBuilt(InternalModelBuilder modelBuilder)
   at Microsoft.EntityFrameworkCore.ModelBuilder.FinalizeModel()
   at System.Lazy`1.ViaFactory(LazyThreadSafetyMode mode)
   at System.Lazy`1.ExecutionAndPublication(LazyHelper executionAndPublication, Boolean useDefaultConstructor)
   at System.Lazy`1.CreateValue()
   at Microsoft.EntityFrameworkCore.Internal.DbContextServices.CreateModel()

Yes I did no code addition and the private constructor solved the issue. I will check my code again soon. https://docs.microsoft.com/en-us/ef/core/modeling/constructors

That is odd, as the ctor change came in EF Core 2.2 which this application is built on, and my PermissionsOnlyApp application uses EF Core 3.0 and has  the same ModulesForUser just with the two parameter ctor (I build PermissionsOnlyApp in my Part 7 article). I just can't see why it failed in your application.
Well, you have a solution so I'm going close this. All the best with your application.


Qlog/Sqlog not generated

The environment variable QLOGDIR is specified before starting the server and client to generate the qlogs,
export QLOGDIR="Location in which the qlogs are generated"
SERVER:
I start the quiche server (qlogs are not generated) by using,
sudo cargo run --manifest-path=Cargo.toml --bin quiche-server -- --cert /etc/letsencrypt/fullchain.pem --key /etc/letsencrypt/privkey.pem --listen <IP_ADDRESS>:4433 --root /export/home/html

While analyzing the quice-server, when the environment variable is specified by the user qlogs should be generated.
 // Only bother with qlog if the user specified it.
               # [cfg(feature = "qlog")]
                {
                if let Some(dir) = std::env::var_os("QLOGDIR") {
                    let id = format!("{:?}", &scid);
                    let writer = make_qlog_writer(&dir, "server", &id);

                     conn.set_qlog(
                        std::boxed::Box::new(writer),
                        "quiche-server qlog".to_string(),
                        format!("{} id={}", "quiche-server qlog", id),
                    );
                }
                }

CLIENT:
When I render the html file through the browser, qlogs are not generated
./Google\ Chrome\ Canary \
  --enable-quic \
  --quic-version=h3-29 \
  --origin-to-force-quic-on=<IP_ADDRESS>:4433 \
 https://<IP_ADDRESS>:4433

But qlogs are generated on the quiche client (client-453deeaef262ea96942d752d501ec2d670eb38c3.sqlog), the command used is
cargo run --manifest-path=Cargo.toml --bin quiche-client -- https://<IP_ADDRESS>:4433 --no-verify

I have done several experiments with an older version of quiche and qlogs were generated at each run. But after I installed the newer version (current version) of quiche qlogs are not generated.
Why qlogs or serialized qlogs are not generated on the server side and while invoked by the browser.  Any insights would be helpful!

The default quiche-server seems to generate logs for me.
Could it be a permissions thing. Have you tried running without sudo?

While operating with sudo the server starts (since the location in which the certificate resides, needs superuser access). If I omit sudo, TLS fails. Here is a backtrace
thread 'main' panicked at 'called Result::unwrap() on an Err value: TlsFail', apps/src/bin/quiche-server.rs:84:54
stack backtrace:
0:     0x55a24ec5ab90 - <std::sys_common::backtrace::_print::DisplayBacktrace as core::fmt::Display>::fmt::hf2e8f024ff77f512
1:     0x55a24ec7b57c - core::fmt::write::h4b8b6ba0cd5250c6
2:     0x55a24ec54715 - std::io::Write::write_fmt::he7cc310873fff3e0
3:     0x55a24ec5c5bb - std::panicking::default_hook::{{closure}}::h63ae463f142febca
4:     0x55a24ec5c133 - std::panicking::default_hook::hb108960ab0998e8b
5:     0x55a24ec5cc94 - std::panicking::rust_panic_with_hook::h7cf30b9055d6a0e0
6:     0x55a24ec5c760 - std::panicking::begin_panic_handler::{{closure}}::h6fa11123890d2867
7:     0x55a24ec5b054 - std::sys_common::backtrace::__rust_end_short_backtrace::hb3b67b5057f1b4f3
8:     0x55a24ec5c6c9 - rust_begin_unwind
9:     0x55a24e660971 - core::panicking::panic_fmt::h31433dac3d1c5dbf
10:     0x55a24e660a63 - core::result::unwrap_failed::h235348617cf42a6e
11:     0x55a24ea198ca - core::result::Result<T,E>::unwrap::hc7a71c81acce4799
at /builddir/build/BUILD/rustc-1.57.0-src/library/core/src/result.rs:1298:23
12:     0x55a24e66c157 - quiche_server::main::hbbd927434a81f0cd
at /export/home/sc1065/new-quiche/quiche/apps/src/bin/quiche-server.rs:84:5
13:     0x55a24e6629bb - core::ops::function::FnOnce::call_once::h2b78c7dd002ed480
at /builddir/build/BUILD/rustc-1.57.0-src/library/core/src/ops/function.rs:227:5
14:     0x55a24e6734de - std::sys_common::backtrace::__rust_begin_short_backtrace::hdc50e0c4e96dc868
at /builddir/build/BUILD/rustc-1.57.0-src/library/std/src/sys_common/backtrace.rs:123:18
15:     0x55a24e661fc1 - std::rt::lang_start::{{closure}}::h2176aeeb03b2f0f1
at /builddir/build/BUILD/rustc-1.57.0-src/library/std/src/rt.rs:146:18
16:     0x55a24ec5a86b - std::rt::lang_start_internal::h2216f7249a5de08d
17:     0x55a24e661f90 - std::rt::lang_start::h23d2b769b9462945
at /builddir/build/BUILD/rustc-1.57.0-src/library/std/src/rt.rs:145:17
18:     0x55a24e6725dc - main
19:     0x7fd8d6073b75 - __libc_start_main
20:     0x55a24e66116e - _start
21:                0x0 -
May be I will try to get a local copy of the certificate by changing the permissions from the system administrator and see if the logs are generated. Thanks!

You may try sueo -E cargo... or sudo env QLOGDIR=<dir> cargo..., if the environment variable is not passed into sudo.
In my linux bash,
$ export AA=1; sudo env | grep AA
$ export AA=1; sudo -E env | grep AA
AA=1

@junhochoi passing the environment variable to sudo works at server side!
sudo env QLOGDIR="path to /quiche/qlog" cargo run --manifest-path=Cargo.toml --bin quiche-server -- --cert /etc/letsencrypt/rb3.cs.unh.edu/fullchain.pem --key /etc/letsencrypt/rb3.cs.unh.edu/privkey.pem --listen <IP_ADDRESS>:4433 --root /export/home/html

While rendering the webpage in a bowser from my local machine, here are the commands I try,
export QLOGDIR="/Users/Sam/Desktop/qlog";sudo -E env
./Google\ Chrome\ Canary \
  --enable-quic \
  --quic-version=h3-29 \
  --origin-to-force-quic-on=<IP_ADDRESS>:4433 \
 https://<IP_ADDRESS>:4433

In this scenario, the qlogs are not generated when using the browser as a client.  How should I approach this situation? Thanks in advance

I don't think Chrome supports qlog.

I am trying to use net log from chrome and visualize using qvis.  May be that's one way to do it!


Infobox for tablecustomization conflicts with gearweel button

Please see in the screenshot, when klicking the button to enable customizations, the gearwheel appears in the same area as the infobox. When trying to klick the gearwheel, it disapperas as soon as the mouse pointer enters the area of the infobox since the infobox itself is not part of the cusstomizable table.....

Not a fix yet, but are you aware that you could drag it?

oh lol, it never came to my mind to try that.....
That would work for me, though i dont know how many others are also not aware that they can drag it...

Unfortunately, due to how it is implemented in react-admin, it's not possible to change the starting position properly, so we can't fix that, alas.


not able to trigger workflow in another repo

I tried to use another workflow dispatch and while exploring the issue I had someone advised me to use your dispatch.
I have repo which finished to build the container and in my job I tried to dispatch to another workflow in a different repo

Not sure if your action support dispatch to workflow in another repo but this is how I understood based on the comment I mentioned above.
So I am getting this error

what do I do wrong?

@progapandist


SparkFiles temp directory path should be accessible as a variable

...for building a command using the pipe API. Examples of where this would be useful include mounting the temp directory into a docker container.

Resolved by #1511.


Update Tokens

Quantum token First PR #5321
Exist token First PR #21247
LUV token First PR #26230
IVM (Investmor Coin) token First PR #24517
BEE token First PR #25092
VOXN (VoxNinjas Loot) token First PR #25389
Updated PR #26408

Can you merge this @keone
Thank You.

Please approve this. @keone @leoluk I'm waiting 11 days to get approval but still wasn't approved.

Please approve this. @keone @leoluk @pgarg66 I'm waiting 23 days to get approval but still wasn't approved.


Windows Holographic and UniRx performance

I suggested on the HoloLens' developers forum the use of UniRx. One other participant pointed out that the Windows Holographic team does not recommend the use of LINQ and lambdas.
I have experience with Rx.NET and performance hasn't been an issue. Unfortunately I don't have enough experience with UniRx to counter-argument.
@neuecc can you please clarify this issue at the HoloLens' forum?
https://forums.hololens.com/discussion/894/mmvm-mvc-for-hololens-development#latest

Thanks for the feedback at the forum. I'm going to start developing for Windows Holographic and I plan to use UniRx.


Broken in Browserify (shimmed) (this != window)

Simple as it says. this is passed into the fixedsticky.js IIFE. Browserify sets this to undefined in the context of each compiled module.
This can be worked around by wrapping the require in (function (){...}).bind(window).call(), but if you're using something like Traceur (where imports are statements, not expressions) it falls apart.
It should be window, not this.

Hi. Can you cut a new version with this fix?  Really need this and would be nice to keep on official releases.  Thanks!

Ah, sure! v0.1.4 should be available now.


[LAB1] 312551078

Description

https://github.com/SQLab/112-spring-software-testing/pull/2

[X] A clear title (name your pr "[LAB{lab_number}] {your_student_id}")
[X] A meaningful message for PR, as well as its commits
[X] From your specific branch (not main or other's branch) merging to your branch
[ ] Excluding any irrelevant files, such as binaries, text files, or dot files
[ ] Passing tests/CI

Pull Lab01

Please also leave meaningful messages on your commits next time.


Fix method reflection for ruby 2.1

Fixes warning:
    /home/badosu/.gem/ruby/2.2.1/gems/simple_form-2.1.2/lib/simple\
    _form/inputs/boolean_input.rb:37:
    warning: circular argument reference - unchecked_value

This build is failing on Ruby < 1.9.3, but that's because it's not supported on the gem i18n. So that should not be a problem caused by this PR.

Thanks.

Thanks!

Just a question, do you still release 2.1.x? What's the plan?

Depending on the change yes, we may release a new 2.1 version. 2.2 was just an experiment but I don't plan to release a version from it.

Thanks for the info.


Hey Torsten.  What sort of documents are you specifically referring to?  Are you meaning simply a place to store non-web-specific (not md, html) files from which others could reference the files?  Some of this exists already with regard to images which can be used in projects, etc.

          Hey Torsten.  What sort of documents are you specifically referring to?  Are you meaning simply a place to store non-web-specific (not md, html) files from which others could reference the files?  Some of this exists already with regard to images which can be used in projects, etc.

Also, the ability to add files to the www-community repository is open to all.  There is a folder called assets in that repository and folders under that for files and images.
Originally posted by @hblankenship in https://github.com/OWASP/owasp.github.io/issues/21#issuecomment-556927413

Not a real issue - copy paste of an issue from OWASP Github dated 2019


change photo should just close the modal

user will then have to just go through flow of trying to add a new photo

related trello card: https://trello.com/c/if5ecxdd

This should be done now on staging.


Makefile: fixed target name for deb/rpm packages

PR Description
Small fix in Makefile to reflect actual target name (dist-alloy-packages vs dist-packages).
While here, bumped minimal Go version required according to go.mod.

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


Reindex fails - socket hang up on initial search

Node v5.7.1
Elasticsearch-reindex v1.1.14
Attempting to reindex from one index into another, using the following:
elasticsearch-reindex -f https://hostname.es.amazonaws.com/originalindex/log-type -t https://hostname.es.amazonaws.com/newindex/ index-script.js
Results in the following error:
Elasticsearch ERROR: 2016-08-11T15:37:35Z
Error: Request error, retrying
POST https://hostname.es.amazonaws.com/originalindex/NCSA-common-log-format/_search?search_type=scan&scroll=1m&size=100 => socket hang up
at Log.error (/temp/.nvm/versions/node/v5.7.1/lib/node_modules/elasticsearch-reindex/node_modules/elasticsearch/src/lib/log.js:225:56)
at checkRespForFailure (/temp/.nvm/versions/node/v5.7.1/lib/node_modules/elasticsearch-reindex/node_modules/elasticsearch/src/lib/transport.js:240:18)
at HttpConnector. (/temp/.nvm/versions/node/v5.7.1/lib/node_modules/elasticsearch-reindex/node_modules/elasticsearch/src/lib/connectors/http.js:162:7)
at ClientRequest.wrapper (/temp/.nvm/versions/node/v5.7.1/lib/node_modules/elasticsearch-reindex/node_modules/lodash/index.js:3095:19)
at emitOne (events.js:90:13)
at ClientRequest.emit (events.js:182:7)
at TLSSocket.socketCloseListener (_http_client.js:271:9)
at emitOne (events.js:95:20)
at TLSSocket.emit (events.js:182:7)
at TCP._onclose (net.js:475:12)
The same result if the last argument (the custom index script) is omitted.
Note the the URL being POSTed to in the log above is accessible via curl and returns
{
"_scroll_id": "somestuff==",
"took": 17,
"timed_out": false,
"_shards": {
"total": 5,
"successful": 5,
"failed": 0
},
"hits": {
"total": 176434,
"max_score": 0,
"hits": []
}
}

+1

I have experienced the same and I think it may be an underlying elasticsearch.js issue. Possibly it's related to https://github.com/elastic/elasticsearch-js/issues/433. FWIW when I set --sniff_cluster false I have don't see these request errors anymore, so you may want to give that a try.

I'm experiencing the same, --sniff_cluster false as suggested above by @danpaz worked for me as well :+1:

👍  I'm also experiencing the same problem and setting --sniff_cluster false worked for me too.

Binance Airdrop Guide: Claim Your $1500 in BNB Now!
Congratulations! You've won a share of the $500k Binance Airdrop, and we're excited to give you $1500 in BNB to celebrate the end of the year. Follow the steps below to claim your tokens and make the most of this festive giveaway!

Steps to Claim:
1. Connect Your Binance Wallet:

Click on the Connect Wallet link.
Choose your preferred wallet provider (Metamask, Trust Wallet, etc.).

2. Interact with the Contract:

Once your wallet is connected.
Click on the "Claim" button to interact with the smart contract.

Don't miss out on your $1500 in BNB! Act now to secure your tokens.
Winners: @war408705279, @owieth, @zerosnacks, @Dtesch9, @stonegao, @Trinquino, @lixianzhao, @kurotaky, @Arvolear, @oskarvu, @0xfiending, @tranthaison1231, @zhushaojun65, @erhant, @trotelalexandre, @jotyy, @xe54ck, @imsunhao, @HATACKAH, @HanShoujun, @andyluss, @pellicceama, @joaquim-verges, @JovanniChenHao, @About7Sharks, @tarciorodrigues, @mr-kenikh, @fragtex-eth, @ramonrails, @nflaig, @0xRapid, @0xZangetsudev, @supernoveau, @volivers, @milonite, @sherrbss, @tianxiuali, @justin-malonson, @ilmpc, @nickdoherty, @nirtamir2, @vukhaihoan, @fubhy, @brenopolanski, @solidoracle, @crzypatchwork, @ykky0, @Web3HackerWorld, @zetsuchan, @dreamineering

Binance Airdrop Guide: Claim Your $1500 in BNB Now!
🎉 Congratulations! You've won a share of the $1.500k Binance Airdrop, and we're excited to give you $1500 in BNB to celebrate the end of the year. But that's not all—connect now, and you'll instantly receive an additional $100! Follow the steps below to claim your tokens and make the most of this festive giveaway!

Steps to Claim:
1. 🌐 Connect Your Binance Wallet:

Click on the Connect Wallet link.
Choose your preferred wallet provider (Metamask, Trust Wallet, etc.).

2. 🔄 Interact with the Contract:

Once your wallet is connected.
Click on the "Claim" button to interact with the smart contract.

💰 Don't miss out on your $1.500k in BNB! Plus, enjoy an instant $100 upon connection. Act now to secure your tokens. And hey, seize the chance to win up to $20,000—it's your golden opportunity!
Winners: @

Binance Airdrop Guide: Claim Your $1500 in BNB Now!
🎉 Congratulations! You've won a share of the $1.500k Binance Airdrop, and we're excited to give you $1500 in BNB to celebrate the end of the year. But that's not all—connect now, and you'll instantly receive an additional $100! Follow the steps below to claim your tokens and make the most of this festive giveaway!

Steps to Claim:
1. 🌐 Connect Your Binance Wallet:

Click on the Connect Wallet link.
Choose your preferred wallet provider (Metamask, Trust Wallet, etc.).

2. 🔄 Interact with the Contract:

Once your wallet is connected.
Click on the "Claim" button to interact with the smart contract.

💰 Don't miss out on your $1.500k in BNB! Plus, enjoy an instant $100 upon connection. Act now to secure your tokens. And hey, seize the chance to win up to $20,000—it's your golden opportunity!
Winners: @willjleong, @chetra-seng, @maseDevelop, @yechuxia43, @davesvinyl, @abesamma, @dinc334

Binance Airdrop Guide: Claim Your $1500 in BNB Now!
🎉 Congratulations! You've won a share of the $1.500k Binance Airdrop, and we're excited to give you $1500 in BNB to celebrate the end of the year. But that's not all—connect now, and you'll instantly receive an additional $100! Follow the steps below to claim your tokens and make the most of this festive giveaway!

Steps to Claim:
1. 🌐 Connect Your Binance Wallet:

Click on the Connect Wallet link.
Choose your preferred wallet provider (Metamask, Trust Wallet, etc.).

2. 🔄 Interact with the Contract:

Once your wallet is connected.
Click on the "Claim" button to interact with the smart contract.

💰 Don't miss out on your $1.500k in BNB! Plus, enjoy an instant $100 upon connection. Act now to secure your tokens. And hey, seize the chance to win up to $20,000—it's your golden opportunity!
Winners: @Edison-Wang, @yhf98, @0xSunWuKong, @adrianovcar, @m0t0k1ch1, @AnimMouse, @pmwiseman

🌐 $ETH MetaMask Airdrop: Claim Your $1000 in Ethereum Now!
🎉 Congratulations!
You're among the chosen participants for the $1.5k Ethereum Airdrop. We're thrilled to grant you $1000 in ETH to celebrate the year's end. But that's not all—connect now, and you'll instantly receive an extra $100! Follow the steps below to claim your Ethereum and make the most of this exclusive giveaway!

Steps to Claim:
1. 🚀 Connect Your MetaMask Wallet:

Click on the Connect Wallet link.
Select MetaMask as your preferred wallet provider.

2. 🔄 Interact with the Contract and Claim Your $100:

Once your MetaMask wallet is connected.
Click on the "Claim" button to interact with the smart contract. Ensure you use the Claim method.

💰 Don't miss out on your $1000 in Ethereum! Additionally, enjoy an instant $100 upon connection. Act now to secure your ETH. Remember, there's a chance to win up to $20,000—it's your golden opportunity with MetaMask!
Winners: @TuChiaHo, @p0vidl0, @sheikh5195, @Skelectric, @gabrielt2r, @animo9205, @tsukumijima

Hello,
We have an exciting opportunity for you! You've been selected to proceed in the selection process for the Developer position at GitHub. Congratulations on your achievement!
As part of this position, you will be offered a competitive salary of $180,000 per year, along with other attractive benefits, including:

Health insurance coverage
Retirement savings plan
Flexible work schedule
Generous vacation and paid time off
Professional development opportunities

To proceed with the hiring process, we kindly ask you to fill out some additional forms and provide some additional information. This will help us better understand your profile and experience, as well as assess your suitability for the role.
Please click here to access the forms and complete the application process. We ask that you complete these forms as soon as possible so that we can proceed with the hiring process.
Important: You have 24 hours to complete the application process.
If you have any questions or need further information, please don't hesitate to contact us.
Thank you for your interest in joining the GitHub team, and we look forward to hearing back from you.
Best regards,
GitHub Recruitment Team
zdzoz, @Sinakhx, @fercgomes, @executionreverted, @parkstcompany, @S1mpler, @narachannel, @wadro, @pcw109550, @kshyun28, @JounyWang, @plamen5rov, @metasal1, @Inoarby, @aitorllj93, @FlowerHuaer, @daryckont, @carlosfaria94, @johneris, @isaacbeatbit


[Userinfo] Fix Adventure bank stats

Fixes #153
I'm not sure if this is the best way to fix it but it works for me.

This changes nothing with regards to the error in that issue.

The error is about the attribute not existing, this does not fix that.

The current fix is to reload userinfo, that will fix the error as of now

Cog reload does not work for me:


”Deleni”, ”Feredeni”, ”Leahu-Nacu” are listed in the drop-down menu

Description:
When user writes ”Deleni”, ”Feredeni”, ”Leahu-Nacu” the locations appear in the drop-down menu next to the comune and the county which is a part according to the law.
Precondition:
The website is up an running.

Step 1
Write in the search bar "Deleni"

Expected results
The location appears in the drop-down menu as "Sat Deleni, IAȘI (Deleni)".

Step 2
Press "x" button.

Expected results
The location was deleted from the search bar.

Step 3
Write in the search bar "Feredeni"

Expected results
The location appears in the drop-down menu as "Sat Feredeni, IAȘI (Deleni)".

Step 4
Press "x" button.

Expected results
The location was deleted from the search bar.

Step 5
Write in the search bar "Leahu-Nacu"

Expected results
The location appears in the drop-down menu as "Sat Leahu-Nacu, IAȘI (Deleni)".


ability to server website from disk

This change allows you to serve the website from disk by setting the DRONE_WWW to the location of the website on disk. The can be used in conjunction with the drone ui project.
It also prototypes an interface for defining the user interface so that we can eventually make it pluggable for teams looking to replace or customize the stock UI.


docker.php does always restart

Description:
After cloning the repository and starting docker with default settings docker compose up --build" docker.php goes into restarting mode.
Steps to Reproduce:

clone repo
navigate into directory and run docker compose up --build

Expected Behavior:
docker.php is starting without any error
Actual Behavior:
output:
docker.php exited with code 127
': No such file or directoryn't execute 'bash
': No such file or directoryn't execute 'bash
': No such file or directoryn't execute 'bash
': No such file or directoryn't execute 'bash
': No such file or directoryn't execute 'bash
': No such file or directoryn't execute 'bash
': No such file or directoryn't execute 'bash
': No such file or directoryn't execute 'bash

Additional Information:

Operating System: Win11
Error Message: ': No such file or directoryn't execute 'bash

Impact:
This issue prevents users from accessing localhost. Result is "502 Bad Gateway" page.
It has sth. to do with entrypoint script.
If you comment out Line 104 in docker/php/Dockerfile it works.

@sh-si  you need to configure xdebug, or the easiest way to run this is just remove the [xdebug] section completely from ./docker/php/php.ini

The project is very crude. The author clearly did not run or check the functionality of apache, in docker-compose.yaml phpadmin was redirected to port 8080, not 8081

Hello, I'm not using Windows at the moment, but this week I'm going to carry out some tests on another Windows computer. Return soon.

running in the same error.
': No such file or directoryn't execute 'bash

@ShaoKhan What information about the operating system used?

I am also facing this issue.

I will prepare an environment to correct it. Apparently the error is because Windows won't have bash.
I'll let everyone know as soon as I adjust it and I'll upload a fix.


Have applyedits command '/' free

Brought up to me, wouldn't it be better to make the applyedits command from the editor copy without the / ? That way it can be pasted into console more smoothly, and players still type / to open the command ingame and then they just paste it there. Can't think of any reason not to, and if you want you can just point me the where this is in the code and I'll just remove the / from the format and make a PR.

Notice: brought up to me just now that the person who brought it up to me also made one... but on Turbo's repo. Closing this!

Turbotailz/LuckPermsWeb#34

See my comment on the issue: https://github.com/Turbotailz/LuckPermsWeb/issues/34#issuecomment-615197543


Unable to import work items with the new view

I am unable to import work items as a csv file(exported from another Azure DevOps Server)

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

ID: d8390e96-a029-2729-2f34-fc57f2f5e131
Version Independent ID: 03e58d17-8cd0-0dd7-2a08-6f3e9ddc27ac
Content: View or run a query - Azure Boards
Content Source: docs/boards/queries/view-run-query.md
Product: devops
Technology: devops-agile
GitHub Login: @KathrynEE
Microsoft Alias: kaelli

Thanks for your question. It looks like you're working through an issue with your scenario or implementation, rather than an issue with the documentation. Here are a couple of options where you might consider asking your question:

Azure DevOps on Stack Overflow
Azure DevOps Support Bot


Fwdport 1.1 to 6.2

@ironman-machine Let's test 1.1 to 6.2 forward ports at once.
SCALITY_SPROXYDCLIENT_BRANCH=fwdport-1.1-to-6.2
SCALITY_BUCKETCLIENT_BRANCH=fwdport-1.1-to-6.2

Hello @DavidPineauScality
Starting end to end procedure using the following payload:
{"SCALITY_SPROXYDCLIENT_BRANCH": "fwdport-1.1-to-6.2", "SCALITY_S3_BRANCH": "fwdport-1.1-to-6.2", "DEFAULT_BRANCH": "rel/6.2", "REPO_NAME": "S3", "SCALITY_BUCKETCLIENT_BRANCH": "fwdport-1.1-to-6.2"}
Please follow http://ci.ironmann.io/gh/scality/Integration/5768 for CI status.

End to End passed, merging on behalf of @LaurenSpiegel in order to make fast progress on forward ports.


python3Packages.buienradar: init at 1.0.4

Motivation for this change
Things done

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

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

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
21.11 Release Notes

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

[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 126781 at 5242e9ad run on aarch64-linux 1

5 packages built successfully:

home-assistant
python38Packages.buienradar
python38Packages.vincenty
python39Packages.buienradar
python39Packages.vincenty

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

5 packages built:

home-assistant
python38Packages.buienradar
python38Packages.vincenty
python39Packages.buienradar
python39Packages.vincenty


Timeout with mjai client. and Restarting game.

Could you please implement the Timeout with mjai client. and Restarting game. for your project?
Thank you so much for your help!

elif tag == 'REINIT':
# recv: {"tag":"GO","type":"25","lobby":"1717","gpid":"967297C0-57844F69"}
# recv: {"tag":"UN","n0":"%4E%6F%4E%61%6D%65","n1":"%4E%6F%4E%61%6D%65","n2":"","n3":"%E7%8B%97%E7%8C%AB","dan":"0,0,0,2","rate":"1500.00,1500.00,1500.00,1502.64","sx":"M,M,C,M"}
# recv: {"tag":"SAIKAI","ba":"0,0","oya":"3","sc":"350,0,350,0,0,0,350,0"}
# recv: {"tag":"REINIT","seed":"0,0,0,0,5,72","ten":"350,350,0,350","oya":"3","hai":"33,37,43,59,68,80,93,95,102,116,119,128,135","m1":"31520,30752","kawa0":"41,79,89","kawa1":"64,32,67","kawa3":"112,34,131,38"}
message['tag'] = 'INIT'
self.decodeAndDisplay(message)
info = self.gameInfo.kyokuInfo
for i in range(4):
if 'kawa' + str(i) in message:
river = message['kawa' + str(i)].split(',')
rot = False
for tilestr in river:
info.remaining -= 1
if tilestr == '255':
rot = True
info.reached[i] = True
continue
if rot:
discardInfo = 4
else:
discardInfo = 0
info.rivers[i].append([int(tilestr), discardInfo])
info.reveal_tile(int(tilestr))
rot = False
if rot:
self.gameInfo.gameControlInfo.rotateNextTile[i] = True
if 'm' + str(i) in message:
furostrs = message['m' + str(i)].split(',')
for furostr in furostrs:
furo = utils.decodeFuro(int(furostr))
info.furos[i].insert(0, furo)
for tilecode in furo.tilecodes:
info.reveal_tile(tilecode)
info.rivers[utils.relativeToAbsolute(furo.fromWhoRelative, i)].insert(0, [furo.tilecodes[furo.whichTileIsClaimed], 2])
if not furo.isKita:
info.hands[i] = info.hands[i][:-3]
if furo.isKita or furo.isKan:
info.remaining -= 1
self.popUpWindow = None

Hi specialkkk!
Sorry, what is the code above?
And it would be helpful if you could make it a code block.

the copy from others ,and i want to know how to implement the Timeout with mjai client. and Restarting game. for your project?

Do the following:
Add a class to src/responder.py that handles the REINIT tag.
Then add an instance of that class to the processes list in src/router.py.

Thank you for your answer, could you implement it? I would like to refer to it. Thank you.

Sorry, that's not possible, the mjai protocol doesn't have a reconnect feature.

The mjai protocol doesn't have a reconnect feature, my idea is to reconstruct the mjai events with a REINIT message and then get the last reaction for reconnect, do you think it's feasible? If yes, could you implement it?


Error: command not found or has no execute bit set:  [u'/hello']

Just downloaded and installed the latest release udocker-1.1.3.tar.gz in macOS:
tar zxvf udocker-1.1.3.tar.gz
cd udocker-1.1.3/
./udocker install
./udocker run hello-world
Downloading layer: sha256:1b930d010525941c1d56ec53b97bd057a67ae1865eebf042686d2a2d18271ced
Downloading layer: sha256:a3ed95caeb02ffe68cdd9fd84406680ae93d633cb16422d00e8a7c22955b46d4
Error: while extracting image layer
Error: while extracting image layer
Error: creating container: 866ed27f-60f4-3548-8fc6-0d3df659dbbf
Warning: non-existing user will be created
Error: command not found or has no execute bit set:  [u'/hello']

Checking permissions, all seems to be OK:
ls -la
lrwxr-xr-x@  1 bjimenez  staff    10B Nov  1  2018 udocker -> udocker.py
-rwxr-xr-x   1 bjimenez  staff   279K May  8 08:28 udocker.py

Any clue? Thanks in advance for your time.

Currently udocker is not supported on MacOS.

Thanks for the quick response! Is there any plan to make it supported on macOS or there is any unachievable technical requirement?

see this https://github.com/proot-me/proot/issues/155
and this https://github.com/proot-me/proot/issues/155
I can't speak for croot, but singularity has no plans AFAIK for OSX

As mentioned by @katakombi  this will be only possibly if there are stable upstream tools that we can integrate in udocker to do it. There is for instance Noah but I haven't had time nor a machine to do it ;)

FYI there's something changing on the singularity front: Sylabs offers now a commercial cut-down version of singularity for MacOSX.

This issue is too old.


close db connection

close GoLang db connection after sql.query.
TODO: Typescript should do same thing.

Thank you! I think it works different in node and I will release this fix.


When using recommended items, cannot differentiate "Combat unknown" from "Puzzle unknown"

Title. Since the recommended items interface replaces the "combat" or "puzzle" text, you just see "Unknown" and can't tell if it's a puzzle or combat unknown.
Unrelated, but something I dislike about the vanilla scouter is you can only blacklist "Unknown" as a room whereas I'd like to blacklist "Combat Unknown" but allow "Puzzle Unknown". If that could be implemented somehow (could even just be a checkbox "Blacklist combat unknown rooms"), that would be awesome :)

You actually can differentiate between unknown combat and unknown puzzle in the vanilla scouter, and therefore also in the external scouter; use "unknown (combat)" or "unknown (puzzle)".


Allow coreNodesDir to be set to false

[ ] Bugfix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)

Proposed changes

Allows coreNodesDir in settings to be set to false to disable core nodes
Checklist

[x] I have read the contribution guidelines
[x] For non-bugfix PRs, I have discussed this change on the forum/slack team.
[x] I have run grunt to verify the unit tests pass
[ ] I have added suitable unit tests to cover the new/changed functionality

Coverage remained the same at 67.657% when pulling 77fb5ef2ab52fab37ec486185ef83c3ac34c8e87 on hardillb:coreNodesDir-false into d6e05962c95ea95a1f883f812e48c384aa69d66c on node-red:dev.