Updated binPath for windows enviroment

I escaped the backlashes in the binPath string so that it works correctly in a windows environment. Without the backslashes the cucumber-js process would not run for me.

Thanks for PR!
Very strange that there were no issues like this. Maybe you were the first, who uses gulp-cucumber on Windows :)


[REQUEST] Capture Proxies From URLs With Bad Format

As you can see we have many good links to scrape list proxies (FREE & PAID) and OB1/OB2 can easy get them with only format IP:PORT
But some sites with bad format as:
{“IP”: “<IP_ADDRESS>”, “PORT”: “12444”, “ANON”: “Elite”, “COUNTRY”: “United Kingdom”, “ISO”: “GB”}, {“IP”: “<IP_ADDRESS>”, “PORT”: “8123”, “ANON”: “Elite”, “COUNTRY”: “France”, “ISO”: “FR”}, {“IP”: “<IP_ADDRESS>”, “PORT”: “80”, “ANON”: “Transparent”, “COUNTRY”: “United States”, “ISO”: “US”}, {“IP”: “<IP_ADDRESS>”, “PORT”: “3128”, “ANON”: “Transparent”, “COUNTRY”: “United States”, “ISO”: “US”}, {“IP”: “<IP_ADDRESS>”, “PORT”: “8123”, “ANON”: “Elite”, “COUNTRY”: “Mexico”, “ISO”: “MX”}, {“IP”: “<IP_ADDRESS>”, “PORT”: “8080”, “ANON”: “Elite”, “COUNTRY”: “Mexico”, “ISO”: “MX”}, {“IP”: “<IP_ADDRESS>”, “PORT”: “8080”, “ANON”: “Transparent”, “COUNTRY”: “United Kingdom”, “ISO”: “GB”}, {“IP”: “<IP_ADDRESS>”, “PORT”: “8080”, “ANON”: “Transparent”, “COUNTRY”: “Iraq”, “ISO”: “IQ”}.etc.
I hope when add that links, OB1/OB2 still can get proxies list in the next version. Thank you for your hard work to have a best tool for us! Good luck!

Could you please clarify if you want to import proxies in the database of OB2 using the remote API option or if you want to be able to use them as proxy sources in a job so they can be queried periodically?

Could you please clarify if you want to import proxies in the database of OB2 using the remote API option or if you want to be able to use them as proxy sources in a job so they can be queried periodically?

I think his suggestion would apply to both cases, what he meant is, there are some websites that returns the proxy "file" with a json format, or any other format that is just different from line breaking(normal txt).

@tcortega I understood that, I just wanted to know if I can get away with adding the box only in the import proxies screen or if I also have to rework the proxy source in the job.


[stable/rabbitmq] Updating readme to match new default for rbac

As of commit #5202

What this PR does / why we need it:
Which issue this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged): fixes #
Special notes for your reviewer:

/ok-to-test

/lgtm


Merging in changes from the google-api-nodejs-library repo

There have been some recent changes to the utils.js file in the google-api-nodejs-client repo. However, that file has been moved to this repo, and will soon be deleted from the original repo.
I am merging the exact same changes into this repo.

Actually that typo is from the previous commit to the google-api-nodejs-client repo, which I merged here. I will fix the typo here. Thanks!


Error: The storage pool already exists when clustered

Required information

Distribution: Linux Mint
Distribution version: 19.1

Issue description
Adding a storage pool to a new cluster of 1 node fails with:
Error: The storage pool already exists
Steps to reproduce

sudo snap install lxd
lxd init
During init, add the node to a new cluster. Do not add storage.
lxc storage create default dir => CREATED
lxc storage create data zfs source=pool1/lxd --target myserver => PENDING
lxc storage create data zfs => ERROR

Server here has a ZFS pool1 and I want it to use a non-existing lxd dataset. Following a similar procedure when the node is not clustered works fine and the dataset is created.
Additional info
config:
  cluster.https_address: `<redacted>`
  core.https_address: `<redacted>`
  core.trust_password: true
api_extensions:
- storage_zfs_remove_snapshots
- container_host_shutdown_timeout
- container_stop_priority
- container_syscall_filtering
- auth_pki
- container_last_used_at
- etag
- patch
- usb_devices
- https_allowed_credentials
- image_compression_algorithm
- directory_manipulation
- container_cpu_time
- storage_zfs_use_refquota
- storage_lvm_mount_options
- network
- profile_usedby
- container_push
- container_exec_recording
- certificate_update
- container_exec_signal_handling
- gpu_devices
- container_image_properties
- migration_progress
- id_map
- network_firewall_filtering
- network_routes
- storage
- file_delete
- file_append
- network_dhcp_expiry
- storage_lvm_vg_rename
- storage_lvm_thinpool_rename
- network_vlan
- image_create_aliases
- container_stateless_copy
- container_only_migration
- storage_zfs_clone_copy
- unix_device_rename
- storage_lvm_use_thinpool
- storage_rsync_bwlimit
- network_vxlan_interface
- storage_btrfs_mount_options
- entity_description
- image_force_refresh
- storage_lvm_lv_resizing
- id_map_base
- file_symlinks
- container_push_target
- network_vlan_physical
- storage_images_delete
- container_edit_metadata
- container_snapshot_stateful_migration
- storage_driver_ceph
- storage_ceph_user_name
- resource_limits
- storage_volatile_initial_source
- storage_ceph_force_osd_reuse
- storage_block_filesystem_btrfs
- resources
- kernel_limits
- storage_api_volume_rename
- macaroon_authentication
- network_sriov
- console
- restrict_devlxd
- migration_pre_copy
- infiniband
- maas_network
- devlxd_events
- proxy
- network_dhcp_gateway
- file_get_symlink
- network_leases
- unix_device_hotplug
- storage_api_local_volume_handling
- operation_description
- clustering
- event_lifecycle
- storage_api_remote_volume_handling
- nvidia_runtime
- container_mount_propagation
- container_backup
- devlxd_images
- container_local_cross_pool_handling
- proxy_unix
- proxy_udp
- clustering_join
- proxy_tcp_udp_multi_port_handling
- network_state
- proxy_unix_dac_properties
- container_protection_delete
- unix_priv_drop
- pprof_http
- proxy_haproxy_protocol
- network_hwaddr
- proxy_nat
- network_nat_order
- container_full
- candid_authentication
- backup_compression
- candid_config
- nvidia_runtime_config
- storage_api_volume_snapshots
- storage_unmapped
- projects
- candid_config_key
- network_vxlan_ttl
- container_incremental_copy
- usb_optional_vendorid
- snapshot_scheduling
- container_copy_project
- clustering_server_address
- clustering_image_replication
- container_protection_shift
- snapshot_expiry
- container_backup_override_pool
- snapshot_expiry_creation
- network_leases_location
- resources_cpu_socket
- resources_gpu
- resources_numa
- kernel_features
- id_map_current
- event_location
- storage_api_remote_volume_snapshots
- network_nat_address
- container_nic_routes
- rbac
- cluster_internal_copy
- seccomp_notify
- lxc_features
- container_nic_ipvlan
- network_vlan_sriov
- storage_cephfs
- container_nic_ipfilter
- resources_v2
- container_exec_user_group_cwd
- container_syscall_intercept
- container_disk_shift
- storage_shifted
- resources_infiniband
- daemon_storage
- instances
- image_types
- resources_disk_sata
- clustering_roles
- images_expiry
- resources_network_firmware
- backup_compression_algorithm
- ceph_data_pool_name
- container_syscall_intercept_mount
- compression_squashfs
- container_raw_mount
- container_nic_routed
- container_syscall_intercept_mount_fuse
- container_disk_ceph
- virtual-machines
- image_profiles
- clustering_architecture
- resources_disk_id
- storage_lvm_stripes
- vm_boot_priority
- unix_hotplug_devices
- api_filtering
- instance_nic_network
- clustering_sizing
- firewall_driver
- projects_limits
- container_syscall_intercept_hugetlbfs
- limits_hugepages
- container_nic_routed_gateway
- projects_restrictions
- custom_volume_snapshot_expiry
- volume_snapshot_scheduling
- trust_ca_certificates
- snapshot_disk_usage
- clustering_edit_roles
- container_nic_routed_host_address
- container_nic_ipvlan_gateway
- resources_usb_pci
- resources_cpu_threads_numa
- resources_cpu_core_die
- api_os
- resources_system
api_status: stable
api_version: "1.0"
auth: trusted
public: false
auth_methods:
- tls
environment:
  addresses:
  - `<redacted>`
  architectures:
  - x86_64
  - i686
  certificate: |
    -----BEGIN CERTIFICATE-----
    `<redacted>`
    -----END CERTIFICATE-----
  certificate_fingerprint: `<redacted>`
  driver: lxc
  driver_version: 4.0.2
  firewall: xtables
  kernel: Linux
  kernel_architecture: x86_64
  kernel_features:
    netnsid_getifaddrs: "true"
    seccomp_listener: "true"
    seccomp_listener_continue: "true"
    shiftfs: "false"
    uevent_injection: "true"
    unpriv_fscaps: "true"
  kernel_version: 5.3.0-42-generic
  lxc_features:
    cgroup2: "true"
    mount_injection_file: "true"
    network_gateway_device_route: "true"
    network_ipvlan: "true"
    network_l2proxy: "true"
    network_phys_macvlan_mtu: "true"
    network_veth_router: "true"
    seccomp_notify: "true"
  os_name: Linux Mint
  os_version: "19.1"
  project: default
  server: lxd
  server_clustered: true
  server_name: myserver
  server_pid: 18129
  server_version: 4.0.1
  storage: dir | zfs
  storage_version: 1 | 0.8.3-1ubuntu6~18.04.york0

I can reproduce this, and it turns out that if you have only one node you don't need to go through the two-stage storage creation (first on the node and then globally). So instead of doing:
lxc storage create data zfs source=pool1/lxd --target myserver => PENDING
lxc storage create data zfs => ERROR

you should be able to do directly:
lxc storage create data zfs source=pool1/lxd => CREATED

However, as long as you have more than one node in the cluster, the two-stage procedure is required.
I can't remember if the one-node "shortcut" is an intentional feature or if it's not intended. @stgraber any idea?
In any case we probably have something to fix, since trying the the two-stage procedure on a single node should either work as well or throw a more clear error.

Thanks! Confirmed, one-step procedure worked in single-node.
I guess that's convenient when manually executed, but makes it harder to automate the workflow and avoid race conditions if you have to do a cluster size check to know which approach to use.
If current behavior stands would be good to at least update the docs on the cluster setup page which currently only mentions the two-stage setup.

@freeekanayaka can we get a hybrid? If we have pending config then treat it like a normal cluster. If we don't and we're single node, allow everything be passed at once?
That should fix this issue while also not breaking anyone who are accidentally running single node clusters.

@freeekanayaka can we get a hybrid? If we have pending config then treat it like a normal cluster. If we don't and we're single node, allow everything be passed at once?
That should fix this issue while also not breaking anyone who are accidentally running single node clusters.

Sounds good, I'll work on that.


[BOOM-4784] Legal Compliance module in footer has non-uppercase header

This issue has been migrated from the Forge. Read the original ticket here.

Reporter: adrian
Created at: Fri, 9 Feb 2018 14:21:59 +0100

When you install the Legal Compliance module, it adds a list of links with the header "Information" to the footer. Unfortunately, this header is not uppercase, so it doesn't fit in with the other headers in the footer.
I suggest changing line 27 of themes/classic/views/templates/hook/hookDisplayFooter.tpl from:
  {l s='Information' d='Modules.Legalcompliance.Shop'}
to:
  {l s='Information' d='Modules.Legalcompliance.Shop'}

How to reproduce the issue ?

Install the Legal Compliance module with the Classic theme.

This module has been archived, it’s no longer maintained but you still can fork it if you need it for your shop. This issue is closed then.


Configure project settings

project name, encoding
java version

modify below Build Stage - Build Shell Command
#!/bin/bash
export JAVA_HOME=/opt/IBM/java8
mvn -B package


Correct soft assertions message format

This PR resolves issue https://github.com/corona-warn-app/cwa-website/issues/3040 "Error in Cypress softAssert error message format".
The formatting characters in the error message are correctly escaped with the backslash character "":
data.error.message = '\n\n\t' + data.error.message + '\n\n';
Verification

Introduce a temporary error, e.g. in /data/index.json Line 18 change #howto to #how
Execute npm run test:open
Select check_anchor_links.js
Check for correctly formatted error message with two blank links before and after the text and a tab before the text Failed soft assertions... check log above ↑

@MikeMcC399 Thanks for reporting issue and providing PR.

LGTM, thank you @MikeMcC399 !


Add import log to colletion detail page.

Fixes: https://github.com/ansible/galaxy-dev/issues/222

@newswangerd displaying import log on collection detail page adds the same information as we already have on 'My imports' page.
Do we plan to keep using both of them?
It feels easier to navigate to the import log on collection detail page, but on 'My imports' page it's possible to switch collection version:

(/automation-hub/my-imports?namespace=rblanco)

(/automation-hub/rblanco/collection_demo/import-log)

/cc @chouseknecht

The plan is to keep both of them. My imports is designed for collection maintainers and it lets them see an overview of all their imports as well as view imports as their happening, which is functionality that isn't in collection details.
Also, failed imports won't be viewable on collection details because the data for the collection detail page isn't available until after the import succeeds and is approved by.


Correct easy typos on README file.

Found some small typos on the readme and "corrected" them on the way I understand should be written. If I did miss understood sorry.

Thank you!


Extend the guidelines

@Oceania2018 @fdncred I started our Wiki (was not a lot but at least some lines ....)
On https://github.com/Oceania2018/NumSharp/wiki/Design-guidelines I started a page with guidelines.
Because I found our discussions and investigations last weeks very interesting and want to write them down. Especially casting, performance, arange instead of ARange, ... such things.
If you do not like some parts, or want to add something, feel free to change. ;)

Looks great. Good job!

Awesome! Good job. Maybe you should put your c# demo app in the repo as an example.

Amazing. I really was impressed when saw it. 🤩

By the way. Technically background question.
You used a matplotlib adapter and in background also using matplotlib. Amazing.
I was wondering how much work it would be to make a own matplotlib but html based.
In my mind hat sth like

tiny web sever in background
plotly.js as drawing lib
chromely project for rendering

Our hard work is worth it.
@dotChris90 I don't want to implement a ploting library for now. Let's focus on NumSharp and Pandas.NET.


Setup the wasmiot build pipeline, and push build containers to registry

As far as I understand this pipeline should:

[x] 1. Build images of the orchestrator and it's attached systems (database and supervisor)
[ ] 2. Contain at the very least some simple smoke test (e.g. succesfully curling the orchestrator index page after startup)
[x] 3. Push the built and tested images to the organization's package registry

Make new issue about the tests


[NavigationExperimental] Allow the disabling of navigation gestures.

During development of an app I decided upon NavigationExperimental as I found it easily configurable with my Redux stores and make it work the way I wanted. One thing I found missing was the ability to decide if gestures were on or not for the card stack. In my case I need the gestures off as they conflict with what I am trying to do. This PR simply opens up the ability to turn the gestures for a CardStack off.
Testing was completed via UI Explorer. An additional example replicating the existing one with the new setting set to false was created. To ensure nothing broke I tested both the original example and new example to ensure gestures worked (and didn't work) when expected.
I did not see any unit tests around NavigationExperimental but if I simply missed them I would be more then happy to update/add any.

By analyzing the blame information on this pull request, we identified @hedgerwang and @ericvicenti to be potential reviewers.

cc @hedgerwang

This mostly looks good. I'm not a big fan of copy-pasting the example code with all the comments included, but we can clean up the examples later.

@facebook-github-bot shipit

Thanks for importing.If you are an FB employee go to Phabricator to review internal test results.


docs: CORE-2372: Add migration sample app to examples

Hi👋, please prefix this PR's title with:

[x] breaking-change: if you have introduced modification that necessitates immediate adjustments by this SDK's users to their applications, clients, or integrations to avert disruptions to existing features or functionalities.
[x] feat:, fix:, refactor:, docs:, or chore:.

Summary

Added sample app for migration of assets from Immutable X to Immutable zkEVM to examples/
Detail and impact of the change

Added

Changed

Deprecated

Removed

Fixed

Security

Anything else worth calling out?

Could you please add these examples to the workspace by adding the examples directory examples/x-to-zkevm-migration-app/** in the workspaces field in the root package.json? This will ensure that we run CI checks on these examples and guarantee their validity 😄


Remove Unverified Role from Discord Server Members

Issue Title: Remove Unverified Role from Discord Server Members
Issue Description
Currently, unverified users in the Discord server are assigned an "Unverified" role. We need to implement a feature that automatically removes this role from users who have completed the verification process on our website after running the /verify command in Discord. Additionally, we need to integrate this feature into a script that can be executed by a superuser to remove the unverified role from users who were verified before this feature was implemented.
Steps to Resolve

Utilize the existing backend service, services/discordservice.js, which already contains the role removal functionality.
Implement the following logic in the script and verification process:

When a user successfully completes the verification process on our website after running the /verify command in Discord:

Retrieve the verified user's Discord ID and store it.
Pass the discordUnverifiedRoleId from the configuration file as an argument to the existing role removal service in services/discordservice.js to remove the "Unverified" role from the user.

Integrate this logic within the appropriate sections of the script and verification process to ensure seamless removal of the unverified role.

Test the feature extensively to verify its proper functionality and ensure it doesn't affect other parts of the system.
Document the implementation steps and update the project's documentation accordingly.
Update the README file with any necessary instructions for superusers to run the script and execute the role removal process for pre-existing verified users.

Additional Information

The existing role removal service can be found in the backend at services/discordservice.js.
The discordUnverifiedRoleId is already available in the configuration file and should be passed as an argument to the role removal service.

Acceptance Criteria

The "Unverified" role should be automatically removed from users who successfully complete the verification process on our website after running the /verify command in Discord.
The role removal feature should be integrated into a script that can be executed by a superuser to remove the unverified role from users who were verified before this feature was implemented.
The role removal service in services/discordservice.js should be consumed to remove the "Unverified" role.
The discordUnverifiedRoleId from the configuration file should be passed as an argument to the role removal service.
The script and verification process should be thoroughly tested to ensure proper functionality.
Documentation and the README file should be updated accordingly.

Related Files

services/discordservice.js
Configuration file (containing discordUnverifiedRoleId)

Please Assign me this task.
ETA: 8th August


Not using class_name

Hi,
So I have belongs_to :card_holder, class_name: "User" in my model but I'm getting this error uninitialized constant CardHolder it looks like client_side_validations isn't looking for and using the class_name.... is this a currently known bug?
Many thanks

Can you provide more detail? I'm sorry I took so long to address this.


Why are mdl-data-table td right aligned by default?

Hi,
Are tables expected to hold numeric data generally? I saw that the MD guidelines recommend right align for numeric but left align for text. With this library by default it behaves for numeric data, one has to explicitly apply class mdl-data-table__cell--non-numeric for text, so I'm wondering why the default is not the other way around. In my case most of my tables hold text and I'm having to litter the code with the explicit classing. I wonder if this is not most peoples use case too? Thanks in advance.

It's probably just from where whomever was doing the original build saw all the examples in the specification were largely numeric. There isn't a decided rhyme-or-reason to it. For Material Components for Web's table we should probably just let text be the default and numeric be the modifier.

Components for Web's table we should probably just let text be the default and numeric be the modifier.

Or use class on <table> to configure the cell default behavior: numeric or text.


[View observation] Label shown for empty fields

Only fields with data should be shown

@scolsen fyi

Obsolete once new UI is available.


[DATASTD-1898] - Adding new descriptor values to the STD

This covers the new descriptors created in MODL-406

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


temp finding always pushed to jira even when push_all_issues is False

temp findings are pushed to jira always even is push_all_issues on the product is false and push_to_jira is not checked on the form

this is in test/vies.py:add_temp_finding. not sure if this code is even used / reachable anymore.


TJWS: Upgrade to 1.114

https://sourceforge.net/projects/tjws/files/tjws/Release 1.114/
https://github.com/drogatkin/TJWS2

PR: https://github.com/couchbase/couchbase-lite-java-listener/pull/77


Add policy test for ingress identity in CNP

Related to the below comment :)
Originally posted by @jrajahalme in https://github.com/cilium/cilium/pull/20536#pullrequestreview-1040169880

This issue is completed via the below PRs
https://github.com/cilium/cilium-cli/pull/2126
https://github.com/cilium/cilium-cli/pull/2106
https://github.com/cilium/cilium-cli/pull/1533


Hotfix: Color Picking Box is not responsive.

PR Type

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Others. (Please describe)

PR Info.
Changes

Change the tag box chip in the Tag detail page to display the color hex code instead of the copy of the tag name

Fixes

#46
#48

Codecov Report

Merging #49 (5cde293) into master (08a8cef) will decrease coverage by 0.15%.
The diff coverage is 0.00%.

@@            Coverage Diff             @@
##           master      #49      +/-   ##
==========================================
- Coverage   31.76%   31.60%   -0.16%
==========================================
  Files          32       32
  Lines        1020     1025       +5
  Branches       96       97       +1
==========================================
  Hits          324      324
- Misses        695      700       +5
  Partials        1        1

Impacted Files
Coverage Δ

src/components/Create.vue
0.00% <0.00%> (ø)

src/components/Tag/TagDetail.vue
16.66% <ø> (ø)

src/views/Tag/TagDetailView.vue
0.00% <0.00%> (ø)

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 08a8cef...5cde293. Read the comment docs.


Make static_secrets optional

Makes StaticSecret optional behind feature flag static_secrets following reusable_secrets

The reasoning for this, as I understand it, is the same for gating reusable secrets: accidental reuse is really bad, and the priority of this crate is (allegedly) ephemeral ECDH. I'm convinced enough.
cc @tarcieri


Track upstream ExternalCatalog work

https://issues.apache.org/jira/browse/SPARK-15691
https://issues.apache.org/jira/browse/SPARK-15777

this is done with dsv2 now in master


CRYPTO_THREAD_write_lock() return codes.

Description
CRYPTO_THREAD_write_lock() returns error when pthread_rwlock_wrlock() fails. But in the OpenSSL code we are not capturing the return code of the function CRYPTO_THREAD_write_lock().

Here do we always expect that the lock should return success ?

The only reasons that pthread_rwlock_wrlock() is documented as returning failure could only arise in this case due to programmer error.  So, expecting that the lock operation will return success is roughly equivalent to assuming that we did not have any bugs with how we use locks, which is ... not always true, but is reasonable to assume for a released version of the software.  Certainly, attempting to debug a failure in such cases would be a similar level of easy/difficult whether or not the return values were actually checked or not.

@kaduk thanks a lot my friend ! I ran into a scenario where CRYPTO_THREAD_write_lock() returned error, but in the OpenSSL code we are failing to capture it. Here is my scenario.

I am writing a sample engine. In the engine initialization function(sample_engine_init()) i am calling RAND_bytes (), to get some random data. But the call to RAND_bytes() is trying to acquire the write lock on the global_engine_lock. As the global_engine_lock is already locked(engine_table_register :128), so the call to lock again is returning error "EDEADLK".

==31940== Thread #1's call to pthread_rwlock_wrlock failed
==31940==    with error code 35 (EDEADLK: Resource deadlock would occur)
==31940==    at 0x4C2FC27: pthread_rwlock_wrlock_WRK (hg_intercepts.c:2164)
==31940==    by 0x4C326C3: pthread_rwlock_wrlock (hg_intercepts.c:2175)
==31940==    by 0x52C5D58: CRYPTO_THREAD_write_lock (threads_pthread.c:78)
==31940==    by 0x522ABED: engine_table_select (eng_table.c:211)
==31940==    by 0x52459F7: EVP_CipherInit_ex (evp_enc.c:102)
==31940==    by 0x52811BD: drbg_ctr_init (drbg_ctr.c:413)
==31940==    by 0x528133F: RAND_DRBG_set (drbg_lib.c:137)
==31940==    by 0x5282258: rand_drbg_new (drbg_lib.c:225)
==31940==    by 0x5282258: RAND_DRBG_secure_new (drbg_lib.c:257)
==31940==    by 0x5282566: drbg_setup (drbg_lib.c:878)
==31940==    by 0x5282566: do_rand_drbg_init (drbg_lib.c:924)
==31940==    by 0x5282566: do_rand_drbg_init_ossl_ (drbg_lib.c:909)
==31940==    by 0x57C420A: __pthread_once_slow (pthread_once.c:117)
==31940==    by 0x52C5DC8: CRYPTO_THREAD_run_once (threads_pthread.c:118)
==31940==    by 0x52829C6: RAND_DRBG_get0_public (drbg_lib.c:1116)
Here is the call stack of the engine init function.
#0  sample_engine_init (e=0x6be380) at sample.c:5461
#1  0x00007ffff77b69f9 in engine_unlocked_init (e=e@entry=0x6be380) at crypto/engine/eng_init.c:26
#2  0x00007ffff77b89ca in engine_table_register (table=table@entry=0x7ffff7b43310 <cipher_table>, cleanup=cleanup@entry=0x7ffff77b91b0 <engine_unregister_all_ciphers>, e=e@entry=0x6be380, nids=0x7ffff6e6ebc0 <nids.27952>,
num_nids=, setdefault=setdefault@entry=1) at crypto/engine/eng_table.c:128
#3  0x00007ffff77b92b3 in ENGINE_set_default_ciphers (e=0x6be380) at crypto/engine/tb_cipher.c:51
#4  0x00007ffff77b67e5 in ENGINE_set_default (e=e@entry=0x6be380, flags=flags@entry=65535) at crypto/engine/eng_fat.c:16
#5  0x0000000000463398 in setup_engine (engine=, debug=debug@entry=0) at apps/apps.c:1310
#6  0x000000000043eaff in rsa_main (argc=, argv=) at apps/rsa.c:112
#7  0x000000000043293d in do_cmd (prog=prog@entry=0x6bcb20, argc=argc@entry=8, argv=argv@entry=0x7fffffffe200) at apps/openssl.c:570
#8  0x000000000041e7e8 in main (argc=8, argv=0x7fffffffe200) at apps/openssl.c:189
Here is the call stack of the RAND_bytes() trying to acquire the lock.
#0  pthread_rwlock_unlock () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_rwlock_unlock.S:50
#1  0x00007ffff7853d79 in CRYPTO_THREAD_unlock (lock=) at crypto/threads_pthread.c:91
#2  0x00007ffff77b8c43 in engine_table_select (table=table@entry=0x7ffff7b43310 <cipher_table>, nid=) at crypto/engine/eng_table.c:282
#3  0x00007ffff77b92ce in ENGINE_get_cipher_engine (nid=) at crypto/engine/tb_cipher.c:65
#4  0x00007ffff77d39f8 in EVP_CipherInit_ex (ctx=0x6bfd70, cipher=0x7ffff7b20100 <aesni_256_ecb>, impl=impl@entry=0x0, key=key@entry=0x7ffff78bf3a0 <df_key.11564> "", iv=iv@entry=0x0, enc=enc@entry=1) at crypto/evp/evp_enc.c:102
#5  0x00007ffff780f1be in drbg_ctr_init (drbg=drbg@entry=0x6bfb50) at crypto/rand/drbg_ctr.c:413
#6  0x00007ffff780f340 in RAND_DRBG_set (drbg=drbg@entry=0x6bfb50, type=type@entry=906, flags=flags@entry=0) at crypto/rand/drbg_lib.c:137
#7  0x00007ffff7810259 in rand_drbg_new (parent=0x0, flags=0, type=906, secure=1) at crypto/rand/drbg_lib.c:225
#8  RAND_DRBG_secure_new (type=906, flags=0, parent=parent@entry=0x0) at crypto/rand/drbg_lib.c:257
#9  0x00007ffff7810567 in drbg_setup (parent=0x0) at crypto/rand/drbg_lib.c:878
#10 do_rand_drbg_init () at crypto/rand/drbg_lib.c:924
#11 do_rand_drbg_init_ossl_ () at crypto/rand/drbg_lib.c:909
#12 0x00007ffff724320b in _pthread_once_slow (once_control=0x7ffff7b460b4 <rand_drbg_init>, init_routine=0x7ffff7810510 <do_rand_drbg_init_ossl>) at pthread_once.c:117
#13 0x00007ffff7249eee in GI___pthread_once (once_control=once_control@entry=0x7ffff7b460b4 <rand_drbg_init>, init_routine=init_routine@entry=0x7ffff7810510 <do_rand_drbg_init_ossl>) at pthread_once.c:146
#14 0x00007ffff7853dc9 in CRYPTO_THREAD_run_once (once=once@entry=0x7ffff7b460b4 <rand_drbg_init>, init=init@entry=0x7ffff7810510 <do_rand_drbg_init_ossl>) at crypto/threads_pthread.c:118
#15 0x00007ffff78109c7 in RAND_DRBG_get0_public () at crypto/rand/drbg_lib.c:1116
#16 0x00007ffff7810aa0 in drbg_bytes (out=0x7fffffffd690 "", count=16) at crypto/rand/drbg_lib.c:966
Note:- Application here is a single threaded application.

I may met the same question as you did @ @sdash713 .I used gdb but couldn't find the wrong code in the program.What kind of tools you used to generate the log like ==31940== Thread #1's call to pthread_rwlock_wrlock failed ==31940== with error code 35 (EDEADLK: Resource deadlock would occur) ==31940== at 0x4C2FC27: pthread_rwlock_wrlock_WRK (hg_intercepts.c:2164) ==31940== by 0x4C326C3: pthread_rwlock_wrlock (hg_intercepts.c:2175)or#0 sample_engine_init (e=0x6be380) at sample.c:5461 #1 0x00007ffff77b69f9 in engine_unlocked_init (e=e@entry=0x6be380) at crypto/engine/eng_init.c:26 #2 0x00007ffff77b89ca in engine_table_register (table=table@entry=0x7ffff7b43310 <cipher_table>, cleanup=cleanup@entry=0x7ffff77b91b0 <engine_unregister_all_ciphers>, e=e@entry=0x6be380, nids=0x7ffff6e6ebc0 <nids.27952>,

@bowensd i used valgrind --tool=helgrind.

Thanks! That's helpful

If OpenSSL is taking the view that CRYPTO_THREAD_write_lock may be assumed infallible outside of programmer errors (I agree with this view), then I'd suggest a couple of changes:

Reflect this in the documentation, since the functions are part of the public API.
CRYPTO_UP_REF is currently considered fallible because CRYPTO_atomic_add is. That only fails due to CRYPTO_THREAD_write_lock. I'd suggest unwinding all those error cases so that FOO_up_ref may be also be infallible. Indeed, although FOO_up_ref is documented to have an error, most (but not all) calls in OpenSSL don't bother to check. (NB: refcounts may also overflow. OpenSSL appears to handle it, but I don't think it works because the overflow has already been written to the refcount. BoringSSL instead saturates the counter because if you've managed to up_ref that many times, you've clearly leaked the object anyway.)
abort on failure, so that, if this is triggered as a result of some external callback, the result is a fast fail, rather than silently continue without holding the lock. (This is what BoringSSL does.)

@sdash713 while we are figuring out the general strategy for whether we think the locking functions should have their return values checked, you might consider using the RAND_DRBG APIs directoy in your engine initialization (or use a call like getentropy() directly).

@kaduk thanks. I will use the mentioned functions.

It seems like there was an implicit question for the team here, in the form of "should we write our code to the assumption that CRYPTO_THREAD_write_lock() (etc.) will never fail?  @paulidale should I open a new issue for that question?

I missed that.  I'll reopen this issue until it is answered.

4 years an no definitive answer.
FWIW, i say yes, there are conditions under which locks can fail, but practically speaking, in a production environment, they should not.
Marking as inactive, to be closed at the end of 3.4 dev, barring further input


Cannot run AWS nginx ingress controler addon

Description
The nginx ingress controller addon does not launch.
Steps to Reproduce

Deploy fresh Typhoon cluster in AWS with Calico CNI (networking   = "calico")
Add nginx ingress controller addon : kubectl apply -R -f addons/nginx-ingress/aws (Followed: https://typhoon.psdn.io/addons/ingress/)
We got crashes on the pods:

❯ kubectl get pods --all-namespaces
NAMESPACE     NAME                                       READY   STATUS             RESTARTS      AGE
ingress       nginx-ingress-controller-c966f5589-h7mn2   0/1     CrashLoopBackOff   6 (17s ago)   4m58s
ingress       nginx-ingress-controller-c966f5589-t8r6t   0/1     CrashLoopBackOff   6 (7s ago)    4m58s

Logs
❯ kubectl logs nginx-ingress-controller-c966f5589-h7mn2 -n ingress
-------------------------------------------------------------------------------
NGINX Ingress controller
  Release:       v1.5.1
  Build:         d003aae913cc25f375deb74f898c7f3c65c06f05
  Repository:    https://github.com/kubernetes/ingress-nginx
  nginx version: nginx/1.21.6

-------------------------------------------------------------------------------

W0606 14:27:31.641402       7 client_config.go:617] Neither --kubeconfig nor --master was specified.  Using the inClusterConfig.  This might not work.
I0606 14:27:31.641700       7 main.go:209] "Creating API client" host="https://<IP_ADDRESS>:443"

Expected behavior
nginx ingress controller AWS addon does not crash
Environment

Platform: AWS
OS: fedora-coreos
Release: Typhoon 1.27.2
Terraform: Terraform v1.4.6
Plugins: poseidon/ct 0.13.0, hashicorp/aws 4.61.0

I've been using Terraform to manage these Kubernetes resources across my clusters, and no longer update these raw Kubernetes manifests examples in this repo. The addons should probably be removed.  I think early on they were important to show, but these days people can probably run their own Nginx, Prometheus, etc. without me maintaining examples.

If you look at the logs, your issue is likely due to missing RBAC permissions for endpoint slices. Nginx Ingress has had some changes and the addon examples aren't updated.


Update multiprocessing import in py_dataset_adapter.py

Multiprocessing import needs to import multiprocessing.dummy.
This has worked up until now due to an import in tensorflow, which will soon no longer be available here.

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Comparison is base (6fe9aab) 79.51% compared to head (9968212) 63.81%.

Additional details and impacted files
@@             Coverage Diff             @@
##           master   #18938       +/-   ##
===========================================
- Coverage   79.51%   63.81%   -15.71%
===========================================
  Files         336      336
  Lines       34982    34982
  Branches     6865     6865
===========================================
- Hits        27817    22323     -5494
- Misses       5586    11191     +5605
+ Partials     1579     1468      -111

Flag
Coverage Δ

keras
63.81% <100.00%> (-15.57%)
:arrow_down:

keras-jax
?

keras-numpy
?

keras-tensorflow
?

keras-torch
63.81% <100.00%> (+<0.01%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


ROX-15852: Move images in ImageSignatureTests to quay.io

Description
This PR moves the images used within the image signature tests to quay.io, instead of reyling on other public registries such as gcr.io, docker.io.
When the tests were originally written, quay.io did not yet support the cosign OCI metadata type, and hence public images were used.
Now, these images have been moved to the quay.io/rhacs-eng/qa-signatures repo, and new cosign signatures have been publish for these images.
The private keys + passphrases of the signatures have been added to BitWarden.
Checklist

[ ] Investigated and inspected CI test results
[ ] Unit test and regression tests added
[ ] Evaluated and added CHANGELOG entry if required
[ ] Determined and documented upgrade steps
[ ] Documented user facing changes (create PR based on openshift/openshift-docs and merge into rhacs-docs)

If any of these don't apply, please comment below.
Testing Performed

see CI (tests should still pass).

Current dependencies on/for this PR:

master

PR #5206   👈

This comment was auto-generated by Graphite.


Social previews of superhero

Shared content from superhero to social media should be previewed better.

It's part of SSR work. Current branch is https://github.com/aeternity/superhero-ui/tree/feature/ssr-combine


Vision Source

Closes #2074

Looks like test is blocked by #2069 or updates to BasePlaceableHud, which don't have a ticket?

Superseded by #2454


_where= parameter is not persisted in hidden form fields

e.g. on this page: https://v0-30.datasette.io/fixtures/roadside_attractions?_where=name like '%museum%'
Click the "Apply" button and the _where= parameter will be dropped.

Relevant code:
https://github.com/simonw/datasette/blob/912ce848b9fa8b1642c800b446f504518bc39f2a/datasette/templates/table.html#L94-L97
And
https://github.com/simonw/datasette/blob/b9ede4c1898616512b5d204f9c941deff473cbe4/datasette/views/table.py#L719-L722

Just adding _where to that tuple won't do the trick, because _where= can be passed multiple times.

Shipped in 0.30.1 https://datasette.readthedocs.io/en/latest/changelog.html#v0-30-1


source-git: patch generation fixes:

order all patches we generate (merge commits were screwing this)
a merge commit can produce multiple patch files

Fixes: https://stg.packit.dev/copr-build/141/logs

@lachmanfrantisek, thanks, fixed; the formatting line was a leftover

Thanks for that.
I was thinking that %autosetup applies the patches in the order they are specified in the spec, i.e. in a spec like
Patch0001: 666.patch
Patch0002: 111.patch

rpm first applies 666.patch and then 111.patch, but obviously it's not the case for systemd spec.
I see it uses
%autosetup -n %{?commit:%{name}%{?stable:-stable}-%{commit}}%{!?commit:%{name}%{?stable:-stable}-%{github_version}} -p1 -Sgit
Is the -Sgit changing the behaviour?
Does anyone know how the -Sgit works and why it doesn't apply the patches as they are specified in the spec?

@mrc0mmand ^ ?

@jpopelka I think even -S git (and -S git_am) respects the order in which PatchXXX: directives are written down (at least according to the rpm sources), but it's hard to say, the documentation is pretty bare in this regard. However, even if that's true, having the unique number prefix for each patch helps in navigation (as it keeps the patches in order in directory listing), if nothing else.
However, the "merge commit" issue was a real one, and given the discussion in systemd-ci-incubator/systemd#1 there might be something else.

it's defined in /usr/lib/rpm/macros
# Git
%__scm_setup_git(q)\
%{__git} init %{-q}\
%{__git} config user.name "%{__scm_username}"\
%{__git} config user.email "%{__scm_usermail}"\
%{__git} add .\
%{__git} commit %{-q} --allow-empty -a\\\
	--author "%{__scm_author}" -m "%{NAME}-%{VERSION} base"

%__scm_apply_git(qp:m:)\
%{__git} apply --index %{-p:-p%{-p*}} -\
%{__git} commit %{-q} -m %{-m*} --author "%{__scm_author}"

# Git, using "git am" (-m is unused)
%__scm_setup_git_am(q)\
%{expand:%__scm_setup_git %{-q}}

%__scm_apply_git_am(qp:m:)\
%{__git} am %{-q} %{-p:-p%{-p*}}

does this help? :D


Can install Preview needed to run "az aks nodepool stop"

This is autogenerated. Please review and update as needed.
Describe the bug
Command Name
az aks nodepool stop
Errors:
The command failed with an unexpected error. Here is the traceback:
cannot import name 'map_azure_error_to_cli_error'
Traceback (most recent call last):
  File "/opt/az/lib/python3.6/site-packages/knack/cli.py", line 231, in invoke
    cmd_result = self.invocation.execute(args)
  File "/opt/az/lib/python3.6/site-packages/azure/cli/core/commands/__init__.py", line 556, in execute
    self.commands_loader.load_arguments(command)
  File "/opt/az/lib/python3.6/site-packages/azure/cli/core/__init__.py", line 515, in load_arguments
    self.command_table[command].load_arguments()  # this loads the arguments via reflection
  File "/opt/az/lib/python3.6/site-packages/azure/cli/core/commands/__init__.py", line 313, in load_arguments
    super(AzCliCommand, self).load_arguments()
  File "/opt/az/lib/python3.6/site-packages/knack/commands.py", line 104, in load_arguments
    cmd_args = self.arguments_loader()
  File "/opt/az/lib/python3.6/site-packages/azure/cli/core/commands/command_operation.py", line 125, in arguments_loader
    op = self.get_op_handler(self.op_path)
  File "/opt/az/lib/python3.6/site-packages/azure/cli/core/commands/command_operation.py", line 59, in get_op_handler
    handler = import_module(mod_to_import)
  File "/opt/az/lib/python3.6/importlib/__init__.py", line 126, in import_module
    return _bootstrap._gcd_import(name[level:], package, level)
  File "<frozen importlib._bootstrap>", line 994, in _gcd_import
  File "<frozen importlib._bootstrap>", line 971, in _find_and_load
  File "<frozen importlib._bootstrap>", line 955, in _find_and_load_unlocked
  File "<frozen importlib._bootstrap>", line 665, in _load_unlocked
  File "<frozen importlib._bootstrap_external>", line 678, in exec_module
  File "<frozen importlib._bootstrap>", line 219, in _call_with_frames_removed
  File "/home/parlin/.azure/cliextensions/aks-preview/azext_aks_preview/custom.py", line 105, in <module>
    from ._helpers import (
  File "/home/parlin/.azure/cliextensions/aks-preview/azext_aks_preview/_helpers.py", line 7, in <module>
    from azure.cli.command_modules.acs._helpers import map_azure_error_to_cli_error
ImportError: cannot import name 'map_azure_error_to_cli_error'

To Reproduce:
Steps to reproduce the behavior. Note that argument values have been redacted, as they may contain sensitive information.

Put any pre-requisite steps here...
az aks nodepool stop --name {} --cluster-name {} --resource-group {}

Expected Behavior
Environment Summary
Linux-5.15.0-43-generic-x86_64-with-debian-bookworm-sid, Ubuntu 22.04 LTS
Python 3.6.10
Installer: DEB

azure-cli 2.33.1 *

Extensions:
aks-preview 0.5.70
ssh 1.0.0

Dependencies:
msal 1.16.0
azure-mgmt-resource 20.0.0

Additional Context

route to CXP team

@pimanuel97 Thanks for reaching out to us and reporting this issue. I see that you are using an older version of the aks-preview extension. Could you please run the below command to update your extension and check if that helps ? Awaiting your reply.

az extension update -n aks-preview

Thank you
Its working now after uninstall and reinstall newest version.


[Fixes] : Add login and Register functionalities

🖥 Frontend Issue
Description

Login and Register is not functional
Steps to Reproduce

Go to Login or Register page
Enter your credentials and try to login or register
you can see that both the button is not functional

Expected behavior

It should send a request to backend and get a response as well
Actual behavior

It is not sending and request to backend
Screenshots or Video

Are you participating in GSSoC?

[x] Yes
[ ] No

@ak3264114 backend is already added check it and make necessary changes .
I will give level after checking PR
Thanks go ahead

completed


Document what you have learned about django in your WIKI

Document your insights from django progressively in your WIKI page.

Documentation page initialized here


Proposal: error on invalid assignments between classes that share a nominal heritage

This proposal serves, at this point, as an trial-and-error experience for myself and to give you guys some ideas to play with.. I understand this may not be 'it' in current form (or not at all) so don't just stamp it with that dreaded "DECLINED" thing. I'll just close it myself after you explain to me how bad it is and why.. and all the edge cases..(e.g. expressions in extends clauses etc.) or who knows, I may be even able to fix it later..
Let A and B be two classes and a: A, b: B.
For the structurally valid assignment a = b.
Either one of the following conditions should hold to error:

B is a strict nominal ancestor of A.
A is a nominal ancestor of B but with an incompatible generic signature.

Examples:
class Base {
	action = "START WORLD WAR III";
}

class Derived extends Base {
	action = "SAVE THE WORLD";
}

function giveMeDerived(shouldBeDerived: Derived) {
	performAction(shouldBeDerived.action);
}

giveMeDerived(new Base()); // Error! The compiler has saved the world!

class Bag<T> {
    items = [];
}

function putStringsInTheBag(bag: Bag<string>) {
    bag.items.push("a", "b", "c", "d");
}

let bagOfNumbers = new Bag<number>();
putStringsInTheBag(bagOfNumbers); // Error! no strings going in this bag..

class Bag<T> {
    items = [];
}

class BagWithMethod<V> extends Bag<V> {
	putItem(item: V) {
		this.items.push(item);
	}
}

let bagWithMethod = new BagWithMethod<number>();
bagWithMethod.putItem(42);

let evilBag: Bag<string> = bagWithMethod; // Error! evil bag detected!

Note: this could be opt-in through a compiler flag, e.g. --nominalClassChecks..

@malibuzios how is this issue different from #7792? and why not keep the question in #7792?
as mentioned in https://github.com/Microsoft/TypeScript/issues/7792#issuecomment-205476110

You'd probably be interested in #202 or some discussion that happened at #6735

Just to be clear,  the proposal:

Note: this could be opt-in through a compiler flag, e.g. --nominalClassChecks..

is a duplicate of #202

@mhegazy
This proposal is about a particular form of error checking for classes based on nominal an ancestry relations. It doesn't propose any keyword or syntax. I don't believe it is a good idea to combine multiple different proposals into one issue. The issue about generics did not contain a proposal and is closed.

@mhegazy
The idea here is that there would be an error only if the two classes share heritage. If they don't, it would work normally. This doesn't convert all classes to 'nominal' ones, just applies some nominal checking for ones that are related.

I am not sure i follow.. how would that help you with something like:
class Base {
    action = "START WORLD WAR III";
}

class Derived extends Base {
    action = "SAVE THE WORLD";
}

class SomeRandomClassWithActionProperty {
    action = "OOPS"
}

giveMeDerived(new SomeRandomClassWithActionProperty());

Classes today are compared structurally. if i understand correctly, you would want them to be compared in a nominal fashion, which is a fair proposition.
I do not think the proposal here solves the underlying problem, it just carves out a small part of the problem space and special case it under a flag. Do not think this is the correct general solution.
We can not just switch classes to be compared nominally either, as that would be a breaking change. so it has to be an opt-in mode.
we have two options, either have a flag, as you mentioned, or a new keyword/annotation that can be attached to declarations.
If were to add support for this proposal, it would be likely a new keyword. that maintains back compat, and allows for a fine grained control over how the compiler should behave.

@mhegazy
Yep, it only carves a small area. I see this as an idea that shows the granular range of checking that is possible. This is a small, but a meaningful step.
I was hoping that if, say, a nominal checker is implemented anyway, this limited form of checking could be there by default, without a flag, and wouldn't be a heavy breaking change as it is very unlikely someone would one to assign this way on purpose.
There could be some opt-out tricks to work-around the limitation (though it would probably be very rare that anyone would want to do that). Perhaps converting the class to an interface (I know this would work but I'm not sure if it'll have the expected effect)?
class A {};
interface B extends A {};

Anyway, I was giving this as an idea. Since it seems my message seem to have been successful communicated I will close the issue.

@mhegazy
Just wanted to add:
The only scenario I can think of when this check would be effective for base and derived classes is when the derived classes essentially override members without actually changing the structure (this may only last for a part of the chain):
class A {
	a = 1;
	b = 2;
}

class B extends A {
	b = 3;
}

class C extends B {
	a = 2;
}

class D extends C {
	b = 5;
}

Say someone used inheritance this way as just a form of incremental sharing where each extending class simply changed a couple of properties but didn't add anything. They can always use the earliest class in the ancestry with the same structure as a base reference (A in this case), as every part of the chain that 'used' to be mutually assignable would have the same structure.
Say they wrote a function that looked like this:
// What benefit does having the class name as C, rather than A here provides?
function iWantC(c: C) {
};

iWantC(new B()); // Error: this wouldn't work anymore with nominal checking

So the question is what benefit would it give them to use anything other than A here aside from having it as some form of documentation? (in that case, why would they pass B?) as structural typing wouldn't provide any type of safety here anyway? (actually nominal typing seems to provide more safety, maybe that's what they wanted in the first place?)
I think this still needs to be investigated a bit more to decide if something like this could be introduced without a flag..

@malibuzios a historical note: classes used to be nominal in TypeScript, so we've both investigated it (by virtue of having many teams, including our own, trying it out that way) and thought it about it a lot (by virtue of having decided to make a big change to structural typing of classes).
The effect of two similar things in the type system (classes, interfaces) behaving radically differently (nominal, structural) didn't lead to a good user experience. There was more confusion gained than saved by having this behavior.

@RyanCavanaugh
Thanks for stopping by! The more I look at this I started to feel that if introduced something like this should be put under a flag. Someone, somewhere, may actually use classes in this unorthodox way I described (probably someone not coming from the background of nominally typed languages). I don't think it would be a good idea to break it for them. It might look a bit strange when seen abstractly but I guess it could actually fit in some pattern.

@RyanCavanaugh
It is still possible that the checking for generic signatures could, possibly, be introduced without a flag. If there are examples where someone find that behavior useful, these should be pretty insane (though possible though! :). It would be very interesting anyway..


syntax highlighting not displayed properly

I'm not sure when this began to happen, but if you create a .md file and add some bold or italics text, there will be no syntax highlighting for them.
Perhaps not only that. Some other texts look weird, too.

atom-light has the same issue.

Things start to work again after deleting the profile folder. Strange...