DRAFT: Add test archlinux iso

This is a 707M bytes image that doesn't unsquashfs that fast... at all.

This is a 707M bytes image that doesn't unsquashfs that fast... at all.

Fixed the speed with https://github.com/wcampbell0x2a/squashfs-deku/pull/35, still working on correctness!

Error one:
thread 'test_archlinux_iso_rootfs' panicked at 'called `Result::unwrap()` on an `Err` value: StdIo(Error { kind: UnexpectedEof, message: "failed to fill whole buffer" })', /home/wcampbell/projects/wcampbell/backhand/src/squashfs.rs:283:64
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
test test_archlinux_iso_rootfs ... FAILED

Error two:
$ unsquashfs test-assets/test_archlinux_iso_rootfs/bytes.squashfs
read_fragment_table: Bad fragment count in super block
FATAL ERROR: File system corruption detected

In the latest version this takes around 45s.

I'll investigate, but I remember that total size was calculated using raw cast (I think as u32) and possibility overflowing, as a sanity check I made that try into.

Yah I think this is correct, as it's a limitation of SquashFS itself?
I'm not at my computer, is that error in the image we generate, or in the iso image?

Ah yes you're correct.
I really should replace the as T statements with try_from and from...

The error is in backhand code that generate a new image. It's able to parse the image, it's just unable to create a new one.
In v.0.11.0 the same thing happened, but because there was not explicit try_into().unwrap() it just overflow the total_size.
BTW: you can reproduce this bug with a much simpler file:
mkdir many_files
for i in {0..18000}; do touch many_files/$i; done
mksquashfs many_files/ many_files.squashfs
rm -rf many_files

You can then reproduce this error using:
touch 18001
add many_files.squashfs 18001 /

I need to add tests, but https://github.com/wcampbell0x2a/backhand/pull/213 should fix this.

@rbran if you apply both #215 and #213, the following errors shows up. Trying to call extract_dir on a BasicFile. Looks like on the src dir.
thread 'test_archlinux_iso_rootfs' panicked at 'called `Result::unwrap()` on an `Err` value: UnexpectedInode(BasicFile(BasicFile { blocks_start: 0, frag_index: 512, block_offset: 71048, file_size: 8871, block_sizes: [] }))', tests/test.rs:53:91

https://github.com/wcampbell0x2a/backhand/blob/1f00845a298a5f01396b71ffd293e04e960a8b08/src/squashfs.rs#L538

I'll investigate this, but calling extract_dir into a non-directory inode is invalid. Whatever is calling this function, is causing this panic.

I'll investigate this, but calling extract_dir into a non-directory inode is invalid. Whatever is calling this function, is causing this panic.

Certainly. Something must be off with the writer.

I could find time this morning to test this, unfortunately I was not able to fix it yet.
But I found a much fast test: test_few_dirs_many_files. I send those files to your email.
The problem seems to be in the creation of a new squashfs file, the files inside the extend directory seems to be lost.

Pushed a couple of commits to a branch of your branch: https://github.com/wcampbell0x2a/backhand/commits/big-files-w

Further fixed fragment tables
Fixed InodeId in DirEntry

Still getting that error, but more correct for these large images.

Mostly good news, with the following line commented out all tests pass.
https://github.com/wcampbell0x2a/backhand/blob/d243dd6bbeb208bb5eac6953ed433d230ba547cb/tests/test.rs#L53
This means that while our reader fails, the generated bytes.image file is a valid SquashFS image.

I would imagine some kind of overflow is happening, and the wrong inode is being read, in this case, a file instead of a directory.


Fix unresolved variable

Here, I have error while trying to apply typeField

I can't merge this PR as changed a lot when implementing modules in Astronomy, so my current version of this file is different. What error do you have when using the typeField? So I will test it out.

Just use typeField somewhere. It's unresolved variable error on typeField, the fix is pretty simple, just use this line:
const typeField = schema.typeField = parsedDefinition.typeField;
or something similar to define typeField variable

By the way, the one more request to think about? Additional to typeField option, like collectionType, or typeName, which will differ from actual type name.
Imagine, I migrate, and have collection conversations with types user and group inside, but also I have User type. So I need the method to set same type-name for different collections. Or name types different for code and db. I hope, I wrote it clear to understand =)

Ok in deed there was an error. I've fixed it but still can't publish it as I'm waiting for information from MDG how to support Meteor 1.2 in packages made for Meteor 1.3 and using ES modules

Thanks! Yeah, its the same for me why I'm not pulling my local v2 anymore.


Update Mono to Jessie for C# Dockerfiles

Fixes #11357
Will wait until C# tests run to see if this version of Mono breaks anything. Install instructions taken from http://www.mono-project.com/download/#download-lin-debian

No significant performance differences

test this please

No significant performance differences

Known failures:
https://github.com/grpc/grpc/issues/11216
https://github.com/grpc/grpc/issues/11223
https://github.com/grpc/grpc/issues/11077


Saving a jupyter as .py problem

We have written the needed data into your clipboard because it was too large to send. Please paste.
Issue Type: Bug
When i try to save any jupyter as .py its show me the new .py just with the first three lines.
It is a very usefull function, so please tell me, what can i do right now.
Regards,
VS Code version: Code 1.48.2 (a0479759d6e9ea56afa657e454193f72aef85bd0, 2020-08-25T10:13:11.295Z)
OS version: Windows_NT x64 10.0.19041

System Info

Item
Value

CPUs
Intel(R) Core(TM) i5-10210U CPU @ 1.60GHz (8 x 2112)

GPU Status
2d_canvas: enabledflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onoop_rasterization: disabled_offprotected_video_decode: enabledrasterization: enabledskia_renderer: disabled_off_okvideo_decode: enabledviz_display_compositor: enabled_onviz_hit_test_surface_layer: disabled_off_okwebgl: enabledwebgl2: enabled

Load (avg)
undefined

Memory (System)
7.79GB (1.26GB free)

Process Argv
.

Screen Reader
no

VM
0%

Extensions (26)

Extension
Author (truncated)
Version

codesnap
adp
1.0.27

path-intellisense
chr
2.2.1

bracket-pair-colorizer-2
Coe
0.2.0

vscode-markdownlint
Dav
0.36.3

gitlens
eam
10.2.2

code-runner
for
0.11.0

latex-workshop
Jam
8.11.1

kite
kit
0.122.0

theme-monokai-pro-vscode
mon
1.1.17

anaconda-extension-pack
ms-
1.0.1

python
ms-
2020.8.105045

vscode-pylance
ms-
2020.8.2

remote-containers
ms-
0.134.1

remote-ssh
ms-
0.51.0

remote-ssh-edit
ms-
0.51.0

remote-wsl
ms-
0.44.4

vscode-remote-extensionpack
ms-
0.20.0

autodocstring
njp
0.5.3

vscode-data-preview
Ran
2.0.0

vscode-yaml
red
0.10.1

code-settings-sync
Sha
3.4.3

code-spell-checker
str
1.9.0

code-spell-checker-spanish
str
1.0.5

redberry-icons
Ten
0.0.5

pdf
tom
1.1.0

material-theme
zhu
3.8.5

(1 theme extensions excluded)

@Rfariaspoblete How are you saving the file? Is this a command from an extension?

Something very weird Just happen. I upgrade the Latex version on Windows and I can now save correctly.
Regards.


export 5' end of extension in Edit-->Copy/paste/select-->Copy image

Create this design:

Go to Edit-->Copy/paste/select-->Copy image and paste the image into Powerpoint. The 5' end of the extension is missing:

When I export the whole design via Export->SVG main view, I do see the 5' and 3' ends of extensions, but they are in the wrong location. For instance:


Walk files with history

What is the goal / desired outcome? Add the ability to WalkFile with history
If there is a way to accomplish this today via workaround, what does that require? You can repeatedly call ListFile against each directory, but it's not particularly efficient.

:+1: this should be fairly easy to implement, probably makes sense to add the flag to glob file as well.


engine: block device permission is not consistent with native block devices

e.g.
directories:
drwxr-xr-x  2 root root         580 Apr  5 11:01 block/
drwx------  2 root root          60 Apr  4 23:53 longhorn/
block devs:
brw-rw----  1 root disk      8,   0 Mar 25 18:58 sda
brw------- 1 root root 8, 16 Apr  4 00:30 /dev/longhorn/test
We should make the permissions consistent with native ones.
Raised by https://forums.rancher.com/t/systemd-complaining-still-working-fine/13860 , systemd complains, though volume still works fine.

https://github.com/rancher/longhorn-engine/pull/350 merged

Longhorn Engine Version:  cb070da

[x] Block Devices created with 0660 permissions


auth_immutable_flag not visible in effects

https://stellar.stackexchange.com/questions/429/confusing-effects-after-set-options-transaction

This is a duplicate of https://github.com/stellar/horizon/issues/390 which has been fixed as of:  https://github.com/stellar/go/commit/e1c17a6980ae3dde6dc569c6330c5553a734b392


content-length header should not be passed to CSRF fetch

CAP adds content-length headers to all requests. For write operations, e.g. patch, custom headers are passed to the CSRF fetch request. Those requests fail during validation, because the fetch request is a HEAD request without content. We should not pass on the content-length.

I'll create this ticket, please reopen if it does not work.


Yarn dev error

Hi,
I can build or serve the gatsby due to error following;
React will try to recreate this component tree from scratch using the error boundary you provided, App.

@emrecan-s can you share the error screenshot to get better idea?
Also, share the gatsby version using gatsby --version


Broken GitHub Link

If you try to select the GitHub link from the npm page, you'll find that it links to https://github.com/jonschlinkert/is-valid-app.
Since the current package.json links to the node-base url and not the jonschlinkert url, it seems like you'd just need to publish a new version to npm.

thanks! we transferred a bunch of repos to this org when I got the base name on npm.

looks like that did the trick, thanks!
strange though, since the version was current and all of the actual links in package.json were up-to-date and correct afaik...


Is it possible to preload previous/next slides with smoothState?

We've essentially made a page slider with smoothState that will grab the prev/next posts (WordPress) with arrows to them.
Is it possible to load up the prev/next posts?

I noticed https://github.com/miguel-perez/smoothState.js#fetchurl but I'm not really sure how to implement it.

Should be something like:
// Access smoothState
var smoothState = $('#main').smoothState().data('smoothState');

// Run method
smoothState.fetch('/nextPost.html');
smoothState.fetch('/previousPost.html');

Awesome, will give that a try. Thanks!


Chat History

Chat history Management would be a great feature if provided.

@destinychanger  @ryonsteele
https://github.com/microsoft/PubSec-Info-Assistant/issues/464
Is it similar to this right?

@destinychanger @ryonsteele #464
Is it similar to this right?

Yes.


Add test for error handling associated with :page-index: or other options

This isn't possible as it doesn't error but reverts to an old page. An issue needs to be created in draw-desktop.


Update sample-apps tests to use shared resources

Set up shared resources before running, don't tear it down after. Depends on https://github.com/klothoplatform/sample-apps/issues/100

Remaining work: figure out why the test failed:
https://github.com/klothoplatform/klotho/actions/runs/4325952477/attempts/1
py-cloudfs
    aws:s3:Bucket (fs):
      error: 1 error occurred:
      	* Error creating S3 bucket: BucketAlreadyOwnedByYou: Your previous request to create the named bucket succeeded and you already own it.

ts-cloudfs
    aws:s3:Bucket (fs):
      error: 1 error occurred:
      	* Error creating S3 bucket: BucketAlreadyOwnedByYou: Your previous request to create the named bucket succeeded and you already own it.

ts-orm-environment-variable-directive
Fixed in https://github.com/klothoplatform/klotho/pull/316/commits/6152191032f9c27178649f751d13de188049a7be to the PR
ts-redis-cluster
    aws:memorydb:Cluster (integ-test4325952477-redis):
      error: 1 error occurred:
      	* error creating MemoryDB Cluster (integ-test4325952477-redis): ClusterAlreadyExistsFault: Cluster with specified name already exists.


Frontmatter in Layout files

It would be great to be able to add frontmatter to layout files.
Example use case:
/source/layouts/docs.erb
---
css:
  - docs
---

<% wrap_layout :layout do %>

    <%= yield %>

<% end %>

/source/localizable/docs/*.html.erb
---
layout: docs
---

...

This way any file using the docs layout would also have the corresponding CSS file included without having to explicitly call it out in every template that uses the layout.
Another great thing to have on top of this would be the ability to add arbitrary data to layouts, for example:
/source/layouts/android.erb
---
platform: android
---

<% wrap_layout :docs do %>

    <%= yield %>

<% end %>

/source/localizable/docs/android/*.html.erb
---
layout: android
---

<%= current_page.layout.platform %>

.. or something along those lines, allowing a template to inherit and access data from its layout.
After digging through docs and code I don't think either of these features exist for now but they're definitely features I would love to see and have an immediate use for. Do these feature requests make sense within the scope of the project or just in general?

I'm doing some issue-gardening 🌿 🌷 🌾 and came across this issue.
Sorry that this has lingered for quite a while! While I think it's a good idea, I'd suggest either closing this issue or submitting a PR with an implementation.

Wow this is a classic! I think I will close as I'm no longer using middleman. Thanks for checking in!


Allows changing the color picker color using the input fields

This PR allows using the keyboard to change the selected color in the builder color picker. In case the user introduces an invalid input, the fields show an error state:

CR: @nobuti
Closes #8363
Closes #8781

sweet! 🇪🇸


Usage with Angular HttpClient?

I'm submitting a...

[ ] Regression (a behavior that used to work and stopped working in a new release)
[ ] Bug report
[ ] Performance issue
[X] Feature request
[ ] Documentation issue or request
[X] Support request
[ ] Other... Please describe:

Current behavior

I've been trying to figure out how to use this library with Angular HttpClient, so I can use interceptors for error handling, JWT etc.
// angular-base-query.ts

import { HttpClient, HttpParams } from '@angular/common/http';
import { Injector } from '@angular/core';
import type { BaseQueryFn } from '@reduxjs/toolkit/query';
import { lastValueFrom } from 'rxjs';

const injector = Injector.create({
  providers: [{ provide: HttpClient }],
});

const http = injector.get(HttpClient);

export const angularBaseQuery =
  (
    { baseUrl }: { baseUrl: string } = { baseUrl: '' }
  ): BaseQueryFn<
    {
      url: string;
      method?: string;
      data?: any;
      params?: HttpParams;
    },
    unknown,
    unknown
  > =>
  async ({ url, method = 'get', data, params }) => {
    const fullUrl = `${baseUrl}${url}`;

    const request$ = http.request(method, fullUrl, {
      body: data,
      params,
    });

    const result = await lastValueFrom(request$);

    return {
      data: result,
    };
  };

Rest of the code looks like in the examples you provide in the docs.
I know my example code is kinda messy, but the main problem is this error thrown during runtime:

core.mjs:8990 Uncaught NullInjectorError: R3InjectorError[HttpClient -> HttpHandler]:
NullInjectorError: No provider for HttpHandler!
at NullInjector.get (core.mjs:8990:27)
at R3Injector.get (core.mjs:9157:33)
at injectInjectorOnly (core.mjs:4778:33)
at Module.ɵɵinject (core.mjs:4782:12)
at Object.HttpClient_Factory [as factory] (http.mjs:1402:1)
at R3Injector.hydrate (core.mjs:9252:35)
at R3Injector.get (core.mjs:9146:33)
at 41 (angular-base-query.ts:13:23)
at webpack_require (bootstrap:19:1)
at 6546 (artic.api.ts:234:20)

From what I understand, my code runs before the HttpClientModule is properly instantiated, and therefore there is no HttpHandler in the injected HttpClient instance.
I'm quite new to Angular and after trying different approaches I couldn't find a workaround for this. Do you think there is a viable way to use ngrx-rtk-query with HttpClient?
I will try to make a minimal app in StackBlitz and add it later.

I've managed to make it work using APP_INITIALIZER and manual lazy loading. Not sure if this is the right way to do this, but it works. I've uploaded my code to stackblitz, but it won't run there, because ngrx-rtk-query doesn't seem to install properly:
https://angular-ivy-6xe4io.stackblitz.io

I've managed to get it working with this StackOverflow answe:
https://stackoverflow.com/a/49508355

Can you share your complete setup in a repo? 🙂
Would be interested in it. 🥇

@faragos here you go:
https://github.com/szyszak/rtk-query-http-client
It's pretty bare bones, but you should to be able to get started from here.
Please note that I've been using Angular 14 in this repo. ngrx-rtk-query doesn't officially support Angular 14, so you'll have to either force install it, or downgrade Angular version.


install guid

need help to install for windows. iam a realy nooby user

download soruce for windows 10
install guid for soruce and windows 10

https://github.com/mvsoft74/BeatDrop/releases/tag/v<IP_ADDRESS>

thanks, you have seen updates on http://www.geisswerks.com/ ? >
http://www.geisswerks.com/milkdrop/favorite_presets_2020_05.zip


[New azd-template] A Blazor Todo App with Dapr and PostgreSQL

{
title: 'ToDo Application - Blazor C# PostgreSQL',
description:
'A simple Blazor ToDo application, C# for the API, Azure PostgreSQL DB SQL API for storage and Azure Container Apps with Dapr for runtime',
website: 'https://github.com/briandenicola',
author: 'Brian Denicola',
source: 'https://github.com/briandenicola/devcontainer-demo-with-azure-developer-cli',
tags: ['devcontainers','csharp','postgresql','containerapp','dapr','blazor','keyvault','codespaces'],
},

I'm getting an exception when I run azd up on this template.  I will continue to investigate it tomorrow.

This is an interesting case because of the blazor (wasm) limitation of not having access to env vars.  I'm investigating ways that we can automate the setup here.  Related to: https://github.com/Azure/azure-dev/issues/958

@briandenicola - Did this work for you doing azd up?

@briandenicola - Did this work for you doing azd up?

Hi @briandenicola any updates on this?

@briandenicola Do you want to try the new hooks feature to update the URI you need in blazor config? https://learn.microsoft.com/en-us/azure/developer/azure-developer-cli/azd-extensibility


Known Issues

Music does not loop after the track is finished within the main menu (FIXED)
Music does not loop after the track is finished within a level. (FIXED)
The Player can perform a wall jump while they are walking into a wall and remaining on the floor, and not falling. (NOT FIXED)
The Player can perform a jump even after they have began falling off of a tile while running horizontally. (NOT FIXED)

Improve springs? The player is able to jump at the same time the spring activates, which causes the player to not get launched by the spring. Does the spring need some sort of collision because it looks like the player is touch the floor beneath the spring on occasion while encountering this bug. Colliding with the spring collision does not always trigger the spring. Especially when jumping through the bottom of a spring.

Volume sliders currently do not disable the audio when moving the slider all the way to the left. (NOT FIXED)

The Player can perform a wall jump while they are walking into a wall and remaining on the floor, and not falling. (WILL NOT BE FIXED)

Jump animation is playing on repeat while the player is in the air.
When pausing the game, moving platforms will continue to move.
When you pause the game and the player is standing on a moving platform, you will get stuck on a gray screen and you can not return to the gameplay after unpausing. You will remain on the gray screen.


remove veeam kb as premium is retiring

remove veeam kb as premium is retiring

@rpdubose please put a 301 redirect to kb root for this


WIP: Add SimpleRewriter tests

This PR adds tests for SimpleRewriter class.
This PR is a WIP and I haven't completed all tests yet but wanted to get it up so I could add some notes before I forget the reasons for the various changes I've made to SimpleRewriter class.

Removed unused constructor
Split the actual rewriting part to its own method for better testability (and separation of concerns)
Removed $wordpress_site_url from $search_patterns and $destination_url from $replace_patterns as their rewrite is already covered by the trailingslashit version of the same URLs.
Replaced the occurrence of untrailingslashit with trailingslashit. They do the same thing so we should be consistent.
Added runTestsInSeparateProcesses comment to classes with Mockery aliases. See https://laracasts.com/discuss/channels/testing/mocking-a-class-persists-over-tests?reply=103075

Other notes:

Should we have some sort of check for what we should do if file_get_contents fails?
Rather than assign the rewritten contents of $file_contents variable to the $rewritten_contents variable, should we just overwrite $file_contents instead? I'm not sure how PHP memory efficiency works in this respect. I'd assume we're using twice as much memory (now 4x as much with my separate rewriteFileContents method) the way we're doing it at the moment.

Are there any tests I'm missing here? Anything you'd like to see added? If not I think we're good here.

Replaced the occurrence of untrailingslashit with trailingslashit. They do the same thing so we should be consistent

As long as we cover cases in code, that may or may not be slashed. Removing slashes for rewriting covers more potential hits in source

Should we have some sort of check for what we should do if file_get_contents fails?

More knowledge of what happens in any case sounds like a good idea :)

Rather than assign the rewritten contents of $file_contents variable to the $rewritten_contents variable, should we just overwrite $file_contents instead? I'm not sure how PHP memory efficiency works in this respect. I'd assume we're using twice as much memory (now 4x as much with my separate rewriteFileContents method) the way we're doing it at the moment.

Simplest benchmark to confirm (pseudo-code):
$start = microtime(true);

for (1;<10000;++)
  do the routing
end

$end = microtime(true);

$result = $end - $start;

and compare.
This was how I found that using multiple str_replace()'s was faster than using arrays within the str_replace()'s.
At this point though, I'd still say code readability and export reliability should be prioritized over raw performance. So, please go with the most memory efficient+readable code combination you find.

The Static HTML Output  repo has a lot of tests for rewriting, although it does a lot more there with DOM manipulation.
The boundaries I'd try to check for here:
Sources/WP Site URLs:

http://localhost:4444

Edge case there - even if you have that as your WP Site URL, WordPress TwentyTwenty theme will generate URLs in source with protocol-relative and no port, ie //localhost so we need to cover that (probably other plugins and themes also ignore the port in naive implementations). I don't like that we have to do this one, but the rewards (leaving unreplaced URLs in output) outweigh the risks (a complex site that actually has WP on custom port and other app on standard port)
That's the only one I can think of at the moment, but we may need to get some users trying it out to surface any other cases.

oh, forgot to add, can use a Draft feature on GH PR's now

This should be ready for testing. Added every rewrite I could think of including http -> https and vice versa, sites that are on or moving to subdirectories and cslashed URLs.

Looking great to me!
LGTM - quicker now to deal with any issues that are raised, so I'm comfortable with the risk and just won't build a release for a while.
Re the untrailingslashit, maybe we should just stick somewhere within plugin or call the rtrim if we're not using it that much - then can get rid of that extra mock for such tiny function.


Update to React18

Description

What was changed in this pull request?

Update React to react 18
Change hglib.viewer() function to return a promise rather than an object. This is necessary because the React component render isn't necessarily synchronous and we may not have a reference to it immediately. We'll likely have to bump the major version number of the library.

Still have to:

[ ] Add an upgrade guide to the docs

Why is it necessary?

Getting with the times.

Fixes #___
Checklist

[ ] Set proper GitHub labels (e.g. v1.6+, ignore if you don't know)
[ ] Unit tests added or updated
[x] Documentation added or updated
[ ] Example(s) added or updated
[ ] Update schema.json if there are changes to the viewconf JSON structure format
[ ] Screenshot for visual changes (e.g. new tracks or UI changes)
[x] Updated CHANGELOG.md

Hi @pkerpedjiev, just checking in since I am excited about this PR. Do you plan to upgrade React version in the near future? I assume, due to the recent adoption of Vite, this will need to be revisited.

Yeah this PR will need to be rebased on the latest vite changes. I haven't had time to work on it recently but it's something we'll have to do at some point.


build userData classes with setters & getters to implement userParameters?

https://github.com/mOrsExtension/mOrs/blob/9c87c6293b7897a7a118c0a2a5803af943984cd5/content/userData.js#L4

Decided that the commands to userdata are straightforward enough that this isn't saving me any headaches or time.


Pass in the SASL options

Looks like the SASL options weren't passed in.

Would be good to coordinate this with: https://github.com/zendesk/delivery_boy/issues/13 as some people use DB with Rc together.


Fix cors

Resolved CORS issue by whitelisting all origins (zuri.chat, www.zuri.chat)

Resolve conflicts @DannyXY

@DannyXY please attend to the comments and fix your conflict


Remove unused file

Codecov Report

Merging #11766 into master will decrease coverage by 0.01%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master   #11766      +/-   ##
==========================================
- Coverage   60.65%   60.63%   -0.02%
==========================================
  Files         628      628
  Lines       33954    33954
  Branches     4781     4781
==========================================
- Hits        20594    20588       -6
- Misses      12363    12367       +4
- Partials      997      999       +2

Impacted Files
Coverage Δ

src/datascience-ui/react-common/arePathsSame.ts
75.00% <0.00%> (-12.50%)
:arrow_down:

src/client/common/utils/platform.ts
64.70% <0.00%> (-11.77%)
:arrow_down:

src/client/linters/pydocstyle.ts
86.66% <0.00%> (-2.23%)
:arrow_down:

src/client/datascience/debugLocationTracker.ts
76.56% <0.00%> (-1.57%)
:arrow_down:

src/client/common/process/proc.ts
14.49% <0.00%> (-0.73%)
:arrow_down:

Continue to review full report at Codecov.

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


KAFKA-5658. Fix AdminClient request timeout handling bug resulting in continual BrokerNotAvailableExceptions

The AdminClient does not properly clear calls from the callsInFlight structure. Later, in an effort to clear the lingering call objects, it closes the connection they are associated with. This disrupts new incoming calls, which then get BrokerNotAvailableException.
This patch fixes this bug by properly removing completed calls from the callsInFlight structure.  It also adds the Call#aborted flag, which ensures that we only abort a connection once-- even if there is a similar bug in the future which causes old Call objects to linger.

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/kafka-pr-jdk8-scala2.12/6409/
Test FAILed (JDK 8 and Scala 2.12).

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/kafka-pr-jdk7-scala2.11/6424/
Test FAILed (JDK 7 and Scala 2.11).

retest this please

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/kafka-pr-jdk7-scala2.11/6451/
Test FAILed (JDK 7 and Scala 2.11).

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/kafka-pr-jdk8-scala2.12/6436/
Test FAILed (JDK 8 and Scala 2.12).

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/kafka-pr-jdk8-scala2.12/6492/
Test FAILed (JDK 8 and Scala 2.12).

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/kafka-pr-jdk7-scala2.11/6506/
Test FAILed (JDK 7 and Scala 2.11).

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/kafka-pr-jdk7-scala2.11/6507/
Test PASSed (JDK 7 and Scala 2.11).

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/kafka-pr-jdk8-scala2.12/6493/
Test PASSed (JDK 8 and Scala 2.12).

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/kafka-pr-jdk7-scala2.11/6621/
Test PASSed (JDK 7 and Scala 2.11).

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/kafka-pr-jdk8-scala2.12/6606/
Test PASSed (JDK 8 and Scala 2.12).


WASI directory map not implemented

It seems the "map_dir_list" is not implemented to allow sandboxing the filesystem properly. There is a need to provide virtual mapping to control where wasm apps store their data.

May I ask at which WASI APIs we are looking? https://github.dev/WebAssembly/WASI/blob/main/phases/ephemeral/witx

wasm_runtime_set_wasi_args_ex(WASMModuleCommon *module, const char *dir_list[],                               uint32 dir_count, const char *map_dir_list[],                               uint32 map_dir_count, const char *env_list[],                               uint32 env_count, char *argv[], int argc,                               int stdinfd, int stdoutfd, int stderrfd) in "wasm_runtime_common.c"
"map_dir_list" is set but never used anywhere in the code to setup the virtual mapping of filesystem paths.

That looks like that's a miss; I wonder if we can, while fixing this, also expose --mapdir parameter in iwasm similar to wasmtime so we can also specify mapping through CLI in addition to programmatic interface.

There will be two steps for implementation:

If WAMR_BUILD_LIBC_UVWASI=1. after taking input argument from --mapdir(need to do),  mapped_path will pass the value to uvwasi_preopen_t (already done).

Otherwise, implement mapping filesystem paths in libc_wasi (need to do)


Better Markdown Syntax

While GitHub can interprete Markdown with no blank line after a header (###, ##, #) most Markdown tools prefer a blank line after it. Adding a blank line also should not generate any new issues as the Markdown interpreter auto chooses how much blank space is required.
Therefore we should add a further "/n" in here at the end, here after the "## Radarplot" and after the .svg file and here.

Should be fixed by Commit 74924c320f2da02dcc57ea568aa5c175606c09af @HendrikBorgelt could you please verify?

Yes, the syntax errors were successfully fixed.


Consider switching from fast_double_parse to fast_float

https://github.com/microsoft/LightGBM/blob/fb37e5074ad0163afd9d88366b58075899775cfa/include/LightGBM/utils/common.h#L354-L373
fast_double_parse is a legacy library (see for example https://github.com/lemire/fast_double_parser/issues/66 ) . fast_float is preferred, maintained, and has better API. Same author.
Code above also claims inf and nan are not supported, and reverts to strtod, but afaik both fast_double_parser and fast_float do support them.

It took me a minute to understand what you meant. In case you haven't seen, it is possible to link to individual comments in GitHub.
I think you're referring to https://github.com/lemire/fast_double_parser/issues/66#issuecomment-1309071297:

I recommend ...https://github.com/fastfloat/fast_float ... The fast_double_parser library is [something] I would like to retire ... New users should adopt fast_float

Thanks very much for this! We'll take this as a feature request. Are you interested in working on it? Otherwise, it's something that probably won't be considered until after the next major release of LightGBM (#5153). Since LightGBM vendors fast_double_parse as a git submodule, LightGBM's usage of that library is heavily tested and we're fairly confident that it's working as expected today.

BTW. Code above also claims inf and nan are not supported, and reverts to strtod. I think this might be true for fast_double_parse, but fast_float does handle it automatically, so the code would also reduce.
https://github.com/fastfloat/fast_float/blob/main/include/fast_float/parse_number.h#L32-L58

@jameslamb I personally do not use LightGBM, it is just a very small part of a way bigger part of code base that I am maintaining, but sporadically causing dependency issues.

oooooh interesting, so by vendoring fast_double_parse, LightGBM is also passing along those leftover defines. I see, thanks for that context. Very interesting!
Thanks for taking the time to report this, and for the link to the corresponding discussion in fast_double_parse.


Feature: Add events before and after mobile category view

Two new events have been added to the mobile view of the shop layout. These events are triggered before and after the category view is rendered. This could assist in adding custom functionality or tracking user interaction with this section.
Issue Reference
There is no way no in mobile drawer to add links before or after the categories.
Description
If you need to add a new link, like "Blog" for example, you can do that on Desktop view, but in mobile view, there is no way without changing the Theme files to add links before or after the categories.
By adding these view_render_event('...') before and after <v-mobile-category> you can now add your own menus, or some other packages can add their own.
How To Test This?
You can add an Event listener that inserts the link there like these example:
Event::listen('bagisto.shop.components.layouts.header.mobile.drawer.categories.after', function($viewRenderEventManager) {
              $template = '

                      Blog

';
            $viewRenderEventManager->addTemplate($template);
        });

@ag84ark, thank you for your contribution, it's greatly appreciated!


Combining ODE and PDE

I would like to create an advection-reaction simulation that combines LaGrangian and Eulerian frames of reference, which means combining ODEs and PDEs together in one system:
using ModelingToolkit, MethodOfLines, OrdinaryDiffEq, DomainSets
using Plots

@parameters x y t
@variables so4(..)
@variables xx(t) yy(t) so2_puff(t)
Dt = Differential(t)
Dx = Differential(x)
Dy = Differential(y)

x_min = y_min = t_min = 0.0
x_max = y_max = 1.0
t_max = 7.0

N = 2

dx = (x_max-x_min)/N
dy = (y_max-y_min)/N

# Interaction between Eulerian and Lagrangian frames of reference
puff_conc(x,y,t) = IfElse(x-dx/2 < xx < x+dx/2 && y-dy/2 < yy < y+dy/2, so2_puff(t), 0.0)
@register puff_conc(x, y, t)

# Circular winds.
θ(x,y) = atan(y.-0.5, x.-0.5)
u(x,y) =  -sin(θ(x,y))
v(x,y) = cos(θ(x,y))

k=0.01 # k is reaction rate
eq = [
    # Lagrangian puff model.
    Dt(xx) ~ u(xx,yy),
    Dt(yy) ~ v(xx,yy),
    Dt(so2_puff) ~ -k*so2_puff,

    # Eulerian model.
    Dt(so4(x,y,t)) ~ -u(x,y)*Dx(so4(x,y,t)) - v(x,y)*Dy(so4(x,y,t)) + k*puff_conc(x,y,t),
]

domains = [x ∈ Interval(x_min, x_max),
              y ∈ Interval(y_min, y_max),
              t ∈ Interval(t_min, t_max)]

# Periodic BCs
bcs = [so4(x,y,t_min) ~ 0.0,
       so4(x_min,y,t) ~ so4(x_max,y,t),
       so4(x,y_min,t) ~ so4(x,y_max,t),
]

@named pdesys = PDESystem(eq,bcs,domains,[x,y,t],[so4(x,y,t), xx, yy, so2_puff])

discretization = MOLFiniteDifference([x=>dx, y=>dy], t, approx_order=2, grid_align=center_align)
@time prob = discretize(pdesys,discretization)

I guess there might be a couple of problems with this, but the first one that shows up is this:
The system of equations is:
Equation[Differential(t)(xx(t)) ~ -sin(atan(yy(t) - 0.5, xx(t) - 0.5)), Differential(t)(yy(t)) ~ cos(atan(yy(t) - 0.5, xx(t) - 0.5)), Differential(t)(so2_puff(t)) ~ -0.01so2_puff(t), Differential(t)(so4[2, 2](t)) ~ 0.01puff_conc(0.5, 0.5, t) + 2.0so4[2, 3](t) - 2.0so4[2, 2](t), Differential(t)(so4[3, 2](t)) ~ 0.01puff_conc(1.0, 0.5, t) + 2.0so4[3, 3](t) - 2.0so4[3, 2](t), Differential(t)(so4[2, 3](t)) ~ 0.01puff_conc(0.5, 1.0, t) + 1.2246467991473532e-16so4[2, 2](t) + 2.0so4[3, 3](t) - 2.0so4[2, 3](t), Differential(t)(so4[3, 3](t)) ~ 0.01puff_conc(1.0, 1.0, t) + 1.414213562373095so4[2, 3](t) + 1.4142135623730951so4[3, 2](t) - 2.82842712474619so4[3, 3](t), so4[2, 1](t) ~ so4[2, 3](t), so4[3, 1](t) ~ so4[3, 3](t), so4[1, 2](t) ~ so4[3, 2](t), so4[1, 3](t) ~ so4[3, 3](t), so4[1, 1](t) ~ 0][Base.OneTo(12)]

Discretization failed, please post an issue on https://github.com/SciML/MethodOfLines.jl with the failing code and system at low point count.

Term{Real, Base.ImmutableDict{DataType, Any}}[so2_puff(t), so4[1, 1](t), so4[2, 1](t), so4[3, 1](t), so4[1, 2](t), so4[2, 2](t), so4[3, 2](t), so4[1, 3](t), so4[2, 3](t), so4[3, 3](t), xx(t), yy(t)][Base.OneTo(12)]
ERROR: ArgumentError: Term{Real, Base.ImmutableDict{DataType, Any}}[xx(t), yy(t), so2_puff(t)] are missing from the variable map.
Stacktrace:
...

Thanks in advance for any information you might have regarding whether this type of simulation should be expected to work, or any suggestions for going about fixing it. Thanks!

I've not seen anyone get this working, but a few things to try:

Don't register puff_conc, should be fine as is.
Give xx, yy and so2_puff (t) wherever they appear.
Give xx, yy and so2_puff  initial condiitions .
Don't broadcast in θ.

Let me know if that changes anything.

There is a test that does a simpler version of this: https://github.com/SciML/MethodOfLines.jl/blob/17f4cbf786d733d9b487efe3b708ae77771d180e/test/pde_systems/MOL_1D_Linear_Diffusion.jl#L742-L789
So it is definitely possible

Thanks! The problem turned out to be that @variables xx(t) yy(t) so2_puff(t) needs to be @variables xx(..) yy(..) so2_puff(..) and
    Dt(xx) ~ u(xx,yy),
    Dt(yy) ~ v(xx,yy),
    Dt(so2_puff) ~ -k*so2_puff,

needs to be
    Dt(xx(t)) ~ u(xx(t),yy(t)),
    Dt(yy(t)) ~ v(xx(t),yy(t)),
    Dt(so2_puff(t)) ~ -k*so2_puff(t),

and then corresponding boundary conditions need to be added.
I'm still having a problem getting the interaction between the two frames of reference to work, but I'll create a separate issue if I'm not able to figure it out. Thanks again!


Fetch non-cached reports in parallel

Currently, if a bunch of requested reports aren't in the cache, we fetch them one at a time inline with the request. This patch updates the code to fetch reports in parallel instead.
While making the change, I noticed that we handled S3 errors differently from gzip & decoder errors. I've updated the code to handle all errors in the same way (i.e. no special logging, just return).
Currently, getNonCached returns only the first error it finds. It should probably aggregate all of the errors somehow so we aren't silently ignoring important conditions. I don't know how best to do that.
Along the way, I extracted the logic for fetching a single report (to make the actual parallelism logic more clear).

This change is

Did you see any performance improvement running this on your laptop?

Haven't actually run it on my laptop, so will at least do that before landing.
I'll also at least attempt to write unit tests (but might end up deciding they're too hard).

Ran this locally & verified that it doesn't break. No metrics. Won't bother with unit tests now.
@tomwilkie OK to merge

@tomwilkie asked for metrics:
Before

After

Running on my laptop locally.

LGTM


Idle timeout fix

Codecov Report

Merging #40 into master will decrease coverage by 0.11%.
The diff coverage is 41.17%.

@@             Coverage Diff              @@
##             master      #40      +/-   ##
============================================
- Coverage     67.21%   67.09%   -0.12%
- Complexity      653      655       +2
============================================
  Files            45       45
  Lines          3303     3316      +13
  Branches        473      475       +2
============================================
+ Hits           2220     2225       +5
- Misses          902      908       +6
- Partials        181      183       +2

Impacted Files
Coverage Δ
Complexity Δ

...l/src/main/java/com/google/api/control/Client.java
46.83% <41.17%> (-0.26%)
20 <6> (+2)

Continue to review full report at Codecov.

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

Threads shutdown in dev server, I'm verifying task shutdown in prod App Engine now.

Can you write tests to verify the startup and shutdown works as intended?

Tests are pretty hard to do given the existing structure of the code and tests. This is more or less only truly testable end-to-end in production.


added gestures

closes: https://github.com/AR-js-org/studio-backend/issues/33
@le0m to be tested

it's working! gg


[SR-13415] Xcode 12b5: source incompatibility w/ generic overloads & trailing closures

Previous ID
SR-13415

Radar
rdar://problem/67451813

Original Reporter
rydermackay (JIRA User)

Type
Bug

Environment
Xcode 12b5 (12A8189h)
macOS 11.0b4 (20A5343i)

Additional Detail from JIRA

Votes
0

Component/s

Labels
Bug, TypeChecker

Assignee
None

Priority
Medium

md5: be271db21582958117b1f424ae61ac39

Issue Description:
I'm not sure if this a regression or a case of ill-formed code no longer being accepted.
Part of our codebase uses ReactiveSwift which defines types similar to the following:
struct Box<Value> {
    let value: Value
}

extension Box {
    // 1.
    func map<T>(_ f: @escaping (Value) -> T) -> Box<T> {
        return Box<T>(value: f(value))
    }

    // 2.
    func map<T>(_ value: T) -> Box<T> {
        return map { _ in value }
    }

    // 3.
    func map<T>(_ keyPath: KeyPath<Value, T>) -> Box<T> {
        return map { $0[keyPath: keyPath] }
    }
}

I just noticed that our own client code, which has "worked" for several releases, no longer compiles in Xcode 12b5. It looks more or less like this:
func test(input: Box<Void>) -> Box<String> {
    // Xcode 12b4: output is Box<String> (overload #1)
    // Xcode 12b5: output is Box<() -> String> (overload #2, but only when #3 exists!!)
    let output = input.map { "foo" }
    return output
}

The really weird thing is it compiles if I remove the seemingly unrelated overload 3 that takes a key path.
I wonder if this might be related to the recent forward scanning trailing closures changes?

@DougGregor ping.
Revision update: Swift 5.9-dev (c1d5118c21d)


nginx: change location configuration file to /etc/nginx/nginx.conf

Motivation for this change
Change location configuration file to /etc/nginx/nginx.conf
Simple viewing of the current configuration.
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Assured whether relevant documentation is up to date
[ ] Fits CONTRIBUTING.md.

I prefer not to do this. The current state allows for users to run these services ad-hoc, without any NixOS system even, with nix-build '<nixpkgs/nixos>' -A config.systemd.services.nginx.runner, and I think some people do indeed make use of this with nginx in their nix-shells. This change would make it dependent on a NixOS system and break this very neat functionality.
For easily viewing config files, I prefer to have modules export a configFile option, so people can vim $(nix-build '<nixpkgs/nixos>' -A config.services.foo.configFile to view it, which has the added side benefit of users being able to supply their own config file.


[Homepages] Include alert if the plugin or theme is not translated

Include an alert text in the top of the plugin or theme if not yet translated to the language.

https://plugins.bludit.com
https://themes.bludit.com

Implemented.


Mismatching Ethereum Xpubs

From the following mnemonic, I have generated its corresponding Ethereum xpub using the current online version of the Mnemonic Code Converter (derivation path: m/44'/60'/0'/0/0).
Mnemonic: myth like bonus scare over problem client lizard pioneer submit female collect (for testing purposes, generated by Ganache)
Mnemonic Code Converter generates—using configuration: ETH - Ethereum, BIP44, default derivation path—the following data:

Account Extended Public Key: xpub6DNro2eEZk9SreVWArMUamKzpa4oV7bJ9T8ffVKxbDPxrhToccxwCLg97v2ct8tk8TNsUEUj6XCUzQmb6LGzZTANdZDPC2KqLk4o3EnPfFi
BIP32 Extended Public Key: xpub6EEDNF2mvRWBANmVjeB1n5ZMWszXnzXUL4u3VMq673qU9HNJ1zvXPLuxpUUmAVDom7Cg2iMDfQtoPL2MALL4qKB3RWsn5BAquLDd3US5XFU

In parallel, I have generated the xpub using the following script:
import * as ethers from "ethers";
import * as bip39 from "bip39";
import HDKey from "hdkey";
import * as assert from "assert";

const mnemonic =
  "myth like bonus scare over problem client lizard pioneer submit female collect";

const derivationPath = "m/44'/60'/0'/0/0";

// Generate the xpub using two different libraries

const mnemonicToXpubMethod1 = (mnemonic: string, derivationPath: string) => {
  const HDNode = ethers.utils.HDNode;
  const masterNode = HDNode.fromMnemonic(mnemonic);
  const standardEthereum = masterNode.derivePath(derivationPath);

  const xpub = standardEthereum.neuter().extendedKey;

  console.log("xpub generated using the `ethers` library:", xpub);

  return xpub;
};

const mnemonicToXpubMethod2 = async (
  mnemonic: string,
  derivationPath: string
) => {
  const seed = await bip39.mnemonicToSeed(mnemonic);

  const master = HDKey.fromMasterSeed(seed);
  const child = master.derive(derivationPath);

  const xpub = child.publicExtendedKey;

  console.log("xpub generated using the `bip39` library: ", xpub);

  return xpub;
};

const run = async () => {
  console.log("Mnemonic:", mnemonic);
  console.log("Correct derivation path:", derivationPath);

  const xpubA = mnemonicToXpubMethod1(mnemonic, derivationPath);
  const xpubB = await mnemonicToXpubMethod2(mnemonic, derivationPath);

  // both xpubs should be strictly identical
  assert.strictEqual(xpubA, xpubB);
};

run();

The xpub generated by this script (using two different libraries) is: xpub6GkCbW4FDnz8k9zhroVhZefi9fXhFFuTmmcQqfQKPDBrQjtSu4pdLpQ1Tje1BAzUw6PbJ47MMtNZ4RYM42VzRNxwaYUFnm3R44Lejvh9nHE. It differs from the xpubs generated by Mnemonic Code Converter
Interestingly, your tool correctly derives the expected addresses from the mnemonic (0x90F8bf6A479f320ead074411a4B0e7944Ea8c9C1, etc.).
Do you perhaps know why the xpubs generated by Mnemonic Code Converter and the one generated by my script differ?
Thank you in advance for your assistance.

I don't know anything about ethereum, but:
Does ethereum have test vectors, or do you have any other "knowns", that you can force into the different steps in your script?
Try adding a debug mode that prints out forced-ascii (like bash cat -A) or hashes or lengths or similar of every input and output of every command line.
Does the order of the "import" statements matter?

Thank you @petjal.

I am not aware of reliable test vectors (that is: mnemonic → xpub, as far as Ethereum is concerned).
The xpub generated by my script seems to be correct. Indeed, the expected address is derived from this xpub (using two different libraries). See the full source code below. Therefore, I was wondering if it may be an issue with the Mnemonic Code Converter (hence my initial question). In other words, I have reasons to believe that:

myth like bonus scare over problem client lizard pioneer submit female collect
⇩
xpub6GkCbW4FDnz8k9zhroVhZefi9fXhFFuTmmcQqfQKPDBrQjtSu4pdLpQ1Tje1BAzUw6PbJ47MMtNZ4RYM42VzRNxwaYUFnm3R44Lejvh9nHE (xpub generated by the script but not by the Mnemonic Code Converter)
⇩
0x90f8bf6a479f320ead074411a4b0e7944ea8c9c1 (address derived by both script and Mnemonic Code Converter)
Source code of the script generating the xpub and the address from the mnemonic:
import * as ethers from "ethers";
import * as bip39 from "bip39";
import HDKey from "hdkey";
import { HDNode } from "@findeth/hdnode";
import Wallet from "ethereumjs-wallet";
import * as assert from "assert";

const mnemonic =
  "myth like bonus scare over problem client lizard pioneer submit female collect";

const derivationPath = "m/44'/60'/0'/0/0";

// Generate xpub using two different libraries

const mnemonicToXpubMethod1 = (mnemonic: string, derivationPath: string) => {
  const HDNode = ethers.utils.HDNode;
  const masterNode = HDNode.fromMnemonic(mnemonic);
  const standardEthereum = masterNode.derivePath(derivationPath);

  const xpub = standardEthereum.neuter().extendedKey;

  console.log("xpub generated using the `ethers` library:", xpub);

  return xpub;
};

const mnemonicToXpubMethod2 = async (
  mnemonic: string,
  derivationPath: string
) => {
  const seed = await bip39.mnemonicToSeed(mnemonic);

  const master = HDKey.fromMasterSeed(seed);
  const child = master.derive(derivationPath);

  const xpub = child.publicExtendedKey;

  console.log("xpub generated using the `bip39` library: ", xpub);

  return xpub;
};

// Derive address from xpub using two different libraries

const deriveAddressMethod1 = (xpub: string) => {
  const address = HDNode.fromExtendedKey(xpub).address;
  console.log(
    "Address derived using the `@findeth/hdnode` library:\t  ",
    address
  );

  return address;
};

const deriveAddressMethod2 = (xpub: string) => {
  const address = Wallet.fromExtendedPublicKey(xpub).getAddressString();
  console.log(
    "Address derived using the `ethereumjs-wallet` library:\t  ",
    address
  );

  return address;
};

const run = async () => {
  console.log("Mnemonic:", mnemonic);
  console.log("Derivation path:", derivationPath);

  const xpubA = mnemonicToXpubMethod1(mnemonic, derivationPath);
  const xpubB = await mnemonicToXpubMethod2(mnemonic, derivationPath);

  // both xpubs should be strictly identical
  assert.strictEqual(xpubA, xpubB);

  const addressA = deriveAddressMethod1(xpubA);
  const addressB = deriveAddressMethod2(xpubB);

  // both addresses should be identical (case insensitive)
  assert.notStrictEqual(addressA, addressB);
};

run();

Output:
Mnemonic: myth like bonus scare over problem client lizard pioneer submit female collect
Derivation path: m/44'/60'/0'/0/0
xpub generated using the `ethers` library: xpub6GkCbW4FDnz8k9zhroVhZefi9fXhFFuTmmcQqfQKPDBrQjtSu4pdLpQ1Tje1BAzUw6PbJ47MMtNZ4RYM42VzRNxwaYUFnm3R44Lejvh9nHE
xpub generated using the `bip39` library:  xpub6GkCbW4FDnz8k9zhroVhZefi9fXhFFuTmmcQqfQKPDBrQjtSu4pdLpQ1Tje1BAzUw6PbJ47MMtNZ4RYM42VzRNxwaYUFnm3R44Lejvh9nHE
Address derived using the `@findeth/hdnode` library:	   0x90F8bf6A479f320ead074411a4B0e7944Ea8c9C1
Address derived using the `ethereumjs-wallet` library:	   0x90f8bf6a479f320ead074411a4b0e7944ea8c9c1


test: integration tests for env manager

PR Description
Integration tests for the feature environment manager.
Related Issues

Related Issue #445
Closes #445

Checklist

[x] I have gone through the contributing guide
[x] I have updated my branch and synced it with project main branch before making this PR
[x] I have run the tests (flutter test) and all tests are passing

Added/updated tests?
We encourage you to add relevant test cases.

[x] Yes
[ ] No, and this is why: please replace this line with details on why tests have not been included

A test failed for this PR:
/Documents/GitHub/apidash/test/providers/ui_providers_test.dart: Testing navRailIndexStateProvider UI should update correctly when navRailIndexStateProvider changes
══╡ EXCEPTION CAUGHT BY FLUTTER TEST FRAMEWORK ╞════════════════════════════════════════════════════
The following TestFailure was thrown running a test:
Expected: exactly one matching candidate
  Actual: _IconWidgetFinder:<Found 0 widgets with icon "IconData(U+0F153)": []>
   Which: means none were found but one was expected

When the exception was thrown, this was the stack:
#4      main.<anonymous closure>.<anonymous closure> (file:///Documents/GitHub/apidash/test/providers/ui_providers_test.dart:220:7)
<asynchronous suspension>
#5      testWidgets.<anonymous closure>.<anonymous closure> (package:flutter_test/src/widget_tester.dart:183:15)
<asynchronous suspension>
#6      TestWidgetsFlutterBinding._runTestBody (package:flutter_test/src/binding.dart:1017:5)
<asynchronous suspension>
<asynchronous suspension>
(elided one frame from package:stack_trace)

This was caught by the test expectation on the following line:
  file:///Documents/GitHub/apidash/test/providers/ui_providers_test.dart line 220
The test description was:
  UI should update correctly when navRailIndexStateProvider changes
════════════════════════════════════════════════════════════════════════════════════════════════════
00:18 +179 -1: /Documents/GitHub/apidash/test/providers/ui_providers_test.dart: Testing navRailIndexStateProvider UI should update correctly when navRailIndexStateProvider changes [E]
  Test failed. See exception logs above.
  The test description was: UI should update correctly when navRailIndexStateProvider changes

To run this test again: /Documents/flutter/bin/cache/dart-sdk/bin/dart test /Documents/GitHub/apidash/test/providers/ui_providers_test.dart -p vm --plain-name 'Testing navRailIndexStateProvider UI should update correctly when navRailIndexStateProvider changes'


Can we do ready() implicitly?

I understand that we need some initialization tasks before the db will be ready to use, so the code in the ready() is necessary.
However, the current design will force the user to call ready() before using the SnapDb, which I believe can be done inside the library itself.
I will get wrong with the following code:
const db = new SnapDb()
// await db.ready()
await db.put('a','b')

I would love to get it to work without the ready() call.

This feature will be live in version 1.1.2

Thank you very much for your improvement!
It will help me to solve my problems inside my library, cheers!

1.1.2 is now live on NPM, this issue has been resolved.  Feel free to comment if you find anything further!


Support Laravel ^6.0

Laravel 6 will be released on Sep 3.
I was wondering why Travis-CI was not triggered for this PR.
Please enable travis-ci for this repo.
Laravel 6 will be a LTS release, so i have dropped all previous version support.

@benwilkins
You can see travis-ci results here
https://travis-ci.com/ankurk91/laravel-fcm-notification/builds/125407078

@benwilkins
I would be great if we can get Laravel 6.0 support, since it has been released.
Thanks

Waiting for this package to support Laravel 6 before we can upgrade as well!

@ankurk91  This PR wouldn't be backwards compatible with L5.5. Why remove that functionality and not just add 6.0 as an option?

@benwilkins
I have updated the PR to allow Laravel 5.5+, have a look.
I think it is good time to remove support for 5.3 and 5.4.


[Bug] k8s application flinksql mode maven pom does not work

Please answer these questions before submitting your issue. Thanks!
Environment Description

StreamX Version:  1.2.1
JVM version (java -version): 1.8
OS version (uname -a if on a Unix-like system):  centos 7.6
Linux app-01 3.10.0-1127.19.1.el7.x86_64 #1 SMP Tue Aug 25 17:23:54 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

Bug Description

k8s application flinksql mode maven pom does not work,
when i added same jars  by Dependency Maven pom or upload jar,such as flink-sql-connector-kafka_2.11-1.14.2.jar. .
auto generate Dockerfille
CP lib $FLINK_HOME/lib/ does not works

anyway ,i try another way ,i build  a images with depency jars,also does not work ,i suggest
CP lib $FLINK_HOME/lib/  need change to
CP lib/*  FLINK_HOME/lib/

How to Reproduce
Steps to reproduce the behavior, for example:

Go to '...'
Click on '....'
Scroll down to '....'
See error

Additional context
Add any other context about the problem here such as JVM track stack log.
Requirement or improvement

Please describe about your requirements or improvement suggestions.

fixed in new version


How to change color of folder

Im attempting to migrate from nvim-tree to neo-tree and just looking for some help on how to do 2 things;

Change the color of the folders

I would like the colors folder color to be blue but by default it appears to be green.

Change the position of the github/diagnostic icons

Is it possible for the icon position to be shown at the front (before the filename).
Left (nvim-tree) Right (neo-tree)

thank you.

@kaykhan Regarding the folder colors, you can modify the highlight groups NeoTreeDirectoryIcon and NeoTreeDirectoryName to your liking. A complete list of highlight groups can be viewed here.
For the diagnostic/git status icons, you can modify the renderers like this
require("neo-tree").setup({
  renderers = {
    directory = {
      { "indent" },
      { "icon" },
      { "current_filter" },
      { "diagnostics", errors_only = true, hide_when_expanded = true },
      { "git_status", hide_when_expanded = true },
      { "name" },
      { "clipboard" },
    },
    file = {
      { "indent" },
      { "icon" },
      { "diagnostics" },
      { "git_status" },
      { "name" },
      { "clipboard" },
      { "modified" },
    },
  },
})

Have a look at here and the wiki for these customizations.


Lightbox image zoomed in from carousel

Hi there!
When clicking on an item in the carousel to display the lightbox, the image is zoomed to 100% width of the screen..  I am working with version 1.7.18.

yes, the wide lightbox is opens 100%. if you want, you can change to
compact lightbox, then it will be a bit smaller.
On Sat, May 7, 2016 at 2:49 PM, krissl94<EMAIL_ADDRESS>wrote:

Hi there!
When clicking on an item in the carousel to display the lightbox, the
image is zoomed to 100% width of the screen.. I am working with version
1.7.18.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
https://github.com/vvvmax/unitegallery/issues/72

If this is supposed to happen, why doesn't it happen with other themes?

HI. I need to see what you talking about. right now I don't understand.
Please write me a ticket: valiano.ticksy.com
send me a link to your gallery so I could look.
if it some bug, then I'll try to fix it.
On Tue, May 10, 2016 at 1:46 PM, krissl94<EMAIL_ADDRESS>wrote:

If this is supposed to happen, why doesn't it happen with other themes?
—
You are receiving this because you commented.
Reply to this email directly or view it on GitHub
https://github.com/vvvmax/unitegallery/issues/72#issuecomment-218122529

You can see the bug occuring here.
When you click on an image, the lightbox is opened with the image zoomed in.

HI. you have too many options here:
Common.initializeGalleries = function(){
in this file:
http://tharprojects.nl/edityourweb/js/common.js?1462622348
I can't understand what option exactly affecting scale mode.
Please run the gallery without all the modifications and check.
then return them one by one.
On Sat, May 14, 2016 at 11:03 AM, krissl94<EMAIL_ADDRESS>wrote:

You can see the bug occuring here
http://tharprojects.nl/edityourweb/carouselexample.
When you click on an image, the lightbox is opened with the image zoomed
in.
—
You are receiving this because you commented.
Reply to this email directly or view it on GitHub
https://github.com/vvvmax/unitegallery/issues/72#issuecomment-219207233


Kafka Inbound endpoint properties are missing in docs

Description
SET_ROLLBACK_ONLY, failure.retry.count, and enable.auto.commit properties are not documented in 4.2.0 and 4.3.0 docs. It is in [1]. We need to bring them to 4.2.0 and 4.3.0 docs
[1] https://github.com/wso2-extensions/esb-inbound-kafka/blob/master/docs/config.md
Steps to Reproduce
SET_ROLLBACK_ONLY, failure.retry.count, and enable.auto.commit properties are not documented in 4.2.0 and 4.3.0 docs. It is in [1]. We need to bring them to 4.2.0 and 4.3.0 docs
[1] https://github.com/wso2-extensions/esb-inbound-kafka/blob/master/docs/config.md
Version
4.2.0
Environment Details (with versions)
No response

PR: https://github.com/wso2/docs-mi/pull/1114


trackupstream: Also track openstack-octavia in C:O:Master

We recently added the openstack-octavia packages to
Cloud:OpenStack:Master. Track the new package.

+1

+1

No gating needed here. Merging...


Visual C++ multithreaded: srand(time(NULL)). Same seeding for one second.

I have visual c++ application (at least VS2013+debug win64 libs) with usrsctp_init and usrsctp_connect performed immediately after launch. I start 10 apps at the same time. Each SCTP_INIT have the same initial vtag and 9 apps unable to connect.
This is because time(NULL) is the same for all 10 apps and is not appropriate choice for srand() seed.
usrsctplib need more complicated seed for srand.

Can you checkout the Issue66 branch and see if it fixes your issue?

Should be fixed by having merged branch issue66.


Bug: Multiple automatic triggers occurring in a pipeline which is configured manual

📜 Description

Description: In a ci-pipeline, there's a manual configuration set up a long time back. However, we're now experiencing multiple automatic triggers with various branches, despite no recent commits. This unexpected behavior is causing confusion.
We're unable to identify the root cause of these triggers and need assistance in debugging this issue. Please let us know if any additional information is required from our end to resolve this issue effectively.
Affected areas
CI
Additional affected areas
None
Prod/Non-prod environments?
Prod
Is User unblocked?
Yes
How was the user un-blocked?
None
Impact on Enterprise
NA
👟 Steps to replicate the Issue
NA
👍 Expected behavior
NA
👎 Actual Behavior
NA
☸ Kubernetes version
1.26
Cloud provider

eks

🌍 Browser
Chrome
✅ Proposed Solution
No response
👀 Have you spent some time to check if this issue has been raised before?

[X] I checked and didn't find any similar issue

🏢 Have you read the Code of Conduct?

[X] I have read the Code of Conduct

AB#9556

The event is coming across multiple clusters and we are fetching the workflow Id on the basis of workflow name. Thus, triggering the build. For now we have set INCLUSTER mode. This also needs to be fixed from the code side.


Finer grained source caching (tech-debt)

See original issue on GitLab
In GitLab by [Gitlab user @raoul].hidalgocharman on Apr 2, 2019, 17:22
Background
A follow up to !1124 and !1214, sources are currently cached and staged altogether, due to some plugins (i.e. patch) requiring previous sources staged to make sense. Being able to more finely cache sources would be beneficial however, allowing more sharing between both elements and different projects.
To allow for this we need to add another flag to plugins, very similar to the existing flags BST_REQUIRES_PREVIOUS_SOURCES_TRACK/FETCH, for staging. This should only require changes to logic in the Element class, to ensure that sources are staged appropriately depending on whether they require previous sources or not. All sources before a source plugin marked to require previous sources to stage will have to be staged together as they currently are, all afterwards can be staged separately. This will have to be taken into account both where they are staged and where they are cached, as well as for key generation.
Task description

[ ] Add BST_REQUIRES_PREVIOUS_SOURCES_TRACK, and logic in Element that uses it.
[ ] Look through and mark relevant plugins with this flag (think it's only patch in the main repo)
[ ] Add some tests to ensure that sources are staged separately when possible.

Acceptance Criteria
Extra tests that show sources are staged separately when appropriate.

In GitLab by [Gitlab user @raoul].hidalgocharman on Apr 2, 2019, 17:23
changed the description

In GitLab by [Gitlab user @raoul].hidalgocharman on Apr 2, 2019, 17:23
changed the description

In GitLab by [Gitlab user @raoul].hidalgocharman on Apr 30, 2019, 18:13
mentioned in commit 6bc6f22f0c8bce165539885f84ad22f4e75c3ba6

In GitLab by [Gitlab user @raoul].hidalgocharman on Apr 30, 2019, 18:15
mentioned in merge request !1319

In GitLab by [Gitlab user @raoul].hidalgocharman on May 1, 2019, 10:46
mentioned in commit a17ab4e1706a760edbb1a2e02c67892318dc1878

In GitLab by [Gitlab user @raoul].hidalgocharman on May 1, 2019, 11:20
mentioned in commit b018d21a9b6cc0cd40c5108a1ab12087d49f5664

In GitLab by [Gitlab user @raoul].hidalgocharman on May 8, 2019, 12:40
mentioned in commit 12fd8281da1cfee6e41f92056345c2f4cb806639

In GitLab by [Gitlab user @raoul].hidalgocharman on May 8, 2019, 15:23
mentioned in commit ffb81bd2d1612518dbd3e0a881a359203059f1f5

In GitLab by [Gitlab user @raoul].hidalgocharman on May 8, 2019, 15:28
mentioned in commit 7456f2a6956fa768ec0120e527f747a72fef15a3

In GitLab by [Gitlab user @raoul].hidalgocharman on May 9, 2019, 16:43
mentioned in commit f60dc8b16b8dc4916f4a96c917fa732d0323464f

In GitLab by [Gitlab user @raoul].hidalgocharman on May 9, 2019, 16:43
mentioned in commit 7bad9897038ec8b44be232a2033d1022a7af3b4b

In GitLab by [Gitlab user @raoul].hidalgocharman on May 9, 2019, 16:44
mentioned in commit be47bb5a431acc92d83a1ef94dbc6fda93d7ac96

In GitLab by [Gitlab user @raoul].hidalgocharman on May 9, 2019, 16:44
mentioned in commit 12e244d753587f0df82d529397e04a4146742d58

In GitLab by [Gitlab user @raoul].hidalgocharman on May 13, 2019, 13:56
mentioned in commit acd6c75bbd7def9c9a80d663313044d9ed6211c9

In GitLab by [Gitlab user @raoul].hidalgocharman on May 13, 2019, 13:56
mentioned in commit bd30f1b97bd76a7c38f6217d1bc7d660d155389d

In GitLab by [Gitlab user @raoul].hidalgocharman on May 14, 2019, 11:26
mentioned in commit 7ad87c75bdf7c1961189bc92f271fcaf4aa75019

In GitLab by [Gitlab user @raoul].hidalgocharman on May 14, 2019, 11:26
mentioned in commit 0c33a3e14b65754717f4bac9c160c198b2b72744

In GitLab by [Gitlab user @raoul].hidalgocharman on May 14, 2019, 14:05
mentioned in commit 36559be383f2148b103b0b5034dc9a231d93f0be

In GitLab by [Gitlab user @raoul].hidalgocharman on May 14, 2019, 14:05
mentioned in commit 995ff5ac2b357fb7da716eabc4b436b8e05d6f26

In GitLab by [Gitlab user @raoul].hidalgocharman on May 14, 2019, 15:08
closed via merge request !1319

In GitLab by [Gitlab user @raoul].hidalgocharman on May 14, 2019, 15:08
mentioned in commit 615c93b5e9c8ddc6734a13cc55b17f33b6c3182f


adding a new component

I would like to have two buttons next to each other in a form, say

<button class="btn btn-primary disabled" type="submit">Save</button>
<button class="btn btn-primary" type="button" style="margin-left: 10px;">Cancel</button>

How can I create this in the formbuilder? Do I have to create a "custom component"? It is not clear for me how to do this after reading section "Adding Components" at https://github.com/formio/ngFormBuilder.
Is this documented clearly for starters somewhere? At https://gitter.im/formio/formio I did not get reactions on the same question.

Hey @StefanHoutzager, sorry for the delay. It's been a strange holiday weekend.
You can add a Column layout component to your form, and put a button in a each column.

@StefanHoutzager, You can use the block setting to make each button take the entire width of the container and you can nest multiple columns if needed.
I think thats the best option for now, unless you want to make a custom layout component, or mess with custom css. It's possible you can use the html component to make a bootstrap row and put the buttons html as the content; however, I haven't tried that personally.

You created a great tool I must say! I succeeded in adding a component with these two buttons in ngFormBuilder-full.js. I have a small question though. How do I add the submit action? For the submit button that is already available I can see this in the json schema:
disableOnInvalid: true,
action: "submit"

What can I add to the following code?
},{}],162:[function(_dereq_,module,exports){
"use strict";

module.exports = function(app) {
  app.config([
    'formioComponentsProvider',
    function(formioComponentsProvider) {
      formioComponentsProvider.register('opslaanannuleer', {
        title: 'Opslaan Annuleer',
        template: 'formio/components/opslaanannuleer.html',
        group: 'advanced',
        settings: {}
      });
    }
  ]);
  app.run([
    '$templateCache',
    function($templateCache) {
      $templateCache.put('formio/components/opslaanannuleer.html',
        "
\n <button class=\"btn btn-primary disabled\" type=\"submit\">\n Submit \n  </button>\n <button class=\"btn btn-primary\" type=\"button\" style=\"margin-left: 10px;\">\n Cancel \n  </button>\n
\n"
      );
    }
  ]);
};

,

Hi, How can i add my custom element to Basic Components here http://prntscr.com/nru2j2
I read this example https://github.com/formio/ngFormBuilder but not understand his

@PetroSutch
You can create a new js file and create a new group if you want like bellow
app.config(['formioComponentsProvider', function (formioComponentsProvider) {

   formioComponentsProvider.addGroup('amazing', { title: 'Custom Template Components' });
formioComponentsProvider.register('name', {
       title: 'Your Title',
       template: 'formio/components/desiredURL.html',
       controller: ['$scope', function ($scope) {

       }],
       group: 'amazing',
       icon: '',
       settings: {
           input: true,
           fontSize: '',
           activeColor: '',
           multiple: false,
           protected: false,
           persistent: true,
           tableView: false
       },
       views: [
         {
             name: 'Display',
             template: 'formio/components/icons/yourURL.html'
         }
       ]
   });

if you don't wanna create new group ,you can give the group name 'basic' and ignore the .addgroup() line.


Color singularity with RGB ImVec4 casting

Hello!
I've found a little issue about ImVec4 <-> sf::Color conversion. It's not really a bug, but I think creating two new functions and/or adding a comment could be a good thing.
Using RGB colors as basis between ImVec4 and sf::Color breaks the ColorPicker when selecting the black color (at the bottom of the color selection square for the ImGuiColorEditFlags_PickerHueBar picker). When doing this, the hue resets itself to the red color. It isn't a bug in dear imgui, as it's known and commented in imgui_demo.cpp#1253.
So, I think it would be great to do something about it. Adding a comment explaining this behavior in imconfig-SFML.h, and adding two helper functions to do alternative conversions between ImVec4-encoded HSV color and sf::Color, using forward-declared ColorConvertHSVtoRGB() and ColorConvertRGBtoHSV() could do the trick.
If you think this is a good addition, I can do a pull request later this week.
And as always, thank you for this project!

Hello. Can you please provide reproducing example?
I've tried this code and everything  works correctly for me:
#include "imgui-SFML.h"
#include "imgui.h"

#include <SFML/Graphics/CircleShape.hpp>
#include <SFML/Graphics/RenderWindow.hpp>
#include <SFML/System/Clock.hpp>
#include <SFML/Window/Event.hpp>

int main() {
    sf::RenderWindow window(sf::VideoMode(640, 480), "ImGui + SFML = <3");
    window.setFramerateLimit(60);
    ImGui::SFML::Init(window);

    sf::CircleShape shape(100.f);
    ImVec4 color = ImVec4(1.0f,1.0f,1.0f,1.0f);

    shape.setFillColor(sf::Color::Green);

    sf::Clock deltaClock;
    while (window.isOpen()) {
        sf::Event event;
        while (window.pollEvent(event)) {
            ImGui::SFML::ProcessEvent(event);

            if (event.type == sf::Event::Closed) {
                window.close();
            }
        }

        ImGui::SFML::Update(window, deltaClock.restart());

        ImGui::Begin("Hello, world!");
        ImGui::Text("Color picker:");
        ImGui::ColorPicker4("MyColor##4", (float*)&color, ImGuiColorEditFlags_PickerHueBar);
        ImGui::End();

        shape.setFillColor(color);

        window.clear();
        window.draw(shape);
        ImGui::SFML::Render(window);
        window.display();
    }

    ImGui::SFML::Shutdown();

    return 0;
}

Oh, you're right, it's more complicated than I assumed.
The problem seems to be the round trip sf::Color -> ImVec4 -> sf::Color. Some data will always be lost doing this way I think. So it's more of an edge case I didn't took care of in my project than a issue in imgui-sfml. I'll let you decide if this is the case before closing the Github issue.
For the record, here's the code to reproduce this behavior:
#include "imgui-SFML.h"
#include "imgui.h"

#include <SFML/Graphics/CircleShape.hpp>
#include <SFML/Graphics/RenderWindow.hpp>
#include <SFML/System/Clock.hpp>
#include <SFML/Window/Event.hpp>

int main() {
    sf::RenderWindow window(sf::VideoMode(640, 480), "ImGui + SFML = <3");
    window.setFramerateLimit(60);
    ImGui::SFML::Init(window);

    sf::CircleShape shape(100.f);
    sf::Color sf_color = sf::Color::Green;             // <--
    ImVec4 im_color = ImVec4(1.0f, 1.0f, 1.0f, 1.0f);  // <--

    shape.setFillColor(sf_color);                      // <--

    sf::Clock deltaClock;
    while (window.isOpen()) {
        sf::Event event;
        while (window.pollEvent(event)) {
            ImGui::SFML::ProcessEvent(event);

            if (event.type == sf::Event::Closed) {
                window.close();
            }
        }

        ImGui::SFML::Update(window, deltaClock.restart());

        ImGui::Begin("Hello, world!");
        ImGui::Text("Color picker:");

        im_color = shape.getFillColor();              // <--
        ImGui::ColorPicker4("MyColor##4", (float*)&im_color, ImGuiColorEditFlags_PickerHueBar);
        ImGui::End();

        sf_color = im_color;                         // <--
        shape.setFillColor(sf_color);                // <--

        window.clear();
        window.draw(shape);
        ImGui::SFML::Render(window);
        window.display();
    }

    ImGui::SFML::Shutdown();

    return 0;
}

Yeah, that's mostly the problem of RGB/HSV being so different. SFML stores colors as RGB, so there's not much I can do about this. Implicitly converting sf::Color to ImVec4 which stores color as HSV is not trivial and requires some calculations, so I'm not sure that I want to do that.
The solution seems to be: use HSV encoded ImVec4 with ImGui and then cast it to sf::Color (RGB).

Yes, that's what I've done, the colors are now encoded in ImVec4 for the most part and only cast to sf::Color when there will not be any interaction with the user anymore.
Anyway, thank you for helping me with this and sorry for this false alarm. I'll close this issue.


Linux self-hosted - Container jobs - Pipelines build error

Hi,
I'm trying to run container jobs on self-hosted Linux agent but i have an error :
##[debug]Evaluating condition for step: 'Initialize containers'
##[debug]Evaluating: SucceededNode()
##[debug]Evaluating SucceededNode:
##[debug]=> True
##[debug]Result: True
##[section]Starting: Initialize containers
##[error]Nullable object must have a value.
##[debug]System.InvalidOperationException: Nullable object must have a value.
   at Agent.Sdk.PlatformUtil.get_RunningOnRHEL6()
   at Microsoft.VisualStudio.Services.Agent.Worker.ContainerOperationProvider.StartContainersAsync(IExecutionContext executionContext, Object data)
   at Microsoft.VisualStudio.Services.Agent.Worker.JobExtensionRunner.RunAsync()
   at Microsoft.VisualStudio.Services.Agent.Worker.StepsRunner.RunStepAsync(IStep step, CancellationToken jobCancellationToken)
##[section]Finishing: Initialize containers

Pipeline file
name: $(Build.BuildID)
jobs:
- job: One
  pool: Docker
  container: ubuntu:16.04
  steps:
  - task: Bash@3
    inputs:
      targetType: 'inline'
      script: 'hostname'

Current settings :
Agent Host : Centos 7
cat /etc/redhat-release
CentOS Linux release 7.7.1908 (Core)

Agent version : Linux x64 2.162.0
Azure DevOps Server (On premise)  : 2019.1
Possible fix
By analysing the code in https://github.com/microsoft/azure-pipelines-agent/blob/master/src/Agent.Sdk/Util/PlatformUtil.cs the function DetectRHEL6() do not set detectedRHEL6 to false if the file "/etc/redhat-release" do not contains "CentOS release 6." or "Red Hat Enterprise Linux Server release 6.". This is may be the cause of the problem.

I've just try to rename the file "/etc/redhat-release" to ""/etc/redhat-release.old" the job now start without error.
So my diagnostic seem to be good, the is a problem in the function DetectRHEL6().
Is it possible to fix it on the next release ?
Thanks a lot.
regards

@Fizcko - Thanks for the assist in triaging this issue. I have pushed a PR to fix it.

@jtpetty Thanks !


Async Implementation

Hello, just a quick info check, is there any "simple" way to make the library work with a tokio runtime asynchronously? TY

Ok, got you. Thank you for the example as well. Very helpful :)


nanopolish eventalign with --sample flag leads to core dumped

I am running nanopolish eventalign with dRNA :
nanopolish eventalign --reads ../fastq/sythetic.fastq --genome ../ligated_oligo.fa --bam ../alignment/minimap_filtered.bam --samples  > eventalign.txt terminate called without an active exception Aborted (core dumped)
But if I run it without the --samples flag it works fine
nanopolish eventalign --reads ../fastq/sythetic.fastq --genome ../ligated_oligo.fa --bam ../alignment/minimap_filtered.bam > eventalign.txt [post-run summary] total reads: 270, unparseable: 0, qc fail: 13, could not calibrate: 6, no alignment: 0, bad fast5: 0
I know there is a close issue about this but do not know what happened here.

Which version of nanopolish are you using?
Jared

I see, not the newest,  0.9.0. It is cause I installed like this:
$sudo apt-get install nanopolish Reading package lists... Done Building dependency tree        Reading state information... Done nanopolish is already the newest version (0.9.0-1). The following package was automatically installed and is no longer required:   libllvm7 Use 'sudo apt autoremove' to remove it. 0 to upgrade, 0 to newly install, 0 to remove and 129 not to upgrade.
It is working with the current version,
Thanks a lot,
Pablo


Fix Error.message usage

Some refactoring of __init__.py by:
-  cleaning up if
- reformatting
- removing e.message as this doesn't exist

Hi @Daggy1234
Thanks for contributing.
As your PR is accepted for the Hacktoberfest so can you please fill this form to become eligible for LoginRadius cool swags. :)
Thanks & Regards
Indrasen

HI @Daggy1234
Thanks for your contribution to this project, this particular request is included in our latest Release Version 11.4.0
Please let me know if you see any other areas of improvement.
Regards
Indrasen


[WIP] Coefficient Factory class for mini apps [coef-fact-dev]

This PR adds a class which reads a file (or any input stream) and allocates (and returns) Coefficient, VectorCoefficient, or MatrixCoefficient classes described in that file.  The current implementation recognizes most of the basic coefficient types appearing in coefficients.hpp and is extendable.  There is a small mini app which demonstrates its usage in miniapps/tools/coef-fact.cpp.
The goal of this object is to provide a way to allow an application user to easily specify, in an input file, various coefficients for boundary conditions, initial conditions, material coefficients, etc.. This scheme is not as flexible as converting user input into compilable code but I think it could be useful and much easier to implement.
At this point I'm mainly interested in feedback.  The file format attempts to closely follow the argument lists needed by the various coefficient constructors.  Examining a header file entry for a given coefficient should give you most of the information you need to figure out what data is needed in the file but clearly more documentation will be needed before making this public (unless we choose a different path).

Thanks for writing this PR @mlstowell! I like the idea and the conversation you've started. One cool thing about this idea is the possibility of enabling people who don't write much C++ (say they use ANSYS a lot) to tweak inputs to mfem-linked executables as part of running parameter studies or as part of doing design work. From the perspective of someone who uses mfem to do design work, this capability would be a big force multiplier for us, because it would be possible for our customers to do those sorts of design studies with minimal intervention from the design optimization team. It would free us up to do more feature development.
As currently executed, I agree that it would be possible, but difficult to use this file format for that purpose. As you've alluded to in the PR description, the numbers in the input file format look kind of magic to me, and I have to read the corresponding mfem classes and the source code to figure out what's going on. My customers wouldn't have that option, and I don't know that they'd look at public headers to understand what the inputs in the current input file format mean.
I think using a more semantically rich file format -- one that has tags and doesn't rely so much on positional inputs -- would make it easier for non-developers to understand what's going on, and for developers and non-developers alike to spot questionable or syntactically-invalid inputs.
For example, I could write an input file with the snippet:
##### snip #####
scalar_coef
DeltaCoefficient
2 3 4 5 6
##### snip #####

and not really know that the file parser is going to silently ignore the 6 in that input. Something that tagged those inputs with argument names would be really helpful. For example:
scalar-coefficients:
    - delta-coefficient:
          - name: "my-point-load" # maybe this name could be used to pass the coefficient in as a particular argument
          - dimension: 2
          - location: [3, 4, 5]    # oops! the dimension could also possibly be inferred from the location array
          - amplitude: 6

I don't think the input needs to be YAML-like -- I think lots of options are available that could add useful semantic information, and this semantic information makes it much easier for a non-developer to see what's going on.
I like the factory logic, too. I think refactoring CoefFactory into three abstract factories, one for each of the distinct coefficient class hierarchies (i.e., Coefficient, VectorCoefficient, MatrixCoefficient), and then having those abstract factories delegate to concrete factories would make the resulting design easier to test, debug, and extend.
re: the delegation logic inside your current factories, if you refactored them to the pattern above, I think the delegation logic inside the abstract factories could be simplified to creating a hash table keyed by the std::string name associated with concrete factories. (Similar sorts of constructions, like a factory function mapping keys to concrete factories, would also work.) The factory-specific logic would be in separate classes that could be tested independently. Delegating creation to concrete factories with hash tables would make it easier to change the keys corresponding to each factory if the input file format changes.
I'm curious to see how this effort evolves and hope something like it lands in MFEM eventually. Thanks again!


Additional Python files to exclude

Describe the bug
This is a followup to #259.
__pycache__ directories seem to be only excluded in the root and not recursively.
*.egg-info directories should also be excluded recursively
To Reproduce
Steps to reproduce the behavior:

Test and run coverage on a python project with tox
Use uploader
Look at file list

Expected behavior
__pycache__ and *.egg-info directories should be filtered out when files network is generated
Screenshots
example
Additional context
__pycache__ contains Python bytecode files
*.egg-info contains Python project metadata

We'll investigate this issue alongside our active work on #52 and #360. If there's an advantageous path to solving this as a result of those improvements, we will do so in the same batch of work.


Avoid not_to receive, not_to have_received etc.

# bad
foo.something
expect(foo).not_to have_received(:decrease_counter)

# good
foo.something
expect(foo.counter).to eq(1)
# or
expect { foo.something }.not_to change { foo.counter }

If you refactor and rename :decrease_counter to e.g. :decrease, the first spec would check nothing, but the second specs would still cover the relevant side effect.

Hmm, there are valid cases where you would want to ensure a particular message wasn't sent to a collaborator.
I would say the 'bad' in the first example example is that an expectation is being set on the SUT (i.e. it's testing an implementing detail).

Interesting. I actually have to think about this more. I was initially going to comment that I don't think I would ever write that test but apparently I have at least three times in the last year.
For example, I have some code which parses user input. If we parse it properly and it is invalid then we just return a user error. If we fail to even parse it entirely (can happen on rare occasions) then we notify our bug tracker. As a result, we have specs like this
context 'when invalid input given' do
  let(:input) { 'invalid but parseable' }

  it 'does not notify bugsnag' do
    allow(BugTracker).to receive(:notify)

    expect(handle_input).to be(false)

    expect(BugTracker).not_to have_received(:notify)
  end

  it_behaves_like 'a rejected request'
end

context 'when unparseable input given' do
  let(:input) { 'unparseable!' }

  it 'is invalid and notifies bugsnag' do
    allow(BugTracker).to receive(:notify)

    expect(handle_input).to be(false)

    expect(BugTracker).to have_received(:notify).with(SomeLib::ParseError)
  end

  it_behaves_like 'a rejected request'
end

This seems hard to avoid. We also have similar code for bootstrapping our application. For example, for test mode we expect Sidekiq::Testing to receive inline!. In dev mode and prod we assert it doesn't. I'm not sure how we would test these branches otherwise

There is a valid point here because it seems kind of similar to the expect { ... }.to raise_error problem in terms of potentially missing something, but OTOH the real problem is that it's doing an expect on something that it doesn't check for valid methods. You can have the same class of problem by doing expect(...).to have_received(...) as well though if your test calls a method you allow in rspec but doesn't exist.
In either case the problem is easily solved by using an instance_double (if you can insert a double). So, it seems like we might be punishing a few valid uses when the problem seems to me to be more of choosing to do an allow/expect on an unverifiable option.
@bquorning, @andyw8, @backus, any further thoughts? I think it'd be nice if we could agree on whether or not this makes sense and convert it into an (in?)action item.

In case of properly defined balancing cases, when there is another example that is checking that decrease_counter has been received, and with verifying doubles turned on, this doesn't seem to be a problem anymore.
It's not practical in common case to test side effects, as this might require more stubbing, slows specs down due to real method calls.
What's worst is it breaks boundaries of what we actually test, resulting in brittle tests when the implementation of receiver changes, and we're forced to update all consumer tests (expectations and stubs).

@pirj I follow some of what you're saying but I'm actually not clear on your conclusion--are you saying we don't need a cop for this and doing not_to have_received is ok or the opposite?

Yes, basically my point is that this cop is unnecessary.
I feel it's easier to explain with an example:
module Backend
  class << self
    attr_reader :state

    def long(state)
      sleep 2
      @state = state
    end
  end
end

class Notifier
  def initialize(use_shortcut: false)
    @use_shortcut = use_shortcut
  end

  def notify(state)
    if @use_shortcut
      "meh"
    else
      Backend.long(state)
    end
  end
end

# Isolated, balanced
RSpec.describe Notifier, 'isolated' do
  context 'without shortcut' do
    it 'receives a precious result' do
      expect(Backend).to receive(:long).with(1)
      Notifier.new.notify(1)
    end
  end

  context 'with shortcut' do
    it 'receives zilch' do
      expect(Backend).not_to receive(:long)
      Notifier.new(use_shortcut: true).notify(2)
    end
  end
end

# Non-isolated, balanced
RSpec.describe Notifier, 'breached' do
  context 'without shortcut' do
    it 'receives a precious result' do
      expect { Notifier.new.notify(3) }
        .to change { Backend.state }.to(3)
    end
  end

  context 'with shortcut' do
    it 'receives zilch' do
      expect { Notifier.new(use_shortcut: true).notify(4) }
        .not_to change { Backend.state }
    end
  end
end

$ rspec --profile=4 spec/a_spec.rb
...

Top 4 slowest examples (2.07 seconds, 99.5% of total time):
  Notifier breached without shortcut receives a precious result
    2.01 seconds ./spec/a_spec.rb:46
  Notifier isolated without shortcut receives a precious result
    0.0516 seconds ./spec/a_spec.rb:29
  Notifier breached with shortcut receives zilch
    0.01 seconds ./spec/a_spec.rb:53
  Notifier isolated with shortcut receives zilch
    0.00071 seconds ./spec/a_spec.rb:36

Non-isolated is slower (in this case insanely slower).
In both cases, we rely on Backend's interface (state or long), as in the original example with foo we rely either on decrease_counter or counter.
However, we have an agreement that Notifier is able to call long, while there's no guarantee that state is there to stay. In case the reader interface changes, the examples using change will have to be updated, indicating brittleness.
My eye is soaped though, pretty sure there are equally valid opposite arguments.
On a side note, it seems that the original bad example is also bad because it's stubbing the subject:
# bad
foo.something
expect(foo).not_to have_received(:decrease_counter)

PS Tried to use doubles in those examples, but encountered that case when a real object keeps the double for itself between the examples:
       #<InstanceDouble(String) (anonymous)> was originally created in one example but has leaked into another example and can no longer be used. rspec-mocks' doubles are designed to only last for one example, and you need to create a new one in each example you wish to use it for.

so resorted to use arbitrary numbers instead. There's a trick to reuse and reset mock proxy, but it's over the top for this spec.

Got it.
I'm in favor of just closing this--I don't think it has a clear enough benefit to merit a cop. @bquorning, do you have a dissenting opinion?

Closing as controversial.


document force_ip_resolve option

depend of https://github.com/M6Web/GuzzleHttpBundle/pull/48

closed see #48


[Question] - Display Plane

Hi there,
In my project I show a text that displays all information from a detected plane using the function onPlaneDetected of the ARKit component.
Is there a way to display the plane somehow?
Thanks in advance.
Cheers,
Tom

yes.
Store the plane in onDetectedPlane somewhere (redux or setState) and use a ARKit.Box or ARKit.Plane to display it. E.g.
<ARKit.Box
    position={position}
    shape={{
      width: 20,
      height: 0.001,
      length: 20,
    }}
  />

this does not take the extent of the plane into account, i used it to display the floor. But using extend should not be a problem.
Btw. once https://github.com/HippoAR/react-native-arkit/pull/71 is merged, you can use shaders to add gridlines or other programmed textures to planes. E.g. this shows gridlines where the colors shows whether the coordinates are positive or negative (x and z):
import { ARKit } from 'react-native-arkit'
import React from 'react'

export default ({ position }) => (
  <ARKit.Box
    position={position}
    material={{
      blendMode: ARKit.BlendMode.Screen,
      color: 'green',
      shaders: {
        [ARKit.ShaderModifierEntryPoint.Surface]: `
        float lineSize = 4;
        vec2 coord = 50*_surface.diffuseTexcoord.xy;
        vec2 grid = abs(fract(coord - 0.5) - 0.5) / fwidth(coord);
        float line = 1/lineSize*min(grid.x, grid.y);

        #pragma transparent

        vec4 posWorld = u_inverseViewTransform * vec4(_surface.position,1.0);
        bool xIsPos = posWorld.x >=0 ;
        bool zIsPos = posWorld.z >=0 ;
        vec4 pospos = vec4(1.0,0,0,1.0);
        vec4 posmin = vec4(1.0,1.0,0,1.0);
        vec4 minpos = vec4(0,0,1.0,1.0);
        vec4 minmin = vec4(0,1.0,0,1.0);
        if(xIsPos && zIsPos) {
            _surface.diffuse = pospos;
        } else if(xIsPos && !zIsPos) {
            _surface.diffuse = posmin;
        } else if(zIsPos) {
            _surface.diffuse = minpos;
        } else {
            _surface.diffuse = minmin;
        }

        _surface.transparent = vec4(vec3(1.0), 1.0 - min(line, 1.0));

        `,
      },
    }}
    shape={{
      width: 20,
      height: 0.001,
      length: 20,
    }}
  />
)

That is very cool.
Thanks for the quick reply.
What would be the time frame for #71 to be merged?

@dittmarconsulting i don't have merge rights yet, but i released a fork for the moment:
<EMAIL_ADDRESS>can you check if it works with that? If you install that one, you might need to readd your library project, because the path is a bit different.

Hi @macrozone ,
I get the plane but it seems the displayed, flat 'ARKit.Box' is vertically positioned to the detected plan. Am I correct?

@dittmarconsulting should not be the case 🤔
the box is placed at position, which is the anchor of the detected plane.
Using an actual AR.Plane would be more correct though.

@dittmarconsulting still an issue or can i close this issue?


test Documentation with subclass with #:nodoc:

Will rebase when #1808 lands for a green baseline.

Guess now you can rebase.

rebased

:+1:


Terminal has strange grey bar over scrollbar

On both macOS and Linux.

This was @bpasero vendor prefix cleanse, fixed it already.


README: img.badgesize.io badges are not rendered

Description
In our README, there is a rendering issue with some badges present in the Status section.

These badges are all using https://img.badgesize.io where there is an open issue apparently linked to an expired registry: https://github.com/ngryman/badge-size/issues/113
Several options:

Let these badges as they are now, and wait for an upstream fix
Switch to another badge provider
Drop these badges, and re-include them when the upstream issue is fixed

I tried to fix it statically by brute-forcing it. I simply created another badge with the same link, but I couldn't understand the badge design. I'm unable to match the design of the badge.
Could you please provide the badge design model or style query for it?
Here's what I have tried to build

Please do assign me for this issue

It's back to normal thanks to https://github.com/ngryman/badge-size/issues/113#issuecomment-2126523910. I'll reopen this issue if the issue comes back.


Quintessence

Added Quintessence and Quintessence Points.

Assuming this round of releases (and bug fixes) will settle down, and I can integrate this this week.

Just a note, I've haven't updated my pull request to fix any issues that may have arisen as a result of the recent Foundry updates. One thing of note is that the text in the System Settings option no longer displays correctly, it looks like placeholder text. Also, the way I added it only works per client not as a GM option for everyone.

added the following to line 1091 of /lang/en.json to address labelling issue:
"GURPS.settingUseQuintessence": "Use Quintessence",
"GURPS.settingHintUseQuintessence": "If enabled, adds the Quintessence (QN) attribute and allows the use of QP as a resource tracker. Imports these values from GCS if available.",

FYI - As of 0.13.13 after I added my changes back, as I have done previously, I'm getting an error.
Looking into it but it's something about an "unregistered setting" but is coming from the actor.js file and a function that's checking the actor move attribute.

 Works fine with 0.13.13.
As you were.

Sorry it took SOOO long... I've merge in the code and preparing a release.

No worries, my friend.I understand it’s a low priority item in a very long list.I appreciate that you guys considered adding it at all.Though, I was amused that at least one other person wanted this feature. LOL
Sent from Yahoo Mail for iPhone
On Monday, April 11, 2022, 12:59 PM, Chris Normand @.***> wrote:
Sorry it took SOOO long... I've merge in the code and preparing a release.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: @.***>