Versions are old?

The sbt version (play run) and play framework versions are both relatively old.
Is there any specific reason?

I created this project when I was building with Play, but I have since been working with it less. The versions have fallen out-of-date because I use Play rarely now.
I am happy to accept pull requests if you are familiar with upgrading versions.

"I use Play rarely now."
What are you using more of instead of Play?

@JohnReedLOL My Play usage was short-lived, hence this repo seeing little attention. Rails is my web framework of choice, but I am working primarily in Node and JavaScript at the moment (on the Nuclide IDE project).

@ssorallen I'm kind of split between using your tool and just using Node and doing everything (Elasticsearch, frontend, backed) with Javascript/JSON. The thing is I really don't like Javascript all that much (I don't have auto-complete and I can't remember/learn all the function names so I end up just copy-pasting everything)

This is now on the 2.5.x release of Play thanks to #10.


NPM package using getContext/setContext doesn't work during SSR dev

Describe the bug
I have distilled the issue to this:

Create an npm package that exposes a function that uses setContext or getContext
Make sure that repo does not have svelte as a direct dependency but only as peerDependency (or not even that)
Import the package and use the function
It crashes with: Function called outside component initialization

This only happens as npm package, using a local dependency works fine.
Reproduction
I tried reproducing in a REPL but it works fine, that's why I assume it's a Svelte Kit issue.
Here is the minimal reproduction repo: https://github.com/enyo/context-issue
See the issue immediately:
git clone https://github.com/enyo/context-issue.git
cd context-issue/svelte-kit-app
npm install
npm run dev

The repo contains the package, where the dist/index.js has this content:
import { setContext } from 'svelte';

const testSetContext = () => setContext('test', 'value');

export { testSetContext };
//# sourceMappingURL=index.js.map

and a svelte kit app that uses it.
Logs
No response
System Info
System:
    OS: macOS 12.3.1
    CPU: (10) arm64 Apple M1 Pro
    Memory: 293.67 MB / 32.00 GB
    Shell: 5.8 - /bin/zsh
  Binaries:
    Node: 17.9.0 - ~/.nvm/versions/node/v17.9.0/bin/node
    Yarn: 1.22.18 - ~/.nvm/versions/node/v17.9.0/bin/yarn
    npm: 8.5.5 - ~/.nvm/versions/node/v17.9.0/bin/npm
  Browsers:
    Chrome: 102.0.5005.61
    Firefox: 100.0.2
    Safari: 15.4
    Safari Technology Preview: 15.4
  npmPackages:
    @sveltejs/adapter-auto: next => 1.0.0-next.50
    @sveltejs/kit: next => 1.0.0-next.347
    svelte: ^3.44.0 => 3.48.0

Severity
blocking all usage of SvelteKit
Additional Information
No response

It may be improved by changing this code
https://github.com/sveltejs/vite-plugin-svelte/blob/main/packages/vite-plugin-svelte/src/utils/options.ts#L324-L346
to also add js-libraries to ssr.noExternal during dev. Right now the  else block of isBuild && ssr removes them.
But you mention that you ran into other issues with noExternal. Can you elaborate on them?

One thing that still confuses me a bit is that this seems to be causing an error only with packages from npm, a local workspace package with a very similar setup is working just fine: https://github.com/sveltejs/vite-plugin-svelte/blob/main/packages/e2e-tests/kit-node/src/routes/index.svelte#L26
cc @bluwy

I am a bit stumped by this. Doesn't that mean that no npm dependency can use a context at the moment? If that's the case I'm surprised this isn't higher on the priority list with more people running into the issue.
Is it because there aren't many packages that are using setContext or is there something wrong with my package?

Adding it to ssr.noExternal fixes it for most people. You didn't share what issues this causes for you.

I'm been checking this bug on and off, and it seems like this is a bug that we've missed in our test, even though we test the context api too, but we're not installing it locally as an npm package which hides the error.
From what I can see, in Vite SSR, your source code that imports setContext (including when you import the package via relative path), Vite resolves the import path to /absolute /path/to/node_modules/svelte/internal/index.js.
When letting Node use it's resolve algorithm, it resolves to /absolute /path/to/node_modules/svelte/internal/index.mjs. Notice the file extension difference, it's the reason why the error appeared as they are two separate modules being loaded.
I can re-confirm that Node uses the .mjs variant via import.meta.resolve('svelte/internal'). So Vite is inconsistent here, and the reason is because Svelte (for some reason) has a package.json at svelte/internal/package.json. Vite reads that package.json, and because it imitates Node's resolution, doesn't read the module exports, so it reads main instead.
So how does Node still get the .mjs version, that because Vite's "get nearest package.json" logic isn't compliant with Node's. See https://nodejs.org/api/esm.html#resolver-algorithm-specification.

If pjson is not null and pjson.exports is not null or undefined, then
Return the result of PACKAGE_EXPORTS_RESOLVE(packageURL, packageSubpath, pjson.exports, defaultConditions).

svelte/internal/package.json's exports is undefined, it should continue to search for package.json up the parent directory.
So I think this is a Vite issue, and not something vite-plugin-svelte can fix at the moment. Other than the workaorund of ssr.noExternal, which should be fine to apply.

I have an alternate confirmation of what @dominikg suggested above is working. I distribute a Svelte component library by NPM and while I'm still getting up to speed on Vite a consumer of my lib tried out Vite w/ slightly older versions. The same getContext / setContext issue described above popped up. In testing I upgraded their repo to<EMAIL_ADDRESS>and<EMAIL_ADDRESS>and it is fixed. Cheers!

Thanks for confirming


au body target

this bit of CSS causes unusual behaviour.
https://github.com/govau/design-system-components/blob/2d6ea8a23d4023602152967c7d43ad0c57407c7c/packages/body/src/sass/_module.scss#L68-L71
For example in the skip link component when an item is focused on, it remains focused.
To recreate

See the live example
Press tab and click one of the skip link items
Press tab again to focus on another element.
The skip link anchor remains in focus

@gordongrace could you please mention why this was closed? Or if there was a PR that fixed this issue, could you please reference the number.

"Close" issue button is far too close to the "close popover" function when viewing issue in GitHub Projects ;)


nvm always installs global packages to the latest version

Operating system and version:
MacOS High Sierra 10.13.6

nvm debug output:

nvm --version: v0.34.0
$TERM_PROGRAM: Apple_Terminal
$SHELL: /bin/bash
$SHELL: /bin/bash
$SHLVL: 1
$HOME: /Users/ryan.mcconnell
$NVM_DIR: '$HOME/.nvm'
$PATH: $NVM_DIR/versions/node/v11.10.0/bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin
$PREFIX: ''
$NPM_CONFIG_PREFIX: ''
$NVM_NODEJS_ORG_MIRROR: ''
$NVM_IOJS_ORG_MIRROR: ''
shell version: 'GNU bash, version 3.2.57(1)-release (x86_64-apple-darwin17)'
uname -a: 'Darwin 17.7.0 Darwin Kernel Version 17.7.0: Thu Dec 20 21:47:19 PST 2018; root:xnu-4570.71.22~1/RELEASE_X86_64 x86_64'
OS version: Mac 10.13.6 17G5019
curl: /usr/bin/curl, curl 7.54.0 (x86_64-apple-darwin17.0) libcurl/7.54.0 LibreSSL/2.0.20 zlib/1.2.11 nghttp2/1.24.0
wget: not found
git: /usr/bin/git, git version 2.17.2 (Apple Git-113)
grep: /usr/bin/grep, grep (BSD grep) 2.5.1-FreeBSD
awk: /usr/bin/awk, awk version 20070501
sed: illegal option -- -
usage: sed script [-Ealn] [-i extension] [file ...]
       sed [-Ealn] [-i extension] [-e script] ... [-f script_file] ... [file ...]
sed: /usr/bin/sed,
cut: illegal option -- -
usage: cut -b list [-n] [file ...]
       cut -c list [file ...]
       cut -f list [-s] [-d delim] [file ...]
cut: /usr/bin/cut,
basename: illegal option -- -
usage: basename string [suffix]
       basename [-a] [-s suffix] string [...]
basename: /usr/bin/basename,
rm: illegal option -- -
usage: rm [-f | -i] [-dPRrvW] file ...
       unlink file
rm: /bin/rm,
mkdir: illegal option -- -
usage: mkdir [-pv] [-m mode] directory ...
mkdir: /bin/mkdir,
xargs: illegal option -- -
usage: xargs [-0opt] [-E eofstr] [-I replstr [-R replacements]] [-J replstr]
             [-L number] [-n number [-x]] [-P maxprocs] [-s size]
             [utility [argument ...]]
xargs: /usr/bin/xargs,
nvm current: v11.10.0
which node: $NVM_DIR/versions/node/v11.10.0/bin/node
which iojs:
which npm: $NVM_DIR/versions/node/v11.10.0/bin/npm
npm config get prefix: $NVM_DIR/versions/node/v11.10.0
npm root -g: $NVM_DIR/versions/node/v11.10.0/lib/node_modules

nvm ls output:

        v11.1.0
        v11.9.0
->     v11.10.0
         system
default -> 11.1.0 (-> v11.1.0)
node -> stable (-> v11.10.0) (default)
stable -> 11.10 (-> v11.10.0) (default)
iojs -> N/A (default)
unstable -> N/A (default)
lts/* -> lts/dubnium (-> N/A)
lts/argon -> v4.9.1 (-> N/A)
lts/boron -> v6.16.0 (-> N/A)
lts/carbon -> v8.15.0 (-> N/A)
lts/dubnium -> v10.15.1 (-> N/A)

How did you install nvm? (e.g. install script in readme, Homebrew):
install script in readme

What steps did you perform?

Load an earlier version of node, e.g. v11.1, using nvm
run npm install prettier -g,

What happened?

I enter prettier and I get -bash: prettier: command not found.
If I then switch to v11.10.0, without installing the package again,  prettier is available in that version, but still not in the version used to install the package.
This is the case for any package I attempt to install globally, not just prettier. Also not just the case when installing from v11.1, but any version I've tried.
Even if I rm -r 11.10.0 from the node versions inside the .nvm directory and then install from a different version, a v11.10.0 directory is created containing the node_modules directory. The package remains inaccessible from the installing version of node.
I have also tried installing with nvm install 10.6 --reinstall-packages-from=11.10 and nvm reinstall-packages 11.10 after successfully installing the package in 11.10.0.

What did you expect to happen?
The global package to be available on the version of node from which it was installed.

Is there anything in any of your profile files (.bashrc, .bash_profile, .zshrc, etc) that modifies the PATH?

.bashrc:
export NVM_DIR="$HOME/.nvm" [ -s "$NVM_DIR/nvm.sh" ] && \. "$NVM_DIR/nvm.sh"  # This loads nvm [ -s "$NVM_DIR/bash_completion" ] && \. "$NVM_DIR/bash_completion"  # This loads nvm bash_completion
.bash_profile:
if [ -f ~/.bashrc ]; then    source ~/.bashrc fi

There's a few questions here.
Global packages are per node version - they are not shared across them. Which means, you have to use nvm reinstall-packages or nvm install --reinstall-packages-from= or default-packages or manually npm install -g them if you want them available.
As far as "the latest version", the reinstall-packages mechanism preserves the same version number that's installed; and default-packages uses whatever you've specified in that file.
The implication here, however, is that you've got v11.10.0 hardcoded somewhere in your PATH, or in ~/.npmrc, or in your profile files. Is there a chance you've monkeyed a bit with that in your bashrc or bash_profile?

A hardcoded value in ~/.npmrc was the issue. I must've set v11.10.0 as the prefix when I was trying to get rid of the prefix warning in the integrated terminal in vscode last week, opening up this can of worms in the process. Removing the prefix line solved it.
Thank you so much.


More specs for RecoveryAddress and generate docs for modules

Motivation
This PR adds more specifications to RecoveryAddress.move. I commented out some specs that would cause the prover to hang. Some spec functions are added to VASP and LibraAccount to help prove specs in RecoveryAddress.
Have you read the Contributing Guidelines on pull requests?
Yes.
Test Plan
cargo test

:umbrella: The latest upstream changes (presumably 783d8ae733aa7c848c00e620947ca92afee8bd97) made this pull request unmergeable. Please resolve the merge conflicts.

:umbrella: The latest upstream changes (presumably 0ae6d629f3609ed6f787fd78526c3d7729bffdc0) made this pull request unmergeable. Please resolve the merge conflicts.

@bors-libra r=wrwg

:pushpin: Commit 57fcb9b has been approved by wrwg

:lock: Merge conflict

:umbrella: The latest upstream changes (presumably 95c426b72f15effb97908de8b3dd58846ac3085c) made this pull request unmergeable. Please resolve the merge conflicts.

@bors-libra r=wrwg

:pushpin: Commit 5eafe8d has been approved by wrwg

:hourglass: Testing commit 5eafe8db7525ff5ffdef2afe310838eefaaf663e with merge 26a0654cc1e2f8266736a4d4930f31a03b6ccecd...

:sunny: Test successful - checks-actions_land_blocking_test, checks-circle_commit_workflow
Approved by: wrwg
Pushing 26a0654cc1e2f8266736a4d4930f31a03b6ccecd to master...


Create airport table

Since we reference airports quite a lot in many tables, it would be a good idea to store airports in a table. We can store other data about airpots as well, for example the airport name and location using coordinates. This might be important for drawing of maps in the future, too.
We need a source of data, of all ICAO airports worldwide. An option seems to be: https://ourairports.com/data/

@Konrad00 Could you have a look at this and tell me if this is okay or if I am missing something. Thank you.


git-lfs not allowed on public forks

seems to be a policy on github.
after making the fork, it can be renamed, and then a new blank one created with the same name (fastai-binder-app-template).
then the 'git push' works, and invokes git-lfs perfectly.
original error:
batch response: @davecampbell can not upload new objects to public fork davecampbell/fastai-binder-app-template    error: failed to push some refs to 'git@github.com:davecampbell/fastai-binder-app-template.git'

Thanks for the comment, Dave!
Yeah I found this issue in git-lfs which makes it (I think) more of a policy than a bug (its enabled in Github's enterprise edition) .
I'll update the docs to mention this issue.
Best regards,
Butch


Added Project Gold-Price Prediction

PR accepted @SideWinder1999
Successfully merged to CART repo.
Need to Star this repo incase not done.
🚀🚀👍


Rewrite tests to not use flash classes

It looks like some tests may depend on regular Flex classes and those tests should be rewritten or made optional or put in a profile.

This seems to be working


Weird fix for frame rate doubling after second created window.

I have no idea why this fixes https://github.com/bkaradzic/bgfx/issues/1867
I'm not a metal expert so take this with pull request with a grain of salt. Maybe @attilaz has a better alternative to this?

I have checked this with the latest bgfx on a macbook air 2020 with macos big sur 11.0.1 and xcode 12.4.
With the PR 22-windows works correctly: limiting to 60fps in debug mode, but in release mode the extra nextDrawable has no effect.
So the sample runs at 120 fps in release mode.
It is interesting to see that this has some effect on the frame limiting problem. Getting two drawables instead of one and see the framerate go from 120fps to 60fps makes sense. But I think it could limit the cpu/gpu parallelism in other cases.

It works in release too. Sorry about the confusion. Xcode projects are strange. It seems to me that 'examples' are always linked against debug bgfx lib even if I choose 'examples release' scheme. So when I choose 'examples release' it  builds release libs, but not using them...
But I am still a little concerned about that we can loose performance with the extra nextDrawable call. Maybe do this only when we have multiple windows and vsync enabled?
The syntactic difference between [m_metalLayer nextDrawable] and m_metalLayer.nextDrawable is also strange. But they seem to be meaning the same thing.

Yeah I only see nextDrawable as a function so the ‘.’ access confused me a bit. I’m not really an objective c dev though.

Method call syntax would be better. But according to docs.

Getting a value using somePerson.firstName is the same as using [somePerson firstName]

(https://developer.apple.com/library/archive/documentation/Cocoa/Conceptual/ProgrammingWithObjectiveC/EncapsulatingData/EncapsulatingData.html)
I have tried to limit the usage of extra 'nextDrawable'. I have modified flip instead of currentDrawableTexture. It seems to me that only the main framebuffer needs the extra call. I call it only when needed (vsync is enabled and rendering to multiple windows). @mtytel Can You check if this works for you? thanks
I still don't get why this helps. I assume this is a workaround of a strange behaviour in metal displaySync with multiple presentDrawables. But If this doesn't affects the more common cases I think it can be added as a 'solution' to bgfx.
I wouldn't like to have an extra nextDrawable in our iOS projects for example.
@bkaradzic What do You think?
 		void flip() override
		{
			if (NULL == m_commandBuffer)
			{
				return;
			}

			for (uint32_t ii = 0, num = m_numWindows; ii < num; ++ii)
			{
				FrameBufferMtl& frameBuffer = ii == 0 ? m_mainFrameBuffer : m_frameBuffers[m_windows[ii].idx];
				if (NULL != frameBuffer.m_swapChain
				&&  frameBuffer.m_swapChain->m_drawableTexture)
				{
					MTL_RELEASE(frameBuffer.m_swapChain->m_drawableTexture);

					if (NULL != frameBuffer.m_swapChain->m_drawable)
					{
						m_commandBuffer.presentDrawable(frameBuffer.m_swapChain->m_drawable);
						MTL_RELEASE(frameBuffer.m_swapChain->m_drawable);

						if ( ii == 0 && m_numWindows > 1 && (m_resolution.reset&BGFX_RESET_VSYNC))
							[frameBuffer.m_swapChain->m_metalLayer nextDrawable];
					}
				}
			}

			m_cmd.kick(true);
			m_commandBuffer = 0;
		}

So the original problem is that the frame rate doubles if you've ever had multiple windows open even if you close all but one. With this change if you create a second window and close it the frame rate will then jump to 120.

Alright traced this to another area. If you disable the default triple buffering and make it double buffering it also fixes this issue. Not sure this is something you would want to set though. Hoping I can find a different reason this is happening..
#if BX_PLATFORM_OSX #if __MAC_OS_X_VERSION_MAX_ALLOWED >= 101300 		if (@available(macOS 10.13, *)) 		{ 			m_metalLayer.displaySyncEnabled = 0 != (_flags&BGFX_RESET_VSYNC); 		} 		if (@available(macOS 10.13.2, *)) 		{ 			m_metalLayer.maximumDrawableCount = 2; 		} #endif // __MAC_OS_X_VERSION_MAX_ALLOWED >= 101300 #endif // BX_PLATFORM_OSX

This seems better to me. Can we set 'm_metalLayer.maximumDrawableCount = 2; only when vsync is enabled? But vsync can be modified with reset, so it should handle that case as well.

Alright how does this look?

👍 I will test this on my Mac and if it works this is fine by me.

Setting m_metalLayer.maximumDrawableCount to 2 works for me.

Put up a new version that uses numBackBuffers clamped to [2, 3] which is the accepted range for maximumDrawableCount.

I don't quite understand how maxFrameLatency should map to maximumDrawableCount. Is it just a 1 to 1 value?
The default here is also 3 which creates the original bug this change is trying to prevent.

I don't quite understand how maxFrameLatency should map to maximumDrawableCount. Is it just a 1 to 1 value?

It's 1:1, you can now use bgfx::Init structure to specify 2 instead of 3 there.


Adding the capability to dismiss the preview using a button

Hey there. I like this library and use it in an app. However I thought that it would be nice to have the capability to dismiss the preview with a button instead of tapping on the background.
I've added some code that does that. It might need to be looked at and checked by the creator to discuss if it needs some adjustments etc.
Cheers

Hi !
This pull request is really needed I just had a meetup with this request.

I saw in documentation there is now option to add a close button.
maybe this pr should be closed now?

@Alexookah Agreed. Thanks for the reminder 😃


Eslint

Solving #10 - it's a pretty lenient version of the airbnb eslint config.
Even bigger change: Everything's using 2 space indentation now!

Coverage remained the same at 100.0% when pulling 9b764521b9ce00c401944172473d204ca16cef60 on eslint into af2cedf922809cf847a30534ad77b913ab50cb92 on master.


Remove lodash as a dependency

Lodash is included to support forEach and map, all of which I think we can assume are supported natively.

Fixed with #12


Update Modrinth game version

The latest Modrinth release for 1.20.1 has the game version set as 1.19.4, breaking auto updaters in launchers like Prism Launcher. This updates the listed game versions for future builds; however, the existing build will need to be updated manually.

Fixed on modrinth, ill have to be more careful in the future


Hapi 8 and updated docs

Any word on testing with Hapi 8+?
Also, updated docs?
My team is looking to implement oauth for our API so we may be able to help contrib to this module.
Cheers.

We'd love a PR!  I don't expect it'll take many changes.  I will need to update this to hapi 8 soon regardless (since my team would like to upgrade our oauth service)!  Ideally the update should support hapi 7 and 8.
As an aside, if you're building an API, maybe take a peek at dogwater (integration with Waterline ORM) and bedwetter (model-aware API builder based on Github's API style).

Thanks for the suggestions!

This project still continue?

@marcosbergamo indeed!

Tks =D

Is there any eta on support for Hapi 8.x?  Thanks

There's no ETA at the moment, but I would certainly take a PR.  I've made a new placeholder issue for this at #6 and assigned it to the 2.0.0 milestone.

Hey all, just updated this for hapi8 and hapi9.  I'd like to improve docs and do some testing before publishing 2.0.0, but please feel free to give it a try.  Closed in #6, PR #8.


Pending test cases

Below is a list of test cases we just added on test lodge, for all remaining required items that had no test cases linked to them.
These test cases need to be expanded and clarified as currently is unclear how we should proceed with running them:

TC433
TC436
TC437
TC441

Moved from: https://circles.threefold.me/project/test-tfgrid3/issue/151

Test cases Updated.
TC433
TC433 was updated and test steps were added according to the requirement that it verifies REQ191
TC436, TC437, TC441
After further investigation and discussion with @xmonader These cases were removed from their test suites as they were not supposed to be test cases and they're just documentation requirements.
Please reopen this issue if there's a problem with the mentioned cases.


MMM-Multimonth License issues?

Per your issues page, My license info is all messed up - can you look at my package.json and figure out why? It seems saying my license is NOASSERTION - should be "MIT-Modern-Variant"
Thanks.

Nevermind, I just noticed it's looking for the LICENSE file, not LICENSE.md

My script uses the GitHub API and not the LICENSE file directly. NOASSERTION means that GitHub does not recognize the license from the license file text. Under which license do you want to publish your module?

I actually was going to reopen this later today. I like
the MIT-Modern-Variant
On Mon, May 13, 2024 at 1:38 AM Kristjan ESPERANTO @.***>
wrote:

My script uses the GitHub API and not the LICENSE file directly.
NOASSERTION means that GitHub does not recognize the license from the
license file text. Under which license do you want to publish your module?
—
Reply to this email directly, view it on GitHub
https://github.com/KristjanESPERANTO/MagicMirror-3rd-Party-Modules/issues/30#issuecomment-2106979389,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AKVL3DA7FXKRF5X7PLHOXMDZCB3ZPAVCNFSM6AAAAABHRIUGSKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMBWHE3TSMZYHE
.
You are receiving this because you modified the open/close state.Message
ID: <KristjanESPERANTO/MagicMirror-3rd-Party-Modules/issues/30/2106979389@
github.com>

Status: Still broken.
LICENSE file:
Copyright © 2020-2025 Brendan Keyport. All rights reserved.

Permission is hereby granted, without written agreement and without license or royalty fees, to use, copy, modify, and distribute this software and its documentation for any purpose, provided that the above copyright notice and the following two paragraphs appear in all copies of this software.

IN NO EVENT SHALL BRENDAN KEYPORT et al.  BE LIABLE TO ANY PARTY FOR DIRECT, INDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OF THIS SOFTWARE AND ITS DOCUMENTATION, EVEN IF BRENDAN KEYPORT et al  HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

BRENDAN KEYPORT et al. SPECIFICALLY DISCLAIMS ANY WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE SOFTWARE PROVIDED HEREUNDER IS ON AN "AS IS" BASIS, AND BRENDAN KEYPORT et al.  HAS NO OBLIGATION TO PROVIDE MAINTENANCE, SUPPORT, UPDATES, ENHANCEMENTS, OR MODIFICATIONS.

https://spdx.org/licenses/MIT-Modern-Variant.html it the template I used.

Somehow I feel that the modern MIT version is worse than the classic one...
Please try my PR. It could be the year, the double spaces and/or the ‘et al.’.

Saddly I doubt that this solved the problem. The title still only says Licence and not MIT licence as in the MagicMirror repo.
I'm afraid this is a GitHub problem. GitHub doesn't seem to recognise the MIT-Modern-Variant yet.

Alright, it's switched over to the MIT regular license (Grumble)

Okay, now MIT is also displayed for your module 🙂. Too bad that GitHub can't handle the "modern" version yet.


Java Question: how describe List/Array of composite type in XML?

I need to have next model
User{
Long id,
String name,
List<Address> addresses
}

Address{
Long id,
String address
}

Is it possible in current specification and implementaion?

Composite cannot contain variable length data such as a string. You could model this with groups. Look the car example in the samples module.


Suggestion: Search/ Replace in all files

VSCode Version: 1.11.2
OS Version: Win10

Steps to Reproduce:

CTRL+F  / CTRL +H
Search or Replace should be available also in all files from opened project/ folder  (similar to Visual Studio)


Ignore tables without table_type parameters while loading all iceberg table from Glue and Hive catalog (#1331)

same problem with #1258


Backport: Support for North Central US in AKS

Backport rancher/rancher#19853

Version: v2.2.4-rc1
I can confirm the addition of "North Central US" region for AKS.

The query to aksVersions looks correct and the cluster config looks good as well (azureKubernetesServiceConfig) I see location: "northcentralus" in the cluster creation request and in the API.
My AKS cluster with this Location provisioned successfully and shows as the correct location in Azure web console.
The original issue mentions West Central US support as well and this is tracked separately in #20069 as it is not yet available.


Add option to ignore hardlinks in dsync, dcmp and dwalk

This is a proposal to add -H, --nohardlink option on dsync, dcmp and dwalk to ignore hardlinks when walking in files tree.
The rationale is to avoid producing multiple copies of the same inodes which could result in synchronized files tree requiring much more storage consumption.
The corresponding manpages are also updated accordingly.

Not that if the source filesystem is Lustre and the client is mounted with user_fid2path or as root, you can use lfs path2fid --parents (or llapi_path2parent() equivalent) to generate a list of up to 100 parent directory FIDs for a hard linked file, and/or lfs fid2path (or llapi_fid2path() equivalent) to generate the pathnames for the hard links to a file.
This would allow efficiently maintaining the hard links in the target filesystem without having to make a full separate copy of the file, or scan the source tree trying to find the links.
Alternately, I believe tar will keep an in-memory list of inode numbers with hard links and if they are encountered again during tree traversal it will store a hard link instead of the full file.

Not that if the source filesystem is Lustre and the client is mounted with user_fid2path or as root, you can use lfs path2fid --parents (or llapi_path2parent() equivalent) to generate a list of up to 100 parent directory FIDs for a hard linked file, and/or lfs fid2path (or llapi_fid2path() equivalent) to generate the pathnames for the hard links to a file.
This would allow efficiently maintaining the hard links in the target filesystem without having to make a full separate copy of the file, or scan the source tree trying to find the links.
Alternately, I believe tar will keep an in-memory list of inode numbers with hard links and if they are encountered again during tree traversal it will store a hard link instead of the full file.

Hi @adilger ,
This patch came from CEA with the Lustre filesystem.
I'am totally agree, that's what we did, but we also need to exclude hardlinks to make a full copy of the filesystem without hardlinks and then apply your method.
This is a simple patch, the hardway would be to keep track of each inode in the mpifileutils tools and compare if we already copied this inode or not. If it's already present, make a hardlink, else make a copy.


Improve CtrlP speed with cache and Ag

With cache CtrlP works really fine in big projects. If you want refresh the cache just press F5 with CtrlP opened.
CtrP use vim native globpath() for search files. If you have Ag installed in your machine, search files will be more fast. See the explanation: http://stackoverflow.com/a/22784889

Sounds good for me. :+1:


Create R date from string by dplyr::mutate

When I use Sparklyr and dplyr to create a R date variable from a string, the return value is always NA. Can you help me with this? I don't have a replicable example for you but try my best to show the process.
The raw field was read into Spark from a parquet file:
a <- spark_read_parquet(sc, name = "a", "/blahblah")
There is a field called 'period' with value like this and it is a string:
01JAN19
02JAN19
03JAN18
....
I use the following to create a new field called 'dt_period' to convert string to R date so that I can compare different dates:
a <- a%>%
mutate(dt_period= to_date(period,"%d%b%y"), year_period = year(dt_period))
When I pull 10 records to double check, it gives me errors:
a %>%
select(period,dt_period,year_period) %>% compute() %>% sample_n(10) %>% collect
The two newly created fields show 'NA' as their value.
I also tried dmy function from lubridate package but failed:
a %>%
mutate(dt_period = dmy(period), year_period = year(dt_cur_period))
Log:
Error : org.apache.spark.sql.AnalysisException: Undefined function: 'DMY'. This function is neither a registered temporary function nor a permanent function registered in the database 'default'.; line 4 pos 3361
at org.apache.spark.sql.catalyst.analysis.Analyzer$LookupFunctions$$anonfun$apply$15$$anonfun$applyOrElse$50.apply(Analyzer.scala:1396)
at org.apache.spark.sql.catalyst.analysis.Analyzer$LookupFunctions$$anonfun$apply$15$$anonfun$applyOrElse$50.apply(Analyzer.scala:1396)
at org.apache.spark.sql.catalyst.analysis.package$.withPosition(package.scala:53)
at
I also tried spark_apply():
a <- a%>%
spark_apply(function(dff) dplyr::mutate(dff, dt_period = lubridate::ymd(period), year_period = year(dt_period)))
Log:
Error : org.apache.spark.SparkException: Job aborted due to stage failure: Task 0 in stage 12.0 failed 4 times, most recent failure: Lost task 0.3 in stage 12.0 (TID 295, <IP_ADDRESS>, executor 3): java.lang.Exception: sparklyr worker rscript failure with status 255, check worker logs for details.
at sparklyr.Rscript.init(rscript.scala:106)
at sparklyr.WorkerApply$$anon$2.run(workerapply.scala:116)
Can you please help me to correctly create that date field?

writeLines("01JAN19\n02JAN19\n03JAN18", "dates.txt")

lirbary(sparklyr)
sc <- spark_connect(master = "local")

spark_read_text(sc, "dates.txt") %>%
  dplyr::mutate(
    month = switch(regexp_replace(line, "[0-9]", ""), JAN = 1, FEB = 2, MAR = 3),
    date_raw = regexp_replace(line, "[a-zA-Z]+", paste0("-0", as.integer(month), "-")),
    date = from_unixtime(UNIX_TIMESTAMP(date_raw, 'dd-MM-yy'))
  )

# Source: spark<?> [?? x 4]
  line    month date_raw date
  <chr>   <dbl> <chr>    <chr>
1 01JAN19     1 01-01-19 2019-01-01 00:00:00
2 02JAN19     1 02-01-19 2019-01-02 00:00:00
3 03JAN18     1 03-01-18 2018-01-03 00:00:00

Thanks a lot for prompt help.
I used your first way to try but getting the following error:
Error in UseMethod("escape") :
Error in UseMethod("escape") :
no applicable method for 'escape' applied to an object of class "function"
In addition: Warning message:
Named arguments ignored for SQL SWITCH
Any ideas?
BTW, why lubridate::dmy or to_date won't work here?

I actually find out if I use Spark SQL date function to_date and parsing my data through its corresponding format, in this case "ddMMMyy" could correctly give me R date.
With this, I will close this issue.


DCOS-55895: Support editing Quota limits for an existing top-level Group

Closes https://jira.mesosphere.com/browse/DCOS-55895
Testing

In `Config.dev:

  uiConfigurationFixture: {
    uiConfiguration: {
      features: {
        quota: true
...

Go to services page.
Create a group if there are none.
Verify that an edit action appears in the action dropdown for top-level groups.
Verify that an edit action appears in the top right dropdown after clicking on a top-level-group.
Verify that the edit modal works (you can go to the quota tab to confirm if the limits actually changed).
Verify that the edit action appears only for top-level groups.
Verify that the added tests make sense.

Trade-offs
None.
Dependencies
None.
Screenshots

@TattdCodeMonkey

A different action should send to a different route, and not use EditServiceModal.

Why? A group is still a type of service for us and I think the url "/services/detail/%2Fgroup-name/edit/" isn't wrong or misleading.

:tada: This PR is included in version 2.137.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Custom Music folder

Allow music to be loaded into a folder and the radio plays songs in order from that folder.

http://answers.unity3d.com/questions/468369/play-personal-music-from-a-specific-folder.html


In ChangeLog
https://github.com/googleads/google-ads-ruby/pull/330#discussion_r662992254
:

@@ -1,3 +1,9 @@
+13.0.0:

Removed support for v5.

Updated get_ad_group_bid_modifier example to limit number of results in query.

We don't need to mention any of this in the changelog. The examples aren't
bundled into the gem.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/googleads/google-ads-ruby/pull/330#pullrequestreview-698157972,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AUKNGKRWMJF2N6YLKN2FHH3TVWZN7ANCNFSM47WPVDRQ
.

In ChangeLog
<
https://github.com/googleads/google-ads-ruby/pull/330#discussion_r662992254
:

@@ -1,3 +1,9 @@
+13.0.0:

Removed support for v5.

Updated get_ad_group_bid_modifier example to limit number of results
in query.

We don't need to mention any of this in the changelog. The examples
aren't
bundled into the gem.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<
https://github.com/googleads/google-ads-ruby/pull/330#pullrequestreview-698157972
,
or unsubscribe
<
https://github.com/notifications/unsubscribe-auth/AUKNGKRWMJF2N6YLKN2FHH3TVWZN7ANCNFSM47WPVDRQ
.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/googleads/google-ads-ruby/pull/330#issuecomment-873183269,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AUKNGKWE64SJ753OPERFNHLTVYAVXANCNFSM47WPVDRQ
.


ACC-253.1 (Level AA)_ Listbox _ No visible label provided

v1.1 Internal Message Details
Internal Message:
Test Plan:	ACC SAP Kyma runtime 2024
Message Priority:	High
Affected UI	Listbox
Affected Check Point:	ACC-253.1
Short text:	ACC-253.1 (Level AA)_ Listbox _ No visible label provided
1.2 Application Details
Application Name	Kyma-dashboard
Technology:	SAP UI5
Component:
URL:	https://dashboard.stage.kyma.cloud.sap/cluster/garden-kyma-stage--c-7074971-external/kymamodules
Username/Password:	NA
1.3 Test Environment Details
Web browser:	Google Chrome Version 127.0.6533.89
Operating System:	Microsoft Windows 11 x64
Screen Reader:	JAWS 2024 Version 2024.2406.121 ILM
1.4 JIRA/SNOW Details
Issue:	Bug
Labels:	Accessibility
2 Screen Flow
•	Launch the application using given URL.
•	Select the ‘Link to Kyma dashboard’ from the Kyma Environment section on your SAP BTP subaccount page.
•	Go to KubeconfigURL:https://kyma-env-broker.cp.stage.kyma.cloud.sap/kubeconfig/DFEFE4E0-E202-4455-8A61-37511B4D7553
•	Click on  the link https://dashboard.stage.kyma.cloud.sap/clusters and select Connect.
•	Upload the kubeconfing file downloaded in the first step. You can either drag and drop it or select the upload icon to choose it from the device.
•	Next Step
•	Connect to cluster, A new screen get opens
•

Issue Type: Manual
Observed Behavior:
There is no visible label provided for the Listbox within the table ‘Nodes’.
Screenshot:

Expected Behavior:
All UI elements should have visible and meaningful label provided and it should associated with the UI. Meaningful label supports the user in entering data correctly.
ACC-253.1 (Level AA)_ Listbox _ No visible label provided.docx

Issue processing-09.2021 (2).docx


Added debug mode for clear console log

I use this module for creating about 100+ files.
It hard after that to find previous log info.

Thanks for the PR @igormalanyk!
I'd like to understand the motivation behind this changes. I understand why grunt.log.writeln might be a bit too much on your console, but I do not get why are you also wrapping all grunt.log.debug statements, those will only be shown when --debug option is passed to Grunt.
If I get it right, this PR could be done by just replacing grunt.log.writeln with grunt.verbose.writeln. With this change it is not needed to add a new option parameter since grunt already supports --verbose.

No response from PR author.


Create auto-generated reference docs for the Pipelines DSL

/assign @vicaire

This is done:
https://www.kubeflow.org/docs/pipelines/reference/sdk/
/close


"key values mismatch" when rebuilding nodes

Building a fresh node with your module using the DNS-01 mechanism with GoDaddy works mostly well.  However, if we destroy a node that had already received its certificate, chain, and key files, we are unable to rebuild that node because we end up with a mismatched certificate/key pair.  In my own testing, I was only able to rebuild an affected node by fully destroying both the affected node and the Puppet Server itself, then rebuilding them both!  This is obviously not an ideal workaround.
Steps to reproduce:

Build up a fresh Open-Source Puppet 5 Server with your module properly configured.
Attach and build an Apache HTTPd node that also uses your module and requests a Let's Encrypt certificate via the DNS-01 mechanism for an SSL-enabled vhost.
Note that after about 15 minutes and a few Puppet Agent runs on both the Puppet Server and the Apache HTTPd node, it works.  [Aside:  Please call this out in your README file; that it takes at least15 minutes and a minimum of 3 sequential Puppet Agent runs on the Puppet Server itself to actually obtain a signed certificate.  So, if an unattended Puppet Server runs its Agent only once per hour, it will take over 3 hours to obtain a signed certificate!]
Destroy the Apache HTTPd node.  We do this deliberately to simulate disaster and other dynamic cloud scaling scenarios.
Rebuild the Apache HTTPd node.
Encounter the intractable error, "key values mismatch" even after the 15 minute minimum delay and any number of Puppet Agent runs on the Puppet Server and Apache HTTPd node.

There is no readily-identifiable way to resolve this error.  I manually compared the private key and certificate files on the affected node and indeed, they are mismatched.  I tried destroying the old certificate files from /etc/acme.sh/* directories on the Puppet Server for the affected node and repeating the request sequence in hope that your module would re-request fresh copies of the files from GoDaddy, but this had no effect; in fact, the certificate files are never recreated on the Puppet Server.  This leaves me to suspect that you're caching the certificates in PuppetDB, which is cool except this needs to be clear in your documentation along with a direct means of flushing affected resources.
Please advise.

I also noticed that the node's private key doesn't seem to be collected on the Puppet Server; I couldn't find it anywhere.  This leads me to suspect your module doesn't cache the original private key.  Without it, whenever a node is destroyed and rebuilt, an entirely new private key will be automatically created which will -- of course -- never match the previously-signed certificate that your module will serve up from the Puppet Server.
If this is the case, then please start caching the right private keys with their signed certificates.  It is critical for a node to receive the correct pair.  Your module could easily pass the matching pair back to the requesting node no matter how many times it gets rebuilt.

If this is the case, then please start caching the right private keys with their signed certificates.

They are not cached on purpose. In my opinion the whole point of this module is a clear separation of concerns.
That being said I still have no idea how to fix the mismatch that occurs when rebuilding nodes, so I'm open for suggestions.

Since nobody has come up with a solution for this problem, I've added an entry to the README.


AWS Batch custom dashboards do not display any data

The following custom dashboards return no data in a client's PROD environment even when an AWS Batch calculation falls within the selected time horizon:

Batch-ECS-InstancesRegistration
Batch-Jobs-Placement
Batch-Jobs-states

Batch-ASG-Utilization and Batch-EC2-Capacity dashboards display the correct data and activity.

I had a similar issue where I found the Lambdas for those dashboards were erroring out with the following error message:
[ERROR] Runtime.ImportModuleError: Unable to import module 'app': No module named 'aws_embedded_metrics'
Traceback (most recent call last):

This was caused by the aws_embedded_metrics failing to package correctly. To resolve this issue, I recommend ensuring that you are using Python 3.9 and then running "sam build" ahead of sam deploy --guided.

I had a similar issue where I found the Lambdas for those dashboards were erroring out with the following error message:
[ERROR] Runtime.ImportModuleError: Unable to import module 'app': No module named 'aws_embedded_metrics'
Traceback (most recent call last):

This was caused by the aws_embedded_metrics failing to package correctly. To resolve this issue, I recommend ensuring that you are using Python 3.9 and then running "sam build" ahead of sam deploy --guided.

I got a same issue, but I've already been using python 3.9 and run sam build first. it doesn't work.


Added Routes description to react-router

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the master branch of freeCodeCamp.
[x] None of my changes are plagiarized from another source without proper attribution.
[x] My article does not contain shortened URLs or affiliate links.

If your pull request closes a GitHub issue, replace the XXXXX below with the issue number.
Closes #XXXXX

The changes being made via this PR are already present in the current version of this file, I'm henceforth closing it


Python 3.4 and PyCharm breakpoints when use_reloader=True

Running a flask application with debug=True (and thus, use_reloader=True) in Pycharm, breakpoints inside view functions don't work. Setting use_reloader=False works, but I miss the reloader. This works as expected when running on Python 2.7. I'm not sure if this is an issue on Flask, Werkzeug or Pycharm. Is there somebody with better insights on Werkzeug internals and  how the Pycharm debugger works that could help me with this?.

I have the same problem with python 3.3.5 and pycharm 3.4.1

There are no behavioral differences by Flask between Py2 and Py3.
I suppose that PyCharm doesn't correctly track the PID of the new process, but I'm not entirely sure. I don't think this is an issue Flask/Werkzeug should solve, but I'll leave this issue open anyway. Please refrain from adding :+1: though.

Just one more please :) Link to issue on pycharm tracker here:
https://youtrack.jetbrains.com/issue/PY-14864

Thanks for the link.

tbh i think pycharm should ship a own wsgi server with total controll over breakpoints and restarting
if thats not part of their flask/django/wsgianything integration anyway they are slacking

That'd be the most powerful solution, yes.

Seems to be fixed.  I can set a breakpoint in the view in the following example and the debugger activates correctly.
from flask import Flask

app = Flask(__name__)

@app.route('/')
def index():
    return 'Hello, World!'

app.run(debug=True)


OHRI-2002: Add All TB Clients Table in the Tuberculosis Treatment dashboard

[ ] Add All TB Clients Table in the Tuberculosis Treatment dashboard

[ ] The table will be placed in the All TB Clients tab in the Tuberculosis Treatment dashboard

@pirupius,  Please review this again. Thank you


Configuring Peatio exchange, Rake aborted

Hi im trying to install peatio exchange in ubuntu 12.04 LTS but when i try to deploy Bundle exec rake, they abort the instalation here is the report with the flag --trace,
thanks for all the Help.
N3rvi0zz0 Btctalk
arkhash@Darkhash:/usr/local/peatio$ bundle exec rake daemons:start --trace
rake aborted!
Psych::SyntaxError: (): did not find expected key while parsing a block mapping at line 6 column 3
/home/darkhash/.rbenv/versions/2.2.1/lib/ruby/2.2.0/psych.rb:370:in parse' /home/darkhash/.rbenv/versions/2.2.1/lib/ruby/2.2.0/psych.rb:370:in parse_stream'
/home/darkhash/.rbenv/versions/2.2.1/lib/ruby/2.2.0/psych.rb:318:in parse' /home/darkhash/.rbenv/versions/2.2.1/lib/ruby/2.2.0/psych.rb:245:in load'
/home/darkhash/.rbenv/versions/2.2.1/lib/ruby/gems/2.2.0/gems/figaro-0.7.0/lib/figaro.rb:21:in raw' /home/darkhash/.rbenv/versions/2.2.1/lib/ruby/gems/2.2.0/gems/figaro-0.7.0/lib/figaro.rb:17:in env'
/home/darkhash/.rbenv/versions/2.2.1/lib/ruby/gems/2.2.0/gems/figaro-0.7.0/lib/figaro/railtie.rb:7:in block in <class:Railtie>' /home/darkhash/.rbenv/versions/2.2.1/lib/ruby/gems/2.2.0/gems/activesupport-4.0.12/lib/active_support/lazy_load_hooks.rb:36:in call'
/home/darkhash/.rbenv/versions/2.2.1/lib/ruby/gems/2.2.0/gems/activesupport-4.0.12/lib/active_support/lazy_load_hooks.rb:36:in execute_hook' /home/darkhash/.rbenv/versions/2.2.1/lib/ruby/gems/2.2.0/gems/activesupport-4.0.12/lib/active_support/lazy_load_hooks.rb:45:in block in run_load_hooks'
/home/darkhash/.rbenv/versions/2.2.1/lib/ruby/gems/2.2.0/gems/activesupport-4.0.12/lib/active_support/lazy_load_hooks.rb:44:in each' /home/darkhash/.rbenv/versions/2.2.1/lib/ruby/gems/2.2.0/gems/activesupport-4.0.12/lib/active_support/lazy_load_hooks.rb:44:in run_load_hooks'
/home/darkhash/.rbenv/versions/2.2.1/lib/ruby/gems/2.2.0/gems/railties-4.0.12/lib/rails/application.rb:67:in inherited' /usr/local/peatio/config/application.rb:15:in module:Peatio'
/usr/local/peatio/config/application.rb:14:in <top (required)>' /usr/local/peatio/Rakefile:5:in require'
/usr/local/peatio/Rakefile:5:in <top (required)>' /home/darkhash/.rbenv/versions/2.2.1/lib/ruby/2.2.0/rake/rake_module.rb:28:in load'
/home/darkhash/.rbenv/versions/2.2.1/lib/ruby/2.2.0/rake/rake_module.rb:28:in load_rakefile' /home/darkhash/.rbenv/versions/2.2.1/lib/ruby/2.2.0/rake/application.rb:689:in raw_load_rakefile'
/home/darkhash/.rbenv/versions/2.2.1/lib/ruby/2.2.0/rake/application.rb:94:in block in load_rakefile' /home/darkhash/.rbenv/versions/2.2.1/lib/ruby/2.2.0/rake/application.rb:176:in standard_exception_handling'
/home/darkhash/.rbenv/versions/2.2.1/lib/ruby/2.2.0/rake/application.rb:93:in load_rakefile' /home/darkhash/.rbenv/versions/2.2.1/lib/ruby/2.2.0/rake/application.rb:77:in block in run'
/home/darkhash/.rbenv/versions/2.2.1/lib/ruby/2.2.0/rake/application.rb:176:in standard_exception_handling' /home/darkhash/.rbenv/versions/2.2.1/lib/ruby/2.2.0/rake/application.rb:75:in run'
/home/darkhash/.rbenv/versions/2.2.1/bin/rake:33:in `'
darkhash@Darkhash:/usr/local/peatio$

What's the output when you run the command without the --trace?

tkembo, did you manage to update the price?  my still 0.0  :-(

Hi and sorry I need to open another account, yesterday somebody still my laptop on the tube.
The comand  bundle exec rake daemons:start  without trace give me this output.
darkhash@Darkhash:/usr/local/peatio$ bundle exec rake daemons:start
rake aborted!
Psych::SyntaxError: (): did not find expected key while parsing a block mapping at line 6 column 3
/usr/local/peatio/config/application.rb:15:in <module:Peatio>' /usr/local/peatio/config/application.rb:14:in <top (required)>'
/usr/local/peatio/Rakefile:5:in require' /usr/local/peatio/Rakefile:5:in <top (required)>'
(See full trace by running task with --trace)
darkhash@Darkhash:/usr/local/peatio$
maybe i need to modify any yml appart from application and currencies?
Maybe because the blockchain didnt finish to sync?
as you see in the output I installed peatio in /usr/local/peatio not in /usr/local/share/peatio maybe Gems are looking in the wrong folder.
Thanks a lot in advance

Hi Darkhashmaster,
Have you solved this issue ?. I got same error when run bundle exec rake db:setup
Thanks

Hi guys, i've figured out what's happening here. This errors are all about errors in parsing config files.
Take a close look at them and be aware that indentaions(spaces) matters!


Create tests for src/drone-delivery/MessageParams.ts using jest.

first-timers-only
This issue is tagged :octocat: first-timers-only. It is only for people who have never contributed to open source before, and are looking for an easy way take their first steps.
Consider this your chance to dip your toe into the world of open-source, and get some bragging rights for writing code that makes drones fly, lets cars find charging stations, helps people and goods get from place to place, and more.
Find more first-timers-only issues from DAV Foundation here.
Thank you for your help :heart:
What is this project?
DAV (Decentralized Autonomous Vehicles) is a new foundation working to build an open-source infrastructure for autonomous vehicles (cars, drones, trucks, robots, and all the service providers around them) to communicate and transact with each other over blockchain.
As an organization that believes in building a large community of open-source contributors, we often create issues like this one to help people take their first few steps into the world of open source.
dav-js
This repo contains the DAV JavaScript SDK. This SDK allows developers to build applications and servers that connect to the DAV network. For example, allowing a drone to find charging stations, or an autonomous car to ask for traffic data.
How you can help
In order to foster a community that is welcoming for open source contributions, it is important for us to have good test coverage. And good tests are simple, readable tests.
Here is a good opportunity to simplify one of our tests.
The Issue
We currently do not have unit testing set up for src/drone-delivery/MessageParams.ts. Please create Jest tests for the serialize() and deserialize() methods.
A good reference point would be src/ride-hailing/MissionParams.test.ts and customize it to the expected parameters and properties. If you are unsure what is expected, run npm run jest in the terminal and it should give you a hint.  Also, you can reach out to our gitter channel with any questions 😄
The test you write will be similar to this:
import MessageParams from './MessageParams';

describe('MessageParams class', () => {
  let messageParams: MessageParams;
  let serializedMessageParams: any;

  beforeEach(() => {
    messageParams = new MessageParams({
      senderId: undefined
    });

    serializedMessageParams = {
      protocol: 'drone_delivery',
      senderId: undefined,
      type: 'message',
      ttl: undefined
    };
  });

  describe('serialize method', () => {
    it('should return serialized MessageParams object with the current values', () => {
      expect(messageParams.serialize()).toEqual(serializedMessageParams);
    });
  });

  describe('deserialize method', () => {
    it('should return a MessageParams instance', () => {
      const messageParamsObject = new MessageParams();
      messageParamsObject.deserialize(serializedMessageParams);
      expect(messageParamsObject).toBeInstanceOf(MessageParams);
    });

    it('should return deserialize MessageParams instance with the current parameters', () => {
      const messageParamsObject = new MessageParams();
      messageParamsObject.deserialize(serializedMessageParams);
      expect(messageParamsObject).toEqual(messageParams);
    });
  });
});

After making your changes, run npm run tslint and npm run jest to make sure our tests are passing.
Contributing to dav-js

[ ] Make sure this issue is labeled up-for-grabs and not labeled claimed, to verify no one else is working on it.
[ ] Comment in this issue that you would like to do it.
[ ] Open dav-js GitHub page and click the ★ Star and then ⑂ Fork buttons.
[ ] Clone a copy to your local machine with $ git clone git@github.com:YOUR-GITHUB-USER-NAME/dav-js.git
[ ] Install dependencies by running npm install
[ ] Code Code Code
[ ] Once you've made sure all your changes work correctly and committed all your changes, push your local changes back to github with $ git push -u origin master
[ ] Visit your fork on GitHub.com (https://github.com/YOUR-USER-NAME/dav-js) and create a pull request for your changes.
[ ] Make sure your pull request describes exactly what you changed and references this issue (include the issue number in the title like this: #7)
[ ] Please do not fix more than one issue at a time. Your pull request should only fix what is described in this issue.

Asking for help
We appreciate your effort in taking the time to work on this issue and help out the open source community and the foundation. If you need any help, feel free to ask below or in our gitter channel. We are always happy to help 😄

For sure! Go for it @sionelt.

Thanks for another quick turn around @sionelt I have merged your changes. May I suggest using lint plugins for your IDE to assist code standards on future projects?

I am glad to help. I wish I can do more. Oh was the linting failed on the files I worked on? I do have the Eslint plugin on vs code...

@sionelt I use vs code, too 😃 Yeah I usually have the eslint plugin running and that's good for most projects. I am seeing more projects move towards typescript so it may be another plugin I have to keep running as well 😆 If plugins were better managed in vs code I wouldn't be so concerned.

Yes, I just notice it. It was failing for the Tslint and I didn't have Tslint plugin installed. This is a great tip, I've been learning typescript. I'll make sure to run the Tslint script and passed on future PRs. thanks for the help. This makes more excited to contribute more to open source.


Fix HTML typos

Two small HTML typos I found:

close p tag
add p tag with formatting to message on brief page

Screenshots
Before

After

We should be able to get rid of summary-item-no-content as it's a toolkit style.
https://github.com/alphagov/digitalmarketplace-buyer-frontend/blob/22873dd65aefc230c248b22f8c0cccaefe3d27e2/app/templates/_brief_q_and_a.html#L14

We should be able to get rid of summary-item-no-content as it's a toolkit style.
https://github.com/alphagov/digitalmarketplace-buyer-frontend/blob/22873dd65aefc230c248b22f8c0cccaefe3d27e2/app/templates/_brief_q_and_a.html#L14


Related issue #1856. Add option 'Scheme' for alb config which can be …

…internal or internet-facing.
Description
Add an option to enable private ALB schemes instead of hardcoding the value to internet-facing. To ensure backwards compatibility, still default to internet-facing.
GitHub Issues
#1856

Coverage decreased (-0.2%) to 73.066% when pulling 4b9beb8e260ec6827d06c671f957746288b7a80b on ltwesley:feature/alb-scheme-option into 3ccf7490a8d8b8fa74a61ee39bf44234f3567739 on Miserlou:master.

Coverage decreased (-0.2%) to 73.066% when pulling 4b9beb8e260ec6827d06c671f957746288b7a80b on ltwesley:feature/alb-scheme-option into 3ccf7490a8d8b8fa74a61ee39bf44234f3567739 on Miserlou:master.

Is there any timeline on when this is going to be merged? I am still manually creating my internal load balancers each time I deploy.

Agreed, it would be good to get this merged. I'm manually changing the library in my local zappa installs so I can create internal facing ALBs.

Any word on merging this PR?

If not could we at least get some feedback on the code?

Now if we could get somebody to merge it...

Now if we could get somebody to merge it...

... @jneves ? Just tagging you because it looks like you've been the one that has reviewed and merged the last few PRs.

I would also like to know if this is going to be merged.


Swift 4.2 and 5.0 support

This makes Mortar compatible to Swift 4.2 and 5.0.

test on Travis that it compiles with Swift 4.2 and 5.0
fix all Xcode 10.2 warnings
Podspec:

use swift_versions to define both supported Swift versions (introduced in Cocoapods 1.7.0)
upgrade swift_version to 5.0 (backwards compatibility for Cocoapods < 1.7.0)

Tested integrations:

Xcode 10.0, Swift 4.2, Cocoapods 1.5.3 Podfile post_install: config.build_settings['SWIFT_VERSION'] = '4.0'
Xcode 10.0, Swift 4.2, Cocoapods 1.7.0, Podfile: supports_swift_versions '4.2', no post_install
Xcode 10.2, Swift 4.2, Cocoapods 1.7.0, Podfile: supports_swift_versions '>= 4.2', '< 5.0', no post_install
Xcode 10.2, Swift 5.0, Cocoapods 1.7.0, Podfile: supports_swift_versions '>= 4.2', '<= 5.0', no post_install

Great stuff!  Will integrate

Mortar 1.6.0 was just published to Cocoapods!


unable to run on mac

Operating system
Mac 12.6
Package name
pbmm2 latest version via conda
Conda environment
pbmm2                     1.7.0                h9d1909e_1    bioconda
python                    3.8.3                h26836e1_1
(does it need 2.7? have also tried it in this, same results)
Describe the bug
$ pbmm2 align ref.mmi reads.bam aligned.bam
(from Revio)
Error message

|> 20240313 22:42:54.640 -|- FATAL -|- CheckPositionalArgs -|- 0x2045c9600|| -|- pbmm2 align ERROR: Could not determine read input type(s). Please do not mix data types, such as BAM+FASTQ. File of files may only contain BAMs or datasets.

thanks

Having the same issue

This list will tell you MacOS compatibility https://github.com/PacificBiosciences/pbbioconda?tab=readme-ov-file#packages


State translation

Modification to allow translation of:

Charge and plug status sensors
Charge and plug binary sensors (need to have the PR #4236 merge in HA core to work)

French translation added.
GitHub workflow to check the custom component with hassfest (mainly to check translation files)
Strings file added even if not used in custom component but could be used when merging this integration in HA core.
Fix #60

I don't know why but when I add a file strings.sensor.json (to prepare for merge in HA) the translation stop working. So I remove the file.

Rebased and tested in local. Translations work for status sensors.


Fix broken word wrapping in reporters in Windows TTY (closes #87)

\cc @inikulin @AlexanderMoskovkin

Have you tried it in MacOS TTY, is everything works as expected there?

FPR
Yes the output to MacOS TTY works as expected, I renamed the commit.

Please, use Fix word in the commit message, because currently it sounds like you've introduced the issue with the commit :smile:

Okay

lgtm

\cc @AlexanderMoskovkin

lgtm


Roof shading issues

I'm not sure what exactly might be causing this, but the roof sharing in these buildings is inconsistent for some reason:

Link to the location: https://streets.gl/#16.67498,-22.93461,35.50,332.50,420.15

I'm not sure what exactly might be causing this, but the roof sharing in these buildings is inconsistent for some reason:

Some of these building have roof:orientation=*, same don't. Could be that?

Nice, thanks for the quick fix! Just for reference, linking another thread discussing roof lighting issues: #50.


[$1000] Web - A newly created workspace name follows the sequence of the numbers present in the last workspace

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Action Performed:

Open the website.
Navigate to the settings page, then to the workspaces page.
Edit the name of the last work space from the workspace general settings and add a numerical value at the end of the name (i.e., Workspace 111).
Create a new workspace.
Observe that the newly created workspace name follows the sequence of the number present in the last workspace (i.e., Workspace 112).

Expected Result:
A newly created workspace name should equal the number of workspaces present in the workspaces list, so if the newly created workspace is third in the list, its name should have the number 3 at the end.
Actual Result:
A newly created workspace name follows the sequence of the numbers present in the last workspace; if the last created workspace name ends with 111, then the newly created workspace name ends with 112.
Workaround:
Unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[ ] Android / native
[ ] Android / Chrome
[ ] iOS / native
[ ] iOS / Safari
[x] MacOS / Chrome / Safari
[ ] MacOS / Desktop

Version Number: 1.3.44-0.
Reproducible in staging?: y
Reproducible in production?: y
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
https://github.com/Expensify/App/assets/93399543/be60ddec-3740-48fa-9f80-49cf56975a49
https://github.com/Expensify/App/assets/93399543/dc20ad82-15f2-4cc3-bdfe-0af51289e7c4
Expensify/Expensify Issue URL:
Issue reported by: @Ad-eeb
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1689984658585249
View all open jobs on GitHub
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~0166a81173ade6bb41
Upwork Job ID:<PHONE_NUMBER>023903744
Last Price Increase: 2023-07-24

Proposal
Please re-state the problem that we are trying to solve in this issue.
A newly created workspace name follows the sequence of the numbers present in the last workspace.
What is the root cause of that problem?
New workspaces are named based on arbitrary numbers at the end of existing workspace names.
What changes do you think we should make in order to solve the problem?
I suggest we consider another approach to naming workspaces - using the number of existing workspaces, as opposed to just going off whatever arbitrary number is at the end of existing workspace names.
For example
["myWorkspace", "myWorkspace1"] > "myWorkspace2"
["myWorkspace100"] > "myWorkspace1" // Would have been myWorkspace101 at present

We only need to care about the number at the end of existing workspaces if there is a direct conflict. In the below example, the default option would have been myWorkspace2 since there are 2 existing workspaces. However, since myWorkspace1 has been renamed to myWorkspace2, that name is already used, so we increment the end number to 3. Crucially, this is the only scenario where we would care about the ending numbers of existing workspace names.
["myWorkspace", "myWorkspace2"] > "myWorkspace3"

I think this approach is closer to optimal than going off minimum numbers. Consider the following scenario:
We have 3 workspaces
["myWorkspace", "myWorkspace1" "myRenamedWorkspace"]

myRenamedWorkspace was initially called myWorkspace2, but has been renamed. If we were to go off minimum numbers, we would end up with yet another myWorkspace2, which could be confusing to users. It would, in my opinion, be better to name the new workspace myWorkspace3.
What alternative solutions did you explore? (Optional)

Let's be clear on expected output first.
Personally, I don't think it's a bug and I am okay to leave it at present state. But if we want to make some improvement, my preference will be to add either 'total number of workspaces having default name' or 'total number of workspaces' and use it. But the preference can vary from person to person.
@maddylewis Can you please confirm the expected output here?

@samh-nl Regarding your proposal, I will suggest you to start a discussion on slack. If everyone agrees, we can implement the customization flow. I personally like the idea. Nevertheless, I think even if we implement the flow, we should suggest a default name for workspace.

@sobitneupane - let us know the direction you'd like to go based on this convo https://expensify.slack.com/archives/C01GTK53T8Q/p1690621380575829?thread_ts=1690377659.722669&cid=C01GTK53T8Q

@sobitneupane - another bump on this one. let me know if you'd like me to assign another Contributor+ to lead this one. thanks!

@maddylewis even if we prompt user to name the workspace along with it's creation as suggested by @samh-nl, I believe we will be suggesting some default name which can be edited by the user. So, It will be a different Feature Request.
For handling this issue, we are not sure what should be the expected output? My suggestions are here.

In that case naming the new workspace would be a requirement, not an option @samh-nl, adding one more step to the creation of every workspace. If allowing users to set a name when creating a workspace is desired, the optimal solution IMO would be to not autofocus that input, rather to have an unfocused input with a default name, that is cleared when a user clicks on it.

Started discussion regarding the expected output: https://expensify.slack.com/archives/C01GTK53T8Q/p1690978953836909

based on this comment, i'm going to close this out since it sounds like we decided to Do Nothing in this case - https://expensify.slack.com/archives/C01GTK53T8Q/p1690982790796029?thread_ts=1690978953.836909&cid=C01GTK53T8Q


add limit support

Thanks for this pull request, but the limit parameter is defined with the offset param

Okay


Add an example of how to use SystemBase

Related to #18, only for Python in this case.

:books: Documentation preview :books:: https://rascaline--217.org.readthedocs.build/en/217/

I am happy but the linter not 🥺


End-to-end tests for Beam jobs

With GCP testing infrastructure set up, we can also extend this to GCS tasks that can't be tested now like the path verifications.

I like this idea. It would be good to have e2e canary tests.


Sessions not loading

I just upgraded nvim version and packages:
NVIM v0.10.2
Build type: Release
LuaJIT 2.1.1727870382
Run "nvim -V1 -v" for more info

nvim-possession loaded using Lazy manager:
dir     ~/.local/share/nvim/lazy/nvim-possession
url     https://github.com/gennaro-tedesco/nvim-possession
version 0.0.14
tag     v0.0.14
branch  main
commit  0844f6d
readme  README.md
help    |possession.txt|

The issue is that nvim-possession does not load the sessions anymore as it should.
It displays the session as a buffer in neovim,, the ones located in ~/.local/share/nvim/sessions/

Good evening, could you please indicate some steps to reproduce the issue? In particular the steps that you understand to save the session first, and then loaded it afterwards (for instance are you loading the session automatically)?
It would also help if you could try to reproduce the problem using the minimal repro.lua.

At first the sesions were coming from the older version, so I thought that maybe something broke and I deleted them to start a new fresh session.
At this point, I just created a test session with 2 buffers open in a vertical split and saved the session, exited from neovim.
When entering again, I listed the sessin sl and choose the only 1 existing at this point, howeverthe session was displayed rather than load.
Moreover, when I list the sessions, also a .DS_Store file is shown that it does not exist in location ~/.local/share/nvim/sessions/
And most interesting, it seems fzf-lua fails with this plugin. When I tried ctrl-g errors pop up
This is my nvim-possession setup:
    require("nvim-possession").setup({
	  autoswitch = { enable = true, },
	  autosave = false,
	  post_hook = require("nvim-possession-extension").set_mappings_again,
	  fzf_winopts = {
		  preview = {
			horizontal = "up:60%",
		  },
		}

And most interesting, it seems fzf-lua fails with this plugin. When I tried ctrl-g errors pop up

what is ctrl-g supposed to do here?

post_hook = require("nvim-possession-extension").set_mappings_again,

what are these require("nvim-possession-extension").set_mappings_again?
I presume the problem may lie in some keymappings that you use for fzf where enter doesn't select the list item to source but rather displays it in a buffer. Please try with the minimal repro because we need to isolate if this behaviour is generated by external keymaps (notice that with the minimal repro also fzf is configured minimally).

I found the issue… at least to me!
In nvim-possession/lua/nvim-possession/init.lua function M.list the actions array, rather than defining "enter" I switched to "default" to make it to work.

Yes, if I remember correctly this was a change introduced in fzf-lua some time ago.
Glad that you solved it: can I consider this closed?

IDK!
What should be the correct value for M.list actions? "default" or "enter"?
If I change the code on my box, I will have issues when upgrading the plugin…

As you can see from this commit the value was changed in the upstream fzf-lua to use "enter". Are you sure that your fzf-lua is updated to the latest?

Yes, fzf-lua is updated to the latest. See below image:

Kind regards!


remove link is only visible on just uploaded files, not on ones added programatically

I swear this used to work.. something must have changed in the last update maybe?
When I upload new images, the 'remove' button is visible and I can click it and it works.
However when I load the view with existing images, those don't have the 'remove' button
import Dropzone from "vue2-dropzone";

Vue.component('my-profile-images', {
  props: ['user'],
  components: {
    Dropzone
  },
  data() {
    return {
      dzOptions: {
        dictDefaultMessage: 'Drop your profile images here or click to upload (Max 6 images)',
        acceptedFiles: '.jpg,.jpeg,.png,.gif',
        maxFiles: 6,
        maxFilesize: 5,
        addRemoveLinks: true,
        headers: {'X-CSRF-TOKEN': Spark.csrfToken},
      },
    };
  },
  methods: {
    'showSuccess': function (file) {
      //console.log('A file was successfully uploaded');
    },
    'fileRemoved': function (file, error, xhr) {
      //console.log('File removed', file);
      axios.delete('/api/profile/profile-images', {
        params: {id: file.id}
      }).then(response => {
        this.newNotification = {};
        this.getNotifications();
      });
    }
  },
  mounted() {

    for (var i = 0; i < this.user.images.length; i++) {

      var mockFile = {id: this.user.images[i].id, name: this.user.images[i].name, size: this.user.images[i].size};
      var imageUrl = "/media/" + this.user.images[i].id + "/" + this.user.images[i].file_name;

      this.$refs.myDropzone.manuallyAddFile(mockFile, imageUrl);

      // if (this.$refs.myDropzone.dropzone.options.maxFiles > 0) {
      //   this.$refs.myDropzone.dropzone.options.maxFiles--
      // }
    }

    this.$refs.myDropzone.dropzone.options.addRemoveLinks = true;
  },
});

I used
    console.log(this.$refs.myDropzone.dropzone.options.addRemoveLinks)
    console.log(this.$refs.myDropzone.dropzone.options)

and it does show the option is correctly set to true
Perhaps I need to re-initialize it after adding the existing images? Any idea how I can do that?
Thanks!

Resolved in latest release 2.2.8 b775327. We apologize for unintended changes!


Automated Package Upgrade

:tada: This PR is included in version 13.0.37 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


QW-2905: Add pulsar tests with authorization

This adds token authorization to pulsar so that we can test authorization handling while testing pulsar.

The test passes, but when I change the token's value, the test does not fail.


Don't interpret Proc typedefs as aliases

c.f. https://github.com/crystal-lang/crystal/issues/10001#issuecomment-760929546

@HertzDevil to clarify, the test case in https://github.com/crystal-lang/crystal/issues/10001#issuecomment-761009379 is passing on here, right?
For migration current code type Callback = ... should be redefined as alias Callback = .... No other breaking-change is introduced here, right?

@HertzDevil to clarify, the test case in https://github.com/crystal-lang/crystal/issues/10001#issuecomment-761009379 is passing on here, right?
For migration current code type Callback = ... should be redefined as alias Callback = .... No other breaking-change is introduced here, right?

@bcardiff That one still passes. This PR is only for the type to alias changes.

@bcardiff That one still passes. This PR is only for the type to alias changes.

@bcardiff what do you think about merging this one for 0.36.0? Since it's a breaking change it means 1.0 will have one less breaking change. It also fixes something in the language, because the behavior in this PR is more correct than the old one.

@bcardiff what do you think about merging this one for 0.36.0? Since it's a breaking change it means 1.0 will have one less breaking change. It also fixes something in the language, because the behavior in this PR is more correct than the old one.

It can go into 0.36

It can go into 0.36


Lab 06: Integrating External Source Control with Azure Pipelines

Contact Details
<EMAIL_ADDRESS>What happened?
Exercise : Lab 06: Integrating External Source Control with Azure Pipelines
Task: 4
Step: 6
Description of issue: In this step 6, it is indicated "Create a new branch, set its name to addition-cleanup" which effectively triers a build run in Azure Devops whereas the pipeline trier indicates only master branch as follows

trigger:

master

Is this a bug or there is a config that allows this  that we are not aware of?
Thanks
Repro steps:
1.follow steps task 4 until step 6
1.
1.
Lab
Lab 06 Integrating external source control with Azure Pipelines
Relevant screenshots
paste here 😉
Do you want to help us? 👏

[ ] Create a Pull Request by following this project's Contribution Guide

Please note that the build is not triggered for the new branch and also not just after any new branch is created.
After performing the changes in the new branch, you have to open a new pull request from the new cleanup branch into the master branch. Once the PR is created, it will take some seconds for the pipeline to be triggered. And it will be triggered, as the PR you just opened would affect the master branch. So the trigger definition as-is, is enough to also support PR automation.

Hi Tobias, not sure I understand the response as it does not aligh with what is written and happens when creating the new branch in the lab. It is indicated

On the Open a pull request page, click Create pull request to initiate the process of getting your untested changes into production code.
Note: Azure DevOps will detect the change and start the build pipeline. This will result in failed checks, triggering an update the GitHub UI.

which in fact triggered the pipeline

I am closing the issue for now. The lab will be refreshed soon.


Remove buffer-name-history from perspective state.

It was being tracked in perspectives-hash, and was being copied to every
perspective on activation. So each perspective ended up with the same large copy
of the buffer history list.
It seems to only be relevant to the vanilla (i.e., not ido or any other replacement) implementation of switch-to-buffer (https://www.emacswiki.org/emacs/MinibufferHistory). I think the intent was to keep perspective-specific buffer history around to help narrow down search results (i.e., C-x b then C-r), but right now, it does no perspective-specific history filtering at all.
With this patch, the perspective hash becomes much smaller and cleaner, and perspective activation should be just a little bit faster since there is no need to copy a very large history list around every time.
Am I missing something here? @zenspider, @dzop, @conao3 — your opinions, please?
If this makes sense, it would resolve #115.

I'm nothing on it.

I've been using this patch for the last few weeks, and it works well. I'll merge it in soon if I don't hear any objections.


Strongly typed indices in arrays

Is there a solution to make an array with strong indexing? Such as:
using FooIndex = NamedType<size_t, struct FooTag>;
using BarIndex = NamedType<size_t, struct BarTag>;

std::vector<Foo, FooIndex> foos;
std::vector<Bar, BarIndex> bars;
...
BardIndex barIndex = ..;
FooIndex fooIndex = ...;
foos[barIndex] = Foo(); //should not compile
foos[fooIndex] = Foo(); //ok

Theoretically it's often fine to just deduce FooIndex = NamedType<size_t, Foo> for such containers. Is there a way to achieve it in an stl-compatible way?

I think there are several ways:

Introduce a strongly indexed container, by reusing vector:
** with public inheritance: https://godbolt.org/z/1s4vnP
** with private inheritance: https://godbolt.org/z/z49jax
Use a strongly indexed reference to a container: https://godbolt.org/z/nv7Tq9

Do you think either one of these solutions would allow to write the code you had in mind?

Yes, both of them achieve exactly what I had in mind, however, implementation-wise, inheriting from an stl container is generally not a great practice.

FWIW, some sort of half-automatic proxy wrapper might be great. I was hoping to combine this library with a units library, so that we have both semantic types, and correct phyiscal units/dimensions in our code. And all this would need to operate with matrix, vector, and quaternion types - quite a bit to juggle! So far, NamedType wrapping around boost::qvm is working quite nicely, albeit without the units support. This'll likely need some sort of proxy wrapper. We also have some Mats from OpenCV. This would be one example where being able to index into an opaque structure would be really powerful, if it could be done. QVM is so-designed that it's working nicely enough to have the NamedTypoe on the outside, as QVM is designed explicitly to operate on different (incompatible) types, and is thus mostly free-functions. But CV's Mat would not be so easy, and was one justifying reason for moving away from it and using this lib - access is always risky and very much relies on runtime support, including the type of data it's storing. It's all held behind one single type.
Tl;Dr - I imagine a composition proxy wrapper might work quite powerfully here - a more generic version of the reference version above, I guess - perhaps using some specialised traits to define how to access the wrapped object, with some sensible automatic defaults, like for operator[]. And if done well, I'd hope it would compile away to the same binary format, a bit like how std::chrono evaporates after build-time, and I believe NamedType itself does. Perhaps NamedContainer<Key, Value>, for a rough way of accessing - for things like list and vector, the key becomes more of an index. Am guessing map and set will work as-is, although may be wrong.


Mods to alphabets to incorporate missing characters

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

77 of 81 (95.06%)  changed or added relevant lines in 2 files are covered.
4 unchanged lines in 2 files lost coverage.
Overall coverage decreased (-0.003%) to 90.93%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/cogent3/core/new_alphabet.py
47
48
97.92%

src/cogent3/core/new_moltype.py
30
33
90.91%

Files with Coverage Reduction
New Missed Lines
%

src/cogent3/core/alignment.py
1
93.76%

src/cogent3/core/new_moltype.py
3
95.21%

Totals

Change from base Build<PHONE_NUMBER>:
-0.003%

Covered Lines:
32270

Relevant Lines:
35489

💛  - Coveralls

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Warning: This coverage report may be inaccurate.
This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

For more information on this, see Tracking coverage changes with pull request builds.
To avoid this issue with future PRs, see these Recommended CI Configurations.
For a quick fix, rebase this PR at GitHub. Your next report should be accurate.

Details

109 of 132 (82.58%)  changed or added relevant lines in 2 files are covered.
3 unchanged lines in 1 file lost coverage.
Overall coverage decreased (-0.03%) to 90.902%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/cogent3/core/new_alphabet.py
46
48
95.83%

src/cogent3/core/new_moltype.py
63
84
75.0%

Files with Coverage Reduction
New Missed Lines
%

src/cogent3/core/new_moltype.py
3
90.77%

Totals

Change from base Build<PHONE_NUMBER>:
-0.03%

Covered Lines:
32281

Relevant Lines:
35512

💛  - Coveralls


l10n: On android app, there is only one entry for Chinese

For Chinese, it should be divided into:

Traditional Chinese (zh_TW)
Simplified Chinese (zh_CN)

But for now there is only one, which is Simplified Chinese.
In order to reduce confusion, I would suggest:

Rename "Chinese" to "Simplified Chinese" in the language selection menu.
Add a new entry for Traditional Chinese.

I've added zh_CN and zh_HK. Should I add zh_TW as well ?

Yes please, that would be great. Many terms are significantly different between these three.
(I'm already doing translation work for zh_TW on launchpad.)
Thanks.

I've added a rule on Crowdin and imported your translations from Launchpad.
Although a long time Launchpad user, the platform timeouts too often to be usable.
https://crowdin.com/project/openfoodfacts/zh-TW#

Thanks, so it's better to make translations on Crowdin or on github directly instead of working on launchpad? (If that's the case, issue #301 will need an update)

corrected on #301
Yes, Crowdin is the way to go now. I'll be syncing for a while, but eventually, I'll probably disable Launchpad.

https://crowdin.com/project/openfoodfacts/zh-HK
https://crowdin.com/project/openfoodfacts/zh-CN
https://crowdin.com/project/openfoodfacts/zh-TW

Hi @teolemon, this is fixed I guess

Yes. Serbian still eludes me.

Serbian Cyrillic is a typo in the lang_array; Serbian Latin seems to be trickier


TextBox for passwords doesn't display correctly

In avalonia 11 preview 2 the icon for showing/hiding text isn't displayed

Hello, @kilinnik
Fixed in 3.0.0-avalonia11-preview2.124-nightly


I need to pull my own unwatched episodes of a specific show

Hi,
I really do not know where to post this, i tried the vip.trakt.tv but it is down all day. Also i read the api guide but even though i have a bit of coding experience on this am totally lost on where to start.
If i understood this correctly i can call a URL and return an .xml or other structure format of what i want.
I need to be able to get a list of unwatched and collected episodes (the collected option is so i do not get future unaired ones as unwatched) of a specific show.
Can someone provide the link or what to do.
For example on the show Goldbergs (2013), i have half season 6 and season 7 as unwatched so i need to get for example:
Goldbergs 6x21
Goldbergs 6x22
Goldbergs 7x1
Goldbergs 7x2
etc
I don't care of the output, the number of the episode "21", or "22" is enough i will fix this and get my stuff from my VB6 application that i need for personal tracking. Yes VB6, i'm that old :nerd_face:
I need a serious help boost on this.
Many Thanks in Advance

ok, i have read some stuff on the api wiki and try some things. Of course with no success :cry:

Created the api

Got the auth and register the device (?) the web page ? something

Registration is successful

Tried to call my shows list of 2019-11-1, 7 days program, error 401.

So how dump or off am i ?
Many thanks,
Vassilis

A 401 error means the OAuth (Authorzation header) is invalid. You need to do step 3 listed at https://trakt.docs.apiary.io/#reference/authentication-devices to exchange the device_code for an access_token. Then use the access_token and it should work.

A 401 error means the OAuth (Authorzation header) is invalid. You need to do step 3 listed at https://trakt.docs.apiary.io/#reference/authentication-devices to exchange the device_code for an access_token. Then use the access_token and it should work.

Ok, i made progress :laughing:
I used the correct device code and access token and got the results from this

I got correct results now!
Now which parameters (codeids) should i pass to diplay the unwatch episodes of "https://trakt.tv/shows/the-goldbergs-2013" AND that are status collected.
Many thanks !!
Vassilis

ok i did it !
FYI, the python code in the site is using urllib2 which is depreciated in python 3.x the correct one is:
import urllib.request
req = urllib.request.Request('https://api.trakt.tv/shows/<showname>/progress/watched?hidden=false&specials=false&count_specials=false')
req.add_header('authorization', 'Bearer [access token]')
req.add_header('trakt-api-version', '2')
req.add_header('trakt-api-key', '[api key]')
arxeio=open("c:\Watched.txt","w")
with urllib.request.urlopen(req) as f:
	#title= print(f.read().decode('utf-8'))
	arxeio.write(f.read().decode('utf-8'))

arxeio.close

I also made write the output to a file so that you can access it and work it from any dev language you want.


Coordinate Conversion input format doesn't support / coordinate pair separator character (ArcGIS Pro)

According to the following help topic, ArcGIS Pro supports the forward-slash character / as the coordinate pair separator, however, the Coordinate Convert addin does not. The addin does support the back-slash character.
http://pro.arcgis.com/en/pro-app/tool-reference/data-management/supported-notation-formats.htm
NOTEs:

The addin should support this capability when the input format is in DD, DDM, and DMS.
The addin should also support this when entering in Longitude Latitude order.
The addin should support /, /space, and space/space as coordinate pair separtors.

Here is an example, using the forward-slash. Note: the tool should also support: forward-slash space
45.00N/70.00W
Here is an example in ArcGIS Pro. I had previously entered 0 0 as the coordinates, then I pasted in 45.00N/70.00W:

Tested the Pro addin built on 1.2 and installed on ArcGIS Pro 1.2

@jmhauck Installed Pro addin dated 05 Jan 2017 09:08 and tested on Pro build 1.4.7197 and the / character is working. Closing issue.


Defunct s3fs

Summary
defunct s3fs processes keep piling up in my system.
root      4523  0.0  0.0      0     0 ?        Zs   12:25   0:00 [s3fs] <defunct>
root      4715  0.0  0.0      0     0 ?        Zs   12:01   0:00 [s3fs] <defunct>
root     12083  0.0  0.1  25256  3896 ?        Ssl  12:28   0:00 s3fs sharedstatic /var/lib/rexray/volumes/sharedstatic -oallow_other,umask=002,use_path_request_style,nonempty,url=http://<IP_ADDRESS>:10101
root     18263  0.0  0.0      0     0 ?        Zs   12:18   0:00 [s3fs] <defunct>
root     21834  0.0  0.0      0     0 ?        Zs   12:00   0:00 [s3fs] <defunct>
root     22460  0.0  0.0      0     0 ?        Zs   12:18   0:00 [s3fs] <defunct>

Version
Docker version 18.03.0-ce, build 0520e24
Ubuntu 16.04.4 LTS
Rexray plugin info:
docker plugin inspect a02f355b0adc
[
    {
        "Config": {
            "Args": {
                "Description": "",
                "Name": "",
                "Settable": null,
                "Value": null
            },
            "Description": "REX-Ray FUSE Driver for Amazon Simple Storage Service (S3FS)",
            "DockerVersion": "18.02.0-ce",
            "Documentation": "https://github.com/thecodeteam/rexray/.docker/plugins/s3fs",
            "Entrypoint": [
                "/rexray.sh",
                "rexray",
                "start",
                "-f",
                "--nopid"
            ],
            "Env": [
                {
                    "Description": "",
                    "Name": "REXRAY_LOGLEVEL",
                    "Settable": [
                        "value"
                    ],
                    "Value": "warn"
                },
                {
                    "Description": "",
                    "Name": "LIBSTORAGE_INTEGRATION_VOLUME_OPERATIONS_MOUNT_ROOTPATH",
                    "Settable": [
                        "value"
                    ],
                    "Value": ""
                },
                {
                    "Description": "",
                    "Name": "LINUX_VOLUME_ROOTPATH",
                    "Settable": [
                        "value"
                    ],
                    "Value": ""
                },
                {
                    "Description": "",
                    "Name": "LINUX_VOLUME_FILEMODE",
                    "Settable": [
                        "value"
                    ],
                    "Value": ""
                },
                {
                    "Description": "",
                    "Name": "HTTP_PROXY",
                    "Settable": [
                        "value"
                    ],
                    "Value": ""
                },
                {
                    "Description": "",
                    "Name": "S3FS_ENDPOINT",
                    "Settable": [
                        "value"
                    ],
                    "Value": ""
                },
                {
                    "Description": "",
                    "Name": "S3FS_ACCESSKEY",
                    "Settable": [
                        "value"
                    ],
                    "Value": ""
                },
                {
                    "Description": "",
                    "Name": "S3FS_DISABLEPATHSTYLE",
                    "Settable": [
                        "value"
                    ],
                    "Value": ""
                },
                {
                    "Description": "",
                    "Name": "S3FS_MAXRETRIES",
                    "Settable": [
                        "value"
                    ],
                    "Value": ""
                },
                {
                    "Description": "",
                    "Name": "S3FS_OPTIONS",
                    "Settable": [
                        "value"
                    ],
                    "Value": ""
                },
                {
                    "Description": "",
                    "Name": "S3FS_REGION",
                    "Settable": [
                        "value"
                    ],
                    "Value": ""
                },
                {
                    "Description": "",
                    "Name": "S3FS_SECRETKEY",
                    "Settable": [
                        "value"
                    ],
                    "Value": ""
                },
                {
                    "Description": "",
                    "Name": "CSI_ENDPOINT",
                    "Settable": [
                        "value"
                    ],
                    "Value": ""
                },
                {
                    "Description": "The name of the CSI plug-in used by the CSI module.",
                    "Name": "X_CSI_DRIVER",
                    "Settable": [
                        "value"
                    ],
                    "Value": ""
                },
                {
                    "Description": "A flag that disables the CSI to libStorage bridge.",
                    "Name": "X_CSI_NATIVE",
                    "Settable": [
                        "value"
                    ],
                    "Value": "false"
                }
            ],
            "Interface": {
                "Socket": "rexray.sock",
                "Types": [
                    "docker.volumedriver/1.0"
                ]
            },
            "IpcHost": false,
            "Linux": {
                "AllowAllDevices": true,
                "Capabilities": [
                    "CAP_SYS_ADMIN"
                ],
                "Devices": null
            },
            "Mounts": [
                {
                    "Description": "",
                    "Destination": "/dev",
                    "Name": "",
                    "Options": [
                        "rbind"
                    ],
                    "Settable": null,
                    "Source": "/dev",
                    "Type": "bind"
                }
            ],
            "Network": {
                "Type": "host"
            },
            "PidHost": false,
            "PropagatedMount": "/var/lib/rexray",
            "User": {},
            "WorkDir": "",
            "rootfs": {
                "diff_ids": [
                    "sha256:eebe6ffed8f4c85b884ec7c227cff7ed9a9c189f8d28949aa20c395dd121869f"
                ],
                "type": "layers"
            }
        },
        "Enabled": true,
        "Id": "a02f355b0adce6e694ccfe3865abf0a60a98519b72b04b09d6062433a7eef10b",
        "Name": "rexray/s3fs:latest",
        "PluginReference": "docker.io/rexray/s3fs:latest",
        "Settings": {
            "Args": [],
            "Devices": [],
            "Env": [
                "REXRAY_LOGLEVEL=warn",
                "LIBSTORAGE_INTEGRATION_VOLUME_OPERATIONS_MOUNT_ROOTPATH=/",
                "LINUX_VOLUME_ROOTPATH=/",
                "LINUX_VOLUME_FILEMODE=",
                "HTTP_PROXY=",
                "S3FS_ENDPOINT=http://<IP_ADDRESS>:10101",
                "S3FS_ACCESSKEY=admin",
                "S3FS_DISABLEPATHSTYLE=",
                "S3FS_MAXRETRIES=",
                "S3FS_OPTIONS=allow_other,umask=002,use_path_request_style,nonempty,url=http://<IP_ADDRESS>:10101",
                "S3FS_REGION=",
                "S3FS_SECRETKEY=udLHd8IcFq35OhIYkrdEhxg4H5vQRK86griUfly0SIU=",
                "CSI_ENDPOINT=",
                "X_CSI_DRIVER=",
                "X_CSI_NATIVE=false"
            ],
            "Mounts": [
                {
                    "Description": "",
                    "Destination": "/dev",
                    "Name": "",
                    "Options": [
                        "rbind"
                    ],
                    "Settable": null,
                    "Source": "/dev",
                    "Type": "bind"
                }
            ]
        }
    }
]
```

Hello @ptemmer,
Since S3FS is a separate program its tough to say what might be causing this. I think the best place to start is to try and use S3FS outside of REX-Ray and see if you encounter similar problems. Can you give that a shot?

I've experienced a very similar issue. It seems that nothing is reaping s3fs processes once they've finished. I rebuilt the plugin, having copied /usr/bin/docker-init to rootfs/docker-init, and with a modified entrypoint as follows.
# diff -ubw config.json.orig config.json
--- config.json.orig	2021-01-16 23:44:21.220781544 +0000
+++ config.json	2021-01-16 23:50:09.019973289 +0000
@@ -8,7 +8,7 @@
       "Description": "REX-Ray FUSE Driver for Amazon Simple Storage Service (S3FS)",
       "Documentation": "https://github.com/thecodeteam/rexray/.docker/plugins/s3fs",
       "Entrypoint": [
-        "/rexray.sh", "rexray", "start", "-f", "--nopid"
+        "/sbin/docker-init", "/bin/ash", "--", "/rexray.sh", "rexray", "start", "-f", "--nopid"
       ],

Doing this fixed the problem.

I've experienced a very similar issue. It seems that nothing is reaping s3fs processes once they've finished. I rebuilt the plugin, having copied /usr/bin/docker-init to rootfs/docker-init, and with a modified entrypoint as follows.
# diff -ubw config.json.orig config.json
--- config.json.orig	2021-01-16 23:44:21.220781544 +0000
+++ config.json	2021-01-16 23:50:09.019973289 +0000
@@ -8,7 +8,7 @@
       "Description": "REX-Ray FUSE Driver for Amazon Simple Storage Service (S3FS)",
       "Documentation": "https://github.com/thecodeteam/rexray/.docker/plugins/s3fs",
       "Entrypoint": [
-        "/rexray.sh", "rexray", "start", "-f", "--nopid"
+        "/sbin/docker-init", "/bin/ash", "--", "/rexray.sh", "rexray", "start", "-f", "--nopid"
       ],

Doing this fixed the problem.


Several updates on opensource, visualizing, companies

Thanks for the awesome repo @robmarkcole! I have some updates for you 👍

Add https://github.com/fcakyon/small-object-detection-benchmark that contains pretrained models from ICIP 2022 paper
Add labelme2coco under Annotation visualisation & conversion tools
Update SAHI description to cover recent feature updates
Add SAHI under Image chipping/tiling & merging
Add Open Business Software Solutions under Companies & organisations on Github

Thanks, and keep
Up the great work!


Fix InvalidOperationException of swagger middleware

InvalidOperationException was caused in Swagger middleware because status code and content-type were set after setting response body,

Thank you.
yes, I've forgot fix...

I've pushed 2.0.1 to NuGet.


Not able to pass parameter to onTick method

I am trying to pass the parameter through the Context onto onTick method.

var job = {
                title: 'Sample Cron',
                cronTime: '* * * * * *',
                cronFunction: '',
                timeZone: 'Asia/kolkata',
                isActive: true,
                id: '55e131a486cdff8522b89d32'
            }

var myJob = new sails.cron.CronJob({
		  		cronTime: jobs.cronTime,
		  		onTick: function(job) {
				   	console.log("Ruuning the job : "+ job );
		  		},
		  		onComplete: function(){

		  		},
		  		start: false,
		  		timeZone: job.timeZone,
		  		context: job
});

myJob.start();

Following is getting printed on the console.

Ruuning the job : function (){

                                                }

Could anyone please help me to fix this issue?

That's not how it works. You pass an object in and that object becomes the scope for the onTick method. As in, this is the object that you passed in.


polyfills.ts In Universal

In generated project we have file polyfills.ts however i have not found any places where we use this file. Should we import it in to the client.ts file?

yes, this can be the first import in client.ts