Document pydoc conventions

Per conversation with @bkmartinjr we should standardize how we write Python docstrings
There are standards out there like pandas/numpy.
One example from @bkmartinjr :
def split_column_names(
    array_schema: tiledb.ArraySchema, column_names: Optional[Sequence[str]]
) -> Tuple[Union[Sequence[str], None], Union[Sequence[str], None]]:
    """
    Given a tiledb ArraySchema and a list of dim or attr names, split
    them into a tuple of (dim_names, attr_names).

    This helper is used to turn the SOMA `column_names` parameter into a
    form that can be natively used by tiledb.Array.query, which requires
    that the list of names be separated into `dims` and `attrs`.

    Parameters
    ----------
    array_schema : tiledb.Array
        An array schema which will be used to determine whether a
        column name is a dim or attr.
    column_names : Optional[Sequence[str]]
        List of column names to split into `dim` and `attr` names.

    Returns
    -------
    Tuple[Union[Sequence[str], None], Union[Sequence[str], None]]
        If column_names is `None`, the tuple `(None, None)` will be returned.
        Otherwise, returns a tuple of (dim_names, attr_names), with any unknown
        names, ie, not present in the array schema, ignored (dropped).
    """

For help(foo) kinds of contexts, it's up to us really -- any standard will do IMHO ...
... except ...
our docs do also need to render nicely in readthedocs.
All I know is we definitely need double-backticking for nice rendering in readthedocs.
Also, @bkmartinjr is working on main but at present our readthedocs are for main-old.
Also, since #287 and PRs around that time (the great repo move) I believe readthedocs publishing is currently broken.
So -- in summary -- let's keep this as a tracking ittem open until I unbreak readthedocs and can get a better suggestion for how to write Python docstrings.
For anyone doing Python dev at the moment on this package (@bkmartinjr , @thetorpedodog , myself) the main to-do (besides use double-backtick) is just go ahead and create the verbage. Develop that IP and write it down. I can/will reformat later to fit tooling needs.

I recommend Pandas/Numpy conventions.
We should also make sure the end result looks good in vscode and other editors that display docstrings.  I find this at least as useful as the other doc formats.


Add styles for text view states on Welcome Message Center screen

Add ability to disable text field.
MOB-1797

There are some SwiftLint issues. Some are old but some are very recent. Do you think you could add a commit to fix them?

Fixed warnings related to secure messaging 7656eff892a1c47ea748c78655fc76bd38294035.

!squash

merge!

!merge


Prepare for release 1.4.1

Signed-off-by: Ivan Kozlovic<EMAIL_ADDRESS>

Coverage decreased (-0.08%) to 92.873% when pulling 441edf411399bccab0e8e18432dba94c174f7f7b on release_1_4_1 into 8e883725ecc388a3d5d6a82417e141475ee1cf07 on branch_1_4_0.


ci: test Firefox WebDriverBiDi headless and headful modes

It also test CDP implementation only on headless

@Lightning00Blade let's merge it if ready?


fixing a bug where exceptions would not be thrown because of async co…

Hey,
Using the library I noticed that exceptions are not thrown to the upper stack because the await operator was not used with HandleError and the Task chaining wasn't done properly.
Hopefully that fixes it.

Could you separate this from another one? This PR contains both phoneDialIn issue and exception issue.

Sorry, I took the wrong branch when creating the PR. Just created #12 and closing this one.


Documnet error : vulcan need install in global

What's wrong?

What's the correct behavior?
follow document, install command is npm install @vulcan-sql/cli, but it will install in local place.
But usage command is vulcan init, if modules install in local node_modules, command is npx vulcan init or write usage command in package.json.
 Suggest install command modify to npm install -g  @vulcan-sql/cli, it will make usage command right.

hi @eastmoon
Thanks for your advice on the document.
VulcanSQL is a monorepo, which includes different sub-modules like building-tools, server, catalog, and also the CLI tool you mentioned. Changing the command in the doc to npm install -g @vulcan-sql/cli surely solved the issue you mentioned, but we're also very cautious about keeping the versions of different sub-modules consistent. Not sure if we suggest users install CLI globally and keeping other modules locally will risk versions being inconsistent.
I'll be sure to discuss this matter with other core members and follow up on our discussion later in this thread.


Installer stalls after installing bundle with Ruby 2.2.0

I just tried generating a new Aurora theme, and I'm having problems with the installer never finishing.
This is my setup
[?] What's your theme's name? (Required): spokoi
[?] Which base theme would you like to use? Aurora
[?] What Aurora base would you like to use? Aurora
[?] Do you want to customize your theme's directories? No
[?] What options would you like to include? Gulp, Bower

(I have<EMAIL_ADDRESS>and<EMAIL_ADDRESS>installed)
The error occurs after this:
Installing singularitygs 1.4.0
Installing toolkit 2.6.0
Using bundler 1.7.9
Your bundle is complete!
It was installed into ./.vendor/bundle
Post-install message from compass:
    Compass is charityware. If you love it, please donate on our behalf at http://umdf.org/compass Thanks!
/Users/mikl/Sites/sfera/profiles/sfera/themes/spokoi/spokoi/.vendor/bundle/ruby/2.2.0/gems/compass-core-1.0.1/lib/compass/core/caniuse.rb:72: warning: circular argument reference - browsers
directory css
    write css/print.css
    write css/style.css

It never seems to finish after this (I've waited about 30 minutes now) – like a Node.js program waiting for a callback that never comes, or something like this. I wonder if it's related to the circular argument warning.

I stumbled over your issue googling the same problem. It's actually a compass issue: https://github.com/Compass/compass/issues/1902
and it looks like it's going to be resolved with the next release

That's fantastic!  Thanks for the update


[Bug] ExtendViewIntoTitleBar = true renders differently between Xamarin Forms/UWP and MAUI/WinUI3

Describe the bug
When ExtendViewIntoTitleBar is set to true this causes the titlebar not to show up in MAUI. However on Xamarin Forms/UWP the titlebar does not show up but the minimize, maximize and close buttons show up and can be styled.
Steps to reproduce the bug

Steps to reproduce the behavior:
Xamarin

Create a new xamarin app
In the UWP application open the App.xaml.cs
Add the following code to the OnLaunched method
CoreApplication.GetCurrentView().TitleBar.ExtendViewIntoTitleBar = true;

MAUI

Create a new maui app - Run dotnet new maui2.
In the WinUI application open the Platform/Windows/App.xaml.cs
Add the following code to the OnLaunched method
MauiWinUIApplication.Current.MainWindow.ExtendsContentIntoTitleBar = true;

Expected behavior

The UWP and MAUI applications would either both show the minimize, maximize, and close buttons or they wouldn't
Screenshots

-Xamarin-

-MAUI-

Version Info

NuGet package version:

Microsoft.ProjectReunion 0.8.0

Windows 10 version
Saw the problem?

Insider Build (xxxxx)

May 2020 Update (19041)

November 2019 Update (18363)

May 2019 Update (18362)

October 2018 Update (17763)
Yes

Additional context

Hi @Daniellled, thanks for the feedback! This appears to be an issue related to the .Net Maui team. Please file it under that teams repo for them to appropriately triage!


Allow for signal aliasing

solves #261
supersedes #260
Add a keyword argument to SignalGroupDescriptor to specify signal aliases (if the alias is None, no signal is emitted when changing the field). The signal aliases table is stored in the SignalGroup class.
Also allow for specifying per-field options for Signals using the metadata of the fields (different implementation in the different packages).
It solves #261 elegantly and makes subclassing more automatic:
from typing import ClassVar
from attrs import define, field
from psygnal import SignalGroupDescriptor, EmissionInfo

@define
class Model:
    events: ClassVar = SignalGroupDescriptor(
        signal_suffix="_changed",
        signal_aliases={"_controller": None, "_name": "name_changed", "name": None},
    )

    _controller: str = field()
    _name: str = field(kw_only=True)

    @property
    def name(self) -> str:
        return self._name

    @name.setter
    def name(self, value: str) -> None:
        # Generate a unique name among siblings
        siblings = [self.controller]
        value = f"{value}_1" if value in siblings else value
        self._name = value

    @property
    def controller(self) -> str:
        return self._controller

m = Model("ctt", name="c")
@m.events.connect
def on_any_change(info: EmissionInfo):
    print(f"signal {info.signal.name!r} emitted {info.args}")

m.name = "ctt"; m.name
# >> signal 'name_changed' emitted ('ctt_1', 'c')

hey @getzze, thanks again for all your work on this.  it's greatly appreciated.
I took a quick look yesterday and I like a lot of what I see, and also have a couple minor reservations that I want to think through a bit more (such establishing any new patterns for field-specific metadata, such as the Annotated pattern for pydantic2).  But in general, I think you're right: it's a very flexible solution that solves most of the issues you've pointed out so far.
One other thing I'll mention is the library fieldz.  I have a couple other libraries where I want to be able to support a bunch of different dataclass-like patterns, and fieldz grew out of that.  I hadn't used it yet here to avoid an additional dependency, but with this PR, it might be time to consider using fieldz.fields() instead of the the iter_fields() method that i had, and which you've extended in this PR.  (it's possible we'll need to make a PR or two to fieldz to make sure we're grabbing field-specific metadata in a way that works for psygnal too)
it's been a busy week here, so sorry that I haven't commented yet, but will have a deeper look soon.  (In the meantime, don't worry too much about the mypyc compiled tests failing)

Now it fails only with compile=True, so I'm done :)
I didn't find any official way to add metadata to fields in Pydantic v2, but in the forums people seem to pass the metadata as a dict in the second argument of Annotated. It works but this mechanism was not thought to be used like that indeed: https://docs.pydantic.dev/latest/api/fields/#pydantic.fields.FieldInfo
It would be great to add the iter_fields_with_options function to fieldz, although as you said that would be an extra dependency.
Sorry for the large PR, it has all the part about metadata for individual fields but also the part about signal aliasing.
The signal aliasing mechanism could help solve #260 and #262 if SignalGroup is redesigned as a container with a Signal proxy attribute and a list of attached Signals. I'll explain better in #262

I rebased to main. I just realized that one part of this PR should have gone to v0.10 release, I can make a separate PR.
Do you still think it makes sense to make SignalGroup a Mapping ?
About this PR, I restructured it to include 3 features:

Skip a field: do not create the signal associated with it
Alias a signal: a field called "name", the signal is called "name_changed"
Do not trigger the signal when field is changed.

Maybe 3 is not really needed actually.
There is two ways of doing that:

defining dicts and lists of fields to skip and alias to pass as arguments to @evented or SignalGroupDescriptor
defining in the metadata of each field.

The metadata part can go to another PR (or even to fieldz as you already mentioned).
Another change brought by this PR is the collect_fields argument to SignalGroupDescriptor. Before, if you specified a signal_group_class to a  SignalGroupDescriptor, the fields were not added to it. So you could not provide special signal names, not related to the fields of the dataclass, and at the same time automatically create the signals attached to the fields. With this PR, signal_group_class defines the base SignalGroup type (by default it is just SignalGroup) and specify if you want to also collect the fields with collect_fields. This could go in another PR.
Tell me what you think about it when you have time :slightly_smiling_face:

Once #291 is merged, I'll split this PR, first add the signal_aliases option, then add the metadata on the fields.

Once #291 is merged, I'll split this PR, first add the signal_aliases option, then add the metadata on the fields.

sounds good!  the metadata on the fields is the one i'm the most anxious about :) but we'll find something that works

With #299 merged, this PR adds parsing of field metadata to define aliases directly in the fields declarations.
I don't know if it's worth adding, maybe it's too much work to maintain (like keep up with the dataclasses-like librairies API changes). At least it should be low priority.
It also needs some work to make it work with the compiled version and to improve the speed.

thanks for the update here @getzze, I do think i'm going to take you up on the offer to allow this to be low priority :)
i like the general idea... and indeed there are parts of the EventedModel config that would be better off as a Field() metadata rather than model metadata.


Adding Elestio as deployment option

Hey team,
I am Kaiwalya, Developer Advocate at Elestio. Elestio has been providing options of fully deploying and managing MicroK8s as shown here. I think it would be a great idea if we can add it to official readme/documentation here.
🔔 In addition to this, if you are interested we provide partnership opportunities with tools we support by revenue share upon addition of this method in docs. If you would like to collaborate, just shoot me an email at<EMAIL_ADDRESS>:)

Hey @kaiwalyakoparkar thank you for contacting us!
Please take a look at our "Channel / reseller program": https://canonical.com/partners/channel-and-reseller
Additionally, please feel in your details under the "Become a partner" site: https://canonical.com/partners/become-a-partner
Someone from the Canonical alliance crew should contact you shortly after.
Cheers!


About adding one project of JavaScript

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
Describe the solution you'd like
A clear and concise description of what you want to happen.
Additional context
Add any other context about the feature request here.

Hey @sonalisonawane Please add the full description of what your project is!!

Hey @sonalisonawane may I add a project of a video player that is solely made of javascript that contains play, pause, skip 10 sec, timeline features.. what say?

yes sure!

Hey @sonalisonawane I like your idea

Thank you :) @urvashi-code1255 mam ,glad to add more projects in this repo onwards.


crash: chunk size must be non-zero

Uiua 0.13.0 as well as 0.14.0-dev.2
Run the following code:

uiua eval "⬚0+ ? =0↯⊙⊚ 1 0 [0_0 0_0]"

the interpreter crashes:

(This is a reduced example, just in case you think that the code doesn't make much sense. 😄)

Fixed in 53466b9456c36bce.

Fixed for real in 291c99502ceb40

Confirmed. Thanks.


Need module to create custom cipher list

I don't see this ability in any of the 30 or so ADC modules. This is an example of a command-line version of what we are looking to do:
add ssl cipher CIPHER-STANDARD-2019-07_cg
bind ssl cipher CIPHER-STANDARD-2019-07_cg -cipherName TLS1.2-ECDHE-RSA-AES256-GCM-SHA384 -cipherPriority 1
bind ssl cipher CIPHER-STANDARD-2019-07_cg -cipherName TLS1.2-ECDHE-RSA-AES128-GCM-SHA256 -cipherPriority 2
bind ssl cipher CIPHER-STANDARD-2019-07_cg -cipherName TLS1.2-ECDHE-RSA-AES-128-SHA256 -cipherPriority 3
Could this be added please? See related request on creating custom SSL profile (which will use/bind to a custom cipher list)

Included the requested feature in our plan. Will keep you posted.

Included the requested feature in our plan. Will keep you posted.

#171 Added the modules needed for this use case.
Here is an example playbook.
- hosts: citrix_adc

  gather_facts: False
  vars_files:
    - workflows.yaml
  collections:
    - citrix.adc

  tasks:
    - name: Setup cipher
      delegate_to: localhost
      citrix_adc_sslcipher:
        nsip: "{{ nsip }}"
        nitro_user: "{{ nitro_user }}"
        nitro_pass: "{{ nitro_pass }}"

        validate_certs: no
        state: present

        ciphergroupname: test_cipher

    - name: Setup cipher binding
      delegate_to: localhost
      citrix_adc_sslcipher_sslciphersuite_binding:
        nsip: "{{ nsip }}"
        nitro_user: "{{ nitro_user }}"
        nitro_pass: "{{ nitro_pass }}"

        validate_certs: no
        state: present

        ciphergroupname: test_cipher
        ciphername: TLS1.2-ECDHE-RSA-AES256-GCM-SHA384
        cipherpriority: "2"

    - name: Setup cipher binding
      delegate_to: localhost
      citrix_adc_sslcipher_sslciphersuite_binding:
        nsip: "{{ nsip }}"
        nitro_user: "{{ nitro_user }}"
        nitro_pass: "{{ nitro_pass }}"

        validate_certs: no
        state: present

        ciphergroupname: test_cipher
        ciphername: SSL3-EXP-ADH-DES-CBC-SHA
        cipherpriority: "4"


Allow for error-free build via go github.com/lightningnetwork/lnd/...

Not a big deal, but figured I might as well post this issue.
Currently the uspv package has these build errors:
uspv/eight333.go:21: undefined: wire.TestNetL
uspv/eight333.go:26: undefined: chaincfg.TestNetLParams

Other than that, only other package build issues I think others would run into when trying to do a go get of the .../... variety is the too many errors flavor of error in lnstate

Thanks! I've fixed the build errors with these three commits.
We'll have an automated travis-ci build-bot linked to the repo up shortly.


Can not jump to code from stack window?

How to jump to code from stack window?
Is it possible to jumping by double click or enter key?

Yes you can use the open mapping (o by default)

Yes you can use the open mapping (o by default)

Wow, it works charmly!

open works well, but I would like to use <CR> (mapped to expand) which is more intuitive. Is there any way to map expand behavior to open in the frame stack elements, or override keymap <CR> = open in the frame stack element only?

@wookayin FYI this works to override it in the stacks view:
dapui.setup({
  element_mappings = {
    stacks = {
      open = { "<CR>", "<2-LeftMouse>" },
    }
  },
})


skip flaky test

See discussion in https://github.com/flutter/flutter/issues/70630 and #70631

Landing on red to help make tree green.


fix renderBackgroundImage When receiving an image with 0 width or height

Summary

This PR fixes/implements the following bugs/features

[ ] Fixed bug in background when receiving an image with 0 width or height

Explain the motivation for making this change. What existing problem does the pull request solve?
I get the following error when user zoom in some pages.

Test plan (required)
This bug is a little tricky to reproduce. It happens when user zoom in the browser and it only happens in some pages (i don't know that element html produces the error).
Closing issues

Fixes #2807
Notes : this pr is similar to https://github.com/niklasvh/html2canvas/pull/2409/files#diff-d002d2a3a6a450c487065f80a86beb8070d226d4608ba1c42d468148ad9c24fe

This is merged and should be closed


Annotate function with inferred types

I am looking for a way to get the function arg types. it appears using debug.info I can get the source file and the line number
but this could be bad when the name is diffrent/everything is on one line
if function types dont exist post-compile some way to include that type information on functions would be nice

We don't have a way to do this right now, and enabling it in a Roblox environment is unlikely to be feasible in the near future - the type solver and the bytecode compiler have different performance requirements, and enabling RTTI on all platforms (including clients that didn't actually compile the bytecode they're running) is a pretty complex problem.
Can I ask what you're wanting this information for? If it's for debugging purposes, there may be a less general way to solve this.

I want the information so that I could generate a type for the function so that tools like luau-lsp (or the luau type checker) can prevent me from breaking the api that my module allready defines (so I would write a function that takes a table and returns the type string)

I'm not sure what is being asked here... is it a runtime function? Is it an editor feature that adds explicit annotations? E.g. we already have an --annotate mode in luau-analyze, is that the ask?

huh --annotate exist but is not as good as luau-lsp type infrence? but I was told luau-lsp used functions avaliable in luau
also it appears to contradict it's self when you luau-analyze a file that requires anything which has a table in it (it generates the type infrence, and places it somewhere. but does not fill out the table since it is doing like local module_type: {a:number} = {} which then fails as module_type is still a table and is not being filled

--annotate is not as complete as it could be, because it's written as a debugging tool, not a "canonically annotate this type" tool. Its output is also, by necessity, going to generate errors like what you mentioned, because it applies the "final type" of a variable to the variable declaration, which creates issues when you're partially initializing the table.
luau-lsp likely provides better inference than --annotate because it's working with Luau's C++ API, not the annotation syntax, and thus can handle types that we don't have syntax for, or unannotated types.
We've talked in the past about providing a way to generate an annotation that enforces the current inference results. I don't think it's coming in the next few months, but it is on our radar.

I'm wondering if we need both this and #402 or if we can just keep one of these.


Restart Jupyter kernel if package is installed via bash too

What is the problem that this fixes or functionality that this introduces? Does it fix any open issues?
This PR introduces functionality to restart the Jupyter kernel if a package is installed via bash commands. It addresses issues with kernel state management that arise when new packages are installed via bash, ensuring that changes are correctly reflected without manual intervention.

Give a summary of what the PR does, explaining any non-trivial design decisions
This PR refactors the ServerRuntime class to handle kernel restarts more effectively. Key changes include:

Kernel Restart Logic: Added a restart_kernel method to restart the Jupyter kernel and ensure that it is re-initialized with necessary code.
Parsing Pip Output: Added a parse_pip_output method to handle package installation messages and determine if a kernel restart is needed based on the output of pip install commands.
Removed Redundant Code: Moved kernel_init_code to restart_kernel method and removed unused kernel_init_code attributes from action parser classes (CodeActActionParserIPythonRunCell and CodeActSWEActionParserIPythonRunCell).

These changes ensure that kernel restarts and re-initializations are handled automatically, improving the reliability of the development environment.

Other references
Event history of ollama/llama3

We're doing some cleanup of PRs, and are going to close this one for now.


No DL2 MC files produced in two nodes due to slurm timeout

Missing DL2 files in node_theta_52.374_az_197.973_ and node_theta_52.374_az_49.119_
/fefs/aswg/data/mc/DL2/AllSky/20231024_v0.10.4_base_dec_min_2924_min_1802_6166/TestingDataset/dec_min_2924/node_theta_52.374_az_197.973_
.../node_theta_52.374_az_49.119_

due to exceeded time limit (from the error log):
slurmstepd: error: *** JOB 28907390 ON cp35 CANCELLED AT 2023-10-25T21:01:27 DUE TO TIME LIMIT ***

Is it possible to produce these files?

Hi @morcuended
Thanks for reporting this!
I will have a look.

I restarted jobs for  these two nodes


Using a community triplet

Hello!
I would like to use a custom triplet, provided here: https://github.com/Neumann-A/my-vcpkg-triplets.git
How can I accomplish this?

Hi @MangaD
To use the community triplet, you can clone the repository into your workspace. Then, use the extra-args parameter to vcpkg-action to pass the --overlay-triplets path. You can use {{ github.workspace }} variable to get the absolute path of the workspace.

Thank you, it is working!


Update Readme

I have added the steps for contribution in the readme.md file

Great!! IDK how I forgot to add that.


Update to 1.20.1 Please

Sorry didn't see this, 1.20.1 out now on Modrinth, I'm having issues with uploading to Curseforge at the moment. Will comment on this thread when CF cooperates again.

Thanks 😊


[RPO] fix nll loss

fixes the nll for RPO loss from #1686

@winglian can you kindly try with this fix?

also note @lewtun the v2 of the paper has this loss averaged over the completions (c and y):


CAF fixes

OPS Build status updates of commit c004749:
:clock10: Preparing: average preparing time is 46 sec(s)

OPS Build status updates of commit c004749:
:clock10: Incremental building: average incremental building time is 23 sec(s)

OPS Build status updates of commit c004749:
:warning: Validation status: warnings

File
Status
Preview URL
Details

bread/toc.json
:warning:Warning

Details

toc.json
:warning:Warning

Details

building-blocks/extending-templates/toc.json
:warning:Warning

Details

topics/high-performance-computing/TOC.json
:warning:Warning

Details

topics/high-performance-computing/breadcrumb/TOC.json
:warning:Warning

Details

topics/high-performance-computing/context/hpc-context.json
:warning:Warning

Details

docs/cloud-adoption/_images/formula-gain-from-investment.png
:white_check_mark:Succeeded
View

docs/cloud-adoption/_images/formula-roi.png
:white_check_mark:Succeeded
View

docs/cloud-adoption/business-strategy/financial-models.md
:white_check_mark:Succeeded
View

docs/cloud-adoption/getting-started/overview.md
:white_check_mark:Succeeded
View

docs/cloud-adoption/getting-started/what-is-azure.md
:white_check_mark:Succeeded
View

docs/cloud-adoption/getting-started/what-is-governance.md
:white_check_mark:Succeeded
View

docs/cloud-adoption/governance/policy-compliance/risk-tolerance.md
:white_check_mark:Succeeded
View

docs/cloud-adoption/overview.md
:white_check_mark:Succeeded
View

bread/toc.json

[Warning] Error happen when converting bread/toc.json to Pdf. Details: Could not find a part of the path 'T:\nzq5\bread\toc.json'.

toc.json

[Warning] Error happen when converting toc.json to Pdf. Details: Could not find file 'T:\nzq5\toc.json'.

building-blocks/extending-templates/toc.json

[Warning] Error happen when converting building-blocks/extending-templates/toc.json to Pdf. Details: Could not find a part of the path 'T:\nzq5\building-blocks\extending-templates\toc.json'.

topics/high-performance-computing/TOC.json

[Warning] Error happen when converting topics/high-performance-computing/TOC.json to Pdf. Details: Could not find a part of the path 'T:\nzq5\topics\high-performance-computing\TOC.json'.

topics/high-performance-computing/breadcrumb/TOC.json

[Warning] Error happen when converting topics/high-performance-computing/breadcrumb/TOC.json to Pdf. Details: Could not find a part of the path 'T:\nzq5\topics\high-performance-computing\breadcrumb\TOC.json'.

topics/high-performance-computing/context/hpc-context.json

[Warning] Error happen when converting topics/high-performance-computing/context/hpc-context.json to Pdf. Details: Could not find a part of the path 'T:\nzq5\topics\high-performance-computing\context\hpc-context.json'.

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

OPS Build status updates of commit f66eee5:
:clock10: Preparing: average preparing time is 46 sec(s)

OPS Build status updates of commit f66eee5:
:clock10: Incremental building: average incremental building time is 23 sec(s)

OPS Build status updates of commit f66eee5:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/cloud-adoption/_images/formula-gain-from-investment.png
:white_check_mark:Succeeded
View

docs/cloud-adoption/_images/formula-roi.png
:white_check_mark:Succeeded
View

docs/cloud-adoption/business-strategy/financial-models.md
:white_check_mark:Succeeded
View

docs/cloud-adoption/getting-started/overview.md
:white_check_mark:Succeeded
View

docs/cloud-adoption/getting-started/what-is-azure.md
:white_check_mark:Succeeded
View

docs/cloud-adoption/getting-started/what-is-governance.md
:white_check_mark:Succeeded
View

docs/cloud-adoption/governance/overview.md
:white_check_mark:Succeeded
View

docs/cloud-adoption/governance/policy-compliance/risk-tolerance.md
:white_check_mark:Succeeded
View

docs/cloud-adoption/overview.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

Docs Build status updates of commit 810c54d:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/cloud-adoption/business-strategy/financial-models.md
:white_check_mark:Succeeded
View

docs/cloud-adoption/getting-started/overview.md
:white_check_mark:Succeeded
View

docs/cloud-adoption/getting-started/what-is-azure.md
:white_check_mark:Succeeded
View

docs/cloud-adoption/getting-started/what-is-governance.md
:white_check_mark:Succeeded
View

docs/cloud-adoption/governance/overview.md
:white_check_mark:Succeeded
View

docs/cloud-adoption/governance/policy-compliance/risk-tolerance.md
:white_check_mark:Succeeded
View

docs/cloud-adoption/overview.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Fix a bunch of references, and some formatting, in the doxygen C guide

Part of #460.
Some documentation fixes. No code changes.

Thanks, merging now!


PWN-3049 - Disable skip for ReserveUsernameFragment opened from Home

Jira Ticket
https://p2pvalidator.atlassian.net/browse/PWN-3049
Description of Work
Remove You can also skip this step and reserve a username later text in Reserve Username in case of opening it from Home

wrong commit naming, sry

wrong commit naming and no assignee

What's wrong with commit name?

wrong commit naming and no assignee

What's wrong with commit name?

we don't use square brackets for task name.
 [PWN-3049] - Disable skip for ReserveUsernameFragment opened from Home
to
PWN-3049 - Disable skip for ReserveUsernameFragment opened from Home

Sure, thanks


can't seem to get user.scores to work the way I want it too

Hi there,
this is probably just me being an ape but I'm trying to figure out how to fetch the entirety of a user's top100 scores. I set the limit for user.scores.category to 100 but it still only ever gives me 5 scores.

Please let me know in what way I'm being hare-brained here. I originally wanted to DM you instead of opening an issue but you have DMs closed on both twitter and discord. Thanks :)
edit: i also tried using the offset parameter but that didn't work either, i feel like a complete ape for not being able to get it to work

edit2: upon further investigation i haven't been able to get any params to work for this method. It also seems like a default limit of 5 is hard-coded somewhere I couldn't find (since the api defaults to 10). I assume this mystery code is also what is preventing any other params from applying, but I really have no clue. I have been able to temporarily get my code working by hardcoding my parameters into the url in category.js.
ok i'm stupid and i figured it out, closing

oops, i did mistake in documentation, thats how it should be
await v2.user.scores.category(user: number, type: 'recent' | 'best' | 'firsts' | 'pinned', obj: {
  include_fails?: string,
  mode?: string,
  limit?: number,
  offset?: string,
})

hello?

Sorry I didn't notice you reopened the issue, as mentioned when I originally closed it I figured it out (it was the solution you posted) I just assumed it was down to me not being familiar with node (or js in general)

ah, i see, it's also my fault for mistakes in docs


[Pallas] NotImplementedError: Unimplemented primitive in Pallas GPU lowering: slice.

Related #18897
Reproducing code:
import jax
from jax.experimental import pallas as pl

# take first two elements
def kernel(x_ref, o_ref):
    x = x_ref[...]
    o_ref[...] = jax.lax.slice(x, (0,), (2,))

def call_kernel(x: jax.Array) -> jax.Array:
    return pl.pallas_call(kernel, out_shape=jax.ShapeDtypeStruct((2,), x.dtype))(x)

x = jax.numpy.arange(4)
y = call_kernel(x)

Output:
Traceback (most recent call last):
  File "/home/alex/work/pallas-test/reproducer.py", line 13, in <module>
    y = call_kernel(x)
  File "/home/alex/work/pallas-test/reproducer.py", line 10, in call_kernel
    return pl.pallas_call(kernel, out_shape=jax.ShapeDtypeStruct((2,), x.dtype))(x)
  File "/home/alex/.pyenv/versions/3.10.12/envs/venv/lib/python3.10/site-packages/jax/_src/pallas/triton/lowering.py", line 1621, in pallas_call_lowering
    compilation_result = compile_jaxpr(
  File "/home/alex/.pyenv/versions/3.10.12/envs/venv/lib/python3.10/site-packages/jax/_src/pallas/triton/lowering.py", line 1564, in compile_jaxpr
    lowering_result = lower_jaxpr_to_triton_module(
  File "/home/alex/.pyenv/versions/3.10.12/envs/venv/lib/python3.10/site-packages/jax/_src/pallas/triton/lowering.py", line 280, in lower_jaxpr_to_triton_module
    () = lower_jaxpr_to_triton_ir(ctx, jaxpr, block_infos, *args)
  File "/home/alex/.pyenv/versions/3.10.12/envs/venv/lib/python3.10/site-packages/jax/_src/pallas/triton/lowering.py", line 323, in lower_jaxpr_to_triton_ir
    raise NotImplementedError(
NotImplementedError: Unimplemented primitive in Pallas GPU lowering: slice. Please file an issue on https://github.com/google/jax/issues.

Unfortunately there is no equivalent of slice in Triton so we don't currently have a way of lowering this right now. However, in your example, you could accomplish what you want by using pl.load w/ the correct indices.

Makes sense, actually this is just a small reproducing example. I found the error initially trying to use jax.lax.associative_scan within a kernel. Do you think pl.load could be used to replace slices in this scan?

I think it could but it might not be super performant. The general question to ask is: can I implement this efficiently using Triton? We are limited by the sets of ops that Triton supports, so if you can't express in Triton it's unlikely you can express it in Pallas on GPU.

@sharadmv I saw you directed me to this issue, but I don't understand how pl.load would solve my problem, is there some definition for this primitive and how to use it?
Thank you!

We don't have support for slicing because Triton doesn't support the op afaik. However, you could imagine if you did something like this:

def foo(x_ref):
  x = x_ref[...]
  x_slice = x[0]

you could instead do this:
def foo(x_ref):
  x_slice = x_ref[0]

and that should work.
That's basically what pl.load means.

In my code, it seems like the issue arises from the o_ref[...]=output which  I'm not sure how to handle since I need to return my output. Majority of Pallas examples seems to have this so not sure how to return the output. Thanks for the help!


Individuals: Map options unnecessary

The sidebar options for the map size Map options do not provide much and clutter the page. Perhaps removing these would be better. This would mean Issue #6  is "solved".

Fixed in #41


Luasocket dep

This is cool, I love the simplification over gfx.js.
Quick Q: do you need the latest luasocket? Specifying the 3rc version doesn't work for me.

Thanks!
Seems luasocket 2+ is good enough. See f30c20e469e925d0e7fdee3825fba9e832edaf33

great!


Tree View Controls, Address bar, with focus, enhancements.

Its as simple as providing and address bar for a treeview at the top of the treeview control space.
Think good old windows address bar in explorer, one can always see the current path one is in.
Currently on is not able to know the context of were one is in the tree view of the workspace folder,
because so many modules include modules folder and other recursively. Also src and output folders for js have identical folder structure, so one ends up editing files in the wrong place often due to navigation taken one to the output of a build.
Image of Workspace folder TreeView Address Bar
Please also introduce all the keyboard relevant shortcuts for a full set of all options.
For example:
Ctrl + up: moves to the next item in the tree that is the parent of the current.
Ctrl+ down would do the same.
Ctrl + left, would close the current path, place the parent item under focus.
Ctrl + right, would open the current path.
Ctrl + Alt + up / down, is modifier which will then jump to the next item, that doesn't begin with the same letter.
Ctrl + Alt + Left/Right, is a modifier which will then jump to the next item, that doesn't begin with same 2 first letters, which allows for more granularity of navigation control.
Ctrl + Backspace, navigate back though the navigation history.
Ctrl + Shift + Backspace navigate forward though the navigation history.
Ctrl + Shift + Enter, Will set the address bar into focus on the current item.
Obviously on should support page up. page down, home and end.
Ctrl in the address bar, should jump between path identifiers.
Overall layout navigation for VSCode.
Ctrl +Shift+Alt plus an arrow key, navigation, should allow navigation, which respect to the current control in focus, if arrow left, it will set the control to the left in as potential for focus, by highlight it area, with orange color. Opun hitting enter the control will then be put into focus. This allows me to simple navigate on the keyboard to the control I want then hit focus, to trigger all the UI stuff.
The tree view should also refocus the tree on the current file being edit.
If you want example of focus, you can download Albion and check out how the focus thing works.
Albion GIS

VS Code has support for a breadcrumb in the editor.

Yeah, enable it via "breadcrumbs.enabled": true


WIP: using external language servers to apply code fixes

This attempts to add in a best-efforts strategy for adding missing imports to unit tests after using the generate test actions. Linear.
What this tries to do is hook into the test generation step and check the diagnostics of the generated test file after it's completed. Because we need the file to be in the workspace to get QuickFix actions, It saves the file at the beginning of the process and then deletes it if the user undoes the operation.
Notes:
This approach (if we go with it) is VSCode only because it depends on invoking external extensions. However the other approaches I can think of are:

Trying to improve the LLM prompts so that it gets better at generating imports correctly

This might be better in practice but there is nothing that actually prevents the error from continuing to appear

Trying to detect missing imports and generate them from the file

This is the only sure-fire solution but seem intractable as we'd need parsers for each language we'd support, knowledge of their standard libraries, and an import resolution algorithm for each (there are dozens of extensions where this is the only problem they tackle and they still don't do a good job)

Test plan
Ran manually but will need to add automated test.

I see this is marked as a "quick win" in the Linear issue but based on the PR description and from a quick look at the diff, I don't think this looks like a quick win (and it only helps VS Code, not other clients). @jamesmcnamara what do you think about closing the linked ticket as wontfix? I recommend we focus instead on higher-priority issues on the roadmap https://linear.app/sourcegraph/view/8043082e-605c-4ac1-b8b7-2667e01b5647

@olafurpg I could see us doing that. Before we decide to close this, I did make some changes based on an idea from @abeatrix where I save the file at the beginning of test generation, so the experience for a VSCode user is mostly the same (i.e. they don't get the Modal asking them to accept and hoping it works), we just apply the fixes if we see them and they can still accept or reject the test (if they reject it, we delete the file).
The pro is that we should be able to leverage most language extensions for quick fixes which could be really useful. The con is that it's VSCode only and we are adding a file to their project, so we could mess up any file watchers possibly.
Let me know if that changes your mind, I'm fine to close it if not.


Allow for adding widgets as filters programmatically

Support adding a Panel Widget to the Pipeline programmatically.

Codecov Report

Merging #332 (8a21888) into master (617ae3b) will increase coverage by 0.35%.
The diff coverage is 93.02%.

@@            Coverage Diff             @@
##           master     #332      +/-   ##
==========================================
+ Coverage   66.76%   67.12%   +0.35%
==========================================
  Files          71       71
  Lines        7287     7327      +40
==========================================
+ Hits         4865     4918      +53
+ Misses       2422     2409      -13

Impacted Files
Coverage Δ

lumen/tests/validation/test_filters.py
100.00% <ø> (ø)

lumen/pipeline.py
66.35% <60.00%> (-0.47%)
:arrow_down:

lumen/filters/base.py
71.53% <96.00%> (+2.33%)
:arrow_up:

lumen/schema.py
57.61% <100.00%> (+2.51%)
:arrow_up:

lumen/tests/filters/test_base.py
100.00% <100.00%> (ø)

lumen/util.py
67.03% <0.00%> (+1.09%)
:arrow_up:

lumen/base.py
83.80% <0.00%> (+4.85%)
:arrow_up:

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Add a variant of Wasm image spec based on standard media types.

Description
Following the discussion (led by @dgn) in the Istio Wasm-SIG, this PR added a variant of Wasm image spec for storing Wasm binaries as standard container images.
Notably this new spec leverages the existing standard layers with either one of

application/vnd.oci.image.layer.v1.tar+gzip or
application/vnd.docker.image.rootfs.diff.tar.gzip

media type, not based on the OCI Artifact Spec. This allows users to use standard CLI tools in container ecosystem (such as docker, podman, buildah, etc.) and push to any standard registries without requiring support for arbitrary mediaType (including the one used before).
See #208 and a meeting note by @dgn for the background, and Appendixes sections for how end-users would operate to build images.
cc @dgn, @yuval-k @PiotrSikora @bianpengyuan @kyessenov
Signed-off-by: Takeshi Yoneda<EMAIL_ADDRESS>resolves #208

hi @mathetake! Thanks for working on this.
I believe there has been a misunderstanding. The idea with the OCI-compliant spec, as agreed on with @yuval-k , was not to replace the existing spec, but to add a variant that would only use OCI-compliant mediaTypes. Clients would then be able to look at the manifest and determine (e.g. from an annotation on the manifest) which variant is being used and parse it accordingly - the main difference being that the OCI-compliant variant uses a tarball to package the files, whereas the existing format uses no compression and custom mediaTypes.
That also means we'll want to keep everything that is already in the spec (e.g. all the envoy-specific configuration) and make it available in both variants. We don't want to break any existing users

@dgn ah right, thanks for clarifying.. will fix accordingly. Thanks.

@dgn fixed. PTAL.

@dgn PTAL again when you are back! 🙇  Here's the fetcher implementation for both docker and oci compat images, which I open a PR in Istio once this lands.

cc @mandarjog (I forgot to cc you).

JFYI @lizan

restructured the spec/ directory and added a general instruction as suggested by @mandarjog. PTAL folks https://github.com/mathetake/wasm/tree/oci-compliant-spec/spec

https://github.com/istio/istio/compare/master...mathetake:wasm-image-fetch?expand=1 and there's already working fetcher implementation in Istio: https://github.com/istio/istio/compare/master...mathetake:wasm-image-fetch?expand=1

@dgn @mandarjog PTAL!

Thanks @dgn, addressed all your comments and changed the implementation accordingly.
@Sodman @mandarjog I believe this is ready to land. I already have the implementation here (https://github.com/istio/istio/compare/master...mathetake:wasm-image-fetch?expand=1) which supports all the variants
in Istio. I will open the PR against Istio once this lands.

fyi I just opened a PR for fetching all the variants in Istio: https://github.com/istio/istio/pull/33812


New SyncUsers cannot read or write to shared realms until realm variable is refreshed

Goals
I have a realm which is shared across all users (default permissions are set to read/write for userID "*").
Expected Results
When creating a new user account, I want the account to be able to read and write to the shared realm.
Actual Results
The new user is able to log in, and is able to open the realm. However, the realm is empty, even after session.addProgressNotification(for .download, mode: .forCurrentlyOutstandingWork) has reported that the download of the realm is finished.
The user is able to perform write transactions, and can read the objects from the realm after writing.
When the realm variable is refreshed after some time, however, the full contents of the realm become accessible - however all previous writes performed by the new user are now lost.
Steps to Reproduce
Use the code sample below while observing the realm in the realm browser. Make sure the realm has read/write permissions for all users  (userid "*") and that the realm already has some AppUser objects created. My realm has quite a few objects (around 30 000) - not sure if this has anything to do with it.
Optionally, try commenting out the token creation to see that no new object is created on the realm no matter how long one waits.
Code Sample
SyncUser.logIn(with: .usernamePassword(username: username, password: password, register: true), server: URL(string: "http://"+realmServerIP)!) { user, error in
            guard let user = user else {
                fatalError(String(describing: error))
            }

            DispatchQueue.main.async {

                // realmURL points to a shared realm with write/read permission for all users (userID: "*")
                // the realm already has several AppUser objects stored
                let configuration = Realm.Configuration(
                    syncConfiguration: SyncConfiguration(user: user, realmURL: self.realmURL)
                )

                self.realm = try! Realm(configuration: configuration)

                let appUser = AppUser()
                appUser.userID = user.identity!

                try! self.realm?.write {
                    self.realm.add(appUser)
                }

                let session = user.session(for: self.realmURL)!
                self.downloadToken = session.addProgressNotification(for: .upload,
                                                                     mode: .forCurrentlyOutstandingWork) { progress in
                                                                        if progress.isTransferComplete {
                                                                            self.downloadToken?.stop()

                                                                            // the realm already has several AppUser objects stored
                                                                            if self.realm.objects(AppUser.self).count == 1 {
                                                                                print("Only one AppUser object found - refreshing realm")
                                                                                self.refreshRealm(user: user)
                                                                            } else {
                                                                                print("Realm has been loaded correctly")
                                                                                print("Previous written object exists in realm? \(self.realm.objects(AppUser.self).filter("userID = '\(user.identity!)'").first != nil)")
                                                                            }

                                                                        }

                }

            }
        }

    func refreshRealm(user: SyncUser){

        let configuration = Realm.Configuration(
            syncConfiguration: SyncConfiguration(user: user, realmURL: self.realmURL)
        )

        self.realm = try! Realm(configuration: configuration)

        let session = user.session(for: self.realmURL)!
        self.downloadToken = session.addProgressNotification(for: .download,
                                                             mode: .forCurrentlyOutstandingWork) { progress in
                                                                if progress.isTransferComplete {
                                                                    self.downloadToken?.stop()
                                                                    if self.realm.objects(AppUser.self).count == 1 {
                                                                        print("Only one appUser object found - refreshing realm")
                                                                        self.refreshRealm(user: user)
                                                                    } else {
                                                                        print("Realm has been loaded correctly")
                                                                        print("Previous written object exists in realm? \(self.realm.objects(AppUser.self).filter("userID = '\(user.identity!)'").first != nil)")
                                                                    }

                                                                }

        }

    }

Version of Realm and Tooling
I tried using your script in my project directory to find the realm version etc, but it apparently did not manage to find versions for realm or my dependency manager. I am on RealmSwift version 2.4.2.
ProductName:	Mac OS X
ProductVersion:	10.11.6
BuildVersion:	15G31

/Applications/Xcode.app/Contents/Developer
Xcode 8.2.1
Build version 8C1002

(not in use here)

/bin/bash
GNU bash, version 3.2.57(1)-release (x86_64-apple-darwin15)

(not in use here)

/usr/bin/git
git version 2.10.1 (Apple Git-78)

Looks like this might be caused by some race condition - the following workaround solves the issue:
        SyncUser.logIn(with: .usernamePassword(username: username, password: password, register: true), server: URL(string: "http://"+realmServerIP)!) { user, error in
            guard let user = user else {
                fatalError(String(describing: error))
            }

            DispatchQueue.main.async {

                // realmURL points to a shared realm with write/read permission for all users (userID: "*")
                // the realm already has several AppUser objects stored
                let configuration = Realm.Configuration(
                    syncConfiguration: SyncConfiguration(user: user, realmURL: self.realmURL)
                )

                self.realm = try! Realm(configuration: configuration)

                Timer.scheduledTimer(withTimeInterval: 1, repeats: false, block: { _ in

                    let session = user.session(for: self.realmURL)!
                    self.downloadToken = session.addProgressNotification(for: .download,
                                                                         mode: .forCurrentlyOutstandingWork) { progress in
                                                                            if progress.isTransferComplete {
                                                                                self.downloadToken?.stop()

                                                                                let appUser = AppUser()
                                                                                appUser.userID = user.identity!

                                                                                try! self.realm?.write {
                                                                                self.realm.add(appUser)
                                                                                }

                                                                                // the realm already has several AppUser objects stored
                                                                                if self.realm.objects(AppUser.self).count == 1 {
                                                                                print("Only one AppUser object found")
                                                                                } else {
                                                                                print("Realm has been loaded correctly")
                                                                                print("Previous written object exists in realm? \(self.realm.objects(AppUser.self).filter("userID = '\(user.identity!)'").first != nil)")
                                                                                }

                                                                            }

                    }

                })
            }
        }

Hi @jbuverud. Thank you for reaching out. We'll have someone review what you've provided and follow-up with you soon. :-)

Thanks for using Realm, and I humbly apologize that you're running into this problem. It looks like the same underlying issue as https://github.com/realm/realm-mobile-platform/issues/116. We're looking into the best way to fix it and it's one of our top priorities right now.

I'm going to close this ticket; if you're interested in updates please follow the ticket I linked in the previous comment.

Not working for me, Xcode 8.3.3, Realm 2.8.3.

Please open a new ticket and fill out the issue template. Thanks.


Different confirmation codes for owner and approver

Owner and Approver should receive different messages. Using the same mail and code and owner confirm taxi, it will be equals to approver's confirmation. Also add two new columns to table in the database: confimration code for approver and isConfirmedByApprover

For the moment lets stick to single confirmation. Both owner and approver receive the email because both can confirm it with the same link. If there really is a business need for confirmation from approver we will implement it.


Archive repo

Don't merge until content is migrated
Signed-off-by: Ry Jones<EMAIL_ADDRESS>

OK, please let me know when you finished.


DISCOVERY: Areas [5]

Work with Todd and Pete to gain an understanding of Areas and their role in the product.
Requirements:

Understand what an area is
Understand what can and can't be done with an area
Have questions answered

AC:

Todd/Pete have answered questions needed for design to have an understandable list of requirements.
it is clear which users will utilize this feature and how it impacts other users.
Questions have been answered.

(Originally RHUAP-584)

First iteration of Areas - future iterations to occur.

Second Iteration of Areas

Final iteration of Areas

@mindreeper2420 Regarding the comment that "there can be an infinite number of backlogs." Since each space has a single backlog - there can be only one - the work items that are in view are based on a query... do you mean that there is an infinite number of views into the backlog? Context is effectively a query and sets scope.

@michaelvirgil Perhaps it should be that there are an infinite number of queries that can render an infinite number of Backlog views? The breakout is as you said - there are an infinite number of views into a backlog, depending on the query that is selected (or created).

I took this as there can be an infinite number of views on the backlog as
well Adam... Meaning that any number of queries can be crafted for the view.
Not sure if there is a limit to spaces and areas, I read in TFS there is a
limit and I am sure we have one.... this would limit the number of physical
list/tree components representing the backlog. As far as a limit to the
number of queries stored and what that is based on I don't know.....
On Tue, Jan 17, 2017 at 2:58 PM, Adam Jolicoeur<EMAIL_ADDRESS>wrote:

@michaelvirgil https://github.com/michaelvirgil Perhaps it should be
that there are an infinite number of queries that can render an infinite
number of Backlog views? The breakout is as you said - there are an
infinite number of views into a backlog, depending on the query that is
selected (or created).
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/fabric8io/fabric8-ux/issues/101#issuecomment-273281616,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ARTwq4yglrmklfdIGq60W5sYsQLEtlywks5rTR17gaJpZM4LeqyB
.

General Information from Todd:

Both Areas and Iterations are hierarchies/trees of data. Each node has a name. Areas do not really have any additional info. Iterations have start & end date, plus UXD has recommended Description.

Areas (and Iterations) are configured through an Editor of some kind. The location of this editor is unknown (UXD decision), but should be similar (if not the same) as the Iteration editor.

Assume that these editors can fill the entire blank space inside of the UI (e.g. below the top navigation and above the footer). We'll eventually find the right tabs on which to place them.

I'd like to recommend that the default area has the same name as the name of the Space, rather than "/". I know that's the opposite of what I've told some of you in the past. :) The UX feedback that drove this change was wise.
Similarly, the default root of Iterations will also be the same name as the Space. i.e., in space Foo, there is a default area 'Foo' and a default iteration 'Foo'. Neither of these may be renamed or deleted. All others are descendants of them. (E.g., if the user adds Sprint 1 and Sprint 2, those are both children of iteration Foo. So Foo/Sprint 1 and Foo/Sprint 2. Of course, Sprint 1 and Sprint 2 may also have their own children, etc.)

"Iterations are tied to Spaces(which are tied to areas), so they are team agnostic"?
That kinda implies an Area is above a Space?

Questions/Comments on the diagram:
Team Hierarchy

Teams contain 1..n people (each person can be on 1..n teams) and provide user perms

Each team can be associated with 1..n areas

Organization Hierarchy

Spaces (formerly called "projects"), each space contains one backlog

Areas - hierachical, expressed in paths
Iterations (can also have child iterations)

Planning Hierarchy

Epics

Stories

Tasks

Execution Hierarchy

Release (can also have child releases)

Iterations (can also have child iterations)

Sprints

Open Questions:

Can teams be hierarchical?
Are releases a type of iteration?

Thx!

That kinda implies an Area is above a Space?

Good question.

@kwk @aslakknutsen That wording needs to be fixed. Areas should not be above Spaces. Good catch.
@ldimaggi Hierarchical Teams have not been discussed, but I don't see why they couldn't be - also not sure why they would be? I guess if you wanted to share permissions, but have smaller subsets of Teams. Something that will have to be brought back to the table for further discussion.
I would definitely say that Releases are a type of Iteration.


Question: How can i hide a tab item when creating a resource?

Hi.
Nova Fields has several methods to show / hide fields in form/detail/index views... but the tab itens are not a field, but a part of a field.
I need to show some tabs only in edit form, and hide them from create form. So i've tried hideWhenCreating method, but of course, not works.
Is there a way to do that ?

Hi.
At this time this feature is not available.

Hi.
At this time this feature is not available.

Hi, this option is important because sometimes we need to show only a couple of fiels in creation and in details or edit form other fields... So i think that organizing them into tabs is good.
Exmple: In my Cliente resource, i have two tabs that i need to show on creation: General and Documents and after created nee to show a couple of related resources, each one in a spedific tab: Contacts, Addresses, Owners. See below:

This is one of possible reazons to do this kind hiding tabs...

Hi.
At this time this feature is not available.

Hi, this option is important because sometimes we need to show only a couple of fiels in creation and in details or edit form other fields... So i think that organizing them into tabs is good.
Exmple: In my Cliente resource, i have two tabs that i need to show on creation: General and Documents and after created nee to show a couple of related resources, each one in a spedific tab: Contacts, Addresses, Owners. See below:

This is one of possible reasons to do this kind hiding tabs...

Hi.
You are right;
But at this time; I don't have enough time to implement this feature.

Hi.
At this time this feature is not available.

Hi, this option is important because sometimes we need to show only a couple of fiels in creation and in details or edit form other fields... So i think that organizing them into tabs is good.
Exmple: In my Cliente resource, i have two tabs that i need to show on creation: General and Documents and after created nee to show a couple of related resources, each one in a spedific tab: Contacts, Addresses, Owners. See below:

This is one of possible reasons to do this kind hiding tabs...

Hi.
You are right;
But at this time; I don't have enough time to implement this feature.

No problem. I'm just trying to contribute any way I can!
I was able to do it with a workaround using nova stuffs, by checking if the $request is a \Laravel\Nova\Http\Requests\ResourceDetailRequest instance... see:
public function fields(Request $request)
{
    return [
        Tab::make('fist-tab', function($tab) use($request){
            $tab->group('general', [
                ID::make()->sortable()->hideFromIndex(),
                ...
            ])->label('Geral');

            $tab->group('docs', [
                ...
            ])->label('Documentos');

            if ($request instanceof \Laravel\Nova\Http\Requests\ResourceDetailRequest) {
                $tab->group('contacts', [
                    ...

                $tab->group('addresses', [
                    ...
            }
        }),
    ];
}


chore: no longer use MaterialModule

Replaces the MaterialModule with custom NgModules that contain all required Material modules.

Closes #4532

@jelbourn Is this merge safe?

Nope, the demo app is actually built as part of the presubmit

Good to know that.

Rebased @tinayuangao


Work Item Template Management instructions are slightly off

https://docs.microsoft.com/en-us/azure/devops/boards/backlogs/work-item-template?view=vsts&tabs=browser#manage-work-item-templates
It says "Expand Work and choose Team configuration. " but for me it's under "Boards" not "Work".  And the screenshot doesn't show the list of settings containing these options, but that would be helpful.

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

ID: 1debd814-eb48-c984-a4f9-7606093e9617
Version Independent ID: f48ef796-c2e3-8fa3-6c41-326a5b252a3d
Content: Work item templates - Azure Boards
Content Source: docs/boards/backlogs/work-item-template.md
Product: devops
GitHub Login: @KathrynEE
Microsoft Alias: kaelli

@markfields - Thank you for the correct. The article is getting updated.


AminoMsgTransfer is not supporting Memo of the message

Can it be that the AminoMsgTransfer is not supporting the Memo field of the message?
https://github.com/cosmos/cosmjs/blob/358260bff71c9d3e7ad6644fcf64dc00325cdfb9/packages/stargate/src/modules/ibc/aminomessages.ts#L18
When the OfflineAminoSigner is used for example with a Ledger device, where in the Transfer Msg we also want to send a memo field, the memo gets discarded

Right, thanks for brining this up. The fix is here: https://github.com/cosmos/cosmjs/pull/1456

@webmaster128 Any chance of getting the mentioned fix merged? I've run into some issues with Ledger on both Keplr and Leap and I think this missing field in the encoding may be the root cause.
I noticed the PR has been inactive for some time. Need it be I can fork it and open a new PR.

Right, let's wait a day or two for Shane. Otherwise I can create a new branch and merge it.


Retry on failed docker push

Contributes to https://github.com/ocurrent/docker-base-images/issues/211
This is a retargeted refinement of https://github.com/ocurrent/ocurrent/pull/451
The approach proposed here provides three small, composable, Lwt combinators to offer retry logic in a flexible way. The base function, on_error produces a (potentially) unlimited sequence of attempts. Adding sleeps between attempts and stopping after a set number of retries is provided by small functions that consume the stream. Additionally functionality can easily be added in the similar fashion.
There is a clear recurring need for lwt-level retry logic, as documented in https://github.com/ocurrent/ocurrent/issues/450, which is why a general approach is proposed here. However, we also have a pressing need to get retries in place for the ephemeral failures from docker pushes that are eating up maintenance time. As a compromise, this utility as being added initially at the point of use, but as a relocatable library component, which we can easily promote to a shareable location when needed.
Many thanks to @mtelvers who has been a big help in thinking through what fix is need and where it should go.

This is great to me.  I have tested this with base image builder and a private registry where I can simulate failures.
First test.  The registry fails completely and never recovers.

Pushing "sha256:963ff6ccf841860bbaf9ca7fb76f62f91ed76ada172e528ba9125ae3910f41d9" to "docker.tunbury.org.uk/opam-staging:ubuntu-24.04-opam-arm64" as user "ocurrentbuilder"
Login Succeeded
The push refers to repository [docker.tunbury.org.uk/opam-staging]
e049cd353618: Preparing
dial tcp <IP_ADDRESS>:443: connect: connection refused
The push refers to repository [docker.tunbury.org.uk/opam-staging]
Get "https://docker.tunbury.org.uk/v2/": dial tcp <IP_ADDRESS>:443: connect: connection refused
The push refers to repository [docker.tunbury.org.uk/opam-staging]
Get "https://docker.tunbury.org.uk/v2/": dial tcp <IP_ADDRESS>:443: connect: connection refused
The push refers to repository [docker.tunbury.org.uk/opam-staging]
e049cd353618: Preparing
e049cd353618: Pushed
ubuntu-24.04-opam-arm64: digest: sha256:b38348c93811ae63892446949a7a32bf9555de0be6debf9c1363f3653c3ac5f6 size: 530
Job succeeded
2024-08-29 11:28.04: Job succeeded

It retries five times.  This means it actually tried six times, the initial try plus five more.  This is noted in the code as well.
It would be great to see some kind of logging.  Perhaps as simple as just Retrying or something fancy like failed with exit-code 1.  Retrying in 5 seconds., then after the sleep, Retry 1/5.
I wonder that the delay period is too short.  Using five retries, all the retries are exhausted in 72 seconds.  Perhaps use 2 ^ n rather than 1.5 ^ n, which would give 196 seconds in total (0, 4, 16, 48, 128), and/or skip the retry at 0 seconds.  This would result in 148 seconds with 1.5 or 516 seconds with 2.

Thanks you for the careful review and testing! It is super helpful. Both of your suggestions sound good to me and I'll update accordingly.

Perhaps use 2 ^ n rather than 1.5 ^ n, which
would give 196 seconds in total (0, 4, 16, 48, 128), and/or skip the retry at 0
seconds. This would result in 148 seconds with 1.5 or 516 seconds with 2.

I've increased the base of the backoff to 2 in 8d9003d0768fb9415c3854ce8bb45611aa810fa4.
Since the attempts in the stream is supplied on demand, and the backoff just
adds a delay between the request and fulfillment of the demand, the 0 ends up
applying to first attempt (aka the "try") so we try right away, and start
applying delays to each subsequent attempt (aka the "retries").

The logging is added in 8c6f9ecab14fcc1df7465e3a0086231763e6308d. Thanks again
for the review and suggestions! I think this has ended up in a nicer API and
with more useful logging as a result :)

Looks great! Thank you :)


Stackable? aka Tab Stacking

Could these tabs bend to being stacked? Tab stacking or Tab grouping are the buzz words.
See:
https://www.youtube.com/watch?v=drCAiTSAYdc
Also:
https://www.youtube.com/watch?v=eaaYp8544bs
Would be a nice feature indeed! :)

Your example shows this feature being part of part Opera’s tab implementation and not Chrome’s. As such it falls outside of the scope of this project. Please feel free to fork the project and add it there!


Is there any interest in adding UUIDs?

I was looking for a good, compact and efficient way to store UUIDs in Pandas DataFrames. The easy way is as columns of uuid.UUID objects (56 bytes each). Since UUIDs can be represented as 128 bits (16 bytes), it would be nice for a column to be a contiguous array.
As the cyberpandas IPv6 extension array also stores 128 bit wide IP addresses, I was thinking of leveraging the work done here for IPv6 for UUIDs.
Then a future potential step would be to make an extension type that supports any numpy "Sn" fixed width field, with efficient implementations of the low level Pandas array operations, plus a mechanism to easily register various high-level representation and accessor methods (e.g. IPv6, UUID, and so forth).
Tom, maybe can you say how you see this project evolving? Is it essentially "done" as it is today, with IPv4 and IPv6. Or as a place where similar extension arrays can be added, as semi-standard additions to the Pandas ecosystem?
Thanks
Stephen

I don’t really have plans for cyberpandas itself.
There have been some discussions about a numpy-backed extension array mixin, this provides an implementation of things like take, but I don’t know the exact issue.
If you can’t find an issue you might open one in pandas itself.

On Oct 16, 2020, at 17:12, Steve Simmons<EMAIL_ADDRESS>wrote:

I was looking for a good, compact and efficient way to store UUIDs in Pandas DataFrames. The easy way is as columns of uuid.UUID objects (56 bytes each). Since UUIDs can be represented as 128 bits (16 bytes), it would be nice for a column to be a contiguous array.
As the cyberpandas IPv6 extension array also stores 128 bit wide IP addresses, I was thinking of leveraging the work done here for IPv6 for UUIDs.
Then a future potential step would be to make an extension type that supports any numpy "Sn" fixed width field, with efficient implementations of the low level Pandas array operations, plus a mechanism to easily register various high-level representation and accessor methods (e.g. IPv6, UUID, and so forth).
Tom, maybe can you say how you see this project evolving? Is it essentially "done" as it is today, with IPv4 and IPv6. Or as a place where similar extension arrays can be added, as semi-standard additions to the Pandas ecosystem?
Thanks
Stephen
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.


Run-time error/exception due to un-initialized rsa structure

Version: 2.3.0
How to Reproduce:

Open the VC solution
Build and Run rsa_genkey
Build and Run rsa_encrypt with any string argument
Build and Run rsa_decrypt - You can see a memory writing exception thrown out, which occurs when memset the p pointer in function mbedtls_mpi_lset

int mbedtls_mpi_lset( mbedtls_mpi *X, mbedtls_mpi_sint z )
{
    int ret;

    MBEDTLS_MPI_CHK( mbedtls_mpi_grow( X, 1 ) );
    memset( X->p, 0, X->n * ciL );  <==== the program stopped here.
    X->p[0] = ( z < 0 ) ? -z : z;
    X->s    = ( z < 0 ) ? -1 : 1;

cleanup:

    return( ret );
}

Root Cause
in the main function of file rsa_decrypt.c,  the variable rsa is not initialized before mbedtls_mpi_read_file is called.
In the following function we can see X->p pointer will have mem calloced only when X->n < nblimbs.
But as X is not initialized, the X->n has an undefined value. If you are not lucky enough, the n will much bigger than nblimbs and X->p will never got calloced.
int mbedtls_mpi_grow( mbedtls_mpi *X, size_t nblimbs )
{
    mbedtls_mpi_uint *p;

    if( nblimbs > MBEDTLS_MPI_MAX_LIMBS )
        return( MBEDTLS_ERR_MPI_ALLOC_FAILED );

    if( X->n < nblimbs )
    {
        if( ( p = (mbedtls_mpi_uint*)mbedtls_calloc( nblimbs, ciL ) ) == NULL )
            return( MBEDTLS_ERR_MPI_ALLOC_FAILED );

        if( X->p != NULL )
        {
            memcpy( p, X->p, X->n * ciL );
            mbedtls_mpi_zeroize( X->p, X->n );
            mbedtls_free( X->p );
        }

        X->n = nblimbs;
        X->p = p;
    }

    return( 0 );
}

Additional, the rsa_decrypt main function of 2.2.1 version has the initialization mbedtls_rsa_init before mbedtls_mpi_read_file, which is deleted by version 2.3.0.

Verified that commit 6b46c62d erroneously missed a line when moving initialization code in rsa_decrypt.c

ARM Internal Ref: IOTSSL-950


option to disable encoding slashes for url params

fixes #1388

+1
What is the status quo on this PR?

10 - please, please, can we have this sorted. It has been around since 2012 in https://github.com/angular/angular.js/issues/1388 (as pointed out up the top)

I don't think anything is happening with this version of angular anymore.
All the focus is on angular 2
On Mon, Mar 30, 2015, 4:47 AM toddb<EMAIL_ADDRESS>wrote:

10 - please, please, can we have this sorted. It has been around
since 2012 in #1388 https://github.com/angular/angular.js/issues/1388
(as pointed out up the top)

—
Reply to this email directly or view it on GitHub
https://github.com/angular/angular.js/pull/7940#issuecomment-87593719.


Update deactivate legal entity WS

Update deactivate legal entity WS according to requirements
Requirements: https://docs.google.com/document..

[x] Update WS spec
[x] Update WS logic:
- context
[x] Implement
[ ] Improve test scenarios

Improve test scenarios
https://edenlab.atlassian.net/wiki/spaces/EH/pages/14581764/Register+Pharmacy+Test


Add more details to the failure to admit event and condition message

What type of PR is this?
Add the reason for failing to admit a workload in the event and condition message. We can still do more by plumbing reason related to failed to match affinity or taints.
/kind cleanup

/hold

Please fix vet

/lgtm
Maybe you need to squash it.

/hold cancel
/label tide/merge-method-squash


AnimatedVisualPlayer destructor bug [32126845]

This change should fix the internal bug
The problem is that calling IsPlaying(false) inside the AnimatedVisualPlayers destructor causes a crash. Basically, our goal is to reduce a number of things that destructor is doing, ideally nothing. But the problem is that we want to destroy AnimationPlay m_nowPlaying object (if it is alive) as well, but AnimatedVisualPlayer::PlayAsync keeps this object alive, because it holds reference and awaits (co_await *thisPlay;) for it to call CompleteAwaits(). Also we need to release m_batch listener as well, because it holds weak reference to us (line ~130).
So basically, we want to call AnimationPlay ::Complete() but without touching m_owner. But since AnimationPlay calls m_owner only if it is bound to it, we can detach it first, to ensure that we will not call anything in m_owner inside the destructor.

/azp run

/azp run


GroundPrimitive

Use GroundPrimitive instead of Primitive when altittudeMode is set to clampToGround.
Ready for review @gberaudo .

안녕하세요, @oterral
Nice to see you have started to stab this.
Adding GroundPrimitive support and implementing lines on terrain are two different tasks.
The last one needs to be done in Cesium because corridors take meters but we want to use pixels and the conversion depends on the distance. With a fixed ratio, we get the following incorrect reult:

See my other comments.

I agree, using Corridor for outline is not ideal. It's workaround until lines on terrain will be implemented.
For the hardcoded factor.  it will be great if we could do like the scaleByDistance  options of PointPrimitive

@gberaudo I've removed the use of Corridor geometry

@oterral, could you please modify the vector example as suggested in https://github.com/openlayers/ol3-cesium/pull/243#discussion_r39507298?

Yes I'm doing it.

@oterral, the clampToGround mode button does not seem to work. Maybe it does not work when geometries have absolute 3D coordinates? If it is the case, you could add a new 2D polygon feature to the vector example? See examples/data/geojson/vector_data.geojson.

Ok I had not tested I was on windows yesterday and nothing worked

Ok it works now, there was a typo issue and the layer must be remove then re-add. Is there a way to r-render a layer without adding/removing it?

Your workaround is OK. I created an issue
https://github.com/openlayers/ol3-cesium/issues/250.
On Thu, Sep 24, 2015 at 10:50 AM, oterral<EMAIL_ADDRESS>wrote:

Ok it works now, there was a typo issue and the layer must be remove then
re-add. Is there a way to r-render a layer without adding/removing it?
—
Reply to this email directly or view it on GitHub
https://github.com/openlayers/ol3-cesium/pull/243#issuecomment-142860374
.

It looks good now, please merge.

Thx for the review but I can't merge I haven't the right :)

OK, done


Instant search does not show sales for prices

Exactly as the name suggests

Our Ruby install got screwed so update script no longer worked. Search data will be updated soon, thanks!


Add Option and Future performance benchmark

Expected Behavior

There is a Futures and Options performance algorithm benchmark

Actual Behavior

None available, see https://github.com/QuantConnect/Lean/tree/master/Algorithm.CSharp/Benchmarks and https://www.quantconnect.com/performance

Potential Solution

Implement
Reproducing the Problem

N/A
System Information

N/A
Checklist

[x] I have completely filled out this template
[x] I have confirmed that this issue exists on the current master branch
[x] I have confirmed that this is not a duplicate issue by searching issues

[x] I have provided detailed steps to reproduce the issue

Added EmptyEquityAndOptions400Benchmark.cs
Need futures.


I think there's an issue with Advancement in many versions

I think we need to check if the advancement is working in each version. Basically, it should give an advancement the first time you get a wood chessboard in your inventory, but it many versions it gives the advancement whenever you pick anything up (or maybe never). This was reported and fixed as #90 but I think the source of the error is variance in the format (I hope), but either way resulted in an always true or never true criteria.

[ ] Check which versions this applies to
[ ] Fix in each broken version

1.20 is ok.

1.19 is ok.

1.18 is ok

1.17 is ok.

1.15 is ok.

1.14 is ok.


Social Media links of Twitter, facebook, linkedin are not visible.

Social Media links of Twitter, Facebook, Linkedin are not visible after adding into the data.js file. Please fix it.

Can you attach some screenshots, and what you expected.

Social Media icons and links are not visible in Linux Chrome Desktop version.

Expected:
The icons and links should visible.

Wait...These social media links are visible in Android Desktop mode but not in Linux chrome. Could you clarify, what is this happening?


Bug: A strange UI appears on every tab.

A strange UI appears on every tab.

Do you have mov2mov installed?

Yes. If I remember correctly, the cause is that some elem_ids in their components are duplicates of existing ones in the webui, which we are using.

#176


Upgrade cube version initially and once only on client-side

Situation

Each GQL query re-initiates the version upgrade on it's own, even after the version information is already known at the client
Version upgrade is not streamlined across all the different GQL queries (i.e. some use LightCube, others won't)

Motivation

Firing less queries to the SPARQL endpoint helps to improve the general performance. Therefore omitting double queries (i.e. for version upgrade) will help to improve.

DoD

[ ] The cube version information initially queried by the client is reused - suceeding GQL queries rely on that dynamically queried information, therefore no need to re-query for version upgrades.
[ ] The version upgrade functionality is streamlined among all the GQL queries. The recent improved query pattern from getLatestCubeIriQuery is reused therefore.

LGTM 👍


Docs.MS Release Updates for Microsoft.Extensions.Azure

Update docs metadata and targeting for release of Microsoft.Extensions.Azure

Docs Build status updates of commit 7a734a3:
:warning: Validation status: warnings

File
Status
Preview URL
Details

api/overview/azure/microsoft.extensions.azure-readme-pre.md
:warning:Warning
View
Details

api/overview/azure/microsoft.extensions.azure-readme-pre.md

Line 2, Column 1: [Warning-title-missing] Missing required attribute: 'title'. Add a title string to show in search engine results.
Line 2, Column 1: [Warning-ms-prod-and-service] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.
Line 9, Column 16: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'azure' is not valid with 'ms.prod' value 'azure'.
Line 11, Column 13: [Warning-ms-service-subservice-invalid] Invalid value for 'ms.service': 'extensions'.
Line 2, Column 1: [Suggestion-description-missing] Missing required attribute: 'description'.
Line 16, Column 105: [Suggestion-preserve-view-not-set] Did you mean to link to a specific version? It's usually better not to specify a version, so the link always goes to the canonical version. If you really need to link to a specific version, add &preserve-view=true to the URL: https://docs.microsoft.com/aspnet/core/fundamentals/dependency-injection?view=aspnetcore-3.0. Otherwise, remove the view parameter.
Line 16, Column 154: [Suggestion-preserve-view-not-set] Did you mean to link to a specific version? It's usually better not to specify a version, so the link always goes to the canonical version. If you really need to link to a specific version, add &preserve-view=true to the URL: https://docs.microsoft.com/aspnet/core/fundamentals/configuration/?view=aspnetcore-3.0. Otherwise, remove the view parameter.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel


[examples] Added zoom independent sharp edges to the SDF text example

The signed distance field text rendering example uses a fixed "smoothing" value in the shader. This only works well for one specific zoom level and becomes blurry for others. This PR replaces that with a calculation to always get a sharp text outline regardless of the zoom level. This is based on how much the distance to the outline changes from fragment to fragment (aka local derivatives, dFdx, dFdy).
Unfortunately dFdx and dFdy are optional for GLSL 1.00 and I can't test the GLSL 1.00 shader. Without local derivatives a zoom independent "smoothing" value could be calculated as FONT_SDF_PIXEL_DIST_SCALE / 255.0f * drawScale (I think). Where drawScale would be 1.0 if the font is drawn 1:1 and 2.0 when the font is drawn twice as large as the distance field. drawScale could be calculated e.g. as currentFontSize / initialFontSize. But adding all that would make the example quite a bit more complicated and I don't know how relevant the GLSL 1.00 version actually is.

@arkanis Oh! Thanks! This is a very nice improvement! :D


Getting "FixedDataTable expected an ES6 compatible Object.assign polyfill" error

Browser console error gives:
FixedDataTable expected an ES6 compatible Object.assign polyfill.

Try using es6-shim. Solved the issue for me.

@songz like @michaelcarter-wf said you will need an es6 Object.assign shim for the code to work. es6-shim will work, or a light weight option like https://github.com/sindresorhus/object-assign then do Object.assign = require('object-assign'); would also work.
Please let us know if you can think of a more descriptive error message that would help you solve this issue faster.

How can this be fixed when using webpack?
I have installed this package using npm install --save fixed-data-table, then I have the code below, but I am still getting the error. I am not sure if it is something that I need to fix in my webpack config or anywhere else. Any help will be appreciated!
Thanks.
var React = require('react');
var FixedDataTable = require('fixed-data-table');

var Table = FixedDataTable.Table;
var Column = FixedDataTable.Column;

// Table data as a list of array.
var rows = [
  ['a1', 'b1', 'c1'],
  ['a2', 'b3', 'c2'],
  ['a3', 'b3', 'c3'],
  //..... /// and more
];

function rowGetter(rowIndex) {
  return rows[rowIndex];
}

var MyComponent = React.createClass({
  mixins: [FluxMixin, State],

  render: function() {
    return (<Table
      rowHeight={50}
      rowGetter={rowGetter}
      rowsCount={rows.length}
      width={5000}
      height={5000}
      headerHeight={50}>
      <Column
        label="Col 1"
        width={3000}
        dataKey={0}
      />
      <Column
        label="Col 2"
        width={2000}
        dataKey={1}
      />
    </Table>);
  }
});

module.exports = MyComponent;

Just a note to say with #102 the Object.assign polyfill will no longer be needed :)

This does not work with es6 imports somehow :(

It seems like babel (which Im using to to transpile es6 to es5) is moving all module declarations to the top and that is why I cannot do the Object.assign = Object.assign || require('object-assign');
What I ended doing is to paste verbatim the ponyfill in a script in my index.html and it works. But it's a horrible hack and I will love to see #102 merged!

Hey sorry this is such a pain, #102 will be out soon :P If you want in the mean time you can run the objectAssignTransformer yourself which should fix the issue for you, so grab the objectAssignTransformer.js file from the PR then add "plugins": ["./path/to/my/stuff/objectAssignTransformer.js"], to your babel config and that should fix it.

Hi @pieterv no need to apologize :)
Last night I was kind of frustrated, nevertheless now it works and with #102 on the way there is nothing less to be said but what has already been said.
Thanks a lot for all your support.
Fran

Hi there,
After I added Object.assign = Object.assign || require('object-assign'); before require fixed-data-table. the error in browser console is still:  "FixedDataTable expected an ES6 compatible Object.assign polyfill" and plus another error: Uncaught TypeError: Object.assign is not a function
Anyone can help me here?

Hey @cendy172, Update to the new version we just released (0.2.0) and this issue should be fixed, we don't need the polyfill anymore :) Let me know if not.


Improve coverage

Pull Request Test Coverage Report for Build 298

9 of 9 (100.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.7%) to 97.667%

Totals

Change from base Build 296:
0.7%

Covered Lines:
4060

Relevant Lines:
4157

💛  - Coveralls


SVD power method not converging well

https://github.com/h2oai/h2o4gpu/commit/7a7424f7253ea650989b9b5174e8597801d95222#diff-1a13759f63589530199630e07535c1a7R89

Issue here: https://github.com/h2oai/h2o4gpu/blob/master/tests_open/svd/test_tsvd_wrapper.py#L60

@navdeep-G why such tolerance has been taken in np.allclose?


Handles upload with spaces in filename

in order to upload files with spaces in filename, escape the filename if spaces is found.

Seems like a pretty reasonable change. Thanks!


Removed unnecessary files

Task #12

@reynard2007 you can start resolving issues for this now.

The navbar example isn't rendering correctly for me.

Can we fix the width of the searchbar? Also the quicklinks and user dropdown don't have cursor: pointer

These are acknowledged. Will create a new PR for the above and the other requests for updates within the day (PHT).

Closing. To be replaced by PR #37.


Bot not sending Welcome Message first time

Version
V3
Describe the bug
I'm using the ActivityType Conversation Update to send a welcome message to the user.
This was working fine until now, where the bot doesn't send the message the first time anymore. (Neither on the Emulator or in the Web Chat)
This is the code
            else if (messageType == ActivityTypes.ConversationUpdate)
            {
                // Handle conversation state changes, like members being added and removed
                // Use Activity.MembersAdded and Activity.MembersRemoved and Activity.Action for info
                // Not available in all channels
                IConversationUpdateActivity iConversationUpdated = message as IConversationUpdateActivity;
                if (iConversationUpdated != null)
                {
                    ConnectorClient connector = new ConnectorClient(new System.Uri(message.ServiceUrl));

                    foreach (var member in iConversationUpdated.MembersAdded ?? System.Array.Empty<ChannelAccount>())
                    {
                        // if the bot is added, then
                        if (member.Id == iConversationUpdated.Recipient.Id)
                        {
                            var reply = ((Activity)iConversationUpdated).CreateReply(Properties.Messages.welcome_message);
                            await connector.Conversations.ReplyToActivityAsync(reply);
                        }
                    }
                }
            }

When I run the bot on the Emulator and debug the code, it looks like it works fine but no message is sent on the emulator.
When I reload the bot on the emulator (not restarting the app, just clicking on the reload button), the message is sent correctly.
The same behavior happens on the DirectLine (when loading the page the first time, nothing happens, but after reloading, the message is sent correctly.)
How can I fix this?
Thanks!
[bug]
[dotnet]

Hi @clari182
This is a known issue with a workaround described here: https://blog.botframework.com/2018/07/12/how-to-properly-send-a-greeting-message-and-common-issues-from-customers/
There is also a related issue on the WebChat repository:
https://github.com/Microsoft/BotFramework-WebChat/issues/1371
I'm closing this issue, since this is the BotBuilder-V3 sdk repository and the issue is more related to WebChat or the Emulator.  Please follow https://github.com/Microsoft/BotFramework-WebChat/issues/1371 for progress on the fix.


Add mirroring workflow for code signing repository

This PR adds a mirroring workflow that runs every 10 minutes. This is useful for our codesigning repository.
The mirror workflow is gated by a GitHub secret ENABLE_MIRRORING which must be equal to "true" for the workflow to start.

Closing this in favor a having the release process slurp up the the latest on demand rather than keeping a mirror.