Bugs due to recent updates

Hey @macrozone , I see you are doing quite a lot of good work on the lib! Very happy to see that. While updating to the latest version, I've noticed a few small issues and since I am not currently set up with code, I thought I'd run it past you and you can fix in one of your many releases :)
It all has to do with background plugin:
Here https://github.com/react-page/react-page/blob/master/packages/plugins/layout/background/src/Controls/BackgroundDefaultControls.tsx#L147 it should be changed from "onDragEnd" to "onChangeCommit", same here https://github.com/react-page/react-page/blob/master/packages/plugins/layout/background/src/Controls/BackgroundDefaultControls.tsx#L127.
Then here: https://github.com/react-page/react-page/blob/master/packages/plugins/layout/background/src/Component/index.tsx#L120 the state should be passed in along with the props, otherwise the preview functionality for darken and lighten stops working. This was previously handled by rendering the renderer in Controls like so: https://github.com/react-page/react-page/blob/857b80ac769af74fe8145ba3e19c05bebc8ae541/packages/plugins/layout/background/src/Controls/BackgroundDefaultControls.tsx#L56. But at some point, it was changed thus breaking the preview functionality.
Carry on with the great work!  Cheers

Also when doing all the way to 0.16.0-beta.5, when clicking on background/image plugin in edit mode, I see
Could not find editable: undefined

Which happens over here https://github.com/react-page/react-page/blob/1d3393912927aa9c3d0a5647148bb964b7b71a6b/packages/core/src/selector/editable/index.ts#L101.
Not sure why that is.
Lastly, the draft feature is amazing!!!! But sadly it doesn't work for me. I can still see the "draft" content when rendered via HTMLRenderer. Sorry I am polluting the issue, just wanted to give you the feedback.

@PeterKottas thx so much for your feedback! will fix it!

Lastly, the draft feature is amazing!!!! But sadly it doesn't work for me. I can still see the "draft" content when rendered via HTMLRenderer. Sorry I am polluting the issue, just wanted to give you the feedback.

I also realized that too and i am just about to debug it. I forgot that the serializer removes some properties and i had to transfer the isDraft property over there.

@PeterKottas ok, the Slider bug is because of the upgrade to material-ui 4. i fixed it and will trigger a release

@PeterKottas the second issue is because of this:
My goal was to unify the plugins to this pattern:
<><Renderer />{ !readOnly ? <Controls /> : null}</>
so that the renderer would not need to re-render. however, this did not work with plugin, that used some preview-state in the renderer. e.g. the image-plugin. In these cases, i did:
<>{ !readOnly ? <Controls /> : <Renderer />}</>
and then the Controls would need to include the Renderer as well.
I will now do the same in the background-plugin, ist just forgot to check that.
Having said that, we should probably revisit that. I mitigate the headache around these concerns a bit, because i only use custom plugins with @react-page/create-plugin-materialui and non of the built-in plugins. Would be cool to migrate the built-in plugins to use that (or a more general) factory-function.

@PeterKottas i could not reproduce Could not find editable: undefined but i think i know where it could come from... and i think its already fixed.
can you tell me which version did you use?
0.16.0-beta.7 is been baked now and should fix all issues hopefully

@PeterKottas ok, the Slider bug is because of the upgrade to material-ui 4. i fixed it and will trigger a release

Awesome!

@PeterKottas the second issue is because of this:
My goal was to unify the plugins to this pattern:
<><Renderer />{ !readOnly ? <Controls /> : null}</>
so that the renderer would not need to re-render. however, this did not work with plugin, that used some preview-state in the renderer. e.g. the image-plugin. In these cases, i did:
<>{ !readOnly ? <Controls /> : <Renderer />}</>
and then the Controls would need to include the Renderer as well.
I will now do the same in the background-plugin, ist just forgot to check that.
Having said that, we should probably revisit that. I mitigate the headache around these concerns a bit, because i only use custom plugins with @react-page/create-plugin-materialui and non of the built-in plugins. Would be cool to migrate the built-in plugins to use that (or a more general) factory-function.
EDIT: actually, it already works now, the <Control /> component of the background plugin did not pass anything special to the Renderer unlike the image plugin.
I now will check the Could not find editable: undefined error

Yeah I know, it's a little bit messy right now. I am actually responsible for some of that code. Needles to say, it was sewed with a hot needle :) Would be great if this all could be unified and improved by using a proper pattern for initial configuration. Most of our plugins are custom as well but we still use some from the lib.

@PeterKottas i could not reproduce Could not find editable: undefined but i think i know where it could come from... and i think its already fixed.
can you tell me which version did you use?
0.16.0-beta.7 is been baked now and should fix all issues hopefully

Great, I'll check it out right away!
One extra thing that came up while upgrading. Would you pls be able to add a theme prop to the BottomToolbar? Then on
https://github.com/react-page/react-page/blob/master/packages/ui/src/BottomToolbar/index.tsx#L52
we could do something like:
theme={this.props.theme ? this.props.theme : dark ? darkTheme : null}

The reason for it is right now, it's not possible to override the theme for this new toolbar. I think this whole thing with themes and how they are handled might need some work in the future as well.

Awesome, the new version fixes most of the things. One thing I had to do on my end is add
{...props}

To  when rendering. It appears that's caused by the editable being a required prop because it is used in the duplicate and draft button. Weird thing though it's not picked up by typescript typings. It doesn't give me the warning despite the prop clearly being required.
One last thing is I now constantly get a warning:
Material-UI: you cannot use a custom insertionPoint and <StylesContext injectFirst> at the same time.

Not sure if this is on my end or if you see it too.

And one small style thing:
This https://github.com/react-page/react-page/blob/0.16.0-beta.7/packages/ui/src/DraftSwitch/index.tsx#L24 and 2 lines bellow, the margin should be removed and marginBottom: 0 should be added here : https://github.com/react-page/react-page/blob/0.16.0-beta.7/packages/ui/src/DraftSwitch/index.tsx#L11 This will center things quite nicely. Right now it's a bit out of balance.

@PeterKottas ok, i will see what i can do about the styling.
I already struggled a bit with the toolbar and its styling. I think you can Wrap it in a ThemeProvider i guess? I defaulted it to the light theme, because most ui elements worked a bit better in bright than in dark theme. Only slate defaults to dark.

{...props}
To when rendering. It appears that's caused by the editable being a required prop because it is used in the duplicate and draft button. Weird thing though it's not picked up by typescript typings. It doesn't give me the warning despite the prop clearly being required.

yes, exactly! the Bottom Toolbar now needs to know the id of the current Cell and the editable name (which is only used when having multiple editables in one editor). This is not very clean anymore, so i would suggest to:

Rename the BottomToolbar to something like NodeActionToolbar, because it already comes with some basic actions (delete, draft, copy)
Only pass the id (and editable) to that and use connect to get the cell properties you need. (E.g. in de DraftButton i already do this)

Speaking about.. i would love to migrate to redux hooks (or even something like the lovely https://github.com/ctrlplusb/easy-peasy redux  library) and/or use React.createContext more often (which is so nice with useContext-hook. Then we could e.g. provide the current cell information through the context.
But for the moment, i tried to keep the current style to not make it too messy... but i think we should start migrate some stuff in the near future, because i think it would make it much more readable and understandable and help evolve it further

I already struggled a bit with the toolbar and its styling. I think you can Wrap it in a ThemeProvider i guess? I defaulted it to the light theme, because most ui elements worked a bit better in bright than in dark theme. Only slate defaults to dark.

This unfortunately doesn't work because the bottomToolbar renders it's own theme provider here: https://github.com/react-page/react-page/blob/master/packages/ui/src/BottomToolbar/index.tsx#L52 making it impossible to override the "NodeActionToolbar" if you will. You can only render it inside and override for your own components. Not good. IMHO, it shouldn't render the theme provider at all! Tbh, I think the whole theme handling should be removed from react-page. The fact that we use Material-UI is kind of a choice that was made, not a necessity for the lib itself. If anybody commits to use the controls components provided by the lib, they should be aware of the fact the Material-UI lib is used and the theme should be provided from outside. Right now, it's a little bit messy that we provide some defaults and then give a way of overriding that actually doesn't always work. I would love to hear what you think about it as this would obviously be a breaking change. But maybe one that should be considered.
Yeah, new name would for sure explain better what this does. On the other hand, people who use it will probably complain about the breaking change, and people who don't use it, they wouldn't even notice. Maybe this one is not worth the fuss. As long as typescript works properly with expected props that it requires.

Speaking about.. i would love to migrate to redux hooks (or even something like the lovely https://github.com/ctrlplusb/easy-peasy redux library) and/or use React.createContext more often (which is so nice with useContext-hook. Then we could e.g. provide the current cell information through the context.

I think something should definitely be done about this at some point. I wasn't sure that redux in general was the best choice for a long time. Obviously it made sense at the time, but I do agree that there are now better options.

Haven't seen https://github.com/ctrlplusb/easy-peasy before. Lovely little lib! I would probably need a closer look just to make sure it works with middleware, thinks and so on. But the low configuration complexity as opposed to what redux has is tempting.

bh, I think the whole theme handling should be removed from react-page. The fact that we use Material-UI is kind of a choice that was made, not a necessity for the lib itself. If anybody commits to use the controls components provided by the lib, they should be aware of the fact the Material-UI lib is used and the theme should be provided from outside.

I disagree on that. Abstracting a UI away is very hard. Using material-ui is of course opinionated, but its neutral and customizable and therefore a good solution.
Since we lazy load it, its bloat is no longer an argument. I don't see much business-value of themeing or even replace the UI. E.g. take wordpress, it has a default ui on the backend and does not enforce theming it. I even think that having a neutral ui makes it easier to separate it from the content, which is of course on-brand.
But the main reason for me is that if we need to support every possible customization, we hinder innovation and development. Take my additions above with the delete, copy and draft-button. If I had to also support changing the appearance and icons of these buttons, i would never have finished that feature. As initially mentioned, that is kind of a hard problem. Of course, limiting it to themeing in material-ui mitigates that problem, but its still a debt that you have to fullfill.
So bottom line: We should make the default UI as good as possible to fullfill the tasks that editors want to do. that should be the top priority. Devs are invited to raise issues and provide PRs to make it even better, and add customization options to improve it for some use cases. E.g. themeing could make sense when dealing with special content that look odd with the default theme or for special screen sizes.

And one small style thing:
This https://github.com/react-page/react-page/blob/0.16.0-beta.7/packages/ui/src/DraftSwitch/index.tsx#L24 and 2 lines bellow, the margin should be removed and marginBottom: 0 should be added here : https://github.com/react-page/react-page/blob/0.16.0-beta.7/packages/ui/src/DraftSwitch/index.tsx#L11 This will center things quite nicely. Right now it's a bit out of balance.
This in addition to making the theme injectable into the bottom toolbar will make things absolutely beautiful! :)

I look into that, but:

FormControlLabel has no margin bottom by default in the default theme, so adding marginBottom: 0 there makes no sense to me
removing { marginTop: 5 } will make the icons non-centered in the default theme, but i have to admit that the adding a top margin is not the best solution there.

But as you can see, that supports my concern about theming.
I will add a theme property to the BottomToolbar so you can check if this fixes your issue with the non-centered icons. If not, can you open an issue with a screenshot  and the involved browser? maybe its browser specific. and check if you can reproduce it with the example

bh, I think the whole theme handling should be removed from react-page. The fact that we use Material-UI is kind of a choice that was made, not a necessity for the lib itself. If anybody commits to use the controls components provided by the lib, they should be aware of the fact the Material-UI lib is used and the theme should be provided from outside.

I disagree on that. Abstracting a UI away is very hard. Using material-ui is of course opinionated, but its neutral and customizable and therefore a good solution.
Since we lazy load it, its bloat is no longer an argument. I don't see much business-value of themeing or even replace the UI. E.g. take wordpress, it has a default ui on the backend and does not enforce theming it. I even think that having a neutral ui makes it easier to separate it from the content, which is of course on-brand.
But the main reason for me is that if we need to support every possible customization, we hinder innovation and development. Take my additions above with the delete, copy and draft-button. If I had to also support changing the appearance and icons of these buttons, i would never have finished that feature. As initially mentioned, that is kind of a hard problem. Of course, limiting it to themeing in material-ui mitigates that problem, but its still a debt that you have to fullfill.
So bottom line: We should make the default UI as good as possible to fullfill the tasks that editors want to do. that should be the top priority. Devs are invited to raise issues and provide PRs to make it even better, and add customization options to improve it for some use cases. E.g. themeing could make sense when dealing with special content that look odd with the default theme or for special screen sizes.
Edit: @PeterKottas what is the main reason why you want to theme the editor?

I think you misunderstood what I meant. What I am saying is we might consider removing just the ThemeProvider. As people use their own theme provider in their app and it's fair to assume they will want to continue using that for all parts of their app.
I definitely didn't mean abstracting away the whole UI or adding the ability to replace icons or anything like that.
TBH, I'm not too pushy on this, it was just a though. What I insist on though is we should have a way to override all themed material-ui components from outside of react-page. This is not the case now for the new toolbar. It works everywhere else though.
To answer your last question, being able to override the theme is (in general) extremely important. Take the fuss about the dark/light team that the whole web community is talking about now. Also right now, we have a fairly concise, well-designed UI with our company palette, but when I go to the content editor, there is this bottom toolbar that has one pink delete button, purple switch and another purple button. Colors that are not present anywhere else on our dashboard. This problem can be fixed very easily, all it needs is adding a theme prop on the BottomToolbar and then here https://github.com/react-page/react-page/blob/master/packages/ui/src/BottomToolbar/index.tsx#L52, instead of null passing along that new theme props thus making in overridable.
Generally speaking, no matter how "well" you design the UI, there will always be people who want to change a thing or 2 because it's all subjective. That's why themes exist. It would be crazy to allow for overriding of all components, but theme should be the bare minimum. Especially when material-ui supports it quite nicely :)

I look into that, but:

FormControlLabel has no margin bottom by default in the default theme, so adding marginBottom: 0 there makes no sense to me
removing { marginTop: 5 } will make the icons non-centered in the default theme, but i have to admit that the adding a top margin is not the best solution there.

But as you can see, that supports my concern about theming.
I will add a theme property to the BottomToolbar so you can check if this fixes your issue with the non-centered icons. If not, can you open an issue with a screenshot and the involved browser? maybe its browser specific. and check if you can reproduce it with the example

Cheers, I'll have to pull down the code and look for myself in the lib. We should definitely be able to center the icons without the use of any magic margins.

@PeterKottas unfortuatly, the deploy fails constantly on travis, i have no clue why. All tests are passing, so  i could not release it yet.
i see the point with the themeprovider and i try to leaverage it as much as possible, but i have too little experience and i don't think its that important, that's why i would  love to see others help on that topic!

I look into that, but:

FormControlLabel has no margin bottom by default in the default theme, so adding marginBottom: 0 there makes no sense to me
removing { marginTop: 5 } will make the icons non-centered in the default theme, but i have to admit that the adding a top margin is not the best solution there.

But as you can see, that supports my concern about theming.
I will add a theme property to the BottomToolbar so you can check if this fixes your issue with the non-centered icons. If not, can you open an issue with a screenshot and the involved browser? maybe its browser specific. and check if you can reproduce it with the example

Cheers, I'll have to pull down the code and look for myself in the lib. We should definitely be able to center the icons without the use of any magic margins.

👍

My bad, the 5 bottom margin was in my reboot for some reason! All good now.

@PeterKottas unfortuatly, the deploy fails constantly on travis, i have no clue why. All tests are passing, so i could not release it yet.
i see the point with the themeprovider and i try to leaverage it as much as possible, but i have too little experience and i don't think its that important, that's why i would love to see others help on that topic!

No worries, I have some more experience here so I can help when necessary. Have to set up the code as well. I tried the other day but I think there are some problems with it now on Windows. I think people committed some changes specific for Mac in build scripts. I'll have to look at that.

@PeterKottas version 0.16.0-beta.9 should contain the changes above, but the meta package has not been published, but all others should work

Already pulled down and works like a charm! Cheers


Unable to load unsloth models in just single GPU in a multi GPU system

I have two RTX A6000 and I understand the opensource unsloth version only supports single GPU. Is there anyway I can config to use only one GPU? I currently get this error when I import unsloth and load models

I still get the same error

Try using the CUDA_VISIBLE_DEVICES environment variable in the script itself.
python```
import os
os.environ['CUDA_VISIBLE_DEVICES'] = '0'  # Use GPU 0
or

python```
import os
os.environ['CUDA_VISIBLE_DEVICES'] = '1'  # Use GPU 1

Put it at the top of the script. By the way, the first GPU is "0" and second one is "1".

I have implemented a fix for this here:
https://github.com/unslothai/unsloth/pull/974

Will look into @Sehyo's PR and implement a fix - sorry everyone!

I'm still getting this issue, is there a fix planned?

Any updates on this? Also having the same problem. Would it be possible to put it as a warning to be able to ignore it?


Let flutter/flutter define C flags for flutter/engine build

Maybe we can add something like engine_config.h (which is similar to SkUserConfig.h in Chrome/Android for Skia) to flutter/flutter repo, and use the hash of that file to download the engine binary from Google Cloud bucket?
This way, we can use guard flags to make sure that engine roll is always successful even with breaking engine changes. We can also use those flags to trim down binary size by allowing Skia to have optional features.

CC @chinmaygarde @cbracken @reed-at-google

Would we still need this with FFI in place and the right symbols exported from the engine for extensibility?

I'm not very familiar with FFI. CC @mehmetf who was just talking about FFI in another email thread.

FFI may not be supported on all platforms

Those platforms probably wouldn't benefit from using different builds of the engine either though right?

Hard to say for fuchsia. it's also not clear how exactly it will be exposed for iOS and Android

We're not going to do this.


Error opening table in Azure Storage Explorer (Reason: oom. Code -536870904.)

This error was happening on the previous version I was running (1.19.1??) and today I just installed a new version (1.22.1) and it behaves exactly as before. The error is 100% reproducible. It happens identically every time I try to open the table..
Steps:

Navigate to the subscription ID in the explorer tab
Open the storage account
Open Tables
Click on the "WADWindowsEventLogsTable"
The table attempts to open, beginning by showing only the two key column headings PartitionKey and RowKey (but no data)
It then spins while it attempts to load the rest and will eventually throw an error (after maybe 30-60 seconds)

The error message is: "A renderer process crash caused Storage Explorer to stop working correctly. Storage Explorer can try to restart the program. Reason: oom. Code -536870904.
I would guess that "oom" is out of memory. As the name suggests, this is simply the table that Azure is creates/saves the diagnostic information to. We only have 2 VMs in the cloud, so the volume of data is not massive. If I delete the table, Azure will automatically recreate it (as expected), and I will be able to open it for some time. However, in maybe only 24 hours, I will experience the issue that I cannot open the table anymore. From what I understand, the explorer should only be trying to fetch the first 1,000 records (which do accumulate quite quickly). I would not expect this to cause the kind of error it does. Other WAD tables in the same storage account open just fine, even ones with over 400,000 entries.
Incidentally, this issue is repeatable and identical whether I run Storage Explorer on a local Windows 10 PC, or if I run it on a Server 2016 VM in Azure.

@jkerie

How much RAM does your machine have?
Prior to opening the table how much RAM is being used?
As you open the table, can you watch the RAM usage and see how high it goes?
Would it be possible for you to share a SAS url to the table with us? It can be read only. You can send it so sehelp @ microsoft dot com.

@jkerie Would you like to try using a test build to see if your problem is resolved?
https://cralvordtest02.blob.core.windows.net/customer-share/internal/1.23.0-table-rbac/StorageExplorer-darwin-x64.zip?sv=2020-10-02&st=2022-02-14T19%3A38%3A47Z&se=2022-02-21T19%3A38%3A00Z&sr=b&sp=r&sig=7MRYSOgAwO%2FutNgUaApjkzsv0NOPupvImedJ43QxQg0%3D

Thank you. I will look at this tomorrow.

I am going to try the test build, but wanted to update on the prior questions about RAM, etc.:

System has 16GB RAM.
At the time of opening only about 6.5GB was used.
As it tried to process, it did gradually consumer more, but it wasn't a straight line progression. It wiggled a little as it went up. The error took about 2 minutes to reach and by that point, the memory usage had reached about 8GB (so still about 8GB remaining free).
I will email you an SAS

@jkerie The table loads up normally on my end, so I think the test build should work for you. Let us know how it works out.

Thanks, craxal. I downloaded the zip file, but I guess I wasn't sure how to run it. Do I need to compile it and with what? I am running Windows 10.

@jkerie Sorry, it wasn't clear from the bug description that you were running Windows. Here's another link for a Windows installer:
https://cralvordtest02.blob.core.windows.net/customer-share/internal/1.23.0-table-rbac/StorageExplorer-ia32.exe?sv=2020-10-02&st=2022-02-15T18%3A27%3A45Z&se=2022-02-21T18%3A27%3A00Z&sr=b&sp=r&sig=C7sKDwXRUfMMCvKkKbOxdH2YD4YvTJ31%2FQulG5ouO2U%3D

Yes, that fixed it - it works again! Thanks! When do you expect this version to be officially released?

@jkerie Good to know! Assuming things go smoothly, we are locking down on changes for 1.23.0 now so that we can release sometime this month.


Opt-in for MFA requirement

Make the gem more secure by requiring that all privileged operations by any of the owners require OTP.
Ref: https://guides.rubygems.org/mfa-requirement-opt-in/

Hello,
even if the numbers of downloads can implicitly require MFA to publish this gem, adding this metadata will add an explicit panel on the right sidebar of the gem.
This is also in Sidekiq and a lot of popular gems (which already require MFA)
Ref: sidekiq/sidekiq#5850

Thanks @tagliala


Add llama 3.1 pre-training data video; Add llama 3.1 paper url to "All Papers" section

把最新一期的Llama 3.1论文精读 · 2. 预训练数据【论文精读·54】放入表格，包括b站视频链接、播放量、播放时长和封面
在“所有论文”中加入Llama 3.1论文链接、介绍和应用数

please resolve conflict, others  are good

please resolve conflict, others are good

Will do!

The conflict is resolved. The PR is ready to be merged @mli


Update slotmap when slot is not served by any node

The sync-API will now update the slotmap before attempting to send a command when the slot is not served.
The async-API will initate the slotmap update in parallell so that the next command might have an updated slotmap.
Two additional issues surfaced and are fixed:

Use correct function name for redisClusterUpdateSlotmap()
The former name cluster_update_route() is not defined when HIRCLUSTER_NO_OLD_NAMES is defined, which would break the build.
Disconnect async connection when authentication fails.

Fixes #191

I reverted the callback handling for AUTH commands, to be added via separate PR.
There are other authentication related changes that can be discussed in that PR.
Also removed the use of the eventloop in the testcases that didn't need any events for its testing.


adjust naming convention to match BeatSaverDownloader

BeatSaverDownloader and ModAssistant follow the naming convention "key (songName - levelAuthorName)" to help prevent duplicate songs from being downloaded, especially now that ModAssistant also supports playlist downloading

Looks good to me, will be applied on the next update. 👌


Add import file error for unavailable regions

Overview
Displays an import file error if a user attempts to import a CSV containing rows from a state not currently supported in DistrictBuilder
Checklist

[x] Description of PR is in an appropriate section of CHANGELOG.md and grouped with similar changes, if possible

Demo

Notes
@dmcglone Thoughts on what this text should be?
Testing Instructions

Attempt to import a file for a state not included in local DB database (e.g., California)
Expect: Error is displayed as shown above

Closes #852

@kevinearldenny state ST not currently supported


Fix login fetching for full_gpa

Somehow the login that was fetched in the page got a space added to it at the start of the string messing with the request afterwards.
This commit should fix this even if they change it later and add more whitespace at the start or end of the string.

@MathiDEV

@MathiDEV bump


Cannot import name <msg_name>_C for C++ message when calling isSubscribedTo()

Describe the bug
When calling isSubscribedTo() on a message reader for a C++ message, I get an import error for a C message which doesn't appear to exist.
To reproduce
Steps to reproduce the behavior:

Checkout develop branch
git pull to ensure up-to-date with latest development
Compile Basilisk per instructions
Open python
Run following

>>> import Basilisk
>>> from Basilisk.architecture import messaging
>>> rw_msg_reader = messaging.RWConfigMsgReader()
>>> rw_msg = messaging.RWConfigMsg()
>>> rw_msg_reader.isSubscribedTo(rw_msg )
0
>>> # this makes sense... the message reader isn't subscribed to that message
>>> thr_msg = messaging.THROutputMsg()
>>> rw_msg_reader.isSubscribedTo(thr_msg)
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/home/slentine/basilisk-avs/dist3/Basilisk/architecture/messaging/RWConfigMsgPayload.py", line 712, in isSubscribedTo
    from Basilisk.architecture.messaging.RWConfigMsgPayload import RWConfigMsg_C
ImportError: cannot import name 'RWConfigMsg_C' from 'Basilisk.architecture.messaging.RWConfigMsgPayload' (/home/slentine/basilisk-avs/dist3/Basilisk/architecture/messaging/RWConfigMsgPayload.py)

Expected behavior
isSubscribedTo() should also return false for the second case, because those messages are not subscribed.
Screenshots
N/A
Desktop:

OS: Ubuntu
Version: 20.04
Python version: 3.8.10

Additional context
Problem appears to originate here. The code appears like it'll always fail for a C++ message if the type(source) != messageType, because the messaging module will never contain a type <msg_name>_C.

@ascended121  Good catch! We do a better job handling users that use mismatched message types. PR #429 should get us there. Let us know if this or a similar problem persist once the PR has been merged.


fix bug

Uncaught TypeError: Cannot read property 'init' of null
    at n.<anonymous> (index.js:683)
    at Object.c (index.js:683)
    at n.emit (index.js:683)
    at e.exports.<anonymous> (index.js:683)
    at Object.c (index.js:683)
    at e.exports.n.emit (index.js:683)
    at FullPacketParser.<anonymous> (index.js:683)
    at FullPacketParser.n.emit (index.js:683)
    at B (index.js:683)
    at N (index.js:683)
3index.js?aa4c0e7c5daa59dfafbc:54 Uncaught TypeError: Cannot read property 'inMenu' of null
    at HTMLDocument.<anonymous> (index.js:54)

turns out it was just my cached version that was broken


Got the python version wrong when deploy my flask web app to heroku

Hi miguel,the problem cost me for many days,it's my pleasure if you can help me...
I use linux and ubuntu17.04,My virtualenv is python3.5.3,and runtime.txt:python-3.5.3,and my app include the requirements.txt and Procfile,I create the runtime.txt and Procfile file by echo "python-3.5.3">runtime.txt,and echo "web: gunicorn manage:app">Procfile,no wrong when I ran the pip install -r requirements.txt.
But when I try to deploy the app to heroku,it happens:
(venv3) mo@mo-VirtualBox:~/flasky_1$ git push heroku master
Counting objects: 1178, done.
Compressing objects: 100% (879/879), done.
Writing objects: 100% (1178/1178), 231.05 KiB | 0 bytes/s, done.
Total 1178 (delta 765), reused 428 (delta 262)
remote: Compressing source files... done.
remote: Building source:
remote:
remote: -----> Python app detected
remote:  !     The latest version of Python 3 is python-3.6.3 (you are using Python-2.7.13, which is unsupported).
remote:  !     We recommend upgrading by specifying the latest version (python-3.6.3).
remote:        Learn More: https://devcenter.heroku.com/articles/python-runtimes
remote: -----> Installing Python-2.7.13
remote:  !     Requested runtime (Python-2.7.13) is not available for this stack (heroku-16).
remote:  !     Aborting.  More info: https://devcenter.heroku.com/articles/python-support
remote:  !     Push rejected, failed to compile Python app.
remote:
remote:  !     Push failed
remote: Verifying deploy...
remote:
remote: !	Push rejected to ginnymo.
remote:
To https://git.heroku.com/ginnymo.git
 ! [remote rejected] master -> master (pre-receive hook declined)
error: failed to push some refs to 'https://git.heroku.com/ginnymo.git'

The runtime.txt ,Procfile,requirements.txt are in my  root folder of the project,and I also try to change the runtime.txt to python-3.6.3,try deleting and deploying the app again and again,it seems that the heroku doesn't read my runtime.txt

Make sure runtime.txt is also added to your git repo. Also note that the two choices you have at this time are 2.7.14 and 3.6.3. You cannot use 3.5 with Heroku.

I know what's wrong , I try to install python 3.6.3 in virtualenv,but failed,it turned out that my ubuntu system was broken,due to long time to find the cause,I reinstall the system,install 3.6.3,and no problems happened on the way on heroku.thank you so much..


1.19.2 Compatability

This mod is amazing, but it doesn't seem to work for 1.19.2. I understand not wanting to backport, though I did want to see if a build for this version is possible. Thank you for your time. :)

I would really appreciate a backport for 1.19.2 I would love to use this mod!


Configure SSH

Copy or mount the SSH configuration into the container so it can clone repositories on the host's behalf

https://stackoverflow.com/questions/34932490/inject-hosts-ssh-keys-into-docker-machine-with-docker-compose


Add 'sort' method to Collections

Sometimes people want to find the most recent or latest thing in a collection. This can be done with a single pass through the collection. However, sorting is easier to understand so here's a sorting method for collections that is based on mergesort.

you can use Map.prototype.entries to your advantage to create a much faster and lighter sort using Array.prototype.sort. Tomorrow I can throw something together if you wish.

i came up with this:
sort(fn = (x, y) => x > y) {
  return new Collection(Array.from(this.entries()).sort((a, b) => fn(a[1], b[1], a[0], b[0])));
}

it lets you sort by keys and values for the map and only creates one new collection instead of like four for every time you can evenly divide the collection :)

I was trying to avoid converting to an array at first because I wasn't sure about the cost to do so vs making new objects in JS. After running a few tests today I guess it's a lot more expensive because your method is around 20x faster than this one for Collections of around size 25000.


masterDetail doesnt display on all pages

Hi
I tried to create a masterdetail page using freshmvvm as below. but It looks like that it only display on start up page, when I navigate to any other page that is not the list of MasterPage, it will not be visible
 public App()
    {

        // The root page of your application
        LoadMasterDetail();
    }

public void LoadMasterDetail()
    {
        var masterDetailNav = new FreshMasterDetailNavigationContainer();
        masterDetailNav.Init("Menu", "Menu.png");
        masterDetailNav.AddPage<Page1PageModel>("Page1", null);
        masterDetailNav.AddPage<Page2PageModel>("Page2", null);
        masterDetailNav.AddPage<Page3PageModel>("Page3", null);
        MainPage = masterDetailNav;
    }

So according to above if I have page4Page and Page4PageModel which I am navigating through somewhere else when I am on this page, I dont see any masterdetail container. Is this supposed to be like that?
2nd thing, It executes through each and every pagemodel at the application start. This means if I have some heavy operation in any pageModel, this will reduce application start time. Is there anyway to prevent this?
thanks.

Beside the problem mentioned above, MasterDetailPage is only displayed once and you can never display it again if you navigate to any other page. Because it doesnt actually implement a real navigation page. it takes the first as a primary navigation page. for example. Contacts Page is primary navigation page here. But once you go to ContactDetail page from Contacts page. If you use back button or any other navigation to Contacts page, you wont able to see mastedetailpage.
var masterDetailNav = new FreshMasterDetailNavigationContainer ();
masterDetailNav.Init ("Menu");
masterDetailNav.AddPage<ContactListPageModel> ("Contacts", null);
masterDetailNav.AddPage<QuoteListPageModel> ("Pages", null);
MainPage = masterDetailNav;

I've taken a look and there doesn't seem to be any issue, it works as desired. Can you give some details on your exact issue maybe a screenshot?
In regards to loading once a page is opened you can use the appearing event on the page.


webpack5 devtools hidden-source-map does not generate sourcemap

webpack: 5.92.1
set webpack config  devtools hidden-source-map does not generate sourcemap，set source-map  will generate
I have searched for the following similar questions and have not found a solution:
https://github.com/webpack/webpack/issues/5491
https://github.com/webpack/webpack/issues/5569

Thank you for creating this issue. However, issues need to follow one of our templates so that we can clearly understand your particular circumstances.
Please help us help you by recreating the issue using one of our templates.


Sarif genesis

Description

Simple and Standard Implementation of SARIF for nuclei

Supports both Import & Export

Create an example report by running

  go run example/main.go

It can be viewed using VSCode Sarif Extension or at sarif-webcomponent

Implemented for https://github.com/projectdiscovery/nuclei/issues/2608

With Implementation of Sarif output of [nuclei-gh-action] can be viewed in Security/Code-Scanning-Results of a repository.
as requested at https://github.com/projectdiscovery/nuclei-action/issues/43
something similar to https://www.youtube.com/watch?v=4MduRFoKpGY


YARN-11522. Update the documentation with the YARN-11000 changes.

For code changes:

[x] Does the title or this PR starts with the corresponding JIRA issue id (e.g. 'YARN-11522. Your PR title ...')?
[ ] Object storage: have the integration tests been executed and the endpoint declared according to the connector-specific documentation?
[ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?
[ ] If applicable, have you updated the LICENSE, LICENSE-binary, NOTICE-binary files?

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 30s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  0s

codespell was not available.

+0 :ok:
detsecrets
0m  0s

detect-secrets was not available.

+0 :ok:
markdownlint
0m  0s

markdownlint was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

_ trunk Compile Tests _

+1 :green_heart:
mvninstall
33m 50s

trunk passed

+1 :green_heart:
mvnsite
0m 24s

trunk passed

+1 :green_heart:
shadedclient
54m 50s

branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
0m 13s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
mvnsite
0m 16s

the patch passed

+1 :green_heart:
shadedclient
20m 37s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

+1 :green_heart:
asflicense
0m 29s

The patch does not generate ASF License warnings.

79m 10s

Subsystem
Report/Notes

Docker
ClientAPI=1.43 ServerAPI=1.43 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-5870/1/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/5870

Optional Tests
dupname asflicense mvnsite codespell detsecrets markdownlint

uname
Linux 5d83ecd263a9 4.15.0-213-generic #224-Ubuntu SMP Mon Jun 19 13:30:12 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / 96d1eb8684f7ca9d682449a4873702ddaba80f32

Max. process+thread count
564 (vs. ulimit of 5500)

modules
C: hadoop-yarn-project/hadoop-yarn/hadoop-yarn-site U: hadoop-yarn-project/hadoop-yarn/hadoop-yarn-site

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-5870/1/console

versions
git=2.25.1 maven=3.6.3

Powered by
Apache Yetus 0.14.0 https://yetus.apache.org

This message was automatically generated.

@tomicooler Thank you for your contribution! I quickly read it, LGTM. I will take a closer look later.

@brumi1024 Can you double check this pr? Thank you very much!

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 29s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  0s

codespell was not available.

+0 :ok:
detsecrets
0m  0s

detect-secrets was not available.

+0 :ok:
markdownlint
0m  0s

markdownlint was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

_ trunk Compile Tests _

+1 :green_heart:
mvninstall
33m 59s

trunk passed

+1 :green_heart:
mvnsite
0m 25s

trunk passed

+1 :green_heart:
shadedclient
54m 51s

branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
0m 13s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
mvnsite
0m 16s

the patch passed

+1 :green_heart:
shadedclient
20m 18s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

+1 :green_heart:
asflicense
0m 29s

The patch does not generate ASF License warnings.

78m 58s

Subsystem
Report/Notes

Docker
ClientAPI=1.43 ServerAPI=1.43 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-5870/2/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/5870

Optional Tests
dupname asflicense mvnsite codespell detsecrets markdownlint

uname
Linux cf217b818146 4.15.0-213-generic #224-Ubuntu SMP Mon Jun 19 13:30:12 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / 2f58e5c3ca2bbdeba1808c0395b21ac110b34227

Max. process+thread count
725 (vs. ulimit of 5500)

modules
C: hadoop-yarn-project/hadoop-yarn/hadoop-yarn-site U: hadoop-yarn-project/hadoop-yarn/hadoop-yarn-site

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-5870/2/console

versions
git=2.25.1 maven=3.6.3

Powered by
Apache Yetus 0.14.0 https://yetus.apache.org

This message was automatically generated.

@brumi1024 it can wait for YARN-11514, I used the base scheduler-response.json/xml from the tests.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 28s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  0s

codespell was not available.

+0 :ok:
detsecrets
0m  0s

detect-secrets was not available.

+0 :ok:
markdownlint
0m  0s

markdownlint was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

_ trunk Compile Tests _

+1 :green_heart:
mvninstall
36m 14s

trunk passed

+1 :green_heart:
mvnsite
0m 25s

trunk passed

+1 :green_heart:
shadedclient
56m 57s

branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
0m 13s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
mvnsite
0m 16s

the patch passed

+1 :green_heart:
shadedclient
20m 31s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

+1 :green_heart:
asflicense
0m 29s

The patch does not generate ASF License warnings.

82m  4s

Subsystem
Report/Notes

Docker
ClientAPI=1.43 ServerAPI=1.43 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-5870/3/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/5870

Optional Tests
dupname asflicense mvnsite codespell detsecrets markdownlint

uname
Linux d131aa9fb98e 4.15.0-213-generic #224-Ubuntu SMP Mon Jun 19 13:30:12 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / 6650c836b83a7284bf1032eb7812575d25f96dd2

Max. process+thread count
565 (vs. ulimit of 5500)

modules
C: hadoop-yarn-project/hadoop-yarn/hadoop-yarn-site U: hadoop-yarn-project/hadoop-yarn/hadoop-yarn-site

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-5870/3/console

versions
git=2.25.1 maven=3.6.3

Powered by
Apache Yetus 0.14.0 https://yetus.apache.org

This message was automatically generated.

Thanks @tomicooler for the patch, @slfan1989 for the review, merging to trunk.


Update all the things

Update all the things so as to allow for the building of a new app package.

I'm going to play around with Azure for a few minutes to see if I can get it to test properly.


Tokens always pass validation even with invalid checksums when using asymmetric key algorithms

Hello,
First of all, let me say that my knowledge of Lua can be measured in "days", so please be gentle :-)
I have been using the library for the last weeks, and I it seems that there is a critical bug in the validation of tokens when using asymmetric algorithms (RS256 or RS512).
In the following code in jwt.lua _M:verify_jwt_object:
...
    if alg == str_const.RS256 then
      local verified, err = verifier:verify(message, sig, evp.CONST.SHA256_DIGEST)
    elseif alg == str_const.RS512 then
      local verified, err = verifier:verify(message, sig, evp.CONST.SHA512_DIGEST)
    end
    if not verified then
      jwt_obj[str_const.reason] = err
    end
  else
    jwt_obj[str_const.reason] = "Unsupported algorithm " .. alg
  end

  if not jwt_obj[str_const.reason] then
    jwt_obj[str_const.verified] = true
    jwt_obj[str_const.reason] = str_const.everything_awesome
  end
  return jwt_obj
...

As far as I understand, this piece of code creates variables verified and err in local block scope, meaning that out of the if-then-else they will be nil, no matter what happens after the verification. Then the next piece of code will set the result verified to true depending on reason, which was assigned to nil from the err value.
The end result seems to be that, no matter which key is passed, when this code path is reached the verification will always succeed.
I did a quick fix on my code with something like the following and it seems to work (please excuse my poor Lua):
    -- a previous check makes sure that 'alg' can only be either 'str_const.RS256'
    -- or 'str_const.RS512'
    local evp_digest = nil
    if alg == str_const.RS256 then
      evp_digest = evp.CONST.SHA256_DIGEST
    else
      evp_digest = evp.CONST.SHA512_DIGEST
    end

    local verified, err = verifier:verify(message, sig, evp_digest)

    if not verified then
      jwt_obj[str_const.reason] = err
    end
  else
    jwt_obj[str_const.reason] = "Unsupported algorithm " .. alg
  end

  if not jwt_obj[str_const.reason] then
    jwt_obj[str_const.verified] = true
    jwt_obj[str_const.reason] = str_const.everything_awesome
  end
  return jwt_obj

Am I missing anything here?

Seems like that was introduced only recently when adding support for RS512: https://github.com/SkyLothar/lua-resty-jwt/commit/6de92897ec6fab063d889b33baf6600df3b6f942

I'll dig into it in few days. Thank you guys for reporting.

I understand this shall be closed following #54.

Hello team, could we expect a release soon? I'm still fixing this manually in our build, and in the meantime another critical issue #57 was reported. Both seem to have been fixed in master, just expecting a release so that I can update our build configuration :-)

Just released v0.1.10 on

github
luarocks
opm


Fix #16152

Please note that I have tested this fix only on Ubuntu 16.04 with python 3.5. It should in theory work for both python 2+ and python 3+ but I have not tested it on all major versions of python.

I signed.


In Machine Inventories, the Import YAML button is displayed as an icon rather than the words Import YAML

Setup

Rancher version: v2.6.8
Browser type & version: Chrome

Describe the bug

In the Machine Inventories page, currently here is the view:

In the top-right corner, we have the buttons of Import YAML, Create from YAML and Add Filter. When you hover over the first button, it shows that the button is Import YAML. Rather than having an icon detonate this, it would be better if we have the button explicitly state Import YAML.
We're already stating what the name of the button is as soon as you hover it, so it makes sense to just have the name shown as Import YAML rather than the import icon.
To Reproduce

Setup Rancher and ensure that elemental-operator is applied to access OS Management.
Navigate to OS Management > Create Machine Inventories.

If needed, create a machine registration first, so that you can access.

Note that the Import YAML is an icon rather than the phrase Import YAML itself.

Result
There is an icon that detonates the operation Import YAML.
Expected Result
The button should simply state Import YAML instead of being an icon that signifies what the operation is doing.

@kwwii Thoughts?


Flutterwave payment  webview  screen does not close when close button is pressed

I have been trying to process flutter-wave transaction in react native using  PayWithFlutterWave component in flutterwave-react-native.However,after the OTP verification step, and entering my momo pin,I wanted to close the Flutterwave payment modal by tapping on the close button at the top right corner of the flutterwave  payment screen. Tapping the close button does not close the modal. It show the attached image.
Kindly assist me to fix.

Hi @Akola-Mbey-Denis, there appears to be no button on the top right corner of the page, can you share a state in which the button on the top right shows? Also, are you saying that when you tap on the close button it loads nonstop as shown on your attached image?

Thanks,I increase the view height of the web view and I was able to close the button.

All right @Akola-Mbey-Denis will be closing this now, but feel free to reopen anytime you experience this again.


Update proposal.md

I need a review.

Oh I forgot the project vision statement.


Add note to Spinnaker doc about destination path for additionalConfigMaps

What this PR does / why we need it:
A suggestion for improving docs. I spent a while trying to figure out where additional configMaps are uploaded to the halyard pod on a k8s spinnaker deployment so they could be used in config scripts, and this one line would've helped.
Special notes for your reviewer:
I realize Spinnaker is deployed on multiple kinds of infra, not just k8s, which is why I didn't mention a halyard pod, but maybe there's a better way to make this note generic.
Checklist

[x] DCO signed

The linter is complaining because I didn't bump the chart version, but I don't think this change needs a version bump since it's just documentation.

All changes require a version bump since the contents of the chart will
change.
On Thu, Feb 14, 2019 at 1:17 PM Miles Matthias<EMAIL_ADDRESS>wrote:

The linter is complaining because I didn't bump the chart version, but I
don't think this change needs a version bump since it's just documentation.
—
You are receiving this because your review was requested.
Reply to this email directly, view it on GitHub
https://github.com/helm/charts/pull/11437#issuecomment-463800411, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAZCp2qE240wrqkZlF4z7Sh-aWSMvUHWks5vNdJYgaJpZM4a8dGH
.

Bumped chart version.

/lgtm


What is the way to serialise strings with double quotes instead of single quotes?

Single quotes are slightly inconvenient when the text inside is mostly English, and contains no escape sequence.

Maintenance of this crate has moved to the https://github.com/toml-rs/toml repo.  As a heads up, we plan to move toml to be on top of toml_edit, see https://github.com/toml-rs/toml/issues/340.
Closing this out.  If this is still a problem, feel free to recreate this issue in the new repo.


Add dependency files to repo to enable offline developing.

Right now, all the dependencies are being served from CDNs. This prevents us from developing when offline. So it would be better to have the file served from our servers itself.
Major dependencies:

[ ] jQuery

[ ] Material.css

[ ] Material

[ ] Scroll Reveal.js

@digi0ps We can serve it locally for development, but I think it would rather be better to stick with the CDNs for serving production. How do we isolate it only for development though?

That seems good!
We can do it through an if condition in the base template.


chapter3:  norm_conf_mx =  conf_mx  / row_sums :return all zeros

in python 2.7
"norm_conf_mx =  conf_mx  / row_sums"
returns all 0 array.
so, to get float array
norm_conf_mx  =  (conf_mx * 1.0)  / row_sums"

This issue is due to python version.
In python3,  "norm_conf_mx = conf_mx / row_sums"  returns  float array.
I think code in this boook supports python 2.7.

from __future__ import division


Execution fails because of insufficient permissions

Hello,
The codecarbon execution fails because of insufficient permissions to access the GPU NVML interface, is there any way I can resolve this or disable GPU tracking? (I can not get permissions)
Thanks in advance!
A part of the error logs:
File "/usr/local/lib/python3.9/dist-packages/codecarbon/emissions_tracker.py", line 284, in init
gpu_devices = GPU.from_utils(self._gpu_ids)
File "/usr/local/lib/python3.9/dist-packages/codecarbon/external/hardware.py", line 121, in from_utils
return cls(gpu_ids=gpu_ids)
File "", line 4, in init
File "/usr/local/lib/python3.9/dist-packages/codecarbon/external/hardware.py", line 63, in post_init
self.devices = AllGPUDevices()
File "/usr/local/lib/python3.9/dist-packages/codecarbon/core/gpu.py", line 208, in init
gpu_device = GPUDevice(handle=handle, gpu_index=i)
File "", line 8, in init
File "/usr/local/lib/python3.9/dist-packages/codecarbon/core/gpu.py", line 47, in post_init
self._init_static_details()
File "/usr/local/lib/python3.9/dist-packages/codecarbon/core/gpu.py", line 83, in _init_static_details
memory = self._get_memory_info()
File "/usr/local/lib/python3.9/dist-packages/codecarbon/core/gpu.py", line 137, in _get_memory_info
return pynvml.nvmlDeviceGetMemoryInfo(self.handle)
File "/usr/local/lib/python3.9/dist-packages/pynvml/nvml.py", line 2440, in nvmlDeviceGetMemoryInfo
_nvmlCheckReturn(ret)
File "/usr/local/lib/python3.9/dist-packages/pynvml/nvml.py", line 833, in _nvmlCheckReturn
raise NVMLError(ret)
Message:
Insufficient Permissions

User error.

Thanks, you're right, CodeCarbon should be able to run without monitoring GPU.
Do you know how can we reproduce this ?


Dapr AWS X-Ray Tracing Exporter for OpenTelemetry Collector is not exporting traces to AWS X-Ray

Note: If you have a general support question and are looking for a quicker response, please checkout our discord channel for answers from the community:
https://aka.ms/dapr-discord
In what area(s)?

/area runtime

/area operator

/area placement

/area docs

/area test-and-release

Ask your question here
Deployed services on EKS and configured Dapr to send distributed tracing data. Deployed Dapr OpenTelemetry Collector using Dapr AWS X-Ray Exporter to export traces to X-Ray. But tracing data is not exported to X-Ray

@aniljdk
Just to double check, did you follow these instructions?

@olitomlinson
i  have followed instructions from
https://docs.dapr.io/operations/monitoring/tracing/open-telemetry-collector/
https://aws-otel.github.io/docs/getting-started/x-ray#configuring-the-aws-x-ray-exporter

Hi Team,
Greetings, can someone please help us with the configuration to export traces from DAPR to AWS Xray through Open telemetry exporter , DAPR and Open telemetry running on EKS
Reciever config is as follows
  otlp:
    protocols:
      grpc:
        endpoint: <IP_ADDRESS>:4317
      http:
        endpoint: <IP_ADDRESS>:4318
  awsxray:
  awsxray/udp_endpoint:
      endpoint: "<IP_ADDRESS>:5678"
      transport: udp
  awsxray/proxy_server:
      proxy_server:
        endpoint: "<IP_ADDRESS>:1234"
        tls:
          insecure: true
        region: ap-south-1

Exporter config is as follows
  awsxray:
    region: ap-south-1
    index_all_attributes: true
    resource_arn: "arn:aws:iam:xxxxxxxxxxx:role/xyzNodegroup"
    role_arn: "arn:aws:iam::xxxxxxxxxxx:role/abc"

Service configuration as follows:
service:
  extensions: [pprof, zpages, health_check]
  pipelines:
    traces:
      receivers: [otlp]
      # List your exporter here.
      exporters: [awsxray,logging]

DAPR Configuration as follows
apiVersion: dapr.io/v1alpha1
kind: Configuration
metadata:
name: appconfig
namespace: dapr-test
spec:
tracing:
samplingRate: "1"
zipkin:
endpointAddress: "http://otel-collector.dapr-test.svc.cluster.local:9411/api/v2/spans"
Tried configuring receiver as both otlp and awsxray and getting below mentioned error , Any help would be very much appreciated
Getting following error in DAPR
2022/09/12 18:54:54 failed to send the request: Post "http://otel-collector.dapr-test.svc.cluster.local:9411/api/v2/spans": dial tcp x.x.x.x:9411: connect: connection refused
2022/09/12 18:54:55 failed to send the request: Post "http://otel-collector.dapr-test.svc.cluster.local:9411/api/v2/spans": dial tcp x.x.x.x:9411: connect: connection refused
2022/09/12 18:54:56 failed to send the request: Post "http://otel-collector.dapr-test.svc.cluster.local:9411/api/v2/spans": dial tcp x.x.x.x:9411: connect: connection refused
2022/09/12 18:54:57 failed to send the request: Post "http://otel-collector.dapr-test.svc.cluster.local:9411/api/v2/spans": dial tcp x.x.x.x:9411: connect: connection refused
2022/09/12 18:54:59 failed to send the request: Post "http://otel-collector.dapr-test.svc.cluster.local:9411/api/v2/spans": dial tcp x.x.x.x:9411: connect: connection refused


Remove check that _id is an instance of ObjectID

This removes a check that _id is an instance of ObjectID. My understanding when reading the docs is that the _id is recommended to be an ObjectId, but that it is not required. When I tested with a database for parse-server (which uses strings as _id), updates to documents failed with  the following error InvalidArugmentError('objectId must be an instance of ObjectId');. With the check removed it worked perfectly.

awesome looks good, thanks @simonbengtsson !


Restore "snap to minimize/maximize" feature with grid editor layout

VSCode Version: 1.25.0-insider
OS Version: Windows 7

Steps to Reproduce:

Open 2 files
Split panes
Drag the panes so one is as small as possible
Click that pane

Expected Result
The small pane, when clicked on, should expand to take as much space as possible, shrinking the other pane(s).
Actual Result
The pane stays small.

Does this issue occur when all extensions are disabled?: Yes

This came in when we moved to grid. @joaomoreno to comment how feasible it would be to restore this in the grid widget.

Unpleasantly surprised to discover this feature gone in the stable release yesterday. Please bring this feature back.

Pushed a change to maximize a view in the grid that is either vertically or horizontally with minimal size.

Thank you!

@bpasero May I ask if the feature is released in  1.25.1? My view is not expanded when focused

@lsps9150414 no, July is 1.26. But you can stop waiting for stable releases and start using our nightly releases where this fix already landed: You can give our preview releases a try from: https://code.visualstudio.com/insiders/


Hosting an angular library outside the application module

Bug Report or Feature Request (mark with an x)

[ ] bug report -> please search issues before submitting
[x ] feature request
Command (mark with an x)
[ ] new
[ ] build
[ ] serve
[ ] test
[ ] e2e
[ x] generate
[ ] add
[ ] update
[ ] lint
[ ] xi18n
[ ] run
[ ] config
[ ] help
[ ] version
[ ] doc
Versions
Angular CLI: 7.1.2
Node: 8.11.3
OS: win32 x64

Package Version
@angular-devkit/architect 0.11.2
@angular-devkit/core 7.1.2
@angular-devkit/schematics 7.1.2
@schematics/angular 7.1.2
@schematics/update 0.11.2
rxjs 6.3.3
typescript 3.1.6
Repro steps
ng generate library "mylib"
Desired functionality
Hi,
I want to create Angular libraries, while having the "container" app living in another "npm" module. I need to do this for module sharing purposes, for clear module separation concerns and because our app is already organized in that way.
This is the target architecture I'm trying to achieve :
-> myApp (NPM module)
----> angular.json
----> src
----> package.json
-> myLib1 (another NPM module, not living inside myApp)
----> src
----> some .ts files
----> dist
----> package.json
-> myLib2 (yet another NPM module not living inside myApp)
----> src
----> some .ts files
----> dist
----> package.json
I cannot achieve this result by using CLI options or by setting "newProjectRoot" parameter to ".. " in myApp/angular.json for example.
I would like to avoid re-creating for each library an empty "app" container, that embeds a "projects" folder, itself contains a "library" folder, itself containing an "src" folder...
Since I'm using Yarn, I have a root-level "nodes_modules" folder containing symlinks pointing to myLib1 and myLib2, so I do not need to have everything "installed" in the same folder.
Do you see a solution with actual CLI tools for :
having the bootstrapping app in one module
having the library folder in another module, not inside the app
avoiding recreating a folder scaffolding in each library ?
Thanks in advance ;)

@djflex68 thanks for sharing your idea! At the moment you should be able to achieve this using something like this:
If myApp depends on myLib1, you can update package.json of myApp to:
"dependencies": {
  "myLib1": "../myLib1/dist/myLib1"
}

This way myApp will take the package from dist.
Also look at the multi app support https://github.com/angular/angular-cli/wiki/stories-multiple-apps.


fail to run controller_manager

THIS IS my controller.yaml file
controller_manager:
  ros__parameters:
    update_rate: 100 # Hz

    joint_state_broadcaster:
      type: joint_state_broadcaster/JointStateBroadcaster

    joint0_position_controller:
      type: position_controllers/JointGroupPositionController

    joint0_velocity_controller:
      type: velocity_controllers/JointGroupVelocityController

    joint0_effort_controller:
      type: effort_controllers/JointGroupEffortController

    joint1_position_controller:
      type: position_controllers/JointGroupPositionController

    joint1_velocity_controller:
      type: velocity_controllers/JointGroupVelocityController

    joint1_effort_controller:
      type: effort_controllers/JointGroupEffortController

    group_position_controller:
      type: position_controllers/JointGroupPositionController

    group_velocity_controller:
      type: velocity_controllers/JointGroupVelocityController

    group_effort_controller:
      type: effort_controllers/JointGroupEffortController

joint0_position_controller:
  ros__parameters:
    joints:
      - joint0

joint0_velocity_controller:
  ros__parameters:
    joints:
      - joint0

joint0_effort_controller:
  ros__parameters:
    joints:
      - joint0

joint1_position_controller:
  ros__parameters:
    joints:
      - joint1

joint1_velocity_controller:
  ros__parameters:
    joints:
      - joint1

joint1_effort_controller:
  ros__parameters:
    joints:
      - joint1

group_position_controller:
  ros__parameters:
    joints:
      - joint0
      - joint1

group_velocity_controller:
  ros__parameters:
    joints:
      - joint0
      - joint1

group_effort_controller:
  ros__parameters:
    joints:
      - joint0
      - joint1

This is my launch file
# Copyright 2021 Factor Robotics
#
# Licensed under the Apache License, Version 2.0 (the "License");
# you may not use this file except in compliance with the License.
# You may obtain a copy of the License at
#
#     http://www.apache.org/licenses/LICENSE-2.0
#
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the License for the specific language governing permissions and
# limitations under the License.

from launch import LaunchDescription
from launch.actions import DeclareLaunchArgument
from launch.conditions import IfCondition
from launch.substitutions import Command, FindExecutable, LaunchConfiguration, PathJoinSubstitution
from launch_ros.actions import Node
from launch_ros.substitutions import FindPackageShare

def generate_launch_description():
    declared_arguments = []

    declared_arguments.append(
        DeclareLaunchArgument(
            "enable_joint0",
            default_value="true",
        )
    )

    declared_arguments.append(
        DeclareLaunchArgument(
            "enable_joint1",
            default_value="true",
        )
    )

    declared_arguments.append(
        DeclareLaunchArgument(
            "joint0_controller",
            default_value="joint0_position_controller",
        )
    )
    declared_arguments.append(
        DeclareLaunchArgument(
            "joint1_controller",
            default_value="joint1_position_controller",
        )
    )

    enable_joint0 = LaunchConfiguration("enable_joint0")
    enable_joint1 = LaunchConfiguration("enable_joint1")
    joint0_controller = LaunchConfiguration("joint0_controller")
    joint1_controller = LaunchConfiguration("joint1_controller")

    robot_description_content = Command(
        [
            PathJoinSubstitution([FindExecutable(name="xacro")]),
            " ",
            PathJoinSubstitution(
                [
                    FindPackageShare("odrive_description"),
                    "urdf",
                    "odrive.urdf.xacro",
                ]
            ),
            " ",
            "enable_joint0:=",
            enable_joint0,
            " ",
            "enable_joint1:=",
            enable_joint1,
        ]
    )
    robot_description = {"robot_description": robot_description_content}

    robot_controllers = PathJoinSubstitution(
        [
            FindPackageShare("odrive_bringup"),
            "config",
            "odrive_controllers.yaml",
        ]
    )

    control_node = Node(
        package="controller_manager",
        executable="ros2_control_node",
        parameters=[robot_description, robot_controllers],
        output={
            "stdout": "screen",
            "stderr": "screen",
        },
    )

    robot_state_pub_node = Node(
        package="robot_state_publisher",
        executable="robot_state_publisher",
        output="both",
        parameters=[robot_description],
    )

    joint_state_broadcaster_spawner = Node(
        package="controller_manager",
        executable="spawner.py",
        arguments=["joint_state_broadcaster", "--controller-manager", "/controller_manager"],
    )

    joint0_controller_spawner = Node(
        package="controller_manager",
        executable="spawner.py",
        arguments=[joint0_controller, "-c", "/controller_manager"],
        condition=IfCondition(enable_joint0),
    )

    joint1_controller_spawner = Node(
        package="controller_manager",
        executable="spawner.py",
        arguments=[joint1_controller, "-c", "/controller_manager"],
        condition=IfCondition(enable_joint1),
    )

    nodes = [
        control_node,
        robot_state_pub_node,
        joint_state_broadcaster_spawner,
        joint0_controller_spawner,
        joint1_controller_spawner,
    ]

    return LaunchDescription(declared_arguments + nodes)

[ERROR] [ros2_control_node-1]: process has died [pid 28410, exit code -6, cmd '/opt/ros/foxy/lib/controller_manager/ros2_control_node --ros-args --params-file /tmp/launch_params_0nfwf8mm --params-file /home/khadas/workspace/install/odrive_bringup/share/odrive_bringup/config/odrive_controllers.yaml'].
Could any one tell me the reason why it fails?

Hi,
Your configuration looks fine, there should be other problems. Is there any other error message before this one? Other issues like communication failures can cause this error.

I've used default configurations with jetson nano and version ROS foxy. I'm a beginner with ROS2 I don't know the real problem, please acknowledge the problem. I don't know the real problem.
INFO] [launch]: Default logging verbosity is set to INFO [INFO] [ros2_control_node-1]: process started with pid [7383] [INFO] [robot_state_publisher-2]: process started with pid [7385] [INFO] [spawner.py-3]: process started with pid [7387] [INFO] [spawner.py-4]: process started with pid [7389] [robot_state_publisher-2] Parsing robot urdf xml string. [robot_state_publisher-2] Link link0 had 0 children [robot_state_publisher-2] [INFO] [1655720483.823214464] [robot_state_publisher]: got segment link0 [robot_state_publisher-2] [INFO] [1655720483.823509470] [robot_state_publisher]: got segment world [spawner.py-3] Traceback (most recent call last): [spawner.py-3]   File "/opt/ros/foxy/lib/controller_manager/spawner.py", line 204, in <module> [spawner.py-3]     sys.exit(main()) [spawner.py-3]   File "/opt/ros/foxy/lib/controller_manager/spawner.py", line 123, in main [spawner.py-3]     if is_controller_loaded(node, controller_manager_name, controller_name): [spawner.py-3]   File "/opt/ros/foxy/lib/controller_manager/spawner.py", line 65, in is_controller_loaded [spawner.py-3]     controllers = list_controllers(node, controller_manager).controller [spawner.py-3]   File "/opt/ros/foxy/lib/python3.8/site-packages/controller_manager/controller_manager_services.py", line 49, in list_controllers [spawner.py-3]     return service_caller(node, f'{controller_manager_name}/list_controllers', [spawner.py-3]   File "/opt/ros/foxy/lib/python3.8/site-packages/controller_manager/controller_manager_services.py", line 29, in service_caller [spawner.py-3]     raise RuntimeError(f'Could not contact service {service_name}') [spawner.py-3] RuntimeError: Could not contact service /controller_manager/list_controllers [spawner.py-4] Traceback (most recent call last): [spawner.py-4]   File "/opt/ros/foxy/lib/controller_manager/spawner.py", line 204, in <module> [spawner.py-4]     sys.exit(main()) [spawner.py-4]   File "/opt/ros/foxy/lib/controller_manager/spawner.py", line 123, in main [spawner.py-4]     if is_controller_loaded(node, controller_manager_name, controller_name): [spawner.py-4]   File "/opt/ros/foxy/lib/controller_manager/spawner.py", line 65, in is_controller_loaded [spawner.py-4]     controllers = list_controllers(node, controller_manager).controller [spawner.py-4]   File "/opt/ros/foxy/lib/python3.8/site-packages/controller_manager/controller_manager_services.py", line 49, in list_controllers [spawner.py-4]     return service_caller(node, f'{controller_manager_name}/list_controllers', [spawner.py-4]   File "/opt/ros/foxy/lib/python3.8/site-packages/controller_manager/controller_manager_services.py", line 29, in service_caller [spawner.py-4]     raise RuntimeError(f'Could not contact service {service_name}') [spawner.py-4] RuntimeError: Could not contact service /controller_manager/list_controllers [ERROR] [spawner.py-4]: process has died [pid 7389, exit code 1, cmd '/opt/ros/foxy/lib/controller_manager/spawner.py joint0_velocity_controller -c /controller_manager --ros-args']. [ERROR] [spawner.py-3]: process has died [pid 7387, exit code 1, cmd '/opt/ros/foxy/lib/controller_manager/spawner.py joint_state_broadcaster --controller-manager /controller_manager --ros-args'].

I've used default configurations with jetson nano and version ROS foxy. I'm a beginner with ROS2 I don't know the real problem, please acknowledge the problem. I don't know the real problem.
INFO] [launch]: Default logging verbosity is set to INFO [INFO] [ros2_control_node-1]: process started with pid [7383] [INFO] [robot_state_publisher-2]: process started with pid [7385] [INFO] [spawner.py-3]: process started with pid [7387] [INFO] [spawner.py-4]: process started with pid [7389] [robot_state_publisher-2] Parsing robot urdf xml string. [robot_state_publisher-2] Link link0 had 0 children [robot_state_publisher-2] [INFO] [1655720483.823214464] [robot_state_publisher]: got segment link0 [robot_state_publisher-2] [INFO] [1655720483.823509470] [robot_state_publisher]: got segment world [spawner.py-3] Traceback (most recent call last): [spawner.py-3] File "/opt/ros/foxy/lib/controller_manager/spawner.py", line 204, in <module> [spawner.py-3] sys.exit(main()) [spawner.py-3] File "/opt/ros/foxy/lib/controller_manager/spawner.py", line 123, in main [spawner.py-3] if is_controller_loaded(node, controller_manager_name, controller_name): [spawner.py-3] File "/opt/ros/foxy/lib/controller_manager/spawner.py", line 65, in is_controller_loaded [spawner.py-3] controllers = list_controllers(node, controller_manager).controller [spawner.py-3] File "/opt/ros/foxy/lib/python3.8/site-packages/controller_manager/controller_manager_services.py", line 49, in list_controllers [spawner.py-3] return service_caller(node, f'{controller_manager_name}/list_controllers', [spawner.py-3] File "/opt/ros/foxy/lib/python3.8/site-packages/controller_manager/controller_manager_services.py", line 29, in service_caller [spawner.py-3] raise RuntimeError(f'Could not contact service {service_name}') [spawner.py-3] RuntimeError: Could not contact service /controller_manager/list_controllers [spawner.py-4] Traceback (most recent call last): [spawner.py-4] File "/opt/ros/foxy/lib/controller_manager/spawner.py", line 204, in <module> [spawner.py-4] sys.exit(main()) [spawner.py-4] File "/opt/ros/foxy/lib/controller_manager/spawner.py", line 123, in main [spawner.py-4] if is_controller_loaded(node, controller_manager_name, controller_name): [spawner.py-4] File "/opt/ros/foxy/lib/controller_manager/spawner.py", line 65, in is_controller_loaded [spawner.py-4] controllers = list_controllers(node, controller_manager).controller [spawner.py-4] File "/opt/ros/foxy/lib/python3.8/site-packages/controller_manager/controller_manager_services.py", line 49, in list_controllers [spawner.py-4] return service_caller(node, f'{controller_manager_name}/list_controllers', [spawner.py-4] File "/opt/ros/foxy/lib/python3.8/site-packages/controller_manager/controller_manager_services.py", line 29, in service_caller [spawner.py-4] raise RuntimeError(f'Could not contact service {service_name}') [spawner.py-4] RuntimeError: Could not contact service /controller_manager/list_controllers [ERROR] [spawner.py-4]: process has died [pid 7389, exit code 1, cmd '/opt/ros/foxy/lib/controller_manager/spawner.py joint0_velocity_controller -c /controller_manager --ros-args']. [ERROR] [spawner.py-3]: process has died [pid 7387, exit code 1, cmd '/opt/ros/foxy/lib/controller_manager/spawner.py joint_state_broadcaster --controller-manager /controller_manager --ros-args'].

Hi @ReginaldSourn,
Just check that you have selected the correct branch, must be the same as your odrive firmware version. I had the same problem with the RPi board, after the branch change, everything works great.

Thank @rgruberski!!
Your solutions Still not working. I try to dig to get some clues. For now, I have questions for @borongyuan  ** why the spawner /controller_manager/list_controller can't find  joint_state_broadcaster? is it the bug from hardware_interface ?**
Thanks for the answers @borongyuan. _ My Remote is JETSON_NANO and I using Ros Foxy _. Thanks!!!

@rgruberski you're right !!  what I was missing is I changed only the Odrivetool version and branch version switching from fw-v0.5.3 to fw-v0.5.1. I haven't changed firmware by using odrivetool dfu and downgrading versions of the firmware Odrive. So, to change firmware we need to go Odrive Firmware Release  and then download the correct firmware matching with the branch we want to use. I am using fw-v0.5.3 firmware to upload it :

power off Odrive Controller Devices
Download the right firmware .hex and go to the file download direction.
run  odrivetool df ODriveFirmware_v**_***V.hex
turn on power Odrive Controller Devices and it starts to erase and upload new firmware.
Once it's finished, turn off or restart Devices that's it.

libsub also can create trouble in compiling also please make sure we use libusb-1.0.0 not libusb-0.1-4.
after that, we need configurations odrive hardware with python scripts before running testing axis0 spinning.
Thank @borongyuan for giving me the answer.

@ReginaldSourn I did all the steps you mentioned, flashed the firmware, removed libusb-0.1-4 so it won't mess up with the driver yet it's not working.
What are the odrive hardware configuration you mentioned?

Found the solution.
Odrivetool was blocking the USB port, I had to quit it so the driver can access it


WIP: Vercel edge

⚠ Don't review yet. It's not ready
Describe this PR

This PR adds a Vercel Edge function guide.
Technologies:

Vercel Edge functions
Postgres
Prisma
Typescript

Changes

Added a new guide

Any other relevant information

@matthewmueller randomly found this, Vercel Edge functions are in beta now, any plan to finish this?

Not for now, but this could be a decent starting point if someone wants to push it over the finish line. (Going through old PRs and closing them)


Default timeout(90s) of downstream requests is broken

Expected Behavior
According to the documentation, if QoSOptions is not configured, by default, the timeout value for downstream requests is set to 90 seconds. In our project, using Ocelot 18.0.0 + .NET 6, the runtime behavior aligns with the documentation.

Actual Behavior
When we upgraded to Ocelot 22.0.0 + .NET 8, also without configuring QoSOptions, the downstream requests never timeout.
Specifications

Version: 22.0.0
Platform: .NET 8

I took a brief look at the code and noticed that in version 22.0.0, the default value of TimeoutValue in QoSOptions was changed from 0 to int.MaxValue. The code where the default value of 90 seconds is effective seems to be here when it is set to 0. I'm not sure if my analysis is correct.

Hi Alvin!
Thanks for reporting the bug!
Yes, your analysis is correct! The code is not consistent now because the bug was introduced in the default constructor of the FileQoSOptions class.
Will you open a PR with the fix? It should be pretty short and simple to assign zero in default constructor like this
        public FileQoSOptions()
        {
            DurationOfBreak = 1;
            ExceptionsAllowedBeforeBreaking = 0;
            TimeoutValue = 0; // int.MaxValue bug
        }

@raman-m
Thank you for your prompt response! I'm happy to contribute to the pull request #1834.

Released by #1847


fix: Ensure resultSize resolves to a number.

Fixes #1116.
Passing a number to parseInt is safe so this won't break any calling
code that is already manually doing the casting.

Coverage increased (+0.0002%) to 97.262% when pulling 8f448db29aad39ac093c47ef3fa4eeb334adfab4 on mastermatt:bug/ensure-resultsize-resolves-to-number into 17b65dee7f1f0198a64314925f34b85b4b019d16 on Vincit:master.

Coverage increased (+0.0002%) to 97.262% when pulling 8f448db29aad39ac093c47ef3fa4eeb334adfab4 on mastermatt:bug/ensure-resultsize-resolves-to-number into 17b65dee7f1f0198a64314925f34b85b4b019d16 on Vincit:master.

Coverage increased (+0.0002%) to 97.262% when pulling 8f448db29aad39ac093c47ef3fa4eeb334adfab4 on mastermatt:bug/ensure-resultsize-resolves-to-number into 17b65dee7f1f0198a64314925f34b85b4b019d16 on Vincit:master.


cmd/go: 'build output "...." already exists and is not an object file' error after interrupted compilation

What version of Go are you using (go version)?

$ go version
go version go1.19.3 linux/amd64

Does this issue reproduce with the latest release?
Unknown.
What did you do?
Rough steps:

Interrupt a build with ^C
Make some changes that cause our build system to attempt to rebuild the binary (like git rebase)
Run the build

What did you expect to see?
No error.
What did you see instead?
go build go.fuchsia.dev/fuchsia/tools/fidl/fidlmerge: build output "../../../../fidlmerge" already exists and is not an object file

Upon inspection, the file starts with 4KB of 0x00s, which definitely isn't an object file.  But the block of the file at 0x1000 does match the contents of the file that's written by the compiler if I delete the "bad" file and re-run the build.

The only workaround seems to be to delete the output file and try again.

is this using the go tool or bazel ?

Yes, looks related. This is using the go tool.

The 4KB of zeros could be related to #53804 (which is a kernel bug as far as we understand). But this issue is about interrupting a build with ctrl-C, which leaves more uncertainty and could result in a corrupted file in other ways.
I think this issue is more about whether the go command should emit an error for an existing non-object output file (possibly due to corruption)? If so, this would be working as intended.

Thanks @woody77.
The issue had reproduced for me as well, thanks for aiming to fix it.


[Improvement]: Change strand dump tests to wait on logs instead of timed wait

Description
$title
Then it is will adapt to delays in starting processes if needed, and will complete the test as soon as possible.
Describe your problem(s)
No response
Describe your solution(s)
No response
Related area
-> Runtime
Related issue(s) (optional)
No response
Suggested label(s) (optional)
No response
Suggested assignee(s) (optional)
No response

See https://scans.gradle.com/s/gbnsxyjilv2t4/tests/:jballerina-integration-test:test/org.ballerinalang.test.troubleshoot.StrandDumpTest?top-execution=1

https://scans.gradle.com/s/nqqx5r7faftb4/tests/:jballerina-integration-test:test/org.ballerinalang.test.troubleshoot.StrandDumpTest/testStrandDumpDuringBalTest?expanded-stacktrace=WyIwIl0&top-execution=1
https://scans.gradle.com/s/nqqx5r7faftb4/tests/overview?outcome=failed

Enable strand dump tests after fixing this. Search // TODO: enable after fixing https://github.com/ballerina-platform/ballerina-lang/issues/38737


Build of rav1e 0.3.5 on Alpine Linux fails for aarch64 and ppc64le with bus error

Build for Alpine Linux [1] fails with same error for both architectures:
365    Finished release [optimized + debuginfo] target(s) in 13m 46s
366 Bus error (core dumped)
367 >>> ERROR: rav1e: build failed

Build log for aarch64 is here [2], for ppc64le is here [3].
[1] https://gitlab.alpinelinux.org/alpine/aports/-/merge_requests/16346
[2] https://gitlab.alpinelinux.org/otlabs/aports/-/jobs/292026#L366
[3] https://gitlab.alpinelinux.org/otlabs/aports/-/jobs/283623#L369

Can you please provide the stand alone command that is failing? Which kind of hardware is used to run those jobs?

Can you please provide the stand alone command that is failing? Which kind of hardware is used to run those jobs?

Sure, with pleasure.
I use:
build() {
	cargo build --release --frozen
	cargo cbuild --release --frozen --prefix /usr
}

It is the same build procedure used to successfully build rav1e 0.3.4.
I will investigate about used hardware and comment later.

Sure, with pleasure.
I use:
build() {
	cargo build --release --frozen
	cargo cbuild --release --frozen --prefix /usr
}

It is the same build procedure used to successfully build rav1e 0.3.4.
I will investigate about used hardware and comment later.

So to reproduce it I'd have to run cargo cbuild (which cargo-c version?) on native power9 and aarch64?

So to reproduce it I'd have to run cargo cbuild (which cargo-c version?) on native power9 and aarch64?

cargo-c (0.7.0-r0) was used.
Sorry, I still have no info about hardware.

cargo-c (0.7.0-r0) was used.
Sorry, I still have no info about hardware.

From the build logs:
(12/15) Installing cargo-c (0.7.0-r0)

From the build logs:
(12/15) Installing cargo-c (0.7.0-r0)

Running this on our CI host (qemu) as our builders (LXC on baremetal) results in the same:
Program received signal SIGILL, Illegal instruction.
0x0000fffff7be64d0 in ?? () from /usr/bin/../lib/libcrypto.so.1.1

Our builder runs on Ampere eMAG servers, but as this seems to happen on both qemu as baremetal, it does not seem to be hardware related.

Running this on our CI host (qemu) as our builders (LXC on baremetal) results in the same:
Program received signal SIGILL, Illegal instruction.
0x0000fffff7be64d0 in ?? () from /usr/bin/../lib/libcrypto.so.1.1

Our builder runs on Ampere eMAG servers, but as this seems to happen on both qemu as baremetal, it does not seem to be hardware related.

It seems that the openssl provider is doing something fishy.

It seems that the openssl provider is doing something fishy.

It's strange though that we get a SIGBUS normally, and a SIGILL when running under gdb.

It's strange though that we get a SIGBUS normally, and a SIGILL when running under gdb.

Can you confirm that the current cargo-c release does not show the problem?

Currently rav1e 0.4.0 was built with cago-c 0.7.1 without any problem.

Tried to build rav1e 0.4.1 with cargo-c 0.8.0 and got no any .so libraries built. I was expecting to get: librav1e.so.0 and librav1e.so.0.4.1.

Could you please open an issue on cargo-c ? I think it is due how the musl target is managed, if you want shared libraries on a musl-based distribution it requires probably some cli overrides.

Done! https://github.com/lu-zero/cargo-c/issues/180

rav1e 0.4.1 with cargo-c 0.8.0  builds as expected with --library-type staticlib --library-type cdylib.


Convert Bull Creek use case data to CDL

Encode all geometries in a single NetCDF3 & 4 file with CDL. Use case data located here.

[ ] NetCDF3 Encoding
[ ] NetCDF4 Encoding
[ ] NetCDF3 Multi-Geometry Encoding
[ ] NetCDF4 Multi-Geometry Encoding

NetCDFs created with and without CRAs. If you'd like to take a look, they are here: https://www.dropbox.com/sh/sn1sijgi6a2hoo1/AABmxt8A_CACPTztDI3tk_4Ta?dl=0.
I am pondering how best to hold multiple geometry variables in a single file. For this example, I gave each "CF geometry collection" a unique string identifier. You'll notice a number duplicate dimensions with the same length. We could write a function to re-index coordinate arrays and stack the coordinate variables. This would make for a cleaner CDL, but it would add complexity if a client wished to break the geometries into separate files...or whatever.

Script used to generated NetCDFs: https://github.com/bekozi/netCDF-CF-simple-geometry/blob/master/misc/create_cdl_bull_creek.py
Note, data variables still need to be added to files.

Added GeoJSON properties as data variables in the example netCDF. I was vexed how to use the time series approach as these properties have no associated time. Some standard attributes are used to link data variables with their coordinate index variable in the meantime. Here is CDL for the CRA case:
benkoziol:[tmp]$ ncdump -h bull_creek_NCSG_CRA.nc
netcdf bull_creek_NCSG_CRA {
dimensions:
	catchments_node = 4275 ;
	catchments_geom = 20 ;
	catchments_node_index = 4276 ;
	flowlines_node = 515 ;
	flowlines_geom = 20 ;
	flowlines_node_index = 515 ;
	upstream_node = 20 ;
	upstream_geom = 20 ;
	upstream_node_index = 20 ;
variables:
	int64 catchments_coordinate_index(catchments_node_index) ;
		catchments_coordinate_index:cf_role = "simple_geom" ;
		catchments_coordinate_index:geom_type = "multipolygon" ;
		catchments_coordinate_index:stop_encoding = "cra" ;
		catchments_coordinate_index:coordinates = "catchments_x catchments_y" ;
		catchments_coordinate_index:multipart_break_value = -1LL ;
		catchments_coordinate_index:hole_break_value = -2LL ;
		catchments_coordinate_index:outer_ring_order = "anticlockwise" ;
		catchments_coordinate_index:closure_convention = "last_node_equals_first" ;
	int64 catchments_geom_stop(catchments_geom) ;
		catchments_geom_stop:continuous_ragged_dimension = "catchments_node_index" ;
	double catchments_x(catchments_node) ;
	double catchments_y(catchments_node) ;
	double catchments_AreaSqKM(catchments_geom) ;
		catchments_AreaSqKM:cf_simple_geom = "catchments_coordinate_index" ;
	int64 catchments_COMID(catchments_geom) ;
		catchments_COMID:cf_simple_geom = "catchments_coordinate_index" ;
	int64 flowlines_coordinate_index(flowlines_node_index) ;
		flowlines_coordinate_index:cf_role = "simple_geom" ;
		flowlines_coordinate_index:geom_type = "linestring" ;
		flowlines_coordinate_index:stop_encoding = "cra" ;
		flowlines_coordinate_index:coordinates = "flowlines_x flowlines_y flowlines_z" ;
		flowlines_coordinate_index:multipart_break_value = -1LL ;
	int64 flowlines_geom_stop(flowlines_geom) ;
		flowlines_geom_stop:continuous_ragged_dimension = "flowlines_node_index" ;
	double flowlines_x(flowlines_node) ;
	double flowlines_y(flowlines_node) ;
	double flowlines_z(flowlines_node) ;
	int64 flowlines_COMID(flowlines_geom) ;
		flowlines_COMID:cf_simple_geom = "flowlines_coordinate_index" ;
	char flowlines_GNIS_NAME(flowlines_geom) ;
		flowlines_GNIS_NAME:cf_simple_geom = "flowlines_coordinate_index" ;
	int64 upstream_coordinate_index(upstream_node_index) ;
		upstream_coordinate_index:cf_role = "simple_geom" ;
		upstream_coordinate_index:geom_type = "point" ;
		upstream_coordinate_index:stop_encoding = "cra" ;
		upstream_coordinate_index:coordinates = "upstream_x upstream_y upstream_z" ;
		upstream_coordinate_index:multipart_break_value = -1LL ;
	int64 upstream_geom_stop(upstream_geom) ;
		upstream_geom_stop:continuous_ragged_dimension = "upstream_node_index" ;
	double upstream_x(upstream_node) ;
	double upstream_y(upstream_node) ;
	double upstream_z(upstream_node) ;
	int64 upstream_COMID(upstream_geom) ;
		upstream_COMID:cf_simple_geom = "upstream_coordinate_index" ;
	char upstream_GNIS_NAME(upstream_geom) ;
		upstream_GNIS_NAME:cf_simple_geom = "upstream_coordinate_index" ;

// global attributes:
		:_NCProperties = "version=1|netcdflibversion=4.4.1|hdf5libversion=1.8.17" ;
}

What's the story on this ticket? I get the sense that it's done... ?


Add send response API that accepts io blob list

Codecov Report

Merging #224 (23579f9) into master (6bf081f) will increase coverage by 0.33%.
The diff coverage is 100.00%.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff             @@
##           master     #224      +/-   ##
==========================================
+ Coverage   63.48%   63.82%   +0.33%
==========================================
  Files          72       72
  Lines        4401     4403       +2
  Branches      557      557
==========================================
+ Hits         2794     2810      +16
+ Misses       1357     1344      -13
+ Partials      250      249       -1

Components
Coverage Δ

AuthManager
77.77% <ø> (ø)

Cache
28.43% <ø> (+2.44%)
:arrow_up:

FDS
70.92% <ø> (-0.03%)
:arrow_down:

FileWatcher
56.25% <ø> (ø)

Flip
65.34% <ø> (ø)

gRPC
74.89% <100.00%> (+0.36%)
:arrow_up:

Logging
30.18% <ø> (ø)

Metrics
80.20% <ø> (ø)

Options
100.00% <ø> (ø)

Setting
56.79% <ø> (ø)

StatusObject
73.83% <ø> (ø)

Utility
82.71% <ø> (ø)

Version
95.83% <ø> (ø)


Update TF, add ResNext Stage1 example

LGTM - does not appear to break anything I've been working on


Fix Cowswap tests

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
3 unchanged lines in 1 file lost coverage.
Overall coverage remained the same at 90.588%

Files with Coverage Reduction
New Missed Lines
%

gnosis/util/util.py
3
66.67%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
3773

Relevant Lines:
4165

💛  - Coveralls


Ambiguous Reference

In Bond 4.3.1 (I would use the Bond 5 beta but I can't get it to compile from Carthage) I use the code provided in the readme to bind an ObservableArray of Strings to the UICollectionView as so:
viewModel?.voters.bindTo(voters) { array, indexPath, voters in
    let cell = voters.dequeueReusableCell(withReuseIdentifier: "Cell", for: indexPath) as! Cell
    let name = array[indexPath.item]

   name.bindTo(cell.nameLabel)
        .disposeIn(cell.onReuseBag)

    return cell
}

where voters in the ViewModel is an ObservableArray and voters is the UICollectionView defined in the ViewController.
On the first line, XCode complains and says: Ambiguous reference to member 'bindTo(_:proxyDataSource:createCell). I'm unsure why.  However, code completion will show like this: .
I'm open to either figuring out how to compile Bond 5 beta and using the code in that readme or fixing this code.
I compile Bond 4.3.1 this way: carthage update Bond --platform ios --no-use-binaries.

Fixed by doing this:
let voters = viewModel?.voterNames
let dataSource = ObservableArray([voters!])


Paralell UPERF sessions

In scale test environment, we would like to be able to launch multiple UPERF sessions in parallel to speed up scale tests.
For example, with carefully partitioning, we can setup multiple worker node sets. Each set can run its own tests.
One of the implementation code points that prevents parallel sessions today is the redis variable for the operator and client workload pod communication. This var has fixed name 'redis-start'.  If this name can be enhanced to something like 'redis-{{'session-number}}'-start.  The operator and the client pods of the same UPERF session can run w/o interfering with other sessions.  This enhancement should be followed AFTER the uperf scale PR.

we could use the {{uuid}}-start versus having yet another session id.


Always call init method on main thread

This would fix #11.
If calling init (or sharedInstance) method on other threads, the arView will not be initialized correctly and show nothing on the screen.

For a RCTViewManager class, the view method will always run on main thread but other customized methods will run on child threads. That's why calling [ARKit sharedInstance] in a customized method before view will raise the problem. My guess is the SCNView or ARSCNView should always be initialized on main thread.

@qftgtr ok, so i think you can merge that


Push notification Feature to individual user about there birthday

Bday wish for individual users

This feature should be society configurable. Society 1 wants to wish birthday but society 2 doesn't want this feature.


notmuch-bower: 2017-09-27 -> 0.8.1

0.8.1 was released Mar 31, 2018, so lets move this up to stable.

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Fits CONTRIBUTING.md.

No attempt on x86_64-darwin (full log)
The following builds were skipped because they don't evaluate on x86_64-darwin: notmuch-bower
Partial log (click to expand)

a) For `nixos-rebuild` you can set
  { nixpkgs.config.allowUnsupportedSystem = true; }
in configuration.nix to override this.

b) For `nix-env`, `nix-build`, `nix-shell` or any other Nix command you can add
  { allowUnsupportedSystem = true; }
to ~/.config/nixpkgs/config.nix.

No attempt on aarch64-linux (full log)
The following builds were skipped because they don't evaluate on aarch64-linux: notmuch-bower
Partial log (click to expand)

a) For `nixos-rebuild` you can set
  { nixpkgs.config.allowUnfree = true; }
in configuration.nix to override this.

b) For `nix-env`, `nix-build`, `nix-shell` or any other Nix command you can add
  { allowUnfree = true; }
to ~/.config/nixpkgs/config.nix.

Success on x86_64-linux (full log)
Attempted: notmuch-bower
Partial log (click to expand)
glibPreFixupPhase
post-installation fixup
shrinking RPATHs of ELF executables and libraries in /nix/store/vx1sg9x9k3b34bgxkgj2ybsc6sgi6k79-notmuch-bower-0.8.1
shrinking /nix/store/vx1sg9x9k3b34bgxkgj2ybsc6sgi6k79-notmuch-bower-0.8.1/bin/bower
gzipping man pages under /nix/store/vx1sg9x9k3b34bgxkgj2ybsc6sgi6k79-notmuch-bower-0.8.1/share/man/
strip is /nix/store/h0lbngpv6ln56hjj59i6l77vxq25flbz-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/vx1sg9x9k3b34bgxkgj2ybsc6sgi6k79-notmuch-bower-0.8.1/bin
patching script interpreter paths in /nix/store/vx1sg9x9k3b34bgxkgj2ybsc6sgi6k79-notmuch-bower-0.8.1
checking for references to /build in /nix/store/vx1sg9x9k3b34bgxkgj2ybsc6sgi6k79-notmuch-bower-0.8.1...
/nix/store/vx1sg9x9k3b34bgxkgj2ybsc6sgi6k79-notmuch-bower-0.8.1


Random projections

introduces Gaussianity tests on rng (based on Anderson-Darling)
introduces random projection using a Gaussian matrix, w/scikit-style
auto-mode that only requires max relative error in distances to
compute the dimension of the projection (based on Johnson-Lindenstrauss).

See unit tests, esp. TestRandomProjection/testEmbedding.
From the discard pile of high-performance ANN experiments.
Edit: Unit Tests forked in https://github.com/deeplearning4j/nd4j/pull/2036

Thanks @gagatust !

@turambar See also https://github.com/deeplearning4j/deeplearning4j/pull/3878 before you go too deep in the ANN rabbit hole

@turambar Any news from your experiments ?

@turambar Updates ? A field test wouldn't go amiss to press buttons on this PR.