text:
Need a way to deal with objects changing state (i.e. arrays)

From @catmando on May 3, 2015 4:5
For example
define_state(:foo) { ['joe', 'fred'] }

def add_friend(friend)
  foo << friend
end

This does not work as foo << friend updates the array object, but there is no way to know that the foo state has been updated.
I have implemented a couple of solutions, and am interested in which people would prefer:

define foo! method that will return an object that wrap the current value of foo, and observe any changes to that object.   So you can write

def add_friend(friend)
  foo! << friend
end

define foo! method that simple does foo = foo to indicate a state change.  This would return self so that the methods could be chained

def add_friend(friend)
  foo << friend; foo!
end

or
def add_friend(friend)
  foo << friend
ensure
  foo!.bar!
end

2b) In addition the Proc class can be updated so this works
lambda { |new_friend| foo << new_friend }.foo!

Just looking for people's input, preferences, or other ideas!
Copied from original issue: zetachang/react.rb#24

From @catmando on May 4, 2015 18:51
I understand that the current solution is to do something like you said above...
My intention is to add a solution that will read cleaner and be shorter.
I have implemented the all the solutions suggested above, and after playing with them in some code feel that just adding the foo! method is the easiest and cleanest.
I.e. foo! << friend is equal to foo << friend; self.foo = foo
If I do a pull request with this will you accept it?

From @zetachang on May 5, 2015 1:10
I think I get your point now, looks like a nice to have feature. Feel free to open up a pull request :+1:

From @zetachang on May 3, 2015 5:56
Thanks for pointing this out, I think this could be a common mistake given that the original setState is wrapped inside the setter.
Currently, you can write as below,
def add_friend(friend)
  self.foo = foo << friend; self
end

To get the benefit of brevity and also make it chainable.

From @catmando on May 6, 2015 22:37
i've made some more improvements to this... expect a pull request soon, but first I am integrating with some real code to see how everything feels.
Basically there is now a foo! method that can be either used to send a new value to foo as in foo!('new value') (equivilent to self.foo = 'new value')
or if no parameter is provided then foo! returns an object that will update after any method calls on foo.   This is nice because foo! consistently means update foo, and foo! 'new value' is shorter and less error prone than self.foo = 'new value'. (I say less error prone because you don't have to remember to include self.
In addition I added two class methods require_param and optional_param that will declare a validated parameter. The difference is these methods will also create methods that can read the parameters directly.
I.e. require_param :foo, type: String will require a foo parameter and will create a foo method that returns that parameter.
Finally if the type of parameter is Proc then the created method will call the proc.  So
require_param :foo, type: Proc
then
foo 1,2,3
will send 1,2,3 to whatever Proc foo got bound to.
Altogether these changes clean things up so that things read really nicely.
Oh yeah two other things:
You can say class MyComponent < React::Component::Base instead of including React::Component
And any class that responds to 'render' can be used in the rendering dsl.  So you can say
div do
  my_component param_1: 'Joe', param_2: 'Fred'
end

As long as an instance of MyComponent responds to render...
How does all that sound :-)

From @zetachang on May 8, 2015 7:3
Hey, thanks for taking time making this suggestion.

or if no parameter is provided then foo! returns an object that will update after any method calls on foo.

How is this going to be implemented? A wrapper object which will delegate all method invocations?

In addition I added two class methods require_param and optional_param that will declare a validated parameter. The difference is these methods will also create methods that can read the parameters directly.

We currently got a params class methods, it becomes complicated for me to choose which one to use if another require_params, optional_params is introduced. So maybe add a new parameter, that's say accessor: true. So you can write like this,
params do
    requires :foo, type: Proc, accessor: true
end

Finally if the type of parameter is Proc then the created method will call the proc.

This is actually quite neat,  :+1:  on this.

You can say class MyComponent < React::Component::Base instead of including React::Component

Would you mind elaborating more on why having a base class rather than current module approach? The initial design decision made is to allow every Ruby class got render defined could be valid component. React::Component only provide helper methods. And there is a lot of refactoring work for React::Component on #17 , so I will suggest postponing this until it's done.

And any class that responds to 'render' can be used in the rendering dsl.

:+1:  on this.
Last but not least, would you mind open separate pull requests for these features? Thus we can review and merge them faster. :smiley:

From @catmando on May 8, 2015 7:36
Thanks for the feedback... will discuss more on the pull request.
As I am using this in a real app, I am making adjustments to the API as I go

From @catmando on May 17, 2015 12:15
Okay.. I setup a WIP pull request... your comments on these items would be great.

From @ajjahn on October 30, 2015 14:45
@catmando This is implemented as part of the state observer (! bang method) API. Right?

repo: reactrb/reactrb


text:
Not capturing the correct selected words for the highlight

running the latest develop branch on a real device (oneplus 5)
please see the attached video
https://user-images.githubusercontent.com/1643992/133790542-6ec2d267-0116-47f2-af5f-faa8088a6065.mov

@mrifni but how are you even able to play the audio?

@og-abdul-mateen You don't have anything to do to support it. However on FXL EPUB it's currently broken because of this issue: https://github.com/readium/kotlin-toolkit/issues/131

That's interesting. I've been scratching my head over trying to support audiobook + text highlight support (basically Epub3 with MediaOverlay), but couldn't find a sample or documentation for it. Will try it on some Ebooks to see how it goes. Thanks @mickael-menu.

Media overlays is not the same as <audio> resources embedded in HTML pages. They are not yet supported but will be later this year.

Umm okay. I have generated some Ebook files of my own using syncabook (plaintext + audio -> SMIL + XHTML -> EPUB3 with MediaOverlay), but as you mentioned, it might not  atm. Is there a spec for the supported <audio> embedded books format so that I can read more about it and maybe create my own versions using some tool?
PS: Sorry for bloating this thread with unrelated questions.

I would suggest waiting for the Media overlays implementation, this is the most user friendly and easiest to generate. <audio> are just plain HTML elements that are displayed like in this page: https://developer.mozilla.org/en-US/docs/Web/HTML/Element/audio The user must interact with it.

Do we have any ETA for that?

Should be in 2023

@mickael-menu do we have sample Ebooks with audio that work with Readium Kotlin Toolkit on Android? I couldn't make any Ebook audio format work with Readium Android.

https://github.com/IDPF/epub3-samples/releases/download/20230704/cc-shared-culture.epub
This one is supposed to work. If not (with some patience), please report a detailed issue.

https://github.com/IDPF/epub3-samples/releases/download/20230704/cc-shared-culture.epub
This one is supposed to work. If not (with some patience), please report a detailed issue.

@qnga I tried this sample Ebook. Video works fine, but audio doesn't work. Even it would, this is not what I'm looking for. I guess I'll wait for the official MediaOverlay support in Readium Mobile. So far, Readium looks like the most modern Android library for Ebooks while ticking the right boxes for me (except for the MediaOverlay support).

@mickael-menu do we have any update on the EPUB3 with MediaOverlay support in Readium Kotlin Toolkit? If it's far away in future, can you suggest another solution that essentially does the same thing?

It should be available in 2024, I can't be more precise than that.
I'm not sure about any alternative, it depends what you need and if you produce your own publications. If you must consume EPUBs containing media overlays, then no there's no alternative besides implementing it yourself.

source: gharchive/issue

authors: devsm2 mickael-menu mrifni og-abdul-mateen qnga

repo: readium/kotlin-toolkit

license_type: permissive

license_source: github-api


text:
Update KTLint

This PR updates the ktlint gradle plugin to the latest version. In doing so, we are also updating ktlint itself to 1.0.0, and there seems to be a lot of changes there.
Right now, I have only updated the plugin and disabled the rules that currently cause it to error, and there's a lot of them. See https://pinterest.github.io/ktlint/latest/rules/standard/.
Note that ktlint_code_style is set to intellij_idea. That was the default style before 1.0 so it should match our current. There is an option for android_studio too.

@mickael-menu @qnga This is ready for review. Simply comment out the rule in .editorconfig and run ktlintCheck to see where the issues still are. I'm surprised that right now it doesn't catch ones like ktlint_standard_no-semi, unless there is some other configuration?

This is ready for review again. The auto-format was run and committed for individual rules, so those can be reverted easily if needed. The only one I'm not sure about that I did run was wrapping. If you don't like those changes, I'll revert that commit. Otherwise, I think everything else looks good.
Note that I left trailing-comma-on-call-site and trailing-comma-on-declaration-site in there as it changes 357 files and 162 files respectively.

Indeed, I would go without the wrapping rule. Constructors look cumbersome with it.

Looking at it again, maybe it's not horrible. Generic type and type parameter each has its own line.
Old
public interface TtsEngine<S : TtsEngine.Settings, P : TtsEngine.Preferences<P>,
    E : TtsEngine.Error, V : TtsEngine.Voice> : Configurable<S, P>, Closeable {

New
public interface TtsEngine<
    S : TtsEngine.Settings,
    P : TtsEngine.Preferences<P>,
    E : TtsEngine.Error,
    V : TtsEngine.Voice
    > : Configurable<S, P>, Closeable {

I think that looks fine but more importantly I prefer sticking to default options unless they are really asinine.

@mickael-menu @qnga here is a full list of the remaining failures. function-naming is one we will want to keep disabled, as Compose functions generally start with an uppercase letter. The rest, you tell me if they should be fixed.
A (block or EOL) comment inside or on same line after a 'value_parameter' is not allowed. It may be placed on a separate line above. (standard:discouraged-comment-location)

ByteArray.kt#L120

A block comment in between other elements on the same line is disallowed (standard:comment-wrapping)

VisualReaderFragment.kt#L11
VisualReaderFragment.kt#L13
R2WebView.kt#L84
R2WebView.kt#L85
R2WebView.kt#L87
ByteArray.kt#L119
ExoPlayerDataSource.kt#L138
TtsSessionAdapter.kt#L141
AudioFocusManager.kt#L143

A comment in a 'type_argument_list' is only allowed when placed on a separate line (standard:discouraged-comment-location)

VisualReaderFragment.kt#L12
VisualReaderFragment.kt#L14

A comment in a 'value_argument_list' is only allowed when placed on a separate line (standard:discouraged-comment-location)

HtmlResourceContentIterator.kt#L106
LinkTest.kt#L122
ExoPlayerDataSource.kt#L139
TtsSessionAdapter.kt#L142

A comment in a 'value_parameter_list' is only allowed when placed on a separate line (standard:discouraged-comment-location)

Properties.kt#L89
Properties.kt#L90
Metadata.kt#L98
Metadata.kt#L99
Metadata.kt#L100
Metadata.kt#L101
Metadata.kt#L102
Metadata.kt#L103
PdfDocument.kt#L108
MediaOverlayNode.kt#L117
MediaOverlayNode.kt#L118

A single line block comment after a code element on the same line must be replaced with an EOL comment (standard:comment-wrapping)

GridAutoFitLayoutManager.kt#L15
GridAutoFitLayoutManager.kt#L16
R2WebView.kt#L86

Class or object name should start with an uppercase letter and use camel case (standard:class-naming)

LicenseValidation.kt#L45
LicenseValidation.kt#L46
LicenseValidation.kt#L47
LicenseValidation.kt#L48
LicenseValidation.kt#L49
LicenseValidation.kt#L50
LicenseValidation.kt#L51
LicenseValidation.kt#L52
LicenseValidation.kt#L53
LicenseValidation.kt#L54
LicenseValidation.kt#L55
LicenseValidation.kt#L56
LicenseValidation.kt#L57
LicenseValidation.kt#L58
LicenseValidation.kt#L59
LicenseValidation.kt#L60
LicenseValidation.kt#L61
LicenseValidation.kt#L62
LicenseValidation.kt#L63
LicenseValidation.kt#L64
LicenseValidation.kt#L65
LicenseValidation.kt#L66
LicenseValidation.kt#L67
LicenseValidation.kt#L68
PropertyDataType.kt#L129

Function name should start with a lowercase letter (except factory methods) and use camel case (standard:function-naming)

UserPreferences.kt#L1
UserPreferences.kt#L2
UserPreferences.kt#L3
UserPreferences.kt#L4
UserPreferences.kt#L5
UserPreferences.kt#L6
UserPreferences.kt#L7
TtsControls.kt#L8
TtsControls.kt#L9
VisualReaderFragment.kt#L10
ToggleButton.kt#L18
ToggleButton.kt#L19
ToggleButton.kt#L20
EmphasisProvider.kt#L21
AppTheme.kt#L22
DropdownMenuButton.kt#L23
ColorPicker.kt#L24
ColorPicker.kt#L25
ColorPicker.kt#L26
ComposeBottomSheetDialogFragment.kt#L27
Group.kt#L28
Preferences.kt#L29
Preferences.kt#L30
Preferences.kt#L31
Preferences.kt#L32
Preferences.kt#L33
Preferences.kt#L34
Preferences.kt#L35
Preferences.kt#L36
Preferences.kt#L37
Preferences.kt#L38
Preferences.kt#L39
Preferences.kt#L40
Preferences.kt#L41
Preferences.kt#L42
AccessibilityAdapter.kt#L126
AccessibilityAdapter.kt#L127
AccessibilityAdapter.kt#L128
FixedWebRendition.kt#L130
ComposableWebView.kt#L131
ComposableWebView.kt#L132
SingleViewportSpread.kt#L133
DoubleViewportSpread.kt#L134
SpreadWebView.kt#L135
NavigatorPager.kt#L137

No comment expected at this location (standard:discouraged-comment-location)

MediaOverlays.kt#L121

Property name should start with a lowercase letter and use camel case (standard:property-naming)

CatalogFeedListFragment.kt#L43
AppDatabase.kt#L44
LcpDecryptor.kt#L69
LcpDecryptor.kt#L70
LcpDatabase.kt#L71
LcpDatabase.kt#L72
R2WebView.kt#L76
R2WebView.kt#L77
R2WebView.kt#L78
R2WebView.kt#L79
R2WebView.kt#L80
R2WebView.kt#L81
R2WebView.kt#L82
R2WebView.kt#L83
R2WebView.kt#L88
PositionsService.kt#L104
PublicationContentIterator.kt#L105
StringSearchService.kt#L107
ContentResource.kt#L109
ContentResource.kt#L110
HttpResource.kt#L111
TransformingResource.kt#L112
FallbackResource.kt#L113
LazyResource.kt#L114
InMemoryResource.kt#L115
Buffering.kt#L116
PdfPositionsService.kt#L123
LcpdfPositionsService.kt#L124
EpubPositionsService.kt#L125

Property name should use the screaming snake case notation when the value can not be changed (standard:property-naming)

GridAutoFitLayoutManager.kt#L17
CRLService.kt#L73
CRLService.kt#L74
CRLService.kt#L75
R2EpubPageFragment.kt#L91
OPDS1Parser.kt#L92
OPDS1Parser.kt#L93
OPDS1Parser.kt#L94
OPDS1Parser.kt#L95
OPDS1Parser.kt#L96
OPDS1Parser.kt#L97
Scrollable2D.kt#L136
PsPdfKitDocumentFragment.kt#L140

source: gharchive/pull-request

authors: mickael-menu qnga stevenzeck


text:
GitHub alpha releases broken (automatic continuous integration from develop branch)

https://github.com/readium/readium-js-viewer/releases
The tag is correctly generated, but the proper release description (including download links for prebuilt chrome app and cloud reader) is missing.
TravisCI script:
https://github.com/readium/readium-js-viewer/blob/develop/.travis.yml#L95
NodeJS task:
https://github.com/readium/readium-js-viewer/blob/develop/build-config/deployCrx.js
TravisCI job:
https://travis-ci.org/readium/readium-js-viewer/jobs/210072846#L4036

deploying crx to github
deleting previous "0.26.0-alpha" release tag
0.26.0-alpha tag re-creating.
BUILD DATE/TIME: Sat, 11 Mar 2017 16:06:47 GMT
BUILD tag: 0.26.0-alpha
TRAVIS_BRANCH: develop
TRAVIS_COMMIT: 2c349d0fec1b93d61d1148a86855735d925de243
TRAVIS_JOB_NUMBER: 742.1
TRAVIS_BUILD_ID: 210072845
TRAVIS_BUILD_NUMBER: 742
release created
UPLOAD TO RELEASE: [Readium.crx] from [/home/travis/build/readium/readium-js-viewer/dist/Readium.crx] (application/x-chrome-extension)
error uploading binary: 404

False alert: the problem is actually different, the old releases are left over by GitHub as "drafts", they only show-up in my logged-in session.
See:
https://github.com/readium/readium-js-viewer/releases

repo: readium/readium-js-viewer

license_source: bigquery


text:
Intel contribution: CFI improvements

Implement CFI operations that work on text range offsets instead of spatial offsets. Fixes #35, #157, partially fixes #121, #114,
Add convenience functions to views and reader API that uses new CFI functions. Fixes #155.

Some of the new logic breaks in some cases due to issues #37 and #181

@JCCR the "spine item" API change (e.g. getElementByCfi() now takes the string ID instead of object instance) breaks one client-side call in readium-js-viewer EpubReader.js:
element = readium.reader.getElementByCfi(pageChangeData.spineItem, bookmark.contentCFI,
                            ["cfi-marker", "mo-cfi-highlight"],
                            [],
                            ["MathJax_Message"]);

Easy to fix: pageChangeData.spineItem parameter becomes pageChangeData.spineItem.idref

@JCCR it looks like Internet Explorer is not liking the new Node Iterator:
SCRIPT9: Exception occurred.
cfi_navigation_logic.js (1365,17)
var node;
        while ((node = nodeIterator.nextNode())) {
            var $node = $(node);
            var $element = (node.nodeType === Node.TEXT_NODE) ? $node.parent() : $node;
            if (!isElementBlacklisted($element)) {
                $leafNodeElements.push($node);
            }
        }

@JCCR I created a new branch in readium-js-viewer to match the API changes:
https://github.com/readium/readium-js-viewer/tree/feature/intel-cfi-improvements

@danielweck
Thanks for the feedback & fixes. The IE crash is interesting, I'll take a look into that.

@danielweck
Which version of IE were you looking at?

@JCCR Latest IE11 on Windows10

@danielweck
Looks like IE11 doesn't like NodeIterator but does like TreeWalker.

@danielweck
It seems to work fine in Edge.. I'm still writing a fix for the IE10-11 issues. I'm also thinking of updating the accompanying test suites so they work on other browsers.

@danielweck
Navigating to properly generated CFIs is not working in Edge though

I fixed the nodeiterator problem but there are still lots of issues surrounding that piece of code. The IE compatible changes also work on the other browsers, so I'm going to push that here for now.

ACTION:  WIP. Still some issues related to some browsers (e.g. IE, Edge).  Juan is looking into this.

Comparing with bibliolab's implementation right now: https://github.com/bibliolabs/readium-shared-js/commit/cbfb96860f3dad2702398d7cb35d9bccddf1a32c

Regression bug with RTL Right To Left arabic EPUB "regime anticancer arabic": page is offset (not sure why yet, investigating...)

authors: JCCR danielweck rkwright

repo: readium/readium-shared-js


text:
Sorry, someAction does not appear to be a valid operation on this API.

Actual Error
Error: Sorry, `getVouchersApi` does not appear to be a valid operation on this API.
    at Proxy.<anonymous> (/mnt/c/Users/Bruce/Documents/workspace/CoinPlanet/xoxoday_server/node_modules/api/dist/index.js:179:47)
    at step (/mnt/c/Users/Bruce/Documents/workspace/CoinPlanet/xoxoday_server/node_modules/api/dist/index.js:33:23)
    at Object.next (/mnt/c/Users/Bruce/Documents/workspace/CoinPlanet/xoxoday_server/node_modules/api/dist/index.js:14:53)
    at fulfilled (/mnt/c/Users/Bruce/Documents/workspace/CoinPlanet/xoxoday_server/node_modules/api/dist/index.js:5:58)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)

I am referring the docs mentioned here https://helpcenter.xoxoday.com/reference/get-vouchers-api. Although it is working in the docs (on providing my access token) when i perform the same action in my localhost server it is not working.
The above error is being shown. The version is also exactly the same. Even the example is the same.
It is working in the docs but not in my localhost server.
const { pool} = require("../../server");
const sdk = require("api")("@xoxoday/v1.0#d550oavlgo466vx");

// =========== TEST =============

// Retrieve all from the database.
exports.testController = async (req, res) => {
  try {
    const query = {
      text: 'SELECT COUNT(*) FROM "Users"',
    };

    const users = await pool.query(query);
    console.log(users);

    sdk.auth(".........my_access_token..........");
    sdk
      .getVouchersApi({
        query: "plumProAPI.mutation.getVouchers",
        tag: "plumProAPI",
        variables: {
          data: {
            limit: 10,
            page: 1,
            exchangeRate: 1,
            sort: { field: "name", order: "ASC" },
          },
        },
      })
      .then(({ data }) => console.log(data))
      .catch((err) => console.error(err));

    return res.status(200).json({
      usersCount: users.rows,
      // vouchers: vouchers,
    });
  } catch (error) {
    console.log(error);
  }
};

Hi! It looks like the API Registry entry for that API has been a bit corrupted and doesn't have any documented endpoints.

This is unfortunately a known rare quirk in our registry system and something we're working towards resolving but we sadly don't have a workaround for you for this right now. 😞

Hi, Can you suggest a workaround bcz I have paid a lot of money to use this API. Sorry, but will downgrading or using some other version will it work?

It works on the docs because those docs aren't using the api library to make request in the browser, and thereby don't use this API Registry system. Unfortunately cannot be fixed from their site but we're slowly working on fixes it's just a tough problem to solve with how rare it happens.
You can still use their API, just not through the api library. On https://helpcenter.xoxoday.com/reference/get-vouchers-api you can click on this little arrow to see other code snippets for Node HTTP libraries:

Thank You @erunion . I thought using it via api library was the only way

repo: readmeio/api

license: MIT


text:
[C++]: Remove const qualifiers where they have no effect

This qualifier should have no effect because you are returning a copy.

@tmontgomery Do you have a view on that making the next release?

Also so see #384
I recommend to enable warning -Wignored-const-qualifiers with this patch so we prevent this in the future.

@rigtorp is this still relevant given #384?

@tmontgomery No, #384 is a super set of this and will warn about these issues if reintroduced in the future.

Closing this. Per @rigtorp

authors: abbradar mjpt777 rigtorp tmontgomery

repo: real-logic/simple-binary-encoding


text:
'Download Core' occurs an error: Zlib.zlibOnError, errno: -5, code: 'Z_BUF_ERROR'

Running script 'Download Core' occurs an error
Steps to Reproduce
Using Xcode build a react-native project.
Or run command node node_modules/realm/scripts/download-realm.js ios --sync
Log
Resolved requirements: { SYNC_SERVER_FOLDER: 'sync',
SYNC_ARCHIVE: 'realm-sync-cocoa-3.7.0.tar.gz',
SYNC_ARCHIVE_ROOT: 'core' }
No lockfile found at the target, proceeding.
Download url: https://static.realm.io/downloads/sync/realm-sync-cocoa-3.7.0.tar.gz
Extracting realm-sync-cocoa-3.7.0.tar.gz => /node_modules/realm/vendor/realm-ios
{ Error: unexpected end of file
at Zlib.zlibOnError [as onerror] (zlib.js:153:17) errno: -5, code: 'Z_BUF_ERROR'
}
Command /bin/sh failed with exit code 1
Version of Realm and Tooling
Realm version:
Realm: 2.12.0
Xcode version: ?
Xcode 9.4.1
iOS/OSX version: ?
10.13.6
Dependency manager + version: ?
node: v8.11.3
react-native-cli: 2.0.1
react-native: 0.55.4
npm: 5.6.0
More info
I can download from https://static.realm.io/downloads/sync/realm-sync-cocoa-3.7.0.tar.gz using safari.
Thanks.

Closing this issue with no recent activity. I assume this issue has been resolved -- please let us know if that is not the case.

authors: erickyim stennie

repo: realm/realm-cocoa


text:
Upon updating Realm Sync rules/schema, mobile clients don't sync anymore

How frequently does the bug occur?
All the time
Description
Using Realm sync on Atlas v4.x and iOS SDK 10.20.0, when I update the Realm Sync schema by adding a new field to a document or a new collection using the Realm Sync Dashboard, I realized that the "living" mobile client doesn't sync anymore (I'm talking about clients that open a sync stream before and during the schema update). Realm would then only work locally, and a restart of the app is required in order send the fresh data to the servers.
How can I keep the clients synced when I update the server schema?
Stacktrace & log output
No response
Can you reproduce the bug?
Yes, always
Reproduction Steps
No response
Version
10.20.0
What SDK flavour are you using?
MongoDB Realm (i.e. Sync, auth, functions)
Are you using encryption?
Yes, using encryption
Platform OS and version(s)
iOS 15.1
Build environment
Xcode version: 13.2
Dependency manager and version: SPM

Hi @Kalzem,
I will take a look into this issue.

Hi @Kalzem ,
I tried to reproduce this and it first it looked like a bug. I done an additive change to the Realm Sync schema and then modified some documents in Atlas. At first it looked like they were not syncing, but after about 2-3 minutes I received a sync changeset and all objects synced correctly.
Could you also check and see if your objects sync after a certain amount of time?

Hello @leemaguire
Thank you for answering and sorry for the very late delay.
I confirm your observation: Client side re-syncs after 2-3 minutes (or at next launch if the user killed the app before).
Is there a way to make it happen sooner - to control it from the client SDK?
On a final note, I believe that it can be helpful for others to have this behaviour documented.

@Kalzem I spoke with the team and this is the expected behaviour, there is no way to speed up the changes. I will note your suggestion to add this to the documentation.

authors: Kalzem leemaguire

repo: realm/realm-swift


text:
Crash in encrypted realm

How frequently does the bug occur?
All the time
Description
Hi, after upgrading Realm I noticed a crash happening once the app had started up which then seems to corrupt the realm object. I've narrowed it down to upgrading from realm swift 10.21.0 to 10.21.1.
The app will launch OK and seem to run until some kind of interaction happens with the realm. When the app is restarted the realm can no longer be opened and needs to be recreated. I've checked the password remains consistent and none of the code to do the setup has changed for a long time.
Stacktrace & log output
0   App                           0x000000010acc22dc _ZN5realm4utilL18terminate_internalERNSt3__118basic_stringstreamIcNS1_11char_traitsIcEENS1_9allocatorIcEEEE + 28
1   App                           0x000000010acc259f _ZN5realm4util9terminateEPKcS2_lOSt16initializer_listINS0_9PrintableEE + 287
2   App                           0x000000010ac374ab _ZN5realm4util20EncryptedFileMapping13validate_pageEm + 1275
3   App                           0x000000010ac37524 _ZN5realm4util20EncryptedFileMapping8validateEv + 68
4   App                           0x000000010ac36043 _ZN5realm4util20EncryptedFileMapping5flushEv + 307
5   App                           0x000000010ac68826 _ZN5realm4util4File7MapBase5flushEv + 118
6   App                           0x000000010a46ba45 _ZN5realm4util4File3MapIcE5flushEv + 21
7   App                           0x000000010a46ba25 _ZN5realm11GroupWriter9MapWindow5flushEv + 21
8   App                           0x000000010a46c907 _ZN5realm11GroupWriter18flush_all_mappingsEv + 135
9   App                           0x000000010a470f4e _ZN5realm11GroupWriter6commitEm + 382
10  App                           0x000000010a42e2af _ZZN5realm11Transaction9async_endENS_4util14UniqueFunctionIFvvEEEENK3$_3clEv + 159
11  App                           0x000000010a42e205 _ZN5realm4util14UniqueFunctionIFvvEE17call_regular_voidIZNS_11Transaction9async_endES3_E3$_3EEvNSt3__117integral_constantIbLb1EEERT_ + 21
12  App                           0x000000010a42e169 _ZZN5realm4util14UniqueFunctionIFvvEE9make_implIZNS_11Transaction9async_endES3_E3$_3EEDaOT_EN12SpecificImpl4callEv + 25
13  App                           0x000000010a40db0a _ZNK5realm4util14UniqueFunctionIFvvEEclEv + 106
14  App                           0x000000010a40d6ed _ZN5realm2DB17AsyncCommitHelper4mainEv + 205
15  App                           0x000000010a41c6e8 _ZZN5realm2DB17AsyncCommitHelper12start_threadEvENKUlvE_clEv + 24
16  App                           0x000000010a41c68d _ZNSt3__1L8__invokeIZN5realm2DB17AsyncCommitHelper12start_threadEvEUlvE_JEEEDTclclsr3std3__1E7forwardIT_Efp_Espclsr3std3__1E7forwardIT0_Efp0_EEEOS5_DpOS6_ + 29
17  App                           0x000000010a41c625 _ZNSt3__1L16__thread_executeINS_10unique_ptrINS_15__thread_structENS_14default_deleteIS2_EEEEZN5realm2DB17AsyncCommitHelper12start_threadEvEUlvE_JEJEEEvRNS_5tupleIJT_T0_DpT1_EEENS_15__tuple_indicesIJXspT2_EEEE + 37
18  App                           0x000000010a41bea5 _ZNSt3__1L14__thread_proxyINS_5tupleIJNS_10unique_ptrINS_15__thread_structENS_14default_deleteIS3_EEEEZN5realm2DB17AsyncCommitHelper12start_threadEvEUlvE_EEEEEPvSC_ + 101
19  libsystem_pthread.dylib             0x00007fff6da2b8fc _pthread_start + 224
20  libsystem_pthread.dylib             0x00007fff6da27443 thread_start + 15!!! IMPORTANT: Please report this at https://github.com/realm/realm-core/issues/new/choose

Can you reproduce the bug?
Yes, always
Reproduction Steps
The encryption of the Realm is handled as described here https://docs.mongodb.com/realm/sdk/swift/advanced-guides/encrypt-a-realm/
The configuration is
Realm.Configuration(
fileURL: Utils.documentsURLFor(fileName: "cache.realm"),
encryptionKey: {KEY},
schemaVersion: 113,
migrationBlock: {....}
)
And when accessing it the Realm initially with try Realm() there is no error thrown. The database has been integrated for a few years now and this basic flow hasn't changed in that time
Version
10.21.1
What SDK flavour are you using?
Local Database only
Are you using encryption?
Yes, using encryption
Platform OS and version(s)
iOS 15.2
Build environment
Xcode version: 13.2 & 13.2.1
Dependency manager and version: Swift Package Manager

same

same issue

Hi @allanweir
Sorry to hear that you are encountering this. To help narrow this down further could you tell us if you using Realm Sync? And does your model use EmbeddedObject's?

Same problem for me, as well.

Same problem for me.
One other issue we are having is a similar and happening even on 10.21.0 where TouchID devices crash on launch.

This is happening to me as well.

I am using Real Encrypted, only local realm, not Realm Sync
I am using EmbeddedObjects(s).

About the above, this is the error and the stack trace from firebase.

We're also still suffering crashes with encrypted Realms.  We upgraded Realm to 10.21.1 and started experiencing these issues.  Is there anyone from the Realm team actively investigating this issue?

@dianaafanador3 Thanks, Diana.  That's great to hear and I look forward to testing the next release!

@bmt2018 I'll try to investigate a little bit further into this next week when I get to do support, as it seems this affecting a lot of people.

@dianaafanador3 Thank you!  That would be much appreciated!  :-)

Hi, @dianaafanador3  any workaround for this issue? let's say I downgrade the realm SDK version and release a new version for my application, and if someone still faces this issue I can ask them to reinstall my application will this help?
My month crashlytics looked like 200-300 crashes after this update it has been 18k for this month only

I have just tested upgrading from 10.21.0 to 10.25.0 and everything seems to be working as expected, no errors on the first or subsequent runs of the build.
Thanks for looking into this and getting it sorted!
I'll leave closing the issue for when you're happy it's resolved everyone.

Actually there is still an issue:
About 7 builds/runs in I got an error similar to my original post. There were 2 errors in sequence it looks like:
/Users/user/Library/Developer/Xcode/DerivedData/MyApp-gbughxsxqnhbrdfiuvzigofzgcyo/SourcePackages/checkouts/realm-core/src/realm/util/encrypted_file_mapping.cpp:622: [realm-core-11.13.0]  0   MyApp                               0x000000010439b94c _ZN5realm4utilL18terminate_internalERNSt3__118basic_stringstreamIcNS1_11char_traitsIcEENS1_9allocatorIcEEEE + 28 1   MyApp                               0x000000010439bb9c _ZN5realm4util9terminateEPKcS2_lOSt16initializer_listINS0_9PrintableEE + 228 2   MyApp                               0x0000000104318cd0 _ZN5realm4util20EncryptedFileMapping13validate_pageEm + 1048 3   MyApp                               0x0000000104318d30 _ZN5realm4util20EncryptedFileMapping8validateEv + 76 4   MyApp                               0x00000001043179a8 _ZN5realm4util20EncryptedFileMapping5flushEv + 300 5   MyApp                               0x00000001043439e8 _ZN5realm4util4File7MapBase5flushEv + 108 6   MyApp                               0x0000000103c78eec _ZN5realm4util4File3MapIcE5flushEv + 24 7   MyApp                               0x0000000103c78ec8 _ZN5realm11GroupWriter9MapWindow5flushEv + 24 8   MyApp                               0x0000000103c79be0 _ZN5realm11GroupWriter18flush_all_mappingsEv + 128 9   MyApp                               0x0000000103c7d970 _ZN5realm11GroupWriter6commitEm + 404 10  MyApp                               0x0000000103c13be0 _ZN5realm2DB16low_level_commitEyRNS_11TransactionEb + 716 11  MyApp                               0x0000000103c13890 _ZN5realm2DB9do_commitERNS_11TransactionEb + 176 12  MyApp                               0x0000000103c13f10 _ZN5realm11Transaction27commit_and_continue_as_readEb + 260 13  MyApp                               0x0000000103daed64 _ZN5realm5_impl16RealmCoordinator12commit_writeERNS_5RealmEb + 216 14  MyApp                               0x0000000103eefe40 _ZN5realm5Realm18commit_transactionEv + 276 15  MyApp                               0x0000000103adbe8c -[RLMRealm commitWriteTransactionWithoutNotifying:error:] + 552 16  MyApp                               0x00000001044eef60 $s10RealmSwift0A0V11commitWrite16withoutNotifyingySaySo20RLMNotificationTokenCG_tKF + 148 17  MyApp                               0x00000001044eeab4 $s10RealmSwift0A0V5write16withoutNotifying_xSaySo20RLMNotificationTokenCG_xyKXEtKlF + 420 18  MyApp                               0x00000001037b2b68 $s7AppCore12RealmManagerC5writeyyy0B5Swift0B0VXEF + 376 19  MyApp                               0x00000001036a28e0 $s7AppCore14ContentDataSourceC7cleanupyyF + 88 20  MyApp                               0x00000001037b39c0 $s7AppCore12RealmManagerC7cleanup10completionyyAC16StepResponseTypeOc_tFyycfU_ + 256 21  MyApp                               0x000000010348d918 $sIeg_IeyB_TR + 52 22  libdispatch.dylib                   0x000000010aa406d4 _dispatch_call_block_and_release + 32 23  libdispatch.dylib                   0x000000010aa423b4 _dispatch_client_callout + 20 24  libdispatch.dylib                   0x000000010aa44f2c _dispatch_queue_override_invoke + 1052 25  libdispatch.dylib                   0x000000010aa56500 _dispatch_root_queue_drain + 408 26  libdispatch.dylib                   0x000000010aa56f0c _dispatch_worker_thread2 + 196 27  libsystem_pthread.dylib             0x00000001f1bbf0b8 _pthread_wqthread + 228 28  libsystem_pthread.dylib             0x00000001f1bbee94 start_wqthread + 8!!! IMPORTANT: Please report this at https://github.com/realm/realm-core/issues/new/choose2022-04-04 11:42:29.603246+0100 MyApp[6637:2564589] /Users/user/Library/Developer/Xcode/DerivedData/MyApp-gbughxsxqnhbrdfiuvzigofzgcyo/SourcePackages/checkouts/realm-core/src/realm/util/encrypted_file_mapping.cpp:622: [realm-core-11.13.0]
and
libc++abi: terminating with uncaught exception of type realm::util::DecryptionFailed: Decryption failed Exception backtrace: 0   MyApp                               0x0000000103b602c0 _ZN5realm4util6detail26ExceptionWithBacktraceBaseC2Ev + 48 1   MyApp                               0x0000000103b6d428 _ZN5realm4util22ExceptionWithBacktraceISt13runtime_errorEC2IJRKNSt3__112basic_stringIcNS5_11char_traitsIcEENS5_9allocatorIcEEEEEEEDpOT_ + 88 2   MyApp                               0x0000000103b6d208 _ZN5realm4util4File11AccessErrorC2ERKNSt3__112basic_stringIcNS3_11char_traitsIcEENS3_9allocatorIcEEEESB_ + 68 3   MyApp                               0x0000000104319ed4 _ZN5realm4util16DecryptionFailedC2Ev + 100 4   MyApp                               0x0000000104316a30 _ZN5realm4util16DecryptionFailedC1Ev + 28 5   MyApp                               0x0000000104316814 _ZN5realm4util10AESCryptor4readEixPcm + 504 6   MyApp                               0x0000000104318460 _ZN5realm4util20EncryptedFileMapping12refresh_pageEm + 228 7   MyApp                               0x0000000104319970 _ZN5realm4util20EncryptedFileMapping12read_barrierEPKvmPFmPKcE + 156 8   MyApp                               0x0000000103b606dc _ZN5realm4util26do_encryption_read_barrierEPKvmPFmPKcEPNS0_20EncryptedFileMappingE + 68 9   MyApp                               0x0000000103b5f9bc _ZN5realm4util23encryption_read_barrierEPKvmPNS0_20EncryptedFileMappingEPFmPKcE + 60 10  MyApp                               0x0000000103b6cba8 _ZNK5realm9Allocator18translate_criticalEPNS0_14RefTranslationEm + 220 11  MyApp                               0x0000000103b63014 _ZNK5realm9Allocator9translateEm + 72 12  MyApp                               0x0000000103d2f200 _ZN5realm13ArrayBigBlobs3getEPKcmRNS_9AllocatorE + 80 13  MyApp                               0x0000000103d2f0e8 _ZN5realm13ArrayBigBlobs10get_stringEPKcmRNS_9AllocatorEb + 48 14  MyApp                               0x0000000103d221e0 _ZN5realm11ArrayString3getEPKcmRNS_9AllocatorE + 164 15  MyApp                               0x0000000103d1ed58 _ZNK5realm3Obj4_getINS_10StringDataEEET_NS_6ColKey3IdxE + 384 16  MyApp                               0x0000000103d1ebbc _ZNK5realm3Obj3getINS_10StringDataEEET_NS_6ColKeyE + 172 17  MyApp                               0x00000001038962c4 _ZN12_GLOBAL__N_18getBoxedIN5realm10StringDataEEEP11objc_objectP13RLMObjectBasem + 124 18  MyApp                               0x000000010389623c RLMGetSwiftPropertyString + 36 19  MyApp                               0x0000000104471fc8 $sSS10RealmSwiftE23_rlmGetPropertyOptionalySSSgSo13RLMObjectBaseC_s6UInt16VtFZ + 40 20  MyApp                               0x00000001044720e8 $sSS10RealmSwift26_PersistableInsideOptionalA2aBP015_rlmGetPropertyE0yxSgSo13RLMObjectBaseC_s6UInt16VtFZTW + 20 21  MyApp                               0x0000000104477d98 $sSq10RealmSwiftAA26_PersistableInsideOptionalRzlE15_rlmGetPropertyyxSgSo13RLMObjectBaseC_s6UInt16VtFZ + 56 22  MyApp                               0x0000000104478078 $sxSg10RealmSwift12_PersistableA2B01_C14InsideOptionalRzlAbCP15_rlmGetPropertyyxSo13RLMObjectBaseC_s6UInt16VtFZTW + 20 23  MyApp                               0x00000001044d2158 $s10RealmSwift9PersistedV3getyxSo13RLMObjectBaseCF + 3436 24  MyApp                               0x00000001044d13b0 $s10RealmSwift9PersistedV18_enclosingInstance7wrapped7storagexqd___s24ReferenceWritableKeyPathCyqd__xGAHyqd__ACyxGGtcSo13RLMObjectBaseCRbd__luigZ + 204 25  MyApp                               0x000000010375a1ac $s7AppCore7ItemStepC14imageURLStringSSSgvg + 100 26  MyApp                               0x00000001037b5f58 $s7AppCore15UserFileManagerC11fileCleanupyyF + 1288 27  MyApp                               0x00000001037b3bc0 $s7AppCore12RealmManagerC7cleanup10completionyyAC16StepResponseTypeOc_tFyycfU_ + 768 28  MyApp                               0x000000010348d918 $sIeg_IeyB_TR + 52 29  libdispatch.dylib                   0x000000010aa406d4 _dispatch_call_block_and_release + 32 30  libdispatch.dylib                   0x000000010aa423b4 _dispatch_client_callout + 20 31  libdispatch.dylib                   0x000000010aa44f2c _dispatch_queue_override_invoke + 1052 32  libdispatch.dylib                   0x000000010aa56500 _dispatch_root_queue_drain + 408 33  libdispatch.dylib                   0x000000010aa56f0c _dispatch_worker_thread2 + 196 34  libsystem_pthread.dylib             0x00000001f1bbf0b8 _pthread_wqthread + 228 35  libsystem_pthread.dylib             0x00000001f1bbee94 start_wqthread + 8
5 runs later I just have a decryption error:
libc++abi: terminating with uncaught exception of type realm::util::DecryptionFailed: Decryption failed Exception backtrace: 0   MyApp                               0x0000000101edc280 _ZN5realm4util6detail26ExceptionWithBacktraceBaseC2Ev + 48 1   MyApp                               0x0000000101ee93e8 _ZN5realm4util22ExceptionWithBacktraceISt13runtime_errorEC2IJRKNSt3__112basic_stringIcNS5_11char_traitsIcEENS5_9allocatorIcEEEEEEEDpOT_ + 88 2   MyApp                               0x0000000101ee91c8 _ZN5realm4util4File11AccessErrorC2ERKNSt3__112basic_stringIcNS3_11char_traitsIcEENS3_9allocatorIcEEEESB_ + 68 3   MyApp                               0x0000000102695e94 _ZN5realm4util16DecryptionFailedC2Ev + 100 4   MyApp                               0x00000001026929f0 _ZN5realm4util16DecryptionFailedC1Ev + 28 5   MyApp                               0x00000001026927d4 _ZN5realm4util10AESCryptor4readEixPcm + 504 6   MyApp                               0x0000000102694984 _ZN5realm4util20EncryptedFileMapping13validate_pageEm + 268 7   MyApp                               0x0000000102694cf0 _ZN5realm4util20EncryptedFileMapping8validateEv + 76 8   MyApp                               0x0000000102693968 _ZN5realm4util20EncryptedFileMapping5flushEv + 300 9   MyApp                               0x00000001026bf9a8 _ZN5realm4util4File7MapBase5flushEv + 108 10  MyApp                               0x0000000101ff4eac _ZN5realm4util4File3MapIcE5flushEv + 24 11  MyApp                               0x0000000101ff4e88 _ZN5realm11GroupWriter9MapWindow5flushEv + 24 12  MyApp                               0x0000000101ff5ba0 _ZN5realm11GroupWriter18flush_all_mappingsEv + 128 13  MyApp                               0x0000000101ff9930 _ZN5realm11GroupWriter6commitEm + 404 14  MyApp                               0x0000000101f8fba0 _ZN5realm2DB16low_level_commitEyRNS_11TransactionEb + 716 15  MyApp                               0x0000000101f8f850 _ZN5realm2DB9do_commitERNS_11TransactionEb + 176 16  MyApp                               0x0000000101f8fed0 _ZN5realm11Transaction27commit_and_continue_as_readEb + 260 17  MyApp                               0x000000010212ad24 _ZN5realm5_impl16RealmCoordinator12commit_writeERNS_5RealmEb + 216 18  MyApp                               0x000000010226be00 _ZN5realm5Realm18commit_transactionEv + 276 19  MyApp                               0x0000000101e57e4c -[RLMRealm commitWriteTransactionWithoutNotifying:error:] + 552 20  MyApp                               0x000000010286af20 $s10RealmSwift0A0V11commitWrite16withoutNotifyingySaySo20RLMNotificationTokenCG_tKF + 148 21  MyApp                               0x000000010286aa74 $s10RealmSwift0A0V5write16withoutNotifying_xSaySo20RLMNotificationTokenCG_xyKXEtKlF + 420 22  MyApp                               0x0000000101b2eb28 $s7AppCore12RealmManagerC5writeyyy0B5Swift0B0VXEF + 376 23  MyApp                               0x0000000101a1e8a0 $s7AppCore14ContentDataSourceC7cleanupyyF + 88 24  MyApp                               0x0000000101b2f980 $s7AppCore12RealmManagerC7cleanup10completionyyAC16StepResponseTypeOc_tFyycfU_ + 256 25  MyApp                               0x00000001018098d8 $sIeg_IeyB_TR + 52 26  libdispatch.dylib                   0x0000000108f086d4 _dispatch_call_block_and_release + 32 27  libdispatch.dylib                   0x0000000108f0a3b4 _dispatch_client_callout + 20 28  libdispatch.dylib                   0x0000000108f0cf2c _dispatch_queue_override_invoke + 1052 29  libdispatch.dylib                   0x0000000108f1e500 _dispatch_root_queue_drain + 408 30  libdispatch.dylib                   0x0000000108f1ef0c _dispatch_worker_thread2 + 196 31  libsystem_pthread.dylib             0x00000001f1bbf0b8 _pthread_wqthread + 228 32  libsystem_pthread.dylib             0x00000001f1bbee94 start_wqthread + 8
The sequence of events on my app starting up are:

Launch
Wait for Realm to be setup (i.e. let realm = try Realm())
When the Realm object is available run a cleanup on old content straight away, before the rest of the app can do anything
During cleanup items older than 30 days may be removed, or marked for deletion on an object property

The first crash sequence happened during this cleanup. All the cleanup is ran on the main thread in a sequence rather than concurrently. In that sequence the first error happens opening a write block (realm.write { .. } ). The second comes accessing an object property (.imageURLString)

Hi Pavel, looks to be working well! Thanks for the update and getting the fix out

Updated this morning and so far, so good.  Thank you for the update on this!

authors: Sethmr allanweir bmt2018 c128128 cupcake-shukla dianaafanador3 kordem leemaguire matthewjordanRiM


text:
Weird characters appended to file on every save

a file with the following content:
type hello = {
  name: string,
  is: bool
};

gets l; appended to it every time I save

I think this should be fixed in version 1.0.23.

repo: reasonml-editor/vscode-reasonml


text:
feat: add empty polyfill for react-native-web

Description
Implemented support for react-native-web (#323). We now provide an empty polyfill.

It would be handy if userAgent returned accurate information since it's applicable for web.
userAgent: window.navigator.userAgent

authors: machour peacechen

repo: rebeccahughes/react-native-device-info

license: mit


text:
fix(hlgroups): use vim.tbl_extend to apply config styles

Closes #50 by replacing unpack with vim.tbl_extend. The builtin unpack function is used for list-like tables according to the docs.
First attempt at creating a pull request on Github, so apologies if format or anything else is off.

Here's a preview of the updated version:


text:
Demo page error: Fatal error: Cannot retrieve a version for package rector/rector since it is replaced by some other package

Step to reproduce:
Open https://getrector.org/demo/6bb1f170-57b0-4fb1-8e53-7fbaa57fb736 click "Process", got the following error:

Thanks!
Any steps how to reproduce locally with repository only? That way I could try to figure out the solution

I tried install via clone - run composer update, got the following error:
An exception has been thrown during the rendering of a template ("Asset manifest file "/Users/samsonasik/www/getrector.org/public/build/manifest.json" does not exist.").

it seems need docker

Hi, this bug is caused by https://github.com/rectorphp/getrector.org/pull/292
I will create integration test as this is happening way too often and finally when demo does not need to run in docker it will be much easier.
You do not need docker to run getrector.org locally, just follow the instructions that are happening in docker build:
yarn install
yarn run build
composer install

Thank you Honza

I also found this issue:
Warning: The lock file is not up to date with the latest changes in composer.json. You may be getting outdated dependencies. It is recommended that you run `composer update` or `composer update <package name>`.

https://github.com/rectorphp/getrector.org/runs/2156349807?check_suite_focus=true
Test successfully detects this issue

Im not sure how to fix. I merged the failing test into main (as the broken code is already merged) so you can rebase and fix.
I am able to get to it later today (in like 3 hours) if you are not able to fix yourself.
Anyways it seems like some changes in rector itself are causing this and are not related to getrector.org at all. Just try to install rector locally and run with json output formatter.

Thank you :+1:
It's related to jean85/pretty-package-versions. It kinda buggy with various composer 1/2 prefixed combinations.

authors: JanMikes TomasVotruba samsonasik


text:
Add DependencyLibrary to support test case/suite dependency

Robot Framework DependencyLibrary allows creating dependency between test cases and test suites.
For example, we can create the foloowing logic:
If test A must be executed before test B, because test B expects some resources created by test A,
but test A failed - then test B will not be executed and marked as skipped.
Adopting DependencyLibrary Keywards often in our sequential tests can save a lot of run-time and diagnostic time, in case of failed tests that were dependent on previous tests.
This commit includes a first use of the KW Depends On Test in: 420__model_serving.robot suite.

Agree with Jan on running the smoke to make sure nothing is broken

I'm not in favor of having the dependent tests in general (setup and teardown seem nicer to me),

Counting on test setup (which means call test teardown later too) brings more code + more test runtime + more maintenance + debug time on falied tests that counts on earlier tests, as in my example:
Test Inference Without Token Authentication which runs in smoke after Verify Openvino_IR Model Via UI is expecting to have the model interface already running. Currently if you try to run Verify Openvino_IR Model Via UI solely, it will always fail. This is where DependencyLibrary is so effective.
Once we start to adopt it in our code, which anyhow uses a lot of dependency - without specifying it in the tests sometimes - we would save much more setup code lines, and failure analysis time.

Also, there are some major upgrades of python dependencies included with this, so hopefully all will work as expected. Would be nice to run a couple of more tests (smoke?) with this PR too, though.
Yes, running as we speak :)

I verified on 2.9 and the the pass rate was similar as we had for 2.9 before this commit.

authors: manosnoam tarukumar

repo: red-hat-data-services/ods-ci


text:
[Lib-160] added support to remove disabled card for ovms and aikit

Signed-off-by: tarukumar takumar@redhat.com
Added support to remove the disabled card from rhods dashboard for openvino and intel aikit operator

/test image=qe-catalog-source:v160-8;testrepo=https://github.com/tarukumar/ods-ci;testbranch=remove-aikit-openvino-card-from-dashboard;testuser=user1;testcluster=qeaisrhods-fr9;testarg=--extra-robot-args '-i ODS-702';


text:
DO NOT MERGE: deleting and recreating deployments on v1->v2 upgrade

Initial code to delete deployments when upgrading v1->v2

performed test:
from v2->v2

install wenzhou/v2.11.746-33 (code from rhods-1.33 of v2) as base
enable dashboard and workbench, create workbenche (see pod running in notebook NS)

build wenzhou/v2.11.746-170( code from this PR) set above image as FROM (patch version need to be higher than FROM one....)
dashboard did not recreated, but 2 NBC did get recreated => NEED TO CHECK WHY

workbench not get recreate  => GOOD
we will need complete test when all GA components are Managed to do full test on this case
from v1->v2
i cannot have a FROM image from rhods, had to switch to ODH operator base code to patch this PR for testing

install the latest ODH 1.11.0 release (took bit time to get it, because the accelerator in dashboard api version conflict)

check dashbaord and create notebook

TODO

build a new v2 from incubation + this PR, use v1.11.0 as FROM

close as not needed

authors: etirelli zdtsw

repo: red-hat-data-services/rhods-operator


text:
[cherry-pick from main] Remove: embedded channel from 1.33

ref: https://github.com/red-hat-data-services/rhods-operator/pull/59

close it, since not critical for 1.33 and seems we do not need rebuild 1.33


text:
DFBUGS-872: [release-4.17] server: saving quota in GiB instead GB

PVCs are in Gib and quota is in GB because of which pvc creation is restricted when the quota reaches around 95%
manual Cherry-pick of https://github.com/red-hat-storage/ocs-operator/pull/2895

/test ocs-operator-bundle-e2e-aws

/test ocs-operator-bundle-e2e-aws

/lgtm

/jira refresh

/jira refresh

/jira refresh

/jira refresh

authors: nb-ohad rchikatw

repo: red-hat-storage/ocs-operator


text:
Various small improvements

These fix #3 and #4. I'll do retries next.
:eyeglasses: @bsimpson63 @kjoconnor

:fish:

:fish:

authors: bsimpson63 kjoconnor spladug

repo: reddit/baseplate


text:
Appstudio update test-component-pac-nilq

Pipelines as Code configuration proposal
To start the PipelineRun, add a new comment with content /ok-to-test
For more detailed information about running a PipelineRun, please refer to Pipelines as Code documentation Running the PipelineRun
To customize the proposed PipelineRuns after merge, please refer to Build Pipeline customization

Pipelines as Code CI/test-component-pac-nilq-on-pull-request has successfully validated your commit.

StatusDurationName

✅ Succeeded
16 seconds
init

✅ Succeeded
35 seconds
clone-repository

✅ Succeeded
1 minute
build-container

✅ Succeeded
24 seconds
inspect-image

✅ Succeeded
26 seconds
deprecated-base-image-check

✅ Succeeded
1 minute
clamav-scan

✅ Succeeded
3 minutes
clair-scan

✅ Succeeded
34 seconds
sbom-json-check

✅ Succeeded
18 seconds
label-check

✅ Succeeded
7 seconds
show-sbom

✅ Succeeded
10 seconds
show-summary

Pipelines as Code CI/test-component-pac-nilq-on-pull-request has successfully validated your commit.

StatusDurationName

✅ Succeeded
6 seconds
init

✅ Succeeded
26 seconds
clone-repository

✅ Succeeded
1 minute
build-container

✅ Succeeded
11 seconds
clair-scan

✅ Succeeded
10 seconds
inspect-image

✅ Succeeded
11 seconds
deprecated-base-image-check

✅ Succeeded
49 seconds
clamav-scan

✅ Succeeded
9 seconds
sbom-json-check

✅ Succeeded
19 seconds
label-check

✅ Succeeded
8 seconds
show-sbom

✅ Succeeded
7 seconds
show-summary


text:
Appstudio update test-custom-default-branch-nrjd

Pipelines as Code configuration proposal
To start the PipelineRun, add a new comment with content /ok-to-test
For more detailed information about running a PipelineRun, please refer to Pipelines as Code documentation Running the PipelineRun
To customize the proposed PipelineRuns after merge, please refer to Build Pipeline customization

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-simple-build-nyrh-on-pull-request-
creating pipelinerun test-simple-build-nyrh-on-pull-request- in namespace build-e2e-zvaa-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-simple-build-wadk-on-pull-request-
creating pipelinerun test-simple-build-wadk-on-pull-request- in namespace build-e2e-zvaa-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-simple-build-mcmm-on-pull-request-
creating pipelinerun test-simple-build-mcmm-on-pull-request- in namespace build-e2e-zvaa-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-simple-build-imul-on-pull-request-
creating pipelinerun test-simple-build-imul-on-pull-request- in namespace build-e2e-zvaa-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-simple-build-lqle-on-pull-request-
creating pipelinerun test-simple-build-lqle-on-pull-request- in namespace build-e2e-zvaa-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-simple-build-uqzm-on-pull-request-
creating pipelinerun test-simple-build-uqzm-on-pull-request- in namespace build-e2e-zvaa-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-simple-build-nwtb-on-pull-request-
creating pipelinerun test-simple-build-nwtb-on-pull-request- in namespace build-e2e-zvaa-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-annotations-mijr-on-pull-request-
creating pipelinerun test-annotations-mijr-on-pull-request- in namespace build-e2e-zvaa-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-simple-build-ufgi-on-pull-request-
creating pipelinerun test-simple-build-ufgi-on-pull-request- in namespace build-e2e-zvaa-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request


text:
Create temporary pipeline with HACBS enabled

Create HACBS enabled pipeline for testing purposes.

LGTM

authors: Michkov tkdchen

repo: redhat-appstudio/build-definitions


text:
Pipeline Service Dashboard

Add a grafana dashboard for Pipeline Service

/assign @amisstea

I"m surprised that there is not a staging and production definition for the dashboards. Don't we need to validate dashboards changes before promoting them?

/approve

/lgtm

authors: Roming22 adambkaplan amisstea

repo: redhat-appstudio/infra-deployments


text:
Allow mintmaker team members to create delete dependencyupdatechecks

DependencyUpdateCheck is a CR used by mintmaker to trigger Renovate jobs.

/approve
/lgtm

authors: gnaponie qixiang


text:
sender.Client.Send() says failed eventhough data is send

linuxptp-daemon
time="2022-11-10T20:39:45Z" level=info msg="setting return address to /cluster/node/cp-baremetal-ptpstack-1/mock/RRyIz"
time="2022-11-10T20:39:45Z" level=info msg="got status check call,fire events returning to /cluster/node/cp-baremetal-ptpstack-1/mock/RRyIz"
time="2022-11-10T20:39:45Z" level=info msg="created new sender for /cluster/node/cp-baremetal-ptpstack-1/mock/RRyIz"
time="2022-11-10T20:39:47Z" level=error msg="failed to send(TO): /cluster/node/cp-baremetal-ptpstack-1/mock/RRyIz result context deadline exceeded "
time="2022-11-10T20:39:47Z" level=error msg="postprocessfn:not finding publisher for address /cluster/node/cp-baremetal-ptpstack-1/mock/status"

consumer side:
time="2022-11-10T20:39:45Z" level=info msg="sending status requerst to status address /cluster/node/cp-baremetal-ptpstack-1/mock/status with return /cluster/node/cp-baremetal-ptpstack-1/mock/RRyIz"
time="2022-11-10T20:39:45Z" level=info msg="waiting to receive message at /cluster/node/cp-baremetal-ptpstack-1/mock/RRyIz"
time="2022-11-10T20:39:45Z" level=info msg="got the status msg Context Attributes,\n  specversion: 0.3\n  type: /cluster/node/cp-baremetal-ptpstack-1/mock\n  source: /cluster/node/cp-baremetal-ptpstack-1/mock\n  subject: mock\n  id: 3eb49d48-f07b-4406-b8f0-d445472fe629\n  time: 2022-11-10T20:39:45.485Z\n  datacontenttype: application/json\nData,\n  {\n    \"version\": \"v1\",\n    \"values\": [\n      {\n        \"resource\": \"/mock\",\n        \"dataType\": \"notification\",\n        \"valueType\": \"enumeration\",\n        \"value\": \"ACQUIRING-SYNC\"\n      },\n      {\n        \"resource\": \"/mock\",\n        \"dataType\": \"metric\",\n        \"valueType\": \"decimal64.3\",\n        \"value\": \"99.6\"\n      }\n    ]\n  }\n"
time="2022-11-10T20:39:47Z" level=error msg="failed to send(TO): /cluster/node/cp-baremetal-ptpstack-1/mock/status result context deadline exceeded "
time="2022-11-10T20:39:47Z" level=error msg="failed to receive status request to address /cluster/node/cp-baremetal-ptpstack-1/mock/status"

Even though data is send, send() says "failed to send(TO): /cluster/node/cp-baremetal-ptpstack-1/mock/status result context deadline exceeded"
On Further debugging it narrowed down to this issue https://github.com/Azure/go-amqp/issues/193
@aneeshkp

https://github.com/Azure/go-amqp/issues/193 is a different problem I think , @aneeshkp

I think ,  this is because the receiver is not sending back  ack as delivered.
I will have to look at the code I am using to build temp AMQ   receiver
https://github.com/redhat-cne/sdk-go/blob/main/pkg/protocol/amqp/amqp.go#L313

@aneeshkp any updates?

I  thnk the sender object we are using doesn't expect an acknowledgment.
I still have to get into testing and fixing this.
https://github.com/redhat-cne/sdk-go/blob/e226a93f380acba9a212be3ca6fdc6397572187b/pkg/protocol/amqp/amqp.go#L687

@aneeshkp Any further updates?

Did you try with latest changes. ?

No, any changes went in?

Working now... closing the issue

authors: aneeshkp nmathew

repo: redhat-cne/cloud-event-proxy


text:
Bundle considerations for non tagged releases

Bundle considerations for non tagged releases
For non release builds, bundle version will be latest tagged version (0.0.0 if none exist) + 0.0.1. Bundle image is pushed as latest

LGTM

LGTM

repo: redhat-cop/group-sync-operator


text:
Ploigos gets stuck on cluster-check

I've just tried to install ploigos, but it gets stuck on the cluster-check (CRD never gets created)
cd ploigos
export project_name="ploigos-$(date +'%d%m%Y')"
oc new-project ${project_name}
helm install ploigos -f values.yaml --set-string operator.namespaces[0].name=${project_name} .

@eformat ; any ideas?

yup .. looks like older operator versions not in catalog anymore ... updating
https://github.com/redhat-cop/helm-charts/pull/136

authors: eformat garethahealy

repo: redhat-cop/helm-charts


text:
Use pre-defined service status constant values

Closes #1174
Verification Steps

Do x
Do y

Type of change

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Documentation change
[ ] Other (please specify)

Checklist

[ ] Documentation added for the feature
[ ] CI and all relevant tests are passing
[ ] Code Review completed
[ ] Verified independently by reviewer

Amazing contribution. @craicoverflow will review

authors: kashifsoofi wtrocki

repo: redhat-developer/app-services-cli


text:
Fix the wrong serviceaccount name bug

I extracted the fix for the serviceaccount name bug from PR:
https://github.com/redhat-developer/build/pull/109
There is a bug:

When you input a wrong serviceaccount name which doesn't exist
The current logic will check it is not found and but continue using default service account for end-user
But the end-user doesn't know he input wrong and be changed to use the default service account, so it is a bad user experience

I change to:

If cannot get service account correctly, doesn't change to use default sa anymore
Report the error directly to let the user know the problem

I talked with @qu1queee this afternoon.
The initial fix is not good for us. We may miss the default serviceaccount configuration in the logic.
So I refine the code logic as below:

If end user doesn't set the serviceaccount property, try to find pipeline sa, if doesn't exist try to find default sa

If end user set the serviceaccount , but doesn't exist, then report the error directly

It is better than before. Thanks for the suggestion Enrique!

/hold
Changes have been moved to https://github.com/redhat-developer/build/pull/105

repo: redhat-developer/build


text:
RHIDP-2149 chore: Added configuration files for AsciiDoc preview in the IDE

With this update, the documentation author can preview AsciiDoc files in the editor with style.
Supported IDEs: IntelliJ and Visual Studio Code.
Example, in IntelliJ:

Example, in Visual Studio Code:

/lgtm
this is great, it makes reviewing in VSCode much easier

did not test, but looks good; assuming @kadel tested it, let's merge and see what happens! I have already been using asciidoctor previews in vscode but I guess this will apply a more consistent css than the default one

I get a different markup but the fact that includes are now followed is awesome.

authors: kadel nickboldt themr0c


text:
RHIDP-2264 : add extra app-config configuration for AKS Operator installation procedure

Fix for https://issues.redhat.com/browse/RHIDP-2264

/cherrypick 1.1.x

/cherrypick 1.2.x

authors: gazarenkov hmanwani-rh


text:
operator dynatrace-operator (0.9.0)

Signed-off-by: Dynatrace Team Kubernetes team-kubernetes-operator@dynatrace.com
Thanks for submitting your Operator. Please check the below list before you create your Pull Request.
New Submissions

[ ] Are you familiar with our contribution guidelines?
[ ] Have you packaged and deployed your Operator for Operator Framework?
[ ] Have you tested your Operator with all Custom Resource Definitions?
[ ] Have you tested your Operator in all supported installation modes?
[ ] Have you considered whether you want to use semantic versioning order?
[ ] Is your submission signed?
[ ] Is operator icon set?

Updates to existing Operators

[x] Did you create a ci.yaml file according to the update instructions?
[x] Is your new CSV pointing to the previous version with the replaces property if you chose replaces-mode via the updateGraph property in ci.yaml?
[x] Is your new CSV referenced in the appropriate channel defined in the package.yaml or annotations.yaml ?
[x] Have you tested an update to your Operator when deployed via OLM?
[x] Is your submission signed?

Your submission should not

[x] Modify more than one operator
[x] Modify an Operator you don't own
[x] Rename an operator - please remove and add with a different name instead
[x] Modify any files outside the above mentioned folders
[x] Contain more than one commit. Please squash your commits.

Operator Description must contain (in order)

[x] Description of the managed Application and where to find more information
[x] Features and capabilities of your Operator and how to use it
[x] Any manual steps about potential pre-requisites for using your Operator

Operator Metadata should contain

[x] Human readable name and 1-liner description about your Operator
[x] Valid category name1
[x] One of the pre-defined capability levels2
[x] Links to the maintainer, source code and documentation
[x] Example templates for all Custom Resource Definitions intended to be used
[x] A quadratic logo

Remember that you can preview your CSV here.
--
1 If you feel your Operator does not fit any of the pre-defined categories, file an issue against this repo and explain your need
2 For more information see here

/merge possible

/merge possible

authors: dt-team-kubernetes framework-automation


text:
operator gitlab-operator-kubernetes (0.23.4)

Thanks for submitting your Operator. Please check the below list before you create your Pull Request.
New Submissions

[ ] Are you familiar with our contribution guidelines?
[ ] Have you packaged and deployed your Operator for Operator Framework?
[ ] Have you tested your Operator with all Custom Resource Definitions?
[ ] Have you tested your Operator in all supported installation modes?
[ ] Have you considered whether you want to use semantic versioning order?
[ ] Is your submission signed?
[ ] Is operator icon set?

Updates to existing Operators

[ ] Did you create a ci.yaml file according to the update instructions?
[ ] Is your new CSV pointing to the previous version with the replaces property if you chose replaces-mode via the updateGraph property in ci.yaml?
[ ] Is your new CSV referenced in the appropriate channel defined in the package.yaml or annotations.yaml ?
[ ] Have you tested an update to your Operator when deployed via OLM?
[ ] Is your submission signed?

Your submission should not

[ ] Modify more than one operator
[ ] Modify an Operator you don't own
[ ] Rename an operator - please remove and add with a different name instead
[ ] Modify any files outside the above mentioned folders
[ ] Contain more than one commit. Please squash your commits.

Operator Description must contain (in order)

[ ] Description of the managed Application and where to find more information
[ ] Features and capabilities of your Operator and how to use it
[ ] Any manual steps about potential pre-requisites for using your Operator

Operator Metadata should contain

[ ] Human readable name and 1-liner description about your Operator
[ ] Valid category name1
[ ] One of the pre-defined capability levels2
[ ] Links to the maintainer, source code and documentation
[ ] Example templates for all Custom Resource Definitions intended to be used
[ ] A quadratic logo

Remember that you can preview your CSV here.
--
1 If you feel your Operator does not fit any of the pre-defined categories, file an issue against this repo and explain your need
2 For more information see here

/merge possible

/merge possible

authors: framework-automation gl-distribution-oc


text:
operators universal-crossplane (1.6.1-up.1)

Thanks submitting your Operator. Please check below list before you create your Pull Request.
New Submissions

[ ] Are you familiar with our contribution guidelines?
[ ] Have you packaged and deployed your Operator for Operator Framework?
[ ] Have you tested your Operator with all Custom Resource Definitions?
[ ] Have you tested your Operator in all supported installation modes?
[ ] Have you considered whether you want use semantic versioning order?
[ ] Is your submission signed?
[ ] Is operator icon set?

Updates to existing Operators

[x] Did you create a ci.yaml file according to the update instructions?
[x] Is your new CSV pointing to the previous version with the replaces property if you chose replaces-mode via the updateGraph property in ci.yaml?
[x] Is your new CSV referenced in the appropriate channel defined in the package.yaml or annotations.yaml ?
[ ] Have you tested an update to your Operator when deployed via OLM?
[x] Is your submission signed?

Your submission should not

[x] Modify more than one operator
[x] Modify an Operator you don't own
[x] Rename an operator - please remove and add with a different name instead
[x] Modify any files outside the above mentioned folders
[x] Contain more than one commit. Please squash your commits.

Operator Description must contain (in order)

[x] Description about the managed Application and where to find more information
[x] Features and capabilities of your Operator and how to use it
[x] Any manual steps about potential pre-requisites for using your Operator

Operator Metadata should contain

[x] Human readable name and 1-liner description about your Operator
[x] Valid category name1
[x] One of the pre-defined capability levels2
[x] Links to the maintainer, source code and documentation
[x] Example templates for all Custom Resource Definitions intended to be used
[x] A quadratic logo

Remember that you can preview your CSV here.
--
1 If you feel your Operator does not fit any of the pre-defined categories, file an issue against this repo and explain your need
2 For more information see here

/retest-required

/merge possible

@turkenh can you please fix: https://github.com/redhat-openshift-ecosystem/community-operators-prod/runs/4883448404?check_suite_focus=true#step:6:1072

@turkenh can you please fix: https://github.com/redhat-openshift-ecosystem/community-operators-prod/runs/4883448404?check_suite_focus=true#step:6:1072

@mvalarh need some guidance on that: https://github.com/k8s-operatorhub/community-operators/pull/619#issuecomment-1018434683
Could you help?

/merge possible

@mvalarh removed service accounts from the manifest and previously failing kiwi test passed this time, but now all deployment tests failed.
Tested locally and observed exactly the same behaviour, e.g. operator-sdk bundle validate works but when I try to deploy, no pods created because service account not created at all. 😕

/test all

@turkenh looks like service account name has some conflict. Like 2 different service accounts using the same name. The error is  sa name cannot match service account defined for deployment spec in CSV

@turkenh looks like service account name has some conflict. Like 2 different service accounts using the same name. The error is  sa name cannot match service account defined for deployment spec in CSV

Let me summarize, I am confused because:

There are no such duplicated service accounts in the bundle
Even the existing latest version fails with the same error locally (with operator-sdk bundle validate)
Following @estroz suggestion in this comment, I removed service account manifests. Validation passed this time but the installation failed on all jobs and reproduced locally that it is because there is no SA, OLM didn't create the service accounts referenced in CSV

So, I am kind of stuck at this point regarding how to proceed.

@turkenh If I understand correctly, you would like to include service account on one hand and keep validator satisfied on the other hand. Maybe using different name for service account could help. Validate it by SDK.

@turkenh are you able to install the operator on OCP?

@turkenh closing due to no activity, feel free to reopen any time.

authors: J0zi framework-automation mvalarh turkenh


text:
Upstream community operators update (10.06.2021)

Signed-off-by: Martin Vala mavala@redhat.com

Please try to sync roles which are already in master rather than creating copies

I would start with copy of roles in upstream first. When we will merge to master then i would start to move roles from upstream dir. I would like to have it merged as soon as possible and not influence your code.

Is this connected to some sort of story/epic?

@jsztuka yes, https://projects.engineering.redhat.com/browse/CVP-1441

@mvalarh  looks like the role final_cleanup_upstream is not used.
Can you remove it from PR ?

authors: jsztuka lslebodn mvalarh


text:
Need to fix post install tasks for provisioningOSDownloadURL for 4.10 clusters

It seems the 4.10 builds lack the proper url to perform these tasks
Error:
TASK [bm-post-cluster-install : Determine metal3 provisioning URL] *********************************************************************************************************************************
Tuesday 22 February 2022  17:06:02 +0000 (0:00:00.032)       1:01:40.518 ******
changed: [f04-h17-b07-5039ms.rdu2.scalelab.redhat.com]

TASK [bm-post-cluster-install : Set download url] **************************************************************************************************************************************************
Tuesday 22 February 2022  17:06:02 +0000 (0:00:00.349)       1:01:40.867 ******
fatal: [f04-h17-b07-5039ms.rdu2.scalelab.redhat.com]: FAILED! => {"msg": "The task includes an option with an undefined variable. The error was: 'dict object' has no attribute 'provisioningOSDownloadURL'\n\nThe error appears to be in '/root/acm-ztp/jetlag/ansible/roles/bm-post-cluster-install/tasks/main.yml': line 114, column 5, but may\nbe elsewhere in the file depending on the exact syntax problem.\n\nThe offending line appears to be:\n\n\n  - name: Set download url\n    ^ here\n"}

And the provisionings object:
# oc get provisionings provisioning-configuration -o yaml
apiVersion: metal3.io/v1alpha1
kind: Provisioning
metadata:
  creationTimestamp: "2022-02-22T16:19:28Z"
  finalizers:
  - provisioning.metal3.io
  generation: 2
  name: provisioning-configuration
  resourceVersion: "9759"
  uid: e5cb49a0-4514-4289-8653-ccc95225c001
spec:
  preProvisioningOSDownloadURLs: {}
  provisioningNetwork: Disabled
status:
  generations:
  - group: apps
    hash: ""
    lastGeneration: 1
    name: metal3
    namespace: openshift-machine-api
    resource: deployments
  - group: apps
    hash: ""
    lastGeneration: 1
    name: metal3-image-cache
    namespace: openshift-machine-api
    resource: daemonsets
  - group: admissionregistration.k8s.io
    hash: ""
    lastGeneration: 1
    name: baremetal-operator-validating-webhook-configuration
    namespace: ""
    resource: validatingwebhookconfigurations
  - group: apps
    hash: ""
    lastGeneration: 1
    name: metal3-image-customization
    namespace: openshift-machine-api
    resource: deployments
  observedGeneration: 2
  readyReplicas: 0

Fixed by #196

repo: redhat-performance/jetlag


text:
User mgmt changes PCM-1445

@pbathia @renujhamtani Please review

Reviewed. Looks good.

I will merge this once udsjs changes are merged.

authors: gandhikeyur pbathia renujhamtani


text:
root passwd

I want to know the root password.
because I want to edit the .conf file but I do not have permission.

You can use the user 'hunter' with password 'hunter' in sudo mode to do that.

hunter's privilege can‘t edit /usr/sbin/sshd
need root password

authors: RedTeamWing SudhanshuC soonkwan

repo: redhuntlabs/RedHunt-OS


text:
Would be nice to have a way to extend the TTL on an RLock

Is your feature request related to a problem? Please describe.
I have some situations where I'd like to keep the lock acquired for potentially a long time, but I don't find out until I've held it for a while.  I don't want to set a long TTL because I might finish soon; I basically need to extend the acquisition of the lock in increments.
Describe the solution you'd like
A simple RLock.setNewTTL() method, or similar.
Describe alternatives you've considered
https://redis.io/topics/distlock describes how this can be accomplished by sending a Lua script:
If the work performed by clients is composed of small steps, it is possible to use smaller lock validity times by default, and extend the algorithm implementing a lock extension mechanism. Basically the client, if in the middle of the computation while the lock validity is approaching a low value, may extend the lock by sending a Lua script to all the instances that extends the TTL of the key if the key exists and its value is still the random value the client assigned when the lock was acquired.
It would be nice if Redisson's RLock API could take care of this for you.  Apologies if there's already a way to do this that I missed.

RLock lock = redissonClient.getLock("myLock");
if (lock.tryLock()) {
    try {
        // Your long-running task here
        // Extend lock TTL when needed
        String script = "if redis.call('get', KEYS[1]) == ARGV[1] then return redis.call('pexpire', KEYS[1], ARGV[2]) else return 0 end";
        RFuture<Boolean> future = commandExecutor.evalWriteAsync(lock.getName(), LongCodec.INSTANCE, script,
            RLock.REDISSON_LOCK_PREFIX + lock.getName(), lock.getLockId(), 30000); // extend by 30 seconds
        future.await(); // Wait for the script execution to complete

        // More work here...
    } finally {
        lock.unlock();
    }
}

authors: ljluestc steveyegge

repo: redisson/redisson


text:
Does RLocalCachedMap get invalidated with the changes in Redis-Server ?

Hi,
My use case:
I have a single node application(MyApplication) which uses RLocalCachedMap (say testMap)to communicate with redis-server and also cache data locally in aplication.
On the other hand there is another Non java application say anotherApplication(which we have no control of) will update the data in redis-server on same map testMap.
In which case, does RLocalCachedMap in  MyApplication will invalidate the local cache entries when there is change in redis server ?
LocalCachedMapOptions<String, String> options = LocalCachedMapOptions.<String, String>defaults()
                .evictionPolicy(LocalCachedMapOptions.EvictionPolicy.LRU)
                .syncStrategy(LocalCachedMapOptions.SyncStrategy.INVALIDATE)
                .reconnectionStrategy(LocalCachedMapOptions.ReconnectionStrategy.CLEAR)
                .storeMode(LocalCachedMapOptions.StoreMode.LOCALCACHE_REDIS)
                .cacheSize(1000)
                .cacheProvider(LocalCachedMapOptions.CacheProvider.REDISSON);

If not, how would you suggest to implement Redis Server assisted client side caching (https://redis.io/topics/client-side-caching)?
Is there a way that i can use listen to redis-server invalidation events and keep the local cache in sync with redis-server data (with or without RLocalCachedMap as Its not mandate for use to use RLocalCahedMap). ?
Please suggest.

not, RLocalCachedMap sync invalidate msg by redis pubsub topic:  {}:topic
invalidate msg is: org.redisson.cache.LocalCachedMapInvalidate, which contains invalidated hash keys.
see org.redisson.cache.LocalCacheListener


text:
While run task Unable to inject Spring beans

My config class：
@Configuration(proxyBeanMethods = false)
public class DistributedExecutorServiceConfig {
    @Bean(destroyMethod = "")
    public RScheduledExecutorService executorService(RedissonClient redissonClient, ConfigurableListableBeanFactory beanFactory) {
        ExecutorOptions defaults = ExecutorOptions.defaults()
                .taskRetryInterval(2, TimeUnit.SECONDS);
        RScheduledExecutorService executorService = redissonClient
                .getExecutorService("alarm-task-executor", defaults);
        WorkerOptions workerOptions = WorkerOptions.defaults().workers(5).beanFactory(beanFactory);
        executorService.registerWorkers(workerOptions);
        if (executorService.isShutdown()) {
            executorService.delete();
            executorService = redissonClient.getExecutorService("alarm-task-executor", defaults);
            executorService.registerWorkers(workerOptions);
        }
        return executorService;
    }
}

my task class:
public class AlarmExceptionRequestDistributedJob implements Runnable, Serializable {
    @JsonIgnore
    private final Logger logger = LoggerFactory.getLogger(getClass());
    @JsonIgnore
    private final String datePattern = "yyyy-MM-dd HH:mm:ss.SSS";
    @JsonIgnore
    private transient final ThreadLocal<SimpleDateFormat> tlDateFormat = ThreadLocal.withInitial(() -> new SimpleDateFormat(datePattern));
    private static final String esProtectiveLogIndex = Constants.ES_PROTECTIVE_LOG_INDEX;
    private AlarmPolicyDTO alarmPolicyDTO;
    @JsonIgnore
    @Autowired
    private BizProtectedObjectMapper bizProtectedObjectMapper;
    @JsonIgnore
    @Autowired
    private EmailSendService emailSendService;
    @JsonIgnore
    @Autowired
    private AliyunSMService aliyunSMService;

    /**
     * 不要删除这个空构造函数，在Jackson序列化时要用
     */
    public AlarmExceptionRequestDistributedJob() {
    }

    public AlarmExceptionRequestDistributedJob(AlarmPolicyDTO alarmPolicyDTO) {
        this.alarmPolicyDTO = alarmPolicyDTO;
    }

    @Override
    public void run() {
        AlarmPolicyDTO alarmPolicy = alarmPolicyDTO;
        BizAlarmPolicy.AlarmType type = alarmPolicy.getType();
        if (!type.equals(BizAlarmPolicy.AlarmType.EXCEPTION_REQUEST)) {
            return;
        }
        Long protectedId = alarmPolicy.getProtectedId();
        //BizProtectedObjectMapper protectedObjectMapper = beanFactory.getBean(BizProtectedObjectMapper.class);
        BizProtectedObject bizProtectedObject = bizProtectedObjectMapper.selectById(protectedId);
        if (bizProtectedObject == null)
            return;
        //omit...
    }
}

then when task running，throw exception：
2022-02-08 18:52:57.107 ERROR 7748 [  redisson-3-16] (ssonExecutorRemoteService.java:120) : Can't execute: RemoteServiceRequest [requestId=01a9496cb666c612eac5ceb6de3c1b70e6, methodName=scheduleAtFixedRate, signature=[2954431956196527280, 5708544082777223948], args=[org.redisson.executor.params.ScheduledAtFixedRateParameters@5f589620], options=RemoteInvocationOptions[ackTimeoutInMillis=null, executionTimeoutInMillis=null], date=1644317002124]

java.lang.reflect.InvocationTargetException: null
	at sun.reflect.GeneratedMethodAccessor129.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at org.redisson.executor.RedissonExecutorRemoteService.invokeMethod(RedissonExecutorRemoteService.java:106)
	at org.redisson.RedissonRemoteService.lambda$executeMethod$11(RedissonRemoteService.java:456)
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
	at java.util.concurrent.FutureTask.run$$$capture(FutureTask.java:266)
	at java.util.concurrent.FutureTask.run(FutureTask.java)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
	at io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
	at java.lang.Thread.run(Thread.java:748)
Caused by: java.lang.IllegalStateException: Unable to initialize codec with ClassLoader parameter
	at org.redisson.executor.TasksRunnerService.decode(TasksRunnerService.java:324)
	at org.redisson.executor.TasksRunnerService.executeRunnable(TasksRunnerService.java:342)
	at org.redisson.executor.TasksRunnerService.scheduleAtFixedRate(TasksRunnerService.java:128)
	... 12 common frames omitted
Caused by: org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'null': Unsatisfied dependency expressed through field 'bizProtectedObjectMapper'; nested exception is org.springframework.beans.factory.NoSuchBeanDefinitionException: No qualifying bean of type 'com.cssth.web.biz.dao.mapper.BizProtectedObjectMapper' available: expected at least 1 bean which qualifies as autowire candidate. Dependency annotations: {@com.fasterxml.jackson.annotation.JsonIgnore(value=true), @org.springframework.beans.factory.annotation.Autowired(required=true)}
	at org.springframework.beans.factory.annotation.AutowiredAnnotationBeanPostProcessor$AutowiredFieldElement.inject(AutowiredAnnotationBeanPostProcessor.java:643)
	at org.springframework.beans.factory.annotation.InjectionMetadata.inject(InjectionMetadata.java:119)
	at org.springframework.beans.factory.annotation.AutowiredAnnotationBeanPostProcessor.processInjection(AutowiredAnnotationBeanPostProcessor.java:430)
	at org.redisson.executor.SpringTasksInjector.inject(SpringTasksInjector.java:38)
	at org.redisson.executor.TasksRunnerService.decode(TasksRunnerService.java:319)
	... 14 common frames omitted
Caused by: org.springframework.beans.factory.NoSuchBeanDefinitionException: No qualifying bean of type 'com.cssth.web.biz.dao.mapper.BizProtectedObjectMapper' available: expected at least 1 bean which qualifies as autowire candidate. Dependency annotations: {@com.fasterxml.jackson.annotation.JsonIgnore(value=true), @org.springframework.beans.factory.annotation.Autowired(required=true)}
	at org.springframework.beans.factory.support.DefaultListableBeanFactory.raiseNoMatchingBeanFound(DefaultListableBeanFactory.java:1717)
	at org.springframework.beans.factory.support.DefaultListableBeanFactory.doResolveDependency(DefaultListableBeanFactory.java:1273)
	at org.springframework.beans.factory.support.DefaultListableBeanFactory.resolveDependency(DefaultListableBeanFactory.java:1227)
	at org.springframework.beans.factory.annotation.AutowiredAnnotationBeanPostProcessor$AutowiredFieldElement.inject(AutowiredAnnotationBeanPostProcessor.java:640)
	... 18 common frames omitted

2022-02-08 18:52:59.206 ERROR 7748 [   redisson-3-2] (ssonExecutorRemoteService.java:120) : Can't execute: RemoteServiceRequest [requestId=01a9496cb666c612eac5ceb6de3c1b70e6, methodName=scheduleAtFixedRate, signature=[2954431956196527280, 5708544082777223948], args=[org.redisson.executor.params.ScheduledAtFixedRateParameters@4b93023a], options=RemoteInvocationOptions[ackTimeoutInMillis=null, executionTimeoutInMillis=null], date=1644317002124]

java.lang.reflect.InvocationTargetException: null
	at sun.reflect.GeneratedMethodAccessor129.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at org.redisson.executor.RedissonExecutorRemoteService.invokeMethod(RedissonExecutorRemoteService.java:106)
	at org.redisson.RedissonRemoteService.lambda$executeMethod$11(RedissonRemoteService.java:456)
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
	at java.util.concurrent.FutureTask.run$$$capture(FutureTask.java:266)
	at java.util.concurrent.FutureTask.run(FutureTask.java)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
	at io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
	at java.lang.Thread.run(Thread.java:748)
Caused by: java.lang.IllegalStateException: Unable to initialize codec with ClassLoader parameter
	at org.redisson.executor.TasksRunnerService.decode(TasksRunnerService.java:324)
	at org.redisson.executor.TasksRunnerService.executeRunnable(TasksRunnerService.java:342)
	at org.redisson.executor.TasksRunnerService.scheduleAtFixedRate(TasksRunnerService.java:128)
	... 12 common frames omitted
Caused by: org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'null': Unsatisfied dependency expressed through field 'bizProtectedObjectMapper'; nested exception is org.springframework.beans.factory.NoSuchBeanDefinitionException: No qualifying bean of type 'com.cssth.web.biz.dao.mapper.BizProtectedObjectMapper' available: expected at least 1 bean which qualifies as autowire candidate. Dependency annotations: {@com.fasterxml.jackson.annotation.JsonIgnore(value=true), @org.springframework.beans.factory.annotation.Autowired(required=true)}
	at org.springframework.beans.factory.annotation.AutowiredAnnotationBeanPostProcessor$AutowiredFieldElement.inject(AutowiredAnnotationBeanPostProcessor.java:643)
	at org.springframework.beans.factory.annotation.InjectionMetadata.inject(InjectionMetadata.java:119)
	at org.springframework.beans.factory.annotation.AutowiredAnnotationBeanPostProcessor.processInjection(AutowiredAnnotationBeanPostProcessor.java:430)
	at org.redisson.executor.SpringTasksInjector.inject(SpringTasksInjector.java:38)
	at org.redisson.executor.TasksRunnerService.decode(TasksRunnerService.java:319)
	... 14 common frames omitted
Caused by: org.springframework.beans.factory.NoSuchBeanDefinitionException: No qualifying bean of type 'com.cssth.web.biz.dao.mapper.BizProtectedObjectMapper' available: expected at least 1 bean which qualifies as autowire candidate. Dependency annotations: {@com.fasterxml.jackson.annotation.JsonIgnore(value=true), @org.springframework.beans.factory.annotation.Autowired(required=true)}
	at org.springframework.beans.factory.support.DefaultListableBeanFactory.raiseNoMatchingBeanFound(DefaultListableBeanFactory.java:1717)
	at org.springframework.beans.factory.support.DefaultListableBeanFactory.doResolveDependency(DefaultListableBeanFactory.java:1273)
	at org.springframework.beans.factory.support.DefaultListableBeanFactory.resolveDependency(DefaultListableBeanFactory.java:1227)
	at org.springframework.beans.factory.annotation.AutowiredAnnotationBeanPostProcessor$AutowiredFieldElement.inject(AutowiredAnnotationBeanPostProcessor.java:640)
	... 18 common frames omitted

2022-02-08 18:53:01.314 ERROR 7748 [   redisson-3-4] (ssonExecutorRemoteService.java:120) : Can't execute: RemoteServiceRequest [requestId=01a9496cb666c612eac5ceb6de3c1b70e6, methodName=scheduleAtFixedRate, signature=[2954431956196527280, 5708544082777223948], args=[org.redisson.executor.params.ScheduledAtFixedRateParameters@4b9f10ae], options=RemoteInvocationOptions[ackTimeoutInMillis=null, executionTimeoutInMillis=null], date=1644317002124]

java.lang.reflect.InvocationTargetException: null
	at sun.reflect.GeneratedMethodAccessor129.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at org.redisson.executor.RedissonExecutorRemoteService.invokeMethod(RedissonExecutorRemoteService.java:106)
	at org.redisson.RedissonRemoteService.lambda$executeMethod$11(RedissonRemoteService.java:456)
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
	at java.util.concurrent.FutureTask.run$$$capture(FutureTask.java:266)
	at java.util.concurrent.FutureTask.run(FutureTask.java)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
	at io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
	at java.lang.Thread.run(Thread.java:748)
Caused by: java.lang.IllegalStateException: Unable to initialize codec with ClassLoader parameter
	at org.redisson.executor.TasksRunnerService.decode(TasksRunnerService.java:324)
	at org.redisson.executor.TasksRunnerService.executeRunnable(TasksRunnerService.java:342)
	at org.redisson.executor.TasksRunnerService.scheduleAtFixedRate(TasksRunnerService.java:128)
	... 12 common frames omitted
Caused by: org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'null': Unsatisfied dependency expressed through field 'bizProtectedObjectMapper'; nested exception is org.springframework.beans.factory.NoSuchBeanDefinitionException: No qualifying bean of type 'com.cssth.web.biz.dao.mapper.BizProtectedObjectMapper' available: expected at least 1 bean which qualifies as autowire candidate. Dependency annotations: {@com.fasterxml.jackson.annotation.JsonIgnore(value=true), @org.springframework.beans.factory.annotation.Autowired(required=true)}
	at org.springframework.beans.factory.annotation.AutowiredAnnotationBeanPostProcessor$AutowiredFieldElement.inject(AutowiredAnnotationBeanPostProcessor.java:643)
	at org.springframework.beans.factory.annotation.InjectionMetadata.inject(InjectionMetadata.java:119)
	at org.springframework.beans.factory.annotation.AutowiredAnnotationBeanPostProcessor.processInjection(AutowiredAnnotationBeanPostProcessor.java:430)
	at org.redisson.executor.SpringTasksInjector.inject(SpringTasksInjector.java:38)
	at org.redisson.executor.TasksRunnerService.decode(TasksRunnerService.java:319)
	... 14 common frames omitted

Expect your help，thanks！

Caused by: org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'null': Unsatisfied dependency expressed through field 'bizProtectedObjectMapper'; nested exception is org.springframework.beans.factory.NoSuchBeanDefinitionException: No qualifying bean of type 'com.cssth.web.biz.dao.mapper.BizProtectedObjectMapper' available: expected at least 1 bean which qualifies as autowire candidate. Dependency annotations: {@com.fasterxml.jackson.annotation.JsonIgnore(value=true), @org.springframework.beans.factory.annotation.Autowired(required=true)}

I think you need to check your dependencies.

I want to know how to solve this problem. I have encountered the same problem?

I still haven't solved it！

Caused by: org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'null': Unsatisfied dependency expressed through field 'bizProtectedObjectMapper'; nested exception is org.springframework.beans.factory.NoSuchBeanDefinitionException: No qualifying bean of type 'com.cssth.web.biz.dao.mapper.BizProtectedObjectMapper' available: expected at least 1 bean which qualifies as autowire candidate. Dependency annotations: {@com.fasterxml.jackson.annotation.JsonIgnore(value=true), @org.springframework.beans.factory.annotation.Autowired(required=true)}

I think you need to check your dependencies.

Can you give an example of configuring Spring beans dependencies when run task?

authors: CarryWll cloudgyb mrniko


text:
Add Page redirect management

When porting a CMS to Redkite url's need to be remapped/redirected to new url's.
Currently there is no place to do this and this should be added (in my opinion).
Also when changing published page/seo permalink support should be added to auto generate permanent redirect for these pages.
I will probably start work on this next week but please let me know if you are already working on this or if you have a better idea.

No more appliable

authors: boekkooi janxin

repo: redkite-labs/RedKiteCms


text:
Mono price 6-Zone Amp Plugin

https://community.smartthings.com/t/russound-multi-zone-controller-integration/41203/19

If you merge this pull req, you will want to update the icon URLs in the groovy files.

Done!  And thanks for your contribution!!!

authors: redloro tcjennings

repo: redloro/smartthings


text:
Show position on map via OSM not working

From @einervonvielen on April 22, 2014 15:21
Steps:

Setting > Channel Settings > Use Browser Location: = checked
Share something
Klick on the link "Map" (next to my avatar)
The browser opens http://nominatim.openstreetmap.org/?lat=54.3443447&lon=13.5030036&zoom=17

Expected

An OSM map (zoom 17) is shown with marker for the location

Observed

An OSM map of the world is shown but WITHOUT marker for the location

Proposed solution

Use https://www.openstreetmap.org/#map=17/54.34434/13.50300

Copied from original issue: friendica/red#426

From @pafcu on October 18, 2014 16:31
This seems to have been fixed by friendica/red-addons@ee88304b83487711bbec11580faae3b7f34599c3

From @dawnbreak on April 23, 2014 12:50
This is still on my list. Nominatim is for reverse geocoding, looking up names in the OSM database. You have lat/lon if you use browser location and can point directly to the map. But it is also still the old syntax for parameters. Will take a look this week.

repo: redmatrix/redmatrix


text:
Show selected collection in matrix

From @zzottel on December 5, 2013 16:46
If I choose to view only one collection, there is no visual indication that I'm not seeing the whole stream.
This is the case in several themes I tested, so I hope there's a possibility to fix that for them all in a template or something?
Copied from original issue: friendica/red#224

From @zzottel on December 6, 2013 15:51
Fixed, thanks.


text:
doc: update to beta

Updates docs to beta

This LGTM. Btw could we also update the Github release 0.9.0 to mention that 0.9.0 is the first beta release of the provider?

authors: david-yu gene-redpanda