[All Distros] Default PyAssimp version 4.1.4 causes silent crash when loading STL through MoveIt's PlanningSceneInterface

Describe the bug
PyAssimp version 4.1.4 causes a silent crash when loading STL through MoveIt's PlanningSceneInterface (Python).
The issue can be fixed by installing pyAssimp==4.1.3. The issue is present in both Melodic and Noetic and seems to be rather old (https://github.com/ros-planning/moveit/issues/86#issuecomment-480698001, https://answers.ros.org/question/316515/cannot-add-mesh-files-to-moveit/) and related to pyAssimp itself rather than ROS (https://github.com/assimp/assimp/issues/2343) .
A potential solution is to change the installed version in  patch.bat
To Reproduce
Please see the attached MRE: example.zip
Steps:
roslaunch panda_moveit_config demo.launch
rosrun panda_moveit_config src/attached_obj_collision.py

attached_obj_collision.py silently fails after printing MoveIt commander ok, objects are not added into the scene, trajectory is not planned.
Expected behavior
Running attached_obj_collision.py (violet object in the attached image) should load work_object.stl into the planning scene and execute the trajectory around two green boxes.

Environment information:

OS version: Win11 22H2 22621.1105
Chocolatey Versions:

Chocolatey v1.2.0
chocolatey-compatibility.extension 1.0.0
chocolatey-core.extension 1.4.0
chocolatey-windowsupdate.extension 1.0.5
KB2919355 1.0.20160915
KB2919442 1.0.20160915
KB2999226 1.0.20181019
KB3033929 1.0.5
KB3035131 1.0.3
ros-melodic-moveit 20201<IP_ADDRESS>4300002
vcredist140 14.34.31931
vcredist2010 10.0.40219.32503
11 packages installed.

Thanks for the report. Given the upstream issue, I'm tagging on all distros to validate.

Hi! Is ROS2-Iron supported on Win11?

The doc said they only support Win10.


Process for reading .circle file with typescript

Compile the corresponding circle_schema file.

Download the executable file appropriate for your OS from FlatBuffers release 2.0.0.
It can be compiled into various languages as shown in the picture below.

Enter the following command:
flatc --ts -o ./{path to save} ./schema.fbs
You can see the compiled result in the specified path.
Now we need to find a way to read the circle file with this compiled output.

/cc @yesfordev @parkjisu6239 @donggillee-dev @wnsdud4197

Thank you for your explanation👍

Thank u!! :)
but now it seems that javascript is not supported. T.T

In https://google.github.io/flatbuffers/flatbuffers_guide_use_javascript.html, following announcement is found :(
Due to the complexity related with large amounts of JS flavors and module types, native JS support has been replaced in 2.0 by transpilation from TypeScript.

Please look at TypeScript usage and transpile your sources to desired JS flavor. The minimal steps to get up and running with JS are:

Generate TS files from *.fbs by using the --ts option.
Transpile resulting TS files to desired JS flavor using tsc (see https://www.typescriptlang.org/download for installation instructions).

Could you let me know about the information you want to read?

@yesfordev
There is a way but it looks complicated
transpile into javascript

There is a way but it looks complicated
transpile into javascript

This repo is(will be) developed with TypeScript...

Could you let me know about the information you want to read?

We need to check circle file information using circle_schema. I am trying to check circle_schema by converting it to javascript or typescript by using flatbuffers! :)

We need to check circle file information

Another way is to develop npm native module library in ONE and use it here... somehow...

This is a view point of execution time of flatbuffer validation time taken in JS engine
If this takes too long with JS (or TypeScript) for typical .circle file, several MB to several 10 MB, it is not good environment to work on.

@CODe1995
Result FLATBUFFER 2.0 seems to be quite different with FLATBUFFER 1.xx -_-
In FLATBUFFER 1.10, .ts is also generated as only one file.


How do I change the walls

I was wondering how to change the walls to make them straight instead of rounded. I was looking around in the code and found what rounded them. But I'm not quite sure how to straighten them. I haven't messed with js for years so I'm quit rusty, Plus I never made much of an effort with java, python was always more my style.

Hey there
thanks for your message. Can you explain what you mean by "straighten the
walls"? They do not look "unstraight" to me? :)
I am also more into Python than Java, fortunately I did not have to use
Java in my Pacman project.
Looking forward to your reply
cheers
Chris
Am 22.03.2016 15:32 schrieb "zshep99"<EMAIL_ADDRESS>
I was wondering how to change the walls to make them straight instead of
rounded. I was looking around in the code and found what rounded them. But
I'm not quite sure how to straighten them. I haven't messed with js for
years so I'm quit rusty, Plus I never made much of an effort with java,
python was always more my style.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
https://github.com/daleharvey/pacman/issues/12

@platzhersh Sorry, could have been a little clearer. I noticed most of the lines were curved where they join together. I wanted to make them straight and more rectangular.


Separate repo size calculation into shared view model.

Or we can get it from Kubo API:
https://docs.ipfs.tech/reference/kubo/rpc/#api-v0-repo-stat


Wine and sprits

Add new icon(s) to the library

Name: Wine and spirits
Description: 3 sizes of the Wine and spirit icon (16, 24, 32px)

The icon(s) per this request, has the new art been completed?

[X] Yes
[ ] No

If YES, does the new icon art follow all the recommendations from the Auro Icon Design Guidelines?

[X] Yes
[ ] No

If YES, the icon(s) in the request, have they been added to the UiKit Abstract repo?

[X] Yes
[ ] No

Attach exported SVG files to this issue
See the options below for attaching a file to this request.

Already have this in our library.


fix(tool-bar-btn): target span, not button

and feat(logo): use ui theme colour for more pleasing aesthetic

Thanks Ben. Merged! As I put into the merge commit message, I made the logo blue on a whim and you found the best way to indulge that whim. Thanks! Also thanks for catching the span/button bug. As you probably know, those buttons were indeed actual buttons originally and I missed changing them when I cut over to spans.

No problem! It was clashing with my UI theme which has its own nice blue, which gave me the idea.


[Bug]: Pop with content from the image edition completion callback doesn't transfer the content

Package Version
4.0.4
Flutter Version
3.22.2
Platforms
Android
How to reproduce?
I'm trying to get the result (bytes) of my page redirection :
Future<void> _onImageEditionCompleted(
    BuildContext context, {
    required Uint8List bytes,
  }) async {
      log(bytess.toString()) // Has content
      Navigator.pop(context, bytes);
  }

  @override
  Widget build(BuildContext context) {
    return ProImageEditor.memory(
      image,
      callbacks: ProImageEditorCallbacks(
        onImageEditingComplete: (bytes) => _onImageEditionCompleted(
          context,
          bytes: bytes,
        ),
      ),
      configs: configs,
    );
  }

Log the result of the page (result of null) :
log((await Navigator.push(
        context,
        MaterialPageRoute(
          builder: (context) => WidgetImageEditor(
            image: image,
            configs: configs,
          ),
        ),
      )).toString()); // Result null

The result of the pop page doesn't return you the bytes.
Logs (optional)
No response
Example code (optional)
No response
Device Model (optional)
Crosscall

Hello,
This is a normal behavior, because the editor internally needs to call Navigator.pop to close the loading-dialog. However, if you want to close the page with the final result bytes, you can do it like below.
Uint8List? _result;

@override
Widget build(BuildContext context) {
  return ProImageEditor.memory(
    image,
    callbacks: ProImageEditorCallbacks(
      onImageEditingComplete: (bytes) async => _result = bytes,
      onCloseEditor: () => Navigator.pop(context, _result),
    ),
    configs: configs,
  );
}


raw3-1 emergency state topic in wrong ns

in raw3-1.xml the relayboard.launch is started in simulation mode which results in a wrong ns of the /emergency_stop_state topic (which is relayboard/emergency_stop_state) and the robot can not be moved.

This PR https://github.com/ipa320/cob_robots/pull/395  solves the problem

Even if #395 solves the namespace problem in simulation....why is this node run in simulation on real hardware anyways?

I guess because the r@w does not have a relayboard. How is it handled on cob4?

If raw3-1 does not have a relayboard, we should not have the robot to require a topic coming from this node in order to be able to operate it...

Even if #395 solves the namespace problem in simulation....why is this node run in simulation mode on real hardware anyways? There seems to be something wrong about this...

This is something I found out a year a go or so, but I was never really sure and had time to change it for all robots. For raw3-5 should be changed in #400

I guess because the r@w does not have a relayboard.

raw3-5 has? Or at least can publish this topics through phidgetboard. Probably I have to look at it again more closely.... Anyway I solved it for raw3-5...

Yes, the emergency_stop_state  topic can be published from a phidget board.

But than on all r@ws (if all have phidged board) this:
<include file="$(find cob_bringup)/drivers/relayboard.launch" >
		<arg name="sim" value="true" />
</include>

should be changed for this:
<include file="$(find cob_bringup)/drivers/phidgets.launch" >
		<arg name="robot" value="$(arg robot)" />
</include>

as I did in #400

True, but not all have a phidget board (actually, I'm not sure if there not only two that actually have one). And there are different versions. We have to check with our r@w's, at least the two that are still at IPA. For the rest, we need to keep it as is.

Ok check it, at KIT we have phidgetboard, so for raw3-5 it can be also changed.

from my point of view just two things need to be done.

merge PR #395 because we still need the simulated relayboard for robots without relayboard and phidgetboard.
replace relayboard launch with phidgetboard launch for raw3-1 and raw3-5. raw3-3 was already changed and the other raw's do not have a phidget board.

because we still need the simulated relayboard for robots without relayboard and phidgetboard.
Why? Which node requires the topic to be available?
Is it only me who thinks it is strange that a (software) node (I don't know which one it is) requires a hardware to be present in order to work...?
I thought we use "simulated" nodes in order to have the same set of topics and message in simulation than we do on the respective hardware. NOT for making all hardware setups equal in case one does not have a relayboard...

Alright. The /emergency_stop_state topic is required by the cob_undercarriage_control node (subscriber callback / setter function in controller / block calculation of control step if in EM stop).
I guess this is a left over from the cob3-era, where all cob3's had a relayboard.
I'm not sure if this is used anywhere else (diagonstics? @ipa-fmw, cob_omni_drive_controller? @ipa-mdl) or how the controllers behave, if we where to remove this.
If the emergency_stop_state is set to true, the output commands will be 0.0 and some internal controller state variables will be reset. If this, however, is required, and how the control behaviour will change then, I cannot say. Maybe worth a test.

as @ipa-mig wrote, cob_undercarriage_control needs the emergency_stop_state topic to be published. If it's not published the base will not move. This behavior is implemented because of safety reasons. (No EM Stop State means that there is probably something wrong and we should not move the base).

Yes, the base should not be moved in case of EM-Stop, but this is enforced due to the EM-Stop cutting of the power from the drives - on the hardware-side!
It should not need to be handled by software...even more, the hardware will not start to move after the EM-Stop has been released again without recovering it anyways...

Yes to both. It would be nice to have this topic and handle the different controllers respectively.
Especially, as it allows for differntiating between button stop and scanner stop.
However, if the sim node is used, the emergency stop flags are always false, i.e. not in EM stop. Thus, I guess it could be removed.

It should not need to be handled by software...even more, the hardware will not start to move after the EM-Stop has been released again without recovering it anyways...

The software controller should reset its internals in order to not jump after recover.
Within the migration of the platform controllers to ROS (for cob3) the emergency_stop_state was introduces and the EM stop was handled in (too) many places.

How is it handled on cob4?

The topic is published by cob_safety_controller, but it is used only on cob4-2 with the old drives.

cob_omni_drive_controller?

The new base chain does not need this topic anymore, since `ros_canopen reset the controller internally.

The new base chain does not need this topic anymore, since ros_canopen resets the controller internally.

The software controller should reset its internals in order to not jump after recover.

How is this handled therein, i.e. how does the controller know when to reset?

How is this handled therein, i.e. how does the controller know when to reset?

The controller does not know this, but ros_canopen/ros_control reset the controller.
Not only in case of EM stops, but as well for mode switches etc.

Yes, but what triggers the reset? The EM stop as well? Then, this needs to be known by ros_canopen/ros_control. How so?
 ;-)

Then, this needs to be known by ros_canopen/ros_control. How so?

This is a different question ;)
The Elmo controller reports the failure via a CANopen emergency message.
For old Elmos and Schunk you get a motor undervoltage error and for the new Elmos you get a Safety stop error :)
cob_canopen_motor disabled these error messages for some reason.

Alright, so the new modules don't rely on the emergency_stop_state topic anymore. Understood ;-)

Trying to catch up on this:
I guess the approach to follow is what @ipa-bnm wrote in https://github.com/ipa320/cob_robots/issues/403#issuecomment-173558816:

none of the raw's have real relayboard
raw3-1, raw3-3 and raw3-5 have phidgetboard that is able to publish the required emergency_stop_state topic. thus, for them relayboard sim should be removed and phidgetboard added
raw3-2, raw3-4 and raw3-6 will use relayboard sim
https://github.com/ipa320/cob_robots/pull/395 needs to be merged
modification of cob_undercarriage_control is not worth the effort as it is going to be deprecated/removed soon anyway...

@ipa-mig, @ipa-bnm @destogl please confirm or correct me if I'm wrong.....

as far as I see, you are correct.
I'm unsure if the phidget boards are all the same, are wired correctly/the same or if there are any discrepancies between raw3-1, 3-3 and 3-5.

You are correct.

Seems legit.
I suggest to migrate just the robots that have their EM wiring confirmed.

configuration of phidget board in #400 is correct for raw3-5


Update runbook re bucket name

Link to Ticket
Description of Changes Made
Make sure runbook has the correct production bucket name
How to Test
Screenshots

Expand to see more

MR Checklist

[x] Add a description of your pull request and instructions for the reviewer to verify your work.
[x] If your pull request is for a specific ticket, link to it in the description.
[x] Stay on point and keep it small so the merge request can be easily reviewed.
[x] Tests and linting passes.

Unit tests

[ ] Added
[x] Not required

Documentation

[x] Updated build docs
[ ] Updated editor guidelines (https://docs.google.com/document/d/1PAWccdQ4tfaZsrEWmpDhvP3GH5RRmBOARFVp4b-kje8/edit?usp=sharing)
[ ] Updated field spec (https://docs.google.com/spreadsheets/d/1v1yqcSC54Vag4mxmTp8e6ZrnxITqzbjCA4A9XPQdXk8/edit?usp=sharing)
[ ] Not required

Browser testing

[ ] I have tested in the following browsers and environments (edit the list as required)

Latest version of Chrome on mac
Latest version of Firefox on mac
Latest version of Safari on mac
Safari on last two versions of iOS
Chrome on last two versions of Android

[x] Not required

Data protection

[x] Not relevant
[ ] This adds new sources of PII and documents it and modifies Birdbath processors accordingly

Accessibility

[ ] Automated WCAG 2.1 tests pass
[ ] HTML validation passes
[ ] Manual WCAG 2.1 tests completed
[ ] I have tested in a screen reader
[ ] I have tested in high-contrast mode
[ ] Any animations removed for prefers-reduced-motion
[x] Not required

Sustainability

[ ] Images are optimised and lazy-loading used where appropriate
[ ] SVGs have been optimised
[ ] Perfomance and transfer of data considered
[ ] If JavaScript is needed alternatives have been considered
[x] Not required

Pattern library

[ ] The pattern library component for this template displays correctly, and does not break parent templates
[ ] The styleguide is updated if relevant
[x] Changes are not relevant the pattern library

@nickmoreton have put you as a reviewer as you are also making changes to the runbook in the wagtail upgrade mr.

@nickmoreton have put you as a reviewer as you are also making changes to the runbook in the wagtail upgrade mr.

removing you again as dan has reviewed.


Defensive copying for data source

Should we add defensive sopying to ListDataSource constructor ?

@nesterov-n I think we can add this as a feature. It's not something that we need every time, but nice option to have


Having Trouble with Minus in JsonPath

Are you experiencing an issue with...
shields.io
🐞 Description
When trying to reference vue-i18n with a jsonpath badge, I get unparseable jsonpath query while https://jsonpath.com/ says everything works fine.
The json ressource is: https://raw.githubusercontent.com/IT4Change/boilerplate-frontend/master/package.json
The queries, which all work on jsonpath, but not on the badge for some reasons are:

dependencies.vue-i18n
dependencies.$['vue-i18n']
dependencies.'vue-i18n'
...

Related issue: https://github.com/badges/shields/issues/5580
🔗 Link to the badge
https://img.shields.io/badge/dynamic/json?url=https%3A%2F%2Fraw.githubusercontent.com%2FIT4Change%2Fboilerplate-frontend%2Fmaster%2Fpackage.json&query=dependencies.vue-i18n&label=vue-i18n&color=green

💡 Possible Solution
Unknown
Related issue, which did not solve my problem even tho it did for the author: https://github.com/badges/shields/issues/5580

Looks like https://img.shields.io/badge/dynamic/json?url=https%3A%2F%2Fraw.githubusercontent.com%2FIT4Change%2Fboilerplate-frontend%2Fmaster%2Fpackage.json&query=dependencies['vue-i18n']&label=vue-i18n&color=green is what you're trying to do?
That's dependencies['vue-i18n'] with the single quotes URL encoded.

Works like a charm, thank you ❤
Sorry for borthering.


Innocuous Change

It's really me.. BEN. Just testing that I can contribute from outside of the sf org

POC


Support Svelte 4

WIP
Linked Issue
Closes #1689
Description
Adds support for Svelte 4. Currently a WIP.
Current issues:

[x] Some dependencies haven't updated their peerDependencies to include Svelte 4 yet, so we're going to see warnings like this for now (fortunately, it's not a breaking issue and are just annoying warnings):

[x] Need to perform a full audit making sure we cover everything from the migration guide
[ ] There are 2 kinds of a11y warnings that comes with Svelte 4 that we should resolve before merging:

https://github.com/jsx-eslint/eslint-plugin-jsx-a11y/blob/main/docs/rules/no-static-element-interactions.md
https://github.com/jsx-eslint/eslint-plugin-jsx-a11y/blob/main/docs/rules/no-noninteractive-element-interactions.md

[ ] Determine the lowest version of Svelte we want to support

Changsets
Instructions: Changesets automate our changelog. If you modify files in /packages/skeleton, run pnpm changeset in the root of the monorepo, follow the prompts, then commit the markdown file. Changes that add features should be minor while chores and bugfixes should be patch. Please prefix the changeset message with feat:, bugfix: or chore:.
Checklist
Please read and apply all contribution requirements.

[ ] This PR targets the dev branch (NEVER master)
[ ] Documentation reflects all relevant changes
[ ] Branch is prefixed with: docs/, feat/, chore/, bugfix/
[ ] Ensure Svelte and Typescript linting is current - run pnpm check
[ ] Ensure Prettier linting is current - run pnpm format
[ ] All test cases are passing - run pnpm test
[ ] Includes a changeset (if relevant; see above)

The svelte-check is failing due to @testing-library/svelte missing it's types module path in their exports map. Currently waiting for this PR https://github.com/testing-library/svelte-testing-library/pull/228 to merge.

I've successfully tested a tarball of this in my wiki app, seemed to be working well!

Just noting that myself and @Mahmoud-zino tested a variety of projects, including the Skeleton doc site and multiple standalone Skeleton apps. All were working great!


Upgraded all dependencies

This fixes #6

Sorry, there is a conflict. Could you help fix it?

@dtinth conflicts fixed


wrap-up section for guide?

some sort of wrap-up section might be helpful. something like
'Chapter 6. What next?'
for me, 'what next?' is definitely that I want to learn wdl syntax.  this wrap-up section could be a good spot to list the sources of help you linked to elsewhere in the guide (right now they're buried somewhere in the middle).  Both Hutch-based help, as well as external links to WDL syntax/language definition.
I don't know what Amanda's owl meme referred to, but I can totally imagine - right now I have a big gap in my ability to actually use WDL.  The guide was very helpful in seeing how I can submit/monitor/troubleshoot a workflow here at the Hutch, but figuring out the workflow itself is a huge black box for me.

100% I think actually this is a good sign.  This WDL 101 class was actually intended JUST to get you able to RUN the test workflows successfully.  Now on to WDL 102, which is a guide I know have the luxury of being able to put together and have someone actually read it!!!


StackOverflow Exception on Cycles

I'm getting a StackOverflow Exception on the code below. I think it may have something to do with the fact that Company and Employee both reference each other. Is there a way around this?
using System;
using System.Collections.Generic;
using System.Linq;
using System.Text;
using System.Threading.Tasks;
using Bond;
using Bond.IO.Unsafe;
using Bond.Protocols;

namespace BondSimpleExample
{
    [Schema]
    public class Company
    {
        [Id(0)]
        public string Name;
        [Id(1)]
        public double MarketValue;
        [Id(2)]
        public List<Employee> Employees;
    }
    [Schema]
    public class Employee
    {
        [Id(0)]
        public string Name { get; set; }
        [Id(1)]
        public int Age { get; set; }
        [Id(2)]
        public int ID { get; set; }
        public enum GenderTypes { Male, Female }
        [Id(3)]
        public GenderTypes Gender { get; set; }
        [Id(4)]
        public double Salary { get; set; }
        [Id(5)]
        public Company Company { get; set; }
    }
    class Program
    {
        static void Main(string[] args)
        {
            var emp1 = new Employee()
            {
                Name = "John Doe",
                Age = 33,
                ID = 10001,
                Gender = Employee.GenderTypes.Male,
                Salary = 56700,
                Company = null,
            };
            var emp2 = new Employee()
            {
                Name = "Sarah Connor",
                Age = 36,
                ID = 10002,
                Salary = 62500,
                Company = null,
            };
            var comp = new Company()
            {
                Name = "Skynet",
                MarketValue =<PHONE_NUMBER>3,
                Employees = new List<Employee>()
            };
            comp.Employees.AddRange(new[] { emp1, emp2 });
            emp1.Company = emp2.Company = comp;
            var serializer = new Serializer<CompactBinaryWriter<OutputBuffer>>(typeof(Employee));
            var deserializer = new Deserializer<CompactBinaryReader<InputBuffer>>(typeof(Employee));
            var output = new OutputBuffer();
            var writer = new CompactBinaryWriter<OutputBuffer>(output);

            Console.WriteLine("Employee Name: " + emp1.Name);
            Console.WriteLine("Serializing Employee");
            serializer.Serialize(emp1, writer);
            Console.WriteLine("Serialized Successful");
            Console.ReadKey();
        }
    }
}

#39
Bummer, if this is the same issue then you can go ahead and close this issue. Fingers Crossed

Yes, this is the same as #39.

Yes, these two issues are the same.
Even Bond itself it hit by this problem. Take a look at the Bond types TypeDef and SchemaDef used to represent schemas. You can think of the struct_def field in TypeDef as a hand-rolled pointer.


Add missing requirements

Summary

How to test

Checklist

[ ] I have added unit tests to cover my changes.
[ ] I have added integration tests to cover my changes.
[ ] I have added the description of my changes into CHANGELOG.
[ ] I have updated the documentation accordingly

License

[x] I submit my code changes under the same MIT License that covers the project.
Feel free to contact the maintainers if that's a concern.
[x] I have updated the license header for each file (see an example below)

# Copyright (C) 2023 Intel Corporation
#
# SPDX-License-Identifier: MIT

Codecov Report
Patch coverage has no change and project coverage change: -0.01 :warning:

Comparison is base (f67fc90) 78.49% compared to head (c302854) 78.49%.

Additional details and impacted files
@@             Coverage Diff             @@
##           develop     #877      +/-   ##
===========================================
- Coverage    78.49%   78.49%   -0.01%
===========================================
  Files          206      206
  Lines        24939    24939
  Branches      5007     5007
===========================================
- Hits         19577    19575       -2
- Misses        4236     4237       +1
- Partials      1126     1127       +1

Flag
Coverage Δ

macos-11_Python-3.8
?

ubuntu-20.04_Python-3.8
78.49% <ø> (ø)

windows-2019_Python-3.8
?

Flags with carried forward coverage won't be shown. Click here to find out more.
see 1 file with indirect coverage changes
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.

LGTM
@wonjuleee I think we need to have a time to update ./3rd-party.txt before releasing 1.1.0.

Yes, I think so. Let me request to generate this from the system.


glav.su - some requests are not blocked

https://github.com/AdguardTeam/AdguardFilters/issues/39814
https://glav.su/forum/4/432/messages/?offset=20
Not all an.yandex.ru requests are blocked.

Screenshots

Screenshot 1

System configuration

Information
value

Platform:
Win

AdGuard version:
7.2.2910.0

Browser:
Chrome

AdGuard driver:
WFP

Filters:
AdGuard Russian,AdGuard Annoyances,AdGuard Base,AdGuard Tracking Protection,AdGuard Social Media

logs.zip

the same issue
https://github.com/AdguardTeam/AdguardFilters/issues/39744
requests to fafc5ra6.ru must be blocked by .ru/show/?*=*&*=*&*=*&$script,third-party
It is blocked by browser extension.


package generation for tizen and webos platforms

Hi,
in the given demo examples, the package generation done through gruntfile for tizen doesn't result in the expected .wgt file where as by default in the demos package folder you have the tizen zip file on extraction of which where we have the .wgt file, if we generate grunt build for the tizen platform. the package is no different from the legacy orsay platform? are we missing something here?
the grunt file doesn't have the webOS build generation can you please help on that too.
Thanks

Hi Rkdroidm
That is because both platforms needed their own IDE installed, must be build in SDK (Tizen) or exe files from their SDK is needed (webOS).

Hi Daniel,
Thanks for the info, can you please provide your point on developing the smart tv application on angularJS platform, specific to using it for the user interface part. with the approach you have currently it will be little difficult to achieve the separations of concerns as there is a lot of html sitting in JS code.
Thanks

Hi Rkdroid,
So, we doesn't use angularJS, but you can use some of templates frameworks.

yeah, i have tried with handlebars it works okay, but do you see any drawbacks of developing the app on Angular JS framework, example:  might be resource heavy which in turn can lead to lag in UI navigation especially with grids.
do you see this as a problem or should be fine going head with angularJS for development?

Be aware, most of old televisions have not good performance. This also applies for example to css and javascript animations.

Hi Rkdroid,
Did the answer help you? If yes please close the issue.
Thanks
Mautilus SmartTV SDK Team

Thanks Daniel, it was helpful.


local mode looses error messages and loops forever

Following https://github.com/dotnet/crank/blob/master/docs/local_application.md I malevolently put a syntax error into samples/hello/Program.cs and run the crank. (I am not using code to edit c#, but plain old vi.)
I don't see where the error messages end up.  I can't find a log file.  The error messages don't seem to come out on stderr.
The crank engine spits out this string once per second, for 3 minutes, before complaining that the job didn't start.
[09:51:30.228] Processing job 'application' (9) in state Starting

I'm having a similar issue, except that as far as I know I don't have any syntax error in my app. It builds and runs just fine when I run it locally using dotnet run. I'm guessing there's something going wrong during startup, but I don't see any output from that anywhere.

I installed Crank on my machine today using the documented instructions. If that gets me the latest version then I think it has not been fixed unfortunately. Or do I need to do something special to get the latest build?

Thanks, the change was in the agent. I did the change on Friday and someone provided a fix related to it yesterday.
Can you share your project file? I want to see how you specified the assembly name.
Relevant code:
https://github.com/dotnet/crank/blob/master/src/Microsoft.Crank.Agent/Startup.cs#L2577-L2592

I've defined it as follows:
<Project Sdk="Microsoft.NET.Sdk.Web">

  <PropertyGroup>
    <TargetFramework>net5.0</TargetFramework>
    <AssemblyName>RR.ApiGateway</AssemblyName>
    ...
  </PropertyGroup>
  ...
</Project>

If I look at that code I would say that would work.

Ah, I thought you were using the code one.
I will update the package soon and let you know. You can try with the source in the meantime.

Fixed

@sebastienros Does your comment mean you've updated the package, because I'm still seeing a version from 19 days ago up on NuGet? Or are you referring to the code fix?


Not working with VSCode on Windows

With windows, I am facing below issue while saving the flow.
Error: ENOENT: no such file or directory, open 'C:\c:\Code\vscodeFolder\rrrd.yaml
Looks like the file path is not resolved properly in the extension for windows style.

Same problem.
Issue described in https://github.com/apache/camel-karavan/issues/72

Duplicate of #72. Hence closing!


Add support for directly decoding/encoding DNS PTR Records

Motivation:
The current implementation will provide a DnsRawRecord, which, while
containing the host name it resolves to, would require the user to
decode the name using the decode method currently private to
DefaultDnsRecordDecoder, which in fact means copying it.
Modifications:
Introduce DnsPtrRecord, which is a specialization of DnsRecord which
provides a decoded host name.
Result:
PTR Records are much easier to work with, as the name is decoded already.

@trustin tweeted me that we should do that :)
https://twitter.com/trustin/status/703763956934930432
I was using netty to reverse lookup IP addresses.
The code still requires the nasty reversing of IP, which I also want to write a helper for, but in general looks like this
      AddressedEnvelope<DnsResponse, InetSocketAddress> response = resolver.query(new Ipv4ReverseLookup(ipv4)).get();
      if (response instanceof DnsResponse) {
        DnsResponse dnsResponse = (DnsResponse) response;
        if (DnsResponseCode.NOERROR.equals(dnsResponse.code()) && (dnsResponse.count(DnsSection.ANSWER) > 0)) {
          DnsRecord dnsRecord = dnsResponse.recordAt(DnsSection.ANSWER, 0);
          if (dnsRecord instanceof DnsRawRecord) {
            DnsRawRecord defaultDnsRawRecord = (DnsRawRecord) dnsRecord;
            dnsName = decodeName(defaultDnsRawRecord.content());
          }
        }
      }

what botherd me the most is that the DnsRawRecord contains just a ByteBuf, and I finally figured out I need to copy the decodeName method to understand its content.
So this PR will make the DnsRecord be a DnsPtrRecord, which provides the convenient hostName() method.

One think I would like to point out, is that I was unsure about the class/interface hierarchy. The biggest problem is that this is potentially not backwards compatible, for people assuming it will be a (Default)DnsRawRecord. But I thought it would be cleaner to hide the bytebuffer and actually just provide the String Hostname.
what you guys think?

@CodingFabian LGTM... @trustin WDYT ?

@trustin ping

Looks good to me except a few nits. I wonder if you would also be interested in implementing DnsA/AaaaRecord and a few other commonly used ones?

Not really, I also do not use it :)

@CodingFabian let us know once you addressed the comments

Sure, @normanmaurer @trustin what do you think about type hierarchy and casting? I am really not sure if it would not be better to make it extend the DefaultDnsRawRecord instead. while i want to hide the bytebuf, somehow it feel like th casing would be easier

nits pushed.

LGTM sans 1 nit. Great job! :-)

@CodingFabian I think it's fine not to extend DefaultDnsRawRecord. It's supposed to be only used as a fallback.

https://github.com/openssl/openssl/blob/master/CHANGES

@CodingFabian thanks!
Cherry-picked into 4.1 as 58c63b788857e503f3b48bc0d2d794d504495acb


Add Exec.to_string() and Pipeline.to_string()

The purpose of this PR is to have ready to use display functions for Exec & Pipeline.
Happy to discuss the output of the fmt functions.

I like this idea. Two remarks:

the commit message mentions to_string(), but the patch seems to implement Display::fmt.
we probably want the displayed string to quote the arguments that contain whitespace, the same way the OS shell would. For example, Exec::cmd("command").arg("foo").arg("bar") should display different than Exec::cmd("command").arg("foo bar").

@hniksic Done!

@hniksic Done. WDYT?

It's very close. Your contains_metachar checks for control characters and whitespace, but not for other shell metacharacters, such as *, ?, |, &, quote chars, backslash, and possibly others. I'd replace the lines:
                let contains_quote = arg_as_str.contains("'");
                let contains_metachar = arg_as_str.chars().any(|c| c.is_control() || c.is_whitespace());

with:
                let needs_quote = arg_as_str.chars().any(|c| !c.is_ascii_alphanumeric());

This will also quote arguments that contain punctuations such as _, but that shouldn't be a problem in practice.

Another thing: in display code, you probably want to use path.to_string_lossy() in preference to path.to_string().unwrap_or(""). That will leave replacement characters to indicate that parts of the argument could not be fully converted.

Done!

Looking at the changes, there's seems to be a left-over self.command.to_str().unwrap_or("").

I've added your changes with minor improvements to the formatting routine - instead of building a vector of args, you can simply call write!() in the loop. Also, I made it so often-used characters like ., -, and / don't cause quoting.

I've looked a bit more at how the Display trait is used in Rust, and it seems more fit for data that has a good human-readable representation, such as strings and numbers. For example, even containers don't define Display. They do define Debug, however.
Should Exec and Pipeline define a custom Debug trait instead, so that printing them with {:?} prints a nicer output?

I'm sorry but this is going too far for me. I'm not using this library any more, but I was willing to finish the PR based on your reviews.
As I need to redo everything, I'm not willing to pursue this any more. Feel free to change the code as you see fit!

@ElPicador Your contribution is still appreciated and will make it into subprocess. If I can just ask you, what was your use case for defining the Display trait?

I'm developing a CLI that runs some shell commands.
And I wanted to display to the user the command ran when if it fails.
Something like (probably not compiling):
let directory: &str = ...;
let ls = Exec::cmd("ls").arg("-l").arg(directory);
let wc = Exec::cmd("wc").arg("-l");
let cmd = ls | wc;

match cmd.capture() {
  Err(e) => println!("failed to run command {}: {}", cmd, e)
  Ok(r) => ...
}

[...]

I didn't want to construct the command twice: one for display, one to use it with subprocess.
The idea was only to have an error message, not for the user to be able to copy/paste it and run it manually.
I used the {:?} in the println, but it displayed internal state as well as the command run.

Thanks for the clarification. I am asking because Exec has a number of additional options that are not reflected in the Display::fmt we are adding, and I'm not sure if that breaks the contract of Display.
I'll definitely leave some way of accessing this string because I think it's useful, maybe it'll just need to be explicitly requested with cmd.to_string_lossy() or something like that. That will ensure the caller to be aware that there is no one-to-one correspondence between the string and the actual command.

Closing this as it seems not useful anymore


Data race causing incorrect values for solr_up metric

Running the following simple bash script causes the first request to get a value of 0 for the solr_up metric:
curl -s localhost:9231/metrics &
curl -s  localhost:9231/metrics &

It appears to be a data race, as changing line 228 of exporter.go to the following fixes it:
defer func() {
    ch <- e.up
    time.Sleep(1 * time.Millisecond)
}()

I don't know Go well enough to know what a proper fix might be, but from what I can tell it appears that the second metrics request enters the Collect function and resets the value of e.up before the first one is received and processed on the other side of the channel.

I made a fix which I believe should work. Though as I mentioned, I am far from a Go expert, so could be that it's not an optimal solution.


feat: add some SparkLikeLazyFrame methods

What type of PR is this? (check all applicable)

[ ] 💾 Refactor
[x] ✨ Feature
[ ] 🐛 Bug Fix
[ ] 🔧 Optimization
[ ] 📝 Documentation
[ ] ✅ Test
[ ] 🐳 Other

Related issues
Should we start tracking pyspark methods?
Checklist

[x] Code follows style guide (ruff)
[x] Tests added
[ ] Documented the changes

If you have comments or can explain your changes, please do so below
It adds:

with_row_index
drop_nulls
rename
unique
join

And fixes sort
TODO
There is one test failing, because of how I implemented join to coalesce columns. The test is test_left_join_overlapping_column which tries to map a column called d to one called antananarivo, which already exist, and would try to rename such one to antananarivo_right. Yet fails to do so

for tests, maybe after this one we should start adding it to constructor and xfailing things?

We have a lot of expressions that would fail 🙃 I would say to wait a little bit more for now

I am not sure if the failing test should be considered an edge case, or it is worth to create a temporary name mapping layer/step to have it run successfully 🤔 It would definitly add a fair bit of complexity

thanks! i'll take a look, but i think we should address the join test

thanks! i think a loud error like
E               pyspark.errors.exceptions.captured.AnalysisException: [COLUMN_ALREADY_EXISTS] The column `antananarivo_right` already exists. Consider to choose another name or rename the existing column.

is fine, i think it's ok to assert that for pyspark it raises


Im2Col_0: Dilation value != 1 is not supported  for square convolutions

Prerequisites
Please make sure to check off these prerequisites before submitting a bug report.

[√] Test that the bug appears on the current version of the dev-branch. Make sure to include the commit hash of the commit you checked out.
[√] Check that the issue hasn't already been reported, by checking the currently open issues.
[√] If there are steps to reproduce the problem, make sure to write them down below.
[√] If relevant, please include the ONNX files, which were created directly before and/or after the bug.

Quick summary
Sorry to bother you. Now I am using a custom network architecture to use finn, and I have encountered the problem that dilation must be '1'.
Details
I ran into problems running the InferConvInpGen() function while using finn:

That is, the InferConvInpGen() function doesn't support dilation greater than 1, but now my code needs network support for dilation greater than 1.
Then, I tried to comment out the assert field in the function, and although I successfully executed the function, I got another error when executing the following function.
model = Model.transform (ZynqBuild(platform = test_pynq_board, period_ns = target_clk_ns))

The following error occurs:

I have checked the previous issue and judged that this should be caused by the wrong generation of hls before, so I would like to ask you if there is any way to deal with the situation where dilation is greater than 1.

Hi,
can you try to use the RTL implementation of the ConvolutionInputGenerator by calling the transformation with InferConvInpGen(use_rtl_variant=True)? It should support dilation > 1.

Ok, thank you very much. I'll try again tomorrow and ask you if I have any questions.
---- Replied Message ----
| From | Felix @.> |
| Date | 07/20/2023 22:50 |
| To | @.> |
| Cc | Special-zhang @.>,
Author @.> |
| Subject | Re: [Xilinx/finn] Im2Col_0: Dilation value != 1 is not supported for square convolutions (Issue #860) |
Hi,
can you try to use the RTL implementation of the ConvolutionInputGenerator by calling the transformation with InferConvInpGen(use_rtl_variant=True)? It should support dilation > 1.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: @.***>

I'm sorry to bother you again. I used the solution you gave to solve the dilation problem, but there was an error when I set PE and SIMD value and used ZynqBuild function.
First
Since I wasn't sure how to properly configure my PE and SIMD, I used the automatic conversion functions SetFolding() and InsertAndSetFIFODepths("ZCU104") (I used ZCU104). But I got an error using InsertAndSetFIFODepths:

Seems I'm missing some ip info.
Second
I tried using the default fifo, Skip InsertAndSetFIFODepths and run model = model.transform(ZynqBuild(platform = test_pynq_board, period_ns = target_clk_ns)), but again we have a problem:

To verify if it was my network problem, I tried to run the CNV program from finn's library, but when I ran ZynqBuild, I got a similar error:

I continued to verify on TFC, but TFC's ZynqBuild function worked fine.
So now I am very confused and I hope you can help me solve it.
Finally
I want to try to configure appropriate PE and SIMD by myself. I hope you can give me some suggestions and reference configuration methods.

To get to the bottom of these failures you will need to dig deeper into the Vivado/Vitis HLS logs. See the path given by the message ("Check logs under ...") and individual run directories that might be located within them.
To get an idea about PE & SIMD, you can check out our tutorial notebook on folding: https://github.com/Xilinx/finn/blob/dev/notebooks/advanced/3_folding.ipynb

Hi, I'm terribly sorry to bother you again.
Question
With your generous help, I successfully completed the HLS generation of the custom network model. I also successfully ran the InsertAndSetFIFODepths('xczu7ev-ffvc1156-2-e') function, but its execution time was too long (more than 4 hours were not finished). So I probably won't consider this approach to building fifo depth again.
I tried to check out more information in finn's notebooks and readthedocs, and looked through issues, bugs, and code related to deep fifo design, but I didn't understand how to choose the depth of the fifo after each MVAU.
Therefore, I hope you can tell me the relevant methods and design ideas.
Extend
In the future, I want to try to do more complex network quantification operations. The total number of convolutional layers of the network should be under 50. The middle part of the network should contain multiple branches (similar to the image below), no other convolutional and fully connected layers, and mainly quantized in 2 and 4 bits.
And I choose to place the special data processing operation of preprocessing and the softmax operation of post-processing on ARM, that is, to run a series of convolution operations (2D convolution, ReLU, BN and stack) only on the FPGA chip.
Now I want to ask you to verify the feasibility of my branch design idea and whether the network architecture can be deployed in a Streamline way on ZCU104. Moreover, whether the PE and SMID Settings should be small for such a large network? Finally, how do I set the fifo depth in this network.

Thanks again

Sorry to bother you again.
Below, I have encountered the problems I encountered in carrying out the above tasks, and I hope you can answer them for me.
First
I tried the deeper network I mentioned above today, but I had issues running the GiveReadableTensorNames() function.

Then I did some debugging and I noticed that it looked like I was using weight sharing in my code (I called the same block of code multiple times).
Then I tried to unshare the weight sharing code and found that the GiveReadableTensorNames() function worked.
I then tried to verify if the problem was caused by directly using the same code block, but no matter how much I changed the shared method, it didn't seem to work.
So I would like to ask you if there is any way to make the use of weight sharing can still work.
Second
I used the non-weight sharing method to continue the following work, but I ran into a problem again.
I ran CreateDataflowPartition() and got an error.

As far as the error message is concerned, it seems that a loop in my code is causing the problem. I checked my code and the corresponding onnx file, and there is no loop issue.
I then did some testing. I ported all the convolutional subclasses from my source code to the main class implementation and fully unrolled all the convolution loops, but I was still stuck in CreateDataflowPartition() with the same error message.
Below is a snippet of the onnx file  before I did the tests.

Below is a snippet of the onnx file  that I tested.

Thanks again


Carbon Calculation

Carbon footprint is a useful metric to output.
Tools such as the following coupled with location data associated with nodes could be useful:
https://github.com/Green-Software-Foundation/carbon-aware-sdk
High Level Plan:

[ ] Phase 1 - Simple static CO2 Calculation (AKA "Getting our feet wet")
Goal: demonstrate that SusQL can report usable Carbon Emissions aggregation data as POC

Allow user defined energy->carbon conversion factor per labelgroup

"staticcarbonintensity" -- Static Carbon Intensity Factor in grams CO2 / Joule

Grams CO2 used since it matches the Carbon Aware SDK, Joules used since SusQL uses this internally
Default value of 0.00000000011583333 grams Co2/Joule based on eGrid data for USA in 2021. Ref: https://www.epa.gov/energy/greenhouse-gases-equivalencies-calculator-calculations-and-references

provide option to calculate carbon on-the-fly from cli tool (interim verification)

include ongoing storage of carbon emission data in parallel with energy storage

Tracking in labelgroup as "totalgco2" to match Carbon Aware SDK units.

update any tools, etc to correctly handle/display this new carbon data

(And undo "on-the-fly" interim calculation?)

[ ] Phase 2 - Ongoing conversion from single provider (AKA "Wading deeper")
Goal: demonstrate that SusQL can easily use current regional carbon intensity data.

Allow user defined location specification at operator level (ideally config map) (No longer labelgroup level)

Attempt to gather ongoing energy-conversion factor from free carbon data provider.

Only gather conversion periodically. Perhaps hourly? Make tunable.

Use this to perform ongoing storage of carbon emission data.

Correctly store data in Prometheus as is done with with TotalEnergy data.

Define and document priorities. e.g., user can choose between phase1 and phase2 carbon calculation

[ ] Phase 3 - Full carbon-aware-sdk utilization (AKA "Dive in all the way")
Goal: demonstrate integration with industry standard carbon aware toolkit

Allow user customization of carbon data subscription provider

Gather data from carbon-aware-sdk rather than directly from provider

Ensure full operator level customization and integration.

Slightly separate point. The SusQL operator does need a better operator level configuration mechanism.
Two possible contenders include configmap and an additional CRD....

Phase 1 works! suqltop shows totalCarbon data from labelgroup. Likewise when operator is deployed from operatorhub.io data can be graphed in the Observe->metric tab by searching for susql_total_carbon_dioxide_grams.

Phase 2 is looking good! susqltop and the Observe->Metric tab provide CO2 information, and the carbon intensity is updated periodically according to the ConfigMap parameters! Reviewing the program logic to be sure I didn't leave something out.

Phase 3 works!!!!!

Complete! Marking finished!


Fix duplicate sub-path for avatars

Fix #31361, and add tests
And this PR introduces an undocumented & debug-purpose-only config option: USE_SUB_URL_PATH. It does nothing for end users, it only helps the development of sub-path related problems.
And also fix #31366
Co-authored-by: @ExplodingDragon

It's not clear to me what USE_SUB_URL_PATH based on the app.ini description. Even if it is a dev-only option, it needs a proper description what it does.

It's not clear to me what USE_SUB_URL_PATH based on the app.ini description. Even if it is a dev-only option, it needs a proper description what it does. "For development purpose only." is not a description.

It has been documented in the source code, if a developer really needs it.

Also, I recommend adding a development section to app.ini, e.g. dev.USE_SUB_URL_PATH. Properly describe it there and also add it to config cheat sheet which should be a exact mirror of all app.ini settings.

Also, I recommend adding a development section to app.ini, e.g. dev.USE_SUB_URL_PATH. Properly describe it there and also add it to config cheat sheet which should be a exact mirror of all app.ini settings.

This option does belongs to [server] and is related to ROOT_URL, so putting them together is fine.
And it is not publicly documented, so we always have the change to rename/move it in the future

Is my understanding correct that this option routes single level sub-path /foo to / even when gitea is not configured for sub-path routing?
Why even have it at all? Can't developers just configure a sub path using the documented options?

Is my understanding correct that this option routes single level sub-path /foo to / even when gitea is not configured for sub-path routing?

Gitea was never able to do sub-path routing, it was never able to handle sub-path

Why even have it at all? Can't developers just configure a sub path using the documented options?

Then you need to setup a separate reverse proxy like nginx.


netbird: 0.8.10 -> 0.8.11

Description of changes
https://github.com/netbirdio/netbird/releases/tag/v0.8.11
https://github.com/netbirdio/netbird/compare/v0.8.10...v0.8.11

Things done

Built on platform(s)

[X] x86_64-linux
[X] aarch64-linux
[X] x86_64-darwin
[X] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[X] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[X] Tested basic functionality of all binary files (usually in ./result/bin/)
22.11 Release Notes (or backporting 22.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[X] Fits CONTRIBUTING.md.

@ofborg build netbird netbird-ui


"No timeline information was provided." for git history

Issue Type: Bug
Normally, viewing a file tracked in git in the editor would fill the timeline with the git history of this file. I'm pretty sure it worked on my system at some point, but now whatever git-tracked file I open, I never get the timeline.
EDIT: it happens to work for some git repositories, i.e. if I just initialize one with simple text files.
EDIT2: now I managed to make it work for the problematic repositories by moving them in my home directory.
EDIT3: now it works for the original copies of the problematic repositories... not sure if we should keep the issue open, since it was still an odd behavior that someone else might encounter?
VS Code version: Code - OSS 1.45.1 (5763d909d5f12fe19f215cbfdd29a91c0fa9208a, 2020-05-17T22:31:53.325Z)
OS version: Linux x64 5.6.11-arch1-1

System Info

Item
Value

CPUs
Intel(R) Core(TM) i5-5300U CPU @ 2.30GHz (4 x 2712)

GPU Status
2d_canvas: enabledflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onoop_rasterization: disabled_offprotected_video_decode: unavailable_offrasterization: disabled_softwareskia_renderer: disabled_off_okvideo_decode: unavailable_offviz_display_compositor: enabled_onviz_hit_test_surface_layer: disabled_off_okwebgl: enabledwebgl2: enabled

Load (avg)
1, 1, 1

Memory (System)
7.64GB (1.35GB free)

Process Argv
--no-sandbox

Screen Reader
no

VM
0%

DESKTOP_SESSION
undefined

XDG_CURRENT_DESKTOP
undefined

XDG_SESSION_DESKTOP
undefined

XDG_SESSION_TYPE
tty

Extensions: none

Ok I think I found the issue: when I open the folder using a path containing symlinks, I don't get the timeline, but I do if the path is free of symlinks. I was able to reproduce this with a fresh git repo, e.g.:
mkdir test
ln -s test link_to_test
cd test
git init .
touch foo
git add foo
git commit -am "Init"
echo "bar" > foo
git commit -am "Foo bar"

Then launching command File: Open Folder... on test I get the timeline, but not on link_to_test.

I'm having the same issue with Timeline - can confirm that it's somehow related to symlinks.

It self-fixed, then again stopped working - the same folders with symlinks. VS Code 1.49.1 and 1.49.2.

BTW GitLens works fine - everything is shown. But VS Code Timeline is empty

The same issue with the latest 1.51.0 update on Win 10 x64 1909.

Some update:
When I open Source Control -> Changes -> Click on changed file -> Diff File is Opened (Working Tree) and then Timeline starts to work - I see all my previous commits.
Repo is local with symbolic links in path
Git 2.29.1.windows.1
VS Code 1.51.0
Win 10 x64 1909

I see the same issue. Opening the workspace by browsing from the root works fine, but if I follow a symlink from my home dir then I see no timeline. I think that fairly conclusively points to symlinks being the cause somehow.

Same issue.
doing what @mrdc  recommended makes it work.

Same issue on some files, but not all

Still getting intermittent issues with VS Code v1.72.2.  It's difficult to find a pattern on why it works with some files over others.

После добавления символических ссылок(linux) в домашнюю папку для удобства, шкала отказалась работать

Indeed, it seems to be that it can't cope with symlinks. As reported by @Champitoad, if I re-open my workspace with the canonical path to it (which is quite inconvenient), I get the timeline information.

Since the issue was last updated, we have added support for git repositories that have a symbolic link on their path. I will go ahead and optimistically close this issue, but in case you are still able to reproduce this with the latest version of VS Code please reopen the issue. Thanks!


[CERT-TEST-FAILURE] Test_TC_ACL_2_3 implicitely requires chip chunked array writes

Feature Area
Other
Test Case
Test_TC_ACL_2_3
Reproduction steps
Formally the last successful write is in "step 9" of the test ... but Step 18 expects another value.
It seems Step 18 expects the "first of the second entries" from step 17 ... which gave an ConstraintError because tried to write 2 entries while only one is allowed.
I assume that this is because of the chunked write handling added in https://github.com/project-chip/connectedhomeip/blob/master/src/app/clusters/access-control-server/access-control-server.cpp#L353 which is very chip specific because formally there is no requiremenst that I know that any array needs to be transported in a chunked way ... and also not that writes needs to be handled chunked at all.
In fat it is really unexpected in case of acl (and especially in case of ACL where consistence should be the most important topic) that a write command like in step 17 returns an error, BUT had an effect by writing the first of the two chunked parts ...
It would be great to get some background information for this, thank you!
In general the test will also have issues as soon as a controller implementation is not sending the list "always chunked" as chip does, because the logic in the access-control-server.cpp would return an Constraint error without saving any value when it is >1 entry in the array. So this behavior is not consistent.
Bug prevalence
always
GitHub hash of the SDK that was being used
master
Platform
core
Anything else?
PS: matter.js would be such an controller which is not automatically chunks every value. We try to get the array unchunked into the data report and only if this does not fit we fallback to chunk the array.

@mlepage-google @hasty

Ok the more I look into it the more it becomes clear to me that the expectation with chunked writes is to really process them also in their chunks one by one. Matter.js is currently not doing this that way. I can change that.
With this the question (that is unanswered for me also after consulting specs - or I am too blind) I added above is the one left: If on one chunk an error happens are more chunks for the same path also processed or not? I assume yes. In fact the result would be then one response per chunk, e.g. one ok, one error and one ok ... and it is up to the caller to decide whats now up ;-) Correct?
Thank you for your support.

Another follow up question: how exactly data version protected writes work with chinked writes? On acl cluster the specs tell the administrator to ideally protect writes with data version filters. So… when each chunked part is handled as own write then dataversion changes after each. So after first write that will change unless the controller makes assumptions on how be re ion increases. Is that also correct? So data version protected writes should never be chunked ?!

Hello Appollon.
Some clarifications...
First, the extension attribute is optional and if present, must be of length 1. That is where there is a constraint error when attempting to write a second element to that list.
The ACL attribute is mandatory, and must support at least 3 entries per fabric. Therefore, writing 3 entries will never result in a constraint error due to exhausting list length; writing 4 or more entries might (depending on actual supported length) result in such errors, but they would always be at the end, and never have a successful entry after exhausting the supported length.
An ACL entry may fail other data validity checks, and fail to write for that reason.
In the SDK, when a list is written (say with 3 elements), it is done as follows:

List cleared via list replace (with empty list) action.
First element added via list item append action.
Second element added via list item append action.
Third element added via list item append action.

In that case, if the second item resulted in a failure (e.g. due to invalid item data), the list would still be of length 1 after having attempted to append the second item. Processing would continue, and the third item would be appended, resulting in a list of length 2. It is as if only the two valid items were sent, except that a write error occurred for the second item.

All right. Thank you for confirmation. In fact this is then also no testing issue and could be closed or moved.
Nevertheless the specification lack details on chunked write operations and how this should work. It was completely unclear to me till now.
In my eyes this behavior is maximum inconsistent because if I send an unchunked array with the 3 items where second is invalid then nothing is written and the constraint error happens for all three. But unassigned that this ship has sailed ;-)
Would you also have an info how chunked writes work with dataversion check on the write? (Also because acl specs propose to use that). In my understanding each processed chunk increase the version so the data version check only works for the first chunk.
I know that chip always send array full and so resets the array with the first chunk but the protocol does not dictate that. So someone could really just add items to an existing list. ;-)

Ps: (and slightly off topic) is there a reason why Chip always chunks the data in data reports and writes? If the array would fit into the data report then sending it unchanged would need less bytes then always chunked.
Would that not be important for low power devices?
But yes then the test here would get issues because they could behave differently ;-))

Re your infos on dataversion: ok thank you for the reference. Puuhh that makes things interesting.
So we have kind of a „transaction“ (summarize multiple changes and „commit“ at the end to increase version) but without having a real „transaction“ (aka rollback everything in case of an error). Good. Will be fun to implement that. ;-)

When I think deeper then I also ask myself why the spec 1.3 in "<IP_ADDRESS>.1. Lists" just tals about "full list" or "clear the list and send appends" ... Combined with a dataVersion security approach it should be easiely possible to just send list modifications. Also the spec examples kind of contain all these examples, just the spec tells is "SHOULD" not be done ...
This should be even less bytes needed and should be (because of the dataVersion security guard) end in the same final list ... or?! But yes thats more "spec and protocol feedback" and I have no idea if chip has implemented that ... I assume not becuse eg acl just handled additions beside "full array" and last time I checked in the c++ code I only saw places that handle these two cases, nothing else... Sorry to place it here, but I have no other ways to bring such thoughts/questions to any attention ;-)

… as example in acl code is there for both options but the „full array“ code path should always ever be executed with zero or one element …

In access-control-server.cpp for writing the Extension attribute with an entire list, it only ever handles a list of length 0 or 1 because that attribute list can only ever be length 0 or 1.
https://github.com/project-chip/connectedhomeip/blob/22b9c96b691d3bb5a5d3db510db353b3b2bc2f74/src/app/clusters/access-control-server/access-control-server.cpp#L350
For the ACL attribute, the length of the list being written is not assumed.
https://github.com/project-chip/connectedhomeip/blob/22b9c96b691d3bb5a5d3db510db353b3b2bc2f74/src/app/clusters/access-control-server/access-control-server.cpp#L252

I did most adjustments needed and are currently finalizing all the tests but I need to tell you that the tests here (especially ACE 2_5, 2_6 and such) are veeery chip implementation specific. I now need to mimic the event order based on the code how chip is managing the entries in the relevant cases and send out events. Also the events have the "latestValue" which is not really described in the specs, but in the end is a different value depending on if it is a Removal or other action. All this is nowhere mentioned in the specification. In the end thats all valid and ok to require it, but if such things like the exact event behaviour, orders and such are checked in certification in this depth then also the specification should contain these implementation details as requirements. Thats at least my opinion :-)
In fact I spent at least 4-8h today to just run tests, analyze why it broke, adjust code, and do this in loops ;) Same for the specific write request handling for "splitted/chunked list processing". The specification (at least not clear to me) is not containing all the details whats requitred and tested. I think all details in specification would have saved me a lot of this time.
Please see this as feedback from a developer that implements the protocol mainly after specs (as it should work out).

In addition to above I also see a spec issue here ...
Spec tells in 6.6.4. Access Control Cluster update side-effects

Updates to the Access Control Cluster SHALL take immediate effect in the Access Control system.

and then having the example of "1. Action: Write (1st path)" ... but with chunked writing the first write path action is the complete reset of the array to be empty! so the first real value gets added in the second Write action. So if this would become effective really directly then all other acl actions will indeed fail because the acl list is empty.
So it would be great to know how this should be really handled with all chunked writes. Does ACL list changes really become effective directly, but "ignoring" the initial write action to clear the list? Or is the new entry just effective after all writes are done? In both cases specification would require an update in my pov.
Also in general this "proceed the writes entries one by one" also could have effects in e.g. bindings or groups. In both cases lists are used to handle things. If we also here clear the lists and then "write one by one with immediately becoming effective" means that if I have 5 groups/bindings and I add a sixths then the first write clears the list and then the first entry gets added and formally all others removed. if this becomes effective directly too that would mean we stop listening to all these groups or disconnect from all bound devices except the first and then we rebuild all these connections and listening sockets again newly and add one more. or am I wrong or miss a point?

Ok, I verified one of the things by experimenting with chip:
It seems to me that a "write to the acl attribute" is processed completely in the write message and becomes effective then. This is the reason that clearing the array as first write path action or adding acl entries in strange order is now screwing up the whole acl system. So with this assumption is that chunked list writes are processed as a sequence in chip until the "write path" (regarding endpoint/cluster/attribute) changes and are then being updated in the acl system. At least so it seems to me.

@Apollon77 can we close this issue ?

In my eyes not tbh. Because we were in the middle of a certification we now adjusted matter.js to process list writes the exact same way as chip does by never writing the full list but always "chunking" it. If I would change this back to the original way to write the full list at once then by the defined logic of the "how events are needed to be sent defined by spec" we would have different events triggered.
Example:

currently: the first event is always an update of the first element, followed by delete events (in backwards order which is also nowhere defined in the specs, but implemented that way by chip) for all other former list entries, then it generates more add-events.
with a read full list write there would be update events for all "overlapping" list indices and then add or delete events for the rest depending on if the new list is longer then the old list

As you can see, based on the event logic defined by spec these two "way to process lists" is different and will cause a different order of events by nature as soon as the list is longer then 1 entry. Additionally the fact that add/update cases are processed in ascending order, but delete cases are process in descending order is undefined by the specs, so also the order of delete events itself would be undefined, but the yaml tests are explicitly requiring them to be in "the" order that chip implements.
So yes - because of several "workarounds" and "codeflow like chip" in matter.js - it is formally no cert blocker for matter.js devices, but mainly because we did not wanted to have this discussing within the certification process. But as soon as another implementation implements the same (e.g rust) the same issue could arise again.
Meaning, in my eyes, if the current behavior and tests should stay as is, this would require some spec adjustments to define the chip behavior as "the one". In my eyes this would not be the best idea tbh ...
So other options would be to adjust the tests in a way that relaxes the checks in a way that things work or are ok.
Basically this topic also touches the whole topic that chip choose to send "lists always chunked" also if they would match into one message ...

Ok, I thought a bit on how we could ideally discuss this with a chance to come to solutions and not to run in circles ;-)
In my eyes the very first topic is: If there is an agreement on the fact that normal list write interaction are always done chunked as chip sdk is sending them currently and this stays that way forever that would simplify a lot. So that would be the very first topic to discuss.

if there is an agreement then this should be simply added to the spec as a "SHALL" requirement and 80% of the topic is solved basically. And formally that's just an "editorial" because noone was able to certify a device without this behaviour because else the above mentioned ACL tests would all have failed. When this is decided it would also be a great idea to reflect this in chip code and just support this case and error if someone sends something different to be clear here.
if this is no agreement then we have a funny discussion :-)

When the above topic is agreed only one main topic is left: order of delete events in the ACL case which relies on the sdk implementation where deletions are processed from the highest list index down to 0. If this is the way to go for ACL, define it in the specs and we are also done here. Or we should think about how we could enhance the yaml tests to just verify event existence and not the order :-)
(side note: the acl yaml tests rely on the fact that the latest acl events are still readable ... which (as I understood) might not be the case, so also test could fail if too many events are generated, but thats other topic)


Decompiler:  do not read offsets inline from void pointer

Is your feature request related to a problem? Please describe.
I have a struct with a field that is an opaque pointer (and have also tested with a union pointer).  Typically in an if/else or switch, but sometimes just read directly (specific handler func), that field will be read, the decompiler will then sometimes also read a field offset out of that void pointer for read or write operations.  There is no intermediate pointer variable generated for type information.
Describe the solution you'd like
If an offset is read from a void pointer from a struct, it be assigned to a variable first, allowing for that variable to be typed.  The offset/field read then takes place from the intermediate variable instead of a chain in the original struct
I may not be considering type conflicts with larger functions or issues non-stack based variables, but wondering about something like this happening vs what might be easier to handler:
struct foo *x = getfoo();
if (*(undefined4 *)&x->opaquedata + 0x90)) {
   // do something
}

struct foo *x = getfoo();
void *data = x->opaquedata; // this data could then get typed manually
if (*(undefined4 *)&data + 0x90)) {
   // do something
}

Describe alternatives you've considered
None, I don't see a current work around.
** Additonal **
This may just be the generic union issue in general since they may be treated the same way.... @caheckman (@ryanmkurtz ) could you just mark dup /close , unless you think this is another case to be handled

Isn't this just a situation where opaquedata is a pointer to another structure (or union of structures) containing at least 0x90 + sizeof(pointer) bytes that you could create and assign to the definition of opaquedata?

Not quite sure what is going on here. The example seems incomplete, as the parentheses in the "if" condition are unbalanced. What is the type of the field "opaquedata"? If it is a "void *", does it not work to redefine it as a union of pointers?

Wasn't able to repro on master, not sure if i had something weird going on (I started the image new for master) or 10.1.3 related


With Dump.Tables set to a single table, canal is still listening to all tables.

The canal package is not respecting dumping config.
I set cfg.Dump.Tables = []string{"user"}, but my handler is still being called when other tables are updated.

what is your whole configuration for dumper?
do you pass multi databases?

	cfg := canal.NewDefaultConfig()
	cfg.Addr = "localhost:3306"
	cfg.User = "root"
	cfg.Password = "root"
	cfg.Dump.TableDB = "user"
	cfg.Dump.Tables = []string{"user"}

	c, err := canal.NewCanal(cfg)

@siddontang That's everything.

but my handler is still being called when other tables are updated.

The config is only for mysqldump, not for mysql binlog.
The mysql binlog will sync all the changes.


chore: Add cocoapods publishing automation

For this to work on the next release, you'll need to add COCOAPODS_TRUNK_TOKEN to the repo secrets


Provide a default grant description

In #2967 is was suggested for providing a default description. It doesn't look like this was implemented. I think there is a lot of value in doing this.  Second, providing a default descriptive name is obviously useful.
Is there a way to do this without a lot of heavy lifting currently? And for the future, providing an easier mechanism for this that would also inject the context to get things like client description as well as the user context would be super helpful.

I don't follow what a default description would be. A description is not required.

Imagine a scenario where we provide a UI to revoke a login.
I have a client specifically for Zapier connections to my API. So when creating that connection and consenting, I could provide a default description like "Zapier (brockallen)" that would already be filled out which results in a clean user experience on both ends.
I hope that clarifies a little bit.

Ok, sure... then your UI for the consent page can do that. That's why the quickstart UI is provided -- for you to make any of those kinds of modifications/customizations. Our quickstart UI is not sacrosanct.

Sure I know I can rip that apart and that's all fine. Was looking for feedback I suppose on if you thought this was a good idea or worth exploring. Other instances include non visual instances where grabbing the user agent would be nice, etc... I think a service to inject that can supply this would be useful but maybe I'm over complicating it :)

Yea, we're a framework and provide building blocks to do with as you see fit. I don't see many people actually using description, to be honest, but it's something that might be useful for some scenarios.

Maybe I'll try a PR on it. I think you're underestimating its value though ;) Maybe I'm wrong.


Algo Linear Search in JavaScript

@Abishethvarman Can you assign this issue to me? I want to work on this!

ok, carry on @pranav-kale-01

@Abishethvarman Linear Search is already implemented. Can you please close this issue?

@Abishethvarman Linear Search is already implemented. Can you please close this issue?

try something else


Hide selected option id in multiple select

Hi,
When the user uses the multiple autocomplete, and selects an option, a chip of this option is created. Is there any way to hide the id that is being show along with the name of option?
Thanks

You can set the appender.tagTemplate option with template string by modifying the default value.
e.g.
'<div class="chip" data-id="<%= item.id %>" data-text="<%= item.text %>"><%= item.text %>close
'

thank you


Readme.md has old links. Documentation has old links.

Readme.md has old links. Documentation has old links.
Nice work recently!

Are you referring to the sample reports?


Minimal change to allow "in" parameters for operators

Fixes #835.
I don't believe any grammar changes are required - the operator grammar uses fixed_parameter which already permits modifiers, so it's down to the operator text to reject the others (which it does).

I'll merge as-is, but create an issue for a note to be added post C# 7. At this point I'm trying to stick to the bare minimum for correctness in order to get C# 7 out :)


Make elements independent of each other

I'm combining Draggable and ResizableBox together to make a layout where you can freely drag and resize images.
My problem is that whenever I add a 2nd image it always start under the first one and if I want to set the top bound to 0, this means that the 2nd image can never go further up than the bottom of the first component.
In addition, if I resize the first image it will affect the y position of the 2nd one.
Is there a prop I'm missing or some styling that can make them fully independent of each others position?

 They should then all start at the same position, then you can use Draggable to set their initial position relative to the same 0,0.

Thank you, worked perfectly!


chore(maintain): Integrate Coveralls

What does this PR do?

This PR displays  coverage badge into the Readme file of the project

Description of Task to be completed?

Integrates coveralls, gets test result from travis and displayed badges on readme

How should this be manually tested?

npm run coveralls

Any background context you want to provide?
Travis CI finally builds without errors and the badge is displayed on the readme file.  The link to the badge in the readme file was changed from pointing to my branch name to the staging branch.
Therefore the badge wouldn't display on 'Chore/146622687/coveralls-build-displays-readme' branch because the badge is pointing to the 'staging' branch which has errors on travis build - this PR would fix it.
What are the relevant pivotal tracker stories?

#146622687

Questions:

None

Changes Unknown when pulling 195c506ceb622fac0c7976c22c2f543d63205801 on chore/146622687/coveralls-build-displays-readme into ** on staging**.


Create img

Hi @julinomio ,
It looks like you accidentally submitted this PR against the upstream template repo instead of your own fork: https://github.com/julinomio/pythontst
Regards,
Stennie


VS editor won't load JSON file >5 MB, so SARIF results don't load

The JSON editor doesn't like files > 5MB and won't load them. As a result, we won't show results in those files.
SARIF files can be very large due to things like embedded file content. If the file is too large, we should not try to load the file (or catch the exception so we can continue processing) but should try to process the SARIF by loading all results in the error list.

@eddynaka, this one is high priority.


Emissary Barrett is white

If the Emissary is Barrett from another universe while meeting him and the Hunter before going to the temple, when the Emissary reveals his face, he's light-skinned.

Details
Not sure if this is a bug because perhaps Barrett is not black in most universes?
Game Version
<IP_ADDRESS>
Language
English (EN)
New Game
Yes
Reproduction Steps

Be playing the main story
have Barrett be killed by the Hunter
meet the emissary and the hunter and proceed through the dialogue on the Hunter's ship

This actually affects them all. If Andreja is the Emissary, her skin tone and tints are not applied correctly. It's the same thing that sometimes happens to Unity you, when scars, makeup, etc are not applied as they should be. I believe this may be an engine level bug with the copy appearance function that is used to replicate the appearance of NPCs.

I have never experienced this myself, but Bethesda has fixed some issues relating to this in official updates. Closing this one, will work off of a new report if the issue can still be replicated.


Correct metric names

com.dynatrace.extension.active-directory.server.host.cpu.time.* metrics - replace processor with CPU, both in description and displayName
fix typos in * reponse * metrics (missing 's')

outdated


Readme doesn't have enough detail to get started

It took me a while to get up and running with J-Bob using the Dracula package. In particular:

I didn't realize that I had to install ACL2 separately.
I couldn't get J-Bob to load by typing commands in the REPL.

When trying to use the "include-book" command in the Dr. Racket REPL, I'd get an error:
> (include-book "j-bob-lang" :dir :teachpacks)
 Library/Racket/6.10.1/pkgs/dracula/lang/do-check.rkt:92:34: rename-below: defined outside of begin-below in: here

Eventually, I figured out how to do it, and I even wrote up a blog post. I recommend adding more detail to the README to make it easier on new users. I'm happy to submit a PR updating the README with the additional details.

Totally agree that getting j-bob installed could be made much easier with better instructions.
@lorin Thanks for posting here and your blog post it really helped me get going.  One small thing that tripped me up with your instructions was finding the binary downloads on the ACL2 site.
For future travellers, I downloaded the binaries from here: http://acl2s.ccs.neu.edu/acl2s/src/acl2/

This seemed to work for me (not using drracket):
raco pkg install dracula
#lang dracula
(include-book "j-bob-lang" :dir :teachpacks)
(include-book "j-bob" :dir :teachpacks)

;;first example using J-Bob
(J-bob/step (prelude)
    '(car (cons 'ham '(cheese)))
    '((() (car/cons 'ham '(cheese)))))


Add account sits in Saving.... if you rename after getting "not unique" error

Rancher Version:
v1.0.1
Docker Version:
1.10.3
OS and where are the hosts located? (cloud, bare metal, etc):
centos7.2
Setup Details: (single node rancher vs. HA rancher, internal DB vs. external DB)
single node rancher
Environment Type: (Cattle/Kubernetes/Swarm/Mesos)
Cattle
Steps to Reproduce:

enabled local Authentication
add an new account called "test".
add another account called "test" too ,and it will fail for "publicValue is not unique";
Then change "Login Username" to a name which is unique, e.g."test123". Click "Save"
Wait a few seconds, UI shows a Warning icon without any message. Click “Cancel" to return to upper menu.

Results:
Account "test123" created.
Expected:

Verified that this is an issue in v1.1.0-dev2-rc4.
It looks as if the account is being created in the backend because if I click on cancel, the account is created. But for some reason the UI isn't exiting back to the account screen.

Version - master 11/10
Verified fixed


[flutter admod] FutureBuilder is constantly renovating

FutureBuilder is constantly renovating
just getting iphone

@hsnbsst Can you explain in more details what is the issue exactly? May be to provide you flutter doctor -v output, admob version, some code to reproduce the issue.

Without additional information, we are unfortunately not sure how to resolve this issue. We are therefore reluctantly going to close this bug for now. Please don't hesitate to comment on the bug if you have any more information for us; we will reopen it right away!
Thanks for your contribution.
Could everyone who still has this problem please file a new issue with the exact descriptions what happens, logs and the output of 'flutter doctor -v'  please.
All system setups can be slightly different so its always better to open new issues and reference related issues.


Linking error on compile

When I try to build godot (8698876) on Windows 10 x64, I get this error:
[ 97%] Linking Static Library ==> modules\freetype\freetype_builtin.windows.tools.64.lib
[ 97%] Linking Program        ==> bin\godot.windows.tools.64.exe
LINK : fatal error LNK1181: cannot open input file 'fmod64_vc.windows.tools.64.lib'
scons: *** [bin\godot.windows.tools.64.exe] Error 1181
scons: building terminated because of errors.
I have tried both x86 and x64, multithreaded on/off, same error. I have tried both Windows and Windows 10 UWP api files for fmod.
>python --version
Python 3.7.2
>scons --version
        script: v<IP_ADDRESS>a41ed6b288cee8d085373ad7fa02894e1903864, 2019-01-20 22:51:36
        engine: v<IP_ADDRESS>a41ed6b288cee8d085373ad7fa02894e1903864, 2019-01-20 22:51:36

Same issue here.

I should say I'm using python2.7

Found this while googling, https://github.com/godotengine/godot-docs/issues/2099. Looks like it might be an issue with scons.

This is an issue with Scons that only applies to the Visual Studio compiler. An easy but hacky workaround is to simply rename your library file from 'fmod64' to fmod64_vc.windows.tools.64.lib'


[OSX 10.11.2] Uncaught exception - std@module_read

I got this:
Uncaught exception - std@module_read
when trying to run my neko program using openfl / lime test neko on my mac osx 10.11.2
Haxe 3.2.1
NekoVM 2.1.0

This is a Neko size limit thing.
<haxedef name="no-inline" if="neko"/>
<haxedef name="dce=full" if="neko"/>

should fix it.

got this when using dce=full
Called from ru.stablex.ui.widgets.Widget::set_top line 767
Called from openfl.display.DisplayObject::set_y line 1457
Uncaught exception - Invalid field access : ty

I can't really respond to this, unless you can share your code. Invalid field access usually means you haven't initialized the object.

This error is being caused by dead-code elimination ("dce"), which is removing a field it thinks your project is not using. DCE reduces the size of your project, but may not be enough to make it small enough for Neko 2.0, Neko 2.1 has fixed this by increasing the maximum size of a Neko project, in Lime, we use an inbetween development build of Neko 2.0 that had this patched, but I think this might not have been patched for Mac
We need to integrate Neko 2.1 in our Lime tools binaries, and sort any differences on our end to support the newer version. This will fix the issue for Mac, in the meantime, I would recommend using openfl test mac instead of Neko for this project until we update

thanks for the clarification. Hope this get sorted out soon, it's taking a long time to compile each time I want to test my game using "openfl test mac".

A new version of Neko was released, which raises the maximum application size limit -- we don't have this included in Lime yet, but this would be the best way to fix this