ion-item-sliding class active-options-left/right is not always applied leading into buttons not being rendered

Ionic version:  (check one with "x")
[ ] 1.x (For Ionic 1.x issues, please use https://github.com/ionic-team/ionic-v1)
[ ] 2.x
[x] 3.x
I'm submitting a ...  (check one with "x")
[x] bug report
[ ] feature request
[ ] support request => Please do not submit support requests here, use one of these channels: https://forum.ionicframework.com/ or http://ionicworldwide.herokuapp.com/
Current behavior:
Sliding ion-options sometimes does not show buttons but empty space. Sliding the item back and forth a bit shows the buttons.

Expected behavior:
Sliding ion-options should always display the buttons underneath.

Steps to reproduce:
My exact case is a virtual scroll list that renders custom components that wrap an ion-item-sliding but should be reproducible in simpler examples.
In a list rendering ion-item-sliding slide the item left or right in a slow device or using chrome dev tools CPU throttling (seems to be a race condition of some kind).
Some times buttons will appear, some times a white area will appear instead of the buttons until you
nudge the item again a bit.
When buttons appear DOM looks like

When buttons do not appear DOM looks like:

Notice that in the second case the class active-options-left is missing, although active-slide is present
Other information:
Have tested this in 3.1.0, 3.3.0 and latest nightly and consistently happens across all.
Ionic info: (run ionic info from a terminal/cmd prompt and paste output below):
global packages:

    @ionic/cli-utils : 1.3.0
    Cordova CLI      : 7.0.1
    Ionic CLI        : 3.3.0

local packages:

    @ionic/app-scripts              : 1.3.7
    @ionic/cli-plugin-cordova       : 1.3.0
    @ionic/cli-plugin-ionic-angular : 1.3.0
    Cordova Platforms               : android 6.2.3
    Ionic Framework                 : ionic-angular 3.3.0-201706052245

System:

    Node       : v7.10.0
    OS         : macOS Sierra
    Xcode      : Xcode 8.3.3 Build version 8E3004b
    ios-deploy : not installed
    ios-sim    : not installed

Note: a similar issue had been filed for an older version of Ionic but was closed due to lack of reporter feedback. I have commented both on the closed issue, but opened a new updated issue, so this doesn't fall between the cracks.

Ahh, interesting find! Unfortunately, i have not been able to reproduce this issue, would you mind sharing a minimal repo we could use to reproduce this?

I will give it a try, but not sure I will be able to make a repo as complex as the actual case.
Interesting fact, in my repo I see these warning in the console when sliding an item with x20 CPU slowdown:
[Violation] Added non-passive event listener to a scroll-blocking 'touchmove' event. Consider marking event handler as 'passive' to make the page more responsive.
item-sliding-gesture.js:90

Ignored attempt to cancel a touchend event with cancelable=false, for example because scrolling is in progress and cannot be interrupted.
ItemSlidingGesture.onDragEnd @ item-sliding-gesture.js:90
PanGesture.pointerUp @ pan-gesture.js:141
PointerEvents.handleTouchEnd @ pointer-events.js:86
platform.js:633

[Violation] Added non-passive event listener to a scroll-blocking 'touchmove' event. Consider marking event handler as 'passive' to make the page more responsive.
pan-gesture.js:113 [Violation] Handling of 'touchmove' input event was delayed for 110 ms due to main thread being busy. Consider marking event handler as 'passive' to make the page more responsive.
item-sliding-gesture.js:90

Ignored attempt to cancel a touchend event with cancelable=false, for example because scrolling is in progress and cannot be interrupted.
ItemSlidingGesture.onDragEnd @ item-sliding-gesture.js:90
PanGesture.pointerUp @ pan-gesture.js:141
PointerEvents.handleTouchEnd @ pointer-events.js:86
platform.js:633

[Violation] Added non-passive event listener to a scroll-blocking 'touchmove' event. Consider marking event handler as 'passive' to make the page more responsive.

Whereas in a simplistic repo trying to reproduce this I only see:
[Violation] Added non-passive event listener to a scroll-blocking 'touchmove' event. Consider marking event handler as 'passive' to make the page more responsive.

If I remove the CPU slowdown both repos show only the violation warning once per slide.

OK I managed to reproduce it in the ionic repo tests.
I created a branch on my fork with a few small modifications to the sliding-item virtual scroll test until the issue was reproduced.
Take a look here
https://github.com/masimplo/ionic/tree/feature/virtualscroll-sliding-item
or just get the patch
https://github.com/masimplo/ionic/commit/ac960e369d8d7cfc42e0e5d81b02f520f52e8d72.patch
I also made a video demonstrating the issue in this repo

@jgw96 are you still not able to reproduce this or just didn't get the chance to update this issue?

Hey @masimplo , Sorry have been very busy with getting the latest release ready (: Would you be able to try the latest nightly and see if you can still reproduce this issue? It seems to be working fine for me (:

@jgw96 I know you guys are all over the place these days, but are doing a great job on the latest releases!
Unfortunately, the issue is still happening even in nightly. Don't understand how you are not able to reproduce it. I have tried the repo in 3-4 different machines (and a bunch of phones) and is happening every single time. Did you try to enable CPU throttling in chrome as in faster machines is harder to reproduce without it.
I updated the branch of my ionic-fork with the latest version from master and made a little screencast demonstrating the issue. Please have a look again.
Fork to clone and try: https://github.com/masimplo/ionic/tree/feature/virtualscroll-sliding-item
zip here
To run the example test run the sliding-item virtual scroll tests as usual gulp e2e.watch --folder virtual-scroll/sliding-item
and here is the screencast

@manucorporat this issue is happening on Ionic 2.x can we expect a fix for it as well?

it works after i use:
ion-item-sliding.active-slide ion-item-options[side=left] {
visibility: visible;
}


Updated documentation

What's Changing
Updated documentation and added LICENSE file.
Fixes #72
Change Type

[x] documentation
[ ] patch
[ ] minor
[ ] major

This is useful 😃

:rocket: PR was released in v2.2.1 :rocket:


No Passive Mob or Wandering Trader is Spawning

I tried everything but nothing seems to work

Pretty sure this isn't an issue with this mod. Make sure your creature mob cap isn't full and your spawn area is in a good biome. Passive mobs try to spawn 400x less often than hostile mobs and their mobcap is 7 times smaller, so getting them to spawn needs knowledge of their spawn mechanics. Maybe test in a creative world.

I tried it in multiple Creative Worlds, multiple altitudes and bioms. I don't get it to work in the skyblock worlds

Hmm. I just created a new world in both 1.19-4.1.3 and 1.19.2-4.1.3, used /fill to create a grass platform and cows, sheep, chickens etc spawned immediately. What version of Minecraft and the mod are you on and how are you testing?

Well, I'm testing the same way with version 19.2-4.1.3 and the /fill command. But I now tested with just carpet mod and without the Add-on and it's not working either so it must be something with carpet. Ofc I tested it without any mods too and it worked...

After installing a older version of carpet it worked flawless.

Maybe submit an issue to the Carpet mod then. Thanks for reporting.


update linux test results based on the command line scripts branch

I couldn't get the Linux build to run just on patch (given the CMakeLists changes) so I ran it on Command_line_script. Please make sure these are the expected results based on changes since March.

Build passes with latest push: https://travis-ci.org/github/NREL/SAM/builds/685741708 this merges to Command_line_script, so it should be safe to merge.


update logged out nav to match pelican

The line count may look scary but it's basically a copy + paste from pelican with reactified interactions for dropdowns, etc.

👍 !!


Tox is not working anymore

Since 4694684d4032aa5daab7d0aec6e643a8338ad0fc the file test-requirements.txt does not exist, so running tox on the repository does not work anymore:
$ tox -e py38
GLOB sdist-make: /restfly/setup.py
py38 create: /restfly/.tox/py38
py38 installdeps: -rtest-requirements.txt
ERROR: invocation failed (exit code 1), logfile: /restfly/.tox/py38/log/py38-1.log
======================================================================= log start ========================================================================
ERROR: Could not open requirements file: [Errno 2] Aucun fichier ou dossier de ce type: 'test-requirements.txt'
WARNING: You are using pip version 21.3.1; however, version 22.0.2 is available.
You should consider upgrading via the '/restfly/.tox/py38/bin/python -m pip install --upgrade pip' command.

======================================================================== log end =========================================================================
ERROR: could not install deps [-rtest-requirements.txt]; v = InvocationError('/restfly/.tox/py38/bin/python -m pip install -rtest-requirements.txt', 1)
________________________________________________________________________ summary _________________________________________________________________________
ERROR:   py38: could not install deps [-rtest-requirements.txt]; v = InvocationError('/restfly/.tox/py38/bin/python -m pip install -rtest-requirements.txt', 1)

apologies for the delay in responding on this one, In light of just using github actions and "act" locally, I have stopped using tox as it simplifies my workstations.
https://github.com/nektos/act

Agree 100%.  Leaving it there was completely due to laziness.


1:1 Inter polarity with SFB and Teams

We have noticed that SFB to Teams communications only works as long as one of the Users only has SFB.
If Both Users have Teams account, but is signed out of one, interpolarity no longer works.
Example:
Works:

User A on SFB, No Teams Account. , is able to message User B on Teams.

Does Not Work:
Once User A has a Teams account, this no longer works.

User A on SFB, with Teams Closed, is no longer able to message User B on Teams, with SFB closed. (emails get sent to inbox)

User A on Teams, with SFB Closed, is no longer able to message User B on SFB, with Teams Closed (email is sent to inbox)

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

ID: 41ddf8ce-fda9-ee9d-d96a-801f9a2f66b7
Version Independent ID: 9aa5a49f-c440-95a8-83a1-9d38bdaeda39
Content: Known issues for Microsoft Teams
Content Source: Teams/Known-issues.md
Service: msteams
GitHub Login: @LolaJacobsen
Microsoft Alias: lolaj

@moore1emu - Looking into this to see how I can make the documentation better. Thank you for reporting!

@moore1emu - I created this Pull Request (PR) and am just getting sign off from the product team to make sure there isn't a configuration that we are missing that might help solve this. Let me know if it accurately reflects the issue. The PR is #293

hi @moore1emu - I found out that this is a by design since after a person is upgraded to Teams the communications go to Teams and closing teams would cause a problem for message flow. We will look for places to make this clearer in the docs but isn't really a bug that can be included in the known-issues list. Thanks for feedback on this and I will try to make it clearer.


Multiple instances of formly-form break after angular 13.2

Hello , we're using formly on our project and because of design needs we had to implement a page with multiple formly-form directives with the same form. I even found a thread about this and everything seemed to work fine until we upgraded to angular 13.
if you try to use multiple formly-form with different fields and with the same form , everything works fine except for the custom validations (not the one from TO) . it appears that they get overwritten or something because it takes in consideration only the last fields custom validation.

Angular version: 13.2.0
Formly version:  5.10.1

I can't reproduce the issue in stackblitz unfortunately because I cannot use angular 13 inside there.
This are the last versions which works with.

This is not really helping us out because the desired thing would be to have an formly-form then some html content and after that another formly-form with different fields but to be linked to the same form as the first one , any recommendations for achieving this ? would this be fixed in the future ?
Thank you for the fast reply !


rescue_from :all documentation fix

Addresses rescue_from :all documentation aspect of https://github.com/ruby-grape/grape/issues/1713

Merged, thank you!


deps: bump @camunda/form-linting

Proposed Changes

This version fixes the C7 form-js mapping (https://github.com/camunda/form-linting/pull/111) and bumps some deps
Checklist
To ensure you provided everything we need to look at your PR:

[ ] Brief textual description of the changes present
[ ] Visual demo attached
[ ] Steps to try out present, i.e. using the @bpmn-io/sr tool
[ ] Related issue linked via Closes {LINK_TO_ISSUE} or Related to {LINK_TO_ISSUE}

I am adding Closes... to this to close https://github.com/camunda/camunda-modeler/issues/4733


Help

PLease after importing the requirements, I run the run.py but I get downloaded megabytes then indexes documents but the parsing XML and other results doesn't not exists. Should I add some codes or do something else?

File "C:\User\nin\desktop\python-searchengine-master\run.py", line 25, in
index = index_documents(load_documents(), Index())
File "C:\User\nin\desktop\python-searchengine-master\search\timing.py", line 21, in timed
result = method(*args, **kwargs)
File "C:\User\nin\desktop\python-searchengine-master\run.py", line 12, in index_documents
for i, document in enumerate(documents):
File "C:\User\nin\desktop\python-searchengine-master\load.py", line 11, in load_documents
for _, element in etree.iterparse(f, events=('end',), tag='doc'):

I ran into a similar issue with etree with Python 3.10. Installing Python 3.8.13, creating the virtual environment, and running through the installation resolved it for me.


Scrolling drop down 'year'

Is there a way to have the drop down for the year to be scrollable?

I can only select five years in the past and in the future on Safari.

Did you increase selectYears?

I had selectYears=true. Good pointer, that it can be a number. Now it's scrolling!
I'm using a Deform widget in my project, which is incorporating the settings like this:
class BirthdateField(colander.SchemaNode):
    oid = "birthdate"
    schema_type = colander.Date
    widget = deform.widget.DateInputWidget(
        options={'selectMonths': True,
                'formatSubmit': "yyyy-mm-dd",
                'selectYears': 200,
                'format': 'yyyy-mm-dd'}
    )


We need to call C.rte_pause() from asm, not from C

Can you explain, why? And which asm code do you mean?


@Controllers cannot use Guards as it throws a Not found module error

Describe the bug
When using Controllers, adding any guard in a @UseGuards of either a class scope or a method scope gives this error :
Error: Not found module for InteractionsGateway class
    at InstantiationService.getHostModule (<project path>/node_modules/.pnpm/@discord-nestjs+core@3.0.6_650a03e96f43d1bb974a6fd03a710d01/node_modules/@discord-nestjs/core/src/services/instantiation.service.ts:19:13)
    at GuardResolver.<anonymous> (<project path>/node_modules/.pnpm/@discord-nestjs+core@3.0.6_650a03e96f43d1bb974a6fd03a710d01/node_modules/@discord-nestjs/core/src/resolvers/guard/guard.resolver.ts:48:50)
    at Generator.next (<anonymous>)
    at <project path>/node_modules/.pnpm/@discord-nestjs+core@3.0.6_650a03e96f43d1bb974a6fd03a710d01/node_modules/@discord-nestjs/core/dist/resolvers/guard/guard.resolver.js:17:71
    at new Promise (<anonymous>)
    at __awaiter (<project path>/node_modules/.pnpm/@discord-nestjs+core@3.0.6_650a03e96f43d1bb974a6fd03a710d01/node_modules/@discord-nestjs/core/dist/resolvers/guard/guard.resolver.js:13:12)
    at GuardResolver.resolve (<project path>/node_modules/.pnpm/@discord-nestjs+core@3.0.6_650a03e96f43d1bb974a6fd03a710d01/node_modules/@discord-nestjs/core/dist/resolvers/guard/guard.resolver.js:62:16)
    at DiscordResolverService.<anonymous> (<project path>/node_modules/.pnpm/@discord-nestjs+core@3.0.6_650a03e96f43d1bb974a6fd03a710d01/node_modules/@discord-nestjs/core/src/services/discord-resolver.service.ts:97:36)
    at Generator.next (<anonymous>)
    at fulfilled (<project path>/node_modules/.pnpm/@discord-nestjs+core@3.0.6_650a03e96f43d1bb974a6fd03a710d01/node_modules/@discord-nestjs/core/dist/services/discord-resolver.service.js:14:58)

To Reproduce
Create a Gateway / controller with such kind of setup :
import { UseGuards } from "@discord-nestjs/core";
import { Controller } from "@nestjs/common";
import { RandomGuard } from "./my-random.guard";

@Controller()
@UseGuards(RandomGuard)
export class InteractionsGateway {}

and you should see the issue.
Note that a Guard is needed in the parameters of @UseGuards, as an empty argument (@UseGuards()) will still work.
Expected behavior
Controllers work like they used to in versions < 3.
Version
3.0.6
Additional context
A workaround is to not create Controller (and adding those controllers to the controllers property of any module) and instead use @Injectable and add the gateway to the providers list of any module. This makes the gateway work and guards are also applied.

Hi! I added potential fix in version 3.0.7

Well, that was much faster than I anticipated, thanks :D
Version 3.0.7 seems to indeed fix this issue, thanks!


Broken link at Configure Liveness, Readiness and Startup Probes page

Link at https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes/#define-a-liveness-http-request it's broken
The link at

You can see the source code for the server in server.go

Points to https://github.com/kubernetes/kubernetes/blob/main/test/images/agnhost/liveness/server.go
This is due to
https://github.com/kubernetes/kubernetes/blob/{{< param "githubbranch" >}}/test/images/agnhost/liveness/server.go
is Pointing to main due to kubernetes/website is using main but kubernetes/kubernetes is still using master

PR #29311 is working on this issue to point to the correct address.


Bim demo uses outdated 3D Tileset

When you run the demo it switches to the console and displays:
The embedded glb is not aligned to a 4-byte boundary.

This was fixed in https://github.com/AnalyticalGraphicsInc/cesium/pull/6862.


Chaos symbol

http://i.imgur.com/X5GzlFx.jpg
http://archive.wizards.com/Magic/magazine/article.aspx?x=mtg/daily/feature/51
107.12. The chaos symbol is {C}. It appears on one face of the planar die used in the Planechase casual variant, as well as in abilities that refer to the results of rolling the planar die. See rule 901, "Planechase."

Implemented!


Don't merge! WIP: temporary hack to disable selinux and run the tests

Debugging: https://github.com/kairos-io/kairos/issues/2802

What this PR does / why we need it:
Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #

Relabeling was skipped:
kairos@localhost:~$ cat /run/immucore/*.log| less
...
2024-08-27T12:01:15Z WRN (conditional) Skip 'Skipping stage (if statement error: failed to run cat /proc/cmdline | grep "selinux=1"
: exit status 1)' stage name: Relabelling
...

The other PR is now merged. Closing this.


Add ability to track cursor outside of the window/scope

Record the cursor position when it is outside the window/scope bounds so sliders don't abruptly stop moving if they go out of focus while still being tracked.

Seems that setPointerCapture can solve this on Web. Need to figure out the best way to handle this on Desktop

Here's the web-sys equivalent https://rustwasm.github.io/wasm-bindgen/api/web_sys/struct.Element.html#method.set_pointer_capture


Auto-mocking classes doesn't work in browser mode

Describe the bug
Apologies if this is by design, but I couldn't find anywhere that confirms this.
When mocking a module that exports a Class, the expectation is that without passing a factory, that all exports (including the exported Class are automocked).
This seems to work as expected with --environment=jsdom, but when used in --browser=chrome it fails with:
TypeError: Class constructor <name of class> cannot be invoked without 'new'

The error in browser mode can be avoided by supplying a factory to the mock function, e.g. instead of:
vi.mock("./foo.js");

we can pass:
vi.mock("./foo.js", () => {
  return {
    Foo: vi.fn()
  };
});

But it is unclear why this additional boilerplate is only needed in browser mode?
Reproduction
https://github.com/scottohara/vitest-browser-automock-class
System Info
System:
    OS: macOS 15.0
    CPU: (8) arm64 Apple M1
    Memory: 88.84 MB / 16.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 20.11.1 - ~/.asdf/installs/nodejs/20.11.1/bin/node
    Yarn: 1.22.19 - ~/.asdf/installs/nodejs/20.11.1/bin/yarn
    npm: 10.5.0 - ~/.asdf/plugins/nodejs/shims/npm
    pnpm: 9.9.0 - ~/.asdf/installs/nodejs/20.11.1/bin/pnpm
  Browsers:
    Chrome: 129.0.6668.59
    Chrome Canary: 131.0.6737.0
    Safari: 18.0
  npmPackages:
    @vitest/browser: 2.1.1 => 2.1.1
    vitest: 2.1.1 => 2.1.1

Used Package Manager
npm
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
[X] The provided reproduction is a minimal reproducible example of the bug.

Spying on classes doesn't work at all: https://github.com/vitest-dev/vitest/pull/6160
Closing this as a duplicate of https://github.com/vitest-dev/vitest/issues/6104


UP ALLOW not working correctly

the full umzug version you're using  3.3.1
which storage you're using  SequelizeStorage

I run npm run umzug down -- --name 0480_create_materialized_db.ts --rerun ALLOW
and I get
Error: Validation error
if I run down and then up on that migration it works so the allow is not working correctly

It looks to be working. I think what you saw was just a confusing error from Sequelize, that umzug is unhelpfully hiding most of. Error: Validation error is the top-level message when you try to create a table which already exists. You probably have a call like await sequelize.getQueryInterface().createTable('users', ...) in your migration, and Sequelize is throwing because users already exists.
The full error will look something more like this:
Error
    at Database.<anonymous> (/Users/mmkal/src/umzug/node_modules/sequelize/src/dialects/sqlite/query.js:236:27)
    at /Users/mmkal/src/umzug/node_modules/sequelize/src/dialects/sqlite/query.js:234:50
    at new Promise (<anonymous>)
    at Query.run (/Users/mmkal/src/umzug/node_modules/sequelize/src/dialects/sqlite/query.js:234:12)
    at /Users/mmkal/src/umzug/node_modules/sequelize/src/sequelize.js:650:28
    at async SQLiteQueryInterface.insert (/Users/mmkal/src/umzug/node_modules/sequelize/src/dialects/abstract/query-interface.js:795:21)
    at async model.save (/Users/mmkal/src/umzug/node_modules/sequelize/src/model.js:4073:35)
    at async Function.create (/Users/mmkal/src/umzug/node_modules/sequelize/src/model.js:2280:12)
    at async SequelizeStorage.logMigration (/Users/mmkal/src/umzug/lib/storage/sequelize.js:56:9)
    at async /Users/mmkal/src/umzug/lib/umzug.js:153:17 {
  name: 'SequelizeUniqueConstraintError',
  errors: [
    ValidationErrorItem {
      message: 'name must be unique',
      type: 'unique violation',
      path: 'name',
      value: '2020.11.24T16.52.04.users-table.ts',
      origin: 'DB',
      instance: [migration_meta],
      validatorKey: 'not_unique',
      validatorName: null,
      validatorArgs: []
    }
  ],
  parent: [Error: SQLITE_CONSTRAINT_PRIMARYKEY: UNIQUE constraint failed: migration_meta.name] {
    errno: 1555,
    code: 'SQLITE_CONSTRAINT_PRIMARYKEY',
    sql: 'INSERT INTO `migration_meta` (`name`) VALUES ($1);'
  },
  original: [Error: SQLITE_CONSTRAINT_PRIMARYKEY: UNIQUE constraint failed: migration_meta.name] {
    errno: 1555,
    code: 'SQLITE_CONSTRAINT_PRIMARYKEY',
    sql: 'INSERT INTO `migration_meta` (`name`) VALUES ($1);'
  },
  fields: [ 'name' ],
  sql: 'INSERT INTO `migration_meta` (`name`) VALUES ($1);'
}

So, I'll close this, but feel free to watch for a fix to #619. Or if you think there's still something wrong, please open a new issue with a repro, or a test which showcases the problem. The existing rerun tests are a good reference point.


MAAP onboarding guide

This PR is for the new onboarding doc: https://github.com/MAAP-Project/maap-documentation/blob/getting-started/docs/source/getting_started.ipynb
@gchang @abarciauskas-bgse  I wanted to include the following text regarding the approval process, but wasn't sure if we had a support email. Is there an email address we can use here?

At this point, a MAAP administrator will approve your account which will grant you access to the MAAP ADE. This process typically takes 5-10 minutes. To check on the status of your pending account, contact the MAAP team at<EMAIL_ADDRESS>

Looks good, however, if someone followed the doc verbatim today, they would end up on the pilot ops site (but registering on Ops URS, which wouldn't work). I think we can release the doc today with it pointing to "*.ops.maap-project.org" ade and repo link, noting that this is temporary for now and update the docs later when we migrate hostnames.

The changes are good! @spa0002 any issues, stylistic or otherwise, with integrating it into readthedocs?
Also with the email, @abarciauskas-bgse, can we set up a<EMAIL_ADDRESS>email and forward it to multiple people?


(PUP-10322) Update facterng feature flag not to use Kernel.require

Initially the require method was written explicitly from Kernel to mock directly the Kernel module.
Set mock to Puppet::Settings::BooleanSetting, because Kernel did not get mocked when running beaker tests.

jenkins please test this,puppet-agent

CLA signed by all contributors.

The ticket referenced above is closed, is this the right ticket number?

The ticket referenced above is closed, is this the right ticket number?

It was caused by that ticket. I did not expect to have acceptance tests failed.
Should I create a new one?

ah, in that case, I would expect the PUP ticket to be reopened, and put into Ready for CI, and only moved to Resolved after the code has passed CI.

Could you add the summary to the git commit itself? Also I didn't follow why the change to require is necessary? How did the old code make beaker acceptance tests fail?

Sure, I'll update the commit message.
I did not have a chance to look at it in depth. The only difference I could spot was that it was running an on ruby 2.4.0, but I'll try to reproduce it locally and find out what is actually happening.

Ah, I think this explains it: https://stackoverflow.com/a/57236134. Calling Kernel.require doesn't search gems due to the way rubygems monkeypatches require.


Private notifications

Hi,
Could you implement Private Notifications, to be able to hide sender and/or message content please?

Sure. How would this mode be set or triggered, in your mind?

Do you mean for the phone lock screen?
On July 16, 2015 8:39:33 AM PDT, Eric Mourougandy<EMAIL_ADDRESS>wrote:

Hi,
Could you implement Private Notifications, to be able to hide sender
and/or message content please?

Reply to this email directly or view it on GitHub:
https://github.com/guardianproject/ChatSecureAndroid/issues/696

It's at user discretion in settings. Just a checkbox to set Private Notifications on (can be 2 checkboxes for sender and message).
Not for the phone lockscreen, but for regular notification.


better on-tag workflow

I'm dissatisfied that tagging causes a full rebuild of the container.
Solution:

build master branch with a "commit-xxx" suffix
on tag, check the commit of the tag, and see if there is an existing commit-xxx tag
if so, just re-tag that with the new version tags
if not, then fine let's do a full rebuild. This should only happen if

we've committed to something that doesn't kick off a master build
or if a master build is in-progress.

I'd like to be able to check for an in-progress build, but I'm not sure that's a real feature of actions

another option is to check the ref of :master label org.opencontainer.image.revision which is injected thanks to the docker/metadata-action@v5 action
if the tag's ref and the label match, then we simply invoke skopeo to add tags to :master
if not a match, then do a full rebuild

if we get caching enabled, this is a non-issue.

ultimately this is a non-issue. I'm focusing very hard on trying to be nice to github's infrastructure, and I genuinely think nobody really cares about saving that tiny fraction of a download in this day and age. I'm just going to close this out.


Adding a label to the month navigation buttons

Improves accessibility and facilitates custom localisation by having a default value for the month navigation.

Thanks, looks good!

Just a heads up, due to the default text on this prop, we started seeing the following after the upgrade to 1.6:

Setting previousMonthButtonLabel and nextMonthButtonLabel to be empty strings will solve it, but wondering if this should be an optional prop.

Yeah I was confused when I saw the labels, came here to find out why XD


KEP: 2170: Adding cel validations on TrainingRuntime/ClusterTrainingRuntime CRDs

What this PR does / why we need it:
Add cel validations on runtime crds for v2 apis
Which issue(s) this PR fixes (optional, in Fixes #<issue number>, #<issue number>, ... format, will close the issue(s) when PR gets merged):
Fixes #
Checklist:

[ ] Docs included if any changes are user facing

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

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

Totals

Change from base Build<PHONE_NUMBER>2:
0.0%

Covered Lines:
77

Relevant Lines:
77

💛  - Coveralls

Fixes: https://github.com/kubeflow/training-operator/issues/2219


Demo network gets created on express startup if needed.

Accessible at '/document/demo'
General information
Associated issues: #213
Checklist
Author:

[ ] One or more reviewers have been assigned.
[ ] Automated tests have been included in this pull request, if possible, for the new feature(s) or bug fix.
[ ] The associated GitHub issues are included (above).
[ ] Notes have been included (below).

Reviewers:

[ ] All automated checks are passing (green check next to latest commit).
[ ] At least one reviewer has signed off on the pull request.  Reviewers have two business days to review the pull request, after which the author may merge in the pull request unilaterally.

Notes

When express starts up it first checks if there's a network document with the demo:true flag. If not it loads the sample file for GSE129943_rsem_counts_HGNC_expr.txt and sends it through the service pipeline, which creates all the necessary mongo documents for the network.
This network then becomes accessible at '/document/demo'.
The 'demo' part of the URL is sent to the server as the network ID as usual. On the server side its automatically rewritten to the actual demo network ID.
Note: it takes a minute or two for the demo network to be initially created. During this time trying to access the url is just like trying to access a network using a bogus ID, it just kicks you back to the home page.

Note this isn't ready to be merged yet, I'm still testing on dev.

If we want this to be more towards stateless, we could lazily create the doc when the /demo route is hit.

I updated the pull request description to reflect the new strategy. The code is live at dev.enrichmentmap.org.

It works well on my iPad.  I’ll take a look at the code later today.


fix(.releaserc): changer la branche de déploiement

Changement de la branche de déploiement de "master" à "production" dans le fichier release.yml.
Fixes: #14

This issue has been resolved in PR #15.

This issue has been resolved in PR #16.

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


Implement Enhanced Visuals and Messaging: Add Banner, Logo, and CTA Buttons

🔴 Note: No other files are touched except ReadMe
The following Additions are Made for better UX:

New Banner & Logo Integration: Added a visually striking banner that prominently features the company logo, boosting brand recognition.
Social Media & Website Buttons: Implemented intuitive buttons linking directly to our website, LinkedIn, and other key platforms for seamless user navigation.
Improved Messaging: Revised and sharpened the messaging to ensure it is clear, engaging, and aligned with our brand's tone and objectives.
Visual Polishing: Upgraded the overall visual design to deliver a more professional and cohesive user experience.

This update is designed to enhance our brand presence, streamline user interaction, and create a visually appealing interface that resonates with our audience.
Before:

After:

Closing as we now have a different logo


Are these still valid

Do these scripts still work now that Opt-Out at tenant level has been removed? I was trying to Opt-In at a site level and was unable to.

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

ID: 267c10c8-06a1-82b8-224e-4cea30144f0a
Version Independent ID: 1d18b823-62d1-c44b-cdb0-a326e142b487
Content: Opting out of the modern list and library experience
Content Source: docs/transform/modernize-userinterface-lists-and-libraries-optout.md
Product: sharepoint
GitHub Login: @spdevdocs
Microsoft Alias: spdevdocs

You can still opt-out of modern lists and libraries by enabling a site or web scoped feature. You mentioned opt-in...and that's not needed.
SharePoint uses modern lists and libraries by default unless you've opted out at site, web or list level.
If a list can't be shown in modern then SharePoint will automatically flip back to the classic rendering of the list


sql: no rows in result set

Summary
The indexer cannot find some block in the database.
Scope/Requirements
Trying to get information about a block.
Urgency/Relative Priority
Quite concerning.
Details
We are trying to get the block information 12508264 from our indexer and running into following problem:
$ curl -X GET -H 'Accept: application/json' 'http://<IP_ADDRESS>:8980/v2/blocks/12508264'
{"message":"error while looking up block for round '12508264': sql: no rows in result set"}

Blocks before and after have no problem:
$ curl -X GET -H 'Accept: application/json' 'http://<IP_ADDRESS>:8980/v2/blocks/12508263'
{"genesis-hash":"SGO1GKSzyE7IEPItTxCByw9x8FmnrCDexi9/cOUJOiI=","genesis-id":"testnet-v1.0","previous-block-hash":"P9cH3dzi69d/p19n/PVkjE/1Neo81+TcUi0VpGjkuS8=","rewards":{"fee-sink":"A7NMWS3NT3IUDMLVO26ULGXGIIOUQ3ND2TXSER6EBGRZNOBOUIQXHIBGDE","rewards-calculation-round":13000000,"rewards-level":26530,"rewards-pool":"7777777777777777777777777777777777777777777777777774MSJUVU","rewards-rate":40,"rewards-residue":24721287},"round":12508263,"seed":"xxbB080+OKajB/SjcDzAigL7YRAxfPX/3tni9RfiGb4=","timestamp":1614013779,"transactions":[{"application-transaction":{"accounts":[],"application-args":["T3B0LWlu","Q2F0ZWdvcnk0","VXJsOiBFT0VJT041WUtBVlZRVUNTTkpGWjc1S1RGVFRTWkFLSUJXSjUzMzRPVktNWE1NVzU3MjQ2TTRWMldV"],"application-id":14153564,"foreign-apps":[],"foreign-assets":[],"global-state-schema":{"num-byte-slice":0,"num-uint":0},"local-state-schema":{"num-byte-slice":0,"num-uint":0},"on-completion":"optin"},"close-rewards":0,"closing-amount":0,"confirmed-round":12508263,"fee":1000,"first-valid":12508261,"genesis-hash":"SGO1GKSzyE7IEPItTxCByw9x8FmnrCDexi9/cOUJOiI=","genesis-id":"testnet-v1.0","global-state-delta":[{"key":"SGFzaDE=","value":{"action":2,"uint":9089200827701843924}},{"key":"SGFzaDI=","value":{"action":2,"uint":8272196729362849917}},{"key":"SW5kZXg=","value":{"action":2,"uint":372}}],"id":"3ZVVPUW7O3VDONAHL5KNJ6NS44WMGTKWBXKPZ6DDCIJ4KJ7PPDZQ","intra-round-offset":0,"last-valid":12509261,"local-state-delta":[{"address":"EOEION5YKAVVQUCSNJFZ75KTFTTSZAKIBWJ5334OVKMXMMW57246M4V2WU","delta":[{"key":"QWR2ZXJ0aXNlclVybA==","value":{"action":1,"bytes":"VXJsOiBFT0VJT041WUtBVlZRVUNTTkpGWjc1S1RGVFRTWkFLSUJXSjUzMzRPVktNWE1NVzU3MjQ2TTRWMldV","uint":0}},{"key":"SW5kZXg=","value":{"action":2,"uint":372}}]}],"receiver-rewards":0,"round-time":1614013779,"sender":"EOEION5YKAVVQUCSNJFZ75KTFTTSZAKIBWJ5334OVKMXMMW57246M4V2WU","sender-rewards":0,"signature":{"sig":"5D+JQ7Ct+IYT/khtQlJowp/TjViORYMdxaTZRXqTuX4s4iu6TmDPCLZ6mDtvgF+iTFsvoSP4cFt5zVOaUE7jCQ=="},"tx-type":"appl"}],"transactions-root":"eo+yDi3E1rRkgXh2Bp36TU67pT86pHKtRFtMFPNMhzo=","txn-counter":14160944,"upgrade-state":{"current-protocol":"https://github.com/algorandfoundation/specs/tree/3a83c4c743f8b17adfd73944b4319c25722a6782","next-protocol-approvals":0,"next-protocol-switch-on":0,"next-protocol-vote-before":0},"upgrade-vote":{"upgrade-approve":false,"upgrade-delay":0}}

$ curl -X GET -H 'Accept: application/json' 'http://<IP_ADDRESS>:8980/v2/blocks/12508265'
{"genesis-hash":"SGO1GKSzyE7IEPItTxCByw9x8FmnrCDexi9/cOUJOiI=","genesis-id":"testnet-v1.0","previous-block-hash":"73FjVr21aGQPYztyM0n/XFe1b81NPAj99SJmj0NsiHA=","rewards":{"fee-sink":"A7NMWS3NT3IUDMLVO26ULGXGIIOUQ3ND2TXSER6EBGRZNOBOUIQXHIBGDE","rewards-calculation-round":13000000,"rewards-level":26530,"rewards-pool":"7777777777777777777777777777777777777777777777777774MSJUVU","rewards-rate":40,"rewards-residue":24721367},"round":12508265,"seed":"goiz1bvUT1Y+anLCe75MMM2yAVTRWB+estBSX1VajAo=","timestamp":1614013787,"transactions":[{"application-transaction":{"accounts":[],"application-args":["T3B0LWlu","Q2F0ZWdvcnk1","VXJsOiBFT0VJT041WUtBVlZRVUNTTkpGWjc1S1RGVFRTWkFLSUJXSjUzMzRPVktNWE1NVzU3MjQ2TTRWMldV"],"application-id":14153567,"foreign-apps":[],"foreign-assets":[],"global-state-schema":{"num-byte-slice":0,"num-uint":0},"local-state-schema":{"num-byte-slice":0,"num-uint":0},"on-completion":"optin"},"close-rewards":0,"closing-amount":0,"confirmed-round":12508265,"fee":1000,"first-valid":12508263,"genesis-hash":"SGO1GKSzyE7IEPItTxCByw9x8FmnrCDexi9/cOUJOiI=","genesis-id":"testnet-v1.0","global-state-delta":[{"key":"SGFzaDE=","value":{"action":2,"uint":9089200827701843924}},{"key":"SGFzaDI=","value":{"action":2,"uint":8272196729362849917}},{"key":"SW5kZXg=","value":{"action":2,"uint":372}}],"id":"7CDTEETN7HV2EP6NO43FARWJUOTDN37G6RIQZHI5A74KF6D7LHGQ","intra-round-offset":0,"last-valid":12509263,"local-state-delta":[{"address":"EOEION5YKAVVQUCSNJFZ75KTFTTSZAKIBWJ5334OVKMXMMW57246M4V2WU","delta":[{"key":"QWR2ZXJ0aXNlclVybA==","value":{"action":1,"bytes":"VXJsOiBFT0VJT041WUtBVlZRVUNTTkpGWjc1S1RGVFRTWkFLSUJXSjUzMzRPVktNWE1NVzU3MjQ2TTRWMldV","uint":0}},{"key":"SW5kZXg=","value":{"action":2,"uint":372}}]}],"receiver-rewards":0,"round-time":1614013787,"sender":"EOEION5YKAVVQUCSNJFZ75KTFTTSZAKIBWJ5334OVKMXMMW57246M4V2WU","sender-rewards":0,"signature":{"sig":"7FpKNy7D/kHswkvUEQnkY9UEbs6W5A3l9wkfmP7zqIXZAEYqzG9LSGAZfY6pHr5gfSUk9NtejbE6luU9MHcCCA=="},"tx-type":"appl"}],"transactions-root":"pjlI7Ky7qv3ej8PAw31EYVFAO1NVcLvIAzIWKs9mKMo=","txn-counter":14160946,"upgrade-state":{"current-protocol":"https://github.com/algorandfoundation/specs/tree/3a83c4c743f8b17adfd73944b4319c25722a6782","next-protocol-approvals":0,"next-protocol-switch-on":0,"next-protocol-vote-before":0},"upgrade-vote":{"upgrade-approve":false,"upgrade-delay":0}}

According to the indexer logs, the block should be imported:
Feb 22 17:09:51 localhost algorand-indexer[19976]: {"level":"info","msg":"round r=12508264 (1 txn) imported in 2.556524ms","time":"2021-02-22T17:09:51Z"}

The mentioned block has a transaction that contains a note.
Ref: https://testnet.algoexplorer.io/tx/NSFVDIEABFTYKHLOVH4CGYTCY62PQQ4L4BFJFH3X2C7XP6QUGC7Q
After checking another block it seems the problem is the same https://testnet.algoexplorer.io/tx/BZA2JZ35AQC34ALFXUHSODWG7WBWP7ST5NSYCLS25PCBC22ADWUQ
Any idea why these ones are not imported (encoding, etc)?
Running:
Debian 10
PostgreSQL: 11.10-0+deb10u1
Algorand Indexer: 2.3.0-beta2

Can you log into the db and run this query?
select round,realtime from block_header where round >= 12508263 and round <= 12508265;

I get no rows from my local indexer for that query.
Metastate is:
migration,"{""next"": 4}"
state,"{""account_round"": 12278741}"

also seeing this issue on our indexer node, different block, running the query above returns no results. Node is fully synced and indexer health endpoint looks fine
{"data":{"migration-status":"Migrations Complete"},"db-available":true,"is-migrating":false,"message":"12274832","round":12274832}

i tried querying the block/round in the ticket as well, 12508264, that returns empty as well

Could you please share which indexer version you're currently using ?

i am using indexer version 2.2.1

Algorand mainnet or another network? At the time I checked this morning mainnet wasn't up to round 12508264

mainnet, that would explain why 12508264 doesnt work (the original block in this ticket) , but I would expect 11968869to be found?

Hi @brianolson ,
forgot to mention, it is testnet.
algorand_indexer=# select round,realtime from block_header where round >=11968869 and round <=11968873;
  round   |      realtime
----------+---------------------
 11968869 | 2021-01-27 01:25:31
 11968870 | 2021-01-27 01:25:36
 11968871 | 2021-01-27 01:25:40
 11968872 | 2021-01-27 01:25:44
 11968873 | 2021-01-27 01:25:49
(5 rows)

algorand_indexer=#


[Feature Request/Bug] Enhanced Error Messages

I've got a fairly large state machine, and it works for most everything I've been doing.  However, I'm currently getting an error and am having a VERY hard time tracking down the line of code that is the culprit (again, large state machine).  If the error had some more information as to where it originated from, I think it would be way more useful.  It would be nice if it referenced the line or name of the state machine, state, or transition that is causing the error.
Here is the error that needs clarity:
StateMachineException:
Context: Running OnEnter of the state machine.
Problem: No start state is selected. The state machine needs at least one state to function properly.
Solution: Make sure that there is at least one state in the state machine before running Init() or OnEnter() by calling fsm.AddState(...).

UnityHFSM.StateMachine`3[TOwnId,TStateId,TEvent].OnEnter () (at Assets/UnityHFSM-v2.1.0/src/StateMachine/StateMachine.cs:400)
UnityHFSM.StateMachine`3[TOwnId,TStateId,TEvent].ChangeState (TStateId name, UnityHFSM.ITransitionListener listener) (at Assets/UnityHFSM-v2.1.0/src/StateMachine/StateMachine.cs:215)
UnityHFSM.StateMachine`3[TOwnId,TStateId,TEvent].OnEnter () (at Assets/UnityHFSM-v2.1.0/src/StateMachine/StateMachine.cs:386)
UnityHFSM.StateMachine`3[TOwnId,TStateId,TEvent].ChangeState (TStateId name, UnityHFSM.ITransitionListener listener) (at Assets/UnityHFSM-v2.1.0/src/StateMachine/StateMachine.cs:215)
UnityHFSM.StateMachine`3[TOwnId,TStateId,TEvent].RequestStateChange (TStateId name, System.Boolean forceInstantly, UnityHFSM.ITransitionListener listener) (at Assets/UnityHFSM-v2.1.0/src/StateMachine/StateMachine.cs:264)
UnityHFSM.StateMachine`3[TOwnId,TStateId,TEvent].TryTransition (UnityHFSM.TransitionBase`1[TStateId] transition) (at Assets/UnityHFSM-v2.1.0/src/StateMachine/StateMachine.cs:319)
UnityHFSM.StateMachine`3[TOwnId,TStateId,TEvent].TryAllDirectTransitions () (at Assets/UnityHFSM-v2.1.0/src/StateMachine/StateMachine.cs:355)
UnityHFSM.StateMachine`3[TOwnId,TStateId,TEvent].OnLogic () (at Assets/UnityHFSM-v2.1.0/src/StateMachine/StateMachine.cs:414)
Update () (at Assets/Scripts/CharacterController.cs:566)

I think I found what these were during my troubleshooting.
I am using enums instead of text fields for my states.  These errors were for the items that were marked as NONE in the enum.  I had associated a state machine with the enum when there weren't any states in the state machine.  It would still be nice to have some idea of what is being referenced in the error.  This was maddening trying to find what was wrong.
The difference between these is what got me:
climbingstatus.AddState(CharacterClimbStatus.None);
climbingstatus.AddState(CharacterClimbStatus.Move, climbingmovement);


[feat] Optimization - parse requests does not require chat context

Don't send full messages context while sending parse requests - it's a waste of resources

Related to #106


Wrong nightly guard in RawTable::data_start

There's nothing nightly specific in this function, and also data_end is not guarded.

@bors r+

:pushpin: Commit b50d9a7794bd475fbca09c2244cfec5e97ecee41 has been approved by Amanieu
It is now in the queue for this repository.

:hourglass: Testing commit b50d9a7794bd475fbca09c2244cfec5e97ecee41 with merge 57870415f4872c2dfd69ca9e38300972185d3e18...

:sunny: Test successful - checks-actions
Approved by: Amanieu
Pushing 57870415f4872c2dfd69ca9e38300972185d3e18 to master...


Rename this resource module to WebAdministrationDsc

Looking for any and all feedback on the first release of WebAdministrationDsc!

Hi Mariah,
maybe you could first explain what this is. Is it the first step of moving xWebAdministration to WebAdministration which will eventually become a part of WMF 5.x rather than a downloadable resource kit? Why did you pick those three resources over the others?
If you want some feedback, please explain what you are trying to do first.

Hi @hahndorf  - this relates to the DSC HQRM programme. All resources in the xWebAdministration kit are going to be reworked so that the meet the HQRM guidelines.
Also, there was some discussion around this in the community calls:
https://github.com/PowerShell/DscResources/blob/master/CommunityCalls/06-30-16/Notes.md#high-quality-resource-modules
https://github.com/PowerShell/DscResources/blob/master/CommunityCalls/08-03-16/Notes.md#high-quality-web-administration-partial-release
HTH

@PlagueHO - Thanks, that's helpful information.

Thank you responding @PlagueHO!  @hahndorf - the reason we chose these resources for the first release is simply because they required the least amount of work to get them to High Quality and we wanted to get a preview out as soon as possible. The rest of the resources in xWebAdministration will be updated as soon as I and the other maintainers have time. Currently xPSDesiredStateConfiguration is our top priority.

But any feedback on these resources is of course still welcomed and encouraged

This issue should be refocused to do the rename as the other resource module are renamed, the entire resource module should be renamed. This is in progress in the working branch in this repo, that branch should be pulled into a new working branch (in the fork of whomever take this on) that renames this entire resource module to WebAdministrationDsc.
I have changed the title and relabelled this issue to reflect this so that anyone in the community can run with this!


[DPE-2994] No more relational databag usage

Overview
This PR is addressing issue https://github.com/canonical/wordpress-k8s-operator/issues/163
Rationale
The Relational Databag is not to be addressed directly but only via interface functions.
Part of the relational data is now "hiding" in Juju Secrets and are not exposed on the databag anymore.
The data_platform_libs/data_interfaces DatabaseRequires and DatabaseProvies interfaces ensure transparent and safe access to all relational data. Outside of these functions, no access/manipulation of this data can be guaranteed in the future.
Module Changes
Relational Databag usage is replaced with DatabaseRequires interface calls.

The PR was merged on the base repository directly


Looks great, but ..

Let me tell you something as non developer. I am spending lot of time into Javascript OS ecosystem, and what is the biggest miss on every OS Repo is live demo link.
Is it to hard deploy app and have live working demo, which can see lot of entrepreneurs, marketing, design and other no technical people ? Which can directly impact of having your OS project getting even more exposure, PR's or paid work ?
Whatever, this is my honest and direct feedback to you and all other open source developers.
Put the Demo of your project online! .
Peace,

Demo link is at very top of page:
Full-featured photo image editor using canvas. It is really easy, and it comes with great filters. http://ui.toast.com/tui-image-editor

Thanks for that @oleteacher , I honestly didn't see that link in the Repo summary.
I was looking at table of contents and didn't find in there.


Offline Cache

I saw a prior ticket related to the Offline Cache functionality, but I am still unclear how to use this feature.  I added the following to my code
options.Connect(settings["ConnectionStrings:AppConfig"])
.SetOfflineCache(new OfflineFileCache(new OfflineFileCacheOptions
{
Path = ""
}))
It's unclear to me what SetOfflineCache is doing or if anything else needs to be done to cache configuration data locally and use the local cache when offline?  Is there a more complete example or explanation of this functionality?

@jmsalvo I apologize we are lack of documentation on this. You may have reviewed #45 already where I discussed what the API will be doing. Please note the OfflineFileCache will only work in Azure App Service currently. Since the whole idea of it is to work transparently, it will kick in automatically when your App Service application fails to connect to App Configuration at startup. You can find the encrypted cache file in App Service at $home/data/azureAppConfigCache in case you want to check whether the cache is created.

Thank you for clarifying this only presently works for Azure App Services.

Hi @fernandozago, we are evaluating how Offline Cache is used in different applications. Could you please help us understand the problem you are trying to solve by using Offline Cache?


nextcloud-notify_push: 0.6.3 -> 0.6.5

Description of changes
Didn't deploy it yet but I have planned that for later today 🤞🏼 done
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[x] Tested, as applicable:

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

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

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

[x] Fits CONTRIBUTING.md.

@Ma27 @dotlambda @RaitoBezarius since this app got bumped in 23.11 this must be backported otherwise IIRC it will complain about a version mismatch.


[xcode-install] add option to customize number of download retry attempts

Checklist

[x] I've run bundle exec rspec from the root directory to see all new and existing tests pass
[x] I've followed the fastlane code style and run bundle exec rubocop -a to ensure the code style is valid
[x] I've read the Contribution Guidelines
[x] I've updated the documentation if necessary.

Motivation and Context
Resolves https://github.com/fastlane/fastlane/discussions/17608
Description
Now that xcode-install supports customizing the number of download attempts (https://github.com/xcpretty/xcode-install/pull/400) in v2.6.7, this option can be received by fastlane and forwarded to xcode-install as well 😊
Testing Steps
To test this branch, modify your Gemfile as:
gem "fastlane", :git => "https://github.com/fastlane/fastlane.git", :branch => "rogerluan-xcode-install-download-retry-attempts"

Run this command such as: xcode_install(version: "12.1", username<EMAIL_ADDRESS>download_retry_attempts: 6)

@googlebot I consent.


Fixes Issue #3368

Fixes #3368

[x] I follow CONTRIBUTING GUIDELINE & CODE OF CONDUCT of this project.
[x] I have performed a self-review of my own code or work.
[x] I have commented my code, particularly in hard-to-understand areas.
[x] My changes generates no new warnings.
[ ] I have followed proper naming convention showed in CONTRIBUTING GUIDELINE
[x] I have added screenshot for website preview in assets/images
[ ] I have added entries for my game in main README.md
[x] I have added README.md in my folder
[ ] I have added working video of the game in README.md (optional)
[x] I have specified the respective issue number for which I have requested the new game.

![Screenshot 2024-05-17 084516](https://github.com/kunjgit/GameZone/assets/128175768/5639033c-fc9e-49f0-94f4-aebabb8f23b7)

Thank you @MohanaSrinivas ,for creating the PR and contributing to our GameZone 💗
Review team will review the PR and will reach out to you soon! 😇
Make sure that you have marked all the tasks that you are done with ✅.
Thank you for your patience! 😀

@MohanaSrinivas resolve merge conflicts


Prismic is not defined?

When adding this package, and adding the "prismic-nuxt" to modules in the nuxt-config, and then running the application using npm run dev, im getting the error:
Could not compile template C:\Websites\testPrismic\node_modules\prismic-nuxt\src\plugin.js: Prismic is not defined

@nickycdk Can you provide some more details about how you're using / installing prismic-nuxt? On a fresh install of nuxt and prismic-nuxt on v.0.2.0 I'm not getting any issues.

Hi... I'm getting this issue also :-?...
I'm not sure what I have done wrong... I just install prismic-nuxt, and add the configuration file (nuxt.config.js):
modules: [
    ['prismic-nuxt', {
      endpoint: 'https://alijaya.cdn.prismic.io/api/v2',
      linkResolver: require('./prismic/link-resolver.js'),
      htmlSerializer: require('./prismic/html-serializer.js')
    }]
  ],

and I have this error:
Error: Could not compile template /home/alijayameilio/Documents/program/alijaya-website/src/node_modules/prismi  c-nuxt/src/plugin.js: Prismic is not defined
- builder.js:471
    [src]/[nuxt]/lib/builder/builder.js:471:17

  - async Promise.all

  - builder.js:441 async Builder.generateRoutesAndFiles
    [src]/[nuxt]/lib/builder/builder.js:441:5

  - builder.js:165 async Builder.build
    [src]/[nuxt]/lib/builder/builder.js:165:5

ah my bad... updating to the latest nuxt version seems to fix it :D


BLE scanning - BT RX thread hangs on.

Describe the bug
During ble scan the BT RX thread hangs on and ble scan callback is not fired. This happens at random time after scan start.
To Reproduce
Example: bluetooth/scan_adv
west build -b nucleo_wb55rg .
scan parameters:

BT_HCI_LE_SCAN_ACTIVE
BT_LE_SCAN_OPT_NONE
interval=128  (tried with other values too)
windows=64 (tried with other values too)

Expected behavior
Scanning is going continously until manually stopped.
Impact
Hard reset has to be done to begin scanning again.
Logs and console output
As you can see below the number of cpu ticks of BT RX thread doesn't change for following threads analysis (time interval = 30s)

Environment (please complete the following information):

OS: Linux
Zephyr SDK 3.1.99
FUS v.1.2.0
ble stack: stm32wb5x_BLE_Stack_full_fw (1.12.1) on stm32wb55 nucleo
ble stack: stm32wb5x_BLE_HCILayer_extended_fw (1.13.2) on own hardware
boards: stm32wb55 nucleo, own pcb based on stm32wb55 mcu

Additional context
This issue occurs on our own hardware based on stm32wb55 mcu and on stm32wb55 nucleo board. There are different ble stacks used as mentioned in Environment section.
This issue occurs at random time (from my observations this time depends on scan parameters, when scan interval and window are bigger then it's harder to reproduce this issue).
When performing tests on scan_adv example i've commented the code part responsible for advertising. Only scanning is performed.
Also i tried to do some workaround and try to reset the bt stack when noticed that this issue occured, but there is another problem.
When i do:
(pseudocode:)
bt_le_scan_disable();
hci_command->BT_HCI_OP_RESET
bt_disable();
bt_enable();
I'm getting an assertion:

Adding this line in hci_core.c bt_enable() resolves problem with assertion.
k_work_queue_init(&bt_workq);

@erwango @fomst could you please try to reproduce this with the Zephyr Link Layer using Nordic nRF hardware?

@erwango @fomst could you please try to reproduce this with the Zephyr Link Layer using Nordic nRF hardware?

@fmost, also can you give an idea about the occurence frequency ?

@carlescufi I'm not able to do that. I've no nordic's hardware.
@erwango As i wrote this occures randomly, but most frequent this happens for low scan interval and scan window. For parameters passed in my first post this happens relatively often - after max few minutes.

@fomst Would you be able to provide a HCI trace using btmon ?
This would speed up investigation

@fomst Would you be able to reproduce the same configuration on a STM32Cube based application ?

@fomst Would you be able to provide a HCI trace using btmon ? This would speed up investigation

@erwango
Here are logs from bt_mon
ble_logs.txt

@fomst Would you be able to reproduce the same configuration on a STM32Cube based application ?

Do you mean to reproduce this without zephyr environment? Just with ST's code base?

@erwango Here are logs from bt_mon ble_logs.txt

Great, thanks

@fomst Would you be able to reproduce the same configuration on a STM32Cube based application ?

Do you mean to reproduce this without zephyr environment? Just with ST's code base?

Indeed.

@fomst Can you confirm status of CONFIG_BT_RECV_BLOCKING ?

@erwango CONFIG_BT_RECV_BLOCKING=n as the BT_RECV_WORKQ_BT is selected.
About reproducing the issue with pure ST's ble stack - i'll try to do it asap, but i've other higher priority tasks to do, so it may take some time, until i'll be back with results.

@fomst I have been trying to reproduce the issue in the conditions you describe since several hours now using Zephyr (only unknown is the SHA1 you're using). To no avail so far.

@erwango Sorry for late answer. Somehow i've missed notification.
Here is the SHA1 string: ae7f349367312dbf3f92e6aea028c0a89bb409a7.
Did you tried to reproduce this issue on the STM32 hardware, or on another one?
I still work on reproducing this issue with ST's sdk, but had not much time. Hope i'll be back with results next week.

Did you tried to reproduce this issue on the STM32 hardware, or on another one?

Was using nucleo_wb55rg.

@fomst Have you been able to make some progress in you investigation ?

Hi @erwango,
Sorry for late answer, i had other stuff to do meantime.
unfortunately no progress from my side. I've not been able to reproduce this issue on pure ST's stack.
If i'll get anything new i'll inform you asap.

@jori-nordic @alwa-nordic maybe we could try to reproduce on nRF:
To Reproduce
Example: bluetooth/scan_adv
west build -b nucleo_wb55rg .

scan parameters:

BT_HCI_LE_SCAN_ACTIVE
BT_LE_SCAN_OPT_NONE
interval=128 (tried with other values too)
windows=64 (tried with other values too)


Incorrect default value for pauseAutoplayOnHover  in documentation

pauseAutoplayOnHover prop
In documentation its default true but in package version 0.2.5 its false

I've fixed the docs, thanks for your feedback!


[PYIC-2580] Allow core front to request callback with no session id

Allow core front to call the cri callback without an ipvSessionId
Proposed changes
What changed
Middleware for cri updated to remove ipvSessionId null checks
Why did it change
Support for mobile browser app change
Issue tracking

PYIC-2580

Checklists
Environment variables or secrets

[ ] No environment variables or secrets were added or changed

Other considerations

[ ] Update README with any new instructions or tasks

I think this is overly broad. In most circumstances we still want frontend to check that we have an ipvSessionId. Perhaps we should have a way of specifying routes where the ipvSessionId check is not mandatory?

I think this is overly broad. In most circumstances we still want frontend to check that we have an ipvSessionId. Perhaps we should have a way of specifying routes where the ipvSessionId check is not mandatory?

Have limited this to only the CRI callback for now, as this seems the simplest way to achieve this


underscore and check-npm-versions not found

Two days ago my app stopped working. I get client side errors that I do not understand:

I updated all packages from npm and Atmosphere. That didn't work. I did a rollback to Meteor 1.3 (although I'm not sure the problems started after upgrading to 1.3.1). No effect.
Does anyone have any idea where this could be coming from?
I'm posting it here as the first error (underscore not found) is thrown from this package. (While the second error says this package can't be found…)
From versions:
<EMAIL_ADDRESS><EMAIL_ADDRESS>

The update to Meteor <IP_ADDRESS> (maybe in combination with other package updates) solved the problem.


Add units to angles and vectorise 'orbital_elements.py'

Fix old to-do: angles now use AMUSE units
Use trigo functions from Amuse to make angles unit-aware

Possible danger: previous default for angles was in degrees. However, unitless angles will now be seen as radians.
Possible workaround: detect unitless angles somehow, and assign units.deg to those? Is this possible/desired?
Also, some code cleanup (indents to multiples of 4, get rid of too long lines) for improved readability

another thing: I wonder if there is a vectorised routine for generating a particle set from arrays of orbital elements (maybe lucie has one?)

@ipelupessy I agree that a vectorised generation of positions and velocities from elements would be good to have. I used a loop over the orbital elements and get the position and velocity vectors from Kepler (see relative_position_and_velocity_from_orbital_elements in isotropic_cloud.py).

Thanks for the feedback. Renaming the functions would be fine. The old one can then use the new one internally, with a conversion to degrees for the angles.
I started working on a vectorised version of the binary generator - might be able to get it done tomorrow.

I've added a function that checks if an angle has a unit or not, and adds degrees if this is not the case. This is still somewhat risky, but the advantage is that now the function works as expected for legacy scripts and for scripts that use units for angles. The deprecation warning could be added to the test function, to warn against unitless usage. @ipelupessy can you add such a warning?

Regarding vectorising: this is not so difficult in principle, but there are a few issues to consider. Most importantly:
Currently (1), the output is a particleset with the two binary stars. Should it be like this for the vectorised version (e.g. an array of particlesets)? This doesn't seem very useful, as it would still require a loop at some point when using the output.
Or (2) should it be a set of primaries and a set of secondaries? These could be used directly, or they could be used to generate binary pairs.
Or (3) should should it already be a set of stars and a set of binary pairs (as needed for SeBa/BSE etc)?
The first option would be the least obtrusive, while the last two seem more useful (but they would break compatibility). I would prefer option 2, since there already is a function to convert that to option 3 and option 1 seems not truly vectorised... Maybe renaming the function is necessary after all.

By the way, is there a way to detect if the unit system is using Hénon units, SI units or generic units? It would be great if we can get rid of the "G=nbody_system.G" kwarg.

I've implemented option 2 for the generation of binaries. Should work as-is, but could use some testing.
Still need to do the reverse: vectorise generating orbital elements from binaries / list of positions and velocities.

Cool!
Just few notes: You use true anomaly as one of the input vectors. If mean anomaly is used instead (there might be cases when that is needed) one still has to go through a loop of Kepler. Also, one should be careful when using the routine to generate binaries with the same primary (e.g. particles in a disk), since each binary has different center of mass.

Yeah - still thinking about a few aspects of this.
There seems to be a "true_anomaly_from_eccentric_anomaly" function already - would this help?
Maybe it's best to split things up in a "orbital_elements_to_cartesian" function (which would return m1, m2, relative position and relative velocity) and a "cartesian_to_binary" function (which would return binaries with center-of-mass at (0,0,0)?

I think that you cannot get true or eccentric anomaly from the mean anomaly without solving Kepler's equation. As far as I know, there is no vectorized version of that in amuse (kepler_orbiters would be one of the places to look, but I didn't find it there).
I think your function is definitely useful for many cases, so I wouldn't make it more complicated. In the case the central body is the same for all binaries, there are different solutions depending on the problem (if the orbiters are zero-mass, your function can be still used; or otherwise some democratic or Jacobi coordinates might be the way, but that is beyond the scope of this function, I think).

Yeah, I think that would be beyond the scope of this function... Nonetheless, splitting it up would seem to be useful and quite straightforward.
Anyway, the function specifically asks for the (kwarg) true_anomaly, so I doubt there will confusion about that bit.

this now contains #137 ??

@ipelupessy yes. #137 was a mistake.

btw for me the tests in test/ext_tests/test_orbital_elements.py break...

Working on it ;).

I would move angle_with_unit to inside new_binary_from_orbital_elementsIts not something that should be used for anything anywhere else... (unitless numbers should always be interpreted as radians since an angle unit can always be dropped by a numerical operation; the angle_with_unit here sort of an exception for legacy reasons, moving it inside the function will prevent people from importing it!)

You're right, I'll do that.

maybe its just me who is confused;-) but: what is your plan with the "Still need to do the reverse: vectorise generating orbital elements" mentioned above?? (this is what orbital_elements_for_rel_posvel_arrays does, or are you talking about wrapping this one for various input options??)

Just checking if every function is vectorised. You're right, that one works for a number of binaries (or others) already.

One of the tests (test10) is now failing, because it is unitless. Actually, I don't want that one to be successful - AMUSE should never be unitless. Is it OK if I remove that test?

you can block it out (don't remove)...I generally try to add tests to make sure code is unit and numpy-array agnostic..

Had to transpose a few arrays to get the tests working.
They are now all OK, except where the tests expect unitless angles (tests 10 (E), 4 and 5 (F)).
Test 10 results in an error since it tries to assign a unitless value to what should be a mass. I think this should result in an error, and the test needs rewriting.
Tests 4 and 5 fail, since the script now returns angles with unit rad even if the input angles were unitless (and therefore assumed to be in deg, per the previous expected behaviour). So the values aren't equal. If this change can be made to the test somehow, it will pass. Or should the resulting angles be given in (unitless) deg in case that was the input? That would make things complicated, so it wouldn't be my choice...
I think the code is now fine by the way, so it can be merged if it checks out OK for others as well and the tests are fixed.

ok, great; can you add the tests file to the pull (with the tests that fail renamed (test10 -> xtest10 or something)?

Will do. And I'll add (a) test(s) for the new stuff I added.

I think it's ok to merge this now.

ok great! I think there is one issue left, since Lucie and other people are using the routines with deg assumed, is that the output orbital elements always have units? I think the it would be good for them  to have the old routine name keep their behaviour (with a deprecation warning). I would name the new one just orbital_elements (ie this contains all the new code, orbital_elements_from_binary call orbital_elements and strips/ converts the angle units)
maybe also ask lucie for comment?
btw: why does orbital_elements_from_binaries not call orbital_elements_for_rel_posvel_arrays? (is there a difference)?

Probably good to rename, yes.
The old functions return values with units now, but default to degrees for output and unitless input. So the behaviour is nearly the same - degrees are a pseudo unit... new functions just use units, without a specific default.
Adding a deprecation warning would be good.
Yes, the new function should be used internally - forgot to clean that up. The code is the same...
I'd welcome comments from @jilkoval!

I haven't been following all the detailed changes here, but If it's not a big trouble to keep the orbital_elements_for_rel_posvel_arrays working with the original input, that would be great. I'm not working with it at the moment (at least I think so ;) ) and am happy to adjust it in the future scripts, but some old scripts might break otherwise. I think keeping it working with a warning, as @ipelupessy suggests, is a good solution. Thanks!

Indeed. Got rid of duplicate code, fixed an error in the test, now it succeeds.

I have made the "old" functions return unitless floats again, I think new_binary_from_orbital_elements
should maybe just not work if the input has units (itsdangerous now, becuase it will work with input as e.g. 1|units.rad, but fail/ give unexpected results if that angle is reduced to unitless (still representing  radians, remember that angles can be converted silently to floats..)
maybe rethink the new function names a bit more (shorter, maybe just generate_binaries??

to be clear, for me its ready to merge once we are sure the function names stay the same  (the other thing can be fixed later)

I'll try to think of good function names. I'm wondering if there is some convention for function names like this in Amuse - if not, maybe we should think about that?

for me its ok now...

Great! I'm fine with it as well.


Modify PII Module to Include Driver's Licenses

💡 Summary
The PII filter module needs to filter out drivers licenses as well as other items.
Motivation and context
This will improve our ability to remove personal data.
Implementation notes
Please provide details for implementation, such as:

Drivers license filtering for all states

Acceptance criteria
How do we know when this work is done?

[ ] Filter for states with just numbers
[ ] Filter for states with a combination of letters and numbers up to 9 chars
[ ] Filter for states using RealID

This was working fine but on a recent run the redact script started failing on the Drivers License Detector, I have broken it out into individual detectors for each state and removed those causing it to fail. I'm going to run through the failures to see what the issue is and see if they can be added back successfully, to ensure we have maximum DL coverage

Needed to implement with different regex library and make slight adjustments to the regex, but this is all completed now and pushed in the following PR: https://github.com/cisagov/crossfeed/pull/1442


Fix promotion precision loss

Closes https://github.com/Quantco/ndonnx/issues/38

Can you please create a separate branch.


Material 3: IconButton default color

Right now, when we set useMaterial3 as true, then IconButton starts to set default color for icon.
By default it's themeData.colorScheme.onSurfaceVariant.
The problem is we can't use IconTheme around IconButton for color anymore.
The theme below won't have any effect with useMaterial3: true.
IconTheme(
  data: IconThemeData(
    color: Colors.red,
  ),
  child: IconButton(
    icon: const Icon(Icons.add),
    onPressed: () {},
  ),
)

But with old icon button that works fine.
Not sure about Material You specification, but that's look like pretty strange limitation.

If that's exactly behavior that Material You said us to do, then, maybe, we can create some IconButtonTheme widget, that will have priority over inner default colors inside _IconButtonM3 and __IconButtonDefaultsM3?

Hello @Vorkytaka. I can reproduce this issue in stable but looks like this is fixed in the beta and master channels. Since this is fixed, I am closing this issue. Thank you


Split batched solver compilation

This PR splits up the compilation of the batched solvers in order to reduce the compilation times. It splits up the instantiations of the kernel launches depending on the number of vectors in shared memory. This is based on the same CMake mechanism as for the csr and fbcsr kernels.

This should have a huge impact, excerpt from the HIP 5.14 debug build log
6534.89 hip/CMakeFiles/ginkgo_hip.dir/solver/batch_bicgstab_kernels.hip.cpp.o

IMO the Jacobi instantiation is more complex than what is here. The kernel and the instantiations are directly together, instead of being generated by CMake, which makes it easier to follow for me.
I also merged the two .cpp files per solver, perhaps that can simplify things a bit again.
But I agree that the batch system needs an overhaul in general.

An alternative approach: https://github.com/ginkgo-project/ginkgo/tree/batch-optim

This seems to be quite orthogonal to this PR. With full optimizations enabled, there would be the same issue as before, so the fix from this PR is still needed. I don't see a reason why we should burden people that want the full optimizations enabled with those long compile times, for which we already have a fix available.
But we could add this into this PR.

@MarcelKoch, can you please rebase this when you have some time and we can try to get it merged ?

@pratikvn this should now be properly rebased.


⚠ Samsung has degraded performance

In 3aff380, Samsung (https://samsung.com) experienced degraded performance:

HTTP code: 200
Response time: 2616 ms

Resolved: Samsung performance has improved in 19ec896.


Lock down report Metabase and setup appropriate permissions

The new Metabase instance will have different access requirements
Our current Metabase is a bit of a wild west, but we need the new one to be different:

We will be responsible for ensuring reports work

We can't support reports written by others
We cannot allow the huge proliferation of reports that happened before

The new reports will be subject to much more stringent performance requirements

This means they based on aggregations we will have to write and manage
This will increase the complexity and so skill requirement to write reports

We want the new reports to have better security and data residency adherance than the old

For these reasons and many more, we can't have anyone and everyone able to add reports to Metabase
Requirements

Devs will need full read-write access
Everyone else will need read-only access
People should be able to customise reports using provided handles (like parameterisation, filtering, sorting etc.)
Do we need to segregate some types of users from others?

If so what's the simplest way to do this?
How will we use this when we add new reports?

It would be ideal if this is powered by Google data

So that people are added and remove automatically
So that we don't have manual processes to assign people to groups if possible

A @hypothes.is email account has been created to simulate the experience of a business user. Details can be found in 1Pass

After playing with this between an engineer role and end user (Staff) role. The following is what we will likely end up with:

We can give "View" access to any collection
We cannot stop them from making their own dashboards
They can only put predefined graphs/models/tables into their own dashboards
They log in via their gmail accounts
They can be invited into the All and Staff groups on registration

Can confirm that "All Users" have no access and can only create their own dashboards. However, they cannot place anything in there as they cannot view anything else.


Get a log of who is using the app/bot and see who has it Paused for Matches

Is there a way to get an insight of what users are actually using the Icebreaker bot when it sends them a message, and get an idea of who has it paused for matches? It would be interesting to see how many people in our organization are utilizing this bot and who isn't.

Hi @BDE-95 ,
Thanks for the inputs. We will discuss with the internal team and then will plan it for future releases accordingly.

@BDE-95  We are closing this issue as the feature has already been added to our backlog. It will be considered for future releases based on its priority.


support custom kube-prometheus configmapReloader & prometheusConfigReloader image

ablity to custom configmapReloader & prometheusConfigReloader image in jsonnet template
also close #1322

@brancz plz review

nice! thanks lgtm :+1: this was on my list to do, awesome, thanks!


Using vscode.nvim with vim

Hi,
is it possible to use this colorscheme with vim (not neovim)?

This plugin being written in Lua, it is not possible to use it with vanilla vim. A vim alternative for this plugin would be tomasiser/vim-code/dark.

I see. Thank you you for the explanation. I was kind of hoping to have also the nice light version which is provided here, but the one you reference has only dark version. I like to switch between light and dark (based on my desktop appearance). Well, I guess there is no solution then.


Unable to run code

[<IP_ADDRESS>] [75.187] [system] [critical] Fatal error. Please report to developers. Log: 'ImageManipHelper' '60'
Found This error when i Excecute the code

Hi @Prakash14328897 ,
Which code you ran? Which device did you use? If USB, did it enable USB3 communication (SUPER) or USB2 (HIGH)? Which depthai version did you use?
Thanks, Erik


Problemas con lectura ocr en ios

En ios no funciona la lectura ocr por que por alguna razón, la imagen hay que voltearla -90º asi como tambien hay que voltear el reflejo de la misma.

@jcazalELPAKOMICHI
Please provide the issue description in English since I don't understand the language in which you posted this issue.

Translation:
In ios the ocr reading does not work because for some reason, the image must be turned -90º as well as the reflection of it must also be turned.

@jcazalELPAKOMICHI
Please provide flutter doctor -v and a minimal complete reproducible code sample that shows the issue. Also specify which firebase plugin are you referring to in this issue.

I’m not exactly sure how I got onto this email string. But I have issues with keyboards switching unexpectedly on iOS. Particularly on my iPad when using Apple Pencil and scribble. My phone number always hangs up whenever I fill it from contacts.  I’m not sure if this is of any help with what you’re talking about. I have suddenly been getting a lot of email over the last 24 hours. So much and given my limited time on the platform, I’m having a hard time discerning who is talking about what.
I should also mention this seems to follow a trending problem. Between copy and paste and dictation.
Sent from my iPhone
On Dec 23, 2020, at 9:02 PM, Google Open Source Bot<EMAIL_ADDRESS>wrote:

Hey @jcazalELPAKOMICHIhttps://github.com/jcazalELPAKOMICHI. We need more information to resolve this issue but there hasn't been an update in 7 weekdays. I'm marking the issue as stale and if there are no new updates in the next 7 days I will close it automatically.
If you have more information that will help us get to the bottom of this, just add a comment!
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://github.com/FirebaseExtended/flutterfire/issues/4395#issuecomment-750703325, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ASDEMZYG3TC375EUIJ3KE5LSWKOMFANCNFSM4U2UQOGA.


Revert "HBASE-23304: RPCs needed for client meta information lookup (…

…apache#904) (#1098)"
This reverts commit 71f035450df0c8f56622b5151003bc134ca0091b.

FYI @bharathv @apurtell

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 40s
Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s
No case conflicting files found.

+0 :ok:
prototool
0m  1s
prototool was not available.

+1 :green_heart:
hbaseanti
0m  0s
Patch does not have any anti-patterns.

+1 :green_heart:
@author
0m  0s
The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  0s
The patch appears to include 18 new or modified test files.

_ branch-2 Compile Tests _

+0 :ok:
mvndep
0m 16s
Maven dependency ordering for branch

+1 :green_heart:
mvninstall
5m 30s
branch-2 passed

+1 :green_heart:
compile
2m 26s
branch-2 passed

+1 :green_heart:
checkstyle
2m 17s
branch-2 passed

+1 :green_heart:
shadedjars
4m 26s
branch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
1m 32s
branch-2 passed

+0 :ok:
spotbugs
0m 38s
Used deprecated FindBugs config; considering switching to SpotBugs.

+1 :green_heart:
findbugs
8m 13s
branch-2 passed

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 15s
Maven dependency ordering for patch

-1 :x:
mvninstall
2m 49s
root in the patch failed.

-1 :x:
compile
0m 55s
hbase-server in the patch failed.

-1 :x:
cc
0m 55s
hbase-server in the patch failed.

-1 :x:
javac
0m 55s
hbase-server in the patch failed.

-1 :x:
checkstyle
0m 36s
hbase-client: The patch generated 1 new + 194 unchanged - 0 fixed = 195 total (was 194)

-1 :x:
checkstyle
1m  8s
hbase-server: The patch generated 13 new + 119 unchanged - 0 fixed = 132 total (was 119)

+1 :green_heart:
whitespace
0m  0s
The patch has no whitespace issues.

-1 :x:
shadedjars
3m 34s
patch has 36 errors when building our shaded downstream artifacts.

-1 :x:
hadoopcheck
2m  5s
The patch causes 36 errors with Hadoop v2.8.5.

-1 :x:
hadoopcheck
4m 35s
The patch causes 36 errors with Hadoop v2.9.2.

-1 :x:
hadoopcheck
7m 31s
The patch causes 36 errors with Hadoop v3.1.2.

-1 :x:
hbaseprotoc
0m 55s
hbase-server in the patch failed.

+1 :green_heart:
javadoc
1m 35s
the patch passed

-1 :x:
findbugs
1m  1s
hbase-server in the patch failed.

_ Other Tests _

+1 :green_heart:
unit
0m 50s
hbase-protocol-shaded in the patch passed.

+1 :green_heart:
unit
4m  3s
hbase-client in the patch passed.

+1 :green_heart:
unit
0m 53s
hbase-zookeeper in the patch passed.

-1 :x:
unit
1m  5s
hbase-server in the patch failed.

+1 :green_heart:
asflicense
0m 47s
The patch does not generate ASF License warnings.

64m 49s

Subsystem
Report/Notes

Docker
Client=19.03.5 Server=19.03.5 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1119/1/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/1119

Optional Tests
dupname asflicense javac javadoc unit spotbugs findbugs shadedjars hadoopcheck hbaseanti checkstyle compile cc hbaseprotoc prototool

uname
Linux 2d3305e3a61c 4.15.0-58-generic #64-Ubuntu SMP Tue Aug 6 11:12:41 UTC 2019 x86_64 GNU/Linux

Build tool
maven

Personality
/home/jenkins/jenkins-slave/workspace/Base-PreCommit-GitHub-PR_PR-1119/out/precommit/personality/provided.sh

git revision
branch-2 / 12f4e0977c

Default Java
1.8.0_181

mvninstall
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1119/1/artifact/out/patch-mvninstall-root.txt

compile
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1119/1/artifact/out/patch-compile-hbase-server.txt

cc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1119/1/artifact/out/patch-compile-hbase-server.txt

javac
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1119/1/artifact/out/patch-compile-hbase-server.txt

checkstyle
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1119/1/artifact/out/diff-checkstyle-hbase-client.txt

checkstyle
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1119/1/artifact/out/diff-checkstyle-hbase-server.txt

shadedjars
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1119/1/artifact/out/patch-shadedjars.txt

hadoopcheck
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1119/1/artifact/out/patch-javac-2.8.5.txt

hadoopcheck
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1119/1/artifact/out/patch-javac-2.9.2.txt

hadoopcheck
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1119/1/artifact/out/patch-javac-3.1.2.txt

hbaseprotoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1119/1/artifact/out/patch-hbaseprotoc-hbase-server.txt

findbugs
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1119/1/artifact/out/patch-findbugs-hbase-server.txt

unit
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1119/1/artifact/out/patch-unit-hbase-server.txt

Test Results
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1119/1/testReport/

Max. process+thread count
283 (vs. ulimit of 10000)

modules
C: hbase-protocol-shaded hbase-client hbase-zookeeper hbase-server U: .

Console output
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1119/1/console

versions
git=2.11.0 maven=2018-06-17T18:33:14Z) findbugs=3.1.11

Powered by
Apache Yetus 0.11.1 https://yetus.apache.org

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m  0s
Docker mode activated.

-1 :x:
patch
0m 12s
https://github.com/apache/hbase/pull/1119 does not apply to branch-2. Rebase required? Wrong Branch? See https://yetus.apache.org/documentation/in-progress/precommit-patchnames for help.

Subsystem
Report/Notes

Console output
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1119/2/console

versions
git=2.17.1

Powered by
Apache Yetus 0.11.1 https://yetus.apache.org

This message was automatically generated.

+1 subject to a clean QA build. Thanks for the revert.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
1m  4s
Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  1s
No case conflicting files found.

+0 :ok:
prototool
0m  0s
prototool was not available.

+1 :green_heart:
hbaseanti
0m  0s
Patch does not have any anti-patterns.

+1 :green_heart:
@author
0m  0s
The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  0s
The patch appears to include 19 new or modified test files.

_ branch-2 Compile Tests _

+0 :ok:
mvndep
0m 14s
Maven dependency ordering for branch

+1 :green_heart:
mvninstall
5m 47s
branch-2 passed

+1 :green_heart:
compile
2m 23s
branch-2 passed

+1 :green_heart:
checkstyle
2m 17s
branch-2 passed

+1 :green_heart:
shadedjars
4m 43s
branch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
1m 26s
branch-2 passed

+0 :ok:
spotbugs
0m 34s
Used deprecated FindBugs config; considering switching to SpotBugs.

+1 :green_heart:
findbugs
8m 11s
branch-2 passed

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 14s
Maven dependency ordering for patch

+1 :green_heart:
mvninstall
5m 21s
the patch passed

+1 :green_heart:
compile
2m 22s
the patch passed

+1 :green_heart:
cc
2m 22s
the patch passed

+1 :green_heart:
javac
2m 22s
the patch passed

-1 :x:
checkstyle
0m 37s
hbase-client: The patch generated 1 new + 194 unchanged - 0 fixed = 195 total (was 194)

-1 :x:
checkstyle
1m 14s
hbase-server: The patch generated 13 new + 119 unchanged - 0 fixed = 132 total (was 119)

+1 :green_heart:
whitespace
0m  0s
The patch has no whitespace issues.

+1 :green_heart:
shadedjars
4m 39s
patch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
hadoopcheck
17m  4s
Patch does not cause any errors with Hadoop 2.8.5 2.9.2 or 3.1.2.

+1 :green_heart:
hbaseprotoc
2m 12s
the patch passed

+1 :green_heart:
javadoc
1m 27s
the patch passed

+1 :green_heart:
findbugs
8m 27s
the patch passed

_ Other Tests _

+1 :green_heart:
unit
0m 42s
hbase-protocol-shaded in the patch passed.

+1 :green_heart:
unit
3m 32s
hbase-client in the patch passed.

+1 :green_heart:
unit
0m 48s
hbase-zookeeper in the patch passed.

+1 :green_heart:
unit
155m  2s
hbase-server in the patch passed.

+1 :green_heart:
asflicense
1m 32s
The patch does not generate ASF License warnings.

239m 20s

Subsystem
Report/Notes

Docker
Client=19.03.5 Server=19.03.5 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1119/3/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/1119

Optional Tests
dupname asflicense javac javadoc unit spotbugs findbugs shadedjars hadoopcheck hbaseanti checkstyle compile cc hbaseprotoc prototool

uname
Linux b1f1ac2279cb 4.15.0-74-generic #84-Ubuntu SMP Thu Dec 19 08:06:28 UTC 2019 x86_64 GNU/Linux

Build tool
maven

Personality
/home/jenkins/jenkins-slave/workspace/Base-PreCommit-GitHub-PR_PR-1119/out/precommit/personality/provided.sh

git revision
branch-2 / 12f4e0977c

Default Java
1.8.0_181

checkstyle
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1119/3/artifact/out/diff-checkstyle-hbase-client.txt

checkstyle
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1119/3/artifact/out/diff-checkstyle-hbase-server.txt

Test Results
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1119/3/testReport/

Max. process+thread count
4979 (vs. ulimit of 10000)

modules
C: hbase-protocol-shaded hbase-client hbase-zookeeper hbase-server U: .

Console output
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1119/3/console

versions
git=2.11.0 maven=2018-06-17T18:33:14Z) findbugs=3.1.11

Powered by
Apache Yetus 0.11.1 https://yetus.apache.org

This message was automatically generated.


Error in preprocess and What is in data_fol

In prepare_dataset.py, some error occured:
Traceback (most recent call last):   File "prepare_dataset.py", line 382, in <module>     mano_mask_gc_lc = largest_component(mano_mask_gc)   File "prepare_dataset.py", line 232, in largest_component     max_label, max_size = max([(i, stats[i, cv2.CC_STAT_AREA]) for i in range(1, nb_components)], key=lambda x: x[1])           # Note: range() starts from 1 since 0 is the background label. ValueError: max() arg is an empty sequence
And what should be in the data_fol(/path/to/train/data)?

I have the same issue with the largest_component.

Hi, could you try saving the mask in the variable 'mano_mask_gc'? I suspect that this is empty, and thus the next step is not able to find any connected component here.
As for the data_fol, it is the path where you are saving the pre-processed data.

Yes, you're right, mano_mask_gc returned from grabcut_refine(mano_mask, rgb) contains only zeros. I can try to replace  mano_mask_gc with mano_mask when it happens.

My guess it could be something to do with the OpenCV grabCut, which OpenCV version are you using?

My opencv-python version is <IP_ADDRESS>.

Hi @ivashmak , have you fixed this problem? I encounter the same issue in data preprocessing, and my opencv version is <IP_ADDRESS>

Hi @sHaol0w , updating the OpenCV version helped me a bit, but there were a few more issues that were fixable. First, in some cases cv2.grabCut failed with mode=cv2.GC_INIT_WITH_MASK, so I used try-catch, and I ran without this mode whenever it was failing. Second, I think sometimes mask had extra dimension (ie, H x W x 1), so I had to remove the redundant dimension.


Can't Block Sites

I'm looking at the "Navigate to the sites you want to block during Pomodoro and click on 'Block Site'." screen, but there's no block site button, what do?

Hi @byohub , to block a website navigate to it  in the browser and click here:

If the button is missing please provide a screenshot
Please let me know it worked out for you :)

This is the problem

@byohub this seems like a bug, what website are you trying to block?

I tried on many sites none worked, but reinstalling worked

Great! Thanks for the update.
On Fri, 2 Apr 2021 at 00:21, byohub @.***> wrote:

Closed #48
https://github.com/ofekmiz/Habitica-Pomodoro-SiteKeeper/issues/48.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/ofekmiz/Habitica-Pomodoro-SiteKeeper/issues/48#event-4543433854,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AJOEOFXYCKFRIKJRPBPB2VTTGTPXFANCNFSM4Z6ETEFA
.


Update gurps.html Bugfix

Size modifier on the combat tab is incorrectly labeled as target size modifier.

Submission Checklist
Required

[X] The pull request title clearly contains the name of the sheet I am editing.
[X] The pull request title clearly states the type of change I am submitting (New Sheet/New Feature/Bugfix/etc.).
[X] The pull request makes changes to files in only one sub-folder.
[X] The pull request does not contain changes to any json files in the translations folder (translation.json is permitted)

New Sheet Details

The name of this game is: <   >  (i.e. Dungeons & Dragons 5th Edition, The Dresden Files RPG)

The publisher of this game is: <   > (i.e. Wizards of the Coast, Evil Hat)

The name of this game system/family is: <   > (i.e. Dungeons & Dragons, FATE)

[ ] I have followed the Character Sheets Standards when building this sheet.

[ ] This sheet has been made on behalf of, or by, the game's publisher.
[ ] This game is not a traditionally published game, but a copy of the game rules can be purchased/downloaded/found at: <   >
[ ] This sheet is for an unofficial fan game, modification to an existing game, or a homebrew system.

Changes / Description

One of the fields on the sheet was incorrectly labeled, with caused confusion.  I have corrected the labeling.

Character Sheet Info Roll20 Internal Use only.

@underjack 30k+ lines seems excessive for a bug fix. Is this just a linter/whitespace change? Can you confirm that the only changes here have been to what you intended to change?


storcon: do az aware scheduling

Problem
Storage controller didn't previously consider AZ locality between compute and pageservers
when  scheduling nodes. Control plane has this feature, and, since we are migrating tenants
away from it, we need feature parity to avoid perf degradations.
Summary of changes
The change itself is fairly simple:

Thread az info into the scheduler
Add an extra member to the scheduling scores

Step (2) deserves some more discussion. Let's break it down by the shard type being scheduled:
Attached Shards
We wish for attached shards of a tenant to end up in the preferred AZ of the tenant since that
is where the compute is like to be.
The AZ member for NodeAttachmentSchedulingScore has been placed
below the affinity score (so it's got the second biggest weight for picking the node). The rationale for going
below the affinity score is to avoid having all shards of a single tenant placed on the same node in 2 node
regions, since that would mean that one tenant can drive the general workload of an entire pageserver.
I'm not 100% sure this is the right decision, so open to discussing hoisting the AZ up to first place.
Secondary Shards
We wish for secondary shards of a tenant to be scheduled in a different AZ from the preferred one
for HA purposes.
The AZ member for NodeSecondarySchedulingScore has been placed first, so nodes in different AZs
from the preferred one will always be considered first. On small clusters, this can mean that all the secondaries
of a tenant are scheduled to the same pageserver, but secondaries don't use up as many resources as the
attached location, so IMO the argument made for attached shards doesn't hold.
Related: https://github.com/neondatabase/neon/issues/8848
Checklist before requesting a review

[ ] I have performed a self-review of my code.
[ ] If it is a core feature, I have added thorough tests.
[ ] Do we need to implement analytics? if so did you add the relevant metrics to the dashboard?
[ ] If this PR requires public announcement, mark it with /release-notes label and add several sentences in this section.

Checklist before merging

[ ] Do not forget to reformat commit message to not include the above checklist

The AZ member for NodeAttachmentSchedulingScore has been placed
below the affinity score (so it's got the second biggest weight for picking the node). The rationale for going
below the affinity score is to avoid having all shards of a single tenant placed on the same node in 2 node
regions, since that would mean that one tenant can drive the general workload of an entire pageserver.
I'm not 100% sure this is the right decision, so open to discussing hoisting the AZ up to first place.

I agree with this in the near term.
The consequence will be that for 8 sharded tenants, until we have 24 pageservers in a region, they'll get spread across AZs rather than concentrated in one.  We may well want to evolve this in a few months in https://github.com/neondatabase/neon/issues/8264, to do something like clamping affinity scores to permit a smalll number of a tenant's shards to co-exist on the same pageserver, so that we can get total AZ locality as soon as we have 3-4 pageservers per region.

The AZ member for NodeAttachmentSchedulingScore has been placed
below the affinity score (so it's got the second biggest weight for picking the node). The rationale for going
below the affinity score is to avoid having all shards of a single tenant placed on the same node in 2 node
regions, since that would mean that one tenant can drive the general workload of an entire pageserver.
I'm not 100% sure this is the right decision, so open to discussing hoisting the AZ up to first place.

I agree with this in the near term.
The consequence will be that for 8 sharded tenants, until we have 24 pageservers in a region, they'll get spread across AZs rather than concentrated in one (this is not a regression, just calling out the behavior). We may well want to evolve this in a few months in #8264, to do something like clamping affinity scores to permit a smalll number of a tenant's shards to co-exist on the same pageserver, so that we can get total AZ locality as soon as we have 3-4 pageservers per region.

Indeed. This PR mostly targets single sharded tenants such that they don't experience degradation when migrated
away from cplane. 100% this can evolve into something that deals with many-sharded tenants in a nicer way.