Footer “edit me” link

If a project is hosted on GitHub (or other hosting service), it’d be nice if we could automatically generate an “edit me” link in the footer.

Here's my take on this, in observablehq.config.js:
const SOURCE_REPO = "https://github.com/USER/PROJECT/blob/main/docs";

const VIEW_SOURCE = `

⚉

`;

export default {
  header: ${VIEW_SOURCE}
};

Would be nice to support non-GitHub hosted (but still open source) websites!

I think we have enough possibilities now for a user to add their own links in header or footer. It could be nice to support passing these options as functions that would receive a bit of context (page name, page url)?


Assessment

Metric
Value

alert_status
:white_check_mark: OK

bugs
0

code_smells
0

reliability_rating
A (0 Bugs)Note: A being best, E being worst

security_rating
A (0 Vulnerabilities)Note: A being best, E being worst

vulnerabilities
0

Drift Video:
https://drive.google.com/drive/folders/1b7D31uGmy4dTXHx4McciJTmnW6dpU0y_
Screenshots:
Question 1:

Question 2:

Question 3:

Fixtures created:


TO Go API: fix origin api tests -- add a tenantId

api test for origins is missing tenant id which causes it to fail on the new not-null db constraint.

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/trafficcontrol-PR/2249/
Test PASSed.


Create helloWorldSam

done hello world please merge it .

Its already there, please contribute to something else

I have added a new file Tower of Hanoi using recursion in C . So, please merge it Okay : )Thank You,Samim Mondal. Sent from Mail for Windows 10 From: Bhavesh LohanaSent: 11 October 2020 02:04To: bhaveshlohana/HacktoberFest2020-ContributionsCc: Samim Hossain Mondal; AuthorSubject: Re: [bhaveshlohana/HacktoberFest2020-Contributions] Create helloWorldSam (#1278) Its already there, please contribute to something else—You are receiving this because you authored the thread.Reply to this email directly, view it on GitHub, or unsubscribe.


UI LDAP settings

ISSUE TYPE

Other

COMPONENT NAME

Management server

CLOUDSTACK VERSION

<IP_ADDRESS>

Don't no if it's issue or not.. In CS UI when configuring LDAP settings instead of values, which were entered I see this:

New values (if I, for example, edit default value) entered are showing normally until I reboot management server (to apply configuration). After, all values regarding LDAP are showed like on screen

that is a strange inconvenience, for some it makes sense (bind password) for this one it doesn't, i think. I also don't know what should be the right behaviour.

Found way to watch them with
java -classpath /usr/share/cloudstack-common/lib/jasypt-1.9.2.jar org.jasypt.intf.cli.JasyptPBEStringDecryptionCLI decrypt.sh

So, UI values for some reason are not decrypted...

@izenk I think this issue is in since 4.9 at least. Are you using the global mapping or the per domain mapping?

Global mapping

@izenk can you check this in the rc3 for 4.11.1? it should have been solved with #2699

Sorry, can't.
Just use as private cloud.

ok, than you'll have to trust me ;)


[TF2.0] Broadcasting

Hello everyone,
I would like resuscitate very old issue. Actually, it is so old that even github's autocompletion doesn't offer it after typing "#" - https://github.com/tensorflow/tensorflow/issues/216. This request was raised several times, but still it hasn't been resolved.
In short, broadcasting interface is not "good enough" in TensorFlow :)
Lets first check how broadcasting works in numpy:
In [1]: import numpy as np
In [2]: a = np.random.rand(2, 3, 4)
In [3]: b = np.random.rand(4, 5)
In [4]: a @ b
Out[4]:
array([[[1.42709275, 1.40630067, 0.46525725, 0.68734581, 0.65227036],
        [2.01336504, 1.59980866, 0.93739699, 0.63190484, 0.92472892],
        [1.82979902, 1.46193243, 0.85498406, 0.5994646 , 0.77767957]],

       [[1.83010035, 1.49088728, 0.76694665, 0.65568003, 0.89110954],
        [2.12214864, 1.41728107, 1.04566743, 0.60652825, 0.97115822],
        [2.32478779, 2.06297214, 1.02016205, 0.81821249, 1.02604722]]])

Now, let's check what the TF is offering:
In [25]: a = tf.random.normal((2, 3, 4))
In [26]: b = tf.random.normal((4, 5))
In [27]: a @ b
... InvalidArgumentError: In[0] is not a matrix. Instead it has shape [2,3,4] [Op:MatMul] name: matmul/

Ouch! The "correct" way of doing it in the TF (of course there are other) is:
In [26]: a = tf.random.normal((2, 3, 4))
In [27]: b = tf.random.normal((4, 5))
In [28]: a @ tf.broadcast_to(b, tf.concat([a.shape[:-2], b.shape], axis=0))
<tf.Tensor: id=87, shape=(2, 3, 5), dtype=float32, numpy=
array([[[ 1.1977772 , -1.363074  ,  1.8021748 ,  0.1448586 , -0.6269997 ],
        [ 1.2322128 , -2.1586194 ,  0.09486479,  0.02937585, 0.9694344 ],
        [ 0.5580032 ,  6.11664   , -0.24535722,  0.16691092, -2.2263217 ]],
       [[-0.7386743 ,  1.2142425 ,  1.1371945 , -1.2736351 , -2.971829  ],
        [-1.9222848 , -0.7198772 , -0.9807504 ,  0.02805561, 1.0210879 ],
        [ 1.8334148 ,  0.80895233,  1.2308785 , -0.23910654, -1.5128168 ]]], dtype=float32)>

You can see how much effort it requires to make operations broadcastable for two distinct tensors: extract leading shape from the left tensor, extract shape from the right tensors, concatenate these shapes with correct axis, call tf.broadcast_to...
The same applies to cholesky, triangular solve and other operations. That is very upsetting that such a crucial feature isn't available out of the box.
Another concern is the performance of these "solutions". E.g. memory consumption for tiling and broadcast_to operations, as they simply copy the tensor to match leading dimensions. Of course, native TensorFlow broadcasting implementation would be preferable in this case.
Kind regards,
Artem Artemev

@rmlarsen , @jvishnuvardhan ping

@awav thankfully when we do add support for this this it will not be an API removal; it just takes code which currently does not work and make it work.
So I don't think we need to block the tf2.0 release on fixing this, though it'd be very nice.
@rmlarsen now that we have a proper batch_matmul can we make it broadcast correctly on leading indices? I feel like this shouldn't be hard but I'm not familiar enough with eigen intricacies to make this happen.

This should be now fixed! (pending 3 week compatibility window)
47ab68d

@bloops , That is fantastic news. Will broadcasting be fixed for all linear algebra operations or only for matmul?

Only for matmul. What else do you have in mind?
We are considering adding broadcasting support for matrix solve as well.

@bloops, ideally, all linear algebra operations, as far as I know some of them already have broadcasting support. The triangular_solve is one important missing bit.

@bloops , any updates on triangular_solve?

Sorry, I am not working on it currently.

@bloops , does anyone else is going to work on that? Do you know what should be changed to make it work?

@bloops , ping? :)

Closing since triangular solve now has broadcasting.


Dynamic content?

I've searched through issues and pull requests and haven't seen this question yet.
Is there a way for json-graphql-server to handle dynamic data passed in from the user?
My idea is to have the user input the JSON which thereafter becomes queryable via graphql.

It's not built in, but you can somehow create such a service using the code of this library.
It's outside of the scope of this project though, so if you want to do it, I invite you to create a new project or to fork this one!

Hi, I'm back. Thanks for this great software.
I'm trying to do this in Express:
app.use('/graphql', getData, jsonGraphqlExpress(data))

My getData middleware dynamically retrieves the JSON I'm interested in serving for the particular request. It is called as expected with every request and is successful at retrieving the JSON and setting the value of data to the JSON.
The challenge, it seems, is that jsonGraphqlExpress(data) initializes the schema on start up with whatever populates data at the time and not with every request.
I've spent several hours trying this and that.
I've tried wrapping the call to jsonGraphqlExpress in other middleware and was not successful.
I've tried using schemaBuilder with graphqlHTTP.
I appreciate any tips and suggestions you might have.

I think I have it working now thanks to another friend:
function startServer (req, res, next) {
    jsonGraphqlExpress(req.data)(req, res)
    next()
}
app.use('/graphql', getData, startServer)
...


error in Internet Explorer 8 using zxcvbn/js

I'm getting this error using zxcvbn.js when doing 'var result = zxcvbn(password);'

Webpage error details
User Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 5.1; Trident/4.0; .NET CLR 1.1.4322; .NET CLR 2.0.50727; .NET CLR 3.0.4506.2152; .NET CLR 3.5.30729; .NET4.0C; .NET4.0E)
Timestamp: Sun, 27 Mar 2016 13:48:44 UTC
Message: Object doesn't support this property or method
Line: 18
Char: 4365
Code: 0
URI: http://.../zxcvbn.js

Hi @EISLtd, we no longer support IE8, but IE9 and above should work. You can see our supported platforms here: saucelabs browser status.


Add .pylintrc file

The JAX project utilizes non-standard PEP 8 settings for indentation.
To validate Python files, we can leverage a .pylintrc configuration file.
For reference, the TensorFlow project has an existing .pylintrc file that outlines its settings.
This PR introduces a .pylintrc file for the JAX project, modeled after the configuration used in TensorFlow.
[FORMAT]

# Maximum number of characters on a single line.
max-line-length=80

# String used as indentation unit. This is usually " " (4 spaces) or "\t" (1
# tab).
indent-string='  '

Usage Example:
### check files in HEAD commit
git diff --name-only HEAD^ HEAD | xargs pylint

Hi - thanks for the PR. We already have pylint configuration in pyproject.toml, and I'd prefer to keep all such configs in a single location

Also, a while ago we moved off pylint and now use ruff for formatting. It's set up as a pre-commit hook.

Got it. Thank you for the info!


Fix JavaDoc

I fixed "calback" to "callback" in JavaDoc.

Hi! Sorry if you haven't gotten a response (from a human) on this pull request so far, but contributing to this project works via Gerrit – see https://chromium.googlesource.com/custom-tabs-client/+/master/CONTRIBUTING.md. Thanks!

@sheepmaster Thank you for your information!

I moved this issue to https://chromium-review.googlesource.com/c/custom-tabs-client/+/935602.


Fix reference counting

I don't know how this could possibly work, but if you create a new application, add this lib and just try to BINDO with -observe: it won't work, because right after the creation of the binding it gets deallocated: BNDBinding is not retained. You had an NSMutableSet, where you add BNDBindings, but now it's gone and only BNDBindingKVOObserver are retained by association. But they have a weak reference to parent BNDBinding. That's a fail.
To fix this we must make BNDBindingKVOObservers to hold strong reference to parent BNDBinding.

Ping, maaan

Hey @aspcartman sorry I'm super busy with other stuff. Had a brief look at it, and I think you might be right. The way we're using BINDO is always by keeping the reference to the BNDBinding that gets returned. I need more time to test your fix though, thanks for spotting this.

@markohlebar thanks :)


"debug: true" exposes Maven credentials

If I specify debug: true I can see in the job output everything that happens, including the determination of usernames and passwords.  Isn't this is a security issue?  Should there be a way to prevent debug from being turned on somehow?

The debug flag is an undocumented feature to help me when I have to troubleshoot the resource.  It's can be incredibly useful, but yes it does have security implications.  I'm open to options for achieving the same result in a more secure fashion... If we can't come up with anything, i'm open to removing it.  Let me know your thoughts.


define/implement additional raw -> engineering  calibration in the IDB

more parameters could be calibrated with the generic IDB raw->engineering  framework

[ ] define a  list of parameters with calibration instruction @samaloney
[ ] implement IDB injection for old packets @nicHoch
[ ] add to IDB for future versions @ennosigaeus

NIX
Conversion

NIX00269
NIX00269 * 0.1 [seconds]

NIX00404
(NIX00405 + 1) * 0.1  [seconds]

NIX00405
(NIX00405 + 1) * 0.1  [seconds]

NIX00441
(NIX00441) * 0.1 [seconds]

NIX00122

NIX00123

NIX00124

@samaloney
NIX00404 | (NIX00405 + 1) * 0.1  [seconds]
multi variant dependency have to be resolved in the specific product not in the generic idb calibration.

Yea that's a typo I'm trying to pull them all out of the current code - not convinced they are correct.

@samaloney as you are already done with the level1 processing of the main packets.
do you think this list ready to go .
So i can implement this.

Should ideally add NIX00123 and NIX00124

@nicHoch can we closet this now or do we need to test?

@ennosigaeus for future IDBs Versions it should defined directly defined in the IDB

I implemented the changes and will provide you with a new intermediate IDB version for testing. NIX00441 has been removed.

Hm, maybe GitHub was a little too fast. Please check first if it is DONE indeed.

@samaloney
NIX00404 | (NIX00405 + 1) * 0.1 [seconds]
multi variant dependency have to be resolved in the specific product not in the generic idb calibration.

So in each tmtc packet definition we need to check and adapt? Possible related to #116

Can this be closed @nicHoch?


App: merge avatar geometries for depth pass

Avatars generally have a large amount of geometries/materials, sometimes upwards of 50. If we merge the geometries correctly (possibly in a worker), we can reduce the number of draw calls on the depth pass by a lot.

Note that with this solution, we do not lose any quality on the avatar. We would simply bake the geometry for depth compute purposes.


Virus scanner health-check

Check that the virus scanner is running and configured suitably

Hi @Franceswog the virus scanner has been checked and is running well. As discussed earlier it is running in what we might call a 'light touch' mode: in that files can be downloaded unless the scanner has marked them as having a virus.
I think we should consider moving to a stricter configuration where files can only be downloaded if they have been marked as not having a virus. Perhaps also we enforce a re-scan policy where a file is re-scanned for viruses if someone is trying to download and it hasn't been scanned for X amount of time.
The problem right now is if our virus scanner stops working, for some reason, all files are still downloadable. If we take a stronger approach then if the scanner stops working our files will stop being available to download. So this helps ensure we keep the scanner up and running.

Hello @warrensearle, thank you for the detailed update. I appreciate your proactive approach to enhance our security measures. I agree with the suggestion to move to a stricter configuration. May I suggest a policy to be implemented  where files can only be downloaded if marked as virus-free, and enforce a re-scan policy to address potential gaps in detection. This not only strengthens our security but also ensures that the scanner's functionality remains a critical component in file availability. It would be a good Idea to discuss this with Nick when he returns to work and  possibly  adopt your idea.

Hello @warrensearle, thank you for the detailed update. I appreciate your proactive approach to enhance our security measures. I agree with the suggestion to move to a stricter configuration. May I suggest a policy to be implemented where files can only be downloaded if marked as virus-free, and enforce a re-scan policy to address potential gaps in detection. This not only strengthens our security but also ensures that the scanner's functionality remains a critical component in file availability. Will you discuss and explain this to Nick when he returns to work and he may possibly adopt your idea. 😊

@nickaddy have assigned this one to you to decide whether this ticket gives birth to any further work on the virus scanner for @HalcyonJAC

@Franceswog I'm going to close this ticket as complete. Could you pls create a new ticket (under digital platform repo) in the backlog, including the proposal above, which I'm happy with? We may be able to cover it in the January sprint.


Code understanding

@HanGuangXin  thanks for sharing hte code base , i having the following queries

I was able to train only on MOT17 data , can we scale the training to other datasets similar to Bytetrack
From the code structure perspective i am to see that you have added any additional reid head to the yolox architecture and this embedding from the reid ur passing it to the tracker, am i right in understanding ? if so by training with larger datasets can we use this model for multicamera person reidentification?
In your comments you have mentioned "#TODO Reid" does that mean you have already implemented it and using these heads in the inference

Thanks in adavance

@abhigoku10 Sorry for the late reply!

Of course yes. But there may be some data format issues to do, which is normal.
A ReID-head? Yes! Use ReID datasets? I don't think so. The training should be done with the whole image, not cropped boxes.
'TODO' just means highlight, which does not mean real 'TODO'.

I'm closing this issue. If you have other questions, please open another one.


How to connect to managed workspace that is private?

[Can you please elaborate on the same page regarding the way to connect to managed workspace that is private?]

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

ID: f51c2f90-acf1-51cc-5c2b-6a48c053cba2
Version Independent ID: cc94d999-3eda-1004-abcf-674b14ed2c8e
Content: Managed virtual network isolation - Azure Machine Learning
Content Source: articles/machine-learning/how-to-managed-network.md
Service: machine-learning
Sub-service: enterprise-readiness
GitHub Login: @jhirono
Microsoft Alias: jhirono

@yogitasrivastava
Thanks for your feedback! We will investigate and update as appropriate.

@yogitasrivastava
Certainly! If you want to connect to a managed workspace that is private, you can use a private endpoint. A private endpoint is a network interface that connects to an Azure service over a private IP address. It provides secure connectivity to a service over a private network connection.
To connect to a managed workspace that is private, you can use the Azure CLI to deploy a workspace and a private link endpoint for the workspace resource. You can use the following parameters as part of the az ml workspace create command or use the az ml workspace private-endpoint commands.
Here is an example of how to create a workspace with a private link endpoint using the Azure CLI:
az ml workspace create -g <resource-group-name> --file privatelink.yml

You can find more information on how to create workspaces with Azure CLI in the following document: https://docs.microsoft.com/en-us/azure/machine-learning/how-to-manage-workspace-cli
If you encounter any issues while connecting to a workspace with a private endpoint, you can troubleshoot the connection using the steps provided in the following document: https://docs.microsoft.com/en-us/azure/machine-learning/how-to-troubleshoot-secure-connection-workspace

@yogitasrivastava
We are going to close this thread .if there are any further questions regarding the documentation, please tag me in your reply and we will be happy to continue the conversation.


Issues with KeyVaultConfigProviderSample

I have tried to follow the instructions and running this sample:
https://github.com/aspnet/Docs/tree/master/aspnetcore/security/key-vault-configuration/sample
But, there seems to be issues with it:

The sample crashes with an exception:

"Operation "list" is not allowed by vault policy"
Nowhere is it mentioned that "list" access should be granted to the application.

There seems to be some confusion related to the naming of a key:

Instructions says:
Create key vault secrets
MySecret: secret_value_1
Section--MySecret: secret_value_2
This is used in the code:
Configuration["Section:MySecret"]
What is the link between: "Section--MySecret" and "["Section:MySecret"]"?

@Rick-Anderson @tdykstra I'm working on the updates now for 2.0. Let's piggyback the 2.0 update on this issue, and I'll knock them both out.
@olavt The part of the topic that pertains to permissions is this bit ...

Authorize the app to access the key vault. When you use the Set-AzureRmKeyVaultAccessPolicy PowerShell cmdlet to authorize the app to access the key vault, provide List and Get access to secrets with -PermissionsToKeys list,get.

However, I didn't add that level of detail to the sample itself (in its README.md file at https://github.com/aspnet/Docs/tree/master/aspnetcore/security/key-vault-configuration/sample), where it merely states ...

Authorize the application to use the secrets

I'll fix that on this pass.
On your point 2: I agree with you: It should have more text here to explain. The current language assumes that the reader will understand the replacement of -- with the colon that's normally used when accessing configuration values. The topic overly relies on the reader having seen/remembered in the Configuration topic: Simple configuration section ...

Configuration consists of a hierarchical list of name-value pairs in which the nodes are separated by a colon. To retrieve a value, access the Configuration indexer with the corresponding item’s key: [followed by an example of where the colon is used to obtain a subsection:suboption1]

I'll work on this problem, too, on this next update to the topic.
Sorry for the confusion. The current version was the first version of the topic, and it takes a little bit of time and an update or two to make a topic really shine. Thanks for reporting the issues you found with the topic. I'll ping you on the PR when I submit it, and then you can review the changes if you like.

@GuardRex  sounds great.


Update README.md

fix output file name in example
Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[x] Docs change / refactoring / dependency upgrade

Motivation and Context / Related issue

How Has This Been Tested (if it applies)

Checklist

[x] The documentation is up-to-date with the changes I made.
[x] I have read the CONTRIBUTING document and completed the CLA (see CONTRIBUTING).
[ ] All tests passed, and additional code has been covered with new tests.

Closing the PR as this has been already fixed.


fetching project/repo from location

Hey, I just made a Pull Request!
backstage.io/managed-by-location: https://dev.azure.com/{org}/{project}/_git/{repo}?path=/.catalog/component.yml
if dev.azure.com/project-repo annotation is not provided and dev.azure.com/project not exits then to extract the project and repo information we can use backstage.io/managed-by-location annotation if location contains dev.azure.com in url to enable CICD tab.

:heavy_check_mark: Checklist

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

Thanks for the contribution @taraknath555, this is a good idea but I think we should make sure to support both Cloud and Server versions of Azure DevOps. This should be achievable if you use git-url-parse, there are many examples in this repo.
Also, I'm not sure if backstage.io/managed-by-location will work for everyone, we keep our YAML in a central repo so it would pull in the wrong project and repo for us. Could we use backstage.io/source-location instead?
Finally, if we could add some tests for this that would be really good!

It seems like this method would work to support both correct? https://github.com/backstage/backstage/blob/master/plugins/github-actions/src/components/getHostnameFromEntity.ts
It also seems like this method should be more of a core helper method. Is that something we should consider?

Hi @taraknath555, I only recently learned about the existence of this processor but I'm think it would be much smarter to add this feature to the existing AnnotateScmSlugEntityProcessor as it then becomes opt-in for users and would support both Cloud and Server usage.
To implement this all you would need to do is add the dev.azure.com/project-repo annotation here: https://github.com/backstage/backstage/blob/263e3846d8e0d2270800f7ddc224da902912f53e/plugins/catalog-backend/src/modules/core/AnnotateScmSlugEntityProcessor.ts#L29
And then update this switch with a case for azure: https://github.com/backstage/backstage/blob/263e3846d8e0d2270800f7ddc224da902912f53e/plugins/catalog-backend/src/modules/core/AnnotateScmSlugEntityProcessor.ts#L77

Hey @awanlin, can you please make me clear if only need to do the below change in this pull request?

If so the other part of the code that will make the requirement work is taken care by #19616 ?

Hi @taraknath555, yes, I would just make the changes I suggested to add getting the dev.azure.com/project-repo annotation set in the AnnotateScmSlugEntityProcessor. I don't want you to have to wait around for my changes to get merged in as they may take a while as they get reviewed. Just doing this will be a big win for the community 🚀
Also, thanks for taking my various requests in stride, I really appreciate it 👍

Hi @taraknath555, yes, I would just make the changes I suggested to add getting the dev.azure.com/project-repo annotation set in the AnnotateScmSlugEntityProcessor. I don't want you to have to wait around for my changes to get merged in as they may take a while as they get reviewed. Just doing this will be a big win for the community 🚀
Also, thanks for taking my various requests in stride, I really appreciate it 👍

Hey @awanlin, I updated the PR as per you suggested, Please take a look on this!

Looks good to me but we should add a test for this in AnnotateScmSlugEntityProcessor.test.ts, please

Done!

what was actually done would be great

Hey @awanlin i updated the PR title! Now, Where you want me to add the things that is actually done for this PR ?

what was actually done would be great

Hey @awanlin i updated the PR title! Now, Where you want me to add the things that is actually done for this PR ?
Hey @awanlin can you please suggest what else changes you required , i already updated the description/title of PR and when can we merge this PR ?

Hi @taraknath555, sorry this fell off my radar. Can you also update the description of this PR? It still talks about the previous changes and has the image that isn't relevant anymore. You could simply replace that with: "Set azure annotation dev.azure.com/project-repo in AnnotateScmSlugEntityProcessor to find the project and repo information for the repos that contains dev.azure.com in the url"
As already mentioned I'm just the first approval you will need approval from the catalog maintainers as well. They will also be the ones to do the merge.

Hey @freben @awanlin just want to check about is this change is added in current release of 1.18.1 as after updating the backstage to same i.e. 1.18.1,  i am not able to take the advantage of the changes!

Hi @taraknath555, did you add the processor? This would be done in your /packages/backend/src/plugins/catalog.ts file and you would add this:
const integrations = ScmIntegrations.fromConfig(env.config);
 builder.addProcessor(new AnnotateScmSlugEntityProcessor(integrations))

There'll be some imports as welll


Upgrade upload-artifact action

I'm not even gonna bother trying to ascertain what they changed that's necessitated two major version bumps. In fact, I might go into a tirade about how absolutely dire the state of CI tooling broadly is if someone doesn't hold me ba--

Alright it works and it only required one superfluous commit. I sure love that the intended path for debugging CI's is to constantly commit and push incremental changes, because having local execution and debuggers is so 90's.

I'm not even gonna bother trying to ascertain what they changed that's necessitated two major version bumps. In fact, I might go into a tirade about how absolutely dire the state of CI tooling broadly is if someone doesn't hold me ba--


Click position problem when using MoPubRecyclerAdapter

I'm having an issue when I try to use MoPubRecyclerAdapter (from MoPub SDK) with FastItemAdapter.
MoPubRecyclerAdapter is basically a wrap adapter to allow MoPub's SDK to place some native ads in the stream.
The problem happens when I press on an item that appears below a native ad. The AbstractItem provided in the FastAdapter listeners is incorrect, probably because the adapter gets the wrong index from the item list.
Is there any way to solve this problem, without modifying MoPubRecyclerAdapter or having to implement my own wrap adapter?

@waninkoko could you please provide a sample app so I could debug this?

@mikepenz Sure, I'm gonna create a quick sample app right away.

@mikepenz A sample app that shows the issue: https://www.dropbox.com/s/dvghaanqp1smowa/MoPubRecyclerAdapterFastAdapter.zip?dl=0

@mikepenz Forgot to say that MoPubRecyclerAdapter provides a getOriginalPosition method that returns the position in the original adapter.

I was able to solve this issue by overriding getRelativeInfo(int position) this way:
@Override
public RelativeInfo<SongItem> getRelativeInfo(int position) {
    return super.getRelativeInfo(mopubRecyclerAdapter.getOriginalPosition(position));
}

@waninkoko I am not sure if I am able to have a closer look today. Will answer as soon as possible

@mikepenz Don't worry, thanks!
I was able to fix the issue with ClickListenerHelper by creating my own and getting the item with getRelativeInfo(int position) instead of getItem(int position)

@waninkoko the id you used in the sample application is it a demo id or a real one?

@mikepenz It's a demo id that MoPub provides to test native ads

@waninkoko great. thank you. added a clean solution to the latest release


attrs attribute with decorator based default not recognized as field with default value

 Environment data

Language Server version: 2022.10.41
OS and version: linux x64
Python version (and distribution if applicable, e.g. Anaconda): Miniconda + Python 3.9.13
python.analysis.indexing: null
python.analysis.typeCheckingMode: off

 Code Snippet

Using attrs v22.1.0 (https://www.attrs.org/en/stable/)
from attrs import define, field

@define
class MyClass:
    arg1: int
    kwarg1: int = 0
    kwarg2: int = field()
    kwarg3: int = 0

    @kwarg2.default
    def _kwarg2_default_factory(self):
        return 0

 Expected behavior
Pylance should recognize that the kwarg2 variable is a keyword argument and has a default value specified using the attrs decorator syntax. This should not raise any syntax errors.
 Actual behavior
Pylance underlines kwarg2 with a red squiggly line and specifies the error:
Fields without default values cannot appear after fields with default values

How do you disable this lint check? It's not obvious to me from the error message where this would be in https://github.com/microsoft/pyright/blob/main/docs/configuration.md#type-check-diagnostics-settings (if that's right at all).

How do you disable this lint check? It's not obvious to me from the error message where this would be in https://github.com/microsoft/pyright/blob/main/docs/configuration.md#type-check-diagnostics-settings (if that's right at all).

You should be able to simply add #noqa at the end of the affected line. i.e.
...
kwarg2: int = field()  #noqa
...

Pylance isn't a linter, it's a static type checker. (Linters tend to focus on code style issues, whereas type checkers validate type consistency and bugs that can result from type violations.) In a type checker, the way to suppress a diagnostic message on a particular line is to use a # type: ignore comment.

So there's no configuration setting to disable this globally?

Most diagnostics have an associated diagnostic rule that can be disabled independently. The specific diagnostic in this case (Fields without default values cannot appear after fields with default values) is currently not associated with a diagnostic rule, so it is always enabled. I think it's reasonable to move this to the reportGeneralTypeIssues diagnostic rule. That way, if you disable all type checking (i.e. set typeCheckingMode to "off"), it will be disabled globally. If that sounds like a good solution to you, please open a separate enhancement request so we can track that change.


Type 'ComponentWithAs<"textarea", TextareaProps>' is not assignable to type 'ComponentWithAs<"input", InputProps>'.

Probably not worth fighting the types here, I would cast it to any
InputOrTextarea = Textarea as any;

Probably not worth fighting the types here, I would cast it to any
InputOrTextarea = Textarea as any;


Implements the extends keyword for types defined in the dsl.

This allows you to inherit from types in the dsl, or from an external type introduced via the define options for a given flow.
#162

I am closing this in order to resubmit after removing code that is refactoring in support of this feature and placing it into a separate PR.


feat: allow to cancel a task that is cancellable

What does this PR do?
Get a cancel icon in the task manager to be able to cancel a task flagged as cancellable.
Screenshot / video of UI
https://github.com/user-attachments/assets/30d55ecb-2bf2-4947-a45d-10056cc7b670
What issues does this PR fix or reference?
fixes https://github.com/podman-desktop/podman-desktop/issues/9092
How to test this PR?

Install the extension from `quay.io/fbenoit/long-task-example:v1.0``
press F1 key to bring the command palette
select Dummy Long task (type dummy it will highlight the task)
click enter
Now open the task manager, see the task progressing and click on the cancel button to cancel it

[x] Tests are covering the bug fix or the new feature

Amazing job! Very nice to see the frontend come all together!
Do you think we could include the cancel action on the status bar ? (Here is an example of what I mean)

I wanted to ask UX people where to put the cancel icon on every implementation (panel, status, toast)

I mean, now it's very easy to handle it, just need to put an icon somewhere :-)

I wanted to ask UX people where to put the cancel icon on every implementation (panel, status, toast)

You want to wait the next UX call and put this PR on hold?

We'll need other tasks to add the cancel action in the status bar, or in the notifications. For now, I think this is a great start. We will have the rework of the task panel coming up shortly where the cancel action will be easier to trigger.

Everything can be follow-up, it's where we put the cursor.

Discussing the subject, it has been decided to not add the ability to cancel a task from the toast, but yes from the status bar
here is the follow-up for the status bar: https://github.com/podman-desktop/podman-desktop/pull/10100

@benoitf I would add an issue for e2e test to cover the feature, or do you think component tests are enough?

unit tests are ok but you can still have a e2e workflow
I would wait for the new task manager for that

pr rebased as there was a conflict


Installing Tekton Pipelines guide is not working

As mentioned in installation guide step 1, release.yaml is not present on the release bucket.
Expected Behavior
kubectl apply --filename https://storage.googleapis.com/tekton-pipeline-releases/latest/release.yaml

Should install Tekton pipeline resources
Actual Behavior
$ kubectl apply --filename https://storage.googleapis.com/tekton-pipeline-releases/latest/release.yaml
error: unable to read URL "https://storage.googleapis.com/tekton-pipeline-releases/latest/release.yaml", server reported 404 Not Found, status code=404

Steps to Reproduce the Problem

kubectl apply --filename https://storage.googleapis.com/tekton-pipeline-releases/latest/release.yaml

Additional Info
Maybe release is broken?

I think the release is not yet published on that bucket (cc @ImJasonH @bobcatfish) and still is on knative release bucket https://storage.googleapis.com/knative-releases/build-pipeline/latest/release.yaml it seems :angel:

yes, the release is in gs://knative-releases/build-pipeline/latest/release.yaml

created a PR to fix the file path for now

Thanks for the detailed report @hrishin - and the quick fix @pivotal-nader-ziada !! :heart:

(Will be creating Tekton specific buckets etc. in https://github.com/knative/build-pipeline/issues/527)


Route53 support

To enable wider k8gb adoption we need to add more common edgeDNS provider like AWS Route53

Extend k8gb with ability to automatically configure DNS zone delegation with Route53. Similar to functionality implemented with Infoblox API right now
Possibly use additional instance of external-dns for configuration assuming no special api calls apart from NS and A creation required.

I like the external-dns option. It would be compatible with many DNS providers. What would it take to implement it? Are there currently "special API calls apart from NS and A creation"? If I'm not mistaken, looking at the Git log, you used to go through external-dns to integrate with Infoblox, but switched to using the Infoblox API directly. Why?

@adrienjt you are totally right, the first attempt was to utilize external-dns for infoblox as well. We had to switch from this approach in case of Infoblox because it has special ZoneDelegated api call which creates NS and A records for name servers in one shot behind the scenes. Because of the fact that we could not create zone delegation with direct creation of DNS records( which would fit external-dns perfectly) so we had to replace it with direct api calls with infoblox-go-client.
I am evaluating route53 and overall external-dns integration for edgeDNS right now - unfortunately zone delegation config is inconsistent from provider to provider

Resolved by #169 , #172 and #179


reset method to reset the pointer to the beginning of the file

#4

can someone help to fix the error ? why i'm getting Bad Argument from fs.readSync ...

I've added reset method in 0.2.4.

I also added close method
https://github.com/nacholibre/node-readlines/pull/5/commits/ca26fe2e4ca71524c4624b67e73a51efbc706555
useful when searching for something in the file to avoid too many open files
while(la = a.next())
    b = new lineByline(path)
    while(lb = b.next())
         if (a.toString() == b.toString())
             found <- a.toString
             b.close()
             break
      print found

the file is closed when the end is reached, so this close() method is not necessary.

no it is useful, take the following example
if you have two files and you want to search for entries from the first file in the 2nd file.
you may find it at the middle of the file
if you dont close the file you will get too many open files" I close it now in this way fs.closeSync(file.fd)
while(la = a.next())
    b = new lineByline(path)
    while(lb = b.next())
         if (a.toString() == b.toString())
             found <- a.toString
             b.close()
             break
      print found

you should let ppl contribute, not just copy their contribution and commit them as yours!

I didn't copy anything, I've just implemented reset method, because you've requested and yours didn't pass the test.. I think I made you a favour.
I will not merge your pull request about the close method, because close method is not necessary.


Add Gitlink in the future.

Try to add GitLink the future since it is giving CI and local build problems. See https://github.com/GitTools/GitLink/issues/176

You should probably consider using SourceLink instead.

@Cheesebaron any cake addin for it yet?

You don't need a cake addin. It is something you add to your csproj file.

@Cheesebaron can you show me some usage of it please?


Incorrect handling of OpSwitch with 64-bit selectors

Description

RenderDoc's SPIR-V parser fails to correctly parse OpSwitch instructions that have a selector value whose type is a OpTypeInt with a width of 64.
This leads to the disassembler and debugger incorrectly handling shaders where such switches appear - the extra word per selector literal gets misinterpreted as a SSA reference.
I am the developer of shady, a research SPIR-V compiler that implements a higher baseline of capabilities. This issue came up while I was trying to diagnose some visual corruptions in one of my C++ shader samples.
The shader in question might have problematic constructs in it, but it does pass spirv-val and I have debugged and inspected RD itself and it's crystal clear that the PairLiteralIntegerIdRef struct is not adequate for handling cases of such switches.

The following function contains this instruction: OpSwitch %rshift_logical_149 %264 0 %265 1 %266 2 %267 3 %268 parses as
void generated_store_Generic_f32(ulong _259, float _260) {
  ulong rshift_logical_149 = _259 >> 62;

  switch(rshift_logical_149) {
      Unreachable();
    case 0:
      Unreachable();
      Unreachable();
    case 0:
      ulong rshift_logical_150 = _259 >> 61;
      ulong and_151 = rshift_logical_150 & 1;
      bool eq_152 = and_151 == 1;
      ulong select_153 = Select(eq_152,<PHONE_NUMBER>5282163712, 0);
      ulong and_154 = _259 &<PHONE_NUMBER>427387903;
      ulong or_155 = and_154 | select_153;
      generated_store_PrivatePhysical_varying_f32(or_155, _260);
      break;
    default:
      Unreachable();
  }

  return;
}

Note the incoherent layout and duplicated zero case. The actual source IR for that function is this:
@Generated fn generated_store_Generic_f32(varying u64 ptr~147, varying f32 value~148) {
    val varying u64 rshift_logical~149 = rshift_logical(ptr~147, 62);
    match(rshift_logical~149) {
        case 0:  {
            unreachable;
        }
        case 1:  {
            unreachable;
        }
        case 2:  {
            unreachable;
        }
        case 3:  {
            val varying u64 rshift_logical~150 = rshift_logical(ptr~147, 61);
            val varying u64 and~151 = and(rshift_logical~150, 1);
            val varying bool eq~152 = eq(and~151, 1);
            val varying u64 select~153 = select(eq~152,<PHONE_NUMBER>5282163712, 0);
            val varying u64 and~154 = and(ptr~147,<PHONE_NUMBER>427387903);
            val varying u64 or~155 = or(and~154, select~153);
            call (generated_store_PrivatePhysical_varying_f32)(or~155, value~148);
            yield();
        }
        default:  {
            unreachable;
        }
    };
    return();
}

The SPIR-V spec says the following about OpSwitch:

[...] Each literal is interpreted with
the type of Selector: The bit width of Selector’s type is the width of each literal’s type. If this width is not a
multiple of 32-bits and the OpTypeInt Signedness is set to 1, the literal values are interpreted as being
sign extended.

This means that you need the type of the selector to parse OpSwitch. I tried writing a RD PR to fix this, but unfortunately it looks to be architectured in such a way that the instruction parser only gets a slice of the words, where it'd need the surrounding context knowledge to know the selector's type.
Steps to reproduce
https://github.com/baldurk/renderdoc/files/13427757/rd_switch64_capture_fixed.zip
Using the linked capture, look at the disassembled shader (there's only one) or try to debug one of the pixels from the triangle.

(NB: The visual corruption is what I was initially debugging. It might be a driver bug. The RD issue is unrelated!)
Environment

RenderDoc version: Git commit 0d9ea809dd436b631874f65d100eac95764ef349
Operating System: Ubuntu 22.04 LTS
Graphics API: Vulkan

It's irrelevant to the SPIR-V parsing issue, but the GPU is a 6900XT and the driver is Mesa RADV 23.1.9 built in Debug mode.

Sorry! I updated the capture after someone pointed out another problem, and forgot to disable the workaround I made in the meanwhile. This capture should exhibits the issue properly.

Hi there
Thank you for reporting this issue. GLSL and HLSL don't appear to support switch statements with 64-bit selectors.
The support for 64-bit selectors has been added in 5bfb844643bd
I also explored the shader debugger with your capture.
When I ran the shader in the capture through "spirv-val" it gave this error
error: line 6: Operand 1 of MemoryModel requires one of these capabilities: PhysicalStorageBufferAddresses
If I edit the shader to add the missing capability then the shader debugger reports the shader can not be edited because is uses unsupported capability PhysicalStorageBufferAddresses (for reference that is Issue #2848)

BTW - the capture replays correctly in RenderDoc on Windows nVidia machine

Thanks! The visual corruption was my own fault (reading undefined values) and I was trying to diagnose it concurrently with reporting the Switch64 issue in RD. I believe the final capture I uploaded contained the fixes, but I have been tweaking it continuously and I may have regressed some other things accidentally, like declaring capabilities inconsistently. The fix looks good, thanks again!


Add a X button to clear the text input field in the model search screen

Should be a X to clear the input field. Currently only way to get back to the main discover page is to manually deleting all characters in the input field.

#251

Fixed by https://github.com/moxin-org/moxin/pull/251


Resolve Links in Editor.js

I am trying to get all data about a linked story but only get the overview data (uuid, cached_url). Is there a way to resolve links with the Storyblok bridge to get this type of data into the visual editor.

@aidenBarrett96 you should be able to achieve this by passing resolve_links into the requests in editor.js.  The resolveLinks key is only for gatsby-source-storyblok config.
  loadStory(payload) {
    const path = window.storyblok.getParam('path')
    window.storyblok.get(
      {
        slug: path,
        version: 'draft',
        resolve_links: sbConfig.options.resolveLinks || 'url',
        resolve_relations: sbConfig.options.resolveRelations || [],
      },
      (data) => {
        this.setState({ story: data.story })
      }
    )
  }

https://www.storyblok.com/docs/api/content-delivery#core-resources/stories/retrieve-multiple-stories

Hi @aidenBarrett96, I will be closing this issue, feel free to open it in the future if you need to.


feat: Collection notification - drops minting is live

Thank you for your contribution to the KodaDot - One Stop Shop for Polkadot NFTs.
👇 __ Let's make a quick check before the contribution.
PR Type

[x] Feature

Needs Design check

@exezbcz please review

Context

[x] Closes #9452

Did your issue had any of the "$" label on it?

[x] My DOT address: Payout

Screenshot 📸

[x] My fix has changed UI

/ahp/collection/95

/ahp/collection/91

Copilot Summary
copilot:summary
copilot:poem

thanks!

not showing on mobile:

not showing on mobile:

✅ Fixed

Thanks!
pay 30 usd

changed to api.tx.balances.transfer -> api.tx.balances.transferAllowDeath

pay 30 usd

😍 Perfect, I’ve sent the payout
💵 $30 @ 7.82 USD/DOT ~ 3.836 $DOT
🧗 16SjUbGKSdjCdWTy3NNT3JxbRVGGqD4mwkHpc6BD9U2Rp29Z
🔗 0x6870fb3460471174d05b6560f5277cdaddccb2ca3567150fc120925e8488bf80
🪅 Let’s grab another issue and get rewarded!
🪄 github.com/kodadot/nft-gallery/issues


[Feature] 28 Make models switchable through the config

This enables instantiation of the model through hydra
Closes #28

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

Project coverage is 99.84%. Comparing base (90ef59c) to head (6afb1cd).

Additional details and impacted files
@@           Coverage Diff            @@
##           develop      #45   +/-   ##
========================================
  Coverage    99.84%   99.84%
========================================
  Files           23       23
  Lines         1277     1277
========================================
  Hits          1275     1275
  Misses           2        2

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


Add TrafficControl API

TrafficControl is a feature which allows mirroring or redirecting the
traffic Pods send or receive. It enables users to monitor and analyze
Pod traffic, and to enforce custom network protections for Pods with
fine-grained control over network traffic.
This patch adds types and CRD for TrafficControl API.
Examples:

Mirror Pods (web=app) ingress traffic to a VXLAN tunnel

apiVersion: crd.antrea.io/v1alpha2
kind: TrafficControl
metadata:
  name: mirror-web-app
spec:
  appliedTo:
    podSelector:
      matchLabels:
        app: web
  direction: Ingress
  action: Mirror
  targetPort:
    vxlan:
      remoteIP: <IP_ADDRESS>

Redirect Pods (web=app) traffic in both direction to OVS internal
port firewall0 and expect the traffic to re-enter OVS via another OVS
internal port firewall1 if they are not dropped.

apiVersion: crd.antrea.io/v1alpha2
kind: TrafficControl
metadata:
  name: redirect
spec:
  appliedTo:
    podSelector:
      matchLabels:
        role: web
  direction: Ingress
  action: Redirect
  targetPort:
    ovsInternal:
      name: firewall0
  returnPort:
    ovsInternal:
      name: firewall1

For #3324
Signed-off-by: Quan Tian<EMAIL_ADDRESS>

Codecov Report

Merging #3644 (835bf6b) into main (ba8210c) will decrease coverage by 25.19%.
The diff coverage is n/a.

@@             Coverage Diff             @@
##             main    #3644       +/-   ##
===========================================
- Coverage   63.56%   38.37%   -25.20%
===========================================
  Files         278      114      -164
  Lines       39360    15442    -23918
===========================================
- Hits        25020     5926    -19094
+ Misses      12420     9042     -3378
+ Partials     1920      474     -1446

Flag
Coverage Δ

integration-tests
38.37% <ø> (?)

kind-e2e-tests
?

unit-tests
?

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

Impacted Files
Coverage Δ

pkg/ipam/poolallocator/allocator.go

...ntroller/networkpolicy/networkpolicy_controller.go

...agent/apiserver/handlers/appliedtogroup/handler.go

pkg/ipfix/ipfix_process.go

pkg/agent/apiserver/apiserver.go

pkg/controller/egress/validate.go

pkg/controller/ipam/antrea_ipam_controller.go

pkg/flowaggregator/apiserver/apiserver.go

pkg/monitor/controller.go

pkg/ovs/ovsctl/ofctl.go

... and 382 more

It seems that the branch has conflicts with the main branch and needs to rebase.

/test-all

@jianjuns In latest patch I added an optional destination port parameter for VXLAN and GENEVE tunnels since some systems use 8472 for VXLAN, and changed to use each type' own term for their tunnel IDs, for example, VNI for VXLAN, Key for GRE, and SessionID of ERSPAN.

/test-all

/test-networkpolicy


[Python] Python track2 autorest tools generate surplus files

Describe the bug
Please provide as much information as you can. This would be:
- OpenAPI files having the issues
- Autorest command used

ENV: Linux
Python:3.6.9
Command:/usr/local/bin/autorest //azure-rest-api-specs/specification/digitaltwins/resource-manager/readme.md --multiapi --python --python-mode=update --python-sdks-folder=//azure-sdk-for-python/sdk --track2 --use=<EMAIL_ADDRESS>--version=3.0.6272
(azure-rest-api-specs  repo: https://github.com/Azure/azure-rest-api-specs.git)
(azure-sdk-for-python repo : https://github.com/Azure/azure-sdk-for-python.git)
Expected behavior
The necessary Python code file is generated
ERROR

Additional context
Add any other context about the problem here.

@msyyc we're generatign a version file for digitaltwins because a package-versionn is present in the config file. We only generate a version file if a package-version is specified (though you can keep a current versioin file you already have with flag keep-version-file. Closinig this issue bc this behavior is expected

@msyyc we're generatign a version file for digitaltwins because a package-versionn is present in the config file. We only generate a version file if a package-version is specified (though you can keep a current versioin file you already have with flag keep-version-file. Closinig this issue bc this behavior is expected


new data source: covid hospitalization

Adds a new data source to the API, start to finish.
"COVID-19 Reported Patient Impact and Hospital Capacity by State Timeseries" dataset provided by the US Department of
Health & Human Services via healthdata.gov.
https://healthdata.gov/dataset/covid-19-reported-patient-impact-and-hospital-capacity-state-timeseries
Fixes #288

See individual commits for more details on what happens at each step.

add test data and code readme
implement network interface
implement database interface, including ddl for new tables
implement acquisition code
add new endpoint covid_hosp to api server
add same endpoint to all epidata clients
write integration tests for acquisition and serving
provide api documentation

repo-wide unit tests: ✔ All 52 tests passed!
repo-wide integration tests: ✔ All 29 tests passed!

@krivard thanks for the review, should be good to go!


how to change port number?

how to change port number?

As of now there is not such feature from UI, Still you can clone the repo and you can modify the port no in below file
Local-Mock-Server/public/express.js


build px4 above 1.80 does not work anymore macbook pro Sierra 10.12.6

Describe the bug
A clear and concise description of the bug.
To Reproduce
Steps to reproduce the behavior:

Drone switched on '...'
Uploaded mission '....' (attach QGC mission file)
Took off '....'
See error

Expected behavior
A clear and concise description of what you expected to happen.
Log Files and Screenshots
Always provide a link to the flight log file:

Download the flight log file from the vehicle (tutorial).
Share the link to a log showing the problem on PX4 Flight Review.

Add screenshots to help explain your problem.
Drone (please complete the following information):

Describe the type of drone.
Photo of the IMU / autopilot setup if possible.

Additional context
Add any other context about the problem here.

up to 1.80 make still works perfect for versions 1.82 and above the following error occurs:Failed to import yaml.
You may need to install it with 'sudo pip install pyyaml'
Traceback (most recent call last):
File "/Users/xxxxx/src/Firmware/Tools/serial/generate_config.py", line 13, in
import yaml
ImportError: No module named yaml
[13/1215] Copying NuttX/nuttx to build/px4_fmu-v4_default/NuttX
ninja: build stopped: subcommand failed.
make: *** [px4_fmu-v4_default] Error 1
(tried to install pyyaml and retried the whole homebrew procedure)

You need to install the dependencies according to the dev guide.

https://dev.px4.io/en/setup/dev_env.html

that I have done before ... all expect pypaml displays already installed.
src xxxxx$ sudo -H pip install pyserial empy toml numpy pandas jinja2 pyyaml
Password:
Requirement already satisfied: pyserial in /Library/Python/2.7/site-packages
Requirement already satisfied: empy in /Library/Python/2.7/site-packages
Requirement already satisfied: toml in /Library/Python/2.7/site-packages
Requirement already satisfied: numpy in /System/Library/Frameworks/Python.framework/Versions/2.7/Extras/lib/python
Requirement already satisfied: pandas in /Library/Python/2.7/site-packages
Requirement already satisfied: jinja2 in /Library/Python/2.7/site-packages
Collecting pyyaml
Could not fetch URL https://pypi.python.org/simple/pyyaml/: There was a problem confirming the ssl certificate: [SSL: TLSV1_ALERT_PROTOCOL_VERSION] tlsv1 alert protocol version (_ssl.c:590) - skipping
Could not find a version that satisfies the requirement pyyaml (from versions: )
No matching distribution found for pyyaml

Attention .... 1.8.2 doesn´t built with GCC 7.3.1 anymore which gets installed by the current  dependencies
1.8.2 needs GCC 7.2.1 then it works flawlessly with my Macbook Pro Sierra
1.9.0 needs GCC 7.3.1

@taileron regarding the pyyaml install failure, I googled this for you:
https://github.com/pypa/pip/issues/5226


Prepare for Spring Cloud Azure AppConfiguration 2.10.0

As title.

API change check
API changes are not detected in this pull request.


PR: Update README usage documentation

Fixes #27

Is there any section that we may need to add/update @goanpeca?

The coverage badge is missing. Let me activate it in coveralls.io

I'm afraid you'll have to add it. I don't have admin permissions here ;-)
Just log with your Github account and add the repo. Once you do that, you need to look for the repo token and add it to appveyor.yml as env var.

The process is exactly the same as the one in spyder-terminal.

Where is appveyor.yml in this repo? I don't understand how the tests are running...

@goanpeca is on charge of CI integration


review of 'inference from experimental data evidence' (ECO:0005611)

Hi @gthayman
As part of  ongoing curation of ECO, we are reviewing a number of terms, one of which is the RGD-requested term 'inference from experimental data evidence' (ECO:0005611).  Currently, this term is a child of 'direct assay evidence used in manual assertion' (ECO:000031).
Here is the definition for ECO:0005611:
"A type of direct assay evidence used in manual assertion where phenotype or disease association is made with the gene because of involvement in the molecular mechanism of disease or involvement in a pathway known to contribute to a disease."
There was also a comment in the original ticket for this term that talked about inferring a gene was part of a disease process when a treatment for the disease affected the gene's expression.
We feel that this definition indicates a situation where a curator draws a logical conclusion based upon transitive association of experimental results.  (gene A is in pathway Y, pathway Y is involved in disease X therefore gene A is associated with disease X.)
As such, this term should not be a child of 'direct assay evidence', rather we think it would be better placed as a child of 'combinatorial experimental and curator inference evidence' (ECO:0007012).
In addition, we feel the term label doesn't completely reflect what is in the definition and it is too similar to 'experimental evidence' ECO:0000006.
We suggest: 'curator inference from transitivity of experimental evidence'
Finally, we have some concerns about the definition in that it refers to phenotype and disease, but such associations could be made for other assertions as well. We'd prefer to make the definition more general and then put some specific examples in comments.
Before making any of these changes we wanted to reach out to you and make sure this is consistent with your meaning and use of the term.
Links to: https://github.com/evidenceontology/evidenceontology/issues/85

Hi @mgiglio99
We recently switched from using disease-specific evidence codes IED and IPM to IDA and IMP, respectively, so the first two can be obsoleted. I understand your concern about a transitive association. I myself don't make disease annotations based on a gene's involvement in a pathway, and after consulting with fellow curators, we think the definition phrase "or involvement in a pathway known to contribute to a disease" is inappropriate and can be removed, hopefully resolving the transitive association issue.

Thanks @gthayman
We will go ahead and and obsolete those two terms.

This term and its assertion terms have been deprecated.
ECO:0005611 - inference from experimental data evidence
ECO:0007293 - inference from experimental data evidence used in automatic assertion
ECO:0007189 - inference from experimental data evidence used in manual assertion
Thanks,
Suvvi


Enhancement Request: Business Hour Reporting

Create a power up that will remove datapoints from a time series graph that fall out of business hours. For example, I have a graph that shows AVG duration for each hour interval over the last 7 days. So a PU like !PU(bizhours):starttime:08:00;endtime:17:00. The the power up would remove all data points that are outside of 9am to 5pm. Maybe add in a parameter to include/exclude weekends.

This is perfect and agree this is huge need for Dynatrace engineers.  There is a RFE for it https://community.dynatrace.com/t5/Dynatrace-product-ideas/RFE-Support-for-Business-Hours-in-timeframe-selector/idi-p/154613

+1
I am trying to powerups for a heatmap during business hours only throughout a week and it will not report on the hours set within dynatraces custom timeframe reporting:

I think I can create a specific workflow in the BizOps Configurator. Here's what I'm thinking. The workflow will prompt for the interval...in your case that - 16:00-9:00 or 7 hours. I can then add in a prompt for business days. In your case that will be 6 days. I will support 5, 6 or 7 days as business days. The dashboard will work off of the beginning timeframe and then go from there. So you will deploy with 7 hours and 6 days. As long as you put your timeframe on any Tuesday at 9:00am, it should work. If you had your timeframe on Wednesday, it would display Wednesday - Monday. And if you had the hour at 10:00 am, it would calculate for 10:00am - 17:00pm. If that approach works for you, let me know and I'll test it out. But thinking that should work...

That sounds amazing!!! I think to start out we would want 5 days or Monday to Friday and have the hour interval either be 0900 to 1600 or 1700. Lastly another piece of complexity that sometimes arises comes from timezones. If we could add just a simple timezone (sometimes ZZ in date-fns) label to show what time zone is being reported on that would be amazing-er.

I made some changes and got things working for now. There are a few limitations that I will work on next week. Here's the workflow (connect to the configurator with GitHub as the changes I made won't be promoted to S3 until this evening):
https://dynatrace.github.io/BizOpsConfigurator/#deploy/persona/App Owner/Application Overview/Application Heatmap (💎)
Limit the app selection to 2-10. I need to make a change to get around the Explorer 10 row limit and will do that next week.
For the interval, use -1d as this makes the most sense for working hours heatmap.
For round down, use /d as this too makes the most sense.
I added 2 new widgets for start time and end time. I'll make that select easier next week, but for now use something like:
StartTime: +9h00m
EndTime: +17h00m
The good news is you don't have to mess with the global timeframe as every tile is autogenerated. So if I have a timeframe for anytime today, the heatmap will have day 1 as yesterday...9-5...and so on.
Let me know your thoughts. For now, weekends are included but I'll figure out an option to include/exclude that as well.

This is great but I am sure I messed up but didn’t see a StartTime or EndTime
From: TechShady @.>
Sent: Tuesday, April 5, 2022 1:45 PM
To: dynatrace-oss/DynatraceDashboardPowerups @.>
Cc: Kenneth Gillette @.>; Comment @.>
Subject: Re: [dynatrace-oss/DynatraceDashboardPowerups] Enhancement Request: Business Hour Reporting (Issue #143)
I made some changes and got things working for now. There are a few limitations that I will work on next week. Here's the workflow (connect to the configurator with GitHub as the changes I made won't be promoted to S3 until this evening):
https://dynatrace.github.io/BizOpsConfigurator/#deploy/persona/App Owner/Application Overview/Application Heatmap (💎)https://urldefense.com/v3/__https:/dynatrace.github.io/BizOpsConfigurator/*deploy/persona/App*20Owner/Application*20Overview/Application*20Heatmap*20(**C)__;IyUlJSXwn5KO!!Cz2fjcuE!gUjFYiUIBPbUtzqZlHTFcstJErQl77FP8CO7oY84fN3X3ymtICrziYw671f4QCvcQqhPXJphC__EJh1KGpP3rMOAYT5dElIFYAw$
Limit the app selection to 2-10. I need to make a change to get around the Explorer 10 row limit and will do that next week.
For the interval, use -1d as this makes the most sense for working hours heatmap.
For round down, use /d as this too makes the most sense.
I added 2 new widgets for start time and end time. I'll make that select easier next week, but for now use something like:
StartTime: +9h00m
EndTime: +17h00m
The good news is you don't have to mess with the global timeframe as every tile is autogenerated. So if I have a timeframe for anytime today, the heatmap will have day 1 as yesterday...9-5...and so on.
Let me know your thoughts. For now, weekends are included but I'll figure out an option to include/exclude that as well.
[image]https://urldefense.com/v3/__https:/user-images.githubusercontent.com/21313331/161817365-3ba4b56f-2a26-4838-9616-e1be4f9c9735.png__;!!Cz2fjcuE!gUjFYiUIBPbUtzqZlHTFcstJErQl77FP8CO7oY84fN3X3ymtICrziYw671f4QCvcQqhPXJphC__EJh1KGpP3rMOAYT5dIfZP8-o$
—
Reply to this email directly, view it on GitHubhttps://urldefense.com/v3/__https:/github.com/dynatrace-oss/DynatraceDashboardPowerups/issues/143*issuecomment-1089106036__;Iw!!Cz2fjcuE!gUjFYiUIBPbUtzqZlHTFcstJErQl77FP8CO7oY84fN3X3ymtICrziYw671f4QCvcQqhPXJphC__EJh1KGpP3rMOAYT5dnPlVguE$, or unsubscribehttps://urldefense.com/v3/__https:/github.com/notifications/unsubscribe-auth/AXWBYE3YZVL6UYZAYNCAOS3VDR3Y7ANCNFSM5RCL5FTQ__;!!Cz2fjcuE!gUjFYiUIBPbUtzqZlHTFcstJErQl77FP8CO7oY84fN3X3ymtICrziYw671f4QCvcQqhPXJphC__EJh1KGpP3rMOAYT5dnM8glTk$.
You are receiving this because you commented.Message ID<EMAIL_ADDRESS>
The information contained in this email message is being transmitted to and is intended for the use of only the individual(s) to whom it is addressed. If the reader of this message is not the intended recipient, you are hereby advised that any dissemination, distribution or copying of this message is strictly prohibited. If you have received this message in error, please immediately delete.
Member FINRAhttp://www.Finra.org / SIPChttp://www.Sipc.org
Copyright 2017 – LPL Financial. All Rights Reserved.


Update secret variable names

It looks like that in merging #33 some of the secret names have changed.

FYI @milen-sage - are the secrets we need to update/change documented somewhere?

@adamjtaylor I think this section  might help. @rrchai do you think GITHUB_TOKEN doc belongs there?

The above is linked from the main docs' deployment section.  The deployment section mainly describes how to setup CI/CD so all the steps should already be taken care off in thet upstream repo from the point of view of downstream forks. But I see how it's relevant, and perhaps needs to be extended for more detail, for situations when changes are made in the CI/CD process and those need to be validated downstream by projects.
I personally am looking forward for the single multi-tenant instance of DCA so that projects no longer need to take care of updates. We are working on that and should have a version by Nov 3 (we'll have one for testing mid-Nov).

@adamjtaylor @milen-sage
You are able to access the GITHUB_TOKEN without adding it to the secret.
see this pr

do you think GITHUB_TOKEN doc belongs there?
@milen-sage it looks like the doc has not been updated with the GITHUB_TOKEN yet


VSCode doesn't open file starting with NUL character

VSCode doesn't open file which starts with one or more NUL characters and has text following them.
It could present NUL character as empty space like notepad does.

Can you try to reproduce with our nightly insider builds? You can give our preview releases a try from: https://code.visualstudio.com/insiders/

Sure.


IE issue

If we empty the value in the input and clicked outside of the input or by clicking next button page is moving to top only  Internet Explorer. The problem is happening only when error message appears. Please suggest me a solution to fix this.
Please find the link below and open in IE11,
http://projects.lollypop.biz/resourcepro/policy-flow.html

Did you maybe used localisations?
Had the pitfall that I included not the distribution versions of the I18n stuff. That did not work in IE because the arrow functions breaks everything in IE11.
But with the right import everything is fine.


Issue links should only be created for comments or actual links

It's linkifying a bunch of CSS colors, ctrl+clicking them results in an error:

Code:
https://github.com/xtermjs/xterm.js/blob/5f0217cdb0baf353b3deedfab25e6e9b49c3d45f/addons/xterm-addon-webgl/src/WebglRenderer.api.ts#L898-L914
Some other problems I'm noticing with the detection:

It matches on ", " on some lines
It should not match when the number starts with #0, if using regex maybe do something like #[1-9][0-9]*?
It would be nice if giant numbers could be excluded based on the highest issue/PR number? Not sure if that's possible

Hmm, I don't think we have real API for determining a SymbolKind at a position. @aeschli is that correct?
Checking if a potential link is actually an issue would be quite costly, so that doesn't seem like a good option either.

This should be improved now.
However, there is no good way to determine if a something is a comment, so it's still not great.


Model is not training for 3rd organ(Mandible)

loss:   0%|          | 0/88 [00:00<?, ?it/s]
epoch 37 TRAIN loss 2.8312
test loss 0.8429, 0.4998, 0.0000, 0.6772, 0.6740, 0.8516, 0.8249, 0.7296, 0.7656
best test loss 0.8437, 0.5580, 0.0000, 0.7028, 0.7022, 0.8647, 0.8469, 0.7699, 0.7822
As you can see the loss is 0 for 3rd organ.
Any idea why this is happening?

Maybe you need to train longer. Empirically, some organs are 0 and you will get reasonable results after you train longer.

I see, just to give a little bit of more insight, I got a non-zero value when I trained with only PDDCA18 data. Now when I'm training with PDDCA18+HNCetuximab data I'm getting this 0 loss.

And the problem is that if I have this 0 loss the model weights corresponding to 3rd organ is not saved. Although that's not an issue in this case because I have weights saved corresponding to other organs, but just thought of confirming with you that its not an issue.

How many epoch did you use? Try to train longer time.

I trained it for 80 epochs with RMSprop optimizer. It took many hours for it to train.

In my code, I trained for 200 epochs. Did you use hybrid loss between dice and focal?

I didn't change any code except the paths and did a little bit of image resizing.
I've trained baselineSERes18Conc.py

The dice loss is implemented in https://github.com/wentaozhu/AnatomyNet-for-anatomical-segmentation/blob/master/src/AnatomyNet.py . Please use hybrid loss as described in the paper. AnatomyNet: Deep Learning for Fast and Fully Automated Whole‐volume Segmentation of Head and Neck Anatomy. Medical physics (2018).


Add black76 (and/or other models) support

I currently have the black76 model in a separate repo https://github.com/hayden4r4/black76-rust, but I believe we should fold it into this one.
This would effectively change this from a "blackscholes" repo to a "option valuation" repo, so it changes the scope, but lets us fit more use cases than black scholes alone applies to.
Given the similar api's I think its a good fit, we should look to modularize (is that a word?) the code better so we can drop in other option valuation models in the future more easily.
I'm open to discussion and or someone to give a shot at an implementation.

This was my next topic that I wanted to discuss. In my opinion, it fits perfectly to unify the approach.

https://github.com/hayden4r4/blackscholes-rust/blob/master/src/lets_be_rational/mod.rs
We have to change functions names to achieve correctness behaviour with different models.
we have here bsm so separation on module level (bsm, b76, bdt etc) or differnet func names?


asciidoctor: Init at 1.5.4

This was sitting in my personal repo until @aneeshusa suggested that I share it.
Asciidoctor is packaged with some of its optional dependencies, this is why there are both asciidoctor and asciidoctor-full as pkgs attributes names. I would very much like the help of someone versed in packaging gems to make this configurable.
Things done

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

[x] NixOS
[ ] OS X
[ ] Linux

[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Fits CONTRIBUTING.md.

The main question for whether to have a full version is whether the optional dependencies are very large (e.g. an optional dependency on Qt would count), and whether there are users who might want to avoid those dependencies (e.g. Git has an optional X11 dependency, but it's perfectly usable without, and there are scenarios like containers where you might want to have a small Git package). If either are not the case then it's probably better to drop the full version.

Just including asciidoctor-diagram and bespoke in the main asciidoctor package is fine. Other than that the packaging looks good to me.

I followed your suggestion and removed the asciidoctor-full attribute in favor to asciidoctor.
I also took the liberty to add the pdf and latex extensions. I don't use them but they are both popular, lightweight enough, and somewhat essential to cover all the use cases.
Also, I would be grateful if you could look at how to prevent bundlerEnv from creating unwanted executables. Currently, one is created in the bin folder for every dependency, which is unneeded.

Alright, take a look at pkgs/development/tools/continuous-integration/cide/default.nix to see how to only expose select binaries.

Thanks for the tip.
If I understand well, the derivation exposes a shell script that will call the given executable with the specified environment. This should do the trick but it adds a layer when none is needed. The environment of the executables are fine. I guess I could just rm the binaries I don't want.

Sure, removing the unecessary bin scripts in a postInstall step would also work. Ideally with a whitelist do new binaries don't emerge when upgrading the packages.

Is this ready?

It's almost ready, it just needs a bit of work to remove the unnecessary binaries that are being produces by the bundlerEnv.

I tried to add a whitelist attribute to bundlerEnv but finally decided to go the ugly route and delete manually the unneeded executables. It's much simpler and doesn't require to list the extensions.

perfect, thanks !

This isn't working for me, it can't find a mirror for asciidoctor-latex:
error: cannot download asciidoctor-latex-<IP_ADDRESS>.dev.gem from any mirror
builder for ‘/nix/store/0jfnhv9s40knjy07mab90sb2cl0z9dvn-asciidoctor-latex-<IP_ADDRESS>.dev.gem.drv’ failed with exit code 1

The URL returns a 404 as well.

I think this particular version has been yanked. https://rubygems.org/gems/asciidoctor-latex/ doesn't list it either.
@gpyh mind making another PR to bump the version to <IP_ADDRESS>.dev ?


Multiple "whereIn" statements causes problems

I have two whereIn statements, and the second one causes the entire SELECT statement to fail.
My code:
$property_classes = ["2-11"];
$zoning_classes = ["RT-4"];

$select = $pdo->select(["*"])
		 ->from("property_table AS p");
$select->whereIn("property_class_15", $property_classes);
$select->whereIn("zone_class", $zoning_classes);

print_r on $select outputs:
[values:protected] => Array
                (
                    [0] => RT-4
                    [1] => 2-11
                    [2] => TRUE
                )

            [table:protected] => propertytaxes_09_15_combined2 AS p
            [whereClause:protected] => Slim\PDO\Clause\WhereClause Object
                (
                    [container:protected] => Array
                        (
                            [0] =>  AND zone_class IN ( ? )
                            [1] =>  AND property_class_15 IN ( ? , ? )
                            [2] =>  AND ST_Intersects(p.geom, ST_Transform(ST_MakeEnvelope(-87.7193069458008,41.931360904903066,-87.7081596851349,41.93654878172632, 4326), 3435)) = ?
                        )

                )

Notice that property_class_15 has two ? yet it only has 1 corresponding value in the values array (2-11). If the property_class_15 has 2 corresponding values, then there will be three ?.
Why is the second whereIn statement increasing the number of placeholders by 1?

abstract class StatementContainer
`    /**
* @return string
*/
protected function getPlaceholders()
{
$placeholders = $this->placeholders;
    // reset($this->placeholders);  change to
    $this->placeholders = array();

    return '( '.implode(' , ', $placeholders).' )';
}`

Thanks @tonylevid - that change worked for me!

PR #75 merged. Patch release coming soon. 😉


"Added Cold Damage" is called "Ice Bite" in the "Calcs" window.

The skill gem "Added Cold Damage" is erroneously called "Ice Bite" in the "Calcs" / "Cold: Added Min/Max" window.
Should be easy enough to see for one self by adding a skill and support it with both "Added Cold Damage" and "Ice Bite". 2 x "Ice Bite" is showing.

Hi, I am unable to replicate in 1.4.137.

That is odd... and I can't replicate it again now.. I guess it must have been a ghost in the machine or something :)


Shortcuts don't show up in menus RTools > Windows

Ignore High-contrast.

We only bind Ctrl+2 in global. But I think we should bind Workspaces in global too.

in mtg, cant participate.  do people switch between R versions that
frequently or mainly when new versions show up?
On Tue, Feb 14, 2017 at 1:47 PM, Mikhail Arkhipov<EMAIL_ADDRESS>wrote:

We only bind Ctrl+2 in global. But I think we should bind Workspaces in
global too.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/Microsoft/RTVS/issues/3186#issuecomment-279846519,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAtUVNTPx0vzWye-MB9vKoQLFL8S56-3ks5rciECgaJpZM4MBBzL
.

https://github.com/Microsoft/RTVS/commit/79e4ef08a4dfc226d3f293f8ebd813eca2756d76


How to upgrade from styleGAN to styleGAN2?

Hi thanks for your great job! This is such the work I am always looking for. But I am wondering how I can upgrade the styleGAN in your architecture to styleGAN2, based on https://github.com/rosinality/stylegan2-pytorch.
Thanks a lot!

Hi, thanks for your kind words.
I would add it the same way rosinality does for the style in that ModulatedConv2d module. You could experiment combining the class and the activation with element-wise multiplication or other operators.


Allow importing velocity command from mcap files

This allows us to match simulated outputs to outputs from real robots. This should help investigate issues.

There are a number of issues with this:

Mcap / rosbag often contain a decent number of velocity commands. So far we have only tested with some simple sets with maybe 200 steps. Given that each step takes a few seconds this means that running a mcap/rosbag file would take a very long time (multiple hours)
The simulation code assumes that every end state is reachable and that it is reached at the end of the command. However in real life this isn't the case and so velocity commands are often send as a stream. In this case the motors don't necessarily reach the commanded velocities at the end of the time step. The simulation doesn't handle this at the moment so just reading in the velocity commands would lead to something odd.


Newest version is not build for MacOS

It seems like there is no build of the newest version 0.1.6 (as of writing this) for MacOS.
Is there a plan to support this platform ?

Hello, the extension isn't compatible with Mac OS unfortunately. If I find any solution that would allow me to make it work there I will let you know.


Add Storage Driver Context.

Carry #1070.  This PR implements review feedback.
Errors thrown by storage drivers don't have the name of the driver, causing user confusion about whether the error is coming from Docker or from a storage driver. This change adds the storage driver name to each error message.
This required changing ErrUnsupportedDriver to a type, leading to code changes whenever ErrUnsupportedDriver is used.
The tests check whether the driver name appears in the error message.
Closes: #664

Please sign your commits following these rules:
https://github.com/docker/docker/blob/master/CONTRIBUTING.md#sign-your-work
The easiest way to do this is to amend the last commit:
$ git clone -b "carry-1070" git@github.com:RichardScothern/distribution.git somewhere
$ cd somewhere
$ git rebase -i HEAD~2
editor opens
change each 'pick' to 'edit'
save the file and quit
$ git commit --amend -s --no-edit
$ git rebase --continue # and repeat the amend for each commit
$ git push -f

Ammending updates the existing PR. You DO NOT need to open a new one.

cc @amitshukla @stevvooe

LGTM


Wrong encoding

I am from russia.
So, when I encrypte backup file, english text is ok, but all cyrylic text is wrong in hieroglyphs.
And the encrypted file is in UCS-2 Little Endian, not in UTF-8.
What's happening?
Windows 10 64bit.

?

I'm unable to reproduce this on Linux. I suspect this may be an issue in Windows. I'll try and make time to spin up a VM to confirm that idea.

Actually, does the problem persist if you use the -o flag instead of piping output from the program? There's a couple of articles around that suggest the Windows terminal doesn't like UTF-8, so it may be being mangled in the pipeline.

Hi.
I was having the same issue, as my language is Spanish and I was having trouble getting the accentuated vowels (á, é, í, ó, ú) correctly. But after toying with the workaround mentioned here, and in #29 , I've managed to get those letters correctly, and the emojis too!
I'm using powershell as me default CLI, and I managed to get the correct result with this commands:
.\signal-back_windows_amd64.exe format -f XML .\signa-.backup | out-file "test.xml" -encoding oem
Emojis:

Accentuated vowels:

Perhaps it isn't an elegant solution, but as long as it works  ¯_(ツ)_/¯ ...

@antonio-gil Thank you very much! Now it's ok!

Glad to hear that, @kostas888 😃

The out-file Powershell cmdlet correctly handles UTF I would suspect. I'll mark this as closed unless the issue crops up again, and I'll add it to the wiki.


Update traceroute_test.go

Enabled the traceroute test cases and replaced the fake response
Test passed on different platforms:

http://sponge2/09d8a8b5-1611-4d6f-989c-d2c2b53aaed9
http://sponge2/41d797c2-ce5e-44a2-b2bb-b52badcbe0e8
http://sponge2/d541f713-a236-4011-97f7-3ed615f92e3f

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 70.423%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
1050

Relevant Lines:
1491

💛  - Coveralls

FYI, created #405 for documenting base config expectations

FYI, created #405 for documenting base config expectations

thanks a lot!


Bound TYPE_FLOAT strategy to IEEE 754 single-precision range

This PR fixes an issue in which values for protobuf float fields are generated which are outside IEEE 754 single-precision range. This manifests on some platforms (OSX) as a field packing error when attempting to serialize the message, e.g.:
Message(float_field=2.1762075962280267e+298).SerializeToString()
---------------------------------------------------------------------------
OverflowError                             Traceback (most recent call last)
<ipython-input-6-528e3539fcdc> in <module>()
----> 1 Message(float_field=2.1762075962280267e+298).SerializeToString()
lib/python2.7/site-packages/google/protobuf/internal/python_message.pyc in SerializeToString(self)
   1034           'Message %s is missing required fields: %s' % (
   1035           self.DESCRIPTOR.full_name, ','.join(self.FindInitializationErrors())))
-> 1036     return self.SerializePartialToString()
   1037   cls.SerializeToString = SerializeToString
   1038

lib/python2.7/site-packages/google/protobuf/internal/python_message.pyc in SerializePartialToString(self)
   1043   def SerializePartialToString(self):
   1044     out = BytesIO()
-> 1045     self._InternalSerialize(out.write)
   1046     return out.getvalue()
   1047   cls.SerializePartialToString = SerializePartialToString

lib/python2.7/site-packages/google/protobuf/internal/python_message.pyc in InternalSerialize(self, write_bytes)
   1049   def InternalSerialize(self, write_bytes):
   1050     for field_descriptor, field_value in self.ListFields():
-> 1051       field_descriptor._encoder(write_bytes, field_value)
   1052     for tag_bytes, value_bytes in self._unknown_fields:
   1053       write_bytes(tag_bytes)

lib/python2.7/site-packages/google/protobuf/internal/encoder.pyc in EncodeField(write, value)
    608         write(tag_bytes)
    609         try:
--> 610           write(local_struct_pack(format, value))
    611         except SystemError:
    612           EncodeNonFiniteOrRaise(write, value)

OverflowError: float too large to pack with f format

Because this is platform-dependent, the error cannot be reproduced on Linux - will need someone running OSX to verify the fix.

If we use travis for #1 we can run CI on linux+osx both

@Daenyth Looks as though it's relatively easy to integrate travis with tox, as well: https://github.com/tox-dev/tox-travis

Yes, I mentioned that in there ;)
tox-travis works well.


Pre-fill verify hashes if status is VerifiedConfigs

If you enter all the verification hashes then refresh, it asks you to do it again but you're already in VerifiedConfigs. We should pre-fill the inputs for you if you're in that state.

I think https://github.com/fedimint/ui/pull/256 closed this. Please re-open if I'm wrong.


Expand the documentation of COVIDcast signals

Work in progress. I'm expanding the API documentation for the COVIDcast signals so consumers clearly understand the new signals and their meaning.

Ready to go whenever the site updates go live.
(doesn't yet say which signals are used on the COVIDcast site; that's on my list to do tomorrow afternoon once we've actually decided that)


CSV export

export poll results to .csv file

exportable from both admin view and normal view with different accuracy?


Error with using PathPrefix

Do you want to request a feature or report a bug?
Bug
What did you do?
my docker-compose.yml conf:
version: '3'
services:
  traefik:
    image: traefik:2.0.0-rc3-alpine
    container_name: traefik
    command:
      - "--log.level=DEBUG"
      - "--api.insecure=true"
      - "--providers.docker=true"
      - "--providers.docker.exposedbydefault=false"
      - "--entrypoints.web.address=:80"
    ports:
      - "80:80" # The HTTP port
      - "443:443" # The HTTPS port
      - "8080:8080" # The web UI
    volumes:
      - /var/run/docker.sock:/var/run/docker.sock # So that Traefik can listen to the Docker events

  echo:
    image: echo-server:1.5.9-2
    ports:
      - 6001
    labels:
      - "traefik.enable=true"
      - "traefik.http.services.echo.loadbalancer.server.port=6001"
      - "traefik.http.routers.echo.rule=Host(`localhost`) && PathPrefix(`/echo`)"

For traefik v1 it worked:
- "traefik.frontend.rule=Host:localhost;PathPrefixStrip:/echo"

What did you expect to see?
On request localhost/echo i wanted to see response from echo-service
What did you see instead?
I saw error: Cannot get /echo
Output of 2.0.0-rc3-alpine: (What version of Traefik are you using?)
 time="2019-11-13T07:37:23Z" level=debug msg="vulcand/oxy/roundrobin/rr: completed ServeHttp on request" Request="{\"Method\":\"GET\",\"URL\":{\"Scheme\":\"\",\"Opaque\":\"\",\"User\":null,\"Host\":\"\",\"Path\":\"/echo\",\"RawPath\":\"\",\"ForceQuery\":false,\"RawQuery\":\"\",\"Fragment\":\"\"},\"Proto\":\"HTTP/1.1\",\"ProtoMajor\":1,\"ProtoMinor\":1,\"Header\":{\"Accept\":[\"text/html,application/xhtml+xml,application/xml;q=0.9,image/webp,image/apng,*/*;q=0.8,application/signed-exchange;v=b3\"],\"Accept-Encoding\":[\"gzip, deflate, br\"],\"Accept-Language\":[\"ru-RU,ru;q=0.9,en-US;q=0.8,en;q=0.7\"],\"Cache-Control\":[\"no-cache\"],\"Connection\":[\"keep-alive\"],\"Cookie\":[\"redirect_to=%252F; adminer_sid=41e6ebab91ba09970138b9a58485ae16; adminer_key=d1556ec57b7048bae092c61278c0bc4b\"],\"Pragma\":[\"no-cache\"],\"Sec-Fetch-Mode\":[\"navigate\"],\"Sec-Fetch-Site\":[\"none\"],\"Sec-Fetch-User\":[\"?1\"],\"Upgrade-Insecure-Requests\":[\"1\"],\"User-Agent\":[\"Mozilla/5.0 (Macintosh; Intel Mac OS X 10_14_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/78.0.3904.70 Safari/537.36\"],\"X-Forwarded-Host\":[\"localhost\"],\"X-Forwarded-Port\":[\"80\"],\"X-Forwarded-Proto\":[\"http\"],\"X-Forwarded-Server\":[\"a4ab8fc6fb98\"],\"X-Real-Ip\":[\"<IP_ADDRESS>\"]},\"ContentLength\":0,\"TransferEncoding\":null,\"Host\":\"localhost\",\"Form\":null,\"PostForm\":null,\"MultipartForm\":null,\"Trailer\":null,\"RemoteAddr\":\"<IP_ADDRESS>:35008\",\"RequestURI\":\"/echo\",\"TLS\":null}"

Hi @rodosskiand , can you switch to the Community forum at https://community.containo.us/ ,
as this is not a bug but a configuration issue, thanks a lot!
Some key points to help you:

Please use the stable version of Traefik, aka. traefik:v2.0 or traefik:v2.0.4, as you are using a release candidate with known bug
The documentation provides explanation on how to migrate from PathPrefixStrip at https://docs.traefik.io/v2.0/migration/v1-to-v2/#strip-and-rewrite-path-prefixes
For the docker-compose's service echo:, please switch from ports: (ref.https://docs.docker.com/compose/compose-file/#ports) to expose: as you don't want to publish the port outside the private network of the stack.


[filebeat|elasticsearch] Labels not propagated to pods

Chart version: 7.4.1
Kubernetes version: 1.14
Kubernetes provider: AWS EKS
Helm Version: 2.15.2
helm get release output
---
# Source: filebeat/templates/daemonset.yaml
apiVersion: apps/v1
kind: DaemonSet
metadata:
  name: filebeat-filebeat
  labels:
    app: "filebeat-filebeat"
    chart: "filebeat-7.4.1"
    heritage: "Tiller"
    release: "filebeat"
    app.kubernetes.io/name: "filebeat"
spec:
  selector:
    matchLabels:
      app: "filebeat-filebeat"
      release: "filebeat"
  updateStrategy:
    type: RollingUpdate
  template:
    metadata:
      annotations:

        configChecksum: 63c911247bda6752c8d4a661a974be82c68ce8bc7d1fc4797fdf8cfffa7ea67
      name: "filebeat-filebeat"
      labels:
        app: "filebeat-filebeat"
        chart: "filebeat-7.4.1"
        heritage: "Tiller"
        release: "filebeat"
    spec:
      serviceAccountName: filebeat-filebeat
      terminationGracePeriodSeconds: 60
      volumes:
      - name: elasticsearch-es-certificates-pem
        secret:
          secretName: elasticsearch-es-certificates-pem
      - name: filebeat-config
        configMap:
          defaultMode: 0600
          name: filebeat-filebeat-config
      - name: data
        hostPath:
          path: /var/lib/filebeat-filebeat-monitoring-data
          type: DirectoryOrCreate
      - name: varlibdockercontainers
        hostPath:
          path: /var/lib/docker/containers
      - name: varrundockersock
        hostPath:
          path: /var/run/docker.sock
      containers:
      - name: "filebeat"
        image: "docker.elastic.co/beats/filebeat:7.4.1"
        imagePullPolicy: "IfNotPresent"
        args:
        - "-e"
        - "-E"
        - "http.enabled=true"
        livenessProbe:
          exec:
            command:
            - sh
            - -c
            - |
              #!/usr/bin/env bash -e
              curl --fail <IP_ADDRESS>:5066
          failureThreshold: 3
          initialDelaySeconds: 10
          periodSeconds: 10
          timeoutSeconds: 5

        readinessProbe:
          exec:
            command:
            - sh
            - -c
            - |
              #!/usr/bin/env bash -e
              filebeat test output
          failureThreshold: 3
          initialDelaySeconds: 10
          periodSeconds: 10
          timeoutSeconds: 5

        resources:
          limits:
            cpu: 200m
            memory: 150Mi
          requests:
            cpu: 10m
            memory: 50Mi

        env:
        - name: POD_NAMESPACE
          valueFrom:
            fieldRef:
              fieldPath: metadata.namespace
        - name: ELASTICSEARCH_USERNAME
          valueFrom:
            secretKeyRef:
              key: ELASTICSEARCH_USERNAME
              name: elasticsearch-filebeat-credentials
        - name: ELASTICSEARCH_PASSWORD
          valueFrom:
            secretKeyRef:
              key: ELASTICSEARCH_PASSWORD
              name: elasticsearch-filebeat-credentials

        securityContext:
          privileged: false
          runAsUser: 0

        volumeMounts:
        - name: elasticsearch-es-certificates-pem
          mountPath: /usr/share/filebeat/certs
        - name: filebeat-config
          mountPath: /usr/share/filebeat/filebeat.yml
          readOnly: true
          subPath: filebeat.yml
        - name: data
          mountPath: /usr/share/filebeat/data
        - name: varlibdockercontainers
          mountPath: /var/lib/docker/containers
          readOnly: true
        # Necessary when using autodiscovery; avoid mounting it otherwise
        # See: https://www.elastic.co/guide/en/beats/filebeat/master/configuration-autodiscover.html
        - name: varrundockersock
          mountPath: /var/run/docker.sock
          readOnly: true

Describe the bug: For labels, the README says:

Configurable label applied to all Filebeat pods

However, labels are not applied to Pods. They're only applied to the DaemonSet object at metadata.labels (values.yaml). See: https://github.com/elastic/helm-charts/blob/7.4.1/filebeat/templates/daemonset.yaml#L11
They should also be applied at spec.template.labels.
This appears to be a bug with the elasticsearch chart as well.
Steps to reproduce:

Define a label in values.yaml. Key = labels. Example label: app.kubernetes.io/name: "filebeat"
Helm upgrade.

Expected behavior: Labels applied to pods
Provide logs and/or server output (if relevant):
Any additional context:

Related to #383


[BUG] "include" in TW config file crashes taskwarrior-syncall

Taskwarrior allows to include theme or external config file (it's great to store sync configuration in different location). With those configuration taskwarrior-syncall crashes.
To Reproduce
In .taskrc
include light-16.theme
include ~/task/wingtask
Error
Traceback (most recent call last):
  File "/home/miro/.local/bin/tw_gcal_sync", line 8, in <module>
    sys.exit(main())
  File "/usr/lib/python3.10/site-packages/click/core.py", line 1130, in __call__
    return self.main(*args, **kwargs)
  File "/usr/lib/python3.10/site-packages/click/core.py", line 1055, in main
    rv = self.invoke(ctx)
  File "/usr/lib/python3.10/site-packages/click/core.py", line 1404, in invoke
    return ctx.invoke(self.callback, **ctx.params)
  File "/usr/lib/python3.10/site-packages/click/core.py", line 760, in invoke
    return __callback(*args, **kwargs)
  File "/home/miro/.local/lib/python3.10/site-packages/taskwarrior_syncall/scripts/tw_gcal_sync.py", line 142, in main
    tw_side = TaskWarriorSide(tags=tw_tags, project=tw_project)
  File "/home/miro/.local/lib/python3.10/site-packages/taskwarrior_syncall/taskwarrior_side.py", line 53, in __init__
    self._tw = TaskWarrior(marshal=True, config_filename=config_file)
  File "/home/miro/.local/lib/python3.10/site-packages/taskw/warrior.py", line 438, in __init__
    super(TaskWarriorShellout, self).__init__(config_filename)
  File "/home/miro/.local/lib/python3.10/site-packages/taskw/warrior.py", line 62, in __init__
    self.config = TaskWarriorBase.load_config(config_filename)
  File "/home/miro/.local/lib/python3.10/site-packages/taskw/warrior.py", line 180, in load_config
    return TaskRc(config_filename, overrides=overrides)
  File "/home/miro/.local/lib/python3.10/site-packages/taskw/taskrc.py", line 58, in __init__
    config = self._read(self.path)
  File "/home/miro/.local/lib/python3.10/site-packages/taskw/taskrc.py", line 106, in _read
    TaskRc(right.strip())
  File "/home/miro/.local/lib/python3.10/site-packages/taskw/taskrc.py", line 58, in __init__
    config = self._read(self.path)
  File "/home/miro/.local/lib/python3.10/site-packages/taskw/taskrc.py", line 96, in _read
    with codecs.open(path, 'r', 'utf8') as config_file:
  File "/usr/lib/python3.10/codecs.py", line 905, in open
    file = builtins.open(filename, mode, buffering)
FileNotFoundError: [Errno 2] No such file or directory: 'light-16.theme'

versions
tw_gcal_sync, version 1.2.1
taskwarrior 2.6.2

Pending PR in taskw that fixes this: https://github.com/ralphbean/taskw/pull/151

The taskw repo doesn't seem to be in active development anymore and thus, the PR above is not merged yet. We should either fork and push our own versions of taskw or, alternatively, switch to tasklib (see https://github.com/bergercookie/syncall/issues/65).