Enables custom default tags and ability to add no tags (issue #51)

The default tag will still remain "clojure", but users can change it by adding :default-metadata {:tags […]} to their opts map in bb.edn, which also enables them to add multiple default tags or none at all (with an empty vector). I hope my changes are aligned with the intended use of :default-metadata.
For a single post, users can just add --tags without any arguments to omit tags even if the default vector is not empty. Maybe there could also be an option --no-tags for clarity of intent, but I don’t think it’s necessary.

I should enable a test runner on CI, but for now you can run tests locally with bb test. If possible, it would be good to add a test for this PR as well.

Oh well, seems like the test for migrate fails, because tags are now ordered before the post title in the document after calling api/migrate. I don’t know what causes this, but I’ll see if I can fix it.
I only tested the behavior of the new command with various tags/defaults in a separate project, but will try to add tests as well, if I can figure out how to set them up correctly.

I think you can change the test by splitting the lines and comparing the set of both lines.

Just changed the failing test according to your suggestion, which I hope I understood correctly. I wasn’t sure what exactly “migrate” does and if the order is important.

Thanks and congrats with your first merged PR :)

Glad I could help, had to learn some new things about Git and GitHub along the way. :D


feat: Add option to disable conversation history

Add new disableConversationHistory boolean parameter under Additional Parameters in Agent and LLMNode to optionally skip including conversation history in prompts, improving sequential agent workflow customization capabilities
Fix potential error in Agent.ts when messages array is empty by adding null safety checks

When testing locally, I encountered an error with the agent tool when the "Require Approval" toggle is set to true. However, this issue occurs regardless of whether "Disable Conversation History" is set to false or true, so I suspect the problem is unrelated to the changes in this PR.

You can use the attached agent workflow, Test flow Agents.json, for verification.
Feel free to check with the joint "Test flow Agents.json" agent workflow.
Test flow Agents.json
Additionally, my existing LLM nodes/agent nodes are not updated automatically. I had to create new nodes for the "Disable Conversation History" parameter to appear under additional parameters. I'm unsure if this behavior is expected, but it happens regardless of whether I bump the component versions.

@jeanibarz
This is great! So for example, if you only need to give a node the last message, you could disable including the full history, and manually pass just the last message right?

Yes, exactly! The feature disables the inclusion of historical messages in the prompt but still allows you to manually add specific messages—whether from the prompt or from the script that allow to create custom conversation messages. In theory, this means you could include the initial user query or even the last two messages from the state messages history, for example. Additionally, it’s worth noting that the node will still append its output to the state messages as usual.

Awesome, I had my fingers crossed that this would come soon. I think a lot of people don't realize the amount tokens they are burning behind the scenes. Hopefully just seeing the option will help increase awareness (on top of control of course).

I attempted to add a history message when the boolean disableConversationHistory is set to true. Here's what I observed:

Success with Human Prompt and Format Values: Using a placeholder and the value from $flow.state.messages[-1].content, the placeholder was correctly replaced with the latest message. This approach works perfectly. Alternatively, the value can also be retrieved directly from the state or the output of another node.

Issue with Script Code in the "Messages History" Field: (probably because I don't know how to use it properly though...) When I tried using state.messages[-1].content, flow.state.messages[-1].content, or $flow.state.messages[-1].content within the script code, I encountered an error stating that the key messages does not exist.
I also attempted to use a placeholder in the format prompt (similar to the human prompt), but the placeholder was not replaced with the expected value. You can see this issue in the screenshot below:
but probably because I don't know how to use it properly: when I use state.messages[-1].content or flow.state.messages[-1].content or $flow.state.messages[-1].content I get an error saying that key messages doesn't exist. I tried also using a placeholder and setting the value in format prompt, as for the human prompt, but the placeholder is not replaced with the value, see the screenshot below

When testing locally, I encountered an error with the agent tool when the "Require Approval" toggle is set to true. However, this issue occurs regardless of whether "Disable Conversation History" is set to false or true, so I suspect the problem is unrelated to the changes in this PR.
Feel free to check with the joint "Test flow Agents.json" agent workflow. Test flow Agents.json
Additionally, my existing LLM nodes/agent nodes are not updated automatically. I had to create new nodes for the "Disable Conversation History" parameter to appear under additional parameters. I'm unsure if this behavior is expected, but it happens regardless of whether I bump the component versions.

When testing locally, I encountered an error with the agent tool when the "Require Approval" toggle is set to true. However, this issue occurs regardless of whether "Disable Conversation History" is set to false or true, so I suspect the problem is unrelated to the changes in this PR.
Feel free to check with the joint "Test flow Agents.json" agent workflow. Test flow Agents.json
Additionally, my existing LLM nodes/agent nodes are not updated automatically. I had to create new nodes for the "Disable Conversation History" parameter to appear under additional parameters. I'm unsure if this behavior is expected, but it happens regardless of whether I bump the component versions.

For approval tools, you need an agent memory attached

When testing locally, I encountered an error with the agent tool when the "Require Approval" toggle is set to true. However, this issue occurs regardless of whether "Disable Conversation History" is set to false or true, so I suspect the problem is unrelated to the changes in this PR.
Feel free to check with the joint "Test flow Agents.json" agent workflow. Test flow Agents.json
Additionally, my existing LLM nodes/agent nodes are not updated automatically. I had to create new nodes for the "Disable Conversation History" parameter to appear under additional parameters. I'm unsure if this behavior is expected, but it happens regardless of whether I bump the component versions.

When testing locally, I encountered an error with the agent tool when the "Require Approval" toggle is set to true. However, this issue occurs regardless of whether "Disable Conversation History" is set to false or true, so I suspect the problem is unrelated to the changes in this PR.
Feel free to check with the joint "Test flow Agents.json" agent workflow. Test flow Agents.json
Additionally, my existing LLM nodes/agent nodes are not updated automatically. I had to create new nodes for the "Disable Conversation History" parameter to appear under additional parameters. I'm unsure if this behavior is expected, but it happens regardless of whether I bump the component versions.

For approval tools, you need an agent memory attached

Thank you. I tested with AgentMemory and it works when the required approval is true: thank you !

rearranging order of the parameters to correctly reflect how sys prompt, history, human prompt are being sent:

Thank you very much to you for your time and your patience ;-)


Cannot deploy Sf 3.3 with bundle v1.0.3

Hello, today I've updated to v1.0.3 and my deploy script is not working.
Im running symfony 3.3, here is my config:
public function configure()
    {
        return $this->getConfigBuilder()
            ->server("servername")
            ->deployDir($this->getDeployDir())
            ->repositoryUrl($this->repoUrl)
            ->remoteComposerBinaryPath('composer')
            ->composerInstallFlags('--prefer-dist --no-interaction --quiet')
            ->sharedFilesAndDirs(array('app/config/parameters.yml', 'var/logs', 'var/sessions'))
            ->writableDirs(array('var/cache/', 'var/logs/', 'var/sessions'))
            ;
    }

This is the error when I run "deploy stag":
[InvalidArgumentException]

   The target directory "/home/user/client_repo/releases/20180404184402/public" does not exist.

I think it's something related to symfony 4 and the "public" directory.
Thanks!

Yeah getting this too, I think the checks for the Symfony version might be failing and defaulting to 4. Pinging @javiereguiluz incase you haven't seen this, it breaks BC.

Same problem .
You can fix this temporarily by adding  ->webDir('web') to the deployer

@gabricom thanks for the suggested fix, I was wondering though, have you tried it and deployed successfully? Because there a other changes in directory structure between Symfony 3.4.x and 4.x.

I tried and it works for me, the other directories seems to be fine

It work if you set shared files and dirs. If it is not set - null break execution. And if I don’t add ssh keys from server to gitlab I cannot enter username and password. On local machine I can do this. And if I use .env.dist on local it does not copy by command cp -a ./repo/* to ./releases/release. It is for example. And it don’t copy hidden files. And composer return error. This regular must be not like *. It is on symfony 4+.
Отправлено с iPhone

19 апр. 2018 г., в 9:26, gabricom<EMAIL_ADDRESS>написал(а):
I tried and it works for me, the other directories seems to be fine
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.


Update README.md

Fix small typo

Thank you! Nice catch! :mag: :taco:

Happy to help, thanks for contributing great open source software!


Change Label orientation on x-Axis for Bar Charts

Expected behavior
Hi,
I rotated the X axis labels 90 degrees. The labels are not in line with the chart as you can see they are slightly shifted to the right.
I removed the css style, but it didn't change anything, it looks like a problem with the script.

chart.js version
v3.9.1

Please when you submit a bug report add a reproducable sample, the field is mandatory for a reason so it saves us time trying to reproduce it and asking for a reproducable sample if we can't reproduce it

Hi,
My code:
new Chart(conversionsChart, { 	 type: 'bar', 	 options: { 		scales: { 		  y: { 			 ticks: { 				callback: function (val) { 				  return val + '%'; 				}, 			 }, 		  }, 		  x: { 			  ticks: { 				  autoSkip: false, 				  maxRotation: 90, 				  minRotation: 90 			  } 		  }, 		}, 	 }, 	 data: { 		labels: [ 		  'Oct 1', 		  'Oct 2', 		  'Oct 3', 		  'Oct 4', 		  'Oct 5', 		  'Oct 6', 		  'Oct 7', 		  'Oct 8', 		  'Oct 9', 		  'Oct 10', 		  'Oct 11', 		  'Oct 12', 		], 		datasets: [ 		  { 			 label: '2020', 			 data: [25, 20, 30, 22, 17, 10, 18, 26, 28, 26, 20, 32], 		  }, 		  { 			 label: '2019', 			 data: [15, 10, 20, 12, 7, 0, 8, 16, 18, 16, 10, 22], 			 backgroundColor: '#d2ddec', 			 hidden: true, 		  }, 		], 	 },   });

Hi,
All settings and styles are removed and the labels are still shifted.

2 cents. It seems to be solved in version 4. Trying in your codepen with<EMAIL_ADDRESS>the ticks sounds to be drawn correctly.

2 cents. It seems to be solved in version 4. Trying in your codepen with<EMAIL_ADDRESS>the ticks sounds to be drawn correctly.

Thank you for the info :)

Fixed in V4
https://codepen.io/leelenaleee/pen/rNqWBQz


I'm getting Error 1 but can't find the 4.1.1 language data

Hello! Thank you for creating this.
I'm trying to get it working but I get the error 1.
I triple checked that I have a tessdata folder inside my debug folder. So from what I'm reading the issue is that I'm using eng.traineddata for 4.1.0 and I have installed 4.1.1. Where can I find the 4.1.1 version?
And just to make sure, language data means .traineddata files right?

SOLVED
If someone else is having this issue, the problem is the tessdata folder must be in your root folder application, I was putting it inside the debug folder.

SOLVED
If someone else is having this issue, the problem is the tessdata folder must be in your root folder application, I was putting it inside the debug folder.


Type inference on shouldBe for maps

Hello everyone,
Maybe this could be marked as an improvement or such a thing, but I noticed when using the plugin and trying to run some tests that it failed at compile. The error was a type inference error, more specifically the ...environment shouldBe emptyMap() :

Setting the type on the emptyMap() receiver fixes this issue :

However, I imagine it could easily figure out the type of the expected map based on the input, as you can see below the type of the value is set explicit and properly in the class itself:

But the IDE will complain that it's redundant (as it's greyed out), so it's a little bit of confusion there, whether the map should have the explicit type or not set. This is not a real problem, it's just a little bit annoying and in the long term people would be tempted to alt+enter and remove the <String,String> and then they would get the compile error on tests. :)
Any possible solution I could take over my side ? (besides setting the type on the map as I did that already). If not, could this be filed as an improvement/something be done about it?

I think this is because the new type interference is enabled in intellij but not in gradle.

This seems to be fine in kotlin 1.4


Add to readme all extra feature provided by streamex.

For example, I will need to "merge" two streams. Look to  https://github.com/amaembo/streamex - nothing :(
So I found out the operation name on Google ("zip"), in parallel I found several other libraries provide such functionality (protonpack, Lazy-Seq) and only after it in Eclipse I realized that such method is exists in StreamEx.

The SO question that may be updated with StreamEx :)
http://stackoverflow.com/questions/17640754/zipping-streams-using-jdk8-with-lambda-java-util-stream-streams-zip

Actually StreamEx cannot merge (zip) two streams. Such operation cannot be implemented efficiently for parallel streams, so I decided not to make this at all. So I cannot answer to that SO question. Instead you can "merge" two arrays or random access lists via StreamEx.zip or EntryStream.zip. I wrote, for example, this and this answers to describe such feature.
Currently the primary information source for StreamEx is JavaDoc. It's quite comprehend and describes almost all methods (though some are still missing the documentation). Adding every single feature to the README.md sounds too much. However I'm thinking about writing the tutorial describing most of the features with some real world examples. Unfortunately so far I had no time to work on such tutorial. If you want to write it by yourself, pull requests are welcome :-)

For readme IMHO perfectly enough just a mention of an extra functionality. For instance, "limited zip operation support" is Ok :)

Ok, I'll think about it. Thank you for suggestion.

I committed a Cheatsheet which lists currently all the additional methods of StreamEx/EntryStream/IntStreamEx/LongStreamEx/DoubleStreamEx classes (new collectors are yet to be added). Please take a look. Is it something you're looking for?

Yes! It is much more than I asked. Learned a lot :)
One note - for the following updates it will be better to add one more column with a version - since such feature appeared.

Ok, as you're satisfied, I'm closing this issue :-)
I don't like adding version number to the cheatsheet. Version numbers are already present in JavaDoc. Adding them to cheatsheet would make it overcrowded. If you want to see the latest changes, just check CHANGES.md. In general if you use the latest version you always have all the available features and there's no need to know when such feature appeared first.

By the way are you the author of org.jresearch.logui? I reviewed the usage of StreamEx in this code (seems that it's the first artifact published in Maven Central which depends on StreamEx!) and has a couple of simple advices. If you want, you may contact me via e-mail<EMAIL_ADDRESS>for details.


docs: add more details about date parsing in the stats command

Hello 👋🏻
I just spent a bit of time figuring out what the stats command can do and what the proper syntax is. I figured I'd spare some people some searching in the future by updating the documentation.

Document the use of chrono_english and point to its documentation for date formatting.
Document the fact that one can manipulate a 24h window, rather that just a specific day.
Document the relationship with the dialect option in the configuration.
Update the existing examples and add a few more.

Also, I think the stats command's help is a bit misleading for 2 reasons:

The argument name period seems like a misnomer. Based on the code, the period is fixed, it's either 1-day or all of history.  I get the idea, treat the command's arguments as a vector and reconstruct the string from there so that the users don't need to quote the period. But it makes it look as though we could potentially give multiple periods, which does not work.

I haven't changed anything in that regard in this PR. I have my idea about a better way to deal with this but I have no experience with rust at all which would make implementing it slow and complicated. Maybe those problems are worth an issue, I'll wait for your feedback on that.
Have a good day ! :)

The argument name period seems like a misnomer. Based on the code, the period is fixed, it's either 1-day or all of history. What the users really give is a starting point for that 1-day period.

Good point. I'd be open to fixing this in an update. I'm not too concerned about this command regarding breaking changes. Wdyt @ellie

period is represented as a list. I get the idea, treat the command's arguments as a vector and reconstruct the string from there so that the users don't need to quote the period. But it makes it look as though we could potentially give multiple periods, which does not work

I think if we fix this, we should have start_date and an optional end_date. The implicit behaviour could remain a single day, but we can then provide the end date to make it longer. The example commands would change accordingly to atuin stats 'last friday'


[FLINK-14068][core] Removes deprecated org.apache.flink.api.common.time.Time

What is the purpose of the change
Removes deprecated org.apache.flink.api.common.time.Time
Brief change log
The changes where done using the IDE refactoring and find&replace operations.
Verifying this change

CI should pass

Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): no
The public API, i.e., is any changed class annotated with @Public(Evolving): no
The serializers: no
The runtime per-record code paths (performance sensitive): no
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn, ZooKeeper: no
The S3 file system connector: no

Documentation

Does this pull request introduce a new feature? no
If yes, how is the feature documented? not applicable

$ find . -name "*.java" | xargs sed -i 's/import org.apache.flink.api.common.time.Time;/import java.time.Duration;/g'

Converting this one to draft. Things to do:
[ ] Going through the code diff and identifying wrong/missing code changes
[ ] Going through the docs diff and identifying wrong/missing changes
[ ] Fixing Python API

@flinkbot run azure

@HuangXingBo @dianfu I am removing the Java class Time in this refactoring but struggle with the flink-python code. CI fails repeatedly with the following error:
Sep 05 18:51:05 >           raise Py4JError("{0} does not exist in the JVM".format(new_fqn))
Sep 05 18:51:05 E           py4j.protocol.Py4JError: org.apache.flink.streaming.connectors.kafka.FlinkKafkaProducer does not exist in the JVM

The error doesn't occur without my changes, so I assume that it's caused by the PR. But the error message seems unrelated (I didn't touch FlinkKafkaProducer). And I don't find any hint where to look for the cause of the issue.
Could you help a bit here or point me to someone who could?

@flinkbot run azure

@flinkbot run azure

The error doesn't occur without my changes, so I assume that it's caused by the PR. But the error message seems unrelated (I didn't touch FlinkKafkaProducer). And I don't find any hint where to look for the cause of the issue.

Ok, looks like the Time class cannot be deleted because other libraries (e.g. flink-connector-kafka with [FlinkKafkaProducer:29](https://github.com/apache/flink-connector-kafka/blob/main/flink-connector-kafka/src/main/java/org/apache/flink/streaming/connectors/kafka/FlinkKafkaProducer.java#L29] still rely on it)
I overlooked the hint in the e2e test failure.
I reverted the removal of the Time class and labeled it as @Internal. Let's see whether that fixes the issue. :crossed_fingers:

@zentol

Thanks for picking this one up, @zentol . I addressed you one change request and will squash-merge the PR after another CI run.
The current CI failure is related to FLINK-36279.

force-pushed a rebase to master after FLINK-36279 was merged.


JSON keys containing a "@" symbol are hidden

It's especially annoying when dealing with JSON-LD document (by the spec reserved keywords start by a @).

When highlighting:

Setup: Mac OS, iterm2, ZSH.

Hello. It seems that this is a terminal configuration problem, not a library one. I tried to play on my mac and I had no problems. This is also indicated by the behavior when selecting the response text.

Good catch @LuckyDenis. The color of keys starting with a @ is black. It's weird because it's not the case for other keys (not starting with a @). It works well on a light background, but not on a dark one.

Here are  screen

@dunglas, thanks. I would still curl -v checked.

It's most likely that your terminal color scheme, which HTTPie adopts by default, doesn't play well with the highlighter. I'd try to tweak the terminal colors or explicitly specify a style to use in the config file (in your case the bundled solarized might do the trick):
{
    "default_options": [
        "--style=solarized"
    ]
}

https://httpie.org/doc#configurable-options
See $ http --help for all available styles.


Use new angular theme package

Changes proposed in this Pull Request:

Use new angular theme package.

No impact noticed.


Makes the config and watch commands to only work if no other instance of them is found.

This is an important change because if you run the config command in multiple instances there is a good chance it will corrupt the json.

I think this PR is done.

If there was smth for me to add that would be a docstring

I think this PR is done.
If there was smth for me to add that would be two docstrings.

done

Because we were getting a lot of unreasonable errors for no apparent reason, I decided to just not support mac in this, if the user uses a mac they will not see any change to the behavior of anime dl from this PR. In other words this PR won't affect mac users in any kind of way.


Complete documentation with the patterns

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

Comparison is base (5329e91) 71.61% compared to head (e78baed) 71.61%.

Additional details and impacted files
@@           Coverage Diff           @@
##             main      #50   +/-   ##
=======================================
  Coverage   71.61%   71.61%
=======================================
  Files          37       37
  Lines        5112     5112
=======================================
  Hits         3661     3661
  Misses       1451     1451

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


how can i generate gt.yml

I'm now using Objectdatasettools to make my dataset. However, Objectdatasettools doesn't provide gt.yml file. Therefore I'm quite confused and want to know how to get this file.

@Jakob0330 Are you using Objectdatasettools  to create 3D model of your dataset object ?

Do you resolve this problem?

Not yet. Can authors help here?


Destroy and create actors dynamically

Is your feature request related to a problem? Please describe.
While I understand that there are only a limited number of actors that you can place in a scene, having the option to add/remove actors on the fly could lead to a treasure trove of new gameplay options.
Describe the solution you'd like
If possible, add a "Destroy Actor" and "Create/Spawn Actor" event to the engine.
Describe alternatives you've considered
If this creates too many edge cases, another option might be to provide an accessible path for creating/spawning actors by handling the engine code directly, and then creating some guide/documentation on how you might do this.
In a similar vein, perhaps there could be an option to create custom events that run small snippets of code and then limit actor creation / destruction to that.
Additional context
As for gameplay examples, when entering a town you could populate it with 10 unique actors assigned randomly from a pool of say 50 possible actors in ROM. Through this you could create environments that feel less static, changing parts of a scene between playthroughs or after completing a quest, without butting into the limits of workarounds like hiding actors or manually duplicating scenes.
Another scenario this could enable would be "recursive" actors i.e. after firing a projectile actor, upon hitting a wall that actor then destroys itself, and spawns another 2 projectile actors that travel in different directions (obviously you would need to be careful with multiple moving actors but you get the idea).

AFAIK you can't bypass the actor limitation, because all possible variations are preloaded for the current scene where they'd be used... the Pros in here will be able to explain the technical reasons ;-)

Projectiles can be created dynamically for how simple they are, and that the event tells the scene to keep the projectile sprite loaded. Projectiles at all, was not a simple task in itself, #73
Dynamically loadable actors are, in part, already a thing now, as there is a pool of 30 actors over a larger scene.
All the scripts for them however, are hard coded pointers, any local variables used in the script, added to the total variable list like a new global variable, references to other actors for movement too, duplicating an actor in editor usually creates new variables and actor references before the compile, which might not work if they were left as is.
Any arrays for amount of actors, or the dynamic pool of projectiles, must also fit within a pre allocated section of ram, and are referenced in collision checks.
From all of that, sprite to scene allocation issues, actor and variable reference setups, and other edge cases, it might be hard to get around.
Ejecting the engine and modifying projectile code might be a good place to start,
Randomly generating actors in a scene might be easier/simpler/more polished as a few duplicated preset scenes, with random actor starting positions on init making everything else.
Your "recursive" actor is hit, and spawns 2 more projectiles, is already possible, update scripts are terminated if the actor is hidden, not sure about hit scripts, you might need to fire the projectiles before hiding. You could experiment with unhiding them after a certain time, or a transparent sprite/ disabling collision, or moving them to the corner of screen instead of hiding the actor.
However, the coming engine rewrite to /gbvm  aims to make scripts human readable when output, and rework a lot of things, so it might be a possibility in future, but not exactly soon. Work around/with the limitations for now, and be glad there are projectiles at all


TypeError: null is not an object (evaluating 'RNKeychainManager.SECURITY_LEVEL_ANY')

Please search the closed issues for solution to this problem.


⚠ ClamAV has degraded performance

In 2b60ce5, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 429 ms

Resolved: ClamAV performance has improved in 9f4d0d2.


[WIP][EmbeddedAnsible] Handle nested playbooks

As mentioned by:
https://bugzilla.redhat.com/show_bug.cgi?id=1734446
We currently don't support nested playbooks with EmbeddedAnsible using AnsibleRunner.  This was an oversight that Ansible Tower / awx gave us for free, so this implements what those two were doing in the past.
Of note, we are saving the full relative file path for the name now in the ConfigurationScriptPayload record.  This is what was done previously when doing a refresh, but worth noting.
Links

Fixes https://bugzilla.redhat.com/show_bug.cgi?id=1734446
awx links:

valid_playbook_re
skip_directory
could_be_playbook

Steps for Testing/QA
Need to test this with an actual playbook run still...

@miq-bot add_label core, embedded ansible, bug
@Fryguy @carbonin please review

I'm good with this testing style and FakeAnsibleRepo helper class.  It seems like we could even reuse this helper elsewhere.  I just don't like the spec + String -> gsub | YAML.parse -> Hash when we can just do spec + Hash.

Still working on trying out some of the other fixes for this PR (supporting $ANSIBLE_VAULT, and adjusting walk_blobs and such), but pushed up the changes for a non-yaml form of the helper.  I left the previous version in a new branch for posterity:
https://github.com/ManageIQ/manageiq/compare/master...NickLaMuro:well_at_least_I_thought_it_was_cool
And will continue working on the other changes after I break for lunch.

@Fryguy is this ready to go outside of the typo? Also @NickLaMuro can you add the BZ link to at least one commit (or ideally all of them)?

@carbonin I am in "rebase hell" with this one trying to fix the merge conflicts with Jason's "SCM Credentials" PR, so I need to fix that before this can be merged.

@Fryguy @carbonin This should be good for a final look.  As part of the rebase, I should have addressed any outstanding comments and feedback, and as a result the logic has changed a bit.  Please do take a look and let me know if I botched anything as a result.

Ivanchuk backport details:
$ git log -1
commit cd0cdd9a65674e135dcbbcdfdca929f98fa0ccba
Author: Nick Carboni<EMAIL_ADDRESS>Date:   Thu Aug 8 17:12:43 2019 -0400

    Merge pull request #19089 from NickLaMuro/embedded-ansible-find-nested-playbooks

    [EmbeddedAnsible] Handle nested playbooks

    (cherry picked from commit 1d47fd71df6ce000d27c557aac80a75340592a26)

    Fixes https://bugzilla.redhat.com/show_bug.cgi?id=1734446

@NickLaMuro Travs is failing in manageiq-providers-vmware, please take a look.
https://travis-ci.org/ManageIQ/manageiq-providers-vmware/jobs/569665969
An error occurred while loading ./spec/manageiq/spec/models/manageiq/providers/embedded_ansible/automation_manager/configuration_script_source_spec.rb.
Failure/Error: require 'support/fake_ansible_repo'
LoadError:
  cannot load such file -- support/fake_ansible_repo
# ./spec/manageiq/spec/models/manageiq/providers/embedded_ansible/automation_manager/configuration_script_source_spec.rb:1:in `<top (required)>'
Run options: include {:providers_common=>true}


Update default values for sealed secrets in service command

What type of PR is this?

/kind bug

What does this PR do / why we need it:
Have you updated the necessary documentation?

[ ] Documentation update is required by this PR.
[ ] Documentation has been updated.

Which issue(s) this PR fixes:
Fixes #?
How to test changes / Special notes to the reviewer:

Codecov Report

Merging #43 into master will not change coverage.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##           master      #43   +/-   ##
=======================================
  Coverage   61.41%   61.41%
=======================================
  Files          52       52
  Lines        2462     2462
=======================================
  Hits         1512     1512
  Misses        816      816
  Partials      134      134

Flag
Coverage Δ

#unittests
61.41% <100.00%> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

pkg/cmd/service/add.go
70.00% <100.00%> (ø)

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 4a7d6f0...9b40a4a. Read the comment docs.

Let's fix this in a better way in a separate branch.

/lgtm


[Feature] Add loader helpers

loadScript
loadImage
loadIframe
integration in the framewok?

Closed in #520.


No Wallet Has Been Loaded

System:
Ubuntu 16.04.3 LTS
Wallet Version:
Dogecoin Core v<IP_ADDRESS>-bb4b082-dirty
Compiled from source
Problem:

@rnicoll ?

The referenced code is not present in 1.14 so I assume this works as intended now.


Code highlighting incorrectly, when it is below jsx code with no , or ; after.

It's hard to describe.
Here is the code and snapshot.
class App extends Component {
    render() {
        const arr = [

        ];

        // Codes highlight incorrectly
        var foo = 'foo';
        if (foo === 'foo') {
            console.log('hello');
        }
    }
}

And the snapshot is

But it happens only when there is not , or ; after jsx code. And the following works well
class App extends Component {
    render() {
        const arr = [

,
        ];

        // Codes highlights well
        var foo = 'foo';
        if (foo === 'foo') {
            console.log('hello');
        }
    }
}

The follow code has the same issue.
class App extends Component {
    render() {
        // NOTCE: no `;` after.
        const arr =

        // Codes highlight well
        var foo = 'foo';
        if (foo === 'foo') {
            console.log('hello');
        }
    }
}

This issue is difficult for me. So, please last a moment.
I may possibly, I can't fix this problem.
To rewrite as below, This issue is fixed.
diff --git a/after/syntax/javascript.vim b/after/syntax/javascript.vim
index 7ec31e3..b4aee53 100644
--- a/after/syntax/javascript.vim
+++ b/after/syntax/javascript.vim
@@ -30,6 +30,7 @@ syntax region jsxRegion
       \ end=+>\n\?\s*)\@=+
       \ end=+>\n\?\s*}\@=+
       \ end=+>;\@=+
+      \ end=+>\n\@=+
       \ end=+\n\?\s\*,+
       \ end=+\s*>,\@=+
       \ end=+\s\+:\@=+

But, syntax-highlight break in different place.

Could you send me PR if you possible?

@MaxMEllon I will try.

I appreciate your kindness. :smile:
I will try too.


Reduce likelihood of failing to update Filestore IP in A3 blueprint

We have seen customers mistakenly skip the step to update the Filestore IP address. Removing it entirely from the blueprint will ensure that the create/deploy commands will fail. We are also moving its setting to higher in the file so it will be more prominent to the user.
Submission Checklist
Please take the following actions before submitting this pull request.

Fork your PR branch from the Toolkit "develop" branch (not main)
Test all changes with pre-commit in a local branch #
Confirm that "make tests" passes all tests
Add or modify unit tests to cover code changes
Ensure that unit test coverage remains above 80%
Update all applicable documentation
Follow Cloud HPC Toolkit Contribution guidelines #

The alternatives here are:

this PR
removing the value from the blueprint but hacking tools/validate_configs/validate_configs.sh to supply a value for server IP during make tests
enforcing a strict validation for var.server_ip in the pre-existing-network-storage module

The 3rd option is appealing but it turns out var.server_ip is allowed to take on more complex values that are not just IP addresses (e.g. lustre) so adding it could easily do more harm than good. For now, we make the requirement to update IP address more obvious in the rendered markdown.


Manpages are still stuck at v2.16.1

v2.16.2 is now more that 10 days old, but git-scm only shows manpages for v2.16.1

How are you measuring this?
I see v2.16.2 at https://git-scm.com/docs/git-cat-file, for instance. I think there's a bug (or maybe lack of feature :wink:) on the display side that says "v2.16.1" for files that were not updated in v2.16.2 (e.g., https://git-scm.com/docs/git), when it could say "v2.16.2 (last updated in v2.16.1)".

That's it! That's not very intuitive.

Agreed. I'm not sure exactly what the bug is, though. If I run the "latest version" query manually against the production database, it seems to give sane results:
git-scm::DATABASE=> select doc_files.name,versions.name from doc_files
  join doc_versions on doc_files.id = doc_versions.doc_file_id
  join versions on versions.id = doc_versions.version_id
  where doc_files.name = 'git'
  order by versions.vorder desc limit 5;

 name |  name
------+--------
 git  | 2.16.2
 git  | 2.16.1
 git  | 2.16.0
 git  | 2.15.1
 git  | 2.15.0

(AFAICT the actual query just does limit(1).first, which should pick 2.16.2). But the doubly weird thing is that it seems to work correctly in my local development environment. So I'm not sure what's different in production.

Aha. I just flushed the redis cache on production, and the problem went away. So there is something about how the cache key for the page is constructed that does not cause it to be invalidated when we bump the version. I know next to nothing about how that caching works (I think it's all implicit Rails magic).


Transfer error when wrapping filename in quotes

I tried transferring a file with weird name. Some *nix programs will let you wrap the filename in quotes rather than escape different parts. When I tried this it threw an error.
user-mbp:Documents User$ zget "namebench_ 2015-07-08 22_37_46.pdf"
Peer found. Downloading...
Exception in thread Thread-3:
Traceback (most recent call last):
File "/usr/local/Cellar/python3/3.4.3_2/Frameworks/Python.framework/Versions/3.4/lib/python3.4/threading.py", line 920, in _bootstrap_inner
self.run()
File "/usr/local/lib/python3.4/site-packages/zeroconf.py", line 1063, in run
handler(self.zc)
File "/usr/local/lib/python3.4/site-packages/zeroconf.py", line 1014, in
state_change=state_change,
File "/usr/local/lib/python3.4/site-packages/zeroconf.py", line 931, in fire
h(**kwargs)
File "/usr/local/lib/python3.4/site-packages/zeroconf.py", line 989, in on_change
listener.add_service(*args)
File "/usr/local/lib/python3.4/site-packages/zget/get.py", line 38, in add_service
urllib.urlretrieve(url, output)
File "/usr/local/Cellar/python3/3.4.3_2/Frameworks/Python.framework/Versions/3.4/lib/python3.4/urllib/request.py", line 186, in urlretrieve
with contextlib.closing(urlopen(url, data)) as fp:
File "/usr/local/Cellar/python3/3.4.3_2/Frameworks/Python.framework/Versions/3.4/lib/python3.4/urllib/request.py", line 161, in urlopen
return opener.open(url, data, timeout)
File "/usr/local/Cellar/python3/3.4.3_2/Frameworks/Python.framework/Versions/3.4/lib/python3.4/urllib/request.py", line 463, in open
response = self._open(req, data)
File "/usr/local/Cellar/python3/3.4.3_2/Frameworks/Python.framework/Versions/3.4/lib/python3.4/urllib/request.py", line 481, in _open
'_open', req)
File "/usr/local/Cellar/python3/3.4.3_2/Frameworks/Python.framework/Versions/3.4/lib/python3.4/urllib/request.py", line 441, in _call_chain
result = func(*args)
File "/usr/local/Cellar/python3/3.4.3_2/Frameworks/Python.framework/Versions/3.4/lib/python3.4/urllib/request.py", line 1210, in http_open
return self.do_open(http.client.HTTPConnection, req)
File "/usr/local/Cellar/python3/3.4.3_2/Frameworks/Python.framework/Versions/3.4/lib/python3.4/urllib/request.py", line 1185, in do_open
r = h.getresponse()
File "/usr/local/Cellar/python3/3.4.3_2/Frameworks/Python.framework/Versions/3.4/lib/python3.4/http/client.py", line 1171, in getresponse
response.begin()
File "/usr/local/Cellar/python3/3.4.3_2/Frameworks/Python.framework/Versions/3.4/lib/python3.4/http/client.py", line 351, in begin
version, status, reason = self._read_status()
File "/usr/local/Cellar/python3/3.4.3_2/Frameworks/Python.framework/Versions/3.4/lib/python3.4/http/client.py", line 333, in _read_status
raise BadStatusLine(line)
http.client.BadStatusLine: <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN"

Thanks for the report. It had to do with urllib.urlretrieve(url, output) apparently requesting unescaped URLs under Python 3. It's fixed in version 0.7.


About amdgpu drive loading problem

Loading the amdgpu module in ubuntu 20.04 failed. Procedure
Hardware :Instinct MI250X
After the GPU is powered off, check the dmesg and find the following information:
[  103.397287] [drm] amdgpu:<PHONE_NUMBER>M of VRAM memory ready
[  103.397290] [drm] amdgpu: 48114M of GTT memory ready.
[  103.397304] [drm] GART: num cpu pages 131072, num gpu pages 131072
[  103.397313] ioremap: invalid physical address 1000efff0000000
[  103.397316] amdgpu 0000:0a:00.0: amdgpu: (-12) kernel bo map failed
[  103.397319] [drm:amdgpu_fill_buffer [amdgpu]] ERROR Trying to clear memory with ring turned off.
Is such VRAM size recognition a hardware problem?
I've tried the vramlimit parameter, but it doesn't seem to work.

Is it possible to attach a full dmesg? I haven't seen that error before, but I'll see if I can find anything. It seems to have the right memory/page info. Which ROCm release are you using? Thanks!

Loading the amdgpu module in ubuntu 20.04 failed. Procedure Hardware :Instinct MI250X After the GPU is powered off, check the dmesg and find the following information: [ 103.397287] [drm] amdgpu:<PHONE_NUMBER>M of VRAM memory ready [ 103.397290] [drm] amdgpu: 48114M of GTT memory ready. [ 103.397304] [drm] GART: num cpu pages 131072, num gpu pages 131072 [ 103.397313] ioremap: invalid physical address 1000efff0000000 [ 103.397316] amdgpu 0000:0a:00.0: amdgpu: (-12) kernel bo map failed [ 103.397319] [drm:amdgpu_fill_buffer [amdgpu]] ERROR Trying to clear memory with ring turned off. Is such VRAM size recognition a hardware problem? I've tried the vramlimit parameter, but it doesn't seem to work.

hello, bro!
I got a AMD MI250X GPU card recently. Obviously it was a part from HPE cray EX235a system.
But I got problem in using it now in ubuntu. Probably no driver in ubuntu?
So, do you have drivers or BIOS that can make my card alive? It is writtern D65201-OB Rev13 on GPU.
THANK YOU!!!!

@BiliMiku Were you able to resolve your issue? Thanks!

@BiliMiku Closing ticket since there is no response for a while. If you still require assistance or believe this issue needs to remain open, please re-open the ticket. Thanks!


feature: Make Overdraft disjoint and independent of Money

This makes some breaking changes to how Overdraft works.
Overdraft no longer accepts a value of zero, but instead raises on instantiation. This includes a revert of 7511220, which made Pydantic behavior inline with previous behavior of accepting zero as value for both Money and Overdraft.
Overdraft no longer has a .money attribute, but instead now carries its own .value and .currency attributes.
MoneyParseError is renamed to just ParseError, because it is also raised on instantiation of Overdraft. This was the case prior as well, but it was raised because an instantiation of an Overdraft object always also instantiated a Money object.

Fixes #58.
Fixes #59.

Codecov Report

Merging #62 (5d31bd4) into main (6b6c922) will not change coverage.
The diff coverage is 100.00%.

@@            Coverage Diff            @@
##              main       #62   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            8         8
  Lines         2360      2369    +9
  Branches       409       360   -49
=========================================
+ Hits          2360      2369    +9

Files
Coverage Δ

src/immoney/_base.py
100.00% <100.00%> (ø)

src/immoney/_pydantic.py
100.00% <100.00%> (ø)

src/immoney/errors.py
100.00% <100.00%> (ø)

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Elasticsearch Index names and document count

Requirement: We have multiple indices in our Es cluster and it should receive documents continuously. However sometimes due to document size or other factors, ES doesn't receive documents/messages.
We want to monitor the no of documents per index wise.
Something like this:
Index_name: No of documents.
At present, I am receiving a total no of documents but not per index wise. Not even the name of my index.
Need help!

I got it. using "-- es.indices" I am able to get the desired result.


[ SENSU && Rabbit ] : Timer based re-connection

Guys, Hi. Would a SENSU client-related feature to re-set/re-connect your Rabbit transport every configurable once in a while, makes sense? One use-case would be to re-balance client connections over a VIP faced Rabbit cluster.
Opinions?
Regards, Andrei

This is interesting, maybe create an issue on https://github.com/sensu/sensu-transport with a RabbitMQ or transport configuration example?

Hi, Sean. @ https://github.com/sensu/sensu-transport/issues/11 Regards, Andrei

Closing in favor of https://github.com/sensu/sensu-transport/issues/11 which we'll revisit soon.


chore(repo): update go-playground link to v2 v2.2.0

resolves https://github.com/taikoxyz/taiko-mono/issues/17017

Please update the dependences by go mod tidy.


Remove nptyping as dependency

nptyping is causing warnings in CI and it is no longer worth it to carry as a dependency.

Most usages of nptyping were using the flat NDArray type, which is 1:1 replaceable with np.ndarray
The usages of nptyping that were more informative were associated with copious comments describing the meaning and shape of those tensors (mostly in the cholesky and knitter modules of EF), so it is reasonable to defer to those comments in favor of more palatable type hints
np.typing module contains more powerful type hinting control if we find a need in the future
flake8 was flagging some of our previous type hints as having incorrect format, so this eliminates the confusion associated with the cumbersome nptyping type hints (i.e. using the Shape and * modules correctly can be tedious)

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

17 of 17 (100.0%)  changed or added relevant lines in 6 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.1%) to 84.572%

Totals

Change from base Build<PHONE_NUMBER>:
-0.1%

Covered Lines:
1513

Relevant Lines:
1789

💛  - Coveralls


Publish doca roadmap (with requirements)

We are currently collecting requirements internally and via issues here for doca, and will be putting together a loose road map for the project.  We should publish some form of that on the wiki here for community feedback and input.  I'm filing this mostly to let people know it's a thing :-)
Of the top of my head, without factoring the requirements-gathering that's just started, I expect something along the lines of:

0.x releases will be strictly compatible, but not a long-term support (LTS) release line

We will do a bit more with this to fix easy but important issues
No guarantees at this time that any specific thing will be fixed in 0.x

1.0 release will involve minor breakage, easy migration, and 1.x will be an LTS release line

Need to define what LTS means for doca
Within the 1.x line, we will maintain compatibility
We will need this to continue to document Cloudflare's v4 APIs
Other JSON-base HTTP APIs that are not strictly RESTful can depend on this
Hopefully we can automate the schema edits needed for migration
1.x will probably not support JSON Schema drafts after Draft 04, unless someone wants to take that on and write PRs for it
Fixing the nonstandard usage of "rel": "self" is the kind of breaking change compared to 0.x that we'll do here
Issues like #10 (standards-compliant URI Template variables) need more work on the JSON Schema spec side, and will likely not be addressed in 1.x

2.0 release will be based on JSON Schema Draft 06 and will be more hypermedia-oriented

Hopefully this will also drive ideas for a JSON Documentation Schema specification (json-schema-org/json-schema-spec#136)
Migrating from 1.x to 2.x will likely require manual changes to schemas
Priority will be given to fully RESTful APIs (strict compliance with HTTP semantics, etc.)
Supporting other API approaches may depend on community contributions
This will probably be an experimental release line, which when stable can cut over to a 3.0 LTS release line

Take all of the above with a grain of salt, as I literally made it up while typing without consulting anyone else.
If you have specific asks for future releases, please file them as their own issues.  If you have more general comments, questions, or concerns, please comment here.  When we publish the road map on the wiki I'll ensure everything is addressed in some way and close this issue.

Paging @Relequestual, @habitullence, and (because we're likely to move to Ajv instead of the existing 3rd-party parser library to fix #11, get Draft 06 support, and other reasons) @epoberezkin

Looks like the start of a plan! Great stuff. You already have my feedback prior to properly using it. Pretty much the same.
Still getting the hang of node and webpack... =]

Getting back to this now and working on improving compliance with draft-04.

I've organized as many of the issues as possible into three milestones, which I'll be working on in roughly the following order:

Draft-04 Conformance
Build/Run/Test
API Docs vocabulary
Draft-06 Conformance

I may split Draft-04 Conformance into two milestones: essential support (including documenting what is not supported) and full support (for things that we can't justify supporting right now, and may never be able to justify now that Draft-06 is out).  For now I'm keeping it all together in hopes that we can support everything that is at all reasonable to consider.
I've also labeled the issues by which part of the suite needs work to implement them, which should make the project a bit more approachable for any potential contributors.

Split a few things out of draft-04 conformance to track the things that are actually broken separately from the things that are just not implemented:
Draft-04 no contradctions

Great organisational work!
I probably need to modify our use of doca to make sure we're using a fixed version in production, so we can test changes in develop.
I believe doca currently doesn't specify specific versions of the theme or example loader. I wonder if it should to avoid the situation where an older release of doca no longer works because newer versions of dependancies are not backwards compatible with doca?
Great stuff!

PR #72 proposes a substantial refactoring of the doca suite that will produce a more flexible, extensible, and maintainable architecture (and modernize a few things along the way, since even though doca proper is less than a year old, the loader code is older than that and JS technologies change every year or two anyway).
The most significant reason for the change is that the majority of requested improvements require work on the theme, and currently that work ends up duplicated between the public and internal themes.  We will merge the React components into one UI and handle theming at the CSS / static asset level.
There are a number of other refactorings planned to modularize the schema transformations in the loaders and ensure that at every step, including the final loader output, the result is still a valid, standards-compliant JSON Schema.
I'll leave the PR open for a few days for feedback, and then unless there are objections I will merge it and close this.  It will be a few weeks before I start on the road map tasks in earnest, so there will be additional time to raise concerns and make changes.

Road map published.
For further discussion, file new issues and reference https://github.com/cloudflare/doca/blob/master/ROADMAP.md


i will add list& graphs

Please  follow the issue template given in README to get issue assigned
And also be particular about the project title give to the issue. Don't generalize it. @sujay2306

Title: list Creation , insertion and deletion operation in Python
Name: Sujay KS
Label: Feature Request
Define You:
DevIncept Participant
Contributor
Describe of changes I want to make
I would like to add all the list  implementations methods and operation on the same using python
Type of change
What sort of change have you made:
New feature (non-breaking change which adds functionality)
Approach
I would Define the Operation and explain the implementation with appropriate comment and a read me with detailed labels and approach.

Per one issue, you can work on only 1 script. So decide on what kind of list you would like to work on, change the issue title and template details accordingly. Also, add a tick mark beside devincept participant in template. Do these changes to get this issue assigned. @sujay2306

What's the project title? Please do the changes asked. @sujay2306

Title: Insertion operation in list
Name: Sujay KS
Label: Feature Request
Assignee: ''
Define You:
✅ DevIncept Participant
Contributor
Is your feature request related to a problem? Please describe.
Its a new feature.
Describe the solution you'd like...
Lists are used to store multiple items in a single variable.
Lists are one of 4 built-in data types in Python used to store collections of data, the other 3 are Tuple, Set, and Dictionary, all with different qualities and usage.
Lists are created using square brackets:[ ]
Describe alternatives you've considered?
Approach to be followed (optional):
This program contains  of operations on  a  orderd List:

insert()
remove()
append()
extend ()

So this project title should be "Ordered List". Add this as issue title. @sujay2306

done

Issue assigned, You can proceed. @sujay2306

thank you

Its been 23 days and no PR from you yet. @sujay2306

Its been 28 days. 9th is the last date to accept PR's. If you wouldn't do it by then, obviously you can submit later but points won't be counted towards DCP program. @sujay2306

Exactly 30 days, Max time is 5 days. And you are unassigned from this issue as time is up for DCP program and you had held it for long time. Next time express interest only if you like to submit it timely. Holding an issue for long is never a right thing. @sujay2306


Build up specificity for nested routes.

When adding an array of routes, each route will increase the
specificity instead of using only that of the last route.
Resolves #102.

@tjni you are on the right track here. Specificity of a previously added route was being stomped by a second route, and using an object as a bucket avoids the stomping. However I'm not sure this restores all the functionality we need (there are definitely two tests I have added that do not pass with it) however this is a step in the right direction.

@tjni this seems an incremental fix, but fails on the following assertion:
test("Matches the route with the longer static prefix with nesting", function() {
  var handler1 = { handler: 1 };
  var handler2 = { handler: 2 };
  var router = new RouteRecognizer();

  router.add([{ path: "/", handler: handler1 }, { path: ":post_id", handler: handler1 }]);
  router.add([{ path: "/team", handler: handler2 }, { path: ":user_slug", handler: handler2 }]);

  resultsMatch(router.recognize("/team"), [
    { handler: handler2, params: { }, isDynamic: false },
    { handler: handler2, params: { }, isDynamic: false }
  ]);
});

Which I believe is appropriate to assert https://github.com/emberjs/ember.js/issues/13960 is fixed.

Planning on looking into this in a few hour in the evening, unless someone else is already.

@tjni in fact the test you've added here already passes on master, I believe.

scratch that, my test does not pass in 0.1.5 either. I must have incorrect ported https://github.com/emberjs/ember.js/issues/13960

@tjni I've confirmed you fix with this test: https://github.com/tildeio/route-recognizer/pull/105/files#diff-d4ce617de337dd77d23737176f335d8cR884 Please add it to this PR! I believe that will give us the option for moving forward with this change instead of reverting.

LGTM

@mixonic It turns out we did need to land the test from #85.
I've extracted exactly the routes generated from https://github.com/emberjs/ember.js/issues/14073 and we trigger the same failure as the test from #85.
Here is what Ember generates to feed into route-recognizer:
  router.add([{"path":"/application_loading","handler":"application_loading"}], {"as":"application_loading"});
  router.add([{"path":"/_unused_dummy_error_path_route_application/:error","handler":"application_error"}], {"as":"application_error"});
  router.add([{"path":"/","handler":"application"},{"path":"/loading","handler":"loading"}], {"as":"loading"});
  router.add([{"path":"/","handler":"application"},{"path":"/_unused_dummy_error_path_route_application/:error","handler":"error"}], {"as":"error"});
  router.add([{"path":"/","handler":"application"},{"path":"/test1_loading","handler":"test1_loading"}], {"as":"test1_loading"});
  router.add([{"path":"/","handler":"application"},{"path":"/_unused_dummy_error_path_route_test1/:error","handler":"test1_error"}], {"as":"test1_error"});
  router.add([{"path":"/","handler":"application"},{"path":"/","handler":"test1"},{"path":"/loading","handler":"test1.loading"}], {"as":"test1.loading"});
  router.add([{"path":"/","handler":"application"},{"path":"/","handler":"test1"},{"path":"/_unused_dummy_error_path_route_test1/:error","handler":"test1.error"}], {"as":"test1.error"});
  router.add([{"path":"/","handler":"application"},{"path":"/","handler":"test1"},{"path":"/test2_loading","handler":"test1.test2_loading"}], {"as":"test1.test2_loading"});
  router.add([{"path":"/","handler":"application"},{"path":"/","handler":"test1"},{"path":"/_unused_dummy_error_path_route_test2/:error","handler":"test1.test2_error"}], {"as":"test1.test2_error"});
  router.add([{"path":"/","handler":"application"},{"path":"/","handler":"test1"},{"path":"/test2","handler":"test1.test2"}], {"as":"test1.test2"});
  router.add([{"path":"/","handler":"application"},{"path":"/","handler":"test1"},{"path":"/index_loading","handler":"test1.index_loading"}], {"as":"test1.index_loading"});
  router.add([{"path":"/","handler":"application"},{"path":"/","handler":"test1"},{"path":"/_unused_dummy_error_path_route_index/:error","handler":"test1.index_error"}], {"as":"test1.index_error"});
  router.add([{"path":"/","handler":"application"},{"path":"/","handler":"test1"},{"path":"/","handler":"test1.index"}], {"as":"test1.index"});
  router.add([{"path":"/","handler":"application"},{"path":"/","handler":"test1"},{"path":"/","handler":"test1.index"}], {"as":"test1"});
  router.add([{"path":"/","handler":"application"},{"path":"/","handler":"test1"},{"path":"/","handler":"test1.index"}], {"as":"application"});
  router.add([{"path":"/","handler":"application"},{"path":"/misc_loading","handler":"misc_loading"}], {"as":"misc_loading"});
  router.add([{"path":"/","handler":"application"},{"path":"/_unused_dummy_error_path_route_misc/:error","handler":"misc_error"}], {"as":"misc_error"});
  router.add([{"path":"/","handler":"application"},{"path":"/:param","handler":"misc"}], {"as":"misc"});


BlinkOCR for swift example

When i try to download and run blink ocr example in swift version. This response so many error.
Can you give working version of this or add BlinkOCR started guid via swift

Hi,
since travis build is passing, we don't believe we have issues with the sample itself.
Please try installing git lfs.
If this still doesn't help, please copy here the exact compile errors.
Kind regards,
Jurica.

Here are some:


Removing ScopedMetricsContainer from Python SDK

As StateSampler is now the main context manager, ScopedMetricsContainer is no longer useful.

Run Python Dataflow ValidatesRunner

Passing Dataflow VR: https://builds.apache.org/job/beam_PostCommit_Py_VR_Dataflow_PR/19/

r: @charlesccychen
this has been cleaned internally, so it's now free to be removed.
Sorry to keep piling up reviews on you : ) FWIW this one is just removals.

Run Python Postcommits

Run postcommits

Thank you Pablo! This is a great cleanup.

LGTM.


implement gotham_restful::ResponseSchema for gotham_restful::Response

Hi @msrd0, thank you for gotham and opeapi integration.
Currently this code causes a issue, which I suppose it mustn't right?
the trait bound `gotham_restful::Response: gotham_restful::ResponseSchema` is not satisfied
the trait `gotham_restful::ResponseSchema` is not implemented for `gotham_restful::Response`

#[create]
async fn foo() -> Response {
    Response::new(StatusCode::ACCEPTED, "", None)
}

Maybe dynamic schema could be created?
Like
#[create]
async fn foo() -> Response {
let schema = OpenAPISchema::new(&[HttpStatus:OK, OpenapiSchema::new(....))
Response::new(StatusCode::ACCEPTED, "", None)
}

But in such case there could be created a new type which implement IntoResponce + ResponceShema I guess

Yes I see what you wrote
Maybe its worth to mention in the doc that for response it might be a way to implement your own response type?

Ok thank you for such a fast feedback.
I'll close the issue there's nothing to address anymore.


Scripts in package.json

Question
What are those scripts in package.json good for? Are they needed additionally to build.fsx and if yes when and why are they called? Would highly appreciate to know that 😉.

I deleted them and I got away with it 😄

I think they are for usage from yarn, if someone wants to bypass build.fsx.


Need information how to use this software

how to use this software? how we can run our LCMS raw data file. is there is any videos/ tutorial related to this software?

Not yet, I will put this into my plan


fetchClosedOrders does not return canceled orders

Canceled orders are not returned by fetchClosedOrders.
This is not a real problem, because this is the behavior of some exchanges out there, probably in the future canceled  orders will be returned.

Since this is the behavior of same exchanges, it will probably prevent bugs when people do not rely on it.


[EventHub,ServiceBus] Update user agent strings to follow guideline

at https://github.com/Azure/azure-sdk/blob/master/docs/design/Telemetry.mdk

The linked guidelines have a different format than what was previously decided...
For eg: https://github.com/Azure/azure-sdk-for-js/blob/master/sdk/servicebus/service-bus/src/connectionContext.ts#L42 is the format that was last discussed and decided
cc @bterlson

@jeremymeng This is for Track 2 correct? We have another minor release in the works for which these changes should probably not be applied

Previous one does not conform to the standard (it has two /)
https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/User-Agent

This is for Track 2 correct?

I am resurrecting the changes I made while moving the repo over. It was mimicking similar service bus change.  I am fine with merging this at a future time.

If the 2 / is a problem, then we need to fix this in Service Bus as well. Can you log an issue for that?

If the 2 / is a problem, then we need to fix this in Service Bus as well. Can you log an issue for that?

I fixed that too in this PR. Although I didn't find any affected tests in service bus. Maybe I'll log an issue to add a test.

@jeremymeng Both Event Hubs and Service Bus sdks in the master branch are updated to use the newly released amqp-common library where the limit on the user agent string size has been increased to 512

@ramya-rao-a Thanks for the info.  I saw that the negative test for the limit has been removed so I did the same as well.


feat: Unify duplicate handling in Tasks

Emit warning`
Take first or last?

Append -> Last
PostAppendNoOp -> Last (no warning)
PostAppendCheck -> Last (no warning)
AuthenticateTask -> Take last data (no warning). May take data instead of status.
...

Proposal:
I think we want to tell our users not only that there was a duplicate, but also how we resolved the situation. Maybe something like ...
if let Some(old) = self.output.replace(seq) {
    // Note: `unwrap` can't fail here.
    warn!(?old, new=?self.output.unwrap(), "duplicate data replaced");
}

... ?

Is there any task that should take and keep the first? Seems like it is always the last. Otherwise I really like your proposition!

I think not. It should always be the last.

Hey @soywod! Can you assign me this issue?

Or make me a collaborator so I can do myself, how you prefer :D

Or make me a collaborator so I can do myself

Invitation sent!


[Task]: [2022/06/30] Daily testing and verification of Choreo staging environment for Choreo samples and connector use cases

Connector Name
connectors/samples (Connector Samples/Templates)
Task Description
We need to involve in the daily testing and verification of Choreo staging environment for Choreo samples and connector use cases during Choreo releases. This is for 2022/06/30.

This is done now. Therefore closing this issue.


Support "::" bind operator ?

It would be great if this plugin could support the new bind operator.
Example:
// Binding a function to a context
let log = ::console.log;

Specs:
https://github.com/tc39/proposal-bind-operator

What you mean it not support the new bind operator? This plugin is just for syntax highlighting and it highlight Bind Operator properly for me.


Update on tutorial

This update fix the tutorial to deploy an Rails app on Azure

@JorgeMadson Thanks for your contribution. However we've recently updated the tutorial to repivot to PostgreSQL instead of MySQL and so your change is now out of date. #please-close.


[FR] Emojis and glyphs?

Is it possible to do emoji or glyphs?

Should be doable by including the code points you need in the kha.graphics2.Graphics.fontGlyphs array. Afterwards, Kha will re-create the font bitmap containing all the specified unicode characters.
https://github.com/Kode/Kha/blob/master/Sources/kha/graphics2/Graphics.hx#L141
https://github.com/Kode/Kha/blob/master/Sources/kha/graphics2/truetype/StbTruetype.hx


[ IMPORTANT ] Read Before Posting Bugs / Issues

Bug Reports

Create concise descriptive title
Don't create duplicate issues
include logoutput.log (it's in your bepinex folder)
Include mod list
Steps to reproduce / circumstance

Moved this to Thunderstore's Wiki entry

Rocket Launcher unable to be purchased
LogOutput.log
018f1e52-204a-9550-e980-745b66898f42 - modlist from Thunderstore (note: this is not the only modpack in which the rocket launcher could not be purchased from the terminal store. this is just the most recent pack I made to use with friends)
It appears that the rocket launcher has been somehow removed. The item shows in the store, but is unable to be purchased. It does not recognize the terminal command to buy, and after typing Store > Rocket Launcher (any quantity) and hitting Enter, it just sits there with the words Rocket Launcher still on the terminal. No error sounds from terminal or anything. I did not see anything about it in the Changelog, and have not been able to find any info on the web about it.


[main] Upgrade to latest dependencies

Cron -knative-prow-robot
/cc knative/networking-wg-leads
/assign knative/networking-wg-leads
Produced by: knative-sandbox/knobots/actions/update-deps
Details:
bumping k8s.io/api a1613d7...cd271e7:
  > cd271e7 Update dependencies to v0.23.5 tag
  > a6b2207 Merge pull request # 108139 from liggitt/automated-cherry-pick-of-# 108138-upstream-release-1.23
  > 80b93d4 Revert v1beta1 PodDisruptionBudget select patchStrategy
bumping k8s.io/client-go b425fb6...97582f2:
  > 97582f2 Update dependencies to v0.23.5 tag
bumping k8s.io/code-generator fb849a7...fb849a7:
bumping knative.dev/hack 14f832e...f067737:
  > f067737 Adding code of conduct to reference knative/community's CoC (# 162)
bumping knative.dev/pkg 7f16595...1f7514a:
  > 1f7514a bump k8s deps to v0.23.5 (# 2469)
  > 19a2589 fix coverage settings (# 2471)
  > 2daa86a Electors can provide an initial set of buckets (# 2473)
  > e6e3cf0 Adding code of conduct to reference knative/community's CoC (# 2470)
  > 26a8fea Update community files (# 2468)
bumping k8s.io/apimachinery 276a8a7...276a8a7:

/retest


[HOLD for payment 2023-06-23] [$1000] Email field is not cleared when the new contact method page is opened

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Action Performed:

Go to https://staging.new.expensify.com/settings/profile/contact-methods/new
Enter some email address
Click on Add button
Click on the New contact method button

Expected Result:
The email field is cleared and empty when the new contact method page is opened
Actual Result:
The email field is not cleared and the last entered email is still there
Workaround:
Can the user still use Expensify without this being fixed? Have you informed them of the workaround?
Platforms:

Which of our officially supported platforms is this issue occurring on?

[ ] Android / native
[ ] Android / Chrome
[ ] iOS / native
[ ] iOS / Safari
[x] MacOS / Chrome / Safari
[ ] MacOS / Desktop

Version Number: 1.3.26-1
Reproducible in staging?: y
Reproducible in production?: y
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
NOTE : Also, sometimes adding a contact method after opening the page direct through URL doesn't allow me to open the newly added contact method. Not sure how to reproduce this since this happens randomly.
https://github.com/Expensify/App/assets/43996225/9bc46c47-dd83-4ab9-a343-a593ecbb476d
https://github.com/Expensify/App/assets/43996225/3e896126-0cae-4e19-8b72-09426eba0272
https://github.com/Expensify/App/assets/43996225/9cace447-1079-4a31-bb46-6bcb6d390973
Expensify/Expensify Issue URL:
Issue reported by: @adeel0202
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1685971374351349
View all open jobs on GitHub
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~01b4247ce2f81e2730
Upwork Job ID:<PHONE_NUMBER>162128896
Last Price Increase: 2023-06-09

@kadiealexander sorry, I need to hand this off since I'll be OOO next week. Thanks for taking over!

Not overdue! Please don't forget to check the proposal above @abdulrahuman5196.

@JmillsExpensify I'm going OOO so I've reassigned this to ensure everyone gets paid on time. I've sent out all the offers which you can find here, and @abdulrahuman5196 and @tienifr are due an #urgency bonus for their quick work (here). Thanks so much for your help!

Circling back to issue payouts now.

Alright, summarizing payouts:

Issue reporter: @adeel0202 $250
Contributor: @tienifr $1,500
Contributor+: @abdulrahuman5196 $1,500

I've added the regression test here.

I think we're good here, so closing this one out!


Azure File Upload empty content type

Describe the bug
When attempting to upload a file to Azure OpenAi API, the content type of the file is required.
OpenAI HTTP Error (spotted in ruby-openai 7.1.0): {"error"=>{"code"=>"invalidPayload", "message"=>"The file has no or an empty content type specified."}}
Looks like this might be a TODO item, based on this comment in OpenAI::HTTP
        # Doesn't seem like OpenAI needs mime_type yet, so not worth
        # the library to figure this out. Hence the empty string
        # as the second argument.

In the Azure docs the content type of the file is passed as application/json
curl -X POST https://YOUR_RESOURCE_NAME.openai.azure.com/openai/files?api-version=2024-07-01-preview \
  -H "Content-Type: multipart/form-data" \
  -H "api-key: $AZURE_OPENAI_API_KEY" \
  -F "purpose=batch" \
  -F "file=@C:\\batch\\test.jsonl;type=application/json"

To Reproduce
client = OpenAI::Client.new(
        uri_base: ENV['AZURE_OPENAI_URI_BASE'],
        access_token: ENV['AZURE_OPENAI_API_KEY'], # azure api key
        api_type: :azure,
        api_version: '2024-07-01-preview',
        log_errors: true,
)

file = Faraday::UploadIO.new(File.open('test_file.jsonl'), 'application/json')
res = client.files.upload(parameters: {file: file, purpose: 'batch' })

# results in this error
# OpenAI HTTP Error (spotted in ruby-openai 7.1.0): {"error"=>{"code"=>"invalidPayload", "message"=>"The file has no or an empty content type specified."}}
# Faraday::BadRequestError: the server responded with status 400

Expected behavior
The file should upload to Azure
Currently I'm patching the gem like this, but maybe Faraday::UploadIO class could be passed as an option.
module OpenAI
  module HTTP
    private

    # Override the multipart_parameters method to set the correct content type for .jsonl files
    def multipart_parameters(parameters)
      parameters&.transform_values do |value|
        next value unless value.respond_to?(:close) # File or IO object.

        path = value.respond_to?(:path) ? value.path : nil
        # Set the correct MIME type for .jsonl files
        mime_type = 'application/json' if path&.end_with?('.jsonl')
        Faraday::UploadIO.new(value, mime_type || '', path)
      end
    end
  end
end

Running into this issue as well for .jsonl files.


Add print feature for Conjure survey components

eg it would be nice to have a more readable display of the questions of the survey I imported:

what does "survey.print()" look like?
On Sat, Aug 10, 2024 at 9:05 AM Robin Yerkes Horton <
@.***> wrote:

eg it would be nice to have a more readable display of the questions of
the survey I imported:
image.png (view on web)
https://github.com/user-attachments/assets/9a430423-2ee1-48c8-84ac-6bf71e134503
—
Reply to this email directly, view it on GitHub
https://github.com/expectedparrot/edsl/issues/843, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AADDNMX7UN7O4235PX35OCLZQYF2LAVCNFSM6AAAAABMJ2LRMKVHI2DSMVQWIX3LMV43ASLTON2WKOZSGQ2TSMBXGY4DAMA
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

I think the questions display is fine here, but it would be nice to call just the questions this way, and also a "rich" format of them:

Could also have survey.question_texts.to_list() to do this:

A use case I'm working on: importing some survey data via Conjure, then running a survey sense checking the responses, then posting it all on Coop.
It would be great it Conjure had methods for directly calling question texts and answers so that you can use them as scenarios in sense-checking surveys.


Add options to avoid atexit, and to avoid pinning the libraries in memory (1.1.1)

This is the backport of #7647 to 1.1.1

Ping @t-j-h, @vdukhovni

@mattcaswell Care to push so I can rebase the 1.1.1 version of my PR?

This may have broken the shlibload test onthe VMS . I will investigate...


Running Pyforest on Anaconda3 Jupyter

I am running Python 3.7.4, and Anaconda3.
I have installed pyforest using pip install pyforest
when i run from pyforest import * in my jupyter, i get this error:
ModuleNotFoundError Traceback (most recent call last)
in
----> 1 from pyforest import *
ModuleNotFoundError: No module named 'pyforest'
Also when i run pip freeze i also get this warning
~(master*) » pip3.7 freeze cyrusmuriithi@Cyruss-MacBook-Pro
WARNING: Could not generate requirement for distribution -forest 0.1.1 (/usr/local/lib/python3.7/site-packages): Parse error at "'-forest='": Expected W:(abcd...)
WARNING: Could not generate requirement for distribution -yforest 0.1.1 (/usr/local/lib/python3.7/site-packages): Parse error at "'-yforest'": Expected W:(abcd...)
WARNING: Could not generate requirement for distribution -.forest 0.1.1 (/usr/local/lib/python3.7/site-packages): Parse error at "'-.forest'": Expected W:(abcd...)
WARNING: Could not generate requirement for distribution - forest (/usr/local/lib/python3.7/site-packages): Parse error at "'-===fore'": Expected W:(abcd...)
pyforest==0.1.1
What could be the issue that i cannot run pyforest

Hi @cyrus-muriithi,
please check your /usr/local/lib/python3.7/site-packages folder and remove the corrupt distributions (-forest 0.1.1 etc.).
Then validate that pip freeze is working again.
Maybe you need to re-install pyforest as well. Make sure you're using pip3 for the installation.

I have done exactly that, but when  i run my code (from pyforest import *) in my jupyter,
i still get the error  ModuleNotFoundError: No module named 'pyforest


Usage fails with or without AWS Credentials

I am unable to use this. If I start sls offline without my AWS keys exported, I get this error:
(node:70507) UnhandledPromiseRejectionWarning: CredentialsError: Missing credentials in config
    at ClientRequest.<anonymous> (/my/path/node_modules/aws-sdk/lib/http/node.js:83:34)
    at Object.onceWrapper (events.js:313:30)
    at emitNone (events.js:106:13)
    at ClientRequest.emit (events.js:208:7)
    at Socket.emitTimeout (_http_client.js:718:34)
    at Object.onceWrapper (events.js:313:30)
    at emitNone (events.js:106:13)
    at Socket.emit (events.js:208:7)
    at Socket._onTimeout (net.js:422:8)
    at ontimeout (timers.js:498:11)
    at tryOnTimeout (timers.js:323:5)
    at Timer.listOnTimeout (timers.js:290:5)

But even when I do export my valid AWS credentials, I get this error:
info: PUT /local-bucket/35e6ab220ef8eafb5ae749f77a3924fb 403 10ms -
{ InvalidAccessKeyId: The AWS Access Key Id you provided does not exist in our records.
    at Request.extractError (/my/path/node_modules/aws-sdk/lib/services/s3.js:585:35)
    at Request.callListeners (/my/path/node_modules/aws-sdk/lib/sequential_executor.js:106:20)
    at Request.emit (/my/path/node_modules/aws-sdk/lib/sequential_executor.js:78:10)
    at Request.emit (/my/path/node_modules/aws-sdk/lib/request.js:683:14)
    at Request.transition (/my/path/node_modules/aws-sdk/lib/request.js:22:10)
    at AcceptorStateMachine.runTo (/my/path/node_modules/aws-sdk/lib/state_machine.js:14:12)
    at /my/path/node_modules/aws-sdk/lib/state_machine.js:26:10
    at Request.<anonymous> (/my/path/node_modules/aws-sdk/lib/request.js:38:9)
    at Request.<anonymous> (/my/path/node_modules/aws-sdk/lib/request.js:685:12)
    at Request.callListeners (/my/path/node_modules/aws-sdk/lib/sequential_executor.js:116:18)
    at Request.emit (/my/path/node_modules/aws-sdk/lib/sequential_executor.js:78:10)
    at Request.emit (/my/path/node_modules/aws-sdk/lib/request.js:683:14)
    at Request.transition (/my/path/node_modules/aws-sdk/lib/request.js:22:10)
    at AcceptorStateMachine.runTo (/my/path/node_modules/aws-sdk/lib/state_machine.js:14:12)
    at /my/path/node_modules/aws-sdk/lib/state_machine.js:26:10
    at Request.<anonymous> (/my/path/node_modules/aws-sdk/lib/request.js:38:9)
    at Request.<anonymous> (/my/path/node_modules/aws-sdk/lib/request.js:685:12)
    at Request.callListeners (/my/path/node_modules/aws-sdk/lib/sequential_executor.js:116:18)
    at callNextListener (/my/path/node_modules/aws-sdk/lib/sequential_executor.js:96:12)
    at IncomingMessage.onEnd (/my/path/node_modules/aws-sdk/lib/event_listeners.js:299:13)
    at emitNone (events.js:111:20)
    at IncomingMessage.emit (events.js:208:7)
    at endReadableNT (_stream_readable.js:1064:12)
    at _combinedTickCallback (internal/process/next_tick.js:139:11)
    at process._tickDomainCallback (internal/process/next_tick.js:219:9)
  message: 'The AWS Access Key Id you provided does not exist in our records.',
  code: 'InvalidAccessKeyId',
  region: null,
  time: 2019-05-16T20:45:16.542Z,
  requestId: null,
  extendedRequestId: undefined,
  cfId: undefined,
  statusCode: 403,
  retryable: false,
  retryDelay: 44.172674758005705 }

My S3 initialization code block looks like
// Initialize S3
const {AWS_ACCESS_KEY_ID, AWS_SECRET_ACCESS_KEY, AWS_REGION} = Config.get('AWS')
const s3Config = {
  accessKeyId: AWS_ACCESS_KEY_ID,
  secretAccessKey: AWS_SECRET_ACCESS_KEY,
  region: AWS_REGION
}
if (Config.get('NODE_ENV') === 'debug') {
  // Use local S3 for local development
  s3Config.s3ForcePathStyle = true
  s3Config.endpoint = new AWS.Endpoint('http://localhost:4002')
}
const s3 = new AWS.S3(s3Config)

Hi @sudosoul
Thanks for your report. I guess that your accessKeyId and secretAccessKey are wrong. Please assign ‘S3RVER’ to accessKeyId and secretAccessKey like serverless-s3-local examples.

I'm actually experiencing the same problem following the simple event example and in my S3 initialization it looks like:
 const S3 = new AWS.S3({     s3ForcePathStyle: true,     endpoint: new AWS.Endpoint('http://localhost:4569'),     accessKeyId: 'S3RVER',     secretAccessKey: 'S3RVER',   });

Hi @codetelo
Thanks for your comment. Please tell me about your situation in more detail. I guess you run the following commands. Is it correct ?
Server:
$ cd path/to/simple_event_example
$ npm install
$ sls offline start

Client:
$ curl http://localhost:3000

@ar90n @codetelo
Thanks I was able to get this working by doing the following

Setting the following S3 config options

const s3Config = {
  accessKeyId: 'S3RVER',
  secretAccessKey: 'S3RVER',
  region: 'us-east-2' (can use any region),
  s3ForcePathStyle: true,
  endpoint = new AWS.Endpoint('http://localhost:4002')
}
const s3 = new AWS.S3(s3Config)

Setting the following my serverless.yml

custom:
  s3:
    host: <IP_ADDRESS>
    port: 4002
    directory: /tmp/serverless-s3-offline

I had to manually create the directory for the local s3 bucket

mkdir -p /tmp/serverless-s3-offline/{name-of-bucket-i-want-to-use}
# Example: mkdir -p /tmp/serverless-s3-offline/local-bucket

Finally, I make sure that my app code has the Bucket value set to local-bucket (or whatever I have named the bucket in the step above.

@ar90n you able to perhaps update the README with these steps?
If not, I can open a PR when I have a free chance this week if you like.

Hi @sudosoul
It sounds great! But I still have a doubt. In my environment, the directory for the S3 buckets is created automatically as following.
$ cat serverless.yml
service: serverless-s3-local-example
provider:
  name: aws
  runtime: nodejs8.10
plugins:
  - serverless-s3-local
  - serverless-plugin-existing-s3
  - serverless-offline
custom:
  s3:
    host: <IP_ADDRESS>
    port: 4002
    directory: /tmp//serverless-s3-offline
resources:
  Resources:
    NewResource:
      Type: AWS::S3::Bucket
      Properties:
        BucketName: local-bucket
functions:
  webhook:
    handler: handler.webhook
    events:
      - http:
          method: get
$ ls /tmp//serverless-s3-offline
ls: cannot access '/tmp//serverless-s3-offline': No such file or directory
$ sls offline start &
[1] 2997
starting handler
S3 local started ( port:4002 )
Serverless: creating bucket: local-bucket
error: Error creating bucket. Bucket "local-bucket" already exists
info: PUT /local-bucket 409 18ms -
Serverless: Starting Offline: undefined/undefined.

Serverless: Routes for webhook:
Serverless: GET /

Serverless: Offline listening on http://localhost:3000

$ ls /tmp//serverless-s3-offline
local-bucket

@ar90n
My assumption is that it's getting created because of you have defined the S3 bucket as a resource maybe?
resources:
  Resources:
    NewResource:
      Type: AWS::S3::Bucket
      Properties:
        BucketName: local-bucket

In my case, I don't want serverless framework to create a S3 bucket for me - I want it to use an existing one. So, I don't use that NewResource block in my serverless.yml. I feel like this could be a popular use case (for example, I minimize the amount of infrastructure serverless framework creates & manages, and instead create & manage these infrastructure resources myself via my own preferred IaC tool - Terraform.
Can you try removing it, and letting me know if the bucket still gets created in your /tmp directory.

Hi @sudosoul
Thanks for your reply. I reproduced your situation when I removed the configurations about S3 Bucket from resources section. And I have understood your use-case such as using IaC tools. It is very useful information for me. I’ll  improve README by adding these steps.

I'm having the same issue here (using AWS V3)
My config initialization is
const s3Client = new S3Client({
  region: 'us-east-2',
  accessKeyId: 'S3RVER',
  secretAccessKey: 'S3RVER',
  forcePathStyle: true,
  endpoint: 'http://localhost:4569'
})

and I get

InvalidAccessKeyId: The AWS Access Key Id you provided does not exist in our records.

if I remove the endpoint property, I get

PermanentRedirect: The bucket you are attempting to access must be addressed using the specified endpoint. Please send all future requests to this endpoint.

@gndelia
Thanks for your comment. And I'm sorry for the trouble.
Please try the following codes.
const s3Client = new S3Client({
  region: 'us-east-2',
  credentials: {
    accessKeyId: 'S3RVER',
    secretAccessKey: 'S3RVER',
  },
  forcePathStyle: true,
  endpoint: 'http://localhost:4569'
})

Now I'm trying to upgrade the dependency of serverless-s3-local from AWS SDK v2 to AWS SDK v3.
And it seems that it works correctly in my local environment. So it will be released in these days.

@ar90n Thx! it works


ML 2.8: K-Nearest Neighbour Algorithm (A)

Description
Welcome to 'ML' Team, good to see you here
This issue will helps readers in acquiring all the knowledge that one needs to know about K-Nearest Neighbour.
To get assigned to this issue, add your Batch Numbers mentioned in the spreadsheet of "Machine Learning", this issue is only for Audio content.
Domain : Machine Learning
Points to Note :

The issues will be assigned on a first come first serve basis, 1 Issue == 1 PR.

"Issue Title" and "PR Title should be the same. Include issue number along with it.

Changes should be made inside the Machine Learning/Machine_Learning/Supervised_Machine_Learning Branch.

Follow Contributing Guidelines & Code of Conduct before start Contributing.

This issue is only for 'GWOC' contributors of 'Machine Learning' domain.

To be Mentioned while taking the issue :

Full name
Batch Number
GitHub Profile Link
Which type of Contribution you want to make :

[ ] Audio

All the best. Enjoy your open source journey ahead. 😎
Domain
Machine Learning
Type of Contribution
Audio
Code of Conduct

[X] I follow Contributing Guidelines & Code of conduct of this project.

I would like to contribute to this issue. @Isha307
Name: Riya Srisailam Sailesh
Batch: 4
Profile link: https://github.com/riyasai22
Contribution type: Audio
/assign

/assign

@riyasai22 one issue at a time. Complete the assigned issue previously and do not use /assign tag in future.

I would like to contribute.
Full name: Sanjana Alaham
Batch Number: 6
GitHub Profile Link: https://github.com/sanjana-iyengar
Contribution: Audio

@sanjana-iyengar Issue assigned to you. Go ahead 🚀


added windows 32-bit build option

@mnaamani Thank you! I'll take a look at this and test it when I get a chance.

Pattarapong Raungrum


einweggerat can't be compiled due to missing dependencies

I know you said support would be ignored, but I don't think it was meant to be uploaded unable to be compiled 😅
The "3rdparty-deps" folder mentioned in multiple places isn't in the repository, so einweggerat can't be compiled. I saw some mentions of libretro.h, but if I create the directories and put the libretro.h in the correct folder it still doesn't compile.
So my questions would be:

Was this just mistakenly not commited and is an easy fix or
Is there a way to replicate the needed files to compile this that you know of?

Any help would be appreciated 😄

Okay, I could upload the needed dependancies.

Thanks for adding that, works now! 😄


Add debugger type in extension view

Fixes #14681

@Krzysztof-Cieslak,
Thanks for having already signed the Contribution License Agreement. Your agreement was validated by Microsoft. We will now review your pull request.
Thanks,
Microsoft Pull Request Bot

Thanks! 🍻


Switch from set-output to github environment files

Hello!
Github has changed the way outputs get passed around to now use environment files.
Full details are in this blog post on the topic:
https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
This is a very tiny change that should quieten deprecation warnings in the workflow runner, and hopefully ensure this action continues to work when Github finally gets around to removing set-output.
p.s. Thanks for writing the action, it's dead helpful 💖

Looks good @roc and thanks for contributing! I hadn't noticed this change to be honest, and really appreciate your input! Love that you find this action useful as well :D

@roc I had sadly to revert this PR as it caused problems (see more at #48). Presumably it has something to do with the multi-line responses, I tried to find a solution to that but failed during my own attempts.
Had you tested this change out successfully before submitting? Is there any chance you can submit it with support for multi-line responses too?

Ah I'm so sorry, that did work for us, but we're using v1.25.2.
I've tested with multiline outputs in this branch:
https://github.com/koslib/helm-eks-action/compare/master...roc:helm-eks-action:github-output?expand=1
A successful run using that action is here:
https://github.com/nhsx/standards-registry/actions/runs/3629725119/jobs/6122265491#step:7:72
Though I've noticed there's still an output warning! 🙄
Checking very briefly it seems like these are the only other points where that could be an issue in the action, so it may well be us causing the error at this point
https://github.com/koslib/helm-eks-action/blob/master/.github/workflows/dockerhub.yaml#L15-L19


"Could not retrieve POM" spam

Whenever I execute "./gradlew build", the task :bundles will be followed by a long list of "Could not retrieve POM" followed by a plugin name. The thing is that all these plugins are fetched from a repository that doesn't contain any POM files, which makes the whole task of trying to retrieve POMs a bit unnecessary.
I wonder if there's a way to prevent the task from trying to retrieve POMs?
Thankful for help.

I guess this is what you refer to: https://github.com/stempler/bnd-platform/blob/83a5235bc8afa76d69c4e020cab68b9a2fd800de/src/main/groovy/org/standardout/gradle/plugin/platform/internal/ResolvedBundleArtifact.groovy#L385
What would be your suggestion?
A setting or changing the logging or something else?


Media player / sensors don’t update

Just something I’ve noticed over the last couple of days, our Yoto doesn’t update the media player after a period of time. It just shows Idle even if something is playing. If I open the Yoto app then the media player updates in HASS and shows the currently playing item.
Strangely I can still control the volume from HASS but the state won’t update to Playing until the Yoto app has been opened.
I also noticed this morning that other sensors like Charging or Ambient Light didn’t update either. Both showed old data until I reloaded the configuration.

Anything in logs showing disconnects?

Unfortunately not. I went to the Yoto just now, saw it showed idle so plugged a card in and let it play. Still showed idle in HASS. So I turned debug logging on and then opened the Yoto app.
It immediately updated to 'playing' in HASS (this was around 16:49/16:50). No logs listed for Yoto at all until I opened the app but then these followed in the debug file. Almost like the player wasn't sending any commands until I used the app to wake it? Even though it was technically awake as it was playing.
Anything else I can check for you?
2024-09-09 16:50:14.459 DEBUG (Thread-9181 (_thread_main)) [yoto_api.YotoMQTTClient] yoto_api - MQTT Topic: device/y2ENCAR0tJ9EVzZKlo6bVvQv/status
2024-09-09 16:50:14.459 DEBUG (Thread-9181 (_thread_main)) [yoto_api.YotoMQTTClient] yoto_api - MQTT Message: {"status":{"battery":3995,"powerCaps":"0x08","batteryLevel":100,"batteryTemp":0,"batteryData":"0:0:0","batteryLevelRaw":81,"free":3708948,"freeDMA":62506,"free32":84610,"upTime":113429,"utcTime":1725897010,"aliveTime":181410,"activeCard":"qQAag","cardInserted":1,"playingStatus":5,"qiOtp":0,"dnowBrightness":100,"errorsLogged":186,"nightlightMode":"off","temp":"964:24:311","als":4095}}
2024-09-09 16:50:14.459 DEBUG (Thread-9181 (_thread_main)) [yoto_api.YotoMQTTClient] yoto_api - Message is for: y2ENCAR0tJ9EVzZKlo6bVvQv
2024-09-09 16:50:22.054 DEBUG (Thread-9181 (_thread_main)) [yoto_api.YotoMQTTClient] yoto_api - MQTT Topic: device/y2ENCAR0tJ9EVzZKlo6bVvQv/response
2024-09-09 16:50:22.054 DEBUG (Thread-9181 (_thread_main)) [yoto_api.YotoMQTTClient] yoto_api - MQTT Message: {"status":{"events":"OK","req_body":""}}
2024-09-09 16:50:22.054 DEBUG (Thread-9181 (_thread_main)) [yoto_api.YotoMQTTClient] yoto_api - Message is for: y2ENCAR0tJ9EVzZKlo6bVvQv
2024-09-09 16:50:22.115 DEBUG (Thread-9181 (_thread_main)) [yoto_api.YotoMQTTClient] yoto_api - MQTT Topic: device/y2ENCAR0tJ9EVzZKlo6bVvQv/events
2024-09-09 16:50:22.115 DEBUG (Thread-9181 (_thread_main)) [yoto_api.YotoMQTTClient] yoto_api - MQTT Message: {"repeatAll":false,"streaming":false,"volume":4,"volumeMax":16,"playbackWait":false,"sleepTimerActive":false,"eventUtc":1725897018,"trackLength":359,"position":298,"cardId":"qQAag","source":"card","cardUpdatedAt":"2021-11-17T13:05:17.856Z","chapterTitle":"Iron Man: Invincible!","chapterKey":"8z89rR-l14","trackTitle":"Iron Man: Invincible!","trackKey":"8z89rR-l14","playbackStatus":"playing"}
2024-09-09 16:50:22.115 DEBUG (Thread-9181 (_thread_main)) [yoto_api.YotoMQTTClient] yoto_api - Message is for: y2ENCAR0tJ9EVzZKlo6bVvQv
2024-09-09 16:50:22.116 DEBUG (MainThread) [custom_components.yoto.coordinator] yoto - Updating Card details for:  qQAag
2024-09-09 16:50:27.175 DEBUG (Thread-9181 (_thread_main)) [yoto_api.YotoMQTTClient] yoto_api - MQTT Topic: device/y2ENCAR0tJ9EVzZKlo6bVvQv/events
2024-09-09 16:50:27.176 DEBUG (Thread-9181 (_thread_main)) [yoto_api.YotoMQTTClient] yoto_api - MQTT Message: {"trackLength":359,"position":303,"cardId":"qQAag","repeatAll":false,"source":"card","cardUpdatedAt":"2021-11-17T13:05:17.856Z","chapterTitle":"Iron Man: Invincible!","chapterKey":"8z89rR-l14","trackTitle":"Iron Man: Invincible!","trackKey":"8z89rR-l14","streaming":false,"volume":4,"volumeMax":16,"playbackStatus":"playing","playbackWait":false,"sleepTimerActive":false,"eventUtc":1725897023}
2024-09-09 16:50:27.176 DEBUG (Thread-9181 (_thread_main)) [yoto_api.YotoMQTTClient] yoto_api - Message is for: y2ENCAR0tJ9EVzZKlo6bVvQv
2024-09-09 16:50:32.225 DEBUG (Thread-9181 (_thread_main)) [yoto_api.YotoMQTTClient] yoto_api - MQTT Topic: device/y2ENCAR0tJ9EVzZKlo6bVvQv/events
2024-09-09 16:50:32.225 DEBUG (Thread-9181 (_thread_main)) [yoto_api.YotoMQTTClient] yoto_api - MQTT Message: {"trackLength":359,"position":311,"cardId":"qQAag","repeatAll":false,"source":"card","cardUpdatedAt":"2021-11-17T13:05:17.856Z","chapterTitle":"Iron Man: Invincible!","chapterKey":"8z89rR-l14","trackTitle":"Iron Man: Invincible!","trackKey":"8z89rR-l14","streaming":false,"volume":4,"volumeMax":16,"playbackStatus":"playing","playbackWait":false,"sleepTimerActive":false,"eventUtc":1725897028}
2024-09-09 16:50:32.225 DEBUG (Thread-9181 (_thread_main)) [yoto_api.YotoMQTTClient] yoto_api - Message is for: y2ENCAR0tJ9EVzZKlo6bVvQv
2024-09-09 16:50:37.341 DEBUG (Thread-9181 (_thread_main)) [yoto_api.YotoMQTTClient] yoto_api - MQTT Topic: device/y2ENCAR0tJ9EVzZKlo6bVvQv/events
2024-09-09 16:50:37.341 DEBUG (Thread-9181 (_thread_main)) [yoto_api.YotoMQTTClient] yoto_api - MQTT Message: {"trackLength":359,"position":315,"cardId":"qQAag","repeatAll":false,"source":"card","cardUpdatedAt":"2021-11-17T13:05:17.856Z","chapterTitle":"Iron Man: Invincible!","chapterKey":"8z89rR-l14","trackTitle":"Iron Man: Invincible!","trackKey":"8z89rR-l14","streaming":false,"volume":4,"volumeMax":16,"playbackStatus":"playing","playbackWait":false,"sleepTimerActive":false,"eventUtc":1725897033}
2024-09-09 16:50:37.341 DEBUG (Thread-9181 (_thread_main)) [yoto_api.YotoMQTTClient] yoto_api - Message is for: y2ENCAR0tJ9EVzZKlo6bVvQv

What I find is the Mqtt server stops sending updates after some time.  We have to poke the server to wake it up again.
Right now some logic exists to do that after an interval.   Sounds like it may need to be shorter.   I'm finding mine works fine, but may have other factors.

You mean on the Yoto integration? The scan interval is just the default, 60 mins.
Would setting it lower give me a more responsive update on the media player side of things? Basically I want to tie automations to playback start and stop so ideally want to get it fairly reactive.

Shouldn't be needed, play back should come in real time.   That polling interval is just configuration items not playback.
I'll double check the interval that it kicks off the "request playback" update.  Like opening the app I wrote in something to ping the server if it hasn't had an update in awhile.  Since server seems to fall asleep after awhile.

Have you tried this out recently?  Do you still have this issue?

Actually, no, it appears to be fixed. I've noticed it's working and responsive now so that's great thanks.

Hello, I think I am seeing something similar to this.  I am noticing the state of the player is not always updating in HA.  However, if I adjust the volume using the slides in HA, that seems to trigger an immediate update of the state.

Could you open a new issue since this one is closed? Logs would help as well.

Ah, of course.  I created #149.  There are no errors in my logs to share.


Confused CK status

I'm confused about ck status:
$ ck status
Your version is outdated: V1.6.3
New available version   : V1.6.1

Just execute "ck pull all --kernel" to update CK and all repositories (if you installed CK from GIT) or visit https://github.com/ctuning/ck for more details ...

This could be because I installed CK both from PyPi and in the canonical way (by cloning).

It's a bug. Also, I currently check version via Internet via manually changed JSON file on cknowledge.org - I should change it and check version directly from github.com/ctuning/ck ...

Fixed in the latest release (1.6.4). Also now checking version directly from setup.py from GitHub ...
Can you please check and close this ticket...

No longer getting this message in 1.6.11:
anton@localhost / $ ck version
V1.6.11
anton@localhost / $ ck status
Your version is up-to-date: V1.6.11

Closing...