Multiple nodes showing up when adding device

Good morning,
I’m trying to add a Zooz outdoor plug (Zen14) to my HA using Zwave-JS-UI. I scanned the QR code, plugged it in, and turned it on. All of a sudden I keep getting multiple nodes trying to add (up to 6 nodes now), and none of them complete. I’ve let it go for like 20 minutes now, and it’s just spinning at me being dumb. I’ve had this happen a few times, but just 1 or 2 extra inclusions, and they usually end up adding a final secure node.
I tried soft resetting Z-Wave-JS-UI, and I’ve tried restarting Home Assistant, but it just keeps spinning.
What is going on here?
I’m running HA 2022.10.5 (not upgrading to 11.1 until the bugs are worked out)
OS 9.3
RaspPi 4.

When I've seen this before, it was the device crashing and seemingly factory resetting in the middle of the interview, but only when included via SmartStart. That then triggers another inclusion and so on...
As a workaround just do a normal manual inclusion. I guess also report this to Zooz but I'm not sure is this is something they can fix themselves. since the same thing seems to happen across manufacturers, it might also be an SDK bug.

Also make sure your dongle is on an USB cord, away from an USB input
Where is this documented? I have mine connected directly to the box and am having this same issue, however mine appears to be paired successfully but then it keeps adding the same one ever 20s.

There: https://zwave-js.github.io/node-zwave-js/#/troubleshooting/connectivity-issues?id=general-troubleshooting

The original issue was fixed in v11.0.0: https://github.com/zwave-js/node-zwave-js/blob/master/CHANGELOG.md#1100-2023-06-19--im-on-the-highway-to-hell-certification
This happens when including a device via SmartStart fails (e.g. due to communication issues or timeouts in the key exchange). The device then resets and tries again.
We now remove the remains of the failed inclusion automatically.


Build Docker with arm64

Tried to use your docker image in arm CPU however, it does not work. So I cloned the repo and modified Dockerfile with the following:

FROM ... changed to alpine:latest
Replace all add-pkg to apk add
Replace all del-pkg to apk del

Run docker build . and it built successfully.
Use your docker-compose example to deploy without any issue
However the docker log shows: No log line matching the '' filter and nothing happened.
Did I do anything wrong? Is it possible to create a arm image from your side (or maintains a base-image:alpine with arm)?
I used your docker image for years and love it.
Thanks for maintaining this great docker image

The latest image is now multi-arch.


handle manifests with replaces field

This does not (yet???) write manifests in the new format

Area of interest:
https://github.com/sifive/wit/blob/f2d3d23b3a7fbc7cfb6b5d3eb067554d58da9701/lib/wit/workspace.py#L177-L180


add blockchain

add blockchain
i did not check if this works

unfortunately I have learned that you do not own any Fencoin, so I must retract this PR

oh


Java indexer: add subkinds to 'function' and 'variable' nodes [phab:D90]

Created by schroederc at 2015-02-24 17:51:10:

zarko commented inline (context lost during migration) at 2015-02-24 18:24:05:
What's the semantic difference between a resource variable and a local variable? How about 'local/resource'?

zarko commented inline (context lost during migration) at 2015-02-24 18:24:05:
What's the semantic difference between an exception variable and a local variable? How about 'local/exception'?

zarko wrote at 2015-02-24 18:24:05:
LGTM, only some non-blocking suggestions

zarko accepted this revision at 2015-02-24 18:24:05

schroederc wrote at 2015-02-24 19:24:06:
Nest 'exception', 'parameter', and 'resource' subkinds as locals.

schroederc commented inline (context lost during migration) at 2015-02-24 19:24:14:
I don't believe there are any different semantics at play.  I'll change the subkinds as suggested, including the 'parameter' subkind.

schroederc commented inline (context lost during migration) at 2015-02-24 19:24:14:
Done.

schroederc closed via commit 66580fbbbfed8517c209908400456169c677b4a3 at 2015-02-24 19:56:20

schroederc closed via commit 7898a9b4b8cf35de0b7a7cc04487e76bc5474b31 at 2015-02-24 19:56:21


Fixed README.md Code of Conduct Link

Previous Code of Conduct Link brought me to 404 not found I changed it to the Code of Conduct found under the contributing section.
Describe the change
What does this Pull Request do?
Why are we doing this?
Any related context as to why is this is a desirable change.
Benefits
How will the library improve?
Drawbacks
Possible drawbacks applying this change.
Requirements
Put an X between brackets on each line if you have done the item:
[] Tests written & passing locally?
[] Code style checked?
[] Rebased with master branch?
[] Documentaion updated?

Coverage decreased (-1.04%) to 90.796% when pulling 27c79352b5713403806c3fdb719bf5f155ae2746 on Taljjaa:patch-1 into 1b0073ea25faed507007d1bb889844ca3da26ceb on piotrmurach:master.

Thanks ❤


feat: private liquidity mining experiment

...
Checklist:
Remove the checklist to signal you've completed it. Enable auto-merge if the PR is ready to merge.

[ ] If the pull request requires a cryptography review (e.g. cryptographic algorithm implementations) I have added the 'crypto' tag.
[ ] I have reviewed my diff in github, line by line and removed unexpected formatting changes, testing logs, or commented-out code.
[ ] Every change is related to the PR description.
[ ] I have linked this pull request to relevant issues (if any exist).

Benchmark results
Metrics with a significant change:

note_trial_decrypting_time_in_ms (8): 99.9 (+1523%)

Detailed results
All benchmarks are run on txs on the Benchmarking contract on the repository. Each tx consists of a batch call  to create_note and increment_balance, which guarantees that each tx has a private call, a nested private call, a public call, and a nested public call, as well as an emitted private note, an unencrypted log, and public storage read and write.
This benchmark source data is available in JSON format on S3 here.
Values are compared against data from master at commit d94d88bf and shown if the difference exceeds 1%.
L2 block published to L1
Each column represents the number of txs on an L2 block published to L1.

Metric
8 txs
32 txs
128 txs

l1_rollup_calldata_size_in_bytes
45,444
179,588
716,132

l1_rollup_calldata_gas
222,984
867,788
3,449,468

l1_rollup_execution_gas
842,071
3,594,896
22,204,837

l2_block_processing_time_in_ms
2,017 (-1%)
7,590 (-2%)
30,003 (-1%)

note_successful_decrypting_time_in_ms
296 (-2%)
881 (-2%)
3,189 (-4%)

note_trial_decrypting_time_in_ms
:warning: 99.9 (+1523%)
93.5 (-13%)
140 (-3%)

l2_block_building_time_in_ms
20,764
82,217
327,512

l2_block_rollup_simulation_time_in_ms
11,911 (-2%)
47,137 (-1%)
187,818 (-1%)

l2_block_public_tx_process_time_in_ms
8,812 (+2%)
34,944 (+2%)
139,177 (+1%)

L2 chain processing
Each column represents the number of blocks on the L2 chain where each block has 16 txs.

Metric
5 blocks
10 blocks

node_history_sync_time_in_ms
21,699 (-1%)
42,682 (-1%)

note_history_successful_decrypting_time_in_ms
2,039
3,992

note_history_trial_decrypting_time_in_ms
125 (-1%)
157 (-22%)

node_database_size_in_bytes
1,628,303
1,097,591

pxe_database_size_in_bytes
29,748
59,307

Circuits stats
Stats on running time and I/O sizes collected for every circuit run across all benchmarks.

Circuit
circuit_simulation_time_in_ms
circuit_input_size_in_bytes
circuit_output_size_in_bytes

private-kernel-init
778 (+1%)
61,697
18,905

private-kernel-ordering
129 (+2%)
24,297
8,153

base-rollup
1,756
656,428
873

root-rollup
175 (+4%)
4,072
1,097

private-kernel-inner
804 (+2%)
81,568
18,905

public-kernel-private-input
578 (+1%)
41,519
18,905

public-kernel-non-first-iteration
414 (+1%)
41,561
18,905

merge-rollup
15.7 (+1%)
2,592
873

Miscellaneous
Transaction sizes based on how many contracts are deployed in the tx.

Metric
0 deployed contracts
1 deployed contracts

tx_size_in_bytes
8,787
27,547


Document Databricks Delta features not supported in OSS Delta

Explicitly describe those Databricks features that are not supported in OSS Delta. There repeated slack questions about this especially regarding Delta-specific SQL commands.
For example:

DESCRIBE HISTORY my_table
DESCRIBE DETAIL my_table
SELECT * FROM my_table VERSION AS OF 5
Merge syntax

Looks like VACUUM and HISTORY have been added to the programmatic API in v0.3.0 https://docs.delta.io/0.3.0/delta-utility.html
MERGE is also in the programmatic API https://docs.delta.io/0.3.0/delta-update.html#upsert-into-a-table-using-merge
What are current features that individuals are looking for that are not yet implemented? I know Z-ORDER is one and is not on the roadmap.

After some minor comparison, the difference in features between delta on databricks and oss are

manifest files
data skipping
compaction
auto optimize
native parquet reader
Z-ordering

Thanks for sharing this information. Is there plan to bring these features
to OSS version?
On Wed, 7 Aug, 2019, 4:17 AM Wesley Hoffman<EMAIL_ADDRESS>wrote:

After some minor comparison, the difference in features between delta on
databricks and oss are

manifest files
data skipping
compaction
auto optimize
native parquet reader
Z-ordering

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/delta-io/delta/issues/77?email_source=notifications&email_token=ALJQ5KEJ77UFBV4PI56HLD3QDH5QTA5CNFSM4H3WEYT2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD3WVVII#issuecomment-518871713,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ALJQ5KBN53KIY57GQHTNOETQDH5QTANCNFSM4H3WEYTQ
.

We are discussing this over on #129 and will add some language to clarify the roadmap the readme.
In general though it is our goal to open source all APIs that are required to correctly run a program against a Delta Lake table. This will take some time, as some (SQL time travel) require first adding new APIs to Spark for us to leverage. In some cases we might end up working with other engines to add the same support, rather than waste time open sourcing a workaround (manifests).
Many of the performance features listed, however, are deeply tied to the specifics of Databricks runtime and platform, so there are no plans to open source them at this time.

I think this is the most interesting one:

compaction
(not necessarily automatic):

Will the compaction be supported in the oss, as for example the vacuum ?

@btbbass, vacuum is already supported as of 0.3.0.  For instruction of how to implement compaction, see the answer here: https://github.com/delta-io/delta/issues/49#issuecomment-526343434


Problem when creating a gist

Following the documentation, when I try to create a gist in the browser using the following code:
       var gh = new GitHub();
        var gist = gh.getGist(); // not a gist yet
        gist.create({
            public: true,
            description: 'TEST',
            files: {
                "file1.txt": {
                    contents: "Aren't gists great!"
                }
            }
        }).then(function (httpResponse) {
            // Promises!
            var gist = httpResponse.data;
            gist.read(function (err, gist, xhr) {
                // if no error occurred then err == null

                // gist == httpResponse.data

                // xhr == httpResponse
            });
        });

This returns an error  POST https://api.github.com/gists 422 (Unprocessable Entity)
Can you reproduce? Any idea why?

I can see two issues with the snippet you posted:

Unautenticated users cannot create gists
You redefine gist in your promise handler so gist.read won't work

Other than that you appear to be doing the same thing we do in the tests so it should work.

@RaedsLab Any more thoughts here?

I'm also getting an error, but it seems a 404 error:
Here the code:
var gh = new GitHub({ token: MY_TOKEN });

var gist = gh.getGist();

gist.create({
   public: true,
   description: 'My first gist',
   files: {
      "file1.txt": {
         contents: "Aren't gists great!"
      }
   }
})

The lib  is posting this:
  method: 'POST',
  url: 'https://api.github.com/gists',

  headers:
     authorization: 'token e77..........VALID_TOKEN......0c',
     'content-type': 'application/json'

  body:
     description: 'the description for this gist',
     public: true,
     files: { 'file1.txt': { content: 'String file contents' } } },

  json: true

And the response is:

{
  "message": "Not Found",
  "documentation_url": "https://developer.github.com/v3/gists/#create-a-gist"
}

@guumaster Are you sure your token has the gist permission? Our tests indicate that we can successfully create gists using code almost identical to yours.

sure, I'm using it with raw ajax calls and it works.

@guumaster @RaedsLab This is probably due to a mistake in the example from the readme reported in #374. Can you try with
{
   public: true,
   description: 'My first gist',
   files: {
      "file1.txt": {
         content: "Aren't gists great!"
      }
   }
}

This issue has been fixed, so I'm closing it.


[Help] Constraint at vehicle route end

Based on the Routing.End(int vehicle) method and a distance dimension (so called distance_dimension) , can I set a constraint such as :
Routing.End(int vehicle) < 10 || distance_dimension.CumVar(Routing.End(int vehicle)) < 100
Routing.End(int vehicle) < 8 || distance_dimension.CumVar(Routing.End(int vehicle)) < 80

The idea is I want to set condition based on the total visited node count and the total travelled distance, but I don't want to use DependentDimension... method because it is not ready on Python yet.
For example, I want the max_distance of a trip of 10 nodes should be under 100 kms, trip of 9 nodes should be under 90 kms, etc... So, in this case, if ortools get the distance of 9 nodes at 91kms, it should back to 8 nodes state instead of going further to 10 nodes.
Please advise. Thanks

Maybe I misunderstood but, what is the point of 10 node 100km constraint then, if 9 node 91 km is the limit?

@abduakhatov I charge my customer per stop, say 10$/stop, and I pay our driver per distance, say 5$/km, so my profit is (node_count*10 - distance*5). So I define a required earning per distance (epd) and need to find trips satisfying the epd as many as possible, others will be ignored.
That's is my idea. :D

For example, I want the max_distance of a trip of 10 nodes should be under 100 kms, trip of 9 nodes should be under 90 kms, etc

First you can create distance_dimension and counter of nodes per vehicle
plus_one_callback_index = routing.RegisterUnaryTransitCallback(lambda index : 1)
dimension_name = 'Counter'
routing.AddDimension(
  plus_one_callback_index,
  0,  # null capacity slack
  N,  # vehicle maximum capacities
  True,  # start cumul to zero
  'Counter')
counter_dimension = routing.GetDimensionOrDie(dimension_name)
for vehicle_id in range(num_vehicle):
  index = routing.End(vehicle_id)
  solver = routing.solver();
  num_stops = counter_dimension.CumulVar(index)
  total_distance_per_vehicle = distance_dimension.CumulVar(index)
  solver.Add(num_stops*10 >= total_distance_per_vehicle) # 5stops*10 >= 50km

P.S. did not tested hope it works

@thucnc #1121 you already asked this kinda question.

Hi @abduakhatov , thanks for your solution, let me try on this.
For another similar question, actually the suggested solution doesn't work on python with DependentDimension as I already mentioned at beginning of this issue. Hence I ask for another approach.

On the other hand, is there any way to check and reject a solution at the time it is found ?

You mean post solution or inter-solution? I don't know regarding routing, but pywrapsat contains solution callback. Found something or #651

@abduakhatov I can't find sample code for the solution callback so quite confused how to implement it. On the other hand, the code solver.Add(num_stops*10 >= total_distance_per_vehicle) # 5stops*10 >= 50km does not work, the reason is I can not compare CumulVar with a constant (int) value. I think the current approach for this problem does not work. So, I will check other aspects.


Redesign presets extension API [BREAKING CHANGE]

When I have designed the basic presets extension API back in 2022, there was not a lot of design consideration. It was as simple as "presets are states in a read-only collection", "we can get state binary content by index", and "we offer a setter for the current preset index".
Thus it has a preset getter that it can retrieve the state binary, and a preset index setter that would let the plugin load the binary state. Now, reviewing the actual presets usage, we do not need a binary retriever. We could simply set the preset index, and use the State extension to retrieve the binary.
(The getter was there because it was kind of following LV2 presets design - it is loadable just like a state, and the presets binaries would be useful by hosts. For example, what if multiple plugins can share the same binary resources? Load from disk once and use it many times.)
Actually, get_preset() for the binary blob part and get_preset_data_size() are not in use anywhere in the existing apps - we could simply show the list of preset names, and let app set_preset() by index.
On the other hand, existence of those extension functions means, the plugin needs to know the data size of every preset. Depending on the actual plugin code, it means it will have to load every preset binary just to retrieve the data size, without actually using it. This is actually what aap-juce plugins are kind of forced to do. Especially, aap-juce-byod shows bad performance regarding presets due to this design (https://github.com/atsushieno/aap-juce-byod/issues/1).
Therefore, at this state, I think it's time to make changes to simplify the Presets extension:

we remove get_preset() and get_preset_data_size() : we will not have to retrieve binary blob anymore (we needed data size because we then allocate shared memory to transfer the preset binary blob not on Binder but the AAPXS' own space)
we would need aap_preset_t as a completely different structure. What I think we need now is like this:

typedef struct aap_preset_t {
    // a persistent ID.
    // It should be usable forever across instancing if it is not a user preset.
    // It does not have to match the preset "index"; the index is just an index within the collection.
    // Unlike index, there can be skipped numbers.
    int32_t id{0};

    // preset name, might not be unique even within a plugin
    char name[AAP_PRESETS_EXTENSION_MAX_NAME_LENGTH];
} aap_preset_t;

This affects (improves) how we deal with RT safety:

get_preset_count() could be realistically changed to RT_SAFE as it would at worst only load the number of presets. It could be done just once.

For aap-juce plugins, it can be done by AudioProcessor::getNumPrograms() (best done at prepare() time, as the actual plugin implementation is not guaranteed to be RT safe - it might iterate file systems).
aap-lv2 plugins could do that in lilv API (same approach as ^ applies).

get_preset_index() - I'm sure it's fairly returning in-memory number.
set_preset_index() is RT_UNSAFE regardless. Any notifications required would be sent by notify_preset_loaded() in Presets host extension (to be added).

Dynamic updates of presets could be detected by each backend and then dispatched to host via notify_presets_update() host extension. For aap-juce plugins, AudioProcessorListener::ChangeDetails::withProgramChanged().  For aap-lv2 plugins...dunno, dynamic manifest? Needs investigation.

The relevant API changes have landed in main branch.


Wrong Color for Enum Value - AL Language Syntax Highlights for Microsoft Dynamics 365 Business Central

Please include the following with each issue:
1. Describe the bug
The enum value isn't highlighted correctly.
2. To Reproduce
Steps to reproduce the behavior:

create an enum with with the values in a one line syntax.

Note: Because the developers need to copy and paste the code snippet, including a code snippet as a media file (i.e. .gif) is not sufficient.
3. Expected behavior
Everything that compiles should be highlighted correctly.
4. Actual behavior
No Highliting.
5. Versions:

AL Language Syntax Highlights for Microsoft Dynamics 365 Business Central: 12.7.944946 (Latest)

@thpeder This is about the extension for DevOps, not for/in VS Code.
Locked is supported, but you need to replace the preceding semicolon with a comma - compare with pri-kise's code ;-)

Thanks for the help!
We will have a closer look at it.

Interestingly, this does work when your curly braces are not on the same line as the value(x; someName) declaration:

While we work on a fix to the issue, if this is bothering you, you could switch the enum value declaraton to one of the formats above which are working - dark mode aside, the highlighter works the same.


fix: esbuild 패키지 추가

:tada: This PR is included in version 1.0.0-next.15 :tada:
The release is available on:

npm package (@next dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.0.2 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


[ISSUE] Not playing nice with Sonos

Issue Description
Not sure if this is a bug that can be fixed, but when connected on a local Spotify client that is playing on another device such as a Sonos speaker, the plug-in does not seem to work. For example, a sp next or sp pause  does not result in any action.
Functionality Affected

[x] Controlling the local Spotify client (changing track, pausing, skipping, muting)
[ ] Searching Spotify for albums, artists or songs

Software Versions

Spotify client version  Spotify for Windows (64 bit) <IP_ADDRESS>4.gc16ec9f6
Flow Launcher version 1.19.0

Please also make sure you're running the latest version of Flow.Launcher.Plugin.SpotifyPremium

To add to this - the sonos device does not show up as an option for  sp device


Signing image fails: "valid signatures did not meet threshold for snapshot"

I've been following these simple steps here https://docs.docker.com/engine/security/trust/content_trust/
However, I can't manage to proceed forward as I get this error message "valid signatures did not meet threshold for snapshot"
Docker Version on Mac OS
Client: Docker Engine - Community
 Version:           18.09.2
 API version:       1.39
 Go version:        go1.10.8
 Git commit:        6247962
 Built:             Sun Feb 10 04:12:39 2019
 OS/Arch:           darwin/amd64
 Experimental:      false

Server: Docker Engine - Community
 Engine:
  Version:          18.09.2
  API version:      1.39 (minimum version 1.12)
  Go version:       go1.10.6
  Git commit:       6247962
  Built:            Sun Feb 10 04:13:06 2019
  OS/Arch:          linux/amd64
  Experimental:     true

How to reproduce it
$ docker trust key generate diego
Generating key for diego...
Enter passphrase for new diego key with ID 39cd6f9:
Repeat passphrase for new diego key with ID 39cd6f9:
Successfully generated and loaded private key. Corresponding public key available: /Users/diegomariani/workspace/test-repo/diego.pub

$ docker trust signer add --key diego.pub diego docker.io/diegomariani/test-repo
Adding signer "diego" to docker.io/diegomariani/test-repo...
DEBU[0000] reading certificate directory: /Users/diegomariani/.docker/tls/notary.docker.io
DEBU[0001] No yubikey found, using alternative key storage: no library found
DEBU[0001] Making dir path: /Users/diegomariani/.docker/trust/tuf/docker.io/diegomariani/test-repo/changelist
DEBU[0001] entered ValidateRoot with dns: docker.io/diegomariani/test-repo
DEBU[0001] found the following root keys: [b2550f802363c4a759c3b6802a64261f12a3e63fd5eebbe7548ae8d6d7ace504]
DEBU[0001] found 1 valid leaf certificates for docker.io/diegomariani/test-repo: b2550f802363c4a759c3b6802a64261f12a3e63fd5eebbe7548ae8d6d7ace504
DEBU[0001] found 1 leaf certs, of which 1 are valid leaf certs for docker.io/diegomariani/test-repo
DEBU[0001] checking root against trust_pinning config for docker.io/diegomariani/test-repo
DEBU[0001] checking trust-pinning for cert: b2550f802363c4a759c3b6802a64261f12a3e63fd5eebbe7548ae8d6d7ace504
DEBU[0001]  role has key IDs: b2550f802363c4a759c3b6802a64261f12a3e63fd5eebbe7548ae8d6d7ace504
DEBU[0001] verifying signature for key ID: b2550f802363c4a759c3b6802a64261f12a3e63fd5eebbe7548ae8d6d7ace504
DEBU[0001] root validation succeeded for docker.io/diegomariani/test-repo
DEBU[0001] entered ValidateRoot with dns: docker.io/diegomariani/test-repo
DEBU[0001] found the following root keys: [b2550f802363c4a759c3b6802a64261f12a3e63fd5eebbe7548ae8d6d7ace504]
DEBU[0001] found 1 valid leaf certificates for docker.io/diegomariani/test-repo: b2550f802363c4a759c3b6802a64261f12a3e63fd5eebbe7548ae8d6d7ace504
DEBU[0001] found 1 leaf certs, of which 1 are valid leaf certs for docker.io/diegomariani/test-repo
DEBU[0001] checking root against trust_pinning config for docker.io/diegomariani/test-repo
DEBU[0001] checking trust-pinning for cert: b2550f802363c4a759c3b6802a64261f12a3e63fd5eebbe7548ae8d6d7ace504
DEBU[0001]  role has key IDs: b2550f802363c4a759c3b6802a64261f12a3e63fd5eebbe7548ae8d6d7ace504
DEBU[0001] verifying signature for key ID: b2550f802363c4a759c3b6802a64261f12a3e63fd5eebbe7548ae8d6d7ace504
DEBU[0001] root validation succeeded for docker.io/diegomariani/test-repo
DEBU[0001] updating TUF client
DEBU[0001] Loading timestamp...
DEBU[0001] received HTTP status 404 when requesting timestamp.
DEBU[0001] error downloading timestamp: timestamp trust data unavailable.  Has a notary repository been initialized?
DEBU[0001] no cached or remote timestamp available
DEBU[0001] Client Update (Timestamp): timestamp trust data unavailable.  Has a notary repository been initialized?
DEBU[0001] Error occurred. Root will be downloaded and another update attempted
DEBU[0001] Resetting the TUF builder...
DEBU[0001] Loading root with no expected checksum
DEBU[0002] received HTTP status 404 when requesting root.
DEBU[0002] error downloading root: root trust data unavailable.  Has a notary repository been initialized?
DEBU[0002] Client Update (Root): root trust data unavailable.  Has a notary repository been initialized?
Initializing signed repository for docker.io/diegomariani/test-repo...
DEBU[0002] No yubikey found, using alternative key storage: no library found
DEBU[0002] No yubikey found, using alternative key storage: no library found
Enter passphrase for root key with ID 0e38504:
DEBU[0005] No yubikey found, using alternative key storage: no library found
DEBU[0005] generated ECDSA key with keyID: 79bb712b23942c19889f72ed01f22acfe26c774ced2ba5e7374523e2e9f8dc43
DEBU[0005] generated new ecdsa key for role: targets and keyID: 79bb712b23942c19889f72ed01f22acfe26c774ced2ba5e7374523e2e9f8dc43
Enter passphrase for new repository key with ID 79bb712:
Repeat passphrase for new repository key with ID 79bb712:
DEBU[0010] got remote timestamp ecdsa key with keyID: a1b7cfbbd6a6b0b1b893819f90bcfee74a1368e873d01ad3cdb7f45dc00b04b4
DEBU[0010] got remote snapshot ecdsa key with keyID: 60450a198a0b2d2ac6e781f43ab80ff4b950838e93a868220485331ae9822868
DEBU[0010] generating new snapshot...
DEBU[0010] Saving changes to Trusted Collection.
DEBU[0010] signing root...
DEBU[0010] sign called with 1/1 required keys
DEBU[0010] No yubikey found, using alternative key storage: no library found
DEBU[0010] sign called with 0/0 required keys
DEBU[0010] sign targets called for role targets
DEBU[0010] sign called with 1/1 required keys
DEBU[0010] No yubikey found, using alternative key storage: no library found
DEBU[0010] sign called with 0/0 required keys
Successfully initialized "docker.io/diegomariani/test-repo"
DEBU[0010] Adding delegation "targets/diego" with threshold 1, and 1 keys\n
DEBU[0010] Adding [] paths to delegation targets/diego\n
DEBU[0010] Adding delegation "targets/releases" with threshold 1, and 1 keys\n
DEBU[0010] Adding [] paths to delegation targets/releases\n
DEBU[0010] entered ValidateRoot with dns: docker.io/diegomariani/test-repo
DEBU[0010] found the following root keys: [9c2f987f60f7d1328218b47a080efe56581af674f713b992efcd348a21673cee]
DEBU[0010] found 1 valid leaf certificates for docker.io/diegomariani/test-repo: 9c2f987f60f7d1328218b47a080efe56581af674f713b992efcd348a21673cee
DEBU[0010] found 1 leaf certs, of which 1 are valid leaf certs for docker.io/diegomariani/test-repo
DEBU[0010] checking root against trust_pinning config for docker.io/diegomariani/test-repo
DEBU[0010] checking trust-pinning for cert: 9c2f987f60f7d1328218b47a080efe56581af674f713b992efcd348a21673cee
DEBU[0010]  role has key IDs: 9c2f987f60f7d1328218b47a080efe56581af674f713b992efcd348a21673cee
DEBU[0010] verifying signature for key ID: 9c2f987f60f7d1328218b47a080efe56581af674f713b992efcd348a21673cee
DEBU[0010] root validation succeeded for docker.io/diegomariani/test-repo
DEBU[0010] entered ValidateRoot with dns: docker.io/diegomariani/test-repo
DEBU[0010] found the following root keys: [9c2f987f60f7d1328218b47a080efe56581af674f713b992efcd348a21673cee]
DEBU[0010] found 1 valid leaf certificates for docker.io/diegomariani/test-repo: 9c2f987f60f7d1328218b47a080efe56581af674f713b992efcd348a21673cee
DEBU[0010] found 1 leaf certs, of which 1 are valid leaf certs for docker.io/diegomariani/test-repo
DEBU[0010] checking root against trust_pinning config for docker.io/diegomariani/test-repo
DEBU[0010] checking trust-pinning for cert: 9c2f987f60f7d1328218b47a080efe56581af674f713b992efcd348a21673cee
DEBU[0010]  role has key IDs: 9c2f987f60f7d1328218b47a080efe56581af674f713b992efcd348a21673cee
DEBU[0010] verifying signature for key ID: 9c2f987f60f7d1328218b47a080efe56581af674f713b992efcd348a21673cee
DEBU[0010] root validation succeeded for docker.io/diegomariani/test-repo
DEBU[0010] received HTTP status 404 when requesting root.
DEBU[0010] Loading trusted collection.
DEBU[0010] entered ValidateRoot with dns: docker.io/diegomariani/test-repo
DEBU[0010] found the following root keys: [9c2f987f60f7d1328218b47a080efe56581af674f713b992efcd348a21673cee]
DEBU[0010] found 1 valid leaf certificates for docker.io/diegomariani/test-repo: 9c2f987f60f7d1328218b47a080efe56581af674f713b992efcd348a21673cee
DEBU[0010] found 1 leaf certs, of which 1 are valid leaf certs for docker.io/diegomariani/test-repo
DEBU[0010] checking root against trust_pinning config for docker.io/diegomariani/test-repo
DEBU[0010] checking trust-pinning for cert: 9c2f987f60f7d1328218b47a080efe56581af674f713b992efcd348a21673cee
DEBU[0010]  role has key IDs: 9c2f987f60f7d1328218b47a080efe56581af674f713b992efcd348a21673cee
DEBU[0010] verifying signature for key ID: 9c2f987f60f7d1328218b47a080efe56581af674f713b992efcd348a21673cee
DEBU[0010] root validation succeeded for docker.io/diegomariani/test-repo
DEBU[0010] targets role has key IDs: 79bb712b23942c19889f72ed01f22acfe26c774ced2ba5e7374523e2e9f8dc43
DEBU[0010] verifying signature for key ID: 79bb712b23942c19889f72ed01f22acfe26c774ced2ba5e7374523e2e9f8dc43
DEBU[0010] snapshot role has key IDs: 60450a198a0b2d2ac6e781f43ab80ff4b950838e93a868220485331ae9822868
DEBU[0010] verifying signature for key ID: bcb08ef0d2cff694af6c6203c909148f1b9eff1e7163985149f69715c48a6732
DEBU[0010] continuing b/c keyid lookup was nil: bcb08ef0d2cff694af6c6203c909148f1b9eff1e7163985149f69715c48a6732

DEBU[0010] Unable to load or initialize repository during first publish: valid signatures did not meet threshold for snapshot  error="valid signatures did not meet threshold for snapshot"
valid signatures did not meet threshold for snapshot

Failed to add signer to: docker.io/diegomariani/test-repo

deleting the trust store and generating keys from scratch worked. I'll have a further read on the key generation and signing mechanism. Thanks

@0x13a hi, can you please be more specific about the solved issue?


kismatic Timed out waiting for at least one DNS pod to be in the ready state

I tried to deploy a kubernetes cluster on a Virtualbox node for testing but got the error kismatic Timed out waiting for at least one DNS pod to be in the ready state.
Then I tried to deploy a two-node cluster but got the same problem.
The following is basic info:

OS: MacOS 10.12.4
VM OS: ubuntu-16.04
kismatic version: v1.2.2

The plan file:
cluster:
  name: kubernetes
  admin_password: Selnemakyidi36416
  allow_package_installation: true
  disconnected_installation: false
  networking:
    type: overlay
    pod_cidr_block: <IP_ADDRESS>/16
    service_cidr_block: <IP_ADDRESS>/16
    policy_enabled: false
    update_hosts_files: false
  certificates:
    expiry: 17520h
  ssh:
    user: vagrant
    ssh_key: /Users/flyer/.ssh/id_rsa
    ssh_port: 22
docker_registry:
  setup_internal: false
  address: ""
  port: 8443
  CA: ""
etcd:
  expected_count: 1
  nodes:
  - host: "kismatic"
    ip: "<IP_ADDRESS>"
    internalip: ""
master:
  expected_count: 1
  load_balanced_fqdn: "kismatic"
  load_balanced_short_name: "kismatic"
  nodes:
  - host: "kismatic"
    ip: "<IP_ADDRESS>"
    internalip: ""
worker:
  expected_count: 1
  nodes:
  - host: "kismatic"
    ip: "<IP_ADDRESS>"
    internalip: ""
ingress:
  expected_count: 0
  nodes: []
storage:
  expected_count: 0
  nodes: []
nfs:
  nfs_volume: []

The screeshot:

@flyer103 in the plan file for master.load_balanced_fqdn and master. load_balanced_short_name you have it set to kismatic. This address is used for internal services, including DNS and will not be resolvable from the pods.
Change both of those fields to <IP_ADDRESS> and it should work.

Sorry for replying too late...
I tried what you indicated and it worked. Thank you very much.


Collect data from Gradle on import and add it to the module

this is the first step towards #2105. Also addresses #2106.
Background:
The goal is to enable deployment from Gradle sources with Community Edition (so that Android Studio can use this plugin). In order to accomplish this, we will use the app-gradle-plugin to build the project and create the exploded war directory (the plugin adds an exlodeWar task which gets called on assemble). Then, the existing App Engine standard gcloud based deployment path will be invoked on the built module.
What this PR does:

Creates a new app-engine-gradle-java Gradle module. This is to get around the limitation explained in #2106.
Sets up all the plumbing needed to collect data from Gradle on Gradle sync. Populates the AppEngineGradleModel with the needed information:

does the module have the Gradle plugin configured
path to the gradle build directory

On module import, this sets up the code to add the collected information to a new App Engine Gradle facet

The next PRs will fill in the remaining gaps of:

adding the App Engine Gradle facet
creating the new Gradle based deployment source

@ivanporty should be ready for review now


Launching the testsuite generation produces no test

Launching the testsuite using the readme instructions produces no test, the resulting testsuite.yml has the following content:
tests:

I encountered the same issue
tamaron@PC:~/work/testing$ cargo run -- --gccrs '../gccrs-build/gcc
/crab1' --rustc rustc --gccrs-path ../gccrs/ --rust-path ../rust/ -
-output-dir sources/ --yaml testsuite.yml --pass gccrs-parsing
    Finished dev [unoptimized + debuginfo] target(s) in 0.02s
     Running `target/debug/testsuite-adaptor --gccrs ../gccrs-build/gcc/crab1 --rustc rustc --gccrs-path ../gccrs/ --rust-path ../rust/ --output-dir sources/ --yaml testsuite.yml --pass gccrs-parsing`
[info] running pass `gccrs-parsing`...
[info] fetching test files for `gccrs-parsing`...
[info] generating test cases for `gccrs-parsing`... this might take a while
[info] `gccrs-parsing` pass complete!
tamaron@PC:~/work/testing$ cat testsuite.yml
tests:
tamaron@PC:~/work/testing$

rust/src/test has been moved to rust/tests
https://github.com/rust-lang/rust/commit/cf2dff2b1e3fa55fa5415d524200070d0d7aacfe


Container service and XNAT compatible with Docker > 24

Short Description
When trying to run a container using the current deployment setup, it fails
Evidence/Steps to Reproduce
Follow the README.md document, including:

terraform apply
In ./configure, run ./install_xnat.sh
Then run ./setup_xnat.sh
Run the dmc2niix container as part of the instructions in the MEDICSS tutorial

Acceptance Criteria/Expected Behaviour
The system should be able to run the containers automatically without the user having to go in and manually downgrade the DOcker.
Details
This thread and this one seems to suggest it is a problem with DOcker above version 24. I confirmed this by running sudo yum downgrade docker-ce-3:24.0.9-1.el9.x86_64 on the container server and the containers run fine after the downgrade.
Resolution
No response

This is fixed in the latest version of our Ansible setup, and I'm planning to open a PR soon to switch to that (sorry if it wasted your time troubleshooting this!)


Operation Not Permitted on Multi Node OSD

I am trying to get this working in a multi-node environment and I keep getting operation not permitted errors
I currently have one master node that runs a monitor. When I start an OSD on that node, it comes up fine. I then copied /etc/ceph and /var/lib/ceph to two more machines. When I start the OSD service on those nodes, I get this long output in my logs that seems to be triggered from an Operation not permitted error.
I am really new to ceph so I'm not really sure how to debug this though I did try fiddling with a few files and a lot of googling. Any idea where I'm getting it wrong?
--container="mesos-8aa60360-3d0a-4713-8fe2-60046f2af3c7-S0.aaf45dfd-a687-4d86-8e6c-0e3407979847" --docker="docker" --docker_socket="/var/run/docker.sock" --help="false" --initialize_driver_logging="true" --launcher_dir="/usr/libexec/mesos" --logbufsecs="0" --logging_level="INFO" --mapped_directory="/mnt/mesos/sandbox" --quiet="false" --sandbox_directory="/var/lib/mesos/slaves/8aa60360-3d0a-4713-8fe2-60046f2af3c7-S0/frameworks/8d0d7003-3072-4176-bf49-3d1551cfefb8-0000/executors/ceph_osd.3571d6e3-f933-11e6-a02d-024287699a2c/runs/aaf45dfd-a687-4d86-8e6c-0e3407979847" --stop_timeout="0ns"
--container="mesos-8aa60360-3d0a-4713-8fe2-60046f2af3c7-S0.aaf45dfd-a687-4d86-8e6c-0e3407979847" --docker="docker" --docker_socket="/var/run/docker.sock" --help="false" --initialize_driver_logging="true" --launcher_dir="/usr/libexec/mesos" --logbufsecs="0" --logging_level="INFO" --mapped_directory="/mnt/mesos/sandbox" --quiet="false" --sandbox_directory="/var/lib/mesos/slaves/8aa60360-3d0a-4713-8fe2-60046f2af3c7-S0/frameworks/8d0d7003-3072-4176-bf49-3d1551cfefb8-0000/executors/ceph_osd.3571d6e3-f933-11e6-a02d-024287699a2c/runs/aaf45dfd-a687-4d86-8e6c-0e3407979847" --stop_timeout="0ns"
Registered docker executor on medifor-tower0.sarnoff.internal
Starting task ceph_osd.3571d6e3-f933-11e6-a02d-024287699a2c
2017-02-22 19:15:27  /entrypoint.sh: static: does not generate config
ceph-1: /usr/bin/ceph-osd --cluster ceph -f -i 1 --osd-journal /var/lib/ceph/osd/ceph-1/journal -k /var/lib/ceph/osd/ceph-1/keyring
2017-02-22 19:15:27  /entrypoint.sh: SUCCESS
forego   | starting ceph-1.1 on port 31854
ceph-1.1 | starting osd.1 at - osd_data /var/lib/ceph/osd/ceph-1 /var/lib/ceph/osd/ceph-1/journal
ceph-1.1 | 2017-02-22 19:15:27.773422 7fde40a38a40 -1 journal FileJournal::_open: disabling aio for non-block journal.  Use journal_force_aio to force use of aio anyway
ceph-1.1 | 2017-02-22 19:15:27.792822 7fde40a38a40 -1 osd.1 0 log_to_monitors {default=true}
ceph-1.1 | 2017-02-22 19:15:27.805961 7fde40a38a40 -1  ** ERROR: osd init failed: (1) Operation not permitted
ceph-1.1 | /tmp/buildd/ceph-11.2.0/src/common/HeartbeatMap.cc: In function 'ceph::HeartbeatMap::~HeartbeatMap()' thread 7fde40a38a40 time 2017-02-22 19:15:27.806847
ceph-1.1 | /tmp/buildd/ceph-11.2.0/src/common/HeartbeatMap.cc: 46: FAILED assert(m_workers.empty())
ceph-1.1 |  ceph version 11.2.0 (f223e27eeb35991352ebc1f67423d4ebc252adb7)
ceph-1.1 |  1: (ceph::__ceph_assert_fail(char const*, char const*, int, char const*)+0x80) [0x55b5d3251380]
ceph-1.1 |  2: (ceph::HeartbeatMap::~HeartbeatMap()+0xd1) [0x55b5d3337a71]
ceph-1.1 |  3: (CephContext::~CephContext()+0x428) [0x55b5d331f498]
ceph-1.1 |  4: (CephContext::put()+0xec) [0x55b5d331f78c]
ceph-1.1 |  5: (main()+0xd97) [0x55b5d2aa4f87]
ceph-1.1 |  6: (__libc_start_main()+0xf0) [0x7fde3e0b1830]
ceph-1.1 |  7: (_start()+0x29) [0x55b5d2b12dc9]
ceph-1.1 |  NOTE: a copy of the executable, or `objdump -rdS <executable>` is needed to interpret this.
ceph-1.1 | 2017-02-22 19:15:27.811335 7fde40a38a40 -1 /tmp/buildd/ceph-11.2.0/src/common/HeartbeatMap.cc: In function 'ceph::HeartbeatMap::~HeartbeatMap()' thread 7fde40a38a40 time 2017-02-22 19:15:27.806847
ceph-1.1 | /tmp/buildd/ceph-11.2.0/src/common/HeartbeatMap.cc: 46: FAILED assert(m_workers.empty())
ceph-1.1 |
ceph-1.1 |  ceph version 11.2.0 (f223e27eeb35991352ebc1f67423d4ebc252adb7)
ceph-1.1 |  1: (ceph::__ceph_assert_fail(char const*, char const*, int, char const*)+0x80) [0x55b5d3251380]
ceph-1.1 |  2: (ceph::HeartbeatMap::~HeartbeatMap()+0xd1) [0x55b5d3337a71]
ceph-1.1 |  3: (CephContext::~CephContext()+0x428) [0x55b5d331f498]
ceph-1.1 |  4: (CephContext::put()+0xec) [0x55b5d331f78c]
ceph-1.1 |  5: (main()+0xd97) [0x55b5d2aa4f87]
ceph-1.1 |  6: (__libc_start_main()+0xf0) [0x7fde3e0b1830]
ceph-1.1 |  7: (_start()+0x29) [0x55b5d2b12dc9]
ceph-1.1 |  NOTE: a copy of the executable, or `objdump -rdS <executable>` is needed to interpret this.
ceph-1.1 |
ceph-1.1 |    -98> 2017-02-22 19:15:27.773422 7fde40a38a40 -1 journal FileJournal::_open: disabling aio for non-block journal.  Use journal_force_aio to force use of aio anyway
ceph-1.1 |    -56> 2017-02-22 19:15:27.792822 7fde40a38a40 -1 osd.1 0 log_to_monitors {default=true}
ceph-1.1 |    -25> 2017-02-22 19:15:27.805961 7fde40a38a40 -1  ** ERROR: osd init failed: (1) Operation not permitted
ceph-1.1 |      0> 2017-02-22 19:15:27.811335 7fde40a38a40 -1 /tmp/buildd/ceph-11.2.0/src/common/HeartbeatMap.cc: In function 'ceph::HeartbeatMap::~HeartbeatMap()' thread 7fde40a38a40 time 2017-02-22 19:15:27.806847
ceph-1.1 | /tmp/buildd/ceph-11.2.0/src/common/HeartbeatMap.cc: 46: FAILED assert(m_workers.empty())
ceph-1.1 |
ceph-1.1 |  ceph version 11.2.0 (f223e27eeb35991352ebc1f67423d4ebc252adb7)
ceph-1.1 |  1: (ceph::__ceph_assert_fail(char const*, char const*, int, char const*)+0x80) [0x55b5d3251380]
ceph-1.1 |  2: (ceph::HeartbeatMap::~HeartbeatMap()+0xd1) [0x55b5d3337a71]
ceph-1.1 |  3: (CephContext::~CephContext()+0x428) [0x55b5d331f498]
ceph-1.1 |  4: (CephContext::put()+0xec) [0x55b5d331f78c]
ceph-1.1 |  5: (main()+0xd97) [0x55b5d2aa4f87]
ceph-1.1 |  6: (__libc_start_main()+0xf0) [0x7fde3e0b1830]
ceph-1.1 |  7: (_start()+0x29) [0x55b5d2b12dc9]
ceph-1.1 |  NOTE: a copy of the executable, or `objdump -rdS <executable>` is needed to interpret this.
ceph-1.1 |
ceph-1.1 | *** Caught signal (Aborted) **
ceph-1.1 |  in thread 7fde40a38a40 thread_name:ceph-osd
ceph-1.1 |  ceph version 11.2.0 (f223e27eeb35991352ebc1f67423d4ebc252adb7)
ceph-1.1 |  1: (()+0x946e4e) [0x55b5d307fe4e]
ceph-1.1 |  2: (()+0x11390) [0x7fde3fad2390]
ceph-1.1 |  3: (gsignal()+0x38) [0x7fde3e0c6428]
ceph-1.1 |  4: (abort()+0x16a) [0x7fde3e0c802a]
ceph-1.1 |  5: (ceph::__ceph_assert_fail(char const*, char const*, int, char const*)+0x26b) [0x55b5d325156b]
ceph-1.1 |  6: (ceph::HeartbeatMap::~HeartbeatMap()+0xd1) [0x55b5d3337a71]
ceph-1.1 |  7: (CephContext::~CephContext()+0x428) [0x55b5d331f498]
ceph-1.1 |  8: (CephContext::put()+0xec) [0x55b5d331f78c]
ceph-1.1 |  9: (main()+0xd97) [0x55b5d2aa4f87]
ceph-1.1 |  10: (__libc_start_main()+0xf0) [0x7fde3e0b1830]
ceph-1.1 |  11: (_start()+0x29) [0x55b5d2b12dc9]
ceph-1.1 | 2017-02-22 19:15:27.817025 7fde40a38a40 -1 *** Caught signal (Aborted) **
ceph-1.1 |  in thread 7fde40a38a40 thread_name:ceph-osd
ceph-1.1 |
ceph-1.1 |  ceph version 11.2.0 (f223e27eeb35991352ebc1f67423d4ebc252adb7)
ceph-1.1 |  1: (()+0x946e4e) [0x55b5d307fe4e]
ceph-1.1 |  2: (()+0x11390) [0x7fde3fad2390]
ceph-1.1 |  3: (gsignal()+0x38) [0x7fde3e0c6428]
ceph-1.1 |  4: (abort()+0x16a) [0x7fde3e0c802a]
ceph-1.1 |  5: (ceph::__ceph_assert_fail(char const*, char const*, int, char const*)+0x26b) [0x55b5d325156b]
ceph-1.1 |  6: (ceph::HeartbeatMap::~HeartbeatMap()+0xd1) [0x55b5d3337a71]
ceph-1.1 |  7: (CephContext::~CephContext()+0x428) [0x55b5d331f498]
ceph-1.1 |  8: (CephContext::put()+0xec) [0x55b5d331f78c]
ceph-1.1 |  9: (main()+0xd97) [0x55b5d2aa4f87]
ceph-1.1 |  10: (__libc_start_main()+0xf0) [0x7fde3e0b1830]
ceph-1.1 |  11: (_start()+0x29) [0x55b5d2b12dc9]
ceph-1.1 |  NOTE: a copy of the executable, or `objdump -rdS <executable>` is needed to interpret this.
ceph-1.1 |
ceph-1.1 |      0> 2017-02-22 19:15:27.817025 7fde40a38a40 -1 *** Caught signal (Aborted) **
ceph-1.1 |  in thread 7fde40a38a40 thread_name:ceph-osd
ceph-1.1 |
ceph-1.1 |  ceph version 11.2.0 (f223e27eeb35991352ebc1f67423d4ebc252adb7)
ceph-1.1 |  1: (()+0x946e4e) [0x55b5d307fe4e]
ceph-1.1 |  2: (()+0x11390) [0x7fde3fad2390]
ceph-1.1 |  3: (gsignal()+0x38) [0x7fde3e0c6428]
ceph-1.1 |  4: (abort()+0x16a) [0x7fde3e0c802a]
ceph-1.1 |  5: (ceph::__ceph_assert_fail(char const*, char const*, int, char const*)+0x26b) [0x55b5d325156b]
ceph-1.1 |  6: (ceph::HeartbeatMap::~HeartbeatMap()+0xd1) [0x55b5d3337a71]
ceph-1.1 |  7: (CephContext::~CephContext()+0x428) [0x55b5d331f498]
ceph-1.1 |  8: (CephContext::put()+0xec) [0x55b5d331f78c]
ceph-1.1 |  9: (main()+0xd97) [0x55b5d2aa4f87]
ceph-1.1 |  10: (__libc_start_main()+0xf0) [0x7fde3e0b1830]
ceph-1.1 |  11: (_start()+0x29) [0x55b5d2b12dc9]
ceph-1.1 |  NOTE: a copy of the executable, or `objdump -rdS <executable>` is needed to interpret this.
ceph-1.1 |

Can you share you command to run that container? Looks like you're using a directory scenario right?

Yes I am using Marathon to manage the deployments, it looks it it runs the following command
docker -H unix:///var/run/docker.sock run --cpu-shares 1024 --memory 134217728 -e MARATHON_APP_VERSION=2017-02-24T14:39:28.961Z -e HOST=medifor-tower0.sarnoff.internal -e MARATHON_APP_RESOURCE_CPUS=1.0 -e CEPH_DAEMON=osd_directory -e MARATHON_APP_RESOURCE_GPUS=0 -e PORT_10006=31110 -e MARATHON_APP_DOCKER_IMAGE=ceph/daemon -e MESOS_TASK_ID=ceph_osd.15082c7d-fa9f-11e6-a02d-024287699a2c -e PORT=31110 -e MARATHON_APP_RESOURCE_MEM=128.0 -e PORTS=31110 -e MARATHON_APP_RESOURCE_DISK=0.0 -e MARATHON_APP_LABELS= -e MARATHON_APP_ID=/ceph/osd -e PORT0=31110 -e MESOS_SANDBOX=/mnt/mesos/sandbox -e MESOS_CONTAINER_NAME=mesos-8aa60360-3d0a-4713-8fe2-60046f2af3c7-S0.4d6175e7-a3c9-4725-ac59-9fd610b4e69d -v /etc/ceph:/etc/ceph:rw -v /data/ceph:/var/lib/ceph:rw -v /data/osd:/var/lib/ceph/osd:rw -v /var/lib/mesos/slaves/8aa60360-3d0a-4713-8fe2-60046f2af3c7-S0/frameworks/8d0d7003-3072-4176-bf49-3d1551cfefb8-0000/executors/ceph_osd.15082c7d-fa9f-11e6-a02d-024287699a2c/runs/4d6175e7-a3c9-4725-ac59-9fd610b4e69d:/mnt/mesos/sandbox --net host --name mesos-8aa60360-3d0a-4713-8fe2-60046f2af3c7-S0.4d6175e7-a3c9-4725-ac59-9fd610b4e69d ceph/daemon

Note that it mounts /data/osd to /var/lib/ceph/osd and the osd directory contains a ceph-N directory where N is the OSD # that I want to run on that machine (this is supposed to allow me to bring the entire cluster up by replicating a single Marathon task and it works fine on the same machine that runs my monitor but on other machines I get the output above)

Seems like I was able to work around this by disabling auth, as I am in a safe environment this works for me, however, I would still like to know what was going wrong if you was to debug it with me

Can you look at the content of the keyring file? Just to make sure it's in a proper shape.

Contents of bootstrap-osd/ceph.keyring
[client.bootstrap-osd]
	key = AQBTvK1YEzFdHRAAeg2MNFqv79aj0w2Elrfwww==
	caps mon = "allow profile bootstrap-osd"

Is there anything that might be changing permission on the journal file/device?

I dont think so, I checked the permissions multiple times during the process and they looked correct (e.g. they always matched what the permissions were on the working machine)

Not sure if it's related but some of your -v have :rw and some don't, could this explain the permission issue?

same problem here with k8s.
running ceph by example. works fine but not persistent.
when changing the osd-ds.yaml from emptyDir: {}  to hostPath:
osd starts with error :
2017-03-27T15:16:13.027414545Z ceph-0.1 |  ceph version 11.2.0 (f223e27eeb35991352ebc1f67423d4ebc252adb7)
2017-03-27T15:16:13.027416787Z ceph-0.1 |  1: (ceph::__ceph_assert_fail(char const*, char const*, int, char const*)+0x80) [0x55d842063380]
2017-03-27T15:16:13.027418976Z ceph-0.1 |  2: (ceph::HeartbeatMap::~HeartbeatMap()+0xd1) [0x55d842149a71]
2017-03-27T15:16:13.027421149Z ceph-0.1 |  3: (CephContext::~CephContext()+0x428) [0x55d842131498]
2017-03-27T15:16:13.027426315Z ceph-0.1 |  4: (CephContext::put()+0xec) [0x55d84213178c]
2017-03-27T15:16:13.027428730Z ceph-0.1 |  5: (main()+0xd97) [0x55d8418b6f87]
2017-03-27T15:16:13.027430900Z ceph-0.1 |  6: (__libc_start_main()+0xf0) [0x7f3807eec830]
2017-03-27T15:16:13.027433082Z ceph-0.1 |  7: (_start()+0x29) [0x55d841924dc9]
2017-03-27T15:16:13.027435293Z ceph-0.1 |  NOTE: a copy of the executable, or `objdump -rdS <executable>` is needed to interpret this.
2017-03-27T15:16:13.027437933Z ceph-0.1 |
2017-03-27T15:16:13.027440854Z ceph-0.1 | *** Caught signal (Aborted) **
2017-03-27T15:16:13.027443054Z ceph-0.1 |  in thread 7f380a874a40 thread_name:ceph-osd
2017-03-27T15:16:13.029062118Z ceph-0.1 |  ceph version 11.2.0 (f223e27eeb35991352ebc1f67423d4ebc252adb7)
2017-03-27T15:16:13.029070326Z ceph-0.1 |  1: (()+0x946e4e) [0x55d841e91e4e]
2017-03-27T15:16:13.029074296Z ceph-0.1 |  2: (()+0x11390) [0x7f380990d390]
2017-03-27T15:16:13.029078074Z ceph-0.1 |  3: (gsignal()+0x38) [0x7f3807f01428]
2017-03-27T15:16:13.029081725Z ceph-0.1 |  4: (abort()+0x16a) [0x7f3807f0302a]
2017-03-27T15:16:13.029085540Z ceph-0.1 |  5: (ceph::__ceph_assert_fail(char const*, char const*, int, char const*)+0x26b) [0x55d84206356b]
2017-03-27T15:16:13.029089328Z ceph-0.1 |  6: (ceph::HeartbeatMap::~HeartbeatMap()+0xd1) [0x55d842149a71]
2017-03-27T15:16:13.029093402Z ceph-0.1 |  7: (CephContext::~CephContext()+0x428) [0x55d842131498]
2017-03-27T15:16:13.029096870Z ceph-0.1 |  8: (CephContext::put()+0xec) [0x55d84213178c]
2017-03-27T15:16:13.029100608Z ceph-0.1 |  9: (main()+0xd97) [0x55d8418b6f87]
2017-03-27T15:16:13.029104446Z ceph-0.1 |  10: (__libc_start_main()+0xf0) [0x7f3807eec830]
2017-03-27T15:16:13.029108004Z ceph-0.1 |  11: (_start()+0x29) [0x55d841924dc9]
2017-03-27T15:16:13.029111800Z ceph-0.1 | 2017-03-27 15:16:13.028863 7f380a874a40 -1 *** Caught signal (Aborted) **
2017-03-27T15:16:13.029114829Z ceph-0.1 |  in thread 7f380a874a40 thread_name:ceph-osd
2017-03-27T15:16:13.029117106Z ceph-0.1 |
2017-03-27T15:16:13.029119196Z ceph-0.1 |  ceph version 11.2.0 (f223e27eeb35991352ebc1f67423d4ebc252adb7)
2017-03-27T15:16:13.029121333Z ceph-0.1 |  1: (()+0x946e4e) [0x55d841e91e4e]
2017-03-27T15:16:13.029126874Z ceph-0.1 |  2: (()+0x11390) [0x7f380990d390]
2017-03-27T15:16:13.029129226Z ceph-0.1 |  3: (gsignal()+0x38) [0x7f3807f01428]
2017-03-27T15:16:13.029131352Z ceph-0.1 |  4: (abort()+0x16a) [0x7f3807f0302a]
2017-03-27T15:16:13.029133517Z ceph-0.1 |  5: (ceph::__ceph_assert_fail(char const*, char const*, int, char const*)+0x26b) [0x55d84206356b]
2017-03-27T15:16:13.029135728Z ceph-0.1 |  6: (ceph::HeartbeatMap::~HeartbeatMap()+0xd1) [0x55d842149a71]
2017-03-27T15:16:13.029138517Z ceph-0.1 |  7: (CephContext::~CephContext()+0x428) [0x55d842131498]
2017-03-27T15:16:13.029141994Z ceph-0.1 |  8: (CephContext::put()+0xec) [0x55d84213178c]
2017-03-27T15:16:13.029145435Z ceph-0.1 |  9: (main()+0xd97) [0x55d8418b6f87]
2017-03-27T15:16:13.029148927Z ceph-0.1 |  10: (__libc_start_main()+0xf0) [0x7f3807eec830]
2017-03-27T15:16:13.029152358Z ceph-0.1 |  11: (_start()+0x29) [0x55d841924dc9]
2017-03-27T15:16:13.029156037Z ceph-0.1 |  NOTE: a copy of the executable, or `objdump -rdS <executable>` is needed to interpret this.
2017-03-27T15:16:13.029168935Z ceph-0.1 |
2017-03-27T15:16:13.029171629Z ceph-0.1 |      0> 2017-03-27 15:16:13.028863 7f380a874a40 -1 *** Caught signal (Aborted) **
2017-03-27T15:16:13.029173942Z ceph-0.1 |  in thread 7f380a874a40 thread_name:ceph-osd
2017-03-27T15:16:13.029176865Z ceph-0.1 |
2017-03-27T15:16:13.029178922Z ceph-0.1 |  ceph version 11.2.0 (f223e27eeb35991352ebc1f67423d4ebc252adb7)
2017-03-27T15:16:13.029181398Z ceph-0.1 |  1: (()+0x946e4e) [0x55d841e91e4e]
2017-03-27T15:16:13.029183521Z ceph-0.1 |  2: (()+0x11390) [0x7f380990d390]
2017-03-27T15:16:13.029185662Z ceph-0.1 |  3: (gsignal()+0x38) [0x7f3807f01428]
2017-03-27T15:16:13.029187862Z ceph-0.1 |  4: (abort()+0x16a) [0x7f3807f0302a]
2017-03-27T15:16:13.029190094Z ceph-0.1 |  5: (ceph::__ceph_assert_fail(char const*, char const*, int, char const*)+0x26b) [0x55d84206356b]
2017-03-27T15:16:13.029192250Z ceph-0.1 |  6: (ceph::HeartbeatMap::~HeartbeatMap()+0xd1) [0x55d842149a71]
2017-03-27T15:16:13.029194365Z ceph-0.1 |  7: (CephContext::~CephContext()+0x428) [0x55d842131498]
2017-03-27T15:16:13.029196450Z ceph-0.1 |  8: (CephContext::put()+0xec) [0x55d84213178c]
2017-03-27T15:16:13.029202323Z ceph-0.1 |  9: (main()+0xd97) [0x55d8418b6f87]
2017-03-27T15:16:13.029204580Z ceph-0.1 |  10: (__libc_start_main()+0xf0) [0x7f3807eec830]
2017-03-27T15:16:13.029206623Z ceph-0.1 |  11: (_start()+0x29) [0x55d841924dc9]
2017-03-27T15:16:13.029208702Z ceph-0.1 |  NOTE: a copy of the executable, or `objdump -rdS <executable>` is needed to interpret this.
2017-03-27T15:16:13.029210922Z ceph-0.1 |
2017-03-27T15:16:13.401459159Z

disabling auth, solves this case, but not the 'problem'.

@leseb I dont think it's that, I tried every permutation of rw/permissions options I could
@J-Ha Indeed it is a (maybe bad) workaround not a solution

@Queuecumber could it be a SELinux content on the host?
Although, I'm not sure why disabling auth would solve that...

even with
sudo chcon -Rt svirt_sandbox_file_t <ceph_dir's>
same error

I need to build a k8s env to reproduce that, every installers I've found failed for me... Any hint on how to install k8s with vagrant + libvirt?
Thanks!

Same error in k8s example with empty dir, the first time osd daemonset run with no errors, but when I delete all osd pods, the pod restart with errors blow:
2017-04-28 07:11:58  /entrypoint.sh: k8s: config is stored as k8s secrets.
2017-04-28 07:11:58  /entrypoint.sh: k8s: does not generate the admin key. Use Kubernetes secrets instead.
ceph-0: /usr/bin/ceph-osd --cluster ceph -f -i 0 --osd-journal /var/lib/ceph/osd/ceph-0//journal -k /var/lib/ceph/osd/ceph-0//keyring
2017-04-28 07:11:58  /entrypoint.sh: SUCCESS
forego   | starting ceph-0.1 on port 5000
ceph-0.1 | starting osd.0 at - osd_data /var/lib/ceph/osd/ceph-0 /var/lib/ceph/osd/ceph-0//journal
ceph-0.1 | 2017-04-28 07:11:59.010832 7f5d53a93a40 -1 journal FileJournal::_open: disabling aio for non-block journal.  Use journal_force_aio to force use of aio anyway
ceph-0.1 | 2017-04-28 07:11:59.020129 7f5d53a93a40 -1 osd.0 0 log_to_monitors {default=true}
ceph-0.1 | 2017-04-28 07:11:59.048259 7f5d53a93a40 -1  ** ERROR: osd init failed: (1) Operation not permitted
ceph-0.1 | /tmp/buildd/ceph-11.2.0/src/common/HeartbeatMap.cc: In function 'ceph::HeartbeatMap::~HeartbeatMap()' thread 7f5d53a93a40 time 2017-04-28 07:11:59.048875
ceph-0.1 | /tmp/buildd/ceph-11.2.0/src/common/HeartbeatMap.cc: 46: FAILED assert(m_workers.empty())
ceph-0.1 |  ceph version 11.2.0 (f223e27eeb35991352ebc1f67423d4ebc252adb7)
ceph-0.1 |  1: (ceph::__ceph_assert_fail(char const*, char const*, int, char const*)+0x80) [0x55cc5fa3b380]
ceph-0.1 |  2: (ceph::HeartbeatMap::~HeartbeatMap()+0xd1) [0x55cc5fb21a71]
ceph-0.1 |  3: (CephContext::~CephContext()+0x428) [0x55cc5fb09498]
ceph-0.1 |  4: (CephContext::put()+0xec) [0x55cc5fb0978c]
ceph-0.1 |  5: (main()+0xd97) [0x55cc5f28ef87]
ceph-0.1 |  6: (__libc_start_main()+0xf0) [0x7f5d5110b830]
ceph-0.1 |  7: (_start()+0x29) [0x55cc5f2fcdc9]
ceph-0.1 |  NOTE: a copy of the executable, or `objdump -rdS <executable>` is needed to interpret this.
ceph-0.1 | 2017-04-28 07:11:59.050623 7f5d53a93a40 -1 /tmp/buildd/ceph-11.2.0/src/common/HeartbeatMap.cc: In function 'ceph::HeartbeatMap::~HeartbeatMap()' thread 7f5d53a93a40 time 2017-04-28 07:11:59.048875
ceph-0.1 | /tmp/buildd/ceph-11.2.0/src/common/HeartbeatMap.cc: 46: FAILED assert(m_workers.empty())
ceph-0.1 |
ceph-0.1 |  ceph version 11.2.0 (f223e27eeb35991352ebc1f67423d4ebc252adb7)
ceph-0.1 |  1: (ceph::__ceph_assert_fail(char const*, char const*, int, char const*)+0x80) [0x55cc5fa3b380]
ceph-0.1 |  2: (ceph::HeartbeatMap::~HeartbeatMap()+0xd1) [0x55cc5fb21a71]
ceph-0.1 |  3: (CephContext::~CephContext()+0x428) [0x55cc5fb09498]
ceph-0.1 |  4: (CephContext::put()+0xec) [0x55cc5fb0978c]
ceph-0.1 |  5: (main()+0xd97) [0x55cc5f28ef87]
ceph-0.1 |  6: (__libc_start_main()+0xf0) [0x7f5d5110b830]
ceph-0.1 |  7: (_start()+0x29) [0x55cc5f2fcdc9]
ceph-0.1 |  NOTE: a copy of the executable, or `objdump -rdS <executable>` is needed to interpret this.
ceph-0.1 |
ceph-0.1 |    -99> 2017-04-28 07:11:59.010832 7f5d53a93a40 -1 journal FileJournal::_open: disabling aio for non-block journal.  Use journal_force_aio to force use of aio anyway
ceph-0.1 |    -57> 2017-04-28 07:11:59.020129 7f5d53a93a40 -1 osd.0 0 log_to_monitors {default=true}
ceph-0.1 |    -25> 2017-04-28 07:11:59.048259 7f5d53a93a40 -1  ** ERROR: osd init failed: (1) Operation not permitted
ceph-0.1 |      0> 2017-04-28 07:11:59.050623 7f5d53a93a40 -1 /tmp/buildd/ceph-11.2.0/src/common/HeartbeatMap.cc: In function 'ceph::HeartbeatMap::~HeartbeatMap()' thread 7f5d53a93a40 time 2017-04-28 07:11:59.048875
ceph-0.1 | /tmp/buildd/ceph-11.2.0/src/common/HeartbeatMap.cc: 46: FAILED assert(m_workers.empty())
ceph-0.1 |
ceph-0.1 |  ceph version 11.2.0 (f223e27eeb35991352ebc1f67423d4ebc252adb7)
ceph-0.1 |  1: (ceph::__ceph_assert_fail(char const*, char const*, int, char const*)+0x80) [0x55cc5fa3b380]
ceph-0.1 |  2: (ceph::HeartbeatMap::~HeartbeatMap()+0xd1) [0x55cc5fb21a71]
ceph-0.1 |  3: (CephContext::~CephContext()+0x428) [0x55cc5fb09498]
ceph-0.1 |  4: (CephContext::put()+0xec) [0x55cc5fb0978c]
ceph-0.1 |  5: (main()+0xd97) [0x55cc5f28ef87]
ceph-0.1 |  6: (__libc_start_main()+0xf0) [0x7f5d5110b830]
ceph-0.1 |  7: (_start()+0x29) [0x55cc5f2fcdc9]
ceph-0.1 |  NOTE: a copy of the executable, or `objdump -rdS <executable>` is needed to interpret this.
ceph-0.1 |
ceph-0.1 | *** Caught signal (Aborted) **
ceph-0.1 |  in thread 7f5d53a93a40 thread_name:ceph-osd
ceph-0.1 |  ceph version 11.2.0 (f223e27eeb35991352ebc1f67423d4ebc252adb7)
ceph-0.1 |  1: (()+0x946e4e) [0x55cc5f869e4e]
ceph-0.1 |  2: (()+0x11390) [0x7f5d52b2c390]
ceph-0.1 |  3: (gsignal()+0x38) [0x7f5d51120428]
ceph-0.1 |  4: (abort()+0x16a) [0x7f5d5112202a]
ceph-0.1 |  5: (ceph::__ceph_assert_fail(char const*, char const*, int, char const*)+0x26b) [0x55cc5fa3b56b]
ceph-0.1 |  6: (ceph::HeartbeatMap::~HeartbeatMap()+0xd1) [0x55cc5fb21a71]
ceph-0.1 |  7: (CephContext::~CephContext()+0x428) [0x55cc5fb09498]
ceph-0.1 |  8: (CephContext::put()+0xec) [0x55cc5fb0978c]
ceph-0.1 |  9: (main()+0xd97) [0x55cc5f28ef87]
ceph-0.1 |  10: (__libc_start_main()+0xf0) [0x7f5d5110b830]
ceph-0.1 |  11: (_start()+0x29) [0x55cc5f2fcdc9]
ceph-0.1 | 2017-04-28 07:11:59.054238 7f5d53a93a40 -1 *** Caught signal (Aborted) **
ceph-0.1 |  in thread 7f5d53a93a40 thread_name:ceph-osd
ceph-0.1 |
ceph-0.1 |  ceph version 11.2.0 (f223e27eeb35991352ebc1f67423d4ebc252adb7)
ceph-0.1 |  1: (()+0x946e4e) [0x55cc5f869e4e]
ceph-0.1 |  2: (()+0x11390) [0x7f5d52b2c390]
ceph-0.1 |  3: (gsignal()+0x38) [0x7f5d51120428]
ceph-0.1 |  4: (abort()+0x16a) [0x7f5d5112202a]
ceph-0.1 |  5: (ceph::__ceph_assert_fail(char const*, char const*, int, char const*)+0x26b) [0x55cc5fa3b56b]
ceph-0.1 |  6: (ceph::HeartbeatMap::~HeartbeatMap()+0xd1) [0x55cc5fb21a71]
ceph-0.1 |  7: (CephContext::~CephContext()+0x428) [0x55cc5fb09498]
ceph-0.1 |  8: (CephContext::put()+0xec) [0x55cc5fb0978c]
ceph-0.1 |  9: (main()+0xd97) [0x55cc5f28ef87]
ceph-0.1 |  10: (__libc_start_main()+0xf0) [0x7f5d5110b830]
ceph-0.1 |  11: (_start()+0x29) [0x55cc5f2fcdc9]
ceph-0.1 |  NOTE: a copy of the executable, or `objdump -rdS <executable>` is needed to interpret this.
ceph-0.1 |
ceph-0.1 |      0> 2017-04-28 07:11:59.054238 7f5d53a93a40 -1 *** Caught signal (Aborted) **
ceph-0.1 |  in thread 7f5d53a93a40 thread_name:ceph-osd
ceph-0.1 |
ceph-0.1 |  ceph version 11.2.0 (f223e27eeb35991352ebc1f67423d4ebc252adb7)
ceph-0.1 |  1: (()+0x946e4e) [0x55cc5f869e4e]
ceph-0.1 |  2: (()+0x11390) [0x7f5d52b2c390]
ceph-0.1 |  3: (gsignal()+0x38) [0x7f5d51120428]
ceph-0.1 |  4: (abort()+0x16a) [0x7f5d5112202a]
ceph-0.1 |  5: (ceph::__ceph_assert_fail(char const*, char const*, int, char const*)+0x26b) [0x55cc5fa3b56b]
ceph-0.1 |  6: (ceph::HeartbeatMap::~HeartbeatMap()+0xd1) [0x55cc5fb21a71]
ceph-0.1 |  7: (CephContext::~CephContext()+0x428) [0x55cc5fb09498]
ceph-0.1 |  8: (CephContext::put()+0xec) [0x55cc5fb0978c]
ceph-0.1 |  9: (main()+0xd97) [0x55cc5f28ef87]
ceph-0.1 |  10: (__libc_start_main()+0xf0) [0x7f5d5110b830]
ceph-0.1 |  11: (_start()+0x29) [0x55cc5f2fcdc9]
ceph-0.1 |  NOTE: a copy of the executable, or `objdump -rdS <executable>` is needed to interpret this.
ceph-0.1 |

@liewegas can you help us decrypting these coredumps?
Thanks!

The crash is because OSD::init() has a buggy error path; you can ignore the assert.
I think teh error is coming from the attempt to authenticate with the mon.  Probably the keyring isn't readable or the key isn't correct or something?  You can pass debug osd = 20 and debug monc = 20 and debug ms = 1 to tell more precisely!

Same issue with kuberntes 1.6.2 using helm.For me one of the OSD is always failing.
kubectl get po -n ceph -o wide
NAME READY STATUS RESTARTS AGE IP NODE
ceph-mds-722237312-3s0vq 1/1 Running 0 19m <IP_ADDRESS> k8node03
ceph-mon-0 1/1 Running 0 19m <IP_ADDRESS> k8node05
ceph-mon-1 1/1 Running 0 15m <IP_ADDRESS> k8node03
ceph-mon-2 1/1 Running 0 15m <IP_ADDRESS> k8node06
ceph-mon-check-3190136794-rnlkr 1/1 Running 0 19m <IP_ADDRESS> k8node03
ceph-osd-06bbb 0/1 CrashLoopBackOff 5 5m <IP_ADDRESS> k8node04
ceph-osd-513kj 1/1 Running 3 19m <IP_ADDRESS> k8node03
ceph-osd-8xwkk 1/1 Running 4 18m <IP_ADDRESS> k8node06
ceph-osd-jcqkc 1/1 Running 1 19m <IP_ADDRESS> k8node05
Not sure if its key related,since other OSDs are good .

@liewegas thanks!
@Queuecumber, @krrypto  could the key be malformed?

@leseb
i am able to reproduce this issue and its environment specific.My node had previous keys,i deleted all ceph contents from /var/lib/ceph/* on  host including old keys and recreated ceph.Everything is working smooth ,thanks alot

@krrypto alright, typical leftovers :). Closing this then.


Publish a version of Visulate-Ora2Pg on Google Cloud Marketplace

Product should be packaged as a virtual machine image. Follow Cloud Marketplace instructions
The image should include versions of Ora2Pg + Visulate for Oracle. Container images for it are in the Google Container Repo - gcr.io/visulate-llc-public/visulate-for-oracle

API Server: gcr.io/visulate-llc-public/visulate-for-oracle:1.1
UI: gcr.io/visulate-llc-public/visulate-for-oracle/ui:1.1
Query Engine: gcr.io/visulate-llc-public/visulate-for-oracle/sql:1.1

The v4oracle README has instructions for running in a docker container. These haven't been tested for a while and may need to be adapted.

Angular stores environment variables like the API server location in a file that gets copied into the app bundle at build time. The file contents are concatenated with other sources into a single minified file. The file checked into source control relies on a load balancer to resolve API calls. It needs to be edited if a load balancer is not being used. Review apiBase value in visulate-for-oracle/ui/src/environments/environment.prod.ts and edit to match the API server deployment value. For example, if you plan to deploy the API server on a VM called my-api-server.com the file would look like this:

export const environment = {
  production: true,
  apiBase: 'http://my-api-server.com:3000/api',
  findObjectBase: 'http://my-api-server.com:3000/find',
  ddlGenBase: 'http://my-api-server.com:3000/ddl'
};

The API server rejects cross origin requests from URLs that have not been whitelisted. Edit visulate-for-oracle/api-server/config/http-server.js to specify the origin server where the UI will be running. For example if the UI will be served from port 8080 of my-ui-server.com:

module.exports = {
  port: process.env.HTTP_PORT || 3000 ,
  corsOriginWhitelist: process.env.CORS_ORIGIN_WHITELIST ||['http://my-api-server.com:8080'],
  logFileLocation: process.env.PWD + '/logs'
};

Pull the docker images:

docker pull gcr.io/visulate-llc-public/visulate-for-oracle:1.1
docker pull gcr.io/visulate-llc-public/visulate-for-oracle/ui:1.1
docker pull gcr.io/visulate-llc-public/visulate-for-oracle/sql:1.1

Docker pull of UI won't work. Need to figure workaround to custom build requirement

Deploy the images:

docker run -d -p 3000:3000/tcp gcr.io/visulate-llc-public/visulate-for-oracle:1.1
docker run -d -p 80:80/tcp gcr.io/visulate-llc-public/visulate-for-oracle/ui:1.1

(Optional) bind the log file directories to a persistent volume (e.g /var/log/some-directory)

docker run -d -p 3000:3000/tcp \
-v /var/log/visulate-server:/visulate-server/logs \
gcr.io/visulate-llc-public/visulate-for-oracle:1.1

docker run --rm -d -p 80:80/tcp \
-v /var/log/visulate-client:/var/log/nginx \
gcr.io/visulate-llc-public/visulate-for-oracle/ui:1.1

(Optional) Copy the visulate-for-oracle/config files to a staging directory before starting the server. This will allow you to edit the database registration file and CORS whitelist without rebuilding the image. Example:

docker run -d -p 3000:3000/tcp \
-v /home/pgoldtho/config:/visulate-server/config \
-v /var/log/visulate-server:/visulate-server/logs \
gcr.io/visulate-llc-public/visulate-for-oracle:1.1

Need to decide whether to deploy as a containerized application or OS native installation
https://cloud.google.com/community/tutorials/migrate-oracle-postgres-using-ora2pg

Google changed the terms and conditions for publishing images to Cloud Marketplace. Publishing is no longer possible


"Paths" in NUXT_DATA are picked up by Google Search Console as internal links

Environment

Operating System: Darwin
Node Version:     v18.12.1
Nuxt Version:     3.8.0
CLI Version:      3.9.1
Nitro Version:    2.7.2
Package Manager<EMAIL_ADDRESS>Builder:          -
User Config:      -
Runtime Modules:  -
Build Modules:    -

Reproduction
https://stackblitz.com/edit/github-auvqvj?file=app.vue
Describe the bug
Google's crawlers identify strings that begin with a forward slash in the payload, treating them as internal links. This leads to the appearance of non-existent pages in the Search Console, which it tries to resolve but cannot, leading to 404 errors.
The core of the issue is how these 404s are perceived as a reflection of site maintenance, potentially impacting the site's search rankings due to perceived poor maintenance.
We now have thousands of 404 warnings in search console due to this issue and it starting to become a serious concern.
Additional context
No response
Logs
No response

I wonder if there is much that we can do here from a framework perspective 🤔
Best would be to:

Update your robots.txt to exclude any possible URLs fetched
Set a robots noindex header for all payload.json files

As you can't prevent google from crawling "parts of your pages", that's IMO the best way to go.


Failed to detect the IPv4 address

😞 Failed to send HTTP(S) request to "https://cloudflare-dns.com/cdn-cgi/trace": context deadline exceeded
😞 Failed to detect the IPv4 address
Hi,
Getting this error when using the recent Edge image.
This doesn't happen with the Latest image.
Please assist.

Let me revert the latest change first.

version: "3"
services:
cloudflare-ddns:
image: favonia/cloudflare-ddns:latest
image: favonia/cloudflare-ddns:edge
container_name: cloudflare-ddns
restart: always
cap_add:
  - SETUID
  - SETGID
cap_drop:
  - all
security_opt:
  - no-new-privileges:true
read_only: true
network_mode: host
environment:
  - CF_API_TOKEN=SomeRandomToken
  - DOMAINS=example.com
  - PROXIED=true
  - PUID=1000
  - PGID=1000
  - TZ=Asia/Jerusalem
  - UPDATE_CRON=@every 5m
  - IP6_PROVIDER=none
  - DETECTION_TIMEOUT=15s

- QUIET=TRUE

@ShlomiD83 Apologies again for my insufficient testing before merging it into the main branch. I will revert the merge soon. On the other hand, may I understand why you are using the edge tag? Is there a feature you are waiting for that was not published yet?

It's stayed that way ever since the Quiet Mode message, never changed it back to the latest tag.

@ShlomiD83 Thank you. Could you confirm that the current edge tag works? If so, maybe we can close this ticket for now. Thank you again for the reporting the bug.

@favonia current edge works as expected.
Issue can be closed.
Thank you for your hard work!

@ShlomiD83 I forgot to say that it's recommended to use the latest tag (or a fixed version tag) because I'll be experimenting with new code with the edge tag. Thanks!

Thank you @favonia .
I've switched back a while ago to the latest tagged image.

@ShlomiD83 This is a head-up---recent versions (1.13.0+) will benefit from an update to your configuration, and I am on the mission to eliminate the old template from this universe. In case you or anyone is confused by how to update the configuration, here's the tl;dr:

Remove cap_add: ... completely.
Add user: "1000:1000" (or other IDs you want to use).
Remove PUID=... and PGID=... (optional, but why not).

For more information, please see the CHANGELOG and README.
PS: the new template works for older versions of the updater as well!

@ShlomiD83 This is a head-up---recent versions (1.13.0+) will benefit from an update to your configuration, and I am on the mission to eliminate the old template from this universe. In case you or anyone is confused by how to update the configuration, here's the tl;dr:

Remove cap_add: ... completely.
Add user: "1000:1000" (or other IDs you want to use).
Remove PUID=... and PGID=... (optional, but why not).

For more information, please see the CHANGELOG and README.
PS: the new template works for older versions of the updater as well!

Thanks @favonia, I've made the changes.


bisq-desktop: 1.9.9 -> 1.9.10

Description of changes

There are two changes included in this PR:

Update bisq-desktop to 1.9.10. See release notes https://github.com/bisq-network/bisq/releases/tag/v1.9.10
Add the ability to customize the JAVA_TOOLS_OPTIONS environment variable in order to allow users to configure the Java VM initialization process. See https://docs.oracle.com/en/java/javase/11/docs/specs/jvmti.html#tooloptions

Instead of having a fixed value, now JAVA_TOOLS_OPTIONS can be modified using the derivation input overrideJavaToolOptions, which is a function that is provided the default JAVA_TOOLS_OPTIONS settings in the form of a set, and returns an equivalent set. Something like this:
overrideJavaToolOptions = { flags, options } @ attrs: attrs
The default implementation is the identity function, which in turn causes JAVA_TOOLS_OPTIONS to retain the default settings. However, the implementation can be replaced by users in order to modify the flags (a list of settings which can be toggled on/off) and options (a set of settings which have a value).
For example, the default flag "XX:+UseG1GC" can be removed by filtering it out:
(bisq-desktop.override {
  overrideJavaToolOptions = orig: {
    flags = builtins.filter (flag: flag != "XX:+UseG1GC") orig.flags;
    options = orig.options;
  };
})

An option can be added by merging it with the original options:
(bisq-desktop.override {
  overrideJavaToolOptions = orig: {
    flags = orig.flags;
    options = { "Dglass.gtk.uiScale" = "2.0"; } // orig.options;
  };
})

Things done

Built on platform(s)

[X] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[X] Tested basic functionality of all binary files (usually in ./result/bin/)
23.05 Release Notes (or backporting 22.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[X] Fits CONTRIBUTING.md.

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-ready-for-review/1016/58

Replaced by #240155


e2e tests should run on min. supported sdk versions

running on the min. supported SDK version, we'd be able to catch back-compatibility during CI run and avoid #634 similar issues

Currently you can't run the tests in the Flutter SDK on Flutter 2.0.x up until at least 2.2.3

Currently you can't run the tests in the Flutter SDK on Flutter 2.0.x up until at least 2.2.3

why so? do we use features on tests that are not available under the min. supported Dart/Flutter SDK? if so, we'd need to adjust the tests then.

It's because of the dev_dependencies having higher requirements than the minimal supported Flutter version.

It's because of the dev_dependencies having higher requirements than the minimal supported Flutter version.

Gotcha, we'd need to downgrade then to make it work, it's better to detect issues on CI in advance rather than using the latest tooling on dev deps.


update tutorials

partial issue #88
-swm
-burst
-tiemfrequency
-laggedcoherence

since these are just (non-breaking) notebook updates, I'm gonna go ahead and merge this.


IE11 bug fixes

IE11 does not support Array.find

Coverage remained the same at 63.626% when pulling b51e048741090412bfe28315ceda3be35d731987 on ie11-bugs into<PHONE_NUMBER>9eeb6783375ced5db8a8c8cba2cf00 on master.


Compliance report pulling old Tenancy name

Hi, Running the CIS compliance report via Python -- it works fine and outputs the reports as it should.
Only thing is, we have renamed our Tenancy and it is somehow pulling the old tenancy name -- any idea why?

Thank you for bringing this to our attention. The reason you are seeing your old tenancy name is because we are using the tenancy's description not the tenancy's name as part of the file name.  We will fix this in our next release.


A proper onboarding for new users

Teach them how to use the app!

Concept: drop people in a newbie "reception" area. During the event, an actual human volunteer sits there and welcomes people, explains how to use the space, etc. The virtual version of phildini and/or Asheesh at the GH entrance.
If they can figure out how to leave, that's a pretty good metric 😂


Move to haskell-cryptography organization

See https://discourse.haskell.org/t/a-new-future-for-cryptography-in-haskell/3888

After some discussions with more people we decided to not do this for now, because this new organization is still fairly new, and we don't know whether it's going to be healthy/functional/useful. For now, this project is going to stay under the Tweag organization and is going to be maintained by at least me.


Disable ResourceOwnerPasswordValidator by default in SPA template

This should flow to all other identity server templates
cc @blowdart

Per brock's email sounds like we don't need to do this anymore


⚠ Bofrost.at has degraded performance

In 0a7a366, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1555 ms

Resolved: Bofrost.at performance has improved in 7290f80 after 9 minutes.


Crash report

Godot version: 3.2-stable
OS/device including version: Linux Mint 19.1
Issue description:  Crash when i tried move a gui object with editor
Steps to reproduce: Casual issue
Crash Report
handle_crash: Program crashed with signal 11
Dumping the backtrace. Please include this when reporting the bug on https://github.com/godotengine/godot/issues
[1] /lib/x86_64-linux-gnu/libc.so.6(+0x3ef20) [0x7f40646d2f20] (??:0)
[2] /home/leandro/Downloads/Godot_v3.2-stable_x11.64() [0xbd4580] (??:?)
[3] /home/leandro/Downloads/Godot_v3.2-stable_x11.64() [0x18c3b31] (??:?)
[4] /home/leandro/Downloads/Godot_v3.2-stable_x11.64() [0x8ea750] (??:?)
[5] /home/leandro/Downloads/Godot_v3.2-stable_x11.64() [0x1d92781] (<artificial>:?)
[6] /home/leandro/Downloads/Godot_v3.2-stable_x11.64() [0x1d9756e] (<artificial>:?)
[7] /home/leandro/Downloads/Godot_v3.2-stable_x11.64() [0x2717936] (??:?)
[8] /home/leandro/Downloads/Godot_v3.2-stable_x11.64() [0xbe22e3] (??:?)
[9] /home/leandro/Downloads/Godot_v3.2-stable_x11.64() [0xc88666] (??:?)
[10] /home/leandro/Downloads/Godot_v3.2-stable_x11.64() [0xc89660] (??:?)
[11] /home/leandro/Downloads/Godot_v3.2-stable_x11.64() [0x18e4b2d] (<artificial>:?)
[12] /home/leandro/Downloads/Godot_v3.2-stable_x11.64() [0x18e4f06] (??:?)
[13] /home/leandro/Downloads/Godot_v3.2-stable_x11.64() [0x18e505e] (<artificial>:?)
[14] /home/leandro/Downloads/Godot_v3.2-stable_x11.64() [0x2717936] (??:?)
[15] /home/leandro/Downloads/Godot_v3.2-stable_x11.64() [0xbe22e3] (??:?)
[16] /home/leandro/Downloads/Godot_v3.2-stable_x11.64() [0xbca5f5] (??:?)
[17] /home/leandro/Downloads/Godot_v3.2-stable_x11.64() [0x1879173] (??:?)
[18] /home/leandro/Downloads/Godot_v3.2-stable_x11.64() [0x187c29c] (??:?)
[19] /home/leandro/Downloads/Godot_v3.2-stable_x11.64() [0x28bdf43] (??:?)
[20] /home/leandro/Downloads/Godot_v3.2-stable_x11.64() [0x28bb1ad] (<artificial>:?)
[21] /home/leandro/Downloads/Godot_v3.2-stable_x11.64() [0x29fd1ab] (<artificial>:?)
[22] /home/leandro/Downloads/Godot_v3.2-stable_x11.64() [0x84876c] (??:?)
[23] /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xe7) [0x7f40646b5b97] (??:0)
[24] /home/leandro/Downloads/Godot_v3.2-stable_x11.64() [0x855b0e] (??:?)
-- END OF BACKTRACE --

Please use a debug build to give a more detailed stacktrace, and provide a sample project and/or more detailed steps on how to reproduce this.

Closing due missing minimal project and no response


Added list billable member func

Under the same API as the regular group member functions, GitLab has a list "billable" group members function that was released fairly recently. See: https://docs.gitlab.com/ee/api/members.html#list-all-billable-members-of-a-group
The structure of a billable group member is fairly close to that of a regular group member, but the main difference is the removal of the expires_at, access_level, and group_saml_identity fields, and the addition of a last_activity_on field.

"Done" playing with this now 😄 Had some conversations internal to my group regarding this API function addition that caused some post-PR opening changes.
I know the convention you tend to prefer (and it makes sense to me) is to have a new service for each html file in GitLab's API docs, and this is underneath members.html. I looked for a members.go, but it looks like everyone else has been putting these functions under group_members.go or project_members.go so far. If you require it to be a new service, let me know and I can do that.


Unsaved Changes Prompt

Describe the bug in current situation
Users are able to navigate away from the request details screen without a warning when there are unsaved changes
Link bug to the User Story
Noticed in testing of #566 however this behaviour is expected to be consistent for all personas for unsaved changes
Impact of this bug
Impact is high. Users are not given a warning that their changes have not been saved and will lose work with no knowledge of what has happened.
Chance of Occurring (high/medium/low/very low)
High. Behaviour occurs with several changes and may not be noticed by the user.
Pre Conditions: which Env, any pre-requesites or assumptions to execute steps?
Steps to Reproduce
Steps to reproduce the behavior:

Go to request details page as a Ministry user
Click on a Select Division and make a selection, and Select Division Stage and make a selection
Click on 'FOI' at the top of the left nav bar to return to the queue
See that user is returned to queue without a warning that there are unsaved changes

Actual/ observed behaviour/ results
Expected behaviour
When a user has made changes and not saved these changes, then the application should prompt with a warning that unsaved changes will be lost when the user tries to navigate away from the current page
Screenshots/ Visual Reference/ Source
If applicable, add screenshots to help explain your problem. You an use screengrab.

@aparna-aot  - please test #1669

handled as part of #1669

Bug has been fixed. Users are prompted with a pop-up that there changes will not be saved if they try to navigate away from the form after making changes. Moving to closed


Automated Package Upgrade

:tada: This PR is included in version 5.0.530 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


[V3] Handling Releasing

Next work load that will be added to my queue:

[x] Create a project for CDN
[x] Create a script that:

[x] Gets all tagged builds from github
[ ] Figures out which tagged builds aren't on the CDN
[x] Collects all dev.js, prod.js and .js.map files for each tag and create directories for each tag
[x] Upload these collections into the CDN.

[x] Create a script that will collect the dev.js, prod.js and .js.map files for a specific tag, create a tar.gz and upload them to a github release.
[ ] Create a script that will collect the dev.js, prod.js and .js.map files for a specific tag, create a .zip and upload them to a github release.
[x] Finally find either an elegant way to add this script to the end of the lerna publish script OR add the lerna publish step as a pre-requisite in this script.

This should be handled by #746
The rough idea being that:

lerna publish is run from gulp publish
Once lerna publish is run, it'll publish a new tag to git
gulp publish-bundle will be run from gulp publish

This task will then grab the current git tags and find ones without releases or releases without assets
The script will create a github release
Build the git tag and generate a .tar.gz and upload it to the github release.
Then upload this to the CDN.

The only different from above is that a .zip isn't generated and the storage bucket assumes if it's in Github, it's in the CDN.

@gauntface It appears the items on this one are complete. Is there anything left to be completed?


add some collated

Pull Request Test Coverage Report for Build 239

0 of 0 (NaN%) changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 62.101%

Totals

Change from base Build 238:
0.0%

Covered Lines:
2022

Relevant Lines:
3256

💛  - Coveralls


Bqml vertex model registry

REQUIRED: Add a summary of your PR here, typically including why the change is needed and what was changed. Include any design alternatives for discussion purposes.

Removed two repeated Vertex AI resources in the notebook objective section for clarity.

REQUIRED: Fill out the below checklists or remove if irrelevant

If you are opening a PR for Official Notebooks under the notebooks/official folder, follow this mandatory checklist:

[x] Use the notebook template as a starting point.
[x] Follow the style and grammar rules outlined in the above notebook template.
[x] Verify the notebook runs successfully in Colab since the automated tests cannot guarantee this even when it passes.
[ ] Passes all the required automated checks. You can locally test for formatting and linting with these instructions.
[x] You have consulted with a tech writer to see if tech writer review is necessary. If so, the notebook has been reviewed by a tech writer, and they have approved it.
[x] This notebook has been added to the CODEOWNERS file under the Official Notebooks section, pointing to the author or the author's team.
[x] The Jupyter notebook cleans up any artifacts it has created (datasets, ML models, endpoints, etc) so as not to eat up unnecessary resources.

1 DISPLAY_NAME = "video_classification" + UUID
Step #5: ----> 3 job = aip.PipelineJob(
Step #5:       4     display_name=DISPLAY_NAME,
Step #5:       5     template_path="video_classification_pipeline.json",
Step #5:       6     parameter_values=parameters,
Step #5:       7     enable_caching=False,
Step #5:       8 )
Step #5:      10 job.run(service_account=SERVICE_ACCOUNT)
Step #5:
Step #5: NameError: name 'aip' is not defined


add head_only option

@Klaim we need this for the latest mamba release.

@JohanMabille this is to include in the powerloader release once merged


sat2018.forsyte.tuwien.ac.at is down

The sources of the 2018 are no longer available at sat2018.forsyte.tuwien.ac.at
Is there any copy somewhere?

Hey @pauleve, I have all SAT2018 solvers that I saved before the website went down. How can I contribute?

Great news :-) Ideally, we should store them on zenodo.
Can you share them with me (loic.pauleve@labri.fr), for instance using wetransfer? I can then make sure you can easily rebuild the docker images from them and then create the persistent zenodo record.


ASDF Provider: Support for .tool-versions

Feature request: If a .tool-versions file (used by asdf) is in the root of the directory, use the providers and versions it defines.

We don't use asdf anywhere fwiw

Just to clarify, my suggestion isn't that asdf is used to install the necessary packages. Instead that the .tool-versions file used by asdf could be used to determine providers and versions.
Here's an example .tool-versions file:
python 3.8.12
nodejs 16.14.2

My suggestion is that nixpacks could read this file and then know to use the nodejs provider and python provider with the versions specified. #237 is somewhat related.

So we just need to parse that file. In that case, this is the same as parsing .node-version, but we just need to find a line that starts with nodejs and get that version. (this was just an example)
Should the title of the issue be changed?

Going to make a function on app called read_tool_versions which takes a regex for matching the version. Should the version inside .tool-versions take priority over environment variables and something like the engines field in package.json?

My 2¢, it should be lower on the priority list. asdf is primarily used for local development environments afaik. So, it can serve as a good hint about what to use, but it should be easy for folks to override if they want to. A specific use case might be if you always want to run the latest node 16.x. I don't think asdf supports that, so a user might want to specify that in nixpacks over the pinned version in .tool-versiosn

Good idea! In the spectrum of priority it'll be at the lowest.

Closing in favour of the discussion item https://github.com/railwayapp/nixpacks/discussions/245.

I would also like support for .tool-versions. We've had users expect that this would be used by default for version detection.


Add db write option

@mauriciofreshw Should we apply the same condition to the sendPhacToSBC job?

@mauriciofreshw Should we apply the same condition to the sendPhacToSBC job?

We have conditions on mark-duplicates.js used by sendPhacToSBC, we still want Infos about what the lambda would do, so the job is not entirely off.

@mauriciofreshw Should we apply the same condition to the sendPhacToSBC job?

We have conditions on mark-duplicates.js used by sendPhacToSBC, we still want Infos about what the lambda would do, so the job is not entirely off.

I think it wouldn't hurt to add it to sendPhacToSBC as well, as in the function in send-to-sbc.js. That's more of a failsafe than anything since the changes in mark-duplicates.js should prevent that from being called.

@mauriciofreshw Should we apply the same condition to the sendPhacToSBC job?

We have conditions on mark-duplicates.js used by sendPhacToSBC, we still want Infos about what the lambda would do, so the job is not entirely off.

I think it wouldn't hurt to add it to sendPhacToSBC as well, as in the function in send-to-sbc.js. That's more of a failsafe than anything since the changes in mark-duplicates.js should prevent that from being called.

Totally, just added. Thanks :)


fix time window active type when the current day is not listed as active but still triggers the subscription

Signed-off-by: Mike Ng<EMAIL_ADDRESS>

/test test-unit


px.histogram: marginal beaks facet_col

Adding marginal to px.histogram breaks the facet_col breakdown.

Yes, today faceting and marginals are incompatible and marginals win out... Sometime in the future we'll make it such that you can get both :)

This now done, you can get marginals on top when using facet_col


feat: add diagnostics

Proposed change

Add diagnostics for troubleshooting.
Type of change

[ ] Dependency upgrade
[ ] Bugfix (non-breaking change which fixes an issue)
[x] New feature (which adds functionality)
[ ] Breaking change (fix/feature causing existing functionality to break)
[ ] Code quality improvements to existing code or addition of tests
[ ] Documentation update
[ ] Adds a new shipper
[ ] Update existing shipper

Additional information

This PR is related to issue: n/a

Codecov Report

Merging #632 (1851373) into dev (71c9d42) will increase coverage by 0.02%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##              dev     #632      +/-   ##
==========================================
+ Coverage   98.30%   98.33%   +0.02%
==========================================
  Files           6        7       +1
  Lines        1355     1378      +23
==========================================
+ Hits         1332     1355      +23
  Misses         23       23

Impacted Files
Coverage Δ

custom_components/mail_and_packages/diagnostics.py
100.00% <100.00%> (ø)


ADD: section for troubleshooting in readme.md

I added a section with information on the problems I ran into getting the HVX sample application to run on my OpenQ 820 develoment board.

Can one of the admins verify this patch?

I signed it!
On Wed, Feb 22, 2017 at 11:08 AM, googlebot<EMAIL_ADDRESS>wrote:

Thanks for your pull request. It looks like this may be your first
contribution to a Google open source project. Before we can look at your
pull request, you'll need to sign a Contributor License Agreement (CLA).
📝 Please visit https://cla.developers.google.com/
https://cla.developers.google.com/ to sign.
Once you've signed, please reply here (e.g. I signed it!) and we'll
verify. Thanks.

If you've already signed a CLA, it's possible we don't have your
GitHub username or you're using a different email address. Check your
existing CLA data https://cla.developers.google.com/clas and verify
that your email is set on your git commits
https://help.github.com/articles/setting-your-email-in-git/.
If you signed the CLA as a corporation, please let us know the
company's name.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/tensorflow/tensorflow/pull/7773#issuecomment-281625003,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AFRAOVSl5Zn1CfIvAP4NVRS7-E5rkFzWks5rfAkvgaJpZM4MIcFp
.

Jenkins, test this please.


Warn if there are unstopped threads

One of the goals with UCXX is to, as much as possible, prevent the user from having to manually cleanup resources, which allows for a simpler programming model and prevents memory leaks. However, there are some resources that are notably difficult to ensure they will be cleaned up appropriately, threads for example.
With this PR the user will now be warned about running threads when a worker is being destroyed, but will nevertheless attempt to stop them. The expectation is that with this change the user can be told how to resolve such problems so that it can be done manually to guarantee there's no leakage of resources in the running thread. What currently happens is, when a certain codeblock causes a ucxx::Worker to go out-of-scope, if care is not taken to ensure, for example, the progress thread has already completed processing all pending tasks (e.g., ucxx::Requests), the surviving thread will end up destroying the ucxx::Worker, and subsequently itself, from the running progress thread which is an invalid pattern and will cause deadlocks. This is currently observed intermittently in some C++ tests, where std::system_error may be raised:
terminate called after throwing an instance of 'std::system_error'
  what():  Resource deadlock avoided
timeout: the monitored command dumped core

The tests are also modified to apply this pattern of calling ucxx::Worker::stopProgressThread() at teardown, and thus prevent errors like above from occurring.
It may still be possible to handle this issue more gracefully, but for the moment it's best to ensure the user takes care of it while a more resilient solution can be worked on.

Thanks @wence- for the review and fixes.

/merge


Multidimensional array

Hi,
I've got an excel file like this:

A
B

settings.layout[0][]
[i]

settings.layout[0][]
[e]

settings.layout[0][]
[ɛ]

settings.layout[0][]
[a]

settings.layout[0][]
[y]

settings.layout[0][]
[ø]

settings.layout[0][]
[œ]

settings.layout[0][]
[u]

settings.layout[0][]
[o]

settings.layout[1][]
[ɔ]

settings.layout[1][]
[ɛ̃]

settings.layout[1][]
[f]

I excepted the output to be:
[
    {
        "settings": {
            "layout": [
                [
                    "[i]",
                    "[e]",
                    "[ɛ]",
                    "[a]",
                    "[y]",
                    "[ø]",
                    "[œ]",
                    "[u]",
                    "[o]",
                ],
                [
                    "[ɔ]",
                    "[ɛ̃]",
                    "[f]",
                ]
            ]
        }
    }
]

But instead I get:
[
    {
        "settings": {
            "layout[0]": [
                "[o]"
            ],
            "layout[1]": [
                "[f]"
            ],
            "layout[3]": [
                "****"
            ]
        }
    }
]

Am I missing something or the plugin doesn't handle the array markup recursively?
If I have in something like this in Excel:

A
B

settings.other[0].setting1
value1

settings.other[0].setting2
value2

I got the following output (as expected):
[
    "settings": {
      "other": [
        {
          "setting1": "value1",
          "setting2": "value2"
        }
      ]

But how I define an array in setting1? If I do:

A
B

settings.other[0].setting1[]
value1.1

settings.other[0].setting1[]
value1.2

settings.other[0].setting2
value2

I got the following output:
[
  "settings": {
    "other": [
      {
        "setting1": [
          "value1.2"
        ],
        "setting2": "value2"
      }
    ]
  }
]

Thanks for your help.

Hi,
You're right, I should have read the readme more carefully.
Thanks for the quick answer.

Implementation notes:
Provide syntax for creating multidimensional arrays as values:
[{
  "settings": {
    "layout": [
      ["[i]", "[e]", "[ɛ]", "[a]", "[y]", "[ø]", "[œ]", "[u]", "[o]"],
      ["[ɔ]", "[ɛ̃]", "[f]"]
    ]
  }
}]

Perhaps names[[n]] = value would set contents of the nth row - keeping with our path = value assignment strategy. But:

How many dimensions should be supported?
Should the multidimensional array be allowed as a value? Requires adding another value parser.
Will the above break existing users - if they have value cells with a leading [?


Test issue

This is an issue for everyone to comment below.

It says: Rating: { "offensive": 8, "anger": 7 }


[FEATURE] Onboard distribution level BWC bundle test

Currently security repo has BWC test on plugin level and only tested within the repo. We have a framework for BWC distribution level test available and you could utilize it and enable distribution level BWC test.
With this framework, you would be able to spin up the test cluster with the latest distribution bundle that engineering effectiveness team generated that installs all the other components. This test will be more comprehensive as it will test the exact product we ship to the customers.
Onboarding this distribution level BWC test can also enable engineering effectiveness team to run BWC tests every time ee team generates a new bundle distribution across each of the plugin through CI
More onboarding info can be found here:
https://github.com/opensearch-project/opensearch-plugins/blob/main/TESTING.md#bwc-tests-on-distribution-bundle-level
What solution would you like?
Similar to what we did to the anomaly-detection plugin. https://github.com/opensearch-project/anomaly-detection/pull/766
Enable bundle level BWC test based on the BWC test you already have.

[Triage] Hi @zelinh, thank you for filing this issue. Based on the linked campaign it seems like this is coming from a build team effort. Can we expect a build team member to be opening a pull request to make this change or are you looking for each repo to swap to the new framework themselves? We can close this issue when we have swapped over to the new framework so going to mark as triaged.

Hi @scrawfor99, we are looking for each plugin team to onboard to this distribution level BWC tests since we have an existing framework for this. It's not swapping; currently the BWC tests most teams running are plugin level tests which was testing the plugin within cluster with only core and this particular plugin.
We want each team to onboard to this distribution level BWC tests framework as well so that we are testing in this case, security plugin with a whole bundle cluster.

This is not going to be complete by 2.13 considering the lack of PR. I am removing the tag.

Can we get some traction on this issue? This BWC tests request would be a future release blocker.

@stephen-crawford Do we have a plan to onboard to this distribution level BWC test? We are planning to add BWC tests as mandatory exit criteria in future releases.


VPRB-221  Accessibility: [react-datepicker] add aria-selected to current selection

What does this PR do?
This PR adds aria-selected to the element which represents the current selection, i.e. has the *--selected class
It also groups up some of the tests into describe blocks to reduce code duplication and show that some tests are related
Actual Result:
Narrator Behaviour: "Choose Wednesday September 29, 2021, button"
Expected Result:
Narrator Behaviour: "Choose Wednesday September 29, 2021, button,  selected"
Related Issue:
#3160

Amazing work, thanks again for your support!