slate adapter is required

plugin-form-builder version: 1.0.15
payload version: 2.2.1
When I install my dependencies in payload project I have the following error:
Error: Cannot find module 'slate'
Require stack:
<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>-/src/plugin/formBuilder.ts
-/src/payload.config.ts
-/node_modules/payload/dist/config/load.js
-/node_modules/payload/dist/payload.js
-/node_modules/payload/dist/initHTTP.js
-/node_modules/payload/dist/index.js
-/src/server.ts
    at Function.Module._resolveFilename (node:internal/modules/cjs/loader:1077:15)
    at Function.Module._resolveFilename.sharedData.moduleResolveFilenameHook.installedValue [as _resolveFilename] (/node_modules/@cspotcode/source-map-support/source-map-support.js:811:30)
    at Function.Module._load (node:internal/modules/cjs/loader:922:27)
    at Module.require (node:internal/modules/cjs/loader:1143:19)
    at require (node:internal/modules/cjs/helpers:110:18)
    at Object.<anonymous> (/node_modules/@payloadcms/plugin-form-builder/src/utilities/serializeRichText.ts:2:1)
    at Module._compile (node:internal/modules/cjs/loader:1256:14)
    at Module._extensions..js (node:internal/modules/cjs/loader:1310:10)
    at Object.require.extensions.<computed> [as .js] (/node_modules/ts-node/src/index.ts:1608:43)
    at Module.load (node:internal/modules/cjs/loader:1119:32) {
  code: 'MODULE_NOT_FOUND',
  requireStack: [
<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>    '/src/plugin/formBuilder.ts',
    '/src/payload.config.ts',
    '/node_modules/payload/dist/config/load.js',
    '/node_modules/payload/dist/payload.js',
    '/node_modules/payload/dist/initHTTP.js',
    '/node_modules/payload/dist/index.js',
    '/src/server.ts'
  ]
}
[nodemon] app crashed - waiting for file changes before starting...

If I install slate ("@payloadcms/richtext-slate": "1.2.0") the error is resolved but I don't use it.
Maybe is up to the new version of payload? Can you check please?

@matteo-naif This package has moved to the monorepo. Issue moved to here https://github.com/payloadcms/payload/issues/4299

Thanks for the report. Looks like slate is in fact used in the serializer. We'll either need to update that or add slate as a peer dep.

@denolfe might need to resolve it. Sending emails fail and the confirmation message doesn't remove the the curly brackets.
I get this error when using the lexical editor in the CMS
err: { "type": "TypeError", "message": "children.map is not a function", "stack": TypeError: children.map is not a function at serialize (node_modules/@payloadcms/plugin-form-builder/src/utilities/serializeRichText.ts:17:7) at /node_modules/@payloadcms/plugin-form-builder/src/collections/FormSubmissions/hooks/sendEmail.ts:54:40 at Array.map (<anonymous>) at node_modules/@payloadcms/plugin-form-builder/src/collections/FormSubmissions/hooks/sendEmail.ts:29:60 at step (/node_modules/@payloadcms/plugin-form-builder/dist/collections/FormSubmissions/hooks/sendEmail.js:33:23) at Object.next (/node_modules/@payloadcms/plugin-form-builder/dist/collections/FormSubmissions/hooks/sendEmail.js:14:53) at fulfilled (node_modules/@payloadcms/plugin-form-builder/dist/collections/FormSubmissions/hooks/sendEmail.js:5:58) at processTicksAndRejections (node:internal/process/task_queues:95:5) }

Could you force the plugin to use the slate editor? eg like this
  {             type: 'richText',             name: 'message',             label: 'Message',             localized: true,             admin: {               description: 'Enter the message that should be sent in this email.',             },             editor: slateEditor({})           },


Handle concurrent downloads of the same key

@yarikoptic Question: Can I rely on s3invsync only being run on filesystems where file locking works?

oh. I wish I knew even for immediate case -- IIRC it is ZFS but either it is interfaced via nfs with some fancy options -- I don't know.  @satra might know more.  But why do we need locking though?  IIRC so far I think I didn't see a need.

@yarikoptic Some form of locking (either internal or using the filesystem) is needed for synchronizing concurrent downloads of the same key and preventing such downloads from stepping on each other.


Yubico local auth

Motivation for this change
Provide a configuration option to use local challenge response authentication with a yubico YubiKey
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nix-review --run "nix-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

Notify maintainers
cc @dtzWill

Looks good! I haven't confirmed it works, but it doesn't look like it'd regress for the non-local case anyway :).
Thanks!
By the way, do you know a reason to prefer using yubico-pam locally vs pam_u2f ? Not being sure of the trade-offs is at least partially why local wasn't supported earlier. It's a good change regardless, IMO :).
FWIW I've been using pam_u2f built against libfido2, I was hoping the software involved would cuta  release before sending upstream.... xD.
Anyway looks good, let me know if you have thoughts about how they compare but that's not important ;).


r_a_j_a_v.py

What is rajav? And what can your code actually implement instead of just the variable's name change?

And by the way. There's an error at line 32. You've mistaken the comma.

hi friend, how can i  use with proxy  i dont know. instagram.py username /proxylist/passlist -m 2 like that or can you write to me right pls


ALMA output is vastly different from other charting software

Which version are you running? The lastest version is on Github. Pip is for major releases.
0.3.14b0
Describe the bug
Current implementation of ALMA produces vastly different results than built-in alma indicator on TradingView.
To Reproduce
# 1. read price data into df
...

# 2. add alma
    df['alma'] = ta.alma(df['close'], 50)

#3. plot result
...

#4. Visually inspect the chart and compare with few other implementations of alma
(TradingView, SierraCharts, Ninjatrader, etc)

Expected behavior
I expect for plotted output of alma indicator to match alma plots of other charting software.
Screenshots

black line is the current implementation of ALMA (50);
red line is what I believe to be the correct ALMA (50);

Same chart on TradingView platform:

Additional context
The reason why I believe other implementations to be correct is because I found the difference between current implementation and the original one provided by authors. After fixing it alma works as expected.

Hello @UncleVasya,
Yeah. Not only is it a correlation issue with other libraries and platforms, it also has a performance issue that I am trying to fix. Thanks for the PR #374 and contribution. 😎
Kind Regards,
KJ

Hey @UncleVasya,
I have an update alma on the development branch if you want to test it out first. It should be quicker also.
$ pip install -U git+https://github.com/twopirllc/pandas-ta.git@development

Thanks,
KJ

I tested your version. It is both correct and amazingly fast. Nice one!
Compared it with another version on 50k candles:
def a():
    df['talma'] = alma(df['close'], 150)

def a1():
    df['a1'] = ta.alma(df['close'], 150)

import timeit

ic(timeit.timeit(stmt=a, number=5))
ic(timeit.timeit(stmt=a1, number=5))

timeit.timeit(stmt=a, number=5):<PHONE_NUMBER>2399993
timeit.timeit(stmt=a1, number=5): 0.29279039500011095

This now must be the best open source implementation of alma out there.

@UncleVasya,

I tested your version. It is both correct and amazingly fast. Nice one!
This now must be the best open source implementation of alma out there.

Thanks! It is definitely faster. It is only slightly off from TradingView's but still greater than 99% correlated with it.
KJ

@twopirllc this sounds like a to-be-closed issue?

@pssolanki111,
I'll close it when I update the main branch as well as other Issues in the similar state.
KJ


How to run

java version "1.8.0_66"
Java(TM) SE Runtime Environment (build 1.8.0_66-b18)
Java HotSpot(TM) 64-Bit Server VM (build 25.66-b18, mixed mode)
Following command "java -jar mxgraph-core.jar" does not lounch app
Could you help?

See https://github.com/jgraph/svg2xml/


Cannot broadcast

When I try to broadcast, I get this message:
secret_sdk.exceptions.LCDResponseError: Status 400 - this transaction cannot be broadcasted via legacy REST endpoints, because it does not support Amino serialization. Please either use CLI, gRPC, gRPC-gateway, or directly query the Tendermint RPC endpoint to broadcast this transaction. The new REST endpoint (via gRPC-gateway) is POST /cosmos/tx/v1beta1/txs. Please also see the REST endpoints migration guide at https://docs.cosmos.network/master/migrations/rest.html for more info
Then I've updated /txs endpoint  as /secret/tx/v1beta1/txs. This time I got 501 since the format of message also changed.
So, forking didn't work. I think it will require more work than I think :) Will you update SDK soon? Is there any ETA?
Thanks.

What type of transaction are you trying to make?

This is most likely an error in the message payload of your tx, could you give more details on what you're trying to broadcast ?

While smart contract execution:
MsgExecuteContract(
    "ADDRESS",
    "TOKEN_CONTRACT",
    {
      "send": {
        "contract": "PAIR_CONTRACT",
        "amount": str(round(1 * 1000000)),
        "msg": str(base64.b64encode(('{
          "swap": {
            "belief_price": "1",
            "max_spread": "0.005",
            "to": "",
          }
        }').encode()), "utf-8")
      }
    }
)

As I wrote in Telegram group, the problem is about the wrong endpoint, the wrong message content, and some issues I didn't know.
Wrong endpoint:  /txs --> /secret/tx/v1beta1/txs
Wrong content: "tx" --> "tx_bytes", mode: block --> "BROADCAST_MODE_BLOCK"
I've updated _broadcast() method in https://github.com/secretanalytics/secret-sdk-python/blob/main/secret_sdk/client/lcd/api/tx.py according to what I wrote above. I'm getting a 501 error without any message.
As a quick solution, if I replace all endpoints of the latest https://github.com/terra-money/terra.py (in which these issues are fixed) with Secret's ones, would it work? Is it worth trying?

I've found the issue. What I wrote above is incorrect. I still couldn't complete the whole process since tx is failed to execute but at least my tx is added to the block successfully.
While I was searching for an easy solution to this, I saw the solution in https://githubmemory.com/@tjpeterson94. I'm not sure whether the problem is the same but it has sparked an idea in my mind.
Following the example in https://github.com/secretanalytics/secret-sdk-python/blob/main/docs/guides/smart_contracts.rst, I was using these lines:
execute_tx = test1.create_and_sign_tx(
    msgs=[execute], fee=StdFee(1000000, Coins(uscrt=1000000))
)

execute_tx_result = secret.tx.broadcast(execute_tx)

and I got the message in my first post.
Now, instead, I use the line below and my tx is broadcasted successfully:
execute_tx = wallet.execute_tx(msg)


Ceiling is too high "Borehole pump"

I can't seem to use the Borehole pump in any of my factory buildings. I get the error "Borehole pump can't be built on this surface. The ceiling is too high" whenever i try to place it either on my factory floor or outside. We do use the Team Starts for Multiplayer mod which puts us on non-vanilla planets. I have not tried to fly over to a vanilla planet to try this but I would assume it would work since I have not seen any issues reported with the borehole pump not working. Currently I am trying to do this on Valcanus from Team Starts and it does not work.

Thanks for the report. I don't have motivation to fix this issue. Feel free to submit a PR.


Question - Is it possible to migrate the data in PersistedGrants table to keep the existing user session active?

We are in the middle of an infrastructure change where we are upgrading to IdentityServer4 and moving to a CICD pipeline with a new database. With this change, we would like to migrate the data in PersistedGrants table from the old environment to the new environment so that users do not get logged out and keep their existing session. So my question is

Is it possible to do what we are trying to migrate the data in PersistedGrants table?
If yes, what is the best way to do that? We already tested this in our test env and we were not able to keep the existing user sessions by just migrating the data over
If no, is there a way to keep the user sessions active in a situation like ours?

We don't provide anything built in for that in the OSS. You could possibly contact us for consulting to provide it as a paid project.


Prepare analyzer 3.2.0 release.

[ ]<EMAIL_ADDRESS>

(approved except for builds breaking...)

Assume this is because npm run nuke updated TypeScript to 3.2.1 from 3.1.6?

Fix typings or pin TS back to 3.1.6?

I can fix the typings.

I can fix the typings.

I think I fixed the typings. Not very proud of the fixes, they seem worse in every case.

I don't think the changes are all that bad.
The ones in the tests are to be expected because of the way .args is going to be ambiguous.  I do agree that adding as any into the code at places feels bad, but I think that's often more a matter of some limitations in the typings we're getting for libraries like with sinon etc.
Anyways lgtm


Binder: Error loading tiagoantao/biopython-notebook/master!

The method of dealing with Binder in this repository is overly complex and not supported. (Dockerfiles are only to be used if all other approaches fail.) Until that is fixed, you can use the link below to run the notebooks in a Binder session that works:
Direct launch a session with biopython notebooks from tiagoantao/biopython-notebook/
Explanation of why that works as a work-around:
My repository here still launches a Binder session with  Biopython installed.  nbgitpuller can be used to pull content from one repository into an environment sourced from another repository. So the above link uses nbgitpuller to launch a session with my working environment specifications that includes biopython and then pulls content from tiagoantao/biopython-notebook/  . So you can use the latest posting of the notebooks still along with CURRENT biopython.

PR applied, closing


Fix issue with entering busy state from pre-suspend hook

Since the pre suspend hook could do anything, we should support possibly entering and exiting a busy state.
The previous version entered a Delayed state immediately.
The sequence of events is:

Suspend signal handler -> sets state to delayed immediately.
pre suspend hook is called
enter busy state (rare, but happens)
exit busy state -> suspend because it thinks we are leaving a delayed suspend
Collection is done, state goes back to None
Now do the rest of the signal handler, assert that state is signaled, but now it's None

I wanted to make a test for this by overriding the pre suspend hook. But sdc does not allow redefining in the local module (not a weak symbol).
The proposed test is the following, to store for later addition if we can figure out how to run it.
//T compiles:yes
//T has-passed:yes
//T retval:0
// GC enterbusystate from presuspend hook

import core.stdc.pthread;
import d.sync.atomic;
                import sys.posix.sched;

// Override sdc's hook.
extern(C) __sd_gc_pre_suspend_hook(void* stackTop) { // sdc doesn't like this redefinition.
        import d.gc.tcache;
        threadCache.state.enterBusyState();
        threadCache.state.exitBusyState();
}

extern(C) void __sd_gc_collect();

void* runThread(void* flagdata) {
        auto flag = cast(shared Atomic!(uint) *)flagdata;
        while((*flag).load() != 1) {
                sched_yield();
        }
        return null;
}

void main() {
        pthread_t tid;
        shared Atomic!uint flag;
        pthread_create(&tid, null, runThread, cast(void*)&flag);
        __sd_gc_collect();
        flag.store(1);
        void* ret;
        pthread_join(tid, &ret);
}

Merged as a081eaed


Clarified remarks on setting InnerHandler

@alfredmyers,
Thanks for having already signed the Contribution License Agreement. Your agreement was validated by .NET Foundation. We will now review your pull request.
Thanks,
.NET Foundation Pull Request Bot

Thanks for making the additional changes, @alfredmyers. We'll merge as soon as the build completes.

Build finished but status wasn't updated. Trying again.

@alfredmyers,
Thanks for having already signed the Contribution License Agreement. Your agreement was validated by .NET Foundation. We will now review your pull request.
Thanks,
.NET Foundation Pull Request Bot


Introduce MS.Term.Core.Color to replace W.U.Color for Core/Control/TSM

This pull request introduces Microsoft.Terminal.Core.Color as an
alternative to both Windows.UI.Color and uint32_t/COLORREF in the
TerminalCore, ...Control, ...SettingsModel and ...SettingsEditor layers.
M.T.C.Color is trivially convertible to/from til::color and therefore
to/from COLORREF, W.U.Color, and any other color representation we might
need².
I've replaced almost every use of W.U.Color and uint32_t-as-color in the
above layers, with minor exception¹.
The need for this work is twofold.
First: We cannot bear a dependency from TerminalCore (which should,
on paper, be Windows 7 compatible) on Windows.UI or any other WinRT
namespace.
This work removes one big dependency on Windows.UI, but it does not go
all the way.
Second: TerminalCore chose to communicate mostly in packed uint32s
(COLORREF), which was inherently lossy and dangerous.
¹ The UI layers (TerminalControl, TerminalApp) still use
Windows.UI.Color as they are intimately connected to the UWP XAML UI.
² In the future, we might even be able to use the alpha channel...
PR Checklist

[x] I ran into the need for this when I introduced cursor inversion
[X] Fixes a longstanding itch

Validation Steps Performed
Built and ran all tests for the impacted layers, even the local ones!

Mike says "[oh] it's a projected type for til::color"


Update typeof-operator.md

per https://github.com/dotnet/vblang/issues/277#issuecomment-487963026

@KathleenDollard Can you double check this? Thanks!

Looks good


Added ability to configure navigation orientation for SPPageController.

Goal

Added ability to configure navigation orientation for SPPageController, I added a parameter name navigationOrientation of type SPPageControllerNavigationOrientation, please note that it is an optional parameter, the default value is horizontal.
Checklist

[x] Testing in compability platforms
[x] Installed correct via Swift Package Manager and Cocoapods

Interesting idea. Did you test it well?

New version released.


Dev

Codecov Report

Merging #38 (083a748) into main (85459ae) will increase coverage by 0.89%.
The diff coverage is 95.74%.

@@            Coverage Diff             @@
##             main      #38      +/-   ##
==========================================
+ Coverage   87.32%   88.21%   +0.89%
==========================================
  Files           7        7
  Lines         284      331      +47
  Branches       83      105      +22
==========================================
+ Hits          248      292      +44
- Misses         25       28       +3
  Partials       11       11

Flag
Coverage Δ

client
88.21% <95.74%> (+0.89%)
:arrow_up:

generator
88.21% <95.74%> (+0.89%)
:arrow_up:

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

Impacted Files
Coverage Δ

packages/client/src/helpers/makeWhere.ts
73.13% <93.02%> (+5.82%)
:arrow_up:

packages/client/src/helpers/makeHooks.ts
97.24% <97.14%> (-0.23%)
:arrow_down:

packages/client/src/helpers/makeFetcher.ts
100.00% <100.00%> (ø)

packages/client/src/helpers/makeSelect.ts
100.00% <100.00%> (ø)

packages/generator/src/utils/writeFiles.ts
100.00% <100.00%> (ø)

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 b682f89...083a748. Read the comment docs.


Feature Request: Take Down This Socialist Free ETC Branded Marketing BS

What’s missing?
Well, it seems that honor and integrity appear to be missing among trusted third party developers seeking "official" ETC Branded marketing to sell / promote / bring awareness or anyone of the responsibilities a community manager, marketer, communications manager, or content manager should be doing for the specific project. This seeming entitlement for free marketing efforts on behalf of an public, open source project  has begun to overflow. PR and Marketing efforts solely relies on which project is seeking such services.  Its not anyone but the project's developers, contributors, or volunteers to do the work.

Why?
I can't believe I really have to explain why. Because for god sake it invites trusted third parties into privileged areas not meant for their marketing, tweeting, blog posting, or use of any necessary platform let alone an ETC branded platform which is disgusting and disingenuous. It also invites unnecessary liability onto a project that praises itself on being trust minimized.  I run my own independent social media on my own dime still for so many reasons but for christ's sake the main one to remain trust minimized. Who's idea was this?

Egregious entitlement for free marketing services on behalf of trusted third parties done so by and on ETC branded platforms and communication channels. I'm facing a lack of integrity for the platform these trusted third party devs and projects are built on, inviting unnecessary potential scams and security holes onto the officially branded website!
Alternatives you tried
Doing it myself, successfully creating my own accounts, using actual plans, data, and tools not winging my marketing, adding potential security risks, misleading end users! I've had incredible success regarding doing this on my own measured with the KPIs that matter. Not amount of followers.
Christ, Look at Donald.  And it is completely unprofessional looking, off-strategy, appears to have no sense of plan or direction besides look at this project, oh and did you notice its displayed on a platform called ETC_Network. Completely misleading and disingenuous imo. Not to  mention this likely breaks several of Twitter's own term's and policies.... specifically hmmmm account / platform manipulation!

 Do it yourself or pay someone to do it for your private project. For fucks sake need I say more about Donald, Etherplan, Tokenhash, immmutable samourai, etclogic and all the successful KPIs he's driven to this project on his own dime and own time? Show this project some respect and stop using any ETC branded asset for your project's sake. This makes me utterly sick to my stomach.  Wouldn't that be a great idea.

I'll fight till the bitter end to protect this project. It's one of two out of 5,000 that are not scams.

Hey Kevin, There is a current issue discussing what rules to adhere for twitter together. Your thoughts and constructive feedback are welcome.
https://github.com/ethereumclassic/twitter-together/issues/15

The input you bring is really valuable because I share the same sentiment, although the intention wasn't like how it shows. So to avoid the miscommunication we first need better rules. I totally agree the way it works today is not the way forward.
That being said, there's no official in ETC so that closing point is invalid. Great to have you back and with passion!
Also the fact that there are 3rd party websites on the internet that shows which apps are active on ETC could make the app section on the .org website obsolete and relay any form of responsibility. That way the website could focus more on other important topics.

@developerkevin please could you give some examples of the content you find questionable?
Thanks!

https://twitter.com/eth_classic/status/1573045351744872448#m
https://twitter.com/eth_classic/status/1519257798491615232#m
https://twitter.com/eth_classic/status/1519219762550624256#m

Also please don't pin issues like this unilaterally if this is your first contribution.

You might have missed this disclaimer in Discord, so I posted it in github. Apologies for not also posting in the repo on the 17th as well. @IstoraMandiri decided to work the kinks out in the open.
https://github.com/ethereumclassic/twitter-together/issues/70
I believe we've talked about running a tweepy script and purging all history on this account and it likely makes sense to do so once the initialization is complete. Currently there are many centralized needs while @IstoraMandiri figures out how to decentralize processes.

I'll fight till the bitter end to protect this project. It's one of two out of 5,000 shitcoin projects that are not scams.

Oi! Eu estou lendo! I'm reading and I'll answer you!

I'll fight till the bitter end to protect this project. It's one of two out of 5,000 shitcoin projects that are not scams.

Oi! Eu estou lendo! I'm reading and I'll answer you!

What’s missing?
Well, it seems that honor and integrity appear to be missing among trusted
third party developers seeking "official" ETC Branded marketing to sell /
promote / bring awareness or anyone of the responsibilities a community
manager, marketer, communications manager, or content manager should be
doing for the specific project. This seeming entitlement for free marketing
efforts on behalf of an public, open source project has begun to overflow.
PR and Marketing efforts solely relies on which project is seeking such
services.  Its
not anyone but the project's developers, contributors, or volunteers to do
the work.

Why?
I can't believe I really have to explain why. Because for god sake it
invites trusted third parties into privileged areas not meant for their
marketing, tweeting, blog posting, or use of any necessary platform let
alone an ETC branded platform which is disgusting and disingenuous. It also
invites unnecessary liability onto a project that praises itself on being
trust minimized.  I run my own independent
social media on my own dime still for so many reasons but for christ's sake
the main one to remain trust minimized. Who's idea was this?
Egregious entitlement for free marketing services on behalf of trusted
third parties done so by and on ETC branded platforms and communication
channels. I'm facing a lack of integrity for the platform these trusted
third party devs and projects are built on, inviting unnecessary potential
scams and security holes onto the officially branded website!
Alternatives you tried
Doing it myself, successfully creating my own accounts, using actual plans,
data, and tools not winging my marketing, adding potential security risks,
misleading end users! I've had incredible success regarding doing this on
my own measured with the KPIs that matter. Not amount of followers.
Christ, Look at Donald.  And
it is completely unprofessional looking, off-strategy, appears to have no
sense of plan or direction besides look at this project, oh and did you
notice its displayed on a platform called ETC_Network. Completely
misleading and disingenuous imo. Not to mention this likely breaks several
of Twitter's own term's and policies.... specifically hmmmm account /
platform manipulation!
 Do it yourself or pay someone to do it for your private
project. For fucks sake need I say more about Donald, Etherplan, Tokenhash,
immmutable samourai, etclogic and all the successful KPIs he's driven to
this project on his own dime and own time? Show this project some respect
and stop using any ETC branded asset for your project's sake. This makes me
utterly sick to my stomach.  Wouldn't that be a great idea.
Em dom., 25 de set. de 2022 12:00, @classic_kevin @.***>
escreveu:

I'll fight till the bitter end to protect this project. It's one of two
out of 5,000 that are not scams.
—
Reply to this email directly, view it on GitHub
https://github.com/ethereumclassic/twitter-together/issues/68#issuecomment-1257223641,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/APISOBWGSGNQ44GH25XLE7TWABZJFANCNFSM6AAAAAAQVES64I
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

Thanks for sharing your experience and analysis. I really came from a trajectory where everything is very serious. Very serious. But people are educated from childhood to futility. I'm very happy that you guys created an element that I was prevented from creating. Here, in creating something serious for the world, I was called crazy. They really tried to get me in. I won judges and defense. But only They left me free. My innovation budget got stuck in the city I was born in.  When you can, please pay attention to the BOMS patent. We can amplify invention collectively. If you want. I do not speak English. But my son is your neighbor. He is studying an MBA at Harvard in California. I want to present to you 7 procedures that meet Brazilian compliance to feed the world. But at the same time it is a modal guide to create Biocapitalism with art! And now, with you! Blockchain and cryptocurrency. It's in the pre-export requirement. Exporting ideas.It is in the environmental requirement of the pre-analysis. It is in the requirement of Art, when it is visionary.But it's not that simple. By doing the biosync, from the market, with art, a series of enemies rise against it. Authorities addicted to corruption and etc.So... It's a secret project! Anyway. I need a Github in Portuguese. And I promise I'm already studying programming.
Isadora Solon autora de BOMS
Wats<PHONE_NUMBER>0
Ricardo, meu filho, +1<PHONE_NUMBER>

th

Also please don't pin issues like this unilaterally if this is your first contribution.

yes dear leader.


[Bug]: Checkmarks are out of circle in callout on mobile

Checklist

[X] I updated to the latest version of the theme (Settings → Appearance → Check for updates).
[X] I made sure that the issue is related to this theme by checking that the problem does not occur with the default theme.
[X] In case I am missing an UI element, I have checked that it cannot be re-enabled with the Style Settings plugin.
[X] This issue concerns the theme in general and is not related to a specific plugin, for which there is the plugin-support form.

Bug Description
On mobile checkmarks are out of checkbox’s circle if checkbox is in callout
Relevant Screenshot

To Reproduce

Open any note
Create callout
Add checkbox
Check checkbox

Sample Text
No response
Obsidian Version
1.5.12
Installer Version
1.5.12
In which mode(s) does the problem occur? (if applicable)

[X] Source (Edit)
[X] Reading (Preview)
[X] Live Preview

Which operating system?

[ ] macOS
[ ] Linux
[ ] Windows
[X] iOS
[ ] Android

see https://github.com/chrisgrieser/shimmering-focus/issues/303#issuecomment-2085272112


⚠ Bofrost.be has degraded performance

In b3b6918, Bofrost.be (https://www.bofrost.be) experienced degraded performance:

HTTP code: 200
Response time: 2195 ms

Resolved: Bofrost.be performance has improved in b8dcf29.


Kubernetes 1.11 drops support for custom fields in 'metadata'

https://github.com/kubernetes/kubernetes/blob/master/CHANGELOG-1.11.md#sig-api-machinery-1
This means that when Releases are created, they get their .metadata.environment stripped out. This causes the Application controller to go into a spin-loop of madly creating new Releases.
Discovered while testing K8s 1.12.
To fix this, we need to store the Release Environment somewhere else. Likely in .spec.

On reflection, this is a sensible change anyways: we can consider Releases a bit like Pods: they have an extensive .spec, but most of it is immutable after creation. This makes things a bit more intuitive for people creating raw Releases (if they don't want the Application level automation).
Unfortunately this migration is going to be fairly hairy. Likely something like:

Stop Shipper (old version)
Remove all the ownerRefs from any *Target objects to a Release
Download all Releases in the cluster
Mutate them to move .environment from .metadata to .spec (also clear up UUIDs, other K8s fields that will prevent re-creation)
Reapply them to the cluster.
Re-apply ownerRefs to *Target objects
Start Shipper (new version)


[PDI-17117]-"Text file input" step picks up the last file in order when supplies with 2 files of same names

-fixed

Build Completed
:fire: This pull request has some issues. It would be preferable to fix them in order for it to be just perfect. See below for more details. Some links are also available below for further assistance in addressing those issues.
Build Commands
mvn -B -fn -f 'pom.xml' -pl 'engine' -P '!assemblies' -Dsurefire.runOrder=alphabetical -Daudit -amd clean install

Cleanup Commands
mvn -B -f 'pom.xml' -pl 'engine' -P '!assemblies' -amd build-helper:remove-project-artifact

Changed files
  engine/src/main/java/org/pentaho/di/trans/steps/file/BaseFileInputStep.java
  engine/src/main/java/org/pentaho/di/trans/steps/file/BaseFileInputStepData.java

Unit Test Coverage
These statistics help you identify how your changes have affected the coverage of the following files. If a file is not in this list, then its coverage was not affected by your changes. To get some help interpreting these metrics, please refer to Jacoco's documentation.

:warning: Coverage Changes (click to expand)
org.pentaho.di.job.entries.evaluatetablecontent.JobEntryEvalTableContent

Branch Change: -1.1% :small_red_triangle_down:
Complexity Change: -1.1% :small_red_triangle_down:
Instruction Change: -0.1% :small_red_triangle_down:

org.pentaho.di.trans.steps.calculator.CalculatorMetaFunction

Branch Change: -8.7% :small_red_triangle_down:
Complexity Change: -3% :small_red_triangle_down:
Instruction Change: -0.7% :small_red_triangle_down:
Line Change: -0.9% :small_red_triangle_down:

org.pentaho.di.trans.steps.constant.ConstantMeta

Instruction Change: -0.1% :small_red_triangle_down:

org.pentaho.di.trans.steps.datagrid.DataGridMeta

Branch Change: -2% :small_red_triangle_down:
Complexity Change: -1.7% :small_red_triangle_down:
Instruction Change: -0.2% :small_red_triangle_down:

org.pentaho.di.trans.steps.dimensionlookup.DimensionLookupMeta

Method Change: -1% :small_red_triangle_down:

org.pentaho.di.trans.steps.file.BaseFileInputStep

Branch Change: -0.9% :small_red_triangle_down:
Complexity Change: -0.6% :small_red_triangle_down:
Instruction Change: -2.7% :small_red_triangle_down:
Line Change: -1.3% :small_red_triangle_down:

org.pentaho.di.trans.steps.groupby.GroupByMeta

Branch Change: -2.1% :small_red_triangle_down:
Complexity Change: -2.1% :small_red_triangle_down:

org.pentaho.di.trans.steps.sort.SortRowsMeta

Instruction Change: -0.1% :small_red_triangle_down:

org.pentaho.di.trans.steps.symmetriccrypto.symmetriccryptotrans.SymmetricCryptoTransMeta

Branch Change: -3.3% :small_red_triangle_down:
Complexity Change: -1.8% :small_red_triangle_down:
Instruction Change: -0.3% :small_red_triangle_down:

org.pentaho.di.trans.steps.salesforceinsert.SalesforceInsertMeta

Instruction Change: -0.1% :small_red_triangle_down:

Build Completed
:fire: This pull request has some issues. It would be preferable to fix them in order for it to be just perfect. See below for more details. Some links are also available below for further assistance in addressing those issues.
Build Commands
mvn -B -fn -f 'pom.xml' -pl 'engine' -P '!assemblies' -Dsurefire.runOrder=alphabetical -Daudit -amd clean install

Cleanup Commands
mvn -B -f 'pom.xml' -pl 'engine' -P '!assemblies' -amd build-helper:remove-project-artifact

Changed files
  engine/src/main/java/org/pentaho/di/trans/steps/file/BaseFileInputStep.java
  engine/src/main/java/org/pentaho/di/trans/steps/file/BaseFileInputStepData.java

Unit Test Coverage
These statistics help you identify how your changes have affected the coverage of the following files. If a file is not in this list, then its coverage was not affected by your changes. To get some help interpreting these metrics, please refer to Jacoco's documentation.

:warning: Coverage Changes (click to expand)
org.pentaho.di.trans.steps.checksum.CheckSumMeta

Instruction Change: -0.2% :small_red_triangle_down:

org.pentaho.di.trans.step.StepMeta

Branch Change: -0.7% :small_red_triangle_down:
Complexity Change: -0.6% :small_red_triangle_down:
Instruction Change: -0.2% :small_red_triangle_down:
Line Change: -0.3% :small_red_triangle_down:

org.pentaho.di.trans.steps.constant.ConstantMeta

Instruction Change: -0.1% :small_red_triangle_down:

org.pentaho.di.trans.steps.datagrid.DataGridMeta

Branch Change: -2% :small_red_triangle_down:
Complexity Change: -1.7% :small_red_triangle_down:
Instruction Change: -0.2% :small_red_triangle_down:

org.pentaho.di.trans.steps.dbproc.DBProcMeta

Instruction Change: -0.1% :small_red_triangle_down:

org.pentaho.di.trans.steps.file.BaseFileInputStep

Branch Change: -0.9% :small_red_triangle_down:
Complexity Change: -0.6% :small_red_triangle_down:
Instruction Change: -2.7% :small_red_triangle_down:
Line Change: -1.3% :small_red_triangle_down:

org.pentaho.di.trans.steps.groupby.GroupByMeta

Branch Change: -4.1% :small_red_triangle_down:
Complexity Change: -4.2% :small_red_triangle_down:
Instruction Change: -0.2% :small_red_triangle_down:
Line Change: -0.7% :small_red_triangle_down:

org.pentaho.di.trans.steps.singlethreader.SingleThreaderMeta

Instruction Change: -0.1% :small_red_triangle_down:

org.pentaho.di.trans.steps.salesforceinsert.SalesforceInsertMeta

Instruction Change: -0.1% :small_red_triangle_down:

org.pentaho.di.trans.steps.salesforceupdate.SalesforceUpdateMeta

Instruction Change: -0.2% :small_red_triangle_down:

@mbatchelor please review the changes

Build Completed
:fire: This pull request has some issues. It would be preferable to fix them in order for it to be just perfect. See below for more details. Some links are also available below for further assistance in addressing those issues.
Build Commands
mvn -B -fn -f 'pom.xml' -pl 'engine' -P '!assemblies' -Dsurefire.runOrder=alphabetical -Daudit -amd clean install

Cleanup Commands
mvn -B -f 'pom.xml' -pl 'engine' -P '!assemblies' -amd build-helper:remove-project-artifact

Changed files
  engine/src/main/java/org/pentaho/di/trans/steps/file/BaseFileInputStep.java
  engine/src/main/java/org/pentaho/di/trans/steps/file/BaseFileInputStepData.java
  engine/src/test/java/org/pentaho/di/trans/steps/fileinput/text/TextFileInputTest.java

Unit Test Coverage
These statistics help you identify how your changes have affected the coverage of the following files. If a file is not in this list, then its coverage was not affected by your changes. To get some help interpreting these metrics, please refer to Jacoco's documentation.

:warning: Coverage Changes (click to expand)
org.pentaho.di.job.entries.evalfilesmetrics.JobEntryEvalFilesMetrics

Branch Change: -0.4% :small_red_triangle_down:
Complexity Change: -0.5% :small_red_triangle_down:
Instruction Change: -0.1% :small_red_triangle_down:

org.pentaho.di.job.entries.evaluatetablecontent.JobEntryEvalTableContent

Branch Change: -1.1% :small_red_triangle_down:
Complexity Change: -1.1% :small_red_triangle_down:
Instruction Change: -0.1% :small_red_triangle_down:

org.pentaho.di.job.entries.getpop.MailConnectionMeta

Branch Change: -1% :small_red_triangle_down:
Complexity Change: -1.5% :small_red_triangle_down:
Instruction Change: -0.3% :small_red_triangle_down:

org.pentaho.di.job.entries.waitforsql.JobEntryWaitForSQL

Branch Change: -0.8% :small_red_triangle_down:
Complexity Change: -1% :small_red_triangle_down:
Instruction Change: -0.1% :small_red_triangle_down:

org.pentaho.di.trans.steps.excelwriter.ExcelWriterStepMeta

Branch Change: -1.3% :small_red_triangle_down:
Complexity Change: -0.7% :small_red_triangle_down:

org.pentaho.di.trans.steps.groupby.GroupByMeta

Branch Change: -2% :small_red_triangle_down:
Complexity Change: -2.1% :small_red_triangle_down:
Instruction Change: -0.2% :small_red_triangle_down:
Line Change: -0.7% :small_red_triangle_down:

org.pentaho.di.trans.steps.ldapoutput.LDAPOutputMeta

Instruction Change: -0.1% :small_red_triangle_down:

org.pentaho.di.trans.steps.rowgenerator.RowGeneratorMeta

Branch Change: -2.6% :small_red_triangle_down:
Complexity Change: -1.5% :small_red_triangle_down:
Instruction Change: -0.1% :small_red_triangle_down:

org.pentaho.di.trans.steps.singlethreader.SingleThreaderMeta

Instruction Change: -0.1% :small_red_triangle_down:

org.pentaho.di.trans.steps.sortedmerge.SortedMergeMeta

Instruction Change: -0.2% :small_red_triangle_down:

org.pentaho.di.trans.steps.textfileinput.TextFileInputMeta

Branch Change: -0.5% :small_red_triangle_down:

org.pentaho.di.trans.steps.webservices.WebServiceMeta

Branch Change: -1.7% :small_red_triangle_down:
Complexity Change: -1.2% :small_red_triangle_down:
Instruction Change: -0.1% :small_red_triangle_down:


Exclude Pages

I am trying to exclude some pages from loading translation, but in the docs, it is not mentioned.  Is it possible?  If yes, then how?

It's planned for 1.1 😊 Duplicated of https://github.com/vinissimus/next-translate/issues/579


Sound doesn't work correctly

"play" method for sounds plays the wrong sounds/sounds don't sound like they should in the game

I tried to troubleshoot it, but no luck. so i rewrote the Audio and Sounds system.
now (at least on my machine) it works fine.
unfortunately, I couldn't understand the design and architecture of the system that you created; i checked a couple resources and I think my design is ok.
I'll link the PR here. #10


E118: Too many arguments for function: function

Just installed in a new fresh and I got this:
Error detected while processing /root/.vim_runtime/sources_non_forked/vim-go/plugin/go.vim: line   70: E118: Too many arguments for function: function E15: Invalid expression: { 'asmfmt':        ['github.com/klauspost/asmfmt/cmd/asmfmt'], 'dlv':           ['github.com/go-delve/delve/cmd/dlv'], 'errcheck':      ['github.com/kisielk/errcheck'], 'fillstruct':    ['github.com/davidrjenni/reftools/cmd/fillstruct'], 'gocode':        ['github.com/mdempsky/gocode', {'windows': ['-ldflags', '-H=windowsgui']}], 'gocode-gomod':  ['github.com/stamblerre/gocode'], 'godef':         ['github.com/rogpeppe/godef'], 'gogetdoc':      ['github.com/zmb3/gogetdoc'], 'goimports':     ['golang.org/x/tools/cmd/goimports'], 'golint':        ['golang.org/x/lint/golint'], 'gopls':         ['golang.org/x/tools/gopls@latest', {}, {'after': function('go#lsp#Restart', [])}], 'gometalinter':  ['github.com/alecthomas/gometalinter'], 'golangci-lint': ['github.com/golangci/golangci-lint/cmd/golangci-lint'], 'gomodifytags':  ['github.com/fatih/gomodifytags'], 'gorename':      ['golang.org/x/tools/cmd/gorename'], 'gotags':        ['github.com/jstemmer/gotags'], 'guru':          ['golang.org/x/t Press ENTER or type command to continue

Same happened to me. Did you figure out how to solve this?

No, the problem persist even in other new fresh machines I'm deploying.
Sadly maintainers did not show up yet.
The only workaround I can suggest to you is to install the Basic version instead of the Awesome (wish is not awesome anymore)

Same error here here. I'm on CentOS 7.

same error in Redhat 7.4

same here, since I dont use go, I just remove the folder temporarily

This is now fixed. I have removed vim-go from the standard dist (it's too heavy).

@amix don't you need to remove vim-go from sources_non_forked manually?

Thanks @amix, that works perfectly!

I’ve now removed it 😊
On Mon, 18 Nov 2019 at 09:45, Alejandro Gomez Espinosa <
<EMAIL_ADDRESS>wrote:

Thanks @amix https://github.com/amix, that works perfectly!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/amix/vimrc/issues/537?email_source=notifications&email_token=AABNBDTUMUJ23QNTWF4XCRDQUJIZBA5CNFSM4IU4WAYKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEEJU3LA#issuecomment-554913196,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AABNBDXFDVMF4I63ZNSSGNLQUJIZBANCNFSM4IU4WAYA
.


add social media card for July 2022 event

Is this what we want to appear as image on twitter when sharing the link to the website?

Is this what we want to appear as image on twitter when sharing the link to the website?

@OriolAbril Yes.


Kong routes traffic to deleted targets

Summary
Kong routes traffic to deleted targets.
Steps To Reproduce

Start 2 upstream servers, let's say server1 listening on localhost:8881, server2 listening on localhost:8882.
Server code:

package main

import (
	"fmt"
	"flag"
	"net/http"
)

var (
	port int
	name string
)

func main() {
	flag.IntVar(&port, "port", 8080, "http server port")
	flag.StringVar(&name, "name", "me", "http server name")
	flag.Parse()

	http.HandleFunc("/about", func (w http.ResponseWriter, r *http.Request) {
		fmt.Fprintf(w, "this is %s, listening on port %d", name, port)
	})

	http.ListenAndServe(fmt.Sprintf(":%d", port), nil)
}

Add a route and related resources. Add server1 as the upstream's target.

curl -i -X POST \
  --url http://localhost:8001/upstreams/ \
  --data 'name=myupstream'

curl -s -X POST --url http://localhost:8001/upstreams/myupstream/targets --data 'target=<IP_ADDRESS>:8881'

curl -i -X POST \
  --url http://localhost:8001/services/ \
  --data 'name=example-service' \
  --data 'url=http://myupstream'

curl -i -X POST \
  --url http://localhost:8001/services/example-service/routes \
  --data 'hosts[]=routea.com' \
  --data 'name=routea'

Delete a target <IP_ADDRESS>:8881, add a target <IP_ADDRESS>:8882

 curl -i -X DELETE --url http://localhost:8001/upstreams/myupstream/targets/<IP_ADDRESS>:8881 && curl -i -X POST --url http://localhost:8001/upstreams/myupstream/targets --data 'target=<IP_ADDRESS>:8882'

Send some requests to Kong and check response, you'll find that Kong's still routing (some) requests to the deleted target server1(listening on 8881). But via admin api, you can find just only one target of this upstream and it's server2(<IP_ADDRESS>:8882).

curl localhost:8000/about -H "Host: routea.com" -H "Kong-Debug: true" -i
HTTP/1.1 200 OK
Content-Type: text/plain; charset=utf-8
Content-Length: 36
Connection: keep-alive
Kong-Route-Id: 26c1a714-06c1-440d-a426-31c7566a4a92
Kong-Route-Name: routea
Kong-Service-Id: 781a15b0-eb78-47f5-bcd3-5ad387bf8a1a
Kong-Service-Name: example-service
Date: Mon, 29 Jul 2019 10:45:06 GMT
X-Kong-Upstream-Latency: 1
X-Kong-Proxy-Latency: 0
Via: kong/1.2.1

this is zero, listening on port 8881

Additional Details & Logs

Kong version: 1.2.1
Kong error logs:

2019/07/29 18:38:00 [notice] 65268#0: *18847 [lua] targets.lua:64: clean_history(): [Target DAO] Starting cleanup of target table for upstream 54f2a833-42c9-48a3-929a-6ee5bf46231e, client: <IP_ADDRESS>, server: kong_admin, request: "DELETE /upstreams/myupstream/targets/<IP_ADDRESS>:8881 HTTP/1.1", host: "localhost:8001"
2019/07/29 18:38:00 [info] 65268#0: *18847 [lua] targets.lua:77: clean_history(): [Target DAO] Finished cleanup of target table for upstream 54f2a833-42c9-48a3-929a-6ee5bf46231e removed 2 target entries, client: <IP_ADDRESS>, server: kong_admin, request: "DELETE /upstreams/myupstream/targets/<IP_ADDRESS>:8881 HTTP/1.1", host: "localhost:8001"
2019/07/29 18:38:00 [info] 65268#0: *18847 kevent() reported that client <IP_ADDRESS> closed keepalive connection
2019/07/29 18:38:00 [info] 65268#0: *18850 kevent() reported that client <IP_ADDRESS> closed keepalive connection
2019/07/29 18:38:01 [error] 65269#0: *18855 [lua] balancer.lua:267: [healthchecks] failed setting peer status: no peer found by name '<IP_ADDRESS>' and address <IP_ADDRESS>:8882, context: ngx.timer
2019/07/29 18:38:01 [error] 65275#0: *18858 [lua] balancer.lua:267: [healthchecks] failed setting peer status: no peer found by name '<IP_ADDRESS>' and address <IP_ADDRESS>:8882, context: ngx.timer
2019/07/29 18:38:01 [error] 65270#0: *18873 [lua] balancer.lua:267: [healthchecks] failed setting peer status: no peer found by name '<IP_ADDRESS>' and address <IP_ADDRESS>:8882, context: ngx.timer
2019/07/29 18:38:01 [error] 65274#0: *18860 [lua] balancer.lua:267: [healthchecks] failed setting peer status: no peer found by name '<IP_ADDRESS>' and address <IP_ADDRESS>:8882, context: ngx.timer
2019/07/29 18:38:01 [error] 65272#0: *18859 [lua] balancer.lua:267: [healthchecks] failed setting peer status: no peer found by name '<IP_ADDRESS>' and address <IP_ADDRESS>:8882, context: ngx.timer
2019/07/29 18:38:01 [error] 65271#0: *18861 [lua] balancer.lua:267: [healthchecks] failed setting peer status: no peer found by name '<IP_ADDRESS>' and address <IP_ADDRESS>:8882, context: ngx.timer
2019/07/29 18:38:01 [error] 65273#0: *18862 [lua] balancer.lua:267: [healthchecks] failed setting peer status: no peer found by name '<IP_ADDRESS>' and address <IP_ADDRESS>:8882, context: ngx.timer

Kong configuration: default config
Operating system: linux/osx

Looked into debug log and found that only one worker rebuilt the ring balancer after step2(Delete a target <IP_ADDRESS>:8881, add a target <IP_ADDRESS>:8882). Other workers just fetched targets for upstream but didn't rebuild the ring balancer.
Debug error:
cat logs/error.log | grep -E "fetching targets for upstream|removeHost|new address for host|Starting cleanup of target"
2019/07/29 20:46:34 [debug] 83340#0: *2711 [lua] balancer.lua:123: fetching targets for upstream: 4af970ea-ab3f-4f91-b089-a324389c0447
2019/07/29 20:46:34 [debug] 83340#0: *2711 [lua] base.lua:905: removeHost(): [ringbalancer 2] removing host <IP_ADDRESS>:8881
2019/07/29 20:46:34 [notice] 83340#0: *2711 [lua] targets.lua:64: clean_history(): [Target DAO] Starting cleanup of target table for upstream 4af970ea-ab3f-4f91-b089-a324389c0447, client: <IP_ADDRESS>, server: kong_admin, request: "DELETE /upstreams/myupstream/targets/<IP_ADDRESS>:8881 HTTP/1.1", host: "localhost:8001"
2019/07/29 20:46:34 [debug] 83340#0: *2711 [lua] balancer.lua:123: fetching targets for upstream: 4af970ea-ab3f-4f91-b089-a324389c0447
2019/07/29 20:46:34 [debug] 83340#0: *2711 [lua] base.lua:304: newAddress(): [ringbalancer 3] new address for host '<IP_ADDRESS>' created: <IP_ADDRESS>:8881 (weight 100)
2019/07/29 20:46:34 [debug] 83340#0: *2711 [lua] balancer.lua:123: fetching targets for upstream: 4af970ea-ab3f-4f91-b089-a324389c0447
2019/07/29 20:46:34 [debug] 83340#0: *2714 [lua] balancer.lua:123: fetching targets for upstream: 4af970ea-ab3f-4f91-b089-a324389c0447
2019/07/29 20:46:34 [debug] 83340#0: *2714 [lua] base.lua:304: newAddress(): [ringbalancer 4] new address for host '<IP_ADDRESS>' created: <IP_ADDRESS>:8882 (weight 100)
2019/07/29 20:46:35 [debug] 83342#0: *2731 [lua] balancer.lua:123: fetching targets for upstream: 4af970ea-ab3f-4f91-b089-a324389c0447
2019/07/29 20:46:35 [debug] 83342#0: *2731 [lua] balancer.lua:123: fetching targets for upstream: 4af970ea-ab3f-4f91-b089-a324389c0447
2019/07/29 20:46:35 [debug] 83342#0: *2731 [lua] balancer.lua:123: fetching targets for upstream: 4af970ea-ab3f-4f91-b089-a324389c0447
2019/07/29 20:46:35 [debug] 83342#0: *2731 [lua] balancer.lua:123: fetching targets for upstream: 4af970ea-ab3f-4f91-b089-a324389c0447
2019/07/29 20:46:35 [debug] 83348#0: *2738 [lua] balancer.lua:123: fetching targets for upstream: 4af970ea-ab3f-4f91-b089-a324389c0447
2019/07/29 20:46:35 [debug] 83348#0: *2738 [lua] balancer.lua:123: fetching targets for upstream: 4af970ea-ab3f-4f91-b089-a324389c0447
2019/07/29 20:46:35 [debug] 83348#0: *2738 [lua] balancer.lua:123: fetching targets for upstream: 4af970ea-ab3f-4f91-b089-a324389c0447
2019/07/29 20:46:35 [debug] 83344#0: *2739 [lua] balancer.lua:123: fetching targets for upstream: 4af970ea-ab3f-4f91-b089-a324389c0447
2019/07/29 20:46:35 [debug] 83346#0: *2735 [lua] balancer.lua:123: fetching targets for upstream: 4af970ea-ab3f-4f91-b089-a324389c0447
2019/07/29 20:46:35 [debug] 83346#0: *2735 [lua] balancer.lua:123: fetching targets for upstream: 4af970ea-ab3f-4f91-b089-a324389c0447
2019/07/29 20:46:35 [debug] 83346#0: *2735 [lua] balancer.lua:123: fetching targets for upstream: 4af970ea-ab3f-4f91-b089-a324389c0447
2019/07/29 20:46:35 [debug] 83344#0: *2739 [lua] balancer.lua:123: fetching targets for upstream: 4af970ea-ab3f-4f91-b089-a324389c0447
2019/07/29 20:46:35 [debug] 83344#0: *2739 [lua] balancer.lua:123: fetching targets for upstream: 4af970ea-ab3f-4f91-b089-a324389c0447
2019/07/29 20:46:35 [debug] 83347#0: *2745 [lua] balancer.lua:123: fetching targets for upstream: 4af970ea-ab3f-4f91-b089-a324389c0447
2019/07/29 20:46:35 [debug] 83347#0: *2745 [lua] balancer.lua:123: fetching targets for upstream: 4af970ea-ab3f-4f91-b089-a324389c0447
2019/07/29 20:46:35 [debug] 83347#0: *2745 [lua] balancer.lua:123: fetching targets for upstream: 4af970ea-ab3f-4f91-b089-a324389c0447
2019/07/29 20:46:35 [debug] 83347#0: *2745 [lua] balancer.lua:123: fetching targets for upstream: 4af970ea-ab3f-4f91-b089-a324389c0447
2019/07/29 20:46:35 [debug] 83343#0: *2746 [lua] balancer.lua:123: fetching targets for upstream: 4af970ea-ab3f-4f91-b089-a324389c0447
2019/07/29 20:46:35 [debug] 83343#0: *2746 [lua] balancer.lua:123: fetching targets for upstream: 4af970ea-ab3f-4f91-b089-a324389c0447
2019/07/29 20:46:35 [debug] 83343#0: *2746 [lua] balancer.lua:123: fetching targets for upstream: 4af970ea-ab3f-4f91-b089-a324389c0447
2019/07/29 20:46:35 [debug] 83343#0: *2746 [lua] balancer.lua:123: fetching targets for upstream: 4af970ea-ab3f-4f91-b089-a324389c0447
2019/07/29 20:46:35 [debug] 83341#0: *2742 [lua] balancer.lua:123: fetching targets for upstream: 4af970ea-ab3f-4f91-b089-a324389c0447
2019/07/29 20:46:35 [debug] 83341#0: *2742 [lua] balancer.lua:123: fetching targets for upstream: 4af970ea-ab3f-4f91-b089-a324389c0447
2019/07/29 20:46:35 [debug] 83341#0: *2742 [lua] balancer.lua:123: fetching targets for upstream: 4af970ea-ab3f-4f91-b089-a324389c0447

@zeeshen we were not able to reproduce the issue. Could you test with version 1.3.0rc1 to check if the problem persists, please?

@zeeshen Can you update the 1.3.0 and give it a try?

We tried the 1.3.0 version and this bug still exists.
In step 2: we use an && to ensure the 2nd request is sent immediately after the 1st request.
In step 3: tools like wrk may be helpful as not all the workers' routing are incorrect.
 So during rapid target changes, the rebuild process will be skipped if the targets length is unchanged.
This bug may be introduced by this commit. This commit removed the call of add_order in select_by_upstream_raw.


Major RC Upgrade: Scroll to active step / have a dropdown arrow in the workflow to avoid seeing the whole workflow when you open the RC

Covered in https://github.com/orgs/equinor/projects/636/views/7?pane=issue&itemId=54883408


Report Flakes UI should include wasm32

Currently, the parameterized test runs do not include wasm32, which can result in a "successful" flake report, with failing wasm32 tests. wasm32 has its own unique setup, but may be able to align the wasm32 tests with the flake reporting.

wasm32 testing doesn't currently use nextest, and I'm not sure if it is even possible because it has a custom test runner under the hood (wasm-bindgen-testrunner). It would be great if we could some how integrate it.


rook provisioner secret doesn't exist

what am I doing wrong?
When I go to provision Harbor, about half the pods never come up. I look into the logs, and I see things like this:
 PersistentVolumeClaims
2s          Normal    ExternalProvisioning   persistentvolumeclaim/harbor-harbor-jobservice                 waiting for a volume to be created, either by external provisioner "rook-ceph.rbd.csi.ceph.com" or manually created by system administrator
2m7s        Normal    Provisioning           persistentvolumeclaim/harbor-harbor-jobservice                 External provisioner is provisioning volume for claim "harbor-system/harbor-harbor-jobservice"
2m7s        Warning   ProvisioningFailed     persistentvolumeclaim/harbor-harbor-jobservice                 failed to provision volume with StorageClass "rook-ceph-block": error getting secret rook-csi-rbd-provisioner in namespace rook-ceph: secrets "rook-csi-rbd-provisioner" not found
4m20s       Normal    ScalingReplicaSet      deployment/harbor-harbor-jobservice                            Scaled up replica set harbor-harbor-jobservice-5866574b74 to 1
4m20s       Normal    Scheduled              pod/harbor-harbor-portal-559d4dfc84-pz28z                      Successfully assigned harbor-system/harbor-harbor-portal-559d4dfc84-pz28z to aks-agentpool-34146011-vmss000002
4m19s       Normal    Pulled                 pod/harbor-harbor-portal-559d4dfc84-pz28z                      Container image "goharbor/harbor-portal:v2.1.0" already present on machine
4m18s       Normal    Created                pod/harbor-harbor-portal-559d4dfc84-pz28z                      Created container portal
4m18s       Normal    Started                pod/harbor-harbor-portal-559d4dfc84-pz28z                      Started container portal
4m20s       Normal    SuccessfulCreate       replicaset/harbor-harbor-portal-559d4dfc84                     Created pod: harbor-harbor-portal-559d4dfc84-pz28z
4m20s       Normal    ScalingReplicaSet      deployment/harbor-harbor-portal                                Scaled up replica set harbor-harbor-portal-559d4dfc84 to 1
7m33s       Warning   FailedScheduling       pod/harbor-harbor-redis-0                                      error while running "VolumeBinding" filter plugin for pod "harbor-harbor-redis-0": pod has unbound immediate PersistentVolumeClaims
4m20s       Warning   FailedScheduling       pod/harbor-harbor-redis-0                                      error while running "VolumeBinding" filter plugin for pod "harbor-harbor-redis-0": pod has unbound immediate PersistentVolumeClaims
3m30s       Warning   FailedScheduling       pod/harbor-harbor-redis-0                                      error while running "VolumeBinding" filter plugin for pod "harbor-harbor-redis-0": pod has unbound immediate PersistentVolumeClaims
4m20s       Normal    SuccessfulCreate       statefulset/harbor-harbor-redis                                create Claim data-harbor-harbor-redis-0 Pod harbor-harbor-redis-0 in StatefulSet harbor-harbor-redis success
4m20s       Normal    SuccessfulCreate       statefulset/harbor-harbor-redis                                create Pod harbor-harbor-redis-0 in StatefulSet harbor-harbor-redis successful
7m33s       Warning   FailedScheduling       pod/harbor-harbor-registry-54d98d469f-p6c8s                    error while running "VolumeBinding" filter plugin for pod "harbor-harbor-registry-54d98d469f-p6c8s": pod has unbound immediate PersistentVolumeClaims
4m20s       Warning   FailedScheduling       pod/harbor-harbor-registry-b6b58668c-6x6zp                     error while running "VolumeBinding" filter plugin for pod "harbor-harbor-registry-b6b58668c-6x6zp": pod has unbound immediate PersistentVolumeClaims
4m20s       Warning   FailedScheduling       pod/harbor-harbor-registry-b6b58668c-6x6zp                     error while running "VolumeBinding" filter plugin for pod "harbor-harbor-registry-b6b58668c-6x6zp": pod has unbound immediate PersistentVolumeClaims
4m20s       Normal    SuccessfulCreate       replicaset/harbor-harbor-registry-b6b58668c                    Created pod: harbor-harbor-registry-b6b58668c-6x6zp
2s          Normal    ExternalProvisioning   persistentvolumeclaim/harbor-harbor-registry                   waiting for a volume to be created, either by external provisioner "rook-ceph.rbd.csi.ceph.com" or manually created by system administrator
2m8s        Normal    Provisioning           persistentvolumeclaim/harbor-harbor-registry                   External provisioner is provisioning volume for claim "harbor-system/harbor-harbor-registry"
2m8s        Warning   ProvisioningFailed     persistentvolumeclaim/harbor-harbor-registry                   failed to provision volume with StorageClass "rook-ceph-block": error getting secret rook-csi-rbd-provisioner in namespace rook-ceph: secrets "rook-csi-rbd-provisioner" not found
4m20s       Normal    ScalingReplicaSet      deployment/harbor-harbor-registry                              Scaled up replica set harbor-harbor-registry-b6b58668c to 1

in particular: failed to provision volume with StorageClass "rook-ceph-block": error getting secret rook-csi-rbd-provisioner in namespace rook-ceph: secrets "rook-csi-rbd-provisioner" not found
So, I go to look at the rook-csi-rbd-provisioner in namespace rook-ceph, and it doesn't exist. Instead, we have a SIMILAR secret with something else appended: rook-csi-rbd-provisioner-sa-token-5p5gt
What am I doing wrong here? Love a 15 minute slot with you.

Here's the line of code that in the storage-class creation refers to the name: https://github.com/phillipgibson/cncf-projects-app/blob/6717a6f798a816543db5f9c81d01a32524c6fa44/yml/rook-storageclass.yaml#L21. But.... huh?

Hmmmm, @fmustaf and @garvinmsft I'll need 15 minutes to work through making this work properly, but I've got the rook and harbor stuff working now, but the portal does not come up as desired. I'll close this.


List contents of a directory asynchronously

Package Name: azure-storage-file-share
Package Version: 12.2.0
Operating System: Ubuntu 20.04
Python Version: 3.8.5

Describe the bug
List contents of a directory asynchronously fails with following error.
....venv/lib/python3.8/site-packages/azure/storage/fileshare/_generated/aio/operations_async/_directory_operations_async.py", line 486, in list_files_and_directories_segment
raise models.StorageErrorException(response, self._deserialize)
azure.storage.fileshare._generated.models._models_py3.StorageErrorException: Operation returned an invalid status 'Value for one of the query parameters specified in the request URI is invalid.'
During handling of the above exception, another exception occurred:
File "...venv/lib/python3.8/site-packages/azure/core/async_paging.py", line 147, in anext
return await self.anext()
File "...venv/lib/python3.8/site-packages/azure/core/async_paging.py", line 150, in anext
self._page = await self._page_iterator.anext()
File "...venv/lib/python3.8/site-packages/azure/core/async_paging.py", line 97, in anext
self._response = await self._get_next(self.continuation_token)
File "...venv/lib/python3.8/site-packages/azure/storage/fileshare/aio/_models.py", line 168, in _get_next_cb
process_storage_error(error)
File "...venv/lib/python3.8/site-packages/azure/storage/fileshare/_shared/response_handlers.py", line 147, in process_storage_error
raise error
azure.core.exceptions.HttpResponseError: Value for one of the query parameters specified in the request URI is invalid.
RequestId:7ecac428-f01e-004c-0909-aefaac000000
Time:2020-10-29T15:35:55.9110150Z
ErrorCode:InvalidQueryParameterValue
Error:None
QueryParameterName:comp
QueryParameterValue:list
To Reproduce
Steps to reproduce the behavior: Used the sample code from README.md
https://github.com/Azure/azure-sdk-for-python/tree/master/sdk/storage/azure-storage-file-share#listing-contents-of-a-directory
from azure.storage.fileshare.aio import ShareClient
share_client = ShareClient(account_url=url, credential=credential, share_name=share_name)
async with share_client:
    my_files = []
    async for item in share_client.list_directories_and_files(directory_name='WQ'):
        my_files.append(item)
    print(my_files)

Expected behavior
The Directory "WQ" contains few csv file, I can list them with sync api code, but does not work with async api code
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
Add any other context about the problem here.

My bad! I was sending a blob storage url to file share api. It did not complain on auth as it is a valid SAS. The errors are very misleading. Closing it. Thanks much.


Webservices do not cap in-line SMILES

The following HELM
PEPTIDE1{C.G.[[*]N[C@@H](C=O)C([*])=O |$_R1;;;;;;_R2;$|]}$$$$V2.0
Does not generate the correct mol formula. The un-substituted R group is not changed into the capping group.

Where is the capping group defined?

I guess it makes sense to not calculate molecular properties from not fully defined structures. I would not recommend to use default values für capping groups.
The user should modify the inline SMILES for a fully defined molecule.

The HELM team agreed that mol properties should not be calculated for structures with free connection points. This issue is continued via the spreadsheet of in-line HELM test structures. CLose here.


Add select maximum number of posts per page

Issue
None, it's just a feature.
Description
With this parameter you can select the maximum number of posts that will appear to each page. It will default to 12 (the value that we were using before). To configure it, just add the following lines under the params section of config.yaml:
postsPage:
    maxPostsPerPage: 20 # Default: 12

Before I add this into the guides and the example file, tell me if you want to change the name of the parameter, or if I have to change the location of it.
Test Evidence
maxPostsPerPage=5

maxPostsPerPage=10

I added it to the example site.
If you want, I can add it to the guides aswell.

I'll fix it now


V2 tests

The issue resolved by this Pull Request:
Resolves https://issues.redhat.com/browse/RHOAIENG-2581
Testing instructions
see kind tests run in gh workflows ui
or try running them in your local cluster here
Checklist

[x] The commits are squashed in a cohesive manner and have meaningful messages.
[x] Testing instructions have been added in the PR body (for PRs involving changes that are not immediately obvious).
[x] The developer has manually tested the changes and verified that the changes work

A new image has been built to help with testing out this PR: quay.io/opendatahub/data-science-pipelines-operator:pr-566
An OCP cluster where you are logged in as cluster admin is required.
To use this image run the following:
cd $(mktemp -d)
git clone git@github.com:opendatahub-io/data-science-pipelines-operator.git
cd data-science-pipelines-operator/
git fetch origin pull/566/head
git checkout -b pullrequest 974f3ed961241395a684f7bf269ff706443d06c8
make deploy IMG="quay.io/opendatahub/data-science-pipelines-operator:pr-566"

More instructions here on how to deploy and test a Data Science Pipelines Application.

Change to PR detected. A new PR build was completed.
A new image has been built to help with testing out this PR: quay.io/opendatahub/data-science-pipelines-operator:pr-566


Are U sure the code is right?

I get my gt files and list the number of each class of objects, and it is absolutely different from your grount-truth histogram. I dont know whether the code is right, please help me

sorry，i didn't notice the different objets.


Renaming ThirdPartyNotices

Docs Build status updates of commit 081ff3c:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

ThirdPartyNotices.md
:white_check_mark:Succeeded

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


Test for pandas_io

Current coverage is 94.70%

Merging #38 into master will increase coverage by +0.73% as of f32f427

@@            master    #38   diff @@
=====================================
  Files           19     20     +1
  Stmts          581    604    +23
  Branches         0      0
  Methods          0      0
=====================================
+ Hit            546    572    +26
  Partial          0      0
+ Missed          35     32     -3

Review entire Coverage Diff as of f32f427

Powered by Codecov. Updated on successful CI builds.


Add resources and scopes docs

Copies over #1957 due to build failure + package-lock file

Coverage remained the same at 81.614% when pulling 3db960a478668de9b79482f237ae5ea48eb52668 on resource-docs into 9ad7ff70ba3b76a5cc70399dd05255e13694eab6 on dev.


Implement PoC VS Code Plugin

Let's start a PoC and push it in a private repo for now.

@amihaiemil this is your task now, please go ahead. Deadline (when this ticket should be closed) is 2023-11-28T14:47:45.916730.
Estimation here is 60 minutes, that's how much you will be paid.
Remember, you don't have to solve everything in this ticket - you can solve it partially and leave todo markers in the code, which will become future tasks.
If you have any questions don't ask me, I'm not a technical person. Open new tickets instead.
If you don't have time or simply don't want to work on this, you can always resign.

@amihaiemil please keep in mind that manual assignment of tickets is a bad practice and it is discouraged. Next time, please let me elect the assignee.

@amihaiemil thank you for resolving this ticket. I've just added it to your active invoice. You can always check all your invoices and more on the Contributor Dashboard.


Fixing java tasks

Problem: The java tasks (ant/maven/gradle) are broken for windows coreclr agent with ps1 implementation.
Fix: The core clr agent asynchronously published build artifacts and we were deleting the directories at the end of the task in ps1 implementation. Moved the deletions to the beginning of the task.
Testing: Manually on AppFabric

$summaryFile = Join-Path $buildRootPath $reportDirectoryName

version bump

Refers to: Tasks/ANT/ant.ps1:132 in 32e21bb. [](commit_id = 32e21bb44fdee0b508bb07a6ae2e65088b362af9, deletion_comment = False)

sign off with comments


poi extension Build native image error

Describe the bug
In my work, I needed to export data to excel, so I adopted quarkus-poi, and there were no errors during the test. When building a local executable, "Windows AWT integration is not ready in native images and Java" is thrown. Lang. UnsatisfiedLinkError: There is no awt in java.library.path.'. But I only want to use excel related functions in poi, not AWT related functions.
Expected behavior
Expect the behavior to build successfully because I'm not going to use the awt functionality
Actual behavior
Building a native executable throws:'Windows AWT integration is not ready in native-image and would result in java.lang.UnsatisfiedLinkError: no awt in java.library.path.'
How to Reproduce?
1:Import the poi extension
 io.quarkiverse.poi quarkus-poi 2.0.3
2:mvnw package -Dnative
Output of uname -a or ver
Microsoft Windows [版本 10.0.19045.3570]
Output of java -version
openjdk version "17.0.6" 2023-01-17 OpenJDK Runtime Environment GraalVM CE 22.3.1 (build 17.0.6+10-jvmci-22.3-b13) OpenJDK 64-Bit Server VM GraalVM CE 22.3.1 (build 17.0.6+10-jvmci-22.3-b13, mixed mode, sharing)
Mandrel or GraalVM version (if different from Java)
OpenJDK 64-Bit Server VM GraalVM CE 22.3.1 (build 17.0.6+10-jvmci-22.3-b13, mixed mode, sharing)
Quarkus version or git rev
3.2.0.Final
Build tool (ie. output of mvnw --version or gradlew --version)
Apache Maven 3.9.2 (c9616018c7a021c1c39be70fb2843d6f5f9b8a1c)
Maven home: D:\apache-maven-3.9.2
Java version: 17.0.6, vendor: GraalVM Community, runtime: D:\graalvm-ce-java17-22.3.1
Default locale: zh_CN, platform encoding: GBK
OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"
Additional information
io.quarkiverse.poi quarkus-poi 2.0.3

Hmm can you create a small reproducer?  Our Integration tests run in native mode and are passing.

嗯，你能创建一个小型复制器吗？我们的集成测试在本机模式下运行并且正在通过。
我还在我的应用程序中以本机模式成功使用它。

Ok, I use quarkus-hibernate-orm as a test case, and the project is on gitee. https://gitee.com/wsl__cn/quarkus-poi-issues.git

Ok great I will check it!

@Sparkel-wsl I don't see any code here: https://gitee.com/wsl__cn/quarkus-poi-issues/blob/master/hibernate-orm-quickstart/src/main/java/org/acme/hibernate/orm/Controller/TestController.java That our integration tests aren't already testing and passing in Native mode.
Did you forget to check something in?

@melloware I did not use poi related functions on the test case, even though I did not use poi related functions, just to repeat the error. However, when building native executables, the error mentioned above is still displayed.

Well this is the POI extension and without a POI issue I will close this. I am not having any Native Image issue and the nightly build is also passing on Native mode.

Don't know why but it looks like you are having this Graal issue https://github.com/oracle/graal/issues/2842


Help me to integrate this player in react app with multi quality and multi audio support

💬 Questions and Help

Read carefully the README of the project
Search if your answer has already been answered in old issues

After you can submit your question and we will be happy to help you!
and i try my source in demo player but after set source it give me error source not support but source fully working ( HLS source )
Try if you wanna test :-  https://pastebin.com/F3i3JdSm

I face this error 😅😅

hls support.
set format =hls

hls support. set format =hls

Can you give me a code snippet for react i try understand documenting but all are mix which plugging use, what is boiler plate code in react little bit Massey

Try in PC very strange behavior ( in mobile working but in pc not working 🤣🤣 )


controller 1 and 2 only move the left screen

How do I make controller 1 and 2 control different screens/ characters

This is very strange and should not happen normally, could you please confirm if you use any software to remap controllers maybe?

This is very strange and should not happen normally, could you please confirm if you use any software to remap controllers maybe?

Thanks for responding so fast you’re awesome, I actually figured it out I had to turn off steam controller but while I have you here I was wondering why does the hud with the level and the health in each body part typically break at 400 points any fixes it really helps thanks so much!

It just stops working

The HUD update loop of the trainer mod sometimes cannot find one of the game's objects (the places from where it reads the player's health, score, etc.), which may happen either due to a bug in UE4SS or due to the general instability of the game's engine. I actually just tried to improve the handling of these errors in the upcoming v0.10 release of the trainer mod (the HUD should try to keep updating itself if).


[WIP] Ndbc module

Problem
The postgresql/mysql-async driver has a few scalability and performance problems.
Solution
I've been working on an alternative driver called ndbc. It's already fully functional for postres and has feature parity with postgresql-async.
Notes

It's possible to easily test this new module using scalafix to rewrite the future compositions to the traneio future. See https://gist.github.com/fwbrasil/07272093ef61033102ce41952243f11b for details.
The configuration has a fixed "ndbc" prefix. See the test configuration for an example.

Checklist

[ ] Unit test all changes
[ ] Update README.md if applicable
[ ] Add [WIP] to the pull request title if it's work in progress
[ ] Squash commits that aren't meaningful changes
[ ] Run sbt scalariformFormat test:scalariformFormat to make sure that the source files are formatted

@getquill/maintainers

Hi @fwbrasil,
Will you consider using ndbc for async-postrgres ?
Thanks

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Closing has we've decided to remove the NDBC support


Fixed typo (classifer)

Docs Build status updates of commit 98f2882:
:warning: Validation status: warnings

File
Status
Preview URL
Details

articles/Setup-Windows-Python.md
:warning:Warning
View
Details

articles/404.md
:warning:Warning
View
Details

articles/Loading-Data-Overview.md
:warning:Warning
View
Details

articles/Unary-Operations.md
:warning:Warning
View
Details

articles/How-do-I-Train-models-in-Python.md
:warning:Warning
View
Details

articles/Interpreting-epoch_size-and-minibatch_size_in_samples-and-MinibatchSource.next_minibatch-in-CNTK.md
:warning:Warning
View
Details

articles/Setup-Linux-Python.md
:warning:Warning
View
Details

articles/BrainScript-Layers-Reference.md
:white_check_mark:Succeeded
View

articles/Setup-Windows-Python.md

[Warning] Duplicate tab id: (cntkpy26, 2).
Line 55: [Warning] Invalid link: 'PyPI'. The file Setup-Windows-Python.md doesn't contain a bookmark named 'installfrompypi'.

articles/404.md

[Warning] Missing attribute: author. Add the current author's GitHub ID.
[Warning] Missing attribute: title. Add a title string to show in search engine results.

articles/Loading-Data-Overview.md

[Warning] Missing attribute: author. Add the current author's GitHub ID.

articles/Unary-Operations.md

[Warning] Missing attribute: author. Add the current author's GitHub ID.
[Warning] Missing attribute: title. Add a title string to show in search engine results.

articles/How-do-I-Train-models-in-Python.md

Line 15: [Warning] Invalid link: 'Relate alpha, beta1, beta2 and epsilon to learning rate and momentum in adam_sgd'. The file How-do-I-Train-models-in-Python.md doesn't contain a bookmark named 'relate-alpha-beta1-beta2-and-epsilon-to-learning-rate-and-momentum-in-adamsgd'.

articles/Interpreting-epoch_size-and-minibatch_size_in_samples-and-MinibatchSource.next_minibatch-in-CNTK.md

Line 14: [Warning] Invalid link: 'epoch_size'. The file Interpreting-epoch_size-and-minibatch_size_in_samples-and-MinibatchSource.next_minibatch-in-CNTK.md doesn't contain a bookmark named 'epochsize'.
Line 15: [Warning] Invalid link: 'minibatch_size_in_samples'. The file Interpreting-epoch_size-and-minibatch_size_in_samples-and-MinibatchSource.next_minibatch-in-CNTK.md doesn't contain a bookmark named 'minibatchsizeinsamples'.
Line 16: [Warning] Invalid link: 'MinibatchSource.next_minibatch'. The file Interpreting-epoch_size-and-minibatch_size_in_samples-and-MinibatchSource.next_minibatch-in-CNTK.md doesn't contain a bookmark named 'minibatchSourcenextminibatch'.

articles/Setup-Linux-Python.md

Line 68: [Warning] Invalid link: 'PyPI'. The file Setup-Linux-Python.md doesn't contain a bookmark named 'installfrompypi'.
Line 222: [Warning] Invalid link: 'prerequisites above'. The file Setup-Linux-Python.md doesn't contain a bookmark named 'prerequisites'.
Line 284: [Warning] Invalid link: 'prerequisites above'. The file Setup-Linux-Python.md doesn't contain a bookmark named 'prerequisites'.

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


update image signing for 1.7

Signed-off-by: Jim Bugwadia<EMAIL_ADDRESS>Related issue
Add 1.7 image signing docs.
Fixes: https://github.com/kyverno/website/issues/512
Proposed Changes
Add 1.7 image signing docs.
Checklist

[x] I have read the contributing guidelines.
[x] I have inspected the website preview for accuracy.
[x] I have signed off my issue.

Preview at: https://deploy-preview-539--kyverno.netlify.app/docs/writing-policies/verify-images/


[Feature Request] Page Number Handling - Android

On iOS the page number is shown below. But it doesn't show in Android. How to handle page number indicator?

@M-HARIS-97 this sounds more like a feature than a bug. It is strange that it's not there, however.
For me, this one isn't a high priority so I'm going to prioritize it behind all the other features currently filed. I'd encourage you to take a look at the codebase and have a shot at a PR if it's important for you! I can give guidance along the way.

any updates regarding this issue @jspizziri  ?

@amalStorilabs still not high on my priority list. Happy to review a PR though.


Here's today's batch of dialyzer

I wanted to get a better type than epgsql:bind_param() but it's a direct consequence of the specific sqerl transformer we're using. Sqerl transformers make the whole thing more versatile, but I'm not up for the challenge of typing half of sqerl today

Lgtm :+1:

Other than the one eg/e comment, LGTM


Adds brew docs to close #13834

[X] Have you followed the guidelines in our Contributing document?
[X] Have you checked to ensure there aren't other open Pull Requests for the same change?
[X] Have you added an explanation of what your changes do and why you'd like us to include them?
[X] Have you written new tests for your changes? Here's an example.

Per the discussion in #13834, here's an MVP for opening docs in a browser.
Fixes #13834

Thanks so much for your first contribution!  You rock, @troymccabe!

🎉 Thanks for implementing my issue @troymccabe!


Get error when running run_workflow_template

Please confirm the following

[X] I agree to follow this project's code of conduct.
[X] I have checked the current issues for duplicates.
[X] I understand that ansible-rulebook is open source software provided for free and that I might not receive a timely response.

Bug Summary
run_workflow_template does not seem to work. When I do try and use it, I get the following error in daphne.log:
Nov 15 22:31:40 eda01 automation-eda-controller-daphne[821839]: 2023-11-16 03:31:40,839 ERROR    Exception inside application: ['“” value has an invalid format. It must be in YYYY-MM-DD HH:MM[:ss[.uuuuuu]][TZ] format.']
Nov 15 22:31:40 eda01 automation-eda-controller-daphne[821839]: Traceback (most recent call last):
Nov 15 22:31:40 eda01 automation-eda-controller-daphne[821839]:  File "/usr/lib/python3.9/site-packages/channels/routing.py", line 62, in __call__
Nov 15 22:31:40 eda01 automation-eda-controller-daphne[821839]:    return await application(scope, receive, send)
Nov 15 22:31:40 eda01 automation-eda-controller-daphne[821839]:  File "/usr/lib/python3.9/site-packages/channels/routing.py", line 116, in __call__
Nov 15 22:31:40 eda01 automation-eda-controller-daphne[821839]:    return await application(
Nov 15 22:31:40 eda01 automation-eda-controller-daphne[821839]:  File "/usr/lib/python3.9/site-packages/channels/routing.py", line 116, in __call__
Nov 15 22:31:40 eda01 automation-eda-controller-daphne[821839]:    return await application(
Nov 15 22:31:40 eda01 automation-eda-controller-daphne[821839]:  File "/usr/lib/python3.9/site-packages/channels/consumer.py", line 94, in app
Nov 15 22:31:40 eda01 automation-eda-controller-daphne[821839]:    return await consumer(scope, receive, send)
Nov 15 22:31:40 eda01 automation-eda-controller-daphne[821839]:  File "/usr/lib/python3.9/site-packages/channels/consumer.py", line 62, in __call__
Nov 15 22:31:40 eda01 automation-eda-controller-daphne[821839]:    await await_many_dispatch([receive], self.dispatch)
Nov 15 22:31:40 eda01 automation-eda-controller-daphne[821839]:  File "/usr/lib/python3.9/site-packages/channels/utils.py", line 50, in await_many_dispatch
Nov 15 22:31:40 eda01 automation-eda-controller-daphne[821839]:    await dispatch(result)
Nov 15 22:31:40 eda01 automation-eda-controller-daphne[821839]:  File "/usr/lib/python3.9/site-packages/channels/consumer.py", line 73, in dispatch
Nov 15 22:31:40 eda01 automation-eda-controller-daphne[821839]:    await handler(message)
Nov 15 22:31:40 eda01 automation-eda-controller-daphne[821839]:  File "/usr/lib/python3.9/site-packages/channels/generic/websocket.py", line 194, in websocket_receive
Nov 15 22:31:40 eda01 automation-eda-controller-daphne[821839]:    await self.receive(text_data=message["text"])
Nov 15 22:31:40 eda01 automation-eda-controller-daphne[821839]:  File "/usr/lib/python3.9/site-packages/aap_eda/wsapi/consumers.py", line 92, in receive
Nov 15 22:31:40 eda01 automation-eda-controller-daphne[821839]:    await self.handle_actions(ActionMessage.parse_obj(data))
Nov 15 22:31:40 eda01 automation-eda-controller-daphne[821839]:  File "/usr/lib/python3.9/site-packages/aap_eda/wsapi/consumers.py", line 135, in handle_actions
Nov 15 22:31:40 eda01 automation-eda-controller-daphne[821839]:    await self.insert_audit_rule_data(message)
Nov 15 22:31:40 eda01 automation-eda-controller-daphne[821839]:  File "/usr/lib/python3.9/site-packages/asgiref/sync.py", line 448, in __call__
Nov 15 22:31:40 eda01 automation-eda-controller-daphne[821839]:    ret = await asyncio.wait_for(future, timeout=None)
Nov 15 22:31:40 eda01 automation-eda-controller-daphne[821839]:  File "/usr/lib64/python3.9/asyncio/tasks.py", line 442, in wait_for
Nov 15 22:31:40 eda01 automation-eda-controller-daphne[821839]:    return await fut
Nov 15 22:31:40 eda01 automation-eda-controller-daphne[821839]:  File "/usr/lib64/python3.9/concurrent/futures/thread.py", line 58, in run
Nov 15 22:31:40 eda01 automation-eda-controller-daphne[821839]:    result = self.fn(*self.args, **self.kwargs)
Nov 15 22:31:40 eda01 automation-eda-controller-daphne[821839]:  File "/usr/lib/python3.9/site-packages/channels/db.py", line 13, in thread_handler
Nov 15 22:31:40 eda01 automation-eda-controller-daphne[821839]:    return super().thread_handler(loop, *args, **kwargs)
Nov 15 22:31:40 eda01 automation-eda-controller-daphne[821839]:  File "/usr/lib/python3.9/site-packages/asgiref/sync.py", line 490, in thread_handler
Nov 15 22:31:40 eda01 automation-eda-controller-daphne[821839]:    return func(*args, **kwargs)
Nov 15 22:31:40 eda01 automation-eda-controller-daphne[821839]:  File "/usr/lib/python3.9/site-packages/aap_eda/wsapi/consumers.py", line 204, in insert_audit_rule_data
Nov 15 22:31:40 eda01 automation-eda-controller-daphne[821839]:    audit_rule = models.AuditRule.objects.filter(
Nov 15 22:31:40 eda01 automation-eda-controller-daphne[821839]:  File "/usr/lib/python3.9/site-packages/django/db/models/manager.py", line 85, in manager_method
Nov 15 22:31:40 eda01 automation-eda-controller-daphne[821839]:    return getattr(self.get_queryset(), name)(*args, **kwargs)
Nov 15 22:31:40 eda01 automation-eda-controller-daphne[821839]:  File "/usr/lib/python3.9/site-packages/django/db/models/query.py", line 941, in filter
Nov 15 22:31:40 eda01 automation-eda-controller-daphne[821839]:    return self._filter_or_exclude(False, args, kwargs)
Nov 15 22:31:40 eda01 automation-eda-controller-daphne[821839]:  File "/usr/lib/python3.9/site-packages/django/db/models/query.py", line 961, in _filter_or_exclude
Nov 15 22:31:40 eda01 automation-eda-controller-daphne[821839]:    clone._filter_or_exclude_inplace(negate, args, kwargs)
Nov 15 22:31:40 eda01 automation-eda-controller-daphne[821839]:  File "/usr/lib/python3.9/site-packages/django/db/models/query.py", line 968, in _filter_or_exclude_inplace
Nov 15 22:31:40 eda01 automation-eda-controller-daphne[821839]:    self._query.add_q(Q(*args, **kwargs))
Nov 15 22:31:40 eda01 automation-eda-controller-daphne[821839]:  File "/usr/lib/python3.9/site-packages/django/db/models/sql/query.py", line 1416, in add_q
Nov 15 22:31:40 eda01 automation-eda-controller-daphne[821839]:    clause, _ = self._add_q(q_object, self.used_aliases)
Nov 15 22:31:40 eda01 automation-eda-controller-daphne[821839]:  File "/usr/lib/python3.9/site-packages/django/db/models/sql/query.py", line 1435, in _add_q
Nov 15 22:31:40 eda01 automation-eda-controller-daphne[821839]:    child_clause, needed_inner = self.build_filter(
Nov 15 22:31:40 eda01 automation-eda-controller-daphne[821839]:  File "/usr/lib/python3.9/site-packages/django/db/models/sql/query.py", line 1370, in build_filter
Nov 15 22:31:40 eda01 automation-eda-controller-daphne[821839]:    condition = self.build_lookup(lookups, col, value)
Nov 15 22:31:40 eda01 automation-eda-controller-daphne[821839]:  File "/usr/lib/python3.9/site-packages/django/db/models/sql/query.py", line 1216, in build_lookup
Nov 15 22:31:40 eda01 automation-eda-controller-daphne[821839]:    lookup = lookup_class(lhs, rhs)
Nov 15 22:31:40 eda01 automation-eda-controller-daphne[821839]:  File "/usr/lib/python3.9/site-packages/django/db/models/lookups.py", line 25, in __init__
Nov 15 22:31:40 eda01 automation-eda-controller-daphne[821839]:    self.rhs = self.get_prep_lookup()
Nov 15 22:31:40 eda01 automation-eda-controller-daphne[821839]:  File "/usr/lib/python3.9/site-packages/django/db/models/lookups.py", line 77, in get_prep_lookup
Nov 15 22:31:40 eda01 automation-eda-controller-daphne[821839]:    return self.lhs.output_field.get_prep_value(self.rhs)
Nov 15 22:31:40 eda01 automation-eda-controller-daphne[821839]:  File "/usr/lib/python3.9/site-packages/django/db/models/fields/__init__.py", line 1406, in get_prep_value
Nov 15 22:31:40 eda01 automation-eda-controller-daphne[821839]:    value = super().get_prep_value(value)
Nov 15 22:31:40 eda01 automation-eda-controller-daphne[821839]:  File "/usr/lib/python3.9/site-packages/django/db/models/fields/__init__.py", line 1266, in get_prep_value
Nov 15 22:31:40 eda01 automation-eda-controller-daphne[821839]:    return self.to_python(value)
Nov 15 22:31:40 eda01 automation-eda-controller-daphne[821839]:  File "/usr/lib/python3.9/site-packages/django/db/models/fields/__init__.py", line 1388, in to_python
Nov 15 22:31:40 eda01 automation-eda-controller-daphne[821839]:    raise exceptions.ValidationError(
Nov 15 22:31:40 eda01 automation-eda-controller-daphne[821839]: django.core.exceptions.ValidationError: ['“” value has an invalid format. It must be in YYYY-MM-DD HH:MM[:ss[.uuuuuu]][TZ] format.']

Here's my stanza:
    - name: Fiber Adapters
      condition: event.payload.event_tags.playbook is select("==", "Tune Fiber Adapters")
      action:
        run_workflow_template:
          name: Tune Fiber Adapters
          organization: Default
          job_args:
            extra_vars:
              key: "{{ event.payload.event_tags.key[0] }}"
              run: "{{ event.payload.host_host }}"
              context: "fiber"
              device: "{{ event.payload.event_tags.device[0] }}"
        ```

### Environment

[root@eda01 log]# ansible-rulebook --version
__version__ = '1.0.0'
  Executable location = /usr/bin/ansible-rulebook
  Drools_jpy version = 0.3.4
  Java home = /usr/lib/jvm/java-17-openjdk-<IP_ADDRESS>.9-2.el8.x86_64
  Java version = 17.0.9
  Python version = 3.9.16 (main, Sep 22 2023, 17:57:55) [GCC 8.5.0 20210514 (Red Hat 8.5.0-18)]

### Steps to reproduce

Create a workflow template with a few steps

Try and run it using EDA.

### Actual results

Error in daphne log.

### Expected results

It to run the workflow template job on AAP.

### Additional information

_No response_

Hi @Sudowojo, looking at the output of ansible-rulebook --version it seems you're running a very old version (v1.0.0) of rulebook. We added support for run_workflow_template in 1.0.2. Can you please update to the latest version and try again? pip install -U ansible-rulebook.

Ok, ansible-rulebook version should be bumped in an upcoming AAP release so best wait for that. For queries related to AAP, you can go via the support portal at https://access.redhat.com/support


The Bouncy Castle 1.51 removes the PGPSecretKey.extractPrivateKey(String)

Dear Sir,
The Bouncy Castle 1.51 removes the PGPSecretKey.extractPrivateKey(String) , it cause the License3j some exception as
java.lang.NoSuchMethodError: org.bouncycastle.openpgp.PGPSecretKey.extractPrivateKey([CLjava/lang/String;)Lorg/bouncycastle/openpgp/PGPPrivateKey;
at com.verhas.licensor.License.encodeLicense(License.java:482)
By overview I've googled and found some example coding at [1]. If I'm not wrong it may be as the following: -
        PGPSecretKey                key          = null;
        String                      pin          = null;
        PGPDigestCalculatorProvider calcProvider = null;
        PBESecretKeyDecryptor       decryptor    = null;
        PGPPrivateKey               pKey         = null;
        try {
            key          = //Loading key
            pin          = "some-pin";
            calcProvider = new JcaPGPDigestCalculatorProviderBuilder().
                                    setProvider(BouncyCastleProvider.PROVIDER_NAME).
                                    build();
            decryptor    = new JcePBESecretKeyDecryptorBuilder(calcProvider).
                                    setProvider(BouncyCastleProvider.PROVIDER_NAME).
                                    build(pin.toCharArray());
            pKey         = key.extractPrivateKey(decryptor);

        } catch (PGPException e) {
            // TODO Handle the exception
            e.printStackTrace();
        } finally {
            key          = null;
            pin          = null;
            calcProvider = null;
            decryptor    = null;
            pKey         = null;
        }

Could you please help to consider? Thank you very much for your help in advance. I'm looking forward to hearing from you soon.
Regards,
Charlee Ch.
[1] https://github.com/bcgit/bc-java/blob/master/pg/src/test/java/org/bouncycastle/openpgp/test/PGPUnicodeTest.java

Since this is an olc issue and the current version is using BC 1.52 I close this issue.


Fixes #25, #26, #29

Some of the tests I added failed on Windows due to slash differences, I fixed those issues and the tests now pass on my Windows machine.

Thanks @brl0! This looks good to me. Once those tests pass, I'll get this merged.

Thanks @andrewfulton9.  I just enabled workflows on my fork so I will be able to run tests there and I will post a message here once everything is passing.

@andrewfulton9, tests are passing now.

Thanks @brl0! Appreciate the work you put in here!