text:
Problem Parsing header

I have problem trying to publish a .ply file generated with lsd_slam. I am able to open the .ply file with meshlab. But when I try to publish the .ply file, I get the following error,
[pcl::PLYReader] ~/catkin_ws/src/lsd-slam/src/lsd_slam/lsd_slam_viewer/pc.ply:1: parse error
[pcl::PLYReader::read] problem parsing header!
[pcl::PLYReader::read] problem parsing header!

This is typically a problem with the formatting of the .ply file. Can you check your .ply file in a text editor and compare it for example to this example file?

I opened the .ply file in meshlab, then exported it. On using the .ply file exported from meshlab, I was able to publish the pointcloud and visualize in RViz.
The actual header of ply before opening in meshlab was,
ply
format binary_little_endian 1.0
element vertex 3044442
property float x
property float y
property float z
property float intensity
end header
and, after exporting from meshlab it became
ply
format binary_little_endien 1.0
comment VCGLIB generated
element vertex 814340
property float x
property float y
property float z
property uchar red
property uchar green
property uchar blue
property uchar alpha
element face 0
property list uchar int vertex_indices
end_header
The intensity has been removed. Is it possible to have ply published with intensity? Is it not essential to preserve intensity in pointcloud data? I am trying to use monocular camera with lsd_slam to create a map for path planning.
The entire pointcloud is completely visible in RED even from the start though the /point_cloud topic is being published for a time. I found a video where they port the pointcloud into RViz, which looks colorful, (https://www.youtube.com/watch?v=CUU3L6_wLXE). Is it because intensity data is removed out of pointcloud?

Could you try to change the line 95 of Read.cpp to the format that you need?
PointCloud<PointXYZRGBNormal> pointCloud;

Hello guys i am having the same problem , how did you fix it? i could not find your Read.cpp file anywhere
Regards

I had a similar issue, when opening a ply-file from a VO software I would get the following errors:
[pcl::PLYReader] /home/ubuntu/mtdata/rtabOutput/rtabmapviz_exportcloud.ply:29: property 'float32 scalex' of element 'camera' is not handled
[pcl::PLYReader] /home/ubuntu/mtdata/rtabOutput/rtabmapviz_exportcloud.ply:30: property 'float32 scaley' of element 'camera' is not handled
[pcl::PLYReader] /home/ubuntu/mtdata/rtabOutput/rtabmapviz_exportcloud.ply:31: property 'float32 centerx' of element 'camera' is not handled
[pcl::PLYReader] /home/ubuntu/mtdata/rtabOutput/rtabmapviz_exportcloud.ply:32: property 'float32 centery' of element 'camera' is not handled
[pcl::PLYReader] /home/ubuntu/mtdata/rtabOutput/rtabmapviz_exportcloud.ply:35: property 'float32 k1' of element 'camera' is not handled
[pcl::PLYReader] /home/ubuntu/mtdata/rtabOutput/rtabmapviz_exportcloud.ply:36: property 'float32 k2' of element 'camera' is not handled

Additionally, no cloud would be visible in Rviz even though rostopic hz showed that the pointcloud was published.
My issue was solved as indicated above by @boonflies  by importing the point cloud into Meshlab, and exporting it again to a .ply file. Using the newly exported file for the publisher, no unhandled properties would be shown, and the point cloud appear in Rviz.

Hey guys,
I just saw this issue and want to add an idea, why this message is triggered by pcl: The .ply file which will be loaded may not contain a line feed at the end of the file. In my case the removal of that empty line fixed the problem.
Regards

One issue can be that the file contains NaN or Inf values. Make sure you delete the corresponding points or replace these value before loading. https://github.com/PointCloudLibrary/pcl/issues/1433

This also doesn't work in CloudCompare unless you remove the camera calibration parameters. The NaNs are fine, they just get ignored.

authors: Gregoriomartjim boonflies heimsi jovobe jveitchmichaelis pfankhauser remod


text:
Large-Scale Refactoring

The modules need to be refactored into the following structure

Media

Articles (rename to News)
Wiki

Guild

Chat (forthcoming)
Characters

Sessions

Contracts
Episodes

Configuration

Backgrounds
Professions
Races
Feats
Items
Spells (forthcoming)

The only one I'm not certain about is Guild. I want to also be able to include Shops, and I have no idea where that will go...

Maybe include a 'World' directory, which could contain shops, maps, cities, or something similar?

That's a good idea. I was trying to figure out how best to do that.

Would the World directory also contain NPCs?

Here's a better idea, IMO.
World
├── News
├── Wiki
├── NPCs
├── Cities (includes Maps, possible also includes ability to travel e.g. take an airship to Luïnden)
└── Shops

Guild
├── Characters
├── Episodes
└── Conversations
```

Hm.
I like Media being grouped with World, because then world-specific items all go in one place (unless characters only exist in a world?).  Would make it easier later on for other people if you're planning to release this tool for any DM :)
If it's not typical to include characters as intrinsically linked to a certain 'World', I think structure 1 is fine, because then World-Specifics are all together.
Otherwise, I think option 2 is better because then that illusion isn't being improperly maintained.

source: gharchive/issue

authors: Tyroche etkirsch

repo: etkirsch/tolmea

license: mit

license_type: permissive

license_source: bigquery


text:
Added translations for confirm password error state

Fixes # BLUI-3944

Changes proposed in this Pull Request:

Added translations for confirm password error state
Updated package version
Updated changelog

Screenshots / Screen Recording (if applicable)

To Test:

Any specific feedback you are looking for?

Please open https://github.com/etn-ccis/blui-react-workflows/pull/237 once this gets merged

I see that we already have this:
https://github.com/etn-ccis/blui-react-auth-shared/blob/e8d29ca51f882c2b41306086c2ffcfd91f58c3f1/src/data/translations/english.ts#L112
and you added this
https://github.com/etn-ccis/blui-react-auth-shared/blob/e8d29ca51f882c2b41306086c2ffcfd91f58c3f1/src/data/translations/english.ts#L163
Are you able to either
(1) reuse what's already there, or if that is not possible
(2) make the verbiage match?

I see that we already have this:
https://github.com/etn-ccis/blui-react-auth-shared/blob/e8d29ca51f882c2b41306086c2ffcfd91f58c3f1/src/data/translations/english.ts#L112
and you added this
https://github.com/etn-ccis/blui-react-auth-shared/blob/e8d29ca51f882c2b41306086c2ffcfd91f58c3f1/src/data/translations/english.ts#L163
Are you able to either
(1) reuse what's already there, or if that is not possible (2) make the verbiage match?

I will reuse the PASS_MATCH_ERROR for this. Closing this PR, as there are no changes needed in shared auth.

source: gharchive/pull-request

authors: huayunh surajeaton

repo: etn-ccis/blui-react-auth-shared

license_source: github-api


text:
Support for millisecond timestamps

Need support for date_field in milliseconds within 411. Able to execute successful searches, but unable to send result to 411 alert index in elasticsearch. Get mapper_parsing_exception and illegal_argument_exception on the alert_date field for Invalid format.

Should be fixed via e4df5965b30c0821a78bd0125c1d774b9a2327da. Define the new date_type attribute in your config file (check config_example.php for details).

Even if the date field in ES does not have a # or @?
I don't see in the changes the date field for the alert index being set to type epoch_millis so I'm confused if it using milliseconds or converting milliseconds to seconds.

Should be all resolved.

authors: kbiedermann kiwiz


text:
List Concat

From Gradualizer suite:
-spec nil_concat_op_elem_gives_elem() -> b.
nil_concat_op_elem_gives_elem() ->
    [] ++ b.

Should pass, but does not. Generated constraints:
[{csubty, 7:11, b, $3},
 {csubty,
  7:8,
  fun((list(a@0 /\ any()), list(a@0 /\ any())) -> list(a@0 /\
                                                       any())),
  fun(($2, $3) -> $4)},
 {csubty, 7:5, [], $2},
 {csubty, 6:1, {}, $0},
 {csubty, 6:1, $0 /\ ({} /\ {}), {}},
 {csubty, 6:1, $0, {} /\ {}},
 {csubty, 6:1, $1, b},
 {csubty, 7:8, $4, $1}]

Semantics of ++ on empty list (Erlang documentation):

The list concatenation operator ++ appends its second argument to its first and returns the resulting list.

2> [] ++ b.
b

Even though lists:append could theoretically produce improper lists, the type specification in the official Erlang documentation prevents this. Closing as works as intended, this should be classified as should fail.

repo: etylizer/etylizer


text:
[FEATURE] Add user friendly API for register events.

Is your feature request related to a problem? Please describe.
There should be a clearly API to allow user register events and init runtime.
Describe the solution you'd like
for example:
// Init runtime
int bpftime_init_runtime(runtime_config* config);
// Register events
int bpftime_register_attach_events(int event_id, event_config* config);
// Handle events
int handle_events(int event_id, struct ecent_ctx* ctx);

We need to discuss how to do that.
Describe alternatives you've considered

Provide usage examples

Additional context

What does event here mean? Attach type?

for example, nginx incoming request is an event, uprobe is an event, syscall tracepoints is an event, dpdk incoming request can be an event
Events can be connected to bpf_prog using bpf_link.

Does that make sense?

for example, nginx incoming request is an event, uprobe is an event, syscall tracepoints is an event, dpdk incoming request can be an event
Events can be connected to bpf_prog using bpf_link.

These were called attach type previously, but we need a full set of callbacks to define an attach type, such ad instantiation at https://github.com/eunomia-bpf/bpftime/blob/a6a132bfe6717a2f41a67ec646b44856d57c5714/runtime/src/attach/bpf_attach_ctx.cpp#L111

repo: eunomia-bpf/bpftime

license: MIT


text:
Doubt about the method lejos.hardware.Key#simulateEvent(int)

Hi,
I am working on an implementation of the ev3dev.sensors.EV3Key class which inherits from implements the mentioned lejos.hardware.Key. I am not quite sure what its simulateEvent(int) method should do and the LeJOS javadoc doesn't contain any description.
I am not even sure what the integer "event" parameter refers to... I guess it may be one of the LEFT, RIGHT, etc. constants but then it's not clear if it should simulate key "press" or "release".
My guess is that it should effectively:

Invoke the registered listeners.
Notify any threads waiting in the #waitForPress() and #waitForPressAndRelease() methods.

Can anyone please shed some light on this for me?
J.

Hi @jartu, it is a good question.
I am not sure too. I reviewed Javadocs and the NXT implementation and this method is new.
http://www.lejos.org/nxt/nxj/api/lejos/nxt/Button.html
http://www.lejos.org/ev3/docs/lejos/hardware/Button.html
http://www.lejos.org/ev3/docs/lejos/hardware/Key.html
In EV3, the implementation is better. Every object is returned an object based on an Interface:
https://github.com/ev3dev-lang-java/lejos-ev3-code-mirror/blob/master/ev3classes/src/lejos/hardware/Button.java
public static final Key ENTER = BrickFinder.getDefault().getKey("Enter");

I found some usages on Github:
https://github.com/lego04/robot/blob/master/robot/src/robot/Main.java
https://github.com/chbe89/mindstormer/blob/master/src/edu/kit/mindstormer/program/implementation/test/MoveFixedDistance.java
https://github.com/chbe89/mindstormer/blob/master/src/edu/kit/mindstormer/program/implementation/test/MoveFixedDistance.java
I suspect that the usage is more for Testing. If the Button in some object is waiting for some event, it is possible to set values to simulate the event. I think that it is interesting the feature but it is better if we fix before this issue:
https://github.com/ev3dev-lang-java/ev3dev-lang-java/issues/298
Currently, we can`t handle the specific event for the any button. In current stable release, we only manage the case of: Button.waitForAnyPress();
https://github.com/ev3dev-lang-java/ev3dev-lang-java/issues/273
package examples.sensors;

import ev3dev.sensors.Button;

public class ButtonExample {

    public static void main(final String[] args){

        System.out.println("Button example");

        Button.waitForAnyPress();

        System.out.println("Button pressed");
    }
}

If could be a good contribution if you are able to run this example:
package examples.sensors;

import ev3dev.sensors.Button;
import lombok.extern.slf4j.Slf4j;

public @Slf4j class ButtonTest2 {

    public static void main(final String[] args){
        log.info("Demo");

        Button.UP.waitForPress();
        log.info("Pressed UP");

        Button.DOWN.waitForPress();
        log.info("Pressed DOWN");

        Button.LEFT.waitForPress();
        log.info("Pressed LEFT");

        Button.RIGHT.waitForPress();
        log.info("Pressed RIGHT");

        Button.ESCAPE.waitForPress();
        log.info("Pressed ESCAPE");

        Button.ENTER.waitForPress();
        log.info("Pressed ENTER");

    }
}

Normally, I search on Github the usages of the community and it is more common the usage of a specific button event than the usage of the new method simulateEvent.
Many thanks @jartu
Juan Antonio

In my case, I execute the programs from an ssh  connection from Intellij, when I have to finish a java process, in my terminal I execute:
pkill java

For EV3, it is perfect. I think that the CPU for an EV3 only is able to run one program at time for BrickPi/PiStorms Bricks, the CPU resources are better so, in general I don´t use the Button to exit manually the programs, I interact the OS to kill the process but you are using some classes from local navigation stack from LeJOS, you know that some methods are non-blocking so the usage of the button is some way to not allow finish the execution in the main thread.
https://github.com/ev3dev-lang-java/lejos-navigation
import ev3dev.sensors.Button;
import ev3dev.sensors.ev3.EV3UltrasonicSensor;
import lejos.hardware.port.SensorPort;
import lejos.robotics.RangeFinderAdapter;
import lejos.robotics.navigation.DifferentialPilot;
import lejos.robotics.objectdetection.Feature;
import lejos.robotics.objectdetection.FeatureDetector;
import lejos.robotics.objectdetection.FeatureListener;
import lejos.robotics.objectdetection.RangeFeatureDetector;

import java.io.IOException;

public class FeatureAvoider2 {

    static final float MAX_DISTANCE = 50f;
    static final int DETECTOR_DELAY = 1000;

    public static void main(String[] args) throws IOException {

        final PilotConfig pilotConf = new PilotConfig();
        final DifferentialPilot pilot = pilotConf.getPilot();

        final EV3UltrasonicSensor ir = new EV3UltrasonicSensor(SensorPort.S1);
        final RangeFeatureDetector detector = new RangeFeatureDetector(
                new RangeFinderAdapter(ir.getDistanceMode()), MAX_DISTANCE, DETECTOR_DELAY);

        detector.enableDetection(true);
        pilot.forward();

        detector.addListener(new FeatureListener() {
            public void featureDetected(Feature feature, FeatureDetector detector) {
                detector.enableDetection(false);
                pilot.travel(-30);
                pilot.rotate(30);
                detector.enableDetection(true);
                pilot.forward();
            }
        });

        Button.waitForAnyPress();
    }
}

OK, I am leaving the #simulateEvent(int) unimplemented because I am still not sure what it should do.
I have submitted a pull request (https://github.com/ev3dev-lang-java/ev3dev-lang-java/pull/357/files) with the EV3Key implementation that solves issue #298. Once this change gets approved I can also change the Button class to use the EV3Key better and I can also write a better version of the https://github.com/ev3dev-lang-java/examples/blob/develop/ev3dev-lang-java/src/main/java/ev3dev/sensors/ButtonExample.java .
Also note: With my implementation, it should not be a problem to call waitFor* from different threads - i.e. the limitation mentioned in the Button class no longer applies.

Hi @jartu,
Tomorrow, I will do a Code Review about the Pull Request and I will test the new features.
Cheers

Test on Brick 1: Passed:
package examples.sensors;

import ev3dev.sensors.Button;

public class ButtonExample {

    public static void main(final String[] args){

        System.out.println("Button example");

        Button.waitForAnyPress();

        System.out.println("Button pressed");
    }
}

Test on Brick 2: Passed
package ev3dev.sensors;

public class ButtonExample2 {

    public static void main(final String[] args){
        System.out.println("Extended Button Example");

        System.out.println("Press UP");
        Button.UP.waitForPress();
        System.out.println("Pressed UP");

        System.out.println("Press DOWN");
        Button.DOWN.waitForPress();
        System.out.println("Pressed DOWN");

        System.out.println("Press LEFT");
        Button.LEFT.waitForPress();
        System.out.println("Pressed LEFT");

        System.out.println("Press RIGHT");
        Button.RIGHT.waitForPress();
        System.out.println("Pressed RIGHT");

        System.out.println("Press ESCAPE");
        Button.ESCAPE.waitForPress();
        System.out.println("Pressed ESCAPE");

        System.out.println("Press ENTER");
        Button.ENTER.waitForPress();
        System.out.println("Pressed ENTER");

    }
}

Unit tests: Passed
@jartu, I liked so much your tests. I am working on this issue to improve the coverage of the whole project:
https://github.com/ev3dev-lang-java/ev3dev-lang-java/issues/209
I think that Unit Testing for Robotics projects is good in general.

In relation to your original question, the method: simulateEvent is not relevant in the functionality of the class Button so we could skip. Now the usage of the Sensor Button for EV3 platform is complete.
Feel free to add new examples or collaborate in other areas. Your syntax is modern and I noticed you have a good professional Java background.
I am going to close this support issue.

authors: jabrena jartu


text:
Different rules on regenerating

I get different rules, each time I run the code.

transaction = [['0', '1', '2', '3', '4', '5', '6', '7', '8', '9', '10', '11', '12', '13', '14',\
 '15', '16', '7', '17', '18', '19', '20', '21', '7', '22', '23', '24', '25', '26', '27', '28', '29', '30', '31', '29', '30'], ['32', '33'],\
['34', '34', '34', '34', '34', '34', '34', '34', '35', '35', '36', '36', '34', '34', '37', '37', '37', '37',\
 '37', '37', '34', '34', '29', '30', '36', '36', '36', '36', '36', '36']]

import pyfpgrowth as fg
patterns = fg.find_frequent_patterns(transaction, 3)
rules = fg.generate_association_rules(patterns, 0.1)

Can anyone see it ?

Ran this code three times and rules always are consistent  as below
(('37',), 1.25)
(('30',), 1.5)
(('34',), 1.0)
(('30',), 1.0)
(('30',), 1.0)
((), 0.2916666666666667)
(('37',), 0.15625)
(('37',), 6.0)
(('36',), 1.0)
((), 0.3125)
(('36',), 0.20833333333333334)
(('29',), 1.0)
(('30',), 1.0)
(('29',), 1.0)
((), 1.0)
((), 0.3125)
(('30',), 1.5)
(('30',), 1.0)
(('30',), 1.0)
(('37',), 6.0)
(('36',), 1.0)
(('36',), 1.0)
(('37',), 6.0)
(('34',), 2.5)
(('36',), 1.0)
(('34',), 12.0)
(('37',), 6.0)
((), 0.20833333333333334)
(('34',), 1.0)
(('34',), 12.0)
(('29', '30'), 1.0)
(('30',), 1.0)
(('30',), 1.0)
(('30',), 0.3125)
(('30',), 1.0)
(('34',), 1.0)
(('34',), 1.0)
((), 0.3125)
(('36',), 1.0)
(('36',), 8.0)
((), 0.20833333333333334)
(('34',), 12.0)
(('30',), 2.0)
(('30', '34'), 1.0)
(('30',), 2.0)
(('29',), 1.0)
(('29',), 1.5)
(('34',), 1.0)
(('30',), 1.0)
((), 1.0)
(('37',), 0.15625)
(('29', '34'), 1.0)
((), 0.3125)
(('30',), 1.0)
(('29',), 1.0)
(('36', '37'), 1.25)
(('30', '37'), 6.0)
((), 0.3125)
(('29',), 1.0)
(('30', '36'), 1.0)

I am running it on python3. Are you using python2 or python3 ?

I am using python  2.7

The issue may be with python 3.

There isn't any issue with python 3. The results are consistent.

repo: evandempsey/fp-growth

license: isc


text:
International Command Center bug

Just a stupid bugfix of I18N tool. (And also a little experiment with my brand new github membership :-) )

Thanks!

authors: evanmiller ztmr


text:
Not updating startDate and endDate

I have a method which updates startDate and endDate as below.
 clearFilters() {     this.options.startDate = this.start ;     this.options.endDate = this.end;   }
In my constructor :
constructor() {
this.start = moment().startOf('month');
    this.end = moment().endOf('month');
  this.options = {
  locale: {
   format: 'DD/MM/YYYY',
  firstDay: 1
      },
      startDate: this.start,
     endDate: this.end,
    showDropdowns: false,
     ranges: {
       'Today': [moment(), moment()],
      'Tomorrow': [moment().add(1, 'days'), moment().add(1, 'days')],
      'Current Week': [moment(), moment().add(6, 'days')],
      'Next Week': [moment().add(7, 'days'), moment().add(14, 'days')],
      'Current Month': [moment().startOf('month'), moment().endOf('month')]
    },
  };
}
I am trying to set startDate and endDate with clearFilters method as mentioned above. But it is not getting updated on my picker. I think it is not calling its callback funtion.

Updating the startDate or endDate options does not change the range after the selection has been done.
If you want to update the startDate and endDate programmatically you have to use the setStartDate and setEndDate methods of the picker.
See this section in the documentation for more details: https://github.com/evansmwendwa/ng2-daterangepicker#daterangepicker-methods


text:
🛑 demo.actionherojs.com is down

In 87279ff, demo.actionherojs.com (https://demo.actionherojs.com/api/status) was down:

HTTP code: 503
Response time: 235 ms

Resolved: demo.actionherojs.com is back up in da8ed8f.

repo: evantahler/upptime


text:
🛑 www.actionherojs.com is down

In e356c33, www.actionherojs.com (https://www.actionherojs.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: www.actionherojs.com is back up in bdad0f4.


text:
Ford (Mustang Mach-E): 403 forbidden

Describe the bug
The connection to the Ford API stopped working for a couple of days.
No changes in my config, no changes in my login data. Ford App works as expected.
Syslog states:
creating vehicle ev5 failed: cannot create vehicle 'template': cannot create vehicle 'ford': login failed: unexpected status: 403 (Forbidden)
I attached the trace output which shows "Service unavailable" HTML page as a response to the GET.
Steps to reproduce

...
Configuration details
- name: ev5
  type: template
  template: ford
  title: Mustang Mach-E # Wird in der Benutzeroberfläche angezeigt (optional)
  user: email # Benutzerkonto (bspw. E-Mail Adresse, User Id, etc.)
  password: "password" # Passwort des Benutzerkontos (bei führenden Nullen bitte in einfache Hochkommata setzen)
  vin: myVIN # Erforderlich, wenn mehrere Fahrzeuge des Herstellers vorhanden sind (optional)
  capacity: 75.7 # Akkukapazität in kWh (optional)

Log details
ov 30 08:07:18 pi4 evcc[139796]: [ford  ] TRACE 2023/11/30 08:07:18 GET https://sso.ci.ford.com/v1.0/endpoint/default/authorize?...
Nov 30 08:07:18 pi4 evcc[139796]: [ford  ] TRACE 2023/11/30 08:07:18 <html>
Nov 30 08:07:18 pi4 evcc[139796]: <title>Service unavailable</title>
Nov 30 08:07:18 pi4 evcc[139796]: <head>
Nov 30 08:07:18 pi4 evcc[139796]: #011<link rel="stylesheet" type="text/css" href="https://unpkg.com/carbon-components/css/carbon-components.min.css">
Nov 30 08:07:18 pi4 evcc[139796]: #011<script src="https://unpkg.com/carbon-components/scripts/carbon-components.min.js"></script>
Nov 30 08:07:18 pi4 evcc[139796]: #011<meta http-equiv="Content-Type" content="text/html; charset=utf-8"/>
Nov 30 08:07:18 pi4 evcc[139796]: #011<style>
...

What type of operating system are you running?
Linux
Version
0.122.1

Ford hat mal wieder den Mechnismus geändert- leider in etwas sehr Kompliziertes... Workaround: Integration per ioBroker.

Naja, in HA wurde es auch adaptiert. Wirkt jetzt auf mich nicht so sehr viel komplexer als vorher.
https://github.com/itchannel/fordpass-ha/commit/306900b6b713ed4759533fc26aed4a58261803f4

I have an old Ford Login - I will see if I can get this adjusted based on the changes they did in HA.

Could someone please share login credentials with info@evcc.io?

@appcoders mal im Browser komplett durchgespielt? Müssen da vielleicht neue TOS oder ähnliches akzeptiert werden?

authors: GrimmiMeloni andig miniluma

repo: evcc-io/evcc


text:
Add GoodWe EM

In diesem Internet:
https://downloads.vodnici.net/uploads/wpforo/attachments/483/4349-1GoodweModbusPROTOCOLHybrid-ENV1-3EMseries.pdf
https://forum.iobroker.net/assets/uploads/files/1666333836822-goodwe_modbus_protocol_hybrid_et_eh_bh_bt__arm205-hv__v1.7-_-read-only_20200226-1.pdf
Originally posted by @pohlinkzei in https://github.com/evcc-io/evcc/discussions/16028#discussioncomment-10653064

@pohlinkzei mir fehl aktuell die Kapazität. Wenn Du es schaffst, aus https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/goodwe-hybrid.yaml oder https://github.com/evcc-io/evcc/blob/master/templates/definition/meter/goodwe-dt.yaml einen Vorschlag mit neuen Registern zu erstellen (jeweils für Grid/ PV/ Battery) würde das den Prozess deutlich beschleunigen.

Ich bin gerade dabei mich in das Thema einzuarbeiten, hab aber (noch) keine Ahnung von Netzwerkzeugs. Mein EM-Wechselrichter hat auf erste Annäherungsversuche per RS485/UDP@Wifi nicht brauchbar reagiert.
Die Implementation vom HA für den EM habe ich auch gefunden, das habe ich aber noch nicht nachstellen können.
https://github.com/marcelblijleven/goodwe/blob/master/goodwe/es.py

Du musst einfach nur ein custom meter konfigurieren. Gebaut werden muss da nix.

Das hatte ich erfolglos versucht. In der Implementierung zum EM-WR stand außerdem, dass die Kommunikation per WiFI (?) mit einem 0xAA 0x55 0xC0 0xF7 Header läuft umd UDP (?) ähnlicher zu werden... Ich habe keine Ahnung von TCP/UDP und so. Ich bin eher der PHY/HAL-Typ. Aber hier mal mein custom-Versuch:
`- type: custom
name: GoodWe-EM-PV
usage: pv
power:
source: calc
add:
source: calc
mul:
- source: modbus
id: 247
uri: 192.168.178.66:8899
timeout: 3s
register:
address: 1280
type: holding
decode: uint16
- source: modbus
id: 247
uri: 192.168.178.66:8899
timeout: 3s
register:
address: 1281
type: holding
decode: uint16
source: calc
mul:
- source: modbus
id: 247
uri: 192.168.178.66:8899
timeout: 3s
register:
address: 1283
type: holding
decode: uint16
- source: modbus
id: 247
uri: 192.168.178.66:8899
timeout: 3s
register:
address: 1284
type: holding
decode: uint16

type: custom
name: GoodWe-EM-BAT
usage: battery
power:
source: calc
mul:

source: modbus
id: 247
uri: 192.168.178.66:8899
timeout: 3s
register:
address: 1286
type: holding
decode: uint16
source: modbus
id: 247
uri: 192.168.178.66:8899
timeout: 3s
register:
address: 1290
type: holding
decode: uint16

soc: # Batterie SOC (%)
source: modbus
id: 247
uri: 192.168.178.66:8899
timeout: 3s
register:
address: 1294
type: holding
decode: uint16`

Und funktoinierts? Die Einrückung brauchts...

Leider nicht. Wie geschrieben, ich glaube es braucht einen anderen Header für die UDP-Modbus-Übertragung, wie hier (https://github.com/marcelblijleven/goodwe/blob/master/goodwe/protocol.py#L469-L479) beschrieben. Bei Homeassistant scheint der WR ja zu funktionieren.

So wird das nicht. Deine Config ist unvollständig. Ich mache hier mal zu bis es eine vollständige Config gibt die überhaupt testfähig wäre.

authors: andig pohlinkzei


text:
Estimator - Fehlermeldungen im UI bezgl. NaN

Discussed in https://github.com/evcc-io/evcc/discussions/2701

Originally posted by Waldmensch1 February 25, 2022
Ich habe gestern mal mit loadpoint.soc.estimate = true gespielt. Über Nacht hatte ich dann diese Fehler im UI. Keine Ahnung, ob estimate dafür ursächlich war, aber der NaN Fall sollte grundsätzlich abgefangen (eventuell auf 0 oder null gesetzt werden) und nicht ans UI gehen. Das mündet sonst in einem invaliden JSON Objekt.
Codebasis: aktueller Master Branch

Nachtrag: es liegt nicht an estimate. Das habe ich jetzt auf false. Der Fehler kommt trotzdem. Muss also am aktuellen Master liegen. Vehicle wird über TRONITY abgefragt. Funktionierte schon eine ganze Weile reibungslos

Nachtrag2: Wenn man den kompletten soc: parameter (mit unterparametern) aus dem Loadpoint entfernt, scheint der Fehler nicht aufzutreten.

Ich kann mir auf einen flüchtigen Blick in den Estimator-Code momentan noch nicht vorstellen woher da NaN kommen sollte.
Wie sieht denn die zugehörige Konfig aus?

Hilfreich wäre vllt auch ein komplettes Logfile damit wir sehen wo die ersten NaNs auftauchen.

@andig da ist im Trace leider nichts zu sehen, oder ich habe es nicht erwischt, weil es in zeitlich großem Abstand auftritt. (Ca. 1h, s. 1. Screenshot). Ich werde über den Tag den evcc nochmal auf auf dem PC starten und den Trace in ein File loggen, um das vielleicht doch zu schnappen.
@premultiply die configuration ist Standard TRONITY, die funktioniert auch. Auffällig im 2. Screenshot ist, dass es das große JSON Objekt ist. Normal kommen über den Websocket ja Einzelwerte. Die Loadpoint config editiere ich hier gleich noch vom PC aus rein

Kannst Du mal in /api/status rein schauen wenn das passiert? Das ist ein kompletter Abzug des ganzen Caches.

Und bitte auch die Fahrzeug-Konfig. Z. B. capacity ist da relevant.

@premultiply capacity ist gar nicht gesetzt. Vieleicht ist es das schon?
- name: enyaq
  type: tronity
  title: Enyaq
  credentials:
    id: 299e4759-0732-416c-8984-xxxxxxxxxxx
    secret: eb76070b-1672-4d1f-xxxxxxxxxxxxxxx
  capacity: # optional
  vin: #optional

Ah, ja, genau. Da wird das herkommen!

Solltest Du dann evtl. abfangen, da der Parameter laut Doku optional ist. Ich lass es jetzt erstmal über den Tag laufen mit full trace 2 file. Wobei im Estimator keine TRACE ausgaben sind. Die laufen alle unter DEBUG

Jo, das hatte ich nicht auf dem Schirm dass das 0 sein könnte.
Würde dann auch IMHO eigentlich weiter vorne abgefangen gehört, oder @andig?

Der Vollständigkeit halber, das NaN kommt direkt nach der Tronity response
[lp-1  ] DEBUG 2022/02/28 11:19:22 charger status: B
[cache ] TRACE 2022/02/28 11:19:22 lp-1/chargeDuration: 0s
[cache ] TRACE 2022/02/28 11:19:22 lp-1/connected: true
[cache ] TRACE 2022/02/28 11:19:22 lp-1/charging: false
[cache ] TRACE 2022/02/28 11:19:22 lp-1/enabled: false
[tronity] TRACE 2022/02/28 11:19:22 POST https://api-eu.tronity.io/oauth/authentication
[tronity] TRACE 2022/02/28 11:19:23 {"client_id":"***","client_secret":"***","grant_type":"app"}
--
{"id":"fe544e35-2df8-4f0e-9b92-3d1236a77e85","access_token":"xxxxxxxxxxxxxxxxx","expires_in":3600,"token_type":"bearer"}
[tronity] TRACE 2022/02/28 11:19:23 GET https://api-eu.tronity.io/v1/vehicles/6207aee48xxxxxx0012c430ff/bulk
[tronity] TRACE 2022/02/28 11:19:23 {"odometer":0,"range":168,"level":47,"charging":"Complete","plugged":true,"chargerPower":0,"chargeRemainingTime":null,"latitude":null,"longitude":null,"timestamp":1646043486619}
[lp-1  ] DEBUG 2022/02/28 11:19:23 soc estimated: NaN% (vehicle: 47.00%)
[lp-1  ] DEBUG 2022/02/28 11:19:23 vehicle soc: NaN%
[lp-1  ] DEBUG 2022/02/28 11:19:23 vehicle range: 168km
[cache ] TRACE 2022/02/28 11:19:23 lp-1/vehicleSoC: NaN
[cache ] TRACE 2022/02/28 11:19:23 lp-1/chargeRemainingEnergy: NaN
[cache ] TRACE 2022/02/28 11:19:23 lp-1/vehicleRange: 168
[lp-1  ] DEBUG 2022/02/28 11:19:23 vehicle odometer: 0km
[cache ] TRACE 2022/02/28 11:19:23 lp-1/vehicleOdometer: 0
[lp-1  ] DEBUG 2022/02/28 11:19:23 max charge current: 0A = 0A + -0.609A (140W @ 1p)
[lp-1  ] DEBUG 2022/02/28 11:19:23 charge power: 0W
[lp-1  ] DEBUG 2022/02/28 11:19:23 charge currents: [0 0 0]A
[cache ] TRACE 2022/02/28 11:19:23 lp-1/chargePower: 0
[cache ] TRACE 2022/02/28 11:19:23 lp-1/chargeCurrents: [0 0 0]
[cache ] TRACE 2022/02/28 11:19:23 homePower: 805.0000000000002
[mqtt  ] TRACE 2022/02/28 11:19:25 recv stadtweg/energy/tripower: '{"smaem":{"regard":0,"surplus":405,"L1":1.223,"L2":2.076,"L3":1.4000000000000001,"energy":26588,"merge":-405},"pwr1":560,"soc":15,"sw":-1456.068,"pwr2":2016.068,"pvgarten":227,"pvgrowatt":391}'
[mqtt  ] TRACE 2022/02/28 11:19:30 recv stadtweg/energy/tripower: '{"smaem":{"regard":0,"surplus":414,"L1":1.241,"L2":2.086,"L3":1.363,"energy":26588,"merge":-414},"pwr1":574,"soc":15,"sw":-1479.9940000000001,"pwr2":2053.994,"pvgarten":227,"pvgrowatt":391}'
[site  ] DEBUG 2022/02/28 11:19:32 ----

authors: Waldmensch1 andig premultiply


text:
Question: 'Failure website' showing for all 'wrong' addresses?

Error description:
We have a wildcard cname for this, so that one could access it from all subdomains under that host.
But if somebody misspells it, they get a certificate signed by CN=letsencrypt-nginx-proxy-companion.
Would it be possible to have some sort of 'catch-all' website that will catch none-configured hostnames.
So if you have
12345.cname.wildcard.com you will be shown the right website
and you mistype maybe like
23456.cname.wildcard.com
they would get a 'default' website.

Hello @fribse I have never tried... would you please share if you accomplish to do that? I would like to add it to the docs.

authors: evertramos fribse

repo: evertramos/nginx-proxy-automation


text:
webassembly build

I tried building on my own but it keeps breaking. will you like to distribute such a build that can be directly consumed using JS?

or maybe just commit your generated pkg folder too so that some exploring can have a look?

Sure, if it is of interest I could probably just publish the generated npm package to npm. I want to avoid committing it to the repo as it contains the binary webassembly file.
What kind of problems did you have trying to build the project?

It was an issue with the rustup version. I had to update it to nightly build to make it work. A npm package will be great. I want to use it on https://transform.tools/ . I can provide the link to your npm package there in case anyone wants to use it programatically.

Hmm, checked now, and seems I am building on stable myself, but I see the CI on this repo is incorrectly configured so that the wasm module is not built on CI, so I'm not too confident in how reliably that part builds.
What kind of interface would you need to use it the way you want? At the moment the wasm module is very much in an MVP stage, so the exposed function just returns a string no matter what happens (the exposed function).

I just need the generated pkg folder. I have been able to build it and just copied the pkg folder. Everything is working great.
I think the function returning a string is good enough. If there is an error, I can catch it via try/catch. So the API doesn't seem to have any issue. btw thanks for this. It has helped me close multiple issues on my repo relating to rust.

Cool, if that's all you need I'll just let what is there now be the initial version of the npm package. And if I change the interface I'll leave the current version around for backwards compatibility.
So there is a npm package here now: https://www.npmjs.com/package/json_typegen_wasm

FYI: I ended up re-publishing (which was then 0.3.3) the wasm module, as compiled with
[profile.release]
lto = true
opt-level = "s"

the wasm module is ~200KB smaller, which is quite a bit.

That's awesome. Thanks a lot for this. ❤


text:
Account for offsets that are too large for first element

When a blacklisted element splits a single text node into multiple nodes, and the offset points to a node that is not the first, then this fix is needed to return the actual elements and offsets that the range cfi is pointing to.

Fixed pull request to ensure that when an offset of "0" is present in the rangeCFI that it doesn't get transformed to undefined.

repo: evidentpoint/readium-cfi-js


text:
Update sbt-release to 1.3.0

About this PR
📦 Updates com.github.sbt:sbt-release from 1.0.15 to 1.3.0
📜 GitHub Release Notes - Version Diff
Usage
✅ Please merge!
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

⚙ Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "com.github.sbt", artifactId = "sbt-release" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "com.github.sbt", artifactId = "sbt-release" }
}]

labels: sbt-plugin-update, early-semver-minor, semver-spec-minor, commit-count:1

Superseded by #580.

repo: evolution-gaming/kafka-flow


text:
Update scalatest to 3.2.12

Updates org.scalatest:scalatest from 3.2.9 to 3.2.12.
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.scalatest", artifactId = "scalatest" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequest = { frequency = "@monthly" },
  dependency = { groupId = "org.scalatest", artifactId = "scalatest" }
}]

labels: test-library-update, early-semver-patch, semver-spec-patch, commit-count:1

Superseded by #93.

repo: evolution-gaming/serially


text:
Unable to get my eGPU working

Howdy folks, I'm on my every year attempt in trialing out linux. I have Intel iGPU, Nvidia dGPU and Nvidia eGPU (via Thunderbolt3). According to nvidia-smi and lspci (or whatever the last command was to list the hardware), the gpu is detected and driver attached to it.
lspci -k -d ::03xx
00:02.0 Display controller: Intel Corporation Alder Lake-P GT2 [Iris Xe Graphics] (rev 0c)
    DeviceName: Onboard - Video
    Subsystem: ASUSTeK Computer Inc. Device 1aec
    Kernel driver in use: i915
    Kernel modules: i915, xe
01:00.0 VGA compatible controller: NVIDIA Corporation GA104 [Geforce RTX 3070 Ti Laptop GPU] (rev a1)
    Subsystem: ASUSTeK Computer Inc. Device 1aec
    Kernel driver in use: nvidia
    Kernel modules: nouveau, nvidia_drm, nvidia
06:00.0 VGA compatible controller: NVIDIA Corporation GA102 [GeForce RTX 3080] (rev a1)
    Subsystem: Gigabyte Technology Co., Ltd Device 405d
    Kernel driver in use: nvidia
    Kernel modules: nouveau, nvidia_drm, nvidia

nvidia-smi
Sat Dec  7 17:19:43 2024
+-----------------------------------------------------------------------------------------+
| NVIDIA-SMI 565.77                 Driver Version: 565.77         CUDA Version: 12.7     |
|-----------------------------------------+------------------------+----------------------+
| GPU  Name                 Persistence-M | Bus-Id          Disp.A | Volatile Uncorr. ECC |
| Fan  Temp   Perf          Pwr:Usage/Cap |           Memory-Usage | GPU-Util  Compute M. |
|                                         |                        |               MIG M. |
|=========================================+========================+======================|
|   0  NVIDIA GeForce RTX 3070 ...    Off |   00000000:01:00.0  On |                  N/A |
| N/A   49C    P0             48W /  139W |    1512MiB /   8192MiB |      3%      Default |
|                                         |                        |                  N/A |
+-----------------------------------------+------------------------+----------------------+
|   1  NVIDIA GeForce RTX 3080        Off |   00000000:06:00.0 Off |                  N/A |
|  0%   24C    P8             11W /  320W |       2MiB /  10240MiB |      0%      Default |
|                                         |                        |                  N/A |
+-----------------------------------------+------------------------+----------------------+

What's the issue is that no monitors connected to it is detected.  I also tried all-ways-egpu - tried all 3 methods. Every time it's supposed to be using the egpu, I just get black screen with the _ on top left or computer boot screen on the laptop monitor.
I've tried cachyos (both KDE and GNOME wayland) and even tried with Nobara. All behaved the same. Currently on cachy KDE (wayland). I know when I last trialed linux longer 2y ago (on another laptop), I had a similar issue. Managed to get it working thorugh X11 then but would like to get it working with wayland this time. Any idea what might be the cause?

The Nvidia eGPU+Nvidia dGPU+iGPU combination seems to be a tricky one for sure. Others have reported issues with this combination as well.
IIRC GNOME still has issues with Intel iGPU when an Nvidia gpu is primary so I'd recommend sticking to KDE.
Have you tried manually reloading the nvidia_drm module as this was found helpful here? https://github.com/hertg/egpu-switcher/issues/117

@GameBurrow I can look into adding a way to automate it, but since I don't have an Nvidia dGPU system I'd have to rely on you to test it to make sure it works as intended

I added changes to the GitHub repo that added an entry point to the script. The idea is that you can add the custom commands needed for your unique setup before and after the script is run.
You can try installing the latest git version following these steps
Then add the commands you need to the /usr/bin/all-ways-egpu-entry.sh file as mentioned in the Entry Point section in the readme. Those commands will then be executed when the script is called at startup or if all-ways-egpu-entry.sh is run
Unfortunately, I can't help with the other Nvidia driver issues as I don't have any experience with those

I also have an Intel cpu/igpu, nvidia dgpu, and nvidia egpu. I'm using a razer blade 2018-base and a razer core x enclosure. Using method 2, I'm able to get the endeavour os (Wayland) login screen to show up on two of my monitors, while my laptop screen is blank. However, once I login, both monitors go blank and my laptop screen turns on.
I'm hoping I might be able to help with troubleshooting the nvidia dgpu/egpu - are there any logs I can share or tests I can do that might provide useful info?
This is the one of the main hurdles preventing me from switching to Linux on my laptop. I've basically replaced windows on my desktop, which outputs directly to a single display.
Lastly, thanks @ewagner12 for all that you've done for those of us stubbornly trying to get our egpus working with Linux!

@GameBurrow
Ok if you get stuck at boot like that the way to recover is to enter the grub boot menu (or whatever bootloader you're using) and boot to the multi-user.target. The script only triggers for the graphical.target so any other target like multi-user or the recovery option Ubuntu provides should avoid the script and let you login.

@GameBurrow @armenmatoosian
I just remembered that SDDM (the KDE login screen) defaults to using X rather than wayland and that's been known to cause issues. So for both of you I'd recommend switching it to use wayland instead: https://wiki.archlinux.org/title/SDDM#Wayland
That might work around some login issues you're seeing.

I added changes to the GitHub repo that added an entry point to the script. The idea is that you can add the custom commands needed for your unique setup before and after the script is run.
You can try installing the latest git version following these steps
Then add the commands you need to the /usr/bin/all-ways-egpu-entry.sh file as mentioned in the Entry Point section in the readme. Those commands will then be executed when the script is called at startup or if all-ways-egpu-entry.sh is run
Unfortunately, I can't help with the other Nvidia driver issues as I don't have any experience with those

Small update, did the try the script, it resulted in my me being unable to get into the OS at all( couldn't even get to TTY), even when eGPU was disconnecced, problably means it attempted to load the script too early or sth. Will try again at one point when I have to time to fix the the issue of me not getting in (thankly I have that the linux build on my disc for testing only atm).

I did some testing with an nvidia eGPU and I think this issue with the git version of the script was caused by reloading the nvidia_drm module. It seems like it resets the parameters needed for Wayland so reloading nvidia_drm should be done with the command:
modprobe -r nvidia_drm && modprobe nvidia_drm modeset=1 fbdev=1
In my testing that seemed to fix the issue so I made that change to the entry point example in the github repo. If you have time to test again you can change your /usr/bin/all-ways-egpu-entry.sh to make sure you're including the modeset=1 and fbdev=1 parameters

authors: GameBurrow armenmatoosian ewagner12


text:
feat(esl-popup): add extended offsetContainer configuration

In the scope of PR:

add extended offsetContainer configuration to set up different values for offset by x and offset by y

:tada: This PR is included in version 4.0.0-beta.4 :tada:
The release is available on:

npm package (@beta dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

authors: ala-n dshovchko

repo: exadel-inc/esl


text:
Option icons usage update

Now icons are in a separate file, and for playground users it is easy to interact with icons and customize them

OptionIcons class was created and jsx-dom was added
Option styles have been simplified
Closes: https://github.com/exadel-inc/ui-playground/issues/507

:tada: This PR is included in version 1.1.0-beta.1 :tada:
The release is available on:

npm package (@beta dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

repo: exadel-inc/ui-playground


text:
from typing import Self not supported

When self-referencing inside a class, it is possible in Python to do
from typing import Self

class Node:
    neighbor: Self

Currently, referencing the Node-class directly is different in Python (neighbor: 'Node') and Codon (neighbor: Node) so I thought it would be nice to use Self, so the script could run on both Python and Codon.
Could the typing-mock be extended with Self?

Oh, we should add this—thanks for the suggestion! Right now you need to use neighbor: Node.

Merging into #608 .

authors: akleemans inumanag

repo: exaloop/codon


text:
[docs]【全般】全体のメニュー名やレコードのカラム名の整理

【全般】全体のメニュー名やレコードのカラム名の整理

321と同件のため

authors: ooif sinatommy

repo: exastro-suite/it-automation-docs


text:
cancelling polygon creation creates unfinished shape with broken annotation [REPLACEMENT ISSUE]

The original issue
Id: 43
Title: cancelling polygon creation creates unfinished shape with broken annotation

could not be created.
This is a dummy issue, replacing the original one. It contains everything but the original issue description. In case the gitlab repository is still existing, visit the following link to show the original issue:
TODO

could not reproduce

authors: duncdrum line-o

repo: exc-asia-and-europe/ecpo-annotator


text:
Feature: New Action - Reseed button

I would like to be able to reseed for a selected shape.
Especially when drawing squared boxes some seeds give double lines that are obstructing.
Having a button to press (e.g. in Actions) would be nice to have
fa-recycle comes to mind.

Example

I don't think adding a dedicated button for a low-level feature like this is the right way to go --- our guiding principle for Exalidraw is to get the defaults right, and offer limited customization for the rest.
If the behavior on the whole is suboptimal, we should address that instead. We haven't gotten complaints on this yet (apart from yours).
But I agree that there are cases where it would be handy. Whether it warrants a new feature is another matter. If this gets rejected, we could possibly add a shortcut for it, for those that really care.

For reseeding specifically one suggestion would be to reseed by default when you change to the "sloppiness" from architect to Artist or cartoonist.
As UX goes they have already significantly changed the line-style (which is already unique for every drawn shape) so I don't think the line being slightly different while toggling options would be startling.
Ultimately I think the real complaint is is the multi-stroke line or the roughness in general.
draw.io which uses the same underlying library (rough.js) exposes wayyy more options but two things they did for this are

added a "Comic Style" which turns down the "roughness" and sets the disableMultiStroke Parameter for a simpler effect.
exposes a toggle for the disableMultiStroke directly.

(Article on how they use rough.js)
Some quick simple options:

as excalidraw already has an artist and comic "sloppiness" level I'd consider one of them having disableMultiStroke set to true
Choose one of the existing levels (say cartoonist) and if the shape is cartoonist expose a new stroke style of "clean" which is just a toggle of the disableMultiStroke property

That was quick, probably already helpful enough, but also kind of hidden. Thanks.

I think we can close that one!

authors: DennisSmolek Jan-M dwelle lipis

repo: excalidraw/excalidraw


text:
Frames

API support. Unclear how/when/if exposed on excalidraw.com

@chrisyelf no, this will allow exporting with a fixed size, but not drawing / scrolling outside of the frame(s).


text:
Create CHANGELOG.md and start publishing release notes

& releases with version numbers and quick recap for your updates and sprints

Beautiful

This would be great indeed. I don't think we need an issue to track it though, I'm going to close it.

authors: RandomFractals bashbsc vjeux


text:
Undo/redo doesn't work if element selected

Not sure when this regression was introduced.
Steps:

select element
resize it
cmd+z/ctrl+z to undo.
Doesn't do anything until you deselected.

We're probably preventing it FSR.

Something related to history!

Is this a duplicate of #687? Do cmd+c/cmd+v work for you?

Not sure, since in that issue the cause is unclear (no repro steps). Either way, this will be fixed  in #701.

fixed in #701

authors: Fausto95 dwelle sompylasar


text:
Styles get lost when saving with writeBuffer function

💬 Questions and Help
Hello. I am opening an xlsx file on the client side, using angular, but when I modify the file and try to save it, all styling get lost. This is my code:
exportLocalXlsx(): void {
    const workBook: Workbook = new Workbook();
    const subscription = this.http.get('./assets/Modelo.xlsx', { responseType: 'blob' })
    .subscribe(value => {
    const blob: Blob = value;
    const reader = new FileReader();
    const tplan = this.totalPlan;
    reader.onload = function (e: any) {
      const contents = e.target.result;
      console.log(contents);
      workBook.xlsx.load(contents).then(data => {
        // workBook.getWorksheet(1).addRow(['new data', 1, 2, 3]);
        // const valor = workBook.worksheets[0].getCell(1, 1).value;
        // console.log(valor);
        workBook.worksheets[0].getCell(3, 14).value = tplan;
        workBook.xlsx.writeBuffer().then(data => {
          const blobUpdate = new Blob([data], { type: 'application/vnd.openxmlformats-officedocument.spreadsheetml.sheet' });
          fsaver.saveAs(blobUpdate, 'samplefile.xlsx');
          console.log('Excel Exported successfully');
        });
      });
    };
    reader.readAsArrayBuffer(blob);
    });
  }

This is the messages shown by Microsoft Excel after opening the file (sorry the text is in Spanish):
Excel ha completado la validación y reparación en nivel de archivo. Puede que se hayan reparado o descartado algunas partes de este libro.
Parte quitada: /xl/styles.xml parte con error de XML.  (Estilos) Cargar error. Línea 2, columna 0.
Registros reparados: Información de celda de /xl/worksheets/sheet1.xml parte
Registros reparados: Información de columna de /xl/worksheets/sheet1.xml parte
Registros reparados: Formato condicional de /xl/worksheets/sheet1.xml parte
Thanks for any help.

Aparently it was a problem with the source xlsx file I was using.

repo: exceljs/exceljs


text:
[BUG]Meet an error "Error: EPERM: operation not permitted" when I use formula to quote another tab's cell's value

I will use exceljs to analyze total amount of some data. I create two tabs which is Q1 and Q2 and contains all the sales number. When I try to create a overview tab and to quote Q1's cell like B2.
I use worksheet.getCell('B2').value = { formula: "'Q1'!B2", date1904: false}
But it give me error: "Error: EPERM: operation not permitted"

It works


text:
Why can't I get the data for @ request

Why can't I get the data for @request? RequestInfo is Null
That's how I use it.
client.submitException(e);

I'm not sure if a plugin is registered or if it's possible to get access to the request context so that is why it may not be populated. It would probably help to say what frameworks you are using and also dig into the library and take a look. I'm not familiar as this is a community maintained integration.

I'm not sure if a plugin is registered or if it's possible to get access to the request context so that is why it may not be populated. It would probably help to say what frameworks you are using and also dig into the library and take a look. I'm not familiar as this is a community maintained integration.

I Create a New Project.
java 11 and pom.xml
<dependency>             <groupId>io.github.nbgesion</groupId>             <artifactId>exceptionress-client</artifactId>             <version>1.0.5</version>         </dependency>         <!-- EXPLICIT DECLARATION -->         <dependency>             <groupId>com.squareup.okhttp3</groupId>             <artifactId>okhttp</artifactId>             <version>4.9.1</version>         </dependency> <dependency>             <groupId>org.springframework.boot</groupId>             <artifactId>spring-boot-starter-web</artifactId>         </dependency>
Debug：

request = null
Please.

I'm not sure if a plugin is registered or if it's possible to get access to the request context so that is why it may not be populated. It would probably help to say what frameworks you are using and also dig into the library and take a look. I'm not familiar as this is a community maintained integration.

I Create a New Project.
java11 and pom.xml:
<dependencies>     <dependency>         <groupId>com.exceptionless</groupId>         <artifactId>exceptionless-client</artifactId>         <version>0.1.0</version>     </dependency>     <dependency>         <groupId>org.springframework.boot</groupId>         <artifactId>spring-boot-starter-web</artifactId>     </dependency>     <!-- EXPLICIT DECLARATION -->     <dependency>         <groupId>com.squareup.okhttp3</groupId>         <artifactId>okhttp</artifactId>         <version>4.9.1</version>     </dependency> </dependencies>
Debug:

I Can't Get the RequestInfo.
Please.

@pc9795 Any ideas?

Let me have a look

Let me have a look

what's up?bro.

@pc9795 please look at this.
https://private-user-images.githubusercontent.com/118280527/335007221-aa036410-c1c1-44de-8856-0ee15501a9c0.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MTc3Mzk0MzAsIm5iZiI6MTcxNzczOTEzMCwicGF0aCI6Ii8xMTgyODA1MjcvMzM1MDA3MjIxLWFhMDM2NDEwLWMxYzEtNDRkZS04ODU2LTBlZTE1NTAxYTljMC5wbmc_WC1BbXotQWxnb3JpdGhtPUFXUzQtSE1BQy1TSEEyNTYmWC1BbXotQ3JlZGVudGlhbD1BS0lBVkNPRFlMU0E1M1BRSzRaQSUyRjIwMjQwNjA3JTJGdXMtZWFzdC0xJTJGczMlMkZhd3M0X3JlcXVlc3QmWC1BbXotRGF0ZT0yMDI0MDYwN1QwNTQ1MzBaJlgtQW16LUV4cGlyZXM9MzAwJlgtQW16LVNpZ25hdHVyZT1hZWE4OThhN2FiOWI2YzdmMGYwMjFlOTliMjVlNjZlYzc1MTllNmY5Y2U3OTdkNzgyZTFjODc0NDVkOTVhMzUzJlgtQW16LVNpZ25lZEhlYWRlcnM9aG9zdCZhY3Rvcl9pZD0wJmtleV9pZD0wJnJlcG9faWQ9MCJ9.QeglFdfyQwpUG7EjAR2_mKLibkF_LGNZ_bez7f0kM58

Hello @nbgesion and thanks for your patience. I was out of the town for a while 🙇
I looked into the issue and I can see you are using
client.submitException(e)

This particular method just submits an error event with an exception and don't know anything about what request has caused this exception. We can see the code here
To get what you want to do we have to do something like this
 client.submitEventWithContext(
        EventPluginContext.builder()
            .event(client.createError().build())
            .context(PluginContext.builder().exception(e).request(request).build())
            .build());

Let me know if it solves your issue

authors: nbgesion niemyjski pc9795


text:
🧹 remove unneeded logic to transform thebe options and improve naming

now that myst-frontmatter is doing more of the thebe options transformation work the logic in here to go from frontmatter to workable thebe options can be reduced.

need https://github.com/executablebooks/mystmd/pull/788 to come in and a myst-frontmatter release

repo: executablebooks/myst-theme


text:
Exercise does not support Latex builds in Sphinx

Sphinx version: 3.5.4
Python version: 3.8.2 (CPython)
Docutils version: 0.16 release
Jinja2 version: 3.0.1
Last messages:
resolving references...
done
writing...
failed
Loaded extensions:
sphinx.ext.mathjax (3.5.4) from c:\program files\python38\lib\site-packages\sphinx\ext\mathjax.py
sphinxcontrib.applehelp (1.0.2) from c:\program files\python38\lib\site-packages\sphinxcontrib\applehelp_init_.py
sphinxcontrib.devhelp (1.0.2) from c:\program files\python38\lib\site-packages\sphinxcontrib\devhelp_init_.py
sphinxcontrib.htmlhelp (2.0.0) from c:\program files\python38\lib\site-packages\sphinxcontrib\htmlhelp_init_.py
sphinxcontrib.serializinghtml (1.1.5) from c:\program files\python38\lib\site-packages\sphinxcontrib\serializinghtml_init_.py
sphinxcontrib.qthelp (1.0.3) from c:\program files\python38\lib\site-packages\sphinxcontrib\qthelp_init_.py
alabaster (0.7.12) from c:\program files\python38\lib\site-packages\alabaster_init_.py
rst2pdf.pdfbuilder (0.98) from c:\program files\python38\lib\site-packages\rst2pdf\pdfbuilder.py
sphinx_copybutton (0.3.3) from c:\program files\python38\lib\site-packages\sphinx_copybutton_init_.py
Traceback (most recent call last):
File "c:\program files\python38\lib\site-packages\sphinx\cmd\build.py", line 280, in build_main
app.build(args.force_all, filenames)
File "c:\program files\python38\lib\site-packages\sphinx\application.py", line 352, in build
self.builder.build_update()
File "c:\program files\python38\lib\site-packages\sphinx\builders_init_.py", line 293, in build_update
self.build(['all'], to_build)
File "c:\program files\python38\lib\site-packages\sphinx\builders_init_.py", line 360, in build
self.write(docnames, list(updated_docnames), method)
File "c:\program files\python38\lib\site-packages\sphinx\builders\latex_init_.py", line 304, in write
docwriter.write(doctree, destination)
File "c:\program files\python38\lib\site-packages\docutils\writers_init_.py", line 78, in write
self.translate()
File "c:\program files\python38\lib\site-packages\sphinx\writers\latex.py", line 101, in translate
self.document.walkabout(visitor)
File "c:\program files\python38\lib\site-packages\docutils\nodes.py", line 214, in walkabout
if child.walkabout(visitor):
File "c:\program files\python38\lib\site-packages\docutils\nodes.py", line 214, in walkabout
if child.walkabout(visitor):
File "c:\program files\python38\lib\site-packages\docutils\nodes.py", line 214, in walkabout
if child.walkabout(visitor):
[Previous line repeated 4 more times]
File "c:\program files\python38\lib\site-packages\docutils\nodes.py", line 206, in walkabout
visitor.dispatch_visit(self)
File "c:\program files\python38\lib\site-packages\sphinx\util\docutils.py", line 471, in dispatch_visit
super().dispatch_visit(node)
File "c:\program files\python38\lib\site-packages\docutils\nodes.py", line 1995, in dispatch_visit
return method(node)
File "c:\program files\python38\lib\site-packages\sphinx\writers\latex.py", line 2072, in unknown_visit
raise NotImplementedError('Unknown node: ' + node.class.name)
NotImplementedError: Unknown node: enumerable_node

Thanks for reporting @martinjaroszewicz
hey @AakashGfude we should look at adding LaTeX nodes to this package in similar fashion to sphinx-proof
Perhaps we can use:
https://ctan.org/pkg/exercise?lang=en
to typeset the exercise / problem sets.

@martinjaroszewicz Latex should be supported now with v0.2.1.

authors: AakashGfude martinjaroszewicz mmcky

repo: executablebooks/sphinx-exercise


text:
config.json: add info for bank-account

See #345

Sorry @tleen, I pressed the resolve conflicts button :grimacing:, I've never used that feature before and I couldn't help myself finding out what it did.
You'll probably want to pull my commit down and rebase the changes onto your commit, sorry for the extra work, still learning!! :grinning:
Also, watch the indentation on the topics, a minor thing perhaps but good to stay consistent :smile:

Np, I haven't used that button either.

I thought I was going to have to redo this one but the resolve conflicts fixed it. yay!

Hm, after rebase I see your changes but not in the file compare. Would merging this as is screw things up?

I think it would. The changes aren't showing up in the Files changed tab and we don't want to include this commit, https://github.com/exercism/go/pull/709/commits/13a1aaf1e2539d50154e6e35de9bb0a6ed37c38c, either.
I'm afraid it might be easier to redo on these changes. Sorry, I should've waited for these to be merged before merging #720

NP its an easy redo. :smile:

authors: robphoenix tleen

repo: exercism/go


text:
Wrong value in unit tests for high-score-board

Wrong value passed to updateScore function in unit tests for high-score-board at https://exercism.org/tracks/javascript/exercises/high-score-board exercise

It's seems that I didn't understand instruction. Sorry my bad.

If you have an idea how to improve the instructions please let us know.

authors: junedev slavict

repo: exercism/javascript


text:
Add list-ops exercise

Add list-ops exercise for 48in24

I've just updated and pushed the changes. Note, I ran configlet fmt which resulted in formatting changes in acronym's config.json.

repo: exercism/lfe


text:
Launch tracking

Edit this issue to keep track of the tasks you're working on towards launch.
We have a rough guide for how to launch a track, which is a good starting point;
please ask if you have any questions or if anything is confusing!
https://github.com/exercism/docs/blob/master/language-tracks/launch/README.md

Scripting fail. Sorry.

repo: exercism/request-new-language-track


text:
[WIP] Rebar3 - DO NOT MERGE

This does step by step move the exercises to rebar3.

exercises:

[x] accumulate
[x] allergies
[ ] atbash-cipher
[ ] anagram
[ ] bank-account
[ ] beer-song
[ ] binary
[ ] bob
[ ] circular-buffer
[ ] clock
[ ] difference-of-squares
[ ] etl
[ ] gigasecond
[ ] grade-school
[ ] grains
[ ] hamming
[ ] hello-world
[ ] largest-series-product
[ ] leap
[ ] luhn
[ ] meetup
[ ] nucleotide-count
[ ] parallel-letter-frequency
[ ] phone-number
[ ] rna-transcription
[ ] robot-simulator
[ ] scrabble-score
[ ] series
[ ] space-age
[ ] strain
[ ] sum-of-multiples
[ ] triangle
[ ] trinary
[ ] word-count
[ ] zipper

other

[ ] umbrella project
[ ] documentation
[ ] CI

FIXES #106

Note to self: I think I've broken something when I rebased...

repo: exercism/xerlang


text:
It does not work at all

I installed Keys-For-Sketch a couple of month ago. Since then Sketch was updated several times. But the Plugin never worked in any version.
I see the preferences tab. I can assign a shortcut. But the shortcut does not work all. Sketch still expects the default shortcuts.
System:

MacOS 10.11.6
Sketch 50.2.
Keys For Sketch 0.8.9

Steps to reproduce:

Assign CMD+Y to Edit>Redo

Expected result:

Pressing CMD+Y fires a Redo

Actual result:

Nothing happens. Sketch still expects SHIFT+CMD+Z

Hello! Thanks for the feedback.
Apparently something went wrong here with the latest Sketch releases. Since I'm not really interested in further plugin development right now I'm thinking about discontinuing of the project support.
Really sorry that I can't help with your problem. Hopefully, I'll update Readme with current project status shortly.

Thanks for the info!
I've just uninstalled the plugin for now and will file a feature request at Bohemian coding.

authors: conceptdeluxe exevil

repo: exevil/Keys-For-Sketch


text:
Deferred renderer setting not working

Unfortunately all I'm getting is a black screen, it works fine in forward rendering mode and the imgui stuff still renders, not sure why this is happening so figured I'd let you know.

What hardware are you running it on? (Also what OS/etc)

@JordanBlythe Any update on this?

Can't replicate the issue myself and have no other information to go on so I'm closing this issue for now.

authors: JordanBlythe exezin

repo: exezin/exengine


text:
Assertion error while trying to run AnswerSimilarity

Ragas version: 0.0.22
Python version: 3.10.12
IDE: Google Colab
I am trying the find out the similarity score between the ground truth and the answers. I am using the following code:
from datasets import load_dataset
from ragas.embeddings.base import HuggingfaceEmbeddings
from ragas.metrics import AnswerSimilarity

fiqa_eval = load_dataset("explodinggradients/fiqa", "ragas_eval")
embeddings = HuggingfaceEmbeddings(model_name="thenlper/gte-large")
answer_similarity = AnswerSimilarity()
results = answer_similarity.score(fiqa_eval['baseline'])

After some time, it is giving the following error:
AssertionError                            Traceback (most recent call last)
[<ipython-input-43-2cc7f45a2a25>](https://localhost:8080/#) in <cell line: 1>()
----> 1 results = answer_similarity.score(fiqa_eval['baseline'])
      2 results

2 frames
[/usr/local/lib/python3.10/dist-packages/ragas/metrics/base.py](https://localhost:8080/#) in score(self, dataset, callbacks)
     74         with trace_as_chain_group(f"ragas_{self.name}", callback_manager=cm) as group:
     75             for batch in tqdm(self.get_batches(len(dataset))):
---> 76                 score = self._score_batch(dataset.select(batch), callbacks=group)
     77                 scores.extend(score)
     78

[/usr/local/lib/python3.10/dist-packages/ragas/metrics/_answer_similarity.py](https://localhost:8080/#) in _score_batch(self, dataset, callbacks, callback_group_name)
     79             scores = np.array(self.embeddings.predict(inputs))
     80         else:
---> 81             embeddings_1 = np.array(self.embeddings.embed_documents(ground_truths))
     82             embeddings_2 = np.array(self.embeddings.embed_documents(answers))
     83             similarity = embeddings_1 @ embeddings_2.T

[/usr/local/lib/python3.10/dist-packages/ragas/embeddings/base.py](https://localhost:8080/#) in embed_documents(self, texts)
    143         )
    144
--> 145         assert isinstance(embeddings, Tensor)
    146         return embeddings.tolist()
    147

AssertionError:

How to fix this issue? Please advise.

Hey @jerilkuriakose , can you try installing ragas using pip install "ragas==0.1.0rc1" and follow this guide? https://docs.ragas.io/en/latest/howtos/customisations/embeddings.html
This should solve your issue.

closing this, feel free to reopen if issue persists

authors: jerilkuriakose jjmachan shahules786

repo: explodinggradients/ragas


text:
Integrity hash mismatches when downloading sharp-libvips package in expo/eas deployment pipeline

Build/Submit details page URL
https://expo.dev/accounts/rithmm/projects/rithmm-mobile/builds/83841b26-0738-4c10-832b-4956d99e831e
Summary
I'm consistently getting this integrity mismatch error when attempting to deploy an android build in the expo / eas development managed workflow.

Output of npm why sharp
sharp@0.32.1 dev
node_modules/appium-uiautomator2-driver/node_modules/sharp
  sharp@"^0.x" from appium-android-driver@5.12.1
  node_modules/appium-uiautomator2-driver/node_modules/appium-android-driver
    appium-android-driver@"^5.12.1" from appium-uiautomator2-driver@2.24.1
    node_modules/appium-uiautomator2-driver
      dev appium-uiautomator2-driver@"^2.12.7" from the root project

sharp@0.32.1 extraneous
node_modules/appium-xcuitest-driver/node_modules/sharp

sharp@0.32.1 dev
node_modules/sharp
  sharp@"0.32.1" from @appium/support@4.0.1
  node_modules/@appium/support
    @appium/support@"^4.0.1" from @appium/base-driver@9.3.10
    node_modules/@appium/base-driver
      @appium/base-driver@"^9.3.10" from @appium/base-plugin@2.2.10
      node_modules/@appium/base-plugin
        @appium/base-plugin@"^2.2.10" from appium@2.0.0-beta.71
        node_modules/appium
          dev appium@"^2.0.0-beta.57" from the root project
          peer appium@"^2.0.0-beta.48" from @appium/typedoc-plugin-appium@0.6.4
          node_modules/@appium/typedoc-plugin-appium
            @appium/typedoc-plugin-appium@"^0.6.4" from @appium/docutils@0.3.13
            node_modules/@appium/docutils
              @appium/docutils@"^0.3.13" from appium@2.0.0-beta.71
          peer appium@"^2.0.0-beta.40" from appium-uiautomator2-driver@2.24.1
          node_modules/appium-uiautomator2-driver
            dev appium-uiautomator2-driver@"^2.12.7" from the root project
          peer appium@"^2.0.0-beta.48" from @appium/typedoc-plugin-appium@0.6.3
          node_modules/appium-uiautomator2-driver/node_modules/@appium/typedoc-plugin-appium
            @appium/typedoc-plugin-appium@"^0.6.3" from @appium/docutils@0.3.9
            node_modules/appium-uiautomator2-driver/node_modules/@appium/docutils
          peer appium@"^2.0.0-beta.40" from appium-android-driver@5.12.1
          node_modules/appium-uiautomator2-driver/node_modules/appium-android-driver
            appium-android-driver@"^5.12.1" from appium-uiautomator2-driver@2.24.1
            node_modules/appium-uiautomator2-driver
              dev appium-uiautomator2-driver@"^2.12.7" from the root project
      @appium/base-driver@"^9.3.10" from appium@2.0.0-beta.71
      node_modules/appium
        dev appium@"^2.0.0-beta.57" from the root project
        peer appium@"^2.0.0-beta.48" from @appium/typedoc-plugin-appium@0.6.4
        node_modules/@appium/typedoc-plugin-appium
          @appium/typedoc-plugin-appium@"^0.6.4" from @appium/docutils@0.3.13
          node_modules/@appium/docutils
            @appium/docutils@"^0.3.13" from appium@2.0.0-beta.71
        peer appium@"^2.0.0-beta.40" from appium-uiautomator2-driver@2.24.1
        node_modules/appium-uiautomator2-driver
          dev appium-uiautomator2-driver@"^2.12.7" from the root project
        peer appium@"^2.0.0-beta.48" from @appium/typedoc-plugin-appium@0.6.3
        node_modules/appium-uiautomator2-driver/node_modules/@appium/typedoc-plugin-appium
          @appium/typedoc-plugin-appium@"^0.6.3" from @appium/docutils@0.3.9
          node_modules/appium-uiautomator2-driver/node_modules/@appium/docutils
        peer appium@"^2.0.0-beta.40" from appium-android-driver@5.12.1
        node_modules/appium-uiautomator2-driver/node_modules/appium-android-driver
          appium-android-driver@"^5.12.1" from appium-uiautomator2-driver@2.24.1
          node_modules/appium-uiautomator2-driver
            dev appium-uiautomator2-driver@"^2.12.7" from the root project
    @appium/support@"^4.0.1" from @appium/base-plugin@2.2.10
    node_modules/@appium/base-plugin
      @appium/base-plugin@"^2.2.10" from appium@2.0.0-beta.71
      node_modules/appium
        dev appium@"^2.0.0-beta.57" from the root project
        peer appium@"^2.0.0-beta.48" from @appium/typedoc-plugin-appium@0.6.4
        node_modules/@appium/typedoc-plugin-appium
          @appium/typedoc-plugin-appium@"^0.6.4" from @appium/docutils@0.3.13
          node_modules/@appium/docutils
            @appium/docutils@"^0.3.13" from appium@2.0.0-beta.71
        peer appium@"^2.0.0-beta.40" from appium-uiautomator2-driver@2.24.1
        node_modules/appium-uiautomator2-driver
          dev appium-uiautomator2-driver@"^2.12.7" from the root project
        peer appium@"^2.0.0-beta.48" from @appium/typedoc-plugin-appium@0.6.3
        node_modules/appium-uiautomator2-driver/node_modules/@appium/typedoc-plugin-appium
          @appium/typedoc-plugin-appium@"^0.6.3" from @appium/docutils@0.3.9
          node_modules/appium-uiautomator2-driver/node_modules/@appium/docutils
        peer appium@"^2.0.0-beta.40" from appium-android-driver@5.12.1
        node_modules/appium-uiautomator2-driver/node_modules/appium-android-driver
          appium-android-driver@"^5.12.1" from appium-uiautomator2-driver@2.24.1
          node_modules/appium-uiautomator2-driver
            dev appium-uiautomator2-driver@"^2.12.7" from the root project
    @appium/support@"^4.0.1" from @appium/docutils@0.3.13
    node_modules/@appium/docutils
      @appium/docutils@"^0.3.13" from appium@2.0.0-beta.71
    @appium/support@"^4.0.1" from appium@2.0.0-beta.71
    node_modules/appium
      dev appium@"^2.0.0-beta.57" from the root project
      peer appium@"^2.0.0-beta.48" from @appium/typedoc-plugin-appium@0.6.4
      node_modules/@appium/typedoc-plugin-appium
        @appium/typedoc-plugin-appium@"^0.6.4" from @appium/docutils@0.3.13
        node_modules/@appium/docutils
          @appium/docutils@"^0.3.13" from appium@2.0.0-beta.71
      peer appium@"^2.0.0-beta.40" from appium-uiautomator2-driver@2.24.1
      node_modules/appium-uiautomator2-driver
        dev appium-uiautomator2-driver@"^2.12.7" from the root project
      peer appium@"^2.0.0-beta.48" from @appium/typedoc-plugin-appium@0.6.3
      node_modules/appium-uiautomator2-driver/node_modules/@appium/typedoc-plugin-appium
        @appium/typedoc-plugin-appium@"^0.6.3" from @appium/docutils@0.3.9
        node_modules/appium-uiautomator2-driver/node_modules/@appium/docutils
      peer appium@"^2.0.0-beta.40" from appium-android-driver@5.12.1
      node_modules/appium-uiautomator2-driver/node_modules/appium-android-driver
        appium-android-driver@"^5.12.1" from appium-uiautomator2-driver@2.24.1
        node_modules/appium-uiautomator2-driver
          dev appium-uiautomator2-driver@"^2.12.7" from the root project

Output of npm why sharp-libvips:

Why would this error consistently occur in my android build but not my ios build?  Do I have control over whether the checksums match?  I contacted the authors of sharp-libvips and just said it had to be some kind of connection issue, but that the sha512 hash returned means zero file length, so that's a clue.
https://github.com/lovell/sharp-libvips/issues/183#issuecomment-1555984111
https://github.com/lovell/sharp-libvips/issues/183#issuecomment-1556148423
What I've tried:

Played around with node versions, went from 16 to 18 which fixed the issue with ios, but not for android
Clearing cache and retrying

Managed or bare?
bare
Environment
expo-env-info 1.0.5 environment info:
    System:
      OS: macOS 13.3.1
      Shell: 5.9 - /bin/zsh
    Binaries:
      Node: 16.17.0 - ~/.nvm/versions/node/v16.17.0/bin/node
      Yarn: 1.22.19 - /opt/homebrew/bin/yarn
      npm: 8.15.0 - ~/.nvm/versions/node/v16.17.0/bin/npm
      Watchman: 2023.01.30.00 - /opt/homebrew/bin/watchman
    Managers:
      CocoaPods: 1.11.2 - /usr/local/bin/pod
    SDKs:
      iOS SDK:
        Platforms: DriverKit 22.4, iOS 16.4, macOS 13.3, tvOS 16.4, watchOS 9.4
      Android SDK:
        API Levels: 28, 31, 33
        Build Tools: 30.0.3, 33.0.0
        System Images: android-33 | Google APIs ARM 64 v8a, android-UpsideDownCake-ext5 | Google Play ARM 64 v8a
    IDEs:
      Android Studio: 2022.1 AI-221.6008.13.2211.9619390
      Xcode: 14.3/14E222b - /usr/bin/xcodebuild
    npmPackages:
      @expo/metro-config: ^0.3.22 => 0.3.22
      expo: ~48.0.15 => 48.0.17
      react: 18.2.0 => 18.2.0
      react-dom: 18.2.0 => 18.2.0
      react-native: 0.71.8 => 0.71.8
      react-native-web: ~0.18.7 => 0.18.12
    npmGlobalPackages:
      eas-cli: 3.9.0
    Expo Workflow: bare

Error output
[stderr]
npm ERR! path /home/expo/workingdir/build/node_modules/sharp
[stderr]
npm ERR! command failed
[stderr]
npm ERR! command sh -c (node install/libvips && node install/dll-copy && prebuild-install) || (node install/can-compile && node-gyp rebuild && node install/dll-copy)
[stderr]
npm ERR! sharp: Downloading https://github.com/lovell/sharp-libvips/releases/download/v8.14.2/libvips-8.14.2-linux-x64.tar.br
[stderr]
npm ERR! sharp: Integrity expected: sha512-wjCKmWfBb0uz1UB7rPDLvO0s+VWuoAY/Vv/YGCRFEQUkdSLQUgHExrOMMbOM3FleuYfQqznDYCXXphkl7X44+w==
[stderr]
npm ERR! sharp: Integrity received: sha512-tGlsuQf/hwneexwpCLWr93OYIWh6b4cyVZ4sQuuuKE7qJ6SdLbU+ryJUYW0O8rtDeW7h/V2dBxrSsguWbgaNfA==
[stderr]
npm ERR! sharp: Please see https://sharp.pixelplumbing.com/install for required dependencies
[stderr]
npm ERR! sharp: Installation error: Integrity check failed for linux-x64
[stderr]
npm ERR! A complete log of this run can be found in:
[stderr]
npm ERR!
[stderr]
/home/expo/.npm/_logs/2023-05-22T17_20_34_291Z-debug-0.log

Reproducible demo or steps to reproduce from a blank project
n/a

Same problem here, weird part here is that it's not happening every Android build but more times than it being coincidentally. It does not happen on iOS builds.

Yarn workspaces
Managed

getting this error, were you able to solve it?

I believe it was an issue with our NPM cache that should be resolved now. If the issue reappears feel free to open a new issue!

authors: MarcK98 jbreemhaar ladyshaitan szdziedzic

repo: expo/eas-cli


text:
Missing parentBundleId for app clip target causes failure when updating credentials

Build/Submit details page URL
No response
Summary
I'm getting an error when running eas credentials on a prebuilt iOS project which includes an App Clip target. Updating the provisioning profile for the App Clip target fails with the following error:
✖ Failed to sync capability identifiers com.my-app.appclip
UnexpectedAppleResponse: Relationship is required but was not provided. - The relationship 'parentBundleId' is required but was not provided with this request.
Relationship is required but was not provided. - The relationship 'parentBundleId' is required but was not provided with this request.

I have several extension targets in our iOS project (added using @EvanBacon 's expo-apple-targets plugin):

a notification service extension,
a notification content extension,
an app clip

If I prebuild the Xcode project with only the notification service and content extensions, eas credentials completes without issues.
I get the above error only if the project includes the app clip target.
It seems that the App Store Connect API is returning an error response because a parentBundleId is not specified when executing BundleId.updateBundleIdCapabilityAsync() for the app clip bundle identifier. Since @expo/apple-utils is a private repo, I can't really see what's going on there.
The com.apple.developer.parent-application-identifiers key in my app clip's entitlements is also set to $(AppIdentifierPrefix)com.my-app.
Any help would be much appreciated.
Managed or bare?
Bare
Environment
  expo-env-info 1.0.5 environment info:
    System:
      OS: macOS 13.5.2
      Shell: 5.9 - /bin/zsh
    Binaries:
      Node: 18.16.0 - ~/.n/bin/node
      Yarn: 1.22.19 - ~/code/my_app/node_modules/.bin/yarn
      npm: 9.5.1 - ~/.n/bin/npm
      Watchman: 2023.04.10.00 - /opt/homebrew/bin/watchman
    Managers:
      CocoaPods: 1.11.3 - /Users/me/.rbenv/shims/pod
    SDKs:
      iOS SDK:
        Platforms: DriverKit 22.4, iOS 16.4, macOS 13.3, tvOS 16.4, watchOS 9.4
    IDEs:
      Android Studio: 2022.1 AI-221.6008.13.2211.9514443
      Xcode: 14.3.1/14E300c - /usr/bin/xcodebuild
    npmPackages:
      expo: ^49.0.7 => 49.0.7
      react: 18.2.0 => 18.2.0
      react-native: 0.72.3 => 0.72.3
    npmGlobalPackages:
      eas-cli: 5.2.0
      expo-cli: 6.3.2
    Expo Workflow: bare

Expo Doctor:
✔ Validating global prerequisites versions
✔ Checking for incompatible packages
✔ Verifying prebuild support package versions are compatible
✔ Checking dependency versions for compatibility with the installed Expo SDK
✔ Validating Expo Config

Didn't find any issues with the project!

Error output
✖ Failed to sync capability identifiers com.my-app.appclip
UnexpectedAppleResponse: Relationship is required but was not provided. - The relationship 'parentBundleId' is required but was not provided with this request.
Relationship is required but was not provided. - The relationship 'parentBundleId' is required but was not provided with this request.
UnexpectedAppleResponse: Relationship is required but was not provided. - The relationship 'parentBundleId' is required but was not provided with this request.
    at o.parseResponse (/Users/me/.n/lib/node_modules/eas-cli/node_modules/@expo/apple-utils/build/index.js:1:742952)
    at o.requestAndParseAsync (/Users/me/.n/lib/node_modules/eas-cli/node_modules/@expo/apple-utils/build/index.js:1:741637)
    at processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async o.fetchSingleModelAsync (/Users/me/.n/lib/node_modules/eas-cli/node_modules/@expo/apple-utils/build/index.js:1:741360)
    at async o.patchModelAsync (/Users/me/.n/lib/node_modules/eas-cli/node_modules/@expo/apple-utils/build/index.js:1:741466)
    at async l.updateBundleIdCapabilityAsync (/Users/me/.n/lib/node_modules/eas-cli/node_modules/@expo/apple-utils/build/index.js:1:802110)
    at async syncCapabilityIdentifiersForEntitlementsAsync (/Users/me/.n/lib/node_modules/eas-cli/build/credentials/ios/appstore/capabilityIdentifiers.js:104:9)
    at async syncCapabilityIdentifiersAsync (/Users/me/.n/lib/node_modules/eas-cli/build/credentials/ios/appstore/ensureAppExists.js:91:37)
    at async syncCapabilitiesAsync (/Users/me/.n/lib/node_modules/eas-cli/build/credentials/ios/appstore/ensureAppExists.js:80:5)
    at async ensureBundleIdExistsWithNameAsync (/Users/me/.n/lib/node_modules/eas-cli/build/credentials/ios/appstore/ensureAppExists.js:58:9)

Reproducible demo or steps to reproduce from a blank project

Running into the same issue when attempting to build a project with an app clip target.

Same issue here!!!

same issue

is there a solution....

I had the same issue. In my case, deleting the ios directory generated by npx expo prebuild resolved it 👍

We are experiencing the same issue. Any help would be appreciated.  @AlexandreFauchard deleting the ios folder and re-generating by npx expo prebuild also does not work. @haoliangz @Lurtroxx and @philtre Any alternatives?

authors: AlexandreFauchard Lurtroxx haoliangz joshidhruv philtre szpasztor


text:
[18/n][eas-cli] Remove unused arguments in some context util functions

Checklist

[ ] I've added an entry to CHANGELOG.md if necessary. You can comment this pull request with /changelog-entry [breaking-change|new-feature|bug-fix|chore] [message] and CHANGELOG.md will be updated automatically.

Why
These arguments are unused in the production callsites, so remove them.
How
Remove unused args.
Test Plan
Run tests and tsc.

Abandoning this one.


text:
feat: restore passOnConnectionError option

This PR closes #190.
It works like a charm with an ioredis client. However, the node-redis client is a bit stubborn when it comes to reconnecting - it waits for the server to reconnect forever. If you use a custom retryStrategy that tells it to stop after x retries, it will stop and not attempt to reconnect, even during the next time increment is called. I haven't yet figured out a workaround for that.

@nfriedly @abhijeetviswa Please do review this PR and let me know if I should make any changes.

Oh all right that makes sense

repo: express-rate-limit/rate-limit-redis


text:
Cors error when connecting through ssh tunnel

I often want to test my apis on a staging server. I use a ssh tunnel to connect with my frontend. Even if I for example allow localhost:3000, I still get cors error. If I use a reverse proxy with a domain etc. the same api connects to my local frontend without problems
Does anyone know how why this happens and how to solve this problem? Can it be a bug in the package?
Thank you

Hi @Hoss3770! Thanks for reporting this bug. Can you provide a reproducible bug so we can investigate it?

repo: expressjs/cors


text:
Try from err typos

Fixes minor typographical errors for the following conversions and adds corresponding integration tests:

TryFrom for Vec was Error::ExpectedInteger and is not Error::ExpectedReal
From<HashMap<String, Robj>> was missing, though &str impl existed

I did not fix the misspelling 'Enviroment' throughout extendr-api since it does not actually produce errors.
R documentation quashed for the conversion test functions.

Apologies for being picky. I think the hashmap code needs to be its own separate PR, and it probably needs some discussion first in an issue. It's not clear to me that we want to always convert a hashmap into a list, as opposed to an environment.
And for a PR that fixes spelling and other minor issues (such as @noRd tags) I think it should also fix the spelling of environment.
Finally, the integration tests are failing because R check notices that there are no man pages. I think @usage NULL will fix this. (But not entirely certain. I just know somehow it's possible to suppress documentation.)

Your comments make sense and aren't too picky. I agree discussing hashmap is reasonable. The lack of From HashMap<String, Robj> seemed to someone new on the project to be simply an oversight given existing From,TryFrom implementations for HashMap with &str and String keys.
Will implement your suggestions and resubmit. Thanks

I've opened an issue about hasmaps: #230

recent upstream commits here, and

removal of HashMap<String, Robj> impl fix from previous push
Rd files suppressed with @usage NULL for all conversion test functions
Enviroment typo fixed throughout extendr-api
maintains fix for typo in TryFrom error type in double_vec

It's starting to look good, but there are some changes that don't seem to belong (the change in the changelog, the hashmap code). Overall, from experience, I'd say once you have more than a handful of commits chances are something went wrong and you'd be better off starting over. Also, never rebase, just merge in the main tree.
The tests fail because there's a formatting error. I'll flag it.

It's possible that a lot of things will be fixed if you just merge in master.

hmm, so i did not make these changes or most of the others below --- they come from the previous commits made yesterday (re: #226) and which i pulled this afternoon to avoid merge conflicts. the same is true from the below.
to your main point: it would have been cleaner to start over.
nonetheless, thank you for the time here, and please do let me know the preference in situations like this.

It's possible that a lot of things will be fixed if you just merge in master.

yes, will do

@clauswilke To clean up this git history mess a bit my plan is to merge to master on my fork and have the PR point there. I've not done that before as I typically am a maintainer on projects I work on. If doing so, with some loss of the commit history, is undesirable please do let me know. Trying to reduce the amount of nonsense I produce for review here going forward. Thanks again

Yes, all you have to do is merge master into your current branch and then push. The PR should update and GitHub should then only register the changes since master.
The history doesn't matter because when we merge the PR we squash. It's another reason why each PR should be one single issue only; it's going to be only one commit on the master branch.

I think this looks good now. Could you try to merge in master so we no longer see the changes that aren't actually part of your PR?

great, thanks for the comments all.
what follows is rather tedious. TLDR summary is that i can reopen a PR to reset history, switch the PR base branch and back to trick github, or do nothing. the PR merge shouldn't associate the unrelated commits to this PR, as the history displayed here is a cosmetic feature of github apparently.
on the commit history from upstream/master that isn't mine but appears here:
i did indeed merge my branch into origin/master (my fork master), but the issue of github showing commits from upstream/master appears to be a github issue. see this long-standing thread, still active:
https://stackoverflow.com/questions/16306012/github-pull-request-showing-commits-that-are-already-in-target-branch#26986320
annoying, though it seems this issue is mostly cosmetic since you will squash this PR's commits anyway.
i see a few options and am happy to do what is easiest or best from your perspective:

try one of the hacks listed above, such as switching PR base branch to something else and back. one person suggested this adds more history, so i did not just do it.

open a new PR and close this one, which should reset the history.

rebase to squash all commits into one and re-push. i am hesitant to do this as I am unsure whether this will make it appear as though i have done someone else's work. i don't believe so --- again, this commit history is a github display issue not a git issue ---- but am unsure.

I think we should try to get this right, most importantly so you've got the workflow down in the future, and also because if I merge now I'm quite certain it'll look like @yutannihilation co-authored the PR.
In brief, I think this is where you went wrong:

i did indeed merge my branch into origin/master (my fork master),

You need to merge upstream master into your branch, but you should not touch your fork master.
In general, the workflow that works is:

Make a fork of the project
Check out the fork and make a branch for development
Make commits, then push (the first time with git push --set-upstream origin <branch>)
Then make a PR
If changes are needed, make more commits and push
If the PR can't be merged because of a conflict, fetch upstream, merge upstream/master into your branch, fix conflicts, and push
Repeat 5 and 6 until ready for merge

looks like a new PR is the cleanest solution i think. if you would prefer, i could squash the history into one commit, with me as author.

In brief, I think this is where you went wrong:

in case this is a reference to my future self or others: i should have been more clear. i did that only after the previous commit history from origin/master had shown up in this PR, so it cannot be the cause, at least not this time.
but your comment is still valid, i think, in broad terms: these errant commits, which were updates to origin/master while this PR was ongoing, showed up after i merged upstream/master into origin/master then into my branch, rather than merging upstream/master directly into my branch. otherwise, i followed your steps 1-7. step 6 was the key here, in other words. noted.

looks like a new PR is the cleanest solution i think. if you would prefer, i could squash the history into one commit, with me as author.

Whichever is easier for you. I don't particularly care. We squash when we merge into master.

ok, this should fix things. thanks for the back and forth.

CI failures on R-devel runner are probably irrelevant to this pull request, so please ignore (probably due to the recent API change on R-devel, which itself is a bit worrisome...).
  error[E0425]: cannot find function, tuple struct or tuple variant `SET_PRSEEN` in this scope
      --> extendr-api/src/wrapper/promise.rs:27:13
       |
  27   |             SET_PRSEEN(sexp, 0);
       |             ^^^^^^^^^^ help: a function with a similar name exists: `SET_PRENV`
       |
      ::: /home/runner/work/extendr/extendr/target/debug/build/libR-sys-fe61ba3184160aea/out/bindings.rs:4969:5
       |
  4969 |     pub fn SET_PRENV(x: SEXP, v: SEXP);
       |     ----------------------------------- similarly named function `SET_PRENV` defined here

I'm still confused by the hashmap situation but I'm going to merge since this contains many useful fixes. We can sort out the hashmap in future PRs.

repo: extendr/extendr


text:
Gitlab CI variables provider

You can store secret values as CI variables in gitlab, and we can retrieve them through the API. We can have a provider using this as a store. In the old CS solution we had a provider implementing this: https://github.com/ContainerSolutions/externalsecret-operator/tree/master/pkg/gitlab

@knelasevero this is fixed by https://github.com/external-secrets/external-secrets/pull/319 isn't it?

authors: alekc knelasevero

repo: external-secrets/external-secrets


text:
Adding dependency license checks in CI

Fixes #993
Signed-off-by: Gustavo Carvalho gustavo.carvalho@container-solutions.com

This was open to test how CI will play. If it works, I'll add a specific job to it.

Note: check-diff is only failing because I did tamper with go.mod so you can see the DLC workflow in action :). I'll fix it after you approve it.

/approve

I'm merging this to test it live with the 1password provider :eyes:. I got the idea how it works so if you think we need to improve something, we can track it afterwards

/merge

authors: gusfcarvalho knelasevero


text:
Moving the repository to a new org broke helm repo.

https://godaddy.github.io/kubernetes-external-secrets/index.yaml is now returning 404, which breaks all deployments depending on the chart repo.
https://external-secrets.github.io/kubernetes-external-secrets/index.yaml now hosts repo, but I don't see any documentation or warning of this breaking change.

#554 tracks move related issues and readme has been updated with new repo and notice.

authors: Flydiverny voldemortensen


text:
Tooltips are not working for

I refer to the example page:
https://github.com/extnet/examples.ext.net/blob/3d91a9ceb02164adcff2ff9ded69c6c1ed09a9e0/src/Pages/samples/layout/formlayout/overview/index.cshtml#L52-L54
Live:
https://examples.ext.net/#/layout/formlayout/overview
In the form the expected tooltips are not showing up.
Can you provide a fix or workaround, please?

Ext.NET 7's support for the datatip plugin was not implemented. The code including the plugin to the sample is commented out because it couldn't make it in time of the release.
Unfortunately at this time there's no fix for that other than actually porting the plugin implementation from Ext.NET 5.
We have created issue extnet/Ext.NET#1867 to track the implementation of this plug in, so you may want to subscribe to it to get an update when the support is implemented.

authors: ALVIS-Software fabriciomurta


text:
🛑 Bilge is down

In 9a666b4, Bilge (https://bilge.world) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Bilge is back up in 27a3750.

repo: extratone/up