[SDL-0188] Tests for OnHashChange

ATF Test Scripts to check #(FORDTCN-7217)[https://adc.luxoft.com/jira/browse/FORDTCN-7217]
This PR is [ready / not ready] for review.
Summary
Tests for OnHashChange notification during processing of subsription to interior vehicle data
ATF version
develop
CLA

[x] I have signed the CLA

All comments are processed in 9768b57


Update displayItems.sql

Complete the sql statement module design of the project
Pull Request Type
What kind of change does this PR introduce?
[1 ] Solved an issue/task
[ ] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] CI related changes
[ ] Documentation content changes
[ ] Other... Please describe:
What is the current behavior?

Issue Number: [Insert Issue Number (if applicable)]
What is the new behavior?

Other information

Merged

This is an automated message from Fork, Commit, Merge [BOT].

Thank you for your contribution! Your pull request has been merged. The files have been reset for the next contributor.
What's next?
If you're looking for more ways to contribute, I invite you to check out my other projects. Just click here to find more. These projects contain real issues that you can help resolve. You can also check out the Influences section in the README to find more projects similar to this one.
Also please leave a star to this project if you feel it helped you, i would really appreciate it.
I look forward to seeing your contributions!


Build overhaul2

This PR contains the changes from the first build overhaul #328 PR (already squashed) plus some changes I had queued up for some time now.

quicker build (using more ninja)
quicker download (avoiding full repo checkout of some dependencies)
added a few patches that silence some warnings and fix some compilation issues
central build/install directory
script parameters to use --cuda or --debug without having to edit the script

Please review @EricMier and/or @pdamme . I'll assign the PR numbers as issue numbers in the commit message when I merge it in. Issues and pull requests seem to have a common counter in github, so this should be fine. If I did miss anything in the commit message for #328 please mention it here @EricMier.
While testing this in a container I noticed that libtinfo.so (provided by ncurses) is now required. Maybe we should find out what pulled in this new dependency before we add it to the documentation (can't be the changes in this PR. Maybe the file readers?)

@pdamme, @EricMier, if there are no further comments to this, I'll merge it in later.

@corepointer I'll have a look at your changes today. Please wait before you merge it in.

@corepointer I'll have a look at your changes today. Please wait before you merge it in.

Awesome, thx :)

Hi @corepointer,
I also wanted to take a look at your changes. But when building after cloning, I get following "error: unable to find library -lpfm". Is this the new dependency you mentioned?

Hi @corepointer, I also wanted to take a look at your changes. But when building after cloning, I get following "error: unable to find library -lpfm". Is this the new dependency you mentioned?

Yes please do! :+1:  I don't know why you would get this library not found error. That's what I found out about it:
dpkg -l | grep -i pfm
ii  libpfm4:amd64                                 4.11.1+git32-gd0b85fb-1                     amd64        Library to program the performance monitoring events

apt-cache rdepends --installed libpfm4
libpfm4
Reverse Depends:
  llvm-10

So that library should be present on all systems that have the required dependencies for Daphne installed.

I addressed all but one issues with this PR:
fixed:

Removed using install target on llvm compile and added the necessary flags to the daphne cmake command again. There were indeed ~700 extra files compiled (50sec/5.5min more compile time on vega/laptop). We can come back to this once there's a standalone install-mlir cmake target upstream (the issue is known (see link in the other comment) but this has not been addressed so far)
I updated the documentation
I incorporated @pdamme 's suggestion about the clean/cleanAll behavior
updated .gitignore
fixed a few other minor things that came up while testing

still open:
The increase in run time for the test cases remains a mystery to me. Afaict it concerns the script based test cases. I tested a few things like omitting the patches, not compiling abseil separately and not using the llvm install target. I also ran on a few systems.
new:
Not an issue but another (convenience) feature: To quickly change build/cache/source/install prefixes to another directory, I introduced another intermediate variable. With all the creativity I could muster I called it myPrefix (but left a comment on what it does). If that bothers anybody I'm open for suggestions ;-)
Sorry for the force-pushing. I rebased to latest on main and already started to squash together some properly formatted commits. You can avoid conflicts in your local version of this branch by either removing it or if you're on that branch do git fetch and git reset --hard origin/build_overhaul2 (essentially separating fetch+merge that a normal pull would do and replacing the latter with a reset). This will remove local modifications so if you have any stash or move commits to a temp branch first.

Fixed the test time issue. Changing back from the cmake openblas build to make did it. For testers: make sure to run build.sh --cleanAll first.

I'd squash and merge tomorrow if everything's ok, also closing #120 and #241 along the way =)

Great! I can confirm that the test cases are back to normal execution time again. I will test a few scenarios (which always takes some time in the background) and report back in the course of the day.

Great that we finally got this merged in, it's a nice improvement. Thanks again @EricMier and @corepointer for pushing this forward!


Add tolerance for keys in mappings

Codecov Report
Patch coverage: 100.00% and no project coverage change.

Comparison is base (6d40744) 100.00% compared to head (dde74b0) 100.00%.

Additional details and impacted files
@@            Coverage Diff            @@
##              main      #191   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files           12        12
  Lines          890       891    +1
  Branches       187       187
=========================================
+ Hits           890       891    +1

Impacted Files
Coverage Δ

src/coola/allclose.py
100.00% <100.00%> (ø)

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Fix a link in getting-started.mdx

Description (required)

Update getting-started.mdx file in src/content/docs/en/ to correct the link to be consistent with the content.

The original content is linked to the Astro theme page, but suggest it would be better to be linked to the actual tutorial page in Astro docs.

[Build a Blog Tutorial]
(https://astro.build/themes/) --> (https://docs.astro.build/en/tutorial/0-introduction/)

Hello! Thank you for opening your first PR to Astro’s Docs! 🎉
Here’s what will happen next:

Our GitHub bots will run to check your changes.
If they spot any broken links you will see some error messages on this PR.
Don’t hesitate to ask any questions if you’re not sure what these mean!

In a few minutes, you’ll be able to see a preview of your changes on Netlify 🥳

One or more of our maintainers will take a look and may ask you to make changes.
We try to be responsive, but don’t worry if this takes a few days.


Getting Timeouts while trying to install or update

Steps to reproduce

Go to the bazaar admin page
Install or update an extension

Expected behaviour
The extension will be updated or installed.
Actual behaviour
I get a message saying that an error occured, when I click debug I get the source of a 524 timeout page by cloudflare
Configuration
Operating system: CloudLinux release 7.4
Version of Bazaar: 0.2.4
Version of Flarum: 0.1.0-beta.7
Other extensions: ["flarum-approval","flarum-bbcode","flarum-emoji","flarum-english","flarum-flags","flarum-likes","flarum-lock","flarum-mentions","flarum-sticky","flarum-subscriptions","flarum-suspend","flarum-tags","flarum-auth-twitter","flarum-auth-facebook","flagrow-bazaar","flagrow-masquerade","wiwatsrt-best-answer","clarkwinkelmann-emojionearea","xengine-signature","sijad-pages","s9e-mediaembed","sijad-spoiler-alert","flagrow-ads","flagrow-upload","flarum-auth-github","sijad-recaptcha","reflar-user-management","sijad-links","flagrow-guardian","flagrow-linguist","flagrow-users-list","datitisev-dashboard","antoinefr-online","reflar-reactions","reflar-gamification","flarum-akismet","sijad-auth-steam","johnhearfield-oauth-google","flarum-markdown","pnobbe-oauth-discord","flagrow-analytics","flagrow-byobu","flagrow-mason","reflar-polls","antoinefr-money","michaelbelgium-discussion-views","sijad-github-autolink","flagrow-impersonate","reflar-twofactor","wiseclock-profile-image-crop","oe800-gravatar","flagrow-auth-twitch","flagrow-latex","flagrow-terms","sledov-quill"]

**Logs**: For some reason all the logs are dated on 2017
Insert logs here (if necessary)

Extension installation is a very long running process. For Flarum beta 8 we're moving this to the background, even though the process might still be equally slow, you won't see the immediate drawback of that anymore.


consider removing the chunk enum wrappers

We're not actually using them for parsing the chunks, both to have more control and for efficiently choosing the right chunk parser. So... Should probably just remove them for consistency. Also, this would allow removing the unknown chunk cases from all of those parsers.
... if so... replace with a function that parses one chunk from a stream?

Ended up going to the opposite direction. Removed custom nested chunk parsing logic, letting the binrw enum variant testing handle it.


[Query] Worker callbacks option

I was going through the worker code and the options take a parameter as callback. Looking at the process code, it tries to find the callback for a particular job.data.name. @scttnlsn if you can help explain the use-case of this functionality?

The worker callbacks are keyed by name and should correspond to the values in job.data.name.  The callbacks perform the actual computation/work and by naming the callbacks, a single worker can perform various tasks based on the name of the enqueued job.  Does that answer your question?

Still trying to figure out. Can you share an example?

Example from the README:
A job named reverse is enqueued.  This sets job.data.name to the string "reverse" in the job document.  A worker function is then registered corresponding to the name:
worker.register({
  reverse: function (params, callback) {
  }
});

You could register as many functions as you need though:
worker.register({
  reverse: ...,
  capitalize: ...,
  lowercase: ...,
  // etc.
});

And enqueue jobs to be processed by those functions respectively:
queue.enqueue('reverse', { text: 'foobar' });
queue.enqueue('capitalize', { text: 'foobar' });
queue.enqueue('lowercase', { text: 'FOOBAR' });

This is brilliant. Thanks.


Compass installation does not work

I tried to install the latest Susy through the latest Compass, using the command from the docs compass create --using susy <project name>, but I got the error No such framework: "susy". Prior to running that command, I had installed each through gem. Am I doing this wrong, or does this method no longer work?
My goal is to package up Susy as a Webjar, so it can easily be used with the Play framework.

Is this issue still relevant?


Add EntryWidget UI

What was solved?
This PR adds EntryWidget bottom sheet. In addition it adds the necessary support files to be able to develop EntryWidget with SwiftUI.
Because this PR is a foundation for the rest of the tickets, some of the elements, such as channel enum will be altered later on
MOB-3477
Release notes:

[ ] Feature
[X] Ignore
[ ] Release notes (Is it clear from the description here?)
[ ] Migration guide (If changes are needed for integrator already using the SDK - what needs to be communicated? Add underneath please)

Additional info:

[ ] Is the feature sufficiently tested? All tests fixed? Necessary unit, acceptance, snapshots added? Check that at least new public classes & methods are covered with unit tests
[ ] Did you add logging beneficial for troubleshooting of customer issues?
[ ] Did you add new logging? We would like the logging between platforms to be similar. Refer to Logging from iOS SDKs → Things to consider for newly added logs in Confluence for more information.

Screenshots:

Thanks for inviting me to the party!
Looking forward to the business logic.
On Tue, 24 Sep 2024 at 22:51, Rasmus Tauts @.***> wrote:

@.**** commented on this pull request.
In GliaWidgets/Sources/EntryWidget/EntryWidgetViewModel.swift
https://github.com/salemove/ios-sdk-widgets/pull/1050#discussion_r1773284483
:

@@ -0,0 +1,26 @@
+import SwiftUI

+extension EntryWidgetView {

class Model: ObservableObject {

As of yet, there no published properties in the class. This is due to the
business logic being in development still. There most likely will be some,
and that's why @observableobject https://github.com/observableobject
was added proactively.
—
Reply to this email directly, view it on GitHub
https://github.com/salemove/ios-sdk-widgets/pull/1050#discussion_r1773284483,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AOJBPYESFCZVFTNMAI2TTKLZYFN3NAVCNFSM6AAAAABOWTCL56VHI2DSMVQWIX3LMV43YUDVNRWFEZLROVSXG5CSMV3GSZLXHMZDGMRVGE2TONBQGM
.
You are receiving this because you were mentioned.Message ID:
@.***>

!squash


Large difference under same condition

Rally version (get with esrally --version): 0.3.0
Invoked command: esrally --pipeline=from-distribution --distribution-version=2.3.4
Configuration file (located in ~/.rally/rally.ini)):
[meta]
config.version = 5

[system]
root.dir = /home/test/.rally/benchmarks
log.root.dir = logs
env.name = local

[provisioning]
local.install.dir = install

[runtime]
java8.home = /usr/lib/jvm/java-8-oracle

[benchmarks]
local.dataset.cache = ${system:root.dir}/data

[reporting]
datastore.type = in-memory
datastore.host =
datastore.port =
datastore.secure =
datastore.user =
datastore.password =

[tracks]
default.url = https://github.com/elastic/rally-tracks

JVM version: 1.8.0_91
OS version: Ubuntu 14.04.1
Description of the problem including expected versus actual behavior:
Running the same condition (8 cores 8G) twice will have large difference:
Round 1:
|                          Min Indexing Throughput [docs/s] |     5526 |
|                       Median Indexing Throughput [docs/s] |     7235 |
|                          Max Indexing Throughput [docs/s] |     7643 |
|                                       Indexing time [min] |  148.684 |
|                                          Merge time [min] |  75.6346 |
|                                        Refresh time [min] |  27.9057 |
|                                          Flush time [min] | 0.333217 |
|                                 Merge throttle time [min] | 0.802633 |
|               Query latency scroll (90.0 percentile) [ms] |  48.2463 |
|               Query latency scroll (99.0 percentile) [ms] |  76.2355 |
|               Query latency scroll (99.9 percentile) [ms] |  90.8294 |
|                Query latency scroll (100 percentile) [ms] |  102.809 |
|                 Query latency term (90.0 percentile) [ms] |  4.16823 |
|                 Query latency term (99.0 percentile) [ms] |  12.4928 |
|                 Query latency term (99.9 percentile) [ms] |  100.319 |
|                  Query latency term (100 percentile) [ms] |  246.462 |
| Query latency country_agg_uncached (90.0 percentile) [ms] |  317.431 |
| Query latency country_agg_uncached (99.0 percentile) [ms] |     1022 |
| Query latency country_agg_uncached (99.9 percentile) [ms] |  1346.53 |
|  Query latency country_agg_uncached (100 percentile) [ms] |  1431.36 |
|              Query latency default (90.0 percentile) [ms] |   71.604 |
|              Query latency default (99.0 percentile) [ms] |  316.913 |
|              Query latency default (99.9 percentile) [ms] |   542.47 |
|               Query latency default (100 percentile) [ms] |  560.789 |
|   Query latency country_agg_cached (90.0 percentile) [ms] |  4.07046 |
|   Query latency country_agg_cached (99.0 percentile) [ms] |  20.8715 |
|   Query latency country_agg_cached (99.9 percentile) [ms] |  82.3027 |
|    Query latency country_agg_cached (100 percentile) [ms] |  202.176 |
|           Query latency expression (90.0 percentile) [ms] |  795.495 |
|           Query latency expression (99.0 percentile) [ms] |  2147.52 |
|           Query latency expression (99.9 percentile) [ms] |  2898.23 |
|            Query latency expression (100 percentile) [ms] |  3233.19 |
|               Query latency phrase (90.0 percentile) [ms] |  5.23883 |
|               Query latency phrase (99.0 percentile) [ms] |  13.1562 |
|               Query latency phrase (99.9 percentile) [ms] |  149.506 |
|                Query latency phrase (100 percentile) [ms] |  225.095 |
|                              Median CPU usage (index) [%] |    655.2 |
|                              Median CPU usage (stats) [%] |   182.75 |
|                             Median CPU usage (search) [%] |    307.6 |
|                                    Total Young Gen GC [s] |  185.841 |
|                                      Total Old Gen GC [s] |   28.299 |
|                                           Index size [GB] |  3.37851 |
|                                      Totally written [GB] |   25.945 |
|                                             Segment count |      120 |
|                       Indices Stats(90.0 percentile) [ms] |  8.87139 |
|                       Indices Stats(99.0 percentile) [ms] |  12.2518 |
|                        Indices Stats(100 percentile) [ms] |  22.0964 |
|                         Nodes Stats(90.0 percentile) [ms] |  8.63969 |
|                         Nodes Stats(99.0 percentile) [ms] |  11.6811 |
|                          Nodes Stats(100 percentile) [ms] |   21.003 |

Round 2:
|----------------------------------------------------------:|---------:|
|                          Min Indexing Throughput [docs/s] |     7841 |
|                       Median Indexing Throughput [docs/s] |     8181 |
|                          Max Indexing Throughput [docs/s] |    10072 |
|                                       Indexing time [min] |  133.989 |
|                                          Merge time [min] |  65.6205 |
|                                        Refresh time [min] |  24.2788 |
|                                          Flush time [min] | 0.321633 |
|                                 Merge throttle time [min] |  0.87815 |
|              Query latency default (90.0 percentile) [ms] |  64.8217 |
|              Query latency default (99.0 percentile) [ms] |  216.476 |
|              Query latency default (99.9 percentile) [ms] |  473.204 |
|               Query latency default (100 percentile) [ms] |  521.881 |
|               Query latency scroll (90.0 percentile) [ms] |  50.4148 |
|               Query latency scroll (99.0 percentile) [ms] |  81.3037 |
|               Query latency scroll (99.9 percentile) [ms] |  102.284 |
|                Query latency scroll (100 percentile) [ms] |  111.201 |
|                 Query latency term (90.0 percentile) [ms] |  4.23551 |
|                 Query latency term (99.0 percentile) [ms] |  11.2422 |
|                 Query latency term (99.9 percentile) [ms] |  45.1594 |
|                  Query latency term (100 percentile) [ms] |  53.4755 |
| Query latency country_agg_uncached (90.0 percentile) [ms] |  270.294 |
| Query latency country_agg_uncached (99.0 percentile) [ms] |  915.455 |
| Query latency country_agg_uncached (99.9 percentile) [ms] |  1142.32 |
|  Query latency country_agg_uncached (100 percentile) [ms] |  1158.38 |
|   Query latency country_agg_cached (90.0 percentile) [ms] |  4.04353 |
|   Query latency country_agg_cached (99.0 percentile) [ms] |  13.2687 |
|   Query latency country_agg_cached (99.9 percentile) [ms] |    111.7 |
|    Query latency country_agg_cached (100 percentile) [ms] |  154.767 |
|           Query latency expression (90.0 percentile) [ms] |  718.149 |
|           Query latency expression (99.0 percentile) [ms] |  1965.82 |
|           Query latency expression (99.9 percentile) [ms] |  2518.28 |
|            Query latency expression (100 percentile) [ms] |  2607.16 |
|               Query latency phrase (90.0 percentile) [ms] |  5.16473 |
|               Query latency phrase (99.0 percentile) [ms] |  18.2519 |
|               Query latency phrase (99.9 percentile) [ms] |  78.8928 |
|                Query latency phrase (100 percentile) [ms] |   319.28 |
|                              Median CPU usage (index) [%] |    665.8 |
|                              Median CPU usage (stats) [%] |    410.5 |
|                             Median CPU usage (search) [%] |    298.6 |
|                                    Total Young Gen GC [s] |  163.584 |
|                                      Total Old Gen GC [s] |   24.907 |
|                                           Index size [GB] |  3.37467 |
|                                      Totally written [GB] |  25.2063 |
|                                             Segment count |      125 |
|                       Indices Stats(90.0 percentile) [ms] |  11.7891 |
|                       Indices Stats(99.0 percentile) [ms] |  26.5643 |
|                        Indices Stats(100 percentile) [ms] |  30.5178 |
|                         Nodes Stats(90.0 percentile) [ms] |  11.6267 |
|                         Nodes Stats(99.0 percentile) [ms] |  24.0409 |
|                          Nodes Stats(100 percentile) [ms] |  26.1791 |

What will affect this ? Shall I run multiple times to calculate a mean value?
Another question: Where can I find every key's meaning ?
Thanks

What will affect this ?

This can have a lot of reasons. First of all, some run-to-run variance is expected. Variance can come from OS noise or (more likely) from JVM activity, e.g. it is not deterministic when the GC will run. Obviously, this will have an influence on tail latencies (like the 99th+ percentile). It's hard to tell so you need to dig deeper and look at system metrics with OS tools or attach additional telemetry devices.
In your case the run-to-run variance is really high compared to our nightly benchmarks (just look at the 99th request latency in our benchmarks, they're pretty stable). It could be that your system is swapping, that you run this benchmark on a notebook and use the powersave CPU governor, etc. etc.

Shall I run multiple times to calculate a mean value?

Yes and no.
I'd first check why the run-to-run variance is so high in your case. We run just one round per trial run in our nightly benchmarks (first, the environment is already exhibits low run-to-run variance, second, the benchmarks run well above 12 hours ;)) but for benchmarks that don't run every day you should run it multiple times (at least to get a feeling for the run-to-run variance) and then use a t-test to determine whether a change can be considered significant.
However, a few caveats apply: You have to be careful when you summarize values. For example, you cannot average percentiles. I have also good news: In your case, I'd use the advanced configuration of Rally and set up a dedicated Elasticsearch instance as metrics store. Then, Rally will push all raw metrics records there and you can calculate summary statistics based on the raw samples.

Where can I find every key's meaning ?

It's an open ticket: See #85
If you have more questions, I'd ask you to ask a question in the Elasticsearch Discuss forum in the future instead of raising a Github issue. I actively watch this forum.

@danielmitterdorfer I'll look into the references, thank you very much.
I'll create posts on the forum. Sorry for the trouble.

Sorry for the trouble.

Really, no worries. This was just a pointer. :)


Guidance on how to fix the scheduler and ConstantLengthDataset

Hello,
I want to fix the issue related to the ConstantLengthDataset not knowing the dataset's length in advance.
Besides having a broken progressbar and a wrong epoch count, the only problem I see is related to the scheduler, as most of us are training using cosine with warmup; if we want a complete cycle, the scheduler needs the total number of steps to adjust the ratios accordingly.
One solution would be to "guess" how many batches/iteration of packed data we will see by grabbing some samples and estimating the total length. A function tries to do something like this by computing a char/tok ratio.
Do you have any advice so I can draft a PR?
Ohh I just saw that @lvwerra has a PR in the works, but only for "finite" dataset.

Yes, I think if you don't precompute there is no way to really know unfortunately. If feel an approximation will also not be a great user experience as it can still be off.

I think so, anyway, then direction on doing stuff like:
TOTAL_PACKED_SAMPLES = 10_000
batch_size = 16
gradient_accumulation_steps = 2
num_train_epochs = 3
total_num_steps = num_train_epochs * TOTAL_PACKED_SAMPLES // (batch_size * gradient_accumulation_steps)
config.eval_steps = total_num_steps // num_train_epochs

I perform this before instantiating the Trainer these days...

Per my understanding the issue should be fixed by this PR: https://github.com/huggingface/trl/pull/1027

do you think that API change being merged?

Should be fixed by https://github.com/huggingface/trl/pull/979
Can you try to install TRL from source?


Adds JSON-event support for fdk-java

Adds a new codec package to keep all the codec stuff in the same place.
Not all the fields in the JSON event are available on the InputEvent object. Those extra fields are ignored.

Build failure, otherwise LGTM.


Add model distillation methods

Review the methods here: https://github.com/UKPLab/sentence-transformers/tree/master/examples/training/distillation
See if this can be integrated to reduce the storage necessary for embeddings indices.

Upon further review a generic way to do this wouldn't be that clean. Additionally, distillation methods are available at the index level (i.e. in Faiss). Closing this issue.


XCTAssertThrows fails when linked with SOLD

This started happening after your recent fix for #17
We have an ImageLoadingDependency provider like this:
@implementation UberImageLoadingDependencyProvider

- (void)setImageLoader:(id<UBImageLoading>)imageLoader
{
    NSParameterAssert(imageLoader != nil);
    NSAssert(_imageLoader == nil, @"it should only be set once!!!!!");

    _imageLoader = imageLoader;
}

and test:
- (void)testAssertWhenSetTwice
{
    UberImageLoadingDependencyProvider *theProvider = [[UberImageLoadingDependencyProvider alloc] init];

    NSObject *imageLoader = [[NSObject alloc] init];
    XCTAssertNoThrow([theProvider setImageLoader:(id)imageLoader]);
    XCTAssertThrows([theProvider setImageLoader:(id)imageLoader]);
}

We get a crash while unwinding:
Thread 0 Crashed::  Dispatch queue: com.apple.main-thread
0   libsystem_kernel.dylib        	    0x7ff834be600e __pthread_kill + 10
1   libsystem_pthread.dylib       	    0x7ff834c3d1ff pthread_kill + 263
2   libsystem_c.dylib             	    0x7ff800132fe0 abort + 130
3   libc++abi.dylib               	    0x7ff800259f72 __cxxabiv1::readEncodedPointer(unsigned char const**, unsigned char, unsigned long) + 269
4   libc++abi.dylib               	    0x7ff800259675 __gxx_personality_v0 + 389
5   libunwind.dylib               	    0x7ff8252fdcbd _Unwind_RaiseException + 233
6   libc++abi.dylib               	    0x7ff80025917d __cxa_throw + 108
7   libobjc.A.dylib               	    0x7ff80004dca6 objc_exception_throw + 307
8   Foundation                    	    0x7ff800b8637c -[NSAssertionHandler handleFailureInMethod:object:file:lineNumber:description:] + 281
9   Tests   	                            0x12a262385 -[UberImageLoadingDependencyProvider setImageLoader:] + 357
10  Tests   	                            0x12a25e323 -[UberImageLoadingDependencyProviderTests testAssertWhenSetTwice] + 131

Reproducer: https://github.com/tapthaker/mold-repro-invalid-parameter

The issue occurs on Intel can you use an intel macOS box to reproduce it? I am sorry; I should have mentioned this.

I ran it on an Intel Mac. The first test case that is supposed to pass got killed with signal 9 and failed. Do you have any idea?
ruiu:/tmp/mold-repro-invalid-parameter$ bash -x test.sh
+ SIM_ID=4CF1DB47-CBAF-4549-8231-67D3251AE2E0
+ RED='\033[0;31m'
+ GREEN='\033[0;32m'
+ NC='\033[0m'
+ printf '\033[0;32m============= LD64 EXPECTED TO PASS ==============\033[0m\n'
============= LD64 EXPECTED TO PASS ==============
++ pwd
+ xcrun ld @response.txt -rpath /tmp/mold-repro-invalid-parameter
+ codesign ImageLoadingLegacyObjcTests.xctest
+ /usr/bin/codesign --force --sign - --timestamp=none --generate-entitlement-der ImageLoadingLegacyObjcTests.xctest
+ run_tests ImageLoadingLegacyObjcTests.xctest tests_default.log
++ pwd
+ WORK_DIR=/tmp/mold-repro-invalid-parameter
+ cmd=(./ios_test_runner.par --test_bundle_path $1 --output_dir "$WORK_DIR" --work_dir "$WORK_DIR" test --id $SIM_ID --platform ios_simulator)
+ echo ./ios_test_runner.par --test_bundle_path ImageLoadingLegacyObjcTests.xctest --output_dir /tmp/mold-repro-invalid-parameter --work_dir /tmp/mold-repro-invalid-parameter test --id 4CF1DB47-CBAF-4549-8231-67D3251AE2E0 --platform ios_simulator
./ios_test_runner.par --test_bundle_path ImageLoadingLegacyObjcTests.xctest --output_dir /tmp/mold-repro-invalid-parameter --work_dir /tmp/mold-repro-invalid-parameter test --id 4CF1DB47-CBAF-4549-8231-67D3251AE2E0 --platform ios_simulator
+ echo 'replace ./ios_test_runner.par with ./ios_test_runner.debug.par if you want to debug this'
replace ./ios_test_runner.par with ./ios_test_runner.debug.par if you want to debug this
+ ./ios_test_runner.par --test_bundle_path ImageLoadingLegacyObjcTests.xctest --output_dir /tmp/mold-repro-invalid-parameter --work_dir /tmp/mold-repro-invalid-parameter test --id 4CF1DB47-CBAF-4549-8231-67D3251AE2E0 --platform ios_simulator
Child process terminated with signal 9: Killed
+ check_if_tests_failed
+ exit_code=11
+ '[' 11 -ne 0 ']'
+ printf '\033[0;31m============= FAILED ==============\033[0m\n'
============= FAILED ==============

Ah, that is probably the macOS Security.  Could you execute the following to remove the quarantine attribute and try again?
xattr -d -r com.apple.quarantine /tmp/mold-repro-invalid-parameter

I ran that command and ran the test again. Unfortunately it failed with the exact same error.

Could you check if the downloaded tar has the quarantine attr set ?
xattr ~/Downloads/mold-repro-invalid-parameter.tar.xz
com.apple.macl
com.apple.metadata:kMDItemDownloadedDate
com.apple.metadata:kMDItemWhereFroms
com.apple.quarantine

If so remove it with:
xattr -d com.apple.quarantine ~/Downloads/mold-repro-invalid-parameter.tar.xz

I can reproduce your problem over here, and removing the quarantine bit for the archive fixes the problem:

Hmm, I removed the quarantine bit from the archive, untar it and re-run the same command, but it still failed with the same error (signal 9).
$ xattr ~/Downloads/mold-repro-invalid-parameter.tar.xz
com.apple.metadata:kMDItemWhereFroms

If you run into issues with iPhone XR assertion, you can use the following command to create an iPhone XR Simulator:
SIM_ID=$(xcrun simctl create UberSim com.apple.CoreSimulator.SimDeviceType.iPhone-XR com.apple.CoreSimulator.SimRuntime.iOS-16-1)
xcrun simctl boot $SIM_ID
echo "Modify the SIM_ID in test.sh  to value: $SIM_ID"

Alternatively, you can modify the file ImageLoadingLegacyObjcTests.xctest/.simulatorversion to your simulator type for the tests to pass.
Apologies for the trouble; I'll send you a repro that removes this assertion if this doesn't work out.

Uploaded https://github.com/tapthaker/mold-repro-invalid-parameter/blob/main/mold-repro-invalid-parameter_v2.tar.xz that doesn't have the XR Simulator Assertion

I've been trying to fix this issue with no luck for a few days so far. Do you mind if I ask you to try to reduce the test case a little further so that it is easy to debug? Currently it contains lots of code and data.

I am also seeing unwind failures on ARM64. Is that helps:
Thread 0 Crashed::  Dispatch queue: com.apple.main-thread
0   libsystem_kernel.dylib        	       0x1af205fa8 __pthread_kill + 8
1   libsystem_pthread.dylib       	       0x1af25a12c pthread_kill + 256
2   libsystem_c.dylib             	       0x180129e28 abort + 124
3   libc++abi.dylib               	       0x18023ea80 __cxxabiv1::readEncodedPointer(unsigned char const**, unsigned char, unsigned long) + 308
4   libc++abi.dylib               	       0x18023e29c __gxx_personality_v0 + 336
5   libunwind.dylib               	       0x1a1350644 _Unwind_RaiseException + 472
6   libc++abi.dylib               	       0x18023dd00 __cxa_throw + 124
7   libobjc.A.dylib               	       0x180051274 objc_exception_throw + 360
8   CoreFoundation                	       0x18040e690 +[NSException raise:format:arguments:] + 92

I'm still working on it. sold didn't support parsing and reconstructing __eh_frame sections, which is I believe needed to fix this issue. So I implemented it. The test is still failing because the exception handler reads a wrong value as a location of Language-Specific Data Area. I believe it needs a few more days to fix it.

It was caused by a subtle error in a __compact_unwind section. Please rebuild sold and try again.


How to handle if image load fails?

I am trying to use LQIP/blurry image placeholder/Blur up image technique. It works well with code below if image load success. However, if image load fails, it firstly shows placeholder and shrinked empty space.
Is there good way to provide fallback image src if data-src path fails ?
 <img
     data-sizes="auto"
     src="placeholder.jpg"
     data-src={src}
     className="lazyload blur-up"
/>

When does this happen? Do you provide a src with 404 network error? If this is the case you should simply fix your 404 errors.

Yes it does return 404 but I want to replace those src to placeholder image on error. and hoped that lazysize handles it.

This is not a task for a lazyloader.
Maybe the following code examples show how you can do this your own.
<img
     data-sizes="auto"
     src="placeholder.jpg"
     data-src={src}
    onerror="this.src='placeholder.jpg'"
     className="lazyload blur-up"
/>

or
document.addEventListener('error', function(e){
    if(e.target.nodeName == 'IMG'){e.target.src = 'placeholder.jpg';}
}, true);

With CSS
img.lazyloaded[data-src=""] {
    display: none;
}

This is not a task for a lazyloader.
Maybe the following code examples show how you can do this your own.
<img
     data-sizes="auto"
     src="placeholder.jpg"
     data-src={src}
     onerror="this.src='placeholder.jpg'"
     className="lazyload blur-up"
/>

or
document.addEventListener('error', function(e){
    if(e.target.nodeName == 'IMG'){e.target.src = 'placeholder.jpg';}
}, true);

thanks u! It's work for me


UPC_Connect: Receive http code 302

Make sure you are running the latest version of Home Assistant before reporting an issue.
You should only file an issue if you found a bug. Feature and enhancement requests should go in the Feature Requests section of our community forum:
Home Assistant release (hass --version):
(homeassistant) homeassistant@hassbian:~ $ hass --version
0.47.1
Python release (python3 --version):
Python 3.4.2
Component/platform:
upc_connect
Description of problem:
I have most of the time following error in log:
2017-06-22 17:08:48 WARNING (MainThread) [homeassistant.components.device_tracker.upc_connect] Receive http code 302
2017-06-22 17:08:48 WARNING (MainThread) [homeassistant.components.device_tracker.upc_connect] Can't read device from <IP_ADDRESS>
Expected:
It should download or survive 302 :)
Problem-relevant configuration.yaml entries and steps to reproduce:
device_tracker:
  - platform: upc_connect
    password: ....
    track_new_devices: false
    interval_seconds: 120

Put it to configuration
Keep it running for a while

Traceback (if applicable):

Additional info:

You Need restart you homeassistant to fix that. Some time on start it can not connect to box and trow this error. Wait a bit and restart your device. That is a bug but I found no sultion for it.

Yep, I did it many times.. it's working some time, but lot of the time it stop working.. any idea how to debug it?

I have the same problem. If it's any use, there are also many "Timer got out of sync" errors when this component is enabled. They disappear when I disable the component device_tracker.
This happens to me on a fresh install of Hassbian where the discovery component has only found my Ikea Tradfri lights and my Chromecast. No other components or automations have been configured yet, apart from the default ones.
2017-07-01 11:42:49 ERROR (MainThread) [homeassistant.core] Timer got out of sync. Resetting
2017-07-01 11:42:49 WARNING (MainThread) [homeassistant.components.device_tracker.upc_connect] Receive http code 302
2017-07-01 11:42:49 WARNING (MainThread) [homeassistant.components.device_tracker.upc_connect] Can't read device from <IP_ADDRESS>
2017-07-01 11:42:57 ERROR (MainThread) [homeassistant.core] Timer got out of sync. Resetting
2017-07-01 11:43:02 ERROR (MainThread) [homeassistant.core] Timer got out of sync. Resetting
2017-07-01 11:43:02 WARNING (MainThread) [homeassistant.components.device_tracker.upc_connect] Receive http code 302
2017-07-01 11:43:02 WARNING (MainThread) [homeassistant.components.device_tracker.upc_connect] Can't read device from <IP_ADDRESS>
2017-07-01 11:43:10 ERROR (MainThread) [homeassistant.core] Timer got out of sync. Resetting

This is my configuration for the device tracker:
device_tracker:
  - platform: upc_connect
    password: xxxxxxxx

Is this any help for solving this bug?

I think I have found the cause of this problem: the sessionToken is specific to the User-Agent header being used. Because the initial call to /common_page/login.html uses a different user agent than the calls to getter.xml, the calls to getter.xml have an invalid token and fail (redirect to the home page).
Also, I've noticed it's not necessary to log in to query the list of devices.
I'm working on a PR to fix the user agent issue, and remove the call to the login and logout functions, so that you no longer need to give your router password to Home Assistant when using this component.

Cool thanks. The out of sync problem is a python34 and aiohttp/asyncio issue. Update to python3.6 (like with docker or hassio) and you system run 30% faster.

Actually, that wasn't the problem. But I found the real root cause. I will submit the PR in a few minutes.


Can't we expect a official validation and multi language  support in slim 3.0

I'm actually using  GUMP in my project for validation and using twig for multi support too in fronted.
I think slim 3.0 should have it or similar something. and if multilingual system could be added that would be great.
Now I'm using:
1.redbenphp as ORM
2.Slim (handling request
3.Twig (as a view)
** Love your Slim.
pseudo code in route:
// Display Confirm
$app->post('/confirm', function () use ($app) {
            $form_post_value           = $app->request()->post();
            $reseller                  = new reseller;
            $reseller->form_post_value = $form_post_value;
            $reseller->save();

            if ($reseller->fails()) {
                $app->view->setData('error', "1");
                $app->view->setData('msg', $reseller->getError());
                $app->render(new u('msg'));
            }
            else {
                $app->view->setData('success', "1");
                $app->view->setData('msg', "Succesfully User Created");
                $app->render(new u('msg'));
            }
        });

pseudo code:
public function save() {
    $gump = new GUMP();

    $rules = array(
        'reseller_username' => 'required|alpha_numeric|max_len,10|min_len,6',
        'reseller_password' => 'required|max_len,10|min_len,3'
    );

    $filters = array(
        'reseller_username' => 'trim|sanitize_string',
        'reseller_password' => 'trim|sanitize_string'

    );

    $postValues  = $gump->filter($this->form_post_value, $filters);
    $validated   = $gump->validate($gump->filter($postValues, $filters), $rules);

    if ($validated === TRUE) {

        if($this->isDublicateUser($filters['reseller_username'])){
            $this->setError('Duplicate user name,Please choose another');
        }
        elseif($this->isNotStrongPassword($filters['reseller_password'])){
         $this->setError('Please choose strong password');
        }
        else{

        $createUser              = R::dispense('user');
        $createUser->user        = $postValues['reseller_username'];
        $createUser->pass        = md5($postValues['reseller_password']);
        $createUser->created_by  = $this->getSessionValue('usid');

        R::store($createUser);
    }

    } else {
         $error=$gump->get_readable_errors(false);
        $this->setError($error[0]);

    }

    if ($this->getError() == "") {$this->fails = FALSE;} else {$this->fails = TRUE;}

}

public function fails() {
return $this->fails;
}

Thanks for your feedback, but I don't think there will ever be an official validation library in Slim itself. We are geared towards making things very modular and don't want to impose any sort of restrictions on the user as to what validation library they work with or how they handle multiple languages in their project.
All of us on the Slim team uses it professionally in our day to day work and we all use different validation libraries and have our projects setup differently, this is what we and most users like the most about Slim.

This will not be in the core. it is a good candidate for third-party components or middleware.


Only apply styles when necessary

Currently on each adjust() call a style object is created based on the queries and container units, then it's applied.
This could be cached, however, so that the same styles are not applied if nothing changed since the last adjust() call.
When there's no container units used for a container, the benefits would be even greater, since then it's even more unlikely that a new style object is needed on every adjust() call.

Done in 2.0.0


(FR) API: Get Item Max Peak and Average RMS Level

Hi,
SWS is capable of analyzing items and determine what is it's Max Peak level, and what is it's Average RMS level. This function is use in the SWS label processor and in the Organize Items by Peak/RMS actions.
It could be nice if we could get this value from ReaScript, with two functions like this:
max_peak = GetMediaItemMaxPeak( item )
average_rms = GetMediaItemAverageRMS( item )
Currently, we can only access this value by using the SWS label processor, and renaming all the items with the level we want. No very flexible.
Thanks for listening !

I'm assigning to this request.
No promises, but I have it basically working already. Will sprobably send a pull request for review to Tim soon.

Added in v2.9.3 thanks to @nofishonfriday  !


Medalla Initial sync: Failed to obtain chunk

Describe the bug
Failure to obtain a chunk results in stalled sync.
But receiving a chunk after that failed chunk causes sync to attempt to progress.
Meanwhile the chain head has never moved past the failed chunk, and the block pool just fills up.
Expected behavior
When failure to obtain a chunk happens, the chunk is re-requested from other peers.
Receiving a chunk after a failed chunk does not cause the sync to progress.
2020-08-04 11:19:53  [SYNC]             info: Fetching blocks for 1...64 slot range

...

2020-08-04 11:20:01  [SYNC]             warn: Failed to obtain chunk {"start":1,"end":12} from peer 16Uiu2HAmBvY9JBraEAQ2dt8XQVJiCmiXrPvD6dK1cuXaJHQkqTw7

...

2020-08-04 11:20:13  [SYNC]             warn: Failed to obtain chunk {"start":1,"end":12} from peer 16Uiu2HAmNgwpRUCL9Q7BmScxeWCAFnxeTGY6N4x21fEofGNtYetH
2020-08-04 11:20:14  [SYNC]             info: Imported blocks for slots: 14,15,16,17,19,22,23,37,49,52,53,55,56,57,58,59,60,61,62,63
2020-08-04 11:20:14  [SYNC]             warn: Received block parent root doesn't match our head head=0xebe49843e96e538592c9e1976e155e9057c251ed9312eba517afce3ca1a0660c, headSlot=0, blockParent=0x8f181722abe3a0383815ec5b71acef8e93
b3002508e5d298686719f3c461371a, blockSlot=14
2020-08-04 11:20:14  [SYNC]             warn: Didn't receive any valid block in given range
2020-08-04 11:20:14  [SYNC]             info: Fetching blocks for 65...128 slot range

I think this will be fixed in https://github.com/ChainSafe/lodestar/pull/1352/files#diff-8fbadb8107c3ad648c4f8238bd7b88d1R80
getBlockRange should now handle errors from network req/resp and retry the failed chunk.

Initial sync is stable now, seems like the issue does not happen anymore


主页显示文章遍数在那调

Expected behavior (预期行为)
Actual behavior (实际行为)
Steps to reproduce the behavior (重现步骤)
NexT Informations
Add the  ✔  sign before an item which is affected by this behavior.
NexT Version:

Master
Latest Release
Old version -

NexT Scheme:

All schemes
Muse
Mist
Pisces

Other Informations (Like Browser, System, Screenshots)

这位同学，建议这样的问题问问谷歌百度。答案如图

http://theme-next.iissnan.com/faqs.html#setting-page-size


False positive warnings and validation crash

If you download this trace:
https://www.dropbox.com/s/ycsy007lli0im5e/witcher3.7z?dl=0
Run it with apitrace.exe with DXVK binaries (d3d11.dll and dxgi.gll) dropped into the same directory; observe these sort of errors:
VkPhysicalDeviceFeatures::shaderStorageImageWriteWithoutFormat but is not enabled on the device
I'm told this particular trace also causes a crash when validation is enabled.

I was finally able to reproduce this issue with the following setup:

wine 3.11
apitrace-msvc-latest (https://people.freedesktop.org/~jrfonseca/apitrace/ 2018-07-04)
DXVK and witcher3.trace from issue descriptoin
NVIDIA driver 396.24.02 (beta version with VK_EXT_vertex_attribute_divisor required by DXVK)

Resulting in the following unique validation errors:
Validation(ERROR): msg_code: -1:  [ UNASSIGNED-CoreValidation-Shader-FeatureNotEnabled ] Object: VK_NULL_HANDLE (Type = 0) | Shader requires extension VK_KHR_shader_draw_parameters but is not enabled on the device
Validation(ERROR): msg_code: -1:  [ UNASSIGNED-CoreValidation-Shader-FeatureNotEnabled ] Object: VK_NULL_HANDLE (Type = 0) | Shader requires VkPhysicalDeviceFeatures::sampleRateShading but is not enabled on the device
Validation(ERROR): msg_code: -1:  [ UNASSIGNED-CoreValidation-Shader-FeatureNotEnabled ] Object: VK_NULL_HANDLE (Type = 0) | Shader requires VkPhysicalDeviceFeatures::shaderClipDistance but is not enabled on the device
Validation(ERROR): msg_code: -1:  [ UNASSIGNED-CoreValidation-Shader-FeatureNotEnabled ] Object: VK_NULL_HANDLE (Type = 0) | Shader requires VkPhysicalDeviceFeatures::shaderCullDistance but is not enabled on the device
Validation(ERROR): msg_code: -1:  [ UNASSIGNED-CoreValidation-Shader-FeatureNotEnabled ] Object: VK_NULL_HANDLE (Type = 0) | Shader requires VkPhysicalDeviceFeatures::shaderStorageImageReadWithoutFormat but is not enabled on the device
Validation(ERROR): msg_code: -1:  [ UNASSIGNED-CoreValidation-Shader-FeatureNotEnabled ] Object: VK_NULL_HANDLE (Type = 0) | Shader requires VkPhysicalDeviceFeatures::shaderStorageImageWriteWithoutFormat but is not enabled on the device
Validation(ERROR): msg_code: 333448904:  [ VUID-VkSubpassDependency-srcAccessMask-00868 ] Object: VK_NULL_HANDLE (Type = 0) | CreateRenderPass: pDependencies[1].srcAccessMask (0x7E0) is not supported by srcStageMask (0x700). The spec valid usage text states 'Any access flag included in srcAccessMask must be supported by one of the pipeline stages in srcStageMask, as specified in the table of supported access types.' (https://www.khronos.org/registry/vulkan/specs/1.0/html/vkspec.html#VUID-VkSubpassDependency-srcAccessMask-00868)
Validation(ERROR): msg_code: 333448906:  [ VUID-VkSubpassDependency-dstAccessMask-00869 ] Object: VK_NULL_HANDLE (Type = 0) | CreateRenderPass: pDependencies[0].dstAccessMask (0x7E0) is not supported by dstStageMask (0x700). The spec valid usage text states 'Any access flag included in dstAccessMask must be supported by one of the pipeline stages in dstStageMask, as specified in the table of supported access types.' (https://www.khronos.org/registry/vulkan/specs/1.0/html/vkspec.html#VUID-VkSubpassDependency-dstAccessMask-00869)
Validation(ERROR): msg_code: 532679382:  [ VUID-vkCreateDevice-ppEnabledExtensionNames-01387 ] Object: 0x7c89f0c0 (Type = 1) | Missing required extensions for device extension VK_EXT_vertex_attribute_divisor, VK_KHR_get_physical_device_properties2. The spec valid usage text states 'All required extensions for each extension in the VkDeviceCreateInfo::ppEnabledExtensionNames list must also be present in that list.' (https://www.khronos.org/registry/vulkan/specs/1.0/html/vkspec.html#VUID-vkCreateDevice-ppEnabledExtensionNames-01387)
Validation(ERROR): msg_code: 532679382:  [ VUID-vkCreateDevice-ppEnabledExtensionNames-01387 ] Object: 0x7cf8b040 (Type = 1) | Missing required extensions for device extension VK_EXT_vertex_attribute_divisor, VK_KHR_get_physical_device_properties2. The spec valid usage text states 'All required extensions for each extension in the VkDeviceCreateInfo::ppEnabledExtensionNames list must also be present in that list.' (https://www.khronos.org/registry/vulkan/specs/1.0/html/vkspec.html#VUID-vkCreateDevice-ppEnabledExtensionNames-01387)

I'll start digging around with debugger to see why the shader validation code is printing those errors.  One final note: I was not able to reproduce the crash.  The attached trace exits cleanly with validation enabled.

@mikes-lunarg : Could you please move this issue to Vulkan-ValidationLayers?


dependency issue | webexteamssdk 1.7 depends on PyJWT==1.7.1

I'm configuring my bot over Python and I'm using multiple chat platforms which require at least PyJWT>=2.4.0
the repo requires PyJWT 1.7.1.
can you update the version of PyJWT? or give me an alternative solution?

@Loprock PyJWT is updated in the 3.0 release
https://github.com/WebexCommunity/WebexPythonSDK/pull/234/files#diff-50c86b7ed8ac2cf95bd48334961bf0530cdc77b5a56f852c5c61b89d735fd711R45


How to infer with my own Data

How can i infernce with custom data

I'm also curious about this. It seems like I have to run the shell script from the so762 recipe to try some inference from custom data. But does it also mean that I can start from recording some pronunciations for myself and extract the feature files by using the kaldi recipe? If so, do I just replace the .wav files with my own recordings in the so762 and run the recipe?
Thank you
Theo Seo

It seems like I have to run the shell script from the so762 recipe to try some inference from custom data.

Yes, you have to run the Kaldi so762 recipe to get GOP features. FYI, GOP feature relies on an ASR model, so Kaldi might be the best tool to run.

But does it also mean that I can start from recording some pronunciations for myself and extract the feature files by using the kaldi recipe? If so, do I just replace the .wav files with my own recordings in the so762 and run the recipe?

Yes, but you need to make the format consistent with the original so762 dataset, in particular, your wav files need to be either have the same content as the original wav files, or you need to prepare the canonical transcripts (i.e., the ground truth text). But once you have your dataset ready, you should be able to generate the GOP features.
-Yuan

Thanks for the reply !

Yes, but you need to make the format consistent with the original so762 dataset, in particular, your wav files need to be either have the same content as the original wav files, or you need to prepare the canonical transcripts (i.e., the ground truth text). But once you have your dataset ready, you should be able to generate the GOP features.

I have another question. If I want to infer my pronunciation from recordings from the pretrained model, all I need would be the GOP features extracted by the recipe. The thing is, I'm still confused with GOP feature extraction.. It seems like the dataset should also have the human-annotated scores of pronunciation to align with the format of so762 or is it not necessary?
Thanks again.
Youngho Seo

The thing is, I'm still confused with GOP feature extraction..
Kaldi certainly has a learning curve - you could raise an issue at the Kaldi repo.

It seems like the dataset should also have the human-annotated scores of pronunciation to align with the format of so762 or is it not necessary
No, I don't think so, those scores are just for evaluation, the Kaldi recipe does not need to know the ground truth score to make a prediction. Specifically, I think you can stop at https://github.com/kaldi-asr/kaldi/blob/9af2c5c16389e141f527ebde7ee432a0c1df9fb9/egs/gop_speechocean762/s5/run.sh#L152-L185 and ignore the last two stages if your goal is just to get GOP features.

@TheoSeo93 Hi ! Have you succeed with the inference on your own data?


GPUDeviceStorage is not used? why?

I found that GPUDeviceStorage is not used, however CPUDeviceStorage is used, why is that?

Are you sure you compiled with CUDA support enabled? What is it that you are trying to do?

I didn't compile with CUDA, I'm reading the code, I see that when CUDA is used, it actually use GPUPooledStorageManager to do the allocation, on the other hand, CPUDeviceStorage is used no where.
I'm just curious why CPUDeviceStorage is there, and not in use.
I'm on the master branch.

Oh, ok. This is because CUDA allocations and deallocations are much more expensive (since they deal with pinned memory), especially with multiple GPUs per node. They also introduce stalls in the GPU pipeline, which is not something we want for maximum performance. That is why MXNet uses caching allocator (GPUPooledStorageManager) instead of a naive one.

@szha please close


Form Recognizer: Don't return interfaces in Response

We'll need to update the return types from client methods so that they don't return Interfaces.
This is for two reasons:

We shouldn't return types in Response that we don't own
We shouldn't return Interfaces because they prevent Response's implicit cast to T from working.

This will allow us to update the extension methods so only one is needed instead of four.
In TextAnalytics we addressed this as follows: https://github.com/Azure/azure-sdk-for-net/pull/11674

APIView has been updated with the design for this.


Add Linear OAuth Provider

Hi,
I've added Linear as an OAuth provider, based on previous OAuth integrations.
Testing locally, I've checked everything several times: PR code, PocketBase UI, Client integration, Linear dashboard (client ID, client secret). But i'm still getting a "Failed to fetch OAuth2 token" error on authWithOAuth2 with oauth2: "invalid_grant" "Invalid grant: code verifier is invalid" as details.
Note:

I've set http://<IP_ADDRESS>:8090/api/oauth2-redirect callback URL into my Linear App.
I can authenticate into Linear and accept integration through the popup window then see the URL to be oauth2-redirect-success just before being automatically closed.

If it doesn't work for you also, let me know how i can fix it.

If the integration doesn't work then it is not ready for a PR.
I'm finalizing the v0.23.0 release and don't have time at the moment to read the Linear documentation and find out why it fails.
I recommend to test it with a plain pb_public/index.html file like:
<!DOCTYPE html>

    <meta charset="utf-8" />
    <meta name="viewport" content="width=device-width, initial-scale=1" />
    <title>OAuth2 test</title>

    <button id="btn">Login</button>

If it still doesn't work, you can experiment switching the pkce option to false.

Now it works !
Switched pkce option to false and corrected the way to retrieve user info to fit Linear GraphQL API.

Earlier today I contacted the Linear support to ask for the PKCE and they confirmed that it is not supported at the moment.
I've rebased and squash merged the changes locally with some minor adjustments:

added check for the active user field to prevent authentication for disabled (suspended) accounts
swapped name and displayName because the latter is the nickname/username that is unique per organization

The provider will be available with the final v0.23.0 release soon.


Off-Chain Trading Visual Design

Personally I would consider closing this as "off chain" trading should look no different to the user than on chain trading, same comment I made on the other issue


The state machines does not work in this version.

"rive version": "0.3.1-canary.26"
"unity version:" "2022.3.49f1c1"
`private void SetValue(string numberName, int num)
{
var mStateMachine = m_rive_file.Artboard.StateMachine(0);
var input = mStateMachine.GetNumber(numberName);
input.Value = num;
}
private void Update()
{
if (m_stateMachine != null)
{
m_stateMachine.Advance(Time.deltaTime);
}
}
`
i see input value was set correctly, but the rive state was not change.

Hi, does this also happen with the v0.2.1 release?

i used urp pipeline, it's looks like v0.2.1 does not support urp?

Because v0.3.1 have Rive Panel and Rive Widget, we can easily add rive animation to UGUI.
but we also find the rive rendered will extra add a black outline.

Ohh I see! When using the RivePanel and RiveWidget, you no longer need to call advance() or instantiate the statemachine yourself like you're doing with m_rive_file.Artboard.StateMachine(0);
In your script, you can take a reference to the rive widget:
        [SerializeField] private RiveWidget m_riveWidget;

        void Start()
        {

             if (m_riveWidget.Status == WidgetStatus.Loaded)
            {
               var input = m_riveWidget.StateMachine.GetNumber(numberName);
               input.Value = num;
            }
        }

In your current script, you're creating a new state machine rather than using the reference in the widget, so you won't be able to see any changes because they're being applied to a different statemachine.

Are you able to share the .riv/rev file with us so we can take a look at the outline issue?
If you don't want to share it publicly, you can also send it to us privately here.

Are you able to share the .riv/rev file with us so we can take a look at the outline issue?
If you don't want to share it publicly, you can also send it to us privately here.

I had send You a .riv file by the privately link (RIV-7607).
please check this problem,  thanks for your help.
At the beginning i want use a shader to fix this problem as before, but in this version it' not easy to apply that.

so, where can i see the up to date API document?

This will be available here later this week
Regarding the outline issue, is this what you're referring to (the dark lines around the finger edges):

yes,how can i solve this problem like this?

It's a renderering issue, so I'll bring it up with the team.
Before RivePanel and RiveWidget, were you applying a shader to a RawImage to fix it?

Yes, i found a solution to fix this problem.

also is change the raw Image shader, it's a Legacy shader can works in urp and build in.


Nlbwmon bug in showing values .

Hi All,
after last update of nlbwmon on OpenWRT, it is showing incorrect values:

What is have managed to figure out it is adding number bytes just before conversion to GiB which makes it unreadable. Previous months looks exactly the same.
I have this bug on both of routers I manage.
Can you Guys check if this is the same case for you?
Is there any fix i could apply to fix this?

You need to upgrade the luci-base package und clear your browser cache.


OpenId screens are ugly

Feel free to copy what Orchard.Users is doing.

/cc @jersiovic

Well I have checked out the head of the branch and I find that there is not any page that looks nice on the Dashboard. In my original pull request that was not the case.
Now I get errors like the following ones in browser console accessing Orchard.User/admin/Index page or any other based on the Admin theme.
Index:13 GET http://localhost:2918/TheAdmin/Styles/TheAdmin.min.css 404 (Not Found)
Index:153 GET http://localhost:2918/TheAdmin/Scripts/TheAdmin.js 404 (Not Found)

Even though those files exists. Any idea of what made it fail?

Same happens in the master branch.

Was this due to my change?
Sent from my iPhone

On 13 Sep 2016, at 23:19, Sergio Navarro<EMAIL_ADDRESS>wrote:
Same happens in the master branch.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

Same happens in the master branch. It is a new clone.
I get 404 errors in Orchard.Setup area . Some js and css res. Even though those files exists after using gulp build.
Orchard2 is new to me.

Can you try again now? It works on my machine ... I will try to reset the assets in the meantime

Yes now it works with your changes in master branch. Thank you.
Can you update the oauth2 branch with changes in master branch?

Yes, you should rebase the openid branch on master (not the opposite). If you are not sure how to do it, I can help.

Despite you added me as a member I still feel more comfortable working on my own repo and sending PRs to be sure I don't break anything :)
But I know how to do a rebase. Later after the Orchard meeting I will do it.

not sure you can make a PR out of a rebase


Pixelbook cannot print

It looks like Google Cloud Print was disabled on 12.31.2020. Currently trying to print from the Pixelbook returns the following error:

The temporary fix for this would be to just print from another machine locally.

The temporary fix for this would be to just print from another machine locally.

So this does not seem to be related to Google Cloud Print being retired, but not being able to connect to local instances due to, perhaps VPN running? I think that this can be closed now.

So this does not seem to be related to Google Cloud Print being retired, but not being able to connect to local instances due to, perhaps VPN running? I think that this can be closed now.


[AutoPR eventgrid/resource-manager] EventGrid: Updated README.MD configuration to include the new preview API version.

Created to sync https://github.com/Azure/azure-rest-api-specs/pull/3830

This PR has been merged into https://github.com/Azure/azure-sdk-for-java/pull/2206


Refresh the install

Just a minor fix to get the example script to work, as recommended in https://github.com/aio-libs/aiohttp-cors/issues/184
Additionally, added a Pipfile (and lock) to have the option of installing using pipenv.

Thanks


Functions of numeric type and support for dark mode of tag type

This is a great form plug-in

I hope to support simple arithmetic functions in number types, such as = sub() in Excel

tag type please consider supporting dark mode.
Dark mode: the current tag can't see the text clearly when selecting the color

@daoif Hi daoif. Thank you for your feature requests. Arithmetic functions seem interesting. Could you give me some specific examples of functions with input and output? e.g.  text: add(1,2) rendered output: 3
Yes, that is something I have noticed about dark mode. I will be able to fix that.

@trey-wallis

I mean the operation between cells, like the sub () of Excel


Update documentation on stdin input with rustfmt

rustfmt supports formatting files as well as rust code provided via stdin. However, the readme documentation and rustfmt --help description text could use some updates to make this explicitly clear, as well as call out that if you run rustfmt without specifying any files that rustfmt will be waiting for input from stdin.
This could be addressed by updating the  running section in the readme, with more details and ideally some examples (e.g. echo "fn     main (   ) {    }" | rustfmt with stdout output from rustfmt), as well as updating the structopt info to provide more detail when users run rustfmt --help.
https://github.com/rust-lang/rustfmt/blob/27b54e9963cefbbb9895e2ba6eaabb48a1d7e110/src/rustfmt/main.rs#L44-L47
https://docs.rs/structopt/0.3.15/structopt/#how-to-derivestructopt
If anyone is interested in working on this please leave a comment or ping us on Discord!

I just started working on this, do you want me to leave it for a new contributor?

I made a pull request for that new note section.

I would like to give the note part a shot. Once I figured out how to make pull requests form fork to forked from.

Here: #4337

Regarding examples, I personally wouldn't even go that far perhaps.
Regarding what I suggested, it may be still not foolproof. The tricky parts is that although most options may need <file>, some may not, like -V for version. And the idea that one may keep the input stdin input out actually still remains although for technical reasons not true. Conveying this dynamic, and trying to keeping it short and snappy without starting the sentence like "YoU mUsT nOt UsE rustfmt FoR pRiNtiNg HeLp", is tricky a bit.
As a side note for the designe choice regarding <file>. I figure <file> wasn't attached to an actual option because it is used by most options anyways, and it's the whole purpose of rustfmt to format that. However, since nobody every, not even I, would use an option without reading it up in the docs/info what it actually does, that actually would clear up this issue. And also allow typing rustfmt for printing help like the others. Except of course, this would be a much bigger change than the docs and introduce legacy code/behavior. But that is not needed, it is just a side note about the design choice here of how <file> functions. My 2 cents.
I closed my previous pull request, this needs a notch more of thought. But I've got an idea.

I think all users of rustfmt have the same goal: just to get the app to format some code. How to tell rustfmt to do this feels secondary to that goal, and while it is important, IMO being able to provide good documentation for the app and maintaining compatibility with existing usages is much more important.
UX on the granularity of CLI flags and default inputs expected by a program can be disagreed on by reasonable people; I think it is unlikely a productive conclusion would be made of this. imho we should focus on where we already are and find ways to better support information discovery.

Current Readme:

You can run Rustfmt by just typing rustfmt filename if you used cargo install. This runs rustfmt on the given file, if the file includes out of line modules, then we reformat those too. So to run on a whole module or crate, you just need to run on the root file (usually mod.rs or lib.rs). Rustfmt can also read data from stdin. Alternatively, you can use cargo fmt to format all binary and library targets of your crate.
You can run rustfmt --help for information about available arguments.
When running with --check, ...

Take 2. Mind the lack of "Rustfmt can also read data from stdin.", since it is later mentioned.

You can run Rustfmt by just typing rustfmt filename if you used cargo install. This runs rustfmt on the given file, if the file includes out of line modules, then we reformat those too. So to run on a whole module or crate, you just need to run on the root file (usually mod.rs or lib.rs). Alternatively, you can use cargo fmt to format all binary and library targets of your crate.
Running rustfmt needs either a file, or a source via stdin directly, and is mandatory.  Except, exclusively with options -V for printing the version and --help for printing option usage information.
When running with --check, ...

For the record, it's bugging me that <file> looks like mandatory only to not be that really. It's of course logical that printing version and help doesn't need any file to format. But it's not logical to look mandatory when from a very technical point, it's actually not. You know 1+1=2.5. I'm not sure how to tackle this issue, unless it doesn't sound too stupid to mention that -V and --help don't need data. For what it's worth, it makes it clear though that all other options need it without exception, it could be worth a hint, and of course a mere rustfmt would be discouraged with that wording.
But, somebody must correct me if that's not even true, that all other options need <file>. It's just the impression I have currently by reading the --help content through.
The new for <file> could be <filename.rs or source via stdin>.

imho we should focus on where we already are and find ways to better support information discovery.
Yeah, people really need to be warned about me. Because I'm beyond making excuses for my failures. I'm already in the realm of the perfectionist who transitions to Obsessives Compulsive Disorder. Ever watched the TV show Monk? Don't...

it's bugging me that <file> looks like mandatory only to not be that really

This would be a good issue to file upstream to structopt. The relevant code is here:
https://github.com/rust-lang/rustfmt/blob/27b54e9963cefbbb9895e2ba6eaabb48a1d7e110/src/rustfmt/main.rs#L130-L132
Imo Vec<T> should be printed as [files]* in the args, not <files>. Maybe they will say that files should be Option<Vec<T>>, but then you get the error message  Option<Vec<T>> type is meaningless for positional argument.

@ayazhafiz If that can mean that typing rustfmt alone can print info then, then I will have a closer look at the code finally.
And regarding this printing of info through just typing cargo, rustup, and perhaps rustfmt, too. Correct me if I'm wrong, but that's an "idiomatic" way for CLI software in general, to be able to do this. My old Quake devs tools collecting dust, so all light, qbsp, and vis exes, they always print usage information in the terminal when used without any input or options, too.
So, whether it's just my OCD or perfectionism, this should be fixed, frankly, either way if possible. I will have a look.

@NickelCoating - I opened this issue specifically to address updating documentation, but I feel like this is going way off topic with the conversation veering back towards when help text should be displayed and the-V for displaying version information.
You've expressed your thoughts on what you think should happen, but the current behavior of rustfmt allowing users to provide text via stdin is a feature, not a bug. Removing the current feature to instead provide help text is an entirely different discussion (and a breaking a change) that should happen elsewhere.
Please keep comments on this thread on topic.

@calebcartwright , yes, I'm not viewing this as a bug. I just need a full picture, and I like to write down such thoughts of the whys. The ripples such a feature change would cause is a such a reason why one may want to stick to just changing the docs instead, indeed. So, I agree with you, @calebcartwright lets not blow things out.
However, unfortunately I added new reasoning to this story that I started with the last issue I opened. Reasoning only mentioned here, and not there. The new reasoning for a blank rustfmt being able to print info is the "idiomatic terminal behavior", that ALWAYS prints info, or usage information when no input is given. I made an example with the Quake level design dev tools that behave all the same way.
So, let's just start here. My claim that a blank command prints usage information is idiomatic terminal behavior, it needs to be challenged. Because if that is true, only a hobby project would ignore such "rules", and not professional software like Rust. Meaning if it possible to maintain the feature, and do the info, too, then writing docs now may only get you to rewrite the docs later when someone else points out this flaw!? The docs really can wait for me at least. I already know what I did run into, for what it's worth.
So, what does everybody think about this idiomatic claim of mine?

@NickelCoating - Please respect my previous ask that you not continue taking this thread off topic. I am marking these comments as off topic, and am not going to allow a continued orthogonal debate here.

@ayazhafiz - let me know if you're still interested in working on this one and if so i'll drop the help-wanted label. Feel free to revamp the running section altogether, as it's a bit outdated with rustfmt 2.0 anyway (for example --recursive flag would be required to format submods).
I'd like to lead with cargo fmt as that's the most common use case and easiest usage pattern for folks, and then call out the files & stdin options with rustfmt itself. There's a portion of rustfmt users that make use of the stdin feature pretty extensively, but we can certainly do a better job broadcasting that feature and use cases.
As far as the inline help text, understood we may be limited in some ways around what's available via structopt, but I have to imagine we can make some improvements. Even something as marginal as changing Format Rust code to something like Format Rust code in files or from stdin would be helpful.

Yeah I can take this, will do in the next day or so.

От: Caleb Cartwright<EMAIL_ADDRESS>Отправлено: Tuesday, July 21, 2020 1:36:24 PM
Кому: rust-lang/rustfmt<EMAIL_ADDRESS>Копия: hafiz<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Тема: Re: [rust-lang/rustfmt] Update documentation on stdin input with rustfmt (#4336)
@ayazhafizhttps://github.com/ayazhafiz - let me know if you're still interested in working on this one and if so i'll drop the help-wanted label. Feel free to revamp the running section altogether, as it's a bit outdated with rustfmt 2.0 anyway (for example --recursive flag would be required to format submods).
I'd like to lead with cargo fmt as that's the most common use case and easiest usage pattern for folks, and then call out the files & stdin options with rustfmt itself. There's a portion of rustfmt users that make use of the stdin feature pretty extensively, but we can certainly do a better job broadcasting that feature and use cases.
As far as the inline help text, understood we may be limited in some ways around what's available via structopt, but I have to imagine we can make some improvements. Even something as marginal as changing Format Rust code to something like Format Rust code in files or from stdin would be helpful.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/rust-lang/rustfmt/issues/4336#issuecomment-662035809, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AE6GL6XQR5UUMQXKDRTYBZLR4XN2RANCNFSM4PDA4D5A.

Awesome, thank you!

@calebcartwright we should reopen this until the follow up PRs go in?

Yeah good catch. I thought the PR description was update to remove the keyword but presumably some commit message had it in there


SVG Icons missing

Hello,
I'm trying to start the app locally using Firefox (latest version 54.0.1) and it does not show the svg images, please see screenshot. Chrome seems to render everything as expected. Is there something to be considered for FF, any ideas? Cloned the code with npm from Github.
thx

It was a cross-site scripting issue while loading the fonts that contain also the SVGs. Changed rule in FF config to allow cross-site scripting during development.


chore: remove coinbase

Description
this is not proceeding and unfortunately needs to be removed.
Notice

[x] Have you followed the guidelines in our Contributing guide?
[x] Have you checked to ensure there aren't other open Pull Requests for the same update/change?

Pull Request Type

[ ] :bug: Bug fix (Non-breaking Change: Fixes an issue)
[x] :hammer_and_wrench: Chore (Non-breaking Change: Doc updates, pkg upgrades, typos, etc..)
[ ] :nail_care: New Feature (Breaking/Non-breaking Change)

Issue (if applicable)

closes #2241
Risk

check fox page still functions as intended
Testing

coinbase should not appear in fiat ramps list
feature flag should be gone

Screenshots (if applicable)
before

after

As @gomesalexandre said, just the coinbase-pay repo to go.
But @gomesalexandre the coinbase.png logo needs to stay, because we still want the coinbase logo to show in the centralised trading opportunities section I imagine.

That's correct, the coinbase.png asset should stay, it is scoped in the foxPage domain and is used as the icon of the centralized opportunity as you've mentioned, linking to Coinbase to get FOX. Only the Coinbase Pay one should go.


[bug/ECP-1298] - Exclude data prior to 2021/2022 Academic Year in stats extracts

@martikat going to re-work this as it looks like the senic gem supports versioning. Will ask for a re-review when ready


Add new fields for default k8s version and ranges

closing in favor of https://github.com/rancher/rancher/pull/16713, which cleans up the commits a bit


Webview2 - Fixed version : sometimes "not found"

Hello,
I could successfully use the option to specify the path to a fixed version of WebView2 (CreateCoreWebView2EnvironmentWithOptions , parameter WEBVIEW2_BROWSER_EXECUTABLE_FOLDER - https://docs.microsoft.com/en-us/microsoft-edge/webview2/reference/win32/webview2-idl?view=webview2-1.0.1293.44#createcorewebview2environmentwithoptions)
But... on some specific computers, this does not work, I just get an error "NOT FOUND".
I already tried to add the access rights on the folder as described here : https://docs.microsoft.com/en-us/microsoft-edge/webview2/concepts/distribution (icacls), but this has no impact.
The only thing I could find is a log in the event viewer that seems to be linked (in french) :
"Les paramètres d’autorisation propres à l’application n’accordent pas l’autorisation Local Activation pour l’application serveur COM avec le CLSID
{2593F8B9-4EAF-457C-B68A-50F6B8EA6B54}
et l’APPID
{15C20B67-12E7-4BB6-92BB-7AFF07997402}
au SID JEAN-MAES-E580\jeang de l’utilisateur (S-1-5-21-2010270883-1447936690-2847641450-1001) depuis l’adresse LocalHost (avec LRPC) s’exécutant dans le SID Non disponible du conteneur d’applications (Non disponible). Cette autorisation de sécurité peut être modifiée à l’aide de l’outil d’administration Services de composants."
Is there any place where we could have a hint on the error ? Any idea why the folder is not found ?
With the evergreen version it's working, but we would like to avoid the automatic updates because we had an issue and we suspect this is linked to an automatic update.
For the moment, that "not found" problem is happening on 2 computers, 6 have no issue.
PS : The final application is a Java application using SWT + Edge brower (which is using the WebView2Loader.dll)
Thank you,
Jean-François

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

ID: 8a805f15-55ba-4ef4-aeda-22188a040c66
Version Independent ID: 88de0955-526f-a4c9-efcc-d952281850e1
Content: Distribute your app and the WebView2 Runtime - Microsoft Edge Development
Content Source: microsoft-edge/webview2/concepts/distribution.md
Product: microsoft-edge
Technology: webview
GitHub Login: @MSEdgeTeam
Microsoft Alias: msedgedevrel

Thanks for reaching out. In order to get this resolved quickly for you, I would advise posting this issue on this other repository instead: https://github.com/MicrosoftEdge/WebView2Feedback/issues
The WebView2 team and community are much more active over there as opposed to here, where we only deal with updating the documentation.
I hope this helps and I hope you can find a solution! Thanks for your understanding.


Watcher assert triggered by writing to non 32B aligned DRAM address

Due to dispatch cmd being 16B we could end up in a case where we split a page of data at a non 32B aligned address. This invalidates DRAM alignment.
This can be addressed by uplifting dispatch cmd to be 32B. A future potential solution could be to have dynamically sized dispatch cmds.

Closing this in favour of uplifting watcher to not assert on cases where src and dst alignment matches, even if dst does not match its alignment spec.
cc @pgkeller


Helpful comments and removed void returns

Hey dudes, I was working on your notifications and I noticed notifications weren't sending if the "email" value of a user was empty. It took me a while to figure out since I was expecting an error.
After a little more thought it was obvious why you wouldn't want to throw an error there, it's not "eloquent" ^^ and will be a pain when dealing with large collections. So I added a little comment above the method that mentions this. That little snippet might clear up future confusion for other developers.
Also as a bonus, I removed some un-needed returns.
Peace <3

y u do diz travis :(

Closing this since my comment is covered by documentation and the removed return was just a bonus but not really needed. <3


Design system adoption & migration

Objective
Provide recommendations on how to best support teams migrating to Salt from UI TK (including the identification of practical limits on migration)
Primary Research Questions
What factors influence users’ (and teams’) decision-making when selecting a design system?

At JPMC
In the CIB
When they currently use a design system (migration)

How can we best support migration to Salt?
What are the motivating factors that would encourage a team to migrate to another design system?

How do decision makers trade off the cost to migrate versus the value from migration?

Secondary/Explorative Questions
What are the use cases for a design system in the CIB?

Among existing UITK users?
How are use cases associated to user and team needs from a design system?

### Tasks
- [x] Briefing/methodology
- [x] Protocols for interviews
- [x] Schedule inteviews
- [x] conduct interviews
- [ ] Code interview transcripts
- [ ] Assess barriers and facilitators: identify range of influences on the target behaviour
- [ ] Potential: evaluative questionnaire with broader participant group (dept on data saturation)
- [ ] Analysis of results
- [ ] Documentation of results/recommendations

2/15 - conducting interviews (11 scheduled) - aim to finish up next week

Final interview with app owners wednesday this week - follow-up / evaluation with broader group will be required after coding of transcripts

Interviews complete - starting analysis now. Will likley use interview themes to construct a survey with a larger sample

@zdxd  - hi zoe, are there any updates on this ticket?

doing analysis

All done, @shinytoyrobots to review and then can be shared with the team

Objective met "Provide recommendations on how to best support teams migrating to Salt from UI TK (including the identification of practical limits on migration)"
New ticket for migration workshop and initatives? @shinytoyrobots


Text Fields > HTML Input Types: Range slider line missing

What RMWC Version are you using [major.minor.patch]:

Name your build system [Webpack, Rollup...]:

Describe the bug with as much detail as possible:

What happened, and what was supposed to happen:

This issue also exists on v 8

I'll look into it.

Fixed in https://github.com/rmwc/rmwc/pull/1051


ERROR in authentification : secretOrPrivateKey must have a value

To Reproduce
Steps to reproduce the behavior:

Use case starter as template
follow the README.me and seed
add a .env with a variable JWT_secret
try to authentificate
the error occurs

Expected behavior
I want to authentificate
Screenshots
When I try to auth I have an internal error server that said :

Additional context
I add a .env with a JWT_SECRET but the error still occurs.
This article talk about it : https://dev.to/emmanuelthecoder/how-to-solve-secretorprivatekey-must-have-a-value-in-nodejs-4mpg

@ismaelguerrib CASE Starter is not supposed to be used as a template.
You can look at CASE docs and follow the install process.


[#noissue] Cleanup configuration of failsafe-plugin

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@bea4d62). Click here to learn what that means.
The diff coverage is 39.43%.

@@            Coverage Diff            @@
##             master    #7971   +/-   ##
=========================================
  Coverage          ?   30.62%
  Complexity        ?    11255
=========================================
  Files             ?     3277
  Lines             ?   117243
  Branches          ?    16183
=========================================
  Hits              ?    35907
  Misses            ?    77991
  Partials          ?     3345

Impacted Files
Coverage Δ

...nt/plugin/proxy/apache/ApacheRequestConstants.java
0.00% <0.00%> (ø)

...in/proxy/apache/ApacheRequestMetadataProvider.java
0.00% <0.00%> (ø)

...ugin/proxy/apache/ApacheRequestParserProvider.java
0.00% <0.00%> (ø)

...t/agent/plugin/proxy/apache/ApacheRequestType.java
0.00% <0.00%> (ø)

...nt/agent/plugin/proxy/app/AppRequestConstants.java
0.00% <0.00%> (ø)

...t/plugin/proxy/app/AppRequestMetadataProvider.java
0.00% <0.00%> (ø)

...ent/plugin/proxy/app/AppRequestParserProvider.java
0.00% <0.00%> (ø)

...inpoint/agent/plugin/proxy/app/AppRequestType.java
0.00% <0.00%> (ø)

...gent/plugin/proxy/nginx/NginxRequestConstants.java
0.00% <0.00%> (ø)

...ugin/proxy/nginx/NginxRequestMetadataProvider.java
0.00% <0.00%> (ø)

... and 5 more

Continue to review full report at Codecov.

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


[Q] What word bank/corpus is used when generating run names for sweeps or upload artifacts?

Can someone point me to the location in the code where run names are generated for sweep runs or uploaded artifacts, as well as the word bank or corpus from which the names are generated?

Hi @evdcush,
The word bank which is used for our run name generation in under a private repo, but the code used to generate the run names is based on this repository.
Please let me know if I can help with anything else.
Thanks,
Ramit

Hi @ramit-wandb,
I'm wondering why the word bank would be private, but I appreciate your response and sharing what you can, thank you!


Mod not functioning [Fabric 1.20.2 Server]

Hey! I'm not sure if this is, like, a mod that isn't being updated, but if it is I would like to note that it currently does not seem to be working!

I do still maintain it, I just haven't actively needed it in the latest versions so I haven't noticed any breakage. I'll take a look at it.

Just to confirm, are you on a Fabric server or a Quilt server?

Currently I'm using Fabric. My client is Quilt, but Fabric was needed for some utility mods

This report is invalid then, as the mod (Currently) requires Quilt on the server. I'll be repackaging the mod to let it work in Fabric when I get some free time.


corrected quote

wrong type of quote used - command does not run this way in the cli

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

Looks good; thanks for this update @tvdvoorde.


Navbar

Description

Improved the navbar of the homepage.
Added a toggle for dark theme
Fixes #8

Type of Change:

Quality Assurance
User Interface

Screenshots

Before

After

Checklist:

[x] My code follows the style guidelines(Clean Code) of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have added tests/screenshots(If any) that prove my fix is effective or that my feature works

Please resolve these merge conflicts

Please resolve these merge conflicts

I've resolved the conflicts. Please review.


Add information about PodLifecycleSleepAction (KEP3960)

PodLifecycleSleepAction updates as part of https://github.com/kubernetes/enhancements/issues/3960

/remove-area blog release-eng

/remove-language de es fr pl pt zh
/remove-sig release

/cc @thockin
Not sure whether if this is enough😢. And if not what should be added, and to where🤦.

Please squash the PR into a single commit.
The definitions (if appears in the types.go file) will be refreshed by the reference generator. Don't worry about it at the moment.

/approve
/hold
The hold can be lifted when the upstream implementation is merged.

The hold can be lifted when the upstream implementation is merged.

What does the upstream implementation refer to? If it's code changes in k/k repo, then we had it merged before. https://github.com/kubernetes/kubernetes/pull/119026

/remove hold

/unhold

Hello @AxeZhan @thockin :wave:, I see there is work in progress with these docs! 👍 Please take a look at Documenting for a release - PR Ready for Review to get your PR ready for review before Tuesday 14th November 2023. Thank you!

Hello @AxeZhan @thockin :wave:, I see there is work in progress with these docs! 👍 Please take a look at Documenting for a release - PR Ready for Review to get your PR ready for review before Tuesday 14th November 2023. Thank you!

This pr is already merged, so why is this wip? I'm sorry but I'm confused of what to do next.

@AxeZhan never mind, disregard. Thanks!


Showing wrong subject when share pdf through gmail in ios

when share pdf through android it work perfect but when share pdf through gmail in ios it show subject same as text we passed but it should show title as subject.

This is a Gmail issue, not related to this plugin. If you still encounter it and need a workaround, see my answer here: https://github.com/fluttercommunity/plus_plugins/issues/1056#issuecomment-1716352726


Assertion in HttpSM

Started getting this on the Docs / CI site recently:
Fatal: HTTP.cc:2090: failed assertion `!"HTTPInfo::unmarshal bad magic"`
traffic_server: using root directory '/opt/ats'
traffic_server: received signal 6 (Aborted)
traffic_server - STACK TRACE:
/opt/ats/lib/libtsutil.so.8(signal_crash_handler(int, siginfo_t*, void*)+0x18)[0x2ad26e589228]
/opt/ats/bin/traffic_server(crash_logger_invoke(int, siginfo_t*, void*)+0x157)[0x699a95]
/lib64/libpthread.so.0(+0xf5e0)[0x2ad26ff695e0]
/lib64/libc.so.6(gsignal+0x37)[0x2ad2708b91f7]
/lib64/libc.so.6(abort+0x148)[0x2ad2708ba8e8]
/opt/ats/lib/libtsutil.so.8(ink_warning(char const*, ...)+0x0)[0x2ad26e54dfe9]
/opt/ats/lib/libtsutil.so.8(+0x729cc)[0x2ad26e5479cc]
/opt/ats/bin/traffic_server(HTTPInfo::unmarshal(char*, int, RefCountObj*)+0x262)[0x9c4c42]
/opt/ats/bin/traffic_server[0xa72988]
/opt/ats/bin/traffic_server(CacheVC::handleReadDone(int, Event*)+0x1764)[0xa74ad0]
/opt/ats/bin/traffic_server(Continuation::handleEvent(int, void*)+0x14a)[0x6a0b42]
/opt/ats/bin/traffic_server(AIOCallbackInternal::io_complete(int, void*)+0x299)[0xa812e9]
/opt/ats/bin/traffic_server(Continuation::handleEvent(int, void*)+0x14a)[0x6a0b42]
/opt/ats/bin/traffic_server(EThread::process_event(Event*, int)+0x2cc)[0xbcf0b2]
/opt/ats/bin/traffic_server(EThread::process_queue(Queue<Event, Event::Link_link>*, int*, int*)+0x1cb)[0xbcf621]
/opt/ats/bin/traffic_server(EThread::execute_regular()+0x456)[0xbcfc54]
/opt/ats/bin/traffic_server(EThread::execute()+0x20f)[0xbd0785]
/opt/ats/bin/traffic_server[0xbcd491]
/lib64/libpthread.so.0(+0x7e25)[0x2ad26ff61e25]
/lib64/libc.so.6(clone+0x6d)[0x2ad27097c34d]

link #3080

Could you please dump all the buffer in CacheVC::handleReadDone?
see https://github.com/apache/trafficserver/blob/master/iocore/cache/Cache.cc#L2329

@scw00 we're not getting core files from this, because it runs with ASAN. I'd have to disable that. I think this is a new bug, and not related to #3080. I think this started maybe a few days ago, and I think #3080 was a red-herring with the cache getting a mix of FIPS and non-FIPS sized hashes (so I think we should close #3080).