Cannot open video stream

PLZ help me!
I have followed INSTALL.md and build dense_flow successfully. But when I use extract_gpu, above error I got. I wonder there are 2 reasons for this error:

I set BUILD_opencv_hdf=OFF when build OpenCV-4.0.1, because it will get error opencv_test_hdf. I'm not sure what it use for, so I close it.
My ffmpeg version is 2.8.15, I can not install ffmpeg4 in my Centos7. But I can transform .avi to .mp4 use ffmpeg-2.8.15 which can indeed open video stream.

Sorry, I know what happened.
When I install ffmepg, I only yum install ffmpeg, without ffmpeg.devel. So during build OpenCV-4.0.1, it cannot find FFmpeg and it's libs(such as avcodec...).
Use yum install ffmpeg-devel.x86_64 and rebuild OpenCV/dense_flow, then it will work normally.


[Documentation] No samples focusing on configuring properties of http annotation and resource level parameters

No samples focusing on configuring properties of http annotation and resource level parameters in https://ballerinalang.org/docs/by-example/

Can you give more information on what exactly is required.

The new BBEs and guides should cover these.


General connection management

This is just a proof of concept PR that tries to make the handling of graceful shutdown work for more than just http scenarios. This should allow us to move TLS further out and should also allow us to start moving things to connection middleware instead of connection adapters.
Summary of the things added:

Added IConnectionHeartbeatTickFeature that represents a per connection heartbeat with DateTimeOffset.UtcNow passed into the callback. This is trying to preserve the performance characteristics Kestrel had before on the HTTP path. Haven't measured anything here as yet.
Added IGracefulConnectionLifetimeFeature that represents an attempt to gracefully close the connection that isn't being aborted. This feels pretty awful but we may have to do it.
Moved connection management to the ConnectionDispatcher and out of the HttpConnectionMiddleware

PS: I haven't even run all tests locally so I expect explosions all over.

Opening a new PR


Document how to author NuGet packages that target .NET Core but don't depend on DNX

Authoring libraries that target .NET Core is being covered as part of the .NET docs (see https://github.com/cartermp/core-docs/blob/new-library-manual/docs/libraries/libraries-with-cli.md).


Adds requiresMainQueueSetup declaration

Solves  #43

Examples of this fix in other libraries:
robinpowered/react-native-frequency#7
blackdeve/react-native-wifi#13
itinance/react-native-fs#371


Upstream v5.43.0

This change updates pulumi-aws to the v5.43.0 version of the upstream provider.
See upstream release notes for the detailed list of changes: https://github.com/hashicorp/terraform-provider-aws/releases/tag/v5.43.0

TestEC2Instance upgrade test failure seems artificial. Once we land https://github.com/pulumi/pulumi-aws/pull/3772 it should pass AFAIK.

Thanks Ramon! Much appreciated.

/release minor


Fix streaming downloads using request

We recently realised that downloads were failing on the latest version. This PR attempts to fix the failures and also ensure the change that caused the issue (enabling support for download behind a proxy) continue to work.
@DanCunnington kindly tested this works behind a proxy.
Fixes #159

Merging, since this broke the install from github via npm install we can close the issue once we've done:
npm install github:RuntimeTools/appmetrics
just to confirm. (It has been tested on another clone already.)


Padding between view controllers

Hi,
how can I give padding (horizontal) between view controllers?

Hi @uzman! This is currently not possible, but I've been thinking about adding support for it. I can't really provide an ETA at the moment.


Php8 support

[x] Moved from Travis CI to Github Actions
[x] Added support for PHP 8.0 (which launches today)

In order to support PHP 8, we have to upgrade PHPUnit to v9. Tis is the only version supporting PHP 8.0. I had to refactor the tests a bit because of incompatibilities and deprecations.
This also means we have to require php ^7.3.
It would be great to see this package support PHP 8!
Also, no green checkmark shown here but you can see the tests passed on my fork: https://github.com/Nielsvanpach/iso3166/commits/php8-support

Thanks a lot for your time and work; I will try to make some time tonight myself to take a closer look.

Looking forward to this.

@pimjansen I did not make any style changes myself. These were done by the php-cs fixer action, which uses the config file .php_cs.dist that was already present in this repo. I assume the command was not run in a while.


getService doesn't filter unhealthy services

Currently it seems that the ConsulHttpClient.getService method uses the Catalog https://www.consul.io/api/catalog.html#list-nodes-for-service to get all the endpoints for a service; but if a certain endpoint is considered unhealthy (for example since the consul agent is in failed mode due to network partition the client doesn't excluded it from the available nodes.
Maybe it's better to use the Health https://www.consul.io/api/health.html#list-nodes-for-service for this?

FYI, we have added support ourselfs in the fork here:
https://github.com/crobox/reactive-consul/commit/d0e041dc113bbfb0d3553ae5b75e934afac9ebfa
thanks to @ecyshor


v.9.3.0 - Bootstrap 5 / Bootstrap Icons

ToDo: Refactor Accordions to https://getbootstrap.com/docs/5.0/components/accordion/


Kernel high-resolution timer support

Several users in the mailing list have asked for highly precise busy-wait primitives that allow them to time with precision.
I don't know what sort of APIs we'd need, but at the very least something like:
k_hr_busy_wait(u64_t microseconds)

@anangl @tbursztyka FYI

In addition to a high-resolution timer API, I imagine users that have the high-frequency clock always-on anyway would like to be able to Kconfigure "_arch_k_cycle_get_32" to use the high-frequency clock instead of the low-frequency clock.

Why only a microseconds resolution?

@diytronic

Why only a microseconds resolution?

Agreed, I checked the Linux HR timer API and it uses nanoseconds.

May be use same approach as system clock - using timer ticks?

Well, there is also k_busy_wait(u32_t microseconds) now already in the kernel

Yeah, on systems with a high precision cycle counter, k_busy_wait() does what you want already.  It just spins on k_cycle_get_32() as described.  On essentially all the current platforms, k_cycle_get_32() is provided out of the timer driver as _timer_cycle_get_32().
Pretty sure you have what you want already, no?

@andyross yeah, I think so. Unless we really need nanosecond precision, but on current microcontrollers this make little sense actually, since the overhead in instructions would already clobber the added resolution.
@diytronic would that cover your needs, if k_busy_wait() was actually precise on Nordic platforms?

@carlescufi For current task yes, but I am implementing 1-wire bus now (need it for ds18b20 sensor, so really writing driver for it too) and among the standard mode 1-wire has so called overdrive mode (faster).  So on my opinion nanosecond resolution could be way better.

@carlescufi For current task yes, but I am implementing 1-wire bus now (need it for ds18b20 sensor, so really writing driver for it too) and among the standard mode 1-wire has so called overdrive mode (faster).  So on my opinion nanosecond resolution could be way better.

@carlescufi BTW just checked for example CAN BUS timings https://www.nxp.com/docs/en/application-note/AN1798.pdf So nanosecond delays there. So I think nanosecond delay must be implemented.

So... two issues: one is that k_busy_wait() only allows a microsecond argument, where the actual cycle counter it wraps can (usually) do better.  I don't see any reason we can't have a k_nano_wait() or whatever that takes different units.
But a request for true nanosecond precision just isn't going to work on CPUs running clocks 10-100x slower than that.  We can't fix that.

honestly an app with precision requirements like this could trivially write its own loop over k_cycle_get_32().

No - it does not work. For example for nRF1x MCU family system tick used 32kHz timer which is unable to provide even microseconds resolution. Really this was the only reason for k_busy_wait API call implementation discussion.

@andyross

But a request for true nanosecond precision just isn't going to work on CPUs running clocks 10-100x slower than that. We can't fix that.

nRF1x MCU has separate 16Mhz timer which can be used for this. So I expect some other MCU can have something similar. Mean some built in mechanisms not related to system clock.

@diytronic: k_cycle_get_32() returns a hardware cycle counter, not scheduler ticks (except on platforms that have no such timer, I guess).  I'm all but certain this would work just fine on nRF1x.  Are you sure you actually have a problem with the API as it stands (which has some precision aliasing due to microsecond conversion, but otherwise should be close to cycle accurate)?

@andyross I am absolutely sure, because I tried to get a delay based on this http://docs.zephyrproject.org/kernel/timing/clocks.html#measuring-time-with-high-precision and finally got got that k_cycle_get_32() working with 32kHz frequencey what was a big surprize (tested on nRF51822 MCY). So I discovered code and found what 32kHz timer used for that (nRF51822 has second timer working in 16Mhz). So I asked in mailing list about it and gor reply

The reason for such a low-resolution system clock is power consumption. Running on the 32KHz clock is much more power efficient than requiring the 16MHz clock continuously

And later this

The CPU itself still works at 16MHz even when the 16MHz external crystal is not enabled, this does not impact actual processing power performance. The idea is that the 16MHz external crystal is only required under certain conditions (Bluetooth Low Energy radio intervals for example) but can be kept off the rest of the time.

But anyway  checking k_cycle_get_32()  (pin output with logic analyser) I see 32kHz frequency of k_cycle_get_32(). So to get smaller delay I am separately turning on and using 16Mhz timer.

I need a 1us timestamp "service". In my use-case it is simply a variable that increments every 1 us infinitely, and that gets read asynchronously as per need.
-be always monotonic at a 1us resolution
-Take care of any rollovers (64bit variable would take care of this almost at any micro-controller clock)
-If it uses interrupts, it does it right to avoid race condition
Neglecting any os issues, would not this be easy to do in the nrf devices by using a 32b-wide timer clocked at a 1MHz and a compare register to detect rollovers. The timer
would generate an interrupt every hour or so to indicate a rollover event.
Thanks
Abderrezak

Saw this came up again on the mailing list. As diytronic explains above: NRF51 devices have power consumption requirements that mean that the system clock will simply never be able to produce timing information of this precision in a way that Zephyr can expose as a straightforward API.  If the clock has to be kHZ-scale at idle, there's just no way to get the main timer (i.e. k_cycle_get_32(), and its derivatives like k_busy_wait()) to give you answers in microseconds.  You have to use some other device, and manage it outside the system timer framework.
I don't think that would be a bad API to have available, but it's much more complicated than "high-resolution timer support", which we already have.

Copying @pizi-nordic since this was raised in the API meeting today by him.

Setting the priority high due to popular demand for this feature

Would be useful to have this for a nanosleep(2) call. I have not looked into Zephyr's clock structure yet though. It would be nice to collect multiple clock sources and make them available to applications / userspace similar to the clock_getres, clock_gettime, etc.

(Doing a grooming pass on bugs/issues that are sitting around with my name on or near them.  No one pays me right now so I get to be an unaccountable whirlwind of chaos!)
Think this one can be closed, as there's nothing in the discussion here that isn't well captured by @cfriedt in #40099.  Broadly the big missing piece is just a sub-microsecond busy wait.  Timer (i.e. interrupt-driven) subsystem rates are arbitrarily precise already (subject to unit overflow) and have been proven out down to a 20us tick granularity on existing platforms.  And even for busy waiting, we have only a handful of platforms (bigcore x86 and the intel_adsp devices, maybe ARM64?) which have software-accessible counters much below 1us anyway.


reenable additional openjdk tests for openj9/ibm

There are some openjdk test targets that are excluded from the playlist due to failures. These test targets may contain lots of subtests. They are valuable for catching defects early in the development stage. We should try to enable them if possible.
run.txt contains additional openjdk tests that CR runs. If we are not running them in our pipeline at the moment, we should consider reenabling these tests for openj9/ibm.
For tracking purposes, we will update the box doc for detail.
cc @pshipton @JasonFengJ9 for awareness.

The tests are added. This issue is completed.


Export ResponsiveArray types

Fixes #250
I'm not sure this is correct, but in case you think the issue is valid and exporting is an ok solution, here's the fix.

Have you tried this fix in the context of your app? Happy to merge it if it fixes your issue, I just don't have a reproduction locally to confirm.

Have you tried this fix in the context of your app? Happy to merge it if it fixes your issue, I just don't have a reproduction locally to confirm.

Yeah, I edited the compiled d.ts file directly in node_modules and this removed the error.

Thanks for the PR! 🙏


Merge master branch to prTesting1_201903141012 branch

OPS Build status updates of commit 8fb1e33:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details
Dependent Files

split/updateTestRef1.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Passing arguments in Automator

The idea here is to to apply a rule to a folder of choice by right-clicking the folder (or selecting the files and right-clicking) and choosing the organize action (which would include a specific --config-file=<>).
So the question is how to pass the specified folder or files arguments onto organize? Is there a way we can specify this in the config file? This would prove really useful to organize certain folders on the spot.
Thanks in advance!

That's an interesting use-case! I haven't worked with Automator much so far but it should be possible to define environment variables? If this is the case then you should be already able to use environment variables as folders:
rules:
  - folders: $MY_FOLDER
    actions:
      - echo: "{path}"

And call it with MY_FOLDER="~/Desktop" organize sim

Thanks, @tfeldmann! I have been trying this approach with automator but I'm failing to pass the arguments to organize. Probably a minor coding issue. Will let you all know when I manage to make it work as it would be very useful :)

Any updates on this?

Hi there! And thanks for asking.
Unfortunately, I haven't managed to make it work (even after last upgrade).
As I mentioned above, the idea is to create an Automator shell script that then I can call from any folder with a mouse click or key shortcut. The Automator shell script receives current "files or folders" and passes input "as arguments".
It contains the following:
export PATH=/usr/local/bin:$PATH
MY_FOLDER="$@"
organize --config-file=/path/to/config.yaml run

The YAML config file defines folder as this:
- folders: $MY_FOLDER`

However, when I call this from a folder, nothing happens (it is supposed to sort file types into subfolders).

Got it working!

Automator shell script:
export PATH=/usr/local/bin:~/.local/bin:$PATH
MY_FOLDER="$@"
organize run ~/Dropbox/Apps/organize/finder-action.yml --working-dir="$MY_FOLDER" > $MY_FOLDER/organize.txt

This uses the new working-dir argument. In your config you then use . as location, no need for env variables:
rules:
  - locations: "."
    filters:
      - name: "test-trash-this-file"
    actions:
      - trash

In the organized folder you will find a organize.txt for debugging. You can disable this in the shell script.
The automator action:
organize this folder.zip

Hey! Just wanted to drop a quick note to say thanks for your response to this issue. It's been a busy time on my front but finally got around to trying your solution, and it worked like a charm!


Playcanvas API Download App - Error Parsing playcanvas-stable-min.js

I am using this guide to download my app. However, when I try to serve it using http-server, I am receiving this error:
Uncaught SyntaxError: Unexpected token ')' (at playcanvas-stable.min.js:1:2)
When I download the app from the playcanvas editor, the playcanvas-stable.min.js file is different than when I download it from the API. Is there anything I'm overlooking or does this need to be fixed?

Hi, can you check what the version and revision numbers are at the top of the two playcanvas-stable.min.js files?

Could you attach the API engine version here?


Adding 10 pair calculation

Adding a 10 pair calcultaion to the existing 11 pair calculation to improve the results eventually.
This may be a trick to get informations about possible pairs erlier then with the 11 pair method
This is not guaranteed and has to be checked

done with latest dev commit


Update Debugging docs to no longer recommend Remote debugging

Summary:
As a follow-up of https://github.com/facebook/react-native/pull/36754, which removes the remote debugging option from the dev menu, this PR updates the Debugging documentation, deprecating Remote debugging and recommending the usage of Direct debugging with Safari as an alternative.
This also adds a quick section about Flipper as it currently is the hard-coded way of debugging when pressing Open Debugger

sidenote: this should not be merged until the PR referenced in merged and ported to 0.72 (if it will).


[wip] build python sdists along with wheel

Description
For #4892, this explores what the CI infrastructure would do if there just happened to be an sdist built at the same time as the wheel. From a cursory look at the workflows and scripts, the dist folder seems to be handed around, rather than the .whl itself, so it's possible everything will "just work" up to deployment to pypi, even if it's not being further tested as an artifact.
Checklist

[ ] I have updated tests where applicable.
[ ] I have added an entry to the CHANGELOG.

I'm closing this as it's marked WIP and CI is failing, please feel free to open a new PR anytime! :)

Sdist builds still seem like something someone with a good understanding of the build machinery could add in a few well-placed lines, and would be very helpful to downstreams, though perhaps I'm not the right one to do so.
So, sure, closing is fine, I've been able to solve my immediate proxy needs with something simpler (but more inflexible), and probably won't pick this back up unless the situation changes drastically.


Properly support decoding NRC-CONST parameters

if a negative response contains an NRC-CONST parameter, where the parameter's value is not in the list of expected values, the response is not applicable and decoding should be stopped at this point. (Thus, NRC-CONST parameters are a multiplexer mechanism which filters responses based on the value of some other parameter.)
This patch implements this by introducing a new DecodeMismatch exception which is raised whenever a NRC-CONST parameter which exhibits an unexpected value is encountered. The higher-level routines for decoding responses then ignore these exceptions when appropriate. IMO, this solution is a bit sub-optimal because it uses exceptions for flow control in normal operation, but alternative implementations would be far more complex.
Andreas Lauser<EMAIL_ADDRESS>on behalf of MBition GmbH.
Provider Information

@kayoub5: do you consider this to be merge-ready with the latest modifications?

@kayoub5: barring objections or approvals, I will merge this PR this Thursday or Friday...


After so many requests, the timeout limit is always reached

*** READ BEFORE POSTING ***
Before posting an issue - please upgrade to the latest version and confirm the issue/bug is still there.
Upgrade using:
$ pip install yfinance --upgrade --no-cache-dir
Bug still there? Delete this content and submit your bug report here...
I am running analysis each day on 8-10 stocks over a 365 day period, and after about 90 days of analysis the ticker.history function is continually reaching the timeout limit of 5 seconds, and returns nothing. Is this an issue with the scraper, or some sort of Yahoo internal limit?

My understanding is this is Yahoo rate-limiting API access. So you have to rate-limit your own data requests, implement some form of caching.
... which is why I'm working on a caching wrapper for yf, because everyone has this issue. Smart caching that only contacts Yahoo if enough time has passed for new data, and then only requests the new data and integrates it into cache. Not simply caching http requests.
Not quite ready yet but close, so feel free to follow me.

Hi @ValueRaider, I'm searching a cache solution too on YF. Did you release yours ?

Hi @ValueRaider, I'm searching a cache solution too on YF. Did you release yours ?

It's almost ready. Just fixing some type issues (date vs datetime vs pd.Timestamp)

Hi @ValueRaider, I'm searching a cache solution too on YF. Did you release yours ?
It's almost ready. Just fixing some type issues (date vs datetime vs pd.Timestamp)

Awesome, excited to try your new versions. Sure, I'll clone your branch and give you some feedback.


Can't find tsserver executable

I use asdf for installing nodejs

https://github.com/pmizio/typescript-tools.nvim/pull/53

@kuator if I understand correctly pr you mentioned fix your issue?

@kuator if I understand correctly pr you mentioned fix your issue?

Yes

Or is merged to master. Closing


Service port cannot be set correctly

Summary
Service port cannot be config correctly
Kong Ingress controller version
1.0
Kong or Kong Enterprise version
2.1
Kubernetes version
Client Version: version.Info{Major:"1", Minor:"19", GitVersion:"v1.19.0", GitCommit:"e19964183377d0ec2052d1f1fa930c4d7575bd50", GitTreeState:"clean", BuildDate:"2020-08-26T14:30:33Z", GoVersion:"go1.15", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"19", GitVersion:"v1.19.1", GitCommit:"206bcadf021e76c27513500ca24182692aabd17e", GitTreeState:"clean", BuildDate:"2020-09-09T11:18:22Z", GoVersion:"go1.15", Compiler:"gc", Platform:"linux/amd64"}
Environment

Cloud provider or hardware configuration:
OS: CentOS Linux release 7.8.2003 (Core)
Kernel : Linux kube-control-plane 3.10.0-1127.13.1.el7.x86_64 #1 SMP Tue Jun 23 15:46:38 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
Install tools: use https://raw.githubusercontent.com/Kong/kubernetes-ingress-controller/master/deploy/single/all-in-one-dbless.yaml file to deploy
Others:

What happened
service.port seems incorrect in logs.(via kubectl logs), but request is proxied correctly.
...
"service": {
		"host": "joke-service.kong.443.svc",
		"created_at":<PHONE_NUMBER>,
		"connect_timeout": 60000,
		"id": "b95c526b-b533-59f3-97c8-c73d93088877",
		"protocol": "https",
		"name": "kong.joke-service.443",
		"read_timeout": 60000,
		"port": 80,
		"path": "\/",
		"updated_at":<PHONE_NUMBER>,
		"write_timeout": 60000,
		"retries": 5,
		"ws_id": "0dc6f45b-8f8d-40d2-a504-473544ee190b"
	}
...

Expected behavior
service.port would be 443.
Steps To Reproduce

create a kongingress

apiVersion: configuration.konghq.com/v1
kind: KongIngress
metadata:
  name: common-kong-ingress
  namespace: kong
proxy:
  path: /
  protocol: https
route:
  strip_path: false
  preserve_host: false
  methods:
    - POST
    - GET
    - PUT
    - PATCH
    - DELETE
    - OPTIONS
    - HEAD

create a service which type is  ExternalName

apiVersion: v1
kind: Service
metadata:
  name: joke-service
  namespace: kong
  annotations:
    konghq.com/override: common-kong-ingress
    configuration.konghq.com: common-kong-ingress
spec:
  ports:
    - protocol: TCP
      port: 443
      targetPort: 443
  type: ExternalName
  externalName: <IP_ADDRESS>

create a ingress

apiVersion: extensions/v1beta1
kind: Ingress
metadata:
  name: express-start-ingress
  namespace: kong
  annotations:
    konghq.com/override: common-kong-ingress
    kubernetes.io/ingress.class: kong
spec:
  rules:
    - host: lb.learn.com1
      http:
        paths:
          - path: /getJoke
            backend:
              serviceName: joke-service
              servicePort: 443

create a global plugin(file-log)

apiVersion: configuration.konghq.com/v1
kind: KongClusterPlugin
metadata:
  name: file-log-plugin
  namespace: kong
  annotations:
    kubernetes.io/ingress.class: kong
  labels:
    global: "true"
config:
  path: /dev/stdout
plugin: file-log

make a request

Then I found the this in log
...
	"tries": [{
		"balancer_latency": 0,
		"port": 443,
		"balancer_start":<PHONE_NUMBER>466,
		"ip": "<IP_ADDRESS>"
	}]
...

After that, I find that there is not override s.port in this file ~/kubernetes-ingress-controller/internal/ingress/controller/parser/service.go
...
// overrideByKongIngress sets Service fields by KongIngress
func (s *Service) overrideByKongIngress(kongIngress *configurationv1.KongIngress) {
	if kongIngress == nil || kongIngress.Proxy == nil {
		return
	}
	p := kongIngress.Proxy
	if p.Protocol != nil {
		s.Protocol = kong.String(*p.Protocol)
	}
	if p.Path != nil {
		s.Path = kong.String(*p.Path)
	}
	if p.Retries != nil {
		s.Retries = kong.Int(*p.Retries)
	}
	if p.ConnectTimeout != nil {
		s.ConnectTimeout = kong.Int(*p.ConnectTimeout)
	}
	if p.ReadTimeout != nil {
		s.ReadTimeout = kong.Int(*p.ReadTimeout)
	}
	if p.WriteTimeout != nil {
		s.WriteTimeout = kong.Int(*p.WriteTimeout)
	}
}
...

Is this a bug?
Or, my configuration is incorrect?

This is known and is harmless. The port that is actually being used is defined in Target.
Do you have any problem proxying requests via Kong when this configuration is present?

@hbagdi ，thanks!
I am not meeting other problems in my use case.


chore(flexbox): add as prop to cutomize component render

General summary

FlexBox: add as prop to customize the root element component render.
GenericBlock: add as prop to customize the root, the figure, the content and actions elements component render.

Test OK
No regression on FlexBox & GenericBlock stories :heavy_check_mark:
FlexBox & GenericBlock can now have a custom react component injected :heavy_check_mark:


Need clarification on transfer date

"For the enrollment transfer effective date, it can be a date on or after the start date of the target enrollment but no earlier than the first day of the month in which the request is made. The chosen date can't affect usage for any overage invoice already issued."
What does bolded text mean? I'm confused.

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

ID: b012da28-41db-78d8-53ac-6322ca21d55b
Version Independent ID: 62425030-1886-4ae1-2bed-273488a38f7b
Content: Transfer Azure Enterprise enrollment accounts and subscriptions - Microsoft Cost Management
Content Source: articles/cost-management-billing/manage/ea-transfers.md
Service: cost-management-billing
Sub-service: enterprise
GitHub Login: @bandersmsft
Microsoft Alias: banders

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

@liutang Thanks for your question.
Assigning to content author @bandersmsft   for review.

@liutang I'm working with the team to clarify, as you requested. I'll reply here where I have more details to share.

@liutang I've updated the article for clarity as you requested.
To answer your question directly:
The effective transfer date is the date that you want to transfer the old source enrollment to the new one. The date can be backdated to the first date of the current month, but not before it. For example, if today’s date is January 25, 2023 the enrollment transfer can be backdated to January 1, 2023 but not before it.
#please-close

https://github.com/MicrosoftDocs/azure-docs-pr/pull/225039


Fixed prompt_rust_version to avoid grep aliases

Fixes #803

Thanks for the review; I silenced the missing rustc error and tried to fix the test

Hah. 🤦♂ In our test we mock rustc. In the new code we avoid any wrapper scripts and call command rustc. So we need to find a good way to mock rustc anyways..

Just for the record: This PR is related to #632


add variable module support to web_app definition

This patch allows a web_app user to specify the modules loaded with the application instead of forcing the hardcoded list. Supports mod_ and mod_modname references, as well as wrapper-cookbook::module_name.

I think we should just remove the modules all together. The only reason they are included is because the default template references directives provided by those modules.
I think the default template should be revisited and made significantly more minimal and rely on individuals to provide a template for the more complex cases.
thoughts?

I always thought that would be good, but there seems to be an awful lot of resistance to making the default template LESS configurable...


Email autolink shouldn't be started by HTML tags

Fixes #565

The regex looks a bit huge, but it isn't very complex (the majority is defining character classes), so I don't think it'll be any (much?) worse than the existing regex complexity (open to performance suggestions though, cc: @PhrozenByte)
I think filter_var's email filter doesn't match the definition that CommonMark references (CommonMark uses the HTML5 definition), but I'm not sure of the exact discrepancies.

The regex was taken from CommonMark, right?

Yup, (though they ripped it straight out the HTML5 spec ;p). The only changes I made were escaping a backslash and a made the "username" part of the email possessive (since that character class is mutually exclusive with @ I don't think we need backtracking?).

Alright. Yeah, no backtracking necessary there.


lagrange: 1.15.7 -> 1.15.8

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for lagrange is: A Beautiful Gemini Client
meta.homepage for lagrange is: https://gmi.skyjake.fi/lagrange/
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 1.15.8 with grep in /nix/store/a540ah35x7myrn6s5li5f9dg1s6ksqlr-lagrange-1.15.8
found 1.15.8 in filename of file in /nix/store/a540ah35x7myrn6s5li5f9dg1s6ksqlr-lagrange-1.15.8

Rebuild report (if merged into master) (click to expand)

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath
lagrange
lagrange-tui

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/a540ah35x7myrn6s5li5f9dg1s6ksqlr-lagrange-1.15.8 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A lagrange https://github.com/r-ryantm/nixpkgs/archive/0c3482b405a0db5ec65fa432d29c2170a0836484.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/a540ah35x7myrn6s5li5f9dg1s6ksqlr-lagrange-1.15.8
ls -la /nix/store/a540ah35x7myrn6s5li5f9dg1s6ksqlr-lagrange-1.15.8/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

2 packages built:

lagrange
lagrange-tui

Maintainer pings
cc @sikmir for testing.

Result of nixpkgs-review pr 225223 run on x86_64-darwin 1

2 packages built:

lagrange
lagrange-tui


Sphinx Configuration for Multi server application

My website using 5 application servers and have a separate sphinx server which ip I have given in thinking_sphinx.yml
Issue is that when I create or update any record it give an error from application servers.  As it wants to run delta index but i have not rebuild sphinx on application servers so no bin and delta files.
I want that delta index also happens on sphinx server so application servers will perform better.
Is that possible or not? If not then what’s the benefit of keeping sphinx server as a standalone server.

Hi Haseeb
When you've got multiple application servers and you want up-to-date indices, there are two options:

Use deltas via a background job worker (such as Sidekiq or DelayedJob), and use the corresponding TS gems ts-sidekiq-delta or ts-delayed-delta. Make sure the background job worker is on the same machine as Sphinx, so it processes the deltas there.
Or, switch to real-time indices rather than SQL-backed indices - which means that changes to your data are communicated to Sphinx using its SphinxQL protocol (instead of needing access to the same file system) via ActiveRecord callbacks.

If real-time indices work for your situation, then that's what I would recommend, as it's better-supported by Sphinx (whereas delta indices fail if you're using Sphinx 3.x and PostgreSQL as your database). But if you stick with Sphinx 2.2.11, then either solution should work well enough.

Hi @pat
Thank you for your reply :)
I have two confusion regarding using background job . I am using sidekiq background job and updated my indices files like
ThinkingSphinx::Index.define(:users,
  :with  => :active_record,
  :delta => ThinkingSphinx::Deltas::SidekiqDelta
) do

end

After how much time background job will run?
How can I make sure that this background job will run on sphinx server as changes are happening on app server and as per thinking sphinx documentation Therefore when the job for the delta index runs, it will only run on the app server that actually processes the job.  . Is it possible that we run background job only on sphinx server even changes happens on app servers.

Thank you again :)

You'll need to have Sidekiq (and so, a copy of your app) running on your Sphinx server - and that Sidekiq process should be processing jobs from the ts_delta queue. That Sphinx/Sidekiq server needs to be talking to the same Redis database as your app servers - that way, they'll add the Sidekiq delta jobs to that database, and the Sphinx Sidekiq worker will pick those jobs and process them.
Sidekiq is pretty fast at picking up jobs - so it shouldn't be that much slower than the classic delta style, but it depends on how many jobs are enqueued.

Great thank you :)
I have done this but how can I stop delta indexing on app servers? My thinking sphinx config is
production:   address: x.x.x.x   mysql41: 9412   mem_limit: 512M   bin_path : "/algaraj/software/sphinx/bin/"   charset_table: "0..9, a..z, _, A..Z->a..z, U+621..U+63a, U+640..U+64a, U+66e..U+66f, U+671..U+6d3, U+6d5, U+6e5..U+6e6, U+6ee..U+6ef, U+6fa..U+6fc, U+6ff"   searchd_log_file: "log/searchd_production.log"   query_log_file: "log/searchd_production.query.log"   pid_file: "/algaraj/software/app/shared/tmp/pids/searchd.production.pid"   indices_location: "/algaraj/software/app/shared/tmp/sphinx/production/"   configuration_file: "/algaraj/software/app/shared/tmp/production.sphinx.conf"
When I do any record change on app server...sphinx delta starts perform on that server ... as I have sidekiq and redis setup on app servers also

Is each app server using their own Redis instance? Or are they using a shared Redis instance? Because it'll need to be shared, and then you'll need to make sure that only the Sidekiq instance on the Sphinx server processes the ts_delta queue.
You can run other Sidekiq instances on your app servers if you want, they just can't be allowed to run jobs in the ts_delta queue.

Its a shared Redis server
I have done exactly mentioned in this gem https://github.com/pat/ts-sidekiq-delta
How can I make sure that only the Sidekiq instance on the Sphinx server processes the ts_delta queue?
As I gave sphinx server IP address in thinking_sphinx.yml and set indices like this
`ThinkingSphinx::Index.define(:users,
:with  => :active_record,
:delta => ThinkingSphinx::Deltas::SidekiqDelta
) do
end`
It should work or I need to write and sidekiq worker also or any other change?

Your Index definition is looking fine - it's the Sidekiq configuration you'll need to check:
https://github.com/mperham/sidekiq/wiki/Advanced-Options#queues
So, if you're configuring Sidekiq via command-line arguments, use -q ts_delta on your Sphinx server, and -q default or whatever other queues you're using on your app servers. Or if it's via configuration files, that's fine too, just make sure that your app server Sidekiq configuration file doesn't include ts_delta in its list of queues, and the Sphinx server file does.

It's been almost two months, so I'm going to close this issue - but, we can reopen it if there's further questions or thoughts, so do get in touch if help's needed :)


Implement functionality to detect that a site integrating the Complianz CMP is GPC-compliant

From what we know, the Complianz consent management platform (CMP) does not have a cookie implementation of GPC. However, as @stanleymarkman observed, we may still be able to detect whether a site that integrates Complianz is compliant with GPC. The reason is the following:
The Complianz plugin always checks whether the GPC header is sent by the visitors browser, and if so, it is automatically assumed that the user wishes to "deny all" preferences and the Cookie Banner is not shown as a result. Thus, the  "cmplz_choice" cookie will have the value "set", but the cookies such as "cmplz_marketing", "cmplz_statistics" will not be created. Section 7.1 in the Cookie Policy that comes with the Complianz integration also changes depending on GPC being enabled/disabled. Thus, by observing these changes, we can indirectly tell whether a site correctly reacts to a GPC signal.
This issue is not the most pressing one. We should definitely tackle first the US Privacy String cookie detection and the OneTrust OptanonConsent detection (#225) before we move to this issue.

One complication for detecting whether the Complianz implementation of a site is reacting to a GPC signal we are sending is that a site's default may be that the "deny all" choice (and the cookie setting related to that choice) is actually the default. If that is the case, we would not be able to detect any change after the GPC signal is sent. So, it may be necessary to first accept all cookies in the first place (via logic in our extension), send the GPC signal, and then detect that the cookie settings have been changed.

Just for info, description of Complianz' cookies on cookiedatabase.org.

Maybe, we pick this up later.


Different dates showing for same article

The date for this article is July 27, 2001 on the article page: http://alistapart.com/article/Process
but August 20, 2005 on her bio page: http://alistapart.com/author/meryl-k-evans

@m1ca: Legacy articles (that belong to an issue) show the date of the issue they belong to on the article page; that specific article is assigned to issue 118, which has a date of  7/27/2001 (http://alistapart.com/issue/118 -  it doesn't have an illustration assigned).
Normally legacy articles should have the issue date assigned to them. So, this article: http://alistapart.com/article/Process, should have a date of 7/27/2001.
That is the case with the legacy articles dating back to issue 231 (dated 1/21/2007, title Paper Prototyping and Quick CSS Mockups with Photoshop). Before that period, legacy articles dates are all wonky (different from the issue date), I assume due to some database migration or change of content strategy.
Correcting the bio page to show the issue date for legacy articles (instead of the article date) would add a lot of unneccessary processing overhead - plus it seems to me that what should be corrected are the legacy article dates; all the more since we ditched issues.
I'll check the database to see how issue and article dates are connected, so we can make the change in the DB in batches.
What do you think? Isn't it better to correct the article dates?

@m1ca @murtaugh @zeldman
I shared a spreadsheet with you containing old issues and corresponding articles and their dates, which highlights the differences between article and issue date.
I wrote a script to update the old article dates to correspond to the issue dates, shall I run it?
Don't we want to change the article date to correspond to the issue date?

@michellekondou @murtaugh @zeldman
Michelle, yes, please update the article dates to match the issue dates. I just did a data sort on the spreadsheet and see lots of heavily-replicated article dates that are totally wrong.

Ok, will do on Monday, I'll be travelling tomorrow

@m1ca @murtaugh
I changed the article dates on DEV, (e.g. http://dev.alistapart.com/author/meryl-k-evans); everything seems to be fine.
I'll change them in production tomorrow morning my time (night time in the US) which is a low traffic hour just to be sure.

@zeldman @m1ca @murtaugh
I have updated the spreadsheet to be easier to scan; Jeffrey you should probably go through those dates, so we're sure before I go updating our Database.

I have not seen a shared spreadsheet. Was it shared via email? Basecamp?

Hi, @m1ca @michellekondou @murtaugh (the 3 M's!)
I've looked at the spreadsheet but am not sure I understand it. Article dates and issue dates should always match. Always. When there is a discrepancy, my guess is that the earlier date is usually correct, i.e. "The Ins and Outs of Intranets" has a 2000 date and a 2005 date. I'm sure the earlier (2000) date is correct.
I cannot account for discrepancies or verify that any of these dates is correct. I can tell you that the issue dates and the article dates should match. That is all I can tell you.
You folks seem to have a much better handle on this than I do. Carry on, I guess?

@m1ca @zeldman @murtaugh
It's done! Article dates have been corrected :)


init_config if config file does not exist

@StephenHynes7 @eflanagan-r7 @cheffernan-r7 @fk92r7
this solves the appdirs dependency on installation and we are not hitting pypi wheels data_files bug anymore: https://bitbucket.org/pypa/wheel/issues/92

LGTM did you update the readme to reflect the last change

+1

@StephenHynes7 nice reminder, will do.

+1


"lib/recorder" has not been loaded yet for context

Error: notloaded: Module name "lib/recorder" has not been loaded yet for context: _. Use require([])

I'm trying to require(['path/to/nock/index'], function(nock) but it gives me the error above. How can I require nock not using the require('nock') syntax?

Same error here...

nock works only on node, using synchronous require.


fix keyboard shortcuts next and previous page on history

Seems keyboard shortcuts wors previous next page but doesn't change the state so needs watch URL change?
https://user-images.githubusercontent.com/5887929/159159558-dab76d32-539f-4bb8-89a0-f7c5fd86e0c0.mov

Hi, I will work on it.


Clicking on the same variant twice causes the variant detail page to not load

Describe the bug
Currently when clicking a small variant to see variant details, closing that view again and clicking the same variant again causes the loading screen to show infinitely.
Opening another variant, the variant before can be opened again.
To Reproduce
Steps to reproduce the behavior:

Click a small variant
Close it
Click the same variant again

Expected behavior
Opening a variant should always work if services are reachable.

@stolpeo Could you look into that? Might cause a lot of false positive VarFish support requests.


feat: limit the number of messages in prepare proposal

This PR limits the number of transactions in prepare proposal.

One extra test case for transactions with multiple messages

c5071a3a3aaa8eea231492f1398123492b195508

https://github.com/celestiaorg/celestia-app/issues/3972


Fix connection broker mode for stat / listings

The "connection broker" mode for an origin allows it to be run from behind a firewall and require no host certificate.
However, recent new features have partially broken the mode.  I spot two issues:

In the new code @haoming29 added to have the director do a HEAD against the origin as part of the origin-selection process.
When the client does a PROPFIND against the director for an object listing, the director will redirect it to the origin (which wouldn't work here).

Suggested fixes:

In broker/client.go, we already have a function that will return a TCP socket connected to the origin based on the origin name and broker address.  Add a new method to the director module that returns a http.Transport object which is aware of the origins that need a connection broker.  Internally, this new object would implement the DialContext method.  Within DialContext, if the requested hostname is that of an origin which needs a connection broker, invoke the connection broker logic to get a new net.Conn from broker.ConnectToOrigin and return that.  Otherwise, perform a "normal" dial to create a TCP socket.
Migrate any place where we invoke GetTransport in the director to the director-specific logic from step (1).
When handling a PROPFIND request, instead of redirecting to the origin, proxy the request to the origin.

This means all clients will go through the director and not contact the origin, allowing the director to reverse the connection.
Additionally, we could implement rate-limits for object listing in the future.  Golang has powerful libraries for rate limiting -- and we know metadata queries are one potential way to overload the object stores behind an origin.  Alternatively, we could just proxy for origins that require connection brokers and otherwise redirect.

Some thoughts on this while I'm working on #1393
If the director decides to proxy the PROPFIND request, it should:

Responds with 207 (per WebDAV standard)
Still includes Pelican-X-Namespace header with collections-url field
This is how I modify the client code to be upward compatible with this change. The client still expects 307 response as another option and it will take the Location header as the collections url in that case.

@bbockelm any words of wisdom before I commit the changes to #1393 ?


Feature/gen commons pkg

GitHub Issue
GitHub issue.
Changes

nx gen the commons library
directory setup: constants, legos, utils, types

Checks
Before making your PR, please check the following:

[x] Critical lint errors are resolved
[x] App runs locally
[x] App builds locally (run the build command for any impacted package and check for any errors before the PR)

This looks good! Once we have some usage instructions we can update the Readme (same with all of our other things in Sage)

Yeah I'll take a stab at that in the next PR that will have actual functionality.
Maybe we need a readme template?


[Task]: Fix account color update

Task description
Account color inside the top navigation doesn't change when updated through the wallet customisation:

Requirements

[ ] Account color in the top navigation is updated when changed by wallet customisation

Acceptance criteria
Can be closed when the requirement is complete.
Creation checklist

[ ] I have assigned this task to the correct people
[X] I have added the most appropriate labels
[X] I have linked the correct milestone and/or project

fyi this also happens in desktop


Current scoring functionality from Scoring branch

Current progress for Scoring.

[Current coverage][cc-pull] is 68.96% (diff: 93.25%)

Merging [#12][cc-pull] into [master][cc-base-branch] will increase coverage by 9.05%

@@             master        #12   diff @@
==========================================
  Files             6         11     +5
  Lines           232        319    +87
  Methods           0          0
  Messages          0          0
  Branches         22         27     +5
==========================================
+ Hits            139        220    +81
- Misses           92         94     +2
- Partials          1          5     +4

Powered by Codecov. Last update [a90193a...4bcee29][cc-compare]
[cc-base-branch]: https://codecov.io/gh/floric/HTWK_Visu/branch/master?src=pr
[cc-compare]: https://codecov.io/gh/floric/HTWK_Visu/compare/a90193a101df422f372d734db6ece6678ab3e231...4bcee297077c9488be23ae5eeae8caeeec401f0b?src=pr
[cc-pull]: https://codecov.io/gh/floric/HTWK_Visu/pull/12?src=pr

ScoringCalculator test isn't perfect code...
I'll wait with it until we test the current code with real data and know if the concept is already enough or not. Then we can improve these tests later.


webhooks: handle nil Response without a panic

Fixes: https://github.com/moov-io/watchman/issues/289

Codecov Report

Merging #290 into master will increase coverage by 0.06%.
The diff coverage is 100.00%.


Region Portability Issue

Trying to get vpc builder running in a different region is not that straight forward. Tried to stand-up in us-west-2 with global: global:
** Replace with overall organizational ID **
Uncomment below  if you'd like to use RAM Sharing
organizationId: o-hjw5j8o5mo
stackNamePrefix: sample-complex
ssmPrefix: /sample-complex/network
region: us-west-2
availabilityZones:
- us-west-2a
- us-west-2b
This leads to error with:
Endpoint vpc-endpoints: Service interface file sample-complex-endpoints-us-west-2.txt not found in the config directory
After creating the interface endpoint file it was looking for based on the us-east-1.txt reference and updating to us-west-2 values I'm still getting endpoint erorrs:
Error: Interface Endpoint named  not found in discovery files
at VpcInterfaceEndpointsStack.lookupPrivateDnsName (/Users/kennschr/IAC/CDK/aws-vpc-builder-cdk/lib/vpc-interface-endpoints-stack.ts:198:13)
at /Users/kennschr/IAC/CDK/aws-vpc-builder-cdk/lib/vpc-interface-endpoints-stack.ts:105:43
at Array.forEach ()
at new VpcInterfaceEndpointsStack (/Users/kennschr/IAC/CDK/aws-vpc-builder-cdk/lib/vpc-interface-endpoints-stack.ts:75:25)
at StackMapper.providerEndpointStacks (/Users/kennschr/IAC/CDK/aws-vpc-builder-cdk/lib/stack-mapper.ts:151:26)
at StackBuilderClass.createEndpointServiceInterfaceStack (/Users/kennschr/IAC/CDK/aws-vpc-builder-cdk/lib/stack-builder.ts:365:37)
at StackBuilderClass.buildEndpointStacks (/Users/kennschr/IAC/CDK/aws-vpc-builder-cdk/lib/stack-builder.ts:334:20)
at StackBuilderClass.build (/Users/kennschr/IAC/CDK/aws-vpc-builder-cdk/lib/stack-builder.ts:128:18)
at processTicksAndRejections (node:internal/process/task_queues:95:5)
at /Users/kennschr/IAC/CDK/aws-vpc-builder-cdk/bin/vpc-builder.ts:15:7

Hey Ken, thanks for kicking the tires!
Can you include the contents of the sample-complex-endpoints-us-west-2.txt file you created?  It looks to me like I've interpreted a blank line as an endpoint given the error you're seeing Error: Interface Endpoint named not found in discovery files.  Does that file have empty lines?
Point taken that multi-region should be easier to implement.  Endpoints are actually a little tricky since coverage is not uniform between regions and AZs.  ie: an endpoint could exist in AZ1, and AZ2, but not AZ3.  The code actually detects that scenario based on discovery files in the discovery/ folder in the project.  That discovery information is populated by code in the /tools folder if you're interested in unpacking that.

sample-complex-endpoints-us-west-2.txt
Attached my config/sample-complex-endpoints-us-west-2.txt
There does not seem to be any empty lines.
I've been exploring all the various folders in the project but this is my first real attempt at using CDK beyond the primer and need to learn Typescript here so slow going at the moment.

Your file has a newline at the end.  That's totally fine but my parsing doesn't handle it well.  I'll add some code to detect and filter it out.  In the meantime you can use this file (which has the newline at the end of the file removed) so you can continue!
sample-complex-endpoints-us-west-2.txt

Created #3 and #4


[BUG] Crc command fails to detect crc vm however oc succeeds

General information

OS: RHEL8
Hypervisor: KVM

CRC version
recent

So this is an interesting situation.
Just reinstalled crc on my RHEL 8 machine.
here's the last output by crc:
[jesaremi@SPE-SAG4HP-43 ~]$ ./crc-linux-1.14.0-amd64/crc start
INFO Checking if oc binary is cached
INFO Checking if podman remote binary is cached
INFO Checking if goodhosts binary is cached
INFO Checking minimum RAM requirements
INFO Checking if running as non-root
INFO Checking if Virtualization is enabled
INFO Checking if KVM is enabled
INFO Checking if libvirt is installed
INFO Checking if user is part of libvirt group
INFO Checking if libvirt daemon is running
INFO Checking if a supported libvirt version is installed
INFO Checking if crc-driver-libvirt is installed
INFO Checking if libvirt 'crc' network is available
INFO Checking if libvirt 'crc' network is active
INFO Checking if NetworkManager is installed
INFO Checking if NetworkManager service is running
INFO Checking if /etc/NetworkManager/conf.d/crc-nm-dnsmasq.conf exists
INFO Checking if /etc/NetworkManager/dnsmasq.d/crc.conf exists
INFO Starting CodeReady Containers VM for OpenShift 4.5.4...
INFO CodeReady Containers VM is running
INFO Stopping network time synchronization in CodeReady Containers VM
INFO Verifying validity of the cluster certificates ...
INFO Check internal and public DNS query ...
INFO Check DNS query from host ...
INFO Starting OpenShift kubelet service
INFO Starting OpenShift cluster ... [waiting 3m]
INFO
INFO To access the cluster, first set up your environment by following 'crc oc-env' instructions
INFO Then you can access it by running 'oc login -u developer -p developer https://api.crc.testing:6443'
INFO To login as an admin, run 'oc login -u kubeadmin -p DhjTx-8gIJC-2h2tK-eksGY https://api.crc.testing:6443'
INFO
INFO You can now run 'crc console' and use these credentials to access the OpenShift web console
Started the OpenShift cluster
WARN The cluster might report a degraded or error state. This is expected since several operators have been disabled to lower the resource usage. For more information, please consult the documentation
[jesaremi@SPE-SAG4HP-43 ~]$ sudo virsh domifaddr crc
[sudo] password for jesaremi:
 Name       MAC address          Protocol     Address
-------------------------------------------------------------------------------
 vnet0      52:fd:fc:07:21:82    ipv4         <IP_ADDRESS>/24

Then in about 2-3 hours later I decided to connect and do a deployment
I went for crc console which failed. Then I ran the following:
[root@SPE-SAG4HP-43 ~]# /home/jesaremi/crc-linux-1.14.0-amd64/crc console
Machine 'crc' does not exist. Use 'crc start' to create it
[root@SPE-SAG4HP-43 ~]# /home/jesaremi/crc-linux-1.14.0-amd64/crc status
Machine 'crc' does not exist. Use 'crc start' to create it

However I can very easily login using oc:
[root@SPE-SAG4HP-43 ~]# /home/jesaremi/.crc/bin/oc/oc login -u kubeadmin -p DhjTx-8gIJC-2h2tK-eksGY https://api.crc.testing:6443
The server uses a certificate signed by an unknown authority.
You can bypass the certificate check, but any data you send to the server could be intercepted by others.
Use insecure connections? (y/n): y

Login successful.

You have access to 58 projects, the list has been suppressed. You can list all projects with 'oc projects'

Using project "default".
Welcome! See 'oc help' to get started.

you might have removed the reference to the VM from the ~/.crc directory as this is the first indication of the Vm exists (or running as a different user, such as root, while started from a regular user). check with sudo virsh list and virsh list

@jeffsaremi does it fix for you or you still have same issue?

I will keep an eye on this and re-open if needed. But for now we can close it.


Add support for GlobalTracer and TracerResolver. Update to opentracin…

…g-java 0.22.0.

@pavolloffay @jpkrohling Could one of you review please?
Purpose of the PR is to enable the agent to either resolve the Tracer itself, or use an existing Tracer previously registered by the application.

I think first, we should update OT version in all used instrumentations.

@pavolloffay No problem - other than that, are there any issues?
Only dependencies that currently have rules are the web-servlet-filter and okhttp integrations.

I think first, we should update OT version in all used instrumentations.

I agree. 0.22.0 isn't 100% compatible from 0.21.0 as I first thought.
The SpanContext and SpanBuilder concepts have now been properly separated in the API.
(e.g. SpanBuilder.baggageItems() no longer exists, see https://github.com/opentracing-contrib/java-spanmanager/pull/13).

@pavolloffay @jpkrohling @sjoerdtalsma Thanks for the reviews. All dependencies now updated to OTJava 0.22.0 compatible versions. Unless any other issues will merge in a couple of hours.


VS Code display issue when using custom title bar, multiple monitors, different text size scaling

Issue Type: Bug
When using VS Code with a custom title bar, and using a primary monitor with a vastly different text/app size scaling setting to a second monitor, VS Code does not display the title bar/status bar correctly and the content within them is cropped.
To reproduce - open VS code on a 4k primary monitor with 350% text scaling (monitor display settings), now maximize the window and it fits correctly.  However, drag the window to a 1080p monitor with 125% scaling and again maximize the window, and note how the title bar/status bar are now being cropped.


JsonSerial: include type params in mixins

From @kevmoo on September 17, 2015 17:25
Copied from original issue: dart-lang/source_gen#62

I think this is fixed...


new macro prepare_result_CString

Signed-off-by: Axel Nennker<EMAIL_ADDRESS>new macro prepare_result_CString to handle the case where libindy returns one CString which is empty in the error case. The macro avoids creating an empty Rust string that is then converted into a CString. Overall fewer code lines.

This PR is superseded by the introduction of boxed_callback_string


75 adjust nbh for ens v2

Reference issue #75
Testing:

[X] Ran tests and they passed OK
[X] Added new tests for the new feature(s)

CLA

[X] If a new developer, signed up to CLA

All tests pass for me. The code looks good. Looking at the data used for the new CLI tests, I believe this has come from the appropriate MOGREPS-UK archive set up for this purpose.
I think the only thing left to do (apart from merge the change) is to copy the slides from the mid-sprint demo file to the end-of-sprint demo file.

I've had a look at the code and think that it looks good too. I have run all the tests and:

Unit test pass

[ x]


Druid doesn't ingest data from Storm Bolt

I'm trying to write a simple Storm Topology with Tranquility. It's working and I can see that the task is submitted and running. However, I can't seem to query any data and it looks like the task is just keep running without closing and the dataSource is not created. I'm not sure how to debug this.
Here's my parsing bolt to just extract the data I want from a tweet
private OutputCollector outputCollector;

    @Override
    public void prepare(Map map, TopologyContext topologyContext, OutputCollector outputCollector) {
        this.outputCollector = outputCollector;
    }

    @Override
    public void execute(Tuple tuple) {
        Status status = (Status) tuple.getValue(0);

        for (URLEntity urlEntity : status.getURLEntities()) {
            HashMap<String, String> json = new HashMap<>();
            json.put("url", urlEntity.getExpandedURL());
            json.put("text", status.getText());
            json.put("_ts", Long.toString(status.getCreatedAt().getTime()));

            this.outputCollector.emit(tuple, new Values(json));
            this.outputCollector.ack(tuple);
        }

    }

    @Override
    public void declareOutputFields(OutputFieldsDeclarer outputFieldsDeclarer) {
        outputFieldsDeclarer.declare(new Fields("event_stream"));
    }

This is my DruidBeamFactory
public class DruidBeamFactory implements BeamFactory {
    @Override
    public Beam makeBeam(Map map, IMetricsContext iMetricsContext) {
        final InputStream configStream = getClass().getClassLoader().getResourceAsStream("twitter_spec_file.json");
        final TranquilityConfig<PropertiesBasedConfig> tranquilityConfig = TranquilityConfig.read(configStream);
        final DataSourceConfig<PropertiesBasedConfig> twitterDataSource = tranquilityConfig.getDataSource("twitter-firehose-web-test");

        return DruidBeams.fromConfig(twitterDataSource).buildBeam();
    }
}

This is my spec_file.
{
  "dataSources": [
    {
      "spec": {
        "dataSchema": {
          "dataSource": "twitter-firehose-web-test",
          "parser": {
            "type": "string",
            "parseSpec": {
              "format": "json",
              "timestampSpec": {
                "column": "_ts",
                "format": "auto"
              },
              "dimensionsSpec": {
                "dimensions": [],
                "dimensionExclusions": [
                  "text"
                ]
              }
            }
          },
          "metricsSpec": [
            {
              "type": "count",
              "name": "count"
            }
          ],
          "granularitySpec": {
            "type": "uniform",
            "segmentGranularity": "DAY",
            "queryGranularity": "none"
          }
        },
        "ioConfig" : {
          "type" : "realtime"
        },
        "properties" : {
          "task.partitions" : "1",
          "task.replicants" : "1"
        },
        "tuningConfig": {
          "type": "realtime",
          "maxRowsInMemory": 500000,
          "intermediatePersistPeriod": "PT10m",
          "windowPeriod": "PT10m",
          "rejectionPolicy": {
            "type": "serverTime"
          }
        }
      }
    }
  ],
  "properties": {
    "zookeeper.connect": "<zookeeper>",
    "druid.discovery.curator.path" : "/druid/discovery",
    "druid.selectors.indexing.serviceName" : "druid/overlord",
  }
}

Here's how I wired the two bolts together.
        builder.setBolt("parsing", new ParsingDruidBolt())
                .shuffleGrouping("twitter");

        builder.setBolt("druid", new BeamBolt<>(new DruidBeamFactory()))
                .fieldsGrouping("parsing", new Fields("event_stream"));

I debugged the topology locally and I can see that the messages going through BeamBolt
After I deployed the topology I can see that the task is submitted.

But I don't see that the dataSource is created.

I forgot to mention. I'm using Druid 0.8.4

@noppanit There is no 0.8.4

Sorry you're right it's 0.8.3

I fixed this issue by putting druid.indexer.task.chathandler.type=announce to the middleManager node.

Hi,
I am also experiencing same problem on 0.9.2 version after adding following property druid.indexer.task.chathandler.type=announce to the middleManager node.
One more thing do i need to run realtime node, is it compulsory for it ?

@kunalgupta22 we don't have realtime node as we go with push ingestion. http://druid.io/docs/latest/ingestion/stream-ingestion.html
If you do pull then you need realtime node.

Where do I have stuck while pushing data into druid?
From Storm to druidbeam i got data and druidbeam send data as well as
indexing task also get started but in druid i cant see an datasource and
data.
On 24 Feb 2017 05:41, "Noppanit Charassinvichai"<EMAIL_ADDRESS>wrote:

@kunalgupta22 https://github.com/kunalgupta22 we don't have realtime
node as we go with push ingestion. http://druid.io/docs/latest/
ingestion/stream-ingestion.html
If you do pull then you need realtime node.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/druid-io/tranquility/issues/165#issuecomment-282163652,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AYVuzQ7Lqe44N7Yd5WqapD5-u4jjH4JNks5rfiAwgaJpZM4ITOwR
.

@kunalgupta22 Are you using tranquility? Here's how I fixed my problem.
I added druid.indexer.task.chathandler.type=announce
I checked the version of tranquility. It needs to compile with the correct version of Druid
I check the connection of zookeeper and look out for the log.
Hope this help. Otherwise, please post your settings or configuration.

No, I am using Storm Trident topology where partitionPersist function of
trident topology try to insert data into druid.
Yes,  Storm-druid use tranquility but that is compatibile with 0.8.2 druid
and I am using 0.9.0, can this cause a problem for me?
But Trident topolgy able to create indexing task but doe snot able to
create datasource and insert data in datasource. As well as indexing
service does not throws any error.
If you want I can share my configuration files with you.
On Fri, Feb 24, 2017 at 9:15 PM, Noppanit Charassinvichai <
<EMAIL_ADDRESS>wrote:

@kunalgupta22 https://github.com/kunalgupta22 Are you using
tranquility? Here's how I fixed my problem.
I added druid.indexer.task.chathandler.type=announce
I checked the version of tranquility. It needs to compile with the correct
version of Druid
I check the connection of zookeeper and look out for the log.
Hope this help. Otherwise, please post your settings or configuration.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/druid-io/tranquility/issues/165#issuecomment-282323855,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AYVuzecQ49bDELbusgwBBBml79Kuim8Gks5rfvsSgaJpZM4ITOwR
.

--
*Thanks *Kunal
+91-9958189589
Senior Software Engineer
Bigfoot Retail Solutions Pvt Ltd.Khasra No. 264, Westend Marg, Saidulajab,
Saket 110030http://www.kartrocket.com http://www.kartrocket.com/

Can you try downgrade to 0.8.1. I think 0.8.2 is built for Druid 0.9.1

Sure will test it and update you.
Thanks
On 25 Feb 2017 00:15, "Noppanit Charassinvichai"<EMAIL_ADDRESS>wrote:

Can you try downgrade to 0.8.1. I think 0.8.2 is built for Druid 0.9.1
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/druid-io/tranquility/issues/165#issuecomment-282371002,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AYVuzRKxepeR-OiEQcTW_LQ9qCpN183Oks5rfyVWgaJpZM4ITOwR
.

Hi,
I tested the same with 0.9.2 druid version and 0.8.2 version of
tranquillity but the same thing happened, It able to create indexing task
but no datasource and data.
Please help me out.
On Sat, Feb 25, 2017 at 12:18 AM, Kunal Gupta<EMAIL_ADDRESS>wrote:

Sure will test it and update you.
Thanks
On 25 Feb 2017 00:15, "Noppanit Charassinvichai"<EMAIL_ADDRESS>wrote:

Can you try downgrade to 0.8.1. I think 0.8.2 is built for Druid 0.9.1
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/druid-io/tranquility/issues/165#issuecomment-282371002,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AYVuzRKxepeR-OiEQcTW_LQ9qCpN183Oks5rfyVWgaJpZM4ITOwR
.

--
*Thanks *Kunal
+91-9958189589
Senior Software Engineer
Bigfoot Retail Solutions Pvt Ltd.Khasra No. 264, Westend Marg, Saidulajab,
Saket 110030http://www.kartrocket.com http://www.kartrocket.com/

One more thing I have noticed is after initializing task in druid it never
ends after stopping storm topology.
On Sat, Feb 25, 2017 at 10:31 PM, Kunal Gupta<EMAIL_ADDRESS>wrote:

Hi,
I tested the same with 0.9.2 druid version and 0.8.2 version of
tranquillity but the same thing happened, It able to create indexing task
but no datasource and data.
Please help me out.
On Sat, Feb 25, 2017 at 12:18 AM, Kunal Gupta<EMAIL_ADDRESS>wrote:

Sure will test it and update you.
Thanks
On 25 Feb 2017 00:15, "Noppanit Charassinvichai" <
<EMAIL_ADDRESS>wrote:

Can you try downgrade to 0.8.1. I think 0.8.2 is built for Druid 0.9.1
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/druid-io/tranquility/issues/165#issuecomment-282371002,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AYVuzRKxepeR-OiEQcTW_LQ9qCpN183Oks5rfyVWgaJpZM4ITOwR
.

--
*Thanks *Kunal
+91-9958189589
Senior Software Engineer
Bigfoot Retail Solutions Pvt Ltd.Khasra No. 264, Westend Marg,
Saidulajab, Saket 110030http://www.kartrocket.com
http://www.kartrocket.com/

--
*Thanks *Kunal
+91-9958189589
Senior Software Engineer
Bigfoot Retail Solutions Pvt Ltd.Khasra No. 264, Westend Marg, Saidulajab,
Saket 110030http://www.kartrocket.com http://www.kartrocket.com/

Hi,
Thanks for helping me, problem got solved.
Problem was related to timestamp, i was using localdatetime instead of
datetime of Joda library.
On 25 Feb 2017 22:33, "Kunal Gupta"<EMAIL_ADDRESS>wrote:

One more thing I have noticed is after initializing task in druid it never
ends after stopping storm topology.
On Sat, Feb 25, 2017 at 10:31 PM, Kunal Gupta<EMAIL_ADDRESS>wrote:

Hi,
I tested the same with 0.9.2 druid version and 0.8.2 version of
tranquillity but the same thing happened, It able to create indexing task
but no datasource and data.
Please help me out.
On Sat, Feb 25, 2017 at 12:18 AM, Kunal Gupta<EMAIL_ADDRESS>
wrote:

Sure will test it and update you.
Thanks
On 25 Feb 2017 00:15, "Noppanit Charassinvichai" <
<EMAIL_ADDRESS>wrote:

Can you try downgrade to 0.8.1. I think 0.8.2 is built for Druid 0.9.1
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/druid-io/tranquility/issues/165#issuecomment-282371002,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AYVuzRKxepeR-OiEQcTW_LQ9qCpN183Oks5rfyVWgaJpZM4ITOwR
.

--
*Thanks *Kunal
+91-9958189589
Senior Software Engineer
Bigfoot Retail Solutions Pvt Ltd.Khasra No. 264, Westend Marg,
Saidulajab, Saket 110030http://www.kartrocket.com
http://www.kartrocket.com/

--
*Thanks *Kunal
+91-9958189589
Senior Software Engineer
Bigfoot Retail Solutions Pvt Ltd.Khasra No. 264, Westend Marg,
Saidulajab, Saket 110030http://www.kartrocket.com
http://www.kartrocket.com/

Glad you solved the problem
On Sun, Feb 26, 2017 at 01:25 KunalKartRocket<EMAIL_ADDRESS>wrote:

Hi,
Thanks for helping me, problem got solved.
Problem was related to timestamp, i was using localdatetime instead of
datetime of Joda library.
On 25 Feb 2017 22:33, "Kunal Gupta"<EMAIL_ADDRESS>wrote:

One more thing I have noticed is after initializing task in druid it
never
ends after stopping storm topology.
On Sat, Feb 25, 2017 at 10:31 PM, Kunal Gupta <
<EMAIL_ADDRESS>wrote:

Hi,
I tested the same with 0.9.2 druid version and 0.8.2 version of
tranquillity but the same thing happened, It able to create indexing
task
but no datasource and data.
Please help me out.
On Sat, Feb 25, 2017 at 12:18 AM, Kunal Gupta <
<EMAIL_ADDRESS>
wrote:

Sure will test it and update you.
Thanks
On 25 Feb 2017 00:15, "Noppanit Charassinvichai" <
<EMAIL_ADDRESS>wrote:

Can you try downgrade to 0.8.1. I think 0.8.2 is built for Druid 0.9.1
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<
https://github.com/druid-io/tranquility/issues/165#issuecomment-282371002
,
or mute the thread
<
https://github.com/notifications/unsubscribe-auth/AYVuzRKxepeR-OiEQcTW_LQ9qCpN183Oks5rfyVWgaJpZM4ITOwR

.

--
*Thanks *Kunal
+91-9958189589
Senior Software Engineer
Bigfoot Retail Solutions Pvt Ltd.Khasra No. 264, Westend Marg,
Saidulajab, Saket 110030http://www.kartrocket.com
http://www.kartrocket.com/

--
*Thanks *Kunal
+91-9958189589
Senior Software Engineer
Bigfoot Retail Solutions Pvt Ltd.Khasra No. 264, Westend Marg,
Saidulajab, Saket 110030http://www.kartrocket.com
http://www.kartrocket.com/

—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/druid-io/tranquility/issues/165#issuecomment-282536264,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAm9qzKfMj8dxfa-BtpOokDRBuDkc4_dks5rgRrLgaJpZM4ITOwR
.


There is no logout button in application

Add a logout button to the profile section. We can incorporate the logout button to resemble the one displayed in the screenshot.

please assign me this issue under GSOC

I want to work on this issue. Please assign this to me.

I have done this already please assign me. I am left with pull request only. waiting for gsoc label.

I want to work on this issue. Please assign me

I want to work on this issue. Please assign this issue to me. Also add GSSoc24 level in the label.

I would like to create a log out button for the given app description #gssoc2024

Log out button seems missing , got to fix it for you . please assign it to me

@maniyaom Thank you for raising this issue but we don't want to add logout feature.


 Because we depend on the technology so heavily, we should also include an overview of things to consider, as well as best practices when using one.

Client side load balancing through proxy mode
Related: https://github.com/cockroachdb/cockroach/issues/24001

See also multi-threading in HAProxy to scale with client load: https://github.com/cockroachlabs/support/issues/263#event-2395588824

https://www.cockroachlabs.com/docs/v21.2/recommended-production-settings.html#load-balancing


no such module "perfectlib"

main_http.swift while using XCode 7.2
Just needs the build settings modified slightly
PerfectLib -> Build Settings -> Packaging -> Defines Module
It currently defaults to No causing the error.

I don't see the problem myself. It builds and runs fine with Xcode 7.2. I will make this change though.

Downloading the project, opening an example (e.g. Authenticator) and building Authenticator Server, I'm experiencing the same problem. Xcode 7.2 and Xcode 7.3 beta.


Blurview cannot contain any child view on Android

use this Library to have a vertical swipe on a sample App I have made. it's working very fine on an iOS device but I got an error while running on Android Device. please look at the screenshot

That's a limitation written down here : https://github.com/react-native-community/react-native-blur#android

The Android library introduces some limitations:
BlurView cannot be a child of the view that is being blurred (this would cause an infinite loop)
BlurView cannot contain any child components.

Hi,
This PR is gonna take care of it :
https://github.com/react-native-community/react-native-blur/pull/358 no more need for viewRef on Android AND BlurView can have children now.

Same here. Why on Earth does the "working example for both iOS and Android" has child inside the blur view then?

updated to 3.6.0 still having same issue.

updated to 3.6.0 still having same issue.


Update build-bundle.yml

https://github.com/papeloto project has moved to https://github.com/vimtor/action-zip

nice! thank you!


Bump color-name to 1.1.4

This PR also expands the version range to allow patch releases so there doesn't have to be a new release of color-convert every time color-name makes a release.

Thank you :) And yes, glad they did that.


Scrubbed VIs - Main, Slots, Utility VIs

[x ] This contribution adheres to CONTRIBUTING.md.

What does this Pull Request accomplish?
General scrubbing of VIs, including window positioning/sizing, panel/diagram layout, label consistency, VI documentation, etc.
All changes are cosmetic in nature, with the exception of the following, none of which change the function of the VI:

Convert CDO Module to Slot Configuration.vi -- replace digital "2" with subVI terminal's ring control equivalent value
Convert Channel Settings to CDO.vi -- replaced Case Selector used to convert a boolean T/F to 1/0 with a Boolean to (0,1) node
Convert Channel Settings to Digital.vi -- replaced Case Selector used to convert a boolean T/F to 1/0 with a Boolean to (0,1) node
Convert PWM Module to Slot Configuration.vi -- replace digital "3" with subVI terminal's ring control equivalent value
Validate Reference by Name.vi -- updated incorrect error code selection

Why should this Pull Request be merged?
Cleans up VIs
What testing has been done?
Ran scripting unit tests

LVCompare is showing many VIs (and more) as not having actual changes, but I noticed for some that there were wiring changes not picked up by the diff. I'm fine submitting them as is
I diffed every VI locally and confirmed there were no unreasonable changes (but didn't look to see if any additional work was required).

LVCompare is showing many VIs (and more) as not having actual changes, but I noticed for some that there were wiring changes not picked up by the diff. I'm fine submitting them as is
I diffed every VI locally and confirmed there were no unreasonable changes (but didn't look to see if any additional work was required).


Split up modules

This is a little overdue I think, and it'll cause problems for the other PRs, but it also makes it much easier to maintain.
I've made a few controversial changes in the last three commits. The rest are pretty straightforward.

Hopefully this wouldn't cause too many conflicts with existing PRs? e.g. https://github.com/rustformers/llama-rs/pull/125 comes to mind

Yeah, I'm a little concerned about that one myself, but I don't think it should be too bad - it'll mostly just be discarding the changes to loader.rs here. The others shouldn't be too hard to accommodate.


ExceptionLayoutRenderer - Support layout for Separator

Changed Separator-property from string to Layout, but added bonus-logic so the property still supports standard string-escape-logic. So it might be confusing for users that these Seperator-properties behaves a little differently from other Layout-properties.
It would ofcourse be nice if one could have both string-escape-logic and Layout-logic together. But because NLog FileTarget was the first real target with its FileName-option as Layout, then the Layout parsing was highly optimized for parsing Windows-File-Paths where single-slash does not mean "escape". But actually it is ONLY when Layout is used for File-Paths that this rules makes sense. I guess with NLog 6.0 then the FilePathLayout should become public and should be used for all filepath-related-properties.

But also very tempted to allow string-properties to capture the ending } after having eaten ${. Mostly because I have thought for a long time that one could have a string-property with a Layout-backing-field. And this idea works great when doing unit-test and assigning the string-value directly. But it fails hard when the config-parser assigns the partially parsed string-value.

@304NotModified Any chance of a code-review of this pull-request? (It is pretty much like your own #4539, but with full layout support).

Sorry, super busy. Will try tomorrow!

FileName-option as Layout, then the Layout parsing was highly optimized for parsing Windows-File-Paths where single-slash does not mean "escape". But actually it is ONLY when Layout is used for File-Paths that this rules makes sense. I guess with NLog 6.0 then the FilePathLayout should become public and should be used for all filepath-related-properties.

It's not only filepaths, but also newlines for layout renders?
Anyway, makes sense to split them

So it might be confusing for users that these Seperator-properties behaves a little differently from other Layout-properties.

I'm doubting because of this. Maybe another way is to create another Layout type, e.g. CompatibeLayout. Or a new StringLayout.
Please let me know what you think.

Maybe another way is to create another Layout type, e.g. CompatibeLayout. Or a new StringLayout.

Yes also considered introducing UnicodeLayout or StringLayout. But still I like that the property-type is Layout so any layout can be used, so it would only be the "backing-field" that would be different.
The only reason for introducing something like UnicodeLayout or StringLayout would be to make it easier for 3rd parties to have official Layout-properties that supports correct string-escape-handling (As they also can use it as "backing-field"). But usually 3rd parties just have a string-property, and then just have a normal Layout as "backing-field". This works as intended for 3rd-party NLog Target-options and NLog Layout-options, but just not NLog LayoutRenderer-options.
Again it is close to impossible to make something consistent here, because of the decisions made for FileTarget-FileName-property. And these seperator-properties are a very isolated part of NLog.
I see 2 directions:

Keep seperators as string-properties that magically are able to handle Layout, because Layout is used as "backing-field".
Change seperators as Layout-properties, but then they will behave differently than other Layout-properties. But at the same time it will be visible that layout-logic is possible.

I guess for consistency then I think that option 1) is the way to go, so seperator-options remains string-properties but have Layout-backing-field (To signal that they are different from normal Layout-properties that are currently intended for FilePath)

The only reason for introducing something like UnicodeLayout or StringLayout would be to make it easier for 3rd parties to have official Layout-properties that supports correct string-escape-handling

Not sure if we are on the same page, but ideally I would propose:

create a new type LayoutWithEscapes (better name would be great) that has the current Layout behaviour
change the current Layout that I won't do the special escapes and that is compatible with a string
change the FileTarget.FileName property (and maybe others) to LayoutWithEscapes

OK, this a breaking changes, but it's easy to change in your config (replace //n to /n etc)

create a new type LayoutWithEscapes (better name would be great) that has the current Layout behaviour

Think you have confused the logic (or confused me). Layout is currently by default WITHOUT string-escape, because it has to support FilePaths.
Any change to the NLog Layout logic would be a huge breaking change, so not interested in going down that road.
The goal for me is to find the least ugly solution for making ExceptionLayoutRenderer-Seperator-property to accept ${newline} as input. But while still supporting \n and \t.

Replaced by #4583


test: update SAC tests to support Auth & Single function invocation

What ?
test: update SAC tests to support Auth & Single function invocation
Epic
https://github.com/stellar/soroban-tools/issues/657
Pre-req

https://github.com/stellar/go/issues/4895

finished test updates for p10 contracts, https://github.com/stellar/go/pull/4951


Allow a max of one service in .dockstore.yml

Is your feature request related to a problem? Please describe.
The .dockstore.yml supports both multiple workflows and multiple services. I think we need to only allow a max of one service.
The difference is that for services .dockstore.yml has information that can only be gleaned by client from reading the .dockstore.yml, e.g., datasets, possibly a port, etc. A platform that is going to run a Dockstore service will need to fetch and read the .dockstore.yml in order to, for example, determine which port to proxy.
If the .dockstore.yml contains an array of services, the client would not be able to tell which service in the .dockstore.yml applies to the current service.
Describe the solution you'd like
.dockstore.yml should allow 0-1 services.
Describe alternatives you've considered
Dockstore could capture the metadata in the .dockstore.yml and store that with the service. Using the port as an example, Dockstore could store the port with the service, and the client could query the api for the port. Similar to how, for example, a workflow stores the primaryDescriptorPath.
This might be the better approach, but:

Ideally we want platforms to fetch services via the TRS API, and TRS does not have a way to surface the port. This would require changes to the TRS specification.
The schema is still evolving; port may not even end up being there, or maybe it will be an array instead of a single port, etc. Other fields might get added. It might be better not to lock in.

Writing this up, maybe we should at least capture the additional info in the schema, even if we don't yet surface it.
May need a storytime.
Additional context
If we decide to do this, it would be good to get into 1.9; otherwise we have a model with a list of services that if anybody takes advantage of, we won't be able to migrate.
┆Issue is synchronized with this Jira Story
┆Issue Type: Story
┆Fix Versions: Dockstore 1.9
┆Sprint: Sprint 36 Krill
┆Issue Number: DOCK-1358

What would be the strategy be if someone does ask for multiple services in one repo ala workflows?
Or do we just put our hammer down?

We either put down the hammer, or we pursue the alternative, to capture the extra metadata. It's hard to know because we don't have any actual services, so I could be totally wrong, but I'm guessing the reasons for creating many workflows from one repo may not apply to services.

Having doubts about this solution, recap with options:
Problem
Platforms launching a service defined in Dockstore will need metadata from the .dockstore.yml, which they have to get by fetching the .dockstore.yml via TRS. If the .dockstore.yml has an array of services, how will they determine which service in the array is the one?
Possible Solutions

They look at the name field and see if it matches that section of the TRS id. Or if it's not set, they look for the non-existence of the portion of the TRS id. Puts a bit of work on the platform, but they're going to have to read the file anyway.
We expose the metadata in the .dockstore.yml through the API. I feel this would be the optimal solution, but 1) the schema is still evolving and 2) it will take a while to work this into TRS. Point 1 could be solved by making the API generic enough, e.g., having a Map of key-value pairs or something like that, but that will require thought, and maybe TRS doesn't want to go down that route.
We only allow one service instead of an array. There will be no confusion. One-repo-many-workflows is a popular model; this would not allow one-repo-many-services. Since there are no real services, who knows if people will want to do that? We could always reintroduce the array in a future version of the schema.

Conclusion
Still lean towards third option, but not wild about it.

I'm ok with option 3. Services are new and I think it is better to restrict now and add later. The service dockstore.yml serves an additional function vs the workflow dockstore.yml. Instead of just being for indexing on Dockstore it is also for running. Due to this, I think I am ok with limiting to one per file (and therefore one per repository).

I'm ok with 1 and 3, I think its not quite ready for 2/TRS

Doesn't sound so bad and would be a future proof schema. The platform could do an initial implementation where they select the "first" service and that would probably be a 95% solution for quite a while.


Follow mode setting

Hello, I'm trying to control go1 robot with ROS.
I read the provided manual's explanation, but I still have a question.
Is there any way to start and stop human following mode without mobile APP?
How are the commands for tag traking mode transmitted from the Go1 app to the robot?
Thanks

Can I control robot dog's posture when robot dos is follow mode?

Hello,first of all, the following mode of the robot dog must be started and stopped through the mobile phone APP, and secondly, the command of the Label tracking mode is transmitted from the APP to the robot dog through mqtt.

How does the app receive the MQTT signal?
What is the IP address and port number?

Thanks,
Can you provide
"/home/pi/Unitree/autostart/utrack/catkin_utrack/src/utrack/a2_ukd/src/uwb_t
riple_udp_node.cpp"
this file to me?
2023년 8월 14일 (월) 오후 3:25, xyq1223 @.***>님이 작성:

Hello,first of all, the following mode of the robot dog must be started
and stopped through the mobile phone APP, and secondly, the command of the
Label tracking mode is transmitted from the APP to the robot dog through
mqtt.
—
Reply to this email directly, view it on GitHub
https://github.com/unitreerobotics/unitree_legged_sdk/issues/110#issuecomment-1676748034,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BBVM46USM5WQOWMKCBU2DB3XVHAD7ANCNFSM6AAAAAA3H5OCSQ
.
You are receiving this because you modified the open/close state.Message
ID: @.***>

Hello, sorry we do not currently provide uwb files


Maintain the Website Guide

In #172 I removed content that still referenced the old website's markdown and YAML (hopefully I didn't delete anything that was still relevant?) We also have the Content Structure Guide!
https://github.com/CodingTrain/thecodingtrain.com/blob/main/content/pages/guides/content-structure-guide.md
Should this be a separate guide that is referenced by the maintenance guide? I think maybe it makes more sense to merge these two and bring all the useful info from the Content Structure Guide into the maintenance guide?
@klinegareth I know you might not see this for a while but feel free to weigh in with any thoughts!
@fdoflorenzano if you are able to do a quick scan over the content structure guide and note anything that you've recently updated or changed that might be helpful!

@shiffman I'll give it a look today, hopefully I'll have an update between today and tomorrow. If I see any relevant stuff to add to the Maintain the Website Guide, should I go ahead? (I'll be working on another branch of course)

@shiffman I'll give it a look today, hopefully I'll have an update between today and tomorrow. If I see any relevant stuff to add to the Maintain the Website Guide, should I go ahead? (I'll be working on another branch of course)

Yes please, any and all contributions / edits / updates to the guides are welcome! They are very much just "starter docs" and in progress now!

@shiffman I think the site maintenance guide is more or less a beginner-friendly version of the content structure guide, or at least that's how I've been thinking about it. It might be good to link to the content structure guide in the maintenance guide as a more detailed breakdown of how the site works for those interested!

Thanks for the work on the site maintenance guide! We can open new issues as needed!


Wrong example

Example:
setspn -A BCSERVER/BC130.corp:7046 corp\bcdomainuser
Should be:
setspn -A BC130/BCSERVER.corp:7046 corp\bcdomainuser
And further down it says:
select Microsoft Dynamics NAV 2017 Web client. Should be changed to Business Central.

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

ID: d9871474-165d-c6bf-93f8-e11ea14c6596
Version Independent ID: a881c98f-927d-f458-7e42-e9380404da6f
Content: Configure Web Client Delegation - Business Central
Content Source: dev-itpro/deployment/configure-delegation-web-server.md
Service: dynamics365-business-central
GitHub Login: @jswymer
Microsoft Alias: solsen

Thanks for the feedback! The issues have been fixed and an update will be published soon.


tests/includes: change wait_for_dad() to wait for real address(es)

This can avoid early exit if the interface was down for example.
Signed-off-by: Simon Deziel<EMAIL_ADDRESS>

BTW, the busybox requirement is also why we don't just add the IPs with nodad in the first place, rather than having to wait for it to succeed.

Ah, busybox doesn't have any of that, sorry for the noise and thanks for the explanations!


Temporary fix for 100 video in a playlist limit

Temporary solution added. Should work until a dedicated solution is found. Because I am not too good with requests, my version is slow, but should do for now if someone really needs to extract video data from long playlists >100 videos, which was a problem before. I assume that a playlist can only contain videos from one channel. I think this is the case for public once.

I also base on latest release of 2.5.1 so some changes on master branch were rolledback

im assuming #64 fixes your issue


chore(main): release 0.1.4

:robot: I have created a release beep boop
0.1.4 (2022-05-30)
Miscellaneous

npm: remove npmignore (0b4662f)
publish: revert publish script, move to release ci job (a6288d3)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/smarlhens/npm-check-engines/releases/tag/v0.1.4 :sunflower:


SuspiciousMessageMode: Don't report 0

Closes #197

[ ] I have updated CHANGELOG.md
[x] I have added tests to demonstrate the contribution is correctly implemented
[x] No test failures were reported when running yarn test-all
[x] I did not do unrelated and/or undiscussed refactorings

Let's just ignore these at the moment.

We will also need the changelog entry for these changes.