[BACKLOG-14866] Adding serializers for metrics and data. Extracted co…

…mmon code to base class. Unit tests added

Build Completed
:x: This pull request has errors. They will need to be addressed before it can be accepted. See below for more details. Some links are also available below for further assistance in addressing those issues.
Build Commands
mvn -B -fn -f pdi-engine/api/pom.xml clean install && mvn -B -f pdi-engine/api/pom.xml site
mvn -B -fn -f pdi-engine/serializers/pom.xml clean install && mvn -B -f pdi-engine/serializers/pom.xml site

Cleanup Commands
mvn -B -f pdi-engine/api/pom.xml build-helper:remove-project-artifact && mvn -B -f pdi-engine/serializers/pom.xml build-helper:remove-project-artifact

Changed files
  pdi-engine/api/src/main/java/org/pentaho/di/engine/api/events/BaseEvent.java
  pdi-engine/api/src/main/java/org/pentaho/di/engine/api/events/DataEvent.java
  pdi-engine/api/src/main/java/org/pentaho/di/engine/api/model/Row.java
  pdi-engine/api/src/main/java/org/pentaho/di/engine/api/model/Rows.java
  pdi-engine/api/src/main/java/org/pentaho/di/engine/api/reporting/Metrics.java
  pdi-engine/serializers/pom.xml
  pdi-engine/serializers/src/main/java/org/pentaho/pdi/engine/serializers/BaseSerializer.java
  pdi-engine/serializers/src/main/java/org/pentaho/pdi/engine/serializers/DataEventSerializer.java
  pdi-engine/serializers/src/main/java/org/pentaho/pdi/engine/serializers/DeserializedRow.java
  pdi-engine/serializers/src/main/java/org/pentaho/pdi/engine/serializers/MetricsEventSerializer.java
  pdi-engine/serializers/src/main/java/org/pentaho/pdi/engine/serializers/StatusEventSerializer.java
  pdi-engine/serializers/src/main/resources/OSGI-INF/blueprint/beans.xml
  pdi-engine/serializers/src/test/java/org/pentaho/pdi/engine/serializers/DataEventSerializerTest.java
  pdi-engine/serializers/src/test/java/org/pentaho/pdi/engine/serializers/MetricsEventSerializerTest.java
  pdi-engine/serializers/src/test/java/org/pentaho/pdi/engine/serializers/StatusEventSerializerTest.java

Checkstyle violations
The code submitted is not complying with one or more of our guidelines. To perform these checks locally, please use this tool.
/home/buildguy/project/pdi-engine/api/src/main/java/org/pentaho/di/engine/api/events/DataEvent.java

:heavy_exclamation_mark: Unused import - org.pentaho.di.engine.api.model.Row. at Line: 28 Column: 8

/home/buildguy/project/pdi-engine/api/src/main/java/org/pentaho/di/engine/api/reporting/Metrics.java

:heavy_exclamation_mark: Unused import - org.pentaho.di.engine.api.events.PDIEvent. at Line: 27 Column: 8

/home/buildguy/project/pdi-engine/serializers/src/main/java/org/pentaho/pdi/engine/serializers/BaseSerializer.java

:heavy_exclamation_mark: Unused import - org.pentaho.di.engine.api.events.StatusEvent. at Line: 30 Column: 8

/home/buildguy/project/pdi-engine/serializers/src/main/java/org/pentaho/pdi/engine/serializers/DataEventSerializer.java

:heavy_exclamation_mark: File does not end with a newline. at Line: 0

:heavy_exclamation_mark: Using a static member import should be avoided - java.text.DateFormat.FULL. at Line: 56

:heavy_exclamation_mark: Unused import - java.text.DateFormat.FULL. at Line: 56 Column: 15

:heavy_exclamation_mark: '(' is not followed by whitespace. at Line: 63 Column: 76

:heavy_exclamation_mark: ')' is not preceded with whitespace. at Line: 63 Column: 101

:heavy_exclamation_mark: 'switch' is not followed by whitespace. at Line: 92 Column: 19

:heavy_exclamation_mark: 'switch' is not followed by whitespace. at Line: 173 Column: 19

/home/buildguy/project/pdi-engine/serializers/src/main/java/org/pentaho/pdi/engine/serializers/DeserializedRow.java

:heavy_exclamation_mark: File does not end with a newline. at Line: 0

/home/buildguy/project/pdi-engine/serializers/src/main/java/org/pentaho/pdi/engine/serializers/MetricsEventSerializer.java

:heavy_exclamation_mark: Unused import - com.fasterxml.jackson.databind.ObjectMapper. at Line: 32 Column: 8

:heavy_exclamation_mark: Unused import - org.pentaho.di.engine.api.events.StatusEvent. at Line: 37 Column: 8

:heavy_exclamation_mark: Unused import - org.pentaho.osgi.objecttunnel.TunnelSerializer. at Line: 40 Column: 8

:heavy_exclamation_mark: Unused import - java.util.Collections. at Line: 43 Column: 8

:heavy_exclamation_mark: Unused import - java.util.List. at Line: 44 Column: 8

/home/buildguy/project/pdi-engine/serializers/src/main/java/org/pentaho/pdi/engine/serializers/StatusEventSerializer.java

:heavy_exclamation_mark: Unused import - com.fasterxml.jackson.databind.ObjectMapper. at Line: 32 Column: 8

:heavy_exclamation_mark: Unused import - org.pentaho.osgi.objecttunnel.TunnelSerializer. at Line: 39 Column: 8

:heavy_exclamation_mark: Unused import - java.util.Collections. at Line: 42 Column: 8

:heavy_exclamation_mark: Unused import - java.util.List. at Line: 43 Column: 8

:heavy_exclamation_mark: '(' is not followed by whitespace. at Line: 60 Column: 40

:heavy_exclamation_mark: '(' is not followed by whitespace. at Line: 61 Column: 40

:heavy_exclamation_mark: '(' is not followed by whitespace. at Line: 69 Column: 26

:heavy_exclamation_mark: '(' is not followed by whitespace. at Line: 73 Column: 27

:heavy_exclamation_mark: ')' is not preceded with whitespace. at Line: 73 Column: 33

Build Completed
:x: This pull request has errors. They will need to be addressed before it can be accepted. See below for more details. Some links are also available below for further assistance in addressing those issues.
Build Commands
mvn -B -fn -f pdi-engine/api/pom.xml clean install && mvn -B -f pdi-engine/api/pom.xml site
mvn -B -fn -f pdi-engine/serializers/pom.xml clean install && mvn -B -f pdi-engine/serializers/pom.xml site

Cleanup Commands
mvn -B -f pdi-engine/api/pom.xml build-helper:remove-project-artifact && mvn -B -f pdi-engine/serializers/pom.xml build-helper:remove-project-artifact

Changed files
  pdi-engine/api/src/main/java/org/pentaho/di/engine/api/events/BaseEvent.java
  pdi-engine/api/src/main/java/org/pentaho/di/engine/api/events/DataEvent.java
  pdi-engine/api/src/main/java/org/pentaho/di/engine/api/model/Row.java
  pdi-engine/api/src/main/java/org/pentaho/di/engine/api/model/Rows.java
  pdi-engine/api/src/main/java/org/pentaho/di/engine/api/reporting/Metrics.java
  pdi-engine/serializers/pom.xml
  pdi-engine/serializers/src/main/java/org/pentaho/pdi/engine/serializers/BaseSerializer.java
  pdi-engine/serializers/src/main/java/org/pentaho/pdi/engine/serializers/DataEventSerializer.java
  pdi-engine/serializers/src/main/java/org/pentaho/pdi/engine/serializers/DeserializedRow.java
  pdi-engine/serializers/src/main/java/org/pentaho/pdi/engine/serializers/MetricsEventSerializer.java
  pdi-engine/serializers/src/main/java/org/pentaho/pdi/engine/serializers/StatusEventSerializer.java
  pdi-engine/serializers/src/main/resources/OSGI-INF/blueprint/beans.xml
  pdi-engine/serializers/src/test/java/org/pentaho/pdi/engine/serializers/DataEventSerializerTest.java
  pdi-engine/serializers/src/test/java/org/pentaho/pdi/engine/serializers/DeserializedRowTest.java
  pdi-engine/serializers/src/test/java/org/pentaho/pdi/engine/serializers/MetricsEventSerializerTest.java
  pdi-engine/serializers/src/test/java/org/pentaho/pdi/engine/serializers/StatusEventSerializerTest.java

Unit test coverage change
These statistics help you identify how your changes have affected the coverage of the following files. If a file is not in this list, then its coverage was not affected by your changes. To get some help interpreting these metrics, please refer to Jacoco's documentation.
org.pentaho.pdi.engine.serializers.BaseSerializer

Complexity New Coverage: 100.00%
Instruction New Coverage: 70.73%
Line New Coverage: 63.64%
Method New Coverage: 100.00%

org.pentaho.pdi.engine.serializers.DataEventSerializer

Complexity New Coverage: 100.00%
Instruction New Coverage: 100.00%
Line New Coverage: 100.00%
Method New Coverage: 100.00%

org.pentaho.pdi.engine.serializers.DataEventSerializer.new JsonSerializer() {...}

Branch New Coverage: 64.29%
Complexity New Coverage: 56.67%
Instruction New Coverage: 86.51%
Line New Coverage: 89.66%
Method New Coverage: 100.00%

org.pentaho.pdi.engine.serializers.DataEventSerializer.new StdNodeBasedDeserializer() {...}

Branch New Coverage: 61.36%
Complexity New Coverage: 53.12%
Instruction New Coverage: 86.53%
Line New Coverage: 81.03%
Method New Coverage: 100.00%

org.pentaho.pdi.engine.serializers.DeserializedRow

Branch New Coverage: 50.00%
Complexity New Coverage: 62.07%
Instruction New Coverage: 68.54%
Line New Coverage: 65.85%
Method New Coverage: 72.00%

org.pentaho.pdi.engine.serializers.MetricsEventSerializer

Complexity New Coverage: 100.00%
Instruction New Coverage: 100.00%
Line New Coverage: 100.00%
Method New Coverage: 100.00%

org.pentaho.pdi.engine.serializers.MetricsEventSerializer.new JsonSerializer() {...}

Complexity New Coverage: 100.00%
Instruction New Coverage: 100.00%
Line New Coverage: 100.00%
Method New Coverage: 100.00%

org.pentaho.pdi.engine.serializers.MetricsEventSerializer.new StdNodeBasedDeserializer() {...}

Complexity New Coverage: 100.00%
Instruction New Coverage: 100.00%
Line New Coverage: 100.00%
Method New Coverage: 100.00%

org.pentaho.pdi.engine.serializers.StatusEventSerializer

Complexity New Coverage: 100.00%
Instruction New Coverage: 100.00%
Line New Coverage: 100.00%
Method New Coverage: 100.00%

org.pentaho.pdi.engine.serializers.StatusEventSerializer.new JsonSerializer() {...}

Complexity New Coverage: 100.00%
Instruction New Coverage: 100.00%
Line New Coverage: 100.00%
Method New Coverage: 100.00%

org.pentaho.pdi.engine.serializers.StatusEventSerializer.new StdNodeBasedDeserializer() {...}

Complexity New Coverage: 100.00%
Instruction New Coverage: 100.00%
Line New Coverage: 100.00%
Method New Coverage: 100.00%

Checkstyle violations
The code submitted is not complying with one or more of our guidelines. To perform these checks locally, please use this tool.
/home/buildguy/project/pdi-engine/api/src/main/java/org/pentaho/di/engine/api/events/DataEvent.java

:heavy_exclamation_mark: Unused import - org.pentaho.di.engine.api.model.Row. at Line: 28 Column: 8

/home/buildguy/project/pdi-engine/api/src/main/java/org/pentaho/di/engine/api/model/Row.java

:heavy_exclamation_mark: Line has trailing spaces at Line: 88

:heavy_exclamation_mark: ')' is not preceded with whitespace. at Line: 89 Column: 44

/home/buildguy/project/pdi-engine/api/src/main/java/org/pentaho/di/engine/api/reporting/Metrics.java

:heavy_exclamation_mark: Unused import - org.pentaho.di.engine.api.events.PDIEvent. at Line: 27 Column: 8

/home/buildguy/project/pdi-engine/serializers/src/main/java/org/pentaho/pdi/engine/serializers/DataEventSerializer.java

:heavy_exclamation_mark: File does not end with a newline. at Line: 0

:heavy_exclamation_mark: 'switch' is not followed by whitespace. at Line: 89 Column: 19

:heavy_exclamation_mark: 'switch' is not followed by whitespace. at Line: 170 Column: 19

/home/buildguy/project/pdi-engine/serializers/src/main/java/org/pentaho/pdi/engine/serializers/DeserializedRow.java

:heavy_exclamation_mark: File does not end with a newline. at Line: 0


Python 3 Django 1.11 (issue 22)

https://github.com/IMGIITRoorkee/django-filemanager/issues/22

Tested manually on Python 3.6 and Django 1.8 & 1.11
I couldn't got a working CK Editor widget, so I couldn't test it, my attempt is on different branch test-widget.
I added a really simple unit test (FilemanagerTest), but runtests.py seems to not detect this one. I was running it directly from IDE, so it wasn't a problem for me, but maybe we can improve this. I would like to write more tests to make this project more maintainable.

Hey @guy881
Thank you so much for taking this forward. I was able to have a quick look and this looks like a good start for me.
One place that I felt still needs some help were the docs.
Also, is this code still Python2 compatible? If not, it might be worth documenting this detail somewhere IMO.

Hello @akki
Thank you for your review, I am glad you liked it, I've made some updates to docs, as you suggested. Yes, this is still compatible with Python 2, I just pointed it in docs, to be clear.


Fix crashing on startup on iOS

ringtone and icon are marked as optional on flutter side but are marked as required on iOS side, leading to the app crashing immediately on startup if we don't pass those two arguments on ConnectycubeFlutterCallKit.instance.init() function.
Resolve #44

@WillowWisp thanks for your contribution


Docs: Add README, CONTRIBUTING.md

[x] Add gitignore
[x] README.md
[x] CONTRIBUTING.md

LGTM - Looks good to me


Release/6.0.1

:white_check_mark: Build TheIdServer 6.0.1+3.build.2441 completed (commit https://github.com/Aguafrommars/TheIdServer/commit/5a921b4806 by @aguacongas)


Set reference level in CPH using formula with Formulaic?

Hi, thanks for a useful package.
Related to #458 and somewhat related to the discussion in #1203, is it possible to set a reference level for a categorical variable using formulas (v0.25.0)? In statsmodels, which uses Patsy, we could set reference level for predictor x to "ref" in the following model
from statsmodels.formula.api import ols
from patsy.contrasts import Treatment

mod = ols("y ~ C(x, Treatment(reference='ref'))", data)

as described here. However, I see that v0.25.8 switched from Patsy to Formulaic.
Is it possible to set a reference level similarly in Formulaic? Or are there other solutions that still use lifelines.CoxPHFitter().fit(..., formula=<myform>) in lifelines>=0.25.8?

Hi @t-silvers, AFAIK formulaic doesn't support that feature yet. If you really need that feature, you can use Patsy to transform your df outside lifelines, and then pass the transformed df into lifelines.

thanks for the speedy reply! Too bad that Formulaic doesn't have that option, but sure--I could use patsy to transform my df outside lifelines.
for completeness, this is the code I'll use until a better solution is available:
import pandas as pd
import patsy
from patsy.contrasts import Treatment
from lifelines import CoxPHFitter

form = "other_pred + C(x, Treatment(reference='ref'))"

# for some data, data: pd.DataFrame(), with survival data cols ['OS.time','OS']
design = pd.concat([
   patsy.dmatrix(formula_like=form, data=data, return_type="dataframe"),
   data[['OS.time','OS']]
], axis=1)

form = None
cph = CoxPHFitter()

cph.fit(
   design,
   duration_col='OS.time',
   event_col='OS',
   formula= form
)

Hi @t-silvers , as of April 2022 Formulaic does support this.
The syntax is nearly identical but follows R conventions:
from formulaic import Formula
f = Formula("y ~ C(x, contr.treatment('ref'))")


Split permissions.yml

For me mysql is too slow for syncing ranks (simply takes bout 2-3 hr) and i would like to try a new method. However for this method i need to split permissions.yml into two different files... A permissions.yml file (for storing ONLY ranks and permissions) and a Users.yml (for storing player related data). Can u please add such thing?

PEX1 will not be getting any new features, but a way to split backends will be supported for PEX2

Where can i get PEX2?

the future.


[WebSocket] OnError Support

Purpose

Fix https://github.com/ballerina-platform/ballerina-lang/issues/7624
Note: Please review and merge https://github.com/wso2/transport-http/pull/188 before merging this PR since this PR depends on it.

Goals

Add onError support to WebSocket service to acknowledge the protocol errors happening in WebSocket connection.

Approach

Add onError resource to WebSocket service

Automation tests

Unit tests

Yes

Integration tests

yes

Security checks

Followed secure coding standards in http://wso2.com/technical-reports/wso2-secure-engineering-guidelines? yes
Ran FindSecurityBugs plugin and verified report? yes
Confirmed that this PR doesn't commit any keys, passwords, tokens, usernames, or other secrets? yes

Samples
import ballerina/io;
import ballerina/http;

@http:WebSocketServiceConfig {
   path: "/error/ws"
}
service<http:WebSocketService> errorService bind {port: 9090} {
   onError(endpoint ep, error err) {
       io:println(string `error occurred: {{err.message}}`);
   }
}

Add license headers to the bal files too.


Warnings in ArchLinux (GCC 10?)

When building the stdlib on ArchLinux (and presumably any system using GCC 10), we get the following warnings:
/builds/gitlab/sac-group/sac2c/build/sac2c-release/src/sac2c-release-build/include/runtime/phm_h/phm.h:68:23: warning: argument 1 range [18446744065119617024,<PHONE_NUMBER>3709551612] exceeds maximum object size<PHONE_NUMBER>854775807 [-Walloc-size-larger-than=]
   68 | #define SAC_MALLOC(x) malloc (x)
      |                       ^~~~~~~~~~
/builds/gitlab/sac-group/sac2c/stdlib/src/stdio/src/ArrayIO/PrintArray.c:203:20: note: in expansion of macro ‘SAC_MALLOC’
  203 |       index=(int *)SAC_MALLOC(sizeof(int)*dim);
      |                    ^~~~~~~~~~
In file included from /builds/gitlab/sac-group/sac2c/stdlib/src/stdio/src/ArrayIO/PrintArray.c:5:
/builds/gitlab/sac-group/sac2c/stdlib/src/stdio/src/ArrayIO/PrintArray.c: In function ‘ARRAYIO__PrintCharArrayFormat’:
/usr/include/stdlib.h:539:14: note: in a call to allocation function ‘malloc’ declared here
  539 | extern void *malloc (size_t __size) __THROW __attribute_malloc__
      |              ^~~~~~
/builds/gitlab/sac-group/sac2c/stdlib/src/stdio/src/ArrayIO/PrintArray.c: At top level:

These warning seem to indicate that the input for malloc may exceed some upper limit, leading to invalid allocation.
A quick look at GCC bug-report 85783 shows that this warning happens in cases where are compile-time can't determine if the input to malloc is sane. A suggested fix is to re-cast the input to something compatible with size_t, e.g. unsigned int.

Ok, looking at the code in src/stdio/src/ArrayIO/PrintArray.c, we have the following lines (refactored to makes things a bit more clear):
void PrintArr(FILE *stream, int typeflag, string format, int dim, int * shp, void *a) {
...
  if (dim == 0) {
    // we do some stuff here
  } else {
    index = malloc (dim * sizeof (int));
    // we do something with `index`
  }
}

If I use a cast to unsigned int in malloc, e.g. malloc (((unsigned int)(dim)) * sizeof (int)), the warnings go away. I don't feel comfortable doing this as its a bit of kludge.
The source of the problem as far as I can see is that because we are calling PrintArr from a stdlib function (printarray), the C compiler can only infer the range of the values for dim based on its type. By casting to unsigned int we limit this range to positive values which is less than PTRDIFF_MAX, so there is no warning any more. Note that the value of PTRDIFF_MAX is set as the default for -Walloc-size-larger-than= to check against.
An alternative solution is to perform some kind of check for dim > 0.


Pursuit documentation for 3.1.0

I only see 3.0.0 on Pursuit, and links from other modules are currently broken -- for examplefrom https://pursuit.purescript.org/packages/purescript-foldable-traversable/3.4.0/docs/Data.Semigroup.Foldable#v:foldMap1

I've republished both now.


loading helper not case sensitive

I try to load a helper module which lives in a camelcased path
$this->load->helper('foo/FooBar/Reporting/reporting');

And it can't be found. On my case insensitive system it works, on my case sensitive it doesn't. The shown error reads:
Unable to load the requested file: helpers/foo/foobar/reporting/reporting_helper.php

Is there any preprocessing of the path, which breaks case? What can I do to get proper case sensitivity?
thanks

Update: I found that the Loader class explicitly transforms paths to lower case (core/Loader.php@_ci_prep_filename). Is there any good reason for that?
I would argue, that the developer has to be responsible for the correct case in loading (via Load) and saving on the filesystem.

Yes, there is a reason for that - we try to enforce our naming conventions where it is appropriate.
You do have a point though. _ci_prep_filename() is only supposed to be applied to file names, directories in the path excluded.
But I have to ask - why do you want to have those subdirs? I can't imagine anyone needing tens of helpers, which would be the only reason to organize them in such a way IMO.

We have something like 30+ helpers. We tend to create many small helpers for special use cases.
Excluding the directory parts from _ci_prep_filesname() would be perfect for me 👍
Thanks!

Well, that's what I'll do because that's how it is supposed to work in the first place.
But I have to say, having 30+ helpers is a sign of MAJOR flaws in your design.

Please test with the commit above.

Works like a charm,
thanks for the hint regarding "too many helpers". I will think about this.


Write hdf5 files as h5ad for AnnData ComputedFiles

Context
When compiling AnnData zips we want to start using the .h5ad file extension instead of the .hdf5 that is currently on the portal. We are anticipating these file extensions changing on the input bucket in the future but in the mean time we just want to rename on the fly when we write the files to the ZipFile.
The contents of these files is unchanged.
Problem or idea
I don't think there is much to do outside of replacing the extension before writing the file and updating tests to expect to see this new extension. I think that there will be some difficulty around the file mapping when we get to zipping a project but I am not 100% sure what that will look like at this time. It would be nice to implement this in a way that would work for either extension in the input bucket.
Solution or next step

Rename AnnData .hdf5 files to .h5ad at time of ComputedFile creation
Address project zip file mapping
Fix tests to expect to see this new extension in AnnData zips

I think we can probably close or rewrite this: all hdf5 files in the scpca-portal-staging-inputs bucket have now been renamed as .h5ad: there should be no need for renaming, just making sure that the ingest scripts are looking for .h5ad files.

Replaced with #667


Bugfixes, Windows support

fixes #16
using os.devnull instead of hardcoded /dev/null
corrected package name (pydep-run.py demo failed)

thanks for the fix!


how is trangeview to pointview implemented

Hi, in which part of the rangeview to pointview is implemented, I see that it directly converts the rangenet dedaode rangeview features to bev features?

The rangeimage batch_dict['rangemap_xyz']  has the 3d coordinates of the point cloud. Therfore it can be reshaped back into a point cloud. We can then use the indices of this point cloud to reproject batch_dict['range_res'] into a point cloud.
This is done in this file


Add more example scripts

rename examples/gcn.jl --> examples/gcn_gpu.jl. (this actually does not run, but IDK if its my setup or a bug)
added examples/gcn.jl (original example but w/o the |> gpu parts
added examples/gcn_featured_graph.jl (was a little more tedious to figure out how to make this work than i hoped from the docs alone)
note Dropout is broken for the FeaturedGraph example

rename examples/gcn.jl --> examples/gcn_gpu.jl. (this actually does not run, but IDK if its my setup or a bug)
added examples/gcn.jl (original example but w/o the |> gpu parts

this seems a wasteful code duplication. You could just add a use_cuda flag, see e.g. https://github.com/FluxML/model-zoo/blob/master/vision/mlp_mnist/mlp_mnist.jl

For GCNConv, if you pass it a FeaturedGraph, it will return you a FeaturedGraph. If you pass it an array, it will give you an array back. So, in the context of input being a FeaturedGraph, a Flux layer should not being used in the network, or you should pass it by bypass_graph.


feat (flutter_box): organize the box component and stylesheet

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

GitHub release
npm package (@latest dist-tag)

Your semantic-release bot :package::rocket:


Adding a program to find and reset all RealSense cameras.

Please ensure the above guidelines for contributing are met.
Fixes Issue: #205
Changes proposed in this pull request:
-Automatically find and reset all types of RealSense camera.
You might want to check that I found all possible device #'s for RealSense cameras:
reset_all_devices("0a80"); // SR300's reset_all_devices("0aa5"); reset_all_devices("0ab3"); // ZR300's reset_all_devices("0ad0"); reset_all_devices("0ACB");

Here's a new way to do it. It would be easier if you could give the process a unique name, though, like realsense_nodelet. I'm not sure how easy that would be.

I believe that the with the initial_reset parameter, the automatic reset following the automatic detection of a problem, this PR is not necessary anymore.
Would you agree?

I haven't tried initial_reset, but feel free to close the issue if that's true.

I am currently using a T265 camera and when launching the node with ros 3 out of 5 times the T265 node will fail to start.
I have in the launch file the  and
And the camera still does not initialise quite often.
Has anyone been able to solve this and have the camera reliably 'turning on'?

Any progress on this ?

Three years later, some clients are still having trouble with Realsense-related ROS nodes not dying. Any chance of getting this updated/merged soon?


Editing causes all contextual blames to disappear

Issue Type: Bug
When I edit a file, the git blame annotations (same line, status bar etc) all disappears. If i hit save, everything re-appears.
The only thing that still works once I make any change to a file, is the gutter blame that I have to toggle on with the button in the top right- also for some reason, that auto-hides itself whenever I start changing the code, and I have to manually press it to turn it back on each time too.
If it might lead to any clues, I am developing while using the remote-ssh extension for vscode, and all the code/projects I'm working on lives remotely on a server (incase that makes any difference)
Extension version: 10.1.0
VS Code version: Code 1.38.1 (b37e54c98e1a74ba89e03073e5a3761284e3ffb0, 2019-09-11T13:31:32.854Z)
OS version: Darwin x64 18.7.0
Remote OS version: Linux x64 4.4.0-143-generic

System Info

Item
Value

CPUs
Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz (16 x 2300)

GPU Status
2d_canvas: enabledflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onnative_gpu_memory_buffers: enabledoop_rasterization: disabled_offprotected_video_decode: unavailable_offrasterization: enabledskia_deferred_display_list: disabled_offskia_renderer: disabled_offsurface_synchronization: enabled_onvideo_decode: enabledviz_display_compositor: disabled_offwebgl: enabledwebgl2: enabled

Load (avg)
2, 2, 1

Memory (System)
16.00GB (0.21GB free)

Process Argv
-psn_0_880855

Screen Reader
no

VM
0%

Item
Value

Remote
SSH: dev2

OS
Linux x64 4.4.0-143-generic

CPUs
Intel(R) Xeon(R) Platinum 8175M CPU @ 2.50GHz (48 x 2500)

Memory (System)
184.85GB (4.25GB free)

VM
0%

facing the same issue #892


HANDWRITTEN CHARACTER RECOGNITION IN ENGLISH [GSSOC'23]

💥 Proposal
A growing field of research in pattern recognition, computer vision, and artificial intelligence is handwritten character recognition.
I will use Convolutional Neural Network model for recognition as it reduce the processing time while providing higher recognition accuracy.
Dataset: https://www.kaggle.com/code/mohammadkumail/handwritten-character-recognition-deep-learning/input

Kindly assign me this issue. I would like to work on it

@Devika-arun - you can go ahead! We are assigning you 21 days for this project, after which it will be assigned to someone else if not completed. All the best!
Name the file as: algorithm_dataset.ipynb and link it in the readme of the labeled directory as algorithm - dataset.
@dynamicdhxx - since we are following the first-come-first-serve policy, we will not be able to assign you this issue. However, you can create another issue on the similar lines.

ok..I'll work on it

Can I work on this? Please assign me


simpler key

In my opinion the way the key is implemented is not very userfriendly, becaus the user has to define a new type to use it with the database. Instead just using &[u8] or the following would make it much simpler.
pub trait Key<'a>: From<&'a[u8]> + AsRef<&'a[u8]>{}

Another way would be to implement Key for &[u8].

A built-in implementation for &[u8], String, u32 and u64 would go a long way on user friendliness for the 95% of cases. Currently the library only comes with i32.

I'm working on this, though I must add that this probably means a bit more effort then expected. Using & [u8] internally means, that the key type would gain a lifetime through From<& [u8]> :(.
https://github.com/skade/key/blob/master/tests/key.rs#L35

After a quite disheartening discussion about this here, I'll stick with my own conversion trait and implement a few more standard things.
http://users.rust-lang.org/t/searching-for-a-nice-to-and-from-binary-slice-abstraction/1092/8

After thinking about this for a while, noting things down: Key should remain a trait and implementations should implement Borrow< > and Into< > for it.

I decided to go a different route: The key implementation stays similar and requires conversion two and from a pointer and a length. For convenience, this comes with a default implementation for types that are Sized + Copy. See https://github.com/skade/db-key/tree/sized-key for details.

Um, doesn't that implementation just flat out break type safety?
Yes, yes it does:
http://is.gd/h5PxTf
(The above example dereferences an arbitrary int (42) in safe code.)
IMHO, the main problem with the old API is just that it leaves no room for
error handling, which the new API doesn't solve.
On Sat, Aug 29, 2015 at 8:20 AM, Florian Gilcher<EMAIL_ADDRESS>wrote:

I decided to go a different route: The key implementation stays similar
and requires conversion two and from a pointer and a length. For
convenience, this comes with a default implementation for types that are Sized

Copy. See https://github.com/skade/db-key/tree/sized-key for details.

—
Reply to this email directly or view it on GitHub
https://github.com/skade/leveldb/issues/6#issuecomment-135984505.

Neither of the approaches suggested here does error handling (which could be solved in this one).
Considering safety concerns, you are right. Although more because of wrongfully making the train unsafe instead of the conversion methods, this would fit the intention better: http://is.gd/ZV7q0l
(same boom, but because of misusing two unsafe methods)

Either way, I'm not sure why you'd want to make db-key unsafe...
The default implementations Ignacio is asking for could be done with the
old API.
On Sat, Aug 29, 2015 at 3:16 PM, Florian Gilcher<EMAIL_ADDRESS>wrote:

Neither of the approaches suggested here does error handling (which could
be solved in this one).
Considering safety concerns, you are right. Although more because of
wrongfully making the train unsafe instead of the conversion methods, this
would fit the intention better: http://is.gd/ZV7q0l
(same boom, but because of misusing two unsafe methods)
—
Reply to this email directly or view it on GitHub
https://github.com/skade/leveldb/issues/6#issuecomment-136042436.

After thinking about it for a weekend, I think the important part here is assuming that the underlying library handles raw pointers.
I'm currently contemplating going the way Path goes: be a type built over &[u8], with conversion traits to and from being implemented for most types.

What is the current status of this? It seems like Vec and String at the very least should implement the Key trait. But since an implementation isn't provided in the same crate as Key, I have to use a wrapper type. This is rather inconvenient.

With the current API I can't even figure out how to use a wrapper around &[u8] where lifetimes work out. I think part of the solution would be to use &Key (in which case the type of Key could be [u8]).  The problem is with iteration.
One way that might work could be something like this:
trait Key {
  type Iterated: Borrow<Self>;
  fn to_u8(&self) -> &[u8];
  fn from_u8(bytes: &[u8]) -> Iterated;
}

With an implementation for [u8] that looked like
impl Key for [u8] {
  type Iterated = &[u8];
  fn to_u8(&self) -> &[u8] { self }
  fn from_u8(bytes: &[u8]) -> Iterated { bytes }
}

And then get and put would take a &Key for the key argument and the key returned by iterators would be of type Key::Iterated

This sounds like a good way. I must admit that a lot of the design around keys was me learning Rust, so I should change that soon (or accept PRs? :) )

It looks like this has been changed, but the documentation hasn't been updated to reflect it: https://skade.github.io/leveldb/db_key/trait.Key.html
I just tried to create a hello-world-style example to print all the keys in a database, and I wasn't able to figure out how to do it. Could you update the README with an example where the keys are strings?

I think you should have a similar API to the RocksDB crate, where instead of a dedicated Key trait the get and put functions are templates that take a From<&[u8]> and As<&[u8]> respectively.
Would a pull request for something like that be accepted or is this crate in full maintenance mode?

@kaimast as long as there's a reasonable backwards-compatibility story, I'm okay with such a change. Not sure how many projects actually express a dependency to the key trait.


intero-restart fails with error message: The following target packages were not found: ghc-bin

I have an issue where when I try to enable intero via emacs, I get the following error message:
The following target packages were not found: ghc-bin

I also get this message:
For troubleshooting purposes, here are the arguments used to launch intero:

  stack ghci --with-ghc intero "--docker-run-args=--interactive=true --tty=false" --no-build --no-load --ghci-options -odir=/var/folders/43/vdy6_vtx22qfpl7_qd6vf2940000gn/T/intero25547FMY --ghci-options -hidir=/var/folders/43/vdy6_vtx22qfpl7_qd6vf2940000gn/T/intero25547FMY ghc-bin

Are you opening a cabal project without a stack.yaml file?

True! The project doesn't have a stack.yaml file. It's the GHC project: https://github.com/ghc/ghc

I think loading GHC is a bit beyond Intero's capabilities.


added the test_set analysis for checking the trends for pv_ids

Pull Request
Description
The file test_set_analysis_pv_id_vs_month.ipynb consists of the analysis of photovoltaic systems trends for all the months of the year.
Fixes #29

Would you be able to add any highlights to https://github.com/openclimatefix/Open-Source-Quartz-Solar-Forecast/blob/main/quartz_solar_forecast/dataset/README.md. Images and plots are welcome

@peterdudfield, sure. on it. It is exciting, i like the work :)))

Hello @peterdudfield, I added the highlights in the readme. and for adding the image I made a new directory images to have a directory structure. But the tests for this PR failed for my second commit. Can you please let me know how can i fix it.

Hello @peterdudfield, I added the highlights in the readme. and for adding the image I made a new directory images to have a directory structure. But the tests for this PR failed for my second commit. Can you please let me know how can i fix it.

I think its linked with #70

@peterdudfield , I opened a PR #71 to fix it. Can you kindly check?

try merging in main, and it should work now

@peterdudfield, I am merging it in the main branch already. Maybe just need to rerun the tests.

@peterdudfield , should I merge this branch of mine with main?

@peterdudfield , done, passed :)))))

Thanks @roshnaeem for adding this extra detail


Cancel concurrent test workflows

Cancel concurrent jobs to avoid bogging down CI across the holoviz org.

Thanks!
As usual the tests are waiting on macos builds...but by merging this now, maybe that won't be quite as bad a problem moving forward!


chore: version packages

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
<EMAIL_ADDRESS>Minor Changes

#1401 9d72053 Thanks @gwansikk! - feat(codemods): add codemod dry, print options

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

Project coverage is 73.89%. Comparing base (9d72053) to head (c156609).

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #1402   +/-   ##
=======================================
  Coverage   73.89%   73.89%
=======================================
  Files          70       70
  Lines         590      590
  Branches      131      131
=======================================
  Hits          436      436
  Misses        142      142
  Partials       12       12

Components
Coverage Δ

@suspensive/react
100.00% <ø> (ø)

@suspensive/react-dom
95.55% <ø> (ø)

@suspensive/react-native
100.00% <ø> (ø)

@suspensive/react-query
83.47% <ø> (ø)

@suspensive/react-query-4
0.00% <ø> (ø)

@suspensive/react-query-5
0.00% <ø> (ø)

@suspensive/jotai
0.00% <ø> (ø)

@suspensive/codemods
42.85% <ø> (ø)

@gwansikk Approve please if you want to merge this!


Unable to update Pi-Hole after re-install of Internet-pi

I removed Internet-pi by uninstalling ansible and rm'ing the directories Internet-pi created (internet-monitoring, pi-hole, internet-pi).  I re-installed and used --force to get the requirements.yml to install the requirements again.  Everything works except I don't have a docker-compose.yml file in my pi-hole dir therefore docker-compose pull does not run.
It appears that this command failed to run from tasks/pi-hole.yml:

name: Copy Pi-hole docker-compose template to Pi.
ansible.builtin.template:
src: templates/pi-hole-docker-compose.yml.j2
dest: "{{ config_dir }}/pi-hole/docker-compose.yml"
mode: '0640'
become: false
notify: Restart pi-hole

I tried to manually copy docker-compose.yml.j2 to the pi-hole directory but when I run docker-compose pull I get:
ERROR: yaml.parser.ParserError: while parsing a block mapping
in "./docker-compose.yml", line 18, column 7
expected , but found ''
in "./docker-compose.yml", line 20, column 36
I'm an ansible and docker noob - can anyone assist?

Could you please share the output from ansible-playbook main.yml?


Cannot read property ‘from’ of undefined at new RouteGoverness

I have created a GitHub repo to show the (“TypeError: Cannot read property ‘from’ of undefined at new RouteGoverness”) problem, mentioned by Wahyu Permadi in your Medium post .
I would be very grateful if you would have a look at it.
In the router file, change ‘showTheBugInAction’ to true and the problem should be immediately apparent.
I am using Node 8 in Ubuntu 18.04.

I notice this problem was first reported by "Muhammad Izzuddin Al Fikri" as a response to your Medium article last August 29.
I also tried the example by @blackpuppy, and found that it fails in the same way, for the same reason.


Update build setup

Updates to latest gradle-intellij to support latest SDKs
Updates Gralde wrapper to version 7.6

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

v0.28.0
GitHub release

Your semantic-release bot :package::rocket:


Permit digits in node name and limit to 255 chars

This makes _check_path conform to the current node name spec.

Thanks @aschampion, much appreciated.


Separate the AWS SNS Publisher implementation from IMessagePublisher

Squash SnsTopicByName and SnsTopicBase into 1 class and rename it to SnsPublisher
Remove the IMessagePublisher from SnsPublisher and SqsPublisher and add a IPublisher interface
Move IMessageSerializationFactory junk away from SnsPublisher

Hey @jaimalchohan There's a bunch of stuff in here which doesn't quite speak for itself. Be goor to have 10 mins on it today.


Generator for StyledProperty does not work anymore on Avalonia 11.0.0 preview6

Describe the bug
In the latest pre-release of Avalonia 11 (preview 6), the prototype of the Register method with the parameter notifying is now internal.
Here a discussion on the Avalonia repo explaining the change: https://github.com/AvaloniaUI/Avalonia/discussions/10766
So your library cannot be used with this version and the later ones.
Steps to reproduce the bug

Migrate the Avalonia nuget references to 11.0.0-preview6

The project no longer builds.
Expected behavior
No response
Screenshots
No response
NuGet package version
No response
IDE
No response
Additional context
No response

I'm not entirely sure if the other changes will apply to older versions as well. There are two ways here - to introduce the MSBuild property DependencyPropertyGenerator_UseAvaloniaPreview, which the generator will read and generate the correct code, or wait until these versions come out of preview. I will implement the first option if there are messages from you or other users that this is necessary.

Message from Intellisence or message when compiling?

When compiling

Is it something related to https://github.com/HavenDV/H.Generators.Extensions/blob/108ce2b09a42ddfd1573c78c82617419fa58df47/src/libs/H.Generators.Extensions/AnalyzerConfigOptionsProviderExtensions.cs#L141
Do I need to set particular settings in my csproj (RecognizeFramework_DefinedConstants...)?

Yes, try setting <RecognizeFramework_DefineConstants>HAS_AVALONIA</RecognizeFramework_DefineConstants> explicitly. I still don't understand what the problem is

Perhaps your build fails for another reason, but you see not the build log, but Intellisence errors that may not be correct?

I've found the problem. I didn't add a reference to the DependencyPropertyGenerator package (+ DefineConstants) in the project. I thought it would consume the package as transient from a referenced project.
It was working until now, so I didn't what changed since.
BTW, it works, I'm happy !
Thank you very much for the time you've spent to help me, very appreciated :)


Put the protocol name in front of the hostname.

Without the protocol name this doesn't work. Adding this makes it
possible to start using the exporter purely looking at the
documentation.

I've just put in a workaround for #24 in this pull request as well.


#616 Finish entry point updates by updating generator

update deps and config for rollup
update config for webpack

I meant to get this into the last PR for this issue. Working on the right communication practices as I get up to speed on the repo.

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.1 out of 2 committers have signed the CLA.:white_check_mark: Westbrook:x: Westbrook JohnsonWestbrook Johnson seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.

This should be good to go if anyone’s ready for a review!

We can squash this to 1 commit on merge, right?

Yes, I love squash.
Webpack is post v1.0.0 so when we make feature releases, it will just take them…yay! 🌮 Happy to make a manual change if you’d prefer to be explicit: https://github.com/open-wc/open-wc/blob/master/packages/create/src/generators/building-webpack/templates/_package.json#L7
Discussed separately doing a v1.0.0 party on the features that we have that are ready for that on Slack, but I’m not 100% which ones are to push that initiative forward.

Ah, yes you're right. We can keep it as is. Happy to bump everything to 1.x.y, I'm not a huge fan of 0.x.y releases unless we're at a very early stage.


Add history feature

Codecov Report

Merging #141 (91b5eb4) into master (a8a9a4e) will decrease coverage by 1.26%.
The diff coverage is 40.00%.

@@             Coverage Diff              @@
##             master     #141      +/-   ##
============================================
- Coverage     74.32%   73.06%   -1.27%
- Complexity      698      709      +11
============================================
  Files            99      101       +2
  Lines          2228     2313      +85
  Branches        276      284       +8
============================================
+ Hits           1656     1690      +34
- Misses          476      527      +51
  Partials         96       96

Impacted Files
Coverage Δ

src/main/java/seedu/address/MainApp.java
0.00% <0.00%> (ø)

...ddress/logic/commands/HideAppointmentsCommand.java
33.33% <ø> (ø)

...du/address/logic/commands/HidePatientsCommand.java
95.23% <ø> (ø)

...java/seedu/address/logic/commands/ListCommand.java
85.71% <ø> (ø)

...ss/logic/parser/HideAppointmentsCommandParser.java
76.19% <ø> (ø)

...ddress/logic/parser/HidePatientsCommandParser.java
100.00% <ø> (ø)

...du/address/model/person/UniqueAppointmentList.java
78.57% <ø> (-0.74%)
:arrow_down:

...el/person/predicates/HiddenPredicateSingleton.java
60.00% <ø> (ø)

...el/person/predicates/HideAppointmentPredicate.java
21.42% <ø> (ø)

...rson/predicates/NameContainsKeywordsPredicate.java
100.00% <ø> (ø)

... and 9 more

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


utility: cleanup - remove unused code

Commit Message: utility: cleanup - remove unused code
Additional Description:
Removing unused code.
Risk Level: low
Testing: N/A
Docs Changes: N/A
Release Notes: N/A
Platform Specific Features: N/A

/assign @KBaichoo


Errors quote non-literal text

Example:
Expected `newline` or `end of input`

See https://github.com/rust-lang/cargo/pull/10086 for a lot more

See https://github.com/Marwes/combine/issues/334


Permadiff in Cloud Run module

 # module.cloud-run-1-0.google_cloud_run_service.service will be updated in-place
  ~ resource "google_cloud_run_service" "service" {
        id                         = "locations/europe-west1/namespaces/tf-playground-svpc-cr-1/services/test-0"
        name                       = "test-0"
        # (4 unchanged attributes hidden)

      ~ template {
          ~ metadata {
              ~ labels      = {
                  - "run.googleapis.com/startupProbeType" = "Default" -> null
                }
                # (2 unchanged attributes hidden)
            }
          ~ spec {
                # (3 unchanged attributes hidden)

              ~ containers {
                  + args    = []
                  + command = []
                    # (1 unchanged attribute hidden)

                    # (3 unchanged blocks hidden)
                }
            }
        }

        # (2 unchanged blocks hidden)
    }

I can reproduce the run.googleapis.com/startupProbeType but no idea how to reproduce args, command.
@ludoo can you double check and post example?

module "cloud-run-1-0" {
  source     = "../cloud-foundation-fabric/modules/cloud-run"
  project_id = module.project-svc-cr-1.project_id
  name       = "test-0"
  region     = "europe-west1"
  containers = {
    hello = {
      image = "europe-west1-docker.pkg.dev/tf-playground-svpc-ar-0/test-0/nginx-hello:plain-text"
      ports = {
        http = {
          container_port = 80
        }
      }
    }
  }
  ingress_settings = "internal-and-cloud-load-balancing"
  depends_on       = [module.project-svc-ar-0]
}

but don't worry, it was more like a self-memo to remember to get to it sooner or later


HttpBasicAuthentication class doesn't exist

In your example, you have this snippet:
$app->add(new \Slim\Middleware\HttpBasicAuthentication([
    "path" => "/api/token",
    "users" => [
        "user" => "password"
    ]
]));

But the HttpBasicAuthentication class is nowhere to be found

You can find it at: https://github.com/tuupola/slim-basic-auth


Removal of workerCleanup is a breaking change

We have a dependency on the workerCleanup function that was removed in release 5.3.0.  Since the removal of this function causes a breaking change I think this release has incorrect semver. Shouldn't it have been 6.0.0?

At the time we didn't make it a /major/ change because:

worker#workerCleanup was always listed as an optional method, and we learned that very few people actually used it
the community was asking for "automatic" cleanup, so we /moved/ the work worker#workerCleanup was doing to the scheduler
we were focused on the new worker.ping API above everything else, which was developed to be transparent (no api changes)

But, I think you are correct! https://semver.org says that any non-backwards compatible (drop-in) API change should be a major version upgrade.  Removing a method probably counts as non-backwards compatible!
Since v5.3 has been out for a few months now (and there are 4 more versions past that now), I don't think it makes sense to deprecate it.  Does it make sense to cut a v6 now, with no code changes... or should we wait until the next release?

From semver.org:

What do I do if I accidentally release a backwards incompatible change as a minor version?

As soon as you realize that you’ve broken the Semantic Versioning spec, fix the problem and release a new minor version that corrects the problem and restores backwards compatibility. Even under this circumstance, it is unacceptable to modify versioned releases. If it’s appropriate, document the offending version and inform your users of the problem so that they are aware of the offending version.

The old implementation of worker#workerCleanup had a few limitations:

only checked for dead workers which happened to have been spawned by this host (by os.hostname())
could not recover from a partially-exited worker (common with redis OOM issues)

If we are brining back worker#workerCleanup, should we bring it back with the same limitations, write out that it is now a no-op, and will be handled by the scheduler, or make it a proxy to scheduler#checkStuckWorkers?

Thanks for your response.  I guess if it were me I would bring it back with the same limitations and then remove in the next major version release.

This might be documented somewhere and/or not needed anymore per @evantahler's note above and in that case apologies for the repetition (I just didn't see it anywhere in this issue), but in case it helps anyone I changed code in our repo to clean up workers in a MultiWorker instance from the following:
multiWorker.workers.forEach(worker => worker.workerCleanup())
to the following
multiWorker.workers.forEach(worker => multiWorker.cleanupWorker(worker))
Hopefully this is the correct way to update to support the removal of workerCleanup :)


Create rebuff.json

Added Rebuff
The Pull Request resolves Issue #[Issue-Number]
Description:
Added the word and definition of the word REBUFF

Added a word successfully


Feature Request - Search with more mode

The search function will do search with whole workspace, may it be possible to control the mode?

Search in current file.
Search in opened files.
Search in workspace.(current mode)

This may cost less and easy to use in some situations.

You can search the currently open file with CTRL + F instead of using the Search Bar (CTRL + SHIFT + F).
You can also restrict the search results e.g. "search in one specific folder" or use a regex:

@pangeax
Yep, I know these functions.
I am just thinking to combine they two (show all target in dialog and click to navigate while CTRL+F too).
I have built a plugin to achieve it, and wonder if it is a general request.

You can also Find in Folder from the context menu on a folder in the Explorer.

@chrmarti  May I fork a branch to implement it?

@FFengIll I don't think I want to add more buttons and controls to the search viewlet, especially since it's possible to use the existing tools to perform those searches.


displaying .Ply image in c#

I have the point cloud from the c# cookbook exported to a ply file. Can someone help me to display this ply image in the code from the csharp wrappers from librealsense.

Hi @Xander-Vreeswijk   Your best option may be to create a non-RealSense function within your C# program that reads the data from the RealSense ply file and converts it, so that you can generate an image within your program.  The link below provides some guidance about how to do this.
https://stackoverflow.com/questions/58916236/reading-binary-ply-file-face-indices-using-c-sharp

Thank you for your response, but I got it to work using the helix toolkit.

Great news - thanks for the update!


Non-jargon way of saying "CFP"

The form has " I was selected from CFP " I'd like to change that to something more clear.
My original thought to call this as CFP was, some conf use this as "call for proposal " or "call for paper" (both intended for talk submission).
Thinking more about it, even "call for proposal/paper" is a odd word if you never looked at how speakers for conference gets selected.  Any suggestion?

perhaps " I was selected after submitting a talk proposal" ?

How about, just "I submitted a talk", because the alternatives are around being invited vs being a sponsor.
There's an implicit "and it was accepted" because you start off with "I spoke at ______ conference, and ...".

@lewiscowper I like Lewis' :clap:

+1 for @lewiscowper suggestion.

Playing off @lewiscowper's good suggestion, maybe even "I submitted an idea for a talk"

I like @brianloveswords' addition, rounds it out, and I know (at least from my experience) that we often don't have the talk already written when we fire off an abstract.

"Call For Speakers" is usually what I call it from "what's on the web site" standpoint.

Thanks everyone for suggestion!
I think going with  @brianloveswords and @lewiscowper 's suggestion and use "I submitted an idea for a talk" would fit well. This also eliminates "I was selected" word which feels a little bit like speaking is "a club"
<3 you all for the help !

hey @brianloveswords @lewiscowper
this might be silly question but which sounds better ?
"I submitted an idea"
"I proposed an idea"
?

Proposing an idea is better IMO, because you lack the knowledge of where
it's being submitted to, so propose sounds more like it was speculative
On 28 Oct 2015 18:44, "Mariko Kosaka"<EMAIL_ADDRESS>wrote:

hey @brianloveswords https://github.com/brianloveswords @lewiscowper
https://github.com/lewiscowper
this might be silly question but which sounds better ?
"I submitted an idea"
"I proposed an idea"
?
—
Reply to this email directly or view it on GitHub
https://github.com/kosamari/who-pays-tech-speakers/issues/8#issuecomment-151925910
.


Investigate if /metrics can be per workspace

I think they're global, but we'll presumably want them to be scoped per workspace

This is something for the operation team, not user visible. I would prefer to keep the experience-blocker for consumer-only topics.

Closing as metrics per workspace is probably not feasible due to cardinality size concerns.


Convert LeNet-MNIST example to X10

First of many PRs for #514.
Been busy with a few things lately hence the hiatus. Played around with X10 the last couple of days and I am really exited about the future of the S4TF project. Great work

As a quick update: I checked this out on Linux and it works great there, however, we're running into some issues with X10 on macOS that we're looking into now. Specifically, this example segfaults under X10 on macOS with both our 0.9 release toolchain and the current nightlies. It's not a problem with what you have here, but something internal.
Before we merge this in, I want to see if we can fix this. If not, we may need to add selective compilation checks to use the TF eager device by default in this example on macOS so that it still works out of the box. I'll let you know what we find.

Yup, I also experienced segmentation fault when executing on X10 on my macOS earlier.


Rename 403_csrf.html to 403.html

403.html is the name that django expects, unless it is overriden. 403_csrf is a separate case, which according to django docs and mailing list should get a separate view/template. Fixes #2163

Docs: https://docs.djangoproject.com/en/2.1/ref/csrf/#rejected-requests
Mailing list: https://groups.google.com/forum/#!msg/django-developers/O2raF0RVGA0/44-3Jz0jCwAJ
Stackoverflow: https://stackoverflow.com/questions/31981239/django-custom-403-template

Thanks for the fix 🎉


RTSP stream problem -Stream exit by signal or not client

Hello,
I have 2 cameras via RTSP, the one that is Ubiquiti works, but the one I have BESDER 1080//960P/720p Full HD IP Camera XMEye so from VLC works for me, but via RTSPtoWEB does not work.
Where's the bug?
OK camera (ubiquiti):rtsp://<IP_ADDRESS>:554/Streaming/Channels/001
Fail/Problem (BESDER) : rtsp://<IP_ADDRESS>:9090/dss/monitor/params?cameraid=1000342%240&substream=1
(VLC player from internet and local site - ok)
LOG image:
level=error msg="Stream error restart stream dial tcp <IP_ADDRESS>:9090: i/o timeout" call=Restart
level=error msg="Stream error restart stream Camera send statusRTSP/1.0 302 Moved Temporarily" call=Restart

same problem, seems no codec support?

if hls

if webrtc

if mse

请问这个问题解决了，我也遇到相同的问题。确定流格式是 H264


Error loading external fonts

TANGRAM VERSION:
Tangram v0.21.1
ENVIRONMENT:
macOS Big Sur running Firefox 83.
TO REPRODUCE THE ISSUE, FOLLOW THESE STEPS:
Add an external font to my scene file like so:
fonts:
  Open Sans Regular: external

RESULT:
Tangram v0.21.1 [error]: Scene.load() failed to load "scene.yaml": can't assign to property "url" on "external": not an object TypeError: can't assign to property "url" on "external": not an object
EXPECTED RESULT:
Per https://tangrams.readthedocs.io/en/master/Syntax-Reference/fonts/#external, it looks like external fonts are supported via this syntax. However, it looks like the current JS (https://github.com/tangrams/tangram/blob/990d2608c7dce2c3801c2cfd676e5c2e5b74c743/src/scene/scene_loader.js#L131) now assumes that there will be an object with a URL property.

Yikes, you're right, external fonts do appear to have been broken for some quite awhile 😬 It's an easy fix. I almost wonder if this functionality should just be deprecated, but it does have a logical use, for example in cases where you have brand-specific font you're already loading in your app and don't want to duplicate resources.

Fixed in master but usually keep issues open until shipped in a production release.

No worries. I'm not convinced I need the feature either, but I was trying some stuff out and noticed that it was busted ;) Thanks for the quick fix!

Fixed in v0.22.0


fix: update to see-lingua v1.0.6

fix: update to see-lingua v1.0.6

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

npm package (@latest dist-tag)
GitHub release
v13.0.4

Your semantic-release bot :package::rocket:


New reference design release with fixed SAT noise and LAT beams

[x] New pole SAT simulations available at /global/cscratch1/sd/keskital/s4sim/reference_tool/out
[x] wait for https://github.com/CMB-S4/s4sim/pull/8 to be merged
[x] update the hardware configuration dump https://github.com/CMB-S4/s4_design_sim_tool/blob/master/cmbs4_tophat.h5 and crosscheck with tables in DSR
[x] implement CMB tensor from https://github.com/simonsobs/so_pysm_models/issues/48#issuecomment-635722659
[x] rerun the input sky https://github.com/CMB-S4/s4mapbasedsims/tree/master/202002_foregrounds_extragalactic_cmb_tophat
[x] decide if we want to adjust the atmosphere simulations #2
[x] process the input sky in time domain
[ ] implement processing of hitmaps and white noise covariance matrices https://github.com/CMB-S4/s4_design_sim_tool/issues/9
[ ] check the CIB https://github.com/CMB-S4/s4mapbasedsims/issues/3
[ ] rerun the reference simulation tool for r=0 and 3e-3

@keskitalo @smsimon

CMB tensor modes implemented, ran a test simulation for SAT with r=1e-3 (will use 3e-3 for production run), scale is in uK_CMB, seems reasonable given input in https://github.com/simonsobs/so_pysm_models/issues/48#issuecomment-637691952:

I thought we had settled on 0, 1-e3, and 1e-2 to span the range of interest.
Julian
On Tue, Jun 2, 2020 at 12:09 PM Andrea Zonca<EMAIL_ADDRESS>wrote:

CMB tensor modes implemented, ran a test simulation for SAT with r=1e-3
(will use 3e-3 for production run), scale is in uK_CMB, seems reasonable
given input in simonsobs/so_pysm_models#48 (comment)
https://github.com/simonsobs/so_pysm_models/issues/48#issuecomment-637691952
:
[image: image]
https://user-images.githubusercontent.com/383090/83559135-eaec7180-a4c8-11ea-850c-59c4e23f1f85.png
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/CMB-S4/s4_design_sim_tool/issues/13#issuecomment-637749932,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAC4LSUIVB6FAN6ZIRURBM3RUVE7FANCNFSM4NQ4TFQQ
.

@jdborrill see https://github.com/simonsobs/so_pysm_models/issues/48

let's assume https://github.com/CMB-S4/s4sim/pull/8 is fine, beams are final, noise not yet, but I'm not using noise directly so it should be fine.
I'll use the tip of that branch as the instrument model, commit hash c57d15d3ee9beb453cc600435f7eba8d08ff3dcd

@smsimon I was comparing the SAT beams from s4sim (see above) to the ones in the DSR table.
I think MFLS and MFHS are switched, can you crosscheck?

I assumed s4sim figures were correct and produced a new set of input sky simulations.
@keskitalo can you run them through the time domain simulations?
the 4 set of maps you need are described in https://github.com/CMB-S4/s4mapbasedsims/tree/master/202006_foregrounds_extragalactic_cmb_tophat#combined-maps, basically just changed the base folder. The SAT maps are ready, I am running the combining script for the LAT, it will be done overnight.

They are right in s4sim. The column headers in the DSR are wrong here (95/155 is certainly higher than 85/145!). The DSR spreadsheet has them correctly labeled, and it makes physical sense.

ok, @keskitalo has executed the time domain simulations, he needs to rerun the SAT.
So for now I have executed the LAT simulations, need validation.

@keskitalo discovered issue in LAT Chile noise and reran the TOD simulations.
Need to run the tool again pointing at:
/global/cscratch1/sd/keskital/s4sim/reference_tool/out_v1

and then go with the validation and release.

ok I launched atmo + noise again with the new input maps. I'll use the foreground and CMB I already ran before, as I believe nothing changed, (please @keskitalo let me know if this is wrong).
I'm also preparing another CMB tensor set of maps which include TT and EE.

@keskitalo I have rerun the CMB tensors including also TT and EE, I have replaced the old ones in the folder:
/global/cscratch1/sd/zonca/cmbs4/map_based_simulations/202006_foregrounds_extragalactic_cmb_tophat/4096/cmb_tensor/0000

and the 512 folder.
Can you please rerun the TOD simulations of those?

I'll get right on it.

@zonca these maps are ring-ordered, unlike the earlier batch. The pipeline will only work with nested maps. Should I re-order the maps or is it easy for you to do?

I am reordering the maps. They will appear here: /global/cscratch1/sd/keskital/s4sim/reference_tool/cmb_tensor if you want copies in your directory.

sorry @keskitalo completely forgot about ordering, I actually modified mapsims to always save nested from now on so this won't happen again.

Looks like the maps are in uK_CMB. Is it difficult for you to account for that during the co-add?

maps from mapsims are always in uK_CMB, in s4_design_sim_tool instead input foregrounds are in uK_CMB, input noise and atmo are K_CMB, outputs are K_CMB.

The new tensor maps are now in place under out_v1.

thanks @keskitalo can you please fix permissions? e.g. /global/cscratch1/sd/keskital/s4sim/reference_tool/out_v1/00000000/chile_cmb-tensors_LAT_HFL1_filtered_telescope_all_time_all_bmap.fits

Oops! Done.

ok, @keskitalo @jdborrill, the new release is ready at:
/global/cscratch1/sd/zonca/cmbs4/s4refsimtool
next I'll implement weighting of hitmaps and noise cov matrices (the input ones are in /global/cscratch1/sd/keskital/s4sim/reference_tool/out_v1), then I'll proceed with proper validation.
@cbischoff would you like to start checking those maps?

Reran the atmosphere + noise simulations with the fix on efficiency provided by @keskitalo. Now also have hitmaps and noise covariance matrices as implemented in #9.
Working now on validation.

see #14 for validation


Add some new cases

- Trim: "   Please, trim   "
    before: "---please-trim---"
    after: "please-trim"

- Remove multiple spaces: "Multiple   spaces"
    before: "multiple---spaces"
    after: "multiple-spaces"

- Handle strings with a hyphen: "The Strokes - Under Cover of Darkness" / "Keep the hyphen: build-up"
    before: "the-strokes--under-cover-of-darkness" / "keep-the-hyphen-buildup"
    after: "the-strokes-under-cover-of-darkness" / "keep-the-hyphen-build-up"

Hey @francolucas thanks for the PR. A good one! 👏


[BUG] ARM template appears to be modified erroneously by the SDK

Describe the bug
One of the parameters provided in the ARM deployment template appears to be modified incorrectly by the Azure SDK. I'm upgrading the SDK in our system from version 1.18.0 to 1.32.1 and it was working fine on version 1.18.0.
Parameter in the template before submitting deployment request:
{
    "properties": {
        "template": {
            "$schema": "https://schema.management.azure.com/schemas/2015-01-01/deploymentTemplate.json#",
            "contentVersion": "<IP_ADDRESS>",
            "parameters": {
                ...
                ...
                "sfcUserAssignedIdentities": {
                    "type": "object",
                    "defaultValue": {
                        "/subscriptions/<redacted>/resourceGroups/<redacted>/providers/Microsoft.ManagedIdentity/userAssignedIdentities/<redacted>": {}
                        }
                    }
                },

Parameter after submitting the deployment request. The resource Id is broken down into a json fragment. I captured this by adding a logging interceptor on the client side and also observed the same through deployment history on Azure portal.
{
    "properties": {
        "template": {
            "$schema": "https://schema.management.azure.com/schemas/2015-01-01/deploymentTemplate.json#",
            "contentVersion": "<IP_ADDRESS>",
            "parameters": {
                ...
                ...
                "sfcUserAssignedIdentities": {
                    "type": "object",
                    "defaultValue": {
                        "/subscriptions/<redacted>/resourceGroups/<redacted>/providers/Microsoft": {
                            "ManagedIdentity/userAssignedIdentities/<redacted>": {}
                        }
                    }
                },

Code for submitting deployment request:
azure.deployments().define(deplName)
     .withExistingResourceGroup(rgName)
     .withTemplate(templateJson)
     .withParameters("{}")
     .withMode(DeploymentMode.INCREMENTAL)
     .beginCreate();

Exception or Stack Trace
NA
To Reproduce
Provided in the description
Code Snippet
Provided in the description
Expected behavior
The SDK should not modify the ARM template in an inconsistent way.
Screenshots
NA
Setup (please complete the following information):

OS: Linux
IDE : IntelliJ
Version of the Library used: 1.32.1

Additional context
Add any other context about the problem here.
Information Checklist
Kindly make sure that you have added all the following information above and checkoff the required fields otherwise we will treat the issuer as an incomplete report

[x] Bug Description Added
[x] Repro Steps Added
[x] Setup information Added

From debugging a bit, this issue starts from version Azure SDK version 1.23.0 and happens due to FlatteningSerializer which breaks up any json property whose name contains a ..

Looks like a "@JsonFlatten" break this key (interpreting it as "properties.nestedProperty". I will investigate it today.

Caused by a bug in dependency https://github.com/Azure/autorest-clientruntime-for-java/issues/663
This might mitigate the issue. Still double checking with owner of the dependency.
ObjectMapper objectMapper = new ObjectMapper();

azure.deployments().define(deplName)
     .withExistingResourceGroup(rgName)
     .withTemplate(objectMapper.readValue(templateJson, new TypeReference<Map<String,Object>>(){}))
     .withParameters("{}")
     .withMode(DeploymentMode.INCREMENTAL)
     .beginCreate();

Thanks @weidongxu-microsoft! I will give it a shot tomorrow.

Thanks @weidongxu-microsoft! I will give it a shot tomorrow.

The above fix worked for us!

@SukruthKS Good to know the workaround works.
I will continue work with owner of the dependency lib on the fix to root cause. If things work as expected, next release (1.34.0, scheduled on 1st May) should have it fixed.

Dependency not fixed. Mitigated in SDK. To be released for 1.34.0, around 1st May.


Add test to track #508

Also documents the current limitation around ron::Value.
* [ ] I've included my change in CHANGELOG.md

Codecov Report
Patch coverage: 100.00% and no project coverage change.

Comparison is base (4697142) 100.00% compared to head (a9ff062) 100.00%.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff            @@
##            master      #509   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files           78        79    +1
  Lines        11063     11109   +46
=========================================
+ Hits         11063     11109   +46

Files Changed
Coverage Δ

tests/508_value_adjacently_tagged_bug.rs
100.00% <100.00%> (ø)

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


Use correct node in API call

My brain doesn't works sometimes. In the old version before my last PR, the request was made directly to the node that the VM was on. Proxmoxer didn't care who authenticated it so it was opening VNC sessions on random hosts. They were made, but then the code tried to open the websockify on the node the VM was on and it was often saying "uhhhhh I'm not open chief". Now it specifies where it wants to authenticate in that route so the open port and VM host are the same device.
IT ACTUALLY ACTUALLY WORKS IN TESTING

clown


Not compatiple with Windows 10 build 10.0.17134

I get following error when I'm trying to install the nuget package in a UWP application.

Severity	Code	Description	Project	File	Line	Suppression State
Error		Package FileContextCore 2.1.0 is not compatible with uap10.0.17134 (UAP,Version=v10.0.17134) / win10-arm. Package FileContextCore 2.1.0 supports: netcoreapp2.1 (.NETCoreApp,Version=v2.1)			0

The package is compatible with .Net Standard and .Net Core. It is not intended to be used with UWP. Entity Framework Core is not compatible with UWP as well.


feature request: isEmailComment

http://tools.ietf.org/html/rfc2822#section-3.2.3
There's this lovely format of "John Doe"<EMAIL_ADDRESS>which is referred to as an email comment. However, it's not kosher to use ( or \ as you might want to do with "(801) 555-1234<EMAIL_ADDRESS>It would be nice to have an isEmailComment validator to go along with the email validator.

Available in 3.29.0 via #358.


Fix resources should have enum labels

This fixes issue #159. When converting JSON into PowerShell object,
replace enum values with the string label names.

@miroman9364 update your PR description to use one of the supported GitHub syntax for referencing an issue so that it closes it automatically upon merge: https://docs.github.com/en/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword


Adds Edge detection

Here's my super niche setup of Linux and Edge Dev working with no config

This PR switches from "which-chrome" to the underlaying deps mentioned by @texastoland in #86 - these only give strings if a particular copy of the browser exists, so it will iterate though and look through Chromes, Chromiums and Edges.

@orta Hi, this looks great!
Did you try it in combination with Edge Tools?


MNT Use GitHub Actions CI

Issue https://github.com/silverstripe/gha-ci/issues/11Workflow run https://github.com/creative-commoners/silverstripe-simple/actions?query=branch%3Apulls%2F3.1%2Fmodule-standards

CI not appropriate for this module


[QUESTION] Nested schema is not being picked up from model/database, despite the relationship existing and the data being there

First check

[x] I used the GitHub search to find a similar issue and didn't find it.
[x] I searched the FastAPI documentation, with the integrated search.
[x] I already searched in Google "How to X in FastAPI" and didn't find any information.

Description
I have posted this on stackoverflow: https://stackoverflow.com/questions/61724245/fastapi-is-not-picking-up-a-nested-schema-despite-the-data-being-there-in-the-db
but here it is again for those who can't follow the link:
I get an error when trying to return data stored in a relationship between two models. More info below:
models.py (relevant models are Company and Address)
from datetime import datetime

from sqlalchemy.ext.declarative import declarative_base
from sqlalchemy.orm import relationship
from sqlalchemy import Column, Integer, String, Date, Sequence, ForeignKey, DateTime

try:
    from .functions import to_camelcase
except:
    from functions import to_camelcase

Base = declarative_base()

class ToDictMixin(object):
    def to_dict(self, camelcase=True):
        if camelcase:
            return {to_camelcase(column.key): getattr(self, attr) for attr, column in self.__mapper__.c.items()}
        else:
            return {column.key: getattr(self, attr) for attr, column in self.__mapper__.c.items()}

class TimestampMixin(object):
    record_created = Column('record_created', DateTime, default=datetime.now())

class Company(Base, ToDictMixin, TimestampMixin):
    __tablename__ = 'companies'

    number = Column(Integer, primary_key=True)
    name = Column(String)
    incorporated = Column(Date)

    address = relationship("Address", back_populates="occupier")

    def __repr__(self):
        return f"<Company(number='{self.number}', name='{self.name}', incorporated='{self.incorporated.isoformat}')>"

class Address(Base, ToDictMixin, TimestampMixin):
    __tablename__ = 'addresses'

    id = Column(Integer, primary_key=True)
    address_line1 = Column(String)
    address_line2 = Column(String)
    address_line3 = Column(String)
    po_box = Column(String)
    post_town = Column(String)
    county = Column(String)
    postcode = Column(String)
    country = Column(String)
    occupier_id = Column(Integer, ForeignKey("companies.number"))

    occupier = relationship("Company", back_populates="address")

schemas.py
import datetime

from pydantic import BaseModel, BaseConfig
from typing import List

from functions import to_camelcase

class APIBase(BaseModel):
    class Config(BaseConfig):
        orm_mode = True
        alias_generator = to_camelcase
        allow_population_by_field_name = True

class AddressBase(APIBase):
    address_line1 : str
    postcode: str

class AddressCreate(AddressBase):
    pass

class Address(AddressBase):
    address_line2 : str
    address_line3 : str
    po_box : str
    post_town : str
    county : str
    postcode : str
    country : str

class CompanyBase(APIBase):
    number: int
    name: str

class CompanyCreate(CompanyBase):
    incorporated : datetime.date

class Company(CompanyBase):
    incorporated : datetime.date
    address: Address

Relevant call in main.py:
@app.get("/companies", response_model=List[schemas.Company])
def get_companies(
    year: int = None, month: int = None, day: int = None, number: int = None,
    name: str = None, db: Session = Depends(get_db)):

    name = name.upper() if name else None

    arguments = locals()
    arguments.pop("db")

    if not any(arguments.values()):
        return None

    myquery = db.query(models.Company)
    datedict = {}

    for key, value in arguments.items():
        if key == "number" and datedict:
            myquery = crud.get_company_by_date(db, **datedict)

        if not value:
            continue

        if key == 'year' or key == 'month' or key == 'day':
            datedict[key] = value
        else:
            myquery = crud.filter_query(myquery, **{key:value})

    return myquery.all()

Now as far as I can tell from the docs I have got everything set up fine. When I remove address: Address from the Company schema this call will return the correct company/companies without the address data.
I have checked that the relevant address data is associated with the company model by testing
>>> x = SESSION.query(Company).filter_by(number=12544331).one_or_none()
>>> x.address[0].address_line1
'4 VICTORIA COURT'

So I know that the data is in the addresses table, the relationship is set up correctly, and the model and schema works before trying to include the address data in the result. However when I try to access http://<IP_ADDRESS>:8000/companies?number=12544331 I get Internal Server Error and the following error message:
INFO:     <IP_ADDRESS>:50928 - "GET /companies?number=12544331 HTTP/1.1" 500 Internal Server Error
ERROR:    Exception in ASGI application
Traceback (most recent call last):
  File "c:\users\admin\google~1\python\new_co~1\env\lib\site-packages\uvicorn\protocols\http\h11_impl.py", line 384, in run_asgi
    result = await app(self.scope, self.receive, self.send)
  File "c:\users\admin\google~1\python\new_co~1\env\lib\site-packages\uvicorn\middleware\proxy_headers.py", line 45, in __call__
    return await self.app(scope, receive, send)
  File "c:\users\admin\google~1\python\new_co~1\env\lib\site-packages\fastapi\applications.py", line 149, in __call__
    await super().__call__(scope, receive, send)
  File "c:\users\admin\google~1\python\new_co~1\env\lib\site-packages\starlette\applications.py", line 102, in __call__
    await self.middleware_stack(scope, receive, send)
  File "c:\users\admin\google~1\python\new_co~1\env\lib\site-packages\starlette\middleware\errors.py", line 181, in __call__
    raise exc from None
  File "c:\users\admin\google~1\python\new_co~1\env\lib\site-packages\starlette\middleware\errors.py", line 159, in __call__
    await self.app(scope, receive, _send)
  File "c:\users\admin\google~1\python\new_co~1\env\lib\site-packages\starlette\exceptions.py", line 82, in __call__
    raise exc from None
  File "c:\users\admin\google~1\python\new_co~1\env\lib\site-packages\starlette\exceptions.py", line 71, in __call__
    await self.app(scope, receive, sender)
  File "c:\users\admin\google~1\python\new_co~1\env\lib\site-packages\starlette\routing.py", line 550, in __call__
    await route.handle(scope, receive, send)
  File "c:\users\admin\google~1\python\new_co~1\env\lib\site-packages\starlette\routing.py", line 227, in handle
    await self.app(scope, receive, send)
  File "c:\users\admin\google~1\python\new_co~1\env\lib\site-packages\starlette\routing.py", line 41, in app
    response = await func(request)
  File "c:\users\admin\google~1\python\new_co~1\env\lib\site-packages\fastapi\routing.py", line 204, in app
    response_data = await serialize_response(
  File "c:\users\admin\google~1\python\new_co~1\env\lib\site-packages\fastapi\routing.py", line 126, in serialize_response
    raise ValidationError(errors, field.type_)
pydantic.error_wrappers.ValidationError: 8 validation errors for Company
response -> 0 -> address -> addressLine1
  field required (type=value_error.missing)
response -> 0 -> address -> postcode
  field required (type=value_error.missing)
response -> 0 -> address -> addressLine2
  field required (type=value_error.missing)
response -> 0 -> address -> addressLine3
  field required (type=value_error.missing)
response -> 0 -> address -> poBox
  field required (type=value_error.missing)
response -> 0 -> address -> postTown
  field required (type=value_error.missing)
response -> 0 -> address -> county
  field required (type=value_error.missing)
response -> 0 -> address -> country
  field required (type=value_error.missing)

It seems to think that the address data isn't there. I thought this would be something to do with orm_mode in schemas.py as there is lazyloading but I have orm_mode set to True to avoid this (see https://fastapi.tiangolo.com/tutorial/sql-databases/#technical-details-about-orm-mode).
Please, what am I missing?

Ok so I updated
class Company(CompanyBase):
    incorporated : datetime.date
    address: Address

to
class Company(CompanyBase):
    incorporated : datetime.date
    address: List[Address]

and it works! Hooray.
However, I don't want it to display as a list as there will never be more than one address. Is there some other way I can define it? How come address: Address doesn't work?
I am just getting into FastAPI and love it so far, I just want to make sure I completely understand what's going on behind the scenes.

Wow, it is now also incredibly slow when I try to load multiple companies and their addresses. Is their a better way to structure my models / schemas?

The problem turned out to be in my relationships in models. The SQLAlchemy docs helped me understand it (https://docs.sqlalchemy.org/en/13/orm/basic_relationships.html#one-to-one)
Marking as closed now.

Thanks for reporting back and closing the issue @ChrisKneller  :+1:


Add/sanity clean template

Add Sanity studio into the project

https://github.com/user-attachments/assets/0c58c2df-b017-4b5e-b004-14523e6577a2

LGTM!
Just a question: wouldn't we use pages/ instead of app folder?

@neliojrr Good point, this was added automatically when using the Sanity installer. Let me try to migrate it to pages.


Material icons not displaying on mobile Safari (and possibly other browsers)

Possible fix? http://stackoverflow.com/questions/31933785/why-google-material-icons-cant-be-shown-on-mobile

Is this fixed? @leonmak

Oh yea fixed


Problem with extend

Hello
Do you have problem with using @extend on inside breakpoint function?
Maybe you have solution for that?
Example:
.item {
     @include breakpoint($breakpoint_tablet) {
          @extend %helper--clearfix;
     }
}

Result:
.item:after {
     clear: both;
     display: block;
}

Should be:
@media (max-width: 1225px) {
    .item:after {
        clear: both;
        display: block;
        content: '';
    }
}

This is not possible to do in Sass. Please track https://github.com/sass/sass/issues/1050 for progress on Sass allowing this functionality.


[4.2][Hashing] Forward-declare hash_value for tuples.

This allows hash_combine to work on tuples containing no types within the
LLVM namespace, because two-phase name lookup is weird.

@swift-ci please test


Fix blocker.py for windows platform

https://github.com/MadhavBahlMD/Control-Yourself/blob/master/Python/blocker.py

Important: Make sure tohave a backup of your hosts file before testing the blocker.py and backup.py


Support of VS2017-64bit (getting rid of warnings)

Current master issues some warnings (mostly about size_t and int not being the same) when compiling with Visual Studio 2017 (Microsoft (R) C/C++ Optimizing Compiler Version 19.16.27026.1 for x64)
Either the compiler flags (not prefered) or the code would need to be adapted to be able to compile (prefered).
Examples for compile issues are (one out of many many)
crypto\asn1\a_object.c(65): error C2220: warning treated as error - no 'object' file generated
crypto\asn1\a_object.c(65): warning C4267: '=': conversion from 'size_t' to 'int', possible loss of data

one of the major problems seems to be the unclean usage of size_t vs. int (or long or unsigned int) in some files.
woudl a way forward be to make it more consistent and use size_t everywhere?

woudl a way forward be to make it more consistent and use size_t everywhere?

Yes, but unfortunately that is easier said than done. We did do a major effort for the 1.1.1 release to make libssl size_t clean throughout. This was a major job. But libcrypto was not tackled because it is even bigger. Part of the problem is that there is inconsistent use of different integer types, int, long, size_t, unsigned int etc baked into the API (which we can't really change without breaking user apps).
I'd love to do libcrypto too, but so far it's not made it to the top of the priority list.

agreed, this is all but a small thing. it also is onyl an issue for the 64bit version, therefore the need might not be as pressing...

Saw these myself, fwiw a distillation...
Summary by warning (duplicates for file/line removed)

Count
Warning
Description

958
warning C4267
conversion, possible loss of data

92
warning C4244
conversion, possible loss of data

6
warning C4133
incompatible types (usually one volatile pointer type to another)

1
warning C4334
32-bit shift implicitly converted to 64 bits (intended?)

1
warning C4311
pointer truncation (the one case impies void** is safely int*)

Summary by source area (duplicates for file/line removed)

Count
Area

438
crypto

278
test

163
providers

68
ssl

49
fuzz

41
apps

19
engines

1
include

1
ms

Source data: nmake_output_warnings_sorted_unique.txt


Update pyscaffold v3.2.3

Package no longer Python 2.7 compatible
Update pyscaffold v3.2.3
Remove build_script and changes.md
Update environment.yml
Package name changed from pynetCF to pynetcf
Updating travis settings

Currently all codes use import pynetcf and not import pynetCF
Making a new scaffold template with pynetCF would have required to change all codes using the package at the moment

Yeah. Also PEP8 recommends it so lets do lowercase.

@cpaulik thanks a lot for your help!


Create a function to allow modularization for the pressure, temperature and the wind functions

ref #29

[x] create process data function
[x] refactor the temperature, pressure and wind functions in read_data to include function
[x] encapsulate functions that does not need to be accessed by users

Work Session:
2am-3am

encapsulated helper functions
created a process data function


Feature/plus and minus 387

Changed the + and - symbols on the buttons for loading repos and removing repo shortcuts to pictures of repos with + or - in the bottom right corner. I also moved them to the left, so they made sense intuitively with the dropdown. I also added a "Current Repository:" label for the dropdown with a default prompt text of None.

Looks great, thanks!


[Printer] - Multiline string as first function argument breaks formatting

The following function call stays as it is, which is, what I expect.
showDialog(
  `Do you really want to leave this workspace?`,
  ~danger=true,
  ~confirmText="Yes, I am sure!",
  ~onConfirm={() => ()},
)

As soon as I break the multiline string into multiple lines, for example like this:
showDialog(
  `
  Do you really want to leave this workspace?
  Some more text with detailed explanations...
  `,
  ~danger=true,
  ~confirmText="Yes, I am sure!",
  ~onConfirm={() => ()},
)

It gets printed like this:
showDialog(`
  Do you really want to leave this workspace?
  `, ~danger=true, ~confirmText="Yes, I am sure!", ~onConfirm=() => ())

I would expect it to stay like the second example.
(When I move the multiline string to the last position, it gets printed as I would expect.)
Playground example

Yes, this is occurring in our codebase a lot and the current form without indentation is quite ugly. See #35.

@eWert-Online Thanks for the report, this is indeed a bug. Will look into this.
@jfrolich If you see other weird patterns in your codebase, feel free to report them. Will probably have a look at "indented strings" end of Q1 2021.

@IwanKaramazow: Great! This was also an issue with Reason, so not really a regression, but I feel like it's something that exists in almost any modern programming language so it would be good to have it for ergonomics.

@eWert-Online Sorry for the delay, but this is now fixed in master. Thank you so much for the report. This was a complex edge case.
@jfrolich I haven't forgotten about "indented multiline strings", will tackle this at at later time. Jsx4 and custom operators are getting my full attention.

@eWert-Online Sorry for the delay, but this is now fixed in master. Thank you so much for the report. This was a complex edge case.
@jfrolich I haven't forgotten about "indented multiline strings", will tackle this at at later time. Jsx4 and custom operators are getting my full attention.

@IwanKaramazow: You're doing an amazing job with the syntax @IwanKaramazow, love the progress! 🙌

@IwanKaramazow: You're doing an amazing job with the syntax @IwanKaramazow, love the progress! 🙌


Updated Quick Example in readme.

Coverage remained the same at 82.621% when pulling db97e1f871d6d851e2e42caa5a001acea7189cca on eeswr:updates into c2844e708df8ec228a459ad34aae97d6ed346f39 on senecajs:master.

please rerun samples after making the changes

Coverage remained the same at 82.621% when pulling 1a87b52f86102781d2bf8728b002e5d2759ff844 on eeswr:updates into c2844e708df8ec228a459ad34aae97d6ed346f39 on senecajs:master.

Coverage remained the same at 82.621% when pulling 1a87b52f86102781d2bf8728b002e5d2759ff844 on eeswr:updates into c2844e708df8ec228a459ad34aae97d6ed346f39 on senecajs:master.

Coverage remained the same at 82.621% when pulling 1a87b52f86102781d2bf8728b002e5d2759ff844 on eeswr:updates into c2844e708df8ec228a459ad34aae97d6ed346f39 on senecajs:master.

Coverage remained the same at 82.621% when pulling 1a87b52f86102781d2bf8728b002e5d2759ff844 on eeswr:updates into c2844e708df8ec228a459ad34aae97d6ed346f39 on senecajs:master.

Coverage remained the same at 82.621% when pulling 1a87b52f86102781d2bf8728b002e5d2759ff844 on eeswr:updates into c2844e708df8ec228a459ad34aae97d6ed346f39 on senecajs:master.

LGTM


Deploy preview page

https://zenn.dev/nwtgck/articles/1fdee0e84e5808
https://github.com/cloudflare/pages-action

Cannot complete in GitHub
https://github.com/github/pages-gem/issues/724#issuecomment-949782624
https://github.com/orgs/community/discussions/47867


License Mismatch

I noticed you have a mismatched license on this project.
README.md says BSD and LICENSE says MIT.

Good catch. Fixed the Readme file. Thanks! 👍
I really should test this and merge it in one of these days. I recently ported it to zsh and should share that.


Add CONTRIBUTING.md

Copy contribution instructions from README.md and organize them in a contributing file.

completed :)


TinyML (O'Reilly) error running test_hello_world_test

Hi,
I cloned (successfully) the git repository (https://github.com/tensorflow/tensorflow.git) from "TinyML" (O'Reilly). But when I run the command:
make -f tensorflow/lite/micro/tools/make/Makefile test_hello_world_test
I get the following answer:
make: tensorflow/lite/micro/tools/make/Makefile: No such file or directory
make: *** No rule to make target `tensorflow/lite/micro/tools/make/Makefile'.  Stop.
And if I look into the directory "../micro/" I find only a README.md file.
What do I have to do?
Thank you very much for your answer.
André Koller

Hi,
Thanks. I made some progress. Changing zsh for bash, upgrading make to 4.3 and cloned the new repository. But now, when I run:
make -f tensorflow/lite/micro/tools/make/Makefile test_hello_world_test
I get the following error:
tensorflow/lite/micro/tools/make/flatbuffers_download.sh: line 63: wget: command not found
tensorflow/lite/micro/tools/make/Makefile:489: *** Something went wrong with the flatbuffers download: .  Stop.
Can you help?
Looking forward for your answer

I don't know your os but you need to install wget e.g. apt-get install wget on Debian derived OS

Thanks.
I have macos 12.6 (monterey). I'm not shure to understand your answer. Do I have to use Linux  or can I install wget on my mac, for example with homebrew ?

I don't know if the build is official supported on macos so It is better that you open a ticket in the Micro repo directly instead of this repo.
For wget on macos https://stackoverflow.com/questions/33886917/how-to-install-wget-in-macos

WOUWWW!! It worked! I've been stuck on this for days. Many thanks for your help!
..
Testing LoadModelAndPerformInference
1/1 tests passed

I juste had to install wget on macos. Befor this I have been reading tens of web pages, nobody never said something about wget.

Yes, please open a new Documentation issue in the TF micro repo.


Reproduction of results for ESOL and FreeSolv

Hi, thanks for releasing the pre-trained model and the code. Could you share the scripts used for fine-tuning on ESOL and FreeSolv data?
I am more interested in the hyper-parameters. I made the scripts similar to the Lipophilicity script but got way higher RMSE (e.g., more than 1 in case of FreeSolv).
Thanks.

could the RMSE's in the paper have been computed on the standardized values rather than the original ones?.. I think that was also the issue in another (BARTSmiles) llm paper that showed order-of-magnitude improvements in regression tasks.
for example, in the MolFormer repositories' data the lipophilicity values seem to be standardized (centered around 0 and all with ~10 decimal points) whereas the MoleculeNet datasets are in the 0-7 range and fewer decimal points. clarification around the regression datasets' treatment would be very appreciated!

Did you fix this？I tried to replicate the results of these two datasets using the normalized results, and although RMSE has decreased, it still falls short of the indicators reported in the paper.
If you have solved the problem, I hope you can tell me the solution, thank you very much

I think the paper's results are for MolFormer-XL, not the published weights, which are just for the model trained on 10% of the data.


[Feature]: UI/UX Designing- Adding Topic link section 1  and All Topic-Link Integration

Is your feature request related to a problem? Please describe.
1.I propose to create an section for Learn The Basics Of Design
2.Topic-link Integration Into the UI/UX designing

Describe the solution you'd like
No response
Describe alternatives you've considered
No response
Additional context
No response

go ahead @sagarbee


Adds new Wintertodt-Scouter repo.

This is basically the old Wintertodt Scouter plugin, with a new server and repo backing it.
There were some potential issues with memory leaks posted in the Discord, so I made sure to run the memory profiler while using this for a few hours and didn't notice the memory ticking up over that timeframe.

current diff for reviewer since the bot doesn't know the old repo is gone https://github.com/Nouser/wintertodt-scouter/commit/c264e5f3c6a56bcb188538dbf59808046d367135

The author has made their repo public again, can you fork their plugin?

Thank you for your patience! I have now forked the original repo and added a new commit here pointing to the head of that new repo.
Let me know if there's anything you need from me!

The previous code was not working with the new WT widget changes in this week's updates. I changed the IDs and things should be working again.
Please let me know if there's anything you need from me!


Working games

911 Operator, F1 2017 & Think To Die 3 all work.

Thanks for the PR, would you remove the no icon comment as we don’t want to store that, commit message can include that info though. https://github.com/SteamDatabase/SteamLinux/pull/606/commits/febcfeeea8d492b32cd0bea589e86c7992f376f1
Managed to merge the same comment in September that I didn’t notice at the time and will remove it once your changes are in – my mistake.

Done, As it was the first commit I did I couldn't squash them, I can create a fresh PR if you prefer

To fix up the commits you can do:

git rebase --interactive 'febcfee^'
replace pick with edit for febcfee
move the line for bd77335 to below febcfee and replace pick with squash, save and exit editor
edit GAMES.json to have the correct modification (if the squash worked above, it should be correct already)
git commit --all --amend to commit while retaining original commit message
git rebase --continue to get up to date with the last commit 6451c0d which will now have a new hash
git push --force master to get it up to date on your github fork which should automatically refresh this PR :)

Or I can just merge it, tell me what you prefer 😄

As it's already pushed, let's just merge, next time I won't put the comment in the JSON :p

Hm, web editor cannot seem to resolve the conflicts with this branch.

Fixed up in CLI and pushed with https://github.com/SteamDatabase/SteamLinux/commit/7227d1a6a6c56834cf51715f63cc58c9b7557a56, thanks for the contrib!


Breakpoint messages no longer shown when hovering the breakpoint indicator

Debug a node app or extension with node2, but mess up the sourcemaps or something so the breakpoints are gray
You should see a message when you hover the cursor over the breakpoint decoration, but you don't. I do see it when I hover over the breakpoint entry in the sidebar, but not the editor margin decoration.

Via bisect I have found that commit 0614806c12b156959acfcddebf6bd226ef492573 has broken this
Forwarding to @jrieken to investigate further since those util methods might break other stuff as well
Easier repro steps: add a conditional breakpoint, hover over it -> it should show the condition, it does not

Most likely a dupe of #33486
@isidorn How do you create your hover messages? Do you use a stringor something like {language: foo, value: fool_and_code}?

In one of the two ways, both do not seem to work
const glyphMarginHoverMessage = new MarkdownString().appendCodeblock(modeId, condition);
new MarkdownString().appendText(breakpoint.message);
More details https://github.com/Microsoft/vscode/blob/master/src/vs/workbench/parts/debug/browser/debugEditorModelManager.ts#L309