Migrate core package 'go-to-line' into Atom repo

This issue tracks the steps necessary to migrate the go-to-line package into the core atom/atom repository under the packages path:
Migration Checklist
Phase 1 - Prepare repo for migration

[x] Merge or close existing pull requests on the atom/go-to-line repository

Some guidelines for merging vs closing PRs:

Merge when the PR is small, useful, has no merge conflicts with master, and has passing tests
Close when the changes are non-trivial, the PR has conflicts with master, or there are failing tests in CI

If you close a PR, let the user know that we are currently moving the repository over to atom/atom so they should feel free to reopen the pull request there once the package code has been migrated.
Phase 2 - Migrate the package code

[x] Create a fresh branch off master in your local clone of atom/atom with the name migrate-go-to-line-package
[x] Delete Atom's node_modules folder if you've built there before and make sure Atom's package-lock.json file is unmodified
[x] Clone the  atom/go-to-line repo into the packages path of your local Atom repository and then delete its .git subfolder
[x] Delete any unnecessary repo configuration files in the packages/go-to-line folder like appveyor.yml, .travis.yml, ISSUE_TEMPLATE.md, and PULL_REQUEST_TEMPLATE.md
[x] Remove any information from the package's README.md which will be inaccurate after the migration is complete (e.g. CI status badges or contribution instructions)
[x] Edit Atom's package.json file to change the following:

[x] Update the go-to-line entry in packageDependencies to reflect the local path of the package:"go-to-line": "file:./packages/go-to-line",

[x] Delete the go-to-line entry in the dependencies section since it may contain a hardcoded tarball link.  This will help avoid issues in the next step
[x] Change the repository field to point to the main repo URL https://github.com/atom/atom

[x] Run a full Atom build using script/build and verify that there are no unexpected build errors
[x] Launch the Atom binary in the ./out folder and manually verify that the migrated package is working without any obvious issues.  For example, if you're migrating a color theme, turn on that theme to make sure that it changes the editor colors as expected.
[x] Open the Chrome Developer Tools console (Ctrl+Shift+I or Cmd+Option+I) and ensure that there are no errors written there.  If there are, add them to this issue and investigate.
[x] Update the second column of the go-to-line row in packages/README.md to reflect the new local path for the package:[`./packages/go-to-line`](./go-to-line)

[x] Commit the migrated package code and any changes to Atom's package-lock.json files to your branch using this commit message::arrow_right: Migrate core package 'go-to-line' into ./packages

Phase 3 - Make sure the package works and send a PR

[x] Run the full suite of Atom tests with script/test and verify that they pass locally
[x] If any tests fail, investigate and fix them then commit the fixes to your branch
[x] Create a PR against atom/atom to verify that CI passes
[x] Once CI is clean and the PR is approved, merge it

Phase 4 - Archive the go-to-line repo

[x] Move all existing issues from the  go-to-line repo to atom/atom using github-issue-mover or a script
[x] Add a label titled packages/go-to-line to the migrated issues so that they can be found easily
[x] Edit the original package repo's README.md (don't commit directly) to point contributors to the code's new home in atom/atom.  You can use the following text:### This package is now a part of the [core Atom repository](https://github.com/atom/atom/tree/master/packages/go-to-line), please direct all issues and pull requests there in the future!

---

[x] Send a PR to the go-to-line repository with the updated README.md so that watchers will be notified of the change.  You do not need to wait for reviews, it can be merged immediately.
[x] Archive the package repository by going to its Settings page, scroll down to the "Danger Zone" section and click "Archive this Repository"

Migration is now complete! :tada:

Migration is complete :tada:

https://github.com/atom/atom/pull/18235
https://github.com/atom/go-to-line/pull/56


S3CrudPolicy does not allow object deletion

The current definition of S3CrudPolicy only allows object create, read, and update permissions. Please add the s3:DeleteObject permission to the policy.

Yes, I confirmed this myself.

Just got bit by this and can't release ServerlessOpsIO/aws-application-dollar-monitoring to AppRepo as a result. :(

You can get around it by manually writing out a policy.
  DeleteData:
    Type: AWS::Serverless::Function
    Properties:
      Handler: ...
      CodeUri: ....
      Policies:
        -
          Version: 2012-10-17
          Statement:
            -
              Effect: Allow
              Action:
                - s3:DeleteObject
              Resource: !Sub ${MyBucket.Arn}/*

@oharaandrew314 I believe I won't be able to publish to AppRepo still  though.  don't have the exact error from earlier, but I believe it was along the lines of "Need to use a policy template"

I commented on #453


MD-3355: baseline updates for MapR-DB tests

@Agirish could you please review this PR?

Tried manually via Sqlline for a query - the fix worked. Merging it in.
Thanks for making the changes.


Checkpoints given show low performance in baz and pmp tasks

First of all, thanks for sharing the code of your amazing work in here.
But when I try to use the checkpoints you give to test performance, I noticed everything works fine except in baz and pmp tasks, ckpts for these 2 may have something wrong, could you please check again if you put wrong files in here by mistake? I'll appreciate that.

p1 for seist-l and p2 for seist-m results on DiTing, I used checkpoints trained on DiTing from this github repository.

Thank you for pointing out this issue. I'll check it.

Hi @Wang-XingHao,
I guess you accidentally missed some arguments (in Supporting Table S1). You could have a try with the following arguments.

For pmp task:
--in-samples 256  --p-position-ratio 0.5

For baz task:
--in-samples 150  --p-position-ratio 0.33

This method refers to the implementation of DiTingMotion which fixes the phase-p position in the input seismogram to improve the model's accuracy.

Oh my bad, indeed I didn't notice this setting : (  now pmp performs well as expected, and baz is better but still low

my test script :
python main.py \     --seed 0 \     --mode "test" \     --model-name "seist_l_baz" \     --checkpoint  "./logs/pretrained_seist_l_***_diting_light/checkpoints/model-baz.pth" \     --log-base "./logs" \     --log-step 600 \     --data "/project/datasets/DiTing330km" \     --dataset-name "diting_light" \     --data-split true \     --train-size 0.8 \     --val-size 0.1 \     --shuffle true \     --workers 6 \     --in-samples 150 \     --p-position-ratio 0.33 \     --batch-size 128 \
do I miss any other specific settings? thank you for kind reply again!

From these args, it is not easy to locate the problem. Maybe you can contact me on WeChat (SKJ1073) for more convenient communication.

many thanks, I just found my co-worker trained a seist-l-baz model on diting_light from scratch quite long ago (train and test with normal input length=8192 and no specific p_position_ratio set) and it performs well with

[BAZ]MEAN -0.0377  STD 68.0148  MAE 42.4609  R2 0.5659
so I get no worries about this issue now, but still happy to communicate with you!


PageIndex Generation Reverted

I added an option named "RevertIndex" to generate Index Page in ascending or descending order.

Can you revert the formatting changes? It would be easier to see what has actually changed.

I reverted text format in homeController only added 2 parameters.

The formatting changes are still visible here

Changed rows are 43 and 51 only added last parameter "false".


docs: punctuation

Overview

What is it?

[ ] Feature / enhancement
[ ] Bug
[ ] Docs / tests / types / typos

Description
Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change.
Use cases and why

One use case

Another use case

Checklist:

[ ] My code follows the developer guidelines of this project
[ ] I have performed a self-review of my own code
[ ] I have made corresponding changes to the documentation
[ ] Added new tests to cover the fix / functionality

thanks so much for the help @sajebehari
Is it possible for you to create just one PR for all of the docs typo and grammar fixes?
It'll help us review it faster and will create less noise in our notifications
Thanks! 🙏


Not reading historic nearshore events

FloodAdapt version checks

[X] I have checked that this issue has not already been reported.
[X] I have checked that this bug exists on the latest version of FloodAdapt.

Reproducible Example
Not reading historic nearshore events
Current behaviour
Not reading historic nearshore events
Desired behaviour
reading historic nearshore events
Task list

[ ] remove the added column in plot water levels

Additional context
No response

Fixed and merged


Docs: explain go templates in custom commands

This PR edits the Config.md doc to explain the go template variables that are available to authors of custom commands.
With this info documented, it becomes much easier for users to write commands such as:
customCommands:
  containers:
    -
      name: dive
      attach: true
      command: dive {{ .Container.Container.ImageID }}
      serviceNames: []

This also takes care of a minor yaml issue in the doc. Before the change, Github highlighted this as invalid:

Thanks for making this @jchvz !


Add collatz-conjecture exercise

Note: I've excluded the test cases for zero or negative inputs.

Some include them, some don't. I initially didn't know what to do with them, so I left them out, but in recent exercises I've adapted the test cases to make them more idiomatic for Roc, i.e., I've use result == Ok 123 and result == Err "some error message.".
Would it be even more idiomatic to use tags instead of strings? E.g., result == Err InvalidNegativeInput or something?

@Anton-4 , I updated the code to add error handling (see #33), thanks for your feedback.


Verify graphics output

HoI4Country::outputIdeaGraphics() currently outputs minister graphics for all ideology types. This may not be correct in cases where the ideologies don't exist.

After verification, this causes no problems.


Using feathers-authentication-jwt for api key authentication

I want to add API keys authentication to my feathesjs app.
It should work by sending a header with a key assigned to the client, which should be checked against a database for validation.
So, if I understand correctly, I could potentially use feathers-authentication-jwt to do this (https://docs.feathersjs.com/api/authentication/jwt.html) by tweaking the configuration and Verifier.
Seems that my problem is that I can't get my Verifier to work and the default one is invoked, so no authentication for you, let me show you.
// authentication.js
'use strict';

const authentication = require('feathers-authentication');
const jwt = require('feathers-authentication-jwt');
const local = require('feathers-authentication-local');
const apikey = require('feathers-authentication-jwt'); // <-- my api key authentication
const Verifier = require('feathers-authentication-jwt').Verifier; // <-- working? apparently yes

console.log('VERIFIER', Verifier); //<-- what is `Verifier`? It's a function

module.exports = function () {
    // do my own verification stuff
	class apiKeyVerifier extends Verifier {
		verify (req, payload, done) {
			console.log('VERIFY');
			done (null, payload);
		}
	}
	const app = this;
	const config = app.get('authentication');

	// Set up authentication with the secret
	app.configure(authentication(config));
	app.configure(jwt());
	app.configure(local());
	console.log('API VERIFIER', apiKeyVerifier); // <-- what is `apiKeyVerifier`? a class
	app.configure(apikey({
		name: 'apikey',
		service: 'api-keys',
		entity: 'api-keys',
		idField: 'api_keys_id',
		header: 'x-api-key',
		Verifier: apiKeyVerifier
	}));

	// The `authentication` service is used to create a JWT.
	// The before `create` hook registers strategies that can be used
	// to create a new valid JWT (e.g. local or oauth2)
	app.service('authentication').hooks({
		before: {
			create: [
				authentication.hooks.authenticate(config.strategies)
			],
			remove: [
				authentication.hooks.authenticate('jwt')
			]
		}
	});
};

What happens when I try to authorize?
I try like this:
curl -X POST \
  http://localhost:5000/authentication \
  -H 'cache-control: no-cache' \
  -H 'content-type: application/x-www-form-urlencoded' \
  -H 'x-api-key: &xh&vtK9s¿Gr<JG' \
  -d strategy=apikey

I get this response:
feathers-authentication:passport:authenticate Authentication strategy 'apikey' failed { JsonWebTokenError: jwt malformed
      at Object.module.exports [as verify] (/Users/transistor/Documents/WebServer/asc-api/node_modules/jsonwebtoken/verify.js:54:17)
      at Function.module.exports [as JwtVerifier] (/Users/transistor/Documents/WebServer/asc-api/node_modules/passport-jwt/lib/verify_jwt.js:4:16)
      at JwtStrategy.authenticate (/Users/transistor/Documents/WebServer/asc-api/node_modules/passport-jwt/lib/strategy.js:91:17)
      at /Users/transistor/Documents/WebServer/asc-api/node_modules/feathers-authentication/lib/passport/authenticate.js:131:18
      at /Users/transistor/Documents/WebServer/asc-api/node_modules/feathers-authentication/lib/passport/authenticate.js:38:14
      at Object.<anonymous> (/Users/transistor/Documents/WebServer/asc-api/node_modules/feathers-authentication/lib/hooks/authenticate.js:80:55)
      at process._tickCallback (internal/process/next_tick.js:103:7) name: 'JsonWebTokenError', message: 'jwt malformed' } undefined
info: error: authentication - Method: create: jwt malformed
error:  NotAuthenticated: jwt malformed
      at NotAuthenticated.ExtendableBuiltin (/Users/transistor/Documents/WebServer/asc-api/node_modules/feathers-errors/lib/index.js:21:28)
      at NotAuthenticated.FeathersError (/Users/transistor/Documents/WebServer/asc-api/node_modules/feathers-errors/lib/index.js:96:116)
      at new NotAuthenticated (/Users/transistor/Documents/WebServer/asc-api/node_modules/feathers-errors/lib/index.js:149:117)
      at /Users/transistor/Documents/WebServer/asc-api/node_modules/feathers-authentication/lib/hooks/authenticate.js:102:31
      at process._tickCallback (internal/process/next_tick.js:103:7)

Which, if I'm not mistaken, it means that my Verifier is not being used, so it fails because it isn't a jwt.
So, first, am I on the right track? I mean, can I use this strategy to authenticate by API keys?
Second, if so, what am I doing wrong?
Thanks!

Hi @jlpellicer
Have you made any progress? I am dealing with a similar problem trying to use passport-custom but I can`t find documentation about how integrate it with feathers.
I think "Authentication strategy 'apikey' failed" because you have not defined apikey strategy. passport-custom allow define your own strategy:
passport.use('strategy-name', new CustomStrategy(
  function(req, callback) {
    // Do your custom user finding logic here, or set to false based on req object
    callback(null, user);
  }
));

Any ideas will be welcome ;-)
Salu2
Fernando

This one might help you guys out: https://docs.feathersjs.com/guides/auth/recipe.custom-auth-strategy.html


Remove hard (epel, apt) module dependencies, use soft ones

According to the Puppet Style Guide https://docs.puppet.com/puppet/latest/style_guide.html#dependencies , epel and apt are soft dependencies and should be treated as such.

Warning: Module 'puppetlabs-apt' (v4.0.0) fails to meet some dependencies:
  'garethr-docker' (v5.3.0) requires 'puppetlabs-apt' (>= 1.8.0 <= 3.0.0)


ServieAccount name changes in Vault CRD are not taken into account

Description
When I update the service account name in my Vault object, the change is not propagated by the operator in the subsequent vault StatefulSets and vault-configurer Deployment.
Steps to reproduce

Deploy the Vault Operator chart v1.4.2
Create a Vault object along with RBAC objects (including the ServiceAccount)
Change the name of the ServiceAccount and update the ServiceAccount field in the Vault object
See vault StatefulSets and vault-configurer deployment are still using the obsolete ServiceAccount

Maybe the operator should delete and recreate the vault StatefulSets and update the vault-configurer Deployment when such changes are detected.

What Kubernetes version are you using @jordanjean, I can't reproduce this on 1.16 with the latest Bank-Vaults code with the exact same steps you described.

Hello @bonifaido,
I'm running Kubernetes 1.16.9 and Bank-Vault 1.4.2.
After updating the ServiceAccount of my Vault object (through Helm) I can see reconciling errors in the Operator logs saying it cannot update the StatefulSets (which is normal as Kubernetes does not allow changes of fields other than Replicas and UpdateStrategy).

Allowing the mutation of the template (where serviceAccount is configurable) field was added a before 1.16:
https://github.com/kubernetes/kubernetes/blob/release-1.16/pkg/apis/apps/validation/validation.go#L144
Could you please post the exact error message from the logs of the operator?

This is the error in the operator:
{"level":"error","ts":1601298919.9049187,"logger":"controller","msg":"Reconciler error","controller":"vault-controller","name":"vault","namespace":"myapp-vault","error":"failed to create/update StatefulSet: StatefulSet.apps \"vault\" is invalid: spec: Forbidden: updates to statefulset spec for fields other than 'replicas', 'template', and 'updateStrategy' are forbidden","stacktrace":"github.com/go-logr/zapr.(*zapLogger).Error\n\t/go/pkg/mod/github.com/go-logr/zapr@v0.1.0/zapr.go:128\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).reconcileHandler\n\t/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.6.2/pkg/internal/controller/controller.go:237\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).processNextWorkItem\n\t/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.6.2/pkg/internal/controller/controller.go:209\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).worker\n\t/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.6.2/pkg/internal/controller/controller.go:188\nk8s.io/apimachinery/pkg/util/wait.BackoffUntil.func1\n\t/go/pkg/mod/k8s.io/apimachinery@v0.18.6/pkg/util/wait/wait.go:155\nk8s.io/apimachinery/pkg/util/wait.BackoffUntil\n\t/go/pkg/mod/k8s.io/apimachinery@v0.18.6/pkg/util/wait/wait.go:156\nk8s.io/apimachinery/pkg/util/wait.JitterUntil\n\t/go/pkg/mod/k8s.io/apimachinery@v0.18.6/pkg/util/wait/wait.go:133\nk8s.io/apimachinery/pkg/util/wait.Until\n\t/go/pkg/mod/k8s.io/apimachinery@v0.18.6/pkg/util/wait/wait.go:90"}

And this is the diff between the manifests of the Vault object before the upgrade and the one after the upgrade:
8c8
<   generation: 4
---
>   generation: 3
13,14c13,14
<     app.kubernetes.io/version: 2.2.0
<     helm.sh/chart: mychart-2.2.0
---
>     app.kubernetes.io/version: 2.1.0
>     helm.sh/chart: mychart-2.1.0
17c17
<   resourceVersion: "504429"
---
>   resourceVersion: "501051"
166c166
<   serviceAccount: newName
---
>   serviceAccount: oldName
199a200
>       creationTimestamp: null
204,205c205,206
<         app.kubernetes.io/version: 2.2.0
<         helm.sh/chart: mychart-2.2.0
---
>         app.kubernetes.io/version: 2.1.0
>         helm.sh/chart: mychart-2.1.0
212a214
>     status: {}

The point is that the upgrades of our Vault object is managed by Helm and we add labels app.kubernetes.io/version: <version> and helm.sh/chart: mychart-<version> to our Vault object volumeClaimTemplate. In the diff we can see that the labels are changed because the chart version changed from 2.1.0 to 2.2.0. That is what Kubernetes does not like.
While I was getting errors speaking of wrong ServiceAccount name at the Kubernetes level, the ServiceAccount field was indeed not involved with the StatefulSet upgrade error, but Helm labels were.

No problem!
So it boils down to the fact that volumeClaimTemplates in StatefulSets can't be updated, I don't think we plan to support that in the near future. So I'm closing this one now if you encounter any issues please feel free to open another ticket, or reopen this one.
Maybe it would be worth not to add the Helm version labels to the volumeClaimTemplate labels and you would leave the whole process distraction-free with this. Anyhow if you stick to leaves the labels there I would delete the StatefulSet with --cascase=false and scale down the operator to 0 replicas, so it will not recreate the StatefulSet in the middle of the upgrade process before just upgrading even with Helm. Then scale it back to the original size. With this procedure, you get no downtime.
Thanks for the heads up!


"Page's .Hugo is deprecated and will be removed in a future release."

When building, I get this message:
WARN 2019/05/15 16:41:47 Page's .Hugo is deprecated and will be removed in a future release. Use the global hugo function.

This appears to be coming from here, but possibly from other places.

Hi @rfilmyer ,
thanks for pointing this out. I had an older version of Hugo installed.
I just changed
{{ .Hugo.Generator }}

to
{{ hugo.Generator }}

in /layouts/partials/head/meta.html which solves the issue. I didn't find any other issue when upgrading version.
Please let me know if you have any other issue. Hope you find the theme useful.


Sphereview generator on 3D model

Sphereview data generator towards 3D objects, the top of the camera is always point towards the z axis.
Such image generator will be used for Triplet training of CNN. the demo use the default sphere iteration depth of '0' and the depth could be changed in the source file.
This is not a function yet, no parameter could be directly type in terminal.

Seems that you haven't change the module name. Choiche a module name that could rappresent your gsoc. This need to be an utility inside a module that will contain your gsoc code. Please see again the buildbot log. This PR it is failing.

/cc @mtamburrano

It is a best practice to generate PR from a dedicated branch. See also the other PR in contrib.

OK, I got it, as you have said that 'Use directly a module name that represent your project and put this generator inside it as utility'. I have just create a namespace cv::sphereview3d in header files and source files, do you mean that? @bhack

I don't think that your gsoc module name (and folder) could be shapeview3d. Shapeview3d it is only an utility inside an opencv modules named .....?

So you mean for the module name should be my GSoC project and the module I just completed could just be represented as a class in my project's namespace, is that right? I used to think that different part in project should be placed in different places. Thanks you.

I will make a new pull request from my dedicated branch and close this PR @bhack


Update dependency delay to v5

This PR contains the following updates:

Package
Type
Update
Change

delay
dependencies
major
^4.4.1 -> ^5.0.0

Release Notes

sindresorhus/delay
v5.0.0
Compare Source
Breaking

Require Node.js 10 (#55)  f3c7542

Improvements

Fix missing range() in createWithTimers() return value (#55)  f3c7542

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.

[ ] If you want to rebase/retry this PR, click this checkbox.

This PR has been generated by Renovate Bot.

⚠ Artifact update problem
Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.
♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

any of the package files in this branch needs updating, or
the branch becomes conflicted, or
you click the rebase/retry checkbox if found above, or
you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:
File name: package-lock.json
df: /tmp/renovate/cache/buildpack: No such file or directory
find: ‘/tmp/renovate/cache/buildpack’: No such file or directory
/usr/local/buildpack/utils/cache.sh: line 90: [: : integer expression expected


Fix: Links to hint documentation in multi-hints index doc

Fix #580

Pull request checklist
Make sure you:

[x] Signed the Contributor License Agreement
[x] Followed the commit message guidelines

Short description of the change(s)

@sarvaje I know it's a bit late to request changes, but this fix also caused the sub-hints to appear in the table of contents (note the three webpack references in the screenshot):

Given we have index pages for the multi-hints, I think we should stick to only showing the index page in the list if possible. Thoughts?

I'll take a look

@antross can you open an issue for that?
Thanks!


MSSQL Profiler fails to PUT sample data because utf-8 codec isn't able to serialize unicode to JSON

Affected module
Ingestion Framework
Describe the bug
A profiler ingestion writes a lot of WARNINGs (see "reproduce") into the log (basically for every table) of a MSSQL Database Connection. The job returns then with "Partially Success". Although it was configured to load 100 Sample Data Records for each table, no sample data is loaded. Other Profiler metrics (sum, mean, etc..) work as expected
To Reproduce

The log says
{table_mixin.py:74} WARNING - Error trying to PUT sample data for xxxxx.yyyy.zzz: 'utf-8' codec can't decode byte 0x94 in position 10: invalid start byte
...with different bytes for every table. The trace 'table_mixin.py' basically points to the API call which tries to serialize the collected sample data into a JSON and PUT it to the Table.
So my guess is, that the sample data contains UNICODE (UTF-16? - as every SQL Server contains only that) and the serializer uses an utf-8 codec which fails then.
Expected behavior
At least the codec should fallback to 'latin-1' and the already collected sample data can be put to the table profile accordingly.
Version:

OpenMetadata version: [e.g. 1.1.1 - official Docker Images]

Additional context
SQL Server Build Version is 15.0.2101 (SQL Server 2019)

similar error found in bigquery:
[2023-09-13, 15:29:07 IST] {table_mixin.py:74} WARNING - Error trying to PUT sample data for xxx.xxx.xxxx.bytes_tables: 'utf-8' codec can't decode byte 0x9e in position 1: invalid start byte
[2023-09-13, 15:29:07 IST] {status.py:57} WARNING - Error trying to ingest sample data for table

@pinkerltm can you share the debug logs and schema of the table as well where it's failing

Closing this issue as no reply from @pinkerltm and we cannot reproduce it. will reopen if there is any comment


Marker Cluster Slow

Marker clustering is pretty slow.  The example for 10000 marker cluster is slow to pan and zoom.  This doesn't seem to be an issue when using just leaflet and the marker cluster plugin.  Even with only 1000 items performance degrades pretty bad.

Hi, the markers performance has been improved lastly. Take a look at this example:
http://tombatossals.github.io/angular-leaflet-directive/examples/0000-viewer.html#/markers/clustering-10000-markers-example
Please reopen if needed


EntityFramework.Tools Mac OSX 10.21

Steps to reproduce

Visual Studio for Mac (and necessary binaries)
Create web application
Install Microsoft.EntityFramework.Tools.DotNet 1.1.0-preview4-final

The issue
Trying to install tooling do run dotnet ef commands
Retrieving package 'Microsoft.EntityFrameworkCore.Tools.DotNet 1.1.0-preview4-final' from 'nuget.org'.
Install failed. Rolling back...
Package 'Microsoft.EntityFrameworkCore.Tools.DotNet.1.1.0-preview4-final' does not exist in project 'App'
Executing nuget actions took 620.74 ms
Package 'Microsoft.EntityFrameworkCore.Tools.DotNet 1.1.0-preview4-final' has a package type 'DotnetCliTool' that is not supported by project 'App'.
Further technical details
EF Core version: 1.1.0
[assembly: AssemblyFileVersion ("<IP_ADDRESS>15")]
[assembly: AssemblyInformationalVersion ("1.1.0-rtm-22752")]
Operating system:
Visual Studio for Mac OSX 10.12.21
Other details about my project setup:
dotnet --version 1.0.0-preview3-004056
sdk 1.0.0-preview3-004056 (/usr/local/share/dotnet/sdk

NuGet currently doesn't support installing .NET CLI Tool packages. You need to manually edit the project.json to register it...
  "tools": {
    "Microsoft.EntityFrameworkCore.Tools.DotNet": "1.1.0-preview4-final"
  },

Closing as I think I have answered this, but reply if not and I will reopen.

Thanks will try it out!

Since I'm running Visual Studio for Mac I added it to .csproj as follows
<PackageReference Include="Microsoft.EntityFrameworkCore.Tools.DotNet">
    <Version>1.1.0-preview4-final</Version>
</PackageReference>

The file package.json was nowhere to be found and, as far as I've read, it pretty much has been replaced by .csproj(correct me if I'm wrong - new to .NET core).
Well enough rambling: it still doesn't work.
$ dotnet ef No executable found matching command "dotnet-ef"
So I found a package.json file and included it as well and added the tools section. dotnet restore does nothing but nuget restore try to do something, but fails since there is missing pieces.
Currently this is my package.json (probably completely incorrect)
{
  "dependencies": {
    "Microsoft.NETCore.App": {
      "version": "1.0.0-rc2-3002702"
    },
    "Microsoft.AspNetCore.Mvc": "1.0.0-rc2-final",
    "Microsoft.AspNetCore.Server.IISIntegration": "1.0.0-rc2-final",
    "Microsoft.AspNetCore.Server.Kestrel": "1.0.0-rc2-final",
    "Microsoft.Extensions.Configuration.EnvironmentVariables": "1.0.0-rc2-final",
    "Microsoft.Extensions.Configuration.FileExtensions": "1.0.0-rc2-final",
    "Microsoft.Extensions.Configuration.Json": "1.0.0-rc2-final",
    "Microsoft.Extensions.Logging": "1.0.0-rc2-final",
    "Microsoft.Extensions.Logging.Console": "1.0.0-rc2-final",
    "Microsoft.Extensions.Logging.Debug": "1.0.0-rc2-final",
    "Microsoft.EntityFrameworkCore": "1.0.0-rc2-final"
  },

  "tools": {
    "Microsoft.EntityFrameworkCore.Tools": {
  "version": "1.0.0-preview1-final",
  "imports": [
    "portable-net45+win8+dnxcore50",
    "portable-net45+win8"
  ]
}
  },

  "frameworks": {
    "netcoreapp1.0": {
      "imports": [
        "dotnet5.6",
        "dnxcore50",
        "portable-net45+win8"
      ]
    }
  },

  "buildOptions": {
    "emitEntryPoint": true,
    "preserveCompilationContext": true
  },

  "runtimeOptions": {
    "gcServer": true
  },

  "publishOptions": {
    "include": [
      "wwwroot",
      "Views",
      "appsettings.json",
      "web.config"
    ]
  },

  "scripts": {
    "postpublish": [ "dotnet publish-iis --publish-folder %publish:OutputPath% --framework %publish:FullTargetFramework%" ]
  }
}
````
The output from `nuget restore` is

````
Restoring packages for tool 'Microsoft.EntityFrameworkCore.Tools' in /Users/.../src/App/project.json...
  GET https://api.nuget.org/v3-flatcontainer/microsoft.entityframeworkcore.tools/index.json
  OK https://api.nuget.org/v3-flatcontainer/microsoft.entityframeworkcore.tools/index.json 516ms
  GET https://api.nuget.org/v3-flatcontainer/microsoft.entityframeworkcore.tools/1.0.0-preview1-final/microsoft.entityframeworkcore.tools.1.0.0-preview1-final.nupkg
  OK https://api.nuget.org/v3-flatcontainer/microsoft.entityframeworkcore.tools/1.0.0-preview1-final/microsoft.entityframeworkcore.tools.1.0.0-preview1-final.nupkg 560ms
Installing Microsoft.EntityFrameworkCore.Tools 1.0.0-preview1-final.
Committing restore...
/Users/.../src/App/project.json
Restore completed in 230965ms.

NuGet Config files used:
    /Users/user/.config/NuGet/NuGet.Config

Feeds used:
    https://api.nuget.org/v3/index.json

Installed:
    193 package(s) to /Users/.../src/App/project.json
````

Where those 193 packages went I've no idea and for what reason they were even installed I don't understand (perhaps the different frameworks dnxcore,dnx,portable and so on that is not part of .netstandard1.1 that my app is targeting)

Anyhow: it still doesn't work. Any clues?

What is the plan for .csproj and project.json? Will both be needed when running Visual Studio for Mac?

# .csproj

````
<Project ToolsVersion="15.0" xmlns="http://schemas.microsoft.com/developer/msbuild/2003">
  <Import Project="$(MSBuildExtensionsPath)\$(MSBuildToolsVersion)\Microsoft.Common.props" />

  <PropertyGroup>
    <OutputType>Exe</OutputType>
    <TargetFramework>netcoreapp1.1</TargetFramework>
    <PreserveCompilationContext>true</PreserveCompilationContext>
    <ReleaseVersion>1.0.0-beta1</ReleaseVersion>
  </PropertyGroup>

  <ItemGroup>
    <Compile Include="**\*.cs" Exclude="$(GlobalExclude)" />
    <EmbeddedResource Include="**\*.resx" Exclude="$(GlobalExclude)" />
    <Compile Remove="Controllers\ListItem.cs" />
    <Compile Remove="Models\Url.cs" />
    <Compile Remove="Authorization\CureAuthorizationHandler.cs" />
  </ItemGroup>

  <ItemGroup>
    <!-- Tools -->
    <PackageReference Include="Microsoft.EntityFrameworkCore.Tools.DotNet">
      <Version>1.1.0-preview4-final</Version>
    </PackageReference>
    <!-- Tools end -->
    <PackageReference Include="Microsoft.NET.Sdk.Web">
      <Version>1.0.0-alpha-20161104-2-112</Version>
    </PackageReference>
    <PackageReference Include="Microsoft.NETCore.App">
      <Version>1.1.0</Version>
    </PackageReference>
    <PackageReference Include="Microsoft.AspNetCore.Diagnostics">
      <Version>1.1.0</Version>
    </PackageReference>
    <PackageReference Include="Microsoft.AspNetCore.Server.IISIntegration">
      <Version>1.1.0</Version>
    </PackageReference>
    <PackageReference Include="Microsoft.AspNetCore.Server.Kestrel">
      <Version>1.1.0</Version>
    </PackageReference>
    <PackageReference Include="Microsoft.Extensions.Logging.Console">
      <Version>1.1.0</Version>
    </PackageReference>
    <PackageReference Include="Microsoft.AspNetCore.Mvc">
      <Version>1.1.0</Version>
    </PackageReference>
    <PackageReference Include="Microsoft.AspNetCore.Mvc.Core">
      <Version>1.1.0</Version>
    </PackageReference>
    <PackageReference Include="Microsoft.Extensions.Configuration.FileExtensions">
      <Version>1.1.0</Version>
    </PackageReference>
    <PackageReference Include="Microsoft.Extensions.Configuration.Json">
      <Version>1.1.0</Version>
    </PackageReference>
    <PackageReference Include="Microsoft.AspNetCore.Mvc.TagHelpers">
      <Version>1.1.0</Version>
    </PackageReference>
    <PackageReference Include="Microsoft.AspNetCore.Mvc.Razor">
      <Version>1.1.0</Version>
    </PackageReference>
    <PackageReference Include="Microsoft.EntityFrameworkCore.SqlServer">
      <Version>1.1.0</Version>
    </PackageReference>
    <PackageReference Include="Microsoft.AspNetCore.StaticFiles">
      <Version>1.1.0</Version>
    </PackageReference>
    <PackageReference Include="Microsoft.EntityFrameworkCore">
      <Version>1.1.0</Version>
    </PackageReference>
    <PackageReference Include="Microsoft.AspNetCore.Authentication">
      <Version>1.1.0</Version>
    </PackageReference>
    <PackageReference Include="Microsoft.AspNetCore.Authentication.Cookies">
      <Version>1.1.0</Version>
    </PackageReference>
    <PackageReference Include="Microsoft.IdentityModel.Logging">
      <Version>1.1.0</Version>
    </PackageReference>
    <PackageReference Include="Microsoft.IdentityModel.Tokens">
      <Version>5.1.0</Version>
    </PackageReference>
    <PackageReference Include="System.IdentityModel.Tokens.Jwt">
      <Version>5.1.0</Version>
    </PackageReference>
    <PackageReference Include="Microsoft.IdentityModel.Protocols">
      <Version>2.1.0</Version>
    </PackageReference>
    <PackageReference Include="Microsoft.IdentityModel.Protocols.OpenIdConnect">
      <Version>2.1.0</Version>
    </PackageReference>
    <PackageReference Include="Microsoft.AspNetCore.Authentication.OpenIdConnect">
      <Version>1.1.0</Version>
    </PackageReference>
    <PackageReference Include="Microsoft.Extensions.Configuration.Binder">
      <Version>1.1.0</Version>
    </PackageReference>
    <PackageReference Include="Microsoft.Extensions.Options.ConfigurationExtensions">
      <Version>1.1.0</Version>
    </PackageReference>
    <PackageReference Include="Microsoft.EntityFrameworkCore.InMemory">
      <Version>1.1.0</Version>
    </PackageReference>
    <PackageReference Include="Microsoft.Extensions.Options">
      <Version>1.1.0</Version>
    </PackageReference>
  </ItemGroup>
  <!--Items removed for brevity -->
  <Import Project="$(MSBuildToolsPath)\Microsoft.CSharp.targets" />
</Project>

````

@rowanmiller Do you have any ideas what might be wrong? Don't know what to try next - running out of ideas

For preview3 (csproj-based) tooling, you'll need to add the following.
<DotNetCliToolReference Include="Microsoft.EntityFrameworkCore.Tools.DotNet">
    <Version>1.0.0-msbuild1-final</Version>
</DotNetCliToolReference>

Also, I don't think the 1.1 runtime is supported on the preview3 tooling. At the least, you'll probably need to add the following package references. But even then it still may not work.
<PackageReference Include="Microsoft.EntityFrameworkCore.Design">
  <Version>1.1.0</Version>
</PackageReference>
<PackageReference Include="Microsoft.EntityFrameworkCore.Tools">
  <Version>1.0.0-msbuild1-final</Version>
</PackageReference>

@bricelam That did the trick. Unfortunately after running it the first time I can't run dotnet ef again. Get **no executable matchin 'dotnet-ef'

Yep. Definitely still a preview. Petsonally, I'm surprised to hear tha VS for Mac works at all woth MSBuild .NET Core projects.

It doesn't work as well as one had hopped though :). Struggling with referencing a Core class library (netstandard1.6) in my asp.net core web (.netcoreapp1.1).
Referencing it directly make it compile but then the assembly file cannot be found. Tried to add it to my "local nuget feed" and install it but that fails since it wants to upgrade the tooling (but fails).
Third try adding it to .csproj directly and performing dotnet clean && dotnet restore adds the nuget but cannot find the assembly.

any luck adding "Microsoft.EntityFrameworkCore.Tools.DotNet" on visual studio for mac? I am using dotnet version 1.0.0-preview3-004056

@vivek306 Yes! Paste below in ItemGroup
<DotNetCliToolReference Include="Microsoft.EntityFrameworkCore.Tools.DotNet">       <Version>1.0.0-msbuild1-final</Version>     </DotNetCliToolReference>     <PackageReference Include="Microsoft.EntityFrameworkCore.Tools.DotNet">       <Version>1.0.0-msbuild1-final</Version>     </PackageReference>         <PackageReference Include="Microsoft.EntityFrameworkCore.Tools">       <Version>1.0.0-msbuild1-final</Version>     </PackageReference>
The CLI-reference will show up as missing in solution explorer (at least for me) and dont remove it since the reference will be removed.

Great that works :).. did u have issues with AddUserSecrets? it pops up with parameter less error for ApplicationDBContext but EF works as it should when I comment that.

Havent used that tool. Can check during the day if i can get it to work. What version are you using?

it seems, what i came across is a know issue (https://stackoverflow.com/questions/40858155/ef-core-1-1-to-webapi-core-add-migration-fails) not related to EF. using the dotnet preview 3 with 1.1 runtime

For EntityFrameworkCore 2.0, I added the following line similar to what bricelam told above. It worked fine.

Thanks!

@technicalganesh - The package version is 2.0.0 (aligned with other EF Core packages) instead of 2.0.0-msbuild1-final.

If you are using Visual Studio 2017, actually you dont need "Microsoft.EntityFrameworkCore.Tools.DotNet"
instead of it  install the "Microsoft.VisualStudio.Web.CodeGeneration.Design"
From Tools > NuGet Package Manager > Package Manager Console    Run the following command
Install-Package Microsoft.VisualStudio.Web.CodeGeneration.Design


Package updates between 2018.03.06 and 2018.03.16 are skipped

In the "Newest updates" list at https://www.rdocumentation.org/trends, there appears to be a gap between 2018.03.06 and 2018.03.16 where package updates were not recorded. Pages for individual packages that were updated during that period appear to not be updated either, e.g. sunburstR which was updated on 2018.03.12
https://www.rdocumentation.org/packages/sunburstR
https://cran.r-project.org/web/packages/sunburstR/

All packages from 2018.01.01 has been reparsed, thanks for reporting


Can this be set up on bower?

http://stackoverflow.com/questions/13114781/bower-registering-local-git-package
Thanks

Fixed via #95


Mark "Needs ID" and "Research Grade" by default in new collection projects

One of the most common issues we see at help@inat is that someone has started a collection project and marked only "Casual" for Data Quality, so pretty much no observations show up in the project. Perhaps marking both "Research Grade" and "Needs ID" by default when a new collection project is created might mitigate this? I think it's worth a try.

@pleary it looks like Research is checked by default now, but not Needs ID

Looks good.


Tor Configuration

Configuration and docker compose for running Tor.
Testnode seeds to speed up connecting to network.

Looks great! Nice job.


Add maven profile to perform a CVE check using OWASP's dependency-check-maven and RH victims.

Note that currently RH victims can't fail the build (there's an open PR https://github.com/victims/maven-security-versions/pull/5  to do this).  You need to parse the output and fail if find the string CVE is found.

There is more concise way suppress the false positive than the one I chose.  It is a suppression rule based on the  Common Platform Enumeration (CPE).  https://jeremylong.github.io/DependencyCheck/general/suppression.html.  It should be possible to tell the Engine concisely that Selenium is not Opera using this method and that should reduce the size of the suppression file somewhat.  Same applies to the other misidentifications.
I'll turn off the CVE check for systemtests.  This should be just the case of setting skip on the module.
https://jeremylong.github.io/DependencyCheck/dependency-check-maven/configuration.html
It is also possible to turn off scanning of artefacts that are test scope.


MaterialSingleLineTextField

Please join MaterialSingleLineTextField TextAlign attribute, and the other Hint display

Thanks

I tried adding the TextAlign Attributes, but Hint didn't show up


When displaying edge lines without using PostProduction, the display appears distorted.

Describe the bug 📝
I want to display edge lines without using PostProduction.
I have written the following code.
const fragmentIfcLoader = new OBC.FragmentIfcLoader(this.components);
fragmentIfcLoader.settings.wasm = {
  path<EMAIL_ADDRESS>  absolute : true
};

const file = await fetch(url);
const data = await file.arrayBuffer();
const buffer = new Uint8Array(data);
const group = await fragmentIfcLoader.load(buffer, '');

this.scene.get().add(group);
this.highlighter.update();

for (let index = 0;index < group.items.length;index++) {
  const edges = new THREE.EdgesGeometry(group.items[index].mesh.geometry);
  const line = new THREE.LineSegments(edges, new THREE.LineBasicMaterial({ color : 0x000000 }));
  this.scene.get().add(line);
}

However, it results in a display like the one shown in the diagram below. (image1)
The edge lines are not displayed for each mesh as they are when displayed in BimVision.(image2)

IFC.zip
Reproduction ▶
No response
Steps to reproduce 🔢
No response
System Info 💻
System:
    OS: Windows 10 10.0.19045
    CPU: (8) x64 11th Gen Intel(R) Core(TM) i7-1185G7 @ 3.00GHz
    Memory: 7.09 GB / 15.71 GB
Binaries:
    Node: 18.15.0 - C:\Program Files\nodejs\node.EXE
    npm: 9.5.0 - C:\Program Files\nodejs\npm.CMD
Browsers:
    Edge: Spartan (44.19041.3570.0), Chromium (119.0.2151.44)
    Internet Explorer: 11.0.19041.3570

Used Package Manager 📦
npm
Error Trace/Logs 📃
No response
Validations ✅

[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Make sure this is a repository issue and not a framework-specific issue. For example, if it's a THREE.js related bug, it should likely be reported to mrdoob/threejs instead.
[X] Check that this is a concrete bug. For Q&A join our Community.
[X] The provided reproduction is a minimal reproducible example of the bug.

Three.js supports edges without postprocessing, so you don't need to rely on our library to do this. For instance, check this thread. Cheers!


apt-get install error: "E: Unable to locate package librealsense2-dkms"

Required Info

Camera Model
n/a

Firmware Version
n/a

Operating System & Version
Linux (Ubuntu 18.04)

Kernel Version (Linux Only)
4.15.0

Platform
PC

SDK Version
n/a

Language
n/a

Segment
n/a

Issue Description
No .*realsense.* packages available in the bionic repo.
To reproduce:

Issue the following commands (from the linux distribution docs):

sudo apt-key adv --keyserver keys.gnupg.net --recv-key C8B3A55A6F3EFCDE || sudo apt-key adv --keyserver hkp://keyserver.ubuntu.com:80 --recv-key C8B3A55A6F3EFCDE

sudo add-apt-repository "deb http://realsense-hw-public.s3.amazonaws.com/Debian/apt-repo bionic main" -u

sudo apt-get update

Search for anything .*realsense.*

sudo apt-cache search --names-only '.*realsense.*'

Result: <no results>
Can someone confirm that the apt repo for bionic is in working order?
Edit:
I did notice the following errors when updating the existing repo on a different machine:
E: Repository 'http://realsense-hw-public.s3.amazonaws.com/Debian/apt-repo bionic InRelease' changed its 'Origin' value from 'Freight' to 'Artifactory'
E: Repository 'http://realsense-hw-public.s3.amazonaws.com/Debian/apt-repo bionic InRelease' changed its 'Label' value from 'Freight-Release' to 'Artifactory'

Hello @matt-deboer , thanks for pointing this out.
The debian repository has been migrated during the weekend.
Now it should be fully functional, please check and update.

Thanks. I can confirm it's working now.

Hi, I'm trying to update my existing repo and am getting similar errors as above:
E: Repository 'http://realsense-hw-public.s3.amazonaws.com/Debian/apt-repo bionic InRelease' changed its 'Origin' value from 'Freight' to 'Artifactory'
E: Repository 'http://realsense-hw-public.s3.amazonaws.com/Debian/apt-repo bionic InRelease' changed its 'Label' value from 'Freight-Release' to 'Artifactory'
N: This must be accepted explicitly before updates for this repository can be applied. See apt-secure(8) manpage for details.
E: Repository 'http://realsense-hw-public.s3.amazonaws.com/Debian/apt-repo xenial InRelease' changed its 'Origin' value from 'Freight' to 'Artifactory'
E: Repository 'http://realsense-hw-public.s3.amazonaws.com/Debian/apt-repo xenial InRelease' changed its 'Label' value from 'Freight-Release' to 'Artifactory'

I am running Ubuntu 18.04 as well. Is this still from the repository migration issue?

I believe I had to remove the repo, (probably run an apt-get update), and then add it back.
Sorry I don't recall the exact steps that I performed, as my main workflow for this was inside a docker container (new repo every time).

Yep, that'll do it. Thanks!

I got this error too, so in a terminal I did a "sudo apt upgrade".  After replying "y" to its confirmation, it then updated fine:
E: Repository 'http://realsense-hw-public.s3.amazonaws.com/Debian/apt-repo xenial InRelease' changed its 'Origin' value from 'Freight' to 'Artifactory'
E: Repository 'http://realsense-hw-public.s3.amazonaws.com/Debian/apt-repo xenial InRelease' changed its 'Label' value from 'Freight-Release' to 'Artifactory'
N: This must be accepted explicitly before updates for this repository can be applied. See apt-secure(8) manpage for details.
Do you want to accept these changes and continue updating from this repository? [y/N] y

Having same issue. Any solution?


Add Apple icons and favicons

Addressed with https://github.com/Shpigford/droptune/commit/5aa2005498103aaa0cddb69a8fbf3936bc8a040d


visit water buckets

Find the optimal itinerary, given an origin waypoint (the source of water) and a list of bucket waypoints. We can only visit a fixed number of buckets before we must return to the origin waypoint to fetch more water each time.
Finishes task https://app.asana.com/0/0/1208532841592407/f

Seems like the checks have failed - check if your linters and formatters are passing


ttt

Codecov Report

:exclamation: No coverage uploaded for pull request base (ci-pr-label-test@12e0c5b). Click here to learn what that means.
 Consider uploading reports for the commit 5719072 to get more accurate results

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more

@@                 Coverage Diff                 @@
##             ci-pr-label-test      #15   +/-   ##
===================================================
  Coverage                    ?   55.29%
===================================================
  Files                       ?       63
  Lines                       ?    10359
  Branches                    ?        0
===================================================
  Hits                        ?     5728
  Misses                      ?     4126
  Partials                    ?      505


Avoid assignments and conversions to/from proxy references in block/c…

…opy & stable_merge_sort
This avoids default-constructing execution policies in thrust::reference when calling
merge sort with a user-defined execution policy.
Fixes #793

@egaburov could you review this and see if it comprehensively fixes the issue? We might also want to add a test case for this in the unit tester.

Thanks Jared. I will test the fix and add the unit test.

Go ahead and merge. The unit tests and examples compiled and run successfully. I will create later a sperate PR with unit test for this functionality.


Bit Manipulation (Basics) | GSSOC 2023

Hello @aaryahjolia 👋,
I want to contribute into your repository under GSSOC '23.
I want to add some content related to basics of BIT MANIPULATION operations with questions like (AND , OR, NOT, Check ith bit set or not) (Code + Diagram and complete explanation).
I will make sure about:

Quality of content.
Easy and Clean Code
Diagrammatic explanation

My leetcode profile for your reference: https://leetcode.com/ashu012002/
Please assign me this issue, I will do my best.

Please go ahead!

Thanku so much @aaryahjolia


Retrieve dispute resolution message in order_messages for moderator

When close_dispute is called, the resolution value is not retrieved by order_messages for the moderator, so the moderator can't see their own resolution message.

Link to the Client issue: https://github.com/OpenBazaar/OpenBazaar-Client/issues/932


Not getting chat messages

Describe the bug
I am trying to get chat messages from the watch.
Therefore I just used the sample main.py and changed print(xplora.getUserName()) to print(xplora.getWatchChatsRaw('theRealWuid'))
I am getting the following error message. (I tried several variants: ...getWatchChatsRaw('theRealWuid', 3, 2, "5") and ...0, 0, ""))
Traceback (most recent call last):
File "/root/pyxplora_api-2.9.0/sample/main.py", line 28, in
main()
File "/root/pyxplora_api-2.9.0/sample/main.py", line 24, in main
print(xplora.getWatchChatsRaw('theRealWuid'))
File "/usr/local/lib/python3.9/dist-packages/pyxplora_api/pyxplora_api.py", line 340, in getWatchChatsRaw
result = ChatsNew.from_dict(result.get("chatsNew", None))
File "/usr/local/lib/python3.9/dist-packages/dataclasses_json/api.py", line 72, in from_dict
return _decode_dataclass(cls, kvs, infer_missing)
File "/usr/local/lib/python3.9/dist-packages/dataclasses_json/core.py", line 152, in _decode_dataclass
types = get_type_hints(cls)
File "/usr/lib/python3.9/typing.py", line 1417, in get_type_hints
value = _eval_type(value, base_globals, localns)
File "/usr/lib/python3.9/typing.py", line 283, in _eval_type
return t._evaluate(globalns, localns, recursive_guard)
File "/usr/lib/python3.9/typing.py", line 539, in _evaluate
eval(self.forward_code, globalns, localns),
File "", line 1, in
TypeError: unsupported operand type(s) for |: 'types.GenericAlias' and 'NoneType'
To Reproduce
with every execution
Expected behavior
getting the chat data

Hello @phil1283, thanks for the report. You are using Python3.9, the version of the lib is compatible from Python3.10.

Thanks @Ludy87, now the error message does not appear anymore!
But I get an empty list, regardless what options I choose.
Any hints for me?
Examples:
print(xplora.getWatchChatsRaw('theRealWuid', 0, 20, "1", True))

{'list': []}
print(xplora.getWatchChats('theRealWuid', 0, 20, "1"))
[]


Implement a way to add an Observation to a FHIR bundle

User Story
As ReportStream, I want the ability to add Observation resources to a FHIR bundle, so that I can add additional information needed for receivers.
Description/Use Case
The RADx MARS HL7 v2 format expects an OBX segment with the patient's age. To accomplish this we need to add an Observation to the FHIR bundle to be able to map that correctly to the HL7 message.
Risks/Impacts/Considerations
RADx MARs messages will not contain the age OBX segment.
Dev Notes

The OBX segment could be created as part of the FHIR to HL7 transforms, but it can be hard since the RADx MARS format expects this to be mapped to the 3rd OBX segment.
This could be added functionality to the sender transforms, but this will cause every receiver to have that additional Observation.
Another option, is to create a custom FHIR path function that returns an Observation.

Acceptance Criteria

[ ] An observation can be added to a bundle

@victor-chaparro Needs further grooming.


cloudinit.GenerateLocalData: minor refactoring

This change fixes two cloudinit.GenerateLocalData issues raised by @ezrasilvera. It drops a needless files variable, and it defers removal of files right after they are created.
Signed-off-by: Dan Kenigsberg<EMAIL_ADDRESS>NONE

/lgtm

/lgtm

/approve
/retest

/approve
/retest


Offline validation of attestations from GitHub's private attestation service

Hi,
I'm wanting to validate the attestations provided by GitHub for artifacts built in a private repository. I would like to do this validation as part of a Rust program.
I came across https://github.com/actions/attest-build-provenance/issues/162, and some merged PRs to this repo that seemed to be making progress towards making this possible in Rust.
I'm curious about the status of validating these new bundle formats, and the gap between sigstore-rs and being able to do this within a Rust program. And, if it is a "good-first-issue" type of task, I'd be happy to help.
Thank you!

We're actually also interested in this!

My understanding is that this is basically https://github.com/sigstore/sigstore-rs/issues/280

@tnytown thank you for the reply! This is very informative.
I have tested to load a v0.3 generated attestation (by Github) yesterday. Verification failed at DSSE not implemented yet. Is it correct that this part should be not too hard (ie. could it be a good first issue to get the feet wet?). I assume it would be easiest to look at the Python implementation as a reference?
Cheers!


chore: add optional API to make tracing level changes "wait-able"

This change adds several *_and_wait() method options to the ApplicationTelemetryClient type. When our services boot up we check the parsed CLI argument for verbosity flags. If there are more than one set then we issue a command to raise the tracing level but prior to this change, this operation was non-blocking/async. That means that the level may not have raised by the time the next line of code executes resulting in potential missing log messages.

bors merge


Support multiple class-name requirements

I think it's valid CSS to have something like:
a.x.y { color: red; }

where it only matches
<a class="x y">...

But the only way to do this here is to "hack" the class name, like so:
a &. ClassName "x.y" ? Rule.do color := red

I was hoping something like:
a &. (ClassName "x"  /\ ClassName "y") ...

or
a &. (ClassName "x"  <> ClassName "y") ...

might work? thoughts? am i missing the right way to do this?

Hi @silky, here's how to append multiple class names to a selector:
a &. ClassName "x" &. ClassName "y" ? Rule.do
  color := rgb 255 0 0

Result:
a.x.y {
  color: hsl(0.0, 100.0%, 50.0%);
}

ah i see; thanks @nsaunders ! :)

Certainly, please let me know if you need anything else!


Error about SRE-Example-17_deferred-shading

Hi,
I think SRE is a great project!  But when I try to run SRE-Example-17_deferred-shading, I got the error message like this
OpenGL version 3.3.0 NVIDIA 384.130 (3.3)
sre version 1.1.4
SRE Error: /home/xhg/SimpleRenderEngine/src/sre/ModelImporter.cpp:82 in getFileContents()
Error reading examples_data/sponza/sponza.obj. Error code: 2
RenderPass
GL_INVALID_ENUM

By the way, my operating system is Ubuntu 16.04.

Sorry for my careless, it is about that the filename of texture is sensitive which can not match with .mtl file


Add support for APFS Fillesystem

We would appreciate it if anyone with additional materials or actual dump files related to this could share them :D
tsk_recover supports this.

https://en.wikipedia.org/wiki/Apple_File_System
https://developer.apple.com/support/downloads/Apple-File-System-Reference.pdf

WIP: https://github.com/ReFirmLabs/binwalk/tree/apfs_support

APFS support is functional and merged into the master branch.
Note that tsk_recover was not able to actually extract any of the APFS images that I created (using both Linux utilities and the OSX disk manager on a MacBook). The latest version of 7zip does work though, and has been added as a new external dependency.

Thank you very much!!


feat: add docs and iconFileName for alert action

Implements #1105.

The PR was split into 2 pieces, closing this one.

This PR is split into PR #1133 and #1134.


Update pin and add pin-slash

Continue #23531
Thanks for the update in https://github.com/primer/octicons/issues/940, @CameronFoxly

It seems that CI failure is related. Wait a moment please.

I see. We need to update the version of primer/octicons then use make svg to create the svg file.

It is ready now. 😄


WIP: Load balance Lua scripts

fixes #382

Currently missing:
Testing of scheduling logic in vmq_diversity_script
Add tests for reloading scripts
Add changelog entry


Add support of the function parametric for ClickHouse dialect

This closes #1301

@iffyio Thanks for your review, all comments are resolved now.

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

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

Details

67 of 68 (98.53%)  changed or added relevant lines in 12 files are covered.
1510 unchanged lines in 10 files lost coverage.
Overall coverage increased (+0.1%) to 89.008%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/parser/mod.rs
12
13
92.31%

Files with Coverage Reduction
New Missed Lines
%

src/lib.rs
1
12.64%

src/parser/alter.rs
2
66.67%

tests/sqlparser_sqlite.rs
4
98.36%

src/dialect/mod.rs
5
72.08%

tests/sqlparser_snowflake.rs
16
98.07%

src/ast/dml.rs
42
73.47%

tests/sqlparser_bigquery.rs
122
90.18%

src/ast/mod.rs
275
81.49%

src/parser/mod.rs
421
93.21%

tests/sqlparser_common.rs
622
89.6%

Totals

Change from base Build<PHONE_NUMBER>:
0.1%

Covered Lines:
26276

Relevant Lines:
29521

💛  - Coveralls

Thanks again @git-hulk  and @iffyio

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

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

Details

67 of 68 (98.53%)  changed or added relevant lines in 12 files are covered.
1510 unchanged lines in 10 files lost coverage.
Overall coverage increased (+0.1%) to 89.008%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/parser/mod.rs
12
13
92.31%

Files with Coverage Reduction
New Missed Lines
%

src/lib.rs
1
12.64%

src/parser/alter.rs
2
66.67%

tests/sqlparser_sqlite.rs
4
98.36%

src/dialect/mod.rs
5
72.08%

tests/sqlparser_snowflake.rs
16
98.07%

src/ast/dml.rs
42
73.47%

tests/sqlparser_bigquery.rs
122
90.18%

src/ast/mod.rs
275
81.49%

src/parser/mod.rs
421
93.21%

tests/sqlparser_common.rs
622
89.6%

Totals

Change from base Build<PHONE_NUMBER>:
0.1%

Covered Lines:
26276

Relevant Lines:
29521

💛  - Coveralls


[NEW LIGHT] Adafruit M4 Express / NeoTrellis

If you would like BusyLight to support a new device, please provide as much of the following as possible.

Product Name: Adafruit M4 Express Feather / NeoTrellis
Vendor URL:  https://www.adafruit.com
Purchase URL: https://www.adafruit.com/product/3857
Public documentation URLs:

I have one of these built and I've been writing some Circuit Python on it and I've started work on adapting the trinket code for the neotrellis.  I opened this issue to start a discussion about whether any changes to busylight would be necessary

Interesting. Just skimming the docs for those devices, I imagine that BusyLight would be on the M4 controlling the lights which are either accessed via GPIO or I2C. BusyLight currently support USB HID and serial "backends" via busylight.lights.USBLight and busylight.lights.SerialLight.  So I guess we would want to add busylight.lights.I2CLight and possibly busylight.lights.GPIOLight (I think your intent is support for NeoTrellis attached via I2C according to the docs, so GPIO might just be a nice to have but not necessary).
I think my biggest concern is light discovery; both HIDAPI and USBSerial have the ability to query available devices and I've spent a lot of time on abstracting the Light API to make it usable without having to know the specifics of a connected device. It might be that I2C/GPIO breaks some of that ease of use, but presumably people using the M4/NeoTrellis devices are a little more technically savvy and up to the task of knowing what lights are available a priori and what "flavor" of device is connected.
I'm not opposed to supporting this combination, but I'll have to spin up on I2C/CircuitPython/etc or have some really good pull requests to work with :)

Well, I haven't really been able to dig into all the magic in busylight yet but I was thinking that on the M4 itself the code could be pretty much this https://github.com/freemansoft/Adafruit-Trinkey-CircuitPython or something similar.  BusyLight would just have to be able to detect the device was present (HID) and send it signals over... serial console? I'm not sure, actually.
I've got CircuitPython on my M4/NeoTrellis now that plays animated 4x4 sequences when you press its own buttons and "types" things as if it was a keyboard.  I just need to have some way of sending it messages from the host to trigger lights / sequences.
It could be that it's not a great fit for the model you've already been working with but I'm curious to try and get something working.

I suspect, for your application, BusyLight is overkill as it is essentially "wallpaper" over the weirdness of talking to USB devices (HID and serial) and the wildly disparate command architectures of various commercial lights. I don't know how your NeoTrellis is connected physically to your M4, but my suspicion is via the I2C bus and not a USB connection. A brief survey of this article seems to indicate that scanning an I2C bus for devices and writing to them is relatively simple.
That said, I'm still willing to entertain the idea of adding I2C support to BusyLight. I've got a Feather lying around somewhere, just need to acquire a NeoTrellis to play with.

One thing just occurred to me. Most of the lights supported by BusyLight don't permit individual access to component lights and so the method busylight.light.Light.on((R, G, B)) turns the light on with color tuple (R, G, B).  There is a precedent for specific lights supporting LED addressability; busylight.light.luxafor.Flag family of lights for instance have a leds attribute that controls which LEDs are turned on and off. IIRC the BlickStick family also has addressable LEDs, but BusyLight treats it as just one light as well.
All this to say, the BusyLight model might not give you the ease of use you were looking for (at least not right away).

You're right, I didn't think about the discoverability aspect of it.  This
particular device probably isn't well suited for busylight because you'd
have to have certain python running on it and configure the serial port
etc.  I'll keep tinkering with it separately.
Thanks!
Andy Watson
https://www.linkedin.com/in/andrewwatson/
On Wed, May 31, 2023 at 5:54 PM Erik OShaughnessy @.***>
wrote:

One thing just occurred to me. Most of the lights supported by BusyLight
don't permit individual access to component lights and so the method busylight.light.Light.on((R,
G, B)) turns the light on with color tuple (R, G, B). There is a
precedent for specific lights supporting LED addressability;
busylight.light.luxafor.Flag family of lights for instance have a leds
attribute that controls which LEDs are turned on and off. IIRC the
BlickStick family also has addressable LEDs, but BusyLight treats it as
just one light as well.
All this to say, the BusyLight model might not give you the ease of use
you were looking for (at least not right away).
—
Reply to this email directly, view it on GitHub
https://github.com/JnyJny/busylight/issues/270#issuecomment-1571013856,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AABMY6RW3OMKIX4TE2Y4LWDXI642VANCNFSM6AAAAAAYU2SYJU
.
You are receiving this because you authored the thread.Message ID:
@.***>


fix database error when attempting to delete a user

error:
Database Error error: update or delete on table "users" violates foreign key constraint "trips_user_id_fkey" on table "trips"

make the delete call recursive

ALTER TABLE trips
DROP CONSTRAINT trips_user_id_fkey,
ADD CONSTRAINT trips_user_id_fkey FOREIGN KEY (user_id)
REFERENCES users(user_id) ON DELETE SET NULL;


exception on loading config

(node:1696) UnhandledPromiseRejectionWarning: TypeError: Key is missing or incorrect.
at new t.exports (/usr/lib/node_modules/homebridge-eufy-robovac/dist/webpack:/node_modules/eufy-robovac/dist/index.js:1:13622)
at new t (/usr/lib/node_modules/homebridge-eufy-robovac/dist/webpack:/node_modules/eufy-robovac/dist/index.js:1:5798)
at t. (/usr/lib/node_modules/homebridge-eufy-robovac/dist/webpack:/src/index.ts:80:18)
at /usr/lib/node_modules/homebridge-eufy-robovac/dist/webpack:/webpack/bootstrap:83:1
at Object.next (/usr/lib/node_modules/homebridge-eufy-robovac/dist/webpack:/webpack/bootstrap:83:1)
at /usr/lib/node_modules/homebridge-eufy-robovac/dist/webpack:/webpack/bootstrap:83:1
at new Promise ()
at r (/usr/lib/node_modules/homebridge-eufy-robovac/dist/webpack:/webpack/bootstrap:83:1)
at t.setup (/usr/lib/node_modules/homebridge-eufy-robovac/dist/webpack:/src/index.ts:79:2)
at new t (/usr/lib/node_modules/homebridge-eufy-robovac/dist/webpack:/src/index.ts:76:8)
at /usr/lib/node_modules/homebridge/src/server.ts:356:50
at Array.forEach ()
at Server._loadAccessories (/usr/lib/node_modules/homebridge/src/server.ts:329:29)
at Server.start (/usr/lib/node_modules/homebridge/src/server.ts:155:12)
at cli (/usr/lib/node_modules/homebridge/src/cli.ts:80:10)
at Object. (/usr/lib/node_modules/homebridge/bin/homebridge:17:22)
at Module._compile (internal/modules/cjs/loader.js:1133:30)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:1153:10)
at Module.load (internal/modules/cjs/loader.js:977:32)
at Function.Module._load (internal/modules/cjs/loader.js:877:14)
at Function.executeUserEntryPoint [as runMain] (internal/modules/run_main.js:74:12)
at internal/main/run_main_module.js:18:47
(node:1696) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag --unhandled-rejections=strict (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
(node:1696) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

It's un-clear where this error was coming from.
However, as of this writing, IP address is no longer supported (README will be updated shortly).  You need to use deviceId, so your config.json `accessories' block needs to have an entry that looks like this:
{
  "accessory": "Eufy RoboVac",
  "name": "Vacuum Cleaner",
  "deviceId": "<your devId>",
  "localKey": "<your localKey>"
},

Instructions to get devId (called deviceId in the plugin config) and localKey are here
Sometime today, I will be adding a config.schema.json to the plugin so that it can be setup use the homebridge-ui.  May also look into making getting deviceId and localKey a bit easier.
If you are confident your config.json is setup correctly an this plugin is still not working, please re-open this issue.

Hi,
I guess i grabbed the wrong lockey.  For whatever reason logcat does not
return the search string you provided in the instructions.  any clues
there?  I've tried various strings that appeared to be lockey's in the adb
log but not having much luck...
On Sat, May 23, 2020 at 11:59 PM apexad<EMAIL_ADDRESS>wrote:

Closed #10
https://github.com/joshstrange/homebridge-eufy-robovac/issues/10.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/joshstrange/homebridge-eufy-robovac/issues/10#event-3367456251,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AHU6JNF7KVGYE5KIIRM3FI3RTBBK3ANCNFSM4NHDUMIA
.

Hi, I guess i grabbed the wrong lockey. For whatever reason logcat does not return the search string you provided in the instructions. any clues there? I've tried various strings that appeared to be lockey's in the adb log but not having much luck...
…

You may have to install EufyHime 2.3.2 via apk since it seems new versions no longer output the information.


cant initialize workspace (wurstscript problem?)

This is the continuation of peq/wurst4vscode#23
problem still exists.
Wurst0 log:
2017-06-27 22:30:38 INFO   ### Started wurst version: (<IP_ADDRESS>-jenkins-Wurst-342)
2017-06-27 22:30:38 INFO   ### With wurst-args -languageServer

VScode console log when I open VScode:
/C:/Program Files (x86)/Microsoft VS Code/resources/app/out/vs/workbench/electron-browser/workbench.main.js:29 [Extension Host] Wurst extension activated!!
/C:/Program Files (x86)/Microsoft VS Code/resources/app/out/vs/workbench/electron-browser/workbench.main.js:29 [Extension Host] Server started 10668!
/C:/Program Files (x86)/Microsoft VS Code/resources/app/out/vs/workbench/electron-browser/workbench.main.js:29 [Extension Host] setup file logging
/C:/Program Files (x86)/Microsoft VS Code/resources/app/out/vs/workbench/electron-browser/workbench.main.js:29 [Extension Host] stderr: Exception in thread "main"
/C:/Program Files (x86)/Microsoft VS Code/resources/app/out/vs/workbench/electron-browser/workbench.main.js:29 [Extension Host] stderr: java.lang.ClassCastException: [Ljava.lang.Object; cannot be cast to [Ljava.lang.String;
/C:/Program Files (x86)/Microsoft VS Code/resources/app/out/vs/workbench/electron-browser/workbench.main.js:29 [Extension Host] stderr:
	at de.peeeq.wurstio.Main.main(Main.java:65)
/C:/Program Files (x86)/Microsoft VS Code/resources/app/out/vs/workbench/electron-browser/workbench.main.js:29 [Extension Host] stderr:

/C:/Program Files (x86)/Microsoft VS Code/resources/app/out/vs/workbench/electron-browser/workbench.main.js:29 [Extension Host] child process exited with code 1
/C:/Program Files (x86)/Microsoft VS Code/resources/app/out/vs/workbench/electron-browser/workbench.main.js:29 This socket has been ended by the other party: Error: This socket has been ended by the other party
    at Socket.writeAfterFIN [as write] (net.js:294:12)
    at Promise (C:\Users\vital\.vscode\extensions\peterzeller.wurst-0.0.13\out\WurstServer.js:225:39)
    at WurstServer.sendRequest (C:\Users\vital\.vscode\extensions\peterzeller.wurst-0.0.13\out\WurstServer.js:213:16)
    at WurstHoverProvider.provideHover (C:\Users\vital\.vscode\extensions\peterzeller.wurst-0.0.13\out\features\hoverProvider.js:8:32)
    at c:\Program Files (x86)\Microsoft VS Code\resources\app\out\vs\workbench\node\extensionHostProcess.js:23:352279
    at c:\Program Files (x86)\Microsoft VS Code\resources\app\out\vs\workbench\node\extensionHostProcess.js:23:57373
    at new n.Class.derive._oncancel (c:\Program Files (x86)\Microsoft VS Code\resources\app\out\vs\workbench\node\extensionHostProcess.js:23:46346)
    at Object.d [as asWinJsPromise] (c:\Program Files (x86)\Microsoft VS Code\resources\app\out\vs\workbench\node\extensionHostProcess.js:23:57336)
    at e.provideHover (c:\Program Files (x86)\Microsoft VS Code\resources\app\out\vs\workbench\node\extensionHostProcess.js:23:352233)
    at c:\Program Files (x86)\Microsoft VS Code\resources\app\out\vs\workbench\node\extensionHostProcess.js:23:362450
e.onUnexpectedError @ /C:/Program Files (x86)/Microsoft VS Code/resources/app/out/vs/workbench/electron-browser/workbench.main.js:29

When I try to open a map using VScode, I get:
shell.ts:445 This socket has been ended by the other party: Error: This socket has been ended by the other party
    at Socket.writeAfterFIN [as write] (net.js:294:12)
    at Promise (C:\Users\vital\.vscode\extensions\peterzeller.wurst-0.0.13\out\WurstServer.js:225:39)
    at WurstServer.sendRequest (C:\Users\vital\.vscode\extensions\peterzeller.wurst-0.0.13\out\WurstServer.js:213:16)
    at WurstServer.startMapIntern (C:\Users\vital\.vscode\extensions\peterzeller.wurst-0.0.13\out\WurstServer.js:268:55)
    at mapPromise.then.path (C:\Users\vital\.vscode\extensions\peterzeller.wurst-0.0.13\out\WurstServer.js:264:25)
    at Object.m [as _notify] (c:\Program Files (x86)\Microsoft VS Code\resources\app\out\vs\workbench\node\extensionHostProcess.js:23:39252)
    at Object.enter (c:\Program Files (x86)\Microsoft VS Code\resources\app\out\vs\workbench\node\extensionHostProcess.js:23:42826)
    at n.Class.derive._oncancel._run (c:\Program Files (x86)\Microsoft VS Code\resources\app\out\vs\workbench\node\extensionHostProcess.js:23:44654)
    at n.Class.derive._oncancel._completed (c:\Program Files (x86)\Microsoft VS Code\resources\app\out\vs\workbench\node\extensionHostProcess.js:23:44095)
    at c:\Program Files (x86)\Microsoft VS Code\resources\app\out\vs\workbench\node\extensionHostProcess.js:23:57805
e.onUnexpectedError	@	shell.ts:445
(anonymous)	@	shell.ts:405
e.onUnexpectedError	@	errors.ts:68
o	@	errors.ts:88
(anonymous)	@	winjs.base.js:43
(anonymous)	@	winjs.base.js:38
winjs.base.js:45 WARNING: Promise with no error callback:69
winjs.base.js:46
Object
error
:
Error: This socket has been ended by the other party at Socket.writeAfterFIN [as write] (net.js:294:12) at Promise (C:\Users\vital\.vscode\extensions\peterzeller.wurst-0.0.13\out\WurstServer.js:225:39) at WurstServer.sendRequest (C:\Users\vital\.vscode\extensions\peterzeller.wurst-0.0.13\out\WurstServer.js:213:16) at WurstServer.startMapIntern (C:\Users\vital\.vscode\extensions\peterzeller.wurst-0.0.13\out\WurstServer.js:268:55) at mapPromise.then.path (C:\Users\vital\.vscode\extensions\peterzeller.wurst-0.0.13\out\WurstServer.js:264:25) at Object.m [as _notify] (c:\Program Files (x86)\Microsoft VS Code\resources\app\out\vs\workbench\node\extensionHostProcess.js:23:39252) at Object.enter (c:\Program Files (x86)\Microsoft VS Code\resources\app\out\vs\workbench\node\extensionHostProcess.js:23:42826) at n.Class.derive._oncancel._run (c:\Program Files (x86)\Microsoft VS Code\resources\app\out\vs\workbench\node\extensionHostProcess.js:23:44654) at n.Class.derive._oncancel._completed (c:\Program Files (x86)\Microsoft VS Code\resources\app\out\vs\workbench\node\extensionHostProcess.js:23:44095) at c:\Program Files (x86)\Microsoft VS Code\resources\app\out\vs\workbench\node\extensionHostProcess.js:23:57805
exception
:
null
handler
:
undefined
id
:
69
parent
:
undefined
promise
:
n.Class.derive._oncancel
__proto__
:
Object

when I try to clean wurst workspace, I get:
shell.ts:445 This socket has been ended by the other party: Error: This socket has been ended by the other party
    at Socket.writeAfterFIN [as write] (net.js:294:12)
    at Promise (C:\Users\vital\.vscode\extensions\peterzeller.wurst-0.0.13\out\WurstServer.js:225:39)
    at WurstServer.sendRequest (C:\Users\vital\.vscode\extensions\peterzeller.wurst-0.0.13\out\WurstServer.js:213:16)
    at WurstServer.clean (C:\Users\vital\.vscode\extensions\peterzeller.wurst-0.0.13\out\WurstServer.js:230:61)
    at vscode.Disposable.from.vscode.commands.registerCommand (C:\Users\vital\.vscode\extensions\peterzeller.wurst-0.0.13\out\features\commands.js:5:169)
    at t.$executeContributedCommand (c:\Program Files (x86)\Microsoft VS Code\resources\app\out\vs\workbench\node\extensionHostProcess.js:23:330741)
    at t.e.handle (c:\Program Files (x86)\Microsoft VS Code\resources\app\out\vs\workbench\node\extensionHostProcess.js:23:312304)
    at s (c:\Program Files (x86)\Microsoft VS Code\resources\app\out\vs\workbench\node\extensionHostProcess.js:23:176531)
    at h (c:\Program Files (x86)\Microsoft VS Code\resources\app\out\vs\workbench\node\extensionHostProcess.js:23:177208)
    at _combinedTickCallback (internal/process/next_tick.js:67:7)
e.onUnexpectedError	@	shell.ts:445
(anonymous)	@	shell.ts:405
e.onUnexpectedError	@	errors.ts:68
o	@	errors.ts:88
(anonymous)	@	winjs.base.js:43
(anonymous)	@	winjs.base.js:38
winjs.base.js:45 WARNING: Promise with no error callback:71
winjs.base.js:46
Object
error
:
Error: This socket has been ended by the other party at Socket.writeAfterFIN [as write] (net.js:294:12) at Promise (C:\Users\vital\.vscode\extensions\peterzeller.wurst-0.0.13\out\WurstServer.js:225:39) at WurstServer.sendRequest (C:\Users\vital\.vscode\extensions\peterzeller.wurst-0.0.13\out\WurstServer.js:213:16) at WurstServer.clean (C:\Users\vital\.vscode\extensions\peterzeller.wurst-0.0.13\out\WurstServer.js:230:61) at vscode.Disposable.from.vscode.commands.registerCommand (C:\Users\vital\.vscode\extensions\peterzeller.wurst-0.0.13\out\features\commands.js:5:169) at t.$executeContributedCommand (c:\Program Files (x86)\Microsoft VS Code\resources\app\out\vs\workbench\node\extensionHostProcess.js:23:330741) at t.e.handle (c:\Program Files (x86)\Microsoft VS Code\resources\app\out\vs\workbench\node\extensionHostProcess.js:23:312304) at s (c:\Program Files (x86)\Microsoft VS Code\resources\app\out\vs\workbench\node\extensionHostProcess.js:23:176531) at h (c:\Program Files (x86)\Microsoft VS Code\resources\app\out\vs\workbench\node\extensionHostProcess.js:23:177208) at _combinedTickCallback (internal/process/next_tick.js:67:7)
exception
:
null
handler
:
undefined
id
:
71
parent
:
undefined
promise
:
n.Class.derive._oncancel
__proto__
:
Object

I see that 343 version is building, so I will check it in 10 minutes. maybe problem disappears

after 343 build now it completely works wothout any errors!
many thanks

There is still a bug, that runmap can't be used because of access denied to WurstRunMap, but yeh, the other bug should be fixed.

I ran the map without errors.

good.


Reset session when an error occurs

Should probably need a dedicated UI component for handling error messages, such as a flash alert/toast
When the prompt fails undo the last prompt into prompt field
Should implement these tests.

:tada: This issue has been resolved in version 0.3.8 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


MaxFileSize not working

I am running the server in a kubernetes statefulset.
Generally the upload is working. The problem is that the MaximumFileSize I set doesn´t seem to have any affect.
I also understand that this error should be Logged which it isn´t.
time="2021-04-08T07:26:13Z" level=info msg="starting up simple-upload-server" time="2021-04-08T07:26:13Z" level=info msg="start listening" cors=false ip=<IP_ADDRESS> port=25478 root=/var/root token=<yes> upload_limit=72118430
The server returns this:
(413) Request Entity Too Large.
the file size is around 7500Kb so the upload size I set should be plenty enough. I have tried several diffrent upload sizes.
I don´t know much about go but as my upload size is logged correctly I figure it probably parses correctly as well.
Btw. it would be great to have support for docker exec :)

Sorry for late reply, and thank you for your reporting :)
As the log shows, MaxUploadSize (-upload_limit) seems to be set correctly.

time="2021-04-08T07:26:13Z" level=info msg="start listening" cors=false ip=<IP_ADDRESS> port=25478 root=/var/root token=<yes> upload_limit=72118430

The request is logged with message "file size exceeded" when this app rejects the request due to the size limit.
If you can't find that message, the request is not reached to this app.
You wrote that you are trying to run this app on k8s, so there might be Ingress controller like ingress-nginx. It has the limit for the uploaded body size which is independent of this app's limit. You may have to modify its configuration.

Yes, thanks fro the reply. It was the Ingress


Connect --watch option with other plugin?

get-schema --watch is a really awesome concept, but on it's own not very useful.
It would be awesome if codegen plugings could hook into it to regenerate code on a schema update.
Wdyt?

Sounds like a great idea. Could you propose a concrete design/implementation that we can discuss?

How about this simple solution: Add a parameter -c that specifies a (sub)command to be run on every change (just like chokidar-cli). E.g.
get-schema dev --watch -c codegen

is the equivalent of running graphql codegen on every update (but more efficient because the plugin is already loaded in memory etc). To pass more arguments, just put quotes around it
get-schema --watch -c "codegen --whatever"

An alternative syntax that does the same to consider would be to use -- to separate the arguments:
get-schema --watch -- codegen --whatever

I like this idea. Could you create a PR?

Could graphql-cli implement a similar event system to serverless plugins? That way, even completely independent and external plugins can hook into each others events to take further action. In this case, the codegen plugin could hook into an event raised by get-schema when a new schema is available.

I think this is a great idea @kbrandwijk! Do you want to create a new issue with a design proposal?

See https://github.com/graphql-cli/graphql-cli/issues/73 for a proposal on this subject.


SBT should respond gracefully on unsupported JDK versions

SBT currently throws an exception and terminates when started using JDK9, working fine with JDK8. SBT should detect the JDK version and terminate gracefully if it is known not work on that JDK version.

Can you detail what exception you're seeing please?

@dwijnand See #2060.
[error] scala.reflect.internal.MissingRequirementError: object java.lang.Object in compiler mirror not found.

this ticket is obsolete now that JDK 9 is supported, yes?

Yes. Let's close it.


[otns] Add default implementation for otPlatOtnsStatus

This PR adds a default implementation for otPlatOtnsStatus, which emits OTNS status messages to log, so that OTNS=1 could be used with real devices. This is required for the Silk-OTNS integration work, as Silk will pick up these messages and reroute them to OTNS for visualization purposes.

Running OT_OPTIONS=-DOT_READLINE=OFF VIRTUAL_TIME=0 NODE_MODE=rcp ./script/test clean build expect seems to pass locally


Use dependabot to keep docker images up to date

See https://docs.github.com/en/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/configuration-options-for-dependency-updates#package-ecosystem

I have to make sure this is possible with Docker images. We should use specific tags and not generic ones (like latest). I have to study if this best practice is compatible with dependabot.

I would prefer to use the latest within a certain major version. For packages it's a different thing, but for runtime images using for example Node 16 latest is safe enough.

In that case, I don't think we need dependabot for keeping images up to date, as the CI/CD workflow will always pull the most recent image from tags like node:16-alpine. Unless we want dependabot to trigger the workflow when a new version of the base image is published under that tag. What do you think?

No not really, we don't want to trigger a deployment when a new version is published under that tag, we are happy that whenever we deploy it will use whatever version is linked to that tag. Then I guess we can decide to close this issue.

In that case, we'd better go without dependabot and leave the decision of deploying in the devs hands through a PR.
Just for the record, I've found out that following Docker tagging best practices is compatible with dependabot: https://dev.to/oracle2025/how-to-keep-a-dockerfile-updated-with-dependabot-1mdn

As a known drawback for using generic tags instead of full version pnes, we won't be able to produce reproducible builds.

True but Node is an extremely stable framework, so stable that in fact I would expect most applications to work flawlessly across major versions. Hence I think we can accept the compromise of using whatever latest version 16.


Remove subdue for sense-check

remove subdue as our sensu infrastructure does not support it yet

Please add description to PR

@nirajdp76 I updated the description


Allow big inline edit per item

Hi,
is there any posibility to disable (not draw) edit button per row?
In my this case based on acl and property of the item itself.
I've tried allow action callback without any luck.
$grid->allowRowsAction('inlineEdit', function ($item) {             return //false;         });

It is not (yet). Adding this to v4.1.


Support attachments

Vbulletin & mybb support attachments (on Postings)- it would be nice if we could import them.

Hey @akhoury, while you're working on getting it to work for 0.8.x, are you doing that refactor you were talking about before your break? I've been holding off any PR's for more functionality I was hoping to add.

hmm - nodebb support attachments on posts?

and I reverted a lot of my refactor-changes, I changed my mind on few things, I think I'm gonna use promises to avoid the horrible callback nesting I am doing now.
btw, 0.8.2 is supported on master now, i just have to do more testing before I release.
If you have a "small" PR, I can merge in,

That's the problem, judging by my last pr, I didn't think adding a new type of import was going to be "small" at all, so I was waiting for a refactor. Using Promises sounds like a good pattern, dealing with all those callbacks was... fun :)
The attachments functionality was pretty simple, it's just a MD link that points to the uploaded file. I'm not sure it can get / we want it to get more complicated than that.

it's just a MD link

I think it should be an HTML anchor - this way it's compatible with BBCode and MD - then the import-user have the option to convert either to MD via the post-import tools.

that points to the uploaded file

Does that mean the files would need to stay where they are - what if we copy then down to nodebb's public dir, i..e. /public/attachments/_pid_attachment_index.extension
I don't know.. just thinking out loud.
As for the refactor, I am crazy busy, like buried with backlog work, I need to be trapped alone somewhere with a laptop for 186.32 years to be done - maybe I will do it once NodeBB 1.0 is out, you know for the celebration.

I think it should be an HTML anchor

Good call, I agree

Does that mean the files would need to stay where they are - what if we copy then down to nodebb's public dir

Possible, Was just thinking of ways to minimize IO if we can just include in the instructions to put the folder in the right spot

I say, just transfer them as anchors - it might require some HTTP server re-routing knowledge to get them to work right, and it someone insists on moving them into the nodebb/public folder they can, then with some regex, they re-iterate over the whole db, search and replace.
option-1
Use the parseBefore() (or parseAfter()) advanced-option in the Post-Import Tools, where you write your own javascript to edit the content of each post content, then select the "Dont touch my content", that will iterate over all posts (or whatever records you choose and execute your javascript)
Old-screenshot but same idea:
https://cloud.githubusercontent.com/assets/1398375/4211624/ac24a21e-388c-11e4-989e-230855a3f116.png
Option-2
Write your own script to edit the data, something like this.
       // assuming you're in NodeBB/node_modules/nodebb-plugin-import/server

        var Data = require("./data.js");
        var Posts = require('../../../src/posts.js');

        Data.eachPost(
            function(post, next) {
                 var newContent = post.content.replace(/apples/, 'oranges'); // or you can use the original post. _imported_content if you haven't deleted them.

                 Posts.setPostField(post.pid, 'content', newContent, next);
            },
            {async: true, eachLimit: 10},
            function(err) {
                if (err) throw err;
                console.log("ALL DONE");
            }
        );

My thought was going with Option 2, since there's data (at least stored in Vanilla databases) that records information about each upload such as who uploaded it, which post it was attached to, etc.

Does the vanilla-data-exporter support ATTACHMENTS?
It's a really big deal.
Also private messages. Conversations, not so much..

@thomasfrivold it's in progress. The importer needs to support it first, then the vanilla exporter can support it

For attachments that is. On vanilla aren't conversations the same thing as private messages? Is that a different plugin?

Vanilla has a very very cool feature where you can add as many recipients you like and start a message stream to all users. So if I talk to Jessica about the party on Saturday, I can add Jenny the "conversation" and ask here if she'll bring her special nuclear bikini.... See what I mean?

Yeah, I use vanilla forums but it's not a very used feature in my community.
Currently nodebb doesn't even support multi-person chats so it wouldn't import correctly anyway.
-Brian

On Nov 15, 2015, at 8:29 AM, thomasfrivold<EMAIL_ADDRESS>wrote:
Vanilla has a very very cool feature where you can add as many recipients you like and start a message stream to all users. So if I talk to Jessica about the party on Saturday, I can add Jenny the "conversation" and ask here if she'll bring her special nuclear bikini.... See what I mean?
—
Reply to this email directly or view it on GitHub.

@bdharrington7, re: attachments i'm thinking that each _topic and _post record, would have an array of _attachments on it, kinda like topic._tags today, (screenshot) (docs)
post example (same for topic)
"{
  "_pid": 65487,
  "_tid": 1234,
  "_uid": 202,

  "_attachments": ["http://example.com/abc/xyz.zip", "http://example.com/abc/xyz2.zip"], // <--- basically an array of URLs

  "_guest": "Some dude",
  "_ip": "123.456.789.012",
  "_content": "Post content ba dum tss",
  "_reputation": 0,
  "_votes": 0,
  "_timestamp":<PHONE_NUMBER>970,
  "_path": "/myoldforum/topic/123#post56789",
  "_slug": "old-post-slug"
}"

This way, it's the expoter's job to make the necessary JOIN an include those
Now since NodeBB doesn't really support attachments, I am think the importer would do 2 things:

1st) it will save on each post/topic record an _imported_attachements field, just like it does for all other fields - that would be useful, if sometime in the future, one decides to use a different plugin for attachments representation, or monitoring or whatever
2nd) it will expose an option in the Post-Import-Tools > Convert to optionally allow the use to "merge attachments in content, while converting to Markdown" (something in that sense) - which will essentially iterate over each record's attachments, and a link to it at the bottom of the content.

Now if the attachments are saved as blobs in the source database, we can also support that, by something like _attachmentsBlobs array - and the importer will essentially write those blobs to the public directory of nodebb, then populate the _attachments array with relative urls to that directory, with unique filenames, the only thing is that we don't know what each file type is, so the attachmentsBlobs items are NOT strings, they need to include the binary and either a filename or extension.
_attachmentsBlobs: [
      {
           blob: <BINARY-BLOB>  // required

           // one these is required, the filename will be prefixed with a unique value anyways
           filename: "abc.zip"
           extension: ".zip" // if no filename is passed, one would be generated.
       }
]

let me know what you think?
@thomasfrivold as @bdharrington7 mentioned, NodeBB does not support "multi-chat" conversations, so we cannot really import them - if you still want to migrate to NodeBB, I suggest you:

definitely keep a copy of your Vanilla database dump
file a feature request with the NodeBB team to support multi-chat,

Once multi-chat is supported, I can probably add this feature here, and allow you to import JUST these conversations from your Vanilla DB - as long, of course, you didn't click that big red button in the Importer > Post-Import Tools

I think this would be a pretty good approach, I was just wondering if we should always run uploads through the nbb uploads module to fire the right hooks, hence my original post. I'm not sure about the performance implications of doing that would be though

On the latest<EMAIL_ADDRESS>you can now either attach urls or blobs, or both at the same time, supported on _topics and on _posts
...
        "_attachments": ["http://example.com/myfile.zip"], // OPTIONAL, an array of urls, to append to the content for download.

        // OPTIONAL, an array of objects, each object mush have the binary BLOB,
        // either a filename or extension, then each file will be written to disk,
        // if no filename is provided, the extension will be used and a filename will be generated as attachment_t_{_tid}_{index}{extension}
        // and its url would be appended to the _content for download
        "_attachmentsBlobs": [ {blob: <BINARY>, filename: "myfile.zip"}, {blob: <BINARY>, extension: ".zip"} ],
...

Obviously writing blobs to disk is going to slow down the importing process, so, if the files are already on disk, put them in nodebb's public folder or somewhere accessible and have your plugin just populates the _attachments array and not the _attachmentsBlobs array