ARROW-15083: [C++][Gandiva] Implement Conv Function

I will close that PR, as there is a PR for the arrow master: https://github.com/apache/arrow/pull/12306


fix(home): display tags properly [EE-2153]

Please review.

closes https://github.com/portainer/portainer/issues/6276


Crunchyroll Premium login not working. User not found.

I typed
youtube-dl "-u username" "-p password" crunchyrollurl
This comes up:
[Crunchyroll] Logging in
[Crunchyroll] 681829: Downloading webpage
ERROR: crunchyroll returned error: User  username not found.
For username, I tried my email associated with my crunchyroll and the crunchyroll username. It still gives me the same message.

Post the full output of youtube-dl when run with --verbose option.

C:\Users\H\Desktop>youtube-dl --verbose
[debug] System config: []
[debug] User config: []
[debug] Command-line args: [u'--verbose']
[debug] Encodings: locale cp1252, fs mbcs, out cp437, pref cp1252
[debug] youtube-dl version 2015.10.12
[debug] Python version 2.7.8 - Windows-8-6.2.9200
[debug] exe versions: none
[debug] Proxy map: {}
Usage: youtube-dl [OPTIONS] URL [URL...]
youtube-dl: error: You must provide at least one URL.
Type youtube-dl --help to see a list of all options.

@hdubb
You should post the result of "youtube-dl -u  --verbose ". ;-)

For some reason, when I typed --verbose, it started working and downloaded the file.


Visual changes

I made some changes to the code as some code was not allowing the list to function in the way that it should (the list is now in a numerical order). I also made changes to the color, font, and layout of the page to make it a little more appealing. I also changed the way the code was presented in the file as a lot of it was jumbled up and not easy to understand.

@RRBCARDO thanks for contributing and pls do follow me


[DOC] tiny typo fixed

Description
(Brief description on what this PR is about)
Checklist
Essentials

[x] PR's title starts with a category (e.g. [BUGFIX], [MODEL], [TUTORIAL], [FEATURE], [DOC], etc)
[ ] Changes are complete (i.e. I finished coding on this PR)
[ ] All changes have test coverage
[ ] Code is well-documented

Changes

[ ] Feature1, tests, (and when applicable, API doc)
[ ] Feature2, tests, (and when applicable, API doc)

Comments

If this change is a backward incompatible change, why must this change be made.
Interesting edge cases to note here

I found mis enter.

Job PR-704/1 is complete.
Docs are uploaded to http://gluon-nlp-staging.s3-accelerate.dualstack.amazonaws.com/PR-704/1/index.html


How to combine unique and stategy merges

I can't seem to figure out how combine the unique and strategy merge options. I want to be able to prepend the results of a plugins array and then only keep unique plugin instances based on the constructor name. The default behavior of the unique function is to keep the first unique instance and I was the latter unique instance essentially. Example below:
configA = {
   plugins: [
        new MiniCssExtractPlugin({
            filename: 'main.[contenthash].css',
        }),
}

configB = {
   plugins: [
        new MiniCssExtractPlugin({
            filename: 'main.css',
        }),
}

merge({
      customizeArray: merge.unique(
        'plugins',
        ['MiniCssExtractPlugin'],
        plugin => plugin.constructor && plugin.constructor.name
      )
    })(configA, configB)

This will result in the MiniCssExtractPlugin plugin instance from configA being kept, and I want to keep the one from configB basically.

The provided merge.unique always keeps the first one, but you can change it a bit as your customized unique function. Like,
 import { differenceWith } from 'lodash';
 function mergeUnique(key, uniques, getter = a => a) {
   return (a, b, k) => (
     k === key && [
-      ...a,
+      ...b,
       ...differenceWith(
-        b, a, item => uniques.indexOf(getter(item)) >= 0
+        a, b, item => uniques.indexOf(getter(item)) >= 0
       )
     ]
   );

merge({
      customizeArray: mergeUnique( // use your customized version
        'plugins',
        ['MiniCssExtractPlugin'],
        plugin => plugin.constructor && plugin.constructor.name
      )
    })(configA, configB)

I also expected merge unique to apply precedence to the item on the right light the rest of the merge package.

There's a fix for this in #135 (v5). I changed the precedence there to pick the last first as that's the best option given the way webpack configurations are structured.


Add jasmine javascript testing setup to Portal just like it is added to LARA. [#94994264]

Please wait to review until Travis runs.  I need to make sure the jasmine:ci task is running on Travis.

Jasmine runs on Travis: https://travis-ci.org/concord-consortium/rigse/jobs/64296419

Looks good.


zookeeper watch support

This pull request adds zookeeper watch support.

LGTM

when will this ship in a release?


face_distance vs compare_faces functionality, is there a better/more accurate choice?

face_recognition version: 1.2.3
python version: 3.73
OS: Ubuntu 18.04 / OSX 10.15.3
I'm using the face_distance calcualation to give me the closest match to the face I'm comparing and the results I'm getting are pretty bad.  Lets say I've trained the system using soccer players from 4 teams, using between 5-15 images from each player as the encodings.
I run a single soccer match thru the DB and it is matching faces from players not in the match at much higher levels than those in the match, pretty consistatly.
I'm wondering if anybody has compared the accuracy of doing closest match via face_distance to the compare_faces function with the true/falce array coming back?
Is one of these methods much more accurate than the other?

If you look at the code, you will see that compare_faces actually calls the face_distance function with a default tolerance of 0.6. If you want stricter accuracy, you may want to try to decrease the tolerance.

Amazing, thank you for the response.Have a great night! -- Stephen Bickle On June 22, 2020 at 11:15:00 PM, rafale77<EMAIL_ADDRESS>wrote:
If you look at the code, you will see that compare_faces
actually calls the face_distance function with a default tolerance
of 0.6. If you want stricter accuracy, you may want to try to
decrease the tolerance.
—
You are receiving this because you authored the thread.
Reply to this email directly,
view it on GitHub, or
unsubscribe.

[
{
"@context": "http://schema.org",
"@type": "EmailMessage",
"potentialAction": {
"@type": "ViewAction",
"target": "https://github.com/ageitgey/face_recognition/issues/1165#issuecomment-647932266",
"url": "https://github.com/ageitgey/face_recognition/issues/1165#issuecomment-647932266",
"name": "View Issue"
},
"description": "View this Issue on GitHub",
"publisher": {
"@type": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]


modified paths and filenames to prepare for  future project edit/dele…

Hi Carlos,
would you mind modifying your structure (as in the pull request) to prepare the project for edit/delete functionality?
Thanks.

Do you have any reason why the post statement is only
app.post('/projects'...

instead of
app.post('/projects/add'...

I think the second approach could be better is we want to add edit/delete functionality.
app.post('/projects/edit'

What do you think?


Improve Controller Support

Wait.. that code I just removed, is required for another feature I made, which is making the scroll buttons in the lookup window clickable. I'll have to combine them with this.

Merged into develop for the upcoming 1.9 release. Thanks!


more-prompt vs hit-enter prompt: different behavior of q press

I observed that it is very easy to start macro recording by accident because pressing q has different behavior in more-prompt and different in hit-enter prompt (in more-prompt it just exits to normal mode, in hit-enter it also will start macro recording). Is it expected?
Quite common scenario:

after vim is started, some plugin prints a message (for example some error)
you press q to close the message, then i to start insert mode
depending on the message length the behavior is different

hit-enter:

more-prompt

I think it's consistent with the documentation, even though I agree it can be unexpected in practice.
At the more-prompt, only a small number of commands are valid.  From :h pager:

Any other key causes the meaning of the keys to be displayed.

q is one of them; it stops the listing:

q, <Esc> or CTRL-C                    stop the listing

OTOH, when you hit a key at the hit-enter prompt which is not valid, it automatically closes the pager, and you're back in regular normal mode, where q gets back its default meaning, i.e. start a recording.
In any case, as a workaround, you could try this code:
augroup hit_enter_prompt | au!
    if has('nvim')
        au CmdlineLeave : call s:hit_enter_prompt_no_recording()
    else
        au CmdlineLeave : call timer_start(0, {-> s:hit_enter_prompt_no_recording()})
    endif
augroup END
fu s:hit_enter_prompt_no_recording() abort
    if has('nvim')
        nno q <c-\><c-n>
        return timer_start(0, {-> execute('nunmap q', 'silent!')})
    endif
    if mode() isnot# 'r' | return | endif
    nno <expr> q execute('nunmap q', 'silent!')[-1]
    if exists('##SafeState')
        au SafeState * ++once sil! nunmap q
    else
        let q = {}
        let q.timer = timer_start(10, {-> mode() isnot# 'r' && q.nunmap()}, {'repeat': -1})
        fu q.nunmap() abort
            call timer_stop(self.timer)
            sil! nunmap q
        endfu
    endif
endfu


use tabs instead of spaces when indenting plists

Xcode uses tabs for indention in plist files, so editing outside of Xcode causes mis-aligned indention.

Thanks


bug: sic_classification doesn't seem to be consistent with current SIC codes online

The codes in the exported sic_classification dataset require 5-digit codes:

The SIC code database only allows codes containing a maximum of 4-digits:

It is very likely that the sic_classification dataset is outdated, as it was first merged 4 years ago.
Possible actions (not mutually exclusive):
Determine if the dataset is referring to some different SIC classification system
Deprecate the sic_classification dataset
Update the sic_classification dataset to the latest version
AB#10292

It seems that this system is consistent with the south African SIC codes:
https://www.statssa.gov.za/additional_services/sic/mdvdvmg4.htm#MAJOR DIVISIONS,DIVISIONS AND MAJOR GROUPS


Add mv/mh/pv/ph

I have a hard time remembering which axis is X and which is Y, I tend to always choose the wrong one, making mx and my a minefield. 😅
It'd be awesome if Rebass had support for mv (margin vertical) and mh (margin horizontal), as well as the equivalent padding props. That I definitely won't mess up.

You can always wrap the component to map props however you want, but I've always leaned towards the x-axis and y-axis shorthand, since that's the same as most CSS properties (e.g. translateX).
This does make me curious though, aren't x-axis and y-axis sort of international (i.e. not English-only) conventions?

aren't x-axis and y-axis sort of international (i.e. not English-only) conventions?

Yes, I just can't remember them 🙈
Will close!


Allow ADO.NET Data Services to return non-entity POCO types

Porting this suggestion from ASP.NET UserVoice site. Please triage as appropriate
https://aspnet.uservoice.com/forums/41199-general-asp-net/suggestions/487712-allow-ado-net-data-services-to-return-non-entity-p
Right now it seems I can only return entity types or entity framework simple types. I would like to return IQueryable from a custom resource method.

This looks more like a Data Services request than an EF feature request.


Update SNAPSHOT for upcoming preview release.

Codecov Report

Merging #639 into dev will decrease coverage by 0.05%.
The diff coverage is n/a.

@@             Coverage Diff             @@
##                dev    #639      +/-   ##
===========================================
- Coverage     46.55%   46.5%   -0.06%
+ Complexity     2226    2222       -4
===========================================
  Files           109     109
  Lines         25409   25409
  Branches       4187    4187
===========================================
- Hits          11830   11817      -13
- Misses        11546   11558      +12
- Partials       2033    2034       +1

Flag
Coverage Δ
Complexity Δ

#JDBC42
46.39% <ø> (ø)
2218 <ø> (+4)
:arrow_up:

#JDBC43
46.32% <ø> (-0.15%)
2215 <ø> (-10)

Impacted Files
Coverage Δ
Complexity Δ

...m/microsoft/sqlserver/jdbc/SQLServerResultSet.java
32.38% <0%> (-0.9%)
238% <0%> (-7%)

...ncurrentlinkedhashmap/ConcurrentLinkedHashMap.java
38.54% <0%> (-0.22%)
42% <0%> (ø)

...om/microsoft/sqlserver/jdbc/SQLServerBulkCopy.java
52.54% <0%> (-0.2%)
240% <0%> (+1%)

...m/microsoft/sqlserver/jdbc/SQLServerStatement.java
59.45% <0%> (+0.1%)
131% <0%> (+1%)
:arrow_up:

...in/java/com/microsoft/sqlserver/jdbc/IOBuffer.java
54.46% <0%> (+0.29%)
0% <0%> (ø)
:arrow_down:

...om/microsoft/sqlserver/jdbc/ReaderInputStream.java
47.19% <0%> (+1.12%)
17% <0%> (ø)
:arrow_down:

...om/microsoft/sqlserver/jdbc/SimpleInputStream.java
52.59% <0%> (+1.48%)
12% <0%> (+1%)
:arrow_up:

Continue to review full report at Codecov.

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


DOCS-Add-NodeLocal-DNSCache-to-ebpf

Add NodeLocal DNSCache to unsupported list
Product Version(s):
CE 3.17 and 3.18
Issue:
n/a
Link to docs preview:

SME review:

[ ] An SME has approved this change.

DOCS review:

[ ] A member of the docs team has approved this change.

Additional information:

Merge checklist:

[x] Deploy preview inspected wherever changes were made
[ ] Build completed successfully
[ ] Test have passed

Do we need to update the node-local-dns doc too?https://github.com/tigera/docs/blob/main/calico-enterprise/networking/configuring/node-local-dns-cache.mdx

Fair enough if that's the convention.
(I have beef with that convention, but that's nothing to do with this PR.)


Add animated gif preview

Would be nice to have an animated preview or screenshot of the spinners without requiring any setup/config changes to see them :) You could also use https://asciinema.org/

It's been on my todo list for a while, just forgot about it. I'll get one up soon

Asciinema demo has been added to README


Add MySQL query external function library

Add external function library providing means to access MySQL database via JDBC.

Addressed by #33


Searchable docs

Add a search-field to https://www.rerun.io/docs

We have some constraints for how search should work:

It should be versioned, or require minimal effort to make it versioned.
We may want to re-use it for in-app documentation.
It must be able to ingest not only the docs/examples on rerun.io, but also our API references (e.g. https://ref.rerun.io/docs/python,  for any present and future languages)

We've decided to use meilisearch as the search engine. It's fast, flexible enough, and they have SDKs for all the languages we'll be using to interact with it (Rust, JS). We can use instantsearch to integrate it into our frontend.
The content indexing part most of the work here. For our markdown docs/examples, we just need to collect titles, content, and URLs of each document and example, and all the infrastructure there is already in place. But for API references, we need to use an external tool to generate machine-readable "documentation", load it, and extract what we need out of it. We'll use the following tools for our currently supported languages:

Rust: rustdoc's nightly JSON output via rustdoc_json and rustdoc_types
Python: mkdocs backend griffe, with our own type definitions
C/C++: doxygen's XML output, also with our own type definitions

Some notes:

In the search window, we should clearly show what type each hit is (which language API, or neither), e.g. with an icon for each language
When searching for some archetype, we should make sure the search window shows the high-level archetype doc first, followed by the API docs for each subsequent language


Setup dependabot with bit.dev private packages

Hi there, just wondering if there is a way to setup dependabot to check private components that live here bit.dev . For more context it is a react project with its package.json file. There are two packages the project is using that are private and live on bit.dev.

Closing for lack of activity


"Preserving" indentation of "injected" strings based on the indentation of their injection point

I'm guessing there's enough prior art here to know that what I want here is not a good idea, all things considered, but I have a use case that looks something like this:
let dedent = await import("https://unpkg.com/string-dedent@3.0.1/dist/dedent.mjs?module").then(m => m.default);
if(true) {
  let plants = dedent`
    plants
      cabbage
      fern
  `;
  console.log(plants);
  let result = dedent`
    life
      animals
        rabbit
        frog
      ${plants}
  `;
  console.log(result);
}

That outputs this:
plants
  cabbage
  fern

life
  animals
    rabbit
    frog
  plants
  cabbage
  fern

Whereas I'm trying to outputs this:
life
  animals
    rabbit
    frog
  plants
    cabbage
    fern

I'm wondering - if the "injected" string is indented, then isn't the dev's intention clearly that the injected string should "live at" that level of indentation?
I guess the key question is: Are there reasonable/common cases where the behaviour I desire here is counter-intuitive?
It's very possible that I'm blinded by my specific use case here. I'm posting this issue because this is basically the first time I've needed to use a dedent library (my use case is LLM prompt construction), and it's possible (though unlikely) that some "fresh eyes" on this might help break away from prior art / conventional wisdom in a way that actually makes sense in terms creating an intuitive developer experience.

Please feel free to close if this is actually an age-old discussion, or something - i.e. something that almost certainly is a bad idea.

Closing this as a dupe of https://github.com/tc39/proposal-string-dedent/issues/25. The committee recognizes this use case, but thinks it can be addressed as a follow up after the core proposal.

@jridgewell Ah, sorry for missing that. Can I quickly ask: Does the committee think that the non-preserved-indent mode is more intuitive as the default behavior?

Maybe it is better for having it enabled by default?

Does the committee think that the non-preserved-expression-indent mode is more intuitive as the default behavior?

Correct. Just having regular string concatenation is the least surprising behavior.


Research Firebase for Web

Problem
Currently we use react-native-firebase for tracking performance issues on mobile.
According to docs https://rnfirebase.io/platforms the lib doesn't support web platform. It would be beneficial to use firebase to track web performance as well.
Solution
We need to do some reaserch and check if we are able to use the the firebase SDK to use performance tracking on the web.
We already have Firebase set up for our mobile platforms, and recently we started using it.
And with relatively low effort, we can extend this setup to the web platform.
It allows us to monitor default key metrics (e.g. firstContentfulPaint ) and our custom metrics (e.g.  trie_initialization )
We can add additional context to the trace, like userId or the number of reports, which can be valuable for diagnosing issues or analyzing performance trends.
In practice, this means that we both can use the dashboard to track any potential performance regressions.
While it might feel somewhat similar to Grafana in terms of monitoring capabilities, Firebase is relatively easier to configure—especially since we already have the setup in place for mobile.
Here are some screenshots from firebase console from test project:

@rinej could you provide some examples of how we're using react-native-firebase to track mobile performance issues now?
Could you also please fill in this information:

Library size:

GitHub stars:

Last release date:

Thank you!

How we currently use react-native-firebase for tracking performance:
Custom Metrics Tracking:
We monitor specific custom metrics to gain deeper insights into key functionalities. For example:

chat_render: Tracks the time taken to render the chat interface.
load_search_options: Monitors the duration for loading search options.
switch_report: Measures the time spent switching between reports.

Detailed Trace Logging:
We log additional details in each trace, such as accountId, the number of reports, and the length of personalDetails. This helps in identifying performance bottlenecks more easily.
Network Request Timing:
We track the time taken for network requests, such as ReconnectApp or OpenApp, to monitor their performance.
Crashlytics Integration:
We use the crashlytics module to help identify the root causes of crashes. (Currently, crashlytics is only available on mobile platforms. For web monitoring, we can use other tools like Sentry or Bugsnag.)
Flexibility
As this is a relatively new initiative, we have the flexibility to add or modify metrics as our needs evolve.
Url to firebase console -> https://console.firebase.google.com/u/0/project/expensify-chat/performance/app/android:com.expensify.chat/trends?time=last-thirty-days
Additional Info:
New package npm url: https://www.npmjs.com/package/firebase
Library size:

the whole firebase package - 24.7 MB (https://www.npmjs.com/package/firebase)
just the module we need firebase/performance -> 615 kB (https://www.npmjs.com/package/@firebase/performance)

GitHub stars: 4.8k
Last release date: a day ago (22 August)

Thanks! I'll bring this to Slack tomorrow

I created the Draft PR with the project configuration: https://github.com/Expensify/App/pull/47795
We will need someone from Exp to create new Web project in firebase console so we can add the proper config:
FIREBASE_WEB_CONFIG: {
        apiKey: 'YOUR_API_KEY',
        authDomain: 'YOUR_AUTH_DOMAIN',
        projectId: 'YOUR_PROJECT_ID',
        storageBucket: 'YOUR_STORAGE_BUCKET',
        messagingSenderId: 'YOUR_MESSAGING_SENDER_ID',
        appId: 'YOUR_APP_ID',
        measurementId: 'YOUR_MEASUREMENT_ID',
    },

We have a draft PR

The PR is ready for review.
We will just need someone from the internal team to create new Firebase Project and set the proper environmental variables so we can take it from ENV. More details in the PR -> https://github.com/Expensify/App/pull/47795

the issue was resolved in the following ticket: https://github.com/Expensify/App/issues/49443#issuecomment-2361239813


Is there opportunity to use CCD with user groups?

Problem Statement
I have Zitadel or anyone other SSO with configured user groups. I want to split resources in my vpn network by access for groups of users. In most cases .ccd used for it. How can we do it with that plugin?
Proposed Solution
Add splitted configurations for groups with routes to resources
Additional information
No response
Acceptance Criteria
No response

I can develop such an feature, I may need some help for design a admin friendly interface
What about 2 new flags
--client-config-dir <ccd-dir>
--client-config-claim roles

In case that the claim contains a list of string, multiple files will be loaded can concatenate

Sounds good, but what will the flag --client-config-claim roles do?

And there is a moment, I'm not sure if this is possible at all, since usually the client's ip is specified in the ccd configurations.

--client-config-claim roles
openvpn-auth-oauth2 will ask the IDP about an ID Token (OIDC authorization code flow) and the ID Token has multiple claims (fields) based on the requested scope. For example if a groups scope is requested, then the ID Token may have an claim called groups which contains all groups.

Okey, I understood now. But can you check what I said before about client's IP, because I think it can be bottle neck in this task

but client IP is an user level setting, but an group based setting or am I wrong?

We need to set subnet for group, not specific IP like in ccd config. I'm talking about that.

At least this feature does not exists in OpenVPN yet
References:

https://community.openvpn.net/openvpn/ticket/1173
https://community.openvpn.net/openvpn/ticket/1419

@DenVilk IPAM for clients is not in scope, I feel that could be a bit error prune at the moment. openvpn-auth-oauth2 has no state and can't save client IPs.


dev error: (node:42372) Warning: To load an ES module, set "type": "module" in the package.json or use the .mjs extension. (Use node --trace-warnings ... to show where the warning was created)

Environment

Operating System: Darwin
Node Version:     v16.13.0
Nuxt Version:     3.0.0-rc.3
Package Manager<EMAIL_ADDRESS>Builder:          vite
User Config:      modules, build, experimental, unocss, colorMode
Runtime Modules<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>./modules/arco
Build Modules:    -

Reproduction
project: https://github.com/hehehai/arco-nuxt3
Describe the bug
import { defineNuxtConfig } from 'nuxt'

export default defineNuxtConfig({
  modules: [
    '@vueuse/nuxt',
    '@unocss/nuxt',
    '@pinia/nuxt',
    '@nuxtjs/color-mode',
    ['./modules/arco', { icon: true }],
  ],
  // build
  build: {
    transpile: ['@arco-design/web-vue'],
  },
  experimental: {
    reactivityTransform: true,
    viteNode: true,
  },
  unocss: {
    preflight: true,
  },
  colorMode: {
    classSuffix: '',
  },
})

<script setup>
import {Message} from "@arco-design/web-vue";

Message.success("测试")
</script>

run dev then open host

only dev show this error, build and start all success
Additional context
ref: https://github.com/hehehai/arco-nuxt3/issues/2
Logs
No response

Same for me, but I can't trace what dependency it's coming from as when I attempt to use --trace-warnings then I'm still advised to use the flag and no trace is shown.
The command I'm using is node --trace-warnings node_modules/nuxi/bin/nuxi.mjs dev but it doesn't make the blindest bit of difference.

cc: @pi0 - it might be worth passing along node flags if we're not already doing so in nuxi...

That would be a big win.

@danielroe Can we please reopen this? It seems node flags still aren't being passed along, so I'm having a very hard time tracking down these errors in my app.

Happens with Nuxt 4 preview, I downloaded Dashboard sample, ran it from scratch and encountered this issue immediately-- no idea how to track it down.


Saving Resource Variables without Copy

Provides a solution for the increase in memory usage when saving models with large sparsely accessed resource variables by avoiding the copying of the variables. The kernel of ReadVariableOp is modified to convert variables that were sparsely accessed from copy-on-read mode to copy-on-write mode under an exclusive lock. The conversion is disabled in the default setting and only occurs when the Python function _read_variable_op is called from class ResourceVariableSaveable during the saving of resource variables.
See issue #54104.

I don't like that ReadVariableOp does this COR-to-COW conversion as a side effect (even if it only happens when no_copy is true). How about adding a new op TurnOffCopyOnRead to do this job?

Thanks for the comment. I've introduced a new ReadVariableWithoutCopyOp, which is exclusively called when saving resource variables. For copy-on-write variables, the op behaves like ReadVariableOp. For copy-on-read variables, the kernel again acquires an exclusive mutex, but avoids the side effect by directly reading the variable instead of changing its type.

The new DisableCopyOnReadOp is called when a resource variable is saved.

Thanks for the update! Overall looks good, except for some minor issues.

I can't reproduce the PyLint error, and I also don't see any lines that are longer than 80 characters in the diff.

Maybe the test was against an older version. Or maybe it's caused by whitespaces. (CCing @mihaimaruseac who may know more.)

Rerunning the pylint job, seems to have been using an old version?
Anyway, if still broken, please ignore.

There are some api_compatibility_test CI failures. Please run bazel run //tensorflow/tools/api/tests:api_compatibility_test -- --update_goldens True to update the API golden files.

This fails with ModuleNotFoundError: No module named 'tensorflow.core.kernels'.

Seems your Python paths are not set up properly. I'll try fixing the CI errors internally.


Update the byetorder crate to 0.3.8 or later (currently 0.3.9)

My travis build is failing to build byteorder 0.3.7 for rust nighly, and it seems that this is fixed in 0.3.8+.
The relevant byteorder fix:
https://github.com/BurntSushi/byteorder/commit/b8d12248946fcac08239373551fc48abe72b9ace
My travis build, that's compiling fine on beta2 but not on nightly:
https://travis-ci.org/madeso/rust-game-engine/builds/61722932
The dependency chain from me to byteorder is:
glium(any version)->image(any version)->byteorder(0.3.7)

Must be some caching issue, we’re not even depending on 0.3.7. cargo should just download the newest version…

I'm not 100 on the semver syntax, but if you're not dependening on the version, shouldn't the dependency be 0.3 or ^0.3.7?
http://doc.rust-lang.org/semver/semver/index.html#requirements

This is not how cargo works. Dunno if that is a bug or not.

That's at least what the documenation on both crates.io and rust-lang says. Then again the documentation might not be updated.
http://doc.crates.io/crates-io.html#using-crates.io-based-crates


spike(http): add swagger validator middleware

This adds an HTTP middleware that performs validation on both requests
and responses to the API.
If running without the assets build tag, it looks in a few reasonable
places on disk to detect swagger.yml. Otherwise, it expects the
swagger.yml Asset to exist.
The validation from kin-openapi/openapi3filter has a lot of whitespace,
so in this commit, instead of logging it which would escape the newlines
and tabs, we just printf the message, which looks like:
SWAGGER RESPONSE VALIDATION ERROR: Error at "/authorizations/0/permissions/16/resource/type":JSON value is not one of the allowed values
Schema:
  {
    "enum": [
      "authorizations",
      "buckets",
      "dashboards",
      "orgs",
      "sources",
      "tasks",
      "telegrafs",
      "users"
    ],
    "type": "string"
  }

Value:
  "variables"

An enhancement here would be to do something smarter with the message --
perhaps embed it into an HTTP header or trailer.
This commit does not include tests for the swaggervalidator middleware.
It also has to record the request and response in a separate
bytes.Buffer, which is created from scratch on every request. There is
likely room for improvement on how we deal with those allocations.

I just rebased this on master. It didn't require any extra changes.
The couple pieces I'm specifically unsure about:

Whether just printing to stdout is acceptable here. Logging is generally preferred, but logfmt does not play well with messages that contain a lot of whitespace like these validation errors. Maybe shoving the error in an HTTP header would be nice since that can be readily inspected from client code. We can set a normal header for request validation, but I think response validation would have to be an HTTP trailer.
Where the middleware should be instantiated. Right now it's happening inside the PlatformHandler which doesn't quite feel right. Maybe that's okay for now.
Under what circumstances the middleware should be short-circuited. It's probably desirable to be on by default in development (i.e. without the assets build tag) and off by default in production (i.e. with the assets build tag), but configurable either way.

So far this has been very helpful in clearly calling out swagger discrepancies. See issues I've recently filed with the area/api-docs label: https://github.com/influxdata/influxdb/issues?q=is%3Aissue+is%3Aopen+label%3Aarea%2Fapi-docs


Update mdb-requirements.md

Cosmetic change (missing word)

@JohanFreelancer9 Please copy review

Issue#https://github.com/MicrosoftDocs/microsoft-365-docs/issues/7224


Can you run this in production?

I've been researching quite a bit on running Rails/Sinatra in production and seen the recommended approach is to start the app servers as services (under systemd or runit) and go from there.
Then I stumbled upon the post on "Running Ruby Apps in Production" and this. So I was wondering, is it recommended to run procodile vs. systemd in production?
The only downside I see here is the inability to use it as an init process, meaning make it so it starts the programs at startup (in case the server restarts).

We run Procodile across lots of production applications and find it far more flexible and convenient than using systemd or any system-level process manager. You can (and probably should) configure your system process manager to start your Procodile supervisors when the system boots.

@adamcooke is it possible to share your systemd configuration for starting Procodile? It's the only thing stopping me from using it in production.

I found this from Eye, you might want to add it as part of your Wiki:
github.com/kostya/eye/wiki/Manage-with-systemd-(WIP)

This has been answered here on another one of Adam's repos 😃

For starting after reboot we are using crontab
@reboot cd /home/api/app && bin/procodile >> /home/api/app/log/cron.log 2>&1


Repo sync for protected CLA branch

The pull request is created from main637751019308487192 to main to fix git push error for protected CLA branch

@ghogen : Thanks for your contribution! The author(s) have been notified to review your proposed change.


\frac from / not working properly with functions

When i write $ f(x)/x $ and press Space it should convert to $ \frac{f(x)}{x} $ however it always gives me $ f\frac{x}{x} $.

I suggest to use $(f(x))/x$ in such situations - I think the existing functionality is correct, otherwise it's not clear what should be in the numerator.

I see... though i think using { } instead of ( ) would make more sense.
Anyway i found using a Shorthand for fractions works better for me so this isnt an issue anymore.


Testing: How to build good IR tests?

For the existing AST-based source-to-source path, our testing strategy has mostly been to confirm that our code produces the exact same (textual) output as fxc or glslang. In some cases we feed slightly different input to slangc than we do to fxc or glslang either to test that Slang is added annotations it is supposed to, or to confirm that Slang is generating appropriate GLSL.
The challenge that arises once we have the IR in the picture is that this kind of comparison-based testing isn't really viable, since it is much harder to guarantee that we will produce identical output to the existing compilers (down to small details of instruction ordering, etc.).
The right testing strategy here is probably two-fold:

We should have isolated IR tests where we output Slang IR and compare it to a baseline. These need to be kept narrow, so that we don't have to repeatedly update baselines whenever we change the lowering pass and/or optimizations.

We need more end-to-end tests where we generate code and then actually run it. The challenge there is that we don't have support for running GPU work on AppVeyor. We might be able to run some tests through "refrast" just to confirm that things work. Another alternative is to have some focused tests where we generate CPU code and/or interpret the IR.

Each of these options requires work. We need to front-load this work before we get too deep into the IR implementation process, or else we are going to have a hard time having any confidence in what we build.

On item (2) above, I've confirmed that we can use the Microsoft "Warp" software renderer to run D3D11 tests on AppVeyor, so that will suffice for some end-to-end testing. The render-test fixture should probably be expanded to support running compute shaders too, so it is a "one stop shop" for end-to-end tests. The current bytecode VM should then be integrated into that application as an alternative back-end (akin to D3D11 vs. GL).
For cross-compilation to GLSL we probably need to continue to use hand-crafted GLSL for examples of desired output (and then hand-crafted SPIR-V when we can bypass glslang). The main issue there will be if we have to keep reviving the expected output for every little change to the IR or optimizations.

Closing this, since we have resolved the original question. We still need to actually implement IR tests around cross-compilation, but we know how they need to work.


Error while starting the meeting

I have deployed the fresh setup with some modifications in the files to rebrand the actual bigbluebutton
Changes:

File: templates/bbb-on-aws-bbbappscalable.template.yaml
Line: 375:
From  "wget -qO- https://ubuntu.bigbluebutton.org/bbb-install.sh | bash -s -- -v xenial-220 -s $instance_fqdn -e ${BBBOperatorEMail} -c $turn_fqdn:$turnsecret"
to  "wget -qO- https://bbb-install.s3.us-east-2.amazonaws.com/bbb-install-v2.sh | bash -s -- -v xenial-220 -s $instance_fqdn -e ${BBBOperatorEMail} -c $turn_fqdn:$turnsecret"

File: templates/bbb-on-aws-bbbappsingle.template.yaml, Line: 330 with same changes

File: templates/bbb-on-aws-bbbturn.template.yaml, Line: 308 with same changes

This 'https://bbb-install.s3.us-east-2.amazonaws.com/bbb-install-v2.sh' file has exactly the same code as in default file " https://ubuntu.bigbluebutton.org/bbb-install.sh" except following lines:
sed -i 's/clientTitle:.*/clientTitle: SWYE360/g' /usr/share/meteor/bundle/programs/server/assets/app/config/settings.yml     sed -i 's/appName:.*/appName: SWYE360/g' /usr/share/meteor/bundle/programs/server/assets/app/config/settings.yml     sed -i 's/copyright:.*/copyright: " 2020 SWYE360 Learning Platform"/g' /usr/share/meteor/bundle/programs/server/assets/app/config/settings.yml     sed -i 's/helpLink:.*/helpLink: https:\/\/www.swye360.com\/virtual-classroom-help/g' /usr/share/meteor/bundle/programs/server/assets/app/config/settings.yml     sed -i 's/defaultWelcomeMessage=Welcome to <b>%%CONFNAME%%<\/b>!.*/defaultWelcomeMessage=Welcome to <b>%%CONFNAME%%<\/b>!/g' /usr/share/bbb-web/WEB-INF/classes/bigbluebutton.properties     sed -i 's/defaultWelcomeMessageFooter=.*/defaultWelcomeMessageFooter=/g' /usr/share/bbb-web/WEB-INF/classes/bigbluebutton.properties     wget -O /var/www/bigbluebutton-default/default.pdf https://bbb-install.s3.us-east-2.amazonaws.com/default.pdf     wget -O /var/www/bigbluebutton-default/favicon.ico https://bbb-install.s3.us-east-2.amazonaws.com/favicon.ico     wget -O /var/www/bigbluebutton-default/images/favicon.png https://bbb-install.s3.us-east-2.amazonaws.com/favicon.png
The whole setup runs perfectly and deployed without any errors. I checked the events logs in autoscaling groups. But when i go to start session through greenlight, it shows 'Oops, there was an error when starting the meeting!'. I run destroy command and again run the setup command, but without any success
This setup used to work 2 months back but now is not working. Is there any way to debug?

Hi @vsinghal339,
a good starting point for debuggin is to take a look at the logs collected in cloudwatch logs.
you should find logs for all related services in there.
the error itself can mean a lot of different things. to clarify try to use a setup without your config customizations. if that works, then most likely some of the customizations is errorous. work step by step through your custom code and check if the configs look good after each of your sed commands.
for that amount of sed. i would rather place a customzed config at s3 and sideload from there. much easier to maintain.
cheers!


Use loremipsum endpoint to generate the random text

Right now, there is a little discrepancy in the functioning of the app.

The app has a https://dqrura49d0.execute-api.us-east-1.amazonaws.com/random-phrase endpoint, which retruns a random phrase in Latin,
but the front end is not using that endpoint — instead it calls https://fish-text.ru

That

We have built a piece of functionality with loremipsum that we're not using;
fish-text.ru provides texts in Russian. That's ok but a project like this — an educational project for beginners in Python & cloud computing — is international. That's why we're writing all our comments, pull requests, and issues in English: thus, whoever wants from any part of the world — be it Russia, Europe, China, India, Brazil or Iceland — may come and join us in writing code.

That being said, please switch the front end to use our own random-phrase API endpoint instead of fish-text.ru.

Yes, of course, this was an intermediate option until the random_phrase endpoint appeared in the main branch. I forgot to note this flaw in the pull request. The adjustment is already in progress.


Web search prompt doesn't used, and noisy RAG

Bug Report
Description
Bug Summary:
When using the web search capability, it seemingly skips the web search prompt and simply uses the original question prompt.
Eg. if I ask "Make a Google search to tell me who's Fusseldieb", it just skips to "Searching 'Make a Google search to tell me who's Fusseldieb'...
When looking at the logs, it really does search for the whole original prompt. Seems like the prompt to transform the query into a Google search doesn't get executed, or ignored.
Also, when searching on the web, when it reads individual searches, it doesn't trim the output, which makes it very noisy, and uses A LOT of useless tokens.
See below.
Steps to Reproduce:

Enable the web search capability within the "+" icon.
Ask anything

Expected Behavior:

Pass through the query transformation prompt

Actual Behavior:

It searches the exact prompt

Environment

Open WebUI Version: 0.3.4

Operating System: Debian GNU/Linux 11 (bullseye)

Reproduction Details
Confirmation:

[x] I have read and followed all the instructions provided in the README.md.
[x] I am on the latest version of both Open WebUI and Ollama.
[x] I have included the browser console logs.
[x] I have included the Docker container logs.

Logs and Screenshots
Docker Container Logs:
INFO:root:trying to web search with ('duckduckgo', 'Search the exact term "Fusseldieb" for me')
[SearchResult(...

Screenshots (if applicable):

Installation Method
Docker
Additional Information
I think ideally this would be a pipeline, not a built-in function.

I encountered the same promble after the upgrade to 0.34. Hope this issue will be fixed soon.

@AeneasZhu that is unrelated to this issue.

You can change the prompt length threshold from admin settings!

@tjbck Thanks for answering, however that doesn't quite address the issues.
The bug in which it skips through the query prompt is, well, a bug.
And the prompt length threshold can be adjusted, but the issue is that it doesn't "clean up" endless ("\n", newlines) which may come from web searches.

The length threshold means that when your prompt word ** exceeds ** the threshold before a web search keyword is generated with the LLM instead of using your request directly, so if you want to generate web search keywords by LLM every time, you should set the threshold to 0.


loadUser does not dispatch LOADING_USER action

When the loadUser function is called , the LOADING_USER action is not dispatched.
So the state value isLoadingUser is always false.
In my application, I have something like that :
function HomePage(props) {
  const { user, isLoadingUser } = props;

  if(isLoadingUser) {
    return Loading...
  }
  if(!user || user.expired) {
    userManaper.signinRedirect(); // This redirects to the login server
                                                        // as I don't have an explicit login page
    return Loading...;
  }

  return <MainPage />;
}

function mapStateToProps(state) {
  return {
    user: state.oidc.user,
      isLoadingUser: state.oidc.isLoadingUser
  };
}

Every time the application is loaded, it redirects to the login server, as it does not have the information that the user is loading (via loadUser call).

You are correct, currently the loadUser helper is not dispatching the LOADING_USER action. I will add this to the next update.

You can check the pull request #77 I have made.
It corrects this behavior and it works on my application.

The new version (beta.13) now dispatches LOADING_USER. I hope this fixes your issue. Thanks for the report.


Update User Registration with update Org functionality for pending users

🗣 Description
Update User Registration with update Org functionality for pending users.

💭 Motivation and context
Pending users have the ability to get an org assigned before becoming a member which requires additional functionality in the User Registration Process.
CRASM-657

🧪 Testing
Registering a user after they already have an organization assigned to them is now possible.

If the pending user's org was already added and not modified, only update the user, not org.
If the pending user now has a different org than before, remove the previous org, then add the new org, and then update the user.
If the pending user had no previous org, add the user to the selected org which then also updates the user.

✅ Pre-approval checklist

[x] This PR has an informative and human-readable title.
[x] Changes are limited to a single goal - eschew scope creep!
[x] All future TODOs are captured in issues, which are referenced
in code comments.
[x] All relevant type-of-change labels have been added.
[x] I have read the CONTRIBUTING document.
[x] These code changes follow cisagov code standards.
[x] All relevant repo and/or project documentation has been updated
to reflect the changes in this PR.
[ ] Tests have been added and/or modified to cover the changes in this PR.
[ ] All new and existing tests pass.

✅ Pre-merge checklist

[ ] Revert dependencies to default branches.
[ ] Finalize version.

✅ Post-merge checklist

[ ] Create a release.

The functionality works perfectly, only if when the Regional Admin selects the same organization that was set in the pending state. It fails if the organization is changed to a different org. If this is acceptable with stakeholders I can move forward to approve. Confirming with stakeholders.

Hey @schmelz21 can you try again? I had plugged in the wrong org ID for that scenario. It should be working now.


docker.socket

Hi
I would like t edit docker.socket file and make it for a partcuilar user.
example:
[Socket]
ListenStream=/var/run/docker.sock
SocketMode=0660
SoketUser=pi
SocketGroup=docker

so SocketUser will be equal pi instead of root because I would like to add the subject in the casbin model.
but I got error message from the socket.
is there anyway to make it in the casbin ?
many thanks

Similar to: https://github.com/casbin/casbin-authz-plugin/issues/22


Implement MyriaL support for MyriaX Split operator

The Split MyriaX operator (splits string values on a regex) has been around for a while but has no support in Raco. We need to add a simple functional syntax to use it in MyriaL. (Eventually both the operator and the syntax will be superseded by a proper flatmap UDF design.)

Can you list a tiny example of what such a plan looks like? Does it assume the input is a relation of 1-arity string type?

This was superseded by SplitExpression (https://github.com/uwescience/raco/pull/537).


Bump rustc

The latest toolstate failure is already fixed (3d8bf92a11f348d8dd2183873ca60e2e4859e5b9), we should only bump rustc and update submodule, I think.
cc: rust-lang/rust#68757
r? @RalfJung

Indeed, and bumping rustc here is actually optional for that. :)  Still, good idea to do that.
@bors r+

:pushpin: Commit 121791b9af0a5d36f619e257262f8e46189c202f has been approved by RalfJung

:hourglass: Testing commit 121791b9af0a5d36f619e257262f8e46189c202f with merge ad7b1bd8367b1dc141ae23033f195ef03e3ccde1...

:sunny: Test successful - checks-travis, status-appveyor
Approved by: RalfJung
Pushing ad7b1bd8367b1dc141ae23033f195ef03e3ccde1 to master...


log on action and prob for off-policy evaluation

The main change is for the off-policy evaluator to log the action and probability of the learning model rather than that of the logged data (which is identical for all models and not very useful when trying to compare different learners).
Introduced a helper function for sampling the actions and used if in some other code placed to avoid redundancy.

I can't seem to re-run tests.
Looks like these unrelated tests should be less sensitive
======================================================================
FAIL: test_DM (coba.tests.test_environments_filters.OpeRewards_Tests)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/home/runner/work/coba/coba/coba/tests/test_environments_filters.py", line 2390, in test_DM
    self.assertAlmostEqual(new_interactions[0]['rewards'].eval('c'),.79699, places=4)
AssertionError: 0.7970473766326904 != 0.79699 within 4 places (5.7376632690453455e-05 difference)

======================================================================
FAIL: test_DM_action_not_hashable (coba.tests.test_environments_filters.OpeRewards_Tests)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/home/runner/work/coba/coba/coba/tests/test_environments_filters.py", line 2404, in test_DM_action_not_hashable
    self.assertAlmostEqual(new_interactions[0]['rewards'].eval(['c']),.79699, places=4)
AssertionError: 0.7970473766326904 != 0.79699 within 4 places (5.7376632690453455e-05 difference)

----------------------------------------------------------------------

I can't seem to re-run tests. Looks like these unrelated tests should be less sensitive
======================================================================
FAIL: test_DM (coba.tests.test_environments_filters.OpeRewards_Tests)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/home/runner/work/coba/coba/coba/tests/test_environments_filters.py", line 2390, in test_DM
    self.assertAlmostEqual(new_interactions[0]['rewards'].eval('c'),.79699, places=4)
AssertionError: 0.7970473766326904 != 0.79699 within 4 places (5.7376632690453455e-05 difference)

======================================================================
FAIL: test_DM_action_not_hashable (coba.tests.test_environments_filters.OpeRewards_Tests)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/home/runner/work/coba/coba/coba/tests/test_environments_filters.py", line 2404, in test_DM_action_not_hashable
    self.assertAlmostEqual(new_interactions[0]['rewards'].eval(['c']),.79699, places=4)
AssertionError: 0.7970473766326904 != 0.79699 within 4 places (5.7376632690453455e-05 difference)

----------------------------------------------------------------------

Totally agree. Are these the only tests you're having problems with? I've tried to bump down a lot of tests over time.


[Accessibility][Keyboard - Open]: Navigation within table is not performed using up/down arrow keys.

User Experience:
For keyboard users it is difficult to perform the task if any control does not perform its functionality.
Test Environment:
Environment: Chromium Edge (Anaheim) + Narrator
Build Version: 2004 (OS Build 19564.1005)
Microsoft Edge Version: 82.0.425.0 (Official build) canary (64-bit)
Test URL: http://localhost:3000/home
Repro Steps:

Open URL: http://localhost:3000/home
"Bot Framework Composer" homepage will gets opened.
Navigate to "Open" button and activate it.
'Select a Bot' dialog gets opened.
Navigate within the table using up/down arrow keys and observe the issue.

Actual Result:
Navigation within table is not performed using up/down arrow keys. When user press down arrow key to navigate to next row, then either the table gets refreshed & focus shifts to another control or new page gets opened.
Note:

Same issue is repro within: Save >Define conversation objective table.
Select 'Notification' from left navigation bar, when focus reach on table 1st column & press down arrow key, the new page gets open, which is incorrect and when user press 'Enter' key on error, then also nothing is happened. (Refer: Attachment: Functional_Notfication_error)
Sorting is also not performed.

Expected Result:
Navigation within table is not performed using up/down arrow keys. When user press down arrow key to navigate to next row, focus should land to next row rather than refreshing the table and new page to open.
MAS Reference:
https://microsoft.sharepoint.com/:w:/r/sites/accessibility/CELA/Official_Microsoft_Accessibility_Standards/MAS 2.1.1 – Keyboard.docx?d=w1f29acf9a3e7414fbd8d7e3598d877bb&csf=1&e=LSJeSF
Attachment:
MAS2.1.1_ Table.zip
MAS2.1.1_Notfication_error.zip

Can we also add the severity label to this issue?

Double-checked this, and this is both repro-able and highly annoying. Our FileSelector code needs some work, so I'll take this on next.

Since selecting is now a double click (thank you thank you), I think the modal will also need a 'next' button for an intuitive UX.

 I'm going to file a new one, unrelated to a11y. Thoughts?

File here: https://github.com/microsoft/BotFramework-Composer/issues/2594

As checked the issue is resolved, so closing the bug.


Mapped enum

Provides support for defining non-integer enum types.
mapped_enum Example do
  A = "foo"
  B = "bar"
  C = "baz"
end

Instances may be read from mapped values
Example["foo"] # => Example::A

Mapped values may also be extracted
Example::A.mapped_value # => "foo"

All other functionality and safety that enums provide holds.

Perhaps overriding the to_json/to_s with the mapped value would be a goer?

While that is definitely a common usage scenario, the mapped value does not need to be a String/Char, or even a type that defines a useful serialisation to String / JSON.
It does however support using a block are to specify this where required:
mapped_enum Example(String),
  A = "foo",
  B = "bar",
  C = "baz" do
  def to_s
    mapped_value
  end
end

Looks great!

Took another look this morning - pretty major refactor in d529e5e that resolved a couple of things that were bugging me.
Points to note:

removes the need for the seperate mapping class - values are placed onto an annotation (which can also be used without the macro)
provides compile time resolution from mapped values and useful errors around this
drops the type restriction for runtime resolution - equivalent objects will resolve to mapped members


Added custom llama-cpp-tokenizer

This PR solves the issue of explicitly setting the tokenizer for llama cpp model.
Work so far -
Implemented custom tokenizer class
made changes in model_registry and tokenizer to get the correct tokenizer model.
Blockers -
The VocabularyMatcher class tries to get the encoding for " ". Llama tokenizers are based on sentencepiece, " " is not tokenized in this method.
Currently investigating what VocabularyMatcher does and possibly extending it to make it compatible with sentencepiece
For issue - https://github.com/eth-sri/lmql/issues/162

Thanks a lot, this is awesome stuff. I am currently testing this and then I will proceed with merging. Is there a reason you used sentencepiece directly, and not the llama-cpp-python integrated tokenizer?

llama-cpp-python did not have a function to get tokenizer vocab, hence did not use it.
I found Sentencepiece and HF's LlamaTokenizer. HF's lib internally used sentencepice so I wanted to have one less layers of unnecessary abstraction.


Adding link to db.runCommand MongoDB documentation from $runCommandRaw section

In the section of $runCommandRaw in our documentation should we add that the object that could be passed while invoking the query should follow the syntax of db.runCommand from MongoDB Docs: https://www.mongodb.com/docs/manual/reference/command/
Right now it's not clear what are the possible parameters we could pass while invoking the $runCommandRaw query.

This should be sufficiently documented here. Feel free to reopen it if we could add any additional information. :)


Remove Rollbar error reporting

I haven't actually looked at the error reports there in years and they've shut us down god knows when:

The deployment email are still working so this is only about the error reports apparently.
Not sure if the emails add any value but this is just about removing the broken error reporting api calls for now.

I should add that our internal logging covers most of this use case, so I'm not sure if it's worth trying to get a free account. I didn't use it even when we had it after I'd set up our logging.

and here I am thinking we just had an app that never ever crashed 😇
Fine by me to shut it down. I did still use the emails as notifications of deployments, but I can switch to the Discord channel instead 👍

This actually highlighted a problem. There seem to be errors that are only reported to rollbar and not to the logs. When rollbar went away we silently lost access to those reports (which isn't that big a deal, because we never checked them).
However, our explicit tests to ensure errors are being reported rely on the rollbar reporting mechanism, giving us a false sense of security.
During my first stab at removing rollbar this became apparent when I tried to assert the errors in the logs.
It's going to be a bit of a bigger task to move this across.


Add doc to describe transaction supported status of read-write split

The proposal of read-write split is using data consistence to exchange performance improvement. Using transaction in write node only is OK, but using transaction with read and write together is not good practice.
We need to add the description to document for read-write split.
The files of document:
docs/document/content/features/read-write-split/unsupported-items.en.md
docs/document/content/features/read-write-split/unsupported-items.cn.md

Tasks are:

[ ] Add a new item for transaction supported status
[ ] Explain the reason for not support transaction cross master and slave nodes.

Link to #4443

I want try it, ths. @terrymanu
我觉得应该分两个名词，读写事务一致性和主从事务一致性；
1、读写事务一致性是从业务场景看读写是否必须同在一个事务中，再从事务隔离级别的角度来决定；
2、主从事务一致性，主从数据库事务一致性需要牺牲性能来保证同步双写才可以。

@ganjx Welcome, can we talk with English?

This's a documents Contributor Guide. https://shardingsphere.apache.org/community/en/contribute/document-contributor/

I can not find the directory you mentioned.
Should I create a new one named "incubator-shardingsphere-doc/document/content/features/read-write-split/"?
Then commit?

I can not find the directory you mentioned.
Sharding-doc git link is "https://github.com/apache/incubator-shardingsphere-doc.git", that's right ?
Should I create a new one named "incubator-shardingsphere-doc/document/content/features/read-write-split/"?
Then commit?

you can see here https://github.com/apache/incubator-shardingsphere/tree/master/docs

i want to try  add   document

Sorry,I can't understand.
Write here,then you move it to these documents?
Or I fork shardingsphere then push it?

Sorry,I can't understand.
Write here,then you move it to these documents?
Or I fork shardingsphere then push it?

yeah, you need fork shardingsphere then push it

Sorry,I can't understand.
Write here,then you move it to these documents?
Or I fork shardingsphere then push it?

this is latest  documents Contributor Guide. you can see this

@gongsiran Welcome, assigned


When trying to better isolate public and private headers, multiple group folders are created in the resulting Xcode project

I was looking towards moving away from Pods and using prebuilt libraries. As part of the process I was experimenting using xcodegen to create Xcode project files for the pods.
When pods builds, it has a method for creating umbrella headers and public headers. For the most part I've been successful at creating Xcode projects which can build each pod. However I've run into a problem with FLEX. The podspec for FLEX indicates only one public header "FLEXManager.h". All their source is placed under a "Classes" directory. I tried using this rule to make "FLEXManager.h" public.
    sources:
      - path: ../Pods/FLEX/Classes/FLEXManager.h
        headerVisibility: public
      - path: ../Pods/FLEX/Classes/
        includes:
          - "**/*.[hm]"
        excludes:
          - "FLEXManager.h"
        headerVisibility: private

The net result of this, however is it creates 2 Classes group folders.

I've also tried this variation and it seems to nest a Classes group folder underneath another.
    sources:
      - path: ../Pods/FLEX/Classes/FLEXManager.h
        headerVisibility: public
        group: Classes
      - path: ../Pods/FLEX/Classes/
        includes:
          - "**/*.[hm]"
        excludes:
          - "FLEXManager.h"
        headerVisibility: private
        group: Classes

I would expect only one Classes folder.
I've tried other variations that have resulted in one Classes folder, but in doing so, "FLEXManager.h" is treated as private.
Is there either a way of handling this properly? Or is this an issue with xcodegen?

Have you tried removing ‘group’ and using the ‘createIntermediateGroups’ flag?


Cleaned up code to fix jump link

Tugboat has finished building the preview for this pull request!
Link:

https://pr198-mhh7d77dh4gisa7mewx2jymeii5etcrj.tugboat.qa

Dashboard:

https://dashboard.tugboat.qa/61a50792de497086afebdc48


data.ocm_rosa_operator_roles.operator_roles fetching error in Windows systems

Hello,
we have observed a different behaviour when fetching operator_roles data source from Windows machines. While in Linux hosts the data source data.ocm_rosa_operator_roles successfully populates the operator_roles variables, in Windows we observe an error when calling the operator list.
terraform {
    required_version = ">= 0.12.0"
    required_providers {
    aws = {
      source  = "hashicorp/aws"
      version = ">= 4.20.0"
    }
    ocm = {
      version = ">=1.0.1"
      source  = "terraform-redhat/ocm"
    }
  }
}

provider "aws" {
	region = "eu-central-1"
	ignore_tags {
        key_prefixes = ["kubernetes.io/"]
    }
}

provider "ocm" {
  token = __REDACTED__
  url   = "https://api.openshift.com"
}

data "ocm_rosa_operator_roles" "operator_roles" {
  operator_role_prefix = "cluster-test"
}

output "operator_roles" {
    value = "${data.ocm_rosa_operator_roles.operator_roles}"
}

Debug output in Windows systems
...
provider.terraform-provider-ocm_v1.0.1.exe: 2023/06/14 16:00:15 {
2023-06-14T16:00:15.952Z [DEBUG] provider.terraform-provider-ocm_v1.0.1.exe:   "access_token": "***",
2023-06-14T16:00:15.952Z [DEBUG] provider.terraform-provider-ocm_v1.0.1.exe:   "expires_in": 900,
2023-06-14T16:00:15.952Z [DEBUG] provider.terraform-provider-ocm_v1.0.1.exe:   "refresh_expires_in": 0,
2023-06-14T16:00:15.952Z [DEBUG] provider.terraform-provider-ocm_v1.0.1.exe:   "refresh_token": "***",
2023-06-14T16:00:15.952Z [DEBUG] provider.terraform-provider-ocm_v1.0.1.exe:   "token_type": "Bearer",
2023-06-14T16:00:15.953Z [DEBUG] provider.terraform-provider-ocm_v1.0.1.exe:   "id_token": "***",
2023-06-14T16:00:15.954Z [DEBUG] provider.terraform-provider-ocm_v1.0.1.exe:   "not-before-policy": 0,
2023-06-14T16:00:15.955Z [DEBUG] provider.terraform-provider-ocm_v1.0.1.exe:   "session_state": "b1bad86b-9b22-408d-b4c3-764e5357dfd0",
2023-06-14T16:00:15.955Z [DEBUG] provider.terraform-provider-ocm_v1.0.1.exe:   "scope": "openid api.iam.service_accounts api.iam.organization offline_access"
2023-06-14T16:00:15.955Z [DEBUG] provider.terraform-provider-ocm_v1.0.1.exe: }
2023-06-14T16:00:15.955Z [DEBUG] provider.terraform-provider-ocm_v1.0.1.exe: 2023/06/14 16:00:15 Got tokens on first attempt
2023-06-14T16:00:15.955Z [DEBUG] provider.terraform-provider-ocm_v1.0.1.exe: 2023/06/14 16:00:15 Request method is GET
2023-06-14T16:00:15.955Z [DEBUG] provider.terraform-provider-ocm_v1.0.1.exe: 2023/06/14 16:00:15 Request URL is 'https://api.openshift.com/api/clusters_mgmt/v1/aws_inquiries/sts_credential_requests'
2023-06-14T16:00:15.956Z [DEBUG] provider.terraform-provider-ocm_v1.0.1.exe: 2023/06/14 16:00:15 Request header 'Accept' is 'application/json'
2023-06-14T16:00:15.956Z [DEBUG] provider.terraform-provider-ocm_v1.0.1.exe: 2023/06/14 16:00:15 Request header 'Authorization' is omitted
2023-06-14T16:00:15.956Z [DEBUG] provider.terraform-provider-ocm_v1.0.1.exe: 2023/06/14 16:00:15 Request header 'User-Agent' is 'OCM-TF/-'
2023-06-14T16:00:16.137Z [DEBUG] provider.terraform-provider-ocm_v1.0.1.exe: 2023/06/14 16:00:16 Failed to get operator list
2023-06-14T16:00:16.142Z [DEBUG] provider.stdio: received EOF, stopping recv loop: err="rpc error: code = Unavailable desc = error reading from server: EOF"
2023-06-14T16:00:16.160Z [DEBUG] provider: plugin process exited: path=.terraform/providers/registry.terraform.io/terraform-redhat/ocm/1.0.1/windows_amd64/terraform-provider-ocm_v1.0.1.exe pid=420
2023-06-14T16:00:16.160Z [DEBUG] provider: plugin exited
2023-06-14T16:00:16.161Z [DEBUG] building apply graph to check for errors
2023-06-14T16:00:16.161Z [DEBUG] ProviderTransformer: "data.ocm_rosa_operator_roles.operator_roles (expand)" (*terraform.nodeExpandApplyableResource) needs provider["registry.terraform.io/terraform-redhat/ocm"]
2023-06-14T16:00:16.161Z [DEBUG] pruning unused provider["registry.terraform.io/hashicorp/aws"]
2023-06-14T16:00:16.161Z [DEBUG] ReferenceTransformer: "data.ocm_rosa_operator_roles.operator_roles (expand)" references: []
2023-06-14T16:00:16.161Z [DEBUG] ReferenceTransformer: "output.operator_roles (expand)" references: [data.ocm_rosa_operator_roles.operator_roles (expand)]
. . .

While in Linux the operator list is retrieved correctly:
2023-06-14T18:02:23.041+0200 [DEBUG] provider.terraform-provider-ocm_v1.0.1: 2023/06/14 18:02:23 {
2023-06-14T18:02:23.041+0200 [DEBUG] provider.terraform-provider-ocm_v1.0.1:   "access_token": "***",
2023-06-14T18:02:23.041+0200 [DEBUG] provider.terraform-provider-ocm_v1.0.1:   "expires_in": 900,
2023-06-14T18:02:23.041+0200 [DEBUG] provider.terraform-provider-ocm_v1.0.1:   "refresh_expires_in": 0,
2023-06-14T18:02:23.041+0200 [DEBUG] provider.terraform-provider-ocm_v1.0.1:   "refresh_token": "***",
2023-06-14T18:02:23.041+0200 [DEBUG] provider.terraform-provider-ocm_v1.0.1:   "token_type": "Bearer",
2023-06-14T18:02:23.041+0200 [DEBUG] provider.terraform-provider-ocm_v1.0.1:   "id_token": "***",
2023-06-14T18:02:23.041+0200 [DEBUG] provider.terraform-provider-ocm_v1.0.1:   "not-before-policy": 0,
2023-06-14T18:02:23.041+0200 [DEBUG] provider.terraform-provider-ocm_v1.0.1:   "session_state": "b1bad86b-9b22-408d-b4c3-764e5357dfd0",
2023-06-14T18:02:23.041+0200 [DEBUG] provider.terraform-provider-ocm_v1.0.1:   "scope": "openid api.iam.service_accounts api.iam.organization offline_access"
2023-06-14T18:02:23.041+0200 [DEBUG] provider.terraform-provider-ocm_v1.0.1: }
2023-06-14T18:02:23.041+0200 [DEBUG] provider.terraform-provider-ocm_v1.0.1: 2023/06/14 18:02:23 Got tokens on first attempt
2023-06-14T18:02:23.041+0200 [DEBUG] provider.terraform-provider-ocm_v1.0.1: 2023/06/14 18:02:23 Request method is GET
2023-06-14T18:02:23.041+0200 [DEBUG] provider.terraform-provider-ocm_v1.0.1: 2023/06/14 18:02:23 Request URL is 'https://api.openshift.com/api/clusters_mgmt/v1/aws_inquiries/sts_credential_requests'
2023-06-14T18:02:23.041+0200 [DEBUG] provider.terraform-provider-ocm_v1.0.1: 2023/06/14 18:02:23 Request header 'Accept' is 'application/json'
2023-06-14T18:02:23.041+0200 [DEBUG] provider.terraform-provider-ocm_v1.0.1: 2023/06/14 18:02:23 Request header 'Authorization' is omitted
2023-06-14T18:02:23.041+0200 [DEBUG] provider.terraform-provider-ocm_v1.0.1: 2023/06/14 18:02:23 Request header 'User-Agent' is 'OCM-TF/-'
2023-06-14T18:02:23.417+0200 [DEBUG] provider.terraform-provider-ocm_v1.0.1: 2023/06/14 18:02:23 Response protocol is 'HTTP/2.0'
2023-06-14T18:02:23.417+0200 [DEBUG] provider.terraform-provider-ocm_v1.0.1: 2023/06/14 18:02:23 Response status is '200 OK'
2023-06-14T18:02:23.417+0200 [DEBUG] provider.terraform-provider-ocm_v1.0.1: 2023/06/14 18:02:23 Response header 'Content-Type' is 'application/json'
2023-06-14T18:02:23.417+0200 [DEBUG] provider.terraform-provider-ocm_v1.0.1: 2023/06/14 18:02:23 Response header 'Date' is 'Wed, 14 Jun 2023 16:02:23 GMT'
2023-06-14T18:02:23.417+0200 [DEBUG] provider.terraform-provider-ocm_v1.0.1: 2023/06/14 18:02:23 Response header 'Server' is 'envoy'
2023-06-14T18:02:23.417+0200 [DEBUG] provider.terraform-provider-ocm_v1.0.1: 2023/06/14 18:02:23 Response header 'Vary' is 'Accept-Encoding'
2023-06-14T18:02:23.417+0200 [DEBUG] provider.terraform-provider-ocm_v1.0.1: 2023/06/14 18:02:23 Response header 'X-Envoy-Upstream-Service-Time' is '2'
2023-06-14T18:02:23.417+0200 [DEBUG] provider.terraform-provider-ocm_v1.0.1: 2023/06/14 18:02:23 Response header 'X-Operation-Id' is '901b5da1-553d-4bc1-8972-17e6a5d9f87d'
2023-06-14T18:02:23.417+0200 [DEBUG] provider.terraform-provider-ocm_v1.0.1: 2023/06/14 18:02:23 Response body follows
2023-06-14T18:02:23.417+0200 [DEBUG] provider.terraform-provider-ocm_v1.0.1: 2023/06/14 18:02:23 {
2023-06-14T18:02:23.417+0200 [DEBUG] provider.terraform-provider-ocm_v1.0.1:   "kind": "STSCredentialRequest",
2023-06-14T18:02:23.417+0200 [DEBUG] provider.terraform-provider-ocm_v1.0.1:   "page": 1,
2023-06-14T18:02:23.417+0200 [DEBUG] provider.terraform-provider-ocm_v1.0.1:   "size": 6,
2023-06-14T18:02:23.417+0200 [DEBUG] provider.terraform-provider-ocm_v1.0.1:   "total": 6,
2023-06-14T18:02:23.418+0200 [DEBUG] provider.terraform-provider-ocm_v1.0.1:   "items": [
2023-06-14T18:02:23.418+0200 [DEBUG] provider.terraform-provider-ocm_v1.0.1:     {
2023-06-14T18:02:23.418+0200 [DEBUG] provider.terraform-provider-ocm_v1.0.1:       "kind": "STSOperator",
2023-06-14T18:02:23.418+0200 [DEBUG] provider.terraform-provider-ocm_v1.0.1:       "name": "machine_api_aws_cloud_credentials",
2023-06-14T18:02:23.418+0200 [DEBUG] provider.terraform-provider-ocm_v1.0.1:       "operator": {
2023-06-14T18:02:23.418+0200 [DEBUG] provider.terraform-provider-ocm_v1.0.1:         "name": "aws-cloud-credentials",
2023-06-14T18:02:23.418+0200 [DEBUG] provider.terraform-provider-ocm_v1.0.1:         "namespace": "openshift-machine-api",
2023-06-14T18:02:23.418+0200 [DEBUG] provider.terraform-provider-ocm_v1.0.1:         "service_accounts": [
2023-06-14T18:02:23.418+0200 [DEBUG] provider.terraform-provider-ocm_v1.0.1:           "machine-api-controllers"
2023-06-14T18:02:23.418+0200 [DEBUG] provider.terraform-provider-ocm_v1.0.1:         ],
2023-06-14T18:02:23.418+0200 [DEBUG] provider.terraform-provider-ocm_v1.0.1:         "min_version": "",
2023-06-14T18:02:23.418+0200 [DEBUG] provider.terraform-provider-ocm_v1.0.1:         "max_version": ""
2023-06-14T18:02:23.418+0200 [DEBUG] provider.terraform-provider-ocm_v1.0.1:       }
2023-06-14T18:02:23.418+0200 [DEBUG] provider.terraform-provider-ocm_v1.0.1:     },
2023-06-14T18:02:23.418+0200 [DEBUG] provider.terraform-provider-ocm_v1.0.1:     {
2023-06-14T18:02:23.418+0200 [DEBUG] provider.terraform-provider-ocm_v1.0.1:       "kind": "STSOperator",
2023-06-14T18:02:23.418+0200 [DEBUG] provider.terraform-provider-ocm_v1.0.1:       "name": "cloud_credential_operator_cloud_credential_operator_iam_ro_creds",
2023-06-14T18:02:23.418+0200 [DEBUG] provider.terraform-provider-ocm_v1.0.1:       "operator": {
2023-06-14T18:02:23.418+0200 [DEBUG] provider.terraform-provider-ocm_v1.0.1:         "name": "cloud-credential-operator-iam-ro-creds",
2023-06-14T18:02:23.418+0200 [DEBUG] provider.terraform-provider-ocm_v1.0.1:         "namespace": "openshift-cloud-credential-operator",
2023-06-14T18:02:23.418+0200 [DEBUG] provider.terraform-provider-ocm_v1.0.1:         "service_accounts": [
2023-06-14T18:02:23.418+0200 [DEBUG] provider.terraform-provider-ocm_v1.0.1:           "cloud-credential-operator"
2023-06-14T18:02:23.418+0200 [DEBUG] provider.terraform-provider-ocm_v1.0.1:         ],
2023-06-14T18:02:23.418+0200 [DEBUG] provider.terraform-provider-ocm_v1.0.1:         "min_version": "",
2023-06-14T18:02:23.418+0200 [DEBUG] provider.terraform-provider-ocm_v1.0.1:         "max_version": ""
2023-06-14T18:02:23.418+0200 [DEBUG] provider.terraform-provider-ocm_v1.0.1:       }
2023-06-14T18:02:23.418+0200 [DEBUG] provider.terraform-provider-ocm_v1.0.1:     },
2023-06-14T18:02:23.418+0200 [DEBUG] provider.terraform-provider-ocm_v1.0.1:     {
2023-06-14T18:02:23.418+0200 [DEBUG] provider.terraform-provider-ocm_v1.0.1:       "kind": "STSOperator",
2023-06-14T18:02:23.418+0200 [DEBUG] provider.terraform-provider-ocm_v1.0.1:       "name": "image_registry_installer_cloud_credentials",
2023-06-14T18:02:23.418+0200 [DEBUG] provider.terraform-provider-ocm_v1.0.1:       "operator": {
2023-06-14T18:02:23.418+0200 [DEBUG] provider.terraform-provider-ocm_v1.0.1:         "name": "installer-cloud-credentials",
2023-06-14T18:02:23.418+0200 [DEBUG] provider.terraform-provider-ocm_v1.0.1:         "namespace": "openshift-image-registry",
2023-06-14T18:02:23.418+0200 [DEBUG] provider.terraform-provider-ocm_v1.0.1:         "service_accounts": [
2023-06-14T18:02:23.418+0200 [DEBUG] provider.terraform-provider-ocm_v1.0.1:           "cluster-image-registry-operator",
2023-06-14T18:02:23.418+0200 [DEBUG] provider.terraform-provider-ocm_v1.0.1:           "registry"
2023-06-14T18:02:23.418+0200 [DEBUG] provider.terraform-provider-ocm_v1.0.1:         ],
2023-06-14T18:02:23.418+0200 [DEBUG] provider.terraform-provider-ocm_v1.0.1:         "min_version": "",
2023-06-14T18:02:23.418+0200 [DEBUG] provider.terraform-provider-ocm_v1.0.1:         "max_version": ""
2023-06-14T18:02:23.418+0200 [DEBUG] provider.terraform-provider-ocm_v1.0.1:       }
2023-06-14T18:02:23.418+0200 [DEBUG] provider.terraform-provider-ocm_v1.0.1:     },
2023-06-14T18:02:23.418+0200 [DEBUG] provider.terraform-provider-ocm_v1.0.1:     {
2023-06-14T18:02:23.418+0200 [DEBUG] provider.terraform-provider-ocm_v1.0.1:       "kind": "STSOperator",
2023-06-14T18:02:23.418+0200 [DEBUG] provider.terraform-provider-ocm_v1.0.1:       "name": "ingress_operator_cloud_credentials",
2023-06-14T18:02:23.418+0200 [DEBUG] provider.terraform-provider-ocm_v1.0.1:       "operator": {
2023-06-14T18:02:23.418+0200 [DEBUG] provider.terraform-provider-ocm_v1.0.1:         "name": "cloud-credentials",
2023-06-14T18:02:23.418+0200 [DEBUG] provider.terraform-provider-ocm_v1.0.1:         "namespace": "openshift-ingress-operator",
2023-06-14T18:02:23.418+0200 [DEBUG] provider.terraform-provider-ocm_v1.0.1:         "service_accounts": [
2023-06-14T18:02:23.418+0200 [DEBUG] provider.terraform-provider-ocm_v1.0.1:           "ingress-operator"
2023-06-14T18:02:23.418+0200 [DEBUG] provider.terraform-provider-ocm_v1.0.1:         ],
2023-06-14T18:02:23.418+0200 [DEBUG] provider.terraform-provider-ocm_v1.0.1:         "min_version": "",
2023-06-14T18:02:23.418+0200 [DEBUG] provider.terraform-provider-ocm_v1.0.1:         "max_version": ""
2023-06-14T18:02:23.418+0200 [DEBUG] provider.terraform-provider-ocm_v1.0.1:       }
2023-06-14T18:02:23.418+0200 [DEBUG] provider.terraform-provider-ocm_v1.0.1:     },
2023-06-14T18:02:23.418+0200 [DEBUG] provider.terraform-provider-ocm_v1.0.1:     {
2023-06-14T18:02:23.418+0200 [DEBUG] provider.terraform-provider-ocm_v1.0.1:       "kind": "STSOperator",
2023-06-14T18:02:23.418+0200 [DEBUG] provider.terraform-provider-ocm_v1.0.1:       "name": "cluster_csi_drivers_ebs_cloud_credentials",
2023-06-14T18:02:23.418+0200 [DEBUG] provider.terraform-provider-ocm_v1.0.1:       "operator": {
2023-06-14T18:02:23.418+0200 [DEBUG] provider.terraform-provider-ocm_v1.0.1:         "name": "ebs-cloud-credentials",
2023-06-14T18:02:23.418+0200 [DEBUG] provider.terraform-provider-ocm_v1.0.1:         "namespace": "openshift-cluster-csi-drivers",
2023-06-14T18:02:23.418+0200 [DEBUG] provider.terraform-provider-ocm_v1.0.1:         "service_accounts": [
2023-06-14T18:02:23.418+0200 [DEBUG] provider.terraform-provider-ocm_v1.0.1:           "aws-ebs-csi-driver-operator",
2023-06-14T18:02:23.418+0200 [DEBUG] provider.terraform-provider-ocm_v1.0.1:           "aws-ebs-csi-driver-controller-sa"
2023-06-14T18:02:23.418+0200 [DEBUG] provider.terraform-provider-ocm_v1.0.1:         ],
2023-06-14T18:02:23.418+0200 [DEBUG] provider.terraform-provider-ocm_v1.0.1:         "min_version": "",
2023-06-14T18:02:23.418+0200 [DEBUG] provider.terraform-provider-ocm_v1.0.1:         "max_version": ""
2023-06-14T18:02:23.418+0200 [DEBUG] provider.terraform-provider-ocm_v1.0.1:       }
2023-06-14T18:02:23.418+0200 [DEBUG] provider.terraform-provider-ocm_v1.0.1:     },
2023-06-14T18:02:23.418+0200 [DEBUG] provider.terraform-provider-ocm_v1.0.1:     {
2023-06-14T18:02:23.418+0200 [DEBUG] provider.terraform-provider-ocm_v1.0.1:       "kind": "STSOperator",
2023-06-14T18:02:23.418+0200 [DEBUG] provider.terraform-provider-ocm_v1.0.1:       "name": "cloud_network_config_controller_cloud_credentials",
2023-06-14T18:02:23.418+0200 [DEBUG] provider.terraform-provider-ocm_v1.0.1:       "operator": {
2023-06-14T18:02:23.418+0200 [DEBUG] provider.terraform-provider-ocm_v1.0.1:         "name": "cloud-credentials",
2023-06-14T18:02:23.418+0200 [DEBUG] provider.terraform-provider-ocm_v1.0.1:         "namespace": "openshift-cloud-network-config-controller",
2023-06-14T18:02:23.418+0200 [DEBUG] provider.terraform-provider-ocm_v1.0.1:         "service_accounts": [
2023-06-14T18:02:23.418+0200 [DEBUG] provider.terraform-provider-ocm_v1.0.1:           "cloud-network-config-controller"
2023-06-14T18:02:23.418+0200 [DEBUG] provider.terraform-provider-ocm_v1.0.1:         ],
2023-06-14T18:02:23.418+0200 [DEBUG] provider.terraform-provider-ocm_v1.0.1:         "min_version": "4.10",
2023-06-14T18:02:23.418+0200 [DEBUG] provider.terraform-provider-ocm_v1.0.1:         "max_version": ""
2023-06-14T18:02:23.418+0200 [DEBUG] provider.terraform-provider-ocm_v1.0.1:       }
2023-06-14T18:02:23.418+0200 [DEBUG] provider.terraform-provider-ocm_v1.0.1:     }
2023-06-14T18:02:23.418+0200 [DEBUG] provider.terraform-provider-ocm_v1.0.1:   ]
2023-06-14T18:02:23.418+0200 [DEBUG] provider.terraform-provider-ocm_v1.0.1: }

With best regards,
Abel.

@bizcochillo  Hey, going to look into this, any bits of information you can share may help me reproduce/debug.

It shouldn't matter, still I'm curious, which Windows version were you using when you hit this, 10 11 ?
What were you trying to do when you hit this, creating  account roles or something else?
Which version of OCP were you planning on installing?
Where you planning on using ROSA classic or OIDC managed or unmanaged?

As a first step, I'll try to create account roles and deploy a cluster using the latest versions of Terraform and RHCS (what was once called OCM) to see if I can reproduce issue.

OK first issue I hit while attempting to deploy a cluster (OIDC managed from Windows 10),
local folder path I'd used was too long, I'll address the issue and retry.
│ Error: Failed to download module │ │   on ..\oidc_provider\[main.tf](http://main.tf/) line 74: │   74: module "operator_roles_and_oidc_provider" { │ │ Could not download module "operator_roles_and_oidc_provider" (..\oidc_provider\main.tf:74) source code from │ "git::https://github.com/terraform-redhat/terraform-aws-rosa-sts?ref=v0.0.12": error downloading │ '[https://github.com/terraform-redhat/terraform-aws-rosa-sts?ref=v0.0.12'](https://github.com/terraform-redhat/terraform-aws-rosa-sts?ref=v0.0.12%27): C:\Program Files\Git\cmd\git.exe exited with 128: Cloning │ into '.terraform\modules\oidc_config.operator_roles_and_oidc_provider'... │ error: unable to open loose object ca95569d51db05b3d00055fe1360ad5670f41102: Filename too long │ error: unable to open loose object ca95569d51db05b3d00055fe1360ad5670f41102: Filename too long

From a Windows 10 system, successfully created account roles and deployed an OIDC managed cluster OCP 4.13.5
Using versions:
Terraform v1.5.4
on windows_amd64

provider registry.terraform.io/hashicorp/aws v4.67.0
provider registry.terraform.io/hashicorp/null v3.2.1
provider registry.terraform.io/hashicorp/random v3.5.1
provider registry.terraform.io/terraform-redhat/rhcs v1.2.2

Final install lines:
rhcs_cluster_wait.rosa_cluster: Creation complete after 28m14s
Apply complete! Resources: 2 added, 0 changed, 0 destroyed.
Outputs:
cluster_id = "25ejrtekdoi0m59qq3md0um08r213kdr"
....
$ rosa describe cluster -c ts-mw0608
Name:                       ts-mw0608
ID:                         25ejrtekdoi0m59qq3md0um08r213kdr
External ID:                2a36b35d-4493-4995-b908-628c5a5a6579
Control Plane:              Customer Hosted
OpenShift Version:
Channel Group:              stable
DNS:                        ts-mw0608.2me4.s1.devshift.org
AWS Account:                42546.......
API URL:                    https://api.ts-mw0608.2me4.....
Console URL:                https://console-openshift-console.apps.ts-mw060......
Region:                     us-east-1
Multi-AZ:                   false
Nodes:

Control plane:           3
Infra:                   2
Compute:                 2
.....
Managed Policies:           No
State:                      ready     <----- Up and running
Private:                    No
Created:                    Aug  6 2023 12:03:03 UTC
Details Page:               https://qaprodauth.console.redhat.c.....
OIDC Endpoint URL:          https://d3gt1gce2zmg3d.cloudf....... (Managed)

Hi @tshefi, thank you for your feedback.
We hit this in two Windows 10 machines and we wanted to install a 4.12.x STS ROSA cluster. We experience this when we were investigating a terraform based approach, just a couple of weeks before the renaming from terraform-redhat/ocm to terraform-redhat/rhcs (version 1.0.4, maybe).
As per the logs provided in my first message, it seems to be some kind of failure by handling the https://api.openshift.com/api/clusters_mgmt/v1/aws_inquiries/sts_credential_requests response, probably by the underlying AWS SDK, but obviously I had no more information.
I don't have those machines by now, but doing the exactly same steps from a fresh windows installation reproduced the error then. I will go through it again and will provide feedback.
With best regards

Hi @bizcochillo
Thanks for the update, waiting to hear from you.
Shall the need arise I can retry again this time a 4.12.x classic STS cluster on api.openshift.com.

@bizcochillo  and @tshefi
Thank you for bringing and checking this issue
I'm closing this issue as it old one
Feel free to reopen this in case the issue gets reproduced again


fix title in reset and payment mails

Codecov Report

Merging #60 (b6bb3ba) into master (232f1cd) will increase coverage by 0.00%.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##           master      #60   +/-   ##
=======================================
  Coverage   84.29%   84.29%
=======================================
  Files          66       66
  Lines        4329     4331    +2
=======================================
+ Hits         3649     3651    +2
  Misses        680      680

Flag
Coverage Δ

unittests
84.29% <100.00%> (+<0.01%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

base/signals.py
97.82% <100.00%> (+0.09%)
:arrow_up:

Continue to review full report at Codecov.

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


added test_03_authn_request.py

Ok nice one @francescatronconi
the title of this OPR would be
feat: a short description of the feature introduced by this PR
then
a short message that tells to readers what's going on

I resolved the conflicts, Remember to do a pull before continue


I'm having an issue with the Meetup API... Blocked from Azure

My call to the API from Azure started failing yesterday.  The error message Azure shows me is "The underlying connection was closed: An unexpected error occurred on a send. ---> System.IO.IOException: Authentication failed because the remote party has closed the transport stream."
Did my service violate part of the meetup API agreement?  Has it been blocked from the Azure URL?  I can call my API from the meetup.api console.
I am calling https://api.meetup.com/self/calendar?photo-host=public&page=30 and including my sig_id and sig.

I believe I resolved my own problem.  The supported version of TLS, either at Azure or Meetup may have changed.  I added the following line of code to my azure function (C# .Net) and it works again:
SecurityProtocolType.Tls | SecurityProtocolType.Tls11 | SecurityProtocolType.Tls12

PROBLEM
I was getting the same "Authentication failed because the remote party has closed the transport stream." when calling azure function API
SOLUTION
After changing my client target framework version from 4.5.2 to 4.6 I was able to do away with the issue


[AUTOMATIC] Release/1.3.3+13.11.0

This is an automatic release.
RevenueCat SDK
📦 Dependency Updates

[AUTOMATIC BUMP] Updates purchases-hybrid-common to 13.11.0 (#267) via RevenueCat Git Bot (@RCGitBot)

iOS 5.10.0
iOS 5.9.0

[AUTOMATIC BUMP] Updates purchases-hybrid-common to 13.10.0 (#266) via RevenueCat Git Bot (@RCGitBot)

iOS 5.10.0
iOS 5.9.0

Closing since we are making a new PHC bump


Provide AWS simulation FPGAPlatform

Using the AWS C library that interfaces with XSIM through Vivado DPI,
it's possible to create an FPGAPlatform that uses this library.
We can then write applications on top of this library once, for both simulation and run time.

merging this issue into #108