Chris s ecal reco phase2 gpu

PR description:

PR validation:

if this PR is a backport please specify the original PR and why you need to backport that PR:

Before submitting your pull requests, make sure you followed this checklist:

verify that the PR is really intended for the chosen branch
verify that changes follow CMS Naming, Coding, And Style Rules
verify that the PR passes the basic test procedure suggested in the CMSSW PR instructions

For the python config files have a look at how I organised them in https://github.com/thomreis/cmssw/tree/ChrisSEcalRecoPhase2GPU-dqm/RecoLocalCalo/EcalRecProducers/python
I could remove the GPU specific _cff file and put everything with the switchProducer in the existing one.

This has been merged elsewhere.


Adding LICENSE and issue and PR template

Will add LICENSE to the Repo
and issue template for bug , docs , feature
and Pr template
@07sumit1002 Please assign me this issue under wob'24

you can assign that task to me under gsso-ext and Hacktoberfest label..


Update languages.yml

Description
Added Somali, Wolof, Inuit, and Mayan as audio/subtitle languages
Type of Change
Please delete options that are not relevant.

[ ] New feature (non-breaking change which adds functionality)

Checklist

[ Y] My code was submitted to the nightly branch of the repository.

Not ready to merge:

Missing doc updates which were in #1534
Doesn't contain any flag images for most of the new languages

Messaged on Discord to discuss.

Ready to be merged along with #1537

still no flags for Wolof, Inuit, and Mayan


home: Remove handler for old compile-handlebars-templates error file

As of commit 8c199fd44c017ff268a87bad0b0980e44b56a16e (#12667) this file is no longer generated.  Handlebars compile errors are raised as webpack errors.

Merged, thanks @andersk!  For context, in https://github.com/zulip/zulip/pull/12802/commits/d1f139dd6097ef82e5c2fb383221b96057f7d046, most of those templates just had been renamed to templates/zerver/app/; so the important actual thing that changed is that our unit tests now cover those files, I think.


A fresh installation does not work?

Just installed, seems broken?
$ markdown-swagger
/usr/local/lib/node_modules/markdown-swagger/index.js:21
const [source, target] = cli.input
^
SyntaxError: Unexpected token [
at exports.runInThisContext (vm.js:53:16)
at Module._compile (module.js:414:25)
at Object.Module._extensions..js (module.js:442:10)
at Module.load (module.js:356:32)
at Function.Module._load (module.js:311:12)
at Function.Module.runMain (module.js:467:10)
at startup (node.js:136:18)
at node.js:963:3

What version of nodejs are you using?
On Fri, Sep 28, 2018, 18:59 andresmv<EMAIL_ADDRESS>wrote:

Just installed, seems broken?
$ markdown-swagger
/usr/local/lib/node_modules/markdown-swagger/index.js:21
const [source, target] = cli.input
^
SyntaxError: Unexpected token [
at exports.runInThisContext (vm.js:53:16)
at Module._compile (module.js:414:25)
at Object.Module._extensions..js (module.js:442:10)
at Module.load (module.js:356:32)
at Function.Module._load (module.js:311:12)
at Function.Module.runMain (module.js:467:10)
at startup (node.js:136:18)
at node.js:963:3
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/rmariuzzo/markdown-swagger/issues/1, or mute the
thread
https://github.com/notifications/unsubscribe-auth/AAa2H6-ZL1GQIIvkZw9QHu7HF66v1ZNWks5ufqnHgaJpZM4XALcX
.

Funny I was finally able to install in my project, but cannot seem to find the markdown-swagger executable anywhere.

@mickeybr try npm install markdown-swagger -g


Support rejecting invites with a reason

Proposal: Tell clients that they can reject an invite with an optional reason on the m.room.member. Copying from kicks/bans.
Use case: A user may wish to reject an invite to say "no, I don't want to talk to you". The homeserver may also be able to enhance the ignored users stuff by auto-rejecting with "This user has ignored you" or something. Another use case would be potentially a bridge/appservice/bot refusing to participate in a room due to some condition.

MSC2367 allows adding reasons to rejecting invites, amongst other things.

The homeserver may also be able to enhance the ignored users stuff by auto-rejecting with "This user has ignored you" or something.

I don't want a user to be able to tell that I ignored them so hopefully this would be optional

I would hope it is optional.

Can this be closed now that MSC2367 is merged?


Persistent collections updates (part 8)

Implement logarithmic-time index(_:offsetBy:) and index(_:offsetBy:limitedBy:) operations.
Cache the shared hash value of items in each collision node. (At the front of the storage buffer, where child entries would otherwise be stored.)
Review and sanitize/simplify node allocation logic. Ditto for key-based lookups.
Implement better handling of compressed paths in isSubset(of:)/isDisjoint(with:)

Checklist

[X] I've read the Contribution Guidelines
[X] My contributions are licensed under the Swift license.
[X] I've followed the coding style of the rest of the project.
[ ] I've added tests covering all new code paths my change adds to the project (if appropriate).
[ ] I've added benchmarks covering new functionality (if appropriate).
[ ] I've verified that my change does not break any existing tests or introduce unexplained benchmark regressions.
[ ] I've updated the documentation if necessary.

@swift-ci test

Showing of the algorithmic improvement by striding over the collection in 10 equal steps using index(_:offsetBy:):

That's 2066x faster on average. 🤓

The last commit adds a very rudimentary memory benchmark, as a standalone executable target in the hidden benchmarking package. It produces CSV output, comparing the memory efficiency of the standard Dictionary vs PersistentDictionary. Current (untuned) results are:

This plots memory efficiency as a function of collection size. Higher values are better.
I define "memory efficiency" as the net amount of memory needed to store the items in the collection divided by the gross amount of memory allocated overall. This ratio generally depends on the memory layout of the Key/Value types -- smaller payloads generally lead to lower memory efficiency, especially for tree-based collections. (As the relative weight of node headers + child references will be higher.)
For Dictionary<String, String>, average memory efficiency (over a logarithmic scale of sizes from 1 to 1M) is about 55%, while for PersistentSet<String, String> we currently measure about 54% -- this is pretty good, considering we haven't really tuned the allocation patterns yet. (The HAMT is really efficient for representing small dictionaries, because of the node compression scheme -- this small-scale behavior is why it is able to catch up to the standard Dictionary. The log scale gives weight to small values, which would be a bit unfair, except it tends to match actual usage -- small data sets are more frequent.)
Of course, this is measuring a single collection instance -- the memory efficiency of PersistentSet goes through the roof in use cases that actually make use of persistency. (Mutated copies of the same original dictionary share their storage nodes, making them extremely memory efficient.)

d87f5fd1e15565d2692895d216046392f33e0bc0 replaces recursion with looping for simple key-based lookups, resulting in a really nice 47-59% speedup.
Tasks with difference scores larger than 1.05:
  Score   Sum     Improvements Regressions  Name
  1.595   1.595   1.595(#75)   0.9998(#1)   PersistentDictionary<Int, Int> defaulted subscript, successful lookups (*)
  1.584   1.584   1.584(#76)   1.000(#0)    PersistentDictionary<Int, Int> subscript, successful lookups (*)
  1.486   1.486   1.486(#75)   0.9997(#1)   PersistentDictionary<Int, Int> defaulted subscript, unsuccessful lookups (*)
  1.474   1.474   1.476(#75)   0.9984(#1)   PersistentDictionary<Int, Int> subscript, unsuccessful lookups (*)

Latest commits:

PersistentSet, PersistentDictionary: Add more protocol conformances
PersistentSet: Add isEqual/isSubset/isSuperset/isStrictSubset/isStrictSuperset/isDisjoint overloads
_FastMembershipCheckable: New utility protocol to make the overload set more manageable
PersistentDictionary: Add structural filter and compactMapValues operations
PersistentSet implement structural filtering, subtraction, intersection
PersistentDictionary: Add an initializer to quickly convert a PersistentSet into a dictionary (without rehashing anything)

Note: The structural filtering/intersection/subtraction operations do not preserve unchanged nodes yet.

It is of course also possible to implement structural union and symmetricDifference operations (as well as structural dictionary merges) -- this is still tbd.

@swift-ci test


Update config.md

Proposed changes

Unreleased product version (optional)

Related issues (optional)

Thanks for picking up this error @ctison :)


Convert readthedocs links for their .org -> .io migration for hosted projects

As per their blog post of the 27th April ‘Securing subdomains’:

Starting today, Read the Docs will start hosting projects from subdomains on the domain readthedocs.io, instead of on readthedocs.org. This change addresses some security concerns around site cookies while hosting user generated data on the same domain as our dashboard.

Test Plan: Manually visited all the links I’ve modified.

The link on the Github repo description also needs updating.

[Current coverage][cc-pull] is 92.39%

Merging [#19][cc-pull] into [master][cc-base-branch] will not change coverage

@@             master        #19   diff @@
==========================================
  Files             3          3
  Lines           644        644
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
  Hits            595        595
  Misses           49         49
  Partials          0          0

Powered by Codecov. Last updated by [2644d20...61906b9][cc-compare]
[cc-base-branch]: https://codecov.io/gh/kislyuk/ensure/branch/master?src=pr
[cc-compare]: https://codecov.io/gh/kislyuk/ensure/compare/2644d20f2ae85c5189097e7ad96ae51bb1e460e3...61906b9c931ff2e5f5bd3398ea30da1065263213
[cc-pull]: https://codecov.io/gh/kislyuk/ensure/pull/19?src=pr


Competitive_Programming: Stack In C++

I would like to write a doc on Stack Data Structure in C++.

Introduction
Syntax and Implementation
Operations
Use cases
Complexity Differences

Can I try it?

sir, i would like to work on it.Please assign it to me.

I don't know how the things works in GWoC, whether contributor themselves can make the issue and can contribute directly to it, or the issue needs to  be first created by mentor/supervisor, then contributor can contribute,
PS: @siddhi-244 & @supriya-045 , @ravireddy07 itself is a contributor, 'Read the last line' he is asking to assign it to him.

@Vidit-Ostwal  Yes. Contributor's can create issues. But, can't work on it until it gets assigned by mentors.

i would like to work on this. please assign this to me.

I would like to contribute on this issue by presentaing a well flow structured  documentation and take it from a beginer to an expertise level explanation.Do assign it to me.
Ayushi Chauhan
Batch-1

I want to try on this issue.
Anjali Kumawat
Batch - 3

/assign

/unassign


Training Checkpoint Loading Error

Hi Team,
When I tried to load checkpoint to continue training via the DMPOConfig.checkpoint_to_load = {run_name}/checkpoints/dmpo_learner/ckpt-4.index, yielded the following AssertionError inside create_dual_variables_once.
ray.exceptions.RayTaskError(AssertionError): ray::Learner.run() (pid=3441185, ip=<IP_ADDRESS>, actor_id=155580693110898c9f9447d701000000, repr=<flybody.agents.ray_distributed_dmpo.Learner object at 0x7f0c90c71240>)
  File "/root/vast/scott-yang/flybody/flybody/agents/ray_distributed_dmpo.py", line 208, in run
    self.step()
  File "/root/vast/scott-yang/flybody/flybody/agents/learning_dmpo.py", line 324, in step
    fetches = self._step()
  File "/root/vast/scott-yang/flybody/flybody/agents/ray_distributed_dmpo.py", line 201, in _step
    return DistributionalMPOLearner._step(self)
  File "/root/anaconda3/envs/flybody/lib/python3.10/site-packages/tensorflow/python/util/traceback_utils.py", line 153, in error_handler
    raise e.with_traceback(filtered_tb) from None
  File "/root/anaconda3/envs/flybody/lib/python3.10/site-packages/tensorflow/python/framework/func_graph.py", line 1147, in autograph_handler
    raise e.ag_error_metadata.to_exception(e)
AssertionError: in user code:

    File "/root/vast/scott-yang/flybody/flybody/agents/learning_dmpo.py", line 274, in _step  *
        policy_loss, policy_stats = self._policy_loss_module(
    File "/root/anaconda3/envs/flybody/lib/python3.10/site-packages/sonnet/src/utils.py", line 85, in _decorate_unbound_method  *
        return decorator_fn(bound_method, self, args, kwargs)
    File "/root/anaconda3/envs/flybody/lib/python3.10/site-packages/sonnet/src/base.py", line 262, in wrap_with_name_scope  *
        return method(*args, **kwargs)
    File "/root/vast/scott-yang/flybody/flybody/agents/losses_mpo.py", line 216, in __call__  *
        self.create_dual_variables_once(dual_variable_shape, scalar_dtype)
    File "/root/anaconda3/envs/flybody/lib/python3.10/site-packages/sonnet/src/utils.py", line 85, in _decorate_unbound_method  *
        return decorator_fn(bound_method, self, args, kwargs)
    File "/root/anaconda3/envs/flybody/lib/python3.10/site-packages/sonnet/src/once.py", line 89, in wrapper  *
        _check_no_output(wrapped(*args, **kwargs))
    File "/root/anaconda3/envs/flybody/lib/python3.10/site-packages/sonnet/src/utils.py", line 85, in _decorate_unbound_method  *
        return decorator_fn(bound_method, self, args, kwargs)
    File "/root/anaconda3/envs/flybody/lib/python3.10/site-packages/sonnet/src/base.py", line 262, in wrap_with_name_scope  *
        return method(*args, **kwargs)
    File "/root/vast/scott-yang/flybody/flybody/agents/losses_mpo.py", line 142, in create_dual_variables_once  *
        self._log_temperature = tf.Variable(

    AssertionError:

This error message from tf.Variable is not particularly helpful since I cannot find any actual asserts to fix my code. However, the training can be run without loading the checkpoint.
Looking deeper into the checkpoint loading logic, I don't quite understand the logic at the this line, where the variable _checkpoint is created and restored but never used.
Could you help me with this issue? Any clarification and guidance is greatly appreciated!
Scott Yang.

Before we look further, can you try the same but without the .index at the end of the checkpoint name?

Thank you so much for your quick reply! That fixed the issue! I can't believe the issue is the checkpoint file name lolll. I guess I am not so familiar with the tf's checkpoint naming system. Anyway, thanks for your help!


assertMethodWired for action with params/args does not work or not documented

What is right syntax to check action with params?
<x-jet-danger-button type="button" wire:click="deleteConfirm({{$id}})" >

This one does not catch
$component->assertMethodWired('deleteConfirm');

Hey @dostrog,
thanks for the update. Params are not supported yet. Could you do a PR for that?

Yeah, sure
PR to resolve issue#7


INFINITY-1110 Clean up port offer evaluation: Remove task update, use DiscoveryInfo names

Ports without VIPs are now correctly grouped by port name rather than task type under endpoints lookup. Now a VIP is no longer needed to appear in endpoints. The port name field itself recently started being set as of PR #1149.
Other cleanup relating to port/VIP handling:

For dynamic port lookup, prefer searching the DiscoveryInfo for a matching port name, instead of the task envvars. Leave envvar lookup as a temporary fallback for upgrade scenarios where the port name isn't set in the TaskInfo.
Remove update logic from both port and VIP evaluation. TaskInfos are now created from scratch every time so any update logic is effectively dead code.
Remove two YAML spec VIP fields which had long-standing TODOs to be removed. Add a temporary throw to explicitly complain if the fields are still present.

Going to reduce this PR to not change the current default behavior (additional non-VIP entries in endpoints) pending PM input. Changes to behavior, if any, will be done in a separate PR. Please hold..

OK back to prior default behavior.

[23:02:23][Step 4/4] frameworks/helloworld/tests/test_web_url.py::test_deploy
[23:02:23][Step 4/4] frameworks.helloworld.tests.test_web_url.test_deploy (15s)
[23:02:38][Step 4/4] The build PR Jobs::Hello World PR #269 {buildId=706942} has been running for more than 130 minutes. Terminating...
[23:02:38][Step 4/4] Execution timeout

??

That should be fixed. Re-running.


Building Issue VS2017

Environment
Windows build number:  [Version 10.0.18362.145]
Windows Terminal version (if applicable): v0.1.1581.0

Any other software?

x64 based processor
VS 2017

MSBuild auto-detection: using msbuild version '<IP_ADDRESS>4' from 'C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\MSBuild\15.0\bin'.

Steps to reproduce
1. git clone https://github.com/microsoft/terminal.git windowsterminal
2. cd windowsterminal
3. git submodule update --init --recursive
4. dep\nuget\nuget.exe restore OpenConsole.sln
5. Open OpenConsole.sln in VS2017
6. Set Solution Platforms to 'x64'
7. Set Solution Configurations to 'Release'
8. Build>Deploy Solution

Expected behavior

Windows Terminal builds successfully so it can be used
Actual behavior

VS2017 gives 3 errors:

Error	MSB3073	The command "mc.exe /h C:\Users\User\Desktop\windowsterminal\\obj\x64\Release\Propsheet.DLL\ /r C:\Users\User\Desktop\windowsterminal\\obj\x64\Release\Propsheet.DLL\ strid.mc" exited with code 1.	Propsheet.DLL	C:\Users\User\Desktop\windowsterminal\src\propsheet\propsheet.vcxproj	81
Error		0x3 trying to open file <User\Desktop\windowsterminal\\obj\x64\Release\Propsheet.DLL\>.	Propsheet.DLL	C:\Users\User\Desktop\windowsterminal\src\propsheet\mc	1
Error		The command "copy C:\Users\User\Desktop\windowsterminal\\dep\WinAppDriver\* C:\Users\User\Desktop\windowsterminal\\bin\x64\Release\\" exited with code 1.	Host.Tests.UIA

I was able to circumvent this problem by using the build guide.
#489

Hi, how did you fix the issue? I followed the build guide but I get those specific three errors everytime when I try to compile the terminal.

Hi there, I built it and I got a few errors but then i deployed it and it seemed to work. I just ignored the errors (sorry if this isn’t that helpful)

Myles Newton

From: theedoran<EMAIL_ADDRESS>Sent: Monday, June 17, 2019 6:25 am
To: microsoft/terminal
Cc: mnewt00; State change
Subject: Re: [microsoft/terminal] Building Issue VS2017 (#1172)
Hi, how did you fix the issue? I followed the build guide but I get those specific three errors everytime when I try to compile the terminal.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHubhttps://github.com/microsoft/terminal/issues/1172?email_source=notifications&email_token=AKTHSFZIEMPQ3R2USRUKQC3P22OTDA5CNFSM4HWGGBIKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODXZUQVY#issuecomment-502483031, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AKTHSF5AVGXXBHYI6RQHOEDP22OTDANCNFSM4HWGGBIA.


Allow selectors to target assigned values

[x] Add new step for assigning values from response body to value.
[x] Allow for testing against value of bound structures without stringifying...or stringify to JSON which will then get transformed back

Subsumed by some newer issues.


Added a top level sln file for all projects, and removed internal ones

Hi @msalehmsft, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution!
You've already signed the contribution license agreement. Thanks!
The agreement was validated by Microsoft and real humans are currently evaluating your PR.
TTYL, MSBOT;

After uploading the nuget package, the solution failed to automatically download the nugets into the provider directory, so the provider library was failing to find them. Making it a flat solution, fixed that issue.


Migration to Mocha doesn't work

I had a meteor project with jasmine tests working correctlly (as per Meteor test 1.3).
I followed the migration guide to Mocha (here: https://github.com/Sanjo/meteor-jasmine/wiki/Migrate-to-Mocha ) and now it doesn't work anymore: no tests are executed.
I made sure I replicated the exact same structure of the sample project in this repo, but when I run the command
meteor test --full-app --driver-package dispatch:mocha-browser

or
meteor test --settings settings.json --port 9000 --driver-package dispatch:mocha-browser --full-app

mocha tells me there are no tests to run.
What am I missing, please?

To anyone interested, I resolved:

changing require() to Npm.require()
moving tests out of /imports (they are totally ignored there, I don't know how to make mocha execute them)

meteor test is broken in Meteor 1.3.2.x. So I would recommend to use 1.3.1 or 1.3 for now until 1.3.3 is released.

I have added a note to the migration guide.


Async implementation

I would like to ask if there is interest in making an async version of the crate?
I'm using the sensor in an embassy project and while some other sensors use async version of the I2C bus and I can use embassy_embedded_hal::shared_bus::asynch::i2c::I2cDevice to share the bus across multiple tasks, it's not possible to use a driver crate with a blocking I2C impl.

So far I haven't yet played with embassy. I assume it uses the traits from embedded-hal-async, right?

Yes, indeed. There's already a RC version for -async so it might get stabilised especially with AFIT (async fn. In traits) hitting 1.75

@dbrgn both embedded-hal and embedded-hal-async are on v1.0.0
It would be amazing to update the crate and support the stable version of the hal crates.

Support for e-h 1.0 is tracked in #31. Once that's in, it probably makes sense to add an optional feature for embedded-hal-async as well.

Can you expect an async version soon?

Can you expect an async version soon?

Only if somebody steps up and contributes an initial implementation.
Something that should be taken into account is that #38 should probably be handled before adding async support (since it might have interactions, potentially even benefits).


"Generic" View Actions?

I am sure this has been discussed in the past, but I could not find any reference to it. The proposal is to provide a way for "generic" Actions to be so that any custom View is already Rx-ready as long as it follows certain naming conventions. I have in mind something along the lines of:
 /**
   * An action which sets the specified property of {@code view}. The View is expected to have a setter of the form set[propertyName] in camel-case.
   *

   * Warning: The created observable keeps a strong reference to {@code view}. Unsubscribe
   * to free this reference.
   */
  public static Action1<?> property(final View view, final String prop) {
    checkNotNull(view, "view == null");
    return new Action1<Object>() {
      @Override public void call(Object value) {
        final Method method = view.getClass().getDeclaredMethod(Utils.getMethodNameForProperty(prop), new Class[]{value.getClass()});
        method.invoke(view, value);
      }
    };
  }

Some observations about this in no particular order:

A useful way to bind any property of any custom View to some value
Roughly comparable to utilities available in ReactiveCocoa (example - RAC() macro) although the language capabilities are a whole lot different in these two cases
Reflection! Ugly, not type-safe.
That requirement about having a setter for the property - again not pretty ... ...
... ... but, you probably already follow it if you are using the Property Animation framework (does this use reflection too BTW?Just curious)

Very hesitant about using reflection. You lose compile-time safety and introduce overhead whereas the library now is very low overhead (close to no overhead).

you probably already follow it if you are using the Property Animation framework (does this use reflection too BTW?Just curious

No. It's parameterized over a type (e.g., Integer) and then offers T get() and set(T value) methods.

Actually, it depends on that last point. You can either use Property-based properties which are reflection free, or it'll fall back to either using jni to cache method handles and invoke as a faster reflection or finally do normal Java-based reflection.

Very hesitant about using reflection.

Fair enough.

it'll fall back to either using jni to cache method handles and invoke as a faster reflection or finally do normal Java-based reflection.

Ah I see. JNI. I guessed there had to be some way to avoid invoking a method through reflection at every frame!
Thanks for the explanation. Do you want to keep this thread open for more opinions? Or should I close it?

I'm going to close it because it's easy to implement this yourself if you wanted the reflection-based version of this. For a library, though, I'd like to retain the safety of the methods.


Keyword expansions should have colon

echo :foo
Should just print ":foo"

Related to #211

Less clear, it is useful to be able to do this.
:<IP_ADDRESS>.* and have expansion work.


Failed with Bolt

I am trying to use this module with bolt targetting remote node. But this fails with the following error.
valuation Error: Error while evaluating a Function Call, Failed to open TCP connection to <IP_ADDRESS>:80 (Connection refused - connect(2) for "<IP_ADDRESS>" port 80) (file: /etc/puppet/site-modules/roles/manifests/mymodule.pp, line: 5, column: 13) on node X.X.X.X
My code is very simple as
$secret = azure_key_vault::secret('myvault', 'PassMain', {
   metadata_api_version => '2018-04-02',
   vault_api_version    => '2016-10-01',
 })
 $rewraped_secret = Sensitive("${secret.unwrap}")
 notice($rewraped_secret)

If i execute the same command using puppet apply that works fine in that remote node. Any  suggestions?

Hey @yesoreyeram ,
Are you able to do the following for me.

Puppet apply
a. Debug logs
b. Code
c. Command line used to run puppet apply
Bolt
a. Debug logs
b. Code
c. Command line used to run bolt

NOTE: Please redact or obfuscate any sensitive data

Hey @yesoreyeram,
Is this still an issue or did you figure it out?

Yes still this is an issue. But sorry, I couldn't get you the traces.  I afraid I can't get you that anytime soon as I am not actively workig on that part.
I am closing this issue. If require i will reopen later or feel free to reopen.


Need a configuration for Binance

Binance is a popular exchange that appears to have good support in XChange, and possibly websocket support as well. We should try to get a working configuration for it that can be posted on the Wiki:
https://github.com/scionaltera/arbitrader/wiki/Recommended-Exchange-Configurations

-
  exchangeClass: org.knowm.xchange.binance.BinanceExchange
  apiKey: x
  secretKey: x
  tradingPairs:
    - BTC/USD
    - ETH/USD
    - XRP/USD
    - ZEC/USD
    - LTC/USD
    - BCH/USD
    - NEO/USD

- ADA/USD
    - EOS/USD
  margin: true
  fee: 0.001

  homeCurrency: USDC

This is what i have for binance. ADA pairs gives division by zero error and i can not understand why.
So far bot works with that config but i did not have real traded happen....

-
  exchangeClass: org.knowm.xchange.binance.BinanceExchange
  apiKey: x
  secretKey: x
  tradingPairs:
    - BTC/USD
    - ETH/USD
    - XRP/USD
    - ZEC/USD
    - LTC/USD
    - BCH/USD
    - NEO/USD
    - EOS/USD
  margin: true
  fee: 0.001

  homeCurrency: USDC

This is what i have for binance. ADA pairs gives division by zero error and i can not understand why.
So far bot works with that config but i did not have real traded happen....

Thanks! I'll sign up for an account when I have a chance and see if it works for me too. You can open a separate issue for the divide by 0 problem if you want to.

Closing this because we have a working configuration for Binance in the docs and are including the Binance library in the main line code now.


Account page

This adds the ability to change name to the account page, fixes the persistent login, and adds a prettyAddress value to the loginAccount selector to work with the new display on the account page in AURC 3.0.20

Coverage decreased (-0.4%) to 76.721% when pulling 2204324c1cb6d79dc674d8e44725992bc0be227e on accountPage into d9fe08dab5bca22c38e30b007c18e3690a70fecd on master.

Coverage decreased (-0.4%) to 76.721% when pulling 26af55a44f032c11dc0d24d90b567e07af94d38b on accountPage into febdcae8a7ef767c5efad97d750fbeede27bcddc on master.


Update Azure.Identity and KeyVault codeowners

Adding @mccoyp and removing @iscai-msft so the former gets more spam, the latter less 😸

/check-enforcer override


Wrong constellation numbers

I've notice that some of my characters have wrong constellation counts. For example i have a c5 razor but on paimon.moe it says c3. The same goes for barbara and amber who is both c3 and the website says they are only c2

The wish history is not kept forever, your first wishes are probably not saved anymore by mihoyo and therefore paimon.moe cannot import them.
You can set the number manually if it isn't correct.

Duplicate #55


Create read-only global variables

[ ] design preliminary syntax
[ ] figure out proper way to encode this in SIR
[ ] Implement correct matching & transformation in dusk

We can probably do this with externals (#42, #60)


Core 3.0 - Server Connections Count

Hi,
I have implemented the service using core 3.0 and I see that the number of server connections does not follow the rule described in
https://docs.microsoft.com/en-us/azure/azure-signalr/signalr-concept-messages-and-connections#how-connections-are-counted
I have one application servers and define five hubs in the code.
(1 application servers * 5 hubs * 5 connections per hub) = 25 connections

Why does the number of connections vary so much?
In the last 12 hours the server connection number remains at 39, but never at 25

Regards,

Thanks for reporting the issue. The document is a bit out-of-date and we will have an update on that. The initial server connection count (when app server starts) is as the document illustrated 25 connections, and while the service is running, there will adjustment to server connections (for example, on-demand created connections or connection close) for better performance and service stability. The principle of server connection adjustment is to minimize the impact on connected client connections.
For your case, you can email me<EMAIL_ADDRESS>your instance name to check the detailed reason for this server connection adjustment.

Hi @vicancy
Thank you for your response and email support.
Regards,


--db option not working

Dear all,
I am just in the process of testing the latest version of testrpc (4.1.3) and the --db option still appears to not be working correctly as reported in earlier versions by users.
In summary, the chain data appears to be saved but when closing and starting testrpc again, my test contract is no longer deployed.
Has anyone been able to get this feature to work in v4.1.3?
Many Thanks,
Pete

Same results here

Same here

Right now for the --db option to work correctly you need to run ganache-cli the second time using the same mnemonic and network id.
In a future release we'll store this information in the database and retrieve it on start, and give a warning when the user specifies a mnemonic or network id which is different from the one which was stored.

This does not work for me. Connected to #642
If I start the chain via my Thundercloud script: https://github.com/status-im/thundercloud
and then try re-running from saved DB inside deploy/db (db exists, files are created), I get a bunch of new accounts, even if I use the same mnemonic and network ID: ganache-cli --db deploy\db --mnemonic "main blouse fashion brand own rocket fluid notable vacuum gain guitar leaf" -i 666

ganache-cli --db deploy/db --mnemonic "main blouse fashion brand own rocket fluid notable vacuum gain guitar leaf" -i 666 outputs the same accounts every time for me (notice I changed \ to / in the --db path).
this small program (install ganache-core locally first) outputs the identical accounts as well:
var provider = require("ganache-core").provider({
    mnemonic: "main blouse fashion brand own rocket fluid notable vacuum gain guitar leaf",
    "network_id": 666
});
provider.send({
    jsonrpc: "2.0",
    id: 1,
    method: "eth_accounts",
    params: []
}, console.log);

@Swader, what version of ganache-cli are you using?

Sorry should have been more specific. Accounts are same, yes, but the state is not. So what I do first is I generate accounts with a script, seed them with some eth, deploy a contract, do some transactions. Then, I fire up ganache from this DB, but my accounts are always fresh - they have 100 eth. Something just occured to me though - if I don't specify an account limiting flag like -a 1 to limit to 1 account, and I have inserted and seeded 10 accounts in another script, will the default of a=10 then reseed those accounts with 100 eth even if they were in the db? It shouldn't right?


Bandwidth optimization (fetching less images) and clusters with temporarily broken internet access

@silenteh @gawertm @alex-dabija @puja108 @piontec fyi we need to define the requirements for the smart factory use case and the bandwidth optimization that we are planning to do. At the moment there seems to be unclarity about what we need to build and we already started with a solution. Are there other issues where this has been discussed? Let's collect all the information here please.

@teemow here the requirements and I have marked the ones which are already supported by the solution I started to build.
@teemow @gawertm @alex-dabija @puja108 @piontec Feel free to add more requirements if needed.

[x] Support for multiple upstream container registries. The registries could be located both in the LAN or WAN. Support for multiple upstream registries based on the hostname (map the hostname of the cache instance to upstream hostname)
[x] Authentication should be handled only at the registry level, so there is no duplication of credentials at the pull-through cache level
[ ] The pull-through cache, should still validate the requests, so that images cannot be pulled unless there is a valid authentication token. This means the pull-through cache should cache the authentication responses itself. Every time a client re-authenticate with the upstream registry the authentication token needs to be refreshed in the pull-through cache.
[x] Pull through cache should re-validate the container image manifest with the upstream repository so that in case upstream has overwritten a tag, then the cache will serve the up to date container image
[ ] In case an upstream registry is not reachable the cache should be able to serve the container image. This means the cache needs to keep a state of: human readable TAG version => SHA256 of the manifest of the specific container image
[x] When the cache downloads the upstream data it should validate the content by calculating the sha256 of the data to make sure it's not storing corrupted blobs. This means the data should be downloaded in a temporary file, the hash calculated and if it matches, the cache should use an atomic move operation to persist the blob.
[x] When the cache both pulls the data and stores it locally it MUST use zero copy, otherwise the cache ends up using gigabytes of RAM. The larger the container image layers the more memory it will use.
[x] When the data is served from the cache it SHOULD use zero copy to decrease memory consumption
[x] Https support
[x] Clean shutdown so that in case there are some files still being written the process waits for them to be fully persisted before exiting
[ ] Support for Helm Charts
[x] Prometheus metric:

[x] total requests
[x] upstream requests
[x] cached requests
[x] cpu and memory consumption (when running in Linux only - does not work in MacOS because it lacks the /proc/ folder)

we need to define the requirements for the smart factory use case and the bandwidth optimization that we are planning to do

This is not only for smart factories but also for customers in general.
The pull through cache allows container images to be served faster and in case the upstream is down (happened recently with Quay.io) then the images can still be pulled.
This also helps to save money when using DockerHub paid subscription.

At the moment there seems to be unclarity about what we need to build and we already started with a solution

It's quite clear to me what needs to be built, this is why I already started.
None of the available open source solutions, I could find and test, fit the bill.

@silenteh I would have preferred to discuss the options for something this fundamental. We've been bitten hard with developing our own solutions because feature a or b is missing in an upstream project. Imo it is far better to work with upstream and adding a feature than developing our own. Especially with the context that you are leaving the company this is a huge risk for us.

All good then.

Development is halted
Above the list of requirements a container registry pull-through cache should have IMHO

I am working on more clarity together with Sebastian. We talked about this a lot already so we will try to destill these thoughts into paper :)

Let's try to clarify a bit here:

The above technical requirements are for a pull-through cache (PTC), which has it's uses in some areas we are interested in (mainly cost-reduction and performance with a bit of failure reduction)
We have different requirements and use-cases at different customer, where such a component could work or not
We know some customers and use cases might need fully private registries (which are also on our roadmap in general) and those usually support at least in parts the work of a PTC

The customer who we started the PTC for wanted it mainly for cost-reduction
We have an existing customer who is asking us for a fully private local registry on-premises, where a PTC is not sufficient to fullfil all their requirements AFAIK
We are ramping up a customer and the Smart Factory use case, where we are unsure if the use case and requirements are actually just a PTC or a private registry

I would assume for the first 2 we have internal issues describing the use cases. Let's also have one for the 3rd and inquire with the customer what the actual requirements are.
Once we have all use cases and timelines it will be easier for the team to decide on implementation details.

@weatherhog this is an old issue about the registry caching. Just FYI. If there is no new information, feel free to close this and use your current issues.

closing this because we are tracking this in these issues:
https://github.com/giantswarm/roadmap/issues/3066
https://github.com/giantswarm/roadmap/issues/3068
https://github.com/giantswarm/roadmap/issues/3069
https://github.com/giantswarm/roadmap/issues/3070


Stuck on redfish-username or redfish-password: "invalid config: 'redfish-username' or 'redfish-password'"

Hi, currently running hardware-observer, rev 59. it's deployed under some ceph-osd units, on bare metal machines (Dell R650). Redfish is enabled on the iDRAC interfaces, and I can test the username/password successfully with redfishtool.
I believe this is an issue with parsing, as the original password has a $ in it. Creating a new user without a $ in the password results in a successful authentication (based on debug logs for the unit).  When passing the redfish-password config option, I am taking care to escape the $; checking the value with juju config hardware-observer confirms the password is set correctly. Interestingly, the status doesn't change from blocked/idle with "invalid config: 'redfish-username' or 'redfish-password'", despite having a seemingly successful connection from the debug log.
To replicate, just set your user password to include at least a $, although the password also contains other special chars (@)
Example of error from $ password:

example of successful auth with "simple" password:

Apologies for the screenshots, I can provide private logs on request.

So I can workaround this issue by updating the redfish username and redfish password. The juju debug log shows 201 status codes, so I am logging in sucessfully and it seems to be able to talk to the iDRAC. However, I see "Exporter is not installed properly" in the debug log. Any ideas on how to reinstall this exporter?

Can you try refreshing the charm to a newer revision, e.g. latest 69 revision? There was an issue before: if the redfish credentials wasn't correct at the beginning (during installation of the charm, the exporter will not be installed, and that issue should be fixed)


Getting installation error "Could not find or load main class add"

Is this a bug report?
Yes

Have you read the Contributing Guidelines on issues?
Yes
Environment
npm
Steps to Reproduce

(Write your steps here:)

Installed using npm
initialized using "docusaurus-init" command
Got the error

`Website folder created!
Installing latest version of Docusaurus in website.
Error: Could not find or load main class add
Docusaurus installed in website folder!
Error: Could not find or load main class run`
Expected Behavior

(Write what you thought would happen.)
Actual Behavior

(Write what happened. Add screenshots, if applicable.)
Reproducible Demo
(Paste the link to an example repo, including a siteConfig.js, and exact instructions to reproduce the issue.)

@muthugit There isn't enough information in your bug report to reproduce this error. Could you add more information?


Adding turns

fixes #106
fixes #113

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

16 of 16 (100.0%)  changed or added relevant lines in 3 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.006%) to 98.845%

Totals

Change from base Build<PHONE_NUMBER>:
0.006%

Covered Lines:
1625

Relevant Lines:
1642

💛  - Coveralls

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Warning: This coverage report may be inaccurate.
This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

For more information on this, see Tracking coverage changes with pull request builds.
To avoid this issue with future PRs, see these Recommended CI Configurations.
For a quick fix, rebase this PR at GitHub. Your next report should be accurate.

Details

60 of 60 (100.0%)  changed or added relevant lines in 3 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.03%) to 98.874%

Totals

Change from base Build<PHONE_NUMBER>:
0.03%

Covered Lines:
1668

Relevant Lines:
1685

💛  - Coveralls

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Warning: This coverage report may be inaccurate.
This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

For more information on this, see Tracking coverage changes with pull request builds.
To avoid this issue with future PRs, see these Recommended CI Configurations.
For a quick fix, rebase this PR at GitHub. Your next report should be accurate.

Details

60 of 60 (100.0%)  changed or added relevant lines in 3 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.03%) to 98.874%

Totals

Change from base Build<PHONE_NUMBER>:
0.03%

Covered Lines:
1668

Relevant Lines:
1685

💛  - Coveralls


fix(chips): add return value type to handleTrailingIconInteraction

Without this, errors will be thrown when incorporating projects have no-implicit-any enabled.

Thanks @rapropos !


apex failure when trying the tutorial twilio-salesforce dialer

I opened a trial account and I'm trying to create a simple dialer with this tutorial
Thing is that first step of installing Twilio-Salesforce library (this url
is failing with
[Installing this package requires the following feature and its associated permissions: Apex Classes]
Apex Classes(classes/TwilioTRCapability.cls-meta.xml) Missing feature
triied to install to admins, to all users, nothing helps.
How exactly I install apex on a new trial salesforce env

Something about this issue??? i have a same problem, one year before....


Unable to add source for libXp6 package

@agramfort Instructions for resolving the missing libXp.so.6 package issue were helpfully added to the MNE-C documentation: http://mne-tools.github.io/dev/install_mne_c.html#troubleshooting. Unfortunately, with my Ubuntu 18.04 setup, the following error pops up when attempting the first command:
W: GPG error: http://security.ubuntu.com/ubuntu precise-security InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 40976EAF437D05B5
E: The repository 'http://security.ubuntu.com/ubuntu precise-security InRelease' is not signed.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
Attached is the full traceback.

Thanks, Joan! Thinking of mne documentation, what is the best place to put these GPG key instructions do you think? From a user perspective, it would be fantastic if a couple lines of code to obtain the keys could be added to the troubleshooting snippet installing the libXp package.

Did it work?
I think that the instructions should be added here. But they change
overtime. So the snipped might be outdated pretty soon. But it might be
worth it. Maybe when it stop working someone would rase the issue.
Would you like to wite a PR for it?
On Tue, Oct 23, 2018, 23:45 nordme<EMAIL_ADDRESS>wrote:

Thanks, Joan! Thinking of mne documentation, what is the best place to put
these GPG key instructions do you think? From a user perspective, it would
be fantastic if a couple lines of code to obtain the keys could be added to
the troubleshooting snippet installing the libXp package.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/mne-tools/mne-python/issues/5650#issuecomment-432432255,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AGt-49cmuR6R7oDF1xBoikO2IeNLMnayks5un43sgaJpZM4X2kCT
.

@massich Hmm. Getting the key for the NeuroDebian repo did not work for me. The initial command wget -O- http://neuro.debian.net/lists/bionic.us-nh.libre | sudo tee /etc/apt/sources.list.d/neurodebian.sources.list results in my terminal sitting around doing nothing. Take a look. This is how the terminal has looked for the past hour.

It seems like the critical command will be the second one (the sudo apt-key one), can you try that then see if the libXp install works?

...actually just try:
sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 40976EAF437D05B5

Hi,
I tried the second command. And I tried to add the key from a different
keyserver as well (keyserver.ubuntu.com). None of the keyservers I tried
seems to have the key for the repository in the proposed fix.
Erica Peterson
Research Scientist
Institute for Learning and Brain Sciences
University of Washington
Box 357988
Seattle, WA 98195
(206) 685-2842
On Thu, Oct 25, 2018 at 12:11 PM Eric Larson<EMAIL_ADDRESS>wrote:

It seems like the critical command will be the second one (the sudo
apt-key one), can you try that then see if the libXp install works?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/mne-tools/mne-python/issues/5650#issuecomment-433170468,
or mute the thread
https://github.com/notifications/unsubscribe-auth/Ak6W0MH7ChKFo2q7roT3kNhcJJ8TJBgiks5uogxXgaJpZM4X2kCT
.

Okay how about these two lines:
sudo apt -o Acquire::AllowInsecureRepositories=true -o Acquire::AllowDowngradeToInsecureRepositories=true update
sudo apt -o APT::Get::AllowUnauthenticated=true install libxp6

To specify, I did try the key command with
40976EAF437D05B5
as the key number.
Erica Peterson
Research Scientist
Institute for Learning and Brain Sciences
University of Washington
Box 357988
Seattle, WA 98195
(206) 685-2842
On Thu, Oct 25, 2018 at 12:14 PM Erica R. Peterson<EMAIL_ADDRESS>wrote:

Hi,
I tried the second command. And I tried to add the key from a different
keyserver as well (keyserver.ubuntu.com). None of the keyservers I tried
seems to have the key for the repository in the proposed fix.
Erica Peterson
Research Scientist
Institute for Learning and Brain Sciences
University of Washington
Box 357988
Seattle, WA 98195
(206) 685-2842
On Thu, Oct 25, 2018 at 12:11 PM Eric Larson<EMAIL_ADDRESS>wrote:

It seems like the critical command will be the second one (the sudo
apt-key one), can you try that then see if the libXp install works?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/mne-tools/mne-python/issues/5650#issuecomment-433170468,
or mute the thread
https://github.com/notifications/unsubscribe-auth/Ak6W0MH7ChKFo2q7roT3kNhcJJ8TJBgiks5uogxXgaJpZM4X2kCT
.

Eric's lines worked great.


Tensorboard logging

Describe the issue:
Hello, I'm using NNI v3.0 and trying to log using tensorboard. On the code I create the logging directory as log_dir = os.path.join(os.environ["NNI_OUTPUT_DIR"], "tensorboard") but when I try to open tensorboard on the webgui doesn't appear any logging. Looking at the output directory I noticed that the NNI_OUTPUT_DIR points towards to

nni-experiments/dh1ou4w7/environments/local-env/trials/dqOLE/tensorboard

but tensorboard is trying to read

nni-experiments/dh1ou4w7/trials/QlXHm/output/tensorboard

How can I get the correct one and what's the difference of both?

Hello, is there any news regarding this?


Typescript rewrite

Coverage increased (+0.2%) to 98.826% when pulling d23e0dfa5acefa6453a1d3e2432943d09b10cd35 on typescript into 475fb53d4094a1cd3a1d05d27483ecb928db228f on master.

I'm going to take more of a hybrid approach instead of going full on.
In fact, bin is already converted to TS!


fix: update workerd version

🔗 Linked issue

❓ Type of change

[ ] 📖 Documentation (updates to the documentation, readme, or JSdoc annotations)
[ ] 🐞 Bug fix (a non-breaking change that fixes an issue)
[ ] 👌 Enhancement (improving an existing functionality like performance)
[ ] ✨ New feature (a non-breaking change that adds functionality)
[ ] 🧹 Chore (updates to the build process or auxiliary tools and libraries)
[ ] ⚠ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description

📝 Checklist

[ ] I have linked an issue or discussion.
[ ] I have updated the documentation accordingly.

Thanks! Could you run pnpm install on the PR to update the lockfile so the tests pass.


zookeeper: Fix wrong paths in startup script

Motivation for this change
Substitution needs to be done before wrapping, else it doesn't substitute anything.
Things done

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

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

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

Notify maintainers
cc @

ping


OpenTelemetry Backend Module Template

Expected Behavior
Create a module for using OpenTelemetry with examples.
Specifications
As a developer, I would like to use OpenTelemetry and understand how to use through examples so I can have my metrics tracked.
Features:

OpenTelemetry integration

Development Tasks:

[x] OpenTelemetry Module

Dependencies
nil
References
nil

Researched and discussed with Richard regarding frontend implementation.


Logging working and enabled by default?

First, based on the comment in addons-setup script it seems that there should be expected issues with logging functionality. Is this still the case or the logging is working correctly now? If it is not working correctly, what are the issues?
Second, is logging addon expected to be installed by default and running after initial vagrant up? I can see it is running for me but after seeing https://github.com/openshift-evangelists/vagrant-origin/issues/28 I wonder if that was the original plan. However, the default configuration seems to include logging now.

I just spun up the latest version and it's close to working, but the route isn't working after I accept the self-signed cert.  Then, looking at the archive yields a redirect error :(

May be this is the same redirecting issue @richm has been hitting for some time now? Rich do you know if there is opened issue for this somewhere (may be in aggregated logging)?

@lukas-vlcek you mean for the kibana issue?  I don't know.  It's probably a configuration issue - i.e. you have to get the vm and the host machine to have the same forward and reverse resolution for the kibana hostname and IP address.  That seems to be tricky to get right, and any guidance from anyone who has been able to do this would be very appreciated.

@lukas-vlcek The comment is there, since I still need to figure out what's the best way to install logging. It seems to change with every release, but latests should be working (Still need to try this again).
The issue #28 adds scripts to enable/disable logging. What these do is scaling them to 0 or back to 1, but the pods need to be installed at least once with the initial setup, which is what happens.
So, in summary, default install will have logging enabled, but can be disabled (although still installed). You can of course, choose not to install.
I'll retry the install and if everything works will close this issue.

Just spun up a new instance, and the LOGS tab is gone entirely :(
What happened?

The logging pod is up, but no log tab :(

@jfmatth and @lukas-vlcek: after PR merge that provided the fix for #39, the logs and even the "View archive" works for me. Please have a check if it also works for you.

With the default configuration:
export __OS_ORIGIN_BRANCH="master"
export __OS_IMAGES_VERSION=latest

the deployment is compiling the last comit, but is downloading the images tagged with v1.2.1
I got it working either by compiling the images or using the configuration:
export __OS_ORIGIN_BRANCH="master"
export __OS_IMAGES_VERSION="v1.3.0-alpha.2"

That's a problem as latest are just tagged after 1.2.1 got released. I hope
this will get fixed soon.
Will open an issue in origin.
El 21 jul. 2016 22:08, "Horatiu Eugen Vlad"<EMAIL_ADDRESS>escribió:

With the default configuration:
export __OS_ORIGIN_BRANCH="master"
export __OS_IMAGES_VERSION=latest
the deployment is compiling the last comit, but is downloading the images
tagged with v1.2.1
I got it working either by compiling the images or using the configuration:
export __OS_ORIGIN_BRANCH="master"
export __OS_IMAGES_VERSION="v1.3.0-alpha.2"
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/openshift-evangelists/vagrant-origin/issues/33#issuecomment-234368414,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAEyDn2S7MtHyshC8UevST9lSah4_shaks5qX9HAgaJpZM4JMj16
.

Just seen again and latest should not be the same as 1.2.1, as a latest is
being built and push every day.
Maybe an error in the script. Will check tomorrow.

Just checked the latest version, and after a bit of time (on my 8gb Windows laptop) Kibana came up, lovely.

I am still not able to access Kibana UI. Probably I am doing something wrong. I haven't installed any app so far, I am just talking about OOB state after vagrant up and after oc get pods indicate all deployments are finished:
# oc whoami
system:admin

# oc project
Using project "openshift-infra" on server "https://<IP_ADDRESS>:8443".

# oc get pods
NAME                          READY     STATUS      RESTARTS   AGE
hawkular-cassandra-1-jst6i    1/1       Running     0          10m
hawkular-metrics-9upxv        1/1       Running     0          10m
heapster-thfmm                1/1       Running     1          10m
logging-curator-1-tx6wp       1/1       Running     0          10m
logging-deployer-rr15x        0/1       Completed   0          12m
logging-es-jg81kanm-1-lqxqs   1/1       Running     0          10m
logging-fluentd-9ocx0         1/1       Running     0          10m
logging-kibana-1-tnisp        2/2       Running     0          10m
metrics-deployer-aag8p        0/1       Completed   0          12m

The way I understand logging deployment it is the following:

There is openshift-infra project, that hosts single EFK stack but there are defined two kibana hosts and two logging services groups:

one for apps developers
second for OPS admins (anything matching *_ops*)

# oc get route
NAME                 HOST/PORT                               PATH      SERVICE                           TERMINATION   LABELS
hawkular-metrics     hawkular-metrics.apps.<IP_ADDRESS>.xip.io             hawkular-metrics:https-endpoint   reencrypt     metrics-infra=hawkular-metrics,name=hawkular-metrics
logging-kibana       kibana.apps.<IP_ADDRESS>.xip.io                       logging-kibana                    reencrypt     component=support,logging-infra=support,provider=openshift
logging-kibana-ops   kibana-ops.apps.<IP_ADDRESS>.xip.io                   logging-kibana-ops                reencrypt     component=support,logging-infra=support,provider=openshift

# oc get services
NAME                       CLUSTER-IP       EXTERNAL-IP   PORT(S)                               AGE
hawkular-cassandra         <IP_ADDRESS>      <none>        9042/TCP,9160/TCP,7000/TCP,7001/TCP   13m
hawkular-cassandra-nodes   None             <none>        9042/TCP,9160/TCP,7000/TCP,7001/TCP   13m
hawkular-metrics           <IP_ADDRESS>    <none>        443/TCP                               13m
heapster                   <IP_ADDRESS>   <none>        80/TCP                                12m
logging-es                 <IP_ADDRESS>   <none>        9200/TCP                              13m
logging-es-cluster         None             <none>        9300/TCP                              13m
logging-es-ops             <IP_ADDRESS>   <none>        9200/TCP                              13m
logging-es-ops-cluster     None             <none>        9300/TCP                              13m
logging-kibana             <IP_ADDRESS>     <none>        443/TCP                               13m
logging-kibana-ops         <IP_ADDRESS>     <none>        443/TCP                               13m

Now, in openshift console it seems that logging-kibana should be accessible at https://kibana.apps.<IP_ADDRESS>.xip.io/:

But accessing https://kibana.apps.<IP_ADDRESS>.xip.io/ in browser gives me error:

This site can’t be reached. kibana.apps.<IP_ADDRESS>.xip.io refused to connect.

My configuration of hosts:
$ cat /private/etc/hosts # (hint: I am on Mac)
<IP_ADDRESS> localhost kibana.apps.<IP_ADDRESS>.xip.io
<IP_ADDRESS>	broadcasthost
::1             localhost

When I try to connect to kibana from within the VM machine (as root) it returns 302 - Moved Temporarily:
[root@origin ~]# curl -v -s -k https://kibana.apps.<IP_ADDRESS>.xip.io
* About to connect() to kibana.apps.<IP_ADDRESS>.xip.io port 443 (#0)
*   Trying <IP_ADDRESS>...
* Connected to kibana.apps.<IP_ADDRESS>.xip.io (<IP_ADDRESS>) port 443 (#0)
* Initializing NSS with certpath: sql:/etc/pki/nssdb
* skipping SSL peer certificate verification
* SSL connection using TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
* Server certificate:
* 	subject: E=root@ip-10-35-63-192,CN=ip-10-35-63-192,OU=SomeOrganizationalUnit,O=SomeOrganization,L=SomeCity,ST=SomeState,C=--
* 	start date: Feb 24 05:56:46 2014 GMT
* 	expire date: Feb 24 05:56:46 2015 GMT
* 	common name: ip-10-35-63-192
* 	issuer: E=root@ip-10-35-63-192,CN=ip-10-35-63-192,OU=SomeOrganizationalUnit,O=SomeOrganization,L=SomeCity,ST=SomeState,C=--
> GET / HTTP/1.1
> User-Agent: curl/7.29.0
> Host: kibana.apps.<IP_ADDRESS>.xip.io
> Accept: */*
>
< HTTP/1.1 302 Moved Temporarily
< X-Powered-By: Express
< Location: https://<IP_ADDRESS>:8443/oauth/authorize?response_type=code&redirect_uri=https%3A%2F%2Fkibana.apps.<IP_ADDRESS>.xip.io%2Fauth%2Fopenshift%2Fcallback&client_id=kibana-proxy
< Content-Length: 0
< Set-Cookie: openshift-auth-proxy-session=j2r-HqX0EOQyPfJG4yqvmw.mSnU_HO3kdqaA2txjFXaHPh6YcJ2L3xhPkSQmrLzcFVpIP3wLdXohJfLKQKLsqcMmD9MzwmdNN36wxZusI4gMg.1469192238549.3600000.dzaAvaP3oEEtMT0fZVcsqUfAepyiK07nw2GIFXSUDRs; path=/; secure; httponly
< Date: Fri, 22 Jul 2016 12:57:18 GMT
< Set-Cookie: 884b5a94f1070fac466538caeec4cf7b=f052203ceec41d220adef761b846a33c; path=/; HttpOnly; Secure
<
* Connection #0 to host kibana.apps.<IP_ADDRESS>.xip.io left intact

I am kinda lost at this point, does it mean I need to provide security certs to curl command and to web browser?

@lukas-vlcek curl does not follow redirects (30x return with Location:) automatically.  You'll have to use a browser or some sort of redirect-aware client.

curl -L does

One config issue that I can see is in your /etc/hosts, try using the following entry:
<IP_ADDRESS> kibana.apps.<IP_ADDRESS>.xip.io

Openshift is running inside the guest VM, so when you are on your host machine you must access the guest VM IP address and not the localhost of the host

I've tried the latest build and although it took a while, it does finally come up.
Can you get to the cockpit app? http://cockpit.apps.<IP_ADDRESS>.xip.io/
I found that if cockpit works, then routing is working and you shouldn't have to change anything in the hosts file.  Also, mine only works with Chrome for some reason, not Edge or Firefox.  I'm a Windows user.
I did have to wait a while after everything was built for Kibana to come up.  I gave it 10min after the build, so it could download everything.
Did you check the events for the Openshift-infra project?


Create Login Page

Structure of Login Pages that can be changed and modified according to the use by the programmer.

readme.md is missing


sqldiff -a raises KeyError

Hi,
I work on Dango project (v2.2.1) with between 50-100 models (running on Postgres). I tried running a ./manage.py sqldiff -a over the project and got a KeyError exception in find_unique_missing_in_model and find_index_missing_in_model.

Thank you


chore: git connect cypress test

Description
Fixes # (issue)
Type of change
How Has This Been Tested?
Checklist:

[ ] My code follows the style guidelines of this project
[ ] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes

Test coverage results :test_tube:
:red_circle: Total coverage has decreased
// Code coverage diff between base branch:release and head branch: add-git-connect-tests

Status
File
% Stmts
% Branch
% Funcs
% Lines

:red_circle:
total
55.28 (-0.02)
37.1 (-0.04)
34.33 (-0.01)
55.79 (-0.02)

:red_circle:
app/client/src/components/designSystems/appsmith/header/DeployLinkButton.tsx
78.79 (-1.86)
84.62 (0)
16.67 (0)
77.42 (-1.89)

:red_circle:
app/client/src/pages/Editor/EditorAppName/NavigationMenuData.ts
66.67 (-0.54)
41.67 (0)
6.25 (0)
66.13 (-0.54)

:red_circle:
app/client/src/pages/Editor/gitSync/QuickGitActions/index.tsx
67.96 (-1.35)
44.44 (-1.71)
33.33 (0)
70.1 (-0.73)

:red_circle:
app/client/src/reducers/entityReducers/pageListReducer.tsx
17.65 (0)
25 (0)
15 (0)
19.57 (-0.43)

:green_circle:
app/client/src/sagas/GitSyncSagas.ts
10.21 (0.04)
0.52 (0)
5.26 (0)
13.33 (0.07)

:red_circle:
app/client/src/selectors/commentsSelectors.ts
83.61 (-1.64)
61.76 (-2.95)
73.33 (0)
88.24 (-2.35)

:red_circle:
app/client/src/selectors/gitSyncSelectors.tsx
66.9 (-4.64)
18.64 (-7.55)
15.22 (-1.06)
56.52 (-6.44)

:sparkles: :new:
app/client/src/utils/bootIntercom.ts
43.75
21.43
100
41.67

:sparkles: :new:
app/client/src/utils/getQueryParamsObject.ts
80
100
100
77.78

:red_circle:
app/client/src/utils/helpers.tsx
61.78 (0.38)
28.77 (-0.24)
45.45 (-2.38)
59 (0.36)

:red_circle:
app/client/src/utils/autocomplete/TernServer.ts
52.71 (-0.23)
40.83 (-0.84)
36.21 (0)
56.74 (-0.25)

/ok-to-test sha=3f6c3dd

/ok-to-test sha=c56b239

/ok-to-test sha=6db516b

/ok-to-test sha=5766d1d

/ok-to-test sha=c80fc42

Closing and recreating a PR


Orion  to Tessera migration documentation

Supporting documentation for Orion to Tessera migration. The actual change could be tracked here.

We already have a PR on Orion that we reviewed a lot https://github.com/ConsenSys/doc.orion/pull/65
The content looks the same to me here:

Is it worth having an identical page in both docs? Maybe just a link?
if we want both docs to have the content, maybe a copy of the one that was fully reviewed would save time.


devhint docs

consider https://devhints.io/bootstrap rather than a custom docs page?
https://devhints.io/es6 is pretty good with links to the js spec

i don't think this is quite the correct direction. was useful for inspiration, but closing


Sprint IDs are consecutive across database, not per-user

Describe the bug
A new user creating their first sprint will not start at sprint 1, but rather the next sprint ID available in the database.
To Reproduce
Steps to reproduce the behavior:

Go to an existing NoScrum instance
Click on "Tasks"
Click "Create new Sprint"
see the number isn't 1

Expected behavior
The sprint number for users should start at 1 and increment with each of their own sprints.

Created an internal method to resolve this. The display portion is fixed, although exposing this number should be part of the core API/data side.


[TH2-1950] Implemented new NoMessageCheck rule task

@OptimumOpium So if we have no messages in the interval or a missed start message from the previous task, should we still need to execute the task? In other words, is there no reason not to execute the task?

@OptimumOpium So if we have no messages in the interval or a missed start message from the previous task, should we still need to execute the task? In other words, is there no reason not to execute the task?

In my opinion, yes. We should execute the check rule event if it is started from an untrusted checkpoint. If you have doubts about that we can add a parameter that will configure the check1 to behave the way we need (fail the rule if it is started from the untrusted checkpoint without any execution or try to execute the next rule and add the failed event to the result regardless the rule succeeds or not).


Changed servlet response to greet me

Sorry about that, I just added you as a contributor. Thanks!


No need to provide args, kwargs

Closes #25

Codecov Report
Attention: 2 lines in your changes are missing coverage. Please review.

Comparison is base (9c6ab20) 50.00% compared to head (7636357) 50.00%.

Files
Patch %
Lines

nats_client/handlers.py
0.00%
2 Missing :warning:

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@           Coverage Diff           @@
##             main      #27   +/-   ##
=======================================
  Coverage   50.00%   50.00%
=======================================
  Files           6        6
  Lines         108      108
  Branches        9        9
=======================================
  Hits           54       54
  Misses         54       54

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


feat: extend ieeg models to be in_roi, if provided

Codecov Report

Merging #178 (6cde7d1) into main (f75d7b9) will increase coverage by 1.07%.
The diff coverage is 95.83%.

@@            Coverage Diff             @@
##             main     #178      +/-   ##
==========================================
+ Coverage   61.45%   62.53%   +1.07%
==========================================
  Files          32       32
  Lines        4426     4441      +15
==========================================
+ Hits         2720     2777      +57
+ Misses       1706     1664      -42

Impacted Files
Coverage Δ

siibra/features/ieeg.py
85.00% <95.65%> (+0.75%)
:arrow_up:

siibra/core/space.py
50.11% <100.00%> (+4.67%)
:arrow_up:

siibra/features/feature.py
64.82% <0.00%> (+8.69%)
:arrow_up:

:mega: Codecov can now indicate which changes are the most critical in Pull Requests. Learn more


Bagisto versioning issue

Hey there,
Nice package, had a small query regarding versioning of the same.
When, I am doing php artisan bagisto:version, then I am getting version as 1.2.0), like shown below, (I have very recently fresh installed, bagisto/bagisto-standard repository as suggested in manual,

But, when I check the same through composer (through composer show bagisto/bagisto), I am getting version as 1.1.2, like shown below,

If my repository is at v1.1.2, then help me, how can I upgrade the same to v1.2.0

@purveshclone
Hopefully, this guide will help you to upgrade the bagisto to the latest version https://devdocs.bagisto.com/1.x/introduction/upgrade_to_latest_bagisto.html

Thank you for your quick response,
Now, How can I Upgrade it through composer ?
The page although lacks proper information, but as far as i have been able to understand, it suggests, replacing the complete project files and rebuilding it. This is good, when we are not customizing the application, but what if we have customized certain modules of the application.
A complete guide is missing I guess.
And why such difference of the version in application and in composer installation?

Hi @purveshclone,
There are several ways to install a project may I know how you installed your project like cloning from git or directly downloaded the zip from the site.

Hi,
I have just installed it by creating a project through composer, as specified in the docs, like below

Hi,
As I am seeing you are using the Bagisto standard. For that, you just need to edit the file composer.json and change the version.
"bagisto/bagisto": "v1.2.0"

Before executing anything just take a backup of your whole project and DB.
Now, after editing the composer.json file have two options i..e,

Run composer update.
OR

Delete or move vendor and composer.lock file somewhere else and then run composer install.

Then after run php artisan migrate.

Then run php artisan vendor:publish --force, this will give the listing of your all modules. Just type the number which you have not customized.

Hello,
Are there any breaking changes, that I should take note of during the upgrade process?

Hi @purveshclone,
As such no breaking changes, but make sure to take all backup of your project and DB as well.
And please do the last step carefully as you have customized.

Hi @purveshclone,
Is your problem solved?

Hello,
I did the backup as specified and then ran composer update, but after its completion, I am facing following error,

Please guide me through.

Hi @purveshclone,
Just go to bootstrap/cache and delete all files except .gitignore. Then try again.

Hi,
I tried it but still getting the same error.

Hi,
Can you share your composer.json file?

Hi @devansh-webkul ,
this turns out to be a legit bug.
Steps to reproduce,

composer create-project bagisto/bagisto-standard
php artisan bagisto:install
Change version of "bagisto/bagisto" from "v1.1.2" to "v1.2.0" in composer.json
composer update (Tried with, clearing bootsrap\cache\*, deleting vendor and composer.lock as specified in the thread above.).

Solution
The error mentioned in the thread occurs, because, of Laravel's version upgrade from v6 to v7. With this upgrade, it is required for us to update App\Exceptions\Handler file, as mentioned in the docs :

First, the report, render, shouldReport, and renderForConsole methods of your application's App\Exceptions\Handler class should accept instances of the Throwable interface instead of Exception instances
I request to mention the same in the upgrade guide, as this is a breaking change.
use Throwable;

public function report(Throwable $exception);
public function shouldReport(Throwable $exception);
public function render($request, Throwable $exception);
public function renderForConsole($output, Throwable $exception);

Other problems, we encountered,

Errors relating to missing packages in dev env after doing the composer update,
1.1. Debugbar, In ProviderRepository.php line 208: Class 'Barryvdh\Debugbar\ServiceProvider' not found, when composer update is performed, within php artisan package:discovery.
1.2 Faker\Factory, In DatabaseServiceProvider.php line 88: Class 'Faker\Factory' not found' not found, when composer update is performed, within php artisan package:discovery.
The packages mentioned above were somehow removed, when composer update was triggered
Now, to solve these, I had to explicitly install the following two packages again, using,
A. composer require barryvdh/laravel-debugbar --dev
B. composer require fzaninotto/faker --dev
At last, we faced another breaking change, relating to admin login, earlier, the admin login took place at URL /admin, while, now, it's working at /login itself.

There should be a legit solution for problems we faced relating to missing packages, they should have removed ideally. Hence please, look onto the same and guide for the same.
Also, we need to update bagisto version either in .env.example from which the .env file is being generated and resulting version 1.2.0 when one does php artisan bagisto:version or bagisto\bagisto-standard's composer.json file to avoid contradictions.

Hi @purveshclone,
So, your problem is solved now.
Please refer to this thread as well https://github.com/bagisto/bagisto/pull/4227.
And all these changes have already been done in master.

Hi @purveshclone,
So, your problem is solved now.
Please refer to this thread as well https://github.com/bagisto/bagisto/pull/4227.
And all these changes have already been done in master.

Yes, the problem has now been solved.
I'd request you to please, update the upgrade guide, to contain, changes regarding L7 upgrade, and /admin URL.
Regarding packages, since, patches are being merged on regular basis, I think, we should release them as soon as possible with newer versions, like, v1.2.1, v1.2.2, etc. And should update the upgrade guide to update "bagisto\bagisto": "^1.2" instead of "bagisto\bagisto": "v1.2.0"

Yeah sure!


Master

Pull Request (PR) description
Adding supportability of empty string in ValidatePattern of EndUserSpamNotificationCustomFromAddress in ExoHostedcontentFilterPolicy. When you didn't parameter this value, it's an empty string.

This Pull Request (PR) fixes the following issues
This PR fixes:

Fixes #323

This change is

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.:x: Kiwi675 sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.

Please do PR against DEV


Cannot cannot unmarshal object into Go value of type bool on Cloud Config

Following the guidance in the docs, I attempted to pass a cloud config as a part of initializing a VM and have run aground a Go error:
xenorchestra_cloud_config.bar: Creating...
╷
│ Error: json: cannot unmarshal object into Go value of type bool
│
│   with xenorchestra_cloud_config.bar,
│   on main.tf line 32, in resource "xenorchestra_cloud_config" "bar":
│   32: resource "xenorchestra_cloud_config" "bar" {

I have tried various forms of the cloud config and tried the last few releases of this provider and am seeing it happening consistently. Here is my config, with privacy redactions.
I have also tried both loading the cloud config from file and inserting it as you see below.
I have also tried only passing hostname as the cloud config, in case any of the parameters were causing the issue.
Terraform validates the config, and I have verified that the connection to our XO is solid.
I dug around in the code for a bit to try to find the offending line, but I can't seem to make the location/stack emit with: export TF_LOG=TRACE && export TF_LOG_PATH=$(pwd)/err.log && terraform apply -- Is there a way to trace back??
Also -- the nmcli config is there only because I failed to notice that a network config could be passed as well, and I hadn't changed that yet. It was a desperate attempt to get everything working in one config.
$ terraform --version
Terraform v1.2.5
on linux_amd64
+ provider registry.terraform.io/terra-farm/xenorchestra v0.23.2

terraform {
  required_providers {
    xenorchestra = {
      source  = "terra-farm/xenorchestra"
      version = "0.23.2"
    }
  }
}

# Configure the XenServer Provider
provider "xenorchestra" {
  # Must be ws or wss
  url      = "REDACTED"             # Or set XOA_URL environment variable
  username = "REDACTED"                 # Or set XOA_USER environment variable
  password = "REDACTED" # Or set XOA_PASSWORD environment variable
  insecure = false                            # Or set XOA_INSECURE environment variable to any value
}

# Content of the terraform files
data "xenorchestra_pool" "pool" {
  name_label = "Dell-Pool"
}

data "xenorchestra_template" "template" {
  name_label = "Rocky 8.5 Cloud Ready_2022-07-21T22:51:17.898Z"
}

data "xenorchestra_network" "net" {
  name_label = "VLAN 2287 Login OpenNMS"
}

resource "xenorchestra_cloud_config" "bar" {
  name = "New Cloud Config Name"
  template = <<EOF
#cloud-config
hostname: swarmhost.dev.login.bz
users:
  - default
  - name: swarm
    sudo: ALL=(ALL) NOPASSWD:ALL
    shell: /bin/bash
    ssh_authorized_keys:
      - ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABgQDeY1SWKERJSfMSFbeAJxgtsxxi5dSk182doo6FIkFfvvULapdMXcokTbGFFhzJvYfFmyUQpiI8bnuGalshT9L9Z/xSFy1CkcKle5A4nO6RWE7e5ESDId1GBFKJzUMyxrJHci962VvH17qxMWicKNHTe3OnjYYCNaduWMCnSUpTABxGN7GGSI3EsbHt2ii5KKVuTDwepVV/0ZXpV27f0JNfOfsHY8clGt8Sg+DftReXRvUZDdmnT+f2mOC1q8dLuobL7LoxYDkW/M/WSkrJsyyume7ghhGWCYp3hUtNkE8Ro0ujXGmrr4hrTbVXIF8xgMO9RitxRVoaBXZSNVslmrTY36a3OAs4x2o5uxaGGB6a68WTAIBBgM68JlD1xV1c3YIRa2BNjpzu9K2rkKYKlV5wpcMPZ6YQwz5ZQ9myD+LA561mZ43Edup0YS9CihtwbI015JRvgvJGS48igdRL9Ay4QIQpyW91HXWpQcaD6+sCvtscwf6VTk4XqIwYzVCo0kk=
runcmd:
  - [/usr/bin/nmcli, con, mod, "System eth0", ipv4.addresses, <IP_ADDRESS>/24]
  - [/usr/bin/nmcli, con, mod, "System eth0", ipv4.gateway, <IP_ADDRESS>]
  - [/usr/bin/nmcli, con, mod, "System eth0", ipv4.dns, <IP_ADDRESS>]
  - [/usr/bin/nmcli, con, mod, "System eth0", ipv4.method, manual]
  - [/usr/bin/nmcli, con, up, "System eth0"]
EOF
}

resource "xenorchestra_vm" "bar" {
  memory_max =<PHONE_NUMBER>
  cpus       = 2

  cloud_config     = xenorchestra_cloud_config.bar.template
  name_label       = "Swarm1"
  name_description = "Swarm1 Descr"
  template         = data.xenorchestra_template.template.id
  network {
    network_id = data.xenorchestra_network.net.id
  }
  disk {
    sr_id      = "ea90dea1-99ab-c218-72b4-93abc5abebbe"
    name_label = "Swarm1 HDD"
    size       =<PHONE_NUMBER>0
  }
  // Override the default create timeout from 5 mins to 20.
  timeouts {
    create = "20m"
  }
}

Here are the errata from the log which may be pertinent:
2022-07-26T02:01:50.113Z [WARN]  Provider "registry.terraform.io/terra-farm/xenorchestra" produced an invalid plan for xenorchestra_vm.bar, but we are tolerating it because it is using the legacy plugin SDK.
    The following problems may be the cause of any confusing errors from downstream operations:
      - .videoram: planned value cty.NumberIntVal(8) for a non-computed attribute
      - .cpu_weight: planned value cty.NumberIntVal(0) for a non-computed attribute
      - .start_delay: planned value cty.NumberIntVal(0) for a non-computed attribute
      - .auto_poweron: planned value cty.False for a non-computed attribute
      - .wait_for_ip: planned value cty.False for a non-computed attribute
      - .cpu_cap: planned value cty.NumberIntVal(0) for a non-computed attribute
      - .hvm_boot_firmware: planned value cty.StringVal("bios") for a non-computed attribute
      - .core_os: planned value cty.False for a non-computed attribute
      - .exp_nested_hvm: planned value cty.False for a non-computed attribute
      - .vga: planned value cty.StringVal("std") for a non-computed attribute

2022-07-26T02:01:51.344Z [TRACE] readDiff: Read Create change from plan for xenorchestra_cloud_config.bar
2022-07-26T02:01:51.344Z [TRACE] readResourceInstanceState: reading state for xenorchestra_cloud_config.bar
2022-07-26T02:01:51.344Z [TRACE] readResourceInstanceState: no state present for xenorchestra_cloud_config.bar
2022-07-26T02:01:51.344Z [TRACE] readDiff: Read Create change from plan for xenorchestra_cloud_config.bar
2022-07-26T02:01:51.344Z [TRACE] vertex "data.xenorchestra_network.net (expand)": visit complete
2022-07-26T02:01:51.344Z [TRACE] Re-validating config for "xenorchestra_cloud_config.bar"
2022-07-26T02:01:51.344Z [TRACE] GRPCProvider: ValidateResourceConfig
2022-07-26T02:01:51.345Z [TRACE] GRPCProvider: PlanResourceChange
2022-07-26T02:01:51.345Z [TRACE] checkPlannedChange: Verifying that actual change (action Create) matches planned change (action Create)
2022-07-26T02:01:51.345Z [INFO]  Starting apply for xenorchestra_cloud_config.bar
2022-07-26T02:01:51.345Z [DEBUG] xenorchestra_cloud_config.bar: applying the planned Create change
2022-07-26T02:01:51.345Z [TRACE] GRPCProvider: ApplyResourceChange
2022-07-26T02:01:51.354Z [INFO]  provider.terraform-provider-xenorchestra_v0.23.2: 2022/07/26 02:01:51 [TRACE] Made rpc call `cloudConfig.create` with params: map[name:New Cloud COnfig Name template:#cloud-config
hostname: swarmhost.dev.login.bz
users:
  - default
  - name: swarm
    sudo: ALL=(ALL) NOPASSWD:ALL
    shell: /bin/bash
    ssh_authorized_keys:
      - ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABgQDeY1SWKERJSfMSFbeAJxgtsxxi5dSk182doo6FIkFfvvULapdMXcokTbGFFhzJvYfFmyUQpiI8bnuGalshT9L9Z/xSFy1CkcKle5A4nO6RWE7e5ESDId1GBFKJzUMyxrJHci962VvH17qxMWicKNHTe3OnjYYCNaduWMCnSUpTABxGN7GGSI3EsbHt2ii5KKVuTDwepVV/0ZXpV27f0JNfOfsHY8clGt8Sg+DftReXRvUZDdmnT+f2mOC1q8dLuobL7LoxYDkW/M/WSkrJsyyume7ghhGWCYp3hUtNkE8Ro0ujXGmrr4hrTbVXIF8xgMO9RitxRVoaBXZSNVslmrTY36a3OAs4x2o5uxaGGB6a68WTAIBBgM68JlD1xV1c3YIRa2BNjpzu9K2rkKYKlV5wpcMPZ6YQwz5ZQ9myD+LA561mZ43Edup0YS9CihtwbI015JRvgvJGS48igdRL9Ay4QIQpyW91HXWpQcaD6+sCvtscwf6VTk4XqIwYzVCo0kk=
runcmd:
  - [/usr/bin/nmcli, con, mod, "System eth0", ipv4.addresses, <IP_ADDRESS>/24]
  - [/usr/bin/nmcli, con, mod, "System eth0", ipv4.gateway, <IP_ADDRESS>]
  - [/usr/bin/nmcli, con, mod, "System eth0", ipv4.dns, <IP_ADDRESS>]
  - [/usr/bin/nmcli, con, mod, "System eth0", ipv4.method, manual]
  - [/usr/bin/nmcli, con, up, "System eth0"]
] and received false: result with error: json: cannot unmarshal object into Go value of type bool: timestamp=2022-07-26T02:01:51.354Z
2022-07-26T02:01:51.354Z [TRACE] maybeTainted: xenorchestra_cloud_config.bar encountered an error during creation, so it is now marked as tainted
2022-07-26T02:01:51.354Z [TRACE] NodeAbstractResouceInstance.writeResourceInstanceState to workingState for xenorchestra_cloud_config.bar
2022-07-26T02:01:51.354Z [TRACE] NodeAbstractResouceInstance.writeResourceInstanceState: removing state object for xenorchestra_cloud_config.bar
2022-07-26T02:01:51.354Z [TRACE] evalApplyProvisioners: xenorchestra_cloud_config.bar is tainted, so skipping provisioning
2022-07-26T02:01:51.354Z [TRACE] maybeTainted: xenorchestra_cloud_config.bar was already tainted, so nothing to do
2022-07-26T02:01:51.354Z [TRACE] NodeAbstractResouceInstance.writeResourceInstanceState to workingState for xenorchestra_cloud_config.bar
2022-07-26T02:01:51.354Z [TRACE] NodeAbstractResouceInstance.writeResourceInstanceState: removing state object for xenorchestra_cloud_config.bar
2022-07-26T02:01:51.354Z [TRACE] statemgr.Filesystem: not making a backup, because the new snapshot is identical to the old
2022-07-26T02:01:51.354Z [TRACE] statemgr.Filesystem: no state changes since last snapshot
2022-07-26T02:01:51.355Z [TRACE] statemgr.Filesystem: writing snapshot at terraform.tfstate
2022-07-26T02:01:51.495Z [ERROR] vertex "xenorchestra_cloud_config.bar" error: json: cannot unmarshal object into Go value of type bool
2022-07-26T02:01:51.495Z [TRACE] vertex "xenorchestra_cloud_config.bar": visit complete, with errors
2022-07-26T02:01:51.495Z [TRACE] dag/walk: upstream of "xenorchestra_vm.bar" errored, so skipping
2022-07-26T02:01:51.495Z [TRACE] dag/walk: upstream of "provider[\"registry.terraform.io/terra-farm/xenorchestra\"] (close)" errored, so skipping
2022-07-26T02:01:51.495Z [TRACE] dag/walk: upstream of "root" errored, so skipping
2022-07-26T02:01:51.495Z [TRACE] statemgr.Filesystem: not making a backup, because the new snapshot is identical to the old
2022-07-26T02:01:51.495Z [TRACE] statemgr.Filesystem: no state changes since last snapshot
2022-07-26T02:01:51.495Z [TRACE] statemgr.Filesystem: writing snapshot at terraform.tfstate
2022-07-26T02:01:51.499Z [TRACE] statemgr.Filesystem: removing lock metadata file .terraform.tfstate.lock.info
2022-07-26T02:01:51.499Z [TRACE] statemgr.Filesystem: unlocking terraform.tfstate using fcntl flock
2022-07-26T02:01:51.499Z [DEBUG] provider.stdio: received EOF, stopping recv loop: err="rpc error: code = Unavailable desc = transport is closing"
2022-07-26T02:01:51.500Z [DEBUG] provider: plugin process exited: path=.terraform/providers/registry.terraform.io/terra-farm/xenorchestra/0.23.2/linux_amd64/terraform-provider-xenorchestra_v0.23.2 pid=79259
2022-07-26T02:01:51.500Z [DEBUG] provider: plugin exited

This has already been fixed in #206, but there has not been a release since.
Until that is released, you can

change your XOA to the stable channel
Compile the provider yourself

Duplicate of #204
@ddelnano Can we do a release soon?

Sorry I didn't make the connnection between these. Makes sense now.
On Tue, Jul 26, 2022 at 9:01 AM Dom Del Nano @.***>
wrote:

@4censord https://github.com/4censord thanks for linking the previous
issue. I'm trying to get a release out today or tomorrow.
—
Reply to this email directly, view it on GitHub
https://github.com/terra-farm/terraform-provider-xenorchestra/issues/207#issuecomment-1195673701,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AACKXZAM2FYQMX5PY454KLTVWADUTANCNFSM54WJZNOQ
.
You are receiving this because you authored the thread.Message ID:
@.***
com>

--
John Bolthouse
https://www.linkedin.com/in/johnbolthouse
https://www.linkedin.com/in/johnbolthouse
May all our earnest efforts to accomplish anything find themselves seasoned
with salt.

This will be fixed in v0.23.3 which will be released within the next hour.


[Trappist on Rococo] Remove pallet-contracts-xcm pallet

Before deploying Trappist on Rococo i think we should remove the pallet-contracts-xcm from the runtime and remove the chain extension for XCM on the pallet_contracts::Config.  The reason behind this is because the purpose of the pallet-contracts-xcm was to provide a PoC rather than a baseline for a production ready solution. As after a couple of months, nothing was done on this pallet besides our upgrades for Trappist making me think that the project/approach is kind of discarded for now.
Also the approach about how to integrate XCM with the pallet_contracts + ink! is still under discussion and it's not even clear if chain extensions are going to be the final design decision for this purpose.
CC: @stiiifff

@stiiifff i have moved this issue to M1 since i think it is cleaner to deploy to Rococo without this chain extension configured.

Pallet removed.


Fix function and package comments

This PR updates comments for functions and packages to ensure that the names in comments and code are synchronized. See https://go.dev/doc/comment.
Additionally, it enables EXC0013 and EXC0014 to prevent these issues from recurring. revive will now flag any discrepancies.

The full list of comment issues that were fixed
❯ golangci-lint run
pkg/start/start.go:327:1: exported: comment on exported function WithWatchHostAgentTimeout should be of the form "WithWatchHostAgentTimeout ..." (revive)
// WithWatchHostAgentEventsTimeout sets the value of the timeout to use for
^
pkg/guestagent/kubernetesservice/kubernetesservice.go:25:2: exported: comment on exported const TCP should be of the form "TCP ..." (revive)
        // UDP/SCTP when lima port forwarding works on those protocols.
        ^
pkg/guestagent/api/gen.go:1:1: package-comments: package comment should be of the form "Package api ..." (revive)
//go:generate protoc --go_out=. --go_opt=paths=source_relative --go-grpc_out=. --go-grpc_opt=paths=source_relative guestservice.proto --descriptor_set_out=guestservice.pb.desc
^
pkg/store/filenames/filenames.go:11:28: exported: comment on exported const CacheDir should be of the form "CacheDir ..." (revive)
        CacheDir    = "_cache"    // not yet implemented
                                  ^
pkg/store/filenames/filenames.go:12:28: exported: comment on exported const NetworksDir should be of the form "NetworksDir ..." (revive)
        NetworksDir = "_networks" // network log files are stored here
                                  ^
pkg/store/filenames/filenames.go:13:28: exported: comment on exported const DisksDir should be of the form "DisksDir ..." (revive)
        DisksDir    = "_disks"    // disks are stored here
                                  ^
pkg/store/filenames/filenames.go:30:40: exported: comment on exported const LimaVersion should be of the form "LimaVersion ..." (revive)
        LimaVersion          = "lima-version" // Lima version used to create instance
                                              ^
pkg/store/filenames/filenames.go:39:38: exported: comment on exported const SerialLog should be of the form "SerialLog ..." (revive)
        SerialLog            = "serial.log" // default serial (ttyS0, but ttyAMA0 on qemu-system-{arm,aarch64})
                                            ^
pkg/store/filenames/filenames.go:41:39: exported: comment on exported const SerialPCILog should be of the form "SerialPCILog ..." (revive)
        SerialPCILog         = "serialp.log" // pci serial (ttyS0 on qemu-system-{arm,aarch64})
                                             ^
pkg/store/filenames/filenames.go:43:39: exported: comment on exported const SerialVirtioLog should be of the form "SerialVirtioLog ..." (revive)
        SerialVirtioLog      = "serialv.log" // virtio serial
                                             ^
pkg/store/filenames/filenames.go:57:44: exported: comment on exported const VzEfi should be of the form "VzEfi ..." (revive)
        VzEfi                = "vz-efi"           // efi variable store
                                                  ^
pkg/store/filenames/filenames.go:58:44: exported: comment on exported const QemuEfiCodeFD should be of the form "QemuEfiCodeFD ..." (revive)
        QemuEfiCodeFD        = "qemu-efi-code.fd" // efi code; not always created
                                                  ^
pkg/store/filenames/filenames.go:64:26: exported: comment on exported const Protected should be of the form "Protected ..." (revive)
        Protected = "protected" // empty file; used by `limactl protect`
                                ^
pkg/networks/const.go:5:2: exported: comment on exported const SlirpNetwork should be of the form "SlirpNetwork ..." (revive)
        // CIDR is intentionally hardcoded to <IP_ADDRESS>/24, as each of QEMU has its own independent slirp network.
        ^

I don't really like that it forces the style on exported constants and struct fields as well.
I guess I would be fine with it if it only applied to comments on a line by itself, but not to comments on the same line as the constant or field definition; it just feels redundant and eats up horizontal space, e.g.
-	SerialVirtioLog      = "serialv.log" // virtio serial
+ 	SerialVirtioLog      = "serialv.log" // SerialVirtioLog is virtio serial

I probably would feel differently if we had comprehensive comments on all exported symbols, but we don't.
I couldn't find any way to enforce the comment style only for functions. Not sure what to do now.

I don't really like that it forces the style on exported constants and struct fields as well.

I added the exclude rule and reverted changes on constants:
  # Disable revive.exported for constants.
  - text: "exported: comment on exported const"
    linters:
    - revive


IE Ajax update not updating tooltip

Hello,
I have a simple ajax update tooltip:
{
	show: {
		event: "mouseover"
	},
	hide: {
		fixed: true,
		delay: 1000,
		event: "mouseout"
	},
	style: {
		classes: 'ui-tooltip-custom ui-tooltip-shadow'
	},
	position: {
		at: "bottom right",
		my: "top right"
	},
	content: {
		text: "Laden...",
		ajax: {
			url: "ajax/file.php",
			once: false,
			type: "get"
		}
	}
}

IT works in Chrome, Firefox and Opera... but in IE (9), it get stuck when i first show it. regardless of what comes after, it appears that the tooltip doesn't update, or even make the ajax call. only a full browser refresh resets it, and then it shows the correct data once, and starts the problem from the start again.
Did i miss something or is this a issue with tooltip caching and ajax?

Remove the hide and show events, as the default options are almost identical and work better (mouseenter/mouseleave). Other than that, is there any errors being generated and if not, you'll need to produce a test case http://jsfiddle.net/fdavn

I'm unsure how to generate a Ajax call with unique content with jsfiddle. i've created the sample as it would be with my code, sans the actuall tooltip content.
http://jsfiddle.net/gNxHM/
Explained:
When mouse-overed the link, the File.php is called and fills the tooltip with data. The data in the tooltip changes depending on actions the user does on other parts of the page. So the first time they mouse-over, it would read "you have chosen option 1" and the second time, if they chose to change the chosen setting somewhere else on the page the file would send back to the tooltip "You have chosen option 2". Now, in other browsers, this updates correctly (if used with the once:false setting) on each mouse-over. In IE. it will update the proper data the FIRST time the tooltip is displayed. and no more (as if once: false was not set). subsequent mouse-over events, and even page-refreshes without a full browser refresh do not update the content of the tooltip further.
if you could tell me how to make a ajax testcase in jsfiddle, i'll gladly try to do so

Yeah this is an issue with the fact IE locally caches gets requests unfortunately. Turning cache to false is the best wy to deal with this, though sometimes even that doesn't fully work... but glad to see you figured it out.


"OpenSSL appears to be unavailable" Error

After applying the command
conda create -n echomimic python=3.8
I get the following error in the command prompt window:
Collecting package metadata (current_repodata.json): failed

CondaSSLError: OpenSSL appears to be unavailable on this machine. OpenSSL is required to
download and install packages.

Exception: HTTPSConnectionPool(host='repo.anaconda.com', port=443): Max retries exceeded with url: /pkgs/main/win-64/current_repodata.json (Caused by SSLError("Can't connect to HTTPS URL because the SSL module is not available."))

Any idea how to solve this please?

The computer is not accessed to anaconda, maybe you can change the source of conda


initial layout for the newtab page

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#961  👈
#958
#957
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @shakyShane and the rest of your teammates on  Graphite


Fix misleading instruction in app-routing-dns-ssl.md, which will make certificate never getting updated

The current version is misleading, which will cause the certificate will be always pointed to one version instead of "current" version. The certificate will never be updated due to this reason.
Already tried the following:
If set to https://<your-unique-keyvault-name>.vault.azure.net/certificates/ExampleCertificate/<version_id>, then the certificate will never be updated.
If set to https://<your-unique-keyvault-name>.vault.azure.net/certificates/ExampleCertificate, the certificate will be updated automatically.
Reference of this usage:
"You can now reference this certificate that you added to Azure Key Vault by using its URI. Use https://<your-unique-keyvault-name>.vault.azure.net/certificates/ExampleCertificate to get the current version."

Reference: https://learn.microsoft.com/en-us/azure/key-vault/certificates/quick-create-cli#add-a-certificate-to-key-vault

@MGoedtel
IMPORTANT: When the changes are ready for publication, add a #sign-off comment to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

#please-close


Add SetContext(ctx) and Context() to the gorm API

Fixes #1231
Utilizes go1.8 context support in database/sql

Picking this up again...  Is there still a wider desire to have context support?  Using context.Background() for the schema modifying functions seems reasonable to me if the desire is to preserve the existing function's API.
What about compatibility with Go versions < 1.8?  Is the goal to support that with file suffixes or will there be another release that specifically supports Go >= 1.8?
Context support is useful for controlling database timeouts, as well as instrumenting queries with metrics using something like the Zipkin which is why it would be great to have this support baked in.
Using an added WithContext function would make it transparent to existing users, similar to the way the Go http package  did it with Request.  I'm happy to help once we get some consensus...
@sarathsp06 -- regarding your comments, I also prefer calling it WithContext rather than SetContext to match the http package.  However, I don't think it helps to add a SetContext method as well.  The context docs indicate that a nil context should never be passed, so having that default to context.Background() as @remohammadi did would seem to be the right thing to do.

This PR won't be merged for now, let me think how to integrate Context into GORM in version 2.
Thanks all for your input.