Generate Javadocs archives in Travis

TODOs

[ ] Tests
[ ] Documentation

@henrikplate, it seems that the jobs are consistently failing. I didn't look up the logs but it seems something related to gpg

This PR will be dismissed, the changes in branch release-to-central represent the latest status (and include the Javadoc creation in .travis.yml.


Breakdowns by host and process

Some of the behavior in #45 (now fixed) is mysterious because multiple processes are rolled together into a job.  Sometimes it is desirable to break a multi-process job down by process, in the same way that a multi-host job can be broken down by host: only this way can we more easily see where to focus next (by excluding process names, or focusing on specific process IDs or process names, or similar).

Consider a switch --breakdown= which (for jobs, anyway) has possible keyword arguments host, command.  In the absence of this switch, jobs are rolled up across commands and hosts, as now, and output like this would be typical:
$ sonalyze jobs --job=281495 -f8d -b -- ../tmp/fox-logs/*.out
jobm     user        duration  host                                 cpu-avg  cpu-peak  mem-avg  mem-peak  gpu-avg  gpu-peak  gpumem-avg  gpumem-peak  cmd
281495<  ec-larstha  0d 0h 2m  c1-[5,8-10,12-14,20-21,23-24,26-28]  1216      1400       1        1         0        0         0           0            srun,slurm_script,sonarloop.sh,tsp_mpi,sonar

This is a job that ran five commands on 14 hosts.  But suppose we breakdown by command (this is simulated):
$ sonalyze jobs --job=281495 -f8d -b --breakdown=cmd --fmt=header,job,host,cpu,cmd -- ../tmp/fox-logs/*.out
job       host                                 cpu-avg  cpu-peak   cmd
281495    c1-[5,8-10,12-14,20-21,23-24,26-28]  1216     1400       srun,slurm_script,sonarloop.sh,tsp_mpi,sonar
* 281495  c1-[5,8-10,12-14,20-21,23-24,26-28]  1213     1395       tsp_mpi
* 281495  c1-[5,8-10,12-14,20-21,23-24,26-28]     1        1       srun
* 281495  c1-[5,8-10,12-14,20-21,23-24,26-28]     1        1       slurm_script
* 281495  c1-[5,8-10,12-14,20-21,23-24,26-28]     1        1       sonarloop.sh
* 281495  c1-[5,8-10,12-14,20-21,23-24,26-28]     1        1       sonar

or by host:
$ sonalyze jobs --job=281495 -f8d -b --breakdown=host --fmt=header,job,host,cpu,cmd -- ../tmp/fox-logs/*.out
job       host                                 cpu-avg  cpu-peak   cmd
281495    c1-[5,8-10,12-14,20-21,23-24,26-28]  1216     1400       srun,slurm_script,sonarloop.sh,tsp_mpi,sonar
* 281495  c1-5                                 100      100        srun,slurm_script,sonarloop.sh,tsp_mpi,sonar
* 281495  c1-8                                 99       100        srun,slurm_script,sonarloop.sh,tsp_mpi,sonar
* 281495  c1-9                                 99       100        srun,slurm_script,sonarloop.sh,tsp_mpi,sonar
* ...

or host first and command second (the other one is also an option):
$ sonalyze jobs --job=281495 -f8d -b --breakdown=host,cmd --fmt=header,job,host,cpu,cmd -- ../tmp/fox-logs/*.out
job       host                                 cpu-avg  cpu-peak   cmd
281495    c1-[5,8-10,12-14,20-21,23-24,26-28]  1216     1400       srun,slurm_script,sonarloop.sh,tsp_mpi,sonar
* 281495  c1-5                                 100      100        srun,slurm_script,sonarloop.sh,tsp_mpi,sonar
** 281495 c1-5                                 99       100        tsp_mpi
** 281495 c1-5                                 1        1          srun
** ...
* 281495  c1-8                                 99       100        srun,slurm_script,sonarloop.sh,tsp_mpi,sonar
** ...
* 281495  c1-9                                 99       100        srun,slurm_script,sonarloop.sh,tsp_mpi,sonar
** ...
* ...

(TODO: On the one hand there is --command, on the other hand the format specifier cmd, leading to confusion above.  We should pick one and stick with it.)

This is working on my branch w-breakdown, there just needs to be some better sorting.    Actually, any predictable sort is better than none.  And then hosts should be sorted by the normal host sorting order underneath that (currently lexicographic).


feat: add region to collection

Closes #263

Thinking more: Georgia is geographically both Europe and Asia. Geopolitically, we typically group Georgia into Eastern Europe and Central Asia. Kyrgyzstan is geographically Asia, but we typically put it in the same region as Georgia.
So maybe add Eastern Europe and Central Asia EECA.

Cyprus is geographically Asia, but is culturally/geopolitically Europe (so we can put it as Europe).


Forward GEMM to GEMV when one argument is actually a vector

I expanded this from #4708, and the tests passed locally but likely needs more checking to ensure it's stable.
Fixes #4580

Thank you - somehow I had failed to realize I still had the bogus incx from the cursed first draft in my fork. (I still get a handful of new LAPACK testsuite failures on x86_64 with this - could be this is the rounding in the gemv microkernel for Haswell again)

That is unfortunate. I've made it opt-in per target so the x86_64 precision errors can be looked at separately. I've also disabled forwarding if ONLY_CBLAS=1, requiring a different code path or some symbol hiding the gemv parts.
Does that make this merge-able @martin-frbg ? 😸

Didn't mean this would make it unmergeable, haven't even gotten around to testing with TARGET=GENERIC yet (the inaccuracy had already been flagged in #4324, but it is not clear if it is really significant in the general case)

@martin-frbg , @Mousius ,
Actually I was checking the gemm and changed gemm(forward to gemv) results with pytorch linear layer in aarch64,
For shape  :[512, 2048], [2048]: In this 9 output values are suffering from accuracy mismatch and their ratio is as follows:
0.9999868
0.99999
0.9999861
0.9998682
1.0000162
1.0002389
0.9999898
0.9998842
0.99992955

We're also seeing regression in some of our PyTorch models:
RuntimeError: probability tensor contains either `inf`, `nan` or element < 0

Interesting the OpenBLAS tests seem fine 🤔

that's fallout from SCAL changes of #4729 - see #4794 and #4807 for the fix (I'm going crazy over making the same fairly trivial change in the Sparc scal kernel, otherwise these should be ready to merge)

@martin-frbg Out of curiosity, why still bother with Sparc?  It's a dead architecture, almost in the domain of retro-computing.  The last proper Sparc CPU release was circa 2017.  Neither Oracle or Fujitsu are making any new Sparc processors (they've moved on to x86-64 and ARM).  Folks still using legacy Sparc hardware can always use older versions of OpenBLAS.

@conradsnicta as far as I know, there may still be distributions providing packages for Sparc hardware, and without the patch they would get a broken build due to utest failures. There are machines in the GCC compile farm I can test on, and the change seemed straightforward enough, but there is something about the ABI that has turned a simple "read another value from the stack into some register and see if it is non-zero" into an energy drain.

I think you will only see the inaccuracies in lapack-test (and when you run the reproducer from #4324), the trouble is that currently all ARM64 except A64FX use the same NEON kernels for GEMV, which may have been inspired by the equally affected x86_64 microkernels for Haswell and up (or vice versa) and I have failed to come up with an easy fix

I think you will only see the inaccuracies in lapack-test (and when you run the reproducer from #4324), the trouble is that currently all ARM64 except A64FX use the same NEON kernels for GEMV, which may have been inspired by the equally affected x86_64 microkernels for Haswell and up (or vice versa) and I have failed to come up with an easy fix

LD_PRELOAD=./libopenblas_neoversev1p-r0.3.27.dev.so ./blas_test
           BLAS                         MAT
1.175201193643801378e+00	1.175201193643801822e+00
1.103638323514327002e+00	1.103638323514327224e+00
3.578143506473725477e-01	3.578143506473724922e-01
7.045563366848892062e-02	7.045563366848883735e-02
9.965128148869423913e-03	9.965128148869309421e-03
1.099586127207508035e-03	1.099586127207556390e-03
9.945433911359019552e-05	9.945433911360671605e-05
7.620541308928086011e-06	7.620541308896932986e-06
5.064719743597123625e-07	5.064719744437437483e-07
2.971814125340976886e-08	2.971814140421127963e-08
1.560886614404566330e-09	1.560886564391797127e-09
7.419931336016816203e-11	7.419902813631537848e-11
3.221423128252354218e-12	3.221406076314455686e-12
1.287858708565181587e-13	1.289813102624490508e-13
4.440892098500626162e-15	4.440892098500626162e-15
0.000000000000000000e+00	-4.440892098500626162e-16
ddot: -3.885780586188047891e-16
dgemv: 0.000000000000000000e+00
ddot == dgemv? NO
dgemv is 0.0? YES

It seems dot might need some work, but nobody has complained yet 🤔 gems looks fine in the given reproducer for the NEOVERSEV1 target, and the lapack tests are run in CI. So, does it look right for the ARM64 target?

The last line of the result array for the GEMV though, truncated to zero where less highly optimized implementations (including OpenBLAS' "generic" C target) show a -4e-16 ... I tried to explain it away with a good bit of handwaving in the original issue, but it at least appears to correlate with about 20 new failures each for S and D popping up in the LAPACK testsuite.

@martin-frbg I've increased the number of accumulators in GEMV T, and that seems to have fixed the issue without impacting performance too much. Unsure how else to validate this 🤔

Great, thanks. I'll try to steal that for x86_64 too, somehow I only managed to break things further when I tried. Also had not realized that the lapack testsuite failures on arm64 were all related to GEMV_T, did not have the impression that this was the case on x86_64.  Anyway we can probably make that opt-out now - I'll check all the other platforms (riscv appears to be fine already)

Question:  If an architecture packs the data a specific way (AKA we pack the data differently for P10 MMA vs the way the generic code does) and it does NOT have a architecture specific implementation of GEMV, won't this be a problem for this patch?  Right now we do NOT have a P10 version of GEMV for BF16.

Question: If an architecture packs the data a specific way (AKA we pack the data differently for P10 MMA vs the way the generic code does) and it does NOT have a architecture specific implementation of GEMV, won't this be a problem for this patch? Right now we do NOT have a P10 version of GEMV for BF16.

I believe you can match on ${CORE} in the Makefile to further filter GEMM_GEMV_FORWARD, is that right @martin-frbg ?

Forwarding happens at the interface stage so any special packing you (plan to) do for or in the kernel should be irrelevant, I hope. The only reason this is activated on a per-architecture basis is that there is an accuracy bug in some x86 GEMV kernels that I haven't been able to fix yet

Forwarding happens at the interface stage so any special packing you (plan to) do for or in the kernel should be irrelevant, I hope. The only reason this is activated on a per-architecture basis is that there is an accuracy bug in some x86 GEMV kernels that I haven't been able to fix yet

I think the issue is you may have an optimized dgem/sgem but not sbgemv, so the sbgemm kernel may be faster than the forward in some cases?

Yes matching on CORE should be possible (except it would lead to some ugly long lines of conditionals...). As said we are in interface/gemm.c here, right after the call to GEMM has been received by the library and before the level3 driver even gets to think about partitioning the problem for the GEMM kernel

Forwarding happens at the interface stage so any special packing you (plan to) do for or in the kernel should be irrelevant, I hope. The only reason this is activated on a per-architecture basis is that there is an accuracy bug in some x86 GEMV kernels that I haven't been able to fix yet

I think the issue is you may have an optimized dgem/sgem but not sbgemv, so the sbgemm kernel may be faster than the forward in some cases?

OK , I must admit having been too fixated on SGEMM/DGEMM, will disable the forwarding for SBGEMM in #4852 until
we have more data.


the conflict of camera driver and wi-fi (IDFGH-9246)

Answers checklist.

[X] I have read the documentation ESP-IDF Programming Guide and the issue is not addressed there.
[X] I have updated my IDF branch (master or release) to the latest version and checked that the issue is present there.
[X] I have searched the issue tracker for a similar issue and not found a similar issue.

General issue report
ask for guide to resolve the conflict
The IDF version:
v5.0,matser branch
the camera is ov2640
the chip is esp32s3
what i do:
i copy the example of esp-idf http-client:
`// ==== Memory allocator that takes advantage of PSRAM if present =======================
char* my_allocateMemory(char* aPtr, size_t aSize){
if (aPtr != NULL) free(aPtr);

char* ptr = NULL;

ptr = (char*)malloc(aSize);

memset(ptr, 0, aSize);

return ptr;

}
void task_post(){
char *post_data = "{\"field1\":\"value1\"}";
//post_data = pic_char;
ESP_LOGW(TAG_my_main,"post start");
esp_http_client_handle_t my_http_client_handle = my_http_stream_init();
ESP_LOGW(TAG_my_main,"get_client_handle");

esp_http_client_set_post_field(my_http_client_handle, post_data, strlen(post_data));
ESP_LOGW(TAG_my_main,"set_post_field");

esp_err_t err = esp_http_client_perform(my_http_client_handle);

if (err == ESP_OK) {
    ESP_LOGI(TAG, "HTTP POST Status = %d, content_length = %lld",
            esp_http_client_get_status_code(my_http_client_handle),
            esp_http_client_get_content_length(my_http_client_handle));
} else {
    ESP_LOGE(TAG, "HTTP POST request failed: %s", esp_err_to_name(err));
}

my_http_stream_clean(my_http_client_handle);

}`
and do same with camera driver
'void task_capture(){
camera_fb_t *pic = my_camera_capture();
//  If frame size is more that we have previously allocated - request  125% of the current frame space
if (pic->len > pic_size){
    pic_size = pic->len * 1.5;
    pic_char = my_allocateMemory(pic_char,pic_size);
}

ESP_LOGI(TAG_my_main, "Picture taken! Its was: %d", pic->len);

sprintf(pic_char ,"{\"field1\":\"");

int i=5;
while(i < pic->len){
    sprintf(pic_char + i*2 +1,"%02x",pic->buf[i]);
    i++;
}

sprintf(pic_char + i*2 ,"\"}");

my_camera_return(pic);
//vTaskDelay(5000);

}'
both them are run successfuly while separately. but have problem when they run together.
i try to local the where the problem, i find that the system reboot when the process of esp_http_client_init try to malloc the ram ,then log many warning.
i not sure which part have the dirt ram allocate. hope for guide to how to deal with.
the log message:
`assert failed: block_trim_free tlsf.c:496 (block_is_free(block) && "block must be free")
Backtrace: 0x40375c1a:0x3fcf3500 0x4037fc95:0x3fcf3520 0x40386c31:0x3fcf3540 0x40385188:0x3fcf3660 0x40384ace:0x3fcf3680 0x40376551:0x3fcf36a0 0x403765f8:0x3fcf36c0 0x40386c41:0x3fcf36e0 0x4201ebbf:0x3fcf3700 0x42009c9a:0x3fcf3730 0x42009d21:0x3fcf37e0 0x42009ea9:0x3fcf3810 0x4209e95b:0x3fcf3830 0x40382669:0x3fcf3860
0x40375c1a: panic_abort at /Users/jinyi/esp/esp-idf/components/esp_system/panic.c:452
0x4037fc95: esp_system_abort at /Users/jinyi/esp/esp-idf/components/esp_system/port/esp_system_chip.c:77
0x40386c31: __assert_func at /Users/jinyi/esp/esp-idf/components/newlib/assert.c:78
0x40385188: block_trim_free at /Users/jinyi/esp/esp-idf/components/heap/tlsf/tlsf.c:496
(inlined by) block_prepare_used at /Users/jinyi/esp/esp-idf/components/heap/tlsf/tlsf.c:579
(inlined by) tlsf_malloc at /Users/jinyi/esp/esp-idf/components/heap/tlsf/tlsf.c:1005
0x40384ace: multi_heap_malloc_impl at /Users/jinyi/esp/esp-idf/components/heap/multi_heap.c:207
0x40376551: heap_caps_malloc_base at /Users/jinyi/esp/esp-idf/components/heap/heap_caps.c:145
0x403765f8: heap_caps_malloc_default at /Users/jinyi/esp/esp-idf/components/heap/heap_caps.c:198
0x40386c41: malloc at /Users/jinyi/esp/esp-idf/components/newlib/heap.c:24
0x4201ebbf: esp_http_client_init at /Users/jinyi/esp/esp-idf/components/esp_http_client/esp_http_client.c:715 (discriminator 1)
0x42009c9a: my_http_stream_init at /Users/jinyi/Desktop/Graduate_Design/trash_cans/main/my_http_get.c:38
0x42009d21: task_post at /Users/jinyi/Desktop/Graduate_Design/trash_cans/main/main.c:31
0x42009ea9: app_main at /Users/jinyi/Desktop/Graduate_Design/trash_cans/main/main.c:108
0x4209e95b: main_task at /Users/jinyi/esp/esp-idf/components/freertos/app_startup.c:208 (discriminator 13)
0x40382669: vPortTaskWrapper at /Users/jinyi/esp/esp-idf/components/freertos/FreeRTOS-Kernel/portable/xtensa/port.c:162
ELF file SHA256: 49dff066672d6b6f`

I will close the issue as duplicate, since you have already reported it in https://github.com/espressif/esp32-camera/issues/501.


There is a small gap in the SynchronizedWeakHashSet implementation. T…

Summary
There is a small gap in the SynchronizedWeakHashSet implementation - the containsKey method of the WeakHashMap is modifying hence calling it during the iteration might cause ConcurrentModificationException. Added a command DO_IF_CONTAINS to safely handle this case.
Changelog
[Android] [Bugfix] - Should fix a ConcurrentModificationException in onResume.
Test Plan
It is hard to reproduce this problem as this is a race condition.
You rather need to have a good set of integration tests or check it in production.

Thanks for the fix! We'll update you if related crash still happens in the future. cc @cpojer

@dryganets - looks like the same crash is still happening:
9Caused by: java.util.ConcurrentModificationException
10java.util.WeakHashMap$HashIterator.nextEntry(WeakHashMap.java:789)
11java.util.WeakHashMap$KeyIterator.next(WeakHashMap.java:822)
12+com.facebook.react.bridge.SynchronizedWeakHashSet.iterate(SynchronizedWeakHashSet.java:63)
13+com.facebook.react.bridge.ReactContext.onHostResume(ReactContext.java:218)
14+com.facebook.react.ReactInstanceManager.moveToResumedLifecycleState(ReactInstanceManager.java:660)
15+com.facebook.react.ReactInstanceManager.onHostResume(ReactInstanceManager.java:579)
16+com.facebook.react.ReactInstanceManager.onHostResume(ReactInstanceManager.java:535)

Thoughts on further corner cases to handle? cc @cpojer

@fkgozali,
I don't see how this could happen now.
All the methods are synchronized.
The iterators are protected with the lock.
For the same thread ConcurrentModification, I had a boolean variable and it was protected with the same lock.


Dockerfile for Snorkel containers

To ease user's setup for running notebooks with Snorkel and all its dependencies, based on jupyter/datascience-notebook.
If user has Docker installed, they can open http://localhost:12345 after
this oneliner:
docker run -it -p12345:8888 --volume "$PWD":/work --rm hazyresearch/snorkel

Configuring your Docker to use our local registry mirror (http://raiders6.stanford.edu:5000) is a good idea as it has to download ~3GB from the cloud.

This is the production Dockerfile mentioned in #321.  The one for development could be done on top of this or separately.
@ajratner Let me know your username for https://hub.docker.com so I can add you to the hazyresearch org owners.

This looks great!  I'll get an account set up on docker hub, and merge this
once new PR is merged- thanks Jaeho!
On Wed, Jul 20, 2016 at 3:23 PM Jaeho Shin<EMAIL_ADDRESS>wrote:

Assigned #323 https://github.com/HazyResearch/snorkel/pull/323 to
@ajratner https://github.com/ajratner.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/HazyResearch/snorkel/pull/323#event-729671367, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ABgw_fn3qu6rjtujJ4Vmh6DnHL0jOp92ks5qXp_MgaJpZM4JRRKw
.

@netj ping me when ready- no rush

Hey @netj just FYI- am snoozing this PR, ping me here whenever I should review & merge!

I've found that the docker image hazyresearch/snorkel is last updated a year ago.
Do you have any newer image?


Use lake serve to start lean server

See also https://github.com/leanprover/vscode-lean4/pull/97.  This is necessary for the workspace symbol search to work in mathlib4: https://github.com/leanprover/lake/pull/46#issuecomment-1028983017

I might wait for https://github.com/leanprover/lake/issues/49 unless someone else wants to do it...


ConsumerGroupStream: Only set committing=true if it can be set false later

Ensure that calling commitQueued() with force=true won't unbalance the this.committing true/false assignments.
Issue https://github.com/SOHU-Co/kafka-node/issues/1065

This looks like a good temporary fix @hyperlink
It roughly matches my logic: https://github.com/aikar/kafka-node/commit/a19b3e34e7502a7c9faba776a2e9c280fbbb5cda#diff-591c50c13e2d409f8187f227a2f6c13bR87
in when the boolean should be set

Thanks for your contribution!


How to avoid np linalg error not positive matrix

from_ewmas(myreturns,...) raised error np linalg error not positive matrix.
How to find which ticks correlated, or  how to solve other way?

Try to compute a sample covariance on parts of your data and see if it is PSD.


BiCGstab smoke tests sometimes does not report useful time...

...e.g., when it did not converge. Similar to #166 . In resolving this issue, also check that it does not occur for other iterative algorithms.

Solution merged


Add scoring logic for users and teams

Calculates a score for a user based on last two bills
Calculates a score for team based on all members with at least two bills

Resolves #166

Code looks great! I tested it out with just one user on a team, and it works as expected. Should we change the heading to How does my electricity bill compare to my neighbors in Cambridge? that way they don't add their June gas and electric bills and get a skewed score?
I ran RSpec and got a failing test in the user_spec. When I ran it again it passed. It must have been an edge case with the randomly generated bill amounts in the factory.

I think you are right, a rounding function makes sense for the view. As far as the test failing, I think that based on your analysis the test itself is wrong, and that zero could be a valid result. (i.e. same energy bill over two months would be 0/something = 0). So that test should simply test for presence. I will make these changes tomorrow and update the PR.


Add profile in Minimalistic

What type of PR is this? (check all applicable)

[x] 🚀 Added Name
[ ] ✨ Feature
[x] ✅ Joined Community
[ ] 🌟 ed the repo
[ ] 🐛 Grammatical Error
[ ] 📝 Documentation Update
[ ] 🚩 Other

Description
Add profile in Minimalistic
Add Link of GitHub Profile
https://github.com/linabellbiu/linabellbiu

Hey @abhisheknaiidu  , any chance my profile qualifies to be added? If not, please let me know what I can do to improve it. Thanks a lot!

Hey @abhisheknaiidu , any chance my profile qualifies to be added? If not, please let me know what I can do to improve it. Thanks a lot!


libcudart.so.10.1: cannot open shared object file: No such file or directory

I just upgraded CUDA version from 10.1 to 10.2 since apex installation keeps encounter bugs for no reason. But I cannot figure out where torch.hub.load calling for libcudart.so.10.1 and raising the bug. Any insight to reinstall or build dependencies is appreciated.
Code
import torch
torch.hub.list('pytorch/fairseq')  # [..., 'lightconv.glu.wmt17.zh-en', ... ]
zh2en = torch.hub.load('pytorch/fairseq', 'lightconv.glu.wmt17.zh-en', tokenizer='moses', bpe='subword_nmt')
assert isinstance(zh2en.models[0], fairseq.models.lightconv.LightConvModel)
zh2en.translate('你好 世界')
What have you tried?
nvcc --version
10.2
torch.version.cuda
10.2
What's your environment?

fairseq Version (master):
PyTorch Version (1.5.1)
OS (Linux):
Python version: 3.6
CUDA/cuDNN version:10.2

Can you reproduce this in pytorch alone?  Something like:
import torch
x = torch.rand(5, 5).cuda()
torch.mm(x, x)

Or is this only happening when trying to use fairseq?  How did you install pytorch?  If you want to use CUDA 10.2 I think you need to explicitly specify when installing: conda install pytorch torchvision cudatoolkit=10.2 -c pytorch

Can you reproduce this in pytorch alone? Something like:
import torch
x = torch.rand(5, 5).cuda()
torch.mm(x, x)

Or is this only happening when trying to use fairseq? How did you install pytorch? If you want to use CUDA 10.2 I think you need to explicitly specify when installing: conda install pytorch torchvision cudatoolkit=10.2 -c pytorch

Thank you for your quick reply. Yes, that definitely works. This error only occurs when using some fairseq methods (fairseq-generate, and torch.hub.load). Surprisingly even fairseq-train works well. I'm wondering if some fairseq function is fixed to call libcudart.so.10.1 during installation, since cuda 10.1 does not exist anymore in my system.

Probably some of the fairseq components need to be recompiled. Try torch.hub.load(..., force_reload=True). Alternatively you may need to clone the fairseq source and run pip install --editable ..

Probably some of the fairseq components need to be recompiled. Try torch.hub.load(..., force_reload=True). Alternatively you may need to clone the fairseq source and run pip install --editable ..

Thanks, I'll have a try.

Fixed, thanks.


[SKIP-1076] AuthorizationSettings for circumventing default blocked actuator

Adds new ActuatorSettings field in application spec for controlling actuator blocking.
It is possible to allow Actuator completely by passing spec.actuatorSettings.allowAll: true, and allow certain endpoints using spec.actuatorSettings.allowList: ["health", "etc"].
According to Istio documentation ALLOW rules are checked after DENY rules, making these trump the earlier DENY rules.
As of now, the tests are not able to spawn the default DENY rule after removing the allowAll: true flag. This is odd however, as this seems to be working just fine when applying the test resources to a local cluster. This seems to be a kuttl issue, see https://github.com/kudobuilder/kuttl/issues/471.

Great input, generalising the specification should be a goal in general, IMO. I will peep this next week :)

Should be good now @omaen :)


How do I enable/disable the different build options

I am trying to enable the SideNav build option but don't know how to accomplish this. Any help would be greatly appreciate it.
Thanks

Side navigation and all other build options are defined in file 'gulpfile.babel.js'
By default you should find option 'sideNav' from gulp task 'dev:generate'.
sideNav: false -> sideNav: true
should do the trick.

Thanks for the quick response :)
I wonder if there is a tutorial online on how to use the generator.


Explore using plutonomy instead of Shrinker

It seems to be better maintained

cc @blamario

https://github.com/well-typed/plutonomy

I tried Plutonomy on Plutarch scripts on a project. There were some decent improvements in some scripts, but there were also some losses for some reason.
But in any case, Plutonomy definitely does a bunch of optimizations that Plutarch doesn't right now.

It would be interesting to explore the differences.

plutonomy is not maintained anymore, and we have compileOptimized that uses optimizer from plutus-core

We need some benchmarks on `compileOptimized


In git bash grr cd doesn't work and grr gd returns a windows style path

I am running Windows 10, and using the latest (5.4) version of RepoZ.
When I try to run a grr cd command, it prints out the matching single repo:
$ grr cd virtual
 virtual-environments   master ≡

but doesn't perform the actual directory change. (Exit code is 0.)
I then tried running grr gd (as a test to see if I at least could for instance a cd $(grr gd <reponame>) workaround in an alias, but it turns out that grr gd returns the path in windows style, e.g. "C:/Users/jkrag/source/repos/virtual-environments/".
I thought that this might be the reason, but now that I actually tested, it turns out that if I try to manually cd to that windows path (with or without the quotes) then it actually works.
The behavior above is seen in both the "Git Bash" terminal (mingw64), in the new Windows terminal configured with Git Bash and in Hyper terminal running the Git Bash.
Can anyone else confirm whether grr cd works is this environment or doesn't?

I can confirm this does not work with MINGW64. I'll have a look at this in a free minute.


Have consistent file structure for sql projects

The file structure for where schemas are created in sql projects when doing create from db and schema compare to update a project is not consistent.
For an example schema Contoso and using "Schema/Object Type" for folder structure, create a project from a database the created file would be Security/Contoso.sql.  Using schema compare to update a project creates the file at Contoso/Schemas/Contoso.sql.
We should make sure that doing a create project from database gives the same resulting file structure as a schema compare apply from that database to an empty project.

As a baseline, lets make sure this creates the same file structure for AdventureWorks or WorldWideImporters

Fixed in DacFx


isValidSpreadType doesn't handle type parameter

TypeScript Version:  2.7.0-dev.20171114
Code
function shallowClone<T extends object>(x: T): T {
    return { ...x };
}

Expected behavior:
No error.
Actual behavior:
src/a.ts(2,14): error TS2698: Spread types may only be created from object types.
@sandersn

This is by design:

...T is not assignable to T

class C {
  m() {
    return 'hi'
  }
}
shallowClone(new C()).m() // runtime error: 'm' is not a function

Typescript doesn't have a spread type because (1) makes it unusable for React without some constraint on T.


Remove copy webpack-stats from dockerfile

Trying to copy webpack-stats.json fails CI on deploy now that webpack is no longer used

Revert this if you don't like it. Merging without approvals as its a veery minor fix and I'm not expecting that many people to be active atm.


Left align blocks of text whenever possible

We might consider left alignment throughout the site for ease of readability / scannability

?

 High-priority GitHub issues before launch


Can't use 443 HTTPS proxy port anymore

I have been experiencing this problem for more than two months, if i use 8088 proxy port the game load slowly
The ISP i use is Indihome

What's the actual cause of the problem? The only problem it has right now is certificate expiration but that happens very recently because I haven't renewed my SSL certificate.

I always use your gbf-proxy with HTTPS port 443 but it's been more than a month that I can't access the game in that way
So now I am using HTTP port 8088 but it is very slow to load the game, can I use the previous way? (maybe my problem has been mentioned by you about SSL certificate)

If the previous way you meant is the HTTPS port 443 then you can try it again, I just renewed the certificate recently.
For the problem with accessing the game through the HTTPS port (outside of expired certificate), I'm not sure what's causing it because I couldn't replicate your problem. Have you checked if this also happens on other ISPs as well?

Ah thank you, that's solved my problem.
Hmm, sorry I've never tried it with other ISP since I only know that Indihome has problem with GBF


[HUDI-1418] set up flink client unit test infra

What is the purpose of the pull request
Add unit test infra to flink client
Brief change log

Added HoodieFlinkTestHarness
Added Unit test for JsonStringToHoodieRecordMapFunction
Refactor HoodieWriteableTestTable to remove Spark components

Verify this pull request
TODO
Committer checklist

[x] Has a corresponding JIRA in PR title & commit

[x] Commit message is descriptive of the change

[ ] CI is green

[ ] Necessary doc changes done or have another open PR

[ ] For large changes, please consider breaking it into sub-tasks under an umbrella JIRA.

Hi @wangxianghu @leesf @yanghua , if any of you have time, please help to review this PR, thanks!

Codecov Report

Merging #2281 (5b5e2fd) into master (bd9ccec) will decrease coverage by 41.88%.
The diff coverage is n/a.

@@              Coverage Diff              @@
##             master    #2281       +/-   ##
=============================================
- Coverage     52.29%   10.40%   -41.89%
+ Complexity     2630       48     -2582
=============================================
  Files           329       51      -278
  Lines         14743     1787    -12956
  Branches       1484      213     -1271
=============================================
- Hits           7710      186     -7524
+ Misses         6419     1588     -4831
+ Partials        614       13      -601

Flag
Coverage Δ
Complexity Δ

hudicli
?
?

hudiclient
?
?

hudicommon
?
?

hudihadoopmr
?
?

huditimelineservice
?
?

hudiutilities
10.40% <ø> (-59.71%)
0.00 <ø> (ø)

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

Impacted Files
Coverage Δ
Complexity Δ

...va/org/apache/hudi/utilities/IdentitySplitter.java
0.00% <0.00%> (-100.00%)
0.00% <0.00%> (-2.00%)

...va/org/apache/hudi/utilities/schema/SchemaSet.java
0.00% <0.00%> (-100.00%)
0.00% <0.00%> (-3.00%)

...a/org/apache/hudi/utilities/sources/RowSource.java
0.00% <0.00%> (-100.00%)
0.00% <0.00%> (-4.00%)

.../org/apache/hudi/utilities/sources/AvroSource.java
0.00% <0.00%> (-100.00%)
0.00% <0.00%> (-1.00%)

.../org/apache/hudi/utilities/sources/JsonSource.java
0.00% <0.00%> (-100.00%)
0.00% <0.00%> (-1.00%)

...rg/apache/hudi/utilities/sources/CsvDFSSource.java
0.00% <0.00%> (-100.00%)
0.00% <0.00%> (-10.00%)

...g/apache/hudi/utilities/sources/JsonDFSSource.java
0.00% <0.00%> (-100.00%)
0.00% <0.00%> (-4.00%)

...apache/hudi/utilities/sources/JsonKafkaSource.java
0.00% <0.00%> (-100.00%)
0.00% <0.00%> (-6.00%)

...pache/hudi/utilities/sources/ParquetDFSSource.java
0.00% <0.00%> (-100.00%)
0.00% <0.00%> (-5.00%)

...lities/schema/SchemaProviderWithPostProcessor.java
0.00% <0.00%> (-100.00%)
0.00% <0.00%> (-4.00%)

... and 306 more

@wangxianghu Can you help to review this PR when you have time? thanks.

@wangxianghu Can you help to review this PR when you have time? thanks.

ack, will review soon

@yanghua @wangxianghu @liujinhui1994 I slightly change the config, shouldn't block the config refactoring I think. Please review again. Thanks!

Ping one more time, @wangxianghu @liujinhui1994 @yanghua any of you guys could review this PR one more time? Thanks a lot!

Ping one more time, @wangxianghu @liujinhui1994 @yanghua any of you guys could review this PR one more time? Thanks a lot!

Will review it tomorrow.

@garyli1019 Similar to the flink client, the java client also needs a similar test framework. Can it be added together?

@garyli1019 Left some minor comments.

@yanghua Thanks for reviewing. Addressed the comments

@garyli1019 Similar to the flink client, the java client also needs a similar test framework. Can it be added together?

Hi @shenh062326 We should definitely add tests for the java client. I am targeting to land this before the release cut, so I am not sure we can add it to this PR.

@garyli1019 Similar to the flink client, the java client also needs a similar test framework. Can it be added together?

IMO, we can open a new PR for the java client.


[master] add aaa

Can one of the admins verify this patch?

Can one of the admins verify this patch?

lgtm


The URL is invalid: two slashes are needed after the http(s):.

Hello,
I have managed to get cors-anywhere setup on my plesk server :)
But I seem to be running into an issue I cannot figure out, no matter what URL I use I am presented with the error:
" The URL is invalid: two slashes are needed after the http(s):. "
This error shows no matter what URL I try to access for example:
https://mycorsproxy.url/http://google.com
https://mycorsproxy.url/https://google.com
Am I missing something obvious here?
Any help is much appreciated, thank you!

Same issue! I´m using Azure Cloud

You have something else running in front of CORS Anywhere that normalizes the URLs. You should disable that URL rewriting mechanism, to preserve the original request URL. If that is not possible at all, an alternative is to omit the scheme.
From a quick search, it seems that Plesk uses Apache. See https://github.com/Rob--W/cors-anywhere/issues/308
For Azure Cloud, see #82.

Thank you for pointing me in the right direction, turning off nginx proxy mode under nginx settings solves the issue in Plesk.

Cloudflare Workers W3C URL JS class has a well known bug that turns "//" into "/" . The CF bug can be googled.

please guide vercel also

If this is useful for someone
Here is a config for nginx

start your cors-anywhere at localhost:4200
Add this config to the nginx

  merge_slashes off;
  location / {
      proxy_pass          http://localhost:4200/;
  }

On PaaS platforms (e.g. Heroku) where there is no "nginx" to configure, add a check before https://github.com/Rob--W/cors-anywhere/blob/70aaa22b3f9ad30c8566024bf25484fd1ed9bda9/lib/cors-anywhere.js#L312 (some may choose to fix the parseURL function instead)


Added ability to configure a node's width and height separately

From #336, added the ability to configure a node's width and height separately when using custom nodes. For example:
node:  {
    size: {
        width: 300,
        height: 200,
    },
}

This does not break any existing configurations. Using this with the standard node shapes will cause the links to disappear, however there is no reason to use a different height and width for these anyways since the d3 shapes cannot be stretched. I explicitly stated that this should only be used for custom nodes in the documentation, as well as added a console.warn() to discourage this incorrect use.
I think this is an important feature for people who want to use custom nodes because when using a custom node with an unequal height and width, unnecessary white space has to be added in order for the node to not be cut off. For example:

Let me know your thoughts on this!

Thanks for the feedback, I've implemented those changes now in the latest commit.
p.s. Ignore the flurry of force pushes, I messed up a bit initially and wanted to clean up the commits a bit 😆


Refactoring VrSystem

Context
With previous implementation, we call the OpenVR API across multiple threads.
Whether it works or not depends on the implementation of OpenVR, which is unknown for us.
During implementing immersive renderer, I found it doesn't work, so I decided to use OpenVR API in a single thread.
Instead, the OpenGL context must be switched between threads. (This is because textures created in the main thread need to be submitted in the OpenVR thread).
Summary

[x] Stop using OpenVR API across multiple thread.

How to check behavior
No behavioral change.

I'll merge this after implementing immersive renderer and confirming this works well.

This doesn't work well.


test(package-manager-support): combine package manager checks with health checks

It's a follow-up PR for https://github.com/aws-amplify/amplify-backend/pull/901#discussion_r1457669965.

use same tests for both Package Manager Support Sanity Checks and Health Checks.

Problem

Issue number, if available:
Changes

Corresponding docs PR, if applicable:
Validation

Test for package-manager-sanity-checks https://github.com/0618/amplify-backend/actions/runs/7620164412
Test for health-checks https://github.com/0618/amplify-backend/actions/runs/7620176164/job/20754460775 (will have another PR to fix the local-checks)

Checklist

[ ] If this PR includes a functional change to the runtime behavior of the code, I have added or updated automated test coverage for this change.
[ ] If this PR requires a change to the Project Architecture README, I have included that update in this PR.
[ ] If this PR requires a docs update, I have linked to that docs PR above.
[x] If this PR modifies E2E tests, makes changes to resource provisioning, or makes SDK calls, I have run the PR checks with the run-e2e label set.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

I'm having second thoughts about doing this refactor. It's becoming clear that combining these two test paths is actually not really the same and keeping them separate makes each test suite easier to understand. I'd suggest we discard this PR. Apologies for the churn!

I agree,
I think we should duplicate logic (pipeline deploy) for now and on the side work to solve underlying problem that prevents us to achieve good code reuse without workarounds in test layout (i.e. solve the vend problem).
The vend problem shouldn't be part of package manager project though, we can take this asynchronously as tech debt.


Pagination, Sorting with Lazyload:false

Hi Mate ,
I have a scenario where i load the data from a recursive query in database which takes around 1 minute to complete , in this case i will get around 20K - 100K+ records.
Do you recommend me to still go with Lazyload:true ? or is Lazyload:false is better in this case ? since for each sort/pagination i cant wait for 1 min to execute.

Hi @Liahus1996, if your able to cut down the server load time by getting a smaller subset I would definitely go for lazy loading and if you optimise your query it shouldn't have to take a minute to return say a 100 records. If you for some reason can't cut down on the load time I guess it's better to have one long loading but it also comes down to the type of data you have and how often it's updated/changed. If the data is pretty static, fetching it once and going through pages and applying filters etc. client side might work but if the data changes often you still might want to go back to the server and get the latest data.
I general I'd say put as much logic as possible on the server and make the client dumb.


'mwc-textfield' on-input provides previous value

When using 'mwc-textfield' and firing the on-input event, e.target.value provides the previous value rather than the changed value. I'm using version 0.2.1.

Is this component available in npm public repo at all?

Is this component available in npm public repo at all?

Nope, please see #76


add mixin ComposableDrawable

related issue: https://github.com/eto-ai/rikai/issues/550

In general , i have some questions w/ the interface design. please take a look

The main issue I have is that the abstractions seem really confusing.

I think so. I think the only interface introduced here is Box2d + "label_text". The impl abstractions are not ideal, but it works. That's why I approved this pull request.

Replaced by a simplified version here https://github.com/eto-ai/rikai/pull/632


Update tr_TR.json

Translation updated

Hi, some previous translations were incorrect. So I updated the translation. The previous editor has stopped updating.

@clickwork-git


Reporting Filters

Concerning filtering, in Wiedmann et al. (2015) they recommend to report:

All filter parameters, including filtertype (high-pass, low-pass, band-pass, band-stop, FIR, IIR), cutoff frequency (including definition), filter order (or length), roll-off or transition bandwidth, passband ripple and stopband attenuation, filter delay(zero-phase, linear-phase, non-linear phase) and causality, and direction of computation (one-pass forward/reverse,or two-pass forward and reverse) must be reported

Checking the MNE documentation and specifically the background on filtering and tutorial, there are some questions that I have:

What is the definition of the cutoff frequency by the filters used in MNE? In the docstring of create_filter it say that -6dB is the middle of the transition window. Does that mean that in MNE, the middle of the transition window is the "half-amplitude" cutoff? (as opposed to half-power)

Filter length and transition bandwidth are being printed upon calling raw.filter(), which is nice - but how would I compute them without having to filter data and copying the values from the console?

I haven't seen a method to calculate stopband attenuation and passband ripple in MNE. Did I miss it? Is there some straight forward way using scipy?

Does anyone besides me think that these outputs would be a nice addition to the raw.info? Maybe providing filter information as a dictionary containing the meta data named above in addition to the frequencies which are the only thing that is specified currently ... opinions?

Someone needs to check all of these things (preferably by showing them by updating the tutorial) because I can't remember offhand, but yes what you say sounds right. Do you have the time / knowledge to check and update it?

Filter length and transition bandwidth are being printed upon calling raw.filter(), which is nice - but how would I compute them without having to filter data and copying the values from the console?

mne.filter.create_filter will create the filter and give these log messages. You can pass it a dummy data array. Actually we should proably make data=None a possibility, meaning "skip length checks/warnings".

I haven't seen a method to calculate stopband attenuation and passband ripple in MNE. Did I miss it? Is there some straight forward way using scipy?

This would be another great addition to the tutorial. We use standard scipy.signal.firwin design, so these properties are dependent upon the window used in design. In theory this might be documented in  SciPy. If not, they should probably be added there. They are standard windows so the values should be listed online somewhere, probably on Wikipedia. We should make a table...

Does anyone besides me think that these outputs would be a nice addition to the raw.info?

Yes in principle but in practice there is a limited set of items we can put in raw.info and the filter parameters are not included. If you want you can modify raw.info['description'] string to include this information.

I'll see what I can do ... I don't have a lot of knowledge about filters though, .. and the scipy docstring for firwin does not specify details about the cutoff either. So maybe I will post a question to stackexchange signal processing or stackoverflow for help ...
related: The docstring "Returns" seems to be wrong. It actually returns h, the filter coefficients:
https://github.com/mne-tools/mne-python/blob/45898628a416691a89a8d48ca38860298cfb58fc/mne/filter.py#L337-L374

Here is a table, the "peak approximation error" here is really the stop-band attenuation (e.g., 53 dB for Hamming) which matches the table in Ifeachor and Jervis p357 (except Blackman attenuation, which I&J list as 75 dB):
https://www.allaboutcircuits.com/technical-articles/design-examples-of-fir-filters-using-window-method/
Filters designed using windowed FIR design have equal pass-band and stop-band ripple, so giving the attenuation effectively gives you those numbers, too.

That's already great. Do you suggest that I copy the table (Ifeachor and Jervis) into the updated version of the "Background on Filtering" example?

I'd do that together with a short intro on Wiedmann's recommendations on what to report of filters ... then followed by a code block on how to get transition bandwidth and filter length.
Then the only missing information at this point is:

are the scipy.signal.firwin filter cutoffs specified in half-amplitude or half-power at the middle of the transition band?
source that "Filters designed using windowed FIR design have equal pass-band and stop-band ripple" (the table actually suggests otherwise?)
all of the above information for IIR filters?

... would be super cool if we had a function to automatically add a fully specified methods section report from filter settings :)

This could be added to the logger.info of create_filter

Reopening this since @bmaess brought up the idea again, and noted we should do this for IIR filters, as well.

Concerning the -3dB versus -6dB problem: Both is 'correct' and it offers a very elegant way to publish the cutoff limits for the forward-backward filters: design the filter using the -3dB cutoff and in case of the two-pass filter - present the cutoff values as -6dB values. If the corresponding report also mentions the damping of the cutoff, there should be no problem. A bandpass designed as a single-pass 5th order butterworth with -3dB cutoffs at 8 and 12 Hz becomes a two-pass filter of 10th order butterworth with -6dB cutoffs at 8 and 12 Hz.


logging config small refinements

This PR addresses three small, but yet important details:

error log file:

rotating;
proper configuration of its location, based on user given setting;
documentation;

--log-level command line option: should also be applied to the log file, not just the console;
show-(log)-config: the command show-config should also display the log config, including when the user has not set anything -- the defaults should then be displayed.

Codecov Report

Merging #1402 into master will increase coverage by <.01%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master    #1402      +/-   ##
==========================================
+ Coverage   98.37%   98.38%   +<.01%
==========================================
  Files          56       56
  Lines        2590     2595       +5
==========================================
+ Hits         2548     2553       +5
  Misses         42       42

We discussed one small change in the docs: suggest they use bigchaindb show-config to find out the default configuration settings. Otherwise :+1:

Since the default log config is now written to file, upon running bigchaindb configure, I updated the default in the docs.


Add nava play library

What does this implement/fix? Explain your changes.
Formerly we used play_sound function to play sound in mytimer. Now we add nava's play function to play sounds.

Should we separate runs for each OS and install dependency packages for each repositories in which nava is being used?
That's not a good think. @sepandhaghighi

@sepandhaghighi do we need to install sudo apt-get install alsa-utils for solving this issue?
That would be a mess tbh.

@sepandhaghighi do we need to install sudo apt-get install alsa-utils for solving this issue? That would be a mess tbh.

No, it is out of the scope of this app.
We should cover the play function with a try-except block.
Something like:
def play_sound(sound_path):
    """
    Play sound.

    :param sound_path: sound path
    :type sound_path: str
    :return: None
    """
    try:
        play(sound_path)
    except Exception:
        print(SOUND_ERROR_MESSAGE)

Thanks for the review @sepandhaghighi
Your concerns addressed in commits.
Please re-review.


Fix code scanning alert - Uncontrolled data used in path expression

Tracking issue for:

[ ] https://github.com/pshongwe/Orda_v1.0/security/code-scanning/2

Fixed the uncontrolled data being used in path expression and waiting to be merged

taking the risk


Switches are not synced

Describe the bug
It seems that I can see all resources that I expect, except for the switches.
Firmware of your Miniserver
<IP_ADDRESS>
HomeAssistant install method
Virtual machine
Version of HomeAssistant
2024.12.2
Version of Pyloxone
0.7.1
Update pyloxone
Yes
Log
Settings for the log can be found on the main page under the section Log Configuration

@pieter-jangoeman did you define a room and a room for the switches. Read thru already closed issues.

I believe I do:

I have the same issue, newly added swithces are not showing up, old switches are still available and do work when changing state in HA

I believe I do:

This is a push button not a switch. Have you searched for a push button with this name?

Nevermind, got them! I updated my Loxone and they appeared... Thanks for the help!


storybook: Change category from Feedback to Data Display for three components

Hey, I just made a Pull Request!

Changes three components from "Feedback" to "Data Display" category in the Storybook.
Other gauges in the same directory are already "Data Display", so thought that was an easy one.  The status circle is a bit harder, but my interpretation of the categories is:

Data Display: Used to display data ABOUT things, like entities or information in entities.
Feedback: Used to feed back to the user about things in Backstage or the UI, e.g. when there's an error, or an issue, or something can be dismissed, etc.

So it seems to me the Status icon ( 🔴  🟢 etc) to always be to display status ABOUT data (a Jenkins build, a Lighthouse result), rather than feedback about Backstage itself or the UI in anyway - so it seems to me it's a data display element, instead.
Open to counter opinions?

Old
New

:heavy_check_mark: Checklist

[ ] A changeset describing the change and affected packages. (more info)
[ ] Added or updated documentation
[ ] Tests for new functionality and regression tests for bug fixes
[x] Screenshots attached (for UI changes)

cc @katz95 if this is your wheelhouse

cc @katz95 if this is your wheelhouse


preview-assets

make assets per preview pr

Reference Server Preview is available here:https://anchor-ref-pr462.previews.kube001.services.stellar-ops.com/SEP Server Preview is available here:https://anchor-sep-pr462.previews.kube001.services.stellar-ops.com/


Separate naming of rules from definition of rules

Simple enough; it'd really just be the following + the closure-based stuff:
#[macro_export]
macro_rules! named (
    ($name:ident<$i:ty,$o:ty>, $rule:tt) => (
        fn<$i,$o>( i: $i ) -> IResult<$i,$o> {
            ($rule)( i )
        }
    );
    ($name:ident, $rule:tt) => (
        named!( $name<&[u8], &[u8]>, $rule )
    );
);

If you wanted to be really fancy, you could abstract the _parser! stuff like so:
#[macro_export]
macro_rules! parser (
    (alt, $i:ident, $($rest:tt)*) => ( alt_parser!( $i | $rest ) );
    ...
);

and then replace $rule:tt and ($rule)( i ) with $rule:ident, $($rest:tt)* and parser!( $rule, i, $rest ) in named.
Then you'd be able to say named!( foo, take, 3 ) and it wouldn't even have any closure overhead :smiley:

It is done now :smile:


Probably wrong release notes?

What did you do?
Two BUGFIXES in the release notes https://github.com/prometheus/prometheus/releases/tag/v2.45.1 refer to #12644. But this task is open and seems to have nothing to do with the mentioned bugs.
What did you expect to see?
the correct links
What did you see instead? Under which circumstances?
n/a
System information
n/a
Prometheus version
n/a

Prometheus configuration file
n/a

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

Nice catch @datamuc
I think the right links are:

[BUGFIX] Linode SD: Cast InstanceSpec values to int64 to avoid overflows on
386 architecture. https://github.com/prometheus/prometheus/pull/12568
[BUGFIX] TSDB: Handle TOC parsing failures. https://github.com/prometheus/prometheus/pull/10623

cc @roidelapluie

Thanks, I have updated it now


Add the ability to get a scenario variable

Currently you can get and set global variables, however you can only set and assert scenario variables. It would be useful to have a function in apickli.js to get a scenario variables.

why dont to prefix a global variable name with scenario prefix?

In the before hook, we typically re-instantiate apickli. In the apickli constructor we only reset this.scenarioVariables and not global variables (obviously :) ). As a work around, I am resetting the global variable too in the Before hook, but it would be good not to have to do this.
e.g.
this.Before(function(scenario, callback) {
this.apickli = new apickli.Apickli('https', 'something.apigee.net/v1');
this.apickli.setGlobalVariable('{scenarioVariableToBeRead}', '');
callback();
});

@seantdg - does this affect your recent PR?

Would you like to use this instead?
this.apickli.scenarioVariables

I can't think of any additional validation we would do on the scenario variable value before setting it, so I don't mind either way.

what you really want is to encapsulate this type of access in a function, right?

what you really want is to encapsulate this type of access in a function, right?

We already have Apickli.prototype.storeValueInScenarioScope(variableName, value)
so I am happy.


HTTP_PROXY

Reset the HTTP_PROXY does not require, as the vulnerability is only in legacy programs that did not have security patches applied. The most correct way is to apply automatic security patches without updating the software.

RHEL based: yum-cron(update_cmd=security).
Ubuntu: unattended-upgrades + Unattended-Upgrade::Allowed-Origins { ... "${distro_id}:${distro_codename}-security"; ... }.

https://httpoxy.org/
Open for PR.

Closing with https://github.com/agarzon/nginx-config/commit/94eba5a074bf24208116ab5cb7ceba2aec87a40b


Chart for version 7.17.0 missing

Hi from what I see elasticsearch version 7.17.0 was released a few days ago.
However, I cannot see any chart update for that version?

Would also like to know. We would like to start patching this issue.  https://discuss.elastic.co/t/kibana-7-17-0-security-update/296215

Hi @rgarcia89,
Unfortunately, there is no ETA for 7.17.0 Helm release.
We have some changes to implement and PRs to integrate before publishing a release.

With the release of 8.0.0, I'd be curious to find out when that chart is coming as well...

Bit odd to see how long the chart update are taking this time. Especially since the ECK repo has already been updated.

Helm charts 7.17.1 are finally released 🎉 => https://github.com/elastic/helm-charts/releases/tag/v7.17.1


add gitignore for .vscode folder

this ensures users who work with vscode to develop vscode :package:  don't accidentally add the .vscode folder into their commits.

Hi @AkashGutha, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution!

This seems like a small (but important) contribution, so no Contribution License Agreement is required at this point. Real humans will now evaluate your PR.

TTYL, MSBOT;

@AkashGutha The point of the .vscode folder is to share config between others so I think the PR goes into the wrong direction. What is your use-case?

@AkashGutha You can always use User Settings to customize VS Code options, workspace settings (that live in the .vscode folder) belong with the workspace.

i ddin't look through that . thanks @alexandrudima  @jrieken .


vk: add /usr/local/lib to rpath on macos

For reasons unknown, after upgrading to XCode 15.3, dlopen can no longer find libvulkan.1.dylib. We fix it by explicitly adding /usr/local/lib to rpath for macos.

hmm, made a mistake.  this doesn't fix the issue.


Fix platform setup script, add kubectl installation

Fixed broken platform setup for tkn and helm
Added in kubectl installation
Fixed cosign installation
Linting and formatting

Not a blocker, but we should be consistent when referring to variables. Either we always use "${var}", either "$var", but we should not switch between both the 2 forms.

Not a blocker, but we should be consistent when referring to variables. Either we always use "${var}", either "$var", but we should not switch between both the 2 forms.

Agreed. I will make a github issue for shell linting.

Annie and I should address that today.
However shellcheck does not address the consistency problem. Would you have another linter in mind for bash/sell by any chance?

Annie and I should address that today.
However shellcheck does not address the consistency problem. Would you have another linter in mind for bash/sell by any chance?

I'm not sure there's a style enforcement tool for bash scripting. shellcheck is pretty much the closest you get, but we could refer folks to the Google Shell Style guide (example for shell variables).

Alright, I think we can continue the conversation for shell style and linting in #64


Vormetric Keys for Storage / Database

This PR rotates our encryption to use the RSA keys provided by Vormetric.
Changes

Rotates storage account to use the Vormetric key
Rotates database to use the Vormetric key

Checklist

[ ] Tested locally?
[ ] Added new dependencies?
[ ] Updated the docs?
[ ] Added a test?
[ ] Did you check for sensitive data, and remove any?
[ ] Are additional approvals needed for this change?
[ ] Are there potential vulnerabilities or licensing issues with any new dependencies introduced?

Fixes

#issue

To Be Done

Once this is verified in test, we reach out to the IAMB team, they send us keys in prod, we update our config to use in prod, then deploy.

@cglodosky I could use your assistance testing this in our test environment. We can investigate after #521.

Aiming to test around 3:30pm EST, after @jimduff-usds gives me an overview of running smoke tests in staging.


Questions about the Gamma distribution parameters

I need help linking the parameter from the various models to the appropriate distribution parameters as I was unable to locate all the answers in the documentations

r and alpha from the BetaGeoFitter and ModifiedBetaGeoFitter functions

r is the shape parameter of the Gamma distribution
alpha is the rate or 1/scale parameter of the Gamma distribution
Is that correct?

p, q and v from the GammaGammaFitter function

p is the shape parameter of the Gamma distribution. The model assumes that this parameter is the same for all customers.
v  is the rate parameter of the Gamma distribution. This parameter varies across customers and has a prior that is also gamma distributed with parameters (q, gamma)
Gama(p, v) defines the distribution of a customer’s observed average transaction value
The expected value of this distribution is p/v ( Shape parameter / Rate parameter]
q is the shape parameter of the 2nd Gamma distribution
Is that correct?

Why is the 'gamma' parameter for the 2nd Gamma distribution (the rate parameter) is not provided as an output? The reason I am asking is that based on the “The Gamma-Gamma Model of Monetary Value” paper by Peter Fader the population mean is Eq. 3 is

gamma* p / (q-1)
where gamma is the rate parameter of the 2nd Gamma distribution
However, in the fit methods of GammaGammaFitter the population mean is the

v * p / (q - 1)

where v is the rate parameter of the 1st distribution.
Which equation is the correct one?

I noticed that when calculating the probability that a customer with history (frequency, recency, T) is currently alive using the conditional_probability_alive for the ModifiedBetaGeoFitter there is always a large spike at p=0.5 in the histogram of the estimated probabilities? Why is that?

For the conditional_expected_number_of_purchases_up_to_time and expected_number_of_purchases_up_to_time methods, does the input t represent the time from the first transaction, or a forecasted time ( i.e., Current time + t)?

Thank you!

Hi,
Not an expert but from my limited experience:

p, q and v from the GammaGammaFitter function
p is the shape parameter of the Gamma distribution. The model assumes that this parameter is the same for all customers.
v is the rate parameter of the Gamma distribution. This parameter varies across customers and has a prior that is also gamma distributed with parameters (q, gamma)
Gama(p, v) defines the distribution of a customer’s observed average transaction value
The expected value of this distribution is p/v ( Shape parameter / Rate parameter]
q is the shape parameter of the 2nd Gamma distribution
Is that correct?

The symbols used are a little confusing -  I think that 'v' actually represents  'γ' from the second gamma distribution, not 'ν' from the first gamma distribution.

Why is the 'gamma' parameter for the 2nd Gamma distribution (the rate parameter) is not provided as an output?

It is - see above.

I noticed that when calculating the probability that a customer with history (frequency, recency, T) is currently alive using the conditional_probability_alive for the ModifiedBetaGeoFitter there is always a large spike at p=0.5 in the histogram of the estimated probabilities? Why is that?

From my dataset the distribution of P(Alive) for customers with frequency=0 is very different from frequency>0.  Could the spike be related to one-time buyers?

For the conditional_expected_number_of_purchases_up_to_time and expected_number_of_purchases_up_to_time methods, does the input t represent the time from the first transaction, or a forecasted time ( i.e., Current time + t)?

I believe that t represents the forecast period, i.e. for the period t following the end of your observation period, your customers are expected to make so many purchases.
Hope that helps,
Duncan

Thank you for taking the time to response. Your answer regarding the P(Alive) makes sense and I was able to reproduce it.
The Gamma-Gamma model should have 4 output parameters (2 parameters per each Gamma distribution). The GammaGammaFitter function outputs only 3 parameters (p,q, and v); therefore I am asking regarding the 4th output
It looks like we are agreeing that the p and q values are the shape parameters for two different Gamma distribution, what I am still not clear on is which Gamma distribution does the v output parameter from the GammaGammaFitter function corresponds with. Is it

the Rate parameters corresponding with the p shape parameter (1st Gamma distribution) ?
or
the Rate parameter corresponding with the q shape parameters (2nd Gamma distribution which defines the distribution of a customer’s observed average transaction value)?

If the expected value is p/v then this v is the rate parameter corresponding with the p shape parameter and not q (See Page 2, i) of The “Gamma-Gamma Model of Monetary Value” paper by Peter Fader)
However, in Eq. 3 of the same paper, the mean is defined as gamma* p / (q-1) while in the fit methods of GammaGammaFitter the population mean was implemented as v * p / (q - 1). In this case, v is the rate parameter corresponding with the q shape parameter and not p.
Am I missing something?

As stated in 2) ii of the paper:

ν ~ gamma(q, γ)

which as I interpret* it implies that

zi ~ gamma(p, gamma(q, γ))

I.e. The output of the second gamma distribution is the scale parameter for the first gamma distribution.
If it's useful, I've posted some code here showing how I plotted the Gamma-Gamma distribution for my dataset (copying the example here).
Cheers,
Duncan
*Disclaimer: not a statistician

@dmanhattan Thank you for taking the time to share your script. I will review it and let you know if I have any further questions.

@shaddyab, I am referring to the 1st question in your 1st comment:
"r and alpha from the BetaGeoFitter and ModifiedBetaGeoFitter functions
r is the shape parameter of the Gamma distribution
alpha is the rate or 1/scale parameter of the Gamma distribution
Is that correct?"
I have the same doubt, were you able to clarify this? I did not find a response to this question in the thread. Thank you

This is right. You can plot scipy.stats.gamma.rvs(r, scale=1/alpha, size = 1000) as your distribution (heterogeneity) of lambda, and similarly scipy.stats.beta.rvs(a, b, size=1000) for the heterogeneity of p.


libmujoco.so.2.1.1 mj_certQuestion

I downlaod & extract mujoco 2.1.1;
Install dm_control by chnaging setup.py:  'dm-control==0.0.364896371',
Ubutnu 20.04, python 3.6.9
But I got error..
AttributeError: /home/delkov/.mujoco/lib/libmujoco.so.2.1.1: undefined symbol: mj_certQuestion

Any reason you're trying to install 2.1.1? I'd just go for the latest dm_control (1.0.2) and mujoco (2.1.5) which you can install with pip install --upgrade dm_control.


Fix Big Button Example - Issue #1099

Overview
This PR fixes the bug that happens while applying the example, as referred at issue #1099  :
<Pane display="flex">   <TextInput width="100%" height={48} placeholder="Change my height to fit your needs." />   <Button height={48} appearance="primary" marginLeft={16}>Big Button</Button> </Pane>
I updated the button style properties by adding white-space: nowrap;.
Screenshots (if applicable)
Before:

After:

Documentation

[x] Updated Typescript types and/or component PropTypes
[ ] Added / modified component docs
[ ] Added / modified Storybook stories

@colinlohner  @akleiner2  could you guys take a look and if it is possible to add the label hacktoberfest-accepted?


Feat: Add Threagile parser

:warning: Note on feature completeness :warning:
We are narrowing the scope of acceptable enhancements to DefectDojo in preparation for v3. Learn more here:
https://github.com/DefectDojo/django-DefectDojo/blob/master/readme-docs/CONTRIBUTING.md
Description
Describe the feature / bug fix implemented by this PR.
If this is a new parser, the parser guide may be worth (re)reading.
Test results
Ideally you extend the test suite in tests/ and dojo/unittests to cover the changed in this PR.
Alternatively, describe what you have and haven't tested.
Documentation
Please update any documentation when needed in the documentation folder)
Checklist
This checklist is for your information.

[x] Make sure to rebase your PR against the very latest dev.
[x] Features/Changes should be submitted against the dev.
[ ] Bugfixes should be submitted against the bugfix branch.
[x] Give a meaningful name to your PR, as it may end up being used in the release notes.
[x] Your code is flake8 compliant.
[x] Your code is python 3.11 compliant.
[x] If this is a new feature and not a bug fix, you've included the proper documentation in the docs at https://github.com/DefectDojo/django-DefectDojo/tree/dev/docs as part of this PR.
[ ] Model changes must include the necessary migrations in the dojo/db_migrations folder.
[x] Add applicable tests to the unit tests.
[ ] Add the proper label to categorize your PR.

Extra information
Please clear everything below when submitting your pull request, it's here purely for your information.
Moderators: Labels currently accepted for PRs:

Import Scans (for new scanners/importers)
enhancement
performance
feature
bugfix
maintenance (a.k.a chores)
dependencies
New Migration (when the PR introduces a DB migration)
settings_changes (when the PR introduces changes or new settings in settings.dist.py)

Contributors: Git Tips
Rebase on dev branch
If the dev branch has changed since you started working on it, please rebase your work after the current dev.
On your working branch mybranch:
git rebase dev mybranch

In case of conflict:
 git mergetool
 git rebase --continue

When everything's fine on your local branch, force push to your myOrigin remote:
git push myOrigin --force-with-lease

To cancel everything:
git rebase --abort

Squashing commits
git rebase -i origin/dev

Replace pick by fixup on the commits you want squashed out
Replace pick by reword on the first commit if you want to change the commit message
Save the file and quit your editor

Force push to your myOrigin remote:
git push myOrigin --force-with-lease

Thanks for making those changes! Test are very closely. Please see errors below
2023-10-11T04:02:46.9464626Z uwsgi_1         | ======================================================================
2023-10-11T04:02:46.9465215Z uwsgi_1         | FAIL: test_file_with_vulnerabilities_returns_correct_findings (unittests.tools.test_threagile_parser.TestThreAgileParser.test_file_with_vulnerabilities_returns_correct_findings)
2023-10-11T04:02:46.9465460Z uwsgi_1         | ----------------------------------------------------------------------
2023-10-11T04:02:46.9465681Z uwsgi_1         | Traceback (most recent call last):
2023-10-11T04:02:46.9466100Z uwsgi_1         |   File "/app/unittests/tools/test_threagile_parser.py", line 31, in test_file_with_vulnerabilities_returns_correct_findings
2023-10-11T04:02:46.9466335Z uwsgi_1         |     self.assertEqual("501", finding.cwe)
2023-10-11T04:02:46.9466537Z uwsgi_1         | AssertionError: '501' != 501
2023-10-11T04:02:46.9466657Z uwsgi_1         |
2023-10-11T04:02:46.9466899Z uwsgi_1         | ======================================================================
2023-10-11T04:02:46.9467466Z uwsgi_1         | FAIL: test_mitigated_is_mitigated (unittests.tools.test_threagile_parser.TestThreAgileParser.test_mitigated_is_mitigated)
2023-10-11T04:02:46.9467718Z uwsgi_1         | ----------------------------------------------------------------------
2023-10-11T04:02:46.9467942Z uwsgi_1         | Traceback (most recent call last):
2023-10-11T04:02:46.9468308Z uwsgi_1         |   File "/app/unittests/tools/test_threagile_parser.py", line 61, in test_mitigated_is_mitigated
2023-10-11T04:02:46.9468542Z uwsgi_1         |     self.assertTrue(finding.mitigated)
2023-10-11T04:02:46.9468760Z uwsgi_1         | AssertionError: None is not true
2023-10-11T04:02:46.9468895Z uwsgi_1         |
2023-10-11T04:02:46.9469120Z uwsgi_1         | ----------------------------------------------------------------------
2023-10-11T04:02:46.9469316Z uwsgi_1         | Ran 2595 tests in 509.099s
2023-10-11T04:02:46.9469454Z uwsgi_1         |
2023-10-11T04:02:46.9469773Z uwsgi_1         | FAILED (failures=2, skipped=475)

I saw some workflow errors regarding merge conflicts. I tried the following but I cannot force push
git checkout feat/add_trheagile_parser
git rebase upstream/dev # to rebase my branch onto the latest dev
git push -f

but I get the following error
 ! [remote rejected]     feat/add_threagile_parser -> feat/add_threagile_parser (refusing to allow a Personal Access Token to create or update workflow `.github/workflows/cancel-outdated-workflow-runs.yml` without `workflow` scope)
error: failed to push some refs to 'https://github.com/avlahop/django-DefectDojo.git'

Not sure but I would like some support here.


Native list operations have redundant checks

The JSArray.[] getter appears hot on some internal profiles.
Here's the generated code.  Worth cleaning up the low hanging fruit here (specializing in JS):
      [dartx._get](index) {
        if (!(typeof index == 'number')) dart.throw(_js_helper.diagnoseIndexError(this, index));
        if (dart.notNull(index) >= dart.notNull(this[dartx.length]) || dart.notNull(index) < 0) dart.throw(_js_helper.diagnoseIndexError(this, index));
        return this[index];
      }

this was fixed! yay :)

was in https://codereview.chromium.org/2927763004/


Error while running the script: unconverted data remains: 3

Hello,
Thanks for good job!
Select Add-On (place a lowercase x for the relevant add-on)

Xiaomi Mi Scale https://github.com/lolouk44/hassio-addons/tree/master/mi-scale

Describe the bug
I have a errors in log

and it do not work.
Once it seems that has read my last measuremt under the name of Jo, when i have not corrected my config

But then, do not work.
Scale (please complete the following information):

Mi Body Composition Scale | XMTZC02HM

Device running Home Assistant (please complete the following information):

Actual Home Assistant with Supervisor
Device used to run the Script/Container Rrpi4 Docker
Bluetooth device used: Built-in

Thanks a lot!

I had a mistake in config. All works fine!
Thanks a lot!!!

Thanks. Out of interest could you confirm what tout dis wrong?
I have forgot Backquote in config.
Thanks a lot!


Fixes UPS GUI broken links in studio

This PR solves the ticket: AGPUSH-15180
Same as #826
Reason
In a previous PR (#804) the ngLink directive that was causing a double HTTP request was changed into a simple href property. This might have caused the current issue.
Solution
Revert the changes made in #804.
Collateral Damage
Reverting to #804 will re-open the double requests issue so this fix should be only temporal until a better solution is found.

:+1:


Incomplete tutorial. Need to add UDR to make this work.

Hi, I followed this article to create Hub and Spoke Transit VNET but the spoke failed to get the route from another spoke. I've posted my question to the community (https://docs.microsoft.com/en-us/answers/questions/706913/vpn-gateway-transit-for-virtual-network-peering.html) and was advised to add UDR.
It appears that this article missing the UDR part to make this hub and spoke setup to work.

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

ID: 9d098f17-7f58-4304-0634-0f57d1d3300a
Version Independent ID: 5624ffea-22c6-8f02-e9fe-a3be3a7cced5
Content: Configure VPN gateway transit for virtual network peering - Azure VPN Gateway
Content Source: articles/vpn-gateway/vpn-gateway-peering-gateway-transit.md
Service: vpn-gateway
GitHub Login: @cherylmc
Microsoft Alias: cherylmc

#reassign:anzaman

#reassign:deeharris-23


Download Progress Queue Display

Need the ability to display the progress of items being downloaded.
This can be a simple list of available items and the progress that is occuring.  Nice to haves are the ability to pause, resume, and cancel items from the queue.
Progress could also be displayed as a widget on the Main Menu screen.

Downloads are out of scope for 2.0.0.


[CMake/build-script/Platform] Stop depending on and inferring simulator-ness.

The *-simulator target triples have been used consistently in build systems for
several years to indicate simulator targets... except for Swift's own CMake configuration
and build-script. Teach our own build to use proper simulator triples like
x86_64-apple-ios7.0-simulator throughout.
Then, stop inferring the simulator part, rdar://problem/35810403.

@swift-ci please test

Seems like we should also remove this from swift-driver. https://github.com/apple/swift-driver/blob/master/Sources/SwiftDriver/Utilities/Triple%2BPlatforms.swift#L133

Build failed
Swift Test Linux Platform
Git Sha - 2d66f2b50a3a28f3b8beb7986eec59cc8aa5cc48

Linux failure is unrelated. Trying again...

@swift-ci please test source compatibility

@swift-ci please smoke test Linux

GitHub connectivity problems affected the compatibility suite. Sigh.

Build failed
Swift Test OS X Platform
Git Sha - 2d66f2b50a3a28f3b8beb7986eec59cc8aa5cc48

Sigh. I need to split this pull request into "fix our build system / test" and "remove the cruft".

@swift-ci please test

Build failed
Swift Test Linux Platform
Git Sha - 2d66f2b50a3a28f3b8beb7986eec59cc8aa5cc48

Build failed
Swift Test OS X Platform
Git Sha - 2d66f2b50a3a28f3b8beb7986eec59cc8aa5cc48

@swift-ci please clean test

@swift-ci please clean test

@swift-ci please test source compatibility

@swift-ci please clean test

@swift-ci please test source compatibility

Build failed
Swift Test OS X Platform
Git Sha - 7346da6a2719ce6024eb8758e5feacbee3dcea18

Build failed
Swift Test Linux Platform
Git Sha - 7346da6a2719ce6024eb8758e5feacbee3dcea18

@swift-ci please test

Build failed
Swift Test Linux Platform
Git Sha - 7346da6a2719ce6024eb8758e5feacbee3dcea18

Build failed
Swift Test OS X Platform
Git Sha - 7346da6a2719ce6024eb8758e5feacbee3dcea18

Much of this pull request came in via https://github.com/apple/swift/pull/30843. I'll rebase the rest on top of this.

@swift-ci please test

@swift-ci please test source compatibility

@swift-ci please test

@swift-ci please test source compatibility

Build failed
Swift Test Linux Platform
Git Sha - 643491e37c4799526a83fd37f345b43fda90dd42

Build failed
Swift Test OS X Platform
Git Sha - 643491e37c4799526a83fd37f345b43fda90dd42

Build failed
Swift Test Linux Platform
Git Sha - 643491e37c4799526a83fd37f345b43fda90dd42

Build failed
Swift Test OS X Platform
Git Sha - 643491e37c4799526a83fd37f345b43fda90dd42

@swift-ci please test

@swift-ci please test source compatibility

Build failed
Swift Test Linux Platform
Git Sha - 856855dd740a682aa70a3b080a429939c78524dc

Build failed
Swift Test OS X Platform
Git Sha - 856855dd740a682aa70a3b080a429939c78524dc

@swift-ci please test

@swift-ci please test

Build failed
Swift Test Linux Platform
Git Sha - 1a860e74c4d97c21a5c57fd2791eeb931a360ebb

@swift-ci test platform Linux

@swift-ci smoke test Linux

@swift-ci smoke test Linux

When this was merged, the Linux PR testing started failing in lldb tests. First Failure here: https://ci.swift.org/job/oss-swift-package-linux-ubuntu-16_04/4933/
I have no idea what's going on, it doesn't make much sense, but the revert unblocked things.


CORE-16614: index utxo_visible_transaction_state.consumed

This PR indexes consumed field of utxo_visible_transaction_state.
This is to improve performance of UtxoPersistenceService.findUnconsumedVisibleStatesByType query so that other tables are pre-sorted by consumed timestamp and we can fetch unsonsumed data quickly.
Index created:

the query

database optimizer has chosen to use an index to retrieve rows from the table

A partial index is an alternative to achieve this, which is faster by indexing null records only (unconsumed states)
The drawbacks of the implementation is:

maintenance if there are other types dbms
implementation doesn't look intuitive as below (stackOverFlow link)

<changeSet  author="some_author" id="someId"  context="some_context" dbms="some_db_key">
    <preConditions onFail="MARK_RAN">

        <columnExists tableName="some_table_name" columnName="Col1"/>

        <columnExists tableName="some_table_name" columnName="Col2"/>

    </preConditions>

    <sql splitStatements="true" stripComments="true" endDelimiter="\nGO">
        CREATE UNIQUE INDEX idx_unique_colName1_colName2 ON some_table_name (Col1, Col2)
        WHERE Col2 = '1'
    </sql>
</changeSet>


Release pipeline speed-up changes incorporating bugfix

Context
Previously deployed change that was reverted due to a bug being discovered in the container instance entrypoint command that resulted in a P1 service incident.
Changes proposed in this pull request
This change is identical to the previous PR (https://github.com/DFE-Digital/apply-for-postgraduate-teacher-training/pull/1319) with the following revisions:

The container instance command parameter has been revised to properly quote the command.
The diff mechanism used with Git now correctly determines the diff between all PRs to be merged into master correctly. Previously it was only comparing with the most recent PR, it now correctly compares the currently deployed PR with all the changes up to the new commit.

Guidance to review
See previous PR. Testing evidence in pipeline here: https://dfe-ssp.visualstudio.com/Become-A-Teacher/_build?definitionId=49&_a=summary&repositoryFilter=37&branchFilter=9070
Link to Trello card
https://trello.com/c/rlWTivDw/1648-bug-container-instance-update-from-cli-failing
Things to check

[x] This code doesn't rely on migrations in the same Pull Request
[ ] If this code includes a migration adding or changing columns, it also backfills existing records for consistency
[ ] API release notes have been updated if necessary
[ ] New environment variables have been added to the Azure config

I'm afraid this is "baby's first powershell review", so it's probably a bit off. I think the code makes sense. Shall we merge and deploy together tomorrow?

Happy to merge and deploy with you. I'm looking at your comments now. I can do something about the latter two, but the variable groups I'm going to need to have a think about because I'm not quite sure how easy that will be to handle.


Decouple from githooks?

First off, this looks really helpful. Unfortunately, hooks aren't ideal for the workflow that I follow (and for various organizational reasons, that workflow can't be changed). Would it be possible to expose the core library so that grunt or gulp tasks could be written around it?

Is there more work to do here? :dancer:

I still suspect it could be useful to separate out the parse/rewrite code from the actual githook part, but I don't have a specific need at the moment, so yea, I think this can be closed.


The 1.1 release is not in this repository

https://hackage.haskell.org/package/rounded metadata points here.

https://github.com/ekmett/rounded/releases/tag/rounded-1.1 https://github.com/ekmett/rounded/tree/v1.x

https://github.com/ekmett/rounded/releases/tag/rounded-1.1 https://github.com/ekmett/rounded/tree/v1.x

Is there a reason why master is not pointing there as well, or why v1.x isn't the default branch on GitHub?
This is slightly confusing setup.

Is there a reason why master is not pointing there as well, or why v1.x isn't the default branch on GitHub?
This is slightly confusing setup.

Ah, good point - I've updated master, not sure how to make v1.x default (I don't use github much).  Thanks for the report!

Ah, good point - I've updated master, not sure how to make v1.x default (I don't use github much).  Thanks for the report!

In Settings -> Branches you can select the default branch.

In Settings -> Branches you can select the default branch.

Oh, I don't have permission on this repository, I guess @ekmett  would have to do that (set default branch of rounded to v1.x)...

Oh, I don't have permission on this repository, I guess @ekmett  would have to do that (set default branch of rounded to v1.x)...

Either way, also having master to track "latest vX.Y" branch would be fine for me (as a random contributor).

Either way, also having master to track "latest vX.Y" branch would be fine for me (as a random contributor).


Is there any possibility to convert JSON to XML in YAJL ver 2.1.0

Hi Team,
In our implementation we download data from http streaming.
As per YAJL documentation I read that, there is a way to convert JSON data to XML format. The below link describes this...
/***
*https://github.com/lloyd/yajl
*## YAJL supports stream parsing
*This means you do not need to hold the whole JSON representation in
*textual form in memory.  This makes YAJL ideal for filtering projects,
*where you're converting YAJL from one form to another (i.e. XML).  The
*included JSON pretty printer is an example of such a filter program.
*/
We used YAJL in our implementation to parse JSON data, by using yajl_tree_parse() API. But, this API is not converting our JSON data into XML format.
As per above documentation is there any way to get XML format from JSON data ?
If so, then which API will help me to get XML format from JSON data ?
Kindly provide your input on this...
Thanks,
Rambabu.

No, there is not any way to convert JSON to XML in YAJL as is.
I'm afraid you've been mislead by the choice of words there.  An XML converter would only be an example of a filtering project in which one could make good use of YAJL.  Such an example is, as they say in textbooks, left as an exercise to the reader.

Hi Robohack,
Thanks for your support. There was a big confusion on YAJL after reading YAJL documentation, weather it can convert JSON data to XML format or not.
Based on your input it is confirmed that YAJL can't convert JSON data to XML fomat.
Thanks,
Rambabu.


cat command not found, shell dont run

Hello!
There was an issue starting the shell. In perspective of the shell, the cat command was not found:
~/workbench/userlandproject
❯ brush
/usr/bin/cat: '': Datei oder Verzeichnis nicht gefunden
~/workbench/userlandproject
❯ ls /usr/bin/cat*
/usr/bin/cat  /usr/bin/catdoc  /usr/bin/catman  /usr/bin/catppt
~/workbench/userlandproject
❯

Is the shell now running? or is it the previous shell.
Thank!

Hi @commitcompanion -- thanks for your interest in brush! I see you filed an issue and then later closed it; were you able to resolve or otherwise sort out the error you were seeing?

Thank you for your patience. The issue seems to be that the command was indeed running, but this was not visible because it was using the same Starship prompt automatically. For some reason, it is searching for the cat command, even though cat is present and functional:
~
❯ brush #it starts brush!
/usr/bin/cat: '': No such file or directory
~
❯ cat
^C
~
❯ cat .bashrc
# .bashrc

# Source global definitions
if [ -f /etc/bashrc ]; then
    . /etc/bashrc
fi

# User specific environment
if ! [[ "$PATH" =~ "$HOME/.local/bin:$HOME/bin:" ]]; then
    PATH="$HOME/.local/bin:$HOME/bin:$PATH"
fi
export PATH

# Uncomment the following line if you don't like systemctl's auto-paging feature:
# export SYSTEMD_PAGER=

# User specific aliases and functions
if [ -d ~/.bashrc.d ]; then
    for rc in ~/.bashrc.d/*; do
        if [ -f "$rc" ]; then
            . "$rc"
        fi
    done
fi
unset rc
. "$HOME/.cargo/env"
eval "$(starship init bash)"
~
❯

so it was working!
Thanks!


use jest for testing

This adds Jest for testing AND generating coverage reports, keeps some of the testing setup the same, and mostly removes mocha, chokidar (jest has its own watcher), chai, and sinon (jest comes with its own mocking tools, and sinon was destroying the world in jest tests).
The warnings that come up when running this are the same as with the mocha tests.
For painless installation and testing, use "react-native-lock": "justinwoo/react-native-lock#feature-customized-theme", in package.json and run yarn && jest 😛 (fixed yarn bug but they still haven't released a new version) (but seriously, takes me 4 min to install this and 20s with yarn)

@justinwoo With yarn v0.16.1 the installation is finally painless without changing the react-native-lock in the package.json ;) I can update the yarn.lock file for it.

Happy to see this! Could Jest be used to test for component state mutation, to allow removal of Immutable in favor of POJOs?


fx import creates 13 inputs vs 1 for pytorch and onnx

for opt-125M, the issue is still there where for fximport it has 13 inputs vs pytorch and onnx having only one:
iree/runtime/src/iree/vm/invocation.c:95: INVALID_ARGUMENT; input list and function mismatch; expected 13 arguments but passed 1; invoking function 'main'; sync func @main(%input0: tensor, %input1: tensor, %input2: tensor, %input3: tensor, %input4: tensor, %input5: tensor, %input6: tensor, %input7: tensor, %input8: tensor, %input9: tensor, %input10: tensor, %input11: tensor, %input12: tensor<1x8xi64>) -> (%output0: tensor<1x8x50272xf32>, %output1: tensor<1x12x8x64xf32>, %output2: tensor<1x12x8x64xf32>, %output3: tensor<1x12x8x64xf32>, %output4: tensor<1x12x8x64xf32>, %output5: tensor<1x12x8x64xf32>, %output6: tensor<1x12x8x64xf32>, %output7: tensor<1x12x8x64xf32>, %output8: tensor<1x12x8x64xf32>, %output9: tensor<1x12x8x64xf32>, %output10: tensor<1x12x8x64xf32>, %output11: tensor<1x12x8x64xf32>, %output12: tensor<1x12x8x64xf32>, %output13: tensor<1x12x8x64xf32>, %output14: tensor<1x12x8x64xf32>, %output15: tensor<1x12x8x64xf32>, %output16: tensor<1x12x8x64xf32>, %output17: tensor<1x12x8x64xf32>, %output18: tensor<1x12x8x64xf32>, %output19: tensor<1x12x8x64xf32>, %output20: tensor<1x12x8x64xf32>, %output21: tensor<1x12x8x64xf32>, %output22: tensor<1x12x8x64xf32>, %output23: tensor<1x12x8x64xf32>, %output24: tensor<1x12x8x64xf32>)
STR:
git clone https://github.com/nod-ai/SHARK-TestSuite.git
cd e2eshark
Read README.md to setup
python run.py --torchmlirbuild /proj/gdba/kumar/nod/torch-mlir/build --ireebuild /proj/gdba/kumar/nod/mainireee/iree-build --hfhome /proj/gdba/kumar/HF_HOME  --mode direct -r test-direct-fp32 --tests pytorch/models/opt-125M
cd test-direct-fp32/pytorch/models/opt-125M
Examine inference.log

Most likely pytorch version related. There have been fixes to the upstream ExportedProgram API, that while good, have made it hard to ensure it is working on all nightlies. There was a range where it was just broken to.
See:
https://github.com/llvm/torch-mlir/commit/3e836d8dad551b6e5302de1b84840b90ee039c83
https://github.com/llvm/torch-mlir/commit/5253282c55546d19e00f8b244c2da74cf76c8486

Looks like kd was able to resolve this with local updates :). @stellaraccident I was wondering if we can switch to using your fx_import that deals with mutable semantics in e2e test suite. I've tested and it works fine with updated nightly, but I just wanted to check with you because it is marked as "experimental_support_mutation".

It just landed on Thursday, but it is works for you and you can use the bleeding edge nightlies, should be fine.

Oh, my bad, I needed to rebuild torch mlir wheel and install it. It works. Hooray!! Thank you!


Normalize branch name suffixes

In dotnet-helix-machines-ci builds like #20230610.01 failed w/ the following unhelpful error in ValidateHelix build steps:
2023-06-12 17:14:47Z pr-osx.1100.amd64-dougbu-unmonitor.win7.: Job has finished
##[error]/Users/runner/work/1/s/ValidateHelix.dll(,): error : No new agent logs for queue pr-osx.1100.amd64-dougbu-unmonitor.win7.
##[error]Bash exited with code '1'.

The problem (that @AlitzelMendez's intuition found quickly :smile:) was the branch name -- dougbu/unmonitor.win7.184 that led to an attempt to create Azure resources named e.g., pr-osx.1100.amd64-dougbu-unmonitor.win7.. Resources were actually created w/o the trailing period e.g., pr-osx.1100.amd64-dougbu-unmonitor.win7 but weren't discoverable when looking for them later.
Need to normalize the branch name suffixes we use beyond the current / to - transformation and truncation. While https://learn.microsoft.com/en-us/azure/azure-resource-manager/management/resource-name-rules seems slightly out of date, we at least know (observing what's in Azure at the moment) ASCII lowercase letters, digits, hyphens, and periods are allowed in resource names. Trailing hyphens seem to work though trailing periods don't. Either way, leading and trailing hyphens and periods in the suffix don't add much value.

Release Note Category

[ ] Feature changes/additions
[ ] Bug fixes
[x] Internal Infrastructure Improvements

Release Note Description
Added more stringent C# and PowerShell code to normalize resource names created in pull requests to ensure Azure supports them and the resource can be found later.
The new code might not cover everything e.g., if double hyphens are unsupported for some resource names. But it's sufficient to avoid most problems going forward.
The changes also add a bit more logging to ValidateHelix, more clearly delineating the chosen queue name and showing the blob storage is empty, not just lacking "new" logs.

Fixed in !31856 and verified.


Bug with automatic argument serialization for routes

Preface:
Automatic argument serialization for routes is not working as expected.
Bug description:
For the view below:
class DetailsView extends StatelessWidget {
  final String name;

  const DetailsView({this.name});

  Widget build(context) {
     // return some widget
  }
}

we get the following error when running the build_runner:
An error `FormatterException` occurred while formatting the generated source for
  `package:cam/app.dart`
which was output to
  `lib/app.router.dart`.
This may indicate an issue in the generator, the input source code, or in the
source formatter.
Could not format because the source could not be parsed:

line 56, column 13 of .: Methods must have an explicit list of parameters.
   ╷
56 │ final String* name;
   │             ^
   ╵
line 56, column 15 of .: A function body must be provided.
   ╷
56 │ final String* name;
   │               ^^^^
   ╵
line 56, column 15 of .: Variables must be declared using the keywords 'const', 'final', 'var' or a type name.
   ╷
56 │ final String* name;
   │               ^^^^
   ╵
line 56, column 13 of .: Operator declarations must be preceded by the keyword 'operator'.
   ╷
56 │ final String* name;
   │             ^
   ╵
line 56, column 7 of .: Expected to find ';'.
   ╷
56 │ final String* name;
   │       ^^^^^^
   ╵

I have added the view to the StackedApp annotation as such:
@StackedApp(
  routes: [
    MaterialRoute(page: DetailsView),
    // other routes
  ],
)

Version descriptions
build_runner: ^2.0.2
stacked_generator: ^0.4.1
stacked_services: ^0.8.5
Dart SDK version: 2.12.3 (stable)
Flutter (Channel stable, 2.0.6, on Linux, locale en_US.UTF-8)
Hacky solution
For now I am removing the type definition as such:
class DetailsView extends StatelessWidget {
  final name;    // <----- remove type
  const DetailsView({String name}) : this.name = name;

  Widget build(context) {
    // return some widget
  }
}

This generates argument with the type of name as dynamic as:
class DetailsViewArguments {
  final dynamic name;
  DetailsViewArguments({this.name});
}

Probably you can take a look into #291

Thanks mate! That fixed the issue.
I upgraded to a null safe version of the Dart SDK and its parsing the syntax correctly.


Install command issue

Describe the bug

The install command
sudo tar -C / -h -xzf linux-enable-ir-emitter-*.tar.gz

incorrectly set several system file owner to the current user including:
/
/etc
/usr
...

Basically all files and directories in the path  of those files in the zip file will be changed.
How to reproduce

Execute install command
sudo tar -C / -h -xzf linux-enable-ir-emitter-*.tar.gz

Additional info

Computer (or camera) model:
Version of linux-enable-ir-emitter:

When executing the command, the current user should be root, because of the sudo command.
I have not observed this bug myself

Thank you so much for pointing me this critical bug !
This can be avoided by using the option --no-same-owner : sudo tar -C / --no-same-owner -h -xzf linux-enable-ir-emitter-*.tar.gz
I've updated the readme. I didn't have this problem, because I go directly through meson, of course ... I should have thought about it.
Thank you again for your vigilance