Required Kubernetes Configuration to Join Worker Nodes

I have issues
understanding how to customize the module config to allow for the worker nodes to automatically get detected by the k8s master.
I'm submitting a...

[ ] bug report
[ ] feature request
[√] support request
[ ] kudos, thank you, warm fuzzy

terraform apply output produces a config_map_aws_auth k8s ConfigMap.
After configuring kubectl to access the cluster, I can see that all my nodes are ready:
✗ kubectl get nodes NAME                                       STATUS   ROLES    AGE   VERSION ip-10-0-2-166.eu-west-1.compute.internal   Ready    <none>   19m   v1.10.3 ip-10-0-2-17.eu-west-1.compute.internal    Ready    <none>   19m   v1.10.3
However, my understanding was that I needed to write the config_map_aws_auth manually to the cluster with kubectl, as I haven't set manage_aws_auth explicitly to true.
According to the kubectl output I provided, it looks the workers have nevertheless managed to join the cluster.
I also found reference to this procedure in the official terrafrom eks-getting-started guide:
https://www.terraform.io/docs/providers/aws/guides/eks-getting-started.html
There don't seem to be any ConfgiMaps avaialable in the cluster:
✗ kubectl get configmaps No resources found.
Environment details

Affected module version: 1.7.0
OS: macOS Mojave 10.14.1
Terraform version: 0.11.10

Any other relevant info
Thanks in advance!

Right, I see it in the kube-system namespace.
Tested scheduling some pods, that seems to work.
So, then, basically manage_aws_auth is enabled by default, and will write the ConfigMap necessary to allow the workers to join the cluster automatically?

Yep: https://docs.aws.amazon.com/eks/latest/userguide/add-user-role.html

Cool, thanks for the info!


[Feature Request] "slow tokenizer" format (vocab.json and merges.txt)

Wondering whether this code is supposed to work (or some variation on the repo URL - I tried a few different things):
await import("https://cdn.jsdelivr.net/npm/@xenova/transformers@1.4.2/dist/transformers.min.js");
let tokenizer = await AutoTokenizer.from_pretrained("https://huggingface.co/cerebras/Cerebras-GPT-1.3B/resolve/main");

The cerebras/Cerebras-GPT-1.3B repo only has a config.json (no tokenizer.json), but the config.json has "model_type": "gpt2", and has vocab.json and merges.txt. It does load successfully with the Python Transformers lib.

This is because the library currently doesn't support the "slow tokenizer" format (which is with vocab.json and mergex.txt). Ours only accepts the fast_tokenizer format (which is constructed directly from the single tokenizer.json; see "fast_tokenizer_file" in the code below)
https://github.com/huggingface/transformers/blob/ac2bc50a10522f15671e351150e03ecd6268da1e/src/transformers/tokenization_utils_fast.py#L95-L126
What's happening in the background of the python library, is that when you load the slow tokenizer, it gets converted to the fast tokenizer format. I'm not too sure why the creators of the model didn't include the tokenizer.json and tokenizer_config.json files, as it should be output when running save_pretrained().
For the moment (since adding support for the slow tokenizer format is not the biggest priority), you can just load the tokenizer and then just save it again (which saves the fast format, by default)
from transformers import AutoTokenizer

tokenizer = AutoTokenizer.from_pretrained('cerebras/Cerebras-GPT-1.3B')
tokenizer.save_pretrained('output')
# Will output merges.txt, special_tokens_map.json, tokenizer.json, tokenizer_config.json, and vocab.json.

Ah, okay - thanks for that! I've changed the title of this issue, but please feel free to close this. In my case it's end users who enter a Hugging Face repo name in order to run the model on OpenCharacters, so most won't know how to do that in Python, but hopefully this isn't an issue for many repos, and I can always create forks on Hugging Face and add the files for the popular repos (that use the slow tokenizer format) that users want.
Again, please feel absolutely free to close this - from what you're saying it sounds like the "slow" format is on its way out and might be a waste time to implement.

Indeed - the slow format is "legacy", see here:
https://github.com/huggingface/transformers/blob/5bb4ec6233d6414a922ad2818f0bcf879de81c28/src/transformers/tokenization_utils_base.py#L2085-L2095
Of course, the main use-case is to load models from repos that contain the .onnx files, which (if correctly converted) should have the tokenizer.json file. I'll close the issue since, as you mentioned, it will probably be a waste of time to implement the legacy format.
That said, I am working with the HF team to get web-ready versions of model files (.onnx and the associated files) in the officially supported model repos. And if a user wants to publish their own model, it should be their responsibility to make it support various formats (e.g., pytorch, safetensors, onnx, tensorflow)

I am working with the HF team to get web-ready versions of model files (.onnx and the associated files) in the officially supported model repos

:eyes: :eyes: :eyes: :eyes: :eyes:

@xenova Can I confirm: The repo needs to have both tokenizer.json and tokenizer_config.json? I expected this to work:
await import("https://cdn.jsdelivr.net/npm/@xenova/transformers@1.4.3/dist/transformers.min.js");
let tokenizer = await AutoTokenizer.from_pretrained("https://huggingface.co/distilgpt2/resolve/main");

Since distilgpt2 has a tokenizer.json file, but I get this error:
caught Error: File not found. Could not locate "https://huggingface.co/distilgpt2/resolve/main/tokenizer_config.json".
    at u (utils.js:244:23)
    at async fetchJSON (utils.js:297:9)
    at async Promise.all (:3001/index 1)
    at async AutoTokenizer.from_pretrained (tokenizers.js:2591:29)

I ran the code below on the first two pages of the text-generation pipeline tag on huggingface.co/models.
let urls = [...document.querySelectorAll("a.block.p-2")].map(el => el.href+"/resolve/main");
let output = "";
for(let url of urls) {
  await import("https://cdn.jsdelivr.net/npm/@xenova/transformers@1.4.3/dist/transformers.min.js");
  let tokenizer = await AutoTokenizer.from_pretrained(url).catch(e => false);
  let success = !!tokenizer;
  console.log(url, success);
  output += `\n${success ? "SUCCESS" : "fail"}: ${url}`;
}

Output:
fail: https://huggingface.co/gpt2/resolve/main
fail: https://huggingface.co/distilgpt2/resolve/main
fail: https://huggingface.co/gpt2-medium/resolve/main
fail: https://huggingface.co/openai-gpt/resolve/main
fail: https://huggingface.co/gpt2-large/resolve/main
SUCCESS: https://huggingface.co/bigscience/bloom-560m/resolve/main
fail: https://huggingface.co/EleutherAI/gpt-neo-2.7B/resolve/main
fail: https://huggingface.co/decapoda-research/llama-7b-hf/resolve/main
SUCCESS: https://huggingface.co/bigscience/test-bloomd-6b3/resolve/main
SUCCESS: https://huggingface.co/bigscience/bloom-7b1/resolve/main
fail: https://huggingface.co/EleutherAI/gpt-neo-1.3B/resolve/main
SUCCESS: https://huggingface.co/Salesforce/codegen-350M-multi/resolve/main
fail: https://huggingface.co/gpt2-xl/resolve/main
fail: https://huggingface.co/bigcode/santacoder/resolve/main
fail: https://huggingface.co/cerebras/Cerebras-GPT-111M/resolve/main
fail: https://huggingface.co/xlnet-base-cased/resolve/main
SUCCESS: https://huggingface.co/Salesforce/codegen-2B-multi/resolve/main
fail: https://huggingface.co/facebook/opt-1.3b/resolve/main
fail: https://huggingface.co/facebook/opt-125m/resolve/main
fail: https://huggingface.co/facebook/opt-350m/resolve/main
SUCCESS: https://huggingface.co/TehVenom/PPO_Pygway-V8p4_Dev-6b/resolve/main
fail: https://huggingface.co/facebook/opt-66b/resolve/main
fail: https://huggingface.co/decapoda-research/llama-13b-hf/resolve/main
SUCCESS: https://huggingface.co/EleutherAI/gpt-j-6b/resolve/main
fail: https://huggingface.co/facebook/opt-13b/resolve/main
fail: https://huggingface.co/facebook/opt-6.7b/resolve/main
SUCCESS: https://huggingface.co/bigscience/bloomz-560m/resolve/main
SUCCESS: https://huggingface.co/codeparrot/codeparrot/resolve/main
fail: https://huggingface.co/KoboldAI/OPT-6.7B-Erebus/resolve/main
SUCCESS: https://huggingface.co/Gustavosta/MagicPrompt-Stable-Diffusion/resolve/main
fail: https://huggingface.co/sshleifer/tiny-gpt2/resolve/main
fail: https://huggingface.co/cerebras/Cerebras-GPT-1.3B/resolve/main
fail: https://huggingface.co/decapoda-research/llama-30b-hf/resolve/main
SUCCESS: https://huggingface.co/codeparrot/codeparrot-small/resolve/main
fail: https://huggingface.co/rinna/japanese-gpt-1b/resolve/main
fail: https://huggingface.co/facebook/opt-2.7b/resolve/main
fail: https://huggingface.co/EleutherAI/gpt-neo-125m/resolve/main
SUCCESS: https://huggingface.co/Salesforce/codegen-350M-mono/resolve/main
fail: https://huggingface.co/robertmyers/bpt-rm-6b/resolve/main
SUCCESS: https://huggingface.co/bigscience/bloom/resolve/main
SUCCESS: https://huggingface.co/bigscience/bloomz-7b1-mt/resolve/main
fail: https://huggingface.co/SkyWork/SkyTextTiny/resolve/main
SUCCESS: https://huggingface.co/Salesforce/codegen-16B-mono/resolve/main
SUCCESS: https://huggingface.co/EleutherAI/gpt-neox-20b/resolve/main
SUCCESS: https://huggingface.co/KoboldAI/PPO_Pygway-6b-Mix/resolve/main
SUCCESS: https://huggingface.co/bigscience/bloom-3b/resolve/main
fail: https://huggingface.co/skt/kogpt2-base-v2/resolve/main
fail: https://huggingface.co/facebook/opt-30b/resolve/main
fail: https://huggingface.co/uer/gpt2-chinese-cluecorpussmall/resolve/main
fail: https://huggingface.co/KoboldAI/OPT-2.7B-Erebus/resolve/main
SUCCESS: https://huggingface.co/TehVenom/Dolly_Shygmalion-6b/resolve/main
fail: https://huggingface.co/FredZhang7/distilgpt2-stable-diffusion-v2/resolve/main
SUCCESS: https://huggingface.co/OpenAssistant/oasst-sft-1-pythia-12b/resolve/main
fail: https://huggingface.co/PascalNotin/Tranception_Small/resolve/main
fail: https://huggingface.co/microsoft/biogpt/resolve/main
fail: https://huggingface.co/trl-internal-testing/tiny-random-GPTNeoXForCausalLM/resolve/main
SUCCESS: https://huggingface.co/KoboldAI/GPT-NeoX-20B-Erebus/resolve/main
SUCCESS: https://huggingface.co/togethercomputer/GPT-JT-6B-v1/resolve/main
SUCCESS: https://huggingface.co/togethercomputer/GPT-NeoXT-Chat-Base-20B/resolve/main
fail: https://huggingface.co/decapoda-research/llama-65b-hf/resolve/main

If this is expected behavior, and I haven't made any mistakes here, then I think the new tokenizer format might be "too new" - i.e. I think it would make sense to support the old format given the "hit rate" here?


THANK YOU!

Im buying you a coffee! You have no idea how long ive been trying to get my display to work! After weeks with no luck, you figured it out! THANK YOU SO MUCH!
This is the kit i bought which i can confirm it works flawlessly on Home Assistant OS on RPI4B
https://wiki.52pi.com/index.php?title=ZP-0130-4wire

I do have a question though. My display is 128X64. It is working but if i wanted to modify the code to be able to make the font larger or icons, is that possible?

Thanks very much :) Much appreciated. Makes me happy that my addon can help others.
As for the font and image sizing....
This is a tricky one given how the content is positioned. Resizing the fonts may be possible via the Screens.fonts method, but images haven't been abstracted. Additionally, when resizing, it will likely overflow off the screen. It may be able to add an encapsulating wrapper to calculate and reposition screen content dynamically, possibly within the draw method, but this could cause quite an overhead making it use an unnecessary amount of service resources - especially for those that wouldn't use the resizing. I will have a ponder on this, but dare say, this one may be a bit more involved. Open to suggestions if anyone has dug into the code and has a better idea for this?

Honestly it looks great as it is so if its that much of a headache, i wouldn't bother. I would be interested in figuring out a way to lower the screen brightness or even turn off option that could be used by an input_boolean toggle or even a light sensor  to turn the brightness down or up or off completely.

Im buying you a coffee! You have no idea how long ive been trying to get my display to work! After weeks with no luck, you figured it out! THANK YOU SO MUCH!
This is the kit i bought which i can confirm it works flawlessly on Home Assistant OS on RPI4B
https://wiki.52pi.com/index.php?title=ZP-0130-4wire

Do you have the ability to go to this website and see if you could figure out a way to get the led's in this fan to work as well. Id be willing to pay you if you could figure this out. Im stumped.

Ijust realized the CPU load data does not populate. It's showing 0.000.00%

Ijust realized the CPU load data does not populate. It's showing 0.000.00%

Interesting. What happens if in a bash terminal you run
top -bn1
Can you confirm what OS you're running on the RPi?

Do you have the ability to go to this website and see if you could figure out a way to get the led's in this fan to work as well. Id be willing to pay you if you could figure this out. Im stumped.

Looking at the specs of this rig, the fan appears to use the GPIO. As HomeAssistant discontinued support for this, this may be pretty involved, and outside the scope of this repo (which uses I2C).
There do appear to be some HA addons which do get around it, and allow access to GPIO controlling fan speeds and lights etc, but as I dont have a fan similar in nature, I'm unable to verify if any of these work. This would indeed be a separate project and repo if it involves any dev effort, but don't think I have the bandwidth for undertaking this task currently.
However, in looking through the supporting repo for the ZP-0130-4wire, located here: https://github.com/rm-hull/luma.examples.git, there do seem to be a nice collection of OLED screens, which are well made and nicely abstracted. So if they don't already work on a HA distribution, think this may be convertible. When I get capacity, and buy a 128x64 display, I may look at forking this repo to work in HA.

Ijust realized the CPU load data does not populate. It's showing 0.000.00%

Interesting. What happens if in a bash terminal you run top -bn1 | grep load
Can you confirm what OS you're running on the RPi?

Found it. Silly mistake.
Command being run was this:
top -bn1 | grep load | awk '{printf "%.2f", $(NF-2)}'
should be this (load should be Load):
top -bn1 | grep Load | awk '{printf "%.2f", $(NF-2)}'

Created a new issue specific to the CPU load #4 and rolled out an update


can't use any of these function

   onLoadStart={this.loadStart}   // Callback when video starts to load
   onLoad={this.setDuration}      // Callback when video loads
   onProgress={this.setTime}      // Callback every ~250ms with currentTime
   onEnd={this.onEnd}             // Callback when playback finishes
   onError={this.videoError}      // Callback when video cannot be loaded

Which version are you using?

"react-native": "0.39.2",
"react-native-video": "^0.9.0",

Change react-native-video to 1.0.0 and 'npm install'

i'll try Thanks

Change react-native-video to 1.0.0 and 'npm install'

RNV requires RN 0.40 or better. Please give 9bcf70c a shot instead. It contains some event bubbling fixes. If it does the trick for you it'll help justify #480 so please report back.

RNV requires RN 0.40 or better. Please give 9bcf70c a shot instead. It contains some event bubbling fixes. If it does the trick for you it'll help justify #480 so please report back.

I'm sorry em..how can i give 9bcf70c a shot instead

Pin the version in your package manifest. Others have done the same. Look through the issues for examples.

Please open a new issue if you are still having problems. We needed to do some housekeeping on issues. Thanks!

Video is not playing/buffering on Network-Connectivity changes. How to resolve this??


Add support for AWS Redshift based on Dasein Cloud Data Warehouse API

Dasein Cloud 2014.03 now supports a Data Warehouse (org.dasein.cloud.platform.bigdata.DataWarehouseSupport). Implement this to reflect AWS Redshift.

This issue was moved to dasein-cloud/dasein-cloud-aws#1


altFINS token

altFINS token submission

what was a problem with the pull request?

why was it closed?


Create an automated suite test with compiler checks

Create a nightly build/test with lib_c++ debug library and as many compiler debug checks enabled as possible.
https://clang.llvm.org/docs/SafeStack.html
https://blog.quarkslab.com/clang-hardening-cheat-sheet.html
Also investigate enabling safestack in all builds if overhead is as little as indicated.

In order to focus our efforts on issues that are currently creating difficulty for the community we are closing tickets that were created prior to the EOSIO 2.0 release.  If you believe this issue is still relevant please feel free to reopen it or create a new one.  Thank you for your continued support of EOSIO!


Added: Detect any folder deletion (rmdir) command.

#128

Thanks, @Geoff12889 for your contribution!


Create LICENSE

Don't want republicans using it but since Reach limits who they work with that takes care of the job for us

Don't want republicans using it but since Reach limits who they work with that takes care of the job for us


Add warning when metadata required by BIDS2NDA are missing

Pinging @yarikoptic, @mgxd, and @mtnhuck for comments.

Metadata required by the BIDS2NDA converter :

I wonder what other "popular" schemas besides image03 are used... May be abcd study used by other studies? Might be worth checking with NDA folks to get a better sense what fields might be needed, or may be bids validator could even get an option to validate for specific NDA schema (would require "integration" of that information with bids2nda)

All required fields in that screenshot are required.


Update ruby to latest

Up to 3.3.4

[ ] Divide version for certain env (staging, production) in Capistrano

requested changes
https://github.com/ita-social-projects/ZeroWaste/pull/899#pullrequestreview-2414838321

approved
https://github.com/ita-social-projects/ZeroWaste/pull/899


Ref #8: Added first draft of contributing guide

From a proof reader: Code of Conduct missing contact email. Going to add.


updateQuickTestStatus fails due to unsupported unicode character in RAT valueset

The current covid-19-lab-test-manufacturer-and-name valuset contains an entry with a unicode character from the "Halfwidth and Fullwidth" Forms  block.
The following entry has a fullwidth left and right paranthesis instead of a common left/right paranthesis:
"2139":{"display":"HANGZHOU LYSUN BIOTECHNOLOGY CO., LTD., COVID-19 Antigen Rapid Test Device（Colloidal Gold）" .......
During the creation of the first page of the PDF document, PDFbox throws an Exception because the characters are not available in the font:
2021-08-11 15:11:56.312Z ERROR 34648 --- [nio-8093-exec-6] a.c.q.controller.QuickTestController     : Temporary Error Log:U+FF08 ('parenleftmonospace') is not available in this font Helvetica encoding: WinAnsiEncoding
Entries in the valueset should use the common latin block U+0000 to U+007F.
Left Paranthesis expected character: U+0028 instead of U+FF08
Right Paranthesis expected character:  U+0029 instead of U+FF09

asked ehn dcc devs: https://github.com/ehn-dcc-development/ehn-dcc-schema/issues/122

fix in https://github.com/corona-warn-app/cwa-quick-test-backend/commit/4e2a3b9647dcf60ce3aff6619ebc07f7bd79cece
Issue still open while there is no answer from ehn dcc

Tested successfully on new deployment on WRU


Add empty method to CloneConfiguration API

Add new convenience method for empty object and use in CloneTestIT
Create private methods for sharing in TableOperationsImpl
Clean up on the CloneConfiguration interface

These changes were inspired by working on https://github.com/apache/accumulo/issues/2849

Merging this so I can continue working on #2849. If there is anymore feedback, I can do it as a follow on.


Permission to use the code in a MIT licensed project

Hi,
First, thanks for releasing the code.
May I have your permission to adapt the code in a MIT licensed project?
@bssrdf

yes, no problem


225 v4 spec directory not included in screenshot path

What are we fixing

When generating screenshots we were flattening test paths. If we had a structure like the one pointed out here we would run into errors.

more info about the reason behind this PR
This PR solves this problem and allows us to have any path depth in our test folder.

Also, we are fixing a use case facing on Cypress that looks like they are not going to fix it, as stated here

For some reason, Cypress saves the screenshots in a different folder when running in headless mode (cypress run), than running in browser mode (cypress open).
It will use the spec file name to build an extra folder in the path
ie:
[CORRECT] cypress open => .../snapshots/actual/cypress/e2e/alt-sub/foo/deep.cy.ts/inside_context.png
[INCORRECT] cypress run => .../snapshots/actual/deep.cy.ts/cypress/e2e/alt-sub/foo/deep.cy.ts/inside_context.png

Adding a simpler log system to use in node

@Zaista , can you do a NPM release?

@area73 hey, did you have a chance to take a look at the slack questions I raised regarding the PR?

@Zaista , sorry I miss your comments 😵💫 I answered you on the slack chanel

Where is the updated package on npm dist??

Hey @Colombo97 , this is going to be the next release (probably next week) V 5.0.1

Looks like the change to "type": "module" in commit 8ab83ce (#233) is breaking Cypress cypress.config.ts configs:

https://github.com/cypress-visual-regression/cypress-visual-regression/issues/243

This was the change from that commit:
   "name": "cypress-visual-regression",
   "version": "5.0.0",
   "description": "Module for adding visual regression testing to Cypress",
+  "type": "module",
   "keywords": [

Now there is no way to remove duplicating cypress in the path to snapshots, when they are located together with tests in cypress directory.

Before: cypress/snapshots/base/Foo.cy.js/<image>\
After: cypress/snapshots/base/cypress/visual/Foo/Foo.cy.js/<image>\

And it seems to be a breaking change - tests fails until snapshots are moved to a new location on a patch dependency bump.


Deploy The Graph for Matic Mainnet

It's live
https://thegraph.com/explorer/subgraph/augurproject/augur-turbo-matic


Introduce OpenFeature.Extensions.Hosting package

I'm eventually planning to offer this upstream as part of a new OpenFeature.Extensions.Hosting package à la OpenTelemetry.Extensions.Hosting, but still working through the realistic use cases and general ergonomics, but just mentioning that so this doesn't seem entirely irrelevant to the project at hand.

This has been suggested before, and I think it's a good idea. I would welcome such a PR, or at least an issue proposing it.

I'll open a new issue to track this, and will see about getting a draft PR put together over the next couple of weeks.

Originally posted by @austindrenski in https://github.com/open-feature/dotnet-sdk-contrib/issues/125#issuecomment-1881205608

Hey @kylejuliandev, @askpt is working on a draft PR. Feel free to review the PR and provide feedback.

Hello everyone,
At ServiceTitan, we're in the process of integrating OpenFeature with LaunchDarkly, and after reviewing this PR, I made some modifications to fit our needs due to time constraints. I created a new package, which we're currently using internally.
During this process, I rewrote certain sections and noticed that the dependency on "Hosting" seemed unnecessary. I've since separated the project into two packages: DependencyInjection and Hosting, and introduced the following interface in the DependencyInjection package:
/// <summary>
/// Defines the contract for managing the lifecycle of a feature API.
/// </summary>
public interface IFeatureLifecycleManager
{
    /// <summary>
    /// Ensures the feature provider is properly initialized and ready for use.
/// </summary>
/// <param name="cancellationToken">Cancellation token for the operation.</param>
/// <returns>A Task for the asynchronous initialization operation.</returns>
ValueTask EnsureInitializedAsync(CancellationToken cancellationToken = default);

/// <summary>
/// Gracefully shuts down the feature API.
/// </summary>
/// <param name="cancellationToken">Cancellation token for the operation.</param>
/// <returns>A Task for the asynchronous shutdown operation.</returns>
ValueTask ShutdownAsync(CancellationToken cancellationToken = default);
}

I’d love to share the full code and gather your feedback. If it aligns with the direction of OpenFeature, we can explore how to integrate it directly.

Thanks @arttonoyan !
Frankly, most of my experience in .NET dependency injection is based on older libraries, namely the Unity container. I'm not yet up-to-date on Microsoft.Extensions.Hosting OR Microsoft.Extensions.DependencyInjection. I'm trying to get up to speed as fast as possible on these, but @askpt, @kinyoklion and @lukas-reining might be more familiar than I am with them at the moment.
At the end of the day, I think we want:

ability to configure providers in a manner that's idiomatic to these packages (setting a provider for a particular domain, shutdown, etc)
ability to inject/locate a client for the domain in question
ability to inject a flag value in a request-scoped manner
convenience methods like the ones you've mentioned above
probably more

I'm not sure if it's necessary to use abstractions from both of these packages to accomplish the above - we may only need the DI package.
I think I speak for the other maintainers when we're open to suggestions here.

Thank you, @toddbaert, for your response.
It would certainly be ideal to have Dependency Injection (DI) directly implemented in the OpenFeature package. However, since that's not available at the moment, I believe it's important not to modify the core code just yet. For now, having a separate DI package makes integration easier and quicker without tightly coupling it to the main codebase. I've already implemented this approach with a separate package, though the specific name isn't important - it could be something like OpenFeature.DependencyInjection or OpenFeature.Extensions.DependencyInjection or somthing else.
A good reason for not merging the DI and Hosting packages is that Dependency Injection (DI) focuses on providing a mechanism to resolve services during application setup, which can be used independently of runtime environments. Moreover, DI and hosting are fundamentally different concerns. In many cases, teams might want to manage services separately, or there might be different hosting versions in use. In such cases, it would be better to have a separate package for DI, without forcing teams to adopt OpenFeature.Extensions.Hosting, which might be unnecessary. Both serve distinct purposes and should remain separate.
Also, in this case, we can add settings to configure the AddHostedFeatureLifecycle extension to run, for example, at "Starting," "Start," or "Started." Additionally, DI could be merged into the OpenFeature core source code in the future, and in that case, hosting would not be necessary - it should remain a separate package.
Anyway, this is just my opinion, and there may be better arguments for why Hosting should be included.
Currently, we are using the following packages, and many teams have already adopted this setup successfully:
dotnet add package ServiceTitan.Standalone.Platform.OpenFeature
dotnet add package ServiceTitan.Standalone.Platform.OpenFeature.Hosting
dotnet add package ServiceTitan.Standalone.Platform.OpenFeature.LaunchDarkly

Here is a simple Setup:
builder.Services.AddOpenFeature(featureBuilder => {
    featureBuilder
        .AddHostedFeatureLifecycle() // From Hosting package
        .AddContext((context, serviceProvider) => {
            // Context settings are applied here. Each feature flag evaluation will
            // automatically have access to these context parameters.
            // Do something with the service provider.
            context
                .Set("kind", "tenant")
                .Set("key", "<some key>")
        })
        .AddLaunchDarkly(builder.Configuration["LaunchDarkly:SdkKey"], cfg => cfg.StartWaitTime(TimeSpan.FromSeconds(10)));
});

This approach has worked well for us, and I believe it provides flexibility for teams that may want to keep DI and hosting concerns separate.

Thank you, @toddbaert, for your response.
It would certainly be ideal to have Dependency Injection (DI) directly implemented in the OpenFeature package. However, since that's not available at the moment, I believe it's important not to modify the core code just yet. For now, having a separate DI package makes integration easier and quicker without tightly coupling it to the main codebase. I've already implemented this approach with a separate package, though the specific name isn't important - it could be something like OpenFeature.DependencyInjection or OpenFeature.Extensions.DependencyInjection or somthing else.
A good reason for not merging the DI and Hosting packages is that Dependency Injection (DI) focuses on providing a mechanism to resolve services during application setup, which can be used independently of runtime environments. Moreover, DI and hosting are fundamentally different concerns. In many cases, teams might want to manage services separately, or there might be different hosting versions in use. In such cases, it would be better to have a separate package for DI, without forcing teams to adopt OpenFeature.Extensions.Hosting, which might be unnecessary. Both serve distinct purposes and should remain separate.
Also, in this case, we can add settings to configure the AddHostedFeatureLifecycle extension to run, for example, at "Starting," "Start," or "Started." Additionally, DI could be merged into the OpenFeature core source code in the future, and in that case, hosting would not be necessary - it should remain a separate package.
Anyway, this is just my opinion, and there may be better arguments for why Hosting should be included.
Currently, we are using the following packages, and many teams have already adopted this setup successfully:
dotnet add package ServiceTitan.Standalone.Platform.OpenFeature
dotnet add package ServiceTitan.Standalone.Platform.OpenFeature.Hosting
dotnet add package ServiceTitan.Standalone.Platform.OpenFeature.LaunchDarkly
Here is a simple Setup:
builder.Services.AddOpenFeature(featureBuilder => {
featureBuilder
.AddHostedFeatureLifecycle() // From Hosting package
.AddContext((context, serviceProvider) => {
// Context settings are applied here. Each feature flag evaluation will
// automatically have access to these context parameters.
// Do something with the service provider.
context
.Set("kind", "tenant")
.Set("key", "")
})
.AddLaunchDarkly(builder.Configuration["LaunchDarkly:SdkKey"], cfg => cfg.StartWaitTime(TimeSpan.FromSeconds(10)));
});
This approach has worked well for us, and I believe it provides flexibility for teams that may want to keep DI and hosting concerns separate.

@arttonoyan, I would be more than happy if you could add a PR for the DI implementation. At the moment, I am fighting the hosting one, but I think we can benefit more if you have a cleaner and ready approach. We could consider expanding your implementation later to all OpenFeature "configuration" requirements like multi-provider and hook/context per provider. At this point, having just a simple implementation and gradually adding more configuration settings is more beneficial.
I understand your points around hosting versus DI, and I fully agree with them.

Thanks, @askpt! I'll create the PR within the next two days. This is our first simple version, and it currently covers our needs. However, I believe that in the near future, we will require a multi-provider version to connect to different projects in LaunchDarkly (as each project has its own SDK key). We will also need to use event handling.
I also want to mention that you've done a lot of great work, which has been very helpful for me to get started-I’ve copied much of your logic.

Team! @askpt @toddbaert @kinyoklion @lukas-reining
I’ve created the #PR-310 that we previously discussed regarding the OpenFeature Dependency Injection and Hosting support. Could you kindly review it and share your feedback on the approach? I’m eager to hear your thoughts and suggestions to ensure we’re aligned before moving forward.


Post Error, Not Sure Why

Hi Norm
We are using 18.9 when I click on a button to open a specific form I get this error:

It doesn't seem to occur anywhere else (yet). When we open this form (same View) from somewhere else the error doesn't happen.
It points to this line of code:

On this form we use your ktl.views.waitSubmitOutcome(viewId), I don't think this is causing it though.
Craig

I bypassed the KTL and it didn't happen.
I went back to 18.2 it still happened

I can't really go back further than that due to other stuff breaking. This form is only a week old and we have never seen this before.

use your normal login and go here
https://arcproject.knack.com/arc-beta#admissions/client-funders/care-managers/?view_4825_filters=[]
then click Add New Funder
Then Add New Care  Manager here:

Craig

I found the problem.
In your form, you have 4 primary buttons. You must always have only one per form - the Submit button.

The code thinks that the first one is the Submit, so it submits the form when you click on it.
Then, since you have 3 required fields that are empty, the error 400 says "xyz are required."  You can see this if you examine the error's content as seen here:

So all you need to do is remove the ,is-primary class from the 3 buttons.
Norm

Hi Norm
Thanks for looking into this for us.
Ok we will remove this.  This is something we used to do and have since adopted for some unknown reason that we can't remember.  We have ended up using this across our app as we thought it provided the colour of the button.
Why doesn't it do it everywhere else including the other view which matched this one.  I'm not questioning the solution as this is an oversight on our part I'm just trying to understand as this was a convention we picked up 18 months ago when we didn't quite know as much as we do now.
Thanks for your time investigating this.
Craig

Your question is legitimate, indeed.
But it's very hard to tell without in-depth investigation by comparing both forms side-by-side.  Maybe it's just because the fields in the other forms are not required?
If you need to keep the color, just add another class to the buttons and use CSS.  Ex: .like-primary
But for sure, having only one primary button is a good practice, and will solve the problem.
I will close this issue now, if you see something else, feel free to re-open.
Cheers,
Norm

Ok thank you.


Update to Minecraft 1.17.1

Very similar PR to https://github.com/dzwdz/toomanybinds/pull/8, updates all around - there was only 1 breaking change with 1.17.
Changelog

update to Gradle 7.1.1, update wrapper files
update to Loom 0.8, Java 16
remove deprecated jcenter maven, add shedaniel's and TerraformersMC's maven
switch from old autoconfig1u and cloth:config-2 to new cloth-config-fabric (which contains the "new" Auto Config)
don't include Cloth Config

Cloth Config is huge and updates pretty often (people likely already have it too), it's better to add it as a requirement on CurseForge

fix getPreferredTarget mixin

The 2 shouldAttack() calls changed to Sensor.testAttackableTargetPredicateIgnoreVisibility() and Sensor.testAttackableTargetPredicate(), the latter being the correct one to target
And finally

bump version to 1.1.0

This version is probably compatible with 1.17 too, haven't tested but would be surprised if it wasn't.
Version 1.0.0 is most likely compatible up to 1.16.5.

Updated the README to reflect the Cloth Config requirement.


Restore hipchat token from previous session

Scenario:
1 - setup auth token in application & verify it is working
2 - close application
3 - reopen application
Expected: starting timer changes hipchat status to busy
Actual: no status change on hipchat + in configuration no token is restored
Note: chrome inspector for application local storage shows info is present

@fbiehl Fixed and closed.

@my8bit thanks!! :)


qbittorrent: fix login (POST) and add category

Login endpoint should be a POST
Add category filter

@DoubleGremlin181 Thoughts on this one?

Thanks for the ping. The current login logic works fine for me but I'll retest it with the changes over the weekend.

@matslina The changes don't break anything, should be good to merge. Thanks @noahpodgurski!


Improved E713 & E714 code examples

These felt reaaally weird seeing how the before/after code is completely changed. The weirdest part for me was E714 changing not x is y to not (x in y) 💀

Thanks! These might've come from pycodestyle originally in some way.


HTML Layout issues for logs

Describe the bug
When Ray displays Laravel log entries that contains html the layout of the Ray app breaks - while it works if the same HTML is send manually using the ray() method.
Versions

spatie/ray package version: 1.19.4
spatie/laravel-ray package version (if applicable): 1.12.6

PHP version: 7.4.3
Laravel version: 8.27.0
To Reproduce
Steps to reproduce the behavior:
Sending HTML to ray manually works perfect:
ray(Http::get('http://example.com')->body());

But logging the same html and sending logs to ray causes the layout to break:
Log::debug(Http::get('http://example.com')->body());

Expected behavior
The layout from normal log entries would be expected:
Log::debug('non-html-string')

Screenshots
See above
Desktop (please complete the following information):

OS: macOS
Version: 11.2.1

Additional context

I can reproduce this issue. We are working on a solution!


BTE no results Workflow A.9

https://github.com/NCATSTranslator/minihackathons/blob/main/2021-12_demo/workflowA/A.9_EGFR_advanced.json

{
  "logs": [
    {
      "code": null,
      "level": "DEBUG",
      "message": "BTE identified 2 QNodes from your query graph",
      "timestamp": "2021-08-12T15:57:38.952Z"
    },
    {
      "code": null,
      "level": "DEBUG",
      "message": "BTE identified 1 QEdges from your query graph",
      "timestamp": "2021-08-12T15:57:38.953Z"
    },
    {
      "code": null,
      "level": "DEBUG",
      "message": "BTE identified your query graph as a 1-depth query graph",
      "timestamp": "2021-08-12T15:57:38.953Z"
    },
    {
      "code": null,
      "level": "DEBUG",
      "message": "REDIS cache is not enabled.",
      "timestamp": "2021-08-12T15:57:39.057Z"
    },
    {
      "code": null,
      "level": "DEBUG",
      "message": "BTE is trying to find SmartAPI edges connecting from OrganismTaxon,Event,AdministrativeEntity,Agent,InformationContentEntity,Dataset,DatasetDistribution,DatasetVersion,DatasetSummary,ConfidenceLevel,EvidenceType,InformationResource,Publication,Book,BookChapter,Serial,Article,PhysicalEntity,MaterialSample,Activity,Procedure,Phenomenon,Device,PlanetaryEntity,EnvironmentalProcess,EnvironmentalFeature,GeographicLocation,GeographicLocationAtTime,BiologicalEntity,BiologicalProcessOrActivity,MolecularActivity,BiologicalProcess,Pathway,PhysiologicalProcess,Behavior,Death,PathologicalProcess,OrganismalEntity,LifeStage,IndividualOrganism,Case,PopulationOfIndividualOrganisms,StudyPopulation,Cohort,AnatomicalEntity,CellularComponent,Cell,GrossAnatomicalStructure,PathologicalAnatomicalStructure,CellLine,DiseaseOrPhenotypicFeature,Disease,PhenotypicFeature,BehavioralFeature,ClinicalFinding,Gene,Genome,Polypeptide,Protein,ProteinIsoform,GeneFamily,Genotype,Haplotype,SequenceVariant,Snv,ReagentTargetedGene,ChemicalEntity,MolecularEntity,SmallMolecule,NucleicAcidEntity,Exon,Transcript,RnaProduct,RnaProductIsoform,NoncodingRnaProduct,MicroRna,SiRna,CodingSequence,ChemicalMixture,MolecularMixture,Drug,ComplexMolecularMixture,ProcessedMaterial,Food,EnvironmentalFoodContaminant,FoodAdditive,Nutrient,Macronutrient,Micronutrient,Vitamin,ClinicalEntity,ClinicalTrial,ClinicalIntervention,Hospitalization,Treatment,NamedThing to SmallMolecule with predicate undefined",
      "timestamp": "2021-08-12T15:57:39.059Z"
    },
    {
      "code": null,
      "level": "DEBUG",
      "message": "BTE found 171 smartapi edges corresponding to e0. These smartaip edges comes from 11 unique APIs. They are MyDisease.info API,MyVariant.info API,SEMMED Disease API,SEMMED Gene API,SEMMED Chemical API,SEMMED Biological Process API,MyChem.info API,Text Mining Targeted Association API,BioThings DGIdb API,Multiomics Wellness KP API,Clinical Risk KP API",
      "timestamp": "2021-08-12T15:57:39.093Z"
    },
    {
      "code": null,
      "level": "DEBUG",
      "message": "BTE found 14 bte edges for this batch.",
      "timestamp": "2021-08-12T15:57:39.142Z"
    },
    {
      "code": null,
      "level": "DEBUG",
      "message": "call-apis: Resolving ID feature is turned on",
      "timestamp": "2021-08-12T15:57:39.142Z"
    },
    {
      "code": null,
      "level": "DEBUG",
      "message": "call-apis: Number of BTE Edges received is 14",
      "timestamp": "2021-08-12T15:57:39.142Z"
    },
    {
      "code": null,
      "level": "DEBUG",
      "message": "call-apis: Succesfully made the following query: {\"url\":\"https://biothings.ncats.io/semmedgene/query\",\"params\":{\"fields\":\"affected_by\"},\"data\":\"q=C1414313&scopes=umls\",\"method\":\"post\",\"timeout\":50000}",
      "timestamp": "2021-08-12T15:57:39.187Z"
    },
    {
      "code": null,
      "level": "DEBUG",
      "message": "call-apis: After transformation, BTE is able to retrieve 0 hits!",
      "timestamp": "2021-08-12T15:57:39.187Z"
    },
    {
      "code": null,
      "level": "DEBUG",
      "message": "call-apis: Succesfully made the following query: {\"url\":\"https://mychem.info/v1/query\",\"params\":{\"fields\":\"drugbank.id\",\"size\":\"1000\"},\"data\":\"q=EGFR&scopes=drugbank.enzymes.gene_name\",\"method\":\"post\",\"timeout\":50000}",
      "timestamp": "2021-08-12T15:57:39.197Z"
    },
    {
      "code": null,
      "level": "DEBUG",
      "message": "call-apis: After transformation, BTE is able to retrieve 0 hits!",
      "timestamp": "2021-08-12T15:57:39.197Z"
    },
    {
      "code": null,
      "level": "DEBUG",
      "message": "call-apis: Succesfully made the following query: {\"url\":\"https://biothings.ncats.io/semmedgene/query\",\"params\":{\"fields\":\"affects\"},\"data\":\"q=C1414313&scopes=umls\",\"method\":\"post\",\"timeout\":50000}",
      "timestamp": "2021-08-12T15:57:39.214Z"
    },
    {
      "code": null,
      "level": "DEBUG",
      "message": "call-apis: After transformation, BTE is able to retrieve 0 hits!",
      "timestamp": "2021-08-12T15:57:39.214Z"
    },
    {
      "code": null,
      "level": "DEBUG",
      "message": "call-apis: Succesfully made the following query: {\"url\":\"https://biothings.ncats.io/semmedgene/query\",\"params\":{\"fields\":\"disrupted_by\"},\"data\":\"q=C1414313&scopes=umls\",\"method\":\"post\",\"timeout\":50000}",
      "timestamp": "2021-08-12T15:57:39.247Z"
    },
    {
      "code": null,
      "level": "DEBUG",
      "message": "call-apis: After transformation, BTE is able to retrieve 0 hits!",
      "timestamp": "2021-08-12T15:57:39.247Z"
    },
    {
      "code": null,
      "level": "DEBUG",
      "message": "call-apis: Succesfully made the following query: {\"url\":\"https://biothings.ncats.io/dgidb/query\",\"params\":{\"fields\":\"object.CHEMBL_COMPOUND,association\",\"size\":1000},\"data\":\"q=1956&scopes=subject.NCBIGene\",\"method\":\"post\",\"timeout\":50000}",
      "timestamp": "2021-08-12T15:57:39.287Z"
    },
    {
      "code": null,
      "level": "DEBUG",
      "message": "call-apis: After transformation, BTE is able to retrieve 456 hits!",
      "timestamp": "2021-08-12T15:57:39.727Z"
    },
    {
      "code": null,
      "level": "DEBUG",
      "message": "call-apis: Succesfully made the following query: {\"url\":\"https://mychem.info/v1/query\",\"params\":{\"fields\":\"drugbank.id\",\"size\":\"1000\"},\"data\":\"q=EGFR&scopes=drugbank.targets.gene_name\",\"method\":\"post\",\"timeout\":50000}",
      "timestamp": "2021-08-12T15:57:39.730Z"
    },
    {
      "code": null,
      "level": "DEBUG",
      "message": "call-apis: After transformation, BTE is able to retrieve 30 hits!",
      "timestamp": "2021-08-12T15:57:39.743Z"
    },
    {
      "code": null,
      "level": "DEBUG",
      "message": "call-apis: Succesfully made the following query: {\"url\":\"https://mychem.info/v1/query\",\"params\":{\"fields\":\"drugcentral.xrefs.chembl_id\",\"size\":\"1000\"},\"data\":\"q=EGFR&scopes=drugcentral.bioactivity.uniprot.gene_symbol\",\"method\":\"post\",\"timeout\":50000}",
      "timestamp": "2021-08-12T15:57:39.744Z"
    },
    {
      "code": null,
      "level": "DEBUG",
      "message": "call-apis: After transformation, BTE is able to retrieve 90 hits!",
      "timestamp": "2021-08-12T15:57:39.782Z"
    },
    {
      "code": null,
      "level": "DEBUG",
      "message": "call-apis: Succesfully made the following query: {\"url\":\"https://biothings.ncats.io/semmedgene/query\",\"params\":{\"fields\":\"disrupts\"},\"data\":\"q=C1414313&scopes=umls\",\"method\":\"post\",\"timeout\":50000}",
      "timestamp": "2021-08-12T15:57:39.812Z"
    },
    {
      "code": null,
      "level": "DEBUG",
      "message": "call-apis: After transformation, BTE is able to retrieve 0 hits!",
      "timestamp": "2021-08-12T15:57:39.813Z"
    },
    {
      "code": null,
      "level": "DEBUG",
      "message": "call-apis: Succesfully made the following query: {\"url\":\"https://biothings.ncats.io/semmedgene/query\",\"params\":{\"fields\":\"negatively_regulated_by\"},\"data\":\"q=C1414313&scopes=umls\",\"method\":\"post\",\"timeout\":50000}",
      "timestamp": "2021-08-12T15:57:39.844Z"
    },
    {
      "code": null,
      "level": "DEBUG",
      "message": "call-apis: After transformation, BTE is able to retrieve 0 hits!",
      "timestamp": "2021-08-12T15:57:39.844Z"
    },
    {
      "code": null,
      "level": "DEBUG",
      "message": "call-apis: Succesfully made the following query: {\"url\":\"https://biothings.ncats.io/semmedgene/query\",\"params\":{\"fields\":\"negatively_regulates\"},\"data\":\"q=C1414313&scopes=umls\",\"method\":\"post\",\"timeout\":50000}",
      "timestamp": "2021-08-12T15:57:39.865Z"
    },
    {
      "code": null,
      "level": "DEBUG",
      "message": "call-apis: After transformation, BTE is able to retrieve 0 hits!",
      "timestamp": "2021-08-12T15:57:39.865Z"
    },
    {
      "code": null,
      "level": "DEBUG",
      "message": "call-apis: Succesfully made the following query: {\"url\":\"https://biothings.ncats.io/semmedgene/query\",\"params\":{\"fields\":\"physically_interacts_with\"},\"data\":\"q=C1414313&scopes=umls\",\"method\":\"post\",\"timeout\":50000}",
      "timestamp": "2021-08-12T15:57:39.923Z"
    },
    {
      "code": null,
      "level": "DEBUG",
      "message": "call-apis: After transformation, BTE is able to retrieve 0 hits!",
      "timestamp": "2021-08-12T15:57:39.923Z"
    },
    {
      "code": null,
      "level": "DEBUG",
      "message": "call-apis: Succesfully made the following query: {\"url\":\"https://biothings.ncats.io/semmedgene/query\",\"params\":{\"fields\":\"positively_regulated_by\"},\"data\":\"q=C1414313&scopes=umls\",\"method\":\"post\",\"timeout\":50000}",
      "timestamp": "2021-08-12T15:57:39.953Z"
    },
    {
      "code": null,
      "level": "DEBUG",
      "message": "call-apis: After transformation, BTE is able to retrieve 0 hits!",
      "timestamp": "2021-08-12T15:57:39.953Z"
    },
    {
      "code": null,
      "level": "DEBUG",
      "message": "call-apis: Succesfully made the following query: {\"url\":\"https://biothings.ncats.io/semmedgene/query\",\"params\":{\"fields\":\"positively_regulates\"},\"data\":\"q=C1414313&scopes=umls\",\"method\":\"post\",\"timeout\":50000}",
      "timestamp": "2021-08-12T15:57:39.977Z"
    },
    {
      "code": null,
      "level": "DEBUG",
      "message": "call-apis: After transformation, BTE is able to retrieve 0 hits!",
      "timestamp": "2021-08-12T15:57:39.977Z"
    },
    {
      "code": null,
      "level": "DEBUG",
      "message": "call-apis: Succesfully made the following query: {\"url\":\"https://biothings.ncats.io/semmedgene/query\",\"params\":{\"fields\":\"related_to\"},\"data\":\"q=C1414313&scopes=umls\",\"method\":\"post\",\"timeout\":50000}",
      "timestamp": "2021-08-12T15:57:40.021Z"
    },
    {
      "code": null,
      "level": "DEBUG",
      "message": "call-apis: After transformation, BTE is able to retrieve 0 hits!",
      "timestamp": "2021-08-12T15:57:40.021Z"
    },
    {
      "code": null,
      "level": "DEBUG",
      "message": "call-apis: Total number of results returned for this query is 576",
      "timestamp": "2021-08-12T15:57:40.022Z"
    },
    {
      "code": null,
      "level": "DEBUG",
      "message": "call-apis: Query completes",
      "timestamp": "2021-08-12T15:57:40.906Z"
    },
    {
      "code": null,
      "level": "DEBUG",
      "message": "query_graph_handler: Post-query predicate restrictions: [\"abundance_decreased_by\",\"activity_decreased_by\",\"expression_decreased_by\",\"synthesis_decreased_by\",\"degradation_increased_by\",\"disrupted_by\",\"entity_negatively_regulated_by_entity\"].",
      "timestamp": "2021-08-12T15:57:40.909Z"
    },
    {
      "code": null,
      "level": "DEBUG",
      "message": "query_graph_handler: Successfully applied post-query predicate restriction: 576 down to 0 results.",
      "timestamp": "2021-08-12T15:57:40.909Z"
    }
  ],
  "message": {
    "knowledge_graph": {
      "edges": {},
      "nodes": {}
    },
    "query_graph": {
      "edges": {
        "e0": {
          "object": "n1",
          "predicates": [
            "biolink:decreases_abundance_of",
            "biolink:decreases_activity_of",
            "biolink:decreases_expression_of",
            "biolink:decreases_synthesis_of",
            "biolink:increases_degradation_of",
            "biolink:disrupts",
            "biolink:entity_negatively_regulates_entity"
          ],
          "subject": "n0"
        }
      },
      "nodes": {
        "n0": {
          "categories": [
            "biolink:SmallMolecule"
          ],
          "constraints": [
            {
              "id": "biolink:highest_FDA_approval_status",
              "name": "highest FDA approval status",
              "operator": "==",
              "value": "regular approval"
            }
          ],
          "name": "Small Molecule"
        },
        "n1": {
          "ids": [
            "NCBIGene:1956"
          ],
          "name": "EGFR"
        }
      }
    },
    "results": []
  },
  "validation_result": {
    "message": "",
    "n_edges": 0,
    "n_nodes": 0,
    "provenance_summary": {
      "n_sources": 0,
      "predicate_counts": {},
      "provenance_counts": {}
    },
    "size": "15 kB",
    "status": "PASS",
    "version": "1.1.1"
  },
  "workflow": [
    {
      "id": "lookup"
    }
  ],
  "araxui_provider": "ARS",
  "araxui_response": "e4286769-39e7-48ea-bf5d-d1a76b39894b"
}

Results https://arax.ncats.io/?source=ARS&id=c9c02a08-5574-45e2-836c-cf16f95fa964


Request from Mugi Purwokerto Indonesia

I am an organizer from Indonesia. Last year we also organize this event. Please approve our request. Thank you

Great work @agussuparno !

Thank you so much
Get Outlook for Androidhttps://aka.ms/AAb9ysg

From: Magnus Mårtensson @.>
Sent: Wednesday, March 8, 2023 4:33:47 PM
To: globalazure/communities @.>
Cc: Agus Suparno @.>; Mention @.>
Subject: Re: [globalazure/communities] Request from Mugi Purwokerto Indonesia (PR #156)
Merged #156https://github.com/globalazure/communities/pull/156 into main.
—
Reply to this email directly, view it on GitHubhttps://github.com/globalazure/communities/pull/156#event-8694691979, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ACH5ZWHPY5LZYFC6AV7LJGDW3BG7XANCNFSM6AAAAAAVRS73OI.
You are receiving this because you were mentioned.Message ID: @.***>


date-fns versions questions

Hi,
I've upgraded to latest version v1.0.0-rc.14 then I noticed that nothing was formatted correctly. Years displayed as yyyy strings instead of actual years, etc.
There is clearly stated in release notes that update was done to<EMAIL_ADDRESS>which caused the break. I've used utils/date-fns-utils-old and all is good.
However, my question is the following. I'm using "date-fns": "2.0.0-alpha.7" meaning it is compatible with the old version but seems like version 2 of date-fns is newer than the 1? Are there any plans in using version 2?

I have similar issue.
I have updated to<EMAIL_ADDRESS>assuming that what is stated in the release notes is a typo.
But still I get multiple errors with the following pattern:
./node_modules/date-fns/locale/{langCode}/_lib/localize/index.js
Module not found: Can't resolve '../../../_lib/buildLocalizeArrayFn/index.js' in '.../node_modules/date-fns/locale/{langCode}/_lib/localize'

I am using utils/date-fns-utils-old for now.

NOTE
I am loading dynamically the locales with something like this:
import(`date-fns/locale/${iso639LangCode}`)

😮 The update was done to date-fns 2-alpha.14
That seems to be a typo in release notes


Wrapper API created

In first place apologies for taking so long. I had to catch up on jest and typescript and as I said, I have to do this on my spare time.
I've created de wrapper API and I think this is what you were looking for but please let me know if I'm wrong.
The second thing I wanted to discuss is testing. I've read that the tests shouldn't hit the API. In that case I really don't know what to do to test it because in my point of view that's the only thing the program does.
Thank for your patience!

In first place apologies for taking so long. I had to catch up on jest and typescript and as I said, I have to do this on my spare time.
I've created de wrapper API and I think this is what you were looking for but please let me know if I'm wrong.
The second thing I wanted to discuss is testing. I've read that the tests shouldn't hit the API. In that case I really don't know what to do to test it because in my point of view that's the only thing the program does.
Thank for your patience!

Great and thanks for the PR!
There are multiple ways we could test the API. I made the constructor allow override of baseUrl. This way we can host a temporary http server with integration testing. But we should also have the ability to run tests against the deployed APIs.

Here is a good example where you could follow DRY (Don't Repeat Yourself):

Most of this code is the same, so you could optimize it a bit by having an "executeGet" method that takes the relative URL, and perhaps some other parameters, depending on what you need.

Thanks for the quick response.
I'm reviewing it now.
First of all I will make the code more concise.
After that

Thanks for the quick response.
I'm reviewing it now.
First of all I will make the code more concise.
After that I will make the tests that actually hits the API as you said.

Closes #1


Fix backend version publish bug

Requirements

Filling out the template is required.

All new code requires tests to ensure against regressions.

However, if your PR contains zero code changes, feel free to select the checkmark below to indicate so.

[ ] Have you ran tests against this code?

[ ] This PR contains zero code changes.

Description of the Change
Addressing errors in prod

Considering these fixes are already in prod, I'll go ahead and merge this one


Make installer portable.

I was unsure if this modpack installer is really requiring the user to install the modpack installer with admin privileges.
If possible, the exacutable could either allow you to either launch straight to the main screen without install or something similar.

It should be really easy to add back a portable zipped executable, will do soon

Ok just as an update, it's a little annoying because I need to package both exe installer and portable on one platform so I need to dig around configs and hop on Windows for a bit. I probably wont finish this as fast haha :p


Setup mysql tables by default

hey, it seems like during first launch even if I create table in mysql manually they does not work. Do you have some database dump that I can use to setup the app initially?

need for those 3 tables, not sure how they are named

resolved, had to run "manage.py migrate"

also, I had a typo. NVM


Any way to remove delay for "fetching data" ?

Im really worried after some update.
It started showing "Data is stale. Fetching again in 5s... Now?"  Any way to remove this function and/or make it automatically search without 5second delay?
Literally all people i knew already stopped using that program cuz 5+ second searches are annoying.

Hi, thanks for creating an issue. This is an intended behavior. Please see #426. There is also an screenshot of the setting you need to change in order to fix this.


Correctly handle presence of multiple plans with the same name

...when looking up the service plan for an instance.
Fixes #1292

Test case to make sure this fails appropriately?

I can confirm this fixes the error I was seeing and the service provisions successfully.
serviceClassRef and servicePlanRef are still not being set on the instance, but @pmorie mentioned that's another known problem.

Could we hold off on this I'll add these to my changes (wrt. setting Service[Plan|Class]Ref). PR coming very shortly.

This has been incorporated into #1305


fetch using topic id

Hello,
I'm trying to use the franz go kafka client to consume records from a source cluster. I'm using a direct consumer, because the workload is to consume a list of arbitrary (topic id, partition id, offset) periodically.
I'm trying to achieve this by keeping a single client alive. When it receives the list of (topic id, partition id, offset) to consume from, it performs remove consume topic partitions using RemoveConsumePartitions or even PurgeTopicsFromClient, and adds the new consume topic partitions using AddConsumePartitions.
However, the above APIs use the topic name string and not the topic ids. I think I can make my use case of ensuring I'm fetching from the correct topic work if the FetchTopic struct also has the topic id in it and it's returned from the PollRecords function with the topic ids also set.
I think it's possible to do this by:

Adding topic id field to FetchTopic.
Adding a config to indicate that the topic id should be set in FetchTopic.
Setting the topic id in the FetchTopic upon fetches(I think this is possible for request versions >= 13?)

What do you think? If you're open to this, then I can implement this.

I'm on board, though I'd skip (2).
I think this is the full patch:
diff --git a/pkg/kgo/record_and_fetch.go b/pkg/kgo/record_and_fetch.go
index 4f1ebe6f..55315644 100644
--- a/pkg/kgo/record_and_fetch.go
+++ b/pkg/kgo/record_and_fetch.go
@@ -274,6 +274,8 @@ func (p *FetchPartition) EachRecord(fn func(*Record)) {
 type FetchTopic struct {
 	// Topic is the topic this is for.
 	Topic string
+	// TopicID is the ID of the topic, if your cluster supports topic IDs.
+	TopicID [16]byte
 	// Partitions contains individual partitions in the topic that were
 	// fetched.
 	Partitions []FetchPartition
@@ -560,6 +562,7 @@ func (fs Fetches) EachTopic(fn func(FetchTopic)) {
 	for topic, partitions := range topics {
 		fn(FetchTopic{
 			topic,
+			[16]byte{},
 			partitions,
 		})
 	}
diff --git a/pkg/kgo/source.go b/pkg/kgo/source.go
index 7a55ef0c..cddb4189 100644
--- a/pkg/kgo/source.go
+++ b/pkg/kgo/source.go
@@ -979,6 +979,7 @@ func (s *source) handleReqResp(br *broker, req *fetchRequest, resp *kmsg.FetchRe

 		fetchTopic := FetchTopic{
 			Topic:      topic,
+			TopicID:    rt.TopicID,
 			Partitions: make([]FetchPartition, 0, len(rt.Partitions)),
 		}

I can push this after I cut a patch release. There aren't many new features at the moment, so I may wait on releasing this for a little bit -- is that alright? (potentially a month?)

I was burned in the past by merging a feature then having to revert it to issue a quick bugfix release; if you're open to using the branch for now, please do that 😅
I'll leave this issue open, it'll be closed once I merge the PR -- which I'll do right as I'm about to cut a release.


I miss "axmol\build.ps1" is it no longer needed?

axmol version: latest

it's was moved to tools/cmdline

see: 2.1.3 changelog at section Break Changes


MacOS: Cmd+[A|X|C|V] commands do not work

Ctrl+[A|X|C|V] should be used instead, which is quite annoying.

Note: Cmd button works on Mac L&F, could make it work on Metal as well


如何才能安装依赖程序pip install -r requirements.txt

Last login: Mon Jan  1 03:24:31 on ttys000
Cdq-Pro:~ cdq$ pip install -r requirements.txt
Could not open requirements file: [Errno 2] No such file or directory: 'requirements.txt'
Cdq-Pro:~ cdq$

运行pip需要在requirements.txt的路径下，否则找不到

推荐小白用这个https://github.com/hakrtt/wechatgame

Last login: Mon Jan  1 08:25:12 on console
Cdq-Pro:~ cdq$ pip install -r requirements.txt
Requirement already satisfied: backports.functools-lru-cache==1.4 in ./anaconda3/lib/python3.6/site-packages (from -r requirements.txt (line 1))
Requirement already satisfied: cycler==0.10.0 in ./anaconda3/lib/python3.6/site-packages (from -r requirements.txt (line 2))
Requirement already satisfied: matplotlib==2.1.1 in ./anaconda3/lib/python3.6/site-packages (from -r requirements.txt (line 3))
Requirement already satisfied: numpy==1.13.3 in ./anaconda3/lib/python3.6/site-packages (from -r requirements.txt (line 4))
Requirement already satisfied: olefile==0.44 in ./anaconda3/lib/python3.6/site-packages (from -r requirements.txt (line 5))
Requirement already satisfied: opencv-python==<IP_ADDRESS> in ./anaconda3/lib/python3.6/site-packages (from -r requirements.txt (line 6))
Requirement already satisfied: Pillow==4.3.0 in ./anaconda3/lib/python3.6/site-packages (from -r requirements.txt (line 7))
Requirement already satisfied: pyparsing==2.2.0 in ./anaconda3/lib/python3.6/site-packages (from -r requirements.txt (line 8))
Requirement already satisfied: python-dateutil==2.6.1 in ./anaconda3/lib/python3.6/site-packages (from -r requirements.txt (line 9))
Requirement already satisfied: pytz==2017.3 in ./anaconda3/lib/python3.6/site-packages (from -r requirements.txt (line 10))
Requirement already satisfied: six==1.11.0 in ./anaconda3/lib/python3.6/site-packages (from -r requirements.txt (line 11))
Cdq-Pro:~ cdq$
谢谢,目前是这个情况,是正确还是错误?

@soysaucemo requirements.txt的路径在哪里？这个text在哪里能下载呢？

作者的文件不是UTF-8编码，改为UTF-8

先cd到你下载的文件路径下


[AutoPR datamigration/resource-manager] typo: Microsoft.DataMigration

Created to sync https://github.com/Azure/azure-rest-api-specs/pull/4681

This PR has been merged into https://github.com/Azure/azure-sdk-for-go/pull/3514


Django 4.0 warnings

Describe the bug
In Django 4.0 apps do not need to declare a default_app_config in the init.py file.
To Reproduce
Steps to reproduce the behavior:

Add scheduler to your INSTALLED_APPS

Expected behavior
No warnings when the project runs

It's a really easy fix but this project doesn't allow PRs

It's a really easy fix but this project doesn't allow PRs

Hi, apologies, I didn't realize the repo does not allow PRs, can you try now?


Install>Configuration needs to reference z/OSMF JWT setup

Somewhere under https://docs.zowe.org/stable/user-guide/configure-zos-system please add a small section which indicates the need to enable JWT in z/OSMF as documented here: https://www.ibm.com/docs/en/zos/2.5.0?topic=configurations-enabling-json-web-token-support. JWT is not enabled in z/OSMF by default.
Also, the z/OSMF doc says the server_override.xml ought to be OK as supplied, but that is only true if z/OSMF is using the default certificate name DefaultzOSMFCert.IZUDFLT. If z/OSMF has been configured to use a different certificate, the element keyAlias in the server_override.xml must be changed to the label of the IZUSVR1's personal certificate.
Also consider updating the Action information in message ZWEAG187W to include a reference to https://www.ibm.com/docs/en/zos/2.5.0?topic=configurations-enabling-json-web-token-support

Thank you for pointing it out.I will take a look on this.


Is HTTP custom data not supported?

Hi,
I am trying to integrate my own custom data into a custom XYZ layer. The data itself is not secured and I usually approach it this way (just for an example):
http://<IP_ADDRESS>:6062/BaseMap/TextureTiles/11/822/1218.jpg It won't load for some reason.
However, the same data is loaded, just when it is secured:
https://aws.XXXXXXXXX.com/BaseMap/TextureTiles/11/822/1218.jpg
Does loading http custom layers have any limitations?

AFAIK Mapbox GL JS / Maplibre GL JS does not support fetching data via http

These tiles look like they're coming from your local network, so I can't test this fully, but the initial reason why this isn't working is because Google Chrome blocks mixed content, and this is mixed content - play.placemark.io is HTTPS, and those tiles are HTTP.
If you go to site settings, and Allow insecure content, Chrome will load the tiles ( https://stackoverflow.com/questions/18321032/how-to-get-chrome-to-allow-mixed-content ) but I can't totally confirm that GL JS will display them.

Yep, you are right. Testing was done using Edge browser (that was a mistake), with Chrome browser it worked right out of the box.

Great, closing this out then - these browser restrictions would be hard to fix at the application level.


Add evicted field to ValidatorStatistic

Since we can set the validator power only once.
We need to add a new flag to ValidatorStatistic.
ref : https://github.com/loomnetwork/loomchain/issues/1612

We've opted for an alternative implementation that doesn't require changing the protobufs, so this is no longer needed.


Incorrect return of Datepart function

hi,
we have issues while running "datepart" function. I found in your code such line:
<formula part='weekday'>toDayOfWeek(%2) mod 7 + 1</formula>
Why do you add this 7+1?
I have tried to run this directly on clickhouse:
select toDayOfWeek(  toDate('2022-12-19')) mod 7 + 1
And it returns 2 where December 19 is Monday.

Hi @vlauzeckas
Tableau interprets 1 as Sunday (hence 2 as Monday) etc.

as i understand it is configurable on data source level in tableau:

currently if i configure that my  week starts on Monday i get wrong results

Could you please explain what the "wrong results" are?

@vlauzeckas  fyi:
both DATEPART('weekday', #2022-12-19#)
and DATEPART('weekday', #2022-12-19#, 'monday')
do always return 2.

ghmm, actually you are right. i have tested with postgresl and it behaves similarly


ENH: look at success state of status objects

This is a proof-of-concept commit.
This relies on @klauer refactoring of the status objects.

This effectively special-cases failure to move over other kinds of exceptions that can bubble up from ophyd. I'm not 100% convinced that it needs to be special-cased.

This catches async failures, the rest of them come up synchronously in the co-routines.   I think this is the only way to make sure that the exceptions BS needs come up on the correct threads / co-routines.
There are some epi-cycles with self._task.cancel() that I do not fully have pinned down.
Not sure what you mean by special casing failure to move, this also deals with trigger and kickoff failures (in the same way).

I meant that is special cases a certain kind of failure coming up from the device layer. My impulse would be to just use exceptions. I see the success bit as something that debuggers will want and plans might use (to decide if it's important that something failed to move) but that the RunEngine doesn't need to know about.

I think this is the only way to make sure that the exceptions BS needs come up on the correct threads / co-routines.

If that's true though, my point is moot.


shotwell: 0.27.0 -> 0.27.1

Motivation for this change
Update shotwell to the last version
https://git.gnome.org/browse/shotwell/diff/NEWS?id=eed20d153fe8d6959947191aa9a99e060c36280b
Things done

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

[X] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[X] Tested execution of all binary files (usually in ./result/bin/)
[X] Fits CONTRIBUTING.md.

Thanks!


initial commit lstm train, forecast

hey Jake - here is a skeleton of how I think this could work. I haven't fixed any of the file paths, so those will need to be fixed. I was prototyping with everything in one folder. I will also need to plugin the model prep code for completeness.
the train code trains the model and saves the model weights and the final states.
the predict/update code reads in the final states saved by the train script, runs a prediction, then adjusts the weights and does the prediction again. I guess the part we are missing there is the reading the states after the initial prediction, but that should be easy to put in.

awesome thanks Jeff! looks great


Auto-create gallery for mass-uploaded photos

Gallery should be automatically created when adding photos by mass upload.

This issue looks little redundant when you consider that #27 does really the same thing only from different point of view. I think, it can be closed.

Would be nice if someone confirmed we can close this.

I don't think this and #27 are the same thing. In #27's scenario, you already have a gallery. Here, you just upload photos.

Don't think so. You can easily do the same by adding blank gallery and in photo selection just trigger mass upload and photos will be created.

Ok, let's discuss it on Monday meeting, so I can understand this issue more from product point of view. Than we decide to close or update issue.

So we finally agreed that the current mass-upload possibilities are satisfying and this issue can be therfore closed.


Get thumbnailphoto from AD

Hi,
I wonder how get thumbnailphoto from AD ? I tried many ways more could not.
help please. :+1:

https://github.com/Adldap2/Adldap2/blob/v5.2/src/Models/User.php#L667
$user = Adldap::users()->find('jdoe');

$photo = $user->getThumbnailPhoto();

I did it this way:
`$user = Adldap::users()->find(Auth::user()->username);
    $photo = $user->thumbnailphoto;

   // dd($photo);

    return view('home', compact('photo'));`

more returned me an error.
htmlentities() expects parameter 1 to be string, array given

Try:
$photo = $user->getThumbnailEncoded();

How to fix Call to a member function getThumbnailEncoded() on null if user haven't thumb?

Hi @ilyadavydyuk, it sounds like you're trying to call getThumbnailEncoded() on null. You wouldn't receive this error if an actual user instance is returned.


missing import statements

the "import logging" module is missing. Incase anybody is stuck with the issue. Please add "import logging" on the memrepl.py file.

Hello @droidresearch thanks for the bugreport. I've pushed the requested changes.
Thanks again.

Thank you.


Update Q&A Booklets

Correct erroneous line number.

This looks old. Do you want me to approve it so you can merge?

@speedy1812 No, this one needs help. It should probably be declined, but I haven't done so because it contains some correction info that I might need. 😄


Document using OhDear's Cron Monitoring

[x] https://github.com/zenstruck/schedule-bundle/blob/master/doc/define-tasks.md#pingtask
[x] https://github.com/zenstruck/schedule-bundle/blob/master/doc/define-tasks.md#ping-webhook
[x] https://github.com/zenstruck/schedule-bundle/blob/master/doc/define-schedule.md#ping-webhook
[x] https://github.com/zenstruck/schedule-bundle/blob/master/doc/run-schedule.md#ensuring-the-schedule-is-running

Closed via 6445da4fd56ea3711aab01bf82a060e5d38e49ed.


Hello, I am a beginner in Python

Hello, I am a beginner in Python. I am studying hard on the code that I really need. There are several python files (utils.py, constant.py, extract.py, mapper.py, stats,py). What order should they be executed? I would really appreciate it if you let me know

I executed extract.py first and got *.jsonl file, than assume I should execute process.py?
It would be great if a high-level walkthrough could be provided.


Update generate-current-manifests.yml

I have written an action that generates a PR using the corresponding action on the GitHub Actions marketplace.  Notable parts:

This creates a branch called 'update-manifests' which will contains the changes to the manifests
This is automatically generated and is a different branch from the one which the PR is generated
It is set to delete so that a branch with the same name can be safely created with each workflow run

Future ideas:

Refactor generate-current-manifests.yml to avoid hitting branch protection and limit manual intervention/duplicative PR review
Refactor generate-current-manifests.yml to only regenerate manifests for which the corresponding Excel files have actually been changed in the commit to hopefully reduce workflow run time


Reading data from any file position

Hello,
I've found the Binary File Viewer and I find it quite useful :-)
Is there any way to read some data from a binary file just from a specific file position?
As far as I have seen you can only read an input file forward with the given amount of bytes - through the "read()" function.
This is enough for easy file formats, but what about more complex ones - like the ELF or PE binary format? To be able to proper parse such files, you have to read data from specific offsets which you know after you have parsed the file header. You would need in the Parser function access to a function like "getBytesAt" to be able to freely "move around" in the binary file.
Thanks,
-Klaus

Yes, that' right. The idea is to continuously move the read pointer.
Can't you just read the header first and parse all the information you need ?

That would be possible, but you also need the possibility to move backwards - and also forwards - in the binary file.
Thanks, Klaus
Sent from my iPhone
On 12.11.2022, at 18:09, maziac @.***> wrote:

Yes, that' right. The idea is to continuously move the read pointer.
Can't you just read the header first and parse all the information you need ?
—
Reply to this email directly, view it on GitHubhttps://github.com/maziac/binary-file-viewer/issues/5#issuecomment-1312529704, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ABS55RXJKULXQABHI2KM6GLWH7FOFANCNFSM6AAAAAAR6LK72M.
You are receiving this because you authored the thread.Message ID: @.***>

Would be there any problem by providing a "getBytesAt" function available within the parser functionality?

A 'getBytesAt' does not fit into the concept.
There is a 'read' function with parameter size.
What I am thinking of is maybe a function that sets the offset to a different value and one function to read the current offset.
I.e. one could read/store the current offset, set to some other offset and restore the offset afterwards.

A function that sets the offset to a different value would work perfectly! :-)
Sent from my iPhone
On 14.11.2022, at 18:36, maziac @.***> wrote:

A 'getBytesAt' does not fit into the concept.
There is a 'read' function with parameter size.
What I am thinking of is maybe a function that sets the offset to a different value and one function to read the current offset.
I.e. one could read/store the current offset, set to some other offset and restore the offset afterwards.
—
Reply to this email directly, view it on GitHubhttps://github.com/maziac/binary-file-viewer/issues/5#issuecomment-1314132154, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ABS55RTZEFK72ZL7N3HOWDDWIJ2B3ANCNFSM6AAAAAAR6LK72M.
You are receiving this because you authored the thread.Message ID: @.***>

Here is a version you can try out with
setOffset() and getOffset():
binary-file-viewer-1.6.0-rc1.vsix.zip
A brief description can be found in the help text.
Please let me know if it works for you.

Is it still required?

Currently not, thanks for your help.
From: maziac @.>
Reply to: maziac/binary-file-viewer @.>
Date: Tuesday, 29 November 2022 at 22:21
To: maziac/binary-file-viewer @.>
Cc: Klaus Aschenbrenner @.>, Author @.***>
Subject: Re: [maziac/binary-file-viewer] Reading data from any file position (Issue #5)
Is it still required?
—
Reply to this email directly, view it on GitHubhttps://github.com/maziac/binary-file-viewer/issues/5#issuecomment-1331326551, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ABS55RTCIU7PZBJPVSYOCHLWKZXWJANCNFSM6AAAAAAR6LK72M.
You are receiving this because you authored the thread.Message ID: @.***>

Could you at least verify that it is working.

No response.


Try catch failure catching

I added the try catch protection to each of the exporters.
I'm not happy with how I'm ultimately displaying a failure:
------------------------------------------------------------
Elapsed time: 3.97s
465 errors (shr-expand, failure in 1 exporter(s) [Model Doc])
5 warnings (shr-text-input, shr-json-schema-export)
------------------------------------------------------------

Do you have any suggestions for a better message?
(P.S. Don't mind the actual error numbers, I was intentionally breaking exporters so that's not reflective of a clean build.)

How about:
------------------------------------------------------------
Elapsed time: 3.97s
1 fatal error (shr-model-doc)
465 errors (shr-expand)
5 warnings (shr-text-input, shr-json-schema-export)
------------------------------------------------------------

Better?

That's better.
Additionally. how do you feel about displaying the 0 fatal errors message when there are no errors? Should that be displayed or should I omit it altogether?

I say omit it.


go: 1.14 -> 1.14.1

Motivation for this change
Update go_1_14 version from 1.14 -> 1.14.1
Things done

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

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

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

Duplicate of https://github.com/NixOS/nixpkgs/pull/83689


Add stdev to benchmark results

Reference: https://twitter.com/trevnorris/status/712355178939199488
https://www.mathsisfun.com/data/standard-deviation-formulas.html

I would like to give this a shot.

@7373Lacym Go ahead :)
Let us know if you have any questions. We're also in https://gitter.im/sindresorhus/ava

Fixed by #744.


Attribute dependency

Description
Compilation error when you need to have cross attribute dependency between two cookbooks. It doesn't resolve/found dependency attribute when you call a cookbook which depends on an other cookbook which himself call an attribute of first cookbook
Chef Version
tested with v14.5.27 and higher
Platform Version
Debian 8
Replication Case
I have 2 cookbooks. Each depends to the other in metadata
cookbooks/cb1
├── attributes
│   └── default.rb
├── metadata.rb
├── recipes
│   └── default.rb

cookbooks/cb2
├── attributes
│   └── default.rb
├── metadata.rb
├── recipes
│   └── default.rb

cookbooks/cb1/attributes/default.rb
default['cb1']['port'] = '1234'
cookbooks/cb1/recipes/default.rb
puts "CB1: #{node['cb1']['port']}"
puts "CB1: #{node['cb2']['service']}"

cookbooks/cb2/attributes/default.rb
default['cb2']['service'] = "service_cb2:#{node['cb1']['port']}"
Add into run_list: recipe['cb1']
Client Output
...
==> jessie: Synchronizing Cookbooks:
==> jessie: - cb1 (0.1.0)
==> jessie:   - cb2 (0.1.0)
==> jessie: Installing Cookbook Gems:
==> jessie: Compiling Cookbooks...
==> jessie:
==> jessie: ================================================================================
==> jessie: Recipe Compile Error in /var/chef/cache/cookbooks/cb2/attributes/default.rb
==> jessie: ================================================================================
==> jessie:
==> jessie: NoMethodError
==> jessie: -------------
==> jessie: undefined method `[]' for nil:NilClass
==> jessie:
==> jessie: Cookbook Trace:
==> jessie: ---------------
==> jessie:   /var/chef/cache/cookbooks/cb2/attributes/default.rb:1:in `from_file'
==> jessie:
==> jessie: Relevant File Content:
==> jessie: ----------------------
==> jessie: /var/chef/cache/cookbooks/cb2/attributes/default.rb:
==> jessie:
==> jessie:   1>> default['cb2']['service'] = "service_cb2:#{node['cb1']['port']}"
==> jessie:   2:
==> jessie:
==> jessie:
==> jessie: System Info:
==> jessie: ------------
==> jessie: chef_version=14.5.27
==> jessie: platform=debian
==> jessie: platform_version=8.11
==> jessie: ruby=ruby 2.5.1p57 (2018-03-29 revision 63029) [x86_64-linux]
==> jessie: program_name=/usr/bin/chef-client
==> jessie: executable=/opt/chef/bin/chef-client
==> jessie:
==> jessie:
==> jessie:
==> jessie: Running handlers:
==> jessie: [2018-11-08T21:31:35+00:00] ERROR: Running exception handlers
==> jessie: Running handlers complete
==> jessie:
==> jessie: [2018-11-08T21:31:35+00:00] ERROR: Exception handlers complete
==> jessie: Chef Client failed. 0 resources updated in 45 seconds
==> jessie: [2018-11-08T21:31:35+00:00] FATAL: Stacktrace dumped to /var/chef/cache/chef-stacktrace.out
==> jessie: [2018-11-08T21:31:35+00:00] FATAL: Please provide the contents of the stacktrace.out file if you file a bug report
==> jessie: [2018-11-08T21:31:35+00:00] FATAL: NoMethodError: undefined method `[]' for nil:NilClass
Chef never successfully completed! Any errors should be visible in the
output above. Please fix your recipes so that they properly complete.

Up.

I have 2 cookbooks. Each depends to the other in metadata

that creates a circular dependency which causes problems.  its is a poor way to structure code, it gives depsolvers performance issues, and causes logical difficulties like the one you've got now.  it is difficult for chef itself to ban, but its a very bad practice that would be banned if it was simple to do so.  the molinillo depsolver in policyfiles and with berkshelf will also fail to upload these files, and i think i've included code now in berkshelf which attempts to fail to upload circular deps even with the gecode solver.
cb2 needs to depend on cb1 and the dependency of cb1 on cb2 needs to be removed.  then cb1 will have its attributes file parsed first, before cb2's attributes file.  right now you're getting the reverse order.
you can also see also noah's blog on this subject where he goes into the problem in more detail:  https://coderanger.net/derived-attributes/


Dump invalid!

Using the similar example mentioned in README (modified dns) I dumped my database without any error (dump.zip). But when I tried to restore it using phpMyAdmin to the same MySQL server I got:
10529 errors were found during analysis.

    Unexpected character. (near "{" at position 20156)
    Unexpected character. (near "}" at position 20193)
    Unexpected character. (near "{" at position 21248)
    Unexpected token. (near "-" at position 30861)

May you please help me to determine the problem?
Important:

This issue doesn't occur in case I use MariaDB LTS (10.11.5)
I couldn't find anything strange using WithDebug()

Some info:

mysqldump: v0.7.0
MySQL:  5.7.43 - Community Server
Go: 1.21.1
dns := "root:rootpasswd@tcp(localhost:3306)/dbname?charset=utf8mb4&parseTime=true"
phpMyAdmin: 5.2.1

New Update 2023.09.13:
Dumping from MariaDB LTS (10.11.5) then restoring to the same server gives the same errors

I dropped using this library. It seems not reliable at all :(


Receiving an error on 'error.accounts.Rating must be a number'

For some reason when developing on my macbook I get this error. My windows machine is just fine. I even tried to delete the project and meteor install and start over but it continues to persist. Any help is appreciated.
Exception while invoking method 'createUser' Error: Rating must be a number
at getErrorObject (packages/aldeed_collection2-core.js:480:15)
at [object Object].doValidate (packages/aldeed_collection2-core.js:462:13)
at [object Object].Mongo.Collection.(anonymous function) [as insert] (packages/aldeed_collection2-core.js:214:25)
at AccountsServer.Ap.insertUserDoc (packages/accounts-base/accounts_server.js:1326:25)
at _createUser (packages/accounts-password/password_server.js:1009:25)
at packages/accounts-password/password_server.js:1040:20
at tryLoginMethod (packages/accounts-base/accounts_server.js:248:14)
at AccountsServer.Ap._loginMethod (packages/accounts-base/accounts_server.js:381:5)
at [object Object].createUser (packages/accounts-password/password_server.js:1026:19)
at maybeAuditArgumentChecks (packages/ddp-server/livedata_server.js:1712:12)
Sanitized and reported to the client as: Rating must be a number [400]

 Rating must be a number
rating is a custom field of yours on Users?
Can you paste here code related to this rating field / users callback ?

Hi Xavier,
It just dawned on me what the problem was, my head wasn't in the game and just resolved it. It was related to my custom field as you stated. A rookie mistake. I really appreciate you taking the time out to help me!


APEXMALHAR-2271 Implement a multimap with time extract from value

@davidyan74  Please review

@siyuanh @davidyan74 @chaithu14 closed due to inactivity


Update quantum_die.py

Updated to pyQuil 2.0 @lcapelluto @mpharrigan

@ryankarle

can you rebase your changes after #611

thanks @tmittal947 and @lcapelluto


[Repository] Entity removal - record is related

src/Controller/Utils/Repositories.php:541
src/Controller/Utils/Repositories.php:379

Solution.
Refactor method hasChildren in Repository.
Use classMeta, extract associations, get field name and with this search for children with deleted = 0.
        $class_meta = $em->getClassMetadata(MyGoals::class);
        dump($class_meta->getAssociationMappings());

Fixed: e5f4de2216031be52b9dd97e6919275fcdd7f512


add an ACM hydrate diff

essentially, this function can be put in a pipeline as a reporter for candidate PRs so that it saves a diff of ACM hydrated  config current and proposed changes.

one good suggestion via johnmurray is to have summary level info also -- that is instead of just having the raw diff output of the resources which normalized/sorted in some way to avoid trivial text changes, also have a digest of the change to indicated which namespace(s) and/or resources(s) were modified in the PR.

Having a "kubectl diff" function would be a good start - i.e. run the hydrated configs against a live cluster specified in a local kubeconfig, then output the results. Bonus points for summarizing the changes so the output is less verbose for large updates.


Refactor AuthenticationManager into interface and implementation

Fixes https://github.com/google/ground-android/issues/465.

[x] Create new AuthenticationManager interface
[x] Move contents of existing AuthenticationManager into AuthenticationManagerImpl
[x] Move SignInState outside of AuthenticationManager so it can be accessed by testing classes (not yet commited)

Hi Don! Why do we need an interface for AuthenticationManager? Is it exclusively to allow us to swap out the implementation for testing? If so, can we use something like Mockito to achieve the same?

Is it exclusively to allow us to swap out the implementation for testing?

Yes, that was the idea.

can we use something like Mockito to achieve the same?

Maybe, although the challenge will be getting Dagger to provide the MockAuthenticationManager during testing. I will investigate.

Is it exclusively to allow us to swap out the implementation for testing?

Yes, that was the idea.

can we use something like Mockito to achieve the same?

Maybe, although the challenge will be getting Dagger to provide the MockAuthenticationManager during testing. I will investigate.

We had a similar issue with Dagger in a previous (pure Java) project I worked on. It would be interesting to see if there's another solution by now to avoid a proliferation of interface + impl pairs only used for testing. Thanks for investigating!

I believe if you set up Mockito you can just declare a private member in the test as @Mock. As long as AuthenticationManager is not final, it should work (even as a class).

Adding my 2 cents to the discussion.
For UI unit tests using Robolectric, we can create "shadow" objects or use Mockito (or PowerMockito for static methods) in order to override specific methods in the tests.
Can't say if they'll be useful in integration tests.

I don't think Mockito will work for e2e / integration tests because what we need is a fake rather than a mock. The fake auth manager needs to offer some basic functionality such as sign in and sign out.
I'll update this PR with all my testing code so you can see the FakeAuthenticationManager

I've added a very rough version of how an integration test might work. Basic architecture:

Tests are run using CustomTestRunner (which is specified in build.gradle).
This instantiates TestGndApplication which is a version of the app specifically tailored for testing
The most important aspect of TestGndApplication is that it has a different dependency graph to the normal app, allowing dependencies to be swapped out for test instances of those classes.
The entry point to the dependency graph is TestGndApplicationComponent which defines the Dagger modules to be used when creating dependencies.
I have created a new module for the MainActivity dependencies called TestMainActivityInjectorModule. It has a corresponding class in the main app called MainActivityInjectorModule.
In the Test version of this module we use the FakeAuthenticationManager to provide login features which allows MainActivity to avoid using Google Sign In and go straight to the map view / project list.

The test itself can be found in MyTests::MainActivity_testLogin. It currently fails 😃 but that's because there are still dependencies on firebase which need faking (or setting up correctly for live instance testing).
Hope that makes sense. Any and all feedback welcome.

I don't think Mockito will work for e2e / integration tests because what we need is a fake rather than a mock. The fake auth manager needs to offer some basic functionality such as sign in and sign out.
I'll update this PR with all my testing code so you can see the FakeAuthenticationManager

As mentioned by VC, could Spies be helpful here? In that case you can mock out some methods while using the actual implementation of others.
https://github.com/mockito/mockito/wiki/Using-Spies-(and-Fakes)
I realize spies aren't a silver bullet; there will be cases where creating an interface + impl + testImpl will be cleaner, but for simple cases perhaps it's worth considering?

@dturner will you come back to this one? Excited to see a well-defined pattern defined for testing!

Of course, sorry for the delay, "real work" getting in the way. Hopefully have some time this week.

Of course, sorry for the delay, "real work" getting in the way. Hopefully have some time this week.

No worries, looking forward!

Hi @dturner ! Is this still WIP? Would it make sense at this point to break this PR into smaller chunks? If so, can we add integration and unit tests separately?


Install virtual kernel headers and image-extra packages

Currently we install the kernel headers for the currently running version as part of this install script, this is necessary for the ZFS kernel modules to build. The package the script currently installs is for a specific kernel version, so updating the kernel with a apt-get dist-upgrade could result in a new kernel being installed without matching headers.
The solution to this appears to be also installing a virtual package that tracks the latest headers, similar to the virtual package that tracks the latest kernel. The only caveat is that there are multiple virtual packages, one for the default kernel, and one for each of the backported kernels. We'll need to detect which one(s) to install based on the installed kernel packages.
We should also do the same thing for linux-image-extra which has the AUFS module.

linux-headers-virtual / linux-headers-virtual-lts-utopic
linux-image-extra-virtual / linux-image-extra-virtual-lts-utopic

This has not been an issue recently, and we are moving away from using any custom kernel modules, so closing.


Remove dead link

It looks like the author deleted the repo: https://github.com/HcySunYang/vue-composition-toolkit
Maybe we should delete the link.

It moved, see https://github.com/vuesomedev/awesome-vue-3/pull/65


getElementAtEvent on Nearest Data Point

Feature Proposal
getElementAtEvent returns the data only if one clicks on the data point.
Feature is to create an event that is similar but returns the closest data point, ideally the data point hovered.
Feature Use Case

This creates better UX, instead of having to click on the specific data point to fire an event, they can move around the graph, whatever data is displayed on the tooltip will be recorded when clicked.
Possible Implementation

See https://github.com/chartjs/Chart.js/issues/5320#issuecomment-548260008

See #5320 (comment)

does this work for react-chartjs-2?

IDK and I'm not going to go find out, if react-chartjs-2 masks the API or not. It works in Chart.js


Translation of README.md

Hi there,
I'd like to run this theme with Typora, unfortunately I'm not familiar with either Korean or Japanese. Could you please translate the instructions of README.md to install it also on my computer?
Many thanks in advance, regards, Thomas

The language of README.md is Chinese, rather than Korean or Japanese. All installation of Typora theme is same, so you can refer to the installation of other English theme.

copy forest.css file and forest direction to your theme direction.


Feature Request(farrow): createFarrowConfig or defineConfig

defineConfig is more common?
https://vitejs.dev/config/#config-intellisense

It doesn't matter, we can support both via one line added.
export const defineConfig = createFarrowConfig

https://www.npmjs.com/package/farrow/v/1.11.1


fix: azurerm_logic_app_standard virtual_network_subnet_id is always r…

1975
PR Checklist

[ ] I have added example(s) inside the [./examples/] folder
[ ] I have added the example(s) to the integration test list for normal (~30 minutes) or long runner >30 minutes
[x] I have checked the coding conventions as per the wiki
[x] I have checked to ensure there aren't other open Pull Requests for the same update/change?

Description

Does this introduce a breaking change

[x] YES - explained in issue # 1975
[ ] NO

Testing

obsolete, created: https://github.com/aztfmod/terraform-azurerm-caf/pull/1978 instead


Representation of empty union

The empty union could be represented by a vector of Intervals
of length == 0 (i.e. a union of no intervals) instead of a vector of length
== 1 with a single empty set (i.e. a union of a single empty set). This could simplify the code a bit, because there will be no need to keep always an empty Interval in the stored vector.
Originally posted by @abraunst in https://github.com/AnderGray/IntervalUnionArithmetic.jl/issues/18#issuecomment-1028175731

Fixed by PR #21


Git - fix stage/unstage selected ranges in nested git repositories

Related #188967
When opening a folder/workspace that contains nested git repositories some operations (ex: stage/unstage selected ranges) do not work as expected. I have tracked this down to the fact that the QuickDiffService will return both repositories instead of only the inner repository. Due to that, the diff information provided to the stage/unstage selected ranges commands is incorrect.
The issue could be fixed either in the git extension or in the QuickDiffService. The changes in this pull request fixes the issue in the git extension but I would like to get your thoughs on whether this should be fixed in the git extension or the QuickDiffService. Thanks!

I think the fix makes more sense to happen in the git extension, this is the best approach. 👌


supplementary material

I see the supplementary material you mentioned in your paper, but it is not available on arxiv, can you share it?

The supplementary is available on arxiv. See pages 9 and after at https://arxiv.org/pdf/2012.01377.pdf


Paths to API-zips are broken in README.md

@bearbin how is the redirection for https://download.cuberite.org/windows-i386/Cuberite.zip to AppVeyor latest build implemented? (interestingly just https://download.cuberite.org/windows-i386 works too). Can we add a http://download.cuberite.org/manual-api and http://download.cuberite.org/auto-api pointing to AppVeyor?

Can also update https://github.com/cuberite/Core/blob/68519b3e0e7fc129f2fae21c7a766c83167c3cc7/.github/workflows/ci.yml#L32