Stop setting z-index

Do you want to request a feature or report a bug?
Bug
What is the current behavior?
The draft-js placeholder show up on top of things that are supposed to be on top of it.
**If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem. You can use this jsfiddle to get started:

See also https://jsfiddle.net/dobesv/t3s8vbf7/1/
What is the expected behavior?
draft-js inputs should behave like other inputs and not use z-index.  Currenly z-index appears twice in the Draft.css.  I think if someone has a need for the z-index to be set to work around some stacking issue, they should do it themselves.  It should not be included in the default styles.
CSS has better ways to solve stacking issues besides z-index.
Which versions of Draft.js, and which browser / OS are affected by this issue? Did this work in previous versions of Draft.js?
Our project has this issue in version 0.11.5, the jsfiddle reproduces it in 0.11.0.

Hiya,
Did you ever find a work around for this bug? I'm having issues with this also.

I added this CSS to force it:
.public-DraftEditorPlaceholder-root {
  z-index: 0 !important;
}

This works for me in version 0.11.7:
.DraftEditor-editorContainer {
  z-index: 0 !important;
}


Mention Ember Named Blocks

Excellent :)
On Wed, Aug 15, 2018, 5:00 AM sandstrom<EMAIL_ADDRESS>wrote:

You can view, comment on, or merge this pull request online at:
https://github.com/ciena-blueplanet/ember-block-slots/pull/59
Commit Summary

Mention Ember Named Blocks
linebreak

File Changes

M README.md
https://github.com/ciena-blueplanet/ember-block-slots/pull/59/files#diff-0
(9)

Patch Links:

https://github.com/ciena-blueplanet/ember-block-slots/pull/59.patch
https://github.com/ciena-blueplanet/ember-block-slots/pull/59.diff

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/ciena-blueplanet/ember-block-slots/pull/59, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AIm6lo_DaOOqAzQVkaq2EAd2JObzepTEks5uQ-MWgaJpZM4V9yLJ
.


Locking the counter.

It is possible to lock any field on the SRI/SRT512 devices.
Is it possible to lock the counter and have the device not error out?
Need to run:
hf 14b sriwrite 2 FF ffff9fff

The contents will be displayed in the format 12345678 and to write the format 78563412 must be used. The counters are in addresses 5 and 6 and the corresponding register bits 21 and 22.  Writing xxxx9Fxx will lock them.

Locking the counter does not work. The device will not error until the cycle is started. The device must be confirming that it can decrement the counter before it proceeds.

[usb] pm3 --> hf 14b sriwrite 2 FF ffff9fff
[+] [SRI512] Write special block FF [ FF FF 9F FF  ]
[+] received SOF only (maybe iCLASS/Picopass)

Nikola.D: 0
[usb] pm3 --> hf 14b sriread 2

Nikola.D: 0
[usb] pm3 -->
[#] Address=00, Contents=00000000, CRC=defc
[#] Address=01, Contents=ffffffff, CRC=470f
[#] Address=02, Contents=ffffffff, CRC=470f
[#] Address=03, Contents=ffffffff, CRC=470f
[#] Address=04, Contents=ffffffff, CRC=470f
[#] Address=05, Contents=00000060, CRC=3a65
[#] Address=06, Contents=00000060, CRC=3a65
[#] Address=07, Contents=00003015, CRC=86d7
[#] Address=08, Contents=00780001, CRC=61de
[#] Address=09, Contents=00780001, CRC=61de
[#] Address=0a, Contents=00780001, CRC=61de
[#] Address=0b, Contents=00000f04, CRC=f5c4
[#] Address=0c, Contents=00000f04, CRC=f5c4
[#] Address=0d, Contents=4e32014e, CRC=9f30
[#] Address=0e, Contents=4e32014e, CRC=9f30
[#] Address=0f, Contents=fc790f04, CRC=cade
[#] Address=ff, Contents=ff9fffff, CRC=126a


New feature request

Hi, your SmartTabLayout is a good library. But it will be very nice if you implement next feature. When user scrolling tabs layout, during scroll viewpager must to be scrolled with the tabs and the tab's indicator will update its state too. Anyway, thank you.

I'm sorry, implementation I gave up.


Export and import functionality and global profile

I've decided to poke around this beautiful extension and tried shrinking the "idea list" (#1) by implementing the import and export functionality for profiles. Basically I've reused createProfile() and deleteProfile() functions and just added file save/open prompts and actual profile file export/import.
Profiles are exported/imported into/from .json files. When exporting, the name of the selected profile is used as a name for the file and when importing the same file name is used for the profile name (profile name is "test" -> exports into "test.json". File name is "123.json" -> gets imported into a new profile "123").
I've been thinking what should be the default path to export profiles and I decided to use the 'Documents' folder. Its path varies from system to system, so I've implemented pathToDocuments(), but I don't have a machine with Windows ATM, though I've tested the extension on Mac and Linux (Ubuntu 20.04) and it works as expected. I'm hoping to get access to one soon, but for now feel free finish the pathToDocuments() function. I've added comments so it's easier to understand.
P.S. There are some cosmetic changes that came from me fixing the .eslintrc's curly rule, hope you don't mind.

@da-the-dev you're doing great, thank you so much for PR.
I fixed minor bugs, did refactoring and added support for multilingual extensions #16.

@evald24 Thank you so much!

@evald24 I've create a VM with Windows 10 installed and tried the extension, it work flawlessly! The homedir() function is a very good idea! I believe it is ready for 1.0.10.

I've also added Global Profile functionality. A few folks from #1 requested a sort of global profile that would apply alongside every other profile. I've added a function to update it (updateGlobalProfile), a command to import it (importGlobalProfile), extended exportProfile() to be able to export it and also modified createProfile(), editProfile() and deleteProfile() to not show the Global Profile in the selection list. Cosmetic changes here and there.
Right now I'm thinking of somehow integrating syncing, but I suppose I'll need to revamp profiles as a whole so that they could be individually applied and disabled.

@da-the-dev great job, I'll watch and test it tomorrow)

I've simplified how global profile works, it used to be some over-engineered over-the-top profile that had separate functions for it, now it's just a profile that you can't delete and is applied along side every other profile.

@da-the-dev Hi! Can you explain the meaning of "Global Profile" if it is no different from a regular profile?

Added support for "WSL" #19

@da-the-dev I'm sorry, I was sick and could not fully understand the idea =)
Congratulations on this first minor update 🥳


Substituting variables into the devfile from the CLI

What type of PR is this:
/kind feature
What does this PR do / why we need it:
Which issue(s) this PR fixes:
Fixes #5489
PR acceptance criteria:

[ ] Unit test

[ ] Integration test

[ ] Documentation

How to test changes / Special notes to the reviewer:

Blocked by https://github.com/devfile/library/pull/136

/approve

/override ci/prow/v4.10-integration-e2e
Infra error
IBM tests pass


asyncData() is not executed after changing route query using $router.push

Version
v2.4.5
Reproduction link
https://codesandbox.io/s/38pzrn9nk1
Steps to reproduce

Navigate to https://38pzrn9nk1.sse.codesandbox.io/?page=1
Notice "current route path" and "asyncData was excecuted for route" values in page
Click button "change route query", which will change route query using this.$router.push({ query: { page: rand_int } })
Notice, that the route (page URL) has changed, but asyncData() was not executed for the new page

What is expected ?
asyncData() should be executed for new route, even if just query param value changes. in this case ?page=
What is actually happening?
URL changes, but new page load cycle is not started, thus asyncData() is not executed too

This bug report is available on Nuxt community (#c8871)

You must enable the watchQuery  property on the page component.  You can read about it here.

As @henriqemalheiros said :relaxed:

thank you for a quick response! Added watchQuery: ["page"] export default {}, however even in asyncData() seems to be executed, it's results are not returned to page (mount does not happen). Am I missing something else here again?

@togishub How can I use the watchQuery property?thank you

My problem is that URL changes don't want to update data asynchronously.

My problem is that query parameter changes don't want to update data asynchronously.

ouyangfan, my example now includes working code with watchQuery property: https://codesandbox.io/s/38pzrn9nk1
see code at:
`


Update onnx commit

Update onnx commit to include Haruki san's big endian fix for numpy_helper.py

@tjingrant Yes and unfortunately the big endian fix was not backported to official v1.7. Hopefully once we support v1.8 this would be a nonissue.


Array of objects with different keys will not return all of them even if specified headers

new CSV([{a:1, b:2}, {a:1, b:2, c:3}], {
  header: ['a','b','c'],
}).encode();

will return:
"a","b","c"
1,2
1,2

value "c" will not render
same apply if first value is null:
new CSV([{a:1, b:2, c: null}, {a:1, b:2, c:3}], {
  header: ['a','b','c'],
}).encode();

That's a good case you found there!
CSV.js uses the first object as a prototype for the keys, and caches those values. But it should do what you're talking about: Specifying a header should work.

Yeah we keep running into this also when parsing user input data.  Working around it for now by putting in a dummy first row containing all the columns, parsing, then removing the first row.


Fix browser cache issues when upgrading

I would like to test the upgrade process between the last two releases to confirm the issue, but based on user reports, it seems that an App bug is often encountered after upgrading because the browser is using the cached version from the previously installed release.
This change ensures the current index.html file is always returned which will load the correct App assets.

I've tested on starlette 0.24 which is the minimum version requirement, and the change works.
Note this only adds the Cache-Control no-store response header only for the index.html response. All other App assets take advantage of caching.


⚠ Thumbnails API Endpoint has degraded performance

In 9fe08f7, Thumbnails API Endpoint (https://thumbnails.roblox.com/v1/assets?assetIds=82738847&format=Png&isCircular=false&size=30x30) experienced degraded performance:

HTTP code: 200
Response time: 1682 ms

Resolved: Thumbnails API Endpoint performance has improved in 57dbc0d after 12 minutes.


OIDC

User stories
As a User I want to create my account and log in with HPI-OIDC in order to make log in more convenient.
Dependencies
Depends on:

#51

UI Mockup
[UI Mockup]
Acceptance Criteria

[ ] I can log in with HPI-OIDC
[ ] If I don't have an account and try to log in with OIDC, my account is created automatically
[ ] My E-Mail is the OIDC E-Mail

Review: @Nils1729


Tutorial on https://docs.qovery.com/guides/getting-started/deploy-your-first-application/ failed

The tutorial on:
https://docs.qovery.com/guides/getting-started/deploy-your-first-application/
Here's what went wrong:

patarapolw@pacharapol-elem:~/projects/simple-example-node$ qovery status
  BRANCH NAME | STATUS | ENDPOINTS | APPLICATIONS | DATABASES |
              |        |           |              |           |

  APPLICATION NAME | STATUS | DATABASES
                   |        |

  DATABASE NAME | STATUS | TYPE | VERSION | ENDPOINT | PORT | USERNAME | PASSWORD | APPLICATIONS
                |        |      |         |          |      |          |          |

patarapolw@pacharapol-elem:~/projects/simple-example-node$ qovery run
ERROR:   The project does not exist. Are you well authenticated with the right user? Do 'qovery auth' to be sure

This is exactly the hello-world forked.

Hi @patarapolw, did you give access to the Qovery github app?

Yes, also with SSH setup as well (otherwise I cannot clone git@)

Hello @patarapolw, thanks for the report.
To make sure that Qovery has access to this particular repository, you can go to:
https://github.com/settings/installations
Click "Configure" next to Qovery:

And you'll see the list of selected repositories (maybe this one is not there?). You can also allow us to access all repositories, so all future repos you create will work fine without any additional actions.

I just forked this repo (from the tutorial) and it deployed successfully for me. It's possible that it's repository acccess issues in your case.

Please reopen this issue if it is still the case. Thanks


How to hide loading or errors?

Just have to setVisibility of emptyView to GONE?

Hi. You can just use showContent() method to hide emptyview.


TypeError: Error while loading rule 'unicorn/expiring-todo-comments': Cannot read properties of undefined (reading 'decoration')

https://togithub.com/sindresorhus/eslint-plugin-unicorn/issues/2496 ?


doc: manual deployment instruction added

Ok, 2 week, btchs
ср, 29 нояб. 2023 г., 23:11 Timothy Jaeryang Baek @.***

:

Merged #160 https://github.com/ollama-webui/ollama-webui/pull/160 into
main.
—
Reply to this email directly, view it on GitHub
https://github.com/ollama-webui/ollama-webui/pull/160#event-11101506055,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A2XOFORLTOQBTLQTFJXDIQLYG6QITAVCNFSM6AAAAABAAD4ECCVHI2DSMVQWIX3LMV45UABCJFZXG5LFIV3GK3TUJZXXI2LGNFRWC5DJN5XDWMJRGEYDCNJQGYYDKNI
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***
com>


ci: clean up to pass linters

Linters https://github.com/xbcsmith/x-commit-hooks/blob/master/scripts/x-go-hooks.sh


Feat/tx builder stake key dereg

Context

TxBuilder delegate(...) call is async only because it fetches rewardAccounts in order to generate certificates.
This forces users to await for delegate call and check for errors.
User cannot deregister stake key using TxBuilder.
User can use OutputBuilder txOut snapshot in addOutput.

Proposed Solution

Postpone fetching rewards accounts and adding certificates until TxBuilder.build()
delegate(...) is stored as an intent configuration in TxBuilder, which is inspected and applied at build() time.
Update api to allow calling delegate() with undefined poolId. Doing this is considered a deregister request, thus adding the Deregister certificate at build time.
OutputBuilder toTxOut() can be used to get a snapshot of the transaction output built so far. This snapshot can be used in txBuilder.addOutput(...). TxBuilder will validate the provided output(s) on build by calling the OutputBuilder.build() method on all outputs.

Important Changes Introduced

delegate(...) is no longer async.
OutputBuilder.partialOutput is private.

For the moment I am not squashing so that the review is easier to do.
I will squash to a smaller number of commits after the final review.

f5a779e contains only some improvements for the generated docs

Nice work! 🚀

Thank you. I have squashed and force pushed.


Make Utils.parseURL public to remove unnecessary reflection

Why are the changes needed?
make Utils.parseURL public to remove unnecessary reflection of it
How was this patch tested?

[x] Add some test cases that check the changes thoroughly including negative and positive cases if possible

[x] Add screenshots for manual tests if appropriate

[x] Run test locally before make a pull request

Codecov Report

Merging #2533 (d4e2f1a) into master (04a91e1) will decrease coverage by 0.02%.
The diff coverage is 0.00%.

@@             Coverage Diff              @@
##             master    #2533      +/-   ##
============================================
- Coverage     63.62%   63.59%   -0.03%
  Complexity       41       41
============================================
  Files           373      373
  Lines         17836    17826      -10
  Branches       2378     2378
============================================
- Hits          11348    11337      -11
+ Misses         5435     5433       -2
- Partials       1053     1056       +3

Impacted Files
Coverage Δ

.../java/org/apache/kyuubi/jdbc/KyuubiHiveDriver.java
4.87% <0.00%> (+0.17%)
:arrow_up:

...c/main/java/org/apache/kyuubi/jdbc/hive/Utils.java
1.73% <ø> (ø)

...ain/scala/org/apache/kyuubi/engine/EngineRef.scala
77.14% <0.00%> (-8.58%)
:arrow_down:

...rg/apache/kyuubi/engine/trino/TrinoStatement.scala
68.96% <0.00%> (-2.30%)
:arrow_down:

...mon/src/main/scala/org/apache/kyuubi/Logging.scala
39.72% <0.00%> (-1.37%)
:arrow_down:

...in/java/org/apache/hive/beeline/KyuubiBeeLine.java
0.00% <0.00%> (ø)

...ache/kyuubi/operation/KyuubiOperationManager.scala
85.24% <0.00%> (+1.63%)
:arrow_up:

Continue to review full report at Codecov.

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

nit: for the PR title, it is better to keep the first letter capitalized.

thanks, merging to master


error getting canonical path in Windows when Trunk.toml file has target "static/index.html"

When using trunk on Windows, and the config file Trunk.toml has a path that uses forward slashes /.
[build] target = "static/index.html" release = false dist = "dist" manifest = "Cargo.toml" public_url = "/
It fails with:
Error: error getting canonical path to source HTML file "\\?\C:\Users\\Projects\\**-web-app\static/index.html"

Hey @kotshie. Sounds like the quick and dirty fix is to just use a Windows style path in your config file. That should resolve the issue. Given that the Trunk.toml is fully controlled by the end user (you), is there any reason why that will not work here?

Hey @kotshie. Sounds like the quick and dirty fix is to just use a Windows style path in your config file. That should resolve the issue. Given that the Trunk.toml is fully controlled by the end user (you), is there any reason why that will not work here?

It's annoying when the code expects developers across different operating systems, which is often the case in the open-source world. I and my coworkers bumped into this problem earlier and our solutions is to have Trunk.toml and Trunk-win.toml, with windows users running trunk --config Trunk-win.toml. This is not very convenient and requires duplicating parts of the config.

I suggest we make it consistent with how Rust's std::path handles paths: "/" on unix, "/" OR "\" on Windows, see https://doc.rust-lang.org/std/path/struct.Path.html
We won't need to change any documentation and this won't even be a breaking change but an extra feature.

I suggest we make it consistent with how Rust's std::path handles paths: "/" on unix, "/" OR "" on Windows, see https://doc.rust-lang.org/std/path/struct.Path.html We won't need to change any documentation and this won't even be a breaking change but an extra feature.

I did some extensive testing and it turns out this is already the behavior on the master branch 🤦 , just not on the changelog.
So to use the new behavior, you can just install the master branch with cargo install --git https://github.com/thedodd/trunk trunk


Package Dependency processing!

Major improvement to handle IG/resource dependency processing.

This is covered by commit #2


GKE Plugin should improve upload-buildpacks

--container-registry should not be required for the upload-buildpacks command after installing gke plugin.

We've removed the upload-buildpacks command, so I'm going to close this.


Pager Duty integration enhancements

Motivation
As for today, the Pager Duty integration initiated with data that lacks the main features of Pager Duty and people struggle to gain real value from it from the first installation.
For improving that it would be best to enrich the Raw Data that the Pager Duty integration brings by addressing more Pager Duty APIS such as Business Service and Service Dependencies.
Moreover, to reduce the time people gain value from the integration we would like to change the default resources of the integration to include more properties such as Slack Channel, Maintenance window, Dependent services and more.
Proposed changes

Add a new kind of Business Services to bring data from the matching API.
Enrich the data on Services to include the dependencies of other services using the Service Dependencies API
Change the default blueprints to the following blueprints and update the config.yaml.

Blueprints
[
{
  "identifier": "pagerdutyService",
  "description": "This blueprint represents a PagerDuty service in our software catalog",
  "title": "PagerDuty Service",
  "icon": "pagerduty",
  "schema": {
    "properties": {
      "description": {
        "icon": "Book",
        "type": "string",
        "title": "Description"
      },
      "status": {
        "icon": "pagerduty",
        "title": "Status",
        "type": "string",
        "enum": [
          "active",
          "warning",
          "critical",
          "maintenance",
          "disabled"
        ],
        "enumColors": {
          "active": "green",
          "warning": "yellow",
          "critical": "red",
          "maintenance": "turquoise",
          "disabled": "lightGray"
        }
      },
      "url": {
        "icon": "pagerduty",
        "title": "URL",
        "type": "string",
        "format": "url"
      },
      "oncall": {
        "icon": "TwoUsers",
        "title": "On Call",
        "type": "string",
        "format": "user"
      },
      "communication_channel": {
        "icon": "Slack",
        "title": "Communication Channel",
        "type": "string",
        "format": "url"
      },
      "maintenance_start_time": {
        "icon": "DevopsTool",
        "title": "Maintenance Start Time",
        "type": "string",
        "format": "date-time"
      },
      "maintenance_end_time": {
        "icon": "DevopsTool",
        "title": "Maintenance End Time",
        "type": "string",
        "format": "date-time"
      },
      "team": {
        "title": "Team",
        "type": "string",
        "icon": "DefaultProperty"
      },
      "last_incident": {
        "icon": "Clock",
        "title": "Last Incident",
        "type": "string",
        "format": "date-time"
      },
      "escalation_policy_unique_level": {
        "title": "Escalation Policy Unique Level",
        "type": "number",
        "icon": "DefaultProperty"
      }
    },
    "required": []
  },
  "mirrorProperties": {},
  "calculationProperties": {},
  "relations": {
    "uses": {
      "title": "Uses",
      "target": "pagerdutyService",
      "required": false,
      "many": true
    }
  }
},
{
  "identifier": "pagerdutyBusinessService",
  "description": "This blueprint represents a PagerDuty business service in our software catalog",
  "title": "PagerDuty Business Service",
  "icon": "pagerduty",
  "schema": {
    "properties": {
      "point_of_contact": {
        "icon": "TwoUsers",
        "type": "string",
        "title": "Point Of Contact",
        "format": "user"
      },
      "team": {
        "type": "string",
        "title": "Team",
        "icon": "DefaultProperty"
      },
      "description": {
        "type": "string",
        "title": "Description",
        "icon": "DefaultProperty"
      },
      "status_page": {
        "type": "string",
        "title": "Status Page",
        "format": "url",
        "icon": "DefaultProperty"
      }
    },
    "required": []
  },
  "mirrorProperties": {},
  "calculationProperties": {},
  "relations": {
    "services": {
      "title": "Services",
      "target": "pagerdutyService",
      "required": false,
      "many": true
    }
  }
},
{
  "identifier": "pagerdutyIncident",
  "description": "This blueprint represents a PagerDuty incident in our software catalog",
  "title": "PagerDuty Incident",
  "icon": "pagerduty",
  "schema": {
    "properties": {
      "status": {
        "icon": "DefaultProperty",
        "title": "Incident Status",
        "type": "string",
        "enum": [
          "triggered",
          "annotated",
          "acknowledged",
          "reassigned",
          "escalated",
          "reopened",
          "resolved"
        ],
        "enumColors": {
          "triggered": "red",
          "annotated": "red",
          "acknowledged": "green",
          "reassigned": "green",
          "escalated": "red",
          "reopened": "red",
          "resolved": "green"
        }
      },
      "url": {
        "type": "string",
        "format": "url",
        "title": "Incident URL",
        "icon": "DefaultProperty"
      },
      "urgency": {
        "icon": "Alert",
        "title": "Incident Urgency",
        "type": "string",
        "enum": [
          "high",
          "low"
        ],
        "enumColors": {
          "high": "lightGray",
          "low": "lightGray"
        }
      },
      "assignee": {
        "icon": "TwoUsers",
        "type": "string",
        "title": "Assignee",
        "format": "user"
      },
      "escalation_policy": {
        "icon": "BlankPage",
        "type": "string",
        "title": "Escalation Policy"
      },
      "created_at": {
        "icon": "DefaultProperty",
        "title": "Created At",
        "type": "string",
        "format": "date-time"
      },
      "updated_at": {
        "title": "Updated At",
        "type": "string",
        "format": "date-time",
        "icon": "DefaultProperty"
      }
    },
    "required": []
  },
  "mirrorProperties": {},
  "calculationProperties": {},
  "relations": {
    "pagerdutyService": {
      "title": "PagerDuty Service",
      "target": "pagerdutyService",
      "required": false,
      "many": false
    }
  }
}
]

Screenshots

Hi, totally agree :)
I believe one of the main use-cases would involve generating scorecards that display the number of open incidents for a specific service. To achieve this in a user-friendly manner, we could enhance the existing implementation by introducing a new type of aggregatedIncidentData. This data would be associated with each individual Pager Duty Service and structured in JSON format as shown below:
{
  "service_id": "PWER234D",
  "total_open_incidents": 12
}

Whenever a new incident is created or updated, this information would be automatically synchronized for the relevant service. Furthermore, during a resynchronization process, this aggregated incident data would also be included.
In addition, we could incorporate this functionality into the default blueprints by adding a property named numberOfOpenIncidents of type number to the PagerDutyService blueprint. This approach would provide a standardized way of representing and accessing the count of open incidents for each service.

Hi, totally agree :)
I believe one of the main use-cases would involve generating scorecards that display the number of open incidents for a specific service. To achieve this in a user-friendly manner, we could enhance the existing implementation by introducing a new type of aggregatedIncidentData. This data would be associated with each individual Pager Duty Service and structured in JSON format as shown below:
{
  "service_id": "PWER234D",
  "total_open_incidents": 12
}

Whenever a new incident is created or updated, this information would be automatically synchronized for the relevant service. Furthermore, during a resynchronization process, this aggregated incident data would also be included.
In addition, we could incorporate this functionality into the default blueprints by adding a property named numberOfOpenIncidents of type number to the PagerDutyService blueprint. This approach would provide a standardized way of representing and accessing the count of open incidents for each service.

That's awesome, I will add that to the ehancement


fix the parsing of fixes

This fixes a very serious bug in parsing & creating Fixes URLs. Noticed it while landing: https://github.com/nodejs/node/commit/291ff72f859df3c4c3849021419f37cd542840a6
This should warrant a new release on npm since this makes get-metadata very problematic to use.

Codecov Report

Merging #70 into master will increase coverage by 0.02%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master      #70      +/-   ##
==========================================
+ Coverage   95.49%   95.51%   +0.02%
==========================================
  Files          13       13
  Lines         444      446       +2
==========================================
+ Hits          424      426       +2
  Misses         20       20

Impacted Files
Coverage Δ

lib/links.js
100% <100%> (ø)
:arrow_up:

lib/metadata_gen.js
100% <100%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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

Great work!

So I think we should merge this now and release soon, we can address https://github.com/joyeecheung/node-core-utils/pull/70#discussion_r148946435 later.


How to manage custom fields for deliveries and dev

In a classic project, custom fields are really fine for protoyping.
Also, it gets close to the custom fields we can add in D365 Sales and already supports to be added into data entities. So it seems to be eligible for projects even with integration to manage.
But, by now, I don't see how I can move such elements from one environment to another one in order to manage it in test/UAT for prototyping and integration validation and then move it to the production.
Also, if further evolutions are required and business rules have to be written using those fields, how can we use those? Are those fields part of a special model/package we can reference in a dev environment?

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

ID: 243a07df-1659-0c6e-6775-f6e86eabf287
Version Independent ID: 1ef4dcc2-b1eb-7806-2eae-6db2951a7c12
Content: Custom fields - Finance & Operations | Dynamics 365 | #MSDyn365FO
Content Source: articles/fin-and-ops/get-started/user-defined-fields.md
Service: dynamics-ax-platform
GitHub Login: @jasongre
Microsoft Alias: jasongre

Thanks for taking the time to provide this kind of feedback. I will pass this message on to the author and your suggestion will be noted as a future enhancement to this topic.

Any update on this?

Custom fields are ok for info only. You can't write code against them so their use is pretty limited in my opinion.

How could I add custom fields to other tables that are not shown in the list? e.g: Invoice Line.


Cannot name a decorator flags lib linter or onEmit (special exports)

Problem
Cannot name a decorator flags lib linter or onEmit (special exports)
Due to how to use certain reserved name in JS we cannot name a decorator with those names
Add a new $decorators export
export const $decorators = {
  Azure.Core: {
    flags: $flags,
    "foo-bar": fooBarDecorator
  }
}

we can additionally provide a typed helper
function defineDecorators(decorators: Record<string, Record<string, DecoratorFunction>>) {
   return decorators;
}

export const $decorators = defineDecorators({
  Azure.Core: {
    flags: $flags,
    "foo-bar": fooBarDecorator
  }
})

Additional items

Update docs to recommend this approach
Update tspd to only support this new approach. This isn't breaking as tspd is not published yet.

Option 1: USe $$ for known configs
This would reserve $ for decorators. For back compat we would still check if the $ variant of $lib, $flags, etc. is a config object and use that instead.
Option 2: Dedicated $decorators export
this allows to exports all decorators

Need to triage for scheduled changes

est: 5


Added available sort options for all REST API endpoints that allow sorting

:heart: Thank you for your contribution!
Description
Added documentation on the sort options available for all REST API endpoints that allow sorting.
Checklist
Ticks in all boxes and 🟢 on all GitHub actions status checks are required to merge:

[X ] I'm aware of the code of conduct.
[X ] I've created logical separate commits and followed the commit message format.
[X ] I've added relevant test cases.
[X ] I've added relevant documentation.
[X ] I've marked translation strings (for relevant code).
[X ] I've followed the CSS/JS and React guidelines (for relevant code).
[X ] I've followed the web accessibility guidelines (for relevant code).
[X ] I've followed the user interface guidelines (for relevant code).
[X ] I've identified the copyright holder(s) and updated copyright headers for touched files (>15 lines contributions).
[X ] I've NOT included third-party code (copy/pasted source code or new dependencies).

Third-party code
If you've added third-party code (copy/pasted or new dependencies), please reach out to an architect.
Reminder
By using GitHub, you have already agreed to the GitHub’s Terms of Service including that:

You license your contribution under the same terms as the current repository’s license.
You agree that you have the right to license your contribution under the current repository’s license.

Okay, I've made the minor changes to default option ordering, removed the table of vocab options (leaving a description of the defaults), and fixed the missing file extensions in the links. Should be good to go.

Hmm something is off with the links (see https://github.com/inveniosoftware/docs-invenio-rdm/actions/runs/8582061590/job/23563183805?pr=612), but at least one other PR is potentially affected: https://github.com/inveniosoftware/docs-invenio-rdm/actions/runs/8526851030/job/23356983728?pr=614 ... I will add this as something I will look into this month as part of preparations for v12 since we need to make sure docs are good.

Okay, I rebased my branch but it doesn't seem to have fixed the issue. When I build the docs locally I get the same error: not from links in the documentation text but because of two missing style files: /assets/stylesheets/main.10ba22f1.min.css and /assets/stylesheets/palette.06af60db.min.css. These are linked in the frontpage_base.html template, and the files do indeed seem to be missing. I don't think this is related to any of my changes. Maybe something happened upstream that is just becoming visible here? (Or maybe I'm missing something!)

Indeed something is strange. If you don't mind, when I look into it, may I push to your branch to fix it? This will be faster and you've already done the heavy lifting, so you shouldn't have to deal with that structural problem :wink:  .

Sure. No problem

Merged it here: https://github.com/inveniosoftware/docs-invenio-rdm/pull/619 (@monotasker 's master branch is probably protected so I couldn't push to it). I think Nico fixed the issue by resetting the clean options: https://github.com/inveniosoftware/docs-invenio-rdm/commit/c6e7334fe0a9386d1db42fe499cd5c53947be556#diff-1db27d93186e46d3b441ece35801b244db8ee144ff1405ca27a163bfe878957fR41 . Kind of strange nevertheless.


Attempting to POST Object with LinkedResourceCollection

First off, this is like my third question so forgive me for being persistent! I am new to iOS so there is a high chance I'm just doing things wrong.
I have an object that takes the following fields on init():
class EventModel: Resource {

  var title: String?
  var startTime: String?
  var endTime: String?
  var descriptionText: String?

  var resources: LinkedResourceCollection?
  var reservations: LinkedResourceCollection?

...

init(title: String?, startTime: String?, endTime: String?, descriptionText: String?, resources: LinkedResourceCollection?) {
    self.title = title
    self.startTime = startTime
    self.endTime = endTime
    self.descriptionText = descriptionText
    self.resources = resources
    super.init()
  }

And in my code, I'm trying to test a save method to make a POST to our API:
let resourceTest = ResourceModel(category: "parking_na", title: "Parking Lot")
    var resources: LinkedResourceCollection?
    resources?.appendResource(resourceTest)
    let eventTest = EventModel(
      title: "Event Blah 4",
      startTime: "2016-11-01T11:00:000Z",
      endTime: "2016-11-01T12:00:000Z",
      descriptionText: "This is an event and stuff 4",
      resources: resources)

    EventAPIHelper.saveEvent(event: eventTest)

The event saves successfully, but my relationships are not properly appearing in the JSON when I get events back from the API:
...
"relationships":{
"reservations":{"data":[]}, // ignore this piece
"resources":{
"data":[]
}
},
...

Am I not implementing the LinkedResourceCollection properly? Because that seems to be the issue.

LinkedResourceCollection has two methods for adding resources:

appendResource just appends the resource to the collection, but doesn't store or link anything.
linkResource appends the resource to the collection, and links it to the parent resource.

The one you want to use in this case is linkResource. However, you cannot link resources that haven't been persisted yet. So you first have to save resourceTest, then add it to the linked collection, and then save eventTest.

I'm also struggling with the same issue, and even after linking the resource, there is no concept of included or any attributes within the data tag of the relationship. I have an Order which has multiple Meal objects, but I cannot seem to easily "place an order" which should be making a POST call with the Order object
`    init(address: Address, meals: [Meal], couponCode: String?) {
self.address = address
    let mealsCollection = LinkedResourceCollection(resourcesURL: nil, linkURL: nil, linkage: nil)
    mealsCollection.linkResources(meals)

    self.meals = mealsCollection

    self.coupon = Coupon()
    self.coupon?.code = couponCode

    super.init()
}

`

Hi Stephen, what exactly isn't working for you? Do you mean you want to POST a new Order, while at the same time POSTing the linked meals?

Correct, I want to POST an order that also includes relationships. Here is an example of what the request would look like:
    "data": {
        "type": "order",
        "attributes": {
            "address_id": 1,
            "payment_id": 1,
            "tip": 10 // optional, this is percentage, 10% tip on top of subtotal + tax
        },
        "relationships": {
          "address": {
            "data": {
              "id": 1,
              "type": "addresses"
            }
          },
          "payment": {
            "data": {
              "id": "1",
              "type": "payments"
            }
          },
          "order_meals": {
            "data": []
          },
          "meals": {
            "data": [{
                "id": 1,
                "type": "meals",
                "quantity": 1,
                "option_id": 1
            }, {
               "id": 2,
               "type": "meals",
               "quantity": 2
           }]
          },
          "coupon": {
            "data": {
              "code": "voluptates",
              "type": "coupons"
            }
          }
        }
    }
}````

Also, I'm aware that attributes aren't really supposed to go inside of the relationships tag, but I don't see a way to put those objects inside of an `included` key anywhere. I have attempted to `addResource` and `linkResource`, but the data for those resources are not included. Since this needs to be a single API call, it's not really possible to save the child relationships before the parent relationship.

If this is not possible, is it possible to use the standalone `Serializer` to parse a response that includes relationships? I am happy to write a custom outgoing network call if the serializer can parse the response and still delivery a `Resource` result.

I'm aware that attributes aren't really supposed to go inside of the relationships tag

This is exactly why Spine has no support for this. The JSON:API standard does not support 'sideposting' resources like this. You have to first save your meals, then link to to the order, and then save the order.
The serializer has no support for this either, sorry.

Closing this since this is not an issue with the library, but with the JSON:API standard. Feel free to reopen if you think something should be update on Spine :).


Bijector caching breaks when used with TransformedDistribution

Currently, the caching that Bijector objects do to avoid unnecessary calculations does not work when the bijector is used in a TransformedDistribution object. I believe the culprit is the reshaping that the distribution object does here; when we call Bijector.inverse on the output, the Bijector object cannot tell that this is merely a reshaped version of what it calculated previously.
My use case is to sample from a TransformedDistribution and then later calculate the log probability of that sample.
This issue is particularly a problem when using a bijector whose inverse is numerically delicate (in my case, I'm chaining together softplus bijectors and my own custom affine bijector).
I'm willing to work on a fix for this problem, but I'm not sure what the best way to do it is (adding caching to the TransformedDistribution code might work, but that seems like code duplication).
System information

OS Platform and Distribution: Ubuntu 16.04
TensorFlow installed from: Source
TensorFlow version: v1.1.0-rc2-773-g7fa0cf3 (commit 7fa0cf39f854d5fdaaa19ad6425dfed02f5fea64)
Bazel version: 0.4.5

@ebrevdo Can you comment?

Waiting for response as well, deep bijections work slow for me

My apologies for the slow response, it looks like this issue was inadvertantly misrouted.
Caching was fixed on Sept 29 and should be working in 1.4.0-rc0.
https://github.com/tensorflow/tensorflow/commit/46cf6262476b1d058e43acacc2c15097cc7bbf5a
If youre still seeing a problem, please let me know.

Closing as fixed.


Concrete archives being templates plus some minor improvements.

Hi.
In this pull request the archive classes that were concrete classes previously have become templates that take a Derived class as a parameter, which is then passed to OutputArchive/InputArchive. This allows one to extend an existing archive's functionality by inheriting from it in CRTP manner. The original archives' names exist as typedefs, so users won't notice the change, except for slightlly bigger build times.
Also some issues have been fixed here:

JSON archive's compilation problems on Mac
XML archive's problem of serializing space characters and space-only strings.

And some tweaks have been made:

CEREAL_REGISTER_TYPE can now be called from multiple translation units for the same type. This allows one to re-register an already registered type when additional archives become available.
Error message has been improved for the case when multiple serialization routines exist for the same type.
CEREAL_DECLARE_DYNAMIC_INIT_ENFORCER and CEREAL_DEFINE_DYNAMIC_INIT_ENFORCER macros have been added, which allow to force the compiler to initialize global data of a certain translation unit.
I personally found the need for them when I had a source file that called CEREAL_REGISTER_TYPE while it and its associated header file didn't have anything that is "odr-usable" - without the macros I had the "Trying to save/load an unregistered polymorphic type" exception on every recompile/run. A colleague of mine had a more subtle issue, where the source file with CEREAL_REGISTER_TYPE contained some definitions for the hierarchy's base class' members but not for the constructor, which was defined as inline in the header file; the application he was working on was only deserializing data that came through a network connection; this lead to the "unregistered polymorphic type" error appearing on every other recompile/run, probably becase the constructor was put to that translation unit by the compiler sometimes, which made it "odr-used" before the deserialization for that type had begun.
Note that in practice I've only seen this issue when the serializable type and the CEREAL_REGISTER_TYPE call were in a static library and the serialization was performed outside of it, this is why the corresponding tests use static libraries.

This will take a little while to process.  Some of your changes may already have been performed in our develop branch, but there are some interesting things here, especially everything related to REGISTER_TYPE.

Going to check off various things that I've found we've already pushed to develop bit by bit.
Your b5a520e7dbfafd1b9b5435e1fe415ff92c6acecb (static assertion improvement) was done by 2edc936e5006a01e8ed33854040e0d9147d45c3d.

XML space saving was resolved by #109 (not sure which of yours does this).
Your CEREAL_DECLARE_DYNAMIC_INIT_ENFORCER was implemented by e423228dde132a1be238096491b9c1e36dadfb2d (see #107).
JSON compilation issues have likely been fixed by a series of changes to long serialization on OSX (see #81 and #105).
I haven't looked into the CRTP changes yet.  However, moving prologue/epilogue functions to be member functions is likely problematic for future user-defined types since they would require direct modification of the archive itself.
Your changes to the registration for polymorphic items are going to solve two issues that have been blocking 1.1 for a while.

XML space saving was resolved by #109 (not sure which of yours does this).

It's funny, the guy who posted this is one of my colleagues, and he sits a couple of meters away from me. It looks like we have a communication problem :-)

Your CEREAL_DECLARE_DYNAMIC_INIT_ENFORCER was implemented by e423228 (see #107).

OK. Just a note: the problem is not specific to shared libraries (it's reproducible for me with static ones) and in theory it's not related to libraries at all - the compiler is just not required to initialize global data from a translation unit until something from it is actually used. Also, CEREAL_REGISTER_SHARED_LIBRARY must not only be in the library, it must be in the same translation unit where CEREAL_REGISTER_TYPE is put (I checked this with Clang and GCC on Ubuntu).  So, it's worth to rename the macro and update the comment.

JSON compilation issues have likely been fixed by a series of changes to long serialization on OSX (see #81 and #105).

I see. Though my solution is a bit cleaner IMO.

I haven't looked into the CRTP changes yet. However, moving prologue/epilogue functions to be member functions is likely problematic for future user-defined types since they would require direct modification of the archive itself.

The default implementations of member prologue/epilogue delegate to the non-member ones, so user-defined types will still be able to have custom overloads for them.

Had a chance to give archive-templates a better looking over and will likely include with 1.2.  I had toyed with a solution when trying to solve #46 that did something similar but ultimately went with something more light weight but less flexible.

Awesome, I'll check it out.


Firefox panic with parking_lot (Parking not supported on this platform)

Describe the bug
With the latest egui commit, egui randomly fails with the error "Parking not supported on this platform" in relation to parking_lot.
To Reproduce
Steps to reproduce the behavior:

Browse to egui site using latest commit of egui with Firefox browser
Interact with site for a bit
Observe panic in browser console

Expected behavior
The site should run fine on Firefox
Screenshots

Desktop (please complete the following information):

OS: Arch Linux
Browser: Firefox
Version: 100 (nightly)

This is on firefox though.

It's a bit dissapointing (and surprising) that you don't get a proper Rust callstack in the console - or did you accidentally crop that from the image?

Please try out https://github.com/emilk/egui/pull/1404 @Titaniumtown

Using latest code, and this is Ok,
OS: Deepin Linux
Browser: Firefox


Service HealthCheck of IngressRoute in K8s is not applied

Bug

What did you do?
Setup health check for an ExternalName service in Kubernetes as in the kubernetes-crd example.

What did you expect to see?
A repeated requests to the service to check if it is alive.
What did you see instead?
No requests at all are fired.
The IngressRoute CDR gets not fully parsed in the function   buildServicesLB of the Kubernetes provider. The HealthCheck definition should probably be copied to the wrrService config object.
In the log output the healthCheck property of the CDR is ignored:
{
  "http": {
    "routers": {
      "default-httpbin-route-899fb09e8f23f84a5a74": {
        "entryPoints": [
          "web"
        ],
        "service": "default-httpbin-route-899fb09e8f23f84a5a74",
        "rule": "Host(`httpbin.org`)"
      },
      "default-traefik-dashboard-d012b7f875133eeab4e5": {
        "entryPoints": [
          "traefik"
        ],
        "service": "api@internal",
        "rule": "PathPrefix(`/dashboard`) || PathPrefix(`/api`)"
      }
    },
    "services": {
      "default-httpbin-route-899fb09e8f23f84a5a74": {
        "loadBalancer": {
          "servers": [
            {
              "url": "http://httpbin.org:80"
            }
          ],
          "passHostHeader": true
        }
      }
    }
  },
  "tcp": {},
  "tls": {}
}

https://github.com/containous/traefik/blob/37fb5298a026fdf6518fae32a5db972e446e152a/pkg/provider/kubernetes/crd/kubernetes_http.go#L182
Output of traefik version: (What version of Traefik are you using?)

Version:      2.1.3
Codename:     cantal
Go version:   go1.13.6
Built:        2020-01-21T17:30:29Z
OS/Arch:      linux/amd64

What is your environment & configuration (arguments, toml, provider, platform, ...)?
kind: Service
apiVersion: v1
metadata:
  name: httpbin-extsrv
  namespace: default
  labels:
    app: httpbin-extsrv
spec:
  ports:
    - name: http
      protocol: TCP
      port: 80
  type: ExternalName
  externalName: httpbin.org
---
apiVersion: traefik.containo.us/v1alpha1
kind: IngressRoute
metadata:
  name: httpbin-route
  namespace: default
spec:
  entryPoints:
    - web
  routes:
    - kind: Rule
      match: Host(`httpbin.org`)
      services:
        - healthCheck:
            path: /status/503
            intervalSeconds: 10
            timeoutSeconds: 3
          kind: Service
          name: httpbin-extsrv
          port: 80
          schema: http

If applicable, please paste the log output in DEBUG level (--log.level=DEBUG switch)
time="2020-03-16T12:32:19Z" level=debug msg="Configuration received from provider kubernetescrd: {\"http\":{\"routers\":{\"default-httpbin-route-899fb09e8f23f84a5a74\":{\"entryPoints\":[\"web\"],\"service\":\"default-httpbin-route-899fb09e8f23f84a5a74\",\"rule\":\"Host(`httpbin.org`)\"},\"default-traefik-dashboard-d012b7f875133eeab4e5\":{\"entryPoints\":[\"traefik\"],\"service\":\"api@internal\",\"rule\":\"PathPrefix(`/dashboard`) || PathPrefix(`/api`)\"}},\"services\":{\"default-httpbin-route-899fb09e8f23f84a5a74\":{\"loadBalancer\":{\"servers\":[{\"url\":\"http://httpbin.org:80\"}],\"passHostHeader\":true}}}},\"tcp\":{},\"tls\":{}}" providerName=kubernetescrd
time="2020-03-16T12:32:19Z" level=debug msg="Added outgoing tracing middleware api@internal" routerName=default-traefik-dashboard-d012b7f875133eeab4e5@kubernetescrd middlewareType=TracingForwarder middlewareName=tracing entryPointName=traefik
time="2020-03-16T12:32:19Z" level=debug msg="Added outgoing tracing middleware ping@internal" middlewareName=tracing middlewareType=TracingForwarder routerName=ping@internal entryPointName=traefik
time="2020-03-16T12:32:19Z" level=debug msg="Creating middleware" entryPointName=traefik middlewareName=traefik-internal-recovery middlewareType=Recovery
time="2020-03-16T12:32:19Z" level=debug msg="Creating middleware" routerName=default-httpbin-route-899fb09e8f23f84a5a74@kubernetescrd entryPointName=web serviceName=default-httpbin-route-899fb09e8f23f84a5a74 middlewareName=pipelining middlewareType=Pipelining
time="2020-03-16T12:32:19Z" level=debug msg="Creating load-balancer" entryPointName=web serviceName=default-httpbin-route-899fb09e8f23f84a5a74 routerName=default-httpbin-route-899fb09e8f23f84a5a74@kubernetescrd
time="2020-03-16T12:32:19Z" level=debug msg="Creating server 0 http://httpbin.org:80" entryPointName=web serviceName=default-httpbin-route-899fb09e8f23f84a5a74 routerName=default-httpbin-route-899fb09e8f23f84a5a74@kubernetescrd serverName=0
time="2020-03-16T12:32:19Z" level=debug msg="Added outgoing tracing middleware default-httpbin-route-899fb09e8f23f84a5a74" middlewareName=tracing middlewareType=TracingForwarder routerName=default-httpbin-route-899fb09e8f23f84a5a74@kubernetescrd entryPointName=web
time="2020-03-16T12:32:19Z" level=debug msg="Creating middleware" middlewareName=traefik-internal-recovery middlewareType=Recovery entryPointName=web
time="2020-03-16T12:32:19Z" level=debug msg="No default certificate, generating one"
time="2020-03-16T12:32:19Z" level=debug msg="Skipping Kubernetes event kind *v1.Endpoints" providerName=kubernetescrd

duplicate of #6492


ESLint: enable no-bitwise rule

Agreed, this is not something that you want normally to do. Should be turned off per line/file.


Plenary sessions not present

The keynotes, the lightning talks, and the ACCU AGM are not listed, only the parallel sessions are present. This may be a development choice for this stage, and that is fine. Going forward though, it would be good to have them.

Yes, I kept things simple for now. I don't think I even serve up those kinds of talks right now.

Let's put that up as an enhancement for later, possibly much later. :-)


Fix for missing values in objects #161

I fixed this issue (using a different approach) in<EMAIL_ADDRESS>👍


Selecting GCC version for build and image

So, I worked with meta-tegra a while back and was having good success. I have come back and am trying to get a build going for TX2 on the Sumo branch.
Since my use case uses Cuda, I have placed the following in local.conf:
GCCVERSION = "6.%"
Unfortunately, I'm getting a Make error saying that a later GCC version is being used. Why would this be the case?
Also, I need to install GCC directly into the final image. Can you tell me how to select 6.% for this built-in GCC toolchain?

Do you have recipes for gcc 6 in your layers somewhere?  OE-Core dropped gcc 6 in sumo.

Ahh. That makes sense. Looks like the error is specifically with OpenCV anyway. Oddly, if I go back to Rocko, OpenCV fails saying that only versions 5 and earlier are supported.
Is there a meta layer that has older recipes? Do you have a recommended setup?

On Sep 20, 2018, at 3:56 AM, Matt Madison<EMAIL_ADDRESS>wrote:
Do you have recipes for gcc 6 in your layers somewhere? OE-Core dropped gcc 6 in sumo.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/madisongh/meta-tegra/issues/108#issuecomment-423139758, or mute the thread https://github.com/notifications/unsubscribe-auth/AUXTFZv_cbvrX-YD1Z8_hcNS8Tzyzhbgks5uc3ROgaJpZM4Wwl11.

Possibly related. My OpenCV version is 3.3.  I see that meta-tegra makes modifications for version 3.4.3.  Should I specifically be getting that version?

On Sep 20, 2018, at 3:56 AM, Matt Madison<EMAIL_ADDRESS>wrote:
Do you have recipes for gcc 6 in your layers somewhere? OE-Core dropped gcc 6 in sumo.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/madisongh/meta-tegra/issues/108#issuecomment-423139758, or mute the thread https://github.com/notifications/unsubscribe-auth/AUXTFZv_cbvrX-YD1Z8_hcNS8Tzyzhbgks5uc3ROgaJpZM4Wwl11.

meta-openembedded/meta-oe updated to opencv 3.4.3 in sumo, so I had to update the bbappend accordingly.  If you're still using 3.3, just copy over the bbappend and patches from the older copy in rocko and apply them locally (e.g. in your distro layer).
As for older gcc recipes, I've tried a couple of different approaches.  I've used the meta-linaro-toolchain layer, which required a bit of work since they provide the full suite of gcc/binutils/glibc, and I had to tweak some things to account for that since I wasn't using all of the meta-linaro layers.  Lately I've just been copying the gcc recipes I need into my distro layer from the prior OE-Core release.  That appears to work OK, and haven't had to add any bbappends for OE-Core recipes to compensate for the older compiler, at least for what I've been using.
Another approach would be to try some hacks to get CUDA 9 to build when using gcc 7.  Searching around I've run into some blog posts about it, and it looks like it's possible to do, but I've been more nervous about using that approach than just falling back to an older gcc.

Thanks for all of the info. Oddly my git clone from GitHub.com/openembedded/meta-openembedded uses opencv_3.3.bb on the sumo branch.

On Sep 20, 2018, at 8:32 AM, Matt Madison<EMAIL_ADDRESS>wrote:
meta-openembedded/meta-oe updated to opencv 3.4.3 in sumo, so I had to update the bbappend accordingly. If you're still using 3.3, just copy over the bbappend and patches from the older copy in rocko and apply them locally (e.g. in your distro layer).
As for older gcc recipes, I've tried a couple of different approaches. I've used the meta-linaro-toolchain layer, which required a bit of work since they provide the full suite of gcc/binutils/glibc, and I had to tweak some things to account for that since I wasn't using all of the meta-linaro layers. Lately I've just been copying the gcc recipes I need into my distro layer from the prior OE-Core release. That appears to work OK, and haven't had to add any bbappends for OE-Core recipes to compensate for the older compiler, at least for what I've been using.
Another approach would be to try some hacks to get CUDA 9 to build when using gcc 7. Searching around I've run into some blog posts about it, and it looks like it's possible to do, but I've been more nervous about using that approach than just falling back to an older gcc.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/madisongh/meta-tegra/issues/108#issuecomment-423227220, or mute the thread https://github.com/notifications/unsubscribe-auth/AUXTFaCIqzKvcZFzFNlKQCBmz6MAkQRpks5uc7UCgaJpZM4Wwl11.

Oh, oops, you're right, I misremembered.  meta-oe master has moved to 3.4.3, but sumo is still 3.3.  But the bbappend for the recipe in meta-tegra sumo branch is also for 3.3.   I only updated it in master.

Try setting SDKGCCVERSION = "7.%" so that the older compiler doesn't get used for building the host-side bits of the SDK.  I have that in my distro configuration too.


Two different kind of blogs with the same name cannot be crawled in parallel

Hi everyone,
Thank you very much for a great program.  I'm currently having a problem with downloading my liked posts.  I've followed the steps - I've logged in through Connections and have changed the privacy settings, and have added the blog to the list - but when I try to queue it, it appears for a moment in the queue and then disappears.  I have tried http://www.tumblr.com/liked/by/wallpaperfx/ and that works fine, queues as normal.
I am trying to crawl my main blog at the same time, and I'm wondering if this is a problem with having the same name for items in the queue?
I haven't seen anyone else with this problem, so please let me know if there's a simple fix that I'm missing.
Cheers!
Breakfast.
EDIT: Can confirm that it seems to be a problem with having the same name.

Thanks for open this issue.
I'll have this fixed with the next release. It's not a technical issue, the code that should prevent TumblThree from crawling the same blog twice just needs to be updated since it's now capable of crawling different kind of websites/tumblrs.


documentation of log_loss/LogLoss

It would be nice to have better documentation for log_loss (No documentation found.) and LogLoss (references unexported LogScore; the naive user wouldn't be happy with the result of help?> LogScore). I'm not familiar enough with @create_docs to write a reasonable pull request in a minute.
p.s. it seems the documentation is outdated (also, why does LogLoss etc. not appear in "measures" but only in "utility functions"?).

Closing in favour of #717 and #718 and https://github.com/alan-turing-institute/MLJ.jl/issues/890


[WIP] [Parse] [Syntax] Simplify TupleTypeRepr parsing and add attributes for Syntax

This patch adds more SourceLocs to TupleTypeRepr's elements and simplifies its implementation. Rather than adding extra trailing object arrays with indices that need to line up, instead just store a trailing array of TupleTypeReprElements.
Also removes the single trailing EllipsisLoc, which obviated the need for the HasEllipsis bit field, the removal of which obviated the need for TupleTypeReprBitfields overall.
This not done, and is currently broken.

@swift-ci please smoke test

@swift-ci please smoke test

@swift-ci please smoke test

@swift-ci please smoke test

@swift-ci please smoke test

@swift-ci please smoke test

@swift-ci please smoke test

:shipit:


[App] Add Kong IngressController

App
As part of the Venafi Development Fund, I've agreed to add Kong IngressController to arkade to support Venafi customer needs.
The openfaas community has also requested Kong Ingress and certain end-users make use of its OAuth capabilities, so it will be a win/win for everyone to have an app available
The openfaas-ingress app which generates ingress definitions should also be updated to have a matching ingress class option (if required).
More on GitHub:
https://github.com/Kong/kubernetes-ingress-controller
I would imagine this app being called kong-ingress
helm instructions
$ helm repo add kong https://charts.konghq.com
$ helm repo update

# Helm 3
$ helm install kong/kong --generate-name --set ingressController.installCRDs=false

@alexellis I can pick this up.

Sure, have you contributed before?
@Waterdrips what is the best app to use as a template?
If Alistair doesn't get back in time, look at our most recently added app in git history as a template.

Hello, good place to start looking is the Loki app, Ingess Nginx app or cert manager. Any questions let me know :)

Sure, have you contributed before?
@Waterdrips what is the best app to use as a template?
If Alistair doesn't get back in time, look at our most recently added app in git history as a template.

@alexellis @Waterdrips Yes, I had worked on converting Nginx App to use "new" pkg/apps/helm_app style

/assign: nitishkumar71

/assign: me

Added in #240 - thank you @nitishkumar71


Notification service

In GitLab by @lakhoune on May 17, 2020, 22:25
manages notifications for the user

In GitLab by @lakhoune on May 18, 2020, 24:24
changed title from {-Move notification functionality to new-} service to {+Notification+} service

In GitLab by @lakhoune on May 18, 2020, 24:24
changed the description

In GitLab by @lakhoune on May 18, 2020, 24:24
closed


Please mention the .Net version

Please mention the .Net version applicable to this example. For sure, this example doesn't work using latest .Net Framework.

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

ID: d118f070-8743-e905-2d08-dc725a4e8b5f
Version Independent ID: fae35cbd-75ae-4448-f066-7c91ccc35779
Content: Using Enumeration classes instead of enum types
Content Source: docs/architecture/microservices/microservice-ddd-cqrs-patterns/enumeration-classes-over-enum-types.md
Product: dotnet-architecture
Technology: microservices
GitHub Login: @nishanil
Microsoft Alias: nanil

Hi @taleleuma, Thanks for posting here. The .NET version currently in use is .NET 6, can you share the exact issue you are getting with .NET 6?

Hi @taleleuma, Thanks for posting here. The .NET version currently in use is .NET 6, can you share the exact issue you are getting with .NET 6?

With no mention of .Net version, I was trying the latest version of .Net Framework i.e. 4.8.x. The article is not applicable to .Net Framework as you have mentioned above. That's the point I am making. Article needs to mention about .Net 6.
.net 6 is not a part of ".net Framework"

Hi @taleleuma, thanks for the recommendation. The (index page)[https://learn.microsoft.com/en-us/dotnet/architecture/microservices/] mentions the .NET version. I believe the issue can be closed now.

The issue can be closed.


CalendarScreen: Replace toLong() with toLongOrNull()

We still get issues with toLong() in CalendarScreen and need to replace with toLongOrNull(). When doing this we also need to follow the code to see what happens. For example, changing this and then we need to add a check before sending to scheduleNotification to make sure we're not sending an empty date to it.

I dont think this is an issue now that I rebuilt calculations


DOC: complete parameter server implementation

What does this PR implement?
It completes the implementation of the parameter server in the documentation. Right now, it has invalid syntax: https://docs.dask.org/en/latest/futures.html#example-parameter-server.
Reference issues/PRs
I saw this issue when linked from https://github.com/dask/dask-examples/pull/158#discussion_r459106996.

[n/a] Tests added / passed
[n/a] Passes black dask / flake8 dask

Thanks for doing this @stsievert !
If you ever wanted to do something more real as a dask example that might also be fun :+1:

If you ever wanted to do something more real as a dask example that might also be fun 👍

That's part of why I submitted this PR. I am planning for a PR to Dask-ML to provide training for PyTorch models.
How experimental are Actors? Could they go in Dask-ML for the distributed training implementation?

How experimental are Actors?

Not so experimental that anyone else is likely to change semantics.  But experimental enough that we can change things if we need to for your work :)
Really though, they're pretty simple.  I have a hard time thinking of parts of the current API that could break.

Could they go in Dask-ML for the distributed training implementation?

I'm ok with it for situations where they're clearly the right fit.

Really though, they're pretty simple.

That's good to hear. I have a use case where I should use them, so that provides more motivation. I've been holding off because there's no tools to monitor actors. I'm most interested in profiling, though it'd be nice to have a task stream too.

I'm ok with it for situations where they're clearly the right fit.

They're not the right fit for this parameter server. The client should be the parameter server and task the gradients with computing the gradients. That's a lot simpler.
For the eventual Dask-ML PR, I have a rough implementation at https://github.com/stsievert/adadamp/pull/6. Better documentation is at https://docs.stsievert.com/adadamp.

I'm most interested in profiling,

I think that they should still participate in the statistical profiler (but I haven't checked, regardless it would be easy to do)

though it'd be nice to have a task stream too

That might be a bit tougher.  One of the advantages of Actors is that there isn't any centralized reporting.  We could always set something up custom if necessary, but these probably won't drop into the existing dashboard system easily.

Hrm, there are some interesting Parquet CI failures here.  They're almost certainly unrelated.
@rjzamora @martindurant are these familiar to you?

Hrm, there are some interesting Parquet CI failures here. They're almost certainly unrelated.
@rjzamora @martindurant are these familiar to you?

Yup - #6346 should deal with them, but those tests need to be relaxed a bit to deal with pyarrow 1.0

The rendering here doesn't look quite right:

xref: https://docs.dask.org/en/latest/futures.html#example-parameter-server

Thanks for providing this example @stsievert
I've been thinking about this example in the context of https://github.com/dask/dask-examples/pull/158, and I'm a bit confused about why Dask is needed.
In particular, I think the example is trying to demonstrate how you could create a very large model that couldn't fit on one machine using Dask to shared the (very large number of) parameters across a number of computers. However by running params = ps.get('parameters').result() you'll be pulling the (very large number of) parameters back to the Client/one machine, which could potentially crash that machine?
Sorry if I am mistaken. Thanks again!

I think the example is trying to demonstrate how you could create a very large model that couldn't fit on one machine

I mostly implemented this example to resolve invalid syntax (from a bad merge?). I suppose Dask might be used if the worker machines have GPUs and the client doesn't.
I think splitting the model up with two Actors would be a useful addition.


defaultConfigRef is not cleared when ReactQueryConfigProvider is unmounted

Working within Storybook, stories are unmounted when switching between each other. Using "decorator" functions, this is useful because we can manage different query configs for different stories.
However, I see that defaultConfigRef is updated when config changes but not reset to the original defaults when the provider unmounts. This persists config across Stories even when config provider is unmounted.
I have reproduced this in a test case and can submit a PR to address this.

Yeah, a PR would be great!

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


fix: support for skip-labeling parameter for GitHub action

Adds support and documentation for the skipLabeling option when running release-please from GitHub Actions.
This option in the config are ignored when running in release-please-action, and only honored when you pass it as an option via a command line. This PR adds the same support to GitHub action.

@chingor13 Could you take a look at this, please.