ocamlPackages.trace: 0.5 -> 0.8

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/c-cube/ocaml-trace/releases.
meta.description for ocamlPackages.trace is: Common interface for tracing/instrumentation libraries in OCaml
meta.homepage for ocamlPackages.trace is: https://c-cube.github.io/ocaml-trace/
Updates performed

Version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 0.7 with grep in /nix/store/w1y19j88m1rp9jb9xsfzbliiyra06p9w-ocaml5.1.1-trace-0.7
found 0.7 in filename of file in /nix/store/w1y19j88m1rp9jb9xsfzbliiyra06p9w-ocaml5.1.1-trace-0.7

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

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
ligo

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/w1y19j88m1rp9jb9xsfzbliiyra06p9w-ocaml5.1.1-trace-0.7 \
  --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 ocamlPackages.trace https://github.com/r-ryantm/nixpkgs/archive/4731d772b2b2ab358e0e9ff93261d03b564b9b78.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/4731d772b2b2ab358e0e9ff93261d03b564b9b78#ocamlPackages.trace

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/w1y19j88m1rp9jb9xsfzbliiyra06p9w-ocaml5.1.1-trace-0.7
ls -la /nix/store/w1y19j88m1rp9jb9xsfzbliiyra06p9w-ocaml5.1.1-trace-0.7/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 --extra-nixpkgs-config '{ allowInsecurePredicate = x: true; }' run on x86_64-linux 1

1 package failed to build:

ocamlPackages.trace-tef

4 packages built:

ligo
ocamlPackages.linol
ocamlPackages.linol-lwt
ocamlPackages.trace

Maintainer pings
cc @vbgl for testing.

Breaks ocamlPackages.trace-tef.

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/c-cube/ocaml-trace/releases.
meta.description for ocamlPackages.trace is: Common interface for tracing/instrumentation libraries in OCaml
meta.homepage for ocamlPackages.trace is: https://c-cube.github.io/ocaml-trace/
Updates performed

Version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 0.8 with grep in /nix/store/39qljl38gs4dfcvikc1inswr4g4953kx-ocaml5.1.1-trace-0.8
found 0.8 in filename of file in /nix/store/39qljl38gs4dfcvikc1inswr4g4953kx-ocaml5.1.1-trace-0.8

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

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath

ligo

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/39qljl38gs4dfcvikc1inswr4g4953kx-ocaml5.1.1-trace-0.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 ocamlPackages.trace https://github.com/r-ryantm/nixpkgs/archive/439035125e6d82b077cba9b1ef0badfd6830c7e9.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/439035125e6d82b077cba9b1ef0badfd6830c7e9#ocamlPackages.trace

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/39qljl38gs4dfcvikc1inswr4g4953kx-ocaml5.1.1-trace-0.8
ls -la /nix/store/39qljl38gs4dfcvikc1inswr4g4953kx-ocaml5.1.1-trace-0.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

1 package failed to build:

ocamlPackages.trace-tef

4 packages built:

ligo
ocamlPackages.linol
ocamlPackages.linol-lwt
ocamlPackages.trace

Maintainer pings
cc @vbgl for testing.

[!TIP]
As a maintainer, if your package is located under pkgs/by-name/*, you can comment @NixOS/nixpkgs-merge-bot merge to automatically merge this update using the nixpkgs-merge-bot.

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


Ignore data sync errors and allow custom should_capture via Delegator pattern

In order to prevent thousands of transient errors being reported to Sentry during the data sync window (errors that occur only because databases are copied/provisioned overnight and are sometimes unavailable), we want to configure the should_capture logic in govuk_app_config in the same way as Content Publisher and Email Alert API, so that the fix is applied centrally. This involves setting the should_capture behaviour to ignore any errors of type PG::Error, if we are in the data sync window (10pm to 8am, according to Puppet).
However, we want to allow downstream apps to be able to define their own should_capture conditions too. Therefore, this PR:

Changes the object apps interact with when they call GovukError.configure - it now yields to a RavenDelegator, which uses the Delegator pattern as suggested by @kevindew. The pattern delegates methods to the Raven.configuration object unless they've been explicitly overridden.
^ this enables us to define our own default should_capture=(callback), inside DefaultConfiguration - but also allows downstream apps to provide their own should_capture=(callback) callbacks too. In our implementation, both the default callback and the custom callback must return true for the overall should_capture callback to return true.
The default should_capture callback examines the error type and determines whether or not we are in the data sync window to decide if the error should be captured. It does this by looking at a global GOVUK_DATA_SYNC_PERIOD ENV variable of the form 22:00-08:00. PG::Error errors that occur during this time frame will be ignored.
The ENV variable doesn't exist yet: I will raise a separate PR in govuk-puppet for that.

Trello: https://trello.com/c/rAlvGlSp/2123-5-ignore-data-sync-errors-in-govukappconfig
Fixes #152. Supersedes #159 (the code has been largely recreated by hand here, as the commit history was meandering and no longer particularly valuable).

Thanks again for the review, @kevindew. Apologies it's taken a while to address your comments - other things have taken priority this week.
I've administered your suggestions in the relevant commits, and then added a final commit for moving the data sync logic into the RavenDelegator.
I'm aware you've opted for a configure.rb for the default configuration and a configuration.rb for the should_capture logic. I've left as-is for now (configure_defaults.rb and raven_delegator.rb respectively) as I think this is more scannable, but I'm happy to be talked out of it. (I'm personally of the view that 'configuration' implies where the default config lives, and I wouldn't know what 'configure' is supposed to do in that context).

Thanks @kevindew - some excellent suggestions there, have applied them all.

(@kevindew I've just pushed a 'bump to 2.5.0' commit, which involved a rebase as the version had changed while this PR was open. There are no other new changes).


[FLINK-21480][runtime] Respect external resources from resource requirements

What is the purpose of the change
Respect external resources from resource requirements
Brief change log
(for example:)

The TaskInfo is stored in the blob store on job creation time as a persistent artifact
Deployments RPC transmits only the blob storage reference
TaskManagers retrieve the TaskInfo from the blob cache

Verifying this change
(Please pick either of the following options)
This change is a trivial rework / code cleanup without any test coverage.
(or)
This change is already covered by existing tests, such as (please describe tests).
(or)
This change added tests and can be verified as follows:
(example:)

Added integration tests for end-to-end deployment with large payloads (100MB)
Extended integration test for recovery after master (JobManager) failure
Added test that validates that TaskInfo is transferred only once across recoveries
Manually verified the change by running a 4 node cluser with 2 JobManagers and 4 TaskManagers, a stateful streaming program, and killing one JobManager and two TaskManagers during the execution, verifying that recovery happens correctly.

Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): (yes / no)
The public API, i.e., is any changed class annotated with @Public(Evolving): (yes / no)
The serializers: (yes / no / don't know)
The runtime per-record code paths (performance sensitive): (yes / no / don't know)
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn/Mesos, ZooKeeper: (yes / no / don't know)
The S3 file system connector: (yes / no / don't know)

Documentation

Does this pull request introduce a new feature? (yes / no)
If yes, how is the feature documented? (not applicable / docs / JavaDocs / not documented)

@xintongsong Thanks for the review! PR updated.

Thanks for the review @xintongsong . I've verified it in a Kubernetes cluster.


Tracking issue for release 0.10.2

If you want to help with the next release, please add a message here picking one item below! There are a few things only I can do, marked with 🔑 below, and a few other only members of the chemfiles organisation can do, marked with 🗝 below.
Pre-built chemfiles

[x] tag the release on chemfiles/chemfiles
[x] build release on conda-forge (https://github.com/conda-forge/chemfiles-lib-feedstock/pull/44)
[ ] ~try building on Linux: https://build.opensuse.org/package/show/home:Luthaf/chemfiles-staging 🔑~

will not happen, see #437

[ ] ~release Linux builds: https://build.opensuse.org/package/show/home:Luthaf/chemfiles 🔑~

will not happen, see #437

[x] Build release for Julia (https://github.com/JuliaPackaging/Yggdrasil): https://github.com/JuliaPackaging/Yggdrasil/pull/3887

Language bindings
Python

[x] Update the submodule, update code, create PR: https://github.com/chemfiles/chemfiles.py/pull/36
[x] Update code to deal with the new SONAME (i.e. #416)
[x] Tag release 🗝
[x] Create PR on https://github.com/conda-forge/chemfiles-python-feedstock/ (https://github.com/conda-forge/chemfiles-python-feedstock/pull/21)
[x] Build wheels & upload on PyPI 🔑

blocked on https://github.com/chemfiles/chemfiles/pull/438 for sdist

Julia

[x] Update Chemfiles_jll version, create PR: https://github.com/chemfiles/Chemfiles.jl/pull/54
[x] Tag release 🗝
[x] Register the new version on https://github.com/JuliaRegistries/General 🗝 (https://github.com/JuliaRegistries/General/pull/49540)

Rust

[X] Update the submodule, update code, create PR: https://github.com/chemfiles/chemfiles.rs/pull/20
[X] Use pre-built chemfiles downloaded from github when possible (I have a branch doing this locally)
[x] Tag release 🗝
[x] Release on crates.io 🔑

blocked on https://github.com/chemfiles/chemfiles/pull/438

Fortran

[X] Update the submodule, update code, create PR: https://github.com/chemfiles/chemfiles.f03/pull/13
[x] Tag release 🗝

All done!


Highlight matched text

The "fuzzy" library has a cool feature to enclose the matched strings with custom text: https://www.stackage.org/haddock/lts-15.1/fuzzy-<IP_ADDRESS>/Text-Fuzzy.html#v:match
Any chance you will support this as well? 😊

Thanks for the suggestion! I will have a look at it this week.


how to change mermaid text color or line text block color？

I am using Typora, and the user are allowed to use .css file to set up the style of mermaid graphs. I am wondering how to set up the text color or line text block filled-color by .css file? Because Typora's author are somehow setting the text color as the same color as my code fence, which is white, the text seems totally invisible in my flowchart. Hope there is a way can figure that out.

Since you can use .css file. You can simply override the color. Here the css(less) code for mermaid: https://github.com/knsv/mermaid/tree/master/src/less

@tylerlong
你好，我最近在使用美人鱼，需求是想要改变某条流程线的颜色，而不是修改整体的CSS去改变所有流程线，目前的API中能实现吗？
Hello, I recently used mermaid, the demand is to change the color of a process line, rather than modify the overall CSS to change all the process lines, the current API can be achieved?

@tylerlong 好吧，我们更改了需求，不再要求修改流程线的颜色，用API的方法修改流程线的样式为实线、虚线。
Ok, we changed the demand, no longer ask to modify the color of the process line, with the API method to modify the flow line style is solid line, dotted line.

Please read https://mermaidjs.github.io/faq.html How to specify custom CSS file?

@tylerlong 好吧，我们更改了需求，不再要求修改流程线的颜色，用API的方法修改流程线的样式为实线、虚线。
Ok, we changed the demand, no longer ask to modify the color of the process line, with the API method to modify the flow line style is solid line, dotted line.

使用 html 语言可以直接在 typora mermaid 编辑内容上改变字体颜色，不知道是否能满足你的需要。
比如 --> tst


Uncaught exception when cancelling connection with pending characteristics read/write

Please check all of the platforms you are having the issue on (if platform is not listed, it is not supported)

[] iOS
[X] Android
[] tvOS
[] macOS
[] .NET Standard
UWP IS NOT SUPPORTED DURING THE BETA PERIOD - ONLY PRs ARE WELCOME FOR NOW

Version of OS(s) listed above with issue
7.0
Version of Library
NuGET 5.2.0
Expected Behaviour
There is a clean way of starting an unawaited read or write on characteristics, and when the connection fails or a CancelConnection on the IDevice is issued between the start of the read/write and the indication of completion by android througt the GattCallback no exception is thrown or it is caught internally by the plugin.
Actual Behavior
When starting a read or write on characteristic that is not awaited, a CancelConnection on the IDevice results in an uncaught exception of a disposed semaphore. The semaphore in question is in DeviceContext.cs in Internals in public IObservable LockObservable() and specifically it is released on line 93 (this.semaphore.Release();).
The exception text is this:
11-17 15:28:43.705 F/art     ( 4980): art/runtime/runtime.cc:403]   at md5e0c8df6e6e221d5c163c41bc679a7531.GattCallbacks.n_onCharacteristicRead(Native method)
11-17 15:28:43.705 F/art     ( 4980): art/runtime/runtime.cc:403]   at md5e0c8df6e6e221d5c163c41bc679a7531.GattCallbacks.onCharacteristicRead(GattCallbacks.java:38)
11-17 15:28:43.705 F/art     ( 4980): art/runtime/runtime.cc:403]   at android.bluetooth.BluetoothGatt$1.onCharacteristicRead(BluetoothGatt.java:334)
11-17 15:28:43.705 F/art     ( 4980): art/runtime/runtime.cc:403]   at android.bluetooth.IBluetoothGattCallback$Stub.onTransact(IBluetoothGattCallback.java:117)
11-17 15:28:43.705 F/art     ( 4980): art/runtime/runtime.cc:403]   at android.os.Binder.execTransact(Binder.java:573)
11-17 15:28:43.705 F/art     ( 4980): art/runtime/runtime.cc:403] Pending exception android.runtime.JavaProxyThrowable: System.ObjectDisposedException: The semaphore has been disposed.
11-17 15:28:43.705 F/art     ( 4980): art/runtime/runtime.cc:403]   at System.Threading.SemaphoreSlim.CheckDispose () [0x00013] in <183b200ee49746d48fc781625979428e>:0
11-17 15:28:43.705 F/art     ( 4980): art/runtime/runtime.cc:403]   at System.Threading.SemaphoreSlim.Release (System.Int32 releaseCount) [0x00000] in <183b200ee49746d48fc781625979428e>:0
11-17 15:28:43.705 F/art     ( 4980): art/runtime/runtime.cc:403]   at System.Threading.SemaphoreSlim.Release () [0x00000] in <183b200ee49746d48fc781625979428e>:0
11-17 15:28:43.705 F/art     ( 4980): art/runtime/runtime.cc:403]   at Plugin.BluetoothLE.Internals.DeviceContext+<>c__DisplayClass15_11[T].<LockObservable>b__1 () [0x00033] in C:\dev\acr\bluetoothle\Plugin.BluetoothLE.Android\Internals\DeviceContext.cs:93  11-17 15:28:43.705 F/art     ( 4980): art/runtime/runtime.cc:403]   at System.Reactive.Disposables.AnonymousDisposable.Dispose () [0x00010] in <99f8205c51c44bb480747b577b8001ff>:0  11-17 15:28:43.705 F/art     ( 4980): art/runtime/runtime.cc:403]   at System.Reactive.Disposables.SingleAssignmentDisposable.Dispose () [0x00014] in <99f8205c51c44bb480747b577b8001ff>:0  11-17 15:28:43.705 F/art     ( 4980): art/runtime/runtime.cc:403]   at System.Reactive.Disposables.StableCompositeDisposable+Binary.Dispose () [0x00026] in <99f8205c51c44bb480747b577b8001ff>:0  11-17 15:28:43.705 F/art     ( 4980): art/runtime/runtime.cc:403]   at System.Reactive.Disposables.SingleAssignmentDisposable.Dispose () [0x00014] in <99f8205c51c44bb480747b577b8001ff>:0  11-17 15:28:43.705 F/art     ( 4980): art/runtime/runtime.cc:403]   at System.Reactive.AutoDetachObserver1[T].Dispose (System.Boolean disposing) [0x0000a] in <99f8205c51c44bb480747b577b8001ff>:0
11-17 15:28:43.705 F/art     ( 4980): art/runtime/runtime.cc:403]   at System.Reactive.ObserverBase1[T].Dispose () [0x00000] in <99f8205c51c44bb480747b577b8001ff>:0  11-17 15:28:43.705 F/art     ( 4980): art/runtime/runtime.cc:403]   at System.Reactive.AutoDetachObserver1[T].OnCompletedCore () [0x0000d] in <99f8205c51c44bb480747b577b8001ff>:0
11-17 15:28:43.705 F/art     ( 4980): art/runtime/runtime.cc:403]   at System.Reactive.ObserverBase1[T].OnCompleted () [0x0000e] in <99f8205c51c44bb480747b577b8001ff>:0  11-17 15:28:43.705 F/art     ( 4980): art/runtime/runtime.cc:403]   at Plugin.BluetoothLE.Extensions.Respond[T] (System.IObserver1[T] ob, T value) [0x00007] in C:\dev\acr\bluetoothle\Plugin.BluetoothLE.Abstractions\Extensions_Rx.cs:22
11-17 15:28:43.705 F/art     ( 4980): art/runtime/runtime.cc:403]   at Plugin.BluetoothLE.GattCharacteristic+<>c__DisplayClass6_0.b__1 (Plugin.BluetoothLE.Internals.GattCharacteristicEventArgs args) [0x0005c] in C:\dev\acr\bluetoothle\Plugin.BluetoothLE.Android\GattCharacteristic.cs:97
11-17 15:28:43.705 F/art     ( 4980): art/runtime/runtime.cc:403]   at System.Reactive.AnonymousSafeObserver1[T].OnNext (T value) [0x0000a] in <99f8205c51c44bb480747b577b8001ff>:0  11-17 15:28:43.705 F/art     ( 4980): art/runtime/runtime.cc:403]   at System.Reactive.Linq.ObservableImpl.Where1+_[TSource].OnNext (TSource value) [0x00030] in :0
11-17 15:28:43.705 F/art     ( 4980): art/runtime/runtime.cc:403]   at System.Reactive.Observer1[T].OnNext (T value) [0x00010] in <99f8205c51c44bb480747b577b8001ff>:0  11-17 15:28:43.705 F/art     ( 4980): art/runtime/runtime.cc:403]   at System.Reactive.Subjects.Subject1[T].OnNext (T value) [0x00000] in :0
11-17 15:28:43.705 F/art     ( 4980): art/runtime/runtime.cc:403]   at Plugin.BluetoothLE.Internals.GattCallbacks.OnCharacteristicRead (Android.Bluetooth.BluetoothGatt gatt, Android.Bluetooth.BluetoothGattCharacteristic characteristic, Android.Bluetooth.GattStatus status) [0x00000] in C:\dev\acr\bluetoothle\Plugin.BluetoothLE.Android\Internals\GattCallbacks.cs:12
11-17 15:28:43.705 F/art     ( 4980): art/runtime/runtime.cc:403]   at Android.Bluetooth.BluetoothGattCallback.n_OnCharacteristicRead_Landroid_bluetooth_BluetoothGatt_Landroid_bluetooth_BluetoothGattCharacteristic_I (System.IntPtr jnienv, System.IntPtr native__this, System.IntPtr native_gatt, System.IntPtr native_characteristic, System.Int32 native_status) [0x00017] in <484d528f6626418ea3cba8d2e5438e61>:0
11-17 15:28:43.705 F/art     ( 4980): art/runtime/runtime.cc:403]   at (wrapper dynamic-method) System.Object:0e5fac13-16cd-4d77-ab92-6af629b938ce (intptr,intptr,intptr,intptr,int)
11-17 15:28:43.705 F/art     ( 4980): art/runtime/runtime.cc:403]   at void md5e0c8df6e6e221d5c163c41bc679a7531.GattCallbacks.n_onCharacteristicRead(android.bluetooth.BluetoothGatt, android.bluetooth.BluetoothGattCharacteristic, int) (GattCallbacks.java:-2)
11-17 15:28:43.705 F/art     ( 4980): art/runtime/runtime.cc:403]   at void md5e0c8df6e6e221d5c163c41bc679a7531.GattCallbacks.onCharacteristicRead(android.bluetooth.BluetoothGatt, android.bluetooth.BluetoothGattCharacteristic, int) (GattCallbacks.java:38)
11-17 15:28:43.705 F/art     ( 4980): art/runtime/runtime.cc:403]   at void android.bluetooth.BluetoothGatt$1.onCharacteristicRead(java.lang.String, int, int, byte[]) (BluetoothGatt.java:334)
11-17 15:28:43.705 F/art     ( 4980): art/runtime/runtime.cc:403]   at boolean android.bluetooth.IBluetoothGattCallback$Stub.onTransact(int, android.os.Parcel, android.os.Parcel, int) (IBluetoothGattCallback.java:117)
11-17 15:28:43.705 F/art     ( 4980): art/runtime/runtime.cc:403]   at boolean android.os.Binder.execTransact(int, long, long, int) (Binder.java:573)
I will ivnestigate some fixes and report back in.
Thanks!
Code of Conduct

No Library Update Requests
No Timeline Requests
Please read through the documentation and FAQs
Please be respectful of my time. I put a lot of effort into my libraries.  I try to support the issue requests within a day.  I'm not psychic, so please take the time to fill out the above form as complete as possible

The issue should be fixed, however, I would recommend trapping errors coming from read/write as they can happen for many other reasons aside from this one.

Thanks! I am trapping around the read/writeand yet these went uncaught. I am unsure as to why. I trapped on all exceptions, to no avail. Any suggestions? Would it help, in this case, to also trap around the CancelConnection()'s?

Follow-up: This seems to, at least for me, break reads (and possibly writes) on characteristics. They now time out for me, where before they returned successfully with the read data from the characteristic. I'm investigating and hope to have more soon but my guess is that it is related to the same semaphore.

It looks like 5.2.1 is no longer available on NuGET. I did previously pull it and noticed a few issues with characteristic reads and writes completing, which I believe are related to the semaphore changes. ANything I can do to help?


win32 spigui should cope properly with multiple serial devices

When there is one serial device, it should just connect to it.
But when there are multiple serial devices, it should not connect, and wait for the user to pick one from the pulldown.

Fixed, closing.


Create goldcup.yml

Adds or updates the following companies, events, or universities:

Checklist
Company updates

[1] I have put the most recent relevant date in the "Last Update" column
[1] I have linked to the article about the change, not the company's homepage (Please put N/A if there is no public post)

Event updates

[1] I have linked to the article about the change, not the event's homepage

University updates

[1] I have linked to the article about the change, not the university's homepage

Hello! My company has not yet been added to the list of companies in stayinghomeclub


New SVGP with posterior object and faster predictions

Posterior class with precomupations speeding up test

Superseded by #1636. @stefanosele do you want to have a look at the new PR? It's changed quite a bit since you last saw it. Would be great to get your thoughts on it.

@st-- I can have a look closer to the end of the week. I'm a bit overwhelmed with starting on the new job. Sorry for the massive delay


Set default date format to locale string

Hello,
How can I set the default date format to be a locale string ? Like
date.toLocaleString(), date.toLocaleDateString() and e.t.c. ?
I want the date format to be defined by user's locale and not hardcoded in the system.

You would have to get the format of the locale date before initializing flatpickr. I found this:
https://stackoverflow.com/questions/2388115/get-locale-short-date-format-using-javascript
that might help you out

This is outside of this project's scope and maintaining such a locale database would be a significant undertaking.

This is outside of this project's scope and maintaining such a locale database would be a significant undertaking.

@chmln Why would there be a need for any maintenance of a database though? It's a native browser feature that uses the user's preferences. Try running (new Date()).toLocaleString() in your browser's console.
Is there perhaps an implementation detail preventing the usage of this? I was looking through the library and it looks pretty decent but this is a pretty big turn off as far as I can tell right now. If you can verify there's no weird implementation detail stopping this I could submit a PR.

@mpalmr
Hi
Would you (or anyone else perhaps) care to suggest where that could be set ?
I have noted the following:
Selecting date and time using flatpickr is great and it's really responsive.
I collect the date and send it to another system as a timestamp, however when receiving it back I have to convert it in my code and it ends up at GMT (at the moment I'm trying to add the extra 3600 to the timestamp to get a matching time)
If user selection can be set to (new Date()).toLocaleString() then changing the code back to the correct date and time from timestamp becomes a whole lot simpler.
@chmln ...May i kindly add this to the wishlist please :-)
If someone could suggest a workaround or easy way in the meantime I would appreciate it.
Is there perhaps a way to set/pin flatpickr to a specific timezone on intialiazation ?
Thank you
Den


Feature: Support for identify IOS 13

Ability to identify the new IOS 13 safari browsers for ipads

https://github.com/arasatasaygin/is.js/pull/319


Updates setup.py to include classifiers and version

@mwengren after this I'd like to push this to pypi so folks can install it through the standard packager, after that I'll work with @ocefpaf to get it into conda.

Once the package mades into PyPI we can do a conda skeleton pypi <package name>, edit the recipe to conform to conda-forge, and send the PR to staged-recipes.

ooh good call @ocefpaf!


text fix FYPO:0003010

Can I have a text summary? Or at least a screenshot with bigger text?

it's just the comment that contains text "MERGED COMMENT:\nTARGET COMMENT:
yadiyada

ok, thanks. fixed at source and will go live next time I run the release script.


Add Microsoft.VisualStudio.Component.WinXP to Visual Studio

Tool information

Tool name: Microsoft.VisualStudio.Component.WinXP
Add or update? Add
Desired version: The one that comes with Visual Studio
Approximate size:
If this is an add request:

Brief description of tool: This is a component of Visual Studio that enables compiling C/C++ with XP compatibility
URL for tool's homepage:

Area for Triage:

Question, Bug, or Feature?:
Feature
Virtual environments affected

[ ] macOS 10.15
[ ] Ubuntu 16.04 LTS
[ ] Ubuntu 18.04 LTS
[ ] Windows Server 2016 R2
[x] Windows Server 2019

Can this tool be installed during the build?

Manual install at each run consumes ~14 minutes (refer to https://github.com/canihavesomecoffee/ccextractor/commit/821f20dc0e443e74155a8eee486957f1cecb51ff/checks?check_suite_id=408296775), so I believe it's more efficient to add this by default.
Are you willing to submit a PR?

Yes! I'll make the modification and open a PR.

The component is presented on the image
https://github.com/actions/virtual-environments/releases/tag/win19%2F20200301.1
Closing the issue


clangmm no longer compiles on windows

libclangmm does no longer compile on windows

@eidheim I will make sure this repo compiles on windows. Do you know how to compile without MSVS?

No idea sorry, but I think there is a free version of MSVS? Visual Studio Code maybe?

There is also a Visual Studio Community: https://www.visualstudio.com/vs-2015-product-editions

I will see if I find an easy way to do it without ms-software.

Hope you figure it out. I used MinGW-w64, which is more updated than MinGW. However MinGW-w64 is less used it seems, so don't know how well it is supported by the various open source projects. Also MinGW-w64 had support for threads and c++14 (which MinGW lacked), however if you have troubles, we could go for boost.threads instead. But you might find better solutions than I did a couple of years ago. Also not sure if MinGW supports regex either since its so old, but luckily boost has this as well. You can see some of the differences here: https://en.wikipedia.org/wiki/MinGW
Also, we might need Boost.PropertyTree in libclangmm to parse comments, which luckily also are exported in XML as well as HTML by libclang. The HTML-output from libclang was awful, but hopefully the XML is better. I will investigate this at some point.

Maybe Cygwin is the way to go (http://stackoverflow.com/a/4147985)? Might be that most if not all of the libraries are included in the cygwin distribution (https://cygwin.com/packages/package_list.html)?

There is also a mingw-w64 package in cygwin that one could use (https://cygwin.com/packages/x86/mingw64-i686-gcc-g++/)?

From https://en.wikipedia.org/wiki/Cygwin: "Cygwin is used heavily for porting many popular pieces of software to the Windows platform. It is used to compile Sun Java, OpenOffice.org, LibreOffice, and even web server software like Lighttpd and Hiawatha."


hello jeremy

hello jeremy .. i installed sonar-dependency-check plugin on sonarqube and i configured pom.xml with maven plugin

org.owasp
dependency-check-maven
1.4.5

and when i run the build it gives me below error
11-May-2017 02:18:04	[ERROR] IO Exception: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
11-May-2017 02:18:05	[ERROR] IO Exception: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
11-May-2017 02:18:05	[WARNING] Unable to download the NVD CVE data; the results may not include the most recent CPE/CVEs from the NVD.
11-May-2017 02:18:05	[INFO] If you are behind a proxy you may need to configure dependency-check to use the proxy.
i added env variables as JAVA_TOOL_OPTIONS="-Djavax.net.ssl.trustStore="/usr/lib/jvm/java-1.8.0/jre/lib/security/cacerts"
and additional parameters as -Ddownloader.quick.query.timestamp=false
nothing worked.
MONGO-AA-JOB1-62.txt

My initial guess based on the log file is that the cacerts file you are using does not contain a necessary cert. In googling your error message I found this article with a simple Java class one could use to diagnose this problem: https://confluence.atlassian.com/kb/unable-to-connect-to-ssl-services-due-to-pkix-path-building-failed-779355358.html

When investigating a different issue I found the same issue. This revolves around not have the correct cert in your keystore.  See the Install Cert example, which is a clone of a previously documented solution.


✅ Add missing union typing import

Adds Union import for type hints in one of tests

Nice, thanks!


Kafka container failed to start ...

Just started a new project with Kafka dependency, got this error when running docker-compose:

docker-compose -f deploy/docker-compose.yml -f deploy/docker-compose.dev.yml --project-directory . up --build

kafka-1          | [2024-06-26 04:23:45,075] INFO Loading logs from log dirs ArrayBuffer(/bitnami/kafka/data) (kafka.log.LogManager)
kafka-1          | [2024-06-26 04:23:45,160] INFO Attempting recovery for all logs in /bitnami/kafka/data since no clean shutdown file was found (kafka.log.LogManager)
kafka-1          | [2024-06-26 04:23:45,514] INFO Loaded 0 logs in 438ms. (kafka.log.LogManager)
kafka-1          | [2024-06-26 04:23:45,535] INFO Starting log cleanup with a period of 300000 ms. (kafka.log.LogManager)
kafka-1          | [2024-06-26 04:23:45,606] INFO Starting log flusher with a default period of<PHONE_NUMBER>854775807 ms. (kafka.log.LogManager)
kafka-1          | [2024-06-26 04:23:46,012] INFO Starting the log cleaner (kafka.log.LogCleaner)
kafka-1          | [2024-06-26 04:23:47,366] INFO [kafka-log-cleaner-thread-0]: Starting (kafka.log.LogCleaner)
kafka-1          | [2024-06-26 04:23:59,841] INFO [BrokerToControllerChannelManager broker=1 name=forwarding]: Starting (kafka.server.BrokerToControllerRequestThread)
dependency failed to start: container market_insights-kafka-1 exited (137)
make: *** [dev] Error 1

How to understand this error? I'm running this on my Mac machine. Thanks

using the latest kafka docker image solves the problem:
kafka:
    image: "bitnami/kafka:latest"


Implements form node admin alter

What's this PR do?
Removes ?destination=admin/content from edit links on admin/content
How should this be manually tested?
Click edit on any campaign on /admin/content
Any background context you want to provide?
Please see the chain of comments here which led to me figuring out this was the cause https://github.com/DoSomething/phoenix/issues/5114#issuecomment-142964203
What are the relevant tickets?
Fixes #5114
Fixes #1273
@angaither

also, you can close out that old issue with this too!

@angaither good to merge?

WHOOPS

@angaither OKAY. got it this time

:+1:


gtksourceview: 4.6.0 -> 4.6.1

Motivation for this change
Version bump:
News in 4.6.1, 2020-06-26
-------------------------
* Fix various G-I annotations
* Improve draw-spaces coloring in solarized-light
* javascript.lang: Performance improvements
* c.lang: Fixes for #include preprocessor
* sql.lang: Language completeness improvements
* latex.lang: additional keywords
* sh.lang: improved parameter expansion
* yara.lang: initial support for YARA
* Translation updates

Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[ ] Fits CONTRIBUTING.md.

Thanks.


Update Getting started Index with typo fixes

What this PR does / why we need it:
Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #

@Princesso thanks for the PR! Could you just sign the commit and force push? You can ping me, and I'll approve it.

Codecov Report

Merging #993 (8ef6a7a) into master (94175ca) will not change coverage.
The diff coverage is n/a.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@           Coverage Diff           @@
##           master     #993   +/-   ##
=======================================
  Coverage   22.79%   22.79%
=======================================
  Files          22       22
  Lines        1610     1610
=======================================
  Hits          367      367
  Misses       1179     1179
  Partials       64       64

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


No LOD0 export using appearances?

I guess defining appearances for LoD0 geometries (e.g. footprint buildings) does not clash with CityGML rules.
The importer/exporter however greys out the possibility to export LoD0 geometries with textures (or X3DMaterials) associated to them.
Am I missing something?
BR
GA

Could you share your CityGML dataset including the textured LoD0 geometries?

Closing due to lack of feedback. @gioagu, feel free to reopen if this is still relevant and you can share test datasets.


Add hero banner

📝 Changed routes:

/

(view full size)

Commit fa30682dafc05d6437c9b01d0011957d3416f3b2 (https://thvu-blog-jqxw2hmne-thvu.vercel.app).


Modulate emissive by alpha on blended objects

This prevents light from being emitted from completely transparent pixels.
Fixes #3454.

The spec says nothing about this. And the asset to repro the issue crashes Babylon.js and Don McCurdy's viewer… :)

The spec says nothing about this. And the asset to repro the issue crashes Babylon.js and Don McCurdy's viewer… :)


Update forms.md

This section was out of date for me; here are some updated instructions (at least for MacOS Sonoma 14).

Thank you! One tiny question: how come we can call an image from the asset url, but it's not stored in the repo 🤔. Is it a temporary storage?

I wasn't sure how to add an image through the web UI (I didn't have a fork at the time), so I dragged it as a comment and it uploaded to that URL.
But you're 100% right to call that out; it should be moved to the repo -- I'm just away from the desk. lmk if you can do it, otherwise I can in an hour or 2

Actually... now that I look, I remember the reason I felt comfortable leaving it: it's hosted under your organization, so I don't think it'll get deleted, unless explicitly. That said, it should still probably be moved.

Sure! Just add the picture to the repo. static/img/docs seems a start, but you can choose other place too

Superseded by #52


Fixing test testThatParserFailsWhenIncompleteDataIsPresent

Was previously not iterating over test cases and instead using hard-coded string " " to test JSONParser.parse

Thanks! Good catch. :)


ImportError: numpy.core.multiarray failed to import (v1.0.1)

(I sent an email for this but just for the record let me create this issue here!)
The Docker container with tag 1.0.1 fails to run with the following error message.
[0mModuleNotFoundError: No module named 'numpy.core._multiarray_umath'
Traceback (most recent call last):
  File "/usr/bin/rsHRF", line 6, in <module>
    from rsHRF.CLI import main
  File "/usr/lib/python3.6/site-packages/rsHRF/__init__.py", line 6, in <module>
    import rsHRF.fourD_rsHRF
  File "/usr/lib/python3.6/site-packages/rsHRF/fourD_rsHRF.py", line 5, in <module>
    import matplotlib.pyplot as plt
  File "/usr/lib/python3.6/site-packages/matplotlib/pyplot.py", line 32, in <module>
    import matplotlib.colorbar
  File "/usr/lib/python3.6/site-packages/matplotlib/colorbar.py", line 27, in <module>
    import matplotlib.artist as martist
  File "/usr/lib/python3.6/site-packages/matplotlib/artist.py", line 13, in <module>
    from .path import Path
  File "/usr/lib/python3.6/site-packages/matplotlib/path.py", line 17, in <module>
    from . import _path, cbook, rcParams
ImportError: numpy.core.multiarray failed to import

The new container seems to be using a slightly newer version of python, but apart from that I couldn't really tell why it's failing.
Soichi

@soichih This probably looks like an issue with which version of numpy is installed. Could you provide me with the data files that you used? That way, I could reproduce the issue and verify it for myself as well.

@madhur-tandon
You don't need any input file to reproduce this problem. You can try this.
$ singularity exec -e docker://bids/rshrf:1.0.1 python -c "import rsHRF.CLI.main"
Docker image path: index.docker.io/bids/rshrf:1.0.1
Cache folder set to /N/dc2/scratch/hayashis/singularity-cache-carb/docker
Creating container runtime...
Exploding layer: sha256:c87736221ed0bcaa60b8e92a19bec2284899ef89226f2a07968677cf59e637a4.tar.gz
Exploding layer: sha256:de018ce6d111d006b377e721c8a3914fc526812c40c188abed659f92d7d894ae.tar.gz
Exploding layer: sha256:79d44530889bef66f3150df5c230e8c24ca117f15c6782421827b119e4f6c81b.tar.gz
Exploding layer: sha256:aa5481042e4030b6f741357f34df851d6fd5434d77d4947bb15f2951811d4b7f.tar.gz
ModuleNotFoundError: No module named 'numpy.core._multiarray_umath'
Traceback (most recent call last):
  File "<string>", line 1, in <module>
  File "/usr/lib/python3.6/site-packages/rsHRF/__init__.py", line 6, in <module>
    import rsHRF.fourD_rsHRF
  File "/usr/lib/python3.6/site-packages/rsHRF/fourD_rsHRF.py", line 5, in <module>
    import matplotlib.pyplot as plt
  File "/usr/lib/python3.6/site-packages/matplotlib/pyplot.py", line 32, in <module>
    import matplotlib.colorbar
  File "/usr/lib/python3.6/site-packages/matplotlib/colorbar.py", line 27, in <module>
    import matplotlib.artist as martist
  File "/usr/lib/python3.6/site-packages/matplotlib/artist.py", line 13, in <module>
    from .path import Path
  File "/usr/lib/python3.6/site-packages/matplotlib/path.py", line 17, in <module>
    from . import _path, cbook, rcParams
ImportError: numpy.core.multiarray failed to import

Hi,

@soichih @markushs I have pushed a new build both on DockerHub and on PyPI. The new version is 1.0.8. I think the error for numpy.core._multiarray_umath or numpy.core.multiarray is fixed. Could any of you please check and confirm? Let me know, Thanks!

@madhur-tandon I just tested 1.0.8 container and it finished successfully.

@soichih Great, I am closing this issue.


Scary message in logs after app start on Android

Steps to Reproduce

Run a starter app on Android device.

Expected: no warnings in log output
Actual: "Unable to start service Intent"
Flutter Version
Flutter from git@github.com:flutter/flutter.git (on hackathon)
flutter revision: 4860e63f444cf3786a6b136430f3058a7b851041 (14 hours ago)
engine revision : a53faaf7983025f83a2059021a409c6e98beb58d

[✓] The iOS toolchain is fully installed.
[✓] The Android toolchain is fully installed.
[✓] The Atom development environment is fully installed.

Logs
W/ActivityManager: Unable to start service Intent { flg=0x4 cmp=com.yourcompany.testme2/org.domokit.sky.shell.UpdateService (has extras) } U=0: not found

(If this is benign, can we hide it? Or, better yet, remove the warning?)

cc @mpcomplete any thoughts? Thanks!

I removed the UpdateService for now.

OK, thanks for the update!


unable to get stub builder for org.jetbrains.lang.manifest.ManifestFileType@480c9db7

After changing okhttp3 library with the latest version 3.5.0 began appears following EmptyThrowable on the Android Studio:
11:29:05 AM EmptyThrowable: unable to get stub builder for org.jetbrains.lang.manifest.ManifestFileType@480c9db7, path = /Users/admin/.gradle/caches/modules-2/files-2.1/com.squareup.okhttp3/logging-interceptor/3.5.0/36f80e3705c6123f2d4ca85ab92efe899d81a93c/logging-interceptor-3.5.0-sources.jar!/META-INF/MANIFEST.MF, stubBindingRoot = ManifestFileImpl, languages = [Manifest], filesTypes = [Manifest], files = [ManifestFileImpl], roots = []
11:29:20 AM EmptyThrowable: unable to get stub builder for org.jetbrains.lang.manifest.ManifestFileType@480c9db7, path = /Users/admin/.gradle/caches/modules-2/files-2.1/com.squareup.okhttp3/logging-interceptor/3.5.0/36f80e3705c6123f2d4ca85ab92efe899d81a93c/logging-interceptor-3.5.0-sources.jar!/META-INF/MANIFEST.MF, stubBindingRoot = ManifestFileImpl, languages = [Manifest], filesTypes = [Manifest], files = [ManifestFileImpl], roots = []
How to fix this is?

What makes you believe this is a problem with OkHttp? It seems like
something related to your build system.
On Wed, Jan 18, 2017, 10:37 PM Saparboy<EMAIL_ADDRESS>wrote:

After changing okhttp3 library with the latest version 3.5.0 began appears
following EmptyThrowable on the Android Studio:
11:29:05 AM EmptyThrowable: unable to get stub builder for
org.jetbrains.lang.manifest.ManifestFileType@480c9db
https://github.com/org.jetbrains.lang.manifest.ManifestFileType/okhttp/commit/480c9db7,
path =
/Users/admin/.gradle/caches/modules-2/files-2.1/com.squareup.okhttp3/logging-interceptor/3.5.0/36f80e3705c6123f2d4ca85ab92efe899d81a93c/logging-interceptor-3.5.0-sources.jar!/META-INF/MANIFEST.MF,
stubBindingRoot = ManifestFileImpl, languages = [Manifest], filesTypes =
[Manifest], files = [ManifestFileImpl], roots = []
11:29:20 AM EmptyThrowable: unable to get stub builder for
org.jetbrains.lang.manifest.ManifestFileType@480c9db
https://github.com/org.jetbrains.lang.manifest.ManifestFileType/okhttp/commit/480c9db7,
path =
/Users/admin/.gradle/caches/modules-2/files-2.1/com.squareup.okhttp3/logging-interceptor/3.5.0/36f80e3705c6123f2d4ca85ab92efe899d81a93c/logging-interceptor-3.5.0-sources.jar!/META-INF/MANIFEST.MF,
stubBindingRoot = ManifestFileImpl, languages = [Manifest], filesTypes =
[Manifest], files = [ManifestFileImpl], roots = []
How to fix this is?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/square/okhttp/issues/3121, or mute the thread
https://github.com/notifications/unsubscribe-auth/AAEEEQu7upBSPmloCSCbS2NzW9DfSrGEks5rTwSsgaJpZM4LnwMH
.

Hi!
I think this is OkHttp issue because, if I will return back library version 3.4.2 will be works like a charm. If I will change library version with latest then you can see these exceptions.
This is my app build.gradle file:
buildscript {
    repositories {
        mavenCentral()
        maven { url 'https://maven.fabric.io/public' }
    }

    dependencies {
        classpath 'io.fabric.tools:gradle:1.+'
    }
}
apply plugin: 'com.android.application'
apply plugin: 'io.fabric'

android {
    compileSdkVersion 25
    buildToolsVersion "25.0.2"

    dataBinding {
        enabled = true
    }

    defaultConfig {
        applicationId "de.fubar.anapp"
        minSdkVersion 15
        targetSdkVersion 25
        versionCode 15
        versionName "1.0.1"
        testInstrumentationRunner "android.support.test.runner.AndroidJUnitRunner"

        vectorDrawables.useSupportLibrary = true
        resConfigs "en", "de"

        multiDexEnabled true
    }

    aaptOptions {
        cruncherEnabled = false
    }

    lintOptions {
        abortOnError false
    }

    buildTypes {
        release {
            minifyEnabled false
            proguardFiles getDefaultProguardFile('proguard-android.txt'), 'proguard-rules.pro'
        }
    }

    packagingOptions {
        exclude 'META-INF/LICENSE.txt'
        exclude 'META-INF/NOTICE.txt'
        exclude 'META-INF/LICENSE'
        exclude 'META-INF/license.txt'
    }
}

repositories {
    mavenCentral()
    maven { url 'https://maven.fabric.io/public' }
}

gradle.taskGraph.useFilter { task ->
    if (task.name.contains("Test") || task.name.contains("mockable")) {
        return false;
    }
    return true;
}

dependencies {
    compile fileTree(dir: 'libs', include: ['*.jar'])
    androidTestCompile('com.android.support.test.espresso:espresso-core:2.2.2', {
        exclude group: 'com.android.support', module: 'support-annotations'
    })

    compile 'com.android.support:multidex:1.0.1'
    compile 'com.android.support:appcompat-v7:25.1.0'
    compile 'com.android.support:design:25.1.0'
    compile 'com.android.support:support-v4:25.1.0'
    compile 'com.google.firebase:firebase-messaging:10.0.1'
    compile 'com.google.firebase:firebase-crash:10.0.1'
    compile 'com.google.android.gms:play-services-maps:10.0.1'
    compile 'com.google.android.gms:play-services-places:10.0.1'
    compile 'com.google.android.gms:play-services-location:10.0.1'
    compile 'com.jakewharton:butterknife:8.4.0'
//    compile 'com.squareup.okhttp3:okhttp:3.5.0'
//    compile 'com.squareup.okhttp3:logging-interceptor:3.5.0'
    compile 'com.squareup.okhttp3:okhttp:3.4.2'
    compile 'com.squareup.okhttp3:logging-interceptor:3.4.2'
    compile 'com.squareup.picasso:picasso:2.5.2'
    compile 'com.mikhaellopez:circularimageview:3.0.2'
    compile 'com.amitshekhar.android:android-networking:0.3.0'
    compile 'com.amitshekhar.android:jackson-android-networking:0.3.0'
    compile 'net.danlew:android.joda:<IP_ADDRESS>'
    compile 'com.github.rubensousa:gravitysnaphelper:1.0'
    compile 'com.bartoszlipinski:viewpropertyobjectanimator:1.4.5'
    compile 'com.facebook.android:facebook-android-sdk:4.+'
    testCompile 'junit:junit:4.12'
    annotationProcessor 'com.jakewharton:butterknife-compiler:8.4.0'
    compile('com.twitter.sdk.android:twitter:2.3.1@aar') {
        transitive = true;
    }
}

apply plugin: 'com.google.gms.google-services'

That doesn't make it a library problem it just means your build system is broken in some way. Did you try a clean build?

Yes, I tried clean, also "Invalid cache/Restart", too. But, did not help

No action for us to take on this.


Scala Hadoop Enrich: process fails with AMI of 2.4.3+

https://groups.google.com/forum/#!topic/snowplow-user/Z992Kk3Df0E
Some kind of Java platform incompatibility?

2.4.8 is a dependency on jobflows with >256 steps

Updated ticket as this has been found to occur on 2.4.3, 2.4.5, 2.4.8. I've also created this ticket:
https://github.com/snowplow/iglu-scala-client/issues/24
My current thinking is that something in 2.4.3 updated the Jackson dependency, which is causing this code to break:
https://github.com/fge/jackson-coreutils/blob/master/src/main/java/com/github/fge/jackson/JsonLoader.java#L74

So 2.4.3 promotes to Java version to 7u60 (early access release):

http://www.oracle.com/technetwork/java/javase/2col/7u60-bugfixes-2202029.html

Here is the line that is throwing the exception:

https://github.com/snowplow/iglu-scala-client/blob/master/src/main/scala/com.snowplowanalytics.iglu/client/repositories/EmbeddedRepositoryRef.scala#L147

I have raised a support ticket with AWS to try and get more insights into what changed between 2.4.2 and 2.4.3...

This issue is being investigated by AWS now...

#1652 is the hopeful fix for this.

Update: #1652 wasn't the fix for this. The good news is that updating our code to Hadoop 2 seems to work - so we can bump the AMI version to 3.6, which does work!

Closing as a won't fix - there are just too many bugs in too many aspects of the 2.4.x series AMIs to make this achievable. See #1651 instead.


Alternative C API

This PR implements the alternative C API discussed here and here. The changes come in two commits:

the first commit (0aa20694383602cb69918fa13fa4b311d6669c0b) is a simple modification of the existing C API so that all structures are passed by address (not by value);

the second commit (d90d0a3b5f13c65f50309ea33571596d24e4c14a) implements a draft of the proposed alternative C API with:

a single opaque structure prima_context_t storing all the parameters,
a couple of functions (prima_context_create and prima_context_destroy to create this structure and, when no longer needed, destroy it as well as related resources),
a number of functions (mutators prima_context_set_... and accessors  prima_context_get_...) to set and retrieve all parameters.

All C examples compile and run fine with the first commit. Example are needed for the 2nd commit but it is mainly there for being discussed.
The two king of API can coexist. In fact the latter one is implemented on top of the former one and is intended to facilitate the writing of bindings in other languages without requiring to directly access C structures in these languages.

Silly me, I forgot to change the tests too (done in 7b35c05a61bde0540e36afce1c9817723141e824). I should have made 2 different PRs (one for passing structures by address, the other for the alternative API) sorry for that.

Thank you @emmt !
int prima_minimize(const prima_algorithm_t algorithm, const prima_problem_t *problem, const prima_options_t *options, prima_result_t *const result);

Why do we use pointers here for problem and options?

Why do we use pointers here for problem and options?

Because passing them by value is not necessary and is a waste of stack space. It is possible but rather unusual in C to pass structures by value (except maybe very small ones). The pointers of these are const so their contents is not supposed to be modified.

Then may I suggest
int prima_minimize(const prima_algorithm_t algorithm, const prima_problem_t *const problem, const prima_options_t *const options, prima_result_t *const result);

as neither the pointer itself nor its content is supposed to be changed in the fiction body?
Of course, any change to the pointer itself will be lost since itself is passed by value, but this will prevent the developers (ourselves, future ourselves, and others) from making mistakes when composing or modifying the implementation of this function. I had a discussion with @amontoison about it and this was the consensus.
Thank you.

Honestly, the const qualifier in function prototypes is only useful for arrays and pointers to indicate that the corresponding content is not modified by the called function. Otherwise, it indicates that the value of the argument (not the content at that address if it is an array or a pointer) is not modified which is irrelevant for the caller and may only be relevant for the optimizer. Modern optimizers can infer this themselves and const is then just a nuisance for the caller when he/she attempt to decode the meaning of the function prototype. To add to the confusion, the const qualifier can be before or after the type. Hence, to simplify the task of understanding the function prototype for the user, I usually restrict the use of const to the former case. But I'll adapt to the consensus...

Why do we use pointers here for problem and options?

Because passing them by value is not necessary and is a waste of stack space. It is possible but rather unusual in C to pass structures by value (except maybe very small ones). The pointers of these are const so their contents is not supposed to be modified.

Thanks for the explanation with stack space!
I understand now why it's more relevant to pass structures by pointer.
For the const, we should think of a compromise between preventing he developers from making mistakes but also the redeability of the header.
@emmt is more expert than me on C, we should probably follow its advice.
For the new C API, it looks good to me. 👍

To add to the confusion, the const qualifier can be before or after the type. Hence, to simplify the task of understanding the function prototype for the user, I usually restrict the use of const to the former case.

Then a user like me would need to check a documentation to make sure what the const really means, because, as you said, there are two different cases. If we use both, the user knows automatically that everything is supposed to be constant.


stderr: error: could not find repository from '.'; class=Repository (6); code=NotFound (-3)

Environment
Flutter: 3.7.12

sentry_flutter: 7.5.2
sentry_dart_plugin: 1.2.0

Steps to Reproduce

Configure Sentry in pubspec.yaml:

sentry:
  upload_debug_symbols: true
  project: vosbor-mobile
  org: vosbor-exchange-bv
  auth_token: XXXX
  wait_for_processing: true

Create new Flutter project
Run flutter build apk --obfuscate --split-debug-info=symbols
Run flutter packages pub run sentry_dart_plugin

Expected Result
It uploads debug symbols and doesn't complain about random things.
Actual Result
It successfully uploads symbols and I can see readable issues on Sentry's panel, but at the same time the command complains about some repository and fails the whole command, which messes with CI.
What is this repository? How can I fix this?

Full output
[❚❚❚❚❚❚❚❚❚❚❚❚❚❚❚❚❚❚❚❚❚❚] 0% reading config values..
Downloading sentry-cli from https://downloads.sentry-cdn.com/sentry-cli/2.17.5/sentry-cli-Darwin-universal to .dart_tool/pub/bin/sentry_dart_plugin/sentry-cli

Downloaded Sentry CLI binary checksum verification passed successfully (hash: XXXXX).

Sentry CLI downloaded successfully.
☑ reading config values
☑ validating config values
[❚❚❚❚❚❚❚❚❚❚❚❚❚❚❚❚❚❚❚❚❚❚] 18% uploading debug symbols..
includeSources is disabled, not uploading sources.

stderr:
stdout: > Found 65 debug information files
> Prepared debug information files for upload
> Uploaded 6 missing debug information files
> File processing complete:

     OK 5fc867f4-1791-fbcf-69d0-20a6d69dbca6 (app.android-arm.symbols; arm debug companion)
     OK bf4aa6bc-93cb-d970-31bb-8f1c70ef2ceb (app.android-arm64.symbols; arm64 debug companion)
     OK 8e504493-c779-358b-4c94-298242f84e77 (app.android-x64.symbols; x86_64 debug companion)
     OK bf4aa6bc-93cb-d970-31bb-8f1c70ef2ceb (app.so; arm64 library)
     OK 5fc867f4-1791-fbcf-69d0-20a6d69dbca6 (app.so; arm library)
     OK 8e504493-c779-358b-4c94-298242f84e77 (app.so; x86_64 library)

☑ uploading debug symbols

stderr:
stdout: Created release<EMAIL_ADDRESS>

uploadSourceMaps is disabled.

exitCode: 1
stderr: error: could not find repository from '.'; class=Repository (6); code=NotFound (-3)

Add --log-level=[info|debug] or export SENTRY_LOG_LEVEL=[info|debug] to see more output.
Please attach the full debug log to all bug reports.

stdout:
pub finished with exit code 1

@PawlikMichal25 thanks for raising.
can you run again with the log_level: true for more detailed logs?
@kamilogorek have you seen this already?

@PawlikMichal25 can you also try to commits: false?

@PawlikMichal25 the fca title is because of https://github.com/getsentry/sentry/issues/48334 and https://docs.flutter.dev/deployment/obfuscate#caveat
Before & after obfuscation and uploading symbol is the Flutter tooling itself, we just report stack traces as it is, if the tooling reports it differently, consider creating a repro case and raising an issue on https://github.com/dart-lang/sdk maybe?
I'll close the issue since the original question is resolved, for the later, if you think it's a sentry's symbolication issue, feel free to raise another one.


support alternate language servers in python.languageServer

currently there are only 3 options in python.LanguageServer: "Pylance", "Jedi" and "None". this isn't ideal for a couple of reasons:

if anyone wants to use an extension that provides an alternative language server, they have to set this setting to "None" to avoid conflicting with one of those two built in language servers, which is confusing to the user. they would expect their language server to just show up as an option in that list.
i want to be able to support jupyter notebooks in my language server, but i can't because there doesn't seem to be a way to do so without changing this hardcoded extension ID to my own extension ID and tricking it into thinking it's interfacing with pylance by implementing a PylanceApi in my extension. this would be fine, if it weren't for the fact that i'd have to fork vscode-python just to change one hardcoded constant. ideally my users of my language server shouldn't have to install two different extensions.

perhaps there could be a CustomLanguageServerApi interface similar to PylanceApi that extensions can implement and register as an option in python.languageServer.

after looking at how ruff supports jupyter notebooks, i think it's possible without this functionality, so i'll close this issue.


Webcambackground

i add new project about remove background with opencv

thanks for help me ,
i use it , very good , i love it

if u can show me more .


Kindly Add Support For Monochrome Theme ⚫⚪

Is your feature request related to a problem? Please describe.
Currently this plugin not supported monochrome theme
Describe the solution you'd like
Add monochrome theme generation support in plugin. please reference below link
Additional context
https://youtu.be/vnDhq8W98O4?t=843

Is this necessary? Or does Android monochrome-ize your colorful theme automaticaly?

yes it's necessary because a  website theme must be started in black and white theme. so they were show it then its important

Resolving as this is in-progress. Keep a look out for color fidelity/color match. It'll allow for lower chroma themes!

okok

@margeeta I don't think this was resolved - yes, you can use a monochrome color as your source color, but it still functions differently than the "monochrome" in color utilities


Disable EOL scylla repositories in k8s node setup image

K8s node setup image which was created 2 years ago was used in scylla-operator EKS example. This image was supposed to set up a RAID array, create XFS filesystem and mount it in desired location using helper scripts taken from this repository and from scylla image.
Image was based on Scylla 4.1 which some time ago ended it's life and it's repository was removed.
This cause failures for k8s image users becasue repository added in base image is no longer there.
Loaded plugins: fastestmirror, ovl
Determining fastest mirrors
 * base: download.cf.centos.org
 * epel: d2lzkl7pfhq30w.cloudfront.net
 * extras: download.cf.centos.org
 * updates: download.cf.centos.org
http://downloads.scylladb.com/rpm/unstable/centos/branch-4.1/2020-08-31T00%3A50%3A11Z/scylla/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.

 One of the configured repositories failed (Scylla for Centos 7 - x86_64),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=scylla ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable scylla
        or
            subscription-manager repos --disable=scylla

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=scylla.skip_if_unavailable=true

failure: repodata/repomd.xml from scylla: [Errno 256] No more mirrors to try.
http://downloads.scylladb.com/rpm/unstable/centos/branch-4.1/2020-08-31T00:50:11Z/scylla/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Traceback (most recent call last):
  File "/opt/scylladb/scripts/libexec/scylla_raid_setup", line 86, in <module>
    run('yum install -y mdadm xfsprogs')
  File "/opt/scylladb/scripts/scylla_util.py", line 340, in run
    return subprocess.check_call(cmd, shell=shell, stdout=stdout, stderr=stderr, env=scylla_env)
  File "/opt/scylladb/python3/lib64/python3.7/subprocess.py", line 363, in check_call
    raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['yum', 'install', '-y', 'mdadm', 'xfsprogs']' returned non-zero exit status 1.
RAID Array containing ['nvme0n1', 'nvme1n1'] not found. Creating...
Traceback (most recent call last):
  File "/opt/scylladb/scylla-machine-image/scylla_create_devices", line 194, in <module>
    get_disk_bundles()
  File "/opt/scylladb/scylla-machine-image/scylla_create_devices", line 183, in get_disk_bundles
    config_array(typemap[t], role[t], mdidx)
  File "/opt/scylladb/scylla-machine-image/scylla_create_devices", line 80, in config_array
    "--update-fstab"], check=True)
  File "/opt/scylladb/python3/lib64/python3.7/subprocess.py", line 512, in run
    output=stdout, stderr=stderr)
subprocess.CalledProcessError: Command '['/opt/scylladb/scripts/scylla_raid_setup', '--raiddev', '/dev/md0', '--disks', '/dev/nvme0n1,/dev/nvme1n1', '--root', '/mnt/hostfs/mnt/raid-disks/disk0', '--volume-role', 'all', '--update-fstab']' returned non-zero exit status 1.
Traceback (most recent call last):
  File "/opt/scylladb/scylla-machine-image/scylla_k8s_node_setup", line 65, in <module>
    run('/opt/scylladb/scylla-machine-image/scylla_create_devices --scylla-data-root {}'.format(root_disk))
  File "/opt/scylladb/scripts/scylla_util.py", line 340, in run
    return subprocess.check_call(cmd, shell=shell, stdout=stdout, stderr=stderr, env=scylla_env)
  File "/usr/lib64/python3.6/subprocess.py", line 311, in check_call
    raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['/opt/scylladb/scylla-machine-image/scylla_create_devices', '--scylla-data-root', '/mnt/hostfs/mnt/raid-disks/disk0']' returned non-zero exit status 1.

Because scylla_create_devices script was moved and changed to the point it's no longer working with k8s node setup, an old version was brought back into the k8s directory just for AWS.
GCE image is not used anywhere, hence I fixed it just for AWS.
This image is going to be removed soon, as different solution for disk setup is coming to scylla-operator.
This PR is just a hot-fix to users which used this image in the past and now are stuck.

@yaronkaikov PTAL

@yaronkaikov PTAL, we need this image published to unblock our users and avoid a workaround in QA code.

@yaronkaikov ping

@zimnx Sorry for the delay , missed this notification

no worries, thanks for merging. Would you mind pushing this image to docker hub? I don't have permissions there.


Transaction Resolver resolves InTransaction into IntraTransaction for Existing RP2 Input

What?
When using the ODS plugin with existing data, the resolver creates IntraTransactions from Buy InTransactions that have fees. For some reason, this doesn't affect buys without fees.
Temporary Workaround
Replacing the unique ids from the buys in the original ODS with __unknown prevents the resolver from matching the transactions.

The resolver turns a buy/in transaction into an intra one if there is also an out transaction with a unique id matching the buy/in transaction. Can you search through your debug logs for the unique id of the buy/in transaction and see if it occurs in an out transaction as well?

Yeah, there are pairs of transactions in/out that share the same transaction id but are on the same exchange and have different assets. Basically, when I buy BTC, I do it in USDT, so there is a BTC buy, InTransaction, and a USDT sell, OutTransaction that share the same unique id. This isn't a problem when I use the rest API, but for some reason when using the existing RP2 plugin, it combines these transactions. They are on the same exchange and use different assets so this should never occur. Putting some kind of filter on the resolver would prevent this from happening. I'm just not sure why it happens on existing rp2 input.
I have a strange feeling we've had this bug before.

That suggests there may be a bug in the way the plugin for that exchange (which one btw?) is assigning unique ids. Maybe the raw data contains other fields (or combination of fields) that can be used as unique ids for in/out transactions?

So, the original plugin is okay. If I run the Binance REST API plugin, it works fine. Everything is okay.
It's just when I take the output of that run in ODS form ( and use the existing RP2 data plugin that reads previously generated ODS files in) and feed it back into dali-rp2 is when things cause trouble. It generates IntraTransactions where the to and from exchanges are equal. Binance to Binance, Can you think of a situation where the resolver should do that?
I guess my point is the resolver should never generate an IntraTransaction where the from and to exchanges are equal. That seems like a bug to me. Especially if it is generating it from two transactions with completely different assets.

Thanks for clarifying. A few comments:

it is possible to have a legitimate  intra transaction to and from the same wallet/exchange (e.g. if you send some coins to an external address and that address is actually a receive address for the source wallet/exchange): this is typically used to consolidate utxos (on wallets);
I agree that the resolver should not try to match two transactions that have same unique id but different assets (but same asset is OK as mentioned above): we should fix that. Could you attach a small input file to repro the issue (unless you're planning on fixing it yourself)?
I guess I don't understand what is the difference between running the Binance rest plugin vs the feeding back the ODS: isn't the data the same? If not what is the difference?


Bookstore Logical Model Design

What changes are you trying to make? (e.g. Adding or removing code, refactoring existing code, adding reports)
Designed a logical model for a bookstore.
What did you learn from the changes you have made?
ERD design, normalized tables, and slowly changing dimensions.
Was there another approach you were thinking about making? If so, what approach(es) were you thinking of?
N/A
Were there any challenges? If so, what issue(s) did you face? How did you overcome it?
N/a
How were these changes tested?
N/A
A reference to a related issue in your repository (if applicable)
N/A
Checklist

[x ] I can confirm that my changes are working as intended

Assignment Marked, Passed.


Add Radial_Velocity table

We have an ingest_radial_velocity function ready to go. Let's add the table!

@kelle Don't we already have some example quantity tables? My gut feeling is that not everyone would have radial velocities in their own databse.

Hmm, this raises a good topic which I don't think we've discussed explicitly recently -- how do we want to decide what tables to include in the template.  At the moment, I'm inclined to include more tables than less...it's easier for a user to remove/modify tables than it is to make up their own from scratch.  The more tables we have defined, the more likely databases will be compatible with each other.  For example, I think it would make sense for the template to have both a radial velocity AND redshift table.

Partially addressed by #86 .  Still will need to add tests from #72


Picking support

Implement raycast picking similar to Cesium for Unreal / Unity so that it's possible to do things like click an OSM building and view its metadata.
Requires physics support first: https://github.com/CesiumGS/cesium-omniverse/issues/153.

Taking a look at this and noting that it depends on #153 . Do you see using https://github.com/CesiumGS/cesium-native/pull/777 as an alternative?

Do you see using https://github.com/CesiumGS/cesium-native/pull/777 as an alternative?

Potentially. We should check out omni.kit.raycast.query first which doesn't depend on physics. Not sure if it works with Fabric yet.

Raycasting request from the forum: https://community.cesium.com/t/ground-detection-in-cesium-for-omniverse/29819/2

@timoore do you know if the ray cast query returns the path of the Fabric prim? If that's not possible we'll likely need to postpone this feature until that capability is supported.

@timoore do you know if the ray cast query returns the path of the Fabric prim? If it doesn't we'll likely need to postpone this feature until that capability is supported.

The raycast query result has methods for get_target_usd_path(), instance_id(), and primitive_id(). I don't know if that is all completely specific to USD or would return sensible results for a Fabric prim.


Rename to determineHTTPRequestMethod

Fix #348

Codecov Report

Merging #349 (3b8b542) into main (035b86a) will increase coverage by 0.00%.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##             main     #349   +/-   ##
=======================================
  Coverage   96.38%   96.38%
=======================================
  Files          55       55
  Lines        3206     3208    +2
=======================================
+ Hits         3090     3092    +2
  Misses         76       76
  Partials       40       40

Impacted Files
Coverage Δ

dtmsvr/trans_status.go
97.48% <100.00%> (+0.03%)
:arrow_up:

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


Preliminary project metadata model

User Story
As a Data Sponsor, I need the metadata I entered into the new project request form to be formatted and supplemented with defaults and/or system-generated values automatically, and then sent to the system administrators automatically, so that I can easily submit my requests and not have to worry about unfamiliar technical details.
Notes
Following up on #170 and #195, I want to be explicit about the expectations for project metadata records. The other issues related to #113 lay out specific requirements for each metadata field in this preliminary phase, according to the TigerData Standard Metadata Schema v0.5. Right now, the only required early adopter field that is not a part of the form is "Project ID", which is system-generated, following #257. As we move forward, however, there will be more required fields, along with some optional fields, that have default and/or system-generated values. The standard metadata schema will also evolve over time. So we need to be careful to establish an adaptable, extensible framework modeling project metadata.
I don't have requirements for how exactly your database is set up to be adaptable and extensible. For me right now, the deliverable that will help me see that we are modeling metadata in accordance with the roadmap from the Metadata Working Group is a JSON or XML file produced for each submitted new project request.
(This issue supersedes and replaces #258.)
Completion Criteria

[ ] Upon submission and validation, the values entered in the new project request form are combined with the system-generated Project ID (DOI) to compose a complete preliminary project metadata record
[ ] The preliminary project metadata record can be formatted as XML for Mediaflux commands
[ ] The preliminary project metadata record can be formatted as JSON schema in addition (human readable)
[ ] .xml on the record show page shows the Mediaflux XML
[ ] .json on the record show page shows the JSON
[ ] The xml file should be available as an attachment to the email
[ ] The json file should be available as an attachment to the email
[ ] During the preliminary testing phase, a XML version of the metadata record for each requested new project is emailed to the PO "Create this new project. see attached XML". The email has two attachments XML & JSON

Hey team! Please add your planning poker estimate with Zenhub @JaymeeH @jrgriffiniii @hectorcorrea

Please add your planning poker estimate with Zenhub @leefaisonr


Run tests

Run the unit test once https://github.com/bodil/purescript-test-unit/pull/19 is resolved

Can only be updated if https://github.com/slamdata/purescript-markdown works with PS 0.9

Fixed via c07a58730394013364b28892bde905d4c16dde4b


Bumping go version to 1.20.10 in v0.57.x line

What this PR does / why we need it:
Bumping go version to 1.20.10
Which issue(s) this PR fixes:

Fixes #
Does this PR introduce a user-facing change?

Additional Notes for your reviewer:
Review Checklist:

[ ] Follows the developer guidelines
[ ] Relevant tests are added or updated
[ ] Relevant docs in this repo added or updated
[ ] Relevant carvel.dev docs added or updated in a separate PR and there's
a link to that PR
[ ] Code is at least as readable and maintainable as it was before this
change

Additional documentation e.g., Proposal, usage docs, etc.:

/cherry-pick 0.55.x


File linker-defs.h does not have a path to file offsets.h.

Describe the bug
When I tried to build an application using the T2 topology, I received an error.
When I specified the full path to the offsets.h file, the application was built successfully.
To Reproduce
4. See error

Expected behavior
specify the path as indicated in the lines above in the linker-defs.h file.
Environment (please complete the following information):

OS: Windows
Toolchain Zephyr SDK 0.16.4
Zephyr version: 3.5.99, build: zephyr-v3.5.0-3682-gd7af6f371034

Will you please provide more details about how to reproduce?

Several people reporting the same error over at DevZone: https://devzone.nordicsemi.com/f/nordic-q-a/106046/offsets-h-no-such-file-or-directory. I have not yet been able to figure out what causes this.
A mentioned workaround is to tell west to use make instead of ninja.
Also some people mention that the error is apparent in the first build, but that it works again on a subsequent builds.

Update: One of the users in the devzone ticket fixed this by including "#include <zephyr/drivers/i2c.h>" into the .cpp file instead of header file. Other users confirm that this fix worked.

I got the same thing yesterday on a fresh ncs installation.
C:/ncs/v2.5.1/zephyr/include/zephyr/linker/linker-defs.h:26:10: fatal error: offsets.h: No such file or directory
26 | #include <offsets.h>
|          ^~~~~~~~~~~
compilation terminated.
I fixed it in both cases with this line:
#include <../subsys/testsuite/ztest/include/zephyr/offsets.h>
Building a free-standing (T3) application.
C:/ncs/v2.5.1/zephyr/include/zephyr/linker/linker-defs.h:26:10: fatal error: offsets.h: No such file or directory
   26 | #include <offsets.h>
      |          ^~~~~~~~~~~
compilation terminated.
[8/369] Building C object drivers/display/CMakeFiles/..__..__..__Projects__Chips__test-origin-tft__drivers__display.dir/display_ili9xxx.c.obj
FAILED: drivers/display/CMakeFiles/..__..__..__Projects__Chips__test-origin-tft__drivers__display.dir/display_ili9xxx.c.obj
C:\ncs\toolchains\c57af46cb7\opt\zephyr-sdk\arm-zephyr-eabi\bin\arm-zephyr-eabi-gcc.exe -DKERNEL -DLV_CONF_INCLUDE_SIMPLE=1 -DLV_CONF_PATH=C:/ncs/v2.5.1/zephyr/modules/lvgl/lv_conf.h -DNRF52840_XXAA -DPICOLIBC_INTEGER_PRINTF_SCANF -D_FORTIFY_SOURCE=1 -D_POSIX_C_SOURCE=200809 -D__LINUX_ERRNO_EXTENSIONS__ -D__PROGRAM_START -D__ZEPHYR__=1 -IC:/ncs/v2.5.1/zephyr/include -Izephyr/include/generated -IC:/ncs/v2.5.1/zephyr/soc/arm/nordic_nrf/nrf52 -IC:/ncs/v2.5.1/zephyr/lib/posix/getopt/. -IC:/ncs/v2.5.1/zephyr/soc/arm/nordic_nrf/common/. -IC:/ncs/v2.5.1/nrf/include -IC:/ncs/v2.5.1/nrf/tests/include -IC:/ncs/v2.5.1/modules/hal/cmsis/CMSIS/Core/Include -IC:/ncs/v2.5.1/zephyr/modules/cmsis/. -IC:/ncs/v2.5.1/modules/hal/nordic/nrfx -IC:/ncs/v2.5.1/modules/hal/nordic/nrfx/drivers/include -IC:/ncs/v2.5.1/modules/hal/nordic/nrfx/mdk -IC:/ncs/v2.5.1/zephyr/modules/hal_nordic/nrfx/. -IC:/ncs/v2.5.1/modules/lib/gui/lvgl/src -IC:/ncs/v2.5.1/zephyr/modules/lvgl/. -IC:/ncs/v2.5.1/modules/debug/segger/SEGGER -IC:/ncs/v2.5.1/modules/debug/segger/Config -isystem C:/ncs/v2.5.1/nrfxlib/crypto/nrf_cc310_platform/include -fno-strict-aliasing -Os -imacros C:/Projects/Chips/test-origin-tft/build/zephyr/include/generated/autoconf.h -fno-printf-return-value -fno-common -g -gdwarf-4 -fdiagnostics-color=always -mcpu=cortex-m4 -mthumb -mabi=aapcs -mfp16-format=ieee --sysroot=C:/ncs/toolchains/c57af46cb7/opt/zephyr-sdk/arm-zephyr-eabi/arm-zephyr-eabi -imacros C:/ncs/v2.5.1/zephyr/include/zephyr/toolchain/zephyr_stdint.h -Wall -Wformat -Wformat-security -Wno-format-zero-length -Wno-pointer-sign -Wpointer-arith -Wexpansion-to-defined -Wno-unused-but-set-variable -Werror=implicit-int -fno-pic -fno-pie -fno-asynchronous-unwind-tables -ftls-model=local-exec -fno-reorder-functions --param=min-pagesize=0 -fno-defer-pop -fmacro-prefix-map=C:/Projects/Chips/test-origin-tft=CMAKE_SOURCE_DIR -fmacro-prefix-map=C:/ncs/v2.5.1/zephyr=ZEPHYR_BASE -fmacro-prefix-map=C:/ncs/v2.5.1=WEST_TOPDIR -ffunction-sections -fdata-sections --specs=picolibc.specs -D_POSIX_THREADS -std=c99 -MD -MT drivers/display/CMakeFiles/..__..__..__Projects__Chips__test-origin-tft__drivers__display.dir/display_ili9xxx.c.obj -MF drivers\display\CMakeFiles\..__..__..__Projects__Chips__test-origin-tft__drivers__display.dir\display_ili9xxx.c.obj.d -o drivers/display/CMakeFiles/..__..__..__Projects__Chips__test-origin-tft__drivers__display.dir/display_ili9xxx.c.obj -c ../drivers/display/display_ili9xxx.c
In file included from C:/ncs/v2.5.1/zephyr/include/zephyr/app_memory/app_memdomain.h:9,
                 from C:/ncs/v2.5.1/zephyr/include/zephyr/rtio/rtio.h:31,
                 from C:/ncs/v2.5.1/zephyr/include/zephyr/drivers/spi.h:29,
                 from ../drivers/display/display_ili9xxx.h:13,
                 from ../drivers/display/display_ili9xxx.c:9:
C:/ncs/v2.5.1/zephyr/include/zephyr/linker/linker-defs.h:26:10: fatal error: offsets.h: No such file or directory
   26 | #include <offsets.h>
      |          ^~~~~~~~~~~
compilation terminated.

Thank you for reporting this. However - unless you are able to reproduce this issue with upstream Zephyr main - please report issues with the nRF Connect SDK (NCS) on the Nordic Semiconductor DevZone.

Eh... command line or Kconfig list to reproduce would be nice, huh?
I have tried building Hello World adding offsets.h to main and flash_shell adding the offsets.h to soc_nrf_flash.c. Both built for nrf52840dk_nrf52840 with the Zephyr at a9779eca400e67e2eebfc1f774eb4186efdc7a96.
Both built with -DCONFIG_I2C=y, and looks ok.
The example, that is supposed to not build on sdk-nrf, but is fine to build with the Zephyr:
https://github.com/robertpaananen/mre_bug_offsets_h
west build -d builds/nrf -b nrf52840dk_nrf52840 ../ncs1/mre_bug_offsets_h/ -DCONFIG_I2C=y

fails, but when you re-try build it builds fine.
Seems that the offsets.h gets generated after the file, triggering the problem, is compiled.

I see the same issue on SDK 0.16.9, Zephyr v3.6.0 with board nucleo_f767zi. (Using SPI and CAN)
However it is not consistent. Sometimes it builds from a clean build folder without issues, other times it complains about the missing <offsets.h>. About 50/50. Building the second time always succeeds.
Because of this random behavior and that some report that it helps to add includes, could it be that this is caused by the parallel nature of ninja and that it sometimes manage to create offsets.h in time?

Would there be a missing dependency somewhere in some CMakeLists.txt? If the build is parallel, one file could be built before another, and depending on the order, there could be a missing dependency or not?
A manual workaround is to generate the offsets.h explicitly:
~/zephyrproject$ cmake --build build --target offsets_h
[1/1] Generating include/generated/offsets.h
~/zephyrproject$

I am also seeing this with the following:

Cmake 3.29.2
Zephyr Build: build: v3.6.0-2750-g6a497ac3735c
Zephyr SDK: 0.16.5

It occurs anytime you perform a pristine build or have otherwise nuked the build directory. If you build again after the failure (without the pristine flag), the process will continue as normal. I believe offsets.h is generated by the Zephyr SDK, and therefore is not built early enough in the compiling process. Hence, the failure upon first clean builds but success after continuing the failed build.
Looking a the offsets.h file (in your build dir/zephyr/include/generated), there are no external includes so ideally, it should be one of the first built with a gated build mechanism (@eriksage, I agree it is the parallelism causing issues).

It occurs anytime you perform a pristine build or have otherwise nuked the build directory.

Please provide concise steps for how to reproduce this (list the exact commands used along with full error output). I am not able to reproduce this just by doing a pristine build.

I looked into this because it's been causing us strife for quite a while. The build process is confounding enough without worrying about intermittent tooling issues like this.
I found that according to the build system docs the offsets.h file is created during pre-build. Critically that comes after the "Configuration Phase" as the first step during the "Build Phase". So this is under the control of either make or ninja.
In my case it is ninja, so I tracked down my build.ninja "makefile". Of course, it is 4.3MB and ninja run builds without inter-dependencies in parallel, so what could possibly go wrong?
I ran ninja -t deps and ninja -t graph to get a view into the dependency tree. The relevant build target was easy to spot in the graph:

So to understand why it's not getting prioritised we simply need to look at it in context within the overall build. I've drawn a big red box around the previous screenshot to make it easy to spot.

Yeah. So I'm still looking into it...

Oh man, that was easy.
Everything that was included using target_sources had dependencies like zephyr_generated_headers. So did drivers I'd added using add_subdirectory, but which have a path already known to Zephyr, like input drivers. They get a line in the build.ninja file like:
cmake_object_order_depends_target_drivers__input: phony || [...] zephyr/zephyr_generated_headers
However, drivers in an unknown path, which are included in my CMakeLists.txt file using a combination of add_subdirectory and target_link_library, get no such dependency. I found an old thread which got me on the right track.
All I had to do, was add add_dependencies(LIBRARY_NAME, offsets_h) to my CMakeLists.txt file, and clean builds are now fast and successful.
If you're following the Zephyr library naming convention, as I am, that would be something like add_dependencies(drivers__fuel_gauge__max17043 offsets_h), or in the OP's case, maybe add_dependencies(drivers__display__display_ili9488 offsets_h).
I'm not sure why this dependency isn't included transitively already...

CC: @tejlmand

@hraftery Using zephyr_library_add_dependencies(offsets_h) worked for me


Simplify target name handling

There is already a mechanism for this, no need to #ifdef every target.
Just stringify TARGET_NAME and there you have it.
Please review @kFYatek

https://forums.mbed.com/t/is-the-target-name-available-as-a-macro/8340

@JanneKiiskila Thanks for the PR. It looks sensible, however please look at my suggestion.@JanneKiiskila Thanks for the PR. It looks sensible, however please look at my suggestion.


Fixes Broken Upsert

resolve #49

Fixes CouchDb upsert function. There were two issues with this  function:  the upsert function would always try to insert. Also it would take an 'id' property from a found document and merge it to the update document. But CouchDb doesn't have 'id', it has '_id'.

Codecov Report

Merging #50 into master will increase coverage by <.01%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master      #50      +/-   ##
==========================================
+ Coverage   99.79%   99.79%   +<.01%
==========================================
  Files          18       18
  Lines         490      491       +1
  Branches       17       17
==========================================
+ Hits          489      490       +1
  Misses          1        1

Impacted Files
Coverage Δ

lib/couchdb/index.js
97.95% <100%> (+0.04%)
:arrow_up:

Continue to review full report at Codecov.

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


[Discussion] Azure Functions Runtime release 3.0.14111

Discussion issue for the Azure Functions runtime release 3.0.14111: https://github.com/Azure/azure-functions-host/releases/tag/v3.0.14111

See https://github.com/Azure/app-service-announcements-discussions/issues/174 for breaking changes related to this release.

Issue found in this release: https://github.com/Azure/azure-webjobs-sdk-extensions/issues/655.
Replaced by hotfix 3.0.14191: #178


Provide code for example card configuration

Version of the custom_component

aa3e219 (according to HACS this is the latest available version)
Describe the bug
Adding the sensor in a sensor card leads to a time output like 2019-12-06T16:53:10.000+01:00 instead of in 7 minutes.
log

Add your logs here.

Please provide a full example of which card to use or with settings need to be changed to get a relative time shown instead of the absolute value.

Solved with this code:
type: entities
entities:
  - entity: sensor.66a_next_departure
    hours_to_show: 24
    name: 66A Reumannplatz
    format: relative


bring the edit button back

Edit is one of the most used actions in the sidekick, and user sessions have shown that "hiding" it one more click away as the source item in the env switcher is not the most intuitive pattern. So we decided to bring back the edit button in addition to the source item in the env switcher.

:tada: This issue has been resolved in version 2.3.0 :tada:
The release is available on:

GitHub release
v2.3.0

Your semantic-release bot :package::rocket:


feat(api): add full word searching

refactor existing search mechanism into genericSearch

It's a minor


GCP: URL Maps

URL Maps URL Maps are one component of many that make up Load Balancing in GCP.
This uses the url maps API: https://cloud.google.com/compute/docs/reference/rest/v1/urlMaps

Blocks

#11

branch: feature/url-maps

gyro up url-maps.gyro creates http load balancer, which comprises of url-map, backend-service, backend-bucket, forwarding-rule, target-http-proxy. You can find resources created via advanced mode in the load balancer page in the console.
resources can be created and deleted.
update needs to be implemented.
finder needs to be implemented.
javadocs need to be cleaned up.

There's another branch feature/url-maps-extra that contains more data structures to cover other  features than just http, but functions still need to be implemented.


Never update the local text while the user is typing

User types in the browser
The editor sends some text (like in #180)
The browser overrides whatever the user types with what the editor sends.

This is a mistake. If you're typing somewhere, that's the only version that matters. External messages should be ignored. I attempted to fix this with faa5a8d8ea744907b1f968b915c34f30e1dd96a7 but it caused #181.
This applies to both parts (browser or editor) but it's probably easier to avoid both issues in the browser:

do not echo received text back to the editor (I think this is already done)
ignore text from the editor while the field is focused

do not echo received text back to the editor (I think this is already done)

I can confirm.  All the subsequent edits in the editor are shown by sent, and we can see that there are no got corresponding to the sent, i.e. the browser doesn't echo back the text.

Thank you! As a solution for this issue, I think an easy fix would be to ignore events received within the next 500ms of a native input (which the browser extension already detects and handles correctly)
Could be as easy as:
// on verified input
clearTimeout(localEditTimer)
localEditTimer = setTimeout(() ={localEditTimer = false}, 500)

#
// on received input
if (localEditTimer) return

The alternative would be to constantly keep track of the browser’s focus state in the background page so that it’s available synchronously when GT received a server event.

I am a total noob in JS, so as far as I understood, it implements a timeout, and rejects everything it receives till the timeout expires.
if that's true, then the messages that come after the 500ms timeout shall still cause the issue!
But, overall, I still think that this is not a valid issue. The extension does what it is meant to do according to the protocol. Receive the WS message and change the text field accordingly.
I personally think the issue of not echoing the sent text is the responsibility of the editor plugin. But I can't speak for other plugin's authors.

I mean, you’re not wrong.
Maybe the extension should highlight this editor mistake on the testing page. If it receives a message identical to the one just sent, show a notification.
This way it would be easier for editor plugin authors to find and solve their issues.

BTW, I just tried to reproduce #180, but couldn't see the effect. Is there any kind of logging facility available to investigate?
Also, could you please check if #180 is still happening?

There should be some logging in the background, but I don’t remember exactly if it makes this visible.
This usually isn’t a problem with short text because it’s quick enough that the content still matches, but if you use longer content and type fast in the browser you’ll see that some keypresses will be lost/overridden.

if you use longer content and type fast in the browser you’ll see that some keypresses will be lost/overridden.

Ah, right! :facepalm:
Tried with longer content, and yes, it occurs.


Render left-most menu for new editor

[x] get latest CSS (unless cartocss is ready?)
[x] static markup is good enough for now
[x] remove the left-most menu rendered by dashboard - awaits https://github.com/CartoDB/deep-insights.js/issues/89

Those points are already implemented, so closing it :dancer:.


Cannot find module 'node:os' in @azure/logger dependency of @azure/identity

Package Name: @azure/identity
Package Version: ^4.2.0
Operating system: Ubuntu
[x] nodejs

version: 20.x

[ ] browser

name/version:

[ ] typescript

version:

Is the bug related to documentation in

[ ] README.md
[ ] source code documentation
[ ] SDK API docs on https://docs.microsoft.com

Describe the bug
Using the latest version of @azure/identity in node js code is breaking with the error: Cannot find module 'node:os'. From the stack trace it looks like the bug is coming from dependency of the identity package on @azure/logger package. Full stack trace:
##[error]Error: Cannot find module 'node:os'
    at Function.Module._resolveFilename (internal/modules/cjs/loader.js:636:15)
    at Function.Module._load (internal/modules/cjs/loader.js:562:25)
    at Module.require (internal/modules/cjs/loader.js:692:17)
    at require (internal/modules/cjs/helpers.js:25:18)
    at Object.<anonymous> (.<redacted>/node_modules/@azure/logger/dist/commonjs/log.js:7:19)
    at Module._compile (internal/modules/cjs/loader.js:778:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:789:10)
    at Module.load (internal/modules/cjs/loader.js:653:32)
    at tryModuleLoad (internal/modules/cjs/loader.js:593:12)
    at Function.Module._load (internal/modules/cjs/loader.js:585:3)

To Reproduce
Steps to reproduce the behavior:

Add the following dependency in package.json:

"dependencies": {
    ...
    "@azure/identity": "^4.2.0",
    ...
}

Expected behavior
Package should work without failing
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
Add any other context about the problem here.

Thanks for looking into it! I tested the command you gave, and it is working in my local machine with Node 20. So, I retried running it in our ADO pipeline and weirdly it is still failing with the same error. The Node install task in the pipeline is claiming it successfully installed Node 20 before running our code, but maybe there is something going wrong in it. I'll log the node version in the pipeline and see what version is getting installed.

Sounds good - going to mark this resolved for now but feel free to unresolve if you still suspect an issue with the SDK

/unresolve
I am getting the same issue with
node version : v18.20.3
azure identity version : ^4.2.0
Error: Cannot find module 'node:os'
    at Function.Module._resolveFilename (internal/modules/cjs/loader.js:636:15)
    at Function.Module._load (internal/modules/cjs/loader.js:562:25)
    at Module.require (internal/modules/cjs/loader.js:692:17)
    at require (internal/modules/cjs/helpers.js:25:18)
    at Object.<anonymous> (/node_modules/@azure/logger/dist/commonjs/log.js:7:19)
    at Module._compile (internal/modules/cjs/loader.js:778:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:789:10)
    at Module.load (internal/modules/cjs/loader.js:653:32)
    at tryModuleLoad (internal/modules/cjs/loader.js:593:12)
    at Function.Module._load (internal/modules/cjs/loader.js:585:3)

Can you help to resolve this issue?


Part 3 - Async Compaction - Track fileIds with pending compaction in FileSystemView to provide correct API semantics

Track fileIds with pending compaction in FileSystemView to provide correct API semantics

@n3nash : This PR takes care of correctly tracking fileIds which have pending (inflight + requested) compactions in file-system view to provide correct functionality in FileSystemView APIs.

@n3nash : ready for review
cc @vinothchandar

@n3nash: Addressed review comments. Please take one more pass when you get a chance.

Committed as part of Consolidated diff


MWPW-138943  POC Integration test

Add pilot tests for accordian, merch card, and review blocks
Accordian and merch card blocks use screenshot verification
Review  block uses action and element verification
Work around CORS using page route

To do:

Eliminate unnecessary components and improve stability
Add tests to a GitHub Actions workflow
Cover more blocks

Tu run integration tests on Chromium only:
npm run int

To run integration tests on 3 browsers:
npm run int3

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

Comparison is base (f095a63) 99.40% compared to head (f940d7b) 99.40%.

Additional details and impacted files
@@           Coverage Diff           @@
##            stage     #496   +/-   ##
=======================================
  Coverage   99.40%   99.40%
=======================================
  Files          26       26
  Lines        2878     2878
=======================================
  Hits         2861     2861
  Misses         17       17

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


lint use of json('null')

After seeing this a bit in bicep (mostly converted json) I've not found a place where null shouldn't be used instead of json('null').

@bmoore-msft So you're saying that all places that use 'null' should actually be json('null') instead? Why is that?
Also, are you saying that's how it should like in an actual Bicep file? Or on the json output file after you Bicep Build the file?

@ucheNkadiCode -- I think brian is saying the opposite. If we see json('null') used, we should throw a linter warning and quick fix it to simply null

yes, thanks for clarifying


Update mysql support

Closes #7
Closes #8
Solution inspired by https://github.com/typeorm/typeorm/blob/ff28aad27958ef7763a305982f70caeb611f2448/src/commands/MigrationGenerateCommand.ts#L120

This is great! Awesome work -- it's working great for us.