feat: 🎸 Add support for btreeset portfolio ID

Description
Updates polkadot types using the latest BtreeSet changes on the core side (wrt instruction portfolios). Updates other logic to handle the BtreeSet values as well
Breaking Changes
NA
JIRA Link
DA-1342
Checklist

[ ] Updated the Readme.md (if required) ?

/fast-forward

:tada: This PR is included in version 26.0.0-alpha.6 :tada:
The release is available on:

npm package (@alpha dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 26.0.0-beta.3 :tada:
The release is available on:

npm package (@beta dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Card Header work

Summary

Updated card header to support edit and view actions, exposed capabilities view object containing booleans in prop.
Added prettierrc rule to disallow same-line jsx bracket closure

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.55.0 :tada:
The release is available on npm package (@release-1.x dist-tag)
Your semantic-release bot :package::rocket:


text_colors.py one color not visible

color and its text of the first color in jp.Tailwind.tw_dict['text_color'] is not visible:

examples/tutorial/tailwind/text_colors.py

The first text has the color transparent so this is working. Problem here seems to be that orange and teal are not working as expected.


Fix typo: "canel" -> "cancel"

I can't find reference to "canel" in the code, so hopefully this change won't impact anything negatively.

Don't merge this - I'm almost 100% certain that this is the queue/table name

Yup: DO NOT MERGE unless you're going to fix the broken queue name, and figure out how to migrate existing users
lhill@st2:~$ sudo rabbitmqctl list_queues | fgrep st2.actionrunner.
st2.actionrunner.canel	0
st2.actionrunner.req	0
st2.actionrunner.work	0
lhill@st2:~$

Update: saw @LindsayHill comment.
Needs a migration or we just leave it as is and call it "easter egg"? :)

I saw it a while ago while putting together some monitoring docs. I'd love to get it fixed, but we'll have to figure out a way of doing it that doesn't cause existing users too much pain. It's possible that they'll be OK if they restart ST2 services. Don't really know all the implications.

I don't believe it needs any special treatment. It should just create the new queue and use it.
Looks like everything consuming it uses it through the return of get_worker so everyone should automagically use the new queue.

It will leave the canel channel hanging around though :D

On related note, we can rename it to camel :)

At a minimum, highlight it in upgrade/change notes. Some ppl are monitoring those queues - e.g. @codyaray

Codecov Report

Merging #3247 into master will increase coverage by 0.11%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #3247      +/-   ##
==========================================
+ Coverage   77.75%   77.85%   +0.11%
==========================================
  Files         433      433
  Lines       22431    22395      -36
==========================================
- Hits        17439    17435       -4
+ Misses       4992     4960      -32

Impacted Files
Coverage Δ

st2actions/st2actions/worker.py
84.78% <ø> (ø)
:white_check_mark:

st2api/st2api/controllers/v1/actionalias.py
70.75% <ø> (-11.65%)
:x:

st2client/st2client/base.py
72.22% <ø> (-8.08%)
:x:

...on/st2common/transport/connection_retry_wrapper.py
75% <ø> (-5.77%)
:x:

st2client/st2client/commands/auth.py
68.13% <ø> (-2.46%)
:x:

st2common/st2common/query/base.py
83.46% <ø> (-1.5%)
:x:

st2api/st2api/controllers/v1/timers.py
76.92% <ø> (-1.28%)
:x:

...2reactor/st2reactor/container/process_container.py
42.47% <ø> (-0.91%)
:x:

st2common/st2common/models/api/rbac.py
80.43% <ø> (-0.82%)
:x:

st2common/st2common/services/triggers.py
92.27% <ø> (-0.52%)
:x:

... and 40 more

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 b5f170d...c627b3c. Read the comment docs.

Checked out the branch. It is as I said.
ubuntu@st2vagrant:~/st2$ sudo rabbitmqctl list_queues | grep st2
st2.actionrunner.cancel 0
st2.actionrunner.canel  0
st2.actionrunner.req    0
st2.actionrunner.work   0

ubuntu@st2vagrant:~/st2$ st2 run core.local cmd=date
.
id: 58ae1679c4da5f1893b6a29b
status: succeeded
parameters:
  cmd: date
result:
  failed: false
  return_code: 0
  stderr: ''
  stdout: Wed Feb 22 22:53:46 UTC 2017
  succeeded: true
ubuntu@st2vagrant:~/st2$

ubuntu@st2vagrant:~/st2$ st2 run core.local cmd="echo Start; sleep 30; echo End;" -a
To get the results, execute:
 st2 execution get 58ae1726c4da5f1893b6a2b0
ubuntu@st2vagrant:~/st2$ st2 execution cancel 58ae1726c4da5f1893b6a2b0
action execution with id 58ae1726c4da5f1893b6a2b0 canceled.
ubuntu@st2vagrant:~/st2$ st2 execution list
+--------------------------+------------------------+--------------+-------------------------+-------------------------------+-------------------------------+
| id                       | action.ref             | context.user | status                  | start_timestamp               | end_timestamp                 |
+--------------------------+------------------------+--------------+-------------------------+-------------------------------+-------------------------------+
| 58ae1679c4da5f1893b6a29b | core.local             | stanley      | succeeded (3s elapsed)  | Wed, 22 Feb 2017 22:54:58 UTC | Wed, 22 Feb 2017 22:55:01 UTC |
| 58ae1726c4da5f1893b6a2b0 | core.local             | stanley      | canceled (11s elapsed)  | Wed, 22 Feb 2017 22:56:38 UTC | Wed, 22 Feb 2017 22:56:49 UTC |
+--------------------------+------------------------+--------------+-------------------------+-------------------------------+-------------------------------+

I'll update the changelog and submit a new commit for review later tonight.

@LindsayHill  thanks for looking out for me. good to know!

LGTM.
Perhaps also not a bad idea to document this in upgrade notes.

@warrenvw Let's resolve conflicts & merge it!
Upcoming v2.4.0 is best for this change.

This is an "empty" PR.


Pushed objects interacts with dead objects sometimes

wee need to prevent the dead object from blocking trace channel. maybe add the trace response to the object saved states list.
i made this level too , this is a reference from the game :

fixed by disabling trace response when the object is dead


WIP: Do not checkin: Testing flipping an experimental flag.

Please provide a description for what this PR is for.
And to help us figure out who should review this PR, please
put an X in all the areas that this PR affects.
[ ] Configuration Infrastructure
[ ] Docs
[ ] Installation
[ ] Networking
[ ] Performance and Scalability
[ ] Policies and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure

@ozevren: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

integ-galley-local-presubmit-tests-release-1.3
f682ecb3a550a4be89aadd3c6255bc5c7fc9f995
link
/test integ-galley-local-presubmit-tests-release-1.3

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.

@ozevren: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

integ-galley-local-presubmit-tests-release-1.3
f682ecb3a550a4be89aadd3c6255bc5c7fc9f995
link
/test integ-galley-local-presubmit-tests-release-1.3

integ-new-install-k8s-presubmit-tests-release-1.3
f682ecb3a550a4be89aadd3c6255bc5c7fc9f995
link
/test integ-new-install-k8s-presubmit-tests-release-1.3

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.

@ozevren: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

integ-galley-local-presubmit-tests-release-1.3
f682ecb3a550a4be89aadd3c6255bc5c7fc9f995
link
/test integ-galley-local-presubmit-tests-release-1.3

integ-new-install-k8s-presubmit-tests-release-1.3
f682ecb3a550a4be89aadd3c6255bc5c7fc9f995
link
/test integ-new-install-k8s-presubmit-tests-release-1.3

e2e-dashboard-release-1.3
f682ecb3a550a4be89aadd3c6255bc5c7fc9f995
link
/test e2e-dashboard-release-1.3

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.

@ozevren: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

integ-galley-local-presubmit-tests-release-1.3
f682ecb3a550a4be89aadd3c6255bc5c7fc9f995
link
/test integ-galley-local-presubmit-tests-release-1.3

integ-new-install-k8s-presubmit-tests-release-1.3
f682ecb3a550a4be89aadd3c6255bc5c7fc9f995
link
/test integ-new-install-k8s-presubmit-tests-release-1.3

e2e-dashboard-release-1.3
f682ecb3a550a4be89aadd3c6255bc5c7fc9f995
link
/test e2e-dashboard-release-1.3

istio-codecov-release-1.3
f682ecb3a550a4be89aadd3c6255bc5c7fc9f995
link
/test istio-codecov-release-1.3

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.

@ozevren: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

integ-galley-local-presubmit-tests-release-1.3
f682ecb3a550a4be89aadd3c6255bc5c7fc9f995
link
/test integ-galley-local-presubmit-tests-release-1.3

integ-new-install-k8s-presubmit-tests-release-1.3
f682ecb3a550a4be89aadd3c6255bc5c7fc9f995
link
/test integ-new-install-k8s-presubmit-tests-release-1.3

e2e-dashboard-release-1.3
f682ecb3a550a4be89aadd3c6255bc5c7fc9f995
link
/test e2e-dashboard-release-1.3

istio-codecov-release-1.3
f682ecb3a550a4be89aadd3c6255bc5c7fc9f995
link
/test istio-codecov-release-1.3

integ-mixer-k8s-presubmit-tests-release-1.3
f682ecb3a550a4be89aadd3c6255bc5c7fc9f995
link
/test integ-mixer-k8s-presubmit-tests-release-1.3

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.

@ozevren: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

integ-galley-local-presubmit-tests-release-1.3
f682ecb3a550a4be89aadd3c6255bc5c7fc9f995
link
/test integ-galley-local-presubmit-tests-release-1.3

integ-new-install-k8s-presubmit-tests-release-1.3
f682ecb3a550a4be89aadd3c6255bc5c7fc9f995
link
/test integ-new-install-k8s-presubmit-tests-release-1.3

e2e-dashboard-release-1.3
f682ecb3a550a4be89aadd3c6255bc5c7fc9f995
link
/test e2e-dashboard-release-1.3

istio-codecov-release-1.3
f682ecb3a550a4be89aadd3c6255bc5c7fc9f995
link
/test istio-codecov-release-1.3

integ-mixer-k8s-presubmit-tests-release-1.3
f682ecb3a550a4be89aadd3c6255bc5c7fc9f995
link
/test integ-mixer-k8s-presubmit-tests-release-1.3

e2e-dashboard_istio_release-1.3
f682ecb3a550a4be89aadd3c6255bc5c7fc9f995
link
/test e2e-dashboard_istio_release-1.3

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.

@ozevren: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

integ-galley-local-presubmit-tests-release-1.3
f682ecb3a550a4be89aadd3c6255bc5c7fc9f995
link
/test integ-galley-local-presubmit-tests-release-1.3

integ-new-install-k8s-presubmit-tests-release-1.3
f682ecb3a550a4be89aadd3c6255bc5c7fc9f995
link
/test integ-new-install-k8s-presubmit-tests-release-1.3

e2e-dashboard-release-1.3
f682ecb3a550a4be89aadd3c6255bc5c7fc9f995
link
/test e2e-dashboard-release-1.3

istio-codecov-release-1.3
f682ecb3a550a4be89aadd3c6255bc5c7fc9f995
link
/test istio-codecov-release-1.3

integ-mixer-k8s-presubmit-tests-release-1.3
f682ecb3a550a4be89aadd3c6255bc5c7fc9f995
link
/test integ-mixer-k8s-presubmit-tests-release-1.3

e2e-dashboard_istio_release-1.3
f682ecb3a550a4be89aadd3c6255bc5c7fc9f995
link
/test e2e-dashboard_istio_release-1.3

integ-galley-local-tests_istio_release-1.3
f682ecb3a550a4be89aadd3c6255bc5c7fc9f995
link
/test integ-galley-local-tests_istio_release-1.3

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.

@ozevren: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

integ-galley-local-presubmit-tests-release-1.3
f682ecb3a550a4be89aadd3c6255bc5c7fc9f995
link
/test integ-galley-local-presubmit-tests-release-1.3

integ-new-install-k8s-presubmit-tests-release-1.3
f682ecb3a550a4be89aadd3c6255bc5c7fc9f995
link
/test integ-new-install-k8s-presubmit-tests-release-1.3

e2e-dashboard-release-1.3
f682ecb3a550a4be89aadd3c6255bc5c7fc9f995
link
/test e2e-dashboard-release-1.3

istio-codecov-release-1.3
f682ecb3a550a4be89aadd3c6255bc5c7fc9f995
link
/test istio-codecov-release-1.3

integ-mixer-k8s-presubmit-tests-release-1.3
f682ecb3a550a4be89aadd3c6255bc5c7fc9f995
link
/test integ-mixer-k8s-presubmit-tests-release-1.3

e2e-dashboard_istio_release-1.3
f682ecb3a550a4be89aadd3c6255bc5c7fc9f995
link
/test e2e-dashboard_istio_release-1.3

integ-galley-local-tests_istio_release-1.3
f682ecb3a550a4be89aadd3c6255bc5c7fc9f995
link
/test integ-galley-local-tests_istio_release-1.3

codecov_istio_release-1.3
f682ecb3a550a4be89aadd3c6255bc5c7fc9f995
link
/test codecov_istio_release-1.3

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.


Make TestPowApprox and TestPow table-driven and add more test cases

Commenting to create an issue for post v10 work (not in this PR):
Make TestPowApprox and TestPow table-driven and add more test cases
Originally posted by @p0mvn in https://github.com/osmosis-labs/osmosis/pull/1755#discussion_r894791047

@p0mvn, I think we should randomized the test, may be have a python file generating all the random test values to test against. We should treat complex math functions like this since they have many edge cases. wdyt?

Good idea. However, while I agree that randomized tests would be useful and we could have a separate issue for it, I think that we still need some well-thought-out table-driven tests.
Table-driven unit tests help to ensure that we cover the edge cases that are expected by the programmer.
On the other hand, randomized tests help to detect unanticipated errors.
So, in my opinion, both are useful but for different reasons.

python file generating all the random test values

I believe that @ValarDragon is working on introducing and improving a simulator that would help us with randomized tests across the repository without having to rely on external scripts.
@catShaark  would you like to create a separate issue for this suggestion so that we continue discussing it there?

Good idea. However, while I agree that randomized tests would be useful and we could have a separate issue for it, I think that we still need some well-thought-out table-driven tests.
Table-driven unit tests help to ensure that we cover the edge cases that are expected by the programmer.
On the other hand, randomized tests help to detect unanticipated errors.
So, in my opinion, both are useful but for different reasons.

python file generating all the random test values

I believe that @ValarDragon is working on introducing and improving a simulator that would help us with randomized tests across the repository without having to rely on external scripts.
@catShaark would you like to create a separate issue for this suggestion so that we continue discussing it there?

ohh, sure thing, lemme close this issue with good old table test first, then I'll put up a new issue like you said

Randomized tests for these functions would look different to the simulator work! I wonder how they'd work with go fuzz

I caught this unexpected behavior of Pow, It returns incorrect result ( off by so many digits ) for large base ( close to 2 ) and large exp. I guess we should have a new issue about this
		{
			// large base, large exp
			base:           sdk.MustNewDecFromStr("1.9999"),
			exp:            sdk.MustNewDecFromStr("123.456"),
			expectedResult: sdk.MustNewDecFromStr("14497004198753074745855987268357259398.755071824935534437"),
		},

The problem partly comes from sdk.Dec Power, it's not correct for large exp input either, what should we do?

Was your decision to allow for error tolerance if it is within precision?
I did not do anything to fix the problem. I think we have no choice but to simply accept it as a limitation of sdk.Dec. Well, If we really want to fix the problem, we have to fix sdk.Dec Power first which is a big deal so we should not include the fix into this PR anyway.
Are you unblocked now?
I definitely don't know how to fix this precision problem.

From playing with the test, I draw the conclusion that the larger the out put number, the worse precision we get


What are the paginated reports REST API limitation ?

[Enter feedback here]

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

ID: 53195679-7a58-c111-3814-fccf4cc38854
Version Independent ID: ee9e8e36-45e1-8029-4f9a-b1d41ef4a3f1
Content: Export Power BI paginated reports API - Power BI
Content Source: powerbi-docs/developer/embedded/export-paginated-report.md
Service: powerbi
Sub-service: powerbi-developer
GitHub Login: @KesemSharabi
Microsoft Alias: kesharab

Thanks for your comment, @kirank5. I’ll investigate and get back to you.

Hi @kirank5,
As far as I'm aware there are no limitations.
Thanks,
Kesem


Can get card type?

ex : Master or Visa
Can we?

You are looking for getInstrumentType().
You can get one from Masked wallet:
mMaskedWallet.getInstrumentInfos()[0].getInstrumentType()
API reference: https://developers.google.com/android/reference/com/google/android/gms/wallet/InstrumentInfo.html#getInstrumentType()
But beware:
This type should not be displayed to the user, but can be used when the details of a user's instrument are needed. (from the DOCS)

@8ofproject
Thank you.


New tabs and panes do not open

Version: 1.0.91
Platform: linux 4.15.0-64-generic
Plugins: none
After opening Terminus, closing it, rebooting my PC and opening Terminus again, it's not possible to open new tabs or panes in the first Terminus window opened. When starting a second copy of Terminus, all those things work fine.
The developer console shows the following error:
errors.ts:35 ERROR Error: Uncaught (in promise): Error: ENOENT: no such file or directory, readlink '/proc/5790/cwd'
Error: ENOENT: no such file or directory, readlink '/proc/5790/cwd'
    at resolvePromise (/opt/Terminus/resources/app.asar/node_modules/zone.js/dist/zone.js:831)
    at /opt/Terminus/resources/app.asar/node_modules/zone.js/dist/zone.js:741
    at rejected (tslib.es6.js:63)
    at ZoneDelegate.invoke (/opt/Terminus/resources/app.asar/node_modules/zone.js/dist/zone.js:391)
    at Object.onInvoke (ng_zone.ts:273)
    at ZoneDelegate.invoke (/opt/Terminus/resources/app.asar/node_modules/zone.js/dist/zone.js:390)
    at Zone.run (/opt/Terminus/resources/app.asar/node_modules/zone.js/dist/zone.js:150)
    at /opt/Terminus/resources/app.asar/node_modules/zone.js/dist/zone.js:889
    at ZoneDelegate.invokeTask (/opt/Terminus/resources/app.asar/node_modules/zone.js/dist/zone.js:423)
    at Object.onInvokeTask (ng_zone.ts:262)
defaultErrorLogger @ errors.ts:35
ErrorHandler.handleError @ error_handler.ts:51
next @ application_ref.ts:230
schedulerFn @ event_emitter.ts:110
SafeSubscriber.__tryOrUnsub @ Subscriber.ts:265
SafeSubscriber.next @ Subscriber.ts:207
Subscriber._next @ Subscriber.ts:139
Subscriber.next @ Subscriber.ts:99
Subject.next @ Subject.ts:70
EventEmitter.emit @ event_emitter.ts:92
(anonymous) @ ng_zone.ts:296
ZoneDelegate.invoke @ /opt/Terminus/resources/app.asar/node_modules/zone.js/dist/zone.js:391
Zone.run @ /opt/Terminus/resources/app.asar/node_modules/zone.js/dist/zone.js:150
NgZone.runOutsideAngular @ ng_zone.ts:218
onHandleError @ ng_zone.ts:296
ZoneDelegate.handleError @ /opt/Terminus/resources/app.asar/node_modules/zone.js/dist/zone.js:395
Zone.runGuarded @ /opt/Terminus/resources/app.asar/node_modules/zone.js/dist/zone.js:164
_loop_1 @ /opt/Terminus/resources/app.asar/node_modules/zone.js/dist/zone.js:694
api.microtaskDrainDone @ /opt/Terminus/resources/app.asar/node_modules/zone.js/dist/zone.js:703
drainMicroTaskQueue @ /opt/Terminus/resources/app.asar/node_modules/zone.js/dist/zone.js:608
Promise.then (async)
scheduleMicroTask @ /opt/Terminus/resources/app.asar/node_modules/zone.js/dist/zone.js:584
ZoneDelegate.scheduleTask @ /opt/Terminus/resources/app.asar/node_modules/zone.js/dist/zone.js:413
onScheduleTask @ /opt/Terminus/resources/app.asar/node_modules/zone.js/dist/zone.js:301
ZoneDelegate.scheduleTask @ /opt/Terminus/resources/app.asar/node_modules/zone.js/dist/zone.js:404
Zone.scheduleTask @ /opt/Terminus/resources/app.asar/node_modules/zone.js/dist/zone.js:238
Zone.scheduleMicroTask @ /opt/Terminus/resources/app.asar/node_modules/zone.js/dist/zone.js:258
scheduleResolveOrReject @ /opt/Terminus/resources/app.asar/node_modules/zone.js/dist/zone.js:879
resolvePromise @ /opt/Terminus/resources/app.asar/node_modules/zone.js/dist/zone.js:825
(anonymous) @ /opt/Terminus/resources/app.asar/node_modules/zone.js/dist/zone.js:741
(anonymous) @ index.js:38
(anonymous) @ fs.js:153

This error happens on every click of the new tab button, or every time the key shortcut for opening a split pane is pressed.
I'm running Terminus on Ubuntu 18.04 LTS, with the KDE window manager (kubuntu-desktop package is installed), and the default shell is zsh.

If I set my current profile's working directory, it starts working, and if I empty the current profile's working directory, the bug reappears.
Bug yes:

Bug no:

https://github.com/Eugeny/terminus/blob/181c5230201659a90af55212deb8b75c93482d94/terminus-terminal/src/services/sessions.service.ts#L294
This is the line that's causing the error.

I'm preparing a fix that simply handles any errors from fs.readlink and returns null instead.

I've pushed a PR with a fix for this!


Error: EPERM: operation not permitted when "npm i"

Hi, i am using Nove v14 and latest sp-dev-fx-controls-react, but got error. please help thanks

Hi @quantrpeter,
I'm not sure this error is related to SPFx Controls.
Did you try to install another package than this one?
If so, can you test the following actions:

Remove node_modules folder and run npm i
If problem still exists, run npm cache clean

Also, I've had a look at you package.json file, it seems that you're trying to use v3 of the Controls within a SPFx v1.12 project. FYI, it's compatible only with SPFx v1.13 or higher, as stated here.

This problem in my experience is almost exclusively antivirus-related and a general issue with Node/NPM and not package-specific. Since running npm i spams network requests and creates hundreds of thousands of tiny files as fast as it can, the antivirus goes all out scanning everything, which on NTFS can create some horrid lock or race condition situations that can end up causing IO to just fail like above.
The solution usually is to add exclusions to your development directory, the NPM cache, and the Node process.


Range Slider does not update when setting *SelectedValue in code

When setting either of these properties, the visual display does not update. The value does stick and can be retrieved but there is no visual indication of the change.

I'll take a look at this as soon as possible. Thanks for the find!

Fixed as part of PR #9.
Restructured the code for the RangeSlider control.


Upload files to a new study is taking so long

I tried to upload a biom file that is very small (~200kb) and I left it for one full day and the percentage sign did not change at all. Why is that?

Hi @negin1986,
Could you send us an email to<EMAIL_ADDRESS>with your study id so we can take a closer look (*)? AFAIK there is nothing that should make uploading any kind of files hard or slower ...
Closing here as the plan is to follow up via email.
(*)

Thank you for your reply. I just sent an email.


Issue with +918700******

Hey,
this is new series for Reliance Jio in India. Please add this.
Thanks.

Update Lib to V8.0.0. Fix this issue.


WIP: Install stylelint

[x] Add stylelint to all packages

Codecov Report
All modified lines are covered by tests :white_check_mark:
see 12 files with indirect coverage changes
:loudspeaker: Thoughts on this report? Let us know!.

Unresolved issues
stylelint does not read the file specified by --config.
It does not work as specified in the path specified by --config.
No warnings are issued whether or not there is a file in the path specified by --config.
I may be misunderstanding something and overlooking it.

Intense structural changes
Ideally, this should be done in a separate Pull Request, but I have made major changes to the directory structure of the monorepo.
I stopped creating the config/* hierarchy and moved it to the project root.
If there are too many types of config, you have to describe the combination of the project and config every time you add a new component. This is a pain.
I have abolished the subcommands of lint, format, test, etc. for each package and unified them in the project root.


Make image leaner

The present image thakes %8min to build and it takes 6.83GB on docker hub.
It must be made lighter

One approach to investigate should be making a multistage Dockerfile. The first one should install cudatoolkit and the second should take the ptxas executable from there. This should allow to avoid using the space of cudatoolkit.


[pytorch] move pytorch JNI into separate package

Change-Id: I78c950aa2ea3866d0a702617a2fcbb290d3e6a5e
Description
Brief description of what this PR is about

If this change is a backward incompatible change, why must this change be made?
Interesting edge cases to note here

Codecov Report

Merging #1385 (bb246d8) into master (bb5073f) will decrease coverage by 1.58%.
The diff coverage is 50.19%.

@@             Coverage Diff              @@
##             master    #1385      +/-   ##
============================================
- Coverage     72.08%   70.50%   -1.59%
- Complexity     5126     5234     +108
============================================
  Files           473      487      +14
  Lines         21970    23030    +1060
  Branches       2351     2516     +165
============================================
+ Hits          15838    16237     +399
- Misses         4925     5527     +602
- Partials       1207     1266      +59

Impacted Files
Coverage Δ

api/src/main/java/ai/djl/modality/cv/Image.java
69.23% <ø> (-4.11%)
:arrow_down:

...i/djl/modality/cv/translator/BigGANTranslator.java
21.42% <ø> (-5.24%)
:arrow_down:

...odality/cv/translator/BigGANTranslatorFactory.java
33.33% <0.00%> (+8.33%)
:arrow_up:

...nslator/InstanceSegmentationTranslatorFactory.java
14.28% <0.00%> (-3.90%)
:arrow_down:

.../modality/cv/translator/YoloTranslatorFactory.java
8.33% <0.00%> (-1.67%)
:arrow_down:

...i/djl/modality/cv/translator/YoloV5Translator.java
5.69% <0.00%> (ø)

...odality/cv/translator/YoloV5TranslatorFactory.java
8.33% <0.00%> (-1.67%)
:arrow_down:

...modality/nlp/embedding/TrainableWordEmbedding.java
45.00% <0.00%> (-3.34%)
:arrow_down:

...pi/src/main/java/ai/djl/ndarray/BytesSupplier.java
54.54% <0.00%> (-12.13%)
:arrow_down:

...i/src/main/java/ai/djl/ndarray/NDArrayAdapter.java
15.23% <0.00%> (-0.83%)
:arrow_down:

... and 139 more

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 29c18f5...bb246d8. Read the comment docs.


Using Http with map to get json response doesn't seem to work

Trying to use http module from angular2 in nativescript, but I am getting this error:
file:///app/tns_modules/angular2/src/platform/serv
er/parse5_adapter.js:55:75: EXCEPTION: TypeError: _this.http.request(address, options)
                            .map is not a function. (In '_this.http.request(address, options)

This is working in the browser and also including in both places the rxjs map module
import 'rxjs/add/operator/map';

If I remove this from the browser I am getting the same message. But with nativescript even if I add it, it doesnt work...
What can be wrong here? Is there any working example using the http module?
Posted here, but so far no ideas, so adding it here as well
http://stackoverflow.com/questions/34899835/using-map-in-nativescript-with-angular2

@eesdil, I had an early experiment with the http module, but then the API changed and I never updated it.
What example are you trying to port from the browser version? Could you post a repro project that I can run locally?

Thanks. It Would be too complicated to share and use it probably.  I will create a repo bit later to be able to check it.

Hmm. I created one, but yet there is no backend to connect and it doesn't start :)... but you can see the code at least for now.
https://github.com/eesdil/test_mobile

I got it running here. I had to add the typescript hooks and some of the compat d.ts files (the commit before that), but nothing more. I wonder if the problem occurs just for certain types of requests or parameters.

Thank you. I am checking it. It can happen that I am not getting back result (wrong ip address, as localhost cannot be accessed in the emulator), thats why it fails. But I am getting a bit frustrated as it takes 10 minutes to start the debugger. And Without debugger I just get immediate crash.

With the default android emulator it is a nightmare..., but using the genymotion it is working pretty well. So the http (map, etc) working fine in android, tried in linux and osx.
But in ios emulator I have the same error using the same code:
.js:79:28: JS ERROR EXCEPTION: Error during evaluation of "tap"
        ORIGINAL EXCEPTION: TypeError: this.http.request(address)
                    .map is not a function. (In 'this.http.request(address)
                    .map(function (res) { return res.json(); })', 'this.http.request(address)
                    .map' is undefined)

Didnt write yesterday, but even this is working in android, in the subscribe function I am getting string instead of json. Strangely if I remove the map function, I am not getting the result (just the headers) in the subscribe function.

This looks like a bug in the iOS require implementation. I'll update this issue when I know more.

@eesdil
Can you please confirm that the issue is resolved with the latest(0.0.36) release of nativescript-angular.
I have tested it with the sample-ng-http project and everything seems to work fine.

Thanks. I will check it and let you know.

@eesdil I'm closing the issue - please reopen it if the problem reoccurs.

It seems it is working fine in the sample-ng-http project, but not in mine... But at least it means it can work, just have to find the reason. thanks anyway

I tried to get an Http request as the following too, in one of my components:
`import {Component, OnInit} from "@angular/core";
import {Http} from "@angular/http";
import "rxjs/Rx";
@Component({
selector:"list",
providers:[Http],
template:        <StackLayout>                           <Button text="GO TO LOGIN" [nsRouterLink]="['/login']"></Button>             <StackLayout>                              </StackLayout>         </StackLayout>
})
export class ListComponent implements OnInit{
private _data;
constructor(private _http:Http){

}
ngOnInit(){
    this._http.get("[URL to get the Json data]").map(res=> res.json()).subscribe(res=> this._data=res);
    console.log(this._data[0].name);
}

}`
But I get the following error:
Error: Uncaught (in promise): Error: Error in ./ListComponent class ListComponent_Host - inline template:0:0 caused by: No provider for ConnectionBackend!


only_include_with_project_file setting not respected

I'm not sure if this is a bug, or I'm just misunderstanding what this setting is supposed to do.
I assume that the only_include_with_project_file = true should only send data to wakatime if there is a .wakatime-project file present.
my .wakatime.cfg file
[settings]
api_key = MY_API_KEY
only_include_with_project_file = true

Then, I create one project with the .wakatime-project file, which works properly and overrides the project name with the one I've specified.

In my second project, the project is still reported with the directory name as the project name.

I expect only Qardisc Admin/API to show in my projects list, but I see both projects.

What exactly is the only_include_with_project_file supposed to do?
Thanks

When looking at this chart, is the coding activity still being tracked after you added the only_include_with_project_file setting? If the project was created before adding that setting, then it won't be deleted... it just won't show up in future coding activity.

@alanhamlett Yes.  I have confirmed that on the above-linked chart, the project is still being tracked.
Some additional information:
This problem is occurring on two different machines, using two different IDE plugins.

MacOS (10.13.5) running PyCharm with the most-recent version of the wakatime plugin.  Wakatime cli is version 10.2.1
MacOS (10.13.5) running the XCode wakatime plugin (installed fresh today)

This problem occurred today as I was helping one of our developers get this setup on their machine so we can begin using waktime teams.  He wants to keep some of his personal projects from being recorded in wakatime.

Oh, sorry about this. The example config had a typo. Using this config should work:
[settings]
api_key = XXX
include_only_with_project_file = true


Updates readme

Description
Updates readme

updates image and links
add CodeCov badge
removes CodeClimate badge (is not useful in React apps)

@martinpovolny @Hyperkid123

Codecov Report

Merging #121 into master will not change coverage.
The diff coverage is n/a.

@@          Coverage Diff           @@
##           master    #121   +/-   ##
======================================
  Coverage    74.7%   74.7%
======================================
  Files          36      36
  Lines         431     431
  Branches       61      61
======================================
  Hits          322     322
  Misses         87      87
  Partials       22      22

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 3adf1d2...dd81463. Read the comment docs.


Update ceilometer.py

@lloydwuhb
fix unit of network incomming / outgoing , MB -> B

Please confirm the latest revising.


Analysis fails: Model hash not found

Description
Some models are now failing analysis due to the model hash not being found. This has potentially been caused by mlagility.analysis using the model's weights to calculate the hash.
Reproducing
Command to reproduce:
benchit models/timm/mobilenetv2_035.py --analyze-only

Expected error:
Traceback (most recent call last):
  File "/net/home/dhnoronha/miniconda3/envs/dse_slurm/bin/benchit", line 8, in <module>
    sys.exit(benchitcli())
  File "/net/home/dhnoronha/mlagility/src/mlagility/cli/cli.py", line 571, in main
    args.func(args)
  File "/net/home/dhnoronha/mlagility/src/mlagility/cli/cli.py", line 47, in benchmark_command
    benchmark_files(
  File "/net/home/dhnoronha/mlagility/src/mlagility/api/script_api.py", line 330, in benchmark_files
    benchmark_script(
  File "/net/home/dhnoronha/mlagility/src/mlagility/api/script_api.py", line 272, in benchmark_script
    models_found = evaluate_script(tracer_args, script_args)
  File "/net/home/dhnoronha/mlagility/src/mlagility/analysis/analysis.py", line 567, in evaluate_script
    spec.loader.exec_module(module)
  File "<frozen importlib._bootstrap_external>", line 843, in exec_module
  File "<frozen importlib._bootstrap>", line 219, in _call_with_frames_removed
  File "/net/home/dhnoronha/mlagility/models/timm/mobilenetv2_035.py", line 19, in <module>
    model(inputs)
  File "/net/home/dhnoronha/miniconda3/envs/dse_slurm/lib/python3.8/site-packages/torch/nn/modules/module.py", line 1194, in _call_impl
    return forward_call(*input, **kwargs)
  File "/net/home/dhnoronha/mlagility/src/mlagility/analysis/analysis.py", line 442, in forward_spy
    model_info = tracer_args.models_found[model_hash]
KeyError: '9110a638'

@jeremyfowers @ramkrishna2910

Proposed solution:

implement the long-term solution and revert the workaround mentioned here: https://github.com/groq/mlagility/issues/316#issuecomment-1581373641 (closing #316 in the same PR)
Add a test to test/analysis.py to prevent this kind of break in the future (perhaps as simple as running benchit models/timm/mobilenetv2_035.py --analyze-only and maybe 1 or two more tiny models from timm?)


Updated JSON and added tech images

Description of Proposed Changes

Updated the JSON file with more info from the Google Sheets document
Added the images for the techs
Linked the email/github/portfolio/linkedin images properly
Created placeholders for the group photos
Added NSS Logo at top of screen

Steps to Test

git fetch --all
git checkout kn-json
If you've previously pulled down this branch, run git pull origin kn-json to get the updates
http-server
Check to make sure placeholder images are there and that the tech images appear properly

🥇 🏆


TO: Fix ADDSSLKeys unit test(s) by recreating x509v1/x509v3 certificate(s) with 20+ year duration

Component: Traffic Ops
Purpose: x509 SSL/TLS certificate/keys validation unit test(s) fix
Description: Many of the inline x509 certificates used in the deliveryservice/keys_test.go expired causing the unit tests to fail.
What does this PR (Pull Request) do?

All inline certificates regenerated to have at least a 20+ year expiration.
All inline certificates/certificate-chains now have the text output from openssl included just above the PEM block start marker.
All private key(s) now have the text output from openssl included just above the PEM block start marker.

Which Traffic Control components are affected by this PR?
[x] Traffic Ops
What is the best way to verify this PR?

Clone this PR
Compile/Build all of Traffic Ops Golang
Run at minimum the unit tests in the deliveryservice package

$  go test github.com/apache/trafficcontrol/traffic_ops/traffic_ops_golang/deliveryservice  -v

All SSL keys related tests should now PASS.  Output should match the following:

=== RUN   TestGetDeliveryServicesMatchLists
--- PASS: TestGetDeliveryServicesMatchLists (0.00s)
=== RUN   TestMakeExampleURLs
--- PASS: TestMakeExampleURLs (0.00s)
=== RUN   TestDecodePrivateKeyPKCS8RSA2048
--- PASS: TestDecodePrivateKeyPKCS8RSA2048 (0.00s)
=== RUN   TestDecodePrivateKeyPKCS1RSA2048
--- PASS: TestDecodePrivateKeyPKCS1RSA2048 (0.00s)
=== RUN   TestDecodePrivateKeyECDSANISTPrime256V1
--- PASS: TestDecodePrivateKeyECDSANISTPrime256V1 (0.02s)
=== RUN   TestDecodePrivateKeyECDSANISTPrime256V1WithoutParams
--- PASS: TestDecodePrivateKeyECDSANISTPrime256V1WithoutParams (0.00s)
=== RUN   TestDecodePrivateKeyECDSANISTSecP384R1
--- PASS: TestDecodePrivateKeyECDSANISTSecP384R1 (0.01s)
=== RUN   TestDecodePrivateKeyECDSANISTSecP384R1WithoutParams
--- PASS: TestDecodePrivateKeyECDSANISTSecP384R1WithoutParams (0.01s)
=== RUN   TestDecodeRSAPrivateKeyBadData
--- PASS: TestDecodeRSAPrivateKeyBadData (0.00s)
    keys_test.go:2202: expected error message: private key validation error: no RSA private key PEM blocks found
=== RUN   TestDecodeECDSAPrivateKeyBadData
--- PASS: TestDecodeECDSAPrivateKeyBadData (0.00s)
    keys_test.go:2213: expected error message: private key validation error: no EC private key PEM blocks found
=== RUN   TestDecodePrivateKeyRSAEncrypted
--- PASS: TestDecodePrivateKeyRSAEncrypted (0.00s)
    keys_test.go:2224: expected error message: private key validation error: encrypted private key not supported - header: 4,ENCRYPTED
=== RUN   TestDecodePrivateKeyECDSAEncrypted
--- PASS: TestDecodePrivateKeyECDSAEncrypted (0.00s)
    keys_test.go:2235: expected error message: private key validation error: encrypted private key not supported - header: 4,ENCRYPTED
=== RUN   TestVerifyAndEncodeCertificateBadData
--- PASS: TestVerifyAndEncodeCertificateBadData (0.00s)
=== RUN   TestVerifyAndEncodeCertificateSelfSignedCertKeyPairDSA
--- PASS: TestVerifyAndEncodeCertificateSelfSignedCertKeyPairDSA (0.00s)
    keys_test.go:2254: expected error message: cert/key validation error: DSA public key algorithm unsupported
=== RUN   TestVerifyAndEncodeCertificateSelfSignedX509v1
--- PASS: TestVerifyAndEncodeCertificateSelfSignedX509v1 (0.03s)
=== RUN   TestVerifyAndEncodeCertificateSelfSignedNoSkiAkiCertKeyPair
--- PASS: TestVerifyAndEncodeCertificateSelfSignedNoSkiAkiCertKeyPair (0.00s)
=== RUN   TestVerifyAndEncodeCertificateSelfSignedCertKeyPair
--- PASS: TestVerifyAndEncodeCertificateSelfSignedCertKeyPair (0.00s)
=== RUN   TestVerifyAndEncodeCertificateSelfSignedCertKeyPairMisMatchedPrivateKey
--- PASS: TestVerifyAndEncodeCertificateSelfSignedCertKeyPairMisMatchedPrivateKey (0.00s)
    keys_test.go:2344: expected error message: cert/key (rsa) mismatch error: RSA public N modulus value mismatch
=== RUN   TestVerifyAndEncodeCertificateSelfSignedNoServerAuthExtKeyUsage
--- PASS: TestVerifyAndEncodeCertificateSelfSignedNoServerAuthExtKeyUsage (0.00s)
    keys_test.go:2356: expected error message: certificate (x509v3) validation error: server certificate missing 'serverAuth' extended key usage
=== RUN   TestVerifyAndEncodeCertificateSelfSignedRSANoKeyEnciphermentKeyUsage
--- PASS: TestVerifyAndEncodeCertificateSelfSignedRSANoKeyEnciphermentKeyUsage (0.00s)
    keys_test.go:2369: expected error message: cert/key (rsa) validation: no keyEncipherment keyUsage extension present in x509v3 server certificate
=== RUN   TestVerifyAndEncodeCertificateCASignedCertKeyPair
--- PASS: TestVerifyAndEncodeCertificateCASignedCertKeyPair (0.00s)
=== RUN   TestVerifyAndEncodeCertificateCASignedCertKeyPairWithRootCA
--- PASS: TestVerifyAndEncodeCertificateCASignedCertKeyPairWithRootCA (0.00s)
=== RUN   TestVerifyAndEncodeCertificateCASignedNoSkiAkiCertKeyPair
--- PASS: TestVerifyAndEncodeCertificateCASignedNoSkiAkiCertKeyPair (0.00s)
=== RUN   TestVerifyAndEncodeCertificateCASignedNoSkiAkiCertKeyPairWithRootCA
--- PASS: TestVerifyAndEncodeCertificateCASignedNoSkiAkiCertKeyPairWithRootCA (0.00s)
=== RUN   TestVerifyAndEncodeCertificateECDSASelfSignedCertificateKeyPairWithoutDigitalSignatureKeyUsage
--- PASS: TestVerifyAndEncodeCertificateECDSASelfSignedCertificateKeyPairWithoutDigitalSignatureKeyUsage (0.00s)
    keys_test.go:2489: expected error message: cert/key (ecdsa) validation error: no digitalSignature keyUsage extension present in x509v3 server certificate
=== RUN   TestVerifyAndEncodeCertificateECDSASelfSignedCertificateKeyPair
--- PASS: TestVerifyAndEncodeCertificateECDSASelfSignedCertificateKeyPair (0.00s)
=== RUN   TestVerifyAndEncodeCertificateECDSASelfSignedCertificateKeyPairECDisabled
--- PASS: TestVerifyAndEncodeCertificateECDSASelfSignedCertificateKeyPairECDisabled (0.00s)
    keys_test.go:2509: expected error message: cert/key validation error: ECDSA public key algorithm unsupported for non-DNS delivery service type
=== RUN   TestVerifyAndEncodeCertificateECDSASelfSignedCertificateKeyPairWithoutParams
--- PASS: TestVerifyAndEncodeCertificateECDSASelfSignedCertificateKeyPairWithoutParams (0.00s)
=== RUN   TestVerifyAndEncodeCertificateECDSASelfSignedCertificateKeyPairMisMatchedPrivateKey
--- PASS: TestVerifyAndEncodeCertificateECDSASelfSignedCertificateKeyPairMisMatchedPrivateKey (0.00s)
    keys_test.go:2529: expected error message: cert/key (ecdsa) mismatch error: ECDSA public X value mismatch
PASS
ok  	github.com/apache/trafficcontrol/traffic_ops/traffic_ops_golang/deliveryservice

If this is a bug fix, what versions of Traffic Ops are affected?

The following criteria are ALL met by this PR

[x] This PR includes tests OR I have explained why tests are unnecessary
[x] This PR includes documentation OR I have explained why documentation is unnecessary
[x] This PR includes an update to CHANGELOG.md OR such an update is not necessary
[x] This PR includes any and all required license headers
[x] This PR ensures that database migration sequence is correct OR this PR does not include a database migration
[x] This PR DOES NOT FIX A SERIOUS SECURITY VULNERABILITY (see the Apache Software Foundation's security guidelines for details)

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/trafficcontrol-PR/3616/
Test PASSed.


feat(scanresult): resource cleanup status refactor

Description
Creates the base status API object in the openapi spec.
Updates the resource cleanup state for the new object, and also enforces the proper state transitions when the API is called.
Type of Change
[x] Bug Fix
[ ] New Feature
[ ] Breaking Change
[x] Refactor
[ ] Documentation
[ ] Other (please describe)
Checklist

[x] I have read the contributing guidelines
[x] Existing issues have been referenced (where applicable)
[x] I have verified this change is not present in other open pull requests
[x] Functionality is documented
[x] All code style checks pass
[x] New code contribution is covered by automated tests
[x] All new and existing tests pass

LGTM!
General question: The PR description states: Creates the base status API object in the openapi spec.
But in the PR we are creating a specific status object for resourceCleanup.
I think it is a good idea to make the status object more general since we use it a lot in all the objects.


Fail to let bot join because fail to get GetMeetingInfoData

First of all, really appreciated the impressive work you did.
I am trying to set up bot to join the zoom meeting and do the audio/video recording.
I tried both main and audio branch. However, I fail to let bot join the meeting due to http get request failure in GetMeetingInfoData function
$ go run examples/record-video/videorecoder.go
panic: Get "https:///wc/ping/?ts=0&auth=&rwcToken=&dmz=1": http: no Host in request URL
I had a live zoom session and used the right meeting number, meeting password, client id as api key ad client secret as api secret. This works in the Chris's master branch.
Could you help me with this?

Should work now, see #7.


CMake refactoring for system DT

Nothing in here directly adds system DT support; it's all just cleanups and rearranging things to make adding it easier. No functional changes expected.

@nordicjm fixed, thanks!

@tejlmand I just dropped the last patch since it's causing controversy. My goal here is just to isolate non-controversial patches that can go in now. We'll deal with printing in the system DT support PRs.


Update the notice in the MessageDialog documentation to be technically correct

ContentDialog works only in XAML apps while MessageDialog works in any UWP app so I updated the notice about recommending replacing MessageDialog with ContentDialog to indicate that it's for XAML apps only.

@ahmed605 : Thanks for your contribution! The author(s) have been notified to review your proposed change.


Azure - new E*_v5 instances support nvme devices

Converting Virtual Machines running Linux from SCSI to NVMe


Fix(backend): Denoise Masks being applied at the wrong time

What type of PR is this? (check all applicable)

[ ] Refactor
[ ] Feature
[x] Bug Fix
[ ] Optimization
[ ] Documentation Update
[ ] Community Node Submission

Have you discussed this change with the InvokeAI team?

[x] Yes
[ ] No, because:

Have you updated all relevant documentation?

[x] Yes
[ ] No

Description
Denoise Mask was being applied at the wrong time in the step loop, creating an off-by-one error. Each step during masked denoise was computing based on an unmasked region that was 1 step more noised than it should have been.
Related Tickets & Documents

Closes #5966

QA Instructions, Screenshots, Recordings
This effect has been seen regularly in SDXL inpainting, since those models are better at matching the surrounding textures during denoising. It was most prevalent on smooth or otherwise featureless backgrounds. In anime models, it tends to present as sparkles or polkadots.

With very low step counts (8-step LCM) there was a fringe effect noticed on the edges of expanded masks.

Results after fix

Inpainting LCM still has some color drift, possibly affected by the VAE round trip. That can be investigated later on. The noise artifacting at least is gone.

Merge Plan
This PR can be merged when approved
Added/updated tests?

[ ] Yes
[x] No : does not affect API for the diffusion pipeline

The results seem fine but the progress images not show that the entire image is being denoised rather than just the area. Is that intended?

The results seem fine but the progress images not show that the entire image is being denoised rather than just the area. Is that intended?

It's expected, not intended. Previously the code was acting on all tensors in step_output with a special case to detect and replace the values in the "predicted original sample". The result of this process converges to the initial image, but the callback gets a preview that is updated each step.
We can add some extra code to capture this again if we want previews to be more stable.
Incidentally, it looks like some samplers call that output "denoised" so we weren't applying that logic to all samplers anyway.

Think it’s a nice to have if we can get the preview back, but I think it should be a follow on. This is solving a big pain point on inpainting that I think worth getting in ASAP

Incidentally, it looks like some samplers call that output "denoised" so we weren't applying that logic to all samplers anyway.

I've noticed this at some point and was wondering what was happening! Good to know.
@dunkeroni Barring a fix for the progress images, is there any reason to not merge this?

@dunkeroni Barring a fix for the progress images, is there any reason to not merge this?

I was going to explain a framework for how I want to hijack the denoise_mask input on the node and generalize it into a denoise_guidance type that allows code injection into multiple points from other nodes... but for now here's a patch that makes the inpaint preview work again.
Also I was wrong. It's just LCM sampler that uses "denoised". A lot of the others have no field at all. This patch just takes whatever is there if there is something and otherwise uses the current latents to create a "pred_original_sample" that the progress callback can use.

Tested. Seems good. Works as advertised. Great job.

Thanks dunkeroni


I387 ventilation systems

This branch should be merged to continue work on #220 and other related
issues of Gabriel Happle.
Archetype properties are exemplary. No research has been done so far.
All AC cooled buildings ('type_cs = T3') are mechanically ventilated. So
are also all industrial and special use buildings (server, coolroom,
etc).
None of the buildings have economizers or night flushing.

I might suggest an easy way around that. We might discuss it at the beginning of next week. It would be easier to explain it if we meet..
On 18 Nov 2016, at 17:04, Gabriel Happle <notifications<EMAIL_ADDRESS>wrote:
@gabriel-happle commented on this pull request.

In cea/demand/thermal_loads.pyhttps://github.com/architecture-building-systems/CEAforArcGIS/pull/410:

@@ -1148,12 +1148,12 @@ def get_temperatures(locator, prop_HVAC):
:type prop_HVAC: Gdf

 Sample data (first 5 rows):

            Name type_cs type_ctrl type_dhw type_hs

0     B154862      T0        T1       T1      T1
1     B153604      T0        T1       T1      T1
2     B153831      T0        T1       T1      T1
3  B302022960      T0        T0       T0      T0
4  B302034063      T0        T0       T0      T0

            Name type_cs type_ctrl type_dhw type_hs MECH_VENT WIN_VENT HEAT_REC NIGHT_FLSH ECONOMIZER

@JIMENOFONSECAhttps://github.com/JIMENOFONSECA: also it makes it almost impossible to study new technologies.
Imagine you want to equip all buildings with mechanical ventilation systems with a new type of heat exchanger. You just have to modify one key with the same value for all cases. In your case, you would have to modify every key of the heating system with an individual key based on the existing heating system (e.g. for building with T3 you have to change to T23, but for a building with T2, you would have to change to T54 to get the desired technical system configuration).
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/architecture-building-systems/CEAforArcGIS/pull/410, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AIjrglvI8eCJI--f0sDgZW5hBoyPopmAks5q_WoygaJpZM4K2Fcz.

I guess we solved the problem with gabriel in the direction you say. There should be an update soon. The json step is provocative
Best, Jimeno
On 23 Nov 2016, at 21:05, Daren Thomas <notifications<EMAIL_ADDRESS>wrote:
@daren-thomas commented on this pull request.

In cea/demand/thermal_loads.pyhttps://github.com/architecture-building-systems/CEAforArcGIS/pull/410:

@@ -1148,12 +1148,12 @@ def get_temperatures(locator, prop_HVAC):
:type prop_HVAC: Gdf

 Sample data (first 5 rows):

            Name type_cs type_ctrl type_dhw type_hs

0     B154862      T0        T1       T1      T1
1     B153604      T0        T1       T1      T1
2     B153831      T0        T1       T1      T1
3  B302022960      T0        T0       T0      T0
4  B302034063      T0        T0       T0      T0

            Name type_cs type_ctrl type_dhw type_hs MECH_VENT WIN_VENT HEAT_REC NIGHT_FLSH ECONOMIZER

maybe we need to discuss the whole systems side a bit better anyway. we probably need to have: heat emission systems, heat generation systems, cool generation systems, cool emission systems, ventilation systems etc., but also allow multiple per building? currently, we are using a tabular format and that might be what is creating our problem. i am becoming more convinced, that the building systems description should be a hierarchical system which would also lend itself to an object oriented approach. we could then have a data helper type script to convert the tabular input we currently have into a hierarchical (e.g. JSON) description. what do you think?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/architecture-building-systems/CEAforArcGIS/pull/410, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AIjrgsPGMP9mVP-7o3PB07TA6uBUXVoRks5rBDocgaJpZM4K2Fcz.

provocative good or provocative bad?

good :)., but it can wait a while,
On 24 Nov 2016, at 3:52 pm, Daren Thomas <notifications<EMAIL_ADDRESS>wrote:
provocative good or provocative bad?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/architecture-building-systems/CEAforArcGIS/pull/410#issuecomment-262711655, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AIjrgrhcDQPtqPrUsxcrHyT-gwTaTko1ks5rBUJbgaJpZM4K2Fcz.

@gabriel-happle could you check the conflicts?

I have merged the thermal_loads.py file that had a merge conflict. I can't run any tests, though, as this branch introduces new input columns and it seems they are not present in the reference cases?

@gabriel-happle this pull request is creating a bottle neck, is it close to be ready to merge? or should it be closed by now and reopen later?

Sorry guys, I will do it again as discussed with @JIMENOFONSECA last week.


Custom components example doesn't scan on iPhone

Issue: https://github.com/xypwn/scadqr/blob/2f38b77a8343d70522721816b58e4752976f23d5/demo-custom.png scans fine on all Android devices I tested (probably all using zxing), but doesn't scan at all on iPhone.
Possible solution: Use rounded rectangles instead of circles (which might also look better aesthetically).

Possibly solved in 3749afe (I don't have an iPhone available to verify at the moment, but I will reopen if this appears to be an issue again)


Validation errors/warning in XSL-FO generated using DITA OT

I generate PDF from a sample DITA Map using DITA OT 2.x (but probably it's the same issue with older versions). The PDF is generated succesfully. But if you open the XSL-FO file, it has lots of problems reported in it. And they seem to be quite easily fixable.
Like:
 <fo:wrapper id="tasks:_unique_d87e216"/>

 Description: value of attribute "id" is invalid; must be an XML name without colons

We should try to avoid ":" when constructing such ID attributes.
 <fo:basic-link color="blue" font-style="italic"
                                              internal-destination="flowers:autumn:chrysanthemums:_unique_d87e988"

value of attribute "internal-destination" is invalid; must be an XML name without colons

Same thing again, colons in ID references.
  <fo:page-number-citation
                                              ref-id="flowers:autumn:chrysanthemums:_unique_d87e988"
                                              />

Same thing again, colons in ID references.
    <fo:list-item-label end-indent="label-end()"
                                keep-together.within-line="always"
                                keep-with-next.within-line="always">

 Error: attribute "keep-with-next.within-line" not allowed here

The specs seems not to allow that attribute there.

That looks like indexing code. Instead of colon we should use e.g. code point from Unicode private use area, that way we're pretty sure delimiter will not clash with index key value.

Sure, as long as it remains a valid ID value. Or use instead of it some pattern like "-.-" or "-_-"

Since in theory it's possible that an index term may use "-.-" in the key, IMO it's better to just use a code point from PUA, e.g. simply 

Ran across this when trying to debug a crash during my PDF build -- the PDF is 1500+ pages with 25+ pages of index, and the log is so full of errors about : that I can't find the actual errors. I tried replacing every one of the : characters in an index with  as suggested and AH didn't like that character either --
AHFCmd :WARNING: Invalid property value: id="publications_unique_d117e24383".

Thought I had a relatively easy fix with the commit above -- turn the full term into a hash, which replaces any special characters that might be invalid (I found a lot of them, with spaces, slashes, parens, etc). But somehow turning it into a hash breaks the index-see-also processing that comes later in XSLT.

Maybe you can try an easier fix and replace ":" and maybe some other characters with underline both in the Java code and in the XSLT which looks for it. Even if the original index key value contains an underline, I do not see a reason why this would not work.

It should work for the simple case - what I discovered with this specific document is that we have index entries full of characters that are not valid in IDs, and I was trying for a simple solution that handled all of these. For example, the document I was working with here had several thousand index terms, and most of them still reported errors after removing : because they had commas or spaces. I definitely don't want to have to handle 100 cases of "If I find x replace with y" so the hash initially seemed like a good way to guarantee a valid ID.

(Initially I just tried to fix the FO file by replacing : ... then spaces ... then commas ... and then ( and ) showed up ... then slashes ... then I stopped looking for new ones, that could go on for a long time and still not be complete.)

Maybe replace all non alphanumeric chars with underline.


Unable to delete last tag of an entity using navigator client

I am using 1.0 version of navigator-sdk-model/client and Navigator 2.4.1. When I try to delete the last tag in an entity using the client, the operation fails to change the metadata. It works if there is at least one tag left after deletion. But I am able to delete the last tag in the UI. Code used to delete tag is provided below.
  MyEntity myEntity = new MyEntity(ENTITY_NAME);
  myEntity.removeTags(args[1]);
  navPlugin.write(myEntity);

I will have to see whether the error is client or server side. It'll be early next week before I'll be able to have time to take a look. In the mean time, try one of the following arounds:

Try to use the override tags instead of remove tags
You can also send a PUT request to /entities/{id}  (this is basically what the UI does)

As per off-github convo, this has been fixed server side in the upcoming release. Closing this issue for now, can re-open if necessary.


access log: Add support for downstream TLS session ID

Description: Make the TLS session ID accessible as a method on the Ssl::ConnectionInfo object. Add a new %DOWNSTREAM_TLS_SESSION_ID% directive to the file access logger, and a tls_session_id field to the gRPC access logger to expose the session ID to access logging / header injection. Update unit tests to validate the new access log fields.
Risk Level: Low
Testing: Unit tests, ad hoc manual tests
Docs Changes: Added documentation to docs/root/configuration/access_log.rst describing the new
Release Notes: Added https://github.com/envoyproxy/envoy/compare/master...mikegrass:session-id-access-logs?expand=1#diff-d8d3e33358b55e6c0466dd1bb5f40c79R42
Incremental progress on #3296.

@zuercher thanks for the quick review! I've addressed your feedback. Let me know if you have any other questions or concerns!

/assign @dio


Cancelling async operations

Hi!
I'm using PuppeteerSharp to generate PDFs for webpages.
Is there a way to cancel any of the async methods like
await page.PdfAsync(outputFile, myCancellationToken);
// or
await new BrowserFetcher().DownloadAsync(BrowserFetcher.DefaultRevision, myCancellationToken);

Since some of these operations can take quite some time, it would be nice to give the user the option to cancel it, if he accidentally triggered the PDF generation.
Thanks!

It would be great to implement this.
I think it might be easy to implement in places where we use native async methods, like DownloadAsync. It's quite tricky when we call chromium methods because we don't have a native method we can pass the token to because we are building TaskCompletionSources and fulfilling them when we get the right message from Chromium.
But it's a nice to have for sure.

@kblok given that we are using TaskCompletionSource, when we initialize the TCS we could just do:
if (cancellationToken.CanBeCanceled)
{
    var registration = cancellationToken.Register(() => tcs.TrySetCanceled());
    tcs.ContinueWith(_ => registration.Dispose());
}

Then when the message does come back from Chromium, we'd call tcs.TrySetResult() and it would noop becuase the task was already in a terminal state.

We are currently using cancellation token registration on the top level that disposes browser like this:
try
{
    using var _ = cancellationToken.Register(() => browser.Dispose());
    await using var page = await browser.NewPageAsync();
    await page.SetContentAsync(html);
    // ...
}
catch (PuppeteerException) when (cancellationToken.IsCancellationRequested)
{
    throw new OperationCanceledException();
}

This is not ideal and we would rather use built-in cancellation support, if it's made available.
Operations using WebSocketTransport.SendAsync can use native cancellation support provided by WebSocket on message sending and, as it was noted above, cancellation token registration can be used on message receiving. This would cover a big amount of methods, like NewPageAsync() or SetContentAsync() in the example above.


Use generated gql types instead of a parser like yup/zod

See discussion here for more context: https://github.com/remix-austin/remixaustin-com/pull/71#pullrequestreview-1225189955

I'm not actually sure we can use types generated from Meetup's GraphQL, looks like they don't allow introspection on their GraphQL endpoint. Feels like that kind of defeats some of the purpose behind using GraphQL in the first place 🙃
I attempted to use the GraphQL Code Generator which gave me this error:
 Failed to load schema from https://api.meetup.com/gql:
      GraphQL introspection is not allowed by Apollo Server, but the query contained __schema or __type. To enable introspection, pass introspection: true to ApolloServer in production
      GraphQLError: GraphQL introspection is not allowed by Apollo Server, but the query contained __schema or __type. To enable introspection, pass introspection: true to ApolloServer in …
      at createGraphQLError

Additionally, even their playground doesn't allow you to see the schema 😢
c.c. @colbywhite just so you don't completely redo the same work I've done. Do let me know if you find something else out, otherwise I think we're going to have to stick with parsing all the responses

Calling bankruptcy on all discussions and issues today. Going to start revamping the direction of this project, so stay tuned 🚀


bug: Fix UID/GID problem in a systematic way

Description
Possible solution:

Use GID=0 for envd user
Use root as the default user

Reference: https://github.com/boxboat/fixuid

I will try to fix this.
/assign @gaocegege

https://docs.bitnami.com/tutorials/why-non-root-containers-are-important-for-security

We should not make envd to root user group by default.

https://github.com/moby/moby/issues/7198
I was thinking if we can mount the root-owned volume to the container, as the envd (UID 1000) owned volume. But it does not work. The mounted volume cannot update the UID/GID.
https://github.com/moby/moby/issues/7198


Question about cloning the queue

Thank you for providing such clear and easy-to-follow code for this great project! I was just curious about line 146 in builder.py:
l_neg = torch.einsum('nc,ck->nk', [q, self.queue.clone().detach()])

Is it necessary to make a copy of the queue at all? Does this introduce unnecessary overhead? Or am I misunderstanding something?

self.queue is in-place modified in self._dequeue_and_enqueue, so a clone is necessary.
If not cloned, you should see an error raised by pytorch.


Don't use blanket "except" in Reporter.publish

https://github.com/bugout-dev/humbug/blob/main/python/humbug/report.py#L128
See comment by u/ElevenPhonons on Reddit: https://www.reddit.com/r/Python/comments/m84h10/humbug_usage_and_crash_reports_for_python/grh7ads?utm_source=share&utm_medium=web2x&context=3
We should at least handle KeyboardInterrupt in a more responsible manner than just eating them up. This should probably apply to everything that gets caught that isn't a subclass of Exception in the exception hierarchy: https://docs.python.org/3/library/exceptions.html#exception-hierarchy

@kompotkot already fixed this.


AboutBox resizes when being used (license text too wide)

Currently, when you open the About dialog window and click through to display the license you notice that the window is resizing. It seems that this is due to the fact that portion of the license text that is written in CAPTIAL LETTERS is too wide to display.
Is there a way to make the dialog window calculate the required width before opening the dialog window? (Kind of, window.pack() in other languages.)

I vaguely remember that wxPython has things like that. Try .Layout() or
.Fit().
On Wed, Sep 26, 2018 at 11:35 AM Peter Bittner<EMAIL_ADDRESS>wrote:

Currently, when you open the About dialog window and click through to
display the license you notice that the window is resizing. It seems that
this is due to the fact that portion of the license text that is written in
CAPTIAL LETTERS is too wide to display.
Is there a way to make the dialog window calculate the required width
before opening the dialog window? (Kind of, window.pack() in other
languages.)
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/cool-RR/PythonTurtle/issues/116, or mute the thread
https://github.com/notifications/unsubscribe-auth/AADdypt163MsM5IiC-q6zI07lDbkECJcks5uezw9gaJpZM4W6J4h
.

I understand. If you'd like to create our own custom class for that, that's
a solution.
On Wed, Sep 26, 2018 at 12:25 PM Peter Bittner<EMAIL_ADDRESS>wrote:

Access to that function(s) seems to be hidden by the AboutBox
https://github.com/cool-RR/PythonTurtle/blob/master/pythonturtle/application.py#L210-L211
class. We don't control the Show() method. That's probably the price for
convenience.
Similar issues: (StackOverflow)

xPython StaticText Issue in my Code
https://stackoverflow.com/questions/22542264/wxpython-statictext-issue-in-my-code
wxpython sizer layout issues
https://stackoverflow.com/questions/51230178/wxpython-sizer-layout-issues

Related classes:

wx.adv.AboutBox
https://wxpython.org/Phoenix/docs/html/wx.adv.functions.html?highlight=aboutbox#wx.adv.AboutBox
wx.adv.AboutDialogInfo
https://wxpython.org/Phoenix/docs/html/wx.adv.AboutDialogInfo.html

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/cool-RR/PythonTurtle/issues/116#issuecomment-424647742,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AADdyrHlepYHwkamWQvZwuv31RLY1jruks5ue0fogaJpZM4W6J4h
.

Probably not worth the effort.


Arg type should provide functions to check the kind

It would be nice that type Arg would provide some methods to check the argument kind
Currently there's isError available but primitive types could be checked  too.
isStirng()
isStirngPtr()
....


Disable and remove Remove Preferences node functionality from GUI

Per #1, this issue will remove the Remove Preferences node functionality from the GUI.

Fixed by 5af217ac0db2df9910d8b36b9124753206b26c7e.


Update dns_zoneedit.sh

move new validation to _zoneedit_api() {

I apparently don't fully understand the pull mechanisms. The pull I did used my fork of dns_zoneedit.sh and added the validation to the _zoneedit_api() { sub but my version does not have the validation in the add and rm subs and the merge did not remove the validations there. I don't think it hurts but the _err message includes $cmd which is not set by the add and rm subs so there could be some undefined consequences. What did I need to do so that the merge removed lines in the main branch that I did not have in my fork?

I have merged your pull request, e.g added the if ... in the api function. I have also removed the superfluous if _err ... in the add and rm functions. Improved the pfsense installation documentation and patch for acme.inc. I have also tested this under pfsense. I will soon push to github. Please review dns_zoneedit.sh if OK then test standalone.

Looks good and test good standalone here. Thank you for your work on this project. Definitely my new goto letsencrypt cert tool.

Your welcome and you contributed. Happy holiday.


calico-kube-controllers: Run as non-root by default for the armv7, ppc64le and s390x images

Description

This PR adapts the armv7, ppc64le and s390x images of calico-kube-controllers to run as non-root by default. Similar to https://github.com/projectcalico/kube-controllers/pull/565 and https://github.com/projectcalico/calico/pull/6346 (the changes that adapted the amd64 and arm64 images to run as non-root).
Related issues/PRs

Not applicable
Todos

[ ] Tests
[ ] Documentation
[x] Release note

Release Note

The armv7, ppc64le and s390x images of calico-kube-controllers now runs as non-root by default (similar to the amd64 and arm64 imagaes).

Reminder for the reviewer
Make sure that this PR has the correct labels and milestone set.
Every PR needs one docs-* label.

docs-pr-required: This change requires a change to the documentation that has not been completed yet.
docs-completed: This change has all necessary documentation completed.
docs-not-required: This change has no user-facing impact and requires no docs.

Every PR needs one release-note-* label.

release-note-required: This PR has user-facing changes. Most PRs should have this label.
release-note-not-required: This PR has no user-facing changes.

Other optional labels:

cherry-pick-candidate: This PR should be cherry-picked to an earlier release. For bug fixes only.
needs-operator-pr: This PR is related to install and requires a corresponding change to the operator.

/sem-approve

go build github.com/projectcalico/calico/libcalico-go/lib/net: mkdir /tmp/go-build357731998/b238/: no space left on device
github.com/gogo/protobuf/protoc-gen-gogo/descriptor
go build github.com/gogo/protobuf/protoc-gen-gogo/descriptor: mkdir /tmp/go-build357731998/b244/: no space left on device
google.golang.org/protobuf/internal/detrand
go build google.golang.org/protobuf/internal/detrand: mkdir /tmp/go-build357731998/b249/: no space left on device
google.golang.org/protobuf/internal/pragma
go build google.golang.org/protobuf/internal/pragma: mkdir /tmp/go-build357731998/b253/: no space left on device

Looks like we're running out of disk space now due to needing multitple copies of the qemu image.
We probably need to update semaphore.yml.tpl to match what calico/node does:

Main build only builds amd64.
have separate build steps for other architectures.

And then run make generate

@caseydavenport how we proceed with this PR? Is there anything that I have to fix in the PR? The things you explained in https://github.com/projectcalico/calico/pull/6749#issuecomment-1261212837 look like CI/CD issues. Are these issues a blocker?

@ialidzhikov yeah, we can't merge this until the CI is passing.
My previous comment suggested how to modify this PR to hopefully get the tests passing. You'll need to make a minor change to .semaphore/semaphore.yml.tpl and then run make gen-semaphore-yaml.
I'd recommend using calico/node's CI configuration as an example, specifically these lines: https://github.com/projectcalico/calico/blob/master/.semaphore/semaphore.yml.tpl#L468-L473
Will want to be copied to this section: https://github.com/projectcalico/calico/blob/master/.semaphore/semaphore.yml.tpl#L508-L510
And then change the Makefile here: https://github.com/projectcalico/calico/blob/master/kube-controllers/Makefile#L141
So that ci just runs image and not image-all

Oof, a lot of time has passed on this one. @ialidzhikov not sure if you're still interested in progressing this - I think it's still relevant though if you are. Otherwise I'll close.

@caseydavenport We have unified Dockerfiles into one so all non-amd64 images also run as non-root now. I believe this PR can be closed.


Remove clone from each model startup for ComfyUI

First pass at cleaning up this example. The should probably make it easy to add the models to the cache but will just take it step by step and hopefully invite other people to contribute.
@htrivedi99 would you mind taking a look please? I tested the dev deployment.

looks good to me :)
I ran the truss as well just to make sure everything still works


Emacspeak

Project description
Emacspeak is a speech interface that allows visually impaired users to interact independently and efficiently with the computer.
Audio formatting—a technique pioneered by AsTeR—and full support for W3C's Aural CSS (ACSS) allows Emacspeak to produce rich aural presentations of electronic information. By seamlessly blending all aspects of the Internet such as Web-surfing and messaging, Emacspeak speech-enables local and remote information via a consistent and well-integrated user interface. Available free of cost on the Internet, Emacspeak has dramatically changed how the author and thousands of blind and visually impaired users around the world interact with the personal computer and the Internet. A rich suite of task-oriented tools provides efficient speech-enabled access to the audio desktop and evolving semantic WWW. When combined with Linux running on low-cost PC hardware, Emacspeak/Linux provides a reliable, stable speech-friendly solution that opens up the Internet to visually impaired users around the world.
Metadata

homepage URL: http://emacspeak.sourceforge.net/
source URL: https://github.com/tvraman/emacspeak
license: GPL
platforms: Linux

@symbiont-matthew-piziak I've created a derivation but I don't use emacspeak. There're lot of irrelevant files it the sources, I copied what I think is important.
Could you try to install it and test if it works?

Hi @Dema! Thank you so much. I've tried installing it, and I get emacspeak and espeak in /nix/store, though not on my PATH. The espeak executable, when invoked directly, works as expected. Moreover, loading the emacspeak-setup.el leaves Emacs in a state of buffer has no process errors on most actions—presumably the ones that are supposed to create sounds. This feels like an issue where Emacs is not able to start and communicate with the espeak speech server.

@matthew-piziak Could you, please retest it? I think I managed to make it work. if I launch ./run or do
export DTK_PROGRAM=$(which espeak) it works.

@Dema What do you do after DTK_PROGRAM?
Should run get put onto the PATH as emacspeak or something?

I'm not sure how it supposed to work. Looks like "run" is just an example and you just need to add emacspeak-setup.el in you .emacs. My emacs skill are a bit rusty :smile: I could try to rename run as emacspeak and put it into $PATH..

This is silly question...but how do I know which emacspeak-setup.el in my /nix/store/ is the most recently built one?

I think you need the one that is in /run/current-system/sw/share/....

Hmmm. I still get buffer has no process when I load emacspeak-setup.el.
I'm sorry I'm probably doing something wrong here. :/

Using nix-shell -p emacsPackages.emacspeak --run "emacspeak" it should start emacs correctly configured for reading.


traffic_dump: don't dump cookies from the wire

Cookies are often very sensitive information and should not be logged.
This change modifies traffic_dump to not dump the actual cookies from
the wire.

--promiscuous-mode is added in case the user wants to dump sensitive
headers.

--sensitive-fields is added so the user can treat customize things to label arbitrary fields as
sensitive.

This should also go to 7.x, but it won't merge cleanly. Once this is approved, I'll create a separate PR to put it there.

I wonder if the default should still be to dump everything and an option be added to support not dump specific headers (not just Cookie but may be a comma separated list)?

This is a good idea to think through.
Cookies are so sensitive that we wanted to configure them to not be dumped by default: logging them could cause legal issues for people. Traffic Server doesn't cache cookies. I'll think through this on Monday.

I wonder if the default should still be to dump everything and an option be added to support not dump specific headers (not just Cookie but may be a comma separated list)?

This is a good idea to think through.
Cookies are so sensitive that we wanted to configure them to not be dumped by default: logging them could cause legal issues for people. Traffic Server doesn't cache cookies. I'll think through this on Monday.

Yeah, I do agree that Cookies are typically sensitive in most use cases.. I am just wondering if it makes sense to make it more generic for all use cases but provide an option to not dump (or even better obfuscate) specific headers as configured.
That said, I’ll leave it to your judgment, as we don’t actually m use this plugin in prod (yet) and if skipping Cookies alone satisfies your immediate requirement and if you feel is something quick to implement for now.. We can always iterate over it in the future depending on the needs. I’ll be okay with your judgement call either way :)
Just my 2c!

Verizon Media operations people push back very hard on a default being the low security option (like dumping everything) versus the high security option.

Thanks for the feedback @sudheerv and @ywkaras . I think I've satisfied what we're looking for now:

A hard-coded set of fields (currently Cookie and Set-Cookie) are considered sensitive and will, by default, be dumped with a generated, generic value. This behavior can be turned off via --promiscuous-mode, which makes traffic_dump dump the value as seen on the wire. Thus the default behavior is the "safe" behavior.
As @sudheerv mentioned, it's hard to anticipate what fields particular users may find sensitive. To address this, I've added --sensitive-fields, which takes a comma-separated list of field names that will be treated as sensitive by traffic_dump in the way described above.

[approve ci rat]

Could you go ahead an update the documentation too?

Thanks for the reminder! I'll update the docs about the new arguments today.

I'm not sure I like the way the sensitive fields setting is done. What if I want Cookie but not another field - that doesn't seem possible. If I set -p I get everything.
What I think would be better is to not have the default field list at all, but instead have a default value for -f.

I'm not sure I like the way the sensitive fields setting is done. What if I want Cookie but not another field - that doesn't seem possible. If I set -p I get everything.

Just to clarify: with the current code that could be done: --promiscuous-mode turns off the filtering of the default sensitive fields, not the user-specified ones. Thus the user can hand-specify filtering for what they want via --promiscuous-mode and --sensitive-fields.

What I think would be better is to not have the default field list at all, but instead have a default value for -f.

This is a good idea, and actually pretty easy to pivot to. I'll implement this.

Could you go ahead an update the documentation too?

Thanks for the reminder! I'll update the docs about the new arguments today.

Docs updated.

[approve ci autest]

Cherry-picked to v9.0.x branch.


bugfix(default-props): excludes default props from snapshops in shallow mode

Closes #55
Atm I'm checking if the default props exists, and if it has the same value in props, then omit it.
This isn't a perfect solution though - what happens if someone passes down a prop that is the same value as the default prop? Semantically we shouldn't omit it then, but this logic will.
Let me know if you can think of another angle we should take.

Can we have it as an opt-in parameter?

@adriantoine any updates on this? I'd love to see this PR merged :)

Yep I just reviewed it, I'm so sorry, I'm quite busy at the moment, I thought this was actually bigger than it actually is 😅
I'll merge and deploy asap.
Thanks @madou for the contribution! 🎉

I'm not sure if this change should actually only be a minor version as it might break builds, I know fixing the build is simple but currently it's not really well communicated that breakage might happen.
What's your opinion @adriantoine ?

It broke build for us. I think it should've been released as major release, because it's a breaking change and not a bugfix.

This is definitely a breaking change.

Definitely a breaking changed, broke a load of builds here for us.

Hi everyone, I understand that was a breaking change for most people, I sent an email to NPM support this afternoon to unpublish this version (this cannot be done by myself anymore) so that I can publish a major version instead but I still didn't get any answer.
Although that's entirely my fault and I apologise for the inconvenience. 😕

@adriantoine no worries. Thank you for taking action! And thank you for this helpful tool!

@adriantoine - cheers!

FWIW: I think not rendering default props is more logical behavior in general, since that is exposing implementation details of the child components. My 2c would be: Publish a major version (3.4?) with default props hidden by default, but allow opting back into the old behavior. But obviously that's just my suggestion :)

Hey @AndyBarron default props rendering will be an opt-in feature. Can you add all your comments to #99 as this PR is closed? Thanks!


Seg fault when using css2xml with latest carto sdk features

Hello
I'm using "exp" function in css styles, when I want to convert it to XML using css2xml program it fails with segfault. It didn't happen in the previous version of css2xml (before Carto 4.4.3 release). What is the problem?
Thanks

@safe-bug Can you share your style? We need more info to investigate this.

@mtehver It fails even with only this part of the style
[highway='trunk'],[highway='trunk_link']{
  line-width: exp([view::zoom]);
}

The XML output for the previous version was this:
<LineSymbolizer stroke=“#000” stroke-linecap="round" stroke-linejoin="round" stroke-width="exp([view::zoom])" />

Thanks for reporting this, should be fixed now.

@mtehver Thanks, it's fixed now.


Add Cross-Platform Binary Path Checking

Any platform should be able to check the binary paths of a package of every other supported platform.
This will make it easy to test all package installation platforms on one machine with a single command.

Added in the webman dev bintest command!


cc-wrapper use xargs

Fixes #39175 (hopefully)
This moves the cc-wrapper call to xargs which hopefully can manage the arguments correctly. This is untested but I'm hoping it will work.
Relevant build log:
/nix/store/8b0gj3bmcy5bh1zcnhn0146199b3m5kb-clang-wrapper-5.0.1/bin/clang++: line 183: /nix/store/p85m242dg1zd85ln3cg0agx0q1n0n6h0-clang-5.0.1/bin/clang++: Argument list too long

https://hydra.nixos.org/build/73059537/nixlog/1
https://hydra.nixos.org/build/73059537

This isn't going to work unless I'm really missing something. Say, if your call is of the form clang <flag 1> <flag 2> <filename 1> <filename 2> <flag 3> <flag 4> it's going to be split up to two commands, say
clang <flag 1> <flag 2> <filename 1>
clang <filename 2> <flag 3> <flag 4>

which will do something completely different.

Yep nevermind on this then! I was misunderstanding how xargs works. I thought there was some special interface that bypassed ARG_MAX.

Failure on x86_64-darwin (full log)
Attempted: diskrsync, enhanced-ctorrent
The following builds were skipped because they don't evaluate on x86_64-darwin: arb, eclib, mono, zfs
Partial log (click to expand)
cannot build derivation '/nix/store/xvamwg2qls37sih26xx6izbkcsc297vp-top-osx-10.11.6.drv': 6 dependencies couldn't be built
cannot build derivation '/nix/store/nxgc676689n7pdhzvx9gzxw5p2p8lm00-system_cmds-osx-10.11.6.drv': 8 dependencies couldn't be built
cannot build derivation '/nix/store/95hfs2h1jj96m0kgrrc4f762pgjspbrw-top.drv': 3 dependencies couldn't be built
cannot build derivation '/nix/store/pg4ijgzlczrzq2837gzhrfpvcih3pynd-sysctl.drv': 3 dependencies couldn't be built
cannot build derivation '/nix/store/ks41rcflpvvicf2sfh0fyqmrvg12srdw-procps-compat.drv': 6 dependencies couldn't be built
cannot build derivation '/nix/store/wsz63id6265nb0xazjamcmin019b33f9-go-1.10.1.drv': 21 dependencies couldn't be built
cannot build derivation '/nix/store/7fbm5jscvmlr54bjbzwnafv68n3k2abx-parallel-20180322.drv': 5 dependencies couldn't be built
cannot build derivation '/nix/store/z1cq2m68p8ima0cwyyxjfyxpwgp8q5kl-govers-20150109-3b5f175.drv': 5 dependencies couldn't be built
cannot build derivation '/nix/store/ybzzi2x5w8xjic0yhbh31w9z3i18qyh3-diskrsync-unstable-2018-02-03.drv': 8 dependencies couldn't be built
error: build of '/nix/store/hmv2f82k5rd1l1j6apr86yxi3llwg927-enhanced-ctorrent.drv', '/nix/store/ybzzi2x5w8xjic0yhbh31w9z3i18qyh3-diskrsync-unstable-2018-02-03.drv' failed

Failure on aarch64-linux (full log)
Attempted: arb, diskrsync, eclib, enhanced-ctorrent, zfs
The following builds were skipped because they don't evaluate on aarch64-linux: mono
Partial log (click to expand)
cannot build derivation '/nix/store/5ya35x1y4w0gf42gjjmkp5bvm4n7b3g7-python2.7-hg-git-0.8.11.drv': 8 dependencies couldn't be built
cannot build derivation '/nix/store/1i9z72qqdi8nb9l73iqd0y55slcxhwn0-mercurial-4.5.2.drv': 11 dependencies couldn't be built
cannot build derivation '/nix/store/kpbk8xn1jn65dg3kdlfsxb2m09sd7mqz-texlive-core-big.bin-2017.drv': 20 dependencies couldn't be built
cannot build derivation '/nix/store/q1zpa37fyjbcgvbd70cabcy3z2m12xpv-go-1.10.1.drv': 19 dependencies couldn't be built
cannot build derivation '/nix/store/gnjjz08m8vq79vvb2r3d2iq6a3yirb95-texlive-combined-basic-2017.drv': 7 dependencies couldn't be built
cannot build derivation '/nix/store/nw4xpmjzgng8am9hvi9yrg6rhbx9zmmb-govers-20150109-3b5f175.drv': 5 dependencies couldn't be built
cannot build derivation '/nix/store/zlx6k9j1m80vxjpki0d9rp6mmm0fcwdy-pari-2.9.4.drv': 8 dependencies couldn't be built
cannot build derivation '/nix/store/fc7gvhcs4j5dbgvwyz63l33a3ns3acia-diskrsync-unstable-2018-02-03.drv': 8 dependencies couldn't be built
cannot build derivation '/nix/store/66n90x7qgaklz0fjh0nvxvmqsi8asmi7-eclib-20171002.drv': 6 dependencies couldn't be built
error: build of '/nix/store/66n90x7qgaklz0fjh0nvxvmqsi8asmi7-eclib-20171002.drv', '/nix/store/c1qldgjbc24jyxlzi827xfm4iy9qk5g0-arb-2.13.0.drv', '/nix/store/fc7gvhcs4j5dbgvwyz63l33a3ns3acia-diskrsync-unstable-2018-02-03.drv', '/nix/store/krrx3n84axxjyyym9fz16ynpfkwrmc00-enhanced-ctorrent.drv', '/nix/store/n2wd73qcc4is7gxfk2082y1p0fc2q0k6-zfs-user-0.7.8.drv' failed

Failure on x86_64-linux (full log)
Attempted: arb, diskrsync, eclib, enhanced-ctorrent, zfs
The following builds were skipped because they don't evaluate on x86_64-linux: mono
Partial log (click to expand)
cannot build derivation '/nix/store/9a47c7cv7nbr6mamgsasj1x5m2h94599-python2.7-hg-git-0.8.11.drv': 8 dependencies couldn't be built
cannot build derivation '/nix/store/vfmw41cfwih6yx4b5bsa94xdp7j7xpsa-mercurial-4.5.2.drv': 11 dependencies couldn't be built
cannot build derivation '/nix/store/qsq6zyircrnd5a3991qjvi133k5f2v15-texlive-core-big.bin-2017.drv': 20 dependencies couldn't be built
cannot build derivation '/nix/store/dkcfc33zyc7xjp5pa0q10zqc18d6ymdv-go-1.10.1.drv': 19 dependencies couldn't be built
cannot build derivation '/nix/store/dpnp9svfjgh0d4b2g4pq7y2n2s7n8hj3-texlive-combined-basic-2017.drv': 7 dependencies couldn't be built
cannot build derivation '/nix/store/yi7a44mr30915lw6y2757bsjircjh7zs-govers-20150109-3b5f175.drv': 5 dependencies couldn't be built
cannot build derivation '/nix/store/jcv9jhl45xinkyxshshwkf5463nqkd7q-pari-2.9.4.drv': 8 dependencies couldn't be built
cannot build derivation '/nix/store/g53dc8cwxpl5v8vw9bp5bjbcq96myzsd-diskrsync-unstable-2018-02-03.drv': 8 dependencies couldn't be built
cannot build derivation '/nix/store/mbxx81ckah76sa1savgzpdnv3w4l0cjp-eclib-20171002.drv': 6 dependencies couldn't be built
error: build of '/nix/store/g53dc8cwxpl5v8vw9bp5bjbcq96myzsd-diskrsync-unstable-2018-02-03.drv', '/nix/store/g85zs6mcyzmwwvd3v4gl123s6v0kyb2a-enhanced-ctorrent.drv', '/nix/store/mbxx81ckah76sa1savgzpdnv3w4l0cjp-eclib-20171002.drv', '/nix/store/w2h6vns4jrrh9alg8wa31046mfmvkr0c-zfs-user-0.7.8.drv', '/nix/store/z13r4y1q7chxvhgzfva73bpgyhznrryi-arb-2.13.0.drv' failed


Make docker-compose launch all services and a setup script

Wanted to make it easy for anyone to spin this up locally with one command.

Extend docker-compose file to run the app, worker and setup script.
Move scheduleWorkerTasks to the worker file.
Make worker run cron tasks on launch.
Improve README, describing how to run the mutations and start the server.

Hey @timjrobinson thanks for the effort on this. A few things:

Unfortunately this setup prevents me from running only the database in docker and the backend from the IDE for debugging purposes. Not sure how to achieve it though.
I think the scheduleLocalWorkerTasks() doesn't include all necessary worker tasks, it wasn't maintained. Would need to compare the jobs yaml file with what this function runs.
I'd like to introduce this only for v3, which is currently in the feature/multiple-chains-single-deployment branch. You mind creating a PR against that branch?


Can't load converter that will makeHTML()

In my source, I have a slightly old version of Showdown:
<script src="//cdnjs.cloudflare.com/ajax/libs/showdown/1.0.2/showdown.js"></script>

In my code I attempt to call:
            var preprocess = function(raw)
                {
                if (!raw)
                    {
                    return '';
                    }
                var workbench = '';
                for(var index = 0; index < raw.length; index += 1)
                    {
                    workbench += raw[index];
                    }
                workbench = workbench.replace(/&/g, '&');
                workbench = workbench.replace(/"/g, '"');
                workbench = workbench.replace(/'/g, ''');
                workbench = workbench.replace(/\\\\/g, '\\\\\\\\');
                workbench = workbench.replace(/</g, '<');
                workbench = workbench.replace(/>/g, '>');
                return converter.makeHTML(workbench);
                };

I get an error in the log saying, "converter.makeHTML is not a function".
What should I be doing to convert Markdown to HTML using Showdown?
Thanks,

Short version
You miss typed the function's name. It's converter.makeHtml
A bit longer version
You're using an outdated version of showdown. You should be using the latest:
<script src="//cdnjs.cloudflare.com/ajax/libs/showdown/1.3.0/showdown.js"></script>

Secondly, you don't really need to encode html entities, since showdown does that for you.
Check a working fiddle here


python310Packages.rising: 0.2.1 -> 0.3.0

Description of changes
Routine update.
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

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

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 214016 run on aarch64-darwin 1

1 package built:

python310Packages.rising

test_progressive_resize_integration still fails on aarch64-linux. Perhaps consider making a PR that disables/fixes it?


[TablePagination] Fix duplicated keys in rows per page

The Select control which appears after Rows per page: shows the current amount of rows per page (value, for example 10).
When clicking on the value, a list with all of the possible options appears (option, for example 5, 10, 20, etc.).
Previously, both the value and the options each had their text as the key.
This resulted in duplicated key usage, as the value 10 with key 10 has the same key as the option 10 with key 10.
By prefixing the value with value- and the option with option-, the keys are guaranteed to be unique.

[x] I have followed (at least) the PR section of the contributing guide.

@eps1lon you're welcome!
As requested, I now added a unit test and confirmed that the test is failing without the fix, and passing after applying my fix.

Thanks for the test case.
We had a very close issue in #18988. I think that it's a signal that this is becoming over-engineered. I have updated the approach to be pragmatic, rowsPerPageOptions is mostly static.

 Interesting, that's definitely a good point. Even though using index as a key is considered to be an anti-pattern I think considering in this specific case we don't expect the order of the options to change at runtime (as probably most developers would just define rows statically) I think we should be fine here. If someone were to dynamically adjust the rows per page based on the dataset size or something like that, it could cause additional re-renderings and lead to worse performance, but I don't think that should be a case that comes up often.

The anti-patern article mentions the following, it seems or match:

To help you decide, I put together three conditions which these examples have in common:
the list and items are static–they are not computed and do not change;
the items in the list have no ids;
the list is never reordered or filtered.
When all of them are met, you may safely use the index as a key.

@eps1lon I agree. Using the label definitely makes sense here.

I came across more harsh than it should've been.
I definitely sympathize with the motivation for the original change. I've built my fair share of pagination UIs and never found pleasure in codifying all the special cases for all the relations the current page can have to last page, first page and page count etc.
I do want to encode these learnings into Material-UI which breaks down once we apply changes just to get rid of warning/error for one particular usage. Instead we want to collect these stress cases and create a solution that takes all of them into account. That solution can require work from the app developer not necessarily from us. Though we do want to guide app devs in these instance as best as possible. If we don't agree on that, we don't need to build a component library.