Unable to play my other server video

Hello,
I am getting a cross-origin error on the console when hovering on it.
I have videos on s3 server and need to play those videos when hovering on the block.
Please help me to solve my issue.
Thanks.

Hello, this is most likely an issue on your end with the configuration of your s3 bucket rather than an issue with the HoverVideoPlayer component. You will need to set a CORS configuration on the bucket to allow cross-origin requests. This seems like a decent article describing how to do that: https://docs.sevenbridges.com/docs/enabling-cross-origin-resource-sharing-cors

@sitestrokes did that resolve your issue?

hello I am also getting cors error on playing a video in my NodeJS server and I am already allowing cors in my node server. please help me to solve my issue @Gyanreyer


New version: XBMCFoundation.Kodi version <IP_ADDRESS>

Pull request has been created with komac v2.0.0 :rocket:

Resolve: #133540

Microsoft Reviewers: Open in CodeFlow

For moderators
This account is automated by Github Actions and the source code was created by CoolPlayLin. If you have any questions about any pull request, don't hesitate to ping @Exorcism0666, I'll get a notification.

[!important]
Please carefully review these Pull Request before merging. If it is a Pull Request for removing incorrect content and the URLs are issue, free upon manual checking, please close this Pull Request directly. (It is best to inform Exorcism0666 of the closure.)

良い一日をお過ごしください！


Consecutive responses

Easily pass multiple consecutive responses to sttp stub.
Fixes #183

Released in 1.5.10, thanks!


Help needed for Characteristic Write Error

Hello,
I've been using the native android code for some BLE operations, but am now trying to migrate to this library for better stability.
I've been trying to write a payload (broken up into 20 byte packets) to a peripheral but I'm getting an error when the following code is called. (I know LongWriteBuilder is available but its not a function I can use atm.)
private fun RxBleConnection.batchWrites(payload: ByteArray, mtu: Int, characteristicUUID: UUID): Completable {
        val cPayload = payload.clone()
        return this.writeCharacteristic(characteristicUUID, cPayload.getNextPacket(mtu))
                .doOnSuccess { Timber.d("Successfully wrote packet: ${payload.toPlainHex()}") }
                .repeatUntil { cPayload.isEmpty() }
                .ignoreElements()

    }

I've been getting error 133 from multiple phones (Pixel 2, Oneplus 3) when it tries to write to the peripheral. Any advice would be appreciated.
(Edit): Similar issue to #210 . I'm still searching around for a reason.

Hello
Thanks for using the library!
It looks that something is off with your peripheral if BLE stacks of Pixel 2 and OnePlus 3 are not handling normal writes
Btw. The above code will repeat indefinitely as cPayload.getNextPacket(mtu) is called only once.

Hello!
Thanks for the prompt reply. cPayload.getNextPacket() will drop the bytes it returns, so the array will eventually empty out.
I've implemented the same behaviour with the Native Android BLE library and it works fine with both phones. So the difference in behaviour is somewhat confusing. I'll put up the logs and more code from my implementation in a few hours.

try to change this:
this.writeCharacteristic(characteristicUUID, cPayload.getNextPacket(mtu))

into this:
Single.defer { this.writeCharacteristic(characteristicUUID, cPayload.getNextPacket(mtu)) }

Then each .repeatUntil { cPayload.isEmpty() } will actually be called with cPayload.getNextPacket(mtu).

Thanks alot for the heads up!
Here is the logs for the error I'm receiving.
14307-16162 D: QUEUED   CharacteristicWriteOperation(129362019)
14307-16161 D: STARTED  CharacteristicWriteOperation(129362019)
14307-14327 D: onCharacteristicWrite characteristic=5c3a659f-897e-45e1-b016-007107c96df6 status=133
14307-14327 D: onClientConnectionState() - status=19 clientIf=6 device=ED:11:D4:AD:25:69
14307-16161 D: FINISHED CharacteristicWriteOperation(129362019) in 311 ms
14307-16162 E: Write failed.
    com.polidea.rxandroidble2.exceptions.BleGattCharacteristicException: GATT exception from MAC address ED:11:D4:AD:25:69, status 133, type BleGattOperation{description='CHARACTERISTIC_WRITE'}. (Look up status 0x85 here https://android.googlesource.com/platform/external/bluetooth/bluedroid/+/android-5.1.0_r1/stack/include/gatt_api.h)
        at com.polidea.rxandroidble2.internal.connection.RxBleGattCallback.propagateErrorIfOccurred(RxBleGattCallback.java:228)
        at com.polidea.rxandroidble2.internal.connection.RxBleGattCallback.access$800(RxBleGattCallback.java:33)
        at com.polidea.rxandroidble2.internal.connection.RxBleGattCallback$2.onCharacteristicWrite(RxBleGattCallback.java:122)
        at android.bluetooth.BluetoothGatt$1$7.run(BluetoothGatt.java:407)
        at android.bluetooth.BluetoothGatt.runOrQueueCallback(BluetoothGatt.java:711)
        at android.bluetooth.BluetoothGatt.-wrap0(Unknown Source:0)
        at android.bluetooth.BluetoothGatt$1.onCharacteristicWrite(BluetoothGatt.java:403)
        at android.bluetooth.IBluetoothGattCallback$Stub.onTransact(IBluetoothGattCallback.java:136)
        at android.os.Binder.execTransact(Binder.java:692)
14307-14327 D: onConnectionStateChange newState=0 status=19
14307-14327 I: Connection operations queue to be terminated (ED:11:D4:AD:25:69)
14307-16161 D: Terminated.
14307-16162 D: QUEUED   DisconnectOperation(266990873)

And this is what I'm using to connect:
fun connect(connectionType: ConnectionType): Observable<ConnectionState> {
        val startTime = System.currentTimeMillis()
        this.connectionType = connectionType
        return rxBleDevice.establishConnection(false)
                .doOnSubscribe { Timber.d("Attempting to connect to: ${this.name}") }
                .doOnNext {
                    this.bleConnection = it
                    Timber.d("BLE Connection to ${name} took: ${System.currentTimeMillis() - startTime}ms")
                }.flatMap {connection -> connection.discoverServices().toObservable().map { Pair(connection, it) } }
                .doOnNext {
                    Timber.d("Successfully discovered services. Took: ${System.currentTimeMillis() - startTime}ms")
                    if (disposableList.find { it.purpose == DisposableHolder.PURPOSE_NOTIFICATION } == null) {
                        disposableList.add(DisposableHolder(
                                DisposableHolder.PURPOSE_NOTIFICATION,
                                it.first.setupNotification(getCurrentCharacteristicUUID(), NotificationSetupMode.COMPAT)
                                        .mergeWith(it.first.writeDescriptor(serviceUUID.uuid, getCurrentCharacteristicUUID(), getCurrentDescriptorUUID(), BluetoothGattDescriptor.ENABLE_NOTIFICATION_VALUE))
                                        .doOnNext { Timber.d("Successfully setup notification. Took: ${System.currentTimeMillis() - startTime}ms") }
                                        .flatMap { it }
                                        .subscribe({
                                            handleBleNotification(it)
                                        }, {
                                            Timber.e(it, "Error setting up notification.")
                                            teardownConnection()
                                        })
                        ))}
                }
                .flatMapCompletable { establishSecureConnection(connectionType) }
                .andThen(Observable.just(ConnectionState.Connected))
    }

Your peripheral is not properly responding for the write and then it disconnects (14307-14327 D: onConnectionStateChange newState=0 status=19)
This seems to be a business logic issue — not library

Hello Darius,
I found the issue. Was send the peripheral incorrect data, forcing the peripheral to disconnect. Thanks alot for your time and advice!


DD_CONTAINER_EXCLUDE_LOGS excludes matching like namespaces #471

Output of the info page (if this is a bug)
root@datadog-xt2h9:/# agent status
2021-12-13 20:03:24 UTC | CORE | WARN | (pkg/util/log/log.go:630 in func1) | Deactivating Autoconfig will disable most components. It's recommended to use autoconfig_exclude_features and autoconfig_include_features to activate/deactivate features selectively
Getting the status from the agent.

2021-12-13 20:03:24 UTC | CORE | INFO | (cmd/system-probe/config/config.go:172 in load) | network_config.enabled detected: enabling system-probe with network module running.
===============
Agent (v7.32.1)
===============

  Status date: 2021-12-13 20:03:24.525 UTC<PHONE_NUMBER>525)
  Agent start: 2021-12-13 16:22:34.644 UTC<PHONE_NUMBER>644)
  Pid: 1
  Go Version: go1.16.7
  Python Version: 3.8.11
  Build arch: amd64
  Agent flavor: agent
  Check Runners: 4
  Log Level: INFO

  Paths
  =====
    Config File: /etc/datadog-agent/datadog.yaml
    conf.d: /etc/datadog-agent/conf.d
    checks.d: /etc/datadog-agent/checks.d

  Clocks
  ======
    NTP offset: -400µs
    System time: 2021-12-13 20:03:24.525 UTC<PHONE_NUMBER>525)

  Host Info
  =========
    bootTime: 2021-10-20 12:19:31 UTC<PHONE_NUMBER>000)
    kernelArch: x86_64
    kernelVersion: 5.8.0-1041-aws
    os: linux
    platform: ubuntu
    platformFamily: debian
    platformVersion: 21.04
    procs: 286
    uptime: 1300h3m11s
    virtualizationRole: guest
    virtualizationSystem: docker

  Hostnames
  =========
    ec2-hostname: xxxx
    host_aliases: xxxx
    hostname: i-xx
    instance-id: i-xx
    socket-fqdn: datadog-xt2h9
    socket-hostname: datadog-xt2h9
    host tags:
      "env:production"
      kube_node_role:node
    hostname provider: aws
    unused hostname providers:
      azure: azure_hostname_style is set to 'os'
      configuration/environment: hostname is empty
      gce: unable to retrieve hostname from GCE: status code 404 trying to GET http://xxx/computeMetadata/v1/instance/hostname

  Metadata
  ========
    cloud_provider: AWS
    hostname_source: aws

=========
Collector
=========

  Running Checks
  ==============

    cpu
    ---
      Instance ID: cpu [OK]
      Configuration Source: file:/etc/datadog-agent/conf.d/cpu.d/conf.yaml.default
      Total Runs: 883
      Metric Samples: Last Run: 9, Total: 7,940
      Events: Last Run: 0, Total: 0
      Service Checks: Last Run: 0, Total: 0
      Average Execution Time : 0s
      Last Execution Date : 2021-12-13 20:03:11 UTC<PHONE_NUMBER>000)
      Last Successful Execution Date : 2021-12-13 20:03:11 UTC<PHONE_NUMBER>000)

    disk (4.4.0)
    ------------
      Instance ID: disk:exxxx [OK]
      Configuration Source: file:/etc/datadog-agent/conf.d/disk.d/conf.yaml.default
      Total Runs: 883
      Metric Samples: Last Run: 372, Total: 328,476
      Events: Last Run: 0, Total: 0
      Service Checks: Last Run: 0, Total: 0
      Average Execution Time : 41ms
      Last Execution Date : 2021-12-13 20:03:18 UTC<PHONE_NUMBER>000)
      Last Successful Execution Date : 2021-12-13 20:03:18 UTC<PHONE_NUMBER>000)

    docker
    ------
      Instance ID: docker [OK]
      Configuration Source: file:/etc/datadog-agent/conf.d/docker.d/conf.yaml.default
      Total Runs: 882
      Metric Samples: Last Run: 206, Total: 181,692
      Events: Last Run: 1, Total: 1
      Service Checks: Last Run: 1, Total: 882
      Average Execution Time : 38ms
      Last Execution Date : 2021-12-13 20:03:10 UTC<PHONE_NUMBER>000)
      Last Successful Execution Date : 2021-12-13 20:03:10 UTC<PHONE_NUMBER>000)

    file_handle
    -----------
      Instance ID: file_handle [OK]
      Configuration Source: file:/etc/datadog-agent/conf.d/file_handle.d/conf.yaml.default
      Total Runs: 883
      Metric Samples: Last Run: 5, Total: 4,415
      Events: Last Run: 0, Total: 0
      Service Checks: Last Run: 0, Total: 0
      Average Execution Time : 0s
      Last Execution Date : 2021-12-13 20:03:17 UTC<PHONE_NUMBER>000)
      Last Successful Execution Date : 2021-12-13 20:03:17 UTC<PHONE_NUMBER>000)

    io
    --
      Instance ID: io [OK]
      Configuration Source: file:/etc/datadog-agent/conf.d/io.d/conf.yaml.default
      Total Runs: 882
      Metric Samples: Last Run: 208, Total: 183,312
      Events: Last Run: 0, Total: 0
      Service Checks: Last Run: 0, Total: 0
      Average Execution Time : 0s
      Last Execution Date : 2021-12-13 20:03:09 UTC<PHONE_NUMBER>000)
      Last Successful Execution Date : 2021-12-13 20:03:09 UTC<PHONE_NUMBER>000)

    kubelet (7.1.0)
    ---------------
      Instance ID: kubelet:5bbc63f3938c02f4 [OK]
      Configuration Source: file:/etc/datadog-agent/conf.d/kubelet.d/conf.yaml.default
      Total Runs: 663
      Metric Samples: Last Run: 549, Total: 363,979
      Events: Last Run: 0, Total: 0
      Service Checks: Last Run: 4, Total: 2,652
      Average Execution Time : 241ms
      Last Execution Date : 2021-12-13 20:03:21 UTC<PHONE_NUMBER>000)
      Last Successful Execution Date : 2021-12-13 20:03:21 UTC<PHONE_NUMBER>000)

    load
    ----
      Instance ID: load [OK]
      Configuration Source: file:/etc/datadog-agent/conf.d/load.d/conf.yaml.default
      Total Runs: 883
      Metric Samples: Last Run: 6, Total: 5,298
      Events: Last Run: 0, Total: 0
      Service Checks: Last Run: 0, Total: 0
      Average Execution Time : 0s
      Last Execution Date : 2021-12-13 20:03:16 UTC<PHONE_NUMBER>000)
      Last Successful Execution Date : 2021-12-13 20:03:16 UTC<PHONE_NUMBER>000)

    memory
    ------
      Instance ID: memory [OK]
      Configuration Source: file:/etc/datadog-agent/conf.d/memory.d/conf.yaml.default
      Total Runs: 883
      Metric Samples: Last Run: 18, Total: 15,894
      Events: Last Run: 0, Total: 0
      Service Checks: Last Run: 0, Total: 0
      Average Execution Time : 0s
      Last Execution Date : 2021-12-13 20:03:23 UTC<PHONE_NUMBER>000)
      Last Successful Execution Date : 2021-12-13 20:03:23 UTC<PHONE_NUMBER>000)

    network (2.4.0)
    ---------------
      Instance ID: network:d884b5186b651429 [OK]
      Configuration Source: file:/etc/datadog-agent/conf.d/network.d/conf.yaml.default
      Total Runs: 883
      Metric Samples: Last Run: 55, Total: 48,565
      Events: Last Run: 0, Total: 0
      Service Checks: Last Run: 0, Total: 0
      Average Execution Time : 3ms
      Last Execution Date : 2021-12-13 20:03:15 UTC<PHONE_NUMBER>000)
      Last Successful Execution Date : 2021-12-13 20:03:15 UTC<PHONE_NUMBER>000)

    ntp
    ---
      Instance ID: ntp:d884b5186b651429 [OK]
      Configuration Source: file:/etc/datadog-agent/conf.d/ntp.d/conf.yaml.default
      Total Runs: 15
      Metric Samples: Last Run: 1, Total: 15
      Events: Last Run: 0, Total: 0
      Service Checks: Last Run: 1, Total: 15
      Average Execution Time : 0s
      Last Execution Date : 2021-12-13 19:52:41 UTC<PHONE_NUMBER>000)
      Last Successful Execution Date : 2021-12-13 19:52:41 UTC<PHONE_NUMBER>000)

    uptime
    ------
      Instance ID: uptime [OK]
      Configuration Source: file:/etc/datadog-agent/conf.d/uptime.d/conf.yaml.default
      Total Runs: 883
      Metric Samples: Last Run: 1, Total: 883
      Events: Last Run: 0, Total: 0
      Service Checks: Last Run: 0, Total: 0
      Average Execution Time : 0s
      Last Execution Date : 2021-12-13 20:03:22 UTC<PHONE_NUMBER>000)
      Last Successful Execution Date : 2021-12-13 20:03:22 UTC<PHONE_NUMBER>000)

========
JMXFetch
========

  Information
  ==================
  Initialized checks
  ==================
    no checks

  Failed checks
  =============
    no checks

=========
Forwarder
=========

  Transactions
  ============
    Cluster: 0
    ClusterRole: 0
    ClusterRoleBinding: 0
    CronJob: 0
    DaemonSet: 0
    Deployment: 0
    Dropped: 0
    HighPriorityQueueFull: 0
    Job: 0
    Node: 0
    PersistentVolume: 0
    PersistentVolumeClaim: 0
    Pod: 0
    ReplicaSet: 0
    Requeued: 1
    Retried: 1
    RetryQueueSize: 0
    Role: 0
    RoleBinding: 0
    Service: 0
    ServiceAccount: 0
    StatefulSet: 0

  Transaction Successes
  =====================
    Total number: 1864
    Successes By Endpoint:
      check_run_v1: 883
      intake: 98
      series_v1: 883

  Transaction Errors
  ==================
    Total number: 1
    Errors By Type:

  API Keys status
  ===============
    API key ending with xxxx: API Key valid

==========
Endpoints
==========
  https://app.datadoghq.eu - API Key ending with:
      - xxxx

==========
Logs Agent
==========

    Sending compressed logs in HTTPS to agent-http-intake.logs.datadoghq.eu on port 443
    BytesSent: 1.3538048e+07
    EncodedBytesSent: 1.778179e+06
    LogsProcessed: 11318
    LogsSent: 11318

  kube-system/kube-proxy-xxxxx.eu-central-1.compute.internal/kube-proxy
  -------------------------------------------------------------------------------
    - Type: file
      Identifier: fb8a5e91607d146b49555cb0a5513dbafe00f21cfe05433bd5c8626e10b56eff
      Path: /var/log/pods/kube-system_kube-proxy-ip-xxxx.eu-central-1.compute.internal_f871400f937e6cb8d8b323b4e1281121/kube-proxy/*.log
      Status: OK
        1 files tailed out of 1 files matching
      Inputs:
        /var/log/pods/kube-system_kube-proxy-ip-xxxx.eu-central-1.compute.internal_f871400f937e6cb8d8b323b4e1281121/kube-proxy/0.log
      BytesRead: 8094
      Average Latency (ms): 0
      24h Average Latency (ms): 0
      Peak Latency (ms): 11
      24h Peak Latency (ms): 11

  container_collect_all
  ---------------------
    - Type: docker
      Status: Pending
      BytesRead: 0
      Average Latency (ms): 0
      24h Average Latency (ms): 0
      Peak Latency (ms): 0
      24h Peak Latency (ms): 0

  datadog/datadog-xt2h9/process-agent
  -----------------------------------
    - Type: file
      Identifier: d7023d1aaaf08ea472e94b11a2c19847156fc20be48ffbb98f7cdd42d5a14a36
      Path: /var/log/pods/datadog_datadog-xt2h9_c33d07b5-e3b9-4f34-8391-ed08d3950617/process-agent/*.log
      Status: Pending
        1 files tailed out of 1 files matching
      BytesRead: 0
      Average Latency (ms): 0
      24h Average Latency (ms): 0
      Peak Latency (ms): 0
      24h Peak Latency (ms): 0

============
System Probe
============
System Probe is running

=========
Aggregator
=========
  Checks Metric Sample: 1,157,715
  Dogstatsd Metric Sample: 208,049
  Event: 2
  Events Flushed: 2
  Number Of Flushes: 883
  Series Flushed: 1,030,670
  Service Check: 12,172
  Service Checks Flushed: 13,052
=========
DogStatsD
=========
  Event Packets: 0
  Event Parse Errors: 0
  Metric Packets: 208,048
  Metric Parse Errors: 0
  Service Check Packets: 0
  Service Check Parse Errors: 0
  Udp Bytes: 20,564,669
  Udp Packet Reading Errors: 0
  Udp Packets: 128,750
  Uds Bytes: 0
  Uds Origin Detection Errors: 0
  Uds Packet Reading Errors: 0
  Uds Packets: 1
  Unterminated Metric Errors: 0

=====================
Datadog Cluster Agent
=====================

  - Datadog Cluster Agent endpoint detected: https://xxxx:5005
  Successfully connected to the Datadog Cluster Agent.
  - Running: 1.16.0+commit.9961689

=============
Autodiscovery
=============
  Enabled Features
  ================
    docker
    kubernetes```

**Describe what happened:**

We're using DD agent in our k8s cluster hosted on AWS, we have the following exclude rules:

DD_CONTAINER_EXCLUDE_LOGS="kube_namespace:logging kube_namespace:monitoring"
We want to exclude logs from logging and monitoring namespaces, the issue appears for other namespaces called processing-logging and processing-monitoring as we want to fetch logs from those namespaces as well, but it seems
DD-agent configuration excludes them because of the DD_CONTAINER_EXCLUDE_LOGS flag.

**Describe what you expected:**
Only logs from namespaces that match exactly the flag DD_CONTAINER_EXCLUDE_LOGS should be excluded, unless there's another workaround for this.

**Steps to reproduce the issue:**

DD_CONTAINER_EXCLUDE_LOGS="kube_namespace:login"
namespace logging : pod test_pod_1
namespace processing-logging: : pod test_pod_2
namespace test : pod test_pod_3
Only logs from the test namespace is appearing in the DD dashboard.

**Additional environment details (Operating System, Cloud provider, etc):**
AWS cloud provider
Agent version: `Agent 7.32.1 - Commit: 52f034f - Serialization version: v4.85.0 - Go version: go1.16.7`
Datadog Helm version: `2.27.5`

Thank you

resolved in dd-helm repo comment :
https://github.com/DataDog/helm-charts/issues/471#issuecomment-993363027


VS2017 RC3: Failure to update many projects from project.json to csproj

##Repro steps:
git clone https://github.com/exceptionless/Exceptionless.Net
Open the .sln file in VS 2017 RC3
Migrate the project.json based projects to .csproj.
##Expected Results
The migration should succeed.
##Actual Results
UpgradeLog.htm.txt
Many projects fail to upgrade

https://github.com/exceptionless/Exceptionless.Net/commit/31ef359ae1f778c7c0a39a268323ad1f3c12381a

Thanks, we'll take a look.

RC3 was affected by this bug: https://github.com/dotnet/roslyn-project-system/issues/1376. Confirmed the issue does not repro on latest internal builds, I have a clean migration report.
However, I am not seeing a NuGet restore getting kicked off for the project, build is complaining about missing package.assets.json. @srivatsn @natidea

I'm going to close this issue, since the original problem is fixed. The NuGet issue appears to be the same one filed by @krwq: https://github.com/dotnet/roslyn-project-system/issues/1447.

This is still broken, my project upgrades in the latest build but the compiler directives are lost on a per framework basis (only some of them are copied).
  <PropertyGroup Condition=" '$(TargetFramework)' == 'netstandard1.2' ">
    <DefineConstants>$(DefineConstants);NO_SQL_CLIENT;NETSTANDARD;NETSTANDARD1_2</DefineConstants>
    <DebugType>portable</DebugType>
  </PropertyGroup>

  <PropertyGroup Condition=" '$(TargetFramework)' == 'netstandard1.3' ">
    <DefineConstants>$(DefineConstants);NETSTANDARD1_3</DefineConstants>
  </PropertyGroup>

Both of them should have NO_SQL_CLIENT and NETSTANDARD


Add version: pnpm.pnpm.6 version 6.32.10

[X] Have you signed the Contributor License Agreement?
[X] Have you checked that there aren't other open pull requests for the same manifest update/change?

[ ] Have you tested your manifest locally with winget install --manifest <path>?
[ ] Does your manifest conform to the 1.1 schema?

Microsoft Reviewers: Open in CodeFlow

@wingetbot run

@wingetbot waivers Add Validation-Executable-Error


[Urgent] .setStatus crashes the bot.

It won't even give me an error, just crashes the bot. I'm doing everything according to the docs so I don't know what's going on.

Have you tried turning it off and on? Try looking at how eris does it and see if you're doing anything wrong or the docs are wrong

Ahh, I'll try turning it off and on. Seriously, will do.

I'll try looking at this asap. If catching does nothing then it means it closes the ws connection without attempting to retry

Have you tried turning it off and on? Try looking at how eris does it and see if you're doing anything wrong or if the docs are wrong

I’m not seeing anything different about the way Eris handles it and we’re handling it right now, apart from a few added things.

I've fixed it with the help of the all legendary Tim 😆


How to handle data from repository to presentation as JSON for REST API

I'm trying to come up with a good way to go from sql database data to json response on a web api.
I want to return product data but with formatted data for a frontend.
My product has pricing that needs to be formatted as well as vendor and category etc.
I want to return something similar
[{
	"id": 123,
	"title": "product1",
	"price": {
		"formatted": "$10",
		"currency": "USD",
		"regular": 2000,
		"sale": 1000,
		"discountFormatted": "50% off"
	},
	"category": {
		"id": 12,
		"title": "category1"
	},
	"vendor": {
		"id": 155,
		"title": "vendor1"
	}
}]

Now I'm wondering should I make a Data object for each part (ProductData, ProductPriceData, ProductVendorData) and then reference them all in ProductData.
And should the formatted parts be prepared in the repository or service classes?
Thank you for your help.

In this case, I would fetch the needed data as an array using the Repository methods. Then loop and map this array(s) into the needed data structure (also an array) in a custom Service class. Let the JsonRenderer convert this Domain result into a JSON response.

Ok so fetch raw data from Repo and then transform it in service class. Would I use multiple data classes and combine them into an array in the service? I appreciate the help!
Example
ProductData

Title
Price
ProductCategoryData

Title
Id
Slug

ProductBrandData

Title
Id
Slug

If you use the results from the repository only in this specific context, an extra data class is not needed, because the scope of the data is so small that there is no real benefit to add extra classes for it. Of course, it depends on your specific use case.

I just found this video that explains when and how you can / should use DTOs:
Data Transfer Objects - What Are DTOs
There is also this blog post about this topic:
Stop returning arrays, use objects instead
But he also says that:

You should also consider returning an array if the call is solely internal (between protected methods, for example); value objects should be used for external calls, but arrays are perfectly suitable for internal calls.

This is how I do it in practice as well. I prefer to return arrays from a repositories' method (for a list of records), but if I want to carry data over multiple places I prefer to use objects (DTO's) instead.
I'm closing this issue for now. If you have any further questions, feel free to ask.


Components should support a root-element that is an SVG

@Component(
  selector: 'svg:[example]'
  directives: [],
  template: '<svg:path [attr.example]="name"></svg:path>',
  changeDetection: ChangeDetectionStrategy.OnPush,
)
class SvgHostComponent {
  @Input()
  String name;
}

It looks like we call createElementNS with the wrong arguments:
_el_0 = doc.createElementNS('http://www.w3.org/2000/svg', 'path');

... instead of:
_el_0 = doc.createElementNS('http://www.w3.org/2000/svg', 'svg', 'path');

On second look, this looks valid:
https://stackoverflow.com/questions/22806022/how-to-use-svg-namespace-in-xhtml-documents

As far as I can tell you can't currently split an SVG into smaller components because the elements are inserted with the wrong namespace. Is this correct and if so will this be supported in the future?  All other major frameworks/libraries support this as far as I know (except the ones that explicitly use web components).


Bits for base address 0x41580, frame 27

These Litex bits:

# In frame 0x0040159b 24 bits were not converted.
{ unknown_bit = "0040159b_53_6", unknown_segment = "0x00401580", unknown_segbit = "27_1702" }
{ unknown_bit = "0040159b_57_6", unknown_segment = "0x00401580", unknown_segbit = "27_1830" }
{ unknown_bit = "0040159b_61_6", unknown_segment = "0x00401580", unknown_segbit = "27_1958" }
{ unknown_bit = "0040159b_69_6", unknown_segment = "0x00401580", unknown_segbit = "27_2214" }
{ unknown_bit = "0040159b_77_6", unknown_segment = "0x00401580", unknown_segbit = "27_2470" }
{ unknown_bit = "0040159b_81_6", unknown_segment = "0x00401580", unknown_segbit = "27_2598" }
{ unknown_bit = "0040159b_85_6", unknown_segment = "0x00401580", unknown_segbit = "27_2726" }
{ unknown_bit = "0040159b_93_6", unknown_segment = "0x00401580", unknown_segbit = "27_2982" }
{ unknown_bit = "0040159b_54_6", unknown_segment = "0x00401580", unknown_segbit = "27_1734" }
{ unknown_bit = "0040159b_58_6", unknown_segment = "0x00401580", unknown_segbit = "27_1862" }
{ unknown_bit = "0040159b_62_6", unknown_segment = "0x00401580", unknown_segbit = "27_1990" }
{ unknown_bit = "0040159b_70_6", unknown_segment = "0x00401580", unknown_segbit = "27_2246" }
{ unknown_bit = "0040159b_78_6", unknown_segment = "0x00401580", unknown_segbit = "27_2502" }
{ unknown_bit = "0040159b_82_6", unknown_segment = "0x00401580", unknown_segbit = "27_2630" }
{ unknown_bit = "0040159b_86_6", unknown_segment = "0x00401580", unknown_segbit = "27_2758" }
{ unknown_bit = "0040159b_94_6", unknown_segment = "0x00401580", unknown_segbit = "27_3014" }
{ unknown_bit = "0040159b_83_18", unknown_segment = "0x00401580", unknown_segbit = "27_2674" }
{ unknown_bit = "0040159b_91_18", unknown_segment = "0x00401580", unknown_segbit = "27_2930" }
{ unknown_bit = "0040159b_95_18", unknown_segment = "0x00401580", unknown_segbit = "27_3058" }
{ unknown_bit = "0040159b_55_18", unknown_segment = "0x00401580", unknown_segbit = "27_1778" }
{ unknown_bit = "0040159b_59_18", unknown_segment = "0x00401580", unknown_segbit = "27_1906" }
{ unknown_bit = "0040159b_67_18", unknown_segment = "0x00401580", unknown_segbit = "27_2162" }
{ unknown_bit = "0040159b_71_18", unknown_segment = "0x00401580", unknown_segbit = "27_2290" }
{ unknown_bit = "0040159b_79_18", unknown_segment = "0x00401580", unknown_segbit = "27_2546" }

are solved by

RIOB33.IOB_Y0.ISERDES.27_18 27_18
RIOB33.IOB_Y0.ISERDES.27_70 27_70
RIOB33.IOB_Y0.ISERDES.27_102 27_102

`27_70 is associated with ISERDES.IN_USE along with few other bits.
The ISERDES.IN_USE is spread across many of the bits we are currently missing for Litex...

RIOB33.IOB_Y0.ISERDES.27_18 27_18 is solved by #991, but it is not Y0: IOB33.IOB_Y1.ISERDES.DATA_WIDTH.W8 27_18

All bits in this frame are solved by current or pending PR's.


Adding a Roster file based Discovery plugin

Adds the ability to specify hosts via the master Automatron configuration file.
Includes:

Plugin
Documentation
Unit Tests

Coverage increased (+0.6%) to 83.464% when pulling 93b7409b0ee3f2142b3bd2931027fee989139b00 on config-discovery into 4138ca463aa78c8353b62cf4bc926a583242d8b6 on develop.


Sensors don't always refresh after HA restart

https://github.com/habuild/hassio-addons/blob/4a33e0fae5350dafc7e57392493f3a48dc17c37f/triinv-sbfspot/Dockerfile#L91
When I restarted my home assistant after dark, all of my entities were unavailable.  When I then restarted HAOS-SBFspot, they started working.

See post 260 for more info
https://community.home-assistant.io/t/sbfspot-bluetooth-homeassistant-addon/402671/260?u=hasqt


MessageCollection has "total" > 0 but "items" is empty?

Describe the bug
Due to Microsoft removing support for Basic authentication using IMAP, I recently switched to oAuth. With everything else left unchanged, my code suddenly fetches a MessageCollection with a "total" of 9 messages (the exact amount currently in the INBOX) but has an empty "items" array. When enabling debug mode, the messages do actually show up in the console output. In addition, the messages are flagged as read even though "leaveUnread()" is specified.
Used config
'host'  => 'outlook.office365.com',
'port'  => 993,
'protocol'  => 'imap'
'encryption'    => 'ssl'
'validate_cert' => true,
'username' => 'xxx'
'authentication' => 'oauth'

Code to Reproduce
$folder = $client->getFolderByName('INBOX');
$messages = $folder->messages()->all()->leaveUnread()->get();

dump($messages);

Expected behavior
"item" array within MessageCollection contains the 9 messages currently in the INBOX.
Screenshots
Webklex\PHPIMAP\Support\MessageCollection^ {#2235
  #total: 9
  #items: []
  #escapeWhenCastingToString: false
}

Desktop / Server (please complete the following information):

OS: Windows 10
PHP: 7.4
Version: 4.1.1
Provider: M365 / Exchange

Any ideas anyone?

After diving into the libraries code myself I figured out the issue. In my configuration file, for some reason the sequence-option was set to 'sequence' => \Webklex\PHPIMAP\IMAP::ST_MSGN instead of \Webklex\PHPIMAP\IMAP::ST_UID. After changing it, the MessageCollection contained the items as expected.


Make install-ansible.sh work with Linux Mint and enable swap by default but decrease vm.swappiness

Just a small one to make it work with Linux Mint
I would like to see the swap enabled by default to guarantee a better resilience. Instead of turning swap completely of the way to go for better performance is to decrease vm.swappiness

Please execute the script to generate group vars files. It's at the root of the repos

Thanks leseb. I'll close the pull request here. Feel free to add the Linux Mint thing.
Cheers

@mcsage why did you close this?

test this please


Remove the last references to static context timeouts in conformance tests

/kind test
What this PR does / why we need it:
This PR removes the last references to static conformance test context timeouts so that implementations can tailor the timeouts to the environment they're run in (e.g. VMs with slower LB address provisioning)

/release-note-none

Thanks @keithmattix!
/lgtm


[2.1.1]Failed to validate cluster: Hostname_override

此集群当前为Updating
Failed to validate cluster: Hostname_override [DataCenter005] for host (1) is not valid: [a DNS-1123 subdomain must consist of lower case alphanumeric characters, '-' or '.', and must start and end with an alphanumeric character (e.g. 'example.com', regex used for validation is 'a-z0-9?(.a-z0-9?)*')]

I modified hostname, still can't update end.

The workaround is mentioned in https://github.com/rancher/rancher/issues/16294

Modified to lowercase letters, still can't update end.


etherlime flatten overloads node.js

etherlime flatten overloads node.js and doesn't complete running.
You can reproduce with argent-contracts repo by running etherlime flatten modules/TransferManager.sol there.

Hi, Elena! I spent some hours to figure out what causes your problem and it seems that you are importing BaseWallet.sol in Module.sol and then also importing Module.sol in BaseWallet.sol. The flattener embeds the content of all imported files first and and at the end the content of the main contract. In this scenario it could not record neither the BaseWallet.sol nor Module.sol (it's some kind of recursion because it would always try to record the imported file first).
The content of imported contracts must be before the content of the main one, otherwise it would throw an error that can not find the resource when trying to compile the flattened .sol.
I haven't gotten into the logic of your contracts, so I don't know whether importing the contracts each other is what you really need.
I'll be glad to help if needed :)

I see, but the problem is that this is valid Solidity which does support such circular dependencies. This is considered safe because neither is inheriting from the other. It's also not a good practice to iterate through the imports sequentially as when imports are repetitive, there'll be duplicated contract code in the flattened version in addition to problems like the above. Logically it seems that a superset of all imports should be composed first and then their source pulled into the flat contract.

Hey, Elena! We've just released new version of etherlime and it should fixes the issue. I've totally rewrote the flattener algorithm so it allows now circular dependencies. Hope that would be useful for you! :)

I'm still getting the same behaviour with 2.3.3 :(

I have tested with the repo you provided and it was able to flatten the TransferManager contract. Just to be sure, can you check with etherlime --version?

Sorry @desimira my mistake, I was running a different install globally. Confirming this works now.


Question about parameter --timeBased

I have a question for the --timeBased parameter.
If I use this parameter with the --parallelRun parameter, does it sort the tests by runtime?
Does it run the long running tests in parallel first and after them the tests, which are faster?

Actually, the idea is that it will collect data about the tests and the time. On the next runs it will use the data to group the tests but equal total time between different processes. There isn't a logic to run the long running first. I hope I managed to answer.


SqlServer module not found

Tested with pre-release: BcContainerHelper is version 6.0.16
Create a multi tenant container based on artifact: https://bcartifacts.azureedge.net/sandbox/24.0.16410.18040/nl
After creating the multtenant container:

Replace App.DB with bacpac from our full build
Replace Tenant DB with default DB from our master sample set

Sync / upgrade environment all went well
Bacpacs created without problems
For development purposes we transform the DB into Single tenant again
Move all apps to DevEndpoint
When invoking the Backup-Navdatabases receive following error:
Backup-NavContainerDatabases -containerName "$ContainerName"         -bakFolder "$BackupFolder"
-Verbose
Backing up default to c:\s-Extensions\database\database.bak
The module 'SqlServer' could not be loaded. For more information, run 'Import-Module SqlServer'.
Exception Script Stack Trace:
at Backup-SqlDatabase, C:\run\pscoreoverrides.ps1: line 2
at Backup, : line 20
at , : line 65
PowerShell Call Stack:
at Invoke-ScriptInBcContainer, C:\Users\buildadmin2\Documents\WindowsPowerShell\Modules\bccontainerhelper\6.0.16\ContainerHandling\Invoke-ScriptInNavContainer.ps1: line 71
at Backup-BcContainerDatabases, C:\Users\buildadmin2\Documents\WindowsPowerShell\Modules\bccontainerhelper\6.0.16\Bacpac\Backup-NavContainerDatabases.ps1: line 52
at , C:\agent2_work\64\s\DevOps.Builds\ERP AL\Invoke-Master-CreateDevelopmentDB.ps1: line 103
at , : line 1
at , C:\agent2_work_tasks\AzurePowerShell_72a1931b-effb-4d2e-8fd8-f8472a07cb62\4.238.7\azurepowershell.ps1: line 261
at , C:\agent2_work_tasks\AzurePowerShell_72a1931b-effb-4d2e-8fd8-f8472a07cb62\4.238.7\azurepowershell.ps1: line 257
at , : line 1
at , : line 22
at , : line 18
at , : line 1
Currently trying with workaround :
New-cdsaAzureDevOpsSection -Message "Workaround BC24 - Install SqlServer module"
Invoke-ScriptInNavContainer -containerName $ContainerName -usePwsh:$false -scriptblock  {
Install-Module PowerShellGet -AllowClobber -Force -verbose -Repository PSGallery
Install-Module -Name SqlServer -RequiredVersion 21.1.18256 -Force -AllowClobber
}

Full log?
(which generic image is used)

and...
If you use docker exec -it containername pwsh and type Import-Module SqlServer (without you adding your own) what does it say?
I mean - it doesn't say it isn't installed - it says it cannot be loaded.

I've added just the import step infront of the backup-navcontainer. I'll check and let you know.

So I changed code to this...
Invoke-ScriptInNavContainer -containerName $ContainerName -usePwsh:$false -scriptblock  {
Import-Module SqlServer
#Install-PackageProvider -Name NuGet -MinimumVersion '<IP_ADDRESS>' -Force
#Install-Module -Name SqlServer -RequiredVersion 21.1.18256 -Force -AllowClobber
}
Backup-NavContainerDatabases -containerName "$ContainerName"         -bakFolder "$BackupFolder"
-Verbose
But failed like this...
The specified module 'SqlServer' was not loaded because no valid module file was found in any module directory.
Exception Script Stack Trace:
at Invoke-ScriptInBcContainer, C:\Users\buildadmin2\Documents\WindowsPowerShell\Modules\bccontainerhelper\6.0.16\ContainerHandling\Invoke-ScriptInNavContainer.ps1: line 61
at , C:\agent2_work\64\s\DevOps.Builds\ERP AL\Invoke-Master-CreateDevelopmentDB.ps1: line 103
at , : line 1
at , C:\agent2_work_tasks\AzurePowerShell_72a1931b-effb-4d2e-8fd8-f8472a07cb62\4.238.7\azurepowershell.ps1: line 261
at , C:\agent2_work_tasks\AzurePowerShell_72a1931b-effb-4d2e-8fd8-f8472a07cb62\4.238.7\azurepowershell.ps1: line 257
at , : line 1
at , : line 22
at , : line 18
at , : line 1
PowerShell Call Stack:
at Invoke-ScriptInBcContainer, C:\Users\buildadmin2\Documents\WindowsPowerShell\Modules\bccontainerhelper\6.0.16\ContainerHandling\Invoke-ScriptInNavContainer.ps1: line 71
at , C:\agent2_work\64\s\DevOps.Builds\ERP AL\Invoke-Master-CreateDevelopmentDB.ps1: line 103
at , : line 1
at , C:\agent2_work_tasks\AzurePowerShell_72a1931b-effb-4d2e-8fd8-f8472a07cb62\4.238.7\azurepowershell.ps1: line 261
at , C:\agent2_work_tasks\AzurePowerShell_72a1931b-effb-4d2e-8fd8-f8472a07cb62\4.238.7\azurepowershell.ps1: line 257
at , : line 1
at , : line 22
at , : line 18
at , : line 1
Container Free Physical Memory: 46.8Gb

When you use -usepwsh:$false - SqlServer module is NOT available and pscoreoverrides should never be included.
When running PS5 - SQLPS is included as always.
Are you including pscoreoverrides overrides yourself?

code looks like this:

I guess found the issue. Part of the upgrade process I'm performing this step:
    Write-Verbose "Restore app database from bacpac $BacpacPath"
    $StringBlock = @'
    param ($BacpacFile,
    $DatabaseName
    )
    Restore-BacpacWithRetry -bacpac $BacpacFile `
    -databasename $DatabaseName `
    -maxattempts 1

'@
$ScriptBlock = [Scriptblock]::Create($StringBlock)
Invoke-ScriptInNAVContainer -containerName $ContainerName -Scriptblock $ScriptBlock -ArgumentList $BacpacFile, $ContainerConfig.DatabaseName -usePwsh:$false
As you can see it has -usePwsh:$false, without this change it will fail with an error.
Could this be the root cause.
The statement Backup-NavDatabase is in a different devops step. Meaning a diffrent session.

Error when not using option UsePwsh
VERBOSE: Restore app database from bacpac
Restoring Database from C:\ProgramData\BcContainerHelper\Extensions\backup\app.bacpac as CRONUS
Exception calling ".ctor" with "1" argument(s): "The type initializer for 'Microsoft.SqlServer.Dac.DacServices' threw an exception."
Exception Script Stack Trace:
at Restore-BacpacWithRetry, C:\run\HelperFunctions.ps1: line 94
PowerShell Call Stack:
at Invoke-ScriptInBcContainer, C:\Program Files\WindowsPowerShell\Modules\BcContainerHelper\6.0.16\ContainerHandling\Invoke-ScriptInNavContainer.ps1: line 71
at Update-cdsaMultiTenantContainer, : line 96
at , : line 6
Container Free Physical Memory: 19.2Gb
Services in container demo:
Exception calling ".ctor" with "1" argument(s): "The type initializer for 'Microsoft.SqlServer.Dac.DacServices' threw an exception."
At C:\Program Files\WindowsPowerShell\Modules\BcContainerHelper\6.0.16\ContainerHandling\Invoke-ScriptInNavContainer.ps1:112 char:13

        throw $errorMessage

        ~~~~~~~~~~~~~~~~~~~

CategoryInfo          : OperationStopped: (Exception calli... an exception.":String) [], RuntimeException
FullyQualifiedErrorId : Exception calling ".ctor" with "1" argument(s): "The type initializer for 'Microsoft.SqlServer.Dac.DacServices' threw an exception."

Any idea from which repo this function is comming?
Restore-BacpacWithRetry it exists in the container.

Restore-BacpacWithRetry is from HelperFunctions inside the generic image (nav-docker repo)
I can see this only works in PS5 - so yes, that code will need -usepwsh $false (no colon - it is not a switch)
You should also use -useSession $false - else it will remove your pwsh session and create a powershell session - which it next time around will do again with a pwsh session.

I added following to the script when restoring the bacpac but it keeps failing at the backup-navcontainer later in the process.
Invoke-ScriptInNAVContainer -containerName $ContainerName -Scriptblock $ScriptBlock -ArgumentList $BacpacFile, $ContainerConfig.DatabaseName -usePwsh $false -useSession $false
I'll try to create a repo scenario for this.

I have a repro on my laptop... Grapping it into script(s) for you and will send it in a presonal mail.

Replied with a workaround on how to modify your code on email

I tested this, but now it fails on step:
Remove-CompanyInBcContainer -containerName $ContainerName -companyName $_
The tenant 'default' is not mounted or does not exist.
Exception Script Stack Trace:
at , : line 2
PowerShell Call Stack:
at Invoke-ScriptInBcContainer, C:\Program Files\WindowsPowerShell\Modules\BcContainerHelper\6.0.16\ContainerHandling\Invoke-ScriptInNavContainer.ps1: line 71
at Get-CompanyInBcContainer, C:\Program Files\WindowsPowerShell\Modules\BcContainerHelper\6.0.16\CompanyHandling\Get-CompanyInNavContainer.ps1: line 22
at , : line 2
Somehow the default tenant doesnt exist anymore after switching to Single tenant.
Also the cmdlet get-Navtenant inside the container is now empty.. This looks like a diff in the platform compared to BC23
I can workaround this I guess using invoke-script instead Remove-NavContainerCompany

Found rootcause the script to convert to single tenant contained a statement:
Dismount-NAVTenant -ServerInstance 'BC' -Tenant 'default' -Force
Before exporting the App.DB and moving it into the tenant DB. Somehow the behavior is different now. In the past it got mounted by defaullt somehow...
I removed the dismounting And now it continues. As we are only using single tenant in DEV environments for this case can be closed. But this might be something from the server team to look into as its changed behavior.

I tested this, but now it fails on step: Remove-CompanyInBcContainer -containerName $ContainerName -companyName $_
The tenant 'default' is not mounted or does not exist.
Exception Script Stack Trace: at , : line 2
PowerShell Call Stack: at Invoke-ScriptInBcContainer, C:\Program Files\WindowsPowerShell\Modules\BcContainerHelper\6.0.16\ContainerHandling\Invoke-ScriptInNavContainer.ps1: line 71 at Get-CompanyInBcContainer, C:\Program Files\WindowsPowerShell\Modules\BcContainerHelper\6.0.16\CompanyHandling\Get-CompanyInNavContainer.ps1: line 22 at , : line 2
Somehow the default tenant doesnt exist anymore after switching to Single tenant. Also the cmdlet get-Navtenant inside the container is now empty.. This looks like a diff in the platform compared to BC23
I can workaround this I guess using invoke-script instead Remove-NavContainerCompany

This is likely because your scriptblock had a switch parameter and then it also read that value from args[0] - that doesn't work - I changed that (as I also saw that problem).

Removing the dismount in my script when transforming to single tenant also solved the problem. Tested on both 23.x and 24x and all is fine. Thx for support again!


chore(main): release 0.0.25

:robot: I have created a release beep boop
0.0.25 (2024-06-12)
Bug Fixes

deps: update kubernetes packages to v0.30.2 (#280) (d262e44)
deps: update module sigs.k8s.io/cluster-api to v1.7.3 (#278) (c5e13f8)

Refactoring

move IsAdmin out from internal package (#281) (84ed6c4)

This PR was generated with Release Please. See documentation.

:robot: Created releases:

v0.0.25
:sunflower:


Empty label pr

When the api returns no results we can add a label to show this to the user. If the user clicks on this label we might want to do something (show an alert with more explanations for example).
This PR adds this functionality by adding two props emptyListLabel and onEmptyListPress.

@bell-steven, Do you have any plans for the implementation of this feature?

@felipemengatto see thisfor more. It probably won't happen until v2.

Thanks for the PR!
Closed with 5756843


Can't turn on setting sync

Type: Bug
Newly installed vscode can not turn on Settings Sync. (No accounts requested yet)
Error while turning on Settings Sync. No authentication providers are available.
VS Code version: Code 1.75.1 (441438abd1ac652551dbe4d408dfcec8a499b8bf, 2023-02-08T21:32:34.589Z)
OS version: Windows_NT x64 10.0.22621
Modes:
Sandboxed: No

System Info

Item
Value

CPUs
AMD Ryzen 9 5900HX with Radeon Graphics         (16 x 3294)

GPU Status
2d_canvas: enabledcanvas_oop_rasterization: disabled_offdirect_rendering_display_compositor: disabled_off_okgpu_compositing: enabledmultiple_raster_threads: enabled_onopengl: enabled_onrasterization: enabledraw_draw: disabled_off_okskia_renderer: enabled_onvideo_decode: enabledvideo_encode: enabledvulkan: disabled_offwebgl: enabledwebgl2: enabledwebgpu: disabled_off

Load (avg)
undefined

Memory (System)
31.86GB (25.05GB free)

Process Argv
--crash-reporter-id f86230a1-001f-4543-b79f-3d0031a7dc6f

Screen Reader
no

VM
0%

Extensions: none
A/B Experiments
vsliv368:30146709
vsreu685:30147344
python383cf:30185419
vspor879:30202332
vspor708:30202333
vspor363:30204092
vstes627:30244334
vslsvsres303:30308271
pythonvspyl392:30443607
vserr242:30382549
pythontb:30283811
vsjup518:30340749
pythonptprofiler:30281270
vsdfh931cf:30280410
vshan820:30294714
vstes263cf:30335440
pythondataviewer:30285071
vscod805:30301674
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
cmake_vspar411:30581797
vsaa593:30376534
pythonvs932:30410667
cppdebug:30492333
vscaac:30438847
vsclangdc:30486549
c4g48928:30535728
dsvsc012:30540252
pynewext54:30660299
azure-dev_surveyone:30548225
pyindex848:30662994
nodejswelcome1:30587005
282f8724:30602487
pyind779cf:30662993
f6dab269:30613381
pythonsymbol12:30657548
vsccsb:30662443

My issue is similar to https://github.com/microsoft/vscode/issues/151434
I googled around, only found this happening on linux distros, so no solution for Windows.

Can you please check if the following extensions are enabled? Go to Extensions view and look for

@builtin github auth
@builtin microsoft account

Nope, it's just installed, very clean. BTW, I found I couldn't even install extensions.

/duplicate
https://github.com/microsoft/vscode/issues/174046
To recover, can you please do following?

F1 > Open Extensions Folder...
Delete extensions.json file

It's working now. Thank you very much! All fixed. But I still wonder the root cause what could be the possible reason that made this happened?

Do not know why you have an empty extensions.json file. May be some extension has created this file.

Here's the thing. I installed vscode on windows. But the firt time I opened it was in WSL. I'm thinking maybe this is related.

Hmm interesting. Are you able to reproduce so that you end up having empty extensions.json file?

Do I just uninstall vscode and install it again, and repeat the steps? Any other files I need to clean before I reproduce?

Delete the extensions folder if you do not have any extensions or if you can install them again.

I deleted the code folder in the AppData\Roaming, deleted .vscode folder in my own user file deleted .vscode-server folder in WSL.
The vscode WSL server download is not triggered, which it should be when I opened the vscode for the first time in WSL.
And yes, it could be reproduced. (I also didn't close the wizard window with the "finish" button when installation was completed. Though I think this doesn't matter, but comment here in in case it does.)

Great. So it reproduces even without connecting to WSL? After installation have you just opened VS Code empty window?

OK, here's the step.

Install vscode on windows without opening it.
Open WSL command line (Ubuntu 22.04 LTS)
Go to a random project, in my case, it's a newly created nestjs project with the nest CLI
run code .

Great. So it reproduces even without connecting to WSL? After installation have you just opened VS Code empty window?

So it's not an empty window. Though I can see the files in the folder tree, but without a WSL server? No it's not connected to WSL.

Great. If you are able to reproduce, can you please share following log when this happens

F1 > Open View... > Window
F1 > Open View... > Shared

Yesterday I already fix it again. So I had to uninstall it again. However I couldn't reproduce it this time.

@drafting-dreams Thanks for sharing lot of information. I filed a separate issue - https://github.com/microsoft/vscode/issues/174695 - that creates an empty extensions.json file.


[TF2] Not catching 'quit' or '_restart"

I've noticed today that the script doesn't seem to be catching the 'quit' or '_restart' commands.
This is a big issue as I have all my server restart at 2AM to prevent performance hitches.
If you run any of those commands, the server just shuts down and the tmux session ends.
Any help would be appreciated.
Thanks,
Ryan.

Do you mean ./tf2server restart does not work ?

You're trying to restart from the tmux session aka console ?
Maybe some read would help https://github.com/dgibbs64/linuxgsm/wiki/Start-Stop-Restart-commands

@UltimateByte Yeah. From within the console.
The script used to catch when this happened and restarted the server, Doesn't seem to be doing it anymore.

It happens if for some reason there is already a typed text in your console.

So can we consider this as solved ?

No.
The script isn't catching the restart command. This has happened every time.
Also, it is a script related issue.
When you type 'quit' in console, the script is supposed to keep the tmux session open then restart the server. It's the crash protection. If the server crashes, it won't come back up.
I have a SourceMod plugin that executes _restart in console, but the srcds instance within tmux isn't restarted, it quits. If it were working properly, the console wouldn't close and the server would say "Server restarting in 10 seconds".
That's the issue.

I run 8 gameservers on one Linux box, but under different users. (tf2server thru 8)
tf2server (1) does this correctly:
https://gyazo.com/06c7975c19445fb012d6572774eb9f67
Instead of this happening, it exits on all but no.1. Could there be an issue with servers running under different users?

The quit command depends upon the server. Some servers quit means shutdown and others its means restart. Should quit mean shutdown the tmux session normally closes as it kills the process. However if quit means restart the process is kept alive and the tmux session is not closed.
Quit meaning restart is a bit of a pain imo as when the server is stopped LGSM sends the quit command to to a graceful shutdown. However the server instead just starts itself back up (Insurgency is an example) meaning stop will take over 30 seconds.
Servers running under different users are separate and should have no bearing on each other.
The issue does not sound like a problem with LGSM to me but rather the server or plugins you are using.
If you have setup LGSM to monitor the server even if the server was killed it will be back online within a few mins.
I hope this explanation helps you a little

Yeah, from your last screenshot, the server IS catching the quit command, but the game server just happens to restart instead for some reason. Garry's Mod did the same at one point, it wasn't a plugin issue, it was gmod itself, so we had to complain about it on their github in order for them to correct it. But some addons might cause that too.
If you wanna restart and you're in a hurry, you can also force close the server before using the restart command. For that, you can kill the pid, but finding it is kinda boring, so I usually run ./gameserver console, then press ctrl + c. to terminate the process Then ./gameserver restart.

That's unusual. The TF2 servers running on that box are all direct clones of eachother.
I also have 2 other seperate dedicated servers with 8 servers on, and the first server (tf2server) on those boxes acts the same way as the above screenshot and the others exit.
This is becoming more strange every time I think about it.

We've deployed the monitor system through a cron job for every 5 mins. (Not sure why I didn't do this a while back)
All my servers go down for updates automatically (plugin detects a Steam update and restarts the server)
I guess the monitor will bring them back up if they don't on their own.
Still doesn't explain the issue.

"All my servers go down for updates automatically (plugin detects a Steam update and restarts the server)"
What if this update plugin fucks things up ? Why are you even using a plugin for that if you can run LGSM's update checker as a cronjob ? :p
https://github.com/dgibbs64/linuxgsm/wiki/Update

Well, closing as isolated issue and no feedback.


7.4.0

Release details
Checklist
Before merge

[ ] Wiki updated with info in ticket listed under Documentation
[x] ran npm run prepare-release (which runs npm audit fix, npm run lint-ts, npm run lint:fix, git add, git commit)
[x] pushed potential changes made by prepare-release

After merge

[ ] merged all dependabot PRs that target main branch
[x] updated bug template to include the new version
[x] updated .mcdevrc for tests to the new version
[x] ran npm run version:major/minor/patch
[x] pushed version-prep commits
[x] merged main branch into develop branch
[x] closed GitHub milestone
[ ] created new GitHub Release

Documentation

#1434 / #1630

https://github.com/Accenture/sfmc-devtools/pull/1642#issuecomment-2353796176

#1651

TODO

#1643

TODO

#1645

TODO

#1666

TODO

#1671

TODO

Issues

closes #1472
closes #1505
closes #1646
closes #1643
closes #1645
closes #1651
closes #1644
closes #1657
closes #1666
closes #1668
closes #1671
closes #1434

https://github.com/Accenture/sfmc-devtools/wiki/06.b-~-Standard-Commands/_edit

#1434

Documentation
execute
Command: mcdev execute <business unit> [type] [key] [--like] [--schedule] [--metadata]
Alias: mcdev exec / mcdev start / mcdev resume
[...]
publish
Command: mcdev publish <business unit> [metadata type] [metadata key] [--like] [--skipStatusCheck] [--metadata]
Alias: mcdev activate

https://github.com/Accenture/sfmc-devtools/wiki/06.b-~-Standard-Commands/_edit

#1651

Documentation
Currently supported types:

Name
CLI Argument

Asset
asset

Data Extension
dataExtension

Documentation - Advanced Configuration
Config options
.mcdevrc.json
The central config in .mcdevrc.json holds multiple adjustable settings:
{
  "options": {
    "deployment": {
      "commitHistory": 10,
      "sourceTargetMapping": {
        "deployment-source": "deployment-target"
      },
      "targetBranchBuMapping": {
        "release/*": "MySandbox/QA-DE",
        "master": ["MyProduction/PROD-DE", "MyProduction/PROD-NL"]
      }
    },
    "validation": {
      "buildDefinition": {
        "noGuidKeys": "warn",
        "noRootFolder": "warn"
      },
      "deploy": {
        "noGuidKeys": "warn",
        "noRootFolder": "warn"
      }
    },
    "documentType": "md",
    "documentStandardRoles": true,
    "exclude": {
      "role": {
        "CustomerKey": ["excludedRoleKey","excludedOtherRoleKey"]
      }
    },
    "include": {
      "asset": {
        "r__folder_Path": ["Content Builder/only/assets/in/here"]
      },
    },
    "serverTimeOffset": -6
  },
  "directories": {
        "businessUnits": "businessUnits/",
        "deploy": "deploy/",
        "docs": "docs/",
        "retrieve": "retrieve/",
        "template": "template/",
        "templateBuilds": ["retrieve/", "deploy/"]
  },
  "metaDataTypes": {
    "documentOnRetrieve": ["user", "automation", "dataExtension", "role"],
    "retrieve": [...]
  }
}

Setting
Default
Description

options.deployment.commitHistory
10
Configures how many commits createDeltaPkg will display if no parameters are given

options.deployment.sourceTargetMapping
{"deployment-source": "deployment-target"}
Configuration of 1 or many source-target marketList combos for mcdev createDeltaPkg

options.deployment.targetBranchBuMapping
{"release/*": "...","master": ["..."]}
Can be used by CI/CD pipelines to know what BUs shall be deployed to upon a merge into one of the specified branches

options.validation
current default and custom rules
Allows setting validation rules to "off", "warn" or "error

options.documentType
'md'
Defines the format for documentation ('md', 'html', 'both')

options.documentStandardRoles
false
Optionally skip standard role documentation by setting to false

options.exclude.type.field
[]
Allows you to filter out metadata on retrieve based on their field values, e.g. CustomerKey (previously options.filter)

options.include.type.field
[]
Allows you to filter out metadata on retrieve based on their field values, e.g. CustomerKey

options.serverTimeOffset
-6
Used to work around quirks in how SFMC handles timezones; For stack4: set to -7 (US Mountain time); others: -6 (US Central)

directories.businessUnits
'businessUnits/'
Directory to save BU base details in

directories.deploy
'deploy/'
Where deploy searches for files to deploy

directories.docs
'docs/'
Directory for document output

directories.retrieve
'retrieve/'
Where retrieve stores downloaded files

directories.template
'template/'
Where rt stores downloaded templates & bd retrieves them from

directories.templateBuilds
['retrieve/','deploy/']
Where bd saves final deployment versions in. This can hold multiple directories, e.g. ['retrieve/','deploy/']

metaDataTypes.documentOnRetrieve
['user', 'automation', 'dataExtension', 'role']
automatically executes document for selected types

metaDataTypes.retrieve
changes with each release
check Metadata Type Support for current list

https://github.com/Accenture/sfmc-devtools/wiki/06.c-~-Templating-Commands
Documentation
Templating Commands
build
Command: mcdev build <--buFrom> <--marketFrom> <--buTo> <--marketTo> <--metadata> [--bulk] [--dependencies] [--retrieve] [--skipValidation]
buildDefinition
Command: mcdev buildDefinition <business unit> [type] [template name] [market] [--metadata] [--market] [--skipValidation]
buildDefinitionBulk
Command: mcdev buildDefinitionBulk <market list name> <type> <template name> [--metadata] [--skipValidation]