Update travis-config to latest version

Fixing some of the same issues that came up in https://github.com/travis-ci/travis-listener/pull/16 and others.
Since travis-config is still on the 0.1.X version instead of 1.X.X version in this project it felt like a good time to get it in line with other projects that have a direct dependency with travis-config (as opposed to travis-core).
Once this gets into master, I'll be looking at creating a backport for Enterprise 2.0. 👍

I'm seeing a lot of deps being downgraded as a result of this.

I'm seeing a lot of deps being downgraded as a result of this.

Eep. Good :eye:. Should just be travis-config and hashr Looks like the rebundle off of the merge conflict is giving me the business. Fixing.

@igorwwwwwwwwwwwwwwwwwwww - OK, should be fixed with https://github.com/travis-ci/travis-logs/pull/45/commits/775c4407a8785d413bdb27656503da3eb8569686
Really glad you caught that! 🙌

I'm getting some pretty bizarre spec failures in this. Bounced off of them yesterday but getting master builds work in Enterprise is already a week behind, so if anyone has time to take a look that would be amazing. I'm probably missing something fairly obvious. Also I'm not sure what I did in https://github.com/travis-ci/travis-logs/pull/45/commits/e275aaf515e3a93164994f6e6b792dd727817893 was a good approach even if it did make a couple spec failures better.
Also there's this whole Travis::Logs.config vs Travis.config thing going on (Travis.config just points at Travis::Logs.config, but I'm wondering if when dealing with stubbing out responses it's causing issues).
Also https://github.com/travis-ci/travis-config/pull/9 needs to be pulled in for this to work in HA setups where the amqps protocol is used, which also needs some review before I merge it.

Added some hacks, it's passing now! :)

Added some hacks, it's passing now! :)

YESSSSSS. Thanks so much for doing this. Deploying to staging now. 🚢

This is currently crashing in staging due to some travis-support and Hashr issues. As mentioned in slack:

New dev question of the day! How actively is travis-support being used by other projects? Is this something that's deprecated or still being used. Big question is that while tracking down the errors in travis-logs after updating travis-config the new behavior of Hashr (where it nolonger is a type of Hash so hash functions return nil. breaks the AMQP support. You can see this here: https://github.com/travis-ci/travis-support/blob/master/lib/travis/support/amqp/march_hare/consumer.rb#L23 leading to https://github.com/travis-ci/travis-support/blob/master/lib/travis/support/amqp/march_hare/consumer.rb#L54-L56 returning nil.

This will need to be fixed in order to move on with this PR, for the ends of getting master building for Enterprise, I may just need to port some of the changes done in the Enterprise 2.0 branch and move on until we can come back to fixing this issue. Exploring that now as I'm already 2-3 levels deep into this yak shave.
Oh yes, and the error in logs itself looks like:
› ./bin/receive_logs
I ** Starting Log Parts Processor **
I Starting metriks reporter librato.
I No metriks reporter configured.
D [consumer] subscribing to "reporting.jobs.logs" with nil
NoMethodError: undefined method `[]' for nil:NilClass
  build_consumer at /Users/bnferguson/.rbenv/versions/jruby-<IP_ADDRESS>/lib/ruby/gems/shared/gems/march_hare-2.21.0-java/lib/march_hare/queue.rb:158
       subscribe at /Users/bnferguson/.rbenv/versions/jruby-<IP_ADDRESS>/lib/ruby/gems/shared/gems/march_hare-2.21.0-java/lib/march_hare/queue.rb:179
       subscribe at /Users/bnferguson/.rbenv/versions/jruby-<IP_ADDRESS>/lib/ruby/gems/shared/bundler/gems/travis-support-2cd02d2a06fd/lib/travis/support/amqp/march_hare/consumer.rb:29
       subscribe at /Users/bnferguson/dev/travis-logs/lib/travis/logs/receive/queue.rb:25
       subscribe at /Users/bnferguson/dev/travis-logs/lib/travis/logs/receive/queue.rb:14
    block in run at /Users/bnferguson/dev/travis-logs/lib/travis/logs/receive.rb:30
            upto at org/jruby/RubyInteger.java:134
             run at /Users/bnferguson/dev/travis-logs/lib/travis/logs/receive.rb:29
          <main> at ./bin/receive_logs:10```

Naturally as soon as I write that, I realize we

Already have the newest travis-config working in enterprise-2.0
The reason that works is because we don't use travis/support/amqp anymore but instead use the travis/amqp gem which has been corrected for the issues I've pointed out. :tada:

This is now working locally. Will get on about testing in it staging and getting it out later tonight.


Animation crashes upon attempt to insert dynamic data to Accordion

Hi. When trying to initialize an accordion with dynamic data, the animation is dropped. Here's an example of inserting data:
  <sui-accordion-panel *ngFor="let item of test.measurements_parameters | keys; let firstState = first;" [isOpen]="firstState">

      <accordion-title [category]="item"></accordion-title>

      <accordion-content [parameters]="item.value"></accordion-content>

  </sui-accordion-panel>

It's not so important how I get the data, but I'll just show that it happens dynamically:
 private getLatestTest(): void
  {
     this.testsService.getLatestTest().then(
       data =>
       {
          this.dataProcessing(data['_items'][0]);
       },
       error =>
       {
          this.errorProcessing(error);
       }
     );
  }

In order to double-check everything, I tried to change the data by clicking on the button:
<sui-accordion class="styled fluid">

  <sui-accordion-panel *ngFor="let item of dummyData">

      {{ item.propOne }}

      {{ item.propTwo }}

  </sui-accordion-panel>

</sui-accordion>

...

  onBtnClick()
  {
     this.fakeData = [ {propOne: 'anotherOne', propTwo: 'anotherTwo'}, {propOne: 'one', propTwo: 'two'} ];
  }

Behavior remains the same, animation crashes with dynamic data. How can I pass dynamic data to accordion? Now this is possible only with the help of resolvers, but this option does not quite fit me.

0.6.5 now contains a fix for this - updating the values with ngFor no longer breaks the animation.

It looks like that in 0.9.7 the error with dynamical accordions with *ngFor is still there.


transaction sign complains when signing with cc-cold-keys

cardano-cli conway transaction sign \
--testnet-magic 42 \
--tx-body-file example/transactions/authorization-tx.raw \
--signing-key-file example/utxo-keys/payment1.skey \
--signing-key-file example/cc/cold1-cc.skey \
--out-file example/transactions/authorization-tx.signed

Command failed: transaction sign  Error: Error reading signing key: example/cc/cold1-cc.skey:
TextEnvelope type error:  Expected one of: PaymentSigningKeyByron_ed25519_bip32,
PaymentSigningKeyShelley_ed25519, PaymentExtendedSigningKeyShelley_ed25519_bip32,
StakeSigningKeyShelley_ed25519, StakeExtendedSigningKeyShelley_ed25519_bip32,
StakePoolSigningKey_ed25519, GenesisSigningKey_ed25519, GenesisExtendedSigningKey_ed25519_bip32, GenesisDelegateSigningKey_ed25519,
GenesisDelegateExtendedSigningKey_ed25519_bip32, GenesisUTxOSigningKey_ed25519,
DRepSigningKey_ed25519 Actual: ConstitutionalCommitteeColdSigningKey_ed25519

This is required to sign transaction that includes
hot-key-authorization-certificate
cardano-cli conway governance committee create-hot-key-authorization-certificate \
--cold-verification-key-file cold1-cc.vkey \
--hot-key-file hot1-cc.vkey \
--out-file hot-key1-cc-authorization.cert

cardano-cli --version
cardano-cli <IP_ADDRESS> - linux-x86_64 - ghc-9.2
git rev 000ba9c1d59efb2dc9f4ae3e7910dba7787f46cf

@CarlosLopezDeLara> can you provide the inputs file you used to test this?

@smelc those come from a local cluster that is on the trash now.  I have a series of scripts for testing Conway functionalities and help me create all these artifiacts.  Would it help for me to put them on the repo together with the /scripts/babbage/mkfiles.sh?

Here you go @smelc
Archive.zip

@carbolymer will take care of this one in the end (as agreed on Slack) as I'm not finished with https://github.com/input-output-hk/cardano-cli/pull/322 yet.


Typo mistake in install command

bin/gpm install image_collage
must be
bin/gpm install image-collage

Thanks, fixed documentation, 83b65783d218bb257fc278b705038053c537a721


SCANsat support

https://github.com/S-C-A-N/SCANsat
It's a fun mod that adds new parts which have different scanning capabilities.  Science is generated as a result, and the science list tool gets a little confused.
I can provide persistent.sfs files with relevant data if that helps.

Hey Please provide the sfs file.

https://gist.github.com/mathuin/369c3a5d1bc427847f57

I'm not too sure what you are expecting to see.
The ScanSat is added to the tool.  As you do science on more rails it'll pick it up.  I see what you mean that maybe a little confusing because it seems to only pick up one biome.  I don't use ScanSat myself so I'm not sure how it can be effectively added.
Are you suggesting there should be a separate table?  Or that the output of the table doesn't match how scan sat is actually used?

Sorry it took me so long to respond -- I finally got my PC back with the game. :-)
The page is organized first by location, then by situation, then by biome, followed by "instrument".
As an example, that file shows 94.67% completion for the mystery goo instrument in the biome "Mission Control" located on the surface of Kerbin.  So far, so good.
The SCANsat data is rendered by the page by adding a fake biome "surface" to every situation at every location.  Additionally, an instrument "SCANsatAltimetryLoRes" is added in this file.  Any science collected by the low-resolution altimetry sensor (the only instrument I've used) is recorded in the fake biome "surface" in the situation "SpaceHigh" for the relevant location.  In this example, 80% of Kerbin has been surveyed by the instrument, 100% of Mun, and 90.97% of Minmus.
I do not think adding the fake biome "surface" to all the things is a good idea.  Unfortunately, I don't have many good ideas. :-)  One suggestion would be a situation-wide bar (like those used for vessel recovery and other instruments) or maybe a location-wide bar for each SCANsat instrument.  It all depends on what the other instruments do, to be honest.  This is the only instrument I've used -- I am hoping someone else can contribute an sfs file with more instruments so we can see what they do, but I suspect they do the same.
What do you think?

I might have time this summer to add support for this mod, and if it turns out to be not too difficult, I might try to add support for Kerbalism as well.  That one is more complex, but SCANsat seems pretty straightforward.
Is it worth trying to implement this myself?  Would you accept a PR if I sent it?


GH-39771: [C++][Device] Generic CopyBatchTo/CopyArrayTo memory types

Rationale for this change
Right now our MemoryManager interfaces operate solely at the buffer level and we do not provide any higher level facilities to copy an entire array or record batch between memory types. We should implement CopyArrayTo and CopyBatchTo functions which recursively utilize the buffer level copying to create a new Array/RecordBatch whose buffers have been copied to the destination memory manager.

What changes are included in this PR?
Exposing a CopyArrayTo and CopyBatchTo function for copying entire Array or RecordBatches between memory types.

Are these changes tested?
Tests are still being written but will be added.

Closes: #39771

Wow. This is what I wanted when I wrote #39164.
Could you replace the copy routine in the change with this something like the following?
diff --git a/cpp/src/arrow/ipc/read_write_test.cc b/cpp/src/arrow/ipc/read_write_test.cc
index bd2c2b716d..a462dd2beb 100644
--- a/cpp/src/arrow/ipc/read_write_test.cc
+++ b/cpp/src/arrow/ipc/read_write_test.cc
@@ -1336,31 +1336,11 @@ class CopyCollectListener : public CollectListener {

   Status OnRecordBatchWithMetadataDecoded(
       RecordBatchWithMetadata record_batch_with_metadata) override {
-    auto& record_batch = record_batch_with_metadata.batch;
-    for (auto column_data : record_batch->column_data()) {
-      ARROW_RETURN_NOT_OK(CopyArrayData(column_data));
-    }
+    ARROW_ASSIGN_OR_RAISE(record_batch_with_metadata.batch,
+                          CopyBatchTo(record_batch_with_metadata.batch,
+                                      default_cpu_memory_manager()));
     return CollectListener::OnRecordBatchWithMetadataDecoded(record_batch_with_metadata);
   }
-
- private:
-  Status CopyArrayData(std::shared_ptr<ArrayData> data) {
-    auto& buffers = data->buffers;
-    for (size_t i = 0; i < buffers.size(); ++i) {
-      auto& buffer = buffers[i];
-      if (!buffer) {
-        continue;
-      }
-      ARROW_ASSIGN_OR_RAISE(buffers[i], Buffer::Copy(buffer, buffer->memory_manager()));
-    }
-    for (auto child_data : data->child_data) {
-      ARROW_RETURN_NOT_OK(CopyArrayData(child_data));
-    }
-    if (data->dictionary) {
-      ARROW_RETURN_NOT_OK(CopyArrayData(data->dictionary));
-    }
-    return Status::OK();
-  }
 };

 struct StreamDecoderWriterHelper : public StreamWriterHelper {

@pitrou I've added all your suggestions in the latest changes


Search.messages API does not return messages from bots/automations

When searching for messages in the UI -- "exclude automation" is a checkbox that allows filtering for messages from bots/automation.
When using the search. messages API, bots/automation messages do not show up. It is not in the documentation how to enable this option (https://api.slack.com/methods/search.messages#markdown)
slack-sdk==3.23.0
Python 3.9.6
ProductName:		macOS
ProductVersion:		14.1
BuildVersion:		23B74
Darwin Kernel Version 23.1.0: Mon Oct  9 21:28:45 PDT 2023; root:xnu-10002.41.9~6/RELEASE_ARM64_T6020
Steps to reproduce:
Search for messages in a channel where bot messages are present, the response will not include bot message:
response = client.search_messages(
            query="in:#channelabc",
            count=100,
            page=1,
        )

Hi @bbchungg thanks for writing in 💯
This seems to be the case the bot messages do not appear in the response using search_messages, if you are trying to find a bot message in a channel you can use client.conversations_history in order to get all the messages in a channel and find what you are looking for.
Let me know if this resolves your issue

Thanks for the response @WilliamBergamin, I just tested the same endpoint search.message with exact same code, and now it is returning bot messages.
I will use the client.conversations_history instead if this provides a more stable response

It looks like the parameter search_exclude_bots controls this behavior.


Jenkins Core: Login Screen div has a limited height

.... and it leads to white rectangles in the bottom.
https://github.com/jenkinsci/jenkins/pull/4763 does not fix it at the moment

Fixed in https://github.com/oleg-nenashev/jenkins/pull/50


Azure Monitor Query: Prepare for July release

Preparing Azure Monitor Query 1.5.0 release

API change check
API changes are not detected in this pull request.


Don't make README examples depend on activesupport

So that users pasting these examples don't get
undefined method `seconds' for 5:Integer

if they're not using activesupport in their apps

😃 👍


Add the pgp signed apk button in our Github Read Me section

Need to add the pgp signed apk button in our Github Read Me section.

Verified this issue.


Power isolation for IEEE 802.3at compliance

I stumbled across a criticism of the ESP32-POE and wanted to submit a project issue for awareness and potential resolution:

No isolation. The IEEE 802.3at spec demands isolation up to 1500 Vrms and the product page of the Olimex ESP32-POE specifically mentions that there is no isolation and that you should not have Ethernet and USB plugged in simultaneously.

Source: Crowd Supply

Yes, I read this, the guy was desperately to justify his high price and I didn't want to spoil his pitch and campain.
Please show me where 802.3at state 1500Vrms insulation is necessary?
Making insulation adds parts to the board, which in most of the cases people would not need.
ESP32-POE works in field connected mostly to sensors or relays etc. There is no need for such insulation in most of the cases.

33.4  -  Additional Electrical Requirements
33.4.1 - Isolation

PDs and PSEs shall provide isolation between all accessible external conductors, including frame ground (if any), and all MDI leads including those not used by the PD or PSE. Any equipment that can
be connected to a PSE or PD through a non-MDI connector that is not isolated from the MDI leads
needs to provide isolation between all accessible external conductors, including frame ground (if any), and the non-MDI connector. Accessible external conductors are specified in subclause 6.2.1b) of IEC60950-1:2001.

This electrical isolation shall withstand at least one of the following electrical strength tests:
a) 1500Vrms at 50Hz to 60Hz for 60s, applied as specified in subclause5.2.2 of IEC60950-1:2001.
b) 2250Vdc for 60s, applied as specified in subclause5.2.2 of IEC60950-1:2001.
c) An impulse test consisting of a 1500V, 10/700μs waveform, applied 10 times, with a 60s interval
between pulses. The shape of the impulses shall be 10/700μs (10μs virtual front time, 700μsvirtual
time of half value), as defined in IEC60950-1:2001 Annex N.

There shall be no insulation breakdown, as defined in subclause5.2.2 of IEC60950-1:2001, during the test. The resistance after the test shall be at least 2MΩ, measured at 500Vdc. Conductive link segments that have differing isolation and grounding requirements shall have those requirements provided by the port-to-port isolation of network interface devices (NID).

Source
Also, I saw your blog post today about the new ESP32-POE-ISO with 3000VDC isolation!

Note that ESP32-POE is neither PD neither PSE and has no MDI.
No one is supposed to touch this board while it's powered, and usually it is mounted in well isolated plastic box somewhere in the field.
If one wants to implement IP phone, router, or other device or want to use ESP32-POE as power supply for other equipment definitely should take measures to not allow people to make physical contact with the board metal parts which is the purpose of this part of the standard and the insulation may not be done necessary INSIDE the board, but with the enclosure where this board is installed.

I see. Based solely on this information, I understand that compliance for this spec is determined at the system level and not necessarily at the level of each individual component. If I'm correct, this would mean that the system (including ESP32-POE) could be compliant with this portion of the specification if isolation is also incorporated within the neighboring components (in an enclosure or otherwise). My interpretation of the snippet above tells me that power isolation is not required without onboard PD/PSE/MDI, which resolves this issue.

ESP32-POE is indeed a PD (Powered device) and has MDI (Medium Dependent Interface, in 100BaseT case: RJ45 and circuitry).
All external connectors and the frame must be isolated from line ethernet cable.
If there are no connectors available in the device and the frame is isolated from the circuits there is no problem.
Otherwise, ESP32-POE is not applicable and ESP32-POE-ISO must be used.


default_auth script not fetching world_address properly

The default_auth.sh script is not being able to fetch world address properly. As you can see it is trying to read that info from manifest.json and that file does not contains that data. Maybe we can fetch it from Scarb.toml
Also I think we should update dojo book to include a hint that user should run this script manually after sozo migrate, that is not being said anywhere and its important to do so (otherwise you get permissions errors that you don't know how to fix).

@kariy (or someone) please let me know what you think, I can take care of this one.

Yes! Please tackle this

I think we can move default auth to the new overlay auth approach cc @lambda-0x

@Jonatan-Chaverri i the command fetching world address from manifest file is working as expected for me, perhaps you ran sozo clean before calling the script?
regarding moving to overlay system for model authorization it will be available from 0.7.0.alpha.1 (currently we are using 0.6.0 in this project) so will open an issue for it

@lambda-0x the issue was that "jq" was not installed in my system. I think this tools does not come with any Unix or linux distributions nor macOS systems. And the script just throw an error indicating that world address was not found. Perhaps adding documentation regarding the tools required will be nice or throwing some more explicit error on the console.
I spend some time trying to figure out why I got 'not writer' error on katana logs before I discover that I needed to manually run this script to grant my address writer access. Then I run into this issue, I just pasted the world address directly in the script and it worked.
But hopefully with the new auth model this will be resolved, so closing the issue. Thanks.


Branding site is currently down

Page URL: https://www.typescriptlang.org/branding
Issue: Site currently returns an error

The resource you are looking for has been removed, had its name changed, or is temporarily unavailable.

Recommended Fix: The site was up 2 days ago when was referencing it for a citation. In the time since then, it appears to have gone down. Looking through commits, I don't see anything that would have broken it.
Browser: Firefox 78.0.2, Safari 13.1.2

You can use staging for now: https://www.staging-typescript.org/branding
You copied the link during the weekend when we've been testing the new website 👍 - we should be shipping mid next week


The test step should not use the same metrics objects as validation

🐛 Bug
https://github.com/PyTorchLightning/lightning-flash/blob/eb1fcd3925ee297d08704d48c5fc57624665ad96/flash/core/model.py#L424

We do a deepcopy of the metrics object here: https://github.com/PyTorchLightning/lightning-flash/blob/eb1fcd3925ee297d08704d48c5fc57624665ad96/flash/core/model.py#L335 - which seems to be sufficient to get the correct results. Simple test for correctness here (although this could be expanded): https://github.com/PyTorchLightning/lightning-flash/blob/eb1fcd3925ee297d08704d48c5fc57624665ad96/tests/core/test_model.py#L345


wh sentences not dealt with at all

Arguably, handling wh sentences (who / what / when / where) is out of scope for a project that aims to discover the propositional content of sentences. Hence this "issue" really just documents the current behavior of the system, which is a bit unusual.
(Generated by  -t -c --dep --oie, -c is my extension that produces the json logical form, it is just a deterministic rewrite of the dependency structure produced by props.)

Who:(prop_of:he )

We indeed left these constructions out of scope, and it's interesting to see what the output for these end up looking like.
I suspect that this is due to the dependency mark relation appearing in both conditionals and wh sentences.


chore(deps): upgrade configuration

Upgrades project dependencies. See details in workflow run.

Automatically created by projen via the "upgrade-configuration-k8s-27-main" workflow

⚪ Backport skipped
The pull request was not backported as there were no branches to backport to. If this is a mistake, please apply the desired version labels or run the backport tool manually.
Manual backport
To create the backport manually run:
backport --pr 3987

Questions ?
Please refer to the Backport tool documentation


Fixed number of selectable rows ?

I am trying to make it so the user can only select a max number of 25 rows.
isRowSelectable: (dataIndex, selectedRows) => {
      return selectedRows.data.length < 25;
},

This does not let a row be selected after there are 25 but I cannot unselect a row. I looked at the selected-rows example but cannot get something to work for me. Thanks

Below is a codesandbox of it working with 25 rows:
https://codesandbox.io/s/muidatatables-custom-toolbar-ps9co?file=/index.js


Next.js guide improvement

I found the Next.js setup guide difficult to understand.

Clarifies several key steps (e.g., App Router vs. Pages Router)
Removes a few sections irrelevant to this guide or unnecessary in general
Improves grammar
Improves formatting

Also fixes a spelling mistake in the Input colors list.

@acdvs thanks for contributing to the project, I check the changes they're really good and I appreciate your work just fix the two missing part and I'll merge that for the next update.

@sajadevo Done!


ndt7: the server should give you the four tuple

Suggested by @mattmathis. This probably means the server should tell the client what it thinks the client IP address is. This can be done with a specific protocol message.

Specifically the jason shown in the "advanced" tab for :3010/static/widget.html should show the connection 4 tuple in parsible form.   It should also appear in the meta report used to generate the "details" tab.

@mattmathis how about:
{
  "server": {
    "address": "<IP_ADDRESS>",
    "port": 1234
  },
  "client": {
    "address": "<IP_ADDRESS>",
    "port": 1234
  }
}

?

Also, a UUID would be nice.

This has clearly been done in #126


Ramp volume on Wake Up

When scheduling a wakeup I'd like to be able to set a target volume, the service should then ramp up the volume from zero over a set time to meet the target volume.
It can be assumed the ramp time can be configured as part of the config.js file as I think it is unlikely different ramp periods would be required for different devices.

I've been thinking about this and I'd rather not have a REST call which sets a Node timer. The problem with this is server would have to maintain a state in memory.
Another thing to consider is if the volume is manually adjusted during the ramping time period.
How about if the volume could be scheduled in much the same was as the sleep state can be now? This way at a specified time you could start a playlist with a specified volume of say 15; then another schedule would just ensure the volume was 25; and a third to ensure the volume was 35?

Seems mighty nice, but what about keeping state of server in a file (either /var/lib/ or some user provided like ~/.upnp-ps). This way we may have a volume gradient (eg. start at volume 0/5/10/whatever and raise 1 point until volume 50 during an hour). If a server got killed during this gradiental progress it may continue after reading the state file.
On the other hand: how likely it is the server would be killed during wakeup?

I will add support for this.
I'll add a POST to request a timer with a number of seconds and target volume. This will respond with a location resource which can be used to DELETE the volume changes or view how they are progressing. I'll configure so it requests the volume from the DS before each change and if the DS volume has been altered from the expected volume level, the ramping will be cancelled.
The API already has a sleep timer which is implemented in a near similar fashion.


Port over Dataset Connector Configuration to system portal

Description
This entails converting the dataset configuration tab into a form field and integrating into the connector configuration form.
Acceptance criteria

Only shows up for database and saas connectors
yaml editor is readonly for saas connectors
yaml editor is only editable for database connectors on creation


Entering a Hungarian phone number breaks formatter

Hi! First of all, many thanks for this amazing component! I've noticed a bug when I was trying to enter a Hungarian phone number.
For example: +36 30 123 4567
When I set the country select to Hungarian, and type in the rest:
301234567
It turns into: (30) 123 7456.
This bug exists on the demo site as well.
Many thanks for your help, and keep up the good work! :)
Regards,
Levi

So that's the bug then

So what's the bug then?

Hi @halt-hammerzeit, please check the order of the last 4 digits. They are mixed.

I see now

Fixed via https://github.com/halt-hammerzeit/libphonenumber-js/commit/a80b3ee8eadc6a55009a05a70f95812d5116b2f8
Reinstall libphonenumber-js dependency


Does Chroma shader variant scale also LUMA?

Does one have to use both non chroma and chroma variants to scale both luma and chroma aka:
glsl-shader="~~/shaders/ArtCNN_C4F16.glsl"
glsl-shader="~~/shaders/ArtCNN_C4F16_Chroma.glsl"

or does the Chroma version scale both LUMA and CHROMA?

Use the YCbCr variants if you want to scale both luma and chroma, just remember to set cscale=bilinear.


Engineering Fundamentals Metrics

Story for feature agera-edc/DataSpaceConnector#13
Description
As part of our success criteria for the engagement we want to contribute to the establishment and adoption of engineering best practices by the EDC community. To measure improvements, we need to collect metrics for the key areas of interest and visualize how these metrics change over time.
Acceptance Criteria

[x] Metrics to be collected and reported on are defined
[x] A first report on initial metrics is available
[ ] Follow-up stories to add additional metrics (which might depend on other stories and might not be available yet) are created.

Metrics in target for collection include the following (at this time):

[x] Code Coverage
[x] PR Age
[x] Frequency of PRs
[ ] Count of Rejected PRs
[x] Cyclomatic Complexity
[ ] Linting Errors
[x] Total # of ADRs

Note that in order to complete this story, the dependent items need to be completed:
agera-edc/DataSpaceConnector#42
agera-edc/DataSpaceConnector#56
agera-edc/DataSpaceConnector#34

Current state of the power bi report has been checked into our internal Azure-DevOps PR
Note that at this stage, CodeCov access is only available (for my account) in our internal Repo.  This is not an issue at this time as the CodeCov reports should be generated for the main EDC repo as well.
I have requested access to the EDC repo from my CodeCov account.
A few points to mention:

We do have metrics for the following in CodeCov reports:
-- Code Coverage
-- Cyclomatic Complexity
Instead of imbedding these metrics in the PBI report; a dashboard should be made that displays the PBI report sections and has the CodeCov reports present (note that it is not possible to include the codecov specific graphs/tables in the PBI in a meaningful way).
Follow up stories for the Linting and new Dashboard will need to be created
Rejected PR's may not be possible given the information that is provided from the API; it is my belief that with the PR insights we have in the report, we have enough meaningful information.

All data we wanted is accumulated. closing this out and next one will be created for follow up work.


Warning in MPI plugin

When compiling master, I get the following warning:
included from /home/jbigot/data/projects/pdi/pdi/plugins/mpi/mpi.cxx:37:
/home/jbigot/data/projects/pdi/pdi/plugins/mpi/mpi_comm_transtyper.h: In member function ‘PDI::Ref {anonymous}::MPI_Comm_transtyper::create_transtyped_ref(PDI::Ref, const PDI::Datatype&, const PDI::Datatype&)’:
/home/jbigot/data/projects/pdi/pdi/plugins/mpi/mpi_comm_transtyper.h:140:5: warning: control reaches end of non-void function [-Wreturn-type]
     }

@tpaluszk could you look into it.

closed via merge request !197

In GitLab by @tpaluszk on Mar 28, 2019, 10:55
@jbigot I couldn't reproduce the warning nor see any warnings on Jenkins. Could you check if this (!197 ) fixes the warning you were getting?


[OPPRO-313] Support sparksql xxhash64

move to https://github.com/facebookincubator/velox/pull/3235/commits


Started working on a time entry override system that will allow users to request current pay period validated entries to be unlocked. An administrator can also unlock previous pay period entries based on a span of time.

Adjusted this functionality to only allow a single date to be unlocked by admin accounts.


refactor: cleanup kratos router method into testable pieces

This is great

@bodymindarts since last approval I:

rebased to bring in phoneMetadata changes from #2997
renamed existing PhoneMetadataValidator to PhoneMetadataChecker (https://github.com/GaloyMoney/galoy/pull/3102/commits/be93cae2b4878438c5b95b795324a8194b1cba8e)
introduced an actual PhoneMetadataValidator to cast incoming values to our domain type (https://github.com/GaloyMoney/galoy/pull/3102/commits/2898e90dcd762e0e14a9efc9decf7614fe0b4009)

This was a significant force-push to resolve merge conflicts introduced from authorization work since this PR was opened


Memory  and disc usage

Hi. I want to get memory and disk usage while running pagerenk aplication, so I wonder to do some manipulations using the code that you proposed.
The problem that i have a prebuilt installation of spark and i don t have core folder inside. only bin, conf, sbin, data, jars .... folders
Can you please tell me how can I put or extend classes inside my spark installation?
How can i get storage memory and execution memory measures even after the execution finished?
Thank you
Please review http://spark.apache.org/contributing.html before opening a pull request.

Can one of the admins verify this patch?

@assia6 please close this; not clear what the pull request is doing. Questions belong on the mailing list.

Sorry,
Done.
2017-12-27 16:06 GMT+01:00 Sean Owen<EMAIL_ADDRESS>
@assia6 https://github.com/assia6 please close this; not clear what the
pull request is doing. Questions belong on the mailing list.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/apache/spark/pull/20092#issuecomment-354126480, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AIfS3FtOEDhhKf97vCEVHBLSnrOQmmacks5tElzygaJpZM4RNin2
.

--
Mme. Assia YDROUDJ
MAB - Dept MI*, Faculté des Sciences, *Alger 1
Tel : +213 662 086 889.


[Spark] Skip reading log entries beyond endOffset, if specified while getting file changes for CDC in streaming queries

Which Delta project/connector is this regarding?

[x] Spark
[ ] Standalone
[ ] Flink
[ ] Kernel
[ ] Other (fill in here)

Description
Skip reading log entries beyond endOffset, if specified while getting file changes for CDC in streaming queries
How was this patch tested?
Added unit tests
Also verified using logs to ensure that additional Delta logs are not read

24/05/16 01:21:01 INFO StateStore: StateStore stopped
Run completed in 54 seconds, 237 milliseconds.
Total number of tests run: 1
Suites: completed 1, aborted 0
Tests: succeeded 1, failed 0, canceled 0, ignored 0, pending 0
All tests passed.

Before:
10457:24/05/16 01:38:37 INFO DeltaSource: [queryId = 199ce] [batchId = 0] Getting CDC dataFrame for delta_log_path=file:/tmp/spark-c3309e79-80cf-4819-8b03-2fc607cc2679/_delta_log with startVersion=0, startIndex=-100, isInitialSnapshot=false, endOffset={"sourceVersion":1,"reservoirId":"75194ee3-4ff6-431e-8e7c-32006684d5ad","reservoirVersion":1,"index":-1,"isStartingVersion":false} took timeMs=52 ms
11114:24/05/16 01:38:39 INFO DeltaSource: [queryId = 199ce] [batchId = 1] Getting CDC dataFrame for delta_log_path=file:/tmp/spark-c3309e79-80cf-4819-8b03-2fc607cc2679/_delta_log with startVersion=1, startIndex=-100, isInitialSnapshot=false, endOffset={"sourceVersion":1,"reservoirId":"75194ee3-4ff6-431e-8e7c-32006684d5ad","reservoirVersion":2,"index":-1,"isStartingVersion":false} took timeMs=25 ms
11518:24/05/16 01:38:39 INFO DeltaSource: [queryId = 199ce] [batchId = 2] Getting CDC dataFrame for delta_log_path=file:/tmp/spark-c3309e79-80cf-4819-8b03-2fc607cc2679/_delta_log with startVersion=2, startIndex=-100, isInitialSnapshot=false, endOffset={"sourceVersion":1,"reservoirId":"75194ee3-4ff6-431e-8e7c-32006684d5ad","reservoirVersion":3,"index":-1,"isStartingVersion":false} took timeMs=24 ms

After:
10498:24/05/16 01:32:10 INFO DeltaSource: [queryId = ede3f] [batchId = 0] Getting CDC dataFrame for delta_log_path=file:/tmp/spark-270c3d6e-40df-4e6f-b1da-c293af5d6741/_delta_log with startVersion=0, startIndex=-100, isInitialSnapshot=false, endOffset={"sourceVersion":1,"reservoirId":"516bafe0-e0ea-4380-afcb-44e416302a07","reservoirVersion":1,"index":-1,"isStartingVersion":false} took timeMs=39 ms
11155:24/05/16 01:32:11 INFO DeltaSource: [queryId = ede3f] [batchId = 1] Getting CDC dataFrame for delta_log_path=file:/tmp/spark-270c3d6e-40df-4e6f-b1da-c293af5d6741/_delta_log with startVersion=1, startIndex=-100, isInitialSnapshot=false, endOffset={"sourceVersion":1,"reservoirId":"516bafe0-e0ea-4380-afcb-44e416302a07","reservoirVersion":2,"index":-1,"isStartingVersion":false} took timeMs=14 ms
11579:24/05/16 01:32:12 INFO DeltaSource: [queryId = ede3f] [batchId = 2] Getting CDC dataFrame for delta_log_path=file:/tmp/spark-270c3d6e-40df-4e6f-b1da-c293af5d6741/_delta_log with startVersion=2, startIndex=-100, isInitialSnapshot=false, endOffset={"sourceVersion":1,"reservoirId":"516bafe0-e0ea-4380-afcb-44e416302a07","reservoirVersion":3,"index":-1,"isStartingVersion":false} took timeMs=13 ms

Difference is even more if we are processing/reading through large number of backlog versions.
In Cx setup, before the change - batches are taking > 300s. After the change, batches complete is < 15s.
Does this PR introduce any user-facing changes?
No

Don't think test failure is related. Happening on other PRs too - https://github.com/delta-io/delta/actions/runs/9122276234/job/25082822738?pr=3112


React-group-project: My profile setup

In this PR

I added a component 'MyProfile'
I modified App.js to add a route to MyProfile component
I modified Header.js to implement active links

STATUS: APPROVED 🎉🎉🎉
Hello @jlvFlores !
The component MyProfile is done.  There is nothing else to say other than... it's time to merge it!

Highlights
Correct linters ✅
Great use of gitflow ✅
Good code design and implementation ✅
Required Changes ♻
None
Optional suggestions
Every comment with the [OPTIONAL] prefix is not crucial enough to stop the approval of this PR. However, I strongly recommend you to take them into account as they can make your code better.
You can also consider:
N/A
Cheers and Happy coding!👏


Shutdown with running tasks doesn't create Error streams as expected.

I shutdown a Stroom with running tasks, no error streams were recorded, but the log is full of
stroom.data.store.impl.fs.FsTarget - getOutputStream() - null
it is possible the tasks were not marked as complete, and reprocessed on startup - this needs to be investigated

Ran a test, it appears to mark the jobs as complete along with a Terminated Error Stream, n=but there are no meta attributes signifying a FATAL error

am still unsure as to what the original error relates to


the builder.py and the server.py and the world.py giving error

in world.py - Traceback (most recent call last):
File "C:\Users\HP\Desktop\my projects\Craft-master\world.py", line 7, in
dll = CDLL('./world')
File "C:\Users\HP\AppData\Local\Programs\Python\Python39\lib\ctypes_init_.py", line 374, in init
self._handle = _dlopen(self._name, mode)
FileNotFoundError: Could not find module 'C:\Users\HP\Desktop\my projects\Craft-master\world' (or one of its dependencies). Try using the full path with constructor syntax.
in builder.py- Traceback (most recent call last):
File "C:\Users\HP\Desktop\my projects\Craft-master\builder.py", line 248, in
main()
File "C:\Users\HP\Desktop\my projects\Craft-master\builder.py", line 189, in main
client = get_client()
File "C:\Users\HP\Desktop\my projects\Craft-master\builder.py", line 185, in get_client
client = Client(host, int(port))
File "C:\Users\HP\Desktop\my projects\Craft-master\builder.py", line 145, in init
self.conn.connect((host, port))
ConnectionRefusedError: [WinError 10061] No connection could be made because the target machine actively refused it
in server.py - giving error of print statement like invalid syntax
Please fix them as i wanted to play this game asap

looks like an error with the server not having the correct dependencies (or client).


Release 2.0 - Getting Start

Translate release-2.0: Getting Started
Translate release-2.0: Getting Started » Prerequisites
Translate release-2.0: Getting Started » Install Samples, Binaries

#554 release-2.0: Getting Started
#553 release-2.0: Getting Started » Prerequisites
#552 release-2.0: Getting Started » Install Samples, Binaries and Docker Images
#550 release-2.0: Developing Applications
#549 release-2.0: Developing Applications » The scenario
#548 release-2.0: Developing Applications » Analysis
#547 release-2.0: Developing Applications » Process and Data Design
#545 release-2.0: Developing Applications » Application
#544 release-2.0: Developing Applications » Application design elements
#542 release-2.0: Tutorials » Writing Your First Application


Should not delete namespace when unjoin cluster

What would you like to be added:
UnjoinCluster in pkg/kubefedctl should not delete the kubefed namespace.
Why is this needed:
Because maybe there are other resources in this namespace, which can not and should not be deleted.
This will leave a Terminating namespace, and will cause a failure when joining this cluster again.
Because it's not allowed to create any resource (include the RBAC resources) in a Terminating namespace.
We cann't stop user to use the kubefed namespace to store other resources. So it' better to keep the namespace left, like what we do on the Primary cluster.

/kind feature

@davidwtf I don't think it is a good and recommended practice to use the kubefed namespace to federated resources. I'd recommend to use a different namespace that you can after federate to the clusters. If you don't want to get the resource deleted when unjoining you could also make usage of an annotation kubefed.io/orphan: true. This annotation ensures retention of the resource (e.g.. namespace) when unjoining.

@hectorj2f Thanks for your suggestion.
But I think the main point is not which namespace to save the federated resources, but is that we can not stop the user to save something in the kubefed namespace.
The user may save just normal resources. And maybe there are other operators will create their CR in the kubefed namespace.
If we delete the namespace, we will delete the resources that not create by us. And we don't know what will happen, the deleting may be blocked.

To be clear,  the namespace which I mentioned, is the not the user defined federated namespace, but the namespace used by kubefed's control plane .

/remove-lifecycle stale


Other Chromium builds

Hi, can you add to your extension the possibility to check for updates also for other Chromium build?
With other Chromium build I mean, for example:

Hibbiki (https://github.com/Hibbiki/chromium-win64);
Marmaduke (https://github.com/macchrome/winchrome)

Hibbiki makes Chromium builds only for Windows (x86 and X86_64) while Marmaduke makes builds for Windows, macOS and Linux.
Hibbiki builds comes with defined Google API keys so Google services work.
Marmaduke builds are based on the "ungoogled-chromium" project of Eloston.
This two examples are really handy because Chromium is compiled with the enabled Widevine support., so Chromium will be able to play DRM content (on Netflix, for example).
Chromium is also compiled with open-source audio/video codecs + AAC + H.264 + H.265.
The "ungoogled-chromium-windows" version (https://github.com/ungoogled-software/ungoogled-chromium-windows) in fact is not compiled with Widevine support or at least this plugin doesn't work.
With Marmaduke builds I have no issue.
You can find other infos here: https://chromium.woolyss.com/
Thank you for your work.
Davide

Hey Dave,
I'll take a look at this once I find some time. The main issue here would be knowing which releases in each repository to grab (e.g. which file is the actual build, are they consistent in naming) and parsing the actual release version from the release details.
With that said, if you know how to do this yourself and wouldn't mind contributing, feel free to PR these changes! The relevant file is https://github.com/claudiodekker/chromium-update-notifier/blob/master/public/repositories.js
Thanks!


Do not use 'sf::err' in examples

sf::err is an implementation detail, SFML applications (and examples) should use std::cerr

SFMLBuildMaster: Build this please.

I disagree about it being an implementation detail but think this is a good change regardless.

Users should definitely not be allowed to stream into sf::err. They should be able to redirect it, and that's it.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall first build on feature/dont_use_err_in_examples at 51.729%

Totals

Change from base Build<PHONE_NUMBER>:
51.7%

Covered Lines:
10476

Relevant Lines:
19032

💛  - Coveralls


Add variant=release to Travis CI builds of tests

This aims to confirm there are no issues depending on build configuration (related to #46 and #49).
References
#51

BTW, variant=debug,release is intentional, it first builds tests with variant=debug, then variant=release.

The channel test fails whenever I compile the "channel.cpp" file with -O3. I'm looking into it now...

...in the test_channel_convert() function, a call to channel_convert<> results in wrong values. This could indeed be a manifestation of the same issue as in https://github.com/boostorg/gil/issues/49.

@stefanseefeld Can you make a minimal code sample?

Yes, and I made an interesting observation:
I narrowed the error down to a call to  do_test<reference_core<bits32&> >().test_all().
As the next step I "unwrapped" that function, replacing it with
   do_test<reference_core<bits32&> >().test_channel_invert();
   do_test<reference_core<bits32&> >().test_channel_convert();
   do_test<reference_core<bits32&> >().test_channel_multiply();
   do_test<reference_core<bits32&> >().test_channel_math();

which made the error disappear ! Notice, however, that this isn't strictly equivalent. In the original case above the test_all() call reuses the do_test object for the four test functions, while in my "unwrapped" case I construct new temporary do_test objects for each of those functions.
Thus suggests that the problem is that the object's state gets altered in a way to make a subsequent test function call fail.
@chhenning does this ring a bell ? Can you think of any possible reason for that behaviour, which is also specific to this using channel references...

(You may just drop the above code right into main() to reproduce the problem. Don't wrap it in a try block, so a failure will cause an "unexpected" exception, allowing you to inspect the core dump...)

@chhenning , looking into the channel.hpp file, I notice quite a few classes (packed_channel_reference_base and all its subclasses) having modifiable state, yet all member functions being declared const. What's up with that ? Can you explain the meaning of const there ?

I guess, this can be confirmed as a bug

Ok. I have set up visual studio code on ubuntu and with boost gil master the channel.cpp test runs through. I'm using gcc 5.4.something
This would imply that gil develop different gil core which is weird.

@chhenning

boost gil master the channel.cpp test runs through. I'm using gcc 5.4.something

What compilation flags exactly?

Yeah, I was just testing debug configuration.

On gil develop I can see an exception with release and release_with_debug_symbols. But no exception with debug config.

@chhenning That seems to confirm the issue.
To summary, it occurs only for optimised builds only.

Linux+GCC, #51, https://travis-ci.org/boostorg/gil/jobs/355009262
Linux+clang,

Question: does it occur for optimised builds for both, 32bit and 64bit targets or olny for 64bit, as it interestingly does in case of the checksum bug, #49, https://ci.appveyor.com/project/stefanseefeld/gil/build/1.0.182-develop

It would be useful to pay close attention to the compiler warnings. (Disable those about unused local typedefs to reduce the noise.) There are a few from channel.hpp about using uninitialized memory. I didn't quite understand that warning, it looked bogus. But then, it may hint at the problem.
(Inserting print statements to print out the max and min values in the test makes the failure disappear, so I'm pretty sure this has to do with illegally aliased data that the optimization pass may actually elide, or some such. I haven't looked at clangs warnings yet.

@stefanseefeld @chhenning It may be a good time to start shooting down the warnings.
To avoid chasing our own and each others tails, we rather get somewhat systematic about it.
Let's agree on some plan:

Create fix-warnings shared branch in the boostorg/gil
Temporarily disable the failing tests
Compile using clang, gcc, msvc (/W3 level but perhaps /W4 too)
Pick warning, fix it, commit
Repeat 2-3 until we are are warnings-free and the builds are green
Re-enable failing tests and see what happens.
If this does not help, we run static analysis and repeat the clean-up cycles.

Comments?

Here is my minimal reproducible code
#include <iostream>
#include <boost/gil/gil_all.hpp>

using namespace boost::gil;
using namespace std;

void error_if(bool condition) {
    if (condition)
        throw std::exception();
}

bits32s c32s_min = channel_traits<bits32s>::min_value();
bits32s c32s_max = channel_traits<bits32s>::max_value();

// For channel values simply initialize the value directly
template <typename ChannelValue>
struct value_core {
    typedef ChannelValue channel_t;
    channel_t _min_v, _max_v;

    value_core() : _min_v(channel_traits<ChannelValue>::min_value()), _max_v(channel_traits<ChannelValue>::max_value())
    {}
};

int main(int argc, char *argv[])
{
    value_core<bits32s> a;

    bits32s v_min, v_max;

    v_min = channel_convert<bits32s>(c32s_min);
    v_max = channel_convert<bits32s>(c32s_max);

    //std::cout << v_min << std::endl;
    // std::cout << this->_min_v << std::endl;
    //std::cout << v_max << std::endl;
    // std::cout << this->_max_v << std::endl;

    error_if(v_min != a._min_v || v_max != a._max_v);
}

Funny enough, when enabling the cout's. All is good.

To expedite the issue I sent an email to boost mailing list.

I've read the post on ML, I'd insist we do need better coverage of compilers and configs on CI builds, plus static analysis. Sorry, we can't save energy there, unless we have too much time.

I have never argued against better coverage. I'v been arguing against redundancy (building the same variants on multiple CI systems, for example, or building unnecessarily often).

I'm sorry if I misunderstood. I'm now on street. I'll be back to this later tonight.

@mloskot , following a suggestion from the Boost ML, I tried out this patch:
--- a/include/boost/gil/channel_algorithm.hpp
+++ b/include/boost/gil/channel_algorithm.hpp
@@ -329,7 +329,7 @@ template <> struct channel_convert_to_unsigned<bits16s> : public std::unary_func

 template <> struct channel_convert_to_unsigned<bits32s> : public std::unary_function<bits32s,bits32> {
     typedef bits32 type;
-    type operator()(bits32s x) const { return static_cast<bits32>(x+(1<<31)); }
+    type operator()(bits32s x) const { return static_cast<bits32>(x)+(1<<31); }
 };

which works for me. Can you try that in your branch (i.e., this PR) ?

@stefanseefeld I've just updated the PR with the extra commit.

I've reverted 9d9fc09a8ffb39667bc27625285d2d8337ba4034 that temporarily disabled the failing checksum test cases and updated this PR to see if the UB fix also fixes the checksum bug #49

I've updated the build jobs layout adding multiple compilers: GCC 5, 6, 7 and clang 3.9 X variant=release,debug. I defined variant=release as allowed to failure builds for now, until we solve the checksum/channel bugs.


Update versions in docs to remove explicit versions

Throughout our docs we provide many explicit versions for libraries. It's nearly impossible to ensure they're all up-to-date given GitBooks limitations. We should update the docs to use LATEST or latest.release throughout.
Here's an example of this: https://github.com/moderneinc/rewrite-recipe-starter/blob/3ade0712960bd4a31641e85b97653a75a9025354/build.gradle.kts

This is no longer needed now that we're moving to Docusaurus. Closing.


fixed issue with clusterType not being passed in through CLI

What
This fixes an issue where the cluster type was not being passed correctly when setting the cluster type through an ENV var (ie running via CLI and jet)

:+1:


Execution word boundaries should be different from movement word boundaries

The word boundaries used for executing a text selection shouldn't be the same as the movement commands. The movement command word boundaries should be the same as in vi, but for the sake of executing a word it should be a little looser about what it considers a boundary (for instance, . and / are often part of a filename or path, so they shouldn't be considered separators when middle clicking or hitting enter.)

Commands are now only deliminated by whitespace, and movement words by various other characters. (If the characters don't match up with vi, it should be added to issue #1)


Getting Build time error  on doing a npm install

Getting error when i try running on archlinux . error snippet below
make: Leaving directory '/home/rajesh/rasa/rasa-voice-interface/node_modules/node-sass/build'
gyp ERR! build error
gyp ERR! stack Error: make failed with exit code: 2
gyp ERR! stack     at ChildProcess.onExit (/home/rajesh/rasa/rasa-voice-interface/node_modules/node-gyp/lib/build.js:262:23)
gyp ERR! stack     at ChildProcess.emit (events.js:210:5)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:272:12)
gyp ERR! System Linux 5.3.4-arch1-1-ARCH
gyp ERR! command "/usr/bin/node" "/home/rajesh/rasa/rasa-voice-interface/node_modules/node-gyp/bin/node-gyp.js" "rebuild" "--verbose" "--libsass_ext=" "--libsass_cflags=" "--libsass_ldflags=" "--libsass_library="
gyp ERR! cwd /home/rajesh/rasa/rasa-voice-interface/node_modules/node-sass
gyp ERR! node -v v12.11.1
gyp ERR! node-gyp -v v3.8.0
gyp ERR! not ok
Build failed with error code: 1
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none is installed. You must install peer dependencies yourself.
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none is installed. You must install peer dependencies yourself.
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none is installed. You must install peer dependencies yourself.
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none is installed. You must install peer dependencies yourself.
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none is installed. You must install peer dependencies yourself.
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>|| ^4.0.0 but none is installed. You must install peer dependencies yourself.
npm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(node_modules/vue-native-websocket/node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for<EMAIL_ADDRESS>wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for<EMAIL_ADDRESS>wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR<EMAIL_ADDRESS>postinstall: node scripts/build.js
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>postinstall script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

Fixed on latest master

Is this already released? If no when should it be released?
I have these versions:
rasa==1.4.3
rasa-sdk==1.4.0
rasa-x==0.22.2
But I still get the error after running 'npm install'
gyp ERR! UNCAUGHT EXCEPTION gyp ERR! stack Error: spawn C:\Program Files (x86)\Microsoft Visual Studio\2019\BuildTools\MSBuild\15.0\Bin\MSBuild.exe ENOENT gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:264:19) gyp ERR! stack     at onErrorNT (internal/child_process.js:456:16) gyp ERR! stack     at processTicksAndRejections (internal/process/task_queues.js:80:21) gyp ERR! System Windows_NT 10.0.17134 gyp ERR! command "C:\\Program Files\\nodejs\\node.exe" "C:\\Users\\z003xpuw\\Documents\\wirtschaftsprojekt-chatbot\\rasa-voice-interface\\node_modules\\node-gyp\\bin\\node-gyp.js" "rebuild" "--verbose" "--libsass_ext=" "--libsass_cflags=" "--libsass_ldflags=" "--libsass_library=" gyp ERR! cwd C:\Users\z003xpuw\Documents\wirtschaftsprojekt-chatbot\rasa-voice-interface\node_modules\node-sass gyp ERR! node -v v12.13.0 gyp ERR! node-gyp -v v3.8.0 gyp ERR! This is a bug in node-gyp`.
gyp ERR! Try to update node-gyp and file an Issue if it does not help:
gyp ERR!     https://github.com/nodejs/node-gyp/issues
Build failed with error code: 7
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none is installed. You must install peer dependencies yourself.
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none is installed. You must install peer dependencies yourself.
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none is installed. You must install peer dependencies yourself.
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none is installed. You must install peer dependencies yourself.
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none is installed. You must install peer dependencies yourself.
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>|| ^4.0.0 but none is installed. You must install peer dependencies yourself.
npm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(node_modules\vue-native-websocket\node_modules\fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for<EMAIL_ADDRESS>wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(node_modules\fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for<EMAIL_ADDRESS>wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"})
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR<EMAIL_ADDRESS>postinstall: node scripts/build.js
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>postinstall script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR!      C:\Users\z003xpuw\AppData\Roaming\npm-cache_logs\2019-11-11T13_35_26_913Z-debug.log`


Issue with rendering the content text for tooltip-icon

Tooltip issue:
I am using tooltip icon and assigning the content. The tooltip display doesn't wrap the text and overflows the tooltip box. Any suggestions on how to overcome this. I am using carbon-components-angular latest version.
Detailed description

Describe in detail the issue you're having.

We are using carbon component tooltip on content switcher buttons.
We have overridden the css of the contentswitcher component to display the overflow for each button.
The tooltip is displayed but the content inside the tooltip is not wrapping.
I have tested this on carbon design system with knobs and found the same issue for tooltip icon component

The actual issue I see on our application is as below

Is this a feature request (new component, new icon), a bug, or a general issue?
This seems to be a bug

Is this issue related to a specific component?
Tooltip-icon component

What did you expect to happen? What happened instead? What would you like to see changed?
The content text of tooltip-icon should wrap inside the tootip box

What browser are you working in?
Firefox, Chrome

What version of the Carbon Design System are you using?
"carbon-components-angular": "3.15.1"
"carbon-components": "10.4.1",
"@carbon/icons-angular": "10.4.0",
"@carbon/themes": "10.5.0"

Steps to reproduce the issue
This sandbox looks like react. I am having issue in angular.
You can reproduce in https://angular.carbondesignsystem.com/?path=/story/tooltip-icon--basic
Step 1: Goto Knobs tab
Step 2: Add the text Filter Filter Filter Filter Filter Filter Filter Filter Filter Filter Filter Filter Filter Filter Filter Filter Filter Filter Filter Filter Filter Filter

It might be better to use the tooltip definition: https://angular.carbondesignsystem.com/?path=/story/tooltip-definition--basic as the content inside the tooltip will be wrapped in your application. However if you really wanted to use the tooltip icon you can overwrite the max-width styling.


Provide ConcurrentLru factory

This consolidates the duplicate creation logic between AsyncConcurrentLruBuilder and ConcurrentLruBuilder, and provides a smaller code size for AOT compilation (builder classes have a huge footprint).
What should this be called? Is it bad to have Create and CreateAsync?

coverage: 98.585% (-0.08%) from 98.665%
when pulling dfab04d37c0af3441842d11047cd9b0c91439a0f on users/alexpeck/lrufactory
into b8eae1f4b2a958ae72eccdc17bde7cf47d21586d on main.


Java Emitter should work correctly with no tspconfig file

tspconfig is an optional file, it shouldn't be necessary.
This is the required scenario for un-branded
Please ensure the following steps would not crash the emitter and generate the right SDK:
tsp init # Chose generic restapi
tsp install
npm install @typespec/http-client-java
tsp compile . --emit @typespec/http-client-java

tested and current version already does this without tspconfig


Update support docs to java11 and min version 64

Description
Update documentation to reflect that we now use java11 and that the minimum RN version has changed to 0.64

retest this please

retest this please

retest this please

retest this please

retest this please

@jonathanmos please revisit and merge when green


Add additional way to exclude code parts using annotations

This issue will implement a new mechanism to exclude specific classes or (this
is new!) specific methods or parts of methods from being checked with
ForbiddenAPIs.

The idea here is to use an annotation, that must have at least
RetentionPolicy.CLASS or RetentionPolicy.RUNTIME. ForbiddenAPIs will not
provide such an annotation, it can simply configured to look for any annotation
type(s), configured as a list of Class parameters.

This allows to run forbidden-apis with ant like:

<forbiddenapis supressAnnotations="org.foo.bar.SuppressForbidden" .../>

(same in maven as a list of class properties).

You have to define the custom annotation (or multiples) as part of your own
project, so we get no external dependencies. You can also misuse another
annotation (LOL). The annotation must just be of RetentionPolicy.CLASS or
RetentionPolicy.RUNTIME. It does not need to be documented. Just SOURCE-only
annotations won't work (because no longer visible in class files).

You can then annotate classes with this annotation (which does the same like
excluding the class file using the excludes="...." Ant/Maven config settings)
or go down to methods or code lines. In fact depending on the type of your
annotation, you can use it like SuppressWarnings. So annotate any method, code
line, or parameter [not yet decided if this makes sense] you want t exclude
from checking (or in Java 8 also types).

Forbidden-APIs will add an "example/default annotation" in its own JAR file,
but you are not required to use it (especially if you don't want to have a
compile-time dependency to forbiddenapis).

Original issue reported on code.google.com by uwe.h.schindler on 14 Sep 2014 at 5:08

I added support for a default (shipped-with) annotation in afce07908af024f73d022588b57d6feb85ad8523

This should work now for Ant, Maven, CLI. Documentation was also updated.


Is build necessary for e2eTest

I am not sure that the build step is completely necessary, and at least in my scenario, it is redundant for the e2eTest task.  e2e requires that dev or something similar has already been run to start up the server, and in that case it is watching/compiling. On running the e2e task another build is done without any files actually changing.

Good call. Should be removed from the task list.

3a196b954f94f86d9abe675b30f771a8a08de840 done


VMs fail to launch with Insufficient devices.kubevirt.io/tun

Is this a BUG REPORT or FEATURE REQUEST?:

/kind bug
What happened:
try to launch a vm on 0.7.0 . the related pod stays in pending mode, with the following message
Warning  FailedScheduling  5s (x6 over 20s)  default-scheduler  0/1 nodes are available: 1 Insufficient devices.kubevirt.io/tun.
What you expected to happen:
vm launches
How to reproduce it (as minimally and precisely as possible):
deploy 0.7.0 with a configmap to useEmulation
create a vm
cry
Anything else we need to know?:
Environment:

KubeVirt version (use virtctl version):
Client Version: version.Info{GitVersion:"v0.7.0", GitCommit:"b5b91243f540739eb5db61af89b2f1e5ba449dfa", GitTreeState:"clean", BuildDate:"2018-07-04T14:16:40Z", GoVersion:"go1.10", Compiler:"gc", Platform:"linux/amd64"}
Server Version: &version.Info{GitVersion:"v0.7.0", GitCommit:"b5b91243f540739eb5db61af89b2f1e5ba449dfa", GitTreeState:"clean", BuildDate:"2018-07-04T14:16:40Z", GoVersion:"go1.10", Compiler:"gc", Platform:"linux/amd64"}

Kubernetes version (use kubectl version):
oc v3.10.0-rc.0+c20e215
kubernetes v1.10.0+b81c8f8
features: Basic-Auth GSSAPI Kerberos SPNEGO
Server https://kubevirt:8443
openshift v3.10.0-rc.0+e132a20-38
kubernetes v1.10.0+b81c8f8

VM or VMI specifications:

Cloud provider or hardware configuration:

OS (e.g. from /etc/os-release):

Kernel (e.g. uname -a):

Install tools:

Others:

<fabiand> mkletzan, I think the issue is that there is a loop which performs checks
<fabiand> the checks are based on the presence of a path
<fabiand> and this check is blocking
<fabiand> iow
<fabiand> we check if /dev/kvm is there and block until it's there
<fabiand> which is never the case on non-kvm systems

@karmab: Though @fabiand is probably correct, there are a small number of things that might cause this. A few questions might help us pinpoint the root cause here.

What host OS are you running KubeVirt from?
Are you using the docker based dev image? ansible?
Does /dev/net/tun exist on your nodes? (./cluster/cli.sh ssh node01 if you're using the dev image)
Does lsmod | grep tun show a module named tun?
If not, does running [sudo] modprobe tun load the module?
Does kubectl get nodes -o yaml show devices.kubevirt.io/tun in both the allocatable and capacity sections?
Do the pod logs show any errors? kubectl -n kube-system get pods then kubectl -n kube-system logs virt-handler-XXXXX

hello @stu-gott

running kubevirt on centos
deploying through a manifest ( no docker based image)
/dev/net/tun does exist
lsmod | grep tun does show the module
devices.kubevirt.io/tun doesnt show in allocatable section nor capacity section
there are no logs for the pod, because it s in pending state

here are the virht-handler logs
level=info timestamp=2018-07-16T13:07:13.320421Z pos=virt-handler.go:87 component=virt-handler hostname=localhost
level=info timestamp=2018-07-16T13:07:13.331827Z pos=vm.go:210 component=virt-handler msg="Starting virt-handler controller."
level=info timestamp=2018-07-16T13:07:13.332648Z pos=cache.go:151 component=virt-handler msg="Synchronizing domains"
level=info timestamp=2018-07-16T13:07:13.432187Z pos=device_controller.go:131 component=virt-handler msg="Starting device plugin controller"
2018/07/16 13:07:13 grpc: addrConn.resetTransport failed to create client transport: connection error: desc = "transport: dial unix /var/lib/kubelet/device-plugins/kubelet.sock: connect: no such file or directory"; Reconnecting to {/var/lib/kubelet/device-plugins/kubelet.sock <nil>}
2018/07/16 13:07:14 grpc: addrConn.resetTransport failed to create client transport: connection error: desc = "transport: dial unix /var/lib/kubelet/device-plugins/kubelet.sock: connect: no such file or directory"; Reconnecting to {/var/lib/kubelet/device-plugins/kubelet.sock <nil>}
2018/07/16 13:07:15 grpc: addrConn.resetTransport failed to create client transport: connection error: desc = "transport: dial unix /var/lib/kubelet/device-plugins/kubelet.sock: connect: no such file or directory"; Reconnecting to {/var/lib/kubelet/device-plugins/kubelet.sock <nil>}
level=info timestamp=2018-07-16T13:07:18.433996Z pos=device_controller.go:125 component=virt-handler msg="kvm device plugin started"
2018/07/16 13:07:18 grpc: addrConn.resetTransport failed to create client transport: connection error: desc = "transport: dial unix /var/lib/kubelet/device-plugins/kubelet.sock: connect: no such file or directory"; Reconnecting to {/var/lib/kubelet/device-plugins/kubelet.sock <nil>}
2018/07/16 13:07:18 grpc: Server.Serve failed to create ServerTransport:  connection error: desc = "transport: write unix /var/lib/kubelet/device-plugins/kubevirt-kvm.sock->@: write: broken pipe"
2018/07/16 13:07:19 grpc: addrConn.resetTransport failed to create client transport: connection error: desc = "transport: dial unix /var/lib/kubelet/device-plugins/kubelet.sock: connect: no such file or directory"; Reconnecting to {/var/lib/kubelet/device-plugins/kubelet.sock <nil>}
2018/07/16 13:07:20 grpc: addrConn.resetTransport failed to create client transport: connection error: desc = "transport: dial unix /var/lib/kubelet/device-plugins/kubelet.sock: connect: no such file or directory"; Reconnecting to {/var/lib/kubelet/device-plugins/kubelet.sock <nil>}
2018/07/16 13:07:22 grpc: addrConn.resetTransport failed to create client transport: connection error: desc = "transport: dial unix /var/lib/kubelet/device-plugins/kubelet.sock: connect: no such file or directory"; Reconnecting to {/var/lib/kubelet/device-plugins/kubelet.sock <nil>}
level=info timestamp=2018-07-16T13:07:23.440245Z pos=device_controller.go:125 component=virt-handler msg="tun device plugin started"
2018/07/16 13:07:23 grpc: Server.Serve failed to create ServerTransport:  connection error: desc = "transport: write unix /var/lib/kubelet/device-plugins/kubevirt-tun.sock->@: write: broken pipe"

I think I am seeing the same issue with kubevirt 0.7.0 on minishift.

@fabiand the current minishift downloads an OpenShift 3.9.0 cluster, which would definitely behave like described as the device manager API changed (and requires a feature-gate to enable). Is there a way to direct minishift to download a 3.10 image?
Per conversations with @karmab, I believe his OpenShift (3.10.0?) cluster is running on CentOS. The "no such file or directory" error seen in the logs is really the case: the kubelet never created the device manager socket--so the bootup sequence for virt-handler obviously couldn't succeed.

checked on a multiple nodes installation using 3.10 and the kubelet socket is indeed there, so i believe the issue is specific to oc cluster up ( and some missing flags)

installed was done with those steps
yum -y install wget docker git bash-completion qemu-img
systemctl enable docker
sed -i "s@# INSECURE_REGISTRY=.*@INSECURE_REGISTRY='--insecure-registry <IP_ADDRESS>/16'@" /etc/sysconfig/docker
wget -O /root/oc.tar.gz https://github.com/openshift/origin/releases/download/v3.10.0-rc.0/openshift-origin-client-tools-v3.10.0-rc.0-c20e215-linux-64bit.tar.gz
cd /root ; tar zxvf oc.tar.gz
mv /root/openshift-origin-client-tools-*/oc /usr/bin
rm -rf  /root/openshift-origin-client-tools-*
curl -L https://storage.googleapis.com/kubernetes-release/release/`curl -s https://storage.googleapis.com/kubernetes-release/release/stable.txt`/bin/linux/amd64/kubectl -o /usr/bin/kubectl
chmod +x /usr/bin/kubectl
chmod +x /root/*sh
sed -i "s@OPTIONS=.*@OPTIONS='--insecure-registry <IP_ADDRESS>/16'@" /etc/sysconfig/docker
systemctl start docker --ignore-dependencies

IP=`ip a l  eth0 | grep 'inet ' | cut -d' ' -f6 | awk -F'/' '{ print $1}'`
PUBLICNAME=$IP.xip.io
oc cluster up --public-hostname $PUBLICNAME --routing-suffix $PUBLICNAME --enable=service-catalog,router,registry,web-console,persistent-volumes,rhel-imagestreams,automation-service-broker
oc login -u system:admin
docker update --restart=always origin
oc adm policy add-cluster-role-to-user cluster-admin developer

VERSION="v0.7.0"
oc project kube-system
wget https://github.com/kubevirt/kubevirt/releases/download/$VERSION/kubevirt.yaml
oc adm policy add-scc-to-user privileged -z kubevirt-privileged -n kube-system
oc adm policy add-scc-to-user privileged -z kubevirt-controller -n kube-system
oc create -f kubevirt.yaml
setfacl -m user:107:rwx /root/openshift.local.clusterup/openshift.local.pv/pv*
oc adm policy add-scc-to-user privileged -z kubevirt-controller -n kube-system

i can confirm that the issue is specific to oc cluster up, where we need to sort out how to properly enable device plugin.
since i dont think work is needed on kubevirt side, closing this

As a data point, I repeated the above steps twice, once using the oc cluster up command exactly as provided and once adding the device-plugins flag to --enable. In both cases I ended up with a cluster with /var/lib/kubelet/device-plugins/kubelet.sock present.

Actually, there is an issue here.

/var/lib/kubelet/device-plugins/ from the virt-handler pod's point of view
/rootfs/var/lib/kubelet/device-plugins/ is where it's actually mounted on the node

I've retraced @karmab's steps and concur with his assessment. The root cause of the symptom seen here is that a mount point is missing in the origin docker container: /var/lib/kubelet/device-plugins needs to be bind mounted to the host's filesystem.
Currently kubelet does create /var/lib/kubelet/device-plugins/kubelet.sock within the origin container, but since it's not exposed on the host, the socket simply cannot be seen by any other cluster resources.

@deads2k @bparees any insights on this?
@stu-gott do you think it's a bug in oc? Worth filing a bug?

opened https://github.com/openshift/origin/pull/20351 with a possible fix

@rwsu Believe it or not your issue is completely different. I just filed https://github.com/kubevirt/kubevirt/issues/1346

for the record, it seems there s little chance the fix will happen on origin side....

Any expectation whether this will be fixed in 0.7.1, please?

Experiencing this same issue on Fedora Atomic running upstream kubernetes 1.10.5.
level=info timestamp=2018-08-02T17:41:36.136023Z pos=virt-handler.go:87 component=virt-handler hostname=shed-compute02
level=info timestamp=2018-08-02T17:41:36.140732Z pos=vm.go:210 component=virt-handler msg="Starting virt-handler controller."
level=info timestamp=2018-08-02T17:41:36.141336Z pos=cache.go:151 component=virt-handler msg="Synchronizing domains"
level=info timestamp=2018-08-02T17:41:36.240992Z pos=device_controller.go:133 component=virt-handler msg="Starting device plugin controller"
level=error timestamp=2018-08-02T17:41:36.241340Z pos=device_controller.go:123 component=virt-handler msg="Error starting kvm device plugin: listen unix /var/lib/kubelet/device-plugins/kubevirt-kvm.sock: bind: no such file or directory"
level=error timestamp=2018-08-02T17:41:36.242016Z pos=device_controller.go:123 component=virt-handler msg="Error starting tun device plugin: listen unix /var/lib/kubelet/device-plugins/kubevirt-tun.sock: bind: no such file or directory"

Looks like the device plugins aren't being created but I'm not sure why.

@rmohr @stu-gott what's the curretn statee? Isn't this already fixed?

@mareklibra @rwsu are you still seeing this issue? (I assume you do)
@stu-gott do you have an idea why the bug appears to them? And do you know why it obviously does not appear in CI?

@rwsu I believe that the issue you reported was fixed in https://github.com/kubevirt/kubevirt/pull/1351. Can you confirm whether or not you're still having issues with latest master? There has not been a release since that was merged, so 0.7.0 will have the improper device plugin order on startup.
@karmab This issue is limited to OpenShift Origin clusters that were instantiated with oc cluster up, correct? Are there any other scenarios where the device plugins directory is not present on the host?
@fabiand We're moving toward removing dependence on device plugins for virt-handler itself (e.g. https://github.com/kubevirt/kubevirt/pull/1404) which would fully address this issue--by simply making the missing device plugins mountpoint moot.

@karmab Are you still completely blocked by this issue, or have you found an interim workaround?

i switched to k8s for the time beeing.
@rwsu also confirmed me that using emulation mode worked correctly on
master.
El El vie, 10 ago 2018 a las 14:28, Stu Gott<EMAIL_ADDRESS>escribió:

@karmab https://github.com/karmab Are you still completely blocked by
this issue, or have you found an interim workaround?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/kubevirt/kubevirt/issues/1316#issuecomment-412067542,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABwVA0ZGoNkIn8DX5-hyhDQsSrx4CytXks5uPXx3gaJpZM4VQx-9
.

--
Karim,

Another fact is that this only seems to affect dockerized based Origin depoyments.
Dropping the urgency.

Still facing the same issue with v0.8.0-alpha.1 for both devices.kubevirt.io/kvm and devices.kubevirt.io/tun.
Running OC 3.10 via oc cluster up.
@stu-gott , I'm not sure if I understand the described issue with missing /var/lib/kubelet/device-plugins . Can you please explain? Is there a workaround? Thanks.

Same for me.

@mareklibra So the issue is there's a missing bind mount in some configurations. Components that use the device plugin framework (e.g. virt-handler) do so by contacting the device plugin manager using a unix socket. Unfortunately the missing bind mount means virt-handler cannot contact the device plugin manager and register tun/kvm devices. Because KubeVirt cannot advertise tun or kvm devices, pods that require them cannot be scheduled.
@karmab submitted a PR to address the issue on the OpenShift side, which was merged this week. https://github.com/openshift/origin/pull/20351
We have an effort on the KubeVirt side to re-think our approach and possibly use a different mechanism to expose devices. Either fix would fully address the problem, by making the socket be available or making it not matter.

To answer myself, looks like you need to go all the way back to v0.6.4 top get something going on Minishift with Origin 3.10 (or at least, to get past this particular error as now I am hitting different issues).

Btw - minishift is likely also affected,because it has the same bug as oc cluster up (as minishift is using oc cluster)

https://github.com/kubevirt/demo/pull/71 conains a workaround: https://github.com/kubevirt/demo/pull/71/files#diff-7efff1768a14c4df93c738d9c406385aR37

Workaround:
  oc cluster up
  oc cluster down
  # Workaround for https://github.com/openshift/origin/pull/20351
  KUBELET_ROOTFS=$(sudo docker inspect $(sudo docker ps | grep kubelet | cut -d" " -f1) | jq -r ".[0].GraphDriver.Data.MergedDir" -)
  sudo mkdir -p /var/lib/kubelet/device-plugins $KUBELET_ROOTFS/var/lib/kubelet/device-plugins
  sudo mount -o bind $KUBELET_ROOTFS/var/lib/kubelet/device-plugins /var/lib/kubelet/device-plugins
  sudo ls /var/lib/kubelet/device-plugins
  oc cluster up
  # … deploy kubevirt

@fabiand when are we expecting this to no longer be required? I ask because I see the getting started content would still fail on Minishift today (it uses 0.8.0 but does not list these workarounds).

The workaround for oc and minishift will be required until openshift
releases an update to 3.10 or 3.11.
We shoudl adjust the getting started content in the meantime ...

I'm apparently confused.  When I try to use the workaround in https://github.com/kubevirt/kubevirt/issues/1316#issuecomment-419071435 , after I do the 'cluster down' there are no docker contaiers running so the search for the KUBELET_ROOTFS fails.

before diving int debugging.
The latest poenshift (3.11) and minishift, as well as minikube don't
require any workaround anymore. Thus I'd suggest to update to the latest
version of the platform you are using.
What are you using?

Fixed as of
origin 3.11 (oc)
minishift 1.26.1
minikube 0.30.0

Im following the kubevirt.io demo for using minishift. http://kubevirt.io/get_kubevirt/.
Host is F29 desktop stock.  I've tried VERSION=0.8.0 per the demo, as well as v0.95.0 and v0.10.0

Yeah this stil manifiest with the versions you cite as fixed.

Mark, just making sure - With the new versions it is fixed for you?
I've filed https://github.com/kubevirt/kubevirt.github.io/issues/160 to update the getting started guide.

@fabiand as of Fri afternoon last, no, it was not fixed, giving the same behavior.  I can re-run it this afternoon to check again.  Are there any specific outputs you need to confirm the versions? If I don't hear I'll put together what seems best and post it before COB today.

@markllama note that if using minishift, you need to pass flag --openshift-version to force version to 3.11.0, default is 3.10

@karmab: that's not what I'm seeing.  I'll try again.  This is the minishift startup?

disregard my last comment, minishift 1.26 version enabled 3.11 as default version for openshift

Yep.  And it still demonstrates the problem.

troubleshooted this with mark and the issue was that minishift lacks nested virt so using emulation mode is necessary on this platform (and our http://kubevirt.io/get_kubevirt/ page needs to be updated to reflect it)

@karmab awesome, thanks for helping mark.
Karim, can you get hold of https://github.com/kubevirt/kubevirt.github.io/issues/160 ?

I get this with v0.10.0 with kubeadm v1.12.2 on CoreOS

I still see this issue on v0.10.0 ; 1.10.4 k8, ubuntu 16.04 (on gcp with HW virt). It was working; cleaned up cluster to redeploy and now its back to reporting 0's on both tun/kvm in kubectl get nodes -o yaml

Seems like we need to reopen this. Could one of you share a corresponding virt-handler log from a node where it reports 0?

I get this with v0.10.0 with kubeadm v1.12.2 on CoreOS (stable (1911.3.0))

@andrewwebber where are you deploying kubevirt? Is the CoreOS instance a VM or a bare-metal machine?

@rmohr I initially tried this on a KVM hosted CoreOS VM installed via the ISO (Matchbox), not the virtual machine image.

I still see this issue on v0.10.0 ; 1.10.4 k8, ubuntu 16.04 (on gcp with HW virt). It was working; cleaned up cluster to redeploy and now its back to reporting 0's on both tun/kvm in kubectl get nodes -o yaml

maybe you re missing nested virt on this new deployment. gcp requires you to use a custom image and specific zones for nested virt. check with grep vmx /proc/cpuinfo that nested virt is indeed enabled or create a configmap enabling emulation as per the doc

virtual machine image

i suggest the same, checking whether nested virt is enabled in the vm as per my previous comment

I could also imagine that coreos is missing the relevant modules .. (kvm, vhost*)

For me; it appears when kubelet is restarted, my kubelet sits in a container, however if kubelet isn't redeployed; no issues.

I was already able to run openstack-helm on coreos so I didnt think there would be an initial concern.

same issue in
``oc v3.11.43
kubernetes v1.11.0+d4cacc0
features: Basic-Auth GSSAPI Kerberos SPNEGO
Server https://cnv-executor-xeniya-master1.example.com:8443
openshift v3.11.43
kubernetes v1.11.0+d4cacc0``

can you run grep vmx / proc/cpuinfo on your nodes?
El El dom, 2 dic 2018 a las 6:01, Xenia Lisovskaia<EMAIL_ADDRESS>escribió:

same issue in
``oc v3.11.43
kubernetes v1.11.0+d4cacc0
features: Basic-Auth GSSAPI Kerberos SPNEGO
Server https://cnv-executor-xeniya-master1.example.com:8443
openshift v3.11.43
kubernetes v1.11.0+d4cacc0``
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/kubevirt/kubevirt/issues/1316#issuecomment-443481906,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABwVAzpkAC1qCC4-N7R1nFNyIfDv6ZlYks5u0165gaJpZM4VQx-9
.

--
Karim,

grep vmx /proc/cpuinfo
gives me no outout. I am trying to deploy Kubevirt on below metioned enviorment:
Base machine:
(python34) [ec2-user@ip-172-31-19-110 ~]$ cat /etc/os-release
NAME="Amazon Linux AMI"
VERSION="2018.03"
ID="amzn"
ID_LIKE="rhel fedora"
VERSION_ID="2018.03"
Kubernetes enviorment:
Kernel Version:             4.4.0-1072-aws
OS Image:                   Ubuntu 16.04.5 LTS
Error:
kubelet, ip-172-16-61-253.us-east-2.compute.internal     Updated Node Allocatable limit across pods
3m          13m          197       virt-launcher-vm-cirros-qkvzz.156e5896b1df1db4                 Pod                                                           Warning   FailedScheduling          default-scheduler                                        0/3 nodes are available: 1 Insufficient devices.kubevirt.io/tun, 1 Insufficient devices.kubevirt.io/vhost-net, 1 node(s) didn't match node selector, 3 Insufficient devices.kubevirt.io/kvm.
19m         34m          294       virt-launcher-vm-cirros-rdfdn.156e5778393eb436                 Pod                                                           Warning   FailedScheduling          default-scheduler                                        0/3 nodes are available: 1 Insufficient devices.kubevirt.io/tun, 1 Insufficient devices.kubevirt.io/vhost-net, 1 node(s) didn't match node selector, 3 Insufficient devices.kubevirt.io/kvm.

Please also provide kubectl get configmap -o yaml -n kube-system kubevirt-config
And if possible, just out of curiosity: virt-host-validate

the above problem no more appearing now after reinstalling it.
But VNC on AWS EC2 machines is not working and getting below error. any help?
[ec2-user@ip-172-31-9-22 ~]$ ./virtctl vnc testvm
{"component":"virtctl","level":"info","msg":"connection timeout: 1m0s","pos":"vnc.go:137","timestamp":"2018-12-10T17:53:38.193593Z"}
{"component":"virtctl","level":"error","msg":"remote-viewer execution failed: exit status 1, output: \n(remote-viewer:13172): Gtk-WARNING **: cannot open display: \n","pos":"vnc.go:230","timestamp":"2018-12-10T17:53:38.217773Z"}

Good to hear!
For VNC to work you need a graphical desktop.
Did you try serial console virtctl console VMNAME?

virtctl console VMNAME working as expected. For Graphical desktop, do you any sample yaml?

For Graphical desktop, do you any sample yaml?

The host where you run virtctl needs to be a graphical desktop.
As VNC (client) needs X11 to run.

Can confirm that v0.11.0 works on CoreOS 1911.4.0 bare metal, including vnc viewer. Thank you kubevirt!
Does anyone get the following kernel warning when starting a VM and is it an issue?
kernel: L1TF CPU bug present and SMT on, data leak possible. See CVE-2018-3646 and https://www.kernel.org/doc/html/latest/admin-guide/l1tf.html for details.

@andrewwebber that's probably due to an "insecure" cpu configuration.
If /dev/kvm is not availale then softwaremulation needs to be used.
/close

Hi,
I'm hitting this:
19s         Warning   FailedScheduling         pod/virt-launcher-testvm-dtvqx                  0/2 nodes are available: 1 Insufficient devices.kubevirt.io/tun, 1 Insufficient devices.kubevirt.io/vhost-net, 1 node(s) didn't match node selector, 2 Insufficient devices.kubevirt.io/kvm.

When using latest 0.18.1 version deployed via the steps at minikube tutorial, both on katacoda and on a UPI installation.
What would be needed to be provided for diagnosis?

@iranzo did you restarted virt-handler and virt-controller pods after config map update?

Hi, configmap update is defined even 'before' starting deploying kubevirt.
Actual sequence of commands are:
kubectl create configmap -n kube-system kubevirt-config --from-literal debug.useEmulation=true
export KUBEVIRT_VERSION=$(curl -s https://api.github.com/repos/kubevirt/kubevirt/releases|grep tag_name|sort -V | tail -1 | awk -F':' '{print $2}' | sed 's/,//' | xargs)
echo $KUBEVIRT_VERSION
kubectl create -f https://github.com/kubevirt/kubevirt/releases/download/${KUBEVIRT_VERSION}/kubevirt-operator.yaml
kubectl create -f https://github.com/kubevirt/kubevirt/releases/download/${KUBEVIRT_VERSION}/kubevirt-cr.yaml
kubectl get pods -n kubevirt
virtctl is a client utility to provide some more convenient ways to interact with the VM:
wget -O virtctl https://github.com/kubevirt/kubevirt/releases/download/${KUBEVIRT_VERSION}/virtctl-${KUBEVIRT_VERSION}-linux-amd64
chmod +x virtctl
kubectl apply -f https://raw.githubusercontent.com/kubevirt/demo/master/manifests/vm.yaml

kubectl get vms
./virtctl start testvm
kubectl get vmis

Did you create the kubvirt-config configmap?

@fabiand in the past I've been  doing above steps in https://github.com/kubevirt/kubevirt/issues/1316#issuecomment-503044457
Is there anything else expected outside of first step?

@iranzo IIRC the kubevirt config map should be under the kubevirt ns. So steps should be:

export KUBEVIRT_VERSION=$(curl -s https://api.github.com/repos/kubevirt/kubevirt/releases|grep tag_name|sort -V | tail -1 | awk -F':' '{print $2}' | sed 's/,//' | xargs)
echo $KUBEVIRT_VERSION
kubectl create -f https://github.com/kubevirt/kubevirt/releases/download/${KUBEVIRT_VERSION}/kubevirt-operator.yaml
kubectl create -f https://github.com/kubevirt/kubevirt/releases/download/${KUBEVIRT_VERSION}/kubevirt-cr.yaml
create or edit the kubevirt-config(I do not remember if it exists)
delete all pods under the kubevirt ns to be sure that new ones will apply all options from the config-map

I'll redeploy the environment to validate, but as said, it was working like this (and steps were taken from kubevirt.io website)

Seems that during my tests, the configmap being created on kube-system was good because the underlying hipervisor had indirect support for nested vms, I've replaced the name and create it after the operator is deployed and worked fine so far.
Thanks!


Trying to read a BSON in JSON

hi,
im trying to read from MongoDB I think im using strick mode, but i dont seem to get the right json objetc, for example:
this is what im getting

and this is what i want
"_id": "5000069",
"Key": "edf54559-752a-3e44-a3af-dc8b682ddea3"

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

ID: 05eed8d3-001c-543f-afb2-823a2cff8a35
Version Independent ID: 1485e156-1eab-20ae-8fe6-ac82301fa846
Content: Copy data from MongoDB using Azure Data Factory - Azure Data Factory
Content Source: articles/data-factory/connector-mongodb.md
Service: data-factory
GitHub Login: @linda33wj
Microsoft Alias: jingwang

@giancarlos29 Thanks for your question. We are checking on this and will respond to you soon.

hi, im sorry i did not menction the doc especifically.
https://docs.microsoft.com/en-us/azure/data-factory/connector-mongodb
Im using Azure Data Factory, trying to copy from Mongodb to Azure SQL Server.

@giancarlos29 Since the issue is not a feedback on the doc in reference, I would recommend you to create a thread on the forums - MSDN  or stack overflow.
Once you post your issue on forums, it will have visibility across the community which is a better suited audience for such types of issues.
Please create a Forum thread and post it's link here and tag me so that we can track that thread. We would love to work with you on the issue on the forums.
I will now proceed to close this issue. Feel free to comment if you have any other queries.


delete go-ini files

Sync-ed govendor again and these files were deleted.
It might be causing issues with other services that are using SYNQ-Golang sdk.

Closing this. Changed the package manager to dep.
https://github.com/SYNQfm/SYNQ-Golang/pull/132


setup-dapr GitHub action recommended by docs is out of date and seemingly not maintained

Describe the issue
The How to: Use the Dapr CLI in a GitHub Actions workflow documentation page recommends using the dapr/setup-dapr action to install the Dapr CLI in the context of a GitHub workflow, but dapr/setup-dapr is so out of date that it results in workflow warnings being produced, related to the minimum supported version of Node.js, and use of the set-output command:
Build & Test Samples (ubuntu-latest, sdk-baseline)Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: dapr/setup-dapr@v1. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
Build & Test Samples (ubuntu-latest, sdk-baseline)The following actions uses node12 which is deprecated and will be forced to run on node16: dapr/setup-dapr@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Build & Test Samples (ubuntu-latest, sdk-baseline)The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

This was reported on the repo way back in December 2022 but has not been acknowledged or acted upon, suggesting the workflow action is not maintained.
URL of the docs
How to: Use the Dapr CLI in a GitHub Actions workflow
Expected content
The page should describe how to use the Dapr CLI in a GitHub workflow via a mechanism that is supported, or at the least, doesn't result in workflow warnings.
Screenshots

Additional context
https://github.com/dapr/setup-dapr/issues/106
/Cc @msfussell @paulyuk

We're doing a round of update to migrate all Github Action to use nodejs20. Please consider prioritizing this issue, thanks 🙏


Update ozone from 1.0.0 to 1.1.0

What changes are proposed in this pull request?
Ozone 1.1.0 has been released for a long time and 1.1.0 is more stable than 1.0.0. We can update the ozone version.

@maobaolong Please take a look at this PR.

@captainzmc Would you like to show some change list which have to upgrade the alluxio-side ozone version?

@captainzmc Would you like to show some change list which have to upgrade the alluxio-side ozone version?

@maobaolong Ozone 1.1.0 in addition to fix some 1.0 bugs, It also add some future. I think the third one about performance are helpful, because alluxio currently uses OFS/O3FS to access ozone.
1、Volume/Bucket Quota Support
2、Security related enhancements
3、ofs/o3fs performance improvements with Teragen and Spark
4、Recon improvements

@captainzmc I'm glad that Ozone 1.1.0 have such great features, please list some features or bugfix about client side.

@maobaolong any comments ? are you good with this PR?

@apc999 I'm fine for merge this PR.

@captainzmc I'm glad that Ozone 1.1.0 have such great features, please list some features or bugfix about client side.
Sorry for the late reply. Yes, there are some optimizations and bug fixes for the 1.1 client. For example, enable trash, optimize delete and rename, and fix o3FS list bugs. These all need to be modified on the client side.

@captainzmc Thanks for your information, @apc999 would you please merge this PR?

ping @apc999

alluxio-bot, merge this please