Investigate ttrt perf build tracy flags

Reported by Kyle. With this docker image
--docker-image ghcr.io/tenstorrent/tt-mlir/tt-mlir-ird-ubuntu-22-04:latest
perf mode fails. CI and local testing passes.

tldr: perf build works on-top of tip on a fresh build and using IRD image
okay so there’s a mixed use of this flag in metal
When building metal, you need to provide ENABLE_TRACY. This will set TRACY_ENABLE in third_party/tt-metal/src/tt-metal/CMakeLists.txt  which builds all the tracy modules. (previously. this was an env flag which got converted into a compile flag, hence the change in my commit at: 298afb510
Perf build succeeds with this IRD docker image --docker-image ghcr.io/tenstorrent/tt-mlir/tt-mlir-ird-ubuntu-22-04:latest .
Commit = mlir latest.
No issues, user had to clean tt-metal-build folder and everything else built as expected.


Operate in a common monad encapsulating the behaviour of the optimizer

This will probably make things a lot easier in the long run.

I'm not a fan of this rewrite. Part of my goal in this initial implementation was to preserve the explicit continuation construction; the 'direct-style' rewrite, while useful, doesn't reflect what's in the paper nearly as well.

If that is the design goal, then I would contend that the existence of ContT is just obfuscation. Currently, ContT is really just being used to avoid an extra κ parameter on a few functions. Anecdotally, I found the ping-ponging between State Store and ContT (State Store) rather confusing. I agree that this change removes the explicit construction of continuations, but that is really what ContT is for.
Both approaches are probably just massive over-engineering anyway. The paper never uses the continuation to accomplish non-local control flow (as far as I can tell), and a real implementation would just invoke call/cc. Perhaps my complaint is more with the presentation in the paper; this version does not correspond as well with the paper, but is (in my opinion) clearer. Continuations, are an implementation detail rather than a relevant part of the algorithm.

That's just my 5¢. Ignore me if this is not what you're going for.


chore: do not add label backport-requested to PRs created by renovate

Previously the goal was to backport everything, and this works perfectly, but with renovate we create the PRs with the label do not backport which it's added because those PR will be replicated one per each release branch.
This is the further fix to avoid adding the backport-requested label when the PR is created by renovate

We add a the "do not backport" label to all renovate's by default, I'm not sure why this check is needed 🤔

Sometimes, the backport workflow run faster than the renovate add labels action, so do not backport added after backport-requested label :)

@sxd @phisco
The reason why it not works every time is due to the checking for do not backport label is added in the job level, between job is schedule and steps run, there is time gap. I add redundant check in the label step level, and also, In the final step, add the step to remove the redundant labels if have.


timestamp parameters added (&_=) to JSON get data urls

timestamp parameters are added to JSON get data urls...

wil lead to getLocalValues.php?category=10&_=12345 (timestamp) urls being called and hence not cached through the CDN.

$('#test').editable({
source: "/api/getLocalValues.php?category=13",
sourceCache: true,
                    sourceOptions: {
                        cache: true
                    },

                display: function(value, response) {
                   $(this).text(value);
                 }
                });

This solved it


mat: update docs for SVD.SolveTo and SVD.SolveVecTo

This updates the documentation as promised in #1316.
Please take a look.

PTAL


[Bug Report] Press enter in a form with only one input field will trigger browser redirect

Element UI version
1.4.4
OS/Browsers version
Chrome/60.0.3112.113
Vue version
2.4.3
Reproduction Link
https://jsfiddle.net/mm99jvfg/
Steps to reproduce
focus on input field then press ENTER key
What is Expected?
no action or at least submit form without redirect
What is actually happening?
browser navigate to http:///?#/

That is because the underlying form element is submitted. You can catch that using @submit.native.stop.prevent and a custom submit handler.
https://jsfiddle.net/vhgda6md/


[GLUTEN-3143][CH] Transform arrayJoin function to array join step to apply max_block_size

What changes were proposed in this pull request?
Notice that arrayJoin function and array join step are executing in different places. The former is in ExpressionActions::execute,  and latter is in ArrayJoinAction::execute. max_block_size is currently only valid in array join step, so we must transform arrayJoin function to array join step to apply max_block_size.
Notice: This pr relies on https://github.com/ClickHouse/ClickHouse/pull/54664
(Fixes: #3143)

@liuneng1994 @baibaichen There has been serveral uts about lateral view explode/posexplode, so this pr didn't add new uts.

===== Performance report for TPCH SF2000 with Velox backend, for reference only ====

query
log/native_master_09_20_2023_time.csv
log/native_master_09_19_2023_7d9763c31_time.csv
difference
percentage

q1
43.74
42.27
-1.474
96.63%

q2
24.76
24.49
-0.269
98.91%

q3
36.95
37.17
0.222
100.60%

q4
41.94
41.53
-0.408
99.03%

q5
70.07
70.33
0.256
100.37%

q6
6.73
5.01
-1.722
74.43%

q7
87.08
82.44
-4.643
94.67%

q8
79.39
79.40
0.006
100.01%

q9
116.92
116.28
-0.637
99.46%

q10
46.95
47.47
0.517
101.10%

q11
19.26
18.94
-0.316
98.36%

q12
26.14
23.67
-2.465
90.57%

q13
49.26
49.99
0.726
101.47%

q14
14.99
18.57
3.585
123.91%

q15
29.01
30.46
1.448
104.99%

q16
15.98
16.01
0.026
100.16%

q17
120.85
124.64
3.790
103.14%

q18
162.91
160.41
-2.494
98.47%

q19
13.36
11.89
-1.471
88.99%

q20
31.10
23.90
-7.200
76.85%

q21
244.65
234.75
-9.898
95.95%

q22
15.41
15.10
-0.314
97.96%

total
1297.44
1274.71
-22.736
98.25%


Fix unused pipeline state caches

Fixes https://github.com/ppy/veldrid/issues/48

I'm not sure how to test whether this actually improves anything, but I have tested that it runs at least.


Run custom clean even if cancelled

Change-type: patch

@klutchell any objections to run custom clean if the workflow is cancelled? The issue with cancelling the entire workflow run due to concurrency setting means that currently none of the cleanup steps in the actual custom actions are executed, leaving behind EC2 instances, etc.

@ab77 Currently custom clean actions are used to remove GH pages preview branches for some repos. But I guess a cancelled run due to concurrency will also have a new run re-create the branch?
We might want to consider a new action for cancelled runs, to keep it separate from closed PRs?
Maybe we need to rename them to opened/merged/cancelled/closed to be more obvious?

Maybe we need to rename them to opened/merged/cancelled/closed to be more obvious?

@klutchell yeah, or maybe we leave the cleanup as is, and add an always action, which would be run based on if: always() test?

Yeah, like some kind of always post run step is something I've been looking
for but never quite got the criteria or use case right. It sounds like this
is a good case.
On Mon, Oct 10, 2022, 1:28 p.m. Anton Belodedenko @.***>
wrote:

Maybe we need to rename them to opened/merged/cancelled/closed to be more
obvious?
@klutchell https://github.com/klutchell yeah, or maybe we leave the
cleanup as is, and add an always action, which would be run based on if:
always() test?
—
Reply to this email directly, view it on GitHub
https://github.com/product-os/flowzone/pull/254#issuecomment-1273622772,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AE4CWIGVNTO5NHOU5JQ4F23WCRG4XANCNFSM6AAAAAARBQOYBM
.
You are receiving this because you were mentioned.Message ID:
@.***>


fix: camera mgmt docker build, secret names, and go mods

Fixed the docker build for Camera Management App and make it work with docker compose.
Fixed the naming inconsistencies with secrets in the yaml file and code. Now also matches rtspauth from the device-usb-camera service.
Removed errors package from go.mod, to use EdgeX errors package, to match the device services.

If your build fails  due to your commit message not passing the build checks, please review the guidelines here: https://github.com/edgexfoundry/edgex-examples/blob/main/.github/Contributing.md
PR Checklist
Please check if your PR fulfills the following requirements:

[N/A] I have added unit tests for the new feature or bug fix (if not, why?)
[X] I have fully tested (add details below) this the new feature or bug fix (if not, why?)

Testing Instructions

Valediction looks good in non-secure mode. Tested with ONVIF and USB cameras.
Default pipelines starts automatially, manual start/stop of pipeline works, streaming of events works for both ONVIF and USB cameras. On ONVIF also verified PTZ operations. It works correctly


bugfix: mdivide_left_tri_test random failures

Summary
Kernels now also wait on write events of their out_buffer arguments. This fixes the undeterministic bug that caused stan-math\test\unit\math\rev\mat\mdivide_left_tri_test.cpp to randomly fail.
Also the unnecessary call to .zeros() in tri_inverse() is removed. That was overwritten by next call to batch_identity anyway and caused the bug when those two kernels were executed in wrong order.
Tests
Added tests for checking that multiple asynchronous kernel invocations are executed in correct order.
Side Effects
None.
Checklist

[x] Math issue #1408

[x] Copyright holder: Tadej Ciglarič
The copyright holder is typically you or your assignee, such as a university or company. By submitting this pull request, the copyright holder is agreeing to the license the submitted work under the following licenses:
- Code: BSD 3-clause (https://opensource.org/licenses/BSD-3-Clause)
- Documentation: CC-BY 4.0 (https://creativecommons.org/licenses/by/4.0/)

[x] the basic tests are passing

unit tests pass (to run, use: ./runTests.py test/unit)
header checks pass, (make test-headers)
docs build, (make doxygen)
code passes the built in C++ standards checks (make cpplint)

[x] the code is written in idiomatic C++ and changes are documented in the doxygen

[x] the new changes are tested

I just want to drop in and say kudos to all 3 of you (@rok-cesnovar @SteveBronder @t4c1) for digging in, finding, and fixing such a difficult bug. This is in that class of concurrency bugs that are super hard to reproduce and get to the bottom of, and the three of you worked really well together to narrow it down and tee up Tadej for his critical insight that led him to this superficially simple-looking one-line bugfix (with test!). I am not fooled; I know how hard these are. Thanks everyone :)

All of the cred goes to Rok and Tadej for this one!

Actually all credit goes to Tadej, he squashed this one.


Prevent node-pre-gyp from messing with our UI.

Coverage decreased (-0.02%) to 79.615% when pulling 1daab0adb56031535e4fce035a352d0e1f6db1c4 on block-node-pre-gyp into aab7519d5acdba3f41abfee964215753f40b8c11 on master.


Update App & Reg Details pages

Issue:

bcgov/entity/issues/24504

Description of changes:

For Examiners: Update Application & Registration Details pages to include add details for Primary and Secondary Contacts
Update tests
Tech debt cleanup

Before

After

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of the namex license (Apache 2.0).

/gcbrun

Temporary Url for review: https://strr-ui-dev--pr-330-atq6r9l7.web.app


Add more supported metadata types

See here for current list of supported types.

Need help from an experienced SFDC dev here.

EmailTemplate type (email folder) do I also have to include the -meta.xml file in the root of the email folder (in addition of the email/<member name> folder)?

Document (documents folder) you can specify folders AND objects as <members>?  Can the zip file just include the documents/<members name> folder? Ex:
<name>Document</name>
<members>SharedDocuments</members>
<members>SharedDocuments/user.jpg</members>


Proposal: No more issues on GitHub

CC: @teor2345 @juga0
I propose this to be the last issue created in this repository.

All future issues will be created on trac with the "Core Tor/sbws" component.
All PRs/code review will continue to happy here at pastly/simple-bw-scanner (at some point we may want to switch to torproject/simple-bw-scanner, but at this time let's keep things simple and stay here)
All existing issues will continue to exist until the are closed, migrated ad hoc, or sufficiently few of them remain such that it isn't painful to migrate them all to trac.

If this sounds fine, I'll rename this issue accordingly.

I propose this to be the last issue created in this repository.

Works for me.

I propose this to be the last issue created in this repository.

fine for me too


feat: added new update system

Discussion: https://github.com/orgs/ublue-os/discussions/187
Solves: https://github.com/ublue-os/config/issues/63
after quite a bit of troubleshooting/fixing i've finally gotten the ublue-updater to build, and made a basic draft pull request to add the new update system.
This is by no means meant to be merged right away, and will likely need more changes/review (particularly moving the repo into the uBlue org)
Currently in the PR:
remove the old update services and update services RPM
pull in new update system from https://github.com/gerblesh/ublue-updater

Update: basically everything works that needs to work as an MVP, updating, notification, logging failed updates, etc. It's already quite a bit more polished than the current update system we have in place. I'd say we just move the repo into the uBlue org and merge, that being said, I think it would be good to get some acknowledgement from image maintainers to make sure they are on board with this before merging

Closing this as it's out of scope for the uBlue main images and config, will make a PR in https://github.com/ublue-os/bling instead


Form component catching errors

Good evening! 😃🚀
It seems impossible for me to catch the error if I just submit a form without anything,
I just get an Uncaught (in promise) error: Form validation failed. 😖
The submit function has a try catch block inside..
Am I thinking completely wrong? is it supposed to work like this?
I have tried two of the examples the one with self validation and the other with a scheme from yup no matter which one I use I fail to catch the error.

<template>
  <UForm :schema="schema" :state="state" @submit="submit" class="space-y-2">
    <UFormGroup label="Email" name="email" required>
      <UInput
        v-model="state.email"
        placeholder="Email"
        icon="i-heroicons-envelope"
        size="xl"
        autocomplete="username"
      />
    </UFormGroup>

    <UFormGroup label="Password" name="password" required>
      <UInput
        v-model="state.password"
        placeholder="Password"
        icon="i-heroicons-lock-closed"
        type="password"
        size="xl"
        autocomplete="current-password"
      />
    </UFormGroup>

      <UButton
        type="submit"
        size="xl"
        class="flex item-center justify-center"
        :loading="loading"
      >
        Login
      </UButton>
      <UButton :to="{ path: 'password-request' }" variant="link" :padded="false"
        >Forgot your password?</UButton
      >

  </UForm>
</template>

Hi! The form component was recently refactored (https://github.com/nuxtlabs/ui/pull/487). Although the documentation has been updated, these changes have not yet been released.
In the meantime, you can use nuxthq/ui-edge to get the latest updates, or use the previous version like so:

<template>
  <UForm ref="form" :schema="schema" :state="state" @submit="submit" class="space-y-2">
    <UFormGroup label="Email" name="email" required>
      <UInput
        v-model="state.email"
        placeholder="Email"
        icon="i-heroicons-envelope"
        size="xl"
        autocomplete="username"
      />
    </UFormGroup>

    <UFormGroup label="Password" name="password" required>
      <UInput
        v-model="state.password"
        placeholder="Password"
        icon="i-heroicons-lock-closed"
        type="password"
        size="xl"
        autocomplete="current-password"
      />
    </UFormGroup>

      <UButton
        type="submit"
        size="xl"
        class="flex item-center justify-center"
        :loading="loading"
      >
        Login
      </UButton>
      <UButton :to="{ path: 'password-request' }" variant="link" :padded="false"
        >Forgot your password?</UButton
      >

  </UForm>
</template>

Also, your example won't work with the latest version, the validation error is raised before emitting the @submit event, so if validation fails the event is not fired.
If you want to handle validation errors, you have to use the validate function.

I suspected it was exactly as you explain.
I already use ui-edge, so the idea is that I should add my own validation in addition to yup schema to make it work? or should I skip the schema totally?
Would it not be possible to throw the error or expose it so i can catch it in the submit function?

I'm not sure I fully understand what you are trying to do, could you give me more details?

I have been having a similar problem to this.  The error is only thrown on submit.  It makes sense to throw the validation error on submit, but it might be useful to provide a mechanism to disable the submit button until validation passes so this error doesn't get thrown.
As a temporary workaround I've just been adding this to my components with forms:
onErrorCaptured(e => {
    return false
})

This allows your component to catch the error from within UIForm.

That sounds very promising @brycesteve! I'm going to do some tests tonight, it's exactly what you describe I'm looking for. 🥁😃

@danielohling Does using the latest ui-edge fixes your issue?

For me, the@nuxthq/ui@npm<EMAIL_ADDRESS>does not solve the issue.

@benjamincanac I just tried it, and I have chosen to run on the option that @brycesteve had.

I have the same issue, how should we handle errors on submit ? i get this when i try to submit with some stuff missing
[Vue warn]: Unhandled error during execution of native event handler
at <Form ref="form" schema=
and
Uncaught (in promise) Error: Form validation failed: [
{
"path": "user",
"message": "Required"
},
{
"path": "email",
"message": "Required"
},
{
"path": "msg",
"message": "Required"
}
]

FYI, We recently added a @error callback to handle errors and removed the validation error in https://github.com/nuxt/ui/pull/718 (+ fixed validate arguments @Ashrakk).
It's currently available on @nuxt/ui-edge: https://ui.nuxt.com/dev/forms/form#error-event


add column to beginning of datatable

I am trying to add an extra column to the beginning of the datatable via addColumn but no luck. Anyway if i add the column to the end of the datatable it works. Any help much appreciated.
datatable view
$('#dtGrid').DataTable({
     responsive: true,
     processing: true,
     serverSide: true,
     ajax: {
        url: 'chargeback/grid'
     },
     columns: [
                    { data: 'action', name: 'action' },
                    { data: 'col_1', name: 'col_1' },
                    { data: 'col_2', name: 'col_2' },
                    { data: 'col_3', name: 'col_3' }
                ],
     "sScrollX": '100%',
     "autoWidth": false
 });

Controller method
return Datatables::of($chargeback_logs)
                            ->addColumn('action', 'action here')
                            ->make(true);

Your code should work and add the action column at the beginning of dataTable. However, you need to set action as not orderable and searchable to disable those functionality.
{ data: 'action', name: 'action', orderable: false, searchable: false },
``

great once added
orderable: false, searchable: false

it worked. Thank you.


Support non-Windows/Linux/macOS operating systems

Currently the crate fails to compile for these.
I'd suggest to use the Linux conventions in this case, as these are common for other unix-like operating systems such as the BSDs (FreeBSD, NetBSD, DragonFlyBSD, OpenBSD).

Thanks, I think this makes sense.
I wonder whether it makes more sense to add BSDs to the target section, or just convert the Linux target into !win && !mac instead (not sure how things like Haiku and Redox identify themselves, but it would be nice to catch them, too).
Opinions?

Give it a try ;) I'm working on adding bat to the FreeBSD ports and dictionaries is one of the packages, which are incompatible. Maybe it's the only one.
I'm happy to do some testing but I'm not a Rust user myself, however, so I'll need some help/instructions from you.
Cheers ;)

BTW, do you plan to tag a release soon, which includes recent changes? That would make testing much easier. Thanks!

@0mp Oh, damn, I merged the changes,, but forgot to publish a new version.
Give me a few minutes, I'm on it right now.

CI is building 0.10.0 right now.

Windows is green, directories 0.10.0 is published.
Thanks for reminding me, @0mp!

Whoa, that was fast. Thank you!


MakeSelectable should be new-able or renamed

MakeSelectable has a name with a capital letter. Typically, functions with a capital letter should be called with new, so I expect to be able to call the function in that manner. But the function is defined as an arrow function, and arrow functions cannot be called with new.
Even if it makes no difference for a particular function to be called with or without new, our linters might warn us against calling capitalized functions without new. Some linters allow whitelisting "safe names," but it's nicer not to have to manage that.  Therefore, it's better for us to always have the option to call functions with new, even redundantly.
For the sake of backwards compatibility, it would probably be better to keep the capitalized name, and make the function new-able (i.e., create it with function, rather than () => {}). Otherwise, it should be renamed to makeSelectable, so we have a clearer expectation about its calling convention.

I'm not sure to understand what you proposed.
Regarding the name of this HOC. I completely agree. It would have been much better to call it makeSelectable. That's definitely where the community convention is, e.g. recompose. After all, it's a simple function.

I'm proposing that MakeSelectable should be new-able or renamed to makeSelectable.

I would vote for renamed :+1:.


Add support for ActiveJob.

This PR has some of the initial code to add support for Active Job subclasses regardless of the queue backend that is being used - Raven currently supports Sidekiq on it's own but would be nice to have a broader support for other backends like SuckerPunch (the one I'm using), Resque, DelayedJob, etc.
I couldn't find any tests for the Sidekiq support to use as a base, but I'm take this to a spin in our app to see how it goes. Also, I fear that loading both the ActiveJob support + Sidekiq might generate duplicate reports since both integrations would be executed together, but this is something that I need to test it out to be sure about it.

(thumbsup) We should probably only carry ActiveJob integration in the base gem, and spin out Sidekiq integration to a separate gem.

@nateberkopec one alternative that I can think of is make it disabled by default - the deprecation cycle/upgrade path could be simpler.

@nateberkopec sorry for the huge delay on this one. I've tested this branch against a fresh Rails app using Sidekiq and added a safeguard to the ActiveJob plugin to let the Sidekiq handle the exceptions instead of collecting the same error twice.

I've reverted this for now until we sort out #368.
It might be that as a quick workaround we remove the clause to prevent the duplicate and sort out those problems later.


Add volume mapping for node modules and source code for node services

Suggest adding source code volume mounts to aid in faster development iteration with docker-compose.
Currently, making a change in the code will not be reflected in the running container. Even on a container restart.
The issue is that there are COPY commands in the Dockerfile. This is the BUILD phase.
But the runtime phase simply runs the container from the already-built image.
Using the volume directive in your docker compose can aid in rapid iteration during development to avoid the BUILD step because the volume over-write is a RUNTIME directive.
You can see an example repo here
The important bits are this:
    volumes:
      - ./public-site:/usr/app
      - /usr/app/node_modules

I'm not familiar with this at all.  I like the sound of it and can't wait for you to teach me/us.

Not where this belongs, but oh well...
@all-contributors please add @parithon for code and infra

I'm going to include several changes with this, as well as resource links for why certain things are changing, and I'm happy to discord call and go over it.
I'm also making certain assumptions about your development style, and you most likely are going to want to pull this down and test it out.
My proposed changes:

[ ] Change the Dockerfile command to directly execute node against the dist file, instead of proxying to npm (there is a reason for this)
[ ] Add an "init" property to the docker-compose file to wrap the command in a thin init layer to handle signals even better than item above (there is a reason for this)
[ ] Use a non-root user for all containers (there is a reason for this)
[ ] Add volume mounts (this is the original heart of the issue, but other things are required to take advantage of this, mentioned in below items)
[ ] Add typescript watching, and node process re-starting, as additional npm script commands, and use the docker-compose file to execute this in dev, overriding the default build and start of the container command

I'll be monitoring this issue as I develop and am happy to discuss any concerns with the above-proposed changes.

Also, we should probably specify actual container names in the docker-compose (like we specify image names) for tracking down and interrogating particular containers.
I'll tack that on as well, no sweat.

Was this handled in the recent @parithon PR to allow debugging?

@MichaelJolley It was partially, I'll update this issue to reflect that looks like already complete!

@mtheoryx and @MichaelJolley, to better document why I added the other *.dockerfile's located in the services folder:
I noticed when I built the images for use with the docker-compose containers, the 'node_modules' folder does not include the devDependencies most likely because the Dockerfile installs with the --only=Production flag during the second phase of their build process.
I decided to simply create development Dockerfile's and placed them in the services folder emitting the second phase and mounting the entire service' folder in docker-compose so we can develop based on changes from the host.
My intent wasn't to remove or replace the production Dockerfile's located in each of the services root folders, nor any work that @mtheoryx produced, I simply didn't know a better way to accomplish the goal. I'm eager to learn a better way!
Happy coding everyone!


When generating a class with 'component' in the name (e.g. component base class), anything after the 'component' is ignored

ng generate class xxx.component.base produces a file called 'xxx.component', which clearly wasn't the intention.

@Brocco can you clarify if this is intentional or a bug?

Might be good to add an extra param to the generator command, not only for components but for services, classes an any other createable artefact, e.g. so you can specify the filename and the class name separately.

@Brocco ping ☝
#goodnessSquad

I'm sorry, but we can't reproduce the problem following the instructions you provided.
Remember that we have a large number of issues to resolve, and have only a limited amount of time to reproduce your issue.
Short, explicit instructions make it much more likely we'll be able to reproduce the problem so we can fix it.
If the problem persists, please open a new issue following our submission guidelines.
A good way to make a minimal repro is to create a new app via ng new repro-app and add the minimum possible code to show the problem. Then you can push this repository to github and link it here.


php version bump

I see you bumped the version to php 7 because of phpunit.  I quick tested and it looks like I can get phpunit 4.x running with 2 minor changes to the tests (which supports php 5.5).
Although, I still like the idea of supporting 7+ (or 5.6+) because of PHP security patching support, but I also think the version shouldn't be bumped just because of the testing framework.
PHP support: http://php.net/supported-versions.php
see https://github.com/KJLJon/lockbox/commit/d8be02677d6d763619a52aa00a9fa09edb9e3d53 for 5.5+ fix.
@starekrow what are your thoughts?  I can send a PR for the commit listed above if you still want to support php 5.5+

The bump to 7 was indeed supposed to be temporary, I only had a few minutes to get Travis up and running. However, that got me thinking that it’s been a few years since I did a proper survey of PHP versions in use at various levels/types of hosting. My sense is that 5.6 and even 5.5 are still seeing an amount of use in production, in which case we should definitely support them. I’d be interested in your thoughts as well, and I’ll take a look around the net tomorrow.

Without doing much research on market adoption of php versions.
I think 5.5+ is a good place to start.  If people start wanting to use this package with earlier versions (php5.3+) it could be addressed at that time (with some polyfills where needed).  It might even work already with php5.3 (I would need to look up all the php functions on php.net to see if any aren't supported).
I think it is more of a commitment question on how much work is needed to maintain the older versions vs market adoption.

ill submit a pr for php 5.5.  Feel free to merge, or ask me to update it to any other min version you would like to support, and I can update it :-)


[HelpDot] Enforce redirects in PR

Problem:
Given the helpDot search is just a Google Search and we are kind of constantly moving links around, we are always going to have dead links.
Solution:
When an article or hub is moved/renamed/deleted, we should add a PR check to detect it and enforce that a redirect URL is added for the new links.
Issue OwnerCurrent Issue Owner: @grgia

Not overdue

Waiting for PR review


Add themeing variables and fallback to color events based on category

Not sure if this is the way you were thinking of going about it, but it's a quick way of getting it set up with a fallback in case the css variable for the category isn't set.

Super appreciate your effort here! It's my fault for being unclear at first, but I've cleared up my intention in a related issue. This PR uses exact categories that only exist in our own implementation of the schedule and it's not universally applicable outside of Tekko, so I can't accept it as-is.


Built-in CSS/SCSS formatting

vscode has built-in formatting for web development (HTML, JS...), but no CSS & SCSS
Please add built-in CSS/SCSS formatting support, so we don't have to install a 3rd party extension just for this.
Similar old issue, which was closed: #28836
Thanks

We have still no plans to bundle or provide a css/scss formatter.
See https://github.com/microsoft/vscode/issues/19166#issuecomment-409928738

Actually why not just use the same formatter for formatting


/// overlap reported by this widget, called the _absorbed overlap_, is reported
/// to the [SliverOverlapAbsorberHandle], which is typically passed to a
/// [SliverOverlapInjector].
///
/// See also:
///
///  * [NestedScrollView], whose documentation has sample code showing how to
///    use this widget.
class SliverOverlapAbsorber extends SingleChildRenderObjectWidget {
  /// Creates a sliver that absorbs overlap and reports it to a
  /// [SliverOverlapAbsorberHandle].
  const SliverOverlapAbsorber({
    super.key,
    required this.handle,
    Widget? sliver,
  }) : super(child: sliver);

  /// The object in which the absorbed overlap is recorded.
  ///
  /// A particular [SliverOverlapAbsorberHandle] can only be assigned to a
  /// single [SliverOverlapAbsorber] at a time.
  final SliverOverlapAbsorberHandle handle;

  @override
  RenderSliverOverlapAbsorber createRenderObject(BuildContext context) {
    return RenderSliverOverlapAbsorber(
      handle: handle,
    );
  }

  @override
  void updateRenderObject(
      BuildContext context, RenderSliverOverlapAbsorber renderObject) {
    renderObject.handle = handle;
  }

  @override
  void debugFillProperties(DiagnosticPropertiesBuilder properties) {
    super.debugFillProperties(properties);
    properties.add(
        DiagnosticsProperty<SliverOverlapAbsorberHandle>('handle', handle));
  }
}

/// A sliver that wraps another, forcing its layout extent to be treated as
/// overlap.
///
/// The difference between the overlap requested by the child `sliver` and the
/// overlap reported by this widget, called the _absorbed overlap_, is reported
/// to the [SliverOverlapAbsorberHandle], which is typically passed to a
/// [RenderSliverOverlapInjector].
class RenderSliverOverlapAbsorber extends RenderSliver
    with RenderObjectWithChildMixin<RenderSliver> {
  /// Create a sliver that absorbs overlap and reports it to a
  /// [SliverOverlapAbsorberHandle].
  ///
  /// The [sliver] must be a [RenderSliver].
  RenderSliverOverlapAbsorber({
    required SliverOverlapAbsorberHandle handle,
    RenderSliver? sliver,
  }) : _handle = handle {
    child = sliver;
  }

  /// The object in which the absorbed overlap is recorded.
  ///
  /// A particular [SliverOverlapAbsorberHandle] can only be assigned to a
  /// single [RenderSliverOverlapAbsorber] at a time.
  SliverOverlapAbsorberHandle get handle => _handle;
  SliverOverlapAbsorberHandle _handle;
  set handle(SliverOverlapAbsorberHandle value) {
    if (handle == value) {
      return;
    }
    if (attached) {
      handle._writers -= 1;
      value._writers += 1;
      value._setExtents(handle.layoutExtent, handle.scrollExtent);
    }
    _handle = value;
  }

  @override
  void attach(PipelineOwner owner) {
    super.attach(owner);
    handle._writers += 1;
  }

  @override
  void detach() {
    handle._writers -= 1;
    super.detach();
  }

  @override
  void performLayout() {
    assert(
      handle._writers == 1,
      'A SliverOverlapAbsorberHandle cannot be passed to multiple RenderSliverOverlapAbsorber objects at the same time.',
    );
    if (child == null) {
      geometry = SliverGeometry.zero;
      return;
    }
    child!.layout(constraints, parentUsesSize: true);
    final SliverGeometry childLayoutGeometry = child!.geometry!;
    geometry = childLayoutGeometry.copyWith(
      scrollExtent: childLayoutGeometry.scrollExtent -
          childLayoutGeometry.maxScrollObstructionExtent,
      layoutExtent: math.max(
          0,
          childLayoutGeometry.paintExtent -
              childLayoutGeometry.maxScrollObstructionExtent),
    );
    handle._setExtents(
      childLayoutGeometry.maxScrollObstructionExtent,
      childLayoutGeometry.maxScrollObstructionExtent,
    );
  }

  @override
  void applyPaintTransform(RenderObject child, Matrix4 transform) {
    // child is always at our origin
  }

  @override
  bool hitTestChildren(SliverHitTestResult result,
      {required double mainAxisPosition, required double crossAxisPosition}) {
    if (child != null) {
      return child!.hitTest(
        result,
        mainAxisPosition: mainAxisPosition,
        crossAxisPosition: crossAxisPosition,
      );
    }
    return false;
  }

  @override
  void paint(PaintingContext context, Offset offset) {
    if (child != null) {
      context.paintChild(child!, offset);
    }
  }

  @override
  void debugFillProperties(DiagnosticPropertiesBuilder properties) {
    super.debugFillProperties(properties);
    properties.add(
        DiagnosticsProperty<SliverOverlapAbsorberHandle>('handle', handle));
  }
}

/// A sliver that has a sliver geometry based on the values stored in a
/// [SliverOverlapAbsorberHandle].
///
/// The [SliverOverlapAbsorber] must be an earlier descendant of a common
/// ancestor [Viewport], so that it will always be laid out before the
/// [SliverOverlapInjector] during a particular frame.
///
/// See also:
///
///  * [NestedScrollView], which uses a [SliverOverlapAbsorber] to align its
///    children, and which shows sample usage for this class.
class SliverOverlapInjector extends SingleChildRenderObjectWidget {
  /// Creates a sliver that is as tall as the value of the given [handle]'s
  /// layout extent.
  const SliverOverlapInjector({
    super.key,
    required this.handle,
    Widget? sliver,
  }) : super(child: sliver);

  /// The handle to the [SliverOverlapAbsorber] that is feeding this injector.
  ///
  /// This should be a handle owned by a [SliverOverlapAbsorber] and a
  /// [NestedScrollViewViewport].
  final SliverOverlapAbsorberHandle handle;

  @override
  RenderSliverOverlapInjector createRenderObject(BuildContext context) {
    return RenderSliverOverlapInjector(
      handle: handle,
    );
  }

  @override
  void updateRenderObject(
      BuildContext context, RenderSliverOverlapInjector renderObject) {
    renderObject.handle = handle;
  }

  @override
  void debugFillProperties(DiagnosticPropertiesBuilder properties) {
    super.debugFillProperties(properties);
    properties.add(
        DiagnosticsProperty<SliverOverlapAbsorberHandle>('handle', handle));
  }
}

/// A sliver that has a sliver geometry based on the values stored in a
/// [SliverOverlapAbsorberHandle].
///
/// The [RenderSliverOverlapAbsorber] must be an earlier descendant of a common
/// ancestor [RenderViewport] (probably a [RenderNestedScrollViewViewport]), so
/// that it will always be laid out before the [RenderSliverOverlapInjector]
/// during a particular frame.
class RenderSliverOverlapInjector extends RenderSliver {
  /// Creates a sliver that is as tall as the value of the given [handle]'s extent.
  RenderSliverOverlapInjector({
    required SliverOverlapAbsorberHandle handle,
  }) : _handle = handle;

  double? _currentLayoutExtent;
  double? _currentMaxExtent;

  /// The object that specifies how wide to make the gap injected by this render
  /// object.
  ///
  /// This should be a handle owned by a [RenderSliverOverlapAbsorber] and a
  /// [RenderNestedScrollViewViewport].
  SliverOverlapAbsorberHandle get handle => _handle;
  SliverOverlapAbsorberHandle _handle;
  set handle(SliverOverlapAbsorberHandle value) {
    if (handle == value) {
      return;
    }
    if (attached) {
      handle.removeListener(markNeedsLayout);
    }
    _handle = value;
    if (attached) {
      handle.addListener(markNeedsLayout);
      if (handle.layoutExtent != _currentLayoutExtent ||
          handle.scrollExtent != _currentMaxExtent) {
        markNeedsLayout();
      }
    }
  }

  @override
  void attach(PipelineOwner owner) {
    super.attach(owner);
    handle.addListener(markNeedsLayout);
    if (handle.layoutExtent != _currentLayoutExtent ||
        handle.scrollExtent != _currentMaxExtent) {
      markNeedsLayout();
    }
  }

  @override
  void detach() {
    handle.removeListener(markNeedsLayout);
    super.detach();
  }

  @override
  void performLayout() {
    _currentLayoutExtent = handle.layoutExtent;
    _currentMaxExtent = handle.layoutExtent;
    assert(
        _currentLayoutExtent != null && _currentMaxExtent != null,
        'SliverOverlapInjector has found no absorbed extent to inject.\n '
        'The SliverOverlapAbsorber must be an earlier descendant of a common '
        'ancestor Viewport, so that it will always be laid out before the '
        'SliverOverlapInjector during a particular frame.\n '
        'The SliverOverlapAbsorber is typically contained in the list of slivers '
        'provided by NestedScrollView.headerSliverBuilder.\n');
    final double clampedLayoutExtent = math.min(
      _currentLayoutExtent! - constraints.scrollOffset,
      constraints.remainingPaintExtent,
    );
    geometry = SliverGeometry(
      scrollExtent: _currentLayoutExtent!,
      paintExtent: math.max(0.0, clampedLayoutExtent),
      maxPaintExtent: _currentMaxExtent!,
    );
  }

  @override
  void debugPaint(PaintingContext context, Offset offset) {
    assert(() {
      if (debugPaintSizeEnabled) {
        final Paint paint = Paint()
          ..color = const Color(0xFFCC9933)
          ..strokeWidth = 3.0
          ..style = PaintingStyle.stroke;
        Offset start, end, delta;
        switch (constraints.axis) {
          case Axis.vertical:
            final double x = offset.dx + constraints.crossAxisExtent / 2.0;
            start = Offset(x, offset.dy);
            end = Offset(x, offset.dy + geometry!.paintExtent);
            delta = Offset(constraints.crossAxisExtent / 5.0, 0.0);
          case Axis.horizontal:
            final double y = offset.dy + constraints.crossAxisExtent / 2.0;
            start = Offset(offset.dx, y);
            end = Offset(offset.dy + geometry!.paintExtent, y);
            delta = Offset(0.0, constraints.crossAxisExtent / 5.0);
        }
        for (int index = -2; index <= 2; index += 1) {
          paintZigZag(
            context.canvas,
            paint,
            start - delta * index.toDouble(),
            end - delta * index.toDouble(),
            10,
            10.0,
          );
        }
      }
      return true;
    }());
  }

  @override
  void debugFillProperties(DiagnosticPropertiesBuilder properties) {
    super.debugFillProperties(properties);
    properties.add(
        DiagnosticsProperty<SliverOverlapAbsorberHandle>('handle', handle));
  }
}

/// The [Viewport] variant used by [NestedScrollView].
///
/// This viewport takes a [SliverOverlapAbsorberHandle] and notifies it any time
/// the viewport needs to recompute its layout (e.g. when it is scrolled).
class NestedScrollViewViewport extends Viewport {
  /// Creates a variant of [Viewport] that has a [SliverOverlapAbsorberHandle].
  NestedScrollViewViewport({
    super.key,
    super.axisDirection,
    super.crossAxisDirection,
    super.anchor,
    required super.offset,
    super.center,
    super.slivers,
    required this.handle,
    super.clipBehavior,
  });

  /// The handle to the [SliverOverlapAbsorber] that is feeding this injector.
  final SliverOverlapAbsorberHandle handle;

  @override
  RenderNestedScrollViewViewport createRenderObject(BuildContext context) {
    return RenderNestedScrollViewViewport(
      axisDirection: axisDirection,
      crossAxisDirection: crossAxisDirection ??
          Viewport.getDefaultCrossAxisDirection(
            context,
            axisDirection,
          ),
      anchor: anchor,
      offset: offset,
      handle: handle,
      clipBehavior: clipBehavior,
    );
  }

  @override
  void updateRenderObject(
      BuildContext context, RenderNestedScrollViewViewport renderObject) {
    renderObject
      ..axisDirection = axisDirection
      ..crossAxisDirection = crossAxisDirection ??
          Viewport.getDefaultCrossAxisDirection(
            context,
            axisDirection,
          )
      ..anchor = anchor
      ..offset = offset
      ..handle = handle
      ..clipBehavior = clipBehavior;
  }

  @override
  void debugFillProperties(DiagnosticPropertiesBuilder properties) {
    super.debugFillProperties(properties);
    properties.add(
        DiagnosticsProperty<SliverOverlapAbsorberHandle>('handle', handle));
  }
}

/// The [RenderViewport] variant used by [NestedScrollView].
///
/// This viewport takes a [SliverOverlapAbsorberHandle] and notifies it any time
/// the viewport needs to recompute its layout (e.g. when it is scrolled).
class RenderNestedScrollViewViewport extends RenderViewport {
  /// Create a variant of [RenderViewport] that has a
  /// [SliverOverlapAbsorberHandle].
  RenderNestedScrollViewViewport({
    super.axisDirection,
    required super.crossAxisDirection,
    required super.offset,
    super.anchor,
    super.children,
    super.center,
    required SliverOverlapAbsorberHandle handle,
    super.clipBehavior,
  }) : _handle = handle;

  /// The object to notify when [markNeedsLayout] is called.
  SliverOverlapAbsorberHandle get handle => _handle;
  SliverOverlapAbsorberHandle _handle;

  /// Setting this will trigger notifications on the new object.
  set handle(SliverOverlapAbsorberHandle value) {
    if (handle == value) {
      return;
    }
    _handle = value;
    handle._markNeedsLayout();
  }

  @override
  void markNeedsLayout() {
    handle._markNeedsLayout();
    super.markNeedsLayout();
  }

  @override
  void debugFillProperties(DiagnosticPropertiesBuilder properties) {
    super.debugFillProperties(properties);
    properties.add(
        DiagnosticsProperty<SliverOverlapAbsorberHandle>('handle', handle));
  }
}

Ideally, it would be desirable to reflect the ScrollPosition of the PrimaryScrollController only in the CustomScrollView that is in the active state (the tab is selected) among the CustomScrollViews in the NestedScrollView. However, as far as I checked with the sample code, the above workaround is working without any problems, so I would like you to consider this workaround if possible.

理想情况下，希望仅在 NestedScrollView 中的 CustomScrollView 中处于活动状态（选项卡被选中）的 CustomScrollView 中反映 PrimaryScrollController 的 ScrollPosition。但是，据我检查示例代码，上述解决方法可以正常工作，没有任何问题，因此我希望您尽可能考虑此解决方法。

改动不错，但是有个问题，这样处理之后，列表向下滑动后，SliverAppBar会和列表一起向下滚动，但实际上应该是列表滚动到顶部后，再执行SliverAppBar的滚动，楼主有办法解决吗

The modification is good, but there is an issue. After making these changes, when the list is scrolled downward, the SliverAppBar scrolls down along with the list. However, in reality, the SliverAppBar should only start scrolling after the list has scrolled to the top. Do you have any solutions for this?

Are you referring to the floatHeaderSlivers setting?
In my sample code, floatHeaderSlivers: true is set, so the AppBar scrolls down at all times, but specifying floatHeaderSlivers: false resolves this.

@Piinks
Why was the priority of this issue lowered to P3?
I believe this issue is a critical bug and requires a prompt fix.
If my proposed workaround is acceptable, could it be officially adopted?

Any update in this issue?

Ugh, no updates to this issue :(

2024 is almost over. This problem has lasted for five years. Doesn't Flutter have any solution yet?

This problem still exists...

#21868
#36419
#40740
#62833
#81619

I'd be super happy if all 5 of these were completely resolved by this 1 change, but if there's a bug that still needs to be looked at, feel free to open a new issue.


Uncaught Error: Encountered an invalid scope end id. Popped -59, expected to pop -63.

[Enter steps to reproduce below:]

...
...

Atom Version: 1.0.2
System: Mac OS X 10.10.4
Thrown From: Atom Core
Stack Trace
Uncaught Error: Encountered an invalid scope end id. Popped -59, expected to pop -63.
At /Applications/Atom.app/Contents/Resources/app.asar/src/tokenized-buffer.js:629

Error: Encountered an invalid scope end id. Popped -59, expected to pop -63.
  at TokenizedBuffer.module.exports.TokenizedBuffer.scopesFromTags (/Applications/Atom.app/Contents/Resources/app.asar/src/tokenized-buffer.js:619:23)
  at TokenizedBuffer.module.exports.TokenizedBuffer.openScopesForRow (/Applications/Atom.app/Contents/Resources/app.asar/src/tokenized-buffer.js:601:21)
  at TokenizedBuffer.module.exports.TokenizedBuffer.tokenizeNextChunk (/Applications/Atom.app/Contents/Resources/app.asar/src/tokenized-buffer.js:294:105)
  at /Applications/Atom.app/Contents/Resources/app.asar/src/tokenized-buffer.js:271:26
  at /Applications/Atom.app/Contents/Resources/app.asar/node_modules/underscore-plus/node_modules/underscore/underscore.js:666:47

Commands
     -2:39.3.0 editor:consolidate-selections (atom-text-editor.editor.is-focused)
     -2:39.3.0 core:cancel (atom-text-editor.editor.is-focused)
     -2:31.5.0 find-and-replace:show (atom-text-editor.editor.is-focused)
  7x -2:18.9.0 core:confirm (atom-text-editor.editor.mini.is-focused)
     -2:09.1.0 omnisharp-atom:go-to-definition (atom-text-editor.editor.is-focused)
     -2:07.2.0 editor:consolidate-selections (atom-text-editor.editor.is-focused)
     -2:07.2.0 core:cancel (atom-text-editor.editor.is-focused)
     -1:56.3.0 omnisharp-atom:find-usages (atom-text-editor.editor.is-focused)
     -1:52.1.0 editor:toggle-line-comments (atom-text-editor.editor.is-focused)
     -1:48.9.0 omnisharp-atom:find-usages (atom-text-editor.editor.is-focused)
     -0:21.3.0 editor:consolidate-selections (atom-text-editor.editor.is-focused)
     -0:21.3.0 core:cancel (atom-text-editor.editor.is-focused)
     -0:17 core:backspace (atom-text-editor.editor.is-focused)
     -0:16.1.0 core:undo (atom-text-editor.editor.is-focused)
     -0:15.1.0 editor:toggle-line-comments (atom-text-editor.editor.is-focused)
  2x -0:14.5.0 core:save (atom-text-editor.editor.is-focused)

Config
{
  "core": {
    "themes": [
      "atom-material-ui",
      "solarized-dark-syntax"
    ],
    "projectHome": "/Users/Lee/Documents",
    "ignoredNames": [
      "*.git",
      "*.meta",
      ".DS_Store",
      "obj",
      "Temp",
      "Library",
      "ProjectSettings",
      "*.csproj",
      "*.unityproj",
      "*.sln",
      "*.userprefs",
      ".gitignore"
    ],
    "disabledPackages": [
      "javascript-snippets",
      "autocomplete-paths",
      "atom-yeoman",
      "advanced-new-file",
      "minimap-highlight-selected",
      "minimap-find-and-replace",
      "git-log",
      "jshint",
      "docblockr",
      "pretty-json",
      "script",
      "vim-mode"
    ]
  },
  "editor": {
    "invisibles": {},
    "fontFamily": "Monaco",
    "preferredLineLength": 120,
    "showIndentGuide": true,
    "softWrapAtPreferredLineLength": true,
    "tabLength": 4,
    "zoomFontWhenCtrlScrolling": true,
    "softTabs": false,
    "fontSize": 15
  }
}

Installed Packages
# User
atom-beautify, v0.28.8
atom-material-ui, v0.5.9
file-icons, v1.5.8
highlight-selected, v0.10.1
linter, v1.2.4
minimap, v4.12.0
omnisharp-atom, v0.22.2
pigments, v0.9.0

# Dev
No dev packages

Thanks for another report, @ccbentlee! If you could share the file for which this happened and explain what you were doing when this happened -- that'd be really helpful.
Also, these situations should no longer throw exceptions in the next version of Atom (see https://github.com/atom/atom/pull/7949), so I'm going to close this. Still, if you could share the information I asked about above, that'd be great. /cc @nathansobo


Install ALLUSER=1 error

When trying to install with the ALLUSER=1 switch I'm getting the error:
"cannot install for all users when a VDI environment is not detected"
Any info on why this is happening? Some hidden restriction or requirement to install on a per-machine basis?

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

ID: 17880b9d-6b98-3194-cc33-fe8067ce241e
Version Independent ID: 643bcf2f-507b-e449-73db-923d8a368ad9
Content: Teams for Virtualized Desktop Infrastructure
Content Source: Teams/teams-for-vdi.md
Service: msteams
GitHub Login: @LanaChin
Microsoft Alias: v-lanac

@Everink - Thank you for submitting this feedback.
I will get this over to for investigation. Thank you for reporting and making the docs better. Much appreciated.

@officedocsbot assign @scanum

I am also getting this error when trying to create an captured application using VMware AppVolumes.
Here is the log: https://pastebin.com/daNNZ1kD

@Everink  - thank you for submitting feedback.
I think the best way forward is if you open a service ticket in your tenant so this can get resolved ASAP. Based on the outcome let me know if it is something that can be called out in the docs.
Please follow this link to contact support for business products:  https://docs.microsoft.com/office365/admin/contact-support-for-business-products
Please keep us posted here on the resolution so we can feed whatever information you discover into the content.

@officedocsbot close

The installer looks for VDI registry keys.  If it doesn't find them, then it throws the error that you can't install it.  If you use create the keys it's looking for, then it will let you install it.  I had to do this to package it for my environment, too -- since my packaging machine doesn't have a VDI client installed on it.  I created HKLM\Software\Citrix\PortICA and it was enough to allow me to continue packaging.

Thanks for the info @Chireven. Using this I have found the VMware equivalent as well which is:
HKLM\SOFTWARE\VMware, Inc.\VMware VDM\Agent

I, too, get the "Installation has failed" error, "Cannot install for all users when a VDI environment is not detected."  I use neither VMware nor Citrix but, ironically, Hyper-V.  So, it can't detect that I'm using Hyper-V?  No?  Microsoft, don't you want to promote Hyper-V?  You really need to get this fixed.


OBS: use SeedImage build image from OBS for the chart

We need to double check OBS seedimage image version before merging this PR, as the version there doesn't look the expected one.


SILBridging: fix a compiler warning when building with pure bridging mode (e.g. in Debug)

@swift-ci smoke test


Update deprected database engine in docs

The django.db.backends.postgresql_psycopg2 module is deprecated in favor of django.db.backends.postgresql. It’s been an alias since Django 1.9. This only affects code that imports from the module directly. The DATABASES setting can still use 'django.db.backends.postgresql_psycopg2', though you can simplify that by using the 'django.db.backends.postgresql' name added in Django 1.9.

https://docs.djangoproject.com/en/stable/releases/2.0/#id1

Huh, TIL!


Update usdcreatechannel.md

Updated $createChannel to v5

@Apricityy Very good. Thanks for contributing to the doc. @Leref can you merge this one?

this needs a update because v5.2.0 will support json
to allow optional properties
aka if u want to set rtcRegion then
{
"rtcRegion" : "......"
}

this needs a update because v5.2.0 will support json
to allow optional properties
aka if u want to set rtcRegion then
{
"rtcRegion" : "......"
}

I know but after the release of 5.2.0 it will be updated by us. Till now as per 5.1.2 it's perfect.


How do I contribute?

I've made an icon for Castlevania - Aria of Sorrow, where should I upload it?

Clone this repo and make a pull request after you added the icon to it. If you want I could also just upload it here. Of course you would get the credits for the icon.


Fix selectors for FHKiel's overview

FH Kiel recently updated their QIS system, which for some reason mirrored the order of rows in the exam overview table. This Pull-Request addresses theses changes.

Hey @nscuro, thanks for the pull request. It's merged and published. ✌


WIP: Add weakKeys() to TagTrackingCache

Coverage increased (+0.01%) to 22.882% when pulling 69bd7295aaf90c8fdc6eae0a1455e61a45125cd5 on bjagg:Mem-Issues into 47247bdb315d3715b5a9f9c840d25ac87af56332 on Jasig:master.

Coverage decreased (-0.01%) to 22.857% when pulling 4005876f66aad9876d64f7d10c74d55604565098 on bjagg:Mem-Issues into 47247bdb315d3715b5a9f9c840d25ac87af56332 on Jasig:master.

Coverage decreased (-0.01%) to 22.856% when pulling a659d27f274276abf81a2e0f77c515c6f4ce5bb5 on bjagg:Mem-Issues into 47247bdb315d3715b5a9f9c840d25ac87af56332 on Jasig:master.

Coverage decreased (-0.002%) to 22.869% when pulling a388143858c99799345aa678fce6463194ed67c7 on bjagg:Mem-Issues into 47247bdb315d3715b5a9f9c840d25ac87af56332 on Jasig:master.

I suggest separating DAO_PING into a separate PR. It is a separate issue/behavior.


Bug: Guard with state.can don't react to react useState being toggled

Description
I tried to fiddle with latest beta of xstate and @xstate/react packages and I noticed something odd.
When I tried this simplified replication, it behaved the same.
I basically do simple named guard and provide implementation to the machine in useMachine hook like this
const toggleMachine = createMachine({
  id: "toggle",
  initial: "inactive",

  states: {
    inactive: {
      on: {
        next: {
          target: "active",
          guard: "someCondition"
        }
      }
    },
    active: {
      on: {
        back: {
          target: "inactive"
        }
      }
    }
  }
});

function App() {
  const [state, send] = useMachine(
    toggleMachine.provide({
      guards: {
        someCondition: () => isEnabled
      }
    })
  );
  const [isEnabled, setEnabled] = useState(false);

  return (

XState React Template

      <input
        type="checkbox"
        checked={isEnabled}
        onChange={(e) => {
          setEnabled(e.target.checked);
        }}
      />
      {state.matches("active") && (
        <>

 Active

          <button onClick={() => send({ type: "back" })}>Go back</button>
        </>
      )}
      {state.matches("inactive") && (
        <>

 Inactive

          <button
            //  uncomment this line VVVVVVVVVVVV

            // disabled={!state.can("next")}

            // ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
            onClick={() => send({ type: "next" })}
          >
            Go
          </button>
        </>
      )}

  );
}

Expected result
And I cannot advance until I satisfy the guard condition, and the  is grayed out...
Actual result
...but when I click on the checkbox, react value changes, but button is still grayed out. When I comment out the disable={!state.can(type: {"next"})} it works as expected, but I'd like to provide some user feedback as well
Reproduction
https://codesandbox.io/s/usestate-and-usemachine-ccf3gm?file=/src/index.js
Additional context

Okay, I see. If I get that correctly, it's either go full with xstate, or do odd gymnastics to include a state machine to the existing codebase.
But good to know that state.can needs an object.


Using this as a background service

Hi
Great plugin.. thanks for that. I need to have permanent connection with the server.. is it possible to have this plugin run as a background service so that the service still runs if the app is killed? Or is there a better solution for that scenario?

Although this plugin does not run in service (because of I didn't design for it), the source code is able to run in service.
Create a service class, then copy the source code.

Thanks, yes, I did it and it seems to work. However, https didn't work out of box. I will need to investigate it a bit further. I have seen this thread: https://github.com/nkzawa/socket.io-client.java/issues/26 - but I will read it tomorrow.
Had you tested it with https?

Yes, this library works fine with https. I uses https://github.com/nkzawa/socket.io-client.java in my work project.
Do you use self-signed ssl file, perhaps?

Hi yes, I am using self-signed certificates, but I tried to install it on my device and it said certificate is installed. However, it doesnt list it under Security-Credential Storage-Trusted Credentials. I am not too sure if it is supposed to list it there anyway.
Should it work with self signed certs once they are installed?

Using the SSL configuration code from page below makes it work:
https://github.com/jonathanve/socket-io-android/blob/master/client-snippet.java

asda


used fixed rush version because the latest one has bug

used fixed rush version because the latest one has bug
Packages impacted by this PR
Issues associated with this PR
Describe the problem that is addressed by this PR
What are the possible designs available to address the problem? If there are more than one possible design, why was the one in this PR chosen?
Are there test cases added in this PR? (If not, why?)
Provide a list of related PRs (if any)
Command used to generate this PR:**(Applicable only to SDK release request PRs)
Checklists

[ ] Added impacted package name to the issue description
[ ] Does this PR needs any fixes in the SDK Generator?** (If so, create an Issue in the Autorest/typescript repository and link it here)
[ ] Added a changelog (if necessary)

/check-enforcer override

@dw511214992, @qiaozha, @MaryGao: I suspect you were hitting https://github.com/microsoft/rushstack/issues/3979, which should be fixed in rush 5.93.1.
For context, rush uses a "version selector", where the globally-installed tool should behave like the version specified in rush.json: https://rushjs.io/pages/configs/rush_json/
So normally, it doesn't matter what version of rush you have installed globally, what matters is the version in rush.json.
However, rush 5.93.0 had a rare bug that broke the version selector, and it was fixed quickly.
All this said, if you are installing rush globally in automation, it is best to pin a specific version to avoid the possibility of being broken by a new rush release.  So I recommend keeping the rush version pinned in automation_init.sh.  You could update it occasionally (say every few months), or only update it when something breaks (e.g. when rush releases a new major version).  What really matters is the version in rush.json, not the version globally installed.

Another question is whether you need to be installing rush globally at all.  In the data-plane pipelines, we do not install rush globally, instead we call:
https://github.com/Azure/azure-sdk-for-js/blob/2461696b38f09e54c25f8a7bbf096fd3c8a85548/eng/pipelines/templates/steps/build.yml#L44
The files checked into this repo under common/scripts allow you to run the rush version configured in this repo without needing to install rush globally.  Maybe you could change your automation to call these scripts instead of installing rush globally?


Regression Caused by Permissions Change - Expenses

This is related to several tickets; https://opencollective.freshdesk.com/a/tickets/180260 and https://opencollective.com/ridgewood-mutual-aid-project/expenses/129629
In these cases the collective admins are trying to edit an expense but fails to do so as per the recent expense permissions change, https://github.com/opencollective/opencollective-api/pull/8655.
My suggestion is that since we have remove the permission from the collective admins to do the majority of expense edit functionality not show the "Edit" button in the actions drop-down for collective admins thus making the collective admins unable to edit expenses.

@Betree : Let me know what you think. I've opened a PR with the proposed fix.

Interesting, I didn't see this one coming. Your fix makes sense; we should merge it.
But I see a need for collective admins to upload receipts for any virtual card charge triggered on their collectives, not just the ones they're assigned to. Let's start restrictive and update depending on the feedback we get.

Interesting, I didn't see this one coming. Your fix makes sense; we should merge it.
But I see a need for collective admins to upload receipts for any virtual card charge triggered on their collectives, not just the ones they're assigned to. Let's start restrictive and update depending on the feedback we get.

Yes definitely, I think this new process will create some issues for collective admins who use to edit expenses themselves now that they cannot do it anymore. So being able for the collective admins to edit some parts of the expense might make sense like the virtual cards as well as expense description and title. 🤔


Dump when loading an xlsm with an PieChart

When you are using the Demo Report ZDEMO_EXCEL29 and loading an xlsm with a pie chart .
It will create an Dump.
Because in the Reader Class has no coding which detect the right chart and so it use the the barchart  ( DEFAULT value in Drawing Class). And with the barchart it find no attribute and so you get an dump.
Bugfix:
Line : 765 in zcl_excel_reader_2007
  IF drawing_type = zcl_excel_drawing=>type_chart.

*    ROTDA
    DATA: lo_tmp_node_2                TYPE REF TO if_ixml_element.
    lo_tmp_node_2 ?= rel_drawing-content_xml->find_from_name( name = 'pieChart' namespace = 'c' ).
    if lo_tmp_node_2 is not initial.
        lo_drawing->graph_type = zcl_excel_drawing=>c_graph_pie.
    else.
        lo_tmp_node_2 ?= rel_drawing-content_xml->find_from_name( name = 'barChart' namespace = 'c' ).
          if lo_tmp_node_2 is not initial.
                lo_drawing->graph_type = zcl_excel_drawing=>c_graph_bars.
          else.
              lo_tmp_node_2 ?= rel_drawing-content_xml->find_from_name( name = 'lineChart' namespace = 'c' ).
              if lo_tmp_node_2 is not initial.
                   lo_drawing->graph_type = zcl_excel_drawing=>c_graph_line.
              endif.
          endif.
    endif.
* End of Change
    "-------------Added by Alessandro Iannacci - Should load chart attributes
    lo_drawing->load_chart_attributes( rel_drawing-content_xml ).
  ENDIF.

Can you provide a pull request of this change so we can include this fix to the main stream?


bump to 1.8

Initial PR to test out 1.8 :)
Tackling #879 - not everything from there has been implemented yet though!
Close #879
Close https://github.com/kubernetes-incubator/cri-o/issues/869
Close https://github.com/kubernetes-incubator/cri-o/issues/202
Do not merge this, I'll create a separate branch on origin once this is finished.
@mrunalp PTAL :)

/test all

alrighty, moved tests to kube 1.8 as well

/test all

@mrunalp this is finished now :tada: PTAL commit by commit

/test all

/test all

/test integration_rhel

is RHEL still busted for integration and e2e?
Fedora integration works fine, I see guestbook (2) tests failing on Fedora and other 2 I'm fixing. @mrunalp are the guestbook tests known issue right?

We can rebase and run the ami test on this now.

@mrunalp rebased

This is now tracking upstream v1.8.0 :)

/test all

integration tests are failing because they don't use the correct crictl version as found in contrib/test/integration/build/cri-tools.yml, @mrunalp how do I update the tests to use that? /test ami?

/test ami

rebased

/test all

/test ami

and also updated to kube 1.8.1

Yes lets get this merged.

removed DO NOT MERGE, let's get this merged now that we have a release-1.0 branch

so this is blocked on #1016 as well

/test ami

Ami isn't going to work before #1016

/test all

@runcom does this need to be rebased?

@runcom does this need to be rebased?

not sure, but I've just force pushed after a rebase

/test all

@mrunalp it seems that the stuff failing are still because amis aren't using the fix froom #1016

/test all

/test integration_rhel

/test all

/test all

/test ami

/test ami_fedora

/test integration_fedora

/test integration_rhel

/test ami_fedora

wtf, ami_fedora is failing with:
2017/10/19 02:46:14 e2e.go:77: Calling kubetest --test -test_args=-host=https://<IP_ADDRESS>:6443 --ginkgo.focus=\[Conformance\] --report-dir=/tmp/artifacts...
unknown shorthand flag: 't' in -test_args=-host=https://<IP_ADDRESS>:6443 --ginkgo.focus=\[Conformance\] --report-dir=/tmp/artifacts

when trying to run e2e ...

nevermind, should be fixed now :)

/test all

/test ami

@mrunalp looks like this is ready now :tada:

/test ami

/test all

/test all

/test ami

Looks like integration tests for sysctl must be fixed

/test all

/test ami

/test all

/test ami

/test ami

/test all

We should now merge this one and continue 1.0 development on the release-1.0 branch This is rebased and potentially ready to merge guys.

We should now merge this one and continue 1.0 development on the release-1.0 branch This is rebased and potentially ready to merge guys.

oh well, but AMIs....

/test ami_fedora

/test ami

/test all

/test ami
/test all

/test ami
/test all

/test all

LGTM

we can merge this now :)

we can merge this now :)

oh already done lol

So should we build cri-o 1.8 for Rawhide now?  And Ubuntu?

We'll tag cri-o 1.8 tomorrow, afterwards we'll build packages for ubuntu and rawhide


Persist sandboxed pids

Fixes #59. This will persist even sandboxed PIDs for testing.

[ ] (wip) Implement a minimal (e.g. no human readable names) record representation which can be stored in a database
[ ] test storing and retrieving this representation
[ ] Add this to the inMemory system and change its name. Whether this will be in-memory will then be decided by the database path which is already available
[ ] Document how to switch between in-memory and local storage (can we work around absolute paths?)
[ ] Test the "new pid system"

I've commented a solution which is also used for ContentInformation entities in base-repo (and metastore). For sure, there is also a solution with the approach before (creating a new entity for each key-value pair), but the "new" approach is much easier to handle, also with regards to replacing things, as this is automatically handled by JPA. I was a bit confused, that the @Transactional annotation was needed, as I'm not using it for ContentInformation. Maybe there is still something missing, but for the moment the tests will run.

Pull Request Test Coverage Report for Build #86

9 of 24 (37.5%)  changed or added relevant lines in 2 files are covered.
22 unchanged lines in 1 file lost coverage.
Overall coverage increased (+1.4%) to 48.22%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/main/java/edu/kit/datamanager/pit/domain/minimal/MinPidRecord.java
8
15
53.33%

src/main/java/edu/kit/datamanager/pit/domain/minimal/MinPidRecordEntry.java
1
9
11.11%

Files with Coverage Reduction
New Missed Lines
%

src/main/java/edu/kit/datamanager/pit/web/impl/TypingRESTResourceImpl.java
22
75.86%

Totals

Change from base Build #53:
1.4%

Covered Lines:
650

Relevant Lines:
1348

💛  - Coveralls


Refx/warnings

Clean up a few warnings

Nice!
On January 11, 2024 at 2:19:15 PM, Roland Rabien<EMAIL_ADDRESS>wrote:
Clean up a few warnings

You can view, comment on, or merge this pull request online at:
https://github.com/sudara/melatonin_blur/pull/53
Commit Summary

a9b23f9https://github.com/sudara/melatonin_blur/pull/53/commits/a9b23f9adc35be43e3e7d647e5e9005901be7237 Fix macOS warnings
c793410https://github.com/sudara/melatonin_blur/pull/53/commits/c793410186fb75d4a2f69f781cd6d3e305cc5327 Silence warnings
a158298https://github.com/sudara/melatonin_blur/pull/53/commits/a15829800af7bb63d8fee64399c95b8751105053 Silence warning
ac6d026https://github.com/sudara/melatonin_blur/pull/53/commits/ac6d0269c812b4005d5144c4648c2d0da46b825c Merge branch 'main' into refx/warnings

File Changes
(3 fileshttps://github.com/sudara/melatonin_blur/pull/53/files)

M melatonin/implementations/float_vector_stack_blur.hhttps://github.com/sudara/melatonin_blur/pull/53/files#diff-2c86792a44518b7b0dd561971566b9a11eda59becc890b04e0e075ccecfe8cca (10)
M melatonin/implementations/vImage.hhttps://github.com/sudara/melatonin_blur/pull/53/files#diff-3a5d352d40024b4a48534335e4083e415043064ced70e912c8905492c25c6824 (3)
M melatonin/implementations/vImage_macOS14.hhttps://github.com/sudara/melatonin_blur/pull/53/files#diff-b65bee19eead13345608f60292ac7151fbac6774c29dcd56ba8d5475da447d10 (3)

Patch Links:

https://github.com/sudara/melatonin_blur/pull/53.patch
https://github.com/sudara/melatonin_blur/pull/53.diff

—
Reply to this email directly, view it on GitHubhttps://github.com/sudara/melatonin_blur/pull/53, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ABRAVN4RCKK5VK5L7OD3O3LYOA3K5AVCNFSM6AAAAABBXAFLZ2VHI2DSMVQWIX3LMV43ASLTON2WKOZSGA3TONBSGQYDCMA.
You are receiving this because you are subscribed to this thread.Message ID: @.***>


plz help again😭😭

Describe your problem here.
I've wasted my whole day compiling source code and then now at 12 am this happend and now im sad

btw i have jdk 17
Are you modding a build from source or with Lua?
Source
What is your build target?
Android
Did you edit anything in this build? If so, mention or summarize your changes.
yes but only for that type not found: teacall and project.xml

i think you can update your project compileSdkVersion normally there are a lot of problems whit the buil.gradle, i dont think the problem is the jdk 17, but try updating first the android if you search Android Gradle Plugin 7.0.0  and newest versions are compitable with jdk 17 so the problem can be other.
https://stackoverflow.com/questions/69029508/androidx-corecore-ktx1-7-0-depenceny-error-appeared-without-any-modification

run these commands
haxelib remove extension-androidtools
haxelib git extension-androidtools https://github.com/MobilePorting/extension-androidtools SAF

im going to try

type that in project.xml

in ### project.xml add


Expose tree index at placeholder position

Is your feature request related to a problem? Please describe.
When dragging from one tree to another, I can't currently find a way to drop the external node into the location shown by the placeholder (as demo'd in the "Manual sort with placeholder" example). If the index of the tree item before the placeholder was somehow exposed, I could then calculate the position required to push the new node item into the tree.
Describe the solution you'd like
Expose the index of the tree item before the placeholder component
Describe alternatives you've considered
I cannot find another way of doing what I'm after. Any solution that would allow the correct position for the external node to be placed would be fine - it doesn't have to be the one I've suggested

@chris-oms Can't use options.relativeIndex?

@minop1205 I get Property 'relativeIndex' does not exist on type 'PlaceholderRenderParams'
Looks like the only property of options that is passed through to placeholderRender is depth, or am I missing something?
placeholderRender={(node, { depth }) => <OrderDividerPlaceholder depth={depth} />}


[RESOLVED] Interface eth0(): High error rate (>2 for 5m)

Problem started at 16:15:29 on 2023.06.02
Problem name: Interface eth0(): High error rate (>2 for 5m)
Host: S100-Primario
Severity: Warning
Operational data: errors in: 1, errors out: 0
Original problem ID: 23167
Event details in Zabbix: http://<IP_ADDRESS>/tr_events.php?triggerid=23483&eventid=23167

Problem has been resolved in 9m 0s at 16:24:29 on 2023.06.02
Problem name: Interface eth0(): High error rate (>2 for 5m)
Host: S100-Primario
Severity: Warning
Original problem ID: 23167


pull request for e2e test at 11/28/2016 22:56:03

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


Swift Package Manager

Any chance to add the required package.swift so that we can install the library through Swift Package Manager?
This is the last package of my app for which I a, keeping Cocoa Pod

I created a fork to support SPM, but it will be good to have it here :)

Hi @erwanmace, I also created a SPM fork, upgrading support to XCode 11 (minimum required for SPM availability) and with a dependency to FXPageControl lib (a PR has been pushed to this repo too), which was copied in sources until now. You can check the diff here: https://github.com/xmartlabs/XLPagerTabStrip/compare/master...Climbatize:XLPagerTabStrip:master and use this repo in your SPM config: https://github.com/Climbatize/XLPagerTabStrip.git

Hi all, SPM support has been added in 9.1.0!


fix: correctly claim capability for mock module, handle genesis exports

…ability

Description
This contains two fixes:

the capability being claimed by the scoped keeper was incorrect (mock.ModuleName -> port ID)
the mock module wasn't accounting for non empty genesis state in capabilities (after genesis export, capability will create the bound ports so rebinding doesn't need to happen)

closes: #XXXX

Before we can merge this PR, please make sure that all the following items have been
checked off. If any of the checklist items are not applicable, please leave them but
write a little note why.

[ ] Targeted PR against correct branch (see CONTRIBUTING.md)
[ ] Linked to Github issue with discussion and accepted design OR link to spec that describes this work.
[ ] Code follows the module structure standards.
[ ] Wrote unit and integration tests
[ ] Updated relevant documentation (docs/) or specification (x/<module>/spec/)
[ ] Added relevant godoc comments.
[ ] Added a relevant changelog entry to the Unreleased section in CHANGELOG.md
[ ] Re-reviewed Files changed in the Github PR explorer
[ ] Review Codecov Report in the comment section below once CI passes

Not going to add a changelog since this is a fix to an unreleased feature


What are the different CSAF profiles?

Create short videos (~ 2 minutes long) explaining the content described in the title of this issue. This issue is tracked in the parent issue #30


Added vtsnis.txt

School website is: http://vtsnis.rs
Name: Visoka tehnicka skola strukovnih studija.
Programs that include programming are:
http://vtsnis.rs/savremene_racunarske_tehnologije.html
http://vtsnis.rs/spec_srt.html
Site containing all schools and universities in Serbia, link to this school: http://fakulteti.edukacija.rs/drzavne-visoke-skole/visoka-tehnicka-skola-strukovnih-studija-nis
The school has two domains which share the same website: vtsnis.edu.rs and vtsnis.rs
whois search
vtsnis.rs - https://who.is/whois/vtsnis.rs
vtsnis.edu.rs - https://who.is/whois/vtsnis.edu.rs

@AleksandarPredic Pull request merged. Thank you!


Handle retries correctly (amendment)

Previously a PR related was closed due to a null expression in the retry spel handler. This has now been corrected.
Run all tests, particularly RabbitSpringIntegrationDLQAndRetriesIT.

can you update from master pls - but this looks really good


toggle_check.png is almost invisible

The toggle check image is white on transparent, making it invisble or close to invisible on my setup.
Here it's hardly seen on dark rows, and invisible on white ones:

I'm using chromium Version 40.0.2214.111 on Kubuntu.

btw, I switched to using this: http://www.veryicon.com/icons/internet--web/web-development-3/action-check-grey-thin.html and it looks well.
It comes with Creative Commons Attribution 3.0 License.

At the moment I do not see such a problem. If it is still relevant, tell us more details


Add support for ivy-posframe

This pull request adds themes for Ivy Posframe.
By default, the inherited posframe theme has the same background color as buffers, and it is hard to distinguish where the posframe ends and the buffer begins. This commit sets the background for ivy-posframe and ivy-posframe-border to nord1.

Hi @ReilySiegel :wave:, thanks for your contribution :+1:
I'll review the changes in the near future and get back to you.

Release Note Assets

Before

After


Insert signatures without rpmsign

At this moment, the signature insertion is being handled by using rpmsign and then just cp as the gpg command.
It would be great if we could instead just get the RPM sighdr, insert it in there, and then save that.
That would bring us a step closer to not even needing the full RPM on the box that executed this part of the process (since we upload just the sighdr to Koji).
If this is in place, we could add an endpoint to Koji to get just the sigheader/header part of an RPM, and never need the full RPM.

This is also needed as older RPM versions create a v3 signature by default, which can't work with this method of header signing, and they have no option to not create a v3 signature.

For information: I was waiting to fix this until I had tests in place, to ensure that my changes wouldn't break things (and I didn't have to manually test everything).
Given that I just merged a test suite, I hope to work on this shortly.


[Bug]: HTML headings in quest descriptions don't wrap

Bug Description
In the screen shot the sample sentence is repeated four times.
The first two repetitions are inside <H1> (first line) and <H2> (second line) tags.
The third and fourth repetitions are on one line, without any html tags.

Version
0.5.4
Mod Loader Version
0.14.22
Mod Loader
Fabric
Logs or additional context
No response
Code of Conduct

[X] I have searched the issue tracker and confirmed that the issue has not been reported
[X] I have checked the FAQ (if one is present) and my issue is not listed
[X] I have verified that I am using the latest version of the mod
[X] I have verified that I have installed all the required dependencies for the mod
[X] I have verified that I do not have Optifine installed. We will close issues if we detect Optifine is in your pack. We cannot fix Optifine issues. Please do not report issues with Optifine present.

This needs to be reported to the hermes repo https://github.com/terrarium-earth/Hermes

Ah ha. Looks like someone has already reported this to that repo.


Peering Request

Full Name
Vorsk
ASN
22296
PeeringDB Integration

[X] My PeeringDB Entries are current
[ ] Peer at ALL EXCHANGES (and skip the Peer Address(es) field below)

Peer Address(es)
<IP_ADDRESS>
2602:2e5::1
Multihop

[X] Multihop Peering Request

Thanks for contributing to the RouteViews project! We've established IPv4 and IPv6 multi-hop BGP sessions on the route-views5 collector:

asn:  6447
ipv4: <IP_ADDRESS>
ipv6: 2001:468:d01:33::80df:3369
fqdn: route-views5.routeviews.org

Relevant show bgp summary output:
    Neighbor       V         AS   MsgRcvd   MsgSent   TblVer  InQ OutQ  Up/Down State/PfxRcd   PfxSnt Desc
<IP_ADDRESS>         4      22296         0         0        0    0    0    never       Active        0 Vorsk LLC
2602:2e5::1        4      22296         0         0        0    0    0    never       Active        0 Vorsk LLC

Please filter out default route and RFC6490 address space.
NOTE: we do not accept addpath-RX or TX on connections.
Many thanks! :-)


Configure spotless (linter for java) to check/add licence header

./gradlew spotlessApply

adds missing header automatically for all java files
Note: CI workflow for java includes linter verification
Next step (next PR(s)):

spotless for gradle files
linter for rust for license header check
license header check for all [source] files in CI

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Thanks, working on it


Update team members pagination to be 1-indexed for 1.20

Currently, AllSpice Hub is at 1.19, where the team members endpoint is paginated with a 0-based index. This was fixed in 1.20 (go-gitea/gitea#24754) and the endpoing is 1-based as documented. Right now, py-allspice uses the 0-index, and when AllSpice Hub switches to 1.20 this will lead to duplicates in the list of team members. We'll have to change Team.get_members when we release 1.20.

Thanks for finding this! Can you add a cron job to schedule the CI tests nightly? I think it'll help us preemptively catch issues like this (where we might update the application to 1.20, but forget to update py-allspice).

Resolved by #48.


Skip cell typing if results files already exist

After we complete #415, we will want to add an option to skip the actual cell type classification for SingleR and CellAssign if the output already exists. This should save us time whenever we are re-processing samples. Similar to --repeat_mapping, except --repeat_celltyping.
In doing this we will want a way to track the reference versions used for both cell typing methods and only skip when both the output files exist and the reference version matches.
For PanglaoDB references we can pull the date from the file name. For celldex reference versions we should match up the package version.

Noting that from our discussion this should be done within the annotate_celltypes workflow. We will want to add the following checks for each library:

if the output tsv from CellAssign exists
if the reference version matches for CellAssign (date in file)
if the output tsv from SingleR exists
if the reference version matches for SingleR (package version for celldex)

If those conditions are met the process for classify_SingleR and classify_cellassign will be skipped, but the process for adding cell type annotations into the object will still be run.

@allyhawkins just wanted to link in this somewhat related issue: https://github.com/AlexsLemonade/scpca-nf/issues/470

Closed by #510


RichUtils.toggleInlineStyle doesn't work when using Chinese IME

Do you want to request a feature or report a bug?
bug
What is the current behavior?
here is the official example

this issue exists in version 0.11.0, using chrome

Did you solve this issue? I just found toggleInlineStyle useless in IME because DraftEditoris keeping trigger onChange event when IME is composition

Did you solve this issue? I just found toggleInlineStyle useless in IME because DraftEditoris keeping trigger onChange event when IME is composition

nope, I just use Quill instead of it

any update on this issue?


Reboot to recovery causes loop

Using the reboot to recovery option works as expected, but upon rebooting to system from TWRP, the phone only reboots back into recovery. The only way to solve this is to recover the Para partition from a previous backup (thankfully I had one). No other combination of wiping and resetting fixed the issue.
It's a minor QoL feature, but i'd really love to use the recovery option in the power menu. The app is fantastic aside from this issue.
Running modified stock firmware android 11 on Daoqin f21 pro. Rooted and using the lsposed module.
Other details, may/may not be relevant: The factory power menu is a simple power off option and nothing else (i'm using an intent from a gesture navigation app to access the native android 11 power menu). The device has no physical volume keys and a very particular key combo for launching TWRP at boot.

The reboot recovery option simply calls the system, it has no control over anything beyond that point. This isn't a CPM bug, but a bug in your firmware.

Understandable. Thanks for pointing to the relevant code, might help me out. Thankyou
On 15 September 2023 1:17:42 pm AEST, Kieron Quinn @.***> wrote:

The reboot recovery option simply calls the system, it has no control over anything beyond that point. This isn't a CPM bug, but a bug in your firmware.
--
Reply to this email directly or view it on GitHub:
https://github.com/KieronQuinn/ClassicPowerMenu/issues/121#issuecomment-1720426373
You are receiving this because you authored the thread.
Message ID: @.***>


Updating ci test scripts to run tests related to the change

This has ci now only run tests related to the change. However, if some critical files are changed it will run all the tests.

Results for minikube_jjb

Test
Result
Retries
Duration (HH:MM:SS)

test_backpack
Pass
1
00:01:48

test_ycsb
Pass
1
00:02:19

test_fiod
Pass
0
00:09:17

test_fs_drift
Pass
0
00:05:41

test_smallfile
Pass
0
00:06:50

test_pgbench
Pass
0
00:02:21

test_iperf3
Pass
0
00:03:43

test_sysbench
Pass
0
00:01:35

test_uperf
Pass
0
00:19:30

test_byowl
Pass
0
00:01:23

test_hammerdb
Pass
0
00:03:48

Results for kni_jjb

Test
Result
Retries
Duration (HH:MM:SS)

test_backpack
Pass
0
00:06:05

test_ycsb
Pass
1
00:06:42

test_fiod
Pass
0
00:14:57

test_fs_drift
Pass
0
00:06:20

test_smallfile
Pass
0
00:07:24

test_pgbench
Pass
0
00:02:15

test_iperf3
Pass
0
00:04:13

test_sysbench
Pass
0
00:01:47

test_uperf
Pass
0
00:18:47

test_byowl
Pass
0
00:02:19

test_hammerdb
Pass
0
00:03:58

Results for crc_jjb

Test
Result
Retries
Duration (HH:MM:SS)

test_backpack
Fail
3
00:22:28

test_ycsb
Fail
3
00:22:28

test_fiod
Fail
3
00:22:28

/rerun crc

Results for crc_jjb

Test
Result
Retries
Duration (HH:MM:SS)

/rerun crc

Results for

Test
Result
Retries
Duration (HH:MM:SS)

Results for crc_jjb

Test
Result
Retries
Duration (HH:MM:SS)

Results for crc_jjb

Test
Result
Retries
Duration (HH:MM:SS)

Results for crc_jjb

Test
Result
Retries
Duration (HH:MM:SS)

Results for crc_jjb

Test
Result
Retries
Duration (HH:MM:SS)

Results for crc_jjb

Test
Result
Retries
Duration (HH:MM:SS)

Results for crc_jjb

Test
Result
Retries
Duration (HH:MM:SS)

Results for crc_jjb

Test
Result
Retries
Duration (HH:MM:SS)

Results for crc_jjb

Test
Result
Retries
Duration (HH:MM:SS)

Results for crc_jjb

Test
Result
Retries
Duration (HH:MM:SS)

Results for crc_jjb

Test
Result
Retries
Duration (HH:MM:SS)

Results for crc_jjb

Test
Result
Retries
Duration (HH:MM:SS)

/rerun crc

Results for crc_jjb

Test
Result
Retries
Duration (HH:MM:SS)

test_backpack
Pass
0
00:01:31

test_ycsb
Pass
0
00:02:03

test_fiod
Pass
0
00:09:55

test_fs_drift
Pass
0
00:04:36

test_smallfile
Pass
0
00:05:50

test_pgbench
Pass
1
00:03:14

test_iperf3
Pass
0
00:03:32

test_sysbench
Pass
0
00:01:17

test_uperf
Pass
0
00:17:11

test_byowl
Pass
0
00:01:05

test_hammerdb
Pass
0
00:04:49

Results for crc_jjb

Test
Result
Retries
Duration (HH:MM:SS)

test_backpack
Pass
1
00:01:33

test_byowl
Pass
0
00:02:04

test_fiod
Pass
0
00:08:29

test_fs_drift
Pass
0
00:04:50

test_hammerdb
Pass
0
00:03:38

test_iperf3
Pass
0
00:03:26

test_pgbench
Pass
0
00:01:47

test_smallfile
Pass
0
00:05:43

test_sysbench
Pass
0
00:01:44

test_uperf
Pass
0
00:18:30

test_ycsb
Pass
0
00:01:58

Results for minikube_jjb

Test
Result
Retries
Duration (HH:MM:SS)

test_backpack
Pass
0
00:01:58

test_byowl
Pass
0
00:01:44

test_fiod
Pass
0
00:09:09

test_fs_drift
Pass
0
00:05:50

test_hammerdb
Pass
0
00:04:06

test_iperf3
Pass
0
00:03:58

test_pgbench
Pass
0
00:02:27

test_smallfile
Pass
0
00:06:09

test_sysbench
Pass
0
00:01:35

test_uperf
Pass
0
00:20:30

test_ycsb
Pass
0
00:01:59

Results for kni_jjb

Test
Result
Retries
Duration (HH:MM:SS)

test_backpack
Pass
0
00:04:27

test_byowl
Pass
0
00:04:15

test_fiod
Pass
0
00:15:38

test_fs_drift
Pass
0
00:06:11

test_hammerdb
Pass
0
00:05:34

test_iperf3
Pass
0
00:05:24

test_pgbench
Pass
0
00:03:52

test_smallfile
Pass
2
00:19:56

test_sysbench
Pass
0
00:02:44

test_uperf
Pass
0
00:24:20

test_ycsb
Pass
0
00:07:21


Can the horizontal scroll bar for beadplots be placed at the top?

Horizontal scroll does not respond to two-finger swipe on trackpad

Can we try inserting the scrollbar between the time axis SVG and beadplot SVG please?

Setting overflow-y: hidden hides the scrollbar at the bottom. But the div element / beadplot isn't scrollable anymore. An alternative approach would be to keep overflow-y: scroll and use --webkit to modify just the horizontal scrollbar. The issue with this is that it would only work for Safari and Google Chrome, but not Firefox. Firefox does not allow for customization of just the horizontal scrollbar. However, in all browsers, we can hide both the horizontal scrollbar at the bottom of the beadplot and the vertical scrollbar.
A potential fix in this case would be to hide both the horizontal scrollbar at the bottom of the beadplot and the vertical scrollbar. Then create a separate div element for the vertical scrollbar.

Close upon testing PR #354


Add and fix links required by Apache Podling Website Check

The check results for the current content are here:
https://whimsy.apache.org/pods/project/nuttx
We had license, but it seems we had the wrong link text.
Signed-off-by: Brennan Ashton<EMAIL_ADDRESS>

@btashton @huahang should we generate the content again?

Ideally when this goes into master a CI would pick it up and run the publish script.  Personally I think the commiter who merges to master should publish directly or ask another commiter to do it if they don't know how/can't.   The extra PR of the static content seems redundant.

@liuguo09, please help add a jenkins job to run pushlish.sh script and push the result to asf-site automatically.

@xiaoxiang781216 in the meantime I don't mind being the CI bot only running the publish.sh script. (did it for this one)


Make all client side event handlers async

As a follow up to this https://github.com/aspnet/SignalR/issues/546#issuecomment-307428228, we should make Connected and Closed async

Addressed in: https://github.com/aspnet/SignalR/pull/610


Permissions

There is nowhere stated what and if application permissions are required for the connector.

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

ID: fec9b8b8-5003-1234-48f9-a257b82865b7
Version Independent ID: 5fa3334a-4a32-e318-faea-83ebdb840fc3
Content: Copy and transform data from Microsoft 365 (Office 365) - Azure Data Factory & Azure Synapse
Content Source: articles/data-factory/connector-office-365.md
Service: data-factory
Sub-service: data-movement
GitHub Login: @jianleishen
Microsoft Alias: jianleishen

@chschulsie
Thanks for your feedback! We will investigate and update as appropriate.

@chschulsie
The Office 365 connector in Azure Data Factory requires the following permissions:

Delegated permissions to read and write user files and metadata in OneDrive for Business and SharePoint Online. These permissions are required to access and transfer data between Office 365 and Azure Data Factory.

Application permissions to read and write to the Microsoft Graph API. These permissions are required to authenticate the connector and access the Office 365 APIs.

Thanks for the feedback, but I'm not sure if the answer is complete..
ad 1) As this is a non-interactive scenario, how would you implement delegated permissions here? I assume application permissions are required...
ad 2) "Application permissions to read and write to the Microsoft Graph API" could be everything. Can you provide the exact scopes that are required (e.g. Application.Read.All, etc...)

@chschulsie
You are correct that delegated permissions are not applicable in a non-interactive scenario, and application permissions are required for the Office 365 connector in Azure Data Factory.
Regarding the specific application permissions required to read and write to the Microsoft Graph API, the following permissions are required:
Files.Read.All
Files.ReadWrite.All
Sites.Read.All
Sites.ReadWrite.All

Alright, thanks. We can close this then.


Added compute.CreateInstance.

This method isn't being used yet, but will be in following PRs.

Codecov Report

Merging #70 into master will increase coverage by 0.09%.
The diff coverage is 91.3%.

@@            Coverage Diff             @@
##           master      #70      +/-   ##
==========================================
+ Coverage   77.95%   78.05%   +0.09%
==========================================
  Files          21       21
  Lines        1488     1499      +11
==========================================
+ Hits         1160     1170      +10
- Misses        244      245       +1
  Partials       84       84

Impacted Files
Coverage Δ

daisy/compute/compute.go
77.43% <91.3%> (+1.34%)
:arrow_up:

daisy/workflow/step.go
91.95% <0%> (-1.15%)
:arrow_down:

Continue to review full report at Codecov.

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


pkg/frontend_server/test/frontend_server_test fails on dart2js bots

Failures(Timeout and RuntimeError) need to be investigated.
The test was added(moved from pkg/vm) in https://dart.googlesource.com/sdk/+/13fbf569f666e5da17e6dbe05563a95e220e7f9d#.
Example of a failure: https://ci.chromium.org/p/dart/builders/ci.sandbox/dart2js-strong-hostasserts-linux-ia32-d8/6394

cc @jonahwilliams


Fixes component spec tests

Removes the expect import from the spec files, since those import
NgMatchers which only contain Angular specific jasmine matchers.
However the current tests just use standard jasmine matchers.

Currently, the expect import leads to importing NgMatchers (https://angular.io/docs/ts/latest/api/testing/NgMatchers-interface.html), which defines the following Angular specific jasmine matchers:

not
toBeAnInstanceOf
toBePromise
toContainError
toHaveCssClass
toHaveCssStyle
toHaveText
toImplement
toMatchPattern
toThrowErrorWith

Some of those are not yet documented in the API documentation (see above link).
Since those matchers are Angular specific and do not cover all of the currently used jasmine matchers (which makes sense, since they only provide angular specifics) i propose to remove the import and work with the default jasmine matchers.
Greetings
Dope

NgMatchers interface extends jasmine.Matchers, not replacing it.

@htdt Thank you for the hint!
In that case this is an issue of my Editor. I only stumbled across this, since SublimeText (plus tslint) annotated the jasmine Matchers and threw an error like NgMatchers does not contain a property toEqual.
This pull request can be abandoned then.
Greetings
Dope

also got this issue, was solved this way


iotdb logs to console by default

Whenever I use iotdb, I see objects logged to the console. This is useful for debugging, but it would be nice to be able to turn it off. Is there a way to do this now?

Try (new function) _.logger.silent(). Blog post https://iotdb.org/social/imadeit/post/142404844631/changes-to-iotdb-logging


add json5 macro for value construction

It would be useful to have a macro for constructing values with json5 syntax, in the style of https://docs.rs/serde_json/1.0.33/serde_json/macro.json.html

It certainly would! Thanks for the idea :)


Add issue title here

File: automata/symbol_embedding/builders.py
FIXME - This class is still in an experimental state

Automatabot test


Avalonia Web not support CJK. How can i fix this?

Korean is printed normally on platforms other than browsers, but Korean is broken in browsers.
Do I need to add a Korean font separately?
What do you need to do to fix this part?

Yes, you need to include your fonts. As browser API doesn't really tell enough information about system fonts, so empty canvas-rendered web app will have a basic monospaced font.
See https://github.com/AvaloniaUI/Avalonia/issues/8938
And https://docs.avaloniaui.net/docs/getting-started/assets#referencing-assets

https://github.com/AvaloniaUI/Avalonia/issues/7037#issuecomment-981521743


Docs: The Start Now button in the header is overlapping with the search button on mobile

CC: @GreenMachine01 @mulygottlieb

This bug fixed has been addressed in #323.


Fix/masthead layout fixes

Related Ticket(s)
#781 #782
Description
Masthead platform name, if it exists, is now hidden in mobile views and will appear in the sidenav instead.
Changelog
Changed

Masthead platform name hidden in mobile view and appears in sidenav instead
In mobile breakpoints (md) the sidenav is now 100% wide and covers search/profile buttons
LocaleModal region buttons now scroll if viewport is too short

Looking great. Is it possible to keep the L0 border-bottom when the menu opens? It currently disappears so there is nothing visually separating: