Add labels/properties to doc-heading

Is your feature request related to a problem? Please describe.
Previous python handler can add properties of a method (e.g., "staticmethod", "property", "readonly") after the method's signature, but it seems that griffe hasn't have one. Although there is a template html file called "labels.html", which does exactly the same thing as the previous template "properties.html", it is not operational.
I also notice that in the TODO list of Griffe, the first item is "labels". I'm not sure whether that "labels" is what this feature request is asking for. If so, this issue could be closed, and we can just wait for the new feature to be released. Thank you!

Hello @wxdrizzle!
You're right, I didn't reapply the same logic for properties in Griffe. The "labels?" item in the TODO list just means: "what labels can we have on each type of object?". For example, we could have staticmethod, like before, but maybe it should be called static instead? Since it's a decorator, will every decorator become a label on an object? Or just the ones that are built-in or in the standard library? How to let users extend that?
Griffe already sets labels on attributes (module-attribute, class-attribute and instance-attribute), because it was easy to do, but for methods it's a bit more complicated. Well, not really for the classic staticmethod, classmethod and property: the decorator is a single name that we can easily match. But others, like @property_name.setter or @abc.abstractmethod need a bit more of work.
If you are interested in contributing something, I can give you some guidance, otherwise I'll eventually get to it :smile:

Hi again @pawamoy !
I think staticmethod and classmethod will be a good feature to distinguish those methods from other regular methods, although one can directly get that from whether the signature contains no self or contains cls. For me, both staticmethod and static are good.
Adding the label property is also important, but instead we can also simply remove (self) from a property's signature to tell users that they can just use it without a (). For @property_name.setter, maybe the best way is to add a label readonly, but since you said that would need more work, so currently it is sufficient for users to just add "readonly" information in the docstring.
Personally I think Other non-built-in decorators may be another issue, as it may require a context for both users and readers to know what the decorator means. So it may be better if we can provide an option to enable or disable the labels. That could be a long-term plan.
In a nutshell, I'm happy if I can contribute something. I can help add the classic staticmethod, classmethod and property recently, as you said it is not very complicated. For setter and abstractmethod, I'm just not sure if my knowledge is good enough to handle that, but you can also consider to provide some quick guidance and I'm willing to read some tutorials as well. 😉

Great, your help offering is appreciated :slightly_smiling_face:
Let me handle a few decorators/labels first, and once I'm confident this can be further improved, I'll let you know :slightly_smiling_face:

Also passing by to show my interest. If you have any feel for how this could be implemented, I could also give it a go :)

Thanks! I hope I'll be able to get to it soon so I can give you some feedback!

Hey! So, I just pushed version 0.17.0 which brings more labels based on decorators :slightly_smiling_face:

@property gives property label
if there's a property setter, writable label is added
if there's a property deleter, deletable label is added
@staticmethod gives staticmethod label
@classmethod gives classmethod label
@functools.cache, @functools.cached_property and @functools.lru_cache give cached label (and I realize I forgot to add a property label when the decorator is cached_property, will add later). It works with brief and full path (@functools.... and @...)
@abc.abstractmethod gives abstract label (https://github.com/mkdocstrings/mkdocstrings/issues/349)

I think we can close this issue, but please do open issues if you have other ideas for properties! Now that there's basic support it should not be difficult to add more.


Analysis tool leaks memory

See monologue in #147. Something's wrong, need to identify where the problem is.
Start with the same simulation as in the end of aforementioned ticket, then gradually decrease number of the tasks until memory does not stop leaking.

# You can use YAML anchors to substitute some values that repeat several times over the file.
# About YAML anchors: https://support.atlassian.com/bitbucket-cloud/docs/yaml-anchors/
host: &host
  type: slice
  parts: [[0, 0.666666]]
host_color: &host_clr b

satellite: &satellite
  type: slice
  parts: [[0.666666, 1]]
sat_color: &sat_clr r

all_color: &all_clr y

# File with a set of snapshots.
input_file:
  format: fits
  filenames:
    - !env "{WORKING_DIR}/test_out.fits"

# You can specify filename where JSON logs would be saved.
logging:
  level: debug
  filename: !env "{WORKING_DIR}/test_json_log.txt"
  datefmt: "%Y-%m-%d %H:%M:%S"

# Visualizer module configuration. It specifies list of panels.
visualizer:
  output_dir: !env "{WORKING_DIR}/analysis"
  title: "Time: {time:07.01f} Myr"
  pickle_filename: "pickle-{i:03}.pickle"
  figsize: [20, 11]
  pic_filename: "img-{i:03d}.png"
  panels:
    - id: zy_plane
      coords: [0, 0.35, 0.35, 0.6]
      params:
        xlim: [-45, 45]
        ylim: [-40, 40]
        xlabel: "z, kpc"
        ylabel: "y, kpc"
        xticks: [0, 10]
        yticks: [0, 10]
    - id: xy_plane
      coords: [0.33, 0.35, 0.35, 0.6]
      params:
        xlim: [-45, 45]
        ylim: [-40, 40]
        xlabel: "x, kpc"
        yticks: []
        xticks: [0, 10]
    - id: potential_dist_plane
      coords: [0.72, 0.66, 0.14, 0.3]
      params:
        xlim: [0, 50]
        ylim: [0, 3]
        xlabel: "$r$, kpc"
        ylabel: "Potential, portion of the average"
        grid: True
    - id: bound_mass_evolution_plane
      coords: [0.72, 0.33, 0.14, 0.3]
      params:
        xlim: [0, 10000]
        ylim: [0, 3.e+11]
        xlabel: "Time, Myr"
        ylabel: "Bound mass, MSun"
        grid: True
    - id: separation_evolution_panel
      coords: [0, 0, 0.14, 0.3]
      params:
        xlim: [0, 10000]
        ylim: [0, 150]
        xlabel: "Time, Myr"
        ylabel: "Separation, kpc"
        grid: True
    - id: velocity_profile_panel
      coords: [0.18, 0, 0.32, 0.3]
      params:
        xlim: [0, 15]
        ylim: [0, 400]
        xlabel: "$r$, kpc"
        ylabel: "$v$, km/s"
        grid: True
    - id: density_profile_panel
      coords: [0.54, 0, 0.32, 0.3]
      params:
        xlim: [0, 50]
        ylim: [0, 4.e+8]
        xlabel: "$r$, kpc"
        ylabel: '$\rho$, MSun / kpc ** 3'
        grid: True

# List of tasks. Each one describes arguments to its constructor and list of actions.
tasks:
  - name: PotentialCenterTask
    id: host_potential_center
    actions_before:
      - *host
  - name: PotentialCenterTask
    id: sat_potential_center
    actions_before:
      - *satellite
  - name: PotentialCenterTask
    id: total_potential_center

  - name: ScatterTask
    args: &args
      expressions:
        x: "x"
        y: "y"
        z: "z"
        m: "m"
      units:
        x: !q [1, kpc]
        y: !q [1, kpc]
        z: !q [1, kpc]
        m: !q [1, MSun]
    actions_before:
      - *host
      - type: barion_filter
    actions_after:
      # You can plot one result several times in different projections.
      - type: visualizer
        id: xy_plane
        is_density_plot: True
        resolution: 700
        extent: [-45, 45, -40, 40]
        channel: *host_clr
        x: x
        y: y
        weights: m
      - type: visualizer
        id: zy_plane
        is_density_plot: True
        resolution: 700
        extent: [-45, 45, -40, 40]
        channel: *host_clr
        x: z
        y: y
        weights: m
  - name: ScatterTask
    args: *args
    actions_before:
      - *satellite
      - type: barion_filter
    actions_after:
      - type: visualizer
        id: xy_plane
        is_density_plot: True
        resolution: 700
        extent: [-45, 45, -40, 40]
        channel: *sat_clr
        x: x
        y: y
        weights: m
      - type: visualizer
        id: zy_plane
        is_density_plot: True
        resolution: 700
        extent: [-45, 45, -40, 40]
        channel: *sat_clr
        x: z
        y: y
        weights: m
  - name: ScatterTask
    args: *args
    actions_before:
      - type: slice
        id: 0
    actions_after:
      - type: visualizer
        id: xy_plane
        linestyle: solid
        color: *host_clr
        marker: o
        markersize: 5
        x: x
        y: y
      - type: visualizer
        id: zy_plane
        linestyle: solid
        color: *host_clr
        marker: o
        markersize: 5
        x: z
        y: y
  - name: ScatterTask
    args: *args
    actions_before:
      - type: slice
        id: 1000001
    actions_after:
      - type: visualizer
        id: xy_plane
        linestyle: solid
        color: *sat_clr
        marker: o
        markersize: 5
        x: x
        y: y
      - type: visualizer
        id: zy_plane
        linestyle: solid
        color: *sat_clr
        marker: o
        markersize: 5
        x: z
        y: y

  - name: PotentialTask
    inputs:
      center: host_potential_center.position
    actions_before:
      - *host
    actions_after:
      - type: visualizer
        id: potential_dist_plane
        linestyle: None
        color: *host_clr
        label: host
        x: radii
        y: potential
  - name: PotentialTask
    inputs:
      center: sat_potential_center.position
    actions_before:
      - *satellite
    actions_after:
      - type: visualizer
        id: potential_dist_plane
        linestyle: None
        color: *sat_clr
        label: satellite
        x: radii
        y: potential
  - name: PotentialTask
    inputs:
      center: total_potential_center.position
    actions_after:
      - type: visualizer
        id: potential_dist_plane
        linestyle: None
        color: *all_clr
        label: all
        x: radii
        y: potential

  - name: BoundMassTask
    args:
      number_of_iterations: 5
    actions_before:
      - *satellite
    actions_after:
      - type: visualizer
        id: bound_mass_evolution_plane
        linestyle: solid
        color: r
        x: times
        y: bound_mass
      - type: logging
        print_last: True
        id: bound_mass_data

  - name: DistanceTask
    inputs:
      start: host_potential_center.position
      end: sat_potential_center.position
    actions_after:
      - type: visualizer
        id: separation_evolution_panel
        linestyle: solid
        color: r
        x: times
        y: dist

  - name: VelocityProfileTask
    inputs:
      center: host_potential_center.position
      center_vel: host_potential_center.velocity
    actions_before:
      - *host
    actions_after:
      - type: visualizer
        id: velocity_profile_panel
        markersize: 0.5
        linestyle: None
        color: *host_clr
        label: host
        x: radii
        y: velocity
  - name: VelocityProfileTask
    inputs:
      center: sat_potential_center.position
      center_vel: sat_potential_center.velocity
    actions_before:
      - *satellite
    actions_after:
      - type: visualizer
        id: velocity_profile_panel
        markersize: 0.5
        linestyle: None
        color: *sat_clr
        label: satellite
        x: radii
        y: velocity
  - name: VelocityProfileTask
    inputs:
      center: total_potential_center.position
      center_vel: total_potential_center.velocity
    actions_after:
      - type: visualizer
        id: velocity_profile_panel
        markersize: 0.5
        linestyle: None
        color: *all_clr
        label: all
        x: radii
        y: velocity

  - name: DensityProfileTask
    inputs:
      center: host_potential_center.position
    actions_before:
      - *host
    actions_after:
      - type: visualizer
        id: density_profile_panel
        markersize: 0.5
        linestyle: None
        color: *host_clr
        label: host
        x: radii
        y: densities
  - name: DensityProfileTask
    inputs:
      center: sat_potential_center.position
    actions_before:
      - *satellite
    actions_after:
      - type: visualizer
        id: density_profile_panel
        markersize: 0.5
        linestyle: None
        color: *sat_clr
        label: satellite
        x: radii
        y: densities
  - name: DensityProfileTask
    inputs:
      center: total_potential_center.position
    actions_after:
      - type: visualizer
        id: density_profile_panel
        markersize: 0.5
        linestyle: None
        color: *all_clr
        label: all
        x: radii
        y: densities

Removed scatter tasks

analysis2.txt

Removed velocity profile task
analysis3.txt

Removed density profile tasks

analysis4.txt

Removed distance task

analysis5.txt

Removed potential tasks
analysis6.txt

Removed potential center tasks
analysis7.txt

Removed bound mass task (no tasks left)
analysis8.txt

Seems like there is something else that leaks memory


Add watch script

Added a npm script that enables hot reloading for vue in electron.

Isn't the "dev" script sufficient or am I missing the point ?


Update Octopus to deploy PowerBI XMLA file

Jira Description
None
Jira Metadata
Key: BIA-41
Epic: n/a
Created: 2017-03-15T14:21:07.000-0500
Reporter: Dean Goodman

Jira Comment
Moved from CODS project to BIA project.
Jira Metadata
Created: 2017-03-30T13:50:24.603-0500
Commenter: Dan Malagari


request operation

the request is a 'put' and should be a 'delete'

Are you referring to the delete user API call?  It is already a delete.  See below:
Delete API Call
deleteResponse = requests.delete(......


[Change Request]: Reuse initialization logic for Core Repository from Cosmos ecosystem

Summary
We implement Core initialiazation, when it is technically possible to reuse it.
Gain
We don't need to maintain a piece of a code that is already implemented by 3rd parties.
Evidence
N/A
Implementation ideas
We should wait until Core(Tendermint) or Cosmos will provide reusable functions to accomplish this. Then simply swap out custom logic with theirs.
Urgency
Low

Can we close this? Or what is the plan with this issue?

Let's close for now


fix: undefined functions when compiling on MinGW

Fixes #25 by including conio.h, when a mingw platform.

replaced by #27


[RFE] Add debugging facilities for EmbeddedAnsible (w/ansible-runner)

There is very little transparency currently with EmbeddedAnsible now that we are using ansible-runner directly instead of deferring to AnsibleTower/AWX.  Currently, if something goes wrong, unless it is available in the output for the ansible STDOUT/JSON output, it won't be made apparent to the end user via the UI or even the logs.  Even still, it is possible that even if there was STDOUT/JSON output, it won't make it to the UI if the playbook failed/timedout, which is even worse as that information is valuable in troubleshooting the root cause.
An example of this is a misconfigured SSH auth might cause the playbook run in ansible-runner to timeout when asking for a SSH password to auth with for a given host, but that might not be reflected in the output presented to the user, and is only noticable when looking at the ansible-runner directory that was generated for that given run.
A temp solution for debugging the above scenario is to comment out this line:
https://github.com/ManageIQ/manageiq/blob/44fae8494b1e31720196a9eb079fa01bab9b859d/lib/ansible/runner/response_async.rb#L37
Restart the appliance, and then looking at the /tmp directory to view the artifacts of the given run in question (which is usually in a generated /tmp/ansible-runner* dir and is not easy to track down, and definitely not an appropriate solution for a development environment.
Simply a DEBUG toggle might be a decent first step that would avoid running the cleanup_filesystem! command on that given run, and allow for inspection to determine further action.  Taking it further, presenting that data in the UI might also avoid needing to SSH, but possible just making this an option for admins might be the more secure option to start and determine a more tactical approach for end users in the future.

I realize that this RFE is for the general case, however if we know specific cases can be solved by looking at data from the directory, can we code that in?

An example of this is a misconfigured SSH auth might cause the playbook run in ansible-runner to timeout when asking for a SSH password to auth with for a given host, but that might not be reflected in the output presented to the user, and is only noticable when looking at the ansible-runner directory that was generated for that given run.

So in this example, what exactly in the directory is noticable, and if that noticable thing is well defined, then I think we can code up fetching that information as part of the Ansible::Runner run itself.  Asmittedly, this doesn't really solve the general case, but IMO, the general case is the safety net, but "known" cases should be coded for.

So in this example, what exactly in the directory is noticable, and if that noticable thing is well defined

In this case, generally you are looking at the env/passwords to see what was defined in the YAML for the regexp for:

is there an entry for "^SSH [pP]assword"?
is it correct?
is it blank?

Or did we write the proper args to ansible_runner to ask for the passwords, which you have to check the command line file for, or was there an SSH key passed? So there is a bunch of places that I check around when debugging.  That said, some of it most likely could be extracted, but generally having a mechanism which doesn't require me to tell customers "comment out this line here to debug, and restart" would be ideal.
(also, FYI:  s/noticable/noticeable/ )


Fix Logging Levels

If a user supplies both verbose and debug flags, this fixes the logic and selects the lower level of logging.
(if you did --debug and -v it would just give the info and none of the debug messages)

Nice catch. thanks! 😃


Permitted Actions

Seems like the table above reflects a limited number of actions that Security Admins can complete.  Is there a way to include a listing of all the actions a Security Admin can execute?

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

ID: 8c61e7b5-619a-fbd4-c7de-a1d04a33e61f
Version Independent ID: c35c73d4-42d5-eb01-bb54-6c9c2ad9377a
Content: Permissions in Azure Security Center
Content Source: articles/security-center/security-center-permissions.md
Service: security-center
GitHub Login: @memildin
Microsoft Alias: memildin

@MarileeTurscak-MSFT
Thanks for your feedback! We will investigate and update as appropriate.

@MarileeTurscak-MSFT, thanks for the question.
I think you'll find all the information to answer this question on this page of the Azure RBAC documentation: Azure built-in roles > Security Admin.
Please let us know if there's anything else we can help with.
#please-close


Versioning an Entity can throw an "Index 0 out of bounds for length 0" exception

Originally posted by @pilasou in https://github.com/DSpace/dspace-angular/issues/3069#issuecomment-2127611363
Describe the bug

I have tested the fix in #3069 and thought it worked for a standard Item (I am redirected to the form for the new version), when trying to create a new version of an item with relations, I get an error message (for reference: I used a standard Item part the dataset provided by DSpace: http://localhost:4000/entities/publication/1974d7d3-9648-4dbe-b083-56374f5314e4):
Error from chrome dev tool:

DSpace backend log error:
pr3069-backendlog-error.txt

Related work
This error appears to be directly related to the error discovered/fixed in
https://github.com/DSpace/DSpace/pull/9509
If you look closely, the error stacktrace is showing the same java.lang.IndexOutOfBoundsException: Index 0 out of bounds for length 0 resulting from the same line of code (at org.dspace.content.DSpaceObjectServiceImpl.addMetadata(DSpaceObjectServiceImpl.java:318))

I've verified that this ticket is fixed by the backend PR https://github.com/DSpace/DSpace/pull/9509


Support PrefixOp expressions.

Add support for the PrefixOp expression.

https://docs.circom.io/circom-language/basic-operators/#arithmetic-operators

@brech1 I have a wip branch here but I've run into some questions/issues:

Should new unary gates be supported in the output format? Or should we be compiling to the existing format somehow?
a. Is the format specified somewhere?
How should -x (ExpressionPrefixOpcode::Sub) be handled? Should a u32 underflow? Or perhaps emit a compilation error?

Thank you for bringing this up, so I think the supported gates are determined by our backend target, and so far in mpz these are available:

pub enum ArithGateType {
    /// Addition gate.
    Add,
    /// Subtraction gate.
    Sub,
    /// Multiplication gate.
    Mul,
    /// Constant multiplication gate.
    Cmul,
    /// Unary projection gate.
    Proj,
}

So perhaps we should update the gates we're supporting. This is also related to this comment @namnc left in the overview. There is no defined format.

If an assignment to a gate is only -x I think it would be equal to 0 - x so perhaps declaring a constant 0 as the other gate input for a subtraction gate. I think this and other cases should be handled individually in a new handle_prefix_op function, if it gets too long.

For simplicity let's (for now) stick to binary gate and have x = 0 - x for negation.

Point 2 is another issue itself. Rigft now we consider only u32 (behind the scene we do wraparound so -p becomes M-P with M being the bound of the value) but we should also consider i32? This is related to typing.

For simplicity let's (for now) stick to binary gate and have x = 0 - x for negation.

And what should we do regarding the amount of gates we're supporting (more than the supported by the backend)? Should the backend handle this? Perhaps MP-SPDZ have a broader support?

Point 2 is another issue itself. Rigft now we consider only u32 (behind the scene we do wraparound so -p becomes M-P with M being the bound of the value) but we should also consider i32? This is related to typing.

Even if we add the i32 type we have to handle overflows and underflows on unsigned. We could add a configurable mod integer so we can implement modular arithmetic with it, this would only be applied on integer operations.

https://github.com/namnc/circom-2-arithc/pull/50

The PrefixOp does not seem to be consistent with the InfixOp's behavior due to potential signal name reusage:
e.g. given a and b that are signals, writing a += b is equivalent to a <== a + b, but we shouldn't have this in circom.
We can do either:

allow only this for variables
define a proper scheme to support signal name reusage in circom (this is a circom extension)

@namnc I'm confused, what does a += b have to do with prefix ops?

yeah may be you are right lets make a separate issue for this, my bad


Add missing 'ffe-' prefix to example in ffe-icons

Minor fix in the documentation, add missing ffe- prefix to the example so copy & paste works when getting started with ffe :smile:

Coverage remained the same at 81.008% when pulling 2dc978375ec8f4064e1babf2e38b528e34d70b2e on ffe-icons-missing-ffe-prefix into f865b4b1fcd25ad112bd0ca637dbfc09bc69a061 on develop.


SDA-4652 add list oidc providers

Closes : https://issues.redhat.com/browse/SDA-4652
Usage :

rosa list oidc-providers
rosa list oidc-providers -c <<cluster-id>>

Marked as draft until https://gitlab.cee.redhat.com/service/uhc-clusters-service/-/merge_requests/3301#note_2823437 is merged.


Fixed tqdm log messages and other bugs

This fixes double log messages while the tqdm progress bar is active and a "TypeError" in Mouser dist_define_locale_currency on Python 2.
The file "globals.py" was renamed to "global_vars.py" to avoid a name clash with the builtin "globals()" Python function.
Fixes #193.

Nice! This issue was boring me up.


DocsArchive-<IP_ADDRESS>Auto archive content

Please don't merge this PR until target archive repo PR https://github.com/OPS-E2E-PPE/docs-yml-archive-non-versioning-archive/pull/341 is merged into live branch.
Auto archive content to https://github.com/opstest2/docs-yml-archive-non-versioning-archive.git

Docs Build status updates of commit ff8365e:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

.openpublishing.redirection.json
:white_check_mark:Succeeded

docs/TOC.yml
:white_check_mark:Succeeded
View

docs/to-be-archive/level1/article3-1-1.md
:white_check_mark:Succeeded
View

docs/to-be-archive/level1/article3-1-2.md
:white_check_mark:Succeeded
View

docs/to-be-archive/level1/article3-1-3.yml
:white_check_mark:Succeeded
View

docs/to-be-archive/level2/article3-2-1.md
:white_check_mark:Succeeded
View

docs/to-be-archive/level2/article3-2-2.md
:white_check_mark:Succeeded
View

docs/to-be-archive/level2/article3-2-3.yml
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
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.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


两层iframe嵌套，在hash模式下，第二层iframe不渲染

由于项目的特殊性，要涉及到iframe的多级嵌套使用，我在home页面使用iframe加载detail页面，在detail页面使用iframe加载detail2页面,hash模式，detail2页面根本不加载，而history模式就可以，这个是vue-router本身限制，还是浏览器问题？

路由

home.vue

detail.vue

detail2.vue

Hi, thanks for your interest but Github issues are for bug reports and feature requests only. You can ask questions on the forum, the Discord server or StackOverflow.

是浏览器限制

Infinite recursion is prevented. Any frame that attempts to assign as its SRC a URL used by any of its ancestors is treated as if it has no SRC URL at all (basically a blank frame). This doesn't prevent all malicious documents, but it eliminates a troublesome class of them.

see w3.org/TR/WD-frames-970331


[Enhancement] Support workflow style open metadata elements

Is there an existing issue for this?

[X] I have searched the existing issues

Please describe the new behavior that that will improve Egeria
The following OMASs do not return the instance status in their ElementHeader.

Asset Consumer OMAS
Asset Manager OMAS
Asset Owner OMAS
Community Profile OMAS
Data Manager OMAS
Digital Architecture OMAS
Governance Program OMAS
IT Infrastructure OMAS
Security Manager OMAS
Stewardship Action OMAS

This has not mattered until now because the elements we have been dealing with have a valid status list of {ACTIVE, DELETED}.  However we how have use cases in progress that are working with elements that have a workflow-style list of InstanceStatus and the caller needs to know the current status of these elements in order to determine which step they are at.
Examples of open metadata types that have a workflow-style lifecycle:

ControlledGlossaryTerm
DigitalService
GovernanceDefinition

The proposal is to extend the ElementHeader in these OMASs (and their corresponding converter) to include and populate this value.
This change also provides a base for adding the ability to restrict searches based on the instance status.  However, that will require an enhancement to the generic handlers.
Alternatives
No response
Any Further Information?
No response
Would you be prepared to be assigned this issue to work on?

[ ] I can work on this

As part of this change I have enhanced the Asset Manager FVTs to test the management of controlled glossary terms as they move through there lifecycle states.  This uncovered some issues in the glossary exchange server-side support relating to the converter that retrieve the glossary beans.  The fixes are included in this change.

I also changed the API and property bens in Governance Program OMAS since the status field was included in the properties bean.  This is now passed separately on the APIs and returned in the header.  This removes any confusion as to how the status is managed.


Muxed WebM Opus audio file is not seekable

Thanks for your work on providing a WebM muxer for WebCodecs!
I've been prototyping a WebM Opus transcoder with this and it looks like the resulting WebM Opus file is not seekable in any of the playback software I've tried.
Repro code: webMOpusTranscoder.zip (just host on a local web server or something)
Note this is developed against Chrome Canary 94.0.4579.0 with Experimental Web Platform features enabled, so there may be some API differences to different Chrome versions. I also work on Windows 10 x64.
You'll need a sample audio file as well, which can be any reasonably long audio file the browser can decode - try this if you need one: https://www.dropbox.com/s/jnw8cyn75x67mlk/oglseby7.wav?dl=0
When you open the repro HTML file, drag and drop an audio file to transcode into the dashed box. Check the browser console; it will log some messages about what it's doing (which involves using Web Audio to decode the file; WebCodecs to encode it to Opus; and then muxes to WebM) and then invoke a download of a file named audio.webm. The end result is the dropped audio file is transcoded to WebM Opus.
The produced WebM file plays fine, but does not appear to be seekable. I've tried Windows 10's 'Films & TV' app (the default), Chrome, MPC-HC, and VLC. I don't know much about the WebM format but I believe there is extra data required to be added by the muxer to enable seeking. It would be great if that could be supported.

@AshleyScirra thanks for picking this up. I'll try to take a look in the next couple of days.

OK I modified your program slightly for older Chrome (91.0.4472.114 Linux). This produces a seekable WebM file:

import * as Utils from "./utils.js"

//////////////////////////////////////
// Drag and drop handling
const dropElem = document.getElementById("dropzone");
dropElem.addEventListener("dragover", e => e.preventDefault());
dropElem.addEventListener("dragenter", e => dropElem.classList.add("hover"));
dropElem.addEventListener("dragleave", e => dropElem.classList.remove("hover"));
dropElem.addEventListener("drop", e =>
{
	e.preventDefault();
	e.stopPropagation();

	dropElem.classList.remove("hover");

	TranscodeAudio(e.dataTransfer.files[0]);
});

//////////////////////////////////////
// WebM worker
const muxedDataChunks = [];
let startResolve = null;
const startPromise = new Promise(resolve => startResolve = resolve);

const webMWorker = new Worker("./muxer/webm-worker.js");
webMWorker.onerror = (err => console.error("[WebM worker] Error: ", err));
webMWorker.onmessage = (e =>
{
	const msg = e.data;
	switch (msg.type) {
	case "exit":
		console.log("[Message from WebM worker] Exit");
		OnWebMMuxerDone();
		break;
	case "start-stream":
		startResolve();		// resolve startPromise
		break;
	case "muxed-data":
		console.log("[Message from WebM worker] Received muxed data");
		muxedDataChunks.push(msg.data);
		break;
	case "error":
		console.error("[Message from WebM worker] Error: ", msg.detail);
		break;
	}
});

//////////////////////////////////////
// Transcoding
// Create AudioContext just for decoding
const audioContext = new AudioContext({
	sampleRate: 48000		// match Opus sample rate
});

// Create AudioEncoder
const audioEncoder = new AudioEncoder({
	output: AudioEncoderOutput,
	error: AudioEncoderError
});

async function TranscodeAudio(file)
{
	// Use browser to demux and decode audio data to Float32Arrays
	const fileArrayBuffer = await file.arrayBuffer();
	const audioBuffer = await audioContext.decodeAudioData(fileArrayBuffer);

	// Dump channels in to one big Float32Array in planar arrangement
	const planarData = new Float32Array(audioBuffer.length * audioBuffer.numberOfChannels);
	for (let i = 0; i < audioBuffer.numberOfChannels; ++i)
	{
		planarData.set(audioBuffer.getChannelData(i), i * audioBuffer.length);
	}

	// Start up WebM encoder worker
	webMWorker.postMessage({
		type: "start",
		webm_metadata: {
			max_segment_duration: BigInt(1000000000),
			audio: {
				sample_rate: audioBuffer.sampleRate,
				channels: audioBuffer.numberOfChannels,
				//bit_depth: 32,		// ?
				codec_id: "A_OPUS"
			}
		}
	});

	// Wait for "start-stream" message from WebM encoder
	await startPromise;

	// Configure audio encoder for this audio track
	audioEncoder.configure({
		codec: "opus",
		sampleRate: audioBuffer.sampleRate,
		numberOfChannels: audioBuffer.numberOfChannels
	});

	// Create an AudioData for the entire audio content
	const audioData = new AudioFrame({
		/*format: "FLTP",		// planar float32 data
		sampleRate: audioBuffer.sampleRate,
		numberOfFrames: audioBuffer.length,
		numberOfChannels: audioBuffer.numberOfChannels,*/
		timestamp: 0,
		//data: planarData
        buffer: audioBuffer
	});

	// Encode it then finish WebM worker
	console.log("Encoding...");

	audioEncoder.encode(audioData);
	await audioEncoder.flush();

	console.log("Finished encoding, finishing muxer...");

	webMWorker.postMessage({ type: 'end' });
}

function AudioEncoderOutput(chunk, metadata)
{
	//console.log("Audio encoder output received");

	// Copy out encoded audio data and send it to WebM muxer
	//const data = new ArrayBuffer(chunk.byteLength);
    //chunk.copyTo(data);
    const data = chunk.data.slice(0, chunk.byteLength);

	webMWorker.postMessage({
		type: "audio-data",
		timestamp: chunk.timestamp,
		duration: chunk.duration,		// not sure Canary is setting chunk.duration...
		is_key: true,
		data
	}, /* transfer */ [data]);
}

function AudioEncoderError(err)
{
	console.error("Audio encoder error: ", err);
}

function OnWebMMuxerDone()
{
	// Create blob of all muxed data chunks and download it
	const blob = new Blob(muxedDataChunks, { type: "audio/webm" });
	Utils.Download("audio.webm", URL.createObjectURL(blob));
}

Ah interesting! It's seekable using the built-in Ubuntu player but not using VLC!

OK this might give us a clue: https://bugs.chromium.org/p/chromium/issues/detail?id=642012
Although it's for MediaRecorder, it does say that there would need to be a cues section in the generated WebM file. I'm not sure whether AudioEncoder adds that.

Ah
https://github.com/davedoesdev/webm-tools/blob/707b903f622ddc3585c2f3090c42936f45fa2d17/shared/webm_chunk_writer.h#L49
I'm using WebM tools live muxer and chunk writer so as the comments indicate it's not going to be seekable.
Totem is probably using a hack similar to the one suggested chromium bug above (read all the data in first).
This would need an alternative mode of encoding that doesn't use the WebM tools code. I'm not sure I have time to do that. Perhaps I should rename this repo webm-live-muxer.js as my ultimate aim is to use it to stream to YouTube via HLS.
Another possibility is to port https://github.com/legokichi/ts-ebml or https://github.com/node-ebml/node-ebml to work in the browser. They can convert an unseekable WebM (such as MediaRecorder, or webm-muxer.js, produces) into a seekable one.
@AshleyScirra let me know what you think.

Ooh, this comment:
https://github.com/muaz-khan/RecordRTC/issues/147#issuecomment-459954869
suggests that RecordRTC uses https://www.webrtc-experiment.com/EBML.js to get a seekable file.
I wonder if it would work for your approach too @AshleyScirra ?

This confirms I'm on the right lines here: https://stackoverflow.com/questions/66480784/not-able-to-create-seekable-video-blobs-from-mediarecorder-using-ebml-js-media
I'm not sure whether this should be part of webm-muxer.js or another demo?

Thanks for looking in to this. It seems reasonable to use a post-processing step that modifies the output WebM to add seek information. While a transcoder knows in advance the size of the media it's working with so presumably could add seek information in advance, doing it as a post-process step covers both transcoding and unknown-length cases like live streaming and MediaRecorder (which we also use in some other places... so it would be handy to cover that too). So it seems like a more general-purpose solution, and not supporting that in this project would be a fair conclusion.

I'll add a demo to show post-processing

Demo extended with recording and conversion to seekable format using EBML.js
README updated

Note, AudioData replaced the deprecated AudioFrame, 'f32-planar' replaced 'FLTP' format in latest Chromium though the specification has not been updated to reflect that change.

@guest271314 thanks. I'll work on updating to AudioData when I get time - hopefully later this week.

Updated to AudioData for unencoded PCM in e2a6875595e5c7bf131610adde641aad15143992


feat(ingest): powerbi # store powerbi entity descriptions

Store description fields of Datasets, Reports and Dashboards from PowerBI REST API to ingested data. Showing the possible description of the entity in Datahub improves visibility and adds value to Datahub as there's no need to jump to other system just to see the documentation.
Checklist

[ ] The PR conforms to DataHub's Contributing Guideline (particularly Commit Message Format)
[ ] Links to related issues (if applicable)
[ ] Tests for the changes have been added/updated (if applicable)
[ ] Docs related to the changes have been added/updated (if applicable). If a new feature has been added a Usage Guide has been added for the same.
[ ] For any breaking change/potential downtime/deprecation/big changes an entry has been made in Updating DataHub

(Rebased on latest master)

I like that we are correctly extracting descriptions - totally jive with that. But why are we inserting the display name at the top? Feels a bit odd to change the description at all prior to ingestion? Hoping to gain answer before we merge this

After syncing with @mohdsiddique , we agree that we should first remove any additional formatting from the description before merging this PR.
Thanks
John

Originally I kept the entity name in the description field just because it was there before my changes. Now I think the common consensus lies in the fact that there shouldn't be entity name in the description field. I think that's the only way to not use any formatting in the description field and keep the data readable. Certainly that makes a lot of sense. So, thinking from this point of view, would the PR be more mergeable if I just remove the formulate_description function and use only the description field content everywhere?


Stack unstackable items and stackable items past 64

Reproduction
Throw two of the same unstackable item on the ground and pick it up. You will get a stack of 2.
Throw a stack of 64 and a single item of a stackable item on the ground and pick it up. You will get a stack of 65.
If you attempt to pickup a stack higher than 127, it will disappear. Minecraft can only handle stacks below 128.
Video guide: https://www.youtube.com/watch?v=OHPk7LSOlrc

Yes, item collection is a bit messed up at the moment. I'll get to fixing this later tonight.


Not able to deploy this component

Hello all,
i'm triing to deploy this as a Greengrass component via IoT Greengrass deployments. As I already observed this is not part of the "Greengrass software catalog" e.g. gdk component list --repository is not showing it.
So i was wondering how I will be able to create a component? Is there any documentation about it?

Hi there - I have been adding components by manually adding the recipe.yaml file from 'AWS IOT' 'Greengrass Devices' 'Components' 'My Components' 'Create Component'
However, this one fails for me because 'secrets.jar' isn't a proper URI.  I tried creating an S3 bucket and putting that path there, but then the whole deployment fails since secrets.jar can't be found in the S3 bucket.  No idea where that's supposed to come from; I was rather hoping it would come from this component.  :) (Values "", or "/greengrass/etc etc" also failed.  I haven't found any references to this whole chain of components in the wild, so I'm wondering if we're the first two people to ever try it..

Hi,
thanks for your interest in using this component. I realize the README is not clear enough in regards on how to upload those component. We will work to provide clearer instructions. In the meanwhile please have a look at the instructions provided in BUILD.md


See also\Types links to C# Keywords

The point Types in See also chapter links to C# Keywords.

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

ID: 8a2663a9-16e5-31b7-4841-3f574871b047
Version Independent ID: 471e5c1c-1f4a-a23a-b791-bbae59fe712d
Content: Pointer Conversions - C# Programming Guide
Content Source: docs/csharp/programming-guide/unsafe-code-pointers/pointer-conversions.md
Product: dotnet-csharp
Technology: csharp-advanced-concepts
GitHub Login: @BillWagner
Microsoft Alias: wiwagn

Probably the best thing to do here is to replace this link with two links, the value types and reference types.

Thanks @Youssef1313 That is a good recommendation.


Cypress: migrate to version 12

Cypress v12 is out, but deprecates the Cypress.Cookies.preserveOnce, so that needs to be migrated when upgrading.
https://docs.cypress.io/guides/references/migration-guide#Migrating-to-Cypress-12-0

This has been done


Drop requests with unknown host headers

We had a report that Clojars responds to unknown host headers. We should drop requests that don't match headers that we expect: https://stackoverflow.com/a/28591245/826486

  # If the host isn't for Clojars then reject it.
  # If we return 444 then the connection is immediately closed.
  # This shows up as a 502 error on the load balancer which
  # is probably not ideal. Instead we return 418 (I'm a Teapot).
  if ($host !~* ^(repo|app)\.clojars\.org$ ) {
    return 418;
  }

I have something similar to this for Deps, we just need to tweak the regex, probably to just .*.clojars.org.


Set firefox about as floating window

Small fix

Why

About boxes, "Save as" dialog windows usually are opened in floating mode
by default. 😁
See picture...
сре, 1. јул 2020. у 01:57 drake-newell<EMAIL_ADDRESS>је
написао/ла:

Why
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/LukeSmithxyz/dwm/pull/97#issuecomment-652108053, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ACXTAP33TCDWVYQ5LVLMEZTRZJ3W5ANCNFSM4OMUTXQQ
.


Adding some path functions

I've tried to add the functions I talked about in #871, mirroring the standard library functions from Path.
I've added a bunch of tests, but I haven't updated the documentation.
I'm looking forward to getting this pull request reviewed because it will be my first rust contribution if it gets merged.
For the very same reason, it could be non-optimal or straightforward.
Closes #871.

Awesome, thanks for tackling this! I probably won't be able to take a look at this today, but I should have time tomorrow. In the meantime, it looks like there are some errors from clippy on CI.

Awesome, thanks for tackling this! I probably won't be able to take a look at this today, but I should have time tomorrow. In the meantime, it looks like there are some errors from clippy on CI.

Managed it, thanks!

Just took a quick look, and overall I think it looks good. You're running into a lot of the things that make Rust painful, for example, the fact that paths might not be valid Unicode.
I think one thing that might make this a whole lot nicer is if you use camino's Utf8Path type. That way, you can do Utf8Path::new(argument), which will always succeed, and thereafter you won't have to deal with the error case of non-unicode paths.
The other thing that would be nice would be to de-deuplicate these format calls:
    .ok_or_else(|| {
      format!(
        "Cannot get file stem from {}",
        if file_path.is_empty() {
          "an empty string"
        } else {
          file_path
        }
      )

I'm not entirely sure what the best way to do this would be, but you could do something like:
fn extraction_error_message(part: &string, path: &Utf8Path) -> String {
  format!("Cannot extract {} from `{}`, part, path)
}

If the path is set in backticks, then I think:
Cannot extract X from ``

Is a good error message.

Actually, you could skip the function and just put format!("Cannot extract file stem from {}, path). Without the if … { … } else { … } I don't think it's complicated enough to deserve a function.

Also, thanks for adding tests! That's something that a lot of people forget to do.

Also, thanks for adding tests! That's something that a lot of people forget to do.

My pleasure. I reimplemented the functions using camino and simplifying the error handling. I'm totally not sure about dependency management. Am I supposed to commit the Cargo.lock file too?

And btw compliments for the functions "interface", adding functionality (even coming from a totally different language like Scala) was pretty trivial since it is really well designed ;)

Looking better! A few more comments.
As for the lock file, yes, that should be committed. The general rule is that for binary crates, such as just, the lockfile should be committed so that builds are reproducible. For library crates, the lockfile shouldn't be committed, since it's up to the binary crate that the library is eventually included in to determine dependency versions to use.

Makes totally sense

Not sure if you saw, but I added some comments in-line, for example.

Not sure if you saw, but I added some comments in-line, for example.

Yes, I read the previous comment from the phone, and it hid the in-line comments. I think I addressed them all now.

Looks great! How about using consistent language in all the error message, so:
Cannot extract X from `{}`

Also, instead of:
Cannot extract file_stem from `{}`

How about:
Cannot extract file stem from `{}`

Typo, my bad. Is this okay?

Ahhh, damn, sorry, I forgot to hit the "submit review" button, so you couldn't see any of them.

Just applied everything and verified locally that both tests and clippy are good

Great, looks good, although I think there's a formatting issue.

Merged!


Add README for OpenSearch

Signed-off-by: TheAlgo<EMAIL_ADDRESS>Description
Add installation instructions and configuration details for OpenSearch chart.
Issues Resolved
#15
Check List

[X] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

@DandyDeveloper @smlx @peterzhuamazon Have a look at this PR when free. Thanks

@DandyDeveloper Have a look when free. Thanks

@peterzhuamazon I have addressed your comments. Have a look when free. Thanks


Fix distributed aggregative query error

Fix issue #4937  issue #4965
When distributed aggregative query covers two more seriesKeys(measurement + tagSets) in a shard file, the aggregative query result which is passed accross cluster,  would has two more mapperValues. The node of cluster,  revieving the aggregative query result,  could regard the query result as raw query result. It will lead to ERR: unexpected end of JSON input or double results described by issue #4965 .

[ ] CHANGELOG.md updated
[x] Rebased/mergable
[x] Tests pass
[x] Sign CLA

@otoolep Can you review the PR?

I would like to hold off on merging this until we merge https://github.com/influxdb/influxdb/pull/4848.  This will allow us to write a cluster test to make sure we don't regress.  Hopefully we can merge the cluster test PR today.

Ok, that PR is merged.  I'm happy to write the test for you if you can give me an idea of what type of query was failing before.  If you can provide a couple of sample writes with a query that should be all I need to reproduce in the master branch.

@corylanou
I suggest you should create a InfluxDB cluster and set replication of the retention policy as 1. Then, write some points which are different from tagSets . At last, execute a aggregative query which can cover all points you write in.
The following is a repreduce sample:
Create InfluxDB cluster with three node. There is cluster stats:
> show servers
id	cluster_addr	raft	raft-leader
1	<IP_ADDRESS>:8088	true	true
2	<IP_ADDRESS>:9099	true	false
3	<IP_ADDRESS>:10101	true	false

Create a database named foo and a  retention policy named one_hour with duration 1h and replication 1:
> create database foo
> create retention policy one_hour on foo duration 1h replication 1
> show databases
name: databases
---------------
name
foo

> show retention policies on foo
name		duration	replicaN	default
default		0		3		true
one_hour	1h0m0s		1		false

>

Write several points to one_hour retention policy of  foo database using curl:
➜  ~  curl -i -XPOST 'http://<IP_ADDRESS>:8086/write?db=foo&rp=one_hour' --data-binary 'cpu,host=host_1,region=region_1 value=1'
HTTP/1.1 204 No Content
Request-Id: 0632942a-98a4-11e5-8013-000000000000
X-Influxdb-Version: 0.9
Date: Wed, 02 Dec 2015 03:23:15 GMT
Connection: close

➜  ~  curl -i -XPOST 'http://<IP_ADDRESS>:8086/write?db=foo&rp=one_hour' --data-binary 'cpu,host=host_2,region=region_2 value=2'
HTTP/1.1 204 No Content
Request-Id: 0c490066-98a4-11e5-8014-000000000000
X-Influxdb-Version: 0.9
Date: Wed, 02 Dec 2015 03:23:25 GMT
Connection: close

➜  ~  curl -i -XPOST 'http://<IP_ADDRESS>:8086/write?db=foo&rp=one_hour' --data-binary 'cpu,host=host_3,region=region_3 value=3'
HTTP/1.1 204 No Content
Request-Id: 100443e8-98a4-11e5-8015-000000000000
X-Influxdb-Version: 0.9
Date: Wed, 02 Dec 2015 03:23:31 GMT
Connection: close

➜  ~  curl -i -XPOST 'http://<IP_ADDRESS>:8086/write?db=foo&rp=one_hour' --data-binary 'cpu,host=host_4,region=region_4 value=4'
HTTP/1.1 204 No Content
Request-Id: 1432f71e-98a4-11e5-8016-000000000000
X-Influxdb-Version: 0.9
Date: Wed, 02 Dec 2015 03:23:38 GMT
Connection: close

Now, there are four points in foo database:
➜  ~  curl -G 'http://<IP_ADDRESS>:8086/query?pretty=true' --data-urlencode "db=foo" --data-urlencode "q=SELECT * FROM one_hour.cpu"
{
    "results": [
        {
            "series": [
                {
                    "name": "cpu",
                    "columns": [
                        "time",
                        "host",
                        "region",
                        "value"
                    ],
                    "values": [
                        [
                            "2015-12-02T03:23:15.070506552Z",
                            "host_1",
                            "region_1",
                            1
                        ],
                        [
                            "2015-12-02T03:23:25.283799043Z",
                            "host_2",
                            "region_2",
                            2
                        ],
                        [
                            "2015-12-02T03:23:31.544199738Z",
                            "host_3",
                            "region_3",
                            3
                        ],
                        [
                            "2015-12-02T03:23:38.561141279Z",
                            "host_4",
                            "region_4",
                            4
                        ]
                    ]
                }
            ]
        }
    ]
}

use mean  or other functions to execute aggregative query:
 ➜  ~  curl -G 'http://<IP_ADDRESS>:8086/query?pretty=true' --data-urlencode "db=foo" --data-urlencode "q=SELECT mean(value) FROM one_hour.cpu"
{
    "results": [
        {
            "error": "unexpected end of JSON input"
        }
    ]
}
➜  ~  curl -G 'http://<IP_ADDRESS>:8086/query?pretty=true' --data-urlencode "db=foo" --data-urlencode "q=SELECT sum(value) FROM one_hour.cpu"
{
    "results": [
        {
            "error": "unexpected end of JSON input"
        }
    ]
}
➜  ~  curl -G 'http://<IP_ADDRESS>:8086/query?pretty=true' --data-urlencode "db=foo" --data-urlencode "q=SELECT min(value) FROM one_hour.cpu"
{
    "results": [
        {
            "error": "unexpected end of JSON input"
        }
    ]
}
➜  ~  curl -G 'http://<IP_ADDRESS>:8086/query?pretty=true' --data-urlencode "db=foo" --data-urlencode "q=SELECT max(value) FROM one_hour.cpu"
{
    "results": [
        {
            "error": "unexpected end of JSON input"
        }
    ]
}

@corylanou
The followings are curl command.
curl -G 'http://<IP_ADDRESS>:8086/query' --data-urlencode "q=create database foo"
curl -G 'http://<IP_ADDRESS>:8086/query' --data-urlencode "q=create retention policy one_hour on foo duration 1h replication 1"
curl -X POST 'http://<IP_ADDRESS>:8086/write?db=foo&rp=one_hour' --data-binary 'cpu,host=host_1,region=region_1 value=1'
curl -X POST 'http://<IP_ADDRESS>:8086/write?db=foo&rp=one_hour' --data-binary 'cpu,host=host_2,region=region_2 value=2'
curl -X POST 'http://<IP_ADDRESS>:8086/write?db=foo&rp=one_hour' --data-binary 'cpu,host=host_3,region=region_3 value=3'
curl -X POST 'http://<IP_ADDRESS>:8086/write?db=foo&rp=one_hour' --data-binary 'cpu,host=host_4,region=region_4 value=4'

@dgnorton @corylanou -- what do you think? Should we get this in for 0.9.6?

@otoolep  Please wait a miniute, I will add some commits to this pr.

@otoolep  Done!

Thanks @li-ang
@dgnorton @corylanou -- what do you think?

We have no testing around this yet.  It passes the existing tests so it doesn't introduce any new single node bugs that we are aware of.  We can add more tests in a following PR if you want to ship this.

Thanks @li-ang


Exception after StoryMaker screen is closed - Looking up a deactivated widget's ancestor is unsafe

After closing the screen (clicking "Add to story"), the exception below occurs.
The app does not crash, but still it should be fixed.
I suspect it can be because of PhotoView (or some other widget) is not disposed properly, or because some widget is trying to be rebuilt after the StoryMaker screen has been unmounted.
The following assertion was thrown while finalizing the widget tree:
Looking up a deactivated widget's ancestor is unsafe.

At this point the state of the widget's element tree is no longer stable.

To safely refer to a widget's ancestor in its dispose() method, save a reference to the ancestor by calling dependOnInheritedWidgetOfExactType() in the widget's didChangeDependencies() method.

When the exception was thrown, this was the stack
#0      Element._debugCheckStateIsActiveForAncestorLookup.<anonymous closure>
package:flutter/…/widgets/framework.dart:4153
#1      Element._debugCheckStateIsActiveForAncestorLookup
package:flutter/…/widgets/framework.dart:4167
#2      Element.getElementForInheritedWidgetOfExactType
package:flutter/…/widgets/framework.dart:4193
#3      TickerMode.getNotifier
package:flutter/…/widgets/ticker_provider.dart:96
#4      TickerProviderStateMixin._updateTickerModeNotifier
package:flutter/…/widgets/ticker_provider.dart:327
#5      TickerProviderStateMixin.createTicker
package:flutter/…/widgets/ticker_provider.dart:291
#6      new AnimationController
package:flutter/…/animation/animation_controller.dart:246
#7      PhotoViewCoreState._scaleAnimationController
package:photo_view/…/core/photo_view_core.dart:112
#8      PhotoViewCoreState._scaleAnimationController (package:photo_view/src/core/photo_view_core.dart)
package:photo_view/…/core/photo_view_core.dart:1
#9      PhotoViewCoreState.dispose
package:photo_view/…/core/photo_view_core.dart:274
#10     StatefulElement.unmount
package:flutter/…/widgets/framework.dart:4983
#11     _InactiveElements._unmount
package:flutter/…/widgets/framework.dart:1926
#12     _InactiveElements._unmount.<anonymous closure>
package:flutter/…/widgets/framework.dart:1924
#13     ComponentElement.visitChildren
package:flutter/…/widgets/framework.dart:4807
#14     _InactiveElements._unmount
package:flutter/…/widgets/framework.dart:1922
#15     _InactiveElements._unmount.<anonymous closure>
package:flutter/…/widgets/framework.dart:1924
#16     _LayoutBuilderElement.visitChildren
package:flutter/…/widgets/layout_builder.dart:71
#17     _InactiveElements._unmount
package:flutter/…/widgets/framework.dart:1922
#18     _InactiveElements._unmount.<anonymous closure>
package:flutter/…/widgets/framework.dart:1924
#19     ComponentElement.visitChildren
package:flutter/…/widgets/framework.dart:4807
#20     _InactiveElements._unmount
package:flutter/…/widgets/framework.dart:1922
#21     _InactiveElements._unmount.<anonymous closure>
package:flutter/…/widgets/framework.dart:1924
#22     SingleChildRenderObjectElement.visitChildren
package:flutter/…/widgets/framework.dart:6271
#23     _InactiveElements._unmount
package:flutter/…/widgets/framework.dart:1922
#24     _InactiveElements._unmount.<anonymous closure>
package:flutter/…/widgets/framework.dart:1924
#25 .... (many more similar lines here)
...

@AleksandarSavic95 Sorry for such a late reply. The problem has been fixed.


[WPF] VSCode shows error for WPF project: "The name 'InitializeComponent' does not exist in the current context (Roslyn CS0103)

1/ Install .NET Core 7.0
2/ Create WPF project with "dotnet new wpf"
3/ VSCode > Open Folder.
After awhile, VSCode shows many errors:
"The name 'InitializeComponent' does not exist in the current context"
Moreover, any variables declared in .XAML file will cause error if these variables are used in .CS file
Hope VSCode Dev Team will fix bugs soon, thank you very much !

@HyVong007 @heartacker A couple questions to help narrow down which component might be responsible. Are you using the prerelease C# extension (2.x)? Do you also have the C# DevKit extension installed?

@HyVong007 @heartacker A couple questions to help narrow down which component might be responsible. Are you using the prerelease C# extension (2.x)? Do you also have the C# DevKit extension installed?

I install the pre-release version of C# Dev Kit, it causes error with WPF project. But the release version works fine in WPF.

@HyVong007 @heartacker A couple questions to help narrow down which component might be responsible. Are you using the prerelease C# extension (2.x)? Do you also have the C# DevKit extension installed?

The first time i use C# dev kit (release) and C# (release) extensions => everything works fine !
Then C# Dev Kit shows me a notification that i must upgrade C# extension to pre-release version. After that, WPF has error "InitializeComponent does not exist......"
The notification is here:

I have the exact same issue as the person above on the same version of the Dev Kit. I had the same error on the previous versions as well though

same issue. Any solution?

Seeing the same error. Is there any workaround to fix this issue? Tried searching over the internet but all the answers there were related to this error occurring in Visual Studio and not Visual Studio Code.

Same issue,
Is there any way to stop these suggestions in VS code, I'm get rid of these error lines.

same for me. i already tried using omnisharp and preview versions and the dev toolkit, it's all the same. also no autocomplete for XAML but this might be another typic/plugin

I have the same issue, the wpf project can run normally, but vscode seems to be unable to associate xaml with xaml.cs properly, which is not an issue in Visual Studio

Has anyone solved this problem? My OCD is acting up.

I have the same.

Still seeing this issue with C# version v2.14.8 and C# Dev Kit v1.1.16. Everything builds and runs OK but the error is still there. Any guidance at this point?

I am seeing this same thing.  Project builds in Visual Studio but in vscode it says InitializeCompnent() doesn't exist.  (I should add this is a net472 sdk project) The C# dev kit release and pre-release show this for me.

Still broken

I am also seeing the same symptoms. It affects the hot reload functionality since an error is detected.  Note that these errors are not preventing the building or running of the solution from scratch.
I'm experiencing this in Visual Studio 2022 with a .NET 6 WPF solution consisting of 5 projects.
To temporarily resolve the issue, this is what worked for me.

close the solution
close VS 2022
navigate to the project folder in File Explorer and show hidden files/folders
delete or rename the ".vs" folder
open the solution, errors gone.

Hope this temporary fix assists, but we really do need a permanent solution.

@Brentec-ca we're not talking about Visual Studio here but rather Visual Studio code but I know what you are talking about. When I was inserting one custom control it didn't want to build this in znak designer but cleaning .vs folder, running dotnet clean and then rebuild fixes the issue

Guys, delete "obj" folder of your application. Then rebuild, this will fix that. Visual Studio fix tho.

@marcin-przywoski Yeah surely, I just had this issue with Visual Studio too, so thought would be nice to mention here. If not. I can delete it no without any problem.

I'm seeing the same issue with

VSCode v1.87.2
C# v2.22.5
C# Dev Kit v1.4.29

The strange thing is that this isn't preventing me from running my application.

Navigate to the g.i.cs file of the offending Page or Window, delete the g.i.cs file and rebuild solution. Or, if you're lazy, delete the obj directory inside your project directory and rebuild. This fixed it for me.

Navigate to the g.i.cs file of the offending Page or Window, delete the g.i.cs file and rebuild solution. Or, if you're lazy, delete the obj directory inside your project directory and rebuild. This fixed it for me.

We're not talking about visual studio, we're talking about vs code

Guys, delete "obj" folder of your application. Then rebuild, this will fix that. Visual Studio fix tho.

It works on my VS, thanks.

I have the same issue with VS Code.  As soon as I ran dotnet new wpf, open the project folder in VS Code, within MainWindows.xaml.cs I get The name 'InitializeComponent' does not exist in the current context (CS0103).
But if I perform dotnet run, it compiles properly without any errors, and the window appears.

To all the people suffering from this problem:
I found a temporary solution that makes those errors disappear.
Just add these to your .csproj file:
<ItemGroup>
	<Compile Include="obj/x64/Debug/net8.0-windows/*.cs">
		<AutoGen>True</AutoGen>
	</Compile>
</ItemGroup>

@aianlinb didn't work for me :/ even after I changed the path in Include to the matching one in my project

To all the people suffering from this problem: I found a temporary solution that makes those errors disappear. Just add these to your .csproj file:
<ItemGroup>
	<Compile Include="obj/x64/Debug/net8.0-windows/*.cs">
		<AutoGen>True</AutoGen>
	</Compile>
</ItemGroup>

Unfortunately this didn't work for me.

@marcin-przywoski @codenotworking I edited some messages above, maybe try it again. wish good luck

To all the people suffering from this problem: I found a temporary solution that makes those errors disappear. Just add these to your .csproj file:
<ItemGroup>
	<Compile Include="obj/Debug/net8.0-windows/*.cs">
		<AutoGen>True</AutoGen>
	</Compile>
</ItemGroup>

Edit:
The path should be where the MainWindow.g.cs (or something similar) is. (Find by yourself under obj, must build the project first) And make sure your class declaration in MainWindow.xaml.cs matches the one in the generated file. (e.g. public partial class MainWindow : Window) Finally, try restarting vscode and rebuilding the solution.
(If that doesn't work, maybe you can try replacing Include with Update.)

This works for me, it helps bro, thanks. Seems like Visual Studio does something for the generated build, but the vscode extension does not, so it should be done manually.

Turn this on and it will be fixed. At least we now know it's the c# dev kit extension that is plaguing us.

The DevKit tracking issue for this bug is https://github.com/microsoft/vscode-dotnettools/issues/1018

Turn this on and it will be fixed. At least we now know it's the c# dev kit extension that is plaguing us.

Finally a solution that works!

Turn this on and it will be fixed. At least we now know it's the c# dev kit extension that is plaguing us.

Thank you a lot, it worked for me


[node] Run the action on node20

Both node12 and node16 are deprecated, resulting in the action being run on node20 already.
Fixes #35

@tanmayghosh2507
Sorry for the ping, I'm not sure what is the appropriate way to ask for a review.

Indeed... the action works great for helping us build and maintain a cloud hosted symbol server, but it would be nice if did not read 30 github deprecation warnings in every single build log.

@tanmayghosh2507 Sorry for the ping (again), is this repository still active?


[FLINK-4032] Replace all usages Guava preconditions

This PR replaces every usage of the Guava Preconditions in Flink with our own Preconditions class.
In addition,

the guava dependency was completely removed from the RabbitMQ connector
a checkstyle rules was added preventing further use of guava preconditions

I think the Kinesis connector is missed out as part of this cleanup. Thanks for this!

The Kinesis connector already uses Flink's Preconditions class.

Ah right, sorry I was mistaken by the guava dependency in pom.xml. The dependency can actually be safely removed also though, must have accidentally left it there when the connector was cleaned up to use Flink's preconditions.

It is still used in FlinkKinesisProducer.

Oops, my mistake again ;) Thanks.

Looks good overall. Added just a few minor comments.

@fhueske I've addressed your comments.

Thanks for the update @zentol. +1 to merge

Merging


Update Brokers distribution chart legends to show the number/ percentages

Update Brokers distribution chart legends to show the number/ percentages
Fixes issue#359
storybook story

Looks good thanks. Maybe tweak the numbers a bit in the story so not to have the same exact figures and percentages displayed?


Numba is not work in QGIS python console.

I want to use numba package in QGIS. QGIS is a user friendly Open Source Geographic Information System (GIS) licensed under the GNU General Public License. QGIS is an official project of the Open Source Geospatial Foundation (OSGeo).
I installed numba in qgis with pycharm then I want to test a simple code with numba. I used below code from  numba.pydata.org
from numba import jit
from numpy import arange

# jit decorator tells Numba to compile this function.
# The argument types will be inferred by Numba when function is called.
@jit
def sum2d(arr):
    M, N = arr.shape
    result = 0.0
    for i in range(M):
        for j in range(N):
            result += arr[i,j]
    return result

a = arange(9).reshape(3,3)
print(sum2d(a))

The result of this code is 36.0. In QGIS python console I can call numba with `import numba' without error.
But when I want to run above code in QGIS python console  I received this errors:
Traceback (most recent call last):
  File "<input>", line 1, in <module>
  File "/tmp/tmp890NMS.py", line 16, in <module>
    print(sum2d(a))
  File "/usr/local/lib/python2.7/dist-packages/numba/dispatcher.py", line 307, in _compile_for_args
    return self.compile(tuple(argtypes))
  File "/usr/local/lib/python2.7/dist-packages/numba/dispatcher.py", line 579, in compile
    cres = self._compiler.compile(args, return_type)
  File "/usr/local/lib/python2.7/dist-packages/numba/dispatcher.py", line 80, in compile
    flags=flags, locals=self.locals)
  File "/usr/local/lib/python2.7/dist-packages/numba/compiler.py", line 763, in compile_extra
    return pipeline.compile_extra(func)
  File "/usr/local/lib/python2.7/dist-packages/numba/compiler.py", line 360, in compile_extra
    return self._compile_bytecode()
  File "/usr/local/lib/python2.7/dist-packages/numba/compiler.py", line 722, in _compile_bytecode
    return self._compile_core()
  File "/usr/local/lib/python2.7/dist-packages/numba/compiler.py", line 709, in _compile_core
    res = pm.run(self.status)
  File "/usr/local/lib/python2.7/dist-packages/numba/compiler.py", line 246, in run
    raise patched_exception
KeyError: 'Caused By:\nTraceback (most recent call last):\n  File "/usr/local/lib/python2.7/dist-packages/numba/compiler.py", line 238, in run\n    stage()\n  File "/usr/local/lib/python2.7/dist-packages/numba/compiler.py", line 431, in stage_objectmode_frontend\n    cres = self.frontend_looplift()\n  File "/usr/local/lib/python2.7/dist-packages/numba/compiler.py", line 421, in frontend_looplift\n    lifted=tuple(loops), lifted_from=None)\n  File "/usr/local/lib/python2.7/dist-packages/numba/compiler.py", line 777, in compile_ir\n    lifted_from=lifted_from)\n  File "/usr/local/lib/python2.7/dist-packages/numba/compiler.py", line 368, in compile_ir\n    return self._compile_ir()\n  File "/usr/local/lib/python2.7/dist-packages/numba/compiler.py", line 729, in _compile_ir\n    return self._compile_core()\n  File "/usr/local/lib/python2.7/dist-packages/numba/compiler.py", line 709, in _compile_core\n    res = pm.run(self.status)\n  File "/usr/local/lib/python2.7/dist-packages/numba/compiler.py", line 246, in run\n    raise patched_exception\nKeyError: \'Caused By:\\nTraceback (most recent call last):\\n  File "/usr/local/lib/python2.7/dist-packages/numba/compiler.py", line 238, in run\\n    stage()\\n  File "/usr/local/lib/python2.7/dist-packages/numba/compiler.py", line 622, in stage_objectmode_backend\\n    self._backend(lowerfn, objectmode=True)\\n  File "/usr/local/lib/python2.7/dist-packages/numba/compiler.py", line 599, in _backend\\n    lowered = lowerfn()\\n  File "/usr/local/lib/python2.7/dist-packages/numba/compiler.py", line 573, in backend_object_mode\\n    self.flags)\\n  File "/usr/local/lib/python2.7/dist-packages/numba/compiler.py", line 905, in py_lowering_stage\\n    lower = objmode.PyLower(targetctx, library, fndesc, interp)\\n  File "/usr/local/lib/python2.7/dist-packages/numba/lowering.py", line 65, in __init__\\n    self.env = Environment.from_fndesc(self.fndesc)\\n  File "/usr/local/lib/python2.7/dist-packages/numba/lowering.py", line 21, in from_fndesc\\n    mod = fndesc.lookup_module()\\n  File "/usr/local/lib/python2.7/dist-packages/numba/funcdesc.py", line 77, in lookup_module\\n    return sys.modules[self.modname]\\nKeyError: \\\'__console__\\\'\\n\\nFailed at object (object mode backend)\\n\\\'__console__\\\'\'\n\nFailed at object (object mode frontend)\n\'Caused By:\\nTraceback (most recent call last):\\n  File "/usr/local/lib/python2.7/dist-packages/numba/compiler.py", line 238, in run\\n    stage()\\n  File "/usr/local/lib/python2.7/dist-packages/numba/compiler.py", line 622, in stage_objectmode_backend\\n    self._backend(lowerfn, objectmode=True)\\n  File "/usr/local/lib/python2.7/dist-packages/numba/compiler.py", line 599, in _backend\\n    lowered = lowerfn()\\n  File "/usr/local/lib/python2.7/dist-packages/numba/compiler.py", line 573, in backend_object_mode\\n    self.flags)\\n  File "/usr/local/lib/python2.7/dist-packages/numba/compiler.py", line 905, in py_lowering_stage\\n    lower = objmode.PyLower(targetctx, library, fndesc, interp)\\n  File "/usr/local/lib/python2.7/dist-packages/numba/lowering.py", line 65, in __init__\\n    self.env = Environment.from_fndesc(self.fndesc)\\n  File "/usr/local/lib/python2.7/dist-packages/numba/lowering.py", line 21, in from_fndesc\\n    mod = fndesc.lookup_module()\\n  File "/usr/local/lib/python2.7/dist-packages/numba/funcdesc.py", line 77, in lookup_module\\n    return sys.modules[self.modname]\\nKeyError: \\\'__console__\\\'\\n\\nFailed at object (object mode backend)\\n\\\'__console__\\\'\''

With this error? Can I use numba in QGIS or not?

Thanks for the report. This compiles and executes correctly on the current version of Numba 0.51. The original problem was likely some sort of unsupported construct that tripped up the objectmod fallback. Closing.


cannot control the indentation of the output json

I would like to generate a well formated json file, instead of a long json string without any space and enter. However, seems no way to achieve it without modifying the source. In the typedjson/js/index.js, it has JSON.stringify call:
return JSON.stringify(this.writeToJsonObject(object, {
738                 objectType: ObjectType,
739                 enableTypeHints: settings.enableTypeHints,
740                 typeHintPropertyKey: settings.typeHintPropertyKey
741             }), settings.replacer);
hope to pass the space as the 3rd parameter, like the following:
741             }), settings.replacer, 4);
so that it can generate well-formated json file.

I'll make sure to add this functionality ASAP. The indentation amount setting will be available in both TypedJSON.config and TypedJSON.stringify using the space property:
TypedJSON.config({
    space: 4
});

TypedJSON.stringify(obj, {
    space: 4
});

Hey, if you would be interested again, this is working fine for some time now.


Removing generator version from generated code

This was only used in PHP & Java, is not useful, and would cause a lot of noise if it was updated.

Codecov Report

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

@@             Coverage Diff              @@
##             master    #1951      +/-   ##
============================================
+ Coverage     85.91%   85.92%   +0.01%
+ Complexity     4892     4888       -4
============================================
  Files           451      450       -1
  Lines         19545    19518      -27
  Branches       2043     2041       -2
============================================
- Hits          16792    16771      -21
+ Misses         2062     2058       -4
+ Partials        691      689       -2

Impacted Files
Coverage Δ
Complexity Δ

.../transformer/py/PythonGapicSurfaceTransformer.java
98.24% <ø> (-0.01%)
41 <0> (ø)

...nsformer/nodejs/NodeJSGapicSurfaceTransformer.java
99.5% <ø> (-0.01%)
29 <0> (ø)

.../transformer/ruby/RubyGapicSurfaceTransformer.java
99.58% <ø> (-0.01%)
31 <0> (ø)

...en/transformer/php/PhpGapicSurfaceTransformer.java
95.12% <ø> (-0.02%)
44 <0> (ø)

...i/codegen/viewmodel/metadata/VersionIndexView.java
100% <ø> (ø)
5 <0> (ø)
:arrow_down:

...m/google/api/codegen/viewmodel/FileHeaderView.java
80% <ø> (+8.57%)
4 <0> (-1)
:arrow_down:

...api/codegen/transformer/FileHeaderTransformer.java
100% <ø> (ø)
5 <0> (ø)
:arrow_down:

...gle/api/codegen/viewmodel/DynamicLangXApiView.java
81.81% <ø> (ø)
13 <0> (ø)
:arrow_down:

Continue to review full report at Codecov.

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


python3Packages: don't propagate build-platform cffi

Description of changes
#142301 added cffi to propagatedNativeBuildInputs in many packages to fix cross-compilation. This had the unfortunate effect of making build-platform cffi part of the runtime closure of all downstream packages.
On the other hand, it appears that it is not actually necessary to propagate cffi to fix cross-compilation; instead it is enough to add it to nativeBuildInputs.
This patch implements this change, while also reverting #200779 (my initial attempt at fixing build-platform contamination in brotlicffi) and removing a few other propagatedNativeBuildInputs that were unnecessarily added in #142301.
argon2-cffi fails for other reasons, so I can't check exactly which dependencies are required.

Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin
[x] armv6l-linux (cross)

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

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

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

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

[x] Fits CONTRIBUTING.md.

cc @legendofmiracles @Artturin

I rebased and fixed the conflicts.

argon2-cffi fails for other reasons, so I can't check exactly which dependencies are required.

Are you perhaps also hitting this (when compiling argon2-cffi-bindings though)?
armv6l-unknown-linux-gnueabihf-gcc: error: unrecognized command-line option ‘-msse2’

I was able to work around that by setting: ARGON2_CFFI_USE_SSE2 = 0.
At least, your patch does help since it fixes:
ModuleNotFoundError: No module named '_cffi_backend'

for me.

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/why-does-brotlicffi-depend-on-the-wrong-architectures-cffi/44671/2


Improve pattern matching type checking

Codecov Report
Attention: 2 lines in your changes are missing coverage. Please review.

Comparison is base (2e7264b) 80.79% compared to head (0db39e4) 80.95%.

Files
Patch %
Lines

src/Escalier.TypeChecker/Poly.fs
50.00%
1 Missing :warning:

src/Escalier.TypeChecker/Unify.fs
94.11%
1 Missing :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #112      +/-   ##
==========================================
+ Coverage   80.79%   80.95%   +0.16%
==========================================
  Files          17       17
  Lines        5425     5450      +25
  Branches      663      664       +1
==========================================
+ Hits         4383     4412      +29
+ Misses       1042     1038       -4

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


Need help on Swift implementation

Does somebody have any experience with Bluetooth and this documentation on iOS and Swift?
If so, perhaps somebody can push me to the right direction, as I'm a totally Bluetooth newbie :)

Thanks :)

I works on iOS and OC. I can help something if I known.


Update for translation and add french translation

What ?
Translation of the UI
How ?
Use the svelte-i18n library
Changes

Added i18n.js
Added translation.js
Updated the UI code where translation is needed, using $t("translationExample").

Notes

Only added French translation.

oh wow I didn't know about the i18n svelte package, that's awsome, will look into it and merge asap. thank you!!


feat: implement host.setSecretFile() to securely set binary files as secrets

Fixes https://github.com/dagger/dagger/issues/5069
Problem
Some users need to set binary files or non UTF-8 files (GPG keys for example) as secrets.
Solution
This PR implements a new API endpoints enabling a safe mount of those secrets without leaking information in any layer. (context starting from this comment: https://github.com/dagger/dagger/issues/5069#issuecomment-1568474579)
Open question
Do we scope the host access to the project workdir, as other host APIs: https://github.com/dagger/dagger/blob/main/core/integration/host_test.go#L165-L172 ?

cc @helderco, as https://github.com/dagger/dagger/pull/5502 works (manually tested + context on PR), and given the fact that the current PR has only a 512000 bytes limitation, you can review this one 👍

Since this change affects all SDKs, I think that we should duplicate the release notes as mentioned here: https://github.com/miniscruff/changie/discussions/502#discussioncomment-6552993
WDYT @grouville?

Yes please!


no more intel-based macOS support?

Description
Prior to releases 1.7.1 and 1.7.2, there used to be a release artifact called MBTilesViewer_x64.app.tar.gz which contained the build to install the app for x86_64 macOS. however, with the recent releases, now's there's only a MBTilesViewer_aarch64.app.tar.gz artifact and the build it contains can only run on arm-based macOS.
Is the removal of intel arch intentional in these releases?
Steps To Reproduce
No response
Expected behavior
Have an artifact for installing the app on intel-based macOS devices.
App Version
1.7.0
Operating System Version
2019 MacBook Pro, macOS 14.5 (Sonoma), 2.3 GHz 8-Core Intel Core i9
Additional Information
No response

@achou11 indeed i did not even see that. Must be a tauri change. Will fix that

@achou11 i updated the latest release. I now has the intel macos version https://github.com/Akylas/mbview-rs/releases/tag/v

awesome! was able to install so will close this. thanks!


🐞Bug: Product Cards are too wide to read at big screen size

Describe the bug
The product cards grow extensively for large screen size, which hampers the user experience.
To Reproduce
Steps to reproduce the behavior:

Open 'Chrome Devtools'
Click on 'Responsive Mode'
Expand the screen

Expected behavior
The cards and the card container should have a maximum width.
Screenshots

Desktop (please complete the following information):

OS: Windows
Browser: Chrome

Describe the bug The product cards grow extensively for large screen size, which hampers the user experience.
To Reproduce Steps to reproduce the behavior:

Open 'Chrome Devtools'
Click on 'Responsive Mode'
Expand the screen

Expected behavior The cards and the card container should have a maximum width.
Screenshots
Desktop (please complete the following information):

OS: Windows
Browser: Chrome

what would be the solution?

do we need to add 4 cards in a row?
need to add a small size?

I would like to fix it, could you assign this to me?

I would like to fix it, could you assign this to me?

yeah sure work on it.

Describe the bug The product cards grow extensively for large screen size, which hampers the user experience.
To Reproduce Steps to reproduce the behavior:

Open 'Chrome Devtools'
Click on 'Responsive Mode'
Expand the screen

Expected behavior The cards and the card container should have a maximum width.
Screenshots
Desktop (please complete the following information):

OS: Windows
Browser: Chrome

what would be the solution?

do we need to add 4 cards in a row?
need to add a small size?

The cards container should have a certain max width, beyond which the container would not grow, thereby maintaining the width of each card.

Describe the bug The product cards grow extensively for large screen size, which hampers the user experience.
To Reproduce Steps to reproduce the behavior:

Open 'Chrome Devtools'
Click on 'Responsive Mode'
Expand the screen

Expected behavior The cards and the card container should have a maximum width.
Screenshots
Desktop (please complete the following information):

OS: Windows
Browser: Chrome

what would be the solution?

do we need to add 4 cards in a row?
need to add a small size?

The cards container should have a certain max width, beyond which the container would not grow, thereby maintaining the width of each card.

sounds good 🎉

Take a look at  #174 , let me know if it needs any modification

Completed. Thanks for your contributions 🎉 ❤


Update add-several-users-at-the-same-time.md

updated alternate email address as it is now available in the sample CSV
Fixes#https://github.com/MicrosoftDocs/microsoft-365-docs/issues/11071

@JohanFreelancer9 Please copy review

@kwekuako Please merge this PR. Thanks


Old objects with the same path/name are not deleted

Current Behavior
Uploading file the same name as already existing one doesn't replace the object.
Expected Behavior
Object with the same path to be replaced.
Possible Solution
Check for existing objects with the same path, drop them after upload.
Steps to Reproduce
Upload neofs-spec-latest.pdf via
https://github.com/nspcc-dev/neofs-spec/blob/968f6864e6207667ea2284c9066f4cc8993f494c/.github/workflows/neofs.yml, get it via the gateway.
Context
Related to #2.

Fixed in #16.


Possibility to validate new group on move

We are building a rooms reservation system. The user does not have permission to book every room and therefor some groups in the timeline are readonly.
The user should not be able to drop an item in such group.
Currently there is no way to validate if the new group is valid when the user moves the item into a new group.
Can you please provide a solution for this issue.
If you accept a Pull Request, can you put me in the right direction on how you would add such change?
maybe here?
https://github.com/namespace-ee/react-calendar-timeline/blob/ca66f740b779fa25f9aa35ce3d09fe9f1acd41bd/src/lib/items/Item.js#L215

Hi, any updates on this? I could help implementing this too.

I haven't done any work towards this. Any help you could provide would be awesome


Additional documentation

Do you have any additional documentation on this repository?  I would like to use the layout algorithm in my Python project

Hope you are Ok with my fork here:  https://github.com/hasii2011/OrthogonalDrawing

Still using it

So sorry for getting back to you so late, I have added some content in README. If you need more information, I am willing to answer.

Thanks for the update especially the academic reference.  In order to understand and use the code I actually forked the project here. https://github.com/hasii2011/OrthogonalDrawing


[ENH] - Ability to pass environment variables to custom apps

Feature description
Currently custom apps aren't able to be created with user supplied environment variables.
Value and/or benefit
To be able to deploy variety of apps with like for example to be able to supply something like:

BOKEH_ALLOW_WS_ORIGIN for custom panel apps
OPENAI_API_KEY for custom AI apps

Anything else?
No response

We'll handle it in the next release @dharhas

Maybe this could be done with conda store (not sure if it should)?  I believe conda envs support setting env vars (https://stackoverflow.com/a/62508395/9848141), but I'm not sure if conda store supports it.

Maybe this could be done with conda store (not sure if it should)?

jhub-apps should work with any JupyterHub installation and conda-store is specific to Nebari. By the way I have just added it in the API in this PR: https://github.com/nebari-dev/jhub-apps/pull/107 (frontend is pending though)

This is done.


Examlpe on how to use SDK for creating classifiers metrics

Should this be added to the README.md (perhaps underneath a new "C++ SDK" section)?


MGMT-9662 Use logger stored inside a Context

Removes dedicated loggers from most of a packages.
Instead uses logger that is stored inside a Context instead.
Provides helper functions (based on controller-runtime's) for extracting and storing logger withing Context: in case of missing logger inside Context a just-in-case logger will be used: "ctx-missing-logger".

/cc @yevgeny-shnaidman @qbarrand

/unhold

/retest

/lgtm

/hold

/lgtm

/lgtm


Regarding severe graphical glitches with egui

Title: Regarding severe graphical glitches with egui
Dear emilk,
When continuously running a program that uses the egui library on windows, there is a bug causing severe graphic glitches after about 1 to 6 hours.
Before I explain the circumstances leading to this glitch, I want to highlight another bug.
        frame.set_minimized(true);

When using the above function or the native windows minimize button and then restoring the program to its original size, the frame.info().window_info.minimized remains constantly set to true. Therefore, it's impossible to determine whether the program is in a minimized state. In the minimized state, ui.available_width() slightly decreases, and ui.available_height() becomes 0.0. After restoring from the minimized state, while ui.available_width() returns to normal, sometimes ui.available_height() remains at 0.0.
I've tried to determine the exact conditions that lead to the graphic glitches. The frequency of glitches appears to be higher when restoring the program to its original size after minimizing it for over an hour. The graphical glitches also occur every few hours even without minimizing the program. When these glitches happen, it seems ui.available_height() is at 0.0. It's presumed that the glitches might be linked to the instances when, upon restoring from minimized state, ui.available_height() occasionally remains at 0.0.
Please note that this behavior isn't consistent, as it happens only every few hours. However, these are my observations so far while trying to reproduce and prevent this glitch.
Thanks.

egui Version
egui 0.22.0
egui 0.21.0
[ BUG Capture ]
https://github.com/rustbasic/rdesk/blob/main/bug-capture-1.jpg?raw=true
[ No Bug Capture ]
https://github.com/rustbasic/rdesk/blob/main/no-bug-capture-1.jpg?raw=true

Dear emilk,
I've been working for over 6 months to reproduce the issue of graphics breaking every few hours in a Windows program using the egui library. Through these efforts, I've roughly identified the reason and found a temporary way to prevent it.
When the program is minimized, the value of ui.available_height() decreases.
In the minimized state, the value of ui.available_height() seems to range between 0.0 to 20.0, depending on where the program was launched.
I tried using the method if ui.available_height() < 100.0 { return; }, but graphics still broke every few hours when restoring from a minimized state.
So,
let mut ui_available_height = ui.available_height();
if ui_available_height < 100.0 {
    ui_available_height = ui_available_height.at_least(100.0);
}

I created the ui_available_height value using the above method and used it, but still, the graphics broke every few hours after restoring from a minimized state.
Lastly, I found a method where graphics didn't break for 2-3 days upon testing.
fn update(&mut self, ctx: &egui::Context, frame: &mut eframe::Frame) {
    ...
    let mut minimized_stop_work = false;
    ...
    egui::CentralPanel::default().frame(panel_frame).show(ctx, |ui| {
        let ui_available_height = ui.available_height();
        if ui_available_height < 100.0 {
            minimized_stop_work = true;
        }
        ...
    });     // CentralPanel()
    ...
    if !minimized_stop_work {
        ctx.request_repaint();
    }
}    // fn update()

By assuming that it's in a minimized state when ui.available_height() is below 100.0, and by not executing ctx.request_repaint(); (RunMode::Continuous mode in egui_demo_app.exe), the screen doesn't break even when restoring from a minimized state in Windows for a prolonged period. I've successfully tested this for 2-3 days.
This method might temporarily prevent the screen from breaking. However, I'm looking forward to a fundamental solution provided by the egui library.
Thanks, emilk.

Dear emilk,
I've been working for over 6 months to reproduce the issue of graphics breaking every few hours in a Windows program using the egui library. Through these efforts, I've roughly identified the reason and found a temporary way to prevent it.
When the program is minimized, the value of ui.available_height() decreases.
In the minimized state, the value of ui.available_height() seems to range between 0.0 to 20.0, depending on where the program was launched.
I tried using the method if ui.available_height() < 100.0 { return; }, but graphics still broke every few hours when restoring from a minimized state.
So,
let mut ui_available_height = ui.available_height();
if ui_available_height < 100.0 {
ui_available_height = ui_available_height.at_least(100.0);
}
I created the ui_available_height value using the above method and used it, but still, the graphics broke every few hours after restoring from a minimized state.
Lastly, I found a method where graphics didn't break for 2-3 days upon testing.
fn update(&mut self, ctx: &egui::Context, frame: &mut eframe::Frame) {
...
let mut minimized_stop_work = false;
...
egui::CentralPanel::default().frame(panel_frame).show(ctx, |ui| {
let ui_available_height = ui.available_height();
if ui_available_height < 100.0 {
minimized_stop_work = true;
}
...
});     // CentralPanel()
...
if !minimized_stop_work {
ctx.request_repaint();
}
}    // fn update()
By assuming that it's in a minimized state when ui.available_height() is below 100.0, and by not executing ctx.request_repaint(); (RunMode::Continuous mode in egui_demo_app.exe), the screen doesn't break even when restoring from a minimized state in Windows for a prolonged period. I've successfully tested this for 2-3 days.
This method might temporarily prevent the screen from breaking. However, I'm looking forward to a fundamental solution provided by the egui library.
Thanks, emilk.

Thanks for your investigation!
First of all: your posts are easier to read if you add proper markdown code blocks.
You should be able to read the minimized state with frame.info().window_info.minimized instead of checking for the available height.
The question is what eframe should do when an app is minimized. I think it should still call App::update, but giving a very small available_height seems the wrong thing to do, and sounds like a bug in eframe, or perhaps winit.

We should also consider splitting App::update into two: one App::tick and one App::ui. tick would be called even when minimized, while ui only when non minimized (right after the call to tick).

Dear emilk,
In egui v0.22.0, the value of Frame.info().window_info.minimized seems to be inconsistent, making it unusable.
It (= my program) always calls ctx.request_repaint() in the same manner as RunMode::Continuous.
    if !minimized_stop_work {
        ctx.request_repaint();
    }

Using this approach, I haven't experienced any screen corruption for several days.
Thanks emilk.

P.S. I didn't mention one observed point. When the program exits in a minimized state, the screen briefly flickers (within 0.1 seconds), appearing and disappearing, before the program terminates.


Add rawHistorySupported flag for backward compatability

Added rawHistorySupported flag on GetWorkflowExecutionHistoryRequest to make backward compatibility with the client.

Why?

How did you test it?

Potential risks

Discussed offline: lets use the server version checker to check client instead.


Update 2.0.0

Update to version 2.0.0.

Preventing the redefinition of __weak.
Disabling sanity check the GPIO IRQ status

@cfriedt @carlescufi
I don't have merge permissions, so could you please merge as previous time?

"This branch cannot be rebased due to conflicts"?

@henrikbrixandersen
I used the merge command to incorporate changes, so rebasing may result in complicated results.
Merge with upstream/zephyr produces the expected results,
so can you incorporate the changes with the merge command rather than rebase?

@cfriedt @carlescufi @henrikbrixandersen
The PR for Pico2 support https://github.com/zephyrproject-rtos/zephyr/pull/77368  is progressing,
and it will soon be necessary to merge this.
I do not have write permissions for this repositoy, so I would like you to do this.
As with past updates, the changes are being incorporated using merge, and a conflict would occur if you were to rebase.
I have confirmed that pull/6/head can be merged into main (git merge pr6_fetched_branch), so would it be possible to merge this using this method?