Forced Tunneling

There is this new document that suggests that forced tunneling is now supported through NVAs or Azure Firewalls with the proper configuration. Can we update this doc to reflect that and point to this new document? Shall I write a PR for this?

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

ID: 6d034468-fc28-5eff-4e00-091d2ae7ae2b
Version Independent ID: dbd8f413-2dce-dc9c-4a0c-ea2a3ff982db
Content: Extend HDInsight with Virtual Network - Azure
Content Source: articles/hdinsight/hdinsight-extend-hadoop-virtual-network.md
Service: hdinsight
GitHub Login: @hrasheed-msft
Microsoft Alias: hrasheed

Hi @omartin2010 Thank you for your feedback. Somehow your issue is not attached to a document. Could you please link the URL of the documentation you would like to make better? That way, we can pass your feedback to the appropriate content author.

Hi,
I didn't realize the comments on docs didn't include the URL. The specific one is https://docs.microsoft.com/en-us/azure/hdinsight/hdinsight-extend-hadoop-virtual-network?toc=https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Fhdinsight%2Fhadoop%2FTOC.json&bc=https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Fbread%2Ftoc.json#networktraffic.
In particular, this warning "HDInsight does not support restricting outbound traffic. All outbound traffic should be allowed." is contracted by this new article which is still in preview says things that are the exact opposite. So it's not entirely clear for customers if they read both of them (which IMO should be into a single article for clarity sakes).

@omartin2010 If you click on the feedback button at the bottom of documentation pages then the metadata about the page gets added to the issue. Somehow it failed I guess.
It is great if you want to create a PR you will need the blessing and PR review from the content author. Including content author @hrasheed-msft

@omartin2010 Thanks for bringing this to our attention. Your feedback  has been shared with the content owner for further review.

https://github.com/MicrosoftDocs/azure-docs-pr/pull/78138

@omartin2010 @CHEEKATLAPRADEEP-MSFT the document has been updated. #please-close


[Consensus Serialization] HoneyBadger

don't the variables which are getting set in the constructor are enough to complete the serialisation? or do we have to include all other variables as well?

How can we restore private variables? Do you have a good idea?


Gather network information using qemu-guest-agent

Author Name: OpenNebula Systems Support Team (OpenNebula Systems Support Team)
Original Redmine Issue: 5255, https://dev.opennebula.org/issues/5255
Original Date: 2017-07-19

Use a system similar to vCenter to gather network information for VMs that do not use IPs generated by OpenNebula.

Related to #1529

Example use:
virsh # domifaddr one-291532 --source agent --full
 Name       MAC address          Protocol     Address
-------------------------------------------------------------------------------
 lo         00:00:00:00:00:00    ipv4         <IP_ADDRESS>/8
 lo         00:00:00:00:00:00    ipv6         ::1/128
 eth0       02:00:0a:0a:02:01    ipv4         <IP_ADDRESS>/8
 eth0       02:00:0a:0a:02:01    ipv6         fe80::aff:fe0a:201/64

+1 for this. It is convenient to retrieve such IP details in this way. This will cover cases such as having deployed VMs with or without context. At the first case one verifies that contextualization is working while at the later one can access IP details even when no contextualization is configured.


chore: improve .gitignore and remove .DS_Store

Related Issue
Closes: #966
Changes made 👷🏻♂

Removed .DS_Store
Updated .gitignore (I have avoided duplicate ones)

@tamalCodes
I can still do this till 16th since I am very busy with Web3Conf, so I am not able to devote proper time.

So glad to hear that, I closed majority Issues because most of them were targeted at GSSOC with not much actual intrest in OSS. I'll re-open this up.

Done.

@tamalCodes
Feel free to tag me, if there are any open issues, that you want me to take.


Expose padding on RawScrollbar

Full context: https://github.com/flutter/flutter/pull/107172#issuecomment-1185081910
Allows the user to configure padding on the scrollbar thumb & track.
Pre-launch Checklist

[x] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[x] I read the Tree Hygiene wiki page, which explains my responsibilities.
[x] I read and followed the Flutter Style Guide, including Features we expect every widget to implement.
[x] I signed the CLA.
[ ] I listed at least one issue that this PR fixes in the description above.
[x] I updated/added relevant documentation (doc comments with ///).
[x] I added new tests to check the change I am making, or this PR is test-exempt.
[x] All existing and new tests are passing.

If you need help, consider asking for advice on the #hackers-new channel on Discord.

Add to the 'Scrollbar' widget too?

Add to the 'Scrollbar' widget too?

I am hesitant to do that, since that widget also does not expose margins. It feels like a slippery slope, if you add one, why not the others?
The Material scrollbar follows Material Design, and along with the Cupertino one, they are based on the native specifications. We try to avoid enumerating a lot of properties unless they are necessary, it leads to a bloated API. Usually on the lower level Raw* classes is where we have a lot of the lower level fine tuning available.
What do you think?


daemonic processes are not allowed to have children

Hi, I got below error while using multiprocessing
Traceback (most recent call last):
  File "/usr/lib64/python2.7/site-packages/flask/app.py", line 1997, in __call__
    return self.wsgi_app(environ, start_response)
  File "/usr/lib64/python2.7/site-packages/flask/app.py", line 1985, in wsgi_app
    response = self.handle_exception(e)
  File "/usr/lib64/python2.7/site-packages/flask_restful/__init__.py", line 273, in error_router
    return original_handler(e)
  File "/usr/lib64/python2.7/site-packages/flask/app.py", line 1540, in handle_exception
    reraise(exc_type, exc_value, tb)
  File "/usr/lib64/python2.7/site-packages/flask/app.py", line 1982, in wsgi_app
    response = self.full_dispatch_request()
  File "/usr/lib64/python2.7/site-packages/flask/app.py", line 1614, in full_dispatch_request
    rv = self.handle_user_exception(e)
  File "/usr/lib64/python2.7/site-packages/flask_restful/__init__.py", line 273, in error_router
    return original_handler(e)
  File "/usr/lib64/python2.7/site-packages/flask/app.py", line 1517, in handle_user_exception
    reraise(exc_type, exc_value, tb)
  File "/usr/lib64/python2.7/site-packages/flask/app.py", line 1612, in full_dispatch_request
    rv = self.dispatch_request()
  File "/usr/lib64/python2.7/site-packages/flask/app.py", line 1598, in dispatch_request
    return self.view_functions[rule.endpoint](**req.view_args)
  File "/data/bid/pipeline/app.py", line 121, in task_create
    run_task(config)
  File "/data/bid/pipeline/tasks.py", line 66, in run_task
    run_in_subprocess(_run_task, config)
  File "/data/bid/pipeline/tasks.py", line 27, in run_in_subprocess
    thread.start()
  File "/usr/lib64/python2.7/multiprocessing/process.py", line 124, in start
    'daemonic processes are not allowed to have children'
AssertionError: daemonic processes are not allowed to have children

relevant code:
def run_in_subprocess(func, *args, **kwargs):
    from multiprocessing import Process
    thread = Process(target=func, args=args, kwargs=kwargs)
    thread.daemon = True
    thread.start()
    return thread

This error not show in python:2.7 image.

Were you able to solve this?

I am wrong, this happend in python:2.7 too.

Thank you for the feedback!


Filter out DBs and versions with invalid characters

We've seen problems from versions that inadvertently included special
characters (like '{'). To avoid problems, skip over anything that's
not alphanumeric.
r? @scottjab
cc @stripe/storage

LGTM


Helm installation fails

Describe the bug
The Pulsar Helm installation to EKS fails with the below message.
Error: INSTALLATION FAILED: failed to create resource: ConfigMap in version "v1" cannot be handled as a ConfigMap: v1.ConfigMap.Data: ReadString: expects " or n, but found t, error found in #10 byte of ...|bleData":true,"broke|..., bigger context ...|tMemorySize=256m\n","autoSkipNonRecoverableData":true,"brokerServicePort":"6650","clusterName":"puls|...
command helm install pulsar apache/pulsar --namespace <my-ns> --set initialize=true --set volumes.persistence=false --set affinity.anti_affinity=false --set components.autorecovery=false --set zookeeper.replicaCount=1 --set bookkeeper.replicaCount=1 --set broker.replicaCount=1 --set broker.configData.autoSkipNonRecoverableData="true" --set broker.configData.managedLedgerDefaultEnsembleSize="1" --set broker.configData.managedLedgerDefaultWriteQuorum="1" --set broker.configData.managedLedgerDefaultAckQuorum="1" --set proxy.replicaCount=1
To Reproduce
Steps to reproduce the behavior:

Create a EKS cluster
Run the helm installation with values-one-node.yaml as values file from the examples directory of helm chart repo

Expected behavior
Should install pulsar components with only one instance
Screenshots

Closed as stale.
The development of the Helm Chart has been permanently moved to https://github.com/apache/pulsar-helm-chart. If it's still relevant, please open an issue there.


Add Enum generation for Django choice fields

It would be great to support generating enum return types for Django CharFields where choices are defined. Currently strawberry resolves all CharField values to a String type.
We'll need to make sure that we don't define duplicate enum types or use names that would clash with other types in the schema.
See https://github.com/graphql-python/graphene-django/issues/185#issuecomment-388639988 for a discussion about auto-generated choice enum types in Graphene.

Does this have to be Django specific? A choice-to-enum pattern/utility would be helpful regardless of framework or database.

@agritheory we do support python enums already! See here: https://github.com/strawberry-graphql/strawberry/blob/master/tests/test_enum.py
I've asked a friend to work on the design for the new website+docs so hopefully we'll start working on documentation soon :)

Closing as we have this https://github.com/strawberry-graphql/strawberry-graphql-django :D


add ++close for :terminal

also add {"term_autoclose": 1} for term_start.

I'll add test.

Codecov Report

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

@@            Coverage Diff             @@
##           master    #1950      +/-   ##
==========================================
+ Coverage    74.7%   74.73%   +0.02%
==========================================
  Files          77       77
  Lines      125686   125686
  Branches    28123    28123
==========================================
+ Hits        93900    93936      +36
+ Misses      31782    31750      -32
+ Partials        4        0       -4

Impacted Files
Coverage Δ

src/channel.c
83.88% <ø> (-0.1%)
:arrow_down:

src/os_unix.c
52.35% <0%> (-0.39%)
:arrow_down:

src/if_xcmdsrv.c
84.25% <0%> (-0.19%)
:arrow_down:

src/libvterm/src/screen.c
73.34% <0%> (+0.02%)
:arrow_up:

src/gui_gtk_x11.c
47.34% <0%> (+0.05%)
:arrow_up:

src/if_py_both.h
76.18% <0%> (+0.13%)
:arrow_up:

src/term.c
52.93% <0%> (+0.17%)
:arrow_up:

src/message.c
68.29% <0%> (+0.2%)
:arrow_up:

src/window.c
81.39% <0%> (+0.53%)
:arrow_up:

... and 2 more

Continue to review full report at Codecov.

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

Yasuhiro Matsumoto wrote:

also add {"term_autoclose": 1} for term_start.

Thanks for working on this.
I have been wondering about the syntax of options like autoclose.
We already have two existing mechanisms we could use:
:term <autoclose> {command}
:term ++autoclose {command}

We could even do:
:term +autoclose {command}
But that would be a new one, and confusing with "+cmd" for some
commands.  Also using "-opt" or "--opt", like used for shell commands,
would introduce a new mechanism, and probably can't be used with some
commands.
The two mechanisms were done for various reasons for different commands,
here we have a new command, thus we have a choice.  Hopefully we can use
the same for other commands later.
I don't expect any {command} to start with "<" or "++", so both could be
used.
I have a slight preference for using ++autoclose, mainly because :edit
uses ++opt and that's the most common command.
--
Shaw's Principle: Build a system that even a fool can use, and
only a fool will want to use it.
/// Bram Moolenaar --<EMAIL_ADDRESS>-- http://www.Moolenaar.net   \
///        sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \
\\  an exciting new programming language -- http://www.Zimbu.org        ///
\\            help me help AIDS victims -- http://ICCF-Holland.org    ///

Vim have :e ++enc=latin-1 or :e ++ff=unix or :e ++bin. Also :command -nargs=1. :map <buffer> as you mentioned. My opinion is <xxx> is provided for map command.

I don't have strong opinion.  So I'll change this to use <autoclose>.

Sorry, I don't really understand which style do you expect. When you decide, I'll update this patch. :)

Yasuhiro wrote:

Sorry, I don't really understand which style do you expect. When you
decide, I'll update this patch. :)

So far I prefer ++close.  Mainly because it's easier to type and also
because the ++ arguments in :edit are probably the most often used ones.
--
BEDEVERE: Look!  It's the old man from scene 24 - what's he Doing here?
ARTHUR:   He is the keeper of the Bridge.  He asks each traveler five
questions ...
GALAHAD:  Three questions.
"Monty Python and the Holy Grail" PYTHON (MONTY) PICTURES LTD
/// Bram Moolenaar --<EMAIL_ADDRESS>-- http://www.Moolenaar.net   \
///        sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \
\\  an exciting new programming language -- http://www.Zimbu.org        ///
\\            help me help AIDS victims -- http://ICCF-Holland.org    ///

Just remove auto for :terminal and keep term_autoclose for term-options.

I would say that I use map <…> far more often. But :terminal creates a buffer like :new, so what you selected is more consistent.


feat: add 'lowercase-title' option to upgrade action

Adds 'lowercase-title' option to the 'trunk-action/upgrade' action. Specifying the option converts the PR / commit title "Upgrade trunk" to lowercase, i.e. "upgrade trunk"
Example usage:

uses: trunk-io/trunk-action/upgrade@v1 with: prefix: "chore(deps): " lowercase-title: true

This change makes it possible to use the trunk upgrade action in a way that conforms to the commitlint '@commitlint/config-conventional' configuration which specifies that commit message subject must not be sentence-case, start-case, pascal-case, upper-case. With the default commit message title "Upgrade trunk" and prefix: "chore(deps): " the following error is emitted by commitlint using config-conventional:
⧗   input: chore(deps): Upgrade trunk to 1.19.0
✖   subject must not be sentence-case, start-case, pascal-case, upper-case [subject-case]
✖   found 1 problems, 0 warnings
ⓘ   Get help: https://github.com/conventional-changelog/commitlint/#what-is-commitlint

@TylerJang27 Could you take a look at this?

Hi @rriski! Thanks for the PR! Could you resolve the shellcheck issues seen here and I'll get this landed? You can also repro by running trunk check locally

Hi @rriski! Thanks for the PR! Could you resolve the shellcheck issues seen here and I'll get this landed? You can also repro by running trunk check locally

Hi, thanks for taking a look. Sure thing, I have now fixed the stylelint issue. To test the change I have a tmp.sh:
title_message="Upgrade trunk"

if [[ ${LOWERCASE_TITLE} == "true" ]]; then
  title_message=$(echo "${title_message}" | tr '[:upper:]' '[:lower:]')
fi

echo "${title_message}"

and executed it with different options:
❯ LOWERCASE_TITLE=true bash tmp.sh
upgrade trunk
❯ LOWERCASE_TITLE=True bash tmp.sh
Upgrade trunk
❯ LOWERCASE_TITLE=1 bash tmp.sh
Upgrade trunk
❯ LOWERCASE_TITLE=0 bash tmp.sh
Upgrade trunk
❯ LOWERCASE_TITLE=false bash tmp.sh
Upgrade trunk

Thank you @TylerJang27 for your review and for merging this into main. Could we possibly arrange for a new release to be issued? This would allow us to utilize the new option.

Yep, we'll get this released shortly! @puzzler7

@rriski It's released and the v1 moving tag has been updated to the latest release.


Back to top button visibility and position

Back to mobile view icon should only visible after scrolling the page, and it's position should be in bottom-right of the page. Adding title attribute on it will improve UX.
Desktop view

Mobile view

Please assign me the task, if you find this issue useful.


tests: make sure ctx we use for tests always has (the correct) analytics attached

Hello @nicks, @landism,
Please review the following commits I made in branch maiamcc/analytics-on-test-ctx:
306a57c378822ab269703823dfb196d0b4f66208 (2019-07-18 12:26:38 -0400)
tests: make sure ctx we use for tests always has (the correct) analytics attached
Code review reminders, by giving a LGTM you attest that:

Commits are adequately tested
Code is easy to understand and conforms to style guides
Incomplete code is marked with TODOs
Code is suitably instrumented with logging and metrics

better?


Validate that entities put in the store contain only fields that exist in the schema

Right now we'll hapilly put anything the mapping sends us into the store without validating that the fields actually belong to the schema for that entity. See https://github.com/graphprotocol/graph-node/issues/600 for a case of this happening due to a bug. But could also happen due to user error.
We should also validate that the fields can be converted to the type declared in the schema.

Yeah, this would be lovely to catch. It would require schema knowledge in e.g. the host WasmiModule so that we can validate store.set operations. Not that hard I imagine, the only thing I'm not sure is how we'd best pass the schema to the module.

@Jannis I thought a bit about this. Since the store will soon become the source of truth for schemas, then store.set will have easy access to the schema and can do the validation.

@leodasvacas Will it? In what way?

This has crept up again in the context of https://github.com/graphprotocol/graph-ts/issues/79
I'll add some validation; in particular, this will check for a store.set that

the entity type actually exists
the values being set actually have the proper type for the field
non-nullable fields are not set to null


SVG Cut off / doesn't respect height

I'm rendering an SVG, specified below. Even though the SVG has a specified height (500px), the output is a 259px image, which is consistent with the console output of the code below.
null { format: 'png',
  width: 188,
  height: 259,
  channels: 4,
  premultiplied: false,
  size: 4353 } null

import * as sharp from 'sharp';

const svg = `<?xml version="1.0" standalone="no"?>
<svg
  xmlns="http://www.w3.org/2000/svg"
  xml:lang="en" height='500' width="100%">
  <style type="text/css">
    svg {
        border: 1px solid red;
        font-family: Times;
        font-size: 96px;
    }
  </style>
  <text
    text-anchor="middle"
    alignment-baseline="hanging"
    x="50%" y="50%"
    dy='-144'>
    hello
  </text>
  <text
    text-anchor="middle"
    alignment-baseline="hanging"
    x="50%" y="50%"
    dy='-48'>
    hi
  </text>
  <text
    text-anchor="middle"
    alignment-baseline="hanging"
    x="50%" y="50%"
    dy='48'>
    hello
  </text>
</svg>`;

sharp(new Buffer(svg))
  .png()
  .toFile('test.png', console.log);

Figured this out, but leaving for others - setting a specific pixel-width fixes this.
height='500' width="100%" => height='500' width="400"

Yes, that's correct, the underlying renderer librsvg has nothing to apply the relative "100%" value to so has to guess.


MudTable MultiSelection="true" checkbox  bug

https://try.mudblazor.com/snippet/cEQFuhvCRWlUGUrE
when deleted one item, then check all  not working

https://user-images.githubusercontent.com/1549611/126064315-26766f4d-92da-4337-8d9b-32c92060c54f.mp4

@henon this is fixed. Not reproducable anymore, Issue can be closed.


Uses unsafe-eval

Would be nice with an unsafe-eval free version, both Vue and webpack should support it.

OK. I found which option causing CSP error.
    devtool: '#cheap-module-eval-source-map',

It shouldn't use cheap-module-"eval"-source-map.

Thanks!! :)

thanks your issue!!! 👍


Update to grapher UI with previews and star/trash

This includes a number of updates to the grapher UI, including units in plot labels (#104), preview information for selected datasets in the grapher directory view (#102), and star/trash label handling for datasets and directories (#130).

Comparing to the version on matrix-reloaded (as I have no way to specifically test this branch), I like the changes indicated by commits 2-5. So, for the features indicated by these commit titles, LGTM.
However, I don't know exactly what was changed in your first commit (sparse plot), so I can't comment on that. Do you have an example dataset for me to look at?
In addition note I have not checked the following:

Did these changes break anything else?
To what extent do the changes I looked at on matrix-reloaded reflect the status of these commits? Or have there been further updates to these features?
Code quality, since I don't know scala or typescript.

Further, I notice that there are absolutely no docstrings or comments anywhere in these commits. Are you sure that's good style in scala and typescript? Somehow I have my doubts...

@jwenner, the first commit here just adds a demo plot that produces a sparse dataset, for example here: https://matrix-reloaded.physics.ucsb.edu:7443/dataset/Test/Demo/Demo0000/00005/
The version on matrix-reloaded has numerous other changes that are not yet in PRs. I wanted to push ahead to get more feedback with people using the interface, because our review bandwidth is rather low at the moment.

In that case, assuming that this is all that the first commit does, LGTM as far as the functionality on all 5 commits subject to the note above about the limited nature of the review. However, I still am concerned about the lack of comments/docstrings.


Don't expose phf

Tauri currently exposes phf in its public 1.0 API, but phf is not 1.0. This violates C-STABLE.

phf is only exposed in generated code on the user crate. It should not be used directly. We will document this.

we should probably mark it #[doc(hidden)] too since that's its only purpose.  I mistakenly didn't mark it when exposing it.  While it's "breaking" it's not really a big deal since it's straight up a re-export and we didn't plan to support the re-export explicitly


broken link at Harmony event webpage

HARMONY 2022 will be a mixture of offline and online meeting similar to COMBINE 2021 (http://co.mbine.org/events/COMBINE_2021)

this link includes by error the final bracket

Details, including registration and abstract submission, can be found here.

and if you remove it and then try to reach the COMBINE 2021 details it redirects you to Harmony 2022

@Fontanapink This sentence is really not correct: "HARMONY 2022 will be a mixture of offline and online meeting similar to COMBINE 2021 (http://co.mbine.org/events/COMBINE_2021)."  We should remove it and replace it with current plans:
HARMONY 2022 is going to be organized as a hybrid event with in-person and online participants.  In particular:

April 26 : Online lightning talks (EST afternoon)
April 27-29 : in-person breakouts with online participants (8am to 5pm EST)
April 30 : online breakouts (8am to 5pm EST)

Fixed sentence. The original issue still is unresolved because the bug is in the old website.


Status View glyph does not always display when it should

Bug Report
Description
The Status View component contains logic that attempts to determine if the component has enough space to display the glyph.  In some cases, the glyph is not displayed even when there should be enough room for it.  This has been observed specifically in cases when the browser zoom level is changed.  The following link can be used to recreate the issue:
https://pages.github.cerner.com/healtheintent/action_plan/?knob-icon=plan&knob-title=Activities To Do&knob-subheading=5 of 8 activities need to be completed&knob-content=Card content&selectedKind=Components%2FNoActivitiesCard&selectedStory=default&full=0&addons=1&stories=1&panelRight=1&addonPanel=storybooks%2Fstorybook-addon-knobs
Steps to Reproduce

Using Chrome browser on desktop, set browser zoom level to 100%
Click on link above [a component using Status View should display with a glyph]
Set browser zoom level to 125%
Refresh browser [the component is displayed again this time without the glyph]

Additional Context / Screenshots

Expected Behavior
The glyph should alway be displayed regardless of the browser zoom level when there is no restriction placed on the height of the StatusView component.
Possible Solution
Change the logic that determines whether to display the glyph to be a little more forgiving.  Allow the calculated height of the StatusView contents to be 1 to 2 px greater than the height of the container.  At different zoom levels the calculated height of nodes can change slightly, probably due to the fact that offsetHeight used in the calculations is a rounded value.
Environment

Component Name and Version: terra-status-view v2.20.0
Browser Name and Version: Chrome Version 68.0.3440.84 (Official Build) (64-bit)
Node/npm Version: Node: 8.9.2 / yarn 1.3.2
Webpack Version: 3.12.0
Operating System and version (desktop or mobile): OS X El Capitan version 10.11.6

I have assigned this issue to myself.

we are not able to recreate this issue in our terra code. can you please check and  let us know whether this issue exists in your production code as well ?

I'm unable to reproduce this issue on our doc site as well: https://engineering.cerner.com/terra-ui/#/components/terra-status-view/status-view/status-view
But I am able to reproduce it in the link you provided I believe there is something outside of the terra code causing the issue as we are unable to reproduce it on the doc site.

I am able to reproduce this for several examples on the doc site by setting the zoom level to 110% and refreshing the browser.

I am able to reproduce on https://engineering.cerner.com/terra-ui/#/components/terra-status-view/status-view/status-view with zoom level set to 110% and 200%
@ShettyAkarsh we'll need to dig into this issue some more.

Yes, this issue is reproducible when the zoom level is set to 110% and 200%. this will be fixed as part of general refactoring planned for this component.

This issue occurs when the outer Div container (i.e which contains the status view component) height is not set and the default height value (which will usually be in the range of 250-300 pixels) is inherited from its parent container .
Here basically the inner view which basically holds the status view components (i.e message, title, glych etc) has the  height value lesser than the total height calculated taking each individual component inside the inner view. so the below condition fails and the glych icon component is not displayed in the DOM.
if (viewHeight < (componentsHeight + this.glyphNode.offsetheight))
{
DisplkayGlychIcon
}
The difference in which the condition fails is usually just by 1 pixels or lesser. as the status view components inner divs adjust to the height of its parent container. which traverse back to the main div container of the status view.  if the height of the main div container is not set this issues occurs at certain resolutions.
as the above provided link is not opening  just wanted to know here. so is the height value set for the outer div container of the status view in this case ? if height value is set for the outer div then, can you please let us know what is the height value ?


Redirect back to the previous page after posting a comment

To make UX less confusing redirect users to the previous page after posting a comment, so they can see their saved comment on the screen.

lg


Can not reach groundhog performance

Hi,
we are having a hard time to reproduce the results we got with GroundHog using Blocks.
Given the exact same training data, vocabulary, test set and settings we are 3 Bleu points behind GroundHog on a German to English translation task. We tried many different setups and number of iterations, but we can't reach it.
The GroundHog translation costs also seem to have a higher correlation between good and bad sentences then blocks. e.g.:
"vielen Dank ." translated to "thank you ."
a perfect translation and a common phrase which should have a low cost.
GroundHog cost: 0.000250929
Blocks cost: 0.357417
"fliegende Katze ." is translated to "fly away , cat ." not wrong but kind of a strange/unusual sentence.
GroundHog: 0.280177
Blocks cost: 0.267061
Blocks gives "thank you ." a higher cost to then "fly away , cat ." which seems strange to me. I take this as a hint that the problem is mainly related to the model and not to the search. The last comment here:
https://github.com/kyunghyuncho/NMT/issues/21
seems to have the same issue. Has there been any progress on this?
Any tips where the Blocks computation graph differs from the GroundHog graph (it's to large to just look at it an see a difference)? Or other hints what the problem could be?
Thanks,

We were getting comparable scores for cs-en when the initial pr was made, around august so the issues in NMT repo might be outdated. iirc the there were fixes at beam-search which uses the generate computational graph (same one we generate samples).
Have you checked whether the cost computational graphs are generating the same cost or not (using the same batch and initial parameters)?

Thanks for your fast response,
we didn't try that yet. It's next on the list of things to try. Right now we are looking into something else, I let you know if we find something.

Thanks, keep us posted

Henry Choi told me that he was able to reproduce English to French results
with this implementation.
On 8 January 2016 at 15:32, Orhan Firat<EMAIL_ADDRESS>wrote:

Thanks, keep us posted
—
Reply to this email directly or view it on GitHub
https://github.com/mila-udem/blocks-examples/issues/71#issuecomment-170115829
.

@critias Hi, I am wondering did you reach the Groudhog performance. If you did, how did you reach that? I am trying the example as well and I cannot reach the performance.

Hi,
yes and no. We got roughly equal results on the validation set during training, but not after reloading the saved model. Since we changed the code base a little to reload and translate the model I guess the error is on our side. It's still kinda unclear and we have to look into this in more detail, but were busy with other things last week.
Beside that we also try using orhanfs fork to see if his code to translate works better for us.

It turned out the problem was on our side. We changed some minor parts of the code that caused a mismatch between the encoding used to create the vocabulary (just bytes) and the encoding used during training/translation (unicode).
We are now able to reproduce the GroundHog results and even slightly surpassed it (0.4% Bleu).
I'll close the issue. Thanks for your help and keep up the good work.


Supply keys as headers in proxy config

Use a header such as X-NIPW-Key to pass 1 or more custom keys in the proxy host config.

Implemented with 9f4d03c.


Update e2e test framework code to be multi-cluster

This is being addressed in #34 and is being addressed along side #31. The e2e test framework code does a number of things including:

Create test namespace
Deploy cass-operator and CassandraDatacenter CRD
Deploy k8ssandra-operator and K8ssandraCluster CRD
Delete test namespace

Currently these actions are only performed against a single cluster. Code needs to be updated so that they run against all clusters. We only want to deploy k8ssandra-operator in the control plane cluster though.
As I mentioned I am doing this work in #34, but I wanted to create a separate ticket because the work is fairly involved and might take a day or two.
┆Issue is synchronized with this Jiraserver Task by Unito
┆Epic: CI/CD Environment Bootstrap
┆Fix Versions: k8ssandra-2.0.0-alpha
┆Issue Number: K8SSAND-694
┆Priority: Medium

This is done. The test framework deploys the operator across multiple kind clusters and has a number of methods to perform operations across multiple clusters.


Bower version ?

Is bower version of Toastr  is up to date?
I've version 2.1.0 but I don't see preventDuplicates and progressBar in src.
After investigations, Bower version in bower.json file is 2.1.0 BUT toastr.js file is in 2.0.3.

@phmatray I'm getting the latest version of toastr. Try cleaning your bower cache with bower cache clean. It happens all the time to me on win box.

i just verified the toastr.js files here and in the bower repo are 2.1.0


Update docs

Cover minimal contents such as:

introduction
installation
quick start guide

And api docs with the github page enabled.


Changes made by https://github.com/vsviridov

To work with new version of Sequelize to handle promises.

Thanks! Looks like you need to increment the Sequelize version in the package.json because the tests are failing.

Actually, looks like it's a failure in the beforeEach.


NTR: histone H3-K36 demethylase

Hi,
I need a new term for a specific histone demethylase in the function
ontology. We don't seem to have any histone demethylase terms, or
even much in the way of protein demethylase terms. The EC
classification doesn't seem to have them either, so I've already
submitted a report suggesting the addition of the one that the paper I
read characterized. I'm asking for 1 specific term with this request, but
the paper I read discussed a previously characterized activity that is
different, so I also put some info about that here since it seems that we
should at least have a term for the activity.
As I said, for the one I need, I have already submitted a report to the
Enzyme Commission, copied here. I think you can get the term name
and a definition out of that. Right now, it might just have to go under
'catalytic activity' because I have no idea where it belongs, but once the
EC has added it, we could just move it appropriately.
thanks,
-Karen
REPORT FORM FOR AN ENZYME NOT CURRENTLY INCLUDED
IN "ENZYME NOMENCLATURE"
--------------------------------------------------------
Proposed name(s):
Primary name: histone-lysine(H3-K36) demethylase
Reaction catalysed:
methyl-lysine + alpha-ketoglutarate + O2 --> succinate + CO2 +
HCHO + lysine
can also demethylate dimethyl-lysine to monomethyl-lysine
Subclass in Enzyme Nomenclature proposed: no idea
Source of enzyme:
Organism: human, S. cerevisiae
Cofactor requirement(s):
Fe(II)
Brief comment on specificity:
"We analysed its site specificity using histone substrates radiolabelled
at all known methylated sites in histones H3 (K4, K9, K27, K36, K79)
and H4 (K20, R3). Of the seven substrates, only H3-K36 methylated by
Set2 was a substrate for JHDM1A."
Other comments:
They refer to the human protein as FBXL11, but when I search Entrez
for that name, I get two entries. Because I am not sure which they
used, I have put a quote from the paper here, rather than guessing
which accession number is correct.
"Because histone demethylase activity is the first function attributed to
FBXL11 and because FBXL11 is the first JmjC domain-containing
protein shown to possess histone demethylase activity, we have named
the protein JHDM1A (JmjC domain-containing histone demethylase
1A.). The highly related protein FBXL10, which we have named
JHDM1B (Supplementary Fig. S3a), is also an active H3-K36
demethylase (data not
shown)."
References:
Tsukada YI, Fang J, Erdjument-Bromage H, Warren ME, Borchers CH,
Tempst P, Zhang Y (2005) Histone demethylation by a family of JmjC
domain-containing proteins. Nature (epub ahead of print)
PubMed ID:16362057
---------------------------------------------
quote from paper about other histone demethylase activity:
Using a candidate approach, it has been demonstrated that LSD1/
BHC110, a nuclear amine oxidase homologue previously found in
several histone deacetylase complexes8, 9, 10, can specifically
demethylate monomethyl-H3-K4 (H3K4me1) and H3K4me2 in a FAD
(flavin adenine dinucleotide)-dependent oxidative reaction.
8.  Hakimi, M. A.  et al. A core-BRAF35 complex containing histone
deacetylase mediates repression of neuronal-specific genes. Proc. Natl
Acad. Sci. USA 99, 7420–7425 (2002)
9.  Shi, Y.  et al. Coordinated histone modifications mediated by a CtBP
co-repressor complex. Nature 422, 735–738 (2003)
10.  You, A. , Tong, J. K. , Grozinger, C. M.  & Schreiber, S. L.  CoREST is
an integral component of the CoREST-human histone deacetylase
complex. Proc. Natl Acad. Sci. USA 98, 1454–1458 (2001)
Reported by: krchristie
Original Ticket: "geneontology/ontology-requests/3122":https://sourceforge.net/p/geneontology/ontology-requests/3122

thanks www.movied.org


Package error on QfieldCloud because of Z coordinate

Since 2-3 days we experience a package error for one layer. Because of this, 5000+ features don't show up in the QField app (but do show up in QGis when syncing). Both the latest qfield release 2.8.4 and the earlier 2.8.0 no longer show these features (so I don't think the problem is with one or the other release).
Is this a problem that can be solved on the cloud side or do I have to solve this on the project side? The *.qgs project or layer properties were not changed on user side. The data are stored in a gpkg file. The warning of the newer QGis version existed before. The 'loc' error is in another layer. All pushed changes from collaborators in the 'broken' layer were applied without error.

The organisation/project name is ANB/Walden_v5a
User name is boswachter_marc
The affected layer is a simple linestring layer 'SurveyWerkpadenEnLijnen' (QGis layers data and packaged layers data say no-error).
I am using QGis 3.32.0-Lima on Ubuntu and QFieldSync v4.5.0
Update:
I did a validity check and cleaned up the geometry of the relevant line layer (also with the topology checker) and synced back from QGis to QFieldCloud but the issue remains.
When using QFieldSync with cable, the features are also missing in the layer. In other words, this is perhaps a QFieldSync issue?

I am publishing a updated version of the project in the cloud. After cleaning the geometries and deleting features without geometry, it looks like the problem is solved in the new project. When syncing by cable or cloud, all the features are visible again.  There are no longer any errors in the 'job' except for: "Loading a file that was saved with a newer version of qgis (saved in 3.32.0-Lima, loaded in 3.30.3-'s-Hertogenbosch). Problems may occur"

I am afraid the problem is back...
Nothing was changed project wise; only some collaborators pushed new registrations in the linestring layer.

Assuming that the problem had something to do with z-values, I used the processing toolbox to search for z-values (tool extract z-values). I found one feature out of the 5030 that had a z-value. I deleted it in QGis and synced back to the cloud. There is no longer a packaging problem or message saying the geometry type is not compatible! In other words, all the missing features are visible again in QField.

Looks like #774 is the causing bug. I'm happy to see to not be the only person that is affected (and has the debugging skills).
Do you have any idea, why some points are PointZ at your project?  We are adding all points with QField on different devices, but only some (for me) random Points are PointZ instead of Point.

I have no idea how that single Z-value got there. We work with QField on different smartphones or tablets, with the same GNSS receivers but with different connecting apps like NTRIP Client and Geode Connect. Sometimes points or lines are added with the QField app on pc. I wonder if that could be the cause.

Hi @BoswachterMarc is this still an issue?

Hello @m-kuhn, yes, it is still a issue.
For the moment, I can't replicate it: one way or the other, when collaborators have registered a line feature with QField and they try to change that line feature in QField (each time with a external gnss receiver), a z-value is added to the feature data. The problem does not occur when they register//trace new lines.
When I search for that z-value in QGis with the processing toolbox (remove z-values), i find one or more z-values (for example one, two or more out of the 5000+ features). When I redraw that/those line(s) and I delete the modified one(s), the problem is gone. In the last two weeks it happened twice. I should ask the colleagues what changes they were making.
Anyway, I can confirm that because of the z-value, QFieldCloud gives the error: "geometry type is not compatible with the current layer"
By the way, i suppose there is a nobler way to remove z-values but I haven't looked for it yet...

I think I start to understand, you have a layer with geometry Type LineString, when someone edits a feature, the geometry is stored as LineStringZ in the offline package. Now when synchronizing this to the main data, it won't synchronize because of the different geometry type.
Yes, it would be great to have information how to reproduce.

The QFieldCloud project highly values your report and would love to see it addressed. However, this issue has been left in feedback mode for the last 14 days and is being automatically marked as "stale". If you would like to continue with this issue, please provide any missing information or answer any open questions. If you could resolve the issue yourself meanwhile, please leave a note for future readers with the same problem and close the issue.
In case you should have any uncertainty, please leave a comment and we will be happy to help you proceed with this issue.
If there is no further activity on this issue, it will be closed in a week.

This issue is not solved yet i fear - just ran in the same problem!

Hello @meyerlor and @BoswachterMarc, today I conducted 3 tests with different projects, which contain layers with Z, M, and ZM geometry types, and the synchronization process ran successfully.
If the issue persists with your projects, could you provide us with a sample project for better investigation?

sorry to grave dig here - just ran again in that error (sorry i did not answer earlier) - i looked for z-values, but my layer has none, so it might be another problem - the sync to QField via cloud works with the old, deprecated packager. with the new one i get the error @BoswachterMarc  described.
ProjectID on QField Cloud is 6de7584b-81c7-4f0c-82e0-4570a9d5953d (or do you want the .qgz + .gpkg here via github? )


disabling Polkadot Decoded Vote ad

Disabling polkadot decoded voting ad temporarily,  until the registration page is live.

lgtm


Remove data from sub-model modules

Remove the data files from the sub-model modules.  Must keep github happy!

Removed data files from kopp14 icesheets and kopp14 thermalexpansion.  Committed changes to the branch and now waiting for pull request approval.

It appears as though the data files still exist in the history of the repo.  When cloning the repo, hundreds of MB worth of data are downloaded...and the scripts definitely shouldn't take up that much space.  How do we entirely remove these files from the repo?

Yes, they do remain in the history. Once we are ready to merge we will use the approach documented here: https://help.github.com/en/articles/removing-sensitive-data-from-a-repository

I followed the instructions in the link you sent using BFG to remove the history of the data files.  It looks like it was able to clean things up.  Go ahead and remove any cloned instances of this repo you may currently have and re-clone the repo.

Data removed and branch merged.


silx view aborts when opening IPython console

With silx 0.7.0 on debian8 (rnice8 at least) silx view aborts when one tries to open the embedded IPython console from the GUI.
To reproduce: visualize some curves with silx view and open IPython console (Options->Console).
Error message:
QWidget: Must construct a QApplication before a QPaintDevice
Aborted

On another debian8 computer silx view breaks while loading IPython widget tries to load PyQt4 while silx view loads PyQt5.

Even if I don't like it, I think it is worth doing true lazy-loading of silx.gui.console.
On one side we would loose is disabling the console action if it cannot be used.
On the other side, problems related to IPython widget would only arise when actually requesting the console.

Debugging is made very difficult by the wide range of supported versions of qtconsole/IPython versions.
Ideally I would like to have no try / except in the imports, and only import qtconsole (not IPython).
If this solves your issue, I think it would be preferable to risking to crash the application when someone tries to open the console.
It would just be a matter of teaching users to add a hard dependency on a recent version of qtconsole, in their applications.

Those issues looks to be due to silx view using PyQt5 while IPython v2.3.0 (on debian8) loads PyQt4 and does not check for PyQt5 being loaded...
The option to drop support of old versions of IPython/qtconsole would solve this issue as newer versions support PyQt5.
Are we just OK to drop the console widget on debian8?
To me it seems necessary as we now use PyQt5 as the preferred binding...


Optimize build process

Discussed in https://github.com/railtoolkit/tikz-trackschematic/discussions/17

Originally posted by apriljunge March  3, 2022

Replace copying with environment variables
I am really unsure about this, because I do not know what's exaclty the magic behind copying the files to different folders. It didn't work for me. I could fix it by setting the environment vairable TEXINPUTS (example below for test.sh). Maybe this snippet could replace the copy process? Then maybe the script doesn't need super user rights any more? The environment variable modifies the directories where pdflatex looks for sty files (stackexchange discussion)

export TEXINPUTS=.:../src/:$TEXINPUTS

included with https://github.com/railtoolkit/tikz-trackschematic/commit/c9f5e7a7ba7282c719096dde8035583e1e791e10


CAMEL-11254-Default matchOnUriPrefix to false on Undertow endpoint

Thanks for the PR it has been merged. Do you mind closing this?

thanks for accepting. closing.


melpa(-unstable)-packages 2016-06-12

htmlize broke their hash again, so I ran a full melpa update
cc @ttuegel

fix #16174 (this has intero)


Failed to find .spr for garments

zrenderer can't find some garments .spr files
this is because in some cases gravity only add 1 .spr file and it is located in the root of item folder:

request example:
{
    "job": ["4063"],
    "action": 96,
    "head": 21,
    "headPalette": 6,
    "headgear": [1985,1309,572],
    "gender": 0,
    "garment": 107,
    "bodyPalette": 3
}

result:

zrenderer should also check for .spr in: sprite/로브/item_folder/

Thank you for reporting. Is this something the new clients are doing? I haven't yet gotten the 2021 clients working with rAthena and on my 2018 client it doesn't show the garment unless the corresponding spr name exists for the job.

seems fixed, thanks for your attention and time.

sorry, i don't know since from when it started to use only 1 .spr file, i discovered because i was facing the same issue in another project:
https://github.com/Balferian/ROChargenPHP/pull/1/commits/a12c23d6f1495668810170c9753f4f4ab04a946e


Added github comment icon workflow

This automatically creates and updates a comment in PRs that shows a preview of all icons that have been changed or updated.
Example

Performance
The action itself is quick due to not running any calculations or even starting up Node.
The API route is cashed and takes less than 200ms to return the rendered svg.

Permission problems
This workflow only runs for PRs that are created from inside this repository.
https://securitylab.github.com/research/github-actions-preventing-pwn-requests/

This looks pretty neat, although useful as it is, I think we'll still have to do some validations manually.
I think the white "midlines" will need to be a bit thinner.
What exactly do the colours represent?

The different colors are, so you can easily see when things are not 100% connected, like here in the cat ear for example.

@jguddas Nice work, looks really cool!
I think this really helps the review process of icons.
Maybe we can add the 100% scale variant of the icon somewhere as well.
I noticed that the builds are failing for site and the github action. Can you check what is going on?

@jguddas: do you think it could be possible to different shapes for points within a path and endpoints of paths?
I think that could be super useful for finding misaligned paths and checking if paths are incorrectly merged or broken up for no reason.

@jguddas: do you think it could be possible to different shapes for points within a path and endpoints of paths?

Great idea.
There are 3 things:

Path elements
Path segments (the things split in d using Move command)
Path commands.

I would like to highlight move commands by adding the big start/end circle.
What do you think?
I don't know how to best highlight the path elements.

On the right side, the color is based on the path commands.
On the left side, I changed it, so the colors are different for each Path element.

Nice, the one on the right seems much more legible to me apart from colours that are a bit too close in hue.
A few more questions:

Why is the top control point from the head's circle missing? Is it a bug or is it on purpose?
Is it maybe possible to differentiate closed and non-closed paths? (again, for the head's circle it is not important which point is the starting point, since it's closed)

@ericfennis I don't have access to the build, but I can tell you why the action is failing.
The action fails due to being run from a fork, I will see if I can find a quick fix.

Why is the top control point from the head's circle missing? Is it a bug or is it on purpose?

It's due to being a circle element instead of a path, what do you think of only showing control points for path elements?

Is it maybe possible to differentiate closed and non-closed paths?

Good idea, I think it would definitely be nice to only show the start/end node for open paths.

I have removed the start and end marker for closed paths.
I have removed the control points from non path elements (see head).
I have changed it, so the control points are only shown for start and end of path segments.
I have submitted a pr to svgo to optimize closed paths https://github.com/svg/svgo/pull/1751
I have submitted an issue to svgo to optimize arcs (like here in the wheel chair wheel) https://github.com/svg/svgo/issues/1748

I moved the whole thing into a react component :tada:

That should be everything.

@ericfennis can I get your okay?

@jguddas Sorry for the late reply, was a bit busy.
I think this is still a great tool for reviewing icons.
I really want to test it before we merge this, maybe we can add a dummy icon in this PR to see it?
I notice that the Vercel build is failing, you need to update the pnpm lockfile. Run pnpm install.
Build error:

Also the site/api/gh-icon.ts file is missing in the PR, is it removed?

Well I tried to test it with the preview deployment and it doesn't work.
https://lucide-btt1rfnxj-lucide.vercel.app/api/gh-icon/PHN2Zz4gICA8cGF0aCBkPSJNMiAxN2E1IDUgMCAwIDAgMTAgMGMwLTIuNzYtMi41LTUtNS0zLTIuNS0yLTUgLjI0LTUgM1oiIC8+ICAgPHBhdGggZD0iTTEyIDE3YTUgNSAwIDAgMCAxMCAwYzAtMi43Ni0yLjUtNS01LTMtMi41LTItNSAuMjQtNSAzWiIgLz4gICA8cGF0aCBkPSJNNyAxNGMzLjIyLTIuOTEgNC4yOS04Ljc1IDUtMTIgMS42NiAyLjM4IDQuOTQgOSA1IDEyIiAvPiAgIDxwYXRoIGQ9Ik0yMiA5Yy00LjI5IDAtNy4xNC0yLjMzLTEwLTcgNS43MSAwIDEwIDQuNjcgMTAgN1oiIC8+IDwvc3ZnPiA=.svg
But replacing https://lucide-btt1rfnxj-lucide.vercel.app with localhost:3000 does work :thinking:.

Now it works.
https://github.com/jguddas/github-icon-worflow-test/pull/3

Also how do we deal with a PR with multiple icons? 🤔

How it also works in dark mode.
https://github.com/jguddas/github-icon-worflow-test/pull/10

@jguddas: Really nice, I love the latest changes (dark mode support + extra 1px outline to check for gaps). :)

@jguddas: I think this is almost good to go, but I still strongly believe CSS classes should be used to style the paths, since there are a looooot of repeating attribute values, and dark mode support should be handled not by using a <picture> tag and generating separate preview files, but via CSS prefers-color-scheme media queries embedded within the preview files.
(It could also be a good idea to insert HTML comments before each section, stating the purpose of that group of paths (grid, centerlines, outlines, points, arcs etc.).

It would be nice to not have to use the picture tag, but I'm not sure how I would go about cleanly integrating style tags.
What about getting rid of the duplications by using groups like this?
-

-

+ <g strokeWidth={5} >
+

+

+ </g>

Yeah, grouping is also a good idea, although I'd probably go for BEM style CSS classes instead of using the id attribute, should the SVGs ever need to be embedded in an HTML page (some debug page on the app review site maybe?) where the global IDs would no longer be unique.

I've posted a PR for this branch that solves dark mode support via CSS only, eliminating the need for building separate icons for light and dark modes.

@jguddas: any chance of also adding a curvature preview in v2.0? 😅🤪

as in https://www.figma.com/community/plugin/932729267119671976/Curvature

An edit page that makes it easy for people to contribute by showing them errors and a preview of their icon would be super nice IMO.

Okay @karsa-mistmere, @ericfennis lets merge this!

Okay @karsa-mistmere, @ericfennis lets merge this!


[LIBCLOUD-973] Support disk_size parameter for boot disk when creating instance.

Support specifying the disk size for boot disk when we create (one/more) google compute cloud instances.
Description
This is fix for LIBCLOUD-973 bug.
Link to bug: https://issues.apache.org/jira/browse/LIBCLOUD-973
The ex_create_multiple_nodes API call in gce.py compute driver
does not handle boot disk size. Hence it creates a boot disk of size 10GB every time.
Added disk_size keyword parameter to ex_create_multiple_nodes API call,
It passes the parameter through internal method calls and adds the disk size to the POST request.

API call sequence:

ex_create_multiple_nodes
_multi_create_node
_create_node_req
_create_instance_properties
_build_disk_gce_struct

Status

done, ready for review

Checklist (tick everything that applies)

[X] Code linting (required, can be done after the PR checks)
[X] Documentation
[ ] Tests
[ ] ICLA (required for bigger changes)

Thanks! Merged in trunk. ✨


2404.1

Allow for ISOs with single index WIMs to work Issue 10 - Need to investigate this.
Revert code back to allow optimized FFUs to be applied via ApplyFFU.ps1 now that Sept 2023 ADK release has FFUProvider.dll fix

Will the next update also reinstate the code to enable the creation of the recovery partition in BuildFFUVM.ps1?

Maybe. Depends on if I get around to it. I keep kicking it down the road because things are working OK now and I wanted to get some of the other features in that I've added recently. I'll also need to add a check to make sure the user is running the latest ADK, which I'm assuming most don't have the Sept ADK installed.
Just to be clear, the recovery partition does get created, it just happens during the application of the FFU on the device. So all recovery scenarios should work fine.
Is not having the recovery partition in the FFU itself causing any issues for you?
Thanks,
Richard
From: Zehadi Alam @.>
Sent: Wednesday, March 27, 2024 8:17 PM
To: rbalsleyMSFT/FFU @.>
Cc: Richard Balsley @.>; Author @.>
Subject: Re: [rbalsleyMSFT/FFU] 2404.1 (Issue #15)
Will the next update also reinstate the code to enable the creation of the recovery partition in BuildFFUVM.ps1?

Reply to this email directly, view it on GitHubhttps://github.com/rbalsleyMSFT/FFU/issues/15#issuecomment-2024324141, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AMYE2BHXSAOHTAYE6EIAUL3Y2ODUBAVCNFSM6AAAAABFEFAI6KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMRUGMZDIMJUGE.
You are receiving this because you authored the thread.Message ID<EMAIL_ADDRESS>

Understood. I haven't encountered any issues without the recovery partition - just something I was curious about.
Regarding the ADK portion of the script, I was also considering implementing additional checks in the Get-ADK function for more reliable detection (a computer with the SDK installed but not the ADK will still report as having the ADK installed). Also wanted to handle some additional cases (ADK is installed but not the necessary components/add-on). Let me know your thoughts. I can submit a PR for this once complete.
--Zehadi

That sounds good to me. I can see where those issues could come up.
Thanks,
Richard
From: Zehadi Alam @.>
Sent: Thursday, March 28, 2024 11:42 AM
To: rbalsleyMSFT/FFU @.>
Cc: Richard Balsley @.>; Author @.>
Subject: Re: [rbalsleyMSFT/FFU] 2404.1 (Issue #15)
Understood. I haven't encountered any issues without the recovery partition - just something I was curious about.
Regarding the ADK portion of the script, I was also considering implementing additional checks in the Get-ADK function for more reliable detection (a computer with the SDK installed but not the ADK will still report as having the ADK installed). Also wanted to handle some additional cases (ADK is installed but not the necessary components/add-on). Let me know your thoughts. I can submit a PR for this once complete.
--Zehadi

Reply to this email directly, view it on GitHubhttps://github.com/rbalsleyMSFT/FFU/issues/15#issuecomment-2025879922, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AMYE2BEK6UB6MHHY7B5AWWTY2RQBHAVCNFSM6AAAAABFEFAI6KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMRVHA3TSOJSGI.
You are receiving this because you authored the thread.Message ID<EMAIL_ADDRESS>

@zehadialam Thanks to your ADK work, I've added back in the code to generate the recovery partition. Made some slight modifications to the sizing to make sure to have at least 250MB of free space as per docs. I'm leaving the commented code in for now in case anyone has problems. In my testing though, things seem to be working well. I'll probably do a comment cleanup in 2405.1 since there are quite a few commented out lines that shouldn't be necessary moving forward.


Created new term "Sidecar Container"

Describe your changes
Created new term "Sidecar Container"
Related issue number or link (ex: resolves #issue-number)
resolves #2958
Checklist before opening this PR (put x in the checkboxes)

[X] This PR does not contain plagiarism

don’t copy other people’s work unless you are quoting and contributing it to them.

[X] I have signed off on all commits

signing off (ex: git commit -s) is to affirm that commits comply DCO. If you are working locally, you could add an alias to your gitconfig by running git config --global alias.ci "commit -s".

@iamNoah1 , would you please have a look ? Thanks.

@iamNoah1 Thank you for the patience with me! I think I got it now. Looking forward to any comments or suggestions to improve it. Thanks once more


drotation

Hi - I think it would be good to have a drotation property on game objects. This would function the same as dx and dy and allow for delta time updates automatically.

Thanks for the suggestion. Could you elaborate more on what you mean by allowing delta time updates for dx and dy? Maybe some code examples of how you would want to use drotation?

Sorry - I probably confused things by mentioning them. When you use dx and dy it automatically applies a force to the x and y properties using delta time to get smooth motion at 60fps. I think the same thing for rotation would be useful.


Why is there no UI?

The registry:2 container is started, but no UI is shown when one navigates to localhost:5000

Docker Registry is a backend service and doesn't have any web UI.
You can continue learning about Docker Registry here. If you're looking for a registry with a management UI, maybe take a look into Docker Trusted Registry.
I'm closing this issue since it doesn't report anything we can improve on docs.docker.com. Feel free to open more issues if you find anything wrong with docs.docker.com 🐳


The plugin doesn't work on windows

Description of Issue
Just follow the tutorial , build and install the plugin , when I run "usdview ./src/usdTri/scenes/triangle.usda" in cmd,  it says " ModuleNotFoundError: No module named 'usdpluginexamples'", "Load of usdpluginexamples.UsdviewTri for usdpluginexamples.UsdviewTri failed". The detail is below, I Don't have any idea about this issue. My USD version is 23.05, built in release. I Need help.
Steps to Reproduce

build and install plugin
set up environment variables for plugin
run usdview ./src/usdTri/scenes/triangle.usda in console

System Information (OS, Hardware)
Windows 10
USD 23.05
python 3.10.5
cmake 3.24
visual studio 2022
Build Flags

sorry, I forget to add "${USDPLUGINEXAMPLES_INSTALL_ROOT}/lib/python" to PYTHONPATH. But the error still occur.

Hi @myartings, can you set TF_DEBUG environment variable to "*" prior to launching usdview, then copying & attaching the logged output here?  Thanks!

@rlei-weta Here is the log.
log.txt

Much appreciated @myartings - it looks like the usdTriImaging.dll plugin was loaded but not in a good state.  I will find access to a Windows machine to try and repro this -- will touch base soon

@myartings wanted to give you a heads up that I was able to reproduce the issue you were seeing on Windows.  I don't know what the root problem is yet so will need to investigate.  Thanks for your patience!

Hi @myartings I've merged #45 into main which should fix the issue you are seeing (thanks @OleksiyPuzikov for the suggestion).  Let me know how that goes


Fixes #47: Multi-return function arguments aren't properly supported in codegen

Fixes #47

Pull Request Test Coverage Report for Build 699543985

5 of 7 (71.43%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.05%) to 74.434%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

internal/generator/method/method.go
5
7
71.43%

Totals

Change from base Build 673203423:
-0.05%

Covered Lines:
690

Relevant Lines:
927

💛  - Coveralls


Date pickers universal

Description of the new feature / enhancement
Via executable command or hotkeys opens a popup calendar or clock face to write down dates and/or times.
Scenario when this would be used?
Every time you write a text.
As can be done with the clipboard and Windows Emoji.
Supporting information
No response

Win+N pops out notification center which has the calendar.   is that not enough?  /needinfo

I would like to upvote this, and respond to the WIN-N  question.  Win-N would be great if you could right click on a date and it would give you a "copy date to clipboard" option. Powertoys seems like the perfect option for this, and seems easy to implement.    I've implemented a similar tool inside excel using VBA. But this would make it a universal app for any and all situations requiring a date pick


[ISSUE #2289] Serverless schedule support builtin core

What is the purpose of the change
In order to meet the requirements of flexible time delay messages
Brief changelog
redesign the architecture of delay messages(different from the current delay message, the delay message here refers to the message delivered at a specific time or delayed a period time) and introduce Time Wheel.

Verifying this change
Yes
Follow this checklist to help us incorporate your contribution quickly and easily. Notice, it would be helpful if you could finish the following 5 checklist(the last one is not necessary)before request the community to review your PR.

[x] Make sure there is a Github issue filed for the change (usually before you start working on it). Trivial changes like typos do not require a Github issue. Your pull request should address just this issue, without pulling in other changes - one PR resolves one issue.
[x] Format the pull request title like [ISSUE #123] Fix UnknownException when host config not exist. Each commit in the pull request should have a meaningful subject line and body.
[x] Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
[x] Write necessary unit-test(over 80% coverage) to verify your logic correction, more mock a little better when cross module dependency exist. If the new feature or significant change is committed, please remember to add integration-test in test module.
[x] Run mvn -B clean apache-rat:check findbugs:findbugs checkstyle:checkstyle to make sure basic checks pass. Run mvn clean install -DskipITs to make sure unit-test pass. Run mvn clean test-compile failsafe:integration-test  to make sure integration-test pass.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

Please help to review this pr, thanks. @RongtongJin @duhengforever @vongosling

Great, I would like to follow it.

Can you write some test cases and their results which you have already tested in this pr's link? @Aaron-He

The approach is obvious and vivid,  here are some suggestions(maybe I don't have a thorough graspt of code):

Besides DelayMsgCheckPoint file is persisted on master node, the checkpoint should also be synchronized to slave node periodly; otherewise, if master node crashes down and fails to restart, slave node does not know the timestamp the message can be delivered from;

In method putKey() of file DelayMsgIndexFile.java, if the method is used in multi threads, we will need to lock before operating the index file; otherwise, we might not need to release the file lock since we never use it;

For the message delivered, we'd better keep its physical commitlog offset to a log let's call it deliveryLog,
if master node restarts, we need to find out all the the undelivered messages between deliveryLog and index file, it can try to reduce the number of duplicated messages on the server side.
Whether or not to sync the deliveryLog to slave node? Maybe we need to discuss it later.

If a large mount of delay messages fall into lots of commitlog files randomly,  the speed of delivering delay messages will be slow because of random reading. From our internal tests, the speed is about 200-300 tps on normal disk(15K Rounds Per Minute). Shall we need to limit produce rate?

Let's work together to build open source community better.

I found another problem needed to discuss:
if timewheel deliveries the delay messages  a little later than excepted, assuming now is 9:00 but the timewheel is deleverying the message at 8:30, meanwhile, the system begins to remove the commitlog, the message between 8:30 and 9:00 in the commitlog(going to be removed soon) might be lost forever.
Sometimes it is useless to deliver the delay message much later than excepted,  maybe we need to rebalance how late the message we can remove directly.

Coverage increased (+0.4%) to 51.717% when pulling c45a95c4f24edaecc9495d84a1e18ee8d1d7d324 on Aaron-He:delay_msg into 2abda6d204068517b42a8cd4f0f01c7139511ebd on apache:delay_msg.

The approach is obvious and vivid, here are some suggestions(maybe I don't have a thorough graspt of code):

Besides DelayMsgCheckPoint file is persisted on master node, the checkpoint should also be synchronized to slave node periodly; otherewise, if master node crashes down and fails to restart, slave node does not know the timestamp the message can be delivered from;
In method putKey() of file DelayMsgIndexFile.java, if the method is used in multi threads, we will need to lock before operating the index file; otherwise, we might not need to release the file lock since we never use it;
For the message delivered, we'd better keep its physical commitlog offset to a log let's call it deliveryLog,
if master node restarts, we need to find out all the the undelivered messages between deliveryLog and index file, it can try to reduce the number of duplicated messages on the server side.
Whether or not to sync the deliveryLog to slave node? Maybe we need to discuss it later.
If a large mount of delay messages fall into lots of commitlog files randomly,  the speed of delivering delay messages will be slow because of random reading. From our internal tests, the speed is about 200-300 tps on normal disk(15K Rounds Per Minute). Shall we need to limit produce rate?

Let's work together to build open source community better.

Good suggestion
putKey() is used by reputService, which is single thread. yeah, we can remove the release code block.
Good suggestion. As current implementation, user identifies duplicate messages.
It may not work to limit produce rate, because the delayMsgs delivery is up to its startDeliverTime. We can use more memory to make performance better. There may be other better solutions.

Let's work together to build open source community better. ^_^

I found another problem needed to discuss:
if timewheel deliveries the delay messages a little later than excepted, assuming now is 9:00 but the timewheel is deleverying the message at 8:30, meanwhile, the system begins to remove the commitlog, the message between 8:30 and 9:00 in the commitlog(going to be removed soon) might be lost forever.
Sometimes it is useless to deliver the delay message much later than excepted, maybe we need to rebalance how late the message we can remove directly.

We can separate the commitlog of delayMsg from the normal messages commitlog in the next version.  we can work together.

Any process for this pr?

@vongosling We have already tested by ourselves, and deploy in my production enviroments, but no one review this codes in commnunity.

There are many versions in the community. we could figure out how to integrate them. I would like to help your process.

I found another problem needed to discuss:
if timewheel deliveries the delay messages a little later than excepted, assuming now is 9:00 but the timewheel is deleverying the message at 8:30, meanwhile, the system begins to remove the commitlog, the message between 8:30 and 9:00 in the commitlog(going to be removed soon) might be lost forever.
Sometimes it is useless to deliver the delay message much later than excepted, maybe we need to rebalance how late the message we can remove directly.

We can separate the commitlog of delayMsg from the normal messages commitlog in the next version. we can work together.

Looking forward to working together.
In our internal test cases, if there are a large number of delay messages located in one second, it will cause io utils much higher than usual and take a long time to finish deliver these messages. We'd better suggest max delay messages per second and monitor them in backgroud manage system.

I found another problem needed to discuss:
if timewheel deliveries the delay messages a little later than excepted, assuming now is 9:00 but the timewheel is deleverying the message at 8:30, meanwhile, the system begins to remove the commitlog, the message between 8:30 and 9:00 in the commitlog(going to be removed soon) might be lost forever.
Sometimes it is useless to deliver the delay message much later than excepted, maybe we need to rebalance how late the message we can remove directly.

We can separate the commitlog of delayMsg from the normal messages commitlog in the next version. we can work together.

Looking forward to working together.
In our internal test cases, if there are a large number of delay messages located in one second, it will cause io utils much higher than usual and take a long time to finish deliver these messages. We'd better suggest max delay messages per second and monitor them in backgroud manage system.

Good suggestion. Setting the max number of delay messages per second ensures that the broker can provide normal messaging services. Also, the user and topic should be considered to ensure fair delivery.

https://github.com/airbnb/dynein, These guys have open-source its delay service on top of the SQS. That is the real pattern I've always think about. Messaging is only used to improve the scalability of queues, scheduling, and concrete workers as an external component. I'd like to see what you're thinking about. There are many restrictions on the current implementation,

Any process？

We can use RocksDB to save delayed messages.

@cserwen we have done this in https://github.com/didi/DDMQ/tree/master/carrera-chronos.
One of the problems in this way is that Rocksdb needs heavy maintenance when instance get large. Compaction will consume quite a mount of IO and interfere with message writing. So we have to make it an external service, and causing more maintenance work.

I found another problem needed to discuss:
if timewheel deliveries the delay messages a little later than excepted, assuming now is 9:00 but the timewheel is deleverying the message at 8:30, meanwhile, the system begins to remove the commitlog, the message between 8:30 and 9:00 in the commitlog(going to be removed soon) might be lost forever.
Sometimes it is useless to deliver the delay message much later than excepted, maybe we need to rebalance how late the message we can remove directly.

We can separate the commitlog of delayMsg from the normal messages commitlog in the next version. we can work together.

Is the separate storage of delayed messages and normal messages realized now?

I found another problem needed to discuss:
if timewheel deliveries the delay messages a little later than excepted, assuming now is 9:00 but the timewheel is deleverying the message at 8:30, meanwhile, the system begins to remove the commitlog, the message between 8:30 and 9:00 in the commitlog(going to be removed soon) might be lost forever.
Sometimes it is useless to deliver the delay message much later than excepted, maybe we need to rebalance how late the message we can remove directly.

We can separate the commitlog of delayMsg from the normal messages commitlog in the next version. we can work together.

Is the separate storage of delayed messages and normal messages realized now?

A new architectural implementation (still based on time wheels) will be released in the future, making timing delay message configuration more flexible, more efficient to send and receive, and less impact on “normal messages”.

If 2 different schedule-times have the same hash value, there may be a problem in org.apache.rocketmq.store.index.DelayMsgIndexFile#selectPhyOffset method

It will be better to partition DelayMsgIndex files by time range


Do I need to be on a different branch?

I'm working locally on my main branch, tracking origin/main. I do trunk-based development, so rarely create topic branches.
My local branch is three commits ahead of the remote branch, but I get this error when running git instafix:

Error: selecting commit to amend: No commits between main (cfc2a5d253) and cfc2a5d253599bf6b36e636bc6fa918ca67cd4ab

Does git-instafix assume I'm working on a different branch and merging into something like main or master?
I expected it to allow me to select from my local commits that weren't yet pushed to my remote, and run a fixup on those.

ah, I always work on branches so I made that the most convenient.
You can get the list of changes between you and origin/main temporarily with -u origin/main or more permanently with git config instafix.default-upstream-branch origin/main

You can get the list of changes between you and origin/main temporarily with -u origin/main or more permanently with git config instafix.default-upstream-branch origin/main

Thanks. I'll give it a try.

You probably ran into Error: creating merge base: cannot locate local branch 'origin/main'; class=Reference (4); code=NotFound (-3)
I just released 0.2.6 which should fix that problem and give a better error message for main-only workflows.

Thanks, @quodlibetor! I've just updated to 0.2.7, so I'll try it out and report any further issues.


Incompatibility with StimulusReflex >3.4

We recently updated to StimulusReflex 3.5.0.pre9, which introduced changes to the process of verifying identical client/server version numbers.
The version number is now verified when the channel receives data, so it required to be part of the reflex data.
I'm not intimately familiar with SR or this library, but I can try and get a PR together that would address this.

Thanks for pointing out this issue!

I'm not intimately familiar with SR or this library, but I can try and get a PR together that would address this.

That would wonderful. I'm glad to provide any help I can along the way.

That would be wonderful. I'm glad to provide any help I can along the way.

Great! I'll see what I can do.
One idea that I had, which might be terrible, was to just simply update build_reflex to add the version of SR to the data it uses to instantiate the reflex that's being tested. Since SR now just adds the version data as part of the ReflexData class on the client.
    def build_reflex(opts = {})
      channel = opts.fetch(:channel, TestChannel.new(opts.fetch(:connection, {})))
      element = opts.fetch(:element, StimulusReflex::Element.new)
+     version = StimulusReflex::VERSION

      self.class.reflex_class.new(
-       channel, element: element, url: opts.fetch(:url, ""), method_name: method_name_from_opts(opts), params: opts.fetch(:params, {})
+       channel, element: element, url: opts.fetch(:url, ""), method_name: method_name_from_opts(opts), params: opts.fetch(:params, {}), version: version
      )
    end

The obvious issue there is that it just assumes that the version of the NPM package and the gem would be in sync. Since this library I think is more focused on just testing the expected outcome of a reflex vs. actually triggering one from SR, that seemed like an okay assumption.
What do you think?

I think that would work! 👍

In case that helps others, we worked around this issue by disabling this check in test mode (available since version 3.4.0 of SR):
StimulusReflex.configure do |config|
  # Enable/disable exiting / warning when the sanity checks fail options:
  # `:exit` or `:warn` or `:ignore`
  config.on_failed_sanity_checks = Rails.env.test? ? :ignore : :warn

 # ...
end


Word Separators no longer work with Powershell

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

VS Code Version:

Version: 1.57.0 (system setup)
Commit: b4c1bd0a9b03c749ea011b06c6d2676c8091a70c
Date: 2021-06-09T17:18:42.354Z
Electron: 12.0.9
Chrome: 89.0.4389.128
Node.js: 14.16.0
V8: <IP_ADDRESS>-electron.0
OS: Windows_NT x64 10.0.19042

OS Version:
Version: 1.57.0 (system setup)
Commit: b4c1bd0a9b03c749ea011b06c6d2676c8091a70c
Date: 2021-06-09T17:18:42.354Z
Electron: 12.0.9
Chrome: 89.0.4389.128
Node.js: 14.16.0
V8: <IP_ADDRESS>-electron.0
OS: Windows_NT x64 10.0.19042

Steps to Reproduce:

Set Word Separators to `~!@#%^&*()=+[{]}|;",.<>/?'
The separator above removes the $ sign and the : colon
Open a powershell script
Type $global:somevar = 'abc'
Double click on $global:somevar

Normal behavior should highlight the entire $global:somevar string so a person can copy easily.
The bug arrived sometime on or after 1.56 and the double click will only highlight the $global.

It would appear that the Powershell extension is the culprit.  If I disable it, the problem goes away.  If I reload and enable, problem comes back.
I am running this version of the Powershell extension:
PowerShell
ms-vscode.powershell
Microsoft
4,069,920
Repository
License
v2021.5.1

@JoeBrunsTR It looks like the PowerShell extension defines language specific default settings here. Language specific default settings are "stronger" than regular user settings so to effectively define a "stronger" setting you need to also write a language specific setting. e.g. in your settings.json
"[powershell]": {
  "editor.wordSeparators": "`~!@#%^&*()=+[{]}|;",.<>/?'"
}

@sandy081 This issue is about UX confusion that stems from language specific default settings being "stronger" than regular user settings, it is not a problem with the editor. I believe we should improve our settings UX, like with a hover at the right place warning that "This setting will not apply to [powershell]", etc.

Prior to 1.56, I never had any issues.

@JoeBrunsTR You're right. But this is something the PowerShell extension defines, so this doesn't have anything to do with the VS Code version. If the PowerShell extension released an update at the same time as the VS Code update, then that was a coincidence. This was added by the PowerShell extension very recently -- https://github.com/PowerShell/vscode-powershell/commit/c6085977431878118c5dc28a5e51e05c8947be0f
Again, you can override what they are defining using the following in your settings.json:
"[powershell]": {
  "editor.wordSeparators": "`~!@#%^&*()=+[{]}|;",.<>/?'"
}

Is there a quick way to get to that setting using preferences?

@JoeBrunsTR F1 > Preferences: Open Settings (JSON) and then you can paste the snippet I've shown earlier in the other settings. e.g.
{
  // ... other settings
  "[powershell]": {
    "editor.wordSeparators": "`~!@#%^&*()=+[{]}|;",.<>/?'"
  }
  // ... other settings
}

Thanks for that.  Will someone be contacting the authors of the Powershell extension or do I have to start a thread someplace else?

Unfortunately, the editor in vscode does not like the data.
"[powershell]": {
"editor.defaultFormatter": "ms-vscode.powershell",
"editor.wordSeparators": "`~!@#%^&*()=+[{]}|;",.<>/?'"
},
Starting with the dot after the comma, it is being flagged red.

The string is not properly escaped, there is a " after the semicolon that is closing the string and all characters after that are not properly enclosed.
Escaping the double-quote after the semicolon removes the problem:
"editor.wordSeparators": "`~!@#%^&*()=+[{]}|;\",.<>/?'"

You can escape the " with a backslash so it doesn't end the JSON string

That worked great.  Is there anything we need to ask of the Powershell extension developers?

I think the only issue here is just that this is unfortunately not obvious in the settings editor GUI. Have https://github.com/microsoft/vscode/issues/58995 for that.


Chat automentions users when you type their username

https://user-images.githubusercontent.com/57961822/116165421-22c16080-a6fc-11eb-80ad-79640421f0b0.mov

#2373 Patched it and waiting for approval


Guard page stack issue

Sometimes, my game just crashes mentioning something about an error in a guard page or a stack. I don't really know what this means. Any ideas?

See my comment on #10.

It seems like I can't even load my game before it gives me that error now.
I don't know if has anything to do with my code, but it worked perfectly fine two minutes ago.

You should try and reinstall the .NET framework.

How can I do that as quickly as possible?

I tried reinstalling it, but it still gives me the same error.

Update:
Apparently, it has something to do with my mod, but it just suddenly started doing this.
I didn't add anything that could have caused this. No crash occurs without my mod.

Do you use the "Script.Wait" function?

No, I do not.

All I added was an array of Action<object[]>.
Could that be the cause?

How big is that array?

It's limited to two actions.

I can't help much without source code ...

https://github.com/Nacorpio/GTA-Purge-Mod

    *private int Accuracy {
        get {
            return (IsActive ? Ped.Accuracy : Accuracy);
        }
        set {
            if (IsActive) {
                Ped.Accuracy = value;
            } else {
                Accuracy = value;
            }
        }
    }

    public int Armor {
        get {
            return (IsActive ? Ped.Health : Armor);
        }
        set {
            if (IsActive) {
                Ped.Armor = value;
            } else {
                Armor = value;
            }
        }
    }

    public int Money {
        get {
            return (IsActive ? Ped.Money : Money);
        }
        set {
            if (IsActive) {
                Ped.Money = value;
            } else {
                Money = value;
            }
        }
    }

    public float Heading {
        get {
            return (IsActive ? Ped.Heading : Heading);
        }
        set {
            if (IsActive) {
                Ped.Heading = value;
            } else {
                Heading = value;
            }
        }
    }

    public int Health {
        get {
            return (IsActive ? Ped.Health : Health);
        }
        set {
            if (IsActive) {
                Ped.Health = value;
            } else {
                Health = value;
            }
        }
    }*

Apparently, when those were removed, the error vanishes.
What is wrong here?

I know what was wrong - my property was recursive. That way, I caused an overflow in a stack. Thank you anyways.

Ah, well, that makes sense. =)


Don't embed current thread count into parallel=True functions so that they can be cacheable.

Resolves #7518
Move the printing of the parfor schedule into the C code in debug mode.
Use the dynamic thread count when constructing the schedule so that the parallel=True function can be correctly cacheable.

@sklam @stuartarchibald This PR at this point should work for parallel=True functions that don't contain reductions.  There are several possible strategies to resolve this issue for when the functions do contain reductions and I'd like to discuss the possibilities with you before I do any implementation.

/AzurePipelines run


fix: remove solution code from using-switchmap-operator exercise

@Mishrakk thanks for submitting this. However it still included some more things.
Closing in favor of #31


Changed the footer text from "Lorem ipsum ..." to appropriate text.

Closes #196
Changes proposed
I changed the text of the footer section from "lorem Ipsum..." to appropriate text.
Screenshots

Looks good, thank you for your contribution.


Sync eng/common directory with azure-sdk-tools for PR 8475

Sync eng/common directory with azure-sdk-tools for PR https://github.com/Azure/azure-sdk-tools/pull/8475  See eng/common workflow

API change check
API changes are not detected in this pull request.


chore(deps-dev): bump all dev dependencies

Signed-off-by: Julien Bouyoud<EMAIL_ADDRESS>

:rocket: Release indicator
Recommended bump for this PR : NO release

:tada: This PR is included in version 1.3.0 :tada:
The release is available on:

v1.3.0
GitHub release

Your semantic-release bot :package::rocket:


Fix for AKV signing and update docs

The PR fixes the submission of proposals signed with an AKV member key. We were missing the voting on proposals.
Small edits to docs.

Testing:
https://github.com/microsoft/privacy-sandbox-dev/actions/runs/11256127843

How can KMS members vote to a proposal that were created by another member? Is it future work or already covered by the current code?


Front-End : CSS Layouts

The Documentation contains the brief into of CSS Layouts: Displays, Floats, Positions, FlexBox, CSS Grid.
I want to work on this issue.
Please assign this to me.

I want to make audio content on this, May I ?
Lavleen Agrawal (Batch 18 - Frontend)

i would like to work on this via audio or video. please assign this to me.
Fronted Batch 9

Hi sir! I would love to contribute on this topic, can you please assign it to me?

Debarati Ghatak
Frontend Batch 5

I would like to contribute to this topic via documentation.
fronted batch 5
preeti yadav

/assign


Map not loading

On mac, once all details have been entered and it tries to load the map, it gets stuck on 'loading, please wait...' .

@RJZ-20 please follow #545


Getting ping value from rtmpConnection

Hi, I was just wondering if there was a way of getting the ping value from a connected stream?
We are building a solution where we have a number of different RTMP ingest servers, and we would like to test connectivity to them by measuring latency which should help select the best server.
If there isn't a way to get the ping value from a connected stream, what would be the best class to look through to start implementing this feature?

If there isn't a way to get the ping value from a connected stream

framework has no feature. Please look this this "RTMPUserControlMessage" class.
https://github.com/shogo4405/lf.swift/blob/master/Sources/RTMP/RTMPMessage.swift#L704
The RTMP client can't send a ping(0x06) message. see also "RTMP Specification 1.0" P27. http://www.adobe.com/content/dam/Adobe/en/devnet/rtmp/pdf/rtmp_specification_1.0.pdf

thanks for getting back to me, yeah I think this will do. We can just listen to the PONG messages coming from each of the servers when we run the rtmp in test mode (our internal query param in the rtmp string) and check the time difference from the time received as a timestamp from the ping


Price per block could increase

Here:
https://github.com/edgeandnode/subscription-payments-contract/blob/7b0368e4da25ece37440e0999fbeee652ad8b103/contracts/Subscriptions.sol#L90
there is no "defense" to the consumer for the price per block to increase suddenly. This could be used by a malicious entity to drain funds

My understanding is that transferFrom requires the sender to first approve the transfer of up to some amount of tokens. The expectation is that the subscriber would only approve the expected amount so an unexpected increase would result in the transaction being reverted.

True, but a frequent pattern is to approve an unlimited amount if they expect to repeatedly interact with the contract. Something we should run by experts when the time comes.


Command permission fixes

Required for all non-trivial PRs

[x] Rebased/mergable
[x] Tests pass
[ ] CHANGELOG.md updated
[x] Sign CLA (if not already signed)

I left CHANGELOG.md unmodified as it is unclear to which target version this should go.
It is unclear whether retention policy management is only intended to be available to admin users. This PR allows creating RPs with just write privileges. If the idea is to allow RP management to admins, then the necessary fix would be also restricting the "DROP RETENTION POLICY" command to admins only.
The docs.influxdata.com documentation should also the updated as it states things like "Only admin users are allowed to work with continuous queries.".

@dgnorton @pauldix Create/drop RP should require admin and not just write?

I think create/drop RP and drop measurement should require admin.

Currently it is not possible to create a user that would be able to fully manage the contents of a database. Instead, a mixture of admin and non-admin privileges are required to manipulate RPs, CQs and the measurement/series objects. This does not work well in systems with multiple users, each having their own DBs.
API symmetry should be maintained, e.g. if a user is able to create an object, then he should also be able to delete it.
The whole "admin" superuser concept that allows bypassing all privilege checks seems unnecessary to me, but changing that would require a bigger overhaul. Permissions could be given to run specific commands instead of grouping them to READ, WRITE and admin-only categories.
CQs can be used to DoS the InfluxDB server. Perhaps this is the reason why they are described as admin-only in the documentation? (However, the actual implementation differs from that)
Subscriptions are admin-only and certainly should be such in their current form as they can be used to spray a stream of packets to any ol' network address.

Any ideas how these issues will be addressed in the upcoming 1.0 release?

1.0 has been put into a freeze and we were mostly not accepting any substantial new code for at least a month now. Sorry that it's been awhile since we gave you a response, but we have been very busy trying to get bugfixes done for the 1.0 release.
If I understand you, your underlying problem is that you can't create users who are able to do everything on a specific database. I don't think allowing people with WRITE access to delete anything is necessarily desirable though. It seems to me like you would want to have a third permission that would give permission to delete things. An admin may want to give users, like a daemon, access to write, but not give it permission to delete something as part of the principle of least privilege. From what I interpret, it seems like maybe you want to be able to grant admin to a specific user for a specific database? That way you can grant admin to one user when you create the database and they can then manage the database themselves.
Am I correct in my understanding? If so, I think it might be best for us to close this PR and to create a feature request so that we can have more discussion about what is desired.
Thanks!

@jsternberg Let's just forget for a moment what I blabbered about earlier and focus on the three oneliner patches I provided. Here's a recap:

Bug: Creating a CQ currently only requires the READ privilege, it obviously should require (at least) the WRITE privilege. This is basically a vulnerability. (fixed by b1c0719)
Inconsistent behavior: DROP MEASUREMENT required ADMIN privileges, even though exactly the same can be achieved b "DROP SERIES FROM x", which only requires WRITE privilege. This I would call an annoyance with an existing workaround. (fixed by c11fe73)
Bug: retention policies can be dropped with just the WRITE privilege but creating them requires the ADMIN privilege. Possible fixes: either make also drop require admin OR allow users with WRITE privileges to create retention policies (54cd226)

Interesting that already at least three people from InfluxData have seemed to have reviewed this PR, but none of them have spotted the basic security issue that any read-only user can CREATE a CQ.

I think if we separate the CQ part of the code into a separate PR we could accept this as-is. I agree that creating a CQ isn't appropriate for a read-only user. We might want to target this permission change to the 1.0 branch too.
/cc @jwilder for the call on if the CQ stuff should be merged to the 1.0 branch for 1.0.1.


Proposal: Add animation when Treeview node expands and collapses

Summary
Almost all the UWP UIs have animations built in, except for treeview. It's very unpleasant to see Treeview nodes expanded/collapsed immediately.

@Chigy - once we have the link to the motion comps, we can get going on this one. I'm tagging it for WinUI vNext consideration
@MuziburRahman  - Thanks for filing this 'Issue'! It certainly will help refine the TreeView User experience. We will get working on this once we get done with the current roadmap of investments for WinUI 3.0. Please do review this doc and provude us with your feedback.  : https://github.com/microsoft/microsoft-ui-xaml/issues/717

I hope it's faster than what the start menu and flyout animations use. Those feel very slow and make various other apps feel slow.

Removing myself as there's no immediate plan for tackling this item.


Can I use it with js-ipfs-api

Hello,
I'm looking to create a key-value store using IPFS. I was told that Y.js could be used for this. I'm using the go-ipfs implementation with the js-ipfs-api in node.js. I tried adapting this example to get the connector working with the js-ipfs-api, but without success. Can they work together or does the connector only work with js-ipfs?
Thanks! :)

Y-ipfs-connector only works with js-ipfs because it needs to establish direct p2p connections with a custom protocol and go-ipfs does not support that.
On 25 Nov 2017, 20:06 +0000, João Santos<EMAIL_ADDRESS>wrote:

Hello,
I'm looking to create a key-value store using IPFS. I was told that Y.js could be used for this. I'm using the go-ipfs implementation with the js-ipfs-api in node.js. I tried adapting this example to get the connector working with the js-ipfs-api, but without success. Can they work together or does the connector only work with js-ipfs?
Thanks! :)
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

Ok, thank you for the clarification. I'll have to look for an alternative then. 🙂


react-router-redux 转到 connected-react-router

Upgraded react-redux and redux-saga then reported an error

Upgraded react-redux and redux-saga then reported an error


Another wrong german translation in the "report issue" dialog

Issue Type: Bug

Open "report issue" dialog
See this.

The highlighted link is labeled with an entire sentence which makes sense on its own, but not in the spot where it currently is. The link should probably read something along the lines of
"Versuchen Sie, das Problem nach erneutem Laden des Fensters mit deaktivierten Erweiterungen zu reproduzieren"
VS Code version: Code 1.25.1 (1dfc5e557209371715f655691b1235b6b26a06be, 2018-07-11T15:43:53.668Z)
OS version: Windows_NT x64 10.0.17134

System Info

Item
Value

CPUs
Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz (4 x 3403)

GPU Status
2d_canvas: enabledflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onnative_gpu_memory_buffers: disabled_softwarerasterization: disabled_softwarevideo_decode: enabledvideo_encode: enabledvpx_decode: enabledwebgl: enabledwebgl2: enabled

Memory (System)
15.96GB (7.56GB free)

Process Argv
C:\Program Files\Microsoft VS Code\Code.exe

Screen Reader
no

VM
0%

Extensions (13)

Extension
Author (truncated)
Version

vscode-eslint
dba
1.4.12

gitlens
eam
8.5.2

tslint
eg2
1.0.34

RunOnSave
eme
0.0.16

vscode-language-pack-de
MS-
1.25.2

vscode-docker
Pet
0.0.27

project-snippets
reb
0.5.0

java
red
0.28.0

vscode-coverage-gutters
rya
2.0.1

vscode-java-debug
vsc
0.10.0

vscode-java-pack
vsc
0.3.0

vscode-java-test
vsc
0.7.1

vscode-maven
vsc
0.9.2

@AlCalzone, thank you very much for your feedback!
Translation is opened to community in Transifex. It will be great if you can help to fix there.
See https://aka.ms/vscodeloc for localization project background. Sign up Transifex free.
Here is the string: https://www.transifex.com/microsoft-oss/vscode-workbench/translate/#de/$/132525384?q=text%3A'disabling+all+extensions+and+reloading+the+window'

Thank you @AlCalzone for your help! The translation you suggested is being used now. It will be reflected in German language pack v1.26.


Provide a way to customize the python used for the nixos test-driver.

Describe the bug
I'm developing service that is built on top of NixOS, and am writing tests for our nixos configuration using testing-python.nix. I'd like to be able add python packages (both local and public), that I can use both from the test script, and from the REPL.

This issue has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/improvements-to-the-python-test-runner/15178/4