GUI won't build

There isn't a lot of documentation, so forgive me if I missed something but I was trying to run the gui.sln and the build failed. Debugging also failed because the debugging target "monopoly.exe" was missing.
No idea what to do from here, so was hoping for some documentation that could clarify this.

Hi Yash,
You're right that the documentation about how to run the GUI is fairly
limited. There is quite a lot of documentation about how to write AIs here:
http://richard-shepherd.github.io/monopyly/index.html
It's been a long time since I looked at this. Here are some things
which should get things going:
It looks like running a tournament with the available AIs fails. The sample
AIs do work though. So you can:

Rename the AIs folder to AIs.old
Rename the SampleAIs folder to AIs
Run python main.py

This should work and run a tournament.
To build the GUI, it looks like Visual Studio is more fussy about building
content downloaded from the web than it used to be. A number of the files
are blocked. To unblock them in Powershell you can run this:
Get-ChildItem -Path .\monopyly\ -Recurse | Unblock-File
(This is assuming you are running from the folder one up from the monopyly
code, and that the code is in a folder called 'monopyly'.)
The GUI code should then build.
To run the GUI and have it connect to a game, you need to uncomment the
line below "Sends updates to the C# GUI" in main.py.
That said - I think it will still fail to connect. The messaging uses zmq,
and you will need to install this for Python and also protobuf. But... I
think the versions used were quite old (2013) and I think that the latest
versions are no longer compatible with the code. So if you want the GUI and
the communication to it to work, you will need to do a bit of investigation
/ debugging.
Good luck!
Richard
On Mon, Aug 9, 2021 at 7:20 PM Yash Sabarad @.***>
wrote:

There isn't a lot of documentation, so forgive me if I missed something
but I was trying to run the gui.sln and the build failed. Debugging also
failed because the debugging target "monopoly.exe" was missing.
No idea what to do from here, so was hoping for some documentation that
could clarify this.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/richard-shepherd/monopyly/issues/2, or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABLHQMHTCUQ7GJNJFDWZVXLT4AL5RANCNFSM5B2RL5PA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&utm_campaign=notification-email
.


API review: Remove NullLogger and related classes

NullLogger
NullLoggerFactory
NullDisposable

NullDisposable is used in one place by the TestLogger. Current thought is to just use null instead of NullDisposable.Instance, this works fine as long as .Dispose is not explicitly called on the "IDisposable" which it isn't in all the tests that use this


The difference between your implementation and  official  implementation

Thanks for your work . But I have a question , the  official  implementation can't change the output channel,  why yours can?

Hey @LJill, good question, so in case the number of input channels differs from the number of output channels, a 1X1 convolution is utilized to adapt the channels, of the input tensor.
https://github.com/ChristophReich1996/Involution/blob/2263b6237f837b63051de12773e917b67a740abf/involution/involution.py#L72-L74
Cheers
Christoph


Update to 0.3.2 to encompass package version updates

0.3.1 is in the Python code, but that doesn't influence the package versions.  Get them too,
and update to 0.3.2

@trhoden if you wouldn't mind fast-forward merging this, then there will be no merge commit on the tip of the branch when you tag

@ktdreyer yeah, I can do that.
@dmick shoot, sorry about this.  I'm too used to ceph-deploy, where changing the Python code is the only thing I need to do (Jenkins does the .spec and debian changes for me).


[Bug]: Upgrade to 1.19.27 breaks several widgets

Is there an existing issue for this?

[X] I have searched the existing issues

Description
After upgrading to 1.19.27, several of our widgets are broken:

Images in a common header copied between pages were lost on two of the three pages
A container in the header container on all three pages now has scrolling and a shadow enabled that were previously disabled
Two containers with several widgets in them are now empty

Steps To Reproduce

change deployed version number from 1.19.26 to 1.19.27
restart appsmith

Public Sample App
No response
Environment
Production
Issue video log
No response
Version
Self Hosted 1.19.27

This has been fixed in the v1.9.28 which was release today morning. Please follow the below steps to upgrade
Upgrade your instance to v1.9.28 (for self-hosted).
Revert your branch to the commit before v1.9.27 and push to remote repo.
This is the last commit they made before upgrading to v1.9.27.
This can be done by cloning the repo locally or through the GitHub desktop app.
Pull the reverted branch on Appsmith.

@hweissig This has been fixed in the v1.9.28 which was release today morning. Please follow the below steps to upgrade

Upgrade your instance to v1.9.28 (for self-hosted).
Revert your branch to the commit before v1.9.27 and push to remote repo.
This is the last commit they made before upgrading to v1.9.27.
This can be done by cloning the repo locally or through the GitHub desktop app.
Pull the reverted branch on Appsmith.

I am getting the following error when updating the version to 1.9.28 as suggested:
Error response from daemon: manifest for appsmith/appsmith-ce:v1.9.28 not found: manifest unknown: manifest unknown

Reverting the changes made by upgrading to 1.9.27 and deploying 1.9.28 (as latest) has resolved most of the issues we saw with the 1.9.27 upgrade. The one remaining issue (scrolling enabled for a container that previously had it disabled) was easy enough to fix.
FWIW, we also had a lot of trouble getting a simple color change in the theme of our app to stick after upgrading to 1.9.26, which seems to have been a problem introduced between 1.9.12 and that version. 1.9.27 already seems to have addressed that and it is no longer an issue in 1.9.28 either, it seems.


entra group user list / list nested groups

entra group user list does not show nested security groups. It shows only member users but does not show member groups.
It would be useful to be able to get groups or to get users+groups.
Filtering happens because of the microsoft.graph.user part in group-user-list.ts:184:
const endpoint: string = `${this.resource}/v1.0/groups/${groupId}/${role}/microsoft.graph.user?$select=${selectParam}${expandParam}`;

To get groups microsoft.graph.group can be used:
const endpoint: string = `${this.resource}/v1.0/groups/${groupId}/${role}/microsoft.graph.group?$select=${selectParam}${expandParam}`;

To get user + groups no microsoft.graph.* is needed:
const endpoint: string = `${this.resource}/v1.0/groups/${groupId}/${role}?$select=${selectParam}${expandParam}`;

@pnp/cli-for-microsoft-365-maintainers what is our stance on this? In my opinion, it's not really ideal that we only return users and not groups.

@milanholemans, @dojcsakj I totally agree. I think it would be a great improvement to show always all members of a group, so users and groups.
I only wonder if we should create a new command for it like entra group member list that would list out groups and users and in the current command, so entra group user list we mark is as deprecated and suggest using the ..member list command and for v8 we could remove it. 🤔 @pnp/cli-for-microsoft-365-maintainers what do you think?
it would also align with what we have in spo  so spo group member list

Fully agree that this kind of command should return all the members including the associated groups.
Good point @Adam-it, if we do apply this change, the command would be much clearer as entra group member list instead of user.

In that case, shouldn't we move all group user commands to group member?

In that case, shouldn't we move all group user commands to group member?

@milanholemans but that would mean we need to add support for subgroups in the other commands as well right?

Yes, that would mean we have to add support for this to entra group user set and entra group user add. entra group user remove is still an open PR of me, so I can easily adapt that one.

Yes, that would mean we have to add support for this to entra group user set and entra group user add. entra group user remove is still an open PR of me, so I can easily adapt that one.

yes lets do that.
So to sum up:

we will deprecate (and in v9 if possible remove) the entra group user.... commands in favor of entra group member... commands
we will add support for subgroups to those commands as well

am I right?
if so lets update the initial message of this post to align naming and open it up and create a new epic issue to update the other commands as well
@pnp/cli-for-microsoft-365-maintainers ?

Looks good to me.

Looks good to me.

@milanholemans do you want to take the lead on the related epic or should I do that?
@dojcsakj lets update the naming in your initial issue request. Lets mention that the ... group user list should be marked as deprecated and we should move this logic to ...group member list command which will now support subgroups as well

If you have time, go ahead creating the issue 😊
If not, I can put it on my todo list.

V10 issue has been made, will create other issues to enhance current commands (with group options) soon.

In the last major release, we've updated entra group user list to entra group member list which will also return sub-groups now. I also just created #6480 to introduce support for adding sub groups. If that issue has been reviewed, I will update my PR #5844 for the remove command with support for sub-groups as well.
I think, for now, we can close this issue. Thank you once again for pointing this out @dojcsakj!


Safari compatibility issues

Describe the bug
While browsing the slides of a presentation made with slidev, this caused an interception error with Docusaurus resulting in the index of the page going out off bounds and returning a "Page not found" error. You should go to this issue to see a more in-depth discussion about the problem.
To Reproduce
Steps to reproduce the behavior:

Go to https://embedded-rust-101.wyliodrin.com/docs/lecture/01
Browse through any of the lectures at a moderately high speed using the integrated toolbar at the bottom left of the slides until the end (works from beginning to end and vice versa)
See the error

Desktop (please complete the following information):

OS: macOS Monterey version 12.3.1
Browser: Safari
Slidev version: 0.48.9

I am not sure how to fix this. What can Slidev do to prevent this from happening?

Seems to be dependent on the operating system/browser (macOS/Safari). I've tried replicating the bug on Debian -> Firefox browser + Windows 10 -> OperaGx, and I've only managed to replicate it 2 times.

Close this because cannot be reproduced stably


Dolphin with Super Mario Sunshine hits assertion

When running SMS in dolphin with a release build the rendering is incomplete (other games seem to work fine). The debug build hits an assertion :
dolphin-emu: /home/zenyd/Downloads/amdvlk/drivers/llvm/lib/Target/AMDGPU/SIISelLowering.cpp:8368: llvm::SDNode* llvm::SITargetLowering::adjustWritemask(llvm::MachineSDNode*&, llvm::SelectionDAG&) const: Assertion `NewOpcode != -1 && NewOpcode != static_cast<int>(Node->getMachineOpcode()) && "failed to find equivalent MIMG op"' failed.
To reproduce you need to run dolphin with sms_fifo.dff.zip and the following command:
dolphin-emu -b -e sms_fifo.dff
The game is working fine with radv.
Backtrace of assert
Dolphin: dolphin-emu-git-5.0.r8518.d425732837
Hardware:Mullins

@zenyd Can you help to dump pipelines and shader since I cannot reproduce the issue on my desktop ? Thanks!
The way to dump pipelines:

vi /etc/amd/amdPalSettings.cfg
add following lines:
EnablePipelineDump,1
PipelineDumpDir,<dump_dir_path>  (PipelineDumpDir is a sub-path relative to $AMD_DEBUG_DIR or $TMPDIR or /var/tmp/)

Hello @crystalJinamd, I am somehow not able to reproduce this issue myself anymore! I think it was something on my end, maybe a broken shader cache or something. Sorry for the noise!


feat: integrate asyncapi diff library using the diff command

Description
This PR integrates the asyncapi-dff library using the diff command.
At the moment, the command looks something like this.
asyncapi diff <file-path/context-1> <file-path/context-2>

And it has two flags:
--format(default and only acceptable right now value: json) which determines the format of the output.
--type(all (default) , breaking, non-breaking, unclassified) which determines the type of the output we want.
At the moment, the output is being logged to stdout. The support for outputting data into files is to be added(which is most likely to be done by me, whether in this PR or another one depends on the review :) ).
Related issue(s)

See https://github.com/asyncapi/cli/issues/58

Thanks for the reviews. Will make the changes ASAP.

@aayushmau5 hey, tests are failing because of linter.

This is something new

Yeah, confused as to why this is happening. Let me check if this has something to do with the context I'm setting in the tests.

@aayushmau5 you need a hand? or two? 😄

Yeah :sweat_smile: Not sure why the test fails in windows even though I have not used any context in the tests for diff command :confused:

looking at logs Error: EPERM: operation not permitted, open 'C:\Users\runneradmin\.test.asyncapi' looks like tests fail as there is no access to the config file that keeps context, and test that removes it, cannot do it because it has no rights to do it.
super strange that it is happening right now, they had to do some updates to VM or something.
The problem is I have no idea how to solve it, other than adding a NODE_ENV that you can use in tests to override default context location. This way you could provide location that can be easily modified by the workflow.
@Souvikns @boyney123 @magicmatatjahu thoughts?
to summarize, I'm thinking about modifying these 3 lines -> https://github.com/asyncapi/cli/blob/master/src/models/Context.ts#L8-L10
const isTestEnv = !!process.env.TEST;
const CONTEXT_FILENAME = isTestEnv ? '.test.asyncapi' : '.asyncapi';
export const DEFAULT_CONTEXT_FILE_PATH = path.resolve(os.homedir(), CONTEXT_FILENAME);

with something like
const CONTEXT_FILENAME = process.env.CONTEXT_FILENAME || '.asyncapi';
export const DEFAULT_CONTEXT_FILE_PATH = process.env.CONTEXT_FILE_PATH || path.resolve(os.homedir(), CONTEXT_FILENAME);

and then just update test script in package.json to provide custom name and path location

const isTestEnv = !!process.env.TEST;
const CONTEXT_FILENAME = isTestEnv ? '.test.asyncapi' : '.asyncapi';
export const DEFAULT_CONTEXT_FILE_PATH = path.resolve(os.homedir(), CONTEXT_FILENAME);

we have this so that while testing we don't overwrite the global config file. I think we should just check if it is test env then we should choose .test.asyncapi or choose something from the env variable.
const CONTEXT_FILENAME = isTestEnv ? process.env.context_file_path || '.test.asyncapi' : '.asyncapi'

@Souvikns the thing is that we should have no test-related logic in library, this is why I propose that we have all customizable and we just override it in the test script, and we create context config in test dir during testing, and make sure the file is in gitignore

@Souvikns the thing is that we should have no test-related logic in library, this is why I propose that we have all customizable and we just override it in the test script, and we create context config in test dir during testing, and make sure the file is in gitignore

Oh now I get it, yeah that would be better

hmm :confused: , so the problem still persists. I guess we can try this. @derberg Should I make the changes in this PR or make a new one?

as this is super small change, you can do it in this PR. Cleaner would of course be separate.

So, I'm putting CONTEXT_FILENAME to .test.asyncpi, what should I put into CONTEXT_FILE_PATH?

so, the problem still remains :confused:

I wonder if this bug is occurring due to the tests I added in this PR? Since the other PRs doesn't seem to have this problem.

I wonder if this bug is occurring due to the tests I added in this PR? Since the other PRs doesn't seem to have this problem.

commented out the test, and the test for windows still fails.

@aayushmau5 the tests are working now, check once.

oh, neat! Looks like triggering the workflow again solves the problem.

@derberg since AsyncAPI spec loader already supports loading with URL, I should just make the description changes, right?

also I don't think that you need a dedicated test of url really. You are testing generic CLI functionality and not the ones added by diff command. Isn't it kinda redundant?

Right! I will remove them.

@aayushmau5 I closed and reopened hoping that this will force CI to run on a different worker. Rerun of job did not help 😞

I opened https://github.com/actions/virtual-environments/issues/4902

Great! :crossed_fingers:

@aayushmau5 there is a workaround proposed, please have a look https://github.com/actions/virtual-environments/issues/4902#issuecomment-1019845960 it kinda makes sense

The NodeJS doc says, "Existing hidden files can be opened for writing with the 'r+' flag."
But I don't think the test.asyncpi context file already exists. Adding the r+ flag locally results in failed tests :(

yeah, and in case of tests, context is actually not a hidden file but regular test.asyncapi file

@aayushmau5 some more hints -> https://github.com/actions/virtual-environments/issues/4902#issuecomment-1020051944

@derberg How about I close this PR, and make another one? Would that do anything :thinking:

The problem is I saw the same on another PR :(
How did checks work, so are we sure the context file actually exists?

@aayushmau5 how is it? you mind if I push some code into this PR on my own to play a bit? it is the only way i can test on windows :)

Sure! Go ahead.

@aayushmau5 I think I fixed it. The problem was related to wrongly written tests. Like not tests themselves, just wrong usage of mocha. The thing is that the before and after hooks were in the wrong location, they need to be combined with it. So it was failing randomly as sometimes they run properly and sometimes hooks were not fired properly, and write to the disk was failing as the file was there already, not removed because the hook that was supposed to delete it was too late.
can you have a final look and cleanup stuff that are actually not needed, this access checking and special options passed to writeFileSync. Also please adjust your diff tests accordingly

Awesome! Thanks, @derberg

can you have a final look and cleanup stuff that are actually not needed, this access checking and special options passed to writeFileSync. Also please adjust your diff tests accordingly

Yeah! I will refactor some code.

@aayushmau5 your test still runs outside it function, have a look at the context tests and how I changed them

what did we agree on with another flag that is needed, to enable user to pass a path to custom standard?

Oops, I don't think we have discussed this :thinking: . I completely forgot about passing custom standard.
What flag should we go with? Also, I'm assuming this file will be a json file(or we should treat it as such)?

yeah, just enable what API of the diff library allows you to do. So definitely a json file, and I think --overrides is good, just provide good help description

@derberg It seems adding tests like
it(..., () => {
	it(..., () => {})
})

results in the tests passing no more whether it really fails or not.
But
describe(..., () => {
	it(..., () => {})
})

seems to work fine.

@aayushmau5 yes, go ahead with
describe(..., () => {
	it(..., () => {})
})

@aayushmau5 lgtm 🚀 I guess I can merge, right?

Yes! 🚀

/rtm


Mesh() incorrectly plotted in LIvePlot

User performed mesh(sx,9,11,20,sy-.8,.8,24) but LivePlot began plotting collected data starting with sx = 11, not 9. sy plotted as expected (starting at -0.8). Confirmed in the database that sx started at 9 and sy started at -0.8.
I have screen captures if you need to see.

@tacaswell per your request, I checked and this is still not plotting as expected.  I sent an email with a screen capture to better illustrate.

FYI, you can also drag-and-drop or copy/paste images into github comments.

In [220]: RE(mesh(theta,-0.05,0.05,2,delta,-0.1,0.1,2))
Transient Scan ID: 72529 @ 2016/12/16 13:14:21
Persistent Unique Scan ID: '06b16462-aaab-4d92-ba69-9f08d60ee095'
+-----------+------------+------------+---------------------+------------+---------------------+------------+
|   seq_num |       time |      theta | theta_user_setpoint |      delta | delta_user_setpoint |   sclr_ch2 |
+-----------+------------+------------+---------------------+------------+---------------------+------------+
|         1 | 13:14:28.1 |    -0.0500 |             -0.0500 |    -0.1000 |             -0.1000 |         98 |
|         2 | 13:14:33.7 |    -0.0500 |             -0.0500 |     0.1000 |              0.1000 |        100 |
|         3 | 13:14:39.6 |     0.0500 |              0.0500 |    -0.1000 |             -0.1000 |         99 |
|         4 | 13:14:45.2 |     0.0500 |              0.0500 |     0.1000 |              0.1000 |        101 |
+-----------+------------+------------+---------------------+------------+---------------------+------------+
generator mesh ['06b164'] (scan num: 72529)
Out[220]: ['06b16462-aaab-4d92-ba69-9f08d60ee095']
first point of mesh plot should be (-0.1, -0.5) not (-0.1,0.5).
@wen-hu


Does this calendar support viewing the calendar in Day, Week and Year view?

Not an issue but does JTAppleCalendar support viewing the calendar Day, Week, and Year views? I think I know how to recreate the week view (https://github.com/patchthecode/JTAppleCalendar/issues/581) but how would I go about recreating the year and day view?

Alright thank you! Do you think you'll ever support it?

the thing is li'll have to change some things.
I tried it before, but what happened was it lagged a lot because too many cells on screen.
i'll have to think of somethings.

I'm thinking of giving it a go: according to this stack overflow answer (https://stackoverflow.com/questions/44285708/improve-collectionview-loading-speed) it can be done. I'll report as soon as I can, but I don't have much time in med school.

Yea i saw that one.
But if you notice, the yearview does not have much configuration on the cell.
All it has a is a simple label and selection color. The cell is not fancy.
But with my lib, a user is able to configure the cell to what ever he wants.
Once users begin creating more complex cell designs for the year view, i assume it will again be slow.
I i was thinking of creating a you module for this.

Tracking it here
https://github.com/patchthecode/JTAppleCalendar/issues/349
YearView will be implemented


prisma2 dev: Ctrl+C doesn't stop the script in the terminal while generating Photon.js Client, Nexus, etc..

Basically the title while doing prisma2 dev :)

I am able to reproduce this

As we removed the prisma2 dev command, I'm closing this.


background is rectangle

background of AnimatedCircularProgress is rectangle ? can it style to circle ? I want to fill background with color , but it is rectangle and I just want a circle background
can you help me ? what can i do with this
thanks

@Nasirilahi Could you attach the code you have for the component or a screenshot? + are you testing on android or ios?
On 1 Feb 2018 17:33, Nasir Husain<EMAIL_ADDRESS>wrote:
@dancherbhttps://github.com/dancherb i tried your way but it didn't work for me?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/bgryszko/react-native-circular-progress/issues/110#issuecomment-362302309, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AeyOOZXQt9yiQgRJA_srk2uHB7MQluZWks5tQdk3gaJpZM4RXOuF.

Since the merging of #83 the background should be circular by default. If somebody is able to validate that would be great.

Closing for inactivity. Please re-open if this issue is not resolved.


Added check for "position" property during entity build phase

Qodot currently expects every entity to have a Vector3 "position" property, which can cause errors and crashes if an entity does not inherit from Node3D.
This change performs a check to make sure the property exists before attempting to apply it. During the solid entity build, this change also checks to make sure the "position" is a Vector3 and default the entity_position at line 721 to Vector3.ZERO, to avoid any brush building issues.
The Vector3 check is intentionally omitted for the point entity building as it might actually be useful for some more clever developers to take advantage of building 2D entities in their maps (ex: custom SubViewport camera feed systems; special overlays; etc...).
Adding the check and allowing entities to be built without "position" will also allow for non-positional nodes such as AudioStreamPlayers and CanvasLayers.

Thank you!


Failed to prune sessions: read ECONNRESET

Hi,
I tried to install MongoDB instead PG.
I've this warning after NestJS logs:

Failed to prune sessions: read ECONNRESET

I don't know why...

Will you use TypeORM or Mongoose?
If you are trying to change typeorm you must take into account that the user session middleware is coupled to postgresql specifically the connect-pg-simple package you should look for a similar middleware in mongo, you can also have both databases mounted, without replacing the models of user and use another connection or other ORM for information only.
in the main file you can see that middleware

  // production ready session store
  const pgSession = require('connect-pg-simple')(session);
  server.use(session({
    secret: process.env.SESSION_SECRET as string,
    store: new pgSession({
      conString: `postgres://${process.env.DB_USERNAME}:${process.env.DB_PASSWORD}@${process.env.DB_HOST}:${process.env.DB_PORT}/${process.env.DB_DATABASE}`,
      crear_interval: 60 * 60 // sec
    }),
    resave: false,
    saveUninitialized: false,
    rolling: true,
    cookie: {
      httpOnly: false,
      maxAge: 60 * 60 * 1000 // msec
    }
  }));

I updated some codes today 👍
@pirmax
Still the error happen?

ARK is an example of PostgreSQL, so I closed this issue.


Config not applied

My manifest is very simple and straightforward like this:
class { 'grafana':
  cfg => {
    app_mode => 'production',
  },
}

While grafana is installed with mainfest, the config remains untouched and looks like this:
sebastian@host:~$ sudo cat /etc/grafana/grafana.ini
# This file is managed by Puppet, any changes will be overwritten

sebastian@host:~$

Happens also, if the cfg is more complex and includes non-default values.
Environment:
sebastian@host:~$ lsb_release -d
Description:	Ubuntu 14.04.3 LTS
sebastian@host:~$ puppet --version
3.8.3

puppet-grafana definitely touches this file. Changes done to this file via other mechanisms are nulled, once the grafana class is executed.

Grafana related debug output from a puppet run:
Debug: importing '/etc/puppet/modules/srvgrf/manifests/grafana.pp' in environment production
Debug: importing '/etc/puppet/modules/grafana/manifests/init.pp' in environment production
Debug: Automatically imported grafana from grafana into production
Debug: importing '/etc/puppet/modules/grafana/manifests/params.pp' in environment production
Debug: Automatically imported grafana::params from grafana/params into production
Debug: hiera(): Looking up grafana::archive_source in YAML backend
Debug: hiera(): Looking up grafana::cfg_location in YAML backend
Debug: hiera(): Looking up grafana::cfg in YAML backend
Debug: hiera(): Looking up grafana::ldap_cfg in YAML backend
Debug: hiera(): Looking up grafana::container_cfg in YAML backend
Debug: hiera(): Looking up grafana::container_params in YAML backend
Debug: hiera(): Looking up grafana::data_dir in YAML backend
Debug: hiera(): Looking up grafana::install_dir in YAML backend
Debug: hiera(): Looking up grafana::install_method in YAML backend
Debug: hiera(): Looking up grafana::manage_package_repo in YAML backend
Debug: hiera(): Looking up grafana::package_name in YAML backend
Debug: hiera(): Looking up grafana::package_source in YAML backend
Debug: hiera(): Looking up grafana::service_name in YAML backend
Debug: hiera(): Looking up grafana::version in YAML backend
Debug: importing '/etc/puppet/modules/grafana/manifests/install.pp' in environment production
Debug: Automatically imported grafana::install from grafana/install into production
Debug: importing '/etc/puppet/modules/grafana/manifests/config.pp' in environment production
Debug: Automatically imported grafana::config from grafana/config into production
Debug: Scope(Class[Grafana::Config]): Retrieving template grafana/config.ini.erb
Debug: template[/etc/puppet/modules/grafana/templates/config.ini.erb]: Bound template variables     for /etc/puppet/modules/grafana/templates/config.ini.erb in 0.00 seconds
Debug: template[/etc/puppet/modules/grafana/templates/config.ini.erb]: Interpolated template     /etc/puppet/modules/grafana/templates/config.ini.erb in 0.00 seconds
Debug: importing '/etc/puppet/modules/grafana/manifests/service.pp' in environment production
Debug: Automatically imported grafana::service from grafana/service into production
Debug: Adding relationship from Class[Grafana::Install] to Class[Grafana::Config] with 'before'
Debug: Adding relationship from Class[Grafana::Config] to Class[Grafana::Service] with 'notify'
Debug: /Package[grafana]: Provider dpkg does not support features virtual_packages; not managing     attribute allow_virtual
Debug: /Stage[main]/Grafana::Install/before: requires Class[Grafana::Config]
Debug: /Stage[main]/Grafana::Install/Package[grafana]/require: requires Wget::Fetch[grafana]
Debug: /Stage[main]/Grafana::Install/Package[grafana]/require: requires Package[libfontconfig1]
Debug: /Stage[main]/Grafana::Config/notify: subscribes to Class[Grafana::Service]
Debug: /Stage[main]/Srvgrf/File[/etc/apache2/sites-enabled/grafana.conf]/require: requires     Package[apache2]
Debug: /Stage[main]/Srvgrf/File[/etc/apache2/sites-enabled/grafana.conf]/notify: subscribes to     Service[apache2]
Debug: /Stage[main]/Grafana::Install/Wget::Fetch[grafana]/Exec[wget-grafana]/require: requires     Class[Wget]
Debug: Exec[wget-grafana](provider=posix): Executing check 'test -s '/tmp/grafana.deb''
Debug: Executing 'test -s '/tmp/grafana.deb''
Debug: Service[grafana-server](provider=upstart): Could not find grafana-server.conf in /etc/init
Debug: Service[grafana-server](provider=upstart): Could not find grafana-server.conf in /etc/init.d
Debug: Service[grafana-server](provider=upstart): Could not find grafana-server in /etc/init
Debug: Executing '/etc/init.d/grafana-server status'

Any way how I can help you to debug this further?

Seeing a similar thing on Ubuntu 12.04 with release v2.0.1 of the module where some items appear to be put under sub-sections they don't belong to.
    cfg => {
      app_mode => $::app_tier,
      'auth.ldap' => {
        enabled     => 'true',
        config_file => '/etc/grafana/ldap.toml',
      },
      paths => {
        logs => $log_file,
      },
      security => {
        admin_user     => 'admin',
        admin_password => $admin_password,
      }
      server   => {
        http_addr => 'localhost',
        http_port => $http_port,
      },
      users => {
        allow_sign_up => false,
      },
    },

app_mode ends up under [server] for some reason:

[auth.ldap]
config_file = /etc/grafana/ldap.toml
enabled = true

[server]
http_port = 8080
http_addr = localhost
app_mode = staging

[paths]
logs = /var/log/grafana

[users]
allow_sign_up = false```

I'm wondering if the config value app_mode is no longer used?  I don't see it in the documentation http://docs.grafana.org/v2.1/installation/configuration/

Updating to commit ID e52afa8c43ca101ea8f325aa67404d2cc958e351 fixed this for me.

Hi @nohn thanks for the report. Can you confirm if using a version that includes this commit resolves the issue for you?


notification failed : ReferenceError: identifier 'CurlHttpRequest' undefined

I just imported the file from github but when I tested i got this error.
notification failed : ReferenceError: identifier 'CurlHttpRequest' undefined

Hi, apologies for the late response.
Did you get this sorted or do you still need support to get this fixed?
Regards, Mark


Don't use the faucet address as validator reward address

In the current ZQ2 test networks, the bootstrap is a validator and it uses the faucet address as reward address. We should change it to use a "neutral" address like all other validators do.

Why? Not against doing this, just curious.

My first thought was because it makes harder to check the correctness of the rewards earned by the validator, if they are not sent to a separate account.
On a second thought, I'd start using the null address as reward address for the bootstrap because that is exactly what we will need for the guard nodes we will run with a deposit borrowed from the null address on mainnet i.e. they should not earn rewards.


Buffer size of zero does not work

We're using Que with jobs that take a really long time to complete (hours), and would like to set up Que so that each worker process does not lock more than the one job that it's currently processes.
When we set minimum_buffer_size and manimum_buffer_size to zero, the workers do not pick any jobs at all. When we set the buffer size to one, the workers start picking up jobs but then they also pick and lock the next job.
Is there any way to configure Que not to lock any jobs beside the one it is currently processing?

I just pushed a minor fix to master so that --minimum_buffer_size 0 --maximum_buffer_size 0 should still pick up enough jobs to satisfy the workers - try it out and let me know if that solves your problem.
(Also master has started failing sometime in the last 10 months, looks like it's due to changes in Rails. I may or may not find time to fix that soon.)

Opened issue #236, I'm going to close this one. Thanks for the report!


Added lat and lng to the vendor structure.

These are fields described in the documentation but not exposed to the Golang API.

Thanks for contributing! Merging it!


Documenting extern dec conflicts with autoformatting rules

In order for decorators to be documented in our generated docs, we have to put doc comments on the extern dec statements. However, some kind of auto-formatting rule relocates these doc comments anytime you save so that ALL the doc comments are put above the first extern dec statement.

This doesn't make sense to me, but if the docs can figure it out then okay, whatevs. However, it looks like our ref doc generation does NOT figure it out, giving nonsense output:

Yikes, this is bad. I will tak a look right away.

Are those declarations inside a blockful namespace Foo { ... } rather than under blockess namespace Foo;. That's the repo I see right now. I happened upon it quickly because I noticed this weirdness in comments on extern decs in .Private namespace last week but thought somebody manually moved them up because they didn't want to document the .Private stuff.

Yeah, it's a block because there's Azure.Core, Azure.Core.Foundations and Azure.Core.Foundations.Private. I could put them in separate files if that's a suitable workaround.

It's a reasonable workaround, but I'd like to get this fixed. So far, I am not succeeding though.

Another workaround seems to be not using . in namespace but explicitly declaring hierarchy like this:
namespace Azure {
  namespace Core {
     /** ... */
     extern dec a();
     /** ... */
     extern dec b();

     namespace Foundations {
       /**... */
       extern dec c();
     }
   }
 }

This one might be better in that you don't have to change the number of files involved when you revert the workaround after a fix.
Something about the way we represent those dots is making prettier's life miserable. The way we represent the AST is a little special in that case and I'm not entirely surprised that prettier is confused. There are some overrides in comment-handler.ts, but in this case, it seems the info we need to fix things up is lost so I might need to change the AST. :(

Thanks @nguerrera I'll go with the second to confine the decorator definitions to one file.

OK removing my assignment and putting back onto "needs triage" pile since there is a workaround at least. This still seems pretty severe though.

It impacts more than extern dec and doc comments, basically all comments inside namespace X.Y { ... } are vulnerable.
Here's a repor with only regular comments and model statements:
https://cadlplayground.z22.web.core.windows.net/?c=bmFtZXNwYWNlIFguWSB7DQogIG1vZGVsIE0ge30NCsQQLy8gQW5vdGhlcsYbyiRaxSR9DQo%3D
Hit alt+shift+F to format in playground.

est: 8 (timebox)

Hotfixed in 0.45.1


This Month in Rust OSDev (July 2020)

This is a draft for the upcoming "This Month in Rust OSDev (July 2020)" post. Please add your content to this draft by creating pull requests against the next branch.

@rust-osdev/all It's the end of the month again, so it's time to create a new "This Month in Rust OSDev" post. I'll be handling the updates for the rust-osdev projects again, but please send pull requests with the changes of your personal projects.

@phil-opp I can hopefully get my PR to you sometime this evening. I've also made some pretty substantial changes to acpi this month, so I'm happy to write the section for that.

The draft for the upcoming August post is available in https://github.com/rust-osdev/homepage/pull/19.


[FLINK-13066][hive] append hive-site.xml to path of Hive conf dir

What is the purpose of the change
This PR fixes a bug that we previously only pass Hive conf dir to HiveConf but we really should pass path of hive-site.xml. Thus, the change is to append hive-site.xml to the Hive conf dir and pass into HiveConf if Hive conf dir is not null.
Brief change log

make hiveConfDir String rather than URL to simplify logic
append hive-site.xml to the Hive conf dir and pass into HiveConf if Hive conf dir is not null

Verifying this change

covered by existing test such as DependencyTest and ExecutionContextTest in sql cli
manual testing and verificaiton

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

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

Documentation

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

cc @xuefuz @lirui-apache @zjuwangg
@sunjincheng121 @dianfu can you take a look at the python API change?

@bowenli86 The Python API changes LGTM.


AngularSpacing

@awdigital
I was wondering how to interpret AngularSpacing property.
Obviously the angularSpacing is in degrees. Is it in relation to a full circle being 360 degrees or a full circle being 180 degrees.
i.e. Physical angle spacing = 2 * virtual angle spacing, where angularSpacing variable represents virtual spacing
If I have 3 items, and I want them to be evenly divided in the full circle, should angularSpacing be 360/3 or 180/3?

Hi,
Correct. basically the angular spacing is 360° divided by the number of items in the circle.


ui fails to build

@zeyap getting this error below:
$ npm start

><EMAIL_ADDRESS>start /home/ralford/development/ui-mockup
> node run

Starting 'start'...
Starting 'clean'...
Finished 'clean' after 4ms
webpack built ea6fa60a69a451e0642c in 3397ms
Time: 3397ms

ERROR in ./components/TableView/StandardTableView.js
Module not found: Error: Cannot resolve 'file' or 'directory' ./pagination in /home/ralford/development/ui-mockup/components/TableView
 @ ./components/TableView/StandardTableView.js 41:18-41
webpack: Failed to compile.

It could be that I was using lowercase in specifying directory, but I did not have this issue. Is it resolved now?

It could be that I was using lowercase in specifying directory, but I did not have this issue. Is it resolved now?

Yes.  b5a0619 fixed it. Thanks!


Amazon.AWSCLI version 2.17.20

Checklist for Pull Requests

[ ] Have you signed the Contributor License Agreement?
[ ] Is there a linked Issue?

Manifests

[ ] Have you checked that there aren't other open pull requests for the same manifest update/change?
[ ] This PR only modifies one (1) manifest
[ ] Have you validated your manifest locally with winget validate --manifest <path>?
[ ] Have you tested your manifest locally with winget install --manifest <path>?
[ ] Does your manifest conform to the 1.6 schema?

Note: <path> is the directory's name containing the manifest you're submitting.

Microsoft Reviewers: Open in CodeFlow

Automatic Validation ended with:

2024-07-31T11:32:11.2750765Z Manifest Validation Failed
2024-07-31T11:32:16.2844783Z ##[error]Manifest Validation Failed

(Automated response - build 887.)

Close with reason: Merge Conflicts;


re-setting / clearing selected value does not work

Hi,
I'm struggling to find a solution to clear the selected value from treeselect.
Scenario:
I have a treeselect that uses v-model.
I want to "clear" the selection using a method not the x button but re-setting the v-model value to these: null or '' or undefined or [] does not work. The previously selected item is still displayed.
Is there a way to programmatically re-set or clear the treeselect?
(exmple usecase where the value is bound to vuex state and it changes).

Show your code via codesandbox.io or other service.

@qury Did you solve this after?

@qury Did you solve this after?

Yes.I have put a key on the component and increment it when i want to clear the values. This forces the component to re-render.
Maybe there us a better way, but this worked for me.


Building sfml using vcpkg, builds only debug libraries

Thanks to all the vcpkg team for coming up with this versatile tool. Recently I was able to build static libraries ( latest version of vcpkg ) for sfml using the following command:
.\vcpkg install sfml:x64-windows-static
It built only the debug  libraries and failed to build release libraries. Please advice as to what possibly might be the reason for this. BTW I used VC++2017 to build vcpkg itself, so any connection ?

@seccpur, thank you for posting the issue, does the issue still occur? could you try vcpkg latest revision?
PS F:\vcpkg\src> ./vcpkg version
Vcpkg package management program version 2018.11.23-nohash
It installed successfully with vcpkg latest version and vs 2017 15.9.7:
Starting package 7/7: sfml:x64-windows-static
Building package sfml[core]:x64-windows-static...
-- Downloading https://github.com/SFML/SFML/archive/2.5.1.tar.gz...
-- Extracting source F:/VCPKG/src/downloads/SFML-SFML-2.5.1.tar.gz
-- Applying patch use-system-freetype.patch
-- Using source at F:/VCPKG/src/buildtrees/sfml/src/2.5.1-8da8c5c259
-- Configuring x64-windows-static
-- Building x64-windows-static-dbg
-- Building x64-windows-static-rel
-- Installing: F:/VCPKG/src/packages/sfml_x64-windows-static/share/sfml/copyright
-- Performing post-build validation
-- Performing post-build validation done
Building package sfml[core]:x64-windows-static... done
Installing package sfml[core]:x64-windows-static...
Installing package sfml[core]:x64-windows-static... done
Elapsed time for package sfml:x64-windows-static: 1.394 min
Total elapsed time: 4.474 min
The package sfml:x64-windows-static provides CMake targets:
find_package(SFML CONFIG REQUIRED)
# Note: 7 target(s) were omitted.
target_link_libraries(main PRIVATE FLAC OpenAL OpenGL Vorbis)

@seccpur we cannot reproduce it now with the latest vcpkg. Please open a new issue if this is still a problem for you.


[🌟] Add support for Windows platform (React-Native-Windows)

Description
Package currently supports Android and iOS but not windows.
It would be great for those making cross platform apps.
Proposed Solution
Add windows platform as many others have done.
RNW repo: https://github.com/microsoft/react-native-windows
Example of a few projects supporting windows via RNW:
https://github.com/react-native-device-info/react-native-device-info
https://github.com/zoontek/react-native-localize
https://github.com/react-native-webview/react-native-webview/
https://github.com/react-native-video/react-native-video
What needs to be done to make it happen?
Implement the needed basic functions for windows (C++ WinRT)
Note: I've written a partial implementation for react-native-image-picker for our internal usage and there will be some trickiness around StorageFiles on Windows and how UWP work with an image picker, and will need coordinate with the react-native-filesystem likely as well. I can elaborate on this further if requested, or feel to reach out via Discord namrog84#0880 (also I'm in the React Native Contributors discord if you want to @ me in the RN-image-picker channel to discuss publicly.
I will try and find some time in the next 3-6 months to see if I can get our internal usage improved upon and into a PR into this repo, but would love if someone else could/would tackle it. I'd be glad to help however.
Test Solution
How would we test & validate the feature?
Add windows support to the example project already in this repo.
e.g. see react-native-device-info repo for adding windows support to an example ap.
https://github.com/react-native-device-info/react-native-device-info/tree/master/example/windows

Windows isn't a thing on mobile, but windows is still a thing on PC Desktop.  React-Native-Windows has been gaining a lot of momentum and coverage by many packages.

Sure, re-opened :) If your team has a partial implementation, do you want to open a draft PR?

I can and will

Cool! Thanks :)

I can and will

@namrog84 Hey, I was wondering if you've created a PR yet?

Hey! the feature request was relevant to a project and team that I am no longer on. I've moved industries and don't do react or typescript related work anymore. So I don't know the ongoing needs of it anymore.
I still think its a worthwhile feature that people would benefit from though.

Hi @namrog84
Were you able to finalize customizing the react-native-image-picker for windows support? Or is it still in progress?

A year later, any news on this ? :)


error after publishing connectthedots

Hello,
Am getting the following error after publishing this website in azure.  Kindly help me to proceed further.

Thank you!

What's the name of your EventHub ?

ehdevices & ehalerts

Hello Rob, I found my mistake in web.config file.

changed to

Thank you!

Glad you solved it :)


refacto package build/ publish

Signed-off-by: fahed dorgaa<EMAIL_ADDRESS>
Description of your changes

Fixes #

Use bundled provider packages
Switch to UP cmd when building provider package
Support publish to xpkg.upbound.io

I have:

[x] Read and followed Crossplane's contribution process.
[x] Run make reviewable to ensure this PR is ready for review.
[ ] Added backport release-x.y labels to auto-backport this PR if necessary.

How has this code been tested

@hasheddan I added a new commit to fix module path https://github.com/crossplane-contrib/provider-ansible/pull/116/commits/d5f557d1c1ad23e26673701e11d634ad9eadce44


Braintree JS SDK in sandbox iframe

Originally posted by @jart in https://github.com/braintree/braintree_java/issues/35

Forgive me if this is not the proper place to file this bug.

If I try to embed the 'dropin' Braintree JS SDK v2 in an iframe with the HTML5 sandbox attribute (for bidirectional security), then the browser will raise an error saying that the script is accessing document.cookie to write a value named 'venmo' or something. Even though I'm not using Venmo.

A workaround exists, which is to host the iframe on a separate domain, so cross-origin browser security policies kick in. But it would simplify production systems management if the braintree iframe were able to be hosted inside a sandbox.

@jart We do not support using Drop-in with sandboxed iframes. Although, currently it looks like using allow-scripts allow-same-origin allows Drop-in to work in a sandboxed iframe but we can’t guarantee it will in the future.

Using allow-scripts allow-same-origin disables the sandbox entirely.
Do you guys support drop-in within a cross-origin iframe? Because I was planning on using that in production. Having bidirectional security is kind of important for where this is being embedded.

Yes, we support Drop-in within a cross-origin iframe.


Add ArbitraryInRage to Amount

Leaving this in draft since it's not yet merged into Arbitrary.
Allows for creating Arbitrary Amount in range such as:
let a: Amount = Amount::arbitrary_in_range(u, &(minimal_non_dust..=effective_value_max)).unwrap();

This can also be used for building an Arbitrary Utxo pool such that any Arbitrary subset will not overflow u64 by setting the maximum bound.

Weak concept ACK. Weak because it's likely nowhere near as useful as Arbitrary.

Well that's true.  Luckily we can have both!

s/ArbitraryInRage/ArbitraryinRange/ lol


Bug: false alarm of the analyzer

There is a code snippet.
class Date extends DateTime {
  factory Date.from(DateTime other) {
    return ((other.isUtc) ? Date.utc : Date.new)(
      other.year,
      other.month,
      other.day,
    );
  }

  Date(super.year, [super.month, super.day]);
  Date.utc(super.year, [super.month, super.day]) : super.utc();

  Date copyWith({
    int? year,
    int? month,
    int? day,
    bool? isUtc,
  }) {
    // ignore: unnecessary_cast
    return (this as DateTime)
        .copyWith(
          year: year,
          month: month,
          day: day,
          isUtc: isUtc,
        ).clipTime;
    }
}

extension ClipTimeDateTime on DateTime {
  Date get clipTime => Date.from(this);
}

There are 2 copyWith:

extension DateTimeCopyWith on DateTime
Date.copyWith method.

Date.copyWith should use DateTime.copyWith. Analyzer alerts 'Unnecessary cast'. I remove (this as DateTime). Then there is a cycle dependency: Date.copyWith uses Date.copyWith:
  Date copyWith({
    int? year,
    int? month,
    int? day,
    bool? isUtc,
  }) {
    return copyWith(
          year: year,
          month: month,
          day: day,
          isUtc: isUtc,
        ).clipTime;
    }

It is wrong behaviour.
Also I can't use super.copyWith: The method 'copyWith' isn't defined in a superclass of 'Date'.
Desired behavior
Analyzer doesn't alert unnesessary_cast in this scenario.
General info

Dart 3.2.3 (stable) (Tue Dec 5 17:58:33 2023 +0000) on "macos_arm64"
on macos / Version 14.2.1 (Build 23C71)
locale is ru-RU

Project info

sdk constraint: '>=3.0.2 <4.0.0'
dependencies: auto_route, badges, bloc, bloc_concurrency, carousel_slider, collection, cupertino_icons, dartx, decimal, dio, dotted_line, equatable, excel, expandable, fast_immutable_collections, firebase_core, firebase_crashlytics, firebase_messaging, flutter, flutter_bloc, flutter_local_notifications, flutter_localizations, flutter_slidable, flutter_svg, formz, freezed_annotation, gap, get_it, hexcolor, html_unescape, http, injectable, intl, json_annotation, logger, meta, package_info_plus, path_provider, pretty_dio_logger, provider, pull_down_button, retrofit, rxdart, share_plus, shared_preferences, slang, slang_flutter, sliver_tools, sprintf, syncfusion_flutter_pdf, table_calendar, theme_tailor_annotation, url_launcher, uuid, webview_flutter
dev_dependencies: auto_route_generator, build_runner, flutter_gen_runner, flutter_launcher_icons, flutter_lints, flutter_test, freezed, injectable_generator, json_serializable, melos, slang_build_runner, theme_tailor
elided dependencies: 5

Process info

Memory
CPU
Elapsed time
Command line

629 MB
0.0%
16:10
dart language-server --client-id=Android-Studio --client-version=AI-222.4459.24 --protocol=analyzer

60 MB
0.0%
16:11
flutter_tools.snapshot daemon

unnecessary_cast does indeed have false positives. However, in this particular situation you'd probably do the following anyway (which means that there is no cast, and hence no spurious messages from unnecessary_cast):
  Date copyWith({
    int? year,
    int? month,
    int? day,
    bool? isUtc,
  }) {
    return DateTimeCopyWith(this) // <-- Invoke the extension method explicitly.
        .copyWith(
          year: year,
          month: month,
          day: day,
          isUtc: isUtc,
        )
        .clipTime;
  }

The point is that you can guide the resolution of an extension member invocation by modifying the type of the receiver (e.g., using a cast), but if you just want to ensure that the invocation will call a specific extension member then you might as well perform the resolution manually. This will document the purpose much more directly, and it will force the resolution to choose the extension member that you want to invoke, even in the case where some of the conflicting declarations are modified ().

@ChaserVasya, I think I should close this issue because everything except possibly the unnecessary_cast lint is working as intended. I don't see the lint issue locally (though I haven't tried to debug that), but it would be great if you can create a concise example and report it on the linter repository.


cpackget returns with error state on already installed packs

Describe the bug
cpackget returns with error state when asked to install a pack that is already installed. This leads to CI pipelines to fail.
To Reproduce
Steps to reproduce the behavior:

cpackget -R .packs init https://keil.com/pack/index.pidx
cpackget -R .packs pack add ARM.CMSIS install the pack:I: Using pack root: ".packs"
I: Downloading ARM.CMSIS.pdsc 100% |█████████████████████████████████| (238/238 kB, 338.772 kB/s)
I: Adding pack "ARM.CMSIS.5.8.0"
I: Downloading ARM.CMSIS.5.8.0.pack 100% |██████████████████████████████| (34/34 MB, 30.838 MB/s)
I: Extracting files to .packs\ARM\CMSIS\5.8.0 100% |█████████████████████| (8133/8133, 207 it/s)

cpackget -R .packs pack add ARM.CMSIS recognizes pack is already installed
See error:I: Using pack root: ".packs"
I: Adding pack "ARM.CMSIS.5.8.0"
E: pack ARM.CMSIS.5.8.0 is already installed here: .packs\ARM\CMSIS\5.8.0

Expected behavior
Reinstalling an already installed pack should not be treated as an error. In the first place it may be a no-op with just info (or at max warning) message. In the second place their might be situations where a user wants to force reinstall a pack. While this can already be achieved by removing and install the pack in two steps, a --force flag for the add command may be convenient. Today, the add -f flag conflicts with the usual abbreviation for --force.
Environment (please complete the following information):

OS: Windows
Version: 2020H2

Additional context
Add any other context about the problem here.

Thanks for raising this @JonatanAntoni !
I have changed it so that the error message becomes an info message e.g. `` the PR #59 addresses that.
I'll address the second part of your issue on another PR. What do you think of --force-reinstall? pip[1] uses that option for exactly the same purpose as you described
[1] https://pip.pypa.io/en/stable/cli/pip_install/?highlight=reinstall#cmdoption-force-reinstall

Yes, doing this similar to other package managers seems like a good idea.


Account for possible concurrent topic creation in PubSub topic auto-c…

…reate functionality.
https://github.com/spring-cloud/spring-cloud-gcp/issues/2410

@mvmn Please sign the Contributor License Agreement!
Click here to manually synchronize the status of this Pull Request.
See the FAQ for frequently asked questions.

@mvmn Thank you for signing the Contributor License Agreement!

Thank you @elefeint.
I've added log warning and a unit test, please re-check if it's ok.
Thanks!

Wait, apparently there are checkstyle errors now - let me fix that first...

I can see the warning message in build log - which means unit test has worked and the code in catch clause was called.
Not sure why codecov is reporting a 7% drop in coverage here...

Codecov is showing a decrease because the baseline includes integration tests; this is not a concern.
The warning label was because I asked for it; we can definitely downgrade to INFO. I was thinking it could be useful in production to notice it (and production typically does not show below WARN) and realize that a permanent, non-auto-created, topic would be a better solution where multiple load-balanced publishers exist.

All points addressed, please re-review.


Detect & attach application_protocol = http to appropriate ports from transpiled Compose

Background & motivation
Right now, transpiled Compose files don't get any application_protocol which makes them unclickable & unviewable in the frontend.
Desired behaviour
Transpilation autodetects web ports and attaches application_protocol = http to them. Maybe by doing it for any port that's 80, 8080, or 8000?
How important is this to you?
Critical; Kurtosis is unusable for me without it.
What area of the product does this pertain to?
Other: anything not covered by the above

Addressed by: https://github.com/kurtosis-tech/kurtosis/pull/2281


Add a plain/text highlighter that does not highlight.

This may sound weird at first, but I consider it actually really useful. There are a lot of projects using highlight.js (even some markdown apps on OS X) but there seems to be no way to have a code block unhighlighted. Customizing the css to achieve this, is some of the cases is not easily possible. So I would love to see a text  or plaintext highlighter that does not highlight at all.

Ok, no-highlight did the trick… (Maybe text should be added as an alias for it)
The only problem I have now is that the theme broke, because the code has no hljs class anymore, but that's not really a highlight.js issue.

Maybe text should be added as an alias for it

Already done in e278472b8.
BTW, to my personal liking the best way to have unhighlighted piece of computer output is to mark it up as
<output>..</output>
.

:+1: Thanks, I wasn't aware that there is an <output> html tag!

On the level of semantic the use of <output> at this point is not correct. It's defined as the output of a calculation.

It seems <samp> would be the right thing to use in this case.


Unable to delete project board

Description
The delete button on project boards does nothing.
Notice: I couldn't try this on the public instance since I can't log in. I am assuming YES
Gitea Version
Gitea version 1.17.0 built with GNU Make 4.1, go1.18.4 : bindata, sqlite, sqlite_unlock_notify
Can you reproduce the bug on the Gitea demo site?
Yes
Log Gist
Could not for the life of me get gitea to output logs even though I am basically on the stock config
Screenshots
No response
Git Version
git version 2.34.1
Operating System
Linux selfhosted 5.15.0-1013-raspi #15-Ubuntu SMP PREEMPT Mon Aug 8 06:33:06 UTC 2022 aarch64 aarch64 aarch64 GNU/Linux
How are you running Gitea?
Service from the deb file.
Database
MySQL

Does work for me on https://try.gitea.io when I create a empty project and then delete it afterwards. Maybe there's more conditions? There should be an error in the server log or possibly in the browser console, try to check those.

Does work for me on https://try.gitea.io when I create a empty project and then delete it afterwards. Maybe there's more conditions for the problem to appear? There should be an error in the server log or possibly in the browser console, try to check those.

As I said, I couldn't get gitea to actually start logging anything and the server console didn't show any errors either.

Does it work when you create a empty project and then immediately delete it?

Does it work when you create a empty project and then immediately delete it?

It doesn't no. I can't delete any boards.

I think what silverwind meant is to also check whether there are error logs in your browser's console.
There could be some different issues behind the problem:

The frontend resources are out-of-sync. Upgrade to 1.17.2 will 99.9% resolve the problem.
The are some out-of-sync customized templates or customized static CDN.
There are some permission problem (bug), try with admin account.
If there are other issues, then it needs more logs to continue, see https://docs.gitea.io/en-us/seek-help/

I have already checked the browser console, but it didn't contain any errors

I sure hope that this is the fix
no clue what you are talking about, so probably not. I am pretty much using stock gitea with nginx
Well I only have one account on my gitea instance, so I assume that my account is the admin account
logging for some reason didn't work and the service logs didn't contain any errors

logging for some reason didn't work

That's impossible. Follow the document https://docs.gitea.io/en-us/seek-help/, the logging should always work.
And, "check what HTTP requests are sent to backend when clicking Delete Board", what do you see?

logging for some reason didn't work

That's impossible. Follow the document https://docs.gitea.io/en-us/seek-help/, the logging should always work.
And, "check what HTTP requests are sent to backend when clicking Delete Board", what do you see?

Just checked, a DELETE request gets sent (0b tho? Is that correct?)

Can you show details? For example, what's the response of the 0b DELETE? Do you see the {"ok":true} response?
Even if you thought "Logging yielded no results at all. Just debug prints", it will also help, do you see the DELETE request on the backend? If no, are you using a reverse-proxy? Is it blocking some request? etc.
Please provide enough clues and logs. If you can not follow https://docs.gitea.io/en-us/seek-help/ to provide enough information, it will waste a lot of time on asking and answering.

Can you show details? For example, what's the response of the 0b DELETE? Do you see the {"ok":true} response?
Even if you thought "Logging yielded no results at all. Just debug prints", it will also help, do you see the DELETE request on the backend? If no, are you using a reverse-proxy? Is it blocking some request? etc.
Please provide enough clues and logs. If you can not follow https://docs.gitea.io/en-us/seek-help/ to provide enough information, it will waste a lot of time on asking and answering.

I am using nginx. The debug prints that did exist never mentioned "DELETE". It is not blocking other stuff in gitea. I did not see an OK response.
Here are the logs, but as I said, I didn't see anything:
xorm.log
router.log
gitea.log

certbot apparently added a check which I didn't know about. It filtered some request types like delete


fix: leader election should use different key with each application

ref: https://github.com/cectc/dbpack/issues/
Ⅰ. Describe what this PR did
Ⅱ. Does this pull request fix one issue?
Ⅲ. Why don't you add test cases (unit test/integration test)?
Ⅳ. Describe how to verify it
Ⅴ. Special notes for reviews

Codecov Report

Merging #130 (c25edee) into dev (a0a5bda) will not change coverage.
The diff coverage is n/a.

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

@@           Coverage Diff           @@
##              dev     #130   +/-   ##
=======================================
  Coverage   45.83%   45.83%
=======================================
  Files          62       62
  Lines        6351     6351
=======================================
  Hits         2911     2911
  Misses       3167     3167
  Partials      273      273

Continue to review full report at Codecov.

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

LGTM

LGTM


Add Google Cloud Storage

https://github.com/googleapis/google-cloud-go/tree/main/storage

Anybody working on this?

https://github.com/huacnlee/gobackup/releases/tag/v1.2.0


Add test case for SoulLogo and clear up the test directory structure.

// Describe your PR here; eg. Fixes #issueNo
Fixes #870

Make sure that:

[ x] You have read the contribution guidelines.
[ x] You submit test cases (unit or integration tests) that back your changes.
[ x] Your local test passed mvn clean install -Dmaven.javadoc.skip=true.

Codecov Report

Merging #892 (d3b015f) into master (d3242e3) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master     #892   +/-   ##
=========================================
  Coverage     72.25%   72.25%
- Complexity     1743     1745    +2
=========================================
  Files           303      303
  Lines          6877     6877
  Branches        782      782
=========================================
  Hits           4969     4969
  Misses         1508     1508
  Partials        400      400

Continue to review full report at Codecov.

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

I'm a little confused. What's the point of testing this?

Actually, I'm a little confused, too.


Update framework for e-links with multiple branches

Add support for e-link types that have multiple branches to automated 4-point DC resistance and eye-bert area framework (including template analysis).
python files to update:
https://github.com/ku-cms/eLink_Instrumentation/blob/main/EyeBERT/EyeBertAutomationDev.py
https://github.com/ku-cms/eLink_Instrumentation/blob/main/EyeBERT/template_analysis_windows.py
Requirements:

The user should enter the e-link type.
The user should enter the e-link branch.
The framework should select the correct channel mapping based on the e-link type and branch.
The framework should save the e-link branch and channel information in the data spreadsheets.
The framework should save unique output files based on the e-link branch and channel.

Addressed in this PR: https://github.com/ku-cms/eLink_Instrumentation/pull/51


Implement NudgeCommand.cs

Should we have a notification pop up that says the user was nudged? Old Jabbr does not do that.


Safety beginnings ppm

added in ppm driver
added in interchip code (no clue whether this will work, but the code looks promising)

Merging this without deep review. I'll put it under test right away (at least the ppm/pwm stuff) If it checks out, we can move on to thinking about merging into devel.


Port to new GCP Project

@steveoh would like this function moved to a new GCP project. We need to:

[x] Deploy it to a new GCP project
[x] Register a new DNS for this project and point it to the new project
[x] Reach out to users and ask them to switch to the new DNS
[ ] Retire the old project once users have switched.

/remind me to reach out to users in two weeks

We need to migrate this to it's own project so you might want to wait until the new dns is up to reach out?

Email has been sent out to users asking them to update by Sept 1st.

/remind me to check the usage logs for the old service on September 8.

Looks like we have a couple of accounts still making requests. One is summit county; I've sent them another email about it. The other is the account created for parcels.utah.gov. I'm seeing a fair amount of requests. However, I confirmed that I switched that app to the new URL weeks ago. @steveoh Any ideas on why we are still seeing requests for it?

Not a clue, any chance you can check the referrer header to see where it is originating?

I'm not logging the referrer explicitly and I couldn't find anywhere else to look. I may just have to shut it off and see who complains. I searched GitHub again to make sure that I got all of the old DNS entries.

How easily could we add a log statement for the request headers and a source ip? I'm curious now how the parcel url is being used if the app was updated...

I'll give it a try...

I added the referer and source ip to the logs. I'll check again in a few hours...

I don't understand this, unless parcels.utah.gov is not updating on someone's computer...

OK. The lone hold out is the summit county parcel viewer. I called Jeff from Summit county this morning and asked him if he got my emails. He said that he hasn't been into work all week before a tree fell on his house. 😬 I told him not to worry about it until he comes back to work. He said maybe next week. I'm just going to let it be for now.

Summit county has switched to the new DNS. Jeff sent me an email this afternoon and I verified. BUT...I looked through the logs for today and found another app hitting the old service:

That's probably a bad app to break. I'll reach out to SLCo...

The SLCo app has been switched to the new DNS. Now, I'm seeing WRI requests and found out that my merge request was never acted upon: https://git.dts.utah.gov/sixthfloor-east/wri/-/merge_requests/63
I @-mentioned Casey on it. Hopefully, something happens soon on that one. Is this one of those times that I'm expecting someone to be as on top of things as Steve and I'm just disappointed?

I'll get it moved through. I didn't realize it was in gitlab waiting.

I've deleted the old service. There's no way to shut them down. Hopefully, we are OK. I checked the logs, there are still requests coming from parcels.utah.gov and a few others but I've emailed the owners several times. There's only so much that we can do.


Need a logo for the project

I was thinking in creating something that mixes old-fashioned, vintage, old west characters with futuristic characters, or something like that, maybe

I just created a temporary logo

created a logo for the organization TeixeiraSoftware instead.


Godot 4: adding a property set in Visual Script results in getting a property get instead

Godot version
v4.0.alpha2.official [79077e6c1]
System information
Windows 11, Vulkan Clustered, Intel UHD Graphics 620 v<IP_ADDRESS>0
Issue description
I add a property set but get a property get instead, as shown in the screen recording below:
https://user-images.githubusercontent.com/1403194/153989626-21ccfdd2-c23c-4b47-a7c3-ac214a5e4cd6.mp4
I expect to get the correct node.
Steps to reproduce

Add a property set in Visual Script. You will get a property get instead.

Minimal reproduction project
No response

For an unknown reason to me, you have to press CRTL to get the setter.
It is design this way in the source code.
Looks strange to me but I won't attempt any change before knowning why this is the case.

For an unknown reason to me, you have to press CRTL (while confirming) to get the setter. It is design this way in the source code. Looks strange to me but I won't attempt any change before knowing why this is the case.
https://github.com/godotengine/godot/blob/98b97d34df7f3ab2cafc3847358c231c3d357b40/modules/visual_script/editor/visual_script_editor.cpp#L3397-L3421

When dragging a variable from the members' window to the Visual Script canvas, you will get a PropertyGet node, but if you hold down CTRL, you will get a PropertySet node. It has been like this since Godot 3 (I've never used Godot 2), except that you would get a VariableGet or a VariableSet node in Godot 3 instead of a PropertyGet or a PropertySet node (VariableGet and VariableSet are deprecated - #54663 merged PR).
But in this case, the menu tells the users exactly what node they would've got, as shown in the screenshot below:
PropertyGet:

PropertySet

I understand the confusion.
I think you are looking for visual script nodes. Get, Set and Set_variable, Get_variable
The VisualScriptProperty... class you look for is what describes how the visual script nodes work. that class has a variable/property called ' property' which you may try to set or get from an instance.
@kreaninw thanks for your feedback. I implemented this search system to make sure everyone may find everything they need. I hope it is an overall improvement to 3.4. Do you understand the difference? Do you have any idea how to improve the search so this may be avoided in the future?

I understand the differences compared to 3.4. However, I don't think this is an improvement. Now the users need a lot more steps, from changing this search filter box to "Search All" to search for some very essential nodes that they use all the time, then most of the time they'll also need to enable the class searching that's disabled by default.
I don't think the current search filter box will make anyone coding in Visual Script faster since it adds more steps to get things done. If the goal is to reduce some unrelated nodes from the search result, I think this filter bar would be enough:

https://github.com/godotengine/godot-proposals/discussions/4126

While working on a PR to improve this annoyance I noticed filtering the Show Hierarchy button puts visual script nodes on top.


ERR: Not an editor command: Runcode

What's that?

I have to say I don't understand why the author provides key mappings with "RunCode" command but do not provide cmd option. Maybe because I'm new to nvim, but this is really messing up with me. I finally got it fixed by adding a line like cmd="RunCode", and put this in your plugins folder should get it done:
return {
  "CRAG666/code_runner.nvim",
  cmd = "RunCode",
  config = function()
    require("code_runner").setup {
      filetype = {
        java = {
          "cd $dir &&",
          "javac $fileName &&",
          "java $fileNameWithoutExt",
        },
        python = "python3 -u",
        typescript = "deno run",
        javascript = "node",
        rust = {
          "cd $dir &&",
          "rustc $fileName &&",
          "$dir/$fileNameWithoutExt",
        },
        c = function(...)
          c_base = {
            "cd $dir &&",
            "gcc $fileName -o",
            "/tmp/$fileNameWithoutExt",
          }
          local c_exec = {
            "&& /tmp/$fileNameWithoutExt &&",
            "rm /tmp/$fileNameWithoutExt",
          }
          vim.ui.input({ prompt = "Add more args:" }, function(input)
            c_base[4] = input
            vim.print(vim.tbl_extend("force", c_base, c_exec))
            require("code_runner.commands").run_from_fn(vim.list_extend(c_base, c_exec))
          end)
        end,
      },
    }
  end,
}


Do some exploratory Piret runs with other data, experiment with tweaking config file settings

completed on intoxication transcriptomics dataset.


[MulticastDNS] Add new library

Description

This binding adds support for MulticastDNS to:

Listen for mDNS queries to resolve hostnames to an IP address (typically resolving a domain name to the IP address of the nF device)
Send mDNS messages to (for instance) discover other IoT devices on the local network

Motivation and Context

Fixes nanoFramework/Home#912

Allows to browse to nF devices without knowing their IP address
Allows discovery of other IoT devices on the same network to (for instance) allow P2P communication

How Has This Been Tested?

There is a sample included that functions flawlessly and covers end to end resolving domain to IP address.
Screenshots
Types of changes

[ ] Improvement (non-breaking change that improves a feature, code or algorithm)
[ ] Bug fix (non-breaking change which fixes an issue with code or algorithm)
[x] New feature (non-breaking change which adds functionality to code)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Config and build (change in the configuration and build system, has no impact on code or features)
[ ] Dependencies (update dependencies and changes associated, has no impact on code or features)
[ ] Unit Tests (add new Unit Test(s) or improved existing one(s), has no impact on code or features)
[ ] Documentation (changes or updates in the documentation, has no impact on code or features)

Checklist:

[x] My code follows the code style of this project (only if there are changes in source code).
[ ] My changes require an update to the documentation (there are changes that require the docs website to be updated).
[x] I have updated the documentation accordingly (the changes require an update on the docs in this repo).
[x] I have read the CONTRIBUTING document.
[x] I have tested everything locally and all new and existing tests passed (only if there are changes in source code).
[ ] I have added new tests to cover my changes.

Summary by CodeRabbit

New Features

Introduced a new category labeled protocol in the Multicast DNS classification.
Added versioning and dependency management with new packages.lock.json files in the main and samples directories.
Established a versioning schema with the new version.json file for project standardization.

Documentation

New version.json file added to define versioning schema and release management.

The addition of new entries in category.txt for the SCD4x sensor series is similar to the new entry protocol added in the devices/MulticastDNS/category.txt, indicating a common theme of expanding device classifications.

The categories are here: https://github.com/nanoframework/nanoFramework.IoT.Device/blob/af0c09147d00d5696bf64908cb0b646b76aeb085/src/device-listing/Program.cs#L12
I should move those into a JSON, so it can make it easy to adjust the categories. Still, the protocol one already exist.

I've contemplated the Endian converter changes. I'ld like to keep the IBitConverter interface around and will leave it in this repo for the moment. If another, lower level, spot can be found for it, great, then I'll be able to reuse it in Protobuf context.
As suggested I'm looking at the BinaryPrimitives library. It uses SpanBytes so that would mean that following method:
public char ToChar(byte[] value, int index = 0)
{
    return unchecked((char)FromBytes(value, index, 2));
}

In the implementation for Big Endian would change to this:
public char ToChar(SpanByte value, int index = 0)
{
    return unchecked((char)BinaryPrimitives.ReadInt16BigEndian(value.Slice(index, 2)));
}

All good it seems. However... the current implementation uses the buffer directly and reads the two needed bytes from the buffer at position 'index'. Hence there is no reallocation, no new objects to instantiate... no overhead whatsoever.
Going the SpanByte route seems trivial but does require allocation of a SpanByte through the Slice method... This introduces some overhead opposed to the current implementation when I look at the SpanByte Slice implementation as well as the SpanByte constructor.
So, what would be the preferable route then @Ellerbach?

Going the SpanByte route seems trivial but does require allocation of a SpanByte through the Slice method... This introduces some overhead opposed to the current implementation when I look at the SpanByte Slice implementation as well as the SpanByte constructor.

Slice does not allocate a new buffer, the buffer stays. Now, yes, you have a new object allocated.

Going the SpanByte route seems trivial but does require allocation of a SpanByte through the Slice method... This introduces some overhead opposed to the current implementation when I look at the SpanByte Slice implementation as well as the SpanByte constructor.

Slice does not allocate a new buffer, the buffer stays. Now, yes, you have a new object allocated.

Yep that was my point, new object with checks in both Slice and the SpanByte constructor that are not needed currently.
So seems to me that going with SpanByte only makes sense if there is another viable reason (where consistency could be one to start with)?

Yep that was my point, new object with checks in both Slice and the SpanByte constructor that are not needed currently.
So seems to me that going with SpanByte only makes sense if there is another viable reason (where consistency could be one to start with)?

Personally, I'm more for using the SpanByte and reusing the existing converters. One of the reason is indeed the consistency, we are using a lot in .NET IoT repository. And for maintainability as well, it makes things more clean. And less code to maintain because be already have the conversion done already.
And we don't really have a huge performance push for that specific mDNS thing, creating a class is not really expensive.
What we can do, even if I say we should not touch the System.Binary lib, is add primitives for bytes array with the index and length. Technically, we won't need much change in the code and everything can be reused. That's also an option we can put on the table if that's really necessary but I would prefer to avoid doing it.
@josesimoes any feedback on this?

Agreed that going with SpanByte is mostly consistency oriented. Which is not minor! Go for it.
Now, about adding new APIs to the SpanByte "just" for improving performance (which would be neglectable, if you ask me) I would stay away from that. It won't bring any real gain and would cause a change on mscorlib. Considering the current work and the release plan, it makes even less sense to touch SpanByte at this point.

@KlausVcb a suggestion for you: push changes in batches instead of doing it on each commit. Reason: each time you push a commit the AZDO pipeline starts a new run and that's a waste of resources. 😉

Will do, thanks for the suggestion. I'm used to pushing fast and often on personal dev branches that have no CI pipelines... Duely noted!

For efficient reuse a nuget is the way to go. OK to have it here, I suppose...

For efficient reuse a nuget is the way to go. OK to have it here, I suppose...

So you're saying adding a nanoFramework.BitConverter library or the likes in this repo?

One thing I noticed: BinaryPrimitives is lacking converter methods for double, should be added I guess?

I suppose so. If is not much trouble for you, please complete that missing feature. 😉

Ho, I never paid attention that they are not available! Definitely, something to add indeed!

System.Buffers.Helpers library PR has been created.
Once merged I'll update MulticastDNS to use the library.

Usage of System.Buffers.Helpers is in place and verified/tested :-)


Server complaining Invalid PUBREL fixed header

The 4 reserved bits for PUBREL fixed header is supposed to be 0010, however the mqtt_cpp client is sending 1001. Is there something I am missing ?

@ajayb0507 Is this still a problem?


PCL library missing

Hi,
I am trying to build the general library for my application. I installed libpcap and libyaml as suggestion. Everything is going well until I start building. The error shows
  Could not find a package configuration file provided by "PCL" with any of
  the following names:

    PCLConfig.cmake
    pcl-config.cmake

  Add the installation prefix of "PCL" to CMAKE_PREFIX_PATH or set "PCL_DIR"
  to a directory containing one of the above files.  If "PCL" provides a
  separate development package or SDK, be sure it has been installed.

I intent to install PCL but this library is huge. I dont know if you can list required PCL packages that I need or I have to install all of them (over 1GB)
The system that I want to build this library uses Debian (Buster).
Dung

Install it using apt-get install libpcl-dev


Create the tracing component

The tracing component must support easily adding traces to calculate how long operations too.
We will need to support adapters to send the trace results to 3rd partys (AWS Lambda, Sentry, Datadog, etc.)
I wonder if we should use https://github.com/opentracing/opentracing-javascript/ @mathieugh @Maxime-Gosselin ? It has no dependencies and maybe we could wrap it?

We should probably create network interceptors and everything so that when you include this module, it comes builtin with everything setup. WE should probably have a way to activate or deactivate tracing on top of that.

I mean, we could. It seems that their goal is to standardize tracing for distributed application. It perfectly aligned with our goal here. Plus it doesn't seem complicated to use.
I am not sure I understand the goal of the network layer. Would all of our tracing pass through that layer and depending on what is configure (AWS Lambda / Xray, Sentry, Datadog) it would then get dispatch to their respective service ? Or this mechanism would be the adapters ? Or am I confusing two different thing ?

Yes, something like that. I think we can approach tracing in a similar manner we approached logging. We want to be able to send the trace to different services. It would be nice for it to be plug and play, meaning you include the tracing module and you are good to go.

I just read that OpenTracing is now becoming OpenTelemetry. https://opentelemetry.io/docs/js/getting_started/nodejs/
They are combining Tracing with Metrics to provide a global solution under the name Telemetry.
What's interesting, is that it makes it easy for example to increment a number whenever there's a specific request. You can then out of the box calculate metrics on the number of http requests, the average response time, etc.. and then, when you need to investigate, you look at the traces.


Update TF version and ppc64le providers version

Moving the TF version variables up for global updates in future.
Update the TF version to use v0.13.6 (from v0.13.5) as that is also available for Power.
Update the ppc64le providers artifact version to v0.8 to include latest ibm-cloud plugin update.

Signed-off-by: Yussuf Shaikh<EMAIL_ADDRESS>

/lgtm