text:
Errors building ReactiveUI solution

Do you want to request a feature or report a bug?
Bug
What is the current behavior?
When I pull down the latest on ReactiveUI open the solution in Visual Studio 2017 15.4, I get build errors.  I am unable to build the source code on my local machine.
If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem
Below is a gist containing the list of build errors I am seeing.
I am running Visual Studio 2017 15.4
dotnet --version returns 1.1 but I am sure I have other versions installed.
What is the expected behavior?
The expected behavior is that I am able to build the source code on my local machine.
What is the motivation / use case for changing the behavior?
I wanted to work on issues blocking the 8.0 release.
Which versions of ReactiveUI, and which platform / OS are affected by this issue? Did this work in previous versions of ReativeUI? Please also test with the latest stable and development snapshot
This is not an issue with consumption of ReactiveUI, more an issue that I can't work on the source code.
Other information (e.g. stacktraces, related issues, suggestions how to fix)
https://gist.github.com/RLittlesII/cf1672088522ab9d3b18135e0df899d3
Some of the errors are valid which I see in the project they are set "Warnings as Errors" which are the NU1202 errors, although I am still not sure how to solve those.

Thanks for reporting this.
Can I check a couple of things

do you know which workloads you have installed
would you be able to do git reset HEAD --hard and git clean -fdx
is this from within VS, or is this the output of running build.cmd?

I updated my fork and don't see this issue anymore.  I was getting this from the command line running .\build.cmd in Power Shell.

Thanks for confirming, shout if you hit similar problems again!

authors: RLittlesII olevett

repo: reactiveui/ReactiveUI


text:
Translate React DOM Elements

[x] Overview
[x] Differences in attributes

[x] checked

[x] className

[x] dangerouslySetInnerHTML

[x] htmlFor

[x] onChange

[x] selected

[x] style

[x] suppressContentEditableWarning

[x] supressHydrationWarning

[x] value

[x] All Supported HTML attributes

Line 19 - İstisnalar aria-* və data-* atributlarıdır:  bu atributlar kiçik hərf ilə yazılmalıdır. Məsələn, siz aria-label atributunu aria-label kimi saxlaya bilərsiniz.
Line 33 - Əgər siz React-i Veb Komponentlər ilə işlədirsinizsə (nadir haldır) class atributu işlədin.
Line 37 - Bu səbəbdən HTML-i birbaşa React-ə...
Line 80 - Nəzərə alın ki, stillər avtomatik prefikslənmirlər.
Line 196 - Kiçik hərf istifadə etdiyiniz müddətdə siz xüsusi atributlar da işlədə bilərsiniz.

source: gharchive/pull-request

authors: GasimGasimzada azizaismayilova

license_type: permissive

license_source: github-api


text:
Server side rendering not working

I cant get react-art to render on the server because it relies on:
require('art/modes/fast'); // Flip this to DOM mode for debugging
line 14 ReactART.js
is it possible to load library in a server mode? or some mode option?

No, react-art doesn't support server-side rendering.

k, i'll just add it to my fork. i can do a pull request if you think it something other people would want

At least not crashing on the server would be nice

source: gharchive/issue

authors: equalbackslash eranimo spicyj

repo: reactjs/react-art

license_source: bigquery


text:
documentation inaccurate for props.location

According to the documentation if I want to access props.location it tells me I should add it to the context.

Access location from this.props.location of your Route component. If you'd like to get it deeper in the tree, you can use whatever conventions your app has for getting props from high down low. One option is to provide it on context yourself

When I do this it tells me:

context.location is deprecated, please use a route component's props.location instead. http://tiny.cc/router-accessinglocation

But it doesn't have props.location.  Which is the whole reason I added it to the context.
I tried adding withRouter because the documentation states:

NOTE: v2.4.0 and higher include a higher-order component withRouter that is now the (highly) recommended way of accessing the router object.

But I don't see any way to get access to location from the router object and withRouter doesn't add props.location to the wrapped component.
What is the recommended approach to accessing location when not a top level route component?  This should be documented.

I'm seeing that there was a PR (https://github.com/reactjs/react-router/pull/3444) that adds props.location when you use withRouter but it is not yet available.
The latest in npm is 2.4.1 and the documentation is very confusing and provides no path forward.
Should the documentation be updated telling people to use 3.0 alpha and check it out from github instead of npm?  What's the best route forward?
Another possibility is updating npm to have a version that includes #3444.

The recommendation is to put location on context yourself, not use the deprecated built-in one
That code is released on the v3 alpha

Maybe I'm missing something.  Not sure what you mean by the deprecated built-in one.  There is no context.location by default.  I added it to the context myself from a route component and then pulled in the context with a child component.  When I do that I see the deprecation warning telling me not to use context.location.  If that is the recommended route, then why is it telling me not to do that?

You are not correctly exporting location on context, then. That deprecation warning only shows up if you're somehow hitting the deprecated export of context.

authors: brennancheung taion

repo: reactjs/react-router

license: mit


text:
Translate blog\2018-10-01-create-react-app-v2.md

之前都是在线编辑的，结果发现有冲突。由于这个仓库太难下载，所以还需要一段时间解决冲突。

冲突我来解决吧~

冲突我来解决吧~

貌似你不好解决吧？

不过有点奇怪的是，我反向合并到我的主干，居然也有冲突：https://github.com/hstarorg/zh-hans.reactjs.org/pull/2

提到的冲突还没有解决 @QC-L

把冲突解决了。。。

尴尬，忙忘了...

authors: QC-L hijiangtao hstarorg


text:
[beta]: docs(cn): add-react-to-a-website

@QC-L

Review 完毕，译者已经修改。cc @QC-L  @Atrist


text:
Configured ESLint and Prettier

Description
I have configured ESLint and Prettier in our project. This will ensure that everyone is following the same code standards.
It fixes #263
https://github.com/reactplay/react-play/discussions/277
Type of change
Please delete options that are not relevant.

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

How Has This Been Tested?
I have tested it on my local machine. Everything is working as it should be.
Read Before Merging

Around 180 files have been modified with this PR. However, most of them are results of ESlint and Prettier commands. Things like whitespace, commas, blank lines, and quotes are the ones which are affected mostly.
This PR doesn't solve everything. There are still many (thousands) of warnings/errors that have to be solved manually. These are mostly related to simple coding discussions taken during the development such as:

A variable is declared in underscore_case instead of camelCase
unused variables
JSX in .js files
and so on.

Suggestions

Fix easily fixable warnings/errors by ourselves.
Add more rules in ...ignore files
Request contributors to fix their changes if possible.

What next?

Assuming everyone is using VSCode, installing Prettier and ESLint would be great, though not necessary.
Currently, running yarn format before committing the code is suggested. This command will make the necessary changes in your codebase. If an error occurs during the procedure, it will throw an error at the end, but it is fine.
We can add a husky pre-push hook that will make sure that code is formatted and has no errors before pushing to a branch. (I Strongly suggest this)

Checklist:

[x] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] My changes generate no new warnings
[x] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes
[] Any dependent changes have been merged and published in downstream modules

Hello @atapas, @koustov
Any thoughts here?

Yes, let's plan for this Friday evening! Or if you want to schedule earlier, I am fine with that too.

is this being taken care?

repo: reactplay/react-play

license: MIT


text:
Add JSON schema references for each model item (code comments)

https://github.com/readium/webpub-manifest/tree/master/schema

Maybe - test runner to automate checks using validator:
https://github.com/readium/r2-streamer-js/blob/develop/src/utils/json-schema-validate.ts
https://github.com/readium/r2-streamer-js/blob/develop/src/http/server-manifestjson.ts#L289-L313

Done, for r2-opds-js too.


text:
Search in readium over book

Is there an option to search for text over book content,over all pages in all chapters?
Currently i don't have this option.

We already have an issue recorded for that:
https://github.com/readium/readium-js/issues/17
We do not have a concrete plan / schedule for implementing this feature though. It all depends on programmer resources (+ developer contributions). Right now there are a bunch of other high-priority issues to address, so watch this space!

How to implement text search over entire book using norch.js?

How to implement text search over entire book on readium. Which version previosly integrated. I checked all version. Still i cant able to check that

repo: readium/readium-js-viewer


text:
update japanese message

General Instructions
This pull request is a Work In Progress
Additional information
I add localized strings reference to en-US/message.json.
There are some strings remaind English.

Hello, thank you!
Could you please change the PR target from master to develop? (use the "edit" button)

I already posted a couple of comments (see above, inlined in this discussion thread).
However, there are a number of non-translated strings (still in English). Does this mean this PR is not ready yet? Or do you need help to clarify the meaning / usage in the User Interface?

authors: danielweck toshiakikoike


text:
Add quicker quickstart and rebrand previous quickstart as a demo

The new quickstart doesn't do much aside from show how to connect ReadySet to an existing db, but we want to see if that's what more users want.

Got thumbs up from @alanamarzoev.

repo: readysettech/docs


text:
[Java] Version interface to allow testing usage of it

This should allow to verify logic of validating versions in a test.
constants are still there for the cases where access to version info is on the hot path (+ regardless JIT might optimize it anyway?)

LGTM.

repo: real-logic/aeron


text:
[Java] Remove source of garbage when cancelling missed timers

Use of the Predicate was causing the long values to be auto-boxed to Long.

Damn JIT not smart enough.


text:
Use Java's least common denominator for random access lists

Hi,
Could you accept this minor change so that we can do unordered removals using AbstractList instead of ArrayList? Seems a pity/inconsistent to not be able to use this on org.agrona.collections.IntArrayList and org.agrona.collections.LongArrayList.
An alternative would be to have the latter extend ArrayList instead of AbstactList.
This would of course cause boxing in the "list.set(index, list.remove(lastIndex));" line so maybe it's even better to just add a "removeUnordered" in IntArrayList / LongArrayList themselves?

Why not List?
ListUtil or UnorderedListUtil seems like a more descriptive name...

Are you referring to the name of the org.agrona.collections.ArrayListUtil class that I modified? It was already named as such, I did not want to change it because it might break API with client code (e.g. Aeron) that uses it.
I think the name of this class was meant to point out that it is supposed to be used on direct-access lists (array based) otherwise "fastUnorderedRemove" is not really fast. Right now it picks the last item and uses it to overwrite the item being removed (reducing the collection size by 1).
Like I said, I wanted to use it in combination with org.agrona.collections.IntArrayList  and org.agrona.collections.LongArrayList but these extend java.util.AbstractList.
I actually changed my mind now; I think it's better to just implement these as methods in IntArrayList/LongArrayList to make sure there is no boxing of the primitives possible so I am closing this. I will submit a request to add fast unordered remove in those 2 instead.

authors: JanStureNielsen karypid

repo: real-logic/agrona


text:
hide default.realm and other realm files/folders from itunes sharing?

Is there an option for hiding realm files from itunes sharing?  I would like to turn it on for my users to allow them to download videos taken by the app but don't want them messing with the realm files.

Filenames starting with a dot (.) will not appear in iTunes file sharing, so you can just change the path of the default realm to .default.realm.

Ah perfect.  Thanks for the help.

authors: byjoh tgoyne

repo: realm/realm-cocoa


text:
Crash when create RLMArray

Goals
Create RLMArray of subclasses RLMObject in Swift
Actual Results
After run project Realm throw exception
Terminating app due to uncaught exception 'RLMException', reason: 'Property 'array' is declared as 'id', which is not a supported RLMObject property type. All properties must be primitives, NSString, NSDate, NSData, NSNumber, RLMArray, RLMLinkingObjects, or subclasses of RLMObject. See https://realm.io/docs/objc/latest/api/Classes/RLMObject.html for more information.'
Steps to Reproduce
In subclass of RLMObject create RLMArray of subclasses RLMObject, run project
Code Sample
class Class: RLMObject {

    @objc dynamic var array = RLMArray(objectClassName: Class2.className())

    override init() {
        super.init()
    }
}

class Class2: RLMObject {
@objc dynamic var number: Int = 0
    override init() {
        super.init()
    }
}

Version of Realm and Tooling
Realm framework version: 0.94
Xcode version: 9.4.1
iOS/OSX version:  11
Swift version: 3.3.2

Closing this issue due to age, if you have any other questions please open a new issue.
Thanks.


text:
[Query] Make sure that linked objects are attached

Without that change, if you query for an object, which is linked to a just newly created object, which was never attached to the Realm, you get something arbitrary returned.

[ ] Changelog
[ ] Check whether object is in the same realm as the one being queried
[ ] Fix RealmCollectionTypeTests.testArrayAggregateWithSwiftObjectDoesntThrow Swift tests

This makes all the RealmCollectionTypeTests.testArrayAggregateWithSwiftObjectDoesntThrow Swift tests fail.

There also needs to be a check for the object being in the same realm as the one being queried.
I don't think this needs to be an error, though. Rather than throwing it could just insert a FalseExpression node.

I don't think this needs to be an error, though. Rather than throwing it could just insert a FalseExpression node.

But you mean here that you would effectively return an empty result if the object isn't attached? I'm not sure if that's a good idea. It seems like it could be a programmer error in most cases.

indexOfObject: already does that.

indexOfObject: already does that.

Even though it would be a breaking semantic change, I'd lean towards changing the behavior of indexOfObject: to fail irrecoverably in that case as well.

I don't think it's unreasonable to have a function which can operate on either standalone or persisted objects in the same way. Sort of the opposite, actually; ideally anything which doesn't involve a write transaction should rarely need to care if the objects it's given are persisted in a realm (or persisted in the same realm, for that matter). The semantics of searching for an object that happens to not be persisted in the realm being searched seems perfectly well-formed to me, so I see no reason to just arbitrarily make it an error.

I think there are different models, in which both behaviors are well-formed, while they are not in the other. If we want to stick with the latter, I'd still strongly suggest that we highlight the behavior in this specific case in the documentation of affected methods.

@tgoyne: How would you validate whether the realms are the same? In the function there is no reference to the RLMRealm accessible for which the query is built.

query.get_table()->get_link_target(column).get() == obj->_row.get_table() would cover both the object being from a different realm and being the wrong class (which currently also doesn't appear to be checked anywhere?).

Yes, doesn't seem like that's checked so far. But good idea! Thanks :+1:

@tgoyne: This seems to be ready now to merge. Can you give it another review pass?

:+1:

authors: jpsim mrackwitz tgoyne


text:
specify Xcode version in Jenkins jobs

Addresses #4620

This will need to be amended once we want to resume running jobs with non-default Swift toolchains again (such as when Xcode 9 comes out with a Swift 3 compilation mode) but for now this should be sufficient.

Do the release scripts need to be updated as well so that we don't accidentally cut a release using the 8.3 beta?

You're right @tgoyne, done in ee64c1f.

authors: jpsim tgoyne


text:
Crash when calling flexible_sync_configuration() from an audio plugin

I am testing using Realm sync from within an audio plugin, using the JUCE library.
The standalone build works without issues, but the VST3 plugin fails when calling flexible_sync_configuration().
Below is the stack trace. I'm on macOS.
__pthread_kill 0x00000001a0048724
pthread_kill 0x00000001a007fc28
abort 0x000000019ff8dae8
please_report_this_issue_in_github_realm_realm_core_v_13_23_1() terminate.cpp:65
realm::util::terminate_internal(std::basic_stringstream<…> &) terminate.cpp:143
realm::util::terminate_with_info(const char *, const char *, long, const char *, std::initializer_list<…> &&) terminate.cpp:162
realm::util::terminate(const char *, const char *, long, std::initializer_list<…> &&) terminate.cpp:149
realm::SyncManager::path_for_realm(const realm::SyncConfig &, std::optional<…>) const sync_manager.cpp:559
realm::internal::bridge::sync_manager::path_for_realm(const realm::internal::bridge::realm::sync_config &) const sync_manager.cpp:7
realm::user::flexible_sync_configuration() const app.hpp:144
AudioPluginAudioProcessorEditor::AudioPluginAudioProcessorEditor(AudioPluginAudioProcessor &) PluginEditor.cpp:13
AudioPluginAudioProcessorEditor::AudioPluginAudioProcessorEditor(AudioPluginAudioProcessor &) PluginEditor.cpp:7
AudioPluginAudioProcessor::createEditor() PluginProcessor.cpp:164
juce::AudioProcessor::createEditorIfNeeded() juce_AudioProcessor.cpp:893
juce::JuceVST3EditController::JuceVST3Editor::ContentWrapperComponent::createEditor(juce::AudioProcessor &) juce_audio_plugin_client_VST3.cpp:2092
juce::JuceVST3EditController::JuceVST3Editor::createContentWrapperComponentIfNeeded() juce_audio_plugin_client_VST3.cpp:2272
juce::JuceVST3EditController::JuceVST3Editor::JuceVST3Editor(juce::JuceVST3EditController &, juce::JuceAudioProcessor &) juce_audio_plugin_client_VST3.cpp:1743
juce::JuceVST3EditController::JuceVST3Editor::JuceVST3Editor(juce::JuceVST3EditController &, juce::JuceAudioProcessor &) juce_audio_plugin_client_VST3.cpp:1742
juce::JuceVST3EditController::createView(const char *) juce_audio_plugin_client_VST3.cpp:1267
<unknown> 0x0000000106b10d64
<unknown> 0x0000000106b0b6ec
<unknown> 0x0000000106b0b570
<unknown> 0x0000000106b1ac14
<unknown> 0x0000000106ab1348
<unknown> 0x0000000106a97b98
<unknown> 0x0000000106a97c34
<unknown> 0x000000010552ecac
<unknown> 0x00000001055285ac
<unknown> 0x0000000106a97a58
<unknown> 0x0000000106aaa340
<unknown> 0x000000010568d548
<unknown> 0x000000010568be90
<unknown> 0x0000000105412654
<unknown> 0x00000001054121d0
<unknown> 0x0000000105620c9c
__NSFireTimer 0x00000001a110e448
__CFRUNLOOP_IS_CALLING_OUT_TO_A_TIMER_CALLBACK_FUNCTION__ 0x00000001a01783c8
__CFRunLoopDoTimer 0x00000001a0178070
__CFRunLoopDoTimers 0x00000001a0177bc8
__CFRunLoopRun 0x00000001a015d348
CFRunLoopRunSpecific 0x00000001a015c4b8
RunCurrentEventLoopInMode 0x00000001a99a6c40
ReceiveNextEventCommon 0x00000001a99a6a7c
_BlockUntilNextEventMatchingListInModeWithFilter 0x00000001a99a67d4
_DPSNextEvent 0x00000001a337dd44
-[NSApplication(NSEvent) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] 0x00000001a337cee0
-[NSApplication run] 0x00000001a3371344
<unknown> 0x0000000105620068
start 0x000000019fd27f28

Posted also on realm-core: https://github.com/realm/realm-core/issues/7118

Found the issue: The default path is not accessible from a plugin. Fixed it by setting the "path" value to somewhere the plugin is able to write to.

repo: realm/realm-cpp


text:
Realm Corruption Following Client Resets Due to Permission/Role Changes on Server

How frequently does the bug occur?
Sometimes
Description
We are experiencing corruptions of Realm databases following client resets triggered by permission/role changes on the server. This issue is not reliably reproducible, and unfortunately, we do not have logs to provide more insight. We only have the incorrect Realm files, which we have examined using Realm Studio.
It is suspected that this issue may arise when the client undergoes multiple client resets in quick succession.
It appears there may be flaws in the client reset logic that need to be addressed!
Stacktrace & log output
No response
Can you reproduce the bug?
No
Reproduction Steps
Roughly speaking, our scenario is as follows

We manage SyncPermissions via CustomUser data. Any change in this data typically triggers a client reset.
We handle projects. When a project is added, a Server-Trigger adds a Managed-Team object to the project. This change also modificats our Permission-Properties to the CustomUser data.
A client reset occurs, and usually, everything on the client side appears as it should. However, when a project is deleted, another trigger modifies the CustomUser data changing permissions again, leading to another client reset.

Due to the above workflow, situations may arise where multiple client resets occur in quick succession due to permission/role changes on the server.
However, in some cases, the following issues have been observed:

The ManagedTeam object, which should be added to the Project object by the server trigger, is missing after the client reset.
Lists containing the Project object, or Lists that are included in the project, display incorrect behavior: contents appear duplicated and incorrectly structured (In Realm Studio the List-Elements are duplicated but share the same index(!)) When the Realm is opened in Realm Studio, it seems that identical objects appear duplicated. (Screenshot from RealmStudio attached)

Version
<= 10.49.1
What Atlas Services are you using?
Atlas Device Sync
Are you using encryption?
No
Platform OS and version(s)
macOS
Build environment
Xcode version: ...
Dependency manager and version: ...

That's certainly an odd issue. Two questions
When you examine the data on the server using the Console, is it also duplicated?
Have you examined the data with something other than Realm Studio? e.g. craft up a quick app to read in the local data and output to console?  Then compare that to what's shown in Realm Studio. It would eliminate something funky going on with Realm Studio (which I doubt)

The problem was also synced and could therefore also be seen on the server.
We also saw the problems in our Realm Swift App - that's when we realized that something must be wrong.

Hey @divan84, since this is a sync issue that may require that the team investigates the sync history as well as analyze the server logs, can you please file a support ticket here: http://support.mongodb.com/? The realm-swift repo is primarily used to track bugs with the Realm Swift SDK and engineers working on this project don't have the access necessary to debug server-side problems.

We will contact the support! Thanks!

authors: Jaycyn divan84 nirinchev

repo: realm/realm-swift


text:
[Proposal] Operator: Chunk

Link to .NET 6 Linq documentation
How it will work in Reaqtive:
Input    1    2        3    4        5    |
------------------------------------------------ Chunk(2)
Output        [1, 2]        [3, 4]        [5] |

There is some functional overlap with Buffer which returns an IList<T> for historical reasons (see below), but we should aim for parity with traditional LINQ to Objects, so I approve of the proposal in principle.
One question could be what to do with Buffer overloads such as int count, int skip and the TimeSpan-based variants. For each such overload, do we provide a Chunk alternative that only differs in its result type? I.e. xs.Chunk(args) == xs.Buffer(args).Select(t => t.ToArray()) where Chunk only differs in its performance profile around allocating arrays and potentially just resizing the last one.
I'm thinking we can add Chunk(int size) (matching the parameter name from the Enumerable operator in .NET 6) and Chunk(int size, int skip) as both can be implemented by new T[size] allocations and a single Array.Resize for the last emitted chunk.
The time-based variants don't have such luxury because they can't predict the size of the chunks upfront, which explains why we ended up choosing IList<T> in the Rx days; we have to allocate a list anyway because we don't know the number of elements that will end up in time-based buffers, so we may as well return the list to the user and allow them to mutate it any way they see fit; it's theirs to party on (rather than us then copying it over to a T[] or even just returning it as an IEnumerable<T>). To make all of the Buffer operators consistent in the Rx days, we picked IList<T> for count-based and time-based operators. (We picked an interface to have some flexibility in how we implemented it, not necessarily being tied to List<T>.)
So, in conclusion, my proposal is to have:
IO<T[]> Chunk<T>(IO<T> source, int size);
IO<T[]> Chunk<T>(IO<T> source, int size, int skip);

where IO<T> is the concept of an observable in whatever shape or form it takes (ISubscribable<T> at the operator level, quoted variants higher up). And the operator implementation is based on new T[size] with a Resize for the last chunk. (As such, the implementation isn't a composition of Buffer with Select and ToArray.)
We should also do this work in http://github.com/dotnet/reactive for IObservable<T>, IAsyncEnumerable<T>, and IAsyncObservable<T>.

authors: bartdesmet ronnygunawan

repo: reaqtive/reaqtor


text:
Fix whileEditing to use kebab-case

clearButtonMode in TextInput uses kebab-case.
https://facebook.github.io/react-native/docs/textinput.html#clearbuttonmode

thanks @shritesh

authors: nhducit shritesh

repo: reasonml-community/bs-react-native


text:
When using a HeaderView above PagingViewController how to use custom view controllers rather than UITableViewController?

Whenever I try to use a controller from storyboard I get a crash on tvProfileList (It is a tableView on my custom view controller from storyboard). How should I initialize this as I know that IBOutlets get initialized after push/present
func pagingViewController<T>(_ pagingViewController: PagingViewController<T>, viewControllerForIndex index: Int) -> UIViewController {
    if index < contentViewControllers.count {
        let viewController = self.contentViewControllers[index]
        // Inset the table view with the height of the menu height.
        let height = pagingViewController.options.menuHeight + CustomPagingView.HEADER_VIEW_HEIGHT
        let insets = UIEdgeInsets(top: height, left: 0, bottom: 0, right: 0)
        viewController.tvProfileList.contentInset = insets
        viewController.tvProfileList.scrollIndicatorInsets = insets
        viewController.tvProfileList.delegate = self
        return viewController
    }
    return UIViewController()
}

@rechsteiner Any updates for this?

Hi @ankit0812. This doesn't seem to be an issue related to Parchment. Take a look at the Storyboard example if you want to see how to initialize a view controller from storyboard.

repo: rechsteiner/Parchment


text:
latest_run throws an error if there are no runs in the database

A test should be added for this as well.

Fixed in f94733e882bae395d4bbacab9d25791612ad0cf6

Must still be fixed in the gui (I'll do it)

Oops, I thought they used the same underlying function - sorry!

Well maybe they should use the same underlying function :)

authors: jvdzwaan robintw

repo: recipy/recipy


text:
fix random_string function definition

This } is literal. Check expression (missing ;/\n?) or quote it. [1083] (shellcheck)

Thanks!

authors: dbackeus p-wall

repo: reclaim-the-stack/talos-manager


text:
remove_expired_responses() not imported in init.py

Wanted to remove_expired_responses() like you wrote in your Documentation, but got the Error:
AttributeError: 'module' object has no attribute 'remove_expired_responses'
Because remove_expired_responses() is not imported in __init__.py
My workaround:
from requests_cache import core
core.remove_expired_responses()

Checked the sqlite library and I think it's working.

FYI this hasn't been released in a version yet. Can we get a version bump?

authors: adargu mheppner

repo: reclosedev/requests-cache


text:
💡[Feature]: Exploratory Data Analysis and Demand Predicting for Resort and City Hotels

Is there an existing issue for this?

[X] I have searched the existing issues

Feature Description
This project predicts hotel demand for the next 6 months, aiding room expansion plans and identifying revenue opportunities. Additionally, in depth EDA for data-driven insights to optimize resort operations efficiently.
Use Case

Room expansion planning based on demand forecasts
Revenue optimization through data-driven insights
Operational efficiency improvement strategies

Benefits

Informed room expansion decisions
Maximized revenue opportunities
Streamlined operations for cost efficiency

Add ScreenShots

Priority
High
Record

[X] I have read the Contributing Guidelines
[X] I'm a GSSOC'24 contributor
[X] I want to work on this issue

Please add the necessary labels.

Please add the necessary labels, as I am contributing as part of Hacktoberfest.

please add the necessary labels ,I am new here as contributor .

authors: ShreyasSN singhabhinendra

repo: recodehive/machine-learning-repos


text:
Web catalog: main page is a roster of mugshots

This webpage simply reads specimens_manifest.json and generates a list of images. Each neuron is one image. Probably a single colorized, cropped MinIP. Click on any mugshot to visit the cell's solo personal page, which reads build_artifacts_manifest.json to generates its view. Probably a React app.

Somewhere there is a list of crop bboxes, one for each neuron's MinIP.


text:
Feature/alter user model

Модель пользователя готова, прошу предоставить критику!)

Фото, сортировку, readonly_fields добавил. Жду еще одно ревью и вливаю в develop.


text:
Add BuildConfiguration objects to build RStudio and CUDA R RStudio notebooks oc OCP cluster

This PR fixes:
https://issues.redhat.com/browse/RHOAIENG-1478
https://issues.redhat.com/browse/RHOAIENG-315
This pull request introduces two BuildConfig objects, enabling users to create an RStudio Workbench on their cluster.
The branch that hosts the RStudio dockerfile is hosted on f/rstudio-rhel9 branch
Probably a good enhancement on this implementation is to, have prebuild the base-rhel9 image in order to avoid its build all the time. This enchancment has already stated on this PR: https://github.com/red-hat-data-services/notebooks/pull/123 However, this implementation it stand alone as is now.
How has been Tested
There are two ways to deploy the new Build Configs
The first and the recommended is (Deploy the configs outside from RHOAI):

Login on the cluster:
oc login <ocp cluster url>

Enter on redhat-ods-applications namespace if you use RHOAI or opendatahub if you use ODH
oc project redhat-ods-applications

Create a secret, PM me to provide you testing credentials:
oc create secret generic rhel-subscription-secret --from-literal=USERNAME=<username> --from-literal=PASSWORD=<pass>  --from-literal=BASEURL=<baseurl> --from-literal=SERVERURL=<serverurl> -n redhat-ods-applications

Run the rstudio-buildconfig.yaml file to to deploy the simple version of RStudio:
oc apply -f rstudio-buildconfig.yaml -n redhat-ods-applications
Or run the cuda-rstudio-buildconfig.yaml to build the CUDA version of RStudio:
oc apply -f cuda-rstudio-buildconfig.yaml-n redhat-ods-applications

After creating all the objects, navigate to the BuildConfig and initiate the build process as illustrated in the image:

Once the builds are complete means that the RStudio workbench is ready

To add Workbench to the list of notebooks, start by obtaining the image from the rstudio-rhel9 Image Stream and importing it as a custom notebook, following the instructions in the image below:

Spin up the workbench that you just created

The second way is (Deploy the configs inside RHOAI, as it is implemented already):

Edit the DSC of the operator with the following:

    workbenches:
      devFlags:
        manifests:
          - contextDir: components/odh-notebook-controller/config
            sourcePath: ''
            uri: 'https://github.com/opendatahub-io/kubeflow/tarball/v1.7.0-5'
          - contextDir: components/notebook-controller/config
            sourcePath: ''
            uri: 'https://github.com/opendatahub-io/kubeflow/tarball/v1.7.0-5'
          - contextDir: ''
            sourcePath: base
            uri: >-
              https://github.com/red-hat-data-services/notebooks/tarball/pull/118/head

Create a secret, PM me to provide you testing credentials:
oc create secret generic rhel-subscription-secret --from-literal=USERNAME=<username> --from-literal=PASSWORD=<pass>  --from-literal=BASEURL=<baseurl> --from-literal=SERVERURL=<serverurl> -n redhat-ods-applications

Follow the same steps from (5)  till the end

What's RHOAI 2.7 going to do? The second option? So when I install the Operator, it will automatically deploy the buildconfigs for me, so I then need to create rhel-subscription-secret, and trigger the build?

Created this PR https://github.com/red-hat-data-services/notebooks/pull/127 with two fixes on the CUDA Dockerfile

Created this PR #127 with two fixes on the CUDA Dockerfile

@atheo89 , if we switch to ARG, then we might have to pass in the buildarg on buildconfig:https://docs.openshift.com/container-platform/3.11/dev_guide/builds/build_strategies.html#docker-strategy-build-args
however, i think buildconfig, buildarg doesn't support secrets yet.
https://access.redhat.com/solutions/4501551

if we switch to ARG, then we might have to pass in the buildarg on buildconfig:https://docs.openshift.com/container-platform/3.11/dev_guide/builds/build_strategies.html#docker-strategy-build-args however, i think buildconfig, buildarg doesn't support secrets yet. https://access.redhat.com/solutions/4501551

I will add ENVs on the Dockerfiles as it was

repo: red-hat-data-services/notebooks


text:
/suits/rbd/mirror-thrash/base/

Signed-off-by: harishmunjulur hmunjulu@redhat.com
Description
rpm package format change.
extra_packages:
rpm:
<package_name>
Checklist:

[ ] Create a test case in Polarion reviewed and approved.
[ ] Create a design/automation approach doc. Optional for tests with similar tests already automated.
[ ] Review the automation design
[ ] Implement the test script and perform test runs
[ ] Submit PR for code review and approve
[ ] Update Polarin Test with Automation script details and update automation fields
[ ] If automation is part of Close loop, update BZ flag qe-test_coverage “+” and link Polarion test

logs :
http://pulpito.ceph.redhat.com/hmunjulu-2020-08-24_14:26:11-rbd:mirror-nautilus-distro-basic-argo/384718/

repo: red-hat-storage/ceph


text:
Bug 2107073: [release-4.10] mark enableRookCSICephFS as true always in consumer cluster

We do not want to disable CephFS CSI driver in consumer mode since
CephFS storageclass is available by default.
This is a fix for the problem that ROOK_CSI_ENABLE_CEPHFS is "false" after upgrading the provider cluster alone to ODF 4.11.0.
Fixes-
https://bugzilla.redhat.com/show_bug.cgi?id=2110274
https://bugzilla.redhat.com/show_bug.cgi?id=2107073
This is the manual backport of this PR-https://github.com/red-hat-storage/ocs-operator/pull/1710.
Which was a fix for https://bugzilla.redhat.com/show_bug.cgi?id=2096823. A manual backport was chosen as there was a chain of merge conflicts with automated cherry-pick.

/bugzilla refresh

/hold

/bugzilla refresh

/hold cancel
/retest

/retest

/retest

/retest

/retest

/retest

/retest

/retest

repo: red-hat-storage/ocs-operator


text:
Bug 2277926: [release-4.13] Remove default value of waitTimeoutForHealthyOSDInMinutes

Remove default value of waitTimeoutForHealthyOSDInMinutes from ocs-operator, and only update the SC CR, if a value is provided by the user.

/bugzilla refresh


text:
Limit the length of finalizer if more than 63 char

Signed-off-by: Vineet Badrinath vineetbnath@gmail.com

/test integration-test

/cherry-pick release-4.11

authors: umangachapagain vbnrh


text:
code reformatting and minor fixes

Replaced unnecessary try-catch blocks with if and if-else statements (simpler and more understandable code).
Also made some changes in function choose_words . It now selects all distinct words from wordlist. The previous version had a chance to return duplicate words.
And some other minor edits.

Hey, thanks for the PR. I'm not in favor of replacing try...except in the flagged cases with if...else -  I've added some comments in the commit for your review.

However, if performance is the only reason for using try-except blocks, then too if-else with be more efficient.
Since worddict is a dictionary, the search ( letter in wordict ) happens in constant time O(1). It does searches for every key in worddict. Its value is hashed.

Is it possible to edit this pull request or do I have to close this and create another pull request. If so, the what changes to include?

@goswami-rahul If you push your changes to the same branch, they will be reflected in this PR.

Thanks @ghyde . I'm quite new to GitHub. Opened my first repo this week. :)

PR updated @redacted

Is there something I can add or change to get this PR merged?

Thanks for your work, merged now

authors: ghyde goswami-rahul redacted

repo: redacted/XKCD-password-generator


text:
Expect 'sampled' header to be unicode already

I added a print statement to L221 of baseplate/integration/pyramid/init.py and confirmed that the header is always a unicode object by the time it gets there in both Py2.7 and Py3.7. I don't know why I did this with a byte string, other than potentially stupidly mimicing the .decode("utf8") that was there before my change. That apparently was an unnecessary no-op.
This should fix #278 by properly parsing the header.
cc: @suzie-su

I think the question I have is should TraceInfo.extract_upstream_header_values always return the same type?  I think the reason this started checking against bytes is because that's what it returns for Thrift headers while it's unicode for Pyramid headers.  Do we want to normalize that in extract_upstream_header_values so it always returns either bytes or unicode?  Or do we want that to be a part of the thrift vs pyramid integration (what this PR is doing).

Hmm, I hear ya. I worry that if we put some requirement that the wire contents are unicode compatible it'll limit us, but that's probably YAGNI. Honestly, I don't like that function at all and wish we were still completely separate on header parsing for the various integrations.

authors: pacejackson spladug


text:
Setting the nodejs engine to iojs and install_method to 'source' does not change the prefix_url

Hello,
I'm new to chef.. and I don't open many bugs bare with me....
my /cookbook/attributes/default.rb
default['nodejs']['engine'] = 'iojs'
default['nodejs']['version'] = '2.2.1'
default['nodejs']['source'] = { :checksum => '55e79cc4f4cde41f03c1e204d2af5ee4b6e4edcf14defc82e518436e939195fa' }
default['nodejs']['install_method'] = 'source'
Keeps creating this chef error:
  Error executing action `create` on resource 'remote_file[/var/chef/cache/iojs-source-2.2.1.tar.gz]'
  ================================================================================

Net::HTTPServerException
  ------------------------
  404 "Not Found"

  Resource Declaration:
  ---------------------
  # In /var/chef/cache/cookbooks/ark/providers/default.rb

  279:   remote_file new_resource.release_file do
  280:     Chef::Log.debug('DEBUG: new_resource.release_file')
  281:     source new_resource.url
  282:     checksum new_resource.checksum if new_resource.checksum
  283:     action :create
  284:     notifies :run, "execute[unpack #{new_resource.release_file}]"
  285:   end
  286:

  Compiled Resource:
  ------------------
  # Declared in /var/chef/cache/cookbooks/ark/providers/default.rb:279:in `block in class_from_file'

  remote_file("/var/chef/cache/iojs-source-2.2.1.tar.gz") do
    provider Chef::Provider::RemoteFile
    action [:create]
    retries 0
    retry_delay 2
    default_guard_interpreter :default
    path "/var/chef/cache/iojs-source-2.2.1.tar.gz"
    backup 5
    atomic_update true
    source ["http://nodejs.org/dist/v2.2.1/iojs-v2.2.1.tar.gz"]
    use_etag true
    use_last_modified true
    declared_type :remote_file
    cookbook_name "nodejs"
    checksum "55e79cc4f4cde41f03c1e204d2af5ee4b6e4edcf14defc82e518436e939195fa"
  end

Notice the source goes and fetch from the nodejs and not iojs server
If I override the prefix_url in my cookbook before load the include_recipe of "nodejs" with
node.override['nodejs']['prefix_url'] = 'http://iojs.org/dist/'
Then it works fine.
So I'm wondering if the
https://github.com/redguide/nodejs/blob/8fde9f58856c1243551ab9c2492c96bb420698ed/attributes/default.rb#L31
Works as intended?
Thanks,
Kyle

I can reproduce this error.
Wondering why this attributes are not working as intended :
if node['nodejs']['engine'] == 'iojs'
  default['nodejs']['prefix_url'] = 'http://iojs.org/dist/'
else
  default['nodejs']['prefix_url'] = 'http://nodejs.org/dist/'
end

ok ...
It was an obvious mistake from us :space_invader: :
If you write this :
default['nodejs']['engine'] = 'node' # or iojs
if node['nodejs']['engine'] == 'iojs'
[...]
end

IF test always return false ;-) ... that's why prefix_url always point to nodejs website.

But it's not enough one way or another nodejs cookbook wipes all node['nodejs'] hash or it makes impossible to override engine value... I'm trying to found the root cause

authors: BarthV kembs

repo: redguide/nodejs


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

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-wjwp-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-wjwp-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-wjwp-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-wjwp-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-wjwp-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-wjwp-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-wjwp-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-wjwp-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-wjwp-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:
Appstudio update test-custom-default-branch-xkeq

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-wadk-on-pull-request-
creating pipelinerun test-simple-build-wadk-on-pull-request- in namespace build-e2e-iivx-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-vchz-on-pull-request-
creating pipelinerun test-annotations-vchz-on-pull-request- in namespace build-e2e-iivx-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-nqwj-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-gcoj-on-pull-request-
creating pipelinerun test-annotations-gcoj-on-pull-request- in namespace build-e2e-nqwj-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-dtnt-on-pull-request-
creating pipelinerun test-annotations-dtnt-on-pull-request- in namespace build-e2e-nqwj-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-yrqk-on-pull-request-
creating pipelinerun test-annotations-yrqk-on-pull-request- in namespace build-e2e-iivx-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-nqwj-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-ntht-on-pull-request-
creating pipelinerun test-annotations-ntht-on-pull-request- in namespace build-e2e-iivx-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-gcoj-on-pull-request-
creating pipelinerun test-annotations-gcoj-on-pull-request- in namespace build-e2e-iivx-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-iivx-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-nqwj-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-custom-default-branch-xkeq-on-pull-request-
creating pipelinerun test-custom-default-branch-xkeq-on-pull-request- in namespace build-e2e-nqwj-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-nyrh-on-pull-request-
creating pipelinerun test-simple-build-nyrh-on-pull-request- in namespace build-e2e-iivx-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-nqwj-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-nyrh-on-pull-request-
creating pipelinerun test-simple-build-nyrh-on-pull-request- in namespace build-e2e-nqwj-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-iivx-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-iivx-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-nqwj-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-nqwj-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-vchz-on-pull-request-
creating pipelinerun test-annotations-vchz-on-pull-request- in namespace build-e2e-nqwj-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-dtnt-on-pull-request-
creating pipelinerun test-annotations-dtnt-on-pull-request- in namespace build-e2e-iivx-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-ntht-on-pull-request-
creating pipelinerun test-annotations-ntht-on-pull-request- in namespace build-e2e-nqwj-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-iivx-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-nqwj-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-iivx-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-iivx-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-iivx-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-yrqk-on-pull-request-
creating pipelinerun test-annotations-yrqk-on-pull-request- in namespace build-e2e-nqwj-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-nqwj-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:
Appstudio update test-component-pac-nfvu

Pipelines as Code configuration proposal

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

StatusDurationName

✅ Succeeded
7 seconds
init

✅ Succeeded
18 seconds
clone-repository

✅ Succeeded
34 seconds
build-container

✅ Succeeded
18 seconds
deprecated-base-image-check

✅ Succeeded
19 seconds
sanity-inspect-image

✅ Succeeded
3 minutes
clair-scan

✅ Succeeded
47 seconds
clamav-scan

✅ Succeeded
16 seconds
sbom-json-check

✅ Succeeded
17 seconds
sanity-optional-label-check

✅ Succeeded
18 seconds
sanity-label-check

✅ Succeeded
8 seconds
show-summary

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

StatusDurationName

✅ Succeeded
5 seconds
init

✅ Succeeded
17 seconds
clone-repository

✅ Succeeded
27 seconds
build-container

✅ Succeeded
17 seconds
sanity-inspect-image

✅ Succeeded
16 seconds
deprecated-base-image-check

✅ Succeeded
8 seconds
sbom-json-check

✅ Succeeded
35 seconds
clamav-scan

✅ Succeeded
8 seconds
clair-scan

✅ Succeeded
18 seconds
sanity-label-check

✅ Succeeded
17 seconds
sanity-optional-label-check

✅ Succeeded
6 seconds
show-summary


text:
Appstudio update mvp-test-component

Pipelines as Code configuration proposal

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

StatusDurationName

✅ Succeeded
5 seconds
init

✅ Succeeded
18 seconds
clone-repository

✅ Succeeded
1 minute
build-container

✅ Succeeded
16 seconds
sanity-inspect-image

✅ Succeeded
14 seconds
deprecated-base-image-check

✅ Succeeded
16 seconds
clair-scan

✅ Succeeded
11 seconds
sbom-json-check

✅ Succeeded
57 seconds
clamav-scan

✅ Succeeded
17 seconds
sanity-label-check

✅ Succeeded
17 seconds
sanity-optional-label-check

✅ Succeeded
5 seconds
show-summary

repo: redhat-appstudio-qe/hacbs-test-project


text:
Merge maven-metadata.xml versions

If this is from multiple sources it needs to be merged.
Also add a Jenkins sample build that demonstrates this.

@gabemontero it needed a few minor changes but the initial jenkins build completes now.

cool deal / thanks @stuartwdouglas
I'll build on this after it merges and add the 3 openshift jenkins plugins
Also, I'll try it soon enough, but after the initial build, what was the rough estimate of succeeded vs. failed vs. contaminated dependencies ?
/lgtm

so yeah I see it compile as well ... took way longer than service registry.
I then see 97 artifactbuilds created, all either failed or missing
17 dependency builds, 2 contaminated, the rest failed.
So less of those than service registry, but starting at ground 0.

authors: gabemontero stuartwdouglas

repo: redhat-appstudio/jvm-build-service


text:
My pr new features

Split RHEL and CentOS specifics
ignored errors on clusters. still work todo to align.
made test work with my local vagrant machines

This is a PR on the PR created by cpolizzi (https://github.com/cpolizzi/jboss_amq branch: new-features).

@buuhsmead changes from @cpolizzi have been integrated into master. please base your work off of it.
Thanks!

I am closing this PR as being obsolete. New PR are from master, if created. This one was a PR on a PR and not needed anymore.


text:
Script does not respect a "no_proxy" env in a proxied environment

If running this script behind a proxy, the image pull is running, but the image push to a local registry, which is reachable without a proxy, fails.
The push also uses the proxy, but the local registry is reachable without a proxy.
If a "no_proxy" env is set, the push should not use a proxy.

It seems, that this is a bug in the python requests module:
https://github.com/requests/requests/issues/879

@grimkroton ; which script are you talking about?

@garethahealy this script https://raw.githubusercontent.com/redhat-cop/openshift-toolkit/master/disconnected_registry/docker-registry-sync.py
Sorry for format, answered from mobile.

authors: garethahealy grimkroton

repo: redhat-cop/openshift-toolkit


text:
Incorporation of CoP shared workflow

Incorporation of CoP shared workflow
Secrets have been updated to account for new requirements from workflow
Before merging:

Complete https://github.com/redhat-cop/github-workflows-operators/pull/2
Create tag v1.0.0

@raffaelespazzoli changes have been added to the existing PR https://github.com/redhat-cop/github-workflows-operators/pull/2


text:
Added the ocdev project get command

Added the project get command https://github.com/redhat-developer/ocdev/issues/96

@TomasTomecek I am working on the ocdev project <project_name> command currently. I found out that if the user does oc project <project_name> with the current project_name, the command returns
Already on project "<project_name>" on server "https://192.168.42.29:8443"
Should I replicate this on the ocdev tool too?

I am working on the ocdev project <project_name>command currently.

@mik-dass to switch in between project the command should be ocdev project set

I found out that if the user does oc project <project_name> with the current project_name, the command returns
Already on project "<project_name>" on server "https://192.168.42.29:8443"

Yes, it should show display message like this indicating that you are already using that project.

@kadel I have added all the commands and I think it's ready for review. Not sure about the codecov thing though. Should I add tests for it?

If you can figure out how to add unit tests to this it would be great. But it is not necessary.
Currently, we don't have a easy way to mock oc calls :-(  So adding unit tests might be tricky :-(

@kadel Ok I will look into it :)

Sorry about that @mik-dass , but after #245 was merged you code needs small refactor :-(
I'll merge it as soon as it is done, so you don't end up in the same situation with another PR.

@kadel Done

authors: kadel mik-dass

repo: redhat-developer/ocdev


text:
chore: better css

Update CSS based on latest docs.redhat.com CSS.
Fix display errors with current CSS.
The HTML output is fairly different: the CSS is an attempt to mimic docs.redhat.com visual feeling as much as possible, but is not exactly the same.
Known issue: Callouts have a parenthesis in the code block
Known issue: Admonition icons are missing.
Known issue: Admonition title placement is different.
Known issue: TOC placement is different.
Known issues: The CSS still contains unused rules (even after removing 1000 loc).

Much better. Some callouts are weirdly wider than the page, however.

https://redhat-developer.github.io/red-hat-developers-documentation-rhdh/pr-296/admin-rhdh/

Merging now as it already improves the current situation. New PR following for more fixes.


text:
modify hostpath volume

Signed-off-by: Ryan Cook rcook@redhat.com
Hostpath should use a podman volume

@cooktheryan with the recent merges to remove the microshift-containerized file, this needs a rebase!

authors: cooktheryan sallyom

repo: redhat-et/microshift


text:
Include architecture and/or image digest in JSON output

Is your feature request related to a problem? Please describe.
When scanning an image index, JSON reports do not indicate which architecture the results are about. I can see the image architectures and digests in log messages but not in JSON.
$ preflight-1.7.2 check container 'registry.access.redhat.com/ubi9/buildah:latest' > preflight.json
level=info msg="certification library version" version="1.7.2 <commit: f1bfa27d3f87bc9b95936aaeb4edc6a92a268645>"
level=info msg="running checks for registry.access.redhat.com/ubi9/buildah:latest for platform amd64"
level=info msg="target image" image="registry.access.redhat.com/ubi9/buildah:latest"
…
level=info msg="This image's tag latest will be paired with digest sha256:0e0d263a42c4971c43290489181dfc58ed723a0797400abe2002cdb219e4bb84 once this image has been published…
…
level=info msg="running checks for registry.access.redhat.com/ubi9/buildah:latest for platform arm64"
level=info msg="target image" image="registry.access.redhat.com/ubi9/buildah:latest"
…
level=info msg="This image's tag latest will be paired with digest sha256:73312575856fc4d64b33c757ac3ec0807cb5b3c0527c05b5284832b4e9219791 once this image has been published…
…

$ cat preflight.json
{
    "image": "registry.access.redhat.com/ubi9/buildah:latest",
    "passed": …,
    "test_library": { … },
    "results": { … }
}
{
    "image": "registry.access.redhat.com/ubi9/buildah:latest",
    "passed": …,
    "test_library": { … },
    "results": { … }
}
{
    "image": "registry.access.redhat.com/ubi9/buildah:latest",
    "passed": …,
    "test_library": { … },
    "results": { … }
}
…

Describe the solution you'd like.
I'd like more details in JSON about the image that was scanned.
I'm deep in image contents all the time, so I think I might like a platform field in the JSON that looks like the OCI index field:
{
  "image": "registry.access.redhat.com/ubi9/buildah:latest",
  "platform": {
    "os": "linux",
    "architecture": "amd64"
  },
  "results": {}
}
{
  "image": "registry.access.redhat.com/ubi9/buildah:latest",
  "platform": {
    "os": "linux",
    "architecture": "arm64"
  },
  "results": {}
}

I could infer the platform from a digest field, so that's a second possible solution. Lots of other things can be inferred from the digest, so perhaps it could obviate other feature requests.
{
  "image": "registry.access.redhat.com/ubi9/buildah:latest",
  "digest": "sha256:0e0d263a42c4971c43290489181dfc58ed723a0797400abe2002cdb219e4bb84",
  "results": {}
}
{
  "image": "registry.access.redhat.com/ubi9/buildah:latest",
  "digest": "sha256:73312575856fc4d64b33c757ac3ec0807cb5b3c0527c05b5284832b4e9219791",
  "results": {}
}

$ skopeo inspect --raw docker://registry.access.redhat.com/ubi9/buildah:latest
{
    "manifests": [
        {
            "digest": "sha256:0e0d263a42c4971c43290489181dfc58ed723a0797400abe2002cdb219e4bb84",
            "mediaType": "application/vnd.docker.distribution.manifest.v2+json",
            "platform": {
                "architecture": "amd64",
                "os": "linux"
            },
            "size": 595
        },
        {
            "digest": "sha256:73312575856fc4d64b33c757ac3ec0807cb5b3c0527c05b5284832b4e9219791",
            "mediaType": "application/vnd.docker.distribution.manifest.v2+json",
            "platform": {
                "architecture": "arm64",
                "os": "linux"
            },
            "size": 595
        },
…

Describe alternatives you've considered.
Perhaps the image field should have a digest instead of a tag. This change is potentially disruptive.
{
  "image": "registry.access.redhat.com/ubi9/buildah@sha256:0e0d263a42c4971c43290489181dfc58ed723a0797400abe2002cdb219e4bb84",
  "results": {}
}
{
  "image": "registry.access.redhat.com/ubi9/buildah@sha256:73312575856fc4d64b33c757ac3ec0807cb5b3c0527c05b5284832b4e9219791",
  "results": {}
}

Hi @cbandy thanks for creating this issue, and providing some ideas that you have thought about. The results.json file is used as the payload preflight sends to our backend system, so this file has to conform to that systems schema. This means we'd have to have changes made in that system first before making changes to preflight.
With that said the first 2 options you purpose at face value seem like possibilities that the backend team could agree to to implement. The 3rd option is a non-starter as I'm fairly certainimage is used by other systems, and tag being part of that is important. I'd rather stick to an addition of fields, then change the meaning/data of an existing field.
I'll reach out to the backend team and we can go from there, though I don't think there would be any movement on this till after the 1st of the year.


text:
pull-secret is double-quoted

The Convert pullsecret to JSON in ansible-ipi-install/roles/set-deployment-fact/tasks.main cause the pull secret defined as
pullsecret: '{"auths": ... }'

to end up with one extra layer of quoting, failing the playbook when the pull-secret file is used on the provisioner.

Please use pullsecret as is - without any quotes @rvansa and let me know how it goes

@smalleni I have installed OCP now (disabling the conversion) but I perceive the pull-secret as an opaque string, therefore pasting it as such. Putting the JSON straight into YAML seems awkward.
Maybe a check if the pullsecret is string or object would satisfy any use case.

Ack. I think we had to make that change with something related to exporting these group_vars/all.yml as environment variables for tools like jenkins. We used to require a '' before that?
I like your idea, do you mind sending a PR?

Created https://github.com/redhat-performance/JetSki/pull/174

authors: rvansa smalleni

repo: redhat-performance/JetSki


text:
static inline functions are not within extern C

Hi all,
Actually the complete sds.h is not inside an extern C {. This causes issues when hiredis is included in C++.
Why not put the extern C at the top of hiredis.h?
https://github.com/redis/hiredis/blob/master/hiredis.h#L107-L109
Thanks,
Rik

I am using hiredis with g++ without any problem.
What problem do you have exactly?

I'm compiling my code with -Wold-style-cast and -Werror, now I need to make an exception for every file where hiredis is included.

@rikvdh You can use this way to include hiredis.h
extern "C" {
#include "hiredis/hiredis.h"
}

authors: echoma owt5008137 rikvdh

repo: redis/hiredis


text:
Thread ends up stuck when redis command is sent while the redisson client is disconnected from the redis cluster

Expected behavior
redisson should throw an exception that the command was not successful, and earlier than when the redisson client gets reconnected to the redis cluster
Actual behavior
the thread hangs and gets stuck
Steps to reproduce or test case
a blackhole attack is started to block all traffic to and from a redis cluster (Elasticache on AWS version 6.2.6), and lasts for three minutes.
the log is as follow, in this example, the attack started at 9:51:10 until 9:54:10 (Gremlin is used to run the attack)
caches are instances of RLocalCachedMap
[2022-12-07 09:51:28.761+0000] ExecuteThread: '16' [org.redisson.cluster.ClusterConnectionManager]  slot 71 for A90:witness/usermanager
[2022-12-07 09:51:28.761+0000] ExecuteThread: '16' [org.redisson.command.RedisExecutor] acquired connection for command (EVAL) and params [if ARGV[4] == '1' then redis.call('publish', KEYS[2], ARGV[3]); end;if ARGV[4] == '2' then redis.call('zadd', KEYS[3], ARGV[5], ARGV[6]);redis.call('publish', KEYS[2], ARGV[3]); end;if redis.call('hset', KEYS[1], ARGV[1], ARGV[2]) == 0 then return 0; end; return 1; , 3, A90:witness/usermanager, {A90:witness/usermanager}:topic, redisson__cache_updates_log:{A90:witness/usermanager}, PooledUnsafeDirectByteBuf(ridx: 0, widx: 19, cap: 256), PooledUnsafeDirectByteBuf(ridx: 0, widx: 318, cap: 512), PooledUnsafeDirectByteBuf(ridx: 0, widx: 37, cap: 256), 1, 1670406688761, ...] from slot NodeSource [slot=71, addr=null, redisClient=null, redirect=null, entry=null] using node 10.x.x.x/10.x.x.x:6379... RedisConnection@1466869015 [redisClient=[addr=rediss://10.x.x.x:6379], channel=[id: 0x537b5bf6, L:/10.x.x.x:53709 - R:10.x.x.x/10.x.x.x:6379], currentCommand=null, usage=1]
[2022-12-07 09:51:36.538+0000] -- the Redis connection listener gets onDisconnect from the redis node 10.x.x.x
[2022-12-07 09:51:47.693+0000] [redisson-timer-4-1] [org.redisson.client.handler.ConnectionWatchdog] reconnecting RedisConnection@1466869015 [redisClient=[addr=rediss://10.x.x.x:6379], channel=[id: 0x537b5bf6, L:/10.x.x.x:53709 ! R:10.x.x.x/10.x.x.x:6379], currentCommand=null, usage=1] to 10.x.x.x/10.x.x.x:6379 -- that is the first occurrence of this message
[2022-12-07 09:54:12.995+0000] [redisson-timer-4-1] -- last occurence of the message reconnecting...
[2022-12-07 09:54:10.914+0000] -- the Redis connection listener gets onConnect to the redis node 10.x.x.x
[2022-12-07 09:54:13.007+0000] [redisson-netty-2-3] [org.redisson.client.handler.ConnectionWatchdog] RedisConnection@1466869015 [redisClient=[addr=rediss://10.x.x.x:6379], channel=[id: 0x537b5bf6, L:/10.x.x.x:53709 ! R:10.x.x.x/10.x.x.x:6379], currentCommand=null, usage=1] connected to 10.x.x.x/10.x.x.x:6379, command: null
ExecuteThread: '16' is hogged and get eventually stuck.
note that the command for RedisConnection@1466869015 is null also, and we only got an onDisconnect at 9:51:36, while the attack started at 9:51:10
Are there any configs that would help triggering an exception for commands sent when the client is disconnected from the remote cache?
What config relates to the notification of a disconnection/connection from redisson to redis?
Redis version
Elasticache on AWS version 6.2.6
Redisson version
3.18.1
netty jars used are of version 4.1.79.Final
Redisson configuration
useClusterServers()
setRetryAttempts(1)
everything else are defaults

that is the extract of a stuck thread:
"[STUCK] ExecuteThread: '26' for queue: 'weblogic.kernel.Default (self-tuning)'" #90 daemon prio=1 os_prio=-2 tid=0x0000000042d2e800 nid=0xa5c waiting on condition [0x0000000046abb000]
           java.lang.Thread.State: WAITING (parking)

        	at sun.misc.Unsafe.park(Native Method)

        	- parking to wait for  <0x00000007a40a4d90> (a java.util.concurrent.CompletableFuture$Signaller)

        	at java.util.concurrent.locks.LockSupport.park(Unknown Source)

        	at java.util.concurrent.CompletableFuture$Signaller.block(Unknown Source)

        	at java.util.concurrent.ForkJoinPool.managedBlock(Unknown Source)

        	at java.util.concurrent.CompletableFuture.waitingGet(Unknown Source)

        	at java.util.concurrent.CompletableFuture.get(Unknown Source)

        	at org.redisson.command.CommandAsyncService.get(CommandAsyncService.java:109)

        	at org.redisson.RedissonObject.get(RedissonObject.java:82)

in RedisExecutor, we get to
writeFuture = connection.send(new CommandData<>(attemptPromise, codec, command, params));
but the attemptPromise never seems to complete

@mrniko I think there maybe a mistake in one method:
` @Override
public void channelInactive(ChannelHandlerContext ctx) throws Exception {
Queue queue = ctx.channel().attr(COMMANDS_QUEUE).get();
Iterator iterator = queue.iterator();
while (iterator.hasNext()) {
QueueCommandHolder command = iterator.next();
if (command.getCommand().isBlockingCommand()) {
continue;
}
        iterator.remove();
        command.getChannelPromise().tryFailure(
                new WriteRedisConnectionException("Channel has been closed! Can't write command: "
                            + LogHelper.toString(command.getCommand()) + " to channel: " + ctx.channel()));
    }

    super.channelInactive(ctx);
}`

I think command.getChannelPromise().tryFailure should instead be command.getCommand().tryFailure as it is the command's attemptPromise we are trying to complete

while the redisson client was not connected to the redis cluster, the command will never be executed and the promise never completed

Is there any code to reproduce it?

@mrniko I am having difficulties creating a simple program that would recreate the situation I am getting in the application,in which the connection does not get released.
Could you give me some pointers and tell me if I am making the wrong assumptions?
One of the application servers is disconnected from the redis cluster (two nodes).
An example of redis command being sent while the server is disconnected from the redis cluster is like this: (I changed the debug log messages so I could see more details about the connection and command sent)
####[ProductionServer]-[] [2022-12-16 16:00:05.203+0000] [DEBUG] [[ACTIVE] ExecuteThread: '20' for queue: 'weblogic.kernel.Default (self-tuning)'] [org.redisson.cluster.ClusterConnectionManager] <##[{user=mst-scheduler-05}]##> - slot 14399 for A90:witness/uif/sessionAttributes
####[ProductionServer]-[] [2022-12-16 16:00:05.203+0000] [DEBUG] [[ACTIVE] ExecuteThread: '20' for queue: 'weblogic.kernel.Default (self-tuning)'] [org.redisson.command.RedisExecutor] <##[{user=mst-scheduler-05}]##> - acquired connection for command (INFO REPLICATION) and params [] from slot NodeSource [slot=null, addr=null, redisClient=null, redirect=null, entry=MasterSlaveEntry [masterEntry=[freeSubscribeConnectionsAmount=1, freeSubscribeConnectionsCounter=value:44:queue:0, freeConnectionsAmount=21, freeConnectionsCounter=value:61:queue:0, freezeReason=null, client=[addr=rediss://10.50.71.120:6379], nodeType=MASTER, firstFail=0]]] using node 10.50.71.120/10.50.71.120:6379... RedisConnection@2124380504 [redisClient=[addr=rediss://10.50.71.120:6379], channel=[id: 0xb9b538ba, L:/10.50.71.96:62447 - R:10.50.71.120/10.50.71.120:6379], currentCommand=null, usage=1]
####[ProductionServer]-[] [2022-12-16 16:00:05.203+0000] [DEBUG] [[ACTIVE] ExecuteThread: '20' for queue: 'weblogic.kernel.Default (self-tuning)'] [org.redisson.command.RedisExecutor] <##[{user=mst-scheduler-05}]##> - sendCommand: attemptPromise java.util.concurrent.CompletableFuture@7593062f[Not completed], connection RedisConnection@2124380504 [redisClient=[addr=rediss://10.50.71.120:6379], channel=[id: 0xb9b538ba, L:/10.50.71.96:62447 - R:10.50.71.120/10.50.71.120:6379], currentCommand=null, usage=1]
####[ProductionServer]-[] [2022-12-16 16:00:05.203+0000] [DEBUG] [redisson-netty-2-4] [org.redisson.client.handler.CommandsQueue] <##   ##> - write - command CommandData [promise=java.util.concurrent.CompletableFuture@7593062f[Not completed], command=(INFO REPLICATION), params=[], codec=null], channel [id: 0xb9b538ba, L:/10.50.71.96:62447 - R:10.50.71.120/10.50.71.120:6379], channel promise DefaultChannelPromise@5d1024ca(incomplete)
####[ProductionServer]-[common] [2022-12-16 16:00:24.115+0000] [INFO] [redisson-netty-2-4] [com.bluepumpkin.common.cache.redis.RedisConnectionListener] <##   ##> - Disconnecting from: hostString= 10.50.71.120, client: redisson-34288@APP1-A62-USE1
####[ProductionServer]-[] [2022-12-16 16:00:24.115+0000] [DEBUG] [redisson-netty-2-4] [org.redisson.client.handler.ConnectionWatchdog] <##   ##> - channelInactive [id: 0xb9b538ba, L:/10.50.71.96:62447 ! R:10.50.71.120/10.50.71.120:6379], connection RedisConnection@2124380504 [redisClient=[addr=rediss://10.50.71.120:6379], channel=[id: 0xb9b538ba, L:/10.50.71.96:62447 ! R:10.50.71.120/10.50.71.120:6379], currentCommand=CommandData [promise=java.util.concurrent.CompletableFuture@7593062f[Not completed, 1 dependents], command=(INFO REPLICATION), params=[], codec=null], usage=1]
####[ProductionServer]-[] [2022-12-16 16:00:24.116+0000] [DEBUG] [redisson-netty-2-4] [org.redisson.client.handler.CommandsQueue] <##   ##> - channelInactive [id: 0xb9b538ba, L:/10.50.71.96:62447 ! R:10.50.71.120/10.50.71.120:6379], queue size 1
####[ProductionServer]-[] [2022-12-16 16:00:24.116+0000] [DEBUG] [redisson-netty-2-4] [org.redisson.client.handler.CommandsQueue] <##   ##> - non-blocking command - removing CommandData [promise=java.util.concurrent.CompletableFuture@7593062f[Not completed, 1 dependents], command=(INFO REPLICATION), params=[], codec=null]
####[ProductionServer]-[] [2022-12-16 16:00:24.209+0000] [DEBUG] [redisson-timer-4-1] [org.redisson.client.handler.ConnectionWatchdog] <##   ##> - reconnecting RedisConnection@2124380504 [redisClient=[addr=rediss://10.50.71.120:6379], channel=[id: 0xb9b538ba, L:/10.50.71.96:62447 ! R:10.50.71.120/10.50.71.120:6379], currentCommand=null, usage=1] to 10.50.71.120/10.50.71.120:6379
####[ProductionServer]-[] [2022-12-16 16:00:34.310+0000] [DEBUG] [redisson-timer-4-1] [org.redisson.client.handler.ConnectionWatchdog] <##   ##> - reconnecting RedisConnection@2124380504 [redisClient=[addr=rediss://10.50.71.120:6379], channel=[id: 0xb9b538ba, L:/10.50.71.96:62447 ! R:10.50.71.120/10.50.71.120:6379], currentCommand=null, usage=1] to 10.50.71.120/10.50.71.120:6379
####[ProductionServer]-[] [2022-12-16 16:00:44.410+0000] [DEBUG] [redisson-timer-4-1] [org.redisson.client.handler.ConnectionWatchdog] <##   ##> - reconnecting RedisConnection@2124380504 [redisClient=[addr=rediss://10.50.71.120:6379], channel=[id: 0xb9b538ba, L:/10.50.71.96:62447 ! R:10.50.71.120/10.50.71.120:6379], currentCommand=null, usage=1] to 10.50.71.120/10.50.71.120:6379
####[ProductionServer]-[] [2022-12-16 16:00:54.509+0000] [DEBUG] [redisson-timer-4-1] [org.redisson.client.handler.ConnectionWatchdog] <##   ##> - reconnecting RedisConnection@2124380504 [redisClient=[addr=rediss://10.50.71.120:6379], channel=[id: 0xb9b538ba, L:/10.50.71.96:62447 ! R:10.50.71.120/10.50.71.120:6379], currentCommand=null, usage=1] to 10.50.71.120/10.50.71.120:6379
####[ProductionServer]-[] [2022-12-16 16:01:04.610+0000] [DEBUG] [redisson-timer-4-1] [org.redisson.client.handler.ConnectionWatchdog] <##   ##> - reconnecting RedisConnection@2124380504 [redisClient=[addr=rediss://10.50.71.120:6379], channel=[id: 0xb9b538ba, L:/10.50.71.96:62447 ! R:10.50.71.120/10.50.71.120:6379], currentCommand=null, usage=1] to 10.50.71.120/10.50.71.120:6379
####[ProductionServer]-[] [2022-12-16 16:01:04.623+0000] [DEBUG] [redisson-netty-2-32] [org.redisson.client.handler.ConnectionWatchdog] <##   ##> - RedisConnection@2124380504 [redisClient=[addr=rediss://10.50.71.120:6379], channel=[id: 0xb9b538ba, L:/10.50.71.96:62447 ! R:10.50.71.120/10.50.71.120:6379], currentCommand=null, usage=1] connected to 10.50.71.120/10.50.71.120:6379, command: null
We are seeing:
sendCommand: attemptPromise java.util.concurrent.CompletableFuture@7593062f[Not completed], connection RedisConnection@2124380504
I am expecting to get the attemptPromise completed exceptionally and the connection released.
Instead, I end up in ConnectionWatchdog, at line log.debug("{} connected to {}, command: {}", connection, connection.getRedisClient().getAddr(), connection.getCurrentCommand()); where current command is null.
I need to be able to verify that on channelInactive, the command gets removed from the queue and should get exceptionally completed, which does not happen in our case.
You mentioned earlier that any failure will be propagated to the writeFuture in RedisExecutor. This would mean the attemptPromise in RedisExecutor would be completed exceptionally, yes?

I am expecting to get the attemptPromise completed exceptionally and the connection released.

This happens only if max attempts were reached.

This would mean the attemptPromise in RedisExecutor would be completed exceptionally, yes?

Exactly.

@mrniko
If a command is removed from the queue in CommandsQueue inactiveChannel, we are expecting that the attemptPromise for that command be completed exceptionally, yes?
Where/When would that happen? In our case, it is never completed and the thread is stuck

If a command is removed from the queue in CommandsQueue inactiveChannel, we are expecting that the attemptPromise for that command be completed exceptionally, yes?

Since getChannelPromise() it's a writeFuture field in RedisExecutor which in turn checked in checkWriteFuture method.

@mrniko
thanks for the reply.
the "problem" is that in CommandsQueue channelInactive method, the command.getChannelPromise() is a "success" (command.getChannelPromise() = DefaultChannelPromise@30fb6c76(success))

@mrniko I think I have identified the problem - I am seeing scheduleResponseTimeout timeout of 3600000 ms!
I added log.debug("scheduleResponseTimeout timeout of " + timeoutTime + " for " + attemptPromise.toString() + ", connection "+connection.toString());
timeout = Optional.of(connectionManager.newTimeout(timeoutResponseTask, timeoutTime, TimeUnit.MILLISECONDS));
timeoutTime is initialised with responseTimeout, that is meant to be 3000ms....

@mrniko the issue was the timeout - it was being set to 1 hour in our application code!
thanks for the responses

@mrniko I think I have identified the problem - I am seeing scheduleResponseTimeout timeout of 3600000 ms!
I added log.debug("scheduleResponseTimeout timeout of " + timeoutTime + " for " + attemptPromise.toString() + ", connection "+connection.toString()); timeout = Optional.of(connectionManager.newTimeout(timeoutResponseTask, timeoutTime, TimeUnit.MILLISECONDS));
timeoutTime is initialised with responseTimeout, that is meant to be 3000ms....

hi, i met the similar issue, i guess it happened during the network not stable , how did  you solve your  problem , thanks
my issue: https://github.com/redisson/redisson/issues/5944

@yinyansheng
Right

authors: fkolberg-verint mrniko yinyansheng

repo: redisson/redisson


text:
Don’t make FAIL cause fatal errors

In accordance with making WARN emit warnings, FAIL now takes on WARN’s previous behaviour, which was to emit an error, but not stop assembling.

I don't think this is likely to break anything, but if it does, this could potentially be reimplemented as a new ERROR keyword.

Not sure about this. The reason I had for changing the behaviour of WARN is that it doesn't make sense to have WARN and FAIL functions if they do basically the same thing: Show an error message.
To me, WARN is supposed to show a warning message but continue, like GCC #warning, and FAIL should show the message and stop, like #error. It doesn't make sense to continue assembling after an error because the code may not even make sense (for example, you check if a number is positive and fail if not, then use the number to allocate memory with DS).

Oh, for some reason I was under the impression that #error would continue, at least so it could find all the errors… Maybe I just haven't used these kinds of keywords much lately; my bad!

I've just checked, I was wrong about #error. However, it still doesn't feel like a good idea to continue assembling after the code explicitly has a statement telling the assembler to stop.

Ok, now I remember, -Wfatal-errors makes it behave like I said...

Hm… Do you think it would make sense to allow both behaviours? (if so, I'd probably use a new ERROR keyword for the new behaviour).

It might make sense for the assembler to continue after a syntax error (I disagree, in lots of cases that creates a long list of fake errors caused by the first one) but I'm completely against letting it continue if the code says it has to stop.

And I just don't see the point in adding more keywords for this. Error and fail can be easily mistaken.

OK, I'll leave this closed then.

This is actually the intended original behaviour: http://www.chrisantonellis.com/files/gameboy/asmotor-v0.1.0-manual.pdf I don't know when WARN changed to become yet another error, but that was a mistake.

In macros it can be helpful to warn the user of a wrong argument or completely abort the assembly process. This is possible with the FAIL and WARN commands. FAIL and WARN take a string as the only argument and will print it out as a regular warning or error with a line number.
FAIL stops assembling immediately while WARN continues after printing the error message.

repo: rednex/rgbds


text:
Polyline Component add a properties prop as in Entity

Hi there I need inside Polyline Component to Have properties prop
so I can use a property bag .
is it possible ?
Thanks.

It's Entity's prop. Refer to Entity component.

repo: reearth/resium


text:
Handle deduplication in feature manager

Description
It'd be great to create a map of "page:deduplicate-selector" so that this can be handled by the feature manager instead of having to manually specify it in every feature, but this might take a little effort.
Anyway this is what I mean:
const deduplicateMap = {
  isPR: '.has-rgh-inner',
  isDashboard: '.has-rgh',
}

Originally posted by @fregante in https://github.com/sindresorhus/refined-github/issues/4695#issuecomment-910508914

Deduplication table (collected in features.add)

*.rgh-view-markdown-source, has-rgh-inner, has-rgh, .rgh-feature-description
hasCodehas-rgh-inner, has-rgh, .rgh-observing-whitespace
hasCommentshas-rgh-inner, has-rgh
hasFrontMatterhas-rgh
hasNotificationBarhas-rgh
hasRichTextEditorhas-rgh-inner, has-rgh
is404has-rgh
isActionRunhas-rgh
isBlamehas-rgh
isBrancheshas-rgh
isCommithas-rgh-inner
isCommitListhas-rgh, has-rgh-inner
isComparehas-rgh, has-rgh-inner
isConversationhas-rgh-inner
isConversationListhas-rgh-inner
isDashboardhas-rgh
isDiscussionhas-rgh-inner, has-rgh
isEditingFilehas-rgh, has-rgh-inner, .rgh-list-prs-for-file
isEditingReleasehas-rgh
isEditingWikiPagehas-rgh
isForkedRepohas-rgh
isGisthas-rgh-inner, .rgh-copy-file, has-rgh
isGlobalConversationListhas-rgh, has-rgh-inner
isGlobalSearchResultshas-rgh
isIssuehas-rgh-inner
isMarketplaceActionhas-rgh
isMilestonehas-rgh
isNewFilehas-rgh-inner, has-rgh
isNewIssuehas-rgh-inner
isNewReleasehas-rgh
isNewRepohas-rgh
isNewRepoTemplatehas-rgh
isNewWikiPagehas-rgh
isNotificationshas-rgh
isOrganizationProfilehas-rgh
isOwnUserProfilehas-rgh
isPRhas-rgh-inner, has-rgh
isPRCommit404has-rgh
isPRCommithas-rgh-inner, has-rgh
isPRConflictshas-rgh
isPRConversationhas-rgh-inner
isPRFileshas-rgh-inner, has-rgh
isPRListhas-rgh-inner
isQuickPRhas-rgh
isReleasesOrTagshas-rgh, has-rgh-inner
isRepohas-rgh, has-rgh-inner
isRepoCommitListhas-rgh, .rgh-default-branch-button
isRepoConversationListhas-rgh-inner
isRepoForksListhas-rgh
isRepoHomehas-rgh
isRepoIssueListhas-rgh-inner
isRepoMainSettingshas-rgh
isRepoNetworkGraphhas-rgh
isRepoRoothas-rgh-inner
isRepoSearchhas-rgh
isRepoTreehas-rgh, .rgh-download-folder, .rgh-latest-tag-button, .rgh-default-branch-button, .rgh-quick-file-edit, has-rgh-inner
isRepositoryActionshas-rgh
isSingleCommithas-rgh
isSingleFilehas-rgh, .rgh-copy-file, .rgh-latest-tag-button, .rgh-default-branch-button, .rgh-list-prs-for-file, has-rgh-inner
isSingleGisthas-rgh
isSingleHTMLFile.rgh-html-preview-link
isSingleTaghas-rgh
isUserProfilehas-rgh
isUserProfileMainTabhas-rgh
isUserProfileRepoTabhas-rgh

Given that many features have several page detections, the logic should probably be:

Use has-rgh-inner if at least one detection requires it
Else, use has-rgh

Ofc feature-specific deduplication markers (e.g. .rgh-copy-file) would still need to be specified "by hand".
Screenshot
No response
Example URL
n/a

Unfortunately that selector depends on where the element is, not just what page it is. For example a feature in the title of a PR might need has-rgh but if the feature is in the file list the container might be different.
Maybe we can still use this as a smart default instead of using only has-rgh, and occasionally we can still override it.

Maybe we can still use this as a smart default instead of using only has-rgh, and occasionally we can still override it.

I think this would just make it more complicated, because adding an include could then change the behavior entirely and unexpectedly. Unfortunately we need to keep it manual. The safest deduplication method is to just use the feature’s classname in deduplicate wherever possible instead of rgh/inner

authors: cheap-glitch fregante

repo: refined-github/refined-github


text:
quick-file-edit showing double icons in chrome

Description

screen-capture.webm

for some reason this feature is causing the extension to show double icons when they're files inside of a github repo. I tested it only in chrome, and a video replicating it is linked above, below the image.
this issue started to happen after a few days, and today after being annoyed about it I searched what it was and using the Identify feature button of the extension, it reported it to me and showed that it was a recent feature added two days ago.
I hope this helps. ty!
How to replicate the issue + URL
enabling quick-file-edit feature should replicate the problem.
Extension version
23.5.6
Browser(s) used
Chrome

Duplicate of https://github.com/refined-github/refined-github/issues/6598

authors: fregante pMattheew


text:
Fix clean-repo-tabs wiki count calculating

The code assumes the page counter always exists in a wiki, which is not the case if a page named "Home" doesn't exist (and thus failing back to a simple list view).
Test URLs

Wiki with "Home" page: https://github.com/pixiebrix/pixiebrix-extension/wiki
Wiki without "Home" page: https://github.com/refined-github/refined-github/wiki

Screenshot

Don’t mind me I’m just passively QAing Refined GitHub 😌

I would say that's expected. Writing our wiki means we'll be dogfooding our features there more, so it's expected these stuff comes up

Let's never use Projects then.

authors: fregante kidonng


text:
Test URLs
Screenshot

#sudo su


text:
Inconsistent tests

Multiple times I've see individual tests fail on Travis, been unable to reproduce them, and when I re-ran on Travis they were gone. I want keep a list of them here, and if particular ones are more frequent than others, I want to note that.
0.0.57 in progress, Django2 environment, Travis fails:
tests.test_live.PathRoutingMechanicalSoupTests.testDebuggerLaunch
tests.test_live.HostRoutingClientTests.test_please_wait

======================================================================
ERROR: test_please_wait (tests.test_live.HostRoutingClientTests)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/home/travis/build/refinery-platform/django_docker_engine/django_docker_engine/container_managers/docker_engine.py", line 156, in get_url
    http_port_info = port_infos['{}/tcp'.format(container_port)]
KeyError: '80/tcp'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/home/travis/build/refinery-platform/django_docker_engine/tests/test_live.py", line 137, in test_please_wait
    labels={'subprocess-test-label': 'True'}
  File "/home/travis/build/refinery-platform/django_docker_engine/django_docker_engine/docker_utils.py", line 241, in run
    return self.lookup_container_url(container_spec.container_name)
  File "/home/travis/build/refinery-platform/django_docker_engine/django_docker_engine/docker_utils.py", line 83, in lookup_container_url
    return self._containers_manager.get_url(container_name)
  File "/home/travis/build/refinery-platform/django_docker_engine/django_docker_engine/container_managers/docker_engine.py", line 160, in get_url
    container_name, container_port, port_infos
django_docker_engine.container_managers.docker_engine.ExpectedPortMissing: On container container-name, port 80 is not available, but these are: {}

======================================================================
ERROR: testDebuggerLaunch (tests.test_live.PathRoutingMechanicalSoupTests)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/home/travis/virtualenv/python3.6.3/lib/python3.6/site-packages/urllib3/connectionpool.py", line 595, in urlopen
    chunked=chunked)
  File "/home/travis/virtualenv/python3.6.3/lib/python3.6/site-packages/urllib3/connectionpool.py", line 393, in _make_request
    six.raise_from(e, None)
  File "<string>", line 2, in raise_from
  File "/home/travis/virtualenv/python3.6.3/lib/python3.6/site-packages/urllib3/connectionpool.py", line 389, in _make_request
    httplib_response = conn.getresponse()
  File "/opt/python/3.6.3/lib/python3.6/http/client.py", line 1331, in getresponse
    response.begin()
  File "/opt/python/3.6.3/lib/python3.6/http/client.py", line 297, in begin
    version, status, reason = self._read_status()
  File "/opt/python/3.6.3/lib/python3.6/http/client.py", line 266, in _read_status
    raise RemoteDisconnected("Remote end closed connection without"
http.client.RemoteDisconnected: Remote end closed connection without response


text:
Update cats-core to 2.6.0

Updates org.typelevel:cats-core from 2.4.2 to 2.6.0.
GitHub Release Notes - Changelog - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Files still referring to the old version number
The following files still refer to the old version number (2.4.2).
You might want to review and update them manually.
project/plugins.sbt

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.typelevel", artifactId = "cats-core" } ]

labels: library-update, semver-minor, old-version-remains

Superseded by #85.

repo: regadas/scio-cats


text:
Fix patches & line-endings

Using the same procedure as Ray originally, and documented by Isuru (though that README hasn't been merged yet from the 3.10 PR)

Done in https://github.com/conda-forge/python-feedstock/pull/501/commits/63e4dd7bdf519efaf23d77a67b21676755be1667

repo: regro-cf-autotick-bot/python-feedstock


text:
🛑 SLC Remote Lab (rlab.binus.ac.id) is down

In 9e0d4f4, SLC Remote Lab (rlab.binus.ac.id) (https://rlab.apps.binus.ac.id/) was down:

HTTP code: 502
Response time: 10808 ms

Resolved: SLC Remote Lab (rlab.binus.ac.id) is back up in 4312cd2.


text:
🛑 GreatNusa.com is down

In fabeaa9, GreatNusa.com (https://greatnusa.com) was down:

HTTP code: 403
Response time: 49 ms

Resolved: GreatNusa.com is back up in bd25888.


text:
🛑 BINUSMAYA (Academic Services) is down

In 903048f, BINUSMAYA (Academic Services) (https://acadservices.apps.binus.ac.id/LoginAD.php) was down:

HTTP code: 503
Response time: 786 ms

Resolved: BINUSMAYA (Academic Services) is back up in 1ce6d2e.


text:
Extend overlay effects?

Extending is more work and probably beyond scope; however, I like the idea of improving the aesthetic of the overlay with a soft blur.
What do you think?
Here's a WIP.

I dont think this should be part of a library. The default css should be as small as possible and the user be able to add his own stuff.

authors: paxperscientiam rejas

repo: rejas/imagelightbox