Fails to install for python 3.7 under Ubuntu 20.04

Attempted to install using sudo python3.7 -m pip install pgimp.  I am developing using python3.7, not python3.8. When I run the above command, I get ERROR: Failed building wheel for pgimp.
It appears that python-fu-eval is not found. If I run a command starting with /usr/bin/gimp -idf --batch-interpreter python-fu-eval,  it hangs with the message:
GIMP-Warning: The batch interpreter 'python-fu-eval' is not available. Batch mode disabled.
Here is the output of the attempted install:
Collecting pgimp
  Using cached pgimp-1.0.0a22.tar.gz (140 kB)
Requirement already satisfied: numpy>=1.10 in /usr/local/lib/python3.7/site-packages (from pgimp) (1.19.2)
Requirement already satisfied: psutil in /usr/local/lib/python3.7/site-packages (from pgimp) (5.7.2)
Building wheels for collected packages: pgimp
  Building wheel for pgimp (setup.py) ... error
  ERROR: Command errored out with exit status 1:
   command: /usr/local/bin/python3.7 -u -c 'import sys, setuptools, tokenize; sys.argv[0] = '"'"'/tmp/pip-install-jb34kpbc/pgimp/setup.py'"'"'; __file__='"'"'/tmp/pip-install-jb34kpbc/pgimp/setup.py'"'"';f=getattr(tokenize, '"'"'open'"'"', open)(__file__);code=f.read().replace('"'"'\r\n'"'"', '"'"'\n'"'"');f.close();exec(compile(code, __file__, '"'"'exec'"'"'))' bdist_wheel -d /tmp/pip-wheel-1ht1n8ga
       cwd: /tmp/pip-install-jb34kpbc/pgimp/
  Complete output (122 lines):
  /usr/local/lib/python3.7/site-packages/setuptools/dist.py:452: UserWarning: Normalizing '1.0.0-alpha-22' to '1.0.0a22'
    warnings.warn(tmpl.format(**locals()))
  running bdist_wheel
  running build
  running build_py
  Traceback (most recent call last):
    File "/tmp/pip-install-jb34kpbc/pgimp/pgimp/GimpScriptRunner.py", line 381, in _send_to_gimp
      self._gimp_process.communicate(code.encode(), timeout=timeout_in_seconds)
    File "/usr/local/lib/python3.7/subprocess.py", line 964, in communicate
      stdout, stderr = self._communicate(input, endtime, timeout)
    File "/usr/local/lib/python3.7/subprocess.py", line 1716, in _communicate
      self._check_timeout(endtime, orig_timeout, stdout, stderr)
    File "/usr/local/lib/python3.7/subprocess.py", line 1011, in _check_timeout
      stderr=b''.join(stderr_seq) if stderr_seq else None)
  subprocess.TimeoutExpired: Command '['/usr/bin/gimp', '-i', '-d', '-f', '--batch-interpreter=python-fu-eval', '-b', '-']' timed out after 20 seconds

  During handling of the above exception, another exception occurred:

  Traceback (most recent call last):
    File "<string>", line 1, in <module>
    File "/tmp/pip-install-jb34kpbc/pgimp/setup.py", line 90, in <module>
      build_py=GimpDocumentationGeneratorCommand
    File "/usr/local/lib/python3.7/site-packages/setuptools/__init__.py", line 153, in setup
      return distutils.core.setup(**attrs)
    File "/usr/local/lib/python3.7/distutils/core.py", line 148, in setup
      dist.run_commands()
    File "/usr/local/lib/python3.7/distutils/dist.py", line 966, in run_commands
      self.run_command(cmd)
    File "/usr/local/lib/python3.7/distutils/dist.py", line 985, in run_command
      cmd_obj.run()
    File "/usr/local/lib/python3.7/site-packages/wheel/bdist_wheel.py", line 290, in run
      self.run_command('build')
    File "/usr/local/lib/python3.7/distutils/cmd.py", line 313, in run_command
      self.distribution.run_command(command)
    File "/usr/local/lib/python3.7/distutils/dist.py", line 985, in run_command
      cmd_obj.run()
    File "/usr/local/lib/python3.7/distutils/command/build.py", line 135, in run
      self.run_command(cmd_name)
    File "/usr/local/lib/python3.7/distutils/cmd.py", line 313, in run_command
      self.distribution.run_command(command)
    File "/usr/local/lib/python3.7/distutils/dist.py", line 985, in run_command
      cmd_obj.run()
    File "/tmp/pip-install-jb34kpbc/pgimp/setup.py", line 56, in run
      generate_python_skeleton()
    File "/tmp/pip-install-jb34kpbc/pgimp/pgimp/doc/GimpDocumentationGenerator.py", line 52, in __call__
      self._document_pdb_module()
    File "/tmp/pip-install-jb34kpbc/pgimp/pgimp/doc/GimpDocumentationGenerator.py", line 149, in _document_pdb_module
      methods = self._execute(pdb_dump, 20)
    File "/tmp/pip-install-jb34kpbc/pgimp/pgimp/doc/GimpDocumentationGenerator.py", line 177, in _execute
      return self._gsr.execute_and_parse_json(string, timeout_in_seconds=timeout_in_seconds)
    File "/tmp/pip-install-jb34kpbc/pgimp/pgimp/GimpScriptRunner.py", line 211, in execute_and_parse_json
      timeout_in_seconds=timeout_in_seconds,
    File "/tmp/pip-install-jb34kpbc/pgimp/pgimp/GimpScriptRunner.py", line 300, in execute
      parameters=parameters,
    File "/tmp/pip-install-jb34kpbc/pgimp/pgimp/GimpScriptRunner.py", line 384, in _send_to_gimp
      raise GimpScriptExecutionTimeoutException(str(exception) + '\nCode that was executed:\n' + code)
  pgimp.GimpScriptRunner.GimpScriptExecutionTimeoutException: Command '['/usr/bin/gimp', '-i', '-d', '-f', '--batch-interpreter=python-fu-eval', '-b', '-']' timed out after 20 seconds
  Code that was executed:
  # Copyright 2018 Mathias Burger<EMAIL_ADDRESS>  #
  # SPDX-License-Identifier: MIT

  import os
  import sys

  import gimp

  binary = bool(os.environ['__binary__'])
  stdout_file = os.environ['__stdout__']
  sys.stdout = open(stdout_file, 'w' if not binary else 'wb')
  stderr_file = os.environ['__stderr__']
  sys.stderr = open(stderr_file, 'w')

  def __exception_hook(exctype, value, traceback):
      sys.__excepthook__(exctype, value, traceback)
      sys.stderr.write('__GIMP_SCRIPT_ERROR__ {:d}'.format(1))
      gimp.pdb.gimp_quit(0)

  sys.excepthook = __exception_hook
  if '__working_directory__' in os.environ:
      os.chdir(os.environ['__working_directory__'])
  sys.path.append(os.getcwd())

  if '__PYTHONPATH__' in os.environ:
      pythonpath = os.environ['__PYTHONPATH__']
      for path_component in [x.strip() for x in pythonpath.split(':')]:
          sys.path.append(path_component)

  sys.path.append('/tmp/pip-install-jb34kpbc/pgimp')

  from collections import OrderedDict
  from pgimp.gimp.parameter import return_json

  result = OrderedDict()

  num_matches, procedure_names = pdb.gimp_procedural_db_query("", "", "", "", "", "", "")
  methods = sorted(procedure_names)
  for method in methods:
      blurb, help, author, copyright, date, proc_type, num_args, num_values = pdb.gimp_procedural_db_proc_info(method)
      result[method] = OrderedDict()
      result[method]['blurb'] = blurb
      result[method]['help'] = help
      result[method]['args'] = OrderedDict()
      result[method]['vals'] = OrderedDict()
      for arg_num in range(0, num_args):
          arg_type, arg_name, arg_desc = pdb.gimp_procedural_db_proc_arg(method, arg_num)
          if arg_name == 'run-mode':
              continue
          result[method]['args'][arg_name] = OrderedDict()
          result[method]['args'][arg_name]['type'] = arg_type
          result[method]['args'][arg_name]['desc'] = arg_desc
      for val_num in range(0, num_values):
          val_type, val_name, val_desc = pdb.gimp_procedural_db_proc_val(method, val_num)
          result[method]['vals'][val_name] = OrderedDict()
          result[method]['vals'][val_name]['type'] = val_type
          result[method]['vals'][val_name]['desc'] = val_desc

  return_json(result)

  pdb.gimp_quit(0)
  ----------------------------------------
  ERROR: Failed building wheel for pgimp

Environment:
OS: Ubuntu 20.04
Python:
python3.8 installed (/usr/bin/python3 is linked to /usr/bin/python3.8)
python3.7 installed as /usr/local/bin/python3.7 (/usr/bin/python3.7 is linked to /usr/local/bin/python3.7)
python2 installed as /usr/bin/python2.7 (/usr/bin/python2 is linked to /usr/bin/python2.7)
gimp: gimp-2.10

Me too.
I'm a beginner, so I don't know, but I got the same error on a clean install of Ubuntu.
The page I referred to is here.
[ Python , Gimp ] pgimp (Python-fuを少し使いやすくするツール) を Windows で使う – あきばこ工房
https://akibakokoubou.jp/2020/01/04/python-gimp-pgimp-gimpをpython側から使うライブラリ-を-windows-で使う/
How to Install Python Pip on Ubuntu 20.04 | Linuxize
https://linuxize.com/post/how-to-install-pip-on-ubuntu-20.04/
I hope they fix it.

Can still reproduce today, a long time after this was reported. I think it's safe to call this library deprecated/no longer maintained.

Ubuntu does not ship with python2 anymore and gimp won't have the python2 interpreter that it uses. You need to follow the same setup as on the CI, e.g. https://github.com/mabu-github/pgimp/blob/master/test/envs/linux/ubuntu/20.04/Dockerfile.


Make Hashie >= 4.0 optional

Problem
Spectre uses resque-status that in turn uses github_api that requires Hashie ~> 3.5. v3.0.0 is breaking the build in Spectre.
Solution
Make the usage of Hashie 4.0 optional.

Looks good. You'll need to relax the requirement in the gemspec too. Should we add a comment that provides a hint to when the code can be removed?

Looks good. You'll need to relax the requirement in the gemspec too. Should we add a comment that provides a hint to when the code can be removed?

Thanks @zorab47, I had forgotten to push the gem spec change. It's there now! I'll add the comment as well.


Can't resolve 'ducd' when importing module

Describe the bug
When I try to use this module from a React app after installing it with npm,
To Reproduce
Steps to reproduce the behavior:

Create a React app: npx create-react-app test
Install the module in the app: npm i d3-hypertree
Import the module in src/App.js: import * as hyt from 'd3-hypertree';
Start the app: npm start
This error appears on the console:

Failed to compile.

./node_modules/d3-hypertree/dist/js/components/hypertree/hypertree.js
Module not found: Can't resolve 'ducd' in '/Users/jude/git/test/test/node_modules/d3-hypertree/dist/js/components/hypertree'

Expected behavior
The contents of the module should be imported without error.
Screenshots
Here's the error in the browser:

Desktop (please complete the following information):

OS: macOS Catalina Version 10.15.5
Browser: Firefox 78.0.2 (64-bit)
Version: See above

Smartphone (please complete the following information):
N/A
Additional context
None
NOTE: Unfortunately, I won't be able to participate in further discussion in this thread.

Reproduced this today following instructions above.

I stumbled upon the same problem and I managed to fix it by :

cloning the repo at https://github.com/glouwa/ducd.git
downgrading my node version to 10.17.0
running npm install
running gulp build at the root of the ducd repository
copying the generated dist in the ducd folder in node_modules in my project

The explanation is that when you run npm install ducd, the package is missing the source code (there is no dist folder).
So when you require ducd, the main referenced in ducd/package.json doesn't exist and npm can't resolve the package.
Hope it helps (even if it's a bit late).


Remove trait Exhaust: Clone supertrait bound?

It turns out that several standard library types don't implement Clone; notably, std::sync::Mutex. That may not be the best example of a type to implement Exhaust, but in any case, this is evidence that trait Exhaust: Clone is not ideal.
First idea: never clone an item, but clone the iterators instead. Problem with that: a Peekable iterator only implements Clone if the item type does, since it potentially holds an item. So, the algorithm for iterator combinators would need to change.
(Itertools::cartesian_product has effectively the same requirements as our current algorithm: the left item and the right iterator must both implement Clone.)

A sketch of a solution which avoids all cloning: implementors of Exhaust produce Factorys, which are effectively functions which can be invoked repeatedly to produce items of the type. There would be a generic Factory implementation usable for clonable types.

Advantage: no more Clone bounds on either iterator or value; no unnecessary cloning except insofar as the factories are unnecessarily used in borrowed mode.
Disadvantage: Two associated types to define for every impl.

pub trait Exhaust {
    type Iter: Iterator<Item = Self::Fact>;
    type Fact: Factory<Output = Self>;

    fn exhaust_factory() -> Self::Iter;

    fn exhaust() -> MapToValue<Self::Iter> {
        self.exhaust_factory().map(|f| Self::Fact::new(Cow::Owned(f)))
    }
}

pub trait Factory {
    type Output;
    fn new(f: Cow<'_, Self>) -> Output;
}

type MapToValue<I> = core::iter::Map<I, fn(I::Item) -> I::Item::Output>;

(This would be cleaner if type_alias_impl_trait was stable since we could just use impl Fn() -> Self as the factory trait instead of a new trait.)

I wonder if the advantage of the Factory idea could be provided without complicating the trait. In particular, instead of defining <Mutex<T> as Exhaust>::Factory = MutexFactory<T>, we could say that MutexFactory<T> itself implements Exhaust, and that data types which contain Mutexes should implement their Exhaust by exhausting MutexFactory instead. The problem with this idea is that there still needs to be a way for derive(Exhaust) to pick the factory type for each field automatically, so this probably turns out to be equivalent.

I started writing out the Factory strategy, and it's really annoying that every impl must map() its natural iterator into a wrapper factory. I can't just impl<T: Clone> Factory for T because that would conflict with factories that don't want that impl.
However, it's easier if we stick to the reversed associated type relationship: Exhaust has a function that takes the Factory type and produces Self. That way, a single type can be used as factories by multiple impls, and users don't have to implement two traits, either.

Factory doesn't need to be an associated type, even; it can be the <<Self as Exhaust>::Iter as Iterator>::Item. But the redundancy may be useful for having less horrible type errors. Not sure yet.

Done in #33.


chore: release 4.0.2

:robot: I have created a release *beep* *boop*
4.0.2 (2019-08-09)
Bug Fixes

allow calls with no request, add JSON proto (4a478a7)
deps: use the latest extend (#678) (a094fdd)

This PR was generated with Release Please.

Release is at https://github.com/googleapis/nodejs-spanner/releases/tag/v4.0.2

The release build has started, the log can be viewed here. :sunflower:

:egg: You hatched a release! The release build finished successfully! :purple_heart:


Absolute magnitude patch

This is a patch to allow the results to be created when the absolute magnitude calculation fails (as described in #56). The true fix (i.e. calculating the absolute magnitude for non-DES g,r isochrones) will be more involved.

Trying to create the results with this patch still runs into an error. When the code gets to line 266, Mv has not yet been assigned and so the call fails.

See if this patch works.

It looks like we'll need to look at isochrone for the full fix


plugin version 0.4.20 doesn't actually exist

Within the examples the following line, addSbtPlugin("com.trueaccord.scalapb" % "sbt-scalapb" % "0.4.20"), doesn't download the plugin, but changing the version to 0.5.29 does work.

Can you provide the error you are getting when using 0.4.20. The binaries
for it do exist:
http://central.maven.org/maven2/com/trueaccord/scalapb/sbt-scalapb_2.10_0.13/0.4.20/
On Wed, Jun 15, 2016 at 11:12 AM, Dmitri Iourovitski <
<EMAIL_ADDRESS>wrote:

Within the examples the following line, addSbtPlugin("com.trueaccord.scalapb"
% "sbt-scalapb" % "0.4.20"), doesn't download the plugin, but changing
the version to 0.5.29 does work.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/trueaccord/ScalaPB/issues/130, or mute the thread
https://github.com/notifications/unsubscribe/AASwrVXYx_ndIi4dYhjWZc7Hr2iBS1cnks5qMECqgaJpZM4I2o-n
.

--
-Nadav

Using the configuration above, I was unable to actually download the plugin until I changed it to version 0.5.29.

Great that 0.5.29 works for you. For 0.4.20: can you provide instructions on how to reproduce the problem you are seeing so we can investigate?  If I follow the instructions http://trueaccord.github.io/ScalaPB/sbt-settings.html, things work fine.

I have an SO question pertaining to this issue, I lay out the steps I took to try and install it. I simply copy-pasted the instructions and they didn't work for me.

Resolved by upgrading SBT to 0.13.11.


Fix null trim

If relativeName() ends up returning null then the subsequent call to splitName() will pass the same into trim() which causes a deprecation warning in PHP 8.1:
trim(): Passing null to parameter #1 ($string) of type string is deprecated

firebase/vendor/google/cloud-firestore/src/PathTrait.php:178
firebase/vendor/google/cloud-firestore/src/PathTrait.php:136
firebase/vendor/google/cloud-firestore/src/CollectionReference.php:298

This PR interrupts that chain at the most logical point for an early return.

Hi @MGatner
Thanks a lot for your contribution.
Small thoughts on this. Since splitName is used from many places, it might be better to put this piece of code in the definition of splitName.
Also, since this is the exact behaviour for trim prior to PHP 8.1, it shouldn't be breaking in any way.

Hi @saranshdhingra thanks for the response!
splitName() is typed for string input only: @param string $name. So adding a null check in there doesn't make sense - the violation was the passing in of an invalid parameter. This won't affect the return value of isDocument(), it just gets there a little bit faster!
You're right that it used to be acceptable to call trim(null) but I am running on 8.1 and getting deprecation warnings that are breaking my tests.

Hey @MGatner
It does seem logical to keep the changes in the calling function for a specific case, however, this may happen for other cases too.
We could write another func where the caller may need to check for null. Hence, I think it makes sense to keep the change in the child function, ie, splitName.
We should definitely update the docbloc to accept string|null.
In fact that opens up an opportunity to add a unit test case for splitName too.
Hope this sounds reasonable :)

In my opinion adding a null case to a string helper function is a mistake because it hide potential issues upstream. There may be other functions passing null in here for very different reasons, and if those are legitimate sources then they need tests cases to cover that rather then letting splitName treat it the same as ''.
At the end of the day this is a bug that needs fixing, so if you'd rather proceed with the parameter type change on splitName I will make those updates.

I agree that this fix is better, and the more permanent fix will be to add the string type hint to this, which could be breaking so we will do this in the next major version.


Add support for ignored config

Implements https://github.com/atlassian/changesets/issues/242
@Andarist Can you please take a look? Need to add tests, but want to confirm that this approach looks reasonable to folks first.

Thanks for doing this! I will get to reviewing this soon.

Added changeset

Addressed all comments. I think the PR is ready to merge. Thanks @Andarist for your thorough review!

@Feiyang1 could you resolve conflicts?
@Noviny @mitchellhamilton could you do a second round of reviews? It would be great to land this soon!

@mitchellhamilton gentle ping

One slight problem I have found with this feature. Upgraded dependencies of ignored packages are being written to the ignored package's package.json - which is good, but when we don't ignore packages then "dependency release lines" are being appended at the end of patch release line. So this slight problem is that when we unignore a package those dependency release lines won't magically appear in the changelog so we'll have slightly different content than when not using this feature.
This, of course, is not a big deal - I don't quite care about those dependency release lines. It's just something I've noticed now.


Feature Request: Initialize .projenrc.js with commented out project options

Quality of life / convenience feature.
The idea is when .projenrc.js gets generated, it should include a list of the available options out of the box, similar to how they are provided when you run tsc --init in a new repository, which produces:
{
  "compilerOptions": {
    /* Visit https://aka.ms/tsconfig.json to read more about this file */

    /* Basic Options */
    // "incremental": true,                   /* Enable incremental compilation */
    "target": "es5",                          /* Specify ECMAScript target version: 'ES3' (default), 'ES5', 'ES2015', 'ES2016', 'ES2017', 'ES2018', 'ES2019', 'ES2020', or 'ESNEXT'. */
    "module": "commonjs",                     /* Specify module code generation: 'none', 'commonjs', 'amd', 'system', 'umd', 'es2015', 'es2020', or 'ESNext'. */
    // "lib": [],                             /* Specify library files to be included in the compilation. */
    // "allowJs": true,                       /* Allow javascript files to be compiled. */
    ...

I see that jsii is being used to generate API docs right now -- maybe there's some way to hook into that or leverage it to perform this automatically?

Yes. This idea came to mind and should be achievable.

Yes please.  As a new user I'm finding it difficult to figure out what I can do.  Any documentation help would be a plus.


Allow hiding of any right sidebar tab

The option to hide the Cards tab is great - it would be awesome if I could do this for any tab (and enforce that setting on the player's end).

Hi, you can do this using the new custom css feature in 2.0.0:

In this picture you can see the data names of the various tabs, for example cards is .item[data-tab=cards].
If you want to hide, for example, playlists, add the following:
.item[data-tab=playlists] {display: none}
to the custom CSS section in settings.
As for enforcing the setting for your players, I recommend you use a module like Force Client Settings or Module Management+.


Introduce warning topbar menu, allow following crates to see warnings for

Based on top of #2470, only the last commit is relevant currently
I still need to finish up work on grabbing data for the actual warnings, but I wanted some early feedback on the approach I'm taking to the UI, given this is the most client-side bit of UI we've got, @GuillaumeGomez.
Preview of what it looks like (with my wip warnings rendering too):

for progress this would need to be rebased


OrFeed Contract Update Core Functionality Test Suite (automated)

Currently, OrFeed's core functionality can return popular stock, ETF, and crypto prices on-chain. With all the features we are working to add (Chainlink, Augur, Band, Oracilize, more oracles, etc) and improve (and while we build out our full CI strategy mentioned in the previous issue), we need a simple test implementation that can insure before pull requests are accepted that the following functionality works on all mainnet and testnet contracts should a pull request be accepted. These include:
uint jpyusdPrice = orfeed.getExchangeRate("JPY", "USD", "DEFAULT", 100000);
// returns 920 (or $920.00)
uint price = orfeed.getExchangeRate("ETH", "USDC", "BUY-KYBER-EXCHANGE",<PHONE_NUMBER>00000);
uint price = orfeed.getExchangeRate("BTC", "DAI", "SELL-UNISWAP-EXCHANGE", 100);
uint price = orfeed.getExchangeRate("MKR", "EUR", "",<PHONE_NUMBER>00000);
uint price = orfeed.getExchangeRate("AAPL", "USD", "PROVIDER1", 1);
All of these should not return zero, and in fact return the actual price.
Basically, this core functionality should never break and we would like to automate the checking of that, for when we update the contracts referenced in the main orfeed.sol contract on all the networks.
Further, this will require an update to the readme that explains the test flow and how to check your pull requests etc.

Hey @mikedeshazer, sorry for the long delay, this was wayy tougher than I expected 😅. But still i think I've sorted it and so a few things to note about my PR.

I had to lock in the solidity version in OrFeed.sol to 0.4.26, to avoid truffle compilation errors because of deprecated statements. We'll need to update this to make it compatible with the latest compiler.
But still i'm getting lots of warning's when compiling with truffle this might also need to be fixed.
The tests for mainnet are passing for me but kovan and rinkeby not so, I think because of some of the hardcoded addresses. I will have to check on them without a rush.
I've updated the README as requested.
Finally I've also added a travis.yml file to enable ease of integration with travis-ci

In case of any issues testing, please let me know. Thanks.

Hey @mikedeshazer, sorry for the long delay, this was way tougher than I expected 😅. But still i think I've sorted it and so a few things to note about my PR.

I had to lock in the solidity version in orfeed.sol to 0.4.26, to avoid truffle compilation errors because of deprecated statements. We'll need to update the contract to make it compatible with the latest solidity compiler.
But still i'm getting lots of warnings when compiling with truffle this might also need to be fixed.
The tests for mainnet are passing for me but kovan and rinkeby not so, I think because of some of the hardcoded contract addresses for both. I will have to check on them futher.
I've updated the README as requested, with the test instructions.
I've also added a .travis.yml file to enable ease of integration with travis ci
Finally I moved the orfeed.sol file to its own separate contracts folder and then put the rest in the solidity folder to avoid alot of  compilation errors I was getting when truffle tried to compile all the files in the contracts folder.

Anyway kindly check this and in case of any issues testing, please let me know. Thanks.


Upperbound<EMAIL_ADDRESS>

bors try

bors try

For future reference you might want to add a note on why we're doing this.

For future reference you might want to add a note on why we're doing this.

I was just testing this in the PR. We can add this into #31 instead.


bb watch allows editing duration but doesn't support scheduled ending of infraction

Running
!bb watch <userid> test
!infraction edit last 10s

Will result in this error when the bot tries to end the infraction
bot_1        | Traceback (most recent call last):
bot_1        |   File "/bot/bot/utils/scheduling.py", line 119, in _await_later
bot_1        |     await asyncio.shield(coroutine)
bot_1        |   File "/bot/bot/exts/moderation/infraction/_scheduler.py", line 402, in deactivate_infraction
bot_1        |     raise ValueError(
bot_1        | ValueError: Attempted to deactivate an unsupported infraction #14 (watch)!

Along with fixing this, we may also want to support setting a duration at the time it is set as well as maybe even setting a default duration. (relevant: https://github.com/python-discord/mods/issues/4)

There is quite a lot of code for the message relaying (in https://github.com/python-discord/bot/blob/main/bot/exts/moderation/watchchannels/_watchchannel.py), so there's some benefit in having it separate to avoid having one very large cog, maybe merging them could work though, having the QoL/util functions sounds like a good reason.
I think making it having an expiry was something that was brought up a while ago as a good idea, although it might be worth discussing it again so we're sure what we want. Making it follow the same rules as other infractions sounds good. Personally I don't think i've ever used BB so would be happy to get rid of some code debt and remove it entirely, but I think some might still use it :P

Hey would love to pick this up,
Never worked on discord but I think I can do it. Is this still pending?

Hey would love to pick this up, Never worked on discord but I think I can do it. Is this still pending?

Hey 👋
Thank your for the interest in picking this up.
However, I have tried to work on this in the past, and there's currently an issue with how we deal with our infractions in general due to the design.
So I'm afraid it is currently blocked by this issue
We're still discussing what the schema will look like, etc.
I'll be happy to assign you once the previous issue has been resolved.


[Typecpec] Deserialization bug in DELETE operation

In AppConfig, the generated operation delete_key_value() will return the deleted key-value when status code is 200, or none when status code is 204 if the key-value didn't exist(Rest API link). But the generated implementation trying to deserialize return data in both cases.

Expected should be:

Shall be fixed by https://github.com/Azure/autorest.python/pull/2756


Changing a stack should be possible using previous parameter values.

When updating a stack, most of the parameters do not change and it can often be cumbersome to pass in all the same parameters that the previous stack uses, especially if it was randomly generated (e.g. a generated password for a DB instance).
The aws-cli provides a UsePreviousValue option: something similar would definitely be useful. The straight forward way would probably be to have a flag --reuse-parameters <Parameter1>,<Parameter2>,<Parameter3>....
Thoughts?

Yeah especially for passwords you only want to send in once but then keep around and not write to a config file this would be very helpful.
In general I mostly use config files to store parameters which makes it easy to pass the same ones in all the time, but for this case something else would be neat.
First thought is to make this a config file only option as it would be easier to implement and more understandable for those edge cases. I don't think I want to add another flag because that could lead to confusion when you set a value on the parameter, but then tell it to reuse the same parameter.
But I do like the feature. I'll probably not get around to it for a while, but happy to work on it if someone wants to pick it up.

In general, I'm not the biggest fan of the config file, I don't use them myself. Especially since 99% of the time, I will need to write a wrapper script anyway, it's more convenient to deploy an entire stack via the command line. Correct me if I'm wrong, but currently the config is completely optional as all features are available via the CLI, so this would introduce an inevitable need for a config file just for this option.

Not all features are available on the cli, e.g. nested vars can only be set in config files (this should be the only one at the moment). I'm typically creating config files for different environments (dev.config.yaml, staging.config.yaml) and then for shared options create a common.config.yaml. Formica allows you to load multiple config files and for them to override values, e.g. formica new -c common.config.yaml dev.config.yaml
I want the cli options to be for most common use cases, but I'm generally fine with moving some options that need more complex or nested config to config files. One thing I could think of here would be the following config file:
stack: somestack
parameters:
  SomeParameter:
    reuse: true

In general, I'm not the biggest fan of the config file, I don't use them myself. Especially since 99% of the time, I will need to write a wrapper script anyway, it's more convenient to deploy an entire stack via the command line

Would be interesting to know why you don't like the config files or need to write wrapper scripts. Really intending formica to be used by developers directly (or in some Makefile probably).

Would be interesting to know why you don't like the config files or need to write wrapper scripts. Really intending formica to be used by developers directly (or in some Makefile probably).

Most of the time, I need to lookup some ARN of some resource (e.g. certificate) and pass it as parameter. For this use case, however, I'm beginning to think it's more idiomatic to export reusable resources in a different stack so I can !ImportValue them.
Or for the "reuse", I do it "manually" with
aws cloudformation describe-stacks --output text \
  --stack-name $STACK_NAME \
  --query 'Stacks[0].Parameters[?ParameterKey==`VariableToReuse`].ParameterValue'

Also, the lack of an upsert command currently forces me to formica (change|new) variably. For the new command, I also automatically remove the stack on failure.
And since I have to do all these anyway, I don't see the value of having a config file in my repository. I might as well pass the few parameters via the command line.

For this use case, however, I'm beginning to think it's more idiomatic to export reusable resources in a different stack so I can !ImportValue them.

As long as they are in the same region then yes definitely export/import. There is one usecase when you want to use a certificate for a CloudFront distribution where the cert has to be in us-east-1 no matter where you create the CF distribution. For those cases I really think the config file (especially one for each environment) is a good tradeoff. You can store them in your repo and make it easy for anyone to come in and deploy.

And since I have to do all these anyway, I don't see the value of having a config file in my repository. I might as well pass the few parameters via the command line.

Most importantly here imho is that it documents the parameters and makes the config file usable by someone else on the team. CLI is great for quick things or when working on it only yourself, but it imho creates a situation where you could either have a typo and deploy something you don't want or somebody else doesn't know how to deploy a stack correctly.
Thats where upsert also becomes dangerous because a typo in a Parameter could mean an unstoppable change happening. With change/deploy you at least always have a step in between.

There is now (for a while) an option to use previous parameters, so I'm closing this. Thanks for reporting!


Add Cancel order

Self PR.

Need to add a test to check the keeper got paid and the account was deducted the keeper fee


WIP RF: onyo new

Code Updates:

Moves generate_faux_serial() from utils.py to new.py.
Updates existing tests so they are valid with the changes in new
Updates imports and modernizes code (e.g. uses Repo class, docstrings)
Updates argument parsing in main.py for changed onyo new

Changes in onyo new:

Instead of interactive keyboard input onyo expects the full asset name with directory path, checks it for validity and adds a faux serial number if needed
onyo new can now get one or multiple input-paths (or zero, if reading paths and asset names from a tsv file)

Codecov Report
Base: 88.76% // Head: 89.56% // Increases project coverage by +0.79% :tada:

Coverage data is based on head (2d9f4a2) compared to base (391c526).
Patch coverage: 74.35% of modified lines in pull request are covered.

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #243      +/-   ##
==========================================
+ Coverage   88.76%   89.56%   +0.79%
==========================================
  Files          21       21
  Lines        1202     1198       -4
  Branches      241      230      -11
==========================================
+ Hits         1067     1073       +6
+ Misses         93       86       -7
+ Partials       42       39       -3

Impacted Files
Coverage Δ

onyo/utils.py
97.05% <ø> (+1.50%)
:arrow_up:

onyo/commands/new.py
75.28% <73.33%> (+16.02%)
:arrow_up:

onyo/main.py
99.25% <100.00%> (+0.01%)
:arrow_up:

onyo/commands/edit.py
92.85% <0.00%> (-2.98%)
:arrow_down:

onyo/lib/onyo.py
96.63% <0.00%> (-0.02%)
:arrow_down:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


[BUG]Image chams not working again + No CrystalChams image mode

So idk if you fixed it or smng and the issue is only for me
but when I use either custom shader or image mode, it doesnt work
maybe custom shader needs a .frag or something else than a png but image mode still doesn't work.

I have not touched Image shader, I do not think it ever worked.

my shader files are already in frag format i yoinked them from another client lol
windows just denies phobos from accessing this folder i guess??

my shader files are already in frag format i yoinked them from another client lol windows just denies phobos from accessing this folder i guess??

add it to another folder, also send me them shaders 😻

Custom Shader needs a frag file with this format.
I have not touched Image shader, I do not think it ever worked.

It can't access my downloads folder


Feat/ensure async await

Resolves #https://github.com/ubiquity/ubiquibot/issues/390, https://github.com/ubiquity/ubiquibot/issues/415.
Please review the PR for both issues ^^. @pavlovcik  @rndquu

Looks solid just would prefer to change that linter config to .ts or .json

I am not sure .json would work. but the same thing that we have commitlint.config.js.


npm install does not work

Doing npm install highlight.js gives me the following result:
npm ERR! Darwin 13.4.0
npm ERR! argv "/opt/local/bin/node" "/opt/local/bin/npm" "install" "hightlight.js"
npm ERR! node v4.2.1
npm ERR! npm  v2.1.18
npm ERR! code E404

npm ERR! 404 Registry returned 404 for GET on https://registry.npmjs.org/hightlight.js
npm ERR! 404
npm ERR! 404 'hightlight.js' is not in the npm registry.
npm ERR! 404 You should bug the author to publish it (or use the name yourself!)
npm ERR! 404
npm ERR! 404 Note that you can also install from a
npm ERR! 404 tarball, folder, http url, or git url.

npm ERR! Please include the following file with any support request:
npm ERR!     /Users/ff/x/npm-debug.log

Do I miss something?

According to your log file you have a typo in the module name.

 Sorry about this and thank you very much!

NP and I should notice you that @isagalaev will release 9.0 today :+1:


Form url encoded, field param, response for callback

form-url-encoded mime type added
file/filemap options added
network response added to callback

#102 #95 #91

LGTM


Have the replicator only care about zones with 'Slave' status

Without this fix, replicator quickly deletes the zone for the Signaling Domain that is created upon ns startup. :nerd_face:

added changes, please review again


Maintenance & restore CI

This restores CI for the main branch, wrt the development version of Iris (I left out Coq 8.13 as support for it in Iris is soon going to be dropped).
I moved the github action workflow testing wrt released iris to the GH action file of the iris4.0 branch I just pushed. (I hope this makes sense GH actions-wise -- at least it seemed to work on my fork: the main and the iris4.0 branches do trigger a separate CI run for their respective GH action file.)

(it looks like I can't open a PR that would create a new branch on the repo, so I directly pushed a new iris4.0 branch to this repo, which is intended to build with the iris 4.0 released version)

This looks great, thanks Armael!


Cannot create certificate directly from ingress from different namespace than cert-manager & clusterissuer

Describe the bug:
When CertManager and ClusterIssuer are deployed in namespace cert-manager and ingress is in namespace apps, then cert-manager fails to create a certificate. The error from the certificate request is:
kubectl describe certificaterequests.cert-manager.io kafka-connect-cluster-tls-1673274601 -n apps

Failed to initialise vault client for signing: error reading Kubernetes service account token from cert-manager-token-n2llb: secret "cert-manager-token-n2llb" not found

The cert-manager-token-n2llb secret exists in the cert-manager namespace and I can authenticate to Vault using that token manually.
The ClusterIssuer is ready and the status is:
Message:            Vault verified
Reason:             VaultVerified
Status:             True
Type:               Ready

Ingress looks like this
apiVersion: extensions/v1beta1
kind: Ingress
metadata:
  annotations:
    kubernetes.io/ingress.class: internal-ingress
    cert-manager.io/cluster-issuer: vault-issuer
  labels:
    app: app
  name: kafka-connect-cluster-test
spec:
  tls:
    - hosts:
        - kafka-connect-cluster.example.com
      secretName: kafka-connect-cluster-tls
  rules:
    - host: kafka-connect-cluster.example.com
      http:
        paths:
          - backend:
              serviceName: kafka-connect-cluster
              servicePort: kafka-connect

Expected behaviour:
Certificate should have been created
Steps to reproduce the bug:
Anything else we need to know?:
When creating a certificate manually in the cert-manager namespace everything seems to work:
apiVersion: cert-manager.io/v1alpha2
kind: Certificate
metadata:
  name: example
spec:
  secretName: test-tls
  duration: 24h
  renewBefore: 12h
  commonName: angelos.example.com
  dnsNames:
    -foo.example.com
  issuerRef:
    name: vault-issuer
    kind: ClusterIssuer

but when I apply the same certificate in the apps namespace it fails again with same error as described earlier
Environment details::

Kubernetes version: v1.13.10
Cloud-provider/provisioner: EKS
cert-manager version: v0.11.0
Install method: helm

Not sure if it's a bug or if I a have misconfigured something.
/kind bug

I am having the same issue on my end but I am using Vault so the error looks like this:
 message: 'Required secret resource not found: secret "vault-approle" not found'
The vault-approle secret is within the cert-manager namespace which is different than the namespace I am trying to create the certificate in.

Confirm the Bug, I installed in a specific namespace "security", configured a ClusterIssuer with Hascicorp Vault as backend, and tried to emit a certificate in "default" namespace.
The log message is:
E1027 15:07:14.109045       1 vault.go:72] cert-manager/controller/certificaterequests-issuer-vault/sign "msg"="Required secret resource not found" "error"="secret \"cert-manager-vault-approle\" not found" "related_resource_kind"="ClusterIssuer" "related_resource_name"="vault-server-issuer" "related_resource_namespace"="" "resource_kind"="CertificateRequest" "resource_name"="vault-server-crt-3439034685" "resource_namespace"="default"

Can this issue been given priority?
Same behaviour here on k8s 1.14


Reauth after creating root groups

When a root group is created, the current Chainguard token lacks any capabilities at that new scope. Users must reauth to pick up these changes in their token.
Add support for reauth after root group creation, ambient GHA credentials for acceptance tests, and acceptance tests for creating root groups.

Adding Phil/Nghia for more eyes on the auth flow, and in case this needs consideration for any forthcoming work on refresh tokens (e.g. if we need to handle thread safety with refresh tokens?).

I'll take a look this afternoon!

I'd be fine merging as-is to the the bug tho!

we should consider adding a global lock on Chainguard's credential

Should we add locking to the token package?
https://github.com/chainguard-dev/sdk/blob/main/auth/token/token.go
I've been mulling your comment, and I don't think adding a lock in the terraform provider would resolve your concern, since resources in terraform apply aren't updated concurrently (as far as I can tell), and separate invocations of terraform apply would be using different locks. Making a local copy of the token may work, but then we'd have to copy the expiration logic (or change it in auth/token) since that's all done just by audience on the actual token. And I think then we'd need a filesystem lock, which I couldn't find a good library for that doesn't appear to be abandoned.

Should we add locking to the token package?
https://github.com/chainguard-dev/sdk/blob/main/auth/token/token.go

I think this runs into the same issue as locks in the terraform provider or chainctl, in that it would only be local to the client running, which doesn't stop other clients modifying the token concurrently

We should huddle? I don't have as much context on how terraform works here!


Adding packing plan methods to SchedulerStateManagerAdaptor

I forgot to include my changes to the adaptor in #1274.

👍

Looks good - 👍


Unexpected token C in JSON at position 0

The lamda function was able to found the video when requested, but then crash into this issue: Any suggestions? Thank you!
2017-08-10T10:09:16.713Z	f6cdcd50-7db3-11e7-8359-5f9198326baa	SyntaxError: Unexpected token C in JSON at position 0
at Object.parse (native)
at Request._callback (/var/task/index.js:96:47)
at Request.self.callback (/var/task/node_modules/request/request.js:188:22)
at emitTwo (events.js:106:13)
at Request.emit (events.js:191:7)
at Request.<anonymous> (/var/task/node_modules/request/request.js:1171:10)
at emitOne (events.js:96:13)
at Request.emit (events.js:188:7)
at IncomingMessage.<anonymous> (/var/task/node_modules/request/request.js:1091:12)
at IncomingMessage.g (events.js:292:16)
at emitNone (events.js:91:20)
at IncomingMessage.emit (events.js:185:7)
at endReadableNT (_stream_readable.js:974:12)
at _combinedTickCallback (internal/process/next_tick.js:80:11)
at process._tickDomainCallback (internal/process/next_tick.js:128:9)

Are you using your own Heroku server or are you referring to https://dmhacker-youtube.herokuapp.com?

I am referring to https://dmhacker-youtube.herokuapp.com , a video was found... but then this error occur right after which leave me kinda stuck as of what may caused the issue.

Can you give me a printout of your whole stack log? I'm going to try and reproduce this on my Alexa.

hello, thank you so much for checking. I redeployed the code on lambda to make sure I didn't made any mistake somewhere, and it works now. I probably made some mistakes O_O. I have two unrelated questions wondering if you have the answer to them.
First, does the lamda function stream to the echo or the heroku app handle that job? Because aws lamda accept 1gb out free output per month after that we may have problem.
Second, I have not very familiar with heroku deployment and wondering if you can give a somewhat detail instructions on how to setup on own heroku youtube processor app like you did?
Again thank you!

I'll answer both your questions:

The Heroku app streams the actual files. The Lambda server just returns a link to the file on the Heroku server. And, as far as I can tell, with Heroku free servers (which is what dmhacker-youtube is hosted on), you are allocated 550 hours and 2 TB of bandwidth total for all your free dynos each month. Since I'm not really running any other servers consistently, that server should be fine for now.

Sure, I'll start rewriting the setup instructions in the README to be more clear and detailed.

Thank you so much for your support!

@loctruong96 No problem! Glad I could help.


MAID-2190 fix/NFS: file modified timestamp is incorrect

Coverage increased (+0.4%) to 82.601% when pulling 85579737fc9ec25043dcfe0001561b03371e73b0 on hunterlester:MAID-2190 into 738c8b045574f2d35f91ed615790cbe632ff534c on maidsafe:master.

Coverage increased (+0.4%) to 82.601% when pulling b746f87372efe04c2b6a488655dcf0d92e241a3d on hunterlester:MAID-2190 into 738c8b045574f2d35f91ed615790cbe632ff534c on maidsafe:master.


Make Swift 3 main branch

Not sure why Swift 3 is not the master / dev branch currently?  We are well past Swift 3 release and pre-swift 3 won't even compile in Xcode 8.  Pulling from the latest on Swift 3 branch I am at version 3.0.9 while the latest version is 4.0.4.  If main branch is already Swift 3 moving forward please delete the Swift 3 branch to avoid confusion.
thanks

@abunur master is already Swift 3 / Xcode 8 compatible, so I guess you're asking for the maintainers to remove the branch feature/swift-3.0 to avoid confusion?

Yes exactly - was not sure if master was Swift 3 or not, b/c of the existence of separate Swift 3 branch still.  So please remove the branch.

I can't get the current master to work with Swift 3. I get the same error reported in https://github.com/malcommac/SwiftDate/issues/222#issuecomment-245939262
Only branch feature/swift-3.0 works for me with Carthage.

@Damnum this sounds like a different issue. Could you open a new issue with and supply the output of the following commands:
carthage version
xcode-build -version
cat Cartfile
And the command you're using to build with Carthage ie carthage update?
FYI I got both 4.0.4 and master building using carthage 0.18 and Xcode 8.0

@raven sorry my bad, it works now.
My mistake was I declared the dependency in the Cartfile like this:
github "malcommac/SwiftDate"
Because there is an old tag named "v3.0.0" in the repository, Carthage thought this was the newest tag and downloaded it.
github "malcommac/SwiftDate" ~> 4.0.4
works. But it would be helpful to rename this tag to prevent this from happening.

Ok I've removed the branch. It should now work fine.


End of year documentation

Documentation

Refine Wiki or merge into README.MD
Integrate documents in FHIR Foundry teams into git as necessary
Refine README to support users do-it-yourself with the engine

Completed


upgrade to 0.20.1 fails

i get this part way through
....
Task 705 done
  vm_types:
  - name: concourse-large
    cloud_properties:
-     spot_bid_price: 0.13
-     spot_ondemand_fallback: true
  - name: concourse-xlarge
    cloud_properties:
-     spot_bid_price: 0.27
-     spot_ondemand_fallback: true
  - name: concourse-2xlarge
    cloud_properties:
-     spot_bid_price: 0.53
-     spot_ondemand_fallback: true
  - name: concourse-4xlarge
    cloud_properties:
-     spot_bid_price: 1.07
-     spot_ondemand_fallback: true
  - name: concourse-10xlarge
    cloud_properties:
-     spot_bid_price: 2.67
-     spot_ondemand_fallback: true
+ - cloud_properties:
+     ephemeral_disk:
+       encrypted: true
+       size: 200000
+       type: gp2
+     instance_type: m5.12xlarge
+     security_groups:
+     - sg-00ec7cb724c8143b8
+   name: concourse-12xlarge
  - name: concourse-16xlarge
    cloud_properties:
-     spot_bid_price: 4.26
-     spot_ondemand_fallback: true
+ - cloud_properties:
+     ephemeral_disk:
+       encrypted: true
+       size: 200000
+       type: gp2
+     instance_type: m5.24xlarge
+     security_groups:
+     - sg-00ec7cb724c8143b8
+   name: concourse-24xlarge
  - name: compilation
    cloud_properties:
-     ephemeral_disk:
-       encrypted: true
-       size: 5000
-       type: gp2
-     security_groups:
-     - sg-00ec7cb724c8143b8
-     spot_bid_price: 0.13
-     spot_ondemand_fallback: true

  networks:
  - name: public
    subnets:
    - range: <IP_ADDRESS>/24
-     dns:
-     - <IP_ADDRESS>
  - name: private
    subnets:
    - range: <IP_ADDRESS>/24
-     dns:
-     - <IP_ADDRESS>

  stemcells:
+ - alias: xenial
+   os: ubuntu-xenial
+   version: '170.30'
- - alias: xenial
-   os: ubuntu-xenial
-   version: '97.5'

  releases:
  - name: concourse
-   sha1: dbdbb4dba48d93c073130a415b4af307816badfd
+   sha1: bf0b113a8aa48fb063c6cd39cde6107526d02517
    stemcell:
-     version: '97.5'
+     version: '170.30'
-   url: https://s3-eu-west-1.amazonaws.com/concourse-up-compiled-releases/concourse.tgz?versionId=vt5ZifmUd4HmsqNYqxFalHcTu5C5W05Y
+   url: https://s3-eu-west-1.amazonaws.com/concourse-up-compiled-releases-new/concourse-4.2.3-ubuntu-xenial-170.30-20190225-124109-642484759.tgz
-   version: 4.0.0
+   version: 4.2.3
  - name: garden-runc
-   sha1: e89b672e4f48a277cda57537c3ddd00b273a076f
+   sha1: 896f1b94ecbbc117b0a42ac0c889bcd7a7256429
    stemcell:
-     version: '97.5'
+     version: '170.30'
-   url: https://s3-eu-west-1.amazonaws.com/concourse-up-compiled-releases/garden-runc.tgz?versionId=f53fVACEfZs76tvQuPB2GuOptNHNukm8
+   url: https://s3-eu-west-1.amazonaws.com/concourse-up-compiled-releases-new/garden-runc-1.18.3-ubuntu-xenial-170.30-20190225-124157-21139916.tgz
-   version: 1.16.2
+   version: 1.18.3
  - name: riemann
-   sha1: e335be336ece7f83f682faae28a8957bc06bc277
+   sha1: a98ccebb259e446d1ea830efa811e9816536a5dc
    stemcell:
-     version: '97.5'
+     version: '170.30'
-   url: https://s3-eu-west-1.amazonaws.com/concourse-up-compiled-releases/riemann.tgz?versionId=IW2sS.efrBrd5e2bAGLunj.DJ6oMxfY4
+   url: https://s3-eu-west-1.amazonaws.com/concourse-up-compiled-releases-new/riemann-5-ubuntu-xenial-170.30-20190225-124226-242639627.tgz
  - name: grafana
-   sha1: 1a34a62c0e5e338cfac1b779c14852c3458f24ad
+   sha1: 05b4d65ed61428638f0ffcccfd14605cd75b7cb1
    stemcell:
-     version: '97.5'
+     version: '170.30'
-   url: https://s3-eu-west-1.amazonaws.com/concourse-up-compiled-releases/grafana.tgz?versionId=KJvU5vhc3ZqOslSX_ql_kp6oW2cwoaUS
+   url: https://s3-eu-west-1.amazonaws.com/concourse-up-compiled-releases-new/grafana-13.2.0-ubuntu-xenial-170.30-20190225-124242-918670614.tgz
  - name: influxdb
-   sha1: 0ebed50b3a1532ad7b63c198d98da20d48cfb00b
+   sha1: ba2d2271ba8e96cc62cc478b4717dc0717eab5fe
    stemcell:
-     version: '97.5'
+     version: '170.30'
-   url: https://s3-eu-west-1.amazonaws.com/concourse-up-compiled-releases/influxdb.tgz?versionId=sBPXBsOH5yoOYc8C.7Kv6nYKkvHiqk_L
+   url: https://s3-eu-west-1.amazonaws.com/concourse-up-compiled-releases-new/influxdb-4-ubuntu-xenial-170.30-20190225-124254-534283147.tgz
  - name: credhub
-   sha1: b9e61a2f000b530b36a82ef12725dd56f767bb37
+   sha1: 2960f6166b35052d94eb286241a56bede4d6e6f5
    stemcell:
-     version: '97.5'
+     version: '170.30'
-   url: https://s3-eu-west-1.amazonaws.com/concourse-up-compiled-releases/credhub.tgz?versionId=O82NZqcYl2gwXG47Gmfi.w3rYOBdyTJI
+   url: https://s3-eu-west-1.amazonaws.com/concourse-up-compiled-releases-new/credhub-2.1.2-ubuntu-xenial-170.30-20190225-124319-586905766.tgz
-   version: 2.0.2
+   version: 2.1.2
  - name: uaa
-   sha1: 4fb62da4a02148e9ecf7382ddbcd740e46a4c2f3
+   sha1: 8436c40c26302d00f3a05c8f320a93f81ee271d8
    stemcell:
-     version: '97.5'
+     version: '170.30'
-   url: https://s3-eu-west-1.amazonaws.com/concourse-up-compiled-releases/uaa.tgz?versionId=kR.R23UoYJrBfsR3XTr4Nfc.WkK1WZPB
+   url: https://s3-eu-west-1.amazonaws.com/concourse-up-compiled-releases-new/uaa-70.0-ubuntu-xenial-170.30-20190225-124400-918123017.tgz
-   version: '60.2'
+   version: '70.0'
+ - name: bosh-dns
+   sha1: 73714da658e1966a0b88f076aeb25fdf1911360d
+   stemcell:
+     os: ubuntu-xenial
+     version: '170.30'
+   url: https://s3-eu-west-1.amazonaws.com/concourse-up-compiled-releases-new/bosh-dns-1.10.0-ubuntu-xenial-170.30-20190225-124433-113857975.tgz
+   version: 1.10.0

  update:
-   canary_watch_time: 1000-300000
+   canary_watch_time: 1000-600000
-   update_watch_time: 1000-300000
+   update_watch_time: 1000-600000

  instance_groups:
  - name: web
    jobs:
    - name: atc
      properties:
        influxdb:
-         database: "<redacted>"
+         database: "<redacted>"
-       tls_cert: "<redacted>"
+       tls_cert: "<redacted>"
-       tls_key: "<redacted>"
+       tls_key: "<redacted>"
    - name: grafana
      properties:
        grafana:
          ssl:
-           cert: "<redacted>"
+           cert: "<redacted>"
-           key: "<redacted>"
+           key: "<redacted>"
+   - name: bosh-dns
+     properties:
+       api:
+         client:
+           tls:
+             ca: "<redacted>"
+             certificate: "<redacted>"
+             private_key: "<redacted>"
+         server:
+           tls:
+             ca: "<redacted>"
+             certificate: "<redacted>"
+             private_key: "<redacted>"
+       cache:
+         enabled: "<redacted>"
+     release: bosh-dns
  - name: worker
    jobs:
    - name: garden
      properties:
        garden:
+         no_image_plugin: "<redacted>"

  tags:
+   concourse-up-version: 0.20.1

Task 706

Task 706 | 19:32:10 | Preparing deployment: Preparing deployment (00:00:02)
Task 706 | 19:32:12 | Preparing deployment: Rendering templates (00:00:07)
                    L Error: Unable to render instance groups for deployment. Errors are:
  Blobstore object 'c0e4cc50-ebd3-4b1d-8cfa-7477153f26e9' not found
Task 706 | 19:32:19 | Error: Unable to render instance groups for deployment. Errors are:
  Blobstore object 'c0e4cc50-ebd3-4b1d-8cfa-7477153f26e9' not found

Task 706 Started  Tue Feb 26 19:32:10 UTC 2019
Task 706 Finished Tue Feb 26 19:32:19 UTC 2019
Task 706 Duration 00:00:09
Task 706 error

Updating deployment:
  Expected task '706' to succeed but state is 'error'

Exit code 1
failed to run bosh deploy with commands [/var/folders/nm/f4mbqc4d19s1x9m745_r1vx40000gn/T/concourse-up277427764/concourse.yml --vars-store /var/folders/nm/f4mbqc4d19s1x9m745_r1vx40000gn/T/concourse-up277427764/concourse-creds.yml --ops-file /var/folders/nm/f4mbqc4d19s1x9m745_r1vx40000gn/T/concourse-up277427764/versions.json --ops-file /var/folders/nm/f4mbqc4d19s1x9m745_r1vx40000gn/T/concourse-up277427764/shas.json --ops-file /var/folders/nm/f4mbqc4d19s1x9m745_r1vx40000gn/T/concourse-up277427764/cup_compatibility.yml --vars-file /var/folders/nm/f4mbqc4d19s1x9m745_r1vx40000gn/T/concourse-up277427764/grafana_dashboard.yml --ops-file /var/folders/nm/f4mbqc4d19s1x9m745_r1vx40000gn/T/concourse-up277427764/extra_tags.yml]: [exit status 1]

Hi @phynias. What version of Concourse-up are you trying to upgrade from? The diff output looks like its a big jump.
We have system tests checking upgrades but we only test consecutive releases.

not sure what version i was on, and it appears there is no way to tell what version i was coming from.
so not sure what to do from here.

also since i tried to upgrade to a way newer version it upgraded some things already.
for instance i think i found the version i was on and so i tried to upgrade to the next version. it not complains about the version of terraform being newer and fails.
if anyone can help me figure out what to do next to get this upgraded and fixed i would appreciate it.
also, maybe it would be a good idea to prevent an upgrade from even happening if the versions are not consecutive?

Based on the versions you had before in the diff you were coming from either 0.11.1 or 0.11.2 which are both from August last year. I would generally expect non-consecutive releases to work fine with upgrades (although we don't explicitly test it). We've made some major refactors since August though and pretty much all of the dependencies have bumped substantially. Its an interesting idea to put some kind of version delta limit in place though.
I'll try replicating your upgrade from 0.11.1 -> 0.20.2 tomorrow. I haven't seen your particular error before. Can you run eval "$(concourse-up info --region <your region> --env <your deployment>)"? That will export the env vars needed to interact with bosh and credhub. If that works then you can poke around with bosh to get a better feeling of what is going wrong. You could start with bosh vms to see what vms are failing bosh cck may also be able to get you out of a mess.
The simplest solution may actually be to just cut your losses and deploy a new concourse if this is acceptable given your circumstances. If that eval command works you should be able to export all the credhub secrets with credhub export -f filename.yml then import them to a new concourse with credhub import -f filename.yml. Then just set all the pipelines/teams again. The only thing you should lose is build history.

FWIW @phynias the team are working on an export/import tool, but I wouldn't wait for it.

$ bosh vms
Using environment '<IP_ADDRESS>' as client 'admin'

Task 736. Done

Deployment 'concourse'

Instance                                     Process State  AZ  IPs           VM CID               VM Type              Active
web/7a43297a-38b1-4178-a7f0-e53322cc362a     running        z1  <IP_ADDRESS>      i-0fb9000e08a026e2a  concourse-web-small  true
                                                                <IP_ADDRESS>
worker/60ad6509-a4ea-46a5-8742-1a8d9b8a3f2f  running        z1  <IP_ADDRESS>      i-09ca0986d16dd355b  concourse-xlarge     true
worker/bc9ad1a1-d8c9-4b4a-a0d5-d63dfdcad5f6  running        z1  <IP_ADDRESS>      i-0585ef4c04bc1c929  concourse-xlarge     true
worker/e577709a-f017-415f-af0e-afa082375d1f  running        z1  <IP_ADDRESS>      i-06b6591c251347f2f  concourse-xlarge     true

4 vms

Succeeded

$ bosh cck
Using environment '<IP_ADDRESS>' as client 'admin'

Using deployment 'concourse'

Task 737

Task 737 | 19:51:17 | Scanning 4 VMs: Checking VM states (00:00:12)
Task 737 | 19:51:29 | Scanning 4 VMs: 4 OK, 0 unresponsive, 0 missing, 0 unbound (00:00:00)
Task 737 | 19:51:29 | Scanning 0 persistent disks: Looking for inactive disks (00:00:00)
Task 737 | 19:51:29 | Scanning 0 persistent disks: 0 OK, 0 missing, 0 inactive, 0 mount-info mismatch (00:00:00)

Task 737 Started  Mon Mar  4 19:51:17 UTC 2019
Task 737 Finished Mon Mar  4 19:51:29 UTC 2019
Task 737 Duration 00:00:12
Task 737 done

#  Type  Description

0 problems

Succeeded

yeah. looks like i may have to destroy and rebuild it.
but it may be a good idea to put something in place to prevent the upgrade from even starting if the versions are too big. my fault for not looking but i honestly didn't even think about it.
thanks for the help!

It's curious that it's an error about a missing blobstore object.
@phynias has something happened to your blobstore bucket?

It looks like bosh still thinks everything is fine. You might be able to get a running Concourse with a deploy. bosh deploy <(bosh manifest)

so let me clarify. nothing is broken. concourse is still running fine. i just can't upgrade it.

BOSH is complaining that it can't find something in its blobstore. This is different to a general BOSH blobstore where final releases are published for the general public to use - it's the S3 bucket with blobstore and the name of your Concourse-Up deployment in it. BOSH will unpack releases (Concourse, CredHub, and others) into this blobstore bucket.
BOSH is erring when trying to render templates; presumably it's missing a blob that contains ERB templates for some of the job config. This suggests that the bucket has gone, or has been emptied. As @crsimmons suggests, doing something like bosh manifest > manifest.yml then bosh deploy -d concourse manifest.yml might prompt the BOSH Director to rebuild those blobs from the compiled releases we provide. Once that's done, then it might unblock you from upgrading.
It's the evening here in the UK, but we can look into this more in our working day tomorrow to check our assumptions.

i tried the bosh deploy and pretty much the same errors.
I will wait to see if you guys find anything tomorrow if not i will just destroy and redeploy.
thanks!

@phynias What is the state of your blobstore bucket? Has it been deleted? Have any files been deleted from it?

I've done some investigation and have replicated your issue. Essentially, somewhere between versions 0.11.1 and 0.20.1 there's a bug where namespace (introduced in 0.13.7) doesn't get templated properly into the terraform. This works if you upgrade incrementally but this big bang jump breaks things for some reason. The result is that terraform thinks the blobstore bucket name needs to be renamed from concourse-up-yourdeployment-region-blobstore to concourse-up-yourdeployment--blobstore. When terraform renames a bucket it actually deletes the old one and everything in it before making the new one. So your old blobstore got destroyed. IMO this is an edge case that we probably won't investigate further.
I did manage to get out of the broken state though, and thus was able to finish the upgrade.
TL;DR: run the following against your BOSH director then run concourse-up deploy again with the 0.20.1 binary:
bosh upload-release https://s3-eu-west-1.amazonaws.com/concourse-up-compiled-releases-new/concourse-4.2.3-ubuntu-xenial-170.30-20190225-124109-642484759.tgz --version "4.2.3" --sha1 "bf0b113a8aa48fb063c6cd39cde6107526d02517" --fix
bosh upload-release https://s3-eu-west-1.amazonaws.com/concourse-up-compiled-releases-new/garden-runc-1.18.3-ubuntu-xenial-170.30-20190225-124157-21139916.tgz --version "1.18.3" --sha1 "896f1b94ecbbc117b0a42ac0c889bcd7a7256429" --fix
bosh upload-release https://s3-eu-west-1.amazonaws.com/concourse-up-compiled-releases-new/riemann-5-ubuntu-xenial-170.30-20190225-124226-242639627.tgz --version "5" --sha1 "a98ccebb259e446d1ea830efa811e9816536a5dc" --fix
bosh upload-release https://s3-eu-west-1.amazonaws.com/concourse-up-compiled-releases-new/grafana-13.2.0-ubuntu-xenial-170.30-20190225-124242-918670614.tgz --version "13.2.0" --sha1 "05b4d65ed61428638f0ffcccfd14605cd75b7cb1" --fix
bosh upload-release https://s3-eu-west-1.amazonaws.com/concourse-up-compiled-releases-new/influxdb-4-ubuntu-xenial-170.30-20190225-124254-534283147.tgz --version "4" --sha1 "ba2d2271ba8e96cc62cc478b4717dc0717eab5fe" --fix
bosh upload-release https://s3-eu-west-1.amazonaws.com/concourse-up-compiled-releases-new/credhub-2.1.2-ubuntu-xenial-170.30-20190225-124319-586905766.tgz --version "2.1.2" --sha1 "2960f6166b35052d94eb286241a56bede4d6e6f5" --fix
bosh upload-release https://s3-eu-west-1.amazonaws.com/concourse-up-compiled-releases-new/uaa-70.0-ubuntu-xenial-170.30-20190225-124400-918123017.tgz --version "70.0" --sha1 "8436c40c26302d00f3a05c8f320a93f81ee271d8" --fix
bosh upload-release https://s3-eu-west-1.amazonaws.com/concourse-up-compiled-releases-new/bosh-dns-1.10.0-ubuntu-xenial-170.30-20190225-124433-113857975.tgz --version "1.10.0" --sha1 "73714da658e1966a0b88f076aeb25fdf1911360d" --fix

Then I was even able to upgrade to 0.20.2 successfully! The blobstore bucket name will remain a little weird (missing the region/namespace) though so if you've got the time it might still be a good idea to deploy a new one.
Essentially you need to reupload all the releases that got deleted from the blobstore. The --fix flag tells the director to overwrite releases with the same name. I got the urls and shas from the version of concourse-up-ops used to build 0.20.1 of Concourse-up. (see ops/versions-aws.json and ops/shas-aws.json in that repo).

if there is an edge case i will find it.
thanks for looking into this. i think i will redeploy though, i'd rather have a clean install.


Cluster stuck in provisioning state when creating a new cluster with the same name as the deleted cluster

Rancher versions:
rancher/server: v2.0.0-alpha27
Steps to Reproduce:

Create a 4 node cluster with name "docluster"
Delete the cluster
Create another cluster with the same name "docluster"

Results:
Cluster is stuck in provisioning state with the error
Exit status 1, I0405 01:58:10.286379 710 http.go:105] HTTP2 has been explicitly disabled I0405 01:58:10.312887 710 http.go:105] HTTP2 has been explicitly disabled W0405 01:58:25.396212 710 factory_object_mapping.go:423] Failed to download OpenAPI (an error on the server ("Error: 'EOF'\nTrying to reach: 'https://<IP_ADDRESS>:6443/swagger-2.0.0.pb-v1'") has prevented the request from succeeding), falling back to swagger Error from server (InternalError): an error on the server ("Error: 'EOF'\nTrying to reach: 'https://<IP_ADDRESS>:6443/api'") has prevented the request from succeeding

Its looking for the node <IP_ADDRESS> from the deleted cluster

Tested with master

Create a cluster with name "docluster"
Delete the cluster
Create another cluster with the same name "docluster"

Cluster creation succeeds and is operational.


[Spec] Add axes input to LRN

Adding additional (optional) input to LRN to match new spec.

Need to undo the approval, actually... I thought it was one of the "layer" ops at first as opposed to Core, so wasn't looking quite closely enough. Will give it a full review later. Still, thanks for taking this out of UnaryElementwiseArithmetic. ;)

The axes, if constant, need to be checked in type propagation, and any added checks need tests under test/type_prop.
We need to update the reference implementation in src/ngraph/runtime/reference/lrn.hpp, and update INTERPRETER to use it.
We need tests for the new functionality in test/backend/lrn.in.cpp, and these need to pass on INTERPRETER.
We need to update the other backends (at least the CPU backend) to support the new flag, OR we need to update test backend manifests and inform the backend owners that the op's semantics have changed. (Current backends will be ignoring the axes input silently.)
Serializer (maybe just the deserializer, not sure) needs to be updated for the new input.
Ideally, we should document the new functionality. (This op does not have much existing documentation, unfortunately, so perhaps we can save this for another PR.)

Thank you very much for so precise explanation.
At the moment I've implemented changes related with test new input axes (implementation + unit test) and I updated deserialization.
Working on reference LRN implementation (and changes related to it) is in progress.

@mbencer Is the work on the reference still pending?

@mbencer Is the work on the reference still pending?

@aprocter I've tried to implement reference LRN implementation. At this moment I have some problems with handling case when there are more than one axis across which LRN is calculated. When I won't be able to implement it fast (until tomorrow inclusive) I will implement other review request changes and open JIRA task as you suggested.


<location.attached_to> returning block above when placed on top

https://one.denizenscript.com/paste/55114
The output of /version on my server is: This server is running Paper version git-Paper-120 (MC: 1.14.3) (Implementing API version 1.14.3-R0.1-SNAPSHOT)
The output of /version denizen on my server is: Denizen version 1.0.6-SNAPSHOT (build 914-DEV)
The issue is:
Placing a lever, on top a block, while facing south or east will return the location above the lever instead of the one it's attached to.
Placing a button, on top a block, while facing south, east or west will return the location above the button instead of the one it's attached to.

The return value there is entirely based on Spigot MaterialData methods. If that's wrong, Spigot broke it not us.
That said, we could still replace the logic in 1.13+ with BlockData based methods (the new preferred option).

Fixed for build DEV-927+ for 1.13+ servers using modern block data.


Fix for Issue #1828

@souldreamer Pro tip: In the future, put "Fixes #number" in the pull request description to automatically close the relevant issue on merge.

@ahstro Thanks! I'll definitely do that moving forward!


Feature request: Add option to include Real Debrid

Please add Real Debrid as debrid provider
Website : https://real-debrid.com/
API docs : https://api.real-debrid.com/
Thanks in advance.

real-debrid is available.

Thanks Bro, appreciate your prompt response❤


Chapter 2 - Cannot find type 'PriorityQueue' in scope

When executing Chapter 2 on swift playground with xcode, I get the following error message
Cannot find type 'PriorityQueue' in scope
on line (according to chapter 2.2.5 A* search)
var frontier: PriorityQueue<Node<StateType>> = PriorityQueue<Node<StateType>>(ascending: true, startingValues: [Node(state: initialState, parent: nil, cost: 0, heuristic: heuristicFn(initialState))])
Swift 5.7 and Xcode Version 13.4.1 (13F100)

Sorry. I opened the playground in a wrong way. The PriorityQueue is in the Sources when cloning the GitHub and opening the playground file.


Modified scripts JUNE 01

Fixes issue:  555, 556, 557, 558, 559, 560, 561, 562, 565, 567,851, 847, 27087
Modified scripts:
ci-pics-values
ciTests.json
app1/ciTests.json
app1/config.zap
app2/config.zap
manualTests.json
PICS.yaml
TC_AUDIOOUTPUT_7_2
TC_BINFO_2_1
TC_BRBINFO_2_1
TC_CC_2_2_Simulated
TC_CC_6_5
TC_CHANNEL_5_2
TC_CHANNEL_5_3
TC_DGTHREAD_3_2_Simulated
TC_MEDIAINPUT_3_11
TC_MEDIAINPUT_3_13
TC_MOD_1_2
TC_MOD_2_1
TC_MOD_2_3
TC_MOD_3_1
TC_MOD_3_2
TC_MOD_3_4
TC_PRS_2_1
TC_PS_1_1
TC_TMP_2_1
Semi-Automated tests:
TC-DRLK-2.1
TC-DRLK-2.9
Automated tests:
TC-WNCV-2.2
TC-WNCV-2.4
TC-DRLK-2.8
Added auto generated files
Tested
Execution logs:
exe_log.txt
CC_2_2_Simulated.zip
WNCV_22_24_DRLK_22_Logs.zip

@vivien-apple @bzbarsky-apple  Test Suites - Linux (no-ble-tsan-clang) check is failing for test DRLK-2.8 for step 5 and the expected outcome is Occupied (cluster error: 0x3) script check for it and locally also it worked fine but failing for this check. Please take a look at it.

Local execution logs:
DRLK_2_8.zip

@manjunath-grl It's failing only with chip-repl, right?  Please check with @tehampson or @andy31415

I am OOO today so I will not be able to take a closer look at the moment. If there is a rush to get this in we could add that test to the list here https://github.com/project-chip/connectedhomeip/blob/master/scripts/tests/chiptest/init.py#L130 along with an issue to resolve it ASAP

@manjunath-grl can you please fix the merge conflicts?

@manjunath-grl can you please fix the merge conflicts?

@woody-apple Done rebase.


List initialization as function default parameter wiill have an extra equals sign ("=").

Pretty self-explanatory. If I have a function like this:
void take_an_vector(const std::vector<int>& input = {});

The default parameter parsed through CppAST, which is the InitExpression field of CppParameter, will show up as ={}, instead of {}.
I do not see a test of this behavior. Is this expected or by design?

I do not see a test of this behavior. Is this expected or by design?

Not expected. PR welcome to fix it. 🙂


chore: extend chiado config from gnosis config

Motivation
As noted in https://github.com/ChainSafe/lodestar/issues/6284#issuecomment-1898088566 is might better to extend the chiado config from the gnosis config instead of mainnet.
Both networks override the same mainnet values, there are of course a few values (e.g. DEPOSIT_CHAIN_ID) that chiado still needs to override but this reduces maintenance of network configs and makes overall config more robust / less error prone.
Description
Extend chiado config from gnosis config
I verified that config of both networks did not change by comparing the results of /eth/v1/config/spec. Also made sure we are still able to join the networks.
Note: This PR does not yet schedule Deneb fork on chiado (https://github.com/ChainSafe/lodestar/issues/6284)

:tada: This PR is included in v1.15.0 :tada:


Raw audio data playing JavaScript module for received audio data playing (#35)

Description
Close #35
Audio device output checking is difficult. So random-sound playing program added as test code.
Checks

Created or fixed test code
Tests can cover all features
[ ] Test support utilities added
All tests passed

Current design is not assumed network delay, means not for network streaming play.
Need to add a feature for delay allowing specification.


CLR/System.AccessViolationException in 11.0.48

Hi
a simple Hello world code in fsharp that was working in 11.0.46 is broken in 11.0.48.
The exception that I am getting is
Exception has occurred: CLR/System.AccessViolationException
An unhandled exception of type 'System.AccessViolationException' occurred in LoveSharp.dll: 'Attempted to read or write protected memory. This is often an indication that other memory is corrupt.

In my fsproj file, if I revert the dependency to 11.0.46, the same code works.
Full debug message is
-------------------------------------------------------------------
You may only use the Microsoft .NET Core Debugger (vsdbg) with
Visual Studio Code, Visual Studio or Visual Studio for Mac software
to help you develop and test your applications.
-------------------------------------------------------------------
Loaded 'C:\Users\risharan\scoop\apps\dotnet-sdk\current\shared\Microsoft.NETCore.App\3.1.2\System.Private.CoreLib.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
Loaded 'C:\Users\risharan\DevSpace\fsharp\lovely\bin\Debug\netcoreapp3.1\lovely.dll'. Symbols loaded.
Loaded 'C:\Users\risharan\scoop\apps\dotnet-sdk\current\shared\Microsoft.NETCore.App\3.1.2\System.Runtime.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
Loaded 'C:\Users\risharan\DevSpace\fsharp\lovely\bin\Debug\netcoreapp3.1\LoveSharp.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
Loaded 'C:\Users\risharan\scoop\apps\dotnet-sdk\current\shared\Microsoft.NETCore.App\3.1.2\mscorlib.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
Loaded 'C:\Users\risharan\scoop\apps\dotnet-sdk\current\shared\Microsoft.NETCore.App\3.1.2\System.Console.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
Loaded 'C:\Users\risharan\scoop\apps\dotnet-sdk\current\shared\Microsoft.NETCore.App\3.1.2\System.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
Loaded 'C:\Users\risharan\scoop\apps\dotnet-sdk\current\shared\Microsoft.NETCore.App\3.1.2\System.Diagnostics.TraceSource.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
Loaded 'C:\Users\risharan\scoop\apps\dotnet-sdk\current\shared\Microsoft.NETCore.App\3.1.2\System.Threading.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
Loaded 'C:\Users\risharan\scoop\apps\dotnet-sdk\current\shared\Microsoft.NETCore.App\3.1.2\System.Runtime.Extensions.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
Loaded 'C:\Users\risharan\scoop\apps\dotnet-sdk\current\shared\Microsoft.NETCore.App\3.1.2\System.Text.Encoding.Extensions.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
[Version: <IP_ADDRESS>]
Loaded 'C:\Users\risharan\scoop\apps\dotnet-sdk\current\shared\Microsoft.NETCore.App\3.1.2\System.Core.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
Loaded 'C:\Users\risharan\scoop\apps\dotnet-sdk\current\shared\Microsoft.NETCore.App\3.1.2\System.Linq.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
Loaded 'C:\Users\risharan\scoop\apps\dotnet-sdk\current\shared\Microsoft.NETCore.App\3.1.2\System.Collections.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
Loaded 'C:\Users\risharan\scoop\apps\dotnet-sdk\current\shared\Microsoft.NETCore.App\3.1.2\System.IO.FileSystem.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
Loaded 'C:\Users\risharan\scoop\apps\dotnet-sdk\current\shared\Microsoft.NETCore.App\3.1.2\System.Security.Cryptography.Algorithms.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
Loaded 'C:\Users\risharan\scoop\apps\dotnet-sdk\current\shared\Microsoft.NETCore.App\3.1.2\System.Security.Cryptography.Primitives.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
Loaded 'C:\Users\risharan\scoop\apps\dotnet-sdk\current\shared\Microsoft.NETCore.App\3.1.2\System.Memory.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
Fatal error. System.AccessViolationException: Attempted to read or write protected memory. This is often an indication that other memory is corrupt.
   at NativeLibraryUtil.NativlibTool.WriteToTempDir(System.String, NativeLibraryUtil.LibraryContent[])
   at NativeLibraryUtil.LibraryLoader.GetFunctionAddrLoader(NativeLibraryUtil.LibraryContent[], NativeLibraryUtil.INativeLibraryLoader)
   at NativeLibraryUtil.LibraryLoader.Load(NativeLibraryUtil.LibraryConfig)
   at Love.Boot.InitNativeLibrary()
   at Love.Boot.Init(Love.BootConfig)
   at MyGame.Program.main(System.String[])

Thank you for your feedback! I've confirmed that it's a problem occur on dotnet core(C#/F#). I'll fix it !

I just publish version of <IP_ADDRESS>-alpha, which fix the issue.
change version in ***.fsproj just like:

If everything is ok, I will release the normal version.

I can confirm that this works. On this 49-1lpha version i am no longer getting the exception.


Papilio 45 delete employee

add delete employee button beside add employee on employee dashboard

@hirsh9 You are missing the code for sending the request to the backend, you just added a button so far

I would suggest that you assign someone as a reviewer so that they are alerted of your PR to accelerate the review process. Also @AC159 as a point, you are missing the implementation to connect the backend to the UI. I think we should delete this PR and wait until all the implementation is done to have it open.

This PR is closed until the feature is completed


fix: add row_handler to schema

This PR close #450.
Signed-off-by: Yue Yin<EMAIL_ADDRESS>

Indeed this is not always correct -- row handler will only be in TableScan when there's update / delete. We can fix this when we decide on a rewrite of binder / planner / optimizer.

Indeed this is not always correct -- row handler will only be in TableScan when there's update / delete. We can fix this when we decide on a rewrite of binder / planner / optimizer.

You are right. I did not fully understand how the row handlers are created/used when I was creating this PR.

row handler will only be in TableScan when there's update / delete.

I just read the planner & executor code and this is indeed the case. However, what's the reason for creating this extra temporary "row identifier" for create/delete? Why cannot we use, say, row_id or pk?

We don't have pk. Row handler is like a row id, but row handler contains file id + row id, which means that after compaction, a record's row id could change.

We don't have pk.

Does that mean RisingLight does not store pks? I am pretty sure you can have pk when creating tables.
pub struct BoundCreateTable {
    pub database_id: DatabaseId,
    pub schema_id: SchemaId,
    pub table_name: String,
    pub columns: Vec<ColumnCatalog>,
    pub ordered_pk_ids: Vec<ColumnId>,
}

Row handler is like a row id, but row handler contains file id + row id, which means that after compaction, a record's row id could change.

So row_handler = file id + row id. Does the row_id equal to a row's index in the entire table?

No. It's the offset in the RowSet.


Interim-Technical tasks planning

Title of ticket:
Description
The purpose of this task was to plan , order possible technical tasks or tasks that are non-functional in nature, which can affect futuristic releases!.
Assumptions

Non functional technical tasks can only be planned for known/known-unknown scenarios. unknown-unknown cannot be planned at this moment of time.
The provided list is a running list of technical tasks which can be updated as more information are known as we go
The estimate on technical tasks are only a ball park due to nature of its known info at the given moment, dev team will update business  as we go!

Dependencies
Are there any dependencies? -
DOD

[x] Plan technical  tasks(functional and/or non-functional) with a possible estimate for upcoming  Records Review releases
[x] Plan technical tasks(functional and/or non-functional)  with a possible estimate for upcoming  NLP & Document Extract releases
[x] Plan technical tasks(functional and/or non-functional) with a possible estimate for upcoming  Open Information Publishing releases
[x] Plan technical tasks(functional and/or non-functional) with a possible estimate for upcoming  Decommission Axis releases
[x] Other possible tasks/ technical as per prior experience or pattern

Presented the technical tasks to business and devs and shared the spread sheet on Teams.
cc: @lmullane , @m-prodan , @liseandtea  ,
https://bcgov.sharepoint.com/:x:/r/teams/03521/Shared Documents/Development/Technical Task Projection Document review onwards.xlsx?d=w0ed1039a12784f29b7882b91c134fd88&csf=1&web=1&e=W7JTF7


How does one use espree and the ES6 functionality?

events.js:141
      throw er; // Unhandled 'error' event
            ^
Error: Parsing file *: 'import' and 'export' may appear only with 'sourceType: module' (4:0)

Is there an option to build documentation for an ES6 project? The documentation package which this supports states that it supports ES6 through espree. Does this have to be specified?

This also does not appear to be specific to gulp-documentation or documentation, but this is still a relevant issue because I have not experienced it in any other package.


Update subgraph to use current ABI

New contracts were deployed today based on the latest audit-fixes branch of core.
This PR updates the ABIs/addresses/mappings so that the subgraph won't fail while indexing the new deployments.

There are 2 new events FeeToUpdated, and FeeSwitchUpdated, that do not have ready-to-merge handlers.
Do we want to track these on the subgraph? If, not I will clean up mapping.ts and remove the handlers.
If so, I think a new entity for the schema that looks like this would be enough to track it:
type ValoremProtocol/FeeSwitch/etc @entity {
    id: ID!
    feeToAddress: Address!
    isEnabled: boolean!
}

Since I don't have access to the Subgraph Studio currently, I deployed it temporarily on the hosted service under my account.
Once it's deployed on the Studio, #168 can be marked as resolved.

@0xAlcibiades great; shall I make the FeeSwitch entity as well? Or do you have another preference?

Added feeSwitch entity and fleshed out handlers.
Note that the entity isn't created until the first time setFeesEnabled or setFeeTo is called.

Alrighty, Subgraph is working with current contracts.
After review + merge, if somebody with the proper permissions could deploy it to Subgraph Studio, I will then be able to remove my hosted service deployment from front-end config.


Add support for custom work item types in VSTS

I created custom work item type in VSTS inherited from Scrum system process, but I do not see it in the list of work item types in TfsTeamProjectManager, yet it is listed in Categories.

Custom work item types in the new "inherited" model in VSTS is not yet supported. See https://github.com/jelledruyts/TfsTeamProjectManager/issues/3 for more details.


new field search icon

I would like to see the field icons complimented with a ms-Icon--fieldSearch as drafted in the image below

Thank you for filing this, Martin! Now that we've got in in our issues list, I've gone ahead and added it to our roadmap's icon request section.


Expose current gulpfile path on gulp instancee

I am working on a tool that would enable a configuration with multiple gulpfile's.  The goal is to have each module contain it's own build information and be able to run both the module level gulpfile and a app level gulpfile.
It would be very helpful for this to know which gulpfile is the entry point.  This would enable that:
// /bin/gulp.js:116

require(env.configPath);
gutil.log('Using gulpfile', chalk.magenta(tildify(env.configPath)));

var gulpInst = require(env.modulePath);

//
// The new part
//
gulpInst.gulpfile = env.configPath;

logEvents(gulpInst);

If you guys like this I will submit a PR.

With gulp4 coming very soon, larger builds should be able to be abstracted through custom registries.
🤔


Documentation on how to use the new ImportADFS.ps1 script

Before you post
First make sure that your feature is not already in the program by browsing through the documentation.
Manual: https://www.win-acme.com/manual/getting-started
Reference: https://www.win-acme.com/reference/cli
Then make sure to search through the issue list to check if others have requested a similar feature already. If you find an existing issue, make your voice heard there. Your input may provide valueable extra information towards desiging a fitting solution and will increase its priority.
Is your feature request related to a problem? Please describe.
We don't have a documentation about running the new ImportADFS.ps1 script
Describe the solution you'd like
A new documentation page about how to run this script and configure win-acme on ADFS servers.
Describe alternatives you've considered
I figured it by myself, but I'm not sure if the command was right, I get some inspiration from the Exchange.ps1 script:
./wacs.exe --target manual --host hostname.example.com,adfs.example.com,sts.example.com --installation iis,script --installationsiteid 1 --script ".\Scripts\ImportADFS.ps1" --scriptparameters "'{CertThumbprint}'" --certificatestore My --acl-fullcontrol "network service,administrators"
But I'm not sure if I really needed the ACL setting.
Additional context
The solution appear to be worked as expected.

I've added the full command line example to the script itself, thanks for the suggestion!


% chance or items in a table

Might already be a feature I'm just missing. But a % chance for each item on the table ie 100 actors and a % chance they are in a tavern for a patron generator:

actor 1  10%
actor 2  30%
actor 3  40%

Add this feature on 2.0.24 try out and let me know it

Unable to load the mod getting
better-rolltables| Spell cache could not be initialized/updated.

this is with shadowdark rpg havent checked the others yet

shadow dark rpg has not a supported spell cache. i need the string key of the compendium:


Update Settings “general”

Automatically generated by Netlify CMS

👷 Deploy Preview for eloquent-trifle-1eb8df processing.

Name
Link

🔨 Latest commit
3657fc501fbc0ccd2b0e33c868182b93138bdc6c

🔍 Latest deploy log
https://app.netlify.com/sites/eloquent-trifle-1eb8df/deploys/64b939ecf7f9e700082479a1


fix Merge Files

Merge the files so we don't have to keep a backup of the code in the main repo.

looks ass


"feat: Square Pegs, Round Holes: Reshaping OKRs for Hard Tech Startups"

""

:tada: This PR is included in version 1.65.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Start language specification

What was wrong?
As stated in #40 we need to start writing a language specification.
How was it fixed?
Not fixed but wanted to break ground after implementing the arithmetic operations.
To-Do

[x] Clean up commit history

This is heavily influenced by https://doc.rust-lang.org/stable/reference/expressions/operator-expr.html

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@6105ecf). Click here to learn what that means.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master      #50   +/-   ##
=========================================
  Coverage          ?   70.08%
=========================================
  Files             ?       29
  Lines             ?     2056
  Branches          ?        0
=========================================
  Hits              ?     1441
  Misses            ?      615
  Partials          ?        0

Impacted Files
Coverage Δ

compiler/src/yul/namespace/scopes.rs
82.97% <0.00%> (ø)

compiler/src/abi/elements.rs
89.28% <0.00%> (ø)

compiler/src/abi/builder.rs
86.51% <0.00%> (ø)

parser/src/errors.rs
59.15% <0.00%> (ø)

parser/src/builders.rs
98.82% <0.00%> (ø)

compiler/src/yul/mappers/types.rs
50.00% <0.00%> (ø)

compiler/src/yul/runtime/abi.rs
30.76% <0.00%> (ø)

compiler/src/errors.rs
0.00% <0.00%> (ø)

parser/src/tokenizer/regex.rs
100.00% <0.00%> (ø)

parser/src/lib.rs
100.00% <0.00%> (ø)

... and 19 more

Continue to review full report at Codecov.

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

@g-r-a-n-t are you ok to merge this? I think we can just continue go make changes to this document over time to build out the specification piece by piece.


dev-docs: Documentation is empty

Component/platform: dev-docs
Description of problem:
The sphinx-build for the developer docs is broken ATM. The autoclass statements do not generate any documentation. See:
https://dev-docs.home-assistant.io/en/master/api/core.html
(empty content)

I was trying to track down the issue but didn't solve it. Thanks for bringing it up again.

Since building documentation locally seems to work, how could I try to help with this?
Who builds and publishes the documentation? Travis? A script somewhere?

ReadTheDocs builds seems to be having problems reading majority of the files.
reading sources... [ 11%] api/bootstrap
reading sources... [ 22%] api/core
reading sources... [ 33%] api/device_tracker
reading sources... [ 44%] api/entity
reading sources... [ 55%] api/event
reading sources... [ 66%] api/helpers
reading sources... [ 77%] api/homeassistant
reading sources... [ 88%] api/util
reading sources... [100%] index

Looks like readthedocs is running python 3.5.2 which doesn't have Coroutine. Seems like it's available in 3.5.3. I'm trying to see if I can tell readthedocs which python version I want.

PR coming

As a note the yml file can't parse patch versions so I had to put the python version to 3.6.


UI: Better to have Image Preview for cover uploading

As following:

No cover preview even i have already uploaded the image.

/assign @Baihhh

Fixed.


onwarn in svelte.config.js does not work with Svelte v4.2.0

Describe the bug
I just upgraded from Svelte 3.59.2 to 4.2.0 and noticed a regression issue (since it was the only change)...
This was working as expected in v3.59.2 (warnings suppressed):
import sveltePreprocess from 'svelte-preprocess';

export default {
  preprocess: sveltePreprocess(),
  onwarn: (warning, handler) => {
    if (warning.code.startsWith('a11y-')) {
      return;
    }
    handler(warning);
  },
};

After upgrading to v4.2.0, the code above no longer works and warnings are still shown in VS Code.
Reproduction URL
N/A (vite.new doesn't show warnings)
Reproduction

Add code above to svelte.config.js
Update package.json: "svelte": "^4.2.0",
npm install
Reload VS Code
Edit a .svelte file that would trigger an a11y warning, e.g.: <label tabindex="0" on:click={() => console.log('test')}>Test</label>

Logs
No response
System Info
System:
    OS: Windows 10 10.0.19045
    CPU: (8) x64 Intel(R) Core(TM) i7-7700HQ CPU @ 2.80GHz
    Memory: 15.92 GB / 31.95 GB
  Binaries:
    Node: 16.20.0 - C:\Program Files\nodejs\node.EXE
    Yarn: 1.22.19 - C:\Program Files\nodejs\yarn.CMD
    npm: 8.19.4 - C:\Program Files\nodejs\npm.CMD
    pnpm: 8.6.6 - ~\AppData\Local\pnpm\pnpm.EXE
  Browsers:
    Edge: Spartan (44.19041.1266.0), Chromium (116.0.1938.69)
    Internet Explorer: 11.0.19041.1566
  npmPackages:
    @sveltejs/vite-plugin-svelte: ^2.4.5 => 2.4.5
    svelte: ^3.59.2 => 3.59.2
    vite: ^4.4.9 => 4.4.9

I can't reproduce this locally.

see https://github.com/sveltejs/svelte/issues/9175#issuecomment-1704555547
vite-plugin-svelte handles onwarn for it's own logging, but it cannot control what the vscode extension does.

I originally submitted issue in Svelte repo, but they said it might be related to this module, that's why I submitted it here. I managed to set up an environment for you to reproduce the issue. Steps:

Go to https://prod.liveshare.vsengsaas.visualstudio.com/join?2A35FC729177C50139EBE3BBD0DD762947B0
Install Svelte for VS Code extension
There should be no warnings.
Update package.json: "svelte": "^4.2.0",
In terminal: npm install
In VS Code: Ctrl + Shift + P -> "Svelte: Restart Language Server"
ISSUE: You should see a11y warning.

Your reproduction describes that the warning is shown by vscode. vite-plugin-svelte is not responsible for this.
please stop crossposting
https://github.com/sveltejs/language-tools/issues/2149#issuecomment-1705845910


Fix 'Fetches' example in basic_usage

need ‘as sess’ to be executed.

Thanks for the PR!  I think this was independently fixed in a commit earlier this week -- we appreciate the effort.


lino_msgs i can not use lino_msgs in cpp

ros error  lino_msgs/Imu.h: No such file or directory
compilation terminated.
ros doesn't know lino_msgs header file
but Arduino ok.
Cmakelist, where i have to add library lino_msgs header file .
thy.

@tossapon14 you can do it:
cd ~<your_ws>/src
git clone https://github.com/linorobot/lino_msgs
cd ..
catkin_make


Improve wording on delete access token modal

Fixes #3589, Follow-up of #19894.
This PR highlights the nature of the destructive action.
It also rewords the action buttons to remove ambiguity.
Signed-off-by: André Jaenisch<EMAIL_ADDRESS>

The comments left in #19894 should be removed.

#19921


Upgrade Truth 1.1.4 -> 1.1.5

This PR contains the following updates:

Package
Type
Update
Change

Truth
compile
patch
1.1.4 -> 1.1.5

Release Notes

google/truth
v1.1.5
Compare Source

[ ] If you want to rebase/retry this PR, check this box

Warning
Renovate's suggested commit message is being replaced with improved initial commits to enable automerging. As a side effect, these suggested commit messages might have changed. Consider comparing the initial commit message and this message to determine the most suitable one. Please leave feedback in #sys-renovate.

Suggested commit message:
Upgrade Truth 1.1.4 -> 1.1.5

See https://github.com/google/truth/compare/v1.1.4...v1.1.5


support carton in every environment

This PR aims at extending carton in every environment: npm, pnpm, bun and yarn.

Thanks for getting this started! This is definitely the next step.
I would be surprised if the current approach works, however, since "dist" is not in astro.packageJson.exports.

Yeah, the approach doesn't work.

(The way you have to test it is by creating a tarball with pnpm pack.)
No worries, though, I already know a way it could work.

Thanks for the quick review!

No worries, though, I already know a way it could work.

May you help me with that? I'd love to contribute and learn!

woah, I didn't know import.meta.resolve('module') was an API

Just needs a changeset and readme update now.

Sure, on it
Curious, does import.meta.resolve('node:crypto') work in similar fashion? what if node:crypto is not available?

@lilnasy
Updated the README and added changeset

Curious, does import.meta.resolve('node:crypto') work in similar fashion? what if node:crypto is not available?

Just tried it and it just returns "node:crypto" unchanged.

My pleasure!


Independent of dependency version, serve it if requested

Even if the htmldependency version is higher or lower, the HTML being sent to the user is requesting THIS dependency. Therefore, it should be available to the user independent of any previous versions of the dependency being served.
{htmltools} does de-duplicate dependencies and finds the highest version to return. However, dynamic UI and callable UI do not run through the same filter over time. When using callable UI functions, UI dependencies are reset
on refresh. So if a dependency makes it here, it is not necessarily the highest version served over time but is the highest version for this particular UI. Therefore, serve it must be served.

Needs #441 to test properly

I'd like to understand this one, maybe we can talk tomorrow?