command update on pulling runtime container

Under the section "Store runtime containers in your private registry", the docker pull command "docker pull mcr.microsoft.com/azureiotedge-agent" is not accurate now. This command will auto refer to the version "latest", and it will fail to find the container as the "latest" version is not exist. Suggest to change to "docker pull mcr.microsoft.com/azureiotedge-agent:[version]", and suggest user to find the latest version from azureiotedge-agent description page.
There is a policy changes of Microsoft container version (please correct me if this is not the latest policy), that there will be no default "latest" version, and the version number will be specified for every release.

@ktoliver Can you apply my suggested changes to this pull request and then I can sign off on it? Thank you.

@kgremban Done!

Thank you!
#sign-off


Hover panel links don't do anything

Clicking on the "web" or "more" links in the hover panel does not do anything. However, using the command palette does. Probably the command names were not kept consistent in these codepaths

Sadly, nothing was changed in that part recently, the command naming haven't been changed at all (display label and command names are separated things). The weird thing here is if I create a new command and put a link to that command in a hover it still don't work (following the official documentation and examples), and I can't find a single issue/pr that relates to a change in that part in VSCode recently, I may have to dig into the sources and commits history.


Wrong UI

The screen image in the page is different from what is actually generated by the code.
Page:

Code:

This type of inaccuracy is typical to the entire documentation.

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

ID: 814e94a3-80a3-927b-b1ce-d4526435feb4
Version Independent ID: a304ea23-c2cf-5a31-5b37-74b92da342be
Content: Quickstart - Teams interop on Azure Communication Services - An Azure Communication Services quickstart
Content Source: articles/communication-services/quickstarts/voice-video-calling/get-started-teams-interop.md
Service: azure-communication-services
Sub-service: teams-interop
GitHub Login: @tophpalmer
Microsoft Alias: chpalm

@EDG7
Thanks for your feedback! We will investigate and update as appropriate.

@EDG7 can you please share what's inaccurate about the screen shot besides the 'or"?

Hi Grace, and thanks for much for getting back on this!
You can see the difference in the images attached. The actual rendered form does not have "Or" in it.
This does not seem to be a small typo, but something that probably changed with previous code updates.
In fact, the current code is also NOT functional. Line 35 in the js file breaks, with call.api not identified as a function. The code does run after commenting out that section.
These inaccuracies lead to a struggle when trying to follow the tutorials. There are more issues. Really hope that you folks can help us users with this.
Thanks again,
Udi


Push notification

Hi ,
I integrated this code . it was done successfully.  But I am struck register device to send push notification to device (push notification web service). I am a php developer , I am trying integrate apns and gcm. But I was fail . Please provide any example code of pass push notification. Please Help me.

Unfortunately, sending notification is outside the scope of this library. Have a look at this library: https://github.com/jwage/php-apns


feat: new plugin - tekton

Summary
Key Points
Support tekton plugin installed using helm.
Description

new plugin: tekton
it takes three option inputs: chart, repo and create_namespace
it get helm template from repo and install tekton using chart variable
docs are also updated
added to dtm show as well

Please hold; do not merge for now.

On hold for internal reasons. @imxw, please follow up on this later this month.


WebApp - Re-check min active stake for Relaychain

Describe the task
Re-check min active stake for Relaychain
To reproduce the task
Actual: Show incorrect min active stake in case min validator < min network

Expect: Min active stake  = Max {Min active stake network, Min active stake validator}

Version test : https://24798c9c.subwallet-webapp.pages.dev/
Validation passed


Setting more than 2 threads does not work and no error message

Running the SQLQueryStress.exe
I set my query to SELECT @@VERSION; and set the threads to 2.  It works fine.  I then update the threads to 5 as shown and the program fails to execute but gives no error message or indication that it failed.
Good:

Bad:

I've traced the problem to the MinPool Size and Max Pool Size connection string parameters:
Development machine:
...Pooling=True;Min Pool Size=5;Max Pool Size=5;...
Test Machine:
...Pooling=True;Min Pool Size=5;Max Pool Size=2;...

So we can close this?

No, the Max Pool Size should always be equal to or greater than Min Pool Size and clearly it is not.

No, the Max Pool Size should always be equal to or greater than Min Pool Size and clearly it is not.

No, the Max Pool Size should always be equal to or greater than Min Pool Size and clearly it is not.

Fixed in latest build, thanks for reporting this


Husky gmapping navigation ??

Hi
I run Husky gmapping_demo file with gazebo, everything is fine. However, I am getting different results when I run it with real husky (physical experiment). When I run gmapping_demo asking husky to move forward, husky move forward for short distance then starts to rotate around itself, navigation process is not good.
Based on this Clearpath tutorial. It says

To adapt this demo to your own Husky, you may need to clone the husky_navigation repository, and modify the relevant parameters

But I have no idea what are these relevant parameters that I need to change ??!!
This is the error that appears after running gmapping
 DWA planner failed to produce path
Any suggestions please ??

@Abduoit This should be a good start into helping you tune the navigation: http://wiki.ros.org/navigation/Tutorials/Navigation Tuning Guide  Additionally, the parameters are located in these YAMLs: https://github.com/husky/husky/tree/indigo-devel/husky_navigation/config
Let me know if that helps.

Closing due to inactivity.  Please feel free to re-open if issue persists.


categories disapearing from side bar block after I edit them

I have recently been updating my category descriptions and other things. I noticed today that most of my categories are missing from the front end sidebar.
I realised only the ones I updated were missing,
I tried shortening the names, this did not fix it
I tried toggling the sub category product display to on, this did not fix it
I reset the plugin, this did not fix it (but it did move the block to the bottom of the sidebar)
I tried editing another category by changing ONLY the description, this then removed the category from the sidebar
I changed the edit back as it was, but the category didn't return
I can't find any difference in the ones that are displaying and the ones that are not. They are working fine in the menu etc.
Now I just have two categorises on my live store!

You should check data stored in database, and look for differences between correctly and incorrectly displayed categories.
select * from tb_bees_blog_category;
select * from tb_bees_blog_category_lang;

I checked on my local environment, and editing categories have no negative impact.
I have discovered one minor issue, not related to this one -- disabled categories are always displayed. They should not

ok, we didn't establish the cause but it was fixed by clicking the green ticks off and on again in the categories list. They were all green and the categories were working on the store, this only affected the product categories on the sidebar menu.
also I think I put this in the wrong place, I thought this cas beesBLOCKcategories not beesblog. Don't know how to move it though.


Deprecate unused methods in File

These should have been removed or deprecated by
d5270ea5a0f9ffec69d2ca757835541db1e54918

Coverage increased (+0.01%) to 97.172% when pulling 2e3d17d14e685b6d336241c8ebc7241794cf177d on deprecate_read into 5d41a7f162641b650a53799989dda9adde0ff16b on master.

Coverage increased (+0.01%) to 97.172% when pulling 2e3d17d14e685b6d336241c8ebc7241794cf177d on deprecate_read into 5d41a7f162641b650a53799989dda9adde0ff16b on master.


[Bug]: COOLIFY environment variables not defined when doing preview deployment

Description
When you are doing a preview deployment of Dockerfile the COOLIFY_* environment variables are not known.
Vercel from example expose these variables both in production and preview builds, see:
https://vercel.com/docs/projects/environment-variables/system-environment-variables
Minimal Reproduction (if possible, example repository)
http://github.com/weyert/quote-of-the-day
If you try to do a preview deployment of this the COOLIFY_FQDN will be undefined in next.config.js or when its building the page and calls getBirthOfDay:
#16 24.45 Generating static pages (0/4) ...
[2024-Aug-26 16:00:43.984940]

[COMMAND] docker exec sw8sg0kog8s0wwgcocw84ssg bash -c 'bash /artifacts/build.sh'
[OUTPUT] #16 25.01 API_HOST: undefined #16 25.01 COOLIFY_FQDN: undefined #16 25.01 NEXT_PUBLIC_SOURCE_COMMIT: undefined #16 25.01 API_HOST: undefined #16 25.01 COOLIFY_FQDN: undefined #16 25.01 NEXT_PUBLIC_SOURCE_COMMIT: undefined

Exception or Error
No errors
Version
4.0.0-beta.323
Cloud?

[ ] Yes
[X] No

I just ran into this same issue I believe. You can not set the env variables to be available in developer view, but, you can select them individually to be available during the build by turning off developer view and then on each line item there is a checkbox to select making it available.
I was just about to make an issue with a suggestion for how to fix that and make it more clear to "people like us" who don't just know that.

@pkellner What would you suggest to improve the UX, so that it is more clear?

I was thinking in the dev screen where you paste in the environment variables, add a checkbox below that saying “ export all variables at build”, and default that to checked.  Then, when unchecked, unhide another text input area that lets you put in a comma or semicolon separated list of env variables to expose in build.
I realize that exposing all will create a verbose docker command with lots of args, but I think it will better follow the principle of “least surprise”.

I don't think you can select for the built-in COOLIFY_* variables?

Also, I like the “bug” tag better because as is, if you input your env values in dev mode (like I’m guessing every dev will do), you’ll never know how to expose them at build time as there is not even a hint.
Adding a * comment in the UI would IMHO make this an improvement, but without, definitely a bug.

Ey, bruv, sounds like you're having a bit of a mare with your Vercel deployments.  Variables not playing ball during previews, innit?  Classic Dockerfile shenanigans.
Let's sort this out.  First things first, double-check those environment variables in your Vercel project settings. Make sure they're set up for both production and preview environments, just like the docs say.
Next, peep your next.config.js. Are you trying to access the COOLIFY_* variables directly there? Might need to tweak your logic a bit. Try using process.env.COOLIFY_FQDN instead, mate.
If that doesn't do the trick, try a hard refresh or clear your Vercel cache.  Sometimes those deployments get a bit sticky.
Still no joy? Then it's time to get our hands dirty. Check your build logs in detail.  Look for any errors or warnings related to the COOLIFY_* variables. They might be trying to tell you something.
And if all else fails, don't be afraid to hit up the Vercel support crew. They're usually pretty sound and can help you get to the bottom of it.
Keep me posted, yeah?

Not sure, why you are start talking about Vercel while I am talking about Coolify.
I am trying to say that as far as I can see --build-arg COOLIFY_FQDN=$COOLIFY_FQDN or similar is not happening when building a docker image.  Only get set when running the image. Maybe I am not following the code.

Not sure, why you are start talking about Vercel and contacting Vercel support while I am talking about Coolify.
I am trying to say that as far as I can see --build-arg COOLIFY_FQDN=$COOLIFY_FQDN or similar is not happening when building a docker image.  Only get set when running the image. Maybe I am not following the code.

I think it's a bot 😂

Alright, bruv, my bad.  Got my wires crossed there for a sec. Coolify, not Vercel, innit?  My apologies.
So, you're saying the COOLIFY_FQDN isn't making it into your Docker image during the build, yeah?
Let's have a butcher's at your Dockerfile then. Are you definitely using the --build-arg flag correctly when you're building the image? Double-check the syntax, mate.
Also, make sure you're actually referencing the COOLIFY_FQDN build arg somewhere inside your Dockerfile.  If it's just floating around in there, it's not gonna do much good.
Another thing to consider is the order of your build steps. Are you trying to use the COOLIFY_FQDN before it's actually been set? Dockerfiles can be a bit finicky with that sort of thing.
  Chuck in a cheeky ENV instruction or an echo command to see what's actually going on in there.
And if all else fails, don't be shy about digging into the Coolify docs or community forums. Someone's bound to have bumped into this before.
We'll crack this, bruv. Just keep at it.

In the next version all COOLIFY related environment variables will be available during build time, except for docker compose based application. For those it is a bit complex.

Awesome that's amazingly quick. Thank you


How to avoid hardcoded plugin lists?

Any projects that use bablyon to do source code transformation or analysis typically want to operate on any code that bablyon is capable of parsing. Unfortunately, that means enabling all flags and plugins in every place that babylon is used. Inevitably this list of flags and plugins falls behind eventually.
What do you propose for dealing with this problem? Should we allow passing a parseTarget option, or something, that would take es2015, es2017, stable, latest, etc? We had * as a plugin option that enabled all plugins, but that was removed because of the potential for conflicting plugins.

Currently the concern is all for Stage < 4 functionality. Take decorators for instance, we currently have the old decorators spec exposed as the decorators plugin, but we'd like to add the new spec. Since we want people to actually upgrade to Babel 7, we can't replace the old decorators with the new one as a breaking change, so instead we're likely going to add a second decorators plugin for the new spec language.
If we expose * that will cause a conflict between the plugins.
One option that comes to mind is that we could publish a babel-babylon package that would automatically enable your plugins based on your .babelrc. Now sure how people feel for that.

Maybe what we can do instead is make * different or make another option that basically just checks the current list of plugins and then does a console.warn to tell you if there's an updated version to use instead


Use Buf remote plugins

Description
Changes in this PR:

Updates proto code generation according to this migration guide.
Upgrades the versions of remote plugins being used.
Instead of using conduit-connector-protocol as a Buf remote package, we now use the generated code provided as part of conduit-connector-protocol.

Fixes part of #762.
Depends on https://github.com/ConduitIO/conduit-connector-protocol/pull/17.
Quick checks:

[x] I have followed the Code Guidelines.
[x] There is no other pull request for the same update/change.
[ ] I have written unit tests.
[x] I have made sure that the PR is of reasonable size and can be easily reviewed.

clap nice work!

Thanks:)


Use rich to colorize --help

Look at rich-cli implementation once it's released. Can remove click-help-colors dependency and have more control over output.

See RichCommand

See https://github.com/nf-core/tools/pull/1411

ewels/rich-click is now its own library.

Think it's good to use after https://github.com/ewels/rich-click/issues/36 is fixed.


Too many compaction pending bytes when truncating a huge table in TiDB

Bug Report

What version of TiKV are you using?

5.0 nightly
What operating system and CPU are you using?

Intel(R) Xeon(R) Silver 4214R CPU @ 2.40GHz
Steps to reproduce

Truncate a large table (about 2.3T) in TiDB. The store size reduced about 18T.

What did you expect?
There shouldn't be many compaction pending bytes, according to @5kbpers
What did happened?
There are about 4.5T compaction pending bytes, and causes write stall.

I guess that deleting a lot of sst files by DeleteFilesInRange may cause the LSM tree into a strange shape, and in the abnormal shape, the way of calculating pending compaction bytes may not work well.

Close by https://github.com/tikv/tikv/pull/10978
The PR avoids the write stall after table drop though compaction pending bytes still change dramatically(it's as expected and just a statistics)


Improved collapse transition & typo in README.md

Hi, guys, please take a look at the feature I've just added. I love your component and always wanted this feature to be implemented because it makes the user experience way better. In short - I've created a transition on collapse which makes smooth collapse/deploy transitions via height manipulations. If I broke something, I'll be glad to fix it!

Can you provide a gif/video demo please?


Fix color pickers alignments, add Discord and ToS link

Still not looking as sharp as I wanted, but it's a little more improved than the initial version.

Despite fixes, it breaks mobile version on almost all pages (you can check by yourself).
Let split it into few separate pull requests and check one by one (colour picker / toss and about page/ form width change on 2 screens).


Access-Control-Allow-Origin is missing in headers

qwest.get(my_IP')
     .then(function(xhr, response) {
        alert(response);
     });

Raise an error Response to preflight request doesn't pass access control check: No 'Access-Control-Allow-Origin' header is present on the requested resource
How can I add "Access-Control-Allow-Origin: *" in headers ?

You have an headers option available (see the docs). But I think you're doing a CORS request, then you must have the according headers set on the response from your server : http://www.html5rocks.com/en/tutorials/cors/

Well the same request using jQuery $.get method works fine !?

They probably have some additional code. Did you test the headers option or anything else from the article?

Yes they have Access-Control-Allow-Origin: * in the request header ... I wasn't able to add it with qwest

The Access-Control-Allow-Origin: * needs to come from the server, not from qwest. As the returned error is saying, especially in the last sentence : No 'Access-Control-Allow-Origin' header is present on the requested resource.
That's why I've posted this article about CORS : http://www.html5rocks.com/en/tutorials/cors/
Because it seems you're not understanding well what is happening ^^

Is the example you've posted above is the complete code for the request? You have no data or other options set on qwest?

To well understand what's happening on the request, read this specific section : http://www.html5rocks.com/en/tutorials/cors/#toc-adding-cors-support-to-the-server
Furthermore, CORS is activated by your request because it seems you're running the request on a different domain than the resource itself.

With PHP a simple header('Access-Control-Allow-Origin: *'); do the trick ;)

On my ruby script I use :
before do
    response['Access-Control-Allow-Origin'] = "*" # Allow any origin
 end

Without that, jQuery raise an error too !
But here the response after a simple $.get
HTTP/1.1 200 OK
Content-Type: application/json
Content-Length: 136
Connection: keep-alive
Status: 200 OK
Access-Control-Allow-Origin: *
Date: Mon, 11 Jan 2016 16:19:22 GMT
X-Powered-By: Phusion Passenger 5.0.23
Server: nginx/1.8.0 + Phusion Passenger 5.0.23

As you can see, Access-Control-Allow-Origin: * is there.
I will copy /paste both jquery and Qwest headers and both answers
And yes I use XDomain  :)

I Just found my issue ... Qwest send an OPTIONS ...then my webservice raise a 404 error
It is normal ?
jQuery (OK)
$.get("http://<IP_ADDRESS>/vehicles/search")
Request
GET /vehicles/search HTTP/1.1
Host: <IP_ADDRESS>
Connection: keep-alive
Accept: /
Origin: http://localhost:8081
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_2) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/47.0.2526.106 Safari/537.36
Referer: http://localhost:8081/
Accept-Encoding: gzip, deflate, sdch
Accept-Language: fr-FR,fr;q=0.8,en-US;q=0.6,en;q=0.4
Response
HTTP/1.1 200 OK
Content-Type: application/json
Content-Length: 28
Connection: keep-alive
Status: 200 OK
Access-Control-Allow-Origin: *
Date: Mon, 11 Jan 2016 16:36:12 GMT
X-Powered-By: Phusion Passenger 5.0.23
Server: nginx/1.8.0 + Phusion Passenger 5.0.23
Qwest (NOK)
Request
OPTIONS /vehicles/search HTTP/1.1
Host: <IP_ADDRESS>
Connection: keep-alive
Access-Control-Request-Method: GET
Origin: http://localhost:8081
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_2) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/47.0.2526.106 Safari/537.36
Access-Control-Request-Headers: accept, cache-control
Accept: /
Referer: http://localhost:8081/
Accept-Encoding: gzip, deflate, sdch
Accept-Language: fr-FR,fr;q=0.8,en-US;q=0.6,en;q=0.4
Response
HTTP/1.1 404 Not Found
Content-Length: 9
Connection: keep-alive
Status: 404 Not Found
X-Cascade: pass
Date: Mon, 11 Jan 2016 16:36:08 GMT
X-Powered-By: Phusion Passenger 5.0.23
Server: nginx/1.8.0 + Phusion Passenger 5.0.23

Yes it's normal. The explanations from a previous issue : https://github.com/pyrsmk/qwest/issues/90
Maybe it could fix your problem.

Yep, adding { cache:true } works for me too ! Thank you for your help !

Great!
This OPTIONS issue is really annoying by the way...

I'm reopening this issue to have a reminder. I need to modify how the qwest's cache is working.

nice, good luck :)

Thanks ;)

Related to this PR : https://github.com/pyrsmk/qwest/pull/73

I'll just update the doc since Cache-Control seems the best way to handle request caching.

oh thanks all above, i ve got this problem too and finally i found that i had wrongly spelling header as headers, wish anyone seeing this to check it out~ : )


[Feature] Filter the calculators for an easy access

Description
It becomes difficult to locate the required calculator without spending sometime searching for it.
Solution: Create a filter section based on the subjects these calculators are specific to.
Screenshots
No response
Checklist

[X] I have checked the existing issues.
[X] I follow Contributing Guidelines of this project.
[ ] I am a IWOC'24 contributor.
[ ] I am a JWOC'24 contributor.
[X] I am a SWOC'24 contributor.

Code of Conduct

[X] I agree to follow this project's "Code of Conduct".

Pls complete your previously assigned issues @AkhilaSunesh


Flutter web does not support BlendMode.clear  using html renderer

After latest update to flutter 3.7, I started facing this error on image editing on flutter web when I try to render with html
flutter run -d chrome --web-renderer html
If I try to open the image editor page with canvas kit, it opens just fine but when I build with html renderer ( flutter run -d chrome --web-renderer html ), then the page goes all black and this error is being posted
Another exception was thrown: PersistedOffset: is in an unexpected state.
Sharing the sample file below where it can be reproduced
canvas kit rendering works fine
Error happens on html renderer
import 'package:extended_image/extended_image.dart';
import 'package:flutter/material.dart';
import 'package:image_picker/image_picker.dart';
void main() {
  runApp(const MyApp());
}

class MyApp extends StatelessWidget {
  const MyApp({super.key});

  // This widget is the root of your application.
  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      title: 'Flutter Demo',
      theme: ThemeData(
        primarySwatch: Colors.blue,
      ),
      home: const MyHomePage(title: 'Flutter Demo Home Page'),
    );
  }
}

class MyHomePage extends StatefulWidget {
  const MyHomePage({super.key, required this.title});

  final String title;

  @override
  State<MyHomePage> createState() => _MyHomePageState();
}

class _MyHomePageState extends State<MyHomePage> {
  final ImagePicker _picker = ImagePicker();
  XFile? _image;

  @override
  Widget build(BuildContext context) {
    return Scaffold(
      appBar: AppBar(
        title: Text(widget.title),
      ),
      body: Center(
        child: Column(
          mainAxisAlignment: MainAxisAlignment.center,
          children: <Widget>[
            if (_image != null)
              Image.network(
                _image!.path,
                height: 300,
                width: 300,
              ),
            const SizedBox(height: 20),
            Row(
              mainAxisAlignment: MainAxisAlignment.center,
              children: [
                OutlinedButton(
                    onPressed: () {
                      if (_image != null) {
                        Navigator.push(
                            context,
                            MaterialPageRoute(
                              builder: (context) =>
                                  ImageEditorDemo(fetchedImage: _image!),
                            ));
                      }
                    },
                    child: const Text('Edit Image')),
                const SizedBox(width: 20),
                ElevatedButton(
                    onPressed: () async {
                      _image =
                          await _picker.pickImage(source: ImageSource.gallery);
                      setState(() {});
                    },
                    child: const Text('Get Image')),
              ],
            )
          ],
        ),
      ),
    );
  }
}

class ImageEditorDemo extends StatefulWidget {
  final XFile fetchedImage;
  const ImageEditorDemo({Key? key, required this.fetchedImage});
  @override
  _ImageEditorDemoState createState() => _ImageEditorDemoState();
}

class _ImageEditorDemoState extends State<ImageEditorDemo> {
  final GlobalKey<ExtendedImageEditorState> editorKey =
      GlobalKey<ExtendedImageEditorState>();
  final GlobalKey<PopupMenuButtonState<EditorCropLayerPainter>> popupMenuKey =
      GlobalKey<PopupMenuButtonState<EditorCropLayerPainter>>();

  EditorCropLayerPainter? _cropLayerPainter;

  @override
  void initState() {
    _cropLayerPainter = const EditorCropLayerPainter();
    super.initState();
  }

  @override
  Widget build(BuildContext context) {
    return Scaffold(
      appBar: AppBar(
        title: const Text('image editor demo'),
      ),
      body: Column(children: <Widget>[
        Expanded(
            child: ExtendedImage.network(
          widget.fetchedImage.path,
          fit: BoxFit.contain,
          mode: ExtendedImageMode.editor,
          enableLoadState: true,
          extendedImageEditorKey: editorKey,
          initEditorConfigHandler: (ExtendedImageState? state) {
            return EditorConfig(
              maxScale: 8.0,
              cropRectPadding: const EdgeInsets.all(20.0),
              hitTestSize: 20.0,
              cropLayerPainter: _cropLayerPainter!,
              initCropRectType: InitCropRectType.imageRect,
              cropAspectRatio: 1,
            );
          },
          cacheRawData: true,
        )),
      ]),
    );
  }
}

full error code, and make a simple demo

Thanks for such quick response. It resolved the issue.


CDM R package

CDM R package OMOP CDM v5.4
This package can be downloaded from https://github.com/OHDSI/CommonDataModel/. It functions to dynamically create the OMOP CDM documentation and DDL scripts to instantiate the CDM tables.
https://github.com/OHDSI/CommonDataModel/
Create DDL, Foreign Keys, Primary Keys, and Indexes from R
Typically, new CDM versions and updates are decided by the CDM working group (details to join meetings on homepage). These changes are tracked as issues in the github repo. Once the working group decides which changes make up a version, all the corresponding issues should be tagged with a version number, e.g. v5.4, and added to a project board.
Read from Step 0 onwards at https://github.com/OHDSI/CommonDataModel/?tab=readme-ov-file#step-0


There's a problem when the popup's position is "top".

When clicking the button of increaseMonth and the height of the popup is change.  The popup of Calendar will be moved when clicking the button again. So I can't fire 'increaseMonth()'.
You can reproduce the bug by scrolling page when pupup is in bottom of page.

Confirmed; I got the datepicker into a couple weird states

I'm having the same problem. I put the DatePicker into a relatively positioned and constrained by width element, so the whole thing is
<div style={{display: 'block', position: 'relative', width: '200px', zIndex: 3}}>
  <DatePicker
    className='form-control datepicker'
    dateFormat='MM/DD/YYYY'
    popoverAttachment='bottom right'
    popoverTargetAttachment='top right'
    selected={moment(category.published_at)}
    onChange={::this.setPublishDate} />

It behaves this way:

Having this problem as well. I've been playing around with the tether properties, but haven't come up with a combination that serves as a workaround. If anyone finds one, please lay it down here.

+1 We're having the same issue

+1 same

+1

Is there some option to force the popup to stay at "bottom" and never go to the top to avoid this bug? (I'm not sure what exactly popoverAttachment and popoverTargetAttachment do, but apparently not that...)

@mb21, see #470

@rafeememon thanks, this indeed seems to sidestep the issue:
  <DatePicker
    selected={ this.props.date }
    onChange={ this.props.handleChange }
    tetherConstraints={ [] }
    />

Really like the component, any progress on this bug?

@hakonner, we're open to contributions to fix this

So as already mentioned, this bug happens when the height of the calendar changes due to month change. The calendar's position does not reflect this (issue with tether component?). When the user clicks "next month", the position is moved (in correct direction). It seems like the tether reposition the calendar before the onclick is triggered, so we miss a onclick event and the calendar stays in the same month. After a couple of clicks the calendar has become correctly positioned and the component works as expected again.
The tether component is a bit complex, so haven't had the time to really understand it, but have tested a couple of things. If I delay _tether.position() execution in _updateTether, let's say 100ms and remove the for loop inside _move in TetherClass [2452] (for (var i = 0; i < this.history.length; ++i))
This seems to "fix" the problem, but I have no idea of what bi-effects this may give.
Also, the jump in the calendar can be a bit annoying to the user when flipping through several months. Another solution would be to have a max-height fix or something so the calendar would not change height, but take up a bit more space on the "lower" months. @rafeememon, how hard would this be to implement?

+1

+1 Still an issue as of version ^0.33.0

+1

+1 we are having this issue too. Thank you!

Using fixedHeight prop solved that issue for me (well I'm happy with the behaviour).

We moved away from tether. Closing this as we're not using that lib anymore.

To avoid calendar shakes based on no.of weeks , we can use fixedHeight attribute.
syntax:- <DatePicker fixedHeight
selected={ this.props.date }
onChange={ this.props.handleChange }
/>

This is still a bug even in the demo when the date picker is above the input box. Reproduce by shrinking your window until the date picker appears above the text input and then click back through the months and watch the calendar jump around.

I added fixedHeight={true} option and it looks better


Rename symbol offers the whole function signature, not a symbol

Describe the bug
Given the below function signature:

I should be able to rename just one of the parameters with the Rename Symbol command, and have the change propogate throughout the system. Instead, I get prompted to rename the entire function. This is contrary to how other languages work in VSCode, where the rename symbol command is focused on a single symbol.
I'd instead expect to be able to just rename "message", without making changes inline to the full function signature.
Environment

OS: [e.g. Ubuntu 20.04]: 15.0 Beta (24A5298h)
Swift version (output of swift --version): swift-driver version: 1.112.3 Apple Swift version 6.0 (swiftlang-<IP_ADDRESS>.8 clang-16<IP_ADDRESS>)
Visual Studio Code version: Version: 1.91.1 (Universal)
vscode-swift version: v1.10.6

This is how it has been implemented in sourcekit-lsp. VSCode has no control over this.


Set WarningsReturnAsErrors = 0 before connection

Description
We have moved sqlsrv_configure('WarningsReturnAsErrors', 0); prior to sqlsrv_connect($this->hostname, $connection) because if there is a warning or an information message establishing the connection, it will treat it as an error and Codeigniter will throw an exception. Driver's configuration should be set prior the connection.
Example:
Before change, exception shows up (image1): "Unable to connect to the database. Main connection [SQLSRV]: Driver's SQLSetConnectAttr failed", but it is thrown by information message (IM006), as we can see when executing sqlsrv_errors() (image2).
Image1:

Image2:

After change: Connection is established without problems:

Checklist:

[ ] Securely signed commits
[ ] Component(s) with PHPdocs
[ ] Unit testing, with >80% coverage
[ ] User guide updated
[ ] Conforms to style guide

Please remove the extra whitespace.

Done :)

Thank you, @obelisk-services


Python 3.8 Support

Python 3.8 Support

I think it should work though we test against 3.6 still. I wonder if we should build against 3.7 / 3.8 also. Clearly we don't want to add a new dimension to the build matrix and multiply it by 3, but we could pick a certain database (say postgres) and run the python test suite against it, growing the matrix by 2 slots.

With the release of gunicorn>=20 Superset should now be fully 3.7 compliant, so it would make sense to add at least a test for that. I expect 3.8 to mostly work, but would be surprised if all dependencies are already fully 3.8 compliant. In my experience the ecosystem catches up to new python minors in about a year.


Inconsistent builds

Meta

Hotfix: #4003
Related PR: vuejs/vue-loader#1409

Version
v2.0.0
Reproduction link
dev
Steps to reproduce

./bin/nuxt build examples/hello-world
NODE_ENV=production ./bin/nuxt build examples/hello-world

What is expected?
Results should be the same.
What is actually happening?
Chunk names are different. Also things like s.options.__file should be stripped but it is not.
Additional comments?
Normal build:
Hash: 77622da25e0d579af1b6
Version: webpack 4.20.2
Time: 8670ms
Built at: 2018-09-28 12:43:39
                  Asset       Size  Chunks             Chunk Names
87c9ae15a64580abbac1.js   29.5 KiB       0  [emitted]  app
4767e3f41bc29ddaa1e5.js  494 bytes       1  [emitted]  pages/about
7d029e4429ef3a4557bf.js  437 bytes       2  [emitted]  pages/index
67347ecf5af03458ef7b.js    133 KiB       3  [emitted]  commons.app
ce430f2c9428f9c92feb.js    2.2 KiB       4  [emitted]  runtime
               LICENSES  422 bytes          [emitted]
 + 3 hidden assets
Entrypoint app = ce430f2c9428f9c92feb.js 67347ecf5af03458ef7b.js 87c9ae15a64580abbac1.js

Hash: 3a2a3ea1bb1bb0a04c93
Version: webpack 4.20.2
Time: 669ms
Built at: 2018-09-28 12:43:39
             Asset     Size  Chunks             Chunk Names
server-bundle.json  147 KiB          [emitted]
Entrypoint app = server-bundle.js server-bundle.js.map

When setting NODE_ENV=production:
Hash: 1e074dabd64eeb326435
Version: webpack 4.20.2
Time: 7456ms
Built at: 2018-09-28 12:44:03
                  Asset       Size  Chunks             Chunk Names
964f935295162117ed63.js   29.4 KiB       0  [emitted]  app
06cd332c6aa0e8b0c1f0.js  467 bytes       1  [emitted]  pages/about
efb705924dd2b7ecdb9b.js  410 bytes       2  [emitted]  pages/index
67347ecf5af03458ef7b.js    133 KiB       3  [emitted]  commons.app
8856f1071f6ebf9241d1.js    2.2 KiB       4  [emitted]  runtime
               LICENSES  422 bytes          [emitted]
 + 3 hidden assets
Entrypoint app = 8856f1071f6ebf9241d1.js 67347ecf5af03458ef7b.js 964f935295162117ed63.js
[12:44:03] Compiling server
[12:44:04] Compiled server in 712ms

Hash: a80e17c0968574a4756b
Version: webpack 4.20.2
Time: 715ms
Built at: 2018-09-28 12:44:04
             Asset     Size  Chunks             Chunk Names
server-bundle.json  145 KiB          [emitted]
Entrypoint app = server-bundle.js server-bundle.js.map

This bug report is available on Nuxt community (#c7859)

s.options.__file present inboth normal and production

@aldarund It seems for production builds, a safe file name is being injected. Related PR: https://github.com/vuejs/vue-loader/pull/1368

Closing this issue as #4003's workaround is enough and no action would be required from us but upgrading vue-loader.


fix(atomic): use img instead of atomic-icon for ipx button icon

SVCINT-2203
We had issues with some SVGs where it wasn't showing some images correctly (too big).
I found out that using the img tag instead of the atomic-icon was resolving it.

It's normal for the svg in atomic-icon to expand to fill it, that was done on purpose so that we can set the size of atomic-icon and the svg inside scales.
Instead of trying to use a different method of displaying svgs in IPX, I think we should try to use atomic-icon, but just apply some styling so that it doesn't expand too much.

This is just the case of the button icon. I tried to adjust styling but it still wasn't working for some cases. The img seems to work every time.
If you can try to access to this IPX builder and try to play with it. I did spend all day yesterday trying to adjust the CSS but didn't find a style for it.

Can you give me an example image that doesn't work?
When I try with https://elinux.org/images/c/cb/Raspberry_Pi_Logo.svg, it originally shows up way too big, but upon adding the viewBox property to the SVG to match its width and height, the icon scales correctly.
I suspect that the issue may be that we need to fix the viewBox of icons provided by the user.

viewBox

Sorry for the late follow up. I was off yesterday. You are probably right about the viewbox but I'm not sure whether we want to force this update or just specify it in the IPX doc 🤔.
I tested with two others SVG_Logo and Providenca.

I agree with @jbvouma on that one @btaillon .. We don't want to modify the SVG and img just works so there's no advantage of using atomic-icon? Isn't that component used mostly to display assets?

viewBox

Sorry for the late follow up. I was off yesterday. You are probably right about the viewbox but I'm not sure whether we want to force this update or just specify it in the IPX doc 🤔.
I tested with two others SVG_Logo and Providenca.

I agree with @jbvouma on that one @btaillon .. We don't want to modify the SVG and img just works so there's no advantage of using atomic-icon? Isn't that component used mostly to display assets?

Your current code already modifies the icon though, it changes the fill property.
The main advantage of atomic-icon is consistency across the UI; an icon that works in one place should also work in all others. We allow the customization of certain icons, such as the atomic-result-badge and the atomic-pager.
Another small advantage of atomic-icon is that it sanitizes the icon using DOMPurifier.
It's not strictly necessary, we could have behaviour that's different specifically for the IPX button, but I prefer to have as few exceptions as possible.


Nothing is generated for dart wire class triggered

Describe the bug
We make use of flutter_rust_bridge version 1.82.6. For reasons as of yet unknown, code generation stopped working with this error message:
An error occurred: Nothing is generated for dart wire class. Maybe you forget to put code like mod the_generated_bridge_code; to your lib.rs?
Steps to reproduce

Possibly relevant that I run Rust 1.83 on Arch Linux (btw)?
git clone git@github.com:MinBZK/nl-wallet.git
cd nl-wallet
cargo run --manifest-path wallet_core/flutter_rust_bridge_codegen/Cargo.toml
Observe error (see logs below)

Logs
RUST_BACKTRACE=full RUST_LOG=debug cargo run --manifest-path wallet_core/flutter_rust_bridge_codegen/Cargo.toml
    Finished `dev` profile [unoptimized + debuginfo] target(s) in 0.05s
     Running `wallet_core/flutter_rust_bridge_codegen/target/debug/flutter_rust_bridge_codegen`
the path is "/home/rubin/Source/ICTU/wallet/wallet_core/flutter_rust_bridge_codegen/../../wallet_app/ios/Runner/bridge_generated.h"
thread 'main' panicked at src/main.rs:51:48:
called `Result::unwrap()` on an `Err` value: Nothing is generated for dart wire class. Maybe you forget to put code like `mod the_generated_bridge_code;` to your `lib.rs`?

Stack backtrace:
   0: anyhow::error::<impl core::convert::From<E> for anyhow::Error>::from
             at /home/rubin/.cargo/registry/src/index.crates.io-6f17d22bba15001f/anyhow-1.0.86/src/backtrace.rs:27:14
   1: <core::result::Result<T,F> as core::ops::try_trait::FromResidual<core::result::Result<core::convert::Infallible,E>>>::from_residual
             at /home/rubin/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/core/src/result.rs:2010:27
   2: lib_flutter_rust_bridge_codegen::frb_codegen_multi
             at /home/rubin/.cargo/registry/src/index.crates.io-6f17d22bba15001f/flutter_rust_bridge_codegen-1.82.6/src/lib.rs:76:5
   3: lib_flutter_rust_bridge_codegen::frb_codegen
             at /home/rubin/.cargo/registry/src/index.crates.io-6f17d22bba15001f/flutter_rust_bridge_codegen-1.82.6/src/lib.rs:37:5
   4: flutter_rust_bridge_codegen::main
             at ./wallet_core/flutter_rust_bridge_codegen/src/main.rs:51:5
   5: core::ops::function::FnOnce::call_once
             at /home/rubin/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/core/src/ops/function.rs:250:5
   6: std::sys::backtrace::__rust_begin_short_backtrace
             at /home/rubin/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/std/src/sys/backtrace.rs:154:18
   7: std::rt::lang_start::{{closure}}
             at /home/rubin/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/std/src/rt.rs:195:18
   8: core::ops::function::impls::<impl core::ops::function::FnOnce<A> for &F>::call_once
             at /rustc/90b35a6239c3d8bdabc530a6a0816f7ff89a0aaf/library/core/src/ops/function.rs:284:13
   9: std::panicking::try::do_call
             at /rustc/90b35a6239c3d8bdabc530a6a0816f7ff89a0aaf/library/std/src/panicking.rs:557:40
  10: std::panicking::try
             at /rustc/90b35a6239c3d8bdabc530a6a0816f7ff89a0aaf/library/std/src/panicking.rs:520:19
  11: std::panic::catch_unwind
             at /rustc/90b35a6239c3d8bdabc530a6a0816f7ff89a0aaf/library/std/src/panic.rs:358:14
  12: std::rt::lang_start_internal::{{closure}}
             at /rustc/90b35a6239c3d8bdabc530a6a0816f7ff89a0aaf/library/std/src/rt.rs:174:48
  13: std::panicking::try::do_call
             at /rustc/90b35a6239c3d8bdabc530a6a0816f7ff89a0aaf/library/std/src/panicking.rs:557:40
  14: std::panicking::try
             at /rustc/90b35a6239c3d8bdabc530a6a0816f7ff89a0aaf/library/std/src/panicking.rs:520:19
  15: std::panic::catch_unwind
             at /rustc/90b35a6239c3d8bdabc530a6a0816f7ff89a0aaf/library/std/src/panic.rs:358:14
  16: std::rt::lang_start_internal
             at /rustc/90b35a6239c3d8bdabc530a6a0816f7ff89a0aaf/library/std/src/rt.rs:174:20
  17: std::rt::lang_start
             at /home/rubin/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/std/src/rt.rs:194:17
  18: main
  19: <unknown>
  20: __libc_start_main
  21: _start
stack backtrace:
   0:     0x599897c99c6a - std::backtrace_rs::backtrace::libunwind::trace::h5a5b8284f2d0c266
                               at /rustc/90b35a6239c3d8bdabc530a6a0816f7ff89a0aaf/library/std/src/../../backtrace/src/backtrace/libunwind.rs:116:5
   1:     0x599897c99c6a - std::backtrace_rs::backtrace::trace_unsynchronized::h76d4f1c9b0b875e3
                               at /rustc/90b35a6239c3d8bdabc530a6a0816f7ff89a0aaf/library/std/src/../../backtrace/src/backtrace/mod.rs:66:5
   2:     0x599897c99c6a - std::sys::backtrace::_print_fmt::hc4546b8364a537c6
                               at /rustc/90b35a6239c3d8bdabc530a6a0816f7ff89a0aaf/library/std/src/sys/backtrace.rs:66:9
   3:     0x599897c99c6a - <std::sys::backtrace::BacktraceLock::print::DisplayBacktrace as core::fmt::Display>::fmt::h5b6bd5631a6d1f6b
                               at /rustc/90b35a6239c3d8bdabc530a6a0816f7ff89a0aaf/library/std/src/sys/backtrace.rs:39:26
   4:     0x599897cc2123 - core::fmt::rt::Argument::fmt::h270f6602a2b96f62
                               at /rustc/90b35a6239c3d8bdabc530a6a0816f7ff89a0aaf/library/core/src/fmt/rt.rs:177:76
   5:     0x599897cc2123 - core::fmt::write::h7550c97b06c86515
                               at /rustc/90b35a6239c3d8bdabc530a6a0816f7ff89a0aaf/library/core/src/fmt/mod.rs:1186:21
   6:     0x599897c96613 - std::io::Write::write_fmt::h7b09c64fe0be9c84
                               at /rustc/90b35a6239c3d8bdabc530a6a0816f7ff89a0aaf/library/std/src/io/mod.rs:1839:15
   7:     0x599897c99ab2 - std::sys::backtrace::BacktraceLock::print::h2395ccd2c84ba3aa
                               at /rustc/90b35a6239c3d8bdabc530a6a0816f7ff89a0aaf/library/std/src/sys/backtrace.rs:42:9
   8:     0x599897c9ac7c - std::panicking::default_hook::{{closure}}::he19d4c7230e07961
                               at /rustc/90b35a6239c3d8bdabc530a6a0816f7ff89a0aaf/library/std/src/panicking.rs:268:22
   9:     0x599897c9aac2 - std::panicking::default_hook::hf614597d3c67bbdb
                               at /rustc/90b35a6239c3d8bdabc530a6a0816f7ff89a0aaf/library/std/src/panicking.rs:295:9
  10:     0x599897c9b257 - std::panicking::rust_panic_with_hook::h8942133a8b252070
                               at /rustc/90b35a6239c3d8bdabc530a6a0816f7ff89a0aaf/library/std/src/panicking.rs:801:13
  11:     0x599897c9b0ea - std::panicking::begin_panic_handler::{{closure}}::hb5f5963570096b29
                               at /rustc/90b35a6239c3d8bdabc530a6a0816f7ff89a0aaf/library/std/src/panicking.rs:674:13
  12:     0x599897c9a149 - std::sys::backtrace::__rust_end_short_backtrace::h6208cedc1922feda
                               at /rustc/90b35a6239c3d8bdabc530a6a0816f7ff89a0aaf/library/std/src/sys/backtrace.rs:170:18
  13:     0x599897c9ad7c - rust_begin_unwind
                               at /rustc/90b35a6239c3d8bdabc530a6a0816f7ff89a0aaf/library/std/src/panicking.rs:665:5
  14:     0x5998971fd880 - core::panicking::panic_fmt::h0c3082644d1bf418
                               at /rustc/90b35a6239c3d8bdabc530a6a0816f7ff89a0aaf/library/core/src/panicking.rs:74:14
  15:     0x5998971fdd06 - core::result::unwrap_failed::hd20b4aa073bda1e2
                               at /rustc/90b35a6239c3d8bdabc530a6a0816f7ff89a0aaf/library/core/src/result.rs:1700:5
  16:     0x59989720019f - core::result::Result<T,E>::unwrap::h24330219b5f61b06
                               at /home/rubin/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/core/src/result.rs:1104:23
  17:     0x59989720019f - flutter_rust_bridge_codegen::main::hf40ebb9cec9af3c5
                               at /home/rubin/Source/ICTU/wallet/wallet_core/flutter_rust_bridge_codegen/src/main.rs:51:5
  18:     0x5998971fe3ab - core::ops::function::FnOnce::call_once::h2b95131ff371e616
                               at /home/rubin/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/core/src/ops/function.rs:250:5
  19:     0x5998971fe36e - std::sys::backtrace::__rust_begin_short_backtrace::h836fadafac55b0c8
                               at /home/rubin/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/std/src/sys/backtrace.rs:154:18
  20:     0x5998971fed51 - std::rt::lang_start::{{closure}}::hd638c60f196eca46
                               at /home/rubin/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/std/src/rt.rs:195:18
  21:     0x599897c90b4e - core::ops::function::impls::<impl core::ops::function::FnOnce<A> for &F>::call_once::hfdb85f4ee94732d3
                               at /rustc/90b35a6239c3d8bdabc530a6a0816f7ff89a0aaf/library/core/src/ops/function.rs:284:13
  22:     0x599897c90b4e - std::panicking::try::do_call::h6e577310f330cbef
                               at /rustc/90b35a6239c3d8bdabc530a6a0816f7ff89a0aaf/library/std/src/panicking.rs:557:40
  23:     0x599897c90b4e - std::panicking::try::ha588d438267d2645
                               at /rustc/90b35a6239c3d8bdabc530a6a0816f7ff89a0aaf/library/std/src/panicking.rs:520:19
  24:     0x599897c90b4e - std::panic::catch_unwind::h429fda1e025f26d9
                               at /rustc/90b35a6239c3d8bdabc530a6a0816f7ff89a0aaf/library/std/src/panic.rs:358:14
  25:     0x599897c90b4e - std::rt::lang_start_internal::{{closure}}::h7b731265e841c4bf
                               at /rustc/90b35a6239c3d8bdabc530a6a0816f7ff89a0aaf/library/std/src/rt.rs:174:48
  26:     0x599897c90b4e - std::panicking::try::do_call::hc0f6a675b7ae5a36
                               at /rustc/90b35a6239c3d8bdabc530a6a0816f7ff89a0aaf/library/std/src/panicking.rs:557:40
  27:     0x599897c90b4e - std::panicking::try::h4c93b7ff0671f1ff
                               at /rustc/90b35a6239c3d8bdabc530a6a0816f7ff89a0aaf/library/std/src/panicking.rs:520:19
  28:     0x599897c90b4e - std::panic::catch_unwind::hcc1e154961d16ce6
                               at /rustc/90b35a6239c3d8bdabc530a6a0816f7ff89a0aaf/library/std/src/panic.rs:358:14
  29:     0x599897c90b4e - std::rt::lang_start_internal::h1c66660c99c8424c
                               at /rustc/90b35a6239c3d8bdabc530a6a0816f7ff89a0aaf/library/std/src/rt.rs:174:20
  30:     0x5998971fed2a - std::rt::lang_start::h7a0438420f00993b
                               at /home/rubin/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/std/src/rt.rs:194:17
  31:     0x59989720028e - main
  32:     0x758de3317e08 - <unknown>
  33:     0x758de3317ecc - __libc_start_main
  34:     0x5998971fe285 - _start
  35:                0x0 - <unknown>

Expected behavior
Succesfully generated, valid .dart files.
Generated binding code
N/A

OS
Arch Linux, kernel 6.12.1
Version of flutter_rust_bridge_codegen
1.82.6
Flutter info
[✓] Flutter (Channel stable, 3.24.5, on Arch Linux 6.12.1-arch1-1, locale
    en_US.UTF-8)
    • Flutter version 3.24.5 on channel stable at
      /home/rubin/.local/share/flutterup
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision dec2ee5c1f (2 weeks ago), 2024-11-13 11:13:06 -0800
    • Engine revision a18df97ca5
    • Dart version 3.5.4
    • DevTools version 2.37.3

[✓] Android toolchain - develop for Android devices (Android SDK version
    35.0.0)
    • Android SDK at /opt/android
    • Platform android-35, build-tools 35.0.0
    • ANDROID_HOME = /opt/android
    • Java binary at: /usr/lib/jvm/java-17-jetbrains/bin/java
    • Java version OpenJDK Runtime Environment JBR-17.0.12+1-1087.25-jcef
      (build 17.0.12+1-b1087.25)
    • All Android licenses accepted.

[✓] Chrome - develop for the web
    • CHROME_EXECUTABLE = chromium

[✓] Linux toolchain - develop for Linux desktop
    • clang version 18.1.8
    • cmake version 3.31.1
    • ninja version 1.12.1
    • pkg-config version 2.1.1

[✓] Android Studio (version 2024.2)
    • Android Studio at /opt/jetbrains-toolbox/apps/android-studio
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build
      21.0.3+-12282718-b509.11)

[✓] IntelliJ IDEA Ultimate Edition (version 2024.3)
    • IntelliJ at /opt/jetbrains-toolbox/apps/intellij-idea-ultimate-2
    • Flutter plugin version 82.2.4
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart

[✓] Connected device (3 available)
    • sdk gphone64 x86 64 (mobile) • emulator-5554 • android-x64    • Android
      13 (API 33) (emulator)
    • Linux (desktop)              • linux         • linux-x64      • Arch
      Linux 6.12.1-arch1-1
    • Chrome (web)                 • chrome        • web-javascript • Chromium
      131.0.6778.85 Arch Linux

[✓] Network resources
    • All expected network resources are available.

• No issues found!

Version of clang++
18.1.8
Additional context
# rustc --version
rustc 1.83.0 (90b35a623 2024-11-26)

Note: I tried downgrading to rust 1.82, but while I did note the resulting binary running for a noticably longer time, the error message remains the same.

We make use of flutter_rust_bridge version 1.82.6

Firstly, compared to v1, v2 is much stronger, and thus I strongly suggest to upgrade to v2 :)

code generation stopped working

Since code generation did work before, I guess one approach is to bisect the environment. For example, ffigen version, etc.

Is there a way to get more verbose messaging? I did execute with RUST_LOG=debug, but it doesn't show any additional messages that give me a hint as to where the problem originates.

You can try to run frb by source code (cargo run ...), and then can add arbitrarily many println! here and there for debugging.
The v1 code is in: https://github.com/fzyzcjy/flutter_rust_bridge/tree/v1-master


error TS2304: Cannot find name 'XMLHttpRequest'

Hi Romain,
I'm trying do play around with your library. But installation fails.
Environment:

Windows10, x64
cygwin, vscode
node v7.0.0, npm: 3.10.9
typescript 2.0.3

when i run the command:
npm install --save ts-express-decorators
I get the following errors:
(regards, Walter)
...
<EMAIL_ADDRESS>postinstall D:\Entwicklung\angular2\angular-cli\christian-lehmeier\ts-express-decorators-test\node_modules\ts-express-decorators

npm run build

<EMAIL_ADDRESS>build D:\Entwicklung\angular2\angular-cli\christian-lehmeier\ts-express-decorators-test\node_modules\ts-express-decorators
npm run tsc:es5 && npm run tsc:es6

<EMAIL_ADDRESS>tsc:es5 D:\Entwicklung\angular2\angular-cli\christian-lehmeier\ts-express-decorators-test\node_modules\ts-express-decorators
tsc --project tsconfig.json

../@types/superagent/index.d.ts(79,12): error TS2304: Cannot find name 'XMLHttpRequest'.
npm ERR! Windows_NT 10.0.14393
npm ERR! argv "C:\Program Files\nodejs\node.exe" "C:\Users\Walter\AppData\Roaming\npm\node_modules\npm\bin\npm-cli.js" "run" "tsc:es5"
npm ERR! node v7.0.0
npm ERR! npm  v3.10.9
npm ERR! code ELIFECYCLE
npm ERR<EMAIL_ADDRESS>tsc:es5: tsc --project tsconfig.json
npm ERR! Exit status 2
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>tsc:es5 script 'tsc --project tsconfig.json'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the ts-express-decorators package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     tsc --project tsconfig.json
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs ts-express-decorators
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls ts-express-decorators
npm ERR! There is likely additional logging output above.
npm WARN Local package.json exists, but node_modules missing, did you mean to install?
npm ERR! Please include the following file with any support request:
npm ERR!     D:\Entwicklung\angular2\angular-cli\christian-lehmeier\ts-express-decorators-test\node_modules\ts-express-decorators\npm-debug.log
npm ERR! Windows_NT 10.0.14393
npm ERR! argv "C:\Program Files\nodejs\node.exe" "C:\Users\Walter\AppData\Roaming\npm\node_modules\npm\bin\npm-cli.js" "run" "build"
npm ERR! node v7.0.0
npm ERR! npm  v3.10.9
npm ERR! code ELIFECYCLE
npm ERR<EMAIL_ADDRESS>build: npm run tsc:es5 && npm run tsc:es6
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>build script 'npm run tsc:es5 && npm run tsc:es6'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the ts-express-decorators package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     npm run tsc:es5 && npm run tsc:es6
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs ts-express-decorators
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls ts-express-decorators
npm ERR! There is likely additional logging output above.
npm WARN Local package.json exists, but node_modules missing, did you mean to install?
npm ERR! Please include the following file with any support request:
npm ERR!     D:\Entwicklung\angular2\angular-cli\christian-lehmeier\ts-express-decorators-test\node_modules\ts-express-decorators\npm-debug.log
npm WARN<EMAIL_ADDRESS>requires a peer of express@^4 but none was installed.
npm WARN<EMAIL_ADDRESS>No description
npm WARN<EMAIL_ADDRESS>No repository field.
npm ERR! Windows_NT 10.0.14393
npm ERR! argv "C:\Program Files\nodejs\node.exe" "C:\Users\Walter\AppData\Roaming\npm\node_modules\npm\bin\npm-cli.js" "install" "--save" "ts-express-decorators"
npm ERR! node v7.0.0
npm ERR! npm  v3.10.9
npm ERR! code ELIFECYCLE
npm ERR<EMAIL_ADDRESS>postinstall: npm run build
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>postinstall script 'npm run build'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the ts-express-decorators package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     npm run build
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs ts-express-decorators
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls ts-express-decorators
npm ERR! There is likely additional logging output above.
npm ERR! Please include the following file with any support request:
npm ERR!     D:\Entwicklung\angular2\angular-cli\christian-lehmeier\ts-express-decorators-test\npm-debug.log

Same

The same.
Looks like an issue with dependent library.

I found a similar problem here https://github.com/DefinitelyTyped/DefinitelyTyped/issues/12044
I work on the fix ;)

It's fix with v1.0.1 :)


refactor: default to CID v1 and encode with base32

Not breaking, can be released in a patch version.
Depends on:

[ ] https://github.com/multiformats/js-cid/pull/73

I think this was fixed with a later cids release, hence closing this PR.


Easily disabling some of the rules?

First: thanks for this project!
Now the question:
Is there any less surgical way to disable a rule other than removing it from /usr/local/lib/python2.7/dist-packages/ansiblelint/rules?
For instance, I really don't care for the trailing whitespace rule, to be honest, so it would be great if people could create a configuration file like you can with jslint or jshint.
Thanks!

Thanks!
At the moment there are a couple of options:

use -x to skip rules with tags. But that might still not be specific enough.
Copy all the rules to another directory and delete the ones you don't want, and then specify the path with -r.

A configuration file would be a good idea - I don't really have time to implement such a feature at the moment but a working pull request would definitely be favourably considered

I would like this feature as well. Due to some outstanding issues/bugs in the Ansible 1.9 release, it's not always possible to achieve full compliance. As you mention:

-x is too broad, eg. both ANSIBLE0006 and ANSIBLE0007 belong to the resource tag.
-r requires additional maintainence to keep them in sync & updated.

I agree having a configuration file would be excellent, even something like .pylintrc. As I understand this is too much work. Would it be easier to add another command line option to allow exclusion based on ANSIBLExxxx? Or, alternatively overload the -x option to support exclusion for tags or rules?

@charleswhchan that's a good idea. I still don't have much time available to look at it, but would support a pull request implementing such a change :)
Otherwise, I'll leave this open and see if I get bored at some point!

@willthames Created PR 73. Please review. :relaxed:

Thanks @charleswhchan for #73.
We might still want a configuration file so I'll leave this open for now.

No problem. :relaxed:

Closing this now - if we do want a configuration file, let's have that as a separate issue, preferably as a PR ;)

As with every linter, this feels like a basic requirement ...

@aairey and has a basic solution, using -x as per #73
Either that or use ansible-review which is much more configurable as to what rules are used.

Thanks @willthames, I wasn't aware.
Reading this0 cleared it up for me.
I will switch to ansible-review.
On Thu, 29 Mar 2018, 01:26 Will Thames<EMAIL_ADDRESS>wrote:

@aairey https://github.com/aairey and has a basic solution, using -x as
per #73 https://github.com/willthames/ansible-lint/pull/73
Either that or use ansible-review
https://github.com/willthames/ansible-review which is much more
configurable as to what rules are used.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/willthames/ansible-lint/issues/54#issuecomment-377071005,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AHSjvvfzNm1XDCZzD1G22vycdgi2VdB5ks5tjBw2gaJpZM4DrY3S
.


Customer is misinterpreting the lockbox overview text

[Enter feedback here]
Hi, Customer(Wells Fargo) is misinterpreting the lockbox overview available in public documentation.  customer is reading it as if customers don't use LockBox, Microsoft resources have access to customer data. Please make it clear in the document that  Microsoft engineers dont have access to customer data even without customer lockbox.
Thanks
Raj

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

ID: 985eab9b-60f7-480a-c649-1fd7c6105646
Version Independent ID: 4d5bbc09-fa5a-c67e-b4b8-75a5229506c0
Content: Customer Lockbox for Microsoft Azure
Content Source: articles/security/fundamentals/customer-lockbox-overview.md
Service: security
Sub-service: security-fundamentals
GitHub Login: @TerryLanfear
Microsoft Alias: terrylan

@RPMSFT
Thanks for your feedback! I've assigned this issue to the author who will investigate and update as appropriate.

@RPMSFT - Thank you for your dedication to our documentation. The first paragraph states:
Most operations, support, and troubleshooting performed by Microsoft personnel and sub-processors do not require access to customer data. In those rare circumstances where such access is required, Customer Lockbox for Microsoft Azure provides an interface for customers to review and approve or reject customer data access requests. It is used in cases where a Microsoft engineer needs to access customer data, whether in response to a customer-initiated support ticket or a problem identified by Microsoft.
#please-close


unit testing not working

Error: Timeout - Async callback was not invoked within timeout specified by jasmine.DEFAULT_TIMEOUT_INTERVAL.
If i remove  infiniteScroll attribute  from html then it works fine.

I had the same issue, when component is create with fixture, and I called method detectChanges(). Jasmine throw timeout, without that method everything pass.


Menu sounds based on themes

Many games offer menu sounds, which means a sound plays when the user hovers a button/checkbox/radio buttons or clicks on it.
It would be nice if Godot had a per-theme system to play such menu sounds, without having to create our own node so that all buttons/checkboxes/radio buttons play a sound when hovered/clicked.

Feature and improvement proposals for the Godot Engine are now being discussed and reviewed in a dedicated Godot Improvement Proposals (GIP) (godotengine/godot-proposals) issue tracker. The GIP tracker has a detailed issue template designed so that proposals include all the relevant information to start a productive discussion and help the community assess the validity of the proposal for the engine.
The main (godotengine/godot) tracker is now solely dedicated to bug reports and Pull Requests, enabling contributors to have a better focus on bug fixing work. Therefore, we are now closing all older feature proposals on the main issue tracker.
If you are interested in this feature proposal, please open a new proposal on the GIP tracker following the given issue template (after checking that it doesn't exist already). Be sure to reference this closed issue if it includes any relevant discussion (which you are also encouraged to summarize in the new proposal). Thanks in advance!


Crash with Malisis door

When you use the mod with Malisis it wont start

You found the exact mod, this is great and I am already able to test it, but please provide crash logs or game logs in the future
Added the mod to the list of mods to check compatibility issues with


Animation not working

First of all thank you so much for the library it really help me on my complex project.
I am facing issue on simple task may be I'm missing something. Simple loading animation not working in popup view.
Loading View
struct LoadingView: View {
    @State var shouldAnimate : Bool = false

    var title: String = "Loading ..."

    var body: some View {
        ZStack {
            Color.black.opacity(0.4)
                .ignoresSafeArea(.all, edges: .all)

            VStack(spacing: 20) {
                Circle()
                    .trim(from: 0, to: 0.8)
                    .stroke(Color.blue, lineWidth: 5)
                    .frame(width: 50, height: 50)
                    .rotationEffect(.init(degrees: shouldAnimate ? 360 : 0))

                Text(title)
                    .font(.largeTitle)
                    .multilineTextAlignment(.center)
                    .lineLimit(2)
            }
            .frame(width: 300, height: 150)
            .padding(20)
            .background(Color.white)
            .cornerRadius(10)
        }

        .onAppear(perform: {
            withAnimation(Animation.linear.speed(0.6).repeatForever(autoreverses: false)) {
                shouldAnimate = true
            }
        })
    }
}

on canvas preview it shows animation. Same while using it on .sheet it works perfectly fine.
Working Example Using .Sheet
struct WorkingExampleUsingSheet: View {

    @State var showLoading: Bool = false

    var body: some View {
        ZStack {
            VStack {
                Button {
                    showLoading.toggle()
                } label: {
                    Text("Tap Me")
                        .padding(50)
                        .foregroundColor(.white)
                        .background(Color.pink)
                        .cornerRadius(10)
                }
            }
        }
        .sheet(isPresented: $showLoading, content: {
            LoadingView(title: "Testing IT")
        })
    }
}

Not Working Using .popup
struct NotWorkingUsingPopup: View {

    @State var showLoading: Bool = false

    var body: some View {
        ZStack {
            VStack {
                Button {
                    showLoading.toggle()
                } label: {
                    Text("Tap Me")
                        .padding(50)
                        .foregroundColor(.white)
                        .background(Color.pink)
                        .cornerRadius(10)
                }
            }
        }
        .popup(isPresented: $showLoading) {
            LoadingView(title: "Testing IT")
        } customize: {
            $0
                .type(.default)
                .closeOnTapOutside(false)
                .closeOnTap(false)
                .dragToDismiss(false)
                .backgroundColor(Color.black.opacity(0.4))
                .isOpaque(true)
        }
    }
}

I don't know have clue why it is not animating, I tried to change the animation code with some other animation but still having same issue.
Thanks

Hey @nhjariwala, thank you for reproducible example, I'll be sure to give it a look. In the meantime, is your onAppear called as you expect it? I think problem might be there somewhere, have a beautiful day!

@f3dm76 OMG that super fast response from you I never expect that. Yes onAppear works as I expected. I will share all the code that help you to reproduce and test the code. If you need me more detail I will be more than happy to share. Thanks cheers

Hey @nhjariwala, found the problem - my bad. Please check out version 2.0.1, thanks for brining this to my attention, have a marvellous day!

@f3dm76 Thanks a ton. It's working now.
Cheers

Good Job！


Function.extractParams is deprecated.

Assigning custom properties to a marker when creating/copying it is
deprecated. Please, consider storing the custom properties you need in
some other object in your package, keyed by the marker's id property.
Function.extractParams (/Applications/Atom.app/Contents/Resources/app.asar/node_modules/text-buffer/lib/marker.js:43:14)
MarkerLayer.markRange (/Applications/Atom.app/Contents/Resources/app.asar/node_modules/text-buffer/lib/marker-layer.js:215:71)
DisplayMarkerLayer.markBufferRange (/Applications/Atom.app/Contents/Resources/app.asar/node_modules/text-buffer/lib/display-marker-layer.js:105:52)
TextEditor.markBufferRange (/Applications/Atom.app/Contents/Resources/app.asar/src/text-editor.js:1736:38)
Object.markInScopeVars (/Users/lg/.atom/packages/existdb/lib/existdb.coffee:464:33)
<unknown> (/Users/lg/.atom/packages/existdb/lib/existdb.coffee:118:26)

yup me too
exist-db 3.5.1
Java8
atom 1.20.1
macOS 10.11.6

I'm seeing this warning too on the latest versions of all the above:
eXist-db 3.6.0 develop HEAD
Java 1.8.0_141
atom 1.21.0 x64
macOS 10.13


AnimatedSprite can be convert to the tilemap?

Operating system or device, Godot version, GPU Model and driver (if graphics related):
win7 64
Proposal:
Stationary tilemap looks not good enough.
May be the AnimatedSprite  can be convert to a tileset,and tilemap can use it?

Duplicate of #9179.


Preparation for Grpc.Tools msbuild integration (#13207)

Preparing the ground for https://github.com/grpc/grpc/pull/13207 (so that we don't end up with a large PR that mixes lots of concerns).

upgrade NUnit as NUnit needs to be in sync with #13207 for the tests to pass
improve SanityTest to also detect test annotated with [TestCase] attribute and not just [Test].

The are generally changes we'd want anyway.

@kkm000  FYI

Objective-C binary sizes
*****************STATIC******************
  New size                      Old size
 1,950,903      Total (=)      1,950,903

 No significant differences in binary sizes

***************FRAMEWORKS****************
  New size                      Old size
10,661,270      Total (>)     10,661,268

 No significant differences in binary sizes

Known failures:
https://github.com/grpc/grpc/issues/15916


New Machine requirement: Fedora 40 static docker test system

I need to request a new machine:

New machine operating system (e.g. linux/windows/macos/solaris/aix): Linux, Fedora 40
New machine architecture (e.g. x64/aarch32/arm32/ppc64/ppc64le/sparc): at least x64 and aarch64.
Provider (leave blank if it does not matter):
Desired usage: Testing on the current version of Fedora. This should probably result in any versions prior to 38 being replaced as they are now out of support
Any unusual specification/setup required:
How many of them are required: 1

ref https://github.com/adoptium/infrastructure/pull/3694
https://ci.adoptium.net/computer/test-docker-fedora40-x64-1/ https://ci.adoptium.net/job/AQA_Test_Pipeline/343/console
https://ci.adoptium.net/computer/test-docker-fedora40-armv8-1/ https://ci.adoptium.net/job/AQA_Test_Pipeline/346/console

The x64 aqa pipeline was aborted during its end due to the jenkins upgrade. I can check which jobs were aborted and rerun them

test-docker-fedora40-armv8-1 Triage
Release Summary Report for AQA_Test_Pipeline
Report generated at: Tue, 06 Aug 2024 11:03:20 GMT
TRSS Build and TRSS Grid View
Jenkins Build URL https://ci.adoptium.net/job/AQA_Test_Pipeline/346/
Started by user Haroon Khel at 02/08/2024, 19:20:39

Test_openjdk11_hs_extended.openjdk_aarch64_linux ⚠ UNSTABLE ⚠
Rerun failed
java -version
openjdk version "11.0.24" 2024-07-16
OpenJDK Runtime Environment Temurin-11.0.24+8 (build 11.0.24+8)
OpenJDK 64-Bit Server VM Temurin-11.0.24+8 (build 11.0.24+8, mixed mode)

jdk_tools_1 => deep history 4/5 passed | possible issues
Test_openjdk11_hs_sanity.system_aarch64_linux ❌ FAILURE ❌
Rerun all
java -version
openjdk version "11.0.24" 2024-07-16
OpenJDK Runtime Environment Temurin-11.0.24+8 (build 11.0.24+8)
OpenJDK 64-Bit Server VM Temurin-11.0.24+8 (build 11.0.24+8, mixed mode)

TestJlmRemoteClassNoAuth_0 => deep history 8/9 passed | possible issues
Test_openjdk8_hs_extended.openjdk_aarch64_linux ⚠ UNSTABLE ⚠
Rerun failed
java -version
openjdk version "1.8.0_422"
OpenJDK Runtime Environment (Temurin)(build 1.8.0_422-b05)
OpenJDK 64-Bit Server VM (Temurin)(build 25.422-b05, mixed mode)

hotspot_jre_0 => deep history 4/5 passed | possible issues
jdk_net_1 => deep history 0/5 passed | possible issues
jdk_net_0 => deep history 0/5 passed | possible issues

test-docker-fedora40-x64-1 Triage
Release Summary Report for AQA_Test_Pipeline
Report generated at: Tue, 06 Aug 2024 13:58:42 GMT
TRSS Build and TRSS Grid View
Jenkins Build URL https://ci.adoptium.net/job/AQA_Test_Pipeline/343/
Started by user Haroon Khel at 02/08/2024, 19:06:28

Test_openjdk11_hs_extended.system_x86-64_linux ❌ ABORTED ❌
Rerun all
java -version
openjdk version "11.0.24" 2024-07-16
OpenJDK Runtime Environment Temurin-11.0.24+8 (build 11.0.24+8)
OpenJDK 64-Bit Server VM Temurin-11.0.24+8 (build 11.0.24+8, mixed mode)

MiniMix_10m_1 => deep history 2/3 passed | possible issues
Test_openjdk21_hs_extended.openjdk_x86-64_linux ⚠ UNSTABLE ⚠
Rerun failed
java -version
openjdk version "21.0.4" 2024-07-16 LTS
OpenJDK Runtime Environment Temurin-21.0.4+7 (build 21.0.4+7-LTS)
OpenJDK 64-Bit Server VM Temurin-21.0.4+7 (build 21.0.4+7-LTS, mixed mode, sharing)

jdk_jdi_0 => deep history 2/3 passed | possible issues
Test_openjdk8_hs_extended.openjdk_x86-64_linux ⚠ UNSTABLE ⚠
Rerun failed
java -version
openjdk version "1.8.0_422"
OpenJDK Runtime Environment (Temurin)(build 1.8.0_422-b05)
OpenJDK 64-Bit Server VM (Temurin)(build 25.422-b05, mixed mode)

jdk_net_0 => deep history 2/6 passed | possible issues
jdk_security3_0 => deep history 0/6 passed | possible issues
jdk_net_1 => deep history 2/6 passed | possible issues
jdk_security3_1 => deep history 0/6 passed | possible issues
jdk_jfr_0 => deep history 2/5 passed | possible issues
jdk_jfr_1 => deep history 2/5 passed | possible issues

Test failures are triaged and the containers are up and running


homebridge - CC Remote and 2 TV (or more)

Hi,
I have a issue with my CC (control center) Remote, because I can only watch a single TV in the app.
Do you have any idea how to solve it?
I have a homebridge (Hoobs) and this is my config.json
"accessories": [
{
"accessory": "webostv",
"name": "TV Pieza",
"prefsDir": "~/.webosTv",
"pollingInterval": 5,
"legacyTvService": false,
"showInputButtons": false,
"volumeControl": "slider",
"volumeLimit": 100,
"channelControl": false,
"mediaControl": false,
"inputs": [
{
"appId": "netflix",
"name": "Netflix"
},
{
"appId": "youtube.leanback.v4",
"name": "YouTube"
}
],
"infoButtonAction": "INFO",
"ip": "X.X.X.X",
"mac": "X:X:X:X:X:X",
"plugin_map": {
"plugin_name": "homebridge-webos-tv",
"index": 0
}
}
],
"platforms": [
{
"platform": "BraviaPlatform",
"tvs": [
{
"name": "TV Sala",
"cookiepath": "/home/hoobs/.sonycookie",
"ip": "X.X.X.X",
"soundoutput": "speaker",
"tvsource": "tv:dvbc",
"applications": [
{
"title": "Netflix"
},
{
"title": "Prime Video"
},
{
"title": "Spotify"
},
{
"title": "YouTube"
}
],
"sources": [
"extInput:hdmi",
"extInput:cec"

You have to configure your LG TV to use platform and not accessory (which you are using). Platform is the new recommended way to use this plugin. Accessory will still work, but it only makes sense if you have 1 TV.

Thank you @merdok , I added the tv on the platform and delete it on accessories, But now I don't watch television in my house app.
Could you help me with this?
"accessories": [],
"platforms": [
    {
        "platform": "webostv",
        "devices": [
            {
                "name": "Tele Pieza",
                "ip": "X.X .X.X",
                "mac": "X:X:X:X:X:X",
                "prefsDir": "~/.webosTv",
                "pollingInterval": 10,
                "volumeLimit": 100,
                "inputs": [
                    {
                        "appId": "netflix",
                        "name": "Netflix"
                    },
                    {
                        "appId": "youtube.leanback.v4",
                        "name": "YouTube"
                    }
                ],
                "notificationButtons": [
                    "Movimiento detectado - Cocina"
                ],
                "remoteControlButtons": [
                    "HOME",

I fixed it and it worked !! Thank you!


After update HMR not working on Angular - Error: "Module not found"

From @andresg747 on November 11, 2018 16:19
Environment

CLI: 5.0.0
Cross-platform modules: 5.0.2
Android Runtime: 5.0.0
iOS Runtime: 5.0.0
Plugin(s):
"nativescript-localstorage": "^1.1.5",
"nativescript-pulltorefresh": "^2.1.1",
"nativescript-snackbar": "^3.1.0",
"nativescript-theme-core": "~1.0.4",
"nativescript-ui-chart": "^3.6.1",
"nativescript-ui-listview": "^3.5.11",
"nativescript-ui-sidedrawer": "~4.1.0",

Describe the bug
When running tns run [android | ios] --hmr I get the following errors: Full Log.
The app (obviously), crashes on the device.
When running the same command without the HMR flag, the app runs perfectly.
To Reproduce
tns run [android | ios] --hmr
Expected behavior
Working Hot Module Replacement
I've added the script on main.ts and have "nativescript-dev-webpack": "0.17.0" installed.
Any help would be very appreciated. Thanks in advance.
Copied from original issue: NativeScript/NativeScript#6544

From @andresg747 on November 11, 2018 22:25
Hi, @Fatme.
I've run both commands, then run the tns run android --hmr and now i get the following:

Skipping node_modules folder! Use the syncAllFiles option to sync files from this folder.
Searching for devices...
Hot Module Replacement (HMR) is currently in Beta. For more information about the current development state and any known issues, please check the relevant GitHub issue: https://github.com/NativeScript/NativeScript/issues/6398
To enable Hot Module Replacement (HMR) in Angular projects, follow the steps outlined in this wiki: https://github.com/NativeScript/nativescript-angular/wiki/HMR
Executing before-liveSync hook from /Users/agarciag/Documents/nativescript/LiveData/hooks/before-liveSync/nativescript-angular-sync.js
Executing before-watchPatterns hook from /Users/agarciag/Documents/nativescript/LiveData/hooks/before-watchPatterns/nativescript-dev-sass.js
Executing before-watchPatterns hook from /Users/agarciag/Documents/nativescript/LiveData/hooks/before-watchPatterns/nativescript-dev-typescript.js
Executing before-watchPatterns hook from /Users/agarciag/Documents/nativescript/LiveData/hooks/before-watchPatterns/nativescript-dev-webpack.js
Executing before-watch hook from /Users/agarciag/Documents/nativescript/LiveData/hooks/before-watch/nativescript-dev-sass.js
Hook skipped because bundling is in progress.
Executing before-watch hook from /Users/agarciag/Documents/nativescript/LiveData/hooks/before-watch/nativescript-dev-typescript.js
Hook skipped because bundling is in progress.
Executing before-watch hook from /Users/agarciag/Documents/nativescript/LiveData/hooks/before-watch/nativescript-dev-webpack.js
Running webpack for Android...
module.js:549
    throw err;
    ^

Error: Cannot find module '/Users/agarciag/Documents/nativescript/LiveData/node_modules/webpack/bin/webpack.js'
    at Function.Module._resolveFilename (module.js:547:15)
    at Function.Module._load (module.js:474:25)
    at Function.Module.runMain (module.js:693:10)
    at startup (bootstrap_node.js:188:16)
    at bootstrap_node.js:609:3
Executing webpack failed with exit code 1.
Cannot read property 'kill' of undefined

Still, running without HMR flag, is working correctly.

From @Fatme on November 11, 2018 22:46
@andresg747,
It seems it is still not updated correctly.

rm -rf node_modules
rm -rf hooks
rm -rf platforms
rm -rf webpack.config.js
Ensure nativescript-dev-webpack: 0.17.0 is written in package.json
Ensure nativescipt-angular: 6.2.0 is written in your package.json
Ensure the following code snippet https://github.com/NativeScript/nativescript-angular/wiki/HMR#enable-hmr-in-nativescript-angular-project is added
npm i
tns run ios | android --hmr

NOTE: --hmr mode does not work for projects containing lazy loading - https://github.com/NativeScript/nativescript-angular/issues/1564.

Hi @andresggarcia,
As @Fatme has mentioned, the --hmr mode does not work for projects containing lazy loading. If you still need to use lazy loaded modules, you should build the project without --hmr flag.


Fix typo and correct HTML snippet in README

Fix typo in Typical Output section.
Add missing quote to href attribute in the HTML snippet of Broken Cross
References.

Should the base branch be 1.0.0-RC-2?


Local storage error on mobile Safari?

https://app.getsentry.com/share/issue/37333232342e313231343030363333/

IIRC, most common in private browsing mode.


The capacity shown is double

The drop plan is showing double the capacity value in version 2.0.3.
That is, if, for example, the taskboard shows that a user has a capacity of 30 hours, the Drop plan shows 60 hours.

@joroSharp will look at this later


Build Arrow from source when lib not found

I did a small experiment with FetchContent in CMake to see if we can build Arrow on demand when thee library is not installed to make it easier to build from source. It seems to work. Tested with the apache-arrow-1.0.0 branch of Arrow. We should add this.
[ 98%] Linking CXX shared library ../../release/libarrow.dylib
[ 98%] Built target arrow_shared
[ 99%] Building CXX object CMakeFiles/main.dir/main.cpp.o
[100%] Linking CXX executable main
[100%] Built target main

❯ otool -L main
main:
	@rpath/libarrow.100.dylib (compatibility version 100.0.0, current version 100.0.0)
	/usr/lib/libc++.1.dylib (compatibility version 1.0.0, current version 902.1.0)
	/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 1281.100.1)

It turns out that this doesn't work without some hacks for libraries so I'm closing this.


Add gateway ID for new Nexity rail din S box

I just moved into a new appartment that has a Nexity/Somfy box in the electrical switchboard. It has an ID of 109 and looks just like the TaHoma Rail-DIN S, so I created a new entry in the GatewayType enum with the name NEXITY_RAIL_DIN_S.
Merging this pull request will prevent the following message from appearing the in logs of Home Assistant:
Unsupported value 109 has been returned for <enum 'GatewayType'>
Here is a picture of the box for reference: https://i.imgur.com/BJmhLgm.jpg

Thanks a lot, @lauremi!


THRIFT-3064 added default handler for undeclared exceptions in php gener...

PHP app crashes on every undeclared exception.
But it isn't necessary declare all internal exceptions (like RedisException, DoctrineException, etc.) in .thrift file. They should be catched and serialized by Thrift into TApplicationException (aka INTERNAL_ERROR).
It will be more informative than plane 500 HTTP code.

What was that?


ERROR_INTERNAL_DB_CORRUPTION

Version: 9.0.1
OS/Distro: OSX 10.14.4
my coleague Mac was joind with osx default method, but one days it started giving error "error during connection with server idrogeno.antea.bogus". so I leave domain, and install pbis
when I try to join, I have error:
Error: ERROR_INTERNAL_DB_CORRUPTION [code 0x0000054e]
and cant join, what I can try to do? thanks

I would check on your Domain Controllers and hope you have backups. Review the windows systems event viewer for errors.
System Error Codes (1300-1699)

ERROR_INTERNAL_DB_CORRUPTION
1358 (0x54E)
Unable to complete the requested operation because of either a catastrophic media failure or a data structure corruption on the disk.

uhm strange, but I'll check
I've 2 domain controllers, I'll try turning off the corrupted one and trying to join to the other
I'll update you tomorrow
thanks

as you wrote, the db corrupted was the server one
sorry

No worries. Thanks for the update.


Use in tablet the rationale is too large,even over screen.

Basic Information
Device type: HUAWEI M6
OS version: Android 9
EasyPermissions version: 2.0.1
Describe the problem
The rationale is too large,even over screen.
What happened?  What did you expect to happen?
Code and logs
// TODO(you): show the code that produces the problem,
//            and any relevant logs.

@GitABiao could you show a screenshot of how this looks on the device?

It`s like this

@GitABiao Thank you for the screenshot attached, I tried to reproduce it on simulator forcing rotate screen but unfortunately was no been posible. The devices are Nexus 10 and Pixel C with similar screen resolution with Huawei M6 (2.560 x 1.600)

Could you trying to execute the sample project of this library, to discard posible errors with integration. You could reproduce the same error on a different tablet?

click cancel

@GitABiao it would really help if you showed the code you're using to launch the problematic dialog.

I have confirmed that the dialog created by Huawei M6 using Android api will also appear in the same situation I sent, it should not be a bug in this framework.

@GitABiao That have a lot of sense, basically because the library use the dialog android component for display the rationale message dialog. Thank you for the clarification.
The only solution what I see there is to create a custom view for display, instead the dialog or create an optional callback on request permission method for giving the option to create the user any view their want for show the rationale message, but maybe this is out of scope of library.

@GitABiao thank you for following up and confirming it wasn't something in our code!  I really appreciate it,


The rendered image is not sharp as that in c-ray readme

This is rendered output on M1 MacBook Pro, you may notice it is not as sharp as your demo in readme.
To make it sharper, what should I do?  Appreciated.
BTW, I disabled SDL2 when compiling, does that influence the result?

For easier comparision, I uploaded zipped image here.
rendered_0000.png.zip

The default resolution for that scene is set in the json file at 1280x800, so half that in the README example. You can adjust it by directly editing the json, or by using the -d command line flag to override it. You can see how to use it by running bin/c-ray -h

The default resolution for that scene is set in the json file at 1280x800, so half that in the README example. You can adjust it by directly editing the json, or by using the -d command line flag to override it. You can see how to use it by running bin/c-ray -h

Hi vkoskiv, thanks a lot, it helps.  When I set higher resolution, let say, 5120x3200. on M1 MacBook Pro, the CPU usage reaches 100%, I have a 3060 TI GPU on PC(Windows/Ubuntu), is c-ray written with support of GPU acceleration. Appreciated.

There is no planned GPU support at this time.
Glad you got it working!


SuperCollider: links written within parenthesis are unusable

In SuperCollider HelpFiles, all linkes written within parenthesis are unusable. Link hrefs still contain the closing parenthesis, leading to a variety of 404 pages.
For example, in FluidBufSpectralShape, if I try to click on "(https://www.audiocontentanalysis.org/)", I get redirected to https://www.audiocontentanalysis.org/).

@tedmoore can I assign this one to you as you are more familiar with the SC docs?
@elgiano thanks for raising this. Pretty critical we make links work I'd think :)

Unfortunately @elgiano, these links are working for me, including the one in question. So maybe it's a Linux issue? I don't have a Linux machine nearby, so maybe the next time we do beta testing we'll double check this on all the OSes.

@tedmoore
Interesting... could you please do one more check for me?
Open the generated html file for FluidBufSpectralShape, here is how to find it, in case you need:
SCDoc.findHelpFile("FluidBufSpectralShape")

Line 56 looks like this for me:

 The drawings in Peeters 2003 (http://recherche.ircam.fr/anasyn/peeters/ARTICLES/Peeters_2003_cuidadoaudiofeatures.pdf) are useful, as are the commented examples below. For the mathematically-inclined reader, the tutorials and code offered here (https://www.audiocontentanalysis.org/) are interesting to further the understanding. For examples of the impact of computing the moments in power magnitudes, and/or in exponential frequency scale, please refer to the FluidSpectralShape helpfile.

Hi @elgiano,
Thanks again for your help with this. On 1.0.0-TB2.beta6 (the current release) line 56 is something else, but line 58 is:

 The drawings in Peeters 2003 (http://recherche.ircam.fr/anasyn/peeters/ARTICLES/Peeters_2003_cuidadoaudiofeatures.pdf) are useful, as are the commented examples below. For the mathematically-inclined reader, the tutorials and code offered here (https://www.audiocontentanalysis.org/) are interesting to further the understanding. For examples of the impact of computing the moments in power magnitudes, and/or in exponential frequency scale, please refer to the FluidSpectralShape helpfile.

so no closing parenthesis inside the href.

@elgiano I've added a space both before and after the link (so just inside the parens), or ( so just inside the parens ). I hope this fixes it! Let me know if it doesn't.

@tedmoore The spaces should fix it! However, in which commit did you add them? I can't find it...

Thanks!! I'll try asap

Hi @elgiano, I'm doing a checkup pass on lots of open issues. Did you get a chance to check on this yet!? Cheers.

I just checked the main branch and there is still only one error. The rest looks all good! Thanks.
Here is the error:
$ rg mathematics release-packaging
release-packaging/HelpSource/Classes/FluidSpectralShape.schelp
11:##the four first statistical moments (https://en.wikipedia.org/wiki/Moment_(mathematics) ), more commonly known as:

release-packaging/HelpSource/Classes/FluidBufSpectralShape.schelp
12:##the four first statistical moments (https://en.wikipedia.org/wiki/Moment_(mathematics) ), more commonly known as:

$ rg mathematics install
install/FluidCorpusManipulation/HelpSource/Classes/FluidSpectralShape.schelp
16:    the four first statistical moments (LINK::https://en.wikipedia.org/wiki/Moment_(mathematics)::), more commonly known as:

install/FluidCorpusManipulation/HelpSource/Classes/FluidBufSpectralShape.schelp
16:    the four first statistical moments (LINK::https://en.wikipedia.org/wiki/Moment_(mathematics::) ):

install/FluidCorpusManipulation/HelpSource/sc_ref/Classes/FluidSpectralShape.schelp
16:    the four first statistical moments (LINK::https://en.wikipedia.org/wiki/Moment_(mathematics)::), more commonly known as:

install/FluidCorpusManipulation/HelpSource/sc_ref/Classes/FluidBufSpectralShape.schelp
16:    the four first statistical moments (LINK::https://en.wikipedia.org/wiki/Moment_(mathematics::) ):

As you can see, in FluidBufSpectralShape one closing parenthesis is erroneously excluded from the URL. However, this does not happen in FluidSpectralShape even though the respective HelpSources from release-packaging look exactly the same. Strange, isn't it?
The latest release for linux has the same error. However, the error doesn't happen if I build with -DDOCS=OFF, i.e. sclang parses the links correctly when they are not previously wrapped in a LINK::[...]::.


clonograph adjustment + trajectory error

How can I get more mutations in the clonal architecture portion of the clonograph? The default is set to 3 but I'd like to increase it.
Also I get this issue with the trajectory analysis...
sce_subset<-trajectory_analysis(sce_subset)
[1] "Building MDP"
[1] 27
[1] "Adding Weighted Edges"
Error in UseMethod("rename") :
no applicable method for 'rename' applied to an object of class "NULL"
Appreciate any support-thanks!

Hello,
I can help with a few different things here. Let's start with the easier changes:

This error is because the trajectory_analysis function assumes we are assessing allele dropout by default. Likely if you look into your sce_subset variable with View(sce_subset), you will see in the metadata tab there is no list called FalsePositive. This is needed for the trajectory analysis.
Due to it taking a longer time to run, and not being needed for a majority of analysis we have turned off allele dropout in an earlier function by default.
To fix this, please use the skip_ploidy=FALSE variable in the compute_clone_statistics function earlier in the code. So it should look similar to this:
sce<-compute_clone_statistics(sce,skip_ploidy=FALSE)
Afterwards you can run select_clones like normal and the trajectory_analysis like normal.

The number of mutations is determined by filtering variant_of_interest differently to accept more mutations, and it is based on the cutoff values of the tapestri_h5_to_sce function. This is problem dependent and without knowing more we can't adequately help point in the right direction other than to decrease the values for each filter. Alternatively, in our example vignette we use genes_of_interest to prune our variant list down. Please feel free to ask more specific questions about the different filters and we can help you out.


Text transformation problems

"â" is reduced to a dash. You could find Bandar-e 'Abb-s from original Vic2 Bandar-e 'Abbâs or French Île de P-ques for Île de Pâques. "ž" got itself corrupting to ÅŸ and, somehow, "Ö" works perfectly fine and gets converted as such. (EDIT) Proof:

I kind of suspect that Vic2 isn't really using 8859-15 encoding, but perhaps the 1252 coding page. That needs to be further researched, and if true, the code updated appropriately.

Adding to the madness, here it is how "š" is somehow both supported and unsupported by the latest release.

Turns out this is two separate problems, so I opened the second as issue #608


fix: signature window no longer overlaps cursor

I had an issue where the signature help window was covering the cursor if there was not enough space above or below the cursor.
Not sure if this is the correct way to go about fixing it, I think in the future it should have the direction priority like what autocomplete has. I don't know lua though, so best I can do is a temporary solution.

I've pulled your changes from this PR into my own, and I no longer see overlapped cursor.
Hope this one gets merged asap