Billing for managed connectors in ASEv3 is not clear

Hi,
In the section https://stackoverflow.com/questions/71513050/logic-app-standard-with-asev3-what-is-the-price-for-managed-connectors it is explained that when using an ASEv3, we are

"charged for the instances used by the App Service plan and for running your logic app workflows. No other charges apply.".

What about managed connectors? Are they included in the ASEv3 price or are they billed like in the Standard model without ASEv3?
Thanks.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 8d714050-c05a-cca9-ed86-fbd8ef223b4f
Version Independent ID: f02d2341-a0ad-19b1-edc1-d6f4f9cd3617
Content: Usage metering, billing, and pricing - Azure Logic Apps
Content Source: articles/logic-apps/logic-apps-pricing.md
Service: logic-apps
GitHub Login: @ecfan
Microsoft Alias: estfan

Thank you for your feedback! We will review and update as appropriate.

Hello @dgrospelier - Yes, operations from managed connectors are metered and billed the same Standard or Enterprise connector pricing as the Consumption plan.
We will now proceed to close this thread. If there are further questions regarding this matter, please reopen it and we will gladly continue the discussion.

Ok but in this article: https://docs.microsoft.com/en-us/azure/logic-apps/single-tenant-overview-compare, there is a table where all Logic Apps SKUs are compared.
And for the ASEv3, there is this statement "Pay only for the ASE App Service plan, no matter the number of logic apps that you create and run.". It should probably be clarified.


Update ember to v1.10.0

Updates the Ember.js library to v1.10.0, which is the current stable version.
Ember Release Builds

Doh, sorry, I merged in a new change that caused a conflict on this. Any chance you can submit an updated PR?

The merge conflicts are fixed

@HeroicEric - Mind updating to 1.11.0?

@rwjblue Sure. Does that mean there is a release coming? :smile:

@HeroicEric - Yep, as of about 10 minutes ago :wink:
http://emberjs.com/blog/2015/03/27/ember-1-11-0-released.html

Thanks for updating!

Updated to the latest versions for both ember and ember-data


scoop の標準レポジトリに投げる？

https://github.com/ScoopInstaller/Main

a reasonably well-known and widely used developer tool (e.g. if it's a GitHub project, it should have at least 500 stars and 150 forks)
https://github.com/ScoopInstaller/Scoop/wiki/Criteria-for-including-apps-in-the-main-bucket

無理

For manifests that don't fit the Main criteria.
https://github.com/ScoopInstaller/Extras#readme

投げるとしてもこっち

https://github.com/ScoopInstaller/Extras/pull/12930


benchdnn : backward RELU convolution error (please document or fix)

Backward conv+RELU benchmarks (BWD_W, BWD_D, BWD_WB) fail in benchdnn:
run: --dir=BWD_W --merge=relu mb1ic3ih227oc96oh55kh11sh4nalexnet:conv1
error [int conv::init_pd(const conv::prb_t*, mkldnn_convolution_desc_t&, mkldnn_primitive_desc*&, res_t*):401]: 'mkldnn_convolution_relu_desc_init(&crd, &cd, 0)' -> mkldnn_invalid_arguments(3)
@@@ error [int conv::doit(const conv::prb_t*, res_t*):459]: 'init_pd(p, cd, cpd, r)' -> 1
0:UNTESTED (errors:0 total:0) __REPRO: --dir=BWD_W --merge=relu mb1ic3ih227oc96oh55kh11sh4nalexnet:conv1
tests:1 passed:0 skipped:0 mistrusted:0 unimplemented:0 failed:1

Please fix or document in benchdnn/TODO.md
I won't look into fixing this backward+RELU issue.
I'm adding iterate-over-impls to benchdnn.
My main goal is to muck with new impls, at benchdnn level and then at mkldnn level.
Other benchdnn issues can wait until my code stabilizes and I prepare a PR for comments, but this may be a while.  If anyone wants benchdnn iterating over impls, I can try to get around to the PR it a little bit sooner.

Hi @kruus,
MKL-DNN doesn't support merged conv+relu for backward pass.
That means neither --dir=BWD_W --merged=relu nor --dir=BWD_D --merged=relu would work.
Basically benchdnn reports that mkldnn_convolution_relu_desc_init() returns mkldnn_invalid_arguments.
Benchdnn as a benchmark doesn't know what is implemented of the library side and what is not. So there is nothing to fix there (except adding the implementation in MKL-DNN of course). Maybe more meaningful warning regarding chosen configuration...
Or maybe I missed something.

You didn't miss anything. Thanks for clarification that this "works as intended". I'll add a note to docs.

I saw you added some documentation regarding c vs c++ and data types. Looks cool... 👍
We'd better have something like that as well to simplify developers' life...

old notes-to-self upon a first look at the code... needs cleanup and updates, now that I look at it again. Adding doc update PR to my [long] todo list.

Oh, while I've got a thread, I finally think I found the source of a segfault issue that I noticed
months ago, and that came back to haunt me this week. The segfault happens (sometimes)
when you call mkldnn_primitive_desc_iterator_destroy (file primitive_iterator.cpp).
One way to fix it could involve setting pd_ back to nullptr within operator++ :
    primitive_desc_iterator_t &operator++() {
        if (pd_){
            delete pd_;
            pd_ = nullptr;
        }

helping the destructor not to double-delete pd_:
    ~mkldnn_primitive_desc_iterator() { if (pd_) delete pd_; }

(Thanks for clues, valgrind!)

After above bugfix, benchdnn iterate-over-impls code shaping up nicely:  with new bench_mode ALL (so --skip-impls becomes usable), just need to massage the stats/output code a bit more. Nice to use benchdnn --mode=ACP -skip-impls=ref and see the huge performance difference between avx2 and sse2 (and that all tested impls were correct) :smile:

Critical bug squashed in PR 135


Unnecessary production dependencies

I have found this dependencies in your project, most of them are unnecessary:
  "dependencies": {
    "@types/express": "^4.17.3",
    "@types/yup": "^0.26.33",
    "express": "^4.17.1",
    "http-status-codes": "^1.4.0",
    "ts-node": "^8.8.1",
    "typescript": "^3.8.3",
    "yup": "^0.28.3"
  },

typescript + @types/* + ts-node - should be located in "devDepencdencies"
express + yup - are required only for "typescript types". Maybe this dependencies should be located in "peerDependecies"? or "devDependencies" also?

Thanks for sharing! I've moved most of these. Will double check how to proceed with express and yup. Feel free to open a PR ;)


Fix some jsonDouble unlawfulness

For example, before this change:
scala> import io.circe.{ Json, JsonNumber }
import io.circe.{Json, JsonNumber}

scala> import io.circe.optics.JsonOptics.jsonDouble
import io.circe.optics.JsonOptics.jsonDouble

scala> jsonDouble.getOption(jsonDouble.reverseGet(Double.NaN))
res0: Option[Double] = None

scala> val json = Json.fromJsonNumber(JsonNumber.fromString((BigDecimal(Double.MaxValue) + 1).toString).get)
json: io.circe.Json = ...

scala> jsonDouble.getOrModify(json).fold(identity, jsonDouble.reverseGet)
res1: io.circe.Json = 1.7976931348623157E308

scala> json == res1
res2: Boolean = false

This is another issue turned up by #400, but I've also added two tests specifically for the corner cases that previously broke the laws.

Current coverage is 81.05% (diff: 100%)

Merging #406 into master will increase coverage by 0.19%

@@             master       #406   diff @@
==========================================
  Files            63         63
  Lines          1996       2001     +5
  Methods        1841       1845     +4
  Messages          0          0
  Branches        155        156     +1
==========================================
+ Hits           1614       1622     +8
+ Misses          382        379     -3
  Partials          0          0

Powered by Codecov. Last update 947ba2e...ed3ea5b


disposeResponse_ and disposeClient_ are always true, why check?

The generated C# client is declaring two local variables disposeResponse_ and disposeClient_
and initialising them to true.
Later on, in a finally block they are read to check if the response_ and client_ can be disposed respectively.
Between the initialization and the read, both variables are not updated. Or at least it is not very intuitive .
Either the check is unnecessary or there is missing code that updates the aforementioned variables.
See screenshot:

Please have a look at the template file and you'll understand how convoluted the cases are.
In your case, the check is not useful, but in some cases, e.g. when a file is downloaded from the API and the stream is returned, you don't want the code to dispose the response and let the caller do that.
It would be unnecessarily complex to precompute whether this is needed in the template.

Hi @jeremyVignelles thanks for your quick response.
It doesn't matter the complexity of the template. That's a result of the complexity of the problem that you guys are solving. From what you are saying I understand that there are different scenarios for disposing each variable. The problem is that this code is critical and needs to be addressed on a case basis.
On a side note, it's  less usual to download files than CRUD operations on a web API, therefore, normal requests shouldn't be penalised at runtime because of the special case/cases.
Are there more cases other than the file download?

Did you benchmark the cost implied by this code? it's possible that the compiler is smart enough to remove the useless code

It is not responsibility of the compiler make optimisations across different blocks try  and finally.
Even more, in the previous version there was a null check before disposing it, why it could be null?

If you really care about perf, there are a lot of ways you could improve the template to fit your need. I'd argue that it would be way more performant to not use the code generation and do the http call by hand.
NSwag just tries to work  for many use cases out of the box, and if it introduces a useless variable, I'm fine with that.
Now, if you want to try and make the PR that would solve that without breaking anything nor adding complexity to the code base, please do 🙂

@jeremyVignelles  'by hand' can be equally performant to generated as long as you differentiate each case and do an exercise of abstraction of each scenario. None else than you guys now the intricacies and knock-on effect on other parts of the code.

Also, the pattern to handle the disposal of unmanaged memory can be done in a single try-catch-finally block with no interference of other variables:
finally
{
    if (response_ is object)
    {
        response_.Dispose();
        response_ = null;
    }
    if (client_ is object)
    {
        client_.Dispose();
        client_ = null;
    }
}

client_ and response_ are not nullable anymore, because that would otherwise force us to check for nullability before using every time in a context where Nullable References are enabled. This is why I replaced them with the disposeResponse_ and disposeClient_ boolean.
As for the single finally block, you can't do that, because the response_ is declared in the using(request_) block, and if you would like to declare it outside, you'll have to declare it as nullable, and you don't want to check for null every time.
Semantically, there's no reason response_ and client_ could be null, it's just that we don't want to dispose them under certain circumstances.


Documentation: Clarify declaration files and the declare keyword

TypeScript Version:  2.8.0
Search Terms:
document declaration files
** Issue**
It doesn't look like you actually define what a declaration file is in your documentation. For instance, your introduction to these at https://www.typescriptlang.org/docs/handbook/declaration-files/introduction.html tells me you're going to help me learn how to write them, but not what they are or why I'd want one.  But, I don't think this makes it easy for a newbie to understand.
Similarly, you don't seem to explain when the declare keyword is, or when it should be used (as far as I can tell, it is used when you need to tell the compiler that the module/library/whatever has a value of some type).
You also seem to make some references to the global namespace (declare global { ... })), but don't seem to directly explain it anywhere.
Code
n/a
Expected behavior:
n/a
Actual behavior:
n/a
Playground Link:
n/a
Related Issues:
n/a

+1. This issue still exists and has caused confusion in TypeStrong/ts-loader#1036.
The documentation fails to explain the role of .d.ts files and how they differ from .ts files.

Just in case it helps someone understand, I accidentally found this short section which compares .d.ts files to .h files in C/C++: https://www.typescriptlang.org/docs/handbook/namespaces.html#working-with-other-javascript-libraries (GitHub)


ECOS solver failed

Describe the bug
Got error ECOS solver failed. I have provided the list of solvers(ECOS,SCS,OSQP) to the optimization problem. Goal of the problem is to adjust projected sales into area ,product and period wise. For few countries ECOS is working with zero delta.
Total known sale 2,831,989,482.8; Total projected 74,629,475,848.6. Delta : 71,797,486,365.8. (96.2%)
Total actual sale: 2,831,989,482.8; Delta (projected-actual) : 71,797,486,365.8. (96.2%)
ECOS Failed for period 2000269. Moving to the next solver
Solver 'ECOS' failed. Try another solver, or solve with verbose=True for more information.
OSQP Failed for period 2000269. Moving to the next solver
Problem could not be reduced to a QP, and no conic solvers exist among candidate solvers ({'qp_solvers': ['OSQP'], 'conic_solvers': []}).
SCS Failed for period 2000269. Moving to the next solver
These are the constraints and objective function:
A = vstack((Product_pa_importance*A_products, A_areas))
b = np.concatenate([Product_pa_importance*b_products, b_areas])

nx = C.shape[1]
nA = A.shape[0]
if verbose:
    print('removing zeros')
    print(nx, nA)
nx = C.toarray().shape[1]
gc.collect()

x = cp.Variable(nx)
objective = cp.Minimize(cp.norm(A @ x - b.flatten()))
tol = 0
constr1 = A_products @ x - b_products.flatten() <= tol
constr2 = b_products.flatten() - A_products @ x <= tol
constr3 = xmin <= x
constraints = [constr1, constr2, constr3]

prob = cp.Problem(objective, constraints)
return prob, x, inds

for solver, solver_name in zip(lst_solvers, lst_solvers_name):
        # TODO better deal with qwargs?
        if lst_solvers_name in ['ECOS', 'OSQP']:
            eps_abs, eps_rel = 1e-5, 1e-5
        else:
            eps_abs, eps_rel = 1e-6, 1e-6

Expected behavior
need delta value zero. ECOS should work
Output
This output is for different data for which ECOS is working
total sales projected:          208,577,503.2
total area_sales_acv_predicted: 208,577,503.2
Total known sale 164,847,493.2; Total projected 208,577,503.2. Delta : 43,730,010.0. (21.0%)
Total actual sale: 164,847,493.2; Delta (projected-actual) : 43,730,010.0. (21.0%)
ECOS for period 2000261 status: optimal
ECOS , Succeed for period 2000261 (channel=DataFrame[store_id: bigint, period_id: bigint, channel: string])
Total adjusted sale for 2000261: 208,577,503.2; Total projected 208,577,503.2. Delta: -0.0. (-0.0%)
Version

OS:
CVXPY Version: 1.3.0
Please suggest solution

This sounds like an ECOS issue, not a cvxpy issue. Can you try clarabel, which should also be installed?

Ok. I will try clarabel solver. Thank you

Closing here, feel free to reopen if needed.


Nextjs builds fail with Sentry and headlessui

Environment
What version are you running? Etc.
"@headlessui/react": "^2.1.5",
"@heroicons/react": "^2.1.5",
"@sentry/nextjs": "^8.28.0",
"next": "14.2.8",
"react": "^18",
"react-dom": "^18"
I've created a point-in-time backup of my current working project here: https://github.com/brandinchiu/sentry-build-error
Disabling reactComponentAnnotation will allow the build to complete successfully.
Steps to Reproduce

followed this tutorial to get Sentry installed on a blank Nextjs project: https://docs.sentry.io/platforms/javascript/guides/nextjs/
create a page in Nextjs that makes use of a  component from headlessui/react
attempt to build the application with reactComponentAnnotation enabled.

Expected Result
Build should complete.
Actual Result
Build fails.  Error is throw indicating that Nextjs prerendering failed when trying to inject Sentry annotations into components:
Error occurred prerendering page "/". Read more: https://nextjs.org/docs/messages/prerender-error

Error: Passing props on "Fragment"!

The current component <Menu /> is rendering a "Fragment".
However we need to passthrough the following props:
  - data-sentry-element
  - data-sentry-component
  - data-sentry-source-file
  - data-headlessui-state

You can apply a few solutions:
  - Add an `as="..."` prop, to ensure that we render an actual element instead of a "Fragment".
  - Render a single element as the child so that we can forward the props onto that element.
...

Hi @brandinchiu, have you tried any of the solutions of not using a fragment?

It's an external UI kit, so I have limited control in this case.
Regardless, fragments are a fairly common react construct. Causing all builds to fail if one exists anywhere in the component tree is a bit extreme, imo.

@brandinchiu
Yes, but the error is not originating from Sentry but from headless ui. You could just render the headless menu as a div for example: <Headless.Menu as="div" {...props} />;
This should fix your error 👍

Respectfully, I disagree with the premise that this is a headlessui issue. I don't even think it's a Sentry issue.
But the Venn diagram here creates a legitimate problem, and I just can't see the solution being "never use a naked fragment as long as Sentry is installed".
Or, this needs to be clearly documented as a drawback that anyone who uses react can't use fragments without an as clause with Sentry (if this IS already documented somewhere, please share a link).
I am not working directly with headlessui. I am working with another UI kit that builds on top of headlessui.
Your suggestion above suggests that using a fragment without an as prop is wrong, and the best solution here is to just never do it.
As I mentioned in my first reply, this feels exceptionally harsh.

Well the thrown error from your reproduction repo is coming from headless ui and that is what I pointed out in my previous comment.
I'm not suggesting that you should not be using any fragments, but we cannot change the fact that React fragments are not accepting props. So this is rather an implementation detail on how to pass down props to child components and this implementation detail in this case lies in headless ui – for which use case their as prop could be used.

Fair enough. My solution for now will be to simply disable reactComponentAnnotation, as getting into guts of the UI kit I'm using would kind of defeat the purpose of offloading this work.
I'll spend some time with it at a later date to see if there's a way for me to backfill any missing "as" props to sort this out.

I've had exactly the same problem as @brandinchiu – using Catalyst, which is based on HeadlessUI, causes Sentry to error.
It might not be the fault of Headless or Catalyst, but it would be useful to have something in the documentation to say that fragments can cause problems with reactComponentAnnotation. I wasted most of the day yesterday trying to figure out the problem until I realised there wasn't much I could do as it was caused by a dependency two layers deep. I'd even started looking for alternatives to Sentry before stumbling on a Discord comment that led me to this issue.

@MattKevan sorry to hear that you spend so much time debugging this, we'll add a note on our docs!


.babelrc cause error in react native 43 version

I "fix" remove this file

I got rid of this error by installing babel-plugin-module-resolver on my own npm install --save-dev babel-plugin-module-resolver

Can confirm @gpawlik's answer solves the problem.

@JeffreyHyer yes, it works

@gpawlik Thanks for the pointer!

Tried @gpawlik - not working.

@Vivism could you please paste here the full error message?

not working for me as well,
npm install --save-dev babel-plugin-module-resolver
<EMAIL_ADDRESS>/xxx
├──<EMAIL_ADDRESS>└── UNMET PEER DEPENDENCY<EMAIL_ADDRESS>TransformError: xxx/.js Unknown plugin "module-resolver" specified in "xxxxx/react-native-maps/.babelrc" at 0, attempted to resolve relative to "xxxxxx/react-native-maps"

@notlose could you check if babel-plugin-module-resolver appears in the node_modules directory? Maybe removing node_modules directory and running npm install again might help...

@gpawlik finally get it working by serving the js with "npm start" instead of run by xcode.
thanks!

@notlose hi bro, can you say more detail? I have the same problem with you. And I am trying to use the version 0.14.0

I recently made a fresh example build with pods and GoogleMaps with no issues.
https://github.com/alvelig/react-native-maps-pods-example.
Try to check it out or build through the README.MD. If it does not help, let me know.


Kafka ChannelTemplate Spec (numPartitions, replicationFactor) not working for Sequence Flows

Describe the bug
The following fails to create the sequence flow:
apiVersion: flows.knative.dev/v1
kind: Sequence
metadata:
  name: sequence-example
spec:
  channelTemplate:
    apiVersion: messaging.knative.dev/v1beta1
    kind: KafkaChannel
    spec:
        numPartitions: 10
        replicationFactor: 1
  steps:
  ....

Expected behavior
I expect it to behave like the Parallel flows that correctly generates the subscriptions and the appropriately configured channels.
This works fine:
apiVersion: flows.knative.dev/v1
kind: Parallel
metadata:
  name: parallel-example
spec:
  channelTemplate:
    apiVersion: messaging.knative.dev/v1beta1
    kind: KafkaChannel
    spec:
        numPartitions: 10
        replicationFactor: 1
  steps:
 ....

To Reproduce
Steps to reproduce the behavior.

Install Kafka
Install Knative Serving and Eventing
Install Channel yaml files (I tried with both channel-consolidated and channel-distributed, same behaviour)
Create a bunch of Knative services and wired them together with a Parallel and Sequence flows
In my configuration I have a parallel flow folllowed by a sequence flow connected with the reply tag.

Knative release version
Tried on Latest Nightly Build and v0.26.6
Additional context
I need this to be working for Knative to be considered ready for my company projects.

Hi @holoed, thanks for reporting!
There will be a release next Tuesday with the fix, nightly builds should already contain the fix.
Fixed in https://github.com/knative/eventing/pull/5955


Let LightningDataModule return spatiotemporal metadata

Making the LightningDataModule return not only the image, but also spatiotemporal metadata such as:

bounding box (bbox): (xmin, ymin, xmax, ymax)
coordinate reference system (crs): EPSG code
date: YYYY-MM-DD string format

Note:

The bbox and crs is in the raster image's native UTM projection for now, rather than lonlat coordinates.

This is part 1/2 of adding spatiotemporal metadata to the output embedding table later, as mentioned at https://github.com/Clay-foundation/model/issues/35#issuecomment-1839738582.

Gonna leave this up for review for a day or so before merging. Once merged, I'll proceed to work on part 2/2, which is to get the model to output embeddings with spatiotemporal metadata columns!


Throttle messages

@jkemp101 Please take another look. The only race condition I found is that we would possibly swap the order of messages if sending took a long time. This should be fixed now.

@jkemp101 Final changes. Feel free to take another look.


Update CIKM 2022

Which conference does this PR update?

CIKM

Related URL

https://www.cikm2022.org/calls/call-for-full-papers

The deadlines of abstract and paper submission have been postponed for 3 days.

Sorry for the delayed review caused by the Covid-19 pandemic (:з」∠)


Problem with provider that uses family when initialized with custom ProviderContainer and UncontrolledProviderScope

Describe the bug
Getting the following run-time error:
type 'MapTest' is not a subtype of type 'Notifier<Map<String, dynamic>>' in type cast
I have a provider that works great if I use it using the usual ProviderScope call. But, I'm seeing problems when I load the provider in main and override it in a custom ProviderContainer with an UncontrolledProviderScope.
To Reproduce
import 'package:riverpod_annotation/riverpod_annotation.dart';

part 'map_test_provider.g.dart';

/// This provider is used to determine if mock data is used instead of making
/// API calls.
@Riverpod(keepAlive: true)
class MapTest extends _$MapTest {
  String _namespace = '123';

  @override
  Map<String, dynamic> build({String namespace = 'abc'}) {
    _namespace = namespace;
    return {};
  }

  void addMapValue({required String key, required dynamic value}) {
    final newMap = Map.from(state);
    newMap[key] = value;
    state = Map.from(newMap);
  }
}

void main() {
  WidgetsFlutterBinding.ensureInitialized();

  final mapTest = MapTest();
  final providerContainer = ProviderContainer(
    overrides: [
      mapTestProvider().overrideWith(() => mapTest),
    ],
  );

  final scope = UncontrolledProviderScope(
    container: providerContainer,
    child: const MainApp(),
  );

  runApp(scope);
}

Expected behavior
Works fine with this code:
void main() {
  WidgetsFlutterBinding.ensureInitialized();

  runApp(const ProviderScope(
    child: MainApp(),
  ));
}

I have simplified my provider so that I cut out any extraneous stuff that might cause a problem. I also have an important reason to create the provider BEFORE the call to ProviderScope(). I'm sure there's a way to do this but I'm not sure what to do.
I'm not sure if this is a bug in my code or a bug in the generated code, so I thought I'd put it here in hopes someone would understand what's happening.
Thanks!

@rrousselGit Any guidance you can give on this issue? I've talked with several people who had quite a bit of expertise with Riverpod, but they all said it's above their heads and that you'd have to look at this.

Sounds like a bug.I'll check later
But you could do the same thing without an override.

Can confirm that this is a bug. I'll fix this Monday.

You da'MAN!!! I know you do a lot for the community. I'm the Director of Mobile for my company and I've decided to base our new platform on Flutter and I'm using Riverpod as the foundation for that new initiative. My team and I really appreciates the work you've done here. Thanks again for all your efforts.

Consider supporting it financially.

@ToddManUtah
If you can sponsor him or encourage your team to sponsor him at GitHub, that'd be great and helpful for Riverpod :)

I'll definitely get started at donating to the project. My company is going to use Riverpods extensively and should kick in something to make sure the development continues. I'm hoping that Google acknowledges Riverpod soon and makes it part of its base offering like they did with Provider. I've tried the other state management systems and they just don't have the flexibility that Riverpod has. It's a great solution that Remi, and his associates, have made.
Kind of another topic, but someone was saying the code gen will get a lot easier in the future. They were mentioning some new Dart/Flutter functionality that might make code gen unnecessary. Does anyone know what that might be? I know, I'm not giving you much to run with.

It's called static meta programming

I've found the problem. I'm working on a fix, it shouldn't take too long.

By the way, this is completely unrelated but:

class MapTest extends _$MapTest {
String _namespace = '123';
@override
Map<String, dynamic> build({String namespace = 'abc'}) {
_namespace = namespace;
return {};
}

You don't need that _namespace = namespace
_$MapTest already contains a this.namespace variable ;)

Might as well generate overrideWith for all providers while I'm at it :shrug:

Looks like there's no way to add family parameters to overrideWith without a breaking change. I'll therefore delay those to Riverpod v3, and only release the fix for this.

Meh actually I've managed to do it. PR coming soon.

You're AWESOME! Thanks!


Remove preparedness or surge data if the user removes the url

Fix

Not being able to remove cached data, after removing the preparedness URL or surge data

thanks but it's not needed anymore to remove it from the DB then

closing replaced by #299


Signals with private names

In some cases it is desirable to create a signal with a name that doesn't show up in the waveform viewer, such as when a signal is created to hold the results of intermediate computations, or to change shape, and it would just add noise. I propose adding a notion of a "private signal name".
I suggest changing naming rules so that Signal(name="") creates a signal with a private name. Such a signal is translated to a private wire in RTLIL (with a $\d+ name), doesn't get displayed in the waveform viewer, and so on.

The FSM ongoing signals (not the state signal) should be changed to have private names in the 0.5 milestone.

Would this ever be the default for a signal generated by Amaranth, or would a user always have to create it explicitly?

Would this also be the default for some signals generated by Amaranth

Only the ones that are implementation details (currently just with m.FSM() but I think we might have others later).

I think this should be straightforward, I will try to cook up an implementation this weekend and update by Monday.

Thanks!


Enabling LEDs on Siemens IPC127 and PC Engines APU2

This PR is best reviewed commit by commit -- one commit enables blinky lights on Siemens IPC127 and the other one on PC Engines APU2. What's interesting about both is that they both have 3 user-driven LEDs available for us (and Siemens even allows them to be either RED or GREEN). We may want to start looking into more luxurious ledmanager on these types of boxes, but that's for another time. This just brings hardware support in.

Weir that it wouldn't trigger Eden after @eriknordmark approval -- trying again


⚠ Mobitopup has degraded performance

In 7437262, Mobitopup (https://napcard.voz.tech) experienced degraded performance:

HTTP code: 200
Response time: 10250 ms

Resolved: Mobitopup performance has improved in d4e91b2 after 7 minutes.


The orientation information from the image's EXIF data is ignored in ml-backend examples that load images using Pillow.

The orientation information from the image's EXIF data is ignored in ml-backend examples that load images using Pillow.
Although images are displayed with the correct orientation in Label Studio based on their EXIF data, ml-backend examples such as example/tesseract and example/llm_interactive do not adhere to this orientation. As a result, bounding boxes created in Label Studio end up cropping unintended areas when processed by the ml-backend.
This issue is similar to the one discussed here: https://github.com/HumanSignal/label-studio-ml-backend/issues/156

I have created a pull request. I would appreciate it if you could advise me on who to assign as reviewers!
https://github.com/HumanSignal/label-studio-ml-backend/pull/536

Closed as resolved by https://github.com/HumanSignal/label-studio-ml-backend/pull/536


bigquery: table.insert: correct docs

Fixes #2149

I would love to see a test that verifies that this example actually works in v0.49.0 or is it only for v0.50.0? I know that the code I wrote two weeks ago was working fine in the then block which means that the catch block wasn't being thrown for PartialFailureErrors.

I just tried causing a failure using promises, both on master and from the git tag when we released 0.49.0, and the success handler did not trigger, while the catch was executed with the expected PartialFailureError.
The reason why we're not adding a unique promise test is because this method is no exception from how all of our others behave, in terms of how callbacks/promises are handled. By checking that the callback style works, we are simultaneously confirming it works with promises, as we know the promise behavior is consistent across our API.
I'm not sure how to explain this scenario you mentioned in #2149:
  this.table.insert(item, { raw: false }).then((data) => {
      let insertErrors = data[1];
      // --------------------
      // data[1] should be undefined, we only executed this with one argument, the apiResponse
      // --------------------

      if (insertErrors) {
        logger.info(`insertErrors: ${JSON.stringify(insertErrors)}`);
        // Some rows failed to insert, while others may have succeeded.
        insertErrors.map((insertError) => {
          insertError.errors.map((error) => {
            logger.error(`PartialFailureError: BigQuery insert failed due to: ${JSON.stringify(error)}`);
          });
        });
      }
      return message;
    }).catch((error) => {
      throw new Error(`Error inserting into bigQuery for id: "${item.id}": ${JSON.stringify(error)}`);
    });

Could you provide an isolated, reproducible example in that issue if you're still seeing an apiResponse in the success handler that has insertErrors?

OK, that makes a lot of sense. Thank you. I will run some more tests on my end.


Add ReplayQueueDatabases script for replaying many transport queues

When Transport crashes, in some cases it will move the current queue database and logs to a Messaging.old-<date> nested within the queue database path. Then it creates a new, empty queue database. If there is another crash, a new Messaging.old- is created with the previous Messaging.old-<date> nested inside it.
After several crashes, this creates several challenges.

If shadow redundancy was failing, we need to replay these databases. This involves tedious manual work of either pointing EdgeTransport.exe.config QueueDatabasePath and QueueLoggingPath to different folders, or moving the files/folders themselves around.
When there have been over a dozen crashes, the path becomes so deep that both Explorer and PowerShell start to show errors when moving files, depending on the state of LongPathsEnabled.
Even with LongPathsEnabled, EdgeTransport.exe.config cannot handle these deep paths, and Transport will repeatedly crash when pointed to these paths.

This script solves this problem by automating all of this. It uses long path syntax in PowerShell to find these folders, moves them into a short path that can be used in EdgeTransport.exe.config, and replays them one at a time, taking out all the manual work.

Would recommend requiring that the script checks for running as Administrator.
Could also see some issues if someone doesn't run the script in EMS.


fix: optional mysqlWrapper

From my understanding, mysqlWrapper is optional.

Thanks! That was a big oversight

I'll get this released shortly
On Thu, 20 Jun 2019, 20:23 Dave Welsh<EMAIL_ADDRESS>wrote:

Thanks! That was a big oversight
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/lukeb-uk/node-promise-mysql/pull/117?email_source=notifications&email_token=ABEPFVBOGAERUSXQ46A67DTP3PKM5A5CNFSM4HZ3LDAKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODYGLZJI#issuecomment-504151205,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABEPFVDQOS23D2I46SHEYELP3PKM5ANCNFSM4HZ3LDAA
.


Error: Undefined property: Ratchet\Server\IoConnection::$user

Websocket server is refusing connections after some random time of activity (about 12-20 hours) even with supervisor setup. Which cause refresh loop in browser on login. No proxy is used. After supervisorctl restart it is working again as it should.
[2015-09-04 07:43:20] ELFCHAT.ERROR: Error: Undefined property: Ratchet\Server\IoConnection::$user at app/vendor/cboden/ratchet/src/Ratchet/AbstractConnectionDecorator.php line 31 [] []

PHP Version 5.4.44
libevent version 2.0.22-stable
MySQL 5.5.9
ulimit unlimited
Composer packages:
cboden/ratchet               v0.3.3            PHP WebSocket library
doctrine/annotations         v1.2.7            Docblock Annotations Parser
doctrine/cache               v1.4.2            Caching library offering an object-oriented API for many cache backends
doctrine/collections         v1.3.0            Collections Abstraction library
doctrine/common              v2.5.1            Common Library for Doctrine projects
doctrine/dbal                v2.5.1            Database Abstraction Layer
doctrine/inflector           v1.0.1            Common String Manipulations with regard to casing and singular/plural rules.
doctrine/instantiator        1.0.5             A small, lightweight utility to instantiate objects in PHP without invoking their ...
doctrine/lexer               v1.0.1            Base library for a lexer that can be used in Top-Down, Recursive Descent Parsers.
doctrine/orm                 v2.5.1            Object-Relational-Mapper for PHP
elfet/silicone               v1.0.0
evenement/evenement          v2.0.0            Événement is a very simple event dispatching library for PHP
filp/whoops                  1.1.7             php error handling for cool kids
guzzle/guzzle                v3.9.3            PHP HTTP client. This library is deprecated in favor of https://packagist.org/pack...
imagine/imagine              0.6.2             Image processing for PHP 5.3
ircmaxell/password-compat    v1.0.4            A compatibility library for the proposed simplified password hashing algorithm: ht...
kriswallsmith/buzz           v0.15             Lightweight HTTP client
monolog/monolog              1.17.1            Sends your logs to files, sockets, inboxes, databases and various web services
phpunit/php-code-coverage    1.2.18            Library that provides collection, processing, and rendering functionality for PHP ...
phpunit/php-file-iterator    1.4.1             FilterIterator implementation that filters files based on a list of suffixes.
phpunit/php-text-template    1.2.1             Simple template engine.
phpunit/php-timer            1.0.7             Utility class for timing
phpunit/php-token-stream     1.2.2             Wrapper around PHP's tokenizer extension.
phpunit/phpunit              3.7.38            The PHP Unit Testing framework.
phpunit/phpunit-mock-objects 1.2.3             Mock Object library for PHPUnit
pimple/pimple                v1.1.1            Pimple is a simple Dependency Injection Container for PHP 5.3
psr/log                      1.0.0             Common interface for logging libraries
react/event-loop             v0.4.1            Event loop abstraction layer that libraries can use for evented I/O.
react/socket                 v0.4.2            Library for building an evented socket server.
react/stream                 v0.4.2            Basic readable and writable stream interfaces that support piping.
rych/bytesize                v1.0.0            Utility component for nicely formatted file sizes.
silex/silex                  v1.3.2            The PHP micro-framework based on the Symfony Components
silex/web-profiler           1.0.x-dev 2afc6ba A WebProfiler for Silex
symfony/config               v2.7.3            Symfony Config Component
symfony/console              v2.7.3            Symfony Console Component
symfony/debug                v2.7.3            Symfony Debug Component
symfony/event-dispatcher     v2.7.3            Symfony EventDispatcher Component
symfony/filesystem           v2.7.3            Symfony Filesystem Component
symfony/finder               v2.7.3            Symfony Finder Component
symfony/form                 v2.5.0            Symfony Form Component
symfony/http-foundation      v2.7.3            Symfony HttpFoundation Component
symfony/http-kernel          v2.7.3            Symfony HttpKernel Component
symfony/intl                 v2.7.3            A PHP replacement layer for the C intl extension that includes additional data fro...
symfony/locale               v2.7.3            Symfony Locale Component
symfony/monolog-bridge       v2.7.3            Symfony Monolog Bridge
symfony/options-resolver     v2.7.3            Symfony OptionsResolver Component
symfony/property-access      v2.7.3            Symfony PropertyAccess Component
symfony/routing              v2.7.3            Symfony Routing Component
symfony/security             v2.7.3            Symfony Security Component
symfony/stopwatch            v2.7.3            Symfony Stopwatch Component
symfony/translation          v2.7.3            Symfony Translation Component
symfony/twig-bridge          v2.7.3            Symfony Twig Bridge
symfony/validator            v2.7.3            Symfony Validator Component
symfony/web-profiler-bundle  v2.7.3            Symfony WebProfilerBundle
symfony/yaml                 v2.7.3            Symfony Yaml Component
twig/twig                    v1.21.1           Twig, the flexible, fast, and secure template language for PHP

Sorry, i do not know =(

Is it true that we can only choose websocket or AJAX server? Is there a way to switch to AJAX if client can not connect to websocket?

Addition:
[2015-09-12 20:32:24] ELFCHAT.ERROR: Error: Undefined property: Ratchet\Server\IoConnection::$user at app/vendor/cboden/ratchet/src/Ratchet/AbstractConnectionDecorator.php line 31 [] []
[2015-09-12 20:32:24] ELFCHAT.ERROR: Error: Trying to get property of non-object at app/src/Server/WebSocketServer.php line 182 [] []

    /**
     * Remove user from connected clients by ConnectionInterface.
     *
     * @param ConnectionInterface $conn
     */
    private function detach(ConnectionInterface $conn)
    {
        $user = $conn->user;
        unset($this->clients[$user->id]);
    }

And I have a feeling that sessions from elfchat_session are not removed properly (maybe only in my setup, do not sure). $this->app->session()->remove('user') destroys cookie but leaves session in database. Is it expected behaviour?

Finally I have found the solution.
From Stack Overflow:

For php-scripts that run for a long time (a.o. daemons) persistent connections will almost always be dropped by the MySQL-server after a set timeout (depending on wait_timeout).

Modified server.php:
// Loops
$loop->addPeriodicTimer(1, function () use ($app,$controller) {
    if ($app['em']->getConnection()->ping() === false) {
        $app['em']->getConnection()->close();
        $app['em']->getConnection()->connect();
    }
    $controller->gatherMemoryUsage();
});

$ratchet->run();

Cool1 can you create PR?

#5
Actually I don't sure that is most optimal way but it works, server is up and running.

Can you help me install a chat? I cannot install

Can’t do.

Can you help me install the chat or update the chat to a newer version? I love this chat please

Sorry, I'm not interested in any further development of chat. It takes time and money.


Roll back license, add "datastore" wording

Description

Related Issues

Checklist

[ ] Is this code covered by new or existing unit tests or integration tests?
[ ] Did you run make test successfully?
[ ] Do new classes, functions, methods and parameters all have docstrings?
[ ] Were existing docstrings updated, if necessary?
[ ] Was external documentation updated, if necessary?

Additional Notes or Comments

Codecov Report
Patch coverage: 91.66% and project coverage change: -0.14% :warning:

Comparison is base (f60d69a) 79.70% compared to head (25eda51) 79.56%.
Report is 5 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #645      +/-   ##
==========================================
- Coverage   79.70%   79.56%   -0.14%
==========================================
  Files          79       79
  Lines        4819     4821       +2
==========================================
- Hits         3841     3836       -5
- Misses        978      985       +7

Files Changed
Coverage Δ

superduperdb/base/jsonable.py
80.55% <85.71%> (-1.80%)
:arrow_down:

superduperdb/base/config.py
100.00% <100.00%> (ø)

superduperdb/db/mongodb/cdc.py
76.32% <100.00%> (-1.39%)
:arrow_down:

... and 1 file with indirect coverage changes

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


Allow DataProcessor's copy function to be public.

I need this function for various test rigs I am creating for large schemas where copying the DP saves 10 seconds a test for reloading another one just because I can't copy the object.
DAFFODIL-2723

There's some wierdness. E.g., withDebugger's argument is dbg: AnyRef which it then downcasts to Debugger(?) No comment as to rationale (probably I wrote this.... grrrr).
Making copy public is just a quick painless work around.

Is there a bug with the AnyRef used in withDebugger? Should we open a ticket?

Created https://issues.apache.org/jira/browse/DAFFODIL-2724


Is it possible to pick and choose only certain things to markdown?

I would like for the converter to only parse bold, italics and strike-through tags. Is it possible to do this?

Out of the box no.
But you can try to hack around the subparsers with extensions.

Create a lang extension that calls the following subparsers:

italicsAndBold
strikethrough

Store the parsed text in a var and return empty string from that extension
Create an otp ext that returns the stored text

Fiddle
https://jsfiddle.net/tivie/053f2j7z/
Extension code
showdown.extension('myext', function () {
  var store = '';
  var lngExt = function (text, converter, options) {
    var globals = {converter: converter};
    options.strikethrough = true;
    text = showdown.subParser('italicsAndBold')(text, options, globals);
    text = showdown.subParser('strikethrough')(text, options, globals);
    store = text;
    return "";
  };
  var otpExt = function (text, converter, options) {
    return store;
  };
  return [
    {
      type: 'lang',
      filter: lngExt
    },
    {
      type: 'output',
      filter: otpExt
    }
  ];
});


chore(docs): only deploy on master branch

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

GitHub release
v0.83.5

Your semantic-release bot :package::rocket:


STEPS-blending: Losing small scale features in the first time steps and other issues

Hi everyone,
In setting up pySTEPS for a blended nowcast with STEPS, I have noticed that during the first time steps some of the radar image small-scale features are immediately lost.
This becomes particularly apparent when the blended STEPS nowcast is compared to the non-blended version of the STEPS nowcast.
An example over the Belgian radar domain can be seen here:

Fig. 1: Identical starting conditions (i.e. radar field) for the blenden nowcast (left) and non-blended nowcast (right)

Fig. 2: The blended (left) and non-blended (right) nowcast after 1 time step of 5 minutes
It's clear that even after the first time step (Fig, 2), the blended nowcast field has lost some fine-scale structures w.r.t. the non-blended nowcast (i.e. the blended fields seem smoother). In addition, there also seem to be more broad structures with more intense rainfall in the blended nowcast.
When investigating this phenomenon I came across several issues/points of attention in the blending code.
I already discussed some of them with @RubenImhoff, but I will try to explain them here too so everything is well documented.

In order to explore the problem I plotted the time evolution of the Power (displayed as standard deviation [St. Dev.]) of the different cascade levels for the different fields.
For blending nowcast there are 2 relevant fields per level:

the precipitation field
the noise field

Both are evolved separately using an AR(2) model
In addition I also plotted the time evolution of their respective blending weights with which they are combined. I have deliberately omitted the NWP-component as its weight is typically very small during the first time steps.
For the non-blending nowcast there is only 1 relevant field as the noise is directly incorporated in the AR(2) process.
Finally, also included is a figure of the actual fields themselves at a specific time step.
For the blended nowcast:

the AR(2)-evolved precipitation field
the AR(2)-evolved noise field
both fields combined using their respective blending weights

For the non-blended nowcast:

the AR(2) with noise term-evolved precipitation field

Fig. 3: AR(2)-evolution overview for cascade level 6 at time step 1
Fig 3. shows this AR(2)-evolution overview for cascade level 6 (2nd smallest level).
We notice some problems:

The AR(2) evolution of the precipitation cascade without the noise term EPS is no longer stationary in the variance (something that is necessary according to Bowler et al. 2006:
"The noise term has been omitted from this formulation and the cascade is renormalized at each step to ensure no loss of power")
In practice, this means a dampening of the amplitudes (= loss of power) for all cascade levels
The noise starts from 0 and needs to spin-up. For the largest levels (due to the large temporal autocorrelations) this may take a long time.

This results in the following issues:

The precipitation component gets punished twice: Once because the power is decaying due to the AR(2)-evolution and once due to the weighing by the blending weight
Also the noise amplitude is not high enough because the noise needs to spin up (started from zero) and is also weighted by the blending weight.

What does this mean:
For the smallest levels, due to the low temporal autocorrelation, the precipitation field decays very fast and also the blending weight immediately is very low. This mean that the original precipitation signal is almost immediately lost. This can be seen by comparing the blended field from the blended nowcast with the field from the non-blended nowcast (the two right-most panels in the bottom row of Fig. 3).
Additionally also the noise has a reduced amplitude (due to its initialization to zero) which results in a blended field with a too small power (= St. Dev.) as seen in the right-most upper panels in Fig. 3.
For the largest scales, there is also a loss of power in the blended field. This is mainly due to the spin-up of the noise field. Due to the large temporal-autocorrelation they stay close to zero for a long time. Keeping in mind the blending strategy, I guess the St. Dev. of the noise field should be (close to) 1 and the blending weights should handle their contribution to the blended field. But since this is not the case the overall power of the blended fields is too low for the largest scales (as seen by comparing the two right-most upper row panels in Fig. 4).

Fig. 4: AR(2)-evolution overview for cascade level 2 at time step 10
These issues lead to two effects: The first one being the loss of small scale features in the first time steps of the nowcast (which triggered this investigation).
The second one, which is more subtle, being the large scale noise having not enough power in the beginning of the nowcast.
This syndrome can be seen when there is precipitation from the NWP-forecast outside the radar-domain (e.g. in Fig. 2). In this case the noisy fields (since the NWP blending weight is typically rather small) appear with rather small rainfall amounts (which actually gives  them a quite realistic feel, but theoretically their amplitudes are too small.)
Unfortunately there is another problem. Namely with the semi-Lagrangian advection of the small scales.
In the blending nowcast all the different cascade levels need to be advected separately because they need to be blended with the NWP cascade levels. But for the smallest levels this also leads to a loss in power (as seen in Figs. 5 and 6)

Fig. 5: Standard deviation (~ power) of the noise field before and after semi-Lagrangian advection for level 6.

Fig. 6: Standard deviation (~ power) of the noise field before and after semi-Lagrangian advection for level 7.
The reason for this is less clear to me, but I suspect this has to do with the interpolation needed to find the starting points of the advection. Due to the high spatial variance of the smallest levels, potentially a large error is introduced when interpolating.
The non-blending nowcast does not suffer from this because their the levels are recomposed to the total precipitation field before the advection takes place.
Some possible solution:

Renormalize the precipitation cascade after each AR(2) iteration
Initialize the noise cascade with the appropriate noise

I did a first implementation if these ideas which resulted in the following:

Fig. 7: AR(2)-evolution overview for cascade level 6 at time step 1 after adaptation

Fig. 8: AR(2)-evolution overview for cascade level 2 at time step 10 after adaptation
As Figs. 7 and 8 show, the blended cascade levels now have again the correct St. Dev. (or power) after the AR(2) evolution.
The resulting nowcast is shown in Fig. 9

Fig. 9: The blended (left) and non-blended (middle) and adapted-blended (right) nowcast after 1 time step of 5 minutes
As you can see the adapted nowcast retains better the small-scale features in the first time steps. Also notice the precipitation outside the radar domain immediately coming in at full power (a result of the noise component of the large scales having the correct power).
However, these adaptations still have some drawbacks:

renormalizing the precipitation field after the AR(2) evolution results in a constant precipitation field. So this technique is not ideal. An option could be to use the localized version of the AR(2) process, but this becomes quickly very computationally intensive
No fix is found for the loss of power in the small scales due to the semi-Lagrangian advection. This is also seen in the power spectrum shown in Fig. 10.

Fig. 10: Power spectrum of the radar field, blended nowcast, non-blended nowcast and adapted blended nowcast after 1 and 2 time steps. From this graph it is clear that even after the first time step the blending nowcast loses power at the small scales, while this is not the case for the non-blending nowcast. The adapted blending does perform better but there is still some loss of power in the smaller scales.

@ladc and myself have reserved some time in July to further investigate this issue.
Comments and suggestions are much appreciated.
Kind regards,
Michiel

Hi @mpvginde,
Many thanks for this thorough analysis! We already discussed it earlier, but I'm very happy to see you went through the code and these results in so much detail. And good to see this as a pysteps issue now, so that we can think along in coming up with a solution.
Regarding initializing the noise cascade with the appropriate noise, I think this is the way to go and what you have tested, could in my opinion directly be implemented in the code.
Regarding the renormalization, I remember that @ladc and I discussed this and I can't entirely remember why we decided not to implement that (directly). I think we were worried about any issues at the end of the forecast when the x times renormalized cascades had to be recomposed. Have you tested this by any chance? If there are no issues, I think this would be a great addition as well. The localized version of the AR(2) process would even be better, perhaps this is eventually the way to go for the blending procedure. Maybe we should consider this as step 2 in the improvements? I can imagine that the localized version also takes somewhat more implementation time.
Finally, regarding the semi-Lagrangian advection related issues, perhaps @pulkkins has ideas here?
Cheers,
Ruben

Very interesting issue and a lot of detail to digest!  Many thanks for the analysis @mpvginde!

The noise starts from 0 and needs to spin-up. For the largest levels (due to the large temporal autocorrelations) this may take a long time.

I agree this doesn't sound right. Should we consider it as a bug or does this follow the original formulation in the paper? Can you submit a PR with the fix you've tested above?

The AR(2) evolution of the precipitation cascade without the noise term EPS is no longer stationary in the variance (something that is necessary according to Bowler et al. 2006

Again, should we consider this a bug? From you answer @RubenImhoff , it seemed that it was rather a design choice, was it?
Finally, I'd like to ping @albertocarpentieri here, since he encountered a similar issue in his work (preprint ), although it was related to the extrapolation only case without blending. But he also added a renormalization step after each AR iteration, so maybe there is a more general solution that we can discuss with respect to this?

@mpvginde I sent you an invitation to join the pysteps organization. Feel free to create new branches directly in the pysteps repo.


Create a slingfeature

For easier consumption it would be great if composum would be packaged as a slingfeature ( just a list of bundles in txt format ).
I've added an example of how this could be done in my fork at https://github.com/ist-dresden/composum/compare/master...rombert:slingfeature

cross ref: https://issues.apache.org/jira/browse/SLING-5292

Note that the SLING issue refers to deploying Composum to the Karaf launchpad, which is not part of the default Sling launchpad. Having a Composum slingfeature would make it simpler to consume it in a slingstart-based application.


Topic recognition

Detection and classification of skin lesions on the ISIC2017 dataset using YOLOV7 architecture

This is an initial inspection, no action is required at this point
Difficulty: Normal
Readme:
Poor

no insights/discussion/interpretation of results
no description about how the YOLOv7 algorithm works
no training/testing loss or accuracy(mAP) plots shown
no detection results shown in readme (some images are included in the reults folder)

Commit messages:
OK
Code:

Only has Jupyter notebooks, does not have the file structure required
Uses an open source YOLOv7 implementation by someone else, with command line arguments
No hyperparameter tuning or attempts to improve performance

Functionality/Performance:

Classification accuracy is below 0.8 for all classes
No detection results shown/No IoU metrics shown

Thanks for the feedback, obviously a lot of stuff I didn't deliver on during the initial push. I have now done a series of changes, most related to the readme and documentation of the project. I hope this is sufficient.
When it comes to the structure of the project with filenames as model.py, train.pyy etc I find this difficult to implement given the fact that I use the yolov7 library. If I were to follow this rigid structure I would just add more unnecessary code, hope you understand my point of view on this.
Again thanks for the feedback.

Marking
Some parts marked as per content for due date
Good Practice (Design/Commenting, TF/Torch Usage)
Adequate design and implementation, YOLOv7 external implementation -4
Good spacing and comments
Header blocks missing -1
Recognition Problem
Solves problem
Driver Script present
File structure not present, needs to be in own folder -2
Shows Usage & Demo & Visualisation & Data usage, no detection results initially shown -2
Module present
Commenting
No Data leakage
Difficulty: Normal -5
Commit Log
Meaningful commit messages
Progressive commits used
Documentation
ReadMe good but missing refs -1
Model/technical explanation
Good Description and Comments
Markdown used and PDF submitted
Pull Request
Successful Pull Request (Working Algorithm Delivered on Time in Correct Branch)
No Feedback required
Request Description minimal -1

Cannot be merged as external implementation of YOLOv7, otherwise grade normally.


Stop tabs from being deactivated

I'd like to be able to stop an active tab from being deactivated. Is there a setting for this?
You can see the behaviour on http://www.landcoalition.org/en/resources if you expand the filters and then click on a tab twice. It will toggle between active and inactive states which is odd as the collapsing of the panel has been disabled for tabs.

The tabs shouldt be deactivated, and I can't reproduce this in my demo. I can see the thing happening on your page, could you share your configuration?

Hi, thanks for getting back to me. My config is:
wrapper.responsiveTabs({
  startCollapsed: 'accordion',
  collapsible: 'accordion',
  animation: false,
  animationQueue: true,
  duration: 200,
  active: 0
});

Weird, I've tried your exact config, and for some reason I still cant reproduce this.. It feels like there is something on your website that is interfering with this. Unfortunately I don't have any time to dive more deeply into this..

No problem, thanks for looking though!

 I'm going to close the issue for now, as I can't properly reproduce this with a clean project. If you run into the issue again with a different setup or have a clean example for me, feel free to reopen :)


Hombli TRV no longer detected

Describe the bug
In the prior release we added support for the Hombli TRV device. I installed 9 of the devices and got it all working using a dev version before the 'official' realase version.
Now have tried to ad a 10th device using the latest release. It no longer identifies the device according to the Hombli profile. It is detected as:
hama_radiator_controller
tuya_smart_zigbee_door_sensor
The profile for Hama does not include all the options currently available on the other devices using the Hombli profile.
To Reproduce
Try to install a Hombli TRV device. It is not identified correctly.
Expected behavior
It should be offered at the same time as the 2 other possible devices.
Additional context
I wanted to add support for DP 104 (valve state) but this wasn't working either. I think it has to be manually requested from the device?
If the bug involves a device, then please include device diagnostics from
Settings / Devices & Services / Tuya Local (your device) / "1 device"
Please check if there are messages from Tuya Local in the Home
Assistant log (Settings / System / Logs), and include those too.
If applicable, add screenshots to help explain your problem.
tuya_local-b8923bc411486aa548ba459fc7a5331a-Kitchen Radiator-b1390045808d50967d2b27f80b6e1448.json.txt

I've tried going back to the December release with the pre-merged version of the file. Something's not right as that doesn't work either. I dug into the logs:
[custom_components.tuya_local.helpers.device_config] Loaded device config hombli_thermostatic_radiator_valve.yaml 2024-02-07 16:34:25.089 DEBUG (MainThread) [custom_components.tuya_local.helpers.device_config] Not match for Radiator Thermostat, missing required DPs: [{'23': 'str'}]

Solved by adding optional: true to dps 23. :) Not sure is this was a firmware change that stopped reporting it...?


OUT OF GAS error, when running test_registry.py

the issue is that we get an OUT OF GAS error, when running the following test: https://github.com/brainbot-com/raiden/blob/truffle/raiden/smart_contracts/tests/test_registry.py using py.test. We got it working with Hydrachain, but not with tester.py.

closing. please reopen if you can provide a minimal failing test.


rgbd_launch: 2.3.0-1 in 'noetic/distribution.yaml' [semi-bloom]

Increasing version of package(s) in repository rgbd_launch to 2.3.0:

upstream repository: https://github.com/ros-drivers/rgbd_launch.git
release repository: https://github.com/ros-gbp/rgbd_launch-release.git
distro file: noetic/distribution.yaml
bloom version: 0.9.7, but PR is made manually due to https://github.com/ros-drivers/rgbd_launch/issues/48#issuecomment-637884114
previous version for package: None

@sloretz Thank you for the catch. Since this release unblocks downstream pkgs, I'd like this to be merged sooner. Then I can make a subsequent release.


Fixed typo 'occured' to 'occurred'

message

This PR fixes #

Thank you!

Thank you too @alexdima !


Add support for multiple CA certificates

[Edited to reflect behaviour for DER as well, and to clarify a little what the desired functionality is.]
From https://docs.rs/mysql/20.0.1/mysql/struct.SslOpts.html#method.with_root_cert_path :
"If you have multiple certificates in a .pem file, only the first one will be loaded." (Out of date? I get a TlsError in this case: "One or more parameters passed to a function were not valid.")
For a DER bundle, I get a TlsHandshakeError: "The certificate was not trusted." It would appear to me that some changes have been made in the native-tls crate since this bit in the mysql crate documentation was written.
The IT architecture for one of our customers however was designed with the understanding that cross-region (AWS) DB connections should be supported. Therefore we are keen to use bundle files, like those that AWS provides.
I can see that you're using add_root_certificate ( https://docs.rs/native-tls/0.2.4/native_tls/struct.TlsConnectorBuilder.html#method.add_root_certificate ) behind the scenes, but I see no way of accessing that functionality via the mysql crate as its API revolves around a single CA certificate.
Would it be possible for you to add support for specifying multiple CA certs and / or a bundle file?
Thank you in advance!

@dv-ds, hi!
Sorry for delay. Could you please try this branch with multiple pem certs in single file?

Tested PEM bundle on Linux and looks OK with that branch!


make: entering an unknown directory

So I'm running now in a Red Hat 7.4 environment with the pod_X1Y1_ruche_X16Y8_hbm machine, using the Xcelium platform from the xcelium branch, and trying the run the make regression command. I've been able to get most of the SPMD tests to work, but very few of the CUDA examples. Here are the SPMD tests I've had to remove (in bsg_replicant/examples/spmd/Makefile):

At first, I got an error like "make: entering an unknown directory", but now when I comment out these substitutions and allow the test to run I get something like this for each:

And in bsg_replicant/examples/cuda/Makefile, the only tests I could leave uncommented was test_empty_parallel, test_dma, and group_stride. I also had to comment the test_loader test in bsg_replicant/examples/python/Makefile. Any ideas for debugging these tests?

That is... very odd.
@dpetrisko Set up the xcelium platform. Can you weigh in?

Dan was actually the one who recommended I open an issue an issue here xD But maybe he'll have some more input if there aren't any other ideas you might have

If @dpetrisko can give me instructions for running it at UW, I'll try it here. I haven't seen this error before, and all those tests run here.

I don’t think it has to do with xcelium, as it’s failing before make is even getting to the test directory?
just switching to the xcelium branch and switching the platform to xcelium will reproduce our setup

How are you setting XRUN? (I think I missing some cadenv variable)

I had to run setenv XMSIM xmsim and setenv XRUN xrun in my terminal before running make regression. Not sure if there's a better way of doing it though

My question was directed toward Dan. There's a standard way at UW that I don't have a branch for yet

Ah, found it. An oddity I'll figure out later

I see two issues, so far. The first is simple, and for @dpetrisko. svdpi.h isn't being included:
diff --git a/libraries/platforms/bigblade-xcelium/library.mk b/libraries/platforms/bigblade-xcelium/library.mk
index 89ab8c5e..adafaab2 100644
--- a/libraries/platforms/bigblade-xcelium/library.mk
+++ b/libraries/platforms/bigblade-xcelium/library.mk
@@ -49,6 +49,7 @@ $(PLATFORM_OBJECTS) $(PLATFORM_REGRESSION_OBJECTS): INCLUDES += -I$(LIBRARIES_PA
 $(PLATFORM_OBJECTS) $(PLATFORM_REGRESSION_OBJECTS): INCLUDES += -I$(LIBRARIES_PATH)/platforms/dpi-verilator
 $(PLATFORM_OBJECTS) $(PLATFORM_REGRESSION_OBJECTS): INCLUDES += -I$(BSG_MACHINE_PATH)/notrace/
 $(PLATFORM_OBJECTS) $(PLATFORM_REGRESSION_OBJECTS): INCLUDES += -I$(BSG_PLATFORM_PATH)
+$(PLATFORM_OBJECTS) $(PLATFORM_REGRESSION_OBJECTS): INCLUDES += -I$(XCELIUM_RELEASE)/tools.lnx86/include/
 $(PLATFORM_OBJECTS) $(PLATFORM_REGRESSION_OBJECTS): INCLUDES += -I$(BSG_MANYCORE_DIR)/testbenches/dpi/
 $(PLATFORM_OBJECTS) $(PLATFORM_REGRESSION_OBJECTS): INCLUDES += -I$(BASEJUMP_STL_DIR)/bsg_test/

The second is weirder, and I'm not sure it solves your issue but it solves another one I encountered. #786 fixes some outdated link flags. When I rebase the xcelium branch on fix_pod_repl, the issues I was seeing go away.
Neither issue resolves what you described, but I can now run any CUDA test just fine.

You can checkout my changes at dr-xcelium

Awesome, feel free to push your changes to the xcelium branch itself

I rebased, so it would be a force. That's why I was hesitant

The xcelium binary should automatically include svdpi by default (and this did work for me) but this is probably a safer choice. Although XCELIUM_RELEASE isn’t necessarily a standard variable. Maybe we add an error if it’s not defined?

I’m not particularly sentimental about git history

Me either, but I don't like force pushing branches that are actively being used by others :)

I just force pushed the xcelium branch after merging #786. I also brought it up to feature parity with VCS.
In other words, this branch should work, along with the force pushed branch from bsg_manycore

I force pushed both xcelium branches a couple days ago to bring them up-to-date. You can run git fetch and then git reset --hard origin/xcelium to collect the changes without recloning.
And yes, you need to change bigblade-vcs to bigblade-xcelium. Our default platform is vcs.

That is probably because we set the variable XCELIUM_RELEASE, to the path of our xcelium installation. You should set that variable, and we'll add a check for it in our makefiles (@dpetrisko)
For example, we set these in a makefile fragment that we include in our projects:
CADENCE = /opt/cadence

# Release dirs
XCELIUM_RELEASE = $(CADENCE)/XCELIUM2109

# Bin dirs
XCELIUM_BIN   = $(XCELIUM_RELEASE)/tools/xcelium/bin
SIMVISION_BIN = $(XCELIUM_RELEASE)/tools/simvision/bin

export XRUN      = $(XCELIUM_BIN)/xrun
export XMSIM     = $(XCELIUM_BIN)/xmsim
export SIMVISION = $(SIMVISION_BIN)/simvision

The line that is silently failing and causing this issue is here. You can see how it is incomplete on the fourth line of the screenshot you posted.
https://github.com/bespoke-silicon-group/bsg_replicant/blob/a24fe8d247eb68a59193731e33b19b25b24b2d14/libraries/platforms/bigblade-xcelium/library.mk#L53

Check is added to this PR: https://github.com/bespoke-silicon-group/bsg_replicant/pull/796/files

@dpetrisko Do you know what XCELIUM_RELEASE should be for the chamber?

I would assume that it is a parent of whatever which xrun returns if xrun is on your path
For example if xrun was on our path:
XCELIUM_RELEASE=which xrun/../../../

Yeah I found it offline. That’s a neat trick though, maybe it makes sense to have auto detected defaults like that… but another issue, another PR :)

So with these changes, I was able to get the CUDA examples to work in our environment, only with the exception of 1 test, test_vec_add_parallel. I've also been going through and testing each of the SPMD tests individually. So far almost all the same ones are failing, with the exception of only a few. Other SPMD tests are failing though that weren't before:

The commented lines in the pictures are the tests that are working now. I had to add in bsg_barrier and bsg_barrier_time since these are failing now but weren't before also

What's the issue you see in test_vec_add_parallel?

I forgot that I don't have llvm installed, because I had issues with its setup. I mentioned it to Dan, and he said not to worry about it since most of the examples didn't require it. He recently sent me a potential fix for this though, which could fix this example and probably several of the SPMD one's too.

Yeah @drichmond is there a way to force GCC compilation of everything? Does it matter? I thought I remembered the LLVM research being pretty old at this point so I don’t necessarily want to spend time spinning it up

LLVM works fine. I use it all the time.
There's no easy way to force all of them to use GCC, though test_vec_add doesn't require it.
I don't recall SPMD programs using LLVM. Is that why they're failing?

There's nothing in the SPMD errors directly mentioning LLVM, just that it's "entering an unknown directory", and also the error I screenshotted in my original post

Can you check the tile group dimensions of those tests?
For example:
https://github.com/bespoke-silicon-group/bsg_manycore/blob/151a51862845edb12832944945a7d99d44a84769/software/spmd/hw_barrier_NxN_test/Makefile#L1
Maybe the tests are asking for a larger tile group than your architecture

Sorry, I was unclear. I meant that we weren’t able to compile LLVM on our system (our fault), so ideally we would just use GCC for everything. IIRC, some compiler optimizations depend on LLVM, but presumably all can be compiled using GCC at some performance loss

Yes, nothing depends on LLVM. If a test has LLVM as its compiler we can probably change that.
But my question above still stands. What size architecture are you using?

Oh sorry missed the question. We’re doing 16x8 for the purposes of bringing up the regression, then we’ll be doing 16x12 for our system. So I think anything that requires minimum size should be fine — wouldn’t be surprised if we encounter a NPOT error somewhere for the latter case

That's odd then. Are you able to reproduce these errors?

So I'm still having some issues installing LLVM despite updating our cmake to version 3:

I'm not sure whether to keep debugging the LLVM installation or to switch to gcc like you guys were mentioning. Would switching to GCC be a good option?

I think this is resolved, someone can reopen if they disagree


Cannot read properties of null (reading 'getComputedStyle')

Hi
I'm trying to use the carousel component with Embla, but I'm facing this error:

The error only appears when I switch between routes two times, like:

Home Page -> About Page
About Page -> Home
The error appears-

Already try to use clientOnly as people suggest me on SolidJS Discord group, but didn't work.
Any way to avoid this error without disabling SSR?

Hi @tutods,
does this error also happen if you use the embla package by itself? Or is it a SolidUI only problem?

Didn't try with embla only, but I didn't install from Solid UI, only copy all login and a few styles, and the rest I implement my own styles.

Is it possible for you to create a minimal reproducible example? Without anything just using SolidStart and SSR, 2 pages and a simple carrousel.
Thanks in advance. :)

Any updates? :)

Yes, sorry for the delay.
The problem is using the Iconify for Solid, for now I'm using phosphor icons web font and apparently works.