Fix: fetch only incoming orders from Open Collective in fetch-sponsors

This PR fixes a bug with ESLint currently appearing as its own sponsor. This bug is caused by fetching all orders from OC, including those 3 that are actually from ESLint to its dependencies.
After this fix, the fetch-sponsors.js script will be fetching only incoming orders.
Since I can't fully test this because I can't run the script due to some GitHub issues, this PR needs help from someone who can.
Remaining steps:

Checkout this branch.
Set ESLINT_GITHUB_TOKEN env variable.
Run node _tools/fetch-sponsors.
Verify diff for _data/sponsors.json. The expected outcome is that 3 items with "name": "ESLint" should be deleted.
Commit and push to this branch if it's okay (I think we're usually fixing _data/* in the same PR, not waiting for the bot).

The script works with my token now!
Updated sponsors.json


Object.assign has been deprecated in React 15.0.0

React has deprecated the use of Object.assign in the latest version, which makes this library crash.
A quickfix would be changing it to require('module-assign'). I will be creating a PR with this modification, but I still fear it'll break its usage in previous React versions.
Still, if you encounter this problem, hopefully you can use this Fork to work with 15.0.0.

#25


Lightweight ontologies (chapter 2.2)

In Style Guide (chapter 2.2, Ontology) is stated:

In the SEMIC context, we only consider lightweight ontologies [defined in rule SC-R2]

We are afraid that this is too lightweight and limits expressivity too much. The limitation is perhaps due to restriction of UML notation, but makes later usage of data models more challenging.

In our approach, we are going to use OWL profiles that already narrow expressivity, meaning OWL 2 profiles (EL/QL/RL) that are already quite narrow.
Limiting the expressivity of OWL further loses expressive power which is useful in mapping ontologies together, enriching data with inferencing and performing semantic mapping between datasets.
With relying on the "lightweight" approach, we can easily end up in a situation where users merely tag data with commonly interpreted resources. This will make data machine-readable but not machine-interpretable to any meaningful extent, similar to how e.g. DC Terms functions to a large extent.
The primary use for semantic interoperability is the fact that we are harnessing computation to make explicit the implicit links and features within data structures, and to allow for clear separation of what has been asserted and what can be derived from the data. Thus rich inferencing allows us to avoid situations where derived records would have to be stored and managed as separate assertions and not as dynamic inferred views into the primary records.

In this style guide, we do not prevent people from using heavyweight ontologies. What we say is that the Core Vocabularies shall contain a lightweight ontology artefact. If your use case demands more logical axioms, then they can be placed in a separate OWL artefact that  (imports and) extends the core definitions of classes and properties. This is done, for example, in eProcurement Ontology.

Closing this as a Note with detailed explanation has been added at the end of the  SC-R2 convention (see above commit).


using pod with Swift 3.0 project

Hi!
I'm trying to use this cool library in a Swift 3.0 project with pod.
The problem is that when I'm doing pod install "Font-Awesome", 1.5.3 is installed instead of the 1.6.1, so the project doesn't compile because the 1.5.3 code is not written in Swift 3.0
What should I do :) ?
Thanks
Luca.

Hi Luca,
I fixed that issue by publishing a new Version of STLocationRequest (Version 1.3.6).
Please do a pod update on your project and everything should be fine 👌

You're Awesome ! Thank you very much :)

No problem 👍


add license to library.properties

the library metadata should also include the license type.

@thijstriemstra , I have never seen people putting the license into library.properties.

You're right: https://arduino.github.io/arduino-cli/0.19/library-specification/
Weird IMO.


Better tests

Right now, tests contains a mix up of unit and integration tests both using the python unittest library.
Separate them, evaluate options for integration tests and create missing test cases.

It does not really make sense to split tests in unit and integration tests. As they are only really helpful in combination, tests will continue to stay combined. However, pytest will be used instead of unittest.

Done.


Feature/content middleware

Adds the content middleware and uses the variables added to request in the routes.

Resolves #314
DCO 1.1 Signed-off-by: Scott Nath<EMAIL_ADDRESS>

@scottnath branch out of date. otherwise looks good

Resolves #362
Resolves #347


feat(thanos): deploy thanos in AWS

This PR redesigns the existing thanos module to make it deployable on multiple services and is mainly based on the PRs #430, #555 and #920 in the main module. For the time being this only works in AWS (the thanos pods connect to the S3 bucket using Kubernetes ServiceAccounts that have an annotation referring them to an IAM role), however it suffices to adapt the way the pods connect to the bucket to make the module usable on other services.
The Thanos chart was also upgraded to make it compatible with the OIDC proxy (which justifies the enormous amount of files changed by this PR).
We also need to consider if we want to continue to support K3s because I think these are breaking changes with that type of deployment.

I've finally deleted the K3s module as @yann-soubeyrand confirmed it wasn't used by him.


DEV - Refactor release CI workflow

Description

For whatever reason, the package was not compiled during the last release. So, this PR adds additional cleanup and check tasks to the GH workflow to prevent this from happening.
Pull request checklist

[x] Did you test this change locally?
[x] Did you update the documentation (if required)?
[ ] Did you add/update relevant tests for this change (if required)?

Additional information

I made the last changes, which are updating the workflow step names.
That aside, this should be ready.
I still do not understand how the yarn v1/v4 thing happened/works but 🤷🏽♀

From the NPM v10 docs on npm install:
npm install
These also run when you run npm install -g
preinstall
install
postinstall
prepublish
preprepare
prepare
postprepare
From the Yarn 1 docs on scripts:
Scripts are a great way of automating tasks related to your package, such as simple build processes or development tools. Using the "scripts" field, you can define various scripts to be run as yarn run

Actually the more relevant bit from the NPM docs is:
Life Cycle Scripts
There are some special life cycle scripts that happen only in certain situations. These scripts happen in addition to the pre<event>, post<event>, and <event> scripts.

prepare, prepublish, prepublishOnly, prepack, postpack, dependencies

prepare (since<EMAIL_ADDRESS>

Runs BEFORE the package is packed, i.e. during npm publish and npm pack

Runs on local npm install without any arguments

Runs AFTER prepublish, but BEFORE prepublishOnly

NOTE: If a package being installed through git contains a prepare script, its dependencies and devDependencies will be installed, and the prepare script will be run, before the package is packaged and installed.

As of npm@7 these scripts run in the background. To see the output, run with: --foreground-scripts.

The last push addresses all of @gabalafou concerns and any improvements will have to come later as we only needed to get a working pipeline to try and make a pre-release and this has been hanging for too long now


RetryingHttpClientWrapper - HealthIndicatorStore should not be increased on 404

RetryingHttpClientWrapper  the CreateRequestQueue does  _endpointHealthIndicatorStore.IncreaseHealth(endpoint) on 404.
This should not happen.

@cristinamanum , since we are planning to replace this code (https://github.com/NuGet/NuGetGallery/issues/5700) can I close this issue?


Extension issue

Issue Type: Bug
Extension Name: vsliveshare-audio
Extension Version: 0.1.91
OS Version: Windows_NT x64 10.0.19042
VS Code version: 1.55.2

:warning: We have written the needed data into your clipboard. Please paste! :warning:

Closing and marking as a duplicate of #3808. Feel free to join the conversation there! Please try running the command > Live Share: repair audio installation.


⚠ ClamAV has degraded performance

In 9e2f0cf, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 79 ms

Resolved: ClamAV performance has improved in 2510aca.


chore: remove ethereum libaries

I removed all ethereum libraries and removed the ethereum context wrapper from the root folder

@codeWhizperer looking good but instead of commenting out the code can you delete the lines?

@codeWhizperer looking good but instead of commenting out the code can you delete the lines?
Also, there are some lint warnings as part of npm run build — ptal.

will resolve it Asap. Quick question, the ethereumContext is not part of the root project anymore, should the file also be deleted?

@mazurroman I also want to suggest we have a TG channel for easier communication, what do you think ser?

@codeWhizperer looking good but instead of commenting out the code can you delete the lines?
Also, there are some lint warnings as part of npm run build — ptal.

will resolve it Asap. Quick question, the ethereumContext is not part of the root project anymore, should the file also be deleted?

Yes, if the file is not used let's delete it 👍
Please join our TG group here ser.

@mazurroman  I just updated the commit now. Kindly check it out

@codeWhizperer running npm run build fails, can you check it out


Is this exporter tested for concurrent workflow executions?

We are using zeebe 8.2.12. We plan to use this exporter to fetch incident details at runtime and also for monitoring/troubleshooting workflow executions.
While going through the code, I came across instance variables declared in the exporter class. I wanted to ask if the exporter would work when there are concurrent workflow executions running.
Thanks

Thanks @VonDerBeck for the comments. We recently tried the clickhouse-exporter and it failed during concurrent process executions, hence I posted this just to double check.
On digging further, I see that this repo also includes code for reading the data from redis-streams which is used by zeebe-simple-monitor. We plan to use zeebe-simple-monitor too in our application deployment.
In the reader code (ZeebeRedis) I also see that the reading is done in a single thread.
I am new to redis but we have observed scalability issues with zeebe-hazelcast-exporter which does the same thing hence wanted to understand if you see scalability issues in reading events from redis streams when there are huge number of records exported to redis from zeebe.

Hi @amitonlentra,
you wrote: "In the reader code I also see that the reading is done in a single thread."
That statement is half true and half false and - as of version 0.9.11 - depends on whether you are connecting to a Redis Cluster or not.
Reading from streams is done in ZeebeRedis.readNext().
Please read Using Redis Clusters for a deeper understanding.
In short:

when not using a Redis cluster the connector uses a blocking Multi-key operation to receive events from Redis. This is indeed done in a single thread taking care of all streams at once.
when using a Redis cluster the connector uses multiple connections to read from each stream individually based on the asynchronous connection pool support of Lettuce (the underlying Redis client) - leading to multiple threads, one for each stream.

What's currently not implemented is the optional use of the asynchronous connection pool support of Lettuce in case you do not use a cluster. This could be something to implement in the future. Before doing so I would be interested if the current options are sufficient for your scenario or not.
Performance on the event receiver side - in my opinion - is way more dependent on how fast the receiver is able to process the incoming events (and you're right, multiple threads might help with that). In case of Zeebe Simple Monitor the question is, how fast events can be stored in the database. The main problem with the Hazelcast exporter is that it uses a Ringbuffer! In case of high load combined with slow event receivers this could lead to scenarios where not yet processed events will be overwritten by new ones. Even if like the Hazelcast exporter very much this is nothing I would risk in production. The good thing is that this will not happen with Redis streams.
So just give a start and let me know how this behaves in your environment.
Regards
Gunnar

Thanks @VonDerBeck for the valuable insights.

Before doing so I would be interested if the current options are sufficient for your scenario or not.

Yes this is sufficient. In our scenario we would be deploying a redis cluster through helm. So effectively RedisClusterClient would be executed behind the scenes

The main problem with the Hazelcast exporter is that it uses a Ringbuffer! In case of high load combined with slow event receivers this could lead to scenarios where not yet processed events will be overwritten by new ones.

You have accurately captured the essence. We experienced the same issues when executing a load test with hazelcast and zeeqs. We are hoping we don't face that with redis and zeebe-simple-monitor.

Performance on the event receiver side - in my opinion - is way more dependent on how fast the receiver is able to process the incoming events (and you're right, multiple threads might help with that). In case of Zeebe Simple Monitor the question is, how fast events can be stored in the database.

When going through the zeebe-simple-monitor code I see the application just registers listeners to the RedisConnectionBuilder class of redis-connector for different record types. The listener code then executes create/update operations as necessary. So since the redis stream is read concurrently in a batch form by the connector, I am hoping that the listeners do get called concurrently for different record types.


fix(dipu): Modifies the problem of reusing pytorch _ config _ cuda in tests / pytorch _ config _ muxi

在test/pytorch_config_muxi中手动调用了pytorch_config_cuda中的模块

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.1 out of 2 committers have signed the CLA.:white_check_mark: NeosZhang:x: zyf654321You have signed the CLA already but the status is still pending? Let us recheck it.


[WIP] Election Contract

:white_check_mark: Build AElf <IP_ADDRESS>5 completed (commit https://github.com/AElfProject/AElf/commit/a24b53df82 by @EanCuznaivy)

:white_check_mark: Build AElf <IP_ADDRESS>7 completed (commit https://github.com/AElfProject/AElf/commit/0d85647f47 by @EanCuznaivy)

:white_check_mark: Build AElf <IP_ADDRESS>1 completed (commit https://github.com/AElfProject/AElf/commit/23dfbc92b0 by @EanCuznaivy)

:white_check_mark: Build AElf <IP_ADDRESS>4 completed (commit https://github.com/AElfProject/AElf/commit/0829903c06 by @EanCuznaivy)


Hijack single quote (and update ace again)

This PR updates ACE to 1.2.6 once again. It works around the previously encountered issue #262 (autopairing of single quotes).
I believe that the undesired behaviour was introduced in ajaxorg/ace@b2e85158bcf3e0e72fc6856701052b9594be1a93 on the ace side. A proper fix on the ace side seems to be non-trivial, however just patching ace to never autopair single quotes look like it could be easily done.
To avoid having to fork, build and deploy ace ourselves in the case of the easy fix (or an upstreamed fix if we don't want to wait an indeterminate amount of months for the next ace release), I implemented a workaround in our JavaScript which prevents the autopair behaviour for single quotes by hijacking single quote as a hotkey (see the comments in the workaround).
If it would be acceptable / preferable to build and deploy ace ourselves, I can also send a PR to that regard.
Note that this was tested on an english keyboard layout, where single quote does not require any modifier keys. It would be good if someone with a keyboard layout which requires a modifier key for single quote could test this patch as well.
These changes are deployed at https://dl.timnn.me/54acabe206c95f52/web.html, for anyone to easily try / test them.
Fixes #265.
r? @alexcrichton
cc @bluss, @solson

Awesome, thanks @TimNN!


Failed init TFL interpreter when enabled XNNPACK

System information

IDE: XCode 12.5
Mobile device: iPhone 12 Pro Max
TensorFlow installed: 'TensorFlowLiteObjC' from CocoaPods
TensorFlow version: tried '2.3.0', '2.4.0', and '0.0.1-nightly.20210503'

Describe the current behavior
Whenever enabled XNNPACK, model initiation will fail. (see code snippets below)
Describe the expected behavior
Expected to initiate mode successfully
Standalone code to reproduce the issue
NSError *err = nil;
TFLInterpreterOptions *options = [[TFLInterpreterOptions alloc] init];
options.useXNNPACK = YES;
NSString *modelPath = [[NSBundle mainBundle] pathForResource:@"mymodel" ofType:@"tflite"];
_modelInterpreter = [[TFLInterpreter alloc] initWithModelPath:modelPath options:options error:&err];
where mymodel.tflite is a custom trained model. If set
options.useXNNPACK = NO;
everything will work normally. When XNNPACK is enabled, the init will fail for interpreter. Specifically, it fails at
_interpreter = TfLiteInterpreterCreate(model, cOptions);
inside TFLInterpreter.mm in the framework, and there's no source code to trace further.

@yyoon @multiverse-tf could you take a look?

Hi, Can you make sure you build the XNNPACK with TFLITE_ENABLE_XNNPACK=ON and test the code again.
For details on build, check the document here. Thanks!


Add ctrl-_ undo support

TODO: better pos only changes
TODO: config

This one probably needs some cleanup

Rebased on master and reworked it a bit.
@slingamn what do you think about the approach? i feel like it sprinkle small undo calls a bit to much hmm. Any idea how to make it nicer?
Also this implementation does not behave exactly as gnu readline undo etc but maybe it's close enough?

Thanks for fixing the conflicts on this! I will definitely look at this but I may not have time until April 16th or so.

👍  no hurry!

Sorry I keep introducing conflicts in this :-)
I'm not sure about how important this feature is to end users? Is it something that's important in the fq context? Or is the point more to get to parity with GNU Readline? Unless there's a clear case for it, I'm not sure about including it at this stage.
(I was also considering removing Vim mode, but there seems to be a fair amount of user interest in it, e.g. upstream's #36 and #120).
At a code level this patch seems pretty good except that it increases implementation complexity, and also the size of the undo buffer is unbounded. (I'm thinking about writing a generic expandable ring buffer with a size limit that could replace uses of container/list for history and search, so if I end up doing that, it would be applicable here as well.)

No worries. Don't know how many other use undo, the reason i added it is i'm used to it from other readline implementations. It would of course be nice to not have to maintain my own fork with some addition (only undo i think atm?) but basing it on ergochat/readline would still be a big improvement!

If it's important to fq, then I'll get it merged in this cycle :-)

If it's important to fq, then I'll get it merged in this cycle :-)

That would be great of course 👍 what should be improved before merge, ring buffer? less complex somehow, better way to reset/init undo?
BTW here is draft PR to use ergochat/readline with fq https://github.com/wader/fq/pull/646

@slingamn hey, just curious, any progress on rewrite things to resolve this in a nicer way?

Sorry, work keeps getting in the way, but I'll put it on the list for this weekend.

@slingamn no stress! Did a fq release and tags my forked deps and got thinking of this :)

I promise I haven't forgotten about this :-)

@slingamn no worries :)

Done in #46


CPP 20 flags

Sigh. CPP20 has .u8string and .string not compatible. Apply the flag in a few places we were missing to fix this with the appropriate generator expression

Actually hold off I might want to do this differently

OK f17f5f0 is more like it


Wrong name for cloud-controller-manager in architecture page

This is a Bug Report

Problem: https://kubernetes.io/docs/concepts/architecture/ talks (in the diagram) about a cloud-control-manager. This should be cloud-controller-manager.
Proposed Solution:
Edit the diagram to use the right term.
Page to Update:
https://kubernetes.io/docs/concepts/architecture/

Additional Information:
/language en
/help
/triage accepted

/retitle Wrong name for cloud-controller-manager in architecture page

/priority backlog


Push Notifications

Are there push notifications coded in the app? I can't seem to get them to work.

no for push notifications you should setup firebase along with APNs

I was able to send a notification to all users through the firebase console, but I can't seem to find a way to get it to work peer to peer. Say one user receives a message from another user, but their phone is locked. Nothing happens and there is no notification on their lock screen.

You need to get device token and store in db along with user information. You should also have some logic on backend to send push notification so specific user.


Using Link with getServerSideProps page will be reloaded

Describe the bug
I'm use Link of Next/link and i have a page with getServerSideProps.
When click page not reload => as well
Then i config with myapp.com/lng/news
At right i change Link's Next to Link of i18n
Then i click into it news will be reloaded.
I cannot understand how to reload -.-.
Thank you so much

This is way too less information to be able to help.


Default colors for bash on windows make directories really hard to read

Which operating system does the issue occur on? Windows 10
On windows all directories in bash have the drwxrwxrwx permission, which makes them render in this very low-contrast greenish-yellow on greenish blue. I'm looking into other color schemes but having something higher contrast out of the box would be nice.

You can change the colors in the default configuration file.

Just in case anyone else finds this, my problem wasn't actually the color scheme. My problem was that on Windows, alacritty starts up in Powershell by default. The bash.exe that it executes when I run bash from within alacritty is C:\Windows\System32\bash.exe (which might be the WSL bash? I'm not sure.)
I really wanted to run C:\Program Files\Git\bin\bash.exe which treats NTFS directories as drwxr-xr-x.

You can also set your directory colors by setting the LS_COLORS env variable (you'll probably find plenty of resources for that online).


feat: remove logic that copies py-sc-client

Changes

create_node() can no longer create a node with an identifier. Use ScKeynodes
get_link_content is renamed to get_link_content_data due to name match with py-sc-client
delete_elements removed from kpm this is a copy from client
Tests

There is no releases, I don't know


v13.0.0

13.0.0

added avro support for some specs with the interfaz AvroSpec (not public is used by avro-values proyect)
JsObjSpecBuilder, JsFixedBuilder and JsEnumBuilder to facilitate integration with avro. It
caches specs by name and now is possible to define recursive data types with JsObjSpecs.ofNamedSpec
If spec builder is used to create specs and parsers, the metadata of the spec
can be used for parsing, for example aliases and default values.
added oneOf specs and parsers (JsReader now support set marks and rollback to that marks!)
added JsArray.of(varargs) and JsArray.ofXXX(list)  methods to create arrays from primitives and list of primitives
added map of spec: JsSpecs.mapOfSpec(JsSpec spec)
added array of spec: JsSpecs.arrayOfSpec(JsSpec spec)
Refactor public classes:

JsObjSpecParser.of and JsArraySpecParser.of instead of constructors
JsReader visibility change (is not public)
JsSpec.readNextValue(JsReader) -> JsSpec.parse(String). Method used by jio-console and was changed
since it not necessary to create a JsReader
reduce methods doesn't return Optional (implementation inefficient since create a lot of Optional objects)
JsSerializerException move to spec package to reduce visibility of constructors

Refactor internal classes and tests (clients not affected)
decimal specs like JsSpecs.decimal can parse any kind of numeric values (integers as well)
Removed JsSpecs.number and related specs like arrayOfNumbers  (use decimal instead)
Added JsDoubleSpec and other related specs (JsSpecs.arrayOfDouble and others related)
Removed automatic module name. I'll keep unnamed json-values because of split packages are
not allowed in the module system and then there is a problem with avro-spec and all the libraries
that defined the package jsonvalues.spec (already defined in json-values)

13.0.0

added avro support for some specs with the interfaz AvroSpec (not public is used by avro-values proyect)
JsObjSpecBuilder, JsFixedBuilder and JsEnumBuilder to facilitate integration with avro. It
caches specs by name and now is possible to define recursive data types with JsObjSpecs.ofNamedSpec
If spec builder is used to create specs and parsers, the metadata of the spec
can be used for parsing, for example aliases and default values.
added oneOf specs and parsers (JsReader now support set marks and rollback to that marks!)
added JsArray.of(varargs) and JsArray.ofXXX(list)  methods to create arrays from primitives and list of primitives
added map of spec: JsSpecs.mapOfSpec(JsSpec spec)
added array of spec: JsSpecs.arrayOfSpec(JsSpec spec)
Refactor public classes:

JsObjSpecParser.of and JsArraySpecParser.of instead of constructors
JsReader visibility change (is not public)
JsSpec.readNextValue(JsReader) -> JsSpec.parse(String). Method used by jio-console and was changed
since it not necessary to create a JsReader
reduce methods doesn't return Optional (implementation inefficient since create a lot of Optional objects)
JsSerializerException move to spec package to reduce visibility of constructors

Refactor internal classes and tests (clients not affected)
decimal specs like JsSpecs.decimal can parse any kind of numeric values (integers as well)
Removed JsSpecs.number and related specs like arrayOfNumbers  (use decimal instead)
Added JsDoubleSpec and other related specs (JsSpecs.arrayOfDouble and others related)
Removed automatic module name. I'll keep unnamed json-values because of split packages are
not allowed in the module system and then there is a problem with avro-spec and all the libraries
that defined the package jsonvalues.spec (already defined in json-values)


[Doc] [SqlPackage Publish] Unclear documentation for some properties

Some properties description are unclear / not detailed enough for me:

RegisterDataTierApplication: What is the  purpose of this registration ? How can we see this registration in a database ?
DatabaseMaximumSize: Does this applies only when loading data of both when loading schema only and schema+data ? How is computed the actual size of the database ? is it size of dacpac file, size of target database, something else ? When is this check done (before any change to the target database, just before data stage ?)
DoNotEvaluateSqlCmdVariables: bad wording / rephrase
GenerateSmartDefaults: what are defaults values used ?

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

ID: c457408b-20fb-a617-0bb0-0e73d4f703c5
Version Independent ID: 9a420183-7d44-3d71-1eba-f66bb757bb65
Content: SqlPackage Publish - SQL Server
Content Source: docs/tools/sqlpackage/sqlpackage-publish.md
Product: sql
Technology: tools-other
GitHub Login: @dzsquared
Microsoft Alias: drskwier

@pierrejeandev -- thank you for your feedback.  Please consider these resources:

SQL Server on Microsoft Q&A
DBA Stack Exchange
Stack Overflow

@dzsquared -- please look into this issue.

@pierrejeandev We are closing this issue because we are tracking it internally.
You can also engage with the engineering team directly at https://github.com/microsoft/dacfx.
AB#203362


Improve error handling support

Thanks for this module.
Right now I don't see any docs or test around error handling.
From what I understand, Amazon will return XML in case of an error and this module will pass that through to the user.
I think it would be more node-ish is module parsed the XML and returned JSON instead. No matter the error handling behavior, some tests and docs to clarify what's happening with error handling would be welcome, especially since the SES REST API returns errors as XML.

@markstos Are you parsing the XML errors yourself, or how are you handling them in general (like for determining how your application should respond)?

@rightaway Right now I use node-ses instead of this module, which uses xml2js to convert Amazon's XML resposnes to JavaScript objects.  It's simple and pleasant to use. I was evaluating this module as a replacement, but currently have no problems with node-ses as a solution.


我看到Speech to Text api 可以返回文本的start和end，请问一下Text to Speech api是否也可以返回start和end呢？

Self Checks

[X] I have thoroughly reviewed the project documentation (installation, training, inference) but couldn't find any relevant information that meets my needs. English 中文 日本語 Portuguese (Brazil)
[X] I have searched for existing issues search for existing issues, including closed ones.
[X] I confirm that I am using English to submit this report (我已阅读并同意 Language Policy).
[X] [FOR CHINESE USERS] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:）
[X] Please do not modify this template :) and fill in all the required fields.

1. Is this request related to a challenge you're experiencing? Tell us your story.
我看到Speech to Text api 可以返回start和end，请问一下Text to Speech 是否也可以返回呢

2. What is your suggested solution?
Text to Speech 也可以返回start和end
3. Additional context or comments
No response
4. Can you help us with this feature?

[X] I am interested in contributing to this feature.

同问，这个挺重要，尤其是一些基础功能如标定口播字幕等

火山引擎返回的json, 如果能返回类似结构,处理字幕时会很方便.

FeHelper-20241203114555.json

Currently we don't support this feature.
Beseides, the issue will be closed beacuse it conflict our language policy.


Add version number to package section of Cargo.toml to fix issue #2833

Fix for Issue #2833.
This adds a version number to the [package] section of the Cargo.toml, which resolves the issue.
Admittedly, not the best solution, given that the version number there and in the [workspace] section will have to be kept in sync. I looked around for a better one and couldn't find it, but I'm very open to suggestions.

Thanks! This works but we should really just be fixing manganis to not panic on missing version numbers :-)


mediainfo: 18.03 -> 18.03.1

Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools.
This update was made based on information from https://repology.org/metapackage/mediainfo/versions.
These checks were done:

built on NixOS
ran ‘/nix/store/jw7xbadzlavx5k13ij9686f8cyylbhyz-mediainfo-18.03.1/bin/mediainfo -h’ got 0 exit code
ran ‘/nix/store/jw7xbadzlavx5k13ij9686f8cyylbhyz-mediainfo-18.03.1/bin/mediainfo --help’ got 0 exit code
ran ‘/nix/store/jw7xbadzlavx5k13ij9686f8cyylbhyz-mediainfo-18.03.1/bin/mediainfo --version’ and found version 18.03.1
found 18.03.1 with grep in /nix/store/jw7xbadzlavx5k13ij9686f8cyylbhyz-mediainfo-18.03.1
directory tree listing: https://gist.github.com/1f4582abcedfafe5a1c8e26b5a4af4f9

cc @devhell for review

Success on x86_64-linux (full log)
Attempted: mediainfo
Partial log (click to expand)
make[1]: Nothing to be done for 'install-data-am'.
make[1]: Leaving directory '/build/MediaInfo/Project/GNU/CLI'
post-installation fixup
shrinking RPATHs of ELF executables and libraries in /nix/store/jw7xbadzlavx5k13ij9686f8cyylbhyz-mediainfo-18.03.1
shrinking /nix/store/jw7xbadzlavx5k13ij9686f8cyylbhyz-mediainfo-18.03.1/bin/mediainfo
strip is /nix/store/j75dgadrff2d1fyc4fczmcgqkid2imdx-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/jw7xbadzlavx5k13ij9686f8cyylbhyz-mediainfo-18.03.1/bin
patching script interpreter paths in /nix/store/jw7xbadzlavx5k13ij9686f8cyylbhyz-mediainfo-18.03.1
checking for references to /build in /nix/store/jw7xbadzlavx5k13ij9686f8cyylbhyz-mediainfo-18.03.1...
/nix/store/jw7xbadzlavx5k13ij9686f8cyylbhyz-mediainfo-18.03.1

Success on x86_64-darwin (full log)
Attempted: mediainfo
Partial log (click to expand)
 /nix/store/5lkrw9dnsgy62qm1ampvww1c5n1pdm4b-coreutils-8.29/bin/mkdir -p '/nix/store/6vsp3zk6lnz1m541ak78rggp5m9z2sby-mediainfo-18.03.1/bin'
  /nix/store/r8bx3qf1bpncb14i9gzma4vr089pc3pv-bash-4.4-p19/bin/bash ./libtool   --mode=install /nix/store/5lkrw9dnsgy62qm1ampvww1c5n1pdm4b-coreutils-8.29/bin/install -c mediainfo '/nix/store/6vsp3zk6lnz1m541ak78rggp5m9z2sby-mediainfo-18.03.1/bin'
libtool: install: /nix/store/5lkrw9dnsgy62qm1ampvww1c5n1pdm4b-coreutils-8.29/bin/install -c mediainfo /nix/store/6vsp3zk6lnz1m541ak78rggp5m9z2sby-mediainfo-18.03.1/bin/mediainfo
make[1]: Nothing to be done for 'install-data-am'.
make[1]: Leaving directory '/private/tmp/nix-build-mediainfo-18.03.1.drv-0/MediaInfo/Project/GNU/CLI'
post-installation fixup
strip is /nix/store/kdff2gim6417493yha769kh00n63lnrw-cctools-binutils-darwin/bin/strip
stripping (with command strip and flags -S) in /nix/store/6vsp3zk6lnz1m541ak78rggp5m9z2sby-mediainfo-18.03.1/bin
patching script interpreter paths in /nix/store/6vsp3zk6lnz1m541ak78rggp5m9z2sby-mediainfo-18.03.1
/nix/store/6vsp3zk6lnz1m541ak78rggp5m9z2sby-mediainfo-18.03.1

Success on aarch64-linux (full log)
Attempted: mediainfo
Partial log (click to expand)
make[1]: Nothing to be done for 'install-data-am'.
make[1]: Leaving directory '/build/MediaInfo/Project/GNU/CLI'
post-installation fixup
shrinking RPATHs of ELF executables and libraries in /nix/store/dvic2vv7f0hia0f0hswqzijr2ripzwzj-mediainfo-18.03.1
shrinking /nix/store/dvic2vv7f0hia0f0hswqzijr2ripzwzj-mediainfo-18.03.1/bin/mediainfo
strip is /nix/store/j7d4mr0ikv974ig7yzhknpsq288js4bs-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/dvic2vv7f0hia0f0hswqzijr2ripzwzj-mediainfo-18.03.1/bin
patching script interpreter paths in /nix/store/dvic2vv7f0hia0f0hswqzijr2ripzwzj-mediainfo-18.03.1
checking for references to /build in /nix/store/dvic2vv7f0hia0f0hswqzijr2ripzwzj-mediainfo-18.03.1...
/nix/store/dvic2vv7f0hia0f0hswqzijr2ripzwzj-mediainfo-18.03.1


Switch the default branch to v3/master

v3/master is the place where most of the code is being done, therefore it makes sense to make it the default branch. Also it has a more fancy and modern looking landing page.

Done!


Demo plugin(s)

Right now examples/BlueprintPlugin is half-implemented and doesn't prioritize communicating how to work with the available features. I'd like to put some time into making this more along the lines of a JuceDemoPlugin that shows off what's available and how to use it.
I'll also leave this task open ended for additional demo ideas

Merging #125 here: let this task represent generally adding more and better demos and examples


Upping this timeout as well for Cypress tests

Description
There appear to be smoke test timeouts failing after a 30 second wait. Upping the request timeout to 45 seconds (in a previous PR, the command timeout was increased to 45 seconds).
Issue
A link to a github issue or SEAB- ticket (using that as a prefix)
Please make sure that you've checked the following before submitting your pull request. Thanks!

[ ] Check that your code compiles by running npm run build
[ ] If this is the first time you're submitting a PR or even if you just need a refresher, consider reviewing our style guide
[ ] Do not bypass Angular sanitization (bypassSecurityTrustHtml, etc.), or justify why you need to do so
[ ] If displaying markdown, use the markdown-wrapper component, which does extra sanitization
[ ] Do not use cookies, although this may change in the future
[ ] Run npm audit and ensure you are not introducing new vulnerabilities
[ ] Do due diligence on new 3rd party libraries, checking for CVEs
[ ] Don't allow user-uploaded images to be served from the Dockstore domain

I don't like this trend but I guess there's no other option.

Agreed, on both points. Not sure of other better approaches. If this continues to occur, I'll create a ticket to investigate what calls are taking the most time, which may give us opportunities to improve efficiency.


GitHub authentication

Issue Type: Bug
OS: Amazon Linux virtual desktop
Browser: Mozilla Firefox
When trying to authenticate GitHub using the sign-in on browser feature I am unable to authenticate. I get to the "You are being redirected to the authorized application..." page and nothing happens. In the line "If your browser does not redirect you back, please click here to continue..." the 'click here' link does nothing. If I try to sign on by typing my GitHub username and token into the command palette the "signing into GitHub" notification just spins for a minute or so then cancels.
I am signed into GitHub in the terminal, where my PAT for this machine works fine.
VS Code version: Code 1.66.2 (dfd34e8260c270da74b5c2d86d61aee4b6d56977, 2022-04-11T07:49:24.808Z)
OS version: Linux x64 4.14.275-207.503.amzn2.x86_64
Restricted Mode: No

System Info

Item
Value

CPUs
Intel(R) Xeon(R) Platinum 8259CL CPU @ 2.50GHz (2 x 2499)

GPU Status
2d_canvas: unavailable_softwarecanvas_oop_rasterization: disabled_offdirect_rendering_display_compositor: disabled_off_okgpu_compositing: disabled_softwaremultiple_raster_threads: disabled_offoop_rasterization: disabled_offopengl: disabled_offrasterization: disabled_softwareraw_draw: disabled_off_okskia_renderer: enabled_onvideo_decode: disabled_softwarevideo_encode: disabled_softwarevulkan: disabled_offwebgl: unavailable_softwarewebgl2: unavailable_software

Load (avg)
2, 1, 0

Memory (System)
3.79GB (0.48GB free)

Process Argv
. --crash-reporter-id f3a5e405-ce50-429e-9dd2-cae07d024289

Screen Reader
no

VM
0%

DESKTOP_SESSION
mate

XDG_CURRENT_DESKTOP
MATE

XDG_SESSION_DESKTOP
undefined

XDG_SESSION_TYPE
undefined

Extensions (2)

Extension
Author (truncated)
Version

go
gol
0.32.0

cpptools
ms-
1.9.8

A/B Experiments
vsliv368cf:30146710
vsreu685:30147344
python383cf:30185419
vspor879:30202332
vspor708:30202333
vspor363:30204092
pythonvspyl392:30443607
pythontb:30283811
pythonvspyt551:30345470
pythonptprofiler:30281270
vshan820:30294714
vstes263:30335439
pythondataviewer:30285071
vscod805cf:30301675
pythonvspyt200:30340761
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
vsaa593:30376534
vsc1dst:30438360
pythonvs932:30410667
wslgetstarted:30449410
pythonvsnew555:30457759
vscscmwlcmt:30465135
cppdebugcf:30475217

/duplicate https://github.com/microsoft/vscode/issues/147104

/duplicate #147104 (comment)

The solution you linked does not solve the issue for me

Did you try in Insiders because this hasn't been released to Stable yet (scheduled for early next week)

Using Insiders, I followed the instructions in the linked issue.
Eventually a new prompt came up, asking to authenticate in a different way. I responded "yes", and it gave me a code to submit on GitHub. This worked! Thank you for the help.
Persisting issue (not blocking me -- this is just for your info):
Although I am now logged into GitHub on VS Code, Settings Sync forces authentication a second time. If I do the same method of authentication then it works, but using the default does not work.
Thanks again.

@StevieDicks can you open a new issue about the Settings Sync experience you saw? It'd be great if you could also send screenshots or a gif of the problem as well.


aria2 enabled seems not work

waited for some time and it shows completed but nothing found. The downloading only works when the aria2 is disabled.
Wish I could copy the download addresses manually to use in other downloading tool.

Please first confirm whether you have downloaded aria2, which can be referenced at External-Downloader, and ensure that aria2 is not blocked by your firewall.
As of now, almost no one has reported this issue, and I cannot determine common problems or the specific issue you are currently facing.
If you wish to use a different downloader, please refer to yt-dlp #download-options. You can specify it using the ``--downloader` parameter, and you can configure it to use your specified downloader for each download at Use Configuration.

I confirmed and tested aria2, it's good to normally download but has some error through proxy, maybe that's it.
I checked the --downloader of yt-dlp, ‘Currently supports native, aria2c, avconv, axel, curl, ffmpeg, httpie, wget.’ Well, my favourite downloader is Free Download Manager, and, I'd love to use GUI. May some copy buttons that after the download buttons of the video and audio selection bars works?

Thank you for using and responding.
I have tested several proxies I commonly use on my end, and they all work correctly. Since my GUI is quite simple, it doesn't validate the input values but directly applies them to the parameters of yt-dlp. If execution fails, there might be cases where the functionality becomes ineffective or stops, but in most situations, it fulfills my personal requirements.
FDM is a highly mature tool, and I have previously tried various tools like 3dyd, 4k downloader, and others. However, these tools didn't allow me to use them with the most comfortable workflow. That's why I created the yt-dlp-gui project and tried to give it greater flexibility for others to use in their own ways. If you're willing, please share how we can make it more user-friendly for you, or you can also explore other fully mature projects to see if they meet your needs. :)

I guess it's missing some configuration for aria or something else, but not the GUI.
Maybe I could expect yt-dlp supports FDM in the future. Before that, I can use your GUI to download some short videoes.
Thanx again.


Improve the docs

I am translating gulp docs to Simplified Chinese, and I just find these.
It's all work fine, but it can be more accurate. :P

what"s your name?

Awesome! You should also check out the spanish translation project and see how they did it

@contra Thanks, yes, I will try my best to do it


fix(mac_dispatch): Fixed runner tags to satisfy the need for right architectures

changed runner tags to cover arm64 and x86_64 architectures
removed temporary solution for Mac with arm64 architecture

Tested on successful build - in the macos-13 or macos-latest workflow under the OS info job, there are visible the correct architectures x86_64 or arm64 which are the wheels being built for.

LGTM!


Additional properties on Patient during registration

Fixes #789
Type
Choose one: Feature
Checklist

[x] I have written Unit tests for any new feature(s) and edge cases for bug fixes
[x] I have added any strings visible on UI components to the strings.xml file
[x] I have updated the  CHANGELOG.md file for any notable changes to the codebase
[x] I have run ./gradlew spotlessApply and ./gradlew spotlessCheck to check my code follows the project's style guide
[x] I have built and run the fhircore app to verify my change fixes the issue and/or does not break the app

with #789 now closed, is this still relevant, what issue does this relate to / is it trying to solve?

@maimoonak looks like the switch to pair caused failures here

done with #865


✨ Global site background image

Is your feature request related to a problem? Please describe.
Currently, I can only customize the background color for my site by overriding the css.
Describe the solution you'd like
I would like the ability to use an SVG file to be rendered as a background on the site, similar to:

We could use tools like https://pattern.monster/ to generate these pattern files, for example.
Describe alternatives you've considered
Alternatively, I could look into overriding the appropriate partial for my site, but I think this feature could be helpful to others as well.
Additional context
For reference, this is the site from which I took the screenshot: https://fumio.brightthemes.com/

@mirceanton would it work for you if this is just a matter of being able to load a svg file with the current parameters or are you expecting a different behaviour?

I think that loading an SVG file would be a perfect solution!
That being said, I've just recently move my blog to Jekyll instead of Hugo so I won't be able to test this feature out anymore :(

@mirceanton shame shame shame :P


Can't have a CacheLoaderWriter with a parameterized constructor

Take the code from the Getting Started:
    Class<CacheLoaderWriter<?, ?>> klazz = (Class<CacheLoaderWriter<?, ?>>) (Class) (SampleLoaderWriter.class);

    final Cache<Long, String> writeBehindCache = cacheManager.createCache("writeBehindCache",
        CacheConfigurationBuilder.newCacheConfigurationBuilder()
            .add(new DefaultCacheLoaderWriterConfiguration(klazz)) // <1>
            .add(WriteBehindConfigurationBuilder.newWriteBehindConfiguration() // <2>
                .queueSize(3)// <3>
                .concurrencyLevel(1) // <4>
                .batchSize(3) // <5>
                .enableCoalescing() // <6>
                .retry(2, 1) // <7>
                .rateLimit(2) // <8>
                .delay(1, 1)) // <9>
            .buildConfig(Long.class, String.class));

The way we pass the CacheLoaderWriter doesn't allow us to have a parameterized constructor, only a no-arg one.
See https://groups.google.com/forum/?utm_medium=email&utm_source=footer#!msg/ehcache-dev/XeGxGHv-qSA/b8z8vZZA_RsJ

Is this the kind of thing you were thinking?
final Cache<Long, String> cache = cacheManager.createCache("cache",
    newCacheConfigurationBuilder()
        .add(new DefaultCacheLoaderWriterConfiguration(klazz, "These", "are", "constructor", "arguments"))
        .buildConfig(Long.class, String.class));

Or alternatively at the cache manager level:
CacheManager cacheManager = newCacheManagerBuilder()
    .using(new DefaultCacheLoaderWriterProviderConfiguration()
        .addLoaderFor("writeThroughCache", SampleLoaderWriter.class, "These", "are", "constructor", "arguments"))
    .build(true);

How would I pass something else than a String as a parameter?

or maybe pass a java.util.Properties object like in Ehcache 2 net.sf.ehcache.loader.CacheLoaderFactory ?

Sorry, that wasn't very clear... it would be a var-arg of Object.

Oh of course, sure that sounds fine


Detailed View - Standardize display of Contacts on the Resources tab

On the right side of the Resources tab in the Detailed View the contacts are currently displayed in the order they were entered.  That means for some apps the "Technical Contact" is displayed before the "Management Contact" and for other apps "Management Contact" is shown first.
This a request for consistency between apps.  Always show the contacts in alphabetical order according to contact type.  (So in the example being discussed show the "Management Contact" first.)

contact types are sorted alphabetically by contact type name in the resources view

My test did not sort alphabetically.  It does however correctly group different Contact types together.
How things should be sorted is still a subject of some debate.  See #273.
Let's allow this ticket to proceed since it does fix the groups (but not order) of contacts.

Tested in STG
Contacts are displayed as grouped together. For example, Techs are grouped together under one heading Techs. However, ticket 273 explains the order of the groups.  This ticket is closed.


Union type of exact object types doesn't add refinement based on property only in one of the choices

If this is a bug, please try reproducing using https://flow.org/try/.
Reproducible: https://flow.org/try/#0PTAEAEDMBsHsHcBQBLAtgB1gJwC6gEoCmAhgMZ6RayqgDkWJ5tA3IqbAHYDOepAHqAC8oABQA6CcQ4BPAFxTpASiEA+OsVqJEOaekKgAClXRchoAN4AfRKFAdiqQrNA8syDgHMANDdCloxFxcAHIOTqAA-K7u3oiWAL6glhbWtvaOXM4AglhYxNIAPNGeKj62-oEhYc5ROG6ePgmsbJw8oB6EOADCAUGhGWYi6YSZoDl5hcUeKorZuflFdTFqgmrmvgw4AK5YHHZhXGKoxOhDYar7joqs8c3s3HgAkveD6MajRrAmyquivkXoKR+XpVRyCcz8ERvL6HCp9MJedqdHqVfojKHvMTDSKgADa0JMWLCAF1QM4CYdhlxFIp4sAVIhrlogA
// @flow
import React from 'react';
const cx = (...any:any) => 'a'

type Props = {|
  name: string,
  className: ?string,
|} | {|
  names: Array<string>,
  className: ?string,
|};

const getClassNames = (names: Array<string>): Array<string> => {
  return names.map(name => name);
};

const Icon = (props: Props) => (

);

Error:

18:
                                                                                ^ property `names`. Property not found in
18:
                                                                                ^ object type

The issue here is that there is not yet machinery to add a refinement based on one property only existing in one of the choices of a union type. For now, you have to add a specific tag to distinguish between choices in a union:
// @flow
import React from 'react';
const cx = (...any:any) => 'a'

type Props = {|
  type: "a",
  name: string,
  className: ?string,
|} | {|
  type: "b",
  names: Array<string>,
  className: ?string,
|};

const getClassNames = (names: Array<string>): Array<string> => {
  return names.map(name => name);
};

const Icon = (props: Props) => (

);

Alternately, you can test directly for the presence of the key you want to use.
This has definitely been reported elsewhere and I think I remember a comment that the team was considering adding this type of refinement in a future version.

Here's a simple example:
type A = {isA: true, a: number};
type B = {b: number};

const thing: A | B = {isA: true, a: 1};

if (thing.isA) {
	const num = thing.a;
}

9: 	const num = thing.a;
                      ^ Cannot get `thing.a` because property `a` is missing in `B` [1].
References:
6: const thing: A | B = {isA: true, a: 1};
                    ^ [1]

(Defining B to be type B = {isA: false, b: number}; results in no error.)
If you can't change the types for some reason, you can also work around it by casting to any and then casting to the correct type. (E.g., const num = ((thing: any): A).a in this example.)

Relatedly, seems like you can't use the type switch when destructuring the object:
type A = {| value: string, kind: 'A' |}
type B = {| value: Array<string>, kind: 'B' |}

type Action = A | B

function okay (action: Action) {
  switch (action.kind) {
    case 'A':
      break;
    case 'B':
      console.log('try to map', action.value.map(v => v));
      break;
    default:
      break;
  }
}

function notOkay (action: Action) {
  const {value, kind} = action;
  switch (kind) {
    case 'A':
      break;
    case 'B':
      console.log('try to map', value.map(v => v));
      break;
    default:
      break;
  }
}

https://flow.org/try/#0PQKgBAAgZgNg9gdzCYAoVAXAngBwKZgCCYAvGAN4A+YAbgIYwCueAXGAM4YBOAlgHYBzADRgA1vwAmbAOSFpYSgF9MuAgCFSFavSasiXLnSwAeTr0EA+EeL5Sw0tfKXps+IgGMMPOH03FqauhQjHye3r5wokZgABR0YT5shAl8AJQUqGAcCDwY7gAWsfFePgB0NhLp5JlZYO507ASy0iw1tWAARlx4dKIA3G11DU2Ore1Z7j7scDB4pfACMdLcWGAYcGAAtnQ40iLF4aU6zKXbODE0pBa0qakD453dvfe1EnhQdIwwGGPjXT39GrKZSoYKhEq+PhwDAAeSiqziKSSKSqNUmfE4FGOeGskkUmgOPhe7ByeUKMQqqPa9Ua9jkv3a-2egxpIxagwmUxmcwWSxWaw2Zz2tAYJzOFyuNzuHMeAJeWTeHy+PxlTMBWWBQA

Some related issues:
https://github.com/facebook/flow/issues/6146
https://github.com/facebook/flow/issues/6805
https://github.com/facebook/flow/issues/6594
https://github.com/facebook/flow/issues/6408
https://github.com/facebook/flow/issues/5745


utoronto: r-staging, increase size of hub's disk (was full)

I've applied this to staging and ensured the resize worked out.

Going for a self-merge on this to avoid issues about other deploys ending up down-sizing this PVC.

@consideRatio btw, disks can't be resized down in kubernetes, only up. So deployment would just fail, not size the disk down.
Self-merging this is still ok though, as it prevents mystery failed deployment!


Make models optional to return from the model decorator

Make models optional to return from the model decorator.
This should address https://github.com/layerai/sdk/issues/244 by letting users return None from their training runs without impacting Layer successfully finishing a training run and collecting metadata.

Yep, the UI looks good:

Sorry, here's the one without a returned model. Still looks good :

@volkangurel is there a way to log model via logging api? Something like layer.log_model(model) or layer.log(model)?

got my answer its save_model :+1:


screen shot update for f-droid

Please ensure that your pull request meets the following requirements - thanks!

Does not contain merge commits. Rebase instead.
Contains commits with descriptive titles.
New code is written in Kotlin whenever possible.
Follows our existing codestyle (gradlew spotlessCheck to check and gradlew spotlessApply to format your source code; will be checked by CI).
Does not break any unit tests (gradlew testDebugUnitTest; will be checked by CI).
Uses a descriptive title; don't put issue numbers in there.
Contains a reference to the issue that it fixes (e.g. Closes #XXX or Fixes #XXX) in the body text.
For cosmetic changes add one or multiple images, if possible.

Finally, please replace this template text with a description of the change and additional context if necessary.

Do we want to keep the old tablet screenshots (in sevenInchScreenshots and tenInchScreenshots) or remove them?

I think we can remove them for consistency, it doesn't look like they are shown in f-droid.


Add GROM token

Hi @AndreyTischenko77  - There is a new requirement that the logo has to be in SVG format. Can I ask you to add it as a replacement for the PNG one? Thanks

Yes I can


Tooltip calendar text overflows

Hi, after fixing my calendar configuration that was broken with version 0.9.18, I configured the year/month toggleable calendar - very useful.
However, the year calendar has some unexpected text overflow which breaks the formatting. This is how it looks on openSUSE Tumbleweed:

This is the configuration that results in the above screenshot:
     "clock#date": {
        "format": "{:%F %a}",
        "smooth-scrolling-threshold": 4,
        "tooltip-format": "<tt>{calendar}</tt>",
        "calendar": {
            "mode-mon-col"      : 4,
            "weeks-pos"         : "left",
            "on-scroll"         : 1,
            "on-click-right"    : "mode",
            "format": {
                "months":    "{}",
                "weeks":    "{}",
                "weekdays": "{}",
                "today":    "{}"
            }
        },
        "actions": {
            "on-click-right"    : "mode",
            "on-scroll-up"      : "shift_up",
            "on-scroll-down"    : "shift_down"
        },
        "tooltip": true
    },

Is there something wrong with the configuration here or the css? Or is there a problem in the calendar with how text is split into a new line?

Try to reduce mode-mon-col or, for test purposes, move clock to the center of waybar just to check

The issue seems to me here with GTK Label Tooltip. I didn't find any API's which can help to increase the tooltip width.
I'll create an issue to upstream once I have a time

Upstream issue raised: GTK Label Tooltip

Thanks for raising the upstream issue.

Upd: @FilippoBonazziSUSE here is new cava module you might be interested in. See an example

How is this related?

I've waybar running on Arch Linux but installed directly from github, no pacman, except dependencies.
My calendar window continues misconfigured. Someone has find how to solve that issue?
I am not sure if it has any kind of relationship with the fonts, since it doesn't recognize the calendar icon, but all other icons of the other modules.
Thanks in advance.

Change the columns to 2 in "mode-mon-col" solves the issue, but it looks very small

Hi, this is still broken, any chance this can be fixed?

Hi @FilippoBonazziSUSE , unfortunately not any news from the gtk upstream GTK3. Label tooltip shifted text

Okay, so, this is a very simple hack, but it works pretty well, and doesn't require font sizing shenanigans:
        "clock#date": {
            "rotate": 0,
            "format-alt": "{:%Y/%m/%d}",
            "format": "{:%b %d, %Y}",
            // To set calendar width, write out the entire length of an entire line in the calendar:
            // `10 11 12 13 14 15 16 W00   10 11 12 13 14 15 16 W00   10 11 12 13 14 15 16 W00   10 11 12 13 14 15 16 W00`
            // Then replace every character in that line with a space:
            // `                                                                                `
            // Then take that space, and put it before or after (or both) of `{calendar}` with a newline (`\n`) between that empty line and the `{calendar}`.
            // For best results, probably both? Then also limit the amount of padding-top and/or padding-bottom in the `tooltip label` css.
            // Example:            10 11 12 13 14 15 16 W00   10 11 12 13 14 15 16 W00   10 11 12 13 14 15 16 W00   10 11 12 13 14 15 16 W00
            "tooltip-format": "<tt>                                                                                \n{calendar}</tt>",
            "calendar": {
              "mode"          : "year",
              "mode-mon-col"  : 4,
              "weeks-pos": "right",
              "on-scroll"     : 1,
              "format": {
                "months":     "{}",
                "days":       "{}",
                "weeks":      "W{}",
                "weekdays":   "{}",
                "today":      "{}"
              }
            },
            "interval": 1
        },

Proof:

Hi there. there is merge request which should solve an issue. In the same time it created an issue and discussion in Gnome comunity:

Gnome Issue#5900
Gnome discussion

Finally according this discussion

Gnome discussion
solution is found and #3255 is ready to merge

According to the gtk maintainer's mention tooltip for GtkLabel has limitations.  So, this MR  fixes the issue without any additional actions from the user side.

Hi @FilippoBonazziSUSE,
Can you please check the issue once again in new 0.10.4 Waybar ?


Update pm5

Update pm5

Noted.

Here you go my boi https://github.com/MCPEAbdu77/AutoSellPE/tree/PM5


Add upm header files directory

Signed-off-by: Eugene Bolshakov<EMAIL_ADDRESS>

Merged, thank you!


Update to use forgeapi.puppetlabs.com and API v3

I'm running librarian-puppet 1.0.1 and Puppet 3.6.0-rc1 (the git tag, currently unreleased), but am hitting problems with the migration from forge.puppetlabs.com to forgeapi.puppetlabs.com, and the v1 to v3 API switch.

In the same vein as bd29b9fb, the client_api_version method should return v3 for Puppet 3.6 or higher.
Changing the Forge URL in Puppetfile to https://forgeapi.puppetlabs.com fails too, as librarian-puppet tries to query https://forgeapi.puppetlabs.com/api/v1/releases.json?module=puppetlabs/mysql.  The /api prefix needs removing.

Any thoughts on the best way to implement part (2)?  Forcing users to add /api to their existing Forge URLs would be incompatible, so perhaps detecting the URL is best and then adding/removing /api as applicable...  Or perhaps if Puppet Labs redirected /api to / on forgeapi.pl.com, compatibility could be maintained and in future, the path should be added to the Forge URL in the Puppetfile.  (@ryanycoleman)

Is there any reason to stay on v1? Should v3 be made the default at some point, and when would be the time to consider that change?


difference of methods

Hello,
I am not familiar with these different methods, for a helpdesk which method do you recommend me to go?

Hi,
I did some tests and according to them the best is Fisher-Robinson's Inverse Chi-Square Test method. To test it I used Enron emails database.
Below are results


Update how-to-enable-private-link.md

Cross-tenant scenarios are not supported by ADT.

@baanders
Can you review the proposed changes?
Important: When the changes are ready for publication, adding a #sign-off comment is the best way to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team


[5.0] Passing names to several controllers

Currently router allows to pass names as third attribute $router->controller('foo', 'Foo', ['getIndex' => 'index']); but this feature is not available when passing several controllers.
This fix allows to pass complex structures to controllers method
$router->controllers([
    'foo' => 'FooController',
    'bar' => [
        'uses' => 'BarController',
        'names' => [
            'getIndex' => 'bar.index',
            'postSave' => 'bar.save',
        ]
    ],
]);

The fix does not break any compatibilities.
Tests provided.

:+1:

Is this a breaking change?

@taylorotwell

The fix does not break any compatibilities.
Tests provided.

I suggest just using the Route::controller method.


Flattening empty variants (to null) within an array produces excessive indentation in the output string

(LabVIEW 2013 SP1 + JKI JSON Serialization v<IP_ADDRESS>)
Suppose I provide this JSON string:
[
    "Hello",
    42,
    false,
    null,
    {
        "nested?": true
    }
]

Unflattening and then re-flattening it (with Multiline==TRUE) produces
[
    "Hello",
    42,
    false,
        null,
    {
        "nested?":true
    }
]

Notice that the "null" has too much indentation.

Fixed in 1.0.5


chore(ci): avoid double-zip in build previews; update action

Context

Closes https://github.com/interledger/web-monetization-extension/pull/183
Done during pair-programming
Changes proposed in this pull request

Extension builds preview

Name
Link

Latest commit
d297cc83b36a1b8a40277849b644f52b44f20a26

Latest job logs
Run #10467325168

DownloadDownload


[MINOR] [SQL] Removes an unreachable case clause

This case clause is already covered by the one above, and generates a compilation warning.

Merged build triggered.

Merged build started.

Test build #32923 has started for   PR 6214 at commit c38ca7c.

lgtm

Test build #32923 has finished for   PR 6214 at commit c38ca7c.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/32923/
Test PASSed.


Recommendation to delete all the rules and enable the audit service to run

On applying Flatcar recommendations as mentioned in  https://www.flatcar.org/docs/latest/setup/security/selinux/ (https://www.flatcar.org/docs/latest/setup/security/selinux/") and running "auditctl -l" is returning "No Rules". And with "no rules" it means audit service will not work by default. Why we have this recommendation to delete all the rules and how we can enable the audit service to run ??

Hi @Akshaybaisla,
it is expected that you provide your own audit rules.
This instructions are the way they are because the default Flatcar audit rules in 99-default.rules contain this entry:
# Ignore everything else.
-a exclude,always -F msgtype>0

which disables all other rules. So you definitely need to remove that one.


Memory Issues

FSWatcher objects seem to not be destroyed when a file is 'unwatched', or when the file is deleted from a watched directory. Is this by design?

I don't think so. Did you have any real problems? We'll need to investigate this.

It is by design in many situations. For a file that's deleted, watching is definitely persisted in case it comes back.
For unwatch it depends on what the watch target was to begin with. Sometimes you're unwatching a subset of what's being watched by a particular underlying watch method.
As @paulmillr said, a more concrete example needs to be provided if you think there is a problem.

Here's the code for the unwatch method: https://github.com/paulmillr/chokidar/blob/ba90462886d0fbb1927f70fe2e7a25a4249b9994/index.js#L430-L448
You can see that it either closes the underlying watch instance if there is one, otherwise it just treats the unwatched path as something to be ignored.
And actually, if your concern is the chokidar FSWatcher instance itself, then yes it is definitely by design that it does not get destroyed because users might want to .add() something else after the unwatch.
If you want to clean up memory, you should use the .close() method.

Ok, this is a misunderstanding on my part because yes the files I am calling unwatch on are still in the top level directory path which I am watching. In this case I'd say the library is working as expected, however would you guys know of a library or way i can watch only a directory tree for adds/deletes, and not care about the actual file changes?

Listen to the add and unlink events only. Ignore the change events.

Yes, but our problem is memory consumption caused by all the FSWatcher objects created because of the number of files in the directory we are watching. Is there a way to tell the library to destroy these for files and only watch directories?

So some numbers: my node process with no files in my watched directory and nothing else happening in the system: ~50,000KB of memory, add in 10,182 files and the memory jumps to 340,160KB of memory, stop the node process and start it back up watching this same directory and the memory is less at 163,180KB but this is still ~16KB of memory per  file being watched!!! Seems very high even for just one FSWatcher object per file. I definitely think there is a memory issue.

What OS are you on, and what settings are you using for chokidar?

Ok, ran with the exact code below:
    var express = require('express');
    var chokidar = require('chokidar');

    var dataWatcher = chokidar.watch('C:/testData', {
        persistent: true,
        ignoreInitial: true
    });

    dataWatcher.on('add', function(file){
        console.log('added file: ' + file);
    });

    var app = express();
    app.listen(8080, function(){console.log('express server running')};

Start up: 23,068KB
Dropped 10,182 files: 155,904KB
Restart: 144,424KB
so ~12KB/file

Also tested to see what the .NET directory watcher used in comparison and it was less than 1KB per file.

The short answer is no, chokidar does not provide an option to skip file-level watching. There may be a way to manipulate chokidar into doing this with some clever glob or ignoring settings, but if you only need to target Windows and only need to watch the one directory (no recursion), it may work out better for you to just use fs.watch directly for this use case.
The memory usage you're observing is likely related to the separate watcher instances per file as you've observed, which is necessary to reliably pick up the file events chokidar is observing (including change), and the fact that an fs.Stat is collected for each entry to differentiate between files and dirs. I've discussed the possibility of improving performance using alternate means of scanning the file tree at https://github.com/thlorenz/readdirp/issues/24, but so far have not been able to spend any time trying to implement that idea.

Thank you for the explanation! Preferably I would like to support both windows and linux and it seems that fs.watch will suffice for this... If I've read fs.watch documentation correctly the problem OS is OS X because it handles file system events differently. Is this correct?

The main issue you're likely to encounter is that the events on a dir-level watcher on OS X won't provide the filename of the impacted file.
There's all sorts of other inconsistencies about fs.watch on any OS (largely the reason chokidar exists), but I haven't ever focused on a use case like yours where you're not interested in change events. Even for add/unlink though, Chokidar has to double-check what the system reports by reading dir contents upon an event being reported.  YMMV
It may be possible to add an option to chokidar that skips the file-level watching and otherwise retains the consistency benefits. If you encounter trouble with fs.watch, let me know if you'd be interested in pursuing this feature.

yeah, def will do. Thanks a lot for the help.


[Event Request] Codeunit::"Whse.-Activity-Register" -RegisterWhseActivityLines

We like to request the following Event:
Object: Codeunit::"Whse.-Activity-Register"
Function: RegisterWhseActivityLines
Publisher Event: OnRegisterWhseActivityLinesOnBeforeValidateQuantityFields
Reason: To implement custom business logic
Where is the event placed:
OnAfterFindWhseActivLine(WarehouseActivityLine);
if "Qty. Outstanding" = "Qty. to Handle" then begin
SkipDelete := false;
OnBeforeWhseActivLineDelete(WarehouseActivityLine, SkipDelete);
if not SkipDelete then
Delete;
end else begin
QtyDiff := "Qty. Outstanding" - "Qty. to Handle";
QtyBaseDiff := "Qty. Outstanding (Base)" - "Qty. to Handle (Base)";
IsHandled := false;
OnRegisterWhseActivityLinesOnBeforeValidateQuantityFields(WarehouseActivityLine, QtyDiff, QtyBaseDiff, HideDialog, IsHandled);
if not IsHandled then begin
Validate("Qty. Outstanding", QtyDiff);
if "Qty. Outstanding (Base)" > QtyBaseDiff then // round off error- qty same, not base qty
"Qty. Outstanding (Base)" := QtyBaseDiff;
[IntegrationEvent(false, false)]
local procedure OnRegisterWhseActivityLinesOnBeforeValidateQuantityFields(var WarehouseActivityLine: Record "Warehouse Activity Line"; var QtyDiff: Decimal; var QtyBaseDiff: Decimal; HideDialog: Boolean; var IsHandled: Boolean)
begin
end;

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. We will update this issue with information about availability.


question about centerhead

Hi,
I noticed that the pointpillar backbone version center point is one stage detection. In this situation, What is the difference between center head and other heads ? I don't really see much difference. Could you explain it from the source code?
class CenterHead(nn.Module):
    def __init__(
        self,
        in_channels=[128,],
        tasks=[],
        dataset='nuscenes',
        weight=0.25,
        code_weights=[],
        common_heads=dict(),
        logger=None,
        init_bias=-2.19,
        share_conv_channel=64,
        num_hm_conv=2,
        dcn_head=False,
    ):

Thank you very much!
:)

In this situation, What is the difference between center head and other heads ? I don't really see much difference

Other previous methods do the detection in anchor-based fashion, which means that they will have predetermined box templates of certain shape / rotation and at certain bev location. In contrast, we use point-based detection to detect objects first as center points and regress other attributes from center features after that which tend to perform better for extremely small / large objects or objects with various rotations.  The main convincing experiment is pedestrian detection on Waymo where any sota anchor-based methods lag behind our method by a large margin.

i know, thanks!


flocker_standard_options decorator should account for required arguments

As described at https://github.com/ClusterHQ/flocker/pull/162/files#r14353724, the flocker_standard_options did not account for required arguments and so some patching was added. This patching should be removed, perhaps by making extra values to pass as additional arguments available to the test case and then passing them.

We are moving our development planning to JIRA. This issue is now being tracked at https://clusterhq.atlassian.net/browse/FLOC-184. You are welcome to file additional issues in GitHub if that's easier for you.


Visual Studio 2019

Please update to work with Visual Studio 2019.  Installation throws an error of a missing requirement:  Microsoft.VisualStudio.Component.CoreEditor.
Thank you!!!!!

I've raised a Pull Request here with a change to allow the Extension to work with Visual Studio 2019.
Hope this helps!

The Pull request here which I think will resolve this has been merged into 'master'.
The Repo author has confirmed here that the changes have been merged.
I think all that remains is to have the latest iteration of this Repo published to the VS Gallery, although I've never done this step so I'm not sure what it involves.
@cskardon, is it possible to have the latest changes for this Extension published to the VS Gallery if the changes meet your approval and this isn't too much trouble?
And many thanks for the work involved in creating this Extension, much appreciated!
Cheers,
Michael

OK, I'm having trouble compiling it atm, which means I can't release it.
I've also gone over the changes I needed to do to go from 2015 to 2017 support - and I suspect (but as of yet don't know) a lot more will need to be changed. As it stands, on my list of 'todos' this is pretty low, but I will happily accept tested PRs that provably work in VS2019.
I'm sorry it's not an ideal response, honestly - atm I'd be looking to re-write it for 2019 I think anyhow. :/


IOS: Application crash on release scheme

Description
I already created a fresh react-native project, and it's working fine on android(debug/release) and ios(debug).
But when i switched to release scheme as described by Facebook docs it crash on startup and throw the following exception:

Make sure the packager is running or you have embedded a JS bundle in your application bundle.unsanitizedScriptURLString:((null)) 2017-01-17 21:59:18.720641 XXXX[332:53718] *** Terminating app due to uncaught exception 'RCTFatalException: No script URL provided.

Any idea about the cause of this issue?!
Additional Information

React Native version: 0.40
Platform: IOS
Operating System: MacOS
Xcode: 8.0

My issue has been solved by generating js bundle.
react-native bundle --dev false --assets-dest ./ios --entry-file index.ios.js --platform ios --bundle-output ios/main.jsbundle

https://stackoverflow.com/questions/43854369/no-bundle-url-present-error-with-react-native-ios-release-mode --> helped me a lot

This should be in the official documentation !!!!


[ignore] use deep copy in services

Counter proposition to #1961.
I'm proposing to make a deep copy of an entity in every services before creating or updating the entity. Like that we ensure that the service can modify the object without modifying the initial reference.
As a side effect it also fixes #1960

@sinkingpoint let me know what do you think about this way


Deprecate HookMap.tap methods

In order to simplify the typings and to clean this package, I propose to remove these redundant methods in the next major version. Meanwhile, they are marked as deprecated.

Thanks


Rendering offset for some WSI formats

Just run the nuclei segmentation pipeline which follows with FP on a local WSI, and observed that the rendered segmentations were off.
This was observed for a WSI stored in the generic TIFF format, on Windows 10, using the latest artifact.
See example below.

Just observed the same using the latest artefact when testing a custom mitosis segmentation model.
I was running a lot of different tests. I could not reproduce this issue on the CellSens VSIs, but for the generic TIFF images, it seems to reproduce quite consistently.

However, I find it strange, as these images were originally stored as .vsi, but converted to .tiff. I believe this used to work before. Not sure what changed. Might also be that the converter stores some spacing data wrong.
There should be some WSIs located on the SINTEF-server you could test:
/mnt/EncryptedPathology/pathology/images_tiff_tz_1024_jpeg_85/T.tif
I observed the same issue using the nuclei segmentation method that is part of the software. If that WSI is not in the path, you could test any of the .tif-files. I believe it should be consistent among those files, but not sure.

This is caused by pixel spacing of segmentation being calculating incorrectly.
We are not able to extract spacing information from the VSI format, that is why it is not occurring on these images.

We are not able to extract spacing information from the VSI format

I'm observing this issue on the TIFF images, not the VSI images. But the TIFF images were originally in the VSI format. The TIFF images are located at:
/mnt/EncryptedPathology/pathology/images_tiff_tz_1024_jpeg_85/
The corresponding VSI images are located at:
/mnt/EncryptedPathology/pathology/images/
on the SINTEF server, if I recall correctly, if you wish to check this further.

Hello,
I have observed the same behavior on .MRXS whole slide images, on Windows, with latest release (v1.1.0), with all segmentation models. I can provide a test image if needed.
Thanks,
Vlad

That's interesting, @vladpopovici! Thanks for reporting it!
@smistad is on vacation now and I am preoccupied with some other deadlines, so we will not be able to look into this until August earliest. Will keep you updated!
Regarding test data, could you reproduce the issue on any of the MXRS files that are part of the OpenSlide test data (see here).

Now that's awkward: on the test data the segmentation mask is spot on! I will take a closer look to see what are the differences in metadata between test images and mine. My images are produced by the scanner software for 3DHistech. Keep you posted. V.

My images are produced by the scanner software for 3DHistech.

Oh, yeah. This we have seen in a separate issue. See issue #13 (or more specifically, see this comment). Basically, the MRXS format produced from the 3DHistech format has been modified, which results in OpenSlide failing to interpret it correctly. This was also talked about thoroughly in this thread.
To get these images to work with non 3DHistech-products, you will need to use the 3D Histech converter tool (see here). Which should resolve this issue, but I have myself never tried it. Could you give it a go to see if it resolves the issue you are experiencing on your local WSI?

I can confirm the observations made by @pr4deepr:
-original .MRXS from 3DHistech scanner is read by FP, but segmentation is shifted;
-.MRXS -> .TIFF converted by 3DHistech software (SlideMaster) results in a file that cannot be read in FP;
-.MRXS -> .MRXS results in a file that can be read in FP, but the segmentation is shifted;
Additionally, I tried .MRXS -> OME-TIFF (with bioformats tools: bioformats2raw + raw2ometiff which results in a file that cannot be read by FP ("level is too large to convert into a FAST image").

The annoying problem is basically that the 3DHistech have corrupted the original MRXS format slightly, meaning that for FP the regular OpenSlide test MRXS files reads as expected, but the one directly for the 3DHistech server does not.

-.MRXS -> .TIFF converted by 3DHistech software (SlideMaster) results in a file that cannot be read in FP;

I believe that is because it does not produce a pyramidal TIFF, which is needed to be read by FP. If you try to open it in QuPath, it will likely open, it might take a while and prompt a warning, as it will try to pyramidize the entire image before reading it.

Additionally, I tried .MRXS -> OME-TIFF (with bioformats tools: bioformats2raw + raw2ometiff which results in a file that cannot be read by FP ("level is too large to convert into a FAST image").

That is related to the previous comment. I would recommend using bioformats + vips instead. That is you first convert the WSI to BigTIFF and then to a pyramidal TIFF. See this example python script on how to do it. Note that I just use two command line tools. Below is a simple example of how to do it:
# original format -> btf
> sh /path/to/bfconvert -tilex 1024 -tiley 1024 -nogroup -no-upgrade -overwrite -bigtiff -series 0 /path/to/original/image.format /path/to/temporary/image.btf

# btf -> pyramidal tif
> vips tiffsave /path/to/temporary/image.btf /path/to/converted/image.tif --bigtiff --tile -pyramid --compression=jpeg --Q=85

See the aforementioned script for more information regarding compression in the first step and bfconvert path.

The bfconvert produces a corrupted image that vips fails to convert afterwards.
But I have used this command, which should be (?) equivalent:
> vips openslideload <file>.mrxs <result_file>.tiff[tile,tile-width=1024,tile-height=1024,compression=jpeg,Q=100,bigtiff,pyramid] --vips-progress
The resulting file is perfectly opened by FP, but the detection mask is, again, shifted. I will have to check in the code to see which meta-parameters are causing this behavior. It's really frustrating... :)

I believe by attempting to convert in another software than 3DHistech's own converter, you will likely still get the offset.
Did you try to use the converter I mentioned previously. Might be that it has been rebranded to slidemaster.

Yes, I tried with SlideMaster - see my attempts above.
Anyhow, I did not see this kind of artifact in other programs analyzing the same images (including QuPath, HALO and my own scripts :) ). I used OpenSlide previously and I was able to correctly align the masks and navigate the images.
I will try digging into the code of FAST library.

I guess this is something that could be addressed in FAST then. We have a similar issue with some other WSI formats, so it should be possible to resolve. However, @smistad is on vacation, so it will have to wait until August.

Hi,
As discussed on https://forum.image.sc/t/nocodeseg-deep-learning-based-segmentation-without-code-qupath-deepmib-fastpathology/60069/10, I have the exact same shifting problem in FAST (via FastPathology).
The WSI file is from 3DHistech, and I attach the openslide properties here: openslide_output.txt
And the shift looks like this:

I can send a test image if needed.
This is a bit blocking for me, as no conversion worked: vips keeps the shift issue, and QuPath makes an OME.TIFF that FAST can not open.

I can send a test image if needed.

Hello, @cavenel! It would be great if you could share an image, such that we could see if we could reproduce the issue. It would also help us in debugging the issue and potentially finding a fix.
If you do not wish to make it open to everyone, you could share the WSI with me at<EMAIL_ADDRESS>

Note that we have resolved similar issues before for a difference image format: https://github.com/AICAN-Research/FAST-Pathology/issues/61#issuecomment-1451966053
Also note that for this exact format, @pr4deep seemed to have managed to resolve this issue for the same 3DHistech MRXS format by converting the format to TIFF using 3DHistech's own converter: https://github.com/AICAN-Research/FAST-Pathology/issues/13#issuecomment-1165029997
@cavenel Could you please check again that you did the conversion correctly. This is also relevant for @vladpopovici (see comment below).

-.MRXS -> .TIFF converted by 3DHistech software (SlideMaster) results in a file that cannot be read in FP;

@vladpopovici I believe the conversion you did here actually fixed it, but you have to convert the image to pyramidal TIFF, not regular TIFF, as FastPathology only works with pyramidal images, in contrast to QuPath that can pyramize the image if necessary.

Hello @andreped @cavenel and @vladpopovici
Sorry for responding so slowly to this.
I have now found the reason for this error.
It was due to a rounding error of the pixel spacing in FAST.
After this fix, the segmentation renders at the correct location.
I will commit a fix to FAST soon, then we will need to rebuild FAST-Pathology with the new fix.
Stay tuned.

@cavenel I just tested the nuclei segmentation model on the data you sent @andreped with the fix, and it renders correctly now.

I can confirm that it looks amazing now!


The operation couldn’t be completed. (LaunchServicesError error 0.)

I run into this error when attempting to start the simulator:
The operation couldn’t be completed. (LaunchServicesError error 0.)
Is this related to the app/example or something I have setup wrong?

I guess you already figured it out but for anyone else:
http://stackoverflow.com/questions/25130558/unable-to-run-app-in-simulator-an-error-was-encountered-while-running-domain

to look system.log of simulator for more error messages.

NO system log or other tips

I also meet this problem ,but there is no system log or other tips in Xcode 7.1

i also get this issue

me too..


Lack of information

There is very little information on RScoin online. And the README.md file isn't really helpful at all

See: http://www0.cs.ucl.ac.uk/staff/G.Danezis/papers/ndss16currencies.pdf.


EditText

Hi, I want to know if there is a way to manage the alignment of the text in the .input parameter.
Thankss

You can do anything with the EditText after a MaterialDialog is built using dialog.getInputEditText().


EDU-1002 Use plyr instead of react-player in video and audio plugins

Closes https://educandu.atlassian.net/browse/EDU-1002
This library also has a few glitches that I have corrected or that we might need to correct (or live with). So far though it seems to be less of a black box compared to react-player and the play/pause toggle seems to be reliable.
Also, all videos can now be played/paused by clicking on the video itself, so we would have consistency between youtube and CDN resources.

Closes https://educandu.atlassian.net/browse/EDU-1002
This library also has a few glitches that I have corrected or that we might need to correct (or live with). So far though it seems to be less of a black box compared to react-player and the play/pause toggle seems to be reliable. Also, all videos can now be played/paused by clicking on the video itself, so we would have consistency between youtube and CDN resources.

Looks good so far, and the code is straight-forward. Of course, this is the most basic case, but I'd say we give it a shot also for the more complex media players. The only thing I stumbled upon is that on the cursor on the video (or poster) is not a hand anymore, so it doesn't look like it could be clicked. But I realized that that's also the case on YouTube itself. So maybe we should leave it that way to be consistent.

Closes https://educandu.atlassian.net/browse/EDU-1002
This library also has a few glitches that I have corrected or that we might need to correct (or live with). So far though it seems to be less of a black box compared to react-player and the play/pause toggle seems to be reliable. Also, all videos can now be played/paused by clicking on the video itself, so we would have consistency between youtube and CDN resources.

Looks good so far, and the code is straight-forward. Of course, this is the most basic case, but I'd say we give it a shot also for the more complex media players. The only thing I stumbled upon is that on the cursor on the video (or poster) is not a hand anymore, so it doesn't look like it could be clicked. But I realized that that's also the case on YouTube itself. So maybe we should leave it that way to be consistent.

I actually had added the hand but removed it for exactly this reason of consistency 🤔 Let's see how this works out then.


why the latest vers is the very -old- 2021 one...??!!!

Checklist

[ ] I'm asking a question
[ ] I've looked through the README and FAQ for similar questions
[ ] I've searched the bugtracker for similar questions including closed ones

Question

WRITE QUESTION HERE hi!, why the latest is the very old 2021 vers....??...it really do not work anymore.....:( is this project ELO...??

dose this mean the project is no more maintained?


Support geo commands in lettuce 3.3

Support commands

geoadd
georadius
georadiusbymember
geoencode
geodecode

in lettuce 3.3

geodist

Added GeoTuple type to represent x,y coordinates. georadius commands return a mixed list of string, double/integer and x,y positions (not GeoTuples) because of the dynamic parameters. A future enhancement could be:

either a parser with model
or methods without the possibility to select withdist, withhash and withcoord but providing a nice data structure containing all with details.


Added unsafe.Pointer as a key type

Gives the ability to store a pointer in the map, which the garbage collector will keep alive

Nice job! What do you think about to merge an additional impovement from this separate issue (since you are changing hashable)? :)


Move samples queries file into blob storage

The SamplesQueries.json file is currently stored in a folder directory. The problem with this is:

Updating the web app will overwrite any changes made to the SamplesQueries.json
If we decide to scale out, we will have two copies of the file.
We need to support localization of these resources, so some refactoring/normalization of this data is needed.

This file needs to be moved to an Azure blob storage.

Part of AB#4592


Ensure all managed resources have external names

Description of your changes

In attempting to make provider-aws pass the https://github.com/crossplane/conformance test suite I noticed that three of our managed resources don't expose an external name annotation, which we require. These resources are all somewhat tricky in that they don't have their own obvious identity but are instead bindings between other resources (e.g. an IAM user and a group), so I've set external names that combine the identity of the two bound resources - e.g. group/user.
This PR also fixes https://github.com/crossplane/provider-aws/issues/726.
I have:

[x] Read and followed Crossplane's contribution process.
[x] Run make reviewable test to ensure this PR is ready for review.

How has this code been tested

I've built the provider, applied the relevant examples from the examples/ directory and ensured they resources become healthy and set their external names appropriately.

This is superceded by https://github.com/crossplane/provider-aws/pull/728.


Add docs on how to build docs

After a question on the mailing list about how to build the docs, I thought it was worth documenting for future reference.
This is how I have been building the docs. Hopefully it is how the docs are supposed to be built.

Looks Thanks, @timheap!
P.S.: I like the commit message :+1:

I used your docs to build the docs about building docs, and now I can read the docs about building docs...
Merged in 84432fbfd6e27792a27b99a563b60f10e960d271.

😷😷😷
(actually 'Face With Medical Mask', intended for discussions about bird flu, but the closest I could find to 'docs'.)


Text alpha broken in 0.57.2 on Android

[x] Review the documentation: https://facebook.github.io/react-native
[x] Search for existing issues: https://github.com/facebook/react-native/issues
[x] Use the latest React Native release: https://github.com/facebook/react-native/releases

Environment
Run react-native info in your terminal and paste its contents here.
  React Native Environment Info:
    System:
      OS: Linux 4.15 Ubuntu 16.04.5 LTS (Xenial Xerus)
      CPU: x64 Intel(R) Core(TM) i7-7700 CPU @ 3.60GHz
      Memory: 709.84 MB / 15.54 GB
      Shell: 4.3.48 - /bin/bash
    Binaries:
      Node: 8.11.0 - ~/.nvm/versions/node/v8.11.0/bin/node
      Yarn: 1.10.1 - /usr/bin/yarn
      npm: 5.6.0 - ~/.nvm/versions/node/v8.11.0/bin/npm
      Watchman: 4.9.0 - /usr/local/bin/watchman
    SDKs:
      Android SDK:
        Build Tools: 23.0.1, 26.0.1, 26.0.2, 26.0.3, 27.0.0, 27.0.3
        API Levels: 16, 19, 22, 23, 26, 27, 28
    IDEs:
      Android Studio: 3.1 AI-173.4907809
    npmPackages:
      react: 16.5.0 => 16.5.0
      react-native: 0.57.2 => 0.57.2
    npmGlobalPackages:
      create-react-native-app: 1.0.0
      react-native-cli: 2.0.1
      react-native-create-library: 3.1.2
      react-native-git-upgrade: 0.2.7

Description
Describe your issue in detail. Include screenshots if needed. If this is a regression, let us know.
This is a regression, previously text with colour containing an alpha value would be displayed correctly, now it looks (visually) like the alpha was blended on a dark or black background.
e.g. View with a blue background and rgba(255,255,255,0.2) text on it - the text would display as a light blue. Now it displays as a shade of dark grey (or lighter grey depending on alpha value).

0.57.1
0.57.2

Reproducible Demo
Let us know how to reproduce the issue. Include a code sample, share a project, or     share an app that reproduces the issue using https://snack.expo.io/. Please follow the guidelines for providing a MCVE: https://stackoverflow.com/help/mcve
https://github.com/mjmasn/TextAlpha0571 (0.57.1 - working)
https://github.com/mjmasn/TextAlpha0572 (0.57.2 - broken)

Uhm this is a weird one 🤔
Do you have any idea which commit of the ones cherry picked (you can check the commit history here) could have caused this?
The only one that seem somewhat related is https://github.com/facebook/react-native/commit/65e4e674fca7127fd7800ae011cab449561f475b
But I'm not sure why it should affect your code.

@kelset that was my first thought but gut feeling now is it could be https://github.com/facebook/react-native/commit/b7ba2255df109b9cb8999d0e1584bc2b95a4e07c (which would be a shame as that's a great method for overlaying text on images without a 'scrim'). I'm wondering if maybe a shadow with 0 radius is always displaying under the text even if one is not specified?
I will try to get set up for building from source soon so I can be a bit more helpful in these situations :smile:

ah nice catch, it could very well be!
Can you try to revert the change locally and let me know if it fixes it?

@kelset actually yeah, setting textShadowColor: '#2222ee', in styles.welcome seems to fix the problem, so I guess that's a decent workaround for now, just set textShadowColor to backgroundColor value.

It seems like that commit causes text shadows to be enabled by default. (ReactBaseTextShadowNode.java#L261).
Can't you disable them by setting textShadowRadius: 0 in the style instead of setting the textShadowColor?

@idk-whatever yep that works and is a much easier workaround, thanks :+1:

Worth mentioning that all text now looks slightly bloated even without the alpha, I guess the shadow is peeking out around the edges slightly...

Uhm understood - @yungsters should we consider reverting the cherry pick in 0.57.3? I feel like potentially the fix is easy so not sure which approach should be better 🤔

@kelsey One of our beloved release engineers at Facebook used to say… if you’re going to be around to fix it, do whatever you want.
Let’s fix forward if the fix is easy. :)

Any workarounds for this? For the moment, all texts are blurry in our app.

@Batistleman you need to add textShadowRadius: 0 to the styles on any <Text /> node (and <Icon /> if you're using react-native-vector-icons as that uses <Text /> under the hood).
Bit of a pain if you have a large app... For a slightly quicker way we ended up creating two new components, also called Text and Icon then in the render function for those is just render a RN Text or RNVI Icon with textShadowRadius: 0. We then had to update every import {Text} from 'react-native' to point to the new component, but at least we didn't have to update every single style or use of <Text /> in every file...
Off the top of my head something like this should work:
// Text.js
import react from 'react';
import {Text} from 'react-native';

export default function Text(props) {
  const {style} = props;
  return <Text {...props} style={[{textShadowRadius: 0}, ...(Array.isArray(style) ? style : [style])]} />;
}

"react-native": "0.57.3",
升级成0.57.3之后所有文字变成粗体了 显得很臃肿

Bumped into this as well.
Temporary workaround is to put following snippet in the constructor of your main App.js:
if (Platform.OS === 'android') {
  const oldRender = Text.render;
  Text.render = function render(...args) {
    const origin = oldRender.call(this, ...args);
    return React.cloneElement(origin, {
      style: [origin.props.style, { textShadowRadius: 0 }],
    });
  };
}

This will put textShadowRadius: 0 on all Text components rendered in your app.

I think that this commit that landed 3 days ago may be the solution https://github.com/facebook/react-native/commit/fd78eee11b71799aa7fa57bbd70d59c6c642c3b3

@kelset It's fixed for me in v0.57.8


Enables modals to work with components

Adds an initial attempt to set the controller to a template. If the lookup returns undefined, then the controller is set in the usual way.
Components can be used as modal interfaces:
@send('openModal', 'path/to/component-name', { some_public_interface_property: 'value', closeModal: 'closeModal' } )

In the component handle and send closeModal action:
actions:
 closeModal: ->
   @sendAction('closeModal')

+1 on this

There is a little bit more work to be done. It looks like we also need to merge the optional properties onto the component instead of setting it as the model.

I was thinking about this more, I think we might remove the controller option all together and see how some of the other ember addons do modals. Possibly removing the need for an outlet and having it be purely component based.

We have a component based modal in the new branch for #46. The route mixin may very well get deprecated after this.


where the data(cifar10-lt_train.npz) from?

hello~, where the data(cifar10-lt_train.npz) from?    Are there other proportions of long tail data?

If you need the dataset files you can find them under the data directory.
They've been inferred from the tfrecord dataset at
We've followed the exact same propotions as given in the original research work by Google Research.


Minimum bonus enchantment not working as intended.

This is my setup https://pastebin.com/70UrhhBL
i was intending to have my server setup as semi-vanilla, and set all safe enchantments to true.
i set the minimum bonus enchant to 3, and max to 5.
But there are times when i get items that has none of the bonus enchantments, and only the base enchantments. To my knowledge, i should be getting all the base safe enchantments + 3-5 safe bonus enchantments. Am i doing something wrong here? please advise.

Ive done somemore tests by setting safebonusenchantment to false, and the min/max bonus enchantment does work as intended. It seems to me that if safe bonus enchantment is set to true, MD will generate the number of minimum bonus enchantment for the item, and if it is not 'safe', the enchantment don't apply.
If that is the case, is there some way to allow MD to search for another enchantment as long as it meets the minimum bonus enchant and safe criteria?
E.G if i have unbreaking 1 and efficiency 1 as base enchant, and sharpness 1 and silk touch as bonus enchant, with a minimum and maximum bonus enchant of 1, i generate an pickaxe with the base enchant(unbreaking 1 and eff 1) and bonus enchant(shaprness 1). However, since safebonusenchant is true, sharpness 1 will not apply, and MD will find another suitable bonus enchant, and apply silk touch, meeting the criteria of 1 minimum bonus enchantment.