Standarize Readme and add License

See https://github.com/ipfs/community/issues/124

Made a comment, LGTM otherwise :)

Removed License. @whyrusleeping Can you tell me what License you want on this?

@whyrusleeping Thoughts?

LGTM

Who would be in charge of the license?

MIT

Added. Needs final review.

This closes #4.


HHH-12867 Lazy loaded OneToMany gets initialized on refresh

https://hibernate.atlassian.net/browse/HHH-12867

This is just a test case as I couldn't come up with a fix without triggering other test failures.

Being this an accepted misbehavior, shouldn't the other failing test cases be fixed to be adapted to the new (and correct) behavior?

Sure. I think there's something wrong but unfortunately I'm not fully understanding what's going on with those failing tests, that's why I haven't pushed a fix for now.

Thanks @gsmet for the test case, I added a @FailureExpected annotation and merged it into main.


:recycle: (gocardless) renamed nordigen_* secrets to gocardless_*

Final change for: https://github.com/actualbudget/actual/issues/1244

@MatissJanis is there a matching MR for updating the secret-set in desktop-client? It's still pointing at nordigen there. Currently with this change you can no longer init gocardless fresh.
Might be easiest to leave both sets of constants here in  SecretName, both pointing to the new names. Then following up with a final MR to remove the extra constants after the update in desktop-client is released.

Good catch @twk3 !
We can update both of these variables in-sync. Here's the web PR: https://github.com/actualbudget/actual/pull/2181


Incorrect interval length calculation

I'm pretty sure this requires the following change to correctly calculate the interval length:
https://github.com/specklesystems/speckle-sharp/blob/a7c779049a437605033583252bc40dd17be07c62/Objects/Objects/Primitive/Interval.cs#L27
[JsonIgnore] public double Length => Math.Abs((end ?? 0) - (start ?? 0));

Thanks for spotting @timglewis ! We'll review and get back to you soon :)

🤕 True! Just making the fix now :) Thanks for bringing this up!

Just merged this in! Should be fixed in our next upcoming release 👍🏻
Thanks again!


sublime-merge-dev: 2095 -> 2099

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for sublime-merge-dev is: Git client from the makers of Sublime Text
meta.homepage for sublime-merge-dev is: https://www.sublimemerge.com
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 2099 with grep in /nix/store/wh0gi25vk7iq9jinnr52rys4xsgcks2n-sublime-merge-2099
found 2099 in filename of file in /nix/store/wh0gi25vk7iq9jinnr52rys4xsgcks2n-sublime-merge-2099

Rebuild report (if merged into master) (click to expand)

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath

sublime-merge-dev

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/wh0gi25vk7iq9jinnr52rys4xsgcks2n-sublime-merge-2099 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A sublime-merge-dev https://github.com/r-ryantm/nixpkgs/archive/ba654492e57f31043e49a4b60cbdc1231540bee1.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/ba654492e57f31043e49a4b60cbdc1231540bee1#sublime-merge-dev

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/wh0gi25vk7iq9jinnr52rys4xsgcks2n-sublime-merge-2099
ls -la /nix/store/wh0gi25vk7iq9jinnr52rys4xsgcks2n-sublime-merge-2099/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

sublime-merge-dev

Maintainer pings
cc @zookatron for testing.

Add a :+1: reaction to pull requests you find important.

👍


Pass Google Font path as the URL from Google Fonts

Hey, it would be great if you could pass a link like this:
https://fonts.googleapis.com/css2?family=Poppins
to astro-font. Basically I can't see a way to get the Google hosted woff file. But they give you this URL to access your selected fonts, so that would be super easy!

@jdtjenkins
If you open the URL (https://fonts.googleapis.com/css2?family=Poppins) itself will have the links to the woff/ttf files directly.
But yeah, I am aware that https://github.com/dc7290/astro-fonts-next exists and it fetches it for you. I'd love your thoughts on the DX you'd expect?

Copying from slack because here might be easier to carry this on!
Huh! 🤦♀ I never though to actually click that link. When I loaded it up on a site I was checking the network for woff files and was just coming up with garbage!
Yeah ok that makes it easier! I guess it would be great if it astro-font could do that bit for you. Or even you select all the families and weights you want in the fonts.google.com ui and then just copy the link it gives you and it would automatically import them all for you.
That's probably quite a bit more work 😂 But that would be sick tho

let match;
const fontFaceRegex = /@font-face\s*{([^}]+)}/g;
const fontFaceMatches = [];
while ((match = fontFaceRegex.exec(tmp)) !== null) {
  const fontFaceObject = {};
  const fontFaceRule = match[1];
  fontFaceRule.split(';').forEach(property => {
      if (property.includes('src: ')){
          fontFaceObject['path'] = property.substring(12, property.indexOf('for')-2).trim();
      }
      if (property.includes('-style: ')){
          fontFaceObject['style'] = (property.split(':').map(i => i.trim()))[1]
      }
      if (property.includes('-weight: ')){
          fontFaceObject['weight'] = (property.split(':').map(i => i.trim()))[1]
      }
      if (property.includes('unicode-range: ')){
          if (!fontFaceObject['css']) { fontFaceObject['css'] = {} }
          fontFaceObject['css']['unicode-range'] = (property.split(':').map(i => i.trim()))[1]
      }
  });
  fontFaceMatches.push(fontFaceObject);
}

Executing this on that link will give you the object that can be placed instead of the src array. Let me try and get that pushed into the next release.

Here's how you can do it:
https://github.com/rishi-raj-jain/astro-font?tab=readme-ov-file#use-google-fonts-url-directly
Make sure to use each font-name with it's own URL ^^


Remove version: CrystalDewWorld.CrystalDiskInfo.ShizukuEdition version 8.12.8

[Automated] It returns code over 400 in all urls
Microsoft Reviewers: Open in CodeFlow

URL: https://osdn.net/frs/redir.php?m=ipconnect&f=crystaldiskinfo%2F76087%2FCrystalDiskInfo8_12_8Shizuku.exe
Response Error: The underlying connection was closed: Could not establish trust relationship for the SSL/TLS secure channel.
(Automated message - build 923)


You should write that Aria2 is a requirment to be installed in the sharepoint tree's README

As title.

Good point. Added. Thanks!


Building on Clear Linux fails with add user error

The following error makes it unusable:
adduser: The UID 0 is already in use.
exit status 1

Any help on getting your program to work?

It seems you are running the program as root.
Right now fyne-cross does the assumption that it is executed as non-root user.
Could please try with a different user ?

Fixed into the develop branch via e5a1921

I just tested the change and I can confirm that it fixes my use case. Thanks for the solid support and this absolutely great software for compiling for more os/cpu targets. Highly appreciated 👍
The reason that this had to be done was due to the fact that Clear Linux has some kind of security feature that forces you to use sudo to be able to use docker...


fix: Skip wrapping CJS modules which result in invalid identifiers

Closes #94
Rather than trying to find a way to only export invalid identifiers in versions of Node that support exports with names like this, this PR simply skips wrapping these modules. Since modules that use exports like this are rare, it's unlikely anyone will ever want to Hook them and if they do we can revisit this later.
@babel/helper-validator-identifier was chosen to check for invalid identifiers because the code looks good, it sees 50m+ downloads per week, it's tested, it has no dependencies and maybe most importantly, it's CommonJs!

If such modules are rare, how did the issue get exposed?

When testing the top 250+ npm packages I found webidl-conversions caused invalid wrappers to be emitted
This issue suggests wasm can result in invalid identifiers?
This open PR suggests at some point there was an issue with node-machine-id
Someone reported this issue in the Sentry repository for grpc-tools

If these are the only examples we have, it suggests it's quite uncommon but its prevalent enough for it to cause issues for users.

Thank you.

👋 Is the blocker on this PR still waiting for reviews from specific folks? Anything that can be done to move that along? Happy to help where I can. This change is still required to fix a bug in Sentry that is blocking us, as I understand it.

FWIW, it looks like this:
% cat test/hook/invalid-identifier.mjs
import * as lib from '../fixtures/invalid-identifier.js'
import { strictEqual } from 'assert'

strictEqual(typeof lib['one.two'], 'function')

% cat test/hook/invalid-identifier.mjs
import * as lib from '../fixtures/invalid-identifier.js'
import { strictEqual } from 'assert'

strictEqual(typeof lib['one.two'], 'function')

% cat test/fixtures/invalid-identifier.js
exports['one.two'] = () => console.log('b')

% cat my-setup-hook.mjs
import { register } from 'module'
import { Hook } from './index.js'

register('./hook.mjs', import.meta.url)
Hook((exports, name) => {
  console.log('my-setup-hook: hooking "%s"', name)
})

% node --import ./my-setup-hook.mjs test/hook/invalid-identifier.mjs
(node:33546) Error: 'import-in-the-middle' failed to wrap 'file:///Users/trentm/tm/import-in-the-middle2/test/fixtures/invalid-identifier.js'
(Use `node --trace-warnings ...` to show where the warning was created)
my-setup-hook: hooking "assert"
my-setup-hook: hooking "/Users/trentm/tm/import-in-the-middle2/test/hook/invalid-identifier.mjs"

With --trace-warnings:
% node --trace-warnings --import ./my-setup-hook.mjs test/hook/invalid-identifier.mjs
(node:33566) Warning: Error: 'import-in-the-middle' failed to wrap 'file:///Users/trentm/tm/import-in-the-middle2/test/fixtures/invalid-identifier.js'
    at load (/Users/trentm/tm/import-in-the-middle2/hook.js:431:21)
    at async nextLoad (node:internal/modules/esm/hooks:866:22)
    at async Hooks.load (node:internal/modules/esm/hooks:449:20)
    at async MessagePort.handleMessage (node:internal/modules/esm/worker:196:18) {
  cause: Error: 'one.two' export is not a valid identifier name
      at addSetter (/Users/trentm/tm/import-in-the-middle2/hook.js:205:13)
      at processModule (/Users/trentm/tm/import-in-the-middle2/hook.js:260:7)
      at async load (/Users/trentm/tm/import-in-the-middle2/hook.js:394:25)
      at async nextLoad (node:internal/modules/esm/hooks:866:22)
      at async Hooks.load (node:internal/modules/esm/hooks:449:20)
      at async MessagePort.handleMessage (node:internal/modules/esm/worker:196:18)
}
    at emitWarning (/Users/trentm/tm/import-in-the-middle2/hook.js:183:11)
    at load (/Users/trentm/tm/import-in-the-middle2/hook.js:433:9)
    at async nextLoad (node:internal/modules/esm/hooks:866:22)
    at async Hooks.load (node:internal/modules/esm/hooks:449:20)
    at async MessagePort.handleMessage (node:internal/modules/esm/worker:196:18)
my-setup-hook: hooking "assert"
my-setup-hook: hooking "/Users/trentm/tm/import-in-the-middle2/test/hook/invalid-identifier.mjs"

If I know about the excludes option (I don't recall if this is still considered experimental, hence why not documented) and with some trial and error, I can tweak my-setup-hook.mjs to skip that problematic module to avoid having warnings in my face all the time:
...
register('./hook.mjs', import.meta.url, {
  data: {
    exclude: [/fixtures\/invalid-identifier.js$/]
  }
})

Then, no more warning:
% node --trace-warnings --import ./my-setup-hook.mjs test/hook/invalid-identifier.mjs
my-setup-hook: hooking "assert"
my-setup-hook: hooking "/Users/trentm/tm/import-in-the-middle2/test/hook/invalid-identifier.mjs"

This doesn't need to block this PR, but my guess is this kind of message:
(node:33546) Error: 'import-in-the-middle' failed to wrap 'file:///Users/trentm/tm/import-in-the-middle2/test/fixtures/invalid-identifier.js'
(Use `node --trace-warnings ...` to show where the warning was created)

being seen by end users will result in support issues for us. :)
That might be alleviated somewhat by getting that closer to something like (taking away the words "Error" and "failed"):
(node:33546) Warning: 'import-in-the-middle' could not wrap 'file:///Users/trentm/tm/import-in-the-middle2/test/fixtures/invalid-identifier.js'
(Use `node --trace-warnings ...` to show where the warning was created)

That might be alleviated somewhat by getting that closer to something like (taking away the words "Error" and "failed"):

That would be possible with this diff:
diff --git a/hook.js b/hook.js
index b5d72f5..93664b8 100644
--- a/hook.js
+++ b/hook.js
@@ -428,7 +428,8 @@ register(${JSON.stringify(realUrl)}, _, set, ${JSON.stringify(specifiers.get(rea
         //
         // We log the error because there might be bugs in iitm and without this
         // it would be very tricky to debug
-        const err = new Error(`'import-in-the-middle' failed to wrap '${realUrl}'`)
+        const err = new Error(`'import-in-the-middle' could not wrap '${realUrl}'`)
+        err.name = 'Warning'
         err.cause = cause
         emitWarning(err)


fix(json-schema): handle nullable required props as nullable fields in GraphQL

Closes https://github.com/ardatan/graphql-mesh/pull/6561
Fixes #6560

Thanks for the quick response and fix! Seem so far good to me! 🌟
We'll check this out tomorrow via the alpha build in our main project with our more complex use-case as well.

Works great for our use-cases with the alpha builds! Tanks so much for this quick response and fix! 🙏 🌟


Fixes - Invalid memory access

These two modules were writing in read only memory

Hmmm... So content returned by sol_flow_get_node_type was read only? Does this PR fix all uses? Is this information, about content returned by sol_flow_get_node_type being read only documented?

The first commit looks ok

@edersondisouza i found only these two wrong usages. I'll check the documentation and fix if necessary.

fixes on https://github.com/solettaproject/soletta/pull/1681


Deprecate AccountStore API

We need to mark all AccountStore API's as obsolete.
The message should contain a recommendation to use Xamarin.Essentials' SecureStorage API's instead.

[x] Create a Wiki page on how to migrate from AccountStore to SecureStorage
[ ] Mark AccountStore API's with [Obsolete("Some message about using Essentials and an aka.ms link to Migration wiki page")]
[ ] Update any samples to use Xamarin.Essentials

VS bug #738757

Added a migration guide: https://aka.ms/xamarin-auth-accountstore-migration-guide and updated the repo's README to reference it.


Fix crash when do three finger gesture

Description

The issue(69431) description very clear how reproduce.
Three finger gesture + Redmi device(not only);
When problem happen, it will make app unusable unless restart.

crash stack:
2020-12-16 10:39:34.509 11957-12095/com.xx.yy I/flutter: RuntimeException: exception=Null check operator used on a null value
2020-12-16 10:39:34.510 11957-12095/com.xx.yy I/flutter: RuntimeException: stackTrace=#0      _AndroidMotionEventConverter.toAndroidMotionEvent. (package:flutter/src/services/platform_views.dart:602:73)
#1      MappedListIterable.elementAt (dart:_internal/iterable.dart:417:31)
#2      ListIterator.moveNext (dart:_internal/iterable.dart:343:26)
#3      new List.from (dart:core-patch/array_patch.dart:38:29)
#4      new List.of (dart:core-patch/array_patch.dart:68:17)
#5      ListIterable.toList (dart:_internal/iterable.dart:211:44)
#6      _AndroidMotionEventConverter.toAndroidMotionEvent (package:flutter/src/services/platform_views.dart:603:12)
#7      AndroidViewController.dispatchPointerEvent (package:flutter/src/services/platform_views.dart:867:31)
#8      _PlatformViewGestureRecognizer.handleEvent (package:flutter/src/rendering/platform_view.dart:535:26)
#9      PointerRouter._dispatch (package:flutter/src/gestures/pointer_router.dart:77:12)
#10     PointerRouter._dispatchEventToRoutes. (package:flutter/src/gestures/pointer

Related Issues
Fixes https://github.com/flutter/flutter/issues/69431
Tests
I added the following tests:

With my app, the crash no long happen.
The return null solution will go next to handlePointerCancelEvent function, these will clear pointers variables.
And next time whatever one finger or two finger or more fingers, the pointer will dispatch normally to app view(PlatformView);
Three finger gesture usually is for screen snapshot, it also works normally.

Checklist
Before you create this PR, confirm that it meets all requirements listed below by checking the relevant checkboxes ([x]). This will ensure a smooth and quick review process.

[x] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[x] I signed the CLA.
[x] I read and followed the Flutter Style Guide, including Features we expect every widget to implement.
[x] I read the Tree Hygiene wiki page, which explains my responsibilities.
[] I updated/added relevant documentation (doc comments with ///).
[x] All existing and new tests are passing.
[x] The analyzer (flutter analyze --flutter-repo) does not report any problems on my PR.
[x] I am willing to follow-up on review comments in a timely manner.

About comment, sorry, not '///' style, because  just keep the same style with nearby code.
Breaking Change
Did any tests fail when you ran them? Please read Handling breaking changes.

[x] No, no existing tests failed, so this is not a breaking change.
[x] Yes, this is a breaking change. If not, delete the remainder of this section.

[x] I wrote a design doc: https://flutter.dev/go/template Replace this with a link to your design doc's short link
[x] I got input from the developer relations team, specifically from: Replace with the names of who gave advice
[x] I wrote a migration guide: https://flutter.dev/go/breaking-changes-template Replace this with a link to a pull request that adds the migration guide to https://flutter.dev/docs/release/breaking-changes

I can also confirm, that this fixes the mentioned issue with google_maps_flutter and therefore closes #69431

I can also confirm, that this fixes the mentioned issue with google_maps_flutter and therefore closes #69431

I encounter a simillar issue on Xiaomi phone's three finger feature, but not 'map';

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).
📝 Please visit https://cla.developers.google.com/ to sign.
Once you've signed (or fixed any issues), please reply here with @googlebot I signed it! and we'll verify it.
What to do if you already signed the CLA
Individual signers

It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data and verify that your email is set on your git commits.

Corporate signers

Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data and verify that your email is set on your git commits.
The email used to register you as an authorized contributor must also be attached to your GitHub account.

ℹ Googlers: Go here for more info.

@googlebot I signed it!

@googlebot I fixed it.

@googlebot I fixed it.

@googlebot I fixed it.

What should I do to do next? I want to view the 'flutter-build', but fail to filter out errors.

It builds success  on local 'flutter build ios/apk/web', @flutterbuildbot

This PR is missing tests, can you add some to ensure that this never breaks again?
/cc @iskakaushik

This PR is missing tests, can you add some to ensure that this never breaks again?
/cc @iskakaushik

This pr fixed my issue! 👍

This pr fixed my issue! 👍

@Water-bamboo Do you have plans to come back to this PR and add a test? Thanks.

@Water-bamboo Do you have plans to come back to this PR and add a test? Thanks.
Looking good, please add a test.

Ok, will do that.

After run: flutter analyze --flutter-repo
Analyzing 3 directories...
No issues found! (ran in 107.8s)

@goderbauer @iskakaushik As the modification is in service/platform_views, I have passed the test coverage there.

@goderbauer Did the "add a test" mean 'flutter test'?
Here it's the result,  and finally show "All test passed".

...

@goderbauer In order for us to merge this you'll have to add a new test that passes now, but would be failing if your change ever gets reverted.

@Water-bamboo In order for us to merge this you'll have to add a new test that passes now, but would be failing if your change ever gets reverted.

@goderbauer Sorry, how to add a new test? Write a new test case or do pull code and do 'flutter test' again?
Another solution, would you commit the fix by your way, my modification just prevent Array Overflow, and the 'flutter-build' was green once.

Yes, you will have to write a new test case.

Hi @Water-bamboo, this has not been updated in a while, and is not in a state for code review, so I am going to close it for now. If you would like to come back and continue working on it, feel free to re-open! thanks!

Hi @Water-bamboo, this has not been updated in a while, and is not in a state for code review, so I am going to close it for now. If you would like to come back and continue working on it, feel free to re-open! thanks!

Please reopen it, we really need it to be merged into Flutter to fix this problem: tobrun/flutter-mapbox-gl#578

@idootop Follow up this PR: https://github.com/flutter/flutter/pull/78874

@idootop Follow up this PR: #78874
Please note that there is not really a solution yet. We need to pinpoint the problem down to its core and not only apply workarounds

Ok, thanks.


[3.x] Improve documentation of rand_range

The description of rand_range did not mention whether to is included in the range.
This PR make the description like how it's described in RandomNumberGenerator and on master.

Thanks!

Cherry-picked for 3.4.5.


Github action for new Release

Create a github action for new releases (tagged in git) to create the docker image, push it to docker hub, and create the release package to add in the release section
maybe also publish to npm??

docker already implemented
working on npm


Adding instructions to deploy OCS on 3.x environments

AgnosticD 3.x environments support installing GlusterFS. need instructions to help selectively deploy it with 3.x/ deployment.

Closing as fixed


Docs recipe page lists 'recipe/sentry.php'; but not in current release

Currently the documentation lists sentry as a recipe but it is not in the repository are there plans to take it from the Archived Recipe Repository and bring it forward to the current one?  Or is there an easy way to make use of it?

Yes, there are plans to combine recipes with docs.

So I was able to use it by just making a folder next to my deploy script called recipe and put in the file from the archived repo

I am cleaning up on issues. Fill free to reopen if needed.
Also, we have a new section available: discussions.


Fix static img path

Description of change
I fixed the static img problem by adding a static img path. Sadly this was not detected by the test action as the branch was created before that action was added 😅 .
Edit: Also fixed the branch name. It still used dev instead of dev-refactor
Type of change

[ ] Bug fix (a non-breaking change which fixes an issue)
[ ] Enhancement (a non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[x] Documentation Fix

How the change has been tested
I actually tried to provoke a build fail with the new build system and although the errors get thrown, the build doesn't fail.
I need to have a second look at that. But in the meantime the PR is fine 👍
Change checklist

[x] I have followed the contribution guidelines for this project
[ ] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes

@felsweg-iota I fixed a bug in the cli which basically made our test action basically useless 😅
I will update the cli in this PR once my change on the cli got approved tomorrow if you don't mind.
(Luckily I tried to create a failing commit here and discovered the bug :trollface: )


Get-AeriesSection errors on line 39 ("Input string was not in a correct format.")

When I issue Get-AeriesSection -SchoolCode 6 -Section 140, I get the following error:
Cannot convert value "/140" to type "System.Int32". Error: "Input string was not in a correct format."
At C:\Users\redacted\Documents\WindowsPowerShell\Modules\AeriesApi\1.0.0\Public\Get-AeriesSection.ps1:39 char:13
+             $Endpoint =+ "/$SectionNumber"
+             ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : InvalidArgument: (:) [], RuntimeException
    + FullyQualifiedErrorId : InvalidCastFromStringToInteger

I suspect that the =+ shown there is supposed to be +=. When I make that change in my local copy of the module, everything works as expected.

This happens on PowerShell version 5.1.19041.1682. It doesn't happen on PowerShell 7.2.6 so I guess =+ exists there.

Hi @busdrw! Thanks for submitting this issue along with the fix! I am confirming that I have replicated the issue, and I will be submitting a PR soon to address it.


Hyphen in Resource Name

When creating the resource in the Azure Portal a hyphen (-) passes validation in the resource name and the resource is successfully created.
When publishing to the resource using the hub name containing the hyphen the following error is received:
Unhandled exception. Azure.RequestFailedException: Service request failed.
Status: 400 (Bad Request)
Content:
aracters can be letters, digits or the following symbols _`,.[]
Headers:
Server: nginx
Date: Wed, 04 Aug 2021 09:41:41 GMT
Transfer-Encoding: chunked
Connection: keep-alive
Content-Type: text/plain; charset=utf-8

resource names are allowed to contain hyphen (-) but the hub name does not, hub name should only contain alpha-numeric (0-9, a-z, A-Z) characters or underscore (_)
You don't need hub name to be the same as the resource name.

I was highlighting a discrepancy between what can be provisioned in Azure, and what the Azure.Messaging.WebPubSub package supports.

Get it. Since they are used in different places they follow different rules. For example, the resource name will be used as part of the domain name of the resource. And for Hubs, we try to prevent the characters that are not allowed in C# class naming so that in the future it gives us the flexibility to provide more powerful server SDKs, for example, mapping classes into Hubs.


can't load eslint localy

hi,i have eslint installed locally in my project 'Meteor' i got this message: Failed to load eslint library. Please install eslint in your workspace folder using 'npm install eslint' or globally using 'npm install -g eslint' and then pre...
i want vscode detect the local version eslint.thanks

It should. However the current available version only detects a local install version if it is installed in the workspace folder opened in VS Code. It will not detect it in parent folders.
This will change with the next update of VS Code. Besides looking up the parent chain the extension will also provide a nodePath setting if the eslint library is installed at an unusual location.


flyway rollback to any previous version

Can anyone please tell me flyway gives the facilities to rollback at any point of time/version once it migrated successfully.

Duplicate of #109


Support for MX Records

It would be nice to have support for MX Records in landrush.
Something like config.landrush.mx 'mail', which will add mail.$hostname.$landrush_tld as MX Record for $hostname.$landrush_tld

+1. Need this feature to set up mail server in vagrant.

+1 This is as far as I got looking for such solution. Pity it's not there :(


nvml.py error caused by modin's dask client (Latest modin version as of 3/3/2023)

My program works fine without changes on my primary workstation (Python version 3.9 - Modin Version 0.15.3). I set up a new environment using conda command line statements on another workstation, specifically targetting only CPU packages for my entire build and the latest modin package (conda-forge channel) is causing error messages from nvml.py to form.
It's requesting a GPU and when it doesn't find one, it's throwing a mountain of error messages. Some of this may be that I'm not properly closing out my workers, but I get these messages throughout the rest of my program once modin has finished loading files.

@sabrsulab thank you for reporting this issue. I would really like to help, but I don't know anything about nvml.py, and it's hard to tell what's going wrong here. Could you please provide a stack trace or any of the errors modin is raising? Also, could you give more specific details about the workstation where you are trying to start modin (e.g. operating system, python version, nvml version, modin version)? Could you give a list of the exact steps you took so other people can reproduce the failure?
@modin-project/modin-core	@modin-project/modin-contributors is anything here familiar to anyone?


[REQUEST] Drill offset on modular drill

Description:
When mining horizontally, with a range enhanced modular drill, offset the center of the block breaking area upwards to avoid mining the floor in front you.
Reason:
Mining with a max range modular drill is currently very difficult as you end up breaking the blocks below you.

This is currently not supported by Magna (which handles the animation, outlines and mining for AOE tools). I'll look into this again in the future. Thanks for the suggestion!

yeah I'm a complete idiot, I just wrote a book to read because I didn't check here before


fix: i18n strings not updating

Describe the changes you have made in this PR
Fixed bug in #964. Added an "onLanguageChange" listener for strings that were declared outside React component. I had to abstract these into functions so they could be called again when the listener detected a change (otherwise the strings passed to the component would never change on an update).
Here is where I found the solution, which is from the creator of Reacti18next.
Link this PR to an issue
#964
Type of change (Remove other not matching type)

fix: Bug fix (non-breaking change which fixes an issue)

Screenshots of the changes (If any)
How has this been tested?
Visual testing to ensure strings are translating properly.
Also ran E2E and unit tests.
2 E2E failed due to timeout issues, although I don't think these are due to my changes.

[X] My code follows the style guidelines of this project and performed a self-review of my own code
[ ] New and existing tests pass locally with my changes
[X] I checked if I need to make corresponding changes to the documentation (and made those changes if needed)

Checked it out and tried. Looks good.

2 E2E failed due to timeout issues, although I don't think these are due to my changes.

They can be flakey. If they are passing in CI it's all good.

can you fix the conflicts?
and a check from @dylancom would be good.

@bumi Merge conflicts fixed!
@dylancom this should be ready to check now

utACK
I'll do a full detailed test in master.
great work on all this!


feat: Add stdout/stderr Fd class

stdout/stderr should provide proper rights and filetype because wasi-libc still respects them in fcntl.

I intentionally didn't add stdin and stdout types because there is no stdin/stdout in the browser, so one way or another the user of browser_wasi_shim will have to make their own class to read/write from their own location. For example the rustc.html example uses a class that interacts with a terminal emulated by xterm.js.

Okay, sounds reasonable to me. Then can we export wasi_defs.js from this package to allow users to implement Fd interfaces using some classes in the module (e.g. Filestat, Fdstat)?

Yeah, exposing those types should be fine.


Feedback slider component.

Issue Type:

[x] Feature Request

Describe the bug

**

Possible solution

Hey, project admin I'm a GSSOC participant and I want to add a feedback slider component created with HTML CSS and JavaScript to the current repository. as you have seen on many websites nowadays it can be client feedback or any feedback I'm adding the preview below for more detail

Screenshots

If applicable, add screenshots to help explain your problem.

@VidhiBhatt01 please assign me this issue to work on.


Loss function

Hi, I have a question about implementing the loss function. According to the formula on the paper, the code here doesn't seem correct with some missing terms. Additionally, since it's called "normalized" cross-correlation, the loss value should be between 0 and -1, however, sometimes I would get a value like -1.xxx.
Could you kindly explain why is the implementation of the code and the formula? Thanks a lot in advanced!
cross = torch.clamp(IJ_sum - I_sum*J_sum/self.window_volume, min = self.num_stab_const)
I_var = torch.clamp(I2_sum - I_sum**2/self.window_volume, min = self.num_stab_const)
J_var = torch.clamp(J2_sum - J_sum**2/self.window_volume, min = self.num_stab_const)

The NCC loss equation in paper is

The NCC loos in code is

I did not see the mismatch
Besides, the NCC is in the range of -1, 1, and the higher means more similar. So the negative is used in loss. The value of -1.xxx you mentioned should be the total loss, not just similarity loss?

I copied the entire code but added the permutation lines because my inputs are in shape (1, n, d, h, w)

I get -1.xxx and it is only the NCC loss

I re-read the equation and the code. When unpacking the bracket, why does the numerator have only IJ_sum - I_sum * J_mean without - I_mean * J_sum + I_mean * J_mean? Similarly, some terms seem to be missing from the denominator, or the calculation seems a bit weird. I also reviewed the NCC code from VoxelMorph, and their code seems correct, but my registration result gets messed up after a few epochs. So, I guess I might have some misunderstanding in calculating the equations here.
I've noticed that the equation in your code and the one from VoxelMorph are slightly different, with yours adding a root to the entire equation if I understand it correctly. However, I couldn't understand the missing terms I mentioned above and why the equation here is correct.
Thanks a lot in advance for helping me gain a better understanding of the math here. :)

You are welcome
numerator have only IJ_sum - I_sum * J_mean: this is simplification of the computation by expanding the multiplication in the numerator. Something like simplified expression for variance. https://math.stackexchange.com/questions/1040587/need-explanation-how-we-simplified-expression-for-variance
equation used: The equation I used should be the standard NCC as you can check wiki or matlab doc.
ncc_loss less than -1.0: I can not replicate this behavior. Here is the minimal code to calculate it. The result I got is always around -0.01 which means no correlation. You can try to put your data in. Note: permute data outside the ncc loss to test the ncc function.
import torch
import torch.nn.functional as F
import torch.nn as nn

class NCC(nn.Module):
    '''
    Calculate local normalized cross-correlation coefficient between tow images.

    Parameters
    ----------
    dim : int
        Dimension of the input images.
    windows_size : int
        Side length of the square window to calculate the local NCC.
    '''
    def __init__(self, dim, windows_size = 11):
        super().__init__()
        assert dim in (2, 3)
        self.dim = dim
        self.num_stab_const = 1e-4 # numerical stability constant

        self.windows_size = windows_size

        self.pad = windows_size//2
        self.window_volume = windows_size**self.dim
        if self.dim == 2:
            self.conv = F.conv2d
        elif self.dim == 3:
            self.conv = F.conv3d

    def forward(self, I, J):
        '''
        Parameters
        ----------
        I and J : (n, 1, h, w) or (n, 1, d, h, w)
            Torch tensor of same shape. The number of image in the first dimension can be different, in which broadcasting will be used.
        windows_size : int
            Side length of the square window to calculate the local NCC.

        Returns
        -------
        NCC : scalar
            Average local normalized cross-correlation coefficient.
        '''
        try:
            I_sum = self.conv(I, self.sum_filter, padding = self.pad)
        except:
            self.sum_filter = torch.ones([1, 1] + [self.windows_size, ]*self.dim, dtype = I.dtype, device = I.device)
            I_sum = self.conv(I, self.sum_filter, padding = self.pad)

        J_sum = self.conv(J, self.sum_filter, padding = self.pad) # (n, 1, h, w) or (n, 1, d, h, w)
        I2_sum = self.conv(I*I, self.sum_filter, padding = self.pad)
        J2_sum = self.conv(J*J, self.sum_filter, padding = self.pad)
        IJ_sum = self.conv(I*J, self.sum_filter, padding = self.pad)

        cross = torch.clamp(IJ_sum - I_sum*J_sum/self.window_volume, min = self.num_stab_const)
        I_var = torch.clamp(I2_sum - I_sum**2/self.window_volume, min = self.num_stab_const)
        J_var = torch.clamp(J2_sum - J_sum**2/self.window_volume, min = self.num_stab_const)

        cc = cross/((I_var*J_var)**0.5)

        return -torch.mean(cc)

img_size = (4, 1, 64, 128, 256)
num_repeat = 4
ncc = NCC(dim = 3)

ncc_loss_list = torch.zeros(num_repeat, dtype = torch.float32)
for i in range(num_repeat):
    img1 = torch.randn(img_size, dtype = torch.float32)
    img2 = torch.randn(img_size, dtype = torch.float32)
    ncc_loss = ncc(img1, img2)
    ncc_loss_list[i] = ncc_loss

print(ncc_loss_list.min())
print(ncc_loss_list.max())


Build faliure on Arch Linux

I tried to make and install this amazing software but I'm having issues building it
Make spews all these errors when attempting to build:
make -C /lib/modules/6.6.1-arch1-1/build/ M=`pwd` modules
make[1]: Entering directory '/usr/lib/modules/6.6.1-arch1-1/build'
  CC [M]  /home/bread/uwurandom/uwurandom.o
In file included from ./include/linux/linkage.h:7,
                 from ./include/linux/kernel.h:17,
                 from /home/bread/uwurandom/uwurandom.c:1:
/home/bread/uwurandom/uwurandom.c: In function ‘kinit’:
./include/linux/export.h:29:22: error: passing argument 1 of ‘class_create’ from incompatible pointer type [-Werror=incompatible-pointer-types]
   29 | #define THIS_MODULE (&__this_module)
      |                     ~^~~~~~~~~~~~~~~
      |                      |
      |                      struct module *
/home/bread/uwurandom/uwurandom.c:113:30: note: in expansion of macro ‘THIS_MODULE’
  113 |     dev_class = class_create(THIS_MODULE, "uwurandom");
      |                              ^~~~~~~~~~~
In file included from ./include/linux/device.h:31,
                 from /home/bread/uwurandom/uwurandom.c:5:
./include/linux/device/class.h:230:54: note: expected ‘const char *’ but argument is of type ‘struct module *’
  230 | struct class * __must_check class_create(const char *name);
      |                                          ~~~~~~~~~~~~^~~~
/home/bread/uwurandom/uwurandom.c:113:17: error: too many arguments to function ‘class_create’
  113 |     dev_class = class_create(THIS_MODULE, "uwurandom");
      |                 ^~~~~~~~~~~~
./include/linux/device/class.h:230:29: note: declared here
  230 | struct class * __must_check class_create(const char *name);
      |                             ^~~~~~~~~~~~
cc1: some warnings being treated as errors
make[3]: *** [scripts/Makefile.build:243: /home/bread/uwurandom/uwurandom.o] Error 1
make[2]: *** [/usr/lib/modules/6.6.1-arch1-1/build/Makefile:1913: /home/bread/uwurandom] Error 2
make[1]: *** [Makefile:234: __sub-make] Error 2
make[1]: Leaving directory '/usr/lib/modules/6.6.1-arch1-1/build'
make: *** [Makefile:8: all] Error 2

I'm running kernel version 6.6.1-arch1-1, and I do have the linux-headers package installed

Seems there was a change to the way device classes are created in Linux 6.4 and up. I've fixed the code to build on newer kernels--let me know if you have any further issues.


Applying registration transforms onto points/Physical vs. Index Space

Hello channel,
I am quite new to SITK. I have a similar problem to https://github.com/SimpleITK/SimpleITK/issues/532. My sitk transformations are working for images, but not for points by using TransformPoints.
My problem is the following: I have to knee label images of femur bone, from which I want to take sample points of one fixed image and find the corresponding points in the moving image. Therefore I calculate a transform from moving to fixed and use its TransformPoints to calculate the corresponding points in the other image.
My pipeline is as follows:

My initial points are sampled in the index space since i convert the fixed image to a numpy array.

Calculating a normal affine transform

warp images using the sitk resampler (should not do that much, since both images have same resolution (384, 384, 160)

warp points using transform points.

As you can see in the pics below: The points are aligned with the transform and have similar shape to the registered image. However it is smaller!?
Anyone an idea!?
Thanks in advance

You said your fixed points are in the index space of the fixed image. But at step 4 you transform point are still in physical space. Perhaps you need to convert from physical space to index space with fixed_image.TransformPhysicalPointToContinuousIndex
Also in step 3 you need to specify the output meta-data for the physical range of the resulting image.

So full pipeline would be:

Sample point indices

Get points by using moving_image.TransformContinuousIndexToPhysicalPoint

Calculate transform (done in physical space) from moving to fixed

transform.TransformPoints(point)

Get indices by using fixed_image.TransformPhysicalPointToContinuousIndex

I believe your problem as been solved so I'm closing the issue. Please re-open if needed.

(I dont know if I should open a new issue, but my problem is exactly the same.) The only difference is that the proposed approach doesn't work for me.
Images are the same size. and when I use the resample as in this issue it works fine.
Here is my final transformation
itk::simple::Transform
 BSplineTransform (000002A6FF0FF0A0)
   RTTI typeinfo:   class itk::BSplineTransform<double,2,3>
   Reference Count: 3
   Modified Time: 1211661
   Debug: Off
   Object Name:
   Observers:
     none
   CoefficientImage: [ 000002A683BA9C20, 000002A683BAA190 ]
   TransformDomainOrigin: [-0.625, -0.625]
   TransformDomainPhysicalDimensions: [2304.25, 1312.25]
   TransformDomainDirection: 1 0
0 1

   GridSize: [9, 9]
   GridOrigin: [-384.667, -219.333]
   GridSpacing: [384.042, 218.708]
   GridDirection: 1 0
0 1

and here is an example of my attempt to transform a point
[2173. 1233.]    # indexed point
(2173.0, 1233.0) # moving_image.TransformContinuousIndexToPhysicalPoint([2173. 1233.])
(2174.3411790844652, 1327.8135024643282) # transformed physical point
(2174.3411790844652, 1327.8135024643282) # moving_image.TransformPhysicalPointToContinuousIndex((2174.3411790844652, 1327.8135024643282))

for the last line i also trying using the fixed image to transform it but I wasn't very successful. Any help is more than welcome


CLI command to deploy centralized connection for ICON

Description on the linked epic

https://github.com/icon-project/centralized-relay/pull/109


Make CI work without needing an Amazon S3 or PackageCloud.io account

Summary

There should be a simple and easy way for uploads to Amazon S3 and PackageCloud.io to be disabled in CI. This allows CI to pass without paying for paid services just to hack on Atom in a fork.
Motivation

@aminya and I have been working on a fork of Atom. When running the CI, we have noticed that the "Atom Production Branches" and "Atom Nightly" pipelines require authentication to a paid Amazon S3 account and a paid PackageCloud.io account.
Having a good way for CI to run without attempting to upload to these services is friendly to forks. We could roll our own solution to this at our fork, but any other fork that might come along after us would have to reinvent that wheel, so it would be amazing to centralize the approach here at upstream.
When editing the CI files, we are still hoping to upstream our changes. But this is something I would expect upstream to care fairly strongly about, since it is part of the official release process for stable/official Atom. Rather than try to predict what upstream wants, it seems prudent to ask about it and start a discussion.
Describe alternatives you've considered

We could disable uploading to PackageCloud.io by editing the flags in the pipeline .yml configs, used to call script/vsts/upload-artifacts.js. But these changes would not be suitable for upstreaming. And this could be prone to merge conflicts with upstream if you ever need to update the pipeline .yml files.
This also does not disable uploads to Amazon S3, so editing script/vsts/upload-artifacts.js is required in any case.
In order to avoid merge conflicts and the productivity loss of fragmented and forked CI configs, we are hoping to avoid carrying patches for CI for ourselves.
Additional context

We have been working on an upstream-friendly implementation of these changes here: https://github.com/atom-ide-community/atom/pull/66
This WIP implementation is designed to require no changes (can be merged as-is, "just works") by upstream, while offering forks an easy way to toggle off uploads to paid services (S3 and PackageCloud.io).
With the current WIP design, forks would just need to set a variable (in the Azure DevOps UI) SKIP_UPLOADING_TO = e.g. s3,packagecloud to turn any given service off.

I can see how this would benefit a fork, but what benefit does this provide to the main Atom repo? Adding the complexity of making this able to be toggled is more code to maintain here for no benefit. The entire point of a fork is that you are going in a different direction from the main project so you will need to be changing quite a bit of the code.

I can see how this would benefit a fork, but what benefit does this provide to the main Atom repo?

I'll admit: In a vacuum, this provides nothing immediately to upstream. But for some projects, contributions from upstream make up a large portion of new changes. So it could be meaningful to Atom to have a robust community of forks contributing code that has already been CI-tested before even being posted as PRs. And it affords the community a bit more independence in how they operate. IMO it is an ecosystem investment, rather than strictly a benefit to upstream.

Another thing: I was motivated to post this issue because the CI config is somewhat modular already, allowing uploads to PackageCloud be "turned on or off" with flags, but depending on your perspective (we have a fork's perspective obviously):

It is deficient at disabling S3, as uploads to S3 always happen regardless
Enabling/disabling things by flags is prone to merge conflicts
The flags used to be env variables IIRC, but was changed to yargs and flags at some point, making this feature harder or at least more redundant for us to code downstream.

I'm motivated to post here because the existing solution is "so close, but not quite there", and our WIP solution would add a second layer of configurability, which just doesn't seem right. More complexity than there probably should be. Discussing with upstream in the open puts more options on the table to rewrite this in a way that makes sense for upstream and forks.
In short: The best design here (for us, and in the long view, for a robust fork-friendly ecosystem) is only possible through coordinating with upstream and agreeing on a design.
Worst-case scenario is we have to carry patches for the CI. Best-case scenario, upstream is interested, we improve the CI code, and everyone benefits from the well-considered code.

Thanks for the reply earlier. We found a way to handle this automatically.
We are able to detect if the vars are unset in Azure Pipelines (despite that Azure Pipelines makes them non-empty from a JS point of view, see below). If credentials/API keys are unset, then we skip uploading to whichever service(s) the credentials cars weren't set for.
https://github.com/atom-ide-community/atom/pull/66/files

What was tripping me up: We can't check if these vars are "empty" or "unset" in JS, because they will either be some manually set value, or else when unset in Azure Pipelines, the env vars will hold literally $(VAR_NAME_HERE). Dollar sign and parentheses and ALL_CAPS_VAR_NAME all will be in the env var.
https://docs.microsoft.com/en-us/azure/devops/pipelines/process/variables?view=azure-devops&tabs=yaml%2Cbatch#runtime-expression-syntax
Solution: rather than simply checking for an empty/falsy env var in JS, we can check that the var doesn't equal the default "unset" version of itself per DevOps, e.g. process.env.PACKAGE_CLOUD_API_KEY !== '$(PACKAGE_CLOUD_API_KEY)'.
To be extra safe, we can check that the var is JavaScript truthy. This is to handle the scenarios when someone has set the vars to be the empty string, or some refactor some time in the future allows the vars to be JS unset.
At that point we're back to basically reading env vars, and there's no fancy rewrite of the code needed. No new variables are needed, either.

We might post this as a PR after we've been using it for a bit. It's working great so far. The idea being for the repo to be ready to be forked by anybody and have working CI right away.

@DeeDeeG I don't think that extra check is needed. The process.env variable is either empty or it has some value.

Closing here.
This is 99% solved, so it's no-longer an "actionable"/open issue IMO.
(Still working out the fine details and waiting for a response from Azure pipelines developers on a question we had before we make a final version of the code.)
If we post a PR here, we can still point to this issue even if it's "closed."


ImportError: Using bitsandbytes 8-bit quantization requires Accelerate

(qloravenv) C:\deepdream-test\llm_qlora-main>python train.py C:\deepdream-test\llm_qlora-main\configs\mistralaiMistral-7B-v0.1.yaml
Load base model
Traceback (most recent call last):
File "C:\deepdream-test\llm_qlora-main\train.py", line 25, in
trainer.load_base_model()
File "C:\deepdream-test\llm_qlora-main\QloraTrainer.py", line 37, in load_base_model
model = AutoModelForCausalLM.from_pretrained(model_id, quantization_config=bnb_config, device_map={"":0})
File "C:\deepdream-test\llm_qlora-main\qloravenv\lib\site-packages\transformers\models\auto\auto_factory.py", line 561, in from_pretrained
return model_class.from_pretrained(
File "C:\deepdream-test\llm_qlora-main\qloravenv\lib\site-packages\transformers\modeling_utils.py", line 3024, in from_pretrained
hf_quantizer.validate_environment(
File "C:\deepdream-test\llm_qlora-main\qloravenv\lib\site-packages\transformers\quantizers\quantizer_bnb_4bit.py", line 62, in validate_environment
raise ImportError(
ImportError: Using bitsandbytes 8-bit quantization requires Accelerate: pip install accelerate and the latest version of bitsandbytes: pip install -i https://pypi.org/simple/ bitsandbytes
I did follow the instructions of the import error but no difference..

I also tried testing if accelerate works and it does..
I am running on a windows 10 machine with a 3090
(qloravenv) C:\deepdream-test\llm_qlora-main>accelerate test

Running:  accelerate-launch C:\deepdream-test\llm_qlora-main\qloravenv\lib\site-packages\accelerate\test_utils\scripts\test_script.py
stderr: The following values were not passed to `accelerate launch` and had defaults used instead:
stderr:         `--num_processes` was set to a value of `0`
stderr:         `--num_machines` was set to a value of `1`
stderr:         `--mixed_precision` was set to a value of `'no'`
stderr:         `--dynamo_backend` was set to a value of `'no'`
stderr: To avoid this warning pass in values for each of the problematic parameters or run `accelerate config`.
stdout: **Initialization**
stdout: Testing, testing. 1, 2, 3.
stdout: Distributed environment: NO
stdout: Num processes: 1
stdout: Process index: 0
stdout: Local process index: 0
stdout: Device: cpu
stdout:
stdout: Mixed precision type: no
stdout:
stdout:
stdout: **Test process execution**
stdout:
stdout: **Test split between processes as a list**
stdout:
stdout: **Test split between processes as a dict**
stdout:
stdout: **Test split between processes as a tensor**
stdout:
stdout: **Test random number generator synchronization**
stdout: All rng are properly synched.
stdout:
stdout: **DataLoader integration test**
stdout: 0 tensor([ 0,  1,  2,  3,  4,  5,  6,  7,  8,  9, 10, 11, 12, 13, 14, 15, 16, 17,
stdout:         18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31]) <class 'accelerate.data_loader.DataLoaderShard'>
stdout: Non-shuffled dataloader passing.
stdout: Shuffled dataloader passing.
stdout: Non-shuffled central dataloader passing.
stdout: Shuffled central dataloader passing.
stdout:
stdout: **Training integration test**
stdout: Model dtype: torch.float32, torch.float32. Input dtype: torch.float32
stdout: Model dtype: torch.float32, torch.float32. Input dtype: torch.float32
stdout: Training yielded the same results on one CPU or distributed setup with no batch split.
stdout: Model dtype: torch.float32, torch.float32. Input dtype: torch.float32
stdout: Training yielded the same results on one CPU or distributes setup with batch split.
stdout: BF16 training check.
stdout: Model dtype: torch.float32, torch.float32. Input dtype: torch.float32
stdout: Model dtype: torch.float32, torch.float32. Input dtype: torch.float32
stdout: Model dtype: torch.float32, torch.float32. Input dtype: torch.float32
stdout: Training yielded the same results on one CPU or distributed setup with no batch split.
stdout: Model dtype: torch.float32, torch.float32. Input dtype: torch.float32
stdout: Training yielded the same results on one CPU or distributes setup with batch split.
stdout: BF16 training check.
stdout: Model dtype: torch.float32, torch.float32. Input dtype: torch.float32
stdout:
stdout: **Breakpoint trigger test**
Test is a success! You are ready for your distributed training!

In python if you try import accelerate does that work?


Auth.signUp Error in Local Env with Supabase CLI

Bug report
Describe the bug
supabase.auth.signup on local setup gives 'Database error finding user'.
A clear and concise description of what the bug is.
Installed supabase cli, set up a local project, and then tried to do a simple user signup. On signup I get a status: 500 with message: Database error finding user.
To Reproduce
Steps to reproduce the behavior, please provide code snippets or a repository:

supabase init
localhost:8000
postgres port 5477 (only thing different from default)
create index.js with the following:

import { createClient } from '@supabase/supabase-js'
const SUPABASE_URL = 'http://localhost:8000'
const SUPABASE_ANON_KEY = 'key-here'
const supabase = createClient(SUPABASE_URL, SUPABASE_ANON_KEY)

const main = async () => {
  const { user, session, error } = await supabase.auth.signUp({
    email<EMAIL_ADDRESS>    password: 'superpasswordtighty',
  })
  console.log(user)       //null
  console.log(session)  //null
  console.log(error)     //{ message: 'Database error finding user', status: 500 }
}
main()

Expected behavior
A user would be created in the database.  I can connect to postgres just fine, and it looks like everything is there (as far as I know).  I also tried the auth.signIn method, and I get the same error (which makes sense since there's no user yet). Not sure if the signUp method is getting it's wires crossed with singIn?
Screenshots
postgres database:

System information

OS: Windows running Ubuntu and Docker Desktop through WSL2

Version of supabase-js: 1.7.6, cli: 0.3.3

Version of Node.js: 15.6.0

I raises a similar issue here. https://github.com/supabase/supabase/discussions/1023
Although I am not sure I have the auth.users table in my local db.

@soedirgo Looks like it's here:
https://github.com/supabase/cli/blob/5666b4dad71da0d0d96de040952bfc4d0804a669/src/templates/init/docker/docker-compose.yml#L29
If the port is something other than 5432 I guess GoTrue can't connect

@kiwicopple just following up here. I did run init on port 5432, so it is a little different. But when running supabase start it doesn't seem any of the supabase tables were created in the database.

Thanks for the follow up @KrisCoulson - let us investigate 👍

there should be some more specific error messages from the gotrue logs in docker, it is almost definitely the case that gotrue either:

cannot connect to the database
cannot see or access the auth.users table
some trigger is causing the insert transaction to fail (seen this a couple of times in the wild)

@KrisCoulson can you try checking or tailing the gotrue logs

These are the logs for me:
time="2021-04-01T08:45:39.729628Z" level=debug msg="Set log level to: debug"
time="2021-04-01T08:45:39Z" level=info msg="GoTrue API started on: <IP_ADDRESS>:9999"
time="2021-04-01T08:46:35Z" level=info msg="request started" component=api method=POST path=/signup referer="http://localhost:3000/" remote_addr="<IP_ADDRESS>:51926" request_id=90b5f6be-2d6e-40f1-a774-700e1e538b01
time="2021-04-01T08:46:35Z" level=error msg="500: Database error finding user" component=api error="error finding user: ERROR: relation \"users\" does not exist (SQLSTATE 42P01)" method=POST path=/signup referer="http://localhost:3000/" remote_addr="<IP_ADDRESS>:51926" request_id=90b5f6be-2d6e-40f1-a774-700e1e538b01
time="2021-04-01T08:46:35Z" level=info msg="request completed" component=api duration=68992000 method=POST path=/signup referer="http://localhost:3000/" remote_addr="<IP_ADDRESS>:51926" request_id=90b5f6be-2d6e-40f1-a774-700e1e538b01 status=500

Maybe relevant: auth isn't in search_path, but auth.users exists

I can also replicate - debugging now

Tried a few more times with different settings, still had the same problem. I deleted .supabase and tried again with port: 5432. Interestingly enough, supabase init gives me the exact same credentials each time. Still got the same error, so created an entirely new directory, deleted the docker group, and tried supabase init again with the defaults.  Still got the same credentials, and the same Database error finding user.

@alteredorange this should be fixed in #12 (you'll have to remove .supabase and re-init). I'll just merge it in now - let me know if it works!

Yes, I can sign in now, thanks for getting that sorted!!

@soedirgo I pulled the latest and re-init and I still don't seem to have auth.users generated in my postgres db. Maybe I am setting it up wrong

@KrisCoulson did you delete your docker containers as well? Didn't work for me until I also deleted all supabase docker containers, and then supabases start rebuilt them the correct way.

@alteredorange Yeah I killed the containers and re-init and still no luck my database is completely empty

@KrisCoulson can I please doublecheck that you removed the containers, not just killed them?
 If not, looks like it wasn't building the image properly.

@kiwicopple this time just to make sure everything was clear I removed all containers and images.
@soedirgo a screen recording of the container logs. It does have ALTER ROLE
https://user-images.githubusercontent.com/6943688/113379287-ef262d00-932d-11eb-99f0-f0ec2cd7180d.mov

Yes, that looks right. The auth schema doesn't show up in my Postgres IDE, but when I run select * from auth.users; from psql it can find the table.

@soedirgo I have been using tablePlus and if I connect a supabase a hosted supabase db the schema's show fine. The local one does not show the schemas. But even so selecting from the auth.users does not find the table.
https://user-images.githubusercontent.com/6943688/113423785-efe9ae00-9383-11eb-817b-e334840aaae9.mov

Hmm... this bug keeps eluding me. 😅
Maybe a last straw: can you try opening a shell to the container and run the query with psql directly in it? Failing that, if you run tail -f /var/lib/postgresql/data/log/postgresql.csv inside the container, and then run the query from anywhere, the errors should pop up there.

@soedirgo looks like auth table exists when directly inside of the container. Also ran tail -f

OK, that's good. My guess is psql was run on the wrong port. Can you check if the supabase-db container is running on 5432 on the host? i.e. you should see this:

And when you have any errors from psql, it should show up in the tail logs above.

This is what mine looks like

You shouldn't have to set up the db, it's self contained. I tried running a Postgres server while the supabase-db container was up - turns out it intercepts connections to 5432, so when I psql'd I connected to the native local server rather than the container. Stopping the Postgres server should fix this.

@soedirgo that was it!
I ended up having to run brew services stop postgresql Might be worth mention that in the documentation this edge case where local connections highjack the connection to the docker contiainer.
Thanks for your help!

Whew! Glad to have this resolved. 😄

@soedirgo I guess one more question is the best way to have access to local dbs just to update the port when running a local postgres?
My app also uses a test_db for storing temporary test data. So to have them running I would need to start postgres server on a seperate port and have the docker-container use port 5432
@kiwicopple mentioned that GoTrue cant connect unless it is on 5432

If the port is something other than 5432 I guess GoTrue can't connect

If the port is something other than 5432 I guess GoTrue can't connect

I don't think this applies, 5432 is the default host port, but the container port is always 5432, so no problem there.
Your best bet is probably to reinit, though there are probably ways to do this if you really have to.


Gel image TIFF

Please add TIFF as a gel image file format. It is another common image format output by many gel imagers

Java 11 upgrade complete!


[ingestion/data-quality issue] CycloneDX specification as of 1.4 does not require the component field in metadata

Describe the bug
Discovered by kurt-r2c in original PR https://github.com/guacsec/guac/pull/896:
The CycloneDX specification as of 1.4 does not require the component field in metadata, nor does it require the BOM ref field: https://cyclonedx.org/docs/1.4/json/#metadata_component_bom-ref.
guac was encountering a NPE when trying to read these uninitialized fields from the CycloneDX struct.
Some SBOM generators that only operate on package lockfiles (such as https://pypi.org/project/cyclonedx-bom/) do not generate the component metadata field, nor are they required to by the spec.
To Reproduce
ingestion of an SBOM that is generated by SBOM generators that only operate on package lockfiles (such as https://pypi.org/project/cyclonedx-bom/) that do not generate the component metadata field.
Expected behavior
Currently, output an error message that this is not currently supported as there would be no top-level package node and would result in a bunch of singleton packages. Further discussion and handling will need to be done to handle this use-case.
GUAC version
v0.1

@kurt-r2c wanted to check back here, want to see what other use cases we need to handle here that stemmed from discussion of this issue.

What more specifically needs to be added to the "component field in metadata" to make a CycloneDX file work? Do you have an example of what will work so folks can add that to their CycloneDX output and still make it work with GUAC (even if the spec doesn't support it no biggie to overlay the field post output from existing generators).

Hey @joestein, at the minimum GUAC requires the following in the component field in the metadata:
https://github.com/guacsec/guac/blob/e55fa2498e9b1851b8e0fdb5b95874774005824b/internal/testing/testdata/exampledata/alpine-cyclonedx.json#L15-L20
At the minimum, it needs the name, version, type, and bom-ref. If the purl is available, that would be the best as guac does not need to infer. Based on the CycloneDX spec the version and bom-ref are not required fields but provide a more accurate SBOM.
Without this information, GUAC cannot make proper relationships between the top-level component and its dependencies (resulting in a bunch of singletons).


Popup notification alignment blocking buttons

The popups are infuriatingly placed. For instance after copying an account address, the "Copied Deposit Address" popup covers the bottom of the extension and blocks the 'Close' button to return to the main wallet page. Even when it disappears within a second this is annoying, but sometimes it gets stuck and does not go away ever.
Possible solution could be to align it somewhere besides the bottom, or truncate the width so that it doesn't block the button.

Still present and still annoying.


added in option to smooth scroll back to top

This should provide the requested effect of scrolling back to top of page if logo is clicked while on the homepage.

This is working!
Great work!!
I am merging this.
Thanks @fudgemasterultra


Local DNS records are synced when they shouldn't be

What happened?
I'm syncing two piholes (two docker containers), but do not want them to sync local DNS records, because of the different networks they operate in.
However, the SYNC_LOCALDNSRECORDS is being ignored. I've tried using
SYNC_LOCALDNSRECORDS: 'false' and SYNC_LOCALDNSRECORDS: 0, to no avail.
This is my config:
  orbital-sync-2:
    image: mattwebbio/orbital-sync:1
    container_name: pihole-sync-vpn
    environment:
      PRIMARY_HOST_BASE_URL: 'http://<IP_ADDRESS>'
      PRIMARY_HOST_PASSWORD: ''
      SECONDARY_HOST_1_BASE_URL: 'http://<IP_ADDRESS>'
      SECONDARY_HOST_1_PASSWORD: ''
      SYNC_LOCALDNSRECORDS: 'false' #different IPs
      UPDATE_GRAVITY: 'false'
      TZ: 'Europe/Amsterdam'
      INTERVAL_MINUTES: 1440

Version
latest
Log output
10-11-2022 10:59:55
11/10/2022, 10:59:55 AM: ➡ Signing in to http://<IP_ADDRESS>/admin...
10-11-2022 10:59:55
11/10/2022, 10:59:55 AM: ✔ Successfully signed in to http://<IP_ADDRESS>/admin!
10-11-2022 10:59:55
11/10/2022, 10:59:55 AM: ➡ Downloading backup from http://<IP_ADDRESS>/admin...
10-11-2022 10:59:56
11/10/2022, 10:59:56 AM: ✔ Backup from http://<IP_ADDRESS>/admin completed!
10-11-2022 10:59:56
11/10/2022, 10:59:56 AM: ➡ Signing in to http://<IP_ADDRESS>/admin...
10-11-2022 10:59:56
11/10/2022, 10:59:56 AM: ✔ Successfully signed in to http://<IP_ADDRESS>/admin!
10-11-2022 10:59:56
11/10/2022, 10:59:56 AM: ➡ Uploading backup to http://<IP_ADDRESS>/admin...
10-11-2022 11:00:19
11/10/2022, 11:00:19 AM: ✔ Backup uploaded to http://<IP_ADDRESS>/admin!
10-11-2022 11:00:19
11/10/2022, 11:00:19 AM: ✔ Success: 1/1 hosts synced.
10-11-2022 11:00:19
11/10/2022, 11:00:19 AM: Waiting 1400 minutes...

Has this changed for you in a recent version?
If you run with v.1.3.0 do you have the same issue?

In addition to @cbundy's comment, if you could add VERBOSE: true to your configuration and re-post the log output it would be super helpful :)
The server's response from the upload should get returned when verbose mode is enabled.

I copied and pasted from the homepage so I was apparently running version 1.  Nevertheless, there seems to be no difference between versions. See below.
Just to be sure, I've been running two instances/containers of this image, since I want to sync my primary pi-hole completely to a second pihole, and then without to DNS-records to another pihole. Maybe things (like the backup.zip) are getting mixed up on the host file-system? I suppose this shouldn't happen, but just to make sure.
Complete docker-compose:
  orbital-sync:
    image: mattwebbio/orbital-sync:1.4.0
    container_name: pihole-sync
    environment:
      PRIMARY_HOST_BASE_URL: 'http://<IP_ADDRESS>'
      PRIMARY_HOST_PASSWORD: ''
      SECONDARY_HOST_1_BASE_URL: 'http://<IP_ADDRESS>'
      SECONDARY_HOST_1_PASSWORD: ''
      UPDATE_GRAVITY: 'false'
      INTERVAL_MINUTES: 1440
      TZ: 'Europe/Amsterdam'
  orbital-sync-2:
    image: mattwebbio/orbital-sync:1.3.0
    container_name: pihole-sync-vpn
    environment:
      PRIMARY_HOST_BASE_URL: 'http://<IP_ADDRESS>'
      PRIMARY_HOST_PASSWORD: ''
      SECONDARY_HOST_1_BASE_URL: 'http://<IP_ADDRESS>'
      SECONDARY_HOST_1_PASSWORD: ''
      SYNC_LOCALDNSRECORDS: 'false' #different IPs
      UPDATE_GRAVITY: 'false'
      TZ: 'Europe/Amsterdam'
      INTERVAL_MINUTES: 1400
      VERBOSE: 'true'

Output for 1.3.0
11-11-2022 7:51:32
11/11/2022, 7:51:32 AM: ✔ Backup uploaded to http://<IP_ADDRESS>!
11-11-2022 7:51:32
11/11/2022, 7:51:32 AM: Result:
11-11-2022 7:51:32
Processed adlist (31 entries)

11-11-2022 7:51:32
Processed adlist group assignments (31 entries)

11-11-2022 7:51:32
Processed blacklist (exact) (8 entries)

11-11-2022 7:51:32
Processed blacklist (regex) (0 entries)

11-11-2022 7:51:32
Processed client (3 entries)

11-11-2022 7:51:32
Processed client group assignments (5 entries)

11-11-2022 7:51:32
Processed local DNS records (16 entries)

11-11-2022 7:51:32
Processed local CNAME records (23 entries)

11-11-2022 7:51:32
Processed domain_audit (0 entries)

11-11-2022 7:51:32
Processed black-/whitelist group assignments (274 entries)

11-11-2022 7:51:32
Processed group (2 entries)

11-11-2022 7:51:32
Processed whitelist (exact) (261 entries)

11-11-2022 7:51:32
Processed whitelist (regex) (3 entries)

11-11-2022 7:51:32
OK
11-11-2022 7:51:32
11/11/2022, 7:51:32 AM: ✔ Success: 1/1 hosts synced.

I've been experimenting a bit more, and it seems that also Environment variables like SYNC_LOCALCNAMERECORDS, SYNC_WHITELIST, are not getting picked up on. Which is interesting because       UPDATE_GRAVITY: 'false', is getting handled accordingly.
No differences between versions 1.3.0 and 1.4.0.

So sorry for the delay on this! I'm in the process of moving and so I've not had time to look into this further.
Orbital just tries to emulate the form inputs on the "restore" section of the teleporter - it's possible these have either changed or I just didn't set them up correctly in the first place.
My default troubleshooting step would be to manually run a backup and then try unchecking the things you don't want synced. If it works by hand, it's definitely an issue with Orbital's handling of the checkboxes and I can fix (or PRs welcome!)

I'm not sure if specifying false for those form properties is intended to work in pihole, but what I can see is that when I untick options for restore, the entire property is gone.
All ticked

Untick localdns and localcname

Forgive me if this doesn't make any sense, I'm a bit guessing on how this should work. In my understanding, interpreting  @cbundy response:

Pihole does not want a variable=false when the form is submitted, it expects the value instead of being 'true', to be gone from posted form.
Orbital-sync processes the variables in the generateForm() function:

  private generateForm(): typeof FormData.prototype {
    const form = new FormData();
    form.append('token', this.token);

    form.append('whitelist', Config.syncOptions.whitelist);
    form.append('regex_whitelist', Config.syncOptions.regexWhitelist);
    form.append('blacklist', Config.syncOptions.blacklist);
    form.append('regexlist', Config.syncOptions.regexlist);
    form.append('adlist', Config.syncOptions.adlist);
    form.append('client', Config.syncOptions.client);
    form.append('group', Config.syncOptions.group);
    form.append('auditlog', Config.syncOptions.auditlog);
    form.append('staticdhcpleases', Config.syncOptions.staticdhcpleases);
    form.append('localdnsrecords', Config.syncOptions.localdnsrecords);
    form.append('localcnamerecords', Config.syncOptions.localcnamerecords);
    form.append('flushtables', Config.syncOptions.flushtables);

It may be the case that pihole does not even check the contents of the localdnsrecords variable, but simple checks whether the variable is present.
So, to solve the issue, the generateForm() function should be modified as to only add the variables that are not disabled through the environment-variables passed on from docker-compose.
In pseudo-code (I only know PHP a bit) something like this?
  private generateForm(): typeof FormData.prototype {
    const form = new FormData();
    form.append('token', this.token);

 variables = array ('whitelist','regex_whitelist','blacklist','...');
 foreach (variables as $variable) {
    if(Config.syncOptions$variable!== 'false) {
          form.append('$variable', Config.syncOptions.$variable);
    }
 }

Yep, I think you're spot on. I will give it a test this weekend and can put a PR together if you can't.
If you want to have a crack, there is a dev container so you can just start coding, you can code in the cloud as well without needing anything installed, just click this button above the code!

I actually managed to use this cloud coding and created a pull request. Not sure if I have should've done that, as I'm not able to use the variable name for the config.Syncoptions, it creates an "Identifier expected" error.
  private generateForm(): typeof FormData.prototype {
    const form = new FormData();
    form.append('token', this.token);
    const variables = ['whitelist','regex_whitelist','blacklist','regexlist','adlist','client','group','auditlog','staticdhcpleases','localdnsrecords','localcnamerecords','flushtables'];
    let fLen = variables.length;

    for (let i = 0; i < fLen; i++) {
      var configVariable = variables[i];
      if(Config.syncOptions.[configVariable] != false) {
        form.append(variables[i],Config.syncOptions.[configVariable]);
      }
    }

    return form;
  }

Thanks so much @cbundy and @MJVerhulst for looking in to this while I've been away! I really, really appreciate it. I saw you opened a PR @MJVerhulst but it didn't look like I had write access to the branch to update the tests. I've pushed up a similar PR that omits the form fields (rather than setting them to false), and I've pushed up a prerelease image:
mattwebbio/orbital-sync:1.4.1-0

@MJVerhulst if you have the opportunity to test, that would be amazing!

Thanks @cbundy for your feedback on my JS "code" that you posted on the pull-request, very helpful :).
I did some testing and I think it's now working as expected.
Check 1
Config
  orbital-sync-2:
    image: mattwebbio/orbital-sync:1.4.1-0
    container_name: pihole-sync-vpn
    environment:
      PRIMARY_HOST_BASE_URL: 'http://<IP_ADDRESS>'
      PRIMARY_HOST_PASSWORD: ''
      SECONDARY_HOST_1_BASE_URL: 'http://<IP_ADDRESS>'
      SECONDARY_HOST_1_PASSWORD: 'rdk7DaCKQOE6'
      SYNC_LOCALDNSRECORDS: 'false' #different IPs
      SYNC_LOCALCNAMERECORDS: 'true'
      UPDATE_GRAVITY: 'false'
      TZ: 'Europe/Amsterdam'
      INTERVAL_MINUTES: 1400
      VERBOSE: 'true'
      SYNC_WHITELIST: 'false'

Output
25-11-2022 19:32:06
11/25/2022, 7:32:06 PM: ➡ Signing in to http://<IP_ADDRESS>/admin...
25-11-2022 19:32:07
11/25/2022, 7:32:07 PM: ✔ Successfully signed in to http://<IP_ADDRESS>/admin!
25-11-2022 19:32:07
11/25/2022, 7:32:07 PM: ➡ Downloading backup from http://<IP_ADDRESS>/admin...
25-11-2022 19:32:07
11/25/2022, 7:32:07 PM: ✔ Backup from http://<IP_ADDRESS>/admin completed!
25-11-2022 19:32:07
11/25/2022, 7:32:07 PM: ➡ Signing in to http://<IP_ADDRESS>/admin...
25-11-2022 19:32:07
11/25/2022, 7:32:07 PM: ✔ Successfully signed in to http://<IP_ADDRESS>/admin!
25-11-2022 19:32:07
11/25/2022, 7:32:07 PM: ➡ Uploading backup to http://<IP_ADDRESS>/admin...
25-11-2022 19:32:30
11/25/2022, 7:32:30 PM: ✔ Backup uploaded to http://<IP_ADDRESS>/admin!
25-11-2022 19:32:30
11/25/2022, 7:32:30 PM: Result:
25-11-2022 19:32:30
Processed adlist (33 entries)

25-11-2022 19:32:30
Processed adlist group assignments (33 entries)

25-11-2022 19:32:30
Processed blacklist (exact) (7 entries)

25-11-2022 19:32:30
Processed blacklist (regex) (0 entries)

25-11-2022 19:32:30
Processed client (26 entries)

25-11-2022 19:32:30
Processed client group assignments (28 entries)

25-11-2022 19:32:30
Processed local CNAME records (24 entries)

25-11-2022 19:32:30
Processed black-/whitelist group assignments (277 entries)

25-11-2022 19:32:30
Processed group (2 entries)

25-11-2022 19:32:30
Processed whitelist (regex) (3 entries)

25-11-2022 19:32:30
OK
25-11-2022 19:32:30
11/25/2022, 7:32:30 PM: ✔ Success: 1/1 hosts synced.
25-11-2022 19:32:30
11/25/2022, 7:32:30 PM: Waiting 1400 minutes...

Check 2
  orbital-sync-2:
    image: mattwebbio/orbital-sync:1.4.1-0
    container_name: pihole-sync-vpn
    environment:
      PRIMARY_HOST_BASE_URL: 'http://<IP_ADDRESS>'
      PRIMARY_HOST_PASSWORD: 'rdk7DaCKQOE6'
      SECONDARY_HOST_1_BASE_URL: 'http://<IP_ADDRESS>'
      SECONDARY_HOST_1_PASSWORD: 'rdk7DaCKQOE6'
      SYNC_LOCALDNSRECORDS: 'false' #different IPs
      SYNC_LOCALCNAMERECORDS: 'false'
      SYNC_WHITELIST: 'false'
      SYNC_REGEXLIST: 'true'
      SYNC_BLACKLIST: 'false'
      UPDATE_GRAVITY: 'false'
      TZ: 'Europe/Amsterdam'
      INTERVAL_MINUTES: 1400
      VERBOSE: 'true'

Output
25-11-2022 19:38:46
11/25/2022, 7:38:46 PM: ➡ Signing in to http://<IP_ADDRESS>/admin...
25-11-2022 19:38:47
11/25/2022, 7:38:47 PM: ✔ Successfully signed in to http://<IP_ADDRESS>/admin!
25-11-2022 19:38:47
11/25/2022, 7:38:47 PM: ➡ Downloading backup from http://<IP_ADDRESS>/admin...
25-11-2022 19:38:47
11/25/2022, 7:38:47 PM: ✔ Backup from http://<IP_ADDRESS>/admin completed!
25-11-2022 19:38:47
11/25/2022, 7:38:47 PM: ➡ Signing in to http://<IP_ADDRESS>/admin...
25-11-2022 19:38:47
11/25/2022, 7:38:47 PM: ✔ Successfully signed in to http://<IP_ADDRESS>/admin!
25-11-2022 19:38:47
11/25/2022, 7:38:47 PM: ➡ Uploading backup to http://<IP_ADDRESS>/admin...
25-11-2022 19:38:56
11/25/2022, 7:38:56 PM: ✔ Backup uploaded to http://<IP_ADDRESS>/admin!
25-11-2022 19:38:56
11/25/2022, 7:38:56 PM: Result:
25-11-2022 19:38:56
Processed adlist (33 entries)

25-11-2022 19:38:56
Processed adlist group assignments (33 entries)

25-11-2022 19:38:56
Processed blacklist (regex) (0 entries)

25-11-2022 19:38:56
Processed client (26 entries)

25-11-2022 19:38:56
Processed client group assignments (28 entries)

25-11-2022 19:38:56
Processed black-/whitelist group assignments (277 entries)

25-11-2022 19:38:56
Processed group (2 entries)

25-11-2022 19:38:56
Processed whitelist (regex) (3 entries)

25-11-2022 19:38:56
OK
25-11-2022 19:38:56
11/25/2022, 7:38:56 PM: ✔ Success: 1/1 hosts synced.
25-11-2022 19:38:56
11/25/2022, 7:38:56 PM: Waiting 1400 minutes...


Add option to only shown spawnable

Basically hiding the green overlays, only showing red/orange.

Thank you for your suggestion, I'll look into it! May take some time though

Fixed with Lighty v2.1.0, which you can find on Modrinth or on GitHub.
There are also some other goodies in this release, so feel free to check it out!
Thanks for opening this issue, have fun playing!


Default title only when not explicitly set

Allows push with no title via:
pb push -t "" "Hello world!"

Done. I tend to avoid inline ifs, but they can look nicer.


Assertion 'compressed_pointer != JMEM_CP_NULL' in jmem_decompress_pointer

Jerry version:
Checked revision: 7905422
Build command: ./tools/build.py --clean --debug --profile=es2015-subset

OS:
Ubuntu 16.04.3 LTS

Test case:
var a = Promise.resolve();
for (;;)
    Promise.race([a]).then()
$

Backtrace:
ICE: Assertion 'compressed_pointer != JMEM_CP_NULL' failed at jerryscript/jerry-core/jmem/jmem-allocator.c(jmem_decompress_pointer):96.
Error: ERR_FAILED_INTERNAL_ASSERTION
bt
#0  0x000000000047971f in syscall_2 () at jerryscript/jerry-libc/target/posix/jerry-asm.S:59
#1  0x000000000040489e in raise (sig=6) at jerryscript/jerry-libc/target/posix/jerry-libc-target.c:95
#2  0x0000000000404870 in abort () at jerryscript/jerry-libc/target/posix/jerry-libc-target.c:81
#3  0x0000000000406dc4 in jerry_port_fatal (code=ERR_FAILED_INTERNAL_ASSERTION) at jerryscript/jerry-port/default/default-fatal.c:71
#4  0x000000000042aa80 in jerry_fatal (code=ERR_FAILED_INTERNAL_ASSERTION) at jerryscript/jerry-core/jrt/jrt-fatals.c:58
#5  0x000000000042aad0 in jerry_assert_fail (assertion=0x480c18 "compressed_pointer != JMEM_CP_NULL", file=0x480b38 "jerryscript/jerry-core/jmem/jmem-allocator.c", function=0x494750 <__func__.3185.lto_priv.290> "jmem_decompress_pointer", line=96) at jerryscript/jerry-core/jrt/jrt-fatals.c:82
#6  0x000000000042a8ce in jmem_decompress_pointer (compressed_pointer=0) at jerryscript/jerry-core/jmem/jmem-allocator.c:96
#7  0x00000000004728d0 in ecma_collection_iterator_next (iterator_p=0x7fffffffc890) at jerryscript/jerry-core/ecma/base/ecma-helpers-values-collection.c:332
#8  0x0000000000473327 in ecma_gc_mark (object_p=0x6a4b00 <jerry_global_heap+6160>) at jerryscript/jerry-core/ecma/base/ecma-gc.c:282
#9  0x0000000000474187 in ecma_gc_run (severity=JMEM_FREE_UNUSED_MEMORY_SEVERITY_LOW) at jerryscript/jerry-core/ecma/base/ecma-gc.c:753
#10 0x0000000000474368 in ecma_free_unused_memory (severity=JMEM_FREE_UNUSED_MEMORY_SEVERITY_LOW) at jerryscript/jerry-core/ecma/base/ecma-gc.c:849
#11 0x000000000042aa04 in jmem_run_free_unused_memory_callbacks (severity=JMEM_FREE_UNUSED_MEMORY_SEVERITY_LOW) at jerryscript/jerry-core/jmem/jmem-allocator.c:148
#12 0x0000000000431582 in jmem_heap_gc_and_alloc_block.lto_priv.296 (size=8, ret_null_on_error=false) at jerryscript/jerry-core/jmem/jmem-heap.c:359
#13 0x000000000042a2e6 in jmem_heap_alloc_block (size=8) at jerryscript/jerry-core/jmem/jmem-heap.c:408
#14 0x000000000042a695 in jmem_pools_alloc (size=8) at jerryscript/jerry-core/jmem/jmem-poolman.c:102
#15 0x0000000000472b53 in ecma_alloc_collection_chunk () at jerryscript/jerry-core/ecma/base/ecma-alloc.c:85
#16 0x000000000047239c in ecma_append_to_values_collection (header_p=0x6a4b28 <jerry_global_heap+6200>, v=8123, do_ref_if_object=false) at jerryscript/jerry-core/ecma/base/ecma-helpers-values-collection.c:168
#17 0x0000000000437765 in ecma_promise_do_then (promise=6163, on_fulfilled=7891, on_rejected=7907, result_capability=6371) at jerryscript/jerry-core/ecma/operations/ecma-promise-object.c:700
#18 0x0000000000437943 in ecma_promise_then (promise=6163, on_fulfilled=7891, on_rejected=7907) at jerryscript/jerry-core/ecma/operations/ecma-promise-object.c:765
#19 0x0000000000445375 in ecma_builtin_promise_prototype_then (this_arg=6163, on_fulfilled=7891, on_rejected=7907) at jerryscript/jerry-core/ecma/builtin-objects/ecma-builtin-promise-prototype.c:51
#20 0x000000000044530f in ecma_builtin_promise_prototype_dispatch_routine (builtin_routine_id=58, this_arg_value=6163, arguments_list=0x7fffffffce5c, arguments_number=2) at jerryscript/jerry-core/ecma/builtin-objects/ecma-builtin-promise-prototype.inc.h:31
#21 0x000000000046019c in ecma_builtin_dispatch_routine (builtin_object_id=ECMA_BUILTIN_ID_PROMISE_PROTOTYPE, builtin_routine_id=58, this_arg_value=6163, arguments_list=0x7fffffffce5c, arguments_number=2) at jerryscript/jerry-core/ecma/builtin-objects/ecma-builtins.inc.h:467
#22 0x0000000000460334 in ecma_builtin_dispatch_call (obj_p=0x6a3d78 <jerry_global_heap+2696>, this_arg_value=6163, arguments_list_p=0x7fffffffce5c, arguments_list_len=2) at jerryscript/jerry-core/ecma/builtin-objects/ecma-builtins.c:844
#23 0x000000000043c2ac in ecma_op_function_call (func_obj_p=0x6a3d78 <jerry_global_heap+2696>, this_arg_value=6163, arguments_list_p=0x7fffffffce5c, arguments_list_len=2) at jerryscript/jerry-core/ecma/operations/ecma-function-object.c:419
#24 0x00000000004203ef in opfunc_call.lto_priv.142 (frame_ctx_p=0x7fffffffcea0) at jerryscript/jerry-core/vm/vm.c:408
#25 0x000000000041286e in vm_execute (frame_ctx_p=0x7fffffffcea0, arg_p=0x0, arg_list_len=0) at jerryscript/jerry-core/vm/vm.c:2743
#26 0x0000000000412aef in vm_run (bytecode_header_p=0x6a3890 <jerry_global_heap+1440>, this_binding_value=27, lex_env_p=0x6a3320 <jerry_global_heap+48>, is_eval_code=false, arg_list_p=0x0, arg_list_len=0) at jerryscript/jerry-core/vm/vm.c:2823
#27 0x000000000042005f in vm_run_global (bytecode_p=0x6a3890 <jerry_global_heap+1440>) at jerryscript/jerry-core/vm/vm.c:231
#28 0x0000000000477214 in jerry_run (func_val=259) at jerryscript/jerry-core/api/jerry.c:444
#29 0x0000000000476119 in main (argc=3, argv=0x7fffffffd188) at jerryscript/jerry-main/main-unix.c:707

Found by  Fuzzinator

fixed in #2000.


Talks: add link button for code like on the publication page

It would be nice if a button for code can be integrated on the talk page like on the publication page. Then you have only add url_code="https://linktosourcecode" in the meta data list in your md file for referencing your source code.

Added. Thanks for your suggestion and PR :)


c#_project_directory setting causes C# project feature to be stripped from project.godot

Godot version
4.0 beta5
System information
Windows 11
Issue description
I discovered the dotnet/project/c#_project_directory setting, which is wonderful because I like to keep source separate from the rest of the godot project assets.
I've been using this successfully for a week or two. Unfortunately after settings this, the project.godot file has C# stripped from application/config/features on save, so I've been manually restoring this a lot.
Steps to reproduce

In a project with C# set up already, confirm project.godothas "C#", in the setting config/features=PackedStringArray("4.0", "Forward Plus", "C#")
Edit project settings, turn on advanced, go to DotNet and enter a directory name for c#_project_directory, call it Source for this example
Make Source directory
Move the .csproj into Source directory
Edit .sln file so .csproj is located in the Source dir. Or do this all in your IDE of choice...
Go back to Godot, edit a random setting to trigger project save.
Check project.godot and see C# is removed from the config/features

Minimal reproduction project
SourceDirTest.zip

The dotnet/project/c#_project_directory no longer exists, so this is no longer an issue.


MRU (OldFiles) probably mutates v:oldfiles

After running the MRU function once, the second time it's not working
Error detected while processing function scope#fuzzy#MRU[7]..<lambda>19:
line    1:
E1013: Argument 1: type mismatch, expected string but got dict<string>

I suspect it's because :h filter() and :h map() here https://github.com/girishji/scope.vim/blob/17dec07712708dbe965b670e8ee28b71257d3e47/autoload/scope/fuzzy.vim#L290 mutate the argument v:oldfiles and then all hell breaks loose.

Yes, adding a copy() fixes it.

That's clearly a bug. filter() modifies in place. Bram provided mapnew() but not filternew().
https://github.com/girishji/scope.vim/commit/19a84394fc04d1743cdc6a5b15dec73d64be3ff4 fix this.


Put on NPM?

Hi there,
Any chance you could add this to npm? :)
Thanks.

No, sorry. Slider has been deprecated:

Slider has been deprecated and is no longer maintained. Neither currently open nor new issues will be addressed.

Increasing amounts of data indicate how ineffective sliders are are driving business goals in web design. They often represent an inability of key stakeholders to reach consensus.

When they do serve a focused purpose (for example, image carousels), an alternate design pattern would often better serve the user's goals (for example, just displaying all of the images full-width in a stack).

Beyond pure UX-driven reasons, there are numerous bugs that keep popping up, the original script this was forked from (SwipeJS) is no longer being maintained. I won't be closing the repository, so you'll still be able to access the script and documentation, but I won't be supporting or maintaining it any longer.


Remove task list from pull request template (issue #48)

Pull request type

Please check the type of change your PR introduces:

[x] Bugfix
[ ] Feature
[ ] Code style update (formatting, renaming)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] Other (please describe):

What is the current behavior?

The "type of PR" list causes it to show tasks that cannot be completed.
Issue Number: #48
What is the new behavior?

You no longer select the type of PR since that should be obvious from the Issue that it is related to.

Other information

Updated


Support others date format in events

In events.js, i noticed that you only support "start": new Date(2015, 3, 0) as the date format.
Does bigcalendar support other date formats for start and end date? How can i achieve something of this format
start: '2015-12-01-09:30AM'

It doesn't support anything that isn't an actual Date. Generally speaking, parsing server responses is  outside the scope of this component, which tries to be as agnostic as possible about your data formats.  We think this makes sense anyway since your application will want to handle fetching, parsing, and caching with a more robust holistic approach across your application. We also want to make sure that the user has the opportunity to optimize that step as much as possible, when dealing with thousands or tens of thousands of events.
Not to mention that parsing dates is notoriously fraught and domain specific outside the few ISO formats (even still that can be a nightmare). In terms of getting hte work done though I recommend

https://github.com/csnover/js-iso8601 for simple, straightforward date only parsing
for a more robust solution we use https://github.com/jquense/yup, which is one of many options in js schema parsing libs


May 14, 2020 | Code-Review : The Poodles

Nice start. Keep it up!

nice work
remember to sort out the private event

Hello, thanks for your feedback. :wave:
We have implemented the sort, to show the corresponding events based on it's accessibility either private or public. :male_detective:
You can see the changes in the next link: d81c561cd09ad75b1cbb9155546f3a06b077c7ce :eyes:


Error generating lily58 image

I am getting the following error when trying to generate an image for my lily58 config.
❯ zmk-viewer generate lily58
2023-01-29T14:36:53Z INF Fetching keyboard layout.
zmk-viewer: error: invalid character '<' looking for beginning of value

I get the same error for other variations of the lily58 from the qmk configurator:

zmk-viewer generate "splitkb/aurora/lily58/rev1"
zmk-viewer generate "lily58/light"
zmk-viewer generate "lily58/rev1"

It is also the same whether I add in my config with -f or not.

That error was because there isn't a keyboard named lily58 in the QMK repository and the request was giving a 404 error: https://keyboards.qmk.fm/v1/keyboards/lily58/info.json
The correct name includes the revision (lily58/rev1): https://keyboards.qmk.fm/v1/keyboards/lily58/rev1/info.json
I've added an error message to let the user know the keyboard isn't found instead of just an error

Awesome! Thanks!


Fix required partitioning of Single aggregation mode

Which issue does this PR close?

Closes #6949
Rationale for this change
Fix a small issue in this aggregation mode

What changes are included in this PR?

Are these changes tested?

Are there any user-facing changes?

FYI @mingmwang

According to CombinePartialFinalAggregate rule, when planner sees AggregateMode::Partial + AggregateMode::Final or AggregateMode::Partial + AggregateMode::FinalPartitioned, it replaces these immediate operators with AggregateMode::Single.
For second case changing distribution requirement to Distribution::HashPartitioned makes sense. However, for first case distribution requirement should be SinglePartition I guess.
With the proposed changes, AggregateMode::Single will require vec![Distribution::HashPartitioned(vec![])] (where group by is empty). when it is constructed from AggregateMode::Partial + AggregateMode::Final stack.
Will this requirement add RepartitionExec(hash) during planning?

@mustafasrepo
I think the purpose of this PR is to extend the use case of AggregateMode::Single. I think the change make sense, but it is better to add some comments.

According to CombinePartialFinalAggregate rule, when planner sees AggregateMode::Partial + AggregateMode::Final or AggregateMode::Partial + AggregateMode::FinalPartitioned, it replaces these immediate operators with AggregateMode::Single. For second case changing distribution requirement to Distribution::HashPartitioned makes sense. However, for first case distribution requirement should be SinglePartition I guess.
With the proposed changes, AggregateMode::Single will require vec![Distribution::HashPartitioned(vec![])] (where group by is empty). when it is constructed from AggregateMode::Partial + AggregateMode::Final stack.
Will this requirement add RepartitionExec(hash) during planning?

Ah I missed that part.
I missed the part that Final + FinalPartitioned is also being converted to Single. I think the correct way (that avoids planning errors) would be a Single that requires SinglePartition in that case.
Currently the optimization rule runs after the RepartitionExec(hash) and CoalescePartitions are added so it should already have those requirements, but I think it's better to generate a correct plan, otherwise we could introduce errors later on (e.g. by a rule that removes unnecessary RepartitionExec / CoalescePartitions or by using the Single mode directly before the required partitioning is added).


[GHSA-8mpp-f3f7-xc28] SslConnection does not release pooled ByteBuffers in case of errors

Updates

Affected products

Hi there @sbordet and @waynebeaton! A community member has suggested an improvement to your security advisory. If approved, this change will affect the global advisory listed at github.com/advisories. It will not affect the version listed in your project repository.
This change will be reviewed by our highly-trained Security Curation Team. If you have thoughts or feedback, please share them in a comment here! If this PR has already been closed, you can start a new community contribution for this advisory


"Offset exceeds device limit" while updating pinebookPro SPI to 002

Hello. I've been using Tow-Boot "pine64-pinebookPro-2021.04-001" with some success (and some issues but likely unrelated to Tow-Boot).
I'm trying to update to 002, as described in the release page it fails to recognize $board_identifier. The suggested workaround, env default board_identifier, didn't work ($board_identifier stays empty).
I had to do env set board_identifier pine64-pinebookPro to pass the check.
Then this happens:

Any idea?
I would like to avoid having to completely erase the SPI Flash as it's been annoying to force booting on the SD without Tow-Boot.

Ooooh...
I guess I never tried upgrading from 001 stock to 002.
See the Unknown command 'setexpr'? It's a missing command that the script now relies on.
You should be able to run these commands in the Firmware Console. Note that these will not "harden" against partial flashes like the updater script does. It's not likely to be an issue unless you decide to force reboot the Pinebook Pro while it's writing.
I have not tried running these commands yet. I'll try in a few hours once I'm done with work. I would suggest you wait until I verified they'll work before trying :).
mmc dev 1
load mmc 1:2 $kernel_addr_r Tow-Boot.spi.bin
sf probe
sf update $kernel_addr_r 0x0 $filesize

Added to the known issues. This message is for other users, @badcold, I know you won't be able to erase the SPI and boot from the new release.

Workarounds
If it is not a problem for your situation, erase the SPI Flash content, and reboot into the firmware from the SD card.

How do I know if this is a problem for me or not? Generally, it will be a problem only if you have a valid U-Boot install on the eMMC, which would be preferred over the SD card.

Otherwise, [wait until the previously listed commands are tested and] use the previously listed commands to manually upgrade the firmware in SPI Flash.

@badcold, here's my transcript of going from the 001 release (without a change) to 002 on another RK3399 device. Note that I burned spi.installer.img to an SD card.
[Selected Firmware Console in the menu]

Use `run menucmd` to return to the menu.

=> mmc dev 1
switch to partitions #0, OK
mmc1 is current device
=> load mmc 1:2 $kernel_addr_r Tow-Boot.spi.bin
1566248 bytes read in 72 ms (20.7 MiB/s)
=> sf probe
SF: Detected w25q128 with page size 256 Bytes, erase size 4 KiB, total 16 MiB
=> sf update $kernel_addr_r 0x0 $filesize
device 0 offset 0x0, size 0x17e628
1246760 bytes written, 319488 bytes skipped in 11.471s, speed 139816 B/s
=>

After, I removed the SD card (to ensure things worked), and used reset to restart the machine.
Note that if you're using serial to access the machine, the baud rate was changed. I'm saying so since I scared myself into thinking the machine didn't boot at first :).

Closing since upgrades from 001 to 002 are now unlikely, the documented steps are still valid.