Update dependency Azure.Messaging.EventGrid to v4.24.0

This PR contains the following updates:

Package
Type
Update
Change

Azure.Messaging.EventGrid (source)
nuget
minor
4.22.0-beta.1 -> 4.24.0

Release Notes

Azure/azure-sdk-for-net (Azure.Messaging.EventGrid)
v4.24.0
4.24.0 (2024-04-09)
Features Added

Added new Communication events.

v4.23.0
4.23.0 (2024-03-11)
Features Added

Added API Center events.

v4.22.0
4.22.0 (2024-02-12)
Features Added

Added new Storage Task Assignment system events.
Added new AVS system events.
Added Metadata property to AcsChatThreadCreatedEventData system event.

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

Namespaces are not out of beta versions yet.

 You will get a PR once a newer version is released. To ignore this dependency forever, add it to the ignoreDeps array of your Renovate config.
If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.


Remove default resource limits

We want to avoid a default configuration which can lead to pods crashlooping because they run into memory limits
Follow-up for #24
Checklist

[x] PR contains a single logical change (to build a better changelog).
[x] Categorize the PR by setting a good title and adding one of the labels:
bug, enhancement, documentation, change, breaking, dependency
as they show up in the changelog.
[x] Link this PR to related issues or PRs.

We could potentially leave the CPU limits


ZooKeeperExceptions are not exceptions anymore

We get network issues quite often in our environment, so I set up an alert which fires when ZooKeeperExceptions in system.events increases. After upgrading to 1.1.54380 it increases by a few hundred every 5 minutes.
The only messages about ZooKeeper in logs are these:
<Debug> db.table (StorageReplicatedMergeTree): Removing 1 old parts from ZooKeeper
<Debug> db.table (StorageReplicatedMergeTree): Removed 1 old parts from ZooKeeper. Removing them from filesystem.

It seems that the behaviour was changed in 1.1.54371.
Is this a bug or a feature?

The issue is clearly visible on graphs (from the random server):

Looks like it is better after upgrade to the latest revision.

But the issue still exists. There are more exceptions on the graph that in logs.

It is normal.
It happens in two locations:
#0  ZooKeeperImpl::Exception::Exception (this=0x452b9f280, msg=..., code=-110) at ../dbms/src/Common/ZooKeeper/ZooKeeperImpl.cpp:274
#1  0x0000000005443423 in zkutil::KeeperMultiException::KeeperMultiException (this=0x452b9f280, code=-110, requests=..., responses=...) at ../dbms/src/Common/ZooKeeper/ZooKeeper.cpp:837
#2  0x0000000005443a28 in zkutil::KeeperMultiException::check (code=-110, requests=..., responses=...) at ../dbms/src/Common/ZooKeeper/ZooKeeper.cpp:854
#3  0x0000000005443aaf in zkutil::ZooKeeper::multi (this=<optimized out>, requests=...) at ../dbms/src/Common/ZooKeeper/ZooKeeper.cpp:489
#4  0x000000000501f893 in DB::EphemeralLockInZooKeeper::EphemeralLockInZooKeeper (this=0x7f1747261e80, path_prefix_=..., temp_path=..., zookeeper_=..., precheck_ops=0x7f1747261d30)
    at ../dbms/src/Storages/MergeTree/EphemeralLockInZooKeeper.cpp:29
#5  0x0000000004fd79bf in DB::StorageReplicatedMergeTree::allocateBlockNumber (this=0x14d09610, partition_id=..., zookeeper=..., zookeeper_block_id_path=...) at ../dbms/src/Storages/StorageReplicatedMergeTree.cpp:3453
#6  0x00000000050b8cc9 in DB::ReplicatedMergeTreeBlockOutputStream::commitPart (this=this@entry=0x1ae763670, zookeeper=..., part=..., block_id=...) at ../dbms/src/Storages/MergeTree/ReplicatedMergeTreeBlockOutputStream.cpp:214
#7  0x00000000050bc08a in DB::ReplicatedMergeTreeBlockOutputStream::write (this=0x1ae763670, block=...) at ../dbms/src/Storages/MergeTree/ReplicatedMergeTreeBlockOutputStream.cpp:160
#8  0x0000000005200e13 in DB::PushingToViewsBlockOutputStream::write (this=0x60cb4ca40, block=...) at ../dbms/src/DataStreams/PushingToViewsBlockOutputStream.cpp:62
#9  0x0000000005185098 in DB::AddingDefaultBlockOutputStream::write (this=0x18af00790, block=...) at ../dbms/src/DataStreams/AddingDefaultBlockOutputStream.cpp:73
#10 0x0000000005206168 in DB::SquashingBlockOutputStream::finalize (this=this@entry=0x910fe3350) at ../dbms/src/DataStreams/SquashingBlockOutputStream.cpp:30
#11 0x00000000052063f1 in DB::SquashingBlockOutputStream::writeSuffix (this=0x910fe3350) at ../dbms/src/DataStreams/SquashingBlockOutputStream.cpp:50
#12 0x0000000002dba482 in DB::TCPHandler::processInsertQuery (this=this@entry=0x401bc6000, global_settings=...) at ../dbms/programs/server/TCPHandler.cpp:309
#13 0x0000000002dba9d7 in DB::TCPHandler::runImpl (this=this@entry=0x401bc6000) at ../dbms/programs/server/TCPHandler.cpp:163
#14 0x0000000002dbb7db in DB::TCPHandler::run (this=0x401bc6000) at ../dbms/programs/server/TCPHandler.cpp:791
#15 0x00000000058b355f in Poco::Net::TCPServerConnection::start (this=<optimized out>) at ../contrib/poco/Net/src/TCPServerConnection.cpp:43
#16 0x00000000058b393a in Poco::Net::TCPServerDispatcher::run (this=0xf342d00) at ../contrib/poco/Net/src/TCPServerDispatcher.cpp:114
#17 0x00000000059556d7 in Poco::PooledThread::run (this=0x29c747c00) at ../contrib/poco/Foundation/src/ThreadPool.cpp:214
#18 0x0000000005951598 in Poco::ThreadImpl::runnableEntry (pThread=<optimized out>) at ../contrib/poco/Foundation/src/Thread_STD.cpp:139
#19 0x000000000934596f in execute_native_thread_routine ()
#20 0x00007f1924488182 in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0
#21 0x00007f1923cab47d in clone () from /lib/x86_64-linux-gnu/libc.so.6

when duplicate block is inserted, it is silently deduplicated.

#0  ZooKeeperImpl::Exception::Exception (this=0x26a211c80, msg=..., code=-110) at ../dbms/src/Common/ZooKeeper/ZooKeeperImpl.cpp:274
#1  0x0000000005443423 in zkutil::KeeperMultiException::KeeperMultiException (this=0x26a211c80, code=-110, requests=..., responses=...) at ../dbms/src/Common/ZooKeeper/ZooKeeper.cpp:837
#2  0x0000000005443a28 in zkutil::KeeperMultiException::check (code=-110, requests=..., responses=...) at ../dbms/src/Common/ZooKeeper/ZooKeeper.cpp:854
#3  0x0000000005443aaf in zkutil::ZooKeeper::multi (this=<optimized out>, requests=...) at ../dbms/src/Common/ZooKeeper/ZooKeeper.cpp:489
#4  0x0000000004fdf494 in DB::StorageReplicatedMergeTree::checkPartChecksumsAndCommit (this=this@entry=0x14d08410, transaction=..., part=...) at ../dbms/src/Storages/StorageReplicatedMergeTree.cpp:1016
#5  0x0000000004fe077e in DB::StorageReplicatedMergeTree::tryExecuteMerge (this=this@entry=0x14d08410, entry=...) at ../dbms/src/Storages/StorageReplicatedMergeTree.cpp:1273
#6  0x0000000004fe53fb in DB::StorageReplicatedMergeTree::executeLogEntry (this=0x14d08410, entry=...) at ../dbms/src/Storages/StorageReplicatedMergeTree.cpp:1100
#7  0x0000000004fe5aef in DB::StorageReplicatedMergeTree::<lambda(DB::StorageReplicatedMergeTree::LogEntryPtr&)>::operator()(DB::StorageReplicatedMergeTree::LogEntryPtr &) const (__closure=0x7f191fb6bc50, entry=...)
    at ../dbms/src/Storages/StorageReplicatedMergeTree.cpp:2131
#8  0x00000000050d6fd5 in operator() (__args#0=..., this=0x7f191fb6bc50) at /usr/include/c++/7/bits/std_function.h:706
#9  DB::ReplicatedMergeTreeQueue::processEntry(std::function<std::shared_ptr<zkutil::ZooKeeper> ()>, std::shared_ptr<DB::ReplicatedMergeTreeLogEntry>&, std::function<bool (std::shared_ptr<DB::ReplicatedMergeTreeLogEntry>&)>) (
    this=this@entry=0x14d08d70, get_zookeeper=..., entry=..., func=...) at ../dbms/src/Storages/MergeTree/ReplicatedMergeTreeQueue.cpp:1015
#10 0x0000000004fc16c0 in DB::StorageReplicatedMergeTree::queueTask (this=0x14d08410) at ../dbms/src/Storages/StorageReplicatedMergeTree.cpp:2164
#11 0x00000000050142de in operator() (this=<optimized out>) at /usr/include/c++/7/bits/std_function.h:706
#12 DB::BackgroundProcessingPool::threadFunction (this=0xf35bc90) at ../dbms/src/Storages/MergeTree/BackgroundProcessingPool.cpp:178
#13 0x000000000934596f in execute_native_thread_routine ()
#14 0x00007f1924488182 in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0
#15 0x00007f1923cab47d in clone () from /lib/x86_64-linux-gnu/libc.so.6

when two or more replicas finish a merge simultaneously, they will try to add data part simultaneously - exception is thrown in something like compare-and-swap loop that will proceed to the next iteration.

The message
The part ... on a replica suddenly appeared, will recheck checksums

is output in log, and it is totally Ok.

3b39f6a4c36512aeb49b36d2d8d962698e8419de will help.


doesn't work now.. syntax error

fb API change breakage?  Syntax error then spits back last two lines of commands on console somehow

Same here

Are there any plans to fix this? Would really like to use this tool if possible.

File "get-tagged-photos.py", line 76
    print("Photo stuck. Waiting %s seconds..." % (stuck_wait),end="",flush=True)
                                                                 ^
SyntaxError: invalid syntax


undefined export when compiling vendors with DllPlugin mode production

Bug report

What is the current behavior?
Compiling a simple React App using DLLPlugin with the @reach/dialog package included fails to initialize. Project compiles fine, but crashes at runtime with error:
TypeError: undefined is not an object (evaluating 'e[r].call')

Project runs fine when building in non production mode. (--mode development)
Project runs fine when excluding @reach/dialog from the Dll bundle.
If the current behavior is a bug, please provide the steps to reproduce.
Here is a minimal project to replicate the issue https://glitch.com/edit/#!/reach-webpack-bug

What is the expected behavior?
Same behaviour as in  --mode development.
App boots fine with no error when bootstrapping the application.

Other relevant information:
webpack version:  webpack 4.41.5, webpack-cli 3.3.10
Node.js version: 10.16.3
Operating System: MacOS
Additional tools: include the @reach/dialog package in the project.

Adding optimization.usedExports: false seems to solve the issue. I'm still wondering why @reach/dialog is the only library affected by this in our project with multiple dependencies.

Yep, it's a bug. It's caused by the sideEffects optimization, when combined with DllPlugin with entryOnly: false. The sideEffects optimization skips some modules from the graph because they are unused. These modules are not included in the file. Later in the process the DllPlugin flags all exports from all modules as used, which causes the skipped modules to be referenced again.
You can workaround it by using the entryOnly option for the DllPlugin, which makes only the module specified in the entry option accessible by the app bundle. This way usedExports and sideEffects can still run on the dependency graph of these modules. This is a functional difference, but should result in smaller vendor bundles.
Or you can disable usedExports in the vendor build. This would be functional the same as your original code, but do not yield the bug.


Switching windows by name or handle?

Technical limitations

Selenium 2 can switch windows either by name or by handle (see https://www.selenium.dev/documentation/legacy/json_wire_protocol/#sessionsessionidwindow)
Selenium 3 can switch windows by handle only (see https://www.w3.org/TR/webdriver2/#switch-to-window)

Switching windows by a handle

the Selenium server provides a handle for the currently focused window
the Selenium server provides a handle for all opened windows without the need to focus each of them upfront
using a handle is supported for Selenium 2 and Selenium 3
providing an empty window name will switch to the first opened window in Selenium 2 only

Switching windows by a name

the Selenium server can only return the name for the currently focused window
there can be several windows with an empty (non-unique) name
no way to switch to the first opened window

Current implementation

the getWindowName method returns a handle
the getWindowNames method returns a handles array
the switchToWindow on Selenium 2 can switch windows by name/handle (see Technical limitations above)
the switchToWindow on Selenium 3 can switch windows by a handle (see Technical limitations above)

Proposed implementation
See https://github.com/minkphp/MinkSelenium2Driver/pull/384 .

the getWindowName method returns a window name (if non-empty) or a handle
the getWindowNames method returns a window name (if non-empty) or a handle array
the switchToWindow can switch windows by a name/handle, but needs to iterate/focus over each window to determine the handle by its name

The downside of the proposed implementation
All windows need to be iterated to retrieve their name, which:

can be slow when lots of windows are opened (these websites exist?);
when the website has a JavaScript code that closes a window upon focus loss, then iteration can be very bad.

In the https://github.com/minkphp/MinkSelenium2Driver/pull/384/files#r1501886088 @uuf6429 proposed to replace window name support with window handle support Mink-wise. Considering, that Selenium-based drivers are the only ones that support window operations now. But who knows what will be in the future.
I personally like the proposed implementation, because:

it makes tests pass for Selenium 3;
the potential problems, described above, are really an edge cases, that might be as common.

Please keep any discussion about the changing the Mink API in the main Mink repo rather than in drivers please.


support typescript?

The definition in the typescript official repertory is older

I created TypeScript definitions in #142 but it opens already a month :(

should a PR be made to the typescript repo instead? Just wondering what the best set of definitions is.

Better then you will maintain TypeScript definitions at yours package source code, to my mind

Maintain d.ts at it's own package's repo is the best practice.

I created TypeScript definitions in #142 but it opens already a month :(

It opened for 7 months. I'll move that to @types/eureka-js-client


Build enums from a catalog attribute

If you have a catalog type such as Backstage Component, which itself has tags, you might want to create a separate catalog type called Backstage Tag to represent each value. This allows the UI to find associations and filter by the value of any particular tag.
There's two obvious ways we could do this:

enum_from directive on the attribute

Allow specifying the catalog type you'd create for an attribute's values from the attribute definition itself.
// pipelines.output.attributes
{
  id: 'tags',
  name: 'Tags',
  array: true,
  // Replaces the `type` field, as it will implicitly type the attribute to match
  enum_type: {
    name: 'Backstage Tag',
    type_name: 'Custom["BackstageTag"]',
    description: 'Tags applied to Backstage components.',
    type: 'String',
  }
}

This keeps the definition of the enum close to the attribute that defines it. But it complicates the attribute schema, and it's limited to a single attribute value.
An alternative might be:

Source from entry attributes

Support a pipeline source that creates a set of entries from a catalog types attribute. This would allow creating a separate pipeline to produce the enum output, and combining values from many attributes and types together: say if you wanted to combine tags from all Backstage resources into a single "Backstage Tag" type, rather than just from components.
It might look like:
// pipelines.sources
{
  catalog: {
    type: 'Custom["BackstageComponent"]',
    entry: {
      // Build entry from CEL expressions
    },
  },
}

This is a generic version of reshaping existing catalog data. It's not immediately clear how we'd 'explode' the array value of tags, so that we'd get a separate entry for each attribute value, nor how we'd handle duplicates (outstanding questions on this anyway).
My hunch is ^ is valuable, but a more direct solution to this problem might be:
{
  catalog_values: {
    types: [
      { type: 'Custom["BackstageComponent"]', value: 'tags' },
      { type: 'Custom["BackstageAPI"]', value: 'tags' },
    ],
  },
}

Which can, all within the source implementation itself, de-duplicate the results to provide an easily used set of entries of form [{value}].

Support this natively in the catalog

Enums are pretty common. We could add another resource type that is a string but is represented as an enum.
This would require special casing and specific UX to give a good experience around browsing related entries for a given enum value. That's the clear downside as if we represent enums as catalog types, you get all that for free.
Upside is simpler clients, potentially easier performance.

I'm gonna give (2) a shot, specifically the catalog_values version.

On reflection, either of these are a bit difficult.
If you support the "make this attribute into an enum" you need to provide some post-processing 'after-the-pipeline' step where you collect up the values and produce yet another catalog type. It's extremely special cased and threading that into the existing output feels a bit sad, though probably not as bad as it feels without having tried it.
If you go the source route, you have to source + marshal the values of whichever types you depend on first before you can keep going. The simplest way to do this is to repeatedly source and marshal entries but that feels costly.

Now supported.


fixed css & js to allow for nested numbering

Two small modifications to make nested numbering style work in the ToC (i.e., 1, 1.1, 1.1.1)

correct CSS definitions to remove unused nested class
fix JS generation of the ToC, ensuring correct placement of each <ol> level (inside the parent <li>, not as a sibling).

Tested on Firefox, Chrome and IE11

@paulovn Can you describe teh bug which happens here? the toc extension is also included here https://github.com/ipython-contrib/IPython-notebook-extensions/tree/master/nbextensions/usability/toc and I try to see if we need the same fix :-/

Essentially the original CSS is prepared to number the ToC items with nested numbering, such as
 1 Title
    1.1 Subsection
       1.1.1 subsubsection

it does so by defining counters, and using a custom marker content: counters(item, ".")" ";
But it didn't work as it was, instead what I got was plain simple independent numbers:
 1 Title
    1 Subsection
       1 subsubsection

which, if you have many levels in the headings of your notebook, is confusing for navigation.
The problem is due to two causes:

the CSS <ol> & <li> elements are using the nested class, which the JS code does not set, hence they do not get applied
the JS code generates the ToC tree by inserting <ol> elements as a sibling of the <li> element in the upper level they belong to -- I believe this is wrong, they should be inside the <li> element

The fix corrects both facts. If you don't need nested numbering, it probably won't matter much


Updating the Vendor Contract section

I have updated the vendor contract section to point to our new Vendor Request Process handbook page.

@tammy-zhu Sourcegraph's data should include our personal data as we are employees of the company. Happy to change the wording to explicitly mention personal data as well. We should use the same process for all vendors.


IPSec VPN edits

Description

Motivation and Context

Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Documentation fix (typos, incorrect content, missing content, etc.)

Checklist

[ ] I have read the contributing document.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[ ] I have added tests to cover my changes.
[ ] All new and existing tests passed.

@lysannep thank you for the suggestions and quick turnaround!


All Unique prime factors of n

Hey, I am Kirti as a GSSoC '21 participant
here I want to find all unique prime factors of any number n where (n>1) for example if n is 20 then output will be (2,5).
Please assign this task to me!

Please assign this to me under GSSoC'21, I can do it in python and C++

I am a participant of gssoc 21 ,i want to work on this issue in c/c++/python .please assign this work to me .
For example:a number 10,.   (2,5) will be the answer

Hi,
I am GSSOC'21 participant
My code will be in JAVA with proper comments and test cases.
@rudrakshi99 @nakul-19 @plazzy99 @tarun26091999  please assign me this issue

@Tj8864 do it in python


ios version can't sync twitter's picture which stared

Thanks for what a great app and what you worked  for it.
I installed NetNewsWire both my iPhone and iPad, and use icloud account. A feed which I stared on my phone, I can watch
it(include picture) on my iPad even the source item has been deleted but not Twitter.
Such as I stared a feed from Weibo (a site like Twitter in China), even that item has been deleted but I can also watch it's picture.
It seems the loaded pictures synced with iCloud.
But as you know, we can't visit Twitter directly in China, I have to use VPN again to show pictures from twitter on my iPad which I stared and loaded those pictures on my iPhone.
It seems loaded tweets' pictures haven't sync with iCloud?

Correct. An articles images are served from the hosting web server, so if those get deleted, you won't be able to view them. They aren't cached locally and aren't synced with iCloud.
If you are seeing a difference with Twitter, please make sure you have the Twitter extension enabled in NetNewsWire on all your devices.

正确。. 文章图像是从托管Web服务器提供的,因此,如果这些图像被删除,您将无法查看它们。. 它们不在本地缓存,也没有与iCloud同步。.
如果您发现Twitter有所不同,请确保在所有设备上的NetNewsWire中启用了Twitter扩展名。.

Thanks for your reply.
I tested that, iPhone get this feed with images and I stared, then I deleted the source article, both iPhone and iPad can view those pictures.
I installed twitter extension both iPhone and iPad's NetNewswire, and I will keep focus on it.
Best regards.


Sync API support

Hi!
Does this library support Sync API as well, and if not, are there any plans to add support for this feature?

Hi @szimek,
We don't have the Sync API support yet, but we do have it in our backlog.
We plan to have it in Q1 2021.

Thanks!


Optimize PSG noise generation

VERA currently uses a 16-bit LFSR which has a minimum of 4 XOR taps required for maximum period. However, by increasing the size to 17-bit, only 2 XOR taps are required. Also, the noise is sampled directly from the shift register instead of going through another noise_value_r layer which functionally does the same thing.
Here's the (emulated) audio comparison between current and after this PR:
https://user-images.githubusercontent.com/77432377/231419617-047a3d62-eac9-42f4-bde3-613d1ef1e91f.mp4
https://user-images.githubusercontent.com/77432377/231419836-22c96a0b-df18-40fc-ba9f-8613e9b9f723.mp4

Can you quantify what this gets us in terms of hard metrics such as the delta in the number of logic LUTs, passthrough LUTs, slices, etc.? Subjectively this implementation looks a bit cleaner and sounds the same, but I'm reluctant to merge changes without knowing what they get us.


patchelf: 0.14.5 -> 0.15.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/NixOS/patchelf/releases.
meta.description for patchelf is: "A small utility to modify the dynamic linker and RPATH of ELF executables"
meta.homepage for patchelf is: "https://github.com/NixOS/patchelf"
meta.changelog for patchelf is: ""
Updates performed

Version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 0.15.0 with grep in /nix/store/w0v3kv9z8rpjkr400rwims5bqwfari6k-patchelf-0.15.0
found 0.15.0 in filename of file in /nix/store/w0v3kv9z8rpjkr400rwims5bqwfari6k-patchelf-0.15.0

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

50586 total rebuild path(s)

50586 package rebuild(s)

First fifty rebuilds by attrpath

AMB-plugins
ArchiSteamFarm
AusweisApp2
CHOWTapeModel
ChowCentaur
ChowKick
ChowPhaser
CoinMP
CuboCore.coreaction
CuboCore.corearchiver
CuboCore.corefm
CuboCore.coregarage
CuboCore.corehunt
CuboCore.coreimage
CuboCore.coreinfo
CuboCore.corekeyboard
CuboCore.corepad
CuboCore.corepaint
CuboCore.corepdf
CuboCore.corepins
CuboCore.corerenamer
CuboCore.coreshot
CuboCore.corestats
CuboCore.corestuff
CuboCore.coreterminal
CuboCore.coretime
CuboCore.coretoppings
CuboCore.coreuniverse
CuboCore.libcprime
CuboCore.libcsys
DisnixWebService
EBTKS
EmptyEpsilon
FIL-plugins
Fabric
HentaiAtHome
LAStools
LASzip
LASzip2
LibreArp
LibreArp-lv2
Literate
MACS2
MIDIVisualizer
MMA
NSPlist
OSCAR
OVMF
OVMFFull

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/w0v3kv9z8rpjkr400rwims5bqwfari6k-patchelf-0.15.0 \
  --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 patchelf https://github.com/r-ryantm/nixpkgs/archive/c826b18a286e27686495f6035d57167cf99a1109.tar.gz

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

Pre-merge build results
NixPkgs review skipped

Maintainer pings
cc @edolstra for testing.

Looks like this update broke cryptsetup on armv7l-linux.
building '/nix/store/3md0i19y9xq67fmk9a7pi7h89mbkzphq-cryptsetup-2.4.3.drv'...
error: builder for '/nix/store/3md0i19y9xq67fmk9a7pi7h89mbkzphq-cryptsetup-2.4.3.drv' failed with exit code 2;
       last 10 log lines:
       > 1 of 6 tests failed
       > (23 tests were not run)
       > =======================
       > make[3]: *** [Makefile:802: check-TESTS] Error 1
       > make[3]: Leaving directory '/build/cryptsetup-2.4.3/tests'
       > make[2]: *** [Makefile:928: check-am] Error 2
       > make[2]: Leaving directory '/build/cryptsetup-2.4.3/tests'
       > make[1]: *** [Makefile:930: check] Error 2
       > make[1]: Leaving directory '/build/cryptsetup-2.4.3/tests'
       > make: *** [Makefile:2604: check-recursive] Error 1
       For full logs, run 'nix log /nix/store/3md0i19y9xq67fmk9a7pi7h89mbkzphq-cryptsetup-2.4.3.drv'.
c826b18a286e27686495f6035d57167cf99a1109 is the first bad commit
commit c826b18a286e27686495f6035d57167cf99a1109
Author: R. Ryantm<EMAIL_ADDRESS>Date:   Fri Jul 29 15:34:13 2022 +0000

    patchelf: 0.14.5 -> 0.15.0

 pkgs/development/tools/misc/patchelf/default.nix | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)
bisect found first bad commitgit bisect run nix-build . --no-out-link --fallback -A pkgs.cryptsetup   -Q  6,54s user 6,95s system 0% cpu 4:11:36,77 total


Add CAM-SE analysis blogpost

@philipc2 this may be of interest to you. See the spectral element NB and section 1. Regrid CAM-SE output using map file for the Uxarray mention. I didn't try this NB's files out with UXarray, but if they are already supported, it would be great to mention your recent viz helpers somewhere in this NB (in addition to mentioning our issue).

I would second this suggestion! Maybe mentioning ESMF_RegridWeightGen as a tool to generate mapfiles would be useful.

View entire conversation on ReviewNB

Thanks Teagan! The blog post has an author tag, which you specify in the notebook metadata, so I was able to add my name there. It should show up on the website that way. Here I wanted to acknowledge you and others who contributed to the code/ideas in the notebook. I could also just add you all as authors in the notebook metadata -- what do you think?

View entire conversation on ReviewNB

Great idea! I've never actually generated a map file - Teagan do you know if there is a good link to use to direct others to the appropriate ESMF code/tool?

View entire conversation on ReviewNB

Fixed!

View entire conversation on ReviewNB

Great idea - done.

View entire conversation on ReviewNB

Good suggestion - short summary added to the end. I don't really have a good sense of which is "best", but hopefully as others utilize the code we can have more discussions about the various approaches.

View entire conversation on ReviewNB

That sounds perfect!

View entire conversation on ReviewNB

Perfect, I'm glad that will be clear from the metadata! That makes sense to keep acknowledgements within the notebook.

View entire conversation on ReviewNB

Looks great! The summary you added is really helpful, too.

View entire conversation on ReviewNB

Here's the ESMF tool documentation (this is the one I'm more familiar with, although there is also an ESMPy version tutorial which may be useful).

View entire conversation on ReviewNB

I could also just add you all as authors in the notebook metadata

:+1: . I also like adding the "Co-authored-by" line to the commit message.

@dcherian chimed in with a thumbs up for adding authors to the notebook metadata so I think I will do that instead, it seems cleaner. This is a good discussion though on how we properly credit blog post contributors. Co-authorship on commits is good to know about too.

View entire conversation on ReviewNB

@philipc2 this may be of interest to you. See the spectral element NB and section (1) "Regrid CAM-SE output using map file" for the Uxarray mention. I didn't try this NB's files out with UXarray, but if they are already supported, it would be great to mention your recent viz helpers somewhere in this NB (in addition to mentioning our UXARRAY/uxarray#183 (comment)).

@erogluorhan @philipc2 let me know if there is anything you'd like to add to this notebook from the UXarray side. I think we're pretty close to finalizing it.

The notebook looks great!! The only thing possibly worth adding in the UXarray section is a link to our new usage example notebook, which has a few visualization examples. Other than that I dont have any objections!


Members filter UI appears offscreen on mobile

Issue Summary
Issue with Filter modal CSS.
http://localhost:2368/ghost/#/members.
After navigating click on the filters

Filters appearing in the right side.
Checked with the mobile iPhone SE/12/13 , All resulting the above issue.
Please check the following CSS,
@media (max-width: 690px) {
    .gh-members-filter-builder {
        width: calc(100vw - 20px);
        min-width: calc(100vw - 20px);
        max-width: calc(100vw - 20px);
        left: 0 !important;
        right: 0 !important;
        margin-left: 10px;
        margin-right: 10px;
    }
}

Steps to Reproduce

Navigate to Members
Use mobile resolution
Click on the filters button in the top.

Ghost Version
v5.97.3
Node.js Version
18.17.1
How did you install Ghost?
ghost install local
Database type
MySQL 8
Browser & OS version
Chrome , Mac OS
Relevant log / error output
No response
Code of Conduct

[X] I agree to be friendly and polite to people in this repository

@dvdwinden can you mention the reason for closing please.

@mithelan It's automatically closed via a PR — the issue has been fixed and will be included in the next release.


rocPRIM build failing due to requirement 'hcc' or 'clang' must be compiler

=~=~=~=~=~=~=~=~=~=~=~= MobaXterm log 2021.04.09 22:46:10 =~=~=~=~=~=~=~=~=~=~=~=
na[CXX=hipcc] cmake -DBUILD_BENCHMARK=ON ../.CXX=hipcc;..
root@guest:~/ROCm-4.1/rocPRIM# ehich       which hipcc
/usr/bin/hipcc
root@guest:~/ROCm-4.1/rocPRIM# which hipccCXX=which hipcc
root@guest:~/ROCm-4.1/rocPRIM# [CXX=hipcc] cmake -DBUILD_BENCHMARK=ON ../.Xccm
CMake Error: The source directory "/root/ROCm-4.1" does not appear to contain CMakeLists.txt.
Specify --help for usage, or press the help button on the CMake GUI.
root@guest:~/ROCm-4.1/rocPRIM# cd build
root@guest:~/ROCm-4.1/rocPRIM/build# rm -rf ./*
root@guest:~/ROCm-4.1/rocPRIM/build# rm -rf ./*cd buildmake -DBUILD_BENCHMARK=ON ../.
-- The CXX compiler identification is GNU 7.5.0
-- Check for working CXX compiler: /usr/bin/c++
-- Check for working CXX compiler: /usr/bin/c++ -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Setting build type to 'Release' as none was specified.
CMake Error at cmake/VerifyCompiler.cmake:24 (find_package):
Could not find a package configuration file provided by "hip" with any of
the following names:
hipConfig.cmake
hip-config.cmake

Add the installation prefix of "hip" to CMAKE_PREFIX_PATH or set "hip_DIR"
to a directory containing one of the above files.  If "hip" provides a
separate development package or SDK, be sure it has been installed.
Call Stack (most recent call first):
CMakeLists.txt:67 (include)
-- Configuring incomplete, errors occurred!
See also "/root/ROCm-4.1/rocPRIM/build/CMakeFiles/CMakeOutput.log".
root@guest:~/ROCm-4.1/rocPRIM/build# find /opt -name hipConfig.cmake
root@guest:~/ROCm-4.1/rocPRIM/build# find ~/ROCm-4.1/ -name hipConfig.cmake
root@guest:~/ROCm-4.1/rocPRIM/build# find /opt -name HIP
root@guest:~/ROCm-4.1/rocPRIM/build# find /opt -name HIP   hip
/opt/rocm-4.1.0/include/hip
/opt/rocm-4.1.0/hip
/opt/rocm-4.1.0/hip/include/hip
/opt/rocm-4.1.0/hip/lib/cmake/hip
/opt/rocm-4.1.0/lib/cmake/hip
/opt/rocm/hip
root@guest:~/ROCm-4.1/rocPRIM/build#

hip-config exists however apparently it is not finding it /opt/rocm-4.1.0/hip/lib/cmake/hip/hip-config.cmake

I found this is due to disrepancy in path which I corrected and now, I see it is unable to find hipcc compiler and giving off following error:
cmake -DBUILD_BENCHMARK=ON CXX=/opt/rocm/bin/hipcc ../.
-- The CXX compiler identification is GNU 7.5.0
-- Check for working CXX compiler: /usr/bin/c++
-- Check for working CXX compiler: /usr/bin/c++ -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Setting build type to 'Release' as none was specified.
-- Looking for C++ include pthread.h
-- Looking for C++ include pthread.h - found
-- Performing Test CMAKE_HAVE_LIBC_PTHREAD
-- Performing Test CMAKE_HAVE_LIBC_PTHREAD - Failed
-- Looking for pthread_create in pthreads
-- Looking for pthread_create in pthreads - not found
-- Looking for pthread_create in pthread
-- Looking for pthread_create in pthread - found
-- Found Threads: TRUE
-- ROCclr at /opt/rocm/lib/cmake/rocclr
CMake Error at cmake/VerifyCompiler.cmake:29 (message):
On ROCm platform 'hcc' or 'clang' must be used as C++ compiler.
Call Stack (most recent call first):
CMakeLists.txt:67 (include)
-- Configuring incomplete, errors occurred!
I can see it is coming from
../cmake/VerifyCompiler.cmake in rocPRIM:
if(NOT (CMAKE_CXX_COMPILER MATCHES ".*/hcc$" OR CMAKE_CXX_COMPILER MATCHES ".*/hipcc$"))
    message(FATAL_ERROR "On ROCm platform 'hcc' or 'clang' must be used as C++ compiler.")
elseif(NOT CXX_VERSION_STRING MATCHES "clang")
    list(APPEND CMAKE_PREFIX_PATH /opt/rocm/hcc)
    set(CMAKE_CXX_FLAGS "${CMAKE_CXX_FLAGS} -Wno-unused-command-line-argument")
endif()

It is unclear why it is giving off this error even thou CXX is set to valid hipcc path.

Thanks @gggh000 for reaching out.
Request you to modify the title for calling exact issue.
Request you to share the exact steps to reproduce the problem.
Thank you.

Hi @gggh000
I am not able to reproduce the problem when I followed below steps.
taccuser@taccuser-X399-DESIGNARE-EX:~$ git clone https://github.com/rocmsoftwareplatform/rocprim -b rocm-4.1.x
Cloning into 'rocprim'...
remote: Enumerating objects: 1133, done.
remote: Counting objects: 100% (1133/1133), done.
remote: Compressing objects: 100% (463/463), done.
remote: Total 10231 (delta 699), reused 980 (delta 587), pack-reused 9098
Receiving objects: 100% (10231/10231), 3.19 MiB | 1.93 MiB/s, done.
Resolving deltas: 100% (7005/7005), done.
taccuser@taccuser-X399-DESIGNARE-EX:~$ cd rocprim/
taccuser@taccuser-X399-DESIGNARE-EX:~/rocprim$ mkdir build
taccuser@taccuser-X399-DESIGNARE-EX:~/rocprim$ cd build/
taccuser@taccuser-X399-DESIGNARE-EX:~/rocprim/build$ CXX=/opt/rocm/hip/bin/hipcc cmake -DBUILD_BENCHMARK=ON ../.
-- The CXX compiler identification is Clang 12.0.0
-- Check for working CXX compiler: /opt/rocm/hip/bin/hipcc
-- Check for working CXX compiler: /opt/rocm/hip/bin/hipcc -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Setting build type to 'Release' as none was specified.
-- Looking for C++ include pthread.h
-- Looking for C++ include pthread.h - found
-- Performing Test CMAKE_HAVE_LIBC_PTHREAD
-- Performing Test CMAKE_HAVE_LIBC_PTHREAD - Success
-- Found Threads: TRUE
-- ROCclr at /opt/rocm/lib/cmake/rocclr
-- Performing Test HIP_CLANG_SUPPORTS_PARALLEL_JOBS
-- Performing Test HIP_CLANG_SUPPORTS_PARALLEL_JOBS - Success
-- Found Git: /usr/bin/git (found version "2.25.1")
-- Downloading and building Google Benchmark.
-- Downloading/updating googlebenchmark
-- Configuring done
-- Generating done
-- Build files have been written to: /home/taccuser/rocprim/build/googlebenchmark-download
Scanning dependencies of target googlebenchmark-download
[ 11%] Creating directories for 'googlebenchmark-download'
[ 22%] Performing download step (git clone) for 'googlebenchmark-download'
-- googlebenchmark-download download command succeeded.  See also /home/taccuser/rocprim/build/googlebenchmark-download/googlebenchmark-download-prefix/src/googlebenchmark-download-stamp/googlebenchmark-download-download-.log
[ 33%] No patch step for 'googlebenchmark-download'
[ 44%] Skipping update step for 'googlebenchmark-download'
[ 55%] Performing configure step for 'googlebenchmark-download'
-- googlebenchmark-download configure command succeeded.  See also /home/taccuser/rocprim/build/googlebenchmark-download/googlebenchmark-download-prefix/src/googlebenchmark-download-stamp/googlebenchmark-download-configure-.log
[ 66%] Performing build step for 'googlebenchmark-download'
make -j
-- googlebenchmark-download build command succeeded.  See also /home/taccuser/rocprim/build/googlebenchmark-download/googlebenchmark-download-prefix/src/googlebenchmark-download-stamp/googlebenchmark-download-build-.log
[ 77%] Performing install step for 'googlebenchmark-download'
-- googlebenchmark-download install command succeeded.  See also /home/taccuser/rocprim/build/googlebenchmark-download/googlebenchmark-download-prefix/src/googlebenchmark-download-stamp/googlebenchmark-download-install-.log
[ 88%] No test step for 'googlebenchmark-download'
[100%] Completed 'googlebenchmark-download'
[100%] Built target googlebenchmark-download
-- ******** Summary ********
-- General:
--   System                : Linux
--   HIP ROOT              :
--   C++ compiler          : /opt/rocm/hip/bin/hipcc
--   C++ compiler version  : 12.0.0
--   CXX flags             : -Wno-unused-command-line-argument -Wall -Wextra
--   Build type            : Release
--   Install prefix        : /opt/rocm
--   Device targets        : gfx803;gfx900:xnack-;gfx906:xnack-;gfx908:xnack-
--   DISABLE_WERROR        : ON
--   ONLY_INSTALL          : OFF
--   BUILD_TEST            : OFF
--   BUILD_BENCHMARK       : ON
--   BUILD_EXAMPLE         : OFF
-- Configuring done
-- Generating done
-- Build files have been written to: /home/taccuser/rocprim/build
taccuser@taccuser-X399-DESIGNARE-EX:~/rocprim/build$ make -j
Scanning dependencies of target benchmark_device_merge_sort
Scanning dependencies of target benchmark_device_partition
Scanning dependencies of target benchmark_device_select
Scanning dependencies of target benchmark_warp_scan
Scanning dependencies of target benchmark_block_radix_sort
Scanning dependencies of target benchmark_device_merge
Scanning dependencies of target benchmark_block_scan
Scanning dependencies of target benchmark_block_histogram
Scanning dependencies of target benchmark_device_radix_sort
Scanning dependencies of target benchmark_device_binary_search
Scanning dependencies of target benchmark_block_reduce
Scanning dependencies of target benchmark_device_histogram
Scanning dependencies of target benchmark_device_scan
Scanning dependencies of target benchmark_block_exchange
Scanning dependencies of target benchmark_block_sort
Scanning dependencies of target benchmark_device_transform
Scanning dependencies of target benchmark_warp_reduce
Scanning dependencies of target benchmark_device_reduce_by_key
Scanning dependencies of target benchmark_block_discontinuity
Scanning dependencies of target benchmark_device_reduce
Scanning dependencies of target benchmark_device_run_length_encode
Scanning dependencies of target benchmark_warp_sort
Scanning dependencies of target benchmark_device_segmented_reduce
Scanning dependencies of target benchmark_device_segmented_radix_sort
Scanning dependencies of target benchmark_device_memory
[  6%] Building CXX object benchmark/CMakeFiles/benchmark_device_partition.dir/benchmark_device_partition.cpp.o
[  6%] Building CXX object benchmark/CMakeFiles/benchmark_block_radix_sort.dir/benchmark_block_radix_sort.cpp.o
[  6%] Building CXX object benchmark/CMakeFiles/benchmark_warp_scan.dir/benchmark_warp_scan.cpp.o
[  8%] Building CXX object benchmark/CMakeFiles/benchmark_block_histogram.dir/benchmark_block_histogram.cpp.o
[ 10%] Building CXX object benchmark/CMakeFiles/benchmark_device_binary_search.dir/benchmark_device_binary_search.cpp.o
[ 14%] Building CXX object benchmark/CMakeFiles/benchmark_device_merge.dir/benchmark_device_merge.cpp.o
[ 14%] Building CXX object benchmark/CMakeFiles/benchmark_device_histogram.dir/benchmark_device_histogram.cpp.o
[ 16%] Building CXX object benchmark/CMakeFiles/benchmark_block_scan.dir/benchmark_block_scan.cpp.o
[ 18%] Building CXX object benchmark/CMakeFiles/benchmark_device_radix_sort.dir/benchmark_device_radix_sort.cpp.o
[ 20%] Building CXX object benchmark/CMakeFiles/benchmark_device_merge_sort.dir/benchmark_device_merge_sort.cpp.o
[ 22%] Building CXX object benchmark/CMakeFiles/benchmark_block_reduce.dir/benchmark_block_reduce.cpp.o
[ 24%] Building CXX object benchmark/CMakeFiles/benchmark_device_select.dir/benchmark_device_select.cpp.o
[ 26%] Building CXX object benchmark/CMakeFiles/benchmark_device_scan.dir/benchmark_device_scan.cpp.o
[ 30%] Building CXX object benchmark/CMakeFiles/benchmark_block_discontinuity.dir/benchmark_block_discontinuity.cpp.o
[ 30%] Building CXX object benchmark/CMakeFiles/benchmark_device_run_length_encode.dir/benchmark_device_run_length_encode.cpp.o
[ 36%] Building CXX object benchmark/CMakeFiles/benchmark_block_exchange.dir/benchmark_block_exchange.cpp.o
[ 36%] Building CXX object benchmark/CMakeFiles/benchmark_warp_sort.dir/benchmark_warp_sort.cpp.o
[ 36%] Building CXX object benchmark/CMakeFiles/benchmark_device_transform.dir/benchmark_device_transform.cpp.o
[ 46%] Building CXX object benchmark/CMakeFiles/benchmark_device_reduce.dir/benchmark_device_reduce.cpp.o
[ 46%] Building CXX object benchmark/CMakeFiles/benchmark_block_sort.dir/benchmark_block_sort.cpp.o
[ 46%] Building CXX object benchmark/CMakeFiles/benchmark_device_reduce_by_key.dir/benchmark_device_reduce_by_key.cpp.o
[ 46%] Building CXX object benchmark/CMakeFiles/benchmark_device_segmented_reduce.dir/benchmark_device_segmented_reduce.cpp.o
[ 46%] Building CXX object benchmark/CMakeFiles/benchmark_device_segmented_radix_sort.dir/benchmark_device_segmented_radix_sort.cpp.o
[ 48%] Building CXX object benchmark/CMakeFiles/benchmark_warp_reduce.dir/benchmark_warp_reduce.cpp.o
[ 50%] Building CXX object benchmark/CMakeFiles/benchmark_device_memory.dir/benchmark_device_memory.cpp.o
ctest
[ 52%] Linking CXX executable benchmark_device_transform
[ 52%] Built target benchmark_device_transform
[ 54%] Linking CXX executable benchmark_device_binary_search
[ 54%] Built target benchmark_device_binary_search
[ 56%] Linking CXX executable benchmark_device_reduce
[ 56%] Built target benchmark_device_reduce
[ 58%] Linking CXX executable benchmark_device_segmented_reduce
[ 58%] Built target benchmark_device_segmented_reduce
[ 60%] Linking CXX executable benchmark_device_merge
[ 60%] Built target benchmark_device_merge
[ 62%] Linking CXX executable benchmark_warp_sort
[ 62%] Built target benchmark_warp_sort
[ 64%] Linking CXX executable benchmark_warp_reduce
[ 64%] Built target benchmark_warp_reduce
[ 66%] Linking CXX executable benchmark_block_histogram
[ 66%] Built target benchmark_block_histogram
[ 68%] Linking CXX executable benchmark_device_partition
[ 68%] Built target benchmark_device_partition
[ 70%] Linking CXX executable benchmark_warp_scan
[ 70%] Built target benchmark_warp_scan
[ 72%] Linking CXX executable benchmark_device_reduce_by_key
[ 72%] Built target benchmark_device_reduce_by_key
[ 74%] Linking CXX executable benchmark_block_discontinuity
[ 74%] Built target benchmark_block_discontinuity
[ 76%] Linking CXX executable benchmark_device_merge_sort
[ 76%] Built target benchmark_device_merge_sort
[ 78%] Linking CXX executable benchmark_device_histogram
[ 78%] Built target benchmark_device_histogram
[ 80%] Linking CXX executable benchmark_device_select
[ 80%] Built target benchmark_device_select
[ 82%] Linking CXX executable benchmark_device_run_length_encode
[ 82%] Built target benchmark_device_run_length_encode
[ 84%] Linking CXX executable benchmark_block_reduce
[ 84%] Built target benchmark_block_reduce
[ 86%] Linking CXX executable benchmark_device_scan
[ 86%] Built target benchmark_device_scan
[ 88%] Linking CXX executable benchmark_block_exchange
[ 88%] Built target benchmark_block_exchange
[ 90%] Linking CXX executable benchmark_device_segmented_radix_sort
[ 90%] Built target benchmark_device_segmented_radix_sort
[ 92%] Linking CXX executable benchmark_block_sort
[ 92%] Built target benchmark_block_sort
[ 94%] Linking CXX executable benchmark_device_memory
[ 94%] Built target benchmark_device_memory
[ 96%] Linking CXX executable benchmark_device_radix_sort
[ 96%] Built target benchmark_device_radix_sort
[ 98%] Linking CXX executable benchmark_block_radix_sort
[ 98%] Built target benchmark_block_radix_sort
[100%] Linking CXX executable benchmark_block_scan
[100%] Built target benchmark_block_scan
taccuser@taccuser-X399-DESIGNARE-EX:~

Can you let me know why cmake log printing /usr/bin/c++ as compiler even though i specified compiler to hipcc?
I tried several different ways all same:
cmake -DBUILD_BENCHMARK=ON DCXX=/opt/rocm/bin/hipcc ../.
cmake -DBUILD_BENCHMARK=ON CXX=/opt/rocm/bin/hipcc ../.
cmake -DBUILD_BENCHMARK=ON DCMAKE_CXX_COMPILER=/opt/rocm/bin/hipcc ../.
cmake -DBUILD_BENCHMARK=ON CMAKE_CXX_COMPILER=/opt/rocm/bin/hipcc ../.
root@guest:~/ROCm-4.1/rocPRIM# cd build
root@guest:~/ROCm-4.1/rocPRIM/build# rm -rf ./*
root@guest:~/ROCm-4.1/rocPRIM/build# !1965^C
root@guest:~/ROCm-4.1/rocPRIM/build# cmake -DBUILD_BENCHMARK=ON DCXX=/opt/rocm/bin/hipcc ../.
-- The CXX compiler identification is GNU 7.5.0
-- Check for working CXX compiler: /usr/bin/c++
-- Check for working CXX compiler: /usr/bin/c++ -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Setting build type to 'Release' as none was specified.
-- Looking for C++ include pthread.h
-- Looking for C++ include pthread.h - found
-- Performing Test CMAKE_HAVE_LIBC_PTHREAD
-- Performing Test CMAKE_HAVE_LIBC_PTHREAD - Failed
-- Looking for pthread_create in pthreads
-- Looking for pthread_create in pthreads - not found
-- Looking for pthread_create in pthread
-- Looking for pthread_create in pthread - found
-- Found Threads: TRUE
-- ROCclr at /opt/rocm/lib/cmake/rocclr
CMake Error at cmake/VerifyCompiler.cmake:29 (message):
On ROCm platform 'hcc' or 'clang' must be used as C++ compiler.
Call Stack (most recent call first):
CMakeLists.txt:67 (include)
-- Configuring incomplete, errors occurred!
See also "/root/ROCm-4.1/rocPRIM/build/CMakeFiles/CMakeOutput.log".
See also "/root/ROCm-4.1/rocPRIM/build/CMakeFiles/CMakeError.log".
root@guest:~/ROCm-4.1/rocPRIM/build# cmake -DBUILD_BENCHMARK=ON CXX=/opt/rocm/bin/hipcc ../.
-- ROCclr at /opt/rocm/lib/cmake/rocclr
CMake Error at cmake/VerifyCompiler.cmake:29 (message):
On ROCm platform 'hcc' or 'clang' must be used as C++ compiler.
Call Stack (most recent call first):
CMakeLists.txt:67 (include)
-- Configuring incomplete, errors occurred!
See also "/root/ROCm-4.1/rocPRIM/build/CMakeFiles/CMakeOutput.log".
See also "/root/ROCm-4.1/rocPRIM/build/CMakeFiles/CMakeError.log".
root@guest:~/ROCm-4.1/rocPRIM/build#

On readme.md, it only says following about cxx compiler which does not work when followed:
! IMPORTANT !
Set C++ compiler to HIP-clang. You can do it by adding 'CXX='
before 'cmake' or setting cmake option 'CMAKE_CXX_COMPILER' to path to the compiler.
Using HIP-clang:
[CXX=hipcc] cmake -DBUILD_BENCHMARK=ON ../.

CXX=/opt/rocm/hip/bin/hipcc cmake -DBUILD_BENCHMARK=ON ../.

I dont see which branch you are using.

OK, following works as posted by you:
CXX=/opt/rocm/hip/bin/hipcc cmake -DBUILD_BENCHMARK=ON ../.
However, the readme.md does not convery this information correctly as mentioned above.

Thanks @gggh000
You need to use exactly same as "CXX=/opt/rocm/hip/bin/hipcc cmake -DBUILD_BENCHMARK=ON ../.".
Changing the flags before and after do not work.
I followed documentation only. Doc says: [CXX=hipcc] cmake -DBUILD_BENCHMARK=ON ../., which is the same.
I just replaced CXX with full path.

Thanks @gggh000  for following the above step exactly and confirming that issue is not reproduced.
Thank you.


startup-monitor: always try to delete the symlink before creating it

the existing fileExists method checks only the target file and creating a symlink fails when it already exists

/lgtm
/approve


Gamma correction for depth image option

Hello, I was recently working with NViSII and was trying to get the raw pixels for the images, and it was brought to my attention that this data does not include for gamma correction. I was just wondering if anyone could potentially shed some light on how to add the correction manually or if this could be added as a feature to NViSII directly. Thank you so much for the help!

Hi Abhishek,
You should never use gamma correction on a depth image. Gamma correction is a tone mapping process meant only for final color images.
For depth segmentations, I recommend saving images using either .exr or .hdr, as .png will lose precision.


Update name and URL of "OSS-EC NXP MPXA4250A 00000057"

This PR consists of two changes:

Change URL from https://github.com/RLL-Blue-Dragon/NXP_MPXA4250A_00000057.gi to https://github.com/RLL-Blue-Dragon/OSS-EC_NXP_MPXA4250A_00000057.git (companion to https://github.com/arduino/library-registry/pull/1885)
Change name from NXP_MPXA4250_BSL00000057 to OSS-EC NXP MPXA4250A 00000057 (resolves https://github.com/arduino/library-registry/issues/1893)

Since the name change operation on the database is actually a removal followed by automated re-indexing on the next job run, the URL update will occur as a matter of course. For this reason, the only operation required from the backend maintainer is a standard name change procedure.

I see the request from the library maintainer was closed, probably due to the error reported by the bot:
https://github.com/arduino/library-registry/pull/1885#issuecomment-1251748501
ERROR: Library name OSS-EC NXP MPXA4250A 00000057 not found in the Library Manager index. Library names are not allowed
       to change after being added to the index.
       See: https://github.com/arduino/library-registry/blob/main/FAQ.md#how-can-i-change-a-librarys-name
       (Rule LP018)

I will determine how to proceed and then take the appropriate action for this PR. Until then, I'll leave it open, but marked as "on hold".

Done in https://github.com/arduino/library-registry/pull/1885#issuecomment-1259455512


Bug of code in the book

Never mind, I think it's fixed in the latest edition

Yes, despite all my efforts, there were some errors in the first printed version of the book (see the errata page). Most were minor, but there were a few significant ones. I have fixed them in the book as well as in the notebooks. The digital and printed versions have been updated (the latest update was done earlier this week). Hopefully there are no significant errors left, but if you find some more, please don't hesitate to report them here on via the errata page above.
Thanks!


Could not collect tokens

Before creating an issue, first upgrade cfscrape with pip install -U cfscrape and see if you're still experiencing the problem. Please also confirm your Node version (node --version or nodejs --version) is version 10 or higher.
Make sure the website you're having issues with is actually using anti-bot protection by Cloudflare and not a competitor like Imperva Incapsula or Sucuri. And if you're using an anonymizing proxy, a VPN, or Tor, Cloudflare often flags those IPs and may block you or present you with a captcha as a result.
Please confirm the following statements and check the boxes before creating an issue:

[x] I've upgraded cfscrape with pip install -U cfscrape
[X] I'm using Node version 10 or higher
[X] The site protection I'm having issues with is from Cloudflare
[X] I'm not using Tor, a VPN, or an anonymizing proxy

Python version number
Run python --version and paste the output below:
Python 3.8.3

cfscrape version number
Run pip show cfscrape and paste the output below:
Version: 2.1.1

Code snippet involved with the issue

Complete exception and traceback
(If the problem doesn't involve an exception being raised, leave this blank)
ERROR:root:'https://beta.betonline.ag' returned an error. Could not collect tokens.

URL of the Cloudflare-protected page
https://beta.betonline.ag
URL of Pastebin/Gist with HTML source of protected page
print scraper.get_tokens('https://beta.betonline.ag')

got it, sorry!


Disable flaky test on Windows

What type of PR is this:
/kind tests
What does this PR do / why we need it:
This test fails on Windows because of the terminal emulator behaviour.
Which issue(s) this PR fixes:
Fixes #6327
PR acceptance criteria:

[ ] Unit test

[ ] Integration test

[ ] Documentation

How to test changes / Special notes to the reviewer:

/lgtm

/override ci/prow/v4.11-integration-e2e
Pass on IBM Cloud


update video inside about page

i want watch the video

Fixed by removing the video as we cannot remember what video it was :)


Advice Please on upgrade to 1.5

I have been using localForage v1.3 for over two years with no issues for an app that is available on IOS, Android, Chrome Web Store, MacOS and Windows 10.
I am about to upgrade to localForage v1.5 and I note that the primary new feature is that on Safari 10+/Mobile Safari 10.1+ the default is to now used IndexedDB rather than WebSQL, and I understand defaults the opposite way for older versions of Safari.
I believe that for localForage v1.3, the default was to use IndexedDB if it existed, which is did on mobileSafari since IOS 8 even if it was unreliable. My app users therefore were using IndexedDB even it was unreliable, hence upgrading to v1.5 presents no problem, just the removal of the unreliability.
However what I would like some advice on now, is what I will need to do to support those of my existing user base who are still on IOS 8,9 and 10.0, when they get an app upgrade from me containing localForage v1.5? Presumably it will (from what I have read) no longer default to IndexedDB and rather it will default to WebSQL and they will no longer see their stored data.

With #723 (which is targeted for v1.5.1) we are planning to allow overriding the _support method of the internal drivers. Here is the code of a WIP plugin that will offer compatibility with LF1.4 Safari IndexDB detection.

I believe that for localForage v1.3, the default was to use IndexedDB if it existed, which is did on mobileSafari since IOS 8 even if it was unreliable.

Actually, lf 1.3 does include a safari check. And that's also true from lf 1.3.0.
So I guess you should follow the same process as from upgrading from lf 1.4 .

In other words, you will be able to use the localForage-compatibility-1-4 plugin when it is released to upgrade to v1.5.1.

@SteveBrooker localForage-compatibility-1-4 was just released to resolve the safari migration issue. Please check it out, I hope that you will like it.
Closing this for now. Feel free to re-open in any case.


Unable to build Dockerfile - fails on 'dnf install podman'

Bug Description
Running this command fails:
docker build -t sometag --build-arg release_tag=1.2.0 --build-arg preflight_commit=cabba9e .
# snip
#12 3.857 Error:
#12 3.857  Problem: conflicting requests
#12 3.857   - nothing provides libsubid.so.3()(64bit) needed by podman-2:4.0.2-6.module+el8.6.0+14877+f643d2d6.x86_64
#12 3.857 (try to add '--skip-broken' to skip uninstallable packages or '--nobest' to use not only best candidate packages)

Version and Command Invocation
n/a
Steps to Reproduce:
Run docker build -t sometag --build-arg release_tag=1.2.0 --build-arg preflight_commit=cabba9e .
Expected Result
I would expect the command to succeed and build an image.
Actual Result
See error message above in summary.
Additional Context
I think this is a general issue, as I can't even dnf install podman from within the latest ubi8 image, but I'm not sure where else to report this.

As you said, this is not a preflight problem. I am able to reproduce it. File a bug in Bugzilla.

Thanks for the pointer @bcrochet

FYI anyone looking: https://bugzilla.redhat.com/show_bug.cgi?id=2084179

I see this is affecting builds inside this repository as well now, e.g.: https://github.com/redhat-openshift-ecosystem/openshift-preflight/runs/6393577883?check_suite_focus=true


6.0 Feedback: robot ignoring delay() commands in Python protocols

Overview
On v5.1.0-beta.0 of the robot server, all delay() commands are ignored. Downgrading to 5.0.2 resolves the issue.
Current Behavior
When running a Python protocol on a robot running v5.1.0-beta.0 of the robot server, delay() commands have no effect. They appear in the run log for the protocol, but all other actions are performed as quickly as possible, with no delays.
Expected Behavior
Each delay() action should pause the robot's movements for exactly as long as specified and as shown in the run log.
Steps To Reproduce

Import a protocol that includes delay() commands.
move.py.zip

Run the protocol on a robot running the beta server.

Downgrading to robot server 5.0.2 restores the expected behavior. Upgrading to the beta again reintroduces the bug.
Operating system
Mac
Robot setup or anything else?
Robot Server Version
v5.1.0-beta.0
Robot Serial Number
OT2CEP20210812R11
Firmware Version
v1.1.0-25e5cea

@SyntaxColoring I reproduced this from edge.

Also reproduced. Looking into this now.

Delays respected upon retesting.


Version with brackets breaks APA bibliography

When I render the bibliography for the following CSL-JSON
{
  "id": "ID1",

  "type": "chapter",
  "title": "Catalogue of the Alucitoidea of the World",
  "DOI": "10.1093/database/baw125",
  "author": [
    {
      "family": "Hobern",
      "given": "Donald"
    },
    {
      "family": "Gielis",
      "given": "C."
    }
  ],
  "editor": [
    {
      "family": "Hobern",
      "given": "Donald"
    }
  ],
  "container-title": "Catalogue of Life Checklist",
  "issued": {
    "date-parts": [
      [
        2021,
        7,
        18
      ]
    ]
  },
  "version": "<IP_ADDRESS> (18 Jul 2021)"
}

with the 7th APA style from Zotero using Frank Bennetts citeproc-js v1.4.61 I yield:

Hobern, D., & Gielis, C. (2021). Catalogue of the Alucitoidea of the World. In D. Hobern (Ed.), Catalogue of Life Checklist (<IP_ADDRESS> (18 Jul 2021)). https://doi.org/10.1093/database/baw125

When I do the same with the latest v3 snapshot from citeproc-java the closing brackets from the version are omitted and some superflous ampersand is added to the single editor:

Hobern, D., & Gielis, C. (2021). Catalogue of the Alucitoidea of the World. In D. Hobern (Ed.), & , Catalogue of Life Checklist (<IP_ADDRESS> (18 Jul 2021). https://doi.org/10.48580/e456fgvzb

I've fixed the issue with the closing parenthesis in https://github.com/michel-kraemer/citeproc-java/commit/503d1fbf5b1a825443727a6901e5b1aea4808f64. The superfluous ampersand was already fixed in 6ee967d8db9b11797b708373df85e4734632fcd0.

This issue is now fixed in citeproc-java v3.0.0-alpha.3


TIDE Help | AttributeError: 'DataFrame' object has no attribute 'temporal_cols'

Hi guys!
I just started to understand NeuralForecast, everything is very convenient, but it is not clear, what temporal_cols are required? I didn't find anything like that in the documentation, my dataset structure seems to be normal.
Please help! I'm kind of new to ML/NeuralForecast at the moment.
Columns:
Index(['ds', 'open', 'high', 'low', 'close', 'volume', 'kama', 'y'], dtype='object')
Dataset:
ds     open     high  ...   volume          kama        y
22    2023-12-15 01:50:00  42999.9  43017.2  ...  101.493  42998.398417 -0.00049
23    2023-12-15 01:55:00  42975.3  43007.5  ...  154.853  42998.489312  0.00021
24    2023-12-15 02:00:00  43006.6  43036.6  ...   85.132  42998.604067  0.00027
25    2023-12-15 02:05:00  43003.0  43026.9  ...   92.799  42998.049372 -0.00129
26    2023-12-15 02:10:00  42962.0  42962.0  ...  460.089  42989.881402 -0.01900
Code:
import numpy as np
import pandas as pd
import talib
from neuralforecast.auto import AutoTiDE

config = dict(max_steps=2, val_check_steps=1, input_size=12)
model = AutoTiDE(h=3, num_samples=10, cpus=1, config=config)  # Specify the time column

dataset = pd.read_csv('Datasets/BTCUSDT_5m.csv')
dataset['kama'] = talib.KAMA(dataset['close'], timeperiod=21)
dataset['kslope'] = np.round(np.insert(np.diff(dataset['kama']), 0, 0) / dataset['kama'] * 100, 5)
dataset.rename(columns={'timestamp': 'ds', 'kslope': 'y'}, inplace=True)
dataset['ds'] = pd.to_datetime(dataset['ds'])
dataset.dropna(inplace=True)

model.fit(dataset=dataset)
y_hat = model.predict(dataset=dataset)

Errors:
--> AttributeError: 'DataFrame' object has no attribute 'temporal_cols'
2024-05-12 17:58:16,701
ERROR tune_controller.py:1331 -- Trial task failed for trial _train_tune_58054_00004
--> 2024-05-12 17:58:16,834	WARNING experiment_analysis.py:558 -- Could not find best trial. Did you pass the correct `metric` parameter?

Traceback:
(_train_tune pid=90050) Seed set to 1
2024-05-12 17:58:16,695	ERROR tune_controller.py:1331 -- Trial task failed for trial _train_tune_58054_00006
.....
  File "/Users/ryzzhkovtom/miniconda3/envs/MLLab_LightGBM/lib/python3.9/site-packages/neuralforecast/common/_base_auto.py", line 209, in _train_tune
    _ = self._fit_model(
  File "/Users/ryzzhkovtom/miniconda3/envs/MLLab_LightGBM/lib/python3.9/site-packages/neuralforecast/common/_base_auto.py", line 357, in _fit_model
    model = model.fit(
  File "/Users/ryzzhkovtom/miniconda3/envs/MLLab_LightGBM/lib/python3.9/site-packages/neuralforecast/common/_base_windows.py", line 651, in fit
    return self._fit(
  File "/Users/ryzzhkovtom/miniconda3/envs/MLLab_LightGBM/lib/python3.9/site-packages/neuralforecast/common/_base_model.py", line 188, in _fit
    self._check_exog(dataset)
  File "/Users/ryzzhkovtom/miniconda3/envs/MLLab_LightGBM/lib/python3.9/site-packages/neuralforecast/common/_base_model.py", line 146, in _check_exog
    temporal_cols = set(dataset.temporal_cols.tolist())
  File "/Users/ryzzhkovtom/miniconda3/envs/MLLab_LightGBM/lib/python3.9/site-packages/pandas/core/generic.py", line 6299, in __getattr__
    return object.__getattribute__(self, name)
AttributeError: 'DataFrame' object has no attribute 'temporal_cols'

Hey @da1k-matter do you remember what was the solution? Having the same problem right now.

You need to wrap the model in a NeuralForecast instance as is done here. They don't work directly on dataframes.


Add serde default attribute to non-required, non-Option fields

Using #serde[*with] seems to cause problems with deserialization if the default tag is not also specified. Places where this is used should updated to add the default tag.

Actually when fixing this problem for /sync I looked for and didn't find any other occurrences. But it won't hurt to double-check that.

I also checked, and it looks good. I'll close this.


AttributeError: '_Undefined' object has no attribute 'items'

Hi all,
I've run qsiprep (v 0.19.1) followed by the following command. The program gets stuck at calc_connectivity. qsiprep does not seem to read pipeline.json?
  qsiprep-docker /bids  \
      /bids/derivatives \
      participant \
      --recon-only --recon_spec /bids/files/pipeline.json \
      --recon_input /bids/derivatives/qsiprep \
      --fs-license-file /license.txt \
      --n_cpus 8 --skip_bids_validation -w /bids/derivatives/work

The crash report looks like this. I get the same error with --recon_spec dsi_studio_qgi
    Node: qsirecon_wf.sub-X_dsistudio_pipeline.sub_X_ses_1_space_T1w_desc_preproc_recon_wf.streamline_connectivity.calc_connectivity
    Working directory: /out/work/qsirecon_wf/sub-X_dsistudio_pipeline/sub_X_ses_1_space_T1w_desc_preproc_recon_wf/streamline_connectivity/calc_connectivity

    Node inputs:

    args = <undefined>
    atlas_config = <undefined>
    atlas_configs = <undefined>
    atlas_name = <undefined>
    connectivity = <undefined>
    connectivity_type = pass,end
    connectivity_value = ncount,gfa
    environ = {}
    fa_threshold = <undefined>
    fiber_count = <undefined>
    initial_dir = <undefined>
    input_fib = <undefined>
    interpo_angle = <undefined>
    interpolation = <undefined>
    max_length = <undefined>
    min_length = <undefined>
    num_threads = 3
    random_seed = <undefined>
    seed_count = <undefined>
    seed_file = <undefined>
    seed_plan = <undefined>
    smoothing = <undefined>
    step_size = <undefined>
    thread_count = 1
    to_export = <undefined>
    trk_file = <undefined>
    turning_angle = <undefined>

    Traceback (most recent call last):
      File "/usr/local/miniconda/lib/python3.8/site-packages/nipype/pipeline/plugins/multiproc.py", line 67, in run_node
        result["result"] = node.run(updatehash=updatehash)
      File "/usr/local/miniconda/lib/python3.8/site-packages/nipype/pipeline/engine/nodes.py", line 527, in run
        result = self._run_interface(execute=True)
      File "/usr/local/miniconda/lib/python3.8/site-packages/nipype/pipeline/engine/nodes.py", line 645, in _run_interface
        return self._run_command(execute)
      File "/usr/local/miniconda/lib/python3.8/site-packages/nipype/pipeline/engine/nodes.py", line 771, in _run_command
        raise NodeExecutionError(msg)
    nipype.pipeline.engine.nodes.NodeExecutionError: Exception raised while executing Node calc_connectivity.

    Traceback:
    Traceback (most recent call last):
    File "/usr/local/miniconda/lib/python3.8/site-packages/nipype/interfaces/base/core.py", line 397, in run
    runtime = self._run_interface(runtime)
    File "/usr/local/miniconda/lib/python3.8/site-packages/qsiprep/interfaces/dsi_studio.py", line 459, in _run_interface
    for atlasnum, (atlas_name, atlas_config) in enumerate(atlas_configs.items(), start=1):
    AttributeError: '_Undefined' object has no attribute 'items'

Appreciate your help!

Node inputs:
args =
atlas_config =
atlas_configs =
atlas_name =
connectivity =
connectivity_type = pass,end
connectivity_value = ncount,gfa
environ = {}
fa_threshold =
fiber_count =
initial_dir =
input_fib =
interpo_angle =
interpolation =
max_length =
min_length =
num_threads = 3
random_seed =
seed_count =
seed_file =
seed_plan =
smoothing =
step_size =
thread_count = 1
to_export =
trk_file =
turning_angle =

When I ran QSIprep on ABCD data it created a folder structure:
/qsiprep/sub-/
/qsiprep/sub-/anat/ # contains all but one file ending in mode-image_xfm.txt
/qsiprep/sub-/ses-/anat/ # contains only the file ending in mode-image_xfm.txt
/qsiprep/sub-/ses-/dwi/
/qsiprep/sub-/ses-/figures/
Before running the reconstruction, I moved /qsiprep/sub-/anat/ to /qsiprep/sub-/ses-/anat/ Running qsiprep with --recon-only then resulted in the error above. Restoring the folder structure resolved the issue.

could you post the content of pipeline.json?

Hi all,
I'm getting the same error trying to run --recon_spec dsi_studio_gqi. I have no "anat" folder in my qsiprep output, as I'm analyzing phantom data and used --dwi-only for the preprocessing.
Here is the command I'm using (from inside a bash script):
singularity run --cleanenv \
--bind ${BIDSINDATA}:/recon_in \
--bind ${BIDSOUTDATA}:/recon_out \
--bind /home/Software/FreeSurfer/freesurfer-7.3.2/freesurfer:/fs_license \
/home/Software/qsiPrepS-0.19.1 \
/recon_in \
/recon_out \
participant \
--participant_label ${SUBJECT} \
-w /recon_out/work_${SUBJECT} \
--fs-license-file /fs_license/license.txt \
--recon-only \
--recon-spec dsi_studio_gqi \
--recon-input /recon_in

And here is the error message:
Node: qsirecon_wf.sub-02_dsistudio_pipeline.sub_02_ses_01_space_T1w_desc_preproc_recon_wf.streamline_connectivity.calc_connectivity
Working directory: /recon_out/work_02/qsirecon_wf/sub-02_dsistudio_pipeline/sub_02_ses_01_space_T1w_desc_preproc_recon_wf/streamline_connectivity/calc_connectivity

Node inputs:

args = <undefined>
atlas_config = <undefined>
atlas_configs = <undefined>
atlas_name = <undefined>
connectivity = <undefined>
connectivity_type = pass,end
connectivity_value = count,ncount,mean_length,gfa
environ = {}
fa_threshold = <undefined>
fiber_count = <undefined>
initial_dir = <undefined>
input_fib = <undefined>
interpo_angle = <undefined>
interpolation = <undefined>
max_length = <undefined>
min_length = <undefined>
num_threads = 8
random_seed = <undefined>
seed_count = <undefined>
seed_file = <undefined>
seed_plan = <undefined>
smoothing = <undefined>
step_size = <undefined>
thread_count = 1
to_export = <undefined>
trk_file = <undefined>
turning_angle = <undefined>

Traceback (most recent call last):
  File "/usr/local/miniconda/lib/python3.8/site-packages/nipype/pipeline/plugins/multiproc.py", line 67, in run_node
    result["result"] = node.run(updatehash=updatehash)
  File "/usr/local/miniconda/lib/python3.8/site-packages/nipype/pipeline/engine/nodes.py", line 527, in run
    result = self._run_interface(execute=True)
  File "/usr/local/miniconda/lib/python3.8/site-packages/nipype/pipeline/engine/nodes.py", line 645, in _run_interface
    return self._run_command(execute)
  File "/usr/local/miniconda/lib/python3.8/site-packages/nipype/pipeline/engine/nodes.py", line 771, in _run_command
    raise NodeExecutionError(msg)
nipype.pipeline.engine.nodes.NodeExecutionError: Exception raised while executing Node calc_connectivity.

Traceback:
	Traceback (most recent call last):
	  File "/usr/local/miniconda/lib/python3.8/site-packages/nipype/interfaces/base/core.py", line 397, in run
	    runtime = self._run_interface(runtime)
	  File "/usr/local/miniconda/lib/python3.8/site-packages/qsiprep/interfaces/dsi_studio.py", line 459, in _run_interface
	    for atlasnum, (atlas_name, atlas_config) in enumerate(atlas_configs.items(), start=1):
	AttributeError: '_Undefined' object has no attribute 'items'

Thanks for the help!

Hi @keithgjones, you won't be able to run that pipeline as-is without anatomical data. The transform from the anatomical data to template space is used to get atlases aligned to the dwis so you can calculate connectivity. You can edit the json file here to exclude the connectivity estimation (you'll also have to change line 4 to "atlases": [],)

Here's the content of pipeline.json:
  {
      "name": "dsistudio_pipeline",
      "space": "T1w",
      "atlases": ["schaefer400", "gordon333"],
      "nodes": [
        {
          "name": "dsistudio_gqi",
          "software": "DSI Studio",
          "action": "reconstruction",
          "input": "qsiprep",
          "output_suffix": "gqi",
          "parameters": {"method": "gqi"}
        },
        {
          "name": "scalar_export",
          "software": "DSI Studio",
          "action": "export",
          "input": "dsistudio_gqi",
          "output_suffix": "gqiscalar"
        },
        {
          "name": "tractography",
          "software": "DSI Studio",
          "action": "tractography",
          "input": "dsistudio_gqi",
          "parameters": {
            "turning_angle": 35,
            "smoothing": 0.0,
            "step_size": 1.0,
            "min_length": 30,
            "max_length": 250,
            "seed_plan": 0,
            "interpolation": 0,
            "initial_dir": 2,
            "fiber_count": 5000000
          }
        },
        {
          "name": "streamline_connectivity",
          "software": "DSI Studio",
          "action": "connectivity",
          "input": "tractography",
          "output_suffix": "gqinetwork",
          "parameters": {
            "connectivity_value": "ncount,gfa",
            "connectivity_type": "pass,end"
          }
        }
      ]
    }


Can't remove <% yield p = np %> from existing partial.

Before:

Steps to reproduce:

Clone https://github.com/bullet-train-co/bullet_train
Get it up and running (e.g. bin/setup, bin/dev, etc.)
Run mkdir local; git clone git@github.com:bullet-train-co/nice_partials.git local/nice_partials
Add gem "nice_partials", path: "local/nice_partials" to Gemfile
Run bin/develop and select the bullet_train-themes-light Ruby gem.
Open local/bullet_train-themes-light.
Edit app/views/themes/light/_box.html.erb
Remove <% yield p = np %>
Experience bug.

After:

(Also, if I leave <% yield p = np %> in place, everything continues to work fine.)


Allow bracket pattern customization

allow tokens to replace (...) bracket enclosures
I have my own syntax highlighter and use [..] brackets for debug features
It looks like this might be an easy change

It is fairly easy

[ ] allow customization of rdebugX strings

[ ] allow custom tokens for debug levels

			if (_showDebugLevel) {
				switch (_lastDebugLevel) {
				case PROFILER:
					show.concat("(P"); // tokenize this whole string eg. "[E],[ERROR]"


Add example for Bigquery streaming sink

Be sure to do all of the following to help us incorporate your contribution
quickly and easily:

[ ] Make sure the PR title is formatted like:
[BEAM-<Jira issue #>] Description of pull request
[ ] Make sure tests pass via mvn clean verify.
[ ] Replace <Jira issue #> in the title with the actual Jira issue
number, if there is one.
[ ] If this contribution is large, please file an Apache
Individual Contributor License Agreement.

R: @aaltay PTAL
I think it'll be good to change the example to write a column for the window timestamp as well but that can done in a followup PR. Thoughts?

Changes Unknown when pulling 5eaff01a898bd1cda684ec8b877871c789f4bfd0 on sb2nov:BEAM-BQ-streaming-example into ** on apache:master**.

@aaltay PTAL again

Could you look at the test failures?

Thanks, fixed it.

Coverage decreased (-0.003%) to 70.839% when pulling 960f7ab1ec57bcdf2247d0ec97f35ad058fd612a on sb2nov:BEAM-BQ-streaming-example into 3746d4cadca034d6c45436efb0fc71304d093f91 on apache:master.

LGTM


Authentication failed - logging into gmail account

Hello,
No matter what i try to configure in the domain configuration of gmail i cannot login using my gmail credentials. It always says Authentication failed. My own mail server just works fine using the same domain setup.
Here's the mail log:
Jun 11 12:34:17 mail dovecot: imap-login: Login<EMAIL_ADDRESS>method=PLAIN, rip=<IP_ADDRESS>, lip=<IP_ADDRESS>, mpid=9202, TLS, TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits) Jun 11 12:34:17 mail dovecot: imap(ninetailz@xxx.xx): Disconnected: Logged out in=504 out=13888 Jun 11 12:34:19 mail dovecot: imap-login: Login<EMAIL_ADDRESS>method=PLAIN, rip=<IP_ADDRESS>, lip=<IP_ADDRESS>, mpid=9204, TLS, TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits) Jun 11 12:34:19 mail dovecot: imap(ninetailz@xxx.xx): Disconnected: Logged out in=504 out=4106 Jun 11 12:34:21 mail dovecot: imap-login: Login<EMAIL_ADDRESS>method=PLAIN, rip=<IP_ADDRESS>, lip=<IP_ADDRESS>, mpid=9206, TLS, TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits) Jun 11 12:34:21 mail dovecot: imap(ninetailz@xxx.xx): Disconnected: Logged out in=504 out=8062 Jun 11 12:34:23 mail dovecot: imap-login: Login<EMAIL_ADDRESS>method=PLAIN, rip=<IP_ADDRESS>, lip=<IP_ADDRESS>, mpid=9208, TLS, TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits) Jun 11 12:34:23 mail dovecot: imap(ninetailz@xxx.xx): Disconnected: Logged out in=506 out=6040 Jun 11 12:34:25 mail dovecot: imap-login: Login<EMAIL_ADDRESS>method=PLAIN, rip=<IP_ADDRESS>, lip=<IP_ADDRESS>, mpid=9210, TLS, TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits) Jun 11 12:34:25 mail dovecot: imap(ninetailz@xxx.xx): Disconnected: Logged out in=506 out=28570 Jun 11 12:34:27 mail dovecot: imap-login: Login<EMAIL_ADDRESS>method=PLAIN, rip=<IP_ADDRESS>, lip=<IP_ADDRESS>, mpid=9212, TLS, TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits) Jun 11 12:34:27 mail dovecot: imap(ninetailz@xxx.xx): Disconnected: Logged out in=506 out=27589 Jun 11 12:34:29 mail dovecot: imap-login: Login<EMAIL_ADDRESS>method=PLAIN, rip=<IP_ADDRESS>, lip=<IP_ADDRESS>, mpid=9214, TLS, TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits) Jun 11 12:34:29 mail dovecot: imap(ninetailz@xxx.xx): Disconnected: Logged out in=82 out=725 Jun 11 12:34:29 mail dovecot: imap-login: Login<EMAIL_ADDRESS>method=PLAIN, rip=<IP_ADDRESS>, lip=<IP_ADDRESS>, mpid=9216, TLS, TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits) Jun 11 12:34:29 mail dovecot: imap(ninetailz@xxx.xx): Disconnected: Logged out in=70 out=723 Jun 11 12:34:29 mail dovecot: imap-login: Login<EMAIL_ADDRESS>method=PLAIN, rip=<IP_ADDRESS>, lip=<IP_ADDRESS>, mpid=9219, TLS, TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits) Jun 11 12:34:29 mail dovecot: imap-login: Login<EMAIL_ADDRESS>method=PLAIN, rip=<IP_ADDRESS>, lip=<IP_ADDRESS>, mpid=9220, TLS, TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits) Jun 11 12:34:29 mail dovecot: imap(ninetailz@xxx.xx): Disconnected: Logged out in=241 out=823 Jun 11 12:34:29 mail dovecot: imap(ninetailz@xxx.xx): Disconnected: Logged out in=344 out=34306 Jun 11 12:34:49 mail dovecot: imap-login: Login<EMAIL_ADDRESS>method=PLAIN, rip=<IP_ADDRESS>, lip=<IP_ADDRESS>, mpid=9222, TLS, TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits) Jun 11 12:34:49 mail dovecot: imap(ninetailz@xxx.xx): Disconnected: Logged out in=920 out=482 Jun 11 12:34:49 mail dovecot: imap-login: Login<EMAIL_ADDRESS>method=PLAIN, rip=<IP_ADDRESS>, lip=<IP_ADDRESS>, mpid=9225, TLS, TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits) Jun 11 12:34:49 mail dovecot: imap(ninetailz@xxx.xx): Disconnected: Logged out in=90 out=906 Jun 11 12:35:14 mail dovecot: imap-login: Login<EMAIL_ADDRESS>method=PLAIN, rip=<IP_ADDRESS>, lip=<IP_ADDRESS>, mpid=9227, TLS, TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits) Jun 11 12:35:14 mail dovecot: imap(ninetailz@xxx.xx): Disconnected: Logged out in=89 out=907 Jun 11 12:35:14 mail dovecot: imap-login: Login<EMAIL_ADDRESS>method=PLAIN, rip=<IP_ADDRESS>, lip=<IP_ADDRESS>, mpid=9229, TLS, TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits) Jun 11 12:35:14 mail dovecot: imap(ninetailz@xxx.xx): Disconnected: Logged out in=1024 out=1278 Jun 11 12:35:14 mail dovecot: imap-login: Login<EMAIL_ADDRESS>method=PLAIN, rip=<IP_ADDRESS>, lip=<IP_ADDRESS>, mpid=9232, TLS, TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits) Jun 11 12:35:14 mail dovecot: imap(ninetailz@xxx.xx): Disconnected: Logged out in=90 out=906 Jun 11 12:35:21 mail dovecot: imap-login: Login<EMAIL_ADDRESS>method=PLAIN, rip=<IP_ADDRESS>, lip=<IP_ADDRESS>, mpid=9234, TLS, TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits) Jun 11 12:35:21 mail dovecot: imap(ninetailz@xxx.xx): Disconnected: Logged out in=584 out=2326 Jun 11 12:35:22 mail dovecot: imap-login: Login<EMAIL_ADDRESS>method=PLAIN, rip=<IP_ADDRESS>, lip=<IP_ADDRESS>, mpid=9236, TLS, TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits) Jun 11 12:35:22 mail dovecot: imap(ninetailz@xxx.xx): Disconnected: Logged out in=503 out=2057 Jun 11 12:35:27 mail dovecot: imap-login: Login<EMAIL_ADDRESS>method=PLAIN, rip=<IP_ADDRESS>, lip=<IP_ADDRESS>, mpid=9238, TLS, TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits) Jun 11 12:35:27 mail dovecot: imap(ninetailz@xxx.xx): Disconnected: Logged out in=192 out=1329 Jun 11 12:35:27 mail dovecot: imap-login: Login<EMAIL_ADDRESS>method=PLAIN, rip=<IP_ADDRESS>, lip=<IP_ADDRESS>, mpid=9240, TLS, TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits) Jun 11 12:35:27 mail dovecot: imap(ninetailz@xxx.xx): Disconnected: Logged out in=112 out=1297 Jun 11 12:35:57 mail dovecot: imap-login: Login<EMAIL_ADDRESS>method=PLAIN, rip=<IP_ADDRESS>, lip=<IP_ADDRESS>, mpid=9300, TLS, TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits) Jun 11 12:35:57 mail dovecot: imap(ninetailz@xxx.xx): Disconnected: Logged out in=55 out=923 Jun 11 12:36:58 mail dovecot: imap-login: Login<EMAIL_ADDRESS>method=PLAIN, rip=<IP_ADDRESS>, lip=<IP_ADDRESS>, mpid=9331, TLS, TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits) Jun 11 12:36:58 mail dovecot: imap(thunderbolt@xxx.xx): Disconnected: Logged out in=11 out=423 Jun 11 12:36:59 mail dovecot: imap-login: Login<EMAIL_ADDRESS>method=PLAIN, rip=<IP_ADDRESS>, lip=<IP_ADDRESS>, mpid=9333, TLS, TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits) Jun 11 12:36:59 mail dovecot: imap(thunderbolt@xxx.xx): Disconnected: Logged out in=80 out=1338 Jun 11 12:37:00 mail dovecot: imap-login: Login<EMAIL_ADDRESS>method=PLAIN, rip=<IP_ADDRESS>, lip=<IP_ADDRESS>, mpid=9335, TLS, TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits) Jun 11 12:37:00 mail dovecot: imap(thunderbolt@xxx.xx): Disconnected: Logged out in=110 out=1305 Jun 11 12:37:02 mail dovecot: imap-login: Login<EMAIL_ADDRESS>method=PLAIN, rip=<IP_ADDRESS>, lip=<IP_ADDRESS>, mpid=9337, TLS, TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits) Jun 11 12:37:02 mail dovecot: imap(thunderbolt@xxx.xx): Disconnected: Logged out in=334 out=1269 Jun 11 12:37:05 mail dovecot: imap-login: Login<EMAIL_ADDRESS>method=PLAIN, rip=<IP_ADDRESS>, lip=<IP_ADDRESS>, mpid=9339, TLS, TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits) Jun 11 12:37:05 mail dovecot: imap(thunderbolt@xxx.xx): Disconnected: Logged out in=55 out=832
Here's some screenshots:
http://i.imgur.com/YFSAFc5.png
http://imgur.com/a/udOxD
I don't know how to solve this, please help
Thanks,
Ninetailz

Have you tried enabling Gmail's "less secure apps access" as described here?
https://support.google.com/accounts/answer/6010255?hl=en

Still the same.....

What happens when you press "Test" on this screen? http://imgur.com/a/udOxD

It works

I have the same problem, can't login to my gmail account - try other mail services and all working but not gmail. I'll try Gmail's "less secure apps access"  - don't work for me, but finally i found in logs this: https://support.google.com/mail/answer/78754 and the 3th options about "DisplayUnlockCaptcha". When i do this i can login on my gmail !! Yay! ;))
Please tell if this help you - maybe someone need this too ;)  Hope this can help.
PS Sorry for my bad english ;)

as serfmen said,
if your getting wrong pass or username,
try this:
https://support.google.com/mail/answer/78754
it was the DisplayUnlockCaptcha for me. try all of em til it works. if it works on first option, then that was the issue.
if non of the options works, i don't know what to do.

Unfortunately, App password is no longer available.

App Passwords are going to be deprecatedlater this year. https://support.google.com/accounts/answer/6010255?hl=en&sjid=12187622552632237587-EU


File "invert_v2.py", line 32     parser.add_argument('--learning_rate', type=float, default=0.01,          ^ SyntaxError: invalid syntax

Getting this kind of error, Please Help me Sir/Madam

It looks like the error is caused by the version of python and interpreter (I use python 3.6 and Anaconda). For quick start, you can run the colab demo instead.

Sir I Run in Colab only sir But i got this kind of error, any other suggestion sir ? Please help me

Hi, @Kesavan-Raman
The right parenthesis was accidentally deleted when I cleaned up the code. I have fixed it. Sorry for the inconvience. Please try again.
If encountering the problem of 'No pre-trained weights will be loaded!', please change MODEL_DIR = os.path.join('models', 'pretrain') to MODEL_DIR = os.path.join('idinvert_pytorch', 'models', 'pretrain') in the Colab.

Thank you Sir It's Now working 😇😇

Thank you Sir It's Now working 😇😇


Update CDK and TF "vs" pages to include Automation API

Now that we've launched Automation API (https://www.pulumi.com/blog/automation-api/) we should update our comparison guides to highlight Pulumi's strengths in end to end software-driven automation support.

@spara  do you have any cycles to help out here?


Downloading Linux on Chromebook; cannot run command "sudo startxfce4". Please Help!

Please paste the output of the following command here: sudo edit-chroot -all

name: xenial
encrypted: no
Entering /mnt/stateful_partition/crouton/chroots/xenial...
crouton: version 1-20190902190258~master:9a594a66
release: xenial
architecture: armhf
xmethod: xorg
targets: xfce
host: version 11316.165.0 (Official Build) stable-channel daisy_spring
kernel: Linux localhost 3.8.11 #1 SMP Sun Mar 3 22:44:20 PST 2019 armv7l armv7l armv7l GNU/Linux
freon: yes
Unmounting /mnt/stateful_partition/crouton/chroots/xenial...
Please describe your issue:
I am trying to do coursework for Flatiron and when trying to open my IDE inside of the webpage, I am greeted with a message that says "Google Chrome OS can't open this page". I followed this (https://www.youtube.com/watch?v=QB9puwi2qTo) video exactly to gain access to Linux hoping that would fix this issue. That all seemed to work well until the “sudo startxfce4” command when it failed and said:
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(++) Log file: "/tmp/Xorg.crouton.1.log", Time: Wed Sep  4 14:26:29 2019
(==) Using system config directory "/usr/share/X11/xorg.conf.d"
Error org.freedesktop.DBus.Error.ServiceUnknown: The name org.chromium.LibCrosService was not provided by any .service files
method return time=1567621590.112735 sender=:1.11 -> destination=:1.56 serial=989 reply_serial=2
boolean true
MESA-LOADER: failed to retrieve device information
gbm: failed to open any driver (search paths /usr/lib/arm-linux-gnueabihf/dri:${ORIGIN}/dri:/usr/lib/dri)
gbm: Last dlopen error: /usr/lib/dri/exynos_dri.so: cannot open shared object file: No such file or directory
failed to load driver: exynos
EGL_MESA_drm_image required.
(EE)
Fatal server error:
(EE) AddScreen/ScreenInit failed for driver 1
(EE)
(EE)
Please consult the The X.Org Foundation support
at http://wiki.x.org
for help.
(EE) Please also check the log file at "/tmp/Xorg.crouton.1.log" for additional information.
(EE)
Error org.freedesktop.DBus.Error.ServiceUnknown: The name org.chromium.LibCrosService was not provided by any .service files
method return time=1567621590.656952 sender=:1.11 -> destination=:1.58 serial=990 reply_serial=2
boolean true
(EE) Server terminated with error (1). Closing log file.
/usr/bin/xinit: giving up
/usr/bin/xinit: unable to connect to X server: Connection refused
/usr/bin/xinit: server error
Unmounting /mnt/stateful_partition/crouton/chroots/xenial...
Please help!
If known, describe the steps to reproduce the issue:

I'm having a very simlar problem. Have you tried the common issues process from the wiki? (https://github.com/dnschneid/crouton/wiki/Common-issues-and-reporting) Also, did you follow the process from #4026 ? Nothing from either helped me unfortunately, but maybe they'd help you.

@zclay1,
That's a nice simple video that's easy to understand but it doesn't go into some of the other options available like xiwi probably for good reason as it does get more complicated.
The ARM devices like your HP Chromebook 11 G1 seem to have problems with the xorg xmethod.
I would suggest adding the 'xiwi' xmethod and then try launching your xfce4 desktop.
For your chroot you can add xiwi using the update method with the following:

sudo crouton -n xenial -t xiwi -u

As noted in the installation you'll also have to add the 'crouton integration' extension
Hope this helps,
-DennisLfromGA


DateTimeFormat.prototype.resolveOptions may show fewer resolved options than present in formatted range

Example:
js> var dtf = new Intl.DateTimeFormat("en", {hour: "numeric", timeZone: "UTC"})
js> dtf.resolvedOptions()
({locale:"en", calendar:"gregory", numberingSystem:"latn", timeZone:"UTC", hourCycle:"h12", hour12:true, hour:"numeric"})
js> dtf.formatRange(0, 24*60*60*1000)
"1/1/1970, 12 AM \u2013 1/2/1970, 12 AM"

The resolved options imply that only the "hour" date-time field is used, but the formatted range contains additional date-time fields.
See also #21.

The resolvedOptions should bind to the object itself, not the result fo formatRange which may have different fields depending on the range you call the formatRange, which we do not know what they are when we create the object. I think we should not change the output of resolvedOptions since we do not have the information of what two dates until the formatRange is called.

The implementation constraints due to ICU resp. CLDR resp. ultimately UTS 35 are probably clear for implementers, but I don't really know what users will expect for the above case. They could expect that the output string only contains hours, for example when trying to format something like 10 PM - 6 AM. (*)
And as you've mentioned, the date-time fields in the output string depend on the input range. But that also means there's no way for users to determine upfront which fields are going to be used, which makes the whole feature kind of a black box.
I don't have a clear suggestion on how to move forward, the proposal champions and reviewers should evaluate possible options.

(*) There's this one weird trick you can use get that output: For whatever reason ICU no longer returns year, month, and day fields when the dates are in different eras:
js> var dtf = new Intl.DateTimeFormat("en", {hour: "numeric", timeZone: "UTC"})
js> dtf.formatRange(new Date("-000001-01-01T22:00Z"), new Date("+000001-01-01T06:00Z"))
"10 PM \u2013 6 AM"

It's unlikely someone stumbles across this issue for the Gregorian calendar, but maybe more likely to be noticeable for other calendars like the Japanese calendar:
js> var dtf = new Intl.DateTimeFormat("en", {hour: "numeric", timeZone: "UTC"})
js> dtf.formatRange(new Date("2010-01-01"), new Date("2020-01-01"))
"1/1/2010, 12 AM \u2013 1/1/2020, 12 AM"
js> var dtf = new Intl.DateTimeFormat("en-u-ca-japanese", {hour: "numeric", timeZone: "UTC"})
js> dtf.formatRange(new Date("2010-01-01"), new Date("2020-01-01"))
"12 AM \u2013 12 AM"

I think that there may be two different (but closely related) issues:

Should the resolved options contain the additional date-time fields used when formatting a date range?

There is no way for the user to determine upfront which fields are going to be displayed in the formatted string.

1)
I agree with Frank that the resolvedOptions should bind to the formatter object itself and not to the result of formatRange().
One of the reasons for this is that the current options returned by resolvedOptions() are computed when initializing the formatter and are used when selecting the best date pattern and the best set of date-range patterns. It is true that some of those date-range patterns may contain additional calendar fields not present in the resolvedOptions, but these fields are not relevant when initializing the formatter and do not “characterize” the formatter, instead they are only used to properly format some date-ranges.
Together with this, from a practical point of view, a second issue is that there doesn’t seem to be a straightforward way to include the additional calendar fields in resolvedOptions() because they are only known in formatRange(). It might be possible to either extend the current API or update resolveOptions() to return these additional calendar fields, but it is not clear to me if the gains of doing so are higher than the additional complexity this solution would bring.

2)
I agree that not having a way for the users to determine upfront which fields are going to be displayed or to control this makes this feature as some kind of blackbox. We discussed this during the last 402 working group meeting and examples such as 10 pm - 6 am were brought up.
One idea to potentially support this is to add an option which would allow users to indicate that they want to restrict the calendar fields used when formatting the date range to either a defined subset or to the options in the resolved options.
Now, currently ICU date-range formatting does act as a blackbox which means that changing this behavior will probably require an ICU/CLDR update so that the new behavior can be supported by implementers who use ICU.
Given this, the consensus at the last 402 working group meeting was to keep the current behavior as is and propose an update or an additional option on a follow-up proposal once ICU is updated.
Any thoughts?

There's this one weird trick you can use get that output: For whatever reason ICU no longer returns year, month, and day fields when the dates are in different eras

This behavior seems to be unexpected and it looks like an ICU bug.

(*) There's this one weird trick you can use get that output: For whatever reason ICU no longer returns year, month, and day fields when the dates are in different eras:
I file the issue in https://unicode-org.atlassian.net/browse/ICU-21222 . That is inconsistent.

2020-10-08 discussion: https://github.com/tc39/ecma402/blob/master/meetings/notes-2020-10-08.md#datetimeformatprototyperesolveoptions-may-show-fewer-resolved-options-than-present-in-formatted-range-22

Conclusion from the ECMA-402 meeting (2020-10-08):
Issue 1)
The current resolvedOptions would not allow us to return the additional date-time fields added by range formatting. We should not block the current proposal, but should explore this in a followup proposal. Alternatives to resolve this could be to add an extra API or to extend formateRangeToParts to return this information (by adding an additional field that indicates the calendar field's width).
Issue 2)
We should keep the current behavior for this proposal, as we are formatting JS dates (which are timestamps). We can add support to drop fields when supporting Temporal (e.g. formatting a range of Temporal.Times).


The following error occurred when attempting to publish your file: Cannot read property 'error' of undefined

When I try to upload the video
App | 0.19.2
Daemon (lbrynet) | 0.18.0

@RedbHawk we have this filed under the app https://github.com/lbryio/lbry-app/issues/874
Please try lowering your bid amount, see lbry.io/faq/how-to-publish for more info.


Fixed wrong command

[x] Changes have been thoroughly tested to not break existing functionality.
[x] New functionality has been documented or existing documentation has been updated to reflect changes.
[x] Visual changes are explained in the PR description using a screenshot/recording of before and after.

These are the 2.x docs, where notifications:install is correct


[DCOS-55603] Json format check for TC CI

What changes were proposed in this pull request?
Json formatting check added as part of TC code check , to check json formatting for universe\json files.
Resolves DCOS-55603
How were these changes tested?
Script was run locally against each framework i.e hdfs , cassandra , datastax , elastic and separate PRs were raised and merged post fixing json formatting.

Raised new PR as below , closing this one
https://github.com/mesosphere/dcos-commons/pull/3201