Token support

FireFly should support the creation and tracking of both fungible and non-fungible tokens. Some of the key concepts that must be supported:

Creating multiple types of tokens
Minting, transferring, and burning tokens of a given type
Tracking transaction history and current account balances (must include operations initiated by FireFly and also those initiated on-chain with no trigger from FireFly)
Attaching data to a token transfer, for correlating off-chain items with the transfer event on-chain

The first connector will be focused on Ethereum tokens support via ERC1155. Source code for the connector is here: https://github.com/hyperledger/firefly-tokens-erc1155
Cross-chain functionality, including atomic swaps and the like, will not be part of this design effort (but will be part of a future item).

This tracking issue is a bit late to the game, but tokens have been discussed in detail on these two community calls:
https://wiki.hyperledger.org/display/FIR/2021-06-30+FireFly+Community+Call
https://wiki.hyperledger.org/display/FIR/2021-09-15+FireFly+Community+Call
Below are a few slides from those discussions that informed the initial design:

PRs merged to date:
#154 Add support for creating token pools
#162 Add "confirm" parameter when creating token pools
#163 Reject token pool events with duplicate info
#165 Rename token fields to match backend changes
#166 Add GET routes for token pools
#167 Handle token_pool_rejected, add new transaction type for token pools
#173 Add unit tests for tokens HTTPS plugin
#176 Align the "additionalInfo" for blockchain and token transactions
#177 Read "operator" field instead of "author" for token-pool event
#178 Add skeleton functionality for token accounts
#179 Supply requestId when creating token pools
#185 Pack all token pool info into "data" field
#193 Small fixes to token accounts
#201 Add additional fields to TokenPool
#202 Rename tokens "https" plugin to "fftokens"
#210 Move TokenPoolCreated handler into AssetManager
#212 Add "created" field to token pools, add some extra E2E checks

Next pending (open) PRs:
#211 Announce token pool info via broadcast
#215 Add database types and route for listing token transfers

As these have shaped up, this is the current surface area of the tokens API (current and planned endpoints):
POST /namespaces/{ns}/tokens/{type}/pools - create pool
GET /namespaces/{ns}/tokens/{type}/pools - list pools
GET /namespaces/{ns}/tokens/{type}/pools/{name} - get pool
GET /namespaces/{ns}/tokens/{type}/pools/{name}/accounts - list known accounts (i.e. that have ever had non-zero balance)
GET /namespaces/{ns}/tokens/{type}/pools/{name}/transfers - list all transfers that have occurred in this pool
POST /namespaces/{ns}/tokens/{type}/pools/{name}/transfers - perform a transfer within this pool
POST /namespaces/{ns}/tokens/{type}/pools/{name}/mint - perform a mint (actually this is identical to a transfer, but without a "from" or "tokenIndex")

The last one is a bit of an open question - I think we'll want a separate /mint API for clarity. Technically a mint is just a special case of transfer, but it feels like they should be separate API operations. Open to input on this point.

the list of endpoints above look good to me.
just want to confirm that we have these following ones in the roadmap as well:

approve: to allow a different account to spend on behalf of the token owner, aka the transaction submitter, this is required for use cases that involve an escrow or custody
transferFrom: works together with approve, for the designated spender to spend out of the approver's account balance. this could be merged under transfers but would require an additional parameter in the transfers calls that are extraneous if the transfers are from the submitter's own balance
burn: this is required for use cases such as token bridges

@jimthematrix I was thinking /transfer should have both from and to parameters, with either defaulting to the author if unset (although it's an error if both are unset).
I also agree we should explicitly have /burn in parallel with /mint (even though it's also just a "special" kind of transfer, I think the dedicated API is good for clarity).
And we do definitely need a way to set approvers. Not sure if that'll be a simple /approve or a whole set of role-management endpoints (one other related operation is setting who can mint in a given pool). Haven't given this a ton of thought yet.

Updated #215 to include the POST routes for /mint and /transfers as discussed above.

Also put up a PR for burn support in the ERC1155 connector: https://github.com/hyperledger/firefly-tokens-erc1155/pull/29
Once that is merged, it will be simple to add support in FireFly.

Burn support is now merged in the connector, so #215 has been updated again to include a /burn route.

Diagram of the new two-step create+announce flow for pool creation, introduced in #211:

And a higher-level look at what the validation flow looks like on the other nodes - placeholder logic for this validation was introduced in #211, but the final implementation is tracked by #222:

Basic/standalone token support is now in mainline with the merge of #215 (and a small follow-on in #239).
Now the piece that ties it all together:
#245 Allow sending a message with a token transfer

Noted another bit of functionality that may be desirable for 1.0:
#326 Allow setting a URI for NFTs


Docs: Missing demo and examples

This project looks great but docs desperately need examples/demo section. I get that you use expressive-code in the docs so it's kinda a demo but I would love to see a dedicated showcase of what's possible.

@hippotastic Yes, the text markers subpage looks great. The only problem is that it's buried in docs and as a user who just learned about your lib, I don't want to scroll through multiple subpages only to see what's possible.
I simply suggest creating a "demo" or "examples" page showcasing the most advanced features.

Gotcha, good idea! This would probably serve as a good introduction page, which I'm currently missing. I'll try to come up with something along these lines.
Thanks for your input!


Update jax-triton metadata to depend on the Triton 3.0.0 release.

This seems to work just fine! And it will make the pip install considerably easier.

Tests pass with the triton 3.0 release in a VM.


[Feature request] Support for "time delta" data column transformation

Is your feature request related to a problem? Please describe.
I usually work with UNIX timestamps (as REALs) inside databases which (in my opinion) are best for storing event occurrences, plus processing is usually faster. This has a plus when finding the difference between two events, because I just simply subtract the two timestamps to get a "delta". I like the UI's ability to transform timestamps from REAL into an effective date+time, but there are no transforms for timestamps. I can transform them into "Epoch time", but the results become less legible if we get a delta >= 32d.
Describe the solution you'd like
Have a data column transformation that converts deltas into legible values, much like Python's timedelta string representation. The string can have any form you like, but the fields ([weeks (?)], days, hours, minutes, seconds [+fracs]) should be clearly legible. For example:

Input
Output

0.0
00:00:00.000000

12345.6789
03:25:45.678900

86400.0
1d 00:00:00.000000

3141592.65359
36d 08:39:52.653590 / 4w 6d 08:39:52.653590

-540366.666666
-6d 06:06:06.666666

(sorry for the ugly styling of the table, Github's markdown doesn't support tables natively, so I had to build it in HTML)
Negative timedeltas should be considered as positive with a minus sign preceded. This differs from Python's perspective, where the result ouputted is:
from datetime import timedelta
str(-timedelta(days=6, hours=6, minutes=6, seconds=6, microseconds=6666666)
# --> '-7 days, 17:53:53.333334'

(note that this "normalized" ouput is internally more efficient for the code, but not very user-friendly)
Ideal settings should be:

Unit (exactly like "Epoch time"): s, ms, us, ns, dotnet, and so on (pick as much as suitable for this format)
Split days into weeks+days: [Y/n]

Describe alternatives you've considered
I can transform the column either in a query or in a view, either using the direct SQL sentences or inside my custom-built applications, but this method would be far more efficient (and useful to everyone) if this transformation is included inside dBeaver.
Additional context
Using following versions:

dBeaver 24.2.4 (build 2024-11-03 18:31) on Ubuntu LTS 22.04
dBeaver 24.2.0 (build 2024-09-01 15:51) on Windows 10

This solution is SQLite based, but it can be extended to any other database type.

Thanks for the idea


Live data preview

It would be nice to add a functionality that shows the Q matrix in real time to see how it updates.

Since the project is no further being developed I think we can safely close this issue.


No spans for SQS calls from aws-sdk v3

What version of OpenTelemetry are you using?
The dependencies I'm using in the package.json file are:
"dependencies": {
  "@aws-sdk/client-sqs": "3.5.0",
  "@opentelemetry/instrumentation": "0.49.1",
  "@opentelemetry/instrumentation-aws-sdk": "0.38.1",
  "@opentelemetry/sdk-trace-node": "1.22.0"
}

What version of Node are you using?
v16.20.2 (also reproducing with v18.19.1)
What did you do?
I ran the following script:
const { SQSClient, ReceiveMessageCommand } = require("@aws-sdk/client-sqs");
const { NodeTracerProvider } = require('@opentelemetry/sdk-trace-node');
const { SimpleSpanProcessor, ConsoleSpanExporter } = require('@opentelemetry/sdk-trace-base');
const { registerInstrumentations } = require('@opentelemetry/instrumentation');
const { AwsInstrumentation } = require('@opentelemetry/instrumentation-aws-sdk');

const tracerProvider = new NodeTracerProvider();
tracerProvider.addSpanProcessor(new SimpleSpanProcessor(new ConsoleSpanExporter()));
tracerProvider.register();

registerInstrumentations({ instrumentations: [new AwsInstrumentation()] });

AWS_REGION = "us-west-2"
QUEUE_URL = "https://sqs.us-west-2.amazonaws.com/xxxxxxxxxxxx/some-queue-name"

const sqsClient = new SQSClient({ region: AWS_REGION });

(async () => {
  await sqsClient.send(new ReceiveMessageCommand({ QueueUrl: QUEUE_URL }));
  tracerProvider.forceFlush()
})()

What did you expect to see?
SQS spans printed to the console
What did you see instead?
Nothing
Additional context
To verify that my setup is producing spans to the console otherwise, I've added the following lines:
const { SQS } = require('aws-sdk');
await new SQS({ region: 'us-west-2' }).sendMessage({
  QueueUrl: 'the queue url used above',
  MessageBody: "Hello from OTEL!"
}).promise();

into the body of the IIFE quoted earlier, and did see spans coming from the aws-sdk v2 instrumentation.

I can confirm that changing the line order to:
registerInstrumentations({ instrumentations: [new AwsInstrumentation()] });
...
const { SQSClient, ReceiveMessageCommand } = require("@aws-sdk/client-sqs");

solves the issue, and spans are produced as expected.


[Bug]: 3.12.11 break secrets

Is there an existing issue for this?

[X] I have searched the existing issues

Example public repository
No response
Description
idk how to reproduce this because it happened on one private repo
but I couldn't load any of the secrets of my application at runtime for my Docker buildpack
rollingback to 3.12.10 fixed the issue

Steps To Reproduce

Create an app
add secrets
try to use secrets at runtime

Version
3.12.11

Same problem in v3.12.12

I also have this problem, I need you to solve it as soon as possible, I have applications in production.

@BassoliCodes if you need to continue using it you can just downgrade to 3.12.10

Awesome it is fixed !

I've made a fix in v3.12.13 that fixes the unintended bug. Please check and let me know!

Thank you, problem is solved!


WETV Error

The error i have is when download Battle Through The Heavens. it is normal whene download season regular but when download special episode the error showing.
This is the error -->
Battle Through The Heavens Special 3: Three Years of Pledge
第 1 季 共有：13 集	下載全集
尋找 Battle.Through.The.Heavens.Special.3.Three.Years.of.Pledge.S01E01.WEB-DL.WeTV.vtt ...
getinfo_callback_941137({"ip":"<IP_ADDRESS>","s":"f","em":80,"exem":30001002,"msg":"您所在的地區因版權原因無法播放，去看看其他影片吧","exinfo":"美国---未知","code":""})
Whenever i download special 1,2,3 it wont downloaded but when ragular season it works
Hope you cant fix it.

Battle.Through.The.Heavens.Special.3.

Hi, please execute the script locally. (Not local, or you have to use NordVPN on the cloud)
Colab environment is in the US. So the show is unavailable.
Battle.Through.The.Heavens.Special.3.Three.Years.of.Pledge.S01.WEB-DL.WeTV.zip


[Azure Stack] Updates to Azs.Storage.Admin spec

Latest improvements:
MSFT employees can try out our new experience at OpenAPI Hub  - one location for using our validation tools and finding your workflow.

Contribution checklist:

[ ] I have reviewed the documentation for the workflow.
[ ] Validation tools were run on swagger spec(s) and have all been fixed in this PR.
[ ] The OpenAPI Hub was used for checking validation status and next steps.

ARM API Review Checklist

[ ] Service team MUST add the "WaitForARMFeedback" label if the management plane API changes fall into one of the below categories.
adding/removing APIs.
adding/removing properties.
adding/removing API-version.
adding a new service in Azure.

Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs.

[ ] If you are blocked on ARM review and want to get the PR merged urgently, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.
Please follow the link to find more details on API review process.

/azp run automation - sdk

Can one of the admins verify this patch?

Can one of the admins verify this patch?

@allenjzhang Could you please take a look at this PR and let me know your feedback?

@allenjzhang Could you please take a look at this PR and let me know your feedback?

/azp run

/azp run

@bganapa, doesn't look like x-ms-parameter-location change is needed. Can you remove it. Other things looks fine. There is an issue with GitHub showing checks pending. But accurate results are shown under Checks tab. It is showing breaking changes due to remove of the ReadOnly flag. It is fine as this is preview version.
Can you remove the x-ms-parameter-location change and I can help merge the PR? Thanks!

/azp run automation - sdk

@allenjzhang I removed x-ms-parameter-location. Thank you. Please merge if it looks good.


Implement Demo Feedback from [ENG-111]

Implemented the Feedback to the demo.
Added a section on semantic tags to the section

Other changes

Depricated the requirements.txt to a working version pre the change to the lakefs_sdk. I opened an issue to migrate the demo: https://github.com/appliedAI-Initiative/lakefs-spec/issues/116. I consider it out of scope for this PR.

Note

If you test the demo, change the curl command !curl -o .lakectl.yaml "https://raw.githubusercontent.com/appliedAI-Initiative/lakefs-spec/main/demos/.lakectl.yaml" to !curl -o .lakectl.yaml "https://raw.githubusercontent.com/appliedAI-Initiative/lakefs-spec/demo/demos/.lakectl.yaml". It then references the  .lakectl.yaml  on this branch as opposed to main until this PR is merged.

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Comparison is base (ce1b44c) 87.15% compared to head (c59ac46) 87.15%.

:exclamation: Current head c59ac46 differs from pull request most recent head 71d6a7b. Consider uploading reports for the commit 71d6a7b to get more accurate results

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@           Coverage Diff           @@
##             main     #117   +/-   ##
=======================================
  Coverage   87.15%   87.15%
=======================================
  Files           7        7
  Lines         467      467
  Branches       62       62
=======================================
  Hits          407      407
  Misses         35       35
  Partials       25       25

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

Changes approved by Maciej.


MockFileSystem extensions

Would you find the below extension methods useful? If so, I am happy to open a pull request. I'm hesitant to do so right away because I'm not sure if these should be extension methods in this library or if I should contribute them as actual class members upstream (upstream being the actual IO.Abstractions package).
I found these extension methods to be absolutely invaluable in my own code base in conjunction with the Extensions package. It eliminates a lot of boilerplate in my unit tests, namely these:
var fs = new MockFileSystem();
var myDir = fs.CurrentDirectory().Directory("dir");
var myFile = fs.CurrentDirectory().File("file.txt");

// Creating empty files
fs.AddFile(myFile.FullName, new MockFileData(""));
// Becomes
fs.AddEmptyFile(foo);

// Specifying `FullName` all over the place...
fs.AddDirectory(myDir.FullName);
// Becomes
fs.AddDirectory(myDir);

If you could provide some guidance and feedback, I'm happy to move this to a PR. Thanks for your time!
public static class MockFileSystemExtensions
{
    public static void AddEmptyFile(this MockFileSystem fs, string path)
    {
        fs.AddFile(path, new MockFileData(""));
    }

    public static void AddEmptyFile(this MockFileSystem fs, IFileInfo path)
    {
        fs.AddEmptyFile(path.FullName);
    }

    public static void AddDirectory(this MockFileSystem fs, IDirectoryInfo path)
    {
        fs.AddDirectory(path.FullName);
    }

    public static void AddFile(this MockFileSystem fs, IFileInfo path, MockFileData data)
    {
        fs.AddFile(path.FullName, data);
    }
}

hi @rcdailey ,
The above looks usefull to me.
In my opinion, they should be part of the base package but I know @fgreinacher is not really into it.
@fgreinacher can you please review the above and see if it makes sense to add them to the TestableIO.System.IO.Abstractions.TestingHelpers library.
If not the only alternative is to create a second library in this repo, something like TestableIO.System.IO.Abstractions.TestingHelpers.Extensions, otherwise the normal extensions would depend on the testing library which doesn't make any sense.


when processing, vim does not stay in visual mode (and etc).

After each sentence is processed, Coqtail does something that

makes vim/neovim exit the visual mode
closes git-messenger.vim's floating window in neovim
breaks vim-sneak and neovim's ui with some non-sense error messages like this

I'm not 100% sure but my guess is this is at least partially because coqtail#panels#refresh briefly jumps to the goal and info buffers to update them. If that's the case then maybe using things like appendbufline and the window option for matchaddpos could solve this at least for versions of Vim/NeoVim that support them.

I think you're right. All of the above work correctly if I remove the body of coqtail#panels#refresh.

This line should be wrapped with win_execute because winsaveview and winrestview don't support "window" option.
https://github.com/whonore/Coqtail/blob/3b61d0755a4523a131096c97fb016b102e7b1672/autoload/coqtail/panels.vim#L286
But win_execute is also quite recent and has not been ported to neovim yet (https://github.com/neovim/neovim/pull/13664).
Here's my fix that at least works for vim with win_execute: https://github.com/tomtomjhj/Coqtail/commit/8a646c705120e8dc2c042a609d451703090d6c8b.

win_execute does seem to be the best solution, it's just too bad it's only available in Vim 8.1 and 8.2. Does your deletebufline in #198 still break vim-sneak since it changes windows?

#198 does not fix vim-sneak and git-messenger. I kept that PR small because it fixes the most common scenario with minimal changes. I will open a PR with the full fix using win_execute + compatibility checking stuff later (when win_execute is ported to neovim or someone else complains about this bug).
BTW earlier versions of win_execute() seem to have some critical bugs, so I think we should require at least 8.2.0137 if we want to use it.


Fixed confusing part in readme.md

Changing 1 section of code to make it easier for users to follow. took me 15 mins to figure out i needed to run something else

Thanks for your contribution!


Can't edit local kubernetes cluster automatically imported

What kind of request is this (question/bug/enhancement/feature request):
bug
Steps to reproduce (least amount of steps as possible):
Deploy RKE cluster, deploy rancher within the cluster and try to edit the cluster from rancher web interface.
Result:

Other details that may be helpful:
Environment information

Rancher version (rancher/rancher/rancher/server image tag or shown bottom left in the UI): v2.5.2
Installation option (single install/HA): HA

Cluster information

Cluster type (Hosted/Infrastructure Provider/Custom/Imported): Imported RKE
Machine type (cloud/VM/metal) and specifications (CPU/memory): metal, 24 cores and 256GB RAM
Kubernetes version (use kubectl version): v1.18.10 (I tested with v1.19, same result)

Client Version: version.Info{Major:"1", Minor:"18", GitVersion:"v1.18.5", GitCommit:"e6503f8d8f769ace2f338794c914a96fc335df0f", GitTreeState:"clean", BuildDate:"2020-06-26T03:47:41Z", GoVersion:"go1.13.9", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"18", GitVersion:"v1.18.10", GitCommit:"62876fc6d93e891aa7fbe19771e6a6c03773b0f7", GitTreeState:"clean", BuildDate:"2020-10-15T01:43:56Z", GoVersion:"go1.13.15", Compiler:"gc", Platform:"linux/amd64"}

Docker version (use docker version):

Client: Docker Engine - Community
 Version:           19.03.13
 API version:       1.40
 Go version:        go1.13.15
 Git commit:        4484c46d9d
 Built:             Wed Sep 16 17:02:52 2020
 OS/Arch:           linux/amd64
 Experimental:      false

Server: Docker Engine - Community
 Engine:
  Version:          19.03.13
  API version:      1.40 (minimum version 1.12)
  Go version:       go1.13.15
  Git commit:       4484c46d9d
  Built:            Wed Sep 16 17:01:20 2020
  OS/Arch:          linux/amd64
  Experimental:     false
 containerd:
  Version:          1.3.7
  GitCommit:        8fba4e9a7d01810a393d5d25a3621dc101981175
 runc:
  Version:          1.0.0-rc10
  GitCommit:        dc9208a3303feef5b3839f4323d9beb36df0a9dd
 docker-init:
  Version:          0.18.0
  GitCommit:        fec3683

This is covered in https://github.com/rancher/rancher/issues/22763


Additional mode for loading of segmentation data in tf.keras.preprocessing.image.ImageDataGenerator.flow_from_dataframe()

System information

TensorFlow version (you are using): 2.1.0
Are you willing to contribute it (Yes/No): Yes

Describe the feature and the current behavior/state.
As of now, one has to come around with a workaround to load segmentation data in tf.keras.preprocessing.image.ImageDataGenerator to load images and segmentation masks in a generator. A current workaround could look like:
datagen = tf.keras.preprocessing.image.ImageDataGenerator()

df = pd.DataFrame({'images': images,
                   'masks': masks})
# seed, so that image_generator and mask_generator will rotate and shuffle equivalently
seed = 42
image_generator = datagen.flow_from_dataframe(df,
                                      directory='.',
                                      x_col='images',
                                      y_col='masks',
                                      batch_size=1,
                                      class_mode=None,
                                      seed=seed)
mask_generator = datagen.flow_from_dataframe(df,
                                     directory='.',
                                     x_col='masks',
                                     y_col='images', # Or whatever
                                     batch_size=1,
                                     class_mode=None,
                                     seed=seed)

train_generator = zip(image_generator, mask_generator)

# same for validation data generator

model.fit(x=train_generator, epochs=EPOCHS,
                validation_data=validation_generator, use_multiprocessing=False)

It would be much cleaner, if there would be an option for class_mode (e.g. class_mode='mask') that allows you to load the files specified by the paths in y_col as images.
Will this change the current api? How?
An additional option for the argument class_mode will be added.
Who will benefit with this feature?
Everyone who looks for a simple way to load images and corresponding segmentation data.
Any Other info.

Okay, I tried to solve it on my own. However, there is still a dependency on keras-preprocessing that makes things a bit difficult. Are there any plans to integrate keras-preprocessing into TensorFlow?

Hi @RobinBaumann, do you have a more complete colab example or the stack trace so we know what is the dependency issue? We do have an equivalent dataset_from_directory but not ingesting dataframe for now.

In tensorflow/python/keras/preprocessing/image.py you can find an import statement to:
from keras_preprocessing import image

Which is later used in:
class ImageDataGenerator(image.ImageDataGenerator):
    ....

So all calls to the generator are handled by keras_preprocessing.image.ImageDataGenerator instead of tf.keras.preprocessing.image.ImageDataGenerator.  This is not an error, I just think that it would be cleaner to integrate all functionality keras_preprocessing into tf.keras, especially since Keras is already integrated in TF2 and will no longer be maintained standalone.

In tensorflow/python/keras/preprocessing/image.py you can find an import statement to:
from keras_preprocessing import image

Which is later used in:
class ImageDataGenerator(image.ImageDataGenerator):
    ....

So all calls to the generator are handled by keras_preprocessing.image.ImageDataGenerator instead of tf.keras.preprocessing.image.ImageDataGenerator, beause the latter doesn't provide implementations of flow_from_dataframe, flow_from_directory etc. This is not an error, I just think that it would be cleaner to integrate all functionality keras_preprocessing into tf.keras, especially since Keras is already integrated in TF2 and will no longer be maintained standalone.

OIC. Yeah what we currently have is dataset_from_directory, which is the equivalent of flow_from_directory, as experimental, we don't have a dataset_from_dataframe yet

OIC. Yeah what we currently have is dataset_from_directory, which is the equivalent of flow_from_directory, as experimental, we don't have a dataset_from_dataframe yet

Ah okay,  is currently anybody working on the dataset_from_dataframe or can this be considered a good first issue for me? :)

OIC. Yeah what we currently have is dataset_from_directory, which is the equivalent of flow_from_directory, as experimental, we don't have a dataset_from_dataframe yet

Ah okay, is currently anybody working on the dataset_from_dataframe or can this be considered a good first issue for me? :)

No one is working on that currently, you're welcome for contribution :-)

@RobinBaumann We're planning to get rid of keras-preprocessing dependency as well. If you want to contribute, that'd be great as well :-)

@RobinBaumann On another note, I would think it's probably not the best place to do the shuffle and rotate here. IMHO, it's better to separate the logic of 'load things from files' from 'preprocess those things', i.e.,:
step 1: load the image:
img = dataset_from_dataframe(...)
seg = dataset_from_dataframe(...)
step 2: preprocess it.
def map_fn(x):
return tf.image.rotate(x, seed)  # Or something like that, we launched Keras Image Preprocessing layers.
preproc_img = img.shuffle(your_seed).map(map_fn)
preproc_seg = seg.shuffle(your_seed).map(map_fn)

@RobinBaumann We're planning to get rid of keras-preprocessing dependency as well. If you want to contribute, that'd be great as well :-)

Sounds good 👍 I'm having a look into it this weekend and will come back to you, if i have some questions, if that's okay?

@RobinBaumann We're planning to get rid of keras-preprocessing dependency as well. If you want to contribute, that'd be great as well :-)

Sounds good 👍 I'm having a look into it this weekend and will come back to you, if i have some questions, if that's okay?

Of course!

I'm gonna close this for now, since we all agreed we should implement the dataset way. Please file a PR once it's ready. Thanks!


scaffolder/next: Allow running async validators onBlur of field extensions

Not sure if this is possible, would like some exploration. But would be good if the async validators could be run onBlur for that form element individually.
I think that there is onBlur that gets given to the FieldExtension, so it should be possible to call onBlur selectively, and listen to that handler somehow to run the validator for that element.
I think that coupled with the liveValidate prop could yield a good experience.

Gonna close this as it doesn't look like it's that interesting for users. Feel free to comment if it's something you'd like to see.


Add Sonobuoy blogs from CNABU blog that never got put on sonobuoy.io

Some blog posts were put here https://blogs.vmware.com/cloudnative/?category_name=&s=sonobuoy before we had our own sonobuoy.io to publish blog posts on.
I'd like to move those blogs into our site for completeness; there is some good content that users wont currently find on our site.

To make sure that we don't mess up SEO, what we can do is to have a short blurb about each one and point to the full blog over on the VMware blog. Does that work? If so, I can get on it.

Yea that works for me. I know I've tried to link people to our blogs for xyz a few times only to realize it was on the other site. Having them discoverable via sonobuoy.io would be sufficient for me.

I'll add links here to the ones that I see need references

https://blogs.vmware.com/cloudnative/2019/02/21/certifying-kubernetes-with-sonobuoy/
https://blogs.vmware.com/cloudnative/2019/04/30/sonobuoy-plugins-custom-testing/
https://blogs.vmware.com/cloudnative/2019/04/02/testing-air-gapped-kubernetes-sonobuoy-0-14/
Also, I noticed on the blogs and on https://blogs.vmware.com/cloudnative/author/jschnake/ I dont have an image up. Can we fix that too?

Also, I noticed on the blogs and on https://blogs.vmware.com/cloudnative/author/jschnake/ I dont have an image up. Can we fix that too?

I can show you offline how to do that.
For the blog posts, I'll get those blurbs started. I'll set the to be backdated to the same dates as the original blog posts.

https://blogs.vmware.com/cloudnative/2019/02/21/certifying-kubernetes-with-sonobuoy/
was already published as
https://sonobuoy.io/certifying-kubernetes-with-sonobuoy/


Stuck while starting AEM (Step 4)

Stuck with the AEM startup output
Loading quickstart properties: default
Loading quickstart properties: instance
Low-memory action set to fork
Using 64bit VM settings, min.heap=1024MB, min permgen=256MB, default fork arguments=[-Xmx1024m, -XX:MaxPermSize=256m]
The JVM reports a heap size of 7851 MB, meets our expectation of 1024 MB +/- 20
No console, will fork to get enough memory
Not forking JVM as -nofork option is set
Setting properties from filename '/opt/aem/AEM_6.x_Quickstart.jar'
Setting 'sling.run.modes' to 'publish,nosamplecontent,local' from command line.
Unable to setup Swing UI, will use system console only (java.awt.HeadlessException)
Verbose option not active, closing stdin and redirecting stdout and stderr
Redirecting stdout to /opt/aem/crx-quickstart/logs/stdout.log
Redirecting stderr to /opt/aem/crx-quickstart/logs/stderr.log
Press CTRL-C to shutdown the Quickstart server...
@remcorakers  @sveneh  - Can you help. Have you come across this before?

@harshkotak This error doesn't sound familiar to me. What version of AEM are you using? Is there any info available in the logs of the author, dispatcher or publisher?


Could you give me the ToolBench key quickly?

I filled out the form for the ToolBench key last Friday (2023-08-11).
But I haven't received the key up to now (2023-08-14).
Could please you give me the ToolBench key quickly?
Thanks!

We'll provide it today. Thanks for your patience.

您好 ， 我也填写了表单，daigl@。。。，还请尽快通过多谢！

您好 ， 我也填写了表单，还请尽快通过多谢！

<EMAIL_ADDRESS>


A new release?

Are there plans to do a release anytime soon? I'm pretty excited about the github suggestions feature that is in master, but alas it is not available in the latest version of the gem (v0.10.0).

👍

I'm not sure who has the permission to actually release it. @doomspork?

Suggestion feature rocks! Please release ;-)

Like I said above, I was only recently invited to this org. I think that only @mmozuras (and possibly @doomspork) can do the release to RubyGems.

The work done in 2c16f3f58253e7ac969ec7c46f73f10dd5babbf2 would be great as well so we can update to the latest versions of rubocop. Thanks!

Hound CI now support the 1.x rubocop family, so a new release would be very welcome. @doomspork or @mmozuras can you oblige? A sign that 2021 may be a better year....

Hound CI now support the 1.x rubocop family, so a new release would be very welcome. @doomspork or @mmozuras can you oblige? A sign that 2021 may be a better year....

I've been granted permissions to publish to RubyGems by @doomspork, will try to release by this weekend.

I've been granted permissions to publish to RubyGems by @doomspork, will try to release by this weekend.

Hi @ashkulz, could we get a release? Thank you for working on this gem!

Hi @ashkulz, could we get a release? Thank you for working on this gem!

Unfortunately, I wasn't able to get RuboCop 1.0 working -- there were some test failures. Would gladly accept PRs to fix the same, alternatively will try to work on it in a week or so.

Unfortunately, I wasn't able to get RuboCop 1.0 working -- there were some test failures. Would gladly accept PRs to fix the same, alternatively will try to work on it in a week or so.


[BUG] Fixing the about us and other button in navigation bar

Can i fix  About us and Support Community button that are dissorted  making it difficult for users to visually distinguish between them.
please assign me this task under Hacktober and GSSoC
thankyou!

I have seen many navbar issues, and i have mentioned it before for contributors to not create issues regarding navbar and there should be no more navbar issues, so i have closed this issue, if you have any queries, you can join discord server for further updates and communication.
we are not looking for navbar updates for now, as it was done and changes many times before, please understand.
and there was an updation also, so please understand.


Ros2 enhancement add imu output

protocol adapted to firmware 5.2
fixed bug that prevented the reading of data from the serial
added reading of imu data
added program to enumerate vescs based on their uuid
added possibility to command more vesc through canForward

@anscipione Thank you very much for the PR! However, this is a very extensive overhaul of the code (almost 2,000 lines of changes) which is a bit hard to review all-at-once. Would you mind splitting this into two PRs? Even if one depends on the other, it will be much easier to review them separately.

ok I will try to divide the changes by arguments.

bug fixing of serial comunication.
protocol adapted to firmware 5.2 (this is the change that requires the biggest changes to the code I think )
added reading of imu data
added possibility to command more vesc through canForward
added program to enumerate vescs based on their uuid

can this division fit for you?
unfortunately they are all dependent on each other so I will have to proceed in order.

Yes, that should work fine. I'll do my best to respond to the PRs quickly.


Feature request - control refresh interval

It would be great if you add one more feature to your plugin: ability to externally control refresh interval in the Kibana.
We use Kibana 6.3.2 ;-)
Thank you in advance.

Done, unfortunately the new feature is only in kibana 6.4.2 and above


Does your engine also support radio-buttons ?

In your example exam (Azure-70-532-Practice-Test) a lot of questions should have only 1 answer, but still check-boxes are displayed instead of radio-buttons. Is this intentional or does the engine not support radio-buttons?

This is something that surely needs to be fixed. Thanks for bringing it up. 👍

This has been implemented so questions with multiple correct answers will get radio buttons, and questions with only a single correct answer will get checkboxes.

Very cool ! Thanks.


Codesandbox demos are not working

https://codesandbox.io/s/github/hshoff/vx/tree/master/packages/vx-demo/src/sandboxes/vx-zoom-i
https://codesandbox.io/s/github/hshoff/vx/tree/master/packages/vx-demo/src/sandboxes/vx-linktypes

@TheBrainTeam They are working for me...

I had an issue with Codesandbox a little over a week ago when they changed how they handled modules, but it has been fixed.  Maybe another hiccup?

Also working for me. Without further details it's hard to assist here.


feat: add dependabot support

Signed-off-by: Luca Georges Francois<EMAIL_ADDRESS>📝 Summary
This PR enables dependabot to check new version of dependencies on a daily basis.
@metachris is set as the default reviewer for potential PRs by dependabot.
⛱ Motivation and Context
To avoid having to manually check for new versions of the project's dependencies.
📚 References
Dependabot configuration available here.

✅ I have run these commands

[ ] make lint
[ ] make test-race
[ ] make run-mergemock-integration
[ ] go mod tidy

nice, thanks


Release 1.0.0

This'll be the adoption of Semantic Versioning and a major/breaking release.  Let's use this ticket to determine which breaking changes we want to wrap into 1.0.0 and coordinate on how to release it.
Known tickets requiring a major/breaking semver release:

[ ] #685:  Require Django>=1.8

I think we should also drop support for Python 3.3 in 1.0.0, since it has reached EOL: https://docs.python.org/devguide/index.html#index-6
The Django versions we support that support Python 3.3 also support newer versions of Python that aren't EOL'd.

I think we should also drop support for Python 3.3 in 1.0.0, since it has reached EOL: https://docs.python.org/devguide/index.html#index-6

agreed

Now that https://github.com/django-import-export/django-import-export/tree/0.6.1 has been tagged and released, should we go ahead with the plan to make 1.0.0 the next release?  I just branched and created https://github.com/django-import-export/django-import-export/tree/0.6.x we can use if there are any big bug fixes we need to do before 1.0.0 is released.  So I think we can go ahead with #685 and such, how does that sound @bmihelac?

I would really like to merge this before moving forward:
https://github.com/django-import-export/django-import-export/pull/690/commits/77323e744c50cb2aa0210d853b8f6b5d323ad674
This patch looks fine by me, but would extra eyes :)

Ahh, OK!  I just removed the 0.6.x branch, and we can redo that after #690 gets merged in and 0.6.2 gets released.

Hi! What about moving all settings to dictionary?
IMPORT_EXPORT_SETTINGS = {
    IMPORT_EXPORT_USE_TRANSACTIONS: True
    ...
}

Best doing this before 1.0.0 :)

@manelclos we have only 3 settings right (https://django-import-export.readthedocs.io/en/latest/installation.html#settings)? Personally I would prefer not to complicate about that....

Ok, it was just a suggestion, as some people in PRs want to add options here and there. It would also mean maintaining both for some time...

Hey all! Is there anything that should be done before 1.0.0 release?

I use this project on several production systems. It is actively maintained. Supports latest Django versions. Has a good test coverage. Time to have a 1.0 release :)

What are the priorities from now on?

There are lot of pull requests that could be incorporated (I think) and I waited until 1.0 release.
Currently I use zest.releaser to release new versions - it work great, but I would like to autmate updating changelog.  Creating release description if possible would be awesome. Something like this.
Also what are best practices to allow team to upload new releases to pypi?


Serialize a struct with variable sized sequence

Hello, I read the getting help page which suggested some other mediums, but ended up posting an issue here as the issue seems fairly in depth to serde.
Suppose I have some struct I want to serialize (I'm interested in json but I believe that is irrelevant to the question):
struct Person {
    name: String,
    age: u8,
};

struct Event {
    title: String,
    location: String,
    attendees: Vec<Person>,
}

This is a basic type so I could just slap #[derive(Serialize)] on the types and be done with it. However, this approach requires that I have all of the Person objects collected in a Vec. I'm interested in an approach where I could stream the contents of the attendees field. Perhaps attendees is a very large list that I need to collect from scanning a database or something like that, and that I want to pass the Serializer to my scan function to serialize items as I go (as opposed to collecting a very large list and handling at the end).
I know that I can serialize sequences in isolation with serialize_seq(). However, I don't think I have the option to do that for the field of a struct per the docs for SerializeStruct:
https://docs.rs/serde/latest/serde/ser/trait.SerializeStruct.html
So, two questions:

Am I correct that what I'm asking to do is not possible?
Could SerializeStruct hypothetically be extended to allow a field to be a sequence that is built up element by element (ie same as serialize_seq()) as opposed to needing the field to be an already collected container?

Use a supplier struct instead of Vec<Person> and stream data as you want:
struct Supplier(/*connect to DB*/);
impl Serialize for Supplier {
    fn serialize<S>(&self, serializer: S) -> Result<S::Ok, S::Error>
    where
        S: Serializer,
    {
        let mut seq = serializer.serialize_seq(None)?;
        for element in self.stream_data_from_db() {
            seq.serialize_element(element)?;
        }
        seq.end()
    }
}
struct Event {
    title: String,
    location: String,
    attendees: Supplier,
}

Use a supplier struct instead of Vec<Person> and stream data as you want:
struct Supplier(/*connect to DB*/);
impl Serialize for Supplier {
    fn serialize<S>(&self, serializer: S) -> Result<S::Ok, S::Error>
    where
        S: Serializer,
    {
        let mut seq = serializer.serialize_seq(None)?;
        for element in self.stream_data_from_db() {
            seq.serialize_element(element)?;
        }
        seq.end()
    }
}
struct Event {
    title: String,
    location: String,
    attendees: Supplier,
}

Thank you @Mingun! It seems so obvious seeing it written out, but I couldn't think of this earlier and this looks to accomplish exactly what I want. I prototyped this out for my actual use-case and I see no problems, so going to close this issue out. Thanks again!


Remove Operator links from doc index

Need to sync index page with master to remove the links to Operator documentation. It's not reasonable to manually keep dev and stable versions tracked in the index page for docs.

Thanks @oraNod


[Android] View inside Marker with 0.13.1

Hi, first of all thanks for your hard work.
I'm using react-native 0.42.3, and after upgrading to react-native-maps 0.13.1, i'm getting the following error.
com.facebook.react.views.text.ReactTextView cannot be cast to android.view.viewGroup

addFeature
AirMapView.java  427

addFeature
AirMapView.java  429

addView
AirMapManager.java  266

I think the problem comes from this custom component i'm using
import React, {Component} from 'react';
import {View, Text} from 'react-native';
import MapView from 'react-native-maps';

export default class MarkerCluster extends Component{

	constructor(props) {
		super(props);
		this.state = {...props};
	}

	shouldComponentUpdate(nextProps, nextState) {
		return nextProps.coordinate.latitude != this.state.coordinate.latitude && nextProps.coordinate.longitude != this.state.coordinate.longitude;
	}

	render() {
		return (<MapView.Marker {...this.props}>
			<View style={{borderWidth:3, borderColor: 'white', backgroundColor: 'black', borderRadius: 15, width:30, height:30, justifyContent: 'center', alignItems:'center'}}>
				<Text style={{color:'white', textAlign: 'center'}}>{this.props.clusterLength}</Text>
			</View>
		</MapView.Marker>);
	}
}

If i downgrade to react native maps 0.13.0, the code works as expected.
Hope this helps to solve the issue,
Thanks!

@eard7 can you try adding collapsible={false} to the View inside your marker and see if that changes anything?

@lelandrichardson I can confirm .. this happens only on Android.
Dependencies:
react: 16.0.0-alpha.6
react-native: 0.43.3
react-native-maps: ^0.14.0

I'm having exactly the same issue just adding a TouchableOpacity with a text inside whereas in iOS is working perfectly.
... const myIcon = (<Icon name="rocket" size={30} color="#900" />) .... <TouchableOpacity style={[styles.bubble, styles.button]}>   {myIcon} </TouchableOpacity>

I'm also having this issue but it happens infrequently. I can't nail down why this error is triggering.
<MapView.Marker
  ref={ref => { this.markers[id] = ref; }}
  key={`${id}`}
  identifier={`${id}`}
  title={title}
  description={description}
  coordinate={address.coordinates}
  onPress={() => this.showCallout(`${id}`)}
  onCalloutPress={() => this.onCalloutPress(id)} >
  <View style={styles.marker}>
    <Text
      style={styles.deliveryID}
      allowFontScaling={false}>
      {order}
    </Text>
  </View>
</MapView.Marker>

Happening here too, in RN 0.44 with react-native-maps 15.0 - adding collapsible={false} as suggested by @lelandrichardson doesn't fix it.

Having the same issue, collapsible doesnt help

Same issue here with 0.46, using Expo v19.
On iphone it works just fine, on Android happens every single time, removing touchable opacity from the Marker and adding collapsible={true} had no effect:
        <MapView.Marker
          key={marker.key}
          coordinate={marker.coordinates}
          title={marker.title}
          description={marker.description}
          image={marker.image}
        >
          <MapView.Callout>
            <View>
              <Text>{marker.title}</Text>
              <Button light block
                onPress={() => navigate('PlaceDetailScreen', { id: marker.key, title: marker.title })}
              >
                <Text>Detalhes</Text>
              </Button>
            </View>
          </MapView.Callout>
        </MapView.Marker>

Hey guys,
I was experiencing this problem as well.
My setup was like this:
<MapView>
<Icon onPress={()=>this.doSomething()}>
</MapView>
when I removed the Icon from the MapView component it worked on android.
It works on iOS with the Icon in MapView.

This issue is still present in RN 0.46.4 & react-native-maps v16.2.
Any update on workarounds or how to fix it?

Seeing the same issue RN 0.46.2 &<EMAIL_ADDRESS>

<EMAIL_ADDRESS>&<EMAIL_ADDRESS>same issue caused by using TouchableOpacity inside of MapView.

have the same problem. some TouchableOpacity inside of MapView causes this problem but  some not.

Also having this problem.  Any solution?

My solution is:

Note isAndroid variable

Please, review this commit: https://github.com/react-community/react-native-maps/commit/6220583a19cf62f942b4166927aafeeeb1003a81
The original problem was not reproduced, but the following problems with Text and TextEdit within MapView for Android are fixed there.
As soon as it passes through QA (you are the QA) we will merge it to master and release it on the next iteration.

Awesome! Thanks for fixing it @alvelig :)

@pquattro did the ReactImageView ever get resolved?  I'm having the same problem.  This is a production show-stopper.

same thing with TouchableOpacity on RN 55 and maps ^0.17.1

this is still an issue why is this closed?


Empty Website URL Remain Unchecked

I wrongly pressed Enter when asked for website URL, and the generator crashed. Would it be like asking for GitHub usernames, which warns user of the empty value?
? What is the URL of your website?

/usr/local/lib/node_modules/yo/node_modules/rx/dist/rx.js:77
    throw e;
    ^

Error: Invalid URL
    at module.exports (/usr/local/lib/node_modules/generator-electron/node_modules/normalize-url/index.js:56:9)
    at Object.prompt.filter (/usr/local/lib/node_modules/generator-electron/app/index.js:34:12)
    at /usr/local/lib/node_modules/yo/node_modules/yeoman-environment/node_modules/run-async/index.js:26:25
    at /usr/local/lib/node_modules/yo/node_modules/yeoman-environment/node_modules/run-async/index.js:25:19
    at /usr/local/lib/node_modules/yo/node_modules/yeoman-environment/node_modules/inquirer/lib/prompts/base.js:88:12
    at tryCatcher (/usr/local/lib/node_modules/yo/node_modules/rx/dist/rx.js:63:31)
    at InnerObserver.Rx.FlatMapObservable.InnerObserver.next (/usr/local/lib/node_modules/yo/node_modules/rx/dist/rx.js:2140:43)
    at InnerObserver.Rx.internals.AbstractObserver.AbstractObserver.onNext (/usr/local/lib/node_modules/yo/node_modules/rx/dist/rx.js:1762:31)
    at InnerObserver.tryCatcher (/usr/local/lib/node_modules/yo/node_modules/rx/dist/rx.js:63:31)
    at AutoDetachObserverPrototype.next (/usr/local/lib/node_modules/yo/node_modules/rx/dist/rx.js:5883:51)

It used to work, but Inquirer (the prompt module) annoyingly decided to change the order of the validate and filter steps...

Can't reproduce this anymore. Must have been fixed in Inquirer.js.


React router dom: "Browser history needs a DOM", in production.

i tried react-router-dom in my rouges app, react-router work in development but i get an error in production.
{   "status": 500,   "message": "Browser history needs a DOM",   "name": "Invariant Violation" }

sorry going to deploy an app soon to look into this
can you also post snippets below of your Rogue setup just in case its specific to that

App.jsx
import React, { Component } from 'react'
import { hot } from 'react-hot-loader';
import { Helmet } from 'react-helmet'
import { compose } from 'recompose'
import withStyles from '@roguejs/hocs/emotion'
import { BrowserRouter as Router, Switch, Route, Link } from "react-router-dom";
import { css } from 'emotion'
import '../stylesheets/styles.css'

const Home = () =>
Home

const About = ({match}) =>
About { match.params.id }

const Topics = () =>
Topics

const NotFound = () =>
NotFound

class App extends Component {
	render() {
		return (

      <Helmet>
        <title>test</title>
      </Helmet>
			<Router>

              <Link to="/">Home</Link>

              <Link to="/about">About</Link>

              <Link to="/topics">Topics</Link>

              <Link to="/topicsdd">Topicsdd</Link>

          <Switch>
            <Route exact path="/" component={Home} />
            <Route path="/about/:id" component={About} />
            <Route path="/topics" component={Topics} />
            <Route component={NotFound} />
          </Switch>

      </Router>

		)
	}
}

export default compose(
  withStyles(),
  hot(module)
)(App)

client.js
import { hydrate } from '@roguejs/app'
import App from './containers/App'

hydrate(App)

index.js
import server from './server'

const PORT = process.env.PORT || 3000

server.listen(PORT, error => {
  if (error) console.log(error)

  require('child_process').exec(`${
    process.platform == 'darwin' ? 'open' : process.platform == 'win32' ? 'start' : 'xdg-open'
  } http://localhost:${PORT}`)

  console.log('🚀 started')
})

server.js
import Rogue from '@roguejs/app/server'
import express from 'express'
import App from './containers/App'

const publicDir = process.env.RAZZLE_PUBLIC_DIR
const js = require(process.env.RAZZLE_ASSETS_MANIFEST).client.js
const css = require(process.env.RAZZLE_ASSETS_MANIFEST).client.css

const app = express()
const rogue = new Rogue(App, {
  headTags: [`<link rel="stylesheets" href="${css}"/>`],
  bodyTags: [`<script src=${js} defer></script>`]
})

app.use(express.static(publicDir))
app.use(rogue.render)

export default app

You shouldn't need to wrap your app in a BrowserRouter/Router. Rogue does this for you, in client it does BrowserRouter and in server it does StaticRouter. But gonna try to deploy an app now in case its not that

yea, i was able to deploy an app with zeit's now with a similar setup as above, so that's defintely the issue
closing this, and sorry for delay there!


Heroku-specific error

Everything appears to be set up to the point of having the repo on Heroku, but when I run bundle exec ebooks start on Heroku (through Heroku CLI, heroku run bash), I get the following output:
~ $ bundle exec ebooks start
fatal: Not a git repository (or any parent up to mount point /app)
Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set).
@fontiagoebooks: User information updated
/app/lib/twitter_ebooks/model.rb:49:in `load': dump format error(0x2) (ArgumentError)
	from /app/lib/twitter_ebooks/model.rb:49:in `block in load'
	from /app/lib/twitter_ebooks/model.rb:48:in `instance_eval'
	from /app/lib/twitter_ebooks/model.rb:48:in `load'
	from bots.rb:22:in `on_startup'
	from /app/lib/twitter_ebooks/bot.rb:371:in `fire'
	from /app/lib/twitter_ebooks/bot.rb:353:in `prepare'
	from /app/bin/ebooks:361:in `block (2 levels) in start

And when I run simply ebooks start on Heroku:
~ $ ebooks start
/app/vendor/ruby-2.3.1/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in `require': cannot load such file -- twitter_ebooks (LoadError)
	from /app/vendor/ruby-2.3.1/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in `require'
	from /app/bin/ebooks:4:in `<main>'

Both of these commands work locally on my machine (OS X El Capitan). I'm guessing I've mucked something up with git, as evidenced by the fact that I can run bundle exec ebooks archive <username> corpus/<username>.json:
fatal: Not a git repository (or any parent up to mount point /app)
Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set).
Currently 3253 tweets for <username>
No new tweets

and that works the same as my local machine aside from the git repository error. Any help?

Should be noted that it... obviously is a git repo, and when I run git init on Heroku it simply removes the git repository errors without fixing anything else.


Structure with NOT[] atom does not open

Steps to Reproduce

Launch Ketcher
Open
29DHIS_prohibitatoms.zip

13-AQuery-NotList.zip
Expected behavior
Structure opens
Actual behavior
Modal window with error appears.
Screenshots

Desktop:

OS: Windows 10

Release/2.4 Closed as fixed.


Add TSC Meeting Nodes for July 11th

I also wasn't at the meeting, but I read:
Dan presented Nick's argument
+for the latter and all agreed that this is the better option
considering compile
+times and the existing node parameterization.
to meant that all agreed to use a separate node?  I agree that it should be
a separate node for the reasons you specify, so was happy when I thought
that was the conclusion :>
On Thu, Jul 18, 2019 at 6:05 AM Nick Avramoussis<EMAIL_ADDRESS>wrote:

@Idclip commented on this pull request.
In tsc/meetings/2019-07-11.md
https://github.com/AcademySoftwareFoundation/openvdb/pull/490#discussion_r304837524
:

+PR 452 - Dan to address remaining feedback by adding syncNodeVersion support to
+VDB Scatter SOP to be able to add position compression option now that spare
+data API has been introduced.

+PR 436 - Delay-loading PR. One remaining question from Peter about what happens
+to the metadata when loading just the metadata in the VDB file as a preliminary
+process to loading the rest of the file. Dan to investigate and reply to this
+then Peter to do a final pass before we merge.
+
+PR 402 - Peter to look into improving VDB SOP documentation, low priority item.
+
+Main upcoming feature includes an extension to point moving to provide merging
+grid functionality. Two options for exposing in Houdini, extending the VDB
+Combine SOP and adding a new VDB Point Merge SOP. Dan presented Nick's argument
+for the latter and all agreed that this is the better option considering compile
+times and the existing node parameterization.
Disclaimer: I wasn't at this meeting
I'm a bit confused by the comments here which are pro the Combine SOP due
to compile times and parameterization. With compile times, I'm fairly
confident that splitting it into a new SOP will be more efficient than what
you're proposing. The build can be parallelized (given the existing one
translation unit=one sop structure) and thus essentially overlapped with
the build of the Combine SOP which is by far the slowest building node.
Shoving more functionality into it is guaranteed to increase the maximum
possible build time. Note that as this new functionality will only work on
OpenVDB Points grids, only a single grid type will need to be considered,
which, given the time complexity of building other nodes, becomes
negligible in comparison with more than 1 thread.
In regards to node parameterization, the argument for a new node was to
more closely match Houdini workflow for "points" rather than trying to
augment a SOP where almost none of it's existing behaviour (maybe none at
all?) is actually relevant to OpenVDB Points grids. This will definitely
not be immediately intuitive to users wanting to combine (the Houdini
terminology for this operation is "merge") OpenVDB Point grids. Note that
if we, say, supported activity operations in Houdini on OpenVDB Points
grids, this would make sense to live on the Combine node. The act of
"merging" however perhaps doesn't. An additional minor point is the nice
multi input advantage the merge has vs using an extra Houdini merge.
I almost missed this point, please tag me in future!
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/AcademySoftwareFoundation/openvdb/pull/490?email_source=notifications&email_token=AALXQLYHLI4MCFPLB6AFFMDQAA55VA5CNFSM4IBVBFTKYY3PNVWWK3TUL52HS4DFWFIHK3DMKJSXC5LFON2FEZLWNFSXPKTDN5WW2ZLOORPWSZGOB62YMXY#pullrequestreview-263554655,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AALXQL6AS2BM7O7FBTUOLTLQAA55VANCNFSM4IBVBFTA
.


An intermediate error is seen when more than one field is edited in an EKS cluster

What kind of request is this (question/bug/enhancement/feature request): bug
Steps to reproduce (least amount of steps as possible):

Deploy a hosted EKS cluster
Edit cluster --> Modify Logging types, Add a node group and add tags to the cluster.
Save the changes made
Cluster goes into updating.
An intermediate Error is seen ResourceInUseException: Cannot update because cluster test-auto-eks-84533 currently has update 917f5e3f-d5a2-4c76-8a12-2780f35f2f6b in progress { RespMetadata: { StatusCode: 409, RequestID: "aecde674-4875-4e55-b534-6fb2c68f0403" }, ClusterName: "test-auto-eks-84533", Message_: "Cannot update because cluster test-auto-eks-84533 currently has update 917f5e3f-d5a2-4c76-8a12-2780f35f2f6b in progress" }
It is seen for around less than 30 seconds, and the cluster keeps updating after this and comes to Active state.
Cluster gets updated as expected

Expected Result:
This error message should Not be seen.
Other details that may be helpful:
Environment information

Rancher version (rancher/rancher/rancher/server image tag or shown bottom left in the UI): master-head - commit id: d19f179c4
Installation option (single install/HA): HA

Cluster information

Cluster type (Hosted/Infrastructure Provider/Custom/Imported): hosted EKS
Kubernetes version (use kubectl version):

1.17

Verified on master-head commit id: c428bc9f

Deploy a hosted EKS cluster
Edit cluster --> Modify Logging types, Add a node group and add tags to the cluster.
Save the changes made
Cluster goes into updating.
No error seen on the UI
But error "Cannot update" is seen in the logs for sometime before the errors stop and the nodegroup starts provisioning.

Reopening the issue to see if this error in the logs can be fixed.


Defer re-showing Find widget when restoring hidden webview (may fix #177046)

This is a speculative change which I hope will fix #177046. I am unable to determine whether or not it does because of #136476 (webview find widget doesn't work in OSS builds). Hence submitting the PR as a draft.

@rzhao271 is there a way I can build and test this myself? If not please try it yourself when endgame pressure subsides. Or maybe you already tried my idea and found it made no difference.

Hi John, thanks for the PR and the bump!
In this case, there are some internal processes involved and I had to test the change myself. I have confirmed that the program still crashes with your change on Electron 30.
Some good news is that Deepak and I have just merged in a change to Electron 32 to fix the issue on the internal Electron level.
Closing this PR. @deepak1556 could we make a tracking issue for Electron 32 adoption in VS Code?

You can track the progress for Electron 32 adoption in https://github.com/microsoft/vscode/pull/218245


H.265/HEVC isn't supported by the graphics card

Throws error saying its not supported but the graphics card supports it.
Happens when another program in background uses cuda/nvenc (in my case each time with Adobe Premiere Pro CC 2017)

What's the make of your GPU?
Consumer GPUS are limited to 2 simultaneous NVENC sessions.
On Oct 2, 2017 22:32, "Symbai"<EMAIL_ADDRESS>wrote:

Throws error saying its not supported but the graphics card supports it.
Happens when another program in background uses cuda/nvenc (in my case
each time with Adobe Premiere Pro CC 2017)
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/stax76/staxrip/issues/300, or mute the thread
https://github.com/notifications/unsubscribe-auth/ACP2h7AmIfeeFqUFelFKZlOo8AzzXXBGks5soTo7gaJpZM4PrIjy
.

GTX 1080 (yes consumer). However only Staxrip (once instance) and adobe premiere was running but maybe adobe uses more than 1. Still the error message is confusing in this case

Yes, more than 2 NVENC sessions trigger the error.
On 3 October 2017 at 17:19, Symbai<EMAIL_ADDRESS>wrote:

GTX 1080 (yes consumer). However only Staxrip (once instance) and adobe
premiere was running but maybe adobe uses more than 1. Still the error
message is confusing in this case
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/stax76/staxrip/issues/300#issuecomment-333856797, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ACP2h_bRGKXB7zNd9cliJgYCuSnqStjAks5sokJkgaJpZM4PrIjy
.

Ok thanks


AttributeError: module 'tensorflow_core.keras' has no attribute 'Seqential'

D:\anaconda\python.exe E:/test/hand/have_train.py
(60000, 28, 28) (60000, 10)
Traceback (most recent call last):
File "E:/test/hand/have_train.py", line 19, in
model=keras.Seqential([
File "D:\anaconda\lib\site-packages\tensorflow_init_.py", line 51, in getattr
return getattr(module, item)
AttributeError: module 'tensorflow_core.keras' has no attribute 'Seqential'

@wangshan1997
In order to expedite the trouble-shooting process, please provide a code snippet to reproduce the issue reported here. Thanks!

@wangshan1997
I believe it is tf.keras.Sequential and not the one you mentioned. Please check your spelling.

@wangshan1997 Could you please update as per the comment above ?Thanks!


Implement inventories for players

So far inventories are kept track of server-side, and slot setting and switching works. Also, players have an inventory full of iron shovels to begin with. How fun.

Closing because redundant, mineflayer already has a window class.


Making team page look responsive in mobile view

Describe the feature
I would like to make teams page responsive in mobile view
Add ScreenShots

Record

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

@dhairyagothi assigned


Implement the Features from Paulson et al.

We need public implementations of the features from Paulson et al., Table 1
Implement the following features

[ ] Median current, charge and discharge
[ ] Average voltage, charge and discharge
[x] Cumulative capacity, charge and discharge
[x] Cumulative energy, charge and discharge
[ ] Coulombic efficiency
[ ] Energy efficiency
[ ] Median current normalized by the lifetime median current, charge and discharge
[ ] Capacity as a fraction of initial capacity
[ ] Time charging and time discharging
[ ] Time at constant current, charge and discharge
[ ] Time at constant voltage, charge and discharge
[ ] Ratio between time at constant current and constant voltage, charge and discharge
[ ] Time interval during equal voltage change (3.5-4.0V), charge [Need @npaulson clarification]
[ ] Voltage at start and end of charge and discharge
[ ] Voltage at a certain state of charge, charge and discharge
[ ] Derivative of voltage wrt time at a certain state of charge, charge and discharge
[ ] Voltage change between start of cycle and certain time, charge and discharge
[ ] Open circuit voltage at a certain state of charge [Requires ECM fitter]
[ ] Resistance at a specific state of charge  [Requires ECM fitter]
[ ] SOC at a specified voltage
[ ] Location of each peak in the dQdV curve, charge and discharge [Requires peak detection]
[ ] Magnitude of each peak in the dQdV curve, charge and discharge [Requires peak detection]
[ ] Area under each peak in the dQdV curve, charge and discharge [Requires peak detection]
[ ] Location of each valley in the dQdV curve, charge and discharge [Requires peak detection]
[ ] Magnitude of each valley in the dQdV curve, charge and discharge [Requires peak detection]
[ ] Location of each peak in the dVdQ curve, charge and discharge [Requires peak detection]
[ ] Magnitude of each peak in the dVdQ curve, charge and discharge [Requires peak detection]
[ ] Location of each valley in the dVdQ curve, charge and discharge [Requires peak detection]
[ ] Magnitude of each valley in the dVdq curve, charge and discharge [Requires peak detection]
[ ] Statistics of the different in rate of SOC vs voltage distribution between changes, charge and discharge
[ ] Change in SOH at a function of cycle

then

[ ] Create an example on how to compute the features

Added capacity-related features in #55 , though we can improve them #58


OTG in-game menu bug

OTG Plugin or Mod
[Please specify if it's about Forge Mod or Spigot server Plugin placing "x" into []]

[x] OTG Mod for Forge
[ ] OTG Plugin for Spigot

OTG Version
[Please specify the full OTG version that you are running by placing "x" into []]

[ ] 1.12.2_v8_r1
[ ] 1.12.2_v7_DEV_r26
[ ] 1.12.2-v6
[ ] 1.12.2-v5
[ ] 1.11.2-v8
[ ] 1.11.2-v9
[ ] 1.10.2-v21
[x] Other - specify here 1.12.2_v9.3

Forge or Spigot Versions
[Playing on forge <IP_ADDRESS>54]
What other plugins are you running?
[Playing with the modpack Roguelike Adventures and Dungeons]
Description
[I use the pregenerator for my solo map but when i'm tapping on my o key, (key for opening OTG in-game menu), to see the advance of the pregen, it doesn't work, nothing is happening. How can I fix it? btw my o key is only assigned to the OTG menu]

You must have cheats enabled in single-player or be OPed in multiplayer.

Oh that's works! thank you for the quick reply


how Can I set the log level to output ADEBUG information.

I see a lot of code are using log "ADEBUG',
I can find "INFO","WARNING","ERROR","FATAL",but no “DEBUG”，and I Could not find anything in log related to ADEBUG

Please use - -v=4 for DEBUG

It is defined in apollo/modules/common/log.h

I'm sorry I still don't understand how to use it or define it.

e.g. if you want to see ADEBUG in planning module, modify modules/planning/conf/planning.conf and add one line: --v=4, it will print out all ADEBUG. You can set --vmodule=filename=4 to print just ADEBUG in that filename.

Hi, I  change the --v in the conf. But still, I haven't got any output for the ADEBUG. Thank you.

Hi! How do I add Debug info to log files in Apollo 6? I have already add
--debug level
--vmodule=piecewise_jerk_path_optimizer=4
In bottom of planning.conf fileinside the docker, but nothing happened. I tried to restart the docker and run apollo in debug mode, but there are still no debug info inside planning.


[WIP] remember user.current_group in the session

NOTE: Please don't merge until we discuss this.
High Level:
When an admin changes the group of a user, the user#current_group changes in the database. We need to determine if we want to continue using the group at login, or if we want to reset the session to update the values.
Details:
In 5.4, we used the current_group at the time of login, but in many places fell back to the value in the database. Therefore it was not consistent.
In 5.5, the code has been changed to pass around the user object, which is consistent. But it is always reading the group from the database. This potentially changes the current_user#current_group but has values from the old group in session/@sb.
After:
current_group remains as the value in the login.
Added a block in application_controller to detect a change and act accordingly. We need to determin what should happen.
Also of note, after this change, a single user should be able to be logged in as 2 different groups (via 2 different browsers).
/cc @Fryguy @chessbyte Not sure if we want to target 5.5 or 5.6 for this.
/cc @dclarizio This is what we discussed

@Fryguy updated the comments here. thanks for adding a WIP

/cc @gtanzillo @gmcculloug this is the PR I mentioned.
Of note, fixing this allows us to transition away from the user#current_group_id field and be more confident that the API will be using the correct tenant/group.

@gmcculloug Moving gitter discussion into here.
In 5.5, we change the group, but @sb still has the old values.
This PR says, maybe we should keep using the old group, so @sb and current_group are in sync.
But open for discussion, what do we do when we detect that a user's default group has changed? Do we ensure that they are still a member of the existing group?

But open for discussion, what do we do when we detect that a user's default group has changed? Do we ensure that they are still a member of the existing group?

@kbrock I like the idea of making sure they are still allowed to use the group they logged in with.  If not, it is my opinion that we kick them off (similar to a timeout) with an appropriate message.

@kbrock @dclarizio @gtanzillo @gmcculloug What is the status of this PR?

@chessbyte This is ready to merge
The 2 spec use cases added are:

when an admin changes your group and you are still in the originally logged in group, you continue to be using the original group.
when an admin changes your group and you are no longer in the original group, it times you out.

These changes look good to me :+1:

Looks good to me as well . . . I will merge.


Consider removing or hiding take_body fn

Feature Removal
This is a suggestion to remove or hide the take_body fn from tide::Context.
Context
With the addition of the request_mut function, it might be a good idea to consider removing or hiding this function as it's a bit redundant -- one could achieve the same effect by calling std::mem::replace(cx.request_mut().body_mut(), Body::empty()).
Although request_mut has a much higher surface area, I can't think of many places where one would only want to consume the body outside of extracting forms (which we already provide an interface for through tide::forms).
(On that note we should also rename tide::forms::ExtractForms to tide::forms::ContextExt later...)
Implementation
We could either achieve this by removing all usage of take_body with the aforementioned, or simply just use pub(crate) instead.

@fairingrey I feel we should get our streams story fleshed out + documented completely before we move things out. Ideally I could see us implement AsyncRead on Request directly, but I feel that might not work out well for us in this case.
Which is to say: I don't feel like I'm currently qualified to judge whether we should remove take_body. Probably getting a bit more experience with this would be great.

That sounds like the better approach for now -- we can always revisit this issue later. The bigger issue at hand should be https://github.com/rustasync/http-service/issues/31. From there we'd be able to better reason about these possible changes.

@fairingrey I like the idea of sorting out the streams story with https://github.com/rustasync/http-service/issues/31. That being said - I dislike the idea of encouraging the use of request_mut - it's nice to have for low level control, but I think the use of that should be discouraged other than specific cases, like the the compression module that you just merged - even which I think we probably should find a more refined approach with some abstractions rather than doing request_mut.
Http body (without buffering) is a one time readable. That's the reason take_body method exists in the first place - I think that's more obvious in a code base where take_body is being used.

I agree -- most users shouldn't be using request_mut anyway, given, as it's only there for particular cases where it's absolutely necessary, such as with compression as you've said.
Another remark -- On that note I could refactor it such that middleware context has less overall exposure, but it still requires we somehow have another way to set the body, probably through some fn set_body(&mut self, body: Body) -> Result<()> or something like that.

Http body (without buffering) is a one time readable.

Right, but we do already have other methods for extracting the body in its entirety -- it would only require a change to body_bytes.
Ah, also -- sorry I'm not more clear about this. I mean as someone who would likely work directly with the streaming Body, they might opt to use something with more low-level control. That said, I think now I'm in support of keeping take_body as it stands. But, the bigger concern is if http-service will continue to use Stream<Item = Result<Bytes, io::Error> as its underlying body or if we go with something else.
Anyways, sorry to bother you all, but I think we know where we should go with this for now :sweat_smile: Thanks for the replies!


Please invite me to the GitHub Community Organization

Name
Tran Nguyen Thuong Truong - @thuongtruong1009
Discord Username (if applicable)
thuongtruong1009
Additional Context
Hi guys!
Because this organization is a great community for me.
I want to join this organization for learning good Developer Skills and contribute to Open Source.
Nice to meet you!
Thank you very much!

Welcome to the community! Check your email for an invite.

Welcome to the community! Check your email for an invite.

Thank you very much!


Add a GUC to limit the recursion depth

Description
Currently, recursive CTE has no limit on the recursion depth. This can cause it to run infinitely. T-SQL on the other hand has a default limit of 100 on the recursion depth. The change is to add a new GUC which can store the default maximum recursion depth
Issues Resolved
Task: BABEL-2202
Check List

[x] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is under the terms of the Apache 2.0 and PostgreSQL licenses, and grant any person obtaining a copy of the contribution permission to relicense all or a portion of my contribution to the PostgreSQL License solely to contribute all or a portion of my contribution to the PostgreSQL open source project.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

This feature is de-scoped  for now.


:seedling: performance: run integration tests only on approved PRs

What kind of change does this PR introduce?
This is a CI Performance Improvement.

[x] PR title follows the guidelines defined in our pull request documentation

What is the current behavior?
Currently, Integration tests take ~13m & every run on every PR (without approval).
What is the new behavior (if this is a feature change)?**
This Proposed changes will improve that & it would run Integration Test only on approved PRs.

[ ] Tests for the changes have been added (for bug fixes/features)

Which issue(s) this PR fixes
Fixes #2603

Special notes for your reviewer
Does this PR introduce a user-facing change?
No

NONE

Signed-off-by: Siddhant Khare<EMAIL_ADDRESS>

@Siddhant-K-code  Thank you!!


Point Light not getting the proper priority

On the URP version of the shader, if there's ambiental light, a directional light, then eventually a point light in the scene, liltoon completely ignores the point light even if the intensity of the said point light's set to over 20. Other lit surfaces/shaders react properly to the point light while lilToon completely ignores it thanks to the directional & ambiental light that take over way more than point light's intensity.

On the left's the lilToon material on the right a normal lit surface.

lilToon blends all the lights in a scene and calculates the final light direction, preventing multiple shadows from being applied to a single character and making it look bad. This comes from anime lighting.
Example:
Light Direction += Ambient Light Direction * Ambient Light Intensity;
Light Direction += Sun Light Direction * Sun Light Intensity;
Light Direction += 1st Light Direction * 1st Light Intensity;
Light Direction += 2nd Light Direction * 2nd Light Intensity;
Light Direction += 3rd Light Direction * 3rd Light Intensity;
...
Light Direction = normalize(Light Direction);

The degree of influence varies with the intensity of the light, so if other lights are extremely bright, the point light may appear to be ignored (it actually has a slight influence).


MAINT: stats._contains_nan: fix bug when -inf and inf are in sample

Reference issue
Closes gh-20386
What does this implement/fix?
gh-20386 reported that stats.kstest returned NaNs when both positive and negative infinities were present in the sample. This fixes the (very old) underlying bug.
Additional information
This includes all the gh-20292 commits, so that should merge first.
I could add a test for _contains_nan directly if desired. (Currently, this just adds a test for the reported issue in kstest.)

Title is prefixed with MAINT: but says "fix bug," so I've tentatively added a backport label

Probably better not to backport because this is mixed with adding array API support to the function, which is a new feature. Up to you, though.


add pygeoapi

Related Issue(s): #
none
Proposed Changes:

Add pygeoapi to implementations page.

PR Checklist:

[x] This PR has no breaking changes.
[x] I have added my changes to the CHANGELOG or a CHANGELOG entry is not required.
[ ] API only: I have run npm run generate-all to update the generated OpenAPI files.

Not 100% sure, but implementation changes should go towards dev, right? @cholmes
Probably related to #767

Yeah, everything should start at dev. Just changed the base. And yes, this should migrate to stacspec.org But getting here will help keep track of it.


Ensure proper reference of component information when creating Blackduck finding in the _process_project_findings method

Ensure proper reference of component information when creating Blackduck finding in the _process_project_findings method
:warning: Note on feature completeness :warning:
We are narrowing the scope of acceptable enhancements to DefectDojo in preparation for v3. Learn more here:
https://github.com/DefectDojo/django-DefectDojo/blob/master/readme-docs/CONTRIBUTING.md
Description
Noticed the absence of component information in the results of a Black Duck Hub Scan. Upon inspecting the code, it became apparent that the component information does exist but is not being referenced during the creation of the BlackDuckFinding in the _process_project_findings method of the BlackduckImporter. This pull request aims to address this issue by updating the code to include the necessary references.
Test results
Ideally you extend the test suite in tests/ and dojo/unittests to cover the changed in this PR.
Alternatively, describe what you have and haven't tested.
Documentation
Please update any documentation when needed in the documentation folder)
Checklist
This checklist is for your information.

[ ] Make sure to rebase your PR against the very latest dev.
[ ] Features/Changes should be submitted against the dev.
[x] Bugfixes should be submitted against the bugfix branch.
[x] Give a meaningful name to your PR, as it may end up being used in the release notes.
[x] Your code is flake8 compliant.
[x] Your code is python 3.11 compliant.
[ ] If this is a new feature and not a bug fix, you've included the proper documentation in the docs at https://github.com/DefectDojo/django-DefectDojo/tree/dev/docs as part of this PR.
[ ] Model changes must include the necessary migrations in the dojo/db_migrations folder.
[ ] Add applicable tests to the unit tests.
[ ] Add the proper label to categorize your PR.

Extra information
Please clear everything below when submitting your pull request, it's here purely for your information.
Moderators: Labels currently accepted for PRs:

Import Scans (for new scanners/importers)
enhancement
performance
feature
bugfix
maintenance (a.k.a chores)
dependencies
New Migration (when the PR introduces a DB migration)
settings_changes (when the PR introduces changes or new settings in settings.dist.py)

Contributors: Git Tips
Rebase on dev branch
If the dev branch has changed since you started working on it, please rebase your work after the current dev.
On your working branch mybranch:
git rebase dev mybranch

In case of conflict:
 git mergetool
 git rebase --continue

When everything's fine on your local branch, force push to your myOrigin remote:
git push myOrigin --force-with-lease

To cancel everything:
git rebase --abort

Squashing commits
git rebase -i origin/dev

Replace pick by fixup on the commits you want squashed out
Replace pick by reword on the first commit if you want to change the commit message
Save the file and quit your editor

Force push to your myOrigin remote:
git push myOrigin --force-with-lease

@manuel-sommer Pushed fix in https://github.com/DefectDojo/django-DefectDojo/pull/9155


request: documentation about ByteAPI IDL specification

Missing links in generic documents:

https://www.cloudwego.io/zh/docs/kitex/tutorials/advanced-feature/generic_call/#2-http-映射泛化调用
https://www.cloudwego.io/docs/kitex/tutorials/advanced-feature/generic_call/#2-http-mapping-generic-call

Updated: https://www.cloudwego.io/docs/kitex/tutorials/advanced-feature/generic-call/
IDL Definition Specification for Mapping between Thrift and HTTP


new sitemap plugin completes issue #201

new plugin for report stage (needs to be registered in render stage too to get options)
generates sitemap.xml for SEO and puts it in html root directory
(no other change needed as search engines pick up the file)
change plugins config to add plugin
change plugin-options config to add root-domain
remove redundant plugin-options
some priorities are given to files, which may affect their relative rankings in a search engines result response.

https://new-raku.finanalyst.org/sitemap.xml is a 404

@coke I haven't run this on new-raku. I'll do that now.

@coke sitemap.xml is now accessible on new-raku/sitemap.xml
I haven't looked into styling the sitemap, I don't have the time to do it, and I cant see the point. If someone finds it REALLY necessary, they can raise an issue later.

Seems fine. I would recommend opening a ticket to add <lastmod> which someone else can take a stab at.


Add Target OS and Arch arguments to Dockerfile

Compiling with GOARCH=amd64 and CGO_ENABLED=1 results in failure to build an image with the siteconfig-acm-212-on-pull-request Konflux pipeline job.
This PR introduces arguments  in the Dockerfile for specifying the target OS and target architecture.

/retest siteconfig-acm-212-on-pull-request

/lgtm


Add files via upload

Exercise - Create the pipeline

 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.:x: Erik-Willem sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.


Not used metadata write_only_fields on create field

I have geo field in write_only_fields metadata, but this filed present in view response
Test Model:
class Profile(models.Model):
    id = models.AutoField(primary_key=True)
    name = models.CharField(max_length=50)
    position = models.PointField(null=True, blank=True, geography=True)

Test Serializer:
class ProfileSerializer(serializers.ModelSerializer):
    class Meta:
        model = Profile
        fields = ('id', 'name', 'position', )
        write_only_fields = ('position', )

Server response:
GET /profile
[
    {
        "id": 4,
        "name": "Test",
        "position": {
            "type": "Point",
            "coordinates": [
                37.44638510000001,
                55.72377399999998
            ]
        }
    }
]

Expected response without "position" field

So, to sum up, you meant to say that the write_only_field option is not respected by drf-gis?

Sorry, this is my mistake, i read old doc version.
Worked serializer is:
class ProfileSerializer(serializers.ModelSerializer):
    class Meta:
        model = Profile
        fields = ('id', 'name', 'position', )
        extra_kwargs = {
            'position': {'write_only': True},
        }


Fix Cross Tenant subscriptions related UI issues.

Fix Cross Tenant subscriptions related UI issues.

https://github.com/wso2/product-apim/issues/12570


Including file include from the commandline

Only pitfall is that if an input argument has include as the starting keywords. Probably can make it something like !include instead of include.

Look into if it's somehow possible to use a custom datatype inside dataclass_wrapper and detect it while arparsing.
Testing for various different cases.
a. Nested includes in config files
b. include plus command line:  python dracus.py --config_path config.yaml --data "include data.yaml" --data.data_path "path_not_found"

could you add a couple of unit tests please


Make tag links in collections publisher clickable

Where "urls" are displayed for topics or mainstream browse pages, they
are now clickable and open the corresponding URL on the live site when
clicked.
https://trello.com/c/4xrXljxX/61-make-tag-links-in-collections-publisher-clickable

This looks good - will merge.
One thing for future; it's quite nice to include a screenshot in the PR if you've changed something that can sensibly have a screenshot made of it.


Cache results by mondo adapter

Use something like memoize to cache results and reduce time, somewhere here:
https://github.com/monarch-initiative/malco/blob/7f91ae8002c633552af59479bad886010bb73710/src/malco/post_process/mondo_score_utils.py#L84-L89
Possibly useful links by @pnrobinson :
https://stackoverflow.com/questions/1988804/what-is-memoization-and-how-can-i-use-it-in-python
https://github.com/monarch-initiative/pyphetools/blob/main/src/pyphetools/creation/variant_manager.py

Isn't that what the lru_cache on omim_mappings() is already doing?

Isn't that what the lru_cache on omim_mappings() is already doing?

I did not know what that was, actually, yes!
However, it seems like it's still very very slow. Maybe the cache does not persist between multiple function calls? In the current setup, we are calling score_grounded_result() in a for loop in compute_mrr(), see:
https://github.com/monarch-initiative/malco/blob/2a30bb15d8c7f433495283cbc2b6073b628a7c84/src/malco/post_process/compute_mrr.py#L35-L47
The for loop iterates over grounded prompt replies, i.e. number of phenopackets times number of languages times, well, how many diseases are in each differential. A lot of calls. Can we make the cache persist withing calls, maybe as long as compue_mrr has successfully exited?

Actually, it seems to me like I was off, the cache does persist. But the standard size is 128 elements. I tried running with increased cache size and it seems to be faster, just by looking at it. This needs further testing to be systematic and if we really want to rely on this, especially for larger runs, but it's pointing us in the right direction, I think.

How slow is this now? If it's fast enough we probably should focus on tidying up the the code.
If it's painfully slow probably we should just multiprocess the for loop (see here) instead of improving caching

I should have timed my last run but 2 phenopackets across 5 languages took <10 min.


[ExternalNode] Add known issue in the document

Document a known issue about OVS cleanup in VM reboot case, and
provide a workaround.
Signed-off-by: wenyingd<EMAIL_ADDRESS>

@jianjuns @tnqn I have addressed the comments, could you help review again?

/skip-all

Rebased it on the latest main branch

/skip-all


METRON-235 Expose filtering capability for PCAP via CLI tool

In the process of testing with Vagrant, but wanted to get this in front of people for review.
Relevant Jira:
https://issues.apache.org/jira/browse/METRON-235
In the process of upgrading to Kibana 4, we lost our about to query/filter pcap results. This PR exposes the 2 methods for filtering PCAP data, fixed parameters and the "Stellar" query language, via a command line tool. The tool is executed via ${metron_home}/bin/pcap_query.sh
Note: I also tweaked the mem settings for Ambari mapreduce to get around persistent OOO errors - mapreduce container sizes (mapreduce.[map | reduce].memory.mb) have been increased to 1.2 GiB, mapreduce.[map | reduce].java.opts have been increased to 1 GiB.

Overall outside of the things I mentioned, this looks really great.  Solid contribution @mmiklavc.  The only other thing that I would add is to please document this as part of the README.md in pcap-backend  A simple description and the possible options for the CLI in both modes would be sufficient.

I agree with Casey.  We need more docs on the CLI.  What can I query for?  Which commands should I run to validate this?

+1 from me

+1, looks good!


Add test that validates fingerprint.StartsWith

Description of Changes
Same as https://github.com/open-telemetry/opentelemetry-log-collection/pull/145
Please check that the PR fulfills these requirements

[ ] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features)
[ ] Add a changelog entry (for non-trivial bug fixes / features)
[ ] CI passes

Log Files
Logs / Second
CPU Avg (%)
CPU Avg Δ (%)
Memory Avg (MB)
Memory Avg Δ (MB)

1
1000
1.4138083
+0.13790584
128.63052
+0.004180908

1
5000
4.9655886
+0.37934923
137.38914
+1.8741913

1
10000
11.414107
+1.5862837
144.52249
+0.55145264

1
50000
54.80313
+5.66481
174.2504
-0.16770935

1
100000
87.845474
-7.4488373
222.01064
-18.012802

10
100
1.9655142
+0.20687366
134.13672
+0.09927368

10
500
5.5864544
-1.1551642
139.46565
+0.4035492

10
1000
10.620748
-0.034568787
143.33769
-5.137253

10
5000
50.50157
-3.1547813
176.41164
+2.1430511

10
10000
104.86178
+2.6952972
227.08432
+9.212692

Log Files
Logs / Second
CPU Avg (%)
CPU Avg Δ (%)
Memory Avg (MB)
Memory Avg Δ (MB)

1
1000
1.4482837
+0.17238116
127.57732
-1.0490265

1
5000
5.069172
+0.48293257
136.94922
+1.4342651

1
10000
10.328119
+0.50029564
143.96915
-0.0018920898

1
50000
51.411953
+2.273632
180.12244
+5.7043304

1
100000
96.50711
+1.2127991
238.6207
-1.4027405

10
100
1.931063
+0.17242253
133.90787
-0.12957764

10
500
5.586325
-1.1552935
137.43817
-1.6239319

10
1000
10.724245
+0.06892872
143.40598
-5.0689697

10
5000
54.442932
+0.78657913
176.86314
+2.5945587

10
10000
98.967354
-3.1991272
225.20824
+7.336609