polybar: add module

This module can be used only to configure polybar, but it doesn't start the bars.
The problem with launch is that it might require setting some environment variables depending on the user's configuration.
For example, this is the script I use to run my bar on all screens:
#!/usr/bin/env bash

killall -q polybar

while pgrep -u $UID -x polybar >/dev/null; do sleep 1; done

PRIMARY_MONITOR=`xrandr | grep "primary" | cut -d " " -f1`
MONITOR=$PRIMARY_MONITOR TRAY_POSITION=right polybar bar &

EXTRA_MONITORS=`xrandr | grep " connected" | grep -v $PRIMARY_MONITOR | cut -d " " -f1`
for MONITOR in $EXTRA_MONITORS; do
    MONITOR=$MONITOR polybar bar &
done

echo "Bars launched..."

I wonder if it would be sufficient to have a script option of type str that by default contains a very basic start-up command, maybe simply script = "${cfg.package}/bin/polybar"? Then create a systemd.user.services.polybar roughly like
systemd.user.services.polybar = {
  Unit = {
    Description = "Polybar desktop bar";
    After = [ "graphical-session-pre.target" ];
    PartOf = [ "graphical-session.target" ];
  };

  Service = {
    Type = "forking";
    Environment = "PATH=${cfg.package}/bin";
    ExecStart = pkgs.writeShellScriptBin "polybar-start" cfg.script;
  };

  Install = {
    WantedBy = [ "graphical-session.target" ];
  };
};

It should be then possible to override script for more advanced setups (like yours), with any luck systemd will be able to track all running polybars and stop them when the X session terminates :-)
Just a wild idea, I'm not certain it will work in practice…

Thank you for the suggestions, it made the module much cleaner and better!

Added news entry
Fixed examples
Implemented and tested your suggestion with include-file
Created systemd service as you suggested

pkgs.writeShellScriptBin is not working properly right now (see https://github.com/NixOS/nixpkgs/pull/30153), so used pkgs.writeScriptBin for now.
Tested service start on this config:
    startScript = ''
      #!${pkgs.bash}/bin/bash
      PATH=$PATH:${pkgs.i3-gaps}/bin:${pkgs.xorg.xrandr}/bin:${pkgs.gnugrep}/bin:${pkgs.coreutils}/bin

      PRIMARY_MONITOR=`xrandr | grep "primary" | cut -d " " -f1`
      MONITOR=$PRIMARY_MONITOR TRAY_POSITION=right polybar bar &

      EXTRA_MONITORS=`xrandr | grep " connected" | grep -v $PRIMARY_MONITOR | cut -d " " -f1`
      for MONITOR in $EXTRA_MONITORS; do
          MONITOR=$MONITOR polybar bar &
      done
    '';

Works as it should, even with multiple screens. It would be also neat if home-manager would suggest restarting the service on polybar config file changes.

Unfortunately, we can't set a default value for startScript parameter since it requires the name of the bar defined in the configuration file.

Nice work! I added a few final minor comments. Generally I think this is good to merge 👍

It would be also neat if home-manager would suggest restarting the service on polybar config file changes.

Yes indeed! Unfortunately this is a bit tricky but I dearly hope that the future NixUP work will make it possible for us to use the NixOS systemd module and its nice restartTriggers option. I suppose some custom solution could be made here, basically you could to do something like what is done for the xmonad module but instead of doing xmonad --restart do systemctl --user restart polybar…

Again, thank you for the comments!
Fixed everything you mentioned and implemented polybar service restart in the similar way as it's done for xmonad. Let me know if you think it's too hacky.
As for the script, I'm now adding shebang automatically since writeShellScriptBin is now fixed in master branch and once it will get to 17.09 (not sure when it will happen though), we can easily replace writeScriptBin with writeShellScriptBin without users noticing.

Looks fine to me! I added one final comment but then feel free to merge once you are ready. Thanks!
I might look at some more general restart trigger mechanism but i think this is OK for now.

Changed to reloadSystemD and rebased into master: https://github.com/rycee/home-manager/commit/469caa1a1405b22a849f60280ca4bdaec2f3289b


Error "Could not unzip the archive of" for kotlin 1.0.3+ and sbt 0.13.11

Utils.ps1 fails here:
if ( !(Test-Path "$Script:PGVM_TEMP_PATH\*-$Version") ) {
		throw "Could not unzip the archive of $Candidate $Version. Please delete archive from $Script:PGVM_ARCHIVES_PATH (or delete all with 'gvm flush archives'"
}

Because sbt and kotlin archives don't have version numbers in inner folders. Moreover, kotlin's folder name  is "kotlinc".

Just installed and tried posh-gvm for the first time, to try installing Kotlin 1.1 preview releases alongside stable 1.0.x and encountered the same error.
Any news on this?

@calexHG workaround is to manually rename downloaded archive in PGVM_TEMP_PATH folder and add version to its name like kotlin-1.1. After that you can rerun gvm install. Worked for me.

@shambalaxx Thanks for helping him.
Further work on posh-gvm is on my (overcrowded) todo list. I somehow need to find free time for it. At my work its seldomly used anymore after more and more devs here started to use the new windows subsystem.

@shambalaxx thanks! I may try that later and see if it works.
@flofreud ahhhh — well that makes sense.
I'm still on Windows 8.1, however, as I still haven't heard anything about why I should want Win 10, yet frequently hear about why I would want to avoid it.
The early demo video regarding "Bash on Windows" was interesting until the demonstrator explained roughly that it can't really interoperate with the outside world or something like that (it was a while ago).


feat(Codebytes): add editor and drawers disc 351

Overview

PR Checklist

[x] Related to JIRA ticket: DISC-352
[x] I have run this code to verify it works

This pull request is part of a series of pull requests to migrate the codebytes UI to client modules. The component structure thus far is:
CodebyteEditor
   > Editor
       > Drawers

This pull request migrates the Editor and Drawers components.
In CodebyteEditor, the <EditorContainer /> wraps the Editor with basic styles. We also now pass language and hideCopyButton as props, in case we want to hide the copy button on any page we render it from.
The <Editor /> component contains the following changes from static sites:

adds a Response type (interface) for the response given by the snippets endpoint (line 45)
renders dummy text in place of the Monaco Editor for now (line 123)
uses a more simple and more generic onCopy function when the copy button is clicked. This will be the default behavior. for the Next.js behavior, we'll need to pass in the CopyBBCodeblock which is specific to forums. (line 66)

The <Drawers /> component is identical to the component in static sites. No changes at all since it's just UI.
The CodebyteEditorStories.mdx now imports a number of things that are used to render Gamut styles properly (GamutProvider, AssetProvider, AppWrapper). Followed this example from the static sites repo.

Please note!: I do not expect us to be able to run code in this pr, nor get a response from the Snippets Endpoint. That will come in an upcoming pr when Monaco is added to run code!
Tests for the full Codebytes component to come at the end.

PR Checklist
To see the component locally:

Checkout the branch. Run yarn.
In the root, run "yarn start". This will start the storybook server. Visit http://localhost:6006/

📬Published Alpha Packages:@codecademy/codebytes@0.1.1-alpha.db68a2.0<EMAIL_ADDRESS>
📬Published Alpha Packages:@codecademy/codebytes@0.1.1-alpha.19caf8.0<EMAIL_ADDRESS>
📬Published Alpha Packages:@codecademy/codebytes@0.1.1-alpha.9d702d.0<EMAIL_ADDRESS>
📬Published Alpha Packages:@codecademy/codebytes@0.1.1-alpha.ddee0b.0<EMAIL_ADDRESS>
📬Published Alpha Packages:@codecademy/codebytes@0.1.1-alpha.675361.0<EMAIL_ADDRESS>
📬Published Alpha Packages:@codecademy/codebytes@0.1.1-alpha.263a18.0@codecademy/styleguide@0.1.1-alpha.263a18.0


Filters in sort

Hi,
look at this query:
query {
  categories(
    first: 100
    sort: [
      {
        translation: {
          name: DESC
        }
      }
    ]
    filter: {
      translation: {
        where: {
          language_id: {
            equal: "en-GB"
          }
        }
      }
    }
  ) {
    data {
      id
      translation(
        language_id: "en-GB"
      ) {
        name
      }
    }
  }
}

As you see, I filter product that have language "en-GB" in translations, and sort them by language.name. But my first language in table is "pl", so results are sorted by first language in table.
One of proposal is extend @sortBy directive to accept simple "where" condition:
query {
  categories(
    first: 100
    sort: [
      {
        translation: {
          where: {
          language_id: {
            equal: "en-GB"
          }
        }
          name: DESC
        }
      }
    ]
    filter: {
      translation: {
        where: {
          language_id: {
            equal: "en-GB"
          }
        }
      }
    }
  ) {
    data {
      id
      translation(
        language_id: "en-GB"
      ) {
        name
      }
    }
  }
}

or make search in @searchBy directive:
query {
  categories(
    first: 100
    sort: [
      {
        translation: {
          name: DESC
        }
      }
    ]
    filter: {
      translation: {
        where: {
          language_id: {
            equal: "en-GB"
            sort: true
          }
        }
      }
    }
  ) {
    data {
      id
      translation(
        language_id: "en-GB"
      ) {
        name
      }
    }
  }
}

What do you think?

Seems each category has multiple translations? This case, unfortunately, is not yet supported. But I'm not sure that fully understand what are you trying to achieve... So maybe you can provide minimal db structure, graphql schema, and expected results?

Yes, each category has multiple translations. First query from post above generates this SQL query:
select
  *
from
  `categories`
where
  (
    exists (
      select
        *
      from
        `category_translations`
      where
        `categories`.`id` = `category_translations`.`category_id`
        and `category_translations`.`language_id` = 'en-GB'
    )
  )
order by
  (
    select
      `category_translations`.`name`
    from
      `category_translations`
    where
      `categories`.`id` = `category_translations`.`category_id`
    limit
      1
  ) desc
limit
  100 offset 0

As you can see, in WHERE clause are conditions to fetch only en-gb translations, but in ORDER  clause there is only joining translations by id, default ordered by primary key. So, if language "en-gb" is not created firstly, there is sorting by first matched row (eg. pl language, or any other).

In the master branch (and the next major version) you can try to add Condition operator (or better a subclass because it will allow to redefine extra field name) into extra operators for @sortBy (same as for Random) and technically it may work 😀

Hello,
so, if I understand correctly, in Condition operator I should detect that in @searchBy is used "translations" table, get the language_id value and provide it do @sortBy condition?
Ps. you do awesome job, thank you!

Nope, I meant something like
    'sort_by'   => [
        /**
         * Operators
         * ---------------------------------------------------------------------
         *
         * You can (re)define types and supported operators here.
         *
         * @see Operator
         */
        'operators' => [
            SortByOperators::Extra => [
                \LastDragon_ru\LaraASP\GraphQL\Builder\Contracts\Operator\Condition::class,
            ],
        ],
    ],

but, as I realized now, it unfortunately will not work :( So you need to create a custom operator that will create a custom type, you can check Relation as example.

It is possible to achieve by custom types/operators, but I'm not sure the package should support it out of the box. Sorry. So I will close it for now.


Validate sampling rate of IMU sensor

The sampling rate for the IMU unit is currently at 20 Hz, which may be a little low. It would be nice to see if it could be increased to 100 Hz without much performance impact on the Beaglebone Black. However, this should only be done if we estimate that we are currently losing too much information at 20 Hz, specially for angular velocity and linear acceleration:

Note: the gyroscope sensor operates natively at 800 Hz, and the accelerometer at 1600 HZ.

Maximum rate for the imu capture seems to be around 22Hz. Will continue to investigate if this is a performance issue that we can fix.

With new higher bitrate for i2c, and by using FIFO BYPASS mode for the devices, 130+Hz imu data can be obtained.
However, FIFO BYPASS causes issues with the magnetometer. Also, having a sampling frequency over 20Hz seems to have too much of an impact on performance, especially during recording.

I just found linux drivers for the gyroscope (l3gd20), and accelerometer + magnetometer (lm303):
l3gd20
http://www.st.com/content/st_com/en/products/embedded-software/mems-and-sensors-software/drivers-for-mems/stsw-mems018.html
lm303
http://www.st.com/content/st_com/en/products/embedded-software/mems-and-sensors-software/drivers-for-mems/stsw-mems025.html
Those may allow for better sampling rate than the current implementation.

See commit 7a921d2 for all the necessary Linux drivers to install:
https://github.com/sbrodeur/ros-icreate-bbb/tree/master/src/imu/drivers

It seems that the LSM303D and L3GD20 sensors report data as HAL events:
https://github.com/01org/android-iio-sensors-hal
https://www.inovex.de/blog/android-sensor-integration-part-3-hal/

Right now, the captureBMP node for the barometer, is slower than its accel/gyro counter-part. I suspect this is due to the file reading which can be quite time consuming. I will continue to investigate to speed up the node. Once it reaches an acceptable speed, we could switch LMS303D and L3GD20 to this as well.

I think it is also possible that the delay comes from the overloaded I2C bus. All devices (RTC, accelerometer, gyroscope, magnetometer) are currently sharing that single bus.

captureBMP was using too expensive read operators on the files. Now it's running well and can go 45Hz+ if we desire.

See:
http://elinux.org/Sparkfun:_BMP085_Barometric_Pressure_Sensor#Reading_the_Temperature_and_Pressure_Programmatically

From the datasheet of BMP180 (page 13):

We should get higher rates, up to 128Hz.

Barometer will be updated at 15Hz.


beet command tracebacks in importer in current master

There's a traceback in both the fetchart plugin , and seemingly the importer module itself. I tried without the fetchart plugin and got the 2nd traceback only. They seem to have the same root cause though.
$ ./beet write -p
** error loading plugin fetchart
Traceback (most recent call last):
  File "/home/johnny/src/beets/beets/plugins.py", line 257, in load_plugins
    namespace = __import__(modname, None, None)
  File "/home/johnny/src/beets/beetsplug/fetchart.py", line 28, in <module>
    from beets import importer
  File "/home/johnny/src/beets/beets/importer.py", line 47, in <module>
    'ALBUMS'])
  File "/usr/lib/python2.7/site-packages/enum/__init__.py", line 321, in __call__
    return cls._create_(value, names, module=module, type=type)
  File "/usr/lib/python2.7/site-packages/enum/__init__.py", line 429, in _create_
    enum_class = metacls.__new__(metacls, class_name, bases, classdict)
  File "/usr/lib/python2.7/site-packages/enum/__init__.py", line 183, in __new__
    enum_class = super(EnumMeta, metacls).__new__(metacls, cls, bases, classdict)
TypeError: type() argument 1 must be string, not unicode

Traceback (most recent call last):
  File "./beet", line 20, in <module>
    beets.ui.main()
  File "/home/johnny/src/beets/beets/ui/__init__.py", line 1081, in main
    _raw_main(args)
  File "/home/johnny/src/beets/beets/ui/__init__.py", line 1067, in _raw_main
    subcommands, plugins, lib = _setup(options, lib)
  File "/home/johnny/src/beets/beets/ui/__init__.py", line 949, in _setup
    from beets.ui.commands import default_commands
  File "/home/johnny/src/beets/beets/ui/commands.py", line 32, in <module>
    from beets import importer
  File "/home/johnny/src/beets/beets/importer.py", line 47, in <module>
    'ALBUMS'])
  File "/usr/lib/python2.7/site-packages/enum/__init__.py", line 321, in __call__
    return cls._create_(value, names, module=module, type=type)
  File "/usr/lib/python2.7/site-packages/enum/__init__.py", line 429, in _create_
    enum_class = metacls.__new__(metacls, class_name, bases, classdict)
  File "/usr/lib/python2.7/site-packages/enum/__init__.py", line 183, in __new__
    enum_class = super(EnumMeta, metacls).__new__(metacls, cls, bases, classdict)
TypeError: type() argument 1 must be string, not unicode

Please upgrade your enum34 package:
$ pip install -U enum34

ah, so the distro version in fedora 21 is not new enough. either that of the semi official Fedora COPR version isn't.

@afreof can you add an updated version of python-enum34 to your copr repo if the Fedora folks don't seem to be bumping theirs anytime soon?

@sampsyo:
[root@falling ~]# pip install -U enum34
Requirement already up-to-date: enum34 in /usr/lib/python2.7/site-packages
but uninstalling the distro version and then installing it with pip removed the error.

Did you install beets from my copr repo https://copr.fedoraproject.org/coprs/afreof/beets/ ? At least beets 1.3.10 from the repo fetches cover jpgs without tracebacks on my Fedora 21.
Before we update basic python packages such as enum34, I would like to understand the problem. But in general I could do it, of course.

I only have the the problem when running from the version from git (to test what will become 1.3.11) with ./beet
I don't think you have to make an rpm after all, as the proper version does exist. I thought (before looking) that the version in the repos was older than what pip would give me, but that is not the case.
However, even though both the pip installed version and the rpm version are 1.04, only the pip installed version works. The python-enum34 rpm gives me the traceback above.

Conclusion: The problem seems to be very specific to python-enum34 packaged by Fedora and a pre-release of beets 1.3.11. I will not investigate on that until beets 1.3.11 is officially released. May be Fedora already provides a working python-enum34 update before beets 1.3.11 will be available.


Quark conflict

causes the enchantment table to have missing texture and disappear and renames the item to air
disabling matrix enchantments in quark config does nothing to fix this

Well then it sounds like quark has changed their code to not only always register the blocks, but also broken the hook I had in place to forcibly disable it when apoth was present.  Wonderful...

i love how quick you got to this i respect dedication to ones work
how soon do you think this is going to be fixed?

No clue, depends how hard it is to fix.  Can't start working on it until I'm back from vacation anyhow

found a workaround with createmod make a world back up if you arnt confident with what your doing remove quark and start a new testworld (so not to remove any quark things from your currant playworld) and place an enchant table make a createmod scematic of just the table reinstall quark enter playworld go into creative(if cheats are disabled open to lan with cheats enabled) and use the schematic to print (schematicanon wont work) now you have a working enchantment table be carefull where you put it you cant pick it up or it will revert to the glitched version

You can also head into the quark jar and remove any assets related to matrix enchanting. This fixes the issue, as well.

You can also head into the quark jar and remove any assets related to matrix enchanting. This fixes the issue, as well.

Quark moved matrix enchanting to a new block, so it should no longer crash.

Quark moved matrix enchanting to a new block, so it should no longer crash.


Upgrade Swinsian.app to v0.11.6

Merged as 0319fd1ccf72646c1451aa0622fa75f8b6e9a92f.

Wrong version number: it's 1.11.6, not 0.11.6.

Thank you for noticing, @SirPavlova. My mistake. Fixed in https://github.com/caskroom/homebrew-cask/pull/17493.


Invalid package

When i do package install milo it says "package.lua:60: Invalid package"

What version of CC or CC:Tweaked are you using, do you have the Plethora mod installed?
What Opus branch are you using, if Milo isn't found this means you are using master-1.7 or develop-1.7.
Milo is only available on the master-1.8 and develop-1.8 branches, and will only work on a recent version of CC:Tweaked and Plethora.

I'm using CCT 1.86.2, Plethora 1.2.3, and using master-1.8. Also on minecraft 1.12.2 if that matters.

This all looks good, please use the develop-1.8 branch instead as it's the most up-to-date branch.


1inch Arbitrum deployment

Added 1inch Arbitrum connector

Deployed connector:
ConnectorName: "1INCH-A"
ConnectorAddress: 0xA4BF319968986D2352FA1c550D781bBFCCE3FcaB


Fix typo on README.md

minor fix

Codecov Report

Merging #112 (23ff7c3) into main (9113fd6) will not change coverage.
The diff coverage is n/a.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
@@           Coverage Diff           @@
##             main     #112   +/-   ##
=======================================
  Coverage   35.62%   35.62%
=======================================
  Files          12       12
  Lines         685      685
=======================================
  Hits          244      244
  Misses        415      415
  Partials       26       26

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


ONNX import/export

Hello,
Congrats for this lib.
Any plan to import and/or export ONNX files ?
https://onnx.ai/
Cheers
W.

Hi,
Thanks ! At the moment, we don't have plans for ONNX integration. We may re-evaluate this in future.

Hi,
Thanks ! At the moment, we don't have plans for ONNX integration. We may re-evaluate this in future.

Any update on converting flashlight trained models to ONNX or Tensorflow?

Hi,
Thanks ! At the moment, we don't have plans for ONNX integration. We may re-evaluate this in future.

Any update on converting flashlight trained models to ONNX or Tensorflow?

Not for now yet.


Progress bar with "start" button

I'm wondering if it might be possible to create a Progress Bar app that doesn't "start" until a button is clicked. I have a script that does not accept dropped input, and simply needs to run when called and display a progress bar. Starting the script automatically on launch doesn't really make sense in my case. I would imagine the "Start" button would then change to "Cancel" while the script is running.

Try to add this
echo "MY Progress app "
response=$(osascript -e 'tell app "System Events" to display dialog "
Program is ready click OK to run
Cancel for EXIT😃"System:Library:CoreServices:Installer.app:Contents:Resources:Installer.icns" buttons {"Cancel", "OK"} default button 2 with title "BUILD"')
answer=$(echo $response | grep "OK")
Cancel is user does not select OK
if [ ! "$answer" ] ; then
osascript -e 'display notification "Program closing" with title "'"$apptitle"'" subtitle "User cancelled"'
exit 0
fi

Thanks, you're right there are several alternative ways of doing this.


Indentation bug in TensorFlow main expert tutorial

Click to expand!
Issue Type
Documentation Bug
Source
binary
Tensorflow Version
2.8
Custom Code
Yes
OS Platform and Distribution
No response
Mobile device
No response
Python version
No response
Bazel version
No response
GCC/Compiler version
No response
CUDA/cuDNN version
No response
GPU model and memory
No response
Current Behaviour?
There is an indentation bug in the main Tensorflow expert colab tutorial located here: https://colab.research.google.com/github/tensorflow/docs/blob/master/site/en/tutorials/quickstart/advanced.ipynb. The code does not run because there is an indentation problem.

@tf.function
def train_step(images, labels):
  with tf.GradientTape() as tape:
    # training=True is only needed if there are layers with different
    # behavior during training versus inference (e.g. Dropout).
    predictions = model(images, training=True)
    loss = loss_object(labels, predictions)
  gradients = tape.gradient(loss, model.trainable_variables)  #PROBLEM!!! NEEDS INDENTATION!
  optimizer.apply_gradients(zip(gradients, model.trainable_variables))

  train_loss(loss)
  train_accuracy(labels, predictions)

Standalone code to reproduce the issue
Run the colab all the way through, and you will see that it chokes on the last step.

https://colab.research.google.com/github/tensorflow/docs/blob/master/site/en/tutorials/quickstart/advanced.ipynb

Relevant log output
No response

Hi @doughywilson !
It was running fine in Colab with the existing tutorial, But I raised a PR to fix the indentation issue.
Thank you!

#PROBLEM!!! NEEDS INDENTATION!

It doesn't actually. Why do you think it does?
Closing the tape is "stop writing new gradient ops to the tape", not "throw out the tape".

Closing the issue for now, as it appears to be a non-issue at the moment.

It was running fine in Colab with the existing tutorial

👍

@MarkDaoust @8bitmp3 !
Thanks for the clarification.


[FEATURE REQUEST] Add mechanism for filtering sensitive data on the cli side

Is your feature request related to a problem? Please describe.
Currently we log some sensitive data stored in manifest files, such data should not be logged.
Describe the solution you'd like
Add python code which will filter the data.
Describe alternatives you've considered
.
Additional context
dump_debug_info function in epicli.py:

Filtering could be similar to the one implemented in:
ansible/playbooks/roles/repository/library/filter_credentials.py

DoD checklist

Changelog

[ ] updated
[ ] not needed

COMPONENTS.md

[ ] updated
[ ] not needed

Schema

[ ] updated
[ ] not needed

Backport tasks

[ ] created
[ ] not needed

Documentation

[ ] added
[ ] updated
[ ] not needed

[ ] Feature has automated tests
[ ] Automated tests passed (QA pipelines)

[ ] apply
[ ] upgrade
[ ] backup/restore

[ ] Idempotency tested
[ ] All conversations in PR resolved
[ ] Solution meets requirements and is done according to design doc
[ ] Usage compliant with license

For terraform it would be best to turn off logging sensitive data on their side.
Maybe this could be achieved by passing some params here:

This requires a separate Spike.


Feature Request: Reclaim native taskbar space

When hiding the native taskbar, the space is lost.
It would be good to adjust the workspace to benefit from this space.
Cairo taskbar would then be in front of the windows.

Cairo has an option to auto-hide the Windows taskbar in order to reclaim space left from it.

I will see if the system allows me to remove the taskbar as an 'app bar' to reclaim space without auto-hide.

After some experimenting and some research, I don't believe anything past the options provided is possible unless you select the option to replace Explorer when installing Cairo.


chore: deps upgrade

🧭 What and Why
🎟 JIRA Ticket: https://github.com/algolia/api-clients-automation/issues/532
Changes included:
deps upgrade

we can't update redocly it seems like, it doesn't accept nullable: true but the alternative is not implemented in openapi-generator yet


An error occurred during the 0.4.0 node upgrade

Ubuntu 22.04
The node is running normally in version 0.3.0, but an error is reported after upgrade 0.4.0
api-blockchain-scanner-daemon startup error
2024-03-22T05:20:13.574656Z  INFO api_server_common::storage::impls::postgres::queries: Found database version: 7
2024-03-22T05:20:13.576920Z  INFO api_blockchain_scanner_lib::sync: Found a new best block in node: (0, 2cf0…9870)
2024-03-22T05:20:13.582596Z  INFO api_blockchain_scanner_lib::blockchain_state: Disconnecting blocks above: BlockHeight(0)
2024-03-22T05:20:13.585597Z  INFO api_blockchain_scanner_lib::blockchain_state: Connected block: (1, b2fb33fa786454c245f34425efdb3a0c419a31d4986edf39c2b9cb0b7c20a860)
thread 'main' panicked at /home/runner/work/mintlayer-core/mintlayer-core/api-server/scanner-lib/src/blockchain_state/mod.rs:727:69:
must be present

If you need to use the scanner and are getting this error after the upgrade, consider deleting the database in PostgreSQL. This is the easiest fix to go.
I just tested the instructions in the readme file with podman and it works fine: https://github.com/mintlayer/mintlayer-core/tree/master/api-server

To be clear, from the way this error is reported, I have a feeling you need to run node-daemon. The API blockchain scanner probably isn't the tool you need.

Nodes are back. Thank you very much


Add support for python and clike languages to prismjs highlighting

WIP - do not merge addressing #42
Shows how to enable syntax highlighting support for additional languages with prism.js.
Needs a test—don't yet know the standard for how to do so in this project.
Also needs discussion if we just add a fixed list of useful languages, or if we make this configurable.

Thanks for looking into this, Ludwig. :)

I think this is the correct place to start... I suppose we could query the document for the language attributes on dt-code tags, but then we'd might miss out on dynamically added tags. Seems like just adding python and c will address almost all uses.


Numba causes crash when using python climate-indices package in terminal

Dear all,
I have installed and have been trying to apply the climate indices python package that is usable in the terminal with their provided example data. The PET, SPI and SPEI commands work without error, but when choosing 'palmers' I get an error based on Numba. Does anybody know how to solve this? I am using Ubuntu 20.04.2 LTS
The climate indices package plus example information I downloaded from here: https://pypi.org/project/climate-indices/
The Numba error that I am receiving in the terminal is as follows:
`process_climate_indices --index palmers --periodicity monthly --netcdf_precip nclimgrid_lowres_prcp.nc --var_name_precip prcp --netcdf_pet nclimgrid_lowres_pet.nc --var_name_pet pet --netcdf_awc nclimgrid_lowres_soil.nc --var_name_awc awc --output_file_base ../output/linda_nclimgrid_lowres --calibration_start_year 1951 --calibration_end_year 2010 --multiprocessing all
2021-06-08  14:57:40 INFO Start time:    2021-06-08 14:57:40.184163
2021-06-08  14:57:40 INFO Computing PALMERS
2021-06-08  14:57:53 ERROR Failed to complete
multiprocessing.pool.RemoteTraceback:
"""
Traceback (most recent call last):
File "/home/linda/anaconda3/lib/python3.7/site-packages/numba/errors.py", line 662, in new_error_context
yield
File "/home/linda/anaconda3/lib/python3.7/site-packages/numba/lowering.py", line 258, in lower_block
self.lower_inst(inst)
File "/home/linda/anaconda3/lib/python3.7/site-packages/numba/pylowering.py", line 176, in lower_inst
raise NotImplementedError(type(inst), inst)
NotImplementedError: (<class 'numba.ir.EnterWith'>, <numba.ir.EnterWith object at 0x7fc191806f10>)
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/home/linda/anaconda3/lib/python3.7/multiprocessing/pool.py", line 121, in worker
result = (True, func(*args, **kwds))
File "/home/linda/anaconda3/lib/python3.7/multiprocessing/pool.py", line 44, in mapstar
return list(map(*args))
File "/home/linda/anaconda3/lib/python3.7/site-packages/climate_indices/main.py", line 1478, in _apply_along_axis_palmers
precip[j], pet[j], awc[j], parameters=args
File "/home/linda/anaconda3/lib/python3.7/site-packages/climate_indices/main.py", line 1142, in _palmers
calibration_end_year=parameters["calibration_end_year"])
File "/home/linda/anaconda3/lib/python3.7/site-packages/numba/dispatcher.py", line 395, in _compile_for_args
raise e
File "/home/linda/anaconda3/lib/python3.7/site-packages/numba/dispatcher.py", line 352, in _compile_for_args
return self.compile(tuple(argtypes))
File "/home/linda/anaconda3/lib/python3.7/site-packages/numba/compiler_lock.py", line 32, in _acquire_compile_lock
return func(*args, **kwargs)
File "/home/linda/anaconda3/lib/python3.7/site-packages/numba/dispatcher.py", line 693, in compile
cres = self._compiler.compile(args, return_type)
File "/home/linda/anaconda3/lib/python3.7/site-packages/numba/dispatcher.py", line 76, in compile
status, retval = self._compile_cached(args, return_type)
File "/home/linda/anaconda3/lib/python3.7/site-packages/numba/dispatcher.py", line 90, in _compile_cached
retval = self._compile_core(args, return_type)
File "/home/linda/anaconda3/lib/python3.7/site-packages/numba/dispatcher.py", line 108, in _compile_core
pipeline_class=self.pipeline_class)
File "/home/linda/anaconda3/lib/python3.7/site-packages/numba/compiler.py", line 972, in compile_extra
return pipeline.compile_extra(func)
File "/home/linda/anaconda3/lib/python3.7/site-packages/numba/compiler.py", line 390, in compile_extra
return self._compile_bytecode()
File "/home/linda/anaconda3/lib/python3.7/site-packages/numba/compiler.py", line 903, in _compile_bytecode
return self._compile_core()
File "/home/linda/anaconda3/lib/python3.7/site-packages/numba/compiler.py", line 890, in _compile_core
res = pm.run(self.status)
File "/home/linda/anaconda3/lib/python3.7/site-packages/numba/compiler_lock.py", line 32, in _acquire_compile_lock
return func(*args, **kwargs)
File "/home/linda/anaconda3/lib/python3.7/site-packages/numba/compiler.py", line 266, in run
raise patched_exception
File "/home/linda/anaconda3/lib/python3.7/site-packages/numba/compiler.py", line 257, in run
stage()
File "/home/linda/anaconda3/lib/python3.7/site-packages/numba/compiler.py", line 728, in stage_objectmode_backend
self._backend(lowerfn, objectmode=True)
File "/home/linda/anaconda3/lib/python3.7/site-packages/numba/compiler.py", line 703, in _backend
lowered = lowerfn()
File "/home/linda/anaconda3/lib/python3.7/site-packages/numba/compiler.py", line 675, in backend_object_mode
self.flags)
File "/home/linda/anaconda3/lib/python3.7/site-packages/numba/compiler.py", line 1167, in py_lowering_stage
lower.lower()
File "/home/linda/anaconda3/lib/python3.7/site-packages/numba/lowering.py", line 177, in lower
self.lower_normal_function(self.fndesc)
File "/home/linda/anaconda3/lib/python3.7/site-packages/numba/lowering.py", line 218, in lower_normal_function
entry_block_tail = self.lower_function_body()
File "/home/linda/anaconda3/lib/python3.7/site-packages/numba/lowering.py", line 243, in lower_function_body
self.lower_block(block)
File "/home/linda/anaconda3/lib/python3.7/site-packages/numba/lowering.py", line 258, in lower_block
self.lower_inst(inst)
File "/home/linda/anaconda3/lib/python3.7/contextlib.py", line 130, in exit
self.gen.throw(type, value, traceback)
File "/home/linda/anaconda3/lib/python3.7/site-packages/numba/errors.py", line 670, in new_error_context
six.reraise(type(newerr), newerr, tb)
File "/home/linda/anaconda3/lib/python3.7/site-packages/numba/six.py", line 659, in reraise
raise value
numba.errors.LoweringError: Failed in object mode pipeline (step: object mode backend)
(<class 'numba.ir.EnterWith'>, <numba.ir.EnterWith object at 0x7fc191806f10>)
File "../../../../../../anaconda3/lib/python3.7/site-packages/climate_indices/palmer.py", line 512:
def _cafec_coefficients(potential_evapotranspiration: np.ndarray,

with warnings.catch_warnings():
^

[1] During: lowering "enter_with $phi100.1" at /home/linda/anaconda3/lib/python3.7/site-packages/climate_indices/palmer.py (512)
This should not have happened, a problem has occurred in Numba's internals.
You are currently using Numba version 0.45.1.
Please report the error message and traceback, along with a minimal reproducer
at: https://github.com/numba/numba/issues/new
If more help is needed please feel free to speak to the Numba core developers
directly at: https://gitter.im/numba/numba
Thanks in advance for your help in improving Numba!
"""
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/home/linda/anaconda3/lib/python3.7/site-packages/climate_indices/main.py", line 1813, in main
_compute_write_index(kwrgs)
File "/home/linda/anaconda3/lib/python3.7/site-packages/climate_indices/main.py", line 869, in _compute_write_index
args=args,
File "/home/linda/anaconda3/lib/python3.7/site-packages/climate_indices/main.py", line 1296, in _parallel_process
pool.map(_apply_along_axis_palmers, chunk_params)
File "/home/linda/anaconda3/lib/python3.7/multiprocessing/pool.py", line 268, in map
return self._map_async(func, iterable, mapstar, chunksize).get()
File "/home/linda/anaconda3/lib/python3.7/multiprocessing/pool.py", line 657, in get
raise self._value
numba.errors.LoweringError: Failed in object mode pipeline (step: object mode backend)
(<class 'numba.ir.EnterWith'>, <numba.ir.EnterWith object at 0x7fc191806f10>)
File "../../../../../../anaconda3/lib/python3.7/site-packages/climate_indices/palmer.py", line 512:
def _cafec_coefficients(potential_evapotranspiration: np.ndarray,

with warnings.catch_warnings():
^

[1] During: lowering "enter_with $phi100.1" at /home/linda/anaconda3/lib/python3.7/site-packages/climate_indices/palmer.py (512)
This should not have happened, a problem has occurred in Numba's internals.
You are currently using Numba version 0.45.1.
Please report the error message and traceback, along with a minimal reproducer
at: https://github.com/numba/numba/issues/new
If more help is needed please feel free to speak to the Numba core developers
directly at: https://gitter.im/numba/numba
Thanks in advance for your help in improving Numba!
multiprocessing.pool.RemoteTraceback:
"""
Traceback (most recent call last):
File "/home/linda/anaconda3/lib/python3.7/site-packages/numba/errors.py", line 662, in new_error_context
yield
File "/home/linda/anaconda3/lib/python3.7/site-packages/numba/lowering.py", line 258, in lower_block
self.lower_inst(inst)
File "/home/linda/anaconda3/lib/python3.7/site-packages/numba/pylowering.py", line 176, in lower_inst
raise NotImplementedError(type(inst), inst)
NotImplementedError: (<class 'numba.ir.EnterWith'>, <numba.ir.EnterWith object at 0x7fc191806f10>)
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/home/linda/anaconda3/lib/python3.7/multiprocessing/pool.py", line 121, in worker
result = (True, func(*args, **kwds))
File "/home/linda/anaconda3/lib/python3.7/multiprocessing/pool.py", line 44, in mapstar
return list(map(*args))
File "/home/linda/anaconda3/lib/python3.7/site-packages/climate_indices/main.py", line 1478, in _apply_along_axis_palmers
precip[j], pet[j], awc[j], parameters=args
File "/home/linda/anaconda3/lib/python3.7/site-packages/climate_indices/main.py", line 1142, in _palmers
calibration_end_year=parameters["calibration_end_year"])
File "/home/linda/anaconda3/lib/python3.7/site-packages/numba/dispatcher.py", line 395, in _compile_for_args
raise e
File "/home/linda/anaconda3/lib/python3.7/site-packages/numba/dispatcher.py", line 352, in _compile_for_args
return self.compile(tuple(argtypes))
File "/home/linda/anaconda3/lib/python3.7/site-packages/numba/compiler_lock.py", line 32, in _acquire_compile_lock
return func(*args, **kwargs)
File "/home/linda/anaconda3/lib/python3.7/site-packages/numba/dispatcher.py", line 693, in compile
cres = self._compiler.compile(args, return_type)
File "/home/linda/anaconda3/lib/python3.7/site-packages/numba/dispatcher.py", line 76, in compile
status, retval = self._compile_cached(args, return_type)
File "/home/linda/anaconda3/lib/python3.7/site-packages/numba/dispatcher.py", line 90, in _compile_cached
retval = self._compile_core(args, return_type)
File "/home/linda/anaconda3/lib/python3.7/site-packages/numba/dispatcher.py", line 108, in _compile_core
pipeline_class=self.pipeline_class)
File "/home/linda/anaconda3/lib/python3.7/site-packages/numba/compiler.py", line 972, in compile_extra
return pipeline.compile_extra(func)
File "/home/linda/anaconda3/lib/python3.7/site-packages/numba/compiler.py", line 390, in compile_extra
return self._compile_bytecode()
File "/home/linda/anaconda3/lib/python3.7/site-packages/numba/compiler.py", line 903, in _compile_bytecode
return self._compile_core()
File "/home/linda/anaconda3/lib/python3.7/site-packages/numba/compiler.py", line 890, in _compile_core
res = pm.run(self.status)
File "/home/linda/anaconda3/lib/python3.7/site-packages/numba/compiler_lock.py", line 32, in _acquire_compile_lock
return func(*args, **kwargs)
File "/home/linda/anaconda3/lib/python3.7/site-packages/numba/compiler.py", line 266, in run
raise patched_exception
File "/home/linda/anaconda3/lib/python3.7/site-packages/numba/compiler.py", line 257, in run
stage()
File "/home/linda/anaconda3/lib/python3.7/site-packages/numba/compiler.py", line 728, in stage_objectmode_backend
self._backend(lowerfn, objectmode=True)
File "/home/linda/anaconda3/lib/python3.7/site-packages/numba/compiler.py", line 703, in _backend
lowered = lowerfn()
File "/home/linda/anaconda3/lib/python3.7/site-packages/numba/compiler.py", line 675, in backend_object_mode
self.flags)
File "/home/linda/anaconda3/lib/python3.7/site-packages/numba/compiler.py", line 1167, in py_lowering_stage
lower.lower()
File "/home/linda/anaconda3/lib/python3.7/site-packages/numba/lowering.py", line 177, in lower
self.lower_normal_function(self.fndesc)
File "/home/linda/anaconda3/lib/python3.7/site-packages/numba/lowering.py", line 218, in lower_normal_function
entry_block_tail = self.lower_function_body()
File "/home/linda/anaconda3/lib/python3.7/site-packages/numba/lowering.py", line 243, in lower_function_body
self.lower_block(block)
File "/home/linda/anaconda3/lib/python3.7/site-packages/numba/lowering.py", line 258, in lower_block
self.lower_inst(inst)
File "/home/linda/anaconda3/lib/python3.7/contextlib.py", line 130, in exit
self.gen.throw(type, value, traceback)
File "/home/linda/anaconda3/lib/python3.7/site-packages/numba/errors.py", line 670, in new_error_context
six.reraise(type(newerr), newerr, tb)
File "/home/linda/anaconda3/lib/python3.7/site-packages/numba/six.py", line 659, in reraise
raise value
numba.errors.LoweringError: Failed in object mode pipeline (step: object mode backend)
(<class 'numba.ir.EnterWith'>, <numba.ir.EnterWith object at 0x7fc191806f10>)
File "../../../../../../anaconda3/lib/python3.7/site-packages/climate_indices/palmer.py", line 512:
def _cafec_coefficients(potential_evapotranspiration: np.ndarray,

with warnings.catch_warnings():
^

[1] During: lowering "enter_with $phi100.1" at /home/linda/anaconda3/lib/python3.7/site-packages/climate_indices/palmer.py (512)
This should not have happened, a problem has occurred in Numba's internals.
You are currently using Numba version 0.45.1.
Please report the error message and traceback, along with a minimal reproducer
at: https://github.com/numba/numba/issues/new
If more help is needed please feel free to speak to the Numba core developers
directly at: https://gitter.im/numba/numba
Thanks in advance for your help in improving Numba!
"""
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/home/linda/anaconda3/bin/process_climate_indices", line 10, in
sys.exit(main())
File "/home/linda/anaconda3/lib/python3.7/site-packages/climate_indices/main.py", line 1813, in main
_compute_write_index(kwrgs)
File "/home/linda/anaconda3/lib/python3.7/site-packages/climate_indices/main.py", line 869, in _compute_write_index
args=args,
File "/home/linda/anaconda3/lib/python3.7/site-packages/climate_indices/main.py", line 1296, in _parallel_process
pool.map(_apply_along_axis_palmers, chunk_params)
File "/home/linda/anaconda3/lib/python3.7/multiprocessing/pool.py", line 268, in map
return self._map_async(func, iterable, mapstar, chunksize).get()
File "/home/linda/anaconda3/lib/python3.7/multiprocessing/pool.py", line 657, in get
raise self._value
numba.errors.LoweringError: Failed in object mode pipeline (step: object mode backend)
(<class 'numba.ir.EnterWith'>, <numba.ir.EnterWith object at 0x7fc191806f10>)
File "../../../../../../anaconda3/lib/python3.7/site-packages/climate_indices/palmer.py", line 512:
def _cafec_coefficients(potential_evapotranspiration: np.ndarray,

with warnings.catch_warnings():
^

[1] During: lowering "enter_with $phi100.1" at /home/linda/anaconda3/lib/python3.7/site-packages/climate_indices/palmer.py (512)
This should not have happened, a problem has occurred in Numba's internals.
You are currently using Numba version 0.45.1.
Please report the error message and traceback, along with a minimal reproducer
at: https://github.com/numba/numba/issues/new
If more help is needed please feel free to speak to the Numba core developers
directly at: https://gitter.im/numba/numba
Thanks in advance for your help in improving Numba!
`

Thanks for the report. I think the issue(s) are as follows:

0.45.0 is a very old version of Numba, please consider updating this, 0.53.x is the latest version.
with driven context manager use is very limited in Numba, there's only one real use case supported in nopython mode and that's with numba.objmode https://numba.readthedocs.io/en/stable/user/withobjmode.html#numba.objmode. In object mode it should work but will need a recent version of Numba.

Thank you very much for your prompt response.
I have updated my Numba to version 0.53.1 and ran the climate indices again. It still crashed but with a somewhat smaller error code than the one above, however it is indeed still finding fault in with.
When altering the code too: with objmode(warnings.catch_warnings()): (see attached file) I get the following error (similar to the last one):
`process_climate_indices --index palmers --periodicity monthly --netcdf_precip nclimgrid_lowres_prcp.nc --var_name_precip prcp --netcdf_pet nclimgrid_lowres_pet.nc --var_name_pet pet --netcdf_awc nclimgrid_lowres_soil.nc --var_name_awc awc --output_file_base ../output/linda_nclimgrid_lowres --calibration_start_year 1951 --calibration_end_year 2010 --multiprocessing all
2021-06-08  15:33:22 INFO Start time:    2021-06-08 15:33:22.467978
2021-06-08  15:33:22 INFO Computing PALMERS
2021-06-08  15:33:37 ERROR Failed to complete
multiprocessing.pool.RemoteTraceback:
"""
Traceback (most recent call last):
File "/home/linda/anaconda3/lib/python3.7/site-packages/numba/core/errors.py", line 744, in new_error_context
yield
File "/home/linda/anaconda3/lib/python3.7/site-packages/numba/core/lowering.py", line 230, in lower_block
self.lower_inst(inst)
File "/home/linda/anaconda3/lib/python3.7/site-packages/numba/core/pylowering.py", line 168, in lower_inst
raise NotImplementedError(type(inst), inst)
NotImplementedError: (<class 'numba.core.ir.EnterWith'>, <numba.core.ir.EnterWith object at 0x7fbdfc86e790>)
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/home/linda/anaconda3/lib/python3.7/multiprocessing/pool.py", line 121, in worker
result = (True, func(*args, **kwds))
File "/home/linda/anaconda3/lib/python3.7/multiprocessing/pool.py", line 44, in mapstar
return list(map(*args))
File "/home/linda/anaconda3/lib/python3.7/site-packages/climate_indices/main.py", line 1478, in _apply_along_axis_palmers
precip[j], pet[j], awc[j], parameters=args
File "/home/linda/anaconda3/lib/python3.7/site-packages/climate_indices/main.py", line 1142, in _palmers
calibration_end_year=parameters["calibration_end_year"])
File "/home/linda/anaconda3/lib/python3.7/site-packages/numba/core/dispatcher.py", line 439, in _compile_for_args
raise e
File "/home/linda/anaconda3/lib/python3.7/site-packages/numba/core/dispatcher.py", line 372, in _compile_for_args
return_val = self.compile(tuple(argtypes))
File "/home/linda/anaconda3/lib/python3.7/site-packages/numba/core/dispatcher.py", line 909, in compile
cres = self._compiler.compile(args, return_type)
File "/home/linda/anaconda3/lib/python3.7/site-packages/numba/core/dispatcher.py", line 79, in compile
status, retval = self._compile_cached(args, return_type)
File "/home/linda/anaconda3/lib/python3.7/site-packages/numba/core/dispatcher.py", line 93, in _compile_cached
retval = self._compile_core(args, return_type)
File "/home/linda/anaconda3/lib/python3.7/site-packages/numba/core/dispatcher.py", line 111, in _compile_core
pipeline_class=self.pipeline_class)
File "/home/linda/anaconda3/lib/python3.7/site-packages/numba/core/compiler.py", line 606, in compile_extra
return pipeline.compile_extra(func)
File "/home/linda/anaconda3/lib/python3.7/site-packages/numba/core/compiler.py", line 353, in compile_extra
return self._compile_bytecode()
File "/home/linda/anaconda3/lib/python3.7/site-packages/numba/core/compiler.py", line 415, in _compile_bytecode
return self._compile_core()
File "/home/linda/anaconda3/lib/python3.7/site-packages/numba/core/compiler.py", line 395, in _compile_core
raise e
File "/home/linda/anaconda3/lib/python3.7/site-packages/numba/core/compiler.py", line 386, in _compile_core
pm.run(self.state)
File "/home/linda/anaconda3/lib/python3.7/site-packages/numba/core/compiler_machinery.py", line 339, in run
raise patched_exception
File "/home/linda/anaconda3/lib/python3.7/site-packages/numba/core/compiler_machinery.py", line 330, in run
self._runPass(idx, pass_inst, state)
File "/home/linda/anaconda3/lib/python3.7/site-packages/numba/core/compiler_lock.py", line 35, in _acquire_compile_lock
return func(*args, **kwargs)
File "/home/linda/anaconda3/lib/python3.7/site-packages/numba/core/compiler_machinery.py", line 289, in _runPass
mutated |= check(pss.run_pass, internal_state)
File "/home/linda/anaconda3/lib/python3.7/site-packages/numba/core/compiler_machinery.py", line 262, in check
mangled = func(compiler_state)
File "/home/linda/anaconda3/lib/python3.7/site-packages/numba/core/object_mode_passes.py", line 120, in run_pass
lowered = backend_object_mode()
File "/home/linda/anaconda3/lib/python3.7/site-packages/numba/core/object_mode_passes.py", line 118, in backend_object_mode
state.flags)
File "/home/linda/anaconda3/lib/python3.7/site-packages/numba/core/object_mode_passes.py", line 78, in _py_lowering_stage
lower.lower()
File "/home/linda/anaconda3/lib/python3.7/site-packages/numba/core/lowering.py", line 136, in lower
self.lower_normal_function(self.fndesc)
File "/home/linda/anaconda3/lib/python3.7/site-packages/numba/core/lowering.py", line 190, in lower_normal_function
entry_block_tail = self.lower_function_body()
File "/home/linda/anaconda3/lib/python3.7/site-packages/numba/core/lowering.py", line 216, in lower_function_body
self.lower_block(block)
File "/home/linda/anaconda3/lib/python3.7/site-packages/numba/core/lowering.py", line 230, in lower_block
self.lower_inst(inst)
File "/home/linda/anaconda3/lib/python3.7/contextlib.py", line 130, in exit
self.gen.throw(type, value, traceback)
File "/home/linda/anaconda3/lib/python3.7/site-packages/numba/core/errors.py", line 751, in new_error_context
raise newerr.with_traceback(tb)
numba.core.errors.LoweringError: Failed in object mode pipeline (step: object mode backend)
(<class 'numba.core.ir.EnterWith'>, <numba.core.ir.EnterWith object at 0x7fbdfc86e790>)
File "../../../../../../anaconda3/lib/python3.7/site-packages/climate_indices/palmer.py", line 512:
def _cafec_coefficients(potential_evapotranspiration: np.ndarray,

with objmode(warnings.catch_warnings()):
^

During: lowering "enter_with $phi106.0" at /home/linda/anaconda3/lib/python3.7/site-packages/climate_indices/palmer.py (512)
"""
`
palmer.txt

@Linimie thanks for the update. I think it might be a good idea to report this on the climate_indices issue tracker https://github.com/monocongo/climate_indices/issues, they may have more sense of what the issue is or what is intended to work.
As an aside, with objmode is not intended to be used as presented (docs), though I don't think it will impact the error the that is occurring.

@stuartarchibald  thank you very much for thinking along. I agree to open an issue with climate_indices and will do so later today.

Closing this issue as it seems to be resolved. If this is not the case please re-open with a comment about any item that appears to be unresolved. Many thanks.


[🐞] Array Empty Index Resume Error

Which component is affected?
Qwik Runtime
Describe the bug
When there is an empty index in an array the container throws an error when trying to resume.

Reproduction
https://stackblitz.com/edit/qwik-starter-jywvpm?file=src%2Froutes%2Findex.tsx
Steps to reproduce

Run the stackblitz repo
Open the container in a new window with dev console
Try to click the button
Should open debugger, you can skip the debugging and should see error in the console regarding the resume id

I realize this is a weird case, and actually pointed to more of a bug in our code that react could handle that qwik could not. However, I think there is a bigger issue here. The error message was not at all helpful in finding the bug in our code or the bug in qwik. I imagine this is something that's being worked on but I had to go through and comment out code line by line to figure out what was causing this.
System Info
Stackblitz

Additional Information
No response

The system info is still relevent for us, since it includes the vite/qwik version


Feature: Remove unused file convertToMarkdown.ts

The convertToMarkdown.ts file inside the lexical-markdown plugin is not used at all. It can safely be removed, as $convertToMarkdownString is defined separately inside the index.ts file.

Sure, here you go: https://github.com/facebook/lexical/pull/4169


Multiple Plants

How do I select which plant data to read if there are multiple plants associated to a single Sunsynk login?

Currently the add on selects the first plant and it isn’t exposed as a configuration option.
We can add that pretty easily though!
Will update here once it’s added

Currently the add on selects the first plant and it isn’t exposed as a configuration option.
We can add that pretty easily though!
Will update here once it’s added

That will be amazing - Thank you very much

any progress on this change yet?


[feature request]optimize yurtadm reset command

What would you like to be added:
please optimize yurtadm reset command by invoking kubeadm reset instead of importing code of kubeadm reset
as a plus, clean up the code that is not needed anymore in pkg/yurtadm dir.
Why is this needed:
yurtadm join command is optimized based on the kubeadm join command, it's natural that optimize yurtadm reset command in the same way.
others
/kind feature

I want to do this after completely finish yurtadm join refactoring

/assign @YTGhost


[MCW] Data Parallel Implementation of ShallowUnet in n300

Currently, on main we have Shallow Unet in old conv.
End goal is to have a data parallel implementation of Shallow Unet in n300 with new conv API.
Executive summary:

Implemented model to n150 with new ConvAPI.
Implemented model to n300 with new ConvAPI via data-parallel.
Working on optimising the model using 2cq and trace.
Resolution = 4,1056,160, for n150 batch_size=2, for n300 batch_size = 4.

sub-tasks

[x] #11811
[x] To run n150 version on n300 as is
[x] #11812
[ ] #11813

ToDo:

Double check model running on both devices
Device perf to be 750 FPS
Host perf using trace with 2cqs (on both n150 and n300)
Validate Host side perf. Check with Austin.
generalise and switch between n150 and n300

Currently, this task is on hold. Updates are as of 28th August.
Currently Evan is working on Shallow Unet in #11912


Add iOSSharedManagerWithinProcess Config Option

Description of Change
Implemented the ability to signal to the CentralContext to use a static CBCentralManager, for sharing the same instance within a process.
This was necessary for a use-case with using Shiny within an intents app extension for iOS. Because the app extension process is long lived between intent triggers, it was undesirable (and unworkable) to have it make a new instance of the CBCentralManager each time an intent was triggered. Having a new instance would case the delegates not be called when the state of the adapter changed. The solution was to make the CBCentralManager static to the CentralContext class, so if previously instantiated that instance would be used.
Issues Resolved
None recorded
API Changes
None
Platforms Affected

iOS

Behavioral Changes
This is a completely optional feature, the config option is false by default, and behavior remains the same then.
Testing Procedure
PR Checklist

[x] Rebased on top of the target branch at time of PR
[x] Changes adhere to coding standard (I believe so)

Just wanted to let you know that I am open for discussions about whether or not this feature should be implemented this way.

This PR doesn't make sense to me.  CentralContext is already static, thus so is its cbcentralmanager

Okay, I didn't realize that. That forces me to revisit my solution to see if something else is the problem in my use case then. Allow me to investigate.

Please push your PR again if you figure out what it was that you needed here.  For now, I'm going to close this out.


silent failure pwsh -c "{hi"

Steps to reproduce
PS> pwsh -c '{hi'
PS> pwsh -c '}hi'
ParserError:
Line |
   1 |  }hi
     |  ~
     | Unexpected token '}' in expression or statement.
PS>

Expected behavior
I expect both pwsh invocations to report an error.
Actual behavior
The first pwsh invocation exits with failure status but doesn't report any error.
Environment data

Name                           Value
----                           -----
PSVersion                      7.1.0
PSEdition                      Core
GitCommitId                    7.1.0
OS                             Microsoft Windows 10.0.19042
Platform                       Win32NT
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion      2.3
SerializationVersion           <IP_ADDRESS>
WSManStackVersion              3.0

Try:
pwsh -c "'}hi'"

/cc @mklement0

@doctordns, I think that @felix9's concern is that a syntax error is being quietly ignored.
@iSazonov, without looking at the source code all I can say is that this bug surfaces only via the CLI - Invoke-Expression '{hi' and  [powershell]::Create().AddScript('{hi').Invoke() both report the syntax error, as expected.

@mklement0 I guess it is a command line escaping or quotation marks, no?

@iSazonov, no, it's not related to quoting (argument parsing); what the CLI sees verbatim as the -c argument after argument parsing in this case is {hi, which it parses and executes as PowerShell code, which should therefore result in a syntax (parser) error, just like withInvoke-Expression '{hi'
As @felix9's counter example in the OP implies, the problem must be related to parsing something as a  script block, given that something that doesn't look like a script block, such as pwsh -c '}hi', properly reports a syntax error.

Pragmatically speaking, something like pwsh -c '{get-date}' doesn't make sense, because the script block is merely created, not executed, causing its verbatim contents to be merely echoed, but the problem also occurs when you prepend &  to effect execution:
# Equally broken: also fails silently
pwsh -c '& {get-date'

As an aside: Of course, even pwsh -c '& {get-date}' is unnecessary, given that there's never a need to construct a script block explicitly, given that the whole -c argument is implicitly a script block (pwsh -c 'get-date' will do).


Add MainWindow display test

Give up on the following

[ ] Get main window to work
[x] Try typing into CommandBox
[x] Flip through list and find
[x] Switch tab
[x] Check if you're in the right place

Only the first task succeeded, the rest are given up. Ready to merge.

Only the first task succeeded, the rest are given up. Ready to merge.

lmao its aite


in some sense   <%= bootstrap_devise_error_messages! %> is not working

<%= bootstrap_devise_error_messages! %>

These are needed to display error messages:
https://github.com/plataformatec/devise/blob/master/app/helpers/devise_helper.rb

When registering, leave email blank and click sign up. error message will show up on top.


fix: bump hdwallet package versions to fix walletconnect txs for evm chains

Description
Resolves app attempting to broadcast non-eth-mainnet evm transactions on eth-mainnet, resulting in failed transaction broadcast in the case of trades, and incorrect approvals being sent on the wrong chain.
NOTE: This requires hdwallet changes to work (link to come when i have access)
See here for details:
https://github.com/shapeshift/web/issues/5421#issuecomment-1749805240
Pull Request Type

[x] :bug: Bug fix (Non-breaking Change: Fixes an issue)
[ ] :hammer_and_wrench: Chore (Non-breaking Change: Doc updates, pkg upgrades, typos, etc..)
[ ] :nail_care: New Feature (Breaking/Non-breaking Change)

Issue (if applicable)

closes #5421
Risk

Risk of lost funds and broken trading + approvals when using a wallet connected to app via walletconnect.
Testing

Note that 1inch wallet transactions dont seem to work on iOS app via walletconnect.

Using a wallet connected via walletconnect:

ERC20 allowance approvals on eth mainnet

ERC20 -> ERC20 trade on eth mainnet

ETH -> ERC20 trade on eth mainnet

ERC20 -> ETH trade on eth mainnet

ERC20 allowance approvals on avalanche/polygon/gnosis/bnbsmartchain

ERC20 -> ERC20 trade on avalanche/polygon/gnosis/bnbsmartchain

ETH -> ERC20 trade on avalanche/polygon/gnosis/bnbsmartchain

ERC20 -> ETH trade on avalanche/polygon/gnosis/bnbsmartchain

Engineering
This requires hdwallet changes to work
Operations
☝
Screenshots (if applicable)
DAI on avalanche approval before and after the fix:

Current dependencies on/for this PR:

develop

PR #5425   👈

This comment was auto-generated by Graphite.


Error import thread

Hi,
Using Python 3.4, it's not possible to do an import thread

I did not check the full port for Python 3 yet, will check it this weekend!

Should be fixed with 50dd142c8e4a0d2a4ea195577a31e1de899ee4b1


Better error handling

hi @akashnimare . I have updated the code for better error handling. It will fix #13 . Please have a look.

Merged. @manishsaraan thanks for working on this 🚀


feat: optional flag to treat bip32 paths as relative

Allow relative BIP32Derivation paths to be relative with an optional flag during deserialization. Additionally, during serialization, correct the serialization of relative derivation paths.
BG-54756

Should be good now


fix: Add a switch case to download the binary right version for an OS and CPU arch

fix: Add a switch case to download the binary right version for an OS and CPU arch

Add a switch case to download the binary right version for an OS and CPU arch
Tested against an Apple Silicon Mac, Linux x86-64 and Linux ARM64 .

@niu789 Thank you for fixing this!


Update index.html

@kavindyasinthasilva  contribute to https://github.com/Ishaan28malik/Get-Dev-Resources instead


feat: s3 is_dir and walk support followlink

https://github.com/megvii-research/megfile/issues/13

Codecov Report
Base: 100.00% // Head: 100.00% // No change to project coverage :thumbsup:

Coverage data is based on head (6bf92b8) compared to base (707f317).
Patch coverage: 100.00% of modified lines in pull request are covered.

Additional details and impacted files
@@            Coverage Diff            @@
##              main      #177   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files           35        35
  Lines         4463      4463
=========================================
  Hits          4463      4463

Impacted Files
Coverage Δ

megfile/pathlike.py
100.00% <100.00%> (ø)

megfile/s3.py
100.00% <100.00%> (ø)

megfile/s3_path.py
100.00% <100.00%> (ø)

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.

👍


Mailing List App[Android]

Requirements for the app:-

The app should use recycler view and card view
The app should have a search bar in the top right corner.

Requirements for the README.md file:-

Screenshots
Concepts used
Documentation and resources used
Future Aspects of the app

Note:- Add the app to the Android Projects section

can I work on this ?

@imshahnawazdevil Sure, you can start working on this.

Give a star if you liked our repo.

Doubts:
would I have to take static List for recyclerView or u will provide me API ? Or i have to use my own idea ?

@imshahnawazdevil You can use our own ide.

ok then.

@imshahnawazdevil Best of luck!

@kunal299  can i work on this...
i new to open source so plzz tell me how do i find code for this..


[JENKINS-25920] Update UI style to match that in newer Jenkins versions.

update to build against Jenkins 1.580 (the basis for the first LTS with these style changes)
copy new css from Jenkins

Thank you for a pull request! Please check this document for how the Jenkins project handles pull requests


A problem

Why did the game crash after I replaced the texture 2D? My Unity version is 2021.3.16f1c1.

Please upload a log, otherwise there's no telling what went wrong.

I don't know where the log is, but I replaced the texture 2D and went into the android game and dodged.

You can google how to find unity android logs to get those (generally needs adb). You should also tell me how to reproduce the issue (the new issue template is supposed to contain this but everyone keeps deleting it for some reason)

OK，thank you vary much！

You can google how to find unity android logs to get those (generally needs adb). You should also tell me how to reproduce the issue (the new issue template is supposed to contain this but everyone keeps deleting it for some reason)

I don't know why the logs are blank. My game is WorldWar_v2.6.3 and I changed the texture.

This is the log.Thankyou!

I also mentioned this problem,Just appeared on  every f1c1 version(chinese version?),can't load texture while import it in shared*.assets,maybe should import texture in resS file?


storage: signed url generation

A signed URL allows a user access to a resource for a limited time.

Details at storage/docs/accesscontrol#Signed-URLs.

This is still being implemented.


enable epoll/ipc on Windows wheels

Initially enabled in #1570, epoll has been disabled in our wheels due to causing unavoidable crashes for some users (#1981, #1754, #1999)
Because these crashes are relatively rare, users installing pyzmq from source can still enable it, and pyzmq will follow libzmq's own defaults and build with epoll/ipc enabled:
pip install --no-binary pyzmq pyzmq

We should not re-enable ipc in our Windows wheels until there is a confirmed fix for https://github.com/zeromq/libzmq/issues/4730 (it is incredibly hard to test)

any updates on re-enabling IPC on the windows wheels? I'd really like to use ipc

We need to wait for a libzmq release where ipc doesn't cause crashes on Windows.


Feature Request: Support for owned expansions

First off I would like to say that this tool is awesome, thank you. Secondly I would be astounded if I was the first to suggest this feature, but I would like to add my voice to those requesting it; So here goes:
To say it concisely, I would like to have a option to have the tool prevent me from building squads that I cannot actually build based on the number of core sets and expansions that I own.
I would like to be able to put in the number of each expansion that I own on a page, and then when I go to the squad builder page only be able to select ships/pilots/upgrades in a configuration that I can actually achieve based on what I own. For example, if I only own 2 core sets and one X-Wing expansion, and nothing else, then in the rebel page I would only be able to build a squad using 3 X-Wings, only have pilots from those sets(IE I cannot use Porkins). I would not have access to any Y-Wings, etc. Upgrades would also be limited, preventing me from putting out more of them than I own.
Hopefully this was clear, and thank you for reading,
Alex

Pretty sure this exists via the "Your Collection" link. It's on the right side, in the blue bar, and shows up when you're logged in.

As @elistevens noted, it sounds like what you're looking for is already supported, but you'll need to be logged in.
Note that it doesn't prevent you from adding ships/upgrades you do not already own; instead it warns you.  (After all, you could borrow, say, a Predator card from someone.)
Closing issue; please reopen if the current implementation does not meet your needs.


Outbound Checklists: Added Communications Style Guide

module-name: Outbound Checklists: Added Communications Style Guide
Problem
There does not exist a communication style guide on writing content for the repository's markdown files.
Solution
Added communication style guide which includes:

Tips on communicating project, agency, and work being done
Links to style guides from various resources

This PR also includes missing commits in main

Closing due to extraneous commits, making into a PR


Handle case of trial with items for subscription

Current code bombs out on the check for verify_card_present for a trial
and no card data passed.
Fix is to check the plan exists to see if there's a trial, and if not,
then to check that all subscription items are on trial.

@alexmamonchik Added tests should demonstrate the issue.


terraform-providers: bump versions

Motivation for this change
Update providers to latest versions. Tested google, google-beta and postgresql
##### Things done

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

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

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

Can you try with terraform 0.12 as well?

It looks like those packages have just added dependencies. I'm not too familiar with doing Go packaging with nix, but from the log output you can see that they require new dependencies.

@jonringer Seems to be good for me, please re-try.

@GrahamcOfBorg build terraform-full


Cartoview installation done but how do i set it up on cloud

Please fill the following information to avoid closing issue
Describe your issue in detail

Cartoview Version : (x.xx.x)
Geonode Version : (2.6.3)
log (optional):

I have installed geonode on cloud sucessfully. but how do i add cartoview also on cloud ?

Thankyou @hishamkaram


Outdated? README file

Installed RDKit (2017.03.3) on Debian Scratch from source.
Now am trying to install the postgresql cartridge from source.  The README file (in $RDBASE/Code/PgSQL/rdkit) points to a file (pgsql_install.sh) which does not exist.

run the "pgsql_install" script:
${CMAKE_BINARY_DIR}\Code\PgSQL\rdkit\pgsql_install.bat (Windows)
sh ${CMAKE_BINARY_DIR}/Code/PgSQL/rdkit/pgsql_install.sh (Linux)
which will install rdkit.sql91.in, rdkit--3.4.sql,
rdkit.control and rdkit.dll into PostgreSQL

A find for that file on the whole tree, returns no results.

Please disregard.  It hadn't dawn on me that this is an auto generated file.
cmake -DRDK_BUILD_INCHI_SUPPORT=ON -DRDK_BUILD_PGSQL=ON -DPostgreSQL_ROOT=$PGHOME ..
And building, generates this file with the correct paths.


Chore: Upgrade packages

Notes
@commitlint/cli                   latest  17.1.2   ❯  17.3.0   https://commitlint.js.org/
@commitlint/config-conventional   latest  17.1.0   ❯  17.3.0   https://commitlint.js.org/
@next/eslint-plugin-next          latest  12.2.5   ❯  13.0.5   https://github.com/vercel/next.js#readme
@storybook/addon-actions          latest  6.5.10   ❯  6.5.13   https://github.com/storybookjs/storybook/tree/main/addons/actions
@storybook/addon-essentials       latest  6.5.10   ❯  6.5.13   https://github.com/storybookjs/storybook/tree/main/addons/essentials
@storybook/addon-interactions     latest  6.5.10   ❯  6.5.13   https://github.com/storybookjs/storybook/tree/main/addons/interactions
@storybook/addon-links            latest  6.5.10   ❯  6.5.13   https://github.com/storybookjs/storybook/tree/main/addons/links
@storybook/addon-viewport         latest  6.5.10   ❯  6.5.13   https://github.com/storybookjs/storybook/tree/main/addons/viewport
@storybook/builder-webpack5       latest  6.5.10   ❯  6.5.13   https://github.com/storybookjs/storybook/tree/main/lib/core
@storybook/manager-webpack5       latest  6.5.10   ❯  6.5.13   https://github.com/storybookjs/storybook/tree/main/lib/core
@storybook/react                  latest  6.5.10   ❯  6.5.13   https://github.com/storybookjs/storybook/tree/main/app/react
@testing-library/react            latest  13.3.0   ❯  13.4.0   https://github.com/testing-library/react-testing-library#readme
@types/node                       latest  18.7.14  ❯  18.11.9  https://github.com/DefinitelyTyped/DefinitelyTyped/tree/master/types/node
@types/react                      latest  18.0.18  ❯  18.0.25  https://github.com/DefinitelyTyped/DefinitelyTyped/tree/master/types/react
@types/react-dom                  latest  18.0.6   ❯  18.0.9   https://github.com/DefinitelyTyped/DefinitelyTyped/tree/master/types/react-dom
@typescript-eslint/eslint-plugin  latest  5.36.1   ❯  5.44.0   https://github.com/typescript-eslint/typescript-eslint#readme
@typescript-eslint/parser         latest  5.36.1   ❯  5.44.0   https://github.com/typescript-eslint/typescript-eslint#readme
eslint                            latest  8.23.0   ❯  8.28.0   https://eslint.org
eslint-config-next                latest  12.2.5   ❯  13.0.5   https://github.com/vercel/next.js#readme
eslint-plugin-react               latest  7.31.1   ❯  7.31.11  https://github.com/jsx-eslint/eslint-plugin-react
eslint-plugin-storybook           latest  0.6.4    ❯  0.6.7    https://github.com/storybookjs/eslint-plugin-storybook#readme
eslint-plugin-testing-library     latest  5.6.0    ❯  5.9.1    https://github.com/testing-library/eslint-plugin-testing-library
husky                             latest  8.0.1    ❯  8.0.2    https://typicode.github.io/husky
hygen                             latest  6.2.8    ❯  6.2.11   https://github.com/jondot/hygen#readme
jest                              latest  29.0.1   ❯  29.3.1   https://jestjs.io/
next-sitemap                      latest  3.1.21   ❯  3.1.32   https://github.com/iamvishnusankar/next-sitemap#readme
prettier                          latest  2.7.1    ❯  2.8.0    https://prettier.io
storybook-addon-next              latest  1.6.7    ❯  1.6.10   https://github.com/RyanClementsHax/storybook-addon-next#readme
typescript                        latest  4.8.2    ❯  4.9.3    https://www.typescriptlang.org/
dependencies
@next/bundle-analyzer             latest  12.2.5   ❯  13.0.5   https://github.com/vercel/next.js#readme
next                              latest  12.2.5   ❯  13.0.5   https://nextjs.org
next-seo                          latest  5.5.0    ❯  5.14.1   https://github.com/garmeeh/next-seo#readme
sass                              latest  1.54.8   ❯  1.56.1   https://github.com/sass/dart-sass
Checklist

[ ] All new changes were tested on various devices
[ ] All change-related components were tested for regression
[ ] All new changes were tested with missing or incorrect data

Hey @yordan-hristov, thank you for this PR.
All changes have been merged in #104.
Looks good and we're looking forward to the next NextJS release where the new routing system would be the de-facto solutions! 🎉


fix: use correct path for data files in README

Files are in the public/data directory, not directly in data.

@vjousse Thanks!


Found some minor issues in the Free Code Camp JavaScript Style Guide

Describe your problem and how to reproduce it:
In the Long Strings section, I discovered minor issues in both examples.
1st example
var longString =
  ‘long strings should ‘ +
  ‘be in this form, with the ‘ +
  ‘operator ending the line’;

I copied and pasted this code into the chrome console and it produced the following error:
Uncaught SyntaxError: Invalid or unexpected token
Suggested fix:
I believe those symbols should be back ticks
var longString =
  `long strings should ` +
  `be in this form, with the ` +
  `operator ending the line.`;

Tested this version in the browser and it did not produce any errors.
2nd Example:
var foo = 'bar';

var longString = [
  'long strings with variables such as ',
  foo,
  'should ',
  'be in this form, an array of strings ',
  'that are joined with the join array instance method',
].join('');

I pasted this code into the browser and then entered longString. The console returned:
"long strings with variables such as barshould be in this form, an array of strings that are joined with the join array instance method"
The bar and should are joined.
Suggested fix:
var foo = 'bar';

var longString = [
  'long strings with variables such as ',
  foo,
  ' should ',
  'be in this form, an array of strings ',
  'that are joined with the join array instance method.',
].join('');

Outcome: No errors and logs
"long strings with variables such as bar should be in this form, an array of strings that are joined with the join array instance method."

Add a Link to the page with the problem:
https://www.freecodecamp.org/forum/t/free-code-camp-javascript-style-guide/19121
Tell us about your browser and operating system:

Browser Name: Chrome
Browser Version: Version 76.0.3809.132 (Official Build) (64-bit)
Operating System: 64-bit operating system

If possible, add a screenshot here (you can drag and drop, png, jpg, gif, etc. in this box):

I would like to go ahead and create a pull request.

No need to create a pull request.  I have fixed the Guide topic.  Pull requests are not needed for forum topics.  In the future, you can just reply to the topic and make a comment about what needs to be fixed and someone with moderator or admin access can fix it.
Thanks for reporting.  I will close this issue for now.  If you have other issues with the forum topic, please reply to the forum topic directly.

I guess I am confused. I was looking to contribute to freeCodeCamp. My process was to report what I found and then make the edit in order to make a contribution.

@TishG Sory for the confusion.  For changes to the repo, you create issues and pull requests.  For changes to the forum topics, you can just reply to let someone know what needs to be corrected.  It is still contributing, but it is not via GitHub.


Perssion Denied - brew cask install Cheatsheet -/opt/homebrew-cask/Caskroom/cheatsheet

Hi
I follow the instruction from brew to report this bug
I was hoping to install cheatsheet on my Mac
Therefore i type 'brew cask install cheatsheet'
I got the report as follow:
==> Downloading http://mediaatelier.com/CheatSheet/CheatSheet_1.2.2.zip
######################################################################## 100.0%
Error: Permission denied - /opt/homebrew-cask/Caskroom/cheatsheet
Most likely, this means you have an outdated version of homebrew-cask. Please run:
  brew update && brew upgrade brew-cask && brew cleanup && brew cask cleanup

If this doesn’t fix the problem, please report this bug:
  https://github.com/caskroom/homebrew-cask/issues

/System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/2.0.0/fileutils.rb:245:in mkdir' /System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/2.0.0/fileutils.rb:245:in fu_mkdir'
/System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/2.0.0/fileutils.rb:219:in block (2 levels) in mkdir_p' /System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/2.0.0/fileutils.rb:217:in reverse_each'
/System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/2.0.0/fileutils.rb:217:in block in mkdir_p' /System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/2.0.0/fileutils.rb:203:in each'
/System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/2.0.0/fileutils.rb:203:in mkdir_p' /usr/local/Cellar/brew-cask/0.59.0/rubylib/hbc/installer.rb:100:in extract_primary_container'
/usr/local/Cellar/brew-cask/0.59.0/rubylib/hbc/installer.rb:65:in install' /usr/local/Cellar/brew-cask/0.59.0/rubylib/hbc/cli/install.rb:20:in block in install_casks'
/usr/local/Cellar/brew-cask/0.59.0/rubylib/hbc/cli/install.rb:17:in each' /usr/local/Cellar/brew-cask/0.59.0/rubylib/hbc/cli/install.rb:17:in install_casks'
/usr/local/Cellar/brew-cask/0.59.0/rubylib/hbc/cli/install.rb:6:in run' /usr/local/Cellar/brew-cask/0.59.0/rubylib/hbc/cli.rb:78:in run_command'
/usr/local/Cellar/brew-cask/0.59.0/rubylib/hbc/cli.rb:118:in process' /usr/local/Cellar/brew-cask/0.59.0/rubylib/brew-cask-cmd.rb:19:in '
then i tried 'brew update && brew upgrade brew-cask && brew cleanup && brew cask cleanup'
and the response was
Already up-to-date.
Error: caskroom/cask/brew-cask 0.59.0 already installed
Hope it helps

Oh I got
The main problem is /opt/homebrew-cask/Caskroom is belongs to another user
Sorry for wasting your time for reading


WIP feat: Add graphql helper

What does this do?
Adds GraphQL helper that can be used to make queries to a graphQL endpoint.
resolves #1808.

So I basically copied most of the functions from REST helper with minor modifications. Would it be better to create an abstract class with the relevant needed functions that both REST and GraphQL can inherit from?.
Also, sendQuery() and sendMutation() functions are doing the same thing, with same code. But I  left them like that. Perhaps someone with more experience with graphQL can judge and tell if two separate functions are required or If either function can be improved.

It would be nice to create tests for it as well as adding a doc like we have for REST https://codecept.io/helpers/REST

It would be nice to create tests for it as well as adding a doc like we have for REST https://codecept.io/helpers/REST

Yes, adding tests now.

I have also done a simple implementation of GraphQLDataFactory, which works similar to the rest one. But the configuration part takes some work to set up, compared to the rest one. If anyone has any ideas as to how to improve it, pls let me know.

@DavertMik I have implemented GraphQLDataFactory as per your suggestions. Pls go through the changes when possible.

It would be nice to create tests for it as well as adding a doc like we have for REST https://codecept.io/helpers/REST

@PeterNgTr I will also add the doc once the code is approved.

It would be nice to create tests for it as well as adding a doc like we have for REST https://codecept.io/helpers/REST

@PeterNgTr I will also add the doc once the code is approved.

That's amazing @radhey1851

@radhey1851 please update circle ci builds to include GraphQL helper tests and after all tests pass I'm merging.


Add snapshot exports and PROJECT_SNAPSHOT_EXPORTS to settings

This PR adds PROJECT_SNAPSHOT_EXPORTS to settings and enables the user to export single snapshots using project export plugins from this list. Those plugins need to be slightly refactored to handle snapshots instead of projects.

coverage: 90.492% (+0.01%) from 90.478%
when pulling<PHONE_NUMBER>54cd077e75d9139ed92e848273fb1e on snapshot_export
into 1cdcf9ea6c28c6e4398691ce3093726e79ae2dfb on main.

This PR is also ready to be approved.


Fix devcontainers environment with latest changes

Newest changes (Python and dependencies) broke the devcontainer environment.

To save you from opening about PR I think we might want to wait for https://github.com/onedr0p/flux-cluster-template/pull/1214 to be merged. The only major change would be change task ansible:deps to task init


support more than 9 lights

[ ] brainstorm

Feedback from Reddit
Q: ... why the hard limit to nine lights?
A: It is because you need only one keystroke to select the first 9 lights. If I want to support more lights I need to find a different way to do this. The on/off-switch is currently possible by pressing the light-number again. The goal was to use only as much keys and keystrokes as necessary.
I could map the on/off-switch to a seperate key or completely sperate these functions to different keys; maybe "y" = on and "n" = off. I have to think about it.


Clarify the behavior or rmdir, _rmdir and _wrmdir with symlinks

Hello,
Could you please clarify what is the behavior of _rmdir(const char *dirname) and _wrmdir(const char *dirname) when dirname is actually a symbolic link?
The doc says dirname will not be deleted and ENOTEMPTY will be returned when
Given path is not a directory, the directory is not empty, or the  directory is either the current working directory or the root directory.

but does the statement "is not a directory" apply to a symbolic link?
I tried to test this use case on my side and it looks like dirname is removed if it is a symlink (the link itself is removed, not the target folder) but I would like to get your confirmation.
(If it helps, this question is related to https://github.com/git-for-windows/git/issues/2967. Long story short: I think it was assumed that the Linux rmdir() and Windows _rmdir() behave the same way with symlinks whereas I think they don't: Linux rmdir() does not remove dirname if it is symlink.)
Thank you in advance.

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

ID: ae7d70f2-fe81-39c0-3896-813f22543a71
Version Independent ID: 8f41ca7c-6d2d-e6aa-1adc-b10d2d59be7f
Content: _rmdir, _wrmdir
Content Source: docs/c-runtime-library/reference/rmdir-wrmdir.md
Product: visual-cpp
Technology: cpp-ucrt
GitHub Login: @TylerMSFT
Microsoft Alias: twhitney

Could you please also clarify the behavior of RemoveDirectoryW() with symlinks?
The documentation talks about directory junction but I don't know if it also applies to symlinks:

RemoveDirectory removes a directory junction, even if the contents of the target are not empty; the function removes directory junctions regardless of the state of the target object. For more information on junctions, see Hard Links and Junctions.

We are in the process of moving away from GitHub issues for C++ documentation (we still accept pull requests). For details, please see Announcing a new way to give feedback on Microsoft Learn This issue will be closed after it is copied to an internal tracking system.


Update composer.json, move lib files to src folder

Related to #67
This PR has been made possible thanks to the incorporation of the composer in version 1.5.5 (dfa8fedeca451).
The primary changes in this PR are:

Updated composer.json to adhere to the official schema.
Moved dev depencencies to require-dev in composer.json.
Refreshed composer.lock with the latest dependencies.
Configured automatic loading of helper.php through composer.json > autoload > files
Introduced the Perlite namespace and mapped it to the /perlite/src directory.
Loaded PerliteParseDown and Parsedown using use statement.

Removed Parsedown.php from the root and replaced its usage with vendor/erusev/parsedown/Parsedown.php.

Added blocking rules for /src and /vendor to the Nginx configuration.
Inserted several global keywords to correspond with the actual global variables in perlite/src/helper.php

I have a few concerns to share:

Given the existing folder structure, which exposes the /perlite as the web root, mapping the Perlite namespace to /perlite/src might pose issues if someone chooses src as their vault name (as well as vendor). A more unique and restricted folder name, such as .src or .perlite, might be a better choice, though it doesn't align with common practices I'm familiar with. Many popular frameworks set their web root to /public, making it /perlite/public for this project.
I relocated helper.php to /perlite/src since it's not an intended web entry point, and there's no other suitable location to place it. However, this new location might not be entirely logical in the context of class autoloading.
helper.php will be loaded automatically for every request. This may not be intended by the original author.

Thanks for taking the time to review.
I appreciate your insights and I'm keen to discuss and incorporate any feedback.

Thanks for the PR, not sure if I can merge it since I have already made some changes in the files in the DEV Branch, I need to add some instruction, that PRs should be done against the DEV Branch to adjust them to the current development status.
One question because it seems you have some experience in this field:
How to manage the JS dependency ? I used php composer but it's a mess, first it downloads too much stuff (I just need some files from the dist folders) and now it also has some conflicts between child dependencies of two dependencies. I don't want or need these child dependencies either, because I won't build the packages. Is there a way to tell composer only to download the wanted files instead of the whole package or is there generally another good approach how to manage this?
My current solution is, that I removed mermaid from composer and load it directly from a CDN because some child dependencies have a conflict with Katex dependencies.

Thanks for the PR, not sure if I can merge it since I have already made some changes in the files in the DEV Branch, I need to add some instruction, that PRs should be done against the DEV Branch to adjust them to the current development status.
One question because it seems you have some experience in this field:
How to manage the JS dependencies? I used php composer but it's a mess, first it downloads too much stuff (I just need some files from the dist folders) and now it also has some conflicts between child dependencies of two dependencies. I don't want or need these child dependencies either, because I won't build the packages. Is there a way to tell composer only to download the wanted files instead of the whole package or is there generally another good approach how to manage this?
My current solution is, that I removed mermaid from composer and load it directly from a CDN because some child dependencies have a conflict with Katex dependencies.

Oh, that's my bad. I was not aware of the dev branch. I'll close this PR and see what I can do.
I've no experience using composer for anything other than managing PHP packages.
I assume other usages might complicate things.
Since this project does not involve JS compiling/bundling,
placing static JS library files in a web assets path
and loading them with <script> tags seems natural and straightforward.
Using CDNs is also straightforward.

No problem, feel free to create a new on the dev branch and thanks for the info about the JS files, I will think about to include them all via CDNs


Add getByUIDs and getAllByUIDs

In V6, getByUID allows fetching for a document by its type and UID like the following:
client.getByUID('page', 'about-us')

To query for multiple documents by UID, one must either make one query for each UID or write custom predicates.
client.getByUID('page', 'about-us')
client.getByUID('page', 'contact')

// or

client.get({
  predicates: [
    predicates.at('document.type', 'page'),
    predicates.in('my.page.uid', ['about-us', 'contact'])
  ]
})

To make this process more straightforward, getByUIDs and getAllByUIDs methods could be introduced. Since UIDs are directly associated with a document type, we must still limit a query to just one document type.
The new methods could look like the following:
client.getByUIDs('page', ['about-us', 'contact'])
client.getAllByUIDs('page', ['about-us', 'contact'])

(cc @samlfair)

This is available in v6.0.0-alpha.13. The API is exactly like the proposal:
client.getByUIDs('page', ['about-us', 'contact'])
client.getAllByUIDs('page', ['about-us', 'contact'])


Ensure a node relays.

Even if an application-key is unknown to a node, it should still
proxy/relay an acceptable network-authenticated message.
Rework FSM management for provisioning flow.

bors r+


Fixes #8

@anu1097 Thank you for this library is pretty cool and very extensible! I hit a bug that I just opened and here is a PR with a proposed solve. Please let me know if you see any issues or if you would like to proceed in a different way

@anu1097 was wondering if you had time to look at this quick fix?

@eleduardo LGTM, really appreciate you finding and fixing the issue and the kind words. Sorry for the delay, was away for few days.


Github PR Comment Demo

Trying the GitHubPR Comment Task!

r
This is a text example for the demo

r
This is a text example for the demo

This is a text example for the demo

This is a text example for the demo


Quick fix for "Find" Command

Now doing Find Paul will show the Pauls' that are found in both panels

#81


[Bug] business_days.after inconsistencies

I wasn't sure to post this issue or not because I have no clue what is happening and I don't have much data, or at least I think.
I noticed some day calculations were not working properly in our app so I began troubleshooting it.
This date is returned through an API call. So my app receives some params and returns data, which includes this date.
If I run the request through my production web server, my date is off. However, every 10-15 requests, it would return the correct date.
If I run the same code through production console it is okay.
my config:
business_time:
  beginning_of_workday: 12:00:00 am
  end_of_workday: 11:59:59.999999 pm
  work_week:
    - mon
    - tue
    - wed
    - thu
    - fri

This is basically what's running:
days = 2
now = 'Wed, 17 Mar 2021 20:15:16 EDT -04:00'.to_time
date = days.business_days.after(now).to_date

And it's returning Monday 22 2021 instead of Friday 18 2021.
I decided to add some debugging in production and also trying to fetch the date in a different way:
days = 2
now = 'Wed, 17 Mar 2021 20:15:16 EDT -04:00'.to_time
date = days.business_days.after(now).to_date
date2 = days.business_days.after(now.to_date)
if warehouse.code == 'MA' && days == 2 && date != '19 March 2021'.to_date
  message = {
    time_now: Time.now,
    time_zone_now: Time.zone.now,
    warehouse_local: now,
    date: date,
    date2: date2
  }
  Rails.logger.info(message)
end
date

The results were the following:
2021-03-18T00:15:16.468557+00:00 app[web.1]: I, [2021-03-18T00:15:16.468381 #210]  INFO -- : {:time_now=>2021-03-18 00:15:16.468218979 +0000, :time_zone_now=>Thu, 18 Mar 2021 00:15:16 UTC +00:00, :warehouse_local=>Wed, 17 Mar 2021 20:15:16 EDT -04:00, :date=>Mon, 22 Mar 2021, :date2=>Fri, 19 Mar 2021}
2021-03-18T00:15:57.273594+00:00 app[web.1]: I, [2021-03-18T00:15:57.273391 #100]  INFO -- : {:time_now=>2021-03-18 00:15:57.273113129 +0000, :time_zone_now=>Thu, 18 Mar 2021 00:15:57 UTC +00:00, :warehouse_local=>Wed, 17 Mar 2021 20:15:57 EDT -04:00, :date=>Mon, 22 Mar 2021, :date2=>Fri, 19 Mar 2021}

As you can see, date2 was calculated correct. I am fixing my issue this way, but there's definitely something off as running the same thing in console, same environment returns the correct date too.

March 18, 2021 is a Thursday. 2 business days after that would  be the Monday, March 22, 2021.
What am I misunderstanding about your report here?

Jeez. I apologize, the now date is not the correct one. I wasn't and probably am still not in a correct state of mind.
The now is in a specific time zone.

Closing due to finding the real culprit. Since https://github.com/bokmann/business_time/issues/209 was happening, my config was not present and hence 9pm was after the default 9-5pm work time.


-nm NM, --number_molecules NM question

I would like to know how to calculate the number of molecules in a experiment. In targeted DNA seq, it has something to do with coverage? Million reads per sample? Amplicons per run?
Thanks

Also, I would like to know if this calculation could be adapted to hybridization-capture based assays.

Hi @Tato14,
The number of molecules depends on the cells you are using.
After DNA extraction, you can measure the weight of DNA, then divide it by the weight of a single genome to estimate the number of molecules in your reaction.
For example, the human diploid genome weighs around 3.59 x 10-12 grams. So if you have 1ng (1x10-9) of DNA, this represents 278.6 diploid genomes, or ~557 molecules. If you amplify several amplicons from this material, each amplicon will still have 557 molecules. This is the parameter you will use for -nm for AmpUMI.
I don't quite understand your second question. The number of input molecules does not depend on coverage, reads or amplicons, so the calculation above should be able to be adapted to hybridization-capture based assays.
However, you may be asking if the number of UMIs for PCR amplification could be analogous to the number of hybridization probes?
In the UMI question, if too few UMIs are added to the molecules, the same UMI may attach to different molecules, so AmpUMI deals with trying to find a large enough UMI pool so that you can be confident that your UMIs actually represent unique molecules.
If in your hybridization question you are introducing multiple copies of UMI-tagged hybridization probes, where the same UMI can appear multiple times, yes, this is a similar question where you are trying to find a large-enough UMI-probe pool so that you can be confident that a UMI corresponds to only one probe-molecule pair.
However, if you are wondering how many un-tagged (no UMI) probes to introduce to saturate the number of molecules, this is a different question because you don't have to worry about the same probe hybridizing to two molecules. Instead, you can use the same number of hybridization probes as molecules and expect that your hybridization probes will saturate the number of molecules.