st2 execution resume get Unable to identify resource with id error

Hi,
I've created an inquiry in a flow and the flow is pausing.
st2 execution list --status pausing
+----------------------------+-----------------------+--------------+---------+----------------------------+---------------+
| id                         | action.ref            | context.user | status  | start_timestamp            | end_timestamp |
+----------------------------+-----------------------+--------------+---------+----------------------------+---------------+
| + 5a9ce728198c9744e8f98d68 | dev.test_inquiry | st2admin     | pausing | Mon, 05 Mar 2018 06:43:51  |               |
|                            |                       |              |         | UTC                        |               |
+----------------------------+-----------------------+--------------+---------+----------------------------+---------------+

Then I try to resume it:
st2 execution resume 5a9ce728198c9744e8f98d68
ERROR: 404 Client Error: Not Found
MESSAGE: Unable to identify resource with id "['5a9ce728198c9744e8f98d68']". for url: http://<IP_ADDRESS>:9101/v1/executions/['5a9ce728198c9744e8f98d68']

So a pausing flow cannot be resumed with the cli above? Thanks.

I see what's the root cause:
The flow is changed to pausing, then it will be changed to paused. Only paused flow can be resumed.
It take several minutes for the flow to be changed to paused, that's why I got the error from the CLI. It shouldn't be an issue.


Confused on how Client Config Characteristic works

The GattAttributes class contains a constant for the Client Config and it is defined as:
"00002902-0000-1000-8000-00805f9b34fb"
However, using a simple python app to connect to the device and dump the services and characteristics revealed one with:
"00002a29-0000-1000-8000-00805f9b34fb"
I do not see one that matches the config characteristic exactly. Perhaps it is different per tagger ? The code is using this constant to get a GattDescriptor from the telemetry characteristic and then writes out a value to enable notifications. Why does it do this?
For reference, I am using bluepy as the python library on a raspberry pi. The documentation for Descriptor is not helpful. http://ianharvey.github.io/bluepy-doc/descriptor.html

Nevermind! I was able to write to the descriptor and enable notifications.


Robocopy Language stable 2021-10-01

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

Changelog
Add a changelog entry for this PR by answering the following questions:

What's the purpose of the update?

[ ] new service onboarding
[ ] new API version
[ ] update existing version for new feature
[ ] update existing version to fix swagger quality issue in s360
[ ] Other, please clarify

When are you targeting to deploy the new service/feature to public regions? Please provide the date or, if the date is not yet available, the month.
When do you expect to publish the swagger? Please provide date or, the the date is not yet available, the month.
If updating an existing version, please select the specific language SDKs and CLIs that must be refreshed after the swagger is published.

[ ] SDK of .NET (need service team to ensure code readiness)
[ ] SDK of Python
[ ] SDK of Java
[ ] SDK of Js
[ ] SDK of Go
[ ] PowerShell
[ ] CLI
[ ] Terraform
[ ] No refresh required for updates in this PR

Contribution checklist:

[ ] I commit to follow the Breaking Change Policy of "no breaking changes"
[ ] I have reviewed the documentation for the workflow.
[ ] Validation tools were run on swagger spec(s) and errors have all been fixed in this PR. How to fix?

If any further question about AME onboarding or validation tools, please view the FAQ.
ARM API Review Checklist

Applicability: :warning:
If your changes encompass only the following scenarios, you should SKIP this section, as these scenarios do not require ARM review.

Change to data plane APIs
Adding new properties
All removals

Otherwise your PR may be subject to ARM review requirements. Complete the following:

[ ] Check this box if any of the following appy to the PR so that the label "ARMReview" and "WaitForARMFeedback" will be added by bot to kick off ARM API Review.  Missing to check this box in the following scenario may result in delays to the ARM manifest review and deployment.

Adding a new service
Adding new API(s)
Adding a new API version
-[ ] To review changes efficiently, ensure you are using OpenAPIHub to initialize the PR for adding a new version. More details, refer to the wiki.

[ ] Ensure you've reviewed following guidelines including ARM resource provider contract and REST guidelines. Estimated time (4 hours). This is required before you can request review from ARM API Review board.

[ ] If you are blocked on ARM review and want to get the PR merged with urgency, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.

Breaking Change Review Checklist
If any of the following scenarios apply to the PR, request approval from the Breaking Change Review Board as defined in the Breaking Change Policy.

[ ] Removing API(s) in a stable version
[ ] Removing properties in a stable version
[ ] Removing API version(s) in a stable version
[ ] Updating API in a stable or public preview version with Breaking Change Validation errors
[ ] Updating API(s) in public preview over 1 year (refer to Retirement of Previews)

Action: to initiate an evaluation of the breaking change, create a new intake using the template for breaking changes. Addition details on the process and office hours are on the Breaking change Wiki.
Please follow the link to find more details on PR review process.

I have performed the robocopy step to get Language/stable/2021-10-01 in dev folder. I have ignored the changed in common.json file.

@heaths , @annatisch Please review this PR. I have copied the stable 2021-10-01 language APIs. Will raise a new PR to have new 2022-07-15_preview API with some changes.

@weshaggard @ArthurMa1978 seems the "Swagger Avocado" check wasn't required before, or at least the error it found here didn't trigger. Can we get that fixed?
@lmazuel can you override? Since it's a required check, I cannot squash merge.

@heaths this Avocado looks like an incompatibility between using the "dev" directory and what the tool is expecting to find under a version folder. I'm not sure when the check became required but can you please file an issue against Avocado for this case?
cc @raych1
In the meantime, I will override the failure and merge the PR.

@heaths this Avocado looks like an incompatibility between using the "dev" directory and what the tool is expecting to find under a version folder. I'm not sure when the check became required but can you please file an issue against Avocado for this case?
cc @raych1
In the meantime, I will override the failure and merge the PR.

Thanks for the explanation. Will do. What repo would that be in? the azure-sdk-tools?

Submitted https://github.com/Azure/azure-sdk-tools/issues/3711


Unexpected behavior with Vuex

Please check the sandbox https://codesandbox.io/s/030wm2806n
I got undefined  undefined instead of select option, and in my application I actually get an error "TypeError: Cannot read property 'id' of null" ( I tried, but I couldn't reproduce it)
So, I assume vuex is wrapping my objects with observables, and that is the problem

Hey! I think you got some things wrong.

The fullName function should handle the case where the name and fullName don’t exist. Otherwise, you will get undefined undefined because inside ${name} ${fullName} both of those values are undefined given data is null. Thus trying to get name from null is not an existing value.

If you use Vue-Multiselect for selecting objects you have to make sure that the preselected value has the same structure as the options you pass. Because it will pass the whole selected option into the mutation.

See the fixed version below and compare it with your code. Cheers!
https://codesandbox.io/s/4x7v2v53jw


Emit telemetry consistently

In order to maximise the value of podtato-head for those learning from the exemplar implementations.
Then it is also appropriate to include telemetry signal generators.
These should include but are not limited to:

Logs
Traces
Metrics

I think it would be ideal to add the OpenTelemetry collector as a sidecar in each pod, or a daemonset in the cluster.
We could then demonstrate the collector exporting to open and proprietary backend analysis services like Jaeger. Vendors might build on this and demo connections to their own backends.

I agree it is important to show tooling available openly without any vendor influence.
To that end I think we could do the following:

Introduce structured logging through some open library ( zap/klog/logrus) and print to stdout
Use Opentracing libraries to produce spans to the agent sidecar you mentioned.
Enable the Prometheus metrics endpoint by adding a service monitor and some simple rules in the configuration manifests.


feat(a11y): add aria invalid/describedby attrs to json schema form

A new prop errorsDescriedById was added into <JsonSchemaForm /> to support rendering aria-invalid and aria-describedby on form controls.
this fix FTI-5660

Description

Motivation and Context

How Has This Been Tested?

Screenshots (if appropriate):
Checklist

My PR contains...

[ ] No code changes (src/ is unmodified: changes to documentation, CI, metadata, etc.)
[ ] Dependency changes (any modification to dependencies in package.json)
[ ] Bug fixes (non-breaking change which fixes an issue)
[ ] Improvements (misc. changes to existing features)
[ ] Features (non-breaking change which adds functionality)

My changes...

[ ] are breaking changes to a public API (config options, System API, major UI change, etc).
[ ] are breaking changes to a private API (Redux, component props, utility functions, etc.).
[ ] are breaking changes to a developer API (npm script behavior changes, new dev system dependencies, etc).
[ ] are not breaking changes.

Documentation

[ ] My changes do not require a change to the project documentation.
[ ] My changes require a change to the project documentation.
[ ] If yes to above: I have updated the documentation accordingly.

Automated tests

[ ] My changes can not or do not need to be tested.
[ ] My changes can and should be tested by unit and/or integration tests.
[ ] If yes to above: I have added tests to cover my changes.
[ ] If yes to above: I have taken care to cover edge cases in my tests.
[ ] All new and existing tests passed.

@davidma415  Need a re-review for this PR too due to the correction of errorsDescribedById ❤


[SPARK-42846][SQL] Remove error condition _LEGACY_ERROR_TEMP_2011

What changes were proposed in this pull request?
Removed error condition _LEGACY_ERROR_TEMP_2011, removed dataTypeUnexpectedError, typeUnsupportedError, and replaced them with SparkException.internalError.
Why are the changes needed?
It is impossible to trigger the error from user space.
Here I changed dataTypeUnexpectedError to internalError, since typeSoFar argument will always be either:

NullType if this is the first row or
Some type which is returned by the inferField function(which is a valid type).

Here I changed typeUnsupportedError to internalError, since:

in this function call, the exception will be caught and
in this function call, a valid desiredType will always be passed.

Here and here I changed dataTypeUnexpectedError to internalError, since there is a type signature here which prevents child.dataType from being unexpected type.
Does this PR introduce any user-facing change?
No.
How was this patch tested?
Build passing.
Was this patch authored or co-authored using generative AI tooling?
No.

@ivanjevtic-db Do you have an account at OSS JIRA? If so, please, leave some comment in https://issues.apache.org/jira/browse/SPARK-42846 otherwise submit request:

+1, LGTM. Merging to master.
Thank you, @ivanjevtic-db.

@ivanjevtic-db Congratulations with your first contribution to Apache Spark!


Why between twice nearby notify  have a dealy ?

I want to use nearby notify function. but  i met a question.

Then, i turn off my screen ,  and  i turn on screen again.   i can't recive url notify again.
if  i delay 1 ~ 2 min , then turn on screen again.  i can recive url notify again.
i don't understand this.
my phone infomation
nexus 7
Android 6.0.1
Google Play service 10.2.98(436-146496160)
and
meizu pro6
andorid 6.0
Google Play Service 10.0.84(448-137749526)
other phone   only show url notify once.
nexus 9
andorid 7.1.1
Google Play service 10.2.98(446-146496160)
i get this problem for a week, please help me .
what should i do?
Look forward to your reply.

Do you select the notification? If so, Android guidelines say that you must
remove it. It will return but as you noticed, there is a slight delay.
Scott
On Fri, Feb 10, 2017 at 12:54 AM, SonnySwolf<EMAIL_ADDRESS>wrote:

I want to use nearby notify function. but i met a question.

Then, i turn off my screen , and i turn on screen again. i can't recive
url notify again.
if i delay 1 ~ 2 min , then turn on screen again. i can recive url notify
again.
i don't understand this.
my phone infomation
nexus 7
Android 6.0.1
Google Play service 10.2.98(436-146496160)
and
meizu pro6
andorid 6.0
Google Play Service 10.0.84(448-137749526)
other phone only show url notify once.
nexus 9
andorid 7.1.1
Google Play service 10.2.98(446-146496160)
i get this problem for a week, please help me .
what should i do?
Look forward to your reply.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/google/eddystone/issues/207, or mute the thread
https://github.com/notifications/unsubscribe-auth/ABAbuomDz-1_aDZIZ6jEJL9x2NDIHqQqks5rbCXQgaJpZM4L9I--
.


topViewContent

it's not working
not show anything

Which version are you using @vitrinh282? In latest version, there's not such prop, for changing the top, you should use topContent.
Closing this for instance, but let me know if it did work.


Add tests for Z, ZM, and M variants of WKT

Add tests and fix any issues when dealing with WKT with 3/4 dimensions.

example 49 in the tests is an example where the generated cql2-text and cql2-json is silently dropping the Z coordinate


Error operatorPrecedence' from 'pyparsing' - Google Colab

Hello @rizavelioglu,
first of all I want to thank you for your repository for those of us who are starting to learn IA in robotics.
I am trying to run google colab but unfortunately there is an error in the pyparsing library, I tried to install the version you used in the execution of your google colab but I could not solve the error.

I hope you can help me because your repository is very good to learn.
thank you very much
Raúl

Hello Raúl,
Thank you for your comments!
By the time of writing the notebook (~June 2020), Colab was on Python3.6 and as of today (January 2022) the default Python version on Colab is Python3.7. Therefore, I would guess that the error somehow relates to that. Actually, the Duckietown project owners has faced with this same issue (see the issue at duckietown repo). One of the creators states in the comments that this is a "dependency error", but sadly the issue was not resolved.
However, I found a workaround! I have updated the notebook such that all dependencies are installed in Python3.6 and the scripts are run in Python3.6. Apparently, everything works!
Hope this helps!
Cheers

Thank you very much for your help and quick response @rizavelioglu .
I will continue training the duckie by modifying some hyperparameters.
As a last request could you guide me with this last error that occurs when I try to run the test on my local machine.
I have installed the gym-duckietown project and I'm running it through anaconda3 and everything works fine when I run for example basic _control.py
But when I try to run the trained (following the instructions) and with the weights loaded I get the following error:

I think I need that library as it doesn't find anything related to Zlogger, I tried to install the same requirements like for example zuper-typing-z5==5.1.1 but it didn't work either.
do you have any idea how i can fix it?
Thank you very much again for your time and help
Best regards

I was able to solve this error by installing zuper-commons-z6 6.1.7
Thanks again for your help
best regards


Tests for function parameters

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
No tests are performed if given parameters match requirements.
Describe the solution you'd like
A clear and concise description of what you want to happen.
Implement test of passed function-parameters, and raise matching exceptions.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.

Also add unit testing.

ToDo:

[ ] Function parameters testing
[ ] Unit Tests for every function

No unit tests are implemented, see #15


felix

hi, do you know where I can contact Felix Antoine/Lefela4?
Its urgent and critical

If you don't stop putting random comments on my github projects I will have to block you.

i also need


ctx.text_align not passed to app draw functions consistently

Describe the bug
We had issues with our app not rendering as expected, apparently a bit random, in terms of text alignment. Work around was to explicitly set ctx.text_align and ctx.text_baseline every time.
Version: v1.8 & v1.9.0-beta1 (probably earlier too)
To Reproduce
Not sure - just use the badge and then run app.
Expected behavior
Expect ctx context to be passed into draw consistently each time - hence only need to set things that you want to be different to 'default'
Additional context
Reporting now as I've seen it on CaffeineJitters too and have a suggestion of where the issue lies.
I think the modules/app_components/menu.py draw function modifies ctx.text_align and ctx.text_baseine without saving and restoring.

Second this, I was seeing some strange behaviour when testing some code yesterday. Your idea that something isn't saving and restoring the state feels right.


Add a drop down arrow of profile section

Describe the feature
I can add a drop down arrow of the profile section please assign me
Add ScreenShots

Record

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

@arghadipmanna101 please checkout my pull request


Dragging folder from file explorer collapses the node

#27346
Dragging an expanded entry will collapse it, but dragging a collapsed one doesn't expand it. I think it shouldn't collapse it if possible.

I'm guessing this is by design, so it's easy to the folder to ones below it.

Yes it is.


Design and Implement howto extend McThings

Someone could upload a pip package like:
mcthings-cool-houses
with more things related to houses, and McThings must load it and make the things available.

After read http://pluginbase.pocoo.org/ it seems that we need:
«Setuptools based plugins are very useful to extend libraries from other libraries.»
The way to go:
https://packaging.python.org/guides/creating-and-discovering-plugins/
The first approach must be the simplest one: "Using naming convention".
The goal is to discover the plugins installed, the ones called mcthings_, load them and make visible its things to be used (mcthings will be extended with the new things).

Let's create a new package mcthings-drawings that it will add a new Thing called Sphere implemented using https://minecraft-stuff.readthedocs.io/en/latest/minecraftdrawing.html#minecraftstuff.MinecraftDrawing.drawSphere
If everything goes ok, we will add several new Things created using MinecraftDrawing. With it, we can create richer scenes!

https://github.com/martinohanlon/minecraft-stuff/blob/master/LICENSE is MIT so great to reuse it!

There are samples which you can use it as reference as https://pypi.org/project/flask-talisman/ With this plugin, when you are using Flask, it protects you against some attacks:
from flask import Flask
from flask_talisman import Talisman

app = Flask(__name__)
Talisman(app)

So the plugin changes the Flask behaviour, extending it. In our case, the code must be something like:
from mcthings.scene import Scene
from mcthings_drawing import Sphere

def main():
    try:
        mc = mcpi.minecraft.Minecraft.create(address=MC_SEVER_HOST, port=MC_SEVER_PORT)
        Scene.server = mc

        mc.postToChat("Building a scene with several things")
        pos = mc.entity.getTilePos(mc.getPlayerEntityId(BUILDER_NAME))
        pos.x += 1

        sphere = Spehre(pos)
        sphere.build()

We have it: https://pypi.org/project/mcthings-drawing/0.0.1/
I am going to try to  use all in a notebook!

All have worked from a notebook as expected:

And also the persistence works! We can load the scene from a file:

The plan is to have another repository called mcthings_extra in which includes Things from the samples in:
https://github.com/arpruss/raspberryjammod-minetest/tree/master/raspberryjammod/mcpipy

Mostly done, I will close it once the mcthings-extra repo with some example is created.

Probably the best thing is to merge mcthings_drawing in mcthings_extra, in order to have just one repo for third party Things!

Extra Things repository working!

So in order to extend McThings there are two repository samples doing it. And using the extra things is as easy as included both libraries. So time to close this ticket!

McThings Drawing has been included in McThings and removed the repository. So we have two repositories now, the core and the extras.


Fixes code snippets to use SplunkCimLogEvent

Merged it into develop

w00h00
On Mon, May 18, 2015 at 5:03 PM Shakeel Mohamed<EMAIL_ADDRESS>wrote:

Closed #1 https://github.com/splunk/splunk-plugin-eclipse/pull/1.
—
Reply to this email directly or view it on GitHub
https://github.com/splunk/splunk-plugin-eclipse/pull/1#event-307939928.


Bug in template for ICS events in Reminder format

I want to have the ICS events formatted in reminder format for tasks, but there is a bug in ICS. I want the data to be encoded like this:
(@[[yyyy-MM-DD]] hh:mm) task text
But adding the ]] screws up the format replacement. See in the screenshot the yyyy-MM-DD.

Here's how it resolves when I take out the brackets:

Hi @stoweboyd , that field is only meant for the time format. It's failing because we've got superfluous content in there that the moment library formatting is getting tripped by, as expected.
For more complicated templates, I suggest using Templater as other users have.
For example:
<%*
var events = await app.plugins.getPlugin('ics').getEvents(moment(tp.file.title,'YYYY-MM-DD'));
events.sort((a,b) => a.utime - b.utime).forEach((e) => {
    const calendar = e.icsName.replace(" ","-");
    const callUrl = e.callUrl ? ` [${e.callType}](${e.callUrl})` : '';
    const location = e.location ? ` 📍 *(${e.location})*` : '';
    const eventDate = moment.unix(e.utime).format('yyyy-MM-DD'); // Convert utime to the date format desired
    const eventTime = moment.unix(e.utime).format('HH:mm'); // Convert utime to the time format desired
    tR += `- [ ] (@[[${eventDate]]]] ${eventTime}) **${e.summary}**${location}${callUrl} #${calendar}\n`; // Format as per user request
    if (e.description) {
        const inlineDescription = e.description.replace(/(?:\r\n|\r|\n)/g," ").replace(/\s{2,}/g," ");
        tR += `    - ${inlineDescription}\n`;
    }
})
%>


[BUG] Could not resolve the package

Describe the bug
Error: Could not resolve the package 'google_fonts' in 'package:google_fonts/google_fonts.dart'.
lib/main.dart:2:8: Error: Not found: 'package:google_fonts/google_fonts.dart'
import 'package:google_fonts/google_fonts.dart';

I got this error when i try to use the package. I installed with the version ^1.1.0 .
To Reproduce
Steps to reproduce the behavior:

Install the package with the version ^1.1.0
Use GoogleFonts with whatever font you want (i tried it with poppins & lato)
Run the app
See error

Expected behavior
The package work as intended and change my text font in the UI

I fix this by manually run flutter pub get command and restarting my app. It seems like the pub get command not working properly when i save the pubspec file before.


Seeming race condition with job status

We've scaled up our disco usage a fair amount and I've been seeing a few strange errors when the cluster is under heavy load.  It looks like jobs semi randomly have a JobError exception thrown - the more load on the cluster the more it seems to happen.
It appears that this is happening inside of job.wait() - When tracking down what was happening, I added some extra code to disco/core.py / check_results and found that if the poll off the job status happens right around the instant the job itself finishes all its tasks, it's sometimes receiving a status = 'dead'.  To remedy this I added some code to retry one more time and check the status after 1 second before actually throwing the exception, and upon retry, the status is consistently coming back as 'ready'.  So basically, a completing job is sometimes being labelled as 'dead' before the 'ready' state.  Doing this retry allowed us to hack around the issue.
Additionally, (not sure if this is related), when the cluster is under very heavy load, I can see the same thing happen with the status indicator for jobs - as they complete they first turn red (for failure), then green (for completion/ready).
One note - we are still on 0.5.3, so please let me know if this is known and has been fixed in a later version

Yes. I have seen this issue. The race condition is with the following code in job_event.erl:
    case is_process_alive(Pid) of
        true  -> active;
        false -> dead
    end;

If the job has finished successfully, we still respond that the job is dead.

We see this error quite often as well. I was wondering if there is any update on when this will be fixed?
I would like to look at it myself but I'm not good with Erlang and not yet very familiar with the Erlang part of the disco codebase.
Am I correct to say that the job coordinator sends a ready message to do_update and then exists. Then before do_update is actually called to process the message do_get_status gets called by python which notifies the job coordinator is dead?
If this is correct I guess the way to fix it is either checking again in python with a delay (easy, I can fix that), or for the job coordinator to wait for a message from do_update to notify that it received it before exiting.
Or am I completely wrong here?

Locally, to avoid most of the issues with this (at least to make the client job code not think the job died), I changed disco/core.py to replace the check_results function with this:
def check_results(self, jobname, start_time, timeout, poll_interval, recurse=False):
    try:
        status, results = self.results(jobname, timeout=poll_interval)
    except CommError as e:
        status = 'active'

    if status == 'ready':
        return results
    if status != 'active':
        if not recurse:
            time.sleep(5)
            return self.check_results(jobname, start_time, timeout, poll_interval, recurse=True)
        else:
            raise JobError(Job(name=jobname, master=self), "Status {0}".format(status))
    if timeout and time.time() - start_time > timeout:
        raise JobError(Job(name=jobname, master=self), "Timeout")
    raise Continue()

I realize this is really suboptimal and hackey, but I was running into issues daily on our busy cluster and now very rarely see the issue, so its good enough for me until the actual backend gets fixed.


Feature/adf ci cd auto publish

Type of PR

Documentation changes
Code changes
CI-CD changes

Purpose

The Purpose of this PR is to- Create a sample CI/CD For Azure Data Factory that can eliminate the Manual Publish and allow Auto Publish of ARM Templates that can be used for a fully automated E2E deployment on ADF in multiple environments.

Does this introduce a breaking change? If yes, details on what can break
NO
Author pre-publish checklist

[X] Added test to prove my fix is effective or new feature works
[X] No PII in logs
[X] Made corresponding changes to the documentation

Validation steps

Follow steps in README

Issues Closed or Referenced

References #issue_number

Hi @manjitsin, thanks for the contribution.
While reviewing the PR, I see that it has quite a lot of overlap with the following Microsoft documentation on the same topic https://learn.microsoft.com/en-us/azure/data-factory/continuous-integration-delivery-improvements.
I would request you to review the above document and identify areas where we can add value. One idea that comes to my mind is that we can provide a deployable solutions to showcase this functionality i.e. the sample would have a deploy.sh or something which can spin-up an ADF and Azure DevOps environment.
Please feel free to ping me for further discussion.


duplicate or queued responses?

Hi, I have noticed intermittently that sometimes messenger acts as if it is responding to the same input multiple times.  And it looks when I check the webhook that multiple entries are flowing through.
What causes this and is there something that can prevent the queuing when something has successfully been read and an output has been returned through the smooch API?

Webhooks will automatically retry if your server returns certain errors, or fails to respond. Check out our retry policy. Are you doing any type of processing in your webhook handler that could cause a delay before returning 200 OK?

Hi, I had thought of that.  I use Runscope to tell the response posting to my webhook URL and the response time.
All 200 and < 15 seconds, average 8 seconds.

Is it typically the longer requests that end up duplicated? Do you know?
It's possible that network latency + external factors could time out the request even though you report a < 20s response time on your server. I would suggest returning 200 OK immediately when the payload is received by your server, and processing the request in the background somewhere. If that doesn't work, if you have specific instances (timestamps or message ids, as well as your Smooch app id) that I can take a look at, I can dig a bit deeper to see what error is returned on our side


fix: HASS Discovery - Name - First character fix

Apply a fix for better Naming in Home Assistant. Add a replace of the first character if it is a hyphen -, understore _ or space
by cleaning up the first character, in case of location is empty or unused, like in default payload. Will then clean up the this characted.
fixes #162

Pull Request Test Coverage Report for Build 478380948

1 of 1 (100.0%)  changed or added relevant line in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.009%) to 24.769%

Totals

Change from base Build 478099928:
0.009%

Covered Lines:
1939

Relevant Lines:
7997

💛  - Coveralls

Pull Request Test Coverage Report for Build 478380948

1 of 1 (100.0%)  changed or added relevant line in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.009%) to 24.769%

Totals

Change from base Build 478099928:
0.009%

Covered Lines:
1939

Relevant Lines:
7997

💛  - Coveralls

@billiaz This fixes the problem but IMO it's not the best way. You are replacing _- chars but them could be also .,; or any other as templates have not a strict form, it works for @chilicheech but not in all others templates.
@chilicheech If you are not using location why don't just remove it from the template?

@billiaz This fixes the problem but IMO it's not the best way. You are replacing _- chars but them could be also .,; or any other as templates have not a strict form, it works for @chilicheech but not in all others templates.
@chilicheech If you are not using location why don't just remove it from the template?

@billiaz Ok I have the solution to this. Add a new placeholder %nn that stay for nodeName and use the function getNodeName() to retrive it. That was the function used before and essentially will return location-name or name if location is not defined. Also the default template then will become %nn_%o

@billiaz Ok I have the solution to this. Add a new placeholder %nn that stay for nodeName and use the function getNodeName() to retrive it. That was the function used before and essentially will return location-name or name if location is not defined. Also the default template then will become %nn_%o

Supersided by #218

Supersided by #218


Clear-History does not remove all history

This was reported via LiveFyre comments for Clear-History
In PowerShell 5 on Windows 10 (at least) the 'Clear-History' cmdlet does not clear any session history, and certainly not the on-disk history. None of the options seem effective, it appears to be entirely borked and quite the security vulnerability. Googling around it appears broken for a couple years at least, with some workarounds found:
Steps to reproduce

Run: Remove-Item (Get-PSReadlineOption).HistorySavePath
Run: [Microsoft.PowerShell.PSConsoleReadLine]::ClearHistory()
End the current session

See other online discussions:

https://blogs.msdn.microsoft.com/stevelasker/2016/03/25/clear-history-powershell-doesnt-clear-the-history-3/
https://thetechremix.com/2017/02/22/tip-clear-powershell-history-in-windows-10/
https://stackoverflow.com/questions/13257775/powershell-clear-history-doesnt-clear-history

After local testing:
Clear-History does clear the History from the session. Try doing Clear-History then run Get-History. However, that does not clear the history that PSReadline is using. So up-arrow recall of commands still has history information.
Environment data
Name                           Value
----                           -----
PSVersion                      5.1.16299.98
PSEdition                      Desktop
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}
BuildVersion                   10.0.16299.98
CLRVersion                     4.0.30319.42000
WSManStackVersion              3.0
PSRemotingProtocolVersion      2.3
SerializationVersion           <IP_ADDRESS>

sdwheeler,
I'm not sure this is an actual error, the PowerShell history and Command Buffer are two different things, this seems to be by design, for what appear to be historical reasons.
If you're interested in seeing who has access to this, check out https://docs.microsoft.com/en-us/windows/console/console-buffer-security-and-access-rights You can also reduce your buffer size to zero in the PowerShell properties menu .

I understand that history and command buffer are different. However, before PSReadline. there was no difference. So the user experience has changed and the implications of this change are not well documented. At a minimum, the documentation for History and PSReadline should call this out. But it is also worth discussing whether PSReadline could/should be changed to address these concerns.

I would not want the Clear-History command to clear my PSReadLine history.  However, I could see PSReadLine adding a command Clear-PSReadLineHistory (to make it more obvious) and I could see updating the Clear-History docs to point out Clear-PSReadLineHistory command to fully wipe out history.  That said, I'd want a confirm impact of high on that new command.  I'd be lost if my PSReadLine history were accidentally deleted.  :-)

Yes, I think adding Clear-PSReadlineHistory and cross-documentation would be the right thing to do.

Not to go all too crazy, but would a flag for clear-history make more sense than a new cmdlet? We already have ways to clear the history, and ways to clear the buffer; something like clear-history -includebuffer might make more sense with less redundancy.

The help file that needs to be updated is the one for Clear-History. It should mention that the command only clears the current session's history and if the user if using a module such as PSReadLine that handles the line editing experience (i.e. implements function PSConsoleHostReadline), that those modules often store their own history.  And they provide their own commands to clear their history.

Why would you not want Clear-History to clear both?
Under what circumstances are you trying to clear only your PowerShell history buffer, but not the ON-DISK cache created by PSReadLine.
Given that PSReadline is built in and required for PowerShell 6, why are we still keeping the history separate? What's the point of having multiple copies of history anyway?

A PowerShell host (like PSES) may not be using PSReadLine so having the built-in Clear-History assume that PSReadLine is always loaded is not a good thing.  Plus, I can always remove the PSReadLine module.  OTOH the cmdlet could check for the presence of PSReadLine.  That might be OK but such a command should have a confirm impact of high.  My PSReadLine history is treasure to me.  :-)

I think this is an interesting discussion.  For PSCore6, we deliberately went with a very simple ReadLine implementation in the ConsoleHost deferring all the previous capabilities to PSReadLine so it gets loaded automatically.  Perhaps we can add a -Scope type parameter to Clear-History that PSReadLine can plug into.  cc @lzybkr

@SteveL-MSFT @daxian-dbw Please triage the issue

The repro step mentioned  [Microsoft.PowerShell.PSConsoleReadLine]::ClearHistory(), I just want to clarify that ClearHistory() clears the history for the current running session only. It doesn't affect the history file.
If we want Clear-History to clear the PSReadLine history file as well, all it needs to do is to remove the history-save file, which can be queried by Get-PSReadLineOptions.

I think we should think about how to integrate the History cmdlets with PSReadLine to provide a cohesive experience since we've already married the two together.

Have any plans to move some code from PSRL to Engine (like coloring)? In the case we could do the same for some other  features.


consider moving to gitlab.org or a similar open source git hosting software

Currently, we have no plan to move. We need a clear benefit to justify the cost of moving. Free software fundamentalism is not enough for us.


states_daily.json does not have previous day's data ...

https://api.covid19india.org/states_daily.json / states_daily.json file does not seem to have the most recent data. Right now ( Apr 6th ), this seems to have data only till Apr 4th. How frequently is this supposed to be updated ?

I'm facing the same issue. Why is this not being updated even though the commit message says it has been updated for both 5th and 6th April data?

Seems to be fixed now.

Yes, it has been fixed. @Sdaas this issue can be closed now.


 IF YOU DO NOT FOLLOW THE FORMAT OR MAKE A GENERIC TOKEN REQUEST YOUR ISSUE WILL BE DELETED WITHOUT COMMENT
YOUR JUSTLIST MUST FOLLOW THE JSON SPECIFICATION
https://github.com/justswaporg/justlists/example.justlists.ts
Checklist

[x] I understand that this is not the place to request a token listing.
[x] I have tested that my JustList is compatible by pasting the URL into the add a list UI at justswap.org.
[x] I understand that filing an issue or adding liquidity does not guarantee addition to the justlists website.

Please provide the following information for your token.
JustList URL must be HTTPS.
JustList URL:
JustList Name:
Link to the official homepage of the JustList manager:

Tronpad

Sorry, your issue will be closed as you did not submit your information in the correct format.


Migrate extra DSpace-CRIS "Live Import" sources to DSpace core

DSpace-CRIS (built/maintained by 4Science) has a number of Live Import sources which are not yet available in DSpace core.
These may include:

Scopus
CrossRef
CiNii
NASA/ADS
Web of Science
VuFind
OpenAIRE (by Author and Title)

If possible, we should work with the 4Science team to contribute these back to core code, so that they can be available to and maintained by the entire DSpace community.

@atarix83 : As promised today, I'd appreciate it if you (or someone from your team) could estimate the effort to give this code back to the core codebase.  While I've tentatively flagged this as "medium priority", an estimate might help me better explain why we might want to prioritize this more highly for 7.1.  If there are any questions, let me know!


Conveyor belt using behavior tree

Change WalkBehavior so it checks if the NPC is on top of an item with an use type of move: true, and behave differently in that case.

[ ] The entities might be going too fast.

Another thing... Do we want the NPCs to look towards west and east randomly while going on the conveyors? It seems to be the case in the Ruby server.

There seems to be a bug regarding this, actually.
Apparently, conveyor belts give entities the special ability to walk through solid walls.

I took the liberty of changing a few nitpicky things, but the bug remains.
It seems to happen because the conveyor belt can move entities in directions that they aren't facing, which bypasses the solid wall check.
An easy solution would be to implement an additional solid wall check before the conveyor belt movement section.

I took the liberty of changing a few nitpicky things, but the bug remains. It seems to happen because the conveyor belt can move entities in directions that they aren't facing, which bypasses the solid wall check. An easy solution would be to implement an additional solid wall check in the conveyor belt movement section.

I was afraid of introducing bugs so I didn't do much code shortening myself. I will look into clipping into the walls today since I am done with university stuff.

Hello. I have added a fix for the wall clipping problem. I also changed the architecture of the conveyor belt behavior so it can be composed into other behavior types easily. You can see the work for that in https://github.com/boraini/brainwine/pull/8. Tell me if you want it.

Probably a better idea yeah, feel free to include it.


Latex drawer tested using notebook in binder

Summary
Fixes #6371 .
Details and comments
Following #4544 , this PR enable testing Latex drawer using notebook in Binder. The flow of the testing follows exactly from #4544 .  The binder of this PR can be accessed at https://mybinder.org/v2/gh/TharrmashasthaPV/qiskit-terra/binder_test_branch?filepath=test%2Fipynb%2Flatex_tester.ipynb. The release notes have been added.
Files added/modified

Renamed test/ipynb/mpl_tester.ipynb to test/iplynb/snapshot_tester.ipynb - The notebook that will run in Binder that includes tests for both mpl and latex drawers.
Added apt.txt - This file installs the required latex dependencies.
Modified postBuild - This file now also collect and installs the latex qcircuit.sty package.
Added test/ipynb/latex/references - This folder contains all the reference images.
Added test/ipynb/latex/test_circuit_latex_drawer.py - The file that contains all the latex tests.

Hey @TharrmashasthaPV thanks for all the work on this!
If you take a look at #6672 you can see how the results.py was adjusted to deal with both circuit and graph type snapshots. I think you can adjust the results.py file in a similar way here so that we don't have to duplicate the whole file just for the latex tests.
On another note, since we are expanding the snapshot testing I wonder if we should keep the mpl_tester.ipynb and latex_tester.ipynb separate or combine them into a single snapshot_tester.ipynb. My gut feel is put them all in one notebook, but open to further discussion 🤔

Hey @TharrmashasthaPV thanks for all the work on this!
If you take a look at #6672 you can see how the results.py was adjusted to deal with both circuit and graph type snapshots. I think you can adjust the results.py file in a similar way here so that we don't have to duplicate the whole file just for the latex tests.
On another note, since we are expanding the snapshot testing I wonder if we should keep the mpl_tester.ipynb and latex_tester.ipynb separate or combine them into a single snapshot_tester.ipynb. My gut feel is put them all in one notebook, but open to further discussion 🤔

Hi @javabster . That makes sense. But a small thing is that if we also put the latex testing in results.py it would force us to put the mpl and the latex tests together in a single notebook since calling results.py in the notebook would essentially run both mpl and latex tests together. If we want to have separate notebooks, alternatively, we could define different functions in results.py for all three different test and then use them in the notebooks appropriately. I don't have any strong preferences here. So any idea on which would be better?

Hey Tharma if I understand correctly you need to run the actual test file (e.g. %run "mpl/circuit/test_circuit_matplotlib_drawer.py") in the notebook first to populate the test_results.json, and then that json is what is read by results.py. In which case if we wanted to keep 2 separate notebooks we could still use one  results.py and only call the corresponding test file (so %run "mpl/circuit/test_circuit_matplotlib_drawer.py" in the mpl_tester.ipynb and %run 'latex/test_circuit_latex_drawer.py' in the latex_tester.ipynb)

As for the 1 notebook vs 2 notebook decision I am on the fence 🤔
On the one hand, keeping it all in one notebook means that you only have to open one binder link instead of 2 when you want to run the snapshot tests (and the binders take some time to load so fewer binder links the better maybe?)
On the other hand, if you're making changes to only the latex drawer maybe it's not necessary to run the mpl snapshots as well (and vice versa), in which case maybe it's better to keep them in separate notebooks.
@TharrmashasthaPV and @enavarro51 as you both have done a lot of work in the respective drawers, which do you feel would work best in your workflows?

@TharrmashasthaPV While looking at this PR in order to answer @javabster's query above, I took a look at some of the images, and when I download and view these in my viewer, they seem to be fairly low-res and are cropped around the edges. Is this something that can be fixed?

@javabster @TharrmashasthaPV In regards to whether to combine, I'm generally in favor of a single image tester, for mpl, latex, and graph (and maybe someday pulse as well). When working on only one drawer, the fact that the other images come up should not be an issue and should not increase load time significantly. And when working on multiple drawers, it would be helpful to see all at once.
In fact, though maybe not for this PR, I think that the tests for latex and mpl should be all in one file. They only differ by the circuit_drawer call in most cases. There are some, like iqx_colors that are mpl only, but almost all others are in common. So doing two circuit_drawer calls per test would eliminate having to add tests in 2 places. So in the best of all possible worlds, I see this.
ipynb
    image_tester.ipynb
    results.py
    circuit
        test_circuit_drawer.py
        references
    graph
        test_graph_drawer.py
        references

@TharrmashasthaPV While looking at this PR in order to answer @javabster's query above, I took a look at some of the images, and when I download and view these in my viewer, they seem to be fairly low-res and are cropped around the edges. Is this something that can be fixed?

@enavarro51 I think the low resolution of the images are because the scale at which it is printed is small. The scale is exactly as would be drawn in a notebook. If we need larger resolved images, then I think we might have to change the value of scale in the drawer for the tests which I am not sure if we would want to do. I am open to any suggestions on that front. As for the cropping, it seems like an issue in utils._trim(). The method crops the image very close to the boundaries. I will fix that in my next commit.
@javabster I too agree with @enavarro51 in putting them into a single notebook. You were right in saying that we might not have to run the mpl snapshot tests every time we are testing the latex tests. I guess we can tackle that if we have separate methods for mpl_circuit, mpl_graph and latex in results.py, so that we can call only the required method.

@TharrmashasthaPV Looks like you got the cropping issue taken care of. It would be nice if the latex images were higher res, but I don't know how to do that through jupyter either. I know the mpl images come out much better res. Ultimately I don't suppose it's a problem if you're comparing one low-res image with another. They should still match if produced by the same code.

Hey @TharrmashasthaPV I just pushed a small change to make the results function a generic one that takes an argument instead of having 3 separate functions to do similar things and also tidied up the notebook a bit.

Hey @TharrmashasthaPV I just pushed a small change to make the results function a generic one that takes an argument instead of having 3 separate functions to do similar things and also tidied up the notebook a bit.

That is great! Thanks.

This is getting there thanks @TharrmashasthaPV!
As you've changed the name of the binder test to snapshot_tester can you update the contributing guidelines to reflect the new name that people will have to put in the links they use

Yeah, sure. I will make sure to update that. :)

Awesome work.
For a following PR, would be possible to have a py version of snapshot_tester.ipynb? With #6427 , CI could run snapshot_tester.py. What do you think?

Thanks! I think currently we are just saving the output images at
https://github.com/Qiskit/qiskit-terra/blob/0cdacec2ee3b26a96b1d7bbb0def6b7eb66ac5b4/azure-pipelines.yml#L255-L256
but not comparing them in CI. I think it certainly would be better to have comparison in CI and so I too feel we should have a snapshot_tester.py. I'll be sure to push it in a following PR.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 1 (0.0%)  changed or added relevant line in 1 file are covered.
347 unchanged lines in 9 files lost coverage.
Overall coverage decreased (-0.6%) to 81.971%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

qiskit/visualization/utils.py
0
1
0.0%

Files with Coverage Reduction
New Missed Lines
%

qiskit/visualization/qcstyle.py
1
34.62%

qiskit/circuit/quantumcircuit.py
2
94.19%

qiskit/extensions/quantum_initializer/uc.py
2
88.65%

qiskit/pulse/library/waveform.py
3
90.38%

qiskit/circuit/tools/pi_check.py
4
87.04%

qiskit/visualization/circuit_visualization.py
11
55.71%

qiskit/extensions/simulator/snapshot.py
13
47.06%

qiskit/visualization/utils.py
17
82.83%

qiskit/visualization/latex.py
294
7.89%

Totals

Change from base Build<PHONE_NUMBER>:
-0.6%

Covered Lines:
49486

Relevant Lines:
60370

💛  - Coveralls

In principle, despite its age, this PR still looks mostly appropriate to me, and not too far off merging.  I suspect that the conflicts are mostly a minor change in this PR conflicting with another minor styling change in the LaTeX output since this PR was opened.
@1ucian0 - you assigned yourself before.  Can you finish off driving this over the line?  If you write the small changes you think were required, I can do the final review.

This can probably be closed as we are moving to CI visual testing in #9961


[Docs] Confusion about Volume-Servers and Volume-Files when talking about ‚Volumes‘

I'm trying to come up with a system to use seaweed fs as my home nas server. The exact case and my current understanding can be found at the bottom of this issue.
Now I try to grasp the concept of replication between volume-servers.
The problem for me is, that the usage of 'Volume' in the docs seems to be switching between meaning 'Volume-Files inside a Volume Server' ans 'one or more Volume Servers'
Additionally comes the confusion, that the term 'Volume' is traditionally associated with direct HDDs or SSDs.
I think we, as a community, should clarify this somehow in the docs.
If I find a working solution for my setup, I'll happily contribute my example case to the docs to help future readers.
My Current Setup
I have a 4-Bay Storage Appliance with 2x4TB HDDs and 2x 6TB HDDs.
Each pair is mirrored in ZFS and combined to a pool in ZFS, of around 8 TB.
My SeaweedFS Plan with Question: Is this understanding correct? :
I found the following

weed master has Param "volumeSizeLimit"

= max  size of volume files
(can be larger than 30GB because of large_disk version of seaweed FS supporting volume greater than 30GB)

weed volume has Param max number of volumes

= Max number of volume files
Set so that HDDs do not overfill

=> Therefore I need 4 Volume-Servers (1 per HDD), configured like this:
1. Per 4 TB HDD : 50 GB per Volume-File * 80 Volumes
2. Per 6 TB HDD: 50 GB per Volume-File * 120 Volumes
=> Replication Setup: 001 - Questions

Is it a problem, that two of the underlying HDDs have greater capacity???
Is this the correct mental model or is it planned like this, that each HDD or SSD needs it's own volume server?

The docs say for Fixing Replication

If one replica is missing, there are no automatic repair right away. This is to prevent over replication due to transient volume sever failures or disconnections. In stead, the volume will just become readonly. For any new writes, just assign a different file id to a different volume.

Multiple Questions

If one Replica is missing => Does this mean a missing HDD in one volume server or a missing Volume file?
Instead, the volume will just become readonly => Again: Does this mean a specific volume file or a volume server?

the term 'Volume' is traditionally associated with direct HDDs or SSDs.

Not used this way. This was the source of confusion. Some readers simply have the wrong impression that SeaweedFS can not support files larger than 30GB, because each volume is default to 30GB.
The word volume is always the volume file. volume server is the server.

Is it a problem, that two of the underlying HDDs have greater capacity???

This is fine.

Is this the correct mental model or is it planned like this, that each HDD or SSD needs it's own volume server?

This is correct.
Also, for convenience, One volume server can support multiple directories.

If one Replica is missing => Does this mean a missing HDD in one volume server or a missing Volume file?

One missing volume file.

Instead, the volume will just become readonly => Again: Does this mean a specific volume file or a volume server?

One specific volume file.


fix(ExtractComputedReturns): use explicit Record type

This PR fixes the following errors I was seeing.
app/client/node_modules/@vue/runtime-core/dist/runtime-core.d.ts:437:20 - error TS2344: Type 'Function & T[key]["get"]' does not satisfy the constraint '(...args: any) => any'.
  Type 'Function' provides no match for the signature '(...args: any): any'.

437     } ? ReturnType<T[key]['get']> : ReturnType<T[key]>;
                       ~~~~~~~~~~~~~

app/client/node_modules/@vue/runtime-core/dist/runtime-core.d.ts:437:48 - error TS2344: Type 'T[key]' does not satisfy the constraint '(...args: any) => any'.
  Type 'T[keyof T]' is not assignable to type '(...args: any) => any'.
    Type 'T[string] | T[number] | T[symbol]' is not assignable to type '(...args: any) => any'.
      Type 'T[string]' is not assignable to type '(...args: any) => any'.

437     } ? ReturnType<T[key]['get']> : ReturnType<T[key]>;
                                                   ~~~~~~

Can you provide how to reproduce the error that you were seeing?
Can you add a test on the test-dts folder?

npm init -y
npm install vue@next typescript

tsconfig.json:
{
  "compilerOptions": {
    "target": "es2020",
    "module": "commonjs"
  }
}

index.ts:
import 'vue';

Also in the TypeScript playground pasting the existing definition of ExtractComputedReturns.
Playground Link

I'm not really sure what test I should add. This type is an internal utility so it's not exported from the index file.

When i run script
tsc --target ESNext --module ES6 --outDir esm

Will see this error  for me too.
> tsc --target ESNext --module ES6 --outDir esm

node_modules/@vue/runtime-core/dist/runtime-core.d.ts:437:20 - error TS2344: Type 'Function & T[key]["get"]' does not satisfy the constraint '(...args: any) => any'.
  Type 'Function' provides no match for the signature '(...args: any): any'.

437     } ? ReturnType<T[key]['get']> : ReturnType<T[key]>;
                       ~~~~~~~~~~~~~

node_modules/@vue/runtime-core/dist/runtime-core.d.ts:437:48 - error TS2344: Type 'T[key]' does not satisfy the constraint '(...args: any) => any'.
  Type 'T[keyof T]' is not assignable to type '(...args: any) => any'.
    Type 'T[string] | T[number] | T[symbol]' is not assignable to type '(...args: any) => any'.
      Type 'T[string]' is not assignable to type '(...args: any) => any'.

437     } ? ReturnType<T[key]['get']> : ReturnType<T[key]>;
                                                   ~~~~~~

typescript version: ^3.9.2
tsconfig.json:
{
  "compilerOptions": {
    "declaration": true,
    "esModuleInterop": true,
    "lib": [
      "esnext", "dom"
    ],
    "module": "commonjs",
    "moduleResolution": "node",
    "noEmitOnError": true,
    "noFallthroughCasesInSwitch": true,
    "noImplicitReturns": true,
    "noUnusedLocals": true,
    "noUnusedParameters": true,
    "downlevelIteration": true,
    "outDir": "./dist",
    "types": [
      "node", "jest"
    ],
    "target": "es5",
    "typeRoots": [
      "./types",
      "./node_modules/@types"
    ]
  },
  "include": [
    "src/**/*"
  ]
}

Currently vue-next is not compatible with typescript 3.9
There's a PR open https://github.com/vuejs/vue-next/pull/1106

Should be fixed after #1106. Thanks for the PR though!


Mark captures that don't use DXR/EI as optimized

If a capture file does not use DXR or EI, mark it as optimized. This
makes log messages more consistent and prevents unnecessary tracking
work done by Dx12ResourceValueMapper during replay.
Also make DXR/EI optimizer log messages more consistent.

CI gfxreconstruct build queued with queue ID 56031.

CI gfxreconstruct build # 2643 running.

CI gfxreconstruct build # 2643 passed.

CI gfxreconstruct build queued with queue ID 578.

CI gfxreconstruct build # 2694 running.


Prepare bridge support

Flattened the datamodel a bit more as we've discovered that the datamodel was not flexible enough to cover for bridges.
Better to handle extraction of nodes, clusters and attributes into devices and entities from HA itself with a discovery schema comparable to e.g. Zwave.

Removed the devicetype and rootnode instance layers.
Added some helper attributes to discover if you're dealing with a bridge/bridged device

This one is ready, tested with HA (PR following up next)


Is it possible to change the offset/position of the Ratings? (Sick, Good, Bad, Shit)

Describe your problem here.
Hi! So I'm trying to figure out if there's a way to change the offset of the Ratings but I couldn't find anything.
Is this possible? Any help is appreciated!
Are you modding a build from source or with Lua?
Lua
What is your build target?
Windows x64
Did you edit anything in this build? If so, mention or summarize your changes.
I have not, using Lua.

Ratio + Find it in the settings

Ratio + Find it in the settings

Sorry I should I have been more clear. Is it possible to do using Lua? Like a setProperty() or something similar to that?

Like may be no

May it help you? https://gamebanana.com/questions/45942


Updated Install.md and README files

Updated Install.md and README files related to the new CMake build
procedures involving the Avalon Toolkit, InChI and PostgreSQL cartridge

thanks Paolo.


Update data.json

Hi Eugene,
I just tried to upload my obsidian plugin which is also using OpenAI and doing so I realised that my API key was exposed
While doing a search on github to check if this would be the case for other people I found your repo
Apparently obsidian automatically creates a data.json file inside the plugin folder upon saving , so I wanted to flag this to you before ill-intentioned people figure this out

Wow thanks for catching this and taking the time to make the PR 🙏


ci/arm-13.dat: do not check board tlsr8278adk80d

Summary
Telink toolchain is special and not added to the CI yet.
Impact
Telink boards CI.
Testing
CI.

Close, let's track by https://github.com/apache/incubator-nuttx/pull/6179 instead.


Support lifecycle hook

I would like to suggest that provide that lifecycle hook of the generator, like afterAll, beforeAll, beforeEach and afterEach.  Now, actually, we have afterEach when we pass sh in template files.
However, in the case, we might be run the script after all code generated. I hope that we can set it at .hygen.js, like
module.exports = {
    afterAll: (context) => {
        ...
    }
}

Now, we can do it a workaround as prescript && hygen <name> <action> && postscript. But still hope that we could have the hook. That might be also helpful on  #175.
Thanks!

One other way to create a makefile to help wrap the before and after generation. But adding a hook on this would be very useful.

Intersting. So you want a "post" action after all generation has completed. The way I solve it usually is have:
component/
   new/
      0_create-component.t
      1_inject-dependency.t
      zz_post-action.t        <-- this action runs a shell script (in this case 'yarn install') and it appears in the end

Does this work for you?

@jondot It's better that we have a script hook rather than putting a mock post-action.t file. The reason is that we don't want to generate a file without the template we need. That means that we still need a process to delete all script placeholder files.

Adding on to this, having lifecycle hooks for the following would be helpful

before arg parsing
before generation but just after arg parsing
before/after hooks for each generated template/file
after all generation is done

I'm not sure where how the end user would configure this but for context we've run into a situation where we want to run a script after a certain generator has completed but only if a specific option was passed or if a specific file was generated/modified (instead of skipped for example).


Update DscResource.Template

Update appveyor.yml to support publishing of examples

This change is

@PlagueHO Another small one to review.


Fix return data type of ascent

The ascent function returns a data type int64. However, the minimum and maximum values of the image array are 0 and 255, respectively. The data type should be uint8.

Reference issue

What does this implement/fix?

Additional information

We might want to delay this PR because of #15608/#15607 which just came out. And here we can make sure that we set the types properly.

This is a good suggestion, not because merging this would somehow interfere with those PRs, but because technically this PR is a backwards compatibility break (e.g., img += 10 may now overflow). So not changing misc.ascent but making a new datasets.ascent use uint8 would be better.

Friendly reminder @boeleman

Thanks for the reminder. I just changed the datasets.ascent method.

closing as superseded by #17606


Register

@JuliaRegistrator register

Registration pull request created: JuliaRegistries/General/97153
Tip: Release Notes
Did you know you can add release notes too? Just add markdown formatted text underneath the comment after the text
"Release notes:" and it will be added to the registry PR, and if TagBot is installed it will also be added to the
release that TagBot creates. i.e.
@JuliaRegistrator register

Release notes:

## Breaking changes

- blah

To add them here just re-invoke and the PR will be updated.
Tagging
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v1.0.0 -m "<description of version>" e34931c8316883dea449774b5b7d19260bb66d24
git push origin v1.0.0

@JuliaRegistrator register

Registration pull request created: JuliaRegistries/General/97155
Tip: Release Notes
Did you know you can add release notes too? Just add markdown formatted text underneath the comment after the text
"Release notes:" and it will be added to the registry PR, and if TagBot is installed it will also be added to the
release that TagBot creates. i.e.
@JuliaRegistrator register

Release notes:

## Breaking changes

- blah

To add them here just re-invoke and the PR will be updated.
Tagging
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v1.0.1 -m "<description of version>" 766ef6ee360e89b99b74215f8d050ad9ac4cb2e9
git push origin v1.0.1

Also, note the warning: This looks like a new registration that registers version 1.0.1.
Ideally, you should register an initial release with 0.0.1, 0.1.0 or 1.0.0 version numbers
This can be safely ignored. However, if you want to fix this you can do so. Call register() again after making the fix. This will update the Pull request.

@JuliaRegistrator register

Error while trying to register: "Tag with name v1.0.1 already exists and points to a different commit"

@JuliaRegistrator register

Registration pull request created: JuliaRegistries/General/97314
Tip: Release Notes
Did you know you can add release notes too? Just add markdown formatted text underneath the comment after the text
"Release notes:" and it will be added to the registry PR, and if TagBot is installed it will also be added to the
release that TagBot creates. i.e.
@JuliaRegistrator register

Release notes:

## Breaking changes

- blah

To add them here just re-invoke and the PR will be updated.
Tagging
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v1.0.2 -m "<description of version>" 2a09118f5ea95bf5d67562ed071a161f2f5b3c45
git push origin v1.0.2

Also, note the warning: This looks like a new registration that registers version 1.0.2.
Ideally, you should register an initial release with 0.0.1, 0.1.0 or 1.0.0 version numbers
This can be safely ignored. However, if you want to fix this you can do so. Call register() again after making the fix. This will update the Pull request.

register()

Error while trying to register: "Tag with name v0.1.0 already exists and points to a different commit"

@JuliaRegistrator register

Error while trying to register: "Tag with name v0.1.0 already exists and points to a different commit"

@JuliaRegistrator register

Registration pull request created: JuliaRegistries/General/97317
Tip: Release Notes
Did you know you can add release notes too? Just add markdown formatted text underneath the comment after the text
"Release notes:" and it will be added to the registry PR, and if TagBot is installed it will also be added to the
release that TagBot creates. i.e.
@JuliaRegistrator register

Release notes:

## Breaking changes

- blah

To add them here just re-invoke and the PR will be updated.
Tagging
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.1.0 -m "<description of version>" 20e65d3168cd1e7a3a3ef0a012676297589eb485
git push origin v0.1.0


TypeScript compilerOption target is not used

What are the steps to reproduce this issue?
n/a
What happens?
I noticed my tsconfig.json target is not read by Orval.
I created a pull request to add it: https://github.com/anymaniax/orval/pull/670
What were you expecting to happen?
n/a
Any logs, error output, etc?
n/a
Any other comments?
n/a
What versions are you using?
n/a

Which version do you use?

"orval": "6.9.6"

can you try with 6.11.0-alpha.6 if you still have the problem?

Sadly, I still have the issue with that version
� Start orval v6.11.0-alpha.6 - A swagger client generator for typescript
(node:12904) Warning: Setting the NODE_TLS_REJECT_UNAUTHORIZED environment variable to '0' makes TLS connections and HTTPS requests insecure by disabling certificate verification.
(Use `node --trace-warnings ...` to show where the warning was created)
▲ [WARNING] "import.meta" is not available in the configured target environment ("es2015") and will be empty [empty-import-meta]

    src/helpers/orval/mutator/custom-instance.ts:17:11:
      17 │   baseUrl: import.meta.env.VITE_API_BASE_URL

Is it maybe because my tsconfig.json uses references? It is a create-vue/Vite project:
{
  "files": [],
  "references": [
    {
      "path": "./tsconfig.config.json"
    },
    {
      "path": "./tsconfig.app.json"
    },
    {
      "path": "./tsconfig.vitest.json"
    }
  ]
}

ok now I see

Hmm, gave it a try with a simpler tsconfig.json
{
  "compilerOptions": {
    "module": "ESNext",
    "target": "ESNext"
  }
}

but sadly the same error. So the references it not the issue, i guess (?)

no no it's the way the file is compile you are right

Normally you don't have any side effects right?

What exactly do you with side effects? In what context?

The code is well generated no? Without any issue? You just have the warning

Yes, the code is well generated. It is not a blocking issue/bug

Will check and probably merge. Just afraid that it can cause some problems in some case

it's not exactly the same since it's the build setup for esbuild that you modify here

@anymaniax could you have give a status update?

Hello @wouterkroes, sorry I didn't have the time to check yet. I thought it wasn't urgent since it's only a warning.

@anymaniax anything new? bug continues up to latest version (6.11.1)

When will this issue be fixed? The issue still exists.（6.12.1）

Not sure if this is useful, but I am encountering the same issue:
🍻 Start orval v6.14.1 - A swagger client generator for typescript
flumeHealth: Cleaning output folder
▲ [WARNING] "import.meta" is not available in the configured target environment ("es2015") and will be empty [empty-import-meta]

    src/axiosClient.ts:4:11:
      4 │   baseURL: import.meta.env.VITE_API_URL,
        ╵            ~~~~~~~~~~~

I'm building my app with Vite. I can provide additional details if it's helpful.

Same issue here with Vite & React.
🍻 Start orval v6.15.0 - A swagger client generator for typescript
evo: Cleaning output folder
▲ [WARNING] "import.meta" is not available in the configured target environment ("es2015") and will be empty [empty-import-meta]

    src/api/mutator/custom-instance.ts:4:11:
      4 │   baseURL: import.meta.env.VITE_SERVICE_URL,
        ╵            ~~~~~~~~~~~

🎉 evo - Your OpenAPI spec has been converted into ready to use orval!
✨  Done in 4.64s.

Here's my config FWIW:
// orval/config.ts

import { defineConfig } from "orval";

export default defineConfig({
  evo: {
    input: {
      target: "http://localhost:3002/v3/api-docs",
    },
    output: {
      mode: "tags",
      schemas: "../src/generated/models/user-service",
      client: "axios",
      target: "../src/generated/api/user-service",
      mock: false,
      prettier: true,
      clean: true,
      tsconfig: "../tsconfig.json",
      packageJson: "../package.json",
      override: {
        useDates: true,
        mutator: {
          path: "../src/api/mutator/custom-instance.ts",
          name: "customInstance",
        },
      },
    },
  },
});

In which release should this be included?
I still have the issue with 6.22.1, is this to be expected?


Support for AMD GPUs in the Llama Recipes notebook quickstart

🚀 The feature, motivation and pitch
So I'm using an RX 7900 XTX with PyTorch 2.2.0.dev20231005+rocm5.7. From the error message below, it seems that it's a problem with bitsandbytes not supporting AMD GPUs (yet). I would like to ask for a version of the Quick Start guide that would support AMD GPUs as well, not just Nvidia GPUs.
I get the following error when I try to run model = LlamaForCausalLM.from_pretrained("meta-llama/Llama-2-7b-hf", load_in_8bit=True, device_map='auto',torch_dtype=torch.float16):
Traceback (most recent call last):
File "/home/gabriel/.local/lib/python3.10/site-packages/transformers/utils/import_utils.py", line 1282, in _get_module
return importlib.import_module("." + module_name, self.name)
File "/usr/lib/python3.10/importlib/init.py", line 126, in import_module
return _bootstrap._gcd_import(name[level:], package, level)
File "", line 1050, in _gcd_import
File "", line 1027, in _find_and_load
File "", line 1006, in _find_and_load_unlocked
File "", line 688, in _load_unlocked
File "", line 883, in exec_module
File "", line 241, in _call_with_frames_removed
File "/home/gabriel/.local/lib/python3.10/site-packages/transformers/integrations/bitsandbytes.py", line 11, in
import bitsandbytes as bnb
File "/home/gabriel/.local/lib/python3.10/site-packages/bitsandbytes/init.py", line 6, in
from . import cuda_setup, utils, research
File "/home/gabriel/.local/lib/python3.10/site-packages/bitsandbytes/research/init.py", line 1, in
from . import nn
File "/home/gabriel/.local/lib/python3.10/site-packages/bitsandbytes/research/nn/init.py", line 1, in
from .modules import LinearFP8Mixed, LinearFP8Global
File "/home/gabriel/.local/lib/python3.10/site-packages/bitsandbytes/research/nn/modules.py", line 8, in
from bitsandbytes.optim import GlobalOptimManager
File "/home/gabriel/.local/lib/python3.10/site-packages/bitsandbytes/optim/init.py", line 6, in
from bitsandbytes.cextension import COMPILED_WITH_CUDA
File "/home/gabriel/.local/lib/python3.10/site-packages/bitsandbytes/cextension.py", line 13, in
setup.run_cuda_setup()
File "/home/gabriel/.local/lib/python3.10/site-packages/bitsandbytes/cuda_setup/main.py", line 120, in run_cuda_setup
binary_name, cudart_path, cc, cuda_version_string = evaluate_cuda_setup()
File "/home/gabriel/.local/lib/python3.10/site-packages/bitsandbytes/cuda_setup/main.py", line 341, in evaluate_cuda_setup
cuda_version_string = get_cuda_version()
File "/home/gabriel/.local/lib/python3.10/site-packages/bitsandbytes/cuda_setup/main.py", line 311, in get_cuda_version
major, minor = map(int, torch.version.cuda.split("."))
AttributeError: 'NoneType' object has no attribute 'split'
Alternatives
No response
Additional context
No response

@PatchouliPatch we are looking into AMD GPUs/ will keep you posted, however the bits&bytes issue with AMD you might help to open an issue on their repo.

We have tried this script on AMD GPUs and it works for LoRa and full fine tuning. We have not tried bits-n-bytes.

We have tried this script on AMD GPUs and it works for LoRa and full fine tuning. We have not tried bits-n-bytes.

can u share us your flow/script on how to fix the bit&bytes issue?
thanks


Documentation seems to be outdated.

Following the README.md and trying to run the Ansible playbooks on a new host, results in the follow error:

Edit inventory.yml and add IP to validator and sentry.
Confirm that hosts are reachable:

ansible sentry -m ping

SUCCESS

ansible validator -m ping

SUCCESS

Run the playbook to install sentry and validator

ansible-playbook -l validator playbooks/network.yml --extra-var="bor_branch=v0.2.1 heimdall_branch=v0.2.0-mainnet-1d8aca37 network_version=mainnet-v1 node_type=sentry/validator"

...

TASK [install-heimdall : Creating symlink for bridge] *************************************************
changed: [xxx]

TASK [Build Bor] **************************************************************************************

TASK [install-bor : Cloning the Bor] ******************************************************************
changed: [xxx]

TASK [install-bor : Build Bor] ************************************************************************
fatal: [xxx]: FAILED! => {"changed": true, "cmd": ["make", "bor-all"], "delta": "0:00:00.002954", "end": "2021-05-02 23:41:02.410952", "msg": "non-zero return code", "rc": 2, "start": "2021-05-02 23:41:02.407998", "stderr": "make: *** No rule to make target 'bor-all'.  Stop.", "stderr_lines": ["make: *** No rule to make target 'bor-all'.  Stop."], "stdout": "", "stdout_lines": []}

Ansible version
ansible --version

ansible 2.10.3
  config file = /Users/nonsense/code/src/github.com/maticnetwork/node-ansible/ansible.cfg
  configured module search path = ['/Users/nonsense/.ansible/plugins/modules', '/usr/share/ansible/plugins/modules']
  ansible python module location = /usr/local/Cellar/ansible/2.10.3_1/libexec/lib/python3.9/site-packages/ansible
  executable location = /usr/local/bin/ansible
  python version = 3.9.0 (default, Dec  6 2020, 18:02:34) [Clang 12.0.0 (clang-1<IP_ADDRESS>)]

I'm seeing the same problem. Is there any solution?


Add workaround for Minecraft bugs MC-221987 and MC-231035

This pull request aims to work around issues caused by malformed MOTD strings in Minecraft query responses.
https://bugs.mojang.com/projects/MC/issues/MC-221987
https://bugs.mojang.com/projects/MC/issues/MC-231035
MOTDs in query responses can, in various cases, contain null bytes. This is quite unfortunate, as all strings in query responses are null terminated.
Some Unicode characters, including a number of Chinese and Korean characters, will simply be "encoded" to null bytes. Whenever a code point is larger than one byte, Minecraft will only add the last byte to the encoded string.
It is also possible to add null bytes directly using \u0000 in the server.properties file of a server.
Both of these issues result in invalid query responses and can even be used to intentionally inject fake values.
To prevent intentional injections, this pull request aims to reject responses that contain additional bytes after the end of the query response structure.
To parse query responses with an MOTD that contains null bytes, all null bytes within the MOTD field that are not followed by a valid known key are ignored. That one is a total hack, but I can't think of any better way of doing this.
It will also not eliminate the issue completely, as strings like 最numplayers (a character that becomes a null byte followed by a valid key) would still cause an error.

Thank you for your pull request. Everything checks out so I will go ahead and merge it. You can expect 5.4.0 to be published to the NPM registry in a few minutes.


Add an installed profile overview

Add a page showing the current installed profile and information related to it

added


[zh] Update admission-controllers.md

Fix statement order problem and translate.

signed

signed

Looks like we have some other changes to be synced for this page.
$ ./scripts/lsync.sh content/zh/docs/reference/access-authn-authz/admission-controllers.md
diff --git a/content/en/docs/reference/access-authn-authz/admission-controllers.md b/content/en/docs/reference/access-authn-authz/admission-controllers.md
index 9bd082dc1..e57813ec1 100644
--- a/content/en/docs/reference/access-authn-authz/admission-controllers.md
+++ b/content/en/docs/reference/access-authn-authz/admission-controllers.md
@@ -725,10 +725,15 @@ See the [resourceQuota design doc](https://git.k8s.io/community/contributors/des

 ### RuntimeClass {#runtimeclass}

-{{< feature-state for_k8s_version="v1.16" state="alpha" >}}
+{{< feature-state for_k8s_version="v1.20" state="stable" >}}

-For [RuntimeClass](/docs/concepts/containers/runtime-class/) definitions which describe an overhead associated with running a pod,
-this admission controller will set the pod.Spec.Overhead field accordingly.
+If you enable the `PodOverhead` [feature gate](/docs/reference/command-line-tools-reference/feature-gates/), and define a RuntimeClass with [Pod overhead](/docs/concepts/scheduling-eviction/pod-overhead/) configured, this admission controller checks incoming
+Pods. When enabled, this admission controller rejects any Pod create requests that have the overhead already set.
+For Pods that have a  RuntimeClass is configured and selected in their `.spec`, this admission controller sets `.spec.overhead` in the Pod based on the value defined in the corresponding RuntimeClass.
+
+{{< note >}}
+The `.spec.overhead` field for Pod and the `.overhead` field for RuntimeClass are both in beta. If you do not enable the `PodOverhead` feature gate, all Pods are treated as if `.spec.overhead` is unset.
+{{< /note >}}

 See also [Pod Overhead](/docs/concepts/scheduling-eviction/pod-overhead/)

Looks like we have some other changes to be synced for this page.
$ ./scripts/lsync.sh content/zh/docs/reference/access-authn-authz/admission-controllers.md
diff --git a/content/en/docs/reference/access-authn-authz/admission-controllers.md b/content/en/docs/reference/access-authn-authz/admission-controllers.md
index 9bd082dc1..e57813ec1 100644
--- a/content/en/docs/reference/access-authn-authz/admission-controllers.md
+++ b/content/en/docs/reference/access-authn-authz/admission-controllers.md
@@ -725,10 +725,15 @@ See the [resourceQuota design doc](https://git.k8s.io/community/contributors/des

 ### RuntimeClass {#runtimeclass}

-{{< feature-state for_k8s_version="v1.16" state="alpha" >}}
+{{< feature-state for_k8s_version="v1.20" state="stable" >}}

-For [RuntimeClass](/docs/concepts/containers/runtime-class/) definitions which describe an overhead associated with running a pod,
-this admission controller will set the pod.Spec.Overhead field accordingly.
+If you enable the `PodOverhead` [feature gate](/docs/reference/command-line-tools-reference/feature-gates/), and define a RuntimeClass with [Pod overhead](/docs/concepts/scheduling-eviction/pod-overhead/) configured, this admission controller checks incoming
+Pods. When enabled, this admission controller rejects any Pod create requests that have the overhead already set.
+For Pods that have a  RuntimeClass is configured and selected in their `.spec`, this admission controller sets `.spec.overhead` in the Pod based on the value defined in the corresponding RuntimeClass.
+
+{{< note >}}
+The `.spec.overhead` field for Pod and the `.overhead` field for RuntimeClass are both in beta. If you do not enable the `PodOverhead` feature gate, all Pods are treated as if `.spec.overhead` is unset.
+{{< /note >}}

 See also [Pod Overhead](/docs/concepts/scheduling-eviction/pod-overhead/)

@tengqm Synced.

@tengqm Synced.

change looks good to me.
pls squash your 11 commits into one so we can merge it.

change looks good to me.
pls squash your 11 commits into one so we can merge it.

@tengqm Done.

@tengqm Done.

Thanks.
/lgtm
/approve

Thanks.
/lgtm
/approve


Xcode11.4 Swift5.2 support

I use Carthage to integrate SnapKit into my project:
"github "SnapKit/SnapKit" ~> 5.0.0"
When my Xcode update to 11.4 version, the error occurs:
"Module compiled with Swift 5.1.1 cannot be imported by the Swift 5.2 compiler"

If you rebuild your carthage dependencies using Xcode 11.4, this error will go away. You'll need to make sure xcode-select -p points to the right version of xcode, if you have multiple on your computer.

That's it! Thanks a lot!


PPU: draw background layer + cleanup

This contains a bunch of cleanup and rewrites of PPU stuff. However, it's still far from done. There are still quite a few variables and fields that might be removed in the future. The code contains a bunch of disabled logging statements, too. Those will be removed once the dust around the PPU settles.
What this PR contains:

A more or less finished version of the PixelFifo (I actually think this can stay pretty much like this)
The PPU correctly (I think?) draws the background. I also think that the timing is more or less correct (4 pixels per cycles, ...)
Completely unrelated to the PPU: a bug fix in the instruction data

Wait with this merge for #21.


federation: non-federation DNS lookup can return federation CNAME

 Issue by nikhiljindal
Thursday Jun 23, 2016 at 20:15 GMT
Originally opened as https://github.com/kubernetes/kubernetes/issues/27969

With the current KubeDNS code, it can happen that a pod requests mysvc.somens and resolve.conf adds myns.svc.cluster.local as a search path so that KubeDNS gets mysvc.somns.myns.svc.cluster.local.
If there is a federation with the name myns, isFederationQuery in KubeDNS will think this is a federation query and try to resolve mysvc.somens.svc.cluster.local. If there is a local service resolving to that DNS, then user will get that as expected (all is fine). But if there isnt, then KubeDNS will return mysvc.somens.myns.svc.myzone.myregion.mydomain. If there is no federation service with that name and in that namespace, then user will still get an NXDOMAIN as expected. But if there is, then user might be pointed to a service in another cluster, which user may or may not have wanted.
We can consider this a feature, if users want it or should fix it, if we consider it a bug.
Filing this to keep track.
@kubernetes/sig-cluster-federation

 Comment by nikhiljindal
Thursday Jun 23, 2016 at 20:22 GMT

For the record, @quinton-hoole and I had discussed a potential solution which we decided not to do.
The idea was to update kubedns.isFederationQuery() to look for the pattern svcname.nsname.fedname.nsname.svc.domain instead of looking for svcname.nsname.fedname.svc.domain. That will fix the problem, but it doesnt seem logically and syntactically correct to resolve svcname.nsname.fedname.nsname.svc.domain instead of resolving svcname.nsname.fedname.svc.domain. And this solution works only because of the current ordering of search paths in resolve.conf (we first append nsname.svc.domain and then svc.domain). It can break if that order changes.

 Comment by quinton-hoole
Friday Sep 08, 2017 at 01:35 GMT

I think that we still need to fix this before GA of federation.

cc @nikhiljindal

/kind bug

/assign


Disable UITextField marked text… (not selection)

Marked text: An input session used by some languages to combine characters. It does NOT mean text selection.
It’s not compatible with as-you-type formatting, or requires a decent amount of additional work. If you need marked text, for whatever reason, please pitch your use case and how you want it to work. Until then, I’ve decided to disable it.
Also, the previous mini-rework made it so the app crashes when marked text is entered due to an index out of bounds error. That will be fixed in the next update.

Marked text sessions seem to be possible when their output is accepted by the view's text style. I haven't quite figured out what to do yet, but maybe something async can be done on input cancellation. The reason marked text is so annoying is that it is black voodoo magic outside the control of UITextFieldDelegate.

Some comments for if/when I decide to support marked text.
UITextField contains a selected text range and an optional marked text range. A marked text range, when it exists, contains the selected text range. Changes to either range calls textFieldDidChangeSelection(_:), but entering marked text does not trigger textField(_:shouldChangeCharactersIn:replacementString:). The last point is the primary reason for why marked text has not yet been supported, and why it is removed in textFieldDidChangeSelection(_:).

Note that, even if marked it’s disabled, it is still possible to input characters such as é. The ´ character, in this case, is not dequeued when it is removed from the text and it will still be applied to the next character.


Get the presigned url for the uploaded file on AWS S3?

Is it possible to get the file download link from aws s3 bucket after upload an android apk?
I would like to get presigned url

Thanks for the information guys iMessage on PC


Support IBC in Governance

Why this feature is required pre-mainnet
Governance must be able to manage IBC configurations in the case of unplanned counterparty upgrades (or counterparty exploit and/or hardfork). Having full support for governance of IBC is necessary at mainnet otherwise users of the network may encounter undesirable behavior such as being unable to transfer funds via IBC to certain counterparties.
What we need to implement

[ ] https://github.com/penumbra-zone/penumbra/issues/2173
[x] https://github.com/penumbra-zone/penumbra/issues/3024
[ ] Spike what the unplanned upgrade path looks like for other chains
[ ] Add an UpgradeCounterpartyClient proposal
[ ] Implement amending the state of the host chain light clients

Closing in favor of #2173


java.lang.ArrayIndexOutOfBoundsException: Index 99 out of bounds for length 14

crash-2022-11-12_20.58.23-server.txt
No apparent external cause.

Can you please provide more Informations on this case? Is it a server, lan, singleplayer. When does the error throw?

This is the most descriptive issue report I've ever seen

It takes place in a single player world while mining with the card set to
box mode and fortune set with a speed 0f 1, I've  started with version 1.4
but it happened again with the 1.7 build. so far it just happens at random.
In one case it happened on world load, however this only happened once. My
hypothesis is it might be how the miner keeps track of the block it breaks.
I only say this because so far it only happens when it is mining, though, I
do not know if this is relevant but a create schematic intersects the mined
area but as near as I can tell it hasn't happened when a block breaks in
the schematic area.
On Sun, Nov 13, 2022 at 5:15 AM Sr_endi @.***> wrote:

This is the most descriptive issue report I've ever seen
—
Reply to this email directly, view it on GitHub
https://github.com/UnhappyCodings/vanillaquarry/issues/4#issuecomment-1312694184,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AULYBCJO327WX4MEEQERWNLWIC5VBANCNFSM6AAAAAAR6TCAMI
.
You are receiving this because you authored the thread.Message ID:
@.***>

this is the console output right before an error is thrown.
[15:41:21] [Server thread/WARN] [os.ut.pl.wi.WmiQueryHandler/]: COM
exception: Invalid Query: SELECT PERCENTUSAGE FROM
Win32_PerfRawData_PerfOS_PagingFile
On Sun, Nov 13, 2022 at 3:31 PM s r @.***> wrote:

It takes place in a single player world while mining with the card set to
box mode and fortune set with a speed 0f 1, I've  started with version 1.4
but it happened again with the 1.7 build. so far it just happens at random.
In one case it happened on world load, however this only happened once. My
hypothesis is it might be how the miner keeps track of the block it breaks.
I only say this because so far it only happens when it is mining, though, I
do not know if this is relevant but a create schematic intersects the mined
area but as near as I can tell it hasn't happened when a block breaks in
the schematic area.
On Sun, Nov 13, 2022 at 5:15 AM Sr_endi @.***> wrote:

This is the most descriptive issue report I've ever seen
—
Reply to this email directly, view it on GitHub
https://github.com/UnhappyCodings/vanillaquarry/issues/4#issuecomment-1312694184,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AULYBCJO327WX4MEEQERWNLWIC5VBANCNFSM6AAAAAAR6TCAMI
.
You are receiving this because you authored the thread.Message ID:
@.***>

Hey!
the above reported issue is fixed and is already been uploaded to Curseforge!
If you have any other questions related to this post, feel free to post them.
Otherwise you can close the issue now.
If you have any other question feel free to join our discord server: https://discord.intelligence-modding.de/
Thank you for the report and have a nice day! :)


 Thanks!
@gitcash 132652 satoshis to @deepthawtz

@deepthawtz

@GitCash send 321 bits to @cgcardona

@cgcardona

@GitCash 129816 satoshis to @jbdtky

@jbdtky

@GitCash 129816 satoshis to @sagech

@sagech

@GitCash 129816 satoshis to @zowki

@zowki

@GitCash 129816 satoshis to @maplesyrupsucker

@maplesyrupsucker

@GitCash 129816 satoshis to @magmahindenburg

@magmahindenburg

@GitCash 129816 satoshis to @jelaludo

@jelaludo


[Bug][List] With scroll contents ON in the list item container, the last widget crops

W.r.t to scroll contents turning ON , the container doesnt correctly wrap around the last widget
https://www.loom.com/share/388545ce687e47429349726482bc6d70


Add support for BigQuery resumable uploads via a write channel

This PR adds support to BigQuery for inserts that use resumable upload using a write channel interface (different from #534).
Main changes are:

Move BlobWriteChannel and BlobReadChannel to core module (the latter for consistency)
Rename BlobWriteChannel and BlobReadChannel to WriteChannel and ReadChannel
Add abstract class BaseWriteChannel implementing entity-agnostic channel functionality
Add BlobWriteChannel and BlobReadChannel implementations to gcloud-java-storage
Add LoadConfiguration and modify LoadJobInfo to take configuration as a parameter
Add BigQuery.writer method to return a write channel given a LoadConfiguration
Add BigQueryRpc.open and .write methods to implement write channel
Add TableDataWriteChannel class to support bigquery resumable streaming inserts
Add unit and integration tests
Update bigquery example with load-data action

@ajkannan Thanks for the feedback, I fixed the issues in place

@mziccard I took one more pass, and LGTM except for one small variable name change.  Feel free to merge after fixing that.

Looks good! I would like to give it another pass tomorrow. Until then few questions/comments. Also,
I think there are still unaddressed comments made by @ajkannan.

Ok, finished with my pass. Looks good. Few more suggestion and some cleanup.
Also, do you understand why the coverage was dropped in this PR by almost 1 percent?

@aozarov I fixed your comments and rebased.

do you understand why the coverage was dropped in this PR by almost 1 percent?

I have been trying to figure this out but have not so many ideas. A decrease might be caused by the fact that this adds code to the Rpc layer which is only tested in ITs that are (I think) not considered by coveralls report. However this ~1% seems a bit high to me.


Frontend: Add RaptorJIT "Input Tree" IR view

Clicking on an IR instruction now reveals an object with an "Input Tree" view. This shows the subset of the IR tree showing only the inputs to the selected instruction (transitive closure.)
It's a way to "zoom in" on one instruction and see where its input comes from.
Screenshot of clicking on a problematic instruction (unsunk allocation) to see where its value comes from (click to zoom):

This now works in textual mode too. You can freely select textual or graphical IR listing in any pane. You can also continue to recursively drill down by choosing an instruction in any pane to have its inputs inspected on the right.
Screenshot:

I added the "Export to clipboard" button to the subset listings, so that they work the same way as the main listing.
I also tweaked the IR visuals a bit. That's a bit sneaky to do on this branch but hey. Here's a peek at the dashed borders for constants and heavy borders for values that spill onto the stack:

Now you can use Uses List and Uses Tree tabs for an IR instruction to see the subset of IR (transitive closure) that uses the result of the selected instruction.


How to generate public key from mnemonic in testnet?

I trying mnemonic to public key, it working in mainnet.
NSArray * array = @[@"know", @"final", @"wide", @"brush", @"educate", @"bleak", @"exact", @"exhibit", @"coil", @"galaxy", @"milk", @"rhythm"];

BTCMnemonic *mnemonic = [[BTCMnemonic alloc] initWithWords:array password:nil
wordListType:BTCMnemonicWordListTypeEnglish];
BTCKeychain *mainKeychain = [[BTCKeychain alloc] initWithSeed:mnemonic.seed network:
[BTCNetwork mainnet]];
BTCKeychain *purpose = [mainKeychain derivedKeychainAtIndex:44 hardened:YES];
BTCKeychain *coin = [purpose derivedKeychainAtIndex:0 hardened:YES];
BTCKeychain *account = [coin derivedKeychainAtIndex:0 hardened:YES];

BTCKeychain *keychainFirst = [account derivedKeychainAtIndex:0 hardened:NO];
BTCKeychain *keychainSecond = [keychainFirst derivedKeychainAtIndex:0 hardened:NO];

NSLog(@"public key - %@", keychainSecond.key.compressedPublicKeyAddress.string);

and, i want change testnet:
Change code:
BTCKeychain *mainKeychain = [[BTCKeychain alloc] initWithSeed:mnemonic.seed network:
[BTCNetwork testnet]];
NSLog(@"testnet public key - %@", keychainSecond.key.addressTestnet.string);

I 've got the wrong private.
Could you please explain me solution of that problem?
Do you have any document or example?
Thanks

use [mainKeychain derivedKeychainWithPath:@"m/44'/1'/0'/0/0"];in testnet.


Avoid the float intermediate on the way to Decimal

Though isn't this more MOJO_PER_XCH.

I do believe you're right.


Does branch develop support the newest Elasticsearch 2.1.0 ?

the branch develop support Elasticsearch 2.1.0? if yes, can we use it in product? and how to build it?
the branche 2.0 is corresponding to Elasticsearch 2.0?

The 2.0 branch should work with Elasticsearch 2.1.0 - our priority is getting it to a point to release it, hopefully in the next 1-2 weeks. It's getting there but would say that it's use at your own risk in production right now.
The client can be built by building the solution within Visual Studio, or by running the build script in the root.


fixed bug to return only related table data in join

Feature re: Select Periodic Task joined with discriminator table
Expected Behavior
When querying on PeriodicTask table using session.query(PeriodicTask), the joined schedule table is related to the schedule_id AND the discriminator.
Actual Behavior
When querying, if the same id exists in both schedule tables, both joined tables are returned.
Test sample
    def test_PeriodicTask_specifyjoin(self):
        p = self.create_model_interval(self.session, schedule(timedelta(seconds=3)))
        c = self.create_model_crontab(self.session, crontab(minute="3", hour="3"))

        self.session.add(p)
        self.session.add(c)
        self.session.commit()

        p = self.session.query(PeriodicTask).first()

        assert p.schedule_id == 1
        assert c.schedule_id == 1

        assert p.discriminator == 'intervalschedule'
        assert p.model_crontabschedule is None # this would fail prior to these changes
        assert p.model_intervalschedule is not None

        assert c.discriminator == 'crontabschedule'
        assert c.model_intervalschedule is None # this would fail as well
        assert c.model_crontabschedule is not None

Thoughts
In the older implementation (celery_sqlalchemy_scheduler), there were two separate foreign keys specifically connected by crontab_id and interval_id. The newer version uses the discriminator column and the reasoning behind this seems vague.
Collaborators
Matthew Bronstein
Bazyl Horsey

Great work and thanks for contributing.