JAV-55 added docker compose config

Coverage increased (+4.8%) to 98.592% when pulling 531b350fd919d81a3baa1a5686892ee91e3c4370 on JAV-55_docker_compose into 26339ffe38fa37d795fb0b4cbe42c32223fdbdb5 on master.

Coverage remained the same at 93.791% when pulling 12f53b485a0a66caf232530f4f9da224aca56fd2 on JAV-55_docker_compose into 26339ffe38fa37d795fb0b4cbe42c32223fdbdb5 on master.


mean coordinates of the scene

Hello,
I would like to ask about the effects of computing the mean coordinates and applying these means to the final scene map. Because I only see that you applied this step in the initialization phase but not the end-2-end train phase and the test phase. Is it important to perform this step and what was the motivation behind it? Thank you in advance.

Hi,
the mean coordinate is stored in the network after being set in the initialisation phase. That's why we do not have to set it again during e2e training or testing.
I did not ablate the effect of setting the mean coordinate in the final version of the code.The step normalises the coordinate frame for the network and makes initial predictions more meaningful. Imagine the scene center is 100 kilometers away. The network has to predict scene coordinates in the range of hundreds of kilometers which might be difficult to converge to, because the initial reprojection errors will be very large.
That being said, for most datasets, the effect will be small since the center mean is near 0,0,0 anyway.


gio: move Task::run_in_thread to an extension trait

The trait is implemented only when returning values that implement ToSendValue.

This seems to address the soundness issue. However

It is not ergonomic
Is calling the trait TaskSendManualExt the right convention? or should it simply be TaskSend

I wonder if to improve ergonomics we can make the closure passed to run_in_thread return Result<Value, Error> and call return_value and return_error ourselves... would the compiler be able to infer the value type?

That's not how I was thinking of this. I would've done it as gio::Task<T: ToValue + FromValue>. That way you could also make sure to only implement Send+Sync for T: Send and could simplify a lot of the API here to not have to work on glib::Values anymore.

Oups sorry I misclicked and marked it as ready for review

Actually maybe we do not need neither the extension trait, nor implementing Task manually... How about this approach?

Actually maybe we do not need neither the extension trait, nor implementing Task manually... How about this approach?

That would mean that Task can't be Send though

Closing in favor of https://github.com/gtk-rs/gtk-rs-core/pull/446


深度度量学习 Deep Metric Learning

https://yingzhangdut.github.io/deep-learning/2019/11/03/Deep-Metric-Learning.html

test

hello！


tabletserver endtoend: more tests

I've also simplified streamlog.go along the way.

LGTM thanks for removing the equivalent python tests, saves us run time :)

Build is failing due to something unrelated:
xargs: /home/travis/gopath/dist/protobuf/bin/protoc: Permission denied
So, I'll submit as soon as everything else goes green.


The two-finger move requirement is back in mobile

We changed this a while back, and made it so that even on mobile you don't have to use the two finger gesture to move the map around. It has not returned, however. Only happens in the Luolaseura version of the map, not on planetcaver.net. Maybe an issue in the HTML then?
IIRC the trick last time was to avoid other stuff on the screen, i.e., only have the Google map occupy the screen.

Luolaseura uses the standard html file from repo, dont know what has changed then.
-------- Original Message --------
On 19 Oct 2020, 10:40, Jari Arkko wrote:

We changed this a while back, and made it so that even on mobile you don't have to use the two finger gesture to move the map around. It has not returned, however. Only happens in the Luolaseura version of the map, not on planetcaver.net. Maybe an issue in the HTML then?
IIRC the trick last time was to avoid other stuff on the screen, i.e., only have the Google map occupy the screen.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

Hmm. Maybe it is a platform specific issue then -- I saw it on ipad. Needs more investigation.

... and not on all ipads, either, apparently. will need to investigate ...

Just a thought: If the map is embedded in a page that is scrolled up/down and sideways by sweeps, then it is natural that Maps wants two fingers.


LOLE dashboard item should take electricity from P2P into account (if available)

Before we included P2P (batteries and EV) in the ETM, the loss of load expectation (LOLE) was more of a statistical property. The LOLE calculation, of which the result is shown as a dashboard item, would:

Take the demand profile, scaled by the actual electricity demand
Subtract any electricity production by wind turbines, solar panels and hydro river from it (if available)
Compare the remaining electricity demand with the available dispatchable electricity capacity production and count the hours in which this capacity cannot meet the electricity demand

P2P could lower the LOLE by supplying (some of) its stored electricity back to the grid. It does, however, act differently from a dispatchable electricity, because it might not always be charged when you need its electricity to lower the LOLE. Merit does calculate the amount of electricity stored in the battery at every hour of the year, but including it in the LOLE calculation is a little trickier. I suggest to pick this up after the February deploy.

but including it in the LOLE calculation is a little trickier

I see the following complication:
Merit currently calculates a production (positive part of the load) curve for P2P if Merit is enabled. In this case, the production curve could be subtracted from the demand as with wind, solar etc. to yield the residual demand curve which needs to be compared to the dispatchable capacity at each point.
The current LOLE calculation does not require a full run of Merit, however, so including the effects of P2P   would still depend on whether Merit is 'on'.
@antw @dennisschoenmakers any ideas of how to ga about this?

Could we say: "the LOLE calculation is more accurate with respect to P2P when Merit is turned on"?

Could we say: "the LOLE calculation is more accurate with respect to P2P when Merit is turned on"?

That would be misleading. Currently, the Merit module does not use the effects of P2P on the LOLE whether is is 'on' or 'off'.

That would be misleading. Currently, the Merit module does not use the effects of P2P on the LOLE whether is is 'on' or 'off'.

:grinning: Well, not now: I was talking about that hypothetical situation.

@dennisschoenmakers and I discussed the following solution to this issue:

Leave the LOLE dashboard item and the underlying calculation the way it is; that way the LOLE dashboard item represents a statistical measure for the number of hours per year that the national electricity park cannot meet the national demand. This is not equivalent to the number of blackout hours per year, as these "LOLE" hours could be mitigated by importing electricity or making clever use of the electricity stored in batteries.
Add a new dashboard item called "blackout hours" (or similar). This dashboard item will only be available when merit is on and takes into account the full results of merit including the electricity stored in batteries (see https://github.com/quintel/etmodel/issues/2058)

This solution has the following advantages:

Both dashboard items (LOLE and blackout) are well defined and represent different approaches to the issue of supply being able to meet demand (statistical versus calculated on an hourly basis respectively)
When merit is off we show the LOLE dashboard item, which does not require a full run of merit

What do you think of this solution, @AlexanderWirtz , @ChaelKruip and @antw ?

I like the general idea. It would require merit to do something it currently does not: register the generation 'shortfall' per hour, as well as the actual import capacity used each hour.
The latter would be a useful addition, as it is a step on the way to giving import capacity a 'virtual plant' status with assigned marginal costs according to an imported .csv time curve from a scenario for a neighboring country. Once we do that we can let the import capacity compete in a national market.
I do not think import is an available option yet in merit, is it?

@jorisberkhout: we also discussed the addition of an extra node in the graph that will represent the shortfall of electricity that cannot be produced nor imported. Perhaps it is also good to elaborate a bit on this idea here? or do we have another Issue for that somewhere else? 😄

or do we have another Issue for that somewhere else? 😄

Yes, it is described in https://github.com/quintel/merit/issues/139. Implementing it as we speak 😄

I'll close this issue; the actionable part regarding a new dashboard item displaying blackout hours is described in https://github.com/quintel/etmodel/issues/2058.


How can i generate random faces with texture using this face model?

How can i generate random faces with texture using this face model? Just like script_gen_random_head.m script from the official basel face model.
Thanks!

Have a look at MorphableModel::draw_sample.

I'm going to close this, feel free to re-open if you have specific issues with the library.


103 windows creds fixes

closes #103

Looks good @VegaJakeg - I removed the credentials file with your details


Dashboard ui

@uranusjr 你 users 那邊似乎改了很多東西，可能要請你幫忙 merge master

Current coverage is 95.08%

Merging #60 into master will decrease coverage by -0.73% as of c3e4932

@@            master     #60   diff @@
======================================
  Files           27      25     -2
  Stmts          765     549   -216
  Branches         0       0
  Methods          0       0
======================================
- Hit            733     522   -211
  Partial          0       0
+ Missed          32      27     -5

Review entire Coverage Diff as of c3e4932

Powered by Codecov. Updated on successful CI builds.


how can I understand about "page context" and "browser context"?

I mean, if I want to run some code in target page context, something like  Casperjs.evaluate(). In this case, which one the concept of puppeteer is same with?

I think we have been using them interchangeably to mean the same thing. Code that runs in Chromium as apposed to code that runs in node.
The equivalent of Casperjs.evaluate would be page.evaluate

@JoelEinbinder yep, I ran a test to figure out. And as you said, they are equal. Thanks.


Send context-switch information to remote & Batch multiple callstacks/timers into single messages.

This will enable remote context-switch information tracking. As there are several thousands context-switches per second, this will buffer the context-switches and send them as a single message via a separate thread each 0.02 seconds.
The same thread will also do this buffering for callstacks and timers.
Furthermore, callstacks that are already known, will be only send using there hash and the timestamp.

I'm not convinced this CL leads to performance improvements.
Sending context switches and callstacks as human readable data is way overkill as we need to go through "cereal" serialization which will convert simple POD style data to text containing the names and values of the variables being serialized. The message size for a simple context switch is going to be 10x what it would be were we to send raw binary data.

Okay. So the reason, why I did not send raw data here, was that I think different compilers could rearrange the structs, which would break us. However, I also see your point of the 10X size. And we already send raw data for the timers. So I'd suggest, I also switch to still buffer the messages, but than send raw data as it is done for the uprobe timers. For obvious reasons, I really hope to see this PR upstream within the next two weeks :). In particular this PR is required for remote context switch information.

Also, it seems like there will be quite a lot of contention introduced by locking m_MessageBufferMutex for every callstack, timer, and when serializing the messages...

I see your point. But, from my experience, it does not feel like there is an issue here. But this is something we should benchmark and optimize if needed. However, I'd suggest to do these optimizations later. As this would not harm us.

TcpEntity already implements buffering of messages by pushing every incoming message to a LockFreeQueue and having a consumer thread doing the actual sending. This was done to minimize the cost of sending messages on the caller thread. See TcpEntity::SendMsg, TcpEntity::SendData and TcpEntity::FlushSendQueue. Perhaps we could refine the implementation of that consumer thread so that it would bundle messages together, although keep in mind that Nagle's algorithm does the same thing at a lower level. We could also have that thread sleep a bit instead of busy looping as long as there are messages to be sent.
Another thing we could do is minimize the message header size to a strict minimum. The message class should be refactored. Initially, all messages were the same size. Variable size support was added later but we kept the union for the header. It seems it would be possible to bring down the size of the message header to not much more than 32 bits.
In any case, I think it would be good to actually measure the performance improvements of these changes as it's not obvious that they will be as beneficial as we think.

I agree. There is lot of potential for improving the performance. We should invest time in microbenchmarking and performance measurements, as well as in proper testing. However, I don't think this is something I can achieve in the next one and a half week.

Okay, So I updated the PR, such that we send raw data for the context switch information. For the sampling callstacks, we can't easily send them as rawdata, as they contain a std::vector. We would need to create a deep copy by our own. Also, sampling callstacks have been serialized before this PR, so at least we should not loose performance here.


Set modal form's other value when static select action occurs.

My main purpose is in modal has 2 selects.

First select is Parent category.
Second select is Sub category. When parent category is selected, sub category fetch data from server and appears.

The problem is after select twice parent category, I am updating modal view and replace sub category select box. But can't change selected sub category. Sub category value is not there anymore. I want to set sub category value to empty when change parent category.

Is there a way to set modal form's other value when select or input value changed(triggering action)?

How can I set static select value to empty when other action occurs?

Hi @iamtsend,
Are you using the static_select -› initial_option property to set the default value of the sub-category select? You can also remove the initial_option to not select any default value.

Hi @mwbrooks ,
I don't using initial_option property.
Preparing view like below.
const actions = {
      type: 'actions',
      block_id: 'category',
      elements: [],
    };
    actions.elements.push({
      type: 'static_select',
      placeholder: {
        type: 'plain_text',
        text: 'Please select',
      },
      options: [
        ...initData.categories,
      ],
      action_id: 'parentCategory',
   });
    if (initData.subCategories && initData.subCategories.length > 0) {
     actions.elements.push({
        type: 'static_select',
        placeholder: {
          type: 'plain_text',
          text: '選択してください',
        },
        options: [
          ...initData.subCategories,
        ],
        action_id: 'subCategory',
      });
    }
    view.blocks.push(actions);

Main problem is I cannot set subCategory value to empty. When parentCategory is selected, subCategory must be empty if the subCategory has value.

I am updating modal form like below if parentCategory action triggered.
# prepare initData again here
await client.views.update({
      view_id: viewId,
      hash,
      view: adFormView(initData),
    });

Other question is I prepared initData after parentCategory triggered and modal appeared first. Can I prepare initData once?


How to handleDS.errors?

Is there any code need be wriiten if server throws 422 errors.The one which is mentioned in the below link.
http://emberjs.com/api/data/classes/DS.Errors.html

You can do something like this
const Validations = buildValidations({
  foo: validator(function(value, options, model, attribute) {
    if (model.get('errors').has(attribute)) {
      return model.get(`errors.${attribute}.messages.firstObject`);
    }
    return true;
  }, { dependentKeys: ['errors.foo.messages.[]']})
});

Do I need to use this for each attributes in the model?

it is not working for embedded belongs to and has many relationships..

You have to put your validations on the model that has the errors. You cant validate child on model.child if that makes sense...
On a side note: @blimmer is this the sort of issue you have been facing as well? Would it help to have a validator('ds-error') that handles the dependentKeys and spits out the last error for the given attribute?

@offirgolan that would be helpful - it would be especially helpful if it could identify the model property and mark that invalid (e.g. on a user form, highlight what is invalid like birthdate).

@thiyagu06 v2.5.0 has been released with a new DS Error validator :smile_cat:


Update UUIDs of Services

mapping table:
mappings.txt

config file

Mapped the uuids for all applications except RegistryOffice in the config file. Don't have a mapping for ro-1-0-0 uuids (RO repo already has 2.0.0 uuids)
deleted entries for old invalid uuids from other TAC applications, see attached findings list.

findings_configfile.txt
missing mappings for ro-uuids.txt

After feedback from Iswaryaa updated config file again and only changed uuids for ALT, but not other TAC apps:
•	In ALT data file, other than “alt” control-construct, other control-construct(s) (like RO, TAR, AA, EaTL, OL) they need not be updated for uuid(s) currently since they become a part of Application data and not config data.
•	Updating them here would become a redundant task since these data are already updated in respective application’s repository. So, once we complete all updates in data file, control-construct form other applications can be copied without attributes like operation-key and detailed-logging-is-on.
•	On the other hand, in v2.0.0, current ALT data file would be segregated to config and data files with config file containing profile, ALT control-construct whereas data file will have control-construct data of ALT’s client applications.


Adding Transactions

cc @AshMudra for visibility. Here's what I'm following: https://blog.logrocket.com/django-rest-framework-create-api/, and what I'm going to work on this week.
Setup To Do:

add 'rest_framework' to INSTALLED_APPS
pip install django_rest_framework
pip freeze > requirements.txt  # add django_rest_framework to requirements.txt
create serializers.py in api/bonebudget/..
add path('api-auth/', include('rest_framework.urls')), to api/api/urls.py
python manage.py createsuperuser

Endpoint: bonebudget/transaction/

GET: List all transactions for requested user
POST: Add a new transaction

Endpoint: bonebudget/transaction/<uid:transaction_id>

GET: Retrieve transaction with given transaction_id
PUT: Update a transaction with given transaction_id
DELETE: Delete a transaction with given transaction_id

Models To Do:

Add below to models.Transaction

def __str__(self):
    return self.description

python manage.py makemigrations & python manage.py migrate
Convert Model object to an API-appropriate format using ModelSerializer class. In api/bonebudget/serializers.py:

   from rest_framework import serializers
   from .models import Transaction

   class TransactionSerializer(serializers.ModelSerializer):
       class Meta:
           model = Transaction
           fields = [
               "id", "user_id", "is_credit", "transaction_type", "amount", "posted_date", "status", "description", "created_at", "updated_at"
           ]

Views To Do:

Import:

from rest_framework.views import APIView
from rest_framework.response import Response
from rest_framework import status
from rest_framework import permissions  # authenticated users only
from .models import Transaction
from .serializers import TransactionSerializer

transactions/api/:

Create TransactionView class in api/bonebudget/views.py

class TransactionView(APIView):
    permission_classes = [permissions.IsAuthenticated]

    def get(self):
        pass  # add logic here

    def post(self):
        pass  # add logic here

Create an endpoint for the class-based view in api/bonebudget/urls.py:

import:

from .views import (
    TransactionView,
)

add a url to api/bonebudget/urls.py:

urlpatterns = [
    path('api', TransactionView.as_view()),
]

python manage.py runserver
Navigate to http://<IP_ADDRESS>:8000/transaction/api/ to test.
Try to add a transaction:

{
"description": "barebones buritto",
"is_credit": false,
"amount": 8.0,
"transaction_type": "credit card",
"status": "pending"
}

transaction/api/<uid: transaction_id>:

Create transaction detail view in api/bonebudget/views.py

class TransactionDetailView(APIView):
    permission_classes = [permissions.IsAuthenticated]

    def get_object(self):
    """Helper method"""
        pass  # add logic here

    def get(self):
        pass  # add logic here

    def put(self):
        pass  # add logic here

    def delete(self):
        pass  # add logic here

Add a url to api/bonebudget/urls.py

path('api/<uid: transaction_id>/', TransactionDetailView.as_view()),

Import:

from .views import (
    TransactionView, TransactionDetailView
)

navigate to http://<IP_ADDRESS>:8000/transactions/bonebudget/<transaction_id>/ to test using a valid transaction_id.

Done!


Testing prow jobs

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: roshanirathi
To complete the pull request process, please assign abhinavnagaraj
You can assign the PR to them by writing /assign @abhinavnagaraj in a comment when ready.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

Hi @roshanirathi. Thanks for your PR.
I'm waiting for a spectrocloud member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.
Once the patch is verified, the new status will be reflected by the ok-to-test label.
I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

/test cluster-api-provider-vsphere-static-ip_build

@roshanirathi: Cannot trigger testing until a trusted user reviews the PR and leaves an /ok-to-test message.

In response to this:

/test cluster-api-provider-vsphere-static-ip_build

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

/ok-to-test

@roshanirathi: Cannot trigger testing until a trusted user reviews the PR and leaves an /ok-to-test message.

In response to this:

/ok-to-test

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

/ok-to-test

/ok-to-test

@roshanirathi: Cannot trigger testing until a trusted user reviews the PR and leaves an /ok-to-test message.

In response to this:

/ok-to-test

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

/test cluster-api-provider-vsphere-static-ip_build

@roshanirathi: Cannot trigger testing until a trusted user reviews the PR and leaves an /ok-to-test message.

In response to this:

/test cluster-api-provider-vsphere-static-ip_build

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: roshanirathi
To complete the pull request process, please assign jzhoucliqr, zulfilee
You can assign the PR to them by writing /assign @jzhoucliqr @zulfilee in a comment when ready.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS
prow/OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

/test cluster-api-provider-vsphere-static-ip_image_build

/test cluster-api-provider-vsphere-static-ip_image_build

/test cluster-api-provider-vsphere-static-ip_image_build

@roshanirathi: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

cluster-api-provider-vsphere-static-ip_image_build
1f8030bf8bf2ad4118da50843324b304f8c7481b
link
/test cluster-api-provider-vsphere-static-ip_image_build

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test cluster-api-provider-vsphere-static-ip_image_build

/retest

/test cluster-api-provider-vsphere-static-ip_image_build

@roshanirathi: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

cluster-api-provider-vsphere-static-ip_image_build
a4aa2c2da9d3adb2755156ffb808be30eb107159
link
/test cluster-api-provider-vsphere-static-ip_image_build

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/retest

@roshanirathi: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

cluster-api-provider-vsphere-static-ip_image_build
a4aa2c2da9d3adb2755156ffb808be30eb107159
link
/test cluster-api-provider-vsphere-static-ip_image_build

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test cluster-api-provider-vsphere-static-ip_image_build

@roshanirathi: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

cluster-api-provider-vsphere-static-ip_image_build
2da52348b9a38766b29ee7656d3f0872380e80aa
link
/test cluster-api-provider-vsphere-static-ip_image_build

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/retest

/test cluster-api-provider-vsphere-static-ip_image_build

@roshanirathi: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

cluster-api-provider-vsphere-static-ip_image_build
2da52348b9a38766b29ee7656d3f0872380e80aa
link
/test cluster-api-provider-vsphere-static-ip_image_build

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@roshanirathi: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

cluster-api-provider-vsphere-static-ip_image_build
2da52348b9a38766b29ee7656d3f0872380e80aa
link
/test cluster-api-provider-vsphere-static-ip_image_build

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/retest

@roshanirathi: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

cluster-api-provider-vsphere-static-ip_image_build
2da52348b9a38766b29ee7656d3f0872380e80aa
link
/test cluster-api-provider-vsphere-static-ip_image_build

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/retest

@roshanirathi: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

cluster-api-provider-vsphere-static-ip_image_build
2da52348b9a38766b29ee7656d3f0872380e80aa
link
/test cluster-api-provider-vsphere-static-ip_image_build

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test cluster-api-provider-vsphere-static-ip_image_build

/test cluster-api-provider-vsphere-static-ip_image_build

/test cluster-api-provider-vsphere-static-ip_image_build

@roshanirathi: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

cluster-api-provider-vsphere-static-ip_image_build
8a9d17770e5c5ebe14379189a3ff1ff0837bd3a6
link
/test cluster-api-provider-vsphere-static-ip_image_build

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/retest

@roshanirathi: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

cluster-api-provider-vsphere-static-ip_image_build
8a9d17770e5c5ebe14379189a3ff1ff0837bd3a6
link
/test cluster-api-provider-vsphere-static-ip_image_build

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/retest

/test cluster-api-provider-vsphere-static-ip_image_build

@roshanirathi: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

cluster-api-provider-vsphere-static-ip_image_build
d7538596298c2ac28e7c44a8fb35bc95a4f443e6
link
/test cluster-api-provider-vsphere-static-ip_image_build

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test cluster-api-provider-vsphere-static-ip_image_build

@roshanirathi: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

cluster-api-provider-vsphere-static-ip_image_build
cff3aa6164e52740a00ead94bf7877bbf7246c4f
link
/test cluster-api-provider-vsphere-static-ip_image_build

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test cluster-api-provider-vsphere-static-ip_image_build

/test cluster-api-provider-vsphere-static-ip_image_build

@roshanirathi: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

cluster-api-provider-vsphere-static-ip_image_build
640c8bbe0f34b720b125cc2192b5226b68fea97c
link
/test cluster-api-provider-vsphere-static-ip_image_build

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/retest

@roshanirathi: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

cluster-api-provider-vsphere-static-ip_image_build
640c8bbe0f34b720b125cc2192b5226b68fea97c
link
/test cluster-api-provider-vsphere-static-ip_image_build

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/retest

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: roshanirathi, zulfilee
To complete the pull request process, please assign jzhoucliqr
You can assign the PR to them by writing /assign @jzhoucliqr in a comment when ready.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS
prow/OWNERS [zulfilee]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

/approve

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: roshanirathi, zulfilee
To complete the pull request process, please assign jzhoucliqr
You can assign the PR to them by writing /assign @jzhoucliqr in a comment when ready.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS
prow/OWNERS [zulfilee]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

/lgtm


Rounded amount and correct date format

HI @maassenbas,
paymentAmount is this not already in minor units ?
Notification timeString looks fine.
Are both causing issues with merchants ? Let's push this to SI to include it into certified extension version.
Regards,
Rik
Adyen


remove reshade from readme

reshade support was dropped in 2.3.0 so no reason for it to still be in the readme

oops thanks for pointing that out

your welcome


signal: catch all termination signals by default

In this commit, we modify the primary signal package to instead catch
all signals. Before this commit, it would only catch the interrupt
signal sent from the kernel. With this new commit, we'll now also catch
(or attempt to catch): SIGABRT, SIGTERM, SIGSTOP, and SIGQUIT.

Before this PR, we didn't attempt to catch SIGTERM which is customarily used by systemd to shutdown active services. Many of the raspberry pi guides circulating out there use a ssytemd set up to handle creation/destruction of the lnd process.

expected update reliese anytime soon ?


Instantiation network information

At instantiation time, network information will be required to the user:

Ingress/Egress
Location
Network Attachment Points (network segments)

Done: https://github.com/sonata-nfv/son-bss/pull/83
Pending: adapt the code to retrieve the list of locations from GK API.

Hi, @srodriguezOPT
Can you please paste here an example of the JSON provided to the GK?
Thanks,

Hi @jbonnet
I included an example in http://wiki.sonata-nfv.eu/index.php/D43_BSS_Module#Location_Info

Ha, great, @srodriguezOPT, thanks, I'm reproducing it here, for completeness:
{
  "service_uuid": "8c58b169-7c38-4bcd-9421-a91bd786f1fa",
  "egress": [
    {
    }
  ],
  "ingress": [
    {
      "location": "Aveiro",
      "nap": "<IP_ADDRESS>/32"
    },
    {
      "location": "London",
      "nap": "<IP_ADDRESS>/24"
    }
  ]
}

@srodriguezOPT
Some doubts:
can both egress and ingress be empty?
when empty, can they be like "egress":[] (i.e., without the {} inside)?
when not empty, both location and nap must be present, right?
do we need to store this in the DB, together with the service_uuid (for instance, will the BSS want to search by 'which service instantiation requests were made with ingress location == 'Aveiro')?

@jbonnet:

Yes, they can be empty.
Ok, no problem.
Exactly; when not empty, both fields are mandatory
BSS will not filter by location/nap information. We can include it as part of the requests info, (detailed info) but it's not mandatory. BSS won't use this information

Great, @srodriguezOPT, thanks!

Closed by https://github.com/sonata-nfv/son-bss/pull/83


refactor(Checkbox): redesign javascript invoke improve performance

redesign javascript invoke improve performance
Summary of the changes (Less than 80 chars)
简单描述你更改了什么, 不超过80个字符；如果有关联 Issue 请在下方填写相关编号
Description
fixes #4628
Regression?

[ ] Yes
[ ] No

[If yes, specify the version the behavior has regressed from]
[是否影响老版本]
Risk

[ ] High
[ ] Medium
[ ] Low

[Justify the selection above]
Verification

[ ] Manual (required)
[ ] Automated

Packaging changes reviewed?

[ ] Yes
[ ] No
[ ] N/A

☑ Self Check before Merge
⚠ Please check all items below before review. ⚠

[ ] Doc is updated/provided or not needed
[ ] Demo is updated/provided or not needed
[ ] Merge the latest code from the main branch

Summary by Sourcery
Refactor the Checkbox component to enhance performance by redesigning the JavaScript invocation process, removing unnecessary callbacks, and updating related unit tests.
Enhancements:

Refactor the Checkbox component to improve performance by redesigning the JavaScript invocation mechanism.

Tests:

Update unit tests to reflect changes in the Checkbox component's JavaScript invocation, ensuring correct behavior of the new method.

@sourcery-ai review


Creates new records instead of saving to existing record

Imagine Team has one Coach (one-to-one relationship). On first save in Team, it creates the Coach record. But on each consecutive save, it creates a new coach record instead of saving to the one that's created.
See: http://stackoverflow.com/questions/41653975/silverstripe-single-one-to-one-objects-bug

I did some testing and took one step closer to the issue.
This bug is only in effect when you create multiple has_one relations of the same class type.
class Car extends DataObject {

    private static $has_one = array(
	'Owner' => 'Person',
	'Driver' => 'Person'  // two relations of the same class type
    );
}

This confuses the mod and makes it produce new records on each save rather than saving into the already existing record.
Will see if I can solve the issue in the code. Help and tips are appreciated

I did another test, creating two new pseudo classes that extend Person:

Person_One extends Person
Person_Two extends Person

and changing the Car relation to:
private static $has_one = array(
'Owner' => 'Person',
'Driver' => 'Person'  // two relations of the same class type
);

This does not change the situation: the mod keeps creating new records exactly in the same fashion.

If you didn't it yet, try to use the dot notation with $belongs_to to specify the relation referrals. Take a look to the official doc.


fixing Database.transaction param types

According to docs https://github.com/andregs/arangojs#databasetransaction

Thank you for the PR. For legal reasons we need a signed Contributor License Agreement (CLA) before we can merge your code into the project.
You can download the form from our website: https://www.arangodb.com/documents/cla.pdf
Once you've filled out and signed it, please send it to us via e-mail<EMAIL_ADDRESS>or fax: +49-221-2722999-88.

Done 👍

Thanks for your contribution!


Close Alpha Program with Beta Tease

This commit replaces the claim form and base route with a "closed"
component that announces the end of the Alpha program with a link
to request access to the Beta program.
Screenshot attached:

LGTM


Doesnt work just keeps saying Zoom Join Meeting Not Found onScreen

help

Sure I am here to help you, what version of the zoom client are you using and yes you can change the join-meeting icon by taking a new screenshot of the icon and replacing it

Here is a video show how to bypass it, I made it for you https://youtu.be/VQpo06cs3O4
If you are getting the error that join button is not found, then please log in to a zoom account and then if it still cannot do something then just give it a little help and once it is started it will do the thing

Hope this solves it the image you are taking about, sometimes it does that, but give it a little help and it will do the rest and if still there are issues just replace all the images with the images of these steps on your own PC, and yes do not forget this is STRICTLY FOR EDUCATIONAL PURPOSES ONLY.


Handle getting None arrays back from TileDB Cloud.

When deserializing a notebook listing response from TileDB Cloud, it is possible that the generated client code handles the zero-array case by setting the arrays value to None rather than an empty iterable. This would cause a NoneType is not iterable exception.
I'm not certain if this is the case, but it's a guess.

[sc-53170]


[GSB] Detect self-derived conformances within same-type requirements

Two related fixes for recursive constraints:

More correctly fix SR-5485: we were retaining self-derived conformance
sources when we shouldn't, which led to spurious "redundant
conformance" diagnostics and (much worse) incorrect minimized generic
signatures. Now, when we detect a self-derived conformance source,
return the minimal source that will derive the same conformance... and
retain that one if it's new.
Detect requirement sources that are internally self-derived for
(e.g.) handling of requirement sources for same-type constraints and
superclass constraints. This eliminates some incorrect warnings about
redundant same-type constraints involving recursive protocols, which
(more importantly) were a symptom of incorrect generic signature
minimization. Fixes SR-5473

@swift-ci please smoke test

Still fretting over this failing case:
protocol P5 {
  associatedtype X : P5
    where X.X == X
}

protocol P6 : P5 {
  associatedtype Y : P5
}

extension P6 where X == Y.X { }


Let us mock HTTP Requests in XSD validation

Hello,
I'm using nokogiri in my tests to validate generated XML documents with a schema.
My schems imports namespaces available online, like dublincore's dcterms for example.
As it is intended to do, validating the document makes calls to these namespaces urls. They are, however, not subjected to changes.
And it makes my tests very slow and impossible to run without an internet connection.
Would it be possible to mock these http calls, like I could do with webmock if the calls were made with NET::HTTP ?

Just encountered the same issue. A test suite (that I didn't write) tries to validate a MODS document. The schema definition references external resources, so the test only works with a functioning internet connection. I'd hoped WebMock would make it good, but no luck.

@cwant if you could, please open a new issue with this request, and perhaps a description of how you'd like it to work. it's unlikely i'll have time to work on it, and in all honesty it will likely require hacking the underlying XML engine(s), but I'm open to ideas and definitely open to pull requests.


Migrate build and imports to common-jvm repository import

This change is

src/main/kotlin/org/wfanet/measurement/duchy/deploy/common/daemon/mill/liquidlegionsv2/BUILD.bazel, line 4 at r1 (raw file):
Previously, SanjayVas (Sanjay Vasandani) wrote…

load("@wfa_common_jvm//build/platforms:constraints.bzl", "DISTROLESS_JAVA")

I think this one should stay here and be dropped from wfa_common_jvm. The platforms Bazel package has some dependencies on the RBE configs, which aren't part of common-jvm.

Made the change.

src/main/kotlin/org/wfanet/measurement/gcloud/spanner/testing/BUILD.bazel, line 1 at r1 (raw file):
Previously, SanjayVas (Sanjay Vasandani) wrote…
This whole file should be gone from this repo, as it exists in common-jvm now.
Are you planning on doing all the replacing of targets under /src/main/kotlin in a separate PR? If so, make it clear in this PR description that this is just handling /build and /imports.

I will handle /src/main/kotlin in a separate PR.


Update hotspotsController.js to return ordered list of hotspots

Order hotspots by id when returning all hotspots
This is particularly important for paginating otherwise the pagination will not be consistent across page requests, ie requesting the same page number will return different, random, hotspots

I did test it out in our instance.
Without the explicit order findAll seems to return data in random order and thus the pagination result would also be random, for example if you request page 1 multiple times you get a different set of entries each time.


fix(jest-runner): handle test failures with circular objects

Summary
~Structured clone doesn't handle circular objects seemingly, so I've added telejson which serializes it into a special string that it then restores.~
~It might make sense to make the serializer pluggable?~
Uses advanced serialization for Jest's test worker, and ensuring the assertion error we use can be serialized.
Fixes #10577
Closes #10881

Test plan
E2E test added.

The code looks good to me but I think we should investigate why the structured cloning isn't sufficient. It isn't because of the circular references as my test proofed. The use of telejson is hidding the underlying issue.

The code looks good to me but I think we should investigate why the structured cloning isn't sufficient. It isn't because of the circular references as my test proofed. The use of telejson is hidding the underlying issue.

Agreed, I'll investigate at some point

@MichaReiser I dug a bit more into this, and the issue is that we attempt to send a function over that closes over a variable out of scope. Use this as the worker and it fails:
module.exports = {
  identity() {
    const thing = 'foobar';

    return () => thing;
  },
};

Although it fails with Call retries were exceeded rather than the underlying serialization error.
Concretely in Jest, the issue is the message function we add to errors. This diff "fixes" it..
diff --git i/packages/expect/src/index.ts w/packages/expect/src/index.ts
index e050afe40a..1c6cc45260 100644
--- i/packages/expect/src/index.ts
+++ w/packages/expect/src/index.ts
@@ -293,7 +293,7 @@ const makeThrowingMatcher = (
         // Passing the result of the matcher with the error so that a custom
         // reporter could access the actual and expected objects of the result
         // for example in order to display a custom visual diff
-        error.matcherResult = result;
+        error.matcherResult = {...result, message};

         if (throws) {
           throw error;
diff --git i/packages/jest-worker/src/workers/ChildProcessWorker.ts w/packages/jest-worker/src/workers/ChildProcessWorker.ts
index 6b7daa4758..33b57a1457 100644
--- i/packages/jest-worker/src/workers/ChildProcessWorker.ts
+++ w/packages/jest-worker/src/workers/ChildProcessWorker.ts
@@ -92,6 +92,9 @@ export default class ChildProcessWorker implements WorkerInterface {
       } as NodeJS.ProcessEnv,
       // Suppress --debug / --inspect flags while preserving others (like --harmony).
       execArgv: process.execArgv.filter(v => !/^--(debug|inspect)/.test(v)),
+      // default to advanced serialization in order to match worker threads
+      // @ts-expect-error: option does not exist on the node 10 types
+      serialization: 'advanced',
       silent: true,
       ...this._options.forkOptions,
     });

So  serialization: 'advanced' fixes the circularity error, but introduces a new one (to match worker threads)

@MichaReiser I pushed up a change using advanced serialization in jest-runner instead of changing the default pending #10983. Will probably need to skip the test on node 10

@SimenB would you please release this fix in a new next tag ? For some reasons I only encountered this error while testing ESM, I've never seen this happening to CJS.

@SimenB would you please release this fix in a new next tag ? For some reasons I only encountered this error while testing ESM, I've never seen this happening to CJS.

Not only it resolved the issue on circular objects, it did resolved the problem I encountered while testing with BigInt. Thanks!

Not only it resolved the issue on circular objects, it did resolved the problem I encountered while testing with BigInt. Thanks!

Any idea when this will be available in a npm release?

v27.0.0-next.3 is released now, sorry about the delay

I will have to revert this as any errors thrown in tests containing stuff that cannot be serialized (like a function) will make the test runner crash.
const someString = 'hello from the other side';

test('dummy', () => {
  const error = new Error('boom');

  error.someProp = () => someString;

  throw error;
});

Running this test on its own is fine, but having 2 of them and running in test mode leads to
Error: () => someString could not be cloned.
    at writeChannelMessage (node:internal/child_process/serialization:81:9)
    at process.target._send (node:internal/child_process:822:17)
    at process.target.send (node:internal/child_process:722:19)
    at reportSuccess (/Users/simen/repos/jest/packages/jest-worker/build/workers/processChild.js:67:11)
node:internal/child_process/serialization:81
    ser.writeValue(message);

Out of curiosity, is worker serialization advanced similar to V8 serialize function?

yep. https://nodejs.org/api/child_process.html#child_process_advanced_serialization

Child processes support a serialization mechanism for IPC that is based on the serialization API of the v8 module, based on the HTML structured clone algorithm.

Oh i got exact the error you mentioned above just now
internal/child_process/serialization.js:69
      deserializer.readHeader();
                   ^

Error: Unable to deserialize cloned data due to invalid or unsupported version.
    at ChildProcessDeserializer.readHeader (<anonymous>)
    at parseChannelMessages (internal/child_process/serialization.js:69:20)
    at parseChannelMessages.next (<anonymous>)
    at Pipe.channel.onread (internal/child_process.js:592:18)

Even though it happened randomly.

Yep, that's caused by this PR and why I need to revert it

revert: #11172


Repeated driving order, pickup time missing

Scenario:

create new repeated driving order
the order is not accepted (500 Internal Server Error)

Analysis:

orderTime is missing (null) in DTO

Reported:

TIXIZUG, Monika Rueeg, 08.08.2017

Scenario:

create a new production plan
the same error (as above) occurs (but in a different place)

Screenshot (fatal error in dev-environment):

This has been fixed in commit https://github.com/TIXI24/sfitixi/commit/f920925692c0fa4bab94dc7822bfd500e5db2b91.
The cause is a duplicate order, or overlapping orders, not as first suspected a missing pickup time.
Online error message:

Offline error message (production plan):


TextBuffer.SelectRange() not available

How do I select text in a TextView? The following snippet for selecting all does not work:
func SelectAll(t *gtk.TextView) {
	if t == nil {
		return
	}
	buff, err := t.GetBuffer()
	if err != nil {
		return
	}
	var start = buff.GetIterAtOffset(0)
	var end = buff.GetIterAtOffset(0)
	end.ForwardToEnd()
	buff.SelectRange(start, end)
}

I'm new to GTK3 so maybe I'm missing something obvious. If not, please add the wrapper!

Yes, that function simply wasn't implemented yet. I have added it with commit 770c4e769764890fa0d8a91d6690f9745a757d25.
Check the code, it's rather simple, if you encounter a missing wrapper again, I encourage you to try and add it yourself, we will gladly accept your Pull Requests :)


Include real usecases in documentation - https://docs.microsoft.com/en-us/azure/active-directory/develop/custom-rbac-for-developers

The documentation should include real usecases as well. One of the use case could be:
Lets say, In our platform, We have 2 web applications. Our platform supports multiple organizations. Each organization can have multiple projects.
We want to define authorization access based on "WebApp + OrgName + ProjectName + Role".
For example: user1 has access to "WebApp1 + Org1 (data) + Proj1 (data)" and his role is Modeler. Modeler in WebApp1 can access only certain features in webapp1 (defined in webapp1 code using framework (say spring) specific annotations).
Which approach (out of 3 mentioned in the article) is best for this usecase?
Org and Projects will have more attributes like OrgId, ProjectId respectively. Where to store them and link it with above mapping?

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

ID: 5dc830f1-65af-6a40-c11c-4b394b808b5a
Version Independent ID: 1443081c-71c8-1606-2312-793f89f0b645
Content: Custom role-based access control (RBAC) for application developers - Microsoft identity platform
Content Source: articles/active-directory/develop/custom-rbac-for-developers.md
Service: active-directory
Sub-service: develop
GitHub Login: @Chrispine-Chiedo
Microsoft Alias: cchiedo

@CatchSandeepVaid
Thanks for your feedback! I've assigned this issue to the author who will investigate and update as appropriate.

Thanks @CatchSandeepVaid for sharing your feedback! A work item has been opened for this issue and it's going to be prioritized accordingly.
#please-close


duplicate imports in CrawlController

i guess you first cleaned up/moved imports:
https://github.com/yasserg/crawler4j/commit/6ffe56b42c2b045c856455ca21302bbce5e38b0c
then you did a merge, and pulled the moved imports back in, ending up with duplicates:
https://github.com/yasserg/crawler4j/blob/master/src/main/java/edu/uci/ics/crawler4j/crawler/CrawlController.java#L20-L25
and
https://github.com/yasserg/crawler4j/blob/master/src/main/java/edu/uci/ics/crawler4j/crawler/CrawlController.java#L39-L44

I guess this is fixed?  @yasserg Can you close it?


[BE][DATA_PROVISIONING] Update of Jobdetailresponse for handling Tombstones from IRS

As a developer
I want to extend the jobdetailresponse to read tombstones from IRS and save them
so that the system can accurately handle tombstone data retrieved from IRS
Hints / Details
See concept: Catena Concept
Acceptance Criteria

[ ] AssetAsBuilt and AssetAsPlanned have been extended by a string which reflects a tombstone payload and will be saved into database
[ ] Jobdetailresponse has been extendend to read tombstones from IRS and save them

Out of Scope

...

:no_entry: is blocked by #414

prerequisite to #416

FE Concept regarding how to show a tombstone is needed

@jzbmw

Red border is just there to show whats new, not in implementation.
Changed Icon to error color, here is the implementation:

For Alignment with BE:
partsAsBuilt as partAsPlanned is extended and expects a string field "tombstone" in the part response (for each part which is a tombstone). The FE expects a string which is JSON parsable, which has the following structure (from jobResponse.json in IRS):
	{
		"catenaXId": "urn:uuid:68c9b1bf-b2c1-456a-883c-2aac5f5cb5f4",
		"endpointURL": null,
		"processingError": {
			"processStep": "BpdmRequest",
			"errorDetail": "Cannot find ManufacturerId for CatenaXId: urn:uuid:68c9b1bf-b2c1-456a-883c-2aac5f5cb5f4",
			"lastAttempt": "2022-11-08T08:37:18.724609316Z",
			"retryCounter": 0
		}
	}

@ds-alexander-bulgakov ready for review for the FE part, thanks!

Hi,
after implementation on BE i would need to test the FE part anyways so i would prefer to test the ticket after the whole implementation was done. Therefore the ticket was moved to "next" for BE part to be implemented. Thank you!

[ ] AssetAsBuilt and AssetAsPlanned have been extended by a string which reflects a tombstone payload and will be saved into database
[ ] JobDetailresponse has been extended to read tombstones from IRS and save them
[ ] Response should be aligned with FE (See comments)

Hi @ds-lcapellino short question. What happens if we have an asset with a tombstone. Afterwards we will reload the registry and the tombstone is gone. Will the tombstone be removed from the asset?

Hi @ds-mwesener,
as you can see from the below code snippet, the tombstone value is always set for existing assets. If there was an tombstone in the database, but it has been resolved in the next try, then the tombstone value should be set to null again:

Perfect thank you!

No issues could be found on BE side. Tombstones are saved to new column for each asset and can be consumed by the FE as expected. Assets with tombstones are overwritten and tombstones are deleted if they don´t appear for existing assets with new registry reload. This was tested with manual changes in the database.
On FE-side however there are following questions to clarify, @jzbmw please have a look:

What status is expected for assets with tombstones, ERROR or no special status change is requested?
Currently assets which could not be found in the DTR are displayed in the FE with status ERROR, without the tombstone sign and without any data:

It is possible to create quality-alerts for UNKNOWN assets in status ERROR:

however quality-investigations can not be created due to error message "Backend returned code undefined: Please try again later." in the FE. IMO we should not allow creation of investigations or alerts at all if we want to keep the UNKNOWN-assets in the FE.

Since @jzbmw is in vacation could you @mkanal please support on my questions?

Tombstone are displayed correctly. Verified on Dev with Jaro.


Fix iPad Tests for iOS 10.0.

Fixes https://github.com/google/EarlGrey/issues/239

Holding off on this until all the tests are green for the keyboard. This also requires a small refactor in our Touch Injector.


ASAN Failure in Darwin

Problem
https://github.com/project-chip/connectedhomeip/runs/4927166170?check_suite_focus=true
2022-01-24 19:52:18.586 ERROR   19:52:15.156 - APP  ERR  : ==9163==ERROR: AddressSanitizer: SEGV on unknown address 0x000267000048 (pc 0x7fff204b2623 bp 0x70000e9c9050 sp 0x70000e9c8e78 T1)
1098

Proposed Solution
Fix it

I suspect https://github.com/project-chip/connectedhomeip/pull/14390 fixed this.


Remove unused modal outlet

no issue

leftover from the modals refactor, because of how modals work now this isn't really needed

/cc @kevinansfield

:+1: good :fishing_pole_and_fish:


Crash with / + paste in the log view, on MacOS

To reproduce, on MacOS

select a container
go see the log
type '/'
type cmd-V

instant crash

Hey @thomasd3, I have not been able to reproduce the crash following these steps. Can you provide any additional information?

I tried to make it happen again and it wouldn't crash. So it looks like I had something in the clipboard that caused the crash. I just tried unicode characters and that's not it, I also tried a picture and it wouldn't crash either.


Added visionos support

Support for the Apple Vision Pro was added as a tier 3 target with a targe_os of visionos to rust in https://github.com/rust-lang/rust/pull/121419. Needs https://github.com/rust-lang/libc/pull/3568 to do proper build for the target aarch64-apple-visionos-sim or aarch64-apple-visionos.
This is basically the same changes as #190 but with another target_os.

Thank you


Add CSV support for TestResults

This PR makes it possible to run benchmarking with results aggregation (by LOAD_PREV_RESULTS=1) using CSV instead of Excel.

Hello @PokhodenkoSA! Thanks for updating this PR. We checked the lines you've touched for PEP 8 issues, and found:

In the file sdc/tests/tests_perf/test_perf_utils.py:

Line 236:1: E302 expected 2 blank lines, found 1

@PokhodenkoSA ,
Could you please add benchmark result's dump to html in current PR?


add pip3 config set global.break-system-packages true for non-venv installs

also cehrry-picked into v1.11 branch


update clinical-reasoning and incorporate refactoring

updated the import for FhirModelResolverCache based on https://github.com/cqframework/clinical-reasoning/pull/486/files#diff-acaa5ffc23555ca812a16d78ec3a31f0f0e3c58e3a03ed2869549ab2be156390


Subpartitioning: Fixes handling of split physical partitions

Pull Request Template
Description
Bug where SDK would get hung up on ChangeFeedIterator and Query if one prefix partition key spanned multiple physical partitions is now fixed.
Type of change
Please delete options that are not relevant.

[] Bug fix (non-breaking change which fixes an issue)

Closing issues
To automatically close an issue: closes #3865

@msftbot wait to merge until @kirankumarkolli and @ealsur approve


Umbrella header 'ActiveLabel-umbrella.h' not found

this happens suddenly. I did work for a time but now it does not. I am using the Mainbranch, cocoa pods 1.1.1 and Swift 3.

What's in your Podfile? Are you opening the xcworkspace?

Hey @poolqf I can +1 this. module ActiveLabel.Swift {     header "ActiveLabel-Swift.h" }
which in turn doesn't let me import ActiveLabel
Any fix? I am using the latest version on the master branch

@poolqf  pod 'ActiveLabel', yes i always used xcworkspace.
@JPROFFICIAL
i imported the code directly without cocoa pods, that made it work.


fix: Explicitly set DNS resolver during first boot

This is a potential fix for issue #34; it explicitly adds GCE metadata endpoint as the DNS, at least until overridden by DO.

Thanks Matt (@memes ) for your PR.


[CELEBORN-1026] Optimize registerShuffle fallback log

What changes were proposed in this pull request?
Why are the changes needed?
According to https://github.com/apache/incubator-celeborn/pull/1955 , when celeborn is not available, spark.dynamicAllocation.enabled=true and  spark.shuffle.service. enabled=true, shuffle data should not be lost.
Does this PR introduce any user-facing change?
How was this patch tested?

Merge to main/0.3


Port debris generator from downstream

Because I don't feel like doing it myself. :HECK:
https://github.com/moonheart08/outer-rim-14/tree/asteroid-gen contains support for procedurally generating space rocks and debris, which could be wired up to salvage as a way to generate an endless supply of rocks and ruins.
As SS14 doesn't currently have ore, you'll want to exclusively use debris made with ScrapyardPopulator. (or wait for me to port ores)

From TestDebris2


Add no-only-tests plug-in and rule

To catch bugs of the kind I was trying to prevent in: https://github.com/liferay/liferay-amd-loader/pull/189
As a follow-up, will be able to update that repo to use the next release of eslint-config-liferay, and then I can drop that PR.

Internal ticket: https://issues.liferay.com/browse/IFI-530

Going to merge this directly as it was kind of "approved" already in liferay-amd-loader.


Adversarial images should be normalized before merging them with the original images

It's crucial to have the same distribution with the original data.

closed https://github.com/melihcatal/advsecurenet/commit/817d07512a277fe4418e1ff879a4475659e22db9


feat: include sourcemap & changelog in package contents

This PR fixes the warning/error that people using create-react-app were seeing about failing to load a source map.

[ ] I've added a unit test to test for potential regressions of this bug.
[ ] The changelog has been updated, if applicable.
[x] Commits in this PR are minimal and have descriptive commit messages.

Why is the changelog added too?

Why is the changelog added too?

@NSeydoux because it's useful to have when you're debugging a change, you've upgraded, and that gives you the code, the readme, and the recent changes


heading token content is always the last heading

The content for block_token.Heading gets har
import mistletoe
from mistletoe import Document

markdown_text = """
## Heading A
Some text under heading 1.
## Heading B *italic*
Some text under heading 2.
## Heading C **bold**
Some text under heading 3.
"""

# Parse the Markdown text

doc = Document(markdown_text)

for token in doc.children:
    if isinstance(token, mistletoe.block_token.Heading):
        # heading_content = " ".join(str(child.content) for child in token.children if hasattr(child, 'content'))
        heading_content = token.content
        print(f'Level: {token.level}, Content: {heading_content}')

will output
Level: 2, Content: Heading C **bold**
Level: 2, Content: Heading C **bold**
Level: 2, Content: Heading C **bold**

Hi @clehene, thanks for the report. For elements like BlockCode or HtmlBlock, the content property/attribute makes sense (see #163). For others, like Heading, not so much.
As you are not the first to ask this question (see #99), I think the simplest thing to do now is to rename the reported Heading's content class attribute to _content, so that it is clear that it is not a part of the public API. That would be in-line e.g. with _open_info in the CodeFence token class.
I can also imagine we could introduce a getter property called text or similar that would recursively concat text from the child tokens, but that would be for another feature request...


Limit on ChannelGet/ChannelPut operations?

I was working on https://github.com/Xilinx/mlir-air/pull/642 (which is not ready to merge) and I started to see some behavior I didn't understand. So I tried to make a minimal example and I likewise have some unexpected behavior.
The example I came up with uses somewhat ridiculous things like tiny 1x1 data tiles to make it really obvious to me what was going on in the output. I found that my example fails for a 32x16 image and even an 8x8 image, but it is successful for a 4x4 image.
My example is here. It's not supposed to pass the python test harness, I've just been looking at the output to see what it's doing.
As usual, you can run with:
make clean && make

When it fails, it seems like no output is received (the output stays the original value of 0xFFFFFFFFs in the test harness). When it succeeds, each value in the output image is increasing by 2, e.g. for the 4x4 image,
0000 0002 0004 0006
0008 000a 000c 000e
0010 0012 0014 0016
0018 001a 001c 001e

Because it only works for small images, I'm guessing I'm running into a limit on the number of channel operations/copies allowed at some point, but I have not yet confirmed this theory.
In submitting this issue I'm hoping to discover:

Is this expected behavior when using many ChannelGet/ChannelPut ops? If so, what is the limit (and is there a way to catch it before a programmer runs into trouble?)
If it's not expected behavior, maybe a bug fix?

I don't think this is a great minimal example, so I'm closing it for now until/unless I find similar behavior in a simpler example.


How to get historical market data during the backtesting process

I want to obtain historical prices, trading volumes and other market data before the current time point during the backtesting process to help me post new orders or cancel orders at the current moment. How can I obtain historical market data during the backtesting process?

You'll need to store past values manually. For example, if you're working with time-series data for prices at specific intervals, you should record these values in an array or list. Here’s an example that might help.

您好，您的来信我已收到祝好~

Thanks for your help, this is very useful!


internal/trace: reduce if statement

Since "if ev.Type == EvGoSysExit" must be executed,
use if-elsif to reduce the other if statement in the case of "ev.Type == EvGoSysExit"
when assigning to ev.P.

w00ps. I approved this by accident. How can I remove my approval?


Flutter flake bot fails silently

Three flake APIs are scheduled to run on Weds morning, and API /api/file_flaky_issue_and_pr?threshold=0.02 sometimes failed silently. Some potential actions to improve:

add alerts when API fails
schedule these three APIs at different time (now all are at same hour:min, and increase the chance to hit github API limit error)

Context: https://github.com/flutter/flutter/issues/105265

Setting up a common alert for these API failures when hitting the secondary rate limit error: https://console.cloud.google.com/monitoring/alerting/policies/10132480391958018956?project=flutter-dashboard

And APIs have been updated to run at different times. Closing as resolved.


Some small fixes and more addition of info

I've made some punctuation fixes to clarify understanding by readers. Also, I added some more information, including a link with real statistics.

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the master branch of freeCodeCamp.
[x] None of my changes are plagiarized from another source without proper attribution.
[x] My article does not contain shortened URLs or affiliate links.

If your pull request closes a GitHub issue, replace the XXXXX below with the issue number.
Closes #XXXXX

Thank you for your contribution to the page! 👍
We're happy to accept these changes, and look forward to future contributions. 🎉


Rekindle collaboration?

I have been added as a collaborator to https://github.com/alexplumb/material-ui-phone-number/
I think you might as well retain this package since you appear to be working on it and can maintain your deployment agility with your own npm package etc.. But, do you have interest in syncing up again from time to time?
-Ben

Hi Ben - Glad to hear it. I'm happy to help in any way I can, whether that means working all together on material-ui-phone-number or maintaining the two separate repos and syncing up frequently. From my standpoint I think either could work, as the only real changes that differentiate this repo are currently SSR and TS support. Thoughts?

My suggestion would be  for us to sync up as much as possible
I'm also open to converting all the js to ts/tsx as long as @alexplumb  is ok with it? Will open an issue there,

Hey @bherila and @alexplumb. Apologies for the lack in communication the past few weeks, as I've been a bit busy. As stated above, I'm open to coordinating, but the more I think about it, I think it might be more beneficial to users of both packages to combine the work from mui-phone-input-ssr (SSR-support, TS, formatting changes) into material-ui-phone-number. Would you both be open to that? I would also be happy to join as a maintainer of material-ui-phone-number and lend a hand to the ongoing work there. Thoughts?

Hi @braxex I am definitely open to it! However I don't have permissions on the underlying npm package so we'll need @alexplumb  to help with release
I'm a bit underwater at work this week but will take a look at the open PRs this weekend!

Happy to have it all merged into one (and for the codebase to be updated to ts)

@alexplumb Sounds great. I'll plan on directing users of the other repo back here. Would you be willing to add me as a collaborator? I'd be happy to lend a hand with issues and future updates.


Add support for using namespace scoped role resources

Motivation
In restricted k8s environments (such as Openshift), it is a common practice to limit admin access to a namespace scope.
Currently it's not possible to deploy the helm chart with namespace admin access since non-namespace scoped resources such as ClusterRole and ClusterRoleBinding are used. The solution is to use namespace level Role and RoleBinding resources.
Modifications

Add RBAC configuration to values.yaml

# RBAC resource configuration
rbac:
  # create ClusterRole/Role and ClusterRoleBinding/RoleBinding resources
  create: true
  # use ClusterRole and ClusterRoleBinding resources when set to true
  # use namespaced Role and RoleBinding resources when set to false
  clusterRoles: true

Use .Values.rbac.create and .Values.rbac.clusterRoles in the resource templates which create the RBAC resources

Conditionally use ClusterRole / Role and ClusterRoleBinding / RoleBinding
Skip RBAC configuration when .Values.rbac.create isn't set

There's a remaining issue to solve before merging the PR.
There's a remaining issue with developer account on Openshift.
Steps to reproduce issue:
oc new-project pulsar   --description="pulsar" --display-name="pulsar"
oc adm policy add-role-to-user admin developer
oc login -u developer -p developer https://api.crc.testing:6443

cloning the helm chart with experimental changes (including this PR)
git clone -b lh-openshift-experiment-2021-06-30 https://github.com/lhotari/datastax-pulsar-helm-chart
cd datastax-pulsar-helm-chart/helm-chart-sources/pulsar
helm install pulsar -f ../../examples/dev-values-simple.yaml .

This results in this error
Error: roles.rbac.authorization.k8s.io "pulsar-function" is forbidden: user "developer" (groups=["system:authenticated:oauth" "system:authenticated"]) is attempting to grant RBAC permissions not currently held:
{APIGroups:[""], Resources:["configmaps"], Verbs:["*"]}
{APIGroups:[""], Resources:["pods"], Verbs:["*"]}
{APIGroups:[""], Resources:["secrets"], Verbs:["*"]}
{APIGroups:[""], Resources:["services"], Verbs:["*"]}
{APIGroups:["apps"], Resources:["statefulsets"], Verbs:["*"]}

The role used for the service account of the Pulsar Functions k8s runtime has too wide permissions.
Current permissions
rules:
- apiGroups: [""]
  resources:
  - services
  - configmaps
  - pods
  - secrets
  verbs:
  - '*'
- apiGroups:
  - apps
  resources:
  - statefulsets
  verbs:
  - '*'

I guess it makes sense to merge this PR although it doesn't directly solve the Openshift namespace level admin use case.
I found a workaround for that use case which depends on this PR.
By using a command line tool called yq it's possible to extract the RBAC resources so that a cluster admin can create those resources before the Pulsar deployment is made.
This is possible is rbac.create is set to false in the values.yaml. It's also possible to specify rbac.clusterRoles=false to use namespace level roles & bindings. However in Openshift, the roles and bindings will have to be created by the admin.
The yaml file to send to the admin for creation can be generated with helm template and yq:
for example
helm template pulsar -f ../../examples/dev-values-simple.yaml --set rbac.create=true . | yq e '. | select(.kind == "Role" or .kind == "RoleBinding" or .kind == "ServiceAccount")' - > pulsar_rbac.yaml

it's also possible to directly apply the config by piping to kubectl apply:
helm template pulsar -f ../../examples/dev-values-simple.yaml --set rbac.create=true . | yq e '. | select(.kind == "Role" or .kind == "RoleBinding" or .kind == "ServiceAccount")' - | kubectl apply -n pulsar -f -

the problem mentioned in comment https://github.com/datastax/pulsar-helm-chart/pull/18#issuecomment-871337049 has been addressed for the Pulsar Functions and Pulsar Heartbeat RBAC .
A problem remains with Burnell RBAC. Burnell is not currently compatible with namespaced scoped access roles because of logic to create namespace https://github.com/datastax/burnell/blob/3b813954ec7c27bfcd94ad1ca37a5fb1f0014c51/src/k8s/clientset.go#L188-L225 .

Burnell RBAC revisited in this commit: https://github.com/datastax/pulsar-helm-chart/pull/18/commits/747693b921e8e058127a673eb1e9d5d8a8017f11 .
The namespace create access hasn't been granted. It shouldn't be needed for running Burnell when the namespace exists. (How could it ever not exist?)


fix(load-test): Stop creating redhat-appstudio-registry-pull-secret in user namespace

Description
With #482 the redhat-appstudio-registry-pull-secret secret is created (and set to the value of QUAY_TOKEN variable) by the e2e framework automatically, so when the load test attempts to create the secret, it fails for "already exist" reason.
This PR:

Removes the step to create redhat-appstudio-registry-pull-secret secret
Removes use of the DOCKER_CONFIG_JSON environment variable that was used to set the above secret

Issue ticket number and link
Type of change

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

How Has This Been Tested?
In OpenShift CI: https://prow.ci.openshift.org/view/gs/origin-ci-test/pr-logs/pull/openshift_release/40331/rehearse-40331-periodic-ci-redhat-appstudio-e2e-tests-main-load-test-max-concurrency-basic/1669345903418281984
Checklist:

[x] I have performed a self-review of my code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] I have added meaningful description with JIRA/GitHub issue key(if applicable), for example HASSuiteDescribe("STONE-123456789 devfile source")
[ ] I have updated labels (if needed)

/retest

/retest

/retest


Update Jess' post to use 'Zoo' and 'ZMA'

Just updating to Zoo wherever I come across it, first this post that refers to the company as KittyCAD. Although I don't know if we should update many other posts, they are kind of a historical record of who we were?
This one seemed like it wasn't altering the timeline too much, and is talking about things that are actively relevant today. If you agree @jessfraz I can also update "Why we're building KCMA" in the same manner, plus add a redirect on the website side.

good call!

Companion PR to add a redirect since I took "KCMA" out of the URL in @Irev-Dev's post: https://github.com/KittyCAD/website/pull/1559


Support for WASM with EMSCRIPTEN

Hello! I'm playing with WASM through EMSCRIPTEN and decided to test the library to it 😄
Most of the changes are to the CMake file to get the right flags to the compiler.
Limitations
There are two big limitations though:

Fenster is not supported as that would require a WebGL/WebGPU context to render
OpenMP is not working. More info in the CMake file, but the short story is that the OpenMP library was recently ported and the lib is not included by default with the compiler (I might try later to compile it and link it, but probably won't commit it as that'll be a big change)

Results
From running in my Chrome browser, I get the next numbers (MT numbers are wrong as OpenMP is not enabled):
tiny_bvh version 0.7.2 performance statistics (emcc 3.1 build)
----------------------------------------------------------------
BVH construction speed
warming caches...
- reference builder:  405.86ms for  152292 triangles - 249218 nodes, SAH=96.91
- fast AVX builder:   131.31ms for  152292 triangles - 248966 nodes, SAH=96.87
- HQ (SBVH) builder: 2948.63ms for  152292 triangles - 272018 nodes, SAH=94.88
BVH traversal speed
- CPU, coherent,   basic 2-way layout, ST:   5774.2ms for   7.68M rays =>   1.33MRay/s
- CPU, coherent,   alt 2-way layout,   ST:   5687.8ms for   7.68M rays =>   1.35MRay/s
- CPU, coherent,   soa 2-way layout,   ST:   6355.1ms for   7.68M rays =>   1.21MRay/s
- CPU, coherent,   basic 2-way layout, MT:   5564.1ms for   7.68M rays =>   1.38MRay/s
- CPU, coherent,   2-way, packets,     MT:   1318.4ms for   7.68M rays =>   5.83MRay/s
- CPU, coherent,   2-way, packets/SSE, MT:   1082.2ms for   7.68M rays =>   7.10MRay/s
Optimizing BVH... done (9.10s). New SAH=87.76
- CPU, coherent,   2-way optimized,    ST:   6000.2ms for   7.68M rays =>   1.28MRay/s
- CPU, incoherent, basic 2-way layout, MT:  11005.1ms for   7.68M rays =>   0.70MRay/s

How to compile and run

Download the EMSCRIPTEN compiler here
Start a terminal with the emsdk environment (For Windows emsdk\emsdk.bat activate latest)
Configure CMake, e. g.: emcmake cmake -S . -B ./build/web -G "Ninja Multi-Config" -Demcc_threads=ON -Demcc_proxy_main=ON
Build with:  cmake --build .\build\web\ --config Release
Use a HTTP server for testing. E. g. with this: python custom-http.py -d .\build\web\Release\
Go to localhost:8000 and click a HTML page to test 😄

Looks good to me! I didn't do the CMake support myself so that's a bit harder to assess; I trust the CMake guy will jump in if anything needs refinement there.

Okok, thanks! 😄

Well, it took me more than expected to get OpenMP working, but here is the data
tiny_bvh version 0.8.0 performance statistics (emcc 3.1 build)
----------------------------------------------------------------
BVH construction speed
warming caches...
- reference builder:  431.77ms for  152292 triangles - 249218 nodes, SAH=96.91
- fast AVX builder:   135.89ms for  152292 triangles - 248966 nodes, SAH=96.87
- HQ (SBVH) builder: 3089.17ms for  152292 triangles - 272018 nodes, SAH=94.88
BVH traversal speed
- CPU, coherent,   basic 2-way layout, ST:   6040.9ms for   7.68M rays =>   1.27MRay/s
- CPU, coherent,   alt 2-way layout,   ST:   5923.9ms for   7.68M rays =>   1.30MRay/s
- CPU, coherent,   soa 2-way layout,   ST:   6638.6ms for   7.68M rays =>   1.16MRay/s
- CPU, coherent,   basic 2-way layout, MT:   1210.9ms for   7.68M rays =>   6.34MRay/s
- CPU, coherent,   2-way, packets,     MT:    216.0ms for   7.68M rays =>  35.56MRay/s
- CPU, coherent,   2-way, packets/SSE, MT:    163.0ms for   7.68M rays =>  47.13MRay/s
Optimizing BVH... done (9.90s). New: 272017 nodes, SAH=87.76
- CPU, coherent,   2-way optimized,    ST:   6287.2ms for   7.68M rays =>   1.22MRay/s
- CPU, incoherent, basic 2-way layout, MT:   1402.6ms for   7.68M rays =>   5.48MRay/s

So 84% time reduction for the best MT case 😄 1082.2ms -> 163.0ms

Very nice! Will you make a new pull request?

I don't think so. I would need to change the cmake to pull the llvm project (quite massive), which would defeat the tiny part hehe.
I made a script that compiles it for me at https://github.com/maniatic0/wasm-win-openmp-fix. Also, I use this envar to make it link against the test targets set CXXFLAGS=-I<OpenMP_Build>\build\include <OpenMP_Build>\build\lib\libomp.a -fopenmp=libomp

Mmm, maybe I could add precompiled versions if you think it's alright

Hm I can also link to your repo for those interested; precompiled LLVM
binaries is perhaps still a bit too much.

Jacco.

On Fri, Nov 15, 2024 at 10:03 PM Christian Oliveros <
@.***> wrote:

Mmm, maybe I could add precompiled versions if you think it's alright
—
Reply to this email directly, view it on GitHub
https://github.com/jbikker/tinybvh/pull/18#issuecomment-2479918272, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AFH3PEDIGF7RJWI47BJ425L2AZOQRAVCNFSM6AAAAABRU4H5QCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINZZHEYTQMRXGI
.
You are receiving this because you modified the open/close state.Message
ID: @.***>


Compilation broken

[  8%] Building CXX object code/Modules/Core/CMakeFiles/Core.dir/App.cc.o
In file included from /home/mgerhardy/dev/oryol/code/Modules/Core/App.cc:5:
In file included from /home/mgerhardy/dev/oryol/code/Modules/Core/App.h:36:
In file included from /home/mgerhardy/dev/oryol/code/Modules/Core/Args.h:31:
In file included from /home/mgerhardy/dev/oryol/code/Modules/Core/Containers/Array.h:35:
In file included from /home/mgerhardy/dev/oryol/code/Modules/Core/Containers/elementBuffer.h:22:
In file included from /usr/bin/../lib/gcc/x86_64-linux-gnu/6.1.1/../../../../include/c++/6.1.1/new:40:
In file included from /usr/bin/../lib/gcc/x86_64-linux-gnu/6.1.1/../../../../include/c++/6.1.1/exception:171:
In file included from /usr/bin/../lib/gcc/x86_64-linux-gnu/6.1.1/../../../../include/c++/6.1.1/bits/nested_exception.h:40:
In file included from /usr/bin/../lib/gcc/x86_64-linux-gnu/6.1.1/../../../../include/c++/6.1.1/bits/move.h:57:
/usr/bin/../lib/gcc/x86_64-linux-gnu/6.1.1/../../../../include/c++/6.1.1/type_traits:337:39: error: use of undeclared identifier '__float128'
    struct __is_floating_point_helper<__float128>

cmake -G "Unix Makefiles" -DCMAKE_BUILD_TYPE=Debug -DFIPS_CONFIG=linux-make-debug -DFIPS_USE_CCACHE=OFF -DFIPS_AUTO_IMPORT=ON -B/home/mgerhardy/dev/fips-build/oryol/linux-make-debug -H/home/mgerhardy/dev/oryol
-- The C compiler identification is Clang 3.9.0
-- The CXX compiler identification is Clang 3.9.0
-- Check for working C compiler: /usr/bin/cc
-- Check for working C compiler: /usr/bin/cc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Detecting C compile features
-- Detecting C compile features - done
-- Check for working CXX compiler: /usr/bin/c++
-- Check for working CXX compiler: /usr/bin/c++ -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Detecting CXX compile features
-- Detecting CXX compile features - done
CMAKE_BUILD_TYPE: Debug
FIPS_ROOT_DIR: /home/mgerhardy/dev/fips
FIPS_PROJECT_DIR: /home/mgerhardy/dev/oryol
FIPS_DEPLOY_DIR: /home/mgerhardy/dev/fips-deploy
FIPS_AUTO_IMPORT: ON
Host system: Linux
CMAKE_CXX_COMPILER_ID: Clang
Detected C++ Compiler: Clang (FIPS_CLANG)
FIPS_CONFIG: linux-make-debug
Target Platform: Linux
C++ exceptions are disabled
C++ RTTI is disabled
-- Looking for clock_gettime in rt
-- Looking for clock_gettime in rt - found
FIPS_PLATFORM: Linux
FIPS_PLATFORM_NAME: linux

https://llvm.org/bugs/show_bug.cgi?id=13530

Blargh. I was wondering whether it was caused by a compiler update since it's still compiling fine on travis.ci and on my local machine (with gcc 4.8.4).
As far as I can see fips doesn't use 'gnu++11' but simply '-std=c++11' though (see here: https://github.com/floooh/fips/blob/master/cmake-toolchains/linux.cmake#L52).
I'll try to get a clang 3.9 setup on Linux working to reproduce the problem in the evening, so far I've always been using gcc 4.8 on Linux (should update that too I guess).
Thanks!

btw. -D__STRICT_ANSI__ doesn't work :(
so maybe my only chance is to not use clang for compilation, but stick to gcc... But maybe you have some other ideas that might help. If not, just close this with - "use gcc for libstc++ versions that are compiled with gcc extensions".

I'll first try to reproduce the problem and see if I can find a not-too-hacky solution I guess :)

PS: did you recently switch to clang from gcc? The ticket you linked is fairly old (2013), or was the problem caused by updating to clang 3.9?

No, I am using clang for everything else on this machine.

Ok I found the culprit. I had to force undefine STRICT_ANSI for PNaCl, but did this for all POSIX platforms. I have now added this:
https://github.com/floooh/oryol/blob/master/code/Modules/Core/posix/precompiled.h#L14
This works for me now on Ubuntu Mate 16.04 when switching between gcc-5 and clang-3.8
I also had to do a similar fix in oryol-tbui.


Docs

get_dependencies command on CLI
dependencies & create_archive docs

Coverage decreased (-0.1%) to 93.105% when pulling e8a810ac4c7a04867cb2f9ff4b2cab2f61f92029 on docs into ea5a2c4c56979f79feeeec91b6584d49bc6959ac on staging.


[ASK] Max Items in Feed

What is parameter / command for displaying Max Items in Feed?
Thanks

If you want the number of items that a specific bridge returns, you'll have to check in the bridge code. There is no specific variable holding that information

Let's say i'm taking the twitter bridge at https://bridge.suumitsu.eu/ . What parameter should i type to display the number of items specifically?

The total number of items is not customizable for this bridge, as the bridge is generating its content from the base page, containing only 20 tweets.

Very-well! Thanks. Really appreciate your help.
Is there any way to get twitter rss with customizable number of items?

Might be difficult, as you would need to fetch the other tweets through the network.
What number of tweets would you like to be able to fetch, for example ?

10 is enough :)

Well you already have 20.
If you want less, you could just increment a variable and break when the value's 10.


HDDS-3653. Add documentation for Copy key command

What changes were proposed in this pull request?
Add a documents for cp key command
What is the link to the Apache JIRA
https://issues.apache.org/jira/projects/HDDS/issues/HDDS-3653
How was this patch tested?
Just documents debt. no need to test

@elek Please take a look at this documents, it would be better if land this in 0.6.0 release.


MJDEPS-9 Introduce named property for failOnWarning

Introduce jdeps.failOnWarning named property to support command line and <properties> declarations.
https://issues.apache.org/jira/browse/MJDEPS-9

Was addressed on https://gitbox.apache.org/repos/asf?p=maven-jdeps-plugin.git;a=commit;h=77bbb583496c9dc83d2e69f84ba87ea19b665be4


Text component's mode property's binding icon is not vertically aligned

Duplicates

[X] I have searched the existing issues

Latest version

[X] I have tested the latest version

Steps to reproduce 🕹
Reference screenshot from the new UI revamp:

To fix this we will change how these property controls work. We will equip each of them with a bindingButton property that can except a React node. Then let the property control decide where the icon must be rendered.

/attempt

/attempt #2929


Fonts should be packaged next to the image

Currently BrGlamorousFonts contains fonts on the class side. The data for each font is compiled as a method. Currently due to a bug in Iceberg (pharo-vcs/iceberg#1328) using releaser fails on Linux.
Now we have the gt-extra mechanism for packaging  files, and we can use it for fonts.

I think we can close this one for now. Or?


fix: typo

fixes a typo.

Description

see above.
Motivation and Context

it's not solving anything actually. i'm not sure if anyone needs this change. but yea, it fixes a typo.
How Has This Been Tested?

by just reading the README.md file maybe? idk.
Screenshots (if appropriate):
yes, sure, why not? there you go:

Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[x] none of the above

Author's Checklist:

[ ] My code focuses on the main motivation and avoids scope creep.
[ ] My code passes current tests and adds new tests where possible.
[ ] My code is SOLID and DRY.
[ ] I have updated the documentation as needed.
[x] i.. i don't know. i guess it kind of covers the last item. or maybe not.

Reviewer's Checklist:

[ ] I kept my comments to the author positive, specific, and productive.
[ ] I tested the code and didn't find any new problems.
[ ] I think the motivation is good for the project.
[ ] I think the code works to satisfies the motivation.

Nice!

That's a no then.
Thanks!

Sorry, I thought I hit merge.  PR's are welcome, as well as imperfection.

Ah, I was so sad after I prepared this lovely PR report saw that it was closed :P
Thanks a lot!
BTW: I'm a huge fan of this work, will definitely use it in one of my next projects.

Sorry for the sadness, I hope I've turned everything around.  I look forward to more contributions in the future!

BTW: I'm a huge fan of this work, will definitely use it in one of my next projects.

Ty!  That means a lot!


fix camelCase to kebab-case conversion

Overview
The camelCase to kebab-case string conversion function is updated to use "github.com/ettle/strcase" package instead of local implementation. It should allow converting module names containing digits more correctly.

What this PR does / why we need it
It updates the way we convert camelCased strings to kebab-cased. At now, if we have something like 'l2-load-balancer' in kebab-case, after converting to camelCase and back it ends up with 'l-2-load-balancer'.

Special notes for your reviewer

here is a diff output between values before and after the changes

I think I can't comprehend all possible consequences of these changes, need you to spend a couple of minutes thinking through a possible worst case scenario :) @nabokihms @yalosev