(Potentially) only announce Manifest Cid on the DHT

Right now, we're announcing every single hash/cid from a dataset on the DHT, this has significant overhead and can be potentially overcome by limiting announcements to only the Manifest cid. This would require adding a way to identifying/indexing the Manifests in the repo.
The listBlocks from the BlockStore, will take an additional argument with the multicodec that we want to retrieve. The datastore has to allow querying based on the multicodec.

Maybe classify them by type rather than codec? Note that putBlock should provide this info to the store, we can introduce putBlockEx or add an optional parameter

multicodec is the type, we'll eventually add a manifest multicodec.

Namespaces in Nim-DataStore is the solution that was meant for this usecase from the start.

Yes, exactly. In the PR description for https://github.com/status-im/nim-datastore/pull/19, you can see I gave an example of how key structure might be used to distinguish manifests from blocks, and possibly associate blocks with a particular manifest
for block in ds.query(Query.init("manifest:abcd1234/block:*")):
  let
    # key will look like "manifest:abcd1234/block:[cid]"
    (key, data) = await block

  ...

How we actually do it should take into account the overhead associated with substrings manifest: and block: being in the key of every manifest and block, respectively, i.e. in every row in the database of nim-codex's SQLiteDatastore instance.
It would be even more overhead if every block-key had substrings manifest:, the manifest CID, /, and block: and probably isn't worth it.
We could shorten to m:[cid] for manifests and b:[cid] for blocks.

As the first step, I will modify API so datastore and network part will know whether Cid defines a dataset or a datablock

Talking about advertiseQueueLoop(), I see these ideas:

optimize it: use batches of CIDs in every place (onBlock, asyncQ.put, network send)
send only diff. updates most of the time (require timestamp in BlockStore entries)
advertize only manifest CIDs. This will require node.retrieve to request data from NetworkStore by ManifestCID+BlockCID: getBlock(cid, manifestCID = ...)


How to use swaggerui with drogon?

I saw the drogon has add some feature about swagger recently,does it availiable now? if it is availiable and how to use it.

#923 Is working on that. But that's still only the skeleton. We welcome new contributions though! You're welcomed to build your own version and upstream it or collaborate with us to make it happen earlier.


Do you have an input pipeline example

I am going through your documentation but am still a little confused for how I would need to implement the input pipeline functionality if I want to stream in data.  Say you have data stored in a large CSV that has been scaled as you have specified, how would you go about creating the input pipeline function?  Do you have an example one can use?

Is it something along the lines suggested in this Stanford Tutorial?
https://cs230-stanford.github.io/tensorflow-input-data.html
I'm new to Tensorflow so any additional pointers would be appreciated.

Any thoughts?
Ranjit
From: Chirag Lakhani<EMAIL_ADDRESS>Reply-To: Oracen/MIDAS<EMAIL_ADDRESS>Date: Thursday, May 16, 2019 at 7:10 PM
To: Oracen/MIDAS<EMAIL_ADDRESS>Cc: Subscribed<EMAIL_ADDRESS>Subject: [Oracen/MIDAS] Do you have an input pipeline example (#12)
I am going through your documentation but am still a little confused for how I would need to implement the data pipeline function if I want to stream in data. Say you have data stored in a large CSV that has been scaled as you have specified, how would you go about creating the input pipeline function? Do you have an example one can use?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://github.com/Oracen/MIDAS/issues/12?email_source=notifications&email_token=AINSGRZSB5JNSFTFZL2GABLPVWPS3A5CNFSM4HNO62AKYY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4GUHR5LA, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AINSGRZYQE4LYHQDN6PLQXTPVWPS3ANCNFSM4HNO62AA.

Hi @cmlakhan, sorry for the unacceptably slow response! The latest version of MIDAS is now available here: https://github.com/MIDASverse/MIDASpy
I hope the latest documentation helps clear up your issue, but if it doesn't feel free to file a new issue on the linked repo.
Thanks!

Thanks a bunch!  Wow, didn't realize you guys did an overhaul of MIDAS.
Will definitely check it out.
On Tue, Sep 29, 2020 at 7:07 AM Tom Robinson<EMAIL_ADDRESS>wrote:

Hi @cmlakhan https://github.com/cmlakhan, sorry for the unacceptably
slow response! The latest version of MIDAS is now available here:
https://github.com/MIDASverse/MIDASpy
I hope the latest documentation helps clear up your issue, but if it
doesn't feel free to file a new issue on the linked repo.
Thanks!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/Oracen/MIDAS/issues/12#issuecomment-700631824, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAQMA5WJETWRZVNW36N5C53SIG5WZANCNFSM4HNO62AA
.


Hide unnecessary configurations for pie and doughnut charts

Description
These configs shouldn't be shown because they don't apply to pie and doughnut charts
Configs

[x] default value in dimensions
[x] rotate label in dimensions
[x] label in metrics

For today: take a look at the task and make a plan

For today: if you don;t have any other tasks, start working on this

For today: add plan to ticket and if time (depending on how TestFest goes) start working on it

Daily update: The task was executed correctly but the requirements shifted after a call with Joze:

Default value should be visible
Rotate label functionality should be added for above chart types and be made visible.

For today: add written changes in comment above and re-submit code for review

All good.

Added CL


Register sgyt.is-not-a.dev

Added sgyt.is-not-a.dev using the CLI.

CLA Assistant Lite bot: Thank you for your submission, we really appreciate it. Like many open-source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution. You can sign the CLA by just posting a Pull Request Comment same as the below format.

I have read the CLA Document and I hereby sign the CLA

You can retrigger this bot by commenting recheck in this Pull Request

I have read the CLA Document and I hereby sign the CLA

rechk

recheck


TextEditor.getScrollTop is deprecated.

This is now a view method. Call TextEditorElement::getScrollTop instead.
TextEditor.getScrollTop (/Applications/Atom.app/Contents/Resources/app.asar/src/text-editor.js:3319:12)
showExpressionType (/Users/mairan/.atom/packages/atom-typescript/dist/main/atom/tooltipManager.js:50:31)
<unknown> (/Users/mairan/.atom/packages/atom-typescript/dist/main/atom/tooltipManager.js:41:59)

is anyone working on this?

+1

+1

https://github.com/ionide/ionide-atom-fsharp/issues/257
Is this a hint?

+1

I fixed this error.
See > https://github.com/TypeStrong/atom-typescript/pull/1197


Fix bsql crashing when the connection gets re-made while a query is blocking

Long story short: Use after free on this. Added a zombie bool to the state struct to detect this, added logic to check/set it.
@Cyberboss @SpaceManiac @optimumtact
I haven't tested this without the shared_ptr change me and spacemaniac were trying out yet, but the test that still had that change worked fine.
Edit: found and fixed a second crash with firstSuccessfulConnection shared use:
firstSuccessfulConnection kept a reference even when it was given to a QuertyOperation thread, if the MySqlConnection was later deleted, it could close this handle while mysql was still using it in the QueryOperation thread.
 It only existed for mysql_real_escape_string, and making that hold on to and release a connection is a better solution that lowers the complexity of the overall system. I made sql_sanitize block by doing this, I can think of a better way.

Further testing revealed another crash resulting from the mysql connection object getting released before the blocking thread is done using it. I'm gonna have to redo the logic behind that. It's much harder to trigger, but I'm enjoying the change to re-learn threaded programming

Its randomly hanging on row fetch so I need to examine this some more.

this is still chain crashing servers when the db gets sad

Owo wats this?


Is there any event for asset changed position/orientation ?

I am building a multiplayer app using cloud anchors where two or more people can interact on one or more asset. When the asset changes it's position , how to get the event to broadcast to other connected users ?
Help !

You could try TranslationController#isTransforming(), but since there is no documentation on this method it is hard to tell without conducting own tests.

any update on this ?

Yes we've added a listener to notify on position changes.  You would still have to implement the networking aspects of this.  This code is committed and will be part of an upcoming release

Thanks for the update. It will be a great help for multiplayer apps/games.

Fixed in 1.6


[CRI] Logging plugins

What is the problem you're trying to solve
Forward containers logs to journald.
Describe the solution you'd like
Configure CRI plugin to leverage containerd logging plugins (https://github.com/containerd/containerd/pull/3085).
Additional context
Already discussed here containerd/containerd#6639

It seems to me like proper support for this would need a KEP in Kubernetes. k8s needs to be aware that logs are handled by a plugin, and that operations like attaching or fetching logs (as implemented today) would not work.

@kevpar Good point.
containerd would still manage logging when it comes to running containers not from k8s. At first glance, it looks like container logging is, first of all, a job of the container runtime.
k8s needs logs especially for satisfying kubectl logs command, isn't it ? if so, maybe fetching a container log should be a job for the CRI ?
We could even imagine being able to register multiple (chained?) containerd logging plugins, so one would be provided by CRI plugin/shim in order to satisfy k8s needs and optional ones could be configured by users (like for redacting logs, or centralizing them into journal or whatever).
Or maybe it actually needs another interface layer, similar to CRI, CNI, CSI; say "Container Logging Interface" that would be used by CRI in order to forward logs to whatever logging tech (beats, fluent, logstash, logtail, ...).
A "CLI" KEP sounds good to me.

Meanwhile...
ATM, If we don't profit containerd pluggable logging system to have, minimal IO, logs centralization (journald here) then it means we have to multiply logs collectors to get proper observability (at the cost of extra resource usage).
It also makes early logs filtering not possible (as stated in https://github.com/containerd/cri/issues/1342).
cri-o provide such configuration, which, somehow, cover both needs:
--log-filter="": Filter the log messages by the provided regular expression. For example 'request.*' filters all gRPC requests.
--log-format="": Set the format used by logs: 'text' or 'json' (default: text)
--log-journald: Log to systemd journal (journald) in addition to kubernetes log file (default: false)```

Maybe it would be great for containerd to provide such means ?

cri-o provide such configuration, which, somehow, cover both needs:
--log-filter="": Filter the log messages by the provided regular expression. For example 'request.*' filters all gRPC requests.
--log-format="": Set the format used by logs: 'text' or 'json' (default: text)
--log-journald: Log to systemd journal (journald) in addition to kubernetes log file (default: false)

Maybe it would be great for containerd to provide such means ?

@jbguerraz, as i understand the CRI-O flags (atleast the --log-format one) is that they're used to configure logging of the crio binary itself not containers running on-top of CRI-O:
https://github.com/cri-o/cri-o/issues/3181#issuecomment-581544380

Thank you for the heads-up @mikejoh !
BTW, any point of view on the matter ? :)

@jbguerraz
Np!
I'm still reading up on this and i came here because i was looking for a way to transform logs from text to JSON using containerd as runtime in Kubernetes (via CRI). I figured (naively) that there was support for it after discussing this a bit with my colleagues. We basically thought that there would be support for this just like the JSON log driver in Docker.
When reading through issues and documentation it seems that what we got in Docker in regards to log drivers: https://github.com/moby/moby/tree/master/daemon/logger is largely out-of-scope to add for many of the runtimes, especially when integrating with CRI. And it's not just because it's out-of-scope but basically not possible at all because of e.g. kubectl logs (as you mentioned).
And also maybe for that very reason, the support for so many different logging use cases in Docker, this (logging) was left out of CRI. I'm obviously just speculating and have no proof of this.
I like the idea of plugin chaining, or plugin based logging overall, but as already stated this would also (probably) need changes done on the Kubernetes side of things.

+1 for CRI log plugins, so that a JSON containerd log plugin can be written. All of our Kubernetes clusters expect JSON style logs and migrating from docker-shim to to containerd breaks the JSON format. Today, we are using fluent's regex parsing as a workaround to extract fields out of the default text logs from containerd, but that has performance issues. Would be good to see a JSON plugin solution for containerd CRI.

we are switching too from docker to containerd on some of our kubernetes clusters, and it's a pity that container-logs cannot be similarly formatted like those written by docker in json-format

+1. We switched from docker to containerd (1.6.4) yesterday and find out about this today when our Logging team raised a concern that new format dropping all the application pods logs. We really looking for this feature to set logging format to json. I saw this issue is part of 2.0 milestone. Is there a way I can find the timelines when this solution will be available?. Thanks  Appreciate it.

+1 for json format

+1. We switched from docker to containerd (1.6.4) yesterday and find out about this today when our Logging team raised a concern that new format dropping all the application pods logs. We really looking for this feature to set logging format to json. I saw this issue is part of 2.0 milestone. Is there a way I can find the timelines when this solution will be available?. Thanks Appreciate it.

same, switched to COS_CONTAINERD image-type on our dev k8s node pool, our prod is still on Docker, so we see different log formats from two enironments

I don't think this belongs in a 2.0 milestone at this point.

NRI doesn't allow to edit logPath, to copy container logs to journald, is there a simpler way than having a runc-wrapper that edit the json, and building a modified version of https://github.com/containerd/containerd/blob/main/core/runtime/v2/README.md#logging that also write to file ?


Add yamllint check and fix errors

This will enable the yamllint check in CI
for all yaml files except in vendor and
fix all the yamllint errors
Submitter Checklist
These are the criteria that every PR should meet, please check them off as you
review them:

[x] Includes tests (if functionality changed/added)
[ ] Includes docs (if user facing)
[x] Commit messages follow commit message best practices
[ ] Release notes block has been filled in or deleted (only if no user facing changes)

See the contribution guide for more details.
Double check this list of stuff that's easy to miss:

If you are adding a new binary/image to the cmd dir, please update
the release Task to build and release this image.

Reviewer Notes
If API changes are included, additive changes must be approved by at least two OWNERS and backwards incompatible changes must be approved by more than 50% of the OWNERS, and they must first be added in a backwards compatible way.
Release Notes

/kind misc

/approve


Rename

Ebert has finished reviewing this Pull Request and has found:

4 possible new issues (including those that may have been commented here).
4 fixed issues! 🎉

You can see more details about this review at https://ebertapp.io/github/stepnivlk/pushest/pulls/5.


Keras use only single thread

I have installed keras on a redhat 6 server, it is really a attractive framework cause it is really easy to build a deep neural network. However, I found my keras use only single thread(or single core). I ran examples given in the source code package, such as "mnist_mlp.py", and used "top" command, found the usage of CPU is 100%, never more than CPU, I have 6 cores, each with four threads, no GPU, so hope keras can make efficient use of all cores, however, it use only one thread.
I don't know whether this is caused by my theano or blas.
Below is some information about my keras:
System: redhat 6
Theano:  0.7.0
numpy: 1.10.1
scipy: 0.16.1
BLAS: atlas 3.8.4-1.el6
keras: 0.2.0
Does anyone know how to fix this? I will appreciate any suggestion. Thanks very much.
ps: I can not make keras run with multithreads on Ubuntu 15.10 either.

Try switching the backend to Tensorflow

This enables multithreading in theano:
import theano
theano.config.openmp = True

@dandxy89 I switched backend to Tensoflow by modifying ~/.keras/keras.json, but it didn't work, thank for your reply anyway, any other idea?

@Sebubu I add "import theano theano.config.openmp = True" in the keras example "mnist_mlp.py", but it didn't work, thanks anyway. Any other idea?

@Jallet do any of the examples work for you, after you had switched the backend to "Tensorflow"?

@dandxy89 Yes, the example works, although still with one thread, I added "{"epsilon": 1e-07, "floatx": "float32", "backend": "tensorflow"}" in ~/.keras/keras.json according to the keras document.

@dandxy89 By the way, when I run "OMP_NUM_THREADS=2 python theano/misc/check_blas.py -q", the cpu usage of python is still at most 100%, never more than 100, and found only one core is being in use by command "htop", does this mean there is something wrong with my blas or openmp?
ps: If everyting is fine, when running keras' s example, should it use multi cores, or the cpu usage more than 100%

if check_blas.py only use one cores, it mean your BLAS is an single core
blas. Try to change it.
On Fri, Dec 11, 2015 at 8:52 AM, Liang Jiang<EMAIL_ADDRESS>wrote:

@dandxy89 https://github.com/dandxy89 By the way, when I run
"OMP_NUM_THREADS=2 python theano/misc/check_blas.py -q", the cpu usage of
python is still at most 100%, never more than 100, and found only one core
is being in use by command "htop", does this mean there is something wrong
with my blas or openmp?
ps: If everyting is fine, when running keras' s example, should it use
multi cores, or the cpu usage more than 100%
—
Reply to this email directly or view it on GitHub
https://github.com/fchollet/keras/issues/1245#issuecomment-163940950.

Try OpenBlas.

import theano
theano.config.openmp = True
then after that write OMP_NUM_THREADS=4 python script_name.py and u re good to go


Adds the start of coding conventions.

A few more things we might want to add:

PRs must come w docs updates for functionality that is updated, removed, or added

Did we land on a convention for trailing whitespace? (Specifically this came up w docs for @msteffen recently) ... and having a convention lets us have cleaner diffs

Responded to all comments except the trailing whitespace one. That one seems obvious to me. I've never heard anyone argue in favor of trailing whitespace and I can't imagine a legitimate purpose for it. Is there one?

I agree its apparent, but I think this could still cause problems. Specifically for docs.
This is how (we think) it came up in the PR that Matt was working on:

Someone edits docs, their editor may or may not have added trailing whitespace, but it was added to many/most lines in a file
When that PR was submitted, this was net new content, and so was very hard to tell if there was trailing whitespace (I'm not sure the GH diff view shows trailing whitespace)
Matt's branch had those changes in its commit history
Matt happened to need to update that documentation file ... and his editor does the Right Thing and removes trailing whitespace
The PR that Matt submitted then was really noisy around that doc file ... it was hard to tell which lines were really modified since the diff showed all lines being modified

This makes it really hard to actually validate that doc updates look good. And because we don't enforce it, it could easily happen again if someone adds net-new docs w an editor that has trailing whitespace.
So - this is specifically an issue around docs. I'm pretty sure gofmt does the right thing.
It should be easy to update make lint to check the docs files for trailing whitespace. That way if someone introduces it, the build will error.
Either way, sounds like this is outside the scope of this PR

Linter is go specific but adding a CI step that checks for trailing whitespace seems very easy so I'd definitely be in favor of that.
I agree it's outside the scope of this PR.
This document is really just codifying what we do and don't like style wise, only a small portion of it is actually enforced in anyway and I think our codebase is rife with violations. I'm hoping that over time people will make passes to fix the violations and add CI checks to make sure they stay fixed.


[FEAT] When saving bookmark, indicate successful addition to server

Currently no indication if tab is saved when hitting save in extension UI - save goes grey upon click but this does not mean bookmark is saved on server.
Unfortunately there is some small delay, and saving the bookmark seems to fail most times if you switch or close the tab.
Therefore you are left stuck there waiting for some unknown amt of time for it to save.
Very unpleasant user experience - my workaround is to count to 3 in my head when saving a page .. not great.

There should be an indication on the extension before it closes itself, i will check that

It should look like this now

It had a timeout about 1000ms I had it increased in the last commit to 3500ms.
55683ec


Updates WebClientEurekaHttpClient to use auto configured WebClient.

This allows it to take advantage of settings that are auto-configured such as spring.codec.*.
Fixes gh-3819

Merged via 8d5a3f8ec1405f6add9f177051000edbec23d2ea


Notify patrons via email when user opts-in

#2543

[x] Add opt-out checkbox on account page
[x] Handle patrons without email_address
[x] Tests
[ ] Review email content
[x] What if we're sending emails to 100 patrons? Don't block request on sending emails
[x] What if the account was taken over by another one?

Nice! Our first transactional message! :dancer:
We'll need to include opt-out with this. Probably a "Email Notifications" section on the Account page, parallel to "Privacy." Eh?

Current status:

286c19fa08c4a0c2ce6da8c17d620fe465a09fda seems to be unnecessary, I suggest dropping it from this PR.

286c19f seems to be unnecessary

Yes, that's true. I initially thought that we could batch the emails in one call (have _render_email called just once in send_emails_to), but later realized that we had to identify the language for each user before sending an email.

I suggest dropping it from this PR.

Even though it's functionally the same, I think it looks cleaner.

Even though it's functionally the same, I think it looks cleaner.

It looks a little weird to me. If this code was on master and I was working on an email PR I would be wondering why it's been cut into two functions this way, and I would probably end up refactoring it.

Ready for review.

Content reviewed:

We should use GitHub in the subject instead of github. We have display_name available on the platform object.

Otherwise than that nit, this PR works for me. !m 8

Other than https://github.com/gratipay/gratipay.com/pull/3136#commitcomment-9828767 (Isn't a blocker, we're nowhere close to 30 emails per minute - it's just related to us being able to estimate our limit), this PR looks good to me. :)

@rohitpaulk 0cd858db26d97c7e7c2a1504934202768946d73f

I've set DEQUEUE_EMAILS_EVERY to 60 in production.


chore: Add setup-sbt as it was removed in the latest image

Fixes (?) https://github.com/scala/scala3/issues/22224

Superseded by #22227


Fix/#166 explorer does show all container entries from the sql table

At present, the Explorer doesn't have a system in place for testing SQL queries


[ONNX] Tool to serialize ONNX models

Simple tool to use for debugging problems with ONNX models.

TEST NOW

TEST NOW


Give audio uploads access to the targeted experience ID immediately after uploading

What type of feature request is this?
Mantle doesn't support a Roblox feature I would like to use
Currently I have to manually give every audio asset uploaded access to the proper universe ID for them to play ingame without publishing a build, Ideally mantle should handle this for me, current workaround is going through every audio asset in the asset manager after deploying and clicking this in the output.

Thanks for flagging this! Is this related to a recent Roblox change? Was there an announcement post for it?

Is this related to a recent Roblox change? Was there an announcement post for it?

Yes.
Relevant documentation: https://developer.roblox.com/en-us/articles/audio-asset-privacy

This is fixed in the latest version (0.11.5)


feat: codegen support for Amplify Android Lazy loading

feat: codegen support for Amplify Android Lazy loading and custom selection set

Description of changes

update data packages to release codegen support for Amplify Android Lazy loading and custom selection set

Issue #, if available

Description of how you validated changes
Checklist

[ ] PR description included
[ ] yarn test passes
[ ] Tests are changed or added
[ ] Relevant documentation is changed or added (and PR referenced)
[ ] New AWS SDK calls or CloudFormation actions have been added to relevant test and service IAM policies
[ ] Pull request labels are added

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Replicate changes to tests from: https://github.com/aws-amplify/amplify-category-api/pull/1919/files#diff-bf30dcec7b6663d365b22c23dd21ec8bdc151220fcde17e1d5b697db09a33641


The detached database account shows in the Attached Database Accounts view after executing "Cosmos DB: Detach" from command palette

OS: Win10
Azure Resource Group Build Version: 20230219.1
Azure Databases Build Version: v0.19.3
Repro Steps:

Attached a database account -> F1 -> Cosmos DB: Detach -> Select the above database account.
Check whether the detached database account shows in the Attached Database Accounts view.

Expect:
The detached database account doesn't show in the Attached Database Accounts view.
Actual:
The detached database account shows in the Attached Database Accounts view.
More Info:

This issue doesn't reproduce after executing "Detach" action from context menu.
Refresh can fix this issue.

Given that this is a minor issue which can be easily worked around by refreshing the tree view, I am going to close this issue as won't fix.


Add Normalize library

Just noticed that there's not an option for adding the Normalize.css library. It's probably the most commonly used CSS reset project. Would love to see it added.
/cc @necolas

JS Bin info

https://jsbin.com/edit
Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_2) AppleWebKit/600.3.10 (KHTML, like Gecko) Version/8.0.3 Safari/600.3.10
mdo

Please add it then.
On 16 Jan 2015 00:35, "Mark Otto"<EMAIL_ADDRESS>wrote:

Just noticed that there's not an option for adding the Normalize.css
library http://necolas.github.io/normalize.css/. It's probably the most
commonly used CSS reset project. Would love to see it added.
/cc @necolas https://github.com/necolas
JS Bin info

https://jsbin.com/edit
Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_2) AppleWebKit/600.3.10
(KHTML, like Gecko) Version/8.0.3 Safari/600.3.10
mdo

—
Reply to this email directly or view it on GitHub
https://github.com/jsbin/jsbin/issues/2235.


Offline messages which disappear from the network are retried forever

It seems that if an offline message falls into the retry path (within (m *MessageRetriever) processQueuedMessages()) that they retry forever in the case that the message disappears from the network for whatever reason. We should probably improve this code so that after a period of retrying (45 days or maybe however long the default dispute timeout is) that we eventually stop asking the network for these messages.
This could present a sort of processing DoS attack vector for buyers unwittingly buying from a malicious node.

Some additional thoughts: we only care about these offline order messages for as long as someone might be using the order. The longest use cases of the order remaining active are:

a fulfilled order which has not been completed by the buyer which resolves approx 45 days (in blocktime) after payment in favor of the vendor automatically (for BTC, BCH, and LTC)
a disputed order which has not bee resolved by a moderator for the maximum dispute time 45 days (in realtime, I think, but not positive about that?) after the dispute was started
ZEC doesn't have a blocktime-release redemption option so these orders may be active indefinitely

My suggestion for 45 days is arbitrary. The objective there is we don't want to keep asking about offline messages if they were created X number of days ago because they'd probably be for an old order. The question is what is a good X that doesn't preclude order messages from getting lost if they belong to an order that happens to be running very, very long. My best guess at a number was 45 days at the time that I wrote the description.


added documentation to grid functions

Pull Request Test Coverage Report for Build 3196

18 of 37 (48.65%)  changed or added relevant lines in 2 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.1%) to 88.408%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

examples/rllib/green_wave.py
3
6
50.0%

examples/sumo/grid.py
15
31
48.39%

Totals

Change from base Build 3192:
-0.1%

Covered Lines:
7848

Relevant Lines:
8877

💛  - Coveralls

In rllib/green_wave.py on L80, outer_edges = gen_edges(col_num, row_num) makes col_num and row_num the 1st and 2nd args respectively. The function header for gen_edges indicates that the order is row_num followed by col_num. I don't think you did this, but can you update?

Good catch. I've resolved it now.


Server unavailable, please make sure you have installed Node.

I have node installed and set the path. But this error never disappears.

Did you check FAQ?

I have same error

i have same error too

Thank u.

~i have same error too~
download node here, restart app, then it works https://nodejs.org/en

This worked for me too. Not sure why the version from nvm / brew did not work, but whatever. Thanks a lot

same thing

same thing

Your node version is just too old

@intitni switched to 19.2.0 works fine now. Thank you! 🙏

I am having this issue with latest node and my path to node is /usr/local/bin/node which is the my path

I'm getting some issues here. Does CopilotForXcode not work for organizations? I can't get past the Not Authorized..

@escakot To be honest, I don't know. Please open a new issue about that to see if other users can help.

Must restart Copilot for Xcode after setting 'Path to Node'. Can this setting be fixed? It seems that many people are stuck here.

If you installed it with Homebrew you need to specify the path and version eg: /opt/homebrew/Cellar/node/20.0.0/bin/node


Adding dummy VM to make PEs work in a separate vnet.

The preferred image for this VM would be one that doesn't have any operating system, however I'm not sure if there has to be an active DHCP lease to keep the PE Vnet running correctly.
The credentials installed on the VM are the minimum required, I deleted the private key matching the generated public key. There is no way to ssh into that Virtual Machine.
Context:
A running VM is required in a vnet to make it active and to make PEs accessible.

@julienstroheker fyi


Support Multiple Currencies

Right now Im thinking the user can select two main pairs, one crypto pair...NEO/BTC/ETH and one fiat pair USD/CNY/JPY etc. Then they can do the cycling between whichever two currencies they have in their settings


Update test deps (as of 2018-11-12Z)

This pull request derives from #420. So needs to be handled after that.

This pull request just updates the versions of test dependencies (Saxon).
As for the tests which require Saxon-PE or EE, I ran them with Saxon-EE <IP_ADDRESS> on my local machine and they passed.

@cirulls
Merged this test configuration update.


When adding declared licenses, check

When adding declared licenses, check if the license specifier is in the SPDX license list.

This is not a plugin issue, but should be fixed in the library itself.


Solid color thumbnail when fully zoomed out on wall

Describe the bug
When fully zoomed out on the wall, a solid colour appears for the majority of images. When even slightly zooming in, a proper thumbnail appears. For the amount of space that each grid takes up on the screen, I would expect to see a proper thumbnail like the rest of the images have.
Expected behavior
Images with higher detail thumbnails appear
Screenshots

Desktop (please complete the following information):

OS: OpenSUSE MicroOS, Photofield running as prebuilt executable from Github and inside an Arch Linux distrobox environment
Browser Brave
Version 0.15.0

Additional context
Slightly zooming in reveals higher detail thumbnails. Image censored, completely black grids are images with higher detail thumbnails and I couldn't bother doing the rest so I just blurred the other half of the image.

I just realised that https://github.com/SmilyOrg/photofield/blob/main/defaults.yaml#L27 exists, though I guess a point could still be made about a default which could be made better but I'm closing this.

I also feel like the default is a little too aggressive, so if you find a better default, let me know and I'll try to change it when I can.


Test Biometric Authenticator integrated in the Identity Server

Description:
Setup biometric authentication in the Identity Server and test its functionality using the mobile application by adding biometric as the outbound authentication method for an app using the identity server.
Suggested Labels:
Task, Milestone

Tests Scenarios and Results for WSO2 Verify

Accept straight away

No problems encountered

Hold for 1 minute and Accept

Authenticated without a problem
Adding a timeout might be better

Denying the access when prompted

No problems encountered

Holding and Deny

Add a timeout

Removing profile on app and requesting

Shows “Choose Device Page” on laptop
None of the devices are displayed (Devices weren’t removed on user portal)

Registering without removing from user portal

No problems encountered

Request login when app is asleep

No problems encountered

Request login when app is killed

No problems encountered

Request login when app is asleep and phone is locked

No problems encountered

Request login while app is killed and phone is locked

Throws an exception but the authentication works
Might be because the notification is sent when the app is not opened and and the phone is locked


Auto release scripts not working

When it was working before, you can submit a PR with a commit message "[npm release]" and the script will create a tag and publish the new library to NPM registry.
See

https://github.com/OpenBeta/sandbag/tree/develop/.github/workflows
https://github.com/OpenBeta/sandbag/actions

I'm not too familiar with github actions, but following the actions history here, what seems like happened is that:

There was a second "New release 2" PR, which was updating the package.json in the develop branch to the latest version 0.0.12. This was due to the automated version bump in the "[npm release 2]" PR right before.
This second "New release 2" PR caused the "auto tag based on commit msg" action to run again, which then created a new "v0.0.13" tag in the github repo. See here for when that happened.
Now since there's a "v0.0.13" tag in the github repo, but the develop branch is currently on "v0.0.12", when trying a new "[npm release 3]", the "auto tag based on commit msg" action tries to create a new tag for the repo based on the version in the branch (currently 0.0.12) by bumping it up one. Thus, it tries to create a "v0.0.13" tag, but that already exists, thus the action fails. See here for when that happened.

The "auto tag based on commit msg" action seems to run every time a PR is closed. Does it make sense for this action to only run if the PR has [npm release] in it's head commit message? This would be similar to what the "npm publish action" does, where it has  if: "startsWith(github.event.head_commit.message, '[npm release]')"

To fix the state of this automation, could we delete the currently created "v0.0.13" tag in the github repo?

I'll reproduce the state of this repo in my forked version, and see what will need to be updated.

The publish script finally ran to completion😅 !  For future reference we need to explicitly pass individual secrets from the caller job (or turn on inherit to pass everything).
https://github.com/OpenBeta/sandbag/blob/develop/.github/workflows/auto-version-bump.yml#L34


use utf8 encoding rather than default encoding of the platform

String.getBytes() uses the default encoding of the platform which could be anything.
We should use explicit encoding (i.e., String.getBytes("UTF-8") )

/azp run java - cosmos - tests


service-linked-role needs kms:ListGrants permissions

Description
health-check-session is causing an alarm in our Andromeda environment. The ListGrants request by health-check-session is returning an AccessDenied in that environment.  See the following example event(Event Link):
{
"eventVersion": "1.08",
"userIdentity": {
"type": "AssumedRole",
"principalId": "AROAVSZ4CHCC6SLATTXGL:health-check-session",
"arn": "arn:aws-us-gov:sts::383988676741:assumed-role/a-andromeda20211214030207513900000004/health-check-session",
"accountId": "383988676741",
"accessKeyId": "---",
"sessionContext": {
"sessionIssuer": {
"type": "Role",
"principalId": "---",
"arn": "arn:aws-us-gov:iam::383988676741:role/a-andromeda20211214030207513900000004",
"accountId": "383988676741",
"userName": "a-andromeda20211214030207513900000004"
},
"webIdFederationData": {},
"attributes": {
"creationDate": "2022-10-18T14:03:06Z",
"mfaAuthenticated": "false"
}
},
"invokedBy": "eks.amazonaws.com"
},
"eventTime": "2022-10-18T14:03:06Z",
"eventSource": "kms.amazonaws.com",
"eventName": "ListGrants",
"awsRegion": "us-gov-west-1",
"sourceIPAddress": "eks.amazonaws.com",
"userAgent": "eks.amazonaws.com",
"errorCode": "AccessDenied",
"requestParameters": null,
"responseElements": null,
"requestID": "073d6c6f-106a-4135-89e7-b241d6d58a25",
"eventID": "59b22a0b-5f4f-48a3-a3a1-4286d75d725e",
"readOnly": true,
"eventType": "AwsApiCall",
"managementEvent": true,
"recipientAccountId": "383988676741",
"eventCategory": "Management"
}
I have temporarily worked around this issue by making the following changes on the amazon console :

A proper fix would be for the terraform provider to make a new Policy which provides kms:ListGrants permissions.  Then the kms:ListGrants permission call could be made by health-check-session (which I believe is something in amazon eks infrastructure).

[x] ✋ I have searched the open/closed issues and my issue is not listed.

Versions

Module version 17.24.0

Terraform version:

Provider version(s):

Reproduction Code [Required]
This error can be found by creating ANY EKS cluster with  secrets encryption turned on:

and with the the default service-linked role (i.e. don't set vars to create your own role).  Then search the cloudwatch console for these error messages:
https://us-east-1.console.aws.amazon.com/cloudtrail/home?region=us-east-1#/events?EventName=ListGrants
Expected behavior
The cloudwatch logs should NOT say "AccessDenied" for the kms:ListGrants call.  They should return a null result.
Actual behavior

Terminal Output Screenshot(s)

Additional context
I searched the terraform-aws-eks repo to see where kms:ListGrants privileges are granted.  They are only associated with cluster encryption.  This also need to be associated with

Okay sorry i found the issue in an earlier bug report.  So, closing this now.
https://github.com/terraform-aws-modules/terraform-aws-eks/issues/1913


electron 5 resources/inspector

When packaging an electron 5 app on linux, there is a directory ../resources/inspector that was not seen on electron 4 builds. The app works fine without it. I am not sure what it is for, but in any case for a production application I would not want the user to inspect anything.
How can I prevent it being built?

I see this is really an electron question, not electron-packager. Electron 5 has this directory, but not Electron 4.


Submitted state on FormGroup in subcomponent is inconsistent/incorrect

Reproduction
https://stackblitz.com/edit/components-issue-form-group-submitted
Steps to reproduce:

Click on submit to see one submitted state become true but not the other

Expected Behavior
Both form groups should become submitted.
Actual Behavior
The component which uses a [formGroup] directive does not become submitted.
Environment

Angular: 8.0.0
CDK/Material: 8.0.0
Browser(s): Chrome
Operating System (e.g. Windows, macOS, Ubuntu): Ubuntu & StackBlitz

This repository is for Angular Material, but your question is entirely about the Angular framework, so you're in the wrong repository.
This behavior is correct/intended. For subforms you should use the formGroupName directive rather than another formGroup directive. Or better yet, implement a ControlValueAccessor.

I've added a new scenario to the StackBlitz which uses formGroupName but that does not do what I want either.
If that behavior is intentional as well I'll take this issue to https://github.com/angular/angular.


chore(main): release 1.0.4

:robot: I have created a release beep boop
1.0.4 (2023-06-19)
Bug Fixes

minor chart fix (#23) (3569238)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/Rookout/piper/releases/tag/v1.0.4 :sunflower:


⚠ Bofrost.fr has degraded performance

In 6f715fd, Bofrost.fr (https://www.bofrost.fr) experienced degraded performance:

HTTP code: 200
Response time: 1849 ms

Resolved: Bofrost.fr performance has improved in 65852f8 after 6 minutes.


(Bug) profile image should not be clickable in send screens

profile image is still  clickable in some of the send screens

@sirpy the profile image isn't clickable for send/recive via address screens
Video: https://www.screencast.com/t/qT0rwcXbG
Checked on  QA V1.4.1-2
LG V30+ // Android 8.0 // Google Chrome 85.0.4183.81
Desktop: Windows 10 // Google Chrome  85.0.4183.121


ESLPopup: add offset-trigger attribute

Closes: #2751

TODO: discuss popup logic of exact overriding element attributes (probably we don't need it)

It is logical for sure to have the current options priority:

   opt = {
      ...STATIC_DEFAULTS,
      ...attributes,
      ...actionParams
   }

But it doesn't sound excellent that having actionProps defined leads to attributes being rewritten... This point may become a blocker for consumers...


add support for csv

I have that with privateGPT already, but it's not very good with csv files and is a bit slow perhaps. Can you beat it?

twitter: https://twitter.com/vagero4/status/1676978801383821312

duplicate of #87

closing with a reference to #87


Low GPU-usage during training

Hi, with sockeye2, the GPU-Util in gpustat or nvidia-smi is often low. e.g. as follows:
[0] Quadro RTX 8000  | 50'C,   0 % | 44481 / 48571 MB
[1] Quadro RTX 8000  | 51'C,   0 % | 44705 / 48571 MB
[2] Quadro RTX 8000  | 45'C,   4 % | 44743 / 48571 MB
[3] Quadro RTX 8000  | 50'C,   3 % | 44313 / 48571 MB
[4] Quadro RTX 8000  | 44'C,   7 % | 43667 / 48571 MB
[6] Quadro RTX 8000  | 51'C,  46 % | 44745 / 48571 MB
[7] Quadro RTX 8000  | 48'C,   7 % | 45187 / 48571 MB

The process is run via sockeye.train and not with horovodrun. Is this behaviour expected or are there certain hyperparameters that I have set in a very unoptimized fashion?

Could you please share the training command you have used? Thanks.

What's the size of the data set, roughly? How many batches?
What's the CPU usage during training? How many hyperthreads (or actual cores)?
What happens if you train only on four "adjacent" devices, i.e. 0, 1, 2, 3 or 4, 5, 6, 7?

Hi @bricksdont and thanks for your suggestions!

Are you using sockeye.prepare before training?

Yes I am, and I used the following options for this training:
--pad-vocab-to-multiple-of 8 \
    --max-processes 8 \
    --bucket-width 8 \
    --shared-vocab \
    --max-seq-len "287:95"

What's the size of the data set, roughly? How many batches?

num_sents in data.config is 137'143'533 and one epoch consists of ~167'000 batches

What's the CPU usage during training? How many hyperthreads (or actual cores) on the machine?

CPU-Usage is nowhere near max, and there are 20 physical cores (40 hyperthreads) available.

What happens if you train only on four "adjacent" devices, i.e. 0, 1, 2, 3 or 4, 5, 6, 7?

This is quite interesting, with 2 different trainings at the same time, GPU-Usage is still not at its max, but by eyeballing the average GPU-usage seems to be higher (~60% per GPU it seems)

Just a hunch, perhaps 8 threads are not enough to keep all GPUs busy. The CPU usage is not expected to be at max for 40 cores, since you set OMP_NUM_THREADS to 8. Can you please check if CPU load of the Sockeye process is more or less 800% for 8 GPUs? And then try using more CPU threads.

Thanks a lot, I could very well imagine that this is the problem. The trainings that are currently running on 4 GPUs each use around 600-700% CPU each, so it seems that  OMP_NUM_THREADS 8 is not enough to saturate all 8 GPUs. I will not be able to verify it until Thursday, but I will post the results here asap. If this turns out to be the problem, the help-text for --omp-num-threads should maybe be adjusted, as it currently recommends to set it to the number of GPUs. Or is this usually enough, but just not on cards with a lot of VRAM?

Hi again, so we tested it again and set OMP_NUM_THREADS to 20 but it did not make a difference. Whether we use it set to 8 or to 20, total CPU-Usage of the sockeye process is around 1300% in both cases, which is quite strange given that in the former case it should be at most 800%.

Thanks for testing, increasing OMP_NUM_THREADS does not solve the problem it seems.

You could look into other env variables related to threads (https://mxnet.apache.org/versions/1.7/api/faq/env_var.html), for instance MXNET_GPU_WORKER_NTHREADS. I am not sure what exactly this variable does.
It would perhaps be helpful to ask in the Mxnet forum: https://discuss.mxnet.apache.org/ to get help from someone with a deeper understanding of Mxnet, or open a Github issue in Mxnet. For the latter it would be extremely helpful if you can provide a minimal, reproducible example.

Thanks for all the suggestions Mathias!
One more thing to try for testing purposes is to run single GPU training to see whether that get's the desired utilization on a single GPU (reducing the batch size accordingly).

We now tested it with one GPU and reduced the batch-size to 1/8 of the previous size, and the usage is much higher. It never drops below 70% and also, the single GPU is around 15°C hotter than in the 8 GPU-Setup, so it must be some issue with scaling to multiple GPUs.

Using multiple GPU devices on a single host with MXNet currently seems to not scale well. I would suggest setting up multi-gpu training with Horovod instead.


Trigger designer has a typo "noncontains" --> "notcontains"

The text in the trigger designer should be "notcontains":

Could catch!
Thank you,
Andrew


Suggestion: Use Homebrew / Linuxbrew for installation

This appears to be a direction that the Galaxy project is working toward. (https://trello.com/c/YmIBHyxm/2055-brew-module-installer, https://github.com/platform-brew/platform-brew) Seems time would be more productively spent writing formulas for a common package manager, rather than everybody doing their own thing. Wider adoption, less maintenance / duplication of effort, and whatnot. You'd lose support for Windows; but, given the easy use of Ubuntu VMs and the prevalence of Unix-only bio software, that isn't necessarily a bad thing.

Dear Kevin,
thank you very much for your feedback. I was thinking about your idea for few months. I also did some testing with Brew on several computers. Brew (Science) seems to work well on OS X but I have been experiencing great difficulties on Linux. For sure it is a great project and I like it but I don't see how to incorporate it easily into SMBL such that compilation of at least SamTools, BWA, etc. would work everywhere without need of installation of any special software.
SMBL aims at situations when someone wants to use some of basic bioinformatics programs in a Snakemake pipeline and wants to ensure presence of those programs on user's computer (typical situation: script for a supervisor/student). The only prerequisite are SMBL (which can be installed together will Snakemake by pip3 install smbl) and few programs (GCC, Git, etc.) which should be present on any Unix machine.
I do not plan to spend much time by adding new formulas (as for example people in the Brew Science project do and I am grateful to them for it). I am aware of limitations of SMBL and I add mainly those programs that I use in my own projects.


Source code requires hxCodec to be installed globally, ignoring HMM install

Describe your bug here.
I've been trying to make a build from the latest Psych Engine. However, despite hmm's attempt of installing hxCodec 2.5.1, the source code treats it that hxCodec doesn't exist.
Command Prompt/Terminal logs (if existing)
PS C:\Users\<username>\Documents\GitHub\FNF-PsychEngine> haxelib install hmm
You already have hmm version 3.0.0 installed
PS C:\Users\<username>\Documents\GitHub\FNF-PsychEngine> haxelib run hmm install
haxelib --never newrepo
Local repository created (C:/Users/<username>/Documents/GitHub/FNF-PsychEngine/.haxelib)
haxelib --never install lime
Downloading lime-8,0,1.zip...
Download complete: 0.24KB in 1s (0.2KB/s)
Download complete: 122.37MB in 6.7s (18029.3KB/s)
Installing lime...
  Current version is now 8.0.1
Done
haxelib --never install openfl
Downloading openfl-9,2,1.zip...
Download complete: 0.24KB in 0.9s (0.2KB/s)
Download complete: 2.7MB in 0.7s (3803.7KB/s)
Installing openfl...
  Current version is now 9.2.1
Done
haxelib --never install flixel
Downloading flixel-5,2,2.zip...
Download complete: 0.24KB in 1s (0.2KB/s)
Download complete: 1.14MB in 0.3s (2940.4KB/s)
Installing flixel...
  Current version is now 5.2.2
Done
haxelib --never install flixel-addons
Downloading flixel-addons-3,0,2.zip...
Download complete: 0.25KB in 0.9s (0.2KB/s)
Download complete: 217.03KB in 0.3s (713.9KB/s)
Installing flixel-addons...
  Current version is now 3.0.2
Done
haxelib --never install flixel-tools
Downloading flixel-tools-1,5,1.zip...
Download complete: 0.25KB in 0.9s (0.2KB/s)
Download complete: 61.88KB in 0.2s (243.6KB/s)
Installing flixel-tools...
  Current version is now 1.5.1
Done
haxelib --never install flixel-ui
Downloading flixel-ui-2,5,0.zip...
Download complete: 0.24KB in 1.1s (0.2KB/s)
Download complete: 192.59KB in 0.5s (371.7KB/s)
Installing flixel-ui...
  Current version is now 2.5.0
Done
haxelib --never install hxcpp
Failed. Triggering retry due to HTTP timeout
retry sucessful
Downloading hxcpp-4,2,1.zip...
Download complete: 0KB in 10.1s (0KB/s)
Failed to download https://lib.haxe.org:443/files/3.0/hxcpp-4,2,1.zip. (1/3)
Blocked
Download complete: 0.24KB in 0.9s (0.2KB/s)
Download complete: 14.37MB in 1.1s (13065.9KB/s)
Installing hxcpp...
  Current version is now 4.2.1
Done
haxelib --never install tjson
Downloading tjson-1,4,0.zip...
Download complete: 0.24KB in 0.9s (0.2KB/s)
Download complete: 5.26KB in 0.6s (8.1KB/s)
Installing tjson...
  Current version is now 1.4.0
Done
haxelib --never install hxjsonast
Downloading hxjsonast-1,1,0.zip...
Download complete: 0.24KB in 0.9s (0.2KB/s)
Download complete: 8.96KB in 0.5s (15.6KB/s)
Installing hxjsonast...
  Current version is now 1.1.0
Done
haxelib --never install hxCodec 2.5.1
Downloading hxCodec-2,5,1.zip...
Download complete: 0.24KB in 0.9s (0.2KB/s)
Download complete: 66.39MB in 3.5s (18957.1KB/s)
Installing hxCodec...
  Current version is now 2.5.1
Done
haxelib --never install hscript
Downloading hscript-2,5,0.zip...
Download complete: 0.24KB in 0.9s (0.2KB/s)
Download complete: 165.93KB in 1.6s (99.4KB/s)
Installing hscript...
  Current version is now 2.5.0
Done
haxelib --never install hxcpp-debug-server
Downloading hxcpp-debug-server-1,2,4.zip...
Download complete: 0.25KB in 0.9s (0.2KB/s)
Download complete: 24.72KB in 0.5s (47.8KB/s)
Installing hxcpp-debug-server...
  Current version is now 1.2.4
Done
haxelib --never git discord_rpc https://github.com/Aidan63/linc_discord-rpc master
Installing discord_rpc from https://github.com/Aidan63/linc_discord-rpc branch: master
Library discord_rpc current version is now git
Installing dependency hxcpp 4.2.1
You already have hxcpp version 4.2.1 installed
haxelib --never git hscript-ex https://github.com/ianharrigan/hscript-ex master
Installing hscript-ex from https://github.com/ianharrigan/hscript-ex branch: master
Library hscript-ex current version is now git
haxelib --never git linc_luajit https://github.com/nebulazorua/linc_luajit master
Installing linc_luajit from https://github.com/nebulazorua/linc_luajit branch: master
Library linc_luajit current version is now git
haxelib --never list
discord_rpc: [git]
flixel-addons: [3.0.2]
flixel-tools: [1.5.1]
flixel-ui: [2.5.0]
flixel: [5.2.2]
hscript-ex: [git]
hscript: [2.5.0]
hxCodec: [2.5.1]
hxcpp-debug-server: [1.2.4]
hxcpp: [4.2.1]
hxjsonast: [1.1.0]
lime: [8.0.1]
linc_luajit: [git]
openfl: [9.2.1]
tjson: [1.4.0]
PS C:\Users\<username>\Documents\GitHub\FNF-PsychEngine> lime build windows
source/Achievements.hx:132: characters 30-54 : Warning : `FlxCamera.defaultCameras` is deprecated, use `FlxG.cameras.setDefaultDrawTarget` instead
Error: Could not find haxelib "hxCodec", does it need to be installed?
PS C:\Users\<username>\Documents\GitHub\FNF-PsychEngine>

Are you modding a build from source or with Lua?
Source
What is your build target?
Windows
Did you edit anything in this build? If so, mention or summarize your changes.
No

Looks like the code is checking if hxCodec is installed globally, invalidating the requirement of having HMM.

Try this command: haxelib --global install hxCodec 2.5.1.

yes, I did that. Does anyone know why HMM's download of hxCodec doesn't work then?

I think you need to have the --global tag on both hmm commands when installing to have the download be global. That should really be reflected in the readme file in my opinion but it isn't as of now. Is hxCodec working now or are you still facing the same issue?

I think you need to have the --global tag on both hmm commands when installing to have the download be global.

I think you need to have the --global tag on both hmm commands when installing to have the download be global.

What I meant by my comment was that on a fresh install you need the global tag, not that you specifically should reinstall hmm with the tag. I apologize that I was unclear.

huh. I only --global installed hmm and haxeflixel, in honesty.

I'm now having this issue, can anyone help?


”Târșolț”, ”Aliceni” are listed in the drop-down menu

Description:
When user writes ”Târșolț”, ”Aliceni” the locations appear in the drop-down menu next to the comune and the county which is a part according to the law.
Precondition:
The website is up an running.

Step 1
Write in the search bar "Târșolț"

Expected results
The location appears in the drop-down menu as "Sat Târșolț, SATU MARE (Târșolț)".

Step 2
Press "x" button.

Expected results
The location was deleted from the search bar.

Step 3
Write in the search bar "Aliceni"

Expected results
The location appears in the drop-down menu as "Sat Aliceni, SATU MARE (Târșolț)".


Restart auth flow when Strava is logged out

Not the best approach but it should work.
fix #178

Coverage remained the same at 6.272% when pulling 62af9f52a5298bbc11190a3030063f5e2a5b68e4 on mscansian:patch-1 into a8ae0ce3d77004bbc1d2c1e7ed34b14c344cddba on Tigge:master.

I merged #178, so I guess this can be closed then?


[Feature]eternal storage

Let's discuss this ;)

This is an interesting approach. In my opinion, though, it tries to be too general purpose, and kind of reimplements the EVM storage mechanism, which is already a mapping of keys to values. Upgrading a contract to one that shares the same storage variables (in the same order), and maybe adds new ones, should serve the same purpose for upgradeability.

@frangio are you talking about something like
Contract A {  struct MyType {  uint nb; } mapping<address, MyType> map; function addToMap(); function delFromMap(); } contract B { A storage; function addSomething(uint val) { storage.addToMap(val) }  ?

No, I'm thinking of something lower level.
contract MyContractV1 {
    uint256 x;
    function foo() {
        return x;
    }
}

which if it is accessed behind a delegating proxy can be safely upgraded to something like
contract MyContractV2 is MyContractV1 {
    uint256 y;
    function bar() {
        return x + y;
    }
}

Using inheritance is just a shorthand way of getting the variables to line up.

I see what you mean.
But wouldn't that be unmaintanable in the long run?
contract MyContractV42 is MyContractV41 {
uint256 y;
function bar() returns (uint256) {
return x + y;
}
}

Yes, using inheritance would not be very maintainable. It should definitely not be the long term strategy. I think with the right tooling this approach to upgradeability can be very maintainable and safe to use.
What gas costs are you referring to? I'm pretty sure the gas costs remain constant from upgrade to upgrade. The inheritance chain would be resolved and optimized by the compiler.

I was thinking more about the gas cost when setting information.
If you need to call setA, setB, setC as external call to other contracts it will be more expensive than calling a single set on a single contract

@SylTi what do you think about using an EternalStorage contract like:
contract EternalStorage {

  mapping(bytes32 => uint256) internal uintStorage;
  mapping(bytes32 => string) internal stringStorage;
  mapping(bytes32 => address) internal addressStorage;
  mapping(bytes32 => bytes) internal bytesStorage;
  mapping(bytes32 => bool) internal boolStorage;
  mapping(bytes32 => int256) internal intStorage;

}

If we have them all as internal variables is enough, then we can leave as responsibility of the dev to provide the get functions.

I'm not sure of why you would want an eternal storage without gets? How do you use the data stored?

@SylTi what about using this implementation https://github.com/ethereum/EIPs/issues/930 ?
There is an example of BasicToken using ES.

Closing for now because we don't see this being a part of OpenZeppelin.


Pagination is extremely slow for a profile with a lot of followers

If I take a profile like this:
$id = '470555998474494414';

$limit = 500;

$offset = 2000;

$followers = $bot->pinners->followers($id, $limit)->skip($offset)->get();

which has like 59k followers, it takes around 2 minutes to execute
whereas by using $limit = 500 and $offset = 0 it takes around 30 seconds.
So if the user has 59k followers, and I put $offset = 58500; the script takes forever to execute.
Any ideas how to deal with profiles with many followers?

Hi. You are right. Unfortunately, under the hood, the bot has to loop through all previous followers. Pinterest doesn't provide explicit API for it. So, the bot behaves exactly like the site.

I thought so. I think I will just write some javascript that will scroll down and grab the usernames.
Still, I really like your project and I appreciate your answer!


Allow selecting options by passing current values

At the minute the only way to pre-select or check specific items when using the Nunjucks macros for these components is to pass a boolean flag for each item, which then maps directly to the checked / selected HTML attribute for the  / .
This means the user has to do the work to map the previous form data back to a boolean, resulting in code that might look something like this:
{{ govukSelect({
    id: "sort",
    name: "sort",
    label: {
        text: "Sort by"
    },
    items: [
        {
            value: "published",
            text: "Recently published",
            selected: (data['sort'] == "published")
        },
        {
            value: "updated",
            text: "Recently updated",
            selected: (data['sort'] == "updated")
        },
        {
            value: "views",
            text: "Most views",
            selected: (data['sort'] == "views")
        },
        {
            value: "comments",
            text: "Most comments",
            selected: (data['sort'] == "comments")
        }
    ]
}) }}

This is prone to introducing errors (especially when prototyping) – for example, any changes to the name of the field or the value of the item also need corresponding changes made to the boolean logic, potentially in multiple places.
Allow the user to pass the current value (or array of values, for checkboxes), and using that to work out which item(s) should be checked or selected.
The above example can then be done like this:
{{ govukSelect({
    id: "sort",
    name: "sort",
    label: {
        text: "Sort by"
    },
    items: [
        {
            value: "published",
            text: "Recently published"
        },
        {
            value: "updated",
            text: "Recently updated"
        },
        {
            value: "views",
            text: "Most views"
        },
        {
            value: "comments",
            text: "Most comments"
        }
    ],
    selectedValue: data[‘sort’]
}) }}

Naming the new option has presented a few challenges – I wanted to avoid using checked or selected so that we don’t have options at different ‘levels’ with the same name but accepting different types of values – booleans for individual items and strings / arrays at the top level.
I also felt that value was not an accurate description for what the option did, and may also be confused with item.value (and the top-level value option on other form controls such as text inputs).
I’ve ended up combining the two whilst also trying to be consistent with the underlying HTML attribute, and also reflecting whether the option accepts a string or an array. This does unfortunately mean that the option name is different for each of the three components:

checkedValue for Radios, where a string is passed to check a single radio button
checkedValues for Checkboxes, where an array of strings is passed to check one or more checkboxes
selectedValue for the Select, where a string is passed to select a single option.

I think on balance, although I can see how this may be confusing for users, it is logical and consistent within each individual component.
Closes #2449.

I've raised a PR with a proof of concept of how this could be extended in the Prototype Kit to allow pre-selecting radios and checkboxes from the data object without the user having to do anything, which seems kinda neat: https://github.com/alphagov/govuk-prototype-kit/pull/1316

Naming the new option has presented a few challenges – I wanted to avoid using checked or selected so that we don’t have options at different ‘levels’ with the same name but accepting different types of values – booleans for individual items and strings / arrays at the top level.
I also felt that value was not an accurate description for what the option did, and may also be confused with item.value (and the top-level value option on other form controls such as text inputs).

I'd argue strongly for calling it value. I agree that it is not a completely accurate description, because users will be used to value from other macros, using value here will be the least surprising, in my opinion. I think having the parameter named different for different macros will add friction, and I'm not sure whether there would be a benefit to it.

I think I've addressed the comments from @owenatgov but it could do with another once over. Then I believe this is ready to merge once v4.1.1 is out.


[Explorer] Redesign of Owned Coins Section

Following Figma, this PR redesigns the owned coins section. The Owned Objects is also restructured to simplify future updates of this code.
Screen Recording (on Google Chrome)
https://user-images.githubusercontent.com/11377188/184159643-ad34ff6d-707e-461c-9042-56070ef5c102.mp4
This Screen Recording shows what the new Owned Coins Section looks like on Desktop and the Galaxy Fold. The first part of the video looks at live data where we only have one coin (SUI). The second part of the video uses mock data to show what the Owned Coins section looks like in the case of multiple different types of coin held.

Figma file for reference,
https://www.figma.com/file/kSD0qXCIDZA4KQVNepA5hR/02-Explorer?node-id=204%3A54560

Figma file for reference, https://www.figma.com/file/kSD0qXCIDZA4KQVNepA5hR/02-Explorer?node-id=204%3A54560

Thanks for the URL. In the original design there was a grey background; I'll switch to this new blank background. I'll also make the changes to mobile as described above.

Figma file for reference, https://www.figma.com/file/kSD0qXCIDZA4KQVNepA5hR/02-Explorer?node-id=204%3A54560

@mystie711 --> The point raised regarding scrollbars is an excellent observation. The exact appearance of the scrollbar will vary across Operating Systems and across browsers. It applies to all scrollable content including when we look at modules in a package. In the example above, we're looking at Google Chrome on a Windows OS, which goes for a very particular look for the scrollbar by default.
Because this issue affects the whole website, I've handled it in a separate PR https://github.com/MystenLabs/sui/pull/3931. There are limits on what we can do for each browser and Operating System but we can make it more consistent with Figma, which is what this PR does.

Agree @Andrew47 !
I left a note on Slack after huddle with @Jordan-Mysten,
https://mysten-labs.slack.com/archives/C03RUGM5J8P/p1660246494508639?thread_ts=1660243535.444779&cid=C03RUGM5J8P

@mystie711 --> Updated Look for Coin Aggregation:
https://user-images.githubusercontent.com/11377188/184668227-8c581fdd-890b-4687-97ab-01408fd9032a.mp4

@stella3d / @Jordan-Mysten / @mystie711 --> The above feedback has been incorporated / responded to and, following discussion on Slack, we have buy-in on the Design. Is this PR good for merge?


Could not start Intero : Invalid package ID: "array-<IP_ADDRESS> base-<IP_ADDRESS> binary-<IP_ADDRESS> bytestring-<IP_ADDRESS>"

using lts-9.2.
stack version:
Version 1.5.1, Git revision 2fbc3e93121b97d41f125b3aba9e9f2d8c62888f x86_64 hpack-0.18.1
$ stack new intero-bug simple
creates Main.hs
Opening Main.hs in emacs results in

Intero is not installed in the Stack environment.
Installing intero-0.1.21 automatically ...
Invalid package ID: "array-<IP_ADDRESS> base-<IP_ADDRESS> binary-<IP_ADDRESS> bytestring-<IP_ADDRESS>"
Could not install Intero!
We don't know why it failed. Please read the above output and try
installing manually. If that doesn't work, report this as a
problem.
I see that gcharnock added a similar comment to closed issue #252

Thanks, closing in favor of the original issue which has more context.


Changed the bridge-app to use temperature sensors rather than switches.

Problem
Updated the bridge-app to use temperature sensors rather than switches to match recent changes to the bridge test plan.
Running some of the commands for the bridge test plan and action clusters test plan caused a "Chip stack locking error".
Change overview
The switches in the bridge-app were change to temperature sensors to match
the updated bridge test plan.
A lock was also added in a few places in the bridge-app to fix errors that reported reported
a "Chip stack locking error"
Testing

Start bridge app and wait for initialization to complete
Run chip-tool pairing
chip-tool pairing ethernet 12344321 20202021 3840 localhost 5540
Get the measured-value for a temperature sensor
chip-tool temperaturemeasurement read measured-value 12344321 4
Press t in the bridge-app to change the measured-value for all temperature sensors
Get the measured-value for the same temperature sensor and verify that it has changed.

Fast-tracking example app change that has been up for review for a while.


Integrate Galileo deployment with CD

[ ] Create galileo-preview deployment to run against the main branch of penumbra and testnet-preview. Perhaps send messages to a different private channel or disable Discord messaging entirely.
[ ] Modify testnet-preview GitHub Action to automatically deploy galileo-preview on main branch
[ ] Modify testnet deploy GitHub Action to automatically deploy galileo on testnet release tag
[ ] Update testnet deployment template to incorporate any changes to process

The trickiest thing is that we need to pin the dependency versions of the penumbra repos within the Galileo Cargo.toml.

We've been doing reasonably well with a barebones setup, so I don't think we need to prioritize this.


Converted Markdown files to reStructuredText

In this PR

All the documentation files except the README.md were converted from md to rst.
Links were fixed in order to be correctly parsed by Sphinx.

Thanks for the review @hidmic , just finished addressing your comments and to fix some other minor things here and there.

Ok, I think this one's ready.


Removed editor config.

Would it cause any problems for you JetBrains users to remove these files from version control?
I like the repository to only include what is necessary.
Other repos like React and ESLint ignore .idea from git.

I'm happy to remove it for this project as its small and not a huge deal.
In terms of what Facebook are doing.. I already ignore all the user specific settings. Whats left in the idea folder is the shared project settings.
Any substantial projects I kinda don't want to ignore them.. They are solution files and makes sure all developers are using the same project settings in the idea (linting turned on and ignoring build folders for instance). This is to our advantage.
It's the same for the visual studio code workspace settings.json file we probably shouldn't ignore it.
Typically I always use https://www.gitignore.io/ as a standard.

It would be cool if JetBrains and other IDEs had a way of sharing config across multiple projects, like what we are doing with our ESLint config. I can understand the benefit of making sure all developers are using the same project settings, but it would be even better if those settings were consistent across many projects, and then we could avoid adding proprietary files like .idea to each project repo.

Yeah that would be cool.. I think it makes sense to keep our "library" repos clean as you mentioned and just keep the solution files for projects.


ENH: Handle S1 COGs from Copernicus Dataspace

It would be great to handle S1 COGs from Copernicus Dataspace now that SNAP 10 is out.

[ ] Figure out SNAP version when constructing a SAR object (only in non ortho modes)
[ ] If SNAP>10, let it pass, else raise a NotImplementedError
[ ] If SNAP<8, raise an error to call for an update of the software

For SNAP version, maybe parse:
>>> gpt --diag
INFO: org.esa.snap.core.gpf.operators.tooladapter.ToolAdapterIO: Initializing external tool adapters
INFO: org.esa.snap.core.util.EngineVersionCheckActivator: Please check regularly for new updates for the best SNAP experience.
SNAP Release version 9.0.0
SNAP home: C:\Program Files\snap\bin\/..
SNAP debug: null
SNAP log level: null
Java home: c:\program files\snap\jre\jre
Java version: 1.8.0_242
Processors: 16
Max memory: 39.1 GB
Cache size: 8.0 GB
Tile parallelism: 4
Tile size: 1024 x 1024 pixels

To configure your gpt memory usage:
Edit snap/bin/gpt.vmoptions

To configure your gpt cache size and parallelism:
Edit .snap/etc/snap.properties or gpt -c ${cachesize-in-GB}G -q ${parallelism}

Function snap.get_snap_version has been implemented in sertit-utils. To be released in newt version.


Web Worker support

Currently, AFAIK it is not possible to use copc.js with workers without some form of hack.
The most performance critical part seems to be the LAZ decompression (namely Las.PointData.decompressChunk()). This could very easily be done in a worker while keeping the API almost identical.
I could try to setup a rough PR for discussion if you'd like.

Can you be more specific with exactly what you are trying to accomplish and what issue you are running into?

I'm implementing COPC support for the web library Giro3D.
I would like to move the laz decompression part in a worker. The decompression occurs in Copc.loadPointDataBuffer(), but I don't see how I could inject the worker logic so that the Las.PointData.decompressChunk() happens in a worker.

All of the functions here are part of the public API.  If you'd like to pull them apart and run some of those parts in a web worker, you can do so.  This library provides building blocks and utility functions (and also works in NodeJS), so putting implementation details of composable functions would probably be out of scope here.
For example, in Potree we pass a compressed LAZ buffer received from the fetch API into a worker, where we decompress it and create a View of it, and then extract the data into GL-compatible buffers.
If you specifically want Las.PointData.decompressChunk() to happen in a worker, with the goal of achieving the functionality of Copc.loadPointDataBuffer(), then you can see here that you can use the existing API to do something like this:
function mainThreadStuff() {
  // Here you would already have the COPC metadata, LAS header, node you wish to fetch, etc.
  const compressed = await Copc.loadCompressedPointDataBuffer(filename, node)
  someWorker.postMessage({ compressed, header, node }, [compressed])
}

// Worker code.
function decompress(event) {
  const { compressed, header, node } = event.data
  const { pointDataRecordFormat, pointDataRecordLength } = header
  const { pointCount } = node

  const decompressed = Las.PointData.decompressChunk(
    compressed,
    { pointCount, pointDataRecordFormat, pointDataRecordLength },
    lazPerf
  )
  postMessage(decompressed, [decompressed])
}

I just typed this up now as pseudo-code so do not expect it to work - but hopefully it demonstrates my point: that the building blocks you need to accomplish this via web worker are already part of the public API.

Thanks ! I'll try that and inform how it goes

loadCompressedPointDataBuffer() is not part of the public API AFAIK. It is not exported in the Copc object:
export const Copc = {
  create,
  loadHierarchyPage,
  loadPointDataBuffer,
  loadPointDataView,
}

That's why I couldn't "inject" my worker

That's true, it's such a light wrapper that I probably wasn't sure it was worth exposing - since it's just a range fetch.  So a more accurate code sample would use your COPC getter:
  const { pointDataOffset, pointDataLength } = node
  const compressed = await get(pointDataOffset, pointDataOffset + pointDataLength)

But that can absolutely be added to the public API - no objections to that.

Added, and published to npm as current latest version 0.0.7.

Thanks for your quick response !


Remove em() function

Per this discussion over on Bourbon, we’ll be removing the em() function. This PR removes the use of it from Neat. It really wasn’t doing very much, any way.
I made up 1200px and am open to that being something else.

Looking good to me.

Yeah looks good, let's merge this.


Feature request for world blacklist

I want request a HuskSync feature that can stop the data sync when player in a blacklisted world
I have a parkour plugin which it handle players in a standalone world with standalone inventories, when player leave the parkour, it will restore the inventory
But if player disconnect when they're in parkour world, HuskSync will sync their game menu inventories so player can take all GUI items out of parkour world to survival like bedrock, barrier etc.

Low priority after some thought.
Adding this would require implementing logic for re-syncing players when changing world and inevitably increase the surface area for bug-prone code, for something thats somewhat against the spirit of the plugin's core use case (to load balance [survival multiplayer] server worlds across multiple instances)


$CI_PROJECT_PATH doesn't exist in service

Expected behavior:
In a service for a job, I would expect /builds/$CI_PROJECT_PATH to refer to an existing directory that contains the project files. In other words: parity with GitLab CI.
Actual behavior:
GCL doesn't mount the project files anywhere.

Are you sure services gets a copy of the project files?
I just read the this https://docs.gitlab.com/ee/ci/services/ and nowhere was project files inside service container mentioned.
Can you paste an example, where project files are needed by a service, and I'll run it by my "debugging" gitlab runner to investigate the workflow?

I ran into it with a company image that I can't share here, but it relies on /builds/$CI_PROJECT_PATH/some/path being present.
Technically the path relative to the the project directory is populated by a different job so it is possible it is only available in the service when it is published as an artifact, but I didn't see any immediate connection there.

I agree with @firecow, this is a special case of yours. Even the artifacts are not accessible to services.
There may be special mounting on your runners...

We need an example to use in a potential integration test, and for reproduction.

I'm closing this one for now.
Please do reopen, if an actual minimal example is provided.

should be fixed with #661


doomfist seems to ignore doors?

https://github.com/MaxwellJung/ow1_emulator/assets/107174676/d6545211-b680-4dac-a3cf-1a4b5197639a

duplicate of #294


Comment blog broken link due to rebranding

AFAIK, there is not a replacing page for this atm.

We can probably just link to the October article tbh.

We can probably just link to the October article tbh.

This is a decision I'm not in charge of :]
I just wanted to warn about this tiny issue when discovered it.


[feature-request] Auto Import .hdll Files

Not sure if this is feasible, but it would be very handy if there was a way for a haxelib to automatically import .hdll files from a haxe lib into your project.
Take my use case for example - I use hlimgui in several Heaps projects. Whenever I need to make a change to hlimgui, I have to rebuild the .hdll, then copy/paste it into all my projects. This can be tedious as the number of projects using hlimgui increases.
It would make this process much more convenient if haxelib was able to find any .hdll files in the root of the library (or from some user-defined directory in the library), then automatically link them to your project.

For local development, you can put the hdll into the library path along with the base ones that ship with HashLink. See HashLink's Makefile for the path, it's /usr/local/lib for me. Then you shouldn't need to have a .hdll copy per project, unless you want to ship it.
In terms of a Haxe feature, this sounds like something a build macro could do.

For local development, you can put the hdll into the library path along with the base ones that ship with HashLink. See HashLink's Makefile for the path, it's /usr/local/lib for me. Then you shouldn't need to have a .hdll copy per project, unless you want to ship it.
In terms of a Haxe feature, this sounds like something a build macro could do.

I actually made a macro on my sub projects that haxe hdll files to copy them to the output of the current target build along with any other runtime files needed. So in this case, you can add a build macro to hlimgui that copies the prebuilt hdll over to any project that includes the -lib
Keep in mind other targets that use hashlink won't necessarily have hdll files but .so?


nc unable to listen to reverse connection

Hello sir! Did you everything same as on PoC video?

Yes sir everything same but you did not show how to compile apk

yes i did everything same but unfortunately not getting any connection back. firewall allowed too

What was cmdline output when you execute the shfile.ps1 on the powershell? shfile.ps1 needs a http server to get actual reverse shell script.

no output at all. even with an execution policy set with powershell while running the script . i'm listening on nc -lvp
4545

it's ok i got it now


Deprecation notice

Hi Jharrod,
Since this plugin has been merged into the official Ansible v2 codebase, I wondered if you would consider a deprecation notice in the readme so that people submit bugs and PR improvements to that version instead?
Have added the notice on the merged version in my own profile.

+1

Added a note to the read me.


[tracking] stable release - 4.6.0-0.okd-2021-01-23-132511

Issues fixed:

[ ] #322
[ ] #471

Notable unresolved issues:

#402
This requires fix landing on buildfarm and image rebuild. Critical for image mirroring
#398
Seems to be affecting proxy setups. Make sure all repos on hosts are disabled or have valid proxy configs added
#405
OVN seems to be using more CPU than it used to on 4.5. Needs bugzilla
#430
OpenshiftSDN upgrades are broken

https://github.com/openshift/okd/releases/tag/4.6.0-0.okd-2021-01-23-132511
https://amd64.origin.releases.ci.openshift.org/releasestream/4-stable/release/4.6.0-0.okd-2021-01-23-132511

https://github.com/openshift/okd/releases/tag/4.6.0-0.okd-2021-01-23-132511
https://amd64.origin.releases.ci.openshift.org/releasestream/4-stable/release/4.6.0-0.okd-2021-01-23-132511


Multicolumn indexes

Multicolumn indexes are useful in databases and also would be useful for ACSets. For example, a mapping table (i.e. a span A<-R->B, encoding a relation) is naturally indexed by its two outgoing morphisms to quickly check if (a,b) are related.
I'm not sure what needs to change in the underlying data structure, but an interface might look like this:
@present SchTest(FreeSchema) begin
 (A,B,C,R)::Ob
 f::Hom(R,A)
 g::Hom(R,B)
 h::Hom(R,C)
end

@acset_type Test(SchTest, index=[:h, (:f,:g)])

X = apex(terminal(Test))

incident(X, (1,1), (:f,:g)) # == [1]

Just want to note that I think this would be fantastically useful. In trying to use acsets to store data to parameterize practical optimization tasks, I have found myself wishing this feature existed.
I wonder also if it might work nicely with the ideas in https://github.com/AlgebraicJulia/Catlab.jl/issues/844, certainly it would be very nice to index products this way.

In addition to being able to do something similar to @kris-brown's proposed interface as above, I wonder if sequences of morphisms could also be supported in some future implementation of this feature. The following example is an example of a pattern that seems to come up very often in working with data in applied settings:
using ACSets

MySch = BasicSchema(
    [:X,:Y,:Rel],
    [(:proj_x,:Rel,:X),(:proj_y,:Rel,:Y)],
    [:NameType,:NumberType],
    [(:xname,:X,:NameType),(:yname,:Y,:NameType),(:cost,:Rel,:NumberType)]
)

@acset_type MyDataType(MySch, index=[:proj_x,:proj_y], unique_index=[:xname,:yname])

mydata = @acset MyDataType{Symbol,Float64} begin
    X = 4
    Y = 3
    xname = [:widget1,:widget2,:widget3,:widget4]
    yname = [:place1,:place2,:place3]
end

costs = rand(4,3)

add_parts!(
    mydata, :Rel, prod(size(costs)),
    proj_x = repeat(1:4,3),
    proj_y = vcat(map(i->fill(i,4),1:3)...),
    cost = vcat(costs...)
)

# a pattern that comes up very, very often
mydata[
    intersect(
        incident(mydata, :widget3, [:proj_x,:xname]),
        incident(mydata, :place2, [:proj_y,:yname])
    ),
    :cost
]

In addition, I believe it was previously discussed that at least in the case where the relation is a binary product, and where we want to be able to efficiently do this with caching, one would store a matrix to get these preimages, or an multidimensional array for the n-ary product. I'm not sure if the initial implementation of this feature also needs to consider the general case of a relation that may not be a (multi)product, where I guess one would store a sparse array.
I think that a prototype that nontheless would be useful immediately upon release would be to get the "non cached" version working that computes everything on the fly. This would also help work out the general methods and or structs that need to be implemented/modified for the overall case.


aws-vpc: add support for multiple route tables

Resolving conflicts for pull request #561 and adding documentation.
This change adds the option of the RouteTableID being passed as an array instead of a
string, allowing multiple route tables to be specified.
Todos

[ ] Tests
[X] Documentation

@pingles @t0mmyt Curious to know if you have done any level of manual testing of this PR? I'd like to get this PR merged soon, so won't hold it up too long for not having the tests if there is some level of manual testing done.

We've been running this (albeit against an older release) for quite a few months now without any noticeable issue.

@t0mmyt which release/commit?

f6d7239  on Nov 9 2016.  We've had the current build (prior to the log changes) running on one cluster since this pull request

can you squash both commits?

Done

If you want, I can deploy this build tomorrow morning (it's late here now) and confirm all still works.

Looks good to me  - thanks @gunjan5 for the review and @t0mmyt for the rebase+docs and @pingles for the original code.
@gunjan5 do you want to do the honors and hit merge once travis passes?


Dynamic metadata match not working

Title: Dynamic metadata match not working
Description:
I'm using the lua filter to analize some headers and set some dynamic metadata. That metadata is used in config.route.v3.RouteMatch.dynamic_metadata for route matching.
Using the following configuration with curl localhost:8080 -i then the result is:
HTTP/1.1 404 Not Found
date: Sat, 25 Jun 2022 02:42:15 GMT
server: envoy
content-length: 0

but if I uncomment these lines in lua method
--request_handle:headers():add("my-header", "my-header-value")
--request_handle:headers():remove("my-header")

then the result for the same curl is
HTTP/1.1 200 OK
content-length: 9
content-type: text/plain
date: Sat, 25 Jun 2022 02:45:59 GMT
server: envoy

It works!

Config:
static_resources:
  listeners:
  - name: listener_0
    address:
      socket_address:
        address: <IP_ADDRESS>
        port_value: 8080
    filter_chains:
    - filters:
      - name: envoy.filters.network.http_connection_manager
        typed_config:
          "@type": type.googleapis.com/envoy.extensions.filters.network.http_connection_manager.v3.HttpConnectionManager
          stat_prefix: ingress_http
          http_filters:
          - name: envoy.filters.http.lua
            typed_config:
              "@type": type.googleapis.com/envoy.extensions.filters.http.lua.v3.Lua
              inline_code: |
                function envoy_on_request(request_handle)
                  -- UNCOMMENT NEXT 2 LINES TO START WORKING

                  --request_handle:headers():add("my-header", "my-header-value")
                  --request_handle:headers():remove("my-header")

                  request_handle:streamInfo():dynamicMetadata():set("envoy.filters.http.router", "somepath", "somevalue")
                end
          - name: envoy.filters.http.router
          route_config:
            name: local_route
            virtual_hosts:
            - name: local_service
              domains: ["*"]
              routes:
              - match:
                  prefix: "/"
                  dynamic_metadata:
                  - filter: "envoy.filters.http.router"
                    path:
                    - key: somepath
                    value:
                      string_match:
                        prefix: somevalue
                direct_response:
                  body:
                    inline_string: 'It works!'
                  status: 200

Repro steps:

Download envoy 1.21.1
Run envoy with config file from above
run curl localhost:8080 -i and expect status code 404
stop envoy
Uncomment the lines mentioned in the description
repeat step 2) and 3) but now expect status code 200

The requests cannot match any route entry at first because the dynamic_metadata match. Although you update the dynamic metadata by the Lua code, the initial match result (null) will not be changed. So 404 Not Found will be return by the Envoy.
But if you uncomment the headers updating code, the lua filter will clear the inital match result and for Envoy to re-match the route entry.  So 200 OK will be return by the Envoy.

@wbpcode this is also an issue with a go plugin implementation.
My understanding is that this is a bug.
Can this issue be re-opened?

@tobeyOguney This is not a bug. It is by design. The go plugin need to support route cache clearing if you want to match the dynamic metadata after the go plugin updated the dynamic metadata.

Thanks for clarifying that. @wbpcode
Did further digging in the documentation and found where the route caching mechanism is referenced.
Issue can remain closed.


Standard format for examples

Is there a standard format for adding examples to the documentation. Some of our commands can get a little complex, and it's nice to print examples that can be copied pasted.
Naval Fate.

Usage:
  naval_fate ship new <name>...
  naval_fate ship <name> move <x> <y> [--speed=<kn>]
  naval_fate ship shoot <x> <y>
  naval_fate mine (set|remove) <x> <y> [--moored|--drifting]
  naval_fate -h | --help
  naval_fate --version

Options:
  -h --help     Show this screen.
  --version     Show version.
  --speed=<kn>  Speed in knots [default: 10].
  --moored      Moored (anchored) mine.
  --drifting    Drifting mine.

Examples:
  Here's how you'd move the ship `Disney Cruise` to the coordinates `<2, 3>`:

  naval_fate ship "Disney Cruise" move 2 3 --speed=100

  Here's how you'd shoot at the coordinates `<4, 6>`:

  naval_fate ship shoot 4 6

Adding the examples as you did will show up just as you typed them if someone executes:
naval_fate --help

does that break something for you? It works for me just fine. The format itself is irrelevant, I believe.
You could use the tool tldr, where you specify a set of examples and people can just call:
tldr your_program

and the get a nice output. For example, doing so with tar in a Linux terminal:


MaterialApp.router and friends should take a (single) RouterConfig object for ease-of-use

Right now, you have to pass the routerDelegate, routeInformationProvider, routeInformationParser, and backButtonDispatcher separately to MaterialApp.router, which makes for some awkward code for third-party routing packages that want to provide these and creates unnecessary boilerplate:
final MyThirdPartyRouter myThirdPartyRouter = MyThirdPartyRouter(...);
return MaterialApp.router(
  routerDelegate: myThirdPartyRouter.delegate,
  routeInformationProvider: myThirdPartyRouter.informationProvider,
  routeInformationParser: myThirdPartyRouter.infromationParser,
  backButtonDispatcher: myThirdPartyRouter.backButtonDispatcher,
);

To improve on this, we could define a RouterConfig mixin (or interface):
mixin RouterConfig { // or "abstract class"
  RouterDelegate get delegate;
  RouterInformationParser get informationParser;
  RouterInformationProvider get informationProvider;
  RouterBackButtonDispatcher get backButtonDispatcher;
  // TODO: figure out which of these are optional and need to be nullable.
}

Third-party router packages could implement that interface:
class MyThirdPartyRouter with RouterConfig {
 // ...
}

And MaterialApp.router could then take a single RouterConfig object for some much cleaner code:
return MaterialApp.router(
  routerConfig: MyThirdPartyRouter(...);
);

This could be added to MaterialApp.router in a backwards-compatible way by keeping the existing config options and adding the routerConfig argument as an alternative. We'd have to decide whether we want to disallow using the old API when a routerConfig is provided or whether we want to query the routerConfig first and - if it doesn't provide the requested value - fall back to the values from the old API.

/cc @johnpryan @chunhtai What do you think?

I kinda wish we could define a factory constructor on the RouterConfig mixin, so you could also instantiate it directly to create a custom RouterConfig given a delegate, informationParser, etc. while also allowing third-party router packages to mix it into their implementation directly without messing with their inheritance hierarchy (which we'd have to do if RouterConfig were defined as an (abstract) class).
Unfortunately, dart doesn't allow factory constructors for mixins (yet): https://github.com/dart-lang/language/issues/1803

I really like this idea. Would it be feasible to add a RouterConfig parameter to the normal MaterialApp constructor too? Then maybe we could deprecate the .router constructor...

This sounds good to me, I also want to make informationParser optional, I have encounter some use case where they don't care about platform message.

Would it be feasible to add a RouterConfig parameter to the normal MaterialApp constructor too?

We'd have to take a look what parameters on the regular MaterialApp constructor wouldn't make sense to be used in combination with the new routerConfig (e.g. home, initialRoute) and whether it's too confusing that those parameters are mutually exclusive...
(I believe we added the separate .router constructor because the list of possible arguments to MaterialApp was getting to confusing and we wanted to make it clearer what is available when you use the router-based APIs).

This is the list of parameters, that the regular MaterialApp constructor takes, that are unused if you want to use the Router:
navigatorKey
home
routes
initialRoute
onGenerateRoute
onGenerateInitialRoutes
onUnknownRoute
navigatorObservers

Overall, that is a pretty long list and could be confusing (e.g. why can I not use any of these routing related parameters to configure my router when I use the routerConfig parameter?). So, I would be leaning towards keeping the .router constructor as a clean interface showing clearly what functionality of MaterialApp is available when you use a custom Router.
@johnpryan What do you think? Would you still be in favor of deprecating .router altogether?

I also agree with @goderbauer , the error message when people put in the wrong parameters to original constructor is already quite hard to comprehend. It will be even worse if router api is merged into the original one. I sometimes even think we should separate them out even more, but that adds its own burden too.

These are good points, I would probably vote to keep .router constructor too. MaterialApp.router(routeConfig: myRouter) is short enough for me.


Sending to multiple workspaces

Are there some types of data that can be sent to multiple workspaces and some that can't?
This article implies that Windows events can be sent to multiple workspaces if desired. When testing, say, a Web App's metrics settings, however, I don't see any way to add another workspace. There is no option to set it up in other workspaces once it is tied to the first one.

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

ID: c62e3725-b0dc-5ce5-c049-70fd3ae106e3
Version Independent ID: 9c0c5ef7-bd49-cb39-ca10-d98386004975
Content: Manage workspaces in Azure Log Analytics and the OMS portal
Content Source: articles/azure-monitor/platform/manage-access.md
Service: log-analytics
GitHub Login: @MGoedtel
Microsoft Alias: magoedte

@dcbrown16 It doesn't depend on the type of data you send. Instead it depends from where you're sending the data to the work space. What you're noticing is an expected behavior. Sending data to multiple work  spaces is allowed from a few sources such as virtual machines.

@dcbrown16 We will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion and we will reopen the issue.

@SadiqhAhmed-MSFT thanks for your investigation.
How can we determine which resources allow multiple workspace settings and which do not?
Feel free to include me on any internal communications directly at v-dibr. Thanks!


backend-app-api: fix log redaction escaping

Hey, I just made a Pull Request!
Fixes #15803
:heavy_check_mark: Checklist

[x] A changeset describing the change and affected packages. (more info)
[ ] Added or updated documentation
[x] Tests for new functionality and regression tests for bug fixes
[ ] Screenshots attached (for UI changes)
[x] All your commits have a Signed-off-by line in the message. (more info)

Work will be shipped in #15806


ERROR: Version in "./docker-compose.yml" is invalid - it should be a string.

Do you want to request a feature or report a bug?
Bug
Please provide a sample input docker run command
docker run --init --rm -d -e foo=bar container:latest

What is the current output?*
version: 3
services:
    container:
        environment:
            - foo=bar
        image: 'container:latest'

What is the expected/desired output?
version: "3"
services:
    container:
        environment:
            - foo=bar
        image: 'container:latest'

The version should be a string.  docker-compose tells me:
ERROR: Version in "./docker-compose.yml" is invalid - it should be a string.

This, I have a feeling this project is abandoned, but ill see if i can make a PR.

Huh, apparently 3f37b356915137d9803534226cde88fae6396114 should have fixed it but it not fixed on the website.

Apologies, it's taken me a few weekends to get round to giving this project some love. Fixed the package deployment in this repo, we're now on the latest version on the website.
https://composerize.com/

@magicmark had this happen again today

Please correct the below line , it should be :
version: '3'