[WIP] initial graph implementation

Hey,
This is just a naive pure python implementation to get things started.
I'm planning to benchmark with other data structures, more operations (e.g. iterating over the graph), and other packages (e.g. numba).
Should we support edge features on this first implementation?
How should we organize the files?

I implemented the trackmate-like graph, it's very fast using numba.
I had to duplicate the number of edges for the undirected graph, I'm not sure if there's a better way to do this.

Very cool stuff @JoOkuma!
Mild comments:

I would suggest having a single Graph class, and then directed, undirected, and multigraphs can either have an internal flag, or inherit from the parent class.
I think you do need to duplicate edges for undirected graphs. If you're only ever checking for edge presence, then you can always check (u, v) in E or (v, u) in E. But for things like traversal, this is not an option, and you'd be stuck checking whether any other node has an incoming edge to your current node, which is slow. However, when it comes to e.g. edge features, you can always give (u, v) and (v, u) the same ID, and they resolve to the same feature row.
I'm happy to help with package structure. I'll do that in a separate PR and then you can rebase?
I'd prefer to just use numba as numba rather than nb, as it is less common than the other packages. Also you don't need to call njit: @numba.njit (no parens) will work.
Should we start with 2x the number of node/edge slots rather than 1x? Or 1.3x? Something that won't immediately need a reallocation if we click "add". :joy:

Exciting to see this taking shape!

@JoOkuma see #2. Let me know if it looks ok to you and I'll merge.

I would suggest having a single Graph class, and then directed, undirected, and multigraphs can either have an internal flag, or inherit from the parent class.

Ok, I want to benchmark adding, and transversing the graphs, and then I'll clean up to a single graph class.

However, when it comes to e.g. edge features, you can always give (u, v) and (v, u) the same ID, and they resolve to the same feature row.

Good idea, sibling edges could always be next to each other (e.g, i, i+1), so we can index the features by i // 2, delete the pair without having to search for the sibling, and ignore duplicates fast when sending the bufffer to vispy [::2].

I'd prefer to just use numba as numba rather than nb, as it is less common than the other packages. Also you don't need to call njit: @numba.njit (no parens) will work.

👍

Should we start with 2x the number of node/edge slots rather than 1x? Or 1.3x? Something that won't immediately need a reallocation if we click "add". 😂

Great! It could be an optional parameter.

@jni or anyone else, any thoughts on nodes' indexing?
I think the user should manage the node indexing and we only return the buffer index and keep it consistent.
For example, the node add_nodes(<nodes' coordinates/features>) would return the indices of the added nodes. This is advantageous to us because we don't have to worry about arbitrary indexing and keep things efficient by using our buffers' index.
The downside is if the user decides to use their own indexing they'll have to remap their indices to do any operation, including adding edges.
If we decide to let the user provide their own indexing then we need to store a dictionary from their indexing to our buffer's index and we might not get that much of a speedup. I'm not sure if there's another way to implement this.

@JoOkuma sorry about the slow response! But at any rate, I don't like the idea of not providing indexing. It's weird to provide nodes with only coordinates. Yes you get indices, but as a user I want to provide a graph, which is usually a list of edges, which are id pairs. giving the graph as coordinate pairs is obviously fraught (since coordinates are floating point numbers), while adding the graph in two stages is awkward: here's my point coordinates, now give me my ids, ok now I need to figure out how the coordinates I gave you match those ids and translate my edges to give you the edges... It's all very messy.
With regards to speed, I think it's ok: we have a mapping from external node IDs to sequential IDs as a dictionary; numba supports int-int dictionaries and we only use this rarely: internally, all the operations are on sequential IDs, and when we need to ask for original IDs, the reverse mapping can be stored in an array, which is very fast.
I think operations like adding and removing edges can be "quite fast", but don't need to be blazing fast. The critical speed issues are traversing paths and traversing the whole graph, which we can do in sequential ID land.
Or, at least, that's my rationale. I think the alternative API is too horrible to contemplate though, so we should give this a go. :joy: If we measure a hideous bottleneck in the remapping, we can reconsider.

It makes a lot of sense and we restrict the API to integer indexing only.
I implemented a few additional features and I'll get back to this next week, I need to finish a few other things this week.

@jni, it's taking shape.
My numba implementation seems very C like, euheuehu. I was hoping for a better way to deal with the constants while still inlining them but I couldn't figure it out.

I think the basics are mostly done.
Some points that are still missing are:

[ ] A better approach to handle the nodes' features. I need to check how the feature tables are used in napari.
[ ] Slicing the graph for visualizing it in napari --- important for tracks layer.
[ ] A function serializes the graph data to a vispy buffer.

@jni

loops please avoid while

I will try to fix that.

can we make the public API as close as possible to networkx? Or do you think there are reasons to avoid that?

Yes, but it will be less consistent with the naming convention used in the trackmate's white paper, the backend should remain the same, though.

I think napari will concern itself only with spatial graphs, but I think this library can probably remain more general?

Yes, we can, so the constructor input will be only a sparse matrix.
I discussed a bit with the folks from the architecture working group and I'll remove the features from the napari-graph, the layer can manage that, I think the same could be done with coordinates, I'm going to think if there's any shortcoming.

@jni, the downside of removing the coordinates from napari-graph is that the user will have to manage it on its own, which could be more inefficient.
This won't affect the graph layer implementation because I'm only accessing the _coords buffer as it's more efficient and it shares the functionality from the points layer, reference.
I'm going to proceed with removing this, but we should keep this in mind.

Still, getting the hang of GitHub, should I "add a review" to your comments or just resolve them?
Tomorrow I'll try to finish the API change to scipy sparse matrices and remove the coordinates.

The tests were not running on the CI, kkk.
I'll go back to the layer now.
The recent changes were:

added coverage
remove feats
update constructor
added some alias on the directed graph to be more similar to networkx
update constructor, I decided to use a list of edges rather than a sparse matrix, the sparse matrix would lead to some complications for non-consecutive node indexing or an empty graph.

Just noticed: I would rename BaseGraph to Graph and make it part of the public interface. This can for example be useful for typing during plugin development.

Just noticed: I would rename BaseGraph to Graph and make it part of the public interface. This can for example be useful for typing during plugin development.

I agree it's useful.
I'm afraid some people would try using Graph and get the abstract class error without trying the other classes.
Do you think renaming _BaseGraph to BaseGraph and making it public is a good compromise or it's about the same as having it named Graph?

@jwindhager what do you think is missing for us to merge this PR?
I'm going to write a few test cases for a graph without coordinates.

Hi @JoOkuma
From my point of view:

[ ] As you write: ensure that the graph works without coordinates
[ ] Make BaseGraph part of the public API (I agree with your suggestion!)
[ ] Improve error handling during adding/removal, see https://github.com/napari/napari-graph/pull/1#discussion_r1049728975 and https://github.com/JoOkuma/napari-graph/pull/8#issuecomment-1358767828
[ ] Address the remaining comments of @jni (if any?) and in my review comments above
[ ] Some more tests and documentation (incl. more verbose docstrings)

Happy to help, will continue to file PRs for you to review! :-)

Could we leave the documentation to another PR?

@JoOkuma @jwindhager @jni, I'm planning on digging into napari-graph while at the Janelia Cell Tracking hackathon (starting tomorrow for me).
If you have any thoughts, requests, etc., then please let me know.

Thanks, @kephale .
@jwindhager What do you think about merging this PR so we can improve it with other PRs?
This PR is huge already, and @jwindhager was (almost) done reviewing it.
I think not having this merged into main makes it more difficult for others to contribute.

Agreed @JoOkuma! 😊 🎉 🚀 here we go!

Thanks, @jni

Hey, apologies for the late reply! Yes, merging was definitely the right way to go forward :) Thanks @jni!


Option 1: Mono Repository with symlinks

Included local dependencies vectorclock, antidote-erlang-client, antidote_crdt, antidote_pb_codec, antidote_stats.
+

No structural changes to any project
Github workflow working directory change is enough to get workflows running
Simple

-

No shared configuration (common linting rules, dialyzer rules, etc.), configuration duplication
Including _checkouts feels like a hack
Explicit local dependency management via symlinks and rebar3.config dependencies
Including the Erlang client in another project as a dependency might be difficult

Other comments:

_build folders are not shared
Commands are executed in their respective folders
Local dependencies are not locked to a version

Closing in favor of #472


Log warning but don't fail when multiple pathcounts returned

Refs https://github.com/greenelab/hetmech-backend/issues/43

Logging output as of https://github.com/greenelab/hetmech-backend/pull/44/commits/01ad5c153af794f78207c881c91d84f5b03a2653 for http://localhost:8000/v1/query-paths/?source=8224&target=32460&metapath=GpBPpG is like:
WARNING:root:get_paths returned 2 results, but database should not have more than one row (including inverse orientation) for GpBPpG from 8224 to 32460.
  dgp_id      dwpc        id metapath_id       p_value  path_count  source_id  target_id
 5813985  6.344973  42509492      GpBPpG  8.401434e-14         146       8224      32460
 5862663  6.344973  42603777      GpBPpG  8.401434e-14         146      32460       8224
[02/May/2019 16:17:07] "GET /v1/query-paths/?source=8224&target=32460&metapath=GpBPpG HTTP/1.1" 200 236941


Change of name

As long as we're releasing this anew, what about a change of name? Since they are roles, what about Role::HTTP as the generic name, and then prefix Role:: to the current names?

Maybe better change the name to HTTP::Roles and then HTTP::Roles::Server and so on.

closing with #7 being merged


ITTT needs to be mentioned up front.

I didn't know how to control the system until I read the doc for days. ITTT should be mentioned at the start for context on reading the rest of the docs. If you accept this change, then the phases may need to be renamed in other parts of the docs.

Adding/renaming phases is a bit more than changing this page - point taken about IFTTT/control options being more prominent up front, though, so will close this PR and add it to the list for the re-org that's ongoing.


Quest bundles

I think it's kinda silly to have separate repos for every spec so I'm repurposing this repo as the qwiklabs-bundle-specs repo (we can rename it later).
The only interesting file in this change is quest-bundle-spec.md.

 Define what a quest bundle looks like

@jgan note/comment on:

Resources in whisperer.yaml are not prefixed by anything. Git Whisperer is responsible for seeing if a content ID matches a resource and adding type: Resource or type: Lab appropriately.

If the resource is not present, GW automatically assumes it's a lab

qwiklabs.yaml includes type: {Resource|Lab} so unbundling does not have to guess what a reference ID refers to.
whisperer.yaml lets you omit path in an options block if all of your options are "OR"s. path is added in qwiklabs.yaml by GW

In whisperer.yaml
  - choice:
      prompt:
        locales:
          en: Learn about compute options
      options:
        - content: intro-to-appengine-python
        - content: intro-to-kubernetes-engine
        - content: intro-to-cloud-functions

converted in qwiklabs.yaml
  - choice:
      prompt:
        locales:
          en: Learn about compute options
      options:
        - path:
          - type: Lab
            content: intro-to-appengine-python
        - path:
          - type: Lab
            content: intro-to-kubernetes-engine
        - path:
          - type: Lab
            content: intro-to-cloud-functions

Unrelated to anything in particular in this PR, I believe that labs should not be bundled inside of Quest Bundles and should exclusively be pulled from Alexandria. Bloat and versioning confusion being my two biggest concerns.


Stack Termination protection

Is there a configuration option to enable Cfn stack termination protection in the PCluster configuration file?

Hi @joehellmersNOAA , no there is no way to do it from pcluster config file at the moment. You'd have to set it after cluster creation is start by running something like aws cloudformation update-termination-protection --stack-name <CLUSTER_NAME> --enable-termination-protection

Thanks @demartinofra. I actually embedded my cluster create command in a shell script that does exactly that.
Can I put a request to make this enhancement?  I could either be an option in the configuration file, or it could be an option on the pcluster create-cluster command.

Yes, I think it makes total sense to have this as a create-cluster command option 👍🏻 Marking this as a feature request


App won't run if it's name is provided in a relative form

Wave SDK Version, OS
h2o-wave==0.26.3, Windows 10 build 19044
Actual behavior
App won't run if the path provided like ./app.py
(Happens while using Terminal's Tab-autocomplete). Makes things inconvinient
Expected behavior
App runs independently of way how application name is provided: "app.py" or ".\app.py", etc.
Steps To Reproduce

Open terminal
Run wave run .\app.py
See error message TypeError: the 'package' argument is required to perform a relative import for './app'

Thanks for the suggestion @AWRDev! The solution should be just a simple prefix trimming.


WASM

Just submitting my interest in having the ability to embed Passerine in a WASM game written in Rust.

Ah, that's pretty neat. Because Passerine doesn't have any deps, it's pretty easy to get it compiling on any architecture supported by Rust - that includes wasm32-wasi and wasm32-unknown-unknown. In fact, here's a screenshot I took the other day of me running passerine + aspen in wasmtime compiled with the wasm32-wasi toolchain:

Note that, however, this is compiling the Compiler + VM to wasm and running that; it's not actually producing wat or wasm binary or anything. Getting Passerine to compile down to wasm is an eventual goal of mine (it's on the roadmap I believe), but we can't compile down to anything lower than the VM until we have type-checking in place.

Another thing about Wasm: I'd like to add a playground to https://passerine.io; everything is in place for this to be possible right now. If anyone wants to experiment with making a web playground for Passerine, let me know.

Speaking of Wasm, I've got Passerine running in the browser. This is static and runs in-browser; we're not calling out to any server-side code:
https://user-images.githubusercontent.com/54823450/113659775-0b65f900-96a3-11eb-925d-a4edbeab9973.mov
I still need to add styling and so on, but I've confirmed it's possible to interact with JS from Rust by using the FFI. When we eventually redo https://passerine.io, we'll include this playground. The repo for the playground is https://github.com/vrtbl/playground.

This is amazing, thank you for looking into this!

Cross-referencing this issue here: https://github.com/vrtbl/playground/issues/1. This would require moving hoisting before desugaring, which is good because I think we need to rework the compilation pipeline slightly. Here's my proposal:

lex
parse
desugar (split from macro expansion)
hoist (move up before expansion)
expand (split from desugar)
infer
gen

And the then we'd also move all the types types for each step into a new module. I'm also thinking of refactoring the way Data, Lambda, and Closure work (reference counting lambdas, moving some data, like Heap and NotInit to the stack/VM). And the way the VM is initialized, and what it returns.
We also need to think about moving the FFI to external algebraic effects - i.e. the FFI is just a effect handler implemented in Rust.
At minimum, we need to remove stamp and nantagging to get Wasm 100% working. The above is later stuff - perhaps I'll open a new issue for that.

I've cleaned up the pipeline wrt the above issues, closing. See #52


Defaults: tab -> backspace for revert key?

tab is comfortable to press, and (in theory) works especially well together with right-hand keys, like enter (not sure, but the majority might use the right thumb for space too by default). The problem is that it so strongly evokes some kind of "forward" action/motion that I occasionally still hesitate before using it.
(Feel free to leave a thumbs up/down if you have nothing more to add, but agree/disagree with the idea.)

How about [,]? It has the meaning of backward and forward in vim, its about as comfortable to press as tab and enter (can you confirm? i've actually forgotten since i've used weird layout keyboards for so long). Its nicely symmetric. And it should be safe since its generally a movement command so wouldn't be needed after a leap.

The problem is these should be keys you wouldn't want to search for. As a prev/revert key both ideas are fine, but next_target should be something like enter/tab/etc. See also the most recent commit, I just hardcoded the current defaults, i.e. the assumption that the system only works well if it the three are mapped to the same key https://github.com/ggandor/leap.nvim/commit/3cc0e6a0b99dc18d4e5a88baa3cbe3c7b8b34566.

Tab can be somewhat confusing to people like me that are accustomed to TAB as a pane navigation keystroke


override the endpoint url

I am looking to write a test with the aws-sdk-cpp so that it connects to localstack.
From cli I can do:
aws --endpoint-url=http://localhost:4576 sqs list-queues
How to achieve this with aws-sdk-cpp ?
I have tried to override the url in config, but this way the client times out:
 clientConfiguration.endpointOverride = "http://localhost:4576";
 sqsClient = Aws::SQS::SQSClient( credentialsProvider, config );

What platform/OS are you using?
Ubuntu 16.04
What compiler are you using? what version?
gcc 6.3

Try this:
clientConfiguration.endpointOverride = "localhost:4576"; // remove the http:// part
clientConfiguration.scheme = Aws::Http::Scheme::HTTP; // the default is HTTPS, which will cause signature-v4 to sign with localhost, and it won't match

@marcomagdy Thanks a lot, that works


make jsx-handler-names error messages less specific

I realized the error messages were previously specifying a more specific method name than the rule actually enforced.
For example, onChange={this.itemClicked} would throw the warning Handler function for onChange prop key must be named handleChange, when really this.handleItemClick would (and should) pass.

Not sure why the checks have failed?

Thanks.

Not sure why the checks have failed?

Just a very small coverage decrease because you removed some tested lines, not an error for me.


Change the unit of RTT to microsecond

This change is

Sorry, the change to RTT unit has been made to the upstream code. So I have to close this PR.


Some got JVM OOM on running 31 retz-client simultaneously

Several processed got java.lang.OutOfMemoryError: unable to create new native thread on 16-cores, 48GB RAM machine.

Finally removed client-side Jetty WebSocket library at https://github.com/retz/retz/commit/e5ccb6e2deed4a1b8cbffd9603d481f5776e8ab6 , which could solve this? It still happened at 0.0.27.

$ ulimit -a
core file size          (blocks, -c) 0
data seg size           (kbytes, -d) unlimited
scheduling priority             (-e) 0
file size               (blocks, -f) unlimited
pending signals                 (-i) 31776
max locked memory       (kbytes, -l) 64
max memory size         (kbytes, -m) unlimited
open files                      (-n) 1024
pipe size            (512 bytes, -p) 8
POSIX message queues     (bytes, -q) 819200
real-time priority              (-r) 0
stack size              (kbytes, -s) 8192
cpu time               (seconds, -t) unlimited
max user processes              (-u) 31776
virtual memory          (kbytes, -v) unlimited
file locks                      (-x) unlimited
$ uname -a
Linux uenishi-vbox-ubuntu 4.4.0-45-generic #66-Ubuntu SMP Wed Oct 19 14:12:37 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux

On my above ubuntu, I couldn't reproduce this, but after ulimit -u 1024 I succeeded. Production environment also has max user process 1024 (CentOS 6).

Wasn't a bug.


AADConnect Support policy

[Enter feedback here]
Was the support recently changed? I'm pretty sure, an I have been telling customers this that the support Window was 18 months from date of a new version being released and now I see the page says 12 months?
Is it 12 or 18 months?

Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

ID: 57f5478b-3132-21d0-a420-a1140db235de
Version Independent ID: 266bbd16-2117-f680-6493-e183eb09fdbc
Content: Azure AD Connect: Version release history - Microsoft Entra
Content Source: articles/active-directory/hybrid/reference-connect-version-history.md
Service: active-directory
Sub-service: hybrid
GitHub Login: @billmath
Microsoft Alias: rodejo

@ve-petjohnson
Thanks for your feedback! We will investigate and update as appropriate.

I just want to make sure I'm giving my customer the right info..
From: YashikaTyagi @.>
Sent: Thursday, April 6, 2023 5:17 PM
To: MicrosoftDocs/azure-docs @.>
Cc: Peter Johnson (International Supplier) @.>; Mention @.>
Subject: Re: [MicrosoftDocs/azure-docs] AADConnect Support policy (Issue #107773)
@ve-petjohnsonhttps://github.com/ve-petjohnson
Thanks for your feedback! We will investigate and update as appropriate.

Reply to this email directly, view it on GitHubhttps://github.com/MicrosoftDocs/azure-docs/issues/107773#issuecomment-1499238606, or unsubscribehttps://github.com/notifications/unsubscribe-auth/A2X4LU3L3XUSRTQFTOULFCLW73NABANCNFSM6AAAAAAWVEGIFU.
You are receiving this because you were mentioned.Message ID<EMAIL_ADDRESS>

@ve-petjohnson
According to the Azure AD Connect version release history, the support window for Azure AD Connect is 12 months from the date of a new version being released. The page you mentioned also confirms this information.

@ve-petjohnson
We are going to close this thread as resolved but if there are any further questions regarding the documentation, please tag me in your reply and we will be happy to continue the conversation


chore: switch rbe to buildbuddy

Matches https://github.com/aspect-build/rules_js/pull/1241

NB: this is blocked on aspect CLI not supporting custom flags, needs a fix in the flag parser.


default-props-match-prop-types false positive with ...unpacking

const testShape = {
  isDeleted: PropTypes.bool,
};

const Foo = ({id, caption, custom, isDeleted}) => {
  console.log(id, caption, custom, isDeleted);
  return
test
;
};

Foo.propTypes = {
  custom: PropTypes.bool.isRequired,
  ...testShape,
};

Foo.defaultProps = {
  isDeleted: false,
};

The isDeleted: false line is shown as having an error:
defaultProp "isDeleted" has no corresponding propTypes declaration. eslint(react/default-props-match-prop-types)

If I remove the custom prop from propTypes the error disappears.
eslint v7.32.0
eslint-plugin-react 7.24.0

Dynamically constructing propTypes makes static analysis impossible, except in this exact situation: when the object being spread is statically defined in the same file.
I’d be happy to review a PR that improved propType detection to handle this case, but my suspicion is that you’re much better off explicitly repeating every prop type, both for clarity and for linting.

Closing, but still happy to review such a PR.


bulk importing gets slower and slower

My Environment

ArangoDB Version:        3.4.6-1
Storage Engine:             RocksDB
Deployment Mode:       Single Server
Deployment Strategy:   ArangoDB Starter

Problem:
Parallel bulk import, after about 20 minutes, the import speed slows down and keeps down. After restart arangod service, the speed recovers normal. But after a while, it slows down again. Hours later, everything timed out. Any query timed out, even arangosh can't connect to arangodb.
Expected result:
The speed keeps steady.

I find that disk  io-write is very heavy.
avg-cpu:  %user   %nice %system %iowait  %steal   %idle
           9.83    4.59    7.10    0.03    0.00   78.46

Device:            tps    kB_read/s    kB_wrtn/s    kB_read    kB_wrtn
sda               0.00         0.00         0.00          0          0
nvme0n1          32.00         0.00       128.00          0        128
nvme1n1       85854.00         0.00    397796.00          0     397796
dm-0          86653.00         0.00    400992.00          0     400992

avg-cpu:  %user   %nice %system %iowait  %steal   %idle
           7.91    5.41    7.11    0.03    0.00   79.54

Device:            tps    kB_read/s    kB_wrtn/s    kB_read    kB_wrtn
sda               0.00         0.00         0.00          0          0
nvme0n1          17.00         0.00       116.00          0        116
nvme1n1       87829.00         0.00    405712.00          0     405712
dm-0          87079.00         0.00    402760.00          0     402760

avg-cpu:  %user   %nice %system %iowait  %steal   %idle
           7.63    5.63    7.12    0.01    0.00   79.61

Device:            tps    kB_read/s    kB_wrtn/s    kB_read    kB_wrtn
sda               2.00         0.00        40.00          0         40
nvme0n1           1.00         0.00         4.00          0          4
nvme1n1       89671.00         0.00    390376.00          0     390376
dm-0          89672.00         0.00    390380.00          0     390380

Maybe it's the hard limit of this machine, and has nothing to do with arangodb?


Move ocm/docs to ocm-spec/doc

[ ] Compare and apply all the changes that are in docs files that are missing from the corresponding ocm-spec/doc files
[ ] Delete duplicate documentation files from this repo so that ocm-spec is the SoT

Feel free to split this ticket or create multiple PRs if the diff/number of files changed is too much and makes it hard to review the changes.

I suggest to drop
docs/formats
docs/labels
docs/names
docs/ocm

entirely as this is contained in the spec and does not belong to CLI/lib


Shows Loading... when there are no records

The WebUI shows loading when no records are returned from the api as there are no records in the database. It should rather show a message that indicates that no records are present.
I would like to work on this.

It occur due to the following line
index = Object.keys(json['data'][0])[settings.aLastSort[0].col]

This gives error because the length of json['data'] array is 0 and we try to access the first element. This blocks the further code.


Apple Music

Is there a chance of integrating Apple Music with this?

No

More info here:
https://github.com/insidegui/AnimojiStudio/issues/11#issuecomment-344716228


Is it usable to angular 13

Is it usable to angular 13? I am trying to use it my angular 13 project but not working. can you help me?

Hi,
The plugin is vanilla JavaScript so it will not work with the dom dynamic render of angular or react. You should destroy the google instance and construct the toggle instance with the js api each time the component is dismounted and mounted

Refers #128


⚠ Minecraft has degraded performance

In 8b4452e, Minecraft (https://www.minecraft.net) experienced degraded performance:

HTTP code: 200
Response time: 1066 ms

Resolved: Minecraft performance has improved in 64f27a0.


Provide Template Tag to generate data-reflex html attributes

Feature Request
Currently reflex attributes have to be hand-craftet inside the templates. A custom tag could help users to get these right.
Is your feature request related to a problem?
No
Describe the solution you'd like
I suggest a template tag like: {% stimulus 'lazy_load_reflex#increment' count=count increment=1 %}
which would be used in a Template like
Increment {{ count }}

and would generate the following HTML (formatted differently)
Lazy_LoadReflex#increment"
        data-count="0"
        data-increment="1"
>Increment {{ count }}

PR link
https://github.com/jonathan-s/django-sockpuppet/pull/60

Stimulus also happens to be the name of the front-end framework where it's entirely possible to build an entire UI without once ever referencing the server past the initial page load, so a tag should not be targeted at the subset functionality of this package while being labeled more generally, as that would be confusing.
I think it actually makes sense to have a stimulus tag and a reflex tag. You don't use them on the same element, in most cases, since a Stimulus controller is likely to manage a whole component while Reflexes are fired by individual controls inside that component.

What ultimately gets my knickers in a twist is the possibility of doing something like
{% for user in users %}

    {{ user.name }}

    Tell them how cool they are.

{% endfor %}

Things to ponder

A Stimulus controller can appear multiple times on a page and a full-fledged UI written in Stimulus is likely to have multiple controllers. It's much easier to compile data-attributes in OOP code with full access to things like dicts and tuples than it is to write everything out in a clunky template language, so it makes sense to ship the guts of whole controllers with the context so that you can programmatically reason about the details with the full power of Python behind you. It might be graceful from the end-developer perspective to have the template tag accept both dot notation to a dict in the context and a series of arguments, but I personally want to move my controller details out of the templates and into context as much as I can.
Stimulus tracks data-attributes with controller-namespaced names (eg. data-user-id="", data-user-friendslist-class="") and it's important to be able to dole those out correctly.
Stimulus also allows multiple controllers per element, so it might be necessary to have the ability to reason about that built into the tag. The controller names have to live on the same data-attribute, so they'd have to be defined in one template tag (which can be smart enough to assign all of the Values/Classes data to the appropriate places).
Stimulus 2 uses data-user-target="avatar syntax, and targets have to be inside a controller. An element can have as many target identifiers as you like, but identifiers for the same controller have to live on the same attribute.
Multiple actions can live on the same element, and they have to be in the same attribute. They can be for different controllers, and the required minimum syntax changes depending on the element in question.
An element with a data-controller and a data-reflex actually has two controllers, one explicit and one implicit. The implicit controller is attached by stimulus_reflex at page load.
data-reflex is a wrapper around data-action that does relatively little on the client and runs this.stimulate(). Some controllers will want to do client-side processing or messaging around the reflex actions, so even in a case where most of the interactivity is going through your server, you don't want to hamstring Stimulus. These methods aren't compatible. When you trigger the data-action on an element, you have to call this.stimulate() yourself unless you've also triggered the data-reflex, and when you trigger the data-reflex the explicit controller has no way of tracking that reflex because you've gone through a different controller.
Multiple reflexes can live on the same element, and they have to be in the same attribute.
Reflexes also use data attributes, but they don't have to be controller-namespaced. This is something where people could get tripped up, with their Reflexes recognizing data that their controllers don't.

Stimulus tracks data-attributes with controller-namespaced names (eg. data-user-id="", data-user-friendslist-class="") and it's important to be able to dole those out correctly.

Yes, this is the new stimulus 2.0 syntax. The current docs still contain syntax for stimulus 2.0

It's an interesting idea using
{% stimulus_controller 'example_reflex' %}

{% endcontroller %}

However controllers can be nested like this.

ExampleReflex#increment">

OtherReflex#do_something">

From what I can tell the stimulus_controller won't handle nesting particularly well.
When thinking about this we really have two concepts here that are easy to conflate. We've got stimulus and reflex. They just happen to share some attributes. So it could be wise to separate the two.
So if we have a reflex template tag that only cares about name, action and method to generate. It would also make sure to validate that we've got a reflex in the backend and that it has the method, if not it would throw an error.
{% reflex name="MyReflex" action="click" method="my_method" %}

data-reflex="click->MyReflex#my_method"

Then we could have a stimulus tag that could generate all the data other attributes.
One of the slightly annoying bits in stimulus2.0 is that there is syntax that looks like this, the data attributes become fairly verbose.
https://stimulus.hotwire.dev/reference/values

https://stimulus.hotwire.dev/reference/targets
<form data-controller="search checkbox">
  <input type="checkbox" data-search-target="projects" data-checkbox-target="input">
  <input type="checkbox" data-search-target="messages" data-checkbox-target="input">
  …
</form>

https://stimulus.hotwire.dev/reference/css-classes
<form data-controller="search"
      data-search-loading-class="search--busy"
      data-search-no-results-class="search--empty"
>

# Stimulus can also access normal data attributes. The data attributes don't belong to any particular controller.

Personally I'd be happy to limit the current PR for reflex things only to limit the scope. Getting a good solution for the stimulus parts seems to increase the scope quite dramatically.
Thoughts on this @DamnedScholar and @JulianFeinauer?

@jonathan-s I agree with your comment but thats also possible at the moment. In fact, the *_reflex tag can optionally get two list parameters. Then, the first is the controller and the second the method, like that example (from tag_example.html):
click me

If the rexlex is defined INSIDE a {% stimulus 'xx' %} Block it is allowed to not give a controller (and the one from the stimulus tag is used).
Of cours all of this is undocumented but.. just to give you some context.
The nice thing would be that we isolate all the technical details away from the user.

@DamnedScholar I added the possibility to pass a dict to the *_reflex functions which contains information about controller, reflex and parameters. You can see this in the test test_tag_by_dict where a single dict from the context is used for parametrization.

So, when stimulus_reflex wakes up, it goes through and attaches a new controller to every element with a data-reflex. Unless I misunderstand something, I don't think there's any chance to convert a declared Reflex into a normal action that triggers your normal controller. The data-reflex syntax never allows you to specify a controller, while it's explicit inside data-action.

@DamnedScholar to clarify... I do this in Django and insert the controller on the reflex (as it's needed).

I've been thinking on this for a few days and this an alternative and I think this api for the templatetag could work pretty well.
# The following allows you to add multiple reflexes as a first argument and is shorter.
{% reflex 'click->MyReflex#method' param="param1" param2="param" combined=True permanent=True %}

# this would expand to

data-reflex="click->MyReflex#method"
data-param="param1"
data-param2="param"
dataset-reflex-dataset="combined"
data-reflex-permanent

For the stimulus controller itself. I would suggest
# We can have several actions.
{% stimulus controller='calendar' (optional) for="calendar" (optional) v-myvalue="value" t-mytarget="target" c-myclass="myclass" action="click->calendar#next" param="param1" %}

# Either "controller" or "for" needs to be defined. controller would expand
# to data-controller="calendar" `for` would be used if this is applied
# to a child element of where the parent already has controller defined.
# Ie data-controller is omitted, but the "for" value is used for to get the correct
# data.

# all in all this would generate the following code

data-controller="calendar"
data-calendar-myvalue-value="value"
data-calendar-target="target"
data-calendar-myclass-class="myclass"
data-action="click->calendar#next"
data-param="param1"

I think this hits the balance of giving flexibility while still being less verbose. Plus it's possible to do validation if you are so inclined. It might be that you can't write t-mytarget ie using hyphen. If not, we could have this be t_mytarget.
And just a note, it looks like rails use this as a template tag.
{% data param="1" param2="2" %} which would expand to data-param="1" data-param2="2"


initial check in

In this PR I handle a case where a template calls a Filter that expects hl7 data but what was passed in was fhir. So, in this case there is no hl7 passed in and it fails with a generic message (ie Internal server error with 500) in the convert. This change is needed so that in convert we can catch this specific case and respond with a better message.

@microsoft-github-policy-service agree company="Microsoft"

@microsoft-github-policy-service agree company="Microsoft"

Curious, are there similar cases for other incorrect data type combinations that might also be resulting in a 500 when they should be resulting in a 400 (i.e. what happens today if we specify that we expect Ccda format but the data that is passed in is hL7V2)?

Curious, are there similar cases for other incorrect data type combinations that might also be resulting in a 500 when they should be resulting in a 400 (i.e. what happens today if we specify that we expect Ccda format but the data that is passed in is hL7V2)?

I did try convertToFhir I passed in input data format hl7v2 and root template name Hl7v2/ADT_A01 but the data I passed in was fhir. I thought that behavior would be the same, but I got a different error with a status code of 400.
{
  "error": {
    "code": "InvalidInputData",
    "message": "The InputDataString value provided is invalid.",
    "innerError": {
      "code": "InputParsingError",
      "message": "There was an error parsing the InputDataString: The input data could not be parsed correctly: The HL7 v2 message is invalid, first segment id = {\"r.. Ensure that the InputDataString is of the format specified in InputDataFormat."
    }
  }
}

This error could also work in my case. In fact, I think this is exact same situation but seems like the handling of this is different. Maybe I should look closer at how this one is being handled.

@psapozh82 , @ShaunDonn2 - Based on the PR description, can you clarify if the bug originally was that instead of Hl7v2 data, FHIR data was being passed for conversion and causing a 500 due to unhandled null exception in the filters?
If so, how did this input pass through the hl7v2 parser logic when we initially try to deserialize the input? Wouldn't it fai there if FHIR data was provided? If not, I would expect us to handle it there and fail fast instead of having it get till the template render part.

Hi @pallar-ms
The bug was that I was calling convertToHl7v2, passing in fhir for input data format and input data. But for root template I was passing in Hl7v2/ADT_A01. This root template is what called the SegmentFilter and was assuming that hl7 was in that context but it was fhir rather.


UB: creation of uninitialized array of u8

This code executes UB: https://github.com/rusticata/rusticata-macros/blob/d0e0ab4cb4e060c37bfcbb0c2eebe1325186cad6/src/macros.rs#L157-L159
This code was added as a replacement for mem::uninitialized in https://github.com/rusticata/rusticata-macros/commit/b66c6ed01b592d1545ddc5aadee42aac4c13eb4e, but it fails to address the reason that mem::uninitialized was deprecated. This code is just as UB as calling mem::uninitialized. See the docs for mem::uninitialized: https://doc.rust-lang.org/stable/core/mem/fn.uninitialized.html

Hi,
Thanks for the report. First of all, this function was only added as a "it may serve later" function, and is not used anywhere in rusticata's parsers so there is no immediate urgency nor directly impacted crate. Of course, if there is an UB it is important to fix as quickly as possible.
If I understand correctly, the proper fix is to use write (or similar) functions before calling assume_init? If so, I will release a new version quickly.

As the macro was not used anywhere, and should have been rewritten to use try_from anyway (and as a function, not a macro), I decided to remove it.


Fix npm vulnerabilities

upgrade replace to 1.0.0 to fix vulnerabilities in minimatch
add package.json to install dev dependencies
add autorest as dependency
update generateclient script to use local packages

Pull Request Test Coverage Report for Build 42006

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 51.828%

Totals

Change from base Build 41912:
0.0%

Covered Lines:
4821

Relevant Lines:
9302

💛  - Coveralls


I'm newbie

I'm starting using github. How I can put my code to repository?
I'm configure propertly
$ ssh -T<EMAIL_ADDRESS>Hi xor256! You've successfully authenticated, but GitHub does not provide shell access.
but
$ git push
ERROR: Permission to mrubyc/mrubyc.git denied to xor256.
fatal: Could not read from remote repository.

You need to fork original repository and push in it. After this you should do pull-request to ask original repository maintainer to merge your code in upstream repository. This link will be useful for you

ok

is possible to delete this issue ?

@xor256 you need to just close it. Button is located below comment field (near green comment button)


 IMHO ~/.awsless must only be used to store awless-centric informations.

Hi, thanks for the feedback.
What is you use case ? Do you want to read existing keys already stored in ~/.ssh or write your new keys (generated with awless create keypair) in ~/.ssh ?
We didn't want to write in ~/.ssh folder without user authorization. So perhaps we could at least read keys from both ~/.awless/keys and ~/.ssh. Otherwise, if you also would like to generate keys directly in ~/.ssh we could provide a config parameter to change the keys folder.

Hi

What is you use case ? Do you want to read existing keys already stored in ~/.ssh

Yep.

So perhaps we could at least read keys from both ~/.awless/keys and ~/.ssh. Otherwise, if you also would like to generate keys directly in ~/.ssh we could provide a config parameter to change the keys folder.

Both is fine to me.


entry.WriteToDirectory

This method is missing?

I guess the extract RAR example here is wrong https://github.com/adamhathcock/sharpcompress/blob/master/USAGE.md
The Archive example here works:
https://sharpcompress.codeplex.com/wikipage?title=Composite API Examples

@Ethan872 It's only missing if you're on a platform that doesn't support File operations like phones.
@aximili no, that code sample is wrong unless you're on an old version.


doc: Avoid duplicating the code in github-oauth/astro.md code example

Thanks for the hard work 👍🏻
It is working well.

I get that there's some duplicate code, but I personally find the current code to be easier to follow

I've moved the v3 source code to the v3 branch. You can create a new PR against the new branch if you'd like but I'll be deprecating v3 next year. See https://github.com/lucia-auth/lucia/discussions/1714


[Monitoring V2] UI Requirements

Overview
Minimum Requirements for Release:

Basic Configuration (https://github.com/rancher/dashboard/issues/908)
Advanced Configuration (https://github.com/rancher/dashboard/issues/909)

Fast Followups for Release:

Minor updates to defaults in the basic configuration (https://github.com/rancher/dashboard/issues/1128)
Add field for ignoreNamespaceSelectors (https://github.com/rancher/dashboard/issues/1129)
Add RKE2 as a Cluster Type (https://github.com/rancher/dashboard/issues/1130)
Update namespace from monitoring-system to cattle-monitoring-system (https://github.com/rancher/dashboard/issues/1131)
Prevent deploy when Prometheus Operator already exists (https://github.com/rancher/dashboard/issues/1167)
Expose global fields to construct proxy URLs for chart deployment (https://github.com/rancher/dashboard/issues/1168)
Feature Overview page (https://github.com/rancher/dashboard/issues/1064)
Navigation Bar (https://github.com/rancher/dashboard/issues/1215)
Minor fixes (https://github.com/rancher/dashboard/issues/1230)
Move Prometheus / Alertmanager from Overview to Navigation Bar (https://github.com/rancher/dashboard/issues/1260)

Additional Requests (in order of prioritization):

Feature Overview Page: CRD Summary (https://github.com/rancher/dashboard/issues/1175)
A UI for creating / configuring Prometheus CRs (https://github.com/rancher/dashboard/issues/808)
Display graphs in cluster overview dashboard graphs (https://github.com/rancher/dashboard/issues/812)
Custom UI Component for Grafana Dashboard (https://github.com/rancher/dashboard/issues/806)
Custom UI Component for Grafana Datasource (https://github.com/rancher/dashboard/issues/807)
A UI for creating / configuring ServiceMonitor CRs (https://github.com/rancher/dashboard/issues/809)
A UI for creating / configuring PodMonitor CRs (https://github.com/rancher/dashboard/issues/810)
RFE: Ability for users to test out AlertManager configurations https://github.com/rancher/dashboard/issues/1187

In the below UI specifications, any nil value mentioned is an optional setting and should ideally show a button that says Configure next to it. Once shown, users should be able to make it nil again by clicking on a button that says Remove.
I also make a reference to UIs for the following components:
LabelSelector
UI for a k8s.io/apimachinery/pkg/apis/meta/v1.LabelSelector
Default is nil. If nil, this should submit {}.

Header / Label Name
k8s YAML
Input
Default

Match Labels
*.matchLabels
key: value inputs
nil

Match Expressions
*.matchExpressions
key: Stringoperator: Dropdown (In, NotIn, Exists and DoesNotExist)values: List of Strings. Only required to have at least one element if operator is In or NotIn, otherwise disabled.
nil

NamespaceSelector
UI for a github.com/coreos/prometheus-operator/pkg/client/monitoring/v1.NamespaceSelector

Header / Label Name
k8s YAML
Input
Default

Use All Namespaces
any
Boolean
True

Whitelist of Namespaces
*.matchNames
Ability to select multiple namespaces within a cluster (Dropdown)
nil

If Use All Namespaces is selected, Whitelist of Namespaces should be disabled.
Custom UI Components
Collection View: Viewing a collection of these components should display all ConfigMaps and Secrets in the namespace that have the particular label attached to them. There should also be a column that displays whether the given resource is defined as a ConfigMap or a Secret.
Grafana Dashboard
A ConfigMap or Secret with a particular label grafana_dashboard that persists a Grafana dashboard.
Type Help Text: ConfigMaps should be used for storing Grafana Dashboards unless Secrets are specifically required.

Header / Label Name
k8s YAML
Input
Default

Type
kind
Radio button for ConfigMap or Secret
ConfigMap

Labels
metadata.labels.<key>
key: value inputs
grafana_dashboard:1

Per Dashboard:

Header / Label Name
k8s YAML
Input
Default

Filename
data.<name>
String (needs to be acceptable as k8s key, so no spaces)
dashboard.json

Dashboard JSON
Value at data.<name>
JSON
nil

There should be a + button under the Dashboards that allows users to submit multiple name:dashboard.json pairs. There should also be a Remove button on each Dashboard to allow them to be removed.
Grafana Datasource
A ConfigMap or Secret with a particular label grafana_datasource that adds a Grafana datasource.
Type Help Text: Secrets should be used to store Grafana Datasources to avoid leaking sensitive information that configures access to the datasource.

Header / Label Name
k8s YAML
Input
Default

Type
kind
Radio button for ConfigMap or Secret
Secret

Labels
metadata.labels.<key>
key: value inputs
grafana_datasource: 1

Per Datasource:

Header / Label Name
k8s YAML
Input
Default

Filename
data.<name>
String (needs to be acceptable as k8s key, so no spaces)
datasource.yaml

Datasource
Value at data.<name>
YAML
nil

There should be a + button under the Datasources that allows users to submit multiple name:datasource.yaml pairs. There should also be a Remove button on each Datasource to allow them to be removed.
On create/edit, user should be notified via banner that they need to restart their Grafana deployment to see changes (based on the Grafana docs).
UI for CRDs
Prometheus
Configures a Prometheus server deployment based on selected ServiceMonitors, PodMonitors, and PrometheusRules
Namespace Selectors Help Text: Allows you to select resources from namespaces by labels attached to namespaces. If not configured, the namespace of the Prometheus CRD is selected.
Label Selectors Help Text: Allows you to filter resources within the selected namespaces by labels attached to the resource. If not configured, all resources are selected in the selected namespaces.
ServiceMonitor

Header / Label Name
k8s YAML
Input
Default

Namespace Selector
spec.serviceMonitorNamespaceSelector
See LabelSelector
nil

Labels Selector
spec.serviceMonitorSelector
See LabelSelector
nil

If possible, we should provide links to all ServiceMonitors which match the Labels Selector within all Namespaces that match the Namespace Selector here.
PodMonitors

Header / Label Name
k8s YAML
Input
Default

Namespace Selector
spec.podMonitorNamespaceSelector
See LabelSelector
nil

Labels Selector
spec.podMonitorSelector
See LabelSelector
nil

If possible, we should provide links to all PodMonitors which match the Labels Selector within all Namespaces that match the Namespace Selector here.
PrometheusRules

Header / Label Name
k8s YAML
Input
Default

Namespace Selector
spec.rulesNamespaceSelector
See LabelSelector
nil

Labels Selector
spec.rulesSelector
See LabelSelector
nil

If possible, we should provide links to all PrometheusRules which match the Labels Selector within all Namespaces that match the Namespace Selector here.
AlertManagers (default is empty list)

Header / Label Name
k8s YAML
Input
Default

Namespace
spec.alerting.alertmanagers[i].namespace
Dropdown list of namespaces with ability to supply free-form text
cattle-monitoring

Name
spec.alerting.alertmanagers[i].name
Dropdown list of names of AlertManagers within the selected namespace with ability to supply free-form text; should be disabled if namespace is not selected yet
cattle-monitoring

Port
spec.alerting.alertmanagers[i].port
Integer
9093

Scheme
.spec.alerting.alertmanagers[i].scheme
Dropdown of http or https
nil

Path Prefix
.spec.alerting.alertmanagers[i].pathPrefix
String
nil

TLS Config
.spec.alerting.alertmanagers[I].tlsConfig
YAML
nil

Bearer Token File for AlertManager
.spec.alerting.alertmanagers[I].bearerTokenFile
String
nil

There should be a + button under the AlertManagers that allows users to submit multiple create more AlertManager configurations. There should also be a Remove button on each AlertManager to allow them to be removed.
Storage
If spec.storage is missing (or on creating a new Prometheus resource), there should be a button that says Configure. If it exists (i.e. modifying an existing resource), the radio button value mentioned in the next step will be determined based on whether spec.storage.emptyDir or spec.storage.volumeClaimTemplate exists; if both are defined, spec.storage.emptyDir will take priority.
Upon clicking on Configure, a radio button should be shown which has two options: EmptyDir or VolumeClaimTemplate. EmptyDir should be selected by default.
If EmptyDir is selected, the following fields should be shown:

Header / Label Name
k8s YAML
Input
Default

Medium
spec.storage.emptyDir.medium
Radio button for Use nodes default medium (i.e. "") or Mount a tmpfs (RAM-backed filesystem)  (i.e. "Memory")
""

Size Limit
spec.storage.emptyDir.sizeLimit
String (Quantity)
nil

If VolumeClaimTemplate is selected, the following fields should be shown:

Header / Label Name
k8s YAML
Input
Default

Metadata
spec.storage.volumeClaimTemplate.metadata
YAML
nil

Spec
spec.storage.volumeClaimTemplate.spec
YAML
nil

At the bottom, a button that says Remove should be shown that removes spec.storage entirely. After clicking on this button, Configure should be shown once again.
Secrets

Header / Label Name
k8s YAML
Input
Default

Additional Scrape Configurations
.spec.additionalScrapeConfigs
name: String  key: String
nil

Additional AlertManager Configurations
.spec.additionalAlertManagerConfigs
name: String  key: String
nil

Additional AlertManager Relabel Configurations
.spec.additionalAlertRelabelConfigs
name: String  key: String
nil

If possible, name should be represented by a dropdown with the names of all the keys in the same namespace as the Prometheus CRD and key should be represented as a dropdown with the list of keys in the Secret selected in name. If this is not possible, string inputs for both values should be good, as represented above.
ServiceMonitor
Generates the scrape configuration of a Prometheus instance based on labeled Services.
Namespace Selectors Help Text: Allows you to restrict namespaces of Service resources that can be monitored. By default, the ServiceMonitor monitors all namespaces.
Label Selectors Help Text: Allows you to identify Services to monitor by the labels on each Service. By default, no Services are monitored.

Header / Label Name
k8s YAML
Input
Default

Namespace Selector
spec.namespaceSelector
See NamespaceSelector
nil

Labels Selector
spec.selector
See LabelSelector
{}

Endpoints
spec.endpoints
YAML
Empty

Job Label
spec.jobLabel
String
nil

Target Labels
spec.targetLabels
List of Strings
nil

Pod Target Labels
spec.podTargetLabels
List of Strings
nil

Maximum Samples Per Scrape
spec.sampleLimit
uint64
nil

If possible, we should provide links to all Services which match the Labels Selector within all Namespaces that match the Namespace Selector here.
PodMonitor
Generates the scrape configuration of a Prometheus instance based on labeled Pods.
Namespace Selectors Help Text: Allows you to restrict namespaces of Pod resources that can be monitored. By default, the PodMonitor monitors all namespaces.
Label Selectors Help Text: Allows you to identify Pods to monitor by the labels on each Pod. By default, no Pods are monitored.

Header / Label Name
k8s YAML
Input
Default

Namespace Selector
spec.namespaceSelector
See NamespaceSelector
nil

Labels Selector
spec.selector
See LabelSelector
{}

Endpoints
spec.podMetricsEndpoints
YAML
Empty

Job Label
spec.jobLabel
String
nil

Pod Target Labels
spec.podTargetLabels
List of Strings
nil

Maximum Samples Per Scrape
spec.sampleLimit
uint64
nil

If possible, we should provide links to all Pods which match the Labels Selector within all Namespaces that match the Namespace Selector here.

As these are mostly epics for the entire UI requirements of the feature, I"m going to remove the milestone as all tickets for the feature are tracked separately.

I'm going to close this ticket even though several tickets in it aren't done, but the overall progress on all the other tickets will be tracked in the currently open remaining issues.


Make verbose option to log all the CDP traffic in Mapper Tab

I re-worked the solution and switched to a dedicated binding for debugging, which is more logical.


Update replicator.dbl

fix manual batch mode processing, only delete current instruction when instruction completed

Fixed commit mode = manual it was trying to delete completed instructions in a repeat loop, not singularly.


Bump appium java-client to 5.0.3

[x] By placing an X in the preceding checkbox, I verify that I am a PayPal employee or
I have signed the Contributor License Agreement

Bump appium java-client to 5.0.3

Also updated the swipe and tap methods of SeLionAppiumAndroidDriver and
SeLionAppiumIOSDriver to use TouchActions  -- both methods were removed
from appium java-client
Removed no-op rotation methods which now have implmentations in appium
java-cient

@vikram1711 @elhuang can I also solicit your review of this change set?


Proven always returns unsuccessful response 422

Hi Taiko team,
I have run the Taiko proposal node from this script https://github.com/taikoxyz/simple-taiko-node. And I try to connect to all of the proven listed on Proven Market.
All the node return unsuccessful response 422.
Logs:
simple-taiko-node-taiko_client_proposer-1  | INFO [12-13|04:03:50.671] Attempting to assign prover              endpoint=http://<IP_ADDRESS>:9876  fee=110 expiry=1,702,442,030
simple-taiko-node-taiko_client_proposer-1  | WARN [12-13|04:03:50.724] Failed to assign prover                  endpoint=http://<IP_ADDRESS>:9876  error="unsuccessful response 422"
simple-taiko-node-taiko_client_proposer-1  | INFO [12-13|04:03:50.724] Attempting to assign prover              endpoint=http://<IP_ADDRESS>:9876   fee=110 expiry=1,702,442,030
simple-taiko-node-taiko_client_proposer-1  | WARN [12-13|04:03:51.030] Failed to assign prover                  endpoint=http://<IP_ADDRESS>:9876   error="unsuccessful response 422"
simple-taiko-node-taiko_client_proposer-1  | INFO [12-13|04:03:51.030] Attempting to assign prover              endpoint=http://<IP_ADDRESS>:9876 fee=110 expiry=1,702,442,030
simple-taiko-node-taiko_client_proposer-1  | WARN [12-13|04:03:51.479] Failed to assign prover                  endpoint=http://<IP_ADDRESS>:9876 error="unsuccessful response 422"
simple-taiko-node-taiko_client_proposer-1  | INFO [12-13|04:03:51.498] Attempting to assign prover              endpoint=http://<IP_ADDRESS>:9876  fee=120 expiry=1,702,442,031
simple-taiko-node-taiko_client_proposer-1  | WARN [12-13|04:03:51.585] Failed to assign prover                  endpoint=http://<IP_ADDRESS>:9876  error="unsuccessful response 422"
simple-taiko-node-taiko_client_proposer-1  | INFO [12-13|04:03:51.594] Attempting to assign prover              endpoint=http://<IP_ADDRESS>:9876   fee=120 expiry=1,702,442,031
simple-taiko-node-taiko_client_proposer-1  | WARN [12-13|04:03:51.910] Failed to assign prover                  endpoint=http://<IP_ADDRESS>:9876   error="unsuccessful response 422"
simple-taiko-node-taiko_client_proposer-1  | INFO [12-13|04:03:51.912] Attempting to assign prover              endpoint=http://<IP_ADDRESS>:9876 fee=120 expiry=1,702,442,031
simple-taiko-node-taiko_client_proposer-1  | WARN [12-13|04:03:52.347] Failed to assign prover                  endpoint=http://<IP_ADDRESS>:9876 error="unsuccessful response 422"
simple-taiko-node-taiko_client_proposer-1  | ERROR[12-13|04:03:52.348] Proposing operation error                error="failed to propose transactions: failed to propose transactions: unable to find prover"

Hi,
I was experiencing the same issue, and it was resolved as follows:
You can add all the provers in the prover market (https://taiko.xyz/docs/reference/prover-market-page) separated by commas. Then, you can increase the BLOCK_PROPOSAL_FEE parameter. For example: 50

Thanks, I already fixed the problem.


Furthermore:

using net host works just fine - this definitely has to do with bridge
using a different nameserver (sudo nerdctl run --dns <IP_ADDRESS> --rm -ti debian bash) does NOT fix the problem
using docker with the same images, on the same host, works just fine

Since this is working with alpine, my intuition is to blame glibc.
@AkihiroSuda does this problem sound familiar in any way?
Any pointer on how to debug this?
Steps to reproduce the issue
No response
Describe the results you received and expected
na
What version of nerdctl are you using?
Host is:
apo@amaterasu:~/post $ uname -a
Linux amaterasu 6.6.51+rpt-rpi-v8 #1 SMP PREEMPT Debian 1:6.6.51-1+rpt3 (2024-10-08) aarch64 GNU/Linux
apo@amaterasu:~/post $ cat /etc/issue
Debian GNU/Linux 12 \n \l

apo@amaterasu:~/post $ sudo nerdctl version
WARN[0000] unable to determine buildctl version: exec: "buildctl": executable file not found in $PATH
Client:
 Version:	v2.0.0
 OS/Arch:	linux/arm64
 Git commit:	ef588dafa080e3dbc9c061ff3802affb66aef291
 buildctl:
  Version:

Server:
 containerd:
  Version:	1.7.23
  GitCommit:	57f17b0a6295a39009d861b89e3b3b87b005ca27
 runc:
  Version:	1.1.14
  GitCommit:	v1.1.14-0-g2c9f560

apo@amaterasu:~/post $ sudo nerdctl info
Client:
 Namespace:	default
 Debug Mode:	false

Server:
 Server Version: 1.7.23
 Storage Driver: overlayfs
 Logging Driver: json-file
  Cgroup Driver:  : systemd
  Cgroup Version: : 2
 Plugins:
  Log:     fluentd journald json-file none syslog
  Storage: native overlayfs
 Security Options:
  seccomp
   Profile:	builtin
  cgroupns
 Kernel Version:   6.6.51+rpt-rpi-v8
 Operating System: Debian GNU/Linux 12 (bookworm)
 OSType:           linux
 Architecture:     aarch64
 CPUs:             4
 Total Memory:     3.703GiB
 Name:             amaterasu
 ID:               928b00e8-0257-43b5-be2c-5016e071c1f0

WARNING: No memory limit support
WARNING: No swap limit support
WARNING: bridge-nf-call-iptables is disabled
WARNING: bridge-nf-call-ip6tables is disabled

apo@amaterasu:~/post $ /opt/cni/bin/bridge --version
CNI bridge plugin v1.5.1
CNI protocol versions supported: 0.1.0, 0.2.0, 0.3.0, 0.3.1, 0.4.0, 1.0.0

Are you using a variant of nerdctl? (e.g., Rancher Desktop)
None
Host information
No response

Tried a bunch of cni versions (from 1.4 to 1.6), they all exhibit the same issue.

Also same results with containerd 1.7 vs. containerd 2.0

Is this reproducible with the ARM instance of GHA?

Is this reproducible with the ARM instance of GHA?

I have not tried yet.
Note that things work fine for me inside Lima on an M1 mac, so, there are definitely cases where arm64 is fine...
Will try on GHA though.

Maybe it is related to subnetting for these arm64 boxes.
It is still mindblowing that it works for alpine and not debian, but then it would not be the first time there would be something really weird in glibc wrt dns resolution.

It works fine on the CI.
This has to do with something specific wrt networking on these boxes.

This is nuts.
Networking actually works just fine inside the debian container (dig / curl are happy), just NOT for apt-get, which fails resolving, regardless of which dns server is used in /etc/resolv.conf.
And again, things work just fine with docker for the same images, on the same machine - which is even more baffling.
Possible culprits would be ipv6 (nerdctl seems to enable ipv6 on the iface by default while docker does not) - or something related to CNI doing something with UDP packets (in the specific hardware context of these boxes) that apt (or glibc) does not like.
I give up on this. No time on my side to deepdivedebug apt / glibc (or CNI for that matter).
If anyone else hits this and has ideas on how to debug this further, tag me.

Looks like I just can't let this go (though cannot continue further tonight).
Here is where things are:
Standard resolution works just fine - tested for golang apps, using net.LookupIP, with netcgo and with netgo.
Clearly the issue is when apt is doing something fancier than that.
The message in apt comes from: https://salsa.debian.org/apt-team/apt/-/blob/main/methods/connect.cc?ref_type=heads#L407-430
But then at that point, it is already "too late": with docker, the domain getting resolved is debian.map.fastlydns.net - while with containerd / nerdctl, it is still deb.debian.org.
That is likely because the earlier SRV lookup failed in Connect:
https://salsa.debian.org/apt-team/apt/-/blob/main/methods/connect.cc?ref_type=heads#L478
Which points to https://salsa.debian.org/apt-team/apt/-/blob/main/apt-pkg/contrib/srvrec.cc?ref_type=heads#L36 as the problem area.
So, intuition here is that there is a problem with SRV lookups - getservbyport_r / friends.
Either:

this is some glibc version / compilation fuckerism (between host / CNI / containerd / container)
OR
CNI is manipulating UDP/DNS response in a way that doesn't please glibc

OMFG
ls -lA /etc/resolv.conf
-rw------- 1 root root 56 Dec  2 03:55 /etc/resolv.conf

^^^^^^
🤦♂🤦♂🤦♂🤦♂🤦♂🤦♂🤦♂🤦♂

The reason it affects ONLY apt-get is likely because apt-get drops out of root.

This also affects /etc/hosts, possibly others.


[Script]:  Adjective Comparative and Superlative Generator using NLP

Aim
This Python script takes a list of adjectives and returns their comparative and superlative forms using the TextBlob library.
Details
It's a simple tool to demonstrate how you can handle language-related tasks using NLP techniques.
Record

[X] I agree to follow this project's Code of Conduct
[X] I'm a GSSoC'23 contributor
[X] I want to work on this issue

/assign


Could not install globally with NPM

Hi,
I couldn't install the package by running the command npm install -g nelson.gui.
Error output (taken from Windows, but identical with an Ubuntu):
npm ERR! path C:\Users\...\AppData\Roaming\npm\node_modules\nelson.gui\build\nelson.gui.js
npm ERR! code ENOENT
npm ERR! errno -4058
npm ERR! syscall chmod
npm ERR! enoent ENOENT: no such file or directory, chmod 'C:\Users\...\AppData\Roaming\npm\node_modules\nelson.gui\build\nelson.gui.js'
npm ERR! enoent This is related to npm not being able to find a file.
npm ERR! enoent

npm ERR!      C:\Users\...\AppData\Roaming\npm-cache\_logs\2018-05-10T19_00_47_085Z-debug.log

The issue seems to be that the file build/nelson.gui.js doesn't exist at this point, and cannot be chmoded (and then bin-linked). Running npm install -g nelson.gui --no-bin-links doesn't trigger the error.
Everything seems fine when the package.json is changed to use the file src/nelson.gui.js instead. (see PR #12)
I don't know if it could have any side effect.
Tested with:

Windows 10 / Node 8.11.1 / npm 5.6.0
Ubuntu 16.04 / Node 8.11.1 / npm 6.0.1

Same issue here

I have the same issue.

The file was actuall removed in 0f125015ff395718e1f95b65e6707b544f53623c

@pph7 you can git clone the nelson.gui repo, then edit the package.json:
replace this:
   "nelson.gui": "./build/nelson.gui.js"
with this:
   "nelson.gui": "./src/nelson.gui.js"
then in the parent folder of the cloned repo, run:
npm install ./nelson.gui
hope it helps !

@ianis58 I did this but then I got some other problems. So I used an earlier version and that worked for me so far.


Is there any way currently to deal with trendy only signal ?

Not all signals have necessarily a seasonal component, some might be only trendy and in this case how do we go about setting the <seasonal_length> parameter?
For example, what are the right settings for the classical airline passengers data set? I tried 12 as the seasonal_length, running the robustSTL confounds trend and seasonality !

if you have no seasonality, you can remove seasonality extraction parts in the iterations !


Use relative paths doesn't work when selecting from a list of multiple matches

Actually, relative paths might not be working for me at all in this project.

Is this the same project that didn't have lookup_paths? I think we have something that checks if import_path.start_with?(lookup_path), which won't work for paths starting with .. We should probably address that by stripping out any dots from the start of lookup paths. It's likely that someone will add e.g. ./app/assets here too, which will suffer from the same problem.

This was the line I was talking about: https://github.com/trotzig/import-js/commit/994f70d65d5bf001a3fa278083578634174745b0#diff-ca39607eaaa0631db83ec644bad6bab0R49
Though it was checking make_relative_to instead of import_path, but the result is the same.

Yes, this is the same project that didn't have lookup_paths.


New Document loader request for Sharepoint , OneDrive and Documentum

Many customers has their knowledge base sitting on either in SharePoint , OneDrive and Documentum. Can we have a new document loader for all these?

Totally with you! A loader for SharePoint and OneDrive would be great!

I'll try to work on this one.

hey @netoferraz are by any chance working on sharepoint?

@netoferraz Any news on the SharePoint Loader?

Hi @laveshnk-crypto and @ugoborghetti I'll try to work on this in the following week.

Thank you @netoferraz ! That would be fantastic

Hi @netoferraz , is there any update on this?

We're waiting for a review here.

Cool!

Hi @netoferraz , thanks a lot for your contribution to the LangChain package! its extremely invaluable for developers such as me.
Temporarily, till your SharePoint Loader gets approved, I have gone ahead and cloned your version of langchain and im using that in my project instead. However, I had a few hiccups while following the documentation.
My sharepoint site doesnt have subsites, hence I am not able to retrieve the subsite ID as specified in the docs. What do I do in this case? My document library is located in the main site itself

Hi Folks, So as of today are we having any Git Repo which has used langchain document loader from SharePoint.

Thanks how do we get Sharepoint Loader working with Client Context and Site Tenant specific URL. the current sharepoint loader developed in LC does not allow for O365 authentication it is giving below error error_description=Application is not configured as a multi-tenant application.  Please help

@hsravidatta did you ever solve this? I am getting the same error when following the steps here, in the langchain docs. Thank you!

I know that I'm late but here is an article that I wrote on the subject: https://medium.com/@eric_vaillancourt/filling-the-gap-developing-a-custom-solution-for-sharepoint-integration-with-langchain-d961f7a06c96


feat: flink real-time ETL v2

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license
Summary
(describe what this merge request does)
Implementation highlights
(describe how the merge request does for feature changes, share the RFC link if it has)
Test checklist

[x] add new test cases
[ ] all code changes are covered by unit tests
[ ] end-to-end tests

[ ] deploy web console with CloudFront + S3 + API gateway
[ ] deploy web console within VPC
[ ] deploy ingestion server

[ ] with MSK sink
[ ] with KDS sink
[ ] with S3 sink

[ ] deploy data processing
[ ] deploy data modeling

[ ] new Redshift Serverless
[ ] provisioned Redshift
[ ] Athena

[ ] deploy with reporting
[ ] streaming ingestion

[x] with Redshift Serverless
[ ] with provisioned Redshift

Is it a breaking change

[ ] add parameters without default value in stack
[ ] introduce new service permission in stack
[ ] introduce new top level stack module

Miscellaneous

[ ] introduce new symbol link source file(s) to be shared among infra code, web console frontend, and web console backend

SonarQube Quality Gate Result

Result: :exclamation: Error
Triggered by @amliuyong on pull_request

Metric
Status
Value
Error Threshold

Reliability rating
:white_check_mark: OK
1
> 1

Security rating
:white_check_mark: OK
1
> 1

Sqale rating
:white_check_mark: OK
1
> 1

Coverage
:white_check_mark: OK
83.70
< 80

Duplicated lines density
:white_check_mark: OK
5.10
> 30

Blocker violations
:white_check_mark: OK
0
> 0

Bugs
:white_check_mark: OK
0
> 0

Code smells
:white_check_mark: OK
11
> 40

Critical violations
:white_check_mark: OK
0
> 0

Major violations
:exclamation: Error
3
> 0

Vulnerabilities
:white_check_mark: OK
0
> 0

View on SonarQube
updated: 6/17/2024, 05:30:10 (UTC+0)

SonarQube Code Analytics
Quality Gate failed

Additional information
The following metrics might not affect the Quality Gate status but improving them will improve your project code quality.
Issues
 0 Bugs
 0 Vulnerabilities
 0 Code Smells
Coverage and Duplications
No data Coverage
No data Duplication

SonarQube Quality Gate Result

Result: :exclamation: Error
Triggered by @amliuyong on pull_request

Metric
Status
Value
Error Threshold

Reliability rating
:white_check_mark: OK
1
> 1

Security rating
:white_check_mark: OK
1
> 1

Sqale rating
:white_check_mark: OK
1
> 1

Coverage
:white_check_mark: OK
83.70
< 80

Duplicated lines density
:white_check_mark: OK
5.10
> 30

Blocker violations
:white_check_mark: OK
0
> 0

Bugs
:white_check_mark: OK
0
> 0

Code smells
:white_check_mark: OK
11
> 40

Critical violations
:white_check_mark: OK
0
> 0

Major violations
:exclamation: Error
3
> 0

Vulnerabilities
:white_check_mark: OK
0
> 0

View on SonarQube
updated: 6/17/2024, 05:36:28 (UTC+0)

SonarQube Quality Gate Result

Result: :white_check_mark: OK
Triggered by @amliuyong on pull_request

Metric
Status
Value
Error Threshold

Reliability rating
:white_check_mark: OK
1
> 1

Security rating
:white_check_mark: OK
1
> 1

Sqale rating
:white_check_mark: OK
1
> 1

Coverage
:white_check_mark: OK
83.70
< 80

Duplicated lines density
:white_check_mark: OK
5.10
> 30

Blocker violations
:white_check_mark: OK
0
> 0

Bugs
:white_check_mark: OK
0
> 0

Code smells
:white_check_mark: OK
8
> 40

Critical violations
:white_check_mark: OK
0
> 0

Major violations
:white_check_mark: OK
0
> 0

Vulnerabilities
:white_check_mark: OK
0
> 0

View on SonarQube
updated: 6/17/2024, 06:14:41 (UTC+0)


add tests for path3d

This is part of #43440
I think there is nothing more to test than curve setter and getter.
Tests have been compiled and work.

It should now correspond to your suggestions, but the one about use of suite. I think it is better than tags, but I am no expert in usage of doctest. I could make a bigger pull request changing tags to suites. If you would like.

Yes, if this is better than using tags, it should be done in a separate PR for all test suites, not just in this one, so I suggest removing changes related to that from this PR for now.
I also noticed that there's no need to use square brackets for test suite names ([Path3D] vs just Path3D).

All right, I will adjust the request this evening. And open new request about using suites.

It is adjusted.

Thanks! And congrats for your first merged Godot contribution :tada:


MODCLUSTER-798 Fix handling of offseted ports

https://issues.redhat.com/browse/MODCLUSTER-798
This PR makes it work when portOffset for tomcats 8.5 and 9.0. No fix is required for tomcat-10.1 which seems strange, however, I was not able to determine why tomcat-10.1 behaves differently. Because of this I believe the fix can be made better by someone who understand the codebase better.
This is the server.xml I used
<?xml version="1.0" encoding="UTF-8"?>
<Server port="8005" shutdown="SHUTDOWN" address="<IP_ADDRESS>" portOffset="port_offset">
  <Listener className="org.jboss.modcluster.container.catalina.standalone.ModClusterListener"
              connectorPort="8080"
              advertise="false"
              stickySession="true"
              stickySessionForce="false"
              stickySessionRemove="true"
              proxyList="<IP_ADDRESS>:6666" />
  <Listener className="org.apache.catalina.startup.VersionLoggerListener" />
  <Listener className="org.apache.catalina.core.AprLifecycleListener" SSLEngine="on" />
  <Listener className="org.apache.catalina.core.JreMemoryLeakPreventionListener" />
  <Listener className="org.apache.catalina.mbeans.GlobalResourcesLifecycleListener" />
  <Listener className="org.apache.catalina.core.ThreadLocalLeakPreventionListener" />

  <GlobalNamingResources>
    <Resource name="UserDatabase" auth="Container"
              type="org.apache.catalina.UserDatabase"
              description="User database that can be updated and saved"
              factory="org.apache.catalina.users.MemoryUserDatabaseFactory"
              pathname="conf/tomcat-users.xml" />
  </GlobalNamingResources>

  <Service name="Catalina">
    <Connector port="8080" protocol="HTTP/1.1"
               address="<IP_ADDRESS>"
               connectionTimeout="20000"
               redirectPort="8443"
               portOffset="port_offset" />

    <Connector protocol="AJP/1.3"
               address="<IP_ADDRESS>"
               port="8009"
               secretRequired="false"
               redirectPort="8443"
               portOffset="port_offset" />

    <Engine name="Catalina" defaultHost="localhost">

      <Realm className="org.apache.catalina.realm.LockOutRealm">
        <Realm className="org.apache.catalina.realm.UserDatabaseRealm"
               resourceName="UserDatabase"/>
      </Realm>

      <Host name="localhost"  appBase="webapps"
            unpackWARs="true" autoDeploy="true">

        <Valve className="org.apache.catalina.valves.AccessLogValve" directory="logs"
               prefix="localhost_access_log" suffix=".txt"
               pattern="%h %l %u %t "%r" %s %b" />
      </Host>
    </Engine>
  </Service>
</Server>

with tomcat1 running on <IP_ADDRESS>:8080 (offset 0) and tomcat2 on <IP_ADDRESS>:8081 (offset 1). Without these changes, proxy gets CONFIG message for tomcat2 with port 8080. Alternatively, I could change connectorPort for tomcat2 to 8081, but that would cause some issues in createProxyConnector function (e.g., connectorPort.equals(connector.getPort())).
Edit: Fix formatting.

Looks like portOffset is not widely used setting since noone reported this bug before. Anyway, I ll have a look, but the general fix looks about right.

Thanks a lot! (I would be more confident about the fix if tomcat-10.1 would require it too.)

Thanks @jajik - I could reproduce this with Tomcat 10 no problem. That needs fixing too - replaced by https://github.com/modcluster/mod_cluster/pull/762

Ok, glad to hear that, now it makes sense :slightly_smiling_face:


KeyError:  'Accessing unknown key in a struct: wd'

Hi @felixkreuk .
Thanks for your codes. I have been successfully used predict.py to get the phoneme boundaries, but I would like to train a new model on my own data so that the result may get better. I have configured the timit_path in the conf.yaml to my own datasets which has three sub directory (train/val/test), and did not change anything else in documents.
Then using "python main.py" or "python main.py data=timit", I got the following error reports:
`Traceback (most recent call last):
File "main.py", line 77, in
main()
File "D:\anaconda\lib\site-packages\hydra\main.py", line 20, in decorated_main
run_hydra(
File "D:\anaconda\lib\site-packages\hydra_internal\utils.py", line 171, in run_hydra
hydra.run(
File "D:\anaconda\lib\site-packages\hydra_internal\hydra.py", line 82, in run
return run_job(
File "D:\anaconda\lib\site-packages\hydra\plugins\common\utils.py", line 109, in run_job
ret.return_value = task_function(task_cfg)
File "main.py", line 28, in main
cfg.wd = os.getcwd()
File "D:\anaconda\lib\site-packages\omegaconf\dictconfig.py", line 73, in setattr
self.setitem(key, value)
File "D:\anaconda\lib\site-packages\omegaconf\dictconfig.py", line 40, in setitem
raise KeyError(
KeyError: 'Accessing unknown key in a struct : wd'`
The problem may be very simple since I am not familiar with code-writing. But really hope to know how to use the main.py to train a model based on my own data.

Hi @Taemra, could you please make sure you are using hydra version hydra-core==0.11.3? You can do that by running pip intall hydra-core==0.11.3. Let me know if this solves your error. Thanks.

Hi Felix. It helps, the error is solved. Thank you very much. :D


Chore: unit test device instance

This PR adds unit tests specific to the DeviceInstance class. Based off of https://github.com/nrkno/sofie-timeline-state-resolver/pull/276

Codecov Report
Patch coverage has no change and project coverage change: +62.08% :tada:

Comparison is base (7ac1d7e) 37.91% compared to head (c08fd70) 100.00%.

Additional details and impacted files
@@               Coverage Diff               @@
##           release51      #282       +/-   ##
===============================================
+ Coverage      37.91%   100.00%   +62.08%
===============================================
  Files             99        42       -57
  Lines           9963       649     -9314
  Branches        2466        76     -2390
===============================================
- Hits            3777       649     -3128
+ Misses          5625         0     -5625
+ Partials         561         0      -561

see 57 files with indirect coverage changes

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


Settings not working for '2.0.0-alpha.10'

Hi,
2.0.0-rc.4, 2.0.0-rc.3, 2.0.0-rc.2, 2.0.0-rc.1 these versions are not compatible to my system so i am using '2.0.0-alpha.10'.  But i am unable to add settings to my tree.
Here is my code:

public tree1: TreeModel = {
value: 'Level 1 - B',
settings: {
'static': true,
//  'isCollapsedOnInit': true,
'rightMenu': false,
'leftMenu': false,
'cssClasses': {
'expanded': 'fa fa-caret-down fa-lg',
'collapsed': 'fa fa-caret-right fa-lg',
'leaf': 'fa fa-lg',
'empty': 'fa fa-caret-right disabled'
},
  }

};

Please suggest whats wrong. collapse on init is not working, i want to stop right click and drag.
It's really urgent.
Thanks

@jyotimishra12 and All if I saw a npm package for TreeModel, settings is extended from TreeModelSettings    it has meaning for only static and only static is working for me. I think all the others setting attributes dont have meaning you can see the attached interfaces :

@jyotimishra12 I could only suggest you to upgrade. Maybe you can create an example where issue is reproducible using https://stackblitz.com/?


Updated validations.py python script.

Fixed the behavior of validation_user function in validations.py.
Closes: #1
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

@googlebot I signed it!


filetype: bash history files are not recognized

Problem: Bash history files are not recognized
Solution: Add a pattern for bash history files

thanks!


Zeromq and windows module upgrade version

i have a node.js software that use zmq module for communication with an akka application. We have not installed the zmq library on Windows OS and we see that the node.js application communicate with the akka application. On Windows OS the module zmq use only the dll which is located in the directory lib of the module (node_modules\zmq\windows\lib) ? There is a way to point the module to use the library installed on os?

There is a way to point the module to use the library installed on [Windows]?

It is possible but I wouldn't personally do that. ZeroMQ library for the most part sends messages over backwards compatible major versions. That means you can connect sockets between node's zeromq and your akka application's sockets, assuming the bind and connect pattern is appropriate.
if you want node.js w/ version 4, clone master. that update hasn't been released yet on NPM.

Thank you reqshark!


Conv2D TypeError:  init() takes at least 4 arguments (4 given)

I am learning to use Keras's Functional API . I tried running one of code snippet (ex: inception module ) from the documentation (https://keras.io/getting-started/functional-api-guide/). I get the above mentioned error. I tried running other code snippets as well from the documentation. I get same error for each one.

Inception Module code snippet from the docs:
from keras.layers import Conv2D, MaxPooling2D, Input
input_img = Input(shape=(256, 256,3))
tower_1 = Conv2D(64, (1, 1), padding='same', activation='relu')(input_img)
tower_1 = Conv2D(64, (3, 3), padding='same', activation='relu')(tower_1)
tower_2 = Conv2D(64, (1, 1), padding='same', activation='relu')(input_img)
tower_2 = Conv2D(64, (5, 5), padding='same', activation='relu')(tower_2)
tower_3 = MaxPooling2D((3, 3), strides=(1, 1), padding='same')(input_img)
tower_3 = Conv2D(64, (1, 1), padding='same', activation='relu')(tower_3)
output = keras.layers.concatenate([tower_1, tower_2, tower_3], axis=1)
I am trying to use Conv2D as the first layer in functional API setting. Can anyone please provide me some suggestion on how to resolve this issue?
Thank you.
Ankit Sharma.

Have you checked your keras version?

@ramanb25: I did the same few hours back. The issue got resolved. Thank you for your suggestion.

I have the same problem as you， could you tell me how to solve this issue?  Thanks

x1 = Conv2D(16, (4, 4), strides=(2, 2), activation='relu')(input_1)
TypeError: init() takes at least 4 arguments (4 given)
This is the error I'm getting, I tried upgrading keras and tensorflow versions but nothing seems to be effective. Please give me some solution

@SabariRaaj Me too!Could you tell me how to solve this issue?

@SabariRaaj Me too!Could you tell me how to solve this issue?

@brotheryun Bro just use the following versions, keras 2.1.5 and tensorflow 1.5.0. only these versions matched perfectly and solved my issue. These versions is for python 3.


Update master submodules

Repository: ome/omero-deployment-examples
Already up-to-date.
Repository: ome/ansible-example-omero-onenode
Updating c9a7ef3..19be336
Previously merged:

PR 7 joshmoore 'Upgrade to Python 3'

Repository: ome/ansible-example-omero-public-user
Updating 8b79f69..3d6c44e
Previously merged:

PR 4 sbesson 'Update playbook and requirements for Python 3'
PR 3 manics 'Update Vagrantfile'

Repository: ome/ansible-example-omero-three-nodes
Updating 03d3e75..297cf2e
Previously merged:

PR 3 sbesson 'Update playbook and requirements for Python 3'

Repository: ome/docker-example-omero
Updating 48b4868..24f45b4
Previously merged:

PR 4 joshmoore 'Bump to OMERO 5.6 and PG 11'

Repository: ome/docker-example-omero-websockets
Updating be51e6a..a9d5de3
Previously merged:

PR 4 joshmoore 'Use Python 3'

Generated by build OMERO-DEPLOYMENT-EXAMPLES-submodules#244.

--no-rebase

Back to green state. Merging


issue583 fix (copyfrom_internal.h is not included by chance).

https://github.com/cloudberrydb/cloudberrydb/issues/583
== repro step ==
as issue described
== compile failure ==
pxf_fragment.c: In function ‘ProcessRequest’:
pxf_fragment.c:547:15: error: ‘RAW_BUF_SIZE’ undeclared (first use in this function)
547 |  char  buffer[RAW_BUF_SIZE];
|               ^~~~~~~~~~~~
== analysis ==
RAW_BUF_SIZE is defined in copyfrom_internal.h
src/include/commands/copyfrom_internal.h:#define RAW_BUF_SIZE 65536		/* we palloc RAW_BUF_SIZE+1 bytes */
in pxf_fragment.c
#if (PG_VERSION_NUM <= 140000)
#include "commands/copyfrom_internal.h"
#endif
PG version is 14.4,
PG_VERSION_NUM is 140004
happen to see below code in pxf_fdw.c
#if (PG_VERSION_NUM >= 140000)
#include "commands/copyfrom_internal.h"
#include "commands/copyto_internal.h"
#endif
the one in pxf_fragment.c looks to be typo
#if (PG_VERSION_NUM <= 140000)            ==> should be (PG_VERSION_NUM >= 140000)
#include "commands/copyfrom_internal.h"
#endif
note: git log history for the two files

git log pxf_fdw.c

commit 10538adb70ac5e81abbe0cb16a9e1cf66ad808ec
Merge: d5573b984b d457cb4e8a
Author: Cloudberry<EMAIL_ADDRESS>Date:   Wed Jun 7 08:57:14 2023 +0000
Initial Cloudberry code dump.

commit 7c3ae7bb6af5c9f25f31b153eb9e9e4ee3f89fd1
Author: Ashwin Agrawal<EMAIL_ADDRESS>Date:   Tue Jan 12 09:38:40 2021 -0800
Change "ON MASTER" to "ON COORDINATOR" for gpcontrib

Reviewed-by: Jesse Zhang<EMAIL_ADDRESS>
commit 19cd1cf4b68faff2e29bc2fa884c480e4644cdb4
Merge: a714299cd7 9e1c9f9594
Author: Heikki Linnakangas<EMAIL_ADDRESS>Date:   Tue Sep 22 18:12:30 2020 +0300
Merge with PostgreSQL version 12 (up to a point between beta2 and beta3).

...

git log pxf_fragment.c

commit 10538adb70ac5e81abbe0cb16a9e1cf66ad808ec
Merge: d5573b984b d457cb4e8a
Author: Cloudberry<EMAIL_ADDRESS>Date:   Wed Jun 7 08:57:14 2023 +0000
Initial Cloudberry code dump.

commit 3b1ada53a0e3b1702e9a64debf1cd7cbb2a9c360
Author: Oliver Albertini<EMAIL_ADDRESS>Date:   Thu Jan 30 15:16:58 2020 -0800
Remove gpcontrib/pxf, rename {,gp}contrib/pxf_fdw

Now that we are moving to FDW, we can remove the old external
table-based PXF module. Since PXF FDW only currently supports Greenplum
(not stand-alone Postgres) `pxf_fdw` should live under `gpcontrib`.

Authored-by: Oliver Albertini<EMAIL_ADDRESS>
(END)

Hi @Terry1504 welcome to rewrite your commit title and details following this template to make it look clearer. Thanks!

Hi @Terry1504 welcome to rewrite your commit title and details following this template to make it look clearer. Thanks!

I have closed this one, and submitted a new pull request with respect to the commit template.
https://github.com/cloudberrydb/cloudberrydb/pull/590


MINOR: Update build.gradle and release.py to upload streams-scala_2.12

Committer Checklist (excluded from commit message)

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation (including upgrade notes)

For reference, Scala 2.12 was added to the *All commands when we dropped Java 7 support: https://github.com/apache/kafka/commit/e70a191d3038e00790aa95fbd1e16e78c32b79a4#diff-6512f838e273b79676cac5f72456127f
Looks like the update to release.py was incomplete and the supposedly redundant upload archive line was not removed.

@ijuma Thanks for the review. The various xxxAll tasks in build.gradle seem to explicitly run tasks for core, which is possibly why streams-scala didn't get uploaded for scala 2.12. I have removed the explicit 2.12 upload in release.py and updated build.gradle to run tasks for streams-scala as well wherever it was running tasks for core with different scala versions. Can you take another look? Thanks.

retest this please

Merging to trunk and 2.0.


Rewrite legacy pipeline

To be more like the all pipeline in a vague home to address the issues with that pipeline

Pipeline version deprecated in favor of:

https://github.com/HTTPArchive/dataform
and https://github.com/HTTPArchive/wptagent/tree/main/HTTPArchive


testing cicd

[X] issue #https://github.com/keep-starknet-strange/blobstream-starknet/issues/136
[X] follows contribution guide
[X] code change includes tests
[ ] breaking change

Does not compile on windows. Should I document it?
Reday for a review.

still ready for a review

My bad. I deleted some files by mistake!

I added a few lines in the readme: https://github.com/keep-starknet-strange/blobstream-starknet/pull/141/files#diff-b335630551682c19a781afebcf4d07bf978fb1f8ac04c6bf87428ed5106870f5R25
sadly the crlf seems wrong :/

I will look for the git command to remove crlf on windows tommowor.

I did:
git config --global core.autocrlf true
git config --global core.safecrlf false

did not changed nothing. any idea of why?

pleeeeease!!

Looks like the README is still edited in the PR. Maybe just create a clean branch and only commit the cicd file?

If you need I can create a new PR and just update it with your git action. You will still get paid for the contribution through OnlyDust. lmk

Hello.
I absolutely ignored that I could be paid by only dust. if really you want I could git clone my own fork and try harder.
If it is eady for you to do it, you can do it.
Thank you very much :)

@drspacemn it is ok if you can author me. thanks :)

@drspacemn can I get news please?

@drspacemn I do not have any news. can I continue the PR alone finally then please? I do not want to override your work.

Hello.
As mentionned in private, I would like to know if I can finish it alone or if it will bother you because you could be still busy to do it alone by yourself.
I do not want to overrride your work.

Sorry for the delay. I have not done the work so feel free to complete yourself.

I am going to do it.

ready to merge!

nice work, thank you!


"documentloaded" not working

document.addEventListener("documentloaded", function() {
    alert("TEST");
})

This code not working. The event not working.
I'm not a JS developer. But, I researched this problem.
In file "viewer.js"
this.eventBus.dispatch("documentloaded", {
    source: this
});

I replaced on
const event = document.createEvent("CustomEvent");
event.initCustomEvent("documentloaded", true, true, {});
document.dispatchEvent(event);

and BINGO! This works!
My UA
Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/83.0.4103.116 Safari/537.36

This code not working. The event not working.

It's not supposed to work either, please see PR #11655 for the correct way to access events in the default viewer and see also https://github.com/mozilla/pdf.js/wiki/Third-party-viewer-usage
Given that this works as intended, since we don't want to dispatch events globally, this issue is thus INVALID.

Thanks!


EnergyEfficientAgent and FrequencyMapAgent should ignore very short regions

If the region runtimes are very close to the sample rate, the frequency setting applied will affect the next region as much as if not more than the current region, potentially degrading performance.   The Agent should not lower frequency in this case.

dupe of #125


add a new headline specific RPC for posting a message for blocking and nonblocking mode CORE-5945

Makes life a little easier on frontend, cc @cjb.

The commits 6f023e29b6b5...6e8ddc8d6e2f introduce visual changes on linux. :mag_right: 1 changed

Changed: Markdown-emoji (before) (after)


Any example of payment API ?

I am unable to find how to use payment API so far. Any help ?

This module did not wrap Wechat pay API, check out Wechat JS SDK (by Tencent) instead: http://mp.weixin.qq.com/wiki/7/aaa137b55fb2e0456bf8dd9148dd613f.html
FYI, example here:http://demo.open.weixin.qq.com/jssdk/


Update interested-technical-writers.md

@emckean plss review it

Hi! Would you please make a new pull request adding your information in alphabetical order by surname/family name? If you only use one name, alphabetize under that name. If you have questions about where your name would go in order, please reply to this comment. (Please alphabetize by more than the first letter: for example, Cat would go after Call but before Cave.)
The names are LISTED firstname, surname, but they are alphabetized by surname. So if you have:
Anwar Able
Bill Lion
Caesar Sun
Someone named Amy Pleasant would go between Bill Lion and Caesar Sun.


Threat Vault API Bug Fixes

Description
Updates requested by PM - added authorization and changed application/octet-stream to application/json
Motivation and Context

How Has This Been Tested?

Screenshots (if appropriate)

Types of changes

Bug fix (non-breaking change which fixes an issue)
New feature (non-breaking change which adds functionality)
Breaking change (fix or feature that would cause existing functionality to change)

Checklist

[ ] I have updated the documentation accordingly.
[ ] I have read the CONTRIBUTING document.
[ ] I have added tests to cover my changes if appropriate.
[ ] All new and existing tests passed.

Hi @MisterMcHoward, FYI we are also introducing a feature to support adding a CORS proxy to requests. We did this to help support APIs like ATP and TP which do not include the necessary CORS headers.
PR: https://github.com/PaloAltoNetworks/docusaurus-openapi-docs/pull/366
CORS proxy: https://cors.pan.dev