Fixing Longitude/Latitude to meters transformation

Hi,
the current implementation uses a pseudo meter transformation that will create distortions at higher latitudes. This fix takes care of that issue.
Regards
Richard

Thanks, Richard!  I'll check it out later tonight.

Looks good!


BULK Validation - desc, column headers, ms.date

Category

[x] Content fix
[ ] New article

Related issues

fixes #issuenumber
partially #issuenumber
mentioned in #issuenumber

What's in this Pull Request?
Bulk validation issue fixes.

Docs Build status updates of commit 99e625a:
:warning: Validation status: warnings

File
Status
Preview URL
Details

docs/schema/intervals-element-refinerconfiguration-complextypesps15xsdsearchset2.md
:warning:Warning
View
Details

docs/schema/isdeleted-element-resultitemtype-complextypesps15xsdsearchset2.md
:warning:Warning
View
Details

docs/schema/isfunction-element-propertyruleoperator-complextypesps15xsdsearchset2.md
:warning:Warning
View
Details

docs/schema/ismappedtocontents-element-crawledpropertyinfo-complextypesps15xsdsearchset2.md
:warning:Warning
View
Details

docs/schema/isnameenum-element-crawledpropertyinfo-complextypesps15xsdsearchset2.md
:warning:Warning
View
Details

docs/schema/isquoted-element-propertyruleoperator-complextypesps15xsdsearchset2.md
:warning:Warning
View
Details

docs/schema/isreadonly-element-managedpropertyinfo-complextypesps15xsdsearchset2.md
:warning:Warning
View
Details

docs/schema/joinedbyor-element-propertyruleoperator-complextypesps15xsdsearchset2.md
:warning:Warning
View
Details

docs/schema/intervals-element-refinerconfiguration-complextypesps15xsdsearchset2.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/isdeleted-element-resultitemtype-complextypesps15xsdsearchset2.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/isfunction-element-propertyruleoperator-complextypesps15xsdsearchset2.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/ismappedtocontents-element-crawledpropertyinfo-complextypesps15xsdsearchset2.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/isnameenum-element-crawledpropertyinfo-complextypesps15xsdsearchset2.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/isquoted-element-propertyruleoperator-complextypesps15xsdsearchset2.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/isreadonly-element-managedpropertyinfo-complextypesps15xsdsearchset2.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/joinedbyor-element-propertyruleoperator-complextypesps15xsdsearchset2.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


httpCookies requireSSL in .net core mvc

I just wanted to confirm regarding the following web config setting in .net framework 4.5 mvc:
<httpCookies requireSSL="true" />
so in .net core mvc, should it be this:
services.ConfigureApplicationCookie(o => o.Cookie.SecurePolicy = Microsoft.AspNetCore.Http.CookieSecurePolicy.Always);

ConfigureApplicationCookie only affects one of the authentication cookies, not every cookie. You need to use the CookiePolicy middleware to affect all cookies: https://github.com/aspnet/Security/blob/f084067d6a255fde3d12c07988157311ba52c51a/samples/CookiePolicySample/Startup.cs#L22-L32

Thank you, @Tratcher


Slow to respond on return from sleep

It appears like quicksilver has crashed if the hotkey combo is hit right after returning from sleep mode.
You can see the spinning beachball of death in the status bar, and it seems like the only way to get things working again is to kill off the quicksilver process (from the terminal, there is no other way I found). The reality is that it is EXTREMELY slow to respond to that first hotkey signal - defined as anything from 10 to 120 seconds. Yes, 2 minutes (or more). I discovered this when I decided to just start the app from the finder - the popup appeared long after I had already started using the program I started.  After that first very long delay, normal response is restored.
OS: 10.12.4
QuickSilver version - 1.5.3(401E)
Mid 2015 MacBook Pro Retina with SSD
Of note: I'm an emacs user. The default hotkey for quicksilver collides with the "set mark" command in emacs (ctrl-space). As a result I have it mapped to option-space. It has been working for years without this delay - so it's something newish.

Additional information: I generally do not restart my laptop - I just put it to sleep (Been a unix user for over 30 years - not used to having to reboot machines). I just checked, and the memory allocated to QS exceeded 4.3GB - this explains the very slow start -it was restoring from disk then compressed memory. A clean restart shows 98M of memory at start up. Every time QS is invoked via hotkey it leaks between 2 and 10MB.

Sorry - this appears to be a duplicate of 2343 "Memory Leak" - I thought it was just slow response until this morning.

The “Something newish” is probably the fact that the Safari plug-in was fixed and your catalog suddenly has thousands of things in it that weren’t there before. The work-around for now is to disable Safari History (under Preferences → Catalog → PlugIns → Safari).

Sounds like #2331


CIP-0067, CIP-0068 | Add Clarification for Edits and Modification

Some minor grammatical/typographical errors were fixed
Reformatting some table blocks w/o any modification of content
Update existing language in a few places to follow RFC 2119 format
Add documentation property (URL) to the CIP-67 registry.json file. If we are going to require that future extensions of the CIP-68 standard be submitted via a separate CIP, then when documenting them within the context of the CIP-67 registry it's important for implementers to be able to find documentation on these asset label names and how to support them (if necessary).
Add blocks clarifying the methods and mechanisms to submitting updates or extensions to CIP-68 standard following RFC 2119 format.

Happy to discuss and refine this as needed but consider this simply a first draft.

@Crypto2099 since I know you had already corrected grammar I did find something which I believed to be still incorrect & took a stab at fixing what appeared to be both a couple grammar errors + a nonsensical technical statement: please double check after the last 2 commits.

@Crypto2099 since I know you had already corrected grammar I did find something which I believed to be still incorrect & took a stab at fixing what appeared to be both a couple grammar errors + a nonsensical technical statement: please double check after the last 2 commits.

These couple additional grammatical errors also seem to make sense and fit in the scope of this so happy with those changes :)

FYI @Crypto2099 we need a rebase to fix the merge conflict after finally merging https://github.com/cardano-foundation/CIPs/pull/551 😅

Okay phew! That rebase was fun (not really) but I think we got it all sorted. Would appreciate some eyes @Ryun1 @rphair to make sure I didn't lose any of the formatting changes we had made along the way.

great: merging so we can more forward with this as a baseline for merge conflict resolution of https://github.com/cardano-foundation/CIPs/pull/523 as per meeting decision today.


OFBIZ-11855 Improved: Convert RoutingServices.xml mini lang to groovy.

OFBIZ-11855 Improved: Convert RoutingServices.xml mini lang to groovy.

Hi @yashwantdhakad ,
thanks for your contribution. There are some pull request merges included which do not seem do be related to the Minilan/Groovy conversion. Can you please provide a clean PR which only contains the intended changes based on latest trunk?
Thanks!

Closing this PR, I have provided the patch and the changes already merged in the trunk.


Getting signal: killed using your convstr.go example

I'm using the example found here (https://github.com/qiniu/iconv/blob/develop/examples/convstr/convstr.go) and I get signal: killed each time.  I have verified my iconv install is fine by calling it directly via command line.
I am on OS X Sierra.
Is there something I am missing?

me too.


Support CA certs from external secrets

From the conversation in #7
@roeldev it'd be cool if you could take this branch out for a spin and let me know how it works for you.

Cheers, I'll have a look later today when I'm back home. Thanks! :)

This is great! Thank you very much

This is great! Thank you very much

Excellent, thanks for testing it @roeldev


drivers: serial: Fix race condition in nRF5 UART TX

Fix a somewhat rare race condition when the thread gets
preempted in the middle of sending a byte through UART.
If the other thread also sends another byte through UART
and "consumes" the EVENTS_TXDRDY value, the first thread
will get stuck in the while loop forever.
By moving the reset to the function start, we guarantee that
the baseline state of EVENTS_TXRDY is 1. Therefore, the first
thread will continue normally when it executes again.
Signed-off-by: Thiago Silveira<EMAIL_ADDRESS>

A little tricky to reproduce, and I don't have an easy test case on hand. I was reproducing this on our own project. At first I tried to lock the scheduler in a printk-heavy area of the code, and that fixed the issue. I investigated further and pinpointed it to the uart_nrf5_poll_out while loop.
I also found that RIOT-OS had the same issue in the past, with the exact same fix: https://github.com/RIOT-OS/RIOT/issues/5954

I also removed the documentation part about checking if the transmitter is empty. This doesn't seem to be done at the moment or before. Maybe writing to uart->TXD does it implicitly, but reading the datasheet, it doesn't appear to have this information readily accessible.
Thoughts?
cc @carlescufi @cvinayak

The patch is okay.
From what I see, it fixes the handling of the TXDRDY event in general. Currently, the event is cleared at the exit of _poll_out, and this is not entirely good since the same event is also used by "interrupt driven" API to provide TX status (_tx_complete and _tx_ready). In case someone decided to combine usage of both APIs (what is not forbidden, I guess), this would mean troubles.
Regarding the removed documentation part - indeed, the current implementation does not do exactly what UART API states it should do. Actually, it should wait until the transmitter becomes empty before writing a new character there, i.e. do it like this:
 	/* Wait for transmitter to be ready */
 	while (!uart->EVENTS_TXDRDY) {
 	}

	/* reset transmitter ready state */
	uart->EVENTS_TXDRDY = 0;

 	/* send a character */
 	uart->TXD = (u8_t)c;

But then, we would fall into a similar issue. When the thread is preempted between clearing the TXDRDY event and writing to TXD, then the preempting thread would hang on the while loop if it tried to call _poll_out as well.
Therefore, I think the patch is the best what we can do to provide "thread safety" here without introducing some locking.
Maybe it would be worth mentioning in the code that the while loop has to be placed after the write to TXD (and consequently, _poll_out can't wait for empty transmitter right before writing to TXD) to avoid the rare yet possible race condition.

@anangl thanks for the thorough explanation.
@durub mind adding a comment in the code reflecting what @anangl mentions?

I chatted with @anangl over IRC and we agreed on the comment in the commit.
@carlescufi, I think this is ready now! @anangl, thanks for the explanation and help.

Hi,
After this commit the shell is broken. (nrf52 custom board)
Just no reaction to any command at all.
***** Booting Zephyr OS 1.11.99 *****
Zephyr Shell, Zephyr version: 1.11.99
Type 'help' for a list of available commands
shell>
help
help

Before this commit shell is responding to the commands.
Should I open the issue ?

@leodesigner I can reproduce, let me open the issue


Advanced compilation always gives error.

Is the website at https://closure-compiler.appspot.com/home   down?
The advanced optimization ALWAYS times out and gives error.

advanced optimization is working for me:

If I use incognito mode it works.
No idea why it doesn't in normal mode.

We have been only keeping this service up to simplify bug reporting for our open source users.
Therefore, the service is only expected to be able to handle minimal bug reproductions.
Anything larger than those, failures are expected.
I will close this issue, as for small code snippets we can successfully build code using the service.

This does not work:
https://closure-compiler.appspot.com/home#code%3D%252F%252F%2520%253D%253DClosureCompiler%253D%253D%250A%252F%252F%2520%2540output_file_name%2520default.js%250A%252F%252F%2520%2540compilation_level%2520ADVANCED_OPTIMIZATIONS%250A%252F%252F%2520%253D%253D%252FClosureCompiler%253D%253D%250A%250A((z)%253D%253E%257B%250Areturn%2520z%250A%257D)(%2522The%2520quick%2520brown%2520fox%2520jumps%2520over%2520the%2520lazy%2520dog.%2522)

@gunan
this works in simple but not in advanced.
https://closure-compiler.appspot.com/home#code%3D%252F%252F%2520%253D%253DClosureCompiler%253D%253D%250A%252F%252F%2520%2540output_file_name%2520default.js%250A%252F%252F%2520%2540compilation_level%2520SIMPLE_OPTIMIZATIONS%250A%252F%252F%2520%253D%253D%252FClosureCompiler%253D%253D%250A%250A((z)%253D%253Ez)(%2522The%2520quick%2520brown%2520fox%2520jumps%2520over%2520the%2520lazy%2520dog.%2522)


Environment variables need to be escaped

Variables like POSTGRES_PASSWORD may contain ' or $, which will cause bash to intercept them and open the door to errors. This is an injection problem, yes, but it's also just a convenience problem. Lots of secure (randomly generated) passphrases use quotes and dollar signs.
database_1   | 2018-08-23 20:20:50.925 UTC [66] ERROR:  unrecognized role option "fun" at character 52
database_1   | 2018-08-23 20:20:50.925 UTC [66] STATEMENT:  CREATE USER "zulip" WITH SUPERUSER PASSWORD 'zulip'fun' ;
database_1   | ERROR:  unrecognized role option "fun"
database_1   | LINE 1: CREATE USER "zulip" WITH SUPERUSER PASSWORD 'zulip'fun' ;
database_1   |                                                            ^

This issue originally comes from https://github.com/zulip/docker-zulip/issues/143#issuecomment-415555773

Thank you!


deps: up go-github to v45.1.0

Details are here https://github.com/google/go-github/releases/tag/v45.1.0.

https://github.com/octomation/maintainer/commit/dd6f6002fe441ec0e417cc62e83d9a853c47563e


cli: incorrect order of execution

Given the following workflow:
workflow "example" {
  resolves = "end"
}

action "a" {
  uses = "sh"
  args = "ls"
}

action "b" {
  uses = "sh"
  args = "ls"
}

action "c" {
  uses = "sh"
  args = "ls"
}

action "d" {
  needs = ["c"]
  uses = "sh"
  args = "ls"
}

action "e" {
  needs = ["d", "b", "a"]
  uses = "sh"
  args = "ls"
}

action "end" {
  needs = "e"
  uses = "sh"
  args = "ls"
}

Popper produces the following:
$ popper run --dry-run
Found and running workflow at main.workflow
DRYRUN: [a] ls
DRYRUN: [b] ls
DRYRUN: [c] ls
DRYRUN: [e] ls
DRYRUN: [d] ls
DRYRUN: [e] ls
DRYRUN: [end] ls
DRYRUN: [end] ls
Workflow finished successfully.

But the expected order should be: [a, b, c], [d], [e], [end], where actions in [a,b,c] could be executed in any order.

fixed by #722


Fixed Night Mode Problem in Spinner #2809

Description
Fixes #2809 Night Mode: Language Selection dialog is not readable
Tests performed
Tested betaDebug on Xiaomi Mi A1 with API level 28 stock.
Screenshots showing what changed

Codecov Report

Merging #2826 into master will increase coverage by <.01%.
The diff coverage is 0%.

@@            Coverage Diff            @@
##           master   #2826      +/-   ##
=========================================
+ Coverage    3.83%   3.83%   +<.01%
=========================================
  Files         267     267
  Lines       12534   12532       -2
  Branches     1082    1082
=========================================
  Hits          481     481
+ Misses      12020   12018       -2
  Partials       33      33

Impacted Files
Coverage Δ

...ee/nrw/commons/upload/SpinnerLanguagesAdapter.java
0% <0%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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

Thanks @madhurgupta10 ! Just a quick note, please try to be more clear on your issues and PRs. Ie, expected, found comparaisons, and some written explnation would help.

@neslihanturan I will definitely keep this in mind from now , thanks for the suggestion :)


New Release

Should I produce a new release?

I think so, yes. Please update the version in the pom and tag.

I don't have any context for this question, but it should be ok to go ahead.
I don't know when the last release, which will be the one golr loading is using. Would be a good idea to check if it has been a long time, as owlapi will be upgraded etc

I'm also out of the loop here (and get nervous around things like this).
AmiGO/GOlr currently use a version embedded in a Docker image, with the rest of the pipeline using one that it built itself, so there should no direct pipeline consequences if compatible.

Is there any chance we can get a volunteer to implement this first?
https://github.com/owlcollab/owltools/issues/289
We relatively urgently need this for exomiser.. (right, @julesjacobsen ?)

In forming documentation for the pipeline, I realized that in Jenkins and for me personally when I run the Makefile in go-site, we use a live built owltools. Meaning we build owltools right then, and use the built binary from there. But the documentation on owltools states to use the released version on github. However we haven't released a new version in something like at least a year. The instructions also say you can get owltools from the old Jenkins, which is not great advice.

It's not super-urgent, but this is definitely needed for pheval.

We still need a release—and we should start doing this regularly.

Okay, I can get on this.

Where is the latest release located now? Some of my Travis pipelines are failing now because bbop servers are gone..
Is this 4 year old GitHub release still the most up to date release, or have we simply not been keeping up with GitHub releases over the years?

@matentzn, It is the latter. @dougli1sqrd is looking at getting a new release out. In the interim, the stable-but-hacky location is that of a GO release https://github.com/INCATools/ontology-development-kit/issues/332#issuecomment-604777077 .

Cheers @kltm :P Just want to avoid to hard-code the GO release URLs into the ODK build process now. I will wait for @dougli1sqrd then! :) Thanks.

https://github.com/owlcollab/owltools/releases/tag/2020-04-06

Copy of my comment over at ODK: the Berkley build gave us:
http://build.berkeleybop.org/userContent/owltools/owltools http://build.berkeleybop.org/userContent/owltools/ontology-release-runner
http://build.berkeleybop.org/userContent/owltools/owltools-oort-all.jar
Can those be added to the release as well @dougli1sqrd ?
Thanks!

@dougli1sqrd @matentzn I added some additional files to the release at https://github.com/owlcollab/owltools/releases/tag/2020-04-06 from Eric's tag. Does that cover what people have been using?


[REQUEST] Any plan to extract ui/popup?

Hi there, I've got my own Emacs config but I've been inspired by and borrowing bits and pieces from doom. It's fantastic, nice work.
I was curious if you have any plans to extract your ui/popup code into its own package. I'm wanting to something for popup management and I see that you've gone through popwin and shackle and ended up writing your own, which seems to work quite well.
Would extracting it to its own package be feasible?
Thanks!

I have no plans to do so. It's somewhat-tightly coupled with Doom. Shackle is its closest analogue (and is more general); I'd recommend that. Otherwise, these are all abstractions over display-buffer-alist, which you could modify directly.

Got it, makes sense. Thank you for the recommendation. Feel free to close.

One other question, what was your motivation for switching from shackle to rolling your own? Any limitations of shackle I should be aware of?

@hlissner I've started extracting it, the close/restore is invaluable to me. I hope that you don't mind. It's here:
https://github.com/aaronjensen/emacs-popup-mode/
I don't intend to release on MELPA and I would gladly hand it over if you'd like it. It actually didn't take much to do, though I still need to sort out how you've got q/C-g/esc all closing popups correctly.

One other question, what was your motivation for switching from shackle to rolling your own? Any limitations of shackle I should be aware of?

I essentially wanted lower-level control over display-buffer-alist. The only real limitation of shackle is that it abstracts much of the underlying machinery.

I hope that you don't mind.

I don't mind, feel free to do with it as you like.

though I still need to sort out how you've got q/C-g/esc all closing popups correctly.

That is handled by doom/escape, which is defined in core-keybinds.el, and bound on +popup-buffer-mode-map.
Hope that helps!

Thank you, much appreciated. I've got it working well now. I'll let you know if I have any questions as I continue to use it.

I've fixed this by making the org src window dedicated. I wonder if the popup configuration would benefit from a :dedicated flag for this purpose?


[Suggestion] Split built-in store implementations out into their own Go modules?

Having all the different built-in store implementations in the same one Go module means that their dependencies are also pulled in when using eko/gocahce.
If the built-in implementations were moved to their own sub-modules with their own go.mod files, it would enable a much smaller dependency tree narrowed to only what you're actively using.
This should avoid issues like #144 for everyone not actively using the Pegasus store, since they wouldn't be pulling in the pegasus client package as a dependency.
For me this has become a bit of an issue at the moment while trying to use gocache within a custom Traefik plugin. Traefik runs plugins via Yaegi, which means you cannot have anything in the dependency tree that uses the unsafe or syscall packages.

Also, if it would help, I'd be happy to take a stab at the separation myself and submit a PR.

Hi,
New v4.0.0 release have now separated stores into a separated Go module.
So now we have the library that can be imported:
import "github.com/eko/gocache/v4/lib"

and one or multiple cache store(s):
import (
    "github.com/eko/gocache/v4/store/bigcache"
    "github.com/eko/gocache/v4/store/freecache"
    "github.com/eko/gocache/v4/store/go_cache"
    "github.com/eko/gocache/v4/store/memcache"
    "github.com/eko/gocache/v4/store/pegasus"
    "github.com/eko/gocache/v4/store/redis"
    "github.com/eko/gocache/v4/store/rediscluster"
    "github.com/eko/gocache/v4/store/ristretto"
)

I close this issue for now but feel free to reopen if you still have any issue.


types(message): add 16 & 17 to MessageTypes

Please describe the changes this PR makes and why it should be merged:

Add GUILD_DISCOVERY_GRACE_PERIOD_INITIAL_WARNING (16) and GUILD_DISCOVERY_GRACE_PERIOD_FINAL_WARNING (17) to MessageTypes.

Reference: https://github.com/discord/discord-api-docs/pull/1779 (NOT MERGED)

FYI: this is already in the types branch

FYI: this is already in the types branch


Instructions to run the repo

Hi @junyuchen245  : Nice work , Can we have instructions and the environment packages to run this repo ?

Hi @bhatrana ,
A requirement.txt has been added to this repo.
Thanks,
Junyu


stdlib: Add unavailable declaration for 'withUnsafePointers' and 'readLine'

What's in this pull request?

withUnsafePointers and withUnsafeMutablePointers were removed in 112451c44afa951a7e6447e8b2dc7c52d756dd16
readLine(stripNewline:) was renamed to readLine(strippingNewline:)

Before merging this pull request to apple/swift repository:

[ ] Test pull request on Swift continuous integration.

Triggering Swift CI
The swift-ci is triggered by writing a comment on this PR addressed to the GitHub user @swift-ci. Different tests will run depending on the specific comment that you use. The currently available comments are:
Smoke Testing
    Platform     | Comment
    ------------ | -------------
    All supported platforms     | @swift-ci Please smoke test
    All supported platforms     | @swift-ci Please smoke test and merge
    OS X platform               | @swift-ci Please smoke test OS X platform
    Linux platform              | @swift-ci Please smoke test Linux platform

A smoke test on macOS does the following:

Builds the compiler incrementally.
Builds the standard library only for macOS. Simulator standard libraries and
device standard libraries are not built.
lldb is not built.
The test and validation-test targets are run only for macOS. The optimized
version of these tests are not run.

A smoke test on Linux does the following:

Builds the compiler incrementally.
Builds the standard library incrementally.
lldb is built incrementally.
The swift test and validation-test targets are run. The optimized version of these
tests are not run.
lldb is tested.

Validation Testing
    Platform     | Comment
    ------------ | -------------
    All supported platforms     | @swift-ci Please test
    All supported platforms     | @swift-ci Please test and merge
    OS X platform               | @swift-ci Please test OS X platform
    OS X platform               | @swift-ci Please benchmark
    Linux platform              | @swift-ci Please test Linux platform

Lint Testing
    Language     | Comment
    ------------ | -------------
    Python       | @swift-ci Please Python lint

Note: Only members of the Apple organization can trigger swift-ci.

@swift-ci Please smoke test OS X platform

Thank you!  Could you also cherry-pick this change into swift-3.0-branch?


Rename the 'native' exporter component

Describe the proposal
The native exporter is actually our OpenTelemetry exporter. The name is a bit non-descriptive (and maybe confusing) so it could benefit our users if we rename this to something else.
A few ideas:

If we also switch metrics to OpenTelemetry (tracked here), then we can just rename native to opentelemetry-collector or even opentelemetry.
If we deprecate all exporter components (like this proposal), we could rename native to exporter. However, the configurations will be somewhat OpenTelemetry-specific so exporter will probably be a bit too generic.

cc @yaron2 @msfussell @youngbupark WDYT

If we are only keeping one exporter, it should move out of contrib and into dapr/dapr.

We decided to deprecate exporters in components and move to opentelemetry collector.  @tcnghia can you change this issue's title?

The exporter components are deprecated (see dapr/dapr#2337). So this can be closed.


Tests

More tests.
I didn't do:

gdocs/ebooks/reports as they'll likely change soon
wordpress blogs/arxiv as they're being worked on

ping


Reset extra_compile_args and extra_link_args for each module

Currently, extra_compile_args and extra_link_args are reused between module builds (e.g. '-fopenmp' is added for every module built after cusolver module), because it manipulates on shallow copy of the settings dict...

pfnCI, test this please.

Do you need to remove line 601?

@leofang Thanks, but that's still needed. Just cleaned the code.

pfnCI, test this please.

Thanks, but that's still needed. Just cleaned the code.

Ah ok, I thought the settings in the file loop could be done on a per-module basis. Thanks for clarifying. LGTM.

Jenkins CI test (for commit 4e8a9287338067d18feedc3c7fb11bd613f3f24a, target branch master) succeeded!

@emcastillo This pull-request is marked as to-be-backported, but the corresponding backport PR could not be found. Could you check?


🍒 Cherry pick PR #4807 to staging 🍒

🍒 Cherry pick https://github.com/Expensify/App/pull/4807 to staging 🍒

This pull request has merge conflicts and can not be automatically merged. :disappointed:
Please manually resolve the conflicts, push your changes, and then request another reviewer to review and merge.
Important: There may be conflicts that GitHub is not able to detect, so please carefully review this pull request before approving.

Update: Fixed merge conflicts


Unreal: Added settings for rendering

Brief description
Added settings for rendering in Unreal Engine.
Description
Two settings has been added:

Pre roll frames, to set how many frames are used to load the scene before starting the actual rendering.
Configuration path, to allow to save a preset of settings from Unreal, and use it for rendering.

Testing notes:
A layout will need to be loaded from Maya or Blender to be able to render the shot.
To render:

Create a render instance for a sequence.
Select the render instance and select Render from the OpenPype menu.

You can set the settings from the Studio Settings/Project/Unreal Engine.
For the Pre-roll frames, you can just set any number of frames.
For the Render Config Path, it should work both with an empty setting (and in that case it will use some default settings), or by setting a path with the Unreal format (e.g. /Game/Settings/Config.Config).

Since we are touching settings, shouldn't we add at least option to change file format? If I am not mistaken, now it renders to pngs hardcoded, but it should probably support more formats? Or is it a topic for another PR (along with the resolution that is now hardcoded?)


Fixed title overlapping search bar on full table.

Fixed by only applying margin on medium and larger displays.
Closes #13

That's awesome! Thanks a lot :)


install steps/instructions?

I'd like to install this, but I'm having a heck of a time figuring out how. I've been googling how to install custom atom autocomplete-plus providers but not finding anything. I'm sure it's super easy after doing it once.
Could you either update the README or maybe point me in the right direction and I can update README with install steps in a PR if you'd like.

nevermind, I was searching for the package in atom under "Packages" but I should have been searching in "Install". Thought there was more to the install, but as suspected just a user error.


Mismatch between fire maps and flaming/smoldering consumption maps

Unburned cells adjacent to fire maps (e.g. day-of-fire, fire-intensity) are incorporated into flaming/smoldering consumption maps.  Example, 1090 burned cells, 1234 flaming/smoldering cells.

How do you know how many flaming/smoldering cells?  What values are filtering on?

Mapping needed to add check for Intensity > 0.  Added to all outputs maps.


Fix documentation typo from "creaet" to "create".

@AndySu12 Are you planning to merge this PR?

Hi @babakpst, merge permission is not correct, let me resubmit the PR again, thanks.


feat: added close x button icon to popover

Hi there, I tried to use popover component, But it seemes there is no x button or a popover close button inside popover component, I googled it, It seems people using useState's to achive a close button, But because there is already a better way to close the popover I tried to add the x and close button.
Previous view:

@HoshangDEV Could we document this instead? Let's add an example to the popover docs page.

@shadcn I create an example with close button in the docs, And created another component for that example in apps\www\registry\default\example\popover-close-button.tsx,
but when i run the application i get Component popover-close-button not found in registry,
i tried to run the command pnpm build:registry and fixed the problem,
but after running this command also there is some issue, it make changes to over 1000 files, most of the files have not changed but it appears in the git files changes,
so there is another command for achiving this or what I did was the right way?


SOFTWARE-2884

@DrDaveD and @brianhlin could you review this please?
The VMU results are green:
http://vdt.cs.wisc.edu/tests/20170912-1542/results.html
The travis part may fall cause of the need for the autofs inside docker.

It looks OK to me.
Is it acceptable to fail travis, though?  Can you enable autofs?  Otherwise, manually mount the cvmfs repositories?  I am not familiar with how VMU works, but can you enable the testing you want there without it causing a travis failure on the osg-test github repository?

@DrDaveD I am not that familiar with travis, @brianhlin or @bbockelm  do you know if it is possible?. Or a workaround to make it not fail in travis,

I'm familiar with Travis, but I don't know how it relates to the VMU.
I would think you'd be able to just add autofs to the required packages and do the necessary cvmfs install steps (probably "cvmfs_config setup" is easier).  Alternatively, you can test singularity without cvmfs by having it read an image from dockerhub.

Ahh @DrDaveD I thought the cvmfs VMU tests failed in Travis. Cause Travis runs inside a Docker container and you could not mount cvmfs inside the docker container.

Travis allows running privileged docker containers, which I would think should be able to mount cvmfs.  I guess it depends if they have fuse available on the hypervisor host though.  Anyway like I said you shouldn't need cvmfs to test singularity.

@DrDaveD I do understand that singularity can be tested without cvmfs but since that one is the OSG most common use case, I would like to test it that way. But yes I can change to the singularity out of a docker container as a last resort

Yes, you can set Travis-CI to test CVMFS.  We are in the StashCache project, nightly.
https://travis-ci.org/StashCache/stashcache-tester
And the repo (most everything is done under the “tests” directory)
https://github.com/StashCache/stashcache-tester
-Derek

On Sep 13, 2017, at 12:04 PM, Edgar Fajardo<EMAIL_ADDRESS>wrote:
@DrDaveD I do understand that singularity can be tested without cvmfs but since that one is the OSG most common use case, I would like to test it that way. But yes I can change to the singularity out of a docker container as a last resort
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

@djw8605 thanks for the suggestion. I was able to make it work for el7 but for el6 it keeps failing.
https://travis-ci.org/efajardo/osg-test/jobs/275141035#L1198
FAIL: test_02_start_cvmfs (osgtest.tests.test_18_cvmfs.TestStartCvmfs)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/usr/lib/python2.6/site-packages/osgtest/library/osgunittest.py", line 165, in run
    testMethod()
  File "/usr/lib/python2.6/site-packages/osgtest/tests/test_18_cvmfs.py", line 76, in test_02_start_cvmfs
    stdout, stderr, fail = core.check_system(command, 'Start cvmfs server')
  File "/usr/lib/python2.6/site-packages/osgtest/library/core.py", line 263, in check_system
    assert status == exit, fail
AssertionError: Start cvmfs server
COMMAND: service autofs restart
EXIT STATUS: 1
STANDARD OUTPUT:
Loading autofs4: [FAILED]
STANDARD ERROR: [none]

@DrDaveD any idea on why autofs does not start inside travis on el6, but it does on el7?
Thanks,

Sorry, no I don't.  There's probably some useful information in /var/log/messages but I don't think you can see that from inside docker.  I'm assuming that the test suite adds '/cvmfs /etc/auto.cvmfs' to /etc/auto.master, or the el7 version probably wouldn't have worked.  I suggest trying to do bash -x /etc/init.d/autofs restart instead of service autofs restart to get more details of where exactly it is failing.

So it is failing on the 'modprobe autofs4'.  It's probably running on too new of a kernel where that module can't be loaded.  I can't think of anything to do about that, other than not using autofs but instead just doing a mount of the cvmfs filesystems you want.

@brianhlin I made the changes you requested. The VMU tests are green and the travis checks are passing. Can I merge this?


chore: general improvements to fibers

The main change is that we now rely on liburing function io_uring_peek_batch_cqe
to peek for completions instead of manually iterating with io_uring_for_each_cqe call.
The reason for this is that iouring API evolved, and the logic for peeking completions became
non-trivial: it requires calling a system call in some rare cases. So
in terms correctness and ease of maintainance it's better to rely on the library function to do the right job.
In addition, fibers scheduler code has non-functional changes:
a. Added a trace variable to ease with debugging: it shows the last transitioned state of the fiber
in ambigous situations.
b. ProcessSleep now returns the number of woken fibers.

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Comparison is base (bde6d74) 79.21% compared to head (68b7145) 79.18%.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff             @@
##           master     #193      +/-   ##
==========================================
- Coverage   79.21%   79.18%   -0.04%
==========================================
  Files         100      100
  Lines        7496     7499       +3
==========================================
  Hits         5938     5938
- Misses       1558     1561       +3

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

Hey Roman, shall I take a look despite the failing test? Wanna let me know when to look?

@chakaz you can look now :)


Can't swipe to close using swipeable edge section of a SwipeableDrawer

Duplicates

[X] I have searched the existing issues

Latest version

[x] I have tested the latest version

Steps to reproduce 🕹
Link to live example: https://codesandbox.io/s/sad-almeida-wg7mh3?file=/demo.tsx
Steps:

Open the drawer (either swipe or open button)
Try to close the drawer with a swipe action in the bleeding edge section of the drawer

Current behavior 😯
Only the non-bleeding area of the drawer is tracking swipe events.
Expected behavior 🤔
The bleeding section should track swipe events while the drawer is open so the drawer can be closed by a swipe from the bleed area.
Context 🔦
When the bleed section has a large height value (larger than the demo for example), it would seem like the swipe action doesn't work for the drawer, when in reality it does work but not for the bleeding section.
Your environment 🌎

npx @mui/envinfo
System:
    OS: macOS 13.0.1
  Binaries:
    Node: 16.20.0 - /opt/homebrew/bin/node
    Yarn: Not Found
    npm: 8.19.4 - /opt/homebrew/bin/npm
  Browsers:
    Chrome: 114.0.5735.198
    Edge: Not Found
    Safari: 16.1
  npmPackages:
    @emotion/react: ^11.11.1 => 11.11.1
    @emotion/styled: ^11.11.0 => 11.11.0
    @mui/base:  5.0.0-beta.6
    @mui/core-downloads-tracker:  5.13.7
    @mui/icons-material: ^5.13.7 => 5.13.7
    @mui/lab: ^5.0.0-alpha.135 => 5.0.0-alpha.135
    @mui/material: ^5.13.7 => 5.13.7
    @mui/private-theming:  5.13.7
    @mui/styled-engine:  5.13.2
    @mui/system:  5.13.7
    @mui/types:  7.2.4
    @mui/utils:  5.13.7
    @types/react: ^18.2.14 => 18.2.14
    react: ^18.2.0 => 18.2.0
    react-dom: ^18.2.0 => 18.2.0
    typescript: ^5.1.6 => 5.1.6

I have successfully reporoduced this issue and it seems to be a problem

@NaamanTsur Just to clarify this issue is about this example right? https://mui.com/material-ui/react-drawer/#swipeable-edge

@mj12albert Yes, that's the one. It is kind of hard to notice in the demo because the edge's height is low but at larger heights, closing the drawer is not possible through the bleeding edge section.

Hi - have any steps been discovered to fix how this demo is presented or how the swipeable edge is handled in the open state? We're also using it on a project and it's a usability issue

Came across this issue as well, it is still very present in the current live demo page. I see that this PR was on the path to fix the issue, however got set on hold only becaue some tests were broken. If I have the time, I'll try and help to re-implement the fix and its required tests, if the tests aren't still broken that is.

@Abzdefgxyj sorry for not getting to this so late, are you able to make a simple repro ?


fix(test): fix roxctl auth token test

Description
A PR was missed in the cherry-picks to 4.4. As a consequence, some roxctl unit tests fail.
This change aims at making the tests work again.
Checklist

[ ] Investigated and inspected CI test results
[ ] Unit test and regression tests added
[ ] Evaluated and added CHANGELOG entry if required
[ ] Determined and documented upgrade steps
[ ] Documented user facing changes (create PR based on openshift/openshift-docs and merge into rhacs-docs)

If any of these don't apply, please comment below.
Testing Performed
Here I tell how I validated my change
TODO(replace-me)
Use this space to explain how you validated that your change functions exactly how you expect it.
Feel free to attach JSON snippets, curl commands, screenshots, etc. Apply a simple benchmark: would the information you
provided convince any reviewer or any external reader that you did enough to validate your change.
It is acceptable to assume trust and keep this section light, e.g. as a bullet-point list.
It is acceptable to skip testing in cases when CI is sufficient, or it's a markdown or code comment change only.
It is also acceptable to skip testing for changes that are too taxing to test before merging. In such case you are
responsible for the change after it gets merged which includes reverting, fixing, etc. Make sure you validate the change
ASAP after it gets merged or explain in PR when the validation will be performed.
Explain here why you skipped testing in case you did so.
Have you created automated tests for your change? Explain here which validation activities you did manually and why so.
Reminder for reviewers
In addition to reviewing code here, reviewers must also review testing and request further testing in case the
performed one does not seem sufficient. As a reviewer, you must not approve the change until you understand the
performed testing and you are satisfied with it.

/test gke-nongroovy-e2e-tests


System.TypeLoadException: Failure has occurred while loading a type.

BasePreprocessingPipeline: Microphone subscriber 'DissonanceManager' threw: System.TypeLoadException: Failure has occurred while loading a type.
  at Wendigos.Plugin+DissonanceManager.ReceiveMicrophoneData (System.ArraySegment`1[T] buffer, NAudio.Wave.WaveFormat format) [0x0001d] in <57f01d698a46483ab54928bb129df66b>:0
  at Dissonance.Audio.Capture.BasePreprocessingPipeline.SendSamplesToSubscribers (System.Single[] buffer) [0x0008d] in <71dd734e1ae34dcbb7fcdfa8af2afae2>:0

This happens any time I try to use my WhisperManager class. Any idea what could be causing this? I'm using this with BepInEx in netstandard2.1
public static class WhisperManager
{
    public static async void ProcessFile(string wavFileName)
    {
        using var whisperFactory = WhisperFactory.FromPath("ggml-small.en.bin");

        using var processor = whisperFactory.CreateBuilder()
            .WithLanguage("auto")
            .Build();

        using var fileStream = File.OpenRead(wavFileName);

        await foreach (var result in processor.ProcessAsync(fileStream))
        {
            Console.WriteLine($"{result.Start}->{result.End}: {result.Text}");
        }
    }

    public static async void ProcessBuffer(byte[] buffer)
    {
        //get_model(GgmlType.SmallEn);

        using var whisperFactory = WhisperFactory.FromPath("ggml-small.en.bin");

        using var processor = whisperFactory.CreateBuilder()
            .WithLanguage("auto")
            .Build();

        using var audioStream = new MemoryStream(buffer);

        await foreach (var result in processor.ProcessAsync(audioStream))
        {
            Console.WriteLine($"{result.Start}->{result.End}: {result.Text}");
        }
    }

    public static string[] ModelNamesList =
    {
        "ggml-tiny.bin", "ggml-tiny.en.bin", "ggml-base.bin", "ggml-base.en.bin", "ggml-small.bin",
        "ggml-small.en.bin", "ggml-medium.bin", "ggml-medium.en.bin", "Not supported", "Not supported", "Not supported"
    };

    public static async void get_model(GgmlType model)
    {
        var modelName = ModelNamesList[(int)model];
        if (!File.Exists(modelName))
        {
            using var modelStream = await WhisperGgmlDownloader.GetGgmlModelAsync(model);
            using var fileWriter = File.OpenWrite(modelName);
            await modelStream.CopyToAsync(fileWriter);
        }
    }
}

Hello @TimShaw1 ,
Looks like you're trying to use some NAudio feature without having it referenced (from another part of the code).
Whisper.net doesn't have a direct dependency on NAudio and doesn't require it in order to create transcripts.
Based on your stacktrace, some other component (DissonanceManager in method ReceiveMicrophoneData) is trying to load NAudio but you don't have it installed.
You can probably mitigate your issue by installing NAudio, but it will be good to know why you need it.

Closing due to inactivity and the fact that issue is with NAudio config.


Interlinking in documentation is inconsistent

The interlinking in the documentation appears to fail somewhat randomly- or at least I'm unable to determine the cause. Some things seem to link correctly (e.g., IBMA classes here), while others link to their base classes (e.g., specific kernels link to KernelTransformer here), and still others don't link at all (e.g., CBMA classes here).

This can be fixed by dropping higher-level imports in inits. The problem is that this prevents us from making things more accessible (like making nimare.meta.cbma.kernel.ALEKernel accessible at nimare.meta.cbma.ALEKernel).


Make sure variant calling for eukaryotes takes into account heterozyzgous variants

Just following up about this issue.
I think our current filtering approach filters out any heterozygous SNPs by default (if the bacterial SNP analysis workflow was adapted).
We should double check this again and also be transparent about this.
The downstream filter steps (like vcf-to-tab step) are only consistent if this is the case.
In addition,  we need to check that the intermediate SNP output tables (in vcf_to_tab directory) make sense, not just for haploid organisms.
I will have some new tables generated shortly and will follow-up with this.


Restapi case insensitive search

Featuren with tests and some small fixes in the API (errorhandling etc)

Thank! CI fixed in master branch, please rebase.


Add node-style-guide preset

https://github.com/felixge/node-style-guide
Related #1070

I guess #1070 could be closed in favour of this issue.
@felixge what is you thoughts about this? Would it be cool for jscs to have this?

Ok just wrote it up.

Node Style Guide
.jscsrc

2 Spaces for indention
"validateIndentation": 2,

never mix tabs and spaces
"disallowMixedSpacesAndTabs": true,

UNIX-style newlines
"validateLineBreaks": "LF"

No trailing whitespace
"disallowTrailingWhitespace": true,

Use Semicolons
"disallowSemicolons": null (or no rule)

80 characters per line
"maximumLineLength": 80 (any exceptions?)

Use single quotes (except JSON)
"validateQuoteMarks": "'",

Opening braces go on the same line
"disallowNewlineBeforeBlockStatements": true,

whitespace before and after the condition statement
requireSpaceAfterKeywords and "requireSpaceBeforeBlockStatements": true,

Method chaining (one per line, indent once)
validateIndentation? #511?

Declare one variable per var statement
"disallowMultipleVarDecl": true,

Use lowerCamelCase for variables, properties and function names
"requireCamelCaseOrUpperCaseIdentifiers": true,

Use UpperCamelCase for class names
"requireCapitalizedConstructors": true,

Use UPPERCASE for Constants
new: "requireUppercaseConstants"

Use trailing commas
"requireTrailingComma": { "ignoreSingleLine": true }

short declarations on a single line
[ ]

Only quote keys when your interpreter complains
"disallowQuotedKeysInObjects": true,

Use the === operator
use jshint/eslint eqeqeq

Use multi-line ternary operator
new: "requireMultiLineConditional"

if (a === '')
"disallowSpacesInsideParentheses": true

Any non-trivial conditions should be assigned to a var/func
new: "maxConditionalLength"

Write small functions
new: "maxFunctionLineLength": 15

Return early from functions
[ ]

Name your closures
"disallowAnonymousFunctions": true ?

No nested closures

Use slashes for both single line and multi line comments
new: "disallowMultiLineComments"

// This function has a ..
"requireCapitalizedComments": true

Don't use Object.freeze, Object.preventExtensions, Object.seal, with, eval
"disallowKeywords": ["with"]

wow.

wow.

| From code | JSCS |
| // This function has a .. | "disallowSpaceAfterLineComment": true |

Oh ok. and for the table
First Header  | Second Header
------------- | -------------
Content Cell  | Content Cell

Yeah, sorry. Here time to sleep already...

Node Style Guide
...

short declarations on a single line
"disallowMultipleVarDecl": "exceptUndefined" ?

Write small functions
I think it's not about code style, it's more about complexity

Return early from functions
This idea walking around about half of a year, I'm strongly for adding a rule for it.

Don't use Object.freeze, etc
It'd be great to have a check for that. But is this code style?

We do have disallowKeywords so that's similar in some sense to "Don't use" - but yeah not really code style.

@markelog sure, it'd be cool :)

Does this issue also include stuff like checking for complexity, returning early from functions, and the other things mentioned in https://github.com/jscs-dev/node-jscs/issues/1071#issuecomment-74583649 ?
This would be great! I'm a fan of node-style-guide :smile:

I'm potentially throwing a spanner in the works in felixge/node-style-guide#56. Sorry about that.

I don't think we will include complexity checks as that's that that much of a style thing - I think you'll have to go with JSHint or ESLint for that (like the maxstatements rule in JSHint). I think we could think about a rule for returning early.
Also you can always extend the preset yourself if rules aren't added
{
    "preset": "node-style-guide",
    "other-rule": true
}

Ah, didn't know I could extend presets! (I've never used one before) Thanks :)

Oh ok - yeah presets are meant to be a starting point for your own ruleset so you don't have to read through a bunch of rules.  You can also disable a rule using null.
{
    "preset": "jquery",
    "requireCurlyBraces": null
}

You can even check the .jscsrc for the project: https://github.com/jscs-dev/node-jscs/blob/master/.jscsrc

@hzoo It would be great to note that in docs somehow. I suggest to make an issue with global docs updating to collect some ideas.


The concatenation handling of kv_cache causes a significant time consumption (18%)

I conducted a profile analysis of the inference process and found that the CatArrayBatchedCopy kernel has a high time consumption ratio. After checking the calculation logic, I suspect that this time consumption may be due to improper handling of kv_cache.
https://github.com/FunAudioLLM/CosyVoice/blob/main/cosyvoice/transformer/attention.py#L299
Tool: NVIDIA Nsight Systems

By the way, is there a cosyvoice base model that uses multihead attention?

https://github.com/FunAudioLLM/CosyVoice/blob/main/cosyvoice/transformer/attention.py#L299 concat the history attention with current frame, but I also don't know why this has so much computation cost. add me 铝箱 in dingding group to talk about details


Job 'kubernetes-dependencies' not found in Template table

→ bosh rs
Using environment '<IP_ADDRESS>' as client 'admin'

Name       Version  Commit Hash
bosh-dns   0.2.0    304d6ca
bpm        0.4.0    2722258
cfcr-etcd  1.0      06063f1
docker     31.0.1   eec7bfd
kubo       0.15.0   4438003

(*) Currently deployed
(+) Uncommitted changes

5 releases

Succeeded

→ shasum ~/releases/kubo-release-0.15.0.tgz
42b0000cc3dac0d4622bbad0db2c49803ccf6102  /home/ubuntu/releases/kubo-release-0.15.0.tgz

→ bosh -d cfcr deploy kubo-deployment/manifests/cfcr.yml
......
Task 12 | 04:06:20 | Preparing deployment: Preparing deployment (00:00:02)
                   L Error: Job 'kubernetes-dependencies' not found in Template table
Task 12 | 04:06:32 | Error: Job 'kubernetes-dependencies' not found in Template table

Task 12 Started  Tue Apr  3 04:06:20 UTC 2018
Task 12 Finished Tue Apr  3 04:06:32 UTC 2018
Task 12 Duration 00:00:12
Task 12 error

Updating deployment:
  Expected task '12' to succeed but state is 'error'

Exit code 1

The kubernetes-dependencies job exist in cfcr.yml and I have checked the job spec, confused why it's stuck here, any help would appreciate.

The issue resolved after I use cfcr.yml under tag v0.15.0 instead of master branch.
The tag v0.15.0 manifests/cfcr.yml doesn't contain job kubernetes-dependencies and it use kubo-etcd release, while manifests/cfcr.yml on master branch use cfcr-etcd release.

@qxing3 yep, that's the work around at the moment.
Other project repos have a system where the master branch promises to always work (e.g. #279), and the develop branch is where you'd expect to do a little work to get the thing deployed, e.g. to be building/uploading your own kubo-release etc

@drnic good to know, thanks : )

We don't plan to move to develop/master paradigm immediately. It will be considered when we move to cut our v1.0.0 release.


Add yaml linter github action

What this PR does
Before this PR:

no yaml linter github action

After this PR:

yaml linter github action

Special notes for your reviewer

Checklist
This checklist is not enforcing, but it's a reminder of items that could be relevant to every PR.
Approvers are expected to review this list.

[ ] PR: The PR description is expressive enough and will help future contributors
[ ] Code: Write code that humans can understand and Keep it simple
[ ] Refactor: You have left the code cleaner than you found it (Boy Scout Rule)
[ ] Upgrade: Impact of this change on upgrade flows was considered and addressed if required
[ ] Deployment: The deployment process was considered and addressed if required
[ ] Testing: New code requires new unit tests.
[ ] Documentation: Is the documentation updated? Either in the doc located in focus area, in the README or in the code itself.
[ ] Customers: Is this change affecting customers? Is the release plan considered?

Approved but question: do we want/need the .yaml-lint.yml configuration too?

The .yaml-lint.yml config is for the config for the YAML linter.  We specifically need the check-keys: false config so it doesn't complain about our github actions that have "truthy-like" values (e.g. on, off, yes, no, ...)
on:   # <--------- this ------
    pull_request:


Idea of faster translation: STT->TTS

This is just an idea for improvement.
It would be nice to have one button for both actions:

text to speech button
play translated text

Like a small simulation of a human translator, who listens to a sentence, then translates it in mind and then says it.

Yes, this is the Dialog feature. I think, we should have both in the future, similarly to e.g. Google Translate app:

single-mic icon "Hlas": just ASR, so the users can decide whether to tap the "play" icon in the translation or not
double-mic icon "Konverzace": the Dialog feature, each translation is automatically played. Furthermore, there is an option "Automatický hlasový vstup", so that it tries to detect both languages and decide automatically the translation direction. I can imagine that making this feature reliable is a lot of work (uk-cs Google Translate automatic dialog is very unreliable, almost unusable in all my attempts so far).

text to speech button
I think you meant "speech to text", i.e. ASR, i.e. "mic" button

I think you meant "speech to text", i.e. ASR, i.e. "mic" button

yes, the "mic" button

Google has api for it https://developer.android.com/reference/android/speech/SpeechRecognizer and there is example of use https://medium.com/voice-tech-podcast/android-speech-to-text-tutorial-8f6fa71606ac But it is more comlicated to implement it than dialog. Maybe in future.

something like "auto-play translations"

yes, this is what I exactly wanted, but I was not able to find the right words for "auto-play translation".
I can imagine that "conversation mode" can be difficult to implement.
So I am suggesting implementing walkie-talkie mode:

use two icons for the auto-play microphone (one for Czech and one for Ukraine)
when you press the Czech-flagged auto-play symbol:

record Czech speech
translate it into Ukraine
play translation

when you press the Ukraine-flagged auto-play symbol:

record Ukraine speech
...


Convert to Breakpoint API

Like the current ConvertToNop API we should have one that converts to Breakpoint in the Architecture base class

Debugger APIs implement this separately.


Correction for raw affiliation University of Calgary, Taylor Family Digital Library

Correction needed for raw affiliation University of Calgary, Taylor Family Digital Library
raw_affiliation_name: University of Calgary, Taylor Family Digital Library
new_rors: 03yjb2x39
previous_rors:
works_examples: W2998379281
contact: 88ca6973d2ec0359bbcc26c1d96c9927:36a490c5 @ ourresearch.org

This issue was accepted and ingested by the OpenAlex team on 2024-10-09. The new affiliations should be visible within the next 7 days.


Wildcard module declarations don't work as expected with require.js

If i use an wildcard declaration like recommended in the documentation
TypeScript Version:  2.2.2
declare module "text!*" {
    const content: string;
    export default content;
}

If I do these two imports in a module:
// As documented:
import template from 'text!template.html';
// Not as documented:
import * as template2 from 'text!template.html';

When using the documented import:
console.log(template);

is trinspiled into this:
// As documented:
console.log(template_html_1.default);

which doesn't work, because template_html_1 is an tring, without a property named default
On the other hand, when using it in the other way, this:
console.log(template2);

is trinspiled into this:
// Not as documented:
console.log(template2);

which works perfectly because template2 is in fact an string with the contents imported from template.html by requirejs.
ADDITIONAL PROBLEM: the second form is typed as text!*, instead of as string, so it's necessary to do this ugly cast: <string><any>template to use it as string.
Besides, in Chrome developer console, template doesn't exist (becasuse it's transpiled with the odd name template_html_1) while template2 is available, and has the right contents.
I don't know if this is an special case for requirejs, or if the documentation is wrong for all module loaders.
tsconfig.base.json:
{
	"compilerOptions": {
		"target": "ES5",
		"module": "amd",
		"noImplicitAny": true,
		"sourceMap": true,
		"removeComments": false,
		"preserveConstEnums": true,
		"strictNullChecks": true,
		"emitBOM": true,
		"declaration": false,
		"noUnusedLocals": true,
		"noUnusedParameters": true,
		"noEmitHelpers": true,
		"listEmittedFiles": true
	}
}

tsconfig.json
{
	"extends": "./tsconfig.base.json",
	"compilerOptions": {
		"outDir": "../Scripts"
	},
	"include": [ "**/*" ]
}

your declaration says 'text!template.html' has a default export. if that is not the case, then change the declaration to:
declare module "text!*" {
    const content: string;
    export = content;
}

and use it as:
import * as template2 from 'text!template.html';

Thanks for the quisk and exact answer, @mhegazy. Using the second import with this export, works like a charm.
However, the default export documented in http://www.typescriptlang.org/docs/handbook/modules.html#wildcard-module-declarations doesn't work at all with requirejs. I wonder if these documents could be updated, and if the problem with default is only for my configuration, or is a general problem.

It all depends on what the plugin is doing. If your plugin will return a default, then it is accurate. This is not meant to be a template for all projects, this is just a demonstration that you can declare a module with wild cards just like you can declare any regular module.

Thank you very much for your answer and explanation. I didn't think that the plugin implementation could have something to do with the way to implement the wildcard module declaration, and it's consumption.
As a reference for people using requirejs with its text plugin, as explained above, this combination works perfectly:
Wildcard module declaration:
declare module "text!*" {
    const content: string;
    export = content;
}

Import
import * as template from 'text!aBeautifulTemplate.html';


Question panel doesn't look good in dark mode

What

Find a product with unanswered question
Switch to dark mode

The panel asking users to answer the question looks bad.
Screenshot

Part of

#684

@GowthamGoush, there are probably some hardcoded color values which need to be changed. The card background color as well as the text color

Alright, got it!

I made the necessary change, but could you please verify if it is good enough for the dark mode? If not, I would love to hear your suggestion.

LGTM 👍

fixed


Ability to change the word length

I was thinking it could be cool to have the option of choosing the world length before playing.
As far as implementation is concerned, I'm willing to give it a try. But my background is more with C/Python/Rust, and I might struggle at using React and TailwindCSS. Let me investigate a bit.
@octokatherine, thanks for the game. I'm looking into implementing a version on a 16K RAM ZX81 for fun.

I think this could be a fun addition! If you don't want to implement, maybe someone else will pick it up

@octokatherine I was thinking about this feature too. I would like to try implementing it if @bru65pag doesn't mind. However, I have a few questions:

Would the number of guesses allowed have to change (because if you had a 3 letter word, you wouldn't be able to rule out or confirm as many letters with just 6 guesses)?
There would have to be limits to the word length, since really long words would be hard to guess. I was thinking 3 to 8 letters?

@defyentropy, please go ahead. I'll try on my side as well, but since I'm starting from scratch with WEB dev, it might take a while.
@octokatherine, where did you pick the list of words? Would be good to reuse the same source for different lengths.

@defyentropy

Would the number of guesses allowed have to change (because if you had a 3 letter word, you wouldn't be able to rule out or confirm as many letters with just 6 guesses)?

I think this will be okay if we make 4 letter words the minimum. Let's stick with 6 guesses for simplicity.

I was thinking 3 to 7 letters?
Let's start with 4-6 and iterate based on feedback

@bru65pag

@octokatherine, where did you pick the list of words? Would be good to reuse the same source for different lengths.

I downloaded the word list from here
I used the full list of valid 5 letter words in words.js to check submitted answers against.
Then I manually filtered those to just well known words inside answers.js which are words that can be the target answer word.
If we add more word lengths, we should use the same technique

@octokatherine
I now have a words7.js for 7-letter words. 25133 words! It's in bru65pag/zxmasterword/data/words7.js. I will work on an answers7.js, but going through 25K words might take me a while...

@defyentropy

Would the number of guesses allowed have to change (because if you had a 3 letter word, you wouldn't be able to rule out or confirm as many letters with just 6 guesses)?

I think this will be okay if we make 4 letter words the minimum. Let's stick with 6 guesses for simplicity.

I was thinking 3 to 7 letters?
Let's start with 4-6 and iterate based on feedback

Sounds good. Thanks for clearing it up!

@octokatherine I'm really sorry to say this, but I don't think I'll be able to work on this issue anymore, because I'm extremely busy right now with exams and whatnot. I did manage to get a rough draft of a system to allow the user to change the word length working, but I'm not sure I have enough time to filter through thousands of words and choose more commonly known ones. I hope you understand.
For what it's worth, I love Word Master and think it's a great project, and hope it becomes even more popular in the future.

no worries @defyentropy!

@octokatherine Hi! I've played your game a ton and think it's a fun project. I might be interested in working on this issue, but I wanted to ask, based on your experience with your project, how long would you guess it would take to implement this in full?

Good morning @kcamsanc ,
I am currently working on it (started two days ago).
It took me a while  to setup React locally (I'm an absolute beginner in React). I have modified the settings screen already, created arrays with 7-letter words, and am currently reworking the main screen. I hope to be done with something that works by next week.
I would be more than happy to share my work if you want to contribute; but I"m really not sure how to do that in git/github. If you know, I'll be more than happy to give you access.
Final note: I spent about two hours so far on the topic, and expect that a few more hours should be enough (I am an absolute beginner in React, that is why it takes me more time than it would to a seasoned React programmer).
Happy coding. Bruno.

Good morning,
As mentionned last week, I'm still working on this. I hit a new road block :-) tailwindCSS. I had never used it before, it took me a bit of time to have it installed on my computer and get familiar (more or less with it). I might be a bit behind on schedule, but hope to be able to have a working version end of this week beginning of next week.


Doesn't find CSS/SCSS sourcemaps

I installed this repo as is. After running the dev process it does not find any sourcemap files and shows everything as inline. I tried it with CSS and SCSS.
Is there an option I overlooked?

Duplicate https://github.com/vuejs-templates/webpack/issues/123.


Update ConditionVerificationStatusMenu.tsx

Proposed Changes
. Search Functionality: Added a search input at the top of the dropdown to filter options dynamically.
. Default Value Support: Introduced a defaultValue prop to allow setting an initial value.
. Improved State Management: Integrated state management for the selected value.
. User-Friendly Placeholder: Enhanced placeholder display to provide better guidance to users
@ohcnetwork/care-fe-code-reviewers
Merge Checklist

[ ] Add specs that demonstrate bug / test a new feature.
[ ] Update product documentation.
[ ] Ensure that UI text is kept in I18n files.
[ ] Prep screenshot or demo video for changelog entry, and attach it to issue.
[ ] Request for Peer Reviews
[ ] Completion of QA

Summary by CodeRabbit

New Features

Introduced a search input in the dropdown menu for filtering options.
Added an optional defaultValue property for initializing the dropdown with a default selection.

Improvements

Enhanced state management for selected value and search term.
Updated logic for displaying and selecting dropdown options.

This has been rebuilt in an ongoing development branch. Not relevant.
https://github.com/ohcnetwork/care_fe/blob/form-field-v1/src/components/Questionnaire/QuestionTypes/DiagnosisQuestion.tsx#L217-L241


Add styling

MILESTONES

Apply React best practices and language style guides in code.

@migo1 Kindly avoid making further changes after a review is submitted as this may lead to some confusion between you and the reviewers concerned. You should only submit your project when you are sure it meets the requirement and after, that wait for the review instructions on your dashborad before proceeding to make any change.


Wordpress comics

Category
This change is exactly one of the following (please change [ ] to [x]) to indicate which:

[X] a bug fix (Fix #295 )

Description
I changed the regex for konradokonski.com to match all comics on that site
The SITM comic is failing atm because of a missing image at url http://www.konradokonski.com/SITM/comic/sitm-filler-reading-time/
Testing
Required verification:

[ ] I've verified that there are no regressions in mvn test (there are no new failures or errors).
[ ] I've verified that this change works as intended.

[ ] Downloads all relevant content.
[ ] Downloads content from multiple pages (as necessary or appropriate).
[ ] Saves content at reasonable file names (e.g. page titles or content IDs) to help easily browse downloaded content.

[ ] I've verified that this change did not break existing functionality (especially in the Ripper I modified).

Optional but recommended:

[ ] I've added a unit test to cover my change.

Coverage decreased (-0.03%) to 30.442% when pulling 0a6d049bc31427ceb6597dd77847ce97ba70d3ea on cyian-1756:wordpress_comics into be916af8ce75592b52bf6db98ce2664eee7d3dcb on RipMeApp:master.


Bump to 0.3.0

Summary of Changes

Bump to 0.3.0
Update full name to "Xarray Climate Data Analysis Tools"
Bump minimum Python version to >= 3.8
Add esmpy, xesmf, cftime, and numba to dependencies

TODO

[ ] Update SHA to 0.3.0 GH release

Checklist

[x] Used a personal fork of the feedstock to propose changes
[x] Reset the build number to 0 (if the version changed)
[ ] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[x] Ensured the license file is being packaged.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

@conda-forge-admin, please rerender

Hey @jasonb5, are you willing to be a maintainer too?

@conda-forge-admin, please rerender


Could you provide your model?

Hi, I am researching about persona chatbot.
Now i try training the BoB model for my research but it dosen't work well...
So, I would like you to publish your model.

I would like you to? You did not give any detail about what doesn't work well and sorry I cannot help you.


Cannot import random password

(this is from https://stackoverflow.com/questions/66781327/how-can-i-import-existing-password-into-pulumi, which at the time of writing has no suggested answers)
I am trying to import an existing stack into Pulumi, in particular I want to import an existing password, but have Pulumi generate that password for any future stacks.
As per https://www.pulumi.com/docs/reference/pkg/random/randompassword/#import I am running pulumi import random:index/randomPassword:RandomPassword password Password123!
Expected behavior
The code for adding this password into the Pulumi application is displayed in the console, and the existing value is then available to use within the current stack.
Current behavior
An error is returned: random:index/randomPassword:RandomPassword resource 'password' has a problem: Required attribute is not set. Examine values at 'RandomPassword.Length'
Steps to reproduce
In a blank folder run:

pulumi new azure-python
pulumi plugin install resource random 3.1.1
pulumi import random:index/randomPassword:RandomPassword password Password123!

Context (Environment)
This was actually for a training exercise I was writing which now works around this by setting the existing password as a secret and then requiring new stacks to have the password manually generated by the deployer.
It's not clear to me if the docs need updating (to have either a working command, or to not suggest that this is possible) or if this should work that a change is needed in the code.

Ran into this myself - FWIW, this does work on Terraform so I guess it's supposed to work here too but there seems to be a bridging issue.

Any update on this?

I am running into the same exact problem with importing RandomString as well.

I think the problem will be fixed by solving the overall issue https://github.com/pulumi/pulumi/issues/7160

Sadly https://github.com/pulumi/pulumi/issues/7160 won't fix this issue. We're hitting a limitation that terraform can import these resources using its Importer system.
Pulumi expects to be able to Read then Check a resource to import it. While our Read logic can call into the terraform import system it's import system doesn't fill in the "length" property. Because "length" is a required input when we call Check after getting the result back from Read it fails because "length" isn't there.
I think the easiest way to fix this would be to fix the terraform importer to just set length then everything should just work

@t0yv0 can you check if this is fixed after we update to TLS v4?

I still face this problem with current versions.

Thank you for your patience with us on figuring this out. I'm still a little confused by this issue but I gave it a try just now. We now have the latest release (4.11.1), and I now get this new error message:
    error: Preview failed: Cannot extract ID from "random_password" resource state: ID cannot be empty

The message is not very unhelpful. However looking at the help for pulumi import --help this does not seem to be the right argument set for import:
If using the command line args directly, the type, name, id and optional flags
must be provided.  For example:

    pulumi import 'aws:iam/user:User' name id

So I have tried this instead. I provisioned a stack with pulumi up:
name: test-random-1
runtime: yaml
description: A minimal Pulumi YAML program
resources:
  pw1:
    type: random:RandomPassword
    properties:
      length: 1

Now within the same folder I can find out the name (pw1 from the program), and ID (happens to be "none" from pulumi stack export), and I can run the import:
$ pulumi import random:index/randomPassword:RandomPassword pw1 none

This now succeeds but the output is a bit underwhelming:
Please copy the following code into your Pulumi application. Not doing so
will cause Pulumi to report that an update will happen on the next update command.

Please note that the imported resources are marked as protected. To destroy them
you will need to remove the `protect` option and run `pulumi update` *before*
the destroy will take effect.

resources:
  pw1:
    type: random:RandomPassword
    properties:
      length: 1
    options:
      protect: true

From the Import Docs it seems that import is about harvesting the state of a resource existing in the cloud and bringing it back under Pulumi management so it now appears in the state file. This does not seem to do anything helpful with RandomPassword currently because it has no state in the cloud per se, and only in the state file?
Perhaps stepping back a bit, what is the problem that pulumi import needs to solve here?
If I think of the problem of having an existing Pulumi password in stack X and having to use it in stack Y, I think perhaps of the Stack References feature that could do it.

Is the scenario to import a Terraform-provisioned password into Pulumi?

Is the scenario to import a Terraform-provisioned password into Pulumi?

That was the reason I originally started following this issue. When we migrated to Pulumi I wasn't able to bring some "secrets" over without manually editing the state file.

Thanks for clarifying @jacobfoard !
We have some docs on bringing resources over from Terraform to Pulumi, confusingly they do not involve the pulumi import command:
https://www.pulumi.com/docs/guides/adopting/from_terraform/#importing-resources

Doing a bit more digging, it appears that Terraform supports this behavior also for import:
https://registry.terraform.io/providers/hashicorp/random/latest/docs/resources/password#import
It makes sense that the expectation is that Pulumi will behave similarly. This still doesn't work at the moment but I will have a closer look next week and circle back here.

It appears it's working in v4.12.0! Please let us know if there's any issues!


ipaas-search-connectors seems to cache results

Could be maven causing this.  But basically:

Call ipaas-search-connectors
upload a new connector jar to nexus
Call ipaas-search-connectors again

only the connectors you got back for step 1 are returned.  I can only get my newly uploaded connector to show up if I kill the fabric8-forge pod and let it get restarted.

There is a background thread the re-index the nexus repo and runs every 10 second.
https://github.com/fabric8io/django/blob/master/addons/ipaas/src/main/java/io/fabric8/forge/ipaas/repository/NexusConnectionRepository.java#L52

Yeah let me see if forge don't detect that CDI bean and starts it (CDI is lovely)

So you need to run one of the django commands first to have that background thread start up. I guess forge dont scan CDI beans or something. Will try with some EjbStartup annotations

Okay the new forge release starts the indexer on startup.
You need to name the artifactId of the connector with -connector as suffix. The wizard do not enforce that as its a wizard OOTB from jboss forge (project-new) which we cannot control.


Marking glossary terms as untranslateable

Is your feature request related to a problem? Please describe.
Right now we house our glossary in a Google Sheet, the problem with this is as our glossary grows it becomes more and more likely a linguist will miss a word.
Describe the solution you'd like
It would be great if Pontoon could parse the strings and recognize when a term is marked as untranslateable in our glossary, subsequently letting the linguist know that term should stay in English.
For reference: Lokalise TMS seems to do this really well.

The new "Terms" feature takes care of this


Added support for JWT Bearer grants

TODO:

refactor endpoint_request
refactor Client to make client_id optional

Can you go into the repository settings and add myself and Jack as collaborators with Write access? I presume the Engineering team already has the Read access (since I can read it). Thanks!

Oh and lastly, don't bother merging this. When I manage forks I prefer to keep amendments on a separate branch (jwt-bearer) and the primary branch (main) matching the upstream repo. It's ideal for managing git rebases so that our changes are always applied to the latest history (and can be updated if necessary), and overall keeping the histories clean (merged histories can be hairy to dissect out what it is you actually did in your fork).
The rebasing can technically be managed all within the fork's version of main but I've found separate branch helps avoid confusion.
I'm sure you already are aware of this, but in Cargo.toml you can point to the branch with oauth2 = { git = "https://github.com/onda-ai/oauth2-rs", branch = "jwt-bearer" }

TODO:
refactor endpoint_request
refactor Client to make client_id optional

You did the first part already. I would not break the Client::new() interface. We can just provide an empty ClientId, no big deal. Your work in endpoint_request handles the optional presence of it based on the type of originating oauth2 request.


Allow Running as a Tool Wrapper

This tool could optionally get a command line as parameter, and in this case it should execute the command line, wait for termination of the process, and then print the measurement results (just like the tool time does).
This would make it useful for human users and not only benchmarking frameworks.

Because of the security implications, we are unlikely do implement this.


Change empty state for leaf scope 'Assets' tab

This is for any scope (not the home) where there are no child/descendants assets to show
Add a link to its parent, if multiple parents exist  ??? @doppleware
parent(s) should be set according the current service(s) Filter
https://www.figma.com/design/MxA95ZHK5NqGX4ptFQljRJ/⭐-Design-System-3.0?node-id=12093-197472&t=pOBXeye7JWBHJyNY-4

Show the first three if more than one exist


Remove the "run your java code" from the documentation

Here, the procedure on Windows says Reopen Command prompt window, and run your java code..

FIXED by https://github.com/zetapush/documentation/pull/74


Backport 15705 & 16368 to Druid 30

Backports https://github.com/apache/druid/pull/15705 & https://github.com/apache/druid/pull/16368 to Druid 30 branch.

@findingrish , for future changes, please try to backport each commit separately as it is generally cleaner. It also helps the release scripts in verifying that each milestone-tagged PR has actually been backported.

@kfaraz We can rebase and merge - that doesn't break the script afair.

@kfaraz We can rebase and merge - that doesn't break the script afair.

I see, thanks for the clarification, @LakshSingla .


Feature request  Self-Organizing Map (SOM)

Is your feature request related to a problem? Please describe.
Self-Organizing Map (SOM) algorithm for fraud detection using credit card application data
Describe the solution you'd like
Fraud detection in credit card applications requires identifying patterns within the dataset that indicate potential fraudulent activity. The challenge is to process the dataset and apply the SOM algorithm for clustering and anomaly detection.
Approach to be followed (optional)
Load the dataset from a CSV file, assign feature values to X and the fraud classification to y. Scale the features using MinMaxScaler from sklearn.preprocessing to bring values to a uniform range between 0 and 1. Initialize a SOM using MiniSom from the minisom library, with a 10x10 grid of neurons and an input length of 15 (number of features).Train the SOM using train_random for a specified number of iterations.The SOM will group credit card applications into clusters, helping to identify potential fraud through anomaly detection.

@ramana2074 once check your points and let me know

Updated @UppuluriKalyani

Updated @UppuluriKalyani

I mean  your contributions exceeded 200 points?

180 points are done


Flutter web app doesn't react to line space changes

Steps to reproduce
https://www.w3.org/WAI/WCAG21/Understanding/text-spacing.html

Go to https://codepen.io/stevef/full/YLMqbo
Drag the "Text Spacing" link in to the bookmarks bar
Open a Flutter app
Click on the Text Spacing bookmark

Expected results
The text in the app should increase its line spacing
Actual results
Nothing happens
Code sample
return MaterialApp(
  home: Scaffold(
    appBar: AppBar(
      title: const Text('Repro examples'),
    ),
    body: Center(
      child: Semantics(
        header: true,
        child: Text('''Hello World\n'''
            '''New line \n'''
            '''Next line \n'''),
      ),
    ),
  ),
);

Screenshots or Video

Screenshots / Video demonstration
[Upload media here]

Logs
Logs
[Paste your logs here]

Flutter Doctor output
Doctor output
[Paste your output here]

b/328308198

@franciscojma86 can you provide a video of the steps above?

This is similar to https://github.com/flutter/flutter/issues/100710 and it was marked as a duplicate of https://github.com/flutter/flutter/issues/142712 so I will close this in favor of https://github.com/flutter/flutter/issues/142712. Please follow it for update.


Can't figure out how to use A128CBC-HS256 algorithm

I'm trying to encrypt using the A128CBC-HS256, but I can't figure out what key to use. I've tried a bunch of different ones listed under "Supported Key Encryption Algorithms" and keep getting errors for all of them. Any pointers?

Hi,
To create an encrypted token, you need two algorithms:

Key encryption algorithm
Content encryption algorithm (A128CBC-HS256 in your case)

The key used by the content encryption algorithm depends on the key encryption algorithm.
You will find a small example here. It uses the A256CBC-HS512 algorithm, but the computation is identical.

Thanks for the quick reply. It was actually a problem on my end that had me thinking I had the wrong key type. The key given to me wasn't properly encoded and I hadn't noticed. It's now working as expected. Thanks again!


Spatial layout for qualtran circuits

Given an abstract circuit, is there a convenient way to use qualtran to compile all the way down to a physical spatial layout of the circuits, as is done in Gidney-Ekera's factoring paper? If not, what would be the recommendation to build on top of qualtran to achieve this, assuming that one already knows the layout but wants to use qualtran to express it? An example could be the Gidney factoring layout, or the known layouts in a magic state factory.

Thanks for the question! The data structures in qualtran were tailored for expressing logical operations at increasing levels of abstraction. The idea is: you'd express your algorithm using Bloqs which can be compiled down to a logical gateset (like clifford+T+Toffoli) and then you'd use something else to lay it out. Right now, we have qualtran.surface_code which will give you the physical costs (qubits, wallclock time) using some models from the literature but it doesn't explicitly lay anything out.
You'd likely need a different set of data structures to represent the constraints / reality of your hardware architecture. For a surface code, something like Cirq with its cirq.GridQubit is probably close to what you'd want to express the physical layout. Automating & optimizing the layout is a very challenging problem. This project aims to do this: https://github.com/latticesurgery-com/lattice-surgery-compiler. Interoperability with qualtran would be a great feature but it doesn't exist yet #447.
The Gidney-Ekera factoring layout (as I understand it) was done by hand in sketchup, which is a generic 3d modeling program.


HSM key store to handle AddNOC / UpdateNOC

Problem
HSM key store to handle AddNOC / UpdateNOC

Fixes #20036

Change overview
Implementation of Persistent Storage Operational Keystore class to handle HSM keys.
Testing
Tested using unit tests / lighting example

Fast tracking given this has had enough time for review.


Log NMEA messages

Log all NMEA messages received as csv files, one file per message type (GGA, etc.).
Each row should include the time the message arrived (Pi time).
Filenames should include date and time when the extension started (Pi time). Files should appear in BlueOS File Browser under: /extensions/wl_ugps_external_extension/logs/{date}.
Implements https://github.com/zhrandell/Seattle_Aquarium_CCR_development/issues/14

I don't see a standard NMEA 0183 message that contains roll and pitch.
The Advanced Navigation GNSS compass sends roll and pitch in a few proprietary formats:

$PASHR, NMEA 0183 proprietary message, appears to be used by a few systems, see Hexagon/NovAtel and Trimble
$TSS1, ASCII format that does not follow the NMEA 0183 standard, see Hexagon/NovAtel
$PFEC,GPatt, NMEA 0183 proprietary message defined by Furuno, see Marport/Scala
ANPP is a binary format defined by Advanced Navigation
PGN 127257, NMEA 2000, only sent at 1Hz, not configurable, see ContinuousWave for a description

Of these, $PASHR looks like the easiest to add, so I'll start there.


refactor(server): Provide file-service handlers in the root injector.

By removing the creation of file-service handlers from the webserver, we create functions with better
focus and we allow the file-service handlers to be used in beforeMiddlewaare. The only cost is that these objects are now visible to all modules rather than being private to webserver. The potential for collision seems small.

Ok thanks, fixed, tests pass.

Done


Vulnerability roundup 90: terraform-0.13.0-rc1: 1 advisory [9.8]

search, files

[ ] CVE-2018-9057 CVSSv3=9.8 (nixos-unstable)

Scanned versions: nixos-unstable: 28fce082c8c. May contain false positives.
Cc @Chili-Man
Cc @babariviere
Cc @kalbasit
Cc @marsam
Cc @peterhoeg
Cc @zimbatm

This is a mismatch against the terraform AWS provider.


Minor bug: duplicate linting when linting on save

When using the "Lint on Save" setting and then saving a file, I get two notifications from the Linter plugin. As the notifications show different information, it seems that this is not a notification error but rather the linter running twice?
Obviously, running the Linter twice in a row isn't a big deal since the second run will simply do nothing, but at least the double notification is a bit misleading.

and when saving, the console indeed reports two linter runs:
running linter main.ts:132
running linter main.ts:122

The problem does not occur when I use "lint the current file" instead of the save file command.

hmmm, indeed, restarting Obsidian fixed it 🤔


Can't cut copy and paste

Description
I can't paste my file in other folder and I must use File Explore to paste it
Steps To Reproduce
No response
Expected behavior
Can paste file to other folder ?
Files Version
Version: <IP_ADDRESS> OS Version: 10.0.19043.1021
Windows Version
Windows 10 Pro 21H1 19043.1021
Relevant Assets/Logs
debug.log
debug_fulltrust.log

Same Question here, quite a weird one because sometimes I can copy from File Explorer and paste in Files, but sometimes I can't.

This happens EVERYWHERE, no matter in the cloud or local or libraries or drives. Also, Ctrl+C,Ctrl+V and clicking the Paste button or Copy button simply don't work.

What is more weird is that simply drag a file to another folder/tab can work...

Merging with #7459


feat: support mattr launchpad proof requests

NOTE: very hacky
Uses packed versions of

https://github.com/Sphereon-Opensource/PEX/pull/128
https://github.com/Sphereon-Opensource/SIOP-OID4VP/pull/61

Only supports the single credential request yet, as the multi-request from launchpad contains an invalid presentation definition.

I will try to get this updated with all the changes to credo. Would be nice to have credential selection in the wallet

@TimoGlastra Is this something we would like to add in the wallet right now? With some of the work we will do now, it might get even more out of sync.

I have a local branch that has it 95% complete. I'll see to get it updated. I think the main thing was that the UX didn't work very nicely


katex can be crashed with $ \$

in markdown
\$ \\$

results in
ParseError: KaTeX parse error: Expected 'EOF', got '\' at position 3:  \̲

same as https://github.com/twosigma/beaker-notebook/issues/1569


missing packages in HA docker

running HA within docker, after installing pyscript via HACS i get following errors:
homeassistant  | ERROR: Could not find a version that satisfies the requirement croniter==1.3.4 (from versions: none)
homeassistant  | ERROR: No matching distribution found for croniter==1.3.4

any suggestion how to solve this?

I hit this error occasionally, and it sounds silly, but a container restart usually fixes it for me.

I'm also having this issue, and have not figured out how to solve it.  I have tried installing the missing pip packages from the shell and they do install fine.  I'm wondering if pyscript is wanting specific versions that have now been deprecated

I'm also having this issue, and have not figured out how to solve it. I have tried installing the missing pip packages from the shell and they do install fine. I'm wondering if pyscript is wanting specific versions that have now been deprecated

How are you able to install via pip from the shell? That errors out for me.


Food turns red during the frightened mode.

It's hard for the user to figure out when the Frightened mode ends. It would be cool if the food turns red while the fright mode is true.

Isn't the color of the ghost tell whether it is frightened or not? Why extra visual cue of making the food red?
When the 4 ghosts become normal color from blue, it means the Frightened mode has ended.

Because it looks cooler visually? Just purple ghosts looks boring.
On Fri, Apr 5, 2019, 11:42 AM Shivang Tripathi<EMAIL_ADDRESS>wrote:

Isn't the color of the ghost tell whether it is frightened or not? Why
extra visual cue of making the food red?
When the 4 ghosts become normal color from blue, it means the Frightened
mode has ended.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/pesto-students/batch5-pacman/issues/142#issuecomment-480160005,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ArMADJoJ8-pZYY09fPJgJHeWDroZsHQdks5vdulBgaJpZM4ceLqm
.


Parsing dates in non-ISO format

I have code that does this:
var d = new Date('9/8/18');
// Do something with d.

However, Duktape cannot parse this date correctly and creates an invalid Date object.
I saw this issue: https://github.com/svaarala/duktape/issues/712 but I don't know what's the current status of it. Is it implemented, at least on Unix platforms? What'd be the best way to have this feature at least only for Unix platforms? Thanks

You can provide a custom Date parser via DUK_USE_DATE_PARSE_STRING. See https://github.com/svaarala/duktape/blob/master/doc/datetime.rst#external-date-providers.

As for what's the best parser for parsing a wide variety of different formats, I don't have a recommendation for that. For Unix platforms Duktape automatically uses strptime() with %c:
       %c     The date and time representation for the current locale.

This works e.g. with:
duk> new Date('Sun Sep 23 17:27:23 2018')
= "2018-09-23T14:27:23.000Z"

But it comes down to the locale settings and strftime/strptime in the platform.

Thanks.

If you end up with a good solution which accepts a wide range of Date formats, it'd be nice to hear :)

@jcmerlin Any update on this issue?

You can run/embed moment.js. Works fine.

Yeah, that's true - but it may not be a possible solution if the Date built-in specifically has to accept the locale specific formats (e.g. if you have an existing code base you don't control).


Close button on modal overlaps with content

When modal is used with no margin or padding and with a close button, the button overlaps with the content,  because 100% of the height and width are required along with the close button, the styling breaks and the button position is somewhere between the content.

Currently, the position of the close button in the Modal component of Litmus-ui has a position: absolute which was set as per then available Figma designs in Litmus. If for the given use case the overlapping can be avoided using padding then this issue can be closed as the current styling of the Modal component has been made generic to serve larger usecases. cc: @arkajyotiMukherjee

We'll have a discussion regarding the modals with @mallick370 since the designs have changed quite a lot since our last implementation of the modals. You might want to join if you have suggestions to give @ishangupta-ds @whitetiger1399.

sure @arkajyotiMukherjee i had to use a negative padding/margin for this button while fixing the yaml editor in the modal as the close button came over the content (area) of the editor itself. cc: @mallick370 @whitetiger1399

Currently, the position of the close button in the Modal component of Litmus-ui has a position: absolute which was set as per then available Figma designs in Litmus. If for the given use case the overlapping can be avoided using padding then this issue can be closed as the current styling of the Modal component has been made generic to serve larger use-cases. cc: @arkajyotiMukherjee

I guess the first concern should be implementing something as per the design rather than serving the larger use-case. @whitetiger1399 As @arkajyotiMukherjee mentioned the designs have changed and also the previous design had the close button for editor modal at a different position where the current absolute style won't work no matter how much the positive padding or margin is given. I guess the earlier implementation was not validated / verified against all use-cases from the figma file.


feat: parse commandline args

fixes #734
fixes #157
I decided to not add any arg handling library as we are already
heavy on deps and I don't expect much cli options for now
TODO:

[ ] support for single files as cli arg
[x] turns out it wasn't working because \\wsl.localhost doesn't exist

[x] terminal workdir should be same as path from args
[x] indicate that it's opened in WSL

Why not use clap?

Why use clap?

Because it's robust, very straightforward and comes with numerous features. For instance, with clap, there is no need to implement --help or --version. Especially, --help has to be kept in sync with the actual implementation, when doing hand rolled argument parsing...

Because it's robust, very straightforward and comes with numerous features. For instance, with clap, there is no need to implement --help or --version. Especially, --help has to be kept in sync with the actual implementation, when doing hand rolled argument parsing...

Did you read what I wrote in first post though?

Yes, but it seems arbitrary. Laying groundwork by introducing an implementation that is hard to maintain, just to avoid a fundamental dependency, is counterproductive.

I don't see a reason to shove a dependency for whatever basic functionality we introduce.
If we will have an advanced usecase that will benefit from argument parsing library, then
it will be appropriate time to introduce such library. Now is not the time, we have 2 flags
and one arg.

@panekj Is this PR all ready now?

@panekj Is this PR all ready now?

Yes, unless you have any objections towards current implementation?