tf.nn.softmax on GPU causes CUDA_ERROR_ILLEGAL_ADDRESS (okay on CPU)

CentOS 7
Tensorflow 0.10.0
TITAN X (Pascal) 367.44
I restore a model previously saved with tf.train.Saver() and try to compute probabilities of outputs for a given input batch. Whenever I try to execute tf.nn.softmax on GPU, I get an error:
E tensorflow/stream_executor/cuda/cuda_driver.cc:1140] could not synchronize on CUDA context: CUDA_ERROR_ILLEGAL_ADDRESS :: No stack trace available
F tensorflow/core/common_runtime/gpu/gpu_util.cc:370] GPU sync failed
E tensorflow/stream_executor/cuda/cuda_event.cc:49] Error polling for event status: failed to query event: CUDA_ERROR_ILLEGAL_ADDRESS

but same computations work just fine on CPU:
print('run 1: logits')
logits = s.run(model.other.logits_labl, tf_run_args)
print(logits.shape) # (1001, 289)
print(np.max(logits), np.min(logits)) # 1.80996 -0.752239

print('run 2: probs in np')
probs = s.run(tf.nn.softmax(logits))
print(probs.shape) # (1001, 289)
print(np.sum(probs, axis=1)) # [ 1.   ...  1.00000012  1.          1.00000012]

print('run 3: probs on cpu')
with tf.device('/cpu:0'):
    t = tf.nn.softmax(model.other.logits_labl)
print(s.run(t, tf_run_args)) # okay

print('run 4: probs on gpu')
with tf.device('/gpu:0'):
    t2 = tf.nn.softmax(model.other.logits_labl)
print(s.run(t2, tf_run_args)) # error

produces
run 1: logits
(1001, 289)
1.80996 -0.752239
run 2: probs in np
(1001, 289)
[ 1.          0.99999994  1.         ...,  1.00000012  1.          1.00000012]
run 3: probs on cpu
[[ 0.00353091  0.0032969   0.00355321 ...,  0.00368173  0.00337926
   0.00326502]
 [ 0.00343715  0.00313538  0.00379693 ...,  0.00426536  0.0032676
   0.0031463 ]
 [ 0.00346572  0.00300998  0.00389543 ...,  0.00458091  0.0031747
   0.0030867 ]
 ...,
 [ 0.0035709   0.00302548  0.00384262 ...,  0.0042819   0.00318443
   0.00299288]
 [ 0.00353101  0.00305104  0.00379521 ...,  0.00428836  0.0031993
   0.0029559 ]
 [ 0.00352879  0.00302152  0.00380528 ...,  0.0043787   0.00318416
   0.00294856]]
run 4: probs on gpu
E tensorflow/stream_executor/cuda/cuda_driver.cc:1140] could not synchronize on CUDA context: CUDA_ERROR_ILLEGAL_ADDRESS :: No stack trace available
F tensorflow/core/common_runtime/gpu/gpu_util.cc:370] GPU sync failed
E tensorflow/stream_executor/cuda/cuda_event.cc:49] Error polling for event status: failed to query event: CUDA_ERROR_ILLEGAL_ADDRESS
Aborted

gdb does not give any additional details
... same as above
[New Thread 0x7fff41ffb700 (LWP 26404)]
E tensorflow/stream_executor/cuda/cuda_driver.cc:1140] could not synchronize on CUDA context: CUDA_ERROR_ILLEGAL_ADDRESS :: No stack trace available
E tensorflow/stream_executor/cuda/cuda_event.cc:49] Error polling for event status: failed to query event: CUDA_ERROR_ILLEGAL_ADDRESS
F tensorflow/core/common_runtime/gpu/gpu_util.cc:370] GPU sync failed
F tensorflow/core/common_runtime/gpu/gpu_event_mgr.cc:198] Unexpected Event status: 1

Program received signal SIGABRT, Aborted.
[Switching to Thread 0x7fff5effd700 (LWP 26391)]
0x00007ffff6a315f7 in raise () from /lib64/libc.so.6
Missing separate debuginfos, use: debuginfo-install libX11-1.6.3-2.el7.x86_64 libXau-1.0.8-2.1.el7.x86_64 libXdmcp-1.1.1-6.1.el7.x86_64 libuuid-2.23.2-26.el7_2.3.x86_64

Surprisingly, this error occurred just recently. I have been working with this same codebase for months and before now nothing like this happened, but now it is 100% reproducible on my machine with this specific (code, driver version, etc), so it is not something that effects everyone, but rather pops up randomly. I might have changed operation device placement recently.
code (unfortunately, large piece of code that required certain data; failed to produce a minimal reproducing code): [link]
full gdb output (without prints): [link]
environment:
$ ls -l /usr/lib/libcu*
lrwxrwxrwx. 1 root root      12 Oct  3 15:36 /usr/lib/libcuda.so -> libcuda.so.1
lrwxrwxrwx. 1 root root      17 Oct  3 15:36 /usr/lib/libcuda.so.1 -> libcuda.so.367.44
-rwxr-xr-x. 1 root root 7747600 Oct  3 15:36 /usr/lib/libcuda.so.367.44
$ ls -l /usr/local/cuda/lib64/
lrwxrwxrwx. 1 1000 users       13 Jul 27 01:55 libcudnn.so -> libcudnn.so.5
lrwxrwxrwx. 1 1000 users       17 Jul 27 01:55 libcudnn.so.5 -> libcudnn.so.5.1.5
-rwxrwxr-x. 1 1000 users 79337624 Jul 27 01:53 libcudnn.so.5.1.5
-rw-rw-r--. 1 1000 users 69756172 Jul 27 01:53 libcudnn_static.a

Possibly related issues: #2117 #1450 #2810 #665 #1060 #4425

Could you help narrowing down the error with cuda-memcheck from nvidia?
To make it more easier to trace, probably setting CUDA_LAUNCH_BLOCK=1 and run with --brain_gpu_sync_every_op.

@drpngx memcheck with CUDA_LAUNCH_BLOCK=1 . Do I have to re-build tensorflow from source to set --brain_gpu_sync_every_op or there's an easier way?

Woops, you're right. It looks like you have to tweak gpu_device_factory.cc, but from the trace it's clear that it's in the eigen softmax, probably the dense one.
@zheng-xq for any additional insight. We don't have access to the data, but we have access to the source code. If that's an actual bug in tensorflow, it would be great to get to the bottom of this.

To sync after each op, you'll have to build from source by modifying this line.
https://github.com/tensorflow/tensorflow/blob/master/tensorflow/core/common_runtime/gpu/gpu_device_factory.cc#L34
If you still have this problem with the latest driver, then we will need to know which kernel causes this problem. Combining that with memcheck and CUDA_LAUNCH_BLOCK=1 tends to give the best answer.

@zheng-xq the memcheck above says it's in ReduceInitKernel from the eigen softmax. I wonder if there are diagnostics we could print (dimensions etc) of buffers vs expected op input

here's the tf-related part of the code above, if that is be helpful to understand device placement

Would it be possible for you to create a repro that we could try locally?

If you had a build with debug on, then we might be able to see what the intermediate stack frames are. ReductionInitKernel appears to have been passed nullptr + offset (maybe 300 or so), so it's pulled from a struct which has about 300 bytes worth of stuff before the output, and that struct instance pointer is nullptr, presumably.

@benoitsteiner if you're interested.

@MInner Can you try with the release candidate for 0.11 ? There was a bug in 0.10 that could explain your CUDA_ERROR_ILLEGAL_ADDRESS error and has been fixed since.

@benoitsteiner Which commit fixed this bug? I encountered a same error in tensorflow 1.0.0 and try to reproduce it now.

I also still encounter this problem when use large enough models with google/seq2seq on same hardware as mentioned in the topic heading.

@MInner to be clear, you are getting CUDA_ERROR_ILLEGAL_ADDRESS?

@drpngx yes, and other random errors like shape mismatch in the middle of training; people in seq2seq issue tracker (referenced above) suggest that this might be related to race condition during concurrent training and evaluation in contrib.learn.experiment.train_and_evaluate.

Please link to issue on seq2seq
On Apr 13, 2017 7:45 AM, "Ben Usman"<EMAIL_ADDRESS>wrote:

@drpngx https://github.com/drpngx yes, and other random errors like
shape mismatch in the middle of training; people in seq2seq issue tracker
(referenced above) suggest that this might be related to race condition
during concurrent training and evaluation in contrib.learn.experiment.
train_and_evaluate.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/tensorflow/tensorflow/issues/5221#issuecomment-293915757,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AT_Sbbomikr2D_5AN2rwEKTxqtJbBbTKks5rvjTvgaJpZM4Khtms
.

I meant this comment.

Thanks! Closing this one in favor of the other one, so that we just have place to track.

Have you figured it out?


Fixes, updates, and feature additions

Fixes #35
Replaces #40
Will add support for occupancy sensors and occupancy sensor groups (the latter is really what should be treated as binary sensors in hass)
Converts to async/await syntax
Drops support for Python 3.4
Adds testing/support for Python 3.7
Updates test requirements

TODO

[x] occupancy sensors/groups are supported
[x] add callback/subscriber support to occupancy groups

@mdonoughe @gurumitts - this should be ready for review.
It updates the library to use async/await instead of asyncio.coroutines.  It drops support for Python 3.4 (which is currently EOL and no longer supported even for security fixes, so a good candidate for dropping support here).  However, it also addresses pending deprecations that would have broken the library for Python 3.10.
It adds support for occupancy/vacancy sensors in Caseta (a recent addition) as well as fixing a bug for systems that have scene picos (#40 and #35).

Thanks for the comments, @mdonoughe -- if there aren't any more review comments, this should be ready for merge.


Horizontal merging of DL1 files

To process observed data, e.g. MAGIC + LST, using stage1, we need a tool to merge DL1 files horizontally (merging subarrays instead of appending events).

This is actually quite easy, since the data model was designed for this use case.  In fact, it can be done mostly without copying the actual event data if we want, e.g. by creating a new merged file that just has HDF5 data set symlinks to the other files (which would have to be in the same directory).   So having two options for this might be nice: "copy" and  "link".  The first just creates a totally new file with merged data, and the second just creates a symlinked view of existing files, where the various telescopes are in the same place, and only the subarraydescription changes.

I guess by horizontal merging you mean not only putting all the information in one file, but also matching information from the same event from different telescopes. For this please keep in mind that we have different use cases:

if we want to match  MAGIC1 and MAGIC2 we should use the stereo event number, that it rather easy
if we want to match (one of) MAGIC telescopes with LST1 at least for the time being we need to use time, and this requires some calculated delays.
Since we want to have all possibilities (M1+LST1, M2+LST1, M1+M2) we would need both behaviours, but probably it is easier to make the code in a way that it does either 1) or 2), and then execute it twice to have all the combinations

I think what we need is just:

a way to combine HDF5 datasets from multiple files into one file (either by copying or linking). That may be even possible using the h5 tools that come with libhdf5 (not sure), but would be a pretty simple tool to write in any case.
A tool that is an off-line SWAT that can generate a new dl1.event.subarray.trigger table using either the event_id, event time, or other fields to identify coincidences between telescopes in a file.

Hi @kosack
I thought a bit about this issue with horizontal merging, in particular in the context of MAGIC+LST1, and we also discussed it today among the people involved in LST1+MAGIC analysis. As explained above matching of LST1 to MAGICs is a bit complicated, since you need to use time within a given window and apply configurable delays that can vary between runs and need to be computed first. It is different that matching the MAGIC telescopes together (that is simple because of the common stereo even number) also something that will not be (hopefully) of use to general CTA, so we thought about such a scheme:
in magic-ctapipe we can make the tricky part of assigning the MAGIC stereo trigger number of LST1 events that are matching in time, this number than be added then to the LST1 data.
In ctapipe horizontal merging can be then implemented easily using a single number (MAGIC stereo trigger number in this case, or some general array trigger number in the future) and we could then merge whatever we want, MAGIC alone, or MAGIC+LST1 or some combination of two telescopes...


Compatibility issues with Lumen 5.2.8?

I'm pretty sure I've configured this library correctly, but when I send requests into Lumen I get this exception:
[2016-08-10 22:00:36] lumen.ERROR: exception 'ReflectionException' with message 'Class alexa.router.middleware does not exist' in /srv/www/alexa-project/vendor/illuminate/container/Container.php:734
Stack trace:
#0 /srv/www/alexa-project/vendor/illuminate/container/Container.php(734): ReflectionClass->__construct('alexa.router.mi...')
#1 /srv/www/alexa-project/vendor/illuminate/container/Container.php(629): Illuminate\Container\Container->build('alexa.router.mi...', Array)
#2 /srv/www/alexa-project/vendor/laravel/lumen-framework/src/Application.php(206): Illuminate\Container\Container->make('alexa.router.mi...', Array)
#3 /srv/www/alexa-project/vendor/illuminate/container/Container.php(1174): Laravel\Lumen\Application->make('alexa.router.mi...')
#4 /srv/www/alexa-project/vendor/develpr/alexa-app/src/Provider/AlexaServiceProvider.php(97): Illuminate\Container\Container->offsetGet('alexa.router.mi...')
#5 /srv/www/alexa-project/vendor/illuminate/container/Container.php(731): Develpr\AlexaApp\Provider\AlexaServiceProvider->Develpr\AlexaApp\Provider\{closure}(Object(Laravel\Lumen\Application), Array)
#6 /srv/www/alexa-project/vendor/illuminate/container/Container.php(629): Illuminate\Container\Container->build(Object(Closure), Array)
#7 /srv/www/alexa-project/vendor/laravel/lumen-framework/src/Application.php(206): Illuminate\Container\Container->make('Develpr\\AlexaAp...', Array)
#8 /srv/www/alexa-project/vendor/laravel/lumen-framework/src/Concerns/RoutesRequests.php(362): Laravel\Lumen\Application->make('Develpr\\AlexaAp...')
#9 /srv/www/alexa-project/vendor/laravel/lumen-framework/src/Concerns/RoutesRequests.php(343): Laravel\Lumen\Application->callTerminableMiddleware(Object(Illuminate\Http\Response))
#10 /srv/www/alexa-project/public/index.php(28): Laravel\Lumen\Application->run()
#11 {main}

From what I can tell, alexa.router.middleware is only defined in the LaravelServiceProvider. In LumenServiceProvider there's a app.middleware defined instead.
I tried changing this app.middleware string to alexa.router.middleware but that led to another exception:
[2016-08-10 22:04:29] lumen.ERROR: exception 'ErrorException' with message 'Argument 1 passed to Develpr\AlexaApp\Http\Middleware\Request::__construct() must be an instance of Illuminate\Contracts\Foundation\Application, instance of Laravel\Lumen\Application given, called in /srv/www/alexa-project/vendor/develpr/alexa-app/src/Provider/AlexaServiceProvider.php on line 97 and defined' in /srv/www/alexa-project/vendor/develpr/alexa-app/src/Http/Middleware/Request.php:44
Stack trace:
#0 /srv/www/alexa-project/vendor/develpr/alexa-app/src/Http/Middleware/Request.php(44): Laravel\Lumen\Application->Laravel\Lumen\Concerns\{closure}(4096, 'Argument 1 pass...', '/srv/www/alexa....', 44, Array)
#1 /srv/www/alexa-project/vendor/develpr/alexa-app/src/Provider/AlexaServiceProvider.php(97): Develpr\AlexaApp\Http\Middleware\Request->__construct(Object(Laravel\Lumen\Application), Object(Develpr\AlexaApp\Http\Routing\AlexaRouter), Object(Develpr\AlexaApp\Request\AlexaRequest), Array)
#2 /srv/www/alexa-project/vendor/illuminate/container/Container.php(731): Develpr\AlexaApp\Provider\AlexaServiceProvider->Develpr\AlexaApp\Provider\{closure}(Object(Laravel\Lumen\Application), Array)
#3 /srv/www/alexa-project/vendor/illuminate/container/Container.php(629): Illuminate\Container\Container->build(Object(Closure), Array)
#4 /srv/www/alexa-project/vendor/laravel/lumen-framework/src/Application.php(206): Illuminate\Container\Container->make('Develpr\\AlexaAp...', Array)
#5 /srv/www/alexa-project/vendor/laravel/lumen-framework/src/Concerns/RoutesRequests.php(362): Laravel\Lumen\Application->make('Develpr\\AlexaAp...')
#6 /srv/www/alexa-project/vendor/laravel/lumen-framework/src/Concerns/RoutesRequests.php(343): Laravel\Lumen\Application->callTerminableMiddleware(Object(Illuminate\Http\Response))
#7 /srv/www/alexa-project/public/index.php(28): Laravel\Lumen\Application->run()
#8 {main}

Any thoughts or guidance would be really appreciated - this is my first time working on a Laravel/Lumen application, so I'm a bit over my head.
Edit: Removed the first exception, I think that was the result of me messing around with things.

Downgrading to Lumen 5.1.7 and develpr/alexa-app 0.2.2 seems to work (but obviously isn't ideal).  Versions 0.2.3+ seem broken, likely due to these changes: https://github.com/develpr/alexa-app/compare/0.2.2...0.2.3

Lumen 5.1.7 and develpr/alexa-app 0.2.7 play nicely if https://github.com/develpr/alexa-app/blob/0.2.7/src/Provider/LumenServiceProvider.php#L18 is changed accordingly:
-		$this->app->instance('app.middleware', $this->gatherAppMiddleware($reflection));
+		$this->app->instance('alexa.router.middleware', $this->gatherAppMiddleware($reflection));

So yeah, I'm not a Laravel/Lumen expert by any means, but it almost seems like this library simply isn't compatible with Lumen 5.2.
Would you have any objections to making this library compatible with 5.2 (and dropping support for 5.1)?

Hey @colinodell , thank you so much for taking the time to take a look at this! A few comments:

I have absolutely not problem with updating to make things compatible with Lumen 5.2
If you are willing to take a stab at it please feel free!
For what it's worth, I'm currently working on a Laravel project with the current version and things are working as they should be.. My only point being if you are not 100% married to Lumen, you should be able to use this with Laravel and it should "just work"

To be honest there hasn't been all that much interest in this and as my own projects have mainly been with Laravel lately I haven't given as much love to Lumen.
I will also try to take a look at Lumen support for 5.2/3 myself, but I'm pretty busy with work lately so it could be a bit. Again though, if you want to take a look that would be awesome!

I've ended up switching to Laravel and it does indeed work perfectly.
Not sure if you want to keep this open (should others be interested in fixing this).

I think it's worth leaving open for now. I appreciate your time. I should (and will) reflect in the docs that there is a known issue with 5.2.8 (at least) and point people here for now until it's either resolved by somebody who has a vested interest, or until I am working with Lumen again myself! Thanks again for your time with this @colinodell !


Set up initial guess generator

Function which takes in time and outputs a decision-variable-at-one-point sized vector (ndx + nu). Use inverse of Fint to transform guesses in x to the actual decision variables space (deviants of x)

Implemented in PseudospectralSegment.


toggle arrow

This toggles the arrow.
However, @Carifio24, this does something weird. The first time you click the button, it doesn't do anything. And after that it works fine. The other buttons are fine too. I am not sure why it is doing this.

@johnarban It was due to an issue in the icon button - the button was always starting with some of the state set to off, regardless of the initial v-model value. Should be fixed now.


Addcontrols

just added html controls, nothing special

ADDED CONDITIONAL BUTTON/STYLING ON JOIN LOBBY PAGE:
Only adds a column if the user is logged in.
Styling is a bit sketchy though, but for the most part 80% of the work is already done (just have to tweak the padding)
Used the modals and functions created by @JoshuaWarejko in the account page, and at first glance, it seems to work fine. Might have to fix a thing or two if I messed up though.

apparently the tests aren't passing, but the code is still working.
Console reads mysterious error, which is weird since the code seems to work fine.
ERROR in src/app/pages/join-lobby-page/join-lobby-page.component.ts(32,20): error TS2339: Property 'userLoggedIn' does not exist on type 'JoinLobbyPageComponent'.
src/app/pages/join-lobby-page/join-lobby-page.component.ts(34,20): error TS2339: Property 'userLoggedIn' does not exist on type 'JoinLobbyPageComponent'.
src/app/pages/join-lobby-page/join-lobby-page.component.ts(39,16): error TS2339: Property 'userLoggedIn' does not exist on type 'JoinLobbyPageComponent'.
src/app/pages/join-lobby-page/join-lobby-page.component.ts(43,16): error TS2339: Property 'userLoggedIn' does not exist on type 'JoinLobbyPageComponent'.
src/app/pages/join-lobby-page/join-lobby-page.component.ts(69,49): error TS2339: Property 'token' does not exist on type 'JoinLobbyPageComponent'.


Add simplistic frame pooling

As we potentially create hundreds of frames a tick, this can mean that a lot of objects are created. To reduce the number of objects that we create and destroy during cause creation, we pool the frames themselves. We pool up to 50.
This isn't yet ready for pulling, I need to do some profiling on this first. This might be slower! Just looking for any feedback - if this is no good, it's not good!
This also cleans up some of the calls for the CSM to reduce the number of calls needed. The included tests verify that the functionality is the same.

Access only arrays (even with filling the array with 50 frames on manager creation) made this a bit better, but still a little slower, still a few milliseconds in it. So, pooling is going to be slower, GC not withstanding.
I think we probably want to park this unless we think the savings from not GC-ing the objects is worth it. The object creation is just faster than access with the bounds checking we need to do, probably thanks to the JVM JIT. It would probably be faster if we could just choose the element, but we need to increment an index and check it's not above the max pool size - it looks like this kills any performance advantage.

@gabizou
So, after our discussion a couple of days ago about this and frame/context pooling, I came back to this to give it another shot. This time, I'm running on a Windows 10 machine with the latest Java 8 version, so the comparison with the previous test cannot be considered to be equal.
5 objects per frame, 100 frames pushed then popped, repeated 20000 times, test itself repeated 3 times:
With pooling (ascending order):
563522700ns (563.5ms)
616426000ns (616.4ms)
739853200ns (739.9ms)
Without:
807430600ns (807.4ms)
864693000ns (864.6ms)
873630900ns (873.6ms)
At lower volumes, 50 frames, 500 times,
With: 8174600ns (8.1ms)
Without: 11500800ns (11.50ms)
And 100 frames, 500 tiems:
With: 13388200ns (13.3ms)
Without: 15654400ns (15.65ms)

The times with the pooling are a lot more variable but generally lower than non-pooled, though negligible as we get to fewer frames. The memory usage was also that little bit lower. GC pauses should be lower with the pooling too. So, I think this bodes well for looking at doing this with the phase tracker too, especially if some of the data in the states can also remain within the pooled/cached objects.

https://github.com/SpongePowered/SpongeCommon/commit/ce6928471b1a88515a405210fc6637b6a9028ef0


MaskGenerator can't be run on a DataContainer

Description
This is because of the line:
https://github.com/TomographicImaging/CIL/blob/5d569dc054759a8c137ca72611fc7be07be6080e/Wrappers/Python/cil/processors/MaskGenerator.py#L377
A DataContainer doesn't have a geometry so it throws an error that you can't copy a None.

[ ] Fix the issue by doing a check on if it has a geometry before trying to copy
[ ] Add a unit test for using a MaskGenerator on a DataContainer
[x] Check if there's a similar issue on other processors which may want to run on a DataContainer

Current workaround is to use argument out - then it doesn't encounter this line of code

Environment

import cil, sys
print(cil.version.version, cil.version.commit_hash, sys.version, sys.platform)

I believe this is the only processor we need to update.
Note: its a common usecase to run this processor on a DataContainer e.g. a DataContainer of flat fields.
Less common to run other processors on DataContainers
Worth noting the .copy on geometry was added to the MaskGenerator in this PR https://github.com/TomographicImaging/CIL/commit/66206d335effbf872ac23aa642cc0ea313d347d8

Closed by #2001


Support ttnn.pow with exponent tensor

Currently ttnn.pow only support a singe float/int as the exponent, while to convert aten.pow.Tensor_Tensor, we will need to support tensor as exponent
I think it will be easier to support this on tt-metal side by adding new API/kernel

We also found the ttnn.pow currently only support integer exponent https://github.com/tenstorrent/tt-metal/blob/7ba291dbcbca8ea4a7fd9b67cbe4720d8e3d8f49/tt_metal/hw/ckernels/wormhole_b0/metal/llk_api/llk_sfpu/ckernel_sfpu_power_iterative.h

Even if we only need integer support, we can still optimize it to binary exponentiation.  But I guess you prefer a general floating-point implementation.


As a developer/curator I need IRIs for data concepts to unambigously map my data to CoLDP

As a developer, and user, I need to unambiguously link my data model to a CoL data concept.
For example, in TaxonWorks there is no "extinct" field on an OTU.  However, a data curator can extend the OTU data model by creating data predicates.  Those predicates can in turn be cross referenced to an ontology term via IRI/URI, "my predicate has this meaning".
We need IRIs so that TaxonWorks CoLDP exporter (and others I'm sure) can unambiguously identify that the data predicate attached to the OTU is in fact a field that should be included in a specific field in the CoLDP export.
Providing IRIs for those concepts will essentially pre-adapt the data model for consumption in the OWL/bioportal/obofoundary model as well.
Example:
Taxon#extinct -> URI for concept should look (something) like http://api.catalogue.life/vocab/extinct or http://api.catalogue.life/vocab#extinct  or http://api.catalogue.life/vocab/iri/exting.  Probably completely doable with the documentation/schema approach you are using?
Example in DWC:
http://rs.tdwg.org/dwc/iri/earliestGeochronologicalEra.  Let's TW  users create Predicate with this URI, and lets use dump that fact to CSV if provided.
Example in OBO/OWL
http://bioportal.bioontology.org/ontologies/FISHO#FISHO_0000122 -> extinct!

We have URIs for each ColDP term we are using, very similar to DwC.
They are managed in a Java enumeration that defines a basic namespace and provides a simple, prefixed and fully qualified name (which is a URI) for the term. It also knows whether a term is a "class" term or a "property". Following DwC and DC conventions the property terms a lowerCamelCase, the class terms UpperCamelCase.
The list of all know terms are exposed in the vocabulary API:
http://api.catalogue.life/vocab/terms
You can filter the terms for a certain prefix, which is an alias for a namespace:
http://api.catalogue.life/vocab/terms?prefix=col
You cannot resolve each term right now, but I will add that today, it's trivial:
http://api.catalogue.life/vocab/terms/col:extinct
The resulting qualified name or URI for the coldp extinct term in any case is:
http://catalogueoflife.org/terms/extinct

Do they need to resolve to anything specific?

Btw, the official term IRI for DwC is http://rs.tdwg.org/dwc/terms/xxx, e.g. http://rs.tdwg.org/dwc/terms/earliestEraOrLowestErathem
The dwc/iri ones are later RDF additions that take as values also IRIs as you probably know.

@mdoering thanks for jumping on this, and clarifying IRI vs values.  Working with @gdower we were looking for http://api.dev.catalogue.life/vocab/term/col:extinct, but I think I want the qualified name here.  Will the qualified name resolve to something ultimately.
For the record I don't need think it needs to resolve to anything specific, I just want to use it as a concept identifier.

Yes, http://api.dev.catalogue.life/vocab/term/col:extinct is supposed to be a IRI to be used to refer to coldp:extinct. The qualified name is exactly for that. We might resolve it at some point, probably to the API response for JSON and some RDF we still need to craft.
Also note that the catalogue.life domain in temporary and we will move everything incl the API to catalogueoflife.org at some point this year.


Search and Navigate directly to a skill input does not have an associated label or aria-label attribute

Input field needs an associate label or aria-label attribute to indicate what the field's intent is to screenreader users.

completed as part of #190


Didn't install HENkaku

The h-encore bootstrap works fine. I can install the Vitashell but wen i install HENkaku they say success then i go to the settings and the HENkaku menu dind't exist so i go back to h-encore and reset the taiHEN config.txt and try to reinstall the HENkaku but it's always the same. How i can fix that? By the way i had install HENkaku befor at the firmware 3.60

what firmware Are you on

3.68

Format your memory card

Now it's working. Thank you :)


Add new environment variables

Add new environment variables for configuring long-season space name and city name.
Described richer in #24.

Closes #66 and #65


Update the project to version 3, plus add resources

The PROJECT layout was left behind, updating it to comply to version 3.

cc @sabinaaledort

/lgtm

did u try another resource with this change ? this what I get when I ran it
operator-sdk create api --group=metallb.io --version=v1alpha1 --kind=AddressPool --resource --controller
FATA[0000] failed to read config: error unmarshalling project configuration: error unmarshaling JSON: while decoding JSON: json: unknown field "projectName"

so I changed back to what it was originally that went further and created the objects but gave an error towards the end
Error: failed to create API with version "3-alpha": exit status 2

I have installed this version on fedora33
operator-sdk version
operator-sdk version: "v0.19.4", commit: "125d0dfcc71fef4f9d7e2a42b1354cb79ffdee03", kubernetes version: "v1.18.2", go version: "go1.13.15 linux/amd64"

maybe I need different version ?

Yes I tried before pushing this pr.
I am using the latest which is
operator-sdk version: "v1.8.0", commit: "d3bd87c6900f70b7df618340e1d63329c7cd651e", kubernetes version: "1.20.2", go version: "go1.16.4", GOOS: "linux", GOARCH: "amd64"

following https://sdk.operatorframework.io/docs/installation/#install-from-github-release

@msherif1234
operator-sdk create api --group metallb.io --version v1alpha1 --kind SecondResource --resource --controller
Writing scaffold for you to edit...
api/v1alpha1/secondresource_types.go
controllers/secondresource_controller.go
Update dependencies:
$ go mod tidy
Running make:
$ make generate
/home/fedepaol/go/bin/controller-gen object:headerFile="hack/boilerplate.go.txt" paths="./..."


fix(versions): update Activiti/activiti-cloud-runtime-bundle-service versions into develop

UpdateBot pushed maven dependency: org.activiti.dependencies:activiti-dependencies to: 7.1.95

UpdateBot commands:
updatebot push-version --kind maven org.activiti.dependencies:activiti-dependencies 7.1.95 org.activiti.api:activiti-api-dependencies 7.1.50 org.activiti.core.common:activiti-core-common-dependencies 7.1.57 org.activiti.build:activiti-parent 7.1.28


Issue with screenshots for the failed tests

Hi! I've experienced issue with screenshots display in the Cucumber-JVM-Reports:
if there are 2 failed tests in a suite, 1 screenshot for each test and screenshots look the same visually and a size is the same, then link to the 2nd screenshot doesn't work: link to the 2nd screenshot expands/collapses the 1st screenshot.

Is it a feature or a bug?

Does the issue occur if you do not use the parallel plugin?
This looks like an underlying issue with the HTML reports - they are out of scope for the parallel plugin itself, as it just uses the underlying mechanism.


Decref not releasing memory

Hello.
I am working on a project with nRF52862 mcu and it is doing some thing gateway stuff.
I am creating a json and fill it with some metadata and sensor datas.
I can successfull create json object. And send it over gsm to the cloud.
Then i should update json file. But as i understand that is not possible for me.
So i am using decref function to create all over it again.
But when i recreate second json object (which it is an array) it allocates more memory compare to the before.
Every recreate takes more memory, and then finaly hardfault exception happens.
How can i completly delete json object?My object something like:
{"gw_id": "A0:82:A7:6F:BD:9A:39:2B", "imei": "867521029181135", "gw_rssi": -89, "gw_bat": 4794, "periph": [{"name": "ViLE-Env", "rssi": -69, "srv": [{"s_uuid": "181A", "char": [{"uuid": "2A6D", "val": 9971.3}, {"uuid": "2A6E", "val": 28.42}, {"uuid": "2A6F", "val": 64.0}, {"uuid": "806A", "val": false}]}]}, {"name": "ViLE-Distance", "rssi": -43, "srv": [{"s_uuid": "FEFA", "char": [{"uuid": "8007", "val": 99}]}]}, {"name": "ViLE-Acc", "rssi": -64, "srv": [{"s_uuid": "FF00", "char": [{"uuid": "8000", "val": 496}, {"uuid": "8001", "val": -400}, {"uuid": "8002", "val": 7904}]}]}]}

Decref releases memory when the reference count reaches 0.  I use jansson in Asterisk PBX, if jansson had the bug as you suggest Asterisk developers would absolutely know.  It's difficult to say what you are doing wrong without seeing code.  You are failing to decref an object or you are using a 'bump reference' variant of a function where you should use a reference stealing function.

You are using json_object_set but you need to use json_object_set_new.  json_string() creates an object with 1 reference held, then json_object_set adds another reference.  Same goes for json_array_append, you need the _new variant if you want the array to steal the creation reference.
See https://jansson.readthedocs.io/en/2.11/apiref.html#c.json_object_set_new
Also take a look at json_pack - this function would allow you to write much more compact code.


A backend based on Process.spawn

Process.spawn is the official Ruby core API for spawning subprocesses, and I think it has all features needed to implement ChildProcess on top of it.
I think it is the best way to implement ChildProcess, as it is an official Ruby core API supported by all Ruby implementations, and other backends could actually be removed as they would be redundant.
Process.spawn exists for longer than I can remember and certainly since Ruby 2.4, so I think it should work on all supported Ruby versions (https://github.com/enkessler/childprocess#requirements)
From https://github.com/oracle/truffleruby/issues/1525#issuecomment-445780033
From that note, posix_spawn is unsafe because it might Dir.chdir() concurrently to some other thread executing some code relying on the cwd. And fork is of course not portable. So Process.spawn seems better than both backends.

Hey @eregon—supportive of the request, though would prefer this be contributed by folks whose use case necessitates it so they can test it in a real-world scenario.
I don't have context on why the original ChildProcess backends were chosen over Process.spawn, but I assume there was some reason. Would be happy to review a tested pull request implementing this functionality.

I don't have context on why the original ChildProcess backends were chosen over Process.spawn, but I assume there was some reason.

I don't know for sure, but I would bet it's because ChildProcess already existed in the Ruby 1.8 area, and Process.spawn didn't exist then (it was added in Ruby 1.9, just checked).
There were still patch releases of 1.8 in 2010 when the project was started: https://github.com/enkessler/childprocess/tags?after=v0.1.1, so it seems a likely reason.

I'll try to find some time to make a prototype but if anyone else is interested, go ahead and just mention it.

Here is a prototype, and it already passes all the specs, at least on Linux: https://github.com/enkessler/childprocess/compare/master...eregon:process-spawn
I would think it works fine on Windows too, however the superclass is Unix::Process so there might be some assumptions there.

If Ruby itself has gotten better about cross-platform process handling, I'd be perfectly content for childprocess to become just a more convenient API on top of the core library instead of it having to handle a lot of the more 'fiddly' stuff that might have been needed back in the day.

https://github.com/enkessler/childprocess/pull/175 already works well on UNIX, but not yet on Windows.
I don't have a Windows dev machine, so that's rather impractical as I'd need to wait for CI to know if something works or not.
Maybe I can try to force it to take the Windows branch locally for faster development.
Are constants like ChildProcess::Unix considered public API or not? I guess not given they are conditionally defined based on the current platform.

Update: it works on Windows now, there are only 2 failures left: https://github.com/enkessler/childprocess/pull/175#issuecomment-864585821
And the diff is +166 −2,045.

A couple thousand fewer lines of code to have to worry about is nice!

The second is the issue that there is no builtin way to kill a process group on Windows.

Would it be possible to incrementally replace the internal implementation? Swap the OSX and Linux parts because core Ruby works fine but keep the Windows specific functionality in place until we can work out those last failures?

Would it be possible to incrementally replace the internal implementation? Swap the OSX and Linux parts because core Ruby works fine but keep the Windows specific functionality in place until we can work out those last failures?

I would prefer removing all platform-specific code, that's so much better for maintenance and guarantees it works reliably.
Also IIRC it's not trivial to keep the Windows part but not the rest without incurring a lot of complexity and copying classes etc (but I'd need to look into it again).
That would mean no longer supporting killing a process group on Windows (already not supported with process_builder).
I think we should raise an error in that case.
Does anyone use that?
I think it would be a fair enough change for a new major version of the gem given the most likely very low usage.
What do you think?
BTW, this issue keeps coming up, notably because selenium and other gems don't work without setting CHILDPROCESS=1 on TruffleRuby (https://github.com/oracle/truffleruby/issues/1525).

I forgot, another advantage is Process.spawn is faster than fork+exec as currently used by child_process, because that can use vfork() or posix_spawn() for instance which needs to copy less from the parent process.

Would it be possible to incrementally replace the internal implementation? Swap the OSX and Linux parts because core Ruby works fine but keep the Windows specific functionality in place until we can work out those last failures?

I gave it a try to keep the existing logic for JRuby and Windows backends, but that seems to only results in more test failures, so I don't see the point: https://github.com/eregon/childprocess/tree/process-spawn-non-windows https://github.com/eregon/childprocess/actions/runs/4235173639
Also see my comment at https://github.com/enkessler/childprocess/pull/175#issuecomment-1438858034.
Could we merge https://github.com/enkessler/childprocess/pull/175#issuecomment-1438858034 ?
I think to address that one last failure on Windows we just need to exclude that test on Windows, it doesn't work on master either anyway.

Thank you for your efforts here. Merged in #175.


[US] As a user, I want to have a multichain Explorer, regardless of the networks where Verax is deployed

[!NOTE]
This needs to be merged onto the feat/multichain branch

Current behaviour
Today, the Explorer can only display data for one given network at a time.
Technically speaking, the SDK is instantiated to target one single network, and the URLs when navigating contain the network's name.
Tasks to cover

[ ] Upgrade to SDK V3 ("Multichain mode")
[ ] Instantiate the SDK in only 2 modes ("Testnet" to get all testnet data, "Mainnet" to get all mainnet data)
[ ] Stop considering the network name when reading the URLs path
[ ] Remove the network name when creating the URLs
[ ] Remove the networks dropdown selector from the header navbar
[ ] Add a toggle selector in the header navbar to switch between testnets and mainnets
[ ] Mainnets are selected by default

can i try this?

can i try this?

Yes you can!
Make sure you start from the feat/multichain branch instead of the usual ˋdev` branch 😉

so i have to fork feat/multichain branch right? for this issue?

so i have to fork feat/multichain branch right? for this issue?

Yes, this is the branch with the preview version of the SDK, supporting the multichain calls.


Form validation

INVALID ❌ ❌ ❌
Hi @Christelle-12   👋
While you made a great effort in this project, I can't go ahead and review your code.
Invalid Code Review Request ❌
You have submitted a PR that doesn't have a description explaining the changes made 😨 Kindly add a description to your PR

Your Code Review Request will be marked as invalid in your Dashboard, so please submit a new one once you are ready 🙏
Kindly create  a new PR that follows the Gitflow approach
Cheers and Happy coding!👏👏👏
✅ Feel free to leave any questions or comments in the PR thread if something is not 100% clear.
Remember to tag me in your question so I can receive the notification.
⚠ Please, do not open a new Pull Request for re-reviews. You should use the same Pull Request submitted for the first review, either valid or invalid unless it is requested otherwise.

Invalid Code Review Request does not count into the code reviews limit.


[Test] Do not load string processing when recovery is disabled

This test specifically disables serialization recovery, but that can
cause issues when loading the experimental string processing library. We
don't use it in the test, so just disable it for now.

@swift-ci please test

I expect the string processing library to still be loaded indirectly in this case. Does indexing ignore indirect dependencies?

@swift-ci please smoke test

I expect the string processing library to still be loaded indirectly in this case. Does indexing ignore indirect dependencies?

Ah, thanks. I've disabled in lib/lib2 as well.

@swift-ci please smoke test macOS platform

@swift-ci please smoke test


Builds uploaded with pilot and distributed with the groups option are not submitted for review.

New Issue Checklist

[x] Updated fastlane to the latest version
[x] I read the Contribution Guidelines
[x] I read docs.fastlane.tools
[x] I searched for existing GitHub issues

Issue Description
Complete output when running fastlane, including the stack trace and command used

04:09:59 [04:09:59]: Build doesn't show up in the build list anymore, waiting for it to appear again
04:10:30 [04:10:30]: Successfully finished processing the build *redacted*
04:10:30 [04:10:30]: Distributing new build to testers: *redacted*
04:10:31 [04:10:31]: Successfully distributed build to Internal testers 🚀
Builds we upload with fastlane with the intent to distribute to a "Nightly Testers" group don't seem to be submitted for review. When logging into iTC, the builds appear as waiting for review. However, the logging seems to indicate that the distribute_build method is hit, which would normally indicate that the build would be submitted for review.
Environment

Using a Gemfile with fastlane 2.80.0
Lane that uploads to TestFlight is the following:
  ipa_path = *redacted*
  pilot(
    ipa: ipa_path,
    distribute_external: false,
    skip_waiting_for_build_processing: options[:skip_waiting_for_build_processing], <- false
    wait_for_uploaded_build: true,
    changelog: "Bug fixes",
    beta_app_description: "Nightly Build",
    beta_app_feedback_email<EMAIL_ADDRESS>    groups: ["Nightly Testers"])

I'm wondering what's the best way to debug this? Should I open up a PR that adds some more logging around this part of the code? Has anyone had this issue on 2.80.0?

Will look into 👌

Thanks @joshdholtz. There's an update on my end, it seems like we're hitting some some form of #11828. The first build of a new app version is submitted for review correctly and then subsequent builds only manage to get into the "Approved" state before getting a 504 and making fastlane fail.

I'll close this in favor of #11828


Can't override default mapper for CaseClassMappingException

Not able to override the default mapper for CaseClassMappingException in the ExceptionManager.
Expected behavior
According to the documentation: "If a user wants to swap out any of these defaults they simply need add their own mapper to the manager for the exception type to map."
Actual behavior
Adding a mapper to CaseClassMappingException throws the following exception:
java.lang.IllegalStateException: ExceptionMapper for class com.twitter.finatra.json.internal.caseclass.exceptions.CaseClassMappingException already registered
	at com.twitter.finatra.http.internal.exceptions.ExceptionManager.add(ExceptionManager.scala:65)
	at com.twitter.finatra.http.internal.exceptions.ExceptionManager.add(ExceptionManager.scala:53)
	at com.twitter.finatra.http.routing.HttpRouter.exceptionMapper(HttpRouter.scala:42)

Looking at finatra source code, [ExceptionManager.scala] (https://github.com/twitter/finatra/blob/v2.1.5/http/src/main/scala/com/twitter/finatra/http/internal/exceptions/ExceptionManager.scala#L64-L66) checks if the mapper already contains the Throwable and if so, it throws an Exception.
Steps to reproduce the behavior

Through the HttpRouter, add a new Exception Mapper. E.g:
.exceptionMapper[MyCaseClassMappingExceptionMapper]

Create ExceptionMapper

class MyCaseClassMappingExceptionMapper @Inject()(response: ResponseBuilder) extends ExceptionMapper[CaseClassMappingException] with Logging {

  override def toResponse(request: Request, ex: CaseClassMappingException): Response = {
    logger.info(ex.getMessage)
    response
      .badRequest(Map(
        "code" -> 404,
        "message" -> ex.getMessage
      ))
  }
}

And run the application. Exception thrown in during initial boot sequence.

I think this has been fixed in the commit part of the develop branch: https://github.com/twitter/finatra/commit/36afd2c4f0dfa29108e336bdd60a534a414a9a28
The comments of the commit match the documentation available.
I'm using v2.1.5, the latest available at the moment.

Hi @netrebel, the latest version of Finatra is v2.5.0. That is why the documentation does not match with what you're using.
Previously, users had to override the exceptionMapperModule in their server to control this behavior, but as you found via the docs, that is no longer the case.

@netrebel the latest available version of Finatra is version 2.5.0

Duplicate of #346.


Corrections and additions

Correct the envar spelling and add few options
Allow the build to save the Slurm and CentOS7 builds as
separate images so we can select between them. Correct
the spelling of the PRTE envars so PRRTE recognizes them.
Add a few missing envars, and setup the RPMBUILD directories
as they prove useful.
Add CentOS8 image script
Signed-off-by: Ralph Castain<EMAIL_ADDRESS>

This looks good to me, but I'll hold off merging until @icompres reviews since it impacts PR #11


Add autodetect parameter to BigQueryLoadTask (#2363)

Description
When schema is not provided try to use autodetect parameter.
Removed comment that implicates that it doesn't work for JSON
(docs linked below explicitly says it works for JSON)
Motivation and Context
It solves: https://github.com/spotify/luigi/issues/2363
Have you tested this? If so, how?
I ran my jobs with this code and it works for me.
It also matches description of configuration.load.autodetect
in docs https://cloud.google.com/bigquery/docs/reference/rest/v2/jobs#configuration.load

Hey! Anybody will have time to check this one out or let's agree to close it? Regards.

I have merged current master.
I don't think this change would be testable in unit tests, maybe in some integration tests.


Support the passing of a time rule positionally on the date_rule arg

When the user calls schedule_function(func, a_time_rule), assume that the user meant to specify a time rule but no date rule, instead of a date rule and no time rule as the signature suggests

Coverage increased (+0.004%) to 81.69% when pulling 6bec56f2ea6fbc9582178186b5ef00951a4e8c84 on schedule_func_args into 96ec1fd639cf8310ffe978af441e8053cc796237 on master.

@lianga888 @llllllllll what's the status of this?

@jean, waiting for travis then merging


SublimeLinter cannot read environment variables

SublimeLinter doesn't seem to be able to read environment variables. Specifically, it does not seem to read the $PATH and $HOME variables. Is it supposed to be able to?
If I install eslint locally (in a package.json), it works fine. It lints like it should.
If I am trying to use my global installation of eslint, it does not work. After some trial and error, I found out that if I set an absolute path in SublimeLinter's paths setting, it works. Like this:
"paths": {
    "linux": [
        "/home/dan/.npm-packages/bin"
    ],
    "osx": [],
    "windows": []
},

If I try to use the $HOME variable, it does not work. Like this:
"paths": {
    "linux": [
        "$HOME/.npm-packages/bin"
    ],
    "osx": [],
    "windows": []
},

It seems odd to me. I should add that I'm using zsh and that I'm setting up my $PATH string/$path array in .zshenv, not .zshrc or .zprofile. I also have the same $PATH settings in a .bashrc file, just in case. This is correct though because eslint <file> from Terminal works (with both zsh and bash).
Let me know if I should put this issue in the SublimeLinter repo itself instead.
SublimeLinter console output
Help: Check menu item Tools -> SublimeLinter -> Debug Mode, then check menu item View -> Show Console, then menu item Tools -> Sublime Linter -> Lint This View.
warning: mnemonic t not found in menu caption Tools
Traceback (most recent call last):
  File "/opt/sublime_text_3/sublime_plugin.py", line 258, in on_load_async
    callback.on_load_async(v)
  File "SideBar in /home/dan/.config/sublime-text-3/Installed Packages/SideBarEnhancements.sublime-package", line 70, in on_load_async
  File "/opt/sublime_text_3/sublime.py", line 159, in decode_value
    raise ValueError(err)
ValueError: Error trying to decode value: Unexpected character, expected a comma or closing bracket in (data):55:4
SublimeLinter: WARNING: eslint deactivated, cannot locate local or global binary
SublimeLinter: ERROR: eslint cannot locate 'eslint'
SublimeLinter: WARNING: eslint deactivated, cannot locate local or global binary
SublimeLinter: ERROR: eslint cannot locate 'eslint'

eslint output from command line
Help: Use the same eslint instance which plugin uses (check console output). Run in terminal:
cd your_project_folder
eslint some/file.js # if eslint is global
./node_modules/.bin/eslint some/file.js # if eslint is local

...
✖ 250 problems (250 errors, 0 warnings)

Additional info if needed (ST version, OS, configuration)
Sublime Text 3
Linux (Arch Linux)
Zsh

IME on OS X, Sublime in general does not seem to read any shell .*rc files.
This SO post seems to corroborate: http://stackoverflow.com/a/24311110/344143

@GreenRaccoon23 In general SublimeText and SublimeLinter treat system variables their own way and I am not sure if you can use them in configs (suppose you can't). It is an issue for Sublime Text or Sublime Linter itself, I suppose. I myself use absolute path in paths. Also you can try to check here http://www.sublimelinter.com/en/latest/usage.html#how-linter-executables-are-located, probably it will help you to change $PATH somewhere in system and skip SublimeLinter config.

Having the same issue. It seems "mnemonic": "t" must be changed to "mnemonic": "T", https://github.com/eddiejessup/Transcrypt/issues/4


[TA] enable verifytypes

API change check
APIView has identified API level changes in this PR and created following API reviews.
azure-ai-textanalytics


I18Manager is not forcing RTL on app launch but works when restarting the app.

Description
using I18nManager.forceRTL is not forcing whatever boolean value I give on app launch and require the app to restart in-order to apply the direction, this wasn't happening on 0.64.1
Version
0.66.1
Output of react-native info
System:
OS: macOS 12.0.1
CPU: (8) arm64 Apple M1
Memory: 242.44 MB / 16.00 GB
Shell: 5.8 - /bin/zsh
Binaries:
Node: 16.3.0 - /opt/homebrew/bin/node
Yarn: 1.22.10 - /opt/homebrew/bin/yarn
npm: 7.23.0 - /opt/homebrew/bin/npm
Watchman: 2<IP_ADDRESS> - /opt/homebrew/bin/watchman
Managers:
CocoaPods: 1.10.1 - /opt/homebrew/bin/pod
SDKs:
iOS SDK:
Platforms: DriverKit 21.0.1, iOS 15.0, macOS 12.0, tvOS 15.0, watchOS 8.0
Android SDK:
API Levels: 28, 29, 30
Build Tools: 29.0.2, 30.0.2, 30.0.3
System Images: android-30 | Google APIs Intel x86 Atom
Android NDK: Not Found
IDEs:
Android Studio: 2020.3 AI-203.7717.56.2031.7784292
Xcode: 13.1/13A1030d - /usr/bin/xcodebuild
Languages:
Java: 1.8.0_292 - /usr/bin/javac
npmPackages:
@react-native-community/cli: Not Found
react: 17.0.2 => 17.0.2
react-native: 0.66.1 => 0.66.1
react-native-macos: Not Found
npmGlobalPackages:
react-native: Not Found
Steps to reproduce
add the code below anywhere in app.js
    I18nManager.allowRTL(true);
    I18nManager.forceRTL(true);
    I18nManager.swapLeftAndRightInRTL(true);

expected outcome:
the app to launch in RTL layout

actual outcome:
the app is not changing the layout to RTL

Snack, code example, screenshot, or link to a repository
No response

Any updates

Seeing same problem.
When using RNRestart to reload the app it respects RTL, but when closing the app down then re-open it doesn't work.

Can confirm https://github.com/facebook/react-native/commit/fcead14b0effe2176a5d08ad50ee71e48528ddbd is changing this behaviour. Is there some workaround for this or is this the expected behaviour going forward? cc @Saadnajmi

Yes, my last change to il8n manager does cause that behavior. We can revert it if need be. What scenario did you need to force RTL for, out of curiosity?

Yes, my last change to il8n manager does cause that behavior. We can revert it if need be. What scenario did you need to force RTL for, out of curiosity?

@Saadnajmi we have support for arabic language in our app thus the app must be running in RTL mode so no matter what the scenario is, the user must always see the app in RTL layout from the very beginning of the app lifecycle, the change is forcing the app to launch in LTR mode and requires a restart to flip it back to RTL after the initial launch, which is absolutely not an option in our case, restarting sometimes causes crashes, we are holding off the upgrade for our app for now until this gets resolved

Thanks for replying @Saadnajmi ! We offer an app in several languages (some LTR, some RTL). After user has updated its preferences regarding language, we of course respect that on app launch. With current behavior app will start in LTR mode even if an RTL language is selected. Since it’s not RTL only we can’t force RTL in AppDelegate for example.
Reverted back to RN 0.65.2 but hopeful we can get previous behavior back in coming releases.

I see. As an Arabic speaker I understand. I thought that if the app launched with an RTL language, RN would launch with RTL without needing il8nManager to force it. I'm kind of surprised that's not the behavior. I'll try to send a PR reverting my change. Apologies for the mismatch in behavior!

@Saadnajmi thank you!


[0.27] 'JLinkProbe' object has no attribute '_lock'

Using version 0.27 and JLink, session.open() throws the error below. The previous version was working fine for me.
with ConnectHelper.session_with_chosen_probe() as session:
Traceback (most recent call last):
-truncated-
File "C:\xxx\pycharm\lib\site-packages\pyocd\core\session.py", line 302, in enter
self.open()
File "C:\xxx\pycharm\lib\site-packages\pyocd\core\session.py", line 420, in open
self._board.init()
File "C:\xxx\pycharm\lib\site-packages\pyocd\board\board.py", line 85, in init
self.target.init()
File "C:\xxx\pycharm\lib\site-packages\pyocd\core\coresight_target.py", line 160, in init
seq.invoke()
File "C:\xxx\pycharm\lib\site-packages\pyocd\utility\sequencer.py", line 213, in invoke
resultSequence.invoke()
File "C:\xxx\pycharm\lib\site-packages\pyocd\utility\sequencer.py", line 208, in invoke
resultSequence = call()
File "C:\xxx\pycharm\lib\site-packages\pyocd\coresight\dap.py", line 359, in power_up_debug
self.write_reg(DP_CTRL_STAT, CSYSPWRUPREQ | CDBGPWRUPREQ | MASKLANE | TRNNORMAL)
File "C:\xxx\pycharm\lib\site-packages\pyocd\coresight\dap.py", line 348, in write_reg
self.write_dp(addr, data)
File "C:\xxx\pycharm\lib\site-packages\pyocd\coresight\dap.py", line 528, in write_dp
did_lock = self._set_dpbanksel(addr, True)
File "C:\xxx\pycharm\lib\site-packages\pyocd\coresight\dap.py", line 480, in _set_dpbanksel
self.lock()
File "C:\xxx\pycharm\lib\site-packages\pyocd\coresight\dap.py", line 252, in lock
self.probe.lock()
File "C:\xxx\pycharm\lib\site-packages\pyocd\probe\debug_probe.py", line 173, in lock
self._lock.acquire()
AttributeError: 'JLinkProbe' object has no attribute '_lock'

Thanks for the report!


version6.1.0 : copy then paste, format not good

##copy some code,then paste,format bad!
###copy format:
{
    "name":"singi",
    "notlike":"version 6.1.0"
}

###paste format
{ "name":"singi", "notlike":"version 6.1.0" }

##may I paste the same as copy?just do as old version,you do!
###thank you for your working.

This is a duplicate of #83.
I'm closing this one, we are working on it.


Updated guidance

Is there a more updated guidance for 2021? Specifically, is ACI recommended for any app model at all, or is it better to just go with AKS (our app model is more N-Tier app / microservices architecture)

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

ID: 45be6d71-575d-5d8d-bcdc-b6885ddbb487
Version Independent ID: 7c37b77a-63fc-4fb4-ae32-02ac9c09e1c8
Content: Choosing Azure compute platforms for container-based applications
Content Source: docs/architecture/modernize-with-azure-containers/modernize-existing-apps-to-cloud-optimized/choosing-azure-compute-options-for-container-based-applications.md
Product: dotnet-architecture
Technology: modernize-with-azure-containers
GitHub Login: @nishanil
Microsoft Alias: nanil

Hi @sathiathirumal , thank you for your feedback.
We had an internal discussion on this topic and could find that the content mention in the table seems to be right.
But yes, it will be useful if there is more information in terms of choosing different services. And for that reason, we have included the link of Choose an Azure compute service for your application in the additional resource section.  It will be helpful for you to decide on the right choice of Azure Compute service based on your requirement.
Hope this helps !


Change Dockerfile

because latest one breaks this bot

I'm sorry, but this is a mess. I don't see any Dockerfile changes. Closing.


yesod-bin: fix to work with GHC 8.0.1

Motivation for this change
yesod devel does not work with GHC 8.0.1
https://github.com/yesodweb/yesod/issues/1284
Things done

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

[x] NixOS
[ ] OS X
[ ] Linux

[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Fits CONTRIBUTING.md.

I guess you have to use the correct commit style for update commits.
e. g. yesod-bin: <IP_ADDRESS> -> <IP_ADDRESS>

done

The Hackage package set is automatically generated from upstream at regular intervals, so this will be fixed by itself the next time that happens.

The various haskell-modules/configuration-*.nix files is the right place for manual overrides.


To-do List (version 0.2.0)

[ ] video
[ ] file
[ ] box insertion (/ shortcut, toolbar icon)
[ ] mention
[ ] special characters
[ ] emoticons
[ ] formula
[ ] map
[ ] table editing

todo list (2024.4.29)

[ ] fix(code block): dropdown menu is not fully visible
[ ] fix(toolbar): dropdown should use the center point to determine displaying direction
[ ] feat(toolbar): toolbar can be placed at the bottom of the content
[ ] feat(editor): add placeholder

2024.4.29

[ ] fix(markdown): should not insert code block when inputting less than three colons
[ ] feat: support drag-and-drop feature used to moving a block or a box

2024.5.1

[ ] fix: does not scroll to active line after pressing enter key

2024.5.4

[ ] fix: cannot copy or cut an image

Is there a plan to support LaTex maths formulas?

Is there a plan to support LaTex maths formulas?

There is, but its priority is not very high. I need to support other features before it.

2024.5.9

[ ] fix(image): lose focus when zooming in the iOS

2024.6.17

[ ] fix(code block): scroll to the top after selecting language

version 0.2.0 has been released.


api, labels: pair hash with EndpointSelector, LabelArray

Upon creation of a LabelArray, store the hash of the contents of the
LabelArray within a new type, LabelArrayWithHash. This hash is based off
of the SHA256Sum of the sorted labels in the LabelArray. Simillarly, add a
new field, hash, to EndpointSelector. This hash is currently based on the
String() function within the LabelSelector. This function sorts the
Labels within the LabelSelector, but does not sort the
MatchExpressions field, which means that there is a case where two
instances of the equivalent LabelSelector, but with different ordering of
their`MatchExpressions` are hashed, the hash will be different.
Adding a hash to EndpointSelector is performed upon its creation. This
allows for caching of information about multiple EndpointSelector with the
same labels for aggregating information related to policy, e.g., what identities
are selected by a given EndpointSelector.
Signed-off by: Ian Vernon<EMAIL_ADDRESS>

This change is

test-me-please


Verify that we cannot register a IMixedRealitySystem twice

XRTK - Mixed Reality Toolkit Bug Report
Describe the bug

There may be a regression when registering IMixedRealitySystems more than once. We should write test cases to test this and verify.
To Reproduce

Create two implementations of the same IMixedRealitySystem
Try to manually register them using the Service Locator APIs
Ensure an error is raised when the second system is registered

Expected behavior

Only one system can be registered at a time
Actual behavior

We have no idea. We need test this case.

Thinking I should write the unit test in #765


Suggestion: Order channels alphabetically

Algorithm behind current order is unclear. Workspace has 100+ channels. Hard to find a needle in a haystack in Clicky currently.

At the moment there's no sorting, they're displayed in the same order they're returned from Slack.
On 8 Aug 2018, 20:32 +0200, Terris Linenbach<EMAIL_ADDRESS>wrote:

Algorithm behind current order is unclear. Workspace has 100+ channels. Hard to find a needle in a haystack in Clicky currently.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

There seems to be some Slack intelligence behind it


SMS Backup start date

When I backed up my phone I had about 57,000 texts. It took about 16 hours to complete. I looked in my gmail and it seemed like maybe there wasn't all of them there so I looked. Sure enough, the texts only start from January 16, 2013. I have texts from well before then that never got backed up. I checked and made sure that in the advanced options there wasn't anything selected limiting my texts; i.e. "all" was selected for how many to back up instead of, say, 100. It's backing up new SMS as they come in just fine, but the oldest messages are ignored.
I need all of my texts backed up so I can print some of them out for court.
This is also something I noticed but not important. I don't think a single MMS was backed up since I didn't see a paperclip icon next to any of the conversation threads.
My phone is a HTC Droid something, running Ice Cream Sandwich. I'm sorry I can't be more specific than that. It's from Verizon if it helps.

Same thing here except I have very little texts (possibly less than 100) and yet I'm missing around a dozen texts before 2014-07-05 (oldest being from 2013-0-25).

My phone is Samsung Galaxy Grand 2

Here is my backup log: https://gist.github.com/mwisnicki/6c5ad27ad20cefba8118
My phone has Android 4.4.2.

Sorry it didn't get all your texts.
Please try out the beta and open a new issue if it doesn't work https://github.com/jberkel/sms-backup-plus#beta


net/haproxy: add syslog-ng socket

Hi
for discussion on https://github.com/opnsense/plugins/issues/2587#issuecomment-954598043
drop 'local'
add log socket
if i'm not mistaken this can be applied as a patch without waiting for the https://github.com/opnsense/core/commit/a763313d138258b0044c3285de0e8ac55d308160
Thanks!

I've tested it on my test machine and HAProxy logging is still working as expected. However, it was already working before applying the patch, so I'm probably not the ideal test candidate. :)
I'd merge the PR, but it is marked as draft. Is there anything missing?

it was already working before applying the patch, so I'm probably not the ideal test candidate. :)

with clog disabled?

I'd merge the PR, but it is marked as draft. Is there anything missing?
its ready. I just don't know your plans. @AdSchellevis  has already merged https://github.com/opnsense/core/commit/eab536021e742c0f3c48727613b178f37d3c1cd5 and I'm not sure if an empty string is still needed in the socket template

OK, successfully tested again with clog disabled.

@kulikov-a Thanks!

Thanks!


Errors in agent's netns topology probe on k8s

Hello
I used the master version, and I'm running skydive on k8s v0.19.0.
Env:
host: CentOS7
container: ubuntu20.04

My config is---skydive.yaml---skydive agent ConfigMap
apiVersion: v1
kind: ConfigMap
metadata:
  labels:
    app: skydive-agent
  name: skydive-agent-config
data:
  SKYDIVE_AGENT_TOPOLOGY_PROBES: runc docker
  SKYDIVE_AGENT_LISTEN: <IP_ADDRESS>:8081
  SKYDIVE_AGENT_TOPOLOGY_NETNS_RUN_PATH: /host/run

When I add network namespace on host(Centos7)
# ip netns add net1

Here's the skydive agent log:
2021-03-06T06:56:44.413Z  DEBUG  netns/netns.go:133 (*ProbeHandler).Register host2: Register network namespace: /host/run/net1
2021-03-06T06:56:50.125Z  ERROR  netns/netns.go:307 (*ProbeHandler).start host2: Failed to register namespace: /host/run/net1. All attempts fail:
#1: /host/run/net1 does not seem to be a valid namespace
#2: /host/run/net1 does not seem to be a valid namespace
#3: /host/run/net1 does not seem to be a valid namespace
#4: /host/run/net1 does not seem to be a valid namespace
...

Note the /host/run/net1 does not seem to be a valid namespace errors which means /host/run/net1 's device number is same with /host/run 's device number.
Code is:
if parent := filepath.Dir(path); parent != "" {
	if err := syscall.Stat(parent, &parentStats); err == nil {
		if stats.Dev == parentStats.Dev {
			return fmt.Errorf("%s does not seem to be a valid namespace", path)
		}
	}
}

I use stat command to check this:
in host:
# stat --format=%d /var/run/netns
22
# stat --format=%d /var/run/netns/net1
3

but in agent pod(container):
# stat --format=%d /host/run
22
# stat --format=%d /host/run/net1
22

Note net1's device number is different in host and pod.
It's tricky to debug. Has anyone encountered such a problem before?
Thanks

Hello. We did encounter such bugs some time ago but it was supposed to be fixed :-)
The reason for the check is the "ip netns" just creates a regular file for the new namespace then quick creates a bind mount from the namespace file in /proc to the regular file.
I'll try to reproduce the problem - pretty tricky to debug indeed - and I'll keep you updated

Did you use the Kubernetes template in contrib/kubernetes ? It specifies to use hostPID: true

Sorry for taking so long to answer.
Yes, I used the Kubernetes template in contrib/kubernetes.
hostPID: true
hostNetwork: true

I did try to config more pod security policy.
This is my config:
hostPID: true
hostNetwork: true
hostIPC: true

securityContext:
  privileged: true
  runAsUser: 0
  allowPrivilegeEscalation: true

It didn't work.
I also try on centos(host) with docker container, get the same issue.
env:
host: centos7
container: centos7

When I run docker container:
docker run -it --privileged -v /var/run/netns:/host/run docker.io/centos /bin/bash

When I add network namespace on host(Centos7)
# ip netns add net1

I use stat command to check this:
in host:
# stat --format=%d /var/run/netns
22
# stat --format=%d /var/run/netns/net1
3

but in container:
# stat --format=%d /host/run
22
# stat --format=%d /host/run/net1
22

Note net1's device number is different in host and container.

@waterjiao Hello. Sorry for the long delay.
On my CentOS 7 VM, I have the same results in the container that in the host. What storage driver are you using ? Is it overlayfs ?


ADD NEW TAG OPTIONS

ALL >> NO CHANGE
CASH >> CHANGE TO FSP
DATA >> CEA
PEOPLE >> NO CHANGE
NEW >> REGISTRATION
NEW >> TBD

I've chosen to include "coordination" as well.
Because that way it'll be a sort of "worst case"-scenario for the length of 5 tags in the layout.


[Enhancement]: Add a default Effect Handler For Promises

Something basic like:
(rf/reg-fx
  :promise
  (fn [{:keys [promise on-success on-failure]}]
    (-> promise
        (.then #(rf/dispatch (conj on-success %)))
        (.catch #(rf/dispatch (conj on-failure %))))))

Example Usage:
(rf/reg-event-fx
  ::fetch-data
  (fn [_ [_ params]]
    {:promise {:promise (js/fetch "https://api.example.com/data")
              :on-success [::fetch-success]
              :on-failure [::fetch-error]}}))

;; Success handler
(rf/reg-event-db
  ::fetch-success
  (fn [db [_ result]]
    (assoc db :data result)))

;; Error handler
(rf/reg-event-db
  ::fetch-error
  (fn [db [_ error]]
    (assoc db :error error)))

Maybe also add a :on-finally or :always handler?

First impression: to me this looks a bit awkward compared to other re-frame syntax (overloaded :promise keyword - for which I don't have a better suggestion either - and why not keep closer to the underlying mechanism by having :then and :catch instead of :on-success and :on-failure?)
And isn't a call to js/fetch a side effect already?
Could you point to a discussion of the problem that this solves?

I wonder if passing a function that returns a JS promise would mitigate things:
(rf/reg-event-fx
  ::fetch-data
  (fn [_ [_ params]]
    {:promise {:fn #(js/fetch "https://api.example.com/data")
               :then [::fetch-success]
               :catch [::fetch-error]}}))

Seems like nice sugar.
We do a lot of re-frame testing using jvm i.e. cljc
I presume this would not have any adverse affects on the portability?

What if we need to launch/coordinate with multiple promises?

Something slightly different I would love Re-frame to support, is supporting promises in the effects and listening to them in this way:
(rf/reg-fx :fetch
  (fn [{:keys [url]}]
    (js/fetch url)))

(rf/reg-event-fx ::fetch-data
  (fn [_ [_ params]]
    {:fx [[:promise {:fx [:fetch {:url "https://api.example.com/data"}]
                                  :then ,,,
                                  :else ,,,}]]}))

I've been using https://github.com/smogg/re-promise as a promises effect handler and it works just fine

I'd add two more features:

Support to delay values (will only start the fetch inside the reg-fx call, as re-promise do.
Support literal values

(rf/reg-fx
  :promise
  (fn [{:keys [promise on-success on-failure]}]
    (-> promise
      force
      (js/Promise.resolve)
      (.then ...)
      ...)))

;; all supported:
:promise (js/fetch "https://api.example.com/data")
:promise (delay (js/fetch "https://api.example.com/data"))
:promise {:literal :value}
:promise (delay {:literal :value})


Issue #2: Avoid xdebug logs on console

fixes #2

I'm going to merge the PR because the functionality seems correct and it is very interesting, so as not to block it, I add the ddev-generated comment once merged. Thanks @Eduardo-Morales-Alberti !!


Support magic methods for Class types.  Refs #240, #254.

Motivation and Context

For Class types, interpreted or compiled, support magic methods, except for __getattribute__, __complex__, __enter__, __exit__.

Approach

Fix inplace default fallback for Alternative and Class types.
Support reverse operator magic methods (__radd__, etc.) for Alternative and Class types.
Not supported: __getattribute__, __complex__, __enter__, __exit__.
Avoid Alternative (and Class) types inadvertently converting to float or int.

Test case is test_compile_alternative_float_conv (and test_compile_class_float_conv).
Want numerics (including numpy) to convert, but Alternative (and Class) to require a cast.

Fix interpreted default Alternative len().
Fix interpreted __setitem__ for Alternative types.
For ConstDict, check types for + and - operators (interpreted).
Fix TupleOfListOfInstance operator not implemented behavior.
Add bool conversions for PointerTo, but not testable yet.
Compile Dict.get with 2 parameters.  Refs #254.

How Has This Been Tested?

Tests were written first.

Screenshots or console output (if appropriate)

Types of changes

[x] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist:

[ ] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.

ok, cool, then lets delete them outright.
On Tue, Oct 22, 2019 at 10:12 AM rubidge<EMAIL_ADDRESS>wrote:

@rubidge commented on this pull request.
In typed_python/PyInstance.cpp
https://github.com/APrioriInvestments/typed_python/pull/255#discussion_r337541056
:

     PySequenceMethods* res =

         new PySequenceMethods {0,0,0,0,0,0,0,0};
         res->sq_contains = (objobjproc)PyInstance::sq_contains;
         res->sq_length = (lenfunc)PyInstance::mp_and_sq_length;

       res->sq_item = (ssizeargfunc)PyInstance::sq_item;

       res->sq_ass_item = (ssizeobjargproc)PyInstance::sq_ass_item;

       //res->sq_item = (ssizeargfunc)PyInstance::sq_item;

[ ] could be the SequenceMethod sq_item/sq_ass_item or it could be the
MappingMethod mp_subscript/mp_ass_subscript. The SequenceMethod methods
require an integer index, while the MappingMethod methods are less
restrictive. Since I don't know if the Alternative or Class is emulating a
Sequence or a Map, I went with the less restrictive signature.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/APrioriInvestments/typed_python/pull/255?email_source=notifications&email_token=AB6OHBC5AMGDBIYZ5MWN3ULQP4C3BA5CNFSM4JDE36FKYY3PNVWWK3TUL52HS4DFWFIHK3DMKJSXC5LFON2FEZLWNFSXPKTDN5WW2ZLOORPWSZGOCIYZDCQ#discussion_r337541056,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AB6OHBGIY22LM47OAHQ2GFDQP4C3BANCNFSM4JDE36FA
.

Changes have been made.  Superseded by PR #262.


gyp ERR! UNCAUGHT EXCEPTION [...] gyp ERR! This is a bug in node-gyp.

This happens when I run the "yarn" command from polkadash folder.
I am on:
Win 10
Node 16.2.0
Yarn 1.22.5
C:\laragon\www\polkadash (master)
λ yarn
yarn install v1.22.5
[1/4] Resolving packages...
[2/4] Fetching packages...
info<EMAIL_ADDRESS>The platform "win32" is incompatible with this module.
info<EMAIL_ADDRESS>is an optional dependency and failed compatibility check. Excluding it from installation.
info<EMAIL_ADDRESS>The platform "win32" is incompatible with this module.
info<EMAIL_ADDRESS>is an optional dependency and failed compatibility check. Excluding it from installation.
[3/4] Linking dependencies...
warning " ><EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>|| ^6.0.0".
warning " ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>|| ^4.0.0".
[4/4] Building fresh packages...
[-/6] ⢀ waiting...
[-/6] ⢀ waiting...
[6/6] ⢀ node-sass
[4/6] ⢀ yorkie
error C:\laragon\www\polkadash\node_modules\node-sass: Command failed.
Exit code: 1
Command: node scripts/build.js
Arguments:
Directory: C:\laragon\www\polkadash\node_modules\node-sass
Output:
Building: C:\Program Files\nodejs\node.exe C:\laragon\www\polkadash\node_modules\node-gyp\bin\node-gyp.js rebuild --verbose --libsass_ext= --libsass_cflags= --libsass_ldflags= --libsass_library=
gyp info it worked if it ends with ok
gyp verb cli [
gyp verb cli   'C:\Program Files\nodejs\node.exe',
gyp verb cli   'C:\laragon\www\polkadash\node_modules\node-gyp\bin\node-gyp.js',
gyp verb cli   'rebuild',
gyp verb cli   '--verbose',
gyp verb cli   '--libsass_ext=',
gyp verb cli   '--libsass_cflags=',
gyp verb cli   '--libsass_ldflags=',
gyp verb cli   '--libsass_library='
gyp verb cli ]
gyp info using<EMAIL_ADDRESS>gyp info using<EMAIL_ADDRESS>| win32 | x64
gyp verb command rebuild []
gyp verb command clean []
gyp verb clean removing "build" directory
gyp verb command configure []
gyp verb check python checking for Python executable "C:\Program Files (x86)\Python36-32\Scripts" in the PATH
gyp verb which failed Error: not found: C:\Program Files (x86)\Python36-32\Scripts
gyp verb which failed     at getNotFoundError (C:\laragon\www\polkadash\node_modules\which\which.js:13:12)
gyp verb which failed     at F (C:\laragon\www\polkadash\node_modules\which\which.js:68:19)
gyp verb which failed     at E (C:\laragon\www\polkadash\node_modules\which\which.js:80:29)
gyp verb which failed     at C:\laragon\www\polkadash\node_modules\which\which.js:89:16
gyp verb which failed     at C:\laragon\www\polkadash\node_modules\isexe\index.js:42:5
gyp verb which failed     at C:\laragon\www\polkadash\node_modules\isexe\windows.js:36:5
gyp verb which failed     at FSReqCallback.oncomplete (node:fs:194:21)
gyp verb which failed  C:\Program Files (x86)\Python36-32\Scripts Error: not found: C:\Program Files (x86)\Python36-32\Scripts
gyp verb which failed     at getNotFoundError (C:\laragon\www\polkadash\node_modules\which\which.js:13:12)
gyp verb which failed     at F (C:\laragon\www\polkadash\node_modules\which\which.js:68:19)
gyp verb which failed     at E (C:\laragon\www\polkadash\node_modules\which\which.js:80:29)
gyp verb which failed     at C:\laragon\www\polkadash\node_modules\which\which.js:89:16
gyp verb which failed     at C:\laragon\www\polkadash\node_modules\isexe\index.js:42:5
gyp verb which failed     at C:\laragon\www\polkadash\node_modules\isexe\windows.js:36:5
gyp verb which failed     at FSReqCallback.oncomplete (node:fs:194:21) {
gyp verb which failed   code: 'ENOENT'
gyp verb which failed }
gyp verb could not find "C:\Program Files (x86)\Python36-32\Scripts". checking python launcher
gyp verb check python launcher python executable found: "C:\Python27\python.exe"
gyp verb check python version C:\Python27\python.exe -c "import sys; print "2.7.16 gyp verb check python version .%s.%s" % sys.version_info[:3];" returned: %j
gyp verb get node dir no --target version specified, falling back to host node version: 16.1.0
gyp verb command install [ '16.1.0' ]
gyp verb install input version string "16.1.0"
gyp verb install installing version: 16.1.0
gyp verb install --ensure was passed, so won't reinstall if already installed
gyp verb install version is already installed, need to check "installVersion"
gyp verb got "installVersion" 9
gyp verb needs "installVersion" 9
gyp verb install version is good
gyp verb get node dir target node version installed: 16.1.0
gyp verb build dir attempting to create "build" dir: C:\laragon\www\polkadash\node_modules\node-sass\build
gyp verb build dir "build" dir needed to be created? C:\laragon\www\polkadash\node_modules\node-sass\build
gyp verb find vs2017 Found installation at: C:\Program Files (x86)\Microsoft Visual Studio\2019\Community
gyp verb find vs2017   - Missing Visual Studio C++ core features (Microsoft.VisualStudio.VC.MSBuild.Base)
gyp verb find vs2017   - Missing VC++ 2017 v141 toolset (x86,x64) (Microsoft.VisualStudio.Component.VC.Tools.x86.x64)
gyp verb find vs2017   - Missing a Windows SDK (Microsoft.VisualStudio.Component.Windows10SDK.* or Microsoft.VisualStudio.Component.Windows81SDK)
gyp verb find vs2017   - Some required components are missing, not using this installation
gyp verb find vs2017 Found installation at: C:\Program Files (x86)\Microsoft Visual Studio\2019\BuildTools
gyp verb find vs2017   - Found Microsoft.VisualStudio.VC.MSBuild.Base
gyp verb find vs2017   - Found Microsoft.VisualStudio.Component.VC.Tools.x86.x64
gyp verb find vs2017   - Found Microsoft.VisualStudio.Component.Windows10SDK.18362
gyp verb find vs2017   - Using this installation with Windows 10 SDK
gyp verb find vs2017 using installation: C:\Program Files (x86)\Microsoft Visual Studio\2019\BuildTools
gyp verb build/config.gypi creating config file
gyp verb build/config.gypi writing out config file: C:\laragon\www\polkadash\node_modules\node-sass\build\config.gypi
(node:6292) [DEP0150] DeprecationWarning: Setting process.config is deprecated. In the future the property will be read-only.
 UNCAUGHT EXCEPTION
gyp ERR! stack Error: spawn C:\Program Files (x86)\Microsoft Visual Studio\2019\BuildTools\MSBuild\15.0\Bin\MSBuild.exe ENOENT
gyp ERR! stack     at Process.ChildProcess._handle.onexit (node:internal/child_process:282:19)
gyp ERR! stack     at onErrorNT (node:internal/child_process:480:16)
gyp ERR! stack     at processTicksAndRejections (node:internal/process/task_queues:83:21)
gyp ERR! System Windows_NT 10.0.19042
gyp ERR! command "C:\Program Files\nodejs\node.exe" "C:\laragon\www\polkadash\node_modules\node-gyp\bin\node-gyp.js" "rebuild" "--verbose" "--libsass_ext=" "--libsass_cflags=" "--libsass_ldflags=" "--libsass_library="
gyp ERR! cwd C:\laragon\www\polkadash\node_modules\node-sass
gyp ERR! node -v v16.1.0
gyp ERR! node-gyp -v v3.8.0
gyp ERR! This is a bug in node-gyp.
polkadash error yarn.txt

Hi, this is quite out of date - needs a yarn upgrade across the board, but node-gyp is problematic on Windows machine, always has been, nothing much we can do to help here other than recommend using WSL2 if you're on Windows.

Thanks. I will try WSL2.

Workarounds for node-gyp on Windows that worked for me:

Install build tools globally:

npm install --global windows-build-tools
or
yarn global add windows-build-tools

Set python path manually:

npm config set python c:\python27amd64\python.exe

Set msbuild path manually:

npm config set msbuild_path = "C:\Program Files(x86)\Microsoft Visual Studio\2019\BuildTools" msvs_version = "2019"


[c#] Builtin types not being highlighted in editor

VSCode Version: 0.10.11
OS Version: Windows 10.0.10586

Steps to Reproduce:

Open VSCode
Copy and paste this snippet in:

using System;
using System.Collections.Generic;
using System.Linq;

namespace FooBar
{
    public static class Quux
    {
        public static char GetBlah()
        {
            var thing = default(string);
        }
    }
}

The keywords var, char, and string will not be highlighted.
Here's an image from my local machine:

There's a fix for this in the coming March release.
The Dark/Light (Visual Studio) now show these keywords blue, Dark+/Light+ turquoise (color used for type references).
(It's questionable if 'var' should be considered a type reference, but that's the decision of the C# grammar. To file an issue against the grammar


Closed by #9


docs: indicate minimum drift version for manager functionality

I believe something like this could be helpful.
Also:

drift 2.17 introduced a new set of APIs designed to make common queries much easier to write

It could be good to link/clarify the docs regarding that, though I suspect it is basically referencing the remainder of the docs site? Still, it potentially leaves a new consumer unsure if they are referencing the correct info.

Thanks! I have fixed the mistaken version number in aa5314df67d0f8261f82700a0fe235d5e87119a9 - I hope that clarifies things enough. I'm not sure if we need to put the minimum version on the top of the page that prominently, I think it's somewhat expected that the docs always reference the latest version by default.


feat: expand LND support

Fixes #352
Adds

[x] GetNodeConnectionInfo
[x] ListChannels
[x] OpenChannel
[x] CloseChannel
[x] ListPeers
[x] ConnectPeer
[x] GetOnchainBalance
[x] GetNewOnchainAddress

On the channels page the savings balance shows 0. Can you implement the GetBalances() function in lnd.go?

Open Channel does not work using Polar because there are no channel suggestions. I wonder if we should move the custom option to the frontend CC @bumi
It also then does not need to be duplicated for mainnet and signet

Added GetBalances call 👍

oh yay, merged!


Replace swagger host with request host and adjust scheme

As a follow up for #2217 this change will properly replace the host (currently always host: "<IP_ADDRESS>:8080",) in the generated swagger file with the host of the request that tries to access the swagger file. We strip off the http:// or https:// prefix because that's handled in the swagger schemes section.
We also set the scheme to https if the current request was made using https://.

Ike Plugins (test-keeper)
Thank you @kwk for this contribution!

It appears that no tests have been added or updated in this PR.
Automated tests give us confidence in shipping reliable software. Please add some as part of this change.
If you are an admin or the reviewer of this PR and you are sure that no test is needed then you can use the command /ok-without-tests as a comment to make the status green.
For more information please head over to official documentation. You can find there how to configure the plugin.

Codecov Report

Merging #2220 into master will increase coverage by <.01%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #2220      +/-   ##
==========================================
+ Coverage   69.83%   69.84%   +<.01%
==========================================
  Files         170      170
  Lines       15844    15844
==========================================
+ Hits        11065    11066       +1
+ Misses       3768     3766       -2
- Partials     1011     1012       +1

Impacted Files
Coverage Δ

controller/workitem.go
79.64% <0%> (+0.19%)
:arrow_up:

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 2f7c863...3bec9c0. Read the comment docs.

/ok-without-tests

/ok-without-tests


WIP: Django 3

Remove Python 2 support
Ensure usage with Django 3

See: https://github.com/isl-x/django-rq-scheduler/issues/38

@g3rd Is there anyway I can help here, I'd love to see this released.

@g3rd this seems relatively easy PR, any way this can be released or contributors can be instructed how to do it? I think a lot of projects depend on it and cannot migrate to Django 3.0 because of that library.
Any response is appreciated.

@g3rd I think this is ready to go now and also addresses PR #41


lsp crashing

I'm not sure how to interpret this.
Process beancount-ls stderr finished
thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: Char range out of bounds: char range 2215700..2215700, Rope/RopeSlice char length 2215699', /Users/dustin/.asdf/installs/rust/1.62.1/registry/src/github.com-1ecc6299db9ec823/ropey-1.5.0/src/rope.rs:546:37

Probably something got out of sync with the text file updates
Does it constantly error for you? If it does, can you describe steps to reproduce?

start up emacs (i use doom)
open my journal.beancount file
start typing a new transaction

this is what i type
2022-01-02 * "something"
  ex

As soon as I type "ex" on the second line, the lsp crashes.
emacs log
Found the following clients for /Users/dustin/Documents/accounting/journal.beancount: (server-id beancount-ls, priority 0)
The following clients were selected based on priority: (server-id beancount-ls, priority 0)
Beancount Server initializing

lsp stderr
thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: Char range out of bounds: char range 2215714..2215714, Rope/RopeSlice char length 2215712', /Users/dustin/.asdf/installs/rust/1.62.1/registry/src/github.com-1ecc6299db9ec823/ropey-1.5.0/src/rope.rs:546:37
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

i should also mention this is the first time i've tried using the rust language server in emacs.  was using vscode until now which works fine for me.

also, my journal.beancount is over 40k lines in case that matters

I hade a similar issue in NeoVim 0.8 when opening my "journal.beancount" I get:
[ERROR][2022-09-24 09:55:21] .../vim/lsp/rpc.lua:734	"rpc"	"beancount-language-server"	"stderr"	"thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: Error(\"missing field `journal_file`\", line: 0, column: 0)', /home/alexanderp/.cargo/registry/src/github.com-1ecc6299db9ec823/beancount-language-server-1.2.5/src/server.rs:71:42\nnote: run with `RUST_BACKTRACE=1` environment variable to display a backtrace\n"

Thanks for the report, need to find time to get to the bottom of this report

Can confirm I'm also getting this issue, tried different variations of the journal file option but nothing seems to work, more logs here: https://gist.github.com/Philogy/6253e5a81ae8eb0cef9c9bf6f68a954c. I also get the missing field 'journal_file' error

Same/similar error when using with Neovim
"thread 'main' panicked at 'called Result::unwrap()on anErrvalue: ()', /home/ian/.cargo/registry/src/index.crates.io-6f17d22bba15001f/beancount-language-server-1.3.1/src/server.rs:122:91\nnote: run withRUST_BACKTRACE=1 environment variable to display a backtrace\n"
Beancount LSP will load without the init_options = { journal_file = "<insert beancount main.beancount entry file>"} and highlight beancount errors because I have my accounts in a separate beancount file and included in the main.beancount. Add in the init_options, and it panics.
I hope the above info helps, and thanks for the LSP.

pushed a new release with some extra debugging (v1.3.3), report back errors
It is erroring when I try to create a path buffer of the journal file passed in through LSP init options.
Could you make sure the path is correct and exists?

The new release has resolved the error for me.
Thanks, Polarmutex.

Sorry, I have been running that release for a bit. Thought I had those changes in main. Let me know any features you might find helpful. Probably going to try improve completion when I get time.

Awesome.
For me, code folding around levels of comments (ie. *, **, ***) would be helpful.
I have it on my list to explore if Treesitter can do it through your Treesitter plugin

think all is resolved, please reopen if there is still an issue


How to write sql "group by"/"order by" multi columns?

How to write sql "group by"/"order by" multi columns?

As hack, I merge columns for select and group by : select field1||'-'||field2 from tab group by field1||'-'||field2
but "order by" doesn t work
I do a split to unmerge columns when i get results


A mechanism to associate a tactic with an implicit parameter via an attribute

This is still quite an experimental feature, extending the syntax of implicit arguments like so:
let bind (a:Type) (b:Type)
  (#[@resolve_framing] pre_f:pre_t)
  (#[@resolve_framing] post_f:post_t a)
  (#[@resolve_framing] post_g:post_t b)
  (f:repr a pre_f post_f)
  (g:(x:a -> repr b (post_f x) post_g))
: repr b pre_f post_g

which dispatches the resolution of those implicit arguments to a tactic in scope with an attribute like so:
[@(resolve_implicits)
  (resolve_framing)]
let resolve () : Tac unit =

This is definitely still very experimental and not recommended for general use. However, it relies on changes from the syntax on up and touches many parts of the typechecker. As such, I would like to get it to master to ease the maintenance burden and to enable using it in many other branches that fork from master as we work on Steel.
I don't think this should disturb any existing functionality, but it would be good to have another set of eyes, if possible.

Thanks @nikswamy! This would be very useful for me to do some testing on the _aseem_steel_framing branch where I am experimenting with the 2 effects story.
I will review this in detail soon, but have some high-level comments for now:

Should the syntax of these binder attributes match with the new @@ syntax?
I think the code could use some comments (e.g. new fields in Syntax, Rel, Env, code in Rel that does the dispatching after bucketizing, etc.). I can make sense of what they are doing but some comments would also be nice.
Should we remove the files ulib/experimental/SteelT.* from the PR?
Can we also cleanup the previously added resolve_all_implicits_hook in this PR itself? The Rel support for this never made it to the master branch, but there are remnants of it in Env, Tactics, Pervasives etc. that we should get rid of.

I agree with Aseem's high-level comments.
Regarding Steel files in particular, I think all the FramingBind, Repro and so on should not be included in master. They are remnants of experiments that didn't work, and should hopefully be replaced by the new 2-effect system.
I'm also not completely sure whether DeferredImplicits.fs(i) should be included, as it is extremely Steel-specific WIP for now. Maybe we could keep the machinery and interface as it is, but replace the implementation by a no-op for now? On the fence about this one.
Thanks!

Thanks for taking a look promptly! Much appreciated.
Some responses:

Regarding the syntax: we currently support only adding a single attribute to a binder. That makes it different than [@@ e1;e2] etc. Maybe we should allow multiple attributes here as well. i.e., one would write

(#[@@ resolve_implicits foobar; some; other; attrributes] x) ...
which would dispatch solving this implicit to a tactic with the attribute resolve_implicits foobar. And the rest of the attributes would be uninterpreted for now, but we may have uses for them in the future.

Comments, cleanup, removing the old hook etc: Yep, will do.

Removing DeferredImplicits: Fine with that too. Maintaining and restoring that separately on a branch isn't much work since there's no potentially conflicting churn there. But, that essentially would also mean that the SteelT files go ... since without this sorting, those files will no longer typecheck.

But without those SteelT files, we don't really have existing test cases for this new feature. Makes me wonder if this is worth getting to master at all, until we have something that really uses it successfully.
@aseemr, what do you think about continuing your work by merging this into your branch, rather than using master as a synchronization point?

@aseemr , I'm not sure what this remark refers to:

Can we also cleanup the previously added resolve_all_implicits_hook in this PR itself? The Rel support for this never made it to the master branch, but there are remnants of it in Env, Tactics, Pervasives etc. that we should get rid of.

Can you please clarify? thanks

Hi Nik, I was referring to the env.try_solve_implicits_hook which is disconnected in the current master branch (without Rel support). But I guess you are reusing it in this PR, so may be it's fine?

FYI, I made the syntax
``(#[@@ resolve_implicits foobar])```
i.e., a single attribute with @@. The parser expects a tmNoEq so [@@ f; g] will not currently parse. That should make it future proof in case we want to add support for multiple attributes on a binder.

I removed the sorting code, moved a lot of the logic of deferred implicits to tactics into DeferredImplicits.fs, so that the changes to Rel remain relatively small.
I moved SteelT.Effect and SteelT.Repro to tests/micro-benchmarks and have a tactic there that just checks that it gets the expected number of goals to solve (rather than checking any expected output).
Also added some comments etc.

I also raise a warning on any use of an #[@@] binders, saying that this is experimental and may change.


Add asset map to the bundle as a JS module, so that it can be accessed programmatically without extra network requests

Hi! Thanks for the infrastructural addon!
Problem
I need to access files over network. With the current implementation of broccoli-asset-map, I have the following options:

Disable fingerprinting on specific files. Causes files to be cached, cache does not get busted.
Generate a random hash on build, use the same hash on all files, use the know hash to access the files. Idea by @NullVoxPopuli. Causes cache to be busted on all files, including unchanged ones.
Use an extra request to load assetMap.json over the network and find out fingerprinted URLs to files.

As you can see, all options are suboptimal.
I ended up using the first one, adding a random query param to bust the cache. This make this option tolerable.
Suggested solution
Making the asset map accessible as part of the JS bundle resolves the issue: we will be able to fetch fingerprinted assets without extra network requests, with cache busted when needed and only when needed.
Could be import { assetMap } from 'broccoli-asset-rev' or something.
Of course, this feature should be opt-in to avoid increasing bundle size for those who don't need it.
CC @simonihmig.

I've found this addon: https://github.com/adopted-ember-addons/ember-cli-ifa
It does what I'm asking for, but at the cost of increasing bundle size substantially. It has a service, an initializer, a helper, an util...
I just want to do this, without all the extra weight:
import { assetMap } from 'broccoli-asset-rev';

// e. g. in route model hook:
const url = '/' + assetMap.assets['api/posts/all.json'];
return fetch(url);


removed empty space on cookies policy page

closes #643

Ah oops yes good point @idjevm
i wonder if something went wrong with that file if its showing up for everyone

can you remove package-lock?

I think it is because people are running npm install instead of docker-compose run client npm installl<-  Just a thought though, but from my side, running the client with docker doesn't affect the package-lock.josn file.

Yeah possibly, unless someone forgot to add the lockfile after updating and somehow it causes this for more people that the lock file is also updating or something like that

Closing this PR as it will be resolved with PR #665

@idjevm @nadinejuraschek should we move this to Done on the project?

Yes please! This was resolved with another issue and PR for that other issue!