C8 is no longer working

Please follow the guide below

You will be asked some questions and requested to provide some information, please read them carefully and answer honestly
Put an x into all the boxes [ ] relevant to your issue (like that [x])
Use Preview tab to see how your issue will actually look like

Make sure you are using the latest version: run youtube-dl --version and ensure your version is 2016.12.09. If it's not read this FAQ entry and update. Issues with outdated version will be rejected.

[x] I've verified and I assure that I'm running youtube-dl 2016.12.09

Before submitting an issue make sure you have:

[x] At least skimmed through README and most notably FAQ and BUGS sections
[x] Searched the bugtracker for similar issues including closed ones

What is the purpose of your issue?

[x] Bug report (encountered problems with youtube-dl)
[ ] Site support request (request for adding support for a new site)
[ ] Feature request (request for a new functionality)
[ ] Question
[ ] Other

Description of your issue, suggested solution and other information
bash-4.3$ youtube-dl --verbose http://www.c8.fr/c8-divertissement/ms-touche-pas-a-mon-poste/pid6318-videos-integrales.html?vid=1427375
[debug] System config: []
[debug] User config: [u'-o', u'%(title)s.%(ext)s', u'--prefer-ffmpeg', u'--no-mtime']
[debug] Command-line args: [u'--verbose', u'http://www.c8.fr/c8-divertissement/ms-touche-pas-a-mon-poste/pid6318-videos-integrales.html?vid=1427375']
[debug] Encodings: locale UTF-8, fs UTF-8, out UTF-8, pref UTF-8
[debug] youtube-dl version 2016.12.09
[debug] Python version 2.7.6 - Linux-3.16.0-77-generic-x86_64-with-glibc2.4
[debug] exe versions: ffmpeg 3.2, rtmpdump 2.4
[debug] Proxy map: {}
[Canalplus] pid6318-videos-integrales: Downloading webpage
ERROR: Unable to extract video id; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; type  youtube-dl -U  to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
Traceback (most recent call last):
File "./bin/youtube-dl/youtube_dl/YoutubeDL.py", line 694, in extract_info
ie_result = ie.extract(url)
File "./bin/youtube-dl/youtube_dl/extractor/common.py", line 357, in extract
return self._real_extract(url)
File "./bin/youtube-dl/youtube_dl/extractor/canalplus.py", line 109, in _real_extract
webpage, 'video id', group='id')
File "./bin/youtube-dl/youtube_dl/extractor/common.py", line 660, in _search_regex
raise RegexNotFoundError('Unable to extract %s' % _name)
RegexNotFoundError: Unable to extract video id; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; type  youtube-dl -U  to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.

Same for me
youtube-dl --verbose -F http://www.c8.fr/c8-divertissement/pid8726-c8-le-woop-mission-grand-rex.html?vid=1426849 [debug] System config: [] [debug] User config: [u'-o', u'~/Downloads/%(title)s-%(id)s.%(ext)s', u'--netrc', u'--restrict-filenames'] [debug] Command-line args: [u'--verbose', u'-F', u'http://www.c8.fr/c8-divertissement/pid8726-c8-le-woop-mission-grand-rex.html?vid=1426849'] [debug] Encodings: locale UTF-8, fs utf-8, out UTF-8, pref UTF-8 [debug] youtube-dl version 2016.12.09 [debug] Python version 2.7.10 - Darwin-16.1.0-x86_64-i386-64bit [debug] exe versions: avconv 11.4, avprobe 11.4 [debug] Proxy map: {} [Canalplus] pid8726-c8-le-woop-mission-grand-rex: Downloading webpage ERROR: Unable to extract video id; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; type  youtube-dl -U  to update. Be sure to call youtube-dl with the --verbose flag and include its complete output. Traceback (most recent call last):   File "/usr/local/bin/youtube-dl/youtube_dl/YoutubeDL.py", line 694, in extract_info     ie_result = ie.extract(url)   File "/usr/local/bin/youtube-dl/youtube_dl/extractor/common.py", line 357, in extract     return self._real_extract(url)   File "/usr/local/bin/youtube-dl/youtube_dl/extractor/canalplus.py", line 109, in _real_extract     webpage, 'video id', group='id')   File "/usr/local/bin/youtube-dl/youtube_dl/extractor/common.py", line 660, in _search_regex     raise RegexNotFoundError('Unable to extract %s' % _name) RegexNotFoundError: Unable to extract video id; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; type  youtube-dl -U  to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.


Update Wikipedia metadata

This PR updates:

dataset card
metadata JSON

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint.

Once this last PR validated, I can take care of the integration of all the wikipedia update branch into master.


Improve grid stride GUI

🚀 Feature
I propose to update the Grid view dialog.

Motivation
The small dialog for modifying the Grid view is not user-friendly / self-explanatory. It is not obivous that changing stride from -1 to 1 changes the view order of images in the grid view.
Pitch
I propose to implement a pull-down where users can configure Top down and Buttom up to change the view order (grid stride).
Alternatives

Additional context
I'm working with napari 0.4.17

Stride allows for much more than just "bottom up" and "top down", though. How do you suggest to still allow stride of 2, for example?

I don't understand what grid_stride=2 does. Can you give an example where this appears useful?
grid_stride=-1:

grid_stride=1:

grid_stride=2:

@haesleinhuepf stride is step-size; it's from walking: people with a longer stride take longer steps and walk faster (and can be annoying in groups).
stride 1 means  one by one, stride 2 means you step over 1 to the next, so every other one, etc. Plus or minus indicates direction/order. This can be seen in your screenshots.
Is this more clear?
Is this maybe a documentation issue?

Is this maybe a documentation issue?

I think the user interface needs to be improved.

I guess I'm not clear where the issue lies and what we should change.
I think grid width and grid length are clear, right?
So then, the issue is with the stride parameter?
Given my explanation of stride above, does that help make it clear?
I get this can be tricky simply due to the nuance of the english language, so I just want to be clear on what the actual issue is.
Can we change the text provided by the ? to make it more clear what the effect of the parameters is?
Or is it that you'd prefer a different effect all together.

I guess I'm not clear where the issue lies and what we should change

I propose to have a pulldown where the user can choose the layer view direction "top-down" versus "bottom-up".
Furthermore, one could add a "group n layers" numeric field (where I don't see a real use-case for).
Last but not least, also "width=-1" is nonsense from a UX point of view. I propose to add an "autosize" checkbox that disabled the width numeric field if activated.

If a GUI is complicated to explain, you can explain it in the documentation, which makes it even more complicated to use. Or you simplify the interface. Think of how a new user sees that panel. How would it need to appear so that a newbie immediately know what it does? Let's focus our discussion on this aspect.

After reading the discussion I see the problem, but still do not have an idea for a better UI. It will be nice to have a draft (image) of the interface.

I agree that unless you already know what it doesn't it's not immediately intutive what the controls do. My remark was simply: we should not sacrifice behaviour for that.

Furthermore, one could add a "group n layers" numeric field (where I don't see a real use-case for).

There are several people who use it; for example, if you have a bunch of images each with their 2 own annotation layers, you can have them 3 by 3 in the layerlist and set a stride of 3, and you're good to go. A "group n layers" field could definitely work!

Last but not least, also "width=-1" is nonsense from a UX point of view. I propose to add an "autosize" checkbox that disables the width numeric field if activated.

So in the end yo'd have something like:

ordering dropdown: top-down/bottom-up
width field which can be disabled and set to autosize with a checkbox
same for height field
group [n] layers field

Seems reasonable to me!
By the way, @melonora and I are working on a redesign of the grid canvas over at #5348; please take a look at that @haesleinhuepf and let us know what you think! This is definitely the time to consider this kind of improvement as well.

I think in the short term the tooltips could be made nicer and maybe clarified.

Regarding reversing the order would adding a checkbox reverse order help be better and relatively easy to implement for the short term? In that case, we wouldn't allow stride to be -1 anymore. Might be more effort than it is worth but would bring more clarity without a tooltip.
I agree that a group [n] layers field would be more semantically correct than stride, which is taking a step of size n instead of grouping multiple layers together in the convolutional neural network lingo. For stride in the sense of taking a step of size n, I do not see a use case.
Regarding the use of group [n] layers, I think it would be good to consider whether this should have a value of type int or whether we would allow users to give a sequence of integers equal to the number of grid tiles. For example when showing 6 grid tiles and the user providing the sequence 2 4 1 5 5 6  the first tile would hold the first 2 image layers, the next tile the following 4 image layers, and so on. A use case would be to display a marker set corresponding to a particular cell type in one grid tile.

Regarding the use of group [n] layers, I think it would be good to consider whether this should have a value of type int or whether we would allow users to give a sequence of integers equal to the number of grid tiles. For example when showing 6 grid tiles and the user providing the sequence 2 4 1 5 5 6 the first tile would hold the first 2 image layers, the next tile the following 4 image layers, and so on. A use case would be to display a marker set corresponding to a particular cell type in one grid tile.

This is neat, but I think they are different enough that maybe we should consider splitting them in two mutually-exclusive options. Let's add it to the todo for the new grid mode :P


fix warcli down namespace

Issue
warcli down will throw an error such as
$ helm uninstall tank-0000
Error: uninstall: Release not loaded: tank-0000: release: not found

Solution
Adding the default namespace to the command seems to fix this.

ACK https://github.com/bitcoin-dev-project/warnet/pull/501/commits/900920e0f0b4a46e599a7d877cd9e12da88491d4


Basic demo

Description of changes made

Expanded GenerateTestsAction so that it extracts information about what is the first java class definition in the currently opened file in the IDE. The class FQN is given, which together with the currently hardcoded project build classpath for gradle projects target/classes is enough information to run evosuite and make it generate tests for the user's class.
Added a class that launches evosuite as a separate process with supplied parameters.
Added a configurable which determines the location of the evosuite jar that is used.

Added topic for publishing test generation results objects
Implemented deserialization and publishing of test generation results
Added project-level event listener for said topic that can be expanded

Some things are hardcoded and all of this relies on a custom build of evosuite which comes with this PR. Eventually the jar should be moved elsewhere with its own build process.

Integrated with #26

@lyuben-todorov Can you merge development into your branch? There are merge conflicts. Also, please review and fix Codana's warnings.

@martinmladenov merged and fixed


Should be OK for fragment program to not write when VK_ATTACHMENT_STORE_OP_DONT_CARE

I have a depth-only pass where the color attachment uses VK_ATTACHMENT_STORE_OP_DONT_CARE (and, probably not relevantly) VK_ATTACHMENT_LOAD_OP_DONT_CARE.
I noticed that the depth pass was not significantly faster than a subsequent pass that wrote to the color attachment, and after some experimentation found that I could speed it up by changing my fragment shader to not write a color value.  In other words, I replaced:
  layout(location = 0) out vec4 outColor;
  void main() {
    outColor = vec4(1.f, 1.f, 1.f, 1.f);
  }

... with:
  void main() {}

This resulted in the desired performance improvement (on the Mesa 13.0 Intel Vulkan driver, not that it matters).  However, the core validation layer complains with the error "Attachment 0 not written by fragment shader".
I looked in the 1.0.43 spec, and couldn't find the reason for this validation failure (in fact, I didn't see any language in sections 8.9 or 9.2 that requires the fragment shader to write to an attachment, regardless of the store-op specified by the render-pass).  As a result, I'm not sure if this is a validation bug, a spec bug, or whether my program is actually non-compliant with the intended interpretation of the spec.
If this validation error matches some wording in the spec, I suppose I have two choices:

file a performance bug against Mesa, reasoning that vkCreateGraphicsPipeline() should notice the VK_ATTACHMENT_STORE_OP_DONT_CARE and avoid writing to the attachment even though the fragment shader produces an output value.

file a bug against the spec, reasoning that a fragment shader shouldn't be required to write to an attachment with VK_ATTACHMENT_STORE_OP_DONT_CARE

@chrisforbes, should this be a warning instead of an error?

(until someone points out where the spec prohibits fragment shaders that don't write a value, I'll assume that it is legal not to)
This should not even be a warning, I believe, since it warns against perfectly reasonable usage scenarios. I mentioned one in the original bug report, where I improved performance by not wastefully writing an unused value to the color attachment.
Another scenario is using the stencil buffer to implement clipping in a 2D renderer: it may be useful to update the stencil buffer without touching the color attachment.  This second scenario doesn't assume VK_ATTACHMENT_STORE_OP_DONT_CARE, so maybe this bug should be renamed to "Should be OK for fragment program to not write to color attachment".

If you're doing a depth-only pass, why does the subpass include the color attachment at all?
Shouldn't interpret what you're doing as "not writing to color attachment" -- it's really "may write undefined junk to color attachment".

I think you're right about the behavior being undefined.  As you see above, I just filed an issue against the spec, using the stencil-clipping scenario to focus the discussion.
Re: why use a color attachment with a depth-only pass, let's just say "historical reasons"; the full answer is irrelevant.

@schwa423, if you're OK with it, we'd prefer to close this until the spec issue is resolved and we have a clear direction on what the layers should complain about, but I will leave it up to you.

Sure, that's fine.  Thanks for helping to refine my understanding of this issue!

@mark-lunarg would be good to get all the interface matching stuff nailed down a bit more -- we define what matches are, but not the scope of the misbehavior if a mismatch exists.
I don't have the spare cycles to drive the spec side.


Automated Freelancing Service - 1 - 1

Link to the milestone and objectives table.
https://github.com/thenewboston-developers/Projects/issues/178
Detailed log of all completed objectives including valid proof of work.
Discord link: https://discord.gg/E6q48kKeVC
Link to code: https://github.com/Kycermann/tnb-freelance

#
Objective
Evidence

1
Set up Discord server
https://discord.gg/E6q48kKeVC

2
Terms & Conditions
In Discord #terms-of-service

3
Freelancer agreement & recruit 10+ freelancers
In Discord / #terms-of-service

4
Set up Discord bot code
Bot is online in Discord

5
/ticket
Try it

6
Claim a ticket (button)
Try it as a freelancer

7
/invoice
Try it as a freelancer

8
Sending / receiving TNBC
Invoices will be marked as paid, coins are sent on /close

9
/set_address
Try it and make an invoice

10
/close release and /close refund
Try it

Project Wallet
f1decb80339a4bb6c089b77cbac553e23a6ca86b0cfc64adb8c8eb8f8b57d815

Approved for 50k TNBC.


Using OpenPCDet with your own data

Hi, I'm new to 3D object detection and I discovered OpenPCDet a few days ago, it really caught my attention.
I tried to use it with other LiDAR point clouds but I can't see how should I proceed. I want to use an already trained model, such as PV-RCNN, trained with the KITTY dataset, and test it on my own point clouds ( .npy files) to detect the vehicles and the pedestrians.
At first I thought using demo.py on my files would work, but although I can visualize my files with it, it does not detect anything in my point clouds, even though some cars for example should be easy to detect in comparison to some objects demo.py detects in the KITTY testing dataset. But maybe demo.py only works with the KITTI dataset I trained the model with?
I tried to work with the custom_dataset document, but it seems to be adressed to people who want to train a model with custom datasets, not only test on it.
Could anyone give me some advices on how to proceed? How do I make demo.py detect objects in my point clouds?

Update
I managed to use demo.py to detect cars in my point cloud. I run the command:python demo.py --cfg_file cfgs/custom_models/second.yaml    --ckpt ../checkpoints/pv_rcnn_8369.pth    --data_path ../data/custom/points/my_data.npy
The custom_models/second.yaml config file is the only one that works with my data, if I use custom_models/pv_rcnn.yaml or kitty_models/pv_rcnn.yaml I will get the visualization but cars won't be detected.
The detection isn't perfect though. Half of my cars aren't detected, and for the cars detected there are multiple detection boxes on them.
I don't know if I can correct this by modifying config parameters or if it's only linked to the model used.

Some points which I faced which might help:

LiDAR has a large domain gap between sensors. A network trained on KITTI (Velodyne 64) will perform far worse when infering on out-of-domain data such from an Ouster OS1-64.
Make sure to normalize your remission in range 0..1
Pointcloud Range which have multiple causes:

KITTI dataset configuration sets the minimum x-range to 0, meaning only half the point cloud is infered on (visualized in this issue). You might need to adjust the pointcloud range in the dataset .yaml
Adjusting the pointcloud range can cause Issues, degrading the inference results of a pretrained network, as effectively now it sees double the information. I found much better results by infering twice, rotating the pointcloud by 180° for the second inference.
Use a network from a model pretrained on a different dataset, supporting 360°, such as NuScenes.

I  have faced the same issues before. As @L-Reichardt  mentioned, Normalization and changing the range help, but the accuracy of detection remains generally very low. I have worked with the Ouster OS1-64, and the intensity values are in 16-bit format. Normalizing these values to the range 0-1 causes a significant degradation in the quality of the point cloud.
Some people suggest using a pretrained model with  zero intensity values instead.
Another option is to retrain the model on your dataset.


Reformat screen output for sync mode submission and fix wait flag

What changes are proposed in this pull request?

Reformat screen output for sync mode submission, updated unit tests on distributed commands.
a. Update getCmdStatusDetailed rpc with additional file path information.
b. Extract complete and failed file information on the client side.
Fix wait flag.
Support failed file processing for DistCp command/Migrate operation.
Add OperationType for CmdStatus.

Output format:
Sync Mode Example Output:
“Submitted successfully, jobControlId =<PHONE_NUMBER>729
Waiting for the command to finish ...
Finished running the command, jobControlId =<PHONE_NUMBER>729
Get command status information below:
Successfully loaded path $path1
Successfully loaded path $path2
…
Total completed file count is $completed, failed file count is $failed
Here are failed files: 					(in case when there are failed files)
/$failed_dir/$failed_file1
…
Check out $csv_file for full list of failed files.”
Async Mode Example Output:
“Entering async submission mode.
Submitted distLoad job successfully, jobControlId =<PHONE_NUMBER>503”

could you put in the description what's the new output looks like? both in success and failure scenario

could you attach a screenshot of command output?

@jja725 @yuzhu Here is a doc for the new and old feature example comparison https://docs.google.com/document/d/1G6dFOeFTR4m2L9cSZVUFzIHrSfoEKN4G-5FwsCr2MIo/edit

Async submission and use getCmdStatus to check status (here is a case for both success and failure):

Load a folder which is already loaded

Is there a screenshot for partial failure? you can try to load the directory and delete files in UFS without metadata sync so we have blockmeta exception while loading.

Load a folder which is already loaded

and what would happen if there's partially loaded in a folder?

Load a folder which is already loaded

and what would happen if there's partially loaded in a folder?

Thanks for the comment, synced offline with @jja725 , will added a difference in the doc and this PR description part.

Working on an update to both getCmdStatus and stress bench, will change getCmdStatus to a job command, and update timer for stress bench.

alluxio-bot, merge this please


Usage via omnifunc

Hey!
Thank you for writing this plugin. I would like to use it with Neovim without any additional autocomplete plugins.
I've copied the configuration from the readme but I can't this plugin work with built-in autocomplete. I have a following on_attach function that connects omnifunc with lsp.omnifunc for the buffer:
local on_attach = function(client, bufnr)
    local map = vim.api.nvim_buf_set_keymap
    local ion = vim.api.nvim_buf_set_option
    local opts = { noremap = true }

    ion(bufnr, 'omnifunc', 'v:lua.vim.lsp.omnifunc')
    ion(bufnr, 'formatexpr', 'v:lua.vim.lsp.formatexpr()')

    -- Configure keybindings for LSP
    map(bufnr, 'n', 'C-y', '<Cmd>lua vim.lsp.buf.code_action()<CR>', opts)
    map(bufnr, 'n', 'g0', '<Cmd>lua vim.lsp.buf.document_symbol()<CR>', opts)
    map(bufnr, 'n', 'gf', '<Cmd>lua vim.lsp.buf.definition()<CR>', opts)
    map(bufnr, 'n', 'gi', '<Cmd>lua vim.lsp.buf.implementation()<CR>', opts)
    map(bufnr, 'n', 'gt', '<Cmd>lua vim.lsp.buf.type_definition()<CR>', opts)
    map(bufnr, 'n', 'gr', '<Cmd>lua vim.lsp.buf.references()<CR>', opts)
    map(bufnr, 'n', 'K', '<Cmd>lua vim.lsp.buf.hover()<CR>', opts)
end

Now, if I type valid emmet syntax in the HTML file (e.g. h1.center), and hit CTRL+x, CTRL+o, I see a following message in status line:
^X mode (^]^D^E^F^O^K^L^N^O^Ps^U^V^Y) Pattern not found

How can I force emmet to convert snippet to a proper HTML structure?

Hey! I don't really know much about omni completion since I just use nvim-cmp with LuaSnip (this language server just provides snippet completion).
I know that now we have a new built-in API to work with snippets https://github.com/neovim/neovim/pull/25301. Maybe you can check that out.
Hope that helps!

Thank you @olrtg , is there a way I can hook up this plugin to LuaSnip without nvim-cmp?

Sorry, I don't know. 😢 Maybe https://www.reddit.com/r/neovim/comments/rddugs/snipcomplua_luasnip_companion_plugin_for_omni/?


Only a subset of bookmarks shown when clicking on tags

I have 35 bookmarks for travel, and Raindrop seems to realize that:

However, when I click on the tag I'm only shown 28 bookmarks:

I know for a fact it's not showing everything.
This is the case for many of the tags.

Most of my tags aren't showing any results at all.   It seems like the search index or something might be broken.

Same issue. Seven out of eight results for existing bookmarks simply refuse to appear in the search results.

Hi guys, this issue is pretty much a duplicate of #113 and I believe it's being taken care.
We basically just have to wait for one more day or two.
FYI: https://nitter.net/xeraa/status/1736019592466637303

Disaster happen with our search index. We hosted our search engine on https://github.com/elastic cloud. They just deleted our entire account.
Do not worry, all data is safe. I just need to rebuild search index on a different hosting provider. But this require few days to complete unfortunately

70% is complete, most likely tomorrow search index migration will be done

70% is complete, most likely tomorrow search index migration will be done

Thanks for letting us know!

Looks like it is fixed. Thanks!

Fixed for me as well. Thanks very much Rustem.


optimization: 权限优化(close #313)

Codecov Report

Merging #437 (f141ee0) into V2.1.365-rc (df41da9) will decrease coverage by 0.56%.
The diff coverage is 50.00%.

@@               Coverage Diff               @@
##           V2.1.365-rc     #437      +/-   ##
===============================================
- Coverage        67.47%   66.90%   -0.57%
===============================================
  Files              249      255       +6
  Lines            20234    20580     +346
===============================================
+ Hits             13653    13770     +117
- Misses            6581     6810     +229

Impacted Files
Coverage Δ

apps/node_man/exceptions.py
100.00% <ø> (ø)

apps/node_man/views/plugin.py
51.72% <0.00%> (ø)

apps/iam/handlers/permission.py
21.01% <21.01%> (ø)

apps/node_man/handlers/permission.py
52.40% <23.07%> (-18.28%)
:arrow_down:

apps/node_man/views/cmdb.py
48.27% <23.07%> (-1.73%)
:arrow_down:

apps/node_man/views/job.py
51.16% <29.16%> (-11.34%)
:arrow_down:

apps/node_man/serializers/job.py
56.71% <38.09%> (-3.81%)
:arrow_down:

apps/iam/handlers/actions.py
51.72% <51.72%> (ø)

apps/node_man/views/host.py
67.85% <52.94%> (+25.00%)
:arrow_up:

apps/iam/handlers/resources.py
80.45% <80.45%> (ø)

... and 15 more

Continue to review full report at Codecov.

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


:feet: Add a Plan details page

Issue:
Currently we use the default console details page for Plans
We are missing:
For none running plans - edit plan
For running plans - view progress
The details page should have details, yaml, vms, mappings and hooks tabs
In running mode the details and vms tab will provider progress and debugging information
In edit mode the mappings and hooks will provide editing options
Does the backend support that ?
Allow editing of any none running plans, not just new ones - https://github.com/kubev2v/forklift-console-plugin/issues/141
Optional (covered by other issues):
in edit mode vms list will allow selecting vms to drop from plan - https://github.com/kubev2v/forklift-console-plugin/issues/128
If plan failed highlight vms that failed migration - https://github.com/kubev2v/forklift-console-plugin/issues/135

@ahadas , a question ?

Does the backend support that ?
Allow editing of any none running plans, not just new ones - https://github.com/kubev2v/forklift-console-plugin/issues/141

Ref: https://github.com/kubev2v/forklift-console-plugin/issues/757

https://github.com/kubev2v/forklift-console-plugin/pull/1003 - merged


Microsoft.VisualStudioCode.Insiders_v1.96.0 desktop

Microsoft.VisualStudioCode.Insiders_v1.96.0
Microsoft Reviewers: Open in CodeFlow

@wingetbot run

The pull request doesn't include any manifest files yaml.
This error means that this PR diff Master had no output. In other words, it's like a merge conflict.


Omit ambassador macros from docs

Would it be possible, maybe with an option, to have #[doc(hidden)] for ambassador implementation macros? We have quite a few and they clutter the documentation page (I assume the crate user should never know about them).

I assume the crate user should never know about them

This is not necessarily true, for public delegatable traits users can also use the macros to delegate them for there own structs, for private delegatable traits the macros will also be private and so they shouldn't get documented.


Application window displays nothing

After I updated my PC, the executable only displayed 3 lines of text before launching a blank application. I'm not even sure what is causing this. All I know is that the application stopped working after I updated a driver.

Yes, I meet the same problem.
It seems like a layer of black image is covering it.
You can operate it, but you can't get anything by eyes, without black.
That's interesting.

Upon further examination, I've come to that conclusion as well. All interfaces register inputs. The only issue is that the interfaces arent rendering.

I try to give out all information i can get in my issue.
you can compare with it.
The official developer has not replied to me yet


Playing cards Image Classification

Pull Request for DL-Simplified 💡
Issue Title : Playing Cards Image Classification

Info about the related issue (Aim of the project) : Create models to classify Playing cards based on images.
Name: Ojaswi Chopra
GitHub ID: ojaswichopra
Email ID<EMAIL_ADDRESS>**Idenitfy yourself: GSSOC Contributor

Closes: #745
Describe the add-ons or changes you've made 📃
I have created DL models on CNN as well as AlexNet architecture to classify Playing cards based on Images input.
Type of change ☑
What sort of change have you made:

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

How Has This Been Tested? ⚙
I have used various matrices like accuracy and losses check to verify the model.
Checklist: ☑

[x] My code follows the guidelines of this project.
[x] I have performed a self-review of my own code.
[x] I have commented my code, particularly wherever it was hard to understand.
[x] I have made corresponding changes to the documentation.
[x] My changes generate no new warnings.
[x] I have added things that prove my fix is effective or that my feature works.
[x] Any dependent changes have been merged and published in downstream modules.

@abhisheks008 I have made the changes. I have included an EfficientNet model which has an accuracy of 95%. Please review my PR.


async pipe

In GitLab by @lakhoune on May 23, 2020, 15:48
use asnyc pipe whenever we are only reading, but not modifying the data

In GitLab by @lakhoune on May 23, 2020, 18:34
mentioned in commit d79e809849378438a8070381ad7100d8aad2b0a1

In GitLab by @lakhoune on May 25, 2020, 16:33
closed


[NETBEANS-1074] Relicensing form files in webcommon cluster

Relicensing 54 modules listed under webcommon Cluster using AddFormLicense tool

I meant that not adding but changing. Sorry I did not make it clear enough...
OK, We should squash and merge then should change the commit message.
Thank you for your work, @thilina01 :)


Add tracking URI to MlflowLoggerHook

Describe the feature
If you are using MLFlow to log runs remotely, it would be nice to set the tracking server’s URI by calling mlflow.set_tracking_uri() in the MlflowLoggerHook method before_run(). This way, it would be needed to pass the tracking_uri as an argument to the init function.
Motivation
It is convenient when someone wants to log runs remotely, especially when working on a shared instance of MLFlow.
Related resources
https://www.mlflow.org/docs/latest/python_api/mlflow.html#mlflow.set_tracking_uri
Additional context
I can implement the feature and create a PR if needed.

@jraquelcs Great. you can go to mmcv to create a pr.


fix: fix wrong log in Windows debug script

What type of PR is this?
/kind bug

What this PR does / why we need it:
fix wrong log in Windows debug script
Which issue(s) this PR fixes:

Fixes #
Requirements:

[x] uses conventional commit messages

[ ] includes documentation
[ ] adds unit tests
[ ] tested upgrade from previous version

Special notes for your reviewer:
Release note:
none

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall First build on abelch/fix-debug-script-logs at 60.585%

Totals

Change from base Build<PHONE_NUMBER>:
60.6%

Covered Lines:
2570

Relevant Lines:
4242

💛  - Coveralls


ClusterConnectionManager sets nodesValues as null

Hi,
Following the examples given in the docs, I've initialized my cluster servers as follows:
Configurations.m_config.useClusterServers()
.setScanInterval(1000);
Configurations.m_config.useClusterServers()
.addNodeAddress("<IP_ADDRESS>:6379");
Now, I get a null pointer exception when I try to do Redisson.create using the above config. I've traced it down to the ClusterConnectionManager class, where the following is carried out:
String nodesValue = connection.clusterNodes().awaitUninterruptibly().getNow();
Nodes Value is always null, no matter which port i start redis server on (confirmed that it is running). I'd appreciate any guidance that you can give me as I'm stuck here and cannot proceed with my POC using Redisson otherwise.
BTW, this works perfectly:
Configurations.m_config.useSingleServer().setConnectionPoolSize(Configurations.CONNECTION_POOL_SIZE);
Configurations.m_config.useSingleServer().setAddress("<IP_ADDRESS>:6379");
Configurations.m_config.useSingleServer().setRetryAttempts(
Configurations.m_config.useSingleServer().setRetryInterval(200);
Configurations.m_redisson = Redisson.create(Configurations.m_config);

@savanpatel
You should create a redis cluster first. Please read this how-to about it

Thanks.


Update Headers

Fixes issue mentioned in #624 and also fixes/improves some other things I noticed.
To sum up the changes:

Removed "Profile" links from the Dashboard dropdown, as it becomes unnecessary when there already is "View Profile" in the profile dropdown. (both headers)
Renamed Dashboard to Library as it is only holding links to the libraries and recommendations and the Dashboard is generally accessible over the navbar brand. (both headers)
Removed the link from the Dashboard dropdown in the old header design to unify it with the new header, as dropdown links in Bootstrap can't open another page while being clicked. (basically just links to #)
Added Manga library link (old header)
Added "View Profile" and renamed "Edit Profile" to "Settings" in profile dropdown (old header)

As the old header is going to be dropped at some point these changes are just temporary solutions until everything is switched over to the new design and implemented.

LGTM! Definitely agree with the dashboard / library semantics.


Porn sites

please, can you add spankbang.com and redtube.com.br to porn hosts?

Hi Paolo @paulohpf.  spankbang.com is already blocked by our porn hosts.  The redtube.com.br domain would be new.
Ping @sinfonietta!

Thanks @StevenBlack , i saw spankbang is blocked with www. but the site open without www. and br.spankbang.com, i think it's better block the with "spankbang.com" so it blocks all spankbang's variants

Hosts files don't work like that, Paulo @paulohpf.
Hosts files originate back to the very beginnings of the internet.  There are no wildcards in hosts files, and no generalizations.  Each domain and subdomains needs an explicit entry.

@StevenBlack i undestand, thanks for the explanation


create a roles property for a user that connects to the roles table via user_role table.

so that we can easily query the roles for a given user without having to make a join or do any operations in python.

@pchtsp This should already be working with PR #78 . UserModel has the following property:
user_roles = db.relationship("UserRoleModel", cascade="all,delete", backref="users")
So if we have a user object we can get the list of its assigned roles (objects) doing: user.user_roles, if we want to get the id of any role we can do: user.user_roles[#].role_id, if we want to get the name of the roles: user.user_roles[#].role.name.
I guess that we could improve this with a @property method so that we get information in the format that we want, sso we could have something like this:
    @property
    def roles(self):
        return {r.role.id: r.role.name for r in self.user_roles}

So that we can just use user.roles to get a dict of the role id and the role name?

In this line, what the roles property should give back should aligned with what we use in Auth.get_permission_for_request(), so that the roles of the user can be check against the permissions that the roles have on each endpoint/action.


RESTful web API in Node.js using Postgres SQL and Express

Article checklist
NOTE: (Please ensure that you have only one open issue + linked pull request at a time. This will ensure that we complete the article in a timely manner from inception to publishing.)
Preliminary Checks - Formatting and Structure

[x] Does your article follow any of the suggested structure formats? - see example formats
[x] Is your article properly formatted in Markdown? - see Github Markdown guide
[x] Have you used the correct folder and file structure? - see Contribution Guidelines
[x] Is your article over 750 words? - Tool: Wordcounter.net
[x] Have you used our preferred heading structure? - H3 (###) and up
[x] Does your article provide enough value and detail about your topic? - Articles should be clear, accurate, and fully explained.
[x] Can your article be understood by beginners? - Assume the audience is smart but has no prior exposure to the common terminology in your article.
[x] Have you included a hero image that is 600x400 pixels and have the copyright to use it? - Tools: Pixlr Image Editor for resizing and Unsplash for Creative Commons images
[x] In your PR - add a comment that states "This fixes #(enter your Idea Content Form #)" to link and close your Idea Content (issue) when the PR is merged.

Grammar & plagiarism checks

[x] Have you spellchecked and grammar checked your article? - Tools: Write&Improve - ProWritingAid -  Grammarly
[x] Have you placed your article through a 3rd party plagiarism checker? We suggest using Quetext, this tool is free and has a daily limit. We typically accept articles with 10% or less.
[x] Have you checked your article for readability? - Tool: Hemmingway
[x] Have you added sources for quotes and images that aren't yours?

Technical checks

[x] Are your code snippets properly formatted for syntax highlighting - see Syntax guide

Contribution guidelines
For first-time contributors and for more details, see Contributing Guidelines
fixes #866

@hectorkambow, this article is past 10% by a small margin, (the recommended Plagiarism score). I believe there are some boilerplate codes, which can't be changed. i.e creating a simple Express server. The EJS code blocks contain bootstrap classes and codes, which cannot be changed for the bootstrap to take effect. The reviewer may confirm that if need be. Thank you.

@hectorkambow, this article is past 10% by a small margin, (the recommended Plagiarism score). I believe there are some boilerplate codes, which can't be changed. i.e creating a simple Express server. The EJS code blocks contain Bootstrap classes and codes, which cannot be changed for the Bootstrap to take effect. The reviewer may confirm that if need be. Thank you.

Thank you for the heads up @kimkimani  - if its some boilerplate code that can not be changed - that should be fine 👍
cc @WanjaMIKE

plagiarism check done

@kimkimani could you check the numbering in this section ### Setting up the views. I see several statements with no 1.

Nice article @kimkimani I have learned a lot about node.js. You hosted the node.js web api locally. Maybe, next time you could show us how to host it on section.io node server. Cheer!


fix slow ztunnel uninstall for post submit jobs

Please provide a description of this PR:
potential post submit test failure fix for https://prow.istio.io/view/gs/istio-prow/logs/integ-k8s-124_istio_postsubmit/1735702436804300800
follow up to https://github.com/istio/istio/pull/48168
To help us figure out who should review this PR, please put an X in all the areas that this PR affects.

[ X ] Ambient
[ ] Configuration Infrastructure
[ ] Docs
[ ] Dual Stack
[ ] Installation
[ ] Networking
[ ] Performance and Scalability
[ ] Policies and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure

Please check any characteristics that apply to this pull request.

[ ] Does not have any user-facing changes. This may include CLI changes, API changes, behavior changes, performance improvements, etc.

@GregHanson: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

release-notes_istio
a3503e7ef7bca22454bea48ba3a69abfa6781794
link
true
/test release-notes

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

/test release-notes

putting a do-not-merge since I'm still seeing flakes in my local tests

@GregHanson: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

lint_istio
7acb66a5f8413314d68c3018106b8dae615458ca
link
true
/test lint

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

@howardjohn PTAL

resolves https://github.com/istio/istio/issues/48426

@GregHanson: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

lint_istio
af972dc1ada927392ec1e6cd4e0714df8aaa2441
link
true
/test lint

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

@GregHanson: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

lint_istio
af972dc1ada927392ec1e6cd4e0714df8aaa2441
link
true
/test lint

gencheck_istio
af972dc1ada927392ec1e6cd4e0714df8aaa2441
link
true
/test gencheck

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

@GregHanson: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-ambient_istio
113329dc6d0df8f74db0241a1a335d8420140b89
link
unknown
/test integ-ambient

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

/test integ-ambient

ambient integ test failure related to https://github.com/istio/istio/issues/48508


Client Extensions Destroy Typescript Compilation Performance (and Intellisense)

Bug description
Adding simple client extensions blows up check time reported in tsc --extendedDiagnostics on a basic project from 0.12s to 1.79s, destroying intellisense performance.
Here's the client with extensions:
  const p = new RawPrismaClient({
    datasources: {
      db: {
        url: env.DATABASE_URL ?? "", // This will be undefined during builds
      },
    },
    log:
      (env.NODE_ENV === "development" ? ["error", "warn"] : ["error"]) as Array<Prisma.LogLevel>,
  }).$extends({
    name: "Extensions",
    result: {
      user: {
        realName_DANGEROUS_DO_NOT_USE: { // the users real name, should never be used unless you're an admin and know what you're doing
          needs: { name: true},
          compute(user) {
            return user.name
          }
        },
        name: { // the name that should be used throughout. It will correctly be the real name or the anonymous name based on the user's settings
          needs: { name: true, email: true, anonymous: true, id: true },
          compute(user) {
            const anonymousName = makeAnonymousName(user.id);
            return user.anonymous
              ? anonymousName
              : user.name ?? user.email?.split("@")[0] ?? anonymousName;
          }
        },
        anonymousName: { // should only be used if you really want an anonymous name even if they are not anonymous. Like with comments on the blog
          needs: { id: true },
          compute(user) {
            return makeAnonymousName(user.id);
          }
        }
      }
    }
  });

@typescript/analyze-trace then shows a hotspot (doesn't exist when client extensions aren't present)
Hot Spots
└─ Check file ********** /apps/worker/worker.ts (1334ms)
   └─ Check variable declaration from (line 28, char 7) to (line 40, char 2) (1313ms)
      └─ Compare types 22909 and 109 (1301ms)
         └─ Compare types 22527 and 415 (1301ms)
            └─ Compare types 22527 and 359 (1130ms)
               └─ Compare types 22520 and 359 (1130ms)
                  ├─ {"id":22520,"kind":"AnonymousType","location":{"path":"*********** client/runtime/library.d.ts","line":876,"char":5}}
                  └─ {"id":359,"kind":"AnonymousType","location":{"path":"*********** client/runtime/library.d.ts","line":876,"char":5}}

Happy to share schemas and/or sponsor a fix.
How to reproduce
Add client extensions to a project with a few dozen models.
Expected behavior
No response
Prisma information
Happy to share privately.
Environment & setup
Mac
tsc version 5.1.3
prisma 5.10.2
Prisma Version
prisma                  : 5.10.2
@prisma/client          : 5.10.2
Computed binaryTarget   : darwin-arm64
Operating System        : darwin
Architecture            : arm64
Node.js                 : v20.9.0
Query Engine (Node-API) : libquery-engine 5a9203d0590c951969e85a7d07215503f4672eb9 (at<EMAIL_ADDRESS>Schema Engine           : schema-engine-cli 5a9203d0590c951969e85a7d07215503f4672eb9 (at node_modules/@prisma/engines/schema-engine-darwin-arm64)
Schema Wasm             : @prisma/prisma-schema-wasm 5.10.0-34.5a9203d0590c951969e85a7d07215503f4672eb9
Default Engines Hash    : 5a9203d0590c951969e85a7d07215503f4672eb9
Studio                  : 0.499.0

@iamnafets Thanks for the issue. I'm curious to know more about your setup here, since I saw you mentioned that you were "Happy to share privately.", please email schemas at prisma.io.
Because before trying to fix this, we would first need to reproduce it, so anything that would help to reproduce it easily is very welcome, like a minimal reproduction repo for example, because it's likely related to your specific project, and could be hard to reproduce without it.

Just curious, did you try other TypeScript versions and observed the same results?

Hey @iamnafets  ,
Did you get a chance to have a look at my colleagues previous comment or send the schema to the email address they mention? It'd be helpful for us to move your issue forward.
Without further information, we'll have to close this issue. Thank you 🙏

Hi @iamnafets, we're closing this issue as we didn't receive the reproduction we needed to investigate this.
Please leave a comment whenever you manage to provide such reproduction, so we can re-open this issue. Thanks!


storage.md

Typo

/assign @jlewi

Thanks @sublimotion! It seems that another contributor has submitted the same fix in PR https://github.com/kubeflow/website/pull/1867. Since that one came first, we'll give that contributor an opportunity to finish the CLA process. If there's no further activity on that PR in a day or two, we'll merge this PR.
Assigning a hold to give the earlier contributor time:
/hold

/ok-to-test

/hold cancel
/lgtm
/approve
Thanks!


add HTML Boiler-Plate for front-end

Added the started files for the front end

Thanks for your participation


Split Asserts and add comment

With the introduction of PyTeal Assert comments, SourceMap and tools like Beaker Clients it is very convenient to split Assets to address single failure/error conditions in order to retrieve a more explicit and informative root cause of a failure.
Describe the solution you'd like
Currently the asserts on regular transfer preconditions looks like:
# Asset Regular Transfer Preconditions
Assert(
    Not(asset_frozen),
    Not(asset_sender_frozen),
    Not(asset_receiver_frozen),
    is_current_smart_asa_id,
),

Describe alternatives you've considered
A more informative and useful assertions would be:
# Asset Regular Transfer Preconditions
Assert(Not(asset_frozen), comment="Asset is global frozen"),
Assert(Not(asset_sender_frozen), comment="Asset sender is frozen"),
Assert(Not(asset_receiver_frozen), comment="Asset receiver is frozen"),
Assert(is_current_smart_asa_id, comment="Wrong Smart ASA ID"),

Addressed in https://github.com/algorandlabs/smart-asa/pull/33


How to get all token balances for an account?

How to get all token balances for an account?  getCurrencyBalance returns the balance for 1 token, but how can I know how many and  which distinct tokens to query?

The EOS JSON RPC doesn't provide a way to do this


Gtestify credentials_test

I tried this before with https://github.com/grpc/grpc/pull/27556 and ran into strange failures on OSX. Not sure whether this would be lucky this time but please to make sure this won't break some of OSX CI tests. Fingers crossed!


FR: Code snippets pop up in less constrained modal window

Feature request: Since docker CLI spits out some pretty wide output, it would be nice if code snippets could be "popped out" into a modal popup that takes up the whole viewport width and was easily closeable (click outside, click X, hit ESC).
At Kubernetes I used Sweet Alert for this and it was fairly easy/pretty.
https://limonte.github.io/sweetalert2/

A good example is: https://docs.docker.com/engine/reference/commandline/stack_ps/ which trunks (visually) the result of the commands:

FWIW, my own desire is to be able to read the whole output without having to click on anything.  I have a wide screen, and I'd like to benefit from it to see the output of the commands exactly as is the case with my terminal.  I am not asking for any kind of change for the text body (which is wrapped), I am asking for the raw output of commands to use the whole width of my screen.
IMHO, it should be the default, and should not require any mouse action and pop-up.

Closing this ticket due to its age, and the impending refactor. If you think this is in error, feel free to reopen. Thanks!


Memory leak of create_string_buffer

create_string_buffer in ParcelThread is leaking, due to the loop in Server.listen.  The instance is created in a while loop that never exits, and create_string_buffer counts on being freed by the garbage collector.  But since the loop never exits, the reference is never released.

buffer is no longer allocated here.


pritunl-ssh: 1.0.1674.4 -> 1.0.2435.24

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/pritunl/pritunl-zero-client/releases.
meta.description for pritunl-ssh is: "Pritunl Zero SSH client"
meta.homepage for pritunl-ssh is: "https://github.com/pritunl/pritunl-zero-client"
meta.changelog for pritunl-ssh is: ""
Updates performed

Version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 1.0.2435.24 with grep in /nix/store/8dahzpkci586qigfr1nf0gp670is3y0y-pritunl-ssh-1.0.2435.24
found 1.0.2435.24 in filename of file in /nix/store/8dahzpkci586qigfr1nf0gp670is3y0y-pritunl-ssh-1.0.2435.24

Rebuild report (if merged into master) (click to expand)

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
pritunl-ssh

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/8dahzpkci586qigfr1nf0gp670is3y0y-pritunl-ssh-1.0.2435.24 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A pritunl-ssh https://github.com/r-ryantm/nixpkgs/archive/0ebc83941c89b14463a888ec31f35c18a9d29128.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/8dahzpkci586qigfr1nf0gp670is3y0y-pritunl-ssh-1.0.2435.24
ls -la /nix/store/8dahzpkci586qigfr1nf0gp670is3y0y-pritunl-ssh-1.0.2435.24/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

pritunl-ssh

Maintainer pings
cc @Thunderbottom for testing.

Result of nixpkgs-review pr 183743 run on x86_64-linux 1

1 package built:

pritunl-ssh


Tweak behaviour of localmodeltypes to resolve #356

resolves #356

It seems the julia 1.0 fail is b/s it is still seeing the yanked version 0.3.9 of MLJModelInterface.
Yes this has been confirmed; yank not added till Julia 1.1

It seems the julia 1.0 fail is b/s it is still seeing the yanked version 0.3.9 of MLJModelInterface.
Yes this has been confirmed; yank not added till Julia 1.1

Codecov Report

Merging #357 (161f181) into dev (fa8b6b3) will decrease coverage by 1.04%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##              dev     #357      +/-   ##
==========================================
- Coverage   79.41%   78.36%   -1.05%
==========================================
  Files          11       11
  Lines         855      846       -9
==========================================
- Hits          679      663      -16
- Misses        176      183       +7

Impacted Files
Coverage Δ

src/model_search.jl
77.14% <ø> (-0.64%)
:arrow_down:

src/metadata.jl
79.22% <100.00%> (-0.78%)
:arrow_down:

src/builtins/Transformers.jl
92.85% <0.00%> (-1.86%)
:arrow_down:

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 fa8b6b3...161f181. Read the comment docs.

Codecov Report

Merging #357 (161f181) into dev (fa8b6b3) will decrease coverage by 1.04%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##              dev     #357      +/-   ##
==========================================
- Coverage   79.41%   78.36%   -1.05%
==========================================
  Files          11       11
  Lines         855      846       -9
==========================================
- Hits          679      663      -16
- Misses        176      183       +7

Impacted Files
Coverage Δ

src/model_search.jl
77.14% <ø> (-0.64%)
:arrow_down:

src/metadata.jl
79.22% <100.00%> (-0.78%)
:arrow_down:

src/builtins/Transformers.jl
92.85% <0.00%> (-1.86%)
:arrow_down:

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 fa8b6b3...161f181. Read the comment docs.


Update error_slos.md

The number is incorrect for the total of 'Apdex Frustrated'.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

:tada: This PR is included in version 1.4.6 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


ontap-nas-economy driver validation failed

o	https://kb.netapp.com/app/answers/answer_view/a_id/1096347
Here’s the config I updated the backend with.  The logs from the trident pod said it successfully updated the backend, but the validation check in your CVE article does not pass  - the new backend json doesn’t mention qtree prunes (attached).
After applying the fix to the driver file, validation fails.  Is there another way to validate that the backend has the qtreePruneFlexvolsPeriod value set?
{
"version": 1,
"storageDriverName": "ontap-nas-economy",
"managementLIF": "<IP_ADDRESS>",
"svm": "vs_BFCDVT2VSCONA01",
"dataLIF": "<IP_ADDRESS>",
"username": "openshift",
"password": "",
"storagePrefix": "vf",
"qtreePruneFlexvolsPeriod": "157788000",
"defaults": {
"spaceReserve": "none",
"exportPolicy": "ep_openshift_bdv01",
"snapshotPolicy": "openshift",
"snapshotReserve": "20",
"snapshotDir" : "true"
}
}

Hello, @techie11.  I tried your backend definition file with just enough changes for my SVM, and it worked fine.  Assuming you have Trident 19.10 or later, you should be able to use tridentctl get backend -o yaml to see the value of qtreePruneFlexvolsPeriod.  Alternatively, you can install Trident with the --debug switch and watch the logs in the Trident controller pod (trident-main container) to ensure there is no mention of FlexVol pruning when you update the backend.  The qtreePruneFlexvolsPeriod workaround is really for Trident 19.07 or earlier; later versions of Trident do no Flexvol pruning at all.

I'm running v18.10

@techie11  OK, then until you upgrade, I think you will have to inspect the debug logs to be comfortable that the quota resize housekeeping task is running periodically, but the flexvol pruning task is not.

@techie11 we're closing this issue with the recommendation to upgrade to a newer version of Trident.


Feature Request: breadcrumb

Environment

Python version:
NetBox version:

Proposed Functionality
It maybe useful to intagrate breadcrumb.

Use Case
Browse faster between prefixes

Database Changes

External Dependencies

Closing this out as no effort was put into describing the proposed feature.


Modifications to RT7.2 -BGP Policy Community Set

1 Added deviation community_invert_any_unsupported
2 Added community matchSetOptions

Pull Request Functional Test Report for #3356 / 01cffa9e7ee38ab2993682adf6fca98be1585e4b
Virtual Devices

Device
Test
Test Documentation
Job
Raw Log

Arista cEOS

RT-7.2: BGP Policy Community Set

Cisco 8000E

RT-7.2: BGP Policy Community Set

Cisco XRd

RT-7.2: BGP Policy Community Set

Juniper ncPTX

RT-7.2: BGP Policy Community Set

Nokia SR Linux

RT-7.2: BGP Policy Community Set

Openconfig Lemming

RT-7.2: BGP Policy Community Set

Hardware Devices

Device
Test
Test Documentation
Raw Log

Arista 7808

RT-7.2: BGP Policy Community Set

Cisco 8808

RT-7.2: BGP Policy Community Set

Juniper PTX10008

RT-7.2: BGP Policy Community Set

Nokia 7250 IXR-10e

RT-7.2: BGP Policy Community Set

Help

Hi,
Can we resolve the conflicts for this PR?
-Ram

Pull Request Test Coverage Report for Build<PHONE_NUMBER>1
Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 55.252%

Totals

Change from base Build<PHONE_NUMBER>5:
0.0%

Covered Lines:
1983

Relevant Lines:
3589

💛  - Coveralls


Fix loading of article in editor page

References #15
This change updates to the router to use a single Editor route entry with an optional parameter (/editor/:slug?). It also corrects a typo in the nextProps.match.params access. These two changes restored the 'article editing' functionality for my locally running instance.
Please let me know if there's anything that needs changing.

Should now also address #16.
I updated editorStore.setArticleSlug to reset the form state if a new article slug is set (this could also be moved to loadInitialData as well or just be a direct call in Editor), and changed componentWillReceiveProps to componentDidUpdate since the React Docs indicate that this is a good place to kick off the network requests. I can also revise this if we want the synchronous portion of setting the article slug in componentWillReceiveProps if desired.

Thanks @cfilby!


Error when creating segm.npz from .tif

... I encountered a new issue with a 3D masks.tiff i segmented directly in Cellpose and converted using your utility to  _segm.npz.
I imported the _segm.npz file into the GUI, tried to save it and received the following issue:
==============================
Traceback (most recent call last):
File "D:\Programme\Anaconda3\envs\acdc\lib\site-packages\cellacdc\gui.py", line 1122, in run
acdc_df = self.addMetrics_acdc_df(
File "D:\Programme\Anaconda3\envs\acdc\lib\site-packages\cellacdc\gui.py", line 664, in addMetrics_acdc_df
metrics_values[bkgr_key][i] = np.quantile(
File "<array_function internals>", line 180, in quantile
File "D:\Programme\Anaconda3\envs\acdc\lib\site-packages\numpy\lib\function_base.py", line 4412, in quantile
return _quantile_unchecked(
File "D:\Programme\Anaconda3\envs\acdc\lib\site-packages\numpy\lib\function_base.py", line 4424, in _quantile_unchecked
r, k = _ureduce(a,
File "D:\Programme\Anaconda3\envs\acdc\lib\site-packages\numpy\lib\function_base.py", line 3725, in _ureduce
r = func(a, **kwargs)
File "D:\Programme\Anaconda3\envs\acdc\lib\site-packages\numpy\lib\function_base.py", line 4593, in _quantile_ureduce_func
result = _quantile(arr,
File "D:\Programme\Anaconda3\envs\acdc\lib\site-packages\numpy\lib\function_base.py", line 4704, in _quantile
previous = np.take(arr, previous_indexes, axis=DATA_AXIS)
File "<array_function internals>", line 180, in take
File "D:\Programme\Anaconda3\envs\acdc\lib\site-packages\numpy\core\fromnumeric.py", line 190, in take
return _wrapfunc(a, 'take', indices, axis=axis, out=out, mode=mode)
File "D:\Programme\Anaconda3\envs\acdc\lib\site-packages\numpy\core\fromnumeric.py", line 57, in _wrapfunc
return bound(*args, **kwds)
IndexError: cannot do a non-empty take from an empty axes.

Should i send you the 3D file?
Thanks and best
Mario

Originally posted by @dfgdgdfgd in https://github.com/SchmollerLab/Cell_ACDC/issues/169#issuecomment-1289565595

Closing because created by mistake


Update yarn packages

Who is this PR for?
Developers + codebase health.
What problem does this PR fix?
The entire spec suite won't run because of one missing JS dependency: https://github.com/studentinsights/studentinsights/pull/1742#issuecomment-393362468.
What does this PR do?
Runs yarn upgrade and commits upgrade results.

Clicked around the site in local development mode to triple-check for any breaking changes, didn't find anything and the tests are ✅.


[SUPPORT] Why HUDI ConsistentBucketClusteringExecutionStrategy not supported by flink engine?

Upon reviewing the source code, it is evident that the ConsistentBucketClusteringExecutionStrategy is only implemented for the Spark engine.

Because it's hard for Flink to support both compaction and clustering execution in the same pipeline, current Flink only supports the clustering plan generation for consistnet hashing, a separate clustering job is needed for execution.

Because it's hard for Flink to support both compaction and clustering execution in the same pipeline, current Flink only supports the clustering plan generation for consistnet hashing, a separate clustering job is needed for execution.

However, it seems that org.apache.hudi.sink.clustering.HoodieFlinkClusteringJob does not support ConsistentBucketClusteringExecutionStrategy, which can only be specified with the Spark engine using org.apache.hudi.client.clustering.run.strategy.SparkConsistentBucketClusteringExecutionStrategy. This operation implies that HUDI requires two engines to complete the Consistent Bucket operation: the Flink engine to generate the plan, and the Spark engine to execute the plan.

I think so, @beyond1920 can you chim in for more insights?


Installation and test problems!

Hi，
I met some errors when I run two recipes from the Cookbook (in Linux). Before the test of recipes, the Anaconda and fatiando are installed under my account (not the root account) without any problem. I am fresh to python and fatiando, so would you like to help me  solve these errors?
The 1st recipe is  gravmag_2d_polygon_picker.py. The command and error message are given below:
   wy@wy Downloads]$ python gravmag_2d_polygon_picker.py
   Traceback (most recent call last):
    File "gravmag_2d_polygon_picker.py", line 5, in <module>
    from fatiando import utils, mesher
    ImportError: No module named fatiando

The second recipe is seismic_wavefd_scalar.py.   The corresponding message is here
[wy@wy Downloads]$ python seismic_wavefd_scalar.py
Traceback (most recent call last):
File "seismic_wavefd_scalar.py", line 10, in
from matplotlib import animation
ImportError: cannot import name animation
Next are some other basic information:
OS：Red Hat Enterprise Linux 6
（Linux wy 2.6.32-358.el6.i686 #1 SMP Tue Jan 29 11:48:01 EST 2013 i686 i686 i386 GNU/Linux）
Version of Fatiando ：0.3
Python distribution：Anaconda
Python version：2.7
    Thank you !

Best wishes!

Hi @smallcaiyuan, I see that you've closed the issue. Were you able to resolve the problem?

@leouieda   I'm sorry, I don't know why is was closed. The title also was changed. The problem is not solved. Thank you!

@smallcaiyuan can you


Fix grammatical errors in 4.3.0.rst

Checklist:

[x] Securely signed commits
[ ] Component(s) with PHPDoc blocks, only if necessary or adds value
[ ] Unit testing, with >80% coverage
[x] User guide updated
[ ] Conforms to style guide

Thank you @paulbalandan


Correct version of @include_total_xtp_storage parameter

@stummsft : Thanks for your contribution! The author, @edmacauley, has been notified to review your proposed change.

@stummsft thanks for your edit!  can you change both the comment and the include file though? It would look something like this:
[!INCLUDEsssql17-md]

@stummsft : Thanks for your contribution! The author, @edmacauley, has been notified to review your proposed change.

@stummsft thanks!  #sign-off


Brainstorming Voting Fix

startVoting initializes this.votes with finalIdeas.length instead of ideaEvent.ideas.length

i missed that, will remove the pull request for now. Good job noticing this!


Public folder visible on the URL

Hi,
Started 2 fresh installs of Aksara 5.1.6 version (one in basic mode and other in developer mode) with the current CI version (4.5.5).
In both installs the /public/ folder appears on the URL.
Changing the 'ENVIRONMENT' setting has no effect.
I have a 5.1.1 version installed (with the 'ENVIRONMENT' setted to 'development') with CI 4.5.3 and the '/public/' folder don't appears on the URL...
Am I missing something?
TIA and keep the good work!!

You need to point your sub/domain to /path/to/aksaracms/public directly or follow this step instead: https://github.com/abydahana/aksara/discussions/439

Hi,
I'm in my local machine using Laragon (same as XAMPP) as development environment. The same Laragon on wich I run the older version working ok...
The CI's BaseURL config seems ok: "http://aksara-main.test/public/"
The routes seems ok, too.
So, it seems it's nothing related with your advices...
I did a fresh install of the 5.1.1 released version here at home (wich Composer downloaded the current CI 4.5.5) and the "/public/" appears on the URL too.
As I said, the ok version (at work) runs on CI 4.5.3. Could be the CI version the reason of different behavior?
I'll do more tests on monday at work...
TIA. Best regards.

Hi,
Started 2 fresh installs of Aksara 5.1.6 version (one in basic mode and other in developer mode) with the current CI version (4.5.5). In both installs the /public/ folder appears on the URL. Changing the 'ENVIRONMENT' setting has no effect.
I have a 5.1.1 version installed (with the 'ENVIRONMENT' setted to 'development') with CI 4.5.3 and the '/public/' folder don't appears on the URL...
Am I missing something?
TIA and keep the good work!!

what's your server using? nginx, apacher, litespeed or others?

I tested both Apache and Nginx

Apache 2.4.59-win64-VS17
PHP 8.3.8-x64 [TS]
MySQL 8.4.0
I did a fresh install of 5.1.1 release, developer mode (without sample) and CI 4.5.5, here at work and the /public/ folder appears on the URL too...
I downloaded the 5.1.1 release, unziped it into an empty folder and ran composer install wich downloaded CI 4.5.5. When I open the new site and start the install process, the /public/ folder already appears.
The ok 5.1.1 (on CI 4.5.3) version was formerly a 5.0.6 version wich was updated to 5.1.0 and after to 5.1.1, by copying the new released files over the priors.
Also, the app Description don't appears on the footer of the ok version, while it does on the NOT OK version...
Later I'll try to do a fresh install forcing the CI 4.5.3 and see what happens...

More info:
On the CI's debugbar, I can see that BaseURL is setted to "http://aksara-main.test/public/" instead of "http://aksara-main.test".
Couldn't find where this '/public/' is appended to the $baseURL...

More info:
On the CI's debugbar, I can see that BaseURL is setted to "http://aksara-main.test/public/" instead of "http://aksara-main.test". Couldn't find where this '/public/' is appended to the $baseURL...

Could you please share your virtual host config?

This is the content created by Laragon on the hosts file:
<IP_ADDRESS>      aksara-511.test      #laragon magic!
<IP_ADDRESS>      aksara-main.test     #laragon magic!
<IP_ADDRESS>      aksaracms.test       #laragon magic!

This is the content created by Laragon on the hosts file:
<IP_ADDRESS> aksara-511.test #laragon magic! <IP_ADDRESS> aksara-main.test #laragon magic! <IP_ADDRESS> aksaracms.test #laragon magic!

i'm using laragon too, but not try on localhost, may you can use this
<VirtualHost *:80>
    ServerAdmin webmaster@localhost
    ServerName ahntest.net
    DocumentRoot /home/www/ahntest.net

    Alias /testberg /home/www/testberg
    <Directory "/home/www/testberg">
        Options +Indexes
        AllowOverride All
    </Directory>
</VirtualHost>

// source: https://serverfault.com/a/347549
hope this help you little.

This is the content created by Laragon on the hosts file:
<IP_ADDRESS> aksara-511.test #laragon magic! <IP_ADDRESS> aksara-main.test #laragon magic! <IP_ADDRESS> aksaracms.test #laragon magic!

i'm using laragon too, but not try on localhost, may you can use this
<VirtualHost *:80>
    ServerAdmin webmaster@localhost
    ServerName ahntest.net
    DocumentRoot /home/www/ahntest.net

    Alias /testberg /home/www/testberg
    <Directory "/home/www/testberg">
        Options +Indexes
        AllowOverride All
    </Directory>
</VirtualHost>

// source: https://serverfault.com/a/347549
hope this help you little.

Hi, please check the virtual host config under your nginx and make sure the "root" parameter is pointed to /public directly:

The final config should be like this:
server {
    listen 80;
    server_name aksara-main.test *.aksara-main.test;
    root "/path/to/aksaracms/public"; # LOOK AT THIS

    index index.html index.htm index.php;

    location / {
        try_files $uri $uri/ /index.php$is_args$args;
		autoindex on;
    }

    location ~ \.php$ {
        include snippets/fastcgi-php.conf;
        fastcgi_pass php_upstream;
        #fastcgi_pass unix:/run/php/php7.0-fpm.sock;
    }

    charset utf-8;

    location = /favicon.ico { access_log off; log_not_found off; }
    location = /robots.txt  { access_log off; log_not_found off; }
    location ~ /\.ht {
        deny all;
    }
}

# This file is auto-generated.
# If you want Laragon to respect your changes, just remove the [auto.] prefix
# If you want to use SSL, enable it at: Menu > Nginx > SSL > Enabled

You're using Laragon 5.0.0. Mine is 6.0.0.
Nginx is disabled in my Preferences. I use only Apache. Ever.
I know that Aksara don't needs the .env file. I use it on others CI projects, setting the BaseURL as I said and database credentials.
Opening the CI's DebugBar I can see that the BaseURL is setted without the '/public/' on the updated Aksara 5.1.1. But on the fresh installs the BaseURL is setted with the '/public/'.
The defined BASE_URL on the config.php seems ok.
So, somewhere, sometime, the public $baseURL variable is getting the '/public/' added to the end of the URL..

Thanks for your time with this issue... Hope we can find the answer to this mistery... :-)

Laragon is using Nginx by default. You can check the screenshot on my previous reply just to make sure the virtual host are created correctly.
I tested with Laragon also and had no issue.
And there's no .env required in Aksara's project, so I wonder why you put .env in yours 😁

Sir, we can choose nginx or apache as webservice ...

but this is very mistery ... can you downgrade your laragon version sir @FlavioSuarez only for testing...
i'm using laragon 4 but with apache and php newest.

Bingo!!! Found it!!!
Now I see what you both mean with

Could you please share your virtual host config?

<VirtualHost *:80>
    ServerAdmin webmaster@localhost
    ServerName ahntest.net
    DocumentRoot /home/www/ahntest.net

    Alias /testberg /home/www/testberg
    <Directory "/home/www/testberg">
        Options +Indexes
        AllowOverride All
    </Directory>
</VirtualHost>

I was looking for in the "hosts" file.
But right now I had an insight and found these settings on the Apache > sites-enabled > *.conf files
On the working site, the "DocumentRoot" and "Directory" have "/public" on the path.
On the NOT working site, they doesn't.
Then the 2nd insight was: The ok site was created by running a Composer installation, while in the not-ok sites I did a manual installation.
In the manual installation I first created a blank project on Laragon by going to Quick App > Blank (wich created the folder, the database and the .conf file without the "/public" on the "DocumentRoot" and "Directory" settings) and then I did the manual installation into this folder.
Tested right now doing a Composer installation and all seems ok again!!
Thank you so much for your help, guys!!
Re-starting my testing project from zero...
Keep the good work! This project is really awesome!

Great to know. Now it's clear that the main cause is the virtual host did not created a config like expected.

Yes.
The Laragon's Quick App > Blank don't know if has to add "/public" at the end...
So, the best advice is to allways use the Composer Installation when using Laragon...


Return 404 code on not found and use templates

404 code is now returned when word is not found
both html files now use a base template for uniform look

resolved conflict


Update Example

Once we have the least code working, we should update the examples so that people can try themselves.

Add the list of items we potentially need as examples -
ORAS API Usecases
The following usecase can help define the list of examples that a new developer should be able to refer.

Download Manifest
Download a Blob given the digest
Put Manifest
Create manifest with Annotation
Upload Blob
Upload Manifest with blob
Copy Artifact
Upload manifest with reference
Download reference manifest
Download blob of reference manifest
Copy reference
Copy artifact and references

Authentication tokens

Get token for operation with scopes.
Validate cross mount

Example Permutations

Auth required for pull/push
Insecure planHttp

Assigning this item to @qweeah.

Ack

@qweeah - can you include GetManifest in the examples.

@qweeah - can you include GetManifest in the examples.

@sajayantony I think it's covered by Example_pullByTag and Example_pullByDigest

@wangxiaoxuan273 Could you help sweeping all the scenarios and add examples for them?

Sure. Please assign this to me.

I just noticed that there is no item related to referrers in the example list.
In the following items, does artifact reference mean subject here? Or do we actually mean referrers?

Upload artifact reference manifest
Download artifact reference manifest
Download blob of artifact reference manifest
Copy reference
Copy artifact and references

The term reference seems to represent the artifact referencing the given manifest (which is a referrer of the given manifest) in ORAS Artifact Scenarios.  I'm confused by the terms we are using here.

ExampleRepository_Fetch_layer is an example of Download a Blob given the digest, so this item should be checked.

Closing as "HTTP Client Configuration" is tracked by #182 separately.


Bower package

Need register bower package

Please see https://github.com/blueimp/JavaScript-Canvas-to-Blob/commit/62b03949b9bb9c4da71ec38721abc0ca6c08c988


Inconsistencies within DefinePlugin output

Hi,
I've noticed following strange behavior.
Input file:
var gg = 5, isServer = (typeof window == 'undefined');

if (typeof window) {
  gg = 6;
}

if (!(typeof window)) {
  gg = 7;
}

if (typeof window === true) {
  gg = 8;
}

if (typeof window === false) {
  gg = 9;
}

if (isServer) {
  gg = 10;
}

if (!isServer) {
  gg = 11;
}

if (isServer === true) {
  gg = 12;
}

if (isServer === false) {
  gg = 13;
}

with this config:
new webpack.DefinePlugin({
    isServer: false,
    'typeof window': true
})

I get this output:
var gg = 5, isServer = (typeof window == 'undefined');

if (true) {
  gg = 6;
}

if (false) {
  gg = 7;
}

if (true) {
  gg = 8;
}

if (false) {
  gg = 9;
}

if (isServer) {
  gg = 10;
}

if (!isServer) {
  gg = 11;
}

if (isServer === true) {
  gg = 12;
}

if (isServer === false) {
  gg = 13;
}

– one instance of typeof window wasn't replaced.
with this config:
new webpack.DefinePlugin({
    isServer: false,
    'typeof window': '"object"'
})

I get this output:
var gg = 5, isServer = ("object" == 'undefined');

if (true) {
  gg = 6;
}

if (false) {
  gg = 7;
}

if ("object" === true) {
  gg = 8;
}

if ("object" === false) {
  gg = 9;
}

if (isServer) {
  gg = 10;
}

if (!isServer) {
  gg = 11;
}

if (isServer === true) {
  gg = 12;
}

if (isServer === false) {
  gg = 13;
}

– all instances of typeof window were replaced.
PS. In both cases no instances of isServer haven't been touched.

It doesn't make sense to define typeof window to true. typeof always returns a string.
It's correct that isServer is not replaced. It's not used a "free variable" (because of the var isServer). Only free variables are replaced.

@sokra I just experimented to see how replacement works, and this inconsistency stroke me as the odd one.
And by free variable, do you global ones, or not explicitly defined in the current context or something else? Is there a doc I can read more about free variables?
Giving existing example what would the best way (within webpack universe) to get that if (isServer) { branches to be removed from the bundle?
Thank you.

And by free variable, do you global ones, or not explicitly defined in the current context or something else? Is there a doc I can read more about free variables?

Free as in not global, local, or anything. If the free variables were not replaced, the code would crash (one way to put it).

Giving existing example what would the best way (within webpack universe) to get that if (isServer) { branches to be removed from the bundle?

I would do if (env === 'SERVER') or similar (could be process.env too if you like that convention).
Feel free to re-open at Stack Overflow for more answers.


Add ability to provide a mapper name in Env#read

refs #122
cc @aflatter

that would couple relation with mapper :( suddenly it would know about its existence

BTW I should mention a couple of things just to clarify:

rom.relations are exposed because of a lack of certain interfaces; eventually I would like to have some higher-level interfaces exposed by env so that you don't have to access relations directly. For instance I can easily see a separate interface for aggregations (max, min, count etc.)
Reader object is a top-level interface for reading defined relations via mappers. It is an enumerable object that only exposes publicly available relations and excludes native query DSLs or any other interfaces provided by the adapter layer

I have to admit this my little experiment and maybe this approach will turn out to be too strict and not flexible enough (being enforced to specify relations for every part of your system that needs data can be annoying in very simple applications). So this is something that might be changed. Regardless - I like reader idea as a higher-level object used only for accessing relations, hence I'd like to have this feature to be part of the reader API, not relation. Especially that, like I already mentioned, Relation doesn't know about the mappers and I believe it should stay like that.

OK so now it's:
rom.read(:users).with_mapper(:prefixer)

HAPPY?!!??!?!?! ;)

Haha, let's go with that :+1: Thanks for explaining, you successfully managed to convince me not to :fire: reader. ;-)

:relieved:


Equilibration error due to None in similarity column

Error:
"/work/NBD_Utilities/PELE/PELE_Softwares/adaptive_types/v1.6.2_python3.6foss2018/AdaptivePELE/simulation/simulationrunner.py", line 781, in selectEquilibratedStructure
if energyColumn > similarityColumn or similarityColumn is None:
TypeError: '>' not supported between instances of 'int' and 'NoneType'
The clause if  in simulation/simulationrunner.py", line 781 looks worng as if similarityColumnis none can't do the comparison (>).
Would that be possible?
Thanks!

similarityColumn can be None if there is no RMSD or distance metric in the PELE control file. Do you have them? Because the names are hard-coded and maybe they have changed in new PELE versions. Anyway the error is raised because of a bug in line 781, the two clauses in the if should be switched to avoid the comparison error. I have pushed a commit with a quick fix for this. Thanks for the tip!


Before
After

Fixed:

Trailing Whitespace Violation
Line Length Violation
Generated and third-party files excluded from linting

Thanks for the pull request, @volodymyr-chekyrta! Please note that it may take us up to several weeks or months to complete a review and merge your PR.
Feel free to add as much of the following information to the ticket as you can:

supporting documentation
Open edX discussion forum threads
timeline information ("this must be merged by XX date", and why that is)
partner information ("this is a course on edx.org")
any other information that can help Product understand the context for the PR

All technical communication about the code itself will be done via the GitHub pull request interface. As a reminder, our process documentation is here.
Please let us know once your PR is ready for our review and all tests are green.

@saeedbashir @rnr Kindly review the changes made in this pull request. Thank you.
Feel free to move the review from yourself to someone else.

@volodymyr-chekyrta 🎉 Your pull request was merged!  Please take a moment  to answer a two question survey so we can improve your experience in the future.


Provide a way to globally prevent addition of toolchain settings to global user configuration

Version of VSCode: 1.14.2
Version of the extension: 0.4.2
OS: OSX, Linux, Windows
Description:
I use vscode and rust across multiple operating systems with a shared user configuration.
My user configuration is intentionally platform-portable.
The rust toolchain selection causes me a constant frustration as it adds non-portable configuration to my global user configuration.
I know that most users are happy with that behavior and feature, but it's a real pain for me. I would like some solution that at minimum I can set to prevent the plugin from ever trying to do that. Ideally for me, it would inherit the rustup default from the system, and only allow (not require) per project or per-system configuration in the editor.

I was thinking about it since I have implemented it.
I didn't think it matters much, but I did understand that some people wouldn't be happy with that.
Currently I'm really busy, but I think it's easy to implement.
I'd open a PR tomorrow.
What I'm going to change is that when the extension asks something and you chooses something, then the extension would ask where to save the settings: workspace or global.
Let me know what you think about it.

That sounds really great. I also decided to open the hood and I was able to craft a patch that simply avoids doing any work if there's only a single default toolchain and it's nightly.
Thanks!

It seems I cannot do that at the moment because of my bad architecture.

I've opened #341 which describes what exactly isn't right at the moment.

I think in this weekends I'd change.


mj_ray performance regression from 3.1.1 to 3.2.0

I've recently upgraded from v3.1.1 to v3.2.0 and I'm seeing some large regressions in performance in simulations that call mj_ray. We use mj_ray to determine the visibility of certain objects in a scene. This post is twofold:

Perhaps we're using mj_ray inefficiently and there are some optimizations required on our end.
Perhaps there's been a regression in mj_ray.

For all of our simulations we track simulated time and wall clock time and provide a "realtime ratio" (wall clock time / simulated time) as an output. I noticed that many of our simulations showed little difference in realtime ratio between both mujoco version, but some were quite different. Using one of the simulations that showed a large regression in wall clock time (the sim takes much longer to run), I did some comparisons.
I've run the same simulation using 3.1.1 and 3.2.0 to compare performance. Here is some data I've collected:
For both simulations the simulated time is 12.102 seconds
When running with v3.1.1, the wall clock time is 26.073 seconds (a ratio of 2.15)
When running with v3.2.0, the wall clock time is 110.86 seconds (a ratio of 9.16)
In order to dig deeper, I've run the above simulation using both versions of mujoco under perf to try to pinpoint what was running slower. It turns out that mj_ray is the culprit.
When running with v3.1.1, the calls to mj_ray account for 13.9% of the total execution time of the simulation
When running with v3.2.0, the calls to mj_ray account for 78.6% of the total execution time of the simulation
Diving deeper, mju_rayTree accounts for 13.1% of the simulation time for v3.1.1 and 78.3% of the simulation time for v3.2.0
ray_triangle which is called by mju_rayTree takes less that 1% under both versions.
What additional information can I provide in order to help debug this issue?

Hi, could you provide the value of model.nbvh for your model before and after the change?

With mujoco 3.2.0 we have:
model.nbody=96
model.nbvh=2622528
model.nbvhstatic=2622528
model.nbvhdynamic=0
With mujoco 3.1.1 we have:
model.nbody=96
model.nbvh=2622599
model.nbvhstatic=2622599
model.nbvhdynamic=0
So, pretty similar, but not exactly he same.

How much time is going into mju_raySlab for the two cases? Or where otherwise is the time going?

Let me dig back up the perf data, but from the screenshot I have, I see this:

I don't actually see a call to mju_raySlab, so maybe it's very tiny?
We have a function to check if a point is visible (creatively named isPointVisible to check if a point in our scene is visible from a camera location. We use mj_ray for this (perhaps there is a better way. Here's the timing breakdown that I can find (I'm going to invert the call stack from what is shown in the image):
isPointVisible : 75.3%
mj_ray : 75.3%
mj_rayMesh : 75.1%  | ray_box : 0.0501%
mju_rayTree : 75% |  ray_box : 0.0631%
?? : 0.0958% | ray_triangle : 0.0636
Items on the same line appear to both be called by the function on the line above it. There's a bunch of stuff that seems to be called by the ?? function above, but it and all of the called functions are optimized out. I can try to rebuild with debug symbols and see if I get more data. I'm not sure if any of that helps. What function should be calling mju_raySlab?

Here's another view of all function calls that match _ray:

Could you please set this flag https://mujoco.readthedocs.io/en/latest/XMLreference.html#visual-global-bvactive to false and repeat the benchmark? That's the only line of code that has changed in mj_rayMesh since 3.1.1.

Could you also provide np.max(model.bvh_depth) (or the equivalent from C)?
If possible, it would help if you gave us an example model where this happens, and the code you're using for measurement.

I'm using perf to measure the performance. The only difference between my A/B comparison between 3.1.1 and 3.2.0 is the mujoco version. We use bazel for our build system, so I'm simply fetching a different tarball from the github repository.
max(model.bvh_depth) is 18 for mujoco 3.2.0 and 19 for 3.1.1
I'll try to put together a reproducible model that I can share.

Could you please set this flag https://mujoco.readthedocs.io/en/latest/XMLreference.html#visual-global-bvactive to false and repeat the benchmark? That's the only line of code that has changed in mj_rayMesh since 3.1.1.

Did this make any difference at all?

Could you please set this flag https://mujoco.readthedocs.io/en/latest/XMLreference.html#visual-global-bvactive to false and repeat the benchmark? That's the only line of code that has changed in mj_rayMesh since 3.1.1.

Did this make any difference at all?

I missed your original message. I just gave it a try.
bvactive = "true"
simulation time = 12.10200, wall time = 113.72063, ratio: 9.39685
bvactive = "false"
simulation time = 12.10200, wall time = 110.67355, ratio: 9.14506
Looks like the difference is negligible (probably within the noise of system resource contention).

When would we expect a new release to be created containing #1906?

Look at our historical release cadence on the changelog. Early September. In the meantime build from source.


sftd_get_text_width's text parameter isn't marked "const"

Looking at sftd.c, it doesn't look like sftd_get_text_width modifies the string pointed to by its text parameter in any way, nor can I think of any situation in which it would make sense for it to do so. When dealing with strings, however, making sure parameters are marked const is very important, as otherwise, for instance, string literals don't work. The C++ std::string class also can't be used here, as its c_str method returns a const string. As a result, I had to use the ugly workaround of putting const_cast<char*>(text.c_str()) instead of simply text.c_str().

Yeah, I'll add const right now. Good catch.

Fixed with<PHONE_NUMBER>919ac9c2e06f86b7733e0644c1d7ae.


[RULE] Disable Force strictly even balance across zones in Azure Virtual Machine Scale Sets

Existing rule
No response
Suggested rule
As per APRL recommendation, disabling strictly even VM instance distribution across Availability Zones in VMSS improves scalability and flexibility, noting that uneven distribution may better serve application load demands despite the potential trade-off in resilience.
Resource Type: microsoft.compute/virtualmachinescalesets
Properties should NOT have the following values: properties.orchestrationMode == "Uniform" and _properties.zoneBalance == true
Pillar
Reliability
Additional context
VMSS Custom Scale-in Policy in Reliability Hub
This rule will be used to test against the AVM Bicep VMSS module.
@rahalan

@jeanchg Similar to #2902. Does this recommendation only apply in the case when orchestrationMode is Uniform. OR does it equally apply in the case of Flexible?

I can create the rule, but awaiting for alignment before constructing the rule body.

checking with @rahalan , will update shortly

Any update @jeanchg?

@BenjaminEngeset @jeanchg @BernieWhite after reading thoroughly through the documentation, I see no reason, why this recommendation should only apply to uniform and not flexible as well. I would suggest to recommend it for flexible as well.


CloudWatch scheduled events typo?

I was having issues trying to get my aws.cloudwatch.onSchedule() to execute my aws.lambda.CallbackFunction. Could this be the cause and if so, would these other instances be broken as well? I can't figure out how to run the code locally so I just figured it might be easier to show this to more knowledgeable people.

HI @dixler
Sorry you are finding this error - please can you post some code that helps us recreate this issue and show us the issue you are having?
Paul

HI @dixler
Sorry you are finding this error - please can you post some code that helps us recreate this issue and show us the issue you are having?
Paul

I looked at my package-lock.json and noticed that I'm on 1.18(I've been copying the same directory over and over again). I'm not having the problem after upgrading to 1.25.


Allow obs-text characters in response status reason phrase

In particular, this avoids parsing failures when servers return accented ISO 8859-1 characters.
The existing comment noting the non-compliance had two suggestions for future improvement: return a &[u8], or add specialized helpers such as display(). I decided to go with the former since the reason phrase appears largely unused in downstream dependencies like hyper.
This is unfortunately a breaking change due to the new type, but it's a very important change for interoperability with traffic in the wild.

Do you know of specific websites that do this? (Maybe you can't share, that's fine...)
I'm bummed about the breaking change... I've only thought about this for a minute, but another option is to add some reason_bytes: Option<&[u8]> field...

Do you know of specific websites that do this? (Maybe you can't share, that's fine...)
I'm bummed about the breaking change... I've only thought about this for a minute, but another option is to add some reason_bytes: Option<&[u8]> field...

Do you know of specific websites that do this? (Maybe you can't share, that's fine...)

Yes, and maybe soon but not now :crossed_fingers:

I'm bummed about the breaking change...

Yeah, agreed. The only way I've thought up to avoid the breaking change is to return a static "" if non-utf8 bytes are found, after still consuming the reason phrase from the bytes buffer.

another option is to add some reason_bytes: Option<&[u8]> field...

This would also be breaking because all the fields of Response are pub :disappointed:

Do you know of specific websites that do this? (Maybe you can't share, that's fine...)

Yes, and maybe soon but not now :crossed_fingers:

I'm bummed about the breaking change...

Yeah, agreed. The only way I've thought up to avoid the breaking change is to return a static "" if non-utf8 bytes are found, after still consuming the reason phrase from the bytes buffer.

another option is to add some reason_bytes: Option<&[u8]> field...

This would also be breaking because all the fields of Response are pub :disappointed:

This would also be breaking because all the fields of Response are pub

Eek, you're right! Ugh, I wrote this crate so long ago, before I realized API traps were a thing...

return a static "" if non-utf8 bytes are found, after still consuming the reason phrase from the bytes buffer.

This doesn't sound so bad, actually... Sure, ideally we'd just have them be opaque bytes, but, but! Maybe the bytes aren't really that useful anyways, and so we can just skip them...?

This would also be breaking because all the fields of Response are pub

Eek, you're right! Ugh, I wrote this crate so long ago, before I realized API traps were a thing...

return a static "" if non-utf8 bytes are found, after still consuming the reason phrase from the bytes buffer.

This doesn't sound so bad, actually... Sure, ideally we'd just have them be opaque bytes, but, but! Maybe the bytes aren't really that useful anyways, and so we can just skip them...?

This doesn't sound so bad, actually... Sure, ideally we'd just have them be opaque bytes, but, but! Maybe the bytes aren't really that useful anyways, and so we can just skip them...?

That'd be fine with us, after all we're only using this crate via hyper which doesn't use the reason phrase. Shall I update the PR with the empty string behavior?

This doesn't sound so bad, actually... Sure, ideally we'd just have them be opaque bytes, but, but! Maybe the bytes aren't really that useful anyways, and so we can just skip them...?

That'd be fine with us, after all we're only using this crate via hyper which doesn't use the reason phrase. Shall I update the PR with the empty string behavior?

Yea, that sounds good to me, thanks!

Yea, that sounds good to me, thanks!

Pushed the new behavior in 1ca756c

Pushed the new behavior in 1ca756c


Bump deps

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 97.27%. Comparing base (53d4db0) to head (dd45571).
Report is 1 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #125   +/-   ##
=======================================
  Coverage   97.27%   97.27%
=======================================
  Files          12       12
  Lines         697      697
  Branches      103      103
=======================================
  Hits          678      678
  Partials       19       19

Flag
Coverage Δ

unit-tests
?

unittests
97.27% <ø> (?)

Flags with carried forward coverage won't be shown. Click here to find out more.

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


feat: move cloud provider regions method to cluster

Description
Docs are in for the cloud provider regions it should be in the same group as all cluster methods
This may be a breaking change but since we have not released a client I'm ok with this change
Link to any related issue(s):
Type of change:

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

Required Checklist:

[x] I have signed the MongoDB CLA
[x] I have added tests that prove my fix is effective or that my feature works
[x] I have added any necessary documentation (if appropriate)
[x] I have run make fmt and formatted my code

@themantissa ready for you