Compilation and empty topic problems

Hi, i am facing a few errors while running the package.

First, when i try to compile i get this error:

Starting >>> umrr_ros2_msgs
Starting >>> SensorSimulator
--- stderr: SensorSimulator
/usr/bin/ld: cannot find -lcom_lib
/usr/bin/ld: cannot find -losal
/usr/bin/ld: cannot find -lumrr11_t132_automotivev1.1.1_user_interface
/usr/bin/ld: cannot find -lumrr96_t153_automotivev1.2.1_user_interface
collect2: error: ld returned 1 exit status
make[2]: *** [CMakeFiles/simulator.dir/build.make:84: simulator] Error 1
make[1]: *** [CMakeFiles/Makefile2:76: CMakeFiles/simulator.dir/all] Error 2
make: *** [Makefile:130: all] Error 2
---
Failed   <<< SensorSimulator [0.06s, exited with code 2]
Aborted  <<< umrr_ros2_msgs [2.40s]

Summary: 0 packages finished [2.53s]
  1 package failed: SensorSimulator
  1 package aborted: umrr_ros2_msgs
  1 package had stderr output: SensorSimulator
  1 package not processed

I remove the simulator file and it did not give any error while  building. Is this file neseccary to launch node?

Then, I run into another problem when I try to launch node. The topic is not visualized on the Rviz screen. When I listen to the topic from the terminal, no message appears in it. I configure the  radar.template.yaml file like this:

---
/**:
  ros__parameters:
    # The client_id to be set in smart_access_config.json, must be a unique integer.
      master_client_id: 1
      # This sets the dev_id in the hw_inventory.json
      hw_dev_id: 2
      # This sets the port in the hw_inventory.json
      hw_port: 55555
      # This sets the iface_name in the hw_inventory.json
      hw_iface_name: "enp46s0"
      # An array of sensors to subscribe to.
      sensors:
          # As many as 10 sensors all named as "sensor_<number>" in increasing order of numbers,
          # e.g., sensor_0, sensor_1, etc. The list must start with sensor_0.
          sensor_0:
              # The model of the connected sensor.
              model: "umrr96"
              # The client_id of the sensor/source, must be a unique integer.
              id: 100
              # The ip address of the sensor or of the source acting as a sensor.
              ip: "<IP_ADDRESS>"
              # The port to be used.
              port: 55555
              # The frame_id to be set to the published messages.
              frame_id: "umrr"
              # Specify the history size.
              history_size: 10

When I launch the node, there is no error in the terminal:
ros2 launch umrr_ros2_driver radar_rviz.launch.py
[INFO] [launch]: All log files can be found below /home/nilay/.ros/log/2022-09-13-16-21-37-764950-nilay-40151
[INFO] [launch]: Default logging verbosity is set to INFO
[INFO] [smartmicro_radar_node_exe-1]: process started with pid [40153]
[INFO] [rviz2-2]: process started with pid [40155]
[rviz2-2] [INFO] [1663075298.036421287] [rviz2]: Stereo is NOT SUPPORTED
[rviz2-2] [INFO] [1663075298.036529534] [rviz2]: OpenGl version: 4.6 (GLSL 4.6)
[rviz2-2] [INFO] [1663075298.052637901] [rviz2]: Stereo is NOT SUPPORTED
[smartmicro_radar_node_exe-1] [INFO] [1663075299.831572927] [smartmicro_radar_node]: Radar services are ready.

Do you think there is an error in the parameters in the .yaml file? I would be very grateful if you could help, thank you.

@NilaySener
Hey,
For the first part, the SensorSimulator is not a ros2 package and hence the output. In order to compile the driver and its resources you need to give the following command:
colcon build --packages-select umrr_ros2_driver umrr_ros2_msgs.
For the second part regarding the parameters, yes, there is an issue that I see. The ip address that you have to specify is that of the sensor and not of the interface of your pc/machine. Assuming you are using the default ip address of the sensor(<IP_ADDRESS>) and your interface(<IP_ADDRESS>). You need to set the ip address of the sensor i.e <IP_ADDRESS> in the param file.

Please make sure the interface that you have specified in the param file enp46s0 is configured to be on the same subnet as the sensor. For instance in your case should be configured to <IP_ADDRESS> and also make sure that you are able to ping the sensor.

@smartSRA
Hi, it might be a solution to add a COLCON_IGNORE into the simulator folder. It would make the build process more convenient. Especially, if the Smartmicro driver is integrated into a ROS workspace with other packages.

Yes, i can ping the sensor from terminal and also using wireshark. I verfied the interface name also using ifconfig. You can also see the outputs i mentioned:
nilay@nilay:~$ ifconfig
br-a93efd67668a: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        inet <IP_ADDRESS>  netmask <IP_ADDRESS>  broadcast <IP_ADDRESS>
        ether 02:42:58:91:1a:59  txqueuelen 0  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

docker0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        inet <IP_ADDRESS>  netmask <IP_ADDRESS>  broadcast <IP_ADDRESS>
        inet6 fe80::42:eaff:fe84:3790  prefixlen 64  scopeid 0x20<link>
        ether 02:42:ea:84:37:90  txqueuelen 0  (Ethernet)
        RX packets 34344  bytes 1829616 (1.8 MB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 43138  bytes 220894429 (220.8 MB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

enp46s0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        ether b0:25:aa:4b:c3:01  txqueuelen 1000  (Ethernet)
        RX packets 196016  bytes 47569163 (47.5 MB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 15402  bytes 2764769 (2.7 MB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet <IP_ADDRESS>  netmask <IP_ADDRESS>
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 1000  (Local Loopback)
        RX packets 772277  bytes 100355364 (100.3 MB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 772277  bytes 100355364 (100.3 MB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

wlo1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet <IP_ADDRESS>  netmask <IP_ADDRESS>  broadcast <IP_ADDRESS>
        inet6 fe80::eff8:1f6e:b27d:458c  prefixlen 64  scopeid 0x20<link>
        ether 5c:e4:2a:8c:a3:16  txqueuelen 1000  (Ethernet)
        RX packets 1332049  bytes<PHONE_NUMBER> (1.6 GB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 562026  bytes 83333699 (83.3 MB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

nilay@nilay:~$ ping <IP_ADDRESS>
PING <IP_ADDRESS> (<IP_ADDRESS>) 56(84) bytes of data.
64 bytes from <IP_ADDRESS>: icmp_seq=1 ttl=128 time=0.228 ms
64 bytes from <IP_ADDRESS>: icmp_seq=2 ttl=128 time=0.293 ms
64 bytes from <IP_ADDRESS>: icmp_seq=3 ttl=128 time=0.299 ms
64 bytes from <IP_ADDRESS>: icmp_seq=4 ttl=128 time=3.55 ms
64 bytes from <IP_ADDRESS>: icmp_seq=5 ttl=128 time=0.289 ms
^C
--- <IP_ADDRESS> ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4062ms
rtt min/avg/max/mdev = 0.228/0.932/3.551/1.309 ms

COLCON_IGNORE

Hey @markusschratter ,
I was aware of AMENT_IGNORE but did not know of COLCON_IGNORE. This is great. Thanks for the tip!

@NilaySener
You have not configured(assigned an ip address) your interface:

As I have previously mentioned you need to configure your interface. Set it to the default of <IP_ADDRESS>.

@smartSRA its because of i cut the power of the radar at that time.
enp46s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet <IP_ADDRESS>  netmask <IP_ADDRESS>  broadcast <IP_ADDRESS>
        inet6 fe80::d5ac:3bd9:d725:37d1  prefixlen 64  scopeid 0x20<link>
        ether b0:25:aa:4b:c3:01  txqueuelen 1000  (Ethernet)
        RX packets 244264  bytes 59738112 (59.7 MB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 16854  bytes 3261241 (3.2 MB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

Unfortunately the topic is still empty.

@smartSRA I would also like to mention that with my current configurations, I can visualize the data that comes with the Windows interface of the device, DriveRecorder3. Based on this situation, I can say that my hardware connections are OK.

@smartSRA
Hi,
no problem! COLCON_IGNORE is sometimes useful! ;)
I have the same issues and do not receive data with version v2.1.0. Wireshark shows packages on port 55555.

We use following configuration for the radars:

The ROS2 parameters are correct set. I only observed following behaviour for parameeter iface_name, which can not be set in the param.yaml:
ros2 param get /smartmicro_radar_node sensors.sensor_0.iface_name
String value is: lo

Is this correct?

@smartSRA I would also like to mention that with my current configurations, I can visualize the data that comes with the Windows interface of the device, DriveRecorder3. Based on this situation, I can say that my hardware connections are OK.

Hey,
Could you kindly attach your syslog and wireshark dump so I can have a look in detail?

@smartSRA Hi, no problem! COLCON_IGNORE is sometimes useful! ;)
I have the same issues and do not receive data with version v2.1.0. Wireshark shows packages on port 55555.
We use following configuration for the radars:
The ROS2 parameters are correct set. I only observed following behaviour for parameeter iface_name, which can not be set in the param.yaml:
ros2 param get /smartmicro_radar_node sensors.sensor_0.iface_name
String value is: lo

Is this correct?

Yes, your param look fine and the traffic in the dump is also fine. Could you also provide me with the syslogs?
Regarding the sensor interface, yes it should not make a difference.

@NilaySener @markusschratter Could you both tell me which sensor firmware are you using?

@NilaySener I see that the sensor is not responding.
Which sensor firmware do you have for UMRR96 T153?
The aktuell release of the driver requires firmware bundle UMRR96-T153: V5.2.4 for the sensor. Could you verify this?

@NilaySener I see that the sensor is not responding.
Which sensor firmware do you have for UMRR96 T153?
The aktuell release of the driver requires firmware bundle UMRR96-T153: V5.2.4 for the sensor. Could you verify this?

OK, where can i check the firmware version of my sensor?

It should be provided to you along with the other documents from our support team. If not you can get it using the DriveRecorder tool by sending the sensor a get status request (major,minor,patch) or you could contact our support an ask them to provide you with the firmware bundle UMRR96-T153: V5.2.4 and if using UMRR11-T132: V5.1.4 and flash your sensor using the DriveRecorder with the new firmware.

@NilaySener I see that the sensor is not responding.
Which sensor firmware do you have for UMRR96 T153?
The aktuell release of the driver requires firmware bundle UMRR96-T153: V5.2.4 for the sensor. Could you verify this?

I checked the version and it was V4.1.1, I could update the V5.2.2 and still got the same results. I guess V.5.2.2 is not compatible either. Now, I will try to change it when I receive the V5.2.4 firmware. I will update here soon.

I had this same problem - I couldn't communicate with my sensor because it had an outdated firmware (V5.2.2).  I updated to firmware V5.2.4 and the problem was solved.
I would highly recommend mentioning this firmware dependency in the README of this repository.  I would also recommend mentioning that by default the destination device must be configured to have IP address <IP_ADDRESS> to communicate with the sensor, unless the sensor's default settings are changed.  Both these items caused me much headache and back-and-forth with support.

Great! yes, I've observed a lot of people are having the same issue actually I was not aware that our support has been giving out the old sensor firmware.
I'll update this in the Readme so others can verify.

I had this same problem - I couldn't communicate with my sensor because it had an outdated firmware (V5.2.2). I updated to firmware V5.2.4 and the problem was solved.
I would highly recommend mentioning this firmware dependency in the README of this repository. I would also recommend mentioning that by default the destination device must be configured to have IP address <IP_ADDRESS> to communicate with the sensor, unless the sensor's default settings are changed. Both these items caused me much headache and back-and-forth with support.

Hi, I tested the package after updating the firmware and the problem was solved. Thank you for helping!


changed Condition.enabled to Condition.visible in list interaction steps

Coverage increased (+0.03%) to 80.938% when pulling 86bb92b0740ac68b6af9e79ff4579c94bab4394d on GannaChernyshova:master into 6f9cbfbe9944ca160f580382a9be368cf7d6e4e1 on alfa-laboratory:master.


Add "pub uninstall"

This issue was originally filed by<EMAIL_ADDRESS>
It'd be nice if pub had an uninstall command. For instance, if you make a copy of a pub package, all the symlinks get messed up. Hence, I usually delete all the packages symlinks and the directory and the pubspec.lock. It'd be neat if "pub uninstall" could do that for me.
Dart Editor version 0.2.7_r15699
Dart SDK version <IP_ADDRESS>_r15699

This issue has been moved to dart-lang/pub#339.


Provide error message along with job status

When the job status is reported back by the Agent the status message (if provided) is persistently stored. It is then provided to any clients that request the status of a job.

Looks good! just added a small fix to previous code.


[JFG-1067] Separate Master - JaaS/Env and Master - JaaS/Execution communication

fixed all comments


UI: Add pagination to Select component

What
We want to add pagination to the current Select component.

Implementation could leverage something like: https://www.npmjs.com/package/react-select-async-paginate

We want to achieve something like: https://codesandbox.io/s/o75rno2w65?file=/src/index.js

There is a naive implementation for this here: https://github.com/medusajs/admin/blob/master/src/domain/products/filter-dropdown.tsx#L77
But would definitely be nice to add something like the async paginate plugin


Add tags for various video features

Dependent on https://github.com/sharkusmanch/playnite-pcgamingwiki-metadata-provider/issues/9
https://www.pcgamingwiki.com/wiki/PCGamingWiki:Editing_guide/Video#The_table
Including:

HDR
FPS
Ray Tracing
Ultra-widescreen

HDR and Ray Tracing added in https://github.com/sharkusmanch/playnite-pcgamingwiki-metadata-provider/pull/20


Launcher code not working - Agent does not connect to Empire

Empire Version
2.5
OS Information (Linux flavor, Python version)
Attacker : Kali
Victim : Windows 10 (Defender is disabled)
Expected behavior and description of the error, including any actions taken immediately prior to the error. The more detail the better.

I launched Empire and setup a http listener.
I created a launcher with "launcher powershell http", copied its code (screenshot 1)
Pasted the code to my Victim CMD prompt.

-> The CMD closes, but agent does not connect back to Empire. Nothing happens, Although I have disabled Windows Defender.
Screenshot of error, embedded text output, or Pastebin link to the error

Any additional information

You can try taking the "-w 1" out of the command, this will stop the window
from hiding itself when PowerShell launches. See if there's any helpful
information printed out.
If that doesn't help, here's a more thorough debugging method. Set Base64
to false in the launcher options, then create the launcher. Paste the
launcher code into a PowerShell console, but remove the first command.
($ErrorActionPreference
= "SilentlyContinue";) See if that runs and gets you an agent. If it
doesn't, it should at least provide a helpful error.
On Mon, Dec 10, 2018 at 4:14 AM zazazo<EMAIL_ADDRESS>wrote:

Empire Version
2.5
OS Information (Linux flavor, Python version)
Attacker : Kali
Victim : Windows 10 (Defender is disabled)
Expected behavior and description of the error, including any actions
taken immediately prior to the error. The more detail the better.
I launched Empire, setup a http listener. Then I created a launcher,
copied its code, pasted it to my Windows CMD prompt. The CMD closes, but
agent does not connect back to Empire. Nothing happens, Although I have
disabled Windows Defender.
Screenshot of error, embedded text output, or Pastebin link to the error
[image: screenshot 2018-12-10 at 16 12 22]
https://user-images.githubusercontent.com/44822267/49722093-769b8e00-fc96-11e8-8ce0-934501c145a6.png
[image: screenshot 2018-12-10 at 16 13 47]
https://user-images.githubusercontent.com/44822267/49722158-a185e200-fc96-11e8-86f9-ecfd8c5394d2.png
Any additional information
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/EmpireProject/Empire/issues/1283, or mute the thread
https://github.com/notifications/unsubscribe-auth/ACFwUM4Z6AaSavoqZjb0aLrAQOzCycdwks5u3iX4gaJpZM4ZK8Sg
.

Actually i disabled my windows defender and i got my agents...however windows defender detects and deletes the agents thereby preventing the agents to call the c2 server. Hence,i recommend the team to find a way to bypass the av please

Unfortunately, we don't have the manpower to work around Defender all the time. There's a new AMSI bypass in dev that works consistently however, you're welcome to try that.

@mr64bit I'm using the dev as suggested but I don't know how to make use of the AMSI, can you please tell me how to do that? thanks


Overgrowth modifier has invalid recipe

forge 40.2.0, mantle 1.18.2-1.9.43, tconstruct 1.18.2-<IP_ADDRESS>, jsonthings 1.18.2-0.4.2, tinkers things 1.0
it looks like overgrowth is using tag entries for two of the ingredients for which there is no established tag group. (specifically, sky slime crystals)

i'm guessing the intent was to use "item" for those ingredients, not "tag"

Fixed in 1.0.1


Setting dropdown value based on another dropdown value

I am trying to set a static select dropdown value based on another static select value.
I am able to dispatch an action on first static select dropdown selection.
Able to set values for the second static select dropdown values as well.
But even if i set initial option for second dropdown like below
dropDownElement.setInitialOption(new val)
Even though initial value is updated but initial option is still the older value selected.
InputBlock blockElement =  ... // block element fetched from "req.getPayload().getView()"

List<OptionObject> dropdownOptions = dropdown options;
StaticSelectElement dropdownElement = blockElement.getElement();

dropdownElement(dropdownOptions);
dropdownElement(dropdownOptions.get(0));

After preparing the new view on BlockActionHandler, I am updating the view with
ctx.client().viewsUpdate(r -> r
        .viewId(currentViewId)
        .hash(currentHash)
        .view(finalNewView)
);

Hi @karishma21mahajan21, thanks for asking the question. However, I still don't understand what your question is. Could you share the modal UI you're trying to build? You can simulate it using Block Kit Builder and share the URL with us: https://app.slack.com/block-kit-builder

Hi @seratch,
PFB link:
block-kit-builder

Thanks for your quick reply. It seems that your issue is the same with https://github.com/slackapi/bolt-js/issues/1920#issuecomment-1669627257 . Our team already escalated the issue to the server-side engineering teams, but it seems that it is not yet resolved. Please consider going with the workaround shared in the thread. We apologize for the inconvenience.


[Minor] Enable pybind in mac build

Mac pybind lib build was previously broken by changes. Enable it to avoid it occurs again.

Send out PR later

--enable_pybind  and --build_wheel, you only need one

--enable_pybind  and --build_wheel, you only need one

prefer --build_wheel

yep.. just removed the redundant one


Can you add the Distribution API specs too please?

Can you add the Distribution API specs too please?

Hi @nomad-software, once you've requested access to the Distribution APIs you'll be able to see them in the OHIP Developer Portal.

I need the Json files not auto-magically generated documentation. The developer portal does not contain the Json files.

Hi @nomad-software , the developer portal will soon be able to download the specs as straight JSON files.

Thanks!


Connect to omp client running on a different host on the network

Hello.I am in an office in which we have a vm running OpenVas.
My question is whether I can connect to the omp client running in that vm from a different machine.
I tried to use the following code
HOST='an ip address'
with Client(host=HOST,username='username',password='password') as cli:
    cli.list_tasks()

however I get a Connection timedout error(Errno 110).
Any ideas if that's possible?
If it is I would appreciate a code snippet

Hello, you may find this doc from my fork of pyvas helpful (I'm hoping that this fork will get pulled in soon).  It isn't that difficult to set up, but I found that the available documentation wasn't helpful, so I tried to document what worked for me, so others could benefit.  Hope it helps you!
https://github.com/jal58/pyvas/blob/master/doc/testing.md

Closing for now due to inactivity


Rails 5.2 ActiveStorage Support

This adds the packages poppler-utils and ffmpeg to the cedar-14 and heroku-16 stack images.

As discussed in #91, there is a major security risk to including these packages without proper sandboxing.

Who's "mc3man", and why are we using packages from his PPA and not from official vendor repositories?

@titanous we talked about it offline with the security team. The general consensus was that for the customers using these features, it's more secure to roll this into the stack image so that customers can get security patches without requiring additional actions. (i.e. if it's put somewhere else, like a 3rd party buildpack, it would require an additional deploy before people are protected).
Since this is needed to support a key feature in Rails 5.2 people will definitely be using it. Of those that are using it, they'll be safer if they can get security patches without having to take action.
It's also worth nothing that a key difference between this PR and #91 is that we're using poppler for PDF which is GPL instead of mupdf which is AGPL. There was a licensing concern with mupdf, but not with poppler. Support for poppler was added into Rails by Terence to alleviate this concern.


Aggregate options ignored when passed through Blueprints Find

Waterline version: 0.12.2
Node version: 4.6.0
NPM version: 3.10.8
Operating system: Windows 7 x64

[Steps to reproduce]: Try making a GET request to: http://localhost:1337/modelName/?where={"groupBy":["field1"], "sum":["field2"]}
In /lib/waterline/querydeferred.js: if aggregate options are passed to where function in criteria argument, they are saved to the criteria object from normalize.criteria(criteria) however only criteria.where is
saved to _criteria.where, options saved to criteria object outside of where are ignored.

Ok, fixed!

ok, fixed now?

Final try..

Hi @dinana, for groupBy aggregations, I'd recommend using .query().

(see also https://github.com/treelinehq/waterline-query-docs)

@mikermcneil in my case I'd use .native (using mongo), and would lose blueprints and populate support. It seems this is partially implemented, where the options sent via blueprints are indeed saved to the criteria object, but it is not passed properly to the find method, looks more like a bug to me, would you look at the source code for the corresponding PR I created for this?

@mikermcneil Think you can check my latest on this?


report enhancements: matplotlib and faster data loading

Several enhancements to be merged via "rebase-and-merge". I wrote clean commits, so I recommend reviewing one commit-at-a-time.
Visual changes:

matplotlib for hovmoller and lat/pressure plots

add navigation bar to all pages

[x] merge #1142

Here's the new report:
output4.tar.gz

Thanks @oliverwm1 new report here:  output6.zip


Add environment variable for http requests timeout to hooks endpoints

Option has been added in #129.

Please confirm that issue was resolved in next release. If it is, please close the issue.

Closed due to inactivity.


SQLite timestamp columns have incorrect types

The two columns run_timestamp and completed_timestamp in the runs table of the SQLite database have type INTEGER, but are in fact used to store floats.

I am not really sure how or why that even works in QCoDeS, in particular, which converter is used to read back these numbers? Why not int?
In any case, that typing becomes a problem when third-party applications try to parse the DB file, since these applications will most likely "Believe the type". In the best case, doing so leads to the timestamps losing their sub-second precision, will can cause hard-to-debug problems down the line, since identical datasets will have slightly different timestamps. In the worst case, the timestamps simply appear to be invalid.
I propose that we make a type converting DB upgrade, changing these two INTEGER types to REAL. Alternatively, we could use an integer number of milliseconds, but that is WAY more work and seems like the wrong solution to me.
@QCoDeS/core

yes, yes, yes! agree to a small DB upgrade that just fixes these types and makes them REAL :)
I'd also add start_time/end_time in the experiments table, see here https://github.com/QCoDeS/Qcodes/blob/master/qcodes/dataset/sqlite/initial_schema.py#L25-L26
And for reference, here is where the type for run timestamps are defined in the "wrong" way - https://github.com/QCoDeS/Qcodes/blob/master/qcodes/dataset/sqlite/initial_schema.py#L52-L53 .

Do we really care about sub second resolution? The other alternative could be to just round the time to int

Do we really care about sub second resolution?

important question. i personally feel like we should but i can't find actual reasons.

The other alternative could be to just round the time to int

which will mean just changing return types for timestamps everywhere to int, fixing docstrings to explicitly say "seconds", and correct casting in respective functions/methods, right? would we also want to add a "converted" for type "INTEGER" (because the way our sqlite3.Connection is created, its us who decides on converters and sqlite3 defaults seem(!) not to be used)?

Do we really care about sub second resolution? The other alternative could be to just round the time to int

True, but then we'd have to round off timestamps as a part of the DB upgrade, meaning that we'll be (slightly) modifying user data. That makes me a little anxious. Could somebody have been using that part of the timestamp for anything? Can we be sure that they haven't? Changing the type seems to be the path of least potential complication.

@WilliamHPNielsen I would not change the type of any stored data but only have the reader do the round off of any old data when read

@jenshnielsen but for the user, will that not amount to the same thing? I am specifically worried about someone, somewhere having a check like:
if ds1.run_timestamp < ds2.run_timestamp:

a check that will suddenly behave differently after the DB upgrade. I'll be the first one to admit that my example is slightly contrived, but you really never know, do you? Zooming back out, I don't see what we gain by taking the risks involved in changing the behavior of the timestamp. What are the cons of simply making those two columns be of type REAL?

True, but then we'd have to round off existing timestamps as a part of the DB upgrade, meaning that we'll be (slightly) modifying user data.

oh, i missed that. i think we'd have to do it for the sake of consistency between sqlite types and stored data

but only have the reader do the round off of any old data when read

hm, but the "incorrectness" of the db schema will remain - is it good?

Well changing the column data type looks to be painful at best https://stackoverflow.com/questions/2083543/modify-a-columns-type-in-sqlite3 and comes on top of all the other issues with db upgrades that we know of.

Hmmm, as the SO answer also tells us, it trivially easy from the DB browser

but the generated SQL code does seem a bit scary (involves dropping the runs table). Let me investigate a bit. I guess we need a deeper (offline) discussion.

Just for completeness, let me drop the relevant link from the SQLite docs here:
https://www.sqlite.org/lang_altertable.html
The reason for the complication is that there is no ALTER COLUMN in SQLite. See: https://www.sqlite.org/omitted.html
It seems that the easiest way to get the schema upgrade in place is to create new timestamp columns with INTEGER type.


更新客户端后Openclash消失

更新后就直接白屏，显示：
No page is registered at ' / admin/ services! openclash/ client'
If this url belongs to an extension, make sure it is properly installed.
If the extension was recently installed, try removing the 1 tmp/ luci- indexcache file.

没有更新成功，去 系统 - 软件包 ，先 刷新软件包列表， 然后重新安装一次。


Feature request: show Apple SUS prefs

I'd like to be able to see the Apple SUS prefs in MunkiReport. Maybe this info could be placed in the Reports - Configuration report.
These prefs I have in mind:
/Library/Preferences/ManagedInstalls SoftwareUpdateServerURL
/Library/Preferences/ManagedInstalls InstallAppleSoftwareUpdates (true or false)
/Library/Preferences/com.apple.SoftwareUpdate CatalogURL

I belive all of those featurea are actually included in 2.8.4 munkiinfo module. I have small issue with CatalogURL but apart from that I can see all information in question.

You're right, I see it now. I was on an older version. Thanks, this is very useful.


PCI-3006 Initial creation of Pix4D CI pipeline

The pipeline is available at: https://builder.ci.pix4d.com/teams/developers/pipelines/concourse-pypi-resource-pipeline-PCI-3006-configure-ci
Basically there are 4 steps involved:

run the unit tests.
build the Docker image of the resource as a release candidate.
run the acceptance test using release candidate resource: put and get a simple wheel.
publish the new resource (trigger: true only on master pipeline after validation).

TODO:

[x] Add to ci-pipelines
[x] Add to terraform-tomato
[x] Configure status-checks in repo-settings
[x] Add CODEOWNERS file

pipeline_setter_bot: your pipeline is set: https://builder.ci.pix4d.com/teams/developers/pipelines/concourse-pypi-resource-pipeline-PCI-3006-configure-ci


float3_optimization benchmark's "fast" kernel returns references to stack memory

template <typename T>
struct rotate_tuple
{
    template <typename Tuple>
    __host__ __device__
    Tuple operator()(const Tuple& t) const
    {
        T x = thrust::get<0>(t);
        T y = thrust::get<1>(t);
        T z = thrust::get<2>(t);

        T rx = 0.36f*x +  0.48f*y + -0.80f*z;
        T ry =-0.80f*x +  0.60f*y +  0.00f*z;
        T rz = 0.48f*x +  0.64f*y +  0.60f*z;

        return Tuple(rx, ry, rz);
    }
};

What is Tuple?  It looks like it's a <float, float, float>, but in reality, it's a <float&, float&, float&>.  You can see this by trying to return Tuple(0.0f, 0.0f, 0.0f);:

candidate constructor not viable: expects an l-value for 1st argument

So we're returning references to rx, ry, and rz, which is of course no good.  As a result of the ub, clang optimizes away the whole body of this kernel.
It might be worth running the thrust test suite and benchmark suite under {a,m,ub}san; I think it would have caught this.
Not sending a patch because I'm not actually sure how to fix this.  :)

Try this: return thrust::make_tuple(rx,rx,tz) and make return type thrust::tuple<T,T,T>, e.g.
template <typename T>
struct rotate_tuple
{
    template <typename Tuple>
    __host__ __device__
    thrust::tuple<T,T,T> operator()(const Tuple& t) const
    {
        T x = thrust::get<0>(t);
        T y = thrust::get<1>(t);
        T z = thrust::get<2>(t);

        T rx = 0.36f*x +  0.48f*y + -0.80f*z;
        T ry =-0.80f*x +  0.60f*y +  0.00f*z;
        T rz = 0.48f*x +  0.64f*y +  0.60f*z;

        return thrust::make_tuple(rx, ry, rz);
    }
};

Great success!  I will send a PR, thank you.


Fixed invalid date that breaks the repo

A date was missing "T00" and was preventing helm to add the repo with the following error:
Error: looks like "https://nabsul.github.io/helm" is not a valid chart repository or cannot be reached: error unmarshaling JSON: while decoding JSON: parsing time "\"2022-12-27:00:00Z\"" as "\"2006-01-02T15:04:05Z07:00\"": cannot parse ":00:00Z\"" as "T"

ooops. Thanks for the fix!


Is there plans for a init project option for the CLI?

Just trying this tool out at the moment and i am correct in thinking i need to create the project.json and related folders?
Cheers

yup that's correct. I was going to add a scaffolding command, but you only need:
touch project.json
mkdir -p functions/{foo,bar,baz}
touch functions/{foo,bar,baz}/index.js

Was #44, might re-open if/when things get more complicated.

Maybe just add that tidbit to the Readme?
Just makes it clearer for those just getting started.
Thanks

will do!

opened #92 as well, at very least we'll have some repos that people can clone

Thanks a lot, sounds fantastic, making easy for people to get started makes a big difference :smile:


Allow a single whitespace line in chained expressions

Description
Closes #1248
There's a lot of discussion in the issues as to the right approach, but here's my proposal for a fix. Given the rule is intended to detect "consecutive" blank lines, I've made sure a single blank line is allowed in a chained expression (but that multiple is still disallowed and formats correctly). This will allow for the "blank line followed by a comment" examples brought up in the issue and keeps the whitespace rules consistent between regular statements and chained expressions.
The reasoning behind arguing for blank lines to be allowed in chained expressions is that there's nothing about disallowing them in either the Kotlin coding conventions or the Android Kotlin style guide (as far as I can see) and people have brought up use cases where it's useful in the issue.
Checklist

[x] PR description added
[x] tests are added
[x] CHANGELOG.md is updated

@seadowg Tnx for making the effort for this PR.
Basically you have reverted issue #1105 without offering an alternative solution for that issue. I do not think that we should do so as that functionality is expected to be in place by other users who do not want allow single blank line within dot qualified expression.
So I think that your PR has to be expanded with a new rule that just disallows (needless) blank lines in a dot qualified expression. This new rule should be a simplified version of the current rule. To allow blank lines in a dot qualified expression you will need to disable that additional rule in your projects.

So I think that your PR has to be expanded with a new rule that just disallows (needless) blank lines in a dot qualified expression. This new rule should be a simplified version of the current rule. To allow blank lines in a dot qualified expression you will need to disable that additional rule in your projects.

Sounds good! For the name of the new rule, how about no-blank-lines-in-chain? That's what pops into my head after looking at the language used in chain-wrapping and no-consecutive-blank-lines.

Sounds good! For the name of the new rule, how about no-blank-lines-in-chain? That's what pops into my head after looking at the language used in chain-wrapping and no-consecutive-blank-lines.

I prefer the longer version  no-blank-lines-in-chained-method-calls.

@paul-dingemans this is probably ready for another look.


Omnia/feature/73 phone livewire component

Added GetPhone livewire component.  View file, get-phone, includes links to intlTelInput js library and css.  Could not integrate into app.js.  Had to revert to an earlier version of iti library as current does not work.

@djamesfar are you able to add a screenshot of this working so we can verify what it looks like?


[BACKLOG-19630] Excludes junit from being shipped with karaf client a…

@pentaho/2-1b

Build Completed
:white_check_mark: This pull request has passed all validations.
Build Commands
mvn -Dsurefire.runOrder=alphabetical -B -fn -f 'pom.xml' -pl 'plugins/file-open-save' -P '!assemblies' -amd clean install && mvn -B -f 'pom.xml' -pl 'plugins/file-open-save' -P '!assemblies' -amd site

Cleanup Commands
mvn -B -f 'pom.xml' -pl 'plugins/file-open-save' -P '!assemblies' -amd build-helper:remove-project-artifact

Changed files
  plugins/file-open-save/pom.xml

@pamval @kcruzada @dkincade Please review and merge whenever you have a chance


Come up with a DatasnapshotGeoQueryEventListener.

Simple POC of #89
I just created the new listener and the old one will be bridged to the new one. Hence we don't need to adjust the tests.
Also had to create a cache for the Datasnapshot. This is also the behavior that we have in our fork and it works well for us.
Happy to get some feedback.
I adjusted the License header from 2014 to 2017, I hope that's ok.

@vanniktech thanks for kicking this off!  I think we're 90% of the way there but we could probably make this simpler:

Take your DatasnapshotGeoQueryEventListener and make it the superclass of GeoQueryEventListener.  The latter class just transforms the DataSnapshot events into String events, like you're doing in the bridge.
Drop the bridge class.
Make library methods that previously accepted GeoQueryEventListener as a parameter now accept the DataSnapshotGeoQueryEventListener base class.  People who continue to pass in the GQEL (gotta abbreviate :-) ) will see no change in behavior.

By this method we allow easy extension from the base class so people can do more, like make a joining listener or a listener that converts to model classes.

I'm not seeing how this would be backwards compatible. Is there something I'm missing? GeoQueryEventListener is an interface and hence those other methods would be added and every consumer would need to implement them too.

Oh ... fudge.  I forgot it was an interface.  Ok I'll have to think about this again, thanks!

Yeah. The bridge was the easiest solution that I saw which don't require any changes on any consumers. I agree it's not the most elegant one. We could deprecate the old one and favor the new one. With 3.x we could drop a lot of things and make as less things as possible part of the public API.

Rebased onto latest master & updated the copyrights.

This is now ready for another feedback round.

@vanniktech thanks for all the changes!  This looks great.  Do you have any more improvements you want to make or should I merge it now?  Also do you think this is a good time to cut a release?

I'll need to look tomorrow if there are any other changes but I'd want #87 to be in the release too. Otherwise I wouldn't be able to get rid of our fork.
Do we have Snapshot deploys? Those would come in handy for easy testing.

The new behavior has no tests though since it still uses the old listener for testing.
Let me know what you think.

@vanniktech LGTM!  I will add some tests in another PR.  Thank you for the contribution and discussion.

Oh cool. Thanks :) I executed the tests locally with the json file and everything still worked.


added technology addon feature

The splunk module has no support for configuring forwarders for TA's (technology addons) which, according to the docs, have their input forwarders configured in $SPLUNK_HOME/etc/apps//local/inputs.conf
I'm using a fork of this module to be able to have this feature - it currently only supports configuring inputs and installing packages for TA's but other local config could be added in the same model.
Would like to merge this to keep the upstream updated.

I'd like to see some spec tests here, ensuring there is code coverage and things work as expected.

Thanks for this! I think we don't require tests because there are none for the module at all, but if you could address my review comments that would be great!

@hunner thanks for looking this PR over... I agree with your points and I've modified the PR with a second commit that covers these.


Multiple Grids on XY Grid

Just recently switched from the Float Grid to the XY Grid on 6.4.2 and I struggle to find a way to implement multiple grid semantically as Float Grid was capable of.
It used to be possible through the grid-row() function as in this example:
.container {
  @include grid-row(10) {
    .main-content {
      @include grid-column(7);
    }

    .sidebar {
      @include grid-column(3);
    }
  }
}

How am I supposed to create a new grid-x with a custom number of columns with the new grid system? Seems to be also problematic with the Flexbox Grid, so I'm pretty sure I'm missing the functionality which is somewhere I imagine.

@kvinlambert You are right there isn't a mixin for doing what you describe from the float grid.
However you could easily do it like so:
.container {
  @include xy-grid;

    .main-content {
      @include xy-cell(7 of 10); // or 7/10
    }

    .sidebar {
      @include xy-cell(3 of 10); // or 3/10
    }
  }
}

Here's the function that the `xy-cell` mixin uses for its size calculation: http://foundation.zurb.com/sites/docs/xy-grid.html#xy-cell-size

The `xy-cell` mixin could use a slight docs update though to list you can use it in this way.

Does this help?

Hi @brettsmason! Thanks for the help, that's what I ended up doing just after posting, and I guess it's the same result! ;)


Visual cue to indicate that visitor has voted on comment

As suggested by a user, we could add a class to the arrow container to show that visitor has voted on the comment. Like on Reddit.
https://wordpress.org/support/topic/show-user-their-vote?replies=2#post-7038906

Added a class to indicate comment was voted on by user ( authenticated )


Add new events to the official Indøk Google calendar

When an event is created, it should be added in "indøkkalenderen", the official Indøk Google calendar.
Also, when an event is updated, any changes to the event should also be reflected in the calendar.

This should provide some insight: https://stackoverflow.com/questions/37754999/google-calendar-integration-with-django


Staking with bitconnect coin

I have trouble in singing the wallet with my Mac IOS so please somebody told me how to fix this problem because I cannot fix it myself

Read the following threads carefully:  The updated config file can be found in there too.
Bitconnect-Qt wallet won't sync on Mac OSX
https://github.com/bitconnectcoin/bitconnectcoin/issues/22
BITCONNECT QT WALLET OUT OF SYNC
https://github.com/bitconnectcoin/bitconnectcoin/issues/19
0 Active Connections
https://github.com/bitconnectcoin/bitconnectcoin/issues/13


txn: use Commit to clean up pessimistic locks (#6353)

Signed-off-by: youjiali1995<EMAIL_ADDRESS>
What have you changed?
Cherry pick #6353

/merge

/run-all-tests


Poor visualization about reproducible results by Demo.ipynb and strange F1 scores

The reproduced visualization is quite different from the presentation.

And the F1 score is a bit strange, much higher than the essay

Hi!
Thanks for your attention to our work.
Please refer to a closed issue to solve your visualization problem: #17. I have provided an English solution here: https://github.com/SunnyHaze/IML-ViT/issues/17#issuecomment-2076553542
From the information you have provided, it is difficult to determine the second issue. I suggest checking the generalization performance on other datasets. If the problem persists, consider using a single GPU and a single batch size to obtain prediction results accurately.
If you have further question, please feel free to reach out.

Thank you very much, the first problem has been solved, and the second problem I try the method you provided.

That's great!
For second problem, I believe it is likely an overfitting issue (validated by generalization performance on other datasets. you can try using other Norm to solve this issue) or an unexpected problem during multi-GPU reduction (resolved by using a single GPU and a single epoch).
In our latest work IMDL-BenCo, we have addressed the multi-GPU reduction issue, ensuring accurate results even with multiple GPUs and large batch sizes. However, we are still hard working on the documentation and releasing latest features, so please stay tuned for updates.

Ok, thanks for the answer.


3 Buttons on Dialog

Can you implement Center Button?

It is possible. I will do code refactoring for this library later in next version, maybe v1.1.0. And I will add this function.


enhancement: unify async tests

What this PR changes/adds
This PR Modifies tests using Countdownlatch with the Awaitility Framework.
Why it does that
Awaitility is a DSL that allows to express expectations of an asynchronous system in a conciser and easier to read manner than CountdownLatch.
Linked Issue(s)
Closes #3
Checklist

[x] added appropriate tests?
[x] performed checkstyle check locally?
[x] added/updated relevant documentation?
[x] assigned appropriate label? (exclude from changelog with label no-changelog)
[x] formatted title correctly?

before i forget on monday: let's talk about the status on monday - i'll open the PR in the upstream then

@florianrusch-zf I'm already on vacation, however since the comments I did are addressed, it should be pretty easy to have this merged on upstream


fix: 🎨 use cache.teia.rocks

Draft to identify potential issues/needs.

2 small issues:

pdf files are no longer loading, I used to be able to flip the pages, now it hangs on "Loading PDF..." https://teia-ui-pr-187.onrender.com/objkt/774424
video identicons don't load, it just says "identicon" https://teia-ui-pr-187.onrender.com/jjjjjohn

these issues might also be related to the refactorings.

Actually the logic for falling back to video was only used by media-types (image) component, for now I duplicated the logic for identicons. 🙈


add hlil to rust

This is a draft for the HLIL rust implementation based on MLIL implementation.
TODO list:

[x] implement ConstantData data type
[x] implement Intrinsic data type
[x] allow the user to set (or not) the ast-full option
[x] implement the Label type, used by Goto and Label operations
[x] handle cross reference pointers, eg two jmp instructions one point to the other
[x] create examples for the hlil usage
[x] implement function Hash that is not be based on pointers.
[ ] code cleaning

@KyleMiles I didn't understand this line: https://github.com/Vector35/binaryninja-api/blob/66fe34a49322d0a63d8f6efe00ca20d9a2c4ce05/python/highlevelil.py#L2070
The operand 2 is used twice?
intrinsic: 0
params: 1, 2
dest_memory: 2
src_memory: 3

The correct operands should be 0, 1, 2, 3,4?:
intrinsic: 0
params: 1, 2
dest_memory: 3
src_memory: 4

Yes, that's correct. That's a typo in the HLIL bindings. Thanks for noticing that, I'll fix it.

I believe the corresponding C++ API implementation is here: https://github.com/Vector35/binaryninja-api/blob/dev/highlevelilinstruction.h#L1147.
I would definitely match what the C++ API is doing in this case. We'll look into getting the Python API fixed. Thanks for bringing it up.

Currently, the implementation of Instructions is a little awkward, because getting fields from the operation requires a pointer to the function:
let instr: HighLevelIlInstruction = block.next().unwrap();
match instr.operation() {
    HighLevelILOperation::Goto(goto) => {
        let name = goto.target(instr.function()).name();
        println!("goto {name}")
    }
    _ => println!("other"),
}

This could be solved, although making the struct a little less efficient, by adding a Ref<HighLevelILFunction> to the operator if necessary.

adding a Ref to the operator if necessary.

Sounds like a fair simple/safe fix.

Alternatively, add all fields from HighLevelIlInstruction into each HighLevelILOperation, then make the operation an instruction directly, instead of using it as a field of instruction struct.

I'm okay with the inst.lift()/inst.operands() split right now, but are you proposing merging .operands() into the instruction? I'd love anything that can reduce/simply the APIs like that.

I'm okay with the inst.lift()/inst.operands() split right now, but are you proposing merging .operands() into the instruction? I'd love anything that can reduce/simply the APIs like that.

I mean, instead of having, a struct for instruction (HighLevelILInstruction) and a enum for all operations (HighLevelILOperation), like the PR is doing right now:
pub struct HighLevelILInstruction {
    pub(crate) function: Ref<HighLevelILFunction>, // and fields common to all instructions
    pub(crate) operation: HighLevelILOperation,
}
pub enum HighLevelILOperation {
    Adc(BinaryOpCarry),
    // ... other operations
}
pub struct BinaryOpCarry {
    left: usize,
    right: usize,
    carry: usize,
}

We change the operation enum into the instruction struct, adding all fields common for all instruction into each operation struct:
pub enum HighLevelILInstruction {
    Adc(BinaryOpCarry),
    // ... other operations
}
pub struct BinaryOpCarry {
    pub(crate) function: Ref<HighLevelILFunction>, // and fields common to all instructions
    left: usize,
    right: usize,
    carry: usize,
}

This way, there will be no need to pass the function reference to lift and related functions and avoiding the unnecessary duplication of the function Ref.

@KyleMiles there still lots of implements/simplification to do on the API, but I spend too much time on this PR already and it's time for me to move on.
Do you need any changes before doing a merge?

Sorry for the delay on this, was only able to get back to this PR this week. Thank you for your tremendous effort getting this PR through! I'm extremely glad to finally have HLIL and MLIL bindings in our API. Thank you!
I just merged this manually in f682ca69b356755fe6c06bcdd8f4fab73f7d2c78.


DHCP Proxy Does Not Report Option 12 (Hostname)

Currently, the DHCP proxy does not report option 12 (client hostname) to the DHCP server when requesting a DHCP lease. This means that routers which function also as a DNS server (most consumer routers), and use that information in order to create an A record pointing to the DHCP client, will not function.
This issue does not affect the core DHCP proxy functionality, but instead represents a quality-of-life issue.
I would be willing to submit a PR for this, but I'm not familiar with the codebase; could someone please point me in the direction of the necessary changes?

It should not be that complicated, however as of of today netavark does not know the host name of a container so the first step would be to send the Hostname from podman to netavark.
The type for podman is defined here: https://github.com/containers/common/blob/536bbe5e7e21d8e2087eee9615f3b3c995955840/libnetwork/types/network.go#L233
Then you need to make podman set this new struct field with the correct value, likely here: https://github.com/containers/podman/blob/911be1cbcb0ad654a8e10666262bdcee50ee54e0/libpod/networking_common.go#L47
Change the type here in netavark to read the new field. Then add it to the grpc type so you can send it to the dhcp-proxy and then you need to figure out how to set this field in for the dhcp call. I checked at it seems the our DHCP library seems to support the Hostname option so it should be possible.
That said I definitely wouldn't call this easy which of course depends on your expertise. The proxy code is definitely not very "clean", so figuring out how it works is not as trivial as it should be.

Waiting for this too!

Hi @Luap99, I have an implementation on my dev branch. Should I make a PR?
But I'm changing the proto, and maybe this feature should only be enabled if explicitly asked. Please suggest some idea.

@Luap99 and @SilverBut Any updates on this?

No, this is waiting for someone to propose a PR. I don't have time for it.

Seems my dev branch have not updated for a while. Let me see what I can do.

Using the container name as the dhcp_host_name seems like a reasonable default absent an explicit hostname request. From a podman perspective, interpreting the container name as a DNS hostname also seems reasonable, at least per this comment:
https://github.com/containers/common/blob/536bbe5e7e21d8e2087eee9615f3b3c995955840/libnetwork/types/network.go#L236
... as well as the fact that multiple containers in a podman network can DNS resolve each other via their container names by default

@SilverBut Are you still working on this?  I just started converting containers to macvlan/dhcp and was surprised that a name was not sent.  This has caused me to have to write scripts to update DNS when containers are created.  Does the code in your dev branch work with container name as hostname?  If so, that's a great start.  I you don't have time to work on it would you mind if I took that code and created a PR for it?

I have a working implementation for passing the hostname from podman to netavark that I'm about to push up PRs for.  Since the subject of defaulting to container name came up I want to clarify that the way I have it implemented, the default hostname is left to podman to specify rather than netavark.  The reason is that if you don't specify --hostname in your podman run command, podman currently defaults the hostname to the first 12 characters of the container ID and that's what the container's /etc/hostname is set to.  If we default it to container name in netavark, the container and the dhcp lease/ddns entry will disagree.
I am going to ask the podman folks if it would be reasonable to change its hostname default from the short ID to the container name with characters not in the set [0-9a-zA-Z.-] removed but that might be a big deal to users.  There's also the issue that if no hostname is specified and the container isn't running in a private namespace, the hostname gets set to the hostname of the host which we certainly do NOT want passed in a DHCP request.
In any case, I believe that the responsibility of determining the hostname should rest with podman and that if no hostname is passed to netavark, netavark should simply not send hostname in the DHCP request.
@Luap99 does this make sense to you?

I have a working implementation for passing the hostname from podman to netavark that I'm about to push up PRs for. Since the subject of defaulting to container name came up I want to clarify that the way I have it implemented, the default hostname is left to podman to specify rather than netavark. The reason is that if you don't specify --hostname in your podman run command, podman currently defaults the hostname to the first 12 characters of the container ID and that's what the container's /etc/hostname is set to. If we default it to container name in netavark, the container and the dhcp lease/ddns entry will disagree.

In any case, I believe that the responsibility of determining the hostname should rest with podman and that if no hostname is passed to netavark, netavark should simply not send hostname in the DHCP request.
@Luap99 does this make sense to you?

yes that seems good

I am going to ask the podman folks if it would be reasonable to change its hostname default from the short ID to the container name with characters not in the set [0-9a-zA-Z.-] removed but that might be a big deal to users. There's also the issue that if no hostname is specified and the container isn't running in a private namespace, the hostname gets set to the hostname of the host which we certainly do NOT want passed in a DHCP request.

I don't think we want to change the defaults, it is the same with docker AFAIK. On the other side with pods we default to the pod name as hostname so so there is certainly the case to be made to make this consistent.
We can have such discussion on the podman repo if you like, we netavark maintainers are a subset of podman maintainers to be clear.
The namespace issue can happen but I find it very unlikely that someone wants uts=host while also using a private network with DHCP. Ultimately we would still request a lease for a different mac address so I don't think it is that bad and in the end easy to call a user configuration issue.

Hi @gtjoseph , sorry for late reply. Of course you can take any part of my branch if it's helpful, but seems your implementation is well completed. I have abandoned this feature due to some infra reasons. For now I'm sending additional container information with Option 82.
But I advise against using hostname as client id by default. A option might be better. Problem mentioned in the comment is because some DHCP implements won't always respect reservation due to existing leases. But making client id non-unique could cause additional risk, like container name reused on different host, which is a common use case. According to RFC2131:

The 'client identifier' chosen by a DHCP client MUST be unique to that client within the subnet to which the client is attached.

Even if DHCP server accepts this by assigning same IP for both client, the routing convergence time will be much longer, and such failure is not easy to debug.

@SilverBut What would you think about using the first 16 characters of the container ID as the client id?  This should give enough uniqueness to prevent issues and will remain constant for the life of the container.

I think most DHCP server will be fine as long as the client id is unique across device in same pool.
As for the length, I happen to run both kea and isc-dhcp, so I can get the lease database. Among ~10k leases (including those under reclaim time):

7% have no client id because some weird old IoT devices only use mac address and never provide a client identifier.
Another 18% have more than 16+1 byte client id (some of them are servers running systemd-networkd, which generates a ff:${18-byte-dhcpv6-duid-info}). Maximum length is 37+1 byte and I have no idea about the reason.
All other clients simply use a 6+1 byte client id 01:${mac_addr}.

All length works well for both server. I'm not sure how Microsoft DHCP works but I believe it won't complain for a longer client identifier.


[AutoPR billing/resource-manager] [Billing RP] Rename BillingAccount->EnrollmentAccount.

Created to sync https://github.com/Azure/azure-rest-api-specs/pull/2626

(message created by the CI based on PR content)


Explicit "New topic" UI

@vanclute writes at https://github.com/zulip/zulip-mobile/issues/4378#issuecomment-753572750 :

Adding to this, it looks as if the mobile client actually can't specify any topic at all, and if there is no topic in the stream yet then I think it's able to create the first post, which falls into (no topic).
Users really should be able to create topics in the mobile app.

and adds:

OK adding again, users CAN create new topics on mobile but it is completely not obvious how to do it. You have to start writing a message in an existing topic, then EDIT the topic (that's what it looks like you'll be doing anyway) and post your message. It will actually create a NEW topic and not edit the old one.

The webapp has at the bottom of the message list, when the compose box is closed, a distinct "New topic" button:

It'd be good to find an appropriate design to do something similar in the mobile app.

@gnprice Can I work on this issue?

@gnprice Can I work on this issue?

@gnprice If this is not assigned to anyone, can work on this? I have some ideas to implement this. (ofcourse keeping in mind the UI/UX of the app)

Working on this issue!

Looks like discussion is continuing here.


fix: lookup accessible

fix: #
Changes proposed in this PR:

[ ] I have followed (at least) the PR section of the contributing guide.
@90milesbridge/tigger

Pull Request Test Coverage Report for Build 3687

9 of 13 (69.23%)  changed or added relevant lines in 3 files are covered.
4 unchanged lines in 1 file lost coverage.
Overall coverage decreased (-0.08%) to 79.731%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/components/Lookup/index.js
5
6
83.33%

src/components/Lookup/leftElement.js
2
3
66.67%

src/components/Lookup/icons/closeIconDark.js
2
4
50.0%

Files with Coverage Reduction
New Missed Lines
%

src/components/Lookup/index.js
4
82.41%

Totals

Change from base Build 3679:
-0.08%

Covered Lines:
2793

Relevant Lines:
3386

💛  - Coveralls


 sets align-items: center; and text-align: center;

<Flex align=center /> sets align-items: center; and text-align: center;
This is because Flex is an extension of Box.
On Flex, align means align-items
On Box, align means text-align

Duplicate of #136


Adjust some paint & brush tools icons

My actions before raising this issue

[x] Read/searched the docs
[x] Searched past issues

I do not really like two icons I've highlighted, their style looks a bit bolder that for others.
I've taken them from the Internet, maybe it is a good idea to redraw them from scratch.

Hi, I want to work on this issue

Hello, @rahulsrivastava1
Actually, this is a ticket for our designer.
That is not about development, I am not sure you should work on it.
If you want to collaborate in the project, you can choose between multiple other issues :)


Misdirection

text: you can play and chose no lock and pay 0,did you know that? i dont,is here,but maybe is old rule
link: https://groups.google.com/forum/#!msg/rec.games.trading-cards.jyhad/0KEYzv22kjs/H4MWvI5F_hEJ

Yes it dates from before the card errata. Misdirection used to be X Pool: lock X minions.


Add os-release info for display

This add missing values to /etc/os-release so GamepadUI will pick them up.

I don't think we need or want that. It adds no additional useful information.

I don't think we should put inaccurate information into those fields just to "make it look better".

We could use this to display the actual install channel org/repo/tag could go there.

I don't think we should put inaccurate information into those fields just to "make it look better".

I wouldn't call it inaccurate. But fair enough. Could be useful though.
@pastaq the tag is already there, the problem with adding the update channel is that the image is not modified, the release on GitHub is marked as release.


Using BModal leads to massive memory leak with nuxt

Describe the bug
When I use the BModal component on a page in Nuxt and throw some loads to the page, the heap allocation skyrockets from 20mo to more than 700mo. If I comment the modal component and throw the same loads, the heap allocation just goes from 20mo to 21mo.
I setup on stackblitz the minimal setup to reproduce it. I use npm run build and PORT=3600 node --inspect .output/server/index.mjs to launch the nuxt app production build and run a heap allocation with Chrome dev tools after throwing some loads to the page with npx artillery quick --count 20 --num 100 http://localhost:3600.
Reproduction
https://stackblitz.com/edit/bootstrap-vue-next-modal-memory-leak?file=nuxt.config.ts
Used Package Manager
npm
Validations

[X] Have tested with the latest version. This is still alpha version and sometime things change rapidly.
[X] Follow our Code of Conduct
[X] Read the Contributing Guide.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Check that this is a concrete bug. For Q&A, please open a GitHub Discussion instead.
[X] The provided reproduction is a minimal reproducible of the bug.

I found this issue in vueuse repo that could be related to this issue as useModalManager use the createSharedComposable function: createSharedComposable never dispose when using SSR

If anyone is (or will be) using this lib in production, just don't use the BModal component until this bug is fixed. This is a serious memory leak bug that will crash your node server pretty quickly.


Disable SSL cert verification in ways that are compatible with older

Pythons.

This is the branch that fixes ssl handshakes for older versions of python, as well as enables compressed private keys.  It also fixes a bug with sending transactions to chain.com that I discovered while testing.  These changes are not present in master--is it okay if I go ahead and merge them?  Blockstore will not work without these fixes.

OK taking a look now.

@jcnelson why did you replace:
            if is_int(private_key):
                secret_exponent = private_key
            elif is_256bit_hex_string(private_key):
                secret_exponent = int(private_key, 16)
            elif is_wif_pk(private_key):
                secret_exponent = int(
                    hexlify(b58check_decode(private_key)), 16)
            else:
                raise Exception('Not a valid private key format.')

with
private_key = encode_privkey( private_key, 'decimal' )
secret_exponent = private_key

It seems this breaks things and removes the ability to pass in private key strings of any format.

Also, in this file you're assuming that the desired format is compressed: https://github.com/blockstack/pybitcoin/blob/ssl_noverify_oldpython/pybitcoin/transactions/network.py
Any particular reason why? Both compressed and uncompressed keys need to be supported.

@shea256 The encode_privkey() method from pybitcointools [1] takes a private key encoded in one of the formats it supports (i.e. decimal, bin, bin_compressed, hex, hex_compressed, wif, wif_compressed) and outputs the same private key in the requested format.  Maybe I've misread the code, but it seems that the purpose of the BitcoinPrivateKey constructor is to take an encoded private key (in one of the above formats) and extract its secret exponent as a decimal.  The encode_privkey() method, as used in this pull request, does exactly that.
The sign_transaction method (imported from pybitcointools.sign) will decode the given key regardless of whether or not it is compressed; the "compressed=True" flag proves unnecessary and can be removed from network.py.  However, it has been my experience that the UTXO provider (chain.com in my case) does not seem to recognize uncompressed addresses.  This is part of what necessitated this patch--I need to ensure that the address we feed into the request is compressed.
[1] https://github.com/vbuterin/pybitcointools/blob/master/bitcoin/main.py

Here is the encode_privkey() code:
def encode_privkey(priv, formt, vbyte=0):
    if not isinstance(priv, int_types):
        return encode_privkey(decode_privkey(priv), formt, vbyte)
    if formt == 'decimal': return priv
    elif formt == 'bin': return encode(priv, 256, 32)
    elif formt == 'bin_compressed': return encode(priv, 256, 32)+b'\x01'
    elif formt == 'hex': return encode(priv, 16, 64)
    elif formt == 'hex_compressed': return encode(priv, 16, 64)+'01'
    elif formt == 'wif':
        return bin_to_b58check(encode(priv, 256, 32), 128+int(vbyte))
    elif formt == 'wif_compressed':
        return bin_to_b58check(encode(priv, 256, 32)+b'\x01', 128+int(vbyte))
    else: raise Exception("Invalid format!")

If you provide "decimal" as the format, it assumes the private key was already in decimal format and just returns the input.

@shea256 If the private key is not an integer already, then the line
    return encode_privkey(decode_privkey(priv), formt, vbyte)

is executed, as desired.

OK the decode_privkey function is a little strange. Nonetheless, our goal should be to not rely on pybitcointools at all. I have included some functions in there as temporary hacks.

I'd keep the existing code that I have in privatekey.py, since it's much easier to understand, doesn't rely on pybitcointools, and provides proper error reporting.

@jcnelson both compressed and uncompressed addresses are supported. It just so happens that more and more wallets are switching to compressed keys so you may see a lot of keys. Please note that for a given compressed private key, only the compressed public key and equivalent address based on the compressed public key will be supported (and the same is true for the uncompressed private key).
In fact, onename.com only uses uncompressed keys right now. In general, supporting uncompressed keys is strictly required.

I just pushed some additional code that addresses the issues we discussed in person:

we detect whether or not a public key or private key is compressed.
we do not allow the client to choose whether or not they want the key in compressed or uncompressed format (since this is just asking for trouble, given the construction of Bitcoin private keys).
the code no longer uses the compressed= keyword argument.

Woot! I'm just going to pull and run the tests.

Merged! :dancers:


Help button sends users to the main page

Refer back to TrEnCh project website
Form to send email to huckley@gmail? Or refer to guthub to post issue?

Added the footer to log issues on GitHub.


add rootElement check on vulcan-core/lib/client/start.jsx

in my app i got two rootElement on client. rootElement already exist from SSR, but start.jsx  append it again to body. i don't know why this doesn't happen before upgrade to Apollo 2

Thanks but maybe we should figure out why this is happening in the first place? That fix might just be hiding a deeper issue?

Thanks for the PR. Yes I am not 100% on how it's supposed to work, not sure indeed there is not another underlying mistake.

Was solved in previous update.
Thanks for pointing the issue.


installation  - Windows 10

$ python setup.py install
running install
running build
running build_ext
building 'netfilterqueue' extension
creating build
creating build\temp.win32-3.6
creating build\temp.win32-3.6\Release
C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\BIN\cl.exe /c /nologo /Ox                                                 /W3 /GL /DNDEBUG /MD -IC:\Users\Fetah\AppData\Local\Programs\Python\Python36-32                                                \include -IC:\Users\Fetah\AppData\Local\Programs\Python\Python36-32\include "-IC                                                :\Program Files (x86)\Microsoft Visual Studio 14.0\VC\INCLUDE" "-IC:\Program Fil                                                es (x86)\Windows Kits\10\include\10.0.10240.0\ucrt" "-IC:\Program Files (x86)\Wi                                                ndows Kits\8.1\include\shared" "-IC:\Program Files (x86)\Windows Kits\8.1\includ                                                e\um" "-IC:\Program Files (x86)\Windows Kits\8.1\include\winrt" /Tcnetfilterqueu                                                e.c /Fobuild\temp.win32-3.6\Release\netfilterqueue.obj
netfilterqueue.c
netfilterqueue.c(434): fatal error C1083: Cannot open include file: 'netinet/ip.                                                h': No such file or directory
error: command 'C:\\Program Files (x86)\\Microsoft Visual Studio 14.0\\VC\\BIN\\                                                cl.exe' failed with exit status 2

libnetfilterqueue is a Linux-only feature, so you won't be able to install python-netfilterqueue on Windows.


README: update instruction for prebuit graphic binaries

Add DomD and DomU specific part.
Update DomA specific part.
Signed-off-by: Ruslan Shymkevych<EMAIL_ADDRESS>

Rebased.
Comments are addressed as a fixup commit.

Acked-by: Volodymyr Babchuk<EMAIL_ADDRESS>

'Ack' is added.
The fixup commit is squashed into the main commit.
Ready to be merged.


Documentation For 'NanAsyncProgressWorker' and "NanAsyncBufferWorker"

As I understand, NanAsyncProgressWorker is a new NAN feature, I also suspect that NanAsyncBufferWorker is new, but can't be sure. The tests contain an implementation for both classes, but while I have a rough idea of what NanAsyncProgressWorker does from it's name, I find it hard to work out what NanAsyncBuffer is for.
What I would like to do, is:

Call a Javascript function with a callback
Run an indefinite loop in a C++ async
Have that loop change a handful of static values
Use either a NanAsyncProgressWorker or NanAsyncBufferWorker to retrieve those static values each time they change
Wrap those values up in an object
Return the object as a callback parameter.

Is this possible?

You are right in that NanAsyncProgressWorker is a new feature. However, NanAsyncBufferWorker is not, it is just a realization of NanAsyncWorker that is part of a test.
While it might somehow be possible to do what you want with NanAsyncProgressWorker, that is not its intended use. It is meant to send progress notifications about long running tasks so you can update a progress bar.
Why not just give in a callback that you can invoke whenever those magic values are supposed to change?

Not sure if this is the best place to discuss it, but it's a domain with very little coverage on Stackoverflow... Right now, I:

Feed in a Javascript callback to a 'run' method.
I kick off an NanAsyncWorker with a dummy callback (i.e, NaNAsyncWorker).
The NanAsyncWorker kicks of an infinite while loop in a persistent worker, which updates a struct.
In the main thread, I run another infinite 'event' loop, which contains a conditional that will run the Javascript callback function when key struct values change, and return an object that reflects the current state of the static values inside the struct I'm interested in.

It works, but there's a definite memory leak.
I think the infinite loop in the main thread is preventing the V8 garbage collector from doing what it usually does, so copies of the Javascript object that I create for the callback are being held in memory...
I wanted to make the JavaScript callback from the code kicked off by the NanAsyncWorker, but the manual suggests that any code inside a worker should not call or create any V8 stuff... Am I right?
Some advice will be great, because I'm sure having the two loops is a bad idea. Hence why I'm considering the use of an NanAsyncProgressWorker.

Ok... So I've optimized my application, based on this conversation, and now have a nice clean module that only runs a single long running loop in an AsyncWorker,
interestingly though, when I run the module, I create a new instance of the object that the module produces (it's a .js constructor function from), run it for a while (collecting the yield in a setInterval method), delete it, and then open a new instance. I do this periodically.
After the fifth cycle though, the worker slows down to a shocking rate...  I don't think it's the loop, as I've noticed that the loop will block the entire application if it's not explicitly stopped (or crashes).
Is this not unheard of? I've noticed a similar bug when running Node Serialport on Windows.
Especially when repeatedly connecting to the same serial port and device.
For example, one question I have is how in this small example;
// Spawn a worker thread...
NanCallback* dummyCallback = new NanCallback(args[0].As<Function>());
NanAsyncWorker* workerThread = new DeviceDataThread(dummyCallback, device);
NanAsyncQueueWorker(workerThread);

Will the NanAsyncWorker take care of deleting the "workerThread" internally, or is that my responsibility?

NanAsyncQueueWorker destroys workerThread upon completion, taking dummyCallback with it.

Thank you for the clarification. I'm kinda' keen on examining this stuff fully, as it I've turned to the idea of writing a native module, because of a fault I found in Node Serialport.
So in observing this consistent slow down both in my application, and in Node Serialport (which also uses NAN), I wonder if both issues have the same root cause...
I can't, of course, rule out my own stupidity and inexperience, but what I've written, while a little uncommon, is not overly complicated (it essentially reads a stream from a serial port device... Another common trait between my app, and Node Serialport). It should also be noted that I'm running the app through Node Webkit (v0.7.5) (as I also did with Node Serialport, when I encounter the same problems with slowdown).
Although it's unlikely, the only article that matches my current suspicion is this:
https://www.joyent.com/blog/walmart-node-js-memory-leak
The article alludes to a scale much larger than what I'm working with, but as I'm polling a serial port device (@9600Bd), I would very likely parse enough data to encounter something similar, no?
And failing that line of investigation, what would be a typical cause of the type of slowdown I'd described?
Thank you for the help up to this point, btw.

Ok. Further investigation leads me to believe it's a Node Webkit timer issue...
Thanks all the same.


How do I make percent round down?

I'd like to make the percent field show the floor of the actual value. The motivation for this is that I don't want the percentage to show as 100% till the last block is completed.

That works, thanks! Some examples / better documentation of it would be nice, I did go through the documentation but I couldn't figure out what ProgressTracker was till I saw your comment.

If you would be able to submit a PR with improved documentation and/or examples, that would be great!


commons.bash:61-61: Use $BATS_TMPDIR instead of teardown...

The puzzle 89-c19177fa (from #89) in src/test/commons.bash (lines 61-61) has to be resolved: "Use $BATS_TMPDIR instead of teardown methods for fakes deletion"
The puzzle was created by Dmytro Serdiuk on 09-Nov-17.
Estimate: 0 minutes, role: IMP.
If you have any technical questions, don't ask me, submit new tickets instead. The task will be "done" when the problem is fixed and the text of the puzzle is removed from the source code. Here is more about PDD and about me.

The puzzle 89-c19177fa has disappeared from the source code, that's why I closed this issue.


Support for Flux 2.2.0

Describe the bug
With recent changes to Flux in v2.2.0 parsing of the inventory of HelmReleases is not working.
This will be apparent when viewing a HelmRelease managed by a Flux 2.2.x+ installation, the inventory will show up as empty.
Environment
Flux v2.2.0+

Weave-Gitops Version
Flux Version
Kubernetes version

To Reproduce
Steps to reproduce the behavior:

Expected behavior

Actual Behavior

Additional Context (screenshots, logs, etc)

We have a fix for this, but we don't plan to make a further release in 2023, the fix will go out in early 2024.

With the recent announcement, will this fix still go out?

We have a fix for this, but we don't plan to make a further release in 2023, the fix will go out in early 2024.
half of 2024 is gone and still you don't plan to make a further release ;)) fluxcd 2.3.0 released but still no update here :(

half of 2024 is gone and still you don't plan to make a further release ;)) fluxcd 2.3.0 released but still no update here :(

Weaveworks has been shut down, so it's possible that no one will make plans anymore.

It's still very confusing to not have a HUGE MESSAGE in Readme that this repository and product is abandoned

There are discussions between parties on this repository.
If you are interested in contributing it would be good to put a foot
forward.
On Sat, 2 Nov 2024 at 17:15, Bohdan Yurov @.***> wrote:

It's still very confusing to not have a HUGE MESSAGE in Readme that this
repository and product is abandoned
—
Reply to this email directly, view it on GitHub
https://github.com/weaveworks/weave-gitops/issues/4175#issuecomment-2453020086,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAA6C32AJ6M5M7A6FTLUTXLZ6TUBTAVCNFSM6AAAAABAZ4CWG6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINJTGAZDAMBYGY
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

This will be replaced by #4207


cmake: Cache PATH_TO_LLVM variable

Avoids the need to specify it again if we run cmake . from the build directory.

Nice one, thanks @gebart.
There is something odd with the CI, I'll look into it and merge the PR right after that.

Actually, I think that the failures are good - if the PR is coming from the outside of Mull repo, then we should not publish a package.
Otherwise, nothing will stop a potential malefactor from inserting malicious code and opening PR. If that happens, then we publish the malicious package under Mull repo on Bintray, potentially exposing the users to a threat.
I'll merge this as-is and then add this exception to the CI action.


Add QR Code scanner widget in Ensemble

See the QR code scanner used in Ensemble Live (it uses the qr_code_scanner package). This needs to be a first class widget in Ensemble so developers may be able to use in their apps.

@kmahmood74
Package QRCodeScanner - https://pub.dev/packages/qr_code_scanner
NOTE: It's mentioned that the qr_code_scanner package is in maintenance mode only
Sample EDL:
View:
  header:
    title: QR Code Scanner

  body:
    Column:
      styles: { gap: 30, margin: 30 }
      children:
        - QRCodeScanner:
            id: qrCodeScannerId
            styles:
              cutOutBottomOffset: 2
              cutOutHeight: 3
              cutOutWidth: 4
            formatsAllowed: [qrcode, rss14, upcA]
            initialCamera: front | back
            onReceived: |
              //@code
              console.log("Format: "+event.data.format);  // qrcode, rss14, upcA, aztec, etc
              console.log("Code: "+event.data.code);
              console.log("Raw Bytes: "+event.data.rawBytes); // Only supported for Android & iOS

        - Flow:
            styles: { gap: 16, mainAxis: center }
            children:
              - Button:
                  label: Flip Camera
                  onTap: |
                    //@code
                    qrCodeScannerId.flipCamera();

              - Button:
                  label: Flash ON/OFF
                  onTap: |
                    //@code
                    qrCodeScannerId.toggleFlash();

              - Button:
                  label: Pause Camera
                  onTap: |
                    //@code
                    qrCodeScannerId.pauseCamera();

              - Button:
                  label: Resume Camera
                  onTap: |
                    //@code
                    qrCodeScannerId.resumeCamera();

PRs:
ensemble_camera - https://github.com/EnsembleUI/ensemble_camera/pull/11
starter - https://github.com/EnsembleUI/starter/pull/41
ensemble - https://github.com/EnsembleUI/ensemble/pull/1260
Docs:
https://github.com/EnsembleUI/ensemble_docs/pull/154
Schema:

@vinothvino42 in the kitchen sink, make sure you linked your page from one of the screens on the home page otherwise it won't be visible. Then close this ticket

Added it next to the QRCode widget inside the Content Widgets


Inability to list search indexes is not properly detected

Bug Report

Q
A

BC Break
no

Version
2.8.1

Summary
Inability to list indexes is not properly detected anymore by the following lines of code:
https://github.com/doctrine/mongodb-odm/blob/2.8.1/lib/Doctrine/ODM/MongoDB/SchemaManager.php#L1060-L1063
Current behavior
With MongoDB 7.0.14, the error message is $listSearchIndexes stage is only allowed on MongoDB Atlas.
It does not contain Search index, so it's not recognized as unsupported command.
As such, the odm:schema:update command fails, even when there are no search indexes defined.
How to reproduce
Run the odm:schema:update command.
Expected behavior
The odm:schema:update does not fail when there are no search indexes defined.

Fixed in #2673.


Removing self-pings doesn't trigger a ghost ping alert

Overview
Removing a message containing a self-ping doesn't trigger a ghost ping alert.
Editing a self-ping out of a message also doesn't trigger an alert.
Expected Behaviour
Removing a message containing a self-ping triggers a ghost ping alert, as does editing out the ping.
(this may not be desirable, but it's at least consistent with the rest of the hassle that ghost pings bring)
Actual Behaviour
Neither method of removing the self-ping triggers a ghost ping alert. (see §Overview)

This is not a bug, it is intended behavior in both the update and delete handlers.


chore(release): fix more msr problems

Description
Another attempt at downgrading plugins by MSR which will break the rest of our release process.

/cc @nickboldt @rm3l


Check last rendered location for same-page visits

In #595 the logic for determining whether a visit is a "same page" visit was changed. Previously we were comparing the new location with the current location. In #595 we began comparing with the location of the last visit that was started.
This works great when all the visits are web visits. However, it introduced some problems with apps using the native adapters. In native apps, navigations can be a combination of native screens and WebView navigations, which means that we can't rely on the last visit having been sent.
This manifests as failing navigations in certain situations, such as navigating back from a native modal to a WebView. It also caused some problems restoring scroll positions when navigating back from one WebView to another.
Restoring the original logic prevents these problems.
This reverts commit 2e344b35d983fca636e064bc5ee1801c16908a04.

@domchristie could you please review this change.

Thanks @domchristie. Yes I think that other changes since your original PR have meant that the change was no longer necessary.


QA Documentation

As we get further into scaling into the future. I think this is a good point to write out a QA doc that can be used by the development team and community to QA the fractal product. I see this document will be a living document that should be revised as new features and updated are released.
I also recommend that these 'tasks' should be used in PRs. For example,  an update that 'touches' a certain feature or screen, when the PR is created, under a QA heading the relavant tasks should be copy/pasted into PR description.

Closing I don't think this needs to be tracked as QA gets worked on.


Improved 3d Layout methods to get location

Added 3d Layout component bounding_box property
Added 3d layout component clearance creation on soldermask

Maxime resolved the Vale error yesterday but making the heading in the error sentence case. Updating this branch should resolve it.


Apple ID get disabled after using this generator for 2 days

I was using this generator to generate around 300 emails in 2 days and my apple id get locked on this morning.
Does anyone encounter this issue? I think apple is limiting apple id creating hide my email

Did you ever get your AppleID enabled again?


Scroll to bottom of #scroll-locker

Challenge Name
https://www.freecodecamp.com/challenges/comparisons-with-the-logical-or-operator
Issue Description
This applies to any challenge with large contents.
The scroll to the bottom of #scroll-locker has some side effect, is scrolling the user on inital load.
We should not scroll when the JS does initial challenge run to populate tests

When going to a new challenge, I don't have time to read the instructions before the animation kicks in.
If you can disable the animation on page load, that would be much better.

@bouncey I agree


Consumer: extend unit tests

Test non-trivial properties of the current consumer implementation.
This provides an higher level of safety for the application, at the cost of testing some implementation details (e.g. a process is able to handle some form of failure coming from a monitored process).
Add specific test tags to allow finer-grained testing should implementation change in the future.
Based on #9.

Green CI, finally


Add new custom error type and refactor error handling

Closes #11
Closes #21

Note to self from https://blog.rust-lang.org/inside-rust/2021/07/01/What-the-error-handling-project-group-is-working-towards.html

An error type with a source error should either return that error via source or include that source's error message in its own Display output, but never both.


Add attributes (fixes #12332)

Description:

Return attributes
Upgrade speedtest-cli to 2.0.0

Related issue (if applicable): fixes #12332
Example entry for configuration.yaml (if applicable):
sensor:
  - platform: speedtest
    #server_id: 4205
    monitored_conditions:
      - ping
      - download
      - upload

Checklist:

[x] The code change is tested and works locally.

If the code communicates with devices, web services, or third-party tools:

[x] Local tests with tox run successfully. Your PR cannot be merged unless tests pass
[x] New dependencies have been added to the REQUIREMENTS variable ([example][ex-requir]).
[x] New dependencies are only imported inside functions that use them ([example][ex-import]).
[x] New dependencies have been added to requirements_all.txt by running script/gen_requirements_all.py.

I’ve noted that after 0.64 the home assistant process is getting killed after running the service sensor.update_speedtest. No error is printed on log.


Cover the latest changes in the specs such as string/array for path etc.

Cover the latest changes in the specs such as string/array for path etc.

@roll can we explicitly list these? Looks like this will be the very last issue I will work on so I want to make sure it is 100% clear in case it ends up being an 11th hour thing.

If you don't have any design/prototypes based on the specs from a few month ago then we could close this issue. So we're OK if we're reading current text of the spec.

@roll I just went through implementing that resource.path feature when developing that resource.iter() method. The array of paths can be an array of local paths or an array of remote paths but not a mix of both. So I think we're good?

@georgeslabreche
Can't be mixed. So yes :+1:


istioctl proxy-status missing old version sidecars

Bug description
We have used istioctl proxy-status to detect sidecars in the cluster. I have caught the command missing sidecars when:

The control plane is in a new version X (e.g., 1.9.0)
The data plane (sidecars) are in an older version Y (e.g., 1.5)

Essentially, in the middle of an upgrade.
[ ] Docs
[ ] Installation
[ ] Networking
[ ] Performance and Scalability
[ ] Extensions and Telemetry
[ ] Security
[ ] Test and Release
[x] User Experience
[ ] Developer Infrastructure
[x] Upgrade
Expected behavior
I expected istioctl proxy-status to list all sidecars.
Steps to reproduce the bug

Install Istio 1.5.7 and some workloads with sidecars
Upgrade control plane to 1.9.0
Run istioctl proxy-status

We don't support upgrades from istio 1.5 to 1.9. They are probably missing because a 1.5 proxy cannot actually connect to 1.9 Istio, so its actually reporting the truth?

Thanks @howardjohn. Yes, I'm aware of Istio's upgrade policy. Then I'm guessing that the istioctl command is not meant for the use-case of finding all Pods with sidecars in order to recreate them.
Finally, I wanted to ask if there is an authoritative way to find all Pods with sidecars. Thanks again for your help :)

It doesn't find all pods with sidecars, it finds all pods connected to Istiod. To find all pods with sidecars  you could look for the proxy v2 image in pod spec?

To see which pods have sidecars that need restart or are disconnected, try istioctl x injector list

Closing as working at intended. Thanks!


Implement inline stem macros using a Treeprocessor

The inline stem macros should be handled using a Treeprocessor instead of a Preprocessor. Generally, using Preprocessors should be avoided, especially for any official extension. The reason is that Preprocessors don't respect the AsciiDoc structure and can end up matching syntax that should not be interpreted.
Using a Treeprocessor does require a bit more work. You need to find all simple blocks in the tree (using find_by), then process the lines, then restore the processed lines. In other words, you are performing the inline substitution early.
If you really want to do it right, you also have to look for inline passthroughs and ignore those. But as a first attempted, I would recommend skipping that detail.
We really need to find a way in core to allow extensions to handle this macro.

You need something roughly like:
blocks = doc.find_by {|b| b.content_model == :simple }.each do |b|
  lines = b.lines
  # process lines
  b.lines = lines
end

If the Treeprocessor approach doesn't work, then I recommend using a Postprocessor. The Preprocessor should be the last choice.

Using my proposed approach, you can still reuse a lot of the logic you are currently using in the Preprocessor since you will still convert the inline stem macro to an image macro. You just process the lines from the Treeprocessor instead of from the Preprocessor.

I will try this approach and it shall make handling mathematical attributes and images dir much easier for inline stems.
Just one question. @mojavelinux. Does it means that when running as a Treeprocessor, each paragraph is a un-processed single line? I read from the asciidoctor source that Treeprocessor are running on ASTs, but it seems all inline macros are not built as AST nodes.

Nice to see this issue closed so quickly. @tstumm

Well that was @mojavelinux work ;)

I read from the asciidoctor source that Treeprocessor are running on ASTs, but it seems all inline macros are not built as AST nodes.

That is absolutely correct. The lines of the paragraph are unprocessed at the time the Treeprocessor runs.

I realized we may still be missing some nodes, such as the primary text of a list item. I also don't think the Treeprocessor runs on table cells yet. If I find that is the case, I'll submit a follow-up pull request.

I've sent a pull request to process inline stem macros in list items. That covers all the lists.
What remains is to process inline stem macros in table cells. Unfortunately, find_by doesn't descend into table cells, so we have to go find the cells ourselves.
At some point, someone is probably going to want to process inline stem macros in section titles as well. I haven't handled that yet.

I'm going to open separate issues for processing stem inline macros in normal table cells, AsciiDoc table cells, and section titles.


AzureListing gets a 403 error when used with our SAS connection URIs

I think we need to use ContainerSasPermissions, not Blob: https://docs.microsoft.com/en-us/python/api/azure-storage-blob/azure.storage.blob.containersaspermissions?view=azure-python


curl call between two ddev servers always routes to the server making the call

If I am running two ddev sites on the same host machine (say, site1.ddev.site and site2.ddev.site) then making a curl request from inside the site1 container to the url of site2 - this always shows the content from site1 (and vice versa).
To Reproduce
Spin up two plain php ddev instances (say, site1.ddev.site and site2.ddev.site), add an index.html file to both indicating their name (site1 or site2).
ddev ssh into site2 and execute curl site1.ddev.site. This will return site2 (should return site1, right?). The reverse is true if running from site1.
Example:
dmgig@site1-web:/var/www/html$ curl -i site2.ddev.site
HTTP/1.1 200 OK
Server: nginx
Date: Wed, 02 Dec 2020 17:38:18 GMT
Content-Type: text/html
Content-Length: 6
Last-Modified: Wed, 02 Dec 2020 17:24:09 GMT
Connection: keep-alive
ETag: "5fc7cdb9-6"
Accept-Ranges: bytes

site1

Note: There's no problem connecting to other sites while inside the ddev containers. Nor are there any problems connecting to either site from the host machine.
Expected behavior
When making a curl request from one ddev site to another from another ddev server, the connection should work and not point to the server making the request.
Version and configuration information (please complete the following information):

Host computer OS and Version: macOS Catalina
Docker Desktop version <IP_ADDRESS>
ddev version v1.16.0
config.yaml contents - default
Do you have any custom configuration (nginx, php, mysql) in the .ddev folder? No

Remember that *.ddev.site is a DNS wildcard that resolves to <IP_ADDRESS> (the same web container). So you won't be able to do what you're talking about without some modifications. Please see the FAQ on "How can two projects communicate with each other"
If you want to do exactly what you're now doing, you can create a `docker-compose.othersite.yaml with
version: '3.6'
services:
  web:
      external_links:
        - "ddev-router:secondsite.ddev.site"

Ah, okay -  thank you for your help.

If you want to do exactly what you're now doing, you can create a `docker-compose.othersite.yaml with
version: '3.6'
services:
  web:
      external_links:
        - "ddev-router:secondsite.ddev.site"

Terrific, thanks. I believe this would be worth adding in the FAQ at section "Can different projects communicate with each other?". At least that's where I was expecting to find this piece of information.

@felmab added in #2695  - thanks for the nudge.


Added 105

Added 105
Closes #16

This rule works as expected. However it fails integration tests because the functionality that adds the UASC field to the files (https://github.com/SocialFinanceDigitalLabs/quality-lac-data-beta-validator/pull/538 ) has not yet been merged hence the dummy data does not contain it.
For the same reason, 'UASC' has been provisionally added to the Header fields in the column_names object found in config.py .


Nima: HTTP/2  robustness and production quality code

Make sure we cover all that is needed:

exception handling
configurability
robustness (make sure we do not consume too much memory, implement backpressure where needed etc.)
fix all todos in code

I can have a look at this.


[Developer Portal] - API Console / Tryout with APIKey

API Manager version 3.0.0
Developer Portal
Tryout (Swagger based console)
Trying out the API Key based authorization approach
Authorize » Available Authorizations » api_key (APIKey)
Paste the generated APIKey and try the APIs

Issue:

The header created for the APIKey is api_key
WSO2 API Manager expects the header as apikey ( without the _ )
Check the generated curl command below.

curl -X GET "https://localhost:8243/v2/1.0.3/pet/4" -H  "api_key: eyJ4***-w==" -H  "Authorization: Bearer d912f***1e4b" -H  "accept: application/json"

Suggestion:
Either to use api_key as the header in API-M or to modify the API Console to generate header as apikey.

Duplicate https://github.com/wso2/product-apim/issues/6742


Not a bug: thanks for microui :)

Hi, just wanted to let you know that I've created a little microui sample on top of my cross-platform headers, here's the standard sample running in WebAssembly:
https://floooh.github.io/sokol-html5/wasm/sgl-microui-sapp.html
I need to improve a few input handling things (mobile touch input, and figuring out a better way to map my library's mouse-wheel input to yours), but these are minor things.
Also the default font atlas doesn't look too good on a high-dpi display when rendered at half resolution (I've had the same issues with Dear ImGui when using a TTF font, but Dear ImGui's default font looks fine in such situations, if a bit "low-tec": https://floooh.github.io/sokol-html5/wasm/imgui-sapp.html.
But anyway, these are minor issues, and not an issue with microui. Thanks for that neat little library :)

Oh wow! Would it be alright if I added a link to this in the README.md file?
Regarding the font: the demo program and atlas is meant only as a quick example, hence its crudeness; in practise one is expected to bring along their own font rendering.

Would it be alright if I added a link to this in the README.md file?

Of course :)

Thanks!