DSCP markings for Teams with ExpressRoute?

Under https://docs.microsoft.com/en-US/microsoftteams/qos-in-teams#choose-initial-port-ranges-for-each-media-type
It states "The following table shows the required DSCP markings for Teams with ExpressRoute" - I reckon that DSCP settings are the same regardless of ExpressRoute been used.

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

ID: 76c2487c-044d-1349-708a-5841fcb21ab8
Version Independent ID: b7033454-1a9c-48d4-8004-78415c5feb89
Content: Implement Quality of Service in Microsoft Teams
Content Source: Teams/QoS-in-Teams.md
Service: msteams
GitHub Login: @LanaChin
Microsoft Alias: v-lanac

@JorgeALeitao Thank you for submitting feedback and contributing to the docs. We are currently investigating this.

@jambirk - Can you follow up on this please?

fair comment: both Teams and Expressroute use these specific DSCP markings, and it's not the marking that's customizable here, just the port ranges.


data reproducibility

Hi,
I've tried to reproduce Zhang et al.'s result using your code (downloaded and run as is) but obtain very low accuracy numbers (25%) not at all near the paper's reported numbers.
Have you managed to reproduce their numbers?

Please see https://github.com/mhjabreel/CharCNN/issues/3 .
That's all we know.

Thanks, that is very helpful! I will change the optimizer to momentum and try again.


not an issue, an acknowledgment

I had looked for unzip a while back.  May I use this one?.

Of course.

On Aug 18, 2015, at 6:20 PM, Jeffrey Sarnoff<EMAIL_ADDRESS>wrote:
I had looked for unzip a while back. May I use this one?.
—
Reply to this email directly or view it on GitHub.


Backend/refactoring/small changes inspired by delete account

Various minor additions/changes. Biggest is a password_reset_token purge

Backend checklist

[x] Formatted my code by running autoflake -r -i --remove-all-unused-imports src && isort . && black . in app/backend
[ ] Added tests for any new code or added a regression test if fixing a bug
[x] All tests pass
[ ] Run the backend locally and it works
[ ] Added migrations if there are any database changes, rebased onto develop if necessary for linear migration history

I'm unsure what the workflow is with PR into a feature branch. Please do preparation cleanups as a PR against develop.

@kalvdans I did it against PR b/c I change make_invisible--which is used in PR--to delete_user. Plan would be to merge this once base PR has been merged.
Sorry, should have made a note.

Please mark it as draft until it can be merged.

We should just merge all the token deletion bg jobs into one. No need to run them separately.

On 21 Jul 2021, at 13:47, kalvdans @.***> wrote:

Please mark it as draft until it can be merged.
—
You are receiving this because your review was requested.
Reply to this email directly, view it on GitHub, or unsubscribe.

@aapeliv I was wondering that. I was also wondering about making a parent class and inheritance class for tokens. Thoughts on that? Might be worth doing both at once if we do.


no tar-ball or zip on pypi

Hi
1.0.5 doesn't seem to have a source release on pypi. Would be great to add it over there, especially for linux distribution who build their packages from these (I'm trying to package the latest version for opensuse).
(the changelog also doesn't seem to have 1.0.5 information)
thanks
Arun

Thank you.
https://pypi.python.org/pypi/piexif
http://piexif.readthedocs.io/en/latest/changes.html


Get or set entity health without changing the value internally

I believe we shouldn't change a value in Entity.Health, because it's obviously inconsistent with Entity.HealthFloat (the internal health value) and the ped threshold of death can be changed by changing the injury health threshold values. They can be changed via Ped.FatalInjuryHealthThreshold and Ped.InjuryHealthThreshold.

Fair enough.


Job is not executed within the execution window

I have set a non-periodic schedule for one of my job like this:
new JobRequest.Builder(PendingHttpRequestJob.TAG).setExecutionWindow(1_000L, 10_000L)
                .setRequiredNetworkType(JobRequest.NetworkType.NOT_ROAMING)
                .setBackoffCriteria(5_000L, JobRequest.BackoffPolicy.LINEAR)
                .setRequirementsEnforced(true)
                .setUpdateCurrent(true)
                .build()
                .schedule();

On some device I tested the job is not executed within the execution window, here is my log:
D/PlatformJobService: Run job, request{id=5, tag=PendingHttpRequestJob, transient=false}, waited 00:04:13, start 00:00:01, end 00:00:10
Do you have any ideas why this happend? Thanks

That's possible when the requirements aren't met and your job is rescheduled multiple times.

Is there any more hidden requirement other than the requirement I specify in the JobRequest.Builder? The log say reschedule count 0 so I don't think it was being rescheduled:
D/JobProxy21: Schedule one-off jobInfo success, request{id=10, tag=PendingHttpRequestJob, transient=false}, start 00:00:03, end 00:00:10 (from now), reschedule count 0
I/Timeline: Timeline: Activity_idle id: android.os.BinderProxy@3a973c21 time:57934670
I/art: Explicit concurrent mark sweep GC freed 30079(3MB) AllocSpace objects, 6(96KB) LOS objects, 62% free, 7MB/19MB, paused 821us total 93.531ms
D/PlatformJobService: Run job, request{id=10, tag=PendingHttpRequestJob, transient=false}, waited 00:02:27, start 00:00:03, end 00:00:10
I/JobExecutor: Executing request{id=10, tag=PendingHttpRequestJob, transient=false}, context PlatformJobService```
This is how I recreate the issue on that device: At the begining I turn off the network connection, schedule a job and then turn the network on asap. In the first try it is executed within the time range, but from the second try onward it is not.

What I have post is a full logs between these two.
This is the specs of the device that I have tested on:
Asus Zenpad
Model number: P024
Android version: 5.0.2

No luck, I tried without enforcing requirement and it is still the same

If it's a device specific issue, then there's nothing I can do. Can you provide a sample app that reproduces the issue in the emulator?

Nope, all the emulator I have tried on so far is behaving normally. I think it is really a device related issue then. Thanks for your feedback and great library.

The problem is that some devices delay jobs longer. There's nothing I can do about it. I rely on the JobScheduler API to start and execute jobs.

I know it might not be your fault, but it is still a critical error. When I try to schedule things for a longer period of time, the error in the alarm time only gets worse. Here's an example where it was off by almost 40 minutes:
D/PlatformJobService: Run job, request{id=362, tag=ModifyAlarm, transient=false}, waited 01:12:17, start 00:33:08, end 00:33:18
I/JobExecutor: Executing request{id=362, tag=ModifyAlarm, transient=false}, context PlatformJobService
I/JobExecutor: Finished job{id=362, finished=true, result=SUCCESS, canceled=false, periodic=false, class=ModifyAlarm, tag=ModifyAlarm}
D/PlatformJobService: Finished job, request{id=362, tag=ModifyAlarm, transient=false} SUCCESS

Please also keep Doze in mind. It won't always happen that the device meets all of your requirements.

OK, I know that this may be an obvious solution, but for me, the solution here was to use .setExact() instead of .setExecutionWindow(). This is probably less efficient/more draining for the battery, but I am building an alarm app, so it is pretty important for me that the alarm goes off at the right time. Therefore, if any other people come to this thread and feel like .setExecutionWindow() is not accurate enough for them, then I would suggest using .setExact() instead of .setExecutionWindow(). However, as discussed in this issue, using .setExact() requires AlarmManager which comes with its own potential set of problems with alarms not running after the app is killed.


Fix typos in doc/comments

@clvv
Thanks for merging it!
It's nice to see you're taking care of this nice project still.
I'd be happy to help out with triaging issues etc - because I got the impression that development on it got stalled a bit.  Can you please give some status of this?

There's a list of fixes that should be done. At this point, I don't see any good reason to have big changes made to the code base--fasd is very usable and stable as is. There are some things I said I would fix but never gotten the time to change the code and test things. If you have familiarity with POSIX shell scripting then you are more than welcome to take a try at it. Keep in mind that there are a lot of subtitles in syntax and semantics for the sake of compatibility. I will get this done eventually, when I get the time.
One big thing would be performance. However, there are a lot of variables in terms of versions of shell, sed, and awk to make this quantitative; same goes for functionality testing. It will be a big time investment to set up functionality and regression testing for fasd. I don't think I would have

Thanks for your info!
Tests would be nice.
FWIW I can recommend both https://github.com/sstephenson/bats and https://bitheap.org/cram/.


Problem with a group of plugs: power-sensor has no entities and doesn't show a value

Hi,
i have updated to v0.24.2. Everything is working fine so fare except one thing. I have groups of plugs witch have energy- and power-sensors created but only the energy-sensor shows a value
here the energy-sensor

and here the power-sensor

on the energy-sensor screenshot I can see the entities on the screenshot of the power-sensor not.
That is not the case if I look at a power-sensor of my light group for example.

Here are entities in the attribute section.
Here is my config:
- platform: template
  sensors:
    kwhprice:
      friendly_name: "Preis pro kWh"
      value_template: "0.2345"
      unit_of_measurement: "{currency}/kWh"
    strom_tarif:
      friendly_name: "Strom Tarif"
      value_template: "0.2345"
      unit_of_measurement: "EUR"

# original sensors are in W but I need kW
    dirks_homey_pro_leistung_kw:
      friendly_name: "Homey on / off plug Energysensor kW"
      unit_of_measurement: "kW"
      value_template: "{{ ( states('sensor.dirks_homey_pro_leistung') | float * 0.001) | round(5, 0) }}"
    steckdose_pc_schlafzimmer_power_consumption_kw:
      friendly_name: "PC Stecker kW"
      unit_of_measurement: "kW"
      value_template: "{{ ( states('sensor.steckdose_pc_schlafzimmer_power_consumption') | float * 0.001) | round(5, 0) }}"
    shelly_shplg_s_87e9c7_pc_current_consumption_kw:
      friendly_name: "PC Plug kW"
      unit_of_measurement: "kW"
      value_template: "{{ ( states('sensor.shelly_shplg_s_87e9c7_pc_current_consumption') | float * 0.001) | round(5, 0) }}"
    shelly_shplg_s_ea48f8_dm920_current_consumption_kw:
      friendly_name: "DM920 Plug kW"
      unit_of_measurement: "kW"
      value_template: "{{ ( states('sensor.shelly_shplg_s_ea48f8_dm920_current_consumption') | float * 0.001) | round(5, 0) }}"
    shelly_shplg_s_bc6caa_tv_current_consumption_kw:
      friendly_name: "TV Plug kW"
      unit_of_measurement: "kW"
      value_template: "{{ ( states('sensor.shelly_shplg_s_bc6caa_tv_current_consumption') | float * 0.001) | round(5, 0) }}"
    steckdose_tv_hd_power_consumption_kw:
      friendly_name: "Steckdose TV HD Power Consumption kW"
      unit_of_measurement: "kW"
      value_template: "{{ ( states('sensor.steckdose_tv_hd_power_consumption') | float * 0.001) | round(5, 0) }}"
    steckdosen_tv_box_leistung_kw:
      friendly_name: "Steckdosen TV Box - Leistung kW"
      unit_of_measurement: "kW"
      value_template: "{{ ( states('sensor.steckdosen_tv_box_leistung') | float * 0.001) | round(5, 0) }}"
    steckdose_kuche_power_consumption_kw:
      friendly_name: "Steckdose Küche Power Consumption"
      unit_of_measurement: "kW"
      value_template: "{{ ( states('sensor.steckdose_kuche_power_consumption') | float * 0.001) | round(5, 0) }}"
    steckdose_alexa_sz1_leistung_kw:
      friendly_name: "Steckdose Alexa SZ1 Leistung kW"
      unit_of_measurement: "kW"
      value_template: "{{ ( states('sensor.steckdose_alexa_sz1_leistung') | float * 0.001) | round(5, 0) }}"
    steckdose_ventilator_leistung_kw:
      friendly_name: "Steckdose Verntilator Leistung kW"
      unit_of_measurement: "kW"
      value_template: "{{ ( states('sensor.steckdose_ventilator_leistung') | float * 0.001) | round(5, 0) }}"

# Groups
- platform: powercalc
  create_group: Gruppe Wohnung
  entities:
    - create_group: Gruppe Wohnzimmer Gesamt
      entities:
        - create_group: Gruppe Wohnzimmer Licht Gesamt
          entities:
            - entity_id: light.wohnzimmerlampe
            - entity_id: light.tv_led_kette
              power_sensor_id: sensor.tv_led_kette_energysensor
            - entity_id: light.led_kette_wz
              linear:
                min_power: 0.4
                max_power: 24
            - entity_id: light.hue_play_gradient_lightstrip_1
              linear:
                min_power: 0
                max_power: 17.1
            - entity_id: light.stehlampe_wz
              linear:
                min_power: 0.6
                max_power: 13
        - create_group: Gruppe Wohnzimmer Plugs Gesamt
          entities:
            - entity_id: switch.steckdosen_tv_box_eingeschaltet
              power_sensor_id: sensor.steckdosen_tv_box_leistung_kw
              energy_sensor_unit_prefix: none
            - entity_id: switch.steckdose_tv_hd
              power_sensor_id: sensor.steckdose_tv_hd_power_consumption_kw
              energy_sensor_unit_prefix: none
              # TV Plug
            - entity_id: switch.shelly_shplg_s_bc6caa_tv
              power_sensor_id: sensor.shelly_shplg_s_bc6caa_tv_current_consumption_kw
              energy_sensor_unit_prefix: none
              name: "TV Plug"
              # DM920 Plug
            - entity_id: switch.shelly_shplg_s_ea48f8_dm920
              power_sensor_id: sensor.shelly_shplg_s_ea48f8_dm920_current_consumption_kw
              energy_sensor_unit_prefix: none
              name: "DM920 Plug"
    # Gruppe Schlafzimmer
    - create_group: Gruppe Schlafzimmer Gesamt
      entities:
        - create_group: Gruppe Schlafzimmer Licht Gesamt
          entities:
            - entity_id: light.schlafzimmerlampe
            - entity_id: light.nachttischlampe
              standby_power: 0.4
              fixed:
                power: 15
            - entity_id: light.pc_led_kette
              linear:
                min_power: 0.4
                max_power: 3
            - entity_id: light.led_kette_rechts
              linear:
                min_power: 0.4
                max_power: 3.1
        - create_group: Gruppe Schlafzimmer Plugs Gesamt
          entities:
            - entity_id: switch.steckdose_alexa_sz1_eingeschaltet
              power_sensor_id: sensor.steckdose_alexa_sz1_leistung_kw
              energy_sensor_unit_prefix: none
            - entity_id: switch.steckdose_pc_schlafzimmer
              power_sensor_id: sensor.steckdose_pc_schlafzimmer_power_consumption_kw
              energy_sensor_unit_prefix: none
              #PC Plug
            - entity_id: switch.shelly_shplg_s_87e9c7_pc
              power_sensor_id: sensor.shelly_shplg_s_87e9c7_pc_current_consumption_kw
              energy_sensor_unit_prefix: none
              name: "PC Plug"
            - entity_id: switch.steckdose_ventilator_eingeschaltet
              power_sensor_id: sensor.steckdose_ventilator_leistung_kw
              energy_sensor_unit_prefix: none
            - entity_id: light.homey_on_off_plug
              power_sensor_id: sensor.dirks_homey_pro_leistung_kw
              energy_sensor_unit_prefix: none
    # Gruppe Kueche
    - create_group: Gruppe Küche Gesamt
      entities:
        - create_group: Gruppe Küche Licht Gesamt
          entities:
            # Gruppe Kueche Spots
            - create_group: Gruppe Küche Spots Gesamt
              entities:
                - create_group: Gruppe Küche Spots Innen Gesamt
                  entities:
                    - entity_id: light.kuche_spot_2
                    - entity_id: light.kuche_spot_3
                - create_group: Gruppe Küche Spots Aussen Gesamt
                  entities:
                    - entity_id: light.kuche_spot_1
                    - entity_id: light.kuche_spot_4
            # Gruppe Kueche LED Ketten
            - create_group: Gruppe Küche LED Ketten Gesamt
              entities:
                - entity_id: light.kuhlschrank_led_kette
                - entity_id: light.spule_led_kette
            # Gruppe Kueche LED
            - create_group: Gruppe Küche LED Gesamt
              entities:
                - entity_id: light.kuhlschrank_led
                  standby_power: 0.4
                  fixed:
                    power: 11.4 #Power when the light is on
                - entity_id: light.spule_led
                  standby_power: 0.4
                  fixed:
                    power: 11.4 #Power when the light is on
        - create_group: Gruppe Küche Plugs Gesamt
          entities:
            - entity_id: switch.steckdose_kuche
              power_sensor_id: sensor.steckdose_kuche_power_consumption_kw
              energy_sensor_unit_prefix: none
        # Gruppe Flur
    - create_group: Gruppe Flur Gesamt
      entities:
        - entity_id: light.flurlampe

Thank you!

on the energy-sensor screenshot I can see the entities on the screenshot of the power-sensor not.
That is not the case if I look at a power-sensor of my light group for example.

The provide a screenshot for light group power sensor and not for energy sensor. How should this be compared otherwise?

Why are you creating all these template kW power sensors?
Powercalc is expecting all the sensors in the power group to be the same unit of measurement, all in W. Otherwise it will remove the non compatible power sensor from the group. That would be the reason you see 0.
Probably you see the following error in the logs:
Group member 'sensor.steckdose_kuche_power_consumption_kw' has another unit of measurement 'kW' than the group 'sensor.gruppe_kuche_plugs_gesamt' which has 'W', this is not supported yet. Removing this entity from the total sum.
Maybe I will have a look to convert units in the future, so a group can consist of power sensors from units W, kW, mW etc.
So long story short.
You should just add sensor.steckdose_tv_hd_power_consumption to the group and get rid of the template sensors.

Hi,
thank you! I think I did this because I had to high values in the sensor.
I will try that out...

on the energy-sensor screenshot I can see the entities on the screenshot of the power-sensor not.
That is not the case if I look at a power-sensor of my light group for example.>
Then provide a screenshot for light group power sensor and not for energy sensor. How should this be compared otherwise?
My bad
I have groups of plugs witch have energy- and power-sensors created but only the energy-sensor shows a value

Why do you think that 0 W is not a value - e.g. when everything is off? What are the values for the entities inside the group?

float
Because the plugs have been switched on all the time
It is a surprise that this is working at all, if you are not starting to use default for the floats, Search HA documentation for this.

@DirkStorck Just focus on the group power sensors first and make sure all the power sensors added to there are W sensors, either the ones you create with powercalc or the existing ones you include using power_sensor_id.
Than check under the power group attributes if all entities are listed correctly. And also check if the sum is correct.
So when you have 2 individual power sensors whith are 200 W and 300 W, the group sensor should show 500 W.
Next check if the group energy sensor is correct.
By default the energy sensor should show kWh, When you use energy_sensor_unit_prefix: None than the energy sensor will show wH

I have changed my configuration and have removed all template sensors and use the ones from the entity. But somehow the value for group
These are the plugs in the group witch are currently on

This is what I get for the daily group

And this is are the daily power sensor values

So if I could reset the daily power or energy sensor for any group would be great... UTILITY_METER.CALIBRATE didn't do anything
Thank you

You can reset the group energy and daily energy sensor using a service which powercalc provides.
It's in the readme here. https://github.com/bramstroker/homeassistant-powercalc#resetting-energy-sensor

For the utility meters (daily, monthly etc) you have to use UTILITY_METER.CALIBRATE, not sure why that is not working for you.

OK, thank you. Will try again.

@DirkStorck did you manage to get it to work? Can we close this issue?

Hi,
didn't had the time to look further into it till now, but yes issue can be closed. Working now.  Thank you!
I even found a way to reset all sensors at one time reset-values-of-utility-meter
1 - Remove the sensor from HA
2 - Restarting HA
3 - Deleting that device out of the ../homeassistant/.storage/core.restore_state file and then restarting HA.
4 - Once restarted, recreate the sensor with the same name and it was reset. I had to wait a minute or two for the energy meter to increase in value so the sensor would initialize.
To delete the senors (3.) I have used this page

thanks for posting the information. Can help others searching in the future.
Closing this issue.


YAML syntax error after changing settings in config.yml on Windows.

I just renamed identity to
vagrant_hostname: drupalvm8.dev vagrant_machine_name: drupalvm8
and ran vagrant up.
I have this error:
`Installing additional modules ...
Removing existing VirtualBox DKMS kernel modules ...done.
Removing existing VirtualBox non-DKMS kernel modules ...done.
Building the VirtualBox Guest Additions kernel modules ...done.
Doing non-kernel setup of the Guest Additions ...done.
You should restart your guest to make sure the new modules are actually used
mesg: ttyname failed: Inappropriate ioctl for device
==> drupalvm8: Checking for guest additions in VM...
==> drupalvm8: Setting hostname...
==> drupalvm8: Configuring and enabling network interfaces...
==> drupalvm8: Mounting shared folders...
drupalvm8: /vagrant => E:/VM/drupal-vm8
drupalvm8: /var/www/drupalvm => E:/VM/drupal-vm8
==> drupalvm8: Updating /etc/hosts file on active guest machines...
==> drupalvm8: Updating /etc/hosts file on host machine (password may be required)...
==> drupalvm8: Running provisioner: ansible_local...
drupalvm8: Installing Ansible...
drupalvm8: Running ansible-playbook...
ERROR! Syntax Error while loading YAML.
The error appears to have been in '': line 1, column 12, but may
be elsewhere in the file depending on the exact syntax problem.
Ansible failed to complete successfully. Any error output should be
visible above. Please fix these errors and try again.
`

@ArtuGit - If you're on windows, what editor did you use to save the YML file? You need to make sure you use an editor that can preserve line endings, like Notepad++, Sublime Text, or Atom, then also make sure the line endings are set to Unix, not Windows.

I have checked it.
http://screenpresso.com/=VCFje

I'm actually having the same problem on OSX.
I cloned the repo, then ran cp default.config.yml config.yml and then vagrant up. Oddly enough, when I did this same thing last night on my home Macbook, it seemed to work fine so I'm not sure what has happened between then and now.
==> drupalvm: Checking for guest additions in VM...
==> drupalvm: [vagrant-hostsupdater] Checking for host entries
==> drupalvm: [vagrant-hostsupdater] Writing the following entries to (/etc/hosts)
==> drupalvm: [vagrant-hostsupdater]   <IP_ADDRESS>  drupalvm.dev  # VAGRANT: 940a2291760556f379671ffc2e351e02 (drupalvm) / 1808c2d7-5320-47cb-8172-a4f13dddf633
==> drupalvm: [vagrant-hostsupdater]   <IP_ADDRESS>  www.drupalvm.dev  # VAGRANT: 940a2291760556f379671ffc2e351e02 (drupalvm) / 1808c2d7-5320-47cb-8172-a4f13dddf633
==> drupalvm: [vagrant-hostsupdater]   <IP_ADDRESS>  adminer.drupalvm.dev  # VAGRANT: 940a2291760556f379671ffc2e351e02 (drupalvm) / 1808c2d7-5320-47cb-8172-a4f13dddf633
==> drupalvm: [vagrant-hostsupdater]   <IP_ADDRESS>  xhprof.drupalvm.dev  # VAGRANT: 940a2291760556f379671ffc2e351e02 (drupalvm) / 1808c2d7-5320-47cb-8172-a4f13dddf633
==> drupalvm: [vagrant-hostsupdater]   <IP_ADDRESS>  pimpmylog.drupalvm.dev  # VAGRANT: 940a2291760556f379671ffc2e351e02 (drupalvm) / 1808c2d7-5320-47cb-8172-a4f13dddf633
==> drupalvm: [vagrant-hostsupdater]   <IP_ADDRESS>  dashboard.drupalvm.dev  # VAGRANT: 940a2291760556f379671ffc2e351e02 (drupalvm) / 1808c2d7-5320-47cb-8172-a4f13dddf633
==> drupalvm: [vagrant-hostsupdater] This operation requires administrative access. You may skip it by manually adding equivalent entries to the hosts file.
==> drupalvm: Setting hostname...
==> drupalvm: Configuring and enabling network interfaces...
==> drupalvm: Exporting NFS shared folders...
==> drupalvm: Preparing to edit /etc/exports. Administrator privileges will be required...
==> drupalvm: Mounting NFS shared folders...
==> drupalvm: Running provisioner: ansible_local...
    drupalvm: Installing Ansible...
    drupalvm: Running ansible-playbook...
ERROR! Syntax Error while loading YAML.

The error appears to have been in '<string>': line 1, column 12, but may
be elsewhere in the file depending on the exact syntax problem.

Ansible failed to complete successfully. Any error output should be
visible above. Please fix these errors and try again.

I just tried reproducing this by removing the geerlingguy/ubuntu1604 box, deleting my cloned repository and basically starting again. I did the same thing as above, clone, copy default.config.yml to config.yml and then vagrant up. Same problem. I'm puzzled because as I say on another machine I ran this on last night, it worked fine. Peculiar!

Just checked my vagrant version and it's at 1.8.1 which may well be the cause. I'm upgrading it now to the latest version and hopefully that might fix it. Perhaps @ArtuGit might want to check this too.

The error appears to have been in '<string>': line 1, column 12, but may
be elsewhere in the file depending on the exact syntax problem.

@welly this error is most likely a YAML syntax issue, try test it here -- http://www.yamllint.com/

@thom8 thanks for your suggestion, but it's all cleared up now after updating Vagrant.

I updated Vagrant, this problem disappeared.

Thank you all.


Support Async API's

Hi, migrating over from Mandrill (as I'm sure are many users).
Would love to see async non-blocking api's get added to the surface area.

Hi. I'm not a project member, only a new guy migrating from Mandrill.
It looks like the one implemented method is async already.
Is there something wrong with the current async implementation? Or are you missing the other non-implemented methods?

Ah, I hadn't actually looked at the code, just at the references from the documentation (which were all sync).

I wrote that method... and honestly, it was my first time writing any support for async.
The more eyes :eyes:, the better! :smile:

@ctolkien I believe this has been handled already -- a link to the code is here:
https://github.com/SparkPost/csharp-sparkpost/blob/eb21934481f9b94f6baf36d45110e6dd75369caf/src/SparkPost/RequestSender.cs#L17
If there's something wrong in this implementation, please let me know.  As I mentioned earlier, this is the first time I've written an OSS library with async support.  My plan is to make all API calls through this library go async.
I'm going to close this ticket, but please reopen if there is an issue with this implementation.


Support for syslog format RFC5424

Enhancement summary
RFC5424 is the current RFC for the syslog protocol. Although most of my customers aren't using RFC5424 directly, I have a few customers that require RFC5424 formatting. This feature request would allow users to configure and select RFC5424 as a logging format.
logging format rfc5424 is the command in EOS 4.30.3M.
AVD component impacted would be eos_cli_config_gen as that is where config for logging is done.
Which component of AVD is impacted
eos_cli_config_gen
Use case example
I don't have much experience with SIEM products, mainly logstash, but from what I hear they are fickle in what format they can receive syslog messages in. Fickle in the way that they can't easily be set up to accept both RFC5424 and RFC3126. Therefore and since RFC5424 obsoletes RFC3164 more and more SIEM systems default to RFC5424.
Describe the solution you would like
The solution I'd like is for eos_cli_config_gen to support the configuration of logging format rfc5424. Looking at the logging.j2 template this change seems straight forward as other logging format options are already supported.
Note that I haven't looked at creating tests for this, I also understand that there needs to be documentation created.
Describe alternatives you have considered
A direct alternative would be to create a custom template to attach to eos_cli_config_gen with suitable YAML.
Additional context
No response
Contributing Guide

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

Ok! let us know if you need any help!


NPE if OFunction name is empty

OrientDB Version, operating system, or hardware.

v2.1.19
v2.2 - only sources checked - issue exists

Expected behavior and actual behavior
OFunction.name property defined without "notNull" flag:
https://github.com/orientechnologies/orientdb/blob/862dd179ca269d1f9207e2d401f825dd56682c28/core/src/main/java/com/orientechnologies/orient/core/metadata/function/OFunctionLibraryImpl.java#L121-L127
But that throws NullPointerException here if for some reason user didn't specify name.
https://github.com/orientechnologies/orientdb/blob/862dd179ca269d1f9207e2d401f825dd56682c28/core/src/main/java/com/orientechnologies/orient/core/metadata/function/OFunctionLibraryImpl.java#L80

Hi @PhantomYdn
I just canged it and added a constraint for that
Thanks
Luigi


Karabiner makes other shortcuts with Escape not work

I have installed Karabiner and the shortcuts I had with Escape don't work anymore. For example, I can't open Terminal with VSCode using Shift+Escape. When I try to set up a new shortcut, pressing Escape closes the "Record shortcut" window (I tried that both in VSCode and WebStorm).
It doesn't have anything to do with my modifications since even if I turn them off the problem persists.

macOS version: 10.15.5 Catalina
Karabiner version: 12.10.0
Your Mac hardware: MacBook Pro 15 inch 2016 (with Touch Bar)
Your keyboard hardware: Internal keyboard of said laptop

Closing as I have accidentally posted this to a wrong repo, sorry


Remove unnecessary files at the end

🐛 Describe the bug
If you use this template on windows (or a platform where the unlink command doesn't keep the file open in the current process) removal of personalize.py before doing any work breaks the program. I worked around this by manually removing personalize.py instead of letting it unlink itself
Versions
python 3.9, latest template

7 months later.... 🤦 Sorry I missed this! Should be fixed by #112


[Change Request] Set default values to GraphStorm's gs.initialize() function

For users to initialize GraphStorm standalone environment more easier, need to set default argument value for initialize() method, i.e., ip_config=None, backend='gloo', device='cpu', and log_level='info'.

In order to facilitate convert code written in APIs to run with CLI interface, the GraphStorm need to provide gs.get_device() method for device setup internally in other classes, e.g., DataLoaders, Trainers, and Inferrers, without users' input.

Sample code
import graphstorm as gs
gs.initialize()

To Note: log_level is not set by gs.initialize

How about device? Can gs.initalize() set up device?


Shortcut Keys for Editor

It would be great to be able to use 'esc' to close out of the editor.
It would be great to be able to use Ctrl + Enter to save the image and close the editor.

Your suggestion is very good. It should be completed no later than this weekend. Thank you.

Shortcut key added

This works! Thank you!


Update dependencies for Senzing 3.8.0

See https://github.com/Senzing/senzing-tools/issues/137

Pull requests:

https://github.com/Senzing/check-self/pull/27


[Bug]: Setting heating mode on water tank also sets the climate entity to Heat

The problem
I noticed that recently, when I switch my water tank to heating on my Aquarea HP - the climate entity is also switched to heating (currently it's set to idle all the time considering the summer temps outside).
What's interesting is that I have the climate entity displayed as a separate graph and entity entry on Lovelace. Their status remains idle (even though when I go into history, I can clearly see, that the climate entity is set to Heat the moment the tank is set to heating). Only once the tank is switched to off, the climate entity updates to Heating.
I tried chaning the modes from Normal to Eco, tried manually using services to change modes - nothing changes the actual behavior. Still both the tank and climate get switched to Heating.
I enabled debug logging, and I found this line there:
2024-06-23 17:48:53.440 WARNING (MainThread) [homeassistant.components.climate] Entity None (<class 'custom_components.aquarea.climate.HeatPumpClimate'>) implements HVACMode(s): heat, off and therefore implicitly supports the turn_on/turn_off methods without setting the proper ClimateEntityFeature. Please create a bug report at https://github.com/cjaliaga/home-assistant-aquarea/issues
So here I am :)
What version of Home Assistant Core are you running?
This has been visible in HA 2024.5.5 and all of the recent ones.
What type of installation are you running?
Home Assistant OS
What version of the integration are you running?
v0.71
Device description
The pump here I don't think matters a lot. It's to me a purely data exchange between the integration and HA.
Is the integration loading?
Yes
Is the adapter able to connect to the Aquarea Smart Cloud with a stable internet connection?
Yes
Are you able to perform the action you're trying to with the Aquarea Smart Cloud Site/App?
Yes
Area of the issue
No response
Anything in the logs?
No response
Additional information
No response

Thanks @DorjeDorf, I'll take a look as soon as I can. The integration sends the current status + new changes to the Aquarea API and I tried to replicate their Web App behavior as much as I can so the integration is as consistent as possible. That said, the behavior that you describe doesn't look OK to me but I did that part long time ago so I might be forgetting something 😅
Trying to better understand the issue, let me see if I got it right:

Climate entity mode is Off
Tank entity is Off
Tank entity is switched to On (heating)
Climate entity mode changes to Heat

The mode and actions are different so I want to be sure I understand the issue, mode change versus action reporting.

Correct, although this might have been something on HA side.
I tried to reproduce it again today (running 2024.7.1 now, when reporting it was the last 2024.06) - and it no longer happens. The error in the logs no longer appears and the Climate entity also remains off.
For now, I'd say we can close the ticket, and reopen should this come back (hopefully not) :D


How can I convert into a blob file?

Hi, after this example code:
        console.log('Cropped Image Path!: ' + path);
        // Do whatever you want with new path such as read in a file
        // Here we resolve the path to finish, but normally you would now want to read in the file

How can I read this image and then convert to a blob file to can upload it?
Thanks!

Memory is blurry but I used cordova-plugin-file or cordova-plugin-file-transfer. Closing as this is not a bug.


while not use FileChannel.write()? rocketmq use mmap file write , may cause use a lot of share memory

here  is a test for FileChannel.write() , and mmap file write
https://github.com/jkreps/valencia/blob/master/src/test/java/valencia/TestLinearWritePerformance.java
what,s more , MaxDirectMemorySize dont work for memory hold by mmap file .

@Ah39 Compared with FileChannel, MMAP can write to the page cache directly, but FileChannel and use directbuffer need to write to  memory first, then write to the page cache. so RocketMQ has an advantage when writing a lot of small data into a file.

@duhengforever but the rocketmq may hold 100G even more SHR memory .
how to control the memory use by rocketmq ,by mmap file ??

@duhengforever but the rocketmq may hold 100G even more SHR memory .
how to control the memory use by rocketmq ,by mmap file ??

Maybe using the dio in the future will be a good choice,  memory management is entirely done by the application layer.


Conformance command to compute Lint Results based on API Style Guides

Summary
This pull request aims to add the conformance subcommand under the compute command in the registry CLI. This command, when passed the path of an API Spec, will compute and attach Lint objects as artifacts to the spec according to the API Style Guides defined on the project that contains the spec.
To go into detail, consider the following scenario: there are three API style guides present on the project named example that govern OpenAPI, AsyncAPI, and GraphQL specs. Then, the user calls
registry compute conformance projects/example/locations/global/apis/-/versions/-/specs/-

After this, the three style guides under the project are looked up. Each linter is configured to use the rules defined for it across all three style guides. For each spec, the mime type is looked up. If the mime type matches the mime type a linter supports (OpenAPI, AsyncAPI, or GraphQL), the linter is called on the spec, and the resulting Lint object is stored as an artifact on the spec.
Note
Currently, the Lint objects being attached are blank objects. In a subsequent pull request, the logic of the Spectral and API Linter plugins will be implemented, which will do the actual linting and populate the lint objects.
Test

Have registry running on localhost:8080.
Ensure that https://github.com/APIs-guru/openapi-directory is extracted to your Desktop.
Ensure that the following style guide is located under ~/styleguide.yaml:

name: openapistyleguide
mime_types:
  - application/x.openapi+gzip;version=2
guidelines:
  - name: refproperties
    display_name: Govern Ref Properties
    description: This guideline governs properties for ref fields on specs.
    rules:
      - name: norefsiblings
        description: An object exposing a $ref property cannot be further extended with additional properties.
        linter: spectral
        linter_rulename: no-$ref-siblings
        severity: 1
    status: 1
linters:
  - name: spectral
    uri: https://github.com/stoplightio/spectral

Now, run the following series of bash commands:
apg registry delete-project --name projects/example

apg registry create-project --project_id example --insecure --address localhost:8080

registry upload bulk openapi --project_id example ~/Desktop/openapi-directory/APIs

registry upload styleguide ~/styleguide.yaml --project_id=example

registry compute conformance projects/example/locations/global/apis/zappiti.com/versions/4.15.174/specs/swagger.yaml

registry list projects/example/locations/global/apis/zappiti.com/versions/4.15.174/specs/-/artifacts/-

Expected output:
projects/example/locations/global/apis/zappiti.com/versions/4.15.174/specs/swagger.yaml/artifacts/lint-spectral

@landrito regarding testing strategy, this PR is following an emerging pattern that's also used by tests in https://github.com/apigee/registry/tree/main/cmd/registry/cmd/upload and https://github.com/apigee/registry/tree/main/cmd/registry/cmd/label (for examples). Tests for individual commands are going alongside the code for the command (in the corresponding subdirectory). See #299 for some tests of the initial style guide uploader.

Sweet I'll get caught up on that strategy! Thanks


Report the version of cargo fmt and cargo clippy

Description
Fixes pyrsia/pyrsia#

This PR fixed #591
Screenshots (optional)
PR Checklist

[x] I've read the contributing guidelines.
[x] I've read "What is a Good PR?"
[x] I've included a good title and brief description along with how to review them.
[x] I've linked any associated an issue.
[] I've requested a review  from pyrsia/collaborators.

Code Contributions

[ ] I've built the code cargo build --all-targets successfully.
[ ] I've run the unit tests cargo test --workspace and everything passes.
[ ] I've made sure my rust toolchain is current rustup update.

Need to change .rs files to test it.


deps: enable Dependabot to upgrade base images

Description of the change:
This configures Dependabot (Github feature) to automatically create PRs whenever a newer base image is available.
Motivation for the change:
This simplifies the process of switching to a new base image after security patches are released.
Relates to #4763

/hold
Once this is reviewed by @fabianvf and @estroz we can remove the hold.

For the record, I am not against this PR :) just don't want it to have any adverse affects on things.

@kd7lxl how does dependabot look up viable replacements? For example, ansible-operator's image uses registry.access.redhat.com/ubi8/ubi:8.3-227 as a base; when 8.3-228 becomes available, would a PR be automatically created? Or when 8.4 is available? More generally, what is the granularity for updates?

@kd7lxl how does dependabot look up viable replacements? For example, ansible-operator's image uses registry.access.redhat.com/ubi8/ubi:8.3-227 as a base; when 8.3-228 becomes available, would a PR be automatically created? Or when 8.4 is available? More generally, what is the granularity for updates?

I'm just a user, but what I've observed is it seems to pretty well figure out what the greatest version number available following typical SemVer patterns. Here are some example of PRs it created in a repo that uses operator-sdk: https://github.com/infobloxopen/konk/pulls?q=is%3Apr+is%3Aclosed+label%3Adocker
The exact logic is here: https://github.com/dependabot/dependabot-core/blob/main/docker/lib/dependabot/docker/update_checker.rb#L110
Using the dependabot-core dev tools, I ran a dry run and the diff it spit out looks like this:
[dependabot-core-dev] ~/dependabot-core $ bin/dry-run.rb --dir images/helm-operator docker operator-framework/operator-sdk
warning: parser/current is loading parser/ruby26, which recognizes
warning: 2.6.7-compliant syntax, but you are running 2.6.6.
warning: please see https://github.com/whitequark/parser#compatibility-with-ruby-mri.
=> fetching dependency files
=> dumping fetched dependency files: ./dry-run/operator-framework/operator-sdk/images/helm-operator
=> parsing dependency files
=> updating 2 dependencies: golang, ubi8/ubi-minimal

=== golang (1.15)
 => checking for updates 1/2
 => latest available version is 1.16.3
 => latest allowed version is 1.16.3
 => requirements to unlock: own
 => requirements update strategy:
 => updating golang from 1.15 to 1.16.3

    ± Dockerfile
    ~~~
    2c2
    < FROM --platform=$BUILDPLATFORM golang:1.15 as builder
    ---
    > FROM --platform=$BUILDPLATFORM golang:1.16.3 as builder
    ~~~

=== ubi8/ubi-minimal (8.3-230)
 => checking for updates 2/2
 => latest available version is 8.3-298
 => latest allowed version is 8.3-298
 => requirements to unlock: own
 => requirements update strategy:
 => updating ubi8/ubi-minimal from 8.3-230 to 8.3-298

    ± Dockerfile
    ~~~
    20c20
    < FROM registry.access.redhat.com/ubi8/ubi-minimal:8.3-230
    ---
    > FROM registry.access.redhat.com/ubi8/ubi-minimal:8.3-298
    ~~~

Daily updates to a version containing a build number happen too frequently. It is probably fine to just pin to major+minor (and patch if available). Then I expect update PRs from this config to happen at an acceptable frequency, and I'd be ok with merging. @jmrodri thoughts?

Actual change frequency of these image tags appears to be once every few months, not a daily build:

golang images are released for each patch version.
The daily part of the Dependabot config means that it will check for the latest version once per day. If you prefer weekly PRs, weekly is another option. More details: https://docs.github.com/en/code-security/supply-chain-security/configuration-options-for-dependency-updates#scheduleinterval

Ah I thought the build number was sequential, but it looks like it skips ahead. In that case I'm fine with this addition as-is. Thanks!
/retest

/hold cancel

/retest


Investigate ___zig_probe_stack on Intel Macs

Note we use ReleaseFast to disable the stack probe which causes issues on Intel Macs.
We see the following error in CI
   Undefined symbols for architecture x86_64:
   "___zig_probe_stack", referenced from:
       _debug.panicExtra__anon_3134 in libhost.a.o)
       _debug.panicExtra__anon_3136 in libhost.a.o)
       _debug.panicExtra__anon_3730 in libhost.a.o)
       _debug.panicExtra__anon_4078 in libhost.a.o)
       _debug.ModuleDebugInfo__struct_4612.loadOFile in libhost.a.o)
       _dwarf.DwarfInfo.getLineNumberInfo in libhost.a.o)
       _debug.printLineFromFileAnyOs__anon_7202 in libhost.a.o)
       ...
   ld: symbol(s) not found for architecture x86_64

Need to investigate and figure out if there is anything wrong here. Update build.roc etc...

I think, you have to set stack_check to false. Here is an example how it is done with zig 0.13: https://github.com/ostcar/roc-aoc-platform/blob/43064f864b7a9c1c8db452c85b108bbbe917d3c3/build.zig#L77


Better Reference Documentation

Hey all,
I'm trying to get up and running on a project with Neat 2.0. I have a project that was already using it and I'm struggling with figuring out how to replace older functions/mixins and such. outer-container; and span-columns; are gone so it's hard to figure out what to use in their place. Obviously, I can read what's there and then trial and error things. It's just difficult. Are there plans to provide better reference material?
Thanks for all the work here. I'm excited!

Hi @digisavvy,
I'm not sure regarding the plans for documentation, but in the meantime, the 2.0 equivalent to outer-container -> grid-container, and span-columns -> grid-column

Related, but a "upgrade guide" of sorts would be really helpful.

Thanks @kgcreative! I did get myself sorted out and I do like how simplified Neat has become. An upgrade guide would be useful. I didn't have to change too much, just the functions noted there.


Add the documentation for actions

@jasonpet I moved the actions.md here from openwhisk/docs.

@houshengbo - Carlos already has a PR to update actions.md in openwhisk based on the recent package/action changes.  We need to check with him to see if he wants it in both repositories.  If so we should use the one that he is updating.
https://github.com/openwhisk/openwhisk/pull/1257

@houshengbo - I am closing this.  Carlos wants actions.md to only live in openwhisk.  He is updating it as I mentioned above.


Want to have an API visible to test to clean SharedPreferences._instance

Propose to to add API for test in sharedPreferences:
 @visibleForTesting
  static void resetSharedPreferences() {
       _instance = null;
  }

I'm writing on some test around my code wrapped around  SharedPreferences.
I created a class that simulated the native side of the channel:
class FakeSharedPreferences {
  final Map<String, Object> data;

  FakeSharedPreferences(MethodChannel channel, this.data) {
    channel.setMockMethodCallHandler(handler);
  }

  Future<dynamic> handler(MethodCall methodCall) async {
    print("RPC: $methodCall");

    switch (methodCall.method) {
      case 'getAll':
        return data;
      case 'setString':
      case 'setStringList':
        data[methodCall.arguments['key']] = methodCall.arguments['value'];
        return true;
      case 'remove':
        data.remove(methodCall.arguments['key']);
        return true;
      case 'clear':
        data.clear();
        return true;
      default:
        print("Not implemented ${methodCall.method}");
    }
  }
}

I'll reset the fake class in every test, but I found my tests still failing due to the _instance singleton instance. It is so bad, that my different tests might heavily impact on each other. But it can be fixed quite easily

Is there any workaround available for this, I'm guessing not because that _instance singleton is inaccessible.

Closing as obsolete; setMockInitialValues addresses this use case.


creating RDS Data base Read Replica error

An instance of type db.t2.micro can't be a primary for the oracle-ee engine.
(Service: AmazonRDS; Status Code: 400; Error Code: InvalidParameterCombination; Request ID: b5cffb45-8f74-41de-ac1a-fde6d47bfa62)

db.t2.micro is not work for oracle-ee engine.
db.m5.large is work for oracle Enterprise Edition engine

use MySQL

yes worked for MySQL....thanks!!

close issue


[Gekidou] Remove react-native-youtube and allow the link to be handled natively

Summary
This PR removes the dependency on react-native-youtube and allows the open link functionality to open the link natively either by the universal link or to fallback to a browser.
The reason for this is cause on iOS the library keeps on breaking every other month as it is using a dependency on itself that goes against the Terms of Service of YouTube and that was done in order to be able to play YT videos on a standalone video player.
The other option was to play the video inside a WebView container that is not really a great experience.
Ticket Link
https://mattermost.atlassian.net/browse/MM-43891
NONE

Building app in separate branch.

Successfully building:
https://circleci.com/gh/mattermost/mattermost-mobile/22334
https://circleci.com/gh/mattermost/mattermost-mobile/22333

Artifact links:
https://output.circle-artifacts.com/output/job/541b8ba7-22aa-4807-a355-c88b6ea5fb65/artifacts/0/tmp/artifacts/Mattermost_Beta.ipa
https://output.circle-artifacts.com/output/job/06c9f7f3-15cb-4ea2-bea2-26f7f72834ac/artifacts/0/tmp/artifacts/Mattermost_Beta.apk

@matthewbirtch thumbnails should work just fine for me (same video)

@matthewbirtch thumbnails should work just fine for me (same video)

Hmm, ok, something weird with my install then? I'll leave it. I'm seeing it the same way in v1 actually too.
I have a few styling comments, but I'm going to create a separate ticket for this.


Execution failed for task ':app:mergeExtDexDebug'.

 What went wrong:
Execution failed for task ':app:mergeExtDexDebug'.
> Could not resolve all files for configuration ':app:debugRuntimeClasspath'.
   > Failed to transform play-services-location-21.1.0.aar (com.google.android.gms:play-services-location:21.1.0) to match attributes {artifactType=android-dex, asm-transformed-variant=NONE, dexing-enable-desugaring=true, dexing-enable-jacoco-instrumentation=false, dexing-is-debuggable=true, dexing-min-sdk=23, org.gradle.category=library, org.gradle.libraryelements=jar, org.gradle.status=release, org.gradle.usage=java-runtime}.
      > Execution failed for DexingWithClasspathTransform: /Users/mahmoudazab/.gradle/caches/transforms-3/aded9d2bdb06f1cc5511342cdcf23559/transformed/jetified-play-services-location-21.1.0-runtime.jar.
         > Error while dexing.
   > Failed to transform kotlin-stdlib-1.9.0.jar (org.jetbrains.kotlin:kotlin-stdlib:1.9.0) to match attributes {artifactType=android-dex, asm-transformed-variant=NONE, dexing-enable-desugaring=true, dexing-enable-jacoco-instrumentation=false, dexing-is-debuggable=true, dexing-min-sdk=23, org.gradle.category=library, org.gradle.libraryelements=jar, org.gradle.status=release, org.gradle.usage=java-runtime}.
      > Execution failed for DexingWithClasspathTransform: /Users/mahmoudazab/.gradle/caches/transforms-3/e19d3b32fe7a928919a7681637e41f52/transformed/jetified-kotlin-stdlib-1.9.0.jar.
         > Error while dexing.

* Try:
> Run with --stacktrace option to get the stack trace.
> Run with --info or --debug option to get more log output.
> Run with --scan to get full insights.
> Get more help at https://help.gradle.org.

BUILD FAILED in 1m 56s

┌─ Flutter Fix ──────────────────────────────────────────────────────────────┐
│ [!] The shrinker may have failed to optimize the Java bytecode.            │
│ To disable the shrinker, pass the `--no-shrink` flag to this command.      │
│ To learn more, see: https://developer.android.com/studio/build/shrink-code │
└────────────────────────────────────────────────────────────────────────────┘
Error: Gradle task assembleDebug failed with exit code 1

buildscript {
ext.kotlin_version = '1.8.21'
repositories {
google()
mavenCentral()
}
dependencies {
    classpath 'com.android.tools.build:gradle:7.4.2'
    classpath "org.jetbrains.kotlin:kotlin-gradle-plugin:$kotlin_version"
    classpath 'com.google.gms:google-services:4.4.1'
}

}
allprojects {
repositories {
google()
mavenCentral()
}
}
rootProject.buildDir = '../build'
subprojects {
project.buildDir = "${rootProject.buildDir}/${project.name}"
}
subprojects {
project.evaluationDependsOn(':app')
}
tasks.register("clean", Delete) {
delete rootProject.buildDir
}

def localProperties = new Properties()
def localPropertiesFile = rootProject.file('local.properties')
if (localPropertiesFile.exists()) {
localPropertiesFile.withReader('UTF-8') { reader ->
localProperties.load(reader)
}
}
def flutterRoot = localProperties.getProperty('flutter.sdk')
if (flutterRoot == null) {
throw new GradleException("Flutter SDK not found. Define location with flutter.sdk in the local.properties file.")
}
def flutterVersionCode = localProperties.getProperty('flutter.versionCode')
if (flutterVersionCode == null) {
flutterVersionCode = '44'
}
def flutterVersionName = localProperties.getProperty('flutter.versionName')
if (flutterVersionName == null) {
flutterVersionName = '24.0'
}
apply plugin: 'com.android.application'
apply plugin: 'kotlin-android'
apply from: "$flutterRoot/packages/flutter_tools/gradle/flutter.gradle"
apply plugin: 'com.google.gms.google-services'
def keystoreProperties = new Properties()
def keystorePropertiesFile = rootProject.file('key.properties')
if (keystorePropertiesFile.exists()) {
keystoreProperties.load(new FileInputStream(keystorePropertiesFile))
}
android {
namespace "ccccccc"
compileSdkVersion 34
ndkVersion flutter.ndkVersion
compileOptions {
    sourceCompatibility JavaVersion.VERSION_1_8
    targetCompatibility JavaVersion.VERSION_1_8
}

kotlinOptions {
    jvmTarget = '1.8'
}

sourceSets {
    main.java.srcDirs += 'src/main/kotlin'
}

defaultConfig {
    // TODO: Specify your own unique Application ID (https://developer.android.com/studio/build/application-id.html).
    applicationId "ccccccc"
    // You can update the following values to match your application needs.
    // For more information, see: https://docs.flutter.dev/deployment/android#reviewing-the-gradle-build-configuration.
    minSdkVersion 23
    targetSdkVersion 34
    versionCode flutterVersionCode.toInteger()
    versionName flutterVersionName
    multiDexEnabled true
}
signingConfigs {
    release {
        keyAlias keystoreProperties['keyAlias']
        keyPassword keystoreProperties['keyPassword']
        storeFile keystoreProperties['storeFile'] ? file(keystoreProperties['storeFile']) : null
        storePassword keystoreProperties['storePassword']
    }
}
buildTypes {
    release {
        signingConfig signingConfigs.release
    }
}

}
flutter {
source '../..'
}
dependencies {
implementation "org.jetbrains.kotlin:kotlin-stdlib-jdk7:$kotlin_version"
implementation 'com.android.support:multidex:1.0.3'
implementation platform('com.google.firebase:firebase-bom:31.1.0')
// implementation 'com.google.firebase:firebase-analytics-ktx'
}

Hi @mazab99, can you try the comments in  https://stackoverflow.com/questions/78019106/getting-error-while-dexing-after-upgrading-flutter-to-3-19-0 to see if they help?
Also, you do not need to manually add the multidex library to your android project if you're using minSdkVersion greater than 20. Also, if you are using flutterfire, the flutterfire plugins already add the firebase bom so you do not need to manually add it to your build.gradle

I add ed firebase using cli
should I remove
classpath 'com.google.gms:google-services:4.4.1'
and
id "com.google.gms.google-services"

You need classpath 'com.google.gms:google-services:4.4.1' and id "com.google.gms.google-services"
Can you try removing the multidex from the app to see if it helps?

FAILURE: Build failed with an exception.

What went wrong:
Execution failed for task ':app:compileDebugKotlin'.

A failure occurred while executing org.jetbrains.kotlin.compilerRunner.GradleCompilerRunnerWithWorkers$GradleKotlinCompilerWorkAction
Compilation error. See log for more details

Try:

Run with --stacktrace option to get the stack trace.
Run with --info or --debug option to get more log output.
Run with --scan to get full insights.
Get more help at https://help.gradle.org.

BUILD FAILED in 8s
BUILD FAILED in 8s
┌─ Flutter Fix ──────────────────────────────────────────────────────────────────────────────┐
│ [!] Your project requires a newer version of the Kotlin Gradle plugin.                     │
│ Find the latest version on https://kotlinlang.org/docs/releases.html#release-details, then │
│ update /Volumes/D/HighQ Apps/1 - Clean                    │
│ Arch/droplet_clean_arc/android/build.gradle:                                               │
│ ext.kotlin_version = ''                                                    │
└────────────────────────────────────────────────────────────────────────────────────────────┘
Error: Gradle task assembleDebug failed with exit code 1

@danagbemava-nc  still the same issue

Hi @mazab99, please share the current content of the following files.

android/build.gradle
android/app/build.gradle

Hi  @danagbemava-nc , I am facing same issue after updating my flutter sdk. I have also tried all the methods you advised @mazab99

@Tolulope05, can you share the files in https://github.com/flutter/flutter/issues/144600#issuecomment-1985115228? It would also help if we could get a complete minimal reproducible code sample without any third-party plugins so that we can investigate this

Hy @danagbemava-nc , I am facing the same issue after updating Flutter.
here is the file content
android/build.gradle
`buildscript {
ext.kotlin_version = '1.9.23'
repositories {
google()
mavenCentral()
}
dependencies {
    classpath 'com.android.tools.build:gradle:7.4.2'
    classpath "org.jetbrains.kotlin:kotlin-gradle-plugin:$kotlin_version"
}

}
allprojects {
repositories {
google()
mavenCentral()
}
}
rootProject.buildDir = '../build'
subprojects {
project.buildDir = "${rootProject.buildDir}/${project.name}"
}
subprojects {
project.evaluationDependsOn(':app')
}
tasks.register("clean", Delete) {
delete rootProject.buildDir
}
`
android/app/build.gradle
`plugins {
id 'com.android.application'
id 'kotlin-android'
}
def localProperties = new Properties()
def localPropertiesFile = rootProject.file('local.properties')
if (localPropertiesFile.exists()) {
localPropertiesFile.withReader('UTF-8') { reader ->
localProperties.load(reader)
}
}
def flutterRoot = localProperties.getProperty('flutter.sdk')
if (flutterRoot == null) {
throw new GradleException("Flutter SDK not found. Define location with flutter.sdk in the local.properties file.")
}
def flutterVersionCode = localProperties.getProperty('flutter.versionCode')
if (flutterVersionCode == null) {
flutterVersionCode = '1'
}
def flutterVersionName = localProperties.getProperty('flutter.versionName')
if (flutterVersionName == null) {
flutterVersionName = '1.0'
}
apply from: "$flutterRoot/packages/flutter_tools/gradle/flutter.gradle"
android {
namespace "com.example.medista"
compileSdkVersion flutter.compileSdkVersion
ndkVersion flutter.ndkVersion
compileOptions {
    sourceCompatibility JavaVersion.VERSION_1_8
    targetCompatibility JavaVersion.VERSION_1_8
}

kotlinOptions {
    jvmTarget = '1.8'
}

sourceSets {
    main.java.srcDirs += 'src/main/kotlin'
}

defaultConfig {
    // TODO: Specify your own unique Application ID (https://developer.android.com/studio/build/application-id.html).
    applicationId "com.revca.medassist"
    // You can update the following values to match your application needs.
    // For more information, see: https://docs.flutter.dev/deployment/android#reviewing-the-gradle-build-configuration.
    minSdkVersion 21
    targetSdkVersion 33
    versionCode flutterVersionCode.toInteger()
    versionName flutterVersionName
}
buildTypes {
    release {
        // TODO: Add your own signing config for the release build.
        // Signing with the debug keys for now, so `flutter run --release` works.
        signingConfig signingConfigs.debug
        minifyEnabled true
        shrinkResources true
        proguardFiles getDefaultProguardFile('proguard-android-optimize.txt'), 'proguard-rules.pro'
    }
}

}
flutter {
source '../..'
}
dependencies {
implementation "org.jetbrains.kotlin:kotlin-stdlib-jdk7:$kotlin_version"
}
`

Hi @MeghanshuKumrawat, can you try migrating to the new gradle syntax? You can find the migration guide here https://flutter.dev/go/flutter-gradle-plugin-apply.
Please also make sure your version of kotlin is compatible with your AGP version

Hi @mazab99, can you try the comments in https://stackoverflow.com/questions/78019106/getting-error-while-dexing-after-upgrading-flutter-to-3-19-0 to see if they help?
Also, you do not need to manually add the multidex library to your android project if you're using minSdkVersion greater than 20. Also, if you are using flutterfire, the flutterfire plugins already add the firebase bom so you do not need to manually add it to your build.gradle

The Stackoverflow solution worked for me.


Catching up swift-ast changes

Codecov Report

Merging #29 into master will decrease coverage by <.01%.
The diff coverage is 87.5%.

@@            Coverage Diff             @@
##           master      #29      +/-   ##
==========================================
- Coverage    97.7%   97.69%   -0.01%
==========================================
  Files          52       52
  Lines        2829     2823       -6
  Branches      127      127
==========================================
- Hits         2764     2758       -6
  Misses         63       63
  Partials        2        2


has plan to Migration to httpclient 5 ?

Is your feature request related to a problem? Please describe.
Current dependency httpclient 4.x, it dependency commons-logging, httpclient 5.x used sl4j, has plan to migration?
Describe the solution you'd like
migration from httpclient4.x, see this migration-guide.

It's a transitive dependency from long unmantained com.ecwid.consul:consul-api, check https://github.com/spring-cloud/spring-cloud-consul/pull/840 for latest work on replacing this.

closing in favor of #840


Data Sharding in Redis replication mode

Expected behavior
How to achieve Data Sharding in Redis replication mode through jedis
Sharding (MD5, MurmurHash)
Key-tags for sharding
Sharding with pipelining
Redis / Jedis Configuration -- One master and two slaves.
Jedis version: 2.8
Redis version: 3.2
Java version: 1.8

@vishalsharma13 please post this question in the Jedis mailing list as github is for code bugs or design discussions mainly.
http://groups.google.com/group/jedis_redis


2.0.0a4 is ~2.5 times slower than 0.8.4

Was benchmarking and noticed that mistune 2.0.0a4 is around 2.5 times slower than 0.8.4 on the benchmark suite over at https://github.com/miyuchina/mistletoe. The results I got were surprising:
mistune 0.8.4: 8.952760785999999
mistune 2.0.0a4: 23.15826605300026

Interestingly, this puts mistune's speed at a comparable level to mistletoe, which has a far more robust and spec-compliant parser. Is this something that you are looking to fix with the final 2.0 release?

I'm not sure if it can be faster in mistune v2. I'll still work on it. But v0.8.4 is not robust, there are cases which will make 0.8.4 very slow.
As for spec-compliant? I think you mean Commonmark. Commonmark cares too much about weird cases instead of normal cases.
For instance, In Commonmark:
[<https://lepture.com>](/hello)

Will be rendered as:

https://lepture.com

This is certainly wrong. And they defined many rules for weird cases that I personally don't like. Just like John Gruber said in https://twitter.com/gruber/status/507615356295200770:

Only two maybes I’ve thought of: Strict Markdown or Pedantic Markdown. “Strict” still doesn’t seem right.

If you like a "strict" common mark, mistune is not your choice.

Not an issue report, close it.


Require Wield To Activate Double-bladed ESword

About the PR
Despite being balanced around being wielded, the double-bladed esword could be swung using only one hand if activated on the ground and then picked up. Now, the double-bladed esword can only be activated by wielding it, and can not be activated on the ground. This means that throwing it, putting it down, or dropping it turns the blade off.
Why / Balance
Fixes #32772 and enforces intended weapon balancing.
Technical details
Add onActivate: false component to the double esword, preventing it from being activated outside of the user wielding it.
Requirements

[x] I have read and am following the Pull Request and Changelog Guidelines.
[x] I have added media to this PR or it does not require an ingame showcase.

Changelog

:cl:

tweak: The double-bladed esword now can only be activated when wielded.

Hopefully this doesnt break the syndie assault borg's esword?

Hopefully this doesnt break the syndie assault borg's esword?

I tested both, and this does not affect the [one handed] variant that the borgs use

I have realized that the double bladed esword is more broken than I had originally thought. If you enable it on the floor and then pick it up, you can no longer attack with it, but the model is broken as it pairs the wielded blades with the unwielded handle. Looks like I will have to turn it off on pickup

This change also prevents people from attacking with it when it is unpowered as well, so I am going to have to look into degerming if it is powered on or off

I have realized that the double bladed esword is more broken than I had originally thought. If you enable it on the floor and then pick it up, you can no longer attack with it, but the model is broken as it pairs the wielded blades with the unwielded handle. Looks like I will have to turn it off on pickup

Some of this is fixed in the hypereutactic blade PR, so you can lift some of the fixes from that

I have modified how I've gone about this
Initially I had added the MeleeRequiresWield component, but that had a few unintended side effects:

You could not attack with the weapon turned off
You still get the benefit of the high reflect chance
The sprite is completely broken

The route i have gone now, is adding the parameter onActivate: false to the itemToggle component. This has one issue which is not game breaking or vital:

You can no longer put down, drop, or throw the weapon without it deactivating

However, this has the pros of:

You can attack with the weapon turned off
You no longer get the benefits of the high reflect chance without wielding it
The sprite behaves as intended
You can no longer have the activated weapon in one hand

I have modified how I've gone about this
Initially I had added the MeleeRequiresWield component, but that had a few unintended side effects:
* You could not attack with the weapon turned off

* You still get the benefit of the high reflect chance

* The sprite is completely broken

The route i have gone now, is adding the parameter onActivate: false to the itemToggle component. This has one issue which is not game breaking or vital:
* You can no longer put down, drop, or throw the weapon without it deactivating

However, this has the pros of:
* You can attack with the weapon turned off

* You no longer get the benefits of the high reflect chance without wielding it

* The sprite behaves as intended

* You can no longer have the activated weapon in one hand

https://github.com/space-wizards/space-station-14/pull/32414/files#diff-f50dce3ddc3b090c3a6851ce337a78cf0d86c78cc10eb8061f630a8106d7e4c6
MeleeRequiresWield works for this.
You need to do some sprite renaming for it to work properly.

https://github.com/space-wizards/space-station-14/pull/32414/files#diff-f50dce3ddc3b090c3a6851ce337a78cf0d86c78cc10eb8061f630a8106d7e4c6
MeleeRequiresWield works for this. You need to do some sprite renaming for it to work properly.

This does prevent the user from attacking with the weapon in one hand, which is part of the issue, but it does not take into account if the weapon is activated or not. So if someone wants to hit someone with the blades disabled, it prevents them.
This would also require new sprites, as the Dsword does not have a sprite for an unwielded blade, only an unwielded handle and wielded blades.
The main issue with allowing it to be used in one hand is the high reflect chance. If you have it in one hand, you still have the benefit of the 75% reflect chance, which is balanced under the assumption that it will only be held in both hands. In comparison to the eshield it has a lower reflect chance, but it also doesn't burn out and provides a constant reflection bonus.
In my implementation, it prevents the dsword not only from attacking with one hand, but it also prevents it from providing its above average reflection chance.


Improve path copy/move/delete support for multi nodes

Currenty one can not do something like:

select a tree node (eg. /home/user/)
press m
choose copy or move
add two levels or more deep nodes (eg /home/user/folder/file.py)

NERDTree will copy, move, or delete folders just fine. At least it does now in 2016. The problem may have been in your example. It looks like you're trying to move or copy a folder to a location within itself. This is impossible in any environment without runaway recursion. I'm closing this issue, but it can be reopened with additional description if necessary.


What was the latest average loss?

Hi,
In the readme file, it says:

Dump of generated texts from gpt-2-simple trained on Hacker News titles until April 25th, 2019 (about 603k titles, 30MB of text) for 36,813 steps (12 hours w/ a P100 GPU, costing ~$6). The output is definitely not similar to that of Markov chains.

My questions are:

What was the latest avg_loss you've reached?
Which model (117M or 345M) did you train it with?
Which parameters (especially talking about learning rate) did you use?

Answers to these questions can give us more intuition while training the gpt-2-simple on our datasets.
Thanks for your answer!

FWIW, I've replicated this for another project with 100k steps on a P100. The final loss was somewhere between 0.85 and 0.98 IIRC. I trained on the 345M. The params were the same as in @minimaxir GPT2-simple Colab notebook.

Thanks for the answer!
Was the result (samples it generated) satisfactory for you? How much did it take to train 100k steps on P100 in your case?

satisfactory

That term is pretty ambiguous. I certainly saw no significant improvements after about 50k steps. The coherence/funniness/uniqueness matched the sample batches in this repo more or less at that point. I saw slightly more interesting results when I mixed in titles from my medium125k dataset.

How much did it take to train 100k steps on P100 in your case?

I'm using a Scaleway P100 instance (1 EUR/h). It took me two days, though not with continuous learning. It did take about 12 to 14 hours for each 50k segments IIRC.
The T4 Colab env should suffice to train at a reasonable speed, though I have not yet found a way to get a T4 env reliably. I get K80s about half of the time creating a notebook. TPUs might be worth exploring.

Thanks for sharing your experiences!

Yeah, final loss slightly below 1.0 sounds around right.
FWIW in my work I don't really pay attention to the absolute value of loss; just whether if it's going down.

@minimaxir What about calculating validation loss? As I see, gpt-2-simple calculates loss but not validation_loss. What would you suggest to evaluate the trained model?


Flutter web application download failed - path = Something went wrong, please report the issue https://www.github.com/incrediblezayed/file_saver/issues

Hi,
I tried this package to download the pdf file in flutter web application using the below code and its working fine if i run this web application in localhost.
  final pdfData =
      await _generatePdf(eventdata, eventAttendeeEntry, typeOfReceipt);
  await Printing.layoutPdf(onLayout: (format) => pdfData);

  MimeType type = MimeType.PDF;
  String path = await FileSaver.instance.saveFile(
      'print_receipt_${eventAttendeeEntry.eventAttendeeEntryId}_${eventAttendeeEntry.eventAttendeeEntryPrintReceiptId}',
      pdfData,
      "pdf",
      mimeType: type);
  print('path = $path');

But if i deploy in server (firebase hosting) and then if i try then i get the below error. any idea? anything blocking in server?
path = Something went wrong, please report the issue https://www.github.com/incrediblezayed/file_saver/issues
appreciate your response!

I am also getting in this issue works fine localhost but doesnt work on the web code is similar to yours:
class PdfApi {   static saveDocument({     required String name,     required Document pdf,   }) async {     Uint8List pdfInBytes = await pdf.save();     await FileSaver.instance         .saveFile(name, pdfInBytes, '.pdf', mimeType: MimeType.PDF);   } }
In need of a solution

I'll get the solution asap, but I'm on vacation for 10 days unfortunately, on 20th October, I'll bring the solution

Hi @ranvirsahota, please test the latest updates and let me know

I'm receiving this error as well. But why does saveFile() return an error string instead of throwing an exception???

Getting same issue in latest version file_saver: ^0.2.9
Flutter (Channel stable, 3.16.5)


Feature request: allow themes to provide colour settings

It would be great to allow theme authors to provide colour settings for this package. Unfortunately if the colours are defined via settings I believe theme authors have no way of providing themed colours for them and users need to change the colours themselves.
I would love to define the colour scheme for this package in Remedy theme. 🙏
Thanks in advance!

Do you think it's possible without introducing breaking changes?

Nice theme btw.

Sadly, I would not know - the only extension I ever worked on for VS Code was that theme and that's just flat JSON. I do not know how custom colour "contributions" work or what would be necessary to adopt them here. I'd just love to have the possibility to provide those colours through that theme.
Thanks! ❤ Just released version 3.0 of it. 🚀

Some comparison of the properties that are known to me:

Color
Setting

Can get the value
❌
✅

Can change the value from settings GUI
❌
✅

Auto complete default/current value in settings
❌
✅

Color picker in settings.json
✅
❌

Assign color per theme
✅
❌

Use id of an existing color
✅
❌

There is no way of getting the value (inline svg gutter icon/ css injected style won't work with color) https://github.com/microsoft/vscode/issues/32813
Fill in current value in settings: https://github.com/microsoft/vscode/issues/25633

The plan is to make this in multi-step way.

[x] Create color contributions
[x] Make them under a config errorLens.useColorContributions (false by default)
[ ] In the future: set it to true
[ ] If it can completely replace the settings - then delete settings. Otherwise - delete color contributions.

Added color tokens:

errorLens.errorBackground
errorLens.errorMessageBackground
errorLens.errorForeground
errorLens.warningBackground
errorLens.warningMessageBackground
errorLens.warningForeground
errorLens.infoBackground
errorLens.infoMessageBackground
errorLens.infoForeground
errorLens.hintBackground
errorLens.hintMessageBackground
errorLens.hintForeground

You can test them from 2.8.0 with
"errorLens.useColorContributions": true,

Thank @usernamehw for implementing this! ❤ I have released Remedy v3.4 with colour contributions for this extension and it works great! Here, a screenshot of how it looks like when you install this extension and the Remedy theme - the colours exactly match other decorations of the same type.

I guess the only last missing thing would be to allow defining custom colour for the circle gutter marker, if that is possible. Otherwise I am very happy with this now! 🍻 🎨

I would like to say thank you to @usernamehw
you really made my month.  ive been waiting for updates on this extension for a very long time.
this makes me so happy.  Again thank you for forking and fixing this extension and making it available.
Thank you :D

I'm closing this since most of the work is done.

Thank @usernamehw for implementing this! ❤ I have released Remedy v3.4 with colour contributions for this extension and it works great! Here, a screenshot of how it looks like when you install this extension and the Remedy theme - the colours exactly match other decorations of the same type.

I guess the only last missing thing would be to allow defining custom colour for the circle gutter marker, if that is possible. Otherwise I am very happy with this now! 🍻 🎨

Sorry for creating a reply here, but what is the setting to display "inline icon" as shown in your picture? I think this is nice, but I don't have it and cannot find the setting for it. Did you remove this feature?

It's $severity from the inline message template:
"errorLens.messageTemplate": "$severity $message",
"errorLens.severityText": ["❗", "⚠", "ℹ", "👉"],


content type config error

Hi
When I config my content type at
localhost:1337/admin/plugins/content-manager/ctm-configurations/xxx,
I got a blank page with this error in console:
main.js:16 TypeError: Cannot read property 'getIn' of undefined
    at e.value (main.js:54)
    at main.js:54
    at We.__iterate (main.js:6)
    at We.forEach (main.js:6)
    at e.value (main.js:54)
    at new e (main.js:54)
    at main.js:48
    at Ae (main.js:6)
    at Ae (main.js:6)
    at Ae (main.js:6)

navigator.userAgent:
Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/70.0.3538.77 Safari/537.36

Issue related to the core repository https://github.com/strapi/strapi


Refactor entire hosts reading and writing code

I started refactoring the host reading and writing code. This consists mostly of improvements in readability and performance.

This is a mirror.


python312Packages.cyclonedx-python-lib: 6.4.4 -> 7.3.2

Diff: https://github.com/CycloneDX/cyclonedx-python-lib/compare/refs/tags/v6.4.4...v7.3.2
Changelog: https://github.com/CycloneDX/cyclonedx-python-lib/releases/tag/v7.3.2
Description of changes

Things done

Built on platform(s)

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

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Result of nixpkgs-review pr 309537 run on x86_64-linux 1

8 packages built:

checkov
checkov.dist
pip-audit
pip-audit.dist
python311Packages.cyclonedx-python-lib
python311Packages.cyclonedx-python-lib.dist
python312Packages.cyclonedx-python-lib
python312Packages.cyclonedx-python-lib.dist


Adding bibtex in plot_background_filtering.py

Reference issue
Example: Fixes #8900.
What does this implement/fix?
Add bibtex citations in the tutorial "Background information on filtering"

Thx @marsipu
looked good https://25811-1301584-gh.circle-artifacts.com/0/dev/auto_tutorials/discussions/plot_background_filtering.html#sphx-glr-auto-tutorials-discussions-plot-background-filtering-py


AbstractDependentResource reconciles two times on update

Bug Report
What did you do?
I created Reconciler on primary resource and CRUDKubernetesDependentResource connected with it. On the next step i triggered reconciliation which should update dependent resource.
What did you expect to see?
Single call of desired method
What did you see instead? Under which circumstances?
Two calls of desired method - second is redundant.
Additional context
After analysis i assume the root cause is HERE. The desired method is called here even if Optional returned from computedDesired has value. It's a pretty common mistake during using optionals, that orElse is called instead of orElseGet when we really need lazy evaluation.
Possible Solution
Just make desired call lazily evaluated by using orElseGet ;)
Environment
$ Mention java-operator-sdk version from pom.xml file
3.1.1

Indeed! 🤦🏼


Attach thumbnail files during the upload process.

This fixes a bug that occurs with the provenance plugin (see Girder PR #1591).

This fixes issue #82.

@brianhelba Can you review this?  It is related to the work done in Girder PR #1591.


the note below step 1 is not applicable to os disks with SSE with PMK & ADE

The following note is below step 1:
_Note
After you restore the VM disk, you can manually swap the OS disk of the original VM with the restored VM disk without re-creating it. Learn more._
If you try to do this on a disk with SSE with PMK & ADE it just stop windows from booting.

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

ID: 1b03e5f3-3816-49b1-7354-8939e77a2f7f
Version Independent ID: 519284bf-2567-d3a1-df54-f8b40f458a4b
Content: Restore encrypted Azure VMs - Azure Backup
Content Source: articles/backup/restore-azure-encrypted-virtual-machines.md
Service: backup
GitHub Login: @AbhishekMallick-MS
Microsoft Alias: v-abhmallick

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

@raveheart1 Thank you for reaching out to us. Please note that this channel (the Azure Docs repository) is only for driving improvements related to the Azure documentation. The issue you have reported appears to be more of a technical query. Please reach out to Azure support if it isn't working as expected.

@raveheart1 Closing this issue for now.

It's not a technical issue - if the disks are encrypted using the
aforementioned method your VM will not boot, I had someone on my team try
it during a troubleshooting call with a client and it didn't work. You need
to unlock that disk first before you can swap it.
On Tue, Oct 10, 2023, 12:55 PM SadiqhAhmed-MSFT @.***>
wrote:

Closed #115712 https://github.com/MicrosoftDocs/azure-docs/issues/115712
as completed.
—
Reply to this email directly, view it on GitHub
https://github.com/MicrosoftDocs/azure-docs/issues/115712#event-10607150624,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AMAORVO2NP6OUVJBWQFS2P3X6V4ZPAVCNFSM6AAAAAA5WE3QAWVHI2DSMVQWIX3LMV45UABCJFZXG5LFIV3GK3TUJZXXI2LGNFRWC5DJN5XDWMJQGYYDOMJVGA3DENA
.
You are receiving this because you were mentioned.Message ID:
@.***>

@raveheart1 Thanks for sharing the details. I shall discuss this issue with the content team to verify the steps and see if there is any update required to the documentation.
Thanks once again for your valuable feedback.


Only support valid OpenAPI/Swagger 2.0 specifications

I have added the package swagger_spec_validation because we were supporting some invalid swagger specification definitions so that change will guarantee that we will only keep supporting valid definitions. Along with that I have made the required changes in the code to fix how we handled the specification (mostly related to body parameters).
Changes:

Only supports valid OpenAPI/Swagger 2.0 specifications
Support correctly the body parameter. Before we were taking then default value from the parameter level, but since parameters of type "body" require schema the default value should come from the schema definition object.
Split the file tests/test_app.py in several smaller contextual test files under tests/api/test_*.py so it makes easier to find and extend our tests with more contextualisation on what they aim to cover.

:+1:


How do I change the rancher-server timezone settings?

What kind of request is this (question/bug/enhancement/feature request):
question
Steps to reproduce (least amount of steps as possible):
I want to use kubernetes cronjob. My timezone setting is UTC+9.
I believe that it is necessary to change the timezone setting of the rancher-server container.
Is there any other good way?
Result:
Other details that may be helpful:
Environment information

Rancher version (rancher/rancher/rancher/server image tag or shown bottom left in the UI):
v2.1.7

Installation option (single install/HA):
single install

Cluster information

Cluster type (Hosted/Infrastructure Provider/Custom/Imported):
Machine type (cloud/VM/metal) and specifications (CPU/memory):
Kubernetes version (use kubectl version):

- Cluster type (Hosted/Infrastructure Provider/Custom/Imported):Custom
- Machine type (cloud/VM/metal) and specifications (CPU/memory):cloud
- Kubernetes version (use `kubectl version`):v1.13.4

Docker version (use docker version):

Client:
 Version:         1.13.1
 API version:     1.26
 Package version: docker-1.13.1-88.git07f3374.el7.centos.x86_64
 Go version:      go1.9.4
 Git commit:      07f3374/1.13.1
 Built:           Fri Dec  7 16:13:51 2018
 OS/Arch:         linux/amd64

Server:
 Version:         1.13.1
 API version:     1.26 (minimum version 1.12)
 Package version: docker-1.13.1-88.git07f3374.el7.centos.x86_64
 Go version:      go1.9.4
 Git commit:      07f3374/1.13.1
 Built:           Fri Dec  7 16:13:51 2018
 OS/Arch:         linux/amd64
 Experimental:    false

Change the timezone of the underlying host?

+1. I have a scheduled job on my production cluster that is programmed like so : "0 6,12,18 * * *". Timezone is correctly set in the host node and i confirmed that with date command. But i noticed from workload logs that the job is executing at 8am, 2pm and 8pm everyday. Is there a timezone setting somewhere to configure in rancher cluster settings ?

also having this problem, because rancher is using UTC, anda ll docker containers that execute from it are UTC, but my server host is CEST

I also see this problem, host has the correct timezone set but rancher is off by 2 hours.

Duplicate of #19675 #22259

Edit cluster.yaml (Edit cluster > Edit as YAML) and add this lines to services section:
services:
    kube-controller:
      extra_binds:
        - '/etc/localtime:/etc/localtime'

After that configure correct timezone on Control Plane role nodes.


support PHP >= 5.4

It turns out that it is not too difficult to support PHP 5.4, the only change required was to make setting the "Max-Age" header only when the PHP version is >= 5.5.0 to get matching behavior to PHP's setcookie(). All tests pass.
My reason for needing to support PHP 5.4 is that CentOS/RHEL 7 come with PHP 5.4 that is maintained by Red Hat.
Are you aware of any other reason than Max-Age support that stopped you from implementing support for PHP <= 5.6? Maybe I'm missing some security sensitive issue that has been long fixed in PHP 5.6, but lingers in the depths of old obsolete PHP code ;)
For the setcookie() Changelog: https://secure.php.net/manual/en/function.setcookie.php#refsect1-function.setcookie-changelog
Thanks!

Thanks!
The original rationale for dropping support for PHP 5.3 to 5.5 was outlined here.
On the other hand, if CentOS/RHEL really backport all security-critical patches and thus that platform is a valid use case for modern and secure applications, we should support these platforms – if possible without too much effort, as you said (and showed).
Your fix for that change in behavior across PHP versions looks good. Another issue that comes to mind is this one which was fixed in PHP here.

What you could also do is, like paragonie/sodium_compat is mention something like this:

This library tentativeley supports PHP 5.2.4 - 7.x (latest), but officially only supports non-EOL'd versions of PHP.

PHP 5.4 and 5.5 have been added as targets for Travis CI in https://github.com/delight-im/PHP-Cookie/commit/fd6e232ccf5a641d3b3782930822b42587f11714. The Max-Age property is not written on PHP 5.4 anymore as per https://github.com/delight-im/PHP-Cookie/commit/1b12f69fab1cc275357fe2c6180ee60f5ccb934c. And finally, support for PHP 5.4 and 5.5 has been documented again in https://github.com/delight-im/PHP-Cookie/commit/f797d0cbb679daee5da3a358f73953af6ab89b7a.
We'll keep supporting those versions as long as they're available (with backported patches) on current versions of CentOS/RHEL or until they become too much of a burden to support.
Thank you very much!


Update 0.2.0

Bump version to 0.2.0

Codecov Report

Merging #63 (1c16848) into main (57c76f0) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main      #63   +/-   ##
=======================================
  Coverage   91.67%   91.67%
=======================================
  Files          15       15
  Lines         805      805
=======================================
  Hits          738      738
  Misses         67       67

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Build an adaptive app with adaptive layout: Android Basics with Compose

In Step 5, Add automated test for adaptive apps, around sub-step 6, the string details_screen is used without having been defined in strings.xml. The solution code has this missing line:
<string name="details_screen">Details Screen</string>
Also, the testTag for the details screen isn't being set up; this causes the expandedDevice_selectedEmailEmailRetained_afterConfigChange test to fail. The solution code doesn't contain the missing code, but this works:
ReplyHomeContent.kt in function ReplyListAndDetailContent
val activity = LocalContext.current as Activity
        val detailsScreenContentDescription = stringResource(R.string.details_screen)    // missing
        ReplyDetailsScreen(
            replyUiState = replyUiState,
            modifier = Modifier.weight(1f)
                .testTag(detailsScreenContentDescription),    // missing
            onBackPressed = { activity.finish() }
        )

found this solution in one of the other branches
@Composable
fun ReplyDetailsScreen(
    replyUiState: ReplyUiState,
    modifier: Modifier = Modifier,
    onBackPressed: () -> Unit = {},
    isFullScreen: Boolean = false
) {
    BackHandler {
        onBackPressed()
    }
    LazyColumn(
        modifier = modifier
            .testTag(stringResource(R.string.details_screen))

Also not sure why the codelab is creating a string first and then passing it to .testTag
Also not sure why it's within ReplyDetailsScreen and not passed in as you have done in your solution. As the way you have done it seems more consistent with the codelab examples.


[help] hover color on custom module

With 0.9.15 i can change the hover color to red of a simple custom launcher module:
"custom/firefox": {
	"format": "",
        "on-click": "firefox"
},

In css:
#custom-firefox:hover{
    color: red;
}

But not work with 0.9.16 with the revert of https://github.com/Alexays/Waybar/pull/1120
Anyone can help to achieve this with 0.9.16 ? thank you.
Merci beaucoup pour le boulot. Waybar est super chouette !

Here it works perfect with 0.9.16-2 on arch, actually I ignored always the syntax custom-<module> and tried with  custom/module> which never worked. So thanks!

    "custom/kbdlayout": {
        "format": "{}",
        "max-length": 40,
        "interval": 1,
        "exec": "/home/stef/bin/kbdlayout",
    }

#custom-kbdlayout{
  color: white;
}

Imo issue can be closed.

same problem, :hover with 0.9.17  seems to do nothing, although I set on-click

Is there any way to do this? With the revert of #1120, I can't figure it out. Tried a bunch of options, but as it seems from reading through github issues it's not possible anymore. I also read something about a bump to gtk4 from 3 being helpful? Are we stuck for now?

It would be really nice to have hover effects on all elements of the waybar, it would add so much juice to the interface.

Why was #1120 reverted, this feature takes the styling to another level.

I would also love to have this!

Fixed with https://github.com/Alexays/Waybar/pull/3145


Country code in contact form

Hi Team,
We need to add country code in mobile number section of the contact form. Also create a choice box as per the design.  Please check the design

@2016DigiTech can you please add a design mockup how this should look like?

@2016DigiTech we are still waiting for a design mockup as mentioned by @rofe in the above comment.

@2016DigiTech Below link can be used for reference to get country code part in place:
https://www.twilio.com/blog/international-phone-number-input-html-javascript


remove geom name attribute in block.xml

It seems that the name attribute of geom in the block.xml will raise the following issue when I include block.xml in a new environment.
    model = mujoco.MjModel.from_xml_path(self.fullpath)
ValueError: Error: repeated name in geom array, position 53

Removing the geom name will fix the problem.

For reference geom.name must be unique https://mujoco.readthedocs.io/en/stable/overview.html#types-names-ids
@nicehiro if you want to use the object in your environment and need to modify it, feel free to do so, but unless you can prove that this does affect the existing environments in Metaworld close the issue

Thank you all for your explanation.


LS: Extremely high RAM usage (Previous threads no help)

Hello, I have been looking through a bunch of threads about the language server reloading all modules and not actually completing causing RAM overload and my whole machine just takes the shits. It started to only happen recently about a 4 days ago and I cant seem to find a fix. This is my last resort as I didnt want to start another thread about an old issue

https://github.com/Microsoft/python-language-server/pull/546 eliminates this code. Closing pending new engine release. The release schedule can be observed in Zenhub extension to Chrome. Thanks.

0.2.16 is now available on beta channel. You can set this in your VS Code settings.json to get it:
"python.analysis.downloadChannel": "beta"


Clients in same Identity Zone with different Identity Providers

Can you please let me know if it is possible to have 2 clients in the same identity zone but have one client use an external SAML IDP for authentication while have the other client to go to a LDAP authentication source.
How do we show the standard UAA login screen for the LDAP authentication source, but show the IDP's login screen for the SAML authentication source.

@hyadalam , you can use the allowed identity providers feature for this.
This needs to be set on the client. For LDAP the alias is ldap.
The filed is "allowedproviders":["acme"]


org.wso2.carbon.relay.ExpandingMessageFormatter has a incorrect ContentType in the axis2.xml

Description:
In the axis2.xml the below message formatter has an incorrect contentType.
<messageFormatter contentType="application/octet-streaml"
                          class="org.wso2.carbon.relay.ExpandingMessageFormatter"/>

The contentType should be corrected as application/octet-stream removing the additional letter l from the end.
This issue can be seen in both AM-2.2.0 and AM-2.5.0 but not in earlier versions.
Suggested Labels:

Suggested Assignees:

Affected Product Version:
AM-2.2.0 , AM-2.5.0
OS, DB, other environment details and versions:
Steps to reproduce:
Related Issues:

yeap... happens to me...! must be changed

Closing the issue as this is older than 3 years. Please reopen if the issue is valid still.


Adding msb.com to the list of online learning platforms

I signed it

Hello @dmitriy-at-msb . Thanks for this pull request.
There is active discussion about the policies of including third party content in the Kubernetes docs. For further information , see the kubernetes/enhancements#1327.
/hold

/cc @zacharysarah @jimangel @kbarnard10

hey @kbhawkey are there any updates on this issue? I've had a look at the discussion you posted and I understand the concerns, but i don't think MSB is any different from any other links already posted there

@dmitriy-at-msb @mstipetic Thanks for the PR. However, the KEP @kbhawkey linked (kubernetes/enhancements#1327) led to the removal of the online-training page which now redirects to: https://kubernetes.io/training/.
/close
/cc @zacharysarah @kbarnard10


Fixed hotkey rotating breaking socket connections

I noticed you yeeted the check for the enableSnapRotation. Do you think it's just better off without it? Also good catch with the other bits.

In testing it didn't seem to make a difference, so out the door it went lol
I have since started on a lil side quest to add unit test using ava and puppeteer, its a rabbit hole of awesome lol


Fix for migration missing table name

The table name is not set as 'auth.providers.users.model' in atleast Laravel 5.2.41. But since we got the model anyway. Why no use ->getTable(); Tested & Working.

@d-lamers You should use this one, entrust is poorly maintained