DEV : console error on open #admins or #announce share code page

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Action Performed:

Go to #announce or #admin
Go to details page
click on share code

Expected Result:
should not show any console error
Actual Result: shows console error
Workaround:
Can the user still use Expensify without this being fixed? Have you informed them of the workaround?
Platforms:

Which of our officially supported platforms is this issue occurring on?

[ ] Android / native
[ ] Android / Chrome
[x] iOS / native
[ ] iOS / Safari
[ ] MacOS / Chrome / Safari
[ ] MacOS / Desktop

Version Number: DEV
Reproducible in staging?: n/a
Reproducible in production?: n/a
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
https://github.com/Expensify/App/assets/43996225/555b1287-8c53-466d-bbda-d94d082a1e73
Expensify/Expensify Issue URL:
Issue reported by: @gadhiyamanan
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1684156128912459
View all open jobs on GitHub

I can't test on Dev so I've asked for a help a few times. Still looking for someone who can reproduce for me and link their results.

Fresh reach out for a hand here.

I've reached out a few times for help reproducing this and haven't had any luck. I'm going to send it forward for some help determining if this can be reproduced on DEV and if it should be external/internal.
Thank you for your help assignees!

@puneetlath @0xmiroslav - I'm not able to reproduce this since I don't have a dev environment but I don't want to sit on this any longer. Can you help me repro and decide if this should be external/internal.

Proposal
Updated
cover the issue video logs, and reproduce logs here.

Same issue at another place - https://expensify.slack.com/archives/C049HHMV9SM/p1684850796180919
Kindly verify this is also fixed during PR
@0xmiroslav @ahmedGaber93

@puneetlath @0xmiroslav PR now is ready for review.

Prepping for hold removal.

@0xmiroslav and @ahmedGaber93 - I've hired you for the job in UpWork. Miroslav, feel free to do the checklist and I'll update it and make the reg test GH if needed.
@gadhiyamanan - I have created a reporting job in Upwork and hired you for it as well.

Thanks @0xmiroslav, I've updated the checklist!

Everyone is paid out so I'm going to go ahead and close. Thank you, everyone, for all the hard work here!


fix #496

Fix #496.
Fix:
Replace the broken link with this link in examples/basic/app/routes/demos/about.tsx and examples/blog-tutorial/app/routes/demos/about.tsx examples.

Thank you for your help, but it looks like we've already fixed this.
If I'm wrong, please re-open this issue and we'll get it sorted out. Thanks!


Dynamically generated max complexity

Hello! 👋 First of all, thank you for Absinthe and Absinthe.Plug!
I'm wondering if the maintainers would be open to the addition of a feature to dynamically determine the max complexity per query. I'd like to be able to say something like, "User X made a query, they have Y complexity allowance left, will I allow them to make this query?"
Of course this doesn't match the primary use case. 😄
Whereas the current API looks like this:
plug Absinthe.Plug,
  schema: MyAppWeb.Schema,
  analyze_complexity: true,
  max_complexity: 50

I would like to propose expanding the API to support this as well:
plug Absinthe.Plug,
  schema: MyAppWeb.Schema,
  analyze_complexity: true,
  max_complexity: &MyModule.max_complexity/1

Where &MyModule.max_complexity/1 is a function that is given the context and query and returns back an integer.
Thank you for considering! I would be glad to whip up a PR if you're open to this. Cheers!

We do something similar to this with a custom plug that delegates to Absinthe.Plug, but it's an interesting idea. What do you think @benwilson512 ?

We do something similar to this with a custom plug that delegates to Absinthe.Plug, but it's an interesting idea. What do you think @benwilson512 ?

I think we should allow this to be set via Absinthe.put_options in a higher up plug, it generalizes a lot better. Currently we enable this with a few options https://github.com/absinthe-graphql/absinthe_plug/blob/v1.5.2/lib/absinthe/plug.ex#L301 but we should generalize this to all of the options.

I think we should allow this to be set via Absinthe.put_options in a higher up plug, it generalizes a lot better. Currently we enable this with a few options https://github.com/absinthe-graphql/absinthe_plug/blob/v1.5.2/lib/absinthe/plug.ex#L301 but we should generalize this to all of the options.

In the short term @paulstatezny you can wrap Absinthe.Plug:
defmodule MyAbsinthePlug do

  defdelegate init(opts), to: Absinthe.Plug

  def call(conn, opts) do
    complexity = complexity_for_current_user(conn)
    opts = Map.put(opts, :complexity, complexity)

    Absinthe.Plug.call(conn, opts)
  end
end

In the short term @paulstatezny you can wrap Absinthe.Plug:
defmodule MyAbsinthePlug do

  defdelegate init(opts), to: Absinthe.Plug

  def call(conn, opts) do
    complexity = complexity_for_current_user(conn)
    opts = Map.put(opts, :complexity, complexity)

    Absinthe.Plug.call(conn, opts)
  end
end

Thanks for such a quick and helpful reply! ❤

Thanks for such a quick and helpful reply! ❤

Opened a PR for this https://github.com/absinthe-graphql/absinthe_plug/pull/243

Opened a PR for this https://github.com/absinthe-graphql/absinthe_plug/pull/243


Clarify and document (or fully automate) dependencies

As a novice developer
I want the readme to clearly explain what version of python and associated packages are required to run energyPATHWAYS
so that I can do an initial test run without delay and feel confident that the software is well-documented and supported
AC

README.md should document that python 2.7 is required for reasons of library compatibility.
README.md should note that energyPATHWAYS was developed and tested using Anaconda (with a link to their site) and that it works well with the default Anaconda environment.
README.md should document which packages must be in the environment before running setup.py (and if possible setup.py should validate that these are present before running) or setup.py should be updated to install all necessary packages correctly, eliminating the external dependencies (see below).

Background on AC3
Currently if I set up an "empty" anaconda environment (without the default packages), clone a fresh copy of the repo and run python setup.py develop, several packages install correctly but then there is a failure attempting to install scipy (trace below). If I conda install numpy and then re-run setup.py, the scipy installation gets farther but errors out for lack of a fortran compiler (trace below below). I also encountered these issues during my initial attempt to set up energyPATHWAYS using my macports python environment (prior to switching to anaconda).
We should choose an approach to resolving this before working this ticket. Documenting dependencies and asking users to install packages using a third-party tool (e.g. anaconda) reduces our development effort and probably makes package installation more reliable, since such tools are widely used and well-tested. On the other hand, I presume that fixing up setup.py so it can handle all dependencies gives us finer control over package versions, if we should need that... but it's also somewhat reinventing the wheel. Both ways have pros and cons so some discussion is warranted.
First error:
Searching for scipy
Reading https://pypi.python.org/simple/scipy/
Best match: scipy 0.17.0
Downloading https://pypi.python.org/packages/source/s/scipy/scipy-0.17.0.zip#md5=28a4fe29e980804db162524f10873211
Processing scipy-0.17.0.zip
Writing /var/folders/jz/2f93p0d125344s5ggky1mt0h0000gn/T/easy_install-JqrYgH/scipy-0.17.0/setup.cfg
Running scipy-0.17.0/setup.py -q bdist_egg --dist-dir /var/folders/jz/2f93p0d125344s5ggky1mt0h0000gn/T/easy_install-JqrYgH/scipy-0.17.0/egg-dist-tmp-jYCMmj
Traceback (most recent call last):
  File "setup.py", line 16, in <module>
    'profilehooks'
  File "/Users/michael/anaconda/envs/empty/lib/python2.7/distutils/core.py", line 151, in setup
    dist.run_commands()
  File "/Users/michael/anaconda/envs/empty/lib/python2.7/distutils/dist.py", line 953, in run_commands
    self.run_command(cmd)
  File "/Users/michael/anaconda/envs/empty/lib/python2.7/distutils/dist.py", line 972, in run_command
    cmd_obj.run()
  File "/Users/michael/anaconda/envs/empty/lib/python2.7/site-packages/setuptools-19.4-py2.7.egg/setuptools/command/develop.py", line 34, in run
  File "/Users/michael/anaconda/envs/empty/lib/python2.7/site-packages/setuptools-19.4-py2.7.egg/setuptools/command/develop.py", line 133, in install_for_development
  File "/Users/michael/anaconda/envs/empty/lib/python2.7/site-packages/setuptools-19.4-py2.7.egg/setuptools/command/easy_install.py", line 720, in process_distribution
  File "/Users/michael/anaconda/envs/empty/lib/python2.7/site-packages/setuptools-19.4-py2.7.egg/pkg_resources/__init__.py", line 827, in resolve
  File "/Users/michael/anaconda/envs/empty/lib/python2.7/site-packages/setuptools-19.4-py2.7.egg/pkg_resources/__init__.py", line 1072, in best_match
  File "/Users/michael/anaconda/envs/empty/lib/python2.7/site-packages/setuptools-19.4-py2.7.egg/pkg_resources/__init__.py", line 1084, in obtain
  File "/Users/michael/anaconda/envs/empty/lib/python2.7/site-packages/setuptools-19.4-py2.7.egg/setuptools/command/easy_install.py", line 640, in easy_install
  File "/Users/michael/anaconda/envs/empty/lib/python2.7/site-packages/setuptools-19.4-py2.7.egg/setuptools/command/easy_install.py", line 670, in install_item
  File "/Users/michael/anaconda/envs/empty/lib/python2.7/site-packages/setuptools-19.4-py2.7.egg/setuptools/command/easy_install.py", line 853, in install_eggs
  File "/Users/michael/anaconda/envs/empty/lib/python2.7/site-packages/setuptools-19.4-py2.7.egg/setuptools/command/easy_install.py", line 1081, in build_and_install
  File "/Users/michael/anaconda/envs/empty/lib/python2.7/site-packages/setuptools-19.4-py2.7.egg/setuptools/command/easy_install.py", line 1067, in run_setup
  File "/Users/michael/anaconda/envs/empty/lib/python2.7/site-packages/setuptools-19.4-py2.7.egg/setuptools/sandbox.py", line 242, in run_setup
  File "/Users/michael/anaconda/envs/empty/lib/python2.7/contextlib.py", line 35, in __exit__
    self.gen.throw(type, value, traceback)
  File "/Users/michael/anaconda/envs/empty/lib/python2.7/site-packages/setuptools-19.4-py2.7.egg/setuptools/sandbox.py", line 195, in setup_context
  File "/Users/michael/anaconda/envs/empty/lib/python2.7/contextlib.py", line 35, in __exit__
    self.gen.throw(type, value, traceback)
  File "/Users/michael/anaconda/envs/empty/lib/python2.7/site-packages/setuptools-19.4-py2.7.egg/setuptools/sandbox.py", line 166, in save_modules
  File "/Users/michael/anaconda/envs/empty/lib/python2.7/site-packages/setuptools-19.4-py2.7.egg/setuptools/sandbox.py", line 141, in resume
  File "/Users/michael/anaconda/envs/empty/lib/python2.7/site-packages/setuptools-19.4-py2.7.egg/setuptools/sandbox.py", line 154, in save_modules
  File "/Users/michael/anaconda/envs/empty/lib/python2.7/site-packages/setuptools-19.4-py2.7.egg/setuptools/sandbox.py", line 195, in setup_context
  File "/Users/michael/anaconda/envs/empty/lib/python2.7/site-packages/setuptools-19.4-py2.7.egg/setuptools/sandbox.py", line 239, in run_setup
  File "/Users/michael/anaconda/envs/empty/lib/python2.7/site-packages/setuptools-19.4-py2.7.egg/setuptools/sandbox.py", line 269, in run
  File "/Users/michael/anaconda/envs/empty/lib/python2.7/site-packages/setuptools-19.4-py2.7.egg/setuptools/sandbox.py", line 238, in runner
  File "/Users/michael/anaconda/envs/empty/lib/python2.7/site-packages/setuptools-19.4-py2.7.egg/setuptools/sandbox.py", line 46, in _execfile
  File "/var/folders/jz/2f93p0d125344s5ggky1mt0h0000gn/T/easy_install-JqrYgH/scipy-0.17.0/setup.py", line 265, in <module>

  File "/var/folders/jz/2f93p0d125344s5ggky1mt0h0000gn/T/easy_install-JqrYgH/scipy-0.17.0/setup.py", line 253, in setup_package

ImportError: No module named numpy.distutils.core

Second error:
Could not locate executable gfortran
Could not locate executable f95
Could not locate executable f90
Could not locate executable f77
Could not locate executable xlf90
Could not locate executable xlf
Could not locate executable ifort
Could not locate executable ifc
Could not locate executable g77
Could not locate executable g95
Could not locate executable pgfortran
don't know how to compile Fortran code on platform 'posix'
error: Setup script exited with error: library dfftpack has Fortran sources but no Fortran compiler found

QA: @ryandrewjones

Should also note that numexpr 2.4.4 has a bug that causes intermittent inconsistent results (https://github.com/pydata/numexpr/issues/185). Fixed in 2.4.5.

@ryandrewjones, this is ready for your review. Please see the commit referenced above this comment, or equivalently the document_dependencies_9 branch, and let me know if/when you feel it's ready to merge.

@mactyr I've just committed one small change around what packages come with Anaconda by default. Anaconda does include some of the core packages for the project (ex. numpy, scipy, pandas), but doesn't have others (ex. pint). This looks ready to merge now.

Great. I made one more minor change and squashed our changes down to one commit (referenced above) for master, to avoid cluttering the history with tiny readme edits.


Fix horizontal scrolling

This fixes unwanted horizontal scrolling like explained here: https://github.com/twbs/bootstrap/issues/9862

Thanks for the PR.


removing doc files and adding readme to direct users to the gh-pages …

…branch for doc source

this is in response to #346


Luz hex

[x] I have converted fonts to outlines in the .svg
[x] My PNG has dimensions 2521 x 2911

/render


[Proposal] Support GPU

I would like to make it possible to manage GPU clusters using Infrakit.
As an idea, first of all nvidia GPU only, create a flavor to install nvidia driver and cuda.
For example, by combining cuda falvor and swarm falvor, you can build a GPU cluster with swarm.
Image of running option.
infrakit-flavor-cuda --drive=369.95 --cuda=8.0

@YujiOshima  - I have a few questions:

Are there anything specific about the CUDA flavor that we can't combine it with the swarm flavor?  For example, if we only need some command line (e.g. apt-get install ...) then can't we include them in the template instead?

What are the requirements on health checks that are special for this use case?

What about labeling of the nodes / Docker engines on these nodes?

What are the rolling update / update semantics for the use cases for a) training and b) inference (serving)?   Is your use case focusing only on training?   I think it would be nice to look at how we can support serving / inference as well, since that's when rolling updates etc make the most sense (pushing out a new model, updating tensorflow serving etc.)

I believe tensorflow supports checkpointing during training.  I think we would have to take this into account because we don't want hours of training be destroyed by a simple config change on our side.   For this, I can see how a flavor plugin's Drain would be helpful.

Telemetry -- how can we combine metrics such as CPU/GPU utilization, with events in infrakit?

Storage -- how are we provisioning disks and possibly other blob storage like Cepth so that the TF jobs can easily access storage?

How does the user launch a training session -- through a docker run or deploy a k8s batch job ?   Is the cluster multi-tenant?

@chungers

I want to separate nvidia driver layer and application layer, to manage swarm and app without conscious of nvidia driver version. For example at default, Docker needs to volume mount /usr/lib/nvidia-3xx.

Health checks is pretty difficult as nvidia command does not have remote api so far as I know. May be we need to set agent and check nvidia-smi and libs etc.

I think docker swarm flavor or instance plugin are responsible for it.

Yes, inference and serving are big usecase. Docker swarm or kubernetes are responsible for tensorflow application rolling update. GPU flavor is responsible for Nvidia driver or cuda update. Of course it need to support their update and need to cooperation with swarm flavor.

Yes, it's important problem. For now, it is manage at tensorflow layer in container.
Although it is ideal that users can drain without conscious of jobs in operation, it is necessary to carefully consider the design of physical devices, cluster orchestrator and applications. For example, to have shared storage or to always share as kv-store, and on which layer to provide it.

Same as health checks, how about set some agents to nodes?

Not only Tensorflow but also discussions on how Infrakit treats resources. I think that there is no specific requirement for machine learning applications like current TF.

In my thought, using k8s batch job. And in my usecase, it is multiuser but not multi-tenant.

@YujiOshima
Thank you for your comments.  I think there are a couple of areas we can work on:
1.  Metrics / health

Health checks is pretty difficult as nvidia command does not have remote api so far as I know. May be we need to set agent and check nvidia-smi and libs etc.

Same as health checks, how about set some agents to nodes?

Unless there are specific requirements, I think instead of developing local agent, we should look at integration with Prometheus.  We can then install node_exporter and nvidia_exporter on the host.   Monitoring and alerting would then follow the standard Prometheus set up (e.g. Grafana, etc)
If we care about cluster autoscaling, then I see an area of integration where alerts or thresholds from Prometheus can trigger events to Infrakit to scale up the cluster.  This can mean

Change the allocation size of the gpu group which calls the MAAS plugin to provision a new host (if one is in inventory).  If inventory not available, then create work request for a new GPU host buildout.
Depending on if you want to do GPU virtualization, once a bare-metal host is provisioned, a libvirt/kvm plugin is used to provision a vm instance that has a dedicated GPU bound to it.

2. Interaction with higher-level orchestrators (e.g. k8s / swarm).
There are two directions:

infrakit to container orchestrator  ==> drain a particular node prior to update
Container orchestrator to infrakit ==> scale up / down
For the first one, we already have the Drain method defined in the Flavor plugin for k8s and swarm.  So we just need to add the implementations.  We can use the existing swarm and k8s flavors.

For the second case, the outside-facing API is not yet defined.   As a concrete example, for k8s, we can create an API that easily maps to their cloudprovider spi of their cluster autoscaler: https://github.com/kubernetes/autoscaler/blob/master/cluster-autoscaler/cloudprovider/cloud_provider.go#L29
This is what I meant when I suggested "Infrakit Apps": an application-specific API that can be implemented on top of Infrakit primitives.   So this would be the 'scale group' API for applications that sit on top of infrakit in the stack.  It would also interface with the metrics/health in part 1 so that cluster scale up/down can be triggered by thresholds, etc.
I'd like to get this started and hopefully reconcile with the work you've already done in #474 so that they fit cleanly within the overall architecture of infrakit.  Is that ok with you?

Thank you @chungers !
Rather than developing original agent, I agree to use Prometheus's metrics.
But I am not sure of the relationship between Infrakit and Prometheus.
Apart from Infrakit, deploy Prometheus and Infrakit's health check communicates with Prometheus Server?

Infrakit to container orchestrator ==> drain a particular node prior to update
Container orchestrator to infrakit ==> scale up / down

Please let me confirm my understanding.
First is that the drain function of flavor sends an instruction to container orchestrator, moves the container from one node to another, and deletes the node.
The second is to send autoscale instructions of kubernetes to infrakit app instead of cloud provider, right?
For example, if you deploy k8s to aws you have two choices, whether to make a cloud provider aws or infrakit.
Without aws it will be impossible to link natively with ECR. I am worried about whether this will confuse users.
The idea of providing an API for communicating with the cluster for each container orchestrator in APP is agreeable as it increases flexibility.

@YujiOshima

Rather than developing original agent, I agree to use Prometheus's metrics.
But I am not sure of the relationship between Infrakit and Prometheus.
Apart from Infrakit, deploy Prometheus and Infrakit's health check communicates with Prometheus Server?

I think maybe the first thing we should do is to define "health".  What are the metrics that you'd care about (e.g. with NVML) that would be appropriate for infrakit?    In other words, what metrics, besides the host disappearing altogether, would you care to monitor so that when it changes past certain thresholds, infrakit should start spinning up a new host?  From the list at NVML, I can see metrics like active compute process and the GPU utilization would be useful.
Once we defined what "health" is, we can decide how to collect this data and report to infrakit.  Because node exporter and the nvidia_exporter all listen on network ports, we can have a flavor plugin that polls or scrapes the data from the nodes.  This is similar to how the Prometheus server would do, but if our flavor plugins can scrape the data directly, then Prometheus server can be optional.
Does this seem reasonable?  It's pretty easy to build a collector of prometheus data and in turn implement our flavor's Health method.   I think we can even build it generically so that it works for whatever Prometheus monitors -- we just need to have the agent/exporters running on the hosts.

Please let me confirm my understanding.
First is that the drain function of flavor sends an instruction to container orchestrator, moves the container from one node to another, and deletes the node.

Yes.

The second is to send autoscale instructions of kubernetes to infrakit app instead of cloud provider, right?
For example, if you deploy k8s to aws you have two choices, whether to make a cloud provider aws or infrakit.

Yes - in essence infrakit acts like an autoscaling group.  On AWS yes you could use their ASG, but we can support specialized use cases like retaining the EBS volume where you may have checkpointed and restorable containers.   This may be useful especially for training that has been running for some time and you want to be able to resume cleanly.  I don't think you can do this easily with ASG.  Of course, in the on-prem cases, there are no autoscaling groups so we can definitely fill that gap.

Without aws it will be impossible to link natively with ECR. I am worried about whether this will confuse users.
Are you using ECR?  Do we need some integration with it?   Are you also using the GPU instances on AWS or do you have on-prem / bare-metal hosts?

The idea of providing an API for communicating with the cluster for each container orchestrator in APP is agreeable as it increases flexibility.
We will revisit your infrakit app PR because they are related in terms of how these "apps" fit with the rest of the architecture.  I will start a PR soon and have you take a look and see if that make sense.  The tricky part is that we need to have a single endpoint for higher-level systems to access, but in HA mode, our daemons run on different hosts.  So this API endpoint needs to be able to route traffic to the current leader.

I think the API will be REST instead of JSON-RPC or GRPC.  What do you think?


Testing for CLI main commands; Automated coverage

Fixes https://github.com/Shopify/internal-cli-foundations/issues/432

Adds tests for the commands in CLI main
Adds an automated coverage message for packages supporting test coverage (main + CLI kit)

What about adding a section to this page where we explain how we expect the reported data to be used?

Once we've got a baseline from main in place, we should have something we can screenshot and decide what to do with.


Add support to where queries beginning with a constant

        [Fact]
        public void start_with_constant()
        {
            theSession.Store(new Target{Color = Colors.Blue, Number = 1});
            theSession.Store(new Target{Color = Colors.Blue, Number = 2});

            theSession.SaveChanges();

            theSession.Query<Target>().Where(x =>  2 == x.Number).ToArray()
                .Select(x => x.Number)
                .ShouldHaveTheSameElementsAs(2);
        }

Not my style of writing a where query, but should be supported I believe

Fixed by GH-154


Lock Support Model: YD_BT1 (Wyze Lock Bolt)

Is your feature request related to a problem? Please describe: Wyze Door lock model YD_BT1 does not work

Describe the solution you'd like: I'd like added support for this lock

Describe alternatives you've considered: If there are any workarounds I'd love to know them. It is a Bluetooth device so I am not sure if it is possible but my Pi does have Bluetooth so I feel like it should be. I've considered using the camera as a work around. I know pairing it means it connects to Wi-Fi through the camera so if you can add lock functionality through that, that would work as well.

Additional context:

I would like this too. Thanks.

The Wyze Lock Bolt is bluetooth only so not sure it will be controllable by Homebridge.

Not much I can do at this time.


Update property in sample project.

Refs: https://github.com/microsoft/azure-spring-boot/pull/919

Hi, @saragluna ,
Please review and merge it. 🙏


TokenManagement class not initializing nor returning any instance.

TokenManagement class not initializing, I have even debugged the lib/tokens/index.js but it is not returning any instance of tokenManagement class.
"@binance-chain/javascript-sdk": "^2.15.0"
I am using this version of the sdk

Hello, @shakeib98
Please your code please, thanks!

I had the same issue. I was getting an Error: Private key cannot be null when Transaction.sign got called. The private key was being set correctly, but the this._bncClient was not the same as the parent BncClient instance.
I solved the problem with a little hack:
// token.ts

const issue = (client: any) => {
  return async (
    senderAddress: string,
    tokenName: string,
    symbol: string,
    totalSupply: number,
    mintable: boolean,
  ): Promise<{result: any; status: number}> => {
    try {
      client.tokens._bncClient = client; // <== Replace the client.tokens._bncClient with the passed BncClient
      const res = await client.tokens.issue(senderAddress, tokenName, symbol, totalSupply, mintable);
      return res;
    } catch (error) {
      throw error;
    }
  };
};

Then use it like this:
export const getClient = async (network: string): Promise<any> =>
  new Promise((resolve, reject) => {
    const client = new BNBApiClient(getNetworkURI(network));
    client.chooseNetwork(network);
    resolve(client);
  });

const client = await getClient(network);
await client.initChain();
await client.setPrivateKey(privateKey);
const res = await token.issue(client)( // <== Pass the initialized BncClient
    senderAddress,
    tokenName,
    symbol,
    totalSupply,
    mintable,
);
if (res.status === 200) {
   // do things
}

This hack is due to a singleton in the TokenManagement constructor that is not assigning the initialized BncClient:
class TokenManagement {
  static instance

  /**
   * @param {Object} bncClient
   */
  constructor(bncClient) {
    if (!TokenManagement.instance) {
      this._bncClient = bncClient
      TokenManagement.instance = this
    }

    return TokenManagement.instance
  }

The BncClient is passed its own instance to the this.tokens variable in its constructor:
/**
 * The Binance Chain client.
 */
export class BncClient {
  /**
   * @param {String} server Binance Chain public url
   * @param {Boolean} useAsyncBroadcast use async broadcast mode, faster but less guarantees (default off)
   * @param {Number} source where does this transaction come from (default 0)
   */
  constructor(server, useAsyncBroadcast = false, source = 0) {
    if (!server) {
      throw new Error("Binance chain server should not be null")
    }
    this._httpClient = new HttpRequest(server)
    this._signingDelegate = DefaultSigningDelegate
    this._broadcastDelegate = DefaultBroadcastDelegate
    this._useAsyncBroadcast = useAsyncBroadcast
    this._source = source
    this.tokens = new TokenManagement(this) // <== HERE
    this.swap = new Swap(this)
    this.gov = new Gov(this)
  }

TokenManagement class not initializing, I have even debugged the lib/tokens/index.js but it is not returning any instance of tokenManagement class.
"@binance-chain/javascript-sdk": "^2.15.0"
I am using this version of the sdk

Can you show me your code?

@netpoe
export const getClient = async (network: string): Promise<any> =>
  new Promise((resolve, reject) => {
    const client = new BNBApiClient(getNetworkURI(network));
    client.chooseNetwork(network);
    resolve(client);
  });

const client = await getClient(network);
await client.initChain();
await client.setPrivateKey(privateKey);
const res = await client.token.issue(
    senderAddress,
    tokenName,
    symbol,
    totalSupply,
    mintable,
);
if (res.status === 200) {
   // do things
}

Why don't you just write like this?


feat(breadcrumb): introduce overflow menu

Related Ticket(s)
#442
Description
Introduce horizontal overflow menu for breadcrumb

Changelog
New

added breadcrumb overflow menu for each of the stories and updated docs
created a new component bx-breadcrumb-overflow-menu
added styles for overflow in breadcrumb

would we want to handle keyboard nav for overflow menu before merging this or would a follow up PR be more preferable? related #103

I think handling #103 separately makes sense. this really isn't touching the actual overflow-menu just adjusting styles to allow for users to also use it here.


Trying AMI login in a background thread (MONO)

I'm running in MONO <IP_ADDRESS> - linux
If I try to login in a background thread, it doesn't work, do you know why?
var manager = new Manager(host, port, user, pass);
Task.Factory.StartNew(()=> manager.Login());

Asterisk debug: Connect attempt from 'IP' unable to authenticate
Net debug:
_AsterNET.Manager.TimeoutException: Timeout waiting for protocol identifier
  at AsterNET.Manager.ManagerConnection.login (Int32 timeout) <0xb3e08168 + 0x00618> in <filename unknown>:0
  at AsterNET.Manager.ManagerConnection.Login (Int32 timeout) <0xb3e07e88 + 0x0001b> in <filename unknown>:0
  at UCB.Service.UCBServer.LoginAsterisk () <0xb3e06e08 + 0x000f3> in <filename unknown>:0

In the same thread works:
var manager = new Manager(host, port, user, pass);
manager.Login()

Running on Windows it works just fine thou

Does this work when not using mono?

Yes... it does...
One other thing, when using MONO, is that when manager tries to reconnect it does not send user/password and asterisk rejects the reconnection...
Unfortunately, project needs to run on MONO, so we're having a hard time :)

This is fixed in #140.


Add loading/eager/lazy descriptions

I intend on adding HTML attribute/tag completion to Shopify Liquid HTML templates by using this repo's data.
I noticed that the img#loading data was lacking a description. The loading ValueSet did as well.
This PR adds the description for this attribute and value set as per what's on MDN at the time of making this PR.
MDN reference
Submission containing materials of a third party: Docs from MDN which should be covered by the "reference."

@microsoft-github-policy-service agree company="Shopify"


Problem with logger

I find if I rerun my test code using open_cp logger : log_to_stdout, there will be two logger with same logs in the console.
Would it be possible to add some detection of whether there are existing loggers to avoid this problem?
In my local code, I just add if (len(logger.handlers)==0): in log_to_logger function.

Many thanks for the continued feedback!
I think maybe this is again a case of out of date code.  The current code contains the method:
_current_handler = None

def _set_handler(handler):
    logger = _logging.getLogger("open_cp")
    global _current_handler
    if _current_handler is not None:
        logger.removeHandler(_current_handler)
    _current_handler = handler
    logger.addHandler(handler)

The purpose of this is to stop two loggers being attached at the time.  In a test script:
import open_cp.logger
import logging

open_cp.logger.log_to_stdout()
open_cp.logger.log_to_stdout()

logger = logging.getLogger("open_cp.matt")
logger.debug("A message")

I see only one message.
Can you verify that this is still a problem, and if so, post a minimal working example?

Thanks for quick response.
I updated the code and ran the code you offered. If I run the code run for once, no repeated logs. However, if I run it again, then the logs repreat.
In [1]: runfile('F:/Git/PredictCode/tests/logger_test.py', wdir='F:/Git/PredictCode/tests')
2017-07-20 03:05:46,280 DEBUG open_cp.matt - A message

In [2]: runfile('F:/Git/PredictCode/tests/logger_test.py', wdir='F:/Git/PredictCode/tests')
Reloaded modules: open_cp, open_cp.logger, open_cp.data
2017-07-20 03:05:48,340 DEBUG open_cp.matt - A message
2017-07-20 03:05:48,340 DEBUG open_cp.matt - A message

Ah, right...  In a Jupyter notebook, I can recreate this using importlib:
import open_cp.logger
open_cp.logger.log_to_stdout()
logger = logging.getLogger("open_cp.matt")
logger.debug("A message")

import importlib
importlib.reload(open_cp.logger)

open_cp.logger.log_to_stdout()
logger.debug("A message")

Two messages!
I guess importlib resets the global variable(s) in open_cp.logging but not those in the logging module.
I've fixed this in a way whereby we can recognize an existing logger across a reload.  I want to leave the option of allowing the user to genuinely add another logger themselves.
See commit #26712d7


Filter for one particular interface

First, thanks for fixing the documentation error.
I have another question, if I just want to display one particular interface, how can I filter by interface name instead of getting all the interfaces ? Is there a way to pass in a filter on the following ?
  "interface":      "<get-interface-information/>",

So, without doing any code modifications, you could just grab all the interfaces with the function like it currently does, and then when iterating over them, look for a particular interface, e.g.:
for _, int := range ifaces.Entries {
	if strings.Contains(int.Name, "ge-0/0/1") {
		// Do stuff
	}
}

Would this suffice, or is there a need to only grab a single one without using the above example?

I can certainly do this. But it is not efficient. I find you can do:
...
but it will only match physical interface. for logical interface attached to physical interface, it will not work. Is there a way to fix this ?

I find you can do:
name

<get-interface-information><interface-name>...</interface-name></get-interface-information>

I will see about adding this feature/option. Should have something ready after the weekend :)

I will see about adding this feature/option. Should have something ready after the weekend :)

@MaxBear I just updated this repo with your suggested changes. You can now optionally specify a physical interface, and it will include only that interface, as well as all logical ones tied to it, e.g.:
View("interface", "ge-0/0/0")

Thanks for making the change, Scott. Do you know why when run cli
show interface <logical interface> | display xml
will display one logical interface output. But this will not work for RPC calls ?

Most likely because I have it tied to just a physical interface. I should probably change that so that any interface will work, even logical ones (if you don't need to see the physical). I'll work at fixing that.

If you can fix it, that will be great, thanks !


New PR to test SignCLA at 2020-01-09 17:26:09.828508244 -0800 PST m=+4.134102984

Body of PR

unsigned-fail-fork-staging: test succeeded


Add subnet output designed to work OOTB with the ocp-base module

Description
See https://github.com/terraform-ibm-modules/terraform-ibm-base-ocp-vpc/pull/15#discussion_r1118594503
I think we should add an output designed to be consumed by the ocp module in the vpc module to ease integration between the 2 modules.
New or affected modules

terraform-ibm-base-ocp-vpc module

By submitting this issue, you agree to follow our Code of Conduct

Placing in correct repo https://github.com/terraform-ibm-modules/terraform-ibm-landing-zone-vpc/issues/399


MSC1703: encrypting recovery keys for online megolm backups

Rendered: https://github.com/matrix-org/matrix-doc/tree/dbkr/encrypted-recovery-keys/proposals/1687-encrypted-recovery-keys.md
This is an expanded version of MSC1687

hm, this would be much easier to review if it were wordwrapped

So, it feels there are three actual options here:
1a. Generate the recovery key from the passphrase (vuln to dictionary attacks on the server)
1b. Generate the recovery key randomly, and then encrypt it with a key derived from the passphrase (the original plan)
3. Generate a backup encryption key from random; a passphrase-derived key (which is then XORed with the backup encryption key); and a recovery key from random (which is also then XORed with the backup encryption key). I'm not clear on how these interweave together, or the benefits they bring.
What are we actually proposing in practice?  I'm a bit confused as to what option 3 buys us over option 1b?

My suggestion here is to go with 1a (now just 1 in my renumbering). The summary is that I don't think there's any realistic way of mitigating the dictionary attack: option 2b. runs through a proposed mitigation and why it doesn't really work.
The kicker is that the user will get a new recovery key whenever they change their passphrase. Options 3 adds the ability to retain the same recovery key when you change your passphrase, so if we want that feature, option 1 won't suffice. It sounds like we don't though.

this is much clearer now; thanks. let's just say "for now let's just generate the key from the passphrase and go with option 1" as a conclusion on the MSC and give it a go.

Yup, option 1 seems to be sufficient, and is simpler.

Option 1 does indeed look easiest, even with the potential risk documented later in the proposal. It's also the option that was proofed in riot-web, correct?

[It's now the only MSC for encrypting recovery keys for online megolm backups]

Is there a reason why PBKDF2 is used instead of the state of the art Argon2 ?
Reference: https://password-hashing.net/

Mainly because there are more implementations of it.  In particular, it's in WebCrypto.

Mainly because there are more implementations of it. In particular, it's in WebCrypto.

OK. I think it would be nice to have an attribute specifying the key derivation algorithm though, to make it easier to switch to a different one.
I cannot find quantitative results on state-of-the-art PBKDF2 cracking but I keep reading that PBKDF2 is very weak against ASICs.

This proposal is obsoleted by https://github.com/matrix-org/matrix-doc/pull/1946


add the 'code' and 'column' fields to analysis issues

add the 'code' and 'column' fields to analysis issues

[x] I’ve reviewed the contributor guide and applied the relevant portions to this PR.

Contribution guidelines:

See our contributor guide for general expectations for PRs.
Larger or significant changes should be discussed in an issue before creating a PR.
Contributions to our repos should follow the Dart style guide and use dart format.
Most changes should add an entry to the changelog and may need to rev the pubspec package version.
Changes to packages require corresponding tests.

Note that many Dart repos have a weekly cadence for reviewing PRs - please allow for some latency before initial review feedback.

LGTM
Please note, landing this has to be aligned with publishing the updated front end, otherwise the front end will be sad and not work.

I'm assuming that the frontend just won't see these fields - that the previous protos and generated files will still work against a newer backend?

It's not critical that these fields be available right away, it would just be nice for them to be there eventually.

LGTM

Please note, landing this has to be aligned with publishing the updated front end, otherwise the front end will be sad and not work.

I'm assuming that the frontend just won't see these fields - that the previous protos and generated files will still work against a newer backend?

No, it is serving as JSON. I have a maintenance task to rip out protobuf and replace it with one of the JSON code generation approaches, but I've never had the time to revisit.
You need to push both at the same time. I've caused outages recently by landing the backend before the front end was ready to land.

It's not critical that these fields be available right away, it would just be nice for them to be there eventually.

Do you want to mark this PR as a Draft until you are ready to add the fields to the front end?

@domesticmouse - feel free to land these 2 PRs now or whenever we're ready to do the next push


Crash occuring during TLS reset (IDFGH-799)

Environment

Development Kit: custom board
Module or chip used: ESP32-WROOM-32D
IDF version: v3.1.3
Build System: Make
Compiler version: xtensa-esp32-elf-gcc (crosstool-NG crosstool-ng-1.22.0-80-g6c4433a) 5.2.0
Operating System: Linux

Problem Description
Occasionally the reset of a TLS session crashes with a guru meditation error. Problem also occurs with sdkconfig reset at default values.
Debug Logs
D<PHONE_NUMBER>.728727) HTTP_CLIENT: Code: 2999; Message: D (318819) HTTP_CLIENT: Begin connect to: https://xxxxxxxxxxx:443
D<PHONE_NUMBER>.741048) TRANS_SSL: Code: 2999; Message: D (318829) TRANS_SSL: Cleanup mbedtls
Guru Meditation Error: Core  0 panic'ed (StoreProhibited). Exception was unhandled.
Core 0 register dump:
PC      : 0x4000c46c  PS      : 0x00060930  A0      : 0x8017a1c4  A1      : 0x3ffd95f0
A2      : 0x00000000  A3      : 0x00000000  A4      : 0x0000414d  A5      : 0x00000000
A6      : 0x3f422114  A7      : 0x00000414  A8      : 0x00000000  A9      : 0x3ffd9560
A10     : 0x3ffe247c  A11     : 0x40082e2c  A12     : 0x3f422114  A13     : 0x00000bb7
0x40082e2c: _free_r at /home/solytic/git/esp-idf/components/newlib/syscalls.c:41

A14     : 0x3ffe247c  A15     : 0x00000001  SAR     : 0x00000004  EXCCAUSE: 0x0000001d
EXCVADDR: 0x00000000  LBEG    : 0x4000c46c  LEND    : 0x4000c477  LCOUNT  : 0x00000413
Backtrace: 0x4000c46c:0x3ffd95f0 0x4017a1c1:0x3ffd9600 0x4017a225:0x3ffd9620 0x40176397:0x3ffd9640 0x401767c3:0x3ffd9660 0x4019a42d:0x3ffd96b0 0x40175bc2:0x3ffd96d0 0x40175da8:0x3ffd9710 0x4011fee1:0x3ffd9730 0x401227cc:0x3ffd9750 0x40122965:0x3ffd9940
0x4017a1c1: ssl_session_reset_int at /home/solytic/git/esp-idf/components/mbedtls/mbedtls/library/ssl_tls.c:6781

0x4017a225: mbedtls_ssl_session_reset at /home/solytic/git/esp-idf/components/mbedtls/mbedtls/library/ssl_tls.c:6781

0x40176397: ssl_close at /home/solytic/git/esp-idf/components/esp_http_client/lib/transport_ssl.c:227 (discriminator 6)

0x401767c3: ssl_connect at /home/solytic/git/esp-idf/components/esp_http_client/lib/transport_ssl.c:164

0x4019a42d: transport_connect at /home/solytic/git/esp-idf/components/esp_http_client/lib/transport.c:223

0x40175bc2: esp_http_client_open at /home/solytic/git/esp-idf/components/esp_http_client/esp_http_client.c:992

0x40175da8: esp_http_client_perform at /home/solytic/git/esp-idf/components/esp_http_client/esp_http_client.c:992

@michelesolytic Can you please also analyze heap statistics (minimum free heap, largest available block etc.) when this happens? Also if possible it would be great if you can share your application that successfully reproduces this problem.

Hello Mahavirj!
I don't have heap statistics with me, I will try to make some in the future. I am narrowing down the problem and I believe this occurs either when reusing a connection whose esp_http_client_perform() failed, and/or concurrent connections are taking place. I'll try to develop a test application to narrow down the issue.
Just to be sure: isn't the HTTP stack supposed to be able to handle concurrent connections?

@michelesolytic

Just to be sure: isn't the HTTP stack supposed to be able to handle concurrent connections?

Sorry I missed your question, yes this should work. Do you have any update on example code that can reproduce this issue reliably?

@michelesolytic I will close this due to lack of response, but please feel free to raise issue if still exists.


Auto populate fuel code

#1129
Added a pre-populate function after selecting a fuel code version (user will be prompted)
Changelog:

Added Callable Modal for front-end
Added a new route for getting the latest fuel code
Added a way to disable caching for autocomplete
Added front-end test for formatting the facility nameplate
Added back-end test for getting the latest fuel code
Code linting

 Fuel Codes | Autopopulate input fields for new fuel code versions |13|


Add an ability to add custom info chips to the banner cards

Sometimes we want to expose some inner parameters of a banner to classify or label them.
A banner name is a great place to do this. This method has its limitations. We can't put exit URLs there, often we have a limited amount of symbols or placements.
So having a second place for these labels would be great, avoiding any limitations.
This can be helpful for QAs, PMs, and of course us developers.
This PR provides such a place. In order to use it just define an "info" property in the "settings" of the banner:
"info": {
    "ClickTAG": "${content.clickTag}",
    "ClickTAG Type": "${content.clickTagType}"
},

This feature is hidden under the gsdevtools flag we use for GSAP timeline.
Here you can see the end result with BMW banners.

Nice idea to add optional info! I would say for now it's approved, maybe design-wise in the future we could style it as just text (subject: value) for example, the buttons are a bit too much but that is my opinion.


TURBO_PREFLIGHT=true or 1 vs --preflight is not behaving the same

Verify canary release

[X] I verified that the issue exists in the latest Turborepo canary release.

Link to code that reproduces this issue
Can't create sorry :(
What package manager are you using / does the bug impact?
pnpm
What operating system are you using?
Mac
Which canary version will you have in your reproduction?
1.12.5
Describe the Bug
I'm using a super simple self hosted remote cache only 130 lines of code. It's using the preflight request to redirect the downloading and uploading cache files with AWS S3 presigned urls and it's only working if provide preflight as argument to the task run and not as environment variable. That makes me believe it's broken.
I've created this ticket that I initially thought only were a typo in documentation.
I made some new tests and saw different behaviour if I passed as env or as argument to the task. They missed the cache and wasn't uploading.
Expected Behavior
turbo build --preflight should equal TURBO_PREFLIGHT=true turbo build as documentation states.
To Reproduce
Run:
turbo build --preflight
Then:
TURBO_PREFLIGHT=true turbo build
TURBO_PREFLIGHT=1 turbo build
See different behaviour if you are using remote cache server.
Additional context
No response

@chris-olszewski Do you know how handsome you are. Thanks! 🥂


Fix modal calling onClose twice

Fixes #333
In oruga-next, the close event was being sent twice. Both this.$emit('close') and this.onClose.apply(null, arguments) send the close event. We can delete either of those statements to get a single close event to fire. I chose to delete this.$emit('close') because it wasn't sending arguments.
This double close event behavior does not seem to happen in oruga, so I did not make any changes there.

The oruga and oruga-next code is the same.
Your PR doesn't look correct because the modal won't emit the close event.

@jtommy This appears to be a difference between vue2 and vue3. In vue3, if there is a function prop called onSomething, and we execute this.onSomething.apply, it will emit the something event. That's why we are seeing the close event is getting emitted twice in oruga-next, but only once in oruga.
I have made an example to illustrate this in vue3 outside of the  context of the oruga project:
https://codesandbox.io/s/nervous-rgb-zs2dke?file=/src/components/HelloWorld.vue
HelloWorld executes both this.$emit("foo") and this.onFoo.apply(null, arguments)
App.vue subscribes via @foo and shows an alert. If you click the "hello world" button you will see the alert fires twice, signifying that both this.$emit("foo") and this.onFoo.apply(null, arguments)
So, if we want the event to only fire once, we need to delete either $emit('close') or the onClose.apply in oruga-next.

Really?? And it's an official Vue 3 behavior?

I'm not sure if that was the Vue team's intention, I'm just reporting what I'm seeing as the cause for #333 😄 . I'm pretty new to Vue, so no doubt you are much more familiar with it. Happy to make changes if you see a better solution.
BTW I was able to reproduce #333 in the oruga-next docs application in the develop branch. I added a @close=close to the first modal here and a close() function that simply executes console.log().
Additionally there are multiple ways to open modals and get close events, so it's possible I've overlooked something, but this solution did not seem to break any of the examples in the docs application, or the @close= callback.

@jtommy I'm not sure if that was the Vue team's intention, I'm just reporting what I'm seeing as the cause for #333 😄 . I'm pretty new to Vue, so no doubt you are much more familiar with it. Happy to make changes if you see a better solution.
BTW I was able to reproduce #333 in the oruga-next docs application in the develop branch. I added a @close="close" to the first modal here and a close() function that simply executes console.log().
Additionally there are multiple ways to open modals and get close events, so it's possible I've overlooked something, but this solution did not seem to break any of the examples in the docs application, or the @close= callback.

@jtommy What do you want to do here? It seems like either this.$emit('close') or this.onClose.apply(null, arguments) needs to be removed in oruga-next if we want this callback to fire only once. Unless you see something I don't. 😄
Happy to make any changes, or set up the docs sites to demonstrate the issue if that would help. (IIMO, I don't think the close callback is important enough to be a permanent addition to the docs site though).

@travatomic probably in vue 3 event are passed as props with on[EventName]


Handling null objects on json schema validation

Goals :
Affected keyword : Then I expect response data schema complies to {json file}

should be able to handle null object as value

@jmagaru fixed in 1.7.1
Then I expect that path "path" from body has value of null
Then I expect that the stored value in "variable" is null


[Refactor] Ongoing Refactoring Process

Currently, there are three main files under the project's root directory. Due to an ongoing refactoring process, the initial vincent_main.py utilized a global approach for many variables, making it challenging to fully package. As a result, we have the current state of main.py, which represents a preliminary packaging effort. However, it still falls short of the perfection we are aiming for.
To address these limitations, a new ho_main.py has been introduced. It relies entirely on self-defined update functions with the hope of improving the existing issues. Nevertheless, the presence of these three main files can be confusing for code reviewers.
Once we confirm that ho_main.py can achieve the same functionality as main.py, we will retain only ho_main.py, eliminating the redundancy caused by the coexistence of multiple main files.

Since the current main.py has undergone refactoring, this functionality needs to be reintegrated. The integration should take place within the Refinaid.gui module.


Add words "Ravishing", "Entrance" and "Beguile"

Add words Ravishing, Entrance and Beguile
Add all the definitions of Ravishing in a file named Ravishing.json in folder R
Add all the definitions of Entrance in a file named Entrance.json in folder E
Add all the definitions of Beguile in a file named Beguile.json in folder B
Refer Contribution.md for more details on how to contribute.
Comment here if you're are working on this issue to avoid conflicts.
Add reference to this issue i.e Issue #400 in your pull request description.

working


To add working steps in sum of first n series 3,6,11,....

Is your feature request related to a problem? Please describe.

A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

Describe the solution you'd like

A clear and concise description of what you want to happen.

Hi, I want to work on this issue I will start working on it as soon as I get assigned!! I am a part of GSSoC'21.
Kindly assign this issue to me!
Discord Username : Abhijeet Sinha(P)
Discord Tag: #4018


Improve Docs

Community Contribution
Link to live project, video, or image:

Sharing

[ ] I would be happy to have my project shared on The Coding Train's social media!

Instagram:
Twitter:

So you had to read to change it but still chose to make a spam PR


created counting_sort.py

i had sort the counting by python and also add additional features .
please check

Its not any competitive programing question.
if it is mention the link
Read the Readme.md file for details
please PR in respected file!!


Systemd unit: Do not send falco alerts to /var/log/messages by default

Signed-off-by: Domenico Chirabino<EMAIL_ADDRESS>What type of PR is this?
/kind bug
Any specific area of the project related to this PR?
/area engine
What this PR does:
This PR set StandardOutput to null in the systemd unit configuration falco.service.
Why we need it
After the migration from initd to systemd (#1448), when falco is installed via systemd it writes to /var/log/messages by default.
The problem is not present when manually running Falco (without using systemd).
This is due to the default value in the systemd configuration: DefaultStandardOutput=journal (which falco inherits), so that Falco standard output is redirected to /var/log/messages (see https://manpages.debian.org/wheezy/systemd/systemd.conf.5.en.html).
At the time of writing a workaround is to disable stdout_output:
stdout_output:
  enabled: false

I think that falco should not write to system logs by default. Moreover, asking users to disable stdout_output (enabled by default) may be misleading and confusing (ie. I want stdout_output enabled so I can start falco manually for debugging or for testing rules)
Which issue(s) this PR fixes:
Fixes #1673
Special notes for your reviewer:
Thanks for your time :)
/cc @leogr
Does this PR introduce a user-facing change?:
fix(scripts): correct standard output redirection in systemd config (DEB and RPM packages)

@chirabino: Adding the "do-not-merge/release-note-label-needed" label because no release-note block was detected, please follow our release note process to remove it.

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: chirabino
To complete the pull request process, please assign fntlnz after the PR has been reviewed.
You can assign the PR to them by writing /assign @fntlnz in a comment when ready.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

Welcome @chirabino! It looks like this is your first PR to falcosecurity/falco 🎉

/milestone 0.30.0

LGTM label has been added.  Git tree hash: a0ff8fb9f25322faa0233cf087984753f2d3c2cb

I can kind of agree that falco logs shouldn't go to /var/log/messages by default. But with this change, where are falco alerts logged when run under systemd?

I can kind of agree that falco logs shouldn't go to /var/log/messages by default. But with this change, where are falco alerts logged when run under systemd?

Short answer: alerts will be still sent to syslog since the syslog_output is enabled by default :point_down:
https://github.com/falcosecurity/falco/blob/7c98d0047cb4e926eb0147bc6142dac9e41c0e12/falco.yaml#L154-L155
TL;DR
Actually, this issue is trying to fix a problem introduced in 0.28.0 by https://github.com/falcosecurity/falco/pull/1448 and does not prevent alerts from being sent to syslog.
Before that version, Falco was shipped with the initd configuration. syslog_output was the way to deliver alerts. Moreover, standard output was discarded by initd.
Starting from 0.28.0, when Falco migrated to systemd, the problem was introduced. Basically,  systemd redirects (by default) the Falco's standard output to journal too (or to other destinations, depending the system configuration), while the syslog_output is still enabled. The final result is that we are getting duplicated log lines in /var/log/messages (you can find an example in this comment).
Luckily, the systemd's behavior can be configured (see StandardOutput= in https://manpages.debian.org/wheezy/systemd/systemd.exec.5.en.html).
Indeed, this fix just tells systemd not to copy the Falco standard output to /var/log/messages, avoiding duplicated log lines. Thus, the expected result is to restore the original Falco behavior (pre 0.28.0).
Note: It's been a long time since I've experienced this problem, so that I may have forgotten something. Also, I may be missing something, so make sure my reasons are correct :smile_cat:

Sounds good, as long as there's some output channel still enabled.

/approve

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: chirabino, leogr
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [leogr]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

Sorry for necrobumping; does anyone remember why the patch was only applied to rpm service, and not debian too?

Sorry for necrobumping; does anyone remember why the patch was only applied to rpm service, and not debian too? @leogr @chirabino

IIRC correctly, either the Debian default was different (so the issue was not present there) or we just forget it.


Example - styling with emojis

I'm following this: https://wilsonmar.github.io/git-messages/ for some time now and I came accross your nice extension. 🚀🚀🚀
I build the conf for this, maybe some people are interested too?
In .vscode/settings.json, add:
  "vscodeGitCommit.template": ["{icon} {type}: {message}"],
  "vscodeGitCommit.variables": {
    "icon": "aliasesIcons",
    "aliasesIcons": [
      {
        "label": ":tada:",
        "detail": "🎉 = Initial (NEW) commit."
      },
      {
        "label": ":construction:",
        "detail": "🚧 = Work in progress."
      },
      {
        "label": ":ambulance:",
        "detail": "🚑 = Critical hotfix."
      },
      {
        "label": ":sparkles:",
        "detail": "✨ = Introducing new features."
      },
      {
        "label": ":beers:",
        "detail": "🍻 = Writing code drunkenly."
      },
      {
        "label": ":hankey:",
        "detail": "💩 = Writing bad code that needs to be improved."
      },
      {
        "label": ":rotating_light:",
        "detail": "🚨 :rotating_light: = Removing linter warnings."
      },
      {
        "label": ":rewind:",
        "detail": "⏪ = Reverting changes."
      },
      {
        "label": ":lock:",
        "detail": "🔒 = Fixing security issues."
      },
      {
        "label": ":zap:",
        "detail": "⚡ = Improving performance."
      },
      {
        "label": ":children_crossing:",
        "detail": "🚸 = Improving user experience / usability."
      },
      {
        "label": ":bug:",
        "detail": "🐛 = Fixing a bug."
      },
      {
        "label": ":bulb:",
        "detail": "💡 = Documenting source code"
      },
      {
        "label": ":white_check_mark:",
        "detail": "✅ = Updating tests."
      },
      {
        "label": ":ok_hand:",
        "detail": "👌 = Updating code due to code review changes."
      },
      {
        "label": ":clown_face:",
        "detail": "🤡 = Mocking things."
      },
      {
        "label": ":boom:",
        "detail": "💥 = Introducing breaking changes."
      },
      {
        "label": ":arrow_up:",
        "detail": "⬆ = Upgrading dependencies."
      },
      {
        "label": ":fire:",
        "detail": "🔥 = Removing code or files."
      },
      {
        "label": ":pencil2:",
        "detail": "✏ = Fixing typos."
      },
      {
        "label": ":loud_sound:",
        "detail": "🔊 = Adding logs."
      },
      {
        "label": ":mute:",
        "detail": "🔇 = Removing logs."
      },
      {
        "label": ":art:",
        "detail": "🎨 = Improving structure / format of the code."
      },
      {
        "label": ":recycle:",
        "detail": "♻ = Refactoring code logic."
      },
      {
        "label": ":construction_worker:",
        "detail": "👷 = Adding CI build system."
      },
      {
        "label": ":rocket:",
        "detail": "🚀 = Deploying stuff."
      },
      {
        "label": ":label:",
        "detail": "🏷 = Adding or updating types (Flow, TypeScript)"
      },
      {
        "label": ":card_file_box:",
        "detail": "🗃 = Performing database related changes."
      },
      {
        "label": ":lipstick:",
        "detail": "💄 = Updating the UI and style files."
      },
      {
        "label": ":twisted_rightwards_arrows:",
        "detail": "🔀 = Merging branches."
      },
      {
        "label": ":package:",
        "detail": "📦 = Updating compiled files or packages."
      },
      {
        "label": ":see_no_evil:",
        "detail": "🙈 = Adding or updating a .gitignore file"
      }
    ],
    "type": "aliasesType",
    "aliasesType": [
      {
        "label": "NEW"
      },
      {
        "label": "REMOVE"
      },
      {
        "label": "RENAME"
      },
      {
        "label": "DOC"
      },
      {
        "label": "UPDATE"
      },
      {
        "label": "IMPROVE"
      },
      {
        "label": "FIX"
      },
      {
        "label": "RELEASE"
      }
    ]
  }

Have fun 🤡

Hi, Thank you for sharing this template and settings <3

Thx to you! 👍
Maybe you could add a templates folder? (instead of my "issue"?
For info: https://twitter.com/jycouet/status/1483951282226401284?t=D0kAGhLHUwOQkvBlGlJxgA&s=19

Hi,
I add a share folder on the repo for the future 😉
PS: I deploy a new version (3.0.0) minutes ago
Have a noice day

UI Configurator looks nice 👍


cmd/go: incorrect version of transitive dependencies downloaded by module-aware go-get

What version of Go are you using (go version)?

[u@x1 cfa]$ go version
go version devel +0a72e8eefb Wed Nov 14 14:45:03 2018 +0000 linux/amd64

Does this issue reproduce with the latest release?
Yes
What operating system and processor architecture are you using (go env)?
go env Output
[u@x1 cfa]$ go env
GOARCH="amd64"
GOBIN=""
GOCACHE="/home/u/.cache/go-build"
GOEXE=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOOS="linux"
GOPATH="/home/u/goget:/home/u/Desktop/go"
GOPROXY=""
GORACE=""
GOROOT="/home/u/go1.11"
GOTMPDIR=""
GOTOOLDIR="/home/u/go1.11/pkg/tool/linux_amd64"
GCCGO="gccgo"
CC="gcc"
CXX="g++"
CGO_ENABLED="1"
GOMOD="/tmp/cfa/go.mod"
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build590699671=/tmp/go-build -gno-record-gcc-switches"

What did you do?

I tried to compile the packages of the cfa repository which depend on the llir/llvm module at version v0.3.0-pre1. Doing so, resulted in a compile time error, as the incorrect version of the llir/ll dependency of llir/llvm was downloaded, even though it was specified in the go.mod file of v0.3.0-pre1 of llir/llvm:
From<EMAIL_ADDRESS>	github.com/llir/ll v0.0.0-20181112013344-5eef2118d0e0

From mewmew/cfa/go.mod:
	github.com/llir/llvm v0.3.0-pre1

An extract of the error output reveals that the version of llir/ll downloaded by the module-aware go get does not contain a definition of ast.AliasDef. However, rev llir/ll@5eef2118d0e091289d0d5f8d69816185550acdf3 of llir/ll contains a definition of ast.AliasDef, so we may conclude that the incorrect version was downloaded.
Error message from go get
# github.com/llir/llvm/asm
/home/u/goget/pkg/mod/github.com/llir/llvm@v0.3.0-pre1/asm/global.go:65:8: undefined: ast.AliasDef

From https://github.com/llir/ll/blob/5eef2118d0e091289d0d5f8d69816185550acdf3/ast/ast.go#L1670:
type AliasDef struct {

To reproduce, run the following set of commands:
export GO111MODULE=on
git clone https://github.com/mewmew/cfa.git
cd cfa
go get -v ./...

The output of which is as follows, and contains the compile time error mentioned above.
go get -v ./... Output
[u@x1 cfa]$ go get -v ./...
Fetching https://gonum.org/v1/gonum?go-get=1
go: finding github.com/mewkiz/pkg v0.0.0-20181108225906-b4dee0c4e703
go: finding github.com/pkg/errors v0.8.0
go: finding github.com/graphism/exp v0.0.0-20181114155108-95804a9f182b
go: finding github.com/llir/llvm v0.3.0-pre1
Parsing meta tags from https://gonum.org/v1/gonum?go-get=1 (status code 404)
get "gonum.org/v1/gonum": found meta tag get.metaImport{Prefix:"gonum.org/v1/gonum", VCS:"git", RepoRoot:"https://github.com/gonum/gonum"} at https://gonum.org/v1/gonum?go-get=1
go: finding gonum.org/v1/gonum v0.0.0-20181112092319-eb6a40d81aaf
Fetching https://golang.org/x/exp?go-get=1
Fetching https://golang.org/x/tools?go-get=1
go: finding github.com/graphism/simple v0.0.0-20181114131118-4c2595ff451f
go: finding github.com/llir/ll v0.0.0-20181113011500-98d5284f035c
go: finding github.com/kr/pretty v0.1.0
go: finding github.com/kr/pty v1.1.3
Parsing meta tags from https://golang.org/x/tools?go-get=1 (status code 200)
get "golang.org/x/tools": found meta tag get.metaImport{Prefix:"golang.org/x/tools", VCS:"git", RepoRoot:"https://go.googlesource.com/tools"} at https://golang.org/x/tools?go-get=1
Parsing meta tags from https://golang.org/x/exp?go-get=1 (status code 200)
get "golang.org/x/exp": found meta tag get.metaImport{Prefix:"golang.org/x/exp", VCS:"git", RepoRoot:"https://go.googlesource.com/exp"} at https://golang.org/x/exp?go-get=1
go: finding golang.org/x/tools v0.0.0-20181111003725-6d71ab8aade0
go: finding golang.org/x/tools v0.0.0-20181114145209-99072bc9d7ad
go: finding github.com/mewspring/tools v0.0.0-20181107085742-4dbfa080ff87
go: finding golang.org/x/exp v0.0.0-20181112044915-a3060d491354
go: finding bitbucket.org/zombiezen/cardcpx v0.0.0-20150417151802-902f68ff43ef
go: finding github.com/mewmew/floats v0.0.0-20181110005823-891ed2b7ecb0
go: finding github.com/inspirer/textmapper v0.0.0-20181111212404-973a0cda8bfa
go: finding github.com/llir/ll v0.0.0-20181112013344-5eef2118d0e0
go: finding github.com/kr/text v0.1.0
go: finding golang.org/x/tools v0.0.0-20180525024113-a5b4c53f6e8b
go: finding github.com/kr/pty v1.1.1
go: finding github.com/inspirer/textmapper v0.0.0-20181104204410-4bdb1fb0392a
go: finding github.com/sergi/go-diff v1.0.0
go: finding golang.org/x/exp v0.0.0-20180321215751-8460e604b9de
go: downloading github.com/graphism/exp v0.0.0-20181114155108-95804a9f182b
go: downloading github.com/mewkiz/pkg v0.0.0-20181108225906-b4dee0c4e703
go: downloading gonum.org/v1/gonum v0.0.0-20181112092319-eb6a40d81aaf
go: downloading github.com/llir/llvm v0.3.0-pre1
go: downloading github.com/pkg/errors v0.8.0
go: downloading bitbucket.org/zombiezen/cardcpx v0.0.0-20150417151802-902f68ff43ef
go: downloading github.com/graphism/simple v0.0.0-20181114131118-4c2595ff451f
go: downloading github.com/llir/ll v0.0.0-20181113011500-98d5284f035c
go: downloading github.com/mewmew/floats v0.0.0-20181110005823-891ed2b7ecb0
go: downloading golang.org/x/exp v0.0.0-20181112044915-a3060d491354
gonum.org/v1/gonum/graph
gonum.org/v1/gonum/blas
gonum.org/v1/gonum/internal/asm/c128
bitbucket.org/zombiezen/cardcpx/natsort
gonum.org/v1/gonum/internal/asm/f32
github.com/graphism/simple/internal/ordered
github.com/graphism/simple/internal/set
gonum.org/v1/gonum/graph/iterator
github.com/graphism/simple/internal/uid
gonum.org/v1/gonum/internal/asm/f64
gonum.org/v1/gonum/internal/math32
gonum.org/v1/gonum/lapack
github.com/llir/llvm/internal/enc
github.com/llir/llvm/ir/enum
github.com/mewmew/floats/binary16
github.com/llir/llvm/ir/types
github.com/mewmew/floats/float80x86
github.com/pkg/errors
github.com/llir/llvm/ir/value
github.com/llir/llvm/ir/metadata
github.com/mewkiz/pkg/term
github.com/llir/llvm/ir/constant
gonum.org/v1/gonum/graph/encoding
gonum.org/v1/gonum/graph/formats/dot/ast
gonum.org/v1/gonum/graph/formats/dot/internal/token
gonum.org/v1/gonum/blas/gonum
gonum.org/v1/gonum/floats
gonum.org/v1/gonum/graph/formats/dot/internal/lexer
gonum.org/v1/gonum/graph/formats/dot/internal/astx
github.com/llir/llvm/ir
gonum.org/v1/gonum/graph/formats/dot/internal/errors
gonum.org/v1/gonum/graph/internal/ordered
gonum.org/v1/gonum/graph/formats/dot/internal/parser
gonum.org/v1/gonum/graph/internal/set
github.com/llir/ll
gonum.org/v1/gonum/graph/formats/dot
gonum.org/v1/gonum/graph/encoding/dot
github.com/llir/llvm/asm/enum
github.com/mewkiz/pkg/osutil
github.com/mewkiz/pkg/pathutil
golang.org/x/exp/rand
gonum.org/v1/gonum/graph/internal/uid
gonum.org/v1/gonum/graph/internal/linear
gonum.org/v1/gonum/graph/traverse
gonum.org/v1/gonum/blas/blas64
gonum.org/v1/gonum/lapack/gonum
github.com/llir/ll/selector
github.com/llir/ll/ast
gonum.org/v1/gonum/lapack/lapack64
gonum.org/v1/gonum/mat
github.com/graphism/simple
gonum.org/v1/gonum/graph/simple
github.com/graphism/exp/cfg
gonum.org/v1/gonum/graph/path
github.com/mewmew/cfa/primitive
github.com/mewmew/cfa/interval
github.com/mewmew/cfa/cmd/restructure_interval
github.com/llir/llvm/asm
# github.com/llir/llvm/asm
/tmp/gofoo/pkg/mod/github.com/llir/llvm@v0.3.0-pre1/asm/global.go:65:8: undefined: ast.AliasDef
/tmp/gofoo/pkg/mod/github.com/llir/llvm@v0.3.0-pre1/asm/global.go:68:37: old.ContentType undefined (type ast.LlvmNode has no field or method ContentType)
/tmp/gofoo/pkg/mod/github.com/llir/llvm@v0.3.0-pre1/asm/global.go:74:8: undefined: ast.IFuncDef
/tmp/gofoo/pkg/mod/github.com/llir/llvm@v0.3.0-pre1/asm/global.go:77:37: old.ContentType undefined (type ast.LlvmNode has no field or method ContentType)
/tmp/gofoo/pkg/mod/github.com/llir/llvm@v0.3.0-pre1/asm/global.go:145:9: undefined: ast.AliasDef
/tmp/gofoo/pkg/mod/github.com/llir/llvm@v0.3.0-pre1/asm/global.go:153:9: undefined: ast.IFuncDef
/tmp/gofoo/pkg/mod/github.com/llir/llvm@v0.3.0-pre1/asm/global.go:331:61: undefined: ast.AliasDef
/tmp/gofoo/pkg/mod/github.com/llir/llvm@v0.3.0-pre1/asm/global.go:373:61: undefined: ast.IFuncDef
/tmp/gofoo/pkg/mod/github.com/llir/llvm@v0.3.0-pre1/asm/helper.go:332:43: oldFlag.Text undefined (type ast.DIFlag has no field or method Text)
/tmp/gofoo/pkg/mod/github.com/llir/llvm@v0.3.0-pre1/asm/module.go:71:9: undefined: ast.AliasDef
/tmp/gofoo/pkg/mod/github.com/llir/llvm@v0.3.0-pre1/asm/module.go:71:9: too many errors

What did you expect to see?
Successful compilation.
What did you see instead?
The compile error detailed above.

This seems to be working as designed. The dependency via github.com/llir/llvm is as you say, but you also have a higher requirement via github.com/graphism/exp.
In general, you should be able to use go mod graph to diagnose these sorts of issues:
cfa$ go mod graph | grep 'llir/ll@'
<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>
cfa$ go mod why -m github.com/graphism/exp
# github.com/graphism/exp
github.com/mewmew/cfa/cmd/ll2go_interval
github.com/graphism/exp/cfg

Perhaps we should also have a go mod why mode to query “why this version?” rather than just “why this [package / module]?”. I'll file that separately.


Add navigation to example home using TemPy

This is a similar PR to #64 , but based on that conversation this update uses TemPy to load navigational links to other examples when the user navigates to / after running the tempy_examples.py script; this is in lieu of static HTML element tags, which the aforementioned PR used.

Coverage decreased (-0.04%) to 92.944% when pulling d1e1bc0d1a833bcaf34bafbd2ac39bbfa69935ae on Chiouonthis:add_navigation_to_example_home into 06f2b9226b403fbde09b8694e4125186e21694cd on Hrabal:master.

Coverage decreased (-0.04%) to 92.944% when pulling d1e1bc0d1a833bcaf34bafbd2ac39bbfa69935ae on Chiouonthis:add_navigation_to_example_home into 06f2b9226b403fbde09b8694e4125186e21694cd on Hrabal:master.

Thanks again.


darkening headers

made a small tweak based on feedback in https://github.com/prebid/prebid.github.io/issues/1160
I think the darker header goes part of the wayw towards improving the readability.

Darker text sounds fine to me.


Removed deprecated Mozilla Parser API defs in favor of ESTree.

Original PR: #3201
Removed as per: #4052
/cc @teppeis @vvakame

@RReverser thanks mate!


fix panic when using storage redirect middleware

fix panic when using storage redirect middleware in registry version 2.5.1
When we start registry with storage redirect middleware in config file, it will panic. The error message can be show as follows:
unable to configure storage middleware (redirect): no storage middleware registered with name: redirect

this PR fix this problem by importing storage redirect middleware in main.go

Please sign your commits following these rules:
https://github.com/docker/docker/blob/master/CONTRIBUTING.md#sign-your-work
The easiest way to do this is to amend the last commit:
$ git clone -b "release/2.5" git@github.com:Windfarer/distribution.git somewhere
$ cd somewhere
$ git commit --amend -s --no-edit
$ git push -f

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

Current coverage is 52.57% (diff: 100%)

Merging #2081 into release/2.5 will decrease coverage by 10.12%

@@           release/2.5      #2081   diff @@
=============================================
  Files              120        120
  Lines            10496      10496
  Methods              0          0
  Messages             0          0
  Branches             0          0
=============================================
- Hits              6581       5518   -1063
- Misses            3038       4237   +1199
+ Partials           877        741    -136

Powered by Codecov. Last update 2c3b616...c9ba151

We likely are not going to do a 2.5.2 release, the original change can be picked up in 2.6.0-rc1 by using the image registry:2.6.0-rc.1.

@dmcgowan We cannot run an RC version in production environment. Could you tell me when is the release date of stable 2.6 version? Thanks a lot.

LGTM


Break large Mithril object into named functions to improve readability and hopefully maintainability by breaking it into logical chunks.
Use the m prefix on a function to indicate you'll get a mithril object back (or null).
Add the timestamp itself to the ctrl.start and ctrl.end objects in addition to the date and time strings so we can do direct ts comparisons.
Fix a bunch of logic around the Publish and Unpublish buttons and timestamp comparisons.

[ fixes #125 ]

Not sure what these Travis failures are. I'll take a closer look first thing on Monday.

Just checked with @tivac and I've been informed I can safely ignore the Travis build errors, since they're due to some particular quirk in the version of Node the build is running.

Where'd the Unpublish button go?

@ctcleary Sorry, last thing. Would you please style the "Clear Schedule" button to look like the other buttons? After that I think we're good.


Add option for retrieving first empty workspace

Describe your PR, what does it fix/add?
This pull request adds a new option to reference workspaces with: "empty".
It references the first empty workspace, i.e. the workspace with the smallest (positive) workspace ID without any windows.
The new option allows to e.g. focus an empty workspace or move a window to an empty workspace by using something like this:
bind = $MOD, $KEY1, workspace, empty
bind = $MOD, $KEY2, movetoworkspace, empty

These examples are equivalent to the ws_empty and ws_empty_move actions in spectrwm.
Is there anything you want to mention? (unchecked code, possible bugs, found problems, breaking compatibility, etc.)
I will add a pull request for updating the wiki entry soon after.
Is it ready for merging, or does it need work?
It is ready for merging.

There is a function to retrieve the highest workspace ID in CCompositor iirc. Why not use that?
Also, make a wiki entry prior to merge. I'll merge both at once

I assume you mean CCompositor::workspaceIDOutOfBounds() and to use the workspace ID which is out of bounds as new empty workspace?
I decided against this approach due to three reasons:

There may be workspaces without any windows but still within m_vWorkspaces. Empty workspaces seem to be only removed in CCompositor::sanityCheckWorkspaces(). I am not sure whether this is called often enough to ensure that only non-empty or active empty workspaces are present when getWorkspaceIDFromString() is called.
If an empty workspace is currently focused, the focus would be switched to a new empty workspace, since the current empty workspace is considered to be in bounds.
If we have e.g. two non-empty workspaces with IDs 1 and 3, this approach would result in ID 4 while ID 2 would be the first empty workspace. In general, empty workspaces within the range given by the lowest to highest IDs of non-empty workspaces will never be considered and the IDs potentially becoming larger and larger.

Please correct me, if any of my assumptions are wrong or there is another reason to prefer CCompositor::workspaceIDOutOfBounds(). Thank your for all your work and time for Hyprland!

I see your points. Makes sense, sure. Thanks!


Database queue timeout when waking up computer from suspend

Laravel Version: 8.6.0
PHP Version: 7.4.10
Database Driver & Version: pgsql, PostgreSQL 12.4

Description:
php artisan queue:listen throws ProcessTimedOutException when waking up the computer from suspend.

   Symfony\Component\Process\Exception\ProcessTimedOutException

  The process "'/usr/bin/php' 'artisan' 'queue:work' '--once' '--name=default' '--queue=default' '--backoff=0' '--memory=128' '--sleep=3' '--tries=1'" exceeded the timeout of 60 seconds.

  at vendor/symfony/process/Process.php:1201
    1197▕
    1198▕         if (null !== $this->timeout && $this->timeout < microtime(true) - $this->starttime) {
    1199▕             $this->stop(0);
    1200▕
  ➜ 1201▕             throw new ProcessTimedOutException($this, ProcessTimedOutException::TYPE_GENERAL);
    1202▕         }
    1203▕
    1204▕         if (null !== $this->idleTimeout && $this->idleTimeout < microtime(true) - $this->lastOutputTime) {
    1205▕             $this->stop(0);

      +19 vendor frames
  20  artisan:37
      Illuminate\Foundation\Console\Kernel::handle(Object(Symfony\Component\Console\Input\ArgvInput), Object(Symfony\Component\Console\Output\ConsoleOutput))

Steps To Reproduce:

Set QUEUE_CONNECTION=database in .env
Run php artisan make:job JobName
Run php artisan queue:table
Run php artisan migrate
Run php artisan queue:listen
Suspend computer (Linux if relevant)
Wake up computer and you get this error

Hi there,
Thanks for reporting but it looks like this is a question which can be asked on a support channel. Please only use this issue tracker for reporting bugs with the library itself. If you have a question on how to use functionality provided by this repo you can try one of the following channels:

Laracasts Forums
Laravel.io Forums
StackOverflow
Discord
Larachat
IRC

However, this issue will not be locked and everyone is still free to discuss solutions to your problem!
Thanks.

According to people on IRC what I'm looking for is too low level for a framework like Laravel.
Some suggestions and comments:

Keep PC always on
Get a server
Run the queue on supervisord
Use --timeout 0 but add a timeout in the job itself


This lesson needs to be looked over, had to look up troubleshooting.

Challenge Escape Sequences in Strings has an issue.
User Agent is: Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/49.0.2623.87 Safari/537.36.
Please describe how to reproduce this issue, and include links to screenshots if possible.
My code:
var myStr;
myStr = "\\ \t \t \r \n";// Change this line

@Og-Morrow what exactly are you having trouble with?

what is the issue i went to your link working for me

I fixed the issue. I'm not experienced enough to speak with clarity but the
myStr = " escape sequences "; had to go below and the lesson made it clear
that just the line had to be changed but when you do that then the code
doesn't work
On Mar 20, 2016 12:52 PM, "Ka Lun Lee"<EMAIL_ADDRESS>wrote:

@Og-Morrow https://github.com/Og-Morrow what exactly are you having
trouble with?
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
https://github.com/FreeCodeCamp/FreeCodeCamp/issues/7664#issuecomment-198973747

exercise says Encode the following sequence, separated by spaces:
backslash tab tab carriage-return new-line and assign it to myStr and that is what you did there
var  myStr;
myStr = "\ \t \t \r \n";// Change this line
or you can just write like
var myStr = "\ \t \t \r \n";// Change this line

Right, I tried is this way "var myStr = "\ \t \t \r \n";// Change this line" and just could not figure out why it wasnt working, heres the page i found the answer. I just wanted to help others before they have to go throught the same thing.
https://github.com/FreeCodeCamp/FreeCodeCamp/issues/5673

do like
var myStr = "\\ \t \t \r \n";// Change this line
not like
var myStr = "\ \t \t \r \n
can you please come at https://gitter.im/FreeCodeCamp/Help

Closing as resolved. Thanks and happy coding!


Query methods ancestor, preceding-sibling, following-sibling

Hi @enikao, @dslmeinte, @JojoEffect,
As far as I am concerned, the current implementation lacks the following methods, as explained below:
Ancestor: queries the ancestor nodes filtered by a type, something like:
public static T? Ancestor<T>(this INode node, bool includeSelf = false) where T : INode =>
    node.Ancestors(includeSelf)
        .OfType<T>()
        .FirstOrDefault();

PrecedingSibling  (PrevSiblings) / FollowingSibling  (NextSiblings): queries previous/next siblings of a node, with an optional parameter that specifies whether to include the current node.

The question is whether we should implement this in lionweb-csharp or a downstream project. Do you think it's generally useful?

Compare to XPath axes: https://www.w3.org/TR/1999/REC-xpath-19991116/#axes


Not able to connect from other containers in docker-compose

Describe the bug
It is not possible to comunicate to emulator form other docker services.
It works fine for emulator started over docker to locally running services, but it does not work on docker network
To Reproduce
Minimal reproduction issue:
https://github.com/krystianolech/event-hub-emulator-issue
If we would run this docker-compose (docker-compose up -d) and then run local nodejs script, message are publihed.
However same service within docker is not able to send message and is hanging while trying to send message.
For local connection string is used:
Endpoint=sb://localhost;SharedAccessKeyName=RootManageSharedAccessKey;SharedAccessKey=SAS_KEY_VALUE;EntityPath=eh1;UseDevelopmentEmulator=true;
while in docker endpoint is changed to name of container with emulator:
sb://eventhubs-emulator;SharedAccessKeyName=RootManageSharedAccessKey;SharedAccessKey=SAS_KEY_VALUE;EntityPath=eh1;UseDevelopmentEmulator=true;
I tried both Endpoint=sb://eventhubs-emulator and Endpoint=sb://emulator.
Setting any name give ENOTFOUND error so its clear that service is connecting to emulator container
Docker Version:
Docker version 26.1.1, build 4cf5afa
Arguments && Environment variables to start Emulator:

ACCEPT_EULA:Y

Emulator Launch Method:

Direct Docker compose

This is related to: https://github.com/Azure/azure-event-hubs-emulator-installer/issues/9
As a working alternative you can try out the following setup:
name: "eventhubs-emulator-with-containerized-app"
services:
  azurite:
    image: mcr.microsoft.com/azure-storage/azurite
    network_mode: host

  emulator:
    image: mcr.microsoft.com/azure-messaging/eventhubs-emulator:latest
    volumes:
      - "./Config.json:/Eventhubs_Emulator/ConfigFiles/Config.json"
    environment:
      BLOB_SERVER: localhost
      METADATA_SERVER: localhost
      ACCEPT_EULA: "N"
    network_mode: host
    depends_on:
      - azurite

  sample-containerized-app:
    build:
      context: .
      dockerfile: ./Dockerfile
    network_mode: host
    depends_on:
      - emulator

Few things to note:
a) EULA Flag
b) Connection string used :
"Endpoint=sb://localhost;SharedAccessKeyName=RootManageSharedAccessKey;SharedAccessKey=SAS_KEY_VALUE;EntityPath=eh1;UseDevelopmentEmulator=true;"

c) Sample application should wait for few seconds to allow Emulator to bootup and accept requests

thank you for the update!
Unfortunately it would not work best for my uescase as I have more containers with conflicting ports in that docker-compose file so it would would require more adjustments to separate ports.
Do you know if making it possible to use different host is on a rode map for simulator and when approximately it would be available?

Running into a similar issue.  When packaging event hubs emulator along with other services in our software stack, we keep getting connection refused errors.  Trying to change it from localhost to anything else we get the following: The Event Hubs emulator is only available locally.  The endpoint must reference to the local host. (Parameter 'connectionString')

@AlthalusDGr8; Which language and version of EH Client SDK are we using? This seems like an error from client SDK side.
This check exists in initial versions of SDKs which started out supporting Emulator, upgrading to latest SDK version along with host networking workaround mentioned above should allow you to use the Emulator meanwhile the patch rolls around for this issue.

@AlthalusDGr8; Which language and version of EH Client SDK are we using? This seems like an error from client SDK side.
This check exists in initial versions of SDKs which started out supporting Emulator, upgrading to latest SDK version along with host networking workaround mentioned above should allow you to use the Emulator meanwhile the patch rolls around for this issue.

Tried with both version 5.11.2 and 5.11.3, get the same error (just to be sure, we are using this lib: Azure.Messaging.EventHubs).
As for using the hosts we want to avoid doing so for the time being, so we keep network isolation like the other containers.  We shall wait for the patch and see how it goes from there.

Same here. I'm working on a PoC including Debezium and Azure Event Hub.
My goal is to get a local "installation" of MariaDB, Debezium and Azure Event Hub Emulator. For this I tried a docker compose setup but the debezium container isn't able to connect to the emulator container.

@krystianolech / @piwo1984 - Thanks for bringing this to our attention. Our team is working on fixing above-described behavior. We expect the fix to be shipped with upcoming milestone.

Hi everyone, this issue has been patched with the latest release.
Other containers on the same bridge network can now interact with Emulator using the container alias or IP.  Example connection string below assuming the name of Emulator container is unchanged in default docker compose and is "eventhubs-emulator" :
"Endpoint=sb://eventhubs-emulator;SharedAccessKeyName=RootManageSharedAccessKey;SharedAccessKey=SAS_KEY_VALUE;UseDevelopmentEmulator=true;"

Additionally, if containers are not on the same bridge network "host.docker.internal" can be used as host in the connection string.
"Endpoint=sb://host.docker.internal;SharedAccessKeyName=RootManageSharedAccessKey;SharedAccessKey=SAS_KEY_VALUE;UseDevelopmentEmulator=true;"

Just tested with 1.2.4-preview and works great - thanks!

Confirmed that it worked for me as well thanks

@AlthalusDGr8 @mr-panucci
Which client SDK are you using that had this update? I'm using the one for .NET Azure.Messaging.EventHubs, and it is still refusing to connect

@AlthalusDGr8 @mr-panucci
Which client SDK are you using that had this update? I'm using the one for .NET Azure.Messaging.EventHubs, and it is still refusing to connect

Am using the following nuget: https://www.nuget.org/packages/Azure.Messaging.EventHubs/5.11.3.  Perhaps you can share your yaml,config and connection string maybe we can spot something?

@AlthalusDGr8 @mr-panucci
Which client SDK are you using that had this update? I'm using the one for .NET Azure.Messaging.EventHubs, and it is still refusing to connect

Am using the following nuget: https://www.nuget.org/packages/Azure.Messaging.EventHubs/5.11.3. Perhaps you can share your yaml,config and connection string maybe we can spot something?

The problem is in the client SDK itself not the emulator.
Even though I'm using the correct version of Azure.Messaging.EventHubs, I'm also using this Microsoft.Azure.Functions.Worker.Extensions.EventHubs in a function app, which uses the old version of Azure.Messaging.EventHubs that won't connect to the emulator unless if it was "localhost"

@krishankumar95
I tried that but the Microsoft.Azure.Functions.Worker.Extensions.EventHubs overrides it with its "Azure.Messaging.EventHubs" version "5.11.2" and I keep getting the same error
Azure.Messaging.EventHubs: The Event Hubs emulator is only available locally.  The endpoint must reference to the local host. (Parameter 'connectionString').


[wip] refactor: transaction filter as a modal for mobile devices

Summary
https://app.clickup.com/t/863h8wx7b
requires https://github.com/ArkEcosystem/laravel-foundation/pull/590
Created a new Livewire Paginator which serialises the data between requests. This is instead of using a computed property so the data can be updated as and when, though I'm not sure it's necessary since it now uses the wire:target

[ ] tests?
[x] fix loading of table list on open of modal

Checklist

[ ] I checked my UI changes against the design and there are no notable differences
[ ] I checked my UI changes for any responsiveness issues
[ ] I checked my UI changes in light AND dark mode
[ ] I checked my (code) changes for obvious issues, debug statements and commented code
[ ] I opened a corresponding card on Clickup for any remaining TODOs in my code
[ ] I added a short description on how to test this PR (if necessary)
[ ] Documentation (if necessary)
[ ] Tests (if necessary)
[ ] Ready to be merged

Closing to use the JS method instead in #463


Fix encoder bug when finishing

Via some fuzzing, I found a finish scenario that can result in incorrect encoding. This PR addresses the bug by adding a check for finishing && input size == 0 in the search step to transition to flush bits.
Explanation:
At finish time, if the input_size is 0 then there is no more data to encode and the remaining bits should be flushed. However, because the search step does input_size - 1 this results in an overflow and the search step transitions to yielding a tag bit instead. I'm not really sure what happens from this point on, but I suspect it may loop infinitely.

This kinda sounds like a bug I encountered a few months back, that was triggered, when the following set of conditions were met:

The output buffer was full
The output of the last literal was mid-way (in my case first bit of last literal value written, 7 more for the literal to go that didn't fit)
No further bytes in the input buffer
The encoder trying to finish up

Due to some API inconsistency, the return value was EMPTY instead of OUTPUT_MORE, thus my driver code for compression ended up inadvertently dropping the last byte of the output. It didn't cause an infinite loop, but rather an early termination of the encoder. The example implementation of the CLI utility is not affected; and also was, what in the end allowed me to locate my encoder bug.

It didn't cause an infinite loop, but rather an early termination of the encoder.

That's the behavior I noticed in a Rust port I'm writing. But I wasn't totally convinced there was no loop in the C implementation here.

I also encountered this during some fuzzing on a Rust port. My st_step_search impl looks like this now
fn st_step_search(&mut self) -> HSEState {
    let window_length = self.input_buffer_size;
    let lookahead_sz = self.lookahead_size;
    let msi = self.match_scan_index;

    if msi > self.input_size.saturating_sub(lookahead_sz) {
        return HSEState::SaveBacklog;
    } else if unlikely(self.is_finishing()) && msi >= self.input_size {
        return HSEState::FlushBits;
    }

    let input_offset = self.get_input_offset();
    let end = input_offset + msi;
    let start = end - window_length;

...


Doc update for AWS source-destination-check

Description
Doc update for AWS source-destination-check:

Update calico-vxlan.yaml
Update FelixConfiguration

Related issues/PRs
documents https://github.com/projectcalico/libcalico-go/pull/1249
documents https://github.com/projectcalico/felix/pull/2381
Todos

[ ] separate AWS source-destination-check?

Release Note
None required

Deploy preview for calico ready!
Built with commit 15a318c0e7d5465cce3d74360d06f5c204c087fc
https://deploy-preview-3652--calico.netlify.app

Added "hold-merge" until the code PR is merged.


MINOR: Remove unused field in Topic.java

Remove unused field in Topic.java
Committer Checklist (excluded from commit message)

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation (including upgrade notes)

@showuon Maybe this is too minor change and not sure just delete unused field. But review please.

@YeonCheolGit , thanks for the PR. Have a quick search and found this veariable is used in here. Why should we remove the variable that is still used in the code?

@YeonCheolGit , thanks for the PR. Have a quick search and found this veariable is used in here. Why should we remove the variable that is still used in the code?

Thanks for the review! And sorry, i missed checking that Scala code.
I am closing this PR and thanks for the the review again:)


This is not working

I treid it but this is not working. Please help me out

Where to include above code. in base.html or somewhere else
Please provide better gudie
I'm trying to include this package in this websites
http://sandeepkush.herokuapp.com/
It only works when i open new windows for chat

if you want the chat to appear on every page, this script goes in the base.html.


Portfolio Section editing experience

Issue details from Bug#A0A6-I9
Unable to edit Portfolio initial values (read only)

Sorry, this issue should be filed to sanity-packages repository. Closing this. Thanks!


Initial view flash when using alpha nvim splash screen

Hi! I'm trying to use this plugin, however it produces a visual flash of the stock nvim starting screen when I use it with alpha-nvim's splash screen. Do you know of a way to fix it? Thanks!
https://github.com/user-attachments/assets/0621047d-b908-4896-a94a-dce327084a3d

Hi there @sainttttt! Not really sure how alpha.nvim works, but reactive calls the "redraw" when it needs to correctly reflect current mode/operator
There's a neovim option called shortmess (:h 'shortmess') in which you can disable the startup screen, specifically doing this disables it for me:
vim.opt.shortmess:append('I')

Please try if it's gonna work with alpha-nvim


Q3 USPS County Address Point Submissions

Benefit
Improved addressing and mail delivery in rural Utah.
Acceptance Criteria

County address points submitted to the USPS

[ ] Box Elder
[ ] Millard
[ ] Sevier

...

Notes
No response
Risks
No response
Issue Reference
refs #

Box Elder and Millard have been submitted however the USPS said that the values in the City field are incomplete. Waiting to hear back on how to assign an address to a city if it's in an unincorporated part of the county.

Q3 Sprint 5 Tasks

[ ] Submit Tooele County address points.

Q3 tasks completed. The USPS submission process will be started the week of March 25th. Moving on to Q4 tasks.


Update to Cats 1.0.0-RC1

I want to wait to publish until we have an iteratee.io release for Cats 1.0.0-RC1 (see this issue), but this seems to compile.

Codecov Report

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

@@            Coverage Diff            @@
##             master     #773   +/-   ##
=========================================
  Coverage          ?   85.81%
=========================================
  Files             ?       73
  Lines             ?     2305
  Branches          ?       88
=========================================
  Hits              ?     1978
  Misses            ?      327
  Partials          ?        0

Impacted Files
Coverage Δ

.../shared/src/main/scala/io/circe/ArrayEncoder.scala
77.77% <ø> (ø)

.../core/shared/src/main/scala/io/circe/Encoder.scala
97.75% <ø> (ø)

...re/shared/src/main/scala/io/circe/KeyEncoder.scala
100% <ø> (ø)

...shared/src/main/scala/io/circe/ObjectEncoder.scala
90% <ø> (ø)

Continue to review full report at Codecov.

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

Okay, after #774 this is no longer WIP.

It'll take me a bit to run all the Scala.js tests, etc., but I'm planning to publish 0.9.0-M2 this afternoon.