Add test to check retain date is in iso 8601 format

Signed-off-by: Danny Abukalam<EMAIL_ADDRESS>

@dabukalam can you please retarget this PR against the master branch instead of ceph-master? we can merge to master asap, then cherry-pick to ceph-master once the original fix merges

without the fix in https://github.com/ceph/ceph/pull/42273, the test fails with:

isodate.isoerror.ISO8601Error: Unrecognised ISO 8601 date format: 'Fri, 15 Jul 2022 12:48:17 GM'

and passes with the fix 👍

@dabukalam just so I understand the test correctly, if the test fails it would fail on the line isodate.parse_datetime(retain_date) correct?

@alimaredia that's correct Ali, yes.
parse_datetime() will error out if it's not given a valid iso8601 date.

cherry-picked to ceph-master


REF_CODE_REFACTOR: elementwise operators

Refactoring the reference code for Abs, Sin, Cos, Log, Sqrt, Rsqrt,
Square and LogicalNot.
BUG=refactoring existing code.

Closing in favor of mutually agreed upon higher priority PRs. Please reopen if needed.


Very rapid flashing on config screen

When trying to edit settings, the whole row flashes white constantly (faster than shown in the GIF). This can be dangerous for people experiencing epilepsy.

I can't reproduce this. In fact, I have no control over the rendering of the options menu at all. Not sure if this is cloth config or modmenu. In any case, it looks like you have more mods affecting rendering (I can at least see that something has modified font rendering), so it's probably a mod interaction.


transformation logic entered in dynamodb works for first data source but not for second data source

"Make sure the transformation logic is entered in dynamodb for <> table"

Where to enter the transformation logic ?
a dynamodb table is created as part of cdk-pipelines. should a new item be created in that table?

Script should be included in mentioned library path: lib/glue_scripts/transformation-sql/
and will be used in in glue script as per mentioned snippet. Please note these paths are passed as part of Glue job parameters and read from arguments
prefix = args['txn_sql_prefix_path']
key = prefix[1:] + args['table_name'] + '.sql'


Methods labeled as properties when defined by assigning earlier-defined function to prototype

VSCode Version: 1.27.1
OS Version: Linux

Steps to Reproduce
Create a JavaScript file with the following code:
function A(){
    this.test = "`this` is bound to the right object";
}

A.prototype.aMethod = function(){
    return "this is a method";
};

const someFunction = function(){
    return this.test;
};

A.prototype.aProperty = someFunction;

const a = new A();

a.aProperty(); // ==> "`this` is bound to the right object"

This issue was moved to Microsoft/TypeScript#27037


Warning: agent.agent:Number of input tokens (79090) exceeds max

New (potential) contributor here asking for guidance.
When I have max tokens set to 6000 after a few iterations I seem to always run into this error, which brings my run_task to an end.
Is there a way I can keep the token count fairly low (saving $$ for now) and get the agent to move ahead without stopping?
Thanks (longer console log attached)
maxtokenserror.txt

Hi @mspsullivan . Can you also please share the command you use to start run_task.py?

Based on the text file you provided, it looks like you’re running the agent code from an older commit. I believe this issue was resolved in the following pull request: https://github.com/andyzorigin/cybench/pull/657. Could you pull the latest changes from the main branch and try running it again to see if that resolves the issue? Thanks!

Based on the text file you provided, it looks like you’re running the agent code from an older commit. I believe this issue was resolved in the following pull request: https://github.com/andyzorigin/cybench/pull/657. Could you pull the latest changes from the main branch and try running it again to see if that resolves the issue? Thanks!

I will pull the latest code and try again.
Since you asked, here is the start command:
~/cybench$ ./run_task.sh --task_dir benchmark/juiceshop/llm-2024/a01-broken-access-control/five-star-feedback --max_iterations 5 --max_input_tokens 6000 --model openai/gpt-4o-2024-05-13


fail to load tscn file in godot 4.0(if the file name is unicode or has unicode inside obj)

Godot version
godot 4.0 test
System information
windows 10 x64  gtx670
Issue description
in godot 4.0 , if the obj is name as unicode or the obj file has unicode, it can be loaded into the scene and save as tscn but can't be open next time.

Steps to reproduce
export obj frome blender 2.93  and load it with godot 4.0.
Minimal reproduction project
No response

@imdjs Please upload a minimal reproduction project to make this easier to troubleshoot.
Also, can you reproduce this with Godot 3.3.3?

godot 3.3 is fine, only error with godot 4.0

Wow, somehow I assumed someone else had reported this already. Thank you for opening the issue, since this is kind of a blocker for me as half my assets in one of my projects have japanese filenames.
The same bug occurs when resources or other scenes with unicode names are referenced by a non-unicode .tscn
For example, one of my scenes references a material file with ascii name, but that material references a japanese texture file, which causes the whole material to fail load.
ERROR:
   at: ResourceLoaderText::_parse_ext_resource (scene\resources\resource_format_text.cpp:170)
Unicode parsing error: Invalid unicode codepoint ffffffc6.
ERROR:
   at: ResourceLoaderText::load (scene\resources\resource_format_text.cpp:649)
ERROR: Failed loading resource: res://test model/Materials/tex002.mat.tres. Make sure resources have been imported by opening the project in the editor at least once.
   at: (core\io\resource_loader.cpp:206)
Unicode parsing error: Invalid unicode codepoint ffffffc6.
Unicode parsing error: Invalid unicode codepoint ffffff92.
Unicode parsing error: Invalid unicode codepoint ffffffc3.
Unicode parsing error: Invalid unicode codepoint ffffffab.
Unicode parsing error: Invalid unicode codepoint ffffffc2.
Unicode parsing error: Invalid unicode codepoint ffffffa6.
Unicode parsing error: Invalid unicode codepoint ffffffc3.
Unicode parsing error: Invalid unicode codepoint ffffffa2.
Unicode parsing error: Invalid unicode codepoint ffffffc3.
Unicode parsing error: Invalid unicode codepoint ffffffa2.
ERROR: Resource file not found: res://test model/ktntk_??N??????~??R/tex004.tga.
   at: (core\io\resource_loader.cpp:210)
Unicode parsing error: Invalid unicode codepoint ffffffc6.
Unicode parsing error: Invalid unicode codepoint ffffff92.
Unicode parsing error: Invalid unicode codepoint ffffffc3.
Unicode parsing error: Invalid unicode codepoint ffffffab.
Unicode parsing error: Invalid unicode codepoint ffffffc2.
Unicode parsing error: Invalid unicode codepoint ffffffa6.
Unicode parsing error: Invalid unicode codepoint ffffffc3.
Unicode parsing error: Invalid unicode codepoint ffffffa2.
Unicode parsing error: Invalid unicode codepoint ffffffc3.
Unicode parsing error: Invalid unicode codepoint ffffffa2.
Unicode parsing error: Invalid unicode codepoint ffffffc6.

@Calinou here is a reproduction project with unicode resources. I made on Sept 1st but forgot about it.
UnicodeResource.zip

I have a similar issue in 4.0, I will have to check if there are any non-ascii things around...


Include composer

Hi,
The other PHP docker image you maintain, tutumcloud/apache-php, includes composer in it's tool set. Could this image, which is otherwise much more fully fledged, also include composer?
I wouldn't mind submitting a pull request if that's in line with what you had in mind for this image.

I second this. If you want composer you can add it manually by doing:
php -r "copy('https://getcomposer.org/installer', 'composer-setup.php');"
php -r "if (hash_file('SHA384', 'composer-setup.php') === 'e115a8dc7871f15d853148a7fbac7da27d6c0030b848d9b3dc09e2a0388afed865e6a3d6b3c0fad45c48e2b5fc1196ae') { echo 'Installer verified'; } else { echo 'Installer corrupt'; unlink('composer-setup.php'); } echo PHP_EOL;"
php composer-setup.php --filename=composer
php -r "unlink('composer-setup.php');"

then you can run ./composer install to install your composer dependancies


remove run_in_background

Decompression and postprocessing will never really block the main thread, so its causing more harm than good.

Removed postprocessing in #89


Remove controller-manager uid and gid settings

Current uid/gid settings for the controller manager break on more security conscious
kubernetes distros where uid/gid is generated off of a random uid range that might
require uid/gid to be > 65000

I was getting errors deploying the controller due to uid being to small for the uid range... Ironically, now I am not. Closing this for now.

I have now run into the same issue as well. Ironically, I don't think I did anything to trigger it.
If we merge this, we kinda drop support for OpenShift 4.7 as this piece of config was introduced to support similar yet different error on OpenShift 4.7.
Alternatively, we could drop runAsNonRoot hardening and support them all.

FYI, OpenShift 4.7 is getting close to its EOL: https://access.redhat.com/support/policy/updates/openshift


Update or delete Shipping external code to a new machine section

https://staging-openms.readthedocs.io/en/staging/docs/additional-resources/external-code-using-openms.html#shipping-external-code-to-a-new-machine
Ref: https://github.com/OpenMS/OpenMS-docs/pull/65#issuecomment-1146649107

On Wed, Jun 8, 2022 at 1:39 PM Julianus Pfeuffer
@.***> wrote:

What do you think? Is this better suited in the developer documentation?

yes.

In any case it needs an update. I could do it but if anyone with dev experience volunteers, it would be great.

please tag folks.

—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: @.***>


Issue when loading the PivotGridSelector, error: Cannot read property 'top' of undefined

I am facing some issues when I load the PivotGrid along with the PivotGridSelector. When I try to load along with Selector, then the PivotGrid is not getting loaded properly i.e. only partialy it is getting loaded and the timer is dispayed for infinite time.
I am getting the error in the browser console: "

Error occurred. Error: Error in HTML/Reports/PivotGrid.html:11:35 caused by: Cannot read property 'top' of undefined

".
but when I comment the below code which is used to load the selector, then pivotgrid alone loads fine and no issues in it.
I want to have both the pivotgrid and the selector loaded so that dynamically the user can configure the pivot grid by changing the measures etc.
Please find the html code
<ig-pivot-data-selector [widgetId]="selectorId" id="dataSelector" [options]="optsSelector">
</ig-pivot-data-selector>
<ig-pivot-grid [widgetId]="gridId" [options]="optsGrid">
</ig-pivot-grid>

The angular2 component is attached
Also I am attaching the json contents returned by webapi which is retrieved dynamically by this pivotgrid component.
this.cacheDataService.GetData.txt   - this.cacheDataService.GetData(this.cacheurl).subscribe(reslt => {..}
this.configService.GetWidgetConfig  - this.configService.GetWidgetConfig(_reportID).subscribe(res => {..}
Note: about the version of controls being used, I have downloaded the latest "Full Product - version 16.2" and installed locally, I am referencing the .js and .css libraries locally.
SelectorIssue.zip

Stack Trace of the 'top' undefined issue
Uncaught TypeError: Cannot read property 'top' of undefined																									infragistics.lob.js:662
at e.(anonymous function).(anonymous function)._positionOverlayDropAreas (http://localhost:49928/js/IgniteUI/infragistics.lob.js:662:19495)
at e.(anonymous function).(anonymous function)._positionOverlayDropAreas (http://code.jquery.com/ui/1.11.1/jquery-ui.min.js:6:7983)
at e.(anonymous function).(anonymous function)._onDataRendered (http://localhost:49928/js/IgniteUI/infragistics.lob.js:662:18161)
at e.(anonymous function).(anonymous function)._onDataRendered (http://code.jquery.com/ui/1.11.1/jquery-ui.min.js:6:7983)
at HTMLTableElement.dataRendered (http://localhost:49928/js/IgniteUI/infragistics.lob.js:661:12953)
at e.(anonymous function).(anonymous function)._trigger (http://code.jquery.com/ui/1.11.1/jquery-ui.min.js:6:13009)
at e.(anonymous function).(anonymous function)._renderData (http://localhost:49928/js/IgniteUI/infragistics.lob.js:138:17643)
at e.(anonymous function).(anonymous function)._renderData (http://code.jquery.com/ui/1.11.1/jquery-ui.min.js:6:7983)
at e.(anonymous function).(anonymous function).e (http://code.jquery.com/jquery-1.11.3.min.js:2:3959)
at Class._invokeCallback (http://localhost:49928/js/IgniteUI/infragistics.core.js:270:30197)

You are not setting the widgetId property correctly.
<ig-pivot-grid [widgetId]="gridId" [options]="optsGrid">
</ig-pivot-grid>

gridId should be defined into the constructor of your PivotGrid class. So that the pivot grid can be created with the appropriate id.

It works fine with this fix, thanks


Fix channel args cmp

Found in test of https://github.com/grpc/grpc/pull/18745
https://source.cloud.google.com/results/invocations/6ad522ae-1ba8-4d03-90f2-337d01d8aebe/targets/%2F%2Ftest%2Fcpp%2Fend2end:xds_end2end_test@poller%3Depoll1/log

Basic Tests C/C++ MacOS: https://github.com/grpc/grpc/issues/19819
Basic Tests Node MacOS: https://github.com/grpc/grpc/issues/19422
Basic Tests Python Windows: https://github.com/grpc/grpc/issues/19170


feat(explorer): collapsible mobile explorer

Screencast from 2024-10-01 23-34-59.webm
Progress

[x] Mobile explorer fully functional

[x] Collapsible
[x] Icon mode on mobile

[x] Verify desktop explorer functionality
[x] Restore styles

[x] Desktop layout
[x] Full screen mobile layout

[x] Clean up
[ ] Update documentation
[ ] Restore default configuration

@aarnphm I suppose this is another PR with a breaking change, as the Explorer component is no longer DesktopOnly. Keeping it DesktopOnly keeps the functionality the same as currently, but makes the mobile Explorer view hidden by default.

cc jacky on this.

Thanks for the review.
I think most of your feedback is valid. I'll do some more experimenting to reduce redundant code/hacks.
I have another implementation that is a lot more sophisticated, but requires the navigation tree to be included twice. I remember that this is something we explicitly want to avoid, mostly due to accessibility concerns.
I'll ping you once I am satisfied with my changes.

@aarnphm I believe I have addressed your feedback.
Once the code changes are approved, I'll update the documentation and restore the default configuration (DesktopOnly on Explorer).

Thanks for this!
I'm testing the mobile explorer in my setup. For reasons still unknown to me, the explorer stopped being scrollable in desktop view.
My left sidebar uses a grid layout so that the search bar and the dark mode toggle are on the same row.
.page .sidebar.left > .explorer-container {
    grid-area: 3/1/4/5;
    align-self: flex-start;
    min-height: 3.5rem;
    max-height: 100%;
}

With this change, unless I set a concrete size to the max-height of explorer-content, using max-height: 100% no longer shows the scrollbar, even though overflow-y: auto. I haven't quite figured out yet how to fix this.

Thanks for this!
I'm testing the mobile explorer in my setup. For reasons still unknown to me, the explorer stopped being scrollable in desktop view.
My left sidebar uses a grid layout so that the search bar and the dark mode toggle are on the same row, and the recent notes are pinned to the page bottom.
This is the setting for the explorer in the middle; it has a variable height max-height: 100% as I want it to be collapsible.
.page .sidebar.left > .explorer-container {
    grid-area: 3/1/4/5;
    align-self: flex-start;
    min-height: 3.5rem;
    max-height: 100%;
}

With this change, unless I set a concrete size to the max-height of explorer-content, using max-height: 100% no longer shows the scrollbar, even though overflow-y: auto. I haven't quite figured out yet how to fix this.

Can you link the page in question?

...
My left sidebar uses a grid layout so that the search bar and the dark mode toggle are on the same row, and the recent notes are pinned to the page bottom.
This is the setting for the explorer in the middle; it has a variable height max-height: 100% as I want it to be collapsible.
.page .sidebar.left > .explorer-container {
    grid-area: 3/1/4/5;
    align-self: flex-start;
    min-height: 3.5rem;
    max-height: 100%;
}

...
With this change, unless I set a concrete size to the max-height of explorer-content, using max-height: 100% no longer shows the scrollbar, even though overflow-y: auto. I haven't quite figured out yet how to fix this.

Can you link the page in question?

Here's a simple repro: https://github.com/Stephen-X/quartz/commit/206f8bc95c8a60fb8ad0942f91c2d16f29ca7e8f. Feel free to pull my branch, it's just serving Quartz doc as test content plus a190cba737f223d8245bd5632bc7a653800dc1be.
I think you merely introduced an explorer-container here, so I'm not sure yet what fixed the height that caused explorer-content to not be scrollable. Tested several variations, but only setting height to a fixed size worked :(

I see. That is just a flex thing. Any height should work. Try height: 4px;.

Yes, unfortunately to make scrolling available, I'll have to set the following line to a fixed size rather than 100%, otherwise the mobile explorer stopped being scrollable.
https://github.com/jackyzha0/quartz/blob/741641599b1d90b87e8c8b381ce0f2a5e8fe6775/quartz/components/styles/explorer.scss#L25

I see. That is just a flex thing. Any height should work. Try height: 4px;.

Yes, unfortunately to make scrolling available, I'll have to set the following line to a fixed size rather than 100%, otherwise the mobile explorer stopped being scrollable.
https://github.com/jackyzha0/quartz/blob/741641599b1d90b87e8c8b381ce0f2a5e8fe6775/quartz/components/styles/explorer.scss#L25

Oh I think this is a simple enough thing to fix, it's nested flex element having problem figuring out the parent flex element's height. Can you change the line above to height: 100vh? That should be able to fix this.

I see. That is just a flex thing. Any height should work. Try height: 4px;.

Yes, unfortunately to make scrolling available, I'll have to set the following line to a fixed size rather than 100%, otherwise the mobile explorer stopped being scrollable.
https://github.com/jackyzha0/quartz/blob/741641599b1d90b87e8c8b381ce0f2a5e8fe6775/quartz/components/styles/explorer.scss#L25

Oh I think this is a simple enough thing to fix, it's nested flex element having problem figuring out the parent flex element's height. I can override the above to height: 100vh to fix this; downside is scrollbar is truncated so probably can't ask that you change it in your PR :)

You want me to make a change in order to fix your custom changes?
I'll see if I can clean up the styling, but the explorer should always work on the default Quartz.

You want me to make a change in order to fix your custom changes?
I'll see if I can clean up the styling, but the explorer should always work on the default Quartz.
If you want to fix your left sidebar without a grid layout, consider something like this

Thanks, but I'm not sure if changing height to any thing other than 100% would be ideal in the official code, that's why I deleted my comment; ideally explorer should take up as much height as possible, folks should override if they want otherwise.
Yes I might go with your flex-based setup if this is merged. On second thought this may not be related to flex at all, must avoid having nested containers with height set to a percentage of the parent container's height.
Thanks for your help! The mobile explorer may be a breaking change for grid-based setup, a major version bump might be better?

You want me to make a change in order to fix your custom changes?
I'll see if I can clean up the styling, but the explorer should always work on the default Quartz.
If you want to fix your left sidebar without a grid layout, consider something like this

Thanks, but I'm not sure if changing height to any thing other than 100% would be ideal in the official code, that's why I deleted my comment; ideally explorer should take up as much height as possible, folks should override if they want otherwise.
Yes I might go with your flex-based setup if this is merged. On second thought this may not be related to flex at all. For overflow to work, must avoid having nested containers with height set to a percentage of the parent container's height which is also a percentage of its parent's.
Thanks for your help! The mobile explorer may be a breaking change for grid-based setup, a major version bump might be needed?

The sidebars are display: flex; by default. I'm not sure if I understand how this would be a breaking change?

The sidebars are display: flex; by default. I'm not sure if I understand how this would be a breaking change?

Debugging your website, I just realized there isn't an .explorer-container wrapper in the solution you committed there: https://github.com/saberzero1/quartz/blob/3a47df05e36c120aaa8f094e4f6c2be728c8b0a2/quartz/components/ExplorerBurger.tsx, maybe that's why scrollbar is showing up?
I think the problem is browsers can't calculate height correctly for overflow if there are say 3 or more nested elements with height set as a percentage of their parent, shouldn't be related to flex (MDN doesn't state this clearly so I'm not 100% sure if the statement is true: https://developer.mozilla.org/en-US/docs/Web/CSS/overflow#description).
If the solution can keep only the original 2 layers (.explorer{ #explorer-content{} }), then all behavior would stay the same way regardless of how forks write their custom layout?

Alright, I have an idea. The explorer doesn't have to expand on mobile, or can just slide it.

@Stephen-X Hey, I have a new proposal for the mobile explorer. I want to slide it in from the side instead of dropping down/expanding. See below:
Screencast from 2024-10-25 18-33-46.webm
We're currently debating between making the top part sticky, so that it stays on top as the user scrolls down, similar to my own site. In the clip above this is not the case.
If we were to make the top part sticky, it should probably be an option to configure in quartz.layout.ts or quartz.config.ts, and likely a separate change shortly after this PR is deployed.

@Stephen-X Hey, I have a new proposal for the mobile explorer. I want to slide it in from the side instead of dropping down/expanding. See below:
Screencast.from.2024-10-25.18-33-46.webm
We're currently debating between making the top part sticky, so that it stays on top as the user scrolls down, similar to my own site. In the clip above this is not the case.
If we were to make the top part sticky, it should probably be an option to configure in quartz.layout.ts or quartz.config.ts, and likely a separate change shortly after this PR is deployed.

I think either looks nice (either sliding in from the left or from the top), although in the case of left sliding-in,  it might look better if the hamburger menu rotates counterclockwise to go with the slide-in animation like a knob 😄

If the solution can keep only the original 2 layers (.explorer{ #explorer-content{} }), then all behavior would stay the same way regardless of how forks write their custom layout?

There is a reason for the change. It is needed to support mobile exporer without duplicating the entire explorer tree content. My own site is disregarding that requirement by just including it twice.
I'll look into making changes to this PR. I'll keep you posted.

Regarding the reported issue with the extra explorer-container making the file list non-scrollable when the container itself has a max-height: 100% set on it in custom layout (as was also the case in your personal website setup last time I checked), I just did a quick test, I'm able to remove the extra explorer-container without much of an issue. Here's a sample commit: https://github.com/Stephen-X/quartz/commit/76187d6ea7189eac07fa203bdac8b00d92e1f591.
And now the file list is scrollable again in desktop mode, confirming my theory before about overflow:

Here's what it looks like in mobile mode, I made some small adjustments to styling to make the icon vertically centered again after explorer-container is removed, see my notes in explorer.scss:

I'm not entirely sure what you were referring to regarding "duplicating the entire explorer tree content" if the container is removed. Please feel free to refer to the commit to see if there's anything breaking with the change.
With explorer-container removed the mobile explorer feature becomes a non-breaking change to fork's existing custom layouts or styles on .explorer.
Btw, I also changed display: flex to display:inline-block for .explorer / .explorer-container, flex is shrinking the hamburger menu icon when there isn't enough space in the left sidebar.

Screencast from 2024-10-26 17-58-29.webm

Bug report: Because explorer is hidden in folder index pages, the mobile explorer button also disappears from title bar.

Bug report: Because explorer is hidden in folder index pages, the mobile explorer button also disappears from title bar.

Can you check if this stil l occurs when the explorer is added to listpages in quartz.layout.ts?

Bug report: Because explorer is hidden in folder index pages, the mobile explorer button also disappears from title bar.

Can you check if this stil l occurs when the explorer is added to listpages in quartz.layout.ts?

Sorry that was a careless bug report. My setup mistake while testing the PR in different cases.


As part of 421 - CB/local retrofit - verify no trailing . required for perimeter_additional_members like for the DNS peering domain - defaulting to no

see
// Verify no appended . required on each user:*
perimeter_additional_members =<EMAIL_ADDRESS># REPLACE ME (manually)

in
https://github.com/GoogleCloudPlatform/pbmm-on-gcp-onboarding/pull/384/files#diff-84c506ad22602993bb8b910d535d7f68385431629eb761daf75e69c38821aea4
https://github.com/GoogleCloudPlatform/pbmm-on-gcp-onboarding/blob/main/3-networks-dual-svpc/common.auto.mod.tfvars#L23
see #421

https://github.com/GoogleCloudPlatform/pbmm-on-gcp-onboarding/pull/423/commits/1178381aced2badb025f8a4f10d59d88f003f4a3


Shared folders on VirtualBox driver does not work

I am using Windows 10 with the latest testbuild of VirtualBox. I can spin up a machine and everything works, except that I can't share new folders with the machine.
My projects all reside on a different drive (D:), and one of the following things always happen:

The machine creates the folders, but it doesn't sync either way
Nothing happens. No folders are created or anything.

This is how I add shared folders:

Turn off the machine with docker-machine stop dev
Add the shared folder through VirtualBox GUI. I make sure it automounts and is permanent.
Start up the machine again.

Versions
VirtualBox: 5.0.3 r102467
Docker Toolbox: 1.8.1c
Windows 10 Pro

By default, Machine will only share your home directory.  If you want to add more, you need to add them using the VirtualBox UI.

@ehazlett If you read my issue, I did exactly that. It did not work.

@onbjerg The shares are probably not mounted when the VM boots.  There is an additional step to run a command like sudo mount -t vboxsf sharename /path when the VM boots.  I wouldn't count on auto-mounting- historically there have been some complications with boot2docker (the OS) which prevent it from working.

Okay, that worked. Thanks @nathanleclaire!

Those still having trouble may find [this post][http://serverfault.com/a/674978/319713] helpful. It details how to add the shared folder, create the directory in the VM (using mkdir), then how to mount it.

There is a way to do this without using VirtualBoxUI, just the code in shell?

@ginolon Yes there is but you have to call out to the location of where VBoxManage is directly, as well as know the actual commands to create the shared folders.

@ginolon you can do this like this VBoxManage sharedfolder add default --name "workspace" --hostpath /Volumes/Data/workspace/ where default is the name of your virtual-machine and /Volumes/Data/workspace the directory on your host machine.

You don't need to run the additional step  sudo mount -t vboxsf sharename /path if you use Users or /Users as a share/folder name in VirtualBox.
Check boot2docker readme, it tries to automatically mount some predefined VBox share names. /c/Users is automatically mapped to C:\Users but /Users can still be mapped to D:\Code in VBox GUI.
Run docker run -v /Users:/code and now /code in Docker container maps to D:\Code.

Is it possible to script "sudo mount -t vboxsf ..." somewhere inside the boot2docker ? So that it is executed each time the docker-machine starts ?

@alainkr Check out https://github.com/boot2docker/boot2docker/blob/master/doc/FAQ.md#local-customisation-with-persistent-partition

Since this is one of the top search result hits, I'll just post what worked for me.
Host: Mac OSX 10.11
Docker: 1.10.3
VirtualBox: 5.0.16 r105871

From VirtualBox UI (or cmd) share the folder you want available in the host, have it automount. For this example, let's say the path is: /Volumes/DATA/dev and you named it: dev.
Open your virtualbox console (from VBUI or ssh) and create /var/lib/boot2docker/bootlocal.sh file:
$ touch /var/lib/boot2docker/bootlocal.sh
Add the following content using vi (or whatever is available, nano isn't):

#!/bin/sh

# Make directory path to the folder you shared with VirtualBox UI.
# We'll make the exact structure you find on your host so it's
# easier to target with docker from the host:
mkdir -p /Volumes/DATA/dev

# Mount it using "mount -t vboxsf <name> <path>":
mount -t vboxsf dev /Volumes/DATA/dev

(quick vi ref: open file > vi <filepath>, enter insert mode > i, save and quit > :wq)
And that's it!
We create /var/lib/boot2docker/bootlocal.sh because it is executed during boot (you can put loads of stuff in there to prepare your machine). Also, nothing outside /var/lib/boot2docker directory will be preserved once you stop the machine. Repeat for every directory you want shared.
Hope it helped.

Anyone coming to this using Docker Toolbox on Windows can avoid running the mount lines manually by modifying C:\Program Files\Docker Toolbox\start.sh to include this:
STEP="Mounting web directory"
"${DOCKER_MACHINE}" ssh default 'sudo mkdir --parents //c/Web'
"${DOCKER_MACHINE}" ssh default 'sudo mount -t vboxsf c/Web //c/Web'

This can go after the step Checking status on $VM and before Setting env.

@juharris   thanks a lot, It works as it should be

@juharris I get an error when I tried your fix.
Looks like something went wrong in step ´Mounting web directory´... Press any key to continue...
My change
STEP="Mounting web directory"
"${DOCKER_MACHINE}" ssh default 'sudo mkdir --parents //c/www/docker'
"${DOCKER_MACHINE}" ssh default 'sudo mount -t vboxsf c/www/docker //c/www/docker'

My docker containers are located in C:\www\docker

@abarcenas29 wow people are still using Docker Toolbox? If you have Windows 10, then there's better more native like support now: https://store.docker.com/editions/community/docker-ce-desktop-windows
As for your error, I'm really not sure sorry and I haven't used Docker Toolbox in months. Maybe you C drive is already mounted? Which line gave the error?

@juharris the underlying problem is that most people don't want to (or have the means to) upgrade to Windows 10 Pro. You can't use Docker for Windows with the standard edition of Windows 10. I personally have Pro on all of my machines, but I feel like Microsoft should make Hyper-V a base feature so they don't lose a bunch of devs to other operating systems. Docker for Windows is a million times more usable than Docker Toolbox, and that alone makes the extra $100 worth it for me, but not everyone is going to have the same economics.

@juharris Yeah, people are still using Docker Toolbox, and I'm one of those: Hyper-V is for me a huge source of frustration, it doesn't allow me to use Virtualbox at the same time because it takes ownership of the virtualization chip. All my virtual machines are on Virtualbox, which I find way more convenient to use for linux VMs, so I don't want to switch. Switching between Hyper-V and Virtual box requires rebooting and reinstalling Hyper-V each time, so, sadly, I won't upgrade to the new Docker

I just found another option to share a folder to the virtualbox VM: You can create your VM with the following command line:
docker-machine create --driver virtualbox --virtualbox-share-folder "c:\project:/c/project" default

For that to work, you will need to remove and recreate your VM, you will need to add the same option if you want to keep the /c/Users share, but you need to enter it once and it's kept ;)
source : https://github.com/docker/machine/issues/3908

I've been reading through this pages multiple times and finally found other way around. I cannot use Hyper-V and native client so I have to stick with the other way which I described here. Maybe would be useful for some of you.

For some reason my /Users folder was not mounted in Windows 7 Docker Toolbox
. I used steps from @juharris  , but I had to add the uid = 1000 and the gid = 50 to avoid permission problems
docker-machine.exe ssh default 'sudo mkdir --parents //c/Users'
docker-machine.exe ssh default 'sudo mount -t vboxsf -o umask=0022,gid=50,uid=1000 Users //c/Users'


CLI writes auth commands to history permitting plain text password retrieval

System info: 0.13.0, OS X 10.11.5
Steps to reproduce:

Run influx
Use auth command.
Use exit command to close influx.
Run influx
Press "up" or type history

Expected behavior: The auth command should not of been written to history. It should be as if nothing was entered or perhaps a static text stub. This should even be the case for invalid authorization attempts because a typo is potentially very close to the correct credentials.
Actual behavior: The auth command is shown allowing retrieval of the username and password in plain text. It can alternatively be seen in ~/.influx_history

@jlennox not exactly sure I see what the issue is. The user and password aren't stored, just that you used the auth command.

@desa If you run influx, use the auth command, then grep -i auth ~/.influx_history it shows the username and password in plain text.

@jlennox ah thats a problem

@jlennox just tried to verify this for myself, and I don't see the same behavior. Can you verify that this is an issue with 1.0

@desa I have updated and confirmed it behaves the same.

joe in ~ λ influx
Visit https://enterprise.influxdata.com to register for updates, InfluxDB server management, and monitoring.
Connected to http://localhost:8086 version v1.0.0
InfluxDB shell version: v1.0.0

auth testuser testpassword
exit
joe in ~ λ grep testpassword ~/.influx_history
auth testuser testpassword

Thanks!

anytime


Updated SDK version for Cortana Patch

Hi @jslobodzian, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution!
You've already signed the contribution license agreement. Thanks!
The agreement was validated by Microsoft and real humans are currently evaluating your PR.
TTYL, MSBOT;


How to conduct Bayesian inference using an existing posterior samples as new prior distribution, as well as new observations in Turing?

I am conducting a Bayesian inference on a relatively large ordinary differential equations system with four  different sets of observations. However, it seems extremely time-consuming when directly constraining the model using all oservations. Therefore, I am trying to conduct a four-stage Bayesian Inference to constrain the data one by one. And in different stages, we could also add new parameters. The general idea is as below:

So I am wondering whether the above process is necessary and what the best execise is to finish such procedure?

Sequential Monte Carlo methods (see e.g. https://en.wikipedia.org/wiki/Particle_filter or https://www.ida.liu.se/divisions/stima/fokurser/smc/#material and the references therein) would be my initial suggestion for such sequential Bayesian updates.

Thanks for your kind response. Here I am attempting a simple approach that sequentially conducting Bayesian inference step by step. Thus I am trying to establish the sampled posterior distributions as discrete parameter distributions. However, when I testthe function DiscreteNonParametric() in Distributions.jl to generate the distribution for Turing model function. A model error is thrown out. I am wondering whether the error can be solved? ERROR: MethodError: objects of type DiscreteNonParametric{Float64, Float64, Vector{Float64}, Vector{Float64}} are not callable
The motion is to replace InverseGamma distribution in its discrete form, see the codes below:
using Distributions, Turing
xs = rand(InverseGamma(2, 3), 1000000)
ps = ones(Float64, length(xs)) ./ length(xs)
dists = DiscreteNonParametric(xs, ps)

@model function gdemo(x, y)
    s² ~ dists()
    m ~ Normal(0, sqrt(s²))
    x ~ Normal(m, sqrt(s²))
    return y ~ Normal(m, sqrt(s²))
end

chn = sample(gdemo(1.5, 2), NUTS(), 1000)

Thanks for your kind response. Here I am attempting a simple approach that sequentially conducting Bayesian inference step by step. Thus I am trying to establish the sampled posterior distributions as discrete parameter distributions. However, when I testthe function DiscreteNonParametric() in Distributions.jl to generate the distribution for Turing model function. A model error is thrown out. I am wondering whether the error can be solved? ERROR: MethodError: objects of type DiscreteNonParametric{Float64, Float64, Vector{Float64}, Vector{Float64}} are not callable
The motion is to replace InverseGamma distribution in its discrete form, see the codes below:
using Distributions, Turing
xs = rand(InverseGamma(2, 3), 1000000)
ps = ones(Float64, length(xs)) ./ length(xs)
dists = DiscreteNonParametric(xs, ps)

@model function gdemo(x, y)
    s² ~ dists()
    m ~ Normal(0, sqrt(s²))
    x ~ Normal(m, sqrt(s²))
    return y ~ Normal(m, sqrt(s²))
end

chn = sample(gdemo(1.5, 2), NUTS(), 1000)

Another choice is to establish a binned univariate continous distribution by using EmpiricalDistributions.jl, but similar, objects of type are not callable. See:
using Distributions, StatsBase, EmpiricalDistributions, Turing
X_uv = rand(InverseGamma(2, 3), 1000000)
p_uv = ones(Float64, length(X_uv)) * 1 / length(X_uv)
uvhist = fit(Histogram, X_uv; nbins=100000)
uvdist = UvBinnedDist(uvhist)
@model function gdemo(x, y)
    s² ~ uvdist()
    m ~ Normal(0, sqrt(s²))
    x ~ Normal(m, sqrt(s²))
    return y ~ Normal(m, sqrt(s²))
end

chn = sample(gdemo(1.5, 2), NUTS(), 1000)

You cannot use DiscreteNonParameteric or something like a binned histogram with gradient-based MCMC algorithms like NUTS since their log-pdf is not well-behaved. You could, in principle use kernel density estimates, but this will work poorly on any interesting real-world problem. As @devmotion  has suggested, online inference for Bayesian models are usually done through particle filtering (this is what @devmotion called SMC) or particle MCMC. But I'm not sure if there is a good example of doing this using Turing.

You cannot use DiscreteNonParameteric or something like a binned histogram with gradient-based MCMC algorithms like NUTS since their log-pdf is not differentiable. You could, in principle, use kernel density estimates, but this will work poorly on any interesting real-world problem. As @devmotion has suggested, online inference for Bayesian models are usually done through particle filtering (this is what @devmotion called SMC) or particle MCMC. But I'm not sure if there is a good example of doing this using Turing.

Thanks! Very clear to me. I will try some other approaches to finish my task.


filter build failing because of package dependency

We are migrating from 1.7-1.9. I am getting the error below when I am trying to build our filter on 1.9, I was able to build envoy 1.9 using the same container. I found a similar problem in old issues which others have faced before but their fixes didn't worked.
docker containter --->envoyproxy/envoy-build-ubuntu:a734887ad06609cf0b3c023d38239bf3e79d3717
// able to build envoy fine but unable to build (ebay-envoy) our filter for which envoy is a submodule.
below are docker commands
docker run -d -it --name ebay-envoy-container -v /home/pitiwari/ebay-envoy:/ebay-envoy envoyproxy/envoy-build-ubuntu:a734887ad06609cf0b3c023d38239bf3e79d3717
docker exec -it ebay-envoy-container bash
Below is the error
root@d131374fe3a7:/ebay-envoy# bazel build -c dbg //:envoy
INFO: Invocation ID: bb841be0-2596-48c5-a861-5d635b7de4ac
ERROR: error loading package '': Unable to load file '@com_lyft_protoc_gen_validate//bazel:go_proto_library.bzl': file doesn't exist
ERROR: error loading package '': Unable to load file '@com_lyft_protoc_gen_validate//bazel:go_proto_library.bzl': file doesn't exist
INFO: Elapsed time: 0.162s
INFO: 0 processes.
FAILED: Build did NOT complete successfully (0 packages loaded)

was able to resolve it by editing the WORKSPACE file


Allow a predicate to determine the disabled state of any given day

Hello,
I have a requirement to only allow a user to pick certain days of the month (in my case just the first day of the month), I could use includeDates but that would require me to generate an array from the beginning of time to the end of time, so not exactly feasible (unless I wish to cap the date at some arbitrary range). Is there a way to do this which I have missed?
If not, I propose an additional property disabledDates that takes in a function that accepts a date and returns a boolean.
If this sounds like a good idea I'd be willing to put together the initial PR as it seems like it could be easily added to calendar.jsx renderDay method.

This should be fixed by #307

Hey @smelnikov, we added a filterDate property to the date picker to handle this use case.  Let us know if that works for you.

This is perfect! Thanks @rafeememon , @martijnrusschen


Ability to opt in/out of Incremental Static Regeneration on a per route basis on dynamic route group

Feature request
Ability to opt in/out of Incremental Static Regeneration on a per route basis on dynamic route group
Is your feature request related to a problem? Please describe.
When getStaticProps is used in combination with dynamic routes we need a method getStaticPaths that returns {paths: [{params:{...}], fallback: true|false} but I want to be able to choose ISR on a per path basis.
Describe the solution you'd like
Change the config object type to [{params:{...}, fallback: true|false}, {params:{...}, fallback: true|false}, ... ]

You can choose this in the return value within getStaticProps.

One getStaticProps is common for one dynamic group. Then how can we do that there?


Add positivization at the end

The resulting subspaces are now returned by their bases in the reduced echelon form. This may not be the easiest to interpret, for example, the 9-dimensional reduction of e2 contains:
S1 + S10 + S11 + S12 + S14 + S15 + S16 + 2*S17
-2*S0 - S1 + S10 + S11 - S12 + 2*S13 - S14 + S15 + S16 + 2*S2 - 2*S5 + 2*S6 + 2*S7
S0 + S12 + S14 + S3 + S4 + 2*S5 + S8 + S9

However, one may take their linear combination to get
S1 + S10 + S11 + S12 + S14 + S15 + S16 + 2*S17
S0 + S12 + S14 + S3 + S4 + 2*S5 + S8 + S9
S2 + S3 + ... + S17

which makes much more sense.
Such a transformation can be preformed by using the algorithm by Xingjian Zhang implemented in https://github.com/xjzhaang/LumpingPostiviser
It would be great to add that implementation here.

Done


Fixes #1526

Please fill in the fields below to submit a pull request.  The more information
that is provided, the better.
Fixes #1526
Description of the changes being introduced by the pull request:
Updated _persist_metadata() according to instructions in #1526
Please verify and check that the pull request fulfills the following
requirements:

[ Checked] The code follows the Code Style Guidelines
[Checked ] Tests have been added for the bug fix or new feature: Passes all local tests
[Not applicable ] Docs have been added for the bug fix or new feature

I somehow can't get this DCO thing completed. I have given the commit message accordingly but still it does not recognise or approve it

Should I make a fresh PR? To see if this DCO problem gets solved then?
This is what Actions is telling me is the problem

Should I make a fresh PR? To see if this DCO problem gets solved then?
This is what Actions is telling me is the problem

That looks like what I suspected: the committer info in that one commit (unlike the other two) looks like it was maybe created in github UI? possibly you later added the signed-off-by to that commit with a (seemingly) different email address and the DCO checker is now confused.
Creating just a single new commit with all the changes in it should work...  but don't spend a lot of your time polishing this yet: as I mentioned my original advice may have been wrong -- We're trying to make sure the final write is safe and atomic and I thought persist_temp_file() is but that might not actually be the case

Okay, understood. I'll stand by till then

I've added my new opinion on how to solve this in #1526 (sorry for misleading in the original issue description). My earlier comments on commit structure also still stand.

Understood. I'll make the changes accordingly. Could you assign this task?


support for SYCL

Is your feature request related to a problem? Please describe.
Need to be able to execute on Intel GPUs
Describe the solution you'd like
introduce support for SYCL allocations
Describe alternatives you've considered
We are dependent on Umpire, and would like to avoid the need to find alternatives, if possible :)
Additional context
N/A

Tracking this internally, will ping you when we have a branch ready for testing!

@evaleev this support was added with PR #320 🎉


rename haste-task-server to haste-task-spawn

Codecov Report

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

@@           Coverage Diff           @@
##           master     #105   +/-   ##
=======================================
  Coverage   96.01%   96.01%
=======================================
  Files          18       18
  Lines         201      201
  Branches       20       20
=======================================
  Hits          193      193
  Misses          8        8

Continue to review full report at Codecov.

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


garage: fix missing systemVersion and default pkg

Description of changes

systemVersion was not in scope, added config.system.systemVersion
garage_0_8_0 -> garage_0_8, the former does not exist

Things done

Built on platform(s)

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

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

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

cc @raitobezarius


Add ability to disable BLS verification for fuzzing

For beacon fuzz tests, we need the ability to disable bls signature verification.  See:
https://github.com/PegaSysEng/teku/blob/d2902530d79f417730a679e8a52a12c10605e08f/ethereum/core/src/main/java/tech/pegasys/teku/core/FuzzUtil.java#L90-L95
https://github.com/PegaSysEng/teku/blob/d2902530d79f417730a679e8a52a12c10605e08f/ethereum/core/src/main/java/tech/pegasys/teku/core/FuzzUtil.java#L157-L160

looks like this is talking about incorporating #1444 and then finishing the TODO sections


CK editor | On click of the Image, Link buttons, Admin user is being navigated to top of the Django CMS admin page | Chrome specific

I am currently working on a Django CMS project with below versions:

Django : 3.2.23
Django CMS : 3.11.1
Django CK Editor : 5.9.0 (django-ckeditor==5.9.0)

Issue : (Specific to Chrome browser)

When the admin user clicks on the Link or Image upload button, they are navigated to the top of the page.
Even after uploading the data/link and saving, the user is not navigated back to the same area of the page where the rich text is located.
If the user closes the popup, they are not navigated back to the same area of the page where the rich text is located.
This issue does not occur in Firefox, where it works as expected.

Record:
https://github.com/user-attachments/assets/a8dfd227-acc2-4bf6-b3d5-bb57910d5452

Thanks for the report. I have noticed this too and am also annoyed by it. However, this seems like a CKEditor 4 issue, and not a django-ckeditor issue, but I still hope we (someone) can do something about it.


x/pkgsite: strings.Trim misleading documentation

What is the URL of the page with the issue?
https://pkg.go.dev/strings
What is your user agent?
Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/<IP_ADDRESS> Safari/537.36
Screenshot
No response
What did you do?
I'm working on creating a package that extends the strings from the standard library and noticed a possible documentation oversight. The following functions in the strings package all claim to return a slice when they actually return a string. Maybe the author is considering a string as a special type of slice but based on how it reads I would expect the return type to be []string not string.
func Trim(s, cutset string) string
func TrimFunc(s string, f func(rune) bool) string
func TrimLeft(s, cutset string) string
func TrimLeftFunc(s string, f func(rune) bool) string
func TrimPrefix(s, prefix string) string
func TrimRight(s, cutset string) string
func TrimRightFunc(s string, f func(rune) bool) string
func TrimSpace(s string) string
func TrimSuffix(s, suffix string) string
What did you see happen?
The Trim* functions in the strings package all claim to return a slice when they actually return a string.
What did you expect to see?
Maybe the author is considering a string as a special type of slice but based on how it reads I would expect the return type to be []string not string.

the docs are correct, a string can be sliced, and it's relevant to whether the original string can be garbage collected.

the docs are correct, a string can be sliced, and it's relevant to whether the original string can be garbage collected.

You get how this is misleading though right? I mean I can agree with you but in golang slices have a very specific meaning that is different from what is being referenced here.

You get how this is misleading though right? I mean I can agree with you but in golang slices have a very specific meaning that is different from what is being referenced here.

Not really, this kind of language is used in the Language Specification too, for example:

Except for untyped strings, if the sliced operand is a string or slice, the result of the slice operation is

i.e. strings can be sliced and the result of the operation returns "a slice" of that string.

@seankhliao  @ALTree Your example from the language spec further supports what I am getting at actually. When the spec talks about slicing a string it is using slice as a verb and performing a slice action on a string. When the spec talks about "a slice" using the noun, it is talking about the variable length arrays. See it even goes out of its way to specify the difference. "if the sliced operand is a string or slice". If they were considered the same then they could have just said "if the sliced operand is a slice". In the strings package, the Trim functions say specifically "Trim returns a slice" not "a sliced string". You can't tell me that this is unambiguous. Why are you arguing against clarity in the documentation?


Failed to create process

Hi:
Thanks for your interesting tool.
However I get all the time the same error:  "failed to create process". Just writing the command mkdocs2pandoc .
Any clues on what could be happening?
TIA!

I have the same issue, running windows 7

I have the same issue on Win10, Python 3.5 64bit. It seems there's something wrong with the mkdocs2pandoc.exe file. I bypassed it by running the python script directly:
python "C:\Program Files\Python35\Scripts\mkdocs2pandoc-script.py" <arguments>


Tinymce changes not being recognized

When edits are made to tinymce textareas these should be registered and the questions marked as having changed to do all the "Do you want to quit without saving stuff". It's not happening just now.

fixed by https://github.com/DigitalCurationCentre/roadmap/commit/3503c5cff178f8ea744f4c8d0f5550109addeed9

Working as expected


This fixes addons in Volto itself

by using the root config using the nowadays accepted naming for the babel config:
https://babeljs.io/docs/en/config-files#project-wide-configuration
Projects are already using it.
Also, updated the adding the nodeExternals for testing addons

I messed things up, force pushed a better commit set.


Remove CE notes in Product and Why Pulumi pages

These lines were added in an attempt to make it clear there's a Community Edition and that it's free, but given the recent changes to the Pricing page, they're arguably no longer be necessary (since the VIEW PRICING buttons now bring you to a very that does make that clear).

@joeduffy just for consideration, wondering what you think.

Thanks, I appreciate that. I'm quite confident in how clear the Pricing page makes this now, and I'd like to remove elements that distract from the messaging in these areas, along with anything that makes Community Edition look like it might be something else.


first part of acdc db cleanup

need to update deployment script as well. (Do not merge yet)

https://github.com/dmwm/deployment/pull/156 need to be updated as well


test: add storage size test

Adds a test for how much storage space we're using up in Chromium, Firefox, and WebKit, using Playwright.
Currently does not actually test that the size doesn't increase. It's just for informational purposes for now.
I'm concerned Playwright will not work in CircleCI or will increase the yarn install time, but we'll see.

yarn install increased by 30s, that's fine


Conversions to SkyCoordinates should use astropy machinery for ICRS->GCRS conversion

As requested I've submitted a PR for changes so that the conversion from barycentric coordinates returned by the JPL ephemeris to the GCRS coordinates needed to create a SkyCoord for the apparent planet position is handled by the astropy coordinate transformation machinery.
The easiest way for me to do that was to change _get_absolute_planet_position to _get_barycentric_planet_position and to add a new routine to get the vector and distance between the Earth and the requested planet. This in turn suggested a change in the planet indexing convention.

@StuartLittlefair, do you mind if I include your descriptions on the improvements from your email in this thread, for others who may help review?

Not at all

I've been working on testing the code in this pull request against online tools (JPL Horizons and Skyfield).
Comparisons against JPL Horizons are awkward to get right because the ra and dec returned are not in the GCRS coordinate frame but are w.r.t to the Earth's true equator and poles. You can get the same results from Skyfield py passing epoch='date' to the radec function. I made a brief wrapper function in the tests to convert to ra and dec w.r.t to Earth's true equator and poles for comparison.
For geocentric observers I get compatible answers (to <1 arcsec) to both Horizons and Skyfield. The situation is worse when we have a non-geocentric observer. Errors can be as large as 1 degree for the Moon, but are much smaller for planets, so I suspect a problem in the astropy transformation chain for GCRS frames with non-zero obsgeoloc properties.

@StuartLittlefair - I looked at your improvements and generally they look good! Since @bmorris3 doesn't have time, might it be an idea to open a new PR with his and your commits combined, so one can comment there?
One question on principle: I noticed that you correct the time for light travel time. However, you calculate positions of both the body and the earth at this slightly earlier time; I think you should change the time only for the body in question.
On the final conversion to apparent position for a non-geocentric location: I wonder if the GCRS conversion doesn't somewhere implicitly assume that distances are large..
Finally, I think the routine just getting the barycentric position of the body should be public, as it is very useful.


July 12 - 16 - Take your first steps with Python

Event Information

Category
Details

Reactor Topic
Data Science and Machine Learning

Details
https://github.com/microsoft/Reactors/wiki/Take-Your-First-Steps-with-Python

Workshop(s) details

Date
Local Start Time
Location
Speaker
SharePoint ID
Platform

July 14, 2021
5:00 PM GMT
EMEA+ Bangalore
Allen Sanders
13824
----------

July 16, 2021
7:30 PM China Standard
Shanghai
Ryan Chung
13825
----------

Speakers updated and Shanghai Date updated on June 11


Extensive testing of certain configurations

Testing and benchmarking of different settings (data rate, PRF, channels, etc.).

Tested for all modes except 64 MHz, but should be fine too. Still, will be tested in the next couple of days.

Hi ! Before wiring my arduino Nano which is working with 5v logic, i would like to be sure that i don't risk anything with 5v ? Did you try or just used 3.3V with arduino mini ?
Thanks !

Hi! Yes, you should definitely NOT use 5V input, it will most likely destroy the IC. I have Mini Pro's that already take 3.3V and for other boards I use voltage regulators.
Just had a quick look at an image of the top layer of the Nano board: What about using the pin right next to digital pin "D13"? It seems to say "3V3", which would mean 3.3V (output?) to me.
Hope it helps!

Hi ! thanks for your reply!
yes there is a 3.3V output for tiny supplying but as the atmega on the arduino nano is supplied with a 5v voltage, the logic I/O of the board is 5v-0v ... i have 2 boards which are in 3.3V so i'm going to try that ! Otherwise there is still the possibility to use a standalone atmega ^^
Cheers !
Léopold

... oh, sure - I forgot about the I/O part - it's already late! ;-)

Hi ! I made them work thanks to your code !
I had really hard time to make all of this work... I used standalone atmega in 8Mhz internal clock (i just have 16Mhz quartz and you can't use them for 3.3V).
I didn't have a really good accuracy (something like +-30/30cm). Do you think the internal clock of the atmega can have an impact on it ? (internal clock is not accurate, it's around 8Mhz +-10% !) It seems that the duration of one iteration of the microcontroller does not affect the calcul of the ranging (travel time).
Also, my chip heated. I saw there is a thermometer inside the chip. Do we need to use it in order to correct the ranging or does the module correct it by itself ?
Thanks a lot !
Léopold

Hi! Great that it works!
I guess that the accuracy doesn't depend on you uC clock; the module has a crystal osc. on board and the uC only reads the IC-side timestamps. So delays or other inaccuracies won't matter, I believe.
Yes, there is a temperature sensor inside and another yes: one can use it to adjust timestamp results. Unfortunately I have not implemented the adjustment yet, because from the datasheet it seemed to me that this is not so important. But who knows, maybe it is and I should simply do it :-)
Your 200mA are really high, I have to measure it too. Will come back to you on this!
Cheers!

Thanks ! It's interesting to think that it can work in internal clock. I thought after that my question was stupid because an order of magnitude for Mhz drift would imply 1000m drift ^^ (and not centimeters...).
The datasheet indicates a 170mA max for RX mode and with a 40mA for the standalone atmega the result seems plausible.
Did you supply the module with your arduino pro mini (max current 150mA) ? I used to supply it with a arduino uno but the max output current for 3.3v is 50mA ! :O (that's why i have 2.7v and the chip which randomly restart... I will try with an external 3.3v regulator !)

Hi! You're right, the 200mA are plausible. Maybe I should implement a setting that after an TX/RX the IC can be put to sleep for a specific time span. This would allow to save energy while still one can follow a certain timed protocol (like "I sent something and expect a response as early as in XY ms, so I can safely take a nap for about XY ms"). What do you think?
I use an external power supply; the IC works fine in this setup.
Cheers!


[release/1.6] Adds mediatype to OCI index record on export

Cherry pick for adding the mediatype to oci index record. :)
(cherry picked from commit 17ea3959bc3aa32ac9670983c765c6b28402f618)

xref: https://github.com/containerd/containerd/pull/9867


Update index.md

Added Entity Framework Plus and Entity Framework Extensions in the third party libraries section.

Thanks @JonathanMagnan. I have merged your PR. If you can provide links to more EF Core-related contents, please send a new PR.

Sure we will very soon provide way more example in EF Core.
Now that Fiddle is supporting EF Core: https://dotnetfiddle.net/gIuYXg, we will try to provide 2 examples (one for EF6 and one for EF Core).
EF Plus
At this moment, the following features in EF Plus are supported:

Batch Delete
Batch Update
Audit
Query Cache
Query Deferred
Query Filter
Query Future
Query Include Filter

(Pretty much all features)
EF Extensions
Almost everything here as well should already be supported in EF Core.


feat: Allow connector to persist initial UID validity of mailboxes

I just noticed that since we get the UIDValidity from the connector, update the connector, we might as well just keep it in memory and skip the database all together :thinking:


What is changing in v2?

I see that there is v2.0.0-alpha.1 tag.
Whats changing?

Check https://github.com/bitinn/node-fetch/blob/master/CHANGELOG.md#2x-release (especially the "major" points). The upgrade guide is helpful too, as it outlines the most important changes.

Thank you! Sorry, I have missed it.


Placeholder for PRs regarding identity spec

This is just a tracking issue for myself, and maybe people who review the PRs.
High level PRs:

[x] https://github.com/matrix-org/matrix-doc/pull/2254 - Mirror v1 to v2 where behaviour is unchanged (aside from auth). Covers part of MSC2140.
[x] https://github.com/matrix-org/matrix-doc/pull/2255 - Actually define auth for identity servers. Covers part of MSC2140. Refer to MSC1961 (excl) when in doubt.
[x] https://github.com/matrix-org/matrix-doc/pull/2258 - Define terms of service handling. Covers part of MSC2140. Will probably be based upon PR2, and might be best to just merge them together.
[x] https://github.com/matrix-org/matrix-doc/pull/2279 - Remove bind_msisdn and bind_email from /register. Covers part of MSC2140.
[x] https://github.com/matrix-org/matrix-doc/pull/2282 - Define new unbind endpoint and behaviour from MSC2140 (last 2140).
[x] https://github.com/matrix-org/matrix-doc/pull/2281 - Introduce storing IS in account data. Covers MSC2230 (excl).
[x] https://github.com/matrix-org/matrix-doc/pull/2287 - Introduce new lookup endpoint. Covers MSC2134 (excl).
[ ] Deprecate id_server in requestToken. Covers MSC2263 (excl).
[x] https://github.com/matrix-org/matrix-doc/pull/2304 - Fix isvalid (and other v2) references for third party invites, etc
[ ] Add new add/bind endpoints for 3PIDs. Covers MSC2290 (excl).

Note: MSC2264 (excl) requires no spec changes.

The remainder of this is blocked until 2290 decides if it is obsoletes 2263 or not.

2290 has decided that 2263 is fine, so this is unblocked again.

This now has all spec PRs open/merged - closing as this tracker is not needed anymore.


Move fetch api definition feature to Zally API

The web ui currently does the fetching of an api definition which is given via an url by the user. The web ui implements this on server side in Node.
Let's discuss if we should change our Zally API to also accept links to api definition files. There are different ways of designing this:

adding new endpoint only for urls
adding new optional field in payload of current api-violations endpoint
transparently accepting a link in current api_definitionfield

Looking for feedback from you, @netme @mkulak @rbarilani. Do you wanna have this in Zally API? And if yes, which design do you prefer?

@fmueller, nice summary 👍
I will go for option 2:

adding new optional field in payload of current api-violations endpoint

Reason: the responsibility of /api-violations stays the same, it just a way how you define the API, by URL or providing a JSON.

@fmueller I am for the third option because I like keep the api surface smaller as possible so or you provide a schema or you provide a link to a schema.

Don't have strong preference here.
Option 2 looks slightly better (b/c of not overloading field meaning)

Ok, then we'll go with option 2:

adding api_definition_url field
making both fields, api_definition and api_definition_url, optional
returning BAD_REQUEST if none of them is in the request or both (the API only accepts one field at once)

Btw, we should also move it out of cli component.


Fix: unit test Runtime_Abs random failure

[Problem]
There are very low probability to meet  segmentation fault when run the unit test Runtime_Abs
[Root Cause]
In worst case, we will allocate 3 float arrays each size is 100^3, it's very large for a scoped array on stack.
[Solution]
Avoid use variable-length array which might cause segmentation fault, Use std::vector for dynamic memory allocation.

👍


activePackageSource should be removed since it's deprecated

Per https://learn.microsoft.com/en-us/nuget/reference/nuget-config-file#activepackagesource

Merged the PR. Thanks for taking care of this!


[BUG] Poseidon padding on empty hashes is not correct

https://github.com/webb-tools/arkworks-gadgets/blob/b2fc1f4a6f9a194ba5a5080df96c8783ef45f9bf/arkworks-gadgets/src/merkle_tree/mod.rs#L373
this is feeding evaluate a length-0 array, then a leading 0 is added within evaluate, but then it goes to permute with length 1 and is not padded to have length 3

To make it more semantically correct, we should pass [0u8; 32] here: https://github.com/webb-tools/arkworks-gadgets/blob/master/arkworks-gadgets/src/merkle_tree/mod.rs#L374

Ah I've been meaning to ask: Why should that array have length 32? I removed the constraint on the array's length while trying to match up to our old implementation, but could change it back if there's a reason for 32

Yes, you are right, we should generally avoid using fixed-size arrays for representing field values since not all elliptic curve fields are the same.
@drewstone This can become a problem in substrate since we use Element([u8; 32])

I think we'll be alright here truly on the Substrate side. We are expecting a specific curve/hash there and shouldn't over-worry about generalization.


Bug in model_config - tf_efficientdet_d7

Hi @rwightman,
Thank you for your amazing work.
When I tried using tf_efficientdet_d7, I found out it actually used tf_efficientdet_d6 backbone. Diving a little into your code, I found a small bug in efficientdet_model_param_dict in model_config.py.
    tf_efficientdet_d7=dict(
        name='tf_efficientdet_d7',
        backbone_name='tf_efficientnet_b6', # ~~> should be b7
        image_size=1536,
        fpn_channels=384,
        fpn_cell_repeats=8,
        box_class_repeats=5,
        anchor_scale=5.0,
        fpn_name='bifpn_sum',  # Use unweighted sum for training stability.
        backbone_args=dict(drop_rate=0.5, drop_path_rate=0.2),
        url='https://github.com/rwightman/efficientdet-pytorch/releases/download/v0.1/tf_efficientdet_d7-f05bf714.pth'
    ),

Hope you fix it soon.
Have a nice day.

It's not a bug, D7 uses B6 backbone as per the official impl. The weights wouldn't work if that wasn't the case. You can make your own config and train from scratch if you want to try it.

@rwightman  Do u have a speed benchmark on GTX 1080ti on all variants of efficientdets.


downgrade fedora for sync check

Summary of changes
Changes introduced in this pull request:

let's downgrade Fedora back to 36 for now. The root issue of forest-tester missing calibnet network has been resolved in https://github.com/docker/compose/pull/10778, but it's difficult to say when it will land in the DNF registry.

Reference issue to close (if applicable)

Closes
Other information and links

Also https://github.com/ChainSafe/forest-iac/issues/166

Actually, I'm not sure it's the way to go. Converting to draft.


weird errors when "pip install django-salesforce"

My project layout looks something like this:
project_directory
  .git
  env       # virtualenv directory
  src       # python source files
  .gitignore
  fabfile.py
  config.ini
  requirements.txt

When I try to "pip install django-salesforce" (with activated virtualenv), I get errors like this:
 $ pip install django-salesforce
Downloading/unpacking django-salesforce
  Running setup.py egg_info for package django-salesforce
    package version: 0.2.0

Installing collected packages: django-salesforce
  Running setup.py install for django-salesforce
    package version: 0.2.0

    error: Error: setup script specifies an absolute path:

        /home/benjamin/projects/my-awesome-project/fabfile.py

    setup() arguments must *always* be /-separated paths relative to the
    setup.py directory, *never* absolute paths.

    Complete output from command /home/benjamin/projects/my-awesome-project/env/bin/python -c "import setuptools;__file__='/home/benjamin/projects/my-awesome-project/env/build/django-salesforce/setup.py';exec(compile(open(__file__).read().replace('\r\n', '\n'), __file__, 'exec'))" install --record /tmp/pip-Kl93mQ-record/install-record.txt --single-version-externally-managed --install-headers /home/benjamin/projects/my-awesome-project/env/include/site/python2.7:
    package version: 0.2.0

This happens as long as there is anything in project_directory other than env. Even hidden folders and files like .git and .gitignore cause the exception above.
I'm not really grokking your setup.py, so I have no idea what causes this. But I haven't seen this error with any other package.

WOW thanks


Html rendering as plain text

Hello,
I was able to view an html page as html when I would type it in main.cpp but after creating an index.html file and streaming it in, it is rendering as plain text on my browser.
This is my main.cpp:
#include "crow_all.h"
using namespace std;
using namespace crow;

int main(int argc, char* argv[]) {
    crow::SimpleApp app;

    CROW_ROUTE(app, "/")
        ([](const request &req, response &res){
            ifstream in("../public/index.html", ifstream::in);
            if(in) {
                ostringstream contents;
                contents << in.rdbuf();
                in.close();
                res.write(contents.str());
            } else {
                res.write("Not found");
            }
            res.end();
         });

    char* port = getenv("PORT");
    uint16_t iPort = static_cast<uint16_t>(port != NULL? stoi(port): 18080);
    cout << "PORT = " << iPort << "\n";
    app.port(iPort).multithreaded().run();
}

And this is my index.html:

Crow C++

H1, Crow.

Was able to view it as html by setting the response header to "text/html":
set_header("Content-Type", "text/html");


Update api.php

User description

Closes #
📑 Description

✅ Checks

[ ] My pull request adheres to the code style of this project
[ ] My code requires changes to the documentation
[ ] I have updated the documentation as required
[ ] All the tests have passed

☢ Does this introduce a breaking change?

[ ] Yes
[ ] No

ℹ Additional Information

Description

Refactored the data fetching logic to use fetchAllGitHubPages, improving the handling of paginated responses.
Added a new function getNextPageUrl to manage pagination in API requests.
Enhanced the repository data structure to include additional fields such as language and visibility.
Improved error handling by checking for curl errors during API calls.

Changes walkthrough 📝
Relevant filesEnhancement

api.phpRefactor API data fetching and enhance repository details

Src/api.php
Replaced loadData function with fetchAllGitHubPages for improved data fetching.  Added pagination handling for GitHub API responses.  Enhanced repository data retrieval with additional fields.  Improved error handling during API calls.

+60/-34

💡 Penify usage:
Comment /help on the PR to get a list of all available Penify tools and their descriptions

@gstraccini codacy bypass


/etc/iscsi/initiatorname.iscsi not found

After installing with opensds-installer ansible in csi mode with LVM backend, the nodeplugin pod failed to start.  The reason was /etc/iscsi/initiatorname.iscsi not found.  "sudo apt-get install open-iscsi" should be part of the deployment step if LVM is selected.
xyang@ubuntu:~/go/src/github.com/opensds/nbp/csi/server/deploy$ kubectl get pod
NAME                                 READY     STATUS             RESTARTS   AGE
csi-attacher-opensdsplugin-0         2/2       Running            0          7m
csi-nodeplugin-opensdsplugin-sdhs2   1/2       CrashLoopBackOff   6          7m
csi-provisioner-opensdsplugin-0      2/2       Running            0          7m
xyang@ubuntu:~/go/src/github.com/opensds/nbp/csi/server/deploy$ kubectl logs csi-nodeplugin-opensdsplugin-sdhs2 opensds
2018/06/10 15:45:29 proto: unix addr: var/lib/kubelet/plugins/csi-opensdsplugin/csi.sock
2018/06/10 15:45:29 remove sock file: var/lib/kubelet/plugins/csi-opensdsplugin/csi.sock
2018/06/10 15:45:29 start to serve: var/lib/kubelet/plugins/csi-opensdsplugin/csi.sock
2018/06/10 15:45:30 start to GetPluginInfo
2018/06/10 15:45:30 end to GetPluginInfo
2018/06/10 15:45:30 start to GetNodeID
2018/06/10 15:45:30 result from cat: cat: /etc/iscsi/initiatorname.iscsi: No such file or directory
2018/06/10 15:45:30 Error encountered gathering initiator names: exit status 1
2018/06/10 15:45:30 end to GetNodeID
2018/06/10 15:45:31 start to GetPluginInfo
2018/06/10 15:45:31 end to GetPluginInfo
2018/06/10 15:45:31 start to GetNodeID
2018/06/10 15:45:31 result from cat: cat: /etc/iscsi/initiatorname.iscsi: No such file or directory
2018/06/10 15:45:31 Error encountered gathering initiator names: exit status 1
2018/06/10 15:45:31 end to GetNodeID
2018/06/10 15:45:45 start to GetPluginInfo
2018/06/10 15:45:45 end to GetPluginInfo
2018/06/10 15:45:45 start to GetNodeID
2018/06/10 15:45:45 result from cat: cat: /etc/iscsi/initiatorname.iscsi: No such file or directory
2018/06/10 15:45:45 Error encountered gathering initiator names: exit status 1
2018/06/10 15:45:45 end to GetNodeID
2018/06/10 15:46:12 start to GetPluginInfo
2018/06/10 15:46:12 end to GetPluginInfo
2018/06/10 15:46:12 start to GetNodeID
2018/06/10 15:46:12 result from cat: cat: /etc/iscsi/initiatorname.iscsi: No such file or directory
2018/06/10 15:46:12 Error encountered gathering initiator names: exit status 1
2018/06/10 15:46:12 end to GetNodeID
2018/06/10 15:46:54 start to GetPluginInfo
2018/06/10 15:46:54 end to GetPluginInfo
2018/06/10 15:46:54 start to GetNodeID
2018/06/10 15:46:54 result from cat: cat: /etc/iscsi/initiatorname.iscsi: No such file or directory
2018/06/10 15:46:54 Error encountered gathering initiator names: exit status 1
2018/06/10 15:46:54 end to GetNodeID
2018/06/10 15:48:27 start to GetPluginInfo
2018/06/10 15:48:27 end to GetPluginInfo
2018/06/10 15:48:27 start to GetNodeID
2018/06/10 15:48:27 result from cat: cat: /etc/iscsi/initiatorname.iscsi: No such file or directory
2018/06/10 15:48:27 Error encountered gathering initiator names: exit status 1
2018/06/10 15:48:27 end to GetNodeID

Got it, because open-iscsi is installed in some environments by default, so we forgot to add it in the package.

I found that open-iscsi is already installed when installing nbp modules using ansible, so I guess we should add this package installation in csi Dockfile.


Use natural logarithm in MathUtils

Base 10 logarithms are ugly.

@davidbenjamin This seems like a good task for the reporter to complete :)

With pleasure!


fix: Add MPL-2.0 to allow list for deny action and regenerate Cargo.lock file

Description
The deny action is failing on master due to some of our dependencies using MPL-2.0 and also an issue with respects to duplicate entries in Cargo.toml.
For the first, I added MPL-2.0 to deny.toml and the for the second I regenerated the .lock file
Problem*

Resolves
Summary*

Documentation

[ ] This PR requires documentation updates when merged.

[ ] I will submit a noir-lang/docs PR.

[ ] I will request for and support Dev Rel's help in documenting this PR.

Additional Context

PR Checklist*

[ ] I have tested the changes locally.
[ ] I have formatted the changes with Prettier and/or cargo fmt on default settings.

I had to run cargo update --precise for quite a few dependencies -- which is why the actions are failing. Might be worth it to remove the Cargo.lock change and just add the MPL-2.0 change for now


bug: arm64 binaries are not available on PyPI

Currently, we only distribute amd64 on PyPI for both Mac and Linux but not arm64.
    - name: Configure linux build environment
      if: runner.os == 'Linux'
      run: |
        mkdir -p bin
        mv dist/envd_linux_amd64_v1/envd bin/envd
        chmod +x bin/envd
    - name: Configure macOS build environment
      if: runner.os == 'macOS'
      run: |
        mkdir -p bin
        mv dist/envd_darwin_amd64_v1/envd bin/envd
        chmod +x bin/envd

We should support arm64, especially for Apple M1 users.

SGTM, it should be easy since we use cibuildwheel and goreleaser.

/assign
I can help improve the CI, but I cannot test if it works since I do not have a machine for it.

How can I help test if I have a machine in arm64?

@popfido
Thanks! could you please run the commands to build and test if the build works on ARM64 macOS:
make
./bin/envd bootstrap
./bin/envd up -p ./pkg/app/testdata/build-test

We can add ci with arm by qemu https://github.com/docker/setup-qemu-action. Although I head the performance is very bad

@gaocegege
Here is the  ./bin/envd up -p ./pkg/app/testdata/build-test results in cmd.
[+] ⌚ parse build.envd and download/cache dependencies 0.0s ✅ (finished)
[+] 🐋 build envd environment 90.1s (11/11) ✅ (finished)
 => docker-image://docker.io/tensorchord/python:3.8-ubuntu20.04                                                                                61.4s
 => => resolve docker.io/tensorchord/python:3.8-ubuntu20.04                                                                                5.7s
 => => sha256:c03f0eb9ed3e9ecc9777137ca64d13d1e7dba88eadcc151074a918d94821415c 3.20MB / 3.20MB                                                                                1.4s
 => => sha256:dd0b398750f4b004a65c1bb9bf2c93b7a753756afaea45ac0dd29ab305661141 58.96MB / 58.96MB                                                                                31.1s
 => => sha256:3e66387987ad1b955b18ed108c3e53074f997ec0b7d93a02b11308276e0ddcf6 91.22MB / 91.22MB                                                                                51.1s
 => => sha256:d7bfe07ed8476565a440c2113cc64d7c0409dba8ef761fb3ec019d7e6b5952df 28.57MB / 28.57MB                                                                                11.2s
 => => extracting sha256:d7bfe07ed8476565a440c2113cc64d7c0409dba8ef761fb3ec019d7e6b5952df                                                                                0.9s
 => => extracting sha256:3e66387987ad1b955b18ed108c3e53074f997ec0b7d93a02b11308276e0ddcf6                                                                                2.7s
 => => extracting sha256:dd0b398750f4b004a65c1bb9bf2c93b7a753756afaea45ac0dd29ab305661141                                                                                1.8s
 => => extracting sha256:c03f0eb9ed3e9ecc9777137ca64d13d1e7dba88eadcc151074a918d94821415c                                                                                0.1s
 => [internal] create user group envd                                                                                0.2s
 => [internal] create user envd                                                                                0.2s
 => [internal] add user envd to sudoers                                                                                0.3s
 => [internal] configure user permissions                                                                                0.1s
 => [internal] configure user permissions                                                                                7.0s
 => install ssh keys                                                                                0.0s
 => install PyPI packages                                                                                0.0s
 => install ssh keys                                                                                0.0s
 => merging all components into one                                                                                0.0s
 => exporting to oci image format                                                                                20.8s
 => => exporting layers                                                                                5.5s
 => => exporting manifest sha256:06b240e4fe4d92d1110347c4fa2356f5ca0ed436cf132d640220ba547581dde3                                                                                0.0s
 => => exporting config sha256:5538a6145c5e321d4d2dcd068970e85ab85c117b4119794182b80043556ab665                                                                                0.0s
 => => sending tarball                                                                                15.4s
To run a command as administrator (user "root"), use "sudo <command>".
See "man sudo_root" for details.

Thanks! Then it should work!
@all-contributors please add @popfido  for platform

cc @VoVAllen

Gotcha, let me test if it works on Linux arm64 first. Then let's see why it fails on macOS arm64.

Gotcha, let me test if it works on Linux arm64 first. Then let's see why it fails on macOS arm64.

after update docker for mac and brew install gcc. work fine

It is weird. I cannot figure out why it requires GCC.
BTW, what's your previous docker version?

docker version: v4.9.0, maybe not GCC, I try again without GCC

It is weird. I cannot figure out why it requires GCC.
BTW, what's your previous docker version?

BTW, how to clear cache

Yep. You can docker stop envd_buildkitd && docker rm envd_buildkitd && envd bootstrap to create a new clean buildkitd.

Then it is related to the docker version. It is reasonable although I do not know why hhh

How about this https://veertu.com/?
Originally posted by @aseaday in https://github.com/tensorchord/envd/issues/414#issuecomment-1171382038

https://github.com/github/roadmap/issues/528
GitHub supports M1 now (in beta)
Let's give it a try.

https://dev.to/thewraven/universal-macos-binaries-with-go-1-16-3mm3 I am creating a universal bin for the build.

https://github.com/gaocegege/envd/actions/runs/3562709880/jobs/5984732217 It works!
Let's summarize the change in my personal fork and submit a PR here.

I am publishing v0.2.5-rc.1, which should supports arm64 in macOS.


[7.11.24] Make POI deletion user-friendly

Motivation

POIs referenced by a contact are protected from deletion. Users will encounter an error with no explanation when they try to delete such a POI and this is not friendly.
Proposed Solution

Hide delete option/button if the POI is referenced by a contact and explain why it cannot be deleted.
Alternatives

Leave it as it is
User Story

Additional Context

Implement after #2952 and #2953
Design Requirements

Implemented together in #3007


Test bot

Wowwwww

added backport-needed/1.1.0 issue: #48.

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

2

21

22

23

24

25

26

7

28

29

30

31

32

33

34

35

36

37

38

39

40

1

42

43

44

45

46

47

48

49

50

52

53

54

55

6

57

58

59

60

61

62

63

64

65

66

67

68

69

70

71

72

73

74

75

76

77

78

79

80

81

82

83

84

85

86

87

88

89

90

91

92

93

94

95

96

98

99

100

101

102

103

added backport-needed/1.1.0 issue: #49.

added backport-needed/1.1.0 issue: #52.

added backport-needed/v1.1.0 issue: #53.

added backport-needed/v1.1.0 issue: #54.

added backport-needed/v1.1.0 issue: #55.

added backport-needed/v1.1.0 issue: #56.

added backport-needed/1.1.0 issue: #57.

added backport-needed/v1.1.0 issue: #58.

added backport-needed/1.1.0 issue: #59.

added backport-needed/v1.1.0 issue: #60.

added backport-needed/v1.1.0 issue: #61.

added backport-needed/1.1.0 issue: #62.

added backport-needed/1.1.0 issue: #63.

added backport-needed/1.1.0 issue: #64.

added backport-needed/1.1.0 issue: #65.

added backport-needed/1.1.0 issue: #68.

added backport-needed/1.1.0 issue: #69.

added backport-needed/1.1.0 issue: #71.

added backport-needed/1.1.0 issue: #72.

added backport-needed/1.1.0 issue: #73.

added backport-needed/1.1.0 issue: #74.

added backport-needed/1.1.0 issue: #75.

added backport-needed/1.1.0 issue: #76.

added backport-needed/1.1.0 issue: #77.

added backport-needed/1.1.0 issue: #78.

added backport-needed/1.1.0 issue: #79.

added backport-needed/1.1.0 issue: #80.

added backport-needed/1.1.0 issue: #81.

added backport-needed/1.1.0 issue: #82.

added backport-needed/1.1.0 issue: #83.

added backport-needed/1.1.0 issue: #85.

added backport-needed/1.1.0 issue: #86.

added backport-needed/1.1.0 issue: #87.

added backport-needed/1.1.0 issue: #88.

added backport-needed/1.1.0 issue: #89.

added backport-needed/1.1.0 issue: #90.

added backport-needed/1.1.0 issue: #91.

added backport-needed/1.1.0 issue: #92.

added backport-needed/1.1.0 issue: #93.

added backport-needed/1.1.0 issue: #94.

added backport-needed/1.1.0 issue: #95.

added backport-needed/1.1.0 issue: #96.

added backport-needed/1.1.0 issue: #97.

added backport-needed/1.1.0 issue: #98.

Pre Ready-For-Testing Checklist

[ ] If labeled: require/HEP Has the Harvester Enhancement Proposal PR submitted?
The HEP PR is at:

[ ] Where is the reproduce steps/test steps documented?
The reproduce steps/test steps are at:

[ ] Is there a workaround for the issue? If so, where is it documented?
The workaround is at:

[ ] Have the backend code been merged (harvester, harvester-installer, etc) (including backport-needed/*)?
The PR is at:

[ ] Does the PR include the explanation for the fix or the feature?

[ ] Does the PR include deployment change (YAML/Chart)? If so, where are the PRs for both YAML file and Chart?
The PR for the YAML change is at:
The PR for the chart change is at:

[ ] If labeled: area/ui Has the UI issue filed or ready to be merged?
The UI issue/PR is at:

[ ] If labeled: require/doc, require/knowledge-base Has the necessary document PR submitted or merged?
The documentation/KB PR is at:

[ ] If NOT labeled: not-require/test-plan Has the e2e test plan been merged? Have QAs agreed on the automation test case? If only test case skeleton w/o implementation, have you created an implementation issue?

The automation skeleton PR is at:
The automation test case PR is at:

[ ] If the fix introduces the code for backward compatibility Has a separate issue been filed with the label release/obsolete-compatibility?
The compatibility issue is filed at:

Automation e2e test issue: chrisho/tests#8

added backport-needed/1.1.0 issue: #99.

added backport-needed/1.1.0 issue: #100.

added backport-needed/1.1.0 issue: #101.

added backport-needed/1.1.0 issue: #102.

added backport-needed/1.0.4 issue: #103.

added backport-needed/1.0.4 issue: #104.


Unable to build binaries manually from source in Windows

node-pre-gyp ERR! Tried to download(403): https://mapbox-node-binary.s3.amazonaws.com/sqlite3/v4.0.0/node-v64-win32-x64.tar.gz
node-pre-gyp ERR! Pre-built binaries not found for<EMAIL_ADDRESS>and<EMAIL_ADDRESS>(node-v64 ABI, unknown) (falling back to source compile with node-gyp)
Building the projects in this solution one at a time. To enable parallel build, please add the "/m" switch.
C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\Common7\IDE\VC\VCTargets\Microsoft.Cpp.Platform.targets(57,5): error MSB8020: The build tools for v140 (Platform Toolset = 'v140') cannot be found. To build using the v140
 build tools, please install v140 build tools.  Alternatively, you may upgrade to the current Visual Studio tools by selecting the Project menu or right-click the solution, and then selecting "Retarget solution". [<REDACTED>\node_modules\sqlite3\build\deps\action_before_build.vcxproj]

By forcefully using the build tools from NPM, it worked. But I don't think this is the intended behavior?

Same problem for linux x64
https://mapbox-node-binary.s3.amazonaws.com/sqlite3/v3.1.13/node-v64-linux-x64.tar.gz
Gets back some access denied. And it seems like the fallback to build from source fails, need to manually call it with --build-from-source.

I guess the problem is node v10. It fails to work with sqlite3 latest 3.* version installed before upgrading to node v10, and it fails to install/build sqlite3 v4. I had to downgrade to node v8 and reinstall sqlite3 v4. I suspect upgrading to node v10 after installing/rebuilding sqlite3 v4 will not work.

same here. Fails on node v10
gyp ERR! node -v v10.2.0
gyp ERR! node-gyp -v v3.6.2
gyp ERR! not ok
node-pre-gyp ERR! build error
node-pre-gyp ERR! stack Error: Failed to execute 'C:\Program Files\nodejs\node.exe C:\Users\Patrik\AppData\Roaming\npm\node_mo
dules\npm\node_modules\node-gyp\bin\node-gyp.js build --fallback-to-build --module=D:\Work\PiGallery2\node_modules\sqlite3\lib
\binding\node-v64-win32-x64\node_sqlite3.node --module_name=node_sqlite3 --module_path=D:\Work\PiGallery2\node_modules\sqlite3
\lib\binding\node-v64-win32-x64 --napi_version=3 --node_abi_napi=napi' (1)
node-pre-gyp ERR! stack     at ChildProcess.<anonymous> (D:\Work\PiGallery2\node_modules\sqlite3\node_modules\node-pre-gyp\lib
\util\compile.js:83:29)
node-pre-gyp ERR! stack     at ChildProcess.emit (events.js:182:13)
node-pre-gyp ERR! stack     at maybeClose (internal/child_process.js:961:16)
node-pre-gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:248:5)
node-pre-gyp ERR! System Windows_NT 10.0.17134
node-pre-gyp ERR! command "C:\\Program Files\\nodejs\\node.exe" "D:\\Work\\PiGallery2\\node_modules\\sqlite3\\node_modules\\no
de-pre-gyp\\bin\\node-pre-gyp" "install" "--fallback-to-build"
node-pre-gyp ERR! cwd D:\Work\PiGallery2\node_modules\sqlite3
node-pre-gyp ERR! node -v v10.2.0
node-pre-gyp ERR! node-pre-gyp -v v0.9.0
node-pre-gyp ERR! not ok

#994

The v4.0.1 release now supports node v10: https://github.com/mapbox/node-sqlite3/blob/master/CHANGELOG.md#401


How to simply convert video files (i.e.: Avi to MP4)?

Hi,
I simply want to convert files, any format to any format (at the moment, I need to convert AVI to MP4-h264 AND MP4-h264 to AVI), without losing quality. I don't want to resize (scale) the video, I don't want to change its aspect ratio and I don't want it to lose quality (this is very important); all I want is "to change the format", that's all. I found this code for only ffmpeg
"ffmpeg -i 1.mkv -codec copy 2.mp4"
Is there a similar way in ffmpeg laravel?
I am currently using
"
FFMpeg::fromDisk('local')
->open($path)
->export()
->inFormat(new \FFMpeg\Format\Video\X264('libmp3lame', 'libx264'))
->toDisk('convert_video')
->save('$name.mp4');
"
but it takes too long
Does ffmpeg laravel have a format for avi?

I just tagged v7.0.5 which has a CopyFormat class: https://github.com/pascalbaljetmedia/laravel-ffmpeg#export-without-transcoding


post_boot.sh

I apreciate that you took post_boot.sh on board!
Here are a few suggestions on the current implementation:
1 You left all the post-boot tasks in /etc/profile, further a lot of them use sudo.
This is bad for several reasons:
a) if no local user logs in after boot, net related fixes wont have run when remote logging is attempted.
b) This assumes logged in user has sudo, whilst probably true at this point in time, its an unnecesary dependency, that sooner or later down the line will blow up and cause issues.
c) Unless Im mistaken they are post boot one-offs. If that is true no need to have them run on each login.
2 It should probably be in /usr/local/sbin
This is kind of my fault, when I first sent it to you I referred to its path as /usr/local/bin out of habit
I will include samples of post_boot.sh and /etc/profile with changes that seem to not cause any issue on my instance, but before using, I would suggest to double check all the changes.

Hm file upload doesn't seem to work on the iPad...
#!/bin/sh
#
#  Copyright (c) 2022<EMAIL_ADDRESS>#  License: MIT
#
#   Version: 1.1.0  2022-05-10
#
#  Intended usage is for cronless systems, or when cron can not be trusted
#  to start up on its own.  Needing to do some sanity checks after booting.
#  Trigger this in /etc/inittab by adding a line:
#
#  ::wait:/usr/local/bin/post_boot.sh
#
#  Before starting /sbin/openrc or similar
#

#
#  If run with no params, spawn another instance in the background and exit
#  in order to be inittab friendly
#
if [ "$1" = "" ]; then
    $0 will_run > /tmp/post_boot.log 2>&1  &
    exit 0
fi

#
#  Give the system time to complete it's startup
#
sleep 10

if [[ -e /etc/FIRSTBOOT ]]; then
   # /dev/null gets screwed up at times.  Recreate just in case
   # the first time we boot
   rm /dev/null > /tmp/profile.debug 2>&1
   mknod /dev/null c 1 3 >> /tmp/profile.debug 2>&1
   chmod 666 /dev/null >> /tmp/profile.debug 2>&1

   # Start a couple of services
   rc-update add dcron >/dev/null 2>/dev/null
   rc-update add runbg >/dev/null 2>/dev/null

   rm /etc/FIRSTBOOT # Only do this stuff once, so remove the file now
fi

# The following is needed for upstream PR #1716
if [ ! -e /dev/fd ]; then
   ln -s /proc/self/fd /dev/fd
fi

# Hack for Alpine 3.14.0
OS=`/bin/cat /etc/alpine-release`

if [ $OS = '3.14.0' ]; then
    # In Alpine 3.14 services do not start up correctly.  Run script to fix
    # that if needed
    /usr/local/bin/fix_services
fi

# /etc/init.d/networking keeps getting an extra } written at the end
# For some unknown reason.  Overwrite it when we login to hopefully
# mitigate that
#sudo cp /root/init.d/networking /etc/init.d

#
#  Ensure intended services are up
#

/etc/init.d/sshd restart
/etc/init.d/runbg restart
/etc/init.d/dcron restart

#!/bin/bash
# Do various things to make iSH more useful.  Or work around
# oddness

# First we do stuff that only needs to happen when the root image
# is booted for the first time

ID=`id -u`

# Hack for Alpine 3.14.0
OS=`/bin/cat /etc/alpine-release`

# motd works for root it 3.14.0, but not anyone else for some reason.  Annoying
if [ $OS = '3.14.0' ] && [ $ID -ne 0 ]; then
    echo
    cat /etc/motd
fi

# Let's set the path here since that covers both zsh and bash
export PATH=/usr/local/bin:/bin:/usr/bin:/usr/sbin:/sbin:/usr/local/games

CHECK=`/bin/rc-status 2> /dev/null | grep sshd | wc -l`

VERBOSE=0

if [ $CHECK -eq 0 ] || [ $ID -ne 0 ]; then
   VERBOSE=1
fi

# echo $CHECK $ID $VERBOSE

if [[ $VERBOSE -eq 1 ]]; then
   echo
   echo "------------------------------------------"
   echo
fi

if [[ $CHECK -eq 0 ]]; then
   echo "Enable sshd on port 1022: enable_sshd"
   echo
fi

if [[ $ID -ne 0 ]]; then
   echo "Use sudo to run commands as root"
   echo
fi

if [[ $VERBOSE -eq 1 ]]; then
   echo "------------------------------------------"
   echo
fi

CPU_STATE=`/usr/local/bin/mc status`
echo "Multicore State=$CPU_STATE"

LOCK_STATE=`/usr/local/bin/elock status`
echo "Extra Locking State=$LOCK_STATE"

echo ""

Sorry about that and thank you for the fixes/updates.  I'll investigate/incorporate these into the next FS release.


Update dependences

Update material-ui                  ^0.15.0-alpha.1  →  ^0.15.0-alpha.2
Update react                                ^15.0.0  →          ^15.0.1
Update react-dom                            ^15.0.0  →          ^15.0.1
Update react-redux                           ^4.4.0  →           ^4.4.1
Update babel-core                            ^6.6.5  →           ^6.7.6
Update expect                               ^1.14.0  →          ^1.16.0
Update karma-chrome-launcher                 ^0.2.2  →           ^0.2.3
Update react-addons-test-utils              ^15.0.0  →          ^15.0.1
Update redux-devtools                        ^3.1.1  →           ^3.2.0
Update redux-devtools-dock-monitor           ^1.1.0  →           ^1.1.1
Update redux-devtools-log-monitor            ^1.0.5  →           ^1.0.9
Update sass-loader                           ^3.1.2  →           ^3.2.0
Update style-loader                         ^0.13.0  →          ^0.13.1

The reason of this updates is because in the new release of React (v.15.0) had little bugs that are solved in the v.15.0.1