feat: adding at_repl to packages

- What I did

Created a Dart REPL. Published it onto pub.dev with atsign org  https://pub.dev/packages/at_repl
All of the instructions for installation/use are on pub.dev.
I retracted the latest version until the PR merges.

- Verify
If you guys could test it out it would be very helpful, Xavier C already found a glaring issue yesterday 🙃
- Description for the changelog
Created dart repl.

After reading  https://pub.dev/packages/at_repl I tried installing it via locally
This is how I installed it locally which worked for me
cd packages/at_repl
dart pub global activate .  --source path

I put in an incorrect atSign (that I do not have the keys to)
It did not read my keys
But it continued to put me in REPL
jeremytubongbanua@Jeremys-M2-Air ~ % at_repl -a @jeremy0 -r root.atsign.org:64 -v --no-enforceNamespace
Looking up secondary server address for @jeremy0 on root.atsign.org:64
Connecting...   Authentication failed: PathNotFoundException: Cannot open file, path =<EMAIL_ADDRESS>(OS Error: No such file or directory, errno = 2)
Disconnected, atClient is null.
You don't need to include name spaces.
@jeremy0 scan
Unhandled exception:
Exception: AtClient is null for some reason...
#0      REPL.executeCommand (package:at_repl/src/at_repl.dart:42:7)
#1      main (file:///Users/jeremytubongbanua/GitHub/at_tools/packages/at_repl/bin/at_repl.dart:144:39)
<asynchronous suspension>

In /help Typo?
regex (e.g. _scan<EMAIL_ADDRESS>
Should it be /scan not _scan ?

there is a known bug related to this ticket

Need to wait until the at_client changes get pushed to pub.dev

Need to wait until the at_client changes get pushed to pub.dev

Why?

Can you test with the at_client_sdk trunk branch and verify the issue has been fixed please?

@Xlin123 Once you've verified that the issue has been fixed, please approve this PR so I can publish at_client v 3.0.62

Nice work @Xlin123


Allow HelixClusterManager to adopt different implementations of ClusterChangeHandler

Introduced ClusterChangeHandler interface which allows different implementations.
Moved current ClusterChangeHandler to a separate class (SimpleClusterChangeHandler).
Rewrote some APIs in HelixClusterManager to aggregate cluster-wide infos from all ClusterChangeHandlers.

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@6a35e61). Click here to learn what that means.
The diff coverage is 88.42%.

@@            Coverage Diff            @@
##             master    #1344   +/-   ##
=========================================
  Coverage          ?   72.06%
  Complexity        ?     6601
=========================================
  Files             ?      480
  Lines             ?    37578
  Branches          ?     4751
=========================================
  Hits              ?    27079
  Misses            ?     9229
  Partials          ?     1270

Impacted Files
Coverage Δ
Complexity Δ

...thub.ambry.clustermap/CompositeClusterManager.java
61.42% <100%> (ø)
22 <0> (?)

...m.github.ambry.clustermap/HelixClusterManager.java
87% <84.21%> (ø)
57 <16> (?)

...b.ambry.clustermap/SimpleClusterChangeHandler.java
89.85% <89.85%> (ø)
48 <48> (?)

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 6a35e61...7bec796. Read the comment docs.


Form should check for incorrect reference formatting and not allow annotations to be made if references are not entered correctly

The proper format for references in a GO annotation is:
DB:accession_number
All values entered into the Reference field should be checked for that format and annotations should be flagged with an error message and not created in the model if the Reference entry does not conform to that syntax.
I will also add this same ticket to the Noctua tracker, as the graphical interface should have a check for this, as well.

@vanaukenk I have added the reference and with check 'DB:accession_number', However it doesn't further check if a particular DB exists or a particular accession_number exists. e.g. WRONG_DB:1234 will pass. Should I check this also? Is there a known list of Databases?

@vanaukenk - can this be closed now?


[Android] Text with dynamic width parent makes text stretch/compress

Description
So I have two skia text components beside each other horizontally and I want them to stay close. The text of the components are dynamic related to a graph. So I need the width of the text parent to change based on the text width.
This is a combination of reanimated parent view and skia text field. So might not be skia specific, but looks like it maybe. Or just me using this wrong 😊
Version
0.1.188
Steps to reproduce
Per now I do something like the provided example, an animated view from reanimated (3) outside, with a canvas + text from skia inside. The reanimated view uses an animated style, with changing width based on the text, which is a shared value.
This works nicely on iOS, the view resizes nicely and the text is shown as it should.

But on Android the text get compressed/stretched a lot when changing values.
The background resizes fine in as seen in the gif, but the text compresses/stretches

Snack, code example, screenshot, or link to a repository
    text: SharedValue<string>;
    fontSize: number;
    const lineHeight = fontSize * 1.4;
    const font = useFont(font, fontSize);

    const animatedStyle = useAnimatedStyle(() => {
        const newSize =
            (font?.getTextWidth(text.value) ?? 0) * offsetMultiplier;
        return {
            width: newSize,
            height: lineHeight,
        };
    });

    return (
        <Animated.View style={animatedStyle}>
            <Canvas
                style={{
                    flex: 1
               }}
            >
                <Text
                    text={text}
                    font={font}
                    y={fontSize}
                    x={0}
                />
            </Canvas>
        </Animated.View>
    );

We would definitely need a small standalone reproducible example here.

Sorry for being a bit slow on providing example, I created a example from the react native starter with only skia and reanimated added here: https://github.com/joarkosberg/SkiaTest .
Added just one text component width dynamic width, where iOS is fine and Android compresses/stretches. Might be a problem with my usage as well here, but in case it is a bug 😊
iOS test app:

Android test app:
device-2023-05-19-094649.webm

Oups, that looks bad 😅 Thanks for taking the time to make a reproducible example. Small question: would the same bug happens too with a circle for instance? Or is it only with Text?


safari browser history

hi @artehe  Our current library does not retrieve the history database and call history database. Is it possible to include the call history and Safari browser history databases in our backup functionality

If these database aren't in a normal iOS backup then it's possible that they are only included in an encrypted backup have you checked if they are in one of those?

@artehe  we have the option to encrypt the backup using our library?

Yes you can check if encryption is already enabled by querying lockdown doing something like this:
DictionaryNode? backupDomain = Lockdown.GetValue("com.apple.mobile.backup", null)?.AsDictionaryNode();
backupDomain?.TryGetValue("WillEncrypt", out PropertyNode? isEncryptedNode);
boolean isEncrypted = isEncryptedNode?.AsBooleanNode().Value ?? false;

Then if it isn't set you can enable it by setting a backup password using the Mobilebackup2Service.SetBackupPassword function. You can find about this here: https://github.com/artehe/Netimobiledevice/blob/aa671c3fb0915e60e98dd32e57afe94cc9ae9cdb/Netimobiledevice/Backup/Mobilebackup2Service.cs#L237


Fix Kinesis mailer template to display StreamName and change filter_type to list for Kinesis resource

The default template outputs the entire kinesis resource json object rather than the StreamName, fixed to display just the StreamName

Fixed the filter_type to be 'list'. According to Kinesis boto3 docs StreamNames is a list of strings, not dicts.

rerun with flake8 to fix syntax


String CONCAT Function

Search before asking

[X] I have searched the EvaDB issues and found no similar feature requests.

Description
The String CONCAT Function will help as compose queries in EvaDB
Use case
No response
Are you willing to submit a PR?

[ ] Yes I'd like to help by submitting a PR!

Duplicate of #1193


Enable enet client to setup a local port; fixes #15877

I tested it using my Bomber demo matchmaking server (https://github.com/henriquelalves/Godot-Bomber-matchmaking-server); I set up the server on an Azure VM and 'played' an online game using my smartphone 4G connection and my PC lan connection, which means NAT punching is effectively working. Without setting up the client port, online gaming (not LAN) is only possible by using Godot more low-level network api's (UDP packet or TCP stream).
It's kind of a hassle to test since you'd have to setup the node server on a not-local machine and compile the engine+android exports, but I'd love to know if this fix does work on other machines, or if there is some OS related issues I'm not accounting for here.
Used Android and Fedora 27.

CC @Faless

Without setting up the client port, online gaming (not LAN) is only possible by using Godot more low-level network api's (UDP packet or TCP stream).

Not entirely true, you just need the server (create_server) to have the port open on their NAT.
What is this PR achieving? Connecting two clients together (only create_client)?

Not entirely true, you just need the server (create_server) to have the port open on their NAT.
Exactly, I want to be able to connect two players without one of them having to set up their port open on their NAT by connecting both players to an intermediary server, and using their NAT port to communicate with each other. But this is only doable by using a known port on the client, instead of letting Godot use an arbitrary one. This is better explained on the repository (it's the NAT punching technique).

I think this would be worthwhile for peer-to-peer and NAT punchtrough implementations.
I tested this (after solving the conflicts locally) and it seems to work fine to punch trough, although I had to setup a AWS instance to test my local NAT. :)
@henriquelalves Can you resolve the conflicts? We added DNS resolution to create_client().

I tested this (after solving the conflicts locally) and it seems to work fine to punch trough

I'm glad you manage to get it working, I did try it a couple of time but never succeeded, I believe either my home connection or phone connection is behind a symmetric NAT preventing punch-through to work.
Since it seems to work with asymmetric NATs I would agree to merge once @henriquelalves rebases it.
There is one note though, Adding the parameter client_port like that will break compatibility, so either we add the parameter last, or we add an extra method set_client_port in the same fashion of set_bind_ip

IMO adding the parameter last is fine.

Fixed and merged as part of https://github.com/godotengine/godot/pull/18666.


How to handle optional dependencies to ported to a given host?

Example: strace optionally depends on libunwind, which hasn't yet been ported to RISC-V. Do we want the strace build expression to explicitly say optional libunwind.supportsTarget libunwind, or do we want the libunwind expression to simply be null on unsupported systems? Or is there another alternative?
@Ericson2314 @bgamari @dtzWill (we need @nixpkgs-cross...)

assert and tryEval, lolololol. In seriousness though, this is yet another excellent reason to peak at the meta of invalid derivations. Let's bring in @vcunat and the other meta check people.

C.f. https://github.com/NixOS/nixpkgs/pull/35111 and https://github.com/NixOS/nixpkgs/pull/33057

There is also an option to have requiredBuildInputs and optionalBuildInputs with the latter filtered through a platform-support check.
Of course, this will bring us really close to a point where we need a single buildInputs parameter with a possibility to add attributes native, optional etc.

@Ericson2314 I think you misunderstood: I'm not asking how we check if something is supported, I'm asking where we check. If we check at libunwind, then strace works out of the box but we silently lose features. If we check at strace, then we explicitly opt-out of the features but have to be more verbose.

@7c6f434c yeah, that's a good way to do this. @Ericson2314 can you fit that into your mkDerivation model?

Peeking at meta of invalid derivations works already.

@shlevy I was trying to answer that, just skipped a lot I guess.

We can't just make libunwind null across the board, because some packages might require it.

We don't want to make checking at strace too verbose.

Let's have our cake and eat it too:
# in lib
{
  optionalDep = dep: if dep.meta.available or false then dep else null;
}

# strace v1
{ stdenv, libunwind }:

stdenv.mkDerivation {
  buildInputs = [ (stdenv.lib.optionalDep libunwind) ];
}

# strace v2
{ stdenv
, supportUnwinding ? libunwind.meta.availible or false
, libunwind
}:

stdenv.mkDerivation {
  buildInputs = stdenv.lib.optional supportUnwinding libunwind;
}

Of course, this will bring us really close to a point where we need a single buildInputs parameter with a possibility to add attributes native, optional etc.

@7c6f434c yeah, that's a good way to do this. @Ericson2314 can you fit that into your mkDerivation model?

That's a fine idea, and it fits in that I don't see affecting the core model at all. As long as we do propagation in bash, We'll need to convert that to basically what we have anyways.

Cool, sounds good. I'll go with the optionalFoo approach until optionalInputs etc. is available.

optionalFoo is which approach? You mean making my library helper like that?

See also https://github.com/NixOS/nixpkgs/pull/34444 for making the meta checks work for cross.

Is it a good idea to (eventually) handle native-ness in the same way? Or propagation?

@7c6f434c I'm open to that. I mean I think of deps not in terms of the names but the two axes (see unstable nixpkgs manual), so the flattening that top-level attrs do is unfortunate. The limitations of bash mean that effectively we'll convert away from this stuff in the end so it must be just an easy superficial change.

@Ericson2314 so I'd have foo attribute and an optionalFoo attribute that is null on unsupported systems and thus can be safely added to inputs.
Speaking of limitations of bash... We may want to take advantage of __structuredAttrs = true here.
I'm definitely in favor of inputs being a list (set?) of packages with optional tags like buildTime = true and propagated = false if we can make that work nicely.

@shlevy errrr not to bikeshed, but I must say I like my optionalDep thing better. I don't think optionalFoo scales elegantly. If we end up making an optionalFoo attribute for every Linux-only package a Darwin package could use on Linux, for example, that's a lot of extra bloat in all-packages.nix.
CC @NixOS/darwin-maintainers

(Renamed because I don't see this as a cross-specific issue but general portability one. Reopened waiting on the darwin people's input more than my little bike-shed above.)

Right, that's better.

@Ericson2314 I wonder how to treat noarch packages in the two-axis model (for example, fonts — and yes, they are needed in the build time).

Oops, I guess, the hidden SLNOS agenda behind the sequence of #33057 and #35111 got uncovered :)
We had exactly the same discussion in SLNOS (without reaching a consensus).
I made the two aforementioned PRs to ease SLNOS (and, eventually, nixpkgs) into "optionalBuildInputs" route (yep, I confess, the use of .available in relatedPackages with which I pushed .available through review was an accidental revelation, not the original purpose, the original purpose of .available was exactly this issue).
As to the essence of issue, I do want them unsupported packages to be explicit because I hate to debug those optional nulls. You should try tracing null inputs in stdenv.mkDerivation and you are going to be surprised by how many overrides with nulls you already use. It's in hundreds (well, maybe less, as those traces do have lots of duplicates, still grep -r '= null' is pretty enormous).
They are especially hard to debug when using a package with a custom callPackage or overriding an already overridden package. Anything is better than nulls. I vote for anything except nulls. Explicitly filtering with filter (p: p.meta.available) is fine for me. To be honest, even "strace v2" from above and simple
buildInputs = [
  ...
]
++ optionals stdenv.isLinux [
  ...
]
++ optionals stdenv.isDarwin [
  ...
]

are fine. But I think most people will steer away from such things as they are too verbose. Hence, I vote for optionalBuildInputs. Anything but the nulls.
To be even more honest, now I'm unsure that even meta.available is good enough. It's too permissive with all its options of config.checkMeta, config.checkMetaRecursively and config.handleEvalIssue.
Now I'm experimenting with meta.supported that only checks the platforms (I also call optionalBuildInputs platformBuiltInputs, the name is subject to change, though).
As a side note, meta.platforms should be checked (or just autogenerated, or maybe both, maybe with config.checkMetaPlatforms or something) against platforms produced by intersecting platforms of derivations from buildInputs. But I have not implemented that properly yet.
As another side note, we could have meta.hostPlatforms or something, that describes platforms you can build the derivation on by doing the same for nativeBuildInputs.

Action item tracked in #36226

Unfortunately, null provides a way to quickly remove some dependencies without adding extra support into packages. USE flags require too many changes across the tree and will be hard to negotiate; also, a global override of null ensures that success does mean «no such packages is used», USE flags with Nixpkgs callPackage require active maintenance and vigilance.


Update README.md

Fixed example code because the old one did no longe match the lib requirements.

Please handle this super urgently. The component is unusable without this change in the docs.


Checkpointer: Support more types of serializable states using dill

This PR solves the PicklingError when using states with types that pickle doesn't support but dill does.

hi, @nadav-okami thanks for this, I'm making the serializer used by checkpoints configurable to more easily support this https://github.com/langchain-ai/langgraph/pull/305


Add leak detection API and module

This can be used to watch a reference when it is known to no longer be used, and to check whether or not it was collected by the Kotlin garbage collector or not.
Refs #2037

[ ] CHANGELOG.md's "Unreleased" section has been updated, if applicable.

It doesn't rely on Zipline either. I'm only testing with Zipline to confirm its behavior inside QuickJS (which is that it both doesn't have a mechanism to trigger GC and that it doesn't support WeakRef).
It can live in its own repository someday if we want.


🐛 Bug Report: scaffolder-backend-module-confluence-to-markdown action fails if confluence page title contains special characters

📜 Description
When running the action, if the page title contains any of the following ) ( , / [ ] ' : the execution will fail at the stage where the action tries to fetch the page here -> https://github.com/backstage/backstage/blob/master/plugins/scaffolder-backend-module-confluence-to-markdown/src/actions/confluence/confluenceToMarkdown.ts#L110
👍 Expected behavior
Submitting a valid confluence URL should convert the page and generate a PR
👎 Actual Behavior with Screenshots
When the page title contains special characters, the page conversion fails:
Sample URL:
https://squarespace.atlassian.net/wiki/spaces/REL/pages/38386107403/FAQ+In+30+Mins+Or+Less+Or+The+Deploy+s+Free
Actual page title:
FAQ: In 30 Mins Or Less, Or The Deploy's Free
Output:
2023-12-01T11:05:26.537Z InputError: Could not find document https://squarespace.atlassian.net/wiki/spaces/REL/pages/38386107403/FAQ+In+30+Mins+Or+Less+Or+The+Deploy+s+Free. Please check your input.
    5 at Object.handler (/usr/src/app/node_modules/@backstage/plugin-scaffolder-backend-module-confluence-to-markdown/dist/index.cjs.js:227:17)6    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)7       at async NunjucksWorkflowRunner.executeStep (/usr/src/app/packages/backend/node_modules/@backstage/plugin-scaffolder-backend/dist/cjs/router-68c854a3.cjs.js:7233:9)8    at async NunjucksWorkflowRunner.execute (/usr/src/app/packages/backend/node_modules/@backstage/plugin-scaffolder-backend/dist/cjs/router-68c854a3.cjs.js:7306:9)9    at async TaskWorker.runOneTask (/usr/src/app/packages/backend/node_modules/@backstage/plugin-scaffolder-backend/dist/cjs/router-68c854a3.cjs.js:7528:26)10    at async run (/usr/src/app/node_modules/p-queue/dist/index.js:163:29)

👟 Reproduction steps

Create a page in confluence where the title contains one of the following chars ) ( , / [ ] ' :
Use the URL of the newly created page with the action

📃 Provide the context for the Bug.
A simple alternative that would help mitigate the error would be to get as input instead of the url with the page title, only the page ID. For example:
This URL -> https://squarespace.atlassian.net/wiki/rest/api/content?id={id}&expand=body.export_view
Will return the same as https://squarespace.atlassian.net/wiki/rest/api/content?title=${title}&spaceKey=${spacekey}&expand=body.export_view
🖥 Your Environment
OS:   Darwin 22.6.0 - darwin/arm64
node: v18.17.1
yarn: 1.22.19
cli:  0.23.1 (installed)
backstage:  1.19.5

Dependencies:
  @backstage/app-defaults                                          1.4.4
  @backstage/backend-app-api                                       0.5.7
  @backstage/backend-common                                        0.19.8
  @backstage/backend-dev-utils                                     0.1.2
  @backstage/backend-openapi-utils                                 0.0.5
  @backstage/backend-plugin-api                                    0.6.6
  @backstage/backend-tasks                                         0.5.11
  @backstage/catalog-client                                        1.4.5
  @backstage/catalog-model                                         1.4.3
  @backstage/cli-common                                            0.1.13
  @backstage/cli-node                                              0.1.5
  @backstage/cli                                                   0.22.14, 0.23.1
  @backstage/config-loader                                         1.5.2
  @backstage/config                                                1.1.1
  @backstage/core-app-api                                          1.11.0
  @backstage/core-components                                       0.11.2, 0.12.5, 0.13.6
  @backstage/core-plugin-api                                       1.7.0
  @backstage/dev-utils                                             1.0.22
  @backstage/e2e-test-utils                                        0.1.0
  @backstage/errors                                                1.2.3
  @backstage/eslint-plugin                                         0.1.3
  @backstage/frontend-app-api                                      0.2.0
  @backstage/frontend-plugin-api                                   0.2.0
  @backstage/integration-aws-node                                  0.1.7
  @backstage/integration-react                                     1.1.20
  @backstage/integration                                           1.7.1
  @backstage/plugin-api-docs                                       0.9.12
  @backstage/plugin-app-backend                                    0.3.54
  @backstage/plugin-app-node                                       0.1.6
  @backstage/plugin-auth-backend-module-gcp-iap-provider           0.2.0
  @backstage/plugin-auth-backend-module-github-provider            0.1.3
  @backstage/plugin-auth-backend-module-gitlab-provider            0.1.3
  @backstage/plugin-auth-backend-module-google-provider            0.1.3
  @backstage/plugin-auth-backend-module-oauth2-provider            0.1.3
  @backstage/plugin-auth-backend                                   0.19.4
  @backstage/plugin-auth-node                                      0.4.0
  @backstage/plugin-catalog-backend-module-github                  0.4.4
  @backstage/plugin-catalog-backend-module-scaffolder-entity-model 0.1.3
  @backstage/plugin-catalog-backend                                1.14.0
  @backstage/plugin-catalog-common                                 1.0.17
  @backstage/plugin-catalog-graph                                  0.2.37
  @backstage/plugin-catalog-import                                 0.10.1
  @backstage/plugin-catalog-node                                   1.4.7
  @backstage/plugin-catalog-react                                  1.8.5
  @backstage/plugin-catalog                                        1.14.0
  @backstage/plugin-events-backend-module-github                   0.1.16
  @backstage/plugin-events-backend                                 0.2.15
  @backstage/plugin-events-node                                    0.2.15
  @backstage/plugin-explore-common                                 0.0.2
  @backstage/plugin-explore-react                                  0.0.32
  @backstage/plugin-explore                                        0.4.11
  @backstage/plugin-gcalendar                                      0.3.19
  @backstage/plugin-github-actions                                 0.6.6
  @backstage/plugin-graphiql                                       0.2.55
  @backstage/plugin-home-react                                     0.1.4
  @backstage/plugin-home                                           0.5.9
  @backstage/plugin-kubernetes-backend                             0.13.0
  @backstage/plugin-kubernetes-common                              0.7.0
  @backstage/plugin-kubernetes-node                                0.1.0
  @backstage/plugin-kubernetes-react                               0.1.0
  @backstage/plugin-kubernetes                                     0.11.0
  @backstage/plugin-lighthouse-common                              0.1.4
  @backstage/plugin-lighthouse                                     0.4.10
  @backstage/plugin-org                                            0.6.15
  @backstage/plugin-pagerduty                                      0.6.6
  @backstage/plugin-permission-common                              0.7.9
  @backstage/plugin-permission-node                                0.7.17
  @backstage/plugin-permission-react                               0.4.16
  @backstage/plugin-proxy-backend                                  0.4.4
  @backstage/plugin-scaffolder-backend                             1.18.1
  @backstage/plugin-scaffolder-common                              1.4.2
  @backstage/plugin-scaffolder-node                                0.2.7
  @backstage/plugin-scaffolder-react                               1.5.6
  @backstage/plugin-scaffolder                                     1.15.1
  @backstage/plugin-search-backend-module-catalog                  0.1.10
  @backstage/plugin-search-backend-module-pg                       0.5.15
  @backstage/plugin-search-backend-module-techdocs                 0.1.10
  @backstage/plugin-search-backend-node                            1.2.10
  @backstage/plugin-search-backend                                 1.4.6
  @backstage/plugin-search-common                                  1.2.7
  @backstage/plugin-search-react                                   1.7.1
  @backstage/plugin-search                                         1.4.1
  @backstage/plugin-sonarqube-backend                              0.2.8
  @backstage/plugin-sonarqube-react                                0.1.9
  @backstage/plugin-sonarqube                                      0.7.7
  @backstage/plugin-tech-radar                                     0.6.9
  @backstage/plugin-techdocs-backend                               1.8.0
  @backstage/plugin-techdocs-module-addons-contrib                 1.1.1
  @backstage/plugin-techdocs-node                                  1.9.0
  @backstage/plugin-techdocs-react                                 1.1.12
  @backstage/plugin-techdocs                                       1.8.0
  @backstage/plugin-user-settings                                  0.7.11
  @backstage/plugin-xcmetrics                                      0.2.44
  @backstage/release-manifests                                     0.0.10
  @backstage/test-utils                                            1.4.4
  @backstage/theme                                                 0.2.19, 0.4.3
  @backstage/types                                                 1.1.1
  @backstage/version-bridge                                        1.0.6

👀 Have you spent some time to check if this bug has been raised before?

[X] I checked and didn't find similar issue

🏢 Have you read the Code of Conduct?

[X] I have read the Code of Conduct

Are you willing to submit PR?
No, I don't have time to work on this right now

Thanks for raising this! Is this something that you would like to contribute a fix for? :pray:

I created a page with special characters in my confluence. When linking to it within confluence it does direct you to use to the page id instead of a friendly URI as you pointed out:

If I URL encode the friendly url though (%5BTest%20Page%5D) confluence is able to route the page:

API responds similarly.. would URL encoding previous to the fetch request be a reasonable/friction-less modification here? Or maybe I don't understand the failure setup you have. I would have expected the URL to either be in the confluence pageid format or attempt to url encode it. The sample URL seems to be missing the : altogether based on the title. Perhaps there is a setting in confluence for that I am missing.

@Thutm I did some testing and it seems the issue is caused indeed by a confluence behaviour. By the look of things, not something we have implemented as custom extension but the URL of our pages displayed in the browser is different from the URL in the webui field.
for example:
Page TItle: FAQ: In 30 Mins Or Less, Or The Deploy's Free
URL in Browser: /FAQ+In+30+Mins+Or+Less+Or+The+Deploy+s+Free
URL from webui field in json version of the page: /FAQ%3A+In+30+Mins+Or+Less%2C+Or+The+Deploy%27s+Free
The one in webui has the correct encoding, but there must be some feature in Confluence that generates a more human readable URL for the browser.
I think at this point this issue should no longer be considered a bug, since the action does the conversion correctly when the right input is provided.
I'd still like to send some sort of feature request where we can pass as input the pageID that seems a more consistent parameter.

Its interesting that confluence would interpret and display the pretty URI to user but API doesn't understand how to make the same connection. I agree though if that is the behavior likely easiest to give backstage users the option to submit a pageid instead, at leas they could self resolve when they run into this case. Confluence seems to force the pageid URI anyway if the page title is complex enough (i.e. includes other special characters I guess?).


Duplicate symbols error on OSX

If I do
go install github.com/mattn/go-sqlite3

or
go get github.com/mattn/go-sqlite3

Then I get a long list of similar errors:
....
duplicate symbol _sqlite3_prepare16_v2 in:
$WORK/github.com/mattn/go-sqlite3/_obj/sqlite3-binding.o
$WORK/github.com/mattn/go-sqlite3/_obj/sqlite3.o

And then at the end:
ld: 201 duplicate symbols for architecture x86_64

Any idea what is happening and how this can be solved ?
go version
go version go1.5.1 darwin/amd64
gcc -v
Configured with: --prefix=/Applications/Xcode.app/Contents/Developer/usr --with-gxx-include-dir=/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.11.sdk/usr/include/c++/4.2.1
Apple LLVM version 7.0.0 (clang-700.1.76)
Target: x86_64-apple-darwin15.2.0
Thread model: posix

I cannot reproduce it. Can we close it?

Yes.

I deleted the $GOPATH/src/github.com/mattn/go-sqlite3 folder and then installed it again. That solved the problem.


remove_reference => decay

According to the Library TS
http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2015/n4529.html#optional.object.assign
The assignment operator C++ template <class U> optional<T>& operator=(U&& v);  shall not participate in overload resolution unless  C++ is_same_v<decay_t<U>, T>  is true.
The current reference implementation however uses remove_reference and not decay:
 template <class U>
  auto operator=(U&& v)
  -> typename enable_if
  <
    is_same<typename remove_reference<U>::type, T>::value,
    optional&
  >::type

Fixed


stateful random ops, fix crash for empty output

Fix #51803 for stateful random ops.

Hi @albertz Can you please check @cheshire's comments and keep us posted ? Thank you!

Yes I will try to do in the next week's.

Hi @albertz Any update on this PR? Please. Thank you!

I'm not really familiar with the tests. How would I add a test which runs only with CUDA? Where would I add it?

Hi @cheshire Can you please assist on above comments from @albertz. Thank you!

Hi @cheshire Any update on this PR? Please. Thank you!

Hi @cheshire Any update on this PR? Please. Thank you!

Hi @cheshire Any update on this PR? Please. Thank you!

Hi @cheshire Any update on this PR? Please. Thank you!

Hi @cheshire Any update on this PR? Please. Thank you!

Hi @cheshire Any update on this PR? Please. Thank you!

Hi @cheshire Any update on this PR? Please. Thank you!

Hi @cheshire Any update on this PR? Please. Thank you!

Hi @cheshire Any update on this PR? Please. Thank you!

Hi @cheshire , Any update on this PR? Please. Thank you!

Hi @cheshire , Any update on this PR? Please. Thank you!

Hi @cheshire , Any update on this PR? Please. Thank you!

Hi @cheshire , Any update on this PR? Please. Thank you!

Hi @cheshire , Any update on this PR? Please. Thank you!

Hi @cheshire , Any update on this PR? Please. Thank you!

Hi @cheshire , Any update on this PR? Please. Thank you!

Hi @cheshire , Any update on this PR? Please. Thank you!


test 7

product: unspecified

PRMergerTest3 is not a member of prmergertest organization, therefore is automatically removed from issue assignee list.

PRMergerTest3 is not a member of prmergertest organization, therefore is automatically removed from issue assignee list.


D3D12CreateDevice requires Win32_Graphics_Direct3D11

I would've assumed this was a win32metadata issue, but I can't seem to find the cause of this in win32metadata, so posting it here. If it needs to move, let me know.
However it looks like Win32_Graphics_Direct3D11 is required for D3D12CreateDevice because of the D3D_FEATURE_LEVEL enum which is slightly unfortunate (since it's the only thing that seems to require it).
In the regular C++ headers, these enums are defined in d3dcommon.h so they can be shared between versions.
(In looking through this, I also noticed D3D11On12CreateDevice is behind the 12 feature toggle, which seems slightly odd too, I'd expect it to only need 11).

Yes, I believe this is a metadata issue. Will transfer.
I think @damyanp and @sotteson1 have done some work to clean this up but they can confirm. As soon as a build is available with their changes I can ingest into the Windows crate.


Feature Request: Track which screen to display windows on

It'd be neat if, when I press the [Restart] button, Atom restarted on the same monitor that it was on, in the same place even.  Sometimes I have 2 editor windows on different screens. It'd be nice if Atom tracked all of the display-related information.

I'd like to either work on this feature request or pair with someone who wants to take it on.

This looks like a duplicate of #6268.
@LauraAubin Great to hear!  You might be able to find someone else in #6268, and there's also some advice at the bottom of that issue.


Why doesn't Update-MarkdownHelpModule have the UseFullTypeName switch

Why doesn't Update-MarkdownHelpModule have the UseFullTypeName switch, as with New-MarkdownHelp & Update-MarkdownHelp?
Had a look at Update-MarkdownHelpModule and it looks pretty strait forward

indeed - this is just an oversight. Should be pretty easy to fix - please feel free to send a PR for that!

Added one! https://github.com/PowerShell/platyPS/pull/380 - let me know if I need to do anything except update the code itself.

This may already be fixed in Microsoft.PowerShell.PlatyPS. Need to test.


{Doc} Add local context developer guidelines

Description
local context developer guidelines
Testing Guide
No
History Notes

[Component Name 1] BREAKING CHANGE: az command a: Make some customer-facing breaking change.
[Component Name 2] az command b: Add some customer-facing feature.

This checklist is used to make sure that common guidelines for a pull request are followed.

[ ] The PR title and description has followed the guideline in Submitting Pull Requests.

[ ] I adhere to the Command Guidelines.

local context developer guidelines


[Content Fragment] Fill textUrl/textBytes/textTokens appropriately

Spinned off #4240

https://github.com/dust-tt/dust/issues/4240#issuecomment-2014728899


SIP: Admin API

Ref: #528
My first SIP! Please let me know how it looks.
Rendered
Signed-off-by: Mitchell Hynes<EMAIL_ADDRESS>

I rewrote the Spin Admin API SIP to be based around a new WASI based FS interface instead.
I'm not happy with the design, but if it was implemented in its current state it would serve my purposes.
Overall, I'd like to keep it as simple as possible. The interface I have for logs and the manifest suits me fine, maybe the persisting to disk part could be kicked down the road for later.

I left the original commit for posterities sake :)

Thanks for the thoughtful input, updated!

Could you describe what the Spin workflow/experience would look like for a user to access their logs?

Sure! When the flag is enabled, this directory is mounted to the host component:
tree /.spin/
└── logs
    └── [componentname]
        ├── stderr.txt
        └── stdout.txt

You can access this through WASI File Descriptors, which is just like reading any other file. This directory differs from if you were to mount your app's directory (~/.spin/[appname]) because the files are updated in realtime.


Re-organize docs for better usability

For a while we've been piling docs into existing topics which make them difficult to find. Also the list of topics have grown and should be organized so the reader can more easily find what they're looking for.
The problems I see:

There are too many items in Other information. This should be the last place people look for answers.
Extra software is as well, too long. Also I expect this to be related to installed_extras, while it actually contains tons of other things.
Vagrantfile.local is too well hidden
Drupal VM as a Composer Dependency should probably be brought to readers attention more
Currently there's not much order in which you're supposed to read through the docs.

A first draft with some of my thoughts:

Getting Started

How to configure Drupal VM
Vagrant synced folders

Building your codebase:
(This is probably the most common thing users want to understand.)

A local Drupal codebase
Using composer.json
Using a composer package
Using a Drush Make file
Drupal VM as a Composer Dependency
(I feel this should be more visible in the docs)

Basic configurations:
(Second most common thing would be webserver/database/php. Maybe this could be merged with Getting Started.)

Using different Ubuntu/Centos base OSes
Using other versions of PHP
Webservers:

Using Apache
Using Nginx
SSL VirtualHosts

Databases:

Connect to the MySQL Database
Use MariaDB instead of MySQL
Use PostgreSQL instead of MySQL

Installed Extras:
(Idea is that this matches installed_extras variable)

Adminer: Connect to the database
Drush
Drupal Console
MailHog: Catching Emails
Node.js and NPM
Pimp My Log: View server logs
Selenium: Testing with Behat and Selenium
Solr: For search
Varnish
XDebug: Debug Code
XHProf, Blackfire, XDebug: Profiling code

Advanced Configuration:

Overriding with local.config.yml, vagrant.config.yml, prod.config.yml files
Extending Vagrantfile with Vagrantfile.local
Passing on CLI arguments to ansible
Pre- and Post-Provision Scripts

Vagrant troubleshooting:
(If I used linux/windows and wanted to debug I would look for a troubleshooting section)

Linux
Windows
Networking
Vagrant and VirtualBox Tips

Other Information:

BigPipe with Drupal VM
Drupal multisite
Drupal 6 Notes
Drupal VM Management Tools
Deploying to a production environment

@geerlingguy maybe you can ask on twitter what actual Drupal VM users found difficult/illogical about the docs?

@oxyc - 140 characters is a little rough, but here we go: https://twitter.com/geerlingguy/status/814871272400318464

(I'm also thinking about doing a brief survey to see how users are using Drupal VM sometime, like a Google Forms form to fill out, or SurveyMonkey.)

How about making Getting started into a page, not just a section heading.

Getting Started

Installation

Mac OSX
Linux
Windows

How to configure Drupal VM
Vagrant synced folders

Getting started
Read the quick start guide.... link.
Installation steps/instructions for windows (link), osx, linux (..)
Subpage: Mac OSX
Video
Subpage: Linux
Same OSX video
Move the Platform-specific Install Instructions docs from Linux Notes here.
Subpage: Windows
Video
Move Windows Subsystem for Linux / Ubuntu bash and Command line environment from Windows Notes.

Maybe move all those notes into these sections? Or maybe keep troubleshooting/configugration options separated but end the Getting started section with clear links to the possible issues.

I like that... much more clear for a newcomer. And I can work on the videos soon, and do one for Ubuntu, one for macOS, and another for Windows.

@geerlingguy is it better to keep the quick start guide in the README or should we move it to docs instead?

@oxyc - That's a good question. I kinda like it in the README just because I know I usually skip a project's docs site and head straight through the README to hopefully get off the ground. But we could trim down the README by putting it in the docs, and focus the README on getting people to the right place, quickly.

@oxyc - I'll try to take a look at docs overall with a goal of merging this work by the end of the month. Now that search is working, the only main concern I have is that existing links from many places will get broken (I wish it were possible to set up 301/302s in RTD...).

@geerlingguy if we change the structure entirely (as with the current suggestion) we could keep the old files but add meta redirect tags as their only content.

The meta refresh is a directive in the header of a document indicating that, after a certain quantity of time is passed, the browser should redirect to a new location (or reload the page). Search engines appear to treat most short meta refreshes (a few seconds in length) as permanent redirects, passing the link equity and ranking metrics to the target page (they also claim to do this 100% of the time for meta refreshes marked with "0" seconds of delay).
https://moz.com/blog/answers-to-the-seo-professionals-litmus-test

http://sebastians-pamphlets.com/google-and-yahoo-treat-undelayed-meta-refresh-as-301-redirect/

@oxyc - Would that work while not affecting the new structure in RTD? I imagine we could leave the old files a few months then remove them in a follow up.

Darn, I guess not. https://github.com/mkdocs/mkdocs/issues/699 mkdocs really does not like me.

Shucks :(

@geerlingguy anything you want me to start working on?

Additions that have come up in other issues recently:

Could we add a paragraph in the docs, along the lines of "this is how to setup DrupalVM for contributing to core"?
https://github.com/geerlingguy/drupal-vm/issues/1116#issuecomment-272159320

Definitely useful. Could reference both https://github.com/thom8/drupal8-vagrant and @geerlingguy workflow as some examples.

Add drupalvm_cron_jobs to documentation.
https://github.com/geerlingguy/drupal-vm/issues/1110

I think this would be good to have available somewhere in the docs so you something is found when you search for cron. I dont necessarily think it needs its own section as it is pretty straight forward and clear in the default.config.yml. The issue is you dont find anything when searching for it in the docs. @geerlingguy mentioned interest in adding support for letsencrypt eventually. Maybe this could qualify as we obviously would want to add a cron task for renewing the certificates.

@oxyc - I'm kinda willing to say 'screw it' to all the existing URLs and just merge your PR and go from there :)
Now that search is working, I'm not as opposed to breaking URLs, and technically I could proxy the site and manage redirects through my own reverse proxy or something (since I control the DNS)... but instead I think we could just switch to what's in your PR and go from there.
Do you want to give it another once-over and then I'll merge today sometime?

The PR is pretty outdated by now, but if you think the outline I have above is good, I can start working on it.

Also, do you prefer if I just restructure and leave addition/changes for another PR or should I just open up a "Change all the things!"-PR? :D

@oxyc - Change all the things!


BlFileImageElement Freezes Image w ZeroDivide

This is the error I reported on Discord, @girba. It seems to be a problem with BlFileImageElement , which was created via GtFileUtility imageElementFromFileReference: self imageFile. The error triggers intermittently as I work with the image and requires me to force quit the image. In fact, the debugger doesn't even come up completely, just a blank window.

ZeroDivide
12 September 2020 8:03:34.558959 am

VM: Mac OS - x86_64 - 1000 - CoInterpreterWithQueueFFI * VMMaker-tonel.1 uuid: f993c393-bd64-0d00-b1c2-ba1901178a91 Jun 18 2020
StackToRegisterMappingCogit * VMMaker-tonel.1 uuid: f993c393-bd64-0d00-b1c2-ba1901178a91 Jun 18 2020
5f7d492 - Commit: 5f7d492 - Date: 2020-06-18 16:30:44 +0300

Image: Pharo8.0.0 [Build information: Pharo-8.0.0+build.1141.sha.1b7a8d8203fce2a57794451f555bba4222614081 (64 Bit)]

SmallFloat64>>/
	Receiver: 797.0
	Arguments and temporary variables:
		aNumber:
	Receiver's instance variables:
797.0

BlFileImageElement(BlAsyncImageElement)>>drawOnSpartaCanvas:
	Receiver: BlFileImageElement @ 323523840
	Arguments and temporary variables:
		aCanvas: 	a SkiaCanvas
		ratio: 	nil
		imageExtent: 	nil
		translation: 	nil
		image: 	a SkiaImage((void*)@ 16r00000000
	Receiver's instance variables:
		spaceReference: 	a BlAttachedCachedSpaceReference
		parent: 	BlLazyElement @ 987674112
		children: 	Children array (0)
		bounds<EMAIL_ADDRESS>corner<EMAIL_ADDRESS>		measuredBounds<EMAIL_ADDRESS>corner<EMAIL_ADDRESS>		boundsCache: 	a BlBoundsCache
		eventDispatcher: 	Bubbling event dispatcher for BlFileImageElement @ 323523840
		shouldHandleMouseEvents: 	true
		shouldChildrenHandleMouseEvents: 	true
		constraints: 	a BlLayoutCommonConstraints
		layout: 	a BlBasicLayout
		changes: 	a BlElementChanges
		transformation: 	a BlElementLocalTransformation
		taskQueue: 	a BlTaskQueue
		errorHandler: 	a BlCompositeErrorHandler
		needsPaint: 	true
		userData: 	an IdentityDictionary(#phlow->a GtPhlowElementContext )
		visuals: 	a BlDefaultVisuals
		priority: 	nil
		visibleElement: 	nil
		taskitRunner: 	nil
		previewStrategy: 	a BlAsyncNoPreviewStrategy
		updateStrategy: 	a BlUpdateWhenVisibleStrategy
		errorText: 	'Unable to decode {temp}//tmp/pharo-tempfile/2020-09-10T212835955253...etc...
		exception: 	nil
		errorStencil: 	nil
		entry: 	a BlImageCacheEntry
		preLoad: 	nil
		file: 	File @ /tmp/pharo-tempfile/2020-09-10T212835955253-0400_rlpdf-001-000.jpg...etc...

Can we bump this, @girba? I just lost an entire image to this. Every time I restart, it immediately gives this error.

thank you for reporting this 👍

Thanks for the fix! This was a scary one


Remote App not working with any GFX commandline

@akallabeth
Freerdp Master GIt version remote app,
Also tried with freerdp-nightly-dbg_2.0.0+0~20170110024932.323~1.gbp8fd926_i386.deb	but same result.
ubuntu@ubuntu:~/FreeRDP_Github$ xfreerdp /buildconfig
[11:10:11:801] [6162:6162] [INFO][com.freerdp.utils] - Registering signal hook...
This is FreeRDP version 2.0.0-dev (git 90877f5)
Build configuration: BUILD_TESTING=OFF BUILTIN_CHANNELS=OFF HAVE_AIO_H=1 HAVE_EVENTFD_H=1 HAVE_EXECINFO_H=1 HAVE_FCNTL_H=1 HAVE_INTTYPES_H=1 HAVE_MATH_C99_LONG_DOUBLE=1 HAVE_POLL_H=1 HAVE_PTHREAD_MUTEX_TIMEDLOCK=ON HAVE_PTHREAD_MUTEX_TIMEDLOCK_LIB=1 HAVE_PTHREAD_MUTEX_TIMEDLOCK_SYMBOL= HAVE_SYSLOG_H=1 HAVE_SYS_FILIO_H= HAVE_SYS_MODEM_H= HAVE_SYS_SELECT_H=1 HAVE_SYS_SOCKIO_H= HAVE_SYS_STRTIO_H= HAVE_TIMERFD_H=1 HAVE_TM_GMTOFF=1 HAVE_UNISTD_H=1 HAVE_XI_TOUCH_CLASS=1 WITH_ALSA=ON WITH_CHANNELS=ON WITH_CLIENT=ON WITH_CLIENT_AVAILABLE=1 WITH_CLIENT_CHANNELS=ON WITH_CLIENT_CHANNELS_AVAILABLE=1 WITH_CLIENT_COMMON=ON WITH_CLIENT_INTERFACE=OFF WITH_CUPS=ON WITH_DEBUG_ALL=OFF WITH_DEBUG_CAPABILITIES=OFF WITH_DEBUG_CERTIFICATE=OFF WITH_DEBUG_CHANNELS=OFF WITH_DEBUG_CLIPRDR=OFF WITH_DEBUG_DVC=OFF WITH_DEBUG_KBD=OFF WITH_DEBUG_LICENSE=OFF WITH_DEBUG_MUTEX=OFF WITH_DEBUG_NEGO=OFF WITH_DEBUG_NLA=OFF WITH_DEBUG_NTLM=OFF WITH_DEBUG_RAIL=OFF WITH_DEBUG_RDP=OFF WITH_DEBUG_RDPEI=OFF WITH_DEBUG_REDIR=OFF WITH_DEBUG_RFX=OFF WITH_DEBUG_RINGBUFFER=OFF WITH_DEBUG_SCARD=OFF WITH_DEBUG_SND=OFF WITH_DEBUG_SVC=OFF WITH_DEBUG_SYMBOLS=OFF WITH_DEBUG_THREADS=OFF WITH_DEBUG_TIMEZONE=OFF WITH_DEBUG_TRANSPORT=OFF WITH_DEBUG_TSG=OFF WITH_DEBUG_TSMF=OFF WITH_DEBUG_WND=OFF WITH_DEBUG_X11=OFF WITH_DEBUG_X11_CLIPRDR=OFF WITH_DEBUG_X11_LOCAL_MOVESIZE=OFF WITH_DEBUG_XV=OFF WITH_DIRECTFB=OFF WITH_EVENTFD_READ_WRITE=1 WITH_FFMPEG=ON WITH_GPROF=OFF WITH_GSM=OFF WITH_GSTREAMER_0_10=ON WITH_GSTREAMER_1_0=OFF WITH_IPP=OFF WITH_JPEG=ON WITH_LIBAVCODEC=ON WITH_LIBRARY_VERSIONING=ON WITH_LIBSYSTEMD=OFF WITH_MACAUDIO=OFF WITH_MACAUDIO_AVAILABLE=0 WITH_MANPAGES=OFF WITH_MBEDTLS=OFF WITH_OPENH264=ON WITH_OPENSLES=OFF WITH_OPENSSL=ON WITH_OSS=OFF WITH_PCSC=OFF WITH_PROFILER=OFF WITH_PULSE=OFF WITH_SAMPLE=OFF WITH_SANITIZE_ADDRESS=OFF WITH_SANITIZE_ADDRESS_AVAILABLE=1 WITH_SANITIZE_LEAK=OFF WITH_SANITIZE_LEAK_AVAILABLE=1 WITH_SERVER=OFF WITH_SERVER_INTERFACE=ON WITH_SMARTCARD_INSPECT=OFF WITH_SSE2=ON WITH_THIRD_PARTY=OFF WITH_VALGRIND_MEMCHECK=OFF WITH_VALGRIND_MEMCHECK_AVAILABLE=1 WITH_WAYLAND=OFF WITH_X11=ON WITH_X264=OFF WITH_XCURSOR=ON WITH_XEXT=ON WITH_XFIXES=ON WITH_XI=ON WITH_XINERAMA=ON WITH_XKBFILE=OFF WITH_XRANDR=ON WITH_XRENDER=ON WITH_XSHM=ON WITH_XV=ON WITH_ZLIB=ON
Build type:          Release
CFLAGS:               -march=i686 -Wall -Wno-unused-result -Wno-unused-but-set-variable -Wno-deprecated-declarations -fvisibility=hidden -Wimplicit-function-declaration -Wredundant-decls -msse2
Compiler:            GNU,
Target architecture: x86

Below is the scenario to reproduce the issue:-
1:-Take Remote session of Windows 2012R2 with below command line using ssh
xfreerdp /cert-ignore +compression -toggle-fullscreen /title:xx  /bpp:16 /f /gfx /sound:quality:dynamic /microphone  -wallpaper +fonts /kbd:0x00000409 "/app:||Skype" /d:xxxx /u:xxx /p:xxxx /v:x.x.x.x
2:- now skype will launch with black screen
Note:-skype need to be publish as remote app on 2012R2 server.
Refer :- http://www.kimknight.net/remoteapptool
Thanks & Regards,
Ganesh Kale

We see this black screen when we share desktop from pidgin-sipe to Windows 7/10

both xfreerdp and Remmina causes black screen. I am sure this worked at some point but that could
have been long ago.

@joakim-tjernlund There is a number of issues pending with regard to remote app. Does this behavior only occur with /gfx or also with /bpp:xxor /rfx?

There are flags for Enhanced RemoteApp which is Remoteapp and Gfx working
together.
I'm not sure they're supported in FreeRDP
בתאריך יום ב׳, 13 בפבר׳ 2017 ב-15:43 מאת akallabeth <
<EMAIL_ADDRESS>
@joakim-tjernlund https://github.com/joakim-tjernlund There is a number
of issues pending with regard to remote app. Does this behavior only occur
with /gfx or also with /bpp:xxor /rfx?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/FreeRDP/FreeRDP/issues/3676#issuecomment-279395761,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ADTH1M37YRREI0iOwnYrM3oqMI3Q6vIIks5rcF4SgaJpZM4LcnAA
.

--
Idan Freiberg
PGP FP: 8108 7EC9 806E 4980 75F2  72B3 8AD3 2D04 337B 1F18

@speidy That is why I'm asking. Remote app was not on my priority list, need other stuff running first. If someone would be willing to check out the remote app stuff it would be great.

@akallabeth I cannot say, I just realized that is from pigdin-sipe to Windows and I don't think
either xfreerdp or Remmina are involved in this case but pidgin-sipe uses the freerdp libs
directly.
I can tell that when pidgin-spie is receiving a screen share, it invokes xfreerdp like so:
cmdline = g_strdup_printf("xfreerdp /v:%s /sec:rdp", client_data->socket_path);

@speidy check out https://github.com/tieto/sipe/issues/142#issuecomment-280062262
That fix solved my black screen. You may have to do something similar


Implement Mixer RBAC adapter

What this PR does / why we need it:
This change implements Mixer RBAC adapter.
Which issue this PR fixes (optional, in fixes #(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged): fixes #1233
Special notes for your reviewer:
Release note:

@liminw: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-presubmit.sh
0317c60f33bb8b71a48c3387697b7b9f88539fc8
link
/test istio-presubmit

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@liminw: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-presubmit.sh
479fcce8e1cdbc1d2048026f23f3242a4182e51e
link
/test istio-presubmit

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@liminw: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-presubmit.sh
1c4352c0748dad2e49ed473bb4cf7a3b2b8b046e
link
/test istio-presubmit

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/retest

/assign @geeknoid @mandarjog

I recommend you submit the proto files first with sufficient documentation.
Currently service role doesn't have type or name, but role ref has type and
name. How can a role ref work if the role definition doesn't have a name?
For each field documentation, there should be at least one example showing
what is a valid value. We need to make sure everyone can understand how to
use it.
Please don't refer to any Google doc. When we submit the proto, the doc
should be converted to readme.md as official spec. The corresponding Google
doc should be deprecated soon.

/hold
please adapt the pb.go generation and inventory integration to the new model (recently committed as part of the move away from bazel-based generation logic).

Hi,
So this code is embedding specific knowledge of the RBAC resources in Mixer. This is not what we want. If a specific adapter needs to reads CRDs of its own, the logic to read the CRDs must be contained in the adapter code itself. Otherwise, the general-purpose Mixer starts to have adapter-specific logic, which would be a bad thing.
So please implement all this logic in the adapter proper, and remove any changes to generic Mixer code

Hi @geeknoid, thanks for the comments. I added the RBAC code to the general Mixer code for a couple of reasons:

Mixer already implemented CRD read and watch mechanism today. If this has to be moved to adapter, there will have to be a lot of duplicated code.
As I understand, Istio native RBAC ServiceRole and ServiceRoleBinding will be first-class objects that shipped with Istio. Istio will also manage its config rollout. I think it is ok for Mixer to understand ServiceRole and ServiceRoleBinding CRDs by default.
Most of the RBAC logic is encapsulated in rbacStore.go. It won't affect the rest of the Mixer logic.
Adapter is just a way to enable RBAC. There is a "rbacEnabled" flag in the code, which is enabled only if the RBAC adapter is configured. If RBAC adapter is not configured, Mixer will not process RBAC CRDs.

Sorry, the Mixer is about routing requests to adapters. It doesn't have any specific knowledge of any of the behaviors of the adapters it is routing to. I do not want to compromise on this point. It's not architecturally appropriate.
If the issue is about code duplication, perhaps the right path here is to create a generic utility package that both Mixer and the RBAC adapter can share. Maybe Pilot and Istio-CA can use that same package as well. This is similar to what we're doing with istio/pkg/log.

I totally agree with Martin.
Have we considered implementing this logic in Envoy?

The plan is to have the RBAC logic both in Envoy and in Mixer.
The operator will eventually be programming the system using high-level
config. Based on what the operator intends to do, Galley will be able to
decide whether the proxy's RBAC logic should be used, or whether Mixer
needs to be used instead. Mixer has a richer environment so it can do more
than Envoy can.
On Fri, Dec 22, 2017 at 4:28 PM, Hong Zhang<EMAIL_ADDRESS>wrote:

I totally agree with Martin.
Have we considered implementing this logic in Envoy?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/istio/istio/pull/2299#issuecomment-353695006, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AVucHak1iilhiqVQzi8hsRh_nmAnL8bgks5tDEkUgaJpZM4RJPeJ
.


[DO NOT MERGE] wip: experiment to see what breaks if we enforce IUO checks more stri…

…ctly in all swift versions

@swift-ci Please smoke test

@swift-ci Please test source compatibility

This also fixes some issues with the earlier commit to catch more cases of IUO used in the wrong places, and I'll commit those fixes once I fix up a couple remaining issues.

Looks like there were only two issues! RxSwift had this:
print(convertResponseToString(data, response, error as NSError!, interval))

which has been fixed in the upstream repository already.
Alamofire has this:
if let encodingName = response?.textEncodingName as CFString!, convertedEncoding == nil {

where the '!' is effectively unnecessary. The code is still there upstream at https://github.com/Alamofire/Alamofire/blob/master/Source/ResponseSerialization.swift#L371

Yup. It looks like we give a working fix-it in both cases as well (replace ! with ?).

@rudkx One alternative is to emit this as a warning in Swift 3/4 mode, and continue parsing as if it were a ?.

@slavapestov Yes I mentioned that possibility in another forum. I think that's a reasonable choice for these casts, but probably not for something like [Int!] where other errors will surface and it will be even more confusing than just rejecting [Int!] in the first place.

@swift-ci Please smoke test

@swift-ci Please test source compatibility

Updated this commit since cef6c9463c is now in, which addresses some bugs in the earlier commit.
This is now limited to switching over to using the new tests all the time.
I still do not plan on merging this without further investigation, but want to verify where things stand and fix up any remaining code in our tree (e.g. in tests) that I may have missed.

@swift-ci Please smoke test

@swift-ci Please test source compatibility

@swift-ci Please smoke test

@swift-ci Please test source compatibility

@swift-ci Please test source compatibility

@swift-ci Please smoke test

@swift-ci Please test source compatibility

@swift-ci Please test source compatibility

@swift-ci Please smoke test

@swift-ci Please test source compatibility

@swift-ci Please smoke test

@swift-ci Please smoke test OS X platform

@swift-ci Please test source compatibility

@swift-ci Please test source compatibility

There is still a cast in Foundation that is disallowed by SE-0054. I opened https://github.com/apple/swift-corelibs-foundation/pull/1300 to make it a cast to Optional instead.

@swift-ci Please smoke test

@swift-ci Please smoke test

@swift-ci Please smoke test Linux platform

@swift-ci Please smoke test Linux platform

@swift-ci Please smoke test

@swift-ci Please smoke test Linux platform

@swift-ci Please smoke test

Ran into a couple more casts in Foundation that need to be fixed up: https://github.com/apple/swift-corelibs-foundation/pull/1303

@swift-ci Please test source compatibility

@swift-ci Please smoke test Linux platform

@swift-ci Please test source compatibility

Please test with following pull request:
https://github.com/apple/swift/pull/12682
https://github.com/apple/swift-corelibs-foundation/pull/1306
@swift-ci Please smoke test

@shahmishal Any idea what might have happened here? The multi-PR test doesn't seem to have actually started.

This is was during CI outage yesterday.
Please test with following pull request:
#12682
apple/swift-corelibs-foundation#1306
@swift-ci Please smoke test

Also, it does not support same repository :(
Right now you can only provide one PR per repositories

Closing in favor of a new PR I will open soon.


Use scalastyle's rule for imports order

Since 0.8 Scalastyle supports the rule that checks if imports are ordered according to the predefined order. I tried to pick the most simple order (everything is in one group and sorted alphabetically) for Circe so it matches the previous style.
If you think we should enable some mo complicated rule (i.e., two groups for stdlib imports and everything else as per Finch's config) - let me know, I'm happy to change it.

This is great! I think I'd prefer 'A' < 'a', but I can live with this version.
I don't prefer separating standard library imports, but I'm not sure I have a good reason for that.

Just restarted the build—looks like a Sonatype server issue.

Current coverage is 77.70%

Merging #149 into master will not affect coverage as of 239fa94

Powered by Codecov. Updated on successful CI builds.


Using callbackComponentOverride causes errors when logging in

Issue and Steps to Reproduce
When using callbackComponentOverride there's something extra happening that causes errors in the console. The errors happen when you login, after further page loads they do not happen. These errors happen with dev and production builds. I used React Profiler to check what's happening with AuthenticationProvider and it seems it is doing two extra updates (re-renders) compared to using default callback component. I suspect there is a race condition and some code tries to check state before it's ready.
I tried to follow code in AuthenticationContext.container.js from the line const CallbackComponent = callbackComponentOverride     ? withComponentOverrideProps(CallbackInt, callbackComponentOverride)     : CallbackInt; but I'm not completely sure which part triggers the re-renders.
Error happens with the code below and it goes away if I remove callbackComponentOverride={CallbackComponent}. I've tested with Chrome and Firefox as well.
<AuthenticationProvider
        configuration={oidcConfiguration}
        logger={console}
        loggerLevel={oidcLog.DEBUG}
        isEnabled={true}
        callbackComponentOverride={CallbackComponent}
>

Versions
react-oidc-context": "^3.0.2-alpha.0"
Screenshots
With custom callback component two extra "update" phases (total of 5 events in AuthenticationProvider):

With default callback component (total of 3 events in AuthenticationProvider)

Expected
No errors.
Actual
Errors:
OidcClient.readSigninResponseState: No matching state found in storage
ERROR [react-context-oidc] : There was an error handling the token callback: No matching state found in storage
OidcClient.readSigninResponseState: No state in response
ERROR [react-context-oidc] : There was an error handling the token callback: No state in response

Additional Details

Installed packages:

    "@apollo/react-hooks": "^3.1.2",
    "@axa-fr/react-oidc-context": "^3.0.2-alpha.0",
    "@axa-fr/react-oidc-context-fetch": "^3.0.2-alpha.0",
    "apollo-boost": "^0.4.4",
    "graphql": "^14.5.8",
    "oidc-client": "^1.9.1",
    "prop-types": "^15.7.2",
    "pure-react-carousel": "^1.23.0",
    "react": "^16.10.2",
    "react-dom": "^16.10.2",
    "react-router-dom": "5.1.2",
    "react-scripts": "3.2.0",
    "styled-components": "^5.0.0-beta.9",
    "use-async-effect": "^2.2.1"

This is because the default callback component is under a Memo Hook, but if you change the props  the memo hook reload the component.
I can fix it with a memo.
Thanks :)


ModuleNotFoundError: No module named 'ipware.ip2'  -- error in django-axes==5.0.7, Django==2.2, Python==3.8

django-ipware has no module ipware.ip2 in recent version. Please fix this ASAP.
In the helpers.py file import ipware.ip2 is breaking for new version of django-ipware.
django_1         | Traceback (most recent call last):
django_1         |   File "manage.py", line 30, in <module>
django_1         |     execute_from_command_line(sys.argv)
django_1         |   File "/usr/local/lib/python3.7/site-packages/django/core/management/__init__.py", line 381, in execute_from_command_line
django_1         |     utility.execute()
django_1         |   File "/usr/local/lib/python3.7/site-packages/django/core/management/__init__.py", line 357, in execute
django_1         |     django.setup()
django_1         |   File "/usr/local/lib/python3.7/site-packages/django/__init__.py", line 24, in setup
django_1         |     apps.populate(settings.INSTALLED_APPS)
django_1         |   File "/usr/local/lib/python3.7/site-packages/django/apps/registry.py", line 122, in populate
django_1         |     app_config.ready()
django_1         |   File "/usr/local/lib/python3.7/site-packages/axes/apps.py", line 47, in ready
django_1         |     from axes import checks, signals  # noqa
django_1         |   File "/usr/local/lib/python3.7/site-packages/axes/signals.py", line 11, in <module>
django_1         |     from axes.handlers.proxy import AxesProxyHandler
django_1         |   File "/usr/local/lib/python3.7/site-packages/axes/handlers/proxy.py", line 7, in <module>
django_1         |     from axes.handlers.base import AxesHandler
django_1         |   File "/usr/local/lib/python3.7/site-packages/axes/handlers/base.py", line 2, in <module>
django_1         |     from axes.helpers import (
django_1         |   File "/usr/local/lib/python3.7/site-packages/axes/helpers.py", line 11, in <module>
django_1         |     import ipware.ip2
django_1         | ModuleNotFoundError: No module named 'ipware.ip2'

Same in here

Same here, please update django-ipware dependency

I confirm the issue. Quickfix: change ipware.ip2 to ipware.ip in the helpers file (twice in the file).

@Huertix

Same in here
404... https://github.com/un33k/django-ipware/blob/master/ipware/ip2.py
I hope you can fix this soon guys... our prod envs can not be deployed.. :(

Locking django-ipware in your own requirements file should allow you to build for now until this is sorted.
django-ipware==2.1.0

Highly appreciate it @cheesysam

Fixed in 5.3.5 where ipware has been locked to suitable version range >=2,<3 for now.


does k3s support custom scheduler?

we know k8s support custom scheduler,does k3s support this feature?

Can anyone provide information on this topic? Would be interested as well if K3s provides the possbility to use scheduler extenders through webhooks as K8s...

If it works upstream, it should work in k3s. Have you run into any problems with it?


Fault Simulation

Adding fault simulation functionality, tests and documentation for http, https and tcp.

Thanks! Slammed at the moment but will review shortly.

Looks great, thanks so much for doing this!


How to Format the Resume Sections Underline ?

I want to change the Resume Sections Headline Underline from Current (Where it starts after the text end) to the Normal underline we see in Resume i.e just below the Text not in Front of it. Can anyone Help me out on this?

Got my answer on the TeX exchange https://tex.stackexchange.com/a/639369/267597


Cleanups and docs

Codecov Report

Merging #175 into master will increase coverage by 0.18%.
The diff coverage is 86.36%.

@@            Coverage Diff             @@
##           master     #175      +/-   ##
==========================================
+ Coverage   83.27%   83.46%   +0.18%
==========================================
  Files         102      102
  Lines        2667     2655      -12
  Branches      130      124       -6
==========================================
- Hits         2221     2216       -5
+ Misses        446      439       -7

Impacted Files
Coverage Δ

...main/scala/com/ing/baker/il/RecipeVisualizer.scala
92.06% <100%> (ø)
:arrow_up:

.../scala/com/ing/baker/runtime/java_api/JBaker.scala
50.81% <100%> (ø)
:arrow_up:

...ker/runtime/actor/process_index/ProcessIndex.scala
84.61% <100%> (ø)
:arrow_up:

...ker/runtime/core/internal/InteractionManager.scala
100% <100%> (ø)
:arrow_up:

...ore/internal/MethodInteractionImplementation.scala
84% <100%> (-2.21%)
:arrow_down:

...ng/baker/runtime/core/internal/RecipeRuntime.scala
93.1% <100%> (ø)
:arrow_up:

.../main/scala/com/ing/baker/runtime/core/Baker.scala
82.3% <33.33%> (ø)
:arrow_up:

...ntime/actor/process_instance/ProcessInstance.scala
93.45% <75%> (-0.83%)
:arrow_down:

...untime/core/internal/InteractionTaskProvider.scala
93.18% <80%> (+14.33%)
:arrow_up:

...untime/actor/process_index/ProcessEventActor.scala
92.5% <83.33%> (-0.36%)
:arrow_down:

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 14d4de8...00fa852. Read the comment docs.


Error during distro-sync.

Trying to convert Centos 8 to Rocky with latest script.
Server is default Centos 8 with following extra packages:

@idm:DL1
freeipa-server
kexec
htop (epel)
fish (epel)

Logs:
  Running scriptlet: chrony-3.5-2.el8.x86_64                           699/1508
  Downgrading      : ipa-client-4.9.2-4.module+el8.4.0+589+9650b94f    700/1508
  Running scriptlet: ipa-client-4.9.2-4.module+el8.4.0+589+9650b94f    700/1508
  Running scriptlet: ipa-server-4.9.2-4.module+el8.4.0+589+9650b94f    701/1508
  Downgrading      : ipa-server-4.9.2-4.module+el8.4.0+589+9650b94f    701/1508
  Running scriptlet: ipa-server-4.9.2-4.module+el8.4.0+589+9650b94f    701/1508
  Reinstalling     : dracut-network-049-135.git20210121.el8.x86_64     702/1508
  Downgrading      : python3-wheel-wheel-1:0.31.1-2.module+el8.4.0+    703/1508
  Downgrading      : python3-virtualenv-15.1.0-19.module+el8.4.0+59    704/1508
  Running scriptlet: python3-virtualenv-15.1.0-19.module+el8.4.0+59    704/1508
  Reinstalling     : kexec-tools-2.0.20-46.el8_4.1.x86_64              705/1508
  Running scriptlet: kexec-tools-2.0.20-46.el8_4.1.x86_64              705/1508migrate2rocky.sh: line 646: 2453678 Killed                  dnf -y distro-sync

Error during distro-sync.

An error occurred while we were attempting to convert your system to Rocky Linux. Your system may be unstable. Script will now exit to prevent possible damage.

I was forced to rollback, so this server is no-longer available for further debugging. If needed I can try again the migration on copy of this server.

It would help to have the full log from /var/log/migrate2rocky.log
From what you've provided I would say that the distro-sync got manually killed, possibly by some watchdog process or something?  Are you running any special security software that might be interfering?  Maybe it was an OOM issue?

For sure not OOM, checked it. Full log is no longer available. Currently in progress of rollback.
After rollback finished, I could create clone and try reproduce this there. I will provide further details in a hour.
There isn't special software running on this server outside of listed software in my first post.

Well, the snippet you provided explicitly says, "Killed" which references SIGKILL or signal #9 which cannot be trapped and certainly is not coming from migrate2rocky itself.  To verify next time you run migrate2rocky, can you change line 798 (the distro-sync line) to the following?
dnf -y distro-sync || exit_message "Error during distro-sync: $?"
That will confirm if it's being killed by a signal and which signal (but I suspect it's 9).

Unable to find time to reproduce. Will re-open if I see it necessary.


Fix 404 handling in apstra_datacenter_ip_link_addressing resource

I am unsure why we are removing the resource if the read finds no blueprint, but not if the update finds no blueprint.
We should do the same in either case right?

I am unsure why we are removing the resource if the read finds no blueprint, but not if the update finds no blueprint. We should do the same in either case right?

RemoveResource() has no effect in Update().
There's a short window during plan and apply where the required object could have been deleted, but there's no graceful way of handling an impossible-to-execute plan. It's going to be an error.

I am unsure why we are removing the resource if the read finds no blueprint, but not if the update finds no blueprint. We should do the same in either case right?

RemoveResource() has no effect in Update().
There's a short window during plan and apply where the required object could have been deleted, but there's no graceful way of handling an impossible-to-execute plan. It's going to be an error.

Sounds good.


Debug CI failure

This is an attempt to debug #5972. The failures are potentially caused by processes leaking from one test failing another test. If so, this autouse fixture, which is applied to every test, might cache the bad test.
Or it could be something completely different.

I think https://github.com/dask/dask/pull/5979/commits/39d62f16dcefc57f4e1ed63d01022e1721f4d017 got it.


Issue reproducing tokenized input for BERT

System Info

GPU name: NVIDIA RTX A1000
Windows: 10
0.7.1 tensorrt-llm

Who can help?
@byshiue @symphonylyh
Information

[X] The official example scripts
[X] My own modified scripts

Tasks

[X] An officially supported task in the examples folder (such as GLUE/SQuAD, ...)
[X] My own task or dataset (give details below)

Reproduction
I'm utilizing BertTokenizer alongside optimized BERTModel. However, when decoding the output logits from the TensorRT-optimized BERT model, I encounter unexpected results, notably a significant presence of [unusedXXX] tokens in the decoded text, which suggests a potential mismatch between the tokenizer's vocabulary and the logits produced by the TensorRT engine.
Below is a simplified code snippet that illustrates the issue:
from transformers import BertTokenizer

# Initialize the tokenizer
tokenizer = BertTokenizer.from_pretrained('bert-base-uncased')

# Example of encoding an input
input_text = "This is a test input."
encoded_input = tokenizer.encode_plus(input_text, return_tensors="pt")

# Pseudo-code: Assuming `logits` are obtained from the TensorRT-optimized model
logits = tensorrt_engine_infer(encoded_input['input_ids'])

# Decoding the output logits to text
decoded_output = tokenizer.decode(logits.argmax(-1), skip_special_tokens=True)
print("Decoded Output:", decoded_output)

Full code can be seen here
Expected behavior
The expected behavior is that the decoded output closely resembles the input text or provides meaningful predictions for masked language modeling tasks, without an over-representation of [unusedXXX] tokens.
actual behavior
After disabling Multi-Head Attention (MHA) kernels to sidestep potential accuracy issues with logits, I anticipated that the model's output would align closely with expected results. Instead, the decoded outputs primarily consist of [unusedXXX] tokens. This suggests a misalignment in how the tokenizer interprets the logits from the TensorRT-optimized BERT model, deviating from expected behavior where meaningful tokens are predicted.
additional notes

How can I refine the tokenization, encoding, and decoding workflow to ensure compatibility with a TensorRT-optimized BERT model, especially to mitigate the issue of [unusedXXX] tokens in the output?
Are there best practices or adjustments recommended in the examples/bert to correctly encode and decode logits?
Given the configurations in my config.json (provided below), have I overlooked any settings that could impact the tokenizer's performance with the TensorRT model?

My config.json below:
{
  "builder_config": {
    "int8": false,
    "max_batch_size": 8,
    "max_input_len": 512,
    "name": "BertModel",
    "precision": "float16",
    "tensor_parallel": 1,
    "use_refit": false
  },
  "plugin_config": {
    "attention_qk_half_accumulation": false,
    "bert_attention_plugin": false,
    "context_fmha_type": 0,
    "gemm_plugin": false,
    "gpt_attention_plugin": false,
    "identity_plugin": false,
    "layernorm_plugin": false,
    "layernorm_quantization_plugin": false,
    "lookup_plugin": false,
    "lora_plugin": false,
    "multi_block_mode": false,
    "nccl_plugin": false,
    "paged_kv_cache": false,
    "quantize_per_token_plugin": false,
    "quantize_tensor_plugin": false,
    "remove_input_padding": false,
    "rmsnorm_plugin": false,
    "rmsnorm_quantization_plugin": false,
    "smooth_quant_gemm_plugin": false,
    "tokens_per_block": 0,
    "use_context_fmha_for_generation": false,
    "use_custom_all_reduce": false,
    "use_paged_context_fmha": false,
    "weight_only_groupwise_quant_matmul_plugin": false,
    "weight_only_quant_matmul_plugin": false
  }
}

I appreciate any advice or insights you can share to help resolve this issue. Thank you.

@Muhtasham  can you share the concrete command sequence to reproduce the issue? Including how you build the engine.
Thanks
June

@Muhtasham  can you share the concrete command sequence to reproduce the issue? Including how you build the engine.
Thanks
June

@juney-nvidia hi I followed official bert example in tensorRT-llm rel branch for windows

@symphonylyh I tried to track down here, seems like initializing randomly?

@Muhtasham Do you still have the problem? If not, we will close it soon.

@Muhtasham Do you still have the problem? If not, we will close it soon.

Yes, would be nice to have official documentation regarding this


add validator_index to ValidatorsResponseEntry

Adding validator_index to the builderGetValidators response: https://flashbots.github.io/relay-specs/#/Builder/getValidators

@jtraglia great question, thanks, I should have added it in the beginning!
There is a PR for the relay that adds a proposerIndex check: https://github.com/flashbots/mev-boost-relay/pull/366
To pass the proposer index around, it's added to the internal data structure, which automatically exposes it in the relay API. We could choose to not expose it in the JSON encoding, but I don't see a reason for it as it's strictly additive and backwards compatible.


fix cache error handle

Codecov Report
Patch coverage: 100.00% and no project coverage change.

Comparison is base (096ca0a) 39.90% compared to head (6a67704) 39.90%.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@           Coverage Diff           @@
##             main     #735   +/-   ##
=======================================
  Coverage   39.90%   39.90%
=======================================
  Files          20       20
  Lines        1491     1491
=======================================
  Hits          595      595
  Misses        832      832
  Partials       64       64

Files Changed
Coverage Δ

internal/handler/wallet/sign.go
37.41% <100.00%> (ø)

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


How-to use blueprints with a simple Hello World example

This example walks people through the process of creating a new blueprint, starting from XLD and XLR definitions.
The "DONE" tasks below are complete.
Definition of Done
General

[x] Your branch is up-to-date with development branch
[x] A Readme.md file is generated as part of the blueprint which, at the minimum, explains how to use the blueprint after it is generated(like adding any missing steps, creating accounts, setting up docker containers, applying the yaml using XL-CLI, running release etc). Place this file preferably in the XebiaLabs folder. Do not add the blueprint generation steps here as it wont be useful since the file is ceated only after the blueprint generation.
[x] The blueprint must use an XL product at some capacity
[x] There are no sensitive info in blueprints(tokens, credentials, licence), for questions that ask for password or sensitive info use secret: true in the bleuprint.yaml parameter definition.
[x] Do not add the xebialabs/.gitignore, xebialabs/values.xlvals and xebialabs/secrets.xlvals to the bleuprint.yaml files section, and do not check in those files, as they are autogenerated based on parameter definitions. Secrets are created when a parameter in the blueprint.yaml has the secret: true directive. For adding parameters to values.xlvals use the saveInXlVals: true directive.
[x] Please do not ask questions for trivial things like phase names, task names, folder names etc, ask questions that add value and be opinionated where possible. For example ask for a project name and derive folder names, task names etc based on that.
[x] Folder and file names must use dash-case, for example: aws/sample-app-demo, xld-environment.yaml

Testing

[ ] Works on Linux, Windows and Mac
[ ] Code is reviewed by someone else in the team
[x] Blueprint is manually tested with dockerised instances of our products
[ ] CI is green

@marcoman thanks, please let us know when you think the PR is ready for further review/merge

I believe we're ready.
Of these 3 outstanding items, I have these answers:

Works on Linux, Windows and Mac
I only have access to linux and windows
[ ]  Code is reviewed by someone else in the team
does the PR count as a review by someone else?
[ ]  CI is green
Should I add this to a CI server somewhere?

There is no CI yet and we will review it soon

I agree with @deepu105. Documenting how to create a blueprint and using an example blueprint for that is certainly a good idea. But let's not publish that blueprint in the official blueprint repository.
Most of the users of the blueprint feature are consumers (instead of authors) and might be confused by it. Also, for an example, it is probably best to get people to author their own new blueprint from scratch rather than start with a complete example.


⚠ BCR Bot has degraded performance

In 0f5b229, BCR Bot (https://bcr.alternativasinteligentes.com/BCRApi/web/chatbot) experienced degraded performance:

HTTP code: 200
Response time: 933 ms

Resolved: BCR Bot performance has improved in bd2d8a2.


Closes: #1

Updated validations.py python script.
Fixed the behavior of validate_user function in validaiton.py
Fixes #<issue_number_goes_here>

It's a good idea to open an issue first for discussion.

[ ] Tests pass
[ ] Appropriate changes to README are included in PR

Validations.py files is fixed and working fine


Question: Why other http methods not supported (e.g. DELETE/PUT etc...)

I see in the express server that only get/post is supported, is there a reason for that?

Hi, can you give a bit more info on what you're trying to achieve?
Why are you looking at this specific OpenFaaS Template? We will need more context.
Cheers,
Alex

Thanks @alexellis  for your fast comment.
I am trying to migrate one of our restful api services into openfaas.
Part of what i am trying to achieve is backward compatibility,  so if for example i have a resource "user",
i would like to have endpoint http://some-host.com:8080/api/user which will manage the user resource, hence would be able to deal with GET/POST/PUT/DELETE (sometimes also patch) methods.
That being said, i have few solutions in mind, and would like to see if anyone went in my path before or i am "inventing the wheel" here(this sounds to me like a very common scenario to migrate rest api to serverless architecture)
Solution 1 (no backward compatibility ):
Since a function is invoked only with POST, there should be some sort of "X-Http-method-override" header added to the call, and in express template we need to be able to handle such header accordingly (for example using https://github.com/expressjs/method-override - this kind of solution requires designing the rest service as a single function with a switch-case handlers for each method. since we need to add header from client side, backward compatibility not kept in this case since we need to make POST calls + x-http-method-override header
Solution 2 (Backward compatible):
Using kong Serverless plugin and implementing pre-function and post-function plugin to make a call to the desired function (delete user for example). this way kong is acting as "smart reverse proxy" and we can have different function for each http method (create/delete/update/query without switch-case). This couples the solution to kong and not be suitable for everyone and also requires writing kong plugin in lua.

Hi @kobynet
Let's move the discussion on faas#214 as this is related.
For the path changes there is an issue raised as well: faas#716
In this endpoint -  http://some-host.com:8080/api/user - is user intended to be a function?
A related part of the implementation is in gateway/server.go#L144 and any changes can be considered in the same context.
Ivana

I believe these are supported. Closing the issue. Feel free to keep commenting.


NJ 2023 joint 2x9K wages

NJ 2023 joint 2x9K wages
http://taxsim.nber.org/out2psl/nj
Emulator - -2395, Tax Act -2598.

@feenberg this difference is due to PE-US calculating a tax amount of $203 which I am checking agains the tax rate schedule:

Not sure why TaxAct does not include this amount - the refundable credit amounts are equal in TaxAct and PE


keyboard shortcuts

Hello,
Is it possible to bind remote sync actions to keyboard shortcuts? if so how?
For exemple i'l like to bind cmd+alt+u to upload the current file i'm editing.

Hi @karimcossutti currently there are no default keyboard shortcuts built into remote sync however you can set one up manually doing the following:
Go to settings > Keybindings (on the left)
Clicking your keymap file will open up your custom keymap file
and pasting the following bellow all the comments:

'atom-workspace':
  'cmd-alt-u': 'remote-sync:upload-file'

This creates a keybinding to be used in the workspace that will active the uploading of a file function.
I do think adding a few default keyboard shortcuts would be a nice touch so I'm keeping this ticket open for that.


Update Wireguard LXC - Information about WGDashboard added

Description

Added wg0.conf as default in /etc/wireguard
Added Documentation (Wiki-Page) about WGDashboard vs. Wireguard
Remove (admin|admin) - to harmonize the script to others. As always, login details are available on the website

Fixes # (issue)
https://github.com/community-scripts/ProxmoxVE/issues/245
Type of change
Please check the relevant option(s):

[ ] Bug fix (non-breaking change that resolves an issue)
[x] New feature (non-breaking change that adds functionality)
[ ] Breaking change (a fix or feature that would cause existing functionality to change unexpectedly)
[ ] New script (a fully functional and thoroughly tested script or set of scripts.)

Prerequisites
The following efforts must be made for the PR to be considered. Please check when completed:

[x] Self-review performed (I have reviewed my code, ensuring it follows established patterns and conventions)
[x] Testing performed (I have tested my changes, ensuring everything works as expected)
[x] Documentation updated (I have updated any relevant documentation)

@havardthom, done, check again

quick question - what are the default credentials? One the PVE Help site it lists them as admin | admin...
https://community-scripts.github.io/ProxmoxVE/scripts?id=wireguard
...but this isn't working for me using the default install option.

It should be admin admin, if its not, remove the following lines from wg-dashboard.ini
[Account]
username = admin
password = $2b$12$azSepWJbOXFRngs1fhgW6u/N4QVqRd6nY5KjdN3f8K2nkcrEdRITG

Hope this helps.


⚠ Bofrost.lu has degraded performance

In fd140c1, Bofrost.lu (https://www.bofrost.lu) experienced degraded performance:

HTTP code: 200
Response time: 1065 ms

Resolved: Bofrost.lu performance has improved in 5755595 after 18 minutes.


Update README.md (link to plugin guide)

Update link to plugin guide

Thank you, @poolborges
Per https://github.com/gluonhq/gluonfx-maven-plugin#issues-and-contributions, can you sign the CLA before we can merge your contribution?

I have assign CLA (online form: submited).


Added segnet-video and detectnet-video.

segnet-video and detectnet-video are added with OpenCV. If OpenCV is not installed, CMake won't compile them. The usage is printed when running without any arguments.

Fixed the bugs in the overlay function. The scales should be (s_w/width,s_h/height). And on line 423 the math function floor() should be  applied instead of int.

I haven't been able to replicate your results, everytime  I try to make I got the following mistake:
In file included from /usr/include/opencv2/opencv.hpp:86:0,
                 from /home/nvidia/WorkSpace/jetson-inference/detectnet-video/detectnet-video.cpp:20:
/usr/include/opencv2/stitching.hpp:58:4: warning: #warning Detected X11 'Status' macro definition, it can cause build conflicts. Please, include this header before any X11 headers. [-Wcpp]
 #  warning Detected X11 'Status' macro definition, it can cause build conflicts. Please, include thi
    ^
In file included from /usr/include/GL/glx.h:30:0,
                 from /home/nvidia/WorkSpace/jetson-inference/build/aarch64/include/glUtility.h:10,
                 from /home/nvidia/WorkSpace/jetson-inference/build/aarch64/include/glDisplay.h:9,
                 from /home/nvidia/WorkSpace/jetson-inference/detectnet-video/detectnet-video.cpp:8:
/usr/include/opencv2/stitching.hpp:128:10: error: expected identifier before ‘int’
     enum Status
          ^
In file included from /usr/include/opencv2/opencv.hpp:86:0,
                 from /home/nvidia/WorkSpace/jetson-inference/detectnet-video/detectnet-video.cpp:20:
/usr/include/opencv2/stitching.hpp:129:5: error: expected unqualified-id before ‘{’ token
     {
     ^
detectnet-video/CMakeFiles/detectnet-video.dir/build.make:62: recipe for target 'detectnet-video/CMakeFiles/detectnet-video.dir/detectnet-video.cpp.o' failed
make[2]: *** [detectnet-video/CMakeFiles/detectnet-video.dir/detectnet-video.cpp.o] Error 1
CMakeFiles/Makefile2:635: recipe for target 'detectnet-video/CMakeFiles/detectnet-video.dir/all' failed
make[1]: *** [detectnet-video/CMakeFiles/detectnet-video.dir/all] Error 2
Makefile:127: recipe for target 'all' failed
make: *** [all] Error 2

@gcjyzdd

Hi Davidnet, it seems that OpenCV is not properly compiled on your machine. Could you check if OpenCV works on your machine?

@gcjyzdd ,
Why have you included all opencv headers? isn't this an overkill? Maybe you can just include the headers that are needed.
@Davidnet ,
I just wanted to try detectnet so I included opencv2/core and opencv/highgui headers in detectnet-video.cpp rather than all opencv headers and I could compile. The error, though, could be because of multiple opencv installed or some of the older opencv files not being removed when you uninstalled previous version.

I installed OpenCV 3.4 and modified the CMakeLists.txt file, but I still get the following error when attempting to make... Any ideas?
CMake Error at CMakeLists.txt:112 (add_subdirectory):
add_subdirectory given source "detectnet-video" which is not an existing
directory.

The error indicates cmake cannot find the source file. Have you pulled the
correct repo? Please check if you have detectnet-video.cpp locally.
On Sun, May 20, 2018 at 11:49 PM, zackosmacko32<EMAIL_ADDRESS>wrote:

I installed OpenCV 3.4 and modified the CMakeLists.txt file, but I still
get the following error when attempting to make... Any ideas?
CMake Error at CMakeLists.txt:112 (add_subdirectory):
add_subdirectory given source "detectnet-video" which is not an existing
directory.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/dusty-nv/jetson-inference/pull/114#issuecomment-390515505,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AP7fe6kcCN7cBC0fzmDzVAAZhLdHoTlMks5t0eTMgaJpZM4OmsnI
.

--
Best regards,
Changjie


Infer Directionality from Phylogenetic Tree

Take any two nodes from the Phylogenetic tree and measure their respective distances from their most recent common ancestor. The one with the shorter distance is more likely to be the source, so make sure it's tagged as the source in the corresponding link object. Repeat for all pairs of nodes.

Depends on #57

@Sergey-Knyazev pointed out to me that this is equivalent to determining a sequence's position relative to its link in a sorted list of genetic distances between sequences and the root (for which either the consensus or reference is an adequate proxy)


[Blob][Datalake] Dynamically set read_timeout

We have gotten multiple issues regarding read_timeouts and how they can hang for 20+ hours since they are hardcoded. This PR reduces the read_timeout to 82 sec (4MB @ 50KB/s) for all basic operations that don't have a large payload. And dynamically sets the read_timeout for download and upload operations depending on the chunk size used at a network speed of 50KB/s
Newer versions of Python use this timeout for the the entire roundtrip time.
Resolves https://github.com/Azure/azure-sdk-for-python/issues/21500

As I mentioned in https://github.com/Azure/azure-sdk-for-python/pull/24031/files#r852410779, I believe the role of read_timeout is misunderstood.
See https://github.com/psf/requests/issues/3099 for a more elaborate discussion on the topic, in which large uploads/downloads come up.


PIP-0001 Discussion

Please provide your comments regarding PIP-0001 here.

Software should be tested first.
What is the purpose of PIP without software testing/acceptance phase ? Design decisions ?
If a PIP according to current PIP-0001 is accepted ? How will it be implemented ? Would there be a test phase ?
Are proposal supposed to be pre-tested ?
This is very fuzzy and needs further explanation ?!?